Warning: Rebooting or halting node
"node_name" in an HA-enabled cluster may result in client disruption or
data access
failure. To ensure continuity of service, use the "storage
failover takeover" command. Are you sure you want to halt node
"node_name"? {y|n}:
You must perform a clean system shutdown before replacing the chassis to avoid losing
unwritten data in the nonvolatile memory (NVMEM). If the NVMEM LED is flashing, there is
content in the NVMEM that has not been saved to disk. You need to reboot the node and
start from the beginning of this procedure. If repeated attempts to cleanly shut down the
node fail, be aware that you might lose any data that was not saved to disk.
3. Where applicable, halt the second node to avoid a possible quorum error message in an HA pair
configuration:
system node halt -node second_node_name -ignore-quorum-warnings true
Option 2: Shut down a node in a two-node MetroCluster configuration
To shut down the impaired node, you must determine the status of the node and, if
necessary, switch over the node so that the healthy node continues to serve data from
the impaired node 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
Administration overview with the CLI
• You must leave the power supplies turned on at the end of this procedure to provide power to the healthy
node.
Steps
1. Check the MetroCluster status to determine whether the impaired node has automatically switched over to
the healthy node:
metrocluster show
2. Depending on whether an automatic switchover has occurred, proceed according to the following table:
If the impaired node…
Then…
Has automatically switched over
Proceed to the next step.
Has not automatically switched
over
Perform a planned switchover operation from the healthy node:
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
2
