NetApp ASA C Series Install page 286

b. Rotate the locking latches upward, tilting them so that they clear the locking pins, and then lower
them into the locked position.
c. If you have not already done so, reinstall the cable management device.
5. Return the controller to normal operation by giving back its storage:
-ofnode impaired_node_name
6. If automatic giveback was disabled, reenable it:
local -auto-giveback true
== Step 5: Return the failed part to NetApp
Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the
Return & Replacements
= Replace an NVDIMM - ASA C800
:icons: font
:relative_path: ./asa-c-800/
:imagesdir: /tmp/d20231020-12297-25s5m0/source/./asa-c-250/../media/
You must replace the NVDIMM in the controller module when your system registers
that the flash lifetime is almost at an end or that the identified NVDIMM is not healthy
in general; failure to do so causes a system panic.
All other components in the system must be functioning properly; if not, you must contact technical
support.
You must replace the failed component with a replacement FRU component you received from your
provider.
== Step 1: Shut down the impaired controller
To shut down the impaired controller, you must determine the status of the controller and, if necessary,
take over the controller so that the healthy controller continues to serve data from the impaired controller
storage.
About this task
• If you are using NetApp Storage Encryption, you must have reset the MSID using the instructions in
the Returning SEDs to unprotected
• If you have a SAN system, you must have checked event messages
show) for impaired controller SCSI blade. The
displays the node name, quorum status of that node, availability status of that node, and operational
status of that node.
Each SCSI-blade process should be in quorum with the other nodes in the cluster. Any issues must
be resolved before you proceed with the replacement.
• If you have a cluster with more than two nodes, 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
Steps
1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:
284
page for further information.
mode.
Synchronize a node with the
storage failover giveback
storage failover modify -controller
(cluster kernel-service
cluster kernel-service show
cluster.
Part
command