Skip to main content
NetApp Knowledge Base

SwitchUnreachable_alert in MetroCluster IP

Views:
4
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
HW
Last Updated:

Applies to

  • ONTAP 9
  • FAS/AFF 
  • MetroCluster IP 

Issue

  • SwitchUnreachable_Alert raised on the MCC IP cluster switch

[node1: cshmd: hm.alert.raised:alert]: Alert Id = SwitchUnreachable_Alert , Alerting Resource = Switch_A1(XXXXXXX) raised by monitor ethernet-switch Issue 1 : cluster switch and cluster management IP not reachable.

  • The Cluster-interconnect switch reports it is not monitored by CSHM:

ClusterA::*> system cluster-switch show
Switch                      Type               Address          Model
--------------------------- ------------------ ---------------- ---------------
switch_A1(xxxxxxxxxxx)     cluster-network    10.1.1.111    NX3132V
     Serial Number: xxxxxxxxxxx
      Is Monitored: false 
            Reason: xxxxxxxxxxxxxxx
  Software Version: Cisco Nexus Operating System (NX-OS) Software, Version 7.0(3)I4(1)
    Version Source: CDP

  • The unmonitored switch is present in device-discovery:

::> network device-discovery show

 Node/       Local  Discovered
Protocol    Port   Device                    Interface         Platform
----------- ------ ------------------------- ----------------  ----------------
node1/cdp
            e0a    NX3132V-sw1.example.com(XXXXXXXXXXX)
                                             0/1               NX3132V
            e0b    NX3132V-sw2.example.com(XXXXXXXXXXX)
                                             0/1               NX3132V
node2/cdp
            e0a    NX3132V-sw1.example.com(XXXXXXXXXXX)
                                             0/2               NX3132V
            e0b    NX3132V-sw2.example.com(XXXXXXXXXXX)
                                             0/2               NX3132V

  • There is no answer when pings are attempted from the node-mgmt LIF of the node running the CSHM daemon to the cluster switch management IP address.
  • Cluster LIFs are able to ping the switch successfully.
  • The cluster switch management IP is properly configured.
  • Cluster ping-cluster succeeds on all paths.
  • No issues observed with the physical connectivity between the cluster switch and the management switch.

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.