Handling L2 Watchdog Resets on the FAS90 / FAS70 / ASA A1K / ASA A90 / ASA A70 / AFF A1K / AFF A90 / AFF A70 / AFF C80
Applies to
- ONTAP 9
- FAS90, FAS70
- ASA A1K, ASA A90, ASA A70
- AFF A1K, AFF A90, AFF A70, AFF C80
Issue
- Node reboots unexpectedly.
- Node does not reboot after an unexpected shutdown.
- BMC
events all
output on the impacted node shows the following:
Record 499: Wed Apr 02 23:02:34.264247 2025 [IPMI.notice]: 01aa | 02 | EVT: 6fc824ff | System_Watchdog | Assertion Event, "Timer interrupt"
Record 500: Wed Apr 02 23:02:34.646754 2025 [IPMI Event.critical]: NMI
Record 501: Wed Apr 02 23:02:34.651210 2025 [IPMI.notice]: 01ab | 02 | EVT: 6f00ffff | CriticalInt | Assertion Event, "NMI/Diag Interrupt"
Record 502: Wed Apr 02 23:02:35.492102 2025 [IPMI.notice]: 01ac | 02 | EVT: 6fc124ff | System_Watchdog | Assertion Event, "Hard reset"
Record 503: Wed Apr 02 23:02:35.624499 2025 [IPMI Event.critical]: L2 watchdog timeout hard reset
Record 504: Wed Apr 02 23:02:35.655394 2025 [IPMI Event.critical]: System reset
- If node reboots, the following error can be seen in the EMS log files:
[cluster-01:mgr.boot.reason_abnormal:EMERGENCY]: System rebooted due to a watchdog reset.