If any LIFs are listed as false, revert them to their home ports:
network interface revert
2. Register the system serial number with NetApp Support.
◦
If AutoSupport is enabled, send an AutoSupport message to register the serial number.
◦
If AutoSupport is not enabled, call
to register the serial number.
3. If automatic giveback was disabled, reenable it:
storage failover modify -node local -auto
-giveback true
Step 4: Return the failed part to NetApp
Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the
Replace a DIMM - FAS500f
You must replace a DIMM in the controller module when your system registers an
increasing number of correctable error correction codes (ECC); 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 mode” section of the
ONTAP 9 NetApp Encryption Power Guide
.
ONTAP 9 NetApp Encryption Power Guide
• If you have a SAN system, you must have checked event messages (
event log show
) for impaired
controller SCSI blade.
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 the
Administration overview with the CLI
.
• If you have a MetroCluster configuration, you must have confirmed that the MetroCluster Configuration
State is configured and that the nodes are in an enabled and normal state (
metrocluster node show
).
Steps
1. 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
44
