Unjoin Nodes from a Cluster (cDOT)

  1. Move or delete all volumes and member volumes from aggregates owned by the node to be unjoined
    • nitish-mgmt::> volume move target-aggr show -vserver nitish -volume nitish_test9
    • nitish-mgmt::> volume move start -perform-validation-only true -vserver nitish -volume nitish_test9 -destination-aggregate nitish01_sas_1
    • nitish-mgmt::> volume move start -vserver nitish -volume nitish_test9 -destination-aggregate nitish01_sas_1
    • nitish-mgmt::> vol move show
  2. Quiesce and Break LS Snapmirrors with destinations on aggregates that are owned by the node/s being removed
    • nitish-mgmt::> snapmirror show -type LS
    • nitish-mgmt::> snapmirror quiesce –destination-path <destination-path>
    • nitish-mgmt::> snapmirror break –destination-path <destination-path>
    • nitish-mgmt::> snapmirror delete –destination-path <destination-path>
  3. Offline and delete those snapmirror destination volumes
    • nitish-mgmt::> vol offline –vserver nitish –volume nitish_test9
    • nitish-mgmt::> vol destroy –vserver nitish –volume nitish_test9
  4. Move or delete all aggregates (except for the mroot aggregate) owned by the node to be unjoined
    • nitish-mgmt::> aggr offline <aggr-name>
    • nitish-mgmt::> aggr delete <aggr-name>
  5. Delete or re-home all data LIFs from the node to be unjoined to other nodes in the cluster
    • nitish-mgmt::> network interface delete
    • nitish-mgmt::> network interface migrate
    • nitish-mgmt::> network interface modify
  6. Modify all LIF failover rules to remove ports on the node to be unjoined
    • nitish-mgmt::> failover-groups delete -failover-group data -node nitish-01 -port e0e
    • nitish-mgmt::> failover-groups delete -failover-group data -node nitish-02 -port e0e
  7. Disable SFO on the node to be unjoined
    • nitish-mgmt::> storage failover modify -node nitish-01 –enabled false
  8. Move epsilon to a node other than the node to be unjoined
    • nitish-mgmt::*> cluster show
    • nitish-mgmt::*> cluster ring show
    • nitish-mgmt::*> cluster modify -node nitish-01 –epsilon false
    • nitish-mgmt::*> cluster modify –node nitish-03 –epsilon true
    • nitish-mgmt::*> cluster show
    • nitish-mgmt::*> cluster ring show
  9. Delete all VLANs on the node to be unjoined
    • nitish-mgmt::> vlan delete
  10. Trigger an autosupport from the node to be unjoined
    • nitish-mgmt::> system node autosupport invoke -type all -node nitish-01 -message “pre_unjoin”
  11. Run the cluster unjoin command from a different node in the cluster besides the node that is to be unjoined
    • nitish-mgmt::*> unjoin –node nitish-01
    • nitish-mgmt::*> unjoin –node nitish-02
  • Warning: This command will unjoin node “nitish-01” from the cluster. You must unjoin the failover partner as well. After the node is successfully unjoined, erase its configuration and initialize all disks by using the “Clean configuration and initialize all disks (4)” option from the boot menu.Do you want to continue? {y|n}: y

    [Job 32] Cleaning cluster database [Job 32] Job succeeded: Cluster unjoin succeeded

    *******************************

    * *

    * Press Ctrl-C for Boot Menu. *

    * *

    *******************************

    This node was removed from a cluster. Before booting, use

    option (4) to initialize all disks and setup a new system.

    Normal Boot is prohibited.

    Please choose one of the following:

    (1) Normal Boot.

    (2) Boot without /etc/rc.

    (3) Change password.

    (4) Clean configuration and initialize all disks.

    (5) Maintenance mode boot.

    (6) Update flash from backup config.

    (7) Install new software first.

    (8) Reboot node.

    Selection (1-8)?

    Once Option 4 (or ‘wipeconfig’ and ‘init’) is run, the node is considered to be a ‘fresh’ node.

After the node is unjoined from the cluster, it cannot be re-joined to this or any other cluster until the wipeclean process is performed.

Leave a Reply

Your email address will not be published. Required fields are marked *