Skip to main content
NetApp Knowledge Base

ClusterSwitchConnectivity_Alert triggered on MetroCluster IP

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

Applies to

  • MetroCluster IP
  • AFF A250
  • Back-end switches

Issue

  • ONTAP triggering health alert for back-end switch: 
Cluster::system health alert*> show
Node:Node01
Resource:Node02
Severity:Major
Suppress:false
Acknowledge:false
Probable Cause: One or more nodes are not connected to both cluster switches.
Possible Effect: If one cluster switch fails,"nodeA1" might lose access to the cluster.
Corrective Actions: Verify that the switch "switch1" is connected to the node "node1".
 
  • Cluster configured as switchless:

cluster1::> network options switchless-cluster show

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.