MIB Issue

[Anonymous user]

I have 2 APC UPS RT5000's being SNMP monitored with Nagios. Both worked flawlessly for months. One afternoon, one of the UPS's started having this type error on every one of it's 12 checks:

External command error: Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: iso.3.6.1.4.1.318.1.1.1.2.2.1.0

It used to work fine and there were no changes to the Nagios config. The other APC RT5000 continues to monitor flawlessly. Any suggestions on how I might be able to troubleshoot/resolve this problem?

[BillP]

can you tell me what AOS and application version is on your network management cards that you are polling? did you recently update the firmware or anything? if you connect to the network card via the web UI, is it operating normally and allowing you to see UPS values?

it might be helpful to provide us with the logs, instructions outlined here-> http://nam-en.apc.com/app/answers/detail/a_id/9321

[Anonymous user]

When I try to log in to the web ui, it tells me there is already somebody logged in and will not allow me to continue. However, nobody is logged in.

I tried shutting down the UPS to clear this problem, but when I restarted the UPS I still get the message. I get this message on both the UPS that is still monitoring and the UPS that is a problem.

Any ideas on how to clear the web login block problem?

[Anonymous user]

Resolved.

Both problems went away by rebooting the systems with a paperclip in the pinhole in the back of the unit near the network port.

I can now log into the server via the web and the nagios monitoring is back. The log indictaed communication lost when the problem started and after the reset communication established.

[BillP · Accepted solution]

yes, this issue is specific to the network management card and not the UPS. when you power down the UPS output, the management card probably stayed on if you did not completely braindead your UPS. in the future, you can also take advantage of the log in priorities and log in via telnet or SSH to kill the web session (if you're remote).