Problem:
How do I wipe or decommission a NetApp SAN to clear config and wipe or zero disks?
Solution:
First you will need to break the cluster:
prdsan02::*> cluster ha modify -configured false Warning: This operation will unconfigure cluster HA. Cluster HA must be configured on a two-node cluster to ensure data access availability in the event of storage failover. Do you want to continue? {y|n}: y Notice: HA is disabled.
Then you need to disable failover:
prdsan02::*> storage failover modify -enabled false -node prdsan02-node01
At this stage we can use the GUI to delete all the existing iSCSI interfaces and to migrate the cluster LIF to another node.
We are now ready to remove the 2nd node from the cluster:
prdsan02::*> cluster unjoin -node prdsan02-node02 Warning: This command will remove node "prdsan02-node02" from the cluster. You must remove the failover partner as well. After the node is removed, 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 Warning: This operation will cause node "prdsan02-node02" to be marked as unhealthy. Unhealthy nodes do not participate in quorum voting. If the node goes out of service and one more node goes out of service there will be a data serving failure for the entire cluster. This will cause a client disruption. Use "cluster show" to verify cluster state. If possible bring other nodes online to improve the resiliency of this cluster. Do you want to continue? {y|n}: y [Job 54599] Job is queued: Cluster remove-node of Node:prdsan02-node02 with UU[Job 54599] Cleaning cluster database Warning: Are you sure you want to reboot node "prdsan02-node01"? {y|n}: y
While rebooting hit CTRL+C and wait for the boot menu, then type wipeconfig:
^CSuccessfully loaded SVM keys. Boot Menu will be available. 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. (9) Configure Advanced Drive Partitioning. (10) Set Onboard Key Manager recovery secrets. (11) Configure node for external key management. Selection (1-11)? wipeconfig
Now you can reboot the first node and do the same:
prdsan02::> system node reboot -node prdsan02-node01 -reason decom Warning: Are you sure you want to reboot node "prdsan02-node01"? {y|n}: y SP-login: sshkey_generate failed Terminated . Uptime: 48m58s System rebooting... Boot Loader version 6.0.12 Copyright (C) 2000-2003 Broadcom Corporation. Portions Copyright (C) 2002-2021 NetApp, Inc. All Rights Reserved. Starting AUTOBOOT press Ctrl-C to abort... Boot Menu will be available. SUCCESS Sep 08 14:01:39 Power outage protection flash de-staging: 51 cycles 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. (9) Configure Advanced Drive Partitioning. (10) Set Onboard Key Manager recovery secrets. (11) Configure node for external key management. Selection (1-11)? wipeconfig
You may run into this error ‘Remove the LIF from port sets before deleting the LIF’. If so you can do the following to remove the portsets:
lun portset show lun portset remove -vserver prd_svm -portset prd_portset -port-name san_node_1_iscsi_prd_1
If you cant remove portsets you may see this Error: command failed: Cannot remove all ports from portset “prd_portset”. Igroups are bound to it. So do the following:
lun igroup show lun igroup unbind -vserver prd_svm -igroup prd_esxi
You can then just delete the ports in the GUI. If you cant delete in the gui use these commands to remove logical interface:
sancluster1::*> network interface delete -vserver sancluster1 -lif cluster_setup_cluster_mgmt_lif_1 Warning: Deleting cluster management LIF "cluster_setup_cluster_mgmt_lif_1" (role "cluster-mgmt") is not recommended. This type of LIF is used for administration of the cluster. If you are currently logged in using this LIF, you will be disconnected if you continue. Do you want to continue? {y|n}: y
