Management Processor to Server Association

[Eric Summers_1]

After applying sp3 to our SIM 5 server, most (but not all) servers no longer have a green circle for the MP column. Most are displaying as no management processor detected. If I look at the management processors, it tells me what server it is installed in. If I open up the Server Management agent, it shows me the status of the management processor (all green). I haven't been able to find anything different between the servers that are displaying mgmt proc. status correctly and those that are not. All mgmt procs were displayed correctly pre-sp3 and nothing else has changed. Is there a script to force a 're-association'? The Identify Systems task doesn't help. I have tried deleting and re-adding a few servers and mgmt procs, and that didn't work either. Any ideas?

[Rob Buxton]

I'm seeing the same, except it seems to be all Servers here.

There are still some associations still listed, but the MP Column for all Servrs with ILO/RILO's are "i"'s.
My guess is that where there are still some associations that will drop.

Go to the Server Management Home Page and the MP is listed fine.
We've also updated the SMH to 7.41 on all of our Servers.

[Ole Thomsen_1]

Same problem.

Some servers has kept the MP association, but most is lost.

Also tried identify and delete/add with no luck.

Ole Thomsen

[Darren Z]

Same here. SP3 has gone ahead and disassociated the management processors from their servers.

I'm assuming there is no fix?

[Hense, Klaus]

Hallo,
make a test: delete the MP from one server in the HPSIM and start a discoverery.
after this check the server and MP status.

[Wijnand Lammens]

I have the same, but the association has always been a pain...
I hacked the "dbo_device_associations" table to associate each MP to it's server. This worked well, but now with SP3 a discovery removes my manually created entries again, except for the ones of the G4 Proliants???!
I installed a fresh SIM5-with-SP3, but this one does not associate any of the MPs with it's server.

[Rob Buxton]

Hense,
Tried that and no change. The fact that the MP Icon on the Server is "i" suggests that HPSIM is not picking up the Remote Insight Agent details rather than any issue with the MP itself.

Anyone out there still using 7.40 of the HP Management Agents. Just trying to see if this is an issue with HP SP3, or 7.41 of the Management Agents.
We rolled out both quite close together and it was only seeing this thread that got me checking.

[Eric Summers_1]

We had 7.41 deployed on many servers before sp3 and we never lost the MP association. I haven't tried to open up a case with HP yet, but I guess that will be the next step.

[Rob Buxton]

The agent restart / rediscovery only seemed to work on the new (G4) Servers.
It failed on all of the G3's and G2's.

[Ken Horn]

Rob...we're still using 7.40 for the agents and system home pages and getting the same problem since upgrading to SP3. Problem definitely appears to be with SP3.

[Ken Horn]

Interesting to note that if I look at 'All Management Processors' the iLO/RILOs themselves still show what what server they are in, even though their server itself shows the 'i' in the MP column.

[Wijnand Lammens]

It looks like only half of the association works: during discovery and/or device identification of the iLO the correct servername is recorded. It is written this way in the association table in the SIM database.
Obviously during the discovery of the server the agent does not correctly record the iLO, there is no reference from server to iLO in the association table. That is, with a freshly installed SIM5SP3. In the SIM5 I upgraded to SP3 the existing associations for G4 servers remain.

[Andreas Peetz]

I'm seeing the same here. This is definitely a bug in SP3. After reverting to the state before SP3 (I did the uprade on an undoable VM) the problem was gone again.

[JP_26]

Is any of you seeing this with iLO firmware versino 1.82? If you are seeing this with an older version of iLO, could you please update the firmware to 1.82 and try if this goes away?

Thanks
JP

[Wijnand Lammens]

I have 1.82 on all iLOs.

[Ole Thomsen_1]

Metoo :-)

Ole Thomsen

[John Stalzer]

I've been having the same problem since my upgrade to SP3. Ove the 12 servers I'm monitoring, I'm just able to view the styatus on 5 of the servers.
I've been working with HOP for the last two weeks and am still waiting for tehm to work out the problem. My servers are BL25P.

[CSiem]

If anyone actually opens a support case, please forward the case number along.

[John Stalzer]

My case # is 3213559983

[John Stalzer]

I just received an email rom HP. "There is currently a problem with associations that development is working on, a hot fix is in the works, but has not been fully qualified yet."
I'll post the fix as soon as I here anything from HP.

[Scott_278]

I just got the same information from my SE. there is a hotfix on the way, but hasn't been through QA yet.

[Scott Shaffer]

Official response is: we have identified the problem and are working on a fix. We should have an update avaialable soon to address the problem - look for it early next week (assuming we don't run into any other issues.) If we can get it our sooner we will.

[Rob Buxton]

Scott,
Sounds good. Interestingly all of my ILO/RILOE II associations are back, just the MP icon for the Servers is still just i's.

[Ken Horn]

SP4 is out today. States it addresses the MP problem.

http://h18013.www1.hp.com/products/servers/management/hpsim/dl_windows.html

[Scott_278]

I upgraded so SP4 (not without issues, see "SP4 Upgrade - Gocha" thread). After running an identification, it seems to resolve the MP assciation problem.