Handling L2 Watchdog Resets on the AFF A250 / FAS500f / AFF C250
- Views:
- 1,422
- Visibility:
- Public
- Votes:
- 0
- Category:
- aff-series
- Specialty:
- HW
- Last Updated:
- 1/30/2025, 4:01:47 PM
Applies to
- AFF A250 / FAS500f / AFF C250
Issue
- Node reboots unexpectedly with panic below
watchdog nmi on cpu 2, hang cpu is -1 in process idle: cpu2 208 |XXX | 12:57:16 | Watchdog 2 #0x0f | Timer interrupt | Asserted
- Node does not reboot after an unexpected shutdown and BMC logs on the impacted node show the following:
Record 402: Thu May 05 06:20:35.070000 2022 [ASUP.notice]: First notification email | (REBOOT (abnormal)) WARNING | Send failed
Record 403: Thu May 05 06:20:40.640000 2022 [IPMI.notice]: 0076 | 02 | EVT: 6fc302ff | System_Watchdog | Assertion Event, "Power cycle"
Record 404: Thu May 05 06:20:40.640000 2022 [IPMI Event.critical]: L2 watchdog timeout power cycle
- If node reboots, the following error can be seen in the EMS log files
Thu May 05 15:33:43 +0800 [netapp: splog_main: mgr.boot.reason_abnormal:EMERGENCY]: System rebooted due to a watchdog reset.
Thu May 05 15:33:43 +0800 [netapp: splog_main: callhome.reboot.watchdog:alert]: Call home for REBOOT (watchdog reset)
