NetApp AFF A300 - Page 107

• If you have a MetroCluster configuration, you must have confirmed that the MetroCluster Configuration
State is configured and that the nodes are in an enabled and normal state (
metrocluster node show).
Steps
1. 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
2.
Disable automatic giveback from the console of the healthy node:
storage failover modify –node
local -auto-giveback false
3. Take the impaired node to the LOADER prompt:
If the impaired node is
displaying…
Then…
The LOADER prompt Go to Remove controller module..
Waiting for giveback…
Press Ctrl-C, and then respond y when prompted.
System prompt or password
prompt (enter system password)
Take over or halt the impaired node from the healthy node: storage
failover takeover -ofnode impaired_node_name
+
When the impaired node shows Waiting for giveback…, press Ctrl-C,
and then respond
y.
+
Option 3: Controller is in a two-node MetroCluster
To shut down the impaired node, you must determine the status of the node and, if
necessary, switch over the node so that the healthy node continues to serve data from
the impaired node storage.
About this task
• If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the
"Return a FIPS drive or SED to unprotected mode" section of
NetApp Encryption overview with the CLI.
• You must leave the power supplies turned on at the end of this procedure to provide power to the healthy
node.
Steps
1. Check the MetroCluster status to determine whether the impaired node has automatically switched over to
the healthy node: metrocluster show
2. Depending on whether an automatic switchover has occurred, proceed according to the following table:
105