Option 2: Controller is in a two-node MetroCluster
To shut down the impaired controller, you must determine the status of the controller and, if
necessary, switch 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 "Return a FIPS drive or SED to unprotected mode" section of
NetApp
Encryption overview with the CLI
.
• You must leave the power supplies turned on at the end of this procedure to provide power to the
healthy controller.
Steps
1. Check the MetroCluster status to determine whether the impaired controller has automatically
switched over to the healthy controller:
metrocluster show
2. Depending on whether an automatic switchover has occurred, proceed according to the
following table:
If the impaired controller… Then…
Has automatically switched
over
Proceed to the next step.
Has not automatically
switched over
Perform a planned switchover operation from the healthy
controller:
metrocluster switchover
Has not automatically
switched over, you attempted
switchover with the
metrocluster
switchover
command, and
the switchover was vetoed
Review the veto messages and, if possible, resolve the issue
and try again. If you are unable to resolve the issue, contact
technical support.
3.
Resynchronize the data aggregates by running the
metrocluster heal -phase
aggregates
command from the surviving cluster.
controller_A_1::> metrocluster heal -phase aggregates
[Job 130] Job succeeded: Heal Aggregates is successful.
If the healing is vetoed, you have the option of reissuing the metrocluster heal command
with the
-override-vetoes parameter. If you use this optional parameter, the system
overrides any soft vetoes that prevent the healing operation.
4. Verify that the operation has been completed by using the metrocluster operation show
command.
141
To Next Page
Loading...
