NetApp AFF A300 - Replace the controller module - AFF A300

are required because the failure is restricted to an HA pair and storage failover commands can be used to
provide nondisruptive operation during the replacement.
• This procedure includes steps for automatically or manually reassigning drives to the replacement node,
depending on your system’s configuration.
You should perform the drive reassignment as directed in the procedure.
• 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.
• Any PCIe cards moved from the old controller module to the new controller module or added from existing
customer site inventory must be supported by the replacement controller module.
NetApp Hardware Universe
• 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.
Shut down the impaired controller - AFF A300
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.
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
MAINT=_number_of_hours_down_h
The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*>
system node autosupport invoke -node * -type all -message MAINT=2h
41