• You can use this procedure with all versions of ONTAP supported by your system.
• This procedure is written with the assumption that you are moving the controller module or modules to the
new chassis, and that the chassis is a new component from NetApp.
• This procedure is disruptive. For a two-node cluster, you will have a complete service outage and a partial
outage in a multi-node cluster.
Shut down the controllers - - AFF A300
Option 1: Shut down the node
You must shut down the node or nodes in the chassis prior to moving them to the new
chassis.
About this task
• If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a
healthy node shows
false for eligibility and health, you must correct the issue before shutting down the
impaired node; see the
Administration overview with the CLI.
• If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:
system node autosupport invoke -node * -type all -message
MAINT=number_of_hours_downh
The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*>
system node autosupport invoke -node * -type all -message MAINT=2h
Steps
1. If your system has two controller modules, disable the HA pair.
If your system is running
clustered ONTAP with…
Then…
Two nodes in the cluster
cluster ha modify -configured false storage failover
modify -node node0 -enabled false
More than two nodes in the
cluster
storage failover modify -node node0 -enabled false
2.
Halt the node, pressing
y when you are prompted to confirm the halt: system node halt -node
node_name
The confirmation message looks like the following:
Warning: Rebooting or halting node
"node_name" in an HA-enabled cluster may result in client disruption or
data access
failure. To ensure continuity of service, use the "storage
failover takeover" command. Are you sure you want to halt node
"node_name"? {y|n}:
301
To Next Page
Loading...
Need help?
General
