Step 1: Shut down the impaired controller
You can shut down or take over the impaired controller using different procedures,
depending on the storage system hardware configuration.
Option 1: Most configurations
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.
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
.
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 the next step.
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:
• For an HA pair, take over 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 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
86
