clarify results of -f and -r options

git-svn-id: https://svn.code.sf.net/p/xcat/code/xcat-core/branches/2.8@15438 8638fb3e-16cb-4fca-ae20-7b5d299a9bcd
This commit is contained in:
nott 2013-03-08 15:14:27 +00:00
parent 00c79814f4
commit 6c2c51d3d5

View File

@ -14,11 +14,15 @@ Use this command to remove all NIM client machine definitions that were created
The xCAT node definitions will not be removed.
The default is to assume that the NIM machine names are the same as the xCAT node names. If you had used the "-n" option when you created the NIM machine definitions with the B<mkdsklsnode> command then the NIM machine names would be a combination of the xCAT node name and the osimage name used to initialize the NIM machine. To remove these definitions you must provide the name of the osimage that was used.
The default is to assume that the NIM client names are the same as the xCAT node names. If you had used the "-n" option when you created the NIM client definitions with the B<mkdsklsnode> command then the NIM machine names would be a combination of the xCAT node name and the osimage name used to initialize the NIM machine. To remove these definitions you must provide the name of the osimage that was used.
If you are using xCAT service nodes the B<rmdsklsnode> command will automatically determine the correct server(s) for the node and remove the NIM definitions on that server(s).
If the node you are trying to remove is currently running the B<rmdsklsnode> command will not remove the definitions. You can use the "-f" option to shut down the node and remove the definition. You can also use the "-r" option to leave the node running but remove the NIM definitions.
If the node you are trying to remove is currently running the B<rmdsklsnode> command will not remove the definitions. You can use the "-f" option to shut down the node and remove the definition.
You can also use the "-r" option to leave the node running but remove the NIM definitions. However, this will remove the NIM setup for this node and you will have to run mkdsklsnode again if you wish to boot the node.
B<Note:> Removing an alternate NIM client definition, created with "mkdsklsnode -n", will remove the entries for the node in the /etc/bootptab and /tftpboot files which means you will not be able to reboot the node without running mkdsklsnode again. If you want to clean up old NIM definitions and resources you should wait until you can bring the nodes down. At that point you can remove the old NIM client defintions and old resource, then run mksklsnode, and boot the nodes.
Use the xCAT B<rmdef> command to remove xCAT node definitions.
@ -54,7 +58,7 @@ te both the primary and backup service nodes.
=item B<-r|--remdef>
Use this option to reset, deallocate, and remove NIM client definitions. This option will not attempt to shut down running nodes.
Use this option to reset, deallocate, and remove NIM client definitions. This option will not attempt to shut down running nodes. However, this will leave the node in a state unsupported by NIM.
=item B<-V |--verbose>
@ -90,10 +94,6 @@ B<rmdsklsnode -i AIXdskls node02>
B<rmdsklsnode -f aixnodes>
4) Remove the NIM client definitions for all the xCAT nodes in the group "aixnodes". Do not attempt to shut down any running nodes.
B<rmdsklsnode -r aixnodes>
=head1 FILES
/opt/xcat/bin/rmdsklsnode