Skip to main content
NetApp Knowledge Base

Single node Azure CVO reboots without Azure maintenance events

  1. Last updated
    Sep 5, 2023
  2. Save as PDF
Views:
365
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
cloud
Last Updated:
9/5/2023, 4:16:20 AM

Applies to

  • Azure CVO Single Node
  • No Maintenance Events like freeze or NIC detach
  • reboot
  • Hyper-V shutdown of guest VM

Issue

  • Single node Azure CVO is not reachable for an hour and rebooted

EMS.log

Fri May 28 02:02:00 -0400 [Cluster-01: mgwd: clus.reboot.rebootDetected:notice]: Cluster reboot was detected at 01/01/2021 00:00:00. Sequence number for the cluster reboot was 5. Estimated beginning time of the cluster reboot was 01/01/2021

  • CVO was stopped and Azure activity log showed that it was stopped by Cloud Manager.

 

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.