RIB LoE and ILO's not associated with server

[AndreAs_35]

we have problems with much of our RIB's and ILO's that they are listed in SIM 5 SP4, but no connection between MP and server is done. Means the server and the MP are listed as 2 separate devices and where we have normally the text "in Server xyz" we have nothing. Other servers and MP's work fine and are displayed correctly. If we connect within SIM to the System Management Homepage on the server, the MP is visible and has no errors.

How we can get the connection between server and MP so that SIM sees that a MP is inserted in the server ?

We already tried updates of the Remote Insight Board Driver and deleted not correctly displayed servers and their MP's but after adding them again (manually) the same behaviour. A hardware status polling and software status polling not helps too. We use PSP 7.30 and ROM version 2.53 for RIB's and 1.82 for ILO's on all systems. Any ideas ?

[jptr]

Sorry...this is not a solution to your problem, but an extension question.

Just wondering can they be tied manually if HPSIM does not associate them automatically?

[AndrewF]

If we could establish the connection between RIB/ILO and the server manually that would be already a big help for us. Even if it's more work. Until now we not have an idea how to establish the connection between these 2 devices which belongs together.

[jptr]

This is not a solution of your problem, but it might help.

Set the "Preferred Systen Name" of iLO to something like "iLO-". That way you can atleast recognize iLO and its corresponding node. Make sure you configure it to not to be written by discovery.

[Matthew J Warrick]

In the ilo config under SNMP settings you will need to set the data return field to "enabled" or "medium" depending on what ilo firware you are running so SIM can ID them properly.

Also make sure that the ilo agents are running. This is found in Control Panel on the active agents tab of the mgmt agents item.

You may have to delete and the servers/ilos and readd them but hopefully "Identify Systems" will fix it once the agents are config'd properly.