Skip to main content

Shutting down the controller

You must shut down the controller or controllers in the chassis prior to moving them to the new chassis.

Before you begin

  • If you have a cluster with more than two controllers, check the health and Epsilon from advanced mode: cluster show -epsilon*

  • If the cluster is not in quorum or a controller that is not the degraded controller shows false for eligibility and health, correct the issue before proceeding to the next step.

  1. If Epsilon resides in the degraded controller:
    1. Remove Epsilon from the degraded controller: cluster modify -node impaired_node -epsilon false
    2. Assign Epsilon to a healthy controller in the cluster: cluster modify -node healthy_node -epsilon true
  2. If your system has two controller modules, disable the HA pair.
    If your system is running clustered ONTAP with...Then...
    Two controllers in the cluster

    cluster ha modify -configured false

    storage failover modify -node node0 -enabled false

    More than two controllers in the clusterstorage failover modify -node node0 -enabled false
  3. Halt the controller, pressing y when you are prompted to confirm the halt: system node halt -node node_name

    The confirmation message looks like the following:

    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}:
    Attention
    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 controller and start from the beginning of this procedure. If repeated attempts to cleanly shut down the controller fail, be aware that you might lose any data that was not saved to disk.
  4. Repeat the preceding step for the second controller module, if present.
    To avoid a possible quorum error message in an HA pair configuration, halt the second controller: system node halt -node second_node_name -ignore-quorum-warnings true