Adding Managed Nodes

This procedure walks you through adding managed nodes to a new management domain. Managed node systems must be running a supported version of HP-UX or Linux. Adding a managed node involves:

setting the agent configuration password
verifying the default WBEM and SNMP usernames and passwords
verifying the default authorizations
installing the DTF agent and WBEM software
configuring the managed node
adding the new node to the management domain
adding the new node to the Managed Nodes node group
testing the new node

To add a managed node, you can either:

automatically add a group of managed nodes using the add_nodes script
manually add managed nodes

The add_nodes script walks you through adding managed nodes. Using this script will significantly reduce the time and complexity of adding managed nodes.




	NOTE: The SCM software must be installed on the central management server (CMS) prior to adding a managed node, and the CMS must be available on the network. See “Installing Servicecontrol Manager on HP-UX” or “Installing Servicecontrol Manager on Linux” for details.The CMS and managed nodes must be time-synchronized to prevent authentication failures. The communication time limit is 20 minutes, and exceeding this limit causes authentication failures. This procedure assumes that SNMP is configured on each managed node. If you want to use SNMP tools with SCM, SNMP should be configured prior to adding managed nodes. By default, SNMP is configured on HP-UX systems.

Procedure 2-7 To automatically add managed nodes:

Log on to the CMS as root.
Run the add_nodes script.
/opt/mx/lbin/add_nodes node1 node2 node3...
where node1 node2 node3... is the list of hostnames or IP addresses for the nodes you want to add.
Verify the new nodes by testing the configuration:
/opt/mx/bin/mxexec -t df -n node1 node2 node3...
where node1 node2 node3... is the list of hostnames or IP addresses for the nodes you added.

Procedure 2-8 To manually add managed nodes:

Log on to the CMS as root.
Verify the location of the SCM agent software.
You located and/or downloaded this software at the same time that you located the CMS software during the CMS install process.
View the agent configuration password (MxConfigPassword):
mxpassword -l
Remember this password because it is used to validate communication between the CMS and managed node during the adding managed nodes procedure. Change the password to something easier to remember if desired:
mxpassword -m -x MxConfigPassword=new_password
where new_password is the new password.
By default, SCM expects a WBEM username of guest and a password of guest. The expected username and password information is accessible on the CMS using the mxnodesecurity command.
An account with the expected WBEM username and password must exist on each managed node. Change the default username and password if desired:
/opt/mx/bin/mxnodesecurity -a -p wbem -c username:password
where username is the new username and password is the new password.
By default, SCM expects an SNMP username of public and a password of public. The expected username and password information is accessible on the CMS using the mxnodesecurity command.
An account with the expected username and password must exist on each managed node. Change the default username and password if desired:
/opt/mx/bin/mxnodesecurity -a -p snmp -c username:password
where username is the new username and password is the new password.
By default, all new nodes are added to the Managed Nodes node group. Verify that this node group exists:
mxngroup
If the Managed Nodes node group isn’t listed, you need to create the node group:
mxngroup -a -g “Managed Nodes”
By default, all new nodes inherit the Managed Node node group authorizations. Identify the authorizations for this node group:
mxauth -lt
By default, root should be authorized with the Master Role for this node group. To authorize root with the Master Role for the Managed Nodes node group:
mxauth -a -g ”Managed Nodes” -R “Master Role” -u root
Log on to one of the managed nodes as root.
NOTE: Step 8 to step 11 will need to be completed on each managed node separately.
Install the SCM DTF agent and WBEM software on the managed node:
- For HP-UX (all versions):
  swinstall -s server:directory B8339BA.SysMgmtAgent B8465BA
  where server is the hostname of the depot server and directory is the location of the depot files on the depot server.
  NOTE: You must have appropriate permissions to execute the following bin files. Use the chmod +x command to change the file permissions.
- For Red Hat Linux 7.2 or 7.3:
  SCM.3.0_RH.7.2_7.3_mxagent.bin
- For SuSE Linux 8.0:
  SCM.3.0_SuSE.8.0_mxagent.bin
Configure the managed node:
/opt/mx/bin/mxagentconfig -a -n cms -p password
where cms is the hostname of the CMS and password is the MxConfigPassword that you verified earlier.
Configure WBEM and start the cimserver on the managed node:
/opt/wbem/sbin/cimconfig -s enableRemotePrivilegedUserAccess=true -p
/opt/wbem/sbin/cimserver
Repeat step 8 to step 11 for the remaining managed nodes.
Return to the CMS, and log on as root.
Add the new nodes to the management domain:
/opt/mx/bin/mxnode -a -i node1 node2 node3...
where node1 node2 node3... is the list of hostnames or IP addresses for the nodes you added.
Add the new nodes to the Managed Nodes node group:
/opt/mx/bin/mxngroup -m -g "Managed Nodes" -n node1 node2 node3...
where node1 node2 node3... is the list of hostnames or IP addresses for the nodes you added.
Verify the new nodes by testing the configuration:
/opt/mx/bin/mxexec -t df -n node1 node2 node3...
where node1 node2 node3... is the list of hostnames or IP addresses for the nodes you added.

Adding Managed Nodes

Technical documentation

» Table of Contents

» Glossary

» Index