Skip to main content

Coming soon...New Support-Specific categorization of Knowledge Articles in the NetApp Knowledge Base site to improve navigation, searchability and your self-service journey.

NetApp Knowledge Base

Cisco Nexus 5596 Cluster switch reboots and is hung

Views:
89
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • Cisco Nexus 5596 cluster switches
  • ONTAP 9
  • AFF/FAS

Issue

  • Cisco Nexus 5596 switch reboots and the following alerts are seen in event logs:

[Node-1: cshmd: hm.alert.raised:alert]: Alert Id = SwitchIfIslDownWarn_Alert , Alerting Resource = sw01(XXXXXXXXXX)/port-channel1 raised
[Node-1: cshmd: hm.alert.raised:alert]: Alert Id = ClusterSwitchMissing_Alert , Alerting Resource = Node-1 raised by monitor cluster-switch].
[Node-1: mgwd: callhome.hm.alert.major:alert]: Call home for Health Monitor process cshm: ClusterSwitchMissing_Alert[Node-1 by monitor cluster-switch]

  • The switch boots up only after a power cycle and after the reboot, ClusterSwitchMissing_Alert is cleared:

[Node-1: cshmd: hm.alert.raised:alert]: Alert Id = SwitchReboot_Alert , Alerting Resource = sw02(XXXXXXXXX) raised by monitor cluster-switch
[Node-1: cshmd: hm.alert.cleared:notice]: Alert Id = ClusterSwitchMissing_Alert , Alerting Resource = Node-1 cleared by monitor cluster-switch
[Node-1: cshmd: hm.alert.cleared:notice]: Alert Id = SwitchReboot_Alert , Alerting Resource = sw02(XXXXXXXXX) cleared by monitor cluster-switch

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device