Table 7. Integrated management module error messages (continued)
v Follow the suggested actions in the order in which they are listed in the Action column until the problem
is solved.
v See Chapter 4, “Parts listing, Type 7377 server,” on page 125 to determine which components are
customer replaceable units (CRU) and which components are field replaceable units (FRU).
v If an action step is preceded by “(Trained service technician only),” that step must be performed only by a
trained service technician.
Message Severity Description Action
Watchdog %1 Failed to
Capture Screen.
(%1 = OS Watchdog or
Loader Watchdog)
Error An operating-system error has
occurred, and the screen capture
failed.
1. Reconfigure the watchdog timer
to a higher value.
2. Make sure that the IMM
Ethernet over USB interface is
enabled.
3. Reinstall the RNDIS or
cdc_ether device driver for the
operating system.
4. Disable the watchdog.
5. Check the integrity of the
installed operating system.
6. Update the IMM firmware.
Important: Some cluster
solutions require specific code
levels or coordinated code
updates. If the device is part of
a cluster solution, verify that the
latest level of code is supported
for the cluster solution before
you update the code.
Watchdog %1 Screen
Capture Occurred.
(%1 = OS Watchdog or
Loader Watchdog)
Error An operating-system error has
occurred, and the screen capture
was successful.
1. Reconfigure the watchdog timer
to a higher value.
2. Make sure that the IMM
Ethernet over USB interface is
enabled.
3. Reinstall the RNDIS or
cdc_ether device driver for the
operating system.
4. Disable the watchdog.
5. Check the integrity of the
installed operating system.
Invalid or Unsupported
firmware or software was
detected on System n. (n =
system serial number)
Error IMM firmware failover has occurred
and IMM has reverted to a previous
version of the firmware.
1. Check the IBM support website
for an applicable firmware
update that applies to the rack
server.
2. Reboot IMM and verify the IMM
is running correct firmware level
after firmware update.
Chapter 3. Diagnostics 119