Shutting Down The Node; Shutting Down A Node In An Ha Pair - IBM N6270 Hardware And Service Manual

About this task
Note: If you are replacing or installing a Performance Acceleration Module (PAM)
or Flash Cache module, refer to the "Installing or replacing a Flash Cache module
or PAM" appendix in the IBM System Storage N series Introduction and Planning
Guide.
v This procedure refers to HA pairs, which in releases prior to Data ONTAP 8.0
v All other components in the system must be functioning properly; if not, contact

Shutting down the node

You shut down a node using different procedures, depending on whether it is a
stand-alone system or part of an HA pair.

Shutting down a node in an HA pair

To shut down the node, you must determine the status of the node and, if
necessary, take over the node so that the partner continues to serve data from the
node's storage.
Before you begin
Note: If your system has two controller modules in the same chassis, you must
leave the power supplies turned on at the end of this procedure to provide power
to the partner node.
Procedure
1. Check the status of the target node (the node you want to perform maintenance
2. Take one of the following actions, depending on the result of the cf status or
52
IBM System Storage: N6200 Series Hardware and Service Guide
were called active/active configurations.
technical support.
on) by entering the following command at the system console of either node:
For...
7-Mode
Clustered Data ONTAP
storage failover command:
If...
Neither node is in takeover mode
The partner node took over the target node
The target node took over the partner node
Issue the command...
cf status
storage failover show
Then...
Go to the next step in this procedure.
The target node is in a state where you can
begin removing it from the system chassis.
Continue with the task "Opening the
system".
1. Correct the problem that caused the
takeover.
2. Enter the cf giveback command
(7-Mode) or storage failover giveback
-fromnode nodename command (Clustered
Data ONTAP) from the target node
console.
3. Go back to the beginning of this
procedure.