Skip to main content
NetApp Knowledge Base

CMCCTB-98: Tiebreaker monitor state is reporting incorrect state after restart

  1. Last updated
  2. Save as PDF
Views:
20
Visibility:
Public
Votes:
0
Category:
metrocluster_tiebreaker
Specialty:
metrocluster
Last Updated:

Issue

MetroCluster Tiebreaker might report an incorrect monitoring state after restarting it
If the ISLs (Intersite links) are not severed, then this bug might apply
 
Example:
MetroCluster: ClusterA
    Disaster: false
    Monitor State: All Links of cluster "ClusterA" to its DR cluster is severed
    
MetroCluster: ClusterB
    Disaster: false
    Monitor State: All Links of cluster "ClusterB" to its DR cluster is severed

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.