◦
If the
Key Manager type
=
external
and the
Restored
column = anything other than
yes/true
,
use the
security key-manager external restore
command to restore the key IDs of the
authentication keys.
If the command fails, contact Customer Support.
◦
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
command 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 - FAS500f
Return the failed part to NetApp, as described in the RMA instructions shipped with the
kit. See the
page for further information.
Chassis
Overview of chassis replacement - FAS500f
To replace the chassis, you must move the bezel, controller modules, and NVMe 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 bezel, NVMe drives, 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 - FAS500f
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
.
20
