NMC restart loses SNMP connection

[Anonymous user]

I've got an application that monitors UPS events through the SNMP v3 agent. It works great except whenever the Network Management Card does a 'warmrestart'. When this occurs my application reports everything down, which is correct, however when the NMC has completed its startup, my application never reports everything is back online. This only occurs with the NMC warmrestart. If I reboot the UPS my application reports down and then up when the UPS is back online. After the warmrestart, the only way my application can connect to the UPS again is if I restart the application.

Is there anywhere the UPS would store information/data about the SNMP agent? I know SNMP has built in security to compare timestamps, addresses, etc...so as to verify the integrity of the requester. Perhaps after this warmrestart the SNMP agent on the UPS cannot verify the requester credentials anymore.

Any ideas would certainly help. I'm completely stumped why this is occurring. Thanks.

[BillP]

Hi Guy,

What model Network Management Card (NMC) are you using, what FW APP and AOS are on the card and what SNMP v3 agent are you running?

Thank you.

[Anonymous user]

The NMC is a AP9617, not sure about the AOS and FW. It's never been updated since it came out of the box. Not sure how to answer the SNMP v3 question. I have SNMP v3 access turned on, on the UPS and my application is using net-snmp v3 version 5.3.1

Hope that helps.

[Anonymous user]

Application Module
sumx
Version: v3.5.5
Date: 05/24/2007
Time: 16:14:52



APC OS (AOS)

Name: aos
Version: v3.5.5
Date: 05/24/2007
Time: 15:44:22

Hope that helps.

[BillP]

if you login via telnet/local serial access, the AOS and APP versions will be listed on the top right of the initial menu presented to you.

alternatively, you can locate it in the web interface under Administration->General->About. If its an older version, it will be located under Help->About System on the left hand side.

Lastly, you can also retrieve the .iso.org.dod.internet.mgmt.mib-2.system.sysDescr / .1.3.6.1.2.1.1.1 OID via SNMP for us which should give us something similar to:

APC Web/SNMP Management Card (MB:v3.9.2 PF:v3.7.0 PN:apc_hw02_aos_370.bin AF1:v3.7.0 AN1:apc_hw02_rpdu_370.bin MN:AP7941 HR:B2 SN: ZA0123456780 MD:10/07/2006)

you can remove the serial number at the end if the output if you do that method.

[BillP]

ok, you are one version behind. before we guess and play around, i would try and flash the firmware to the latest which is AOS 3.6.1 and SUMX 3.5.8. it is available from http://www.apc.com/tools/download/index.cfm by choosing Firmware Upgrades - Network Management Card and choosing SFSUMX358.

[voidstar_apc · Accepted solution]

If you continue to have this issue with the latest firmware, I suggest running Wireshark to capture the SNMPv3 traffic. If this is a timeliness issue, you should see a response that indicates "not in time window" or something like that. Or maybe the problem is something else and we can examine the traffic for other issues.

Should timeliness be the cause, I would look at the "Engine Boots" and "Engine Time" within the SNMPv3 packets. We should see the "Engine Boots" value from the network management card increase after a reboot or a warmstart.

!http://apc-forums.com/servlet/JiveServlet/download/25-3822-16534-994/timeliness.png!

Let us know how it goes.