6. Halt all nodes in the cluster:
system node halt -node * -skip-lif-migration-before-shutdown true -ignore
-quorum-warnings true -inhibit-takeover true
.
For clusters using SnapMirror synchronous operating in StrictSync mode: system node
halt -node * -skip-lif-migration-before-shutdown true -ignore-quorum
-warnings true -inhibit-takeover true -ignore-strict-sync-warnings
true
7.
Enter y for each controller in the cluster when you see
Warning: Are you sure you want to halt
node "cluster name-controller number"?
{y|n}:
8. Wait for each controller to halt and display the LOADER prompt.
9. Turn off each PSU or unplug them if there is no PSU on/off switch.
10. Unplug the power cord from each PSU.
11. Verify that all controllers in the impaired chassis are powered down.
Option 2: Shut down a node in a two-node MetroCluster configuration
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
485
To Next Page
Loading...
