ONTAP reports that a cluster switch has rebooted, when the switch did not reboot
Applies to
- ONTAP 9.0 through ONTAP 9.5
- Cisco Nexus Cluster Switches
Issue
ONTAP generates an alert indicating that a cluster switch has rebooted.
Cluster::*> system health alert show -alert-id SwitchReboot_Alert
Node: Cluster-01
Resource: clussw1(FOX0000ZZZZ)
Severity: Minor
Indication Time: Wed Jan 2 00:00:00 2019
Suppress: false
Acknowledge: false
Probable Cause: The cluster switch "clussw1(FOX0000ZZZZ)" has
recently rebooted.
Possible Effect: Communication problems and cluster connectivity issues
might occur.
Corrective Actions: 1) If the cluster switch was not rebooted on purpose, then
check the switch to ensure that it is operating normally.
2) If errors persist, contact technical support for
further assistance.
Wed Jan 2 00:00:00 UTC [Cluster-01: cshmd: hm.alert.raised:alert]: Alert Id = SwitchReboot_Alert , Alerting Resource = clussw1(FOX0000ZZZZ) raised by monitor cluster-switch
Wed Jan 2 00:05:00 UTC [Cluster-01: cshmd: hm.alert.cleared:notice]: Alert Id = SwitchReboot_Alert , Alerting Resource = clussw1(FOX0000ZZZZ) cleared by monitor cluster-switch
The cluster switch shows no evidence of a reboot and the uptime confirms that no switch reboot occurred.
clussw1# show system uptime
System start time: Thu Dec 1 00:00:00 2017
System uptime: 397 days, 11 hours, 6 minutes, 51 seconds
Kernel uptime: 397 days, 11 hours, 8 minutes, 41 seconds
Active supervisor uptime: 397 days, 11 hours, 6 minutes, 51 seconds
clussw1# show version | include uptime
Kernel uptime is 397 day(s), 11 hour(s), 8 minute(s), 43 second(s)