HP SIM cluster installation

[Mikael Rönnbäck]

Hello, I'm looking for some help in finding a registry key. I have lost the old version of the installation whitepaper for setting up HP SIM 4.2 on MSCS clusters, and the new version does not list this item.

Anyway, there is (was?) supposed to be two registry keys replicated when using SIM in a cluster environment, one was the reg-key for the ProLiant Essentials Licensing, but which was the other one, I'm unable to find it in my documentation.

And also, is there anyone else who have installed SIM on a cluster, I'm having an issue with the version control, the VCRM works fine, but the VCAgents are unable to connect to the cluster name, they will only accept one of the node names (either one will do, just not the cluster name, which is kind of annoying since the point of clustering is hiding the actual nodenames behind the virtual name :-) )

[Bernardo Tagariello · Accepted solution]

http://h10018.www1.hp.com/wwsolutions/misc/hpsim-helpfiles/simdply.pdf

page 31

[Brent Seizer]

I have about 10 clusters in my environment.
Each is (2) DL380's and a MSA1000. I have never done anything like you were describing with the registry keys, to get my clustered nodes monitored.

It was my understanding that the purpose of SIM was to monitor the hardware. Since the cluster node is a logical node then your not getting a true report on the hardware.

Anyway, I have SIM installed on each node. Once installed and rediscovered, the software knows that the node is a member of a cluster, and the cluster name is also on the discovery list right above the 2 node names. Clicking on the cluster name, you will some limited amounts of information.

Make sure your using the latest version of SIM CMS, and the new repository manager that works with the new VC agent.
One the managed node I only install CP005171.exe, CP005194.exe, and CP005177.exe. Once these are configured and communicating with the CMS then I run the 7.3 PSP from within the VC agent.
It takes about 3 reboots to do it this way, but at least you can do this during production hours while the other node is running the cluster. Move the cluster to the other node after hours and do the next node the next day.

Once you get one cluster node done then replicate the settings to the others. This was a great help to me.

I hope this helps.

[Mikael Rönnbäck]

Bernardo: Perfect, thanks a lot, exactly what I was looking for, strange that my version of the PDF didn't have that but I should of course have tried downloading a newer version.

Brent, you misunderstand my question, I do not want to MONITOR a cluster, I am running SIM on a clustered solution, and I've had to reconfigure the setting due to problems with one of the cluster nodes.