Alarm: Local Management-To-NMC Integrated EM Sensor Communication Lost: Universal I/O at Port 1

[Anonymous user]

After updating our Firmware to V6.4.0 we're now getting the alarm in the subject line. Resetting only the "Lost Environment Communications Alarms" and rebooting the Management Interface have no affect. Looking in the Event Log, the error only occurs when the interface is rebooted. (IPs taken out, but are present)

08/18/2016	08:59:44	Device	Environment: Lost the local network management interface-to-integrated Environmental Monitor (Universal I/O at Port 1) communication.
08/18/2016	08:59:43	Device	Environment: Restored the local network management interface-to-integrated Environmental Monitor (Universal I/O at Port 1) communication.
08/18/2016	08:59:41	System	Network service started. IPv6 address x.x.x.x assigned by link-local autoconfiguration.
08/18/2016	08:59:39	System	Network service started. System IP is x.x.x.x from manually configured settings.
08/18/2016	08:59:33	System	Network Interface restarted.
08/18/2016	08:59:25	admin	Network Interface restarting. Web user request.

System info is as follows:

Hardware Factory

Model Number: AP8941

Hardware Revision: 02

Network Management Card

Model Number: AP9537

Hardware Revision: 05

Application Module

Name: sumx

Version: v6.4.0

APC OS (AOS)

Name: aos

Version: v6.4.0

APC Boot Monitor

Name: bootmon

Version: v1.0.8

This system is in production so taking it offline will require some coordination.

Any help is appreciated.

[BillP]

Hi Ben,

Can you share the full event.txt file? You can export it from the web interface using the little floppy disk icon when you're viewing the event log.

Is anything physically connected to the Universal I/O port on the PDU? From an overall perspective, is there anything else besides a network cable connected to the display module on the PDU? And if so, what port is it in?

It is normal after the reboot to have 5-6 status messages like established communication with UIO port 1 but of course it shouldn't be telling you "lost communication" afterwards. I'd like to just see the full event log and see if anything else catches my eye and then hopefully you can tell me what is plugged in where, if anything.

What firmware did you have on prior? You're saying that you didn't see these types of messages before you upgraded the firmware?

Again, in the big picture, is this a single PDU showing this behavior or did you upgrade multiple units and just this one is showing an issue, even though others are setup the same way?

[Anonymous user]

Event file attached.

On the PDU we have a network cable and I don't know if it's some sort of loopback or just a protector, but it is similar to the link below. It's in the "Out" port of the PDU. I've rebooted the Network interface with and without that plugged in, no difference there.

Part #0W05545A

http://www.pdlglobal.com/data/product_images/1733_main_image.jpg 

Looking at the entire Event Log now, after upgrading the firmware we couldn't log back into the system, our network engineer had to go and reconfigure as you can see. Could this be some sort of configuration issue then?

I can't say what firmware version we had before, we're good at keep everything up to date, so I'd like to say it was the previously released version.

We have multiple PDUs at varies locations, we were able to upgrade them all no problem, this is our only problem child. And yes, they would all be configure the same.

[BillP · Accepted solution]

Hi Ben,

The 0W05545A is referred to as a CAN bus terminator which is OK to have plugged into the in or out port. You use it specifically when you're utilizing our Network Port Sharing feature which physically connects up to 4 of these AP8XXX series Rack PDUs together over the CAN bus and you can share one IP address across all of them. The terminator gets moved to the beginning and end of your chain you create when doing this so we include a terminator with each PDU so that if you decide to use this feature, you have some available. Also, specifically, a few of the models, AP86XX and AP84XX I think too which offer metering by outlet functionality require the terminators to remain in or else a singular PDU of those types won't work properly. Your model doesn't require it for singular operation technically but you should leave it there as to not misplace it 

Here is what I'd do if you can - is it possible to downgrade the one PDU one revision to see if the error still comes about? I can provide this firmware for you if you're willing. I am thinking it is either a coincidence that there is a problem with the UIO port #1 (or something damaged it around the same time) or there is a firmware issue we'd investigate further.

I would say if we downgrade the firmware, and still see the issue, then you may want to live with it if you don't use that port (supports a AP9335T temp or AP9335TH temp humidity sensor). We could also try a sensor in that port to see if it actually works or not regardless of what the error message is telling us, which is the on board management interface lost communication with that port - if you had one from a different product - NetBotz, UPS Network Card, etc. Or, if it sticks around no matter what firmware is loaded and you don't want to live with it (which I'd expect it to show after each reboot), then the display module could be replaced - either at your cost or not sure of your warranty on this one.

Let me know what you think or if you have questions.