Management Processor Association Problem

[Dave Ostock]

I'm having problems with HPSIM 4.2 losing management processor associations.

I can fix it by manually running "Options-Discovery-Identify Systems" against both "all management processors" and "all servers" lists.

As the day wears on though, the associations start disappearing and by the next day probably less than half are associated.

The interesting thing is the "daily device identification" task doesn't seem to fix the problem. I have to run it manually to fix the associations.

I've read postings about similar problems, but haven't seen any lasting solution. Anyone have any ideas?

Thanks,

Dave

[Ole Thomsen_1]

The SP1 patch mentioned here <> solved the problem for me.

In my case it apparantly had something to do with the blade/enclosure/rack association issue adressed with the patch, only a few hours after patching and deleting the offending enclosures all associations including iLOs were back up.

[Dave Ostock]

I was unable to open the link. I checked the HPSIM download page and didn't see any service packs for HPSIM 4.2. Is the service pack you're referring to for HPSIM 4.1?

Thanks,

Dave

[Darren Z]

Here are the links (found these in another forum post):

Windows Readme

ftp://FTP.compaq.com/PUB/softpaq/sp29001-29500/SP29026.txt

Windows Patch

ftp://ftp.compaq.com/PUB/softpaq/sp29001-29500/SP29026.exe

[Darren Z]

Ohh... and here a a link to the forum thread. There was an '>' character at the end of the above link.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=822681

[Dave Ostock]

Thanks guys. I'll try this out andlet everyone know how it goes.

Dave

[Dave Ostock]

Well I applied the patch and it didn't help. Thanks anyway.

The problem is pretty interesting. We're using a hosts file for discovery and everytime discovery runs we lose most of hte associations. Running the daily device identification task doesn't fix anything. Running discovery identify systems against both server and mgmt processors does fix it though.

I'm going to try removing already discovered servers from the hosts file before running doiscovery and see if that helps

Dave

[Dave Ostock]

We did some more testing and found a solution to this problem.

We use a hosts file for discovery that always had the complete nodelist we wanted SIM to manage. We found when discovery reran against devices already in SIM the associations would disappear. Also, the daily device identification task wouldn't fix the associations.

To correct this problem we did the following:
1. Only include new devices that haven't been added to SIM in the hosts discovery file.
2. Replace default daily device identification task with 2 new ones. The first one is limited to management processors and the second is limited to servers.

With these changes in place it runs like a champ and all the associations are in good shape.

I hope this helps someone else.

Dave