Server Management - Systems Insight Manager
1752591 Members
3399 Online
108788 Solutions
New Discussion юеВ

Re: Manual association

 
SOLVED
Go to solution

Re: Manual association

Hi Shocko,

 

Yes, iLo and OA are in the same subnet.

 

to sumarize:

 

iLo3 are running FW version 1.50 or 1.55

iLo4 are running FW version 1.20 or 1.22

OA are running FW version 3.70 or 3.71

 

Association iLo3/4 <--> server is just working fine

Association Servers (via iLo3/4) <--> enclosure is NOT working

Association OA <--> enclosure is NOT working

 

Many thanks

 

Patrick

shocko
Honored Contributor

Re: Manual association

My iLO XML reply looks different on iLo 3 but my OA is 3.32 (see attached). Did you use the https://iloip/xmldata?item=All format to get the XML reply?

 

If my post was helpful please award me Kudos! or Points :)

Re: Manual association

Hi Shocko,

 

Yes, I got the XML file from https://iloip/xmldata?item=All. It looks quite similar to your file, except for the spaces after the serial number (probably added by my text editor).

 

I did some more investigation in the database itself, but still haven't found what could cause this problem.

 

Many thanks for your help

 

Partrick

shocko
Honored Contributor

Re: Manual association

I wish I had some more time and I would troubleshoot this against my own installation but, als, I don't. Could anyone from HP comment on how these associations are formed? I presume it's a stored proceededure in the DB that runs and creates them based on the UUIDs?

If my post was helpful please award me Kudos! or Points :)
shocko
Honored Contributor

Re: Manual association

See here: http://h18013.www1.hp.com/products/servers/management/hpsim/techsupport.html

Is forward reverse DNS in place for all OA/VC/iLO/Server?

If my post was helpful please award me Kudos! or Points :)
Solution

Re: Manual association

Hi,

 

I tried the Hotfix for SIM 7.2 which was just released, but did not help in my case.

 

Finally, I did something i don't like to do, but we simply could not wait longer without a reliable monitoring in place:

 

 

1) mxnode -r <EnclosureName> -x force (to remove the enclosure without having to remove all blades and switches in it)

 

2) start a Discovery  of the OA

 

The enclusure was rediscovered and all association were successfully re-done.

 

Hope this can help someone else

 

Regards

 

and thank you Shocko for your help

 

Patrick