Problems with SIM 4 an ILO's

[Javier Navarro]

Hi, I'm having a problems in the associations of ILO's an servers. In the "All Systems" page don't appear to be associated (? sign on MP column) but if I enter in the server or MP page it shows corresponding ILO/server.

[Jon Ward]

First, ensure that the iLO itself is discovered as a "Management Processor" device on it's own line.

The server needs to have been discovered as a "Server" device, as opposed to "Unknown".

Then, ensure that the Remote Insight Agent is activated on the managed server. On Windows systems, this is done in the hp Management Agents Control Panel applet.

[David Claypool]

Jon's right--make sure that the iLO has been discovered itself (check the 'All Management Processors' list) and also that your ProLiant has been properly classed as server. However, while it is good to check to see if the 'Remote Insight' module is activated (other than checking the Control Panel applet you can see if the agent has a status box for it), that is not the way associations are done.

During initial or daily device identification, HP SIM asks each iLO some information about itself to which it responds with an XML document. You can view that information from an iLO by typing

http://[ILO-NAME-OR-IP-ADDRESS]/xmldata?item=all

to which you will get a response such as this:




6J2AJNT1B02G


1
Integrated Lights-Out (iLO)
ILO6J2AJNT1B02G



The level of detail that is returned can be set under Administration-->SNMP/Insight Manager Settings. The basic data used for the association is the server's serial number, tagged by above. On a discovered iLO, HP SIM searches the database for a server with the serial number it has received from iLO in order to make the association.

Anything that causes a bad serial number to appear (such as after a motherboard replacement) will interfere with identification.