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.
ONTAP 9 System Administration Reference
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
.
Remove the controller module
To access components inside the controller module, you must remove the controller
module from the chassis.
1. If you are not already grounded, properly ground yourself.
2. Unplug the controller module power supply from the power source.
3. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the
system cables and SFPs (if needed) from the controller module, keeping track of where the cables were
connected.
[drw a320 controller cable unplug animated gif] |
58
