Skip to main content
NetApp Knowledge Base

IOM reboots after software crash

Views:
67
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

I/O module (IOM)

Issue

 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

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

 

  • Was this article helpful?