Skip to main content
NetApp Knowledge Base

Cluster lost quorum during back-end MetroCluster IP switch replacement

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

Applies to

  • ONTAP 9
  • MetroCluster IP
  • Back-end switch replacement
  • Out of quorum (OOQ)

Issue

  • Cluster went out of quorum during a back-end switch replacement procedure
  • CPU starvation reported at the time when ONTAP when the first switch ports were shut down:
Mon Aug 13 15:32:19 +0200 [NodeA-01: vldb: rdb.node.starvation:debug]: CPU starvation detected in the RDB.


 

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.