Server Management - Systems Insight Manager
1833758 Members
2065 Online
110063 Solutions
New Discussion

Unable to modify the CMS built in system group.

 
Stuart M. Garland
Occasional Advisor

Unable to modify the CMS built in system group.

When installing SIM onto a Microsoft Cluster (following all appropriate HP documentation !) the CMS group is populated with the node name of the primary node, instead of the cluster name.
This means that, should the cluster ever fail over to the seconadary node, you loose things like "Software Status".
For example, you have a two node HA cluster called cluster1. The two nodes are server1 & server2. The primary install is performed on server1, and the secondary install is performed on server2. The CMS system group shows the ONLY member as being server1 instead of the cluster name 'cluster1'. When the cluster fails over because server1 has gone down, server2 is unable to perform certain functions and cannot report on any nodes 'software status' (as the VCA is configured to use the cluster name 'cluster1') because the CMS system group does not know about it.
I have tried to modify the CMS system group membership using the mxngroup command, but just get told that this is prohibited !!

Am I doing something completely stupid during the cluster install?
Can anyone from HP help please.