Skip to main content
NetApp Knowledge Base

ClusterSwitchConfig_Alert reported in system health alert for non-existing switch

Views:
1,069
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
hw
Last Updated:
6/2/2025, 11:49:30 AM

Applies to

  • ONTAP 9
  • Cluster Switch Health Monitor (CSHM) AutoSupport message

Issue

  • Subsystem health for switch gets degraded:

cluster1::> system health subsystem show
Subsystem         Health
----------------- ------------------
SAS-connect       ok
Environment       ok
Memory            ok
Service-Processor ok
Switch-Health     degraded
CIFS-NDO          ok
Motherboard       ok
IO                ok
MetroCluster      ok
MetroCluster_Node ok
FHM-Switch        ok
FHM-Bridge        ok
SAS-connect_Cluster ok

  • EMS reports one or more of the following health alerts:
[Node_01: cshmd: hm.alert.raised:alert]: Alert Id = SwitchUnreachable_Alert , Alerting Resource = SW1(FOCXXXXXXXX)
raised by monitor ethernet-switch
[Node_01: cshmd: hm.alert.raised:alert]: Alert Id = ClusterSwitchConfig_Alert , Alerting Resource = node_01 raised by monitor cluster-switch
[Node_01: cshmd: hm.alert.raised:alert]: Alert Id = SwitchCommunityString_Alert , Alerting Resource = SW1 raised by monitor cluster-switch
  • Output of system health alert show similarly shows one or more of the following:

               Node: node-01
           Alert ID: SwitchUnreachable_Alert
           Resource: sw1
     Probable Cause: The ethernet switch's IP address is not reachable from
                     the local node.
    Possible Effect: Monitoring of the switch and log collection will not
                     function.
Corrective Actions: Ensure that the IP address is reachable or specify the
                     correct reachable IP address.

               Node: node-01
           Alert ID: ClusterSwitchConfig_Alert
           Resource: node-01
     Probable Cause: One or more nodes are not connected to both cluster
                     switches.
    Possible Effect: If one cluster switch fails, "node0-1" might lose
                     access to the cluster.
Corrective Actions: Ensure the switch "sw1" is connected
                     to the node "node-01".

               Node: node-01
           Alert ID: SwitchCommunityString_Alert
           Resource: sw1
     Probable Cause: Cluster switch "sw1" with IP address
                     "123.123.123.123" is not reachable via SNMP. Incorrect
                     SNMP community string might be configured on the
                     cluster switch.
    Possible Effect: Cluster switch communication problems and
                     accessibility issues.
Corrective Actions: Check the SNMP community string on the cluster switch
                     to verify the expected community string is configured.
                     Use the "system cluster-switch show -snmp-config"
                     command to view the expected community string.

  • The switch name and IP address in the alert do not belong to any cluster switches or is reported in the case of a switchless cluster.
  • Command system switch ethernet show is blank or unknown or reports switches with IP address not reachable.
  • Deleting the health alert does not resolve the issue.

 

 

 

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.