Skip to main content
NetApp Knowledge Base

CVO in GCP environment reboots due to heartbeat loss

Views:
247
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:

Applies to

  • NetApp Cloud Volumes ONTAP (CVO)
  • High Availability (HA)
  • Google Cloud Provider (GCP)
  • Event Management System (EMS)

Issue

  • CVO VM reboots unexpectedly
  • EMS logs show the following message:
    • cf_main: cf.fsm.takeover.noheartbeat:ALERT]: Failover monitor: Takeover initiated  after no heartbeat was detected from  the partner node.
  • GCP log query show compute.instance.hostError and compute.instance.automaticRestart messages

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.