Smart-UPS RT 6000 - Error

[Anonymous user]

All time my UPS have a log with this message "The local network management interface-to-UPS
communication not established"...

What does that mean?

[BillP]

This means your Network Management Card cannot talk to your UPS.

Can you provide the full event.txt? (instructions here-> How can I download Event, Data, Configuration, and Debug files from my Network Management Card? | FA...)

Did you recently do anything to the UPS?

Here is some information on this issue -> http://www.apc.com/support/index?page=content&country=US〈=en&id=FA156045

It doesn't cover all possibilities but we'll check your firmware (which I can see in the log file I asked for), what is connected to the rear of the UPS if you go back there and look, if the UPS has multiple accessories installed, and we can also try re-seating the card.

Let me see that event.txt file first and we'll see what our next steps will be based on that.

[Anonymous user]

I don't know if have a problem, but I use 2 communications with my UPS.

One by network and other by serial port.

event.txt

Network Management Card AOS v5.1.3
Smart-UPS & Matrix-UPS APP v5.1.3

Date  Time  Name Contact Location System IP
24.10.2013 09:11:13 CAL05NB01 - 192.168.120.41

Date  Time  Event Code
24.10.2013 09:09:21 System: FTP user 'apc' logged in from 192.168.101.12. 0x0016
24.10.2013 08:35:00 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
24.10.2013 08:30:40 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
22.10.2013 14:22:30 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
22.10.2013 14:19:19 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
22.10.2013 10:03:55 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
22.10.2013 10:00:55 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
20.10.2013 05:57:05 UPS: No longer on battery power. 0x010A
20.10.2013 04:13:03 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
20.10.2013 04:09:40 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
20.10.2013 01:08:52 UPS: On battery power in response to an input power problem. 0x0109
18.10.2013 08:09:12 UPS: Restored the local network management interface-to-UPS communication. 0x0101
18.10.2013 08:09:03 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
18.10.2013 08:08:58 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
18.10.2013 08:08:52 System: Warmstart. 0x0002
18.10.2013 06:52:55 UPS: The local network management interface-to-UPS communication not established. 0x0102
18.10.2013 06:52:04 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
18.10.2013 06:51:59 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
18.10.2013 06:51:54 System: Warmstart. 0x0002
18.10.2013 05:35:57 UPS: The local network management interface-to-UPS communication not established. 0x0102
18.10.2013 05:35:06 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
18.10.2013 05:35:02 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
18.10.2013 05:34:56 System: Warmstart. 0x0002
12.10.2013 08:23:29 UPS: Restored the local network management interface-to-UPS communication. 0x0101
12.10.2013 08:23:18 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
12.10.2013 08:23:14 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
12.10.2013 08:23:08 System: Warmstart. 0x0002
12.10.2013 07:07:14 UPS: The local network management interface-to-UPS communication not established. 0x0102
12.10.2013 07:06:23 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
12.10.2013 07:06:19 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
12.10.2013 07:06:13 System: Warmstart. 0x0002
03.10.2013 11:46:26 System: Web user 'apc' logged out from 192.168.121.12. 0x001F
03.10.2013 11:43:00 System: Web user 'apc' logged in from 192.168.121.12. 0x0015
03.10.2013 10:30:59 System: Web user 'apc' logged out from 192.168.121.12. 0x001F
03.10.2013 10:27:08 System: Web user 'apc' logged in from 192.168.121.12. 0x0015
03.10.2013 03:06:03 UPS: Restored the local network management interface-to-UPS communication. 0x0101
03.10.2013 03:05:55 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
03.10.2013 03:05:49 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
03.10.2013 03:05:43 System: Warmstart. 0x0002
03.10.2013 01:49:51 UPS: The local network management interface-to-UPS communication not established. 0x0102
03.10.2013 01:49:00 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
03.10.2013 01:48:56 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
03.10.2013 01:48:50 System: Warmstart. 0x0002
25.09.2013 07:16:54 UPS: No longer on battery power. 0x010A
25.09.2013 07:15:53 UPS: On battery power in response to an input power problem. 0x0109
30.08.2013 17:53:59 UPS: No longer on battery power. 0x010A
30.08.2013 17:23:22 UPS: On battery power in response to an input power problem. 0x0109
20.08.2013 14:13:33 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
20.08.2013 14:10:31 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
19.08.2013 14:36:29 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
19.08.2013 14:32:36 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
19.08.2013 14:19:47 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
19.08.2013 14:16:56 UPS: Passed a self-test. 0x0105
19.08.2013 14:16:46 UPS: Started a self-test. 0x0137
19.08.2013 14:16:36 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
19.08.2013 14:11:50 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
19.08.2013 14:08:35 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
16.08.2013 17:57:25 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
16.08.2013 17:46:38 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
16.08.2013 17:27:19 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
16.08.2013 17:24:09 System: Configuration change. Email recipient 'to' address 1. 0x0033
16.08.2013 17:20:22 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
16.08.2013 17:17:26 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
16.08.2013 17:14:14 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
16.08.2013 16:49:08 System: Web user 'apc' logged out from 192.168.121.10. 0x001F
16.08.2013 16:42:34 System: Configuration change. Email recipient 4 generation. 0x0033
16.08.2013 16:42:34 System: Configuration change. Email recipient 'to' address 4. 0x0033
16.08.2013 16:42:34 System: Configuration change. Email recipient 'to' address 4. 0x0033
16.08.2013 16:42:21 System: Configuration change. Email recipient 3 generation. 0x0033
16.08.2013 16:42:16 System: Configuration change. Email recipient 2 generation. 0x0033
16.08.2013 16:41:26 System: Web user 'apc' logged in from 192.168.121.10. 0x0015
16.08.2013 15:23:13 UPS: Restored the local network management interface-to-UPS communication. 0x0101
16.08.2013 15:23:03 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
16.08.2013 15:22:58 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
16.08.2013 15:22:52 System: Warmstart. 0x0002
15.08.2013 13:52:53 UPS: Restored the local network management interface-to-UPS communication. 0x0101
15.08.2013 13:50:48 UPS: The local network management interface-to-UPS communication not established. 0x0102
15.08.2013 13:49:57 System: Network service started. IPv6 address FE80::2C0:B7FF:FEC8:5B92 assigned by link-local autoconfiguration. 0x0007
15.08.2013 13:49:53 System: Network service started. System IP is 192.168.120.41 from manually configured settings. 0x0007
15.08.2013 13:49:37 System: Coldstart. 0x0001

