IOM reboots after software crash
- Views:
- 1,012
- Visibility:
- Public
- Votes:
- 0
- Category:
- fas-systems
- Specialty:
- hw
- Last Updated:
- 9/6/2024, 9:08:22 AM
Applies to
- ONTAP 9
- I/O module (IOM)
Issue
- EMS shows:
Thu Aug 15 22:47:49 +0900 [Node-01: storlog_admin: sla.shelf.message:debug]: params: {'type': 'SEVERITY', 'log': 'Thu Jan 1 00:00:00 1970 ( 0+00:00:00.498); 02000093; U?; HAL; hal; 04; Module Reboot: Startup type 5-Crash reset'}
Thu Aug 15 22:47:49 +0900 [Node-01: storlog_admin: sla.shelf.message:debug]: params: {'type': 'SEVERITY', 'log': 'Thu Jan 1 00:00:00 1970 ( 0+00:00:00.705); 0200013D; U?; HAL; hal; 02; Failure info:Client "i2cTransport 0" triggered wdg. tNow:144134120, tLast:144054059, interval:80000, failed:0'}
- Messages displayed in
SHELF-LOG-IOM.GZ:
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.496); 02000027; U?; HAL; hal; 04; NDU Data Invalid.
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.496); 02000093; U?; HAL; hal; 04; Module Reboot: Startup type 5-Crash reset
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.496); 02000186; U?; HAL; hal; 04; Module Reboot: Latched power registers - EBOD = EF, ACP = EF
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.496); 0200011E; U?; HAL; hal; 02; Canister CPLD POST passed
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.496); 02000120; U?; HAL; hal; 02; Canister CPLD: V24
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.677); 01000001; U?; CLI; cli; 02; Failed to bind CLI command: gpio_set_bit, status 4
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.704); 0200013C; U?; HAL; hal; 02; Reboot after software crash.
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.705); 0200013D; U?; HAL; hal; 02; Failure info:Cause: 10800408, PC: 5c13170c, . Thread i2cipcwork 3
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.705); 0200013E; U?; HAL; hal; 02; Failed firmware version: 0120, Code Image A
Thu Jan 1 00:00:00 1970 ( 0+00:00:00.705); 020001E3; U?; HAL; hal; 02; Sideband CPLD: V11
