IBM BladeCenter JS20, Руководство по техническому обслуживанию и устранению неисправностей, Страница: 143 / 218

Service
request
number
SRN
source Description FRU/action
A12-12x G A non-critical error has been detected, an
I/O host bridge time-out error.
1. Check the BladeCenter management module
event log; if an error was recorded by the
system or if a checkpoint code is displayed on
the console, see Chapter 10,
“Symptom-to-FRU index,” on page 93.
2. If no entry is found, replace the system board.
A12-13x G A non-critical error has been detected, a
I/O host bridge address/data parity error.
1. Check the BladeCenter management module
event log; if an error was recorded by the
system or if a checkpoint code is displayed on
the console, see Chapter 10,
“Symptom-to-FRU index,” on page 93.
2. If no entry is found, replace the system board.
A12-15x G A non-critical error has been detected, a
system support function error.
1. Check the BladeCenter management module
event log; if an error was recorded by the
system or if a checkpoint code is displayed on
the console, see Chapter 10,
“Symptom-to-FRU index,” on page 93.
2. If no entry is found, replace the system board.
A12-16x G A non-critical error has been detected, a
system bus internal hardware/switch
error.
1. Check the BladeCenter management module
event log; if an error was recorded by the
system or if a checkpoint code is displayed on
the console, see Chapter 10,
“Symptom-to-FRU index,” on page 93.
2. If no entry is found, replace the system board.
A12-50x G Recoverable errors on resource indicate
a trend toward an unrecoverable error.
However, the resource could not be
deconfigured and is still in use. The
system is operating with the potential for
an unrecoverable error.
1. If repair is not immediately available, reboot
and the resource will be deconfigured;
operations can continue in a degraded mode.
2. Check the BladeCenter management module
event log for an entry around this time. If no
entry is found, replace the system board.
A13-00x G A non-critical error has been detected, a
error log analysis indicates an error
detected by the I/O device, but the failure
could not be isolated.
1. Check the BladeCenter management module
event log; if an error was recorded by the
system or if a checkpoint code is displayed on
the console, see Chapter 10,
“Symptom-to-FRU index,” on page 93.
2. If no entry is found, replace the system board.
A13-01x G A non-critical error has been detected, an
I/O bus address parity error.
1. Check the BladeCenter management module
event log; if an error was recorded by the
system or if a checkpoint code is displayed on
the console, see Chapter 10,
“Symptom-to-FRU index,” on page 93.
2. If no entry is found, replace the system board.
A13-02x G A non-critical error has been detected, an
I/O bus data parity error.
1. Check the BladeCenter management module
event log; if an error was recorded by the
system or if a checkpoint code is displayed on
the console, see Chapter 10,
“Symptom-to-FRU index,” on page 93.
2. If no entry is found, replace the system board.
Chapter 10. Symptom-to-FRU index
133