NetApp AFF - Page 864

◦
If the
Key Manager type = onboard and the Restored column = anything other than yes/true,
use the
security key-manager onboard sync command to re-sync the Key Manager type.
Use the security key-manager key query to verify that the
Restored column = yes/true for all
authentication keys.
11. Connect the console cable to the partner controller.
12.
Give back the controller using the
storage failover giveback -fromnode local command.
13.
Restore automatic giveback if you disabled it by using the
storage failover modify -node local
-auto-giveback true
command.
Return the failed part to NetApp - AFF A700s
After you replace the part, you can return the failed part to NetApp, as described in the
RMA instructions shipped with the kit. Contact technical support at
NetApp Support, 888-
463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800
(Asia/Pacific) if you need the RMA number or additional help with the replacement
procedure.
Chassis
Overview of chassis replacement - AFF A700s
To replace the chassis, you must move the controller modules and SSD drives from the
impaired chassis to the replacement chassis, and then remove the impaired chassis from
the equipment rack or system cabinet and install the replacement chassis in its place.
All other components in the system must be functioning properly; if not, you must contact technical support.
• You can use this procedure with all versions of ONTAP supported by your system.
• This procedure is written with the assumption that you are moving the SSDs and controller modules to the
new chassis, and that the replacement chassis is a new component from NetApp.
• This procedure is disruptive. For a two-node cluster, you will have a complete service outage and a partial
outage in a multi-node cluster.
Shut down the controllers - AFF A700s
You must shut down the controller or controller in the chassis prior to moving them to the new chassis.
About this task
• If you have a cluster with more than two controllers, it must be in quorum. If the cluster is not in quorum or
a healthy controller shows false for eligibility and health, you must correct the issue before shutting down
the impaired controller; see the
Administration overview with the CLI.
• 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
862