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. 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 force option to stop and remove running nodes. This handles the situation where a NIM machine definition indicates that a node is still running even though it is not.
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.
2) Remove the NIM client machine definition for xCAT node "node02" that was created with the mkdsklsnode -n option and the image "AIXdskls". (i.e. NIM client machine name "node02_AIXdskls".)
