add -l option
git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/trunk@13089 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
parent
9e1ef03a1d
commit
88ac8cdc5c
@ -1,19 +1,18 @@
|
||||
=head1 NAME
|
||||
|
||||
B<snmove> - Change xCAT compute nodes to use a different xCAT service node.
|
||||
B<snmove> - Move xCAT compute nodes to a different xCAT service node.
|
||||
|
||||
=head1 SYNOPSIS
|
||||
|
||||
B<snmove> I<noderange> [B<-d>|B<--dest> I<sn2>] [B<-D>|B<--destn> I<sn2n>] [B<-i>|B<--ignorenodes>] [B<-P>|B<--postscripts> I<script1,script2...>|I<all>]
|
||||
B<snmove> I<noderange> [B<-V>] [B<-l>|B<--liteonly>] [B<-d>|B<--dest> I<sn2>] [B<-D>|B<--destn> I<sn2n>] [B<-i>|B<--ignorenodes>] [B<-P>|B<--postscripts> I<script1,script2...>|I<all>]
|
||||
|
||||
B<snmove> B<-s>|B<--source> I<sn1> [B<-S>|B<--sourcen> I<sn1n>] [B<-d>|B<--dest> I<sn2>] [B<-D>|B<--destn> I<sn2n>] [B<-i>|B<--ignorenodes>] [B<-P>|B<--postscripts> I<script1,script2...>|I<all>]
|
||||
B<snmove> [B<-V>] [B<-l>|B<--liteonly>] B<-s>|B<--source> I<sn1> [B<-S>|B<--sourcen> I<sn1n>] [B<-d>|B<--dest> I<sn2>] [B<-D>|B<--destn> I<sn2n>] [B<-i>|B<--ignorenodes>] [B<-P>|B<--postscripts> I<script1,script2...>|I<all>]
|
||||
|
||||
B<snmove> [B<-h>|B<--help>|B<-v>|B<--version>]
|
||||
|
||||
=head1 DESCRIPTION
|
||||
|
||||
The B<snmove> command moves a node or nodes from one service node to
|
||||
another.
|
||||
The B<snmove> command may be used to move a node or nodes from one service node to another backup service node.
|
||||
|
||||
The use of backup service nodes in an xCAT hierarchical cluster can
|
||||
help improve the overall reliability, availability, and serviceability
|
||||
@ -48,35 +47,15 @@ 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.
|
||||
|
||||
By default the command will modify the nodes so that they will be able to be managed by the backup service node.
|
||||
|
||||
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:
|
||||
You can also have postscripts executed on the nodes by using the -P option if needed.
|
||||
|
||||
=over 3
|
||||
The xCAT B<snmove> command may also be used to synchronize statelite persistent files from the primary service node to the backup service node without actually moving the nodes to the backup servers.
|
||||
|
||||
=item 1.
|
||||
|
||||
The B<syslog> postscript will be run.
|
||||
|
||||
=item 2.
|
||||
|
||||
The B<setupntp> script will be run IF it was included in the nodes postscript list.
|
||||
|
||||
=item 3.
|
||||
|
||||
The B<mkresolvconf> script will be run IF it was included in the nodes postscript list.
|
||||
|
||||
=item 4.
|
||||
|
||||
The default gateway will be switched to the backup service node if B<networks.gateway=<xcatmaster>>.
|
||||
|
||||
=item 5.
|
||||
|
||||
If it is an AIX diskful node then the B<niminit> command will be run so that it will recognize the new service node as it's NIM master.
|
||||
|
||||
=back
|
||||
|
||||
Note: You can also run other postscripts useing -P option if needed.
|
||||
If you run the command with the "-l" option it will attempt to use rsync to update the statelite persistent directory on the backup service node. This will only be done if the server specified in the "statelite" table is the primary service node.
|
||||
|
||||
When the B<snmove> command is executed the new service node must be running but
|
||||
the original service node may be down.
|
||||
@ -87,14 +66,6 @@ Note: On a Linux cluster, for NFS statelite nodes that do not use external NFS s
|
||||
|
||||
=over 10
|
||||
|
||||
=item B<-s|--source>
|
||||
|
||||
Specifies the hostname of the current (source) service node sa known by (facing) the management node.
|
||||
|
||||
=item B<-S|--sourcen>
|
||||
|
||||
Specifies the hostname of the current service node adapter as known by (facing) the nodes.
|
||||
|
||||
=item B<-d|--dest>
|
||||
|
||||
Specifies the hostname of the new destination service node as known by (facing) the management node.
|
||||
@ -103,17 +74,35 @@ Specifies the hostname of the new destination service node as known by (facing)
|
||||
|
||||
Specifies the hostname of the destination service node as known by (facing) the nodes.
|
||||
|
||||
=item B<-h|--help>
|
||||
|
||||
Display usage message.
|
||||
|
||||
=item B<-i|--ignorenodes>
|
||||
|
||||
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.
|
||||
|
||||
=item B<-l|--liteonly>
|
||||
|
||||
Use this option to ONLY synchronize any AIX statelite files from the primary server to the backup server for the nodes. It will not do the actual moving of thre nodes the the backup servers.
|
||||
|
||||
=item B<-P|--postscripts>
|
||||
|
||||
Specifies a list of extra postscripts to be run on the nodes after the nodes are moved over to the new serive 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.
|
||||
|
||||
=item B<-h|--help>
|
||||
=item B<-s|--source>
|
||||
|
||||
Display usage message.
|
||||
Specifies the hostname of the current (source) service node sa known by (facing)
|
||||
the management node.
|
||||
|
||||
=item B<-S|--sourcen>
|
||||
|
||||
Specifies the hostname of the current service node adapter as known by (facing)
|
||||
the nodes.
|
||||
|
||||
=item B<-V|--verbose>
|
||||
|
||||
Verbose mode.
|
||||
|
||||
=item B<-v|--version>
|
||||
|
||||
@ -151,7 +140,7 @@ B<snmove nodegroup1>
|
||||
|
||||
=item 5.
|
||||
|
||||
Move all the nodes in xCAT group "sngroup1" to the SN named "xcatsn2".
|
||||
Move all the nodes in xCAT group "sngroup1" to the service node named "xcatsn2".
|
||||
|
||||
B<snmove sngroup1 -d xcatsn2>
|
||||
|
||||
@ -167,6 +156,12 @@ Move all the nodes in xCAT group "sngroup1" to the SN named "xcatsn2" and do not
|
||||
|
||||
B<snmove sngroup1 -d xcatsn2 -i>
|
||||
|
||||
=item 8.
|
||||
|
||||
Synchronize any AIX statelite files from the primary server for compute03 to the backup server. This will not actually move the node to it's backup service node.
|
||||
|
||||
B<snmove compute03 -l -V>
|
||||
|
||||
=back
|
||||
|
||||
=head1 FILES
|
||||
|
Loading…
Reference in New Issue
Block a user