Skip to main content
NetApp Knowledge Base

CONTAP-74682: ClusterSwitchConnectivity_Alert with all nodes having working paths to each switch

  1. Last updated
    Apr 2, 2025
  2. Save as PDF
Views:
255
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:
4/2/2025, 3:56:55 PM

Issue

One or more nodes reporting ClusterSwitchConnectivity_Alert events and AutoSupport messages like:
HA Group Notification (Health Monitor process cshm: ClusterSwitchConnectivity_Alert[node_name]) ALERT.

or

Call home for Health Monitor process cshm: ClusterSwitchConnectivity_Alert[node_name]
EMS message:
[node_name: cshmd: hm.alert.raised:alert]: Alert Id = ClusterSwitchConnectivity_Alert, Alerting Resource = node_name raised by monitor ethernet-switch.
All nodes have connections to both cluster switches in NetApp Active IQ AutoSupport section DEVICE-DISCOVERY (or network device-discovery show from ONTAP CLI). Example:
node_name cdp e0a cluster-switch1(FOX1234ABCD) Ethernet1/9
node_name cdp e0b cluster-switch2(FOX5678EFGH) Ethernet1/9
node_name cdp e0c cluster-switch2(FOX5678EFGH) Ethernet1/10
node_name cdp e0d cluster-switch1(FOX1234ABCD) Ethernet1/10
System healt alert output indicates an issue . Example::
::> system health alert show
Node: node_name
Resource: node_name
Severity: Major
Indication Time: Sun Dec 31 23:59:59 2023
Suppress: false
Acknowledge: false
Probable Cause: One or more nodes are not connected to both cluster
switches.
Possible Effect: If one cluster switch fails, node_name might lose
access to the cluster.
Corrective Actions: Verify that the switch switch-01.

or

::> system health alert show
Node node_name
Monitor ethernet-switch
Alert ID ClusterSwitchConnectivity_Alert
Alerting Resource node_name
Subsystem Switch-Health
Indication Time Wed Feb 14 09:47:57 2024
Perceived Severity Major
Probable Cause Configuration_error
Description The ethernet switch, with the name "switch_name", is not connected to all of the nodes in the cluster.
Corrective Actions Verify that the switch "switch_name" is connected
to the node "node_name" and that the switch's name has not
been modified due to a change in the switch's link discovery protocol used for advertisements.
Possible Effect If one cluster switch fails, "node_name" might lose access to the cluster.
Acknowledge false
Suppress false
Policy ClusterSwitchConnectivity_Policy

 

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.