Replace the NVRAM module and/or NVRAM DIMMs - AFF A900
The NVRAM module consists of the NVRAM11 and DIMMs. You can replace a failed
NVRAM module or the DIMMs inside the NVRAM module. To replace a failed NVRAM
module, you must remove it from the chassis, move the DIMMs to the replacement
module, and install the replacement NVRAM module into the chassis.
To replace and NVRAM DIMM, you must remove the NVRAMmodule from th chassis, replace the failed DIMM
in the module, and then reinstall the NVRAM module.
About this task
Because the system ID is derived from the NVRAM module, if replacing the module, disks belonging to the
system are reassigned to a new system ID.
Before you begin
• All disk shelves must be working properly.
• If your system is in an HA pair, the partner node must be able to take over the node associated with the
NVRAM module that is being replaced.
• This procedure uses the following terminology:
◦ The impaired node is the node on which you are performing maintenance.
◦ The healthy node is the HA partner of the impaired node.
• This procedure includes steps for automatically or manually reassigning disks to the controller module
associated with the new NVRAM module. You must reassign the disks when directed to in the procedure.
Completing the disk reassignment before giveback can cause issues.
• You must replace the failed component with a replacement FRU component you received from your
provider.
• You cannot change any disks or disk shelves as part of this procedure.
Step 1: Shut down the impaired node
Steps
You can shut down or take over the impaired controller using different procedures,
depending on the storage system hardware configuration.
Option 1: Most configurations
To shut down the impaired node, you must determine the status of the node and, if
necessary, take over the node so that the healthy node continues to serve data from the
impaired node storage.
About this task
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
node shows false for eligibility and health, you must correct the issue before shutting down the impaired node;
see the
Administration overview with the CLI.
Steps
1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:
system node autosupport invoke -node * -type all -message
92