NetApp AFF A300 - Option 2: Controllers are in a two-node MetroCluster configuration

Warning: This operation will cause node "node-name" to be marked as
unhealthy. Unhealthy nodes do not participate in quorum voting. If the
node goes out of service and one more node goes out of service there
will be a data serving failure for the entire cluster. This will cause a
client disruption. Use "cluster show" to verify cluster state. If
possible bring other nodes online to improve the resiliency of this
cluster.
Do you want to continue? {y|n}:
You must perform a clean system shutdown before replacing the chassis to avoid losing
unwritten data in the nonvolatile memory (NVMEM/NVRAM). Depending on your system, if
the NVMEM/NVRAM LED is flashing, there is content in the NVMEM/NVRAM 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
-skip-lif-migration-before-shutdown true
Answer y when prompted.
Option 2: Controllers are 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
"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
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
27