Netbotz Rack Monitor 450 - Issue

[DCIM_Support]

When the Netbotz is connected to the input power connection (208Vac) the device turn it on normally (power LED = ON), but, after some seconds / minutes the Netbotz shut off suddenly (power LED = OFF). During a visual inspection, some seconds before the netbotz shutt off by its own, the “Alert LED” flashing twice per second and, in the same time, the “power LED” blinking a couple of times. After that, it turns off completely. note: the Netbotz can not be ON more than 5 minutes... in some times, after some seconds!

 in this point, I have not been able to setup and programing the Netbotz due to is imposiblee to get proper funcionality.

- the PDU was checked. the input voltaje is stable in 208Vac / 60Hz

- the Netbotz was updated from firmware version 4.0 to the last version 4.5 ( SKU: SFNBZ450)

Could you send me some advises or troubleshooting ideas to resolve this issue?

(CID:105457054)

[DCIM_Support]

Hi Luis,

I would first disconnect all physical connections. Disconnect power, sensors, Ethernet, everything. Then connect up just the power. Once connected also connect a USB cable used for configuration. Use the following k-base to reset the unit to defaults: FA158175

You can find k-base here:

http://www.apc.com/site/support/index.cfm/faq/

Once that is done, simply monitor the unit for a period of time. Does it continue to reboot? If so you may want to try to re-flash the appliance with 4.5 firmware. If that does not work either, I suggest looking to tech support for a possible replacement.

If disconnecting everything, resetting the appliance or re-flashing it works, then connect the network cable and continue to monitor the unit. If connecting the network cable causes the unit to again reboot, perhaps there is some sort of ground loop issue. If not, re-connect any previous connections one by one making sure they are connected to the proper ports. For instance, don't connect one NetBotz appliance to another, don't connect anything but a sensor pod or proper sensor to the A-link ports etc.

Looking at each component and connection individually, you should be able to isolate the issue.

Thanks,

Steve

(CID:105457058)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.