[BillP]

Yes, to begin, serial and network communications on this UPS are not supported at the same time and very well could cause this problem. The Network Management Card are on the same communication bus and using both can disrupt communications on the other method. Can I ask why you are using both? The Network Management Card should provide everything you need.

I think you have multiple issues.

• Warmstarts - review this article -> http://www.apc.com/support/index?page=content&country=US〈=en&id=FA156063 (I have a feeling your NMC is rebooting due to lack of network traffic or too much and then its disrupting network communication to and from the card - unrelated to using serial at the same time though)
  • Anytime the NMC reboots or "warmstarts" though, the NMC needs to re-establish communication with the UPS. If serial communication is happening at the same time, this may prevent the NMC from talking to the UPS properly and thus gives you: UPS: The local network management interface-to-UPS communication not established

• v5.1.3 firmware - I recommend updating this firmware to at least v5.1.7 (which I can provide to you) or v6.0.6 which is a new major release with a different user interface, multiple user login, etc

[Anonymous user]

I use the both, because by network  communications I send e-mail for me when I have some problems.

I use serial too, because with it I use the PowerChute, If I have some problem, he sends a command for my server shutdown.

I tried to use the PowerChute with network communications, but I dind't do.

(Sorry about the English, because I'm Brazillian)

[BillP · Accepted solution]

No problem

But yes, what you're doing is not supported and I'd have to suggest you don't do it. You should be using the Network Management Card with PowerChute Network Shutdown OR PowerChute Business Edition via serial communications. This type of communication problem is most likely a conflict that will come and go if you continue to do it this way.

[Anonymous user]

OK.

But What PowerChute Version Should I use?

[BillP]

You'd want PowerChute Network Shutdown and it talks to the Network Management Card over the network.

[Anonymous user]

That's ok.

I disabled the serial port now, just for test and the message stopped to show. The Network Management Card become to work normally. So You are correct... Thanks so much for attention andknowledge.

[BillP]

You're very welcome