Skip to main content

Retire node2

Contributors netapp-pcarriga netapp-aherbin
PDFs

To retire node2, you must shut node2 down correctly and remove it from the rack or chassis. If the cluster is in a SAN environment, you also must delete the SAN LIFs.

Steps

  1. Take one of the following actions:

    If the cluster is…​ Then…​

    A two-node cluster

    Go to Step 2.

    A cluster with more than two nodes

    Go to Step 9.

  2. Access the advanced privilege level by entering the following command on either node:

    set -privilege advanced

  3. Verify that the cluster HA has been disabled by entering the following command and examining its output:

    cluster ha show

    The system displays the following message:

    High Availability Configured: false

  4. Check if node2 currently holds epsilon by entering the following command and examining its output:

    cluster show

    The following example shows that node2 holds epsilon:

    cluster*::> cluster show
Node                 Health  Eligibility   Epsilon
-------------------- ------- ------------  -----------
node1                true    true          false
node2                true    true          true

Warning: Cluster HA has not been configured. Cluster HA must be configured on a two-node cluster to ensure data access availability in the event of storage failover. Use the "cluster ha modify -configured true" command to configure cluster HA.

2 entries were displayed.
    Note If you are upgrading a HA pair in a cluster with multiple HA pairs, you must move epsilon to the node of a HA pair not undergoing a controller upgrade. For example, if you are upgrading nodeA/nodeB in a cluster with the HA pair configuration nodeA/nodeB and nodeC/nodeD, you must move epsilon to nodeC or nodeD.

  5. If node2 holds epsilon, mark epsilon as false on the node so that it can be transferred to node3:

    cluster modify -node node2 -epsilon false

  6. Transfer epsilon to node3 by marking epsilon true on node3:

    cluster modify -node node3 -epsilon true

  7. Verify if the setup is a two-node switchless cluster:

    network options switchless-cluster show

    cluster::*> network options switchless-cluster show
Enable Switchless Cluster: false/true

    The value of this command must match the physical state of the system.

  8. Verify if the setup is a two-node switchless cluster:

    network options switchless-cluster show

    cluster::*> network options switchless-cluster show
Enable Switchless Cluster: false/true

    The value of this command must match the physical state of the system.

  9. Return to the admin level:

    set -privilege admin

  10. Halt node2 by entering the following command on either controller:
    system node halt -node node2

  11. After node2 shuts down completely, remove it from the chassis or the rack. You can decommission node2 after the upgrade is completed. See Decommission the old system.