Error Code Description
Action/
Possible Failing FRU
M0SC SI01 Unable to load diagnostics. This error code is
generated by the customer performing “Problem
Determination” as described in the
Eserver
pSeries 670 User’s Guide
.
Go to “MAP 1542: I/O Problem Isolation” on
page 261.
Hypervisor Dump Retrieval Procedure
This procedure defines the requirements and methods for retrieving a hypervisor dump file following a
system crash. This procedure is applicable only if the managed system had been running as a partitioned
system before it crashed.
This procedure requires the managed system to be rebooted as a partitioned system. Retrieval must then
take place from an AIX partition.
Hypervisor Dump Indications
If the system operator panel displays error code 20D00997, 20D00998, or 20D00999, a system crash
within the run-time firmware has occurred.
If error code 20D00997, 20D00998, or 20D00999 is in the service processor error log, a system crash
within the run-time firmware has occurred. The following is an example of a detailed service processor
error log entry with error code 20D00999:
05/29/2001 21:06:12
Operating System Terminated with Error String
Error code: 20D00999
Detail:
A2C1
SRC
--------------------------------------------------------------
word11: B1194690
word12: 04A0005D
word13: A2C1C0FA
word14: 00000000
word15: 00007701
word16: 00000008
word17: 00000000
word18: 00000000
word19: 00000000
20D00999
After a system crash has occurred, verify if a hypervisor dump has been collected, as described in the
following section.
Retrieving the Hypervisor Dump file
After it has been determined that the managed system has crashed and a hypervisor dump exists, or if the
user wants to test for an existing dump file, the managed system must be rebooted as a partitioned
system. A partition or partitions running AIX must then be activated. After rebooting, any partition running
AIX may be used to retrieve the dump file. Do the following:
1. Install the
devices.chrp_lpar.base.ras
fileset.
The
devices.chrp_lpar.base.ras
AIX fileset must be installed and committed. To determine if the
package has been previously installed, enter the following command on the AIX command line:
lslpp -l | grep devices.chrp_lpar.base.ras
If the output on the AIX console is similar to the following, the
devices.chrp_lpar.base.ras
fileset is
already installed and no further action for step 1 is necessary:
devices.chrp_lpar.base.ras
5.X.X.X COMMITTED CHRP LPAR RAS Support
If no output is returned, the
devices.chrp_lpar.base
LPP must be installed from the AIX installation
media by the customer or system administrator.
696
Eserver
pSeries 670 Service Guide
Summary of Contents for pSeries 670
Page 1: ...pSeries 670 Service Guide SA38 0615 03 ERserver...
Page 2: ......
Page 3: ...pSeries 670 Service Guide SA38 0615 03 ERserver...
Page 12: ...x Eserver pSeries 670 Service Guide...
Page 16: ...xiv Eserver pSeries 670 Service Guide...
Page 18: ...xvi Eserver pSeries 670 Service Guide...
Page 324: ...Yes Go to Step 154A 14 on page 302 304 Eserver pSeries 670 Service Guide...
Page 718: ...698 Eserver pSeries 670 Service Guide...
Page 848: ...L3 Cache Shorts Test Step 4 828 Eserver pSeries 670 Service Guide...
Page 849: ...L3 Cache Shorts Test Step 5 Chapter 9 Removal and Replacement Procedures 829...
Page 851: ...L3 Cache Shorts Test Step 2 Chapter 9 Removal and Replacement Procedures 831...
Page 853: ...L3 Cache Shorts Test Step 4 Chapter 9 Removal and Replacement Procedures 833...
Page 854: ...L3 Cache Shorts Test Step 5 834 Eserver pSeries 670 Service Guide...
Page 971: ...7040 Model 671 Media Subsystem 1 2 3 4 5 6 7 8 9 10 Chapter 10 Parts Information 951...
Page 973: ...Power and SCSI Cables to the Media Subsystem 1 2 3 5 4 6 Chapter 10 Parts Information 953...
Page 986: ...966 Eserver pSeries 670 Service Guide...
Page 990: ...970 Eserver pSeries 670 Service Guide...
Page 1018: ...998 Eserver pSeries 670 Service Guide...
Page 1020: ...1000 Eserver pSeries 670 Service Guide...
Page 1028: ...1008 Eserver pSeries 670 Service Guide...
Page 1031: ......