HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Unable to modify the CMS built in system group.
Server Management - Systems Insight Manager
1833776
Members
2056
Online
110063
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2007 10:26 PM
03-29-2007 10:26 PM
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP