Skip to main content
NetApp Knowledge Base

Azure maintenance triggers "monitor.globalStatus.critical" on CVO

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

Applies to

  • Cloud Volumes ONTAP (CVO)
  • Microsoft Azure
  • NetApp Console

Issue

  • After END Cloud Provider Maintenance Event, ONTAP System Manager of CVO reports on Events screen that the following event occurred during the maintenance:
    • monitor.globalStatus.critical: Controller failover of <node> is not possible: partner booting.
    • monitor.globalStatus.critical: Controller failover of <node> is not possible: unsynchronized log.

Note: ONTAP System Manager shows events from the past 24 hours, even when issues are resolved

  • The following event occurs shortly after the monitor.globalStatus.critical event:

monitor.globalStatus.ok: The system's global status is normal.

  • storage failover show command does not indicate any issues
  • ktls.failed:notice and object.store.unavailable evens are not reported after END Cloud Provider Maintenance Event

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.