How to Shutdown Netapp Cluster Mode Storage System with Multi-Node Cluster (6 nodes cluster with ontap version 9.1P14 with model FAS8200, AFF8040 & AFF8020)
Here we have explain step by step how to shutdown the Netapp storage System with Multi-Node Cluster (6 nodes cluster with ontap version 9.1P14 with model FAS8200, AFF8040 & AFF8020)
Dynamic Routing with FRR - pfSense Hangout December 2017
Similar to How to Shutdown Netapp Cluster Mode Storage System with Multi-Node Cluster (6 nodes cluster with ontap version 9.1P14 with model FAS8200, AFF8040 & AFF8020)
Similar to How to Shutdown Netapp Cluster Mode Storage System with Multi-Node Cluster (6 nodes cluster with ontap version 9.1P14 with model FAS8200, AFF8040 & AFF8020) (20)
[2024]Digital Global Overview Report 2024 Meltwater.pdf
How to Shutdown Netapp Cluster Mode Storage System with Multi-Node Cluster (6 nodes cluster with ontap version 9.1P14 with model FAS8200, AFF8040 & AFF8020)
1. 1
How to Shutdown Netapp Cluster Mode Storage System with
Multi-Node Cluster (6 nodes cluster with ontap version 9.1P14
with model FAS8200, AFF8040 & AFF8020)
[if any command is not executing then you need to use the advance mode to execute them
and sometimes you need to type the command instead of simple copy and paste]
Action Items for powering down of Netapp SAN-:
Take the backup of the NetApp configurations files for the future reference.
Trigger the ASUP, for the starting of the maintenance activity.
Shutdown all the connected CIFS/NFS clients and hosts that have FCP or iSCSI-based
LUNs. (All the host machine if you have a plan for Data Center maintenance or power
down activity)
Shutdown the controllers first and wait for 1-2 mins.
Shutdown all the disk-shelves one by one, by removing the power cords from the
respective shelves.
Shutdown the network switches (if you have a plan to shut-down your Data Center)
1.Pre-checks
As a part of pre-checks,you can take the couple of commands out put into your notepad for the
future reference ifsomethingmissmatched after the poweringup the Netapp cluster.
network interface show
vserver show
volumeshow
system node show
lunshow
igroupshow -vserver *
iscsi show
iscsi security show
iscsi sessionshow
storage aggregate show
storage diskshow
storage shelfshow
2. 2
df -g
cifsshow
nfsshow
sp show
system service-processorshow
cluster peer show
cluster ha show
license show
ntp server show
timezone -version
network interface show-vserver Cluster
cluster show
cifsshare show
ipspaceshow
system service-processornetwork show
cluster identityshow
cluster ha show
storage failovershow
storage failoverhwassistshow
autosupportshow
storage shelfshow
storage aggregate show-spare-disks
storage aggregate show-status
diskshow -fieldsnode,aggregate
network interface failover-groupsshow
iscsi connectionshow
system node hardwareunified-connectshow
network port show
acp show
vserver services name-servicednsshow
cluster time-servicentp server show
system healthstatus show
system healthconfigshow
network route show
network port broadcast-domainshow
network subnet show
system cluster-switchshow
2. Take Configuration Backup by executing the below command-:
Note- You needswitchto advanced mode and execute the belowcommand to take the configuration
backup as belowis the one example,the same way you needto take the backup for all the nodes.
3. 3
Live Example-:
clus-prod-1::*> set-privilege advanced
Warning:These advancedcommands are potentiallydangerous;use them onlywhen directedto do
so by NetApp
personnel.
Do you want to continue?{y|n}: y
Syntax-:
#systemconfigurationbackupcreate -node <node name> -backup-type cluster -
backup-name <Name of the backup file>
clus-prod-1::*>systemconfigurationbackup create -node clus-prod-1n1-backup-type cluster -backup-
name Backup_Before_shutdown_clus-prod-1n1
[Job 77985] Job is queued:ClusterBackup OnDemand Job.
To see the job status as below-:
Syntax-
#Job show-id<job ID>
Live example-:
clus-prod-1::*>jobshow -id77985
Owning
Job ID Name Vserver Node State
------ ------------------------------ -------------- ----------
77985 CLUSTER BACKUP ONDEMAND
clus-prod-1 clus-prod-1n1 Running
Description:ClusterBackup Job
Now you can take the cluster configurationbackupfor all the nodes by
executing the commands as below.
4. 4
clus-prod-1::*>systemconfigurationbackup create -node clus-prod-1n2-backup-type cluster -backup-
name Backup_Before_shutdown_clus-prod-1n2
clus-prod-1::*>systemconfigurationbackup create -node clus-prod-1n3-backup-type cluster -backup-
name Backup_Before_shutdown_clus-prod-1n3
clus-prod-1::*>systemconfigurationbackup create -node clus-prod-1n4-backup-type cluster -backup-
name Backup_Before_shutdown_clus-prod-1n4
clus-prod-1::*>systemconfigurationbackup create -node clus-prod-1n5-backup-type cluster -backup-
name Backup_Before_shutdown_clus-prod-1n5
clus-prod-1::*>systemconfigurationbackup create -node clus-prod-1n5-backup-type cluster -backup-
name Backup_Before_shutdown_clus-prod-1n6
To check the backup is taken or not by executing the belowcommand-:
clus-prod-1::*>systemconfigurationbackup show
3. Trigger the Autosupport, that you are doing some maintenance
activity so Netapp support can be aware of your activity.
clus-prod-1::>autosupport invoke -node * -type test -message “Power_down_Activity_started”
Note- * in the above command is for all the nodesASUP is triggering.
4. shut down all the connected CIFS and NFS clients. (If you wanted to
shutdown for the entire data center then do shutdown all the
connected CIFS and NFS clients)
If only needto shut down the Netappstorage system, thenexecutethe below
command-:
clus-prod-1::>cifssessionclose
5. 5
clus-prod-1::>cifsstop -vserver*
clus-prod-1::>nfs stop -vserver*
Note – In above commands * representsfor all the Vservesin the storage system.
5.If your storage system is serving the SAN (FCP and ISCIS) LUNs, then
shutdown all the connected hosts before shutting down the storage
system.
6.Stop Vservers execute the below command-:
clus-prod-1::>vserver stop -vserver* -foregroundtrue
Note- It will show you the message of stoppingthe Vservers,ifyou will use the command -background
then it will be not visible inthe console.
Live example snapshot as below-:
clus-prod-1::>vserver show -fieldsvserver
Note- onlydata vserversare goingto stop, so if some vserveris not stopping thenplease ignore them
as they are offline vserveror clustervserver.
7. Identify Primary and Secondary Nodes
clus-prod-1::*> clusterring show
6. 6
Note- This command will be executedin advancedmode and we can see the one node will be the
master and others will be the secondary nodes.
Live example-:Small portion of the snapshot as below.
Note-Nowyouhave identifiedwhichone isMaster and whichnodes are secondary.
Note-Checkfewthingsifyou wanted to rebootthe clusternodes but it isnot requiredto shutdown
the clusteras below.
clus-prod-1::> cf status
Takeover
7. 7
Node Partner TakeoverPossible State Description
-------------- ---------------------- -------------------------------------
clus-prod-1n1 clus-prod-1n2 true Connectedto clus-prod-1n2
clus-prod-1n2 clus-prod-1n1 true Connectedto clus-prod-1n1
clus-prod-1n3 clus-prod-1n4 true Connectedto clus-prod-1n4
clus-prod-1n4 clus-prod-1n3 true Connectedto clus-prod-1n3
clus-prod-1n5 clus-prod-1n6 true Connectedto clus-prod-1n6
clus-prod-1n6 clus-prod-1n5 true Connectedto clus-prod-1n5
6 entrieswere displayed.
Collectclusterstatus information-:
clus-prod-1::> storage failovershow-giveback
Partner
Node Aggregate GivebackStatus
-------------- ----------------- ---------------------------------------------
clus-prod-1n1 No aggregatesto give back
clus-prod-1n2 No aggregatesto give back
clus-prod-1n3 No aggregatesto give back
clus-prod-1n4 No aggregatesto give back
clus-prod-1n5 No aggregatesto give back
clus-prod-1n6 No aggregates to give back
6 entrieswere displayed.
clus-prod-1::> storage failovershow-takeover
Node Node Status Aggregate Takeover Status
---------- --------------------- -------------- -------------------------------
clus-prod-1n1 Takeover not
attempted.
- -
9. 9
n3_aggr810g_mroot
cfo
n3_aggr810g_ssd_1
sfo
n4_aggr41t_ssd sfo
n4_aggr810g_mroot
cfo
n5_aggr810g_ssd_mroot
cfo
n5aggr810g_ssd_1
sfo
n6_aggr810g_0 sfo
n6_aggr810g_ssd_mroot
cfo
17 entrieswere displayed.
Note- Inabove the command output of “storage aggregate show -fields ha-
policy”you can have the aggregate status informationoncluster failover (CFO)
and storage failover (SFO). If you do manual cluster failover thenCFO
aggregates will be migrating fromnode to takeover node.
SFO = Storage Failover
CFO = ClusterFailover
RDB = ReplicatedDatabase
8.Disable Failover
Failoverdisablingwill helpwhenyou start the nodesthey juststart as it is,do not look for other
nodes’takeoveror givebackprocess.
if you have two nodesthendisable HA more than two nodesdisable failover
10. 10
clus-prod-1::> storage failovermodify-node clus-prod-1n*-enabledfalse
HALT Each Node in NetappClusterone by one but needto halt the secondary nodesfirst then the last
one would be the primary node.
To halt each node,loginto any one of the SP/RLM IP address thenhalt othernodes from master node.
Rememberto halt secondary nodesfirst. Ring show command will give more detailson node roles
which we have already executedthe command and taken the output.
hrz-na-1::> sp show
IP Firmware
Node Type Status Configured Version IP Address
------------- ---- ----------- ------------ --------- -------------------------
clus-prod-1n1 SP online true 5.1P1 10.190.17.170
clus-prod-1n2 SP online true 5.1P1 10.190.17.171
clus-prod-1n3 SP online true 3.3P3 10.190.17.172
clus-prod-1n4 SP online true 3.3P3 10.190.17.173
clus-prod-1n5 SP online true 3.3P3 10.190.17.174
clus-prod-1n6 SP online true 3.3P3 10.190.17.175
6 entrieswere displayed.
9.HALT the Nodes by executing the below command-:
clus-prod-1::>halt -node clus-prod-1n6-inhibit-takeovertrue -ignore-quorum-warningstrue -skip-lif-
migration-before-shutdowntrue -reason "Maintenance Activityplanned"
clus-prod-1::>halt -node clus-prod-1n5-inhibit-takeovertrue -ignore-quorum-warningstrue -skip-lif-
migration-before-shutdowntrue -reason "Maintenance Activityplanned"
clus-prod-1::>halt -node clus-prod-1n4-inhibit-takeovertrue -ignore-quorum-warningstrue -skip-lif-
migration-before-shutdowntrue -reason "Maintenance Activityplanned"
11. 11
clus-prod-1::>halt -node clus-prod-1n3-inhibit-takeovertrue -ignore-quorum-warningstrue -skip-lif-
migration-before-shutdowntrue -reason "Maintenance Activityplanned"
clus-prod-1::>halt -node clus-prod-1n2-inhibit-takeovertrue -ignore-quorum-warningstrue -skip-lif-
migration-before-shutdowntrue -reason "Maintenance Activityplanned"
clus-prod-1::>halt -node clus-prod-1n1-inhibit-takeovertrue -ignore-quorum-warningstrue -skip-lif-
migration-before-shutdowntrue -reason "Maintenance Activityplanned"
Action Items for powering up of Netapp SAN-:
Power up ofall the network switches.(Incase of Data Centerpower up/down activity)
Power up ofall the disk-shelves,thenwait5 to 10Mins, ifall looks good thenjump to the next
step.
Power up ofall the controllers.
Logging into the Netapp and needto do the post check validation.
Note-Like execute all the commands which we have executedbefore shutdownofthe Netapp
clusterand enable the cluster failoverby executingthe belowcommand.
clus-prod-1::>storage failovermodify-node clus-prod-1n* -enabledtrue
Trigger the ASUPas maintenance activityis completed
Thank you so much!!
Saroj Kumar Sahu
NCDA, NetappEngineer
Sarojmsc@gmail.com
YouTube channel-:
https://www.youtube.com/channel/UCNVRwl2kYmNWojAAkGBZmQA
SlideShare-:
https://www.slideshare.net/SarojSahu14/edit_my_uploads