Management domain configuration
When an operating system image is started on a POWER4, POWER5, POWER6®, or POWER7® system, the resource monitoring and control (RMC) subsystem is started and then, the IBM®.CSMAgentRM or IBM.MgmtDomainRM resource manager is started. These resource managers implement the necessary functions to automatically add the operating system image, as a managed node, to the management domains created automatically on each Hardware Management Console (HMC). The IBM.MgmtDomainRM resource manager is started on AIX® 7.1, and later. It is also started on AIX 6.1 if csm.client 1.7.1.4 (PTF U834202), or later, is installed. Otherwise, the IBM.CSMAgentRM resource manager is started on AIX 6.1. On Linux® logical partitions (LPAR) on Power Systems servers, if CSM 1.7.1.6, or later (or no CSM is installed), and RSCT 3.1.0.0, or later, are installed, the IBM.MgmtDomainRM resource manager is started. Otherwise, for previous versions of CSM or RSCT, the IBM.CSMAgentRM resource manager is started.
When the logical partition (LPAR) is managed by the IBM.MgmtDomainRM resource manager, resources of the IBM.ManagementServer class are replaced by resources of the IBM.MCP class.
The following persistent attributes of the IBM.ManagementServer class are supported by the IBM.MCP resources:
| Persistent attribute | Description |
|---|---|
| MNName | The primary host name of the managed node as known to the management control point (MCP) (string). |
| NodeID | The RSCT node ID of the MCP (uint64). |
| KeyToken | The host identity that is used to look up the public key of the MCP in the trusted host list (THL) on the managed node (string). |
| IPAddresses | The list of IP addresses that are assigned to the MCP and reachable from the managed node. Each address must be on a separate subnet (string array). |
| ConnectivityNames | The list of IP addresses that are assigned to the node and reachable from the MCP (string array). One of these addresses is also the value of the MNName attribute. |
| HMCName | The value of the HscName field
that is found in the runtime abstraction services (RTAS) (string). |
| HMCIPAddr | The value of the HscIPAddr field
that is found in the RTAS (string). |
| HMCAddIPs | The value of the HscAddIPs field
that is found in the RTAS (string). |
| HMCAddIPv6s | The value of the HMCAddIPv6s field
that is found in the RTAS (string). |
- Name
- Hostname
- ManagerType
- LocalHostname
- MgmtSvrNodeID
- MgmtSvrPrimaryNames
- ClusterTM
- ClusterSNum
- HAState
- MgmtSvrHostNamesList
- LocalHostNamesList
If the Integrated Virtualization Manager (IVM) is managed by the IBM.MgmtDomainRM resource manager, the resources of the IBM.ManagedNode class are replaced with the IBM.MngNode resources.
The following persistent attributes of the IBM.ManagedNode class are supported by the IBM.MngNode resources.
| Persistent attribute | Description |
|---|---|
| Name | The primary host name of the managed node (string). |
| NodeID | The RSCT node ID of the node (uint64). |
| KeyToken | The host identity that is used to look up the public key of the managed node in the THL on the MCP (string). |
| Aliases | The additional names for the node; might be NULL (string array). |
| IPAddresses | The list of IP addresses that are assigned to the managed node and reachable from the MCP. Each address must be on a separate subnet (string array). |
- Hostname
- UniversalId
- ConnectivityIPAddrs
- A session to each configured IP address of each HMC to validate the IP address. No commands are sent if IBM.CSMAgentRM is used. Otherwise, IBM.MgmtDomainRM sends few commands.
- A session to each HMC. A command is sent to determine the code level on the HMC of the IBM.DMSRM resource manager.
- A session to each HMC. A command is sent containing necessary information, including the node's public key. The response contains necessary information, including the HMC's public key.
As a result of these sessions, barring any errors, the operating system image becomes a managed node, and the RMC daemon begins communication with the RMC daemon on each HMC. Periodically, if the IBM.CSMAgentRM resource manager is started, it examines the state of the operating system image and, if appropriate, initiates another series of sessions and commands to the RMC daemon on each HMC to adjust the managed node configuration within the management domains. If the IBM.MgmtDomainRM resource manager is started, it checks whether the IBM.CSMAgentRM resource manager performed any necessary configuration operations. If so, the IBM.MgmtDomainRM resource manager terminates itself (assuming it is not processing any other RMC commands). Then, periodically, the RMC daemon examines the state of the operating system image and, if it changes, restarts IBM.MgmtDomainRM to perform any necessary configuration.
- A session to the management server. A command is sent to determine the code level on the management server of the IBM.DMSRM resource manager.
- A session to the management server. A command is sent containing necessary information, including the node's public key. The response contains necessary information, including the HMC's public key.
As a result of these sessions, barring any errors, the node becomes a managed node. After it becomes a managed node, the RMC daemon begins communication with the RMC daemon on the management server.
If xCAT optionally configures a management domain, the moncfg rmcmon command creates an IBM.MngNode resource on the management server (MCP) for each xCAT managed node. Then it creates an IBM.MCP resource on each managed node. The last step in creating an IBM.MCP resource is to run the Public Key Exchange protocol between the IBM.MgmtDomainRM resource manager on the MCP and the IBM.MgmtDomainRM resource manager on the managed node. As a result of these actions, barring any errors, each node becomes a managed node. After it becomes a managed node, the RMC daemon begins communication with the RMC daemon on the management server.