AP8853 Communication Lost error messages

[DCIM_Support]

Good day

I applied firmware updates (6.4.4) in DCE 7.3.1 to PDUs in a private network. All other connected devices updated as expected except 2 which give continuous alerts after the update was effected.

Subsequently emails are sent every 5 min for communication lost to the PDUs. I have attempted to adjust the timeouts and retries but nothing seems to work.

Alert   Type:

Communication   Lost

 Is there anything I can do to stop the system sending errors without disabling monitoring?

(CID:110004354)

[DCIM_Support]

Hi Molefi,

You should be able to put that device in maintenance mode by right clicking it and that should disable any messages until you have a chance to resolve the main issue which is the lost comm. There are other options as well.

Click the alarm configuration button just below the menus:

You should see threshold alarm configurations and device alarm configurations. If this communications error is due to DCE loosing SNMP communications with the device, click the threshold alarm configurations tab, select the specific device on the left, and edit the communications status. You can set enabled to no:

If this error is a lost comm between the NMC and the PDU, that would be error specific. Click on the device alarm configuration and the specific PDU and choose the appropriate error:

Once you have this resolved, try to log on to the PDU using a web browser. If you can't get to it, you may need to reboot it. Depending on what happened, you may need to serially access the device. If it is indeed SNMP communications, k-base FA226273 may be helpful in troubleshooting SNMP communications.

Thanks,

Steve.

(CID:110004359)

[DCIM_Support]

Hi all,

I had too several similar problems, which are not a rarity at family of these RPDU's. At the same time, bootmon (APC Boot Monitor) and aos (APC OS) load normally, and here the attempt to load rpdu2g (Application Module) comes to an end with failure (a connection timeout). As a result of the LCD screen on RPDU is in the frozen status, or displays nothing.

For the solution of this problem, just it is necessary to reboot RPDU clicking the hidden button. Attention: The LCD screen won't react to this action in any way, and it is possible to think that nothing occurred, but it is normal. After this RPDU shall appear on a network and it can be updated repeatedly by means of the DCE server.

If RPDU on a network doesn't appear, it is necessary in addition to reset all settings to factory default by long-time clicking the hidden button. Besides, the LCD screen won't react to it in any way, but about result it is possible to judge by a blinking of LED's on the network connector. Then, as it is written to install guide, to setup again the IP address for this RPDU (if the DHCP server isn't used) and to achieve appearance of RPDU on a network. After that the procedure of updating can be repeated again.

I personally performed all these operations and noticed as once again I will repeat, it happens not seldom and to different firmwares.

Very thanks for the support.

(CID:110004445)

[DCIM_Support]

Hi Molefi,

• try to log on directly notebook - pdu using web browser but use extra one network cable

I had the case in this year: by 10 PDU updates via DCE I've got 2 pdu with communication lost messages. After 3 hours troubleshooting it turned out that network cables went broken by the updates.

Regards

Jarek

(CID:110004377)

[DCIM_Support]

Good day

Thank you kindly for the advice. I did apply some of what you included in the replies and it helped a lot. The problem was caused by a simple IP conflict between the PDU devices. I went in locally with a serial cable and verified the IP addresses. Once I discovered the discrepancies I rectified them. I think it was incorrect assignment by the operator who programmed the IP addresses on the PDUs.

Thank you kindly for the advice. I also learned some new tricks that I didn't know prior to this.

Regards,

Molefi

(CID:110004663)

[DCIM_Support]

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