Commands for halting or rebooting a node without initiating takeover
Inhibiting automatic storage failover takeover when halting or rebooting a node requires specific commands. If you have a two-node cluster, you must perform additional steps to ensure continuity of service.
| To prevent the partner from taking over when you... | Use this command... |
|---|---|
| Halt the node | system node halt ‑node node ‑inhibit-takeover If you have a two-node cluster, this command causes all data LIFs in the cluster to go offline unless you first disable cluster HA and then assign epsilon to the node that you intend to keep online. |
| Reboot the node Including the ‑inhibit‑takeover parameter overrides the ‑takeover‑on‑reboot setting of the partner node to prevent it from initiating takeover. | system node reboot ‑node node ‑inhibit-takeover If you have a two-node cluster, this command causes all data LIFs in the cluster to go offline unless you first disable cluster HA and then assign epsilon to the node that you intend to keep online. |
| Reboot the node By default, a node automatically takes over for its partner if the partner reboots. You can change the ‑onreboot parameter of the storage failover command to change this behavior. | storage failover modify ‑node node ‑onreboot false Takeover can still occur if the partner exceeds the user‑configurable expected time to reboot, even when the ‑onreboot parameter is set to false. |