Skip to main content
NetApp Knowledge Base

CVO Takeover initiated after no heartbeat was detected from the partner node

  1. Last updated
  2. Save as PDF
Views:
594
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • Cloud Volumes ONTAP (CVO)
  • Amazon Web Services (AWS)
  • Microsoft Azure
  • Google Cloud Platform (GCP)
  • Unexplained takeovers with no Network Partitioning error logs

Issue

One or Both CVO nodes go down after reporting loss of heartbeats to the partner:

kltp: clam.heartbeat.state.change:INFO]: Heartbeats to node (name=cluster01-02, ID=1001lu) are Failing.

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.