Run updatenode to install CSM, perform Software Maintenance, and distribute CFM files.

Options:
Install CSM Install or update the CSM software on the nodes.
Node root password (1st time only): If this is the 1st time you are running updatenode to this node, and remote shell security is not yet set up to this node, the updatenode command will need the root password of the node to set up the remote shell security.  This option is not implemented yet.  You will have to run updatenode from the command line the first time to a node.
Perform Software Maintenance Install RPMs on the nodes that are in the updates directory on the management server.  The updates should be stored in /csminstall/Linux/<distro>/<version>/i386/updates .
Options to pass to SMS: Forwards options to the smsupdatenode command. The following are the allowed flags: "[--noinsdeps] [-i | --install packagename(s)] [-e | --erase [[--deps] | [--nodeps]] packagename(s)] [-p | --packages packagename(s)]", where packagename(s) denotes a commas separated list.  For allowable options, see the smsupdatenode man page.
Distribute CFM files Update the configuration files on the nodes from /cfmroot on the management server.  You can also edit these files.
Options to pass to CFM: Forwards options to the cfmupdatenode command.  For allowable options, see the cfmupdatenode man page.
Verbose Run updatenode in verbose mode.
Test Only report what would be done by the command. Do not perform any updates.
Exchange Keys Exchange RSCT public keys between the node and management server. Only use this option if the RSCT public key, host name, or IP address of either of the machines has changed. When this option is used you must trust your network at the time to be sure that a rogue machine is not going to insert their public key in place of the real node.
Force Force the updates of CSM RPMs and Software Maintenance RPMs. Perform a binary check on configuration files .

Tips