IBM JS20 - BladeCenter - 8842 Maintenance And Troubleshooting Manual

Also see for BladeCenter JS20: Configuration and options guide Installation and user guide Installation and user guide

Contents

ServicerequestnumberSRNsource Description FRU/actionA12-12x G A non-critical error has been detected, anI/O host bridge time-out error. 1. Check the BladeCenter management moduleevent log; if an error was recorded by thesystem or if a checkpoint code is displayed onthe 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, aI/O host bridge address/data parity error. 1. Check the BladeCenter management moduleevent log; if an error was recorded by thesystem or if a checkpoint code is displayed onthe 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, asystem support function error. 1. Check the BladeCenter management moduleevent log; if an error was recorded by thesystem or if a checkpoint code is displayed onthe 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, asystem bus internal hardware/switcherror.1. Check the BladeCenter management moduleevent log; if an error was recorded by thesystem or if a checkpoint code is displayed onthe 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 indicatea trend toward an unrecoverable error.However, the resource could not bedeconfigured and is still in use. Thesystem is operating with the potential foran unrecoverable error.1. If repair is not immediately available, rebootand the resource will be deconfigured;operations can continue in a degraded mode.2. Check the BladeCenter management moduleevent log for an entry around this time. If noentry is found, replace the system board.A13-00x G A non-critical error has been detected, aerror log analysis indicates an errordetected by the I/O device, but the failurecould not be isolated.1. Check the BladeCenter management moduleevent log; if an error was recorded by thesystem or if a checkpoint code is displayed onthe 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, anI/O bus address parity error. 1. Check the BladeCenter management moduleevent log; if an error was recorded by thesystem or if a checkpoint code is displayed onthe 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, anI/O bus data parity error. 1. Check the BladeCenter management moduleevent log; if an error was recorded by thesystem or if a checkpoint code is displayed onthe 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