Skip to main content
NetApp Knowledge Base

Single Node CVO reboots without any planned maintenance events

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

Applies to

  • Amazon Web Services (AWS)
  • Google Cloud Platform (GCP)
  • No scheduled maintenance events
  • Reboot

Issue

  • Single node AWS CVO is not reachable for a few minutes and it rebooted.

EMS.log:

Sat Feb 24 22:38:56 +0000 [cluster01-01: mgwd: clus.reboot.rebootDetected:notice]: Cluster reboot was detected at X/24/20XX 22:XX:XX. Sequence number for the cluster reboot was XX. Estimated beginning time of the cluster reboot was X/24/20XX 22:XX:XX.

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.