Shut down the node - AFF A250
Option 1: Most systems
After completing the NVE or NSE tasks, you need to complete the shutdown of the
impaired node.
Steps
1. If the impaired node isn’t at the LOADER prompt:
If the impaired node displays…
Then…
Waiting for giveback...
Press Ctrl-C, and then respond
y
when prompted.
System prompt or password
prompt (enter system password)
Take over or halt the impaired node:
• For an HA pair, take over the impaired node from the healthy
node:
storage failover takeover -ofnode
`impaired_node_name`
When the impaired node shows Waiting for giveback…, press
Ctrl-C, and then respond
y
.
2. From the LOADER prompt, enter:
printenv
to capture all boot environmental variables. Save the output
to your log file.
This command may not work if the boot device is corrupted or non-functional.
Option 2: Systems is in a MetroCluster
After completing the NVE or NSE tasks, you need to complete the shutdown of the
impaired node.
Do not use this procedure if your system is in a two-node MetroCluster configuration.
To shut down the impaired node, you must determine the status of the node and, if necessary, take over the
node so that the healthy node continues to serve data from the impaired node storage.
• 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 node shows false for eligibility and health, you must correct the issue before shutting down the
impaired node; 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
16