IBM JS20 Hardware Maintenance Manual - Page 139
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 139 highlights
Service request number A0D-24x A0D-31x A0D-35x A0D-36x A0D-37x A0D-38x A0D-40x A10-100 SRN source Description FRU/action G Service Processor detected a surveillance time-out. 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. G Error detected while handling an attention/interrupt from the system hardware. 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. G Mainstore or Cache IPL Diagnostic 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. G Other IPL Diagnostic 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. G Clock or PLL 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. G Hardware Scan or Initialization 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. G FRU Presence/Detect Error (Mis-Plugged). 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. E The resource is unavailable due to an 1. Check the BladeCenter management module error. System is operating in degraded event log; if an error was recorded by the mode. 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 129