Skip to main content
NetApp Knowledge Base

What are the differences between the storage failover takeover command compared to halt or reboot commands within ONTAP?

Last Updated:

Applies to

  • ONTAP 9
  • AFF Models
  • FAS Models


When using the storage failover takeover command (the preferred method), multiple checks and validations are performed to ensure a successful takeover.  If any of the checks or validations fail, the takeover is vetoed until the issue is corrected and a new takeover attempt is made.

When using the system node halt or system node reboot commands the default action in an HA pair is to perform a takeover of the node being halted or rebooted.  However, these commands assume there is are no issues that would prevent a normal nondisruptive takeover event.  The checks and validations that are normally run during a storage failover takeover are not executed here.  Thus a takeover may not complete successfully and a warning is issued with these commands noting that situation.

Sample output of a 2 node cluster:

cluster1::> system node reboot -node cluster1-01 -inhibit-takeover false

Warning: Rebooting or halting node "cluster1-01" 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 reboot node "cluster1-01"?

Sample output of a cluster with more than 2 nodes:

cluster2::> system node halt -node cluster2-04 -inhibit-takeover false

Warning: This operation will cause node "cluster2-04" 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
Do you want to continue? {y|n}:

Additional Information



NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.