friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzait_5.4.0.1/rzaitsrclist.htm

799 lines
42 KiB
HTML
Raw Permalink Blame History

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="System reference codes (SRCs) for logical partitions" />
<meta name="abstract" content="Find a list that contains the common SRCs that the PAL can report." />
<meta name="description" content="Find a list that contains the common SRCs that the PAL can report." />
<meta name="DC.Relation" scheme="URI" content="rzaittroubleshootoverview.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaitpal.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaitsecurepar.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaitsecurepar.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaitsecurepar.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaitsecurepar.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaitsecurepar.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzahg/rzahgictroub2.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaitsrclist" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>System reference codes (SRCs) for logical partitions</title>
</head>
<body id="rzaitsrclist"><a name="rzaitsrclist"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">System reference codes (SRCs) for logical partitions</h1>
<div><p>Find a list that contains the common SRCs that the PAL can report.</p>
<p>The following table contains the common SRCs that the PAL can report. Suggested
corrective actions follow each SRC. If an SRC is not listed, it might not
be related to logical partitions. </p>
<div class="note"><span class="notetitle">Note:</span> In the following table, the xx numbers in the SRC codes equal the partition
ID.</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Common SRCs that the PAL can report</caption><thead align="left"><tr valign="bottom"><th valign="bottom" id="d0e27">SRC</th>
<th valign="bottom" id="d0e29">Information</th>
</tr>
</thead>
<tbody><tr><td valign="top" headers="d0e27 ">1 B2xx 1230</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The secondary partition could not
perform the IPL. The IPL is ended. An example of what causes this SRC to appear
is not assigning the correct amount of processors or memory to a secondary
partition.</p>
<p><span class="uicontrol">Recovery:</span> From the Work With System
Partitions display, correct the configuration problem based on the reason
code, then try the secondary partition's IPL again. If it continues to fail,
contact your service provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Identify
the reason code from word 3 of the SRC. Possible reason code values are the
following:</p>
<ul><li>000000A2: Insufficient amount of interactive performance</li>
<li>000000A3: Insufficient number of processors</li>
<li>000000A4: Insufficient main storage size</li>
</ul>
<p>For any other reason code, contact your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 1250</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The primary partition's IPL mode does
not allow the secondary partition to IPL the given mode. The IPL is ended.
An example of what causes this SRC to appear is the primary partition is in
C-mode IPL and the secondary partition is B-mode IPL. When the primary partition
is in a D-mode IPL, the secondary partitions are not allowed to IPL at all.</p>
<p><span class="uicontrol">Recovery:</span> Go
to the Work With System Partitions display and assign the secondary partitions
the same IPL mode as the primary partition. Then, try the secondary partition
IPL again. If the problem continues to fail, contact your service provider.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Collect the detailed hexadecimal data from
the product activity log (PAL) entry for this problem.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 1260</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The Timed Power On (TPO) setting was
reached for a secondary partition, but the keylock was not set to Automatic
or Normal. The IPL will end.</p>
<p><span class="uicontrol">Recovery:</span> Go to
the Work With System Partitions display and change the keylock from its current
setting of Manual-Secure to Normal- Automatic. Then, try the secondary partition
IPL again. If the problem continues to fail, contact your service provider.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Collect the detailed hexadecimal data from
the product activity log (PAL) entry for this problem.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 1310</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> No alternate (D-mode) IPL device IOP
selected. The IPL will attempt to continue, but there might not be enough
information to find the correct D-mode load source.</p>
<p><span class="uicontrol">Recovery:</span> Go
to the Work With System Partitions display and configure an alternate IPL
IOP for the secondary partition. Then, try the secondary partition IPL again.
If it continues to fail, contact your service provider.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Collect the detailed hexadecimal data from
the product activity log (PAL) for this problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 1320</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> No default load source IOP selected
for an A-mode or a B-mode IPL. The IPL will attempt to continue, but there
might not be enough information to find the correct load source.</p>
<p><span class="uicontrol">Recovery:</span> Go
to the Work With System Partitions display and configure a load source IOP
for the secondary partition. Then, try the secondary partition IPL again.
If it continues to fail, contact your service provider.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Collect the detailed hexadecimal data from
the product activity log (PAL) for this problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 3110</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> All load source candidates have been
scanned for valid secondary partition code. However, in all cases, errors
were encountered that prevented each from being used as a load source candidate
for the IPL. The IPL is ended.</p>
<p><span class="uicontrol">Recovery:</span> Address
each problem found, and then try the secondary partition's IPL again. If it
continues to fail, contact your service provider.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Scan the secondary partition's SRC history
list for prior B2ppxxxx failure SRCs (where pp is the partition ID) to pinpoint
the source of the problem.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 3123</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The IOA slot does not belong to the
IOP. A check is made to the specific IOP to ensure an IOA slot has been assigned
to it. This SRC indicates that no IOA slot has been assigned to an IOP, and
hence all unit addresses under this slot will not be attempted. The IPL will
attempt to continue by skipping to the next slot address.</p>
<p><span class="uicontrol">Recovery:</span> This
SRC probably indicates a LPAR configuration error. Use the Work with Partitions
display to check your partition configuration to ensure that all the slots
are allocated to the partition correctly.</p>
<p><span class="uicontrol">Problem analysis
procedure:</span> Use the product activity log (PAL) to find SRCs that
pertain to the device address referenced in words 13-16 of the SRC. Correct
any problems found, and then retry the secondary IPL.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 3125</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Memory allocation for early IPL objects
failed. The primary is low on memory. The IPL sequence will be retried to
the same device.</p>
<p><span class="uicontrol">Recovery:</span> If the primary partition
does not have enough main storage, remove some main storage from one or more
secondary partitions, then add it to the primary partition. If the primary
partition does have enough main storage, try the IPL again. If it continues
to fail, contact your service provider.</p>
<p><span class="uicontrol">Problem analysis
procedure:</span> Ensure that the primary partition has an adequate amount
of main storage available to perform the IPL of the secondary partition.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 3130</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> No bus object was found for the specified
bus number. The IPL will attempt to continue, but all subsequent load source
devices at this bus address will be skipped.</p>
<p><span class="uicontrol">Recovery:</span> If
word 3 is zero, then is SRC is informational and can be ignored. A nonzero
bus number has no associated bus object. Contact your service provider to
resolve the issue.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> The
value for word 3 is as follows:</p>
<ul><li>Word 3: Bus address information</li>
</ul>
<p>This value can help you to identify the hardware that caused the error.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 3135</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The Transport Manager bus object type
is neither SPD nor PCI. The only known bus types are RIO, SAN, and Virtual
and none of these support the IPL mode as an LPAR load source. The entire
bus will be skipped. The IPL will attempt to continue.</p>
<p><span class="uicontrol">Recovery:</span> Contact
your service provider to resolve the issue.</p>
<p><span class="uicontrol">Problem analysis
procedure:</span> The value for word 3 is as follows:</p>
<ul><li>Word 3: Bus address information</li>
</ul>
<p>This value can help you to identify the hardware that caused the error.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 3200</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The command (Initiate Self Load) sent
to the IOP telling it to locate the selected load source device and load or
reset itself has failed. The IPL will attempt to continue, and depending on
the type of failure, the load source device can be retried or skipped.</p>
<p><span class="uicontrol">Recovery:</span> Look
for SRCs in the PAL relating to the device location specified in words 3-6.
Follow the recovery actions for problems found. Then, try the secondary partition
IPL again. If it continues to fail, contact your service provider.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> The values for words 3-6 are as follows:</p>
<ul><li>Word 3: Bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
<li>Word 6: Unit address information</li>
</ul>
<p>These values can help you to identify the hardware that caused the
error.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 4310</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The load source device hardware drive
has no HRI object. The IPL will attempt to try the entire IPL sequence from
the specified load source again.</p>
<p><span class="uicontrol">Recovery:</span> If
your IPL failed due to this SRC, capture a primary partition MSD and contact
your service provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> The
value for word 3 is as follows:</p>
<ul><li>Word 3: Bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
<li>Word 6: Unit address information</li>
</ul>
<p>This value can help you to identify the hardware that caused the error.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 4312</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A mismatch has occurred between the
expected load source candidate device's logical device location and the enlisted
load source candidate device. The IPL will attempt to try the entire IPL sequence
from the specified load source again.</p>
<p><span class="uicontrol">Recovery:</span> If
your IPL failed due to this SRC, capture a primary partition MSD and contact
your service provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> The
value for word 3 is as follows:</p>
<ul><li>Word 3: Bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
<li>Word 6: Unit address information</li>
</ul>
<p>This value can help you to identify the hardware that caused the error.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 4315</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A failure occurred when attempting
to allocate storage in the primary partition.</p>
<p><span class="uicontrol">Recovery:</span> If
the primary partition does not have enough main storage, remove some main
storage from one or more secondary partitions, then add it to the primary
partition.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Ensure
the primary partition has an adequate amount of memory. Try the secondary
partition IPL again.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 4320</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The wrong kind of primary load source
reported. The IPL will attempt to proceed by skipping all subsequent attempts
to this device.</p>
<p><span class="uicontrol">Recovery:</span> Verify your hardware
configuration for the secondary partition.</p>
<p><span class="uicontrol">Problem analysis
procedure:</span> Ensure that the devices are located in the correct
location.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 4321</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The wrong kind of alternate load source
reported. The IPL will attempt to continue by skipping all subsequent attempts
to this device.</p>
<p><span class="uicontrol">Recovery:</span> Verify your hardware
configuration for the secondary partition.</p>
<p><span class="uicontrol">Problem analysis
procedure:</span> Ensure that the devices are located in the correct
slot.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 5106</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Creation of main storage dump-temporary
segment has failed. An example of what causes this failure is running out
of memory in the primary partition. The IPL will be retried to the same device
unit address, under the assumption that this is a temporary condition.</p>
<p><span class="uicontrol">Recovery:</span> If
the primary partition does not have enough main storage, remove some main
storage from one or more secondary partitions, then add it to the primary
partition. If the primary partition does have enough main storage, try the
IPL again. If it continues to fail, contact your service provider.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Ensure that the primary partition has an adequate
amount of main storage available to perform the IPL of the secondary partitions.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 5114</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The secondary load source has allocated
a MSD that is smaller than the minimum dump size. No dump can be captured.
The IPL will end.</p>
<p><span class="uicontrol">Recovery:</span> Contact your service
provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) entry for
this problem. Contact your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 5115</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Loading form the load source has failed.
The IPL will attempt to continue by trying the entire IPL sequence to the
same load source device again.</p>
<p><span class="uicontrol">Recovery:</span> If this
SRC is preventing the secondary IPL from continuing, focus on the load source
device at the location specified in words 3-6. Try the secondary partition's
IPL again, after fixing any problems found.</p>
<p><span class="uicontrol">Problem analysis
procedure:</span> These values for words 3-6 is as follows:</p>
<ul><li>Word 3: Bus information</li>
<li>Word 4: Board information</li>
<li>Word 5: Card information</li>
<li>Word 6: Unit information</li>
</ul>
<p>These values can help you to identify the hardware that caused the
error.</p>
<p>Collect the detailed hexadecimal data from the product activity
log (PAL) for this problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 5117</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> An MSD or CPM IPL has occurred, but
the current information cannot be written to the load source device because
a valid dump already exists. The current MSD or CPM information is lost, and
the IPL is ended.</p>
<p><span class="uicontrol">Recovery:</span> Perform the IPL of
the secondary partition past dedicated service tools (DST) to invalidate the
old MSD or CPM information on the load source. Then, subsequent MSD or CPM
dumps can be saved.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Identify
the partition that has the problem through the partition identification number
(xx) given in the SRC.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 5121</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> An MSD or CPM IPL has occurred, but
the current information cannot be written to the load source device because
a valid dump already exists. The current MSD or CPM information is lost, and
the IPL is ended.</p>
<p><span class="uicontrol">Recovery:</span> Perform the IPL of
the secondary partition past dedicated service tools (DST) to invalidate the
old MSD or CPM information on the load source. Then, subsequent MSD or CPM
dumps can be saved.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) and fix
any problems found.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 5135</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A disk unit write operation has failed
during the writing of MSD or CPM mainstore pages. A partial dump of phase
II information might be available in the dump and the MSD or CPM IPL will
continue.</p>
<p><span class="uicontrol">Recovery:</span> Collect the detailed hexadecimal
data from the product activity log (PAL) associated with the disk unit at
the given location. Fix any potential problems found. This can be a sign of
a disk unit, IOP, or Bus problem that needs to be fixed.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Identify the reason code from words 3-9 of
the SRC. Possible reason code values are the following:</p>
<ul><li>Word 3: bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
<li>Word 6: Unit address information</li>
<li>Word 7: Number of pages written in the operation</li>
<li>Word 8: Device page position</li>
<li>Word 9: DASD hardware driver return code</li>
</ul>
<p>For any other reason code, contact your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 5145</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Storing SID 82 LIDs during Phase II
for the MSD or CPM path has failed. Phase II information will most likely
not be available in the dump and the MSD or CPM IPL will continue.</p>
<p><span class="uicontrol">Recovery:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) associated
with the disk unit at the given location. Fix any potential problems found.
This can be a sign of a disk unit, IOP, or Bus problem that needs to be fixed.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Identify the reason code from words 3-6 of
the SRC. Possible reason code values are the following:</p>
<ul><li>Word 3: bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
<li>Word 6: Unit address information</li>
</ul>
<p>For any other reason code, contact your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 5148</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A MSD occurred while the system was
already performing a MSD or CPM recovery IPL. The first dump has already been
copied or cleared. The second dump has been successfully saved into the secondary
load source's SID 82, but he secondary partition will not IPL.</p>
<p><span class="uicontrol">Recovery:</span> Contact
your service provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Identify
the reason code from words 3-6 of the SRC. Possible reason code values are
the following:</p>
<ul><li>Word 3: bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
<li>Word 6: Unit address information</li>
</ul>
<p>For any other reason code, contact your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 6012</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A secondary partition LID has been
loaded into the partition's main storage successfully. However, it has been
determined afterward that the actual LID was not fully contained in the partition's
load area, and memory damage or corruption has potentially occurred. The IPL
will be terminated.</p>
<p><span class="uicontrol">Recovery:</span> Contact your service
provider. The secondary partition's load source device is corrupt. A reinstall
might be necessary if the load source is DASD.</p>
<p><span class="uicontrol">Problem analysis
procedure:</span> Identify the reason code from words 3-6 of the SRC.
Possible reason code values are the following:</p>
<ul><li>Word 3: bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
<li>Word 6: Unit address information</li>
</ul>
<p>For any other reason code, contact your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 6015</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Getting the partition's load data
area failed. The IPL will attempt to continue by skipping this device, and
trying a subsequent load source candidate device.</p>
<p><span class="uicontrol">Recovery:</span> This
is likely a problem with the load source media being corrupt or not valid.
A re-installation of the Licensed Internal Code of the secondary partition
is probably required to recover. If it continues to fail, contact your service
provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) for this
problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 6025</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Invalid memory for loading into the
load ID. The IPL will attempt to continue by skipping this load source device
candidate and trying the next candidate.</p>
<p><span class="uicontrol">Recovery:</span> This
is likely a problem with the load source media being corrupt or invalid. A
re-installation of the Licensed Internal Code of the secondary partition is
probably required to recover. If it continues to fail, contact your service
provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) for this
problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 6027</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A low memory condition in the primary
partition is the most likely cause of this SRC. The entire IPL sequence to
the same unit address will be retried.</p>
<p><span class="uicontrol">Recovery:</span> If
the primary partition does not have enough main storage, remove some main
storage from one or more secondary partitions, then add it to the primary
partition. If the primary partition does have enough main storage and there
are no memory leaks, try the operation again.</p>
<p><span class="uicontrol">Problem analysis
procedure:</span> Ensure that the partition was allocated enough main
storage, verify that no memory leaks are present, and then try the operation
again.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 7111</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The secondary load source does not
have an associated IOP hardware driver.</p>
<p><span class="uicontrol">Recovery:</span> Capture
a primary partition MSD. Contact your service provider to resolve the issue.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Contact your service provider to resolve the
issue.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 7115</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Removing an IOP hardware driver (not
the load source for the current IPL) from the primary partition failed. The
IPL will continue, but the secondary partition will most likely not be able
to establish connections to this IOP.</p>
<p><span class="uicontrol">Recovery:</span> You
might need to perform another IPL of the secondary partition to recover the
specified IOP for use by the secondary partition. If it continues to fail,
contact your service provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Identify
the values for words 3-5 to determine the cause of the error. The values for
the words are as follows:</p>
<ul><li>Word 3: Bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
</ul>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 7117</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Removing the IOP hardware driver that
is associated with the current load source has failed. The IPL will not proceed.</p>
<p><span class="uicontrol">Recovery:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) related
to the specified IOP address. Fix any problems found by following the recovery
actions for the PAL SRCs. Try the secondary partition IPL again. An IPL of
the primary partition might be required to regain control of the IOP.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Identify the reason code from words 3-6 of
the SRC. Possible reason code values are the following:</p>
<ul><li>Word 3: bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
<li>Word 6: IOP return code</li>
</ul>
<p>For any other reason code, contact your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 7200</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> An error condition was encountered
when attempting to send the exit VSP mode command (PCI-only bus command) to
the load source IOP.</p>
<p><span class="uicontrol">Recovery:</span> Collect the detailed
hexadecimal data from the product activity log (PAL) related to the specified
IOP address. Fix any problems found by following the recovery actions for
the PAL SRCs. Try the secondary partition IPL again. An IPL of the primary
partition might be required to regain control of the IOP.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Identify the reason code from words 3-5 of
the SRC. Possible reason code values are the following:</p>
<ul><li>Word 3: bus address information</li>
<li>Word 4: Board address information</li>
<li>Word 5: Card address information</li>
</ul>
<p>For any other reason code, contact your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 8105</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Initialization of secondary partition
main storage data structures failed. The IPL is ended.</p>
<p><span class="uicontrol">Recovery:</span> This
is likely a problem with the load source media being corrupt or invalid. A
re-installation of the Licensed Internal Code of the secondary partition is
probably required to recover. If it continues to fail, contact your service
provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) for this
problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 8107</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Failed to allocate main storage for
Licensed Internal Code event messages. This indicates that free main storage
is low in the primary partition. The IPL is ended.</p>
<p><span class="uicontrol">Recovery:</span> If
the primary partition does not have enough main storage, remove some main
storage from one or more secondary partitions, then add it to the primary
partition.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Ensure
the primary partition has an adequate amount of main storage to IPL the secondary
partition.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B2xx 8115</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The opening Licensed Internal Code
Session Manager connections failed for some or all of the connections. The
IPL will continue, but some connections will not be functional.</p>
<p><span class="uicontrol">Recovery:</span> You
might need to perform another IPL of the secondary partition to recover the
Licensed Internal Code Session Manager connections. If it continues to fail,
contact your service provider.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) for this
problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5310</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Logical partition configuration data
has a consistency error. The server cannot find a working copy of the configuration
data for the logical partition.</p>
<p><span class="uicontrol">Recovery:</span> Contact
your service provider. The server will not continue its IPL past dedicated
service tools (DST) until the problem is corrected.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Collect the detailed hexadecimal data from
the product activity log (PAL) for this problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5311</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Logical partition configuration data
does not match the current server configuration. Possible causes include:</p>
<ul><li>A nonconfigured disk unit which was previously a load source for a logical
partition.</li>
<li>Load source configuration data does not match the logical partition for
which it is being used.</li>
<li>Load source configuration data does not match the server serial number
for which it is being used.</li>
<li>Load source configuration data is newer than the primary partition configuration
data.</li>
</ul>
<p><span class="uicontrol">Recovery:</span> Perform one of the following tasks:</p>
<ul><li>If the load source has been replaced inadvertently, return the original
and restart the server.</li>
<li>If the load source is for the primary partition, recover the logical
partition configuration data.</li>
<li>If the specified load source is for a secondary partition, accept the
disk as a load source for that secondary partition.</li>
<li>If the specified disk unit is not configured, clear the nonconfigured
load source to use the new disk unit in the server.</li>
<li>If a load source disk unit has been moved from a server that has logical
partitions, but the current server should not have logical partitions, clear
all partition configuration data. This will delete all secondary partitions.</li>
<li>If the load source came from a partitioned server and was inadvertently
used to perform a partition IPL, do not take any action. The initialize disk
process during installation clears existing configuration data.</li>
</ul>
<p>The logical partition will not continue its IPL past DST until the
problem is corrected with one of the above actions.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Collect the detailed hexadecimal data from
the product activity log (PAL) entry for this problem for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5312</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> Informational indication that the
server detected and corrected a configuration data inconsistency on a logical
partition without any loss of data.</p>
<p><span class="uicontrol">Recovery:</span> None.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> None unless a significant number of errors
occur. Collect the detailed hexadecimal data from the product activity log
(PAL) entries for these problems for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5313</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> The server detected a configuration
data inconsistency for a logical partition and could not correct it without
loss of the last configuration data update.</p>
<p><span class="uicontrol">Recovery:</span> Manually
validate configuration data and repeat any missing configuration actions.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> None unless a significant number of errors
occur. Collect the detailed hexadecimal data from the product activity log
(PAL) entries for these problems for your service provider.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 "> B600 5320</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> An I/O Adapter used by a guest partition
is located in a card position on the same Multi-adapter bridge domain as an
I/O Processor. Guest partition data might be lost if any of the following
occur:</p>
<ul><li>A primary partition Type D IPL is performed.</li>
<li>The I/O Adapter is moved to an <span class="keyword">i5/OS™</span> partition.</li>
<li>An error causes the Logical partition (LPAR) configuration data to not
be used.</li>
</ul>
<p><span class="uicontrol">Recovery:</span> Use the LPAR Validation Tool (LVT)
to create a valid LPAR configuration. For more information about the LPAR
Validation Tool, see the following Web site: <a href="http://www.ibm.com/eserver/iseries/lpar" target="_blank">http://www.ibm.com/eserver/iseries/lpar</a></p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Use the product activity log (PAL) to check
the reason code from words 3-9 of the SRC. Use the reason code from words
3-9 to identify the location of the IOP and IOA. Possible reason code values
are the following:</p>
<ul><li>Word 3: IOP partition ID</li>
<li>Word 4: IOP Frame ID</li>
<li>Word 5: IOP slot</li>
<li>Word 6: IOA partition ID</li>
<li>Word 7: IOA Frame ID</li>
<li>Word 8: IOA slot</li>
<li>Word 9: IOA Type number</li>
</ul>
<p>For any other reason code, contact your service provider</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5340</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A logical partition is running with
less than the requested number of processors.</p>
<p><span class="uicontrol">Recovery:</span> Perform
recovery for the processor-specific errors that are logged in the primary
partition.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Check
the product activity log (PAL) in the primary partition for SRCs that indicate
hardware errors that should be corrected.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5341</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A logical partition is running with
less than the requested amount of main storage.</p>
<p><span class="uicontrol">Recovery:</span> Perform
recovery for the main storage-specific errors that are logged in the primary
partition.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Check
the product activity log (PAL) in the primary partition for SRCs that indicate
hardware errors that should be corrected.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B600 5342</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A logical partition has an insufficient
number of processors. The logical partitions processor minimums could not
be satisfied.</p>
<p><span class="uicontrol">Recovery</span> All resources have been
temporarily assigned to the primary. Perform recovery for the processor specific
errors that are logged in the primary partition.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Check the product activity log (PAL) for
hardware errors.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B600 5343</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A logical partition has an insufficient
amount of memory. The logical partitions memory minimums could not be satisfied.</p>
<p><span class="uicontrol">Recovery:</span> All
resources have been temporarily assigned to the primary. Perform recovery
for the memory specific errors that are logged in the primary partition.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Check the product activity log (PAL) for
hardware errors.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">B600 5344</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A logical partition has an insufficient
amount of interactive performance. The logical partitions interactive performance
minimums could not be satisfied.</p>
<p><span class="uicontrol">Recovery:</span> All
resources have been temporarily assigned to the primary. Perform recovery
for the interactive performance specific errors that are logged in the primary
partition.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Check
the product activity log (PAL) for hardware errors.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5350</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> A logical partition software version
is outside of the supported secondary partition release delta.</p>
<p><span class="uicontrol">Recovery:</span> Perform
one of the following:</p>
<ul><li>Install a supported operating system version in the logical partition
that has the problem.</li>
<li>Install an operating system version in the primary partition that supports
the version in the offending logical partition.</li>
</ul>
<p><span class="uicontrol">Problem analysis procedure:</span> Display the logical
partition release level and check the logical partition release delta.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5380</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> An unexpected event occurred in the
logical partition management code that was recovered.</p>
<p><span class="uicontrol">Recovery:</span> Contact
your service provider if a significant number of these errors have occurred.</p>
<p><span class="uicontrol">Problem
analysis procedure:</span> Collect the detailed hexadecimal data from
the product activity log (PAL) entry for this problem.</p>
</td>
</tr>
<tr><td valign="top" headers="d0e27 ">1 B600 5390</td>
<td valign="top" headers="d0e29 "><p><span class="uicontrol">Cause:</span> An unexpected event occurred in the
logical partition management code which could not be recovered. Further changes
to the logical partition configuration might not be possible.</p>
<p><span class="uicontrol">Recovery:</span> If
this error occurs on an installation or upgrade, the most likely resolution
is to increase the minimum memory of the partition to which you are installing
or upgrading. If increasing the minimum memory does not resolve the issue,
contact your service provider. The server might not IPL past DST until the
problem is corrected.</p>
<p><span class="uicontrol">Problem analysis procedure:</span> Collect
the detailed hexadecimal data from the product activity log (PAL) entry for
this problem.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaittroubleshootoverview.htm" title="Resolve logical partition errors efficiently using the troubleshooting advisor. You can also determine whether the server having problems has logical partitions so that you can more quickly find a solution.">Troubleshoot logical partitions</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="rzaitsecurepar.htm" title="Understand who has authority to perform logical partition tasks and how to restrict access to the system.">Manage security for logical partitions</a></div>
<div><a href="../rzahg/rzahgictroub2.htm">Troubleshooting and Service</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzaitpal.htm" title="Use Dedicated Service Tools (DST) or System Service Tools (SST) to find system reference codes for logical partitions.">View the Product Activity Log (PAL) for logical partitions</a></div>
</div>
</div>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink