snmove - Change xCAT compute nodes to use a different xCAT service node.
snmove [-h|--help]
snmove noderange [-V] [-l|--liteonly] [[-d|--dest] sn2 ] [[-D|--destn] sn2n] [-i|--ignorenodes] [[-P|--postscripts] script1,script2...|all ]
snmove [-V] [-l|--liteonly] -s|--source sn1 [[-S|--sourcen] sn1n] [[-d|--dest] sn2] [[-D|--destn] sn2n] [-i|--ignorenodes] [-P|--postscripts script1,script2...|all]
The snmove command moves a node or nodes from one service node to another.
The use of backup service nodes in an xCAT hierarchical cluster can help improve the overall reliability, availability, and serviceability of the cluster.
Before you run the snmove command it is assumed that the backup service node has been configured properly to manage the new node or nodes. (See the xCAT document named ``Using xCAT Service Nodes with AIX'' for information on how to set up backup AIX service nodes.).
The snmove command can use the information stored in the xCAT database or information passed in on the command line to determine the current service node and the backup service node.
To specify the primary and backup service nodes you can set the ``servicenode'' attribute of the node definitions.
The servicenode attribute is the hostname of the xCAT service node as it is known by the management node. The xcatmaster attribute is the hostname of the xCAT service node as known by the node. The servicenode attribute should be set to a comma-separated list so that the primary service node is first and the backup service node is second. The xcatmaster attribute must be set to the hostname of the primary service node as it is known by the node.
When the snmove command is run it modifies the xCAT database to switch the the primary server to the backup server.
It will also check the other services that are being used for the node (tftpserver, monserver, nfsserver, conserver), and if they were set to the original service node they will be changed to point to the backup service node.
In some cases, if you are using the xCAT AIX statelite support, the snmove command will synchronize the persistent statelite directories from the nodes primary service node to it's backup service node. This will only be done if the server specified in the statelite table is the primary service node. You can also use the snmove command to do only the synchronization by using the -l option. This support applies to AIX systems only.
If the -i option is specified, the nodes themselves will not be modified.
If the -i option is NOT specified then the nodes will be modified as follows:
The syslog postscript will be run.
The setupntp script will be run IF it was included in the nodes postscript list.
The mkresolvconf script will be run IF it was included in the nodes postscript list.
The default gateway will be switched to the backup service node if networks.gateway=<xcatmaster>.
If it is an AIX diskful node then the niminit command will be run so that it will recognize the new service node as it's NIM master.
Note: You can also run other postscripts useing -P option if needed.
When the snmove command is executed the new service node must be running but the original service node may be down.
Note: On a Linux cluster, for NFS statelite nodes that do not use external NFS server, if the original service node is down, the nodes it manages will be down too. You must run nodeset command and then reboot the nodes after running snmove. For stateless nodes and RAMDisk statelite nodes, the nodes will be up even if the original service node is down. However, make sure to run nodeset command if you decide to reboot the nodes later.
Specifies the hostname of the current (source) service node sa known by (facing) the management node.
Specifies the hostname of the current service node adapter as known by (facing) the nodes.
Specifies the hostname of the new destination service node as known by (facing) the management node.
Specifies the hostname of the destination service node as known by (facing) the nodes.
No modifications will be made on the nodes. If not specified, several xCAT postscripts will be run on the nodes to complete the switch to the new service node.
Used to synchronize the xCAT AIX statelite persistent files to the backup service node. This option will only attempt to synchronize statelite files that are served by the primary service node for the compute node. When you use this option the snmove command will not actually move the nodes to the backup service node.
Specifies a list of extra postscripts to be run on the nodes after the nodes are moved over to the new service node. If 'all' is specified, all the postscripts defined in the postscripts table will be run for the nodes. The specified postscripts must be stored under /install/postscripts directory.
Display usage message.
Command Version.
Move the nodes contained in group ``group1'' to the service node named ``xcatsn02''.
snmove group1 -d xcatsn02 -D xcatsn02-eth1
Move all the nodes that use service node xcatsn01 to service node xcatsn02.
snmove -s xcatsn01 -S xcatsn01-eth1 -d xcatsn02 -D xcatsn02-eth1
Move any nodes that have sn1 as their primary server to the backup service node set in the xCAT node definition.
snmove -s sn1
Move all the nodes in the xCAT group named ``nodegroup1'' to their backup SNs.
snmove nodegroup1
Move all the nodes in xCAT group ``sngroup1'' to the SN named ``xcatsn2''.
snmove sngroup1 -d xcatsn2
Move all the nodes in xCAT group ``sngroup1'' to the SN named ``xcatsn2'' and run extra postscripts.
snmove sngroup1 -d xcatsn2 -P test1
Move all the nodes in xCAT group ``sngroup1'' to the SN named ``xcatsn2'' and do not run anything on the nodes.
snmove sngroup1 -d xcatsn2 -i
Synchronize any AIX statelite files from the primary server for compute03 to the backup server. Do not move the node to the backup server at this time.
snmove compute03 -V -l
/opt/xcat/sbin/snmove