IBM JS20 Hardware Maintenance Manual - Page 135
IBM JS20 - BladeCenter - 8842 Manual
UPC - 000435230263
View all IBM JS20 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 135 highlights
Service request number A03-13x SRN source Description G I/O Expansion bus parity error. A03-14x G I/O Expansion bus time-out error. A03-15x G I/O Expansion bus connection failure. A03-16x G I/O Expansion unit not in an operating state. A05-00x G Error log analysis indicates an environmental and power warning, but the failure could not be isolated. A05-01x G Sensor indicates a fan has failed. A05-02x G System shutdown due to a fan failure. A05-03x G Sensor indicates a voltage outside normal range. FRU/action 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. 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. 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. 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. 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. 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. 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. 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 125