Skip to main content
NetApp Knowledge Base

How to halt a single node without takeover in a two-node ONTAP cluster

  1. Last updated
  2. Save as PDF
Views:
4,175
Visibility:
Public
Votes:
6
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • 2 node cluster

Description

  • In a two-node cluster, cluster HA ensures that the failure of one node does not disable the cluster.

WARNING: If you halt or reboot a node in a two-node cluster without takeover by using the -inhibit-takeover true parameter, both nodes will stop serving data unless you change specific configuration settings.
  • ONTAP will warn you if attempt to reboot or halt a node before disabling cluster HA and moving epsilon

::> sytem node reboot -node <node_name> -inhibit-takeover true
Warning: Rebooting or halting node "cluster1-01" in an HA-enabled cluster with takeover inhibited might result in a data serving failure and client disruption. To ensure
continuity of service, do the following before rebooting or halting the node. Disable cluster HA using the command: "cluster ha modify -configured false".
To transfer epsilon to the partner node, use the following commands (privilege:advanced):
 cluster modify -epsilon false -node <local-node>
 cluster modify -epsilon true -node <partner-node>
Do you want to continue? {y|n}:

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.