Adding a node to increase the size of your cluster using the CLI Increasing the size of your cluster using the CLI Migrating a VDisk to a new I/O group

This task provides step-by-step instructions for adding a node to increase the size of your cluster using the CLI.

Steps

Perform the following steps to add a node to increase the size of your cluster:

  1. Issue the following command to verify that the node can be seen on the fabric:
    svcinfo lsnodecandidate
    You should see the node listed as a candidate.
    Note:Note: Remember the WWNN's. You will need it in the following step.
  2. Issue the following command to determine the I/O group you wish to add the nodes to:
    svcinfo lsiogrp
  3. Select the first I/O group listed that has a node count = 0.
    Note:Note: Remember the I/O group name or ID. You will need it in the following step.
  4. Attention: Attention: If you are re-adding a node to the SAN, ensure that you are adding the node to the same I/O group that it was removed from. Failure to do this can result in data corruption. Use the information that was recorded when the node was originally added to the cluster. If you do not have access to this information, call IBM Service to add the node back into the cluster without corrupting the data.

    This can avoid a possible data corruption exposure if the node must be removed from and re-added to the cluster.

    Note:Note: This warning also is displayed on the SAN Volume Controller Console panel when adding the node.
    Issue the following command to add the node into the cluster. The <newnodename> is the name you wish to assign to this node.
    svctask addnode -wwnodename <WWNN> -iogrp <newiogrpname/id>
    [-name <newnodename>]

  5. Issue the following command to verify that the node is online:
    svcinfo lsnode
    You may also need to modify the configuration of your disk controllers. If your controller uses a mapping technique to present its RAID arrays or partitions to the cluster you will need to modify the port groups that belong to the cluster because the WWNN and WWPN's of the node have changed.
Related topics Increasing the size of your cluster using the CLI Migrating a VDisk to a new I/O group

(C) Copyright International Business Machines Corporation 2003, 2004