Replacing the controller module
You must review the prerequisites for the replacement procedure and select the correct one for your version of the ONTAP operating system.
Before you begin
- All drive shelves must be working properly.
- If your system is in a MetroCluster configuration, you must review the section "Choosing the correct recovery procedure" in the MetroCluster Management and Disaster Recovery Guide to determine whether you should use this procedure.
Shutting down the node
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.
If you have a cluster with more than two nodes,it must be in quorum. If the cluster is not in quorumor a healthy node shows false for eligibility and health, you must correct the issue before shutting down the impaired node.
- If AutoSupport is enabled, suppress automatic log creation by invoking an AutoSupport message:
system node autosupport invoke -node * -type all -message MAINT=<em className="ph i">number_of_hours_down</em>h
Example
The following AutoSupport message suppresses automatic log creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h
Disable automatic giveback from the console of the healthy node: storage failover modify –node local -auto-giveback false
- Take the impaired node to the LOADER prompt:
If the impaired node is displaying... Then... The LOADER prompt Go to the next step. Waiting for giveback... Press Ctrl-C, and then respond y when prompted. System prompt or password prompt (enter system password) Take over or halt the impaired node: For an HA pair, take over the impairednode from the healthy node: storage failover takeover -ofnode impaired_node_name
When the impaired node shows "Waiting for giveback...", press Ctrl-C, and then respond y.
About this task
- You must replace the failed component with a replacement FRU component you received from your provider.
- You must be replacing a controller module with a controller module of the same model type. You cannot upgrade your system by just replacing the controller module.
- You cannot change any drives or drive shelves as part of this procedure.
- In this procedure, the boot device is moved from the impaired node to the replacement node so that the replacement node will boot up in the same version of ONTAP as the old controller module.
- It is important that you apply the commands in these steps on the correct systems:
- The impaired node is the node that is being replaced.
- The replacement node is the new node that is replacing the impaired node.
- The healthy node is the surviving node.
- You must always capture the node's console output to a text file.
This provides you a record of the procedure so that you can troubleshoot any issues that you might encounter during the replacement process.