node1 true true
node2 true true
node3 true true
node4 true true
4 entries were displayed.
b. Take one of the following actions, depending on the result of the command:
If...
Then...
All nodes show
true
for both health and eligibility.
Proceed to Step 3.
The impaired node shows
false
for health.
Proceed to the next step.
Any nodes show
false
for eligibility.
Resolve any cluster issues as needed before continuing with this
procedure.
Any nodes other than the impaired node show
false
for health. Correct the problems that cause the health issues on the nodes before
continuing with this procedure.
2. Check the status of the impaired node (the node you want to perform maintenance on) by entering the following command at
the system console of either node:
For...
Issue the command...
7-Mode
cf status
Clustered Data ONTAP
storage failover show
3. Take one of the following actions, depending on the result of the
cf status
or
storage failover show
command:
If...
Then...
Neither node is in takeover mode
Go to the next step in this procedure.
The healthy node took over the
impaired node
The impaired node is in a state where you can begin removing it from the system chassis.
The impaired node took over the
healthy node
a. Correct the problem that caused the takeover.
b. Enter the
cf giveback
command (7-Mode) or
storage failover giveback
impaired_node_name
command (clustered Data ONTAP) from the impaired node
console.
c. Go back to the Step 1.
4. Take over and power down the impaired node by taking the following steps:
a. Enter one of the following commands from the healthy node’s console and wait for the takeover to complete:
For systems operating in...
Issue the command...
7-Mode
cf takeover
Clustered Data ONTAP
•
In Data ONTAP 8.1.0 or earlier:
storage failover takeover -fromnode
healthy_node_name
•
In Data ONTAP 8.2 or later:
storage failover takeover -ofnode
impaired_node_name
The impaired node is taken over and then automatically reboots and displays the
Waiting for giveback...
message.
2
Replacing an RTC battery
