Skip to main content

Shutting down the controller

To shut down the degraded controller, you must determine the status of the controller and, if necessary, take over the controller so that the healthy controller continues to serve data for the degraded controller’s storage.

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. Disable automatic giveback from the console of the healthy controller using the following command: storage failover modify -node local -auto-giveback false
  3. Take the degraded controller to the LOADER prompt by typing: storage failover takeover <degraded controller name> from the RJ45 Management Port of the degraded controller.
    If the degraded controller is displaying...Then...
    The LOADER promptGo to the next step.
    Waiting for giveback...

    Press Ctrl-C, and then respond y when prompted.

    System prompt or password promptTake over or halt the degraded controller:

    • Take over the degraded controller from the healthy controller: storage failover takeover -ofnode impaired_node_name

      When the degraded controller shows Waiting for giveback..., press Ctrl-C, and then respond y.

  4. If the system is in a dual-chassis HA pair, turn off the power supplies, and then unplug the degraded controller's power cords from the power source.