Replacing A Boot Device In A System Running In Clustered Data Ontap; Shutting Down A Node In A High-Availability Configuration; Opening The System - IBM N6270 Hardware And Service Manual

Replacing a boot device in a system running in Clustered
Data ONTAP
Replacing a boot device in Clustered Data ONTAP involves shutting down the
node, removing the old boot device, and transferring the system files to the new
boot device using either netboot on a local server or netboot with an HTTP server.
About this task
This procedure is for systems running Data ONTAP Clustered Data ONTAP. If
your system is running Data ONTAP 7-Mode, you must use that procedure
instead.

Shutting down a node in a high-availability configuration

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.
About this task
Note: 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 storage
3. Take over the target node by entering the following command:

Opening the system

To access components inside the controller module, you must open the system.
Procedure
1. If you are not already grounded, properly ground yourself.
2. Unplug the system cables and SFPs from the controller module, as needed, and
78
IBM System Storage: N6200 Series Hardware and Service Guide
on) by entering the following command at the system console of either node:
storage failover show
failover show command:
If...
Neither node is in takeover mode
The partner node took over the target node
The target node took over the partner node
storage failover takeover -ofnode target_node_name
keep track of where the cables were connected. Leave the cables in the cable
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.
1. Correct the problem that caused the
takeover.
2. Enter the following command:
storage failover giveback -ofnode
partner_node_name
3. Go back to the beginning of this
procedure.