Incorrect event in the log PCNS-client

[Anonymous user]

Some servers with PCNS-clients connected to the NMC AP9631. I found that the logs on PCNS-clients contain different events.

For example, log onto the same server contains events:

07/11/2013 08:58:11 Communication has been established 

07/11/2013 08:58:11 Network Management Card cannot communicate with the UPS

07/11/2013 08:20:56 Communication has been established 

07/11/2013 08:20:56 Network Management Card cannot communicate with the UPS

On another server, such events are registered at another time:

07/11/2013 08:52:20 Communication has been established 

07/11/2013 08:52:20 Network Management Card cannot communicate with the UPS

07/11/2013 06:49:25 Communication has been established 

07/11/2013 06:49:25 Network Management Card cannot communicate with the UPS

On some servers, such events are not registered at all.

Event log of NMC AP9631 does not contain these events, despite the fact that the settings specified that they should be registered.

Why are different logs at all PCNS-clients?

And why are different events in the logs PCNS-clients and NMC AP9631?

[BillP]

I suggest running a packet sniffer on the servers to capture UDP traffic that is being sent from the NMC IP address to port 3052. You will then be able to match the UDP traffic with what the PCNS log is recording.

In the example below I set the filter to the IP address of my NMC. If your server is on a different network segment then the NMC and the server IP is not registered with the NMC you should not filter by IP. If that is the case then filter by UDP alone.

[voidstar_apc · Accepted solution]

Given how brief those are (communication established less than a second after communication lost), there may not be any communication issue on the NMC. To avoid nuisance alerts, it normally takes 20 seconds before the NMC decides communication has failed, however PCNS seems to be reporting anomalies immediately.