A node might need to be deleted from a cluster if the node has failed and is being replaced with a new node or if the repair that has been performed has caused that node to be unrecognizable by the cluster. For example, if the disk drive or the software on the node has been replaced, that node will no longer be known by the cluster.
Use the command line to identify the node to delete.
svcinfo lsnode
The following is an example of what you might see when you use the svcinfo lsnode command.
id name UPS_serial_number WWNN status IO_group_id IO_group_name config_node UPS_unique_id 1 node1 10L3ANP 50050768010000F6 online 0 io_grp0 yes 202378101C0D17A0 2 node2 10L3BNZ 5005076801000184 online 0 io_grp0 no 202378101C0D27AA 3 node3 10L3BNZ 0000000000000000 offline 1 io_grp1 no 202378101C0D27AA 4 node4 10L3ANP 5005076801000147 online 1 io_grp1 no 202378101C0D17A0
Make a note of the Name and the I/O Group Name of the offline node. In the example, node3 is offline and is assigned to io_grp1. You will need this information when you add a node back into the cluster.
| Attention: If more than one SAN Volume Controller in this or in other clusters on the same SAN is offline make a note of that now because you will need to take special precautions when adding the node back into the cluster. |
svcservicetask rmnode node, where node is the name of the offline node noted in step 1.
In this example the command would be:
svcservicetask rmnode node3
No output is displayed.