Handling L2 Watchdog Resets on the FAS3250
This knowledge base was generated through a script and may contain formatting issues. For the accurate content, please refer to the WIP editor. WIP editor.
Applies to
- FAS3250
Issue
- Node does not reboot after an unexpected shutdown and BMC logs on the impacted node show the following:
Record 2523: Mon Jul 22 11:37:21 2024 [IPMI Event.critical]: L2 watchdog timeout hard reset
Record 2524: Mon Jul 22 11:37:21 2024 [Trap Event.critical]: hwassist l2_watchdog_reset (29)
Record 2525: Mon Jul 22 11:37:21 2024 [IPMI Event.critical]: System reset
Record 2526: Mon Jul 22 11:37:21 2024 [IPMI Event.critical]: L2 watchdog action completed
Record 2527: Mon Jul 22 11:37:21 2024 [IPMI.notice]: L2 to L1 is 1(s) 111429(us)
Record 2528: Mon Jul 22 11:37:22 2024 [IPMI.notice]: 5201 | 02 | EVT: 6fc104ff | System_Watchdog | Assertion Event, "Hard reset"
Record 2529: Mon Jul 22 11:37:30 2024 [SP.notice]: Delaying L2_WDOG ASUP email for 120 seconds
Record 2530: Mon Jul 22 11:39:35 2024 [ASUP.notice]: First notification email | (REBOOT (watchdog reset)) CRITICAL | Sent
Record 2531: Mon Jul 22 11:48:33 2024 [SP.critical]: Heartbeat stopped
Record 2532: Mon Jul 22 11:52:25 2024 [ASUP.notice]: Reminder email | (REBOOT (watchdog reset)) CRITICAL | Sent