NetApp FAS2600, Руководство пользователя

Страница: 738 / 786

or eight node MetroCluster configuration is the same as that in an HA pair. No MetroCluster-specific steps
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.
• 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.
Shut down the impaired node - FAS9500
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
The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*>
system node autosupport invoke -node * -type all -message MAINT=2h
736