Wednesday 7 April 2010

Unknown status for servers in ITAssistant

ITAssistant often seems to give unknown status to servers for no apparent reason.  The usual fix for this is just to refresh the inventory of the unknown servers (annoying but quite quick to do).

However sometimes servers go unknown and won't respond to an inventory, even if you bounce the ITAssistant services or the SNMP services on the remote server.

The first step is to try the troubleshooting tool in ITAssistant...

and run the SNMP connectivity test...


The result should show a list of SNMP agents installed on the server.  A healthy Dell Openmanage report will list the OpenManage Server Agent, plus any additional components that were selected (such as storage management.

If the OpenManage SNMP agent isn't showing you'll probably only see a couple of agents.

e.g.
1) A problem server
Connected to the agent software(s) - [broadcom, NA], [mib2, NA]
2) An OK server
Connected to the agent software(s) - [broadcom, NA], [cminventorysnmp, NA], [drac3, NA], [mib2, NA], [OpenManage Server Agent, 5.8.0], [storagemgmt, NA]

If the server responds with an output similar to the problem server (1) above, then you need to reinstall SNMP.  The good news is that this can be done without rebooting the server.

This usually requires the unzipped files for the installed service pack and the windows installation CD, so make sure you have the media available

1) Uninstall Dell OpenManage
2) Uninstall SNMP
3) Reinstall SNMP
4) Reinstall Dell OpenManage

Finally go back into ITAssistant and re-run the troubleshooting tool to make sure you get the full SNMP output for OpenManage and if this is ok, re-inventory the server in OpenManage and your unknown status should clear.

Of course if you take the opportunity to upgrade OpenManage you may find your firmware is out of date and you get a warning status, but that's a different subject...

Posted via email from Pio's work related musings

1 comment:

Unknown said...

FYI, un-installing and re-installing SNMP on a SQL (2000 or 2005 at least) server can cause the SQL process to restart, since it has to put it's hooks into SQL perf counters.

Just a warning in case you are doing this in the middle of the day to production hardware.