NetApp AFF A700, System Documentation

Page: 518 / 1672

necessary, take over the node so that the healthy node continues to serve data from the
impaired node storage.
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 .
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_down_h
The following AutoSupport message suppresses automatic case creation for two hours:
cluster1:*>
system node autosupport invoke -node * -type all -message MAINT=2h
2. If the impaired node is part of an HA pair, 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 the next step.
Waiting for giveback…
Press Ctrl-C, and then respond
y
.
System prompt or password
prompt (enter system password)
Take over or halt the impaired node:
storage failover
takeover -ofnode impaired_node_name
When the impaired
node shows Waiting for giveback…, press Ctrl-C, and then respond y .
Option 2: Controller is in a MetroCluster
Do not use this procedure if your system is in a two-node MetroCluster configuration.
To shut down the impaired node, you must determine the status of the node and, if necessary, take over the
node so that the healthy node continues to serve data from the impaired node storage.
• 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 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:*>
515