Bull Scala Error Codes 86 A148 FF03
Uploaded by
Jorge VarelaBull Scala Error Codes 86 A148 FF03
Uploaded by
Jorge VarelaESCALA Power7
System Reference Codes (Bxxx)
REFERENCE
86 A1 48FF 03
ESCALA Models Reference
The ESCALA Power7 publications concern the following models:
Bull Escala E1-700 / E3-700 (31E/2B ,8231-E2B)
Bull Escala E1-705 (31E/1C, 8231-E1C)
Bull Escala E1-715 (31E/1D, 8231-E1D)
Bull Escala E3-705 (31E/2C, 8231-E2C)
Bull Escala E3-715 (31E/2D, 8231-E2D)
Bull Escala E2-700 / E2-700T (02E/4B, 8202-E4B)
Bull Escala E2-705 / E2-705T (02E/4C, 8202-E4C)
Bull Escala E2-715 / E2-715T (02E/4D, 8202-E4D)
Bull Escala E4-700 / E4-700T (05F/6B, 8205-E6B)
Bull Escala E4-705 (05E/6C, 8205-E6C)
Bull Escala E4-715 (05E/6D, 8205-E6D)
Bull Escala E5-700 (33E/8B, 8233-E8B)
Bull Escala E5-715 (08E/8D, 8408-E8D)
Bull Escala M5-715 (09R/MD, 9109-RMD)
Bull Escala M6-700 (17M/MB, 9117-MMB)
Bull Escala M6-705 (17M/MC, 9117-MMC)
Bull Escala M6-715 (17M/MD, 9117-MMD)
Bull Escala M7-700 (79M/HB, 9179-MHB)
Bull Escala M7-705 (79M/HC, 9179-MHC)
Bull Escala M7-715 (79M/HD, 9179-MHD)
Bull Escala H9-700 (19F/HB, 9119-FHB)
References to 8236-E8C models are irrelevant.
Hardware
February 2013
BULL CEDOC
357 AVENUE PATTON
B.P.20845
49008 ANGERS CEDEX 01
FRANCE
The following copyright notice protects this book under Copyright laws which prohibit such actions as, but not limited to, copying,
distributing, modifying, and making derivative works.
Copyright © Bull SAS 2013
Printed in France
Trademarks and Acknowledgements
We acknowledge the rights of the proprietors of the trademarks mentioned in this manual.
All brand names and software and hardware product names are subject to trademark and/or patent protection.
Quoting of brand and product names is for information purposes only and does not represent trademark misuse.
The information in this document is subject to change without notice. Bull will not be liable for errors contained herein, or
for incidental or consequential damages in connection with the use of this material.
Contents
Safety notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
System reference codes (Bxxx) overview . . . . . . . . . . . . . . . . . . . . . 1
Block replacement of FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
(B002) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
(B003) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
(B004) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
(B005) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
(B006) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
(B008) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
(B009) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
(B010) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
(B011) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
(B012) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
(B013) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
(B014) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
(B015) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
(B017) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
(B025) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
(B026) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
(B028) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
(B038) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
(B040) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
(B057) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
(B070) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
(B075) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
© Copyright IBM Corp. 2010, 2013 iii
(B1xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
(B2xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
(B3xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
(B4xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
(B6xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
(B7xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
(B9xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
(BAxx) Reference codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
(BF67) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
(BF75) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
(BF77) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Electronic emission notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Class A Notices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Class B Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Terms and conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
iv System reference codes (Bxxx)
Safety notices
Safety notices may be printed throughout this guide:
v DANGER notices call attention to a situation that is potentially lethal or extremely hazardous to
people.
v CAUTION notices call attention to a situation that is potentially hazardous to people because of some
existing condition.
v Attention notices call attention to the possibility of damage to a program, device, system, or data.
World Trade safety information
Several countries require the safety information contained in product publications to be presented in their
national languages. If this requirement applies to your country, safety information documentation is
included in the publications package (such as in printed documentation, on DVD, or as part of the
product) shipped with the product. The documentation contains the safety information in your national
language with references to the U.S. English source. Before using a U.S. English publication to install,
operate, or service this product, you must first become familiar with the related safety information
documentation. You should also refer to the safety information documentation any time you do not
clearly understand any safety information in the U.S. English publications.
Replacement or additional copies of safety information documentation can be obtained by calling the IBM
Hotline at 1-800-300-8751.
German safety information
Das Produkt ist nicht für den Einsatz an Bildschirmarbeitsplätzen im Sinne § 2 der
Bildschirmarbeitsverordnung geeignet.
Laser safety information
IBM® servers can use I/O cards or features that are fiber-optic based and that utilize lasers or LEDs.
Laser compliance
IBM servers may be installed inside or outside of an IT equipment rack.
© Copyright IBM Corp. 2010, 2013 v
DANGER
When working on or around the system, observe the following precautions:
Electrical voltage and current from power, telephone, and communication cables are hazardous. To
avoid a shock hazard:
v Connect power to this unit only with the IBM provided power cord. Do not use the IBM
provided power cord for any other product.
v Do not open or service any power supply assembly.
v Do not connect or disconnect any cables or perform installation, maintenance, or reconfiguration
of this product during an electrical storm.
v The product might be equipped with multiple power cords. To remove all hazardous voltages,
disconnect all power cords.
v Connect all power cords to a properly wired and grounded electrical outlet. Ensure that the outlet
supplies proper voltage and phase rotation according to the system rating plate.
v Connect any equipment that will be attached to this product to properly wired outlets.
v When possible, use one hand only to connect or disconnect signal cables.
v Never turn on any equipment when there is evidence of fire, water, or structural damage.
v Disconnect the attached power cords, telecommunications systems, networks, and modems before
you open the device covers, unless instructed otherwise in the installation and configuration
procedures.
v Connect and disconnect cables as described in the following procedures when installing, moving,
or opening covers on this product or attached devices.
To Disconnect:
1. Turn off everything (unless instructed otherwise).
2. Remove the power cords from the outlets.
3. Remove the signal cables from the connectors.
4. Remove all cables from the devices.
To Connect:
1. Turn off everything (unless instructed otherwise).
2. Attach all cables to the devices.
3. Attach the signal cables to the connectors.
4. Attach the power cords to the outlets.
5. Turn on the devices.
(D005)
DANGER
vi System reference codes (Bxxx)
Observe the following precautions when working on or around your IT rack system:
v Heavy equipment–personal injury or equipment damage might result if mishandled.
v Always lower the leveling pads on the rack cabinet.
v Always install stabilizer brackets on the rack cabinet.
v To avoid hazardous conditions due to uneven mechanical loading, always install the heaviest
devices in the bottom of the rack cabinet. Always install servers and optional devices starting
from the bottom of the rack cabinet.
v Rack-mounted devices are not to be used as shelves or work spaces. Do not place objects on top
of rack-mounted devices.
v Each rack cabinet might have more than one power cord. Be sure to disconnect all power cords in
the rack cabinet when directed to disconnect power during servicing.
v Connect all devices installed in a rack cabinet to power devices installed in the same rack
cabinet. Do not plug a power cord from a device installed in one rack cabinet into a power
device installed in a different rack cabinet.
v An electrical outlet that is not correctly wired could place hazardous voltage on the metal parts of
the system or the devices that attach to the system. It is the responsibility of the customer to
ensure that the outlet is correctly wired and grounded to prevent an electrical shock.
CAUTION
v Do not install a unit in a rack where the internal rack ambient temperatures will exceed the
manufacturer's recommended ambient temperature for all your rack-mounted devices.
v Do not install a unit in a rack where the air flow is compromised. Ensure that air flow is not
blocked or reduced on any side, front, or back of a unit used for air flow through the unit.
v Consideration should be given to the connection of the equipment to the supply circuit so that
overloading of the circuits does not compromise the supply wiring or overcurrent protection. To
provide the correct power connection to a rack, refer to the rating labels located on the
equipment in the rack to determine the total power requirement of the supply circuit.
v (For sliding drawers.) Do not pull out or install any drawer or feature if the rack stabilizer brackets
are not attached to the rack. Do not pull out more than one drawer at a time. The rack might
become unstable if you pull out more than one drawer at a time.
v (For fixed drawers.) This drawer is a fixed drawer and must not be moved for servicing unless
specified by the manufacturer. Attempting to move the drawer partially or completely out of the
rack might cause the rack to become unstable or cause the drawer to fall out of the rack.
(R001)
Safety notices vii
CAUTION:
Removing components from the upper positions in the rack cabinet improves rack stability during
relocation. Follow these general guidelines whenever you relocate a populated rack cabinet within a
room or building:
v Reduce the weight of the rack cabinet by removing equipment starting at the top of the rack
cabinet. When possible, restore the rack cabinet to the configuration of the rack cabinet as you
received it. If this configuration is not known, you must observe the following precautions:
– Remove all devices in the 32U position and above.
– Ensure that the heaviest devices are installed in the bottom of the rack cabinet.
– Ensure that there are no empty U-levels between devices installed in the rack cabinet below the
32U level.
v If the rack cabinet you are relocating is part of a suite of rack cabinets, detach the rack cabinet from
the suite.
v Inspect the route that you plan to take to eliminate potential hazards.
v Verify that the route that you choose can support the weight of the loaded rack cabinet. Refer to the
documentation that comes with your rack cabinet for the weight of a loaded rack cabinet.
v Verify that all door openings are at least 760 x 230 mm (30 x 80 in.).
v Ensure that all devices, shelves, drawers, doors, and cables are secure.
v Ensure that the four leveling pads are raised to their highest position.
v Ensure that there is no stabilizer bracket installed on the rack cabinet during movement.
v Do not use a ramp inclined at more than 10 degrees.
v When the rack cabinet is in the new location, complete the following steps:
– Lower the four leveling pads.
– Install stabilizer brackets on the rack cabinet.
– If you removed any devices from the rack cabinet, repopulate the rack cabinet from the lowest
position to the highest position.
v If a long-distance relocation is required, restore the rack cabinet to the configuration of the rack
cabinet as you received it. Pack the rack cabinet in the original packaging material, or equivalent.
Also lower the leveling pads to raise the casters off of the pallet and bolt the rack cabinet to the
pallet.
(R002)
(L001)
(L002)
viii System reference codes (Bxxx)
(L003)
or
All lasers are certified in the U.S. to conform to the requirements of DHHS 21 CFR Subchapter J for class
1 laser products. Outside the U.S., they are certified to be in compliance with IEC 60825 as a class 1 laser
product. Consult the label on each part for laser certification numbers and approval information.
CAUTION:
This product might contain one or more of the following devices: CD-ROM drive, DVD-ROM drive,
DVD-RAM drive, or laser module, which are Class 1 laser products. Note the following information:
v Do not remove the covers. Removing the covers of the laser product could result in exposure to
hazardous laser radiation. There are no serviceable parts inside the device.
v Use of the controls or adjustments or performance of procedures other than those specified herein
might result in hazardous radiation exposure.
(C026)
Safety notices ix
CAUTION:
Data processing environments can contain equipment transmitting on system links with laser modules
that operate at greater than Class 1 power levels. For this reason, never look into the end of an optical
fiber cable or open receptacle. (C027)
CAUTION:
This product contains a Class 1M laser. Do not view directly with optical instruments. (C028)
CAUTION:
Some laser products contain an embedded Class 3A or Class 3B laser diode. Note the following
information: laser radiation when open. Do not stare into the beam, do not view directly with optical
instruments, and avoid direct exposure to the beam. (C030)
CAUTION:
The battery contains lithium. To avoid possible explosion, do not burn or charge the battery.
Do Not:
v ___ Throw or immerse into water
v ___ Heat to more than 100°C (212°F)
v ___ Repair or disassemble
Exchange only with the IBM-approved part. Recycle or discard the battery as instructed by local
regulations. In the United States, IBM has a process for the collection of this battery. For information,
call 1-800-426-4333. Have the IBM part number for the battery unit available when you call. (C003)
Power and cabling information for NEBS (Network Equipment-Building System)
GR-1089-CORE
The following comments apply to the IBM servers that have been designated as conforming to NEBS
(Network Equipment-Building System) GR-1089-CORE:
The equipment is suitable for installation in the following:
v Network telecommunications facilities
v Locations where the NEC (National Electrical Code) applies
The intrabuilding ports of this equipment are suitable for connection to intrabuilding or unexposed
wiring or cabling only. The intrabuilding ports of this equipment must not be metallically connected to the
interfaces that connect to the OSP (outside plant) or its wiring. These interfaces are designed for use as
intrabuilding interfaces only (Type 2 or Type 4 ports as described in GR-1089-CORE) and require isolation
from the exposed OSP cabling. The addition of primary protectors is not sufficient protection to connect
these interfaces metallically to OSP wiring.
Note: All Ethernet cables must be shielded and grounded at both ends.
The ac-powered system does not require the use of an external surge protection device (SPD).
The dc-powered system employs an isolated DC return (DC-I) design. The DC battery return terminal
shall not be connected to the chassis or frame ground.
x System reference codes (Bxxx)
System reference codes (Bxxx) overview
Reference codes are diagnostics aids that help you find solutions to system problems.
Reference codes are diagnostic aids that help you determine the source of a hardware or operating
system problem. Using a reference code enables you to find the solution to fix the problem. To use
reference codes effectively, you must use them in conjunction with other service and support procedures.
Note: System reference codes (SRCs) often indicate failing items. Some failing items are required to be
exchanged in groups until the problem is solved. Other failing items are flagged as mandatory exchange
and must be exchanged before the service action is complete, even if the problem appears to have been
repaired. For more information, see “Block replacement of FRUs.”
Block replacement of FRUs
Sometimes, multiple field replaceable units (FRUs) or procedures are called out for replacement by an
SRC listed in the service action log (SAL). Each FRU or procedure has a priority, and procedures are
always in priority order, from highest to lowest priority. Follow the steps below:
1. Perform all high priority or mandatory FRU replacements or procedures at the same time (as a block).
2. If the problem persists after performing the high priority FRU replacements or procedures, then
perform the medium priority FRU replacements or procedures one at a time, unless a medium
grouping priority is associated with the FRUs or procedures that are called out in the SRC. A medium
grouping priority, shown with an A, B, or C, means that you need to perform all the FRU
replacements or procedures in that group at the same time (as a block).
3. Finally, if the problem still persists after performing the medium priority FRU replacements or
procedures, then perform the low priority FRU replacements or procedures one at a time.
The priorities of performing the FRU replacements or procedures are shown in the following ways,
depending on how you view the SRC:
v Advanced System Management Interface (ASMI): The ASMI shows a priority with each callout in the
log.
v Control panel: The control panel shows one of the following priorities with each callout:
– H = High
– M = Medium
– MA = Medium group A
– MB = Medium group B
– MC = Medium group C
– L = Low
v Management console: The details of the serviceable event display the FRU replacement priority as
high, medium, and so on.
v Service action log: In the SAL, the Part Action for the FRU in the view of the event shows the
replacement priority.
© Copyright IBM Corp. 2010, 2013 1
2 System reference codes (Bxxx)
(B002) Reference codes
Failing Item:
B0022321 B0022321
v UJ0E3
Explanation: Procedure error in vertical Licensed
v FI00704
Internal Code
v UJB36
Failing Item:
v UJE34
B0022653 B0022653
Explanation: First call failed, retrying call; CFI DE
B0022322 B0022322
from modem
Explanation: Data-set-ready error on modem interface
Response: After dialing, the system detected a call
Failing Item: failure indication DE from the modem. The system tries
v UJE34 the call again, up to the number of tries specified in the
dial retry parameter of the controller description. CFI
DE is sent from the modem if the modem failed to
B0022340 B0022340 detect a dial tone when expected or detected a dial
Explanation: Data-set-ready changed to not active; for tone when another tone was expected. This can occur if
information only the telephone cable is not plugged into the back of the
modem.
Failing Item:
Failing Item:
v FI00704
v UJ0E3
v UJB35
v FI00704
v UJ0E3
v FI00701
B0022654 B0022654
B0022651 B0022651 Explanation: First call failed, retrying call; CFI ET
from modem
Explanation: First call failed, retrying call; no CFI
from modem Response: After dialing, the system detected a call
failure indication ET from the modem. The system tries
Response: The remote answer timer expired without the call again, up to the number of tries specified in the
the system detecting either the rise of DSR or a call dial retry parameter of the controller description. CFI
failure indication from the modem. The system tries the ET is sent from the modem if the modem detects a
call again, up to the number of tries specified in the busy signal (engaged tone).
dial retry parameter of the controller description.
Failing Item:
Failing Item: v UJ0E3
v UJE34 v UJB36
v UJB35
v FI00704 B0022656 B0022656
v FI00701
Explanation: First call failed, retrying call; CFI NT
from modem
B0022652 B0022652
Response: After dialing, the system detected a call
Explanation: First call failed, retrying call; CFI AB failure indication NT from the modem. The system tries
from modem the call again, up to the number of tries specified in the
dial retry parameter of the controller description. CFI
Response: After dialing, the system detected a call
NT is sent from the modem if the modem#csq;s timer
failure indication AB from the modem. The system tries
expires without detecting an answer tone or a ring
the call again, up to the number of tries specified in the
back, and had detected the expected dial tones. This
dial retry parameter of the controller description. CFI
situation could result from a person answering the
AB is sent from the modem if the modem#csq;s timer
telephone.
expires after answer tone was detected and before the
modem is ready for data transfer. Failing Item:
© Copyright IBM Corp. 2010, 2013 3
B0022657 • B0023207
v UJ0E3
B0023202 B0023202
v FI00705
Explanation: Clear-to-send state changed; error limit
v UJB36
per 256 reached
Failing Item:
B0022657 B0022657
v FI00704
Explanation: First call failed, retrying call; CFI RT
v UJB35
from modem
v FI00701
Response: After dialing, the system detected a call
v FI00719
failure indication RT from the modem. The system tries
the call again, up to the number of tries specified in the
dial retry parameter of the controller description. CFI B0023203 B0023203
RT is sent from the modem if the modem does not
Explanation: Carrier-detect state changed; error limit
detect the remote answer when the timer expired or the
per 256 reached
modem is still detecting ring back. This response is also
sent if the modem ends a call because the ring counter Failing Item:
reached its limit. v FI00704
Failing Item: v UJB35
v UJ0E3 v FI00701
v UJB36 v FI00719
B0022660 B0022660 B0023204 B0023204
Explanation: Call failed, retrying call; Non-standard Explanation: Call not completed; error limit per 256
CFI from modem reached
Response: After dialing, the system detected a call Failing Item:
failure indication from the modem that was not v UJB36
recognized. The system tries the call again, up to the
number of tries specified in the dial retry parameter of v UJ0E3
the controller description. v FI00705
Failing Item: v FI00703
v UJ0E3
v FI00704 B0023205 B0023205
Explanation: Call completed with error; error limit per
B0023200 B0023200 256 reached
Explanation: Clear-to-send state changed; error limit Failing Item:
per 256 reached v UJB35
Failing Item:
v FI00704 B0023206 B0023206
v UJB35 Explanation: Data-line-occupied error; error limit per
v FI00701 256 reached
v FI00719 Failing Item:
v FI00703
B0023201 B0023201 v UJB35
Explanation: Data-set-ready state changed; error limit v UJ0E3
per 256 reached v FI00702
Failing Item:
v FI00704 B0023207 B0023207
v UJB35 Explanation: Abandon-call-retry error; error limit per
v FI00701 256 reached
v FI00719 Failing Item:
4 System reference codes (Bxxx)
B0023208 • B0024206
v FI00703 v FI00719
v UJB35
v UJ0E3 B0024201 B0024201
v FI00702 Explanation: Wrong data block received; error limit
v UJB36 per 256 reached
Failing Item:
B0023208 B0023208 v UJ0E3
Explanation: Present-next-digit error; error limit per
256 reached B0024202 B0024202
Failing Item: Explanation: Temporary text delay block sent; error
v FI00702 limit per 256
v FI00703 Failing Item:
v UJB35 v UJB35
v FI00719 v UJB37
B0023209 B0023209 B0024203 B0024203
Explanation: Distant-station-connected error; error Explanation: Wait-acknowledge block sent; error limit
limit per 256 reached per 256 reached
Failing Item: Failing Item:
v FI00703 v UJB35
v UJB35 v UJB37
v UJ0E3
v FI00702 B0024204 B0024204
v UJB36
Explanation: Incorrect data block sent; error limit per
256 reached
B002320B B002320B
Failing Item:
Explanation: Data-set-ready state changed; error limit v FI00730
per 256 reached
v FI00719
Failing Item: v UJB35
v FI00704
v UJB35 B0024205 B0024205
v UJ0E3
Explanation: Communications IOP cannot receive;
v FI00701 limit reached
Failing Item:
B002320C B002320C
v FI00730
Explanation: Incorrect number dialed; error limit per v FI00719
256 reached
v UJB35
Failing Item:
v UJB36 B0024206 B0024206
v UJB35
Explanation: Receive-time-out error; error limit per
256 reached
B0024200 B0024200
Failing Item:
Explanation: Wrong data block received; error limit v FI00730
per 256 reached
v AJDG301
Failing Item:
v UJ0E3
v UJB35
(B002) Reference codes 5
B0024207 • B0024506
B0024207 B0024207 B0024376 B0024376
Explanation: Continuous synchronization on line; Explanation: Automatic call unit already in use
error limit reached
Failing Item:
Failing Item: v AJDG301
v UJ0E3 v UJB35
v UJC38
B0024208 B0024208
Explanation: No synchronization received; error limit B0024502 B0024502
per 256 reached
Explanation: Incorrect command value sent by vertical
Failing Item: LIC
v UJ0E3 Failing Item:
v AJDG301
B0024209 B0024209 v FI00730
Explanation: Synchronous time-out; error limit per 256
reached B0024503 B0024503
Failing Item: Explanation: Incorrect command value sent by vertical
v UJ0E3 LIC
v FI00719 Failing Item:
v UJB35 v AJDG301
B0024220 B0024220 B0024504 B0024504
Explanation: Communications line already in use Explanation: Incorrect parts installed for BSC
Failing Item: communications
v AJDG301 Failing Item:
v FI00719 v UJB35
v UJB35 v AJDG301
B0024240 B0024240 B0024505 B0024505
Explanation: Adapter not installed Explanation: Incorrect command value sent by vertical
LIC
Failing Item:
v AJDG301 Failing Item:
v FI00719 v AJDG301
v UJB35 v UJB35
v FI00730
B0024340 B0024340
B0024506 B0024506
Explanation: V.25 adapter not installed
Explanation: Incorrect command value sent by vertical
Failing Item:
LIC
v AJDG301
Failing Item:
v UJB35
v AJDG301
v FI00719
v UJB35
v FI00702
v FI00730
6 System reference codes (Bxxx)
B0024508 • B0025476
B0024508 B0024508 B0024592 B0024592
Explanation: Incorrect command value sent by vertical Explanation: No number specified in controller
LIC description
Failing Item: Failing Item:
v AJDG301 v UJB36
v FI00730
B0024594 B0024594
B0024509 B0024509 Explanation: Wrong telephone number specified in
Explanation: Incorrect command value sent by vertical system configuration
LIC Failing Item:
Failing Item: v UJB36
v AJDG301 v FI00730
v FI00730 v AJDG301
B002450A B002450A B0025410 B0025410
Explanation: Incorrect command value sent by vertical Explanation: Data-set-ready error on modem interface
LIC
Failing Item:
Failing Item: v FI00704
v AJDG301 v UJB35
v FI00730 v FI00702
v UJB35 v FI00719
B002450B B002450B B0025472 B0025472
Explanation: Incorrect command value sent by vertical Explanation: Data-line-occupied initially 'on' error
LIC
Failing Item:
Failing Item:
v FI00703
v AJDG301
v UJC38
v FI00730
v FI00719
v FI00702
B002450E B002450E
Explanation: Call type not permitted B0025474 B0025474
Failing Item: Explanation: Automatic call unit has
v AJDG301 data-line-occupied error
v FI00730 Failing Item:
v UJB35 v FI00702
v FI00703
B0024590 B0024590 v FI00719
Explanation: Wrong telephone number specified in v UJ0E3
system configuration
Failing Item: B0025476 B0025476
v UJB36 Explanation: Automatic call unit has
v FI00703 present-next-digit error
v UJ0E3 Failing Item:
v FI00702 v FI00703
v FI00719
v FI00702
(B002) Reference codes 7
B0025501 • B0025651
v FI00730
B0025501 B0025501
Explanation: Incorrect command value sent by vertical
B0025549 B0025549
LIC
Explanation: Incorrect command value sent by vertical
Failing Item:
LIC
v AJDG301
Failing Item:
v FI00730
v AJDG301
v FI00730
B0025502 B0025502
Explanation: Incorrect command value sent by vertical
B0025590 B0025590
LIC
Explanation: Too many dial digits in call setup
Failing Item:
v AJDG301 Failing Item:
v FI00730 v UJB36
B0025503 B0025503 B0025630 B0025630
Explanation: Incorrect command value sent by vertical Explanation: Automatic call unit has
LIC distant-station-connected error
Failing Item: Failing Item:
v AJDG301 v FI00700
v FI00730 v UJ0E3
v UJB35
B0025504 B0025504 v FI00701
v FI00719
Explanation: Incorrect command value sent by vertical
LIC
B0025632 B0025632
Failing Item:
v AJDG301 Explanation: Automatic call unit has data-set-ready
error
v UJB35
Failing Item:
B0025505 B0025505 v FI00700
v UJB36
Explanation: Incorrect command value in I/O card
LIC v FI00703
v UJB35
Failing Item:
v FI00701
v FI00730
v FI00719
v UJ0E3
B0025520 B0025520
Explanation: Incorrect command value sent by vertical
B0025651 B0025651
LIC
Explanation: Call failed, no Call Failure Indication
Failing Item:
from modem
v AJDG301
Response: The remote answer timer expired without
v FI00730
the system detecting either the rise of DSR or a call
failure indication from the modem. The system has
B0025521 B0025521 reached the number of tries in the dial retry parameter
in the controller description.
Explanation: Incorrect command value sent by vertical
LIC Failing Item:
Failing Item: v UJE34
v AJDG301 v UJB35
8 System reference codes (Bxxx)
B0025684 • B0025E01
v FI00704
B0025A24 B0025A24
v FI00701
Explanation: Carrier-detect dropped on modem
interface
B0025684 B0025684
Failing Item:
Explanation: Automatic call unit has call-clear error
v FI00701
Failing Item: v FI00704
v FI00704 v UJ0E3
v FI00701 v FI00719
v AJDG301
v FI00719 B0025A54 B0025A54
Explanation: Data-set-ready did not drop during
B0025886 B0025886 time-out
Explanation: Automatic call unit switched link Failing Item:
time-out; no answer
v FI00704
Failing Item: v UJB35
v FI00703 v FI00701
v FI00719 v FI00719
v UJ0E3
v FI00702 B0025A58 B0025A58
Explanation: Data-set-ready did not come up during
B0025A18 B0025A18 time-out
Explanation: Clear-to-send signal failed to drop on Failing Item:
modem interface
v FI00701
Failing Item: v FI00704
v FI00704 v FI00719
v FI00701 v AJDG301
v FI00719
B0025C68 B0025C68
B0025A1C B0025A1C
Explanation: Too many user connections attempted
Explanation: Clear-to-send signal dropped on modem
Failing Item:
interface
v AJDG301
Failing Item:
v UJ0E3
B0025E00 B0025E00
v UJB35
Explanation: Wrong or no external communications
v FI00704
cable installed
v FI00701
Failing Item:
v FI00719
v UJB35
v FI00701
B0025A20 B0025A20
v FI00719
Explanation: Clear-to-send not active on modem
interface
B0025E01 B0025E01
Failing Item:
Explanation: Call error; incoming call received during
v UJ0E3
outgoing call
v UJB35
Failing Item:
v FI00704
v UJC38
v FI00701
v FI00704
v FI00719
(B002) Reference codes 9
B0026210 • B0027C00
v FI00701
B0026870 B0026870
v FI00719
Explanation: Automatic call unit power turned off
B0026210 B0026210 Failing Item:
v FI00703
Explanation: Communications controller storage not
available v FI00702
v FI00719
Failing Item:
v UJB35
B0026890 B0026890
v FI00730
Explanation: Data-set-ready dropped on modem
interface
B0026212 B0026212
Failing Item:
Explanation: Storage deallocation error
v UJ0E3
Failing Item:
v FI00701
v FI00730
v FI00704
v FI00719
B0026214 B0026214
Explanation: Storage allocation error B0026C05 B0026C05
Failing Item: Explanation: Error in I/O card Licensed Internal Code
v FI00730
Failing Item:
v FI00730
B0026288 B0026288
v AJDG301
Explanation: Port not operational
Failing Item: B0026C0A B0026C0A
v FI00719 Explanation: Hardware detected failure
v AJDG301
Failing Item:
v UJB35
v FI00719
v FI00718
B0026320 B0026320
Explanation: Automatic call unit has abandon-call B0027210 B0027210
attempt
Explanation: Communications controller storage not
Failing Item: available
v FI00700
Failing Item:
v UJB36
v UJB35
v FI00703
v FI00730
v FI00719
v FI00702
B0027212 B0027212
Explanation: Communications program error
B0026322 B0026322
Failing Item:
Explanation: Abandon call retry error; incorrect
number length v FI00730
v AJDG301
Failing Item:
v FI00703
B0027C00 B0027C00
v UJB36
Explanation: Communications program error
Failing Item:
v FI00730
10 System reference codes (Bxxx)
B0027C02 • B002FFFF
B0027C02 B0027C02
Explanation: Communications program error
Failing Item:
v FI00730
B0027C03 B0027C03
Explanation: Resource or storage not available
Failing Item:
v UJB37
v FI00730
B0027C04 B0027C04
Explanation: Communications program error
Failing Item:
v FI00730
B0027C05 B0027C05
Explanation: Incorrect command value in I/O card
LIC
Failing Item:
v FI00730
B0027C09 B0027C09
Explanation: Communications program error
Failing Item:
v FI00730
B002FFFF B002FFFF
Explanation: User suspected communications
problem.
Failing Item:
v USER
(B002) Reference codes 11
12 System reference codes (Bxxx)
(B003) Reference codes
Explanation: Clear-to-send state changed; error limit
B0032321 B0032321
per 256 reached
Explanation: Procedure error in vertical Licensed
Response:
Internal Code
Failing Item:
Failing Item:
v FI00704
v UJE34
v UJC35
v FI00701
B0032322 B0032322
v FI00719
Explanation: Data-set-ready error on modem interface
Failing Item: B0033203 B0033203
v UJE34
Explanation: Carrier-detect state changed; error limit
per 256 reached
B0032340 B0032340
Response:
Explanation: Data-set-ready changed to not active; for
Failing Item:
information only
v FI00704
Response:
v UJC35
Failing Item: v FI00701
v FI00704 v FI00719
v UJC35
v FI00701 B0033204 B0033204
v FI00719
Explanation: Call not completed; error limit per 256
reached
B0033200 B0033200
Failing Item:
Explanation: Clear-to-send state changed; error limit v UJC36
per 256 reached
v UJ0E3
Response: v FI00705
Failing Item: v FI00703
v FI00704
v UJC35 B0033205 B0033205
v FI00701 Explanation: Call completed with error; error limit per
v FI00719 256 reached
Failing Item:
B0033201 B0033201 v UJC35
Explanation: Data-set-ready state changed; error limit
per 256 reached B0033206 B0033206
Response: Explanation: Data-line-occupied error; error limit per
Failing Item: 256 reached
v FI00704 Failing Item:
v UJC35 v FI00703
v FI00701 v UJC35
v FI00719 v UJ0E3
v FI00702
B0033202 B0033202
© Copyright IBM Corp. 2010, 2013 13
B0033207 • B0034206
B0033207 B0033207 B0034200 B0034200
Explanation: Abandon-call-retry error; error limit per Explanation: Break character received; error limit per
256 reached 256 reached
Failing Item: Failing Item:
v FI00703 v UJ0E3
v UJC35 v UJC35
v UJ0E3
v FI00702 B0034202 B0034202
v UJC36 Explanation: Received storage overrun; error limit per
256 reached
B0033208 B0033208 Failing Item:
Explanation: Present-next-digit error; error limit per v FI00730
256 reached v UJC35
Response:
Failing Item: B0034203 B0034203
v FI00703 Explanation: Incorrect stop bit; error limit per 256
v UJC35 reached
v FI00702 Failing Item:
v FI00719 v UJ0E3
v UJC35
B0033209 B0033209
Explanation: Distant-station-connected error; error B0034204 B0034204
limit per 256 reached Explanation: Receive-time-out error; error limit per
Failing Item: 256 reached
v FI00703 Failing Item:
v UJC35 v UJC35
v UJ0E3 v UJ0E3
v FI00702
v UJC36 B0034205 B0034205
Explanation: Number of characters discarded; error
B003320B B003320B limit per 256 reached
Explanation: Data-set-ready state changed; error limit Failing Item:
per 256 reached v UJ0E3
Response: v UJC35
Failing Item: v UJB37
v FI00704
v UJC35 B0034206 B0034206
v FI00701 Explanation: Procedure error in vertical Licensed
v FI00719 Internal Code
Failing Item:
B003320C B003320C v FI00730
Explanation: Incorrect number dialed; error limit per v AJDG301
256 reached
Failing Item:
v UJC36
v UJC35
14 System reference codes (Bxxx)
B0034209 • B0034508
B0034209 B0034209 B0034503 B0034503
Explanation: Wrong data received; error limit per 256 Explanation: Wrong configuration value sent by
reached vertical LIC
Failing Item: Failing Item:
v UJ0E3 v AJDG301
v UJC35 v FI00730
v UJC35
B0034220 B0034220
Explanation: Port already in use B0034504 B0034504
Response: Explanation: Wrong configuration value sent by
vertical LIC
Failing Item:
Failing Item:
v AJDG301
v AJDG301
v FI00719
v UJC35
v UJC35
B0034505 B0034505
B0034240 B0034240
Explanation: Wrong configuration value sent by
Explanation: Port not installed
vertical LIC
Response:
Failing Item:
Failing Item: v AJDG301
v AJDG301 v UJC35
v FI00719 v FI00730
v UJC35
B0034506 B0034506
B0034340 B0034340
Explanation: Wrong configuration value sent by
Explanation: Automatic call unit port is not installed vertical LIC
Response: Failing Item:
Failing Item: v AJDG301
v AJDG301 v UJC35
v UJC35 v FI00730
v FI00719
v FI00702 B0034507 B0034507
Explanation: Wrong configuration value sent by
B0034376 B0034376 vertical LIC
Explanation: Automatic call unit already in use Failing Item:
v AJDG301
Failing Item:
v FI00730
v AJDG301
v UJC35
v UJC38
v UJC35
B0034508 B0034508
B0034502 B0034502 Explanation: Wrong configuration value sent by
vertical LIC
Explanation: Wrong configuration value sent by
vertical LIC Failing Item:
v AJDG301
Failing Item:
v FI00730
v AJDG301
v FI00730
(B003) Reference codes 15
B0034509 • B0035410
B0034509 B0034509 B0034549 B0034549
Explanation: Wrong configuration value sent by Explanation: Wrong configuration value sent by
vertical LIC vertical LIC
Failing Item: Failing Item:
v AJDG301 v AJDG301
v UJC35 v FI00730
v FI00730
B0034590 B0034590
B003450A B003450A Explanation: Wrong number specified in controller
Explanation: Wrong configuration value sent by description
vertical LIC Response:
Failing Item: Failing Item:
v AJDG301 v UJC36
v FI00730 v FI00703
v UJC35 v FI00701
v UJC35
B003450B B003450B v FI00719
Explanation: Wrong configuration value sent by
vertical LIC B0034592 B0034592
Failing Item: Explanation: No number specified in controller
v AJDG301 description
v FI00730 Failing Item:
v AJDG301
B003450C B003450C v UJC36
Explanation: Wrong configuration value sent by
vertical LIC B0034594 B0034594
Failing Item: Explanation: Wrong number specified in controller
v AJDG301 description
v FI00730 Failing Item:
v UJC36
B003450D B003450D v FI00730
Explanation: Wrong configuration value sent by v AJDG301
vertical LIC v UJC35
Failing Item:
v UJC35 B0035410 B0035410
v FI00730 Explanation: Switched line already in use
v AJDG301
Response:
Failing Item:
B003450E B003450E
v FI00704
Explanation: Wrong configuration value sent by
v UJC35
vertical LIC
v FI00701
Failing Item:
v FI00719
v AJDG301
v FI00730
v UJC35
16 System reference codes (Bxxx)
B0035472 • B0035514
B0035472 B0035472 B0035503 B0035503
Explanation: Data-line-occupied error at time of Explanation: Wrong configuration value sent by
starting vertical LIC
Response: Failing Item:
Failing Item: v AJDG301
v FI00703 v UJC35
v UJC38 v FI00730
v FI00719
v FI00702 B0035510 B0035510
Explanation: Wrong configuration value sent by
B0035474 B0035474 vertical LIC
Explanation: Automatic call unit line connection error Failing Item:
v AJDG301
Response:
v UJC35
Failing Item:
v FI00730
v FI00702
v FI00703
B0035511 B0035511
v FI00719
Explanation: Wrong configuration value sent by
v UJ0E3
vertical LIC
Failing Item:
B0035476 B0035476
v AJDG301
Explanation: Present-next-digit error
v FI00730
Response:
Failing Item: B0035512 B0035512
v FI00702 Explanation: Wrong configuration value sent by
v FI00703 vertical LIC
v FI00719 Failing Item:
v AJDG301
B0035501 B0035501 v FI00730
Explanation: Wrong configuration value sent by
vertical LIC B0035513 B0035513
Failing Item: Explanation: Wrong configuration value sent by
v AJDG301 vertical LIC
v FI00730 Failing Item:
v AJDG301
B0035502 B0035502 v UJC35
Explanation: Wrong configuration value sent by v FI00730
vertical LIC
Failing Item: B0035514 B0035514
v AJDG301 Explanation: Wrong configuration value sent by
v UJC35 vertical LIC
v FI00730 Failing Item:
v AJDG301
v FI00730
(B003) Reference codes 17
B0035515 • B0035A20
B0035515 B0035515 B0035684 B0035684
Explanation: Wrong configuration value sent by Explanation: Time-out on call-clear-request
vertical LIC
Response:
Failing Item:
Failing Item:
v AJDG301
v FI00704
v UJC35
v FI00701
v FI00730
v AJDG301
v FI00719
B0035549 B0035549
Explanation: Wrong configuration value sent by B0035886 B0035886
vertical LIC
Explanation: Automatic call unit line connection error
Failing Item:
Failing Item:
v AJDG301
v FI00704
v FI00730
v FI00719
v FI00701
B0035590 B0035590
Explanation: Wrong length for number dialed
B0035A18 B0035A18
Failing Item:
Explanation: Clear-to-send signal failed to drop on
v AJDG301 modem interface
Response:
B0035630 B0035630
Failing Item:
Explanation: Automatic call unit distant-station-
v FI00704
connected time out
v FI00701
Failing Item:
v FI00719
v FI00700
v UJ0E3
B0035A1C B0035A1C
v UJC35
Explanation: Clear-to-send signal dropped on modem
v FI00701
interface
v FI00719
Response:
B0035632 B0035632 Failing Item:
v UJ0E3
Explanation: Automatic call unit had data-set-ready
time out v UJC35
v FI00704
Response:
v FI00701
Failing Item:
v FI00719
v FI00700
v UJC35
B0035A20 B0035A20
v UJC36
Explanation: Clear-to-send not active on modem
v FI00703
interface
v FI00701
Response:
v FI00719
v UJ0E3 Failing Item:
v UJ0E3
v UJC35
v FI00704
v FI00701
18 System reference codes (Bxxx)
B0035A24 • B0036320
v FI00719
B0035E01 B0035E01
Explanation: Call received during dialing procedure
B0035A24 B0035A24
Response:
Explanation: Carrier-detect dropped on modem
interface Failing Item:
Response: v UJC38
v FI00704
Failing Item:
v FI00701
v FI00701
v FI00719
v FI00704
v UJ0E3
B0036210 B0036210
v FI00719
Explanation: Resource or storage not available
B0035A54 B0035A54 Failing Item:
Explanation: Time-out; data-set-ready did not drop v UJC35
v FI00730
Response:
Failing Item:
B0036212 B0036212
v FI00704
Explanation: Communications controller error
v UJC35
v FI00701 Response:
v FI00719 Failing Item:
v FI00730
B0035A58 B0035A58 v FI00718
Explanation: Time-out; data-set-ready not received
B0036214 B0036214
Response:
Explanation: Communications controller error
Failing Item:
v FI00701 Response:
v FI00704 Failing Item:
v FI00719 v FI00730
v AJDG301 v FI00718
B0035C68 B0035C68 B0036288 B0036288
Explanation: Procedure error in vertical Licensed Explanation: Port not operational
Internal Code
Response:
Failing Item:
Failing Item:
v AJDG301
v FI00719
v FI00730
v AJDG301
v UJC35
B0035E00 B0035E00
Explanation: Wrong or no external communications B0036320 B0036320
cable installed
Explanation: Abandon-call-retry
Response:
Response:
Failing Item:
Failing Item:
v FI00701
v FI00700
v UJC35
v UJC36
v FI00719
v FI00703
(B003) Reference codes 19
B0036322 • B0037C04
v FI00719
B0037200 B0037200
v FI00702
Explanation: Communications Configuration
B0036322 B0036322 Failing Item:
v UJC35
Explanation: Abandon-call-retry; not all numbers
dialed
B0037210 B0037210
Response:
Explanation: Resource or storage not available
Failing Item:
v UJC36 Failing Item:
v FI00703 v UJC35
v FI00702 v FI00730
v FI00719
v FI00730 B0037212 B0037212
Explanation: Procedure error in vertical Licensed
B0036870 B0036870 Internal Code
Explanation: Automatic call unit power turned off Failing Item:
v AJDG301
Response:
v FI00730
Failing Item:
v FI00703
B0037C00 B0037C00
v FI00702
Explanation: Asynchronous server program ended
v FI00719
abnormally
Failing Item:
B0036890 B0036890
v FI00730
Explanation: Data-set-ready dropped on modem
interface
B0037C02 B0037C02
Response: No action is required if Operations Console
is attached. Explanation: Wrong command sent by vertical
Licensed Internal Code
Failing Item:
Failing Item:
v UJ0E3
v FI00730
v FI00701
v FI00704
B0037C03 B0037C03
v FI00719
Explanation: Resource or storage not available
B0036C05 B0036C05 Failing Item:
Explanation: I/O card Licensed Internal Code error v UJB37
v UJC35
Failing Item:
v FI00730
v FI00730
v AJDG301
B0037C04 B0037C04
B0036C0A B0036C0A Explanation: Wrong internal routing information
Explanation: Hardware detected failure Failing Item:
v FI00730
Response:
Failing Item:
v FI00719
v FI00718
20 System reference codes (Bxxx)
B0037C05 • B003FFFF
B0037C05 B0037C05
Explanation: Error in I/O card Licensed Internal Code
Failing Item:
v FI00730
B0037C09 B0037C09
Explanation: Error in I/O card Licensed Internal Code
Failing Item:
v FI00730
B0038011 B0038011
Explanation: IOP Activation failed.
Response: The MDMCNTRYID parameter in Network
Attributes is not set. Use the CHGNETA command to
set MDMCNTRYID value.
Failing Item:
v UJC37
B0038013 B0038013
Explanation: IOP Activation failed.
Response: The MDMCNTRYID parameter in Network
Attributes is not valid for this adapter. Use the
CHGNETA command to change MDMCNTRYID.
Failing Item:
v UJC37
B0038020 B0038020
Explanation: System log entry only, no service action
required
B003FFFF B003FFFF
Explanation: User suspected communications
problem.
Failing Item:
v USER
(B003) Reference codes 21
22 System reference codes (Bxxx)
(B004) Reference codes
B0047000 B0047000 B004700F B004700F
Explanation: Vertical Licensed Internal Code sent an Explanation: Communications controller storage not
incorrect command available
Failing Item: Failing Item:
v FI00751 v FI00751
v FI00730 v FI00730
B0047002 B0047002 B0047010 B0047010
Explanation: Vertical LIC sent incorrect command Explanation: Vertical LIC sent commands in wrong
values order
Failing Item: Failing Item:
v FI00751 v FI00751
v FI00730 v FI00730
B0047004 B0047004 B0047012 B0047012
Explanation: Vertical LIC sent commands in wrong Explanation: I/O card LIC followed incorrect
order procedure
Failing Item: Failing Item:
v FI00751 v FI00730
v FI00730
B0047014 B0047014
B0047006 B0047006 Explanation: Vertical LIC sent commands in wrong
Explanation: Vertical LIC sent incorrect command order
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B0047018 B0047018
B0047008 B0047008 Explanation: Configuration exceeds allowed
Explanation: Vertical LIC sent incorrect command maximum for X.25 lines
values Failing Item:
Failing Item: v UJJ39
v FI00751
v FI00730 B004701A B004701A
Explanation: Wrong command value sent by IBM i
B004700C B004700C Operating System licensed program
Explanation: Vertical LIC sent commands in wrong Failing Item:
order v AJDG301
Failing Item: v FI00730
v FI00751
v FI00730 B004701C B004701C
Explanation: Wrong command value sent by IBM i
© Copyright IBM Corp. 2010, 2013 23
B004701E • B0047054
Operating System licensed program Failing Item:
Failing Item: v UJJ37
v AJDG301 v FI00751
v FI00730
B0047048 B0047048
B004701E B004701E Explanation: Vertical LIC sent incorrect command
values
Explanation: Wrong command value sent by IBM i
Operating System licensed program Failing Item:
Failing Item: v FI00751
v UJJ36 v FI00730
v FI00730
B0047049 B0047049
B0047020 B0047020 Explanation: Vertical LIC sent incorrect command
values
Explanation: Vertical LIC sent incorrect command
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B004704A B004704A
B0047024 B0047024 Explanation: Vertical LIC sent incorrect command
values
Explanation: No logical link available for packet
network Failing Item:
Failing Item: v FI00751
v UJE38 v FI00730
v FI00751
B004704C B004704C
B0047028 B0047028 Explanation: Vertical LIC sent incorrect command
values
Explanation: No outgoing or two-way logical link
available Failing Item:
Failing Item: v FI00751
v UJE38 v FI00730
v FI00751
B0047050 B0047050
B004702C B004702C Explanation: Vertical LIC sent commands in wrong
order
Explanation: Remote station not connected
Failing Item:
Response: This reference code usually identifies a
condition that is due to a timing problem that will be v FI00751
recovered. v FI00730
Failing Item:
v UJJ37 B0047054 B0047054
v FI00751 Explanation: Vertical Licensed Internal Code sent
wrong password length
B0047030 B0047030 Failing Item:
Explanation: Logical link already disconnected v FI00751
v FI00730
Response: This reference code usually identifies a
condition that is due to a timing problem that will be
recovered.
24 System reference codes (Bxxx)
B0047056 • B0047718
v FI00730
B0047056 B0047056
Explanation: Vertical LIC sent incorrect command
B0047090 B0047090
values
Explanation: I/O card LIC followed incorrect
Failing Item:
procedure
v FI00751
Failing Item:
v FI00730
v FI00751
v FI00730
B0047058 B0047058
Explanation: Vertical LIC sent incorrect command
B0047092 B0047092
values
Explanation: Vertical LIC sent incorrect command
Failing Item:
values
v FI00751
Failing Item:
v FI00730
v UJJ38
v FI00751
B004705C B004705C
v FI00730
Explanation: Vertical LIC sent incorrect command
values
B0047094 B0047094
Failing Item:
Explanation: Vertical LIC sent incorrect command
v FI00751
values
v FI00730
Failing Item:
v FI00751
B0047064 B0047064
v FI00730
Explanation: Vertical Licensed Internal Code sent
wrong data length
B004728C B004728C
Failing Item:
Explanation: Vertical LIC sent incorrect command
v FI00751
values
v FI00730
Failing Item:
v FI00730
B004707C B004707C
Explanation: Vertical LIC sent incorrect command
B00472F0 B00472F0
values
Explanation: I/O card Licensed Internal Code ended
Failing Item:
abnormally
v FI00751
Failing Item:
v FI00730
B0047080 B0047080
Explanation: Vertical Licensed Internal Code sent an
B00472F2 B00472F2
incorrect command
Explanation: I/O card Licensed Internal Code stopped
Failing Item:
because of error
v FI00751
Failing Item:
v FI00730
v FI00730
B0047084 B0047084
B0047718 B0047718
Explanation: Number of user requests more than
maximum allowed Explanation: Network procedure error detected by
I/O card lic int code
Failing Item:
Failing Item:
v FI00751
v UJJ36
(B004) Reference codes 25
B0047740 • B00477A6
v UJ0E2 v UJJ37
B0047740 B0047740 B0047794 B0047794
Explanation: Remote system sent disconnect Explanation: Expected password not provided by
command remote system
Failing Item: Failing Item:
v UJ0E2 v UJ0E2
B0047744 B0047744 B0047798 B0047798
Explanation: Remote system sent disconnect mode Explanation: Remote system did not respond to test
frame command
Failing Item: Failing Item:
v UJ0E2 v UJ0E2
v UJJ36
B0047768 B0047768
Explanation: Remote system did not respond to B00477A0 B00477A0
command sent Explanation: Checksum error; error limit per 256
Failing Item: reached
v UJJ36 Failing Item:
v UJ0E2 v UJ0E2
v UJ0E9
B004776C B004776C v FI00730
Explanation: Remote system did not respond to
command sent B00477A2 B00477A2
Failing Item: Explanation: Bad data sent; error limit per 256
v UJ0E2 reached
v UJJ36 Failing Item:
v UJ0E9
B0047770 B0047770
Explanation: Remote system did not respond to B00477A4 B00477A4
disconnect command Explanation: Bad data received; error limit per 256
Failing Item: reached
v UJJ36 Failing Item:
v UJ0E2 v UJ0E9
v UJJ35
B0047774 B0047774
Explanation: Remote system did not verify receiving B00477A6 B00477A6
data Explanation: Remote system not ready; error limit per
Failing Item: 256 reached
v UJJ36 Failing Item:
v UJ0E2 v UJ0E2
v UJ0E9
B0047788 B0047788 v UJJ35
Explanation: Call rejected; wrong value from remote
system
Failing Item:
v UJ0E6
26 System reference codes (Bxxx)
B0047800 • B0047840
v FI00730
B0047800 B0047800
Explanation: Vertical Licensed Internal Code sent an
B0047812 B0047812
incorrect command
Explanation: Procedure error in vertical Licensed
Failing Item:
Internal Code
v FI00751
Failing Item:
v FI00730
v FI00751
B0047802 B0047802
B0047820 B0047820
Explanation: Vertical LIC sent incorrect command
values Explanation: Too many logical channels defined
Failing Item: Failing Item:
v FI00751 v UJJ36
v FI00730 v FI00730
B0047804 B0047804 B0047824 B0047824
Explanation: Vertical LIC sent commands in wrong Explanation: Outgoing and two-way logical channel
order not available
Failing Item: Response: This reference code usually identifies a
condition that is due to a timing problem that will be
v FI00751
recovered.
v FI00730
Failing Item:
v UJJ37
B0047806 B0047806
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B0047828 B0047828
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B0047808 B0047808
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B004782C B004782C
v FI00751
Explanation: Vertical LIC sent commands in wrong
v FI00730
order
Failing Item:
B004780C B004780C
v FI00751
Explanation: Vertical LIC sent commands in wrong
v FI00730
order
Failing Item:
B0047840 B0047840
v FI00751
Explanation: Vertical LIC sent incorrect command
values
B0047810 B0047810
Failing Item:
Explanation: Vertical LIC sent commands in wrong
v AJDG301
order
v FI00730
Failing Item:
v FI00751
(B004) Reference codes 27
B0047842 • B0047860
v FI00751
B0047842 B0047842
v FI00730
Explanation: Vertical LIC sent incorrect command
values
B0047854 B0047854
Failing Item:
Explanation: Vertical LIC sent incorrect command
v AJDG301
values
v FI00730
Failing Item:
v FI00751
B0047844 B0047844
v FI00730
Explanation: Vertical LIC sent incorrect command
values
B0047857 B0047857
Failing Item:
Explanation: Vertical LIC sent incorrect command
v AJDG301
values
v FI00730
Failing Item:
v AJDG301
B0047846 B0047846
v FI00730
Explanation: Communications controller storage not
available
B0047858 B0047858
Failing Item:
Explanation: Vertical LIC sent incorrect command
v FI00751
values
v FI00730
Failing Item:
v FI00751
B004784C B004784C
v FI00730
Explanation: Vertical LIC sent incorrect command
values
B004785A B004785A
Failing Item:
Explanation: Application sent invalid Q/M bit request
v FI00751
sequence
v FI00730
Failing Item:
v UJ0E6
B004784D B004784D
v AJDG301
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B004785C B004785C
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B004784E B004784E
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B0047860 B0047860
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B0047850 B0047850
v UJJ38
Explanation: Vertical LIC sent incorrect command
values
Failing Item:
28 System reference codes (Bxxx)
B0047864 • B004788C
B0047864 B0047864 B0047876 B0047876
Explanation: Vertical LIC sent incorrect command Explanation: Wrong command value sent by IBM i
values Operating System licensed program
Failing Item: Failing Item:
v UJJ38 v AJDG301
v FI00751 v FI00730
v FI00730
B0047878 B0047878
B0047868 B0047868 Explanation: Vertical LIC sent incorrect command
Explanation: Vertical LIC sent incorrect command values
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B004787A B004787A
B004786C B004786C Explanation: PLC/HDLC DTE/DCE mode configured
Explanation: Vertical LIC sent incorrect command not valid
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B004787C B004787C
B0047870 B0047870 Explanation: Vertical LIC sent incorrect command
Explanation: Vertical LIC sent incorrect command values
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B0047884 B0047884
B0047872 B0047872 Explanation: Procedure error in vertical Licensed
Explanation: Wrong command value sent by IBM i Internal Code
Operating System licensed program Failing Item:
Failing Item: v FI00751
v AJDG301 v FI00730
v FI00730
B0047888 B0047888
B0047874 B0047874 Explanation: Procedure error in vertical Licensed
Explanation: Vertical LIC sent incorrect command Internal Code
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B004788C B004788C
Explanation: Vertical LIC sent commands in wrong
order
Response: This reference code usually identifies a
(B004) Reference codes 29
B0047894 • B0047F1C
condition that is due to a timing problem that will be
B0047A90 B0047A90
recovered.
Explanation: I/O card Licensed Internal Code used
Failing Item:
incorrect value
v UJJ37
Failing Item:
v FI00751
v FI00730
v IOA
v FI00701
B0047AF0 B0047AF0
B0047894 B0047894 Explanation: I/O card Licensed Internal Code stopped
because of error
Explanation: Procedure error in vertical Licensed
Internal Code Failing Item:
v FI00730
Failing Item:
v FI00751
B0047AF4 B0047AF4
v FI00730
Explanation: I/O card Licensed Internal Code stopped
because of error
B0047898 B0047898
Failing Item:
Explanation: Vertical LIC sent commands in wrong
order v FI00751
v FI00730
Failing Item:
v FI00751
B0047F14 B0047F14
v FI00730
Explanation: Reset packet received
B00478A0 B00478A0 Failing Item:
Explanation: No incoming call available to be v UJ0E9
processed v UJ0E2
Response: This reference code usually identifies a v UJJ36
condition that is due to a timing problem that will be v UJJ35
recovered.
Failing Item: B0047F18 B0047F18
v UJJ37 Explanation: Clear packet received
v FI00730
Failing Item:
v UJ0E9
B00478A4 B00478A4
v UJJ39
Explanation: I/O card Licensed Internal Code used v UJ0E2
incorrect value
v UJJ36
Failing Item: v FI00751
v FI00751
v FI00730 B0047F1C B0047F1C
Explanation: X.25 restart packet received
B00478A6 B00478A6
Failing Item:
Explanation: Vertical LIC sent incorrect command
v UJ0E9
values
v UJJ36
Failing Item:
v FI00751
v FI00730
30 System reference codes (Bxxx)
B0047F30 • B0047FB1
B0047F30 B0047F30 B0047F40 B0047F40
Explanation: X.25 reset request packet sent Explanation: Time-out on reset packet
Failing Item: Failing Item:
v UJJ36 v UJ0E9
v UJ0E9 v UJJ36
B0047F34 B0047F34 B0047F44 B0047F44
Explanation: X.25 clear request packet sent Explanation: Time-out on call packet
Failing Item: Failing Item:
v UJJ36 v UJ0E9
v UJ0E9 v UJJ36
B0047F35 B0047F35 B0047F48 B0047F48
Explanation: X.25 clear packet sent, packet size Explanation: Time-out on clear packet
negotiation failed
Failing Item:
Failing Item: v UJ0E9
v UJ0E9 v UJJ36
v UJJ35
B0047F80 B0047F80
B0047F36 B0047F36
Explanation: Packet network used wrong procedures
Explanation: X.25 clear packet sent, window size
Failing Item:
negotiation failed
v UJ0E9
Failing Item:
v UJA36
v UJ0E9
v UJJ35
B0047FA8 B0047FA8
Explanation: Received packet to help diagnosis
B0047F38 B0047F38
Failing Item:
Explanation: X.25 restart request packet sent
v UJ0E9
Failing Item:
v FI00730
v UJ0E9
v UJJ36
B0047FB0 B0047FB0
Explanation: Restart packet sent; error limit per 256
B0047F3A B0047F3A
reached
Explanation: X.32 restart negotiation failed
Failing Item:
Failing Item: v UJ0E9
v UJ0E9
v UJJ39 B0047FB1 B0047FB1
Explanation: Reset packet received; error limit per 256
B0047F3C B0047F3C reached
Explanation: Time-out on restart packet Failing Item:
Failing Item: v UJ0E9
v UJ0E9 v UJ0E2
v UJJ36
v UJJ35
(B004) Reference codes 31
32 System reference codes (Bxxx)
(B005) Reference codes
B005A000 B005A000 B005A007 B005A007
Explanation: Input value error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
B005A001 B005A001 B005A008 B005A008
Explanation: Input value error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
B005A002 B005A002 B005A009 B005A009
Explanation: Input value error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
B005A003 B005A003 B005A00A B005A00A
Explanation: Procedure error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
B005A004 B005A004 B005A00B B005A00B
Explanation: Input value error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
B005A005 B005A005 B005A00C B005A00C
Explanation: Input value error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
B005A006 B005A006 B005A00E B005A00E
Explanation: Input value error in I/O card Licensed Explanation: Procedure error in vertical Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
© Copyright IBM Corp. 2010, 2013 33
B005A010 • B005A01E
v PTFSRCH
B005A010 B005A010
Explanation: Input value error in I/O card Licensed
B005A018 B005A018
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A011 B005A011
Explanation: Input value error in I/O card Licensed
B005A019 B005A019
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A012 B005A012
Explanation: Input value error in I/O card Licensed
B005A01A B005A01A
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A013 B005A013
Explanation: Wrong config data given to local area
B005A01B B005A01B
network controller
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A014 B005A014
Explanation: Input value error in I/O card Licensed
B005A01C B005A01C
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A015 B005A015
Explanation: Input value error in I/O card Licensed
B005A01D B005A01D
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A016 B005A016
Explanation: Input value error in I/O card Licensed
B005A01E B005A01E
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A017 B005A017
Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
34 System reference codes (Bxxx)
B005A01F • B005A02F
v PTFSRCH
B005A01F B005A01F
Explanation: Input value error in I/O card Licensed
B005A028 B005A028
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
B005A029 B005A029
B005A020 B005A020
Explanation: Procedure error in I/O card Licensed
Explanation: Input value error in I/O card Licensed Internal Code
Internal Code
Failing Item:
Failing Item:
v PTFSRCH
v PTFSRCH
B005A02A B005A02A
B005A021 B005A021
Explanation: Input value error in I/O card Licensed
Explanation: Input value error in I/O card Licensed Internal Code
Internal Code
Failing Item:
Failing Item:
v PTFSRCH
v PTFSRCH
B005A02B B005A02B
B005A022 B005A022
Explanation: Input value error in I/O card Licensed
Explanation: Input value error in I/O card Licensed Internal Code
Internal Code
Failing Item:
Failing Item:
v PTFSRCH
v PTFSRCH
B005A02C B005A02C
B005A023 B005A023
Explanation: Input value error in I/O card Licensed
Explanation: Input value error in I/O card Licensed Internal Code
Internal Code
Failing Item:
Failing Item:
v PTFSRCH
v PTFSRCH
B005A02D B005A02D
B005A024 B005A024
Explanation: Input value error in I/O card Licensed
Explanation: Input value error in I/O card Licensed Internal Code
Internal Code
Failing Item:
Failing Item:
v PTFSRCH
v PTFSRCH
B005A02E B005A02E
B005A025 B005A025
Explanation: Wrong frame received from remote
Explanation: Procedure error in I/O card Licensed equipment
Internal Code
Failing Item:
Failing Item:
v UJE39
v PTFSRCH
B005A02F B005A02F
B005A027 B005A027
Explanation: Input value error in I/O card Licensed
Explanation: Input value error in I/O card Licensed Internal Code
Internal Code
Failing Item:
Failing Item:
v PTFSRCH
(B005) Reference codes 35
B005A201 • B005A402
v PTFSRCH
B005A201 B005A201
Explanation: Token-Ring controller storage not
B005A209 B005A209
available
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A202 B005A202
Explanation: Input value error in I/O card Licensed
B005A20A B005A20A
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A203 B005A203
Explanation: Input value error in I/O card Licensed
B005A20B B005A20B
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A204 B005A204
Explanation: Input value error in I/O card Licensed
B005A20C B005A20C
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A205 B005A205
Explanation: I/O card Licensed Internal Code
B005A213 B005A213
received unexpected response
Explanation: Severe error detected by I/O card
Failing Item:
Licensed Internal Code
v AJGJQ01
Failing Item:
v PTFSRCH
B005A206 B005A206
Explanation: Input value error in I/O card Licensed
B005A214 B005A214
Internal Code
Explanation: Severe error detected by I/O card
Failing Item:
Licensed Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005A207 B005A207
Explanation: Input value error in I/O card Licensed
B005A402 B005A402
Internal Code
Explanation: Token-ring adapter card error
Failing Item:
v PTFSRCH Failing Item:
v IOA
B005A208 B005A208 v PTFSRCH
Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
36 System reference codes (Bxxx)
B005A403 • B005A415
B005A403 B005A403 B005A40C B005A40C
Explanation: Token-ring adapter card error Explanation: Token-ring adapter card error
Failing Item: Failing Item:
v IOA v IOA
B005A404 B005A404 B005A410 B005A410
Explanation: Token-ring adapter card error Explanation: Ring status information logged; not
serious
Failing Item:
v IOA Failing Item:
v UJE37 v UJE37
v FI00712
B005A405 B005A405 v FI00701
Explanation: Token-ring adapter card error
B005A411 B005A411
Failing Item:
Explanation: Ring status information logged; not
v IOA
serious
Failing Item:
B005A406 B005A406
v IOA
Explanation: Token-ring adapter card error
v UJE33
Failing Item:
v IOA B005A412 B005A412
Explanation: Ring status information logged; not
B005A408 B005A408 serious
Explanation: Ring status information logged; not Failing Item:
serious
v UJE33
Failing Item: v IOA
v UJE37
B005A413 B005A413
B005A409 B005A409
Explanation: Ring status information logged; serious
Explanation: Severe error detected by I/O card
Failing Item:
Licensed Internal Code
v FI00701
Failing Item:
v FI00712
v IOA
v IOA
B005A40A B005A40A
B005A414 B005A414
Explanation: Token-ring adapter card error
Explanation: Ring status information logged; serious
Failing Item:
Failing Item:
v IOA
v IOA
v FI00701
B005A40B B005A40B
v FI00712
Explanation: Token-ring adapter card error
Failing Item: B005A415 B005A415
v IOA Explanation: Ring status information logged; serious
Failing Item:
v UJE31
(B005) Reference codes 37
B005A416 • B005A42A
v UJE37 The card must be varied off before changing the line
speed.
B005A416 B005A416 Failing Item:
Explanation: Ring status information logged; not v UJE37
serious v UJE35
Failing Item: v FI00712
v UJE37 v IOA
B005A417 B005A417 B005A425 B005A425
Explanation: Wrong frame received from remote Explanation: Input value error in I/O card Licensed
equipment Internal Code
Failing Item: Failing Item:
v UJE37 v UJE35
B005A420 B005A420 B005A426 B005A426
Explanation: Token-ring adapter card error Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
Failing Item:
v IOA
v UJE32
v FI00712
v UJE37
v FI00701
B005A427 B005A427
B005A421 B005A421
Explanation: Input value error in I/O card Licensed
Explanation: Token-ring adapter card error
Internal Code
Failing Item:
Failing Item:
v UJE37
v UJE31
v FI00712
v UJE37
v FI00701
B005A428 B005A428
B005A422 B005A422
Explanation: Token-ring adapter card error
Explanation: Token-ring adapter card error
Failing Item:
Failing Item:
v PTFSRCH
v FI00701
v FI00712
B005A429 B005A429
v IOA
Explanation: Procedure error in I/O card Licensed
Internal Code
B005A423 B005A423
Failing Item:
Explanation: Token-ring adapter card error
v UJE37
Failing Item: v FI00712
v UJE37 v FI00701
v IOA
B005A42A B005A42A
B005A424 B005A424
Explanation: User suspected communications
Explanation: Token-ring adapter card error problem.
Response: Change the line speed parameter for the Response: The adapter does not support Full
Token-ring card. DUPLEX or did not detect Full Duplex.
Failing Item:
38 System reference codes (Bxxx)
B005A703 • B005B003
v USER
B005A715 B005A715
Explanation: Temporary errors; error limit per 256
B005A703 B005A703
reached
Explanation: Ring status information logged; serious
Failing Item:
Failing Item: v IOA
v IOA v UJE37
v FI00701
v UJE37 B005A716 B005A716
Explanation: Transmit beacon; error limit per 256
B005A710 B005A710 reached
Explanation: Address not recognized; error limit per Failing Item:
256 reached
v IOA
Failing Item: v UJE37
v UJE37
v IOA B005A718 B005A718
v PTFSRCH
Explanation: Status queue overrun; error limit per 256
reached
B005A711 B005A711
Failing Item:
Explanation: Frame not copied; error limit per 256 v UJE38
reached
Failing Item: B005A719 B005A719
v UJE39
Explanation: Frames discarded; error limit per 256
v IOA reached
v PTFSRCH
Failing Item:
v PTFSRCH
B005A712 B005A712
v UJE38
Explanation: Transmit strip; error limit per 256
reached
B005A721 B005A721
Failing Item:
Explanation: Interrupts not expected; error limit per
v IOA 256 reached
v UJE37
Failing Item:
v IOA
B005A713 B005A713
Explanation: Access priority not authorized; error B005B000 B005B000
limit per 256 reached
Explanation: I/O card Licensed Internal Code error
Failing Item:
Failing Item:
v PTFSRCH
v PTFSRCH
B005A714 B005A714
B005B003 B005B003
Explanation: Frames not authorized; error limit per
256 reached Explanation: Procedure error in vertical Licensed
Internal Code
Failing Item:
Failing Item:
v PTFSRCH
v PTFSRCH
(B005) Reference codes 39
B005B006 • B005C0E9
B005B006 B005B006 B005C000 B005C000
Explanation: Token-ring error monitor has stopped Explanation: I/O card Licensed Internal Code error
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
B005B009 B005B009 B005C003 B005C003
Explanation: Procedure error in vertical Licensed Explanation: Configuration report server is
Internal Code deactivating
Failing Item: Failing Item:
v PTFSRCH v PTFSRCH
B005B00A B005B00A B005C005 B005C005
Explanation: Output value error in vertical Licensed Explanation: Configuration report server is activating
Internal Code
Failing Item:
Failing Item: v PTFSRCH
v PTFSRCH
B005C010 B005C010
B005B00B B005B00B
Explanation: Procedure error in vertical Licensed
Explanation: Output value error in vertical Licensed Internal Code
Internal Code
Failing Item:
Failing Item: v PTFSRCH
v PTFSRCH
B005C0E6 B005C0E6
B005B0C0 B005B0C0
Explanation: Procedure error in vertical Licensed
Explanation: Required I/O card Licensed Internal Internal Code
Code not active
Failing Item:
Failing Item: v PTFSRCH
v FI00701
v UJE35 B005C0E7 B005C0E7
v UJE37
Explanation: Output value error in vertical Licensed
v FI00712 Internal Code
v IOA
Failing Item:
v PTFSRCH
B005B300 B005B300
Explanation: Procedure error in vertical Licensed B005C0E8 B005C0E8
Internal Code
Explanation: Output value error in vertical Licensed
Failing Item: Internal Code
v PTFSRCH
Failing Item:
v PTFSRCH
B005B700 B005B700
Explanation: Wrong frame received from remote B005C0E9 B005C0E9
equipment
Explanation: Configuration report server activation
Response: All unit reference codes that start with a failed
value of B7 and end with any value from 00 through
FF have the same meaning as this unit reference code. Failing Item:
v PTFSRCH
40 System reference codes (Bxxx)
B005C0EA • B005FFFF
B005C0EA B005C0EA B005C701 B005C701
Explanation: Configuration report server activation Explanation: Procedure error in vertical Licensed
failed Internal Code
Failing Item:
v PTFSRCH B005C702 B005C702
Explanation: Wrong frame received from remote
B005C0EB B005C0EB equipment
Explanation: Configuration report server activation
failed B005C703 B005C703
Failing Item: Explanation: Wrong frame received from remote
equipment
v PTFSRCH
B005FFFF B005FFFF
B005C0EE B005C0EE
Explanation: User suspected communications
Explanation: I/O card Licensed Internal Code error
problem.
Failing Item:
Failing Item:
v PTFSRCH
v USER
B005C0EF B005C0EF
Explanation: Procedure error in vertical Licensed
Internal Code
Failing Item:
v UJE34
B005C0F4 B005C0F4
Explanation: Required I/O card Licensed Internal
Code not active
Failing Item:
v FI00701
v UJE35
v UJE37
v FI00712
v IOA
B005C300 B005C300
Explanation: Procedure error in vertical Licensed
Internal Code
Failing Item:
v PTFSRCH
B005C700 B005C700
Explanation: Procedure error in vertical Licensed
Internal Code
(B005) Reference codes 41
42 System reference codes (Bxxx)
(B006) Reference codes
v AJEQU00
B0061201 B0061201
v FI00131
Explanation: I/O processor resource not available
v FI00132
Response: A deactivation failed to get a resource
controlled by Licensed Internal Code.
B0061206 B0061206
Failing Item:
Explanation: I/O processor card or Licensed Internal
v AJEQU00 Code error
v AJDG301
Response: A microprocessor exception occurred on the
I/O processor.
B0061202 B0061202
Failing Item:
Explanation: Not valid condition in I/O Processor v AJEQU00
Licensed Internal Code
v FI00131
Response: An error in an activation or deactivation v FI00132
occurred.
Failing Item: B0061207 B0061207
v AJEQU00
Explanation: I/O processor resource not available
v AJDG301
Response: The Licensed Internal Code could not
v FI00131
allocate memory resources on the I/O processor card.
Failing Item:
B0061203 B0061203
v AJEQU00
Explanation: I/O processor resource not available
v AJDG301
Response: A resource needed to perform a requested
function is not available in the Licensed Internal Code.
B0061208 B0061208
Failing Item:
Explanation: Not valid condition in I/O Processor
v AJEQU00 Licensed Internal Code
v AJDG301
Response: The Licensed Internal Code found a
condition that should not have occurred.
B0061204 B0061204
Failing Item:
Explanation: Not valid condition in I/O Processor v AJEQU00
Licensed Internal Code
v AJDG301
Response: The Licensed Internal Code has recovered v FI00131
from a condition that was not expected.
Failing Item: B0061209 B0061209
v AJEQU00
Explanation: I/O processor was not ready for
v AJDG301 interrupt that occurred
v FI00131
Failing Item:
v AJEQU00
B0061205 B0061205
v FI00131
Explanation: I/O processor card or Licensed Internal
Code error
B0061210 B0061210
Response: A microprocessor exception occurred on the
Explanation: I/O processor resource not available
I/O processor.
Response: The I/O processor error log is being filled
Failing Item:
faster than the errors are being reported to the system.
© Copyright IBM Corp. 2010, 2013 43
B0061211 • B0061305
Check other errors reported to the system and correct v AJDG301
them.
B0061302 B0061302
B0061211 B0061211
Explanation: Not valid condition in I/O Processor
Explanation: System bus error Licensed Internal Code
Failing Item: Response: An error in an activation or deactivation
v FI00131 occurred.
v ANYBUS Failing Item:
v AJEQU00 v AJDGP01
v AJDG301 v AJDG301
v FI00131
B0061212 B0061212 v FI00132
Explanation: A permanent I/O processor failure
occurred B0061303 B0061303
Failing Item: Explanation: I/O processor resource not available
v FI00131 Response: A resource needed to perform a requested
v AJEQU00 function is not available in the Licensed Internal Code.
Failing Item:
B0061213 B0061213 v IOACNFG
Explanation: System bus error v AJDGP01
Failing Item: v AJDG301
v AJDG301
v AJEQU00 B0061304 B0061304
v FI00131 Explanation: Not valid condition in I/O Processor
Licensed Internal Code
B0061214 B0061214 Response: The Licensed Internal Code has recovered
from an unexpected condition.
Explanation: I/O processor card or Licensed Internal
Code error Failing Item:
Failing Item: v AJDGP01
v FI00131 v AJDG301
v AJEQU00 v FI00131
v FI00132
B0061215 B0061215
B0061305 B0061305
Explanation: I/O processor card or Licensed Internal
Code error Explanation: I/O processor card or Licensed Internal
Code error
Failing Item:
v FI00131 Response: A microprocessor exception occurred on the
I/O processor.
v AJEQU00
Failing Item:
B0061301 B0061301 v AJDGP01
v FI00131
Explanation: I/O processor resource not available
v FI00132
Response: An activation or deactivation failed to get a
v BACKPLN
resource controlled by Licensed Internal Code.
Failing Item:
v UJE38
v AJDGP01
44 System reference codes (Bxxx)
B0061306 • B0061317
B0061306 B0061306 B0061311 B0061311
Explanation: I/O processor card or Licensed Internal Explanation: System bus error
Code error
Failing Item:
Response: A microprocessor exception occurred on the v FI00131
I/O processor.
v ANYBUS
Failing Item: v AJDGP01
v AJDGP01 v AJDG301
v FI00131
v FI00132 B0061312 B0061312
v BACKPLN
Explanation: A permanent I/O processor failure
occurred
B0061307 B0061307
Failing Item:
Explanation: I/O processor resource not available v FI00131
Response: The Licensed Internal Code could not v AJDGP01
allocate memory resources on the I/O processor card.
Failing Item: B0061313 B0061313
v AJDGP01 Explanation: System bus error
v AJDG301
Failing Item:
v IOACNFG
v AJDG301
v FI00132
v AJDGP01
v FI00131
B0061308 B0061308
Explanation: Not valid condition in I/O Processor B0061316 B0061316
Licensed Internal Code
Explanation: I/O processor card or Licensed Internal
Response: The Licensed Internal Code found a Code error
condition that should not have occurred.
Failing Item:
Failing Item:
v AJDGP01
v AJDGP01
v FI00132
v AJDG301
v FI00131
v FI00131
B0061317 B0061317
B0061309 B0061309
Explanation: I/O processor card error
Explanation: I/O processor was not ready for
interrupt that occurred Response: Display the Service Action Log entry for
this SRC. If the Failing Item indicates IOP, then replace
Failing Item: the IOP. If the Failing Item indicates SVCDOCS, then
v AJDGP01 do NOT replace the IOP. This is a recoverable error.
v FI00131 Perform the following:
v FI00132 1. If the I/O Processor is not operable and disk units
v FI01117 are attached, use Hardware Service Manager to re-IPL
the IOP. Other resources attached to the IOP may then
need to be Varied On.
B0061310 B0061310
2. If disk units are not attached, perform the VRYCFG
Explanation: I/O processor resource not available RESET(*YES) command to reset the IOP and Vary On
Response: The I/O processor error log is being filled attached resources.
faster than the errors are being reported to the system. Failing Item:
Check other errors reported to the system and correct
v SVCDOCS
them.
(B006) Reference codes 45
B0061318 • B0061A03
allocate resources on the Service processor.
B0061318 B0061318
Failing Item:
Explanation: I/O processor card error
v AJDGP01
Failing Item:
v SVCPROC
v FI00131
v AJDG301
B0061403 B0061403
B0061408 B0061408
Explanation: Service processor Licensed Internal Code
Explanation: Service processor Licensed Internal Code
error
failed
Response: A resource needed to perform a requested
Failing Item:
function is not available in the Licensed Internal Code.
v AJDGP01
Failing Item:
v AJDG301
v AJDGP01
v SVCPROC
v SVCPROC
B0061409 B0061409
B0061404 B0061404
Explanation: Service processor Licensed Internal Code
Explanation: Service processor Licensed Internal Code failed
error
Response: The Service processor was not ready for an
Response: The Licensed Internal Code has recovered interrupt that occurred.
from an unexpected condition.
Failing Item:
Failing Item:
v AJDGP01
v AJDGP01
v SVCPROC
v SVCPROC
B0061A01 B0061A01
B0061405 B0061405
Explanation: I/O processor resource not available
Explanation: Service processor Licensed Internal Code
error Response: A deactivation failed to get a resource
controlled by Licensed Internal Code.
Response: A recoverable microcode condition
occurred on the Service processor. Failing Item:
v UJE38
Failing Item:
v FI00130
v AJDGP01
v AJDG301
v SVCPROC
B0061A02 B0061A02
B0061406 B0061406
Explanation: Not valid condition in I/O Processor
Explanation: Service processor Licensed Internal Code
Licensed Internal Code
failed
Response: An error in an activation or deactivation
Response: A microprocessor exception occurred on the
occurred.
Service processor.
Failing Item:
Failing Item:
v FI00130
v AJDGP01
v FI00131
v SVCPROC
v FI00132
v AJDG301
B0061A03 B0061A03
B0061407 B0061407
Explanation: I/O processor resource not available
Explanation: Service processor Licensed Internal Code
failed Response: A resource that is needed to perform a
requested function is not available in the Licensed
Response: The Licensed Internal Code could not
Internal Code.
46 System reference codes (Bxxx)
B0061A04 • B0061A10
Failing Item:
B0061A08 B0061A08
v FI00130
Explanation: Not valid condition in I/O Processor
v AJDG301
Licensed Internal Code
v UJE38
Response: The Licensed Internal Code found a
condition that should not have occurred.
B0061A04 B0061A04
Failing Item:
Explanation: Recovered from condition in Licensed
v FI00130
Internal Code.
v FI00131
Response: The Licensed Internal Code has recovered
v FI00132
from a condition that was not expected.
Failing Item:
B0061A09 B0061A09
v FI00130
Explanation: Threshold overflow
v AJDG301
v FI00131 Response: The I/O processor card has detected a
threshold of recoverable error conditions. The errors are
v FI00132
either wrong interruptions or memory error corrections.
If in communications, the line is still running.
B0061A05 B0061A05
If a large number of these errors occur during a short
Explanation: I/O processor card or Licensed Internal time, they may be caused by an electrically noisy
Code error environment, a defective communications I/O
processor card or modem, or a communications I/O
Response: A microprocessor exception occurred on the processor code problem.
I/O processor.
Failing Item:
Failing Item:
v FI00131
v FI00130
v FI00132
v FI00131
v FI01117
v FI00132
v FI00130
B0061A06 B0061A06
B0061A10 B0061A10
Explanation: I/O processor card or Licensed Internal
Code error Explanation: Error reported to system
Response: A microprocessor exception occurred on the Response: The I/O processor error log is being filled
I/O processor. faster than the errors are being reported to the system.
Check other errors reported to the system and correct
Failing Item: them.
v FI00130
v FI00131
v FI00132
B0061A07 B0061A07
Explanation: I/O processor resource not available
Response: The Licensed Internal Code could not
allocate memory resources on the I/O processor card.
Failing Item:
v UJE38
v FI00132
v FI00130
v AJDG301
(B006) Reference codes 47
48 System reference codes (Bxxx)
(B008) Reference codes
B0081200 B0081200 B0081705 B0081705
Explanation: Communications controller task ended Explanation: Frame reject type X received
abnormally; type 1
Failing Item:
Failing Item: v FI00730
v FI00730 v UJ0E3
B0081201 B0081201 B0081706 B0081706
Explanation: Communications controller task ended Explanation: Frame reject type Y received
abnormally; type 2
Failing Item:
Failing Item:
v FI00730
v FI00730
v UJJ35
B0081202 B0081202
B0081707 B0081707
Explanation: Communications controller task ended
Explanation: Frame reject type Z received
abnormally; type 3
Failing Item:
Failing Item:
v FI00730
v FI00730
v UJ0E3
B0081701 B0081701
B0081708 B0081708
Explanation: Disconnect mode frame received
Explanation: Frame reject type W sent
Failing Item:
Failing Item:
v UJ0E9
v UJ0E3
v FI00730
B0081702 B0081702
Explanation: Disconnect mode frame received during
B0081709 B0081709
link activation
Explanation: Frame reject type X sent
Failing Item:
v UJ0E3 Failing Item:
v UJ0E3
B0081703 B0081703 v FI00730
Explanation: Disconnect mode frame received when
transmitting information B008170A B008170A
Failing Item: Explanation: Frame reject type Y sent
v UJ0E3 Failing Item:
v FI00730 v UJJ35
v UJ0E3
B0081704 B0081704
Explanation: Frame reject type W received B008170B B008170B
Failing Item: Explanation: Frame reject type Z sent
v FI00730 Failing Item:
v UJ0E3 v FI00730
v UJ0E3
© Copyright IBM Corp. 2010, 2013 49
B008170C • B0084592
B008170C B008170C B0082654 B0082654
Explanation: Frame retry limit reached Explanation: First call failed, retrying call; CFI ET
from modem
Failing Item:
v UJ0E9 Failing Item:
v FI00701 v UJ0E3
v FI00704 v UJA35
v UJJ35
B0082656 B0082656
B008170D B008170D Explanation: First call failed, retrying call; CFI NT
from modem
Explanation: Set-asynchronous-balance-mode frame
received in data mode Failing Item:
Failing Item: v UJ0E3
v FI00730 v FI00705
v UJ0E3 v UJA35
B008170E B008170E B0082657 B0082657
Explanation: Wrong response received from remote Explanation: First call failed, retrying call; CFI RT
equipment from modem
Failing Item: Failing Item:
v UJJ35 v UJ0E3
v UJ0E3 v UJA35
v FI00700
B0082660 B0082660
B0082651 B0082651 Explanation: Call failed, retrying call; Non-standard
CFI from modem
Explanation: First call failed, retrying call; no CFI
from modem Failing Item:
Failing Item: v UJ0E3
v UJE34 v FI00704
v UJJ35
v FI00704 B008450A B008450A
v FI00701 Explanation: Incorrect command value sent by vertical
LIC
B0082652 B0082652 Failing Item:
Explanation: First call failed, retrying call; CFI AB v AJDG301
from modem
Failing Item: B0084590 B0084590
v UJ0E3 Explanation: Wrong telephone number specified in
v FI00704 system configuration
v UJA35 Failing Item:
v UJA35
B0082653 B0082653 v FI00751
Explanation: First call failed, retrying call; CFI DE
from modem B0084592 B0084592
Failing Item: Explanation: No number specified in controller
v UJ0E3 description
v FI00704 Failing Item:
50 System reference codes (Bxxx)
B0084594 • B0085014
v UJA35
B008500D B008500D
v FI00751
Explanation: Wrong data length received by
communications controller
B0084594 B0084594
Failing Item:
Explanation: Wrong telephone number specified in
v FI00751
system configuration
v UJJ35
Failing Item:
v UJA35
B008500E B008500E
v FI00751
Explanation: Wrong command value received by
communications IOP
B0085000 B0085000
Failing Item:
Explanation: Wrong command received by
v FI00751
communications controller
Failing Item:
B008500F B008500F
v FI00751
Explanation: Wrong command value received by
communications IOP
B0085002 B0085002
Failing Item:
Explanation: Wrong procedure followed by I/O card
v FI00751
Licensed Internal Code
Failing Item:
B0085010 B0085010
v FI00751
Explanation: Wrong reset option received by
communications controller
B0085008 B0085008
Failing Item:
Explanation: Procedure error in vertical Licensed
v FI00751
Internal Code
v FI00730
Failing Item:
v UJE34
B0085011 B0085011
Explanation: Wrong command value received by
B0085009 B0085009
communications IOP
Explanation: Wrong command value received by
Failing Item:
communications IOP
v FI00751
Failing Item:
v FI00730
v FI00751
B0085012 B0085012
B008500B B008500B
Explanation: Wrong session ID received by
Explanation: Wrong command value received by communications controller
communications IOP
Failing Item:
Failing Item:
v FI00751
v FI00751
v FI00730
B008500C B008500C
B0085014 B0085014
Explanation: Wrong command value received by
Explanation: Wrong command value received by
communications IOP
communications IOP
Failing Item:
Failing Item:
v FI00751
v FI00751
v FI00730
(B008) Reference codes 51
B0085015 • B00850E0
B0085015 B0085015 B008501C B008501C
Explanation: Communications line already in use Explanation: Wrong command value received by
communications IOP
Failing Item:
v FI00751 Failing Item:
v FI00730 v FI00730
B0085016 B0085016 B008501E B008501E
Explanation: Wrong command value received by Explanation: Wrong command value received by
communications IOP communications IOP
Failing Item: Failing Item:
v FI00751 v FI00730
v FI00730
B008501F B008501F
B0085017 B0085017 Explanation: Wrong command value received by
communications IOP
Explanation: Wrong storage value received;
communications controller Failing Item:
Failing Item: v FI00730
v FI00751
v FI00730 B0085022 B0085022
Explanation: Port already in use
B0085018 B0085018 Failing Item:
Explanation: Wrong trace type received by v FI00751
communications controller v FI00730
Failing Item:
v FI00751 B0085023 B0085023
v FI00730 Explanation: Procedure error in vertical Licensed
Internal Code
B0085019 B0085019 Failing Item:
Explanation: Wrong trace length received by v FI00751
communications controller
Failing Item: B0085024 B0085024
v FI00751 Explanation: DTE/DCE role negotiation not valid for
v FI00730 leased line
Failing Item:
B008501A B008501A v FI00751
Explanation: Communications controller temporary
storage area too small B00850E0 B00850E0
Failing Item: Explanation: Wrong or no external communications
v FI00751 cable installed
Failing Item:
B008501B B008501B v UJJ35
Explanation: Wrong ID length value sent by vertical v FI00701
LIC v IOA
Failing Item:
v FI00751
52 System reference codes (Bxxx)
B00850E1 • B00850F5
B00850E1 B00850E1 B00850E9 B00850E9
Explanation: Port already in use Explanation: Wrong command value sent by IBM i
Operating System licensed program
Failing Item:
v UJJ35 Failing Item:
v FI00730 v AJDG301
B00850E3 B00850E3 B00850EC B00850EC
Explanation: Wrong command value sent by IBM i Explanation: Wrong command value sent by IBM i
Operating System licensed program Operating System licensed program
Failing Item: Failing Item:
v AJDG301 v AJDG301
v UJJ35
B00850ED B00850ED
B00850E4 B00850E4 Explanation: Wrong command value sent by IBM i
Operating System licensed program
Explanation: Wrong command value sent by IBM i
Operating System licensed program Failing Item:
Failing Item: v AJDG301
v AJDG301
B00850EE B00850EE
B00850E5 B00850E5 Explanation: Wrong command value sent by IBM i
Operating System licensed program
Explanation: Wrong adapter type value sent by
Vertical LIC Failing Item:
Failing Item: v AJDG301
v FI00751
v UJJ35 B00850F1 B00850F1
Explanation: Communications adapter card not
B00850E6 B00850E6 installed
Explanation: Wrong slot number value sent by Failing Item:
Vertical LIC v AJDG301
Failing Item: v UJJ35
v FI00751 v IOA
v UJJ35
B00850F2 B00850F2
B00850E7 B00850E7 Explanation: V.25 adapter not installed
Explanation: Incorrect command value sent by vertical Failing Item:
LIC v UJJ35
Failing Item: v FI00702
v UJJ35 v IOA
v FI00751
B00850F5 B00850F5
B00850E8 B00850E8 Explanation: Network uncontrolled-not-ready
Explanation: Wrong command value sent by IBM i warning; information only
Operating System licensed program Failing Item:
Failing Item: v UJE34
v AJDG301
(B008) Reference codes 53
B00850F6 • B00852EA
B00850F6 B00850F6 B00852E3 B00852E3
Explanation: Network controlled-not-ready warning; Explanation: Wrong response sent by I/O card
information only Licensed Internal Code
Failing Item: Failing Item:
v UJE34 v FI00730
B00850F7 B00850F7 B00852E4 B00852E4
Explanation: Data-set-ready changed to not active; for Explanation: Wrong command value sent by IBM i
information only Operating System licensed program
Failing Item: Failing Item:
v UJE34 v AJDG301
B0085203 B0085203 B00852E5 B00852E5
Explanation: I/O card Licensed Internal Code Explanation: Wrong command value received by
resource not available communications IOP
Failing Item: Failing Item:
v FI00730 v FI00730
B0085206 B0085206 B00852E7 B00852E7
Explanation: Communications controller storage not Explanation: X.21 network not in the ready or
available receive-data state
Failing Item: Failing Item:
v FI00730 v FI00704
v IOA
B00852E0 B00852E0 v FI00701
Explanation: Incorrect command used by I/O card
Licensed Internal Code B00852E8 B00852E8
Failing Item: Explanation: Error when releasing communications
v FI00730 controller storage
Failing Item:
B00852E1 B00852E1 v FI00730
Explanation: Wrong procedure followed by I/O card
Licensed Internal Code B00852E9 B00852E9
Failing Item: Explanation: Error when assigning communications
v FI00730 controller storage
Failing Item:
B00852E2 B00852E2 v FI00730
Explanation: I/O card Licensed Internal Code
resource not available B00852EA B00852EA
Failing Item: Explanation: I/O card Licensed Internal Code error
v FI00730 Failing Item:
v UJJ35 v FI00730
54 System reference codes (Bxxx)
B0085301 • B008560B
v FI00702
B0085301 B0085301
v IOA
Explanation: Adapter card receive error
Failing Item: B00854E1 B00854E1
v IOA
Explanation: Port not operational
Failing Item:
B0085302 B0085302
v IOA
Explanation: Adapter card transmit error
v UJJ35
Failing Item:
v IOA B0085600 B0085600
Explanation: Clear-to-send off; error limit per 256
B0085401 B0085401 reached
Explanation: Communications IOP interrupt not Failing Item:
expected
v FI00704
Failing Item:
v IOA B0085601 B0085601
Explanation: Data-set-ready state changed; error limit
B0085410 B0085410 per 256 reached
Explanation: Data-set-ready error on modem interface Failing Item:
Failing Item: v FI00704
v FI00704
v FI00702 B0085602 B0085602
v IOA Explanation: Clear-to-send state changed; error limit
per 256 reached
B0085472 B0085472 Failing Item:
Explanation: Data-line-occupied initially 'on' error v FI00704
Failing Item:
v FI00702 B0085603 B0085603
v FI00703 Explanation: Carrier-detect state changed; error limit
v UJ0E3 per 256 reached
v IOA Failing Item:
v FI00701
B0085474 B0085474 v FI00704
Explanation: Automatic call unit has v FI00705
data-line-occupied error v UJ0E3
Failing Item:
v FI00702 B008560B B008560B
v FI00703 Explanation: Data-set-ready error; error limit per 256
v UJ0E3 reached
v IOA Failing Item:
v FI00701
B0085476 B0085476 v FI00704
Explanation: Automatic call unit has v UJ0E3
present-next-digit error v FI00705
Failing Item:
v FI00703
(B008) Reference codes 55
B0085630 • B00856F1
v FI00701
B0085630 B0085630
v AJDG301
Explanation: Automatic call unit has
distant-station-connected error
B00856EA B00856EA
Failing Item:
Explanation: Clear-to-send signal dropped on modem
v FI00700
interface
v UJ0E3
Failing Item:
v UJJ35
v UJ0E3
v FI00701
v FI00704
v IOA
v UJJ35
v IOA
B0085632 B0085632
v FI00701
Explanation: Automatic call unit has data-set-ready
error
B00856EB B00856EB
Failing Item:
Explanation: Carrier-detect dropped on modem
v FI00700
interface
v UJJ35
Failing Item:
v UJA35
v FI00701
v FI00703
v FI00704
v FI00701
v FI00705
v IOA
v UJ0E3
v UJ0E3
v IOA
B0085651 B0085651
B00856EC B00856EC
Explanation: Call failed, no Call Failure Indication
from modem Explanation: Data-set-ready signal turn-off time-out
Failing Item: Failing Item:
v UJE34 v FI00704
v UJJ35 v UJJ35
v FI00704 v FI00701
v FI00701 v IOA
B00856E8 B00856E8 B00856ED B00856ED
Explanation: Clear-to-send not active on modem Explanation: Data-set-ready signal turn-on time-out
interface Failing Item:
Failing Item: v FI00704
v UJ0E3 v IOA
v FI00704 v FI00701
v UJJ35 v AJDG301
v FI00701
v IOA B00856F1 B00856F1
Explanation: Data-set-ready dropped on modem
B00856E9 B00856E9 interface
Explanation: Clear-to-send signal failed to drop on Failing Item:
modem interface v FI00704
Failing Item: v FI00705
v FI00704 v UJ0E3
v IOA v FI00701
56 System reference codes (Bxxx)
B0085718 • B00857F1
v IOA v FI00705
v FI00704
B0085718 B0085718 v UJ0E3
Explanation: SABM response or UA command
received B00857E3 B00857E3
Failing Item: Explanation: Abnormal end received; error limit per
v UJJ35 256 reached
v UJ0E3 Failing Item:
v FI00751
B0085719 B0085719 v FI00700
Explanation: Protocol mismatch during link v FI00705
initialization v FI00704
Failing Item: v UJ0E3
v UJA35
v FI00700 B00857E4 B00857E4
v UJ0E3 Explanation: Underrun threshold error; limit per 256
reached
B0085721 B0085721 Failing Item:
Explanation: Could not send frame to remote v IOA
equipment; local problem
Failing Item: B00857E5 B00857E5
v FI00704 Explanation: Long frame; error limit per 256 reached
v AJDG301 Failing Item:
v FI00701 v UJJ35
v IOA v FI00751
v FI00700
B00857E0 B00857E0
Explanation: Frame check error; error limit per 256 B00857F0 B00857F0
reached
Explanation: Send sequence counter error; error limit
Failing Item: per 256 reached
v UJ0E3 Failing Item:
v FI00705 v FI00751
v FI00704 v FI00701
v FI00704
B00857E1 B00857E1 v UJ0E3
Explanation: Overrun error; error limit per 256
reached B00857F1 B00857F1
Failing Item: Explanation: Receive sequence counter error; error
v UJJ35 limit per 256 reached
v FI00751 Failing Item:
v FI00751
B00857E2 B00857E2 v FI00700
Explanation: Short frame error; error limit per 256
reached
Failing Item:
v FI00700
v FI00751
(B008) Reference codes 57
B00857F2 • B008FFFF
B00857F2 B00857F2 B0086870 B0086870
Explanation: Response time-out error; error limit per Explanation: Automatic call unit power turned off
256 reached
Failing Item:
Failing Item: v FI00703
v FI00700 v FI00702
v UJ0E3 v IOA
v FI00751
v FI00704 B0088011 B0088011
v UJJ35
Explanation: IOP Activation failed.
v FI00705
Response: The MDMCNTRYID parameter in Network
v AJDG301
Attributes is not set. Use the CHGNETA command to
set MDMCNTRYID.
B0085886 B0085886
Failing Item:
Explanation: Automatic call unit switched link v UJE34
time-out; no answer
Failing Item: B0088013 B0088013
v FI00703
Explanation: IOP Activation failed.
v IOA
Response: The MDMCNTRYID parameter in Network
v FI00702
Attributes is not valid for this adapter. Use the
v UJ0E3 CHGNETA command to change the MDMCNTRYID
value.
B0085E01 B0085E01 Failing Item:
Explanation: Call error; incoming call received during v UJE34
outgoing call
Failing Item: B0088020 B0088020
v UJ0E3 Explanation: User suspected communications
problem.
B0086320 B0086320
Explanation: Automatic call unit has abandon-call B008DA00 B008DA00
attempt Explanation: The I/O card LIC detected an internal
Failing Item: error
v FI00700 Failing Item:
v UJA35 v FI00730
v FI00703
v IOA B008DA01 B008DA01
v FI00702 Explanation: The I/O card LIC detected an internal
error
B0086322 B0086322 Failing Item:
Explanation: Abandon call retry error; incorrect v FI00730
number length v IOA
Failing Item:
v UJA35 B008FFFF B008FFFF
v FI00703 Explanation: User suspected communications
problem.
Failing Item:
v USER
58 System reference codes (Bxxx)
(B009) Reference codes
v UJE35
B009A000 B009A000
Explanation: Input value error in I/O card Licensed
B009A01B B009A01B
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v FI00730
Failing Item:
v AJDG301
B009A001 B009A001
Explanation: Input value error in I/O card Licensed
B009A01C B009A01C
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v FI00730
Failing Item:
v AJDG301
v AJDG301
B009A002 B009A002
B009A01D B009A01D
Explanation: Input value error in I/O card Licensed
Internal Code Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
Failing Item:
v FI00730
v AJDG301
B009A003 B009A003
B009A01F B009A01F
Explanation: Procedure error in I/O card Licensed
Internal Code Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
Failing Item:
v FI00730
v FI00730
v AJDG301
B009A009 B009A009
Explanation: Input value error in I/O card Licensed
B009A020 B009A020
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v AJDG301
Failing Item:
v FI00730
B009A00A B009A00A
Explanation: Input value error in I/O card Licensed
B009A022 B009A022
Internal Code
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v AJDG301
Failing Item:
v AJDG301
B009A013 B009A013
Explanation: Wrong configuration data given to
B009A023 B009A023
Ethernet controller
Explanation: Input value error in I/O card Licensed
Failing Item:
Internal Code
v AJDG301
© Copyright IBM Corp. 2010, 2013 59
B009A024 • B009A20A
Failing Item:
B009A201 B009A201
v AJDG301
Explanation: Ethernet controller storage not available
B009A024 B009A024 Failing Item:
v FI00730
Explanation: Input value error in I/O card Licensed
Internal Code
B009A203 B009A203
Failing Item:
v AJDG301 Explanation: Input value error in I/O card Licensed
Internal Code
B009A027 B009A027 Failing Item:
v AJDG301
Explanation: Input value error in I/O card Licensed
Internal Code
B009A204 B009A204
Failing Item:
v FI00730 Explanation: Input value error in I/O card Licensed
Internal Code
B009A028 B009A028 Failing Item:
v AJDG301
Explanation: Input value error in I/O card Licensed
Internal Code
B009A205 B009A205
Failing Item:
v FI00730 Explanation: I/O card Licensed Internal Code
received incorrect response
v AJDG301
Failing Item:
B009A02A B009A02A v FI00730
Explanation: Input value error in I/O card Licensed
Internal Code B009A206 B009A206
Failing Item: Explanation: Input value error in I/O card Licensed
Internal Code
v FI00730
Failing Item:
B009A02B B009A02B v AJDG301
Explanation: Input value error in I/O card Licensed
Internal Code B009A208 B009A208
Failing Item: Explanation: Input value error in I/O card Licensed
Internal Code
v AJDG301
Failing Item:
B009A02C B009A02C v AJDG301
Explanation: Input value error in I/O card Licensed
Internal Code B009A209 B009A209
Failing Item: Explanation: Input value error in I/O card Licensed
Internal Code
v AJDG301
Failing Item:
B009A02D B009A02D v AJDG301
Explanation: Input value error in I/O card Licensed
Internal Code B009A20A B009A20A
Failing Item: Explanation: Input value error in I/O card Licensed
Internal Code
v AJDG301
Failing Item:
v AJDG301
60 System reference codes (Bxxx)
B009A20B • B009A6D3
B009A20B B009A20B B009A42B B009A42B
Explanation: Input value error in I/O card Licensed Explanation: Configuration of DUPLEX parameter not
Internal Code supported by network.
Failing Item: Failing Item:
v AJDG301 v UJE35
v UJE40
B009A20C B009A20C
Explanation: Input value error in I/O card Licensed B009A6C0 B009A6C0
Internal Code Explanation: Ethernet adapter card error
Failing Item: Failing Item:
v FI00730 v UJE39
v AJDG301
B009A6C1 B009A6C1
B009A213 B009A213
Explanation: Input value error in I/O card Licensed
Explanation: Serious error detected by I/O card Internal Code
Licensed Internal Code
Failing Item:
Failing Item: v AJDG301
v FI00730
B009A6C2 B009A6C2
B009A214 B009A214
Explanation: Ethernet adapter card error
Explanation: Serious error detected by I/O card
Failing Item:
Licensed Internal Code
v IOA
Failing Item:
v FI00730
B009A6C5 B009A6C5
Explanation: Ethernet adapter card error
B009A404 B009A404
Failing Item:
Explanation: Ethernet adapter card error
v IOA
Failing Item:
v IOA
B009A6D1 B009A6D1
v UJE40
Explanation: Ethernet adapter card error
B009A40B B009A40B Failing Item:
v FI00720
Explanation: Ethernet adapter card error
v FI00722
Failing Item:
v IOA
B009A6D2 B009A6D2
Explanation: Ethernet adapter card error
B009A42A B009A42A
Failing Item:
Explanation: User suspected communications
problem. v IOA
Response: Full DUPLEX is not supported on this
media type. B009A6D3 B009A6D3
Failing Item: Explanation: Ethernet adapter card error
v USER Response: Verify that the signal quality error switch in
the transceiver that the Ethernet is attached to is set to
active.
Failing Item:
(B009) Reference codes 61
B009A6D4 • B009A6F1
v FI00720
B009A6E2 B009A6E2
v FI00722
Explanation: Ethernet adapter card error
v IOA
Failing Item:
B009A6D4 B009A6D4 v IOA
Explanation: Procedure error in I/O card Licensed
Internal Code B009A6E3 B009A6E3
Failing Item: Explanation: Ethernet transceiver error
v AJDG301 Failing Item:
v UJE40
B009A6D5 B009A6D5 v FI00722
Explanation: Wrong configuration data given to v UJE35
Ethernet controller v IOA
Failing Item:
v AJDG301 B009A6E6 B009A6E6
Explanation: Ethernet transceiver error
B009A6D6 B009A6D6 Failing Item:
Explanation: Wrong configuration data given to v IOA
Ethernet controller
Failing Item: B009A6E7 B009A6E7
v AJDG301 Explanation: Ethernet adapter card error
Failing Item:
B009A6D7 B009A6D7
v IOA
Explanation: Wrong configuration data given to
Ethernet controller
B009A6E8 B009A6E8
Failing Item:
Explanation: Ethernet adapter card error
v AJDG301
Failing Item:
v IOA
B009A6D8 B009A6D8
Explanation: Wrong configuration data given to
B009A6E9 B009A6E9
Ethernet controller
Explanation: Ethernet adapter card error
Failing Item:
v AJDG301 Failing Item:
v UJE40
B009A6D9 B009A6D9 v UJE35
Explanation: Ethernet adapter card error
B009A6F1 B009A6F1
Failing Item:
Explanation: User suspected communications
v IOA
problem.
v FI00722
Response: There are two cables attached to the
v FI00720
adapter and only one is allowed. Remove one cable
and vary off and then vary back on the resource.
B009A6E1 B009A6E1
Failing Item:
Explanation: Ethernet adapter card error v FI00722
Failing Item:
v FI00730
62 System reference codes (Bxxx)
B009A6F2 • B009A80F
B009A6F2 B009A6F2 B009A809 B009A809
Explanation: Configured line speed not supported by Explanation: Input value error in I/O card Licensed
network. Internal Code
Failing Item: Failing Item:
v UJE35 v AJDG301
B009A6F3 B009A6F3 B009A80A B009A80A
Explanation: Configuration of DUPLEX parameter not Explanation: Input value error in I/O card Licensed
supported by network. Internal Code
Failing Item: Failing Item:
v UJE35 v AJDG301
B009A6F4 B009A6F4 B009A80B B009A80B
Explanation: Unable to establish a network link. Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v UJE35 Failing Item:
v FI00722 v AJDG301
v UJE40 v UJE36
v IOA
B009A80C B009A80C
B009A801 B009A801 Explanation: Input value error in I/O card Licensed
Internal Code
Explanation: Input value error in I/O card Licensed
Internal Code Failing Item:
Failing Item: v AJDG301
v AJDG301
B009A80D B009A80D
B009A805 B009A805 Explanation: Input value error in I/O card Licensed
Internal Code
Explanation: Input value error in I/O card Licensed
Internal Code Failing Item:
Failing Item: v AJDG301
v AJDG301
B009A80E B009A80E
B009A806 B009A806 Explanation: Input value error in I/O card Licensed
Internal Code
Explanation: Input value error in I/O card Licensed
Internal Code Failing Item:
Failing Item: v AJDG301
v AJDG301
v UJE35 B009A80F B009A80F
Explanation: Input value error in I/O card Licensed
B009A808 B009A808 Internal Code
Explanation: Input value error in I/O card Licensed Failing Item:
Internal Code v AJDG301
Failing Item:
v AJDG301
v UJE36
(B009) Reference codes 63
B009A810 • B009A822
B009A810 B009A810 B009A819 B009A819
Explanation: Procedure error in vertical Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v FI00730
v FI00730
B009A81A B009A81A
B009A811 B009A811 Explanation: Procedure error in vertical Licensed
Explanation: Procedure error in vertical Licensed Internal Code
Internal Code Failing Item:
Failing Item: v FI00730
v AJDG301 v AJDG301
B009A812 B009A812 B009A81B B009A81B
Explanation: Procedure error in vertical Licensed Explanation: Procedure error in vertical Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
v FI00730
B009A815 B009A815
Explanation: Procedure error in vertical Licensed B009A81C B009A81C
Internal Code Explanation: Output value error in vertical Licensed
Failing Item: Internal Code
v AJDG301 Failing Item:
v FI00730
B009A816 B009A816
Explanation: Input value error in I/O card Licensed B009A81E B009A81E
Internal Code Explanation: Output value error in vertical Licensed
Failing Item: Internal Code
v AJDG301 Failing Item:
v AJDG301
B009A817 B009A817
Explanation: Input value error in I/O card Licensed B009A81F B009A81F
Internal Code Explanation: Procedure error in vertical Licensed
Failing Item: Internal Code
v AJDG301 Failing Item:
v FI00730
B009A818 B009A818
Explanation: Output value error in vertical Licensed B009A822 B009A822
Internal Code Explanation: Input value error in I/O card Licensed
Failing Item: Internal Code
v AJDG301 Failing Item:
v AJDG301
64 System reference codes (Bxxx)
B009A824 • B009A838
B009A824 B009A824 B009A830 B009A830
Explanation: Input value error in I/O card Licensed Explanation: Procedure error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v FI00730
B009A826 B009A826 B009A831 B009A831
Explanation: Procedure error in vertical Licensed Explanation: Procedure error in vertical Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
v FI00730 v FI00730
B009A827 B009A827 B009A832 B009A832
Explanation: Procedure error in vertical Licensed Explanation: Output value error in vertical Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
v FI00730
B009A833 B009A833
B009A829 B009A829 Explanation: Output value error in vertical Licensed
Explanation: Output value error in vertical Licensed Internal Code
Internal Code Failing Item:
Failing Item: v AJDG301
v AJDG301 v FI00730
B009A82A B009A82A B009A834 B009A834
Explanation: Procedure error in vertical Licensed Explanation: Output value error in vertical Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
B009A82D B009A82D B009A836 B009A836
Explanation: Output value error in vertical Licensed Explanation: Procedure error in vertical Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v FI00730
B009A82F B009A82F B009A838 B009A838
Explanation: Output value error in vertical Licensed Explanation: Procedure error in vertical Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
(B009) Reference codes 65
B009A839 • B009ACD5
B009A839 B009A839 B009AA11 B009AA11
Explanation: Procedure error in vertical Licensed Explanation: Number of stations greater than allowed
Internal Code in configuration
Failing Item: Failing Item:
v AJDG301 v UJE35
v FI00730 v AJDG301
B009A83B B009A83B B009AA12 B009AA12
Explanation: Procedure error in vertical Licensed Explanation: Not enough storage to process adapter
Internal Code command
Failing Item: Failing Item:
v AJDG301 v AJDG301
v FI00730
B009AA15 B009AA15
B009A840 B009A840 Explanation: Procedure error in I/O card Licensed
Explanation: Procedure error in vertical Licensed Internal Code
Internal Code Failing Item:
Failing Item: v AJDG301
v AJDG301 v FI00730
v FI00730
B009ACD0 B009ACD0
B009A842 B009A842 Explanation: Input value error in I/O card Licensed
Explanation: Procedure error in vertical Licensed Internal Code
Internal Code Failing Item:
Failing Item: v AJDG301
v AJDG301
v FI00730 B009ACD1 B009ACD1
Explanation: Input value error in I/O card Licensed
B009A844 B009A844 Internal Code
Explanation: Output value error in vertical Licensed Failing Item:
Internal Code v AJDG301
Failing Item:
v AJDG301 B009ACD4 B009ACD4
Explanation: Input value error in I/O card Licensed
B009AA06 B009AA06 Internal Code
Explanation: Output value error in vertical Licensed Failing Item:
Internal Code v AJDG301
Failing Item:
v AJDG301 B009ACD5 B009ACD5
Explanation: Input value error in I/O card Licensed
B009AA07 B009AA07 Internal Code
Explanation: Output value error in vertical Licensed Failing Item:
Internal Code v AJDG301
Failing Item:
v AJDG301
66 System reference codes (Bxxx)
B009ACD6 • B009FFFF
B009ACD6 B009ACD6
Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v AJDG301
B009ACD7 B009ACD7
Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v AJDG301
B009ACD8 B009ACD8
Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v AJDG301
B009AF0A B009AF0A
Explanation: Procedure error in vertical Licensed
Internal Code
Failing Item:
v AJDG301
v FI00730
B009AF0B B009AF0B
Explanation: Procedure error in vertical Licensed
Internal Code
Failing Item:
v AJDG301
v FI00730
B009FFFF B009FFFF
Explanation: User suspected communications
problem.
Failing Item:
v USER
(B009) Reference codes 67
68 System reference codes (Bxxx)
(B010) Reference codes
Explanation: First call failed, retrying call; CFI ET
B0102651 B0102651
from modem
Explanation: First call failed, retrying call; no CFI
Response: After dialing the server detected a Call
from modem
Failure Indication ET from the modem. The system is
Response: The remote answer timer expired without trying the call again, up to the value of the Dial retry
the server detecting either the rise of DSR or a Call parameter of the controller description. CFI ET is sent
Failure Indication from the modem. The system is from the modem if the modem detects a busy signal
trying the call again, up to the value of the Dial retry (engaged tone).
parameter of the controller description.
Failing Item:
Failing Item: v UJ0E3
v UJE34 v UJA35
v UJA34
v FI00704 B0102656 B0102656
v FI00701
Explanation: First call failed, retrying call; CFI NT
from modem
B0102652 B0102652
Response: After dialing the server detected a Call
Explanation: First call failed, retrying call; CFI AB Failure Indication NT from the modem. The system is
from modem trying the call again, up to the value of the Dial retry
parameter of the controller description. CFI NT is sent
Response: After dialing the server detected a Call
from the modem if the modems abort timer expires
Failure INDICATION AB from the modem. The system
without detecting answer tone, is not detecting ring
is trying the call again, up to the face value of the Dial
back, and had detected the expected dial tones. This
retry parameter of the controller description. CFI AB is
situation could result from a person answering the
sent from the modem if the modems abort timer
telephone.
expires after answer tone was detected and before the
modem is ready for data transfer. Failing Item:
Failing Item: v UJ0E3
v UJ0E3 v FI00705
v FI00704 v UJA35
v UJA35
B0102657 B0102657
B0102653 B0102653 Explanation: First call failed, retrying call; CFI RT
from modem
Explanation: First call failed, retrying call; CFI DE
from modem Response: After dialing the server detected a Call
Failure Indication RT from the modem. The system is
Response: After dialing the server detected a Call
trying the call again, up to the value of the Dial retry
Failure Indication DE from the modem. The system is
parameter of the controller description. CFI RT is sent
trying the call again, up to the value of the Dial retry
from the modem if the modem does not detect the
parameter of the controller description. CFI DE is sent
remote answer when the abort timer expired, the
from the modem if the modem failed to detect dial tone
modem is still detecting ring back. This response is also
when expected or detected dial tone when another tone
sent if the modem ends a call because the ring counter
was expected. This can occur if the telephone cable is
reached its limit.
not plugged into the back of the modem.
Failing Item:
Failing Item:
v UJ0E3
v UJ0E3
v UJA35
v FI00704
B0102660 B0102660
B0102654 B0102654
© Copyright IBM Corp. 2010, 2013 69
B0104594 • B010500B
Explanation: Call failed, retrying call; Non-standard
B0105004 B0105004
CFI from modem
Explanation: Incorrect command value sent by vertical
Response: After dialing the server detected a Call
LIC
Failure Indication from the modem that was not
recognized. The system is trying the call again, up to Failing Item:
the value of the Dial retry parameter of the controller v AJDG301
description.
Failing Item: B0105005 B0105005
v UJ0E3
Explanation: Procedure error in vertical Licensed
v FI00704 Internal Code
Failing Item:
B0104594 B0104594
v AJDG301
Explanation: Wrong telephone number specified in
system configuration
B0105006 B0105006
Failing Item:
Explanation: Procedure error in vertical Licensed
v UJA35 Internal Code
v AJDG301
Failing Item:
v AJDG301
B0105000 B0105000
Explanation: Wrong command sent by vertical B0105007 B0105007
Licensed Internal Code
Explanation: Procedure error in vertical Licensed
Failing Item: Internal Code
v AJDG301
Failing Item:
v AJDG301
B0105001 B0105001
v UJA34
Explanation: Procedure error in vertical Licensed
Internal Code
B0105009 B0105009
Failing Item:
Explanation: Incorrect command value sent by vertical
v AJDG301 LIC
Failing Item:
B0105002 B0105002
v AJDG301
Explanation: Procedure error in vertical Licensed
Internal Code
B010500A B010500A
Response: Procedure error in machine instructions
Explanation: Procedure error in vertical Licensed
Failing Item: Internal Code
v UJE34 Failing Item:
v AJDG301 v AJDG301
B0105003 B0105003 B010500B B010500B
Explanation: Procedure error in vertical Licensed Explanation: Incorrect command value sent by vertical
Internal Code LIC
Failing Item: Failing Item:
v AJDG301 v AJDG301
v UJA34
70 System reference codes (Bxxx)
B010500C • B010501A
B010500C B010500C B0105013 B0105013
Explanation: Incorrect command value sent by vertical Explanation: Incorrect command value sent by vertical
LIC LIC
Failing Item: Failing Item:
v AJDG301 v AJDG301
B010500D B010500D B0105014 B0105014
Explanation: Incorrect command value sent by vertical Explanation: Incorrect command value sent by vertical
LIC LIC
Failing Item: Failing Item:
v AJDG301 v AJDG301
v UJA34
B0105015 B0105015
B010500E B010500E Explanation: Procedure error in vertical Licensed
Explanation: Incorrect command value sent by vertical Internal Code
LIC Failing Item:
Failing Item: v AJDG301
v AJDG301
B0105016 B0105016
B010500F B010500F Explanation: Incorrect command value sent by vertical
Explanation: Incorrect command value sent by vertical LIC
LIC Failing Item:
Failing Item: v AJDG301
v AJDG301
B0105017 B0105017
B0105010 B0105010 Explanation: Incorrect command value sent by vertical
Explanation: Incorrect command value sent by vertical LIC
LIC Failing Item:
Failing Item: v AJDG301
v AJDG301
B0105018 B0105018
B0105011 B0105011 Explanation: Incorrect command value sent by vertical
Explanation: Incorrect command value sent by vertical LIC
LIC Failing Item:
Failing Item: v AJDG301
v AJDG301
B0105019 B0105019
B0105012 B0105012 Explanation: Incorrect command value sent by vertical
Explanation: Incorrect command value sent by vertical LIC
LIC Failing Item:
Failing Item: v AJDG301
v AJDG301
B010501A B010501A
Explanation: Vertical LIC did not request enough
storage
Failing Item:
(B010) Reference codes 71
B010501C • B01050E5
v AJDG301
B0105024 B0105024
Explanation: Vertical LIC sent commands in wrong
B010501C B010501C
order
Explanation: Command value error in I/O card
Failing Item:
Licensed Internal Code
v AJDG301
Failing Item:
v FI00730
v FI00730
B0105025 B0105025
B010501D B010501D
Explanation: Vertical LIC sent commands in wrong
Explanation: Clear-to-send not active to allow data to order
be sent
Failing Item:
Failing Item:
v AJDG301
v FI00704
v FI00730
v AJDG301
v FI00701
B01050E0 B01050E0
v FI00730
Explanation: Wrong or no external communications
v FI00719
cable installed
Failing Item:
B010501E B010501E
v UJA34
Explanation: Command value error in I/O card
v FI00701
Licensed Internal Code
v FI00719
Failing Item:
v FI00730
B01050E1 B01050E1
Explanation: Communications line already in use
B010501F B010501F
Failing Item:
Explanation: Command value error in I/O card
Licensed Internal Code v AJDG301
v UJA34
Failing Item:
v FI00730
B01050E3 B01050E3
B0105022 B0105022 Explanation: Wrong command value sent by IBM i
Operating System licensed program
Explanation: Procedure error in vertical Licensed
Internal Code Failing Item:
v AJDG301
Failing Item:
v UJA34
v AJDG301
B01050E4 B01050E4
B0105023 B0105023
Explanation: Wrong command value sent by IBM i
Explanation: Procedure error in vertical Licensed
Operating System licensed program
Internal Code
Failing Item:
Failing Item:
v AJDG301
v AJDG301
v UJA34
v UJA34
B01050E5 B01050E5
Explanation: Incorrect command value sent by vertical
LIC
Failing Item:
72 System reference codes (Bxxx)
B01050E6 • B01050F2
v AJDG301
B01050ED B01050ED
v UJA34
Explanation: Wrong command value sent by IBM i
Operating System licensed program
B01050E6 B01050E6
Failing Item:
Explanation: Incorrect command value sent by vertical
v AJDG301
LIC
Failing Item:
B01050EE B01050EE
v AJDG301
Explanation: Incorrect command value sent by vertical
v UJA34
LIC
v FI00730
Failing Item:
v AJDG301
B01050E7 B01050E7
Explanation: Incorrect command value sent by vertical
B01050EF B01050EF
LIC
Explanation: Wrong number of dial digits in
Failing Item:
telephone number
v AJDG301
Failing Item:
v UJA34
v UJA35
v FI00730
v FI00703
v FI00719
B01050E8 B01050E8
v FI00702
Explanation: Wrong command value sent by IBM i
Operating System licensed program
B01050F0 B01050F0
Failing Item:
Explanation: No telephone number provided for the
v AJDG301
call command
Failing Item:
B01050E9 B01050E9
v AJDG301
Explanation: Incorrect command value sent by vertical
v UJA35
LIC
Failing Item:
B01050F1 B01050F1
v AJDG301
Explanation: Communications line not installed
v UJA34
Response:
B01050EB B01050EB Failing Item:
Explanation: Incorrect command value sent by vertical v AJDG301
LIC v FI00719
Failing Item: v UJA34
v AJDG301
v UJA34 B01050F2 B01050F2
Explanation: Automatic call unit cable not installed
B01050EC B01050EC Response:
Explanation: Wrong command value sent by IBM i Failing Item:
Operating System licensed program
v FI00702
Failing Item: v UJA34
v AJDG301 v FI00719
(B010) Reference codes 73
B01050F4 • B01052E1
B01050F4 B01050F4 B0105205 B0105205
Explanation: Clear-to-send signal dropped warning; Explanation: I/O card Licensed Internal Code
information only response not correct
Failing Item: Failing Item:
v UJE34 v FI00730
v AJDG301
B01050F5 B01050F5
Explanation: Network uncontrolled-not-ready B0105206 B0105206
warning; information only Explanation: Communications controller storage not
Failing Item: available
v UJE34 Failing Item:
v UJA33
B01050F6 B01050F6
Explanation: Network controlled-not-ready warning; B0105207 B0105207
information only Explanation: Communications controller storage not
Failing Item: available
v UJE34 Failing Item:
v UJA33
B01050F7 B01050F7
Explanation: Data-set-ready changed to not active; for B0105208 B0105208
information only Explanation: I/O card Licensed Internal Code ended
Failing Item: abnormally
v UJE34 Failing Item:
v FI00730
B01050F8 B01050F8
Explanation: Adapter card transmit error B0105209 B0105209
Response: Explanation: I/O card Licensed Internal Code
response not correct
Failing Item:
Failing Item:
v FI00719
v FI00730
B0105202 B0105202
B01052E0 B01052E0
Explanation: I/O card Licensed Internal Code ended
abnormally Explanation: Incorrect command used by I/O card
Licensed Internal Code
Failing Item:
Failing Item:
v FI00730
v FI00730
B0105203 B0105203
B01052E1 B01052E1
Explanation: I/O card Licensed Internal Code
resource not available Explanation: Wrong procedure used in I/O card
Licensed Internal Code
Failing Item:
Failing Item:
v FI00730
v FI00730
74 System reference codes (Bxxx)
B01052E2 • B0105600
B01052E2 B01052E2 B01052E8 B01052E8
Explanation: I/O card Licensed Internal Code Explanation: Command value error in I/O card
resource not available Licensed Internal Code
Failing Item: Failing Item:
v UJA33 v FI00730
v UJA34
B01052E9 B01052E9
B01052E3 B01052E3 Explanation: Command value error in I/O card
Explanation: Command response error in I/O card Licensed Internal Code
Licensed Internal Code Failing Item:
Failing Item: v FI00730
v FI00730
B01052EA B01052EA
B01052E4 B01052E4 Explanation: I/O card Licensed Internal Code error
Explanation: Wrong command value sent by IBM i Failing Item:
Operating System licensed program
v FI00730
Failing Item:
v AJDG301 B0105301 B0105301
v UJA34
Explanation: Adapter card receive error
Failing Item:
B01052E5 B01052E5
v FI00719
Explanation: Incorrect command value sent by vertical
LIC
B0105302 B0105302
Failing Item:
Explanation: Adapter card transmit error
v AJDG301
Failing Item:
B01052E6 B01052E6 v FI00719
Explanation: Data-line-occupied already active from
automatic call unit B0105401 B0105401
Failing Item: Explanation: Communications adapter card interrupt
not expected
v FI00703
v UJA32 Failing Item:
v FI00719 v FI00719
v FI00702 v FI00718
B01052E7 B01052E7 B01054E1 B01054E1
Explanation: X.21 network not in the ready or Explanation: Communications line not operational
receive-data state Failing Item:
Failing Item: v FI00719
v FI00704 v UJA34
v FI00701
v FI00719 B0105600 B0105600
Explanation: Clear-to-send off; error limit per 256
reached
Failing Item:
v FI00704
(B010) Reference codes 75
B0105601 • B010560B
v AJDG301 v UJ0E3
v UJA34 v UJA34
v FI00701
v FI00719 B0105606 B0105606
Explanation: Data-line-occupied error; error limit per
B0105601 B0105601 256 reached
Explanation: Data-set-ready state changed; error limit Failing Item:
per 256 reached v FI00703
Failing Item: v FI00719
v FI00704 v UJA34
v UJA34 v FI00702
v FI00701
v FI00719 B0105607 B0105607
Explanation: Abandon-call-retry error; error limit per
B0105602 B0105602 256 reached
Explanation: Clear-to-send state changed; error limit Failing Item:
per 256 reached v UJA35
Failing Item: v FI00703
v FI00704 v UJA34
v UJA34 v FI00705
v FI00701 v UJ0E3
v FI00719
B0105608 B0105608
B0105603 B0105603 Explanation: Present-next-digit error; error limit per
Explanation: Carrier-detect state changed; error limit 256 reached
per 256 reached Failing Item:
Failing Item: v FI00703
v FI00704 v UJA34
v FI00705 v FI00719
v UJA34 v FI00702
v FI00701
v FI00719 B0105609 B0105609
v UJ0E3 Explanation: Distant-station-connected error; error
limit per 256 reached
B0105604 B0105604 Failing Item:
Explanation: Call attempted; error limit per 256 v UJA34
reached v FI00705
Failing Item: v FI00700
v FI00705 v FI00703
v UJ0E3 v FI00719
v FI00703 v FI00702
v UJA34
B010560B B010560B
B0105605 B0105605 Explanation: Data-set-ready error; error limit per 256
Explanation: Call completed with error; error limit per reached
256 reached Failing Item:
Failing Item: v UJA34
76 System reference codes (Bxxx)
B010560C • B01056E8
v FI00705
B01056E4 B01056E4
v FI00700
Explanation: Automatic call unit has
v FI00701
present-next-digit error
v FI00719
Failing Item:
v FI00704
v FI00703
v FI00719
B010560C B010560C
v FI00702
Explanation: Wrong number length; error limit per
256 reached
B01056E5 B01056E5
Failing Item:
Explanation: Automatic call unit distant-station-
v UJA35
connected error
v FI00703
Failing Item:
v UJA34
v FI00700
v UJA34
B0105651 B0105651
v UJA35
Explanation: Call failed, no Call Failure Indication
v FI00703
from modem
v FI00701
Response: The remote answer timer expired without
v FI00719
the server detecting either the rise of DSR or a Call
Failure Indication from the modem. The system has v UJ0E3
reached the number of tries in the dial retry parameter
in the controller description. B01056E6 B01056E6
Failing Item: Explanation: Data-set-ready error on modem interface
v UJE34
Failing Item:
v UJA34
v FI00700
v FI00704
v UJ0E3
v FI00701
v UJA34
v FI00701
B01056E2 B01056E2
v FI00719
Explanation: Data-set-ready already active on modem
interface
B01056E7 B01056E7
Failing Item:
Explanation: Automatic call unit command error
v FI00704
Failing Item:
v FI00701
v FI00701
v FI00719
v FI00704
v FI00719
B01056E3 B01056E3
Explanation: Automatic call unit data-line-occupied
B01056E8 B01056E8
error
Explanation: Clear-to-send not active on modem
Failing Item:
interface
v FI00703
Failing Item:
v FI00702
v UJ0E3
v FI00719
v UJA34
v UJ0E3
v FI00704
v FI00701
v FI00719
(B010) Reference codes 77
B01056E9 • B0105702
B01056E9 B01056E9 B01056EE B01056EE
Explanation: Clear-to-send signal failed to drop on Explanation: Automatic call unit abandon-call-retry
modem interface error
Failing Item: Failing Item:
v FI00704 v FI00700
v FI00701 v UJA35
v FI00719 v FI00703
v FI00719
B01056EA B01056EA v FI00702
Explanation: Clear-to-send signal dropped on modem
interface B01056EF B01056EF
Failing Item: Explanation: Automatic call unit telephone-number-
v UJ0E3 length error
v UJA34 Failing Item:
v FI00704 v UJA35
v FI00701 v FI00703
v FI00719 v FI00701
B01056EB B01056EB B01056F0 B01056F0
Explanation: Carrier-detect dropped on modem Explanation: Automatic call unit power turned off
interface
Failing Item:
Failing Item: v FI00703
v FI00701 v FI00702
v FI00704 v FI00719
v UJ0E3
v FI00719 B01056F1 B01056F1
Explanation: Data-set-ready dropped on modem
B01056EC B01056EC interface
Explanation: Data-set-ready turn-off time-out on Failing Item:
modem interface
v FI00701
Failing Item: v FI00704
v FI00704 v FI00719
v UJA34 v UJ0E3
v FI00701
v FI00719 B0105701 B0105701
Explanation: SDLC frame reject type W transmitted
B01056ED B01056ED
Failing Item:
Explanation: Data-set-ready turn-on time-out on
v FI00700
modem interface
v UJA34
Failing Item:
v FI00701
B0105702 B0105702
v FI00704
Explanation: SDLC frame reject type X transmitted
v FI00719
v AJDG301 Failing Item:
v FI00700
v FI00730
v UJA34
78 System reference codes (Bxxx)
B0105703 • B010570F
B0105703 B0105703 B0105709 B0105709
Explanation: SDLC frame reject type Y transmitted Explanation: Not valid control field received from
remote equipment
Failing Item:
v UJA34 Failing Item:
v FI00700 v UJA34
v FI00700
B0105704 B0105704
B010570A B010570A
Explanation: SDLC frame reject type Z transmitted
Explanation: Incorrect information field received from
Failing Item:
remote equipment
v FI00730
Failing Item:
v FI00700
v FI00700
v UJA34
B010570B B010570B
B0105705 B0105705
Explanation: Incorrect frame reject received from
Explanation: SDLC frame reject type W received from
remote equipment
remote equipment
Failing Item:
Failing Item:
v FI00700
v FI00730
v FI00700
B010570C B010570C
B0105706 B0105706 Explanation: Wrong sequence number received from
remote equipment
Explanation: SDLC frame reject type X received from
remote equipment Failing Item:
v FI00700
Failing Item:
v UJA34
v FI00730
v FI00700
B010570D B010570D
B0105707 B0105707 Explanation: Wrong response received from remote
equipment
Explanation: SDLC frame reject type Y received from
remote equipment Failing Item:
v FI00700
Failing Item:
v FI00730
B010570E B010570E
v FI00700
v UJA34 Explanation: Wrong command received from remote
equipment
B0105708 B0105708 Failing Item:
v FI00700
Explanation: SDLC frame reject type Z received from
remote equipment
B010570F B010570F
Failing Item:
v FI00730 Explanation: No data in information frame received
from remote equipment
v FI00700
v UJA34 Failing Item:
v FI00700
(B010) Reference codes 79
B0105710 • B0105719
B0105710 B0105710 B0105715 B0105715
Explanation: Nonproductive receive time-out while Explanation: Remote equipment did not respond
receiving from remote causing an idle-time-out
Failing Item: Failing Item:
v UJA34 v UJA34
v UJ0E3 v UJ0E3
v FI00704 v FI00701
v FI00705 v FI00704
v FI00700 v FI00705
v FI00701 v FI00700
v FI00719 v FI00719
B0105711 B0105711 B0105716 B0105716
Explanation: Remote equipment sent more data Explanation: Communications controller storage not
frames than allowed available
Failing Item: Failing Item:
v UJA34 v FI00730
v FI00700
B0105717 B0105717
B0105712 B0105712 Explanation: No response from modem during
Explanation: No data received from remote modem test
equipment; time-out Failing Item:
Failing Item: v FI00704
v UJA34 v FI00701
v AJDG301 v FI00719
v UJ0E3 v AJDG301
v FI00704
v FI00705 B0105718 B0105718
v FI00700 Explanation: Retry limit reached for sending frames to
v UJA35 remote equipment
v FI00701 Failing Item:
v FI00719 v UJ0E3
v FI00704
B0105713 B0105713 v FI00705
Explanation: Disconnected mode response received v FI00700
from remote system v UJA34
Failing Item: v FI00701
v FI00700 v FI00719
v FI00730
B0105719 B0105719
B0105714 B0105714 Explanation: Retry limit reached for sending frames to
Explanation: Disconnected mode response received remote equipment
from remote system Failing Item:
Failing Item: v FI00700
v FI00700
80 System reference codes (Bxxx)
B010571A • B0105754
B010571A B010571A B0105724 B0105724
Explanation: Retry limit reached for sending frames to Explanation: Retry limit reached for sending frames to
remote equipment remote equipment
Failing Item: Failing Item:
v UJA34 v UJ0E3
v AJDG301 v FI00704
v UJ0E3 v FI00705
v FI00704 v FI00700
v FI00705 v UJA34
v FI00700 v FI00701
v FI00701 v FI00719
v FI00719
v UJA35 B0105750 B0105750
Explanation: Incorrect command value sent by vertical
B0105720 B0105720 LIC
Explanation: Retry limit reached for sending poll Failing Item:
frame to remote v AJDG301
Failing Item: v FI00730
v FI00700
v UJA34 B0105751 B0105751
Explanation: Incorrect command value sent by vertical
B0105721 B0105721 LIC
Explanation: Could not send frame to remote Failing Item:
equipment; local problem v AJDG301
Failing Item: v FI00730
v FI00701
v UJA34 B0105752 B0105752
v FI00704 Explanation: Wrong response received from remote
v FI00730 equipment
v FI00719 Failing Item:
v FI00700
B0105722 B0105722 v UJA35
Explanation: Wrong command value sent by IBM i
Operating System licensed program B0105753 B0105753
Failing Item: Explanation: Wrong response received from remote
v AJDG301 equipment
v UJA35 Failing Item:
v FI00700
B0105723 B0105723 v FI00730
Explanation: Wrong response received from remote
equipment B0105754 B0105754
Failing Item: Explanation: Wrong response received from remote
v FI00700 equipment
v UJA34 Failing Item:
v FI00700
v UJA35
(B010) Reference codes 81
B0105755 • B0105776
v UJA34
B0105762 B0105762
Explanation: No data received from remote
B0105755 B0105755
equipment; time-out
Explanation: Wrong response received from remote
Failing Item:
equipment
v FI00700
Failing Item:
v UJ0E3
v FI00700
v UJA34
v UJA35
B0105764 B0105764
B0105756 B0105756
Explanation: Adapter card transmit error
Explanation: Wrong response received from remote
equipment Failing Item:
v FI00701
Failing Item:
v FI00704
v FI00700
v FI00719
v UJA35
v FI00730
B0105757 B0105757
B0105768 B0105768
Explanation: Wrong response received from remote
equipment Explanation: Communications line clear
Failing Item: Failing Item:
v FI00700 v UJ0E3
v FI00730 v FI00700
v UJA34
B0105758 B0105758
B010576A B010576A
Explanation: Wrong response received from remote
equipment Explanation: Wrong response received from remote
equipment
Failing Item:
v FI00700 Failing Item:
v FI00730 v FI00700
v UJA34 v UJ0E3
v AJDG301 v UJA34
B0105759 B0105759 B0105770 B0105770
Explanation: Wrong response received from remote Explanation: Incorrect command value sent by vertical
equipment LIC
Failing Item: Failing Item:
v UJA34 v AJDG301
v FI00700 v FI00730
B0105760 B0105760 B0105776 B0105776
Explanation: Nonproductive receive time-out while Explanation: Wrong response received from remote
receiving from remote equipment
Failing Item: Failing Item:
v FI00700 v FI00700
v UJ0E3 v FI00730
v UJA34
82 System reference codes (Bxxx)
B0105778 • B01057E3
v UJA33
B0105778 B0105778
v UJA35
Explanation: Wrong response received from remote
v UJE34
equipment
Failing Item:
B0105784 B0105784
v FI00700
Explanation: Call cleared after answer; session reset
v FI00730
Response: Call cleared after answer, reset while link
disconnected.
B010577A B010577A
Failing Item:
Explanation: Wrong response received from remote
equipment v UJE34
v UJE39
Failing Item:
v FI00700
B01057E0 B01057E0
v FI00730
Explanation: Frame-check-sequence error; error limit
per 256 reached
B010577C B010577C
Failing Item:
Explanation: Wrong response received from remote
equipment v UJ0E3
v FI00705
Failing Item:
v FI00704
v UJA34
v UJA34
v FI00700
v UJA35
B01057E1 B01057E1
v FI00730
v AJDG301 Explanation: Overrun error; error limit per 256
reached
B010577E B010577E Failing Item:
v UJA34
Explanation: Wrong command received from remote
equipment
B01057E2 B01057E2
Failing Item:
v FI00700 Explanation: Short frame error; error limit per 256
reached
v FI00730
Failing Item:
B0105780 B0105780 v UJ0E3
v FI00700
Explanation: Maximum retries reached on XID polls
after answer v FI00705
v FI00704
Failing Item:
v UJA34
v UJ0E3
v UJA34
B01057E3 B01057E3
v FI00719
v FI00704 Explanation: Frame-cancel-received error; error limit
per 256 reached
B0105782 B0105782 Failing Item:
v UJ0E3
Explanation: Connection cleared after answer after
XID exchange v FI00700
v FI00705
Failing Item:
v FI00704
v UJE39
v UJA34
v UJA34
(B010) Reference codes 83
B01057E4 • B0105805
B01057E4 B01057E4 B0105801 B0105801
Explanation: Idle link detected error; error limit per Explanation: Uncontrolled-not-ready time-out; error
256 reached limit per 256 reached
Failing Item: Failing Item:
v UJA34 v AJDG301
v FI00700 v FI00704
v UJ0E3 v UJA34
v FI00705 v FI00701
v FI00704
B0105802 B0105802
B01057F0 B01057F0 Explanation: State-not-known time-out error; error
Explanation: Send sequence counter error; error limit limit per 256 reached
per 256 reached Failing Item:
Failing Item: v AJDG301
v UJ0E3 v FI00704
v FI00700 v UJA34
v FI00705 v FI00701
v FI00704 v FI00719
v UJA34
B0105803 B0105803
B01057F1 B01057F1 Explanation: Control-not-ready state changed; error
Explanation: Receive sequence counter error; error limit per 256 reached
limit per 256 reached Failing Item:
Failing Item: v FI00704
v FI00704 v UJA34
v FI00700
v UJ0E3 B0105804 B0105804
v FI00705 Explanation: Not-ready state changed; error limit per
v UJA34 256 reached
Failing Item:
B01057F2 B01057F2 v FI00704
Explanation: Response time-out error; error limit per v UJA34
256 reached v FI00701
Failing Item:
v FI00700 B0105805 B0105805
v UJA34 Explanation: State-not-known changed; error limit per
v UJ0E3 256 reached
v FI00704 Failing Item:
v FI00705 v FI00704
v UJA34
B0105800 B0105800 v FI00701
Explanation: Control-not-ready time-out; error limit v FI00719
per 256 reached
Failing Item:
v FI00704
v AJDG301
v UJA34
84 System reference codes (Bxxx)
B0105806 • B0105810
v UJA33
B0105806 B0105806
v UJA34
Explanation: State interrupt overrun error; error limit
v FI00730
per 256 reached
Failing Item:
B010580C B010580C
v FI00730
Explanation: Clear was missed; error limit per 256
v UJA34
reached
v FI00704
Failing Item:
v UJ0E3
v UJA33
v UJA34
B0105807 B0105807
v FI00730
Explanation: Not valid data; error limit per 256
reached
B010580D B010580D
Failing Item:
Explanation: Parity error; error limit per 256 reached
v FI00704
v UJA34 Failing Item:
v FI00704
B0105808 B0105808 v FI00701
v UJA34
Explanation: Data-communications-equipment error;
limit per 256 reached v FI00719
Failing Item:
B010580E B010580E
v FI00704
v FI00705 Explanation: Receive overrun; error limit per 256
reached
v UJA34
v UJ0E3 Failing Item:
v FI00719
B0105809 B0105809 v UJA34
Explanation: Control-not-ready in data mode; error
limit per 256 reached B010580F B010580F
Failing Item: Explanation: Temporary storage overrun; error limit
per 256 reached
v UJA34
v FI00705 Failing Item:
v FI00700 v FI00730
v UJ0E3 v UJA34
v FI00704
B0105810 B0105810
B010580A B010580A Explanation: Network type 1 time-out; error limit per
256 reached
Explanation: Incoming call received during outgoing
call; limit reached Failing Item:
Failing Item: v AJDG301
v UJA34 v FI00704
v UJE34 v UJA34
v FI00701
B010580B B010580B v FI00719
Explanation: Missed incoming call; error limit per 256
reached
Failing Item:
(B010) Reference codes 85
B0105811 • B010581B
B0105811 B0105811 B0105816 B0105816
Explanation: Network type 2 time-out; error limit per Explanation: Network type 5 time-out; error limit per
256 reached 256 reached
Failing Item: Failing Item:
v UJA34 v FI00704
v AJDG301 v AJDG301
v FI00704 v UJA34
v FI00705
v UJ0E3 B0105817 B0105817
Explanation: Network type 6 time-out; error limit per
B0105812 B0105812 256 reached
Explanation: Network type 3A time-out; error limit Failing Item:
per 256 reached v FI00704
Failing Item: v AJDG301
v UJA34 v UJA34
v AJDG301
v FI00704 B0105818 B0105818
v FI00705 Explanation: Network type 7 time-out; error limit per
v UJ0E3 256 reached
Failing Item:
B0105813 B0105813 v FI00704
Explanation: Network type 3B time-out; error limit v AJDG301
per 256 reached v UJA34
Failing Item:
v UJA34 B0105819 B0105819
v AJDG301 Explanation: Network type 20 time-out; error limit per
v FI00704 256 reached
v FI00705 Failing Item:
v UJ0E3 v AJDG301
v FI00704
B0105814 B0105814 v UJA34
Explanation: Network type 4A time-out; error limit v FI00701
per 256 reached v FI00719
Failing Item:
v FI00704 B010581A B010581A
v AJDG301 Explanation: Network type 21 time-out; error limit per
v UJA34 256 reached
Failing Item:
B0105815 B0105815 v FI00704
Explanation: Network type 4B time-out; error limit v AJDG301
per 256 reached v UJA34
Failing Item:
v UJA34 B010581B B010581B
v AJDG301 Explanation: Call-progress-signal type 00; error limit
v FI00704 per 256 reached
v FI00705 Failing Item:
v UJ0E3
86 System reference codes (Bxxx)
B010581C • B0105827
v UJA34
B0105822 B0105822
v UJE34
Explanation: Call-progress-signal type 21; error limit
per 256 reached
B010581C B010581C
Failing Item:
Explanation: Call-progress-signal type 01; error limit
v FI00700
per 256 reached
v UJA34
Failing Item:
v UJE34
v UJA34
v UJA35
v UJE34
B0105823 B0105823
B010581D B010581D
Explanation: Call-progress-signal type 22; error limit
Explanation: Call-progress-signal type 02; error limit per 256 reached
per 256 reached
Failing Item:
Failing Item:
v UJA35
v UJA34
v FI00704
v UJE34
v UJA34
B010581E B010581E
B0105824 B0105824
Explanation: Call-progress-signal type 03; error limit
Explanation: Call-progress-signal type 23; error limit
per 256 reached
per 256 reached
Failing Item:
Failing Item:
v UJA34
v FI00701
v UJE34
v FI00704
v FI00719
B010581F B010581F
v UJA34
Explanation: Call-progress-signal type 04; error limit
per 256 reached
B0105825 B0105825
Failing Item:
Explanation: Call-progress-signal type 41; error limit
v UJA34 per 256 reached
v UJE34
Failing Item:
v UJA35
B0105820 B0105820
v UJE34
Explanation: Call-progress-signal type 05; error limit v UJA34
per 256 reached
v UJ0E3
Failing Item:
v UJA34 B0105826 B0105826
v UJE34
Explanation: Call-progress-signal type 42; error limit
per 256 reached
B0105821 B0105821
Failing Item:
Explanation: Call-progress-signal type 20; error limit v UJA35
per 256 reached
v UJA34
Failing Item:
v UJA34 B0105827 B0105827
v UJA35
Explanation: Call-progress-signal type 43; error limit
v FI00700 per 256 reached
v FI00705
Failing Item:
v UJ0E3
(B010) Reference codes 87
B0105828 • B0105832
v UJA34 v UJA34
v UJA35 v FI00704
v FI00704
v FI00705 B010582D B010582D
v UJ0E3 Explanation: Call-progress-signal type 49; error limit
per 256 reached
B0105828 B0105828 Failing Item:
Explanation: Call-progress-signal type 44; error limit v UJ0E3
per 256 reached v UJA34
Failing Item:
v FI00705 B010582E B010582E
v FI00700 Explanation: Call-progress-signal type 51; error limit
v UJA35 per 256 reached
v UJA34 Failing Item:
v FI00704
B0105829 B0105829 v FI00705
Explanation: Call-progress-signal type 45; error limit v UJ0E3
per 256 reached v UJA34
Failing Item:
v UJA35 B010582F B010582F
v FI00700 Explanation: Call-progress-signal type 52; error limit
v UJA34 per 256 reached
v FI00705 Failing Item:
v UJE34
B010582A B010582A v UJA35
Explanation: Call-progress-signal type 46; error limit v UJA34
per 256 reached v FI00705
Failing Item:
v UJA35 B0105830 B0105830
v FI00700 Explanation: Call-progress-signal type 61; error limit
v FI00705 per 256 reached
v UJA34 Failing Item:
v UJ0E3
B010582B B010582B v UJA34
Explanation: Call-progress-signal type 47; error limit
per 256 reached B0105831 B0105831
Failing Item: Explanation: Call-progress-signal type 71; error limit
v FI00705 per 256 reached
v UJA34 Failing Item:
v UJA35 v UJ0E3
v UJA34
B010582C B010582C
Explanation: Call-progress-signal type 48; error limit B0105832 B0105832
per 256 reached
Explanation: Call-progress-signal type 72; error limit
Failing Item: per 256 reached
v UJE34 Failing Item:
v UJA35 v UJ0E3
88 System reference codes (Bxxx)
B0105833 • B0105841
v UJA35
B010583B B010583B
v UJA34
Explanation: Wrong command value sent by IBM i
Operating System licensed program
B0105833 B0105833
Failing Item:
Explanation: Call-progress-signal; error limit per 256
v FI00730
reached
Failing Item:
B010583C B010583C
v AJDG301
Explanation: Incorrect command value sent by vertical
v UJA34
LIC
Failing Item:
B0105836 B0105836
v AJDG301
Explanation: Call cleared by network equipment
Failing Item: B010583D B010583D
v UJ0E3
Explanation: I/O card Licensed Internal Code
v FI00705 processed wrong command
v FI00704
Failing Item:
v FI00700
v FI00730
B0105837 B0105837
B010583E B010583E
Explanation: Network-controlled not-ready state;
Explanation: I/O card Licensed Internal Code
information only
processed wrong command
Failing Item:
Failing Item:
v UJ0E3
v FI00730
B0105838 B0105838
B010583F B010583F
Explanation: I/O card Licensed Internal Code
Explanation: Incorrect command value sent by vertical
processed wrong command
LIC
Failing Item:
Failing Item:
v FI00730
v AJDG301
v AJDG301
B0105840 B0105840
B0105839 B0105839
Explanation: I/O card Licensed Internal Code used
Explanation: Incorrect command value sent by vertical incorrect procedure
LIC
Failing Item:
Failing Item:
v UJA33
v AJDG301
v FI00730
B010583A B010583A
B0105841 B0105841
Explanation: Wrong command value sent by IBM i
Explanation: I/O card Licensed Internal Code used
Operating System licensed program
incorrect procedure
Failing Item:
Failing Item:
v UJA34
v UJA33
v FI00730
(B010) Reference codes 89
B0105842 • B0105853
B0105842 B0105842 B0105849 B0105849
Explanation: I/O card Licensed Internal Code used Explanation: Wrong information provided by network
incorrect procedure
Failing Item:
Failing Item: v UJ0E3
v FI00730
B010584A B010584A
B0105843 B0105843
Explanation: Automatic answer time-out
Explanation: Communications overrun while receiving
Failing Item:
network data
v UJA34
Failing Item:
v UJ0E3
v UJA33
v FI00704
v FI00730
v FI00705
v FI00719
v FI00704
B010584B B010584B
Explanation: Call error; incoming call received during
B0105844 B0105844
outgoing call
Explanation: Communications adapter error while
Failing Item:
receiving network data
v UJE34
Response:
v UJA34
Failing Item: v FI00730
v FI00719 v FI00719
v FI00704
B0105845 B0105845
Explanation: Communications adapter transmit error B0105851 B0105851
on selection sequence
Explanation: Network did not leave
Failing Item: controlled-not-ready condition
v FI00719 Failing Item:
v UJ0E3
B0105846 B0105846 v FI00704
Explanation: Communications adapter received v AJDG301
network data incorrectly
Failing Item: B0105852 B0105852
v UJ0E3 Explanation: Network did not leave
v FI00701 uncontrolled-not-ready condition
v FI00719 Failing Item:
v UJ0E3
B0105847 B0105847 v FI00704
Explanation: Communications controller storage not v FI00701
available v AJDG301
Failing Item:
v FI00730 B0105853 B0105853
v UJ0E3 Explanation: Network remained in unknown
condition
Failing Item:
v AJDG301
v FI00704
90 System reference codes (Bxxx)
B0105854 • B010587A
v FI00701 v AJDG301
v FI00719
B0105874 B0105874
B0105854 B0105854 Explanation: Network time-out type 4A occurred
Explanation: Network time-out type 5 occurred Failing Item:
Failing Item: v FI00704
v FI00704 v AJDG301
v AJDG301
B0105875 B0105875
B0105855 B0105855 Explanation: Network time-out type 4B occurred
Explanation: Network time-out type 6 occurred Failing Item:
Failing Item: v UJ0E3
v FI00704 v FI00704
v AJDG301 v AJDG301
B0105870 B0105870 B0105876 B0105876
Explanation: Network time-out type 1 occurred Explanation: Network time-out type 7 occurred
Failing Item: Failing Item:
v AJDG301 v FI00704
v FI00704 v AJDG301
v FI00701
v FI00719 B0105877 B0105877
Explanation: Network time-out type 20 occurred
B0105871 B0105871
Failing Item:
Explanation: Network time-out type 2 occurred v AJDG301
Failing Item: v FI00704
v UJ0E3 v FI00701
v FI00704 v FI00719
v FI00705
v AJDG301 B0105878 B0105878
Explanation: Network time-out type 21 occurred
B0105872 B0105872
Failing Item:
Explanation: Network time-out type 3A occurred v FI00704
Failing Item: v AJDG301
v UJ0E3
v FI00704 B010587A B010587A
v FI00705 Explanation: Call cleared by network equipment
v AJDG301
Failing Item:
v FI00704
B0105873 B0105873
v UJ0E3
Explanation: Network time-out type 3B occurred v FI00705
Failing Item:
v UJ0E3
v FI00704
v FI00705
v UJA35
(B010) Reference codes 91
B010587B • B010589A
B010587B B010587B B0105895 B0105895
Explanation: Clock signal missing from external Explanation: Network call-progress-signal type 42
communications interface
Failing Item:
Failing Item: v FI00700
v FI00701 v UJA35
v FI00719
v FI00704 B0105896 B0105896
Explanation: Network call-progress-signal type 43
B0105890 B0105890
Failing Item:
Explanation: Network call-progress-signal type 20
v UJ0E3
Failing Item: v FI00700
v FI00700 v FI00704
v FI00705 v FI00705
v UJ0E3 v UJA35
v UJA35
B0105897 B0105897
B0105891 B0105891
Explanation: Network call-progress-signal type 44
Explanation: Network call-progress-signal type 21
Failing Item:
Failing Item: v FI00700
v FI00700 v FI00705
v UJA35 v UJA35
v UJE34
B0105898 B0105898
B0105892 B0105892
Explanation: Network call-progress-signal type 45
Explanation: Network call-progress-signal type 22
Failing Item:
Failing Item: v FI00700
v FI00700 v FI00705
v FI00704 v UJA35
v UJA35
B0105899 B0105899
B0105893 B0105893
Explanation: Network call-progress-signal type 46
Explanation: Network call-progress-signal type 23
Failing Item:
Failing Item: v FI00700
v FI00704 v FI00705
v FI00701 v UJA35
v FI00719
B010589A B010589A
B0105894 B0105894
Explanation: Network call-progress-signal type 47
Explanation: Network call-progress-signal type 41
Failing Item:
Failing Item: v FI00700
v FI00700 v UJ0E3
v UJE34 v UJA35
v UJ0E3 v FI00705
v UJA35
92 System reference codes (Bxxx)
B010589B • B01058E4
B010589B B010589B B01058E0 B01058E0
Explanation: Network call-progress-signal type 48 Explanation: Communications line not operational
Failing Item: Failing Item:
v UJE34 v FI00719
v FI00700 v UJA34
v FI00704
v UJA35 B01058E1 B01058E1
Explanation: Communications connection not made
B010589C B010589C
Failing Item:
Explanation: Network call-progress-signal type 49 v UJA33
Failing Item: v FI00730
v UJ0E3
B01058E2 B01058E2
B010589D B010589D Explanation: Communications line not operational
Explanation: Network call-progress-signal type 51 Failing Item:
Failing Item: v FI00704
v FI00704 v FI00701
v UJ0E3 v FI00719
v FI00705 v FI00730
B010589E B010589E B01058E4 B01058E4
Explanation: Network call-progress-signal type 52 Explanation: Port or DCE error has recovered; port
now available
Failing Item:
v UJE34 Response: This reference code does not identify an
error but is used to report that an X.21 port used in a
v FI00700
short-hold mode, multiple port sharing configuration
v FI00705 that was temporarily not operating is now available.
v UJA35 One of the following reference codes may have been
reported previously:
B010589F B010589F v 5870
v 5871
Explanation: Network call-progress-signal type 61
v 5872
Failing Item: v 5873
v UJ0E3 v 5893
v 5851
B01058A0 B01058A0 v 5852
Explanation: Network call-progress-signal type 71 v 5853
Failing Item: v 587B
v UJ0E3
If any of the listed reference codes are occurring
frequently and are causing performance problems, use
B01058A1 B01058A1 the reported reference code to isolate the problem.
Explanation: Network call-progress-signal type 72 Failing Item:
Failing Item: v UJE34
v UJ0E3
(B010) Reference codes 93
B0108011 • B010FFFF
B0108011 B0108011
Explanation: IOP Activation failed.
Response: MDMCNTRYID parameter in Network
Attributes is not set. Use the CHGNETA command to
set MDMCNTRYID value.
Failing Item:
v UJE34
B0108013 B0108013
Explanation: IOP Activation failed.
Response: The MDMCNTRYID parameter in Network
Attributes is not valid for this adapter. Use the
CHGNETA command to change MDMCNTRYID.
Failing Item:
v UJE34
B0108020 B0108020
Explanation: System log entry only, no service action
required
B010FFFF B010FFFF
Explanation: User suspected communications
problem.
Failing Item:
v USER
94 System reference codes (Bxxx)
(B011) Reference codes
B0116240 B0116240 B0116252 B0116252
Explanation: I/O processor detected a NetBIOS Explanation: I/O processor detected an Interconnect
Device Driver error. OS/400 portion of LAN Device Driver error. OS/400 portion of LAN
SERVER/400 configuration error. SERVER/400 configuration error.
Problem determination: Work with the configuration Problem determination: Work with the configuration
to resolve the error before working the failing item list. to resolve the error before working the failing item list.
Failing Item: Failing Item:
v AJDG301 v AJDG301
B0116241 B0116241 B0116254 B0116254
Explanation: I/O processor detected a NetBIOS Explanation: I/O processor detected an Interconnect
Device Driver error. OS/400 portion of LAN Device Driver error. OS/400 portion of LAN
SERVER/400 configuration error. SERVER/400 configuration error.
Problem determination: Work with the configuration Problem determination: Work with the configuration
to resolve the error before working the failing item list. to resolve the error before working the failing item list.
Failing Item: Failing Item:
v AJDG301 v AJDG301
B0116242 B0116242
Explanation: I/O processor detected a NetBIOS
Device Driver error. OS/400 portion of LAN
SERVER/400 configuration error.
Problem determination: Work with the configuration
to resolve the error before working the failing item list.
Failing Item:
v AJDG301
B0116243 B0116243
Explanation: I/O processor detected a NetBIOS
Device Driver error. OS/400 portion of LAN
SERVER/400 configuration error.
Problem determination: Work with the configuration
to resolve the error before working the failing item list.
Failing Item:
v AJDG301
B0116250 B0116250
Explanation: I/O processor detected an Interconnect
Device Driver error. OS/400 portion of LAN
SERVER/400 configuration error.
Problem determination: Work with the configuration
to resolve the error before working the failing item list.
Failing Item:
v AJDG301
© Copyright IBM Corp. 2010, 2013 95
96 System reference codes (Bxxx)
(B012) Reference codes
B0126201 B0126201
Explanation: I/O adapter hardware error detected.
PCI bridge error on 285A FSIOA card.
Failing Item:
v FI00719
v AJDGP01
B0126202 B0126202
Explanation: I/O processor Licensed Internal Code
error with PCI bridge on 285A FSIOA card.
Failing Item:
v AJDGP01
v FI00719
© Copyright IBM Corp. 2010, 2013 97
98 System reference codes (Bxxx)
(B013) Reference codes
Explanation: Tampering of cryptographic card
B0136601 B0136601
suspected.
Explanation: I/O adapter hardware error detected
Failing Item:
Failing Item: v IOA
v IOA v PTFSRCH
v PTFSRCH
v IOP B0136614 B0136614
Explanation: Operating voltage or temperature range
B0136602 B0136602 limits exceeded.
Explanation: An I/O processor Licensed Internal Code Response: Correct any conditions in the physical
error occurred. environment which might have caused the voltage or
Failing Item: temperature out-of-range error on the cryptographic
adapter card. After you correct the conditions, vary off
v PTFSRCH
and then vary back on the device description associated
v IOA with the cryptographic adapter card.
v IOP
Failing Item:
v CARDTMP
B0136603 B0136603
Explanation: Tampering of cryptographic card B0136615 B0136615
suspected.
Explanation: Cryptographic adapter LIC not loaded or
Failing Item: not valid.
v IOA
Failing Item:
v IOP
v CRYPTLP
v PTFSRCH
v PTFSRCH
v IOA
B0136604 B0136604
Explanation: Operating voltage or temperature range B0136616 B0136616
limits exceeded.
Explanation: System log entry only, no service action
Response: Correct any conditions in the physical required
environment which might have caused the voltage or
temperature out-of-range error on the 4758 adapter
card. After you correct the conditions, vary off and then B0136617 B0136617
vary back on the 4758 device description associated Explanation: Adapter monitoring circuitry has failed.
with the 4758 adapter card.
Failing Item:
Failing Item:
v IOA
v CARDTMP
v PTFSRCH
B0136611 B0136611
B0136618 B0136618
Explanation: I/O adapter hardware error detected
Explanation: Adapter monitoring circuitry has
Failing Item: exceeded threshold.
v IOA Response: The adapter can be varied on and used, but
v PTFSRCH should be replaced during the next scheduled
maintenance of the system.
B0136613 B0136613 Failing Item:
v IOA
© Copyright IBM Corp. 2010, 2013 99
B0136619 • B0136620
v PTFSRCH
B0136619 B0136619
Explanation: Cryptographic adapter LIC is down level
Problem determination: The cryptographic adapter
can not confirm that an optional method for processing
cryptographic operations is currently available. This
can be for 2 different reasons:
v The most current version of its licensed internal code
is not installed on the system. The licensed internal
code for the adapter does not ship with the system.
For systems with Licensed Internal Code V5R4M5 or
earlier, it is contained within the licensed program
5733-CY1 Cryptographic Device Manager. For
systems with Licensed Internal Code V6R1M0 or
V6R1M1 it is contained within the licensed program
5733-CY2 Cryptographic Device Manager, and for
systems with Licensed Internal Code V7R1M0 or
later it is contained within the licensed program
5733-CY3 Cryptographic Device Manager.
v The Function Control Vector, which is required to be
loaded by the customer before performing any
cryptographic operations, has not been loaded.
Please refer to the "Loading a Function Control
Vector" in the cryptographic topic in the Security
section of the IBM i information center.
For both cases, the adapter is still available for use, but
may not take advantage of performance enhancements
found in a newer version of Cryptographic Device
Manager.
Note: This event is logged for every vary on of the
cryptographic card if one of the conditions above exist.
It should be rare to see a V6R1 or later system without
the upgraded version of the Cryptographic Device
Manager. Also, when the product is announced, the
customer will be instructed to load the code.
Failing Item:
v CRYPTLP
v PTFSRCH
B0136620 B0136620
Explanation: Cryptographic adapter not operating at
optimum performance
Response: The cryptographic adapter will continue to
run, but performance could be improved. Vary off the
cryptographic adapter and then vary it on. The vary on
may take up to 15 minutes. If the problem does not
reccur, optimum performance has been restored. If the
problem does reccur, contact your next level of support.
Failing Item:
v SVCDOCS
100 System reference codes (Bxxx)
(B014) Reference codes
v AJDG301
B0146661 B0146661
Explanation: Negative-acknowledgment received
B014B025 B014B025
Explanation: Clear-to-send signal did not drop in
B014B005 B014B005
required time
Explanation: Block-check error on data received
Failing Item:
Failing Item: v FI00701
v UJ0E3 v FI00704
v UJB35 v UJB35
v FI00704 v FI00719
v FI00705 v AJDG301
v FI00719
v UJE34 B014B030 B014B030
Explanation: Remote equipment did not respond in
B014B010 B014B010 time-out period
Explanation: Clear-to-send signal dropped on modem Failing Item:
interface
v UJ0E3
Failing Item: v FI00700
v FI00701 v UJB35
v FI00704 v FI00719
v FI00719 v FI00704
v AJDG301 v AJDG301
B014B015 B014B015 B014B035 B014B035
Explanation: Carrier-detect dropped on modem Explanation: Remote equipment did not respond in
interface time-out period
Failing Item: Failing Item:
v FI00701 v FI00700
v UJ0E3 v UJB35
v FI00704
v FI00705 B014B037 B014B037
v UJB35
Explanation: Too many or too few synchronization
v AJDG301 characters
v FI00719
Failing Item:
v UJ0E3
B014B020 B014B020
v FI00700
Explanation: Clear-to-send signal did not come up in v UJB35
required time
v FI00719
Failing Item: v FI00704
v FI00701 v AJDG301
v FI00704
v UJB35 B014B040 B014B040
v FI00719
Explanation: Time-out; no data received
© Copyright IBM Corp. 2010, 2013 101
B014B045 • B014B085
Failing Item:
B014B065 B014B065
v UJ0E3
Explanation: Protocol error
v UJB35
v FI00701 Failing Item:
v FI00719 v UJB35
v FI00704 v FI00718
v FI00700 v FI00700
v FI00719
B014B045 B014B045 v FI00704
Explanation: Unexpected response to
temporary-text-delay B014B070 B014B070
Failing Item: Explanation: Clock signal missing from external
communications interface
v FI00700
v UJ0E3 Failing Item:
v FI00719 v FI00701
v UJB35 v FI00704
v FI00704 v FI00719
B014B050 B014B050 B014B072 B014B072
Explanation: Unexpected response to Explanation: Clock signal missing from external
wait-acknowledge communications interface
Failing Item: Failing Item:
v FI00700 v FI00701
v UJ0E3 v FI00704
v FI00719 v FI00719
v UJB35
v FI00704 B014B075 B014B075
Explanation: Communications IOP processed data
B014B055 B014B055 received too slow
Explanation: Data loss because receive buffer full Failing Item:
v UJP37
Failing Item:
v UJB35
v UJB35
v FI00719
v UJ0E3
v UJ0E3
v FI00719
v FI00704
B014B085 B014B085
v FI00700
Explanation: Data-set-ready dropped on modem
interface
B014B060 B014B060
Failing Item:
Explanation: No response to temporary-text-delay or
wait-acknowledge v FI00701
v FI00704
Failing Item:
v FI00719
v UJ0E3
v UJ0E3
v UJB35
v AJDG301
v FI00701
v FI00719
v FI00704
v FI00700
102 System reference codes (Bxxx)
B014B090 • B014B110
B014B090 B014B090
Explanation: Negative-acknowledgment received
Failing Item:
v UJ0E3
v UJB35
v FI00719
v UJE34
v FI00704
B014B105 B014B105
Explanation: Data not recognized
Failing Item:
v UJ0E3
v FI00719
v UJB35
v FI00704
B014B110 B014B110
Explanation: Remote system did not receive last
acknowledgment sent
Failing Item:
v UJ0E3
v UJB35
v FI00719
v FI00704
(B014) Reference codes 103
104 System reference codes (Bxxx)
(B015) Reference codes
B015A555 B015A555 B015A5F3 B015A5F3
Explanation: I/O card Licensed Internal Code failed Explanation: I/O card Licensed Internal Code failed
Failing Item: Failing Item:
v FI00730 v FI00730
B015A5AA B015A5AA B015A5F5 B015A5F5
Explanation: I/O card Licensed Internal Code failed Explanation: I/O card Licensed Internal Code failed
Failing Item: Failing Item:
v FI00730 v FI00730
B015A5DD B015A5DD B015A5F7 B015A5F7
Explanation: I/O card Licensed Internal Code failed Explanation: I/O card Licensed Internal Code failed
Failing Item: Failing Item:
v FI00730 v FI00730
B015A5E1 B015A5E1 B015A5F9 B015A5F9
Explanation: I/O card Licensed Internal Code failed Explanation: I/O card Licensed Internal Code failed
Failing Item: Failing Item:
v FI00730 v FI00730
B015A5E2 B015A5E2 B015A5FA B015A5FA
Explanation: I/O card Licensed Internal Code failed Explanation: I/O card Licensed Internal Code failed
Failing Item: Failing Item:
v FI00730 v FI00730
B015A5EE B015A5EE B015A5FC B015A5FC
Explanation: I/O card Licensed Internal Code failed Explanation: I/O card Licensed Internal Code failed
Failing Item: Failing Item:
v FI00730 v FI00730
B015A5F1 B015A5F1 B015A800 B015A800
Explanation: I/O card Licensed Internal Code failed Explanation: I/O card Licensed Internal Code failed
Failing Item: Failing Item:
v FI00730 v UJE36
B015A5F2 B015A5F2 B015A802 B015A802
Explanation: I/O card Licensed Internal Code failed Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v FI00730 Failing Item:
v AJDG301
© Copyright IBM Corp. 2010, 2013 105
B015A803 • B015A847
B015A803 B015A803 B015A825 B015A825
Explanation: Input value error in I/O card Licensed Explanation: Procedure error in vertical Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
v FI00730
B015A804 B015A804
Explanation: Input value error in I/O card Licensed B015A837 B015A837
Internal Code Explanation: Procedure error in vertical Licensed
Failing Item: Internal Code
v AJDG301 Failing Item:
v AJDG301
B015A807 B015A807 v FI00730
Explanation: Input value error in I/O card Licensed
Internal Code B015A83C B015A83C
Failing Item: Explanation: Procedure error in vertical Licensed
v FI00730 Internal Code
v AJDG301 Failing Item:
v AJDG301
B015A814 B015A814
Explanation: Procedure error in vertical Licensed B015A83D B015A83D
Internal Code Explanation: Procedure error in vertical Licensed
Failing Item: Internal Code
v AJDG301 Failing Item:
v FI00730 v FI00730
B015A820 B015A820 B015A845 B015A845
Explanation: Procedure error in vertical Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
B015A821 B015A821 B015A846 B015A846
Explanation: Input value error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
B015A823 B015A823 B015A847 B015A847
Explanation: Input value error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v AJDG301 v AJDG301
106 System reference codes (Bxxx)
B015AA09 • B015AFFF
B015AA09 B015AA09 B015AF07 B015AF07
Explanation: Response from I/O card Licensed Explanation: Local area network adapter; remote
Internal Code not expected station error
Failing Item: Failing Item:
v FI00730 v UJE39
B015AA10 B015AA10 B015AF08 B015AF08
Explanation: Number of stations greater than allowed Explanation: Wrong response received from I/O card
in configuration Licensed Internal Code
Failing Item: Failing Item:
v UJE35 v FI00730
B015AA13 B015AA13 B015AF09 B015AF09
Explanation: Procedure error in I/O card Licensed Explanation: Input value error in I/O card Licensed
Internal Code Internal Code
Failing Item: Failing Item:
v FI00730 v FI00730
v AJDG301
B015AA16 B015AA16
Explanation: Procedure error in I/O card Licensed B015AFFF B015AFFF
Internal Code Explanation: Procedure error in vertical Licensed
Failing Item: Internal Code
v FI00730 Failing Item:
v FI00730
B015AA17 B015AA17 v UJE34
Explanation: I/O card Licensed Internal Code failed
Failing Item:
v FI00730
B015AA18 B015AA18
Explanation: I/O card Licensed Internal Code failed
Failing Item:
v FI00730
B015AF04 B015AF04
Explanation: Wrong response received from I/O card
Licensed Internal Code
Failing Item:
v AJDG301
B015AF05 B015AF05
Explanation: Local area network adapter; remote
station error
Failing Item:
v UJE39
(B015) Reference codes 107
108 System reference codes (Bxxx)
(B017) Reference codes
B0170001 B0170001
Explanation: Low battery condition detected on IOA.
Failing Item:
v CRYPBAT
B0179001 B0179001
Explanation: Information only, no service action
required
© Copyright IBM Corp. 2010, 2013 109
110 System reference codes (Bxxx)
(B025) Reference codes
B025A000 B025A000 B025A6D6 B025A6D6
Explanation: Input value error in I/O card Licensed Explanation: Wrong configuration data given to
Internal Code Ethernet controller
Failing Item: Failing Item:
v AJDGP01 v AJDG301
B025A001 B025A001 B025A6D9 B025A6D9
Explanation: Input value error in I/O card Licensed Explanation: Ethernet adapter card error
Internal Code
Failing Item:
Failing Item: v IOA
v AJDG301 v FI00722
v IOP
B025A013 B025A013
Explanation: Wrong configuration data given to B025A6E3 B025A6E3
Ethernet controller
Explanation: Ethernet adapter or network device
Failing Item: cabling error
v AJDG301 Failing Item:
v FI00722
B025A01B B025A01B v UJE40
Explanation: Input value error in I/O card Licensed v IOA
Internal Code
Failing Item: B025A6F2 B025A6F2
v AJDG301 Explanation: Configured line speed not supported by
network.
B025A209 B025A209 Failing Item:
Explanation: Input value error in I/O card Licensed v UJE35
Internal Code
Failing Item: B025A6F3 B025A6F3
v AJDG301 Explanation: Configuration of DUPLEX parameter not
supported by network.
B025A404 B025A404 Failing Item:
Explanation: Ethernet adapter card error v UJE35
Failing Item:
v IOA B025A6F4 B025A6F4
v AJDGP01 Explanation: Unable to establish a network link.
Failing Item:
B025A6D5 B025A6D5 v UJE35
Explanation: Wrong configuration data given to v FI00722
Ethernet controller
Failing Item: B025A800 B025A800
v AJDG301 Explanation: MAXFRAME value in CRTLINETH
command too large.
© Copyright IBM Corp. 2010, 2013 111
B025A801 • B025B001
Failing Item:
v UJE35
B025A801 B025A801
Explanation: Adapter does not support
user-configured adapter address
Failing Item:
v UJE35
B025B000 B025B000
Explanation: System log entry only, no service action
required
B025B001 B025B001
Explanation: Automatic recovery has been attempted
on the ethernet port
Response: This error is logged for information only.
No service action is required.
112 System reference codes (Bxxx)
(B026) Reference codes
B026A000 B026A000 B026A01D B026A01D
Explanation: I/O card Licensed Internal Code error Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v FI00730 Failing Item:
v AJDG301
B026A001 B026A001
B026A01F B026A01F
Explanation: Input value error in I/O card Licensed
Internal Code Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v FI00730 Failing Item:
v AJDG301 v FI00730
v AJDG301
B026A002 B026A002
B026A020 B026A020
Explanation: Input value error in I/O card Licensed
Internal Code Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v FI00730 Failing Item:
v FI00730
B026A003 B026A003
B026A022 B026A022
Explanation: Procedure error in I/O card Licensed
Internal Code Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v FI00730 Failing Item:
v AJDG301
B026A013 B026A013
B026A027 B026A027
Explanation: Address error on communications IOP
card Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v UJ9GC Failing Item:
v FI00730
B026A01B B026A01B
B026A028 B026A028
Explanation: Input value error in I/O card Licensed
Internal Code Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v AJDG301 Failing Item:
v FI00730
B026A01C B026A01C v AJDG301
Explanation: Input value error in I/O card Licensed
Internal Code B026A02A B026A02A
Failing Item: Explanation: Input value error in I/O card Licensed
Internal Code
v AJDG301
v FI00730 Failing Item:
© Copyright IBM Corp. 2010, 2013 113
B026A02B • B026A210
v FI00730
B026A205 B026A205
Explanation: Licensed Internal Code received not
B026A02B B026A02B
correct response
Explanation: I/O card Licensed Internal Code error
Failing Item:
Failing Item: v FI00730
v FI00730
v AJDG301 B026A206 B026A206
Explanation: Input value error in I/O card Licensed
B026A02C B026A02C Internal Code
Explanation: Input value error in I/O card Licensed Failing Item:
Internal Code
v AJDG301
Failing Item:
v FI00730 B026A209 B026A209
v AJDG301
Explanation: Procedure error in I/O card Licensed
Internal Code
B026A02D B026A02D
Failing Item:
Explanation: Input value error in I/O card Licensed v AJDG301
Internal Code
Failing Item: B026A20A B026A20A
v AJDG301
Explanation: Input value error in I/O card Licensed
Internal Code
B026A030 B026A030
Failing Item:
Explanation: Procedure error in I/O card Licensed v AJDG301
Internal Code
Failing Item: B026A20B B026A20B
v FI00730
Explanation: Input value error in I/O card Licensed
Internal Code
B026A201 B026A201
Failing Item:
Explanation: Communications adapter detected v AJDG301
storage access error
Failing Item: B026A20C B026A20C
v FI00730
Explanation: Input value error in I/O card Licensed
Internal Code
B026A203 B026A203
Failing Item:
Explanation: Input value error in I/O card Licensed v FI00730
Internal Code
v AJDG301
Failing Item:
v AJDG301 B026A210 B026A210
Explanation: Procedure error in I/O card Licensed
B026A204 B026A204 Internal Code
Explanation: Input value error in I/O card Licensed Failing Item:
Internal Code
v FI00730
Failing Item:
v AJDG301
114 System reference codes (Bxxx)
B026A213 • B026FFFF
B026A213 B026A213 B026A6D6 B026A6D6
Explanation: I/O card Licensed Internal Code error Explanation: Adapter card detected not valid data
Failing Item: Failing Item:
v FI00730 v AJDG301
B026A300 B026A300 B026A6D7 B026A6D7
Explanation: I/O Adapter hardware error detected Explanation: Adapter card detected not valid data
Failing Item: Failing Item:
v IOA v FI00730
v IOP
B026A710 B026A710
B026A301 B026A301 Explanation: I/O Adapter hardware error detected
Explanation: I/O Adapter hardware error detected Failing Item:
Failing Item: v IOA
v IOA
v IOP B026FFFF B026FFFF
Explanation: User suspected communications
B026A302 B026A302 problem.
Explanation: I/O Adapter hardware error detected Failing Item:
Failing Item: v USER
v IOA
v IOP
B026A40B B026A40B
Explanation: Address error on communications IOP
card
Failing Item:
v IOA
B026A6C2 B026A6C2
Explanation: I/O card Licensed Internal Code error
Failing Item:
v AJDG301
B026A6D4 B026A6D4
Explanation: Procedure error in I/O card Licensed
Internal Code
Failing Item:
v AJDG301
B026A6D5 B026A6D5
Explanation: Input value error in I/O card Licensed
Internal Code
Failing Item:
v AJDG301
(B026) Reference codes 115
116 System reference codes (Bxxx)
(B028) Reference codes
B0281200 B0281200 B0281705 B0281705
Explanation: Communications controller task ended Explanation: Frame reject type X received
abnormally; type 1
Failing Item:
Failing Item: v FI00730
v FI00730 v UJ0E3
B0281201 B0281201 B0281706 B0281706
Explanation: Communications controller task ended Explanation: Frame reject type Y received
abnormally; type 2
Failing Item:
Failing Item:
v FI00730
v FI00730
v UJJ35
B0281202 B0281202
B0281707 B0281707
Explanation: Communications controller task ended
Explanation: Frame reject type Z received
abnormally; type 3
Failing Item:
Failing Item:
v FI00730
v FI00730
v UJ0E3
B0281701 B0281701
B0281708 B0281708
Explanation: Disconnect mode frame received
Explanation: Frame reject type W sent
Failing Item:
Failing Item:
v UJ0E9
v UJ0E3
v FI00730
B0281702 B0281702
Explanation: Disconnect mode frame received during
B0281709 B0281709
link activation
Explanation: Frame reject type X sent
Failing Item:
v UJ0E3 Failing Item:
v UJ0E3
B0281703 B0281703 v FI00730
Explanation: Disconnect mode frame received when
transmitting information B028170A B028170A
Failing Item: Explanation: Frame reject type Y sent
v UJ0E3 Failing Item:
v FI00730 v UJJ35
v UJ0E3
B0281704 B0281704
Explanation: Frame reject type W received B028170B B028170B
Failing Item: Explanation: Frame reject type Z sent
v FI00730 Failing Item:
v UJ0E3 v FI00730
v UJ0E3
© Copyright IBM Corp. 2010, 2013 117
B028170C • B0284592
B028170C B028170C B0282654 B0282654
Explanation: Frame retry limit reached Explanation: First call failed, retrying call; CFI ET
from modem
Failing Item:
v UJ0E9 Failing Item:
v FI00701 v UJ0E3
v FI00704 v UJA35
v UJJ35
B0282656 B0282656
B028170D B028170D Explanation: First call failed, retrying call; CFI NT
from modem
Explanation: Set-asynchronous-balance-mode frame
received in data mode Failing Item:
Failing Item: v UJ0E3
v FI00730 v FI00705
v UJ0E3 v UJA35
B028170E B028170E B0282657 B0282657
Explanation: Wrong response received from remote Explanation: First call failed, retrying call; CFI RT
equipment from modem
Failing Item: Failing Item:
v UJJ35 v UJ0E3
v UJ0E3 v UJA35
v FI00700
B0282660 B0282660
B0282651 B0282651 Explanation: Call failed, retrying call; Non-standard
CFI from modem
Explanation: First call failed, retrying call; no CFI
from modem Failing Item:
Failing Item: v UJ0E3
v UJE34 v FI00704
v UJJ35
v FI00704 B028450A B028450A
v FI00701 Explanation: Incorrect command value sent by vertical
LIC
B0282652 B0282652 Failing Item:
Explanation: First call failed, retrying call; CFI AB v AJDG301
from modem
Failing Item: B0284590 B0284590
v UJ0E3 Explanation: Wrong telephone number specified in
v FI00704 system configuration
v UJA35 Failing Item:
v UJA35
B0282653 B0282653 v FI00751
Explanation: First call failed, retrying call; CFI DE
from modem B0284592 B0284592
Failing Item: Explanation: No number specified in controller
v UJ0E3 description
v FI00704 Failing Item:
118 System reference codes (Bxxx)
B0284594 • B0285014
v UJA35
B028500D B028500D
v FI00751
Explanation: Wrong data length received by
communications controller
B0284594 B0284594
Failing Item:
Explanation: Wrong telephone number specified in
v FI00751
system configuration
v UJJ35
Failing Item:
v UJA35
B028500E B028500E
v FI00751
Explanation: Wrong command value received by
communications IOP
B0285000 B0285000
Failing Item:
Explanation: Wrong command received by
v FI00751
communications controller
Failing Item:
B028500F B028500F
v FI00751
Explanation: Wrong command value received by
communications IOP
B0285002 B0285002
Failing Item:
Explanation: Wrong procedure followed by I/O card
v FI00751
Licensed Internal Code
Failing Item:
B0285010 B0285010
v FI00751
Explanation: Wrong reset option received by
communications controller
B0285008 B0285008
Failing Item:
Explanation: Procedure error in vertical Licensed
v FI00751
Internal Code
v FI00730
Failing Item:
v UJE34
B0285011 B0285011
Explanation: Wrong command value received by
B0285009 B0285009
communications IOP
Explanation: Wrong command value received by
Failing Item:
communications IOP
v FI00751
Failing Item:
v FI00730
v FI00751
B0285012 B0285012
B028500B B028500B
Explanation: Wrong session ID received by
Explanation: Wrong command value received by communications controller
communications IOP
Failing Item:
Failing Item:
v FI00751
v FI00751
v FI00730
B028500C B028500C
B0285014 B0285014
Explanation: Wrong command value received by
Explanation: Wrong command value received by
communications IOP
communications IOP
Failing Item:
Failing Item:
v FI00751
v FI00751
v FI00730
(B028) Reference codes 119
B0285015 • B02850E0
B0285015 B0285015 B028501C B028501C
Explanation: Communications line already in use Explanation: Wrong command value received by
communications IOP
Failing Item:
v FI00751 Failing Item:
v FI00730 v FI00730
B0285016 B0285016 B028501E B028501E
Explanation: Wrong command value received by Explanation: Wrong command value received by
communications IOP communications IOP
Failing Item: Failing Item:
v FI00751 v FI00730
v FI00730
B028501F B028501F
B0285017 B0285017 Explanation: Wrong command value received by
communications IOP
Explanation: Wrong storage value received;
communications controller Failing Item:
Failing Item: v FI00730
v FI00751
v FI00730 B0285022 B0285022
Explanation: Port already in use
B0285018 B0285018 Failing Item:
Explanation: Wrong trace type received by v FI00751
communications controller v FI00730
Failing Item:
v FI00751 B0285023 B0285023
v FI00730 Explanation: Procedure error in vertical Licensed
Internal Code
B0285019 B0285019 Failing Item:
Explanation: Wrong trace length received by v FI00751
communications controller
Failing Item: B0285024 B0285024
v FI00751 Explanation: DTE/DCE role negotiation not valid for
v FI00730 leased line
Failing Item:
B028501A B028501A v FI00751
Explanation: Communications controller temporary
storage area too small B02850E0 B02850E0
Failing Item: Explanation: Wrong or no external communications
v FI00751 cable installed
Failing Item:
B028501B B028501B v UJJ35
Explanation: Wrong ID length value sent by vertical v FI00701
LIC v IOA
Failing Item:
v FI00751
120 System reference codes (Bxxx)
B02850E1 • B02850F5
B02850E1 B02850E1 B02850E9 B02850E9
Explanation: Port already in use Explanation: Wrong command value sent by IBM i
Operating System licensed program
Failing Item:
v UJJ35 Failing Item:
v FI00730 v AJDG301
B02850E3 B02850E3 B02850EC B02850EC
Explanation: Wrong command value sent by IBM i Explanation: Wrong command value sent by IBM i
Operating System licensed program Operating System licensed program
Failing Item: Failing Item:
v AJDG301 v AJDG301
v UJJ35
B02850ED B02850ED
B02850E4 B02850E4 Explanation: Wrong command value sent by IBM i
Operating System licensed program
Explanation: Wrong command value sent by IBM i
Operating System licensed program Failing Item:
Failing Item: v AJDG301
v AJDG301
B02850EE B02850EE
B02850E5 B02850E5 Explanation: Wrong command value sent by IBM i
Operating System licensed program
Explanation: Wrong adapter type value sent by
Vertical LIC Failing Item:
Failing Item: v AJDG301
v FI00751
v UJJ35 B02850F1 B02850F1
Explanation: Communications adapter card not
B02850E6 B02850E6 installed
Explanation: Wrong slot number value sent by Failing Item:
Vertical LIC v AJDG301
Failing Item: v UJJ35
v FI00751 v IOA
v UJJ35
B02850F2 B02850F2
B02850E7 B02850E7 Explanation: V.25 adapter not installed
Explanation: Incorrect command value sent by vertical Failing Item:
LIC v UJJ35
Failing Item: v FI00702
v UJJ35 v IOA
v FI00751
B02850F5 B02850F5
B02850E8 B02850E8 Explanation: Network uncontrolled-not-ready
Explanation: Wrong command value sent by IBM i warning; information only
Operating System licensed program Failing Item:
Failing Item: v UJE34
v AJDG301
(B028) Reference codes 121
B02850F6 • B02852EA
B02850F6 B02850F6 B02852E3 B02852E3
Explanation: Network controlled-not-ready warning; Explanation: Wrong response sent by I/O card
information only Licensed Internal Code
Failing Item: Failing Item:
v UJE34 v FI00730
B02850F7 B02850F7 B02852E4 B02852E4
Explanation: Data-set-ready changed to not active; for Explanation: Wrong command value sent by IBM i
information only Operating System licensed program
Failing Item: Failing Item:
v UJE34 v AJDG301
B0285203 B0285203 B02852E5 B02852E5
Explanation: I/O card Licensed Internal Code Explanation: Wrong command value received by
resource not available communications IOP
Failing Item: Failing Item:
v FI00730 v FI00730
B0285206 B0285206 B02852E7 B02852E7
Explanation: Communications controller storage not Explanation: X.21 network not in the ready or
available receive-data state
Failing Item: Failing Item:
v FI00730 v FI00704
v IOA
B02852E0 B02852E0 v FI00701
Explanation: Incorrect command used by I/O card
Licensed Internal Code B02852E8 B02852E8
Failing Item: Explanation: Error when releasing communications
v FI00730 controller storage
Failing Item:
B02852E1 B02852E1 v FI00730
Explanation: Wrong procedure followed by I/O card
Licensed Internal Code B02852E9 B02852E9
Failing Item: Explanation: Error when assigning communications
v FI00730 controller storage
Failing Item:
B02852E2 B02852E2 v FI00730
Explanation: I/O card Licensed Internal Code
resource not available B02852EA B02852EA
Failing Item: Explanation: I/O card Licensed Internal Code error
v FI00730 Failing Item:
v UJJ35 v FI00730
122 System reference codes (Bxxx)
B0285301 • B028560B
v FI00702
B0285301 B0285301
v IOA
Explanation: Adapter card receive error
Failing Item: B02854E1 B02854E1
v IOA
Explanation: Port not operational
Failing Item:
B0285302 B0285302
v IOA
Explanation: Adapter card transmit error
v UJJ35
Failing Item:
v IOA B0285600 B0285600
Explanation: Clear-to-send off; error limit per 256
B0285401 B0285401 reached
Explanation: Communications IOP interrupt not Failing Item:
expected
v FI00704
Failing Item:
v IOA B0285601 B0285601
Explanation: Data-set-ready state changed; error limit
B0285410 B0285410 per 256 reached
Explanation: Data-set-ready error on modem interface Failing Item:
Failing Item: v FI00704
v FI00704
v FI00702 B0285602 B0285602
v IOA Explanation: Clear-to-send state changed; error limit
per 256 reached
B0285472 B0285472 Failing Item:
Explanation: Data-line-occupied initially 'on' error v FI00704
Failing Item:
v FI00702 B0285603 B0285603
v FI00703 Explanation: Carrier-detect state changed; error limit
v UJ0E3 per 256 reached
v IOA Failing Item:
v FI00701
B0285474 B0285474 v FI00704
Explanation: Automatic call unit has v FI00705
data-line-occupied error v UJ0E3
Failing Item:
v FI00702 B028560B B028560B
v FI00703 Explanation: Data-set-ready error; error limit per 256
v UJ0E3 reached
v IOA Failing Item:
v FI00701
B0285476 B0285476 v FI00704
Explanation: Automatic call unit has v UJ0E3
present-next-digit error v FI00705
Failing Item:
v FI00703
(B028) Reference codes 123
B0285630 • B02856F1
v FI00701
B0285630 B0285630
v AJDG301
Explanation: Automatic call unit has
distant-station-connected error
B02856EA B02856EA
Failing Item:
Explanation: Clear-to-send signal dropped on modem
v FI00700
interface
v UJ0E3
Failing Item:
v UJJ35
v UJ0E3
v FI00701
v FI00704
v IOA
v UJJ35
v IOA
B0285632 B0285632
v FI00701
Explanation: Automatic call unit has data-set-ready
error
B02856EB B02856EB
Failing Item:
Explanation: Carrier-detect dropped on modem
v FI00700
interface
v UJJ35
Failing Item:
v UJA35
v FI00701
v FI00703
v FI00704
v FI00701
v FI00705
v IOA
v UJ0E3
v UJ0E3
v IOA
B0285651 B0285651
B02856EC B02856EC
Explanation: Call failed, no Call Failure Indication
from modem Explanation: Data-set-ready signal turn-off time-out
Failing Item: Failing Item:
v UJE34 v FI00704
v UJJ35 v UJJ35
v FI00704 v FI00701
v FI00701 v IOA
B02856E8 B02856E8 B02856ED B02856ED
Explanation: Clear-to-send not active on modem Explanation: Data-set-ready signal turn-on time-out
interface Failing Item:
Failing Item: v FI00704
v UJ0E3 v IOA
v FI00704 v FI00701
v UJJ35 v AJDG301
v FI00701
v IOA B02856F1 B02856F1
Explanation: Data-set-ready dropped on modem
B02856E9 B02856E9 interface
Explanation: Clear-to-send signal failed to drop on Failing Item:
modem interface v FI00704
Failing Item: v FI00705
v FI00704 v UJ0E3
v IOA v FI00701
124 System reference codes (Bxxx)
B0285718 • B02857F1
v IOA v FI00705
v FI00704
B0285718 B0285718 v UJ0E3
Explanation: SABM response or UA command
received B02857E3 B02857E3
Failing Item: Explanation: Abnormal end received; error limit per
v UJJ35 256 reached
v UJ0E3 Failing Item:
v FI00751
B0285719 B0285719 v FI00700
Explanation: Protocol mismatch during link v FI00705
initialization v FI00704
Failing Item: v UJ0E3
v UJA35
v FI00700 B02857E4 B02857E4
v UJ0E3 Explanation: Underrun threshold error; limit per 256
reached
B0285721 B0285721 Failing Item:
Explanation: Could not send frame to remote v IOA
equipment; local problem
Failing Item: B02857E5 B02857E5
v FI00704 Explanation: Long frame; error limit per 256 reached
v AJDG301 Failing Item:
v FI00701 v UJJ35
v IOA v FI00751
v FI00700
B02857E0 B02857E0
Explanation: Frame check error; error limit per 256 B02857F0 B02857F0
reached
Explanation: Send sequence counter error; error limit
Failing Item: per 256 reached
v UJ0E3 Failing Item:
v FI00705 v FI00751
v FI00704 v FI00701
v FI00704
B02857E1 B02857E1 v UJ0E3
Explanation: Overrun error; error limit per 256
reached B02857F1 B02857F1
Failing Item: Explanation: Receive sequence counter error; error
v UJJ35 limit per 256 reached
v FI00751 Failing Item:
v FI00751
B02857E2 B02857E2 v FI00700
Explanation: Short frame error; error limit per 256
reached
Failing Item:
v FI00700
v FI00751
(B028) Reference codes 125
B02857F2 • B028FFFF
B02857F2 B02857F2 B0286870 B0286870
Explanation: Response time-out error; error limit per Explanation: Automatic call unit power turned off
256 reached
Failing Item:
Failing Item: v FI00703
v FI00700 v FI00702
v UJ0E3 v IOA
v FI00751
v FI00704 B0288011 B0288011
v UJJ35
Explanation: IOP Activation failed.
v FI00705
Response: The MDMCNTRYID parameter in Network
v AJDG301
Attributes is not set. Use the CHGNETA command to
set MDMCNTRYID.
B0285886 B0285886
Failing Item:
Explanation: Automatic call unit switched link v UJE34
time-out; no answer
Failing Item: B0288013 B0288013
v FI00703
Explanation: IOP Activation failed.
v IOA
Response: The MDMCNTRYID parameter in Network
v FI00702
Attributes is not valid for this adapter. Use the
v UJ0E3 CHGNETA command to change the MDMCNTRYID
value.
B0285E01 B0285E01 Failing Item:
Explanation: Call error; incoming call received during v UJE34
outgoing call
Failing Item: B0288020 B0288020
v UJ0E3 Explanation: User suspected communications
problem.
B0286320 B0286320
Explanation: Automatic call unit has abandon-call B028DA00 B028DA00
attempt Explanation: The I/O card LIC detected an internal
Failing Item: error
v FI00700 Failing Item:
v UJA35 v FI00730
v FI00703
v IOA B028DA01 B028DA01
v FI00702 Explanation: The I/O card LIC detected an internal
error
B0286322 B0286322 Failing Item:
Explanation: Abandon call retry error; incorrect v FI00730
number length v IOA
Failing Item:
v UJA35 B028FFFF B028FFFF
v FI00703 Explanation: User suspected communications
problem.
Failing Item:
v USER
126 System reference codes (Bxxx)
(B038) Reference codes
B0387000 B0387000 B038700F B038700F
Explanation: Vertical Licensed Internal Code sent an Explanation: Communications controller storage not
incorrect command available
Failing Item: Failing Item:
v FI00751 v FI00751
v FI00730 v FI00730
B0387002 B0387002 B0387010 B0387010
Explanation: Vertical LIC sent incorrect command Explanation: Vertical LIC sent commands in wrong
values order
Failing Item: Failing Item:
v FI00751 v FI00751
v FI00730 v FI00730
B0387004 B0387004 B0387012 B0387012
Explanation: Vertical LIC sent commands in wrong Explanation: I/O card LIC followed incorrect
order procedure
Failing Item: Failing Item:
v FI00751 v FI00730
v FI00730
B0387014 B0387014
B0387006 B0387006 Explanation: Vertical LIC sent commands in wrong
Explanation: Vertical LIC sent incorrect command order
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B0387018 B0387018
B0387008 B0387008 Explanation: Configuration exceeds allowed
Explanation: Vertical LIC sent incorrect command maximum for X.25 lines
values Failing Item:
Failing Item: v UJJ39
v FI00751
v FI00730 B038701A B038701A
Explanation: Wrong command value sent by IBM i
B038700C B038700C Operating System licensed program
Explanation: Vertical LIC sent commands in wrong Failing Item:
order v AJDG301
Failing Item: v FI00730
v FI00751
v FI00730 B038701C B038701C
Explanation: Wrong command value sent by IBM i
© Copyright IBM Corp. 2010, 2013 127
B038701E • B0387054
Operating System licensed program Failing Item:
Failing Item: v UJJ37
v AJDG301 v FI00751
v FI00730
B0387048 B0387048
B038701E B038701E Explanation: Vertical LIC sent incorrect command
values
Explanation: Wrong command value sent by IBM i
Operating System licensed program Failing Item:
Failing Item: v FI00751
v UJJ36 v FI00730
v FI00730
B0387049 B0387049
B0387020 B0387020 Explanation: Vertical LIC sent incorrect command
values
Explanation: Vertical LIC sent incorrect command
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B038704A B038704A
B0387024 B0387024 Explanation: Vertical LIC sent incorrect command
values
Explanation: No logical link available for packet
network Failing Item:
Failing Item: v FI00751
v UJE38 v FI00730
v FI00751
B038704C B038704C
B0387028 B0387028 Explanation: Vertical LIC sent incorrect command
values
Explanation: No outgoing or two-way logical link
available Failing Item:
Failing Item: v FI00751
v UJE38 v FI00730
v FI00751
B0387050 B0387050
B038702C B038702C Explanation: Vertical LIC sent commands in wrong
order
Explanation: Remote station not connected
Failing Item:
Response: This reference code usually identifies a
condition that is due to a timing problem that will be v FI00751
recovered. v FI00730
Failing Item:
v UJJ37 B0387054 B0387054
v FI00751 Explanation: Vertical Licensed Internal Code sent
wrong password length
B0387030 B0387030 Failing Item:
Explanation: Logical link already disconnected v FI00751
v FI00730
Response: This reference code usually identifies a
condition that is due to a timing problem that will be
recovered.
128 System reference codes (Bxxx)
B0387056 • B0387718
v FI00730
B0387056 B0387056
Explanation: Vertical LIC sent incorrect command
B0387090 B0387090
values
Explanation: I/O card LIC followed incorrect
Failing Item:
procedure
v FI00751
Failing Item:
v FI00730
v FI00751
v FI00730
B0387058 B0387058
Explanation: Vertical LIC sent incorrect command
B0387092 B0387092
values
Explanation: Vertical LIC sent incorrect command
Failing Item:
values
v FI00751
Failing Item:
v FI00730
v UJJ38
v FI00751
B038705C B038705C
v FI00730
Explanation: Vertical LIC sent incorrect command
values
B0387094 B0387094
Failing Item:
Explanation: Vertical LIC sent incorrect command
v FI00751
values
v FI00730
Failing Item:
v FI00751
B0387064 B0387064
v FI00730
Explanation: Vertical Licensed Internal Code sent
wrong data length
B038728C B038728C
Failing Item:
Explanation: Vertical LIC sent incorrect command
v FI00751
values
v FI00730
Failing Item:
v FI00730
B038707C B038707C
Explanation: Vertical LIC sent incorrect command
B03872F0 B03872F0
values
Explanation: I/O card Licensed Internal Code ended
Failing Item:
abnormally
v FI00751
Failing Item:
v FI00730
B0387080 B0387080
Explanation: Vertical Licensed Internal Code sent an
B03872F2 B03872F2
incorrect command
Explanation: I/O card Licensed Internal Code stopped
Failing Item:
because of error
v FI00751
Failing Item:
v FI00730
v FI00730
B0387084 B0387084
B0387718 B0387718
Explanation: Number of user requests more than
maximum allowed Explanation: Network procedure error detected by
I/O card lic int code
Failing Item:
Failing Item:
v FI00751
v UJJ36
(B038) Reference codes 129
B0387740 • B03877A6
v UJ0E2 v UJJ37
B0387740 B0387740 B0387794 B0387794
Explanation: Remote system sent disconnect Explanation: Expected password not provided by
command remote system
Failing Item: Failing Item:
v UJ0E2 v UJ0E2
B0387744 B0387744 B0387798 B0387798
Explanation: Remote system sent disconnect mode Explanation: Remote system did not respond to test
frame command
Failing Item: Failing Item:
v UJ0E2 v UJ0E2
v UJJ36
B0387768 B0387768
Explanation: Remote system did not respond to B03877A0 B03877A0
command sent Explanation: Checksum error; error limit per 256
Failing Item: reached
v UJJ36 Failing Item:
v UJ0E2 v UJ0E2
v UJ0E9
B038776C B038776C v FI00730
Explanation: Remote system did not respond to
command sent B03877A2 B03877A2
Failing Item: Explanation: Bad data sent; error limit per 256
v UJ0E2 reached
v UJJ36 Failing Item:
v UJ0E9
B0387770 B0387770
Explanation: Remote system did not respond to B03877A4 B03877A4
disconnect command Explanation: Bad data received; error limit per 256
Failing Item: reached
v UJJ36 Failing Item:
v UJ0E2 v UJ0E9
v UJJ35
B0387774 B0387774
Explanation: Remote system did not verify receiving B03877A6 B03877A6
data Explanation: Remote system not ready; error limit per
Failing Item: 256 reached
v UJJ36 Failing Item:
v UJ0E2 v UJ0E2
v UJ0E9
B0387788 B0387788 v UJJ35
Explanation: Call rejected; wrong value from remote
system
Failing Item:
v UJ0E6
130 System reference codes (Bxxx)
B0387800 • B0387840
v FI00730
B0387800 B0387800
Explanation: Vertical Licensed Internal Code sent an
B0387812 B0387812
incorrect command
Explanation: Procedure error in vertical Licensed
Failing Item:
Internal Code
v FI00751
Failing Item:
v FI00730
v FI00751
B0387802 B0387802
B0387820 B0387820
Explanation: Vertical LIC sent incorrect command
values Explanation: Too many logical channels defined
Failing Item: Failing Item:
v FI00751 v UJJ36
v FI00730 v FI00730
B0387804 B0387804 B0387824 B0387824
Explanation: Vertical LIC sent commands in wrong Explanation: Outgoing and two-way logical channel
order not available
Failing Item: Response: This reference code usually identifies a
condition that is due to a timing problem that will be
v FI00751
recovered.
v FI00730
Failing Item:
v UJJ37
B0387806 B0387806
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B0387828 B0387828
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B0387808 B0387808
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B038782C B038782C
v FI00751
Explanation: Vertical LIC sent commands in wrong
v FI00730
order
Failing Item:
B038780C B038780C
v FI00751
Explanation: Vertical LIC sent commands in wrong
v FI00730
order
Failing Item:
B0387840 B0387840
v FI00751
Explanation: Vertical LIC sent incorrect command
values
B0387810 B0387810
Failing Item:
Explanation: Vertical LIC sent commands in wrong
v AJDG301
order
v FI00730
Failing Item:
v FI00751
(B038) Reference codes 131
B0387842 • B0387860
v FI00751
B0387842 B0387842
v FI00730
Explanation: Vertical LIC sent incorrect command
values
B0387854 B0387854
Failing Item:
Explanation: Vertical LIC sent incorrect command
v AJDG301
values
v FI00730
Failing Item:
v FI00751
B0387844 B0387844
v FI00730
Explanation: Vertical LIC sent incorrect command
values
B0387857 B0387857
Failing Item:
Explanation: Vertical LIC sent incorrect command
v AJDG301
values
v FI00730
Failing Item:
v AJDG301
B0387846 B0387846
v FI00730
Explanation: Communications controller storage not
available
B0387858 B0387858
Failing Item:
Explanation: Vertical LIC sent incorrect command
v FI00751
values
v FI00730
Failing Item:
v FI00751
B038784C B038784C
v FI00730
Explanation: Vertical LIC sent incorrect command
values
B038785A B038785A
Failing Item:
Explanation: Application sent invalid Q/M bit request
v FI00751
sequence
v FI00730
Failing Item:
v UJ0E6
B038784D B038784D
v AJDG301
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B038785C B038785C
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B038784E B038784E
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B0387860 B0387860
v FI00751
Explanation: Vertical LIC sent incorrect command
v FI00730
values
Failing Item:
B0387850 B0387850
v UJJ38
Explanation: Vertical LIC sent incorrect command
values
Failing Item:
132 System reference codes (Bxxx)
B0387864 • B038788C
B0387864 B0387864 B0387876 B0387876
Explanation: Vertical LIC sent incorrect command Explanation: Wrong command value sent by IBM i
values Operating System licensed program
Failing Item: Failing Item:
v UJJ38 v AJDG301
v FI00751 v FI00730
v FI00730
B0387878 B0387878
B0387868 B0387868 Explanation: Vertical LIC sent incorrect command
Explanation: Vertical LIC sent incorrect command values
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B038787A B038787A
B038786C B038786C Explanation: PLC/HDLC DTE/DCE mode configured
Explanation: Vertical LIC sent incorrect command not valid
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B038787C B038787C
B0387870 B0387870 Explanation: Vertical LIC sent incorrect command
Explanation: Vertical LIC sent incorrect command values
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B0387884 B0387884
B0387872 B0387872 Explanation: Procedure error in vertical Licensed
Explanation: Wrong command value sent by IBM i Internal Code
Operating System licensed program Failing Item:
Failing Item: v FI00751
v AJDG301 v FI00730
v FI00730
B0387888 B0387888
B0387874 B0387874 Explanation: Procedure error in vertical Licensed
Explanation: Vertical LIC sent incorrect command Internal Code
values Failing Item:
Failing Item: v FI00751
v FI00751 v FI00730
v FI00730
B038788C B038788C
Explanation: Vertical LIC sent commands in wrong
order
Response: This reference code usually identifies a
(B038) Reference codes 133
B0387894 • B0387F1C
condition that is due to a timing problem that will be
B0387A90 B0387A90
recovered.
Explanation: I/O card Licensed Internal Code used
Failing Item:
incorrect value
v UJJ37
Failing Item:
v FI00751
v FI00730
v IOA
v FI00701
B0387AF0 B0387AF0
B0387894 B0387894 Explanation: I/O card Licensed Internal Code stopped
because of error
Explanation: Procedure error in vertical Licensed
Internal Code Failing Item:
v FI00730
Failing Item:
v FI00751
B0387AF4 B0387AF4
v FI00730
Explanation: I/O card Licensed Internal Code stopped
because of error
B0387898 B0387898
Failing Item:
Explanation: Vertical LIC sent commands in wrong
order v FI00751
v FI00730
Failing Item:
v FI00751
B0387F14 B0387F14
v FI00730
Explanation: Reset packet received
B03878A0 B03878A0 Failing Item:
Explanation: No incoming call available to be v UJ0E9
processed v UJ0E2
Response: This reference code usually identifies a v UJJ36
condition that is due to a timing problem that will be v UJJ35
recovered.
Failing Item: B0387F18 B0387F18
v UJJ37 Explanation: Clear packet received
v FI00730
Failing Item:
v UJ0E9
B03878A4 B03878A4
v UJJ39
Explanation: I/O card Licensed Internal Code used v UJ0E2
incorrect value
v UJJ36
Failing Item: v FI00751
v FI00751
v FI00730 B0387F1C B0387F1C
Explanation: X.25 restart packet received
B03878A6 B03878A6
Failing Item:
Explanation: Vertical LIC sent incorrect command
v UJ0E9
values
v UJJ36
Failing Item:
v FI00751
v FI00730
134 System reference codes (Bxxx)
B0387F30 • B0387FB1
B0387F30 B0387F30 B0387F40 B0387F40
Explanation: X.25 reset request packet sent Explanation: Time-out on reset packet
Failing Item: Failing Item:
v UJJ36 v UJ0E9
v UJ0E9 v UJJ36
B0387F34 B0387F34 B0387F44 B0387F44
Explanation: X.25 clear request packet sent Explanation: Time-out on call packet
Failing Item: Failing Item:
v UJJ36 v UJ0E9
v UJ0E9 v UJJ36
B0387F35 B0387F35 B0387F48 B0387F48
Explanation: X.25 clear packet sent, packet size Explanation: Time-out on clear packet
negotiation failed
Failing Item:
Failing Item: v UJ0E9
v UJ0E9 v UJJ36
v UJJ35
B0387F80 B0387F80
B0387F36 B0387F36
Explanation: Packet network used wrong procedures
Explanation: X.25 clear packet sent, window size
Failing Item:
negotiation failed
v UJ0E9
Failing Item:
v UJA36
v UJ0E9
v UJJ35
B0387FA8 B0387FA8
Explanation: Received packet to help diagnosis
B0387F38 B0387F38
Failing Item:
Explanation: X.25 restart request packet sent
v UJ0E9
Failing Item:
v FI00730
v UJ0E9
v UJJ36
B0387FB0 B0387FB0
Explanation: Restart packet sent; error limit per 256
B0387F3A B0387F3A
reached
Explanation: X.32 restart negotiation failed
Failing Item:
Failing Item: v UJ0E9
v UJ0E9
v UJJ39 B0387FB1 B0387FB1
Explanation: Reset packet received; error limit per 256
B0387F3C B0387F3C reached
Explanation: Time-out on restart packet Failing Item:
Failing Item: v UJ0E9
v UJ0E9 v UJ0E2
v UJJ36
v UJJ35
(B038) Reference codes 135
136 System reference codes (Bxxx)
(B040) Reference codes
Explanation: Incorrect command value sent by vertical
B040501C B040501C
lic int code
Explanation: Command value error in I/O card
Failing Item:
Licensed Internal Code
v AJDG301
Failing Item:
v UJA34
v FI00730
B04050E6 B04050E6
B040501E B040501E
Explanation: Incorrect command value sent by vertical
Explanation: Command value error in I/O card lic int code
Licensed Internal Code
Failing Item:
Failing Item:
v AJDG301
v FI00730
v UJA34
v FI00730
B04050E0 B04050E0
Explanation: Wrong or no external communications B04050E7 B04050E7
cable installed
Explanation: Incorrect command value sent by vertical
Failing Item: lic int code
v UJA34
Failing Item:
v FI00701
v AJDG301
v IOA
v UJA34
v FI00730
B04050E1 B04050E1
Explanation: Communications line already in use B04050E8 B04050E8
Failing Item: Explanation: Wrong command value sent by IBM i
v AJDG301 Operating System licensed program
v UJA34 Failing Item:
v AJDG301
B04050E3 B04050E3
Explanation: Wrong command value sent by IBM i B04050E9 B04050E9
Operating System licensed program
Explanation: Incorrect command value sent by vertical
Failing Item: lic int code
v AJDG301 Failing Item:
v UJA34 v AJDG301
v UJA34
B04050E4 B04050E4
Explanation: Wrong command value sent by IBM i B04050EB B04050EB
Operating System licensed program
Explanation: Incorrect command value sent by vertical
Failing Item: lic int code
v AJDG301 Failing Item:
v UJA34 v AJDG301
v UJA34
B04050E5 B04050E5
B04050EC B04050EC
© Copyright IBM Corp. 2010, 2013 137
B04050ED • B04052E8
Explanation: Wrong command value sent by IBM i v FI00730
Operating System licensed program
Failing Item: B04052E0 B04052E0
v AJDG301 Explanation: Incorrect command used by I/O card
Licensed Internal Code
B04050ED B04050ED Failing Item:
Explanation: Wrong command value sent by IBM i v FI00730
Operating System licensed program
Failing Item: B04052E1 B04052E1
v AJDG301 Explanation: Wrong procedure used in I/O card
Licensed Internal Code
B04050EE B04050EE Failing Item:
Explanation: Incorrect command value sent by vertical v FI00730
lic int code
Failing Item: B04052E2 B04052E2
v AJDG301 Explanation: I/O card Licensed Internal Code
resource not available
B04050F1 B04050F1 Failing Item:
Explanation: Communications line not installed v UJA33
Failing Item: v UJA34
v AJDG301
v UJA34 B04052E4 B04052E4
v IOA Explanation: Wrong command value sent by IBM i
Operating System licensed program
B04050F5 B04050F5 Failing Item:
Explanation: Network uncontrolled-not-ready v AJDG301
warning; information only v UJA34
Failing Item:
v UJA34 B04052E7 B04052E7
Explanation: X.21 network not in the ready or
B04050F6 B04050F6 receive-data state
Explanation: Network controlled-not-ready warning; Failing Item:
information only v FI00704
Failing Item: v UJ0E3
v UJA34 v FI00701
v IOA
B04050F8 B04050F8
B04052E8 B04052E8
Explanation: Adapter card transmit error
Explanation: Command value error in I/O card
Failing Item:
Licensed Internal Code
v IOA
Failing Item:
v FI00704
v FI00730
B0405203 B0405203
Explanation: I/O card Licensed Internal Code
resource not available
Failing Item:
138 System reference codes (Bxxx)
B04052E9 • B040A001
B04052E9 B04052E9 B04056E9 B04056E9
Explanation: Command value error in I/O card Explanation: Clear-to-send signal failed to drop on
Licensed Internal Code modem interface
Failing Item: Failing Item:
v FI00730 v FI00704
v FI00701
B04052EA B04052EA v IOA
Explanation: I/O card Licensed Internal Code error
B04056EA B04056EA
Failing Item:
v FI00730 Explanation: Clear-to-send signal dropped on modem
interface
B0405301 B0405301 Failing Item:
v UJ0E3
Explanation: Adapter card receive error
v FI00704
Failing Item:
v UJA34
v FI00730
v IOA
v IOA
v FI00701
B0405302 B0405302
B04056ED B04056ED
Explanation: Adapter card transmit error
Explanation: Data-set-ready turn-on time-out on
Failing Item: modem interface
v FI00730 Failing Item:
v IOA v FI00701
v FI00704
B0405401 B0405401 v IOA
Explanation: Communications adapter card interrupt v AJDG301
not expected
Failing Item: B04056F1 B04056F1
v FI00730 Explanation: Data-set-ready dropped on modem
v IOA interface
Failing Item:
B04054E1 B04054E1 v FI00704
Explanation: Communications line not operational v FI00701
Failing Item: v UJ0E3
v IOA v IOA
v UJA34
B040A000 B040A000
B04056E8 B04056E8 Explanation: Input value error in communications IOP
LIC
Explanation: Clear-to-send not active on modem
interface Failing Item:
Failing Item: v FI00730
v UJ0E3
v UJA34 B040A001 B040A001
v FI00704 Explanation: Input value error in communications IOP
v FI00701 LIC
v IOA Failing Item:
(B040) Reference codes 139
B040A002 • B040A210
v FI00730
B040A02D B040A02D
v AJDG301
Explanation: Input value error in communications IOP
LIC
B040A002 B040A002
Failing Item:
Explanation: Input value error in communications IOP
v AJDG301
LIC
v FI00730
Failing Item:
v FI00730
B040A201 B040A201
Explanation: Frame Relay IOP storage not available
B040A003 B040A003
Failing Item:
Explanation: Input value error in communications IOP
LIC v FI00730
Failing Item:
B040A204 B040A204
v AJDG301
Explanation: Input value error in communications IOP
LIC
B040A00E B040A00E
Failing Item:
Explanation: Procedure error in Vertical LIC
v AJDG301
Failing Item:
v AJDG301
B040A205 B040A205
Explanation: Communications IOP LIC unexpected
B040A016 B040A016
reponse
Explanation: Input value error in communications IOP
Failing Item:
LIC
v AJDG301
Failing Item:
v AJDG301
B040A209 B040A209
v FI00730
Explanation: Input value error in communications IOP
LIC
B040A01B B040A01B
Failing Item:
Explanation: Input value error in communications IOP
v AJDG301
LIC
Failing Item:
B040A20A B040A20A
v AJDG301
Explanation: Input value error in communications IOP
LIC
B040A01C B040A01C
Failing Item:
Explanation: Input value error in communications IOP
v AJDG301
LIC
Failing Item:
B040A20B B040A20B
v AJDG301
Explanation: Input value error in communications IOP
LIC
B040A01D B040A01D
Failing Item:
Explanation: Input value error in communications IOP
v AJDG301
LIC
Failing Item:
B040A210 B040A210
v AJDG301
Explanation: Communication adapter card error
Failing Item:
v FI00701
140 System reference codes (Bxxx)
B040A213 • B040FFFF
v IOA
B040FFFF B040FFFF
Explanation: User perceived problem
B040A213 B040A213
Failing Item:
Explanation: Severe error detected by communications
IOP LIC v USER
Failing Item:
v FI00730
B040A800 B040A800
Explanation: Network not responding.
Failing Item:
v UJ0E3
v FI00730
B040A801 B040A801
Explanation: Too many frames with bad receive
sequence counts
Failing Item:
v UJ0E3
v FI00730
B040A807 B040A807
Explanation: Network not responding.
Failing Item:
v UJ0E3
B040AB00 B040AB00
Explanation: Incorrect config data for Frame Relay
LIC
Failing Item:
v AJDG301
B040AB01 B040AB01
Explanation: Incorrect config data for Frame Relay
LIC
Failing Item:
v AJDG301
B040AB02 B040AB02
Explanation: Incorrect config data for Frame Relay
LIC
Failing Item:
v AJDG301
(B040) Reference codes 141
142 System reference codes (Bxxx)
(B057) Reference codes
B0570010 B0570010
Explanation: iSCSI initiator requested unknown
storage target node
Failing Item:
v AJDG301
B0570011 B0570011
Explanation: iSCSI Login failure
B0570012 B0570012
Explanation: iSCSI Login failure
B0570013 B0570013
Explanation: iSCSI Login failure
B0570014 B0570014
Explanation: iSCSI Login failure
B0570015 B0570015
Explanation: iSCSI Login failure
B0570016 B0570016
Explanation: iSCSI Login failure
B0570020 B0570020
Explanation: CHAP authentication failure
B0571040 B0571040
Explanation: iSCSI Login failure
Failing Item:
v HBATARG
v HBAINIT
v ROUTER
B0571041 B0571041
Explanation: iSCSI Login failure
Failing Item:
v HBATARG
v HBAINIT
© Copyright IBM Corp. 2010, 2013 143
144 System reference codes (Bxxx)
(B070) Reference codes
Response: Is the problem intermittent?
B0700000 B0700000
Yes: Perform the following procedures:
Explanation: Device no response time-out; temporary
error 1. INTIP05
2. INTIP14
Failing Item:
v FI00601 No: Perform TWSIP01.
v FI00602
Failing Item:
v FI00610
v FI00602
v FI00601
B0700001 B0700001
v UY1Z1
Explanation: WS IOP detected error when v FI00610
transmitting data
Response: Is the problem intermittent? B0700005 B0700005
Yes: Perform the following procedures: Explanation: WS IOP detected error when
1. INTIP05 transmitting data
2. INTIP14 Response: Is the problem intermittent?
No: Perform TWSIP01. Yes: Perform the following procedures:
1. INTIP05
Failing Item:
2. INTIP14
v FI00602
v FI00601 No: Perform TWSIP01.
v UY1Z1
Failing Item:
v UY1Z3
v FI00602
v FI00610
v FI00601
v FI00615
v UY1Z3
v FI00610
B0700003 B0700003
v FI00615
Explanation: WS IOP detected parity error from
device
B0700006 B0700006
Response: Is the problem intermittent?
Explanation: WS IOP detected wrong data from
Yes: Perform the following procedures: device
1. INTIP05 Response: Is the problem intermittent?
2. INTIP14
Yes: Perform the following procedures:
No: Perform TWSIP01. 1. INTIP05
2. INTIP14
Failing Item:
v FI00602 No: Perform TWSIP01.
v FI00601
Failing Item:
v UY1Z1
v FI00601
v FI00610
v FI00602
v UY1Z3
B0700004 B0700004
v FI00610
Explanation: Device detected parity error from WS
IOP
© Copyright IBM Corp. 2010, 2013 145
B0700007 • B0700025
B0700007 B0700007 B0700021 B0700021
Explanation: WS IOP detected wrong address from Explanation: Device detected not valid value from WS
device IOP
Response: Is the problem intermittent? Response:
Yes: Perform the following procedures: Failing Item:
1. INTIP05 v TWSIP01
2. INTIP14 v FI00601
v AJLYD01
No: Perform TWSIP01.
v FI00610
Failing Item:
v FI00601 B0700022 B0700022
v UY1Z3
Explanation: Device detected storage or data overrun
v UY1Z1
Response:
v FI00610
Failing Item:
B0700008 B0700008 v TWSIP01
v FI00601
Explanation: WS IOP detected device power turned
off, and then on v AJLYD01
v FI00610
Response:
Failing Item:
B0700023 B0700023
v TWSIP01
Explanation: Device detected null or attribute
v UY1Z5
exception error
v FI00601
Response:
B0700009 B0700009 Failing Item:
v TWSIP01
Explanation: WS IOP detected wrong device response
to start command v FI00601
v FI00610
Response:
Failing Item:
B0700024 B0700024
v TWSIP01
Explanation: Device detected wrong start command
v FI00601
from WS IOP
v FI00610
Response:
B0700020 B0700020 Failing Item:
v TWSIP01
Explanation: Device detected wrong command or
device ID from WS IOP v FI00601
v AJLYD01
Response:
v FI00610
Failing Item:
v TWSIP01
B0700025 B0700025
v FI00601
Explanation: WS IOP detected wrong exception
v AJLYD01
response from device
v FI00610
Response:
Failing Item:
v TWSIP01
v FI00601
146 System reference codes (Bxxx)
B0700026 • B0700104
v FI00610
B0700100 B0700100
Explanation: Device no response time-out; temporary
B0700026 B0700026
error
Explanation: WS IOP detected not valid pass-through
Failing Item:
command
v FI00601
Response:
v FI00602
Failing Item: v FI00610
v TWSIP01
v UY1Z4 B0700101 B0700101
v FI00610
Explanation: WS IOP detected error when
transmitting data
B0700049 B0700049
Response: Is the problem intermittent?
Explanation: WS IOP detected wrong request or
Yes: Perform the following procedures:
response from device
1. INTIP05
Response:
2. INTIP14
Failing Item:
v TWSIP01 No: Perform TWSIP01.
v FI00601 Failing Item:
v FI00610 v FI00602
v FI00601
B0700082 B0700082 v UY1Z1
Explanation: WS IOP detected wrong device type v UY1Z3
from device v FI00610
Response: v FI00615
Failing Item:
B0700103 B0700103
v TWSIP01
v FI00601 Explanation: WS IOP detected parity error from
device
B0700090 B0700090 Response: Is the problem intermittent?
Explanation: WS IOP detected no status change from Yes: Perform the following procedures:
device 1. INTIP05
Response: 2. INTIP14
Failing Item: No: Perform TWSIP01.
v TWSIP01
Failing Item:
v FI00601
v FI00602
v FI00610
v FI00601
v UY1Z1
B0700091 B0700091
v FI00610
Explanation: WS IOP detected busy time-out from
device
B0700104 B0700104
Response:
Explanation: Device detected parity error from WS
Failing Item: IOP
v TWSIP01 Response: Is the problem intermittent?
v FI00601
Yes: Perform the following procedures:
v FI00610
1. INTIP05
2. INTIP14
(B070) Reference codes 147
B0700105 • B0700120
No: Perform TWSIP01. Failing Item:
Failing Item: v FI00601
v FI00602 v UY1Z3
v FI00601 v UY1Z1
v UY1Z1 v FI00610
v FI00610
B0700108 B0700108
B0700105 B0700105 Explanation: WS IOP detected device power turned
off, and then on
Explanation: WS IOP detected error when
transmitting data Response:
Response: Is the problem intermittent? Failing Item:
Yes: Perform the following procedures: v TWSIP01
1. INTIP05 v UY1Z5
2. INTIP14 v FI00601
No: Perform TWSIP01. B0700109 B0700109
Failing Item: Explanation: WS IOP detected wrong device response
v FI00602 to start command
v FI00601 Response:
v UY1Z3
Failing Item:
v FI00610
v TWSIP01
v FI00615
v FI00601
v FI00610
B0700106 B0700106
Explanation: WS IOP detected wrong data from B0700111 B0700111
device
Explanation: WS IOP detected wrong keyboard scan
Response: Is the problem intermittent? code from display
Yes: Perform the following procedures: Response:
1. INTIP05
Failing Item:
2. INTIP14
v TWSIP01
No: Perform TWSIP01. v FI00601
v AJLYD01
Failing Item:
v FI00610
v FI00601
v FI00602
B0700120 B0700120
v UY1Z3
v FI00610 Explanation: Device detected wrong command or
device ID from WS IOP
B0700107 B0700107 Response:
Explanation: WS IOP detected wrong address from Failing Item:
device v TWSIP01
Response: Is the problem intermittent? v FI00601
v AJLYD01
Yes: Perform the following procedures:
v FI00610
1. INTIP05
2. INTIP14
No: Perform TWSIP01.
148 System reference codes (Bxxx)
B0700121 • B0700173
v FI00610
B0700121 B0700121
Explanation: Device detected not valid value from WS
B0700126 B0700126
IOP
Explanation: WS IOP detected not valid pass-through
Response:
command
Failing Item:
Response:
v TWSIP01
Failing Item:
v FI00601
v TWSIP01
v AJLYD01
v UY1Z4
v FI00610
v FI00610
B0700122 B0700122
B0700149 B0700149
Explanation: Device detected storage or data overrun
Explanation: WS IOP detected wrong request or
Response: response from device
Failing Item: Response:
v TWSIP01
Failing Item:
v FI00601
v TWSIP01
v AJLYD01
v FI00601
v FI00610
v FI00610
B0700123 B0700123
B0700170 B0700170
Explanation: Device detected null or attribute
Explanation: WS IOP detected error downloading
exception error
printer definition table
Response:
Failing Item:
Failing Item: v AJDG301
v TWSIP01 v FI00601
v FI00601
v FI00610 B0700171 B0700171
Explanation: WS IOP detected error downloading
B0700124 B0700124 printer definition table
Explanation: Device detected wrong start command Failing Item:
from WS IOP
v FI00601
Response: v AJLYD01
Failing Item:
v TWSIP01 B0700172 B0700172
v FI00601 Explanation: WS IOP detected error downloading
v AJLYD01 printer definition table
v FI00610 Failing Item:
v UX201
B0700125 B0700125 v AJDG301
Explanation: WS IOP detected wrong exception v FI00601
response from device
Response: B0700173 B0700173
Failing Item: Explanation: WS IOP detected error downloading
v TWSIP01 printer definition table
v FI00601 Failing Item:
(B070) Reference codes 149
B0700174 • B0700190
v UX201 v TWSIP01
v FI00601 v FI00601
B0700174 B0700174 B0700183 B0700183
Explanation: WS IOP detected error unloading printer Explanation: WS IOP detected wrong display size
definition table value
Failing Item: Response:
v FI00601 Failing Item:
v AJLYD01 v TWSIP01
v FI00601
B0700175 B0700175
Explanation: WS IOP detected device configuration B0700184 B0700184
error
Explanation: WS IOP detected wrong keyboard
Failing Item: identification
v FI00601 Response: Verify that the correct keyboard is attached
v AJLYD01 correctly to the workstation.
If the correct keyboard is attached correctly to the
B0700176 B0700176 workstation, perform the procedure indicated in the
failing item list.
Explanation: WS IOP detected error downloading LIC
to device Failing Item:
Failing Item: v TWSIP01
v UX202 v FI00601
v FI00601
B0700189 B0700189
B0700177 B0700177 Explanation: Wrong magnetic stripe reader or light
pen status
Explanation: WS IOP detected error downloading LIC
to device Response:
Failing Item: Failing Item:
v UX202 v TWSIP01
v FI00601 v FI00601
v FI00605
B0700181 B0700181 v FI00607
Explanation: Wrong magnetic stripe reader response v FI00610
Response:
B0700190 B0700190
Failing Item:
Explanation: WS IOP detected no status change from
v TWSIP01
device
v FI00605
Response: Is the problem intermittent?
v MEDIA
v FI00601 Yes: Perform the following procedures:
v FI00610 1. INTIP05
2. INTIP14
B0700182 B0700182
No: Perform TWSIP01.
Explanation: WS IOP detected wrong device type
Failing Item:
from device
v FI00601
Response:
v FI00610
Failing Item: v UY1Z1
150 System reference codes (Bxxx)
B0700191 • B0700206
v FI00610
B0700191 B0700191
Explanation: WS IOP detected busy time-out from
B0700204 B0700204
device
Explanation: Device detected parity error from WS
Response:
IOP
Failing Item:
Response: Is the problem intermittent?
v TWSIP01
Yes: Perform the following procedures:
v FI00601
1. INTIP05
v FI00610
2. INTIP14
B0700200 B0700200 No: Perform TWSIP01.
Explanation: Device no response time-out; temporary Failing Item:
error
v FI00602
Failing Item: v FI00604
v FI00604 v UY1Z1
v FI00602 v FI00610
v FI00610
B0700205 B0700205
B0700201 B0700201
Explanation: WS IOP detected error when
Explanation: WS IOP detected error when transmitting data
transmitting data
Response: Is the problem intermittent?
Response: Is the problem intermittent?
Yes: Perform the following procedures:
Yes: Perform the following procedures: 1. INTIP05
1. INTIP05 2. INTIP14
2. INTIP14
No: Perform TWSIP01.
No: Perform TWSIP01.
Failing Item:
Failing Item: v FI00602
v FI00602 v FI00604
v FI00604 v UY1Z1
v UY1Z1 v FI00610
v UY1Z3 v FI00615
v FI00610
v FI00615 B0700206 B0700206
Explanation: WS IOP detected wrong data from
B0700203 B0700203 device
Explanation: WS IOP detected parity error from Response: Is the problem intermittent?
device
Yes: Perform the following procedures:
Response: Is the problem intermittent?
1. INTIP05
Yes: Perform the following procedures: 2. INTIP14
1. INTIP05
2. INTIP14 No: Perform TWSIP01.
Failing Item:
No: Perform TWSIP01.
v FI00604
Failing Item: v FI00602
v FI00602 v UY1Z3
v FI00604 v FI00610
v UY1Z1
(B070) Reference codes 151
B0700207 • B0700225
B0700207 B0700207 B0700220 B0700220
Explanation: WS IOP detected wrong address from Explanation: Device detected wrong command or
device device ID from WS IOP
Response: Is the problem intermittent? Failing Item:
Yes: Perform the following procedures: v FI00604
1. INTIP05 v AJLYD01
2. INTIP14 v FI00610
No: Perform TWSIP01. B0700221 B0700221
Failing Item: Explanation: Device detected not valid value from WS
v FI00604 IOP
v UY1Z3 Failing Item:
v UY1Z1 v FI00604
v FI00610 v AJLYD01
v FI00610
B0700208 B0700208
Explanation: WS IOP detected device power turned B0700222 B0700222
off, and then on
Explanation: Device detected storage or data overrun
Failing Item:
Failing Item:
v UY1Z5
v FI00604
v FI00604
v AJLYD01
v FI00610
B0700209 B0700209
Explanation: WS IOP detected wrong device response B0700223 B0700223
to start command
Explanation: WS IOP detected start command to
Failing Item: printer was lost
v FI00604
Failing Item:
v FI00610
v FI00604
v FI00602
B0700210 B0700210
v FI00610
Explanation: Printer detected equipment error
Failing Item: B0700224 B0700224
v FI00604 Explanation: Device detected wrong start command
from WS IOP
B0700211 B0700211 Failing Item:
Explanation: Printer detected equipment error v FI00604
Failing Item: v AJLYD01
v FI00604 v FI00610
v AJLYD01
v FI00610 B0700225 B0700225
Explanation: WS IOP detected wrong exception
B0700212 B0700212 response from device
Explanation: Printer detected equipment error Failing Item:
v FI00604
Failing Item:
v FI00610
v FI00604
152 System reference codes (Bxxx)
B0700226 • B0700246
B0700226 B0700226 B0700238 B0700238
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
B0700230 B0700230 B0700239 B0700239
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
B0700231 B0700231 B0700240 B0700240
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
B0700232 B0700232 B0700241 B0700241
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
B0700233 B0700233 B0700242 B0700242
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
B0700234 B0700234 B0700243 B0700243
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
B0700235 B0700235 B0700244 B0700244
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
B0700236 B0700236 B0700245 B0700245
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
B0700237 B0700237 B0700246 B0700246
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Failing Item: Failing Item:
v FI00604 v FI00604
(B070) Reference codes 153
B0700247 • B07002A4
B0700247 B0700247 B0700291 B0700291
Explanation: Printer detected equipment error Explanation: WS IOP detected busy time-out from
device
Failing Item:
v FI00604 Failing Item:
v FI00604
B0700248 B0700248 v FI00610
Explanation: Printer detected equipment error
B07002A0 B07002A0
Failing Item:
Explanation: Printer detected equipment error
v FI00604
Response: Consult the printer's manual for additional
information.
B0700249 B0700249
Failing Item:
Explanation: WS IOP detected wrong request or
response from device v FI00604
Failing Item:
B07002A1 B07002A1
v FI00604
v FI00610 Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional
B070026X B070026X information.
Explanation: Printer detected equipment error Failing Item:
v FI00604
Response: See printer documentation for more
information.
B07002A2 B07002A2
Failing Item:
v FI00604 Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional
B070027X B070027X information.
Explanation: Printer detected equipment error Failing Item:
v FI00604
Response: See printer documentation for more
information.
B07002A3 B07002A3
Failing Item:
v FI00604 Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional
B070028X B070028X information.
Explanation: Printer detected equipment error Failing Item:
v FI00604
Response: See printer documentation for more
information.
B07002A4 B07002A4
Failing Item:
v FI00604 Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional
B0700290 B0700290 information.
Explanation: WS IOP detected no status change from Failing Item:
device v FI00604
Failing Item:
v FI00604
v FI00610
154 System reference codes (Bxxx)
B07002A5 • B07002FF
B07002A5 B07002A5 B07002AB B07002AB
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional Response: Consult the printer's manual for additional
information. information.
Failing Item: Failing Item:
v FI00604 v FI00604
B07002A6 B07002A6 B07002AC B07002AC
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional Response: Consult the printer's manual for additional
information. information.
Failing Item: Failing Item:
v FI00604 v FI00604
B07002A7 B07002A7 B07002AD B07002AD
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional Response: Consult the printer's manual for additional
information. information.
Failing Item: Failing Item:
v FI00604 v FI00604
B07002A8 B07002A8 B07002AE B07002AE
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional Response: Consult the printer's manual for additional
information. information.
Failing Item: Failing Item:
v FI00604 v FI00604
B07002A9 B07002A9 B07002AF B07002AF
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional Response: Consult the printer's manual for additional
information. information.
Failing Item: Failing Item:
v FI00604 v FI00604
B07002AA B07002AA B07002FF B07002FF
Explanation: Printer detected equipment error Explanation: Printer detected equipment error
Response: Consult the printer's manual for additional Response: Consult the printer's manual for additional
information. information.
Failing Item: Failing Item:
v FI00604 v FI00604
(B070) Reference codes 155
B070A000 • B070F000
B070A000 B070A000 B070D021 B070D021
Explanation: Too many devices active on the Explanation: WS IOP detected errors on all cables
workstation IOP
Failing Item:
Response: This error occurs if you attempted to v FI00602
activate more workstations than allowed.
v FI00601
Switch off power to (or remove) one or more of the v FI00610
display stations (except for the console) that are
v FI00615
attached to this workstation I/O processor. Perform an
initial program load (IPL) from the control panel to
correct the problem. B070D022 B070D022
Refer to the local workstation diagrams for the location Explanation: WS IOP parity errors detected on all
of workstations if necessary. cables
Failing Item: Failing Item:
v UY1Z2 v FI00602
v FI00601
B070B000 B070B000 v FI00610
Explanation: WS IOP fails to report part, model and v FI00615
serial number
Response: B070D023 B070D023
Failing Item: Explanation: WS IOP detected errors on some, but not
all cables
v TWSIP01
v FI00610 Response:
Failing Item:
B070C000 B070C000 v TWSIP01
Explanation: WS IOP error not known v FI00602
v FI00601
Failing Item:
v FI00610
v AJLYD01
v FI00610
B070E000 B070E000
B070D000 B070D000 Explanation: WS IOP or IOA error during working
operation
Explanation: Work Station IOA start-up test error
Failing Item:
Failing Item:
v AJLYD01
v FI00610
v FI00610
B070D010 B070D010
B070F000 B070F000
Explanation: WS IOP storage failure corrected
Explanation: WS IOP or IOA operating system
Response: program error
Failing Item: Failing Item:
v TWSIP01 v AJLYD01
v FI00610 v FI00719
B070D011 B070D011
Explanation: WS IOP card storage failure
Failing Item:
v FI00610
156 System reference codes (Bxxx)
(B075) Reference codes
v FI00730
B0750101 B0750101
Explanation: WS IOP detected error when
B0750106 B0750106
transmitting data
Explanation: WS IOP detected wrong data from
Response:
device
Failing Item:
Response:
v WSCIP01
Failing Item:
v FI00601
v WSCIP01
v UY1Z1
v FI00601
v FI00631
v FI00631
v FI00730
v UY1Z1
v FI00730
B0750103 B0750103
Explanation: WS IOP detected parity error from
B0750107 B0750107
device
Explanation: WS IOP detected wrong address from
Response:
device
Failing Item:
Response:
v WSCIP01
Failing Item:
v FI00601
v WSCIP01
v UY1Z1
v FI00601
v FI00631
v UY1Z1
v FI00730
v FI00730
B0750104 B0750104
B0750108 B0750108
Explanation: Device detected parity error from WS
IOP Explanation: WS IOP detected device power turned
off, and then on
Response:
Response:
Failing Item:
Failing Item:
v WSCIP01
v WSCIP01
v FI00601
v UY1Z5
v UY1Z1
v FI00601
v FI00631
v FI00730
B0750109 B0750109
B0750105 B0750105 Explanation: WS IOP detected wrong device response
to start command
Explanation: WS IOP detected error when
transmitting data Response:
Response: Failing Item:
v WSCIP01
Failing Item:
v FI00601
v WSCIP01
v FI00615
v FI00601
v UY1Z1
B0750111 B0750111
v FI00631
© Copyright IBM Corp. 2010, 2013 157
B0750120 • B0750190
Explanation: WS IOP detected wrong keyboard scan
B0750124 B0750124
code from display
Explanation: Device detected wrong start command
Response:
from WS IOP
Failing Item:
Response:
v WSCIP01
Failing Item:
v FI00601
v WSCIP01
v FI00730
v FI00601
v FI00730
B0750120 B0750120
Explanation: Device detected wrong command or
B0750125 B0750125
device ID from WS IOP
Explanation: WS IOP detected wrong exception
Response:
response from device
Failing Item:
Response:
v WSCIP01
Failing Item:
v FI00601
v WSCIP01
v FI00730
v FI00601
v FI00730
B0750121 B0750121
Explanation: Device detected not valid value from WS
B0750126 B0750126
IOP
Explanation: WS IOP detected not valid pass-through
Response:
command
Failing Item:
Response:
v WSCIP01
Failing Item:
v FI00601
v WSCIP01
v FI00730
v UY1Z4
v FI00730
B0750122 B0750122
Explanation: Device detected storage or data overrun
B0750149 B0750149
Response:
Explanation: WS IOP detected wrong request or read
Failing Item: response from device
v WSCIP01 Response:
v FI00601
Failing Item:
v FI00730
v WSCIP01
v FI00601
B0750123 B0750123
v FI00730
Explanation: Device detected null or attribute
exception error
B0750190 B0750190
Response:
Explanation: WS IOP detected no status change from
Failing Item: device
v WSCIP01 Response:
v FI00601
Failing Item:
v FI00730
v WSCIP01
v FI00601
v UY1Z1
v FI00730
158 System reference codes (Bxxx)
B0750191 • B0750211
Failing Item:
B0750191 B0750191
v WSCIP01
Explanation: WS IOP detected busy time-out from
v FI00604
device
v UY1Z1
Response:
v FI00631
Failing Item: v FI00730
v WSCIP01
v FI00601 B0750206 B0750206
v FI00730
Explanation: WS IOP detected wrong data from
device
B0750201 B0750201
Response:
Explanation: WS IOP detected error when
Failing Item:
transmitting data
v WSCIP01
Response:
v FI00604
Failing Item: v FI00631
v WSCIP01 v FI00730
v FI00604
v UY1Z1 B0750207 B0750207
v FI00631
Explanation: WS IOP detected wrong address from
v FI00730 device
Response:
B0750203 B0750203
Failing Item:
Explanation: WS IOP detected parity error from
v WSCIP01
device
v FI00604
Response:
v UY1Z1
Failing Item: v FI00730
v WSCIP01
v FI00604 B0750208 B0750208
v UY1Z1
Explanation: WS IOP detected device power turned
v FI00631 off, and then on
v FI00730
Failing Item:
v UY1Z5
B0750204 B0750204
v FI00604
Explanation: Device detected parity error from WS
IOP
B0750209 B0750209
Response:
Explanation: WS IOP detected wrong device response
Failing Item: to start command
v WSCIP01 Failing Item:
v FI00604 v FI00604
v UY1Z1 v FI00730
v FI00631
v FI00730 B0750211 B0750211
Explanation: Printer detected equipment error
B0750205 B0750205
Failing Item:
Explanation: WS IOP detected error when
v FI00604
transmitting data
v FI00730
Response:
(B075) Reference codes 159
B0750221 • B0755022
B0750221 B0750221 B0755002 B0755002
Explanation: Device detected not valid value from WS Explanation: Procedure error in vertical Licensed
IOP Internal Code
Failing Item: Response: Procedure error in machine instructions
v FI00604 Failing Item:
v FI00730 v UJE34
v AJDG301
B0750224 B0750224
Explanation: Device detected wrong start command B0755006 B0755006
from WS IOP
Explanation: Procedure error in vertical Licensed
Failing Item: Internal Code
v FI00604 Failing Item:
v FI00730 v AJDG301
B0750225 B0750225 B0755007 B0755007
Explanation: WS IOP detected wrong exception Explanation: Procedure error in vertical Licensed
response from device Internal Code
Failing Item: Failing Item:
v FI00604 v AJDG301
v FI00730 v UJA34
B0750290 B0750290 B0755009 B0755009
Explanation: WS IOP detected no status change from Explanation: Incorrect command value sent by vertical
device LIC
Failing Item: Failing Item:
v FI00604 v AJDG301
v FI00730
B075500A B075500A
B0750291 B0750291
Explanation: Procedure error in vertical Licensed
Explanation: WS IOP detected busy time-out from Internal Code
device
Failing Item:
Failing Item: v AJDG301
v FI00604
v FI00730 B075500D B075500D
Explanation: Incorrect command value sent by vertical
B0755000 B0755000 LIC
Explanation: Wrong command sent by vertical Failing Item:
Licensed Internal Code
v AJDG301
Failing Item: v UJA34
v AJDG301
B0755022 B0755022
B0755001 B0755001
Explanation: Procedure error in vertical Licensed
Explanation: Procedure error in vertical Licensed Internal Code
Internal Code
Failing Item:
Failing Item: v AJDG301
v AJDG301
160 System reference codes (Bxxx)
B0755206 • B0755719
B0755206 B0755206 B0755712 B0755712
Explanation: Communications controller storage not Explanation: No data received from remote
available equipment; time-out
Failing Item: Failing Item:
v UJA33 v UJA34
v AJLAG01
B07556EA B07556EA v UJ0E3
Explanation: Clear-to-send signal dropped on modem v FI00704
interface v FI00705
Failing Item: v FI00700
v UJ0E3 v UJA35
v FI00704 v FI00701
v UJA34 v FI00719
v FI00719
v FI00701 B0755715 B0755715
Explanation: Remote equipment did not respond
B07556ED B07556ED causing an idle-time-out
Explanation: Data-set-ready turn-on time-out on Failing Item:
modem interface v UJA34
Failing Item: v UJ0E3
v FI00701 v FI00701
v FI00704 v FI00704
v FI00719 v FI00705
v AJLAG01 v FI00700
v FI00719
B07556F1 B07556F1
B0755718 B0755718
Explanation: Data-set-ready dropped on modem
interface Explanation: Retry limit reached for sending frames to
remote equipment
Failing Item:
v FI00704 Failing Item:
v FI00701 v UJ0E3
v UJ0E3 v FI00705
v FI00719 v FI00704
v FI00700
B0755710 B0755710 v UJA34
v FI00719
Explanation: Nonproductive receive time-out while
receiving from remote v FI00701
Failing Item:
B0755719 B0755719
v UJA34
v FI00700 Explanation: Retry limit reached for sending frames to
remote equipment
v FI00705
v FI00704 Failing Item:
v UJ0E3 v FI00700
v FI00701
v FI00719
(B075) Reference codes 161
B0755720 • B075FFFF
B0755720 B0755720 B075D000 B075D000
Explanation: Retry limit reached for sending poll Explanation: Workstation IOP error not known
frame to remote
Failing Item:
Failing Item: v AJLAG01
v FI00700
v UJA34 B075D001 B075D001
Explanation: Wrong or no external communications
B0755721 B0755721 cable installed
Explanation: Could not send frame to remote Failing Item:
equipment; local problem
v FI00631
Failing Item: v AJLAG01
v FI00704
v UJA34 B075F003 B075F003
v FI00701
Explanation: WS IOA buffer utilization threshold
v FI00719 exceeded temporarily
v FI00730
Failing Item:
v AJLAG01
B0755722 B0755722
Explanation: Wrong command value sent by IBM i B075FFFF B075FFFF
Operating System licensed program
Explanation: User suspected problem
Failing Item:
Response: Reference code FFFF is assigned by the
v AJLAG01
ANZPRB (Analyze Problems) for user-detected errors.
v UJA35 Run ANZPRB again if the problem still exists or look in
the problem log (WRKPRB) for possible failing FRUs.
B075A000 B075A000 Failing Item:
Explanation: Too many devices active on the v USER
workstation IOP
Failing Item:
v UY1Z2
B075B000 B075B000
Explanation: WS IOP card failing to report part,
model and serial number
Response:
Failing Item:
v WSCIP01
v FI00615
B075C000 B075C000
Explanation: Workstation IOP error not known
Failing Item:
v AJLAG01
162 System reference codes (Bxxx)
(B1xx) Reference codes
A B1xx reference code indicates that an event or exception occurred in service processor firmware. To
resolve any B1xx reference code, determine if the SRC requires a service action or if it is for tracking
purposes only.
Diagnostics analyze an event when it occurs to determine if the event requires service or if the event will
only be recorded for tracking purposes and future reference. The determination is based on machine type,
model, installed features, configuration, topology and activations at the time of the event.
If you do not find the SRC in a serviceable event view then it is a tracking event only and does not
require service.
v Tracking events appear as "informational" or "Misc." or "temp" in the IBM i product activity log and the
Advanced System Manage Interface (ASMI).
v Serviceable event views are:
– AIX® Diagnostics Results Log
– IBM i problem log
– IBM i service action log (SAL)
– Management console service focal point
– Linux® Diagnostic Messages Log
– System control panel
– ASMI listed under serviceable events
Explanation: CINI has detected a plug count greater
B104B201 B104B201
than the limit for the multi-chip module
Explanation: Dynamic recalibration is not valid on
Response: If this is a tracking event, no service actions
this elastic interface bus.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B110C65C B110C65C
Explanation: The chip's scan ring did not work
B104B2CC B104B2CC
correctly.
Explanation: Internal software error: invalid
Response: If this is a tracking event, no service actions
parameter passed into a function.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B110C65F B110C65F
Explanation: An ASIC scan failed.
B110C004 B110C004
Response: If this is a tracking event, no service actions
Explanation: The first clock card is defective; all
are required. Otherwise, use the FRU and procedure
processors have clock errors.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B110D141 B110D141
actions.
Explanation: The chip attention handler was asked to
handle an invalid attention type.
B110C011 B110C011
© Copyright IBM Corp. 2010, 2013 163
B110D145 • B111C034
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1112600 B1112600
B110D145 B110D145
Explanation: The processor VPD was invalid or
Explanation: An scom attention was detected on the missing
current chip.
Response: If this is a tracking event, no service actions B1112601 B1112601
are required. Otherwise, use the FRU and procedure
Explanation: Failed to unflatten an error log.
callouts detailed with the SRC to determine service
actions.
B1112608 B1112608
B110E501 B110E501 Explanation: A critical thermal sensor detected an
over-temperature condition
Explanation: There was a hardware-detected problem
due to the processor subsystem.
B111C01F B111C01F
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: CINI has detected a JTAG failure.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B110E503 B110E503 actions.
Explanation: There was a hardware-detected thermal
failure due to the processor subsystem. B111C026 B111C026
Response: If this is a tracking event, no service actions Explanation: CINI has detected an attempt to execute
are required. Otherwise, use the FRU and procedure an unsupported operation.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B110E504 B110E504 actions.
Explanation: A hardware failure was detected in the
central electronics complex (CEC). B111C027 B111C027
Response: If this is a tracking event, no service actions Explanation: CINI has received invalid data.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B110E540 B110E540
Explanation: There was a failure most likely B111C033 B111C033
attributable to the processor subsystem, but it could
also be software-related or require further support. Explanation: CINI has detected an invalid GPTR data
version.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B110E550 B110E550
B111C034 B111C034
Explanation: There was a software problem, but this
could also be processor subsystem-related or require Explanation: CINI has detected a CFAM ID mismatch
further support. between the VPD and a chip.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
164 System reference codes (Bxxx)
B111C035 • B111C656
callouts detailed with the SRC to determine service
B111C651 B111C651
actions.
Explanation: The chip's LBIST signature did not match
expected value.
B111C035 B111C035
Response: If this is a tracking event, no service actions
Explanation: CINI has detected a mismatch between
are required. Otherwise, use the FRU and procedure
the ring length stored in VPD and the actual service
callouts detailed with the SRC to determine service
processor ring length.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B111C652 B111C652
callouts detailed with the SRC to determine service
actions. Explanation: A chip's LBIST signature did not equal
the expected value.
B111C03F B111C03F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A phase-locked loop (PLL) error
callouts detailed with the SRC to determine service
occurred.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B111C653 B111C653
callouts detailed with the SRC to determine service
actions. Explanation: A chip's signature was missing the
engineering change (EC) level.
B111C040 B111C040 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: CINI was unable to get a PLL sync after
callouts detailed with the SRC to determine service
10 attempts.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B111C654 B111C654
callouts detailed with the SRC to determine service
actions. Explanation: The chip ABIST signature didn't match
the expected signature.
B111C04F B111C04F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The version of the data in the PLL vital
callouts detailed with the SRC to determine service
product data (VPD) record is not supported.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B111C655 B111C655
callouts detailed with the SRC to determine service
actions. Explanation: A chip's HBIST result did not equal the
expected value.
B111C051 B111C051 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A clock check failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B111C656 B111C656
actions.
Explanation: There was a file error in the LBIST setup
data.
B111C052 B111C052
Response: If this is a tracking event, no service actions
Explanation: A chip data flush operation failed to
are required. Otherwise, use the FRU and procedure
complete in the allotted time.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 165
B111C657 • B111C667
callouts detailed with the SRC to determine service
B111C657 B111C657
actions.
Explanation: The L2 line delete count exceeded the
threshold.
B111C662 B111C662
Response: If this is a tracking event, no service actions
Explanation: SVPD function did not return the
are required. Otherwise, use the FRU and procedure
expected data length.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B111C658 B111C658
actions.
Explanation: The system performed a line delete. This
is an informational message; no action is required.
B111C663 B111C663
Response: None.
Explanation: The module VPD does not have the
correct version of the data structure.
B111C65C B111C65C
Response: If this is a tracking event, no service actions
Explanation: The chip's scan ring did not work are required. Otherwise, use the FRU and procedure
correctly. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B111C664 B111C664
actions.
Explanation: CFAM ID does not match the CFAM ID
in the module VPD.
B111C65E B111C65E
Response: If this is a tracking event, no service actions
Explanation: An L3 cache chip's arrays were bad. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B111C665 B111C665
Explanation: The fuse ring length does not match the
B111C65F B111C65F fuse ring length from the module VPD.
Explanation: The scan ring for a chip did not work Response: If this is a tracking event, no service actions
correctly. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B111C666 B111C666
Explanation: eCMD function fails.
B111C660 B111C660
Response: If this is a tracking event, no service actions
Explanation: The chips that were tested do not have are required. Otherwise, use the FRU and procedure
any of the good arrays required for operation. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B111C667 B111C667
actions.
Explanation: A processor chip's arrays were bad.
Response: If this is a tracking event, no service actions
B111C661 B111C661
are required. Otherwise, use the FRU and procedure
Explanation: The P6 small array signature did not callouts detailed with the SRC to determine service
equal the expected value. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
166 System reference codes (Bxxx)
B111C66F • B112B841
B111C66F B111C66F B111E550 B111E550
Explanation: A processor chip had an array that was Explanation: There was a software problem, but this
not repairable. could also be processor FRU-related or require further
support.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B111C6F0 B111C6F0
B112B2DF B112B2DF
Explanation: The processor chip test data was bad.
Explanation: A fatal IAP error occurred.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B111E501 B111E501
B112B2E0 B112B2E0
Explanation: There was a hardware-detected problem
due to the processor FRU. Explanation: An IAP error that was not fatal occurred,
or an IAP warning was issued. The system should be
Response: If this is a tracking event, no service actions
rebooted in slow mode to diagnose this potential
are required. Otherwise, use the FRU and procedure
problem.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B111E503 B111E503
actions.
Explanation: A hardware-detected thermal failure
occurred.
B112B71D B112B71D
Response: If this is a tracking event, no service actions
Explanation: The VPD cannot be updated with the
are required. Otherwise, use the FRU and procedure
new L2 line-delete information because the record is
callouts detailed with the SRC to determine service
already full.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B111E504 B111E504
callouts detailed with the SRC to determine service
Explanation: A hardware failure was detected in the actions.
central electronics complex (CEC).
Response: If this is a tracking event, no service actions B112B720 B112B720
are required. Otherwise, use the FRU and procedure
Explanation: The VPD indicates less space for
callouts detailed with the SRC to determine service
line-delete entries than the firmware expects. This is an
actions.
informational message; no action is required.
Response: If this is a tracking event, no service actions
B111E540 B111E540
are required. Otherwise, use the FRU and procedure
Explanation: There was a failure most likely callouts detailed with the SRC to determine service
attributable to the processor FRU, but it could also be actions.
software-related or require further support.
Response: If this is a tracking event, no service actions B112B841 B112B841
are required. Otherwise, use the FRU and procedure
Explanation: A hardware timeout occurred during a
callouts detailed with the SRC to determine service
cache operation.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 167
B112B89E • B113B83B
callouts detailed with the SRC to determine service
B112B89E B112B89E
actions.
Explanation: The L2 purge engine was busy or timed
out.
B112E504 B112E504
Response: If this is a tracking event, no service actions
Explanation: A hardware failure was detected in the
are required. Otherwise, use the FRU and procedure
central electronics complex (CEC).
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B112C657 B112C657
actions.
Explanation: The L2 line delete count exceeded the
threshold.
B112E540 B112E540
Response: If this is a tracking event, no service actions
Explanation: There was a failure most likely
are required. Otherwise, use the FRU and procedure
attributable to the processor chip cache, but it could
callouts detailed with the SRC to determine service
also be software-related or require further support.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B112C66F B112C66F
callouts detailed with the SRC to determine service
Explanation: A processor chip had an array that was actions.
not repairable.
Response: If this is a tracking event, no service actions B112E550 B112E550
are required. Otherwise, use the FRU and procedure
Explanation: There was a software problem, but this
callouts detailed with the SRC to determine service
could also be processor chip cache-related or require
actions.
further support.
Response: If this is a tracking event, no service actions
B112C807 B112C807
are required. Otherwise, use the FRU and procedure
Explanation: There was an L3 CST hardware failure. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B113B72D B113B72D
actions.
Explanation: This is an error log entry created by a
debug routine.
B112C808 B112C808
Response: If this is a tracking event, no service actions
Explanation: There was an L3 RDT hardware failure. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B113B825 B113B825
Explanation: Unable to stop the instructions.
B112C853 B112C853
Response: If this is a tracking event, no service actions
Explanation: Line test failed. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B113B83B B113B83B
Explanation: An error occurred when starting
B112E501 B112E501 firmware. This is a secondary error; look for prior
entries in the error logs.
Explanation: There was a hardware-detected problem
due to the processor chip cache. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
168 System reference codes (Bxxx)
B113C005 • B114B202
callouts detailed with the SRC to determine service
B113E501 B113E501
actions.
Explanation: There was a hardware-detected problem
due to the processor unit.
B113C005 B113C005
Response: If this is a tracking event, no service actions
Explanation: CINI detected a processor clock failure.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B113E503 B113E503
Explanation: There was a hardware-detected thermal
B113C651 B113C651
failure due to the processor FRU.
Explanation: The P6 chips LBIST signature did not
Response: If this is a tracking event, no service actions
match the expected value.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B113E504 B113E504
Explanation: A hardware failure was detected in the
B113C661 B113C661
central electronics complex (CEC).
Explanation: The failing array cannot be repaired.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B113E540 B113E540
B113C73F B113C73F
Explanation: There was a failure most likely
Explanation: The data in the status address is not attributable to the processor unit, but it could also be
changing. Data should be changing if the test were software-related or require further support.
running correctly.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B113E550 B113E550
B113C74C B113C74C
Explanation: There was a software problem, but this
Explanation: A failure occurred while performing a could also be processor unit-related or require further
direct memory access (DMA) read. support.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B113C74D B113C74D B114B202 B114B202
Explanation: A failure occured while checking the L2 Explanation: Informational message: an IAP warning
AVPS test status. was issued.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 169
B114B2DF • B114C037
B114B2DF B114B2DF B114C005 B114C005
Explanation: A fatal IAP error occurred. Explanation: CINI detected a processor clock failure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B114B2E0 B114B2E0 B114C028 B114C028
Explanation: An IAP error that was not fatal occurred, Explanation: CINI was unable to start vital clocks.
or an IAP warning was issued. The system should be
Response: If this is a tracking event, no service actions
rebooted in slow mode to diagnose this potential
are required. Otherwise, use the FRU and procedure
problem.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B114C02F B114C02F
actions.
Explanation: CINI was unable to find a master
time-of-day chip in the system.
B114B71D B114B71D
Response: If this is a tracking event, no service actions
Explanation: The VPD cannot be updated with the
are required. Otherwise, use the FRU and procedure
new L2 line-delete information because the record is
callouts detailed with the SRC to determine service
already full.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B114C030 B114C030
callouts detailed with the SRC to determine service
actions. Explanation: CINI has detected an SCOM attention on
a chip. This chip will be deconfigured.
B114B757 B114B757 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A chip ID or EC level was not found in
callouts detailed with the SRC to determine service
the list of valid parts on the system.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B114C034 B114C034
callouts detailed with the SRC to determine service
actions. Explanation: CINI has detected a CFAM ID mismatch
between the VPD and a chip.
B114B898 B114B898 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The hypervisor has not handed off the
callouts detailed with the SRC to determine service
bus after forcing the link down; there must be a
actions.
hypervisor problem.
Response: If this is a tracking event, no service actions
B114C037 B114C037
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: CINI has detected a break in the
actions. processor fabric making it unable to find a valid
time-of-day path.
B114C002 B114C002 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: CINI has encountered a software failure.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
170 System reference codes (Bxxx)
B114C040 • B114C804
B114C040 B114C040 B114C661 B114C661
Explanation: CINI was unable to get a phase-locked Explanation: The failing array cannot be repaired.
loop (PLL) synchronization after 10 attempts.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B114C664 B114C664
B114C053 B114C053
Explanation: CFAM ID does not match the CFAM ID
Explanation: No processor chip was available for the in the module VPD.
master drawer master.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B114C66F B114C66F
B114C651 B114C651
Explanation: A processor chip had an array that was
Explanation: The P6 chips LBIST signature did not not repairable.
match the expected value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B114C6F0 B114C6F0
B114C65C B114C65C
Explanation: The processor chip test data was bad.
Explanation: The chip's scan ring did not work
Response: If this is a tracking event, no service actions
correctly.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B114C714 B114C714
Explanation: An uncorrectable error on an up-steam
B114C65D B114C65D
bus was detected.
Explanation: BIST (built-in self-test) did not finish
Response: If this is a tracking event, no service actions
within the allotted time.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B114C803 B114C803
Explanation: CST detected a hardware error.
B114C660 B114C660
Response: If this is a tracking event, no service actions
Explanation: The chips that were tested do not have
are required. Otherwise, use the FRU and procedure
any of the good arrays required for operation.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B114C804 B114C804
actions.
Explanation: RDT detected a hardware error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 171
B114C805 • B114E550
callouts detailed with the SRC to determine service
B114C87B B114C87B
actions.
Explanation: RDT has detected a hardware error in
the processor wire test.
B114C805 B114C805
Response: If this is a tracking event, no service actions
Explanation: Wire node CST hardware failure.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B114E501 B114E501
Explanation: There was a hardware-detected problem
B114C806 B114C806
due to the processor bus controller.
Explanation: A hardware error was detected.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B114E503 B114E503
B114C829 B114C829
Explanation: A thermal event occurred.
Explanation: The wire repair threshold was exceeded
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B114E504 B114E504
B114C878 B114C878
Explanation: A hardware failure was detected in the
Explanation: CST has detected a hardware error. central electronics complex (CEC).
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B114C879 B114C879 B114E540 B114E540
Explanation: CST has detected a hardware error. Explanation: There was a failure most likely
attributable to the processor bus controller, but it could
Response: If this is a tracking event, no service actions also be software-related or require further support.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B114C87A B114C87A
Explanation: The processor wire test has detected a B114E550 B114E550
hardware error.
Explanation: There was a software problem, but this
Response: If this is a tracking event, no service actions could also be processor bus controller-related or require
are required. Otherwise, use the FRU and procedure further support.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
172 System reference codes (Bxxx)
B120105C • B120C732
B120105C B120105C B120C712 B120C712
Explanation: Corrupted data from memory was sent Explanation: The memory controller detected a
to the service processor without an indication that is correctable memory bus error.
was corrupted.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B120C714 B120C714
B120B889 B120B889
Explanation: An uncorrectable error on an up-steam
Explanation: The hardware configuration is invalid. bus was detected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B120C04E B120C04E B120C715 B120C715
Explanation: The DIMMS in the callout list are in a Explanation: A correctable error on an up-stream
configuration that is not supported on this system. memory bus was detected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B120C067 B120C067 B120C716 B120C716
Explanation: The DIMMS in the callout list are in a Explanation: A down-stream uncorrectable error was
quad configuration that is not supported on this detected on the memory bus.
system.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B120C717 B120C717
B120C65F B120C65F
Explanation: A down-stream correctable error was
Explanation: The chip's scan ring did not work detected on the memory bus.
correctly.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B120C732 B120C732
B120C711 B120C711
Explanation: An uncorrectable error on the command
Explanation: The memory controller detected an bus was detected.
uncorrectable memory bus error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 173
B120C733 • B121C710
B120C733 B120C733 B121B85E B121B85E
Explanation: A correctable error on the command bus Explanation: The maintenance command timed out.
was detected.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B121B889 B121B889
B120E501 B120E501
Explanation: The hardware configuration is invalid.
Explanation: There was a hardware-detected problem
Response: If this is a tracking event, no service actions
due to the memory subsystem.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B121C056 B121C056
Explanation: Memory error: training state 0 did not
B120E504 B120E504
complete in the time allotted.
Explanation: A hardware failure was detected in the
Response: If this is a tracking event, no service actions
central electronics complex (CEC).
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B121C70E B121C70E
Explanation: The memory controller failed during
B120E540 B120E540
memory diagnostics.
Explanation: There was a failure most likely
Response: If this is a tracking event, no service actions
attributable to the memory subsystem, but it could also
are required. Otherwise, use the FRU and procedure
be software-related or require further support.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B121C70F B121C70F
actions.
Explanation: The memory controller did not respond
to the command within the time limit.
B120E550 B120E550
Response: If this is a tracking event, no service actions
Explanation: There was a software problem, but this
are required. Otherwise, use the FRU and procedure
could also be memory subsystem-related or require
callouts detailed with the SRC to determine service
further support.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B121C710 B121C710
callouts detailed with the SRC to determine service
actions. Explanation: The memory controller failed during
main storage diagnostics.
B121B2DF B121B2DF Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A fatal IAP error occurred.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
174 System reference codes (Bxxx)
B121C720 • B123C04D
B121C720 B121C720 B123C029 B123C029
Explanation: A correctable error was detected but the Explanation: CINI has detected a memory card
firmware was unable to capture the error information. mismatch. The DIMMs in the DIMM group do not
match and therefore form an invalid memory group.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B121E501 B121E501
B123C02A B123C02A
Explanation: There was a hardware-detected problem
due to the memory controller. Explanation: CINI has detected a DIMM group that is
missing DIMMs.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B121E504 B121E504
B123C02B B123C02B
Explanation: A hardware failure was detected in the
central electronics complex (CEC). Explanation: CINI has detected a missing DIMM
group that is required to configure other DIMM groups
Response: If this is a tracking event, no service actions
in the system.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B121E540 B121E540
Explanation: There was a failure most likely
B123C036 B123C036
attributable to the memory controller, but it could also
be software-related or require further support. Explanation: CINI has detected a DIMM connected to
a memory controller that does not support it.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B121E550 B121E550
B123C04C B123C04C
Explanation: There was a software problem, but this
could also be memory controller-related or require Explanation: A mix of memory DIMM frequencies
further support. was detected that is not supported.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B123C01C B123C01C B123C04D B123C04D
Explanation: CINI has detected an invalid hardware Explanation: The DIMMs in the callout list are not
configuration. DDR2-400.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 175
B123C04E • B124A40F
B123C04E B123C04E B123C76C B123C76C
Explanation: The DIMMS in the callout list are in a Explanation: The threshold for correctable memory
configuration that is not supported on this system. errors was exceeded.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B123C718 B123C718 B123E501 B123E501
Explanation: The main storage diagnostics detected an Explanation: There was a hardware-detected problem
uncorrectable error on a DRAM. due to a memory DIMM or DIMMs.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B123C71A B123C71A B123E504 B123E504
Explanation: The main storage diagnostics detected a Explanation: There was a hardware failure due to a
correctable error on a DIMM. memory DIMM (or DIMMs)
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B123C71B B123C71B B123E540 B123E540
Explanation: More than the allowable number of soft Explanation: There was a failure most likely
memory correctable errors were detected. attributable to a memory DIMM (or DIMMs), but it
could also be software-related or require further
Response: If this is a tracking event, no service actions
support.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B123C71E B123C71E
Explanation: The main storage diagnostics detected
B123E550 B123E550
too many correctable errors.
Explanation: There was a software problem, but this
Response: If this is a tracking event, no service actions
could also be memory DIMM-related or require further
are required. Otherwise, use the FRU and procedure
support.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B123C732 B123C732
actions.
Explanation: An uncorrectable error on the command
bus was detected.
B124A40F B124A40F
Response: If this is a tracking event, no service actions
Explanation: A failure occurred when trying to set the
are required. Otherwise, use the FRU and procedure
block offset and length.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
176 System reference codes (Bxxx)
B124B202 • B124C02D
B124B202 B124B202 B124B758 B124B758
Explanation: Informational message: an IAP warning Explanation: A valid pair was not found the MSL mix
was issued. allowed list
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B124B208 B124B208 B124B889 B124B889
Explanation: Channel initialization failed; a TS0 clock Explanation: Unable to find the associate fabric chip.
miss is suspected.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B124B8A4 B124B8A4
B124B210 B124B210
Explanation: A problem was found when setting up
Explanation: A channel init error occurred. or reading a temperature sensor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B124B2DF B124B2DF B124C027 B124C027
Explanation: A fatal IAP error occurred. Explanation: The value generated was outside the
expected range, and an overflow occurred. The system
Response: If this is a tracking event, no service actions
should checkstop.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B124B2E0 B124B2E0
Explanation: An IAP error that was not fatal occurred,
B124C028 B124C028
or an IAP warning was issued. The system should be
rebooted in slow mode to diagnose this potential Explanation: CINI was unable to start vital clocks.
problem.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B124C02D B124C02D
B124B757 B124B757
Explanation: CINI has detected the DRAMs are not
Explanation: A chip ID or EC level was not found in ready.
the list of valid parts on the system.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 177
B124C030 • B124E504
B124C030 B124C030 B124C714 B124C714
Explanation: The SCOM attention line is active on the Explanation: An uncorrectable error on an up-steam
chip being called out. bus was detected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B124C04C B124C04C B124C803 B124C803
Explanation: Vital clocks are still running and Explanation: CST detected a hardware error.
shouldnt be.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B124C809 B124C809
B124C652 B124C652
Explanation: There was a memory CST hardware
Explanation: A chip's LBIST signature did not equal failure.
the expected value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B124C80A B124C80A
B124C65D B124C65D
Explanation: There was a memory RDT hardware
Explanation: BIST (built-in self-test) did not finish failure.
within the allotted time.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B124E501 B124E501
B124C711 B124C711
Explanation: There was a hardware-detected problem
Explanation: The memory controller detected an due to a memory FRU.
uncorrectable memory bus error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B124E504 B124E504
B124C713 B124C713
Explanation: A hardware failure was detected in the
Explanation: The main storage diagnostics detected a central electronics complex (CEC).
bad memory buffer.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
178 System reference codes (Bxxx)
B124E540 • B125C724
B124E540 B124E540 B125C030 B125C030
Explanation: There was a failure most likely Explanation: The SCOM attention line is active on the
attributable to a memory FRU, but it could also be chip being called out.
software-related or require further support.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B125C652 B125C652
B124E550 B124E550
Explanation: A chips LBIST signature did not
Explanation: There was a software problem, but this equal the expected value.
could also be memory FRU-related or require further
Response: If this is a tracking event, no service actions
support.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B125C65D B125C65D
Explanation: BIST (built-in self-test) did not finish
B125B202 B125B202
within the allotted time.
Explanation: Informational message: an IAP warning
Response: If this is a tracking event, no service actions
was issued.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B125C721 B125C721
Explanation: L3 diagnostics timed out.
B125B2DF B125B2DF
Response: If this is a tracking event, no service actions
Explanation: A fatal error occurred during the elastic
are required. Otherwise, use the FRU and procedure
interface alignment procedure.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B125C722 B125C722
actions.
Explanation: L3 diagnostics failed.
B125B71F B125B71F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The VPD cannot be updated with the
callouts detailed with the SRC to determine service
new L3 line-delete information because the record is
actions.
already full.
Response: If this is a tracking event, no service actions
B125C723 B125C723
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: An unexpected L3 interrupt was found.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B125C028 B125C028 callouts detailed with the SRC to determine service
actions.
Explanation: CINI was unable to start vital clocks.
Response: If this is a tracking event, no service actions
B125C724 B125C724
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The L3 line delete threshold was
actions. exceeded.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 179
B125C726 • B125E550
callouts detailed with the SRC to determine service
B125C769 B125C769
actions.
Explanation: An interface error occurred.
B125C726 B125C726 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: There is no more VPD space to save the
callouts detailed with the SRC to determine service
L3 line delete information.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B125C76A B125C76A
callouts detailed with the SRC to determine service
actions. Explanation: An L3 line delete occurred.
Response: If this is a tracking event, no service actions
B125C755 B125C755 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An L3 cache FBIST failure occurred.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B125E501 B125E501
callouts detailed with the SRC to determine service
actions. Explanation: There was a hardware-detected problem
due to the external cache.
B125C756 B125C756 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An L3 FBIST time-out limit was
callouts detailed with the SRC to determine service
exceeded.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B125E504 B125E504
callouts detailed with the SRC to determine service
actions. Explanation: A hardware failure was detected in the
central electronics complex (CEC).
B125C757 B125C757 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The L3 cache FBIST test is not being run
callouts detailed with the SRC to determine service
because all EDRAM pair halves contain line deletes.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B125E540 B125E540
callouts detailed with the SRC to determine service
actions. Explanation: There was a failure most likely attributed
to the external cache, but it could also be
software-related or require further support.
B125C75C B125C75C
Response: If this is a tracking event, no service actions
Explanation: The L3 FIR bits were set before running
are required. Otherwise, use the FRU and procedure
sequential FBIST.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B125E550 B125E550
actions.
Explanation: There was an external cache failure, most
likely attributable to a software problem, but it could
B125C764 B125C764
also be hardware-related or require further support.
Explanation: The transactions was not synchronized.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
180 System reference codes (Bxxx)
B125FAA2 • B130C654
callouts detailed with the SRC to determine service
B125FAA2 B125FAA2
actions.
Explanation: The CRAM file system on the service
processor is corrupted. Replace the service processor.
B130C01B B130C01B
Response: If this is a tracking event, no service actions
Explanation: CINI was unable to find the frequency
are required. Otherwise, use the FRU and procedure
data that was requested.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B130B202 B130B202
actions.
Explanation: Informational message: an IAP warning
was issued.
B130C028 B130C028
Response: If this is a tracking event, no service actions
Explanation: CINI was unable to start vital clocks.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B130B2DF B130B2DF
Explanation: A fatal IAP error occurred.
B130C030 B130C030
Response: If this is a tracking event, no service actions
Explanation: CINI has detected an SCOM attention on
are required. Otherwise, use the FRU and procedure
a chip. This chip will be deconfigured.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B130B2E0 B130B2E0
actions.
Explanation: A recoverable error occurred during the
elastic interface alignment procedure.
B130C03F B130C03F
Response: If this is a tracking event, no service actions
Explanation: A PLL (phase-locked loop) lock error
are required. Otherwise, use the FRU and procedure
occurred.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B130B889 B130B889
actions.
Explanation: The hardware configuration is invalid
Response: If this is a tracking event, no service actions B130C652 B130C652
are required. Otherwise, use the FRU and procedure
Explanation: A chips LBIST signature did not
callouts detailed with the SRC to determine service
equal the expected value.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B130B892 B130B892
callouts detailed with the SRC to determine service
Explanation: Hardware register access timed out actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B130C654 B130C654
callouts detailed with the SRC to determine service
Explanation: A chips ABIST signature did not
actions.
equal the expected value.
Response: If this is a tracking event, no service actions
B130B8AF B130B8AF
are required. Otherwise, use the FRU and procedure
Explanation: A temperature sensor calibration was not callouts detailed with the SRC to determine service
valid; a default value is being used. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 181
B130C65D • B131B2DF
are required. Otherwise, use the FRU and procedure
B130C65D B130C65D
callouts detailed with the SRC to determine service
Explanation: BIST (built-in self-test) did not finish actions.
within the allotted time.
Response: If this is a tracking event, no service actions B130E501 B130E501
are required. Otherwise, use the FRU and procedure
Explanation: There was a hardware-detected problem
callouts detailed with the SRC to determine service
due to the I/O subsystem.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B130C65F B130C65F
callouts detailed with the SRC to determine service
Explanation: The scan ring for a chip did not work actions.
correctly.
Response: If this is a tracking event, no service actions B130E504 B130E504
are required. Otherwise, use the FRU and procedure
Explanation: A hardware failure was detected in the
callouts detailed with the SRC to determine service
central electronics complex (CEC).
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B130C670 B130C670
callouts detailed with the SRC to determine service
Explanation: The chip is bad - all processors have actions.
clock errors.
Response: If this is a tracking event, no service actions B130E540 B130E540
are required. Otherwise, use the FRU and procedure
Explanation: There was a failure most likely
callouts detailed with the SRC to determine service
attributable to the I/O subsystem, but could also be
actions.
software-related or require further support.
Response: If this is a tracking event, no service actions
B130C80B B130C80B
are required. Otherwise, use the FRU and procedure
Explanation: CST detected a hardware error. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B130E550 B130E550
actions.
Explanation: There was a software problem, but this
could also be I/O subsystem-related or require further
B130C853 B130C853 support.
Explanation: Line test failed. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B131B202 B131B202
B130C854 B130C854 Explanation: Informational message: IAP warning
Explanation: Wire test has detected an RDT error. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B131B2DF B131B2DF
B130CD0B B130CD0B Explanation: A fatal IAP error occurred.
Explanation: The number of lane failures between the Response: If this is a tracking event, no service actions
control module and the optical links exceeded the are required. Otherwise, use the FRU and procedure
threshold during an internal test. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
182 System reference codes (Bxxx)
B131B2E0 • B131C027
B131B2E0 B131B2E0 B131B895 B131B895
Explanation: An IAP error that was not fatal occurred, Explanation: A hardware timeout occurred during
or an IAP warning was issued. The system should be accessing a chip.
rebooted in slow mode to diagnose this potential
Response: If this is a tracking event, no service actions
problem.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B131C01B B131C01B
Explanation: No valid GXPT bus ratio or frequency
B131B82A B131B82A
was found to accommodate the chip in the GXTP slot.
Explanation: A hardware operation timed out The chip will be deconfigured and the boot will
continue.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B131B84E B131B84E
B131C01F B131C01F
Explanation: A phase-locked loop lock failure
occurred. Explanation: A chip's JTAG was not granted the
PSCOM engine.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B131B857 B131B857
B131C023 B131C023
Explanation: Unable to properly quiesce I/O
hardware Explanation: CINI failed during the auto TLAR
calculation.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B131B889 B131B889
B131C026 B131C026
Explanation: Unable to find the associate fabric chip.
Explanation: CINI has detected an attempt to execute
Response: If this is a tracking event, no service actions
an operation that is unsupported.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B131B892 B131B892
Explanation: Hardware register access timed out
B131C027 B131C027
Response: If this is a tracking event, no service actions
Explanation: CINI has received invalid data.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 183
B131C030 • B131E550
B131C030 B131C030 B131C65F B131C65F
Explanation: The SCOM attention line is active on the Explanation: The chips scan ring is not working
chip being called out. properly.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B131C03E B131C03E B131C853 B131C853
Explanation: CINI was unable to obtain a PLL lock on Explanation: Line test failed.
the controller chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B131E501 B131E501
B131C03F B131C03F
Explanation: There was a hardware-detected problem
Explanation: CINI was unable to obtain a due to the I/O hub.
phased-locked loop (PLL) lock.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B131E504 B131E504
B131C652 B131C652
Explanation: A hardware failure was detected in the
Explanation: The chips LBIST signature did not central electronics complex (CEC).
match the expected value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B131E540 B131E540
B131C658 B131C658
Explanation: There was a failure most likely
Explanation: Informational message: an L2 line delete attributable to the I/O hub, but it could also be
was done. software-related or require further support.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B131C65D B131C65D B131E550 B131E550
Explanation: BIST (built-in self-test) did not finish Explanation: There was a software problem, but this
within the allotted time. could also be I/O hub-related or require further
support.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
184 System reference codes (Bxxx)
B132C009 • B134C654
B132C009 B132C009 B133E501 B133E501
Explanation: CINI failed to enable the host PCI bus. Explanation: There was a hardware-detected problem
due to the I/O bus interface.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B132C00A B132C00A
B133E504 B133E504
Explanation: CINI failed to verify the host PCI bus.
Explanation: A hardware failure was detected in the
Response: If this is a tracking event, no service actions
central electronics complex (CEC).
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B132E501 B132E501
Explanation: There has been a hardware-detected
B133E540 B133E540
problem due to the I/O bridge.
Explanation: There was a failure most likely
Response: If this is a tracking event, no service actions
attributable to the I/O bus interface, but it could also
are required. Otherwise, use the FRU and procedure
be software-related or require further support.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B132E504 B132E504
actions.
Explanation: A hardware failure was detected in the
central electronics complex (CEC).
B133E550 B133E550
Response: If this is a tracking event, no service actions
Explanation: There was a software problem, but this
are required. Otherwise, use the FRU and procedure
could also be I/O bus interface-related or require
callouts detailed with the SRC to determine service
further support.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B132E540 B132E540
callouts detailed with the SRC to determine service
Explanation: There was a failure most likely actions.
attributable to the I/O bridge hardware, but it could
also be software-related or require further support.
B134C652 B134C652
Response: If this is a tracking event, no service actions
Explanation: A chips LBIST result did not equal
are required. Otherwise, use the FRU and procedure
the expected value.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B132E550 B132E550
actions.
Explanation: There was a software problem, but this
could also be I/O bridge chip-related or require further
B134C654 B134C654
support.
Explanation: The chip's ABIST signature didnt
Response: If this is a tracking event, no service actions
match the expected signature.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 185
B134C655 • B13BC764
B134C655 B134C655 B13BC75F B13BC75F
Explanation: A chips HBIST result did not equal Explanation: The port ready bit was not set; unable to
the expected value. proceed with the test.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B134C65F B134C65F B13BC760 B13BC760
Explanation: The scan ring on a chip did not work Explanation: The port ready bit was not set; unable to
correctly. proceed with the test.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B135E501 B135E501 B13BC761 B13BC761
Explanation: There was a hardware-detected problem Explanation: A phase-locked loop (PLL) was not
due to the SMA I/O hub. locked; unable to proceed with the test.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B135E504 B135E504 B13BC762 B13BC762
Explanation: There was a hardware failure due to the Explanation: A phase-locked loop (PLL) was not
I/O SMA hub. locked; unable to proceed with the test.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B135E540 B135E540 B13BC763 B13BC763
Explanation: There was a failure most likely Explanation: Configuring the circumvention register
attributable to the I/O SMA hub, but it could also be failed; the test cannot proceed.
software-related or require further support.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B13BC764 B13BC764
B135E550 B135E550
Explanation: The data was not synchronized; unable
Explanation: There was a software problem, but this to proceed with the test.
could also be I/O SMA hub-related or require further
Response: If this is a tracking event, no service actions
support.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
186 System reference codes (Bxxx)
B13BC766 • B1501059
B13BC766 B13BC766 B1501049 B1501049
Explanation: An error counter was not zero; the test Explanation: Unable to determine the type of error
cannot proceed. from the hardware.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B13BC767 B13BC767 B150104B B150104B
Explanation: An error counter was not zero; the test Explanation: The PSI link is down. No DMAs are
cannot proceed. possible.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B13BC768 B13BC768 B150104E B150104E
Explanation: An error counter was not zero; the test Explanation: A hardware protocol violation has been
cannot proceed. detected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1501034 B1501034 B150104F B150104F
Explanation: The chic client thread failed to collect Explanation: A hardware timeout has been detected.
DMA error data.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1501050 B1501050
B1501037 B1501037
Explanation: The link needs to be reset.
Explanation: C hic client thread that was supposed to
Response: If this is a tracking event, no service actions
collect DMA error data encountered an error.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1501059 B1501059
Explanation: The device driver has returned an
B1501045 B1501045
unknown error type.
Explanation: Time out waiting for CEC debug data.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 187
B1502616 • B150B12D
B1502616 B1502616 B150B106 B150B106
Explanation: A critical error occurred on the Explanation: There were no functional nodes found in
thermal/power management device (TPMD); it is being the system. If this is a multi-processor-drawer system,
disabled. the first node is not functioning.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150A422 B150A422 B150B107 B150B107
Explanation: A file was not found. Explanation: This indicates that there are no
functional processor clocks in the system, or no active
Response: If this is a tracking event, no service actions
functional processor clocks.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B150A450 B150A450
Explanation: The RB keyword is not programmed.
B150B10C B150B10C
Response: If this is a tracking event, no service actions
Explanation: An error occurred when creating a group
are required. Otherwise, use the FRU and procedure
object.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B150A492 B150A492
actions.
Explanation: No VPD was found.
Response: If this is a tracking event, no service actions B150B110 B150B110
are required. Otherwise, use the FRU and procedure
Explanation: The P5IOC2 was not functional.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B150B104 B150B104
actions.
Explanation: Resources are present but not
functioning.
B150B12B B150B12B
Response: If this is a tracking event, no service actions
Explanation: There is not enough hardware in the
are required. Otherwise, use the FRU and procedure
system to boot.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B150B105 B150B105
actions.
Explanation: The processor core is not functioning, or
it cannot be detected.
B150B12D B150B12D
Response: If this is a tracking event, no service actions
Explanation: An invalid unit id was detected.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
188 System reference codes (Bxxx)
B150B131 • B150B203
B150B131 B150B131 B150B177 B150B177
Explanation: A card in the system is missing, or its Explanation: A functional TPMD card was not found
VPD data is corrupted. in a server that requires one.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150B13B B150B13B B150B17B B150B17B
Explanation: A hole was detected in the plugging of Explanation: Not all of the DIMMs in the power
the nodes. domain have the same minimum voltage.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150B145 B150B145 B150B17C B150B17C
Explanation: A chip has been found to be missing. Explanation: The DIMMs with the CCIN listed do not
have a valid voltage in the DIMM voltage definition
Response: If this is a tracking event, no service actions
file.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
If this is not a tracking event p erform isolation
actions.
procedure FSPSP46 located in your host server's service
guide.
B150B180 B150B180
B150B151 B150B151 Explanation: One or more memory cards in the
system is not supported.
Explanation: An error occurred while creating a chip
object. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B150B202 B150B202
B150B170 B150B170 Explanation: Informational message: an IAP warning
was issued.
Explanation: The configuration of the processor
card(s) is invalid. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B150B203 B150B203
B150B176 B150B176 Explanation: Timed out waiting for a slow bus
operation to complete.
Explanation: A system was found without a functional
TPMD card. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 189
B150B2C5 • B150B716
B150B2C5 B150B2C5 B150B480 B150B480
Explanation: One or more bus alignment errors Explanation: An error was returned from a
occurred; look for prior error log entries with the lower-level function.
format B1xxB2DF and take the recommended actions
Response: If this is a tracking event, no service actions
for those entries.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B150B481 B150B481
Explanation: Failed to turn on a chip clock.
B150B2CC B150B2CC
Response: If this is a tracking event, no service actions
Explanation: Internal software error: invalid
are required. Otherwise, use the FRU and procedure
parameter passed into a function
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B150B482 B150B482
actions.
Explanation: The service processor was unable to turn
off a chip clock.
B150B2DE B150B2DE
Response: If this is a tracking event, no service actions
Explanation: Fatal bus alignment error occurred
are required. Otherwise, use the FRU and procedure
between items in the callout list
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B150B483 B150B483
actions.
Explanation: Failure of a chip clock operation.
B150B2DF B150B2DF Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Fatal bus alignment error occurred
callouts detailed with the SRC to determine service
between items in the callout list
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B150B484 B150B484
callouts detailed with the SRC to determine service
actions. Explanation: Internal firmware error.
Response: If this is a tracking event, no service actions
B150B2E0 B150B2E0 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Non-fatal bus alignment error occurred
actions.
between items in callout list. System will continue to
run.
B150B485 B150B485
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: The clock selection value is not
callouts detailed with the SRC to determine service supported on this system.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B150B2E8 B150B2E8 callouts detailed with the SRC to determine service
actions.
Explanation: An internal firmware error occurred.
Response: If this is a tracking event, no service actions
B150B716 B150B716
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The IPL was restarted due to hardware
actions. deconfiguration.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
190 System reference codes (Bxxx)
B150B718 • B150B941
callouts detailed with the SRC to determine service
B150B918 B150B918
actions.
Explanation: An ADAL PSI error occurred.
B150B718 B150B718 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Unable to find a functional
callouts detailed with the SRC to determine service
communication path between the service processor and
actions.
the processor. Look at the error logs and guard records
to isolate the failing or missing hardware.
B150B919 B150B919
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: An ADAL JTAG error occurred.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B150B72D B150B72D actions.
Explanation: This is an error log entry created by a
debug routine. B150B91B B150B91B
Response: If this is a tracking event, no service actions Explanation: An ADAL mailbox error occurred.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B150B73F B150B73F
Explanation: A power fault was detected. B150B91C B150B91C
Response: If this is a tracking event, no service actions Explanation: There was an error when closing the test.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B150B913 B150B913
Explanation: T he call to rdal_scom_open failed. B150B921 B150B921
Response: If this is a tracking event, no service actions Explanation: An error occurred when shifting data in.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B150B914 B150B914
Explanation: The call to rdal_scom_close failed. B150B922 B150B922
Response: If this is a tracking event, no service actions Explanation: The firmware encountered an error when
are required. Otherwise, use the FRU and procedure shifting data out from a chip as part of a scan
callouts detailed with the SRC to determine service operation.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B150B917 B150B917 callouts detailed with the SRC to determine service
actions.
Explanation: An ADAL SCOM error occurred.
Response: If this is a tracking event, no service actions
B150B941 B150B941
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The firmware encountered an error when
actions. trying to read data from a ring inside a chip.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 191
B150B942 • B150B967
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150B942 B150B942 B150B959 B150B959
Explanation: The firmware encountered an error when Explanation: There was an ADAL MBX scratch read
trying to read data from an SCOM register inside a error.
chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B150B963 B150B963
B150B943 B150B943
Explanation: The firmware detected that the value
Explanation: The firmware encountered an error when scanned out from the instruction status register of the
trying to write data to a ring inside a chip. chip is invalid.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150B944 B150B944 B150B964 B150B964
Explanation: The firmware encountered an error when Explanation: SCOM attentions were detected.
trying to write data to an SCOM register inside a chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B150B965 B150B965
B150B946 B150B946
Explanation: There was a CRC miscompare, or a
Explanation: The firmware encountered an error when non-SCOM vital error.
trying to write data to a general purpose register inside
Response: If this is a tracking event, no service actions
a chip.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B150B966 B150B966
Explanation: The firmware detected a CRC
B150B948 B150B948
miscompare error from the specified chip.
Explanation: Unable to start a data flushing process
Response: If this is a tracking event, no service actions
on a chip.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B150B967 B150B967
Explanation: The firmware detected either a parity
B150B94B B150B94B
error or an invalid command attention raised from the
Explanation: The SCAN/SCOM device driver specified chip.
encountered an error when trying to write to an
Response: If this is a tracking event, no service actions
internal register of a chip.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
192 System reference codes (Bxxx)
B150B982 • B150C801
B150B982 B150B982 B150C02B B150C02B
Explanation: The firmware has detected an SCOM Explanation: CINI has detected a missing DIMM
attention raised from the specified chip. group that is required to configure other DIMM groups
in the system.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B150C005 B150C005
B150C02F B150C02F
Explanation: CINI detected a processor clock failure.
Explanation: CINI was unable to find a master
Response: If this is a tracking event, no service actions
time-of-day chip in the node.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B150C01C B150C01C
Explanation: CINI has detected an invalid hardware
B150C04B B150C04B
configuration.
Explanation: Clocks that should be stopped at this
Response: If this is a tracking event, no service actions
point are still running.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B150C023 B150C023
Explanation: CINI failed during the auto TLAR
B150C04C B150C04C
calculation.
Explanation: Vital clocks are still running and
Response: If this is a tracking event, no service actions
shouldn't be.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B150C028 B150C028
Explanation: CINI was unable to start vital clocks.
B150C053 B150C053
Response: If this is a tracking event, no service actions
Explanation: No processor chip was available for the
are required. Otherwise, use the FRU and procedure
master drawer master
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B150C02A B150C02A
actions.
Explanation: CINI has detected a DIMM group that is
missing DIMMs.
B150C801 B150C801
Response: If this is a tracking event, no service actions
Explanation: CST detected a hardware error.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 193
B150C802 • B150C80F
B150C802 B150C802 B150C809 B150C809
Explanation: RDT detected a hardware error. Explanation: CST detected a hardware error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150C803 B150C803 B150C80A B150C80A
Explanation: CST detected a hardware error. Explanation: RDT detected a hardware error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150C804 B150C804 B150C80B B150C80B
Explanation: RDT detected a hardware error. Explanation: CST detected a hardware error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150C805 B150C805 B150C80C B150C80C
Explanation: A hardware error was detected. Explanation: RDT detected a hardware error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150C806 B150C806 B150C80D B150C80D
Explanation: A hardware error was detected. Explanation: CST detected a hardware error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150C807 B150C807 B150C80E B150C80E
Explanation: eRepair data was successfully saved. Explanation: RDT detected a hardware error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150C808 B150C808 B150C80F B150C80F
Explanation: RDT detected a hardware error. Explanation: The wire test error log is full.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
194 System reference codes (Bxxx)
B150C817 • B150C87B
B150C817 B150C817 B150C861 B150C861
Explanation: Wire test received an invalid input Explanation: The hardware may not exist or was
parameter. garded out.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150C81A B150C81A B150C869 B150C869
Explanation: A null pointer was found. Explanation: The hardware may not exist or was
garded out.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B150C822 B150C822
B150C878 B150C878
Explanation: eRepair data was successfully applied.
Explanation: CST has detected a hardware error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B150C823 B150C823
B150C879 B150C879
Explanation: The system processor group object was
not found. Explanation: CST has detected a hardware error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150C826 B150C826 B150C87A B150C87A
Explanation: RDT was run using the current IPL Explanation: CST has detected a hardware error in the
speed and type settings, even though the processor wire test.
manufacturing flag that allows the RTD to be run at the
Response: If this is a tracking event, no service actions
maximum speed was enabled.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B150C87B B150C87B
Explanation: RDT has detected a hardware error in
B150C852 B150C852
the processor wire test.
Explanation: CST detected a hardware error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 195
B150CA01 • B150E501
callouts detailed with the SRC to determine service
B150CA01 B150CA01
actions.
Explanation: Informational only: Guard actions
performed on items the system detected and guarded
B150D134 B150D134
during runtime.
Explanation: The AH server process failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B150CA02 B150CA02
B150D141 B150D141
Explanation: Informational only: Guard actions
performed on items the system detected and guarded Explanation: The chip attention handler was asked to
during runtime, or that were guarded out using the handle an invalid attention type.
ASMI.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B150D145 B150D145
B150CA03 B150CA03
Explanation: An scom attention was detected on the
Explanation: The guard data did not exist because it current chip.
was the first boot of this system, or NVRAM had been
cleared. Guard data is now available.
B150D151 B150D151
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: There was a callout failure.
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B150CA04 B150CA04 actions.
Explanation: Guard detected a new version of the
guard data area. The guard data area was reformatted B150D159 B150D159
and the previous guard actions have been lost. Explanation: An invalid register value was found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B150CA16 B150CA16 B150D15E B150D15E
Explanation: Informational message: gard actions Explanation: An invalid callout was found.
were performed on devices the system detected and
garded out during runtime. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B150E501 B150E501
B150D106 B150D106 Explanation: There was a hardware-detected problem
due to the CEC hardware subsystem.
Explanation: AH log read failure.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
actions.
196 System reference codes (Bxxx)
B150E504 • B151B729
B150E504 B150E504 B1517204 B1517204
Explanation: There was a hardware problem in the Explanation: Error reading boot parameters
CEC hardware subsystem.
Response: FSPSP02
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1517205 B1517205
callouts detailed with the SRC to determine service
actions. Explanation: Boot code error
Response: FSPSP02
B150E540 B150E540
Explanation: There was a failure most likely B1517206 B1517206
attributable to the CEC hardware subsystem, but it
could also be software-related or require further Explanation: Unit check timer was reset
support. Response: FSPSP02
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B151720A B151720A
callouts detailed with the SRC to determine service
actions. Explanation: Power-off reset occurred. FipsDump
should be analyzed: Possible hardware problem
B150E550 B150E550 Response: FSPSP02
Explanation: There was a CEC hardware subsystem
failure, most likely attributable to a software problem, B151B202 B151B202
but it could also be hardware-related or require further Explanation: Informational message: an IAP warning
support. was issued.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1517200 B1517200 B151B2DF B151B2DF
Explanation: Invalid boot request Explanation: A fatal IAP error occurred.
Response: FSPSP02 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1517201 B1517201 callouts detailed with the SRC to determine service
actions.
Explanation: Service processor failure
Response: FSPSP02 B151B2E0 B151B2E0
Explanation: An IAP error that was not fatal occurred,
B1517202 B1517202 or an IAP warning was issued. The system should be
Explanation: The permanent and temporary firmware rebooted in slow mode to diagnose this potential
sides are both marked invalid problem.
Response: FSPSP02 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1517203 B1517203 actions.
Explanation: Error setting boot parameters
B151B729 B151B729
Response: FSPSP02
Explanation: There was a pattern mismatch during the
DMA test between the service processor and the
processor; memory could not be read from or written
to correctly.
Response: If this is a tracking event, no service actions
(B1xx) Reference codes 197
B151B72A • B151F116
are required. Otherwise, use the FRU and procedure
B151E6D0 B151E6D0
callouts detailed with the SRC to determine service
actions. Explanation: The secondary service processor was
deconfigured because there was no commuication
between the primary and the secondary for more than
B151B72A B151B72A
one hour.
Explanation: An error was received when attempting
Response: If this is a tracking event, no service actions
a DMA operation between the service processor and
are required. Otherwise, use the FRU and procedure
the processor.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B151F107 B151F107
actions.
Explanation: The threshold of new DRAM errors was
reached.
B151B732 B151B732
Response: If this is a tracking event, no service actions
Explanation: An internal firmware error occurred.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B151F109 B151F109
Explanation: The threshold of new NVRAM errors
B151B890 B151B890
was reached.
Explanation: A hardware error was detected on an
Response: If this is a tracking event, no service actions
internal bus.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B151F10A B151F10A
Explanation: An NVRAM address has appeared
B151B893 B151B893
multiple times.
Explanation: An internal firmware error occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B151F10D B151F10D
B151E405 B151E405
Explanation: The threshold of bad blocks in the
Explanation: A failure in the memory subsystem was NVRAMs flash memory was exceeded.
detected.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B151F116 B151F116
B151E504 B151E504
Explanation: FSI IRQ loop event occurred; one or
Explanation: A CEC hardware failure was detected. more engines was masked.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
198 System reference codes (Bxxx)
B151F127 • B155130C
B151F127 B151F127 B152F127 B152F127
Explanation: The number of one-bit flips exceeded the Explanation: The number of one-bit flips exceeded the
threshold. The service processor hardware will have to threshold. The service processor hardware will have to
be replaced. be replaced.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B151F128 B151F128 B1534126 B1534126
Explanation: The health monitor found that a Explanation: There was an ERC GPIO (general
threshhold had been exceeded. purpose I/O) failure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B152B732 B152B732 B1534128 B1534128
Explanation: An internal firmware error occurred. Explanation: There was an I2C open failure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B152E6D0 B152E6D0 B1551309 B1551309
Explanation: The secondary service processor was Explanation: IVPD is unable to determine the
deconfigured because there was no communication presence of end devices.
between the primary and the secondary for more than
Response: If this is a tracking event, no service actions
one hour.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B155130A B155130A
Explanation: While detecting the end device status
B152F109 B152F109
using the I2C ADAL, both the SDA and SCL lines were
Explanation: The threshold of new NVRAM errors found to be low. This means no devices are present on
was reached. the I2C bus.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B152F10D B152F10D B155130C B155130C
Explanation: The threshold of bad blocks in the Explanation: Failed to open an I2C device.
NVRAMs flash memory was exceeded.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 199
B155130E • B1551320
B155130E B155130E B1551317 B1551317
Explanation: Failed to configure the I2C bus. Explanation: Failed to close an I2C ADAL handle.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B155130F B155130F B155131A B155131A
Explanation: First-failure-data-capture unlock failed. Explanation: An "invalid sub-device" error was
returned by the hub expansion processor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1551310 B1551310
B155131B B155131B
Explanation: First-failure-data-capture failed.
Explanation: An I2C read/write operation was retried,
Response: If this is a tracking event, no service actions
and failed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1551311 B1551311
Explanation: Failed to read from an I2C device.
B155131E B155131E
Response: If this is a tracking event, no service actions
Explanation: A hardware error was returned by the
are required. Otherwise, use the FRU and procedure
hub expansion processor.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1551312 B1551312
actions.
Explanation: Failed to read from an I2C device.
Response: If this is a tracking event, no service actions B155131F B155131F
are required. Otherwise, use the FRU and procedure
Explanation: An "invalid command" or "invalid bus
callouts detailed with the SRC to determine service
speed" error was returned by the hub expansion
actions.
processor.
Response: If this is a tracking event, no service actions
B1551313 B1551313
are required. Otherwise, use the FRU and procedure
Explanation: Failed to seek on an I2C ADAL handle. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1551320 B1551320
actions.
Explanation: Sub-bus reset failed.
Response: If this is a tracking event, no service actions
B1551314 B1551314
are required. Otherwise, use the FRU and procedure
Explanation: Failed to write to an I2C device. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
200 System reference codes (Bxxx)
B155132A • B155A40E
B155132A B155132A B1552600 B1552600
Explanation: A query of the hub status failed. Explanation: A vital product data (VPD) error
occurred.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: Use the FRU and procedure callouts
callouts detailed with the SRC to determine service detailed with the SRC to determine service actions.
actions.
B1558903 B1558903
B1551331 B1551331
Explanation: The service processor synchronization
Explanation: The IVPD query of the HUB version (SINK) interface timed out waiting for a firmware
failed. component to establish a synchronization lock.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B155A404 B155A404
callouts detailed with the SRC to determine service
Explanation: A failure occurred when validating vital
actions.
product data (VPD) in the converged format.
Response: If this is a tracking event, no service actions
B1551332 B1551332
are required. Otherwise, use the FRU and procedure
Explanation: The IVPD query of the HUB version callouts detailed with the SRC to determine service
failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B155A408 B155A408
callouts detailed with the SRC to determine service
Explanation: An invalid VPD format found.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1551333 B1551333
callouts detailed with the SRC to determine service
Explanation: The IVPD query of the HUB version actions.
failed.
Response: If this is a tracking event, no service actions B155A409 B155A409
are required. Otherwise, use the FRU and procedure
Explanation: An I2C bus configuration operation
callouts detailed with the SRC to determine service
failed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1551334 B1551334
callouts detailed with the SRC to determine service
Explanation: The IVPD query of the HUB version actions.
failed.
Response: If this is a tracking event, no service actions B155A40C B155A40C
are required. Otherwise, use the FRU and procedure
Explanation: A failure occurred.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1551361 B1551361
actions.
Explanation: A write operation to set the device failed.
Response: If this is a tracking event, no service actions B155A40E B155A40E
are required. Otherwise, use the FRU and procedure
Explanation: Failed to read a local device string, or
callouts detailed with the SRC to determine service
the read operation was successful but the data did not
actions.
match.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 201
B155A40F • B155A436
B155A40F B155A40F B155A41D B155A41D
Explanation: A failure occurred when trying to set the Explanation: The vital product data (VPD) code
block offset and length. exited.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B155A413 B155A413 B155A423 B155A423
Explanation: An error occurred. Explanation: Failed to open a file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B155A415 B155A415 B155A430 B155A430
Explanation: A failure occurred when writing to the Explanation: Failed to validate the format of the VPD.
I2C device.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B155A433 B155A433
B155A416 B155A416
Explanation: A file index was not found.
Explanation: A failure occurred when attempting to
Response: If this is a tracking event, no service actions
reset a chip.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B155A434 B155A434
Explanation: An invalid call was made.
B155A41B B155A41B
Response: If this is a tracking event, no service actions
Explanation: The enclosure feature code is the same as
are required. Otherwise, use the FRU and procedure
the system's machine type and model. To resolve this,
callouts detailed with the SRC to determine service
the enclosure "FC" keyword must be verified and
actions.
reentered if necessary.
Response: If this is a tracking event, no service actions
B155A435 B155A435
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: A failure occurred when trying to get the
actions. block entry information.
Response: If this is a tracking event, no service actions
B155A41C B155A41C are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A keyword cannot be found in the VPD
actions.
buffer.
Response: If this is a tracking event, no service actions
B155A436 B155A436
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: An invalid device type was found.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
202 System reference codes (Bxxx)
B155A437 • B155A442
B155A437 B155A437 B155A43D B155A43D
Explanation: An invalid vital product data (VPD) Explanation: An invalid parsing operation was
format was found. attempted.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B155A438 B155A438 B155A43E B155A43E
Explanation: The file index was not valid. Explanation: An invalid synchronization file was
found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B155A439 B155A439
B155A43F B155A43F
Explanation: The block offset and block length are
greater than the calculated vital product data (VPD) Explanation: The synchronization success was not
image size, or the block read size is not the same as the valid.
size in the table of block data.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B155A440 B155A440
B155A43A B155A43A
Explanation: The system ID is invalid or has not been
Explanation: VTOC block offset and VTOC block programmed.
length are greater than the calculated VPD image size.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B155A441 B155A441
B155A43B B155A43B
Explanation: Setting an attribute failed.
Explanation: The operation was not valid.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B155A442 B155A442
B155A43C B155A43C
Explanation: Building a location failed.
Explanation: A parameter was not valid.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 203
B155A445 • B155A455
callouts detailed with the SRC to determine service
B155A445 B155A445
actions.
Explanation: A failure occurred.
Response: If this is a tracking event, no service actions B155A450 B155A450
are required. Otherwise, use the FRU and procedure
Explanation: The RB system keyword is not valid or
callouts detailed with the SRC to determine service
has not been programmed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A44A B155A44A
callouts detailed with the SRC to determine service
Explanation: Failed to read the module VPD from an actions.
I2C SEEPROM.
Response: If this is a tracking event, no service actions B155A451 B155A451
are required. Otherwise, use the FRU and procedure
Explanation: The system storage serial number (SG) is
callouts detailed with the SRC to determine service
not valid or has not been programmed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A44B B155A44B
callouts detailed with the SRC to determine service
Explanation: There was a failure trying to read one of actions.
the smart chip blocks.
Response: If this is a tracking event, no service actions B155A452 B155A452
are required. Otherwise, use the FRU and procedure
Explanation: The system unique ID (SU) is not valid
callouts detailed with the SRC to determine service
or has not been programmed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A44C B155A44C
callouts detailed with the SRC to determine service
Explanation: ECC check failed on the given FRU. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B155A453 B155A453
callouts detailed with the SRC to determine service
Explanation: The system serial number (SE) is not
actions.
valid or has not been programmed.
Response: If this is a tracking event, no service actions
B155A44D B155A44D
are required. Otherwise, use the FRU and procedure
Explanation: Failed to get VTOC block entry callouts detailed with the SRC to determine service
information. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B155A454 B155A454
callouts detailed with the SRC to determine service
Explanation: The system model (TM) is not valid or
actions.
has not been programmed.
Response: If this is a tracking event, no service actions
B155A44E B155A44E
are required. Otherwise, use the FRU and procedure
Explanation: Checksum failed on a FRU. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B155A455 B155A455
actions.
Explanation: The system storage type model (TN) is
not valid or has not been programmed.
B155A44F B155A44F
Response: If this is a tracking event, no service actions
Explanation: The world-wide node name is not valid are required. Otherwise, use the FRU and procedure
or has not been programmed. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
204 System reference codes (Bxxx)
B155A46B • B155A499
B155A46B B155A46B B155A47E B155A47E
Explanation: A read failure occurred. Explanation: No valid copy of the system vital
product data (VPD) was found on this system.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B155A46E B155A46E
B155A483 B155A483
Explanation: Failure when reading a registry value.
Explanation: A failure occurred when reading a table.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B155A46F B155A46F
B155A486 B155A486
Explanation: Failure when writing a registry value.
Explanation: A recalculation failure occurred.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B155A471 B155A471
B155A490 B155A490
Explanation: The resource ID (RID) was not tagged.
Explanation: The vital product data (VPD) was
Response: If this is a tracking event, no service actions
guarded.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B155A472 B155A472
Explanation: The SCED sense operation failed.
B155A491 B155A491
Response: If this is a tracking event, no service actions
Explanation: No valid copy of the enclosure vital
are required. Otherwise, use the FRU and procedure
product data (VPD) was found on this system.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B155A476 B155A476
actions.
Explanation: Failed to set the DIMM change
parameter.
B155A499 B155A499
Response: If this is a tracking event, no service actions
Explanation: A failure occurred when finding a data
are required. Otherwise, use the FRU and procedure
block in the converged-format vital product data
callouts detailed with the SRC to determine service
(VPD).
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A477 B155A477
callouts detailed with the SRC to determine service
Explanation: Failed to set the DIMM speed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 205
B155A4AF • B15738B0
callouts detailed with the SRC to determine service
B155A4AF B155A4AF
actions.
Explanation: Configuration on the I2C DP failed.
Response: If this is a tracking event, no service actions B155B107 B155B107
are required. Otherwise, use the FRU and procedure
Explanation: A card has been detected in the system,
callouts detailed with the SRC to determine service
but valid VPD cannot be collected for it.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A4B9 B155A4B9
callouts detailed with the SRC to determine service
Explanation: There was an error in finding the serial actions.
number keyword data.
Response: If this is a tracking event, no service actions B155B128 B155B128
are required. Otherwise, use the FRU and procedure
Explanation: An invalid vital product data (VPD) port
callouts detailed with the SRC to determine service
number was detected.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A4D4 B155A4D4
callouts detailed with the SRC to determine service
Explanation: A failure occurred when reading the actions.
table from p1.
Response: If this is a tracking event, no service actions B155B129 B155B129
are required. Otherwise, use the FRU and procedure
Explanation: An invalid VPD port number was
callouts detailed with the SRC to determine service
encountered.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A4E0 B155A4E0
callouts detailed with the SRC to determine service
Explanation: The RB system keyword is invalid or has actions.
not been programmed.
Response: If this is a tracking event, no service actions B155B131 B155B131
are required. Otherwise, use the FRU and procedure
Explanation: A card in the system is missing, or its
callouts detailed with the SRC to determine service
VPD data is corrupted.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A4E5 B155A4E5
callouts detailed with the SRC to determine service
Explanation: Validation before update failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1561111 B1561111
callouts detailed with the SRC to determine service
Explanation: There was a slave read error.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A4E6 B155A4E6
callouts detailed with the SRC to determine service
Explanation: Validation after update failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B15738B0 B15738B0
callouts detailed with the SRC to determine service
Explanation: An unrecovered FSI error was detected.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B155A4FD B155A4FD
callouts detailed with the SRC to determine service
Explanation: There was a mismatch in the VPD data. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
206 System reference codes (Bxxx)
B157B10B • B158B484
Response: If this is a tracking event, no service actions
B157B10B B157B10B
are required. Otherwise, use the FRU and procedure
Explanation: No functional direct memory access callouts detailed with the SRC to determine service
(DMA) paths were found. The system cannot boot. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B157E550 B157E550
callouts detailed with the SRC to determine service
Explanation: There was a CEC hardware JTAG failure,
actions.
most likely attributable to a software problem, but it
could also be hardware-related or require further
B157B145 B157B145 support.
Explanation: A chip is missing. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B157F12E B157F12E
B157B90C B157B90C Explanation: An error occurred when the health
checking firmware tried to read a registry value.
Explanation: An engine is missing.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service
actions.
actions.
B158B481 B158B481
B157B919 B157B919
Explanation: Failed to turn on a chip clock.
Explanation: An ADAL JTAG error was encountered.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service
actions.
actions.
B158B482 B158B482
B157E501 B157E501
Explanation: Failed to turn off the chip clock.
Explanation: There was a hardware-detected problem
due to the CEC hardware JTAG. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B158B483 B158B483
B157E504 B157E504 Explanation: Failure of a chip clock operation.
Explanation: A hardware failure was detected in the Response: If this is a tracking event, no service actions
central electronics complex (CEC). are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B158B484 B158B484
Explanation: Unable to get a pointer to the CEC cage.
B157E540 B157E540
Response: If this is a tracking event, no service actions
Explanation: There was a failure most likely are required. Otherwise, use the FRU and procedure
attributable to the CEC clock control hardware, but it callouts detailed with the SRC to determine service
could also be software-related or require further actions.
support.
(B1xx) Reference codes 207
B158B485 • B159A070
B158B485 B158B485 B158E501 B158E501
Explanation: The clock selection value is not Explanation: There was a hardware-detected problem
supported on this system. due to the CEC hardware clock controller.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B158C004 B158C004 B158E504 B158E504
Explanation: CINI has detected a clock failure. Explanation: A hardware failure was detected in the
central electronics complex (CEC).
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B158C005 B158C005
B158E540 B158E540
Explanation: CINI detected a processor clock failure.
Explanation: There was a failure most likely
Response: If this is a tracking event, no service actions
attributable to the CEC JTAG hardware, but it could
are required. Otherwise, use the FRU and procedure
also be software-related or require further support.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B158C670 B158C670
actions.
Explanation: The chip is bad - all processors have
clock errors.
B158E550 B158E550
Response: If this is a tracking event, no service actions
Explanation: There was a CEC hardware clock control
are required. Otherwise, use the FRU and procedure
failure, most likely attributable to a software problem,
callouts detailed with the SRC to determine service
but it could also be hardware-related or require further
actions.
support.
Response: If this is a tracking event, no service actions
B158CC61 B158CC61
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred on an oscillator (clock) callouts detailed with the SRC to determine service
card. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B15911A6 B15911A6
callouts detailed with the SRC to determine service
Explanation: Failed to read a panel attention
actions.
command from the panel.
Response: If this is a tracking event, no service actions
B158CC62 B158CC62
are required. Otherwise, use the FRU and procedure
Explanation: An oscillator (clock) card failover callouts detailed with the SRC to determine service
occurred. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B159A070 B159A070
callouts detailed with the SRC to determine service
Explanation: The panel function is not active.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
208 System reference codes (Bxxx)
B159A0B0 • B15C9537
Response: If this is a tracking event, no service actions
B159A0B0 B159A0B0
are required. Otherwise, use the FRU and procedure
Explanation: The panel was deactivated. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B15A3305 B15A3305
actions.
Explanation: The service processor battery needs to be
replaced.
B159A0B2 B159A0B2
Response: If this is a tracking event, no service actions
Explanation: Too many panels are present in the are required. Otherwise, use the FRU and procedure
system. This is an invalid configuration. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B15AE504 B15AE504
actions.
Explanation: A hardware failure was detected in the
central electronics complex (CEC).
B159A0FC B159A0FC
Response: If this is a tracking event, no service actions
Explanation: More physical control (operator) panels are required. Otherwise, use the FRU and procedure
are in the system than is allowed. This is an invalid callouts detailed with the SRC to determine service
configuration. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B15C104B B15C104B
callouts detailed with the SRC to determine service
Explanation: The PSI link is down. No DMA
actions.
operations are possible.
Response: If this is a tracking event, no service actions
B15A3301 B15A3301
are required. Otherwise, use the FRU and procedure
Explanation: There is a problem with the service callouts detailed with the SRC to determine service
processor hardware time-of-day clock (RTC). It does actions.
not appear to be counting.
Response: If this is a tracking event, no service actions B15C104C B15C104C
are required. Otherwise, use the FRU and procedure
Explanation: Communication paths on the service
callouts detailed with the SRC to determine service
processor side are not enabled to do DMA operations.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B15A3302 B15A3302
callouts detailed with the SRC to determine service
Explanation: An error occurred while writing the actions.
service processor hardware time-of-day clock (RTC).
The service processor hardware may need to be
B15C1050 B15C1050
replaced.
Explanation: The link needs to go through
Response: If this is a tracking event, no service actions
retry/failover.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B15A3303 B15A3303
Explanation: The service procesor time-of-day is
B15C9537 B15C9537
invalid. If the error occurred while reading the service
processor's hardware time-of-day clock (also known as Explanation: An error was detected by the operating
the real time clock), this error indicates that the time of system when communicating with the service
day must be set to a valid time. If the error occurred processor.
while setting the service processor's hardware
time-of-day clock (the RTC), the service processor may Response: If this is a tracking event, no service actions
need to be replaced. are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 209
B15CB10B • B15CE504
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B15CB10B B15CB10B
Explanation: No functional direct memory access
B15CB72A B15CB72A
(DMA) paths were found. The system cannot boot.
Explanation: An error was received when attempting
Response: If this is a tracking event, no service actions
a DMA operation between the service processor and
are required. Otherwise, use the FRU and procedure
the processor.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B15CB202 B15CB202
actions.
Explanation: Informational message: an IAP warning
was issued.
B15CB890 B15CB890
Response: If this is a tracking event, no service actions
Explanation: The PSI link is not active on the service
are required. Otherwise, use the FRU and procedure
processor side after enabling it.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B15CB2DF B15CB2DF
actions.
Explanation: A fatal IAP error occurred.
Response: If this is a tracking event, no service actions B15CB891 B15CB891
are required. Otherwise, use the FRU and procedure
Explanation: The PSI link has errors on the processor
callouts detailed with the SRC to determine service
side after enabling it.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B15CB2E0 B15CB2E0
callouts detailed with the SRC to determine service
Explanation: An IAP error that was not fatal occurred, actions.
or an IAP warning was issued. The system should be
rebooted in slow mode to diagnose this potential
B15CB898 B15CB898
problem.
Explanation: The hypervisor has not handed off the
Response: If this is a tracking event, no service actions
bus; there may be a hardware problem with the
are required. Otherwise, use the FRU and procedure
interrupt.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B15CB718 B15CB718
actions.
Explanation: Unable to find a functional
communication path between the service processor and
B15CE465 B15CE465
the processor. Look at the error logs and guard records
to isolate the failing or missing hardware. Explanation: A PSI link surveillance failure occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B15CB729 B15CB729 B15CE504 B15CE504
Explanation: There was a pattern mismatch during the Explanation: There was a hardware failure due to
DMA test between the service processor and the service processor code.
processor; memory could not be read from or written
Response: If this is a tracking event, no service actions
to correctly.
are required. Otherwise, use the FRU and procedure
210 System reference codes (Bxxx)
B15CF201 • B160E7C3
callouts detailed with the SRC to determine service
B1608A1A B1608A1A
actions.
Explanation: The operation to dynamically load a
library failed.
B15CF201 B15CF201
Response: If this is a tracking event, no service actions
Explanation: A PSI link error was detected.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1608C55 B1608C55
Explanation: Network data was not available.
B15CF20E B15CF20E
Response: If this is a tracking event, no service actions
Explanation: Informational message: No error was
are required. Otherwise, use the FRU and procedure
detected on the processor support interface (PSI) link.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1608CAB B1608CAB
actions.
Explanation: A cable is not plugged properly.
B15EE6ED B15EE6ED Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Service processor (or system controller)
callouts detailed with the SRC to determine service
redundancy is disabled.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1608CAD B1608CAD
callouts detailed with the SRC to determine service
actions. Explanation: The host is only on one network.
Response: If this is a tracking event, no service actions
B16087D2 B16087D2 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A socket error occurred.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1608CB0 B1608CB0
callouts detailed with the SRC to determine service
actions. Explanation: An invalid connection was detected.
Response: If this is a tracking event, no service actions
B16087D4 B16087D4 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A connection error occurred.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B160B73F B160B73F
callouts detailed with the SRC to determine service
actions. Explanation: A power fault was detected.
Response: If this is a tracking event, no service actions
B1608902 B1608902 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The service processor synchronization
actions.
(SINK) interface timed out waiting for a firmware
component to create a synchronization lock.
B160E7C3 B160E7C3
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Unable to open a synchronization file.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 211
B1701002 • B1701011
callouts detailed with the SRC to determine service
B1701002 B1701002
actions.
Explanation: The DMA driver has encountered an
error, and the firmware was not able to determine if the
B170100A B170100A
error was due to a checkstop.
Explanation: The DMA driver has encountered an
Response: If this is a tracking event, no service actions
error due to a hardware checkstop during a read
are required. Otherwise, use the FRU and procedure
operation in the TCE mode.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1701003 B1701003
actions.
Explanation: The DMA driver has encountered an
error, and the firmware was not able to determine if the
B170100C B170100C
error was due to a checkstop.
Explanation: The DMA driver has encountered an
Response: If this is a tracking event, no service actions
error in TCE mode in which a write has worked but a
are required. Otherwise, use the FRU and procedure
read has failed.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1701004 B1701004
actions.
Explanation: The DMA driver has encountered an
error due to a hardware checkstop during a read
B170100D B170100D
operation in the IPL mode.
Explanation: The DMA driver has encountered an
Response: If this is a tracking event, no service actions
error due to a hardware checkstop during a write
are required. Otherwise, use the FRU and procedure
operation in the TCE mode.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1701006 B1701006
actions.
Explanation: The DMA driver has encountered an
error in IPL mode in which a write has worked but a
B170100F B170100F
read has failed.
Explanation: The DMA driver has encountered an
Response: If this is a tracking event, no service actions
unknown error in TCE mode during a write operation.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1701007 B1701007
Explanation: The DMA driver has encountered an
B1701010 B1701010
error due to a hardware checkstop during a write
operation in the IPL mode. Explanation: A DMA adal read returned zero bytes of
data.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1701009 B1701009
B1701011 B1701011
Explanation: The DMA driver has encountered an
unknown error in IPL mode during write operation. Explanation: User-given data length doesn't match the
amount of data being DMA'ed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
212 System reference codes (Bxxx)
B1701012 • B170C011
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1701012 B1701012 B1708505 B1708505
Explanation: A DMA adal write returned zero bytes of Explanation: Failed to create the file name for a new
data. socket.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1701013 B1701013 B170901A B170901A
Explanation: User-given data length doesn't match Explanation: The hypervisor has not allocated enough
with the amount of data being DMA'ed. storage for the data structures being built.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B170102A B170102A B1709020 B1709020
Explanation: Manufacturing test failed because the Explanation: The service processor either retrieved
data being read does not match the data that was invalid data from CEC memory, or there are too many
previously written. FRUs to process.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B170102B B170102B B170902A B170902A
Explanation: Manufacturing test failed because the Explanation: An integrity check failed on data that the
data being read does not match the data that was service processor retrieved from CEC memory.
previously written.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B170B838 B170B838
B170102C B170102C
Explanation: The clocks are in the wrong state for this
Explanation: Manufacturing test for DMA failed while SCOM operation.
writing random data at the host address.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B170C011 B170C011
B1701041 B1701041
Explanation: CINI has detected a plug count greater
Explanation: The operation type was not read or than the limit for the multi-chip module
write.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 213
B170C728 • B1753127
B170C728 B170C728 B175104B B175104B
Explanation: The main storage diagnostics detected a Explanation: The PSI link is down. No DMAs are
special type of uncorrectable error. possible.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B170E501 B170E501 B175104D B175104D
Explanation: There was a hardware-detected problem Explanation: The CEC is not configured properly.
due to a subsystem.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B175105F B175105F
B170E504 B170E504
Explanation: A DMA operation failed, but the
Explanation: A hardware failure was detected in the hypervisor is not accepting messages. In this case,
central electronics complex (CEC). DMAs are invalid so an informational error log is
passed back to the caller.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B170E540 B170E540
B1752411 B1752411
Explanation: There was a failure most likely
attributable to a subsystem, but it might also be Explanation: An error occurred when deactivating the
software-related or require further support. wake-on-LAN hardware.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B170E550 B170E550 B1753126 B1753126
Explanation: There was a software problem, but this Explanation: A request to clear the error/event log
could also be miscellaneous subsystem-related problem has been processed.
or require further support.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1753127 B1753127
B170E560 B170E560
Explanation: Informational message: the error logging
Explanation: The hardware detected a problem that server has been started.
was caused by software. The dump that was taken may
Response: If this is a tracking event, no service actions
need to be analyzed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
214 System reference codes (Bxxx)
B1753130 • B1754201
callouts detailed with the SRC to determine service
B1753130 B1753130
actions.
Explanation: The data synchronization thread on the
error logging server was not started.
B175392F B175392F
Response: If this is a tracking event, no service actions
Explanation: There is a node present that is not under
are required. Otherwise, use the FRU and procedure
surveillance.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1753131 B1753131
actions.
Explanation: The data sync thread was cancelled.
Response: If this is a tracking event, no service actions B175393E B175393E
are required. Otherwise, use the FRU and procedure
Explanation: There was a node controller failover
callouts detailed with the SRC to determine service
request by the user.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1753132 B1753132
callouts detailed with the SRC to determine service
Explanation: Sub-bus reset failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1753940 B1753940
callouts detailed with the SRC to determine service
Explanation: There was a request to disable a note
actions.
controller by the user.
Response: If this is a tracking event, no service actions
B1753133 B1753133
are required. Otherwise, use the FRU and procedure
Explanation: The role changed callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1753943 B1753943
actions.
Explanation: There was an error in the ping
acknowledgement received.
B17531FF B17531FF
Response: If this is a tracking event, no service actions
Explanation: An error occurred in the error logging are required. Otherwise, use the FRU and procedure
firmware. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B175394F B175394F
actions.
Explanation: A node controller surveillance error
occurred.
B1753909 B1753909
Response: If this is a tracking event, no service actions
Explanation: The IPL is being terminated due to the are required. Otherwise, use the FRU and procedure
loss of the primary node controller. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1754201 B1754201
actions.
Explanation: A problem was detected on an internal
I2C bus.
B1753918 B1753918
Response: If this is a tracking event, no service actions
Explanation: There was an error due to the loss of are required. Otherwise, use the FRU and procedure
surveillance when activating a node controller. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 215
B1754202 • B175B16A
B1754202 B1754202 B1758C03 B1758C03
Explanation: RDAL handle failure Explanation: A null pointer was passed to a function.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1754203 B1754203 B1758C0B B1758C0B
Explanation: An error occured, but FFDC could not be Explanation: Unable to verify the type of system
extracted enclosure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1754204 B1754204 B1758C0D B1758C0D
Explanation: FFDC data was extracted, but the unlock Explanation: Unable to determine the enclosure type.
failed
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B175A043 B175A043
B175440B B175440B
Explanation: An incorrect data size was received for
Explanation: There was a hard socket failure the function action that was requested.
disconnection.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B175B13F B175B13F
B175440F B175440F
Explanation: The SMP cables are plugged incorrectly.
Explanation: Failed to write data to a socket.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B175B16A B175B16A
B1757026 B1757026
Explanation: The IVPD data for a cable does not
Explanation: The system power interface (SPIF) server match any known cable types; check for improperly
thread was canceled while sending a command to the plugged cables and correct any problems that are
system power control network (SPCN). found.
Response: If this is a tracking event, no service actions
B1758504 B1758504 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: These SRCs are added to the primary
actions.
SRC to show control flow.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
216 System reference codes (Bxxx)
B175B170 • B175E01C
callouts detailed with the SRC to determine service
B175B170 B175B170
actions.
Explanation: The SMP cables are not plugged in
securely.
B175D003 B175D003
Response: If this is a tracking event, no service actions
Explanation: This SRC is reserved.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B175B17F B175B17F
Explanation: The configuration was degraded due to
B175D010 B175D010
SMP cabling
Explanation: The service processor is about to be reset
Response: If this is a tracking event, no service actions
with toolreset.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B175B718 B175B718
Explanation: Unable to find a functional
B175E019 B175E019
communication path between the service processor and
the processor. Look at the error logs and guard records Explanation: Communications failure with RETAIN.
to isolate the failing or missing hardware.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B175E01A B175E01A
B175B838 B175B838
Explanation: The system called home to the IBM
Explanation: Internal software error: hardware in service center. This entry tracks the successful
incorrect state for attempted operation. communication with the RETAIN server. Errorlog
information shows the PMH number in the user details
Response: If this is a tracking event, no service actions
section. with the RETAIN server. Errorlog information
are required. Otherwise, use the FRU and procedure
shows the PMH number in the user details section.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B175C01D B175C01D
actions.
Explanation: CINI has detected a user-overridden
logical memory block (LMB) size that is not valid for
B175E01B B175E01B
the systems memory size. The CINI will instead use
the default LMB size. Explanation: Service center did not respond as
expected.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B175CA10 B175CA10
B175E01C B175E01C
Explanation: Resources that had been guarded out
were returned to the functional state to allow the Explanation: The system failed to log into the IBM
system boot to continue. service center.
Response: If this is a tracking event, no service actions Response: Verify system is entitled to RETAIN/IPAP
are required. Otherwise, use the FRU and procedure service. Verify call home settings are correct. perform
call home test and examine error log for other fialures.
(B1xx) Reference codes 217
B175E01D • B1763225
Problem determination: Verify that the correct are required. Otherwise, use the FRU and procedure
hemisphere data has been programmed. Also confirm callouts detailed with the SRC to determine service
that the system is entitled for service via the IBM actions.
service center.
B175E580 B175E580
B175E01D B175E01D
Explanation: Processor runtime diagnostics (PRD) has
Explanation: Verify that the system is entitled to found an invalid attention type in the attention data.
service and is registered with RETAIN.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B175F109 B175F109
B175E501 B175E501
Explanation: The threshold of new NVRAM errors
Explanation: There was a hardware-detected problem was reached.
due to an unknown subsystem.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1762A11 B1762A11
B175E504 B175E504
Explanation: The TPMD (thermal/power management
Explanation: There was a hardware failure, but the device) failed to communicate with a processor over
cause cannot be determined. the I2C bus.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B175E540 B175E540 B1763221 B1763221
Explanation: There was a failure most likely Explanation: Informational message: The hyperboot
attributable to something in the hardware, but could capability registry entry was changed to capable and
also be software-related or require further support. the IPL speed to hyper because NVRAM was reset.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B175E550 B175E550 B1763224 B1763224
Explanation: There was a software problem from an Explanation: The service processor rebooted to
unknown subsystem; it will require further support. Standby on iplp/NextSide.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B175E560 B175E560 B1763225 B1763225
Explanation: The hardware detected a problem that Explanation: The hyperboot capability setting was
was caused by an unknown entity. The dump that was changed to capable.
taken may need to be analyzed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
218 System reference codes (Bxxx)
B1763227 • B1763437
callouts detailed with the SRC to determine service
B1763321 B1763321
actions.
Explanation: The service processor's time-of-day has
changed. The error log detail contains information that
B1763227 B1763227
is useful in analyzing time change events.
Explanation: The iplp/IplSpeedOverride and
Response: If this is a tracking event, no service actions
iplp/CurrentIplSpeed values are being changed to the
are required. Otherwise, use the FRU and procedure
input speed Value.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1763324 B1763324
actions.
Explanation: The timed-power-on function was
disabled when the service processor discovered that its
B1763231 B1763231
time-of-day was invalid.
Explanation: This SRC is reserved.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1763325 B1763325
B1763303 B1763303
Explanation: Invalid data was received by a service
Explanation: The service processor's time-of-day clock processor time-of-day process.
is invalid. This error indicates that the time-of-day
Response: If this is a tracking event, no service actions
clock must be set to a correct time before the next
are required. Otherwise, use the FRU and procedure
system IPL.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B176332B B176332B
actions.
Explanation: An error was returned from a function.
B176330F B176330F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned from the real time
callouts detailed with the SRC to determine service
clock ADAL.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1763435 B1763435
callouts detailed with the SRC to determine service
actions. Explanation: Write the IPL type.
Response: If this is a tracking event, no service actions
B1763320 B1763320 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Internal service processor time-of-day
actions.
data was initialized to a default value. This may be due
to an NVRAM battery or service processor replaceme
nt, or because the service processor was reset to factory B1763437 B1763437
defaults.
Explanation: Tool reset has been requested.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service
actions.
actions.
(B1xx) Reference codes 219
B1763438 • B176402B
B1763438 B1763438 B1763892 B1763892
Explanation: A power-cycle reset request was Explanation: The configuration file key is not valid.
received.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B17638A0 B17638A0
B1763441 B1763441
Explanation: frum detected a bad fsi link.
Explanation: The fspipltype variable's value was
Response: If this is a tracking event, no service actions
modified to modified to keep the primary and
are required. Otherwise, use the FRU and procedure
secondary service processors' roles in sync.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B17638B2 B17638B2
actions.
Explanation: A failover could not be initiated because
rmgrBackupFailoverCapability indicates that it is not
B1763833 B1763833
allowed.
Explanation: A duplicate add event was found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1764007 B1764007
B1763834 B1763834
Explanation: Unable to open the dhclient.pid file.
Explanation: A duplicate removal event was found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1764009 B1764009
B1763839 B1763839
Explanation: ipconfig failed.
Explanation: There was an error during a forced
Response: If this is a tracking event, no service actions
device addition.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B176400A B176400A
Explanation: There was a DHCP link error.
B1763850 B1763850
Response: If this is a tracking event, no service actions
Explanation: The IOMUX (I/O multiplexer)
are required. Otherwise, use the FRU and procedure
configuration is not valid.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B176402B B176402B
actions.
Explanation: Unable to open the DHCP client leases
file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
220 System reference codes (Bxxx)
B176402C • B176440F
callouts detailed with the SRC to determine service
B1764032 B1764032
actions.
Explanation: The IP address for the node controller
was not assigned based on the node ID and side but is
B176402C B176402C
from a pool.
Explanation: There was an error in the DHCP lease
Response: If this is a tracking event, no service actions
file information.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B176410A B176410A
Explanation: RDAL's ERC connection failed.
B176402E B176402E
Response: If this is a tracking event, no service actions
Explanation: Unable to check to see if the link is up or
are required. Otherwise, use the FRU and procedure
not.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B176410F B176410F
actions.
Explanation: RDAL's ERC write failed.
B176402F B176402F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Unable to read DHCP failure tracking
callouts detailed with the SRC to determine service
registry.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1764120 B1764120
callouts detailed with the SRC to determine service
actions. Explanation: I nvalid AIO parameters were passed to
rdal_aio_ctx_submit.
B1764030 B1764030 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: When the node controller was booting, it
callouts detailed with the SRC to determine service
was unable to obtain an IP address for 30 minutes or
actions.
more. However, the DHCP client was able to get an IP
address and the controller booted successfully. A dump
was generated. B1764121 B1764121
Response: If this is a tracking event, no service actions Explanation: The RDAL ERC object was not found.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B1764031 B1764031
Explanation: When the node controller was booting, B176440B B176440B
tftp failed multiple times. It then recovered and the
Explanation: An ERC hard failure was recorded.
node controller booted successfully. A dump was
generated. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B176440F B176440F
Explanation: The BFMK ERC object was not found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 221
B1766035 • B1768B01
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1766035 B1766035
Explanation: The IPL type was written to the registry.
B17684A7 B17684A7
Explanation: A failure from the
B1768453 B1768453
nets_process_sess_cmd() function occurred during a
Explanation: There was an error when closing the serial-over-LAN session. The message was received
session. from a storage subsystem but failed to process.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1768478 B1768478 B17684A8 B17684A8
Explanation: An error occurred in the SSL part of the Explanation: Informational message: Serial over LAN
connection (SOL) processing was requested.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B176847D B176847D B1768902 B1768902
Explanation: An error occurred when getting the Explanation: A time-out occurred because the file does
socket options. not exist.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1768497 B1768497 B1768A1A B1768A1A
Explanation: There was an error when setting the Explanation: The loading of a shared library has
network interface. failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B17684A0 B17684A0 B1768A1B B1768A1B
Explanation: Unable to read the registry value that Explanation: There was a library DL synchronization
indicates whether or not the network is available. error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B17684A1 B17684A1 B1768B01 B1768B01
Explanation: Return from the error log indicates that Explanation: Informational message: cannot open a
the connection to a storage subsystem was not made device
and the connection timed out.
Response: If this is a tracking event, no service actions
222 System reference codes (Bxxx)
B1768B07 • B1768B35
are required. Otherwise, use the FRU and procedure
B1768B14 B1768B14
callouts detailed with the SRC to determine service
actions. Explanation: Unable to set the hostname.
Response: If this is a tracking event, no service actions
B1768B07 B1768B07 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A system call was made.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1768B18 B1768B18
callouts detailed with the SRC to determine service
actions. Explanation: Unable to write to a file.
Response: If this is a tracking event, no service actions
B1768B0C B1768B0C are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Informational message: failed to set up
actions.
the FSI adapter; the sibling is not present.
Response: If this is a tracking event, no service actions
B1768B1E B1768B1E
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: A network reset was issued as the pin
actions. value changed.
Response: If this is a tracking event, no service actions
B1768B0D B1768B0D are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Informational message: failed to set up
actions.
the FSI adapter; the sibling is not present.
Response: If this is a tracking event, no service actions
B1768B1F B1768B1F
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: A network reset was issued as the pin
actions. value changed.
Response: If this is a tracking event, no service actions
B1768B0E B1768B0E are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: IFCONFIG mailbox 2 failure.
actions.
Response: If this is a tracking event, no service actions
are required. IBM Otherwise, use the FRU and
B1768B23 B1768B23
procedure callouts detailed with the SRC to determine
service actions. Explanation: Informational message:
FrumWaitDeviceList timed out; cannot open the device.
B1768B0F B1768B0F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to set up the FSI adapter; the
callouts detailed with the SRC to determine service
sibling is not present.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1768B2E B1768B2E
callouts detailed with the SRC to determine service
actions. Explanation: A software open error occurred.
Response: If this is a tracking event, no service actions
B1768B13 B1768B13 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Failed to configure the IP address.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1768B35 B1768B35
callouts detailed with the SRC to determine service
actions. Explanation: A VLAN remove operation was
performed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 223
B1768B36 • B1769006
callouts detailed with the SRC to determine service
B1768B4E B1768B4E
actions.
Explanation: There was a failure when creating the
route.
B1768B36 B1768B36
Response: If this is a tracking event, no service actions
Explanation: The network configuration data from the
are required. Otherwise, use the FRU and procedure
user was incorrect.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1768BC1 B1768BC1
actions.
Explanation: Informational message: the service
processor has been rebooted by the CMM due to an
B1768B3B B1768B3B
I2C communications failure or a security exception in
Explanation: The device cannot be opened. phase 1.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1768B43 B1768B43 B1768BC2 B1768BC2
Explanation: An error occurred when getting an IP Explanation: Informational message: the service
address. processor has been rebooted by the CMM due to a
communication failure or security exception in phase 2
Response: If this is a tracking event, no service actions or 3.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1768B44 B1768B44
Explanation: An ARP send operation was performed. B1768BC3 B1768BC3
Response: If this is a tracking event, no service actions Explanation: Informational message: the service
are required. Otherwise, use the FRU and procedure processor lost connection to the CMM security
callouts detailed with the SRC to determine service component and rebooted to recover the secure state.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1768B46 B1768B46 callouts detailed with the SRC to determine service
Explanation: The mailbox route was rejected. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1769004 B1769004
callouts detailed with the SRC to determine service Explanation: A dump request was rejected by the
actions. service processor. It is possible that a dump was
already done or in progress at the time of the request.
B1768B47 B1768B47 Response: If this is a tracking event, no service actions
Explanation: A DHCP failure occurred. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1769006 B1769006
Explanation: An internal service processor error
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
Response: If this is a tracking event, no service actions
224 System reference codes (Bxxx)
B1769007 • B1769052
are required. Otherwise, use the FRU and procedure
B1769014 B1769014
callouts detailed with the SRC to determine service
actions. Explanation: An internal service processor error
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
B1769007 B1769007
Response: If this is a tracking event, no service actions
Explanation: An internal service processor error
are required. Otherwise, use the FRU and procedure
occurred. Check for system firmware updates and
callouts detailed with the SRC to determine service
apply if available before replacing the service processor.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1769028 B1769028
callouts detailed with the SRC to determine service
actions. Explanation: An error occurred while trying to write
data to CEC memory.
B1769008 B1769008 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An internal service processor error
callouts detailed with the SRC to determine service
occurred. Check for system firmware updates and
actions.
apply if available before replacing the service processor.
Response: If this is a tracking event, no service actions
B176902A B176902A
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: An integrity check failed on data that the
actions. service processor retrieved from CEC memory.
Response: If this is a tracking event, no service actions
B176900D B176900D are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An internal service processor error
actions.
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
B1769042 B1769042
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: An error log was generated at the end of
callouts detailed with the SRC to determine service the memory test. This indicates that non-terminating
actions. errors were generated during the test.
Response: If this is a tracking event, no service actions
B176900E B176900E are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An internal service processor error
actions.
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
B176904F B176904F
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: A secondary SRC was added to show
callouts detailed with the SRC to determine service control flow. The primary SRC indicates the actual
actions. error.
Response: If this is a tracking event, no service actions
B1769010 B1769010 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An internal service processor error
actions.
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
B1769052 B1769052
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: The memory test completed successfully.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 225
B176905C • B176B740
B176905C B176905C B176B2DF B176B2DF
Explanation: Terminations have been disabled so Explanation: A fatal IAP error occurred.
AVP-related errors will simply cause reboots.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B176B507 B176B507
B176A40F B176A40F
Explanation: Keys were not found in a table. This
Explanation: Unable to open the directory into which could be any table and any keys, so the details in the
this data file should have gone. error log entry are very important in debugging this
type of error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B176A41C B176A41C
B176B70C B176B70C
Explanation: Failed to find the input keyword or
record in the module VPD. Explanation: An internal firmware error occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B176B105 B176B105 B176B739 B176B739
Explanation: The processor core is not functioning, or Explanation: There was an error when forcing a lock.
it cannot be detected.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B176B73F B176B73F
B176B202 B176B202
Explanation: The CEC encountered a power line
Explanation: Informational message: an IAP warning disturbance.
was issued.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B176B740 B176B740
B176B2DE B176B2DE
Explanation: The secondary service processor has
Explanation: The elastic interface alignment procedure detected missing devices.
never completed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
226 System reference codes (Bxxx)
B176B836 • B176B91B
B176B836 B176B836 B176B914 B176B914
Explanation: The parent chip returned a null value for Explanation: An error was encountered when the
ruleCommonFacade. firmware tried to close the SCAN/SCOM device driver.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B176B838 B176B838 B176B915 B176B915
Explanation: The clocks are in the wrong state for this Explanation: The SCOM device driver is unable to
SCOM operation. scan the data out from the ID register.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B176B87D B176B87D B176B916 B176B916
Explanation: An operation was attempted on a Explanation: The firmware encountered an internal
non-functional unit. problem: a chip doesnt have a valid scan interface.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B176B887 B176B887 B176B917 B176B917
Explanation: Internal software information log entry; Explanation: An ADAL SCOM error was encountered.
informationl message only.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B176B918 B176B918
B176B90C B176B90C
Explanation: An ADAL PSI error was encountered.
Explanation: An engine is missing.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B176B919 B176B919
B176B913 B176B913
Explanation: An ADAL JTAG error was encountered.
Explanation: The firmware encountered an error when
Response: If this is a tracking event, no service actions
opening an ADAL (access device abstraction layer) to a
are required. Otherwise, use the FRU and procedure
chip.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B176B91B B176B91B
actions.
Explanation: There was an ADAL mailbox error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 227
B176B920 • B176B9B1
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B176B920 B176B920
B176B94A B176B94A
Explanation: The firmware encountered an error when
shifting a command into a chip as part of a scan Explanation: The SCAN/SCOM device driver
operation. encountered an error when trying to read an internal
register on a chip.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B176B924 B176B924
B176B963 B176B963
Explanation: The firmware timed out when waiting
for a JTAG lock to be granted by the JTAG ADAL Explanation: The firmware detected that the value
(access device abstraction layer). scanned out from the instruction status register of the
chip is invalid.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B176B940 B176B940
B176B964 B176B964
Explanation: The SCOM device driver encountered an
error when trying to read the status register of a chip. Explanation: The firmware detected an SCOM
attention raised from the specified chip.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B176B941 B176B941
B176B967 B176B967
Explanation: The firmware encountered an error when
trying to read data from a ring inside a chip. Explanation: The firmware detected either a parity
error or an invalid command attention raised from the
Response: If this is a tracking event, no service actions
specified chip.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B176B942 B176B942
Explanation: The firmware encountered an error when
B176B982 B176B982
trying to read data from an SCOM register inside a
chip. Explanation: The firmware has detected an SCOM
attention raised from the specified chip.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B176B945 B176B945
B176B9B1 B176B9B1
Explanation: The SCOM device driver encountered an
error when trying to read a GP (general purpose) Explanation: The ivJtagEnginePtr pointer is NULL.
register of a chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
228 System reference codes (Bxxx)
B176B9D8 • B176E501
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B176B9D8 B176B9D8 B176C742 B176C742
Explanation: HCSI_P7_PCB_PIB_TIME_OUT Explanation: Summary errorlog: this error log
indicates that there is one or more memory AVPS test
Response: If this is a tracking event, no service actions
failures.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B176C01D B176C01D
Explanation: CINI has detected a user-overridden
B176C74A B176C74A
loginal memory block (LMB) size that is not valid for
the system's memory size. The CINI will instead use Explanation: A summary error log was created to
the default LMB size. terminate the IPL.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B176C709 B176C709 B176C74B B176C74B
Explanation: The number of memory errors detected Explanation: Summary errorlog: this error log
by main storage diagnostics exceeded the indicates that there is one or more L2 AVPS test
manufacturing threshold. failures.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B176C70A B176C70A B176C751 B176C751
Explanation: A memory-preserving IPL occurred, so a Explanation: Informational message: The memory test
summary error log was created to terminate the IPL, case completed successfully.
and that previous logs that pointed to hardware or
Response: If this is a tracking event, no service actions
software failures had been created and committed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B176D401 B176D401
Explanation: An unexpected signal was caught.
B176C729 B176C729
Response: If this is a tracking event, no service actions
Explanation: One or more of the wrap tests failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B176E501 B176E501
Explanation: There was a hardware-detected
B176C740 B176C740
informational message of unknown origin. No action is
Explanation: The L2 AVPS test has completed required.
successfully (informational message).
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 229
B176E504 • B180E560
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B176E504 B176E504
Explanation: A hardware failure was detected in the
B180E501 B180E501
central electronics complex (CEC).
Explanation: There has been a hardware-detected
Response: If this is a tracking event, no service actions
problem due to the firmware subsystem.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B176E540 B176E540
Explanation: There was an informational message due
B180E504 B180E504
to hardware, but could also be software-related. No
further action is required. Explanation: A hardware failure was detected in the
central electronics complex (CEC).
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B176E550 B176E550
B180E540 B180E540
Explanation: There was a software problem; this is an
informational message. No action is required. Explanation: There was a failure most likely
attributable to the firmware subsystem, but it could
Response: If this is a tracking event, no service actions
also be software-related or require further support.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B176E658 B176E658
Explanation: This indicates the requested action failed
B180E550 B180E550
because the sibling service processor is not in the
working state. Explanation: There was a firmware subsystem
problem, but it could also be hardware-related or
Response: If this is a tracking event, no service actions
require further support.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B17BE434 B17BE434
Explanation: This error log entry is generated when
B180E560 B180E560
the hypervisor fails to send its heartbeat message
within the allotted time. Explanation: The hardware detected a problem that
was caused by a firmware component. The dump that
Response: If this is a tracking event, no service actions
was taken may need to be analyzed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B17CE433 B17CE433
Explanation: This error log entry is generated when
the HMC fails to send its heartbeat message within the
allotted time. The reason could be network issues, or
the Ethernet cable is disconnected.
230 System reference codes (Bxxx)
B180E580 • B181100D
callouts detailed with the SRC to determine service
B180E580 B180E580
actions.
Explanation: There was a failure in the service
processor firmware.
B1811007 B1811007
Response: If this is a tracking event, no service actions
Explanation: The DMA driver has encountered an
are required. Otherwise, use the FRU and procedure
error due to a hardware checkstop during a write
callouts detailed with the SRC to determine service
operation in IPL mode. Look for an error log entry
actions.
generated by PRD (processor runtime diagnostics). (The
checkstop needs to be analyzed to determine the root
B181000A B181000A cause of the failure. The DMA failure is a secondary
effect of the hardware checkstop.)
Explanation: "Malformed" SRC
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service
actions.
actions.
B1811009 B1811009
B1811002 B1811002
Explanation: The DMA driver has encountered an
Explanation: The DMA driver has encountered an
unknown error during a write operation. The error
error; unable to determine if a hardware checkstop has
information needs to be analyzed to determine the
occurred.
cause. If the first DMA operation always fails with this
Response: If this is a tracking event, no service actions error, it is probably a hardware problem.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B1811003 B1811003
Explanation: The DMA driver has encountered an B181100A B181100A
error; unable to determine if a hardware checkstop has
Explanation: The DMA driver has encountered an
occurred.
error due to a hardware checkstop during a read
Response: If this is a tracking event, no service actions operation. (The checkstop needs to be analyzed to
are required. Otherwise, use the FRU and procedure determine the root cause of the failure. The DMA
callouts detailed with the SRC to determine service failure is a secondary effect of the hardware checkstop.)
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1811004 B1811004 callouts detailed with the SRC to determine service
actions.
Explanation: The DMA driver has encountered an
error due to a hardware checkstop during a read
operation. (The checkstop needs to be analyzed to B181100C B181100C
determine the root cause of the failure. The dma failure
Explanation: The DMA driver has encountered an
is a secondary effect of the hardware checkstop.)
unknown error during a read operation. The error
Response: If this is a tracking event, no service actions information needs to be analyzed to determine the
are required. Otherwise, use the FRU and procedure cause.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811006 B1811006 actions.
Explanation: The DMA driver has encountered an
unknown error during a read operation. The error B181100D B181100D
information needs to be analyzed to determine the
Explanation: The DMA driver has encountered an
cause.
error due to a hardware checkstop during a write
Response: If this is a tracking event, no service actions operation in TCE mode. Look for an error log entry
are required. Otherwise, use the FRU and procedure generated by PRD (processor runtime diagnostics). (The
(B1xx) Reference codes 231
B181100F • B1811022
checkstop needs to be analyzed to determine the root
B1811014 B1811014
cause of the failure. The DMA failure is a secondary
effect of the hardware checkstop.) Explanation: The DMA driver could not be opened.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181100F B181100F B181101B B181101B
Explanation: The DMA driver has encountered an Explanation: The DMA user attempted a DMA read
unknown error during a write operation. The error with a length of zero.
information needs to be analyzed to determine the
Response: If this is a tracking event, no service actions
cause.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181101C B181101C
Explanation: The DMA user attempted a DMA write
B1811010 B1811010
with a length of zero.
Explanation: A read was attempted, but the DMA
Response: If this is a tracking event, no service actions
driver returned zero bytes of data.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181101D B181101D
Explanation: DMA user provided NULL as an
B1811011 B1811011
address.
Explanation: The amount of data being transferred by
Response: If this is a tracking event, no service actions
DMA does not match the length passed in by the user.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181101E B181101E
Explanation: NULL was received by a function as the
B1811012 B1811012
service processor's (or system controller's) address.
Explanation: A write operation was attempted, but the
Response: If this is a tracking event, no service actions
DMA driver returned zero bytes of data.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1811022 B1811022
Explanation: The DMA user attempted a DMA during
B1811013 B1811013
a window in which DMAs are not available.
Explanation: The amount of data being transferred by
Response: If this is a tracking event, no service actions
DMA does not match the length passed in by the user.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
232 System reference codes (Bxxx)
B1811023 • B1811037
B1811023 B1811023 B1811030 B1811030
Explanation: The sbcu/BusController register did not Explanation: Unable to read registry value.
contain one of the expected values.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1811031 B1811031
B1811027 B1811027
Explanation: This is a DMA code error. One thread is
Explanation: The CEC is powering off. There has been overwriting another.
a power off just before, or during, the DMA operation.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1811032 B1811032
B1811028 B1811028
Explanation: The timer returned an unknown error.
Explanation: Manufacturing test failed because
Response: If this is a tracking event, no service actions
/dev/urandom could not be opened.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1811033 B1811033
Explanation: Chic call returned an error.
B1811029 B1811029
Response: If this is a tracking event, no service actions
Explanation: Manufacturing test failed because
are required. Otherwise, use the FRU and procedure
/dev/urandom could not be read.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811034 B1811034
actions.
Explanation: The chic client thread failed to collect
DMA error data.
B181102D B181102D
Response: If this is a tracking event, no service actions
Explanation: The chic client thread timed out trying to
are required. Otherwise, use the FRU and procedure
collect DMA error data.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811036 B1811036
actions.
Explanation: Manufacturing test failed because of
incorrect DMA mode.
B181102E B181102E
Response: If this is a tracking event, no service actions
Explanation: The event management constructor
are required. Otherwise, use the FRU and procedure
failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811037 B1811037
actions.
Explanation: Chic client thread that was supposed to
collect DMA error data encountered an error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 233
B1811039 • B181104B
callouts detailed with the SRC to determine service
B1811041 B1811041
actions.
Explanation: Dmae detected an unexpected event.
B1811039 B1811039 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Svpd call returned an error.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811042 B1811042
actions.
Explanation: The spif/PowerState register is
undefined.
B181103A B181103A
Response: If this is a tracking event, no service actions
Explanation: Svpd call returned an error.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1811043 B1811043
Explanation: DMAE could not determine if the CEC
B181103B B181103B
was powering off.
Explanation: The current resource ID did not match
Response: If this is a tracking event, no service actions
the list of available resource IDs.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1811045 B1811045
Explanation: Time out waiting for CEC debug data.
B181103C B181103C
Response: If this is a tracking event, no service actions
Explanation: The DMA path could not be determined.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1811047 B1811047
Explanation: A CEC data processing operation failed.
B181103D B181103D
Response: If this is a tracking event, no service actions
Explanation: DMA paths were found, but none of
are required. Otherwise, use the FRU and procedure
them was marked as the primary path.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811048 B1811048
actions.
Explanation: Unable to interpret the
first-failure-data-capture (FFDC) data.
B1811040 B1811040
Response: If this is a tracking event, no service actions
Explanation: The DMA user provided an invalid
are required. Otherwise, use the FRU and procedure
address.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181104B B181104B
actions.
Explanation: PSI link is down.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
234 System reference codes (Bxxx)
B181104C • B181105A
callouts detailed with the SRC to determine service
B1811054 B1811054
actions.
Explanation: The service processor is trying to write a
read-only or read a write-only page.
B181104C B181104C
Response: If this is a tracking event, no service actions
Explanation: Communication paths on the service
are required. Otherwise, use the FRU and procedure
processor side are not enabled to do DMA operations.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811055 B1811055
actions.
Explanation: There is a problem in the device driver
code.
B181104D B181104D
Response: If this is a tracking event, no service actions
Explanation: The CEC is not configured to do DMA
are required. Otherwise, use the FRU and procedure
operations.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811056 B1811056
actions.
Explanation: The operation was cancelled by the
caller.
B1811050 B1811050
Response: If this is a tracking event, no service actions
Explanation: The link needs to go through a reset,
are required. Otherwise, use the FRU and procedure
then failover.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811057 B1811057
actions.
Explanation: A function call failed.
B1811051 B1811051 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Software detected a timeout.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811058 B1811058
actions.
Explanation: Invalid HOM node information was
received.
B1811052 B1811052
Response: If this is a tracking event, no service actions
Explanation: A DMA was attempted with an invalid
are required. Otherwise, use the FRU and procedure
address.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181105A B181105A
actions.
Explanation: A component name of NULL was passed
into a function.
B1811053 B1811053
Response: If this is a tracking event, no service actions
Explanation: A DMA was attempted using an invalid
are required. Otherwise, use the FRU and procedure
TCE token.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 235
B181105C • B1811121
B181105C B181105C B1811104 B1811104
Explanation: Corrupted data was sent to the service Explanation: Failed to close the master I2C device
processor or system controller without an error being driver.
flagged.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1811110 B1811110
B181105D B181105D
Explanation: Failed to open the slave I2C device
Explanation: Corrupted data from memory was sent driver.
to the service processor without an indication that is
Response: If this is a tracking event, no service actions
was corrupted.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1811111 B1811111
Explanation: There was a slave read error.
B1811060 B1811060
Response: If this is a tracking event, no service actions
Explanation: The user passed in a component name of
are required. Otherwise, use the FRU and procedure
NULL.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811113 B1811113
actions.
Explanation: Failed to close the slave I2C device
driver.
B1811101 B1811101
Response: If this is a tracking event, no service actions
Explanation: Failed to open the master I2C device
are required. Otherwise, use the FRU and procedure
driver.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811120 B1811120
actions.
Explanation: An invalid parameter was passed into
the function.
B1811102 B1811102
Response: If this is a tracking event, no service actions
Explanation: Failed to configure the master I2C device
are required. Otherwise, use the FRU and procedure
driver.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811121 B1811121
actions.
Explanation: The panel attention command that was
received did not have a valid checksum.
B1811103 B1811103
Response: If this is a tracking event, no service actions
Explanation: Failed to write to the panel via the
are required. Otherwise, use the FRU and procedure
master I2C device driver.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
236 System reference codes (Bxxx)
B1811122 • B1811155
B1811122 B1811122 B1811150 B1811150
Explanation: The panel attention command that was Explanation: Failed to get the possible resource
received was not valid because the "press and release" identities of all the panels in the system.
button sequence was violated, or an invalid button
Response: If this is a tracking event, no service actions
action was received.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1811151 B1811151
Explanation: No panels may be installed in this
B1811130 B1811130
system according to VPD.
Explanation: Failed to lock the mutex.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1811152 B1811152
B1811131 B1811131
Explanation: Failed to determine if the panel is
Explanation: Failed to stop the execution of the thread present or not.
holding the mutex.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1811153 B1811153
B1811132 B1811132
Explanation: An error occurred when getting the
Explanation: Failed to lock the mutex with a timeout. number of panel resource IDs that may be installed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1811133 B1811133 B1811154 B1811154
Explanation: Failed to unlock the mutex. Explanation: An error occurred getting the master and
slave I2C device paths and the panel I2C device
Response: If this is a tracking event, no service actions
address.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1811140 B1811140
Explanation: Failed to read a value from a registry.
B1811155 B1811155
Response: If this is a tracking event, no service actions
Explanation: No master I2C device was found.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 237
B18111A0 • B1811304
B18111A0 B18111A0 B18111A6 B18111A6
Explanation: Failed to send the internal scroll Explanation: Failed to read a panel attention
command to the panel. command from the panel.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18111A1 B18111A1 B1811300 B1811300
Explanation: Failed to send the soft reset command to Explanation: There was a problem in the way the
the panel. function was called, or it an invalid parameter was
passed to it.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18111A2 B18111A2
B1811301 B1811301
Explanation: Failed to send the display data write
command to the panel. Explanation: An invaled attribute was specified in an
attribute parameter.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18111A3 B18111A3
B1811302 B1811302
Explanation: Failed to send the lamp test command to
the panel. Explanation: An invalid address list was specified in
the address list parameter.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18111A4 B18111A4
B1811303 B1811303
Explanation: Failed to send the button control
command to the panel. Explanation: An errror was encountered while trying
to detect the SVPD read mode.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18111A5 B18111A5
B1811304 B1811304
Explanation: Failed to send the LED control command
to the panel. Explanation: The mode is unknown.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
238 System reference codes (Bxxx)
B1811305 • B1811314
B1811305 B1811305 B181130D B181130D
Explanation: An error was encountered by the Explanation: A first-failure-data-capture deadlock was
external library interface. encountered.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1811306 B1811306 B181130E B181130E
Explanation: The external library interface received a Explanation: Failed to configure the I2C bus.
zero-size data length from the
Response: If this is a tracking event, no service actions
svpd_read_data_persistancy interface.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181130F B181130F
Explanation: First-failure-data-capture unlock failed.
B1811307 B1811307
Response: If this is a tracking event, no service actions
Explanation: A non-null value was detected in the
are required. Otherwise, use the FRU and procedure
data address pointed to by the data address pointer
callouts detailed with the SRC to determine service
parameter; a null pointer is required.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1811310 B1811310
callouts detailed with the SRC to determine service
actions. Explanation: First-failure-data-capture failed.
Response: If this is a tracking event, no service actions
B1811308 B1811308 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An error was encountered by the
actions.
external library interface.
Response: If this is a tracking event, no service actions
B1811312 B1811312
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to read from an I2C device.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181130B B181130B callouts detailed with the SRC to determine service
actions.
Explanation: Failed to open an I2C device.
Response: If this is a tracking event, no service actions
B1811313 B1811313
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to seek on an I2C ADAL handle.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181130C B181130C callouts detailed with the SRC to determine service
actions.
Explanation: Failed to open an I2C device.
Response: If this is a tracking event, no service actions
B1811314 B1811314
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to write to an I2C device.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 239
B1811315 • B1811327
callouts detailed with the SRC to determine service
B1811315 B1811315
actions.
Explanation: Invalid device information was passed to
the IVPD library.
B1811322 B1811322
Response: If this is a tracking event, no service actions
Explanation: An invalid operation was specified.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1811316 B1811316
Explanation: Failed to close an I2C RDAL handle.
B1811323 B1811323
Response: If this is a tracking event, no service actions
Explanation: The first level of basic input parameter
are required. Otherwise, use the FRU and procedure
validation failed.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811317 B1811317
actions.
Explanation: Failed to close an I2C ADAL handle.
Response: If this is a tracking event, no service actions B1811324 B1811324
are required. Otherwise, use the FRU and procedure
Explanation: The process message request data size is
callouts detailed with the SRC to determine service
invalid.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1811318 B1811318
callouts detailed with the SRC to determine service
Explanation: An I2C bus node was not found. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1811325 B1811325
callouts detailed with the SRC to determine service
Explanation: There was insufficient data in the process
actions.
message request.
Response: If this is a tracking event, no service actions
B1811319 B1811319
are required. Otherwise, use the FRU and procedure
Explanation: An "invalid sub-bus" error was returned callouts detailed with the SRC to determine service
by the hub expansion processor. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1811326 B1811326
callouts detailed with the SRC to determine service
Explanation: There was insufficient data in the process
actions.
message request.
Response: If this is a tracking event, no service actions
B181131C B181131C
are required. Otherwise, use the FRU and procedure
Explanation: An "invalid command" error was callouts detailed with the SRC to determine service
returned by the hub expansion processor. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1811327 B1811327
callouts detailed with the SRC to determine service
Explanation: SVPD_get_dev_addr_string failed and
actions.
returned an error.
Response: If this is a tracking event, no service actions
B181131D B181131D
are required. Otherwise, use the FRU and procedure
Explanation: An "invalid bus speed" error was callouts detailed with the SRC to determine service
returned by the hub expansion processor. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
240 System reference codes (Bxxx)
B1811328 • B1811337
B1811328 B1811328 B181132F B181132F
Explanation: Failed to reset the I2C engine or bus. Explanation: A device was closed but never unlocked.
This may cause I2C bus problems later.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1811329 B1811329
B1811330 B1811330
Explanation: An error occurred when trying to read
the thermal sensor temperature data. Explanation: IVPD detected that the SEEPROM
interface was called to access a non-SEEPROM device.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181132B B181132B
B1811334 B1811334
Explanation: A null pointer was received in an array
parameter. Explanation: A node controller was missing from the
address string that was received.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181132C B181132C
B1811335 B1811335
Explanation: An invalid device type was used to call a
function. Explanation: An invalid node was found in the
address string that was received.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181132D B181132D
B1811336 B1811336
Explanation: An invalid device type was used to call a
function, or the register that was requested is not Explanation: A node was missing in the address string
available on this chip. that was received.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181132E B181132E B1811337 B1811337
Explanation: An invalid device type was used to call a Explanation: An I2C device path was missing in
function. address string that was received.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 241
B1811338 • B1811345
B1811338 B1811338 B1811340 B1811340
Explanation: A subbus address was missing in the Explanation: The last function sent failed after several
address string that was received. retries.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1811339 B1811339 B1811341 B1811341
Explanation: Failed to configure the I2C bus for a Explanation: Unable to convert a bad device string
module. into a device structure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181133A B181133A B1811342 B1811342
Explanation: Failed to open the I2C bus for a device. Explanation: Failed to reset the open master I2C bus.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181133D B181133D B1811343 B1811343
Explanation: Tried to open the master I2C but to a Explanation: The master I2C bus going to the device
device, but it was already open. to be read is not open.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181133E B181133E B1811344 B1811344
Explanation: Failed to read the control registers of a Explanation: The node controller B I2C device path
module. was missing in the string that was received.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181133F B181133F B1811345 B1811345
Explanation: Failed to send the read register Explanation: The address list that was created was not
command to a module. valid.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
242 System reference codes (Bxxx)
B18113FF • B1811534
callouts detailed with the SRC to determine service
B18113FF B18113FF
actions.
Explanation: An attempt was made to call process
functionality that is not supported at this time.
B1811510 B1811510
Response: If this is a tracking event, no service actions
Explanation: Invalid data was received.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1811401 B1811401
Explanation: An invalid argument was passed to a
B1811515 B1811515
function.
Explanation: A nonzero return code was returned by
Response: If this is a tracking event, no service actions
the smartchip.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1811402 B1811402
Explanation: A call to ADAP open failed for the
B1811530 B1811530
secondary file descriptor.
Explanation: Unexpected null pointer, or zero, passed
Response: If this is a tracking event, no service actions
to routine.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1811403 B1811403
Explanation: A function call failed.
B1811531 B1811531
Response: If this is a tracking event, no service actions
Explanation: A null pointer was expected for a given
are required. Otherwise, use the FRU and procedure
parameter in this routine.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811404 B1811404
actions.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions B1811533 B1811533
are required. Otherwise, use the FRU and procedure
Explanation: Failed to obtain the svpd read mode.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811405 B1811405
actions.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions B1811534 B1811534
are required. Otherwise, use the FRU and procedure
Explanation: Failed to obtain svpd read mode.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811406 B1811406
actions.
Explanation: The message received was larger than
the message buffer.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 243
B1811535 • B1811545
B1811535 B1811535 B181153E B181153E
Explanation: Failed to read the data persistency. Explanation: Invalid block name length.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1811536 B1811536 B1811540 B1811540
Explanation: Failed to obtain data from persistent Explanation: Failed to configure the UART.
memory in filemode. The file corresponding to the
Response: If this is a tracking event, no service actions
device given does not exist.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1811541 B1811541
Explanation: Failed to reset the UART.
B1811538 B1811538
Response: If this is a tracking event, no service actions
Explanation: Failed to write block data to persistent
are required. Otherwise, use the FRU and procedure
memory.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811542 B1811542
actions.
Explanation: Failed to open a UART handle.
B1811539 B1811539 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to obtain the block in filemode.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811543 B1811543
actions.
Explanation: Failed to close the UART device handle.
B181153A B181153A Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The block that was searched for does not
callouts detailed with the SRC to determine service
exist or contains invalid data in filemode.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1811544 B1811544
callouts detailed with the SRC to determine service
actions. Explanation: Failed to write to the UART buffer.
Response: If this is a tracking event, no service actions
B181153B B181153B are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Invalid block data size in filemode.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1811545 B1811545
callouts detailed with the SRC to determine service
actions. Explanation: Failed to read data from the UART
buffer.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
244 System reference codes (Bxxx)
B1811546 • B1811553
B1811546 B1811546 B181154D B181154D
Explanation: The size of the data written to the UART Explanation: Failed to open the smartchip lock file.
buffer is not equal to the size of the data that was sent
Response: If this is a tracking event, no service actions
to it.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181154E B181154E
Explanation: Failed to write to the smartchip lock file.
B1811547 B1811547
Response: If this is a tracking event, no service actions
Explanation: The data obtained from the UART is
are required. Otherwise, use the FRU and procedure
bigger than the expected data size.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181154F B181154F
actions.
Explanation: Failed to write to the smartchip lock file.
B1811549 B1811549 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned when extracting
callouts detailed with the SRC to determine service
the node ID from the device address string.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1811550 B1811550
callouts detailed with the SRC to determine service
actions. Explanation: Failed to obtain a handle on the
smartchip lock file.
B181154A B181154A Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to check on the existence of the
callouts detailed with the SRC to determine service
smartchip lock file.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1811551 B1811551
callouts detailed with the SRC to determine service
actions. Explanation: Failed to obtain a handle for the
smartchip lock file.
B181154B B181154B Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to rename the smartchip lock file.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1811552 B1811552
actions.
Explanation: Device address format given is invalid.
B181154C B181154C Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to rename the smartchip lock file,
callouts detailed with the SRC to determine service
and thus failed to release the lock.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1811553 B1811553
callouts detailed with the SRC to determine service
actions. Explanation: Failed to obtain the free space on a given
smartchip.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 245
B1811554 • B181155F
callouts detailed with the SRC to determine service
B181155A B181155A
actions.
Explanation: The process message request buffer had
no data in it
B1811554 B1811554
Response: If this is a tracking event, no service actions
Explanation: Failed to obtain the free space on a given
are required. Otherwise, use the FRU and procedure
smartchip.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181155B B181155B
actions.
Explanation: The smartchip request size is invalid.
B1811555 B1811555 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to read a registry value.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181155C B181155C
actions.
Explanation: The smart chip packet size was not
valid.
B1811556 B1811556
Response: If this is a tracking event, no service actions
Explanation: Timed out waiting for a response from
are required. Otherwise, use the FRU and procedure
the universal asynchronous receiver/transmitter
callouts detailed with the SRC to determine service
(UART) read buffer command.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181155D B181155D
callouts detailed with the SRC to determine service
actions. Explanation: Failed to unlock the UART FFDC.
Response: If this is a tracking event, no service actions
B1811557 B1811557 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An invalid number of bytes was
actions.
returned by a chip in response to a read command.
Response: If this is a tracking event, no service actions
B181155E B181155E
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to unlock the universal
actions. asynchronous receiver/transmitter (UART) RDAL
failed.
B1811558 B1811558 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Invalid process message operation.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181155F B181155F
actions.
Explanation: A first failure data capture (FFDC) at the
thread level returned multiple blocks of data; this is
B1811559 B1811559
invalid.
Explanation: Failed to receive a request buffer from
Response: If this is a tracking event, no service actions
the process message interface.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
246 System reference codes (Bxxx)
B1811560 • B1811574
B1811560 B1811560 B181156F B181156F
Explanation: A UART event extraction failed. Explanation: The chip sent a response to a
non-resynchronization request.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181156A B181156A
B1811570 B1811570
Explanation: A UART event extraction failed.
Explanation: Sending a packet as a response to a chip
Response: If this is a tracking event, no service actions
resynchronization failed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181156B B181156B
Explanation: Multiple attempts to recover from a chip
B1811571 B1811571
communication failure have been made, and failed.
Explanation: A bad response was received from a
Response: If this is a tracking event, no service actions
chip.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181156C B181156C
Explanation: A time-out occurred waiting for the
B1811572 B1811572
response from the universal asynchronous
receiver/transmitter (UART) read buffer command. Explanation: Failed to read the chip line status.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181156D B181156D B1811573 B1811573
Explanation: A non-zero return code was returned by Explanation: Failed to write the chip line status
the chip. changes to enable the port's DCR lines.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181156E B181156E B1811574 B1811574
Explanation: The chip responded to with a "receive Explanation: Failed to write the chip line status
ready" flag to a resynchronization request. changes to enable the chip reset line.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 247
B1811575 • B1811580
B1811575 B1811575 B181157B B181157B
Explanation: Failed to write the chip line status Explanation: The chip lock has been taken over due to
changes to disable the chip reset line. two minutes of inactivity.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1811576 B1811576 B181157C B181157C
Explanation: Failed to reset the UART. Explanation: The user number received to lock out the
chip was invalid.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1811577 B1811577
B181157D B181157D
Explanation: Locking a binary semaphore failed when
attempting to reserve a chip. Explanation: The chip returned an unexpected
response when attempting to lock out a chip.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1811578 B1811578
B181157E B181157E
Explanation: Unlocking a binary semaphore failed
when attempting to reserve a chip. Explanation: The attempt to delete aiocb failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1811579 B1811579 B181157F B181157F
Explanation: Locking a binary semaphore failed when Explanation: The RDAL UART event extraction call
attempting to release a chip. returned an invalid status.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181157A B181157A B1811580 B1811580
Explanation: Unlocking a binary semaphore failed Explanation: A device address string was received
when attempting to release a lock . that shorter than 22 bytes.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
248 System reference codes (Bxxx)
B1811581 • B1812008
B1811581 B1811581 B1812003 B1812003
Explanation: The chip lock has been taken due to Explanation: The pthread_once POSIX function has
inactivity for a specified length of time, or the priority returned an error in system power interface firmware
of the current user. (SPIF).
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18115CC B18115CC B1812004 B1812004
Explanation: The smartchip for the device given is not Explanation: The pthread_setspecific POSIX function
reserved. returned an error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18115CD B18115CD B1812005 B1812005
Explanation: The smartchip is currently reserved by Explanation: An internal function call has failed in
this caller. SPIF.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18115CF B18115CF B1812006 B1812006
Explanation: The smartchip for the given device is Explanation: System power interface firmware (SPIF)
locked by another user. internal error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812001 B1812001 B1812007 B1812007
Explanation: The SPIF application received a signal. Explanation: System power interface firmware (SPIF)
internal error
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812002 B1812002
B1812008 B1812008
Explanation: An internal function call has failed in
SPIF. Explanation: An invalid parameter was passed to a
system power interface firmware (SPIF) function.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 249
B1812009 • B1812015
B1812009 B1812009 B181200F B181200F
Explanation: The pthread_mutex_lock function Explanation: SPIF failed to synchronize with the
returned an error in system power interface firmware power process.
(SPIF).
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812010 B1812010
B181200A B181200A
Explanation: System power interface firmware (SPIF)
Explanation: The pthread_mutex_lock function communication error.
returned an error in system power interface firwmare
Response: If this is a tracking event, no service actions
(SPIF).
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812012 B1812012
Explanation: System power interface firmware (SPIF)
B181200B B181200B
communication error.
Explanation: System power interface firmware (SPIF)
Response: If this is a tracking event, no service actions
failed to create a software object necessary for further
are required. Otherwise, use the FRU and procedure
processing.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812013 B1812013
actions.
Explanation: System power interface firmware (SPIF)
communication error.
B181200C B181200C
Response: If this is a tracking event, no service actions
Explanation: System power interface firmware (SPIF)
are required. Otherwise, use the FRU and procedure
timed out waiting for a particular event.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812014 B1812014
actions.
Explanation: System power interface firmware (SPIF)
communication error.
B181200D B181200D
Response: If this is a tracking event, no service actions
Explanation: Error occured during the updating of
are required. Otherwise, use the FRU and procedure
system power interface (SPIF) server's internal power
callouts detailed with the SRC to determine service
state.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1812015 B1812015
callouts detailed with the SRC to determine service
actions. Explanation: Error occured in system power interface
firmware (SPIF) while processing an error log object.
B181200E B181200E Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: SPIF detected invalid data.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
250 System reference codes (Bxxx)
B1812016 • B1812021
B1812016 B1812016 B181201C B181201C
Explanation: Error occured in system power interface Explanation: The pthread_cond_wait function
firmware (SPIF) while processing an error log object. returned an error in system power interface firmware
(SPIF).
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812017 B1812017
B181201D B181201D
Explanation: One of the spif_queue mutexes could not
be initialized. Explanation: A function call failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812018 B1812018 B181201E B181201E
Explanation: Error occured while attempting to Explanation: The pthread_cond_signal function
initialize SPIF thread condition variable. returned an error when called from system power
interface firmware (SPIF).
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812019 B1812019
B181201F B181201F
Explanation: Error occured while attempting to erase
SPIF thread condition variable. Explanation: The pthread_create function has failed in
system power interface firmware (SPIF).
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181201A B181201A
B1812020 B1812020
Explanation: One of the spif_queue mutexes could not
be erased. Explanation: System power interface firmware (SPIF)
failed to cancel its threads.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181201B B181201B
B1812021 B1812021
Explanation: System power interface firmware (SPIF)
terminated the system because it detected a power Explanation: The pthread_setcancelstate function
fault. returned an error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 251
B1812023 • B181202E
B1812023 B1812023 B1812029 B1812029
Explanation: The pthread_join function has failed to Explanation: System power interface firmware (SPIF)
join the SPIF server threads. communication error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812024 B1812024 B181202A B181202A
Explanation: System power interface firmware (SPIF) Explanation: System power interface firmware (SPIF)
communication error. communication error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812025 B1812025 B181202B B181202B
Explanation: System power interface firmware (SPIF) Explanation: System power interface firmware (SPIF)
communication error. communication error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812026 B1812026 B181202C B181202C
Explanation: System power interface firmware (SPIF) Explanation: System power interface firmware (SPIF)
communication error. communication error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812027 B1812027 B181202D B181202D
Explanation: The SPIF server has routed an Explanation: The SPIF client found that the SPIF
acknowledgment message to the command queue. This server was not ready for communication.
indicates an internal problem with the SPIF server.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181202E B181202E
B1812028 B1812028
Explanation: System power interface firmware (SPIF)
Explanation: A command sent by SPIF was rejected by communication error.
the power firmware.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
252 System reference codes (Bxxx)
B181202F • B181203A
B181202F B181202F B1812035 B1812035
Explanation: System power interface firmware (SPIF) Explanation: System power interface firmware (SPIF)
communication error. internal failure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812030 B1812030 B1812036 B1812036
Explanation: System power interface firmware (SPIF) Explanation: The pthread_detach function has failed
communication error. to detach in system power interface firmware (SPIF).
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812031 B1812031 B1812037 B1812037
Explanation: System Power Interface firmware (SPIF) Explanation: Error occured while updating the
communication error. operator (control) panel.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812032 B1812032 B1812038 B1812038
Explanation: An error was caused by invalid Explanation: Power on/off notification failed because
arguments in SPIF. of bad service processor state.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812033 B1812033 B1812039 B1812039
Explanation: System power interface firmware (SPIF) Explanation: Power off notification by SPIF to the
communication error. service processor's state manager failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812034 B1812034 B181203A B181203A
Explanation: System power interface firmware (SPIF) Explanation: Power on notification by SPIF to the
internal failure. service processor's state manager failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 253
B181203B • B1812046
B181203B B181203B B1812041 B1812041
Explanation: The pthread_cond_timedwait() call timed Explanation: An internal function call has failed in
out on a thread condition. SPIF.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181203C B181203C B1812042 B1812042
Explanation: The pthread_cond_timedwait function Explanation: The SPIF client failed to send a message
returned an error when called from system power to the SPIF server.
interface firmware (SPIF).
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812043 B1812043
B181203D B181203D
Explanation: An internal function call has failed in
Explanation: The error log is returned by SPIF when a SPIF.
queue is full.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812044 B1812044
B181203E B181203E
Explanation: Unexpected data were detected by SPIF.
Explanation: This error log is used by SPIF when the
Response: If this is a tracking event, no service actions
queue is empty.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812045 B1812045
Explanation: An internal function call has failed in
B181203F B181203F
SPIF.
Explanation: One of the two input parameters is
Response: If this is a tracking event, no service actions
NULL. The SPIF server cannot function without these
are required. Otherwise, use the FRU and procedure
parameters.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812046 B1812046
actions.
Explanation: An internal function call has failed in
SPIF.
B1812040 B1812040
Response: If this is a tracking event, no service actions
Explanation: System power interface firmware (SPIF)
are required. Otherwise, use the FRU and procedure
communication error.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
254 System reference codes (Bxxx)
B1812047 • B1812108
B1812047 B1812047 B1812102 B1812102
Explanation: System power interface firmware (SPIF) Explanation: Memory allocation failed.
communication error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812103 B1812103
B1812048 B1812048
Explanation: A failure occurred when creating a
Explanation: System power interface firmware (SPIF) thread.
internal error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812104 B1812104
B1812049 B1812049
Explanation: A system call failed.
Explanation: Power-related function failed in SPIF
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812105 B1812105
B181204A B181204A
Explanation: A system call failed.
Explanation: A system power interface firmware
Response: If this is a tracking event, no service actions
(SPIF) command failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812106 B1812106
Explanation: A system call failed.
B181204B B181204B
Response: If this is a tracking event, no service actions
Explanation: System power interface firmware (SPIF)
are required. Otherwise, use the FRU and procedure
communication error.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812107 B1812107
actions.
Explanation: An invalid parameter was passed to a
function.
B1812101 B1812101
Response: If this is a tracking event, no service actions
Explanation: REMP initialization failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812108 B1812108
Explanation: Unable to create a message queue.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 255
B1812109 • B1812115
B1812109 B1812109 B181210F B181210F
Explanation: An invalid command was received from Explanation: An error occurred when removing a
an RPC device. message from the queue.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181210A B181210A B1812110 B1812110
Explanation: The message had an invalid function ID. Explanation: An error log was committed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181210B B181210B B1812111 B1812111
Explanation: A call returned a time-out condition, but Explanation: The power lock error log was committed.
no time-out was specified.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812112 B1812112
B181210C B181210C
Explanation: The netc close operation failed.
Explanation: The file descriptor that was expected
Response: If this is a tracking event, no service actions
was not set after the system call.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812113 B1812113
Explanation: An error from the event manager was
B181210D B181210D
committed.
Explanation: The CDAL call failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812114 B1812114
B181210E B181210E
Explanation: Unable to create a token queue.
Explanation: Unable to insert the initial events into
Response: If this is a tracking event, no service actions
the queue.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812115 B1812115
Explanation: Unable to insert tokens into the token
queue.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
256 System reference codes (Bxxx)
B1812116 • B181220B
callouts detailed with the SRC to determine service
B1812206 B1812206
actions.
Explanation: An error occurred when the power lock
(PLCK) interface was updating the lock data file.
B1812116 B1812116
Response: If this is a tracking event, no service actions
Explanation: The number of threads exceeded the
are required. Otherwise, use the FRU and procedure
maximum.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812207 B1812207
actions.
Explanation: The power lock (PLCK) interface
experienced an error while trying to read the lock data
B1812201 B1812201
file.
Explanation: An error occurred when the power lock
Response: If this is a tracking event, no service actions
(PLCK) interface was opening the lock data file.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812208 B1812208
Explanation: The power lock (PLCK) interface
B1812202 B1812202
experienced an error while trying to write to the lock
Explanation: The power lock (PLCK) interface data file.
experienced an error when unlocking or closing the
Response: If this is a tracking event, no service actions
lock data file.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812209 B1812209
Explanation: The power lock (PLCK) interface was not
B1812203 B1812203
able to read the lock data file.
Explanation: The power lock interface experienced an
Response: If this is a tracking event, no service actions
error when initializing the header of the lock data file.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181220A B181220A
Explanation: An invalid pointer was passed into a
B1812204 B1812204
function.
Explanation: Failed to read a registry value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181220B B181220B
B1812205 B1812205
Explanation: An invalid parameter was passed into a
Explanation: An error occurred when the power lock function.
(PLCK) interface was reading the lock data file.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 257
B181220C • B1812218
B181220C B181220C B1812212 B1812212
Explanation: The power state of the system was not Explanation: A firmware component has used the
valid for the IPL lock that was requested. power lock (PLCK) interface incorrectly.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181220D B181220D B1812213 B1812213
Explanation: The power lock (PLCK) interface could Explanation: An error occurred when the power lock
not determine the current power state of the system. (PLCK) interface was allocating memory.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181220E B181220E B1812214 B1812214
Explanation: Failed to open and lock the lock data Explanation: The power lock (PLCK) interface
file. experienced a threading error
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181220F B181220F B1812215 B1812215
Explanation: Failed to close or unlock the power lock Explanation: An error occurred when removing the
lock data file. lock from the lock data file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812210 B1812210 B1812216 B1812216
Explanation: A firmware component has used the Explanation: The firmware component that requested
power lock (PLCK) interface incorrectly. the unlock operation did not have a lock on the lock
data file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812211 B1812211
B1812218 B1812218
Explanation: A firmware component has tried to use
the power lock (PLCK) interface incorrectly. Explanation: The requested IPL has been blocked by
the power lock (PLCK) component. The IPL will
Response: If this is a tracking event, no service actions
proceed when the lock has been released.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
258 System reference codes (Bxxx)
B1812219 • B1812224
B1812219 B1812219 B181221F B181221F
Explanation: A value passed into a function was out Explanation: The power lock (PLCK) process did not
of range. initialize correctly.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181221A B181221A B1812220 B1812220
Explanation: The power lock (PLCK) interface Explanation: The power lock (PLCK) process was did
received an immediate IPL request and bypassed any not initialize correctly.
existing power locks.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812221 B1812221
B181221B B181221B
Explanation: An invalid argument was passed into the
Explanation: The state manager (SMGR) firmware timer thread.
component has rejected an IPL request made by the
Response: If this is a tracking event, no service actions
power lock (PLCK) interface.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1812222 B1812222
Explanation: The power lock (PLCK) process received
B181221C B181221C
an unexpected signal.
Explanation: A power IPL has already been requested
Response: If this is a tracking event, no service actions
and queued by the power lock (PLCK) interface.
are required. Otherwise, use the FRU and procedure
Therefore, this IPL request will be rejected.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812223 B1812223
actions.
Explanation: The power lock (PLCK) interface
experienced a threading error
B181221D B181221D
Response: If this is a tracking event, no service actions
Explanation: Failed to send a power-on event to the
are required. Otherwise, use the FRU and procedure
panel for the requested IPL.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812224 B1812224
actions.
Explanation: A power IPL was already in progress, so
another IPL lock could not be created.
B181221E B181221E
Response: If this is a tracking event, no service actions
Explanation: Failed to send a power-off event to the
are required. Otherwise, use the FRU and procedure
panel.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 259
B1812225 • B1812230
B1812225 B1812225 B181222B B181222B
Explanation: The power lock (PLCK) interface could Explanation: The power lock (PLCK) interface was not
not determine if a power on or power off was in able to determine the size of the lock data file.
progress.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181222C B181222C
B1812226 B1812226
Explanation: The power lock (PLCK) interface
Explanation: Failed to write a registry value. experienced a problem while determining how much
time has elapsed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812227 B1812227
B181222D B181222D
Explanation: The power lock (PLCK) interface
experienced an error when indicating that a power IPL Explanation: Failed to read a registry value.
was started.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181222E B181222E
B1812228 B1812228
Explanation: The power-on request cannot be
Explanation: The power lock (PLCK) interface was processed because the system has not been granted the
unable to determine the current firmware state. appropriate permission by the IPMI component.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812229 B1812229 B181222F B181222F
Explanation: Failed to read a registry value. Explanation: The original IPL request has been
mapped to an APOR IPL type.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181222A B181222A
B1812230 B1812230
Explanation: A firmware component has used the
power lock (PLCK) interface incorrectly. Explanation: Failed to read apor/armed from the
registry.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
260 System reference codes (Bxxx)
B1812231 • B181230D
B1812231 B1812231 B1812306 B1812306
Explanation: An invalid parameter passed into the Explanation: A synchronization failed.
function.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812307 B1812307
B1812232 B1812232
Explanation: A registry read failed.
Explanation: Failed to read a registry value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812308 B1812308
B1812233 B1812233
Explanation: A registry write failed.
Explanation: Failed to read a registry value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812309 B1812309
B1812235 B1812235
Explanation: Failed to build a constructor.
Explanation: Call to client API returned an error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181230A B181230A
B1812301 B1812301
Explanation: Failed to get an SRC.
Explanation: An unexpected signal was received.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181230C B181230C
B1812302 B1812302
Explanation: An error occurred.
Explanation: A fork operation failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181230D B181230D
B1812305 B1812305
Explanation: An error occurred in an event monitor.
Explanation: The function received less data than it
Response: If this is a tracking event, no service actions
was expecting.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 261
B181230E • B1812407
callouts detailed with the SRC to determine service
B181230E B181230E
actions.
Explanation: A daemon was not ready.
Response: If this is a tracking event, no service actions B1812402 B1812402
are required. Otherwise, use the FRU and procedure
Explanation: Failed to read the service processor role
callouts detailed with the SRC to determine service
from the registry.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181230F B181230F
callouts detailed with the SRC to determine service
Explanation: A function call failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1812403 B1812403
callouts detailed with the SRC to determine service
Explanation: Failed to read the system operation
actions.
mode from the registry.
Response: If this is a tracking event, no service actions
B1812310 B1812310
are required. Otherwise, use the FRU and procedure
Explanation: PLCK returned an error. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1812404 B1812404
actions.
Explanation: Failed to read the service processor
device driver level from the registry.
B1812312 B1812312
Response: If this is a tracking event, no service actions
Explanation: A bad return code was received. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1812405 B1812405
Explanation: Failed to write the wake-on-LAN policy
B1812313 B1812313 to the registry.
Explanation: A function call failed. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B1812406 B1812406
B1812314 B1812314 Explanation: Failed to get the p0 file path from the
registry.
Explanation: The secondary service processor (or
system controller) did not reach standby within the Response: If this is a tracking event, no service actions
allotted time. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1812407 B1812407
Explanation: Failed to read svpd/WakeOnLAN from
B1812401 B1812401 the registry.
Explanation: Failed to read the wake-on-LAN policy Response: If this is a tracking event, no service actions
from the registry. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
262 System reference codes (Bxxx)
B1812410 • B1812429
B1812410 B1812410 B1812424 B1812424
Explanation: An error occurred when activating the Explanation: Failed to get the current wake-on-LAN
wake-on-LAN hardware. policy.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812411 B1812411 B1812425 B1812425
Explanation: An error occurred when deactivating the Explanation: Failed to get the MAC address from
wake-on-LAN hardware. VPD.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812420 B1812420 B1812426 B1812426
Explanation: Wake-on-LAN is not supported. Explanation: Failed to determine from VPD whether
wake-on-LAN is supported.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812421 B1812421
B1812427 B1812427
Explanation: Wake-on-LAN is not supported on this
system because there is no Ethernet card. Explanation: Wake-on-LAN is not supported on the
secondary service processor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812422 B1812422
B1812428 B1812428
Explanation: The value of the wake-on-LAN policy is
not valid. Explanation: Failed to get the status of a FRU from
VPD.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812423 B1812423
B1812429 B1812429
Explanation: Failed to get the current power state of
the system. Explanation: Failed to get the maximum number of
field replaceable units (FRUs) from vital product data
Response: If this is a tracking event, no service actions
(VPD).
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 263
B1812430 • B1812451
B1812430 B1812430 B1812440 B1812440
Explanation: Failed to start the wake-on-LAN process. Explanation: Failed to wait for the requested state of
the wake-on-LAN interrupt.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812431 B1812431
B1812441 B1812441
Explanation: Failed to create the process
synchronization file for the wake-on-LAN process. Explanation: Failed to set the general purpose I/O pin
to the appropriate level.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812432 B1812432
B1812442 B1812442
Explanation: Another wake-on-LAN process was
already running. Explanation: Failed to close the general purpose I/O
device driver.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812433 B1812433
B1812443 B1812443
Explanation: Failed to power on the system via
wake-on-LAN. Explanation: Failed to open the general purpose I/O
device driver.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812434 B1812434
B1812450 B1812450
Explanation: An error occurred while processing the
wake-on-LAN interrupt. Explanation: Failed to shift the data into the target
chip via the JTAG device driver.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812435 B1812435
B1812451 B1812451
Explanation: An error occurred while waiting for the
wake-on-LAN interrupt. Explanation: Failed to lock the JTAG device driver.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
264 System reference codes (Bxxx)
B1812452 • B18124B3
B1812452 B1812452 B18124A4 B18124A4
Explanation: Failed to close the JTAG device driver. Explanation: Failed to delete the asynchronous
input/output control block from memory.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812453 B1812453
B18124A5 B18124A5
Explanation: Failed to open the JTAG device driver.
Explanation: Failed to delete the context for an
Response: If this is a tracking event, no service actions
asynchronous input/output device driver.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B18124A0 B18124A0
Explanation: Failed to initialize an asynchronous
B18124B0 B18124B0
input/ouput control block.
Explanation: Failed to drive the input/ouput pin to
Response: If this is a tracking event, no service actions
the correct level.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B18124A1 B18124A1
Explanation: Failed to create the context for an an
B18124B1 B18124B1
asynchronous input/ouput device driver.
Explanation: Failed to close the general purpose
Response: If this is a tracking event, no service actions
input/output device driver.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B18124A2 B18124A2
Explanation: Received the wrong number of
B18124B2 B18124B2
asynchronous input/output control blocks from the
AIO device driver. Explanation: Failed to open the general purpose
input/output device driver.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18124A3 B18124A3
B18124B3 B18124B3
Explanation: Submitted the wrong number of
asynchronous input/ouput control blocks to the AIO Explanation: Failed to initialize the general purpose
device driver. input/output events.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 265
B18124C0 • B1812615
B18124C0 B18124C0 B1812605 B1812605
Explanation: Failed to shift data into the target chip Explanation: The alert level is invalid
via the JTAG device.
Response: If this is a tracking event, no service actions B1812606 B1812606
are required. Otherwise, use the FRU and procedure
Explanation: The domain is invalid
callouts detailed with the SRC to determine service
actions.
B1812607 B1812607
B18124C1 B18124C1 Explanation: The o_throttlePowerArray is NULL.
Explanation: Failed to lock the JTAG device. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B1812609 B1812609
B18124C2 B18124C2 Explanation: Command to POWR via SPIF failed
Explanation: Failed to close the JTAG device.
B181260A B181260A
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Request to CHIC/PRD failed
callouts detailed with the SRC to determine service
actions.
B181260E B181260E
B18124C3 B18124C3 Explanation: When the processors were being polled
about their utilization levels, at least one processor
Explanation: Failed to open the JTAG device. returned an invalid status.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181260F B181260F
callouts detailed with the SRC to determine service
actions. Explanation: The processor card's thermal index is
invalid, or the function is not supported
B1812600 B1812600
B1812611 B1812611
Explanation: A vital product data (VPD) error
occurred. Explanation: Invalid chip number
Response: Use the FRU and procedure callouts
detailed with the SRC to determine service actions. B1812612 B1812612
Explanation: Invalid message size
B1812601 B1812601
Explanation: An internal error occurred when B1812613 B1812613
processing a request in TMGT Explanation: GPIO read failure
B1812602 B1812602 B1812614 B1812614
Explanation: The sensors could not be read due to Explanation: Registry read operation failure
thermal monitoring being disabled
B1812615 B1812615
B1812603 B1812603
Explanation: A TPMF failure was logged during a
Explanation: The processor FRU RID is not present in reset.
the TMGT configuration tables
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
266 System reference codes (Bxxx)
B1812616 • B1812622
B1812616 B1812616 B181261C B181261C
Explanation: A critical error occurred on the Explanation: The TPMF response has an invalid
thermal/power management device (TPMD); it is being length.
disabled.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181261D B181261D
B1812617 B1812617
Explanation: An error was created by the
Explanation: There was a TPMD download failure in thermal/power management device (TPMD).
state 3.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181261E B181261E
B1812618 B1812618
Explanation: A function call failed.
Explanation: An I2C send failure was logged.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181261F B181261F
B1812619 B1812619
Explanation: The I2C interface controller failed to
Explanation: A checksum failure occurred. enable the I2C interface.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181261A B181261A B1812620 B1812620
Explanation: TPMF communications was not Explanation: chicReserve failed.
established, or an unsupported application was found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812621 B1812621
B181261B B181261B
Explanation: chicRelease failed.
Explanation: The TPMF failed to respond.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812622 B1812622
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 267
B1812623 • B181262F
callouts detailed with the SRC to determine service
B1812629 B1812629
actions.
Explanation: The thermal and power management
firmware (TPMF) is not in a good state.
B1812623 B1812623
Response: If this is a tracking event, no service actions
Explanation: An invalid thermal throttle value was
are required. Otherwise, use the FRU and procedure
passed in set command.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181262B B181262B
actions.
Explanation: The mode will not be changed - already
in nominal mode.
B1812624 B1812624
Response: If this is a tracking event, no service actions
Explanation: The get throttle status command was not
are required. Otherwise, use the FRU and procedure
sent because there was no communication to the TPMF.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181262C B181262C
actions.
Explanation: Unable to write the current power cap
value to a registry.
B1812625 B1812625
Response: If this is a tracking event, no service actions
Explanation: Received zero entries back from
are required. Otherwise, use the FRU and procedure
chicGetCoreStatus call.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181262D B181262D
actions.
Explanation: Mnfg mode is enabled and TPMF is
oversubscribed.
B1812626 B1812626
Response: If this is a tracking event, no service actions
Explanation: "IPMI Throttle Watts" call failed when
are required. Otherwise, use the FRU and procedure
getting the maximum power cap.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181262E B181262E
actions.
Explanation: The get throttle status command was not
sent because TPMD is being downloaded.
B1812627 B1812627
Response: If this is a tracking event, no service actions
Explanation: A failure occurred when trying to get a
are required. Otherwise, use the FRU and procedure
common card identification number (CCIN).
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181262F B181262F
actions.
Explanation: The mode will not be changed - already
in nominal mode.
B1812628 B1812628
Response: If this is a tracking event, no service actions
Explanation: Safe mode is complete.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
268 System reference codes (Bxxx)
B1812630 • B181263B
B1812630 B1812630 B1812636 B1812636
Explanation: A failure occurred when trying to change Explanation: Unable to calculate the system's ideal
the memory controller mode. clock speed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812631 B1812631 B1812637 B1812637
Explanation: An error was returned from a function Explanation: The mode change that was required for
call. concurrent maintenance failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812632 B1812632 B1812638 B1812638
Explanation: Unable to calculate the system's ideal Explanation: Informational message: the mode change
clock speed. was successful.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812633 B1812633 B1812639 B1812639
Explanation: Failed to get into the active state. Explanation: When the thermal and power
management firmware (TPMF) was polling for the
Response: If this is a tracking event, no service actions
utilization of each processor, no functional processor
are required. Otherwise, use the FRU and procedure
cores were found. At least one should have been found.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812634 B1812634
actions.
Explanation: The frequency change was canceled due
to failures to read the registry.
B181263A B181263A
Response: If this is a tracking event, no service actions
Explanation: An error occurred when trying to acquire
are required. Otherwise, use the FRU and procedure
an I2C bus lock.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812635 B1812635
actions.
Explanation: A TPMF voltage change timed out.
Response: If this is a tracking event, no service actions B181263B B181263B
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned from a function
callouts detailed with the SRC to determine service
call.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 269
B181263E • B1812801
B181263E B181263E B1812701 B1812701
Explanation: An error occurred while parsing the Explanation: An invalid voltage control command was
power definitions file received.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812644 B1812644 B1812702 B1812702
Explanation: Memory throttle failure. Explanation: The daemon received a message with an
invalid function field.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812647 B1812647
B1812707 B1812707
Explanation: Fidle disable failure.
Explanation: The POWR server wasn't ready for the
Response: If this is a tracking event, no service actions
command it was sent.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181268A B181268A
Explanation: Changing to a new state or mode is not
B181270E B181270E
supported.
Explanation: The daemon received a request while
Response: If this is a tracking event, no service actions
running on the secondary service processor.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181268B B181268B
Explanation: There was an error writing the new
B18127C0 B18127C0
TPMF state to the registry.
Explanation: The "power off unit" command failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18126B9 B18126B9
B1812801 B1812801
Explanation: Powercap calculation and distribution
have been completed Explanation: An internal error occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
270 System reference codes (Bxxx)
B1812802 • B1812A06
B1812802 B1812802 B1812A01 B1812A01
Explanation: A secondary error occurred. Explanation: This is an informational SRC; no service
actions are required. It indicates that the system made a
Response: If this is a tracking event, no service actions
periodic call home with system power and thermal
are required. Otherwise, use the FRU and procedure
information.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1812803 B1812803
actions.
Explanation: The array depth was not valid.
Response: If this is a tracking event, no service actions B1812A02 B1812A02
are required. Otherwise, use the FRU and procedure
Explanation: This is an informational SRC; no service
callouts detailed with the SRC to determine service
actions are required. It indicates that the TPMD
actions.
(thermal/power mangement device) is about to be
reset.
B1812804 B1812804
Response: If this is a tracking event, no service actions
Explanation: Non-terminated input was found. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1812A03 B1812A03
Explanation: A communication failure between the
B1812805 B1812805 TPMD (thermal/power management device) and the
service processor occurred.
Explanation: The input was null.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1812A04 B1812A04
B1812806 B1812806
Explanation: This is an informational SRC; no service
Explanation: The input was not valid. actions are required. It indicates that thermal data was
Response: If this is a tracking event, no service actions logged.
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812809 B1812809
Explanation: The instance was not valid. B1812A05 B1812A05
Response: If this is a tracking event, no service actions Explanation: This is an informational SRC; no service
are required. Otherwise, use the FRU and procedure actions are required. It indicates that a power supply
callouts detailed with the SRC to determine service event was detected.
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1812A00 B1812A00 callouts detailed with the SRC to determine service
actions.
Explanation: This is a general TPMD (thermal/power
management device) firmware SRC. See the callouts to
determine the service actions. B1812A06 B1812A06
Response: If this is a tracking event, no service actions Explanation: Failure to hold a hard power cap.
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions.
(B1xx) Reference codes 271
B1812A10 • B1812A61
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1812A10 B1812A10
Explanation: The TPMD (thermal/power management
B1812A30 B1812A30
device) was unable to enforce thermal limits on a
processor. Explanation: There was a thermal failure logged
against a memory DIMM.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812A11 B1812A11
B1812A40 B1812A40
Explanation: The TPMD (thermal/power management
device) failed to communicate with a processor over Explanation: The TPMD (thermal/power management
the I2C bus. device) was unable to enforce thermal limits on a
memory controller.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812A12 B1812A12
B1812A50 B1812A50
Explanation: The TPMD (thermal/power management
device) detected a failure of a processor due to a Explanation: The TPMD (thermal/power management
timeout on special wake-up, reaching the voltage device) was unable to enforce thermal limits on a GX
target, waiting for PMC idle, or changing frequency. hub.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1812A13 B1812A13 B1812A60 B1812A60
Explanation: All DTS (digital thermal sensor) Explanation: Throttling occurred in nominal or turbo
temperatures read from a processor core were zero. mode due to a thermal limit being reached on a
processor, memory DIMM, or memory controller.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1812A20 B1812A20
B1812A61 B1812A61
Explanation: There was a thermal failure logged
against a VRM (voltage regulator module). Explanation: Throttling occurred in nominal or turbo
mode due to the bulk power limit being reached with
Response: If this is a tracking event, no service actions
both power supplies good.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1812A21 B1812A21
Explanation: The TPMD (thermal/power management
device) failed to communicate with a VRM (voltage
regulator module) over the I2C bus.
272 System reference codes (Bxxx)
B1812A70 • B1813007
B1812A70 B1812A70 B1813002 B1813002
Explanation: The TPMD (thermal/power management Explanation: Code update was busy.
device) failed to communicate with a DCA (distributed
Response: If this is a tracking event, no service actions
converter assembly).
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813003 B1813003
Explanation: A failure occurred when reading a
B1812A80 B1812A80
registry value.
Explanation: A communication error between a
Response: If this is a tracking event, no service actions
processor and the QVRM was detected.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813004 B1813004
Explanation: A failure occurred when writing a
B1812A82 B1812A82
registry value.
Explanation: An IO hub to DCCA communication
Response: If this is a tracking event, no service actions
failure occurred. One of the DCCAs is not present, is
are required. Otherwise, use the FRU and procedure
defective, or has lost power.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813005 B1813005
actions.
Explanation: An error occurred when getting data
from a registry variable.
B1812A90 B1812A90
Response: If this is a tracking event, no service actions
Explanation: The TPMD (thermal/power management
are required. Otherwise, use the FRU and procedure
device) detected an A/D (analog to digital) calibration
callouts detailed with the SRC to determine service
failure.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813006 B1813006
callouts detailed with the SRC to determine service
actions. Explanation: Unable to set a registry variable.
Response: If this is a tracking event, no service actions
B1812AA0 B1812AA0 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A communication failure over the I2C
actions.
bus to the I/O chip was detected.
Response: If this is a tracking event, no service actions
B1813007 B1813007
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The system firmware installation image
actions. is invalid.
Response: If this is a tracking event, no service actions
B1812AA1 B1812AA1 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A timeout failure of the I/O chip was
actions.
detected.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 273
B1813008 • B1813014
B1813008 B1813008 B181300F B181300F
Explanation: The system firmware installation image Explanation: Informational message: Firmware update
is invalid. is attempting to update the P side of the firmware
flash.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813009 B1813009
B1813010 B1813010
Explanation: There is at least one part of the firmware
in the specified flash that is corrupted. Explanation: The system firmware installation image
is invalid.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181300A B181300A
B1813011 B1813011
Explanation: A problem was encountered during
system firmware installation. Explanation: A system call failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181300B B181300B B1813012 B1813012
Explanation: The process that started firmware update Explanation: Firmware image module does not exist .
is not the process that is requesting that the firmware
Response: If this is a tracking event, no service actions
update be ended.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813013 B1813013
Explanation: A firmware update module did not exist.
B181300D B181300D
Response: If this is a tracking event, no service actions
Explanation: An attempt was made to write the
are required. Otherwise, use the FRU and procedure
registry data, but it had already been written.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813014 B1813014
actions.
Explanation: Firmware installation was not allowed
due to a limitation.
B181300E B181300E
Response: If this is a tracking event, no service actions
Explanation: A flash side other than temporary (T) or
are required. Otherwise, use the FRU and procedure
permanent (P) was specified.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
274 System reference codes (Bxxx)
B1813015 • B181302B
B1813015 B1813015 B1813023 B1813023
Explanation: Unable to request a power lock. Explanation: Failed to execute cupdLidValidation()
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813016 B1813016 B1813025 B1813025
Explanation: The system firmware installation image Explanation: A request was made to installation a file
is invalid. beyond the file's size.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813017 B1813017 B1813028 B1813028
Explanation: The buffer provided is too small to store Explanation: There was a problem with the flashing of
the data and header information. the firmware.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181301F B181301F B1813029 B1813029
Explanation: A firmware installation was attempted Explanation: An invalid component ID was found.
the side from which the system was booted.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181302A B181302A
B1813020 B1813020
Explanation: A firmware installation code module was
Explanation: An attempt was made to installation the being modified, when another modify request was
system firmware on the flash side with the good image received. The request was denied.
when the other flash side has a bad image. This is
Response: If this is a tracking event, no service actions
prohibited; otherwise, both sides could become
are required. Otherwise, use the FRU and procedure
corrupted.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181302B B181302B
actions.
Explanation: The digital signature does not match the
expected value.
B1813022 B1813022
Response: If this is a tracking event, no service actions
Explanation: After the firmware was installed, the
are required. Otherwise, use the FRU and procedure
newly-installed firmware was found to be corrupted.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 275
B181302D • B181303E
B181302D B181302D B1813038 B1813038
Explanation: Informational message: A firmware Explanation: An error was detected while creating an
installation was successfully performed. event manager object.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813030 B1813030 B1813039 B1813039
Explanation: An invalid code installation type was Explanation: Unable to create a thread.
found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181303A B181303A
B1813031 B1813031
Explanation: The wrong firmware image was sent to
Explanation: A data file was sent with the incorrect the service processor to be flashed.
header format.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181303B B181303B
B1813034 B1813034
Explanation: This indicates that the service processor
Explanation: The power state is invalid. Firmware no longer has the power lock (that is refreshed by the
update from the HMC is only allowed when the HMC) during a firmware update because it has
managed system is at standby or running. rebooted for some other reason.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813035 B1813035 B181303D B181303D
Explanation: The file offset that was specified Explanation: The data is not correct.
exceeded the file size.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181303E B181303E
B1813036 B1813036
Explanation: A function call failed.
Explanation: A request has been received to abort the
Response: If this is a tracking event, no service actions
flash update.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
276 System reference codes (Bxxx)
B181303F • B1813099
B181303F B181303F B1813050 B1813050
Explanation: Reading a file failed. Explanation: An unknown signal was received.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813043 B1813043 B1813061 B1813061
Explanation: The data necessary to store a certain type Explanation: A system call returned an error.
of information is not the correct size.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813072 B1813072
B1813044 B1813044
Explanation: Setting CTX from the registry failed.
Explanation: An invalid system firmware flash
Response: If this is a tracking event, no service actions
installation file was received.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813088 B1813088
Explanation: Failure when opening a file.
B1813045 B1813045
Response: If this is a tracking event, no service actions
Explanation: Unable to find the keyword that
are required. Otherwise, use the FRU and procedure
indicates the bank ID.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813097 B1813097
actions.
Explanation: Mirroring of volumes failed.
B1813047 B1813047 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The code update policy cannot be
callouts detailed with the SRC to determine service
changed due to an inband update.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813098 B1813098
callouts detailed with the SRC to determine service
actions. Explanation: Set "no updates allowed" policy on a
node controller.
B181304F B181304F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The hardware management console
callouts detailed with the SRC to determine service
(HMC) requested an invalid operation, or an operation
actions.
that is no longer supported.
Response: If this is a tracking event, no service actions
B1813099 B1813099
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Unable to obtain a firmware module's
actions. cyclic redundancy check (CRC) value.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 277
B181309A • B181310E
B181309A B181309A B1813107 B1813107
Explanation: The stat command failed on a file. Explanation: Failure to establish communication pipe
to the error log server.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181309B B181309B
B1813108 B1813108
Explanation: A system call returned an error.
Explanation: The operation to talk to the hypervisor
Response: If this is a tracking event, no service actions
failed, and will be retried.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181309F B181309F
Explanation: Reading a file failed.
B1813109 B1813109
Response: If this is a tracking event, no service actions
Explanation: Generic failure writing data to the file
are required. Otherwise, use the FRU and procedure
system; possible file system problem.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813101 B1813101
actions.
Explanation: The operation failed to create a thread.
Response: If this is a tracking event, no service actions B181310A B181310A
are required. Otherwise, use the FRU and procedure
Explanation: Generic read failure of data on the
callouts detailed with the SRC to determine service
current stream.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813104 B1813104
callouts detailed with the SRC to determine service
Explanation: Generic network communication failure. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181310B B181310B
callouts detailed with the SRC to determine service
Explanation: The operation to expand an error log
actions.
failed.
Response: If this is a tracking event, no service actions
B1813105 B1813105
are required. Otherwise, use the FRU and procedure
Explanation: Network communication receiving callouts detailed with the SRC to determine service
failure. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181310E B181310E
callouts detailed with the SRC to determine service
Explanation: The operation to read the manufacturing
actions.
policy flags failed.
Response: If this is a tracking event, no service actions
B1813106 B1813106
are required. Otherwise, use the FRU and procedure
Explanation: Generic network communication failure callouts detailed with the SRC to determine service
closing a connection. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
278 System reference codes (Bxxx)
B1813111 • B181311E
B1813111 B1813111 B1813119 B1813119
Explanation: The operation to read via the error log Explanation: The operation to assign a unique entry
server pipe failed. ID failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813112 B1813112 B181311A B181311A
Explanation: An event caught by the error log server Explanation: The operation to turn on the platform
was found to have an incorrect data length. service indicator failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813113 B1813113 B181311B B181311B
Explanation: The operation to notify the system of a Explanation: The error log operation failed due to an
new error log entry has failed. invalid section header ID.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813114 B1813114 B181311C B181311C
Explanation: The operation to collect error logs that Explanation: The error log operation failed due to the
were committed prior to the error log server being fully section size being invalid.
initialized has failed; possible file system problems.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181311D B181311D
B1813116 B1813116
Explanation: The error log operation failed due to an
Explanation: The change of state failed for the given invalid section version.
entry ID.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181311E B181311E
B1813117 B1813117
Explanation: The operation failed due to an invalid
Explanation: Input data was found to be corrupted. section count in the section header.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 279
B181311F • B181312C
B181311F B181311F B1813126 B1813126
Explanation: Generic network communication failure. Explanation: The operation to format the error log file
system failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813120 B1813120
B1813127 B1813127
Explanation: The error log server detected an
unrecognized signal. Explanation: The error log server has been fully
initialized; informational only; no action required.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813121 B1813121
B1813129 B1813129
Explanation: The current operation failed due to
invalid data. Explanation: The error log server received a syslog
message which requires attention.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813122 B1813122
B181312A B181312A
Explanation: The error log file system detected a
possible problem. Explanation: The current operation failed due to the
current Linux system call.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813123 B1813123
B181312B B181312B
Explanation: Operation to call home has failed.
Explanation: The operation to unload the file headers
Response: If this is a tracking event, no service actions
into the error log file system failed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813125 B1813125
Explanation: The error log server failed to initialize its
B181312C B181312C
file system.
Explanation: The operation failed due to the
Response: If this is a tracking event, no service actions
secondary service processor not responding during the
are required. Otherwise, use the FRU and procedure
alloted time.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
280 System reference codes (Bxxx)
B181312D • B1813205
are required. Otherwise, use the FRU and procedure
B181312D B181312D
callouts detailed with the SRC to determine service
Explanation: Failed to initialize the P3 statistics file. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181313E B181313E
callouts detailed with the SRC to determine service
Explanation: A generic unknown failure was received;
actions.
current error log operation failed.
Response: If this is a tracking event, no service actions
B181312E B181312E
are required. Otherwise, use the FRU and procedure
Explanation: The error log server detected a possibly callouts detailed with the SRC to determine service
fatal hardware error in the service processor flash. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1813201 B1813201
callouts detailed with the SRC to determine service
Explanation: A bad command argument was passed
actions.
to IPLP.
Response: If this is a tracking event, no service actions
B181312F B181312F
are required. Otherwise, use the FRU and procedure
Explanation: The error log server detected a possibly callouts detailed with the SRC to determine service
fatal hardware error in the service processor flash. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1813202 B1813202
callouts detailed with the SRC to determine service
Explanation: The argument after "iplp speed_override"
actions.
is missing.
Response: If this is a tracking event, no service actions
B1813130 B1813130
are required. Otherwise, use the FRU and procedure
Explanation: The data synchronization thread on the callouts detailed with the SRC to determine service
error logging server was not started. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1813203 B1813203
callouts detailed with the SRC to determine service
Explanation: The argument after "iplp speed_override"
actions.
was invalid in a command.
Response: If this is a tracking event, no service actions
B1813131 B1813131
are required. Otherwise, use the FRU and procedure
Explanation: The data sync thread was cancelled. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1813204 B1813204
actions.
Explanation: iplp_process_msg recevied an invalid
operation code.
B1813132 B1813132
Response: If this is a tracking event, no service actions
Explanation: The role c hanged are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1813205 B1813205
Explanation: Invalid number of arguments in a
B1813133 B1813133 command.
Explanation: The event monitor detected that the Response: If this is a tracking event, no service actions
sibling service processor's (or system controller's) state are required. Otherwise, use the FRU and procedure
changed. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
(B1xx) Reference codes 281
B1813206 • B181321E
B1813206 B1813206 B1813219 B1813219
Explanation: An error occurred reserving the Explanation: Invalid data received for
iplpInterface semaphore. NextSystemIplMode.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813207 B1813207 B181321A B181321A
Explanation: An iplp application received a signal. Explanation: Invalid data received for
NextPlatformIplSpeed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813208 B1813208
B181321B B181321B
Explanation: A side-switching boot is not allowed for
the given CecIplType. Explanation: Invalid data received for
NextPlatformIplSpeedOverride.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813209 B1813209
B181321C B181321C
Explanation: A side-switch reboot failed; firmware is
not valid on the new NextSide. Explanation: Invalid data received for
NextHypervisorIplState.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813217 B1813217
B181321D B181321D
Explanation: Invalid data was received for
SysClickToAcceptState. Explanation: Invalid data received for
NextRpaPartitionIplMode.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813218 B1813218
B181321E B181321E
Explanation: Invalid data received for
NextPlatformIplSide. Explanation: Invalid data received for
NextCecLmbSize.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
282 System reference codes (Bxxx)
B1813221 • B181322F
callouts detailed with the SRC to determine service
B1813221 B1813221
actions.
Explanation: The iplpRegMon daemon discovered that
the P2 registry was recently cleared, and all entries
B1813229 B1813229
were set back to default values. Some customer settings
may have been lost. If the P2 registry was not Explanation: The argument after 'iplp
intentionally cleared, it's possible that there's a set_maxiplspeed' is invalid.
firmware or hardware problem with the service
processor. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181322A B181322A
B1813222 B1813222 Explanation: The argument after 'iplp
set_maxiplspeed' is missing.
Explanation: The iplpRegMon daemon could not get
the lock. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181322B B181322B
B1813223 B1813223 Explanation: The service processor is no longer
booting in hyperboot.
Explanation: A task failed to fork.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181322C B181322C
B1813224 B1813224
Explanation: Informational message: The IPL speed
Explanation: The service processor was rebooted due was changed.
to invalid registry data.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181322D B181322D
B1813226 B1813226
Explanation: A firmware installation was done, so the
Explanation: The interface that was called is not next system boot will not be in hyperboot.
supported in the current context.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181322F B181322F
B1813228 B1813228
Explanation: The hypervisor's IPL state was modified.
Explanation: A side-switching IPL is needed, but the
firmware on the secondary service processor is not Response: If this is a tracking event, no service actions
valid. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 283
B1813302 • B1813323
B1813302 B1813302 B181330B B181330B
Explanation: An internal service processor time-of-day Explanation: An error log could not be properly
process did not complete successfully. constructed by the time-of-day process.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813306 B1813306 B181330D B181330D
Explanation: Invalid data was received by an service Explanation: The service processor time-of-day
processor time-of-day function. process encountered a fatal error and had to be
restarted. Install all server firmware updates, if
Response: If this is a tracking event, no service actions
available, before any hardware is replaced.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813307 B1813307
Explanation: An attempt was made to set the service
B181330F B181330F
processor's time-of-day when the service processor was
not at standby. Explanation: An error was returned from the real time
clock ADAL.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813308 B1813308
B181331C B181331C
Explanation: A service processor device driver
returned an error. Explanation: An invalid time-of-day operation request
was received by the service processor, most likely from
Response: If this is a tracking event, no service actions
the HMC.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813309 B1813309
Explanation: An error occurred while reading
B1813322 B1813322
time-of-day function parameters from service processor
storage. Explanation: An internal service processor process
could not get exclusive access to resources that were
Response: If this is a tracking event, no service actions
needed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181330A B181330A
Explanation: An error occurred while writing to the
B1813323 B1813323
service processor time-of-day clock. Install all server
firmware updates before any hardware is replaced. Explanation: An internal service processor time-of-day
process failed to start.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
284 System reference codes (Bxxx)
B1813326 • B181340F
B1813326 B1813326 B1813409 B1813409
Explanation: An internal service processor time-of-day Explanation: A state transition requested by the user
process failed to start. or system was rejected because transitioning from the
current state to the requested state is not supported.
Response: If this is a tracking event, no service actions
State transitions are generated by both the system and
are required. Otherwise, use the FRU and procedure
user as a part of boot sequences, service processor
callouts detailed with the SRC to determine service
failover, service processor reset/reload and a system
actions.
failure (checkstop, TI, termination).
Response: If this is a tracking event, no service actions
B1813327 B1813327
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred while the hypervisor callouts detailed with the SRC to determine service
was attempting to set the service processor's actions.
time-of-day clock. This is a temporary error that may
indicate that the command took too long to process and
B181340A B181340A
had to be repeated.
Explanation: Terminate request was received from
Response: If this is a tracking event, no service actions
non-CTRM.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181332A B181332A
Explanation: An internal service processor time-of-day
B181340C B181340C
process failed to start.
Explanation: Registry size to data mismatch.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813403 B1813403
B181340D B181340D
Explanation: Failure trying to fork the smgrinit
process. Explanation: Registry data incorrect
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813406 B1813406 B181340E B181340E
Explanation: Unable to allocate storage. Explanation: Registry read failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813407 B1813407 B181340F B181340F
Explanation: Unable to write MSQueue. Explanation: Registry write failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 285
B1813410 • B181342B
B1813410 B1813410 B1813421 B1813421
Explanation: Call to a service processor initialization Explanation: There was an error synchronizing the
routine failed trans handler and request handler threads with a
message.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813411 B1813411
B1813422 B1813422
Explanation: Read in do_dump failed.
Explanation: Bad message passed to trans handler
Response: If this is a tracking event, no service actions
thread.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813413 B1813413
Explanation: The state manager's state was set to
B1813423 B1813423
invalid.
Explanation: Error reading data from internal mapfile
data.
B181341A B181341A
Response: If this is a tracking event, no service actions
Explanation: Smgrinit has failed to open /proc/reset/.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813425 B1813425
Explanation: The request to reboot the service
B181341C B181341C
processor was returned or it failed.
Explanation: Smgrinit has failed to decode the reset
Response: If this is a tracking event, no service actions
values.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813426 B1813426
Explanation: Incorrect map data, or no map data, for
B181341D B181341D
the IPL request type.
Explanation: Smgrinit has failed to build the message
Response: If this is a tracking event, no service actions
queue.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181342A B181342A
Explanation: A parameter was out of range.
B181341E B181341E
Explanation: The system was powered on with service
B181342B B181342B
processor failover disabled, even though a functional
secondary service processor is installed. Explanation: Reading the MNFG flag for reset/reload
failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions.
286 System reference codes (Bxxx)
B1813430 • B181345E
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813430 B1813430
B1813443 B1813443
Explanation: Smgr client library has been passed a
bad parameter. Explanation: There was an error reading the specified
file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813431 B1813431
B1813444 B1813444
Explanation: Smgr client lib has detected an extneral
error. Explanation: The exec to run the command to reboot
all node controllers failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813433 B1813433
B1813445 B1813445
Explanation: Smgr client lib has failed to synchronize
with server. Explanation: Unable to get a valid value from a
function.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813436 B1813436
B1813446 B1813446
Explanation: Validation of the persistent control
storage failed. Explanation: The exec to run the command to reboot
all node controllers failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813438 B1813438
B1813450 B1813450
Explanation: A power cycle reset request was
received. Explanation: A sub-segment (transition file script) of
the boot process (power on, power off, or a recovery
Response: If this is a tracking event, no service actions
action like fail-over or reset/reload) was hung and
are required. Otherwise, use the FRU and procedure
timed out.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813440 B1813440
actions.
Explanation: A counter's time stamp was incorrect.
B181345E B181345E
B1813442 B1813442
Explanation: Call to a service processor initialization
Explanation: A time-out occurred while waiting to routine failed
unlock the file so that is could be read.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 287
B1813463 • B1813518
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813463 B1813463 B1813513 B1813513
Explanation: An unsupported level of system Explanation: An error was returned from a function
firmware has been detected. Go to Fix Central Web site call.
at http://www.ibm.com/support/fixcentral/ for the
Response: If this is a tracking event, no service actions
recovery procedure documented in the latest firmware
are required. Otherwise, use the FRU and procedure
description file for your machine type and model, or
callouts detailed with the SRC to determine service
contact next level of support.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813514 B1813514
callouts detailed with the SRC to determine service
actions. Explanation: An error was returned from a function
call.
B1813502 B1813502 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned from a function
callouts detailed with the SRC to determine service
call.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813515 B1813515
callouts detailed with the SRC to determine service
actions. Explanation: An error was returned from a function
call.
B1813503 B1813503 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: There was an error opening the sys
callouts detailed with the SRC to determine service
entry.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813516 B1813516
callouts detailed with the SRC to determine service
actions. Explanation: An error was returned from a function
call.
B1813504 B1813504 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: error returned from exchangeBootSide()
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813517 B1813517
actions.
Explanation: An error was returned when trying to
connect to the sibling service processor or system
B1813505 B1813505
controller.
Explanation: error returned from
Response: If this is a tracking event, no service actions
exchangeFspIPLType()
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813518 B1813518
Explanation: An error was returned from a function
B1813506 B1813506
call.
Explanation:
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
actions.
288 System reference codes (Bxxx)
B1813519 • B1813524
B1813519 B1813519 B181351F B181351F
Explanation: An error was returned from a function Explanation: An error was returned from a function
call. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181351A B181351A B1813520 B1813520
Explanation: When checking the guard state, the Explanation: There was an error when reading the
sibling service processor or system controller was service processor's state.
found to be guarded out.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813521 B1813521
B181351B B181351B
Explanation: An error was returned from a function
Explanation: The response from the machine-type, call.
model, and serial number exchange was empty.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813522 B1813522
B181351C B181351C
Explanation: Error returned from
Explanation: An error occurred when attempting to goodPathRelationDetermination()
create an address object.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813523 B1813523
B181351D B181351D
Explanation: Error returned from sibling when
Explanation: An error occurred when attempting to requesting that he sets up his role
create an address object.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813524 B1813524
B181351E B181351E
Explanation: An error was returned from a function
Explanation: An error was returned from a function call.
call.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 289
B1813525 • B1813530
B1813525 B1813525 B181352B B181352B
Explanation: An error was returned from a function Explanation: Error returned from an information
call. exchange function
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813526 B1813526 B181352C B181352C
Explanation: An unsupported command was received Explanation: An error was returned from a function
from the sibling service processor or system controller. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813527 B1813527 B181352D B181352D
Explanation: The response from the secondary service Explanation: An error was returned from a function
processor contains no data. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813528 B1813528 B181352E B181352E
Explanation: Error returned from setAddressObj() Explanation: An error was returned when attempting
to switch sides.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813529 B1813529
B181352F B181352F
Explanation: An error was returned from a function
call. Explanation: An error was returned from a function
call.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181352A B181352A
B1813530 B1813530
Explanation: Error returned from setSiblingState()
Explanation: A sibling was detected, but the
Response: If this is a tracking event, no service actions
communication lines broke down, and the error
are required. Otherwise, use the FRU and procedure
threshold was exceeded.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
290 System reference codes (Bxxx)
B1813531 • B181353C
B1813531 B1813531 B1813537 B1813537
Explanation: An error was returned from a function Explanation: An error was returned from a function
call. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813532 B1813532 B1813538 B1813538
Explanation: An error was returned from a function Explanation: An error was returned from a function
call. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813533 B1813533 B1813539 B1813539
Explanation: An error was returned from a function Explanation: An error was returned from a function
call. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813534 B1813534 B181353A B181353A
Explanation: An error was returned from a function Explanation: The data read from the I/O multiplexor
call. did not equal the data written.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813535 B1813535 B181353B B181353B
Explanation: An error was returned from a function Explanation: An error was returned from a function
call. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813536 B1813536 B181353C B181353C
Explanation: An error was returned from a function Explanation: An error was returned from a function
call. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 291
B181353D • B181354A
B181353D B181353D B1813543 B1813543
Explanation: Error returned from Explanation: There was an error returned from a
rdal_fsi_ffdc_extract() utility when getting data.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181353E B181353E B1813544 B1813544
Explanation: An error was returned from the role Explanation: An error occurred when reading data.
determination object.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813545 B1813545
B181353F B181353F
Explanation: Undefined position data was read.
Explanation: An error was returned from a function
Response: If this is a tracking event, no service actions
call.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813546 B1813546
Explanation: An error was returned from a function
B1813540 B1813540
call.
Explanation: An error was returned from a function
Response: If this is a tracking event, no service actions
call.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813548 B1813548
Explanation: A call was made to set the error number.
B1813541 B1813541
Response: If this is a tracking event, no service actions
Explanation: An error was returned from a function
are required. Otherwise, use the FRU and procedure
call.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813549 B1813549
actions.
Explanation: An undefined sibling state was passed
into a function call.
B1813542 B1813542
Response: If this is a tracking event, no service actions
Explanation: Undefined data was received from the
are required. Otherwise, use the FRU and procedure
sibling service processor or system controller.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181354A B181354A
actions.
Explanation: An error was returned from a function
call.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
292 System reference codes (Bxxx)
B181354B • B1813557
callouts detailed with the SRC to determine service
B1813552 B1813552
actions.
Explanation: An error was returned when trying to
read a keyword.
B181354B B181354B
Response: If this is a tracking event, no service actions
Explanation: There was an error when reading the
are required. Otherwise, use the FRU and procedure
service processor's state.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813553 B1813553
actions.
Explanation: There was an error when reading the
service processor's state.
B181354C B181354C
Response: If this is a tracking event, no service actions
Explanation: An error was returned from a function
are required. Otherwise, use the FRU and procedure
call.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813554 B1813554
actions.
Explanation: The amount of data that was read was
not expected.
B181354D B181354D
Response: If this is a tracking event, no service actions
Explanation: An error was returned from a function
are required. Otherwise, use the FRU and procedure
call.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813555 B1813555
actions.
Explanation: An error was returned from a function
call.
B181354F B181354F
Response: If this is a tracking event, no service actions
Explanation: Timed out waiting for GPIO device to
are required. Otherwise, use the FRU and procedure
appear
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813556 B1813556
actions.
Explanation: An error was returned from a function
call.
B1813550 B1813550
Response: If this is a tracking event, no service actions
Explanation: An artificially injected error used for
are required. Otherwise, use the FRU and procedure
debugging
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813557 B1813557
actions.
Explanation: An error was returned from a function
call.
B1813551 B1813551
Response: If this is a tracking event, no service actions
Explanation: An error was returned from a function
are required. Otherwise, use the FRU and procedure
call.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 293
B1813558 • B1813564
B1813558 B1813558 B181355F B181355F
Explanation: An error was returned from a function Explanation: There was an error in opening the sys
call. entry.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813559 B1813559 B1813560 B1813560
Explanation: An error was returned from a function Explanation: Error returned from rdal_iomux_seek()
call.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813561 B1813561
B181355B B181355B
Explanation: An error was returned from a function
Explanation: Error returned from adal_mbx_open() call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181355C B181355C B1813562 B1813562
Explanation: There was an error in the data received Explanation: There was an error in the call to another
from the sibling service processor. component interface.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181355D B181355D B1813563 B1813563
Explanation: There was an error in the call to another Explanation: An error was returned from a function
firmware component interface. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181355E B181355E B1813564 B1813564
Explanation: There was an error when reading 1 byte Explanation: Error returned from
from the SYS entry. rdal_iomux_query_state()
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
294 System reference codes (Bxxx)
B1813565 • B1813576
B1813565 B1813565 B1813571 B1813571
Explanation: An error was returned from a function Explanation: The rdal_jtag_shift_data interface for
call. JTAG returned an error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813566 B1813566 B1813572 B1813572
Explanation: A command to start VPD sync returned Explanation: The rdal_gpio_write_pin interface
an error. returned an error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813567 B1813567 B1813573 B1813573
Explanation: A n error was returned from a function Explanation: The rdal_gpio_open interface returned an
call. error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813568 B1813568 B1813574 B1813574
Explanation: setsocketopt system call failed. Explanation: An error was returned from a function
call.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813569 B1813569
B1813575 B1813575
Explanation: The getsockopt system call returned an
error. Explanation: The rdal_jtag_open interface returned an
error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813570 B1813570
B1813576 B1813576
Explanation: The rdal_jtag_shift_cmd interface for
JTAG returned an error. Explanation: An error was returned while waiting for
JTAG-lock.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 295
B1813577 • B1813582
B1813577 B1813577 B181357D B181357D
Explanation: The rdal_gpio_open interface returned an Explanation: An error was returned from an interface
error. to the sibling service processor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813578 B1813578 B181357E B181357E
Explanation: An error was returned from Explanation: An error was returned from an interface
rdal_gpio_set_mode. to the sibling service processor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813579 B1813579 B181357F B181357F
Explanation: The ppcdbg_open_jtag interface for JTAG Explanation: An error was returned from a function
returned an error. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181357A B181357A B1813580 B1813580
Explanation: An error was returned from an interface Explanation: An error was returned from a function
to the sibling service processor. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181357B B181357B B1813581 B1813581
Explanation: An error was returned from an interface Explanation: An error was returned when setting up
to the sibling service processor. or triggering a kernel panic.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181357C B181357C B1813582 B1813582
Explanation: An error was returned from a function Explanation: An error was returned from a function
call. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
296 System reference codes (Bxxx)
B1813583 • B181358E
B1813583 B1813583 B1813589 B1813589
Explanation: An error occurred when trying to read Explanation: Data of incorrect length was read from
the sibling service processor's scratch pad register. the VSRC block.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813584 B1813584 B181358A B181358A
Explanation: There was an error when writing to the Explanation: An error was returned from an open
mailbox. command.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813585 B1813585 B181358B B181358B
Explanation: An error occurred when setting up or Explanation: An error was returned from a seek
reading the cable ID. command.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813586 B1813586 B181358C B181358C
Explanation: An error was returned from a function Explanation: An error was returned from a write
call. command.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813587 B1813587 B181358D B181358D
Explanation: There was an error when closing the FSI Explanation: An error was received when trying to
device. write a trace file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813588 B1813588 B181358E B181358E
Explanation: Vital product data (VPD) collection was Explanation: An error was returned from a write
disabled because of previous VPD collection failures. command.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 297
B181358F • B181359B
B181358F B181358F B1813596 B1813596
Explanation: There was an error when checking the Explanation: The position file contained undefined
I/O multiplexer state. data.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813590 B1813590 B1813597 B1813597
Explanation: Timed out waiting for the GPIO device Explanation: An error was returned from
to appear. utilreg::write.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813591 B1813591 B1813598 B1813598
Explanation: There was an error when collecting the Explanation: A n error was returned from Util when
system VPD when known to own local bus zero. closing the service processor position file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813593 B1813593 B1813599 B1813599
Explanation: An error was returned from util when Explanation: A sscanf call was made to set the error
opening the position file. number.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813594 B1813594 B181359A B181359A
Explanation: The position file does not exist. Explanation: An undefined sibling state was passed
into setSiblingState().
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813595 B1813595
B181359B B181359B
Explanation: An error occurred when reading the
position file. Explanation: An error was returned from utilreg::read.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
298 System reference codes (Bxxx)
B181359C • B18135A7
B181359C B181359C B18135A2 B18135A2
Explanation: An error was returned from Explanation: An error was returned from
ReadScratchPadReg(). rdal_fsi_ffdc_extract().
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181359D B181359D B18135A3 B18135A3
Explanation: An error was returned from Explanation: An error was returned from the role
SVPD_collect_system_vpd determination object.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181359E B181359E B18135A4 B18135A4
Explanation: An error was returned from Explanation: An error was returned from setFspRole().
ReadCableID()
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18135A5 B18135A5
B181359F B181359F
Explanation: An error was returned from sendRcv().
Explanation: The data read from the IOMux was not
Response: If this is a tracking event, no service actions
equal to the data that was written.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B18135A6 B18135A6
Explanation: An error was returned from
B18135A0 B18135A0
setupSibling().
Explanation: An error was returned from
Response: If this is a tracking event, no service actions
rdal_iomux_close().
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B18135A7 B18135A7
Explanation: An error was returned from
B18135A1 B18135A1
getCmdResponse().
Explanation: An error was returned from
Response: If this is a tracking event, no service actions
rdal_iomux_ffdc_extract().
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 299
B18135A8 • B18135B3
B18135A8 B18135A8 B18135AE B18135AE
Explanation: An error was returned from Explanation: An error was returned from
readNvramMTMS(). goodPathRelationDetermination().
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18135A9 B18135A9 B18135AF B18135AF
Explanation: An error was returned from Explanation: An error was returned from the sibling
CollectSystemVPD(). service processor when requesting that it set up its role.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18135AA B18135AA B18135B0 B18135B0
Explanation: An error was returned from is Explanation: Returned error from
FSPGarded(). SingleFSP_CommFail_RoleDeter mination()
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18135AB B18135AB B18135B1 B18135B1
Explanation: An error was returned from Explanation: An error was returned becomeSlave().
ReadVSRCBlock().
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18135B2 B18135B2
B18135AC B18135AC
Explanation: An error was returned from
Explanation: An error was returned from becomeMaster().
ReadFSPSerialNumbers().
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18135B3 B18135B3
B18135AD B18135AD
Explanation: An error was returned from
Explanation: An error was returned from CheckVPDAndDetermineRole().
recvRoleCmd().
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
300 System reference codes (Bxxx)
B18135B4 • B18135BF
B18135B4 B18135B4 B18135BA B18135BA
Explanation: An undefined command was received Explanation: An error was returned from
from the sibling service processor. dscvReadFspState().
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18135B5 B18135B5 B18135BB B18135BB
Explanation: The response from the secondary service Explanation: An error was returned from
processor contained no data. PrimarySideCheck().
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18135B6 B18135B6 B18135BC B18135BC
Explanation: An error was returned from Explanation: An error was returned from iplp when
setAddressObj(). attempting to switch sides.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18135B7 B18135B7 B18135BD B18135BD
Explanation: An error was returned from Explanation: An error was returned
incrementReEntrant(). SecondarySideCheck().
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18135B8 B18135B8 B18135BE B18135BE
Explanation: An error was returned from Explanation: An error was returned from
setSiblingState(). GardGetFspState().
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18135B9 B18135B9 B18135BF B18135BF
Explanation: An error was returned from an Explanation: An error was returned when trying to
information exchange function. connect to the sibling
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 301
B18135C0 • B1813801
B18135C0 B18135C0 B181360C B181360C
Explanation: An error was returned from Explanation: A function call failed.
GetSiblingFSIState().
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181360E B181360E
B18135C1 B18135C1
Explanation: An event detection failure occurred.
Explanation: An error was returned from
Response: If this is a tracking event, no service actions
netsConnectServer().
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813613 B1813613
Explanation: A firmware failure caused a signal to be
B18135C2 B18135C2
received.
Explanation: An error log entry to record the sibling
Response: If this is a tracking event, no service actions
service processor's status was made.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813614 B1813614
Explanation: The event loop exited.
B18135C3 B18135C3
Response: If this is a tracking event, no service actions
Explanation: While making the connection to establish
are required. Otherwise, use the FRU and procedure
the handshake, the message from the sibling service
callouts detailed with the SRC to determine service
processor contained no data.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813615 B1813615
callouts detailed with the SRC to determine service
actions. Explanation: A call to chdir failed.
Response: If this is a tracking event, no service actions
B1813603 B1813603 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A function failed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813616 B1813616
callouts detailed with the SRC to determine service
actions. Explanation: A function call failed.
Response: If this is a tracking event, no service actions
B1813608 B1813608 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A host ADAL or registry failure
actions.
occurred.
Response: If this is a tracking event, no service actions
B1813801 B1813801
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to open a multiplexer
actions. configuration file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
302 System reference codes (Bxxx)
B1813802 • B1813810
callouts detailed with the SRC to determine service
B1813802 B1813802
actions.
Explanation: An ERC file read failed.
Response: If this is a tracking event, no service actions B181380B B181380B
are required. Otherwise, use the FRU and procedure
Explanation: Failed to read the service processor's
callouts detailed with the SRC to determine service
position from the registry.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813803 B1813803
callouts detailed with the SRC to determine service
Explanation: A FRU manager (FRUM) even failure actions.
occurred.
Response: If this is a tracking event, no service actions B181380C B181380C
are required. Otherwise, use the FRU and procedure
Explanation: Failed to write the watchdog-complete
callouts detailed with the SRC to determine service
key to the registry.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813805 B1813805
callouts detailed with the SRC to determine service
Explanation: Failed to fork the process. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181380D B181380D
callouts detailed with the SRC to determine service
Explanation: Failed to write the configuration change
actions.
key to the registry.
Response: If this is a tracking event, no service actions
B1813807 B1813807
are required. Otherwise, use the FRU and procedure
Explanation: Failed to unflatten the error log from the callouts detailed with the SRC to determine service
network message. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181380E B181380E
callouts detailed with the SRC to determine service
Explanation: The key that was requested from the
actions.
registry is not valid for this function.
Response: If this is a tracking event, no service actions
B1813808 B1813808
are required. Otherwise, use the FRU and procedure
Explanation: Failed to read the path from the registry. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181380F B181380F
actions.
Explanation: Failed to set the synchronization file for
the client.
B1813809 B1813809
Response: If this is a tracking event, no service actions
Explanation: Failed to read the sibling service are required. Otherwise, use the FRU and procedure
processor's state from the registry. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1813810 B1813810
actions.
Explanation: Failed to synchronize with the field
replaceable unit (FRU) manager server.
B181380A B181380A
Response: If this is a tracking event, no service actions
Explanation: Failed to read the service processor's role are required. Otherwise, use the FRU and procedure
from the registry. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 303
B1813811 • B181381D
callouts detailed with the SRC to determine service
B1813811 B1813811
actions.
Explanation: Failed to send a network message.
Response: If this is a tracking event, no service actions B1813818 B1813818
are required. Otherwise, use the FRU and procedure
Explanation: Failed to listen on the network server
callouts detailed with the SRC to determine service
address.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813812 B1813812
callouts detailed with the SRC to determine service
Explanation: Failed to receive a network message. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1813819 B1813819
callouts detailed with the SRC to determine service
Explanation: Failed to listen for a network server
actions.
connection.
Response: If this is a tracking event, no service actions
B1813813 B1813813
are required. Otherwise, use the FRU and procedure
Explanation: Failed to establish communication with callouts detailed with the SRC to determine service
server. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181381A B181381A
callouts detailed with the SRC to determine service
Explanation: Failed to initialize the thread attribute
actions.
variable.
Response: If this is a tracking event, no service actions
B1813814 B1813814
are required. Otherwise, use the FRU and procedure
Explanation: Failed to close an open socket. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181381B B181381B
actions.
Explanation: Failed to set the thread attribute variable.
Response: If this is a tracking event, no service actions
B1813815 B1813815
are required. Otherwise, use the FRU and procedure
Explanation: Failed to create the network client callouts detailed with the SRC to determine service
address object. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181381C B181381C
callouts detailed with the SRC to determine service
Explanation: Failed to create the monitor thread.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813816 B1813816
callouts detailed with the SRC to determine service
Explanation: Failed to create the network server actions.
address object.
Response: If this is a tracking event, no service actions B181381D B181381D
are required. Otherwise, use the FRU and procedure
Explanation: Failed to lock the device list mutex.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813817 B1813817
actions.
Explanation: Failed to find the network address
server.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
304 System reference codes (Bxxx)
B181381E • B1813829
B181381E B181381E B1813824 B1813824
Explanation: An error occurred when unlocking a Explanation: The message that was received does not
mutex thread. contain data about a device from the caller list.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181381F B181381F B1813825 B1813825
Explanation: Failed to wait for the mutex conditional. Explanation: The ACTION environment variable was
missing.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813820 B1813820
B1813826 B1813826
Explanation: A parameter passed into a function is
not valid. Explanation: No ERC event sequence variable was
found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813821 B1813821
B1813827 B1813827
Explanation: An error occurred when reading from or
writing to the message buffer. Explanation: The DEVPATH environment variable
was missing.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813822 B1813822
B1813828 B1813828
Explanation: The message type that was received is
not valid. Explanation: The CFAM environment variable was
missing.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813823 B1813823
B1813829 B1813829
Explanation: Message flags were received that indicate
this was not a response message. Explanation: The LINK environment variable was
missing.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 305
B181382D • B181383B
are required. Otherwise, use the FRU and procedure
B181382D B181382D
callouts detailed with the SRC to determine service
Explanation: A subsystem type argument was actions.
missing.
Response: If this is a tracking event, no service actions B1813835 B1813835
are required. Otherwise, use the FRU and procedure
Explanation: Failed to get a device list to validate.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181382E B181382E
actions.
Explanation: Failed to create an event manager object.
Response: If this is a tracking event, no service actions B1813836 B1813836
are required. Otherwise, use the FRU and procedure
Explanation: An ERC validation mismatch occurred.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181382F B181382F
actions.
Explanation: Failed to look for events from the list.
Response: If this is a tracking event, no service actions B1813837 B1813837
are required. Otherwise, use the FRU and procedure
Explanation: There was an ERC validation mismatch.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813830 B1813830
actions.
Explanation: An unknown event was received.
Response: If this is a tracking event, no service actions B1813838 B1813838
are required. Otherwise, use the FRU and procedure
Explanation: Validation of the device list failed due to
callouts detailed with the SRC to determine service
the lists being disjointed, missing primary devices, or
actions.
missing backup devices.
Response: If this is a tracking event, no service actions
B1813831 B1813831
are required. Otherwise, use the FRU and procedure
Explanation: Failed to send an event for CFAM. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1813839 B1813839
actions.
Explanation: ERC forced a device addition.
Response: If this is a tracking event, no service actions
B1813833 B1813833
are required. Otherwise, use the FRU and procedure
Explanation: An "add event" for a device has been callouts detailed with the SRC to determine service
received twice. This indicates a problem with hot-plug actions.
processing.
Response: If this is a tracking event, no service actions B181383B B181383B
are required. Otherwise, use the FRU and procedure
Explanation: The node that was requested is out of
callouts detailed with the SRC to determine service
range.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813834 B1813834
callouts detailed with the SRC to determine service
Explanation: A "removal event" for a device has been actions.
received twice. This indicates a problem with hot-plug
processing.
Response: If this is a tracking event, no service actions
306 System reference codes (Bxxx)
B181383C • B1813864
B181383C B181383C B1813852 B1813852
Explanation: Failed to get the node status or device Explanation: The size was incorrect for the I/O
driver level. multiplexor configuration file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181383D B181383D B1813860 B1813860
Explanation: Failed to get the hot-plug event list, or Explanation: Failed to extract the
the vector size was zero. first-failure-data-capture (FFDC) data for the I/O
multiplexor device driver.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181383F B181383F
B1813861 B1813861
Explanation: Failed to guard out the secondary service
processor. Explanation: Failed to unlock the failure data for a
multiplexer device driver.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813840 B1813840
B1813862 B1813862
Explanation: The local bus grab operation failed.
Explanation: Failed to open a multiplexer device
Response: If this is a tracking event, no service actions
driver.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813850 B1813850
Explanation: The multiplexer configuration key is not
B1813863 B1813863
valid with the sibling state change.
Explanation: Failed to close a multiplexer device
Response: If this is a tracking event, no service actions
driver.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813851 B1813851
Explanation: The actual I/O multiplexor size does not
B1813864 B1813864
equal the saved control data size.
Explanation: Failed to reposition the read/write offset
Response: If this is a tracking event, no service actions
for the multiplexer device driver.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 307
B1813865 • B1813877
callouts detailed with the SRC to determine service
B1813865 B1813865
actions.
Explanation: Failed to get the state of a multiplexer
device driver.
B1813871 B1813871
Response: If this is a tracking event, no service actions
Explanation: Failed to unlock the failure data for a
are required. Otherwise, use the FRU and procedure
device driver.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813866 B1813866
actions.
Explanation: Failed to validate a multiplexer through
a device driver.
B1813872 B1813872
Response: If this is a tracking event, no service actions
Explanation: Failed to open a device driver.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813867 B1813867
Explanation: Failed to mark a multiplexer as not valid
B1813873 B1813873
through a device driver.
Explanation: Failed to close a device driver.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1813868 B1813868
B1813874 B1813874
Explanation: Failed to write to a multiplexer.
Explanation: Failed to configure a communication link
Response: If this is a tracking event, no service actions
to a device driver.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813869 B1813869
Explanation: Failed to read from a multiplexer.
B1813876 B1813876
Response: If this is a tracking event, no service actions
Explanation: Failed to configure the I2C bus.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181386A B181386A
Explanation: Failed to get the size of a multiplexer.
B1813877 B1813877
Response: If this is a tracking event, no service actions
Explanation: Failed to close the I2C device driver.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1813870 B1813870
Explanation: Failed to extract the failure data for a
device driver.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
308 System reference codes (Bxxx)
B1813878 • B18138A0
B1813878 B1813878 B1813883 B1813883
Explanation: Failed to extract the "first failure data Explanation: Failed to close a device driver.
capture" data from the I2C device driver.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813884 B1813884
B1813879 B1813879
Explanation: Failed to set the mode.
Explanation: Failed to unlock the FFDC for the IIC
Response: If this is a tracking event, no service actions
device driver.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813885 B1813885
Explanation: Failed to write to the output pins on the
B181387A B181387A
GPIO.
Explanation: Failed to open the I2C device driver.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813886 B1813886
B1813880 B1813880
Explanation: Failed to set the blink rate.
Explanation: Failed to extract the failure data for a
Response: If this is a tracking event, no service actions
device driver.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813891 B1813891
Explanation: Configuration file size is not valid.
B1813881 B1813881
Response: If this is a tracking event, no service actions
Explanation: Failed to unlock the failure data for a
are required. Otherwise, use the FRU and procedure
device driver.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813892 B1813892
actions.
Explanation: Configuration file key is not valid.
B1813882 B1813882 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to open a device driver.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18138A0 B18138A0
actions.
Explanation: Failure detected in a communication
link.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 309
B18138A1 • B18138B8
B18138A1 B18138A1 B18138B3 B18138B3
Explanation: An error occurred when initializing the Explanation: Failed to set the I2C bus frequency.
mutex attribute.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138B4 B18138B4
B18138A2 B18138A2
Explanation: A time-out occurred while waiting on
Explanation: An error occurred when setting the the status of the devices.
mutex attribute type.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138B5 B18138B5
B18138A3 B18138A3
Explanation: There was time-out from the devlist
Explanation: An error was returned from a mutex server.
thread initialization.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138B6 B18138B6
B18138B0 B18138B0
Explanation: An invalid callout file size was found.
Explanation: An unrecovered FSI error was detected.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138B7 B18138B7
B18138B1 B18138B1
Explanation: ERC forced the configuration timer to
Explanation: The maximum number of recovered FSI expire.
errors was reached.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138B8 B18138B8
B18138B2 B18138B2
Explanation: ERC deferred setcc; no primary service
Explanation: A failover could not be initiated because processor was found.
rmgrBackupFailoverCapability indicates that it is not
Response: If this is a tracking event, no service actions
allowed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
310 System reference codes (Bxxx)
B18138B9 • B18138C9
B18138B9 B18138B9 B18138C3 B18138C3
Explanation: ERC deferred setcc; local devices are Explanation: An ERC RDAL SCAN failed to close.
missing.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138C4 B18138C4
B18138BA B18138BA
Explanation: An ERC RDAL SCAN failed to extract
Explanation: ERC deferred setcc; node devices are the FFDC (first failure data capture) information.
missing.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138C5 B18138C5
B18138BB B18138BB
Explanation: An ERC RDAL SCAN failed to unlock
Explanation: Setting the primary node controller the FFDC (first failure data capture) information.
failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138C7 B18138C7
B18138C0 B18138C0
Explanation: An ERC RDAL SCAN failed to extract
Explanation: An ERC RDAL SCAN failed to open. the FFDC (first failure data capture) information
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18138C1 B18138C1 B18138C8 B18138C8
Explanation: An ERC RDAL SCAN failed to get the Explanation: An ERC RDAL SCAN failed to get the
pulse length. GP1 value.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18138C2 B18138C2 B18138C9 B18138C9
Explanation: An ERC RDAL SCAN failed to set the Explanation: Failed to write the SCOM GP1 register.
pulse length.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 311
B18138CA • B18138D6
B18138CA B18138CA B18138D0 B18138D0
Explanation: An ERC RDAL SCAN failed to reset. Explanation: A netlink socket connection operation
failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18138CB B18138CB
B18138D1 B18138D1
Explanation: An ERC RDAL SCAN failed to get the
arbiter. Explanation: A netlink socket send operation failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18138CC B18138CC B18138D2 B18138D2
Explanation: An ERC RDAL SCAN failed to set the Explanation: A netlink socket send operation failed.
arbiter.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138D3 B18138D3
B18138CD B18138CD
Explanation: A netlink socket receive operation failed.
Explanation: An ERC RDAL SCAN failed to close.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18138D4 B18138D4
B18138CE B18138CE
Explanation: A netlink socket receive operation failed.
Explanation: An ERC RDAL SCAN failed to extract
Response: If this is a tracking event, no service actions
the FFDC (first failure data capture) information.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B18138D5 B18138D5
Explanation: A netlink socket receive operation failed.
B18138CF B18138CF
Response: If this is a tracking event, no service actions
Explanation: An ERC RDAL SCAN failed to unlock
are required. Otherwise, use the FRU and procedure
the FFDC (first failure data capture) information.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18138D6 B18138D6
actions.
Explanation: A netlink socket receive operation failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
312 System reference codes (Bxxx)
B18138D7 • B1813911
callouts detailed with the SRC to determine service
B18138D7 B18138D7
actions.
Explanation: A netlink socket receive operation failed.
Response: If this is a tracking event, no service actions B1813906 B1813906
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when getting the IP
callouts detailed with the SRC to determine service
address from node controller surveillance.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18138D8 B18138D8
callouts detailed with the SRC to determine service
Explanation: A netlink socket receive operation failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1813909 B1813909
callouts detailed with the SRC to determine service
Explanation: The IPL is being terminated due to the
actions.
loss of the primary node controller.
Response: If this is a tracking event, no service actions
B18138D9 B18138D9
are required. Otherwise, use the FRU and procedure
Explanation: A netlink socket receive operation failed. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181390D B181390D
actions.
Explanation: Unable to perform a node controller
failover because the redundancy policy is not set to
B18138DA B18138DA correctly.
Explanation: A netlink socket receive operation failed. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B181390E B181390E
B18138EB B18138EB Explanation: Unable to perform a node controller
failover because there is no node controller under
Explanation: Device not found in FSM
surveillance.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service
actions.
actions.
B18138F3 B18138F3
B181390F B181390F
Explanation: A timeout occurred in the FRU manager
Explanation: Unable to make node controller B
component while waiting for FWSM.
primary because only node controller A is under
Response: If this is a tracking event, no service actions surveillance.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B1813901 B1813901
Explanation: Informational message: an invalid B1813911 B1813911
request was send to the node manager; it will be
Explanation: Unable to make node controller A
ignored.
primary because only node controller B is under
Response: If this is a tracking event, no service actions surveillance.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
(B1xx) Reference codes 313
B1813914 • B1813928
are required. Otherwise, use the FRU and procedure
B1813923 B1813923
callouts detailed with the SRC to determine service
actions. Explanation: An invalid parameter was found.
Response: If this is a tracking event, no service actions
B1813914 B1813914 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Unable to send a command to the
actions.
secondary service processor because it is in a bad state.
Response: If this is a tracking event, no service actions
B1813924 B1813924
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Unable to make node controller B
actions. primary because only node controller A is under
surveillance.
B1813917 B1813917 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when reading a
callouts detailed with the SRC to determine service
register.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1813925 B1813925
callouts detailed with the SRC to determine service
actions. Explanation: Unable to make node controller A
primary because only node controller B is under
surveillance.
B1813918 B1813918
Response: If this is a tracking event, no service actions
Explanation: There was an error due to the loss of
are required. Otherwise, use the FRU and procedure
surveillance when activating a node controller.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813926 B1813926
actions.
Explanation: Unable to perform a node controller
failover because there is no node controller under
B1813919 B1813919
surveillance.
Explanation: A failover was made due to node
Response: If this is a tracking event, no service actions
correlation.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813927 B1813927
Explanation: An error occurred when trying to start
B1813920 B1813920
the FRUM configuration timer after a new node
Explanation: Node controller correlation failed. controller was discovered by the system controller.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1813921 B1813921 B1813928 B1813928
Explanation: Node controller correlation failed. Explanation: An error occurred when trying to
broadcast an event after a new node controller was
Response: If this is a tracking event, no service actions discovered by the system controller.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
314 System reference codes (Bxxx)
B181392A • B1813938
B181392A B181392A B1813930 B1813930
Explanation: A request was sent to the NPL to insure Explanation: There are two secondary node
that there is a functional node controller in a node. controllers.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181392B B181392B B1813931 B1813931
Explanation: First failure data collection (FFDC) was Explanation: Only node controller A was visible to the
done on BPH side A. system controller.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181392C B181392C B1813932 B1813932
Explanation: First failure data collection (FFDC) was Explanation: Only node controller B was visible to the
done on BPH side B. system controller.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181392D B181392D B1813936 B1813936
Explanation: The system controller lost Explanation: The interface to read node controller
communication with a node controller for an extended entries from P1 received an invalid argument.
period of time.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813937 B1813937
B181392E B181392E
Explanation: The system controller was unable to
Explanation: There was a surveillance failure of a communicate with a node controller for an extended
node controller. period of time.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181392F B181392F B1813938 B1813938
Explanation: A node is present that is not under Explanation: The system controller was unable to
surveillance. communicate with a node controller for an extended
period of time.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 315
B1813939 • B1813946
B1813939 B1813939 B1813940 B1813940
Explanation: The controller selected was not the Explanation: Informational message: When a node
primary. controller was disabled, it was rebooted.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181393B B181393B B1813942 B1813942
Explanation: An invalid request to read all alerts was Explanation: The system controller is trying to start
received. services on a node controller.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181393C B181393C B1813943 B1813943
Explanation: A perc signal was received. Explanation: The system controller did not receive a
response (within the allotted time) to a ping command
Response: If this is a tracking event, no service actions
from the node controller.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181393D B181393D
Explanation: Informational message: surveillance on a
B1813944 B1813944
node controller was turned off at the request of an
external component. Explanation: The system controller received bad data
back after sending a ping command to a node
Response: If this is a tracking event, no service actions
controller.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181393E B181393E
Explanation: Informational message: A reboot of a
B1813945 B1813945
node controller was requested by an external
component. Explanation: The system controller received bad data
back after sending a ping command to a node
Response: If this is a tracking event, no service actions
controller.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181393F B181393F
Explanation: Informational message: A reboot of a
B1813946 B1813946
node controller was requested by an external
component. Explanation: The system controller did not receive a
response (within the allotted time) from a node
Response: If this is a tracking event, no service actions
controller after sending a surveillance off command to
are required. Otherwise, use the FRU and procedure
the node controller.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
316 System reference codes (Bxxx)
B1813947 • B1813951
callouts detailed with the SRC to determine service
B181394C B181394C
actions.
Explanation: The system controller did not receive a
response (within the allotted time) from the node
B1813947 B1813947
controller after sending a "hold sibling in reset
Explanation: The system controller received bad data command".
back after sending a surveillance off command to a
Response: If this is a tracking event, no service actions
node controller.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181394D B181394D
Explanation: The system controller received bad data
B1813948 B1813948
back after sending a "hold sibling in reset command" to
Explanation: The system controller received bad data a node controller.
back after sending a surveillance off command to a
Response: If this is a tracking event, no service actions
node controller.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181394E B181394E
Explanation: The system controller received bad data
B1813949 B1813949
back after sending a hold sibling in reset
Explanation: The system controller did not receive a command to a node controller.
response (within the allotted time) from a node
Response: If this is a tracking event, no service actions
controller after sending a reboot command.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181394F B181394F
Explanation: The system controller lost the connection
B181394A B181394A
to a node controller.
Explanation: The system controller received bad data
Response: If this is a tracking event, no service actions
back after sending a reboot command to a node
are required. Otherwise, use the FRU and procedure
controller.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1813950 B1813950
actions.
Explanation: The system controller did not receive a
response (within the allotted time) from the node
B181394B B181394B
controller after trying to start services on the node
Explanation: The system controller received bad data controller.
back after sending a reboot command to a node
Response: If this is a tracking event, no service actions
controller.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1813951 B1813951
Explanation: The system controller received
unexpected data back from a node controller when
trying to start services on the node controller.
Response: If this is a tracking event, no service actions
(B1xx) Reference codes 317
B1813952 • B181395E
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1813959 B1813959
B1813952 B1813952
Explanation: Node controllers were found with pool
Explanation: The system controller received an error IP addresses.
message from a node controller when trying to start
Response: If this is a tracking event, no service actions
services on the node controller.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181395A B181395A
Explanation: The node controller did not become
B1813954 B1813954
visible in time.
Explanation: The system controllers see a different
Response: If this is a tracking event, no service actions
number of nodes.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181395B B181395B
Explanation: An error occurred when getting the IP
B1813955 B1813955
address from the dynamic node controller list.
Explanation: Node controllers that were visible during
Response: If this is a tracking event, no service actions
a previous boot are no longer visible.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181395C B181395C
Explanation: The node controller was disabled by a
B1813956 B1813956
command line request.
Explanation: The node controller is rebooting by
Response: If this is a tracking event, no service actions
request.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181395D B181395D
Explanation: The node controllers moved to the
B1813957 B1813957
surveillance service level.
Explanation: A time-out occurred when getting data
Response: If this is a tracking event, no service actions
from a node controller surveillance.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181395E B181395E
Explanation: Timed out waiting for the data from the
B1813958 B1813958
node manager daemon.
Explanation: A node controller was found with an
Response: If this is a tracking event, no service actions
invalid ID.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
318 System reference codes (Bxxx)
B181395F • B181401A
B181395F B181395F B1814012 B1814012
Explanation: A reboot of a node controller was Explanation: The was a node controller surveillance
requested by an external component. failure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1814001 B1814001 B1814013 B1814013
Explanation: An unknown request was received. Explanation: The was a node controller surveillance
failure.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1814006 B1814006
B1814015 B1814015
Explanation: No target IP address was found.
Explanation: An error was received from the remove
Response: If this is a tracking event, no service actions
function.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181400F B181400F
Explanation: An error was received from the scandir
B1814016 B1814016
function.
Explanation: The requested trace buffer was not
Response: If this is a tracking event, no service actions
found.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1814010 B1814010
Explanation: An error occurred when opening the
B1814019 B1814019
error log file.
Explanation: An error occurred when the node
Response: If this is a tracking event, no service actions
controller was trying to read its own node driver_name
are required. Otherwise, use the FRU and procedure
registry value. Refer to the primary SRC for additional
callouts detailed with the SRC to determine service
detail.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1814011 B1814011
callouts detailed with the SRC to determine service
Explanation: An error was received from a function actions.
call.
Response: If this is a tracking event, no service actions B181401A B181401A
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when the node
callouts detailed with the SRC to determine service
controller was trying to read its own role registry
actions.
value. Refer to the primary SRC for additional detail.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 319
B181401B • B1814025
Response: If this is a tracking event, no service actions
B181401B B181401B
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when the node callouts detailed with the SRC to determine service
controller was trying to read its own node driver_name actions.
registry value. Refer to the primary SRC for additional
detail.
B1814021 B1814021
Response: If this is a tracking event, no service actions
Explanation: An error occurred when the node
are required. Otherwise, use the FRU and procedure
controller was trying to read its own eth1-ip-address
callouts detailed with the SRC to determine service
registry value. Refer to the primary SRC for additional
actions.
detail.
Response: If this is a tracking event, no service actions
B181401C B181401C
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when the node callouts detailed with the SRC to determine service
controller was trying to read its own role registry actions.
value. Refer to the primary SRC for additional detail.
Response: If this is a tracking event, no service actions B1814022 B1814022
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when the node
callouts detailed with the SRC to determine service
controller was trying to read its own eht1-ip-address
actions.
registry value. Refer to the primary SRC for additional
detail.
B181401D B181401D
Response: If this is a tracking event, no service actions
Explanation: An error occurred when the node are required. Otherwise, use the FRU and procedure
controller was trying to read its own role registry callouts detailed with the SRC to determine service
value. Refer to the primary SRC for additional detail. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1814023 B1814023
callouts detailed with the SRC to determine service
Explanation: An error occurred when the node
actions.
controller was trying to read its own node
controller-ID-address registry value. Refer to the
B181401E B181401E primary SRC for additional detail.
Explanation: An error occurred when the node Response: If this is a tracking event, no service actions
controller was trying to read its own role registry are required. Otherwise, use the FRU and procedure
value. Refer to the primary SRC for additional detail. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1814024 B1814024
actions.
Explanation: An error occurred when the node
controller was trying to read its own node
B181401F B181401F controller-DD-address registry value. Refer to the
primary SRC for additional detail.
Explanation: An error occurred when the node
controller was trying to read its own node driver_name Response: If this is a tracking event, no service actions
registry value. Refer to the primary SRC for additional are required. Otherwise, use the FRU and procedure
detail. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1814025 B1814025
actions.
Explanation: An error occurred when calling the
p-open function.
B1814020 B1814020
Response: If this is a tracking event, no service actions
Explanation: An error occurred when the node are required. Otherwise, use the FRU and procedure
controller was trying to read its own eth0-ip-address callouts detailed with the SRC to determine service
registry value. Refer to the primary SRC for additional actions.
detail.
320 System reference codes (Bxxx)
B1814026 • B1814110
B1814026 B1814026 B1814033 B1814033
Explanation: An error occurred when setting the PRA Explanation: A panic request was received from the
word to zero. system controller.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1814027 B1814027 B181410A B181410A
Explanation: An error occurred when reading the PRA Explanation: Connect to the server failed.
word.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181410B B181410B
B1814028 B1814028
Explanation: A error occurred on an operation that
Explanation: An error occurred when the node could not be retried with a communications channel.
controller was trying to read its own role registry
Response: If this is a tracking event, no service actions
value. Refer to the primary SRC for additional detail.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181410C B181410C
Explanation: The connection timed out.
B1814029 B1814029
Response: If this is a tracking event, no service actions
Explanation: A perc signal was received.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181410D B181410D
Explanation: The connection timed out.
B181402A B181402A
Response: If this is a tracking event, no service actions
Explanation: An error occurred when calling a system
are required. Otherwise, use the FRU and procedure
function.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181410F B181410F
actions.
Explanation: Failed to write data to a socket.
B181402D B181402D Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when the node
callouts detailed with the SRC to determine service
controller was trying write a unique error ID to the
actions.
registry.
Response: If this is a tracking event, no service actions
B1814110 B1814110
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to read a message from the
actions. channel.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 321
B1814114 • B1814131
callouts detailed with the SRC to determine service
B1814121 B1814121
actions.
Explanation: Unable to find the proxy control block.
B1814114 B1814114 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A call back failure occurred.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1814122 B1814122
actions.
Explanation: The context cannot be cleaned up after
the submission fails.
B1814115 B1814115
Response: If this is a tracking event, no service actions
Explanation: The incoming message has no callback
are required. Otherwise, use the FRU and procedure
correlator.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1814123 B1814123
actions.
Explanation: The context cannot be cleaned up after
the submission fails.
B1814116 B1814116
Response: If this is a tracking event, no service actions
Explanation: There is FFDC data from the building
are required. Otherwise, use the FRU and procedure
block.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1814129 B1814129
actions.
Explanation: The dispatcher shutdown timed out.
B1814117 B1814117 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: NMGR returned a failure; there is a
callouts detailed with the SRC to determine service
broken link or a node does not exist.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1814130 B1814130
callouts detailed with the SRC to determine service
actions. Explanation: Writing the message to the channel
failed.
B1814119 B1814119 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The rmgrd daemon received a signal that
callouts detailed with the SRC to determine service
was not expected.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1814131 B1814131
callouts detailed with the SRC to determine service
actions. Explanation: Writing the message to the channel
failed.
B1814120 B1814120 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Invalid AIO parameters were passed to
callouts detailed with the SRC to determine service
rdal_aio_ctx_submit.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
322 System reference codes (Bxxx)
B1814132 • B181440A
B1814132 B1814132 B1814204 B1814204
Explanation: Reading the message from the channel Explanation: FFDC data was extracted, but the unlock
failed. failed
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1814133 B1814133 B1814205 B1814205
Explanation: Reading the message from the channel Explanation: An invalid error log was passed into an
failed. FFDC function
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1814134 B1814134 B1814206 B1814206
Explanation: Unable to get the target node's IP Explanation: An invalid RDAL object was returned
address; the sibling service processor or the node is from an open command.
inactive.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1814301 B1814301
B1814201 B1814201
Explanation: An error was detected while setting the
Explanation: RDAL reported a GPIO close failure. DD level of the service processor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1814202 B1814202 B1814407 B1814407
Explanation: RDAL handle failure Explanation: Unable to initialize the address structure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1814203 B1814203 B181440A B181440A
Explanation: An error occured, but FFDC could not be Explanation: The connection to the server failed.
extracted
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 323
B181440B • B1817209
B181440B B181440B B1817201 B1817201
Explanation: There was a hard socket failure Explanation: A reset/reload occurred on a service
disconnection. processor or system controller due to a kernel panic.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181440C B181440C B1817202 B1817202
Explanation: The connection timed out. Explanation: The permanent and temporary firmware
sides are both marked invalid
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: Perform FSPSP02 .
callouts detailed with the SRC to determine service
actions.
B1817203 B1817203
Explanation: Error setting boot parameters
B181440D B181440D
Response: Perform FSPSP02 .
Explanation: The connection is closed.
Response: If this is a tracking event, no service actions
B1817204 B1817204
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Error reading boot parameters
actions.
Response: Perform FSPSP02 .
B181440F B181440F
B1817205 B1817205
Explanation: Failed to write data to a socket.
Explanation: Boot code error
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: Perform FSPSP02 .
callouts detailed with the SRC to determine service
actions. B1817206 B1817206
Explanation: Unit check timer was reset
B181460B B181460B
Response: Perform FSPSP02 .
Explanation: An exception was encountered.
Response: If this is a tracking event, no service actions B1817207 B1817207
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Error reading from NVRAM
actions. Response: Perform FSPSP02 .
B1814616 B1814616 B1817208 B1817208
Explanation: An XREF synchronization error occurred. Explanation: Error writing to NVRAM
Response: If this is a tracking event, no service actions Response: Perform FSPSP02 .
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1817209 B1817209
Explanation: The service processor boot watchdog
B1817200 B1817200 timer expired and forced the service processor to
attempt a boot from the other firmware image in the
Explanation: Invalid boot request service processor flash memory
Response: Perform FSPSP02 . Response: Perform FSPSP02 .
324 System reference codes (Bxxx)
B181720A • B181810D
B181720A B181720A B1818107 B1818107
Explanation: Power-off reset occurred. FipsDump Explanation: Wrong bus owner in the argument
should be analyzed: Possible software problem
Response: If this is a tracking event, no service actions
Response: Perform FSPSP02 . are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181720B B181720B
Explanation: Link 0 is not plugged.
B1818108 B1818108
Response: If this is a tracking event, no service actions
Explanation: Invalid number of command line
are required. Otherwise, use the FRU and procedure
arguments
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181720C B181720C
actions.
Explanation: No space is left on P1.
Response: Perform FSPSP02 . B1818109 B1818109
Explanation: Missing reserve ID, no argument value
B181720D B181720D for --r option
Explanation: A service processor kernel panic was Response: If this is a tracking event, no service actions
caused by an out-of-memory condition. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B181810A B181810A
Explanation: Multiple -c arguments
B181720E B181720E
Response: If this is a tracking event, no service actions
Explanation: A service processor kernel panic was are required. Otherwise, use the FRU and procedure
caused by uncorrectable error in the flash memory on callouts detailed with the SRC to determine service
the service processor. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181810B B181810B
callouts detailed with the SRC to determine service
Explanation: -s option specified with -c
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1817210 B1817210
callouts detailed with the SRC to determine service
Explanation: A reset/reload occurred on a node actions.
controller or system controller due to a cache parity
error, but the error threshold has not been exceeded.
B181810C B181810C
This is an informational message; no action is required.
Explanation: Multiple -s arguments
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818104 B1818104
B181810D B181810D
Explanation: Registry write failed
Explanation: -c option specified with -s
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 325
B181810E • B1818214
B181810E B181810E B1818118 B1818118
Explanation: Invalid command line options Explanation: Processor state query failed
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181810F B181810F B1818204 B1818204
Explanation: Bad command line arguments Explanation: A requested SRC was not found in the
list of SRCs.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818110 B1818110
B1818205 B1818205
Explanation: No numeric input for reserve ID
Explanation: A possible file system problem was
Response: If this is a tracking event, no service actions
detected when attempting to open a directory for
are required. Otherwise, use the FRU and procedure
reading.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818111 B1818111
actions.
Explanation: Empty numeric string for reserve ID
Response: If this is a tracking event, no service actions B1818212 B1818212
are required. Otherwise, use the FRU and procedure
Explanation: The operation requested by an external
callouts detailed with the SRC to determine service
entity was not understood.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1818112 B1818112
callouts detailed with the SRC to determine service
Explanation: Invalid character encountered in actions.
conversion.
Response: If this is a tracking event, no service actions B1818213 B1818213
are required. Otherwise, use the FRU and procedure
Explanation: A failure occurred when trying to read a
callouts detailed with the SRC to determine service
registry key.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1818116 B1818116
callouts detailed with the SRC to determine service
Explanation: Processor stop instruction failed actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818214 B1818214
callouts detailed with the SRC to determine service
Explanation: Invalid input data was found during an
actions.
SRCI operation.
Response: If this is a tracking event, no service actions
B1818117 B1818117
are required. Otherwise, use the FRU and procedure
Explanation: A function call failed. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
326 System reference codes (Bxxx)
B1818215 • B1818309
B1818215 B1818215 B1818302 B1818302
Explanation: The size specified for the SRCI operation Explanation: CTRM is already in the power-off state.
was inaccurate.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818303 B1818303
B1818216 B1818216
Explanation: ctrm currently processing a poweroff
Explanation: A generic stream failure has been request from the SPCN
detected during an SRCI operation.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818304 B1818304
B1818217 B1818217
Explanation: CTRM is currently processing a request
Explanation: A possible file system failure while SRCI to terminate the service processor from another service
operation attempted to create a file. processor firmware component.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818218 B1818218 B1818305 B1818305
Explanation: SRCI detected bad input data; a valid Explanation: Termination request to the state manager
identifier byte was not found. failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818219 B1818219 B1818307 B1818307
Explanation: SRCI received a signal it does not Explanation: An error was encountered with the IPL
understand. request during the processing of a power fault.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818301 B1818301 B1818309 B1818309
Explanation: CTRM is already in the termination state. Explanation: Too many client connections were
established.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 327
B181830A • B181831A
callouts detailed with the SRC to determine service
B181830A B181830A
actions.
Explanation: An unexpected signal was received.
Response: If this is a tracking event, no service actions B1818313 B1818313
are
Explanation: An error was encountered when
connecting to the communications server.
B181830B B181830B
Response: If this is a tracking event, no service actions
Explanation: Client request timeout. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1818316 B1818316
Explanation: Failed to trace SRC.
B181830C B181830C
Response: If this is a tracking event, no service actions
Explanation: The event timed out waiting for the are required. Otherwise, use the FRU and procedure
termination state. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818317 B1818317
actions.
Explanation: Error reading registry entry.
Response: If this is a tracking event, no service actions
B181830D B181830D
are required. Otherwise, use the FRU and procedure
Explanation: An error was encountered starting the callouts detailed with the SRC to determine service
request process. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818318 B1818318
callouts detailed with the SRC to determine service
Explanation: Error updating registry entry.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181830E B181830E
callouts detailed with the SRC to determine service
Explanation: Synchronization with client process actions.
failed.
Response: If this is a tracking event, no service actions B1818319 B1818319
are required. Otherwise, use the FRU and procedure
Explanation: The firmware state was not reset.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818310 B1818310
actions.
Explanation: A client request failed due to "server
busy" condition.
B181831A B181831A
Response: If this is a tracking event, no service actions
Explanation: No error log passed to the CTRM client
are required. Otherwise, use the FRU and procedure
library.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818312 B1818312
actions.
Explanation: An error was encountered while
receiving from socket.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
328 System reference codes (Bxxx)
B181831C • B1818344
callouts detailed with the SRC to determine service
B181831C B181831C
actions.
Explanation: Unable to retrieve the embedded SRC
from the error log.
B181833C B181833C
Response: If this is a tracking event, no service actions
Explanation: A failure occurred when updating a
are required. Otherwise, use the FRU and procedure
registry value.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181831D B181831D
actions.
Explanation: Error processing client request.
Response: If this is a tracking event, no service actions B181833D B181833D
are required. Otherwise, use the FRU and procedure
Explanation: Processing was terminated on the
callouts detailed with the SRC to determine service
secondary.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181831E B181831E
callouts detailed with the SRC to determine service
Explanation: Error processing client request. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181833F B181833F
callouts detailed with the SRC to determine service
Explanation: gardCheckFailoverCapable() returned an
actions.
error.
Response: If this is a tracking event, no service actions
B1818320 B1818320
are required. Otherwise, use the FRU and procedure
Explanation: CTRM server error binding to socket. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818341 B1818341
actions.
Explanation: Invalid error log object.
Response: If this is a tracking event, no service actions
B1818321 B1818321
are required. Otherwise, use the FRU and procedure
Explanation: Error while attempting to obtain a lock. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818343 B1818343
actions.
Explanation: There was an error when connecting to
the network.
B1818322 B1818322
Response: If this is a tracking event, no service actions
Explanation: CTRM server error when canceling client are required. Otherwise, use the FRU and procedure
request processing threads. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818344 B1818344
actions.
Explanation: Invalid Errorlog object.
Response: If this is a tracking event, no service actions
B181833B B181833B
are required. Otherwise, use the FRU and procedure
Explanation: An invalid request was received. No callouts detailed with the SRC to determine service
operation was performed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 329
B1818345 • B1818404
B1818345 B1818345 B1818360 B1818360
Explanation: The sending of a CTRM client request to Explanation: rmgrNotifySibling( ) FAILED
the server failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818361 B1818361
B1818346 B1818346
Explanation: Unable to read a registry value.
Explanation: The sending of a CTRM client request to
Response: If this is a tracking event, no service actions
the server failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818362 B1818362
Explanation: An error was returned from trying to
B1818347 B1818347
clear the dscv role lock.
Explanation: Synchronization with CTRM server
Response: If this is a tracking event, no service actions
failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818401 B1818401
Explanation: There was an error in selecting the
B181834A B181834A
socket.
Explanation: The client failed to retreive the P0 root
Response: If this is a tracking event, no service actions
path.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818402 B1818402
Explanation: There was an error in "SSL listen".
B181834B B181834B
Response: If this is a tracking event, no service actions
Explanation: Termination failed without failover.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818403 B1818403
Explanation: There was an error in the bind operation
B181834F B181834F
for UNIX .
Explanation: A function in the firmware has called
Response: If this is a tracking event, no service actions
another function without an error handle.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818404 B1818404
Explanation: There was an error in the bind operation
for SSL.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
330 System reference codes (Bxxx)
B1818405 • B1818411
callouts detailed with the SRC to determine service
B181840C B181840C
actions.
Explanation: There was an error in the "receive
message" queue.
B1818405 B1818405
Response: If this is a tracking event, no service actions
Explanation: There was an error when accepting a
are required. Otherwise, use the FRU and procedure
UNIX connection.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181840D B181840D
actions.
Explanation: An error occurred when deleting the old
message queue.
B1818406 B1818406
Response: If this is a tracking event, no service actions
Explanation: An error occurred when opening a vtty
are required. Otherwise, use the FRU and procedure
session.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181840E B181840E
actions.
Explanation: An error occurred when creating the
inbound thread.
B1818407 B1818407
Response: If this is a tracking event, no service actions
Explanation: There was an error in accepting a
are required. Otherwise, use the FRU and procedure
TCP/IP connection.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181840F B181840F
actions.
Explanation: An error occurred in the inbound
connection.
B1818409 B1818409
Response: If this is a tracking event, no service actions
Explanation: An error occurred when creating the
are required. Otherwise, use the FRU and procedure
unique key for the message queue.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818410 B1818410
actions.
Explanation: An error occurred when receiving
outbound messages.
B181840A B181840A
Response: If this is a tracking event, no service actions
Explanation: An error occurred during message queue
are required. Otherwise, use the FRU and procedure
creation.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818411 B1818411
actions.
Explanation: An error occurred when calling a
routine.
B181840B B181840B
Response: If this is a tracking event, no service actions
Explanation: An error occurred when queueing
are required. Otherwise, use the FRU and procedure
messages.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 331
B1818412 • B1818421
B1818412 B1818412 B181841C B181841C
Explanation: There was an error in "receive message". Explanation: There was an error in deleting the
message queue.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818414 B1818414
B181841D B181841D
Explanation: An error occurred sending a message.
Explanation: Unable to remove the previous mount.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818415 B1818415
B181841E B181841E
Explanation: An error occurred when deleting the old
message queue. Explanation: A failure occurred when reading a
registry value.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818416 B1818416
B181841F B181841F
Explanation: The maximum number of socket
connections for TCP clients was reached Explanation: An error occurred when writing to a file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818418 B1818418 B1818420 B1818420
Explanation: An error occurred in the address Explanation: There was an error when closing the
creation. vtty.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818419 B1818419 B1818421 B1818421
Explanation: An error occurred when closing the Explanation: Unable to activate the user configuration
inbound socket. set up file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
332 System reference codes (Bxxx)
B1818422 • B181842D
B1818422 B1818422 B1818428 B1818428
Explanation: A NETS script was executed. Explanation: An error occurred when killing a thread.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818423 B1818423 B1818429 B1818429
Explanation: An error occurred when writing the Explanation: An error occurred in SSL for a remote
system name. message object.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818424 B1818424 B181842A B181842A
Explanation: An invalid name was received. Explanation: An error occurred when requeueing.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818425 B1818425 B181842B B181842B
Explanation: A failure occurred when setting the user Explanation: The kill operation was called; the virtual
password. TTY (VTTY) server will close.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818426 B1818426 B181842C B181842C
Explanation: A failure occurred when validating the Explanation: An error occurred when deleting the old
password. message queue.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818427 B1818427 B181842D B181842D
Explanation: An error occurred in the initial set up of Explanation: An error occurred when creating a
the out bound remote thread. process thread.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 333
B181842E • B1818439
B181842E B181842E B1818434 B1818434
Explanation: An error occurred when creating a Explanation: A failure occurred when setting the
session thread. status field to "failure" in the hypervisor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181842F B181842F B1818435 B1818435
Explanation: There was an error in using userconfig. Explanation: An error occurred when verifying the
dynamic password.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818430 B1818430
B1818436 B1818436
Explanation: A failure occurred when reading a
registry value. . Explanation: An error occurred when writing the
password signature.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818431 B1818431
B1818437 B1818437
Explanation: The user password value's length was
not valid. Explanation: An error occurred when writing the
manufacturing password signature.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818432 B1818432
B1818438 B1818438
Explanation: An error occurred when opening the
port for connection. Explanation: An error occurred in the universal
asynchronous receiver/transmitter (UART)
Response: If this is a tracking event, no service actions
configuration for parity.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818433 B1818433
Explanation: An error occurred in the universal
B1818439 B1818439
asynchronous receiver/transmitter (UART)
configuration for the baud rate. Explanation: An error was found in the configuration
of the universal asynchronous receiver/transmitter
Response: If this is a tracking event, no service actions
(UART) configuration for trans_normal.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
334 System reference codes (Bxxx)
B181843A • B1818445
B181843A B181843A B1818440 B1818440
Explanation: An internal error occurred. Explanation: An error occurred when initializing the
serial server daemon.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181843B B181843B
B1818441 B1818441
Explanation: An internal error occurred.
Explanation: An error ocurred when creating a session
Response: If this is a tracking event, no service actions
thread.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181843C B181843C
Explanation: An error occurred when sending a
B1818442 B1818442
message to a client.
Explanation: An error occurred in the stat file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181843D B181843D
B1818443 B1818443
Explanation: An error occurred when getting the
machine type vital product data (VPD). Explanation: An invalid error path was found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181843E B181843E B1818444 B1818444
Explanation: A failure occurred when reading the Explanation: An error occurred when writing the
system serial number. manufacturing password signature.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181843F B181843F B1818445 B1818445
Explanation: An error occurred when reading the Explanation: An invalid socket descriptor was
machine brand. selected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 335
B1818446 • B1818453
callouts detailed with the SRC to determine service
B1818446 B1818446
actions.
Explanation: The signal length exceeded the limit.
Response: If this is a tracking event, no service actions B181844D B181844D
are required. Otherwise, use the FRU and procedure
Explanation: An invalid error path was found.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818447 B1818447
actions.
Explanation: Error statistics are available.
Response: If this is a tracking event, no service actions B181844E B181844E
are required. Otherwise, use the FRU and procedure
Explanation: An internal error occurred.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818448 B1818448
actions.
Explanation: Memory allocation failed.
Response: If this is a tracking event, no service actions B181844F B181844F
are required. Otherwise, use the FRU and procedure
Explanation: An error was found in a certificate.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818449 B1818449
actions.
Explanation: The universal asynchronous
receiver/transmitter (UART) configuration failed.
B1818450 B1818450
Response: If this is a tracking event, no service actions
Explanation: An internal error occurred.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181844A B181844A
Explanation: The universal asynchronous
B1818451 B1818451
receiver/transmitter (UART) configuration failed.
Explanation: An internal error occurred.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181844B B181844B
B1818452 B1818452
Explanation: The universal asynchronous
receiver/transmitter (UART) configuration failed. Explanation: An internal error occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181844C B181844C B1818453 B1818453
Explanation: The universal asynchronous Explanation: An internal error occurred.
receiver/transmitter (UART) configuration failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
336 System reference codes (Bxxx)
B1818454 • B1818462
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818454 B1818454 B181845D B181845D
Explanation: The wrong password was found. Explanation: An error occurred in an SSL write.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818456 B1818456 B181845E B181845E
Explanation: An internal error occurred. . Explanation: There was an error in PERC.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818457 B1818457 B181845F B181845F
Explanation: An internal error occurred. Explanation: There was an error when reading the
registry.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818458 B1818458
B1818460 B1818460
Explanation: An internal error occurred.
Explanation: An invalid error path was found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181845A B181845A
B1818461 B1818461
Explanation: An internal error occurred.
Explanation: There was an error when reading the
Response: If this is a tracking event, no service actions
registry.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181845B B181845B
Explanation: An error occurred with a daemon.
B1818462 B1818462
Response: If this is a tracking event, no service actions
Explanation: There was an error when starting the
are required. Otherwise, use the FRU and procedure
vtty daemon.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181845C B181845C
actions.
Explanation: There was an error when enabling a
login.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 337
B1818463 • B1818473
B1818463 B1818463 B1818469 B1818469
Explanation: There was an error in obtaining a file Explanation: There was an error when reading the
descriptor. registry.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818464 B1818464 B181846A B181846A
Explanation: An error occurred when getting the file. Explanation: There was an error when reading the
registry.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818465 B1818465
B1818470 B1818470
Explanation: There was an error when validating the
password. Explanation: The UART adal configuration failed for
serial-type connections.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818466 B1818466
B1818471 B1818471
Explanation: There was an error when writing the
manufacturing password. Explanation: There was an error in getting the HMC
certificates.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818467 B1818467
B1818472 B1818472
Explanation: An error occurred when setting the user
password. Explanation: There was an error in SSL_CTX_new.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818468 B1818468 B1818473 B1818473
Explanation: An error occurred when creating a key. Explanation: There was an error in
SSL_CTX_use_certificate.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
338 System reference codes (Bxxx)
B1818474 • B181848A
B1818474 B1818474 B181847F B181847F
Explanation: There was an error in Explanation: An invalid tool was found.
SSL_CTX_use_PrivateKey.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818482 B1818482
B1818475 B1818475
Explanation: The process to open a file failed.
Explanation: There was an error in
Response: If this is a tracking event, no service actions
SSL_CTX_check_private_key.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818483 B1818483
Explanation: The IP query failed.
B1818477 B1818477
Response: If this is a tracking event, no service actions
Explanation: There was an error in readCertKeyPair.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818486 B1818486
Explanation: There was an error in eraseCertKeyPair.
B1818478 B1818478
Response: If this is a tracking event, no service actions
Explanation: There was an error in BIO_new_socket.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818487 B1818487
Explanation: There was an error with the daemon; no
B181847C B181847C
parent or child was found.
Explanation: An error occurred in setsockopt.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818488 B1818488
B181847D B181847D
Explanation: SLP deregulation error
Explanation: An error occurred in getsockopt.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181848A B181848A
B181847E B181847E
Explanation: A failure in the acceptance portion of the
Explanation: A failover was detected. TCP/IP-type connection.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 339
B181848C • B1818509
callouts detailed with the SRC to determine service
B181848C B181848C
actions.
Explanation: The TCPIP socket listen failed.
Response: If this is a tracking event, no service actions B1818503 B1818503
are required. Otherwise, use the FRU and procedure
Explanation: An invalid message has been received by
callouts detailed with the SRC to determine service
either the client or the daemon.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181848D B181848D
callouts detailed with the SRC to determine service
Explanation: The Unix socket accept operation failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818504 B1818504
callouts detailed with the SRC to determine service
Explanation: These SRCs are added to the primary
actions.
SRC to show control flow.
Response: If this is a tracking event, no service actions
B181848E B181848E
are required. Otherwise, use the FRU and procedure
Explanation: An improper error path was found. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818505 B1818505
actions.
Explanation: Failed to create the file name for a new
socket.
B1818496 B1818496
Response: If this is a tracking event, no service actions
Explanation: There was an error when setting the user are required. Otherwise, use the FRU and procedure
password. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818506 B1818506
actions.
Explanation: Event notifier initialization failed because
a thread could not be created.
B181849B B181849B
Response: If this is a tracking event, no service actions
Explanation: An IP query for the HMC failed. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1818508 B1818508
Explanation: An event could not be sent to one or
B1818501 B1818501 more subscribers.
Explanation: An invalid value was passed into an Response: If this is a tracking event, no service actions
EvenMgt method call. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1818509 B1818509
Explanation: Attempted to signal an event using an
B1818502 B1818502 invalid event ID.
Explanation: An invalid value was passed into an Response: If this is a tracking event, no service actions
EvenMgt method call. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
340 System reference codes (Bxxx)
B181850A • B1818519
B181850A B181850A B1818514 B1818514
Explanation: An unexpected signal has been received. Explanation: Internal firmware error: a bad parameter
was passed into the EvenMgt method call.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181850F B181850F
B1818515 B1818515
Explanation: The user specified a time limit to wait
for an event, and the time limit was reached. Explanation: Internal firmware error: the caller
wanted to monitor for events but is not subscribed to
Response: If this is a tracking event, no service actions
any.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818510 B1818510
Explanation: Attempted to subscribe to or unsubscribe
B1818516 B1818516
from an event while the event management object was
in use by another thread. Explanation: Internal firmware error: the caller did
not pass in a valid buffer pointer to hold event-related
Response: If this is a tracking event, no service actions
data.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818511 B1818511
Explanation: The subscribed process appeared to have
B1818517 B1818517
ended without unsubscribing.
Explanation: Internal firmware error: a bad parameter
Response: If this is a tracking event, no service actions
was passed into the EvenMgt constructor.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818512 B1818512
Explanation: Internal firmware error: an invalid filter
B1818518 B1818518
value was passed into the EvenMgt method call.
Explanation: The user passed in a buffer that was too
Response: If this is a tracking event, no service actions
small to hold all of the event-related data.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818513 B1818513
Explanation: Internal firmware error: an invalid event
B1818519 B1818519
id was passed into the EvenMgt method call.
Explanation: Reading the registry failed to obtain the
Response: If this is a tracking event, no service actions
path to the socket file.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 341
B1818601 • B1818785
B1818601 B1818601 B181871F B181871F
Explanation: An application has received an Explanation: Invalid data received.
unexpected signal.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181877F B181877F
B181860F B181860F
Explanation: An error occurred when the networking
Explanation: A process is calling another process firmware set the idle options.
without being set up correctly.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818780 B1818780
B1818610 B1818610
Explanation: An error ocurred when reading the
Explanation: A process is calling a procedure more registry.
than once.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818782 B1818782
B1818611 B1818611
Explanation: An error occurred when creating a file
Explanation: An application has received an handle.
unexpected signal.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818783 B1818783
B1818612 B1818612
Explanation: There was an error in a session to create
Explanation: There was an error processing the stack a socket.
trace.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818785 B1818785
B1818613 B1818613
Explanation: An error occurred when bind ing a
Explanation: There was an error processing the stack socket.
trace.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
342 System reference codes (Bxxx)
B1818786 • B1818794
callouts detailed with the SRC to determine service
B1818786 B1818786
actions.
Explanation: There was an error in "socket listen".
Response: If this is a tracking event, no service actions B181878E B181878E
are required. Otherwise, use the FRU and procedure
Explanation: There was an error in "read for session
callouts detailed with the SRC to determine service
entry".
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1818787 B1818787
callouts detailed with the SRC to determine service
Explanation: A failure occurred when writing a actions.
session entry.
Response: If this is a tracking event, no service actions B181878F B181878F
are required. Otherwise, use the FRU and procedure
Explanation: There was an error in "lookup in session
callouts detailed with the SRC to determine service
entry".
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1818788 B1818788
callouts detailed with the SRC to determine service
Explanation: There was an error in the client name. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818791 B1818791
callouts detailed with the SRC to determine service
Explanation: There was an error in "seek for session
actions.
entry".
Response: If this is a tracking event, no service actions
B181878A B181878A
are required. Otherwise, use the FRU and procedure
Explanation: The maximum number of sessions is callouts detailed with the SRC to determine service
already active. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818792 B1818792
callouts detailed with the SRC to determine service
Explanation: There was an error in "session entry
actions.
read".
Response: If this is a tracking event, no service actions
B181878B B181878B
are required. Otherwise, use the FRU and procedure
Explanation: An invalid offset entry was found. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818793 B1818793
actions.
Explanation: There was an error in "session entry
read".
B181878C B181878C
Response: If this is a tracking event, no service actions
Explanation: There was an error when reading the are required. Otherwise, use the FRU and procedure
registry. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818794 B1818794
actions.
Explanation: An invalid entry number was found.
Response: If this is a tracking event, no service actions
B181878D B181878D
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when updating a callouts detailed with the SRC to determine service
session entry. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 343
B1818795 • B18187A2
B1818795 B1818795 B181879D B181879D
Explanation: There was an error in a "session entry Explanation: An error occurred in a message
seek". constructor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818796 B1818796 B181879E B181879E
Explanation: There was an error when updating a Explanation: Allocation of memory for a message
session entry. failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818797 B1818797 B181879F B181879F
Explanation: An invalid PID was found in a session Explanation: Allocation of memory for a message
entry. failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181879A B181879A B18187A0 B18187A0
Explanation: An error when creating a socket. Explanation: There was an error in the buffer length.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181879B B181879B B18187A1 B18187A1
Explanation: Failed to create a socket. Explanation: An error occurred when creating a
message.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181879C B181879C
B18187A2 B18187A2
Explanation: Creation of the socket path failed due to
a registry read. Explanation: A null value was found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
344 System reference codes (Bxxx)
B18187A3 • B18187B3
callouts detailed with the SRC to determine service
B18187A3 B18187A3
actions.
Explanation: An invalid message was sent.
Response: If this is a tracking event, no service actions B18187AE B18187AE
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred in a routine
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187A4 B18187A4
actions.
Explanation: An invalid message was received.
Response: If this is a tracking event, no service actions B18187AF B18187AF
are required. Otherwise, use the FRU and procedure
Explanation: A connection failed due to the
callouts detailed with the SRC to determine service
connection timing out.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18187A5 B18187A5
callouts detailed with the SRC to determine service
Explanation: A null value was found. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B18187B0 B18187B0
callouts detailed with the SRC to determine service
Explanation: An error occurred in a connection.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18187A7 B18187A7
callouts detailed with the SRC to determine service
Explanation: There was an error in a UNIX actions.
connection.
Response: If this is a tracking event, no service actions B18187B1 B18187B1
are required. Otherwise, use the FRU and procedure
Explanation: A connection failed due to a timeout.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187A8 B18187A8
actions.
Explanation: There was a time-out on a connection.
Response: If this is a tracking event, no service actions B18187B2 B18187B2
are required. Otherwise, use the FRU and procedure
Explanation: A connection timed out.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187AC B18187AC
actions.
Explanation: An error occurred when an SSL socket
was being closed at the same time an SSL connect was
B18187B3 B18187B3
occuring.
Explanation: A socked error occurred.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187AD B18187AD
Explanation: There was an error when closing a
socket.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 345
B18187B4 • B18187C1
callouts detailed with the SRC to determine service
B18187B4 B18187B4
actions.
Explanation: A connection failed.
Response: If this is a tracking event, no service actions B18187BB B18187BB
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when sending a serial
callouts detailed with the SRC to determine service
connection message.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18187B5 B18187B5
callouts detailed with the SRC to determine service
Explanation: An error occurred in a selection. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B18187BC B18187BC
callouts detailed with the SRC to determine service
Explanation: An error occurred in a send operation.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18187B6 B18187B6
callouts detailed with the SRC to determine service
Explanation: An error occurred when trying to make a actions.
connection.
Response: If this is a tracking event, no service actions B18187BD B18187BD
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when opening a port
callouts detailed with the SRC to determine service
number.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18187B7 B18187B7
callouts detailed with the SRC to determine service
Explanation: An error occurred when trying to make a actions.
connection.
Response: If this is a tracking event, no service actions B18187BF B18187BF
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when writing to a
callouts detailed with the SRC to determine service
port.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18187B8 B18187B8
callouts detailed with the SRC to determine service
Explanation: There was a secure read failure. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B18187C0 B18187C0
callouts detailed with the SRC to determine service
Explanation: An error occurred in a system call.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18187B9 B18187B9
callouts detailed with the SRC to determine service
Explanation: An error occurred when sending a serial actions.
connection message.
Response: If this is a tracking event, no service actions B18187C1 B18187C1
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when setting up the
callouts detailed with the SRC to determine service
passwords.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B18187BA B18187BA
callouts detailed with the SRC to determine service
Explanation: An error occurred when sending a actions.
disconnection message.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
346 System reference codes (Bxxx)
B18187C2 • B18187CD
B18187C2 B18187C2 B18187C8 B18187C8
Explanation: An error occurred when sending a Explanation: The universal asynchronous
message. receiver/transmitter (UART) ADAL configuration
failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187C3 B18187C3
B18187C9 B18187C9
Explanation: An error occurred in a receive operation.
Explanation: The universal asynchronous
Response: If this is a tracking event, no service actions
receiver/transmitter (UART) ADAL configuration
are required. Otherwise, use the FRU and procedure
failed.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187C4 B18187C4
actions.
Explanation: The universal asynchronous
receiver/transmitter (UART) device abstraction layer
B18187CA B18187CA
(ADAL) configuration failed.
Explanation: There was a time-out on the secure
Response: If this is a tracking event, no service actions
receive.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B18187C5 B18187C5
Explanation: The universal asynchronous
B18187CB B18187CB
receiver/transmitter (UART) ADAL configuration
failed. Explanation: A secure receive error occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18187C6 B18187C6 B18187CC B18187CC
Explanation: The universal asynchronous Explanation: A polling error occurred.
receiver/transmitter (UART) ADAL configuration
Response: If this is a tracking event, no service actions
failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B18187CD B18187CD
Explanation: Poll events occurred on the secure
B18187C7 B18187C7
receive.
Explanation: The universal asynchronous
Response: If this is a tracking event, no service actions
receiver/transmitter (UART) ADAL configuration
are required. Otherwise, use the FRU and procedure
failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 347
B18187CE • B18187DA
B18187CE B18187CE B18187D5 B18187D5
Explanation: A secure receive operation failed. Explanation: An error was returned from a system
call.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187CF B18187CF
B18187D6 B18187D6
Explanation: An error occurred in a secure receive
operation. Explanation: An error occurred when closing the
serial connection.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187D0 B18187D0
B18187D7 B18187D7
Explanation: An error occurred when reading a
registry value. Explanation: An error occurred when closing the eth0
connection.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187D1 B18187D1
B18187D8 B18187D8
Explanation: A connection error occurred in TCP/IP.
Explanation: An error occurred when closing the eth1
Response: If this is a tracking event, no service actions
connection.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B18187D2 B18187D2
Explanation: A socket error occurred
B18187D9 B18187D9
Response: If this is a tracking event, no service actions
Explanation: There was a time-out on the secure
are required. Otherwise, use the FRU and procedure
receive.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187D3 B18187D3
actions.
Explanation: A socket time-out occurred.
Response: If this is a tracking event, no service actions B18187DA B18187DA
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when receiving.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187D4 B18187D4
actions.
Explanation: An error occurred when closing a socket.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
348 System reference codes (Bxxx)
B18187DB • B18187E7
B18187DB B18187DB B18187E1 B18187E1
Explanation: An error was returned from a system Explanation: There was an error in SSL write.
call.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18187E2 B18187E2
B18187DC B18187DC
Explanation: An error occurred in a send/receive
Explanation: A time-out occurred while waiting for function.
data.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18187E3 B18187E3
B18187DD B18187DD
Explanation: An error occurred when reading the
Explanation: There was an error in SSL receive. registry.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18187DE B18187DE B18187E4 B18187E4
Explanation: There was an error in secure receive. Explanation: A private key failure occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B18187DF B18187DF B18187E5 B18187E5
Explanation: An error was returned by the poll Explanation: A read certificate and key error occurred.
command.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B18187E6 B18187E6
B18187E0 B18187E0
Explanation: A private key mismatch occurred.
Explanation: An error occurred in a message
Response: If this is a tracking event, no service actions
processing function.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B18187E7 B18187E7
Explanation: Unable to complete a connection, but not
because of a time-out.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 349
B18187E8 • B18187F4
callouts detailed with the SRC to determine service
B18187EE B18187EE
actions.
Explanation: An error occured when getting the
header.
B18187E8 B18187E8
Response: If this is a tracking event, no service actions
Explanation: An error occurred when trying to close a
are required. Otherwise, use the FRU and procedure
TCP/IP connection.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187EF B18187EF
actions.
Explanation: There was a timeout while waiting for
TCP/IP.
B18187E9 B18187E9
Response: If this is a tracking event, no service actions
Explanation: An SSL handshake failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B18187F0 B18187F0
Explanation: A certificate clean-up error occurred.
B18187EA B18187EA
Response: If this is a tracking event, no service actions
Explanation: These was an error in a write operation.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B18187F1 B18187F1
Explanation: There was an error in TCP/IP "select".
B18187EB B18187EB
Response: If this is a tracking event, no service actions
Explanation: There was an error in TCP/IP select.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B18187F2 B18187F2
Explanation: A semaphore error occurred.
B18187EC B18187EC
Response: If this is a tracking event, no service actions
Explanation: A timeout occurred in "select" while
are required. Otherwise, use the FRU and procedure
waiting for data.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187F3 B18187F3
actions.
Explanation: An SSL shutdown failure occurred.
B18187ED B18187ED Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred in "received message".
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18187F4 B18187F4
actions.
Explanation: A set up error occurred.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
350 System reference codes (Bxxx)
B18187F5 • B1818801
B18187F5 B18187F5 B18187FB B18187FB
Explanation: Generating a key failed. Explanation: An error occurred when writing a
registry value.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187F6 B18187F6
B18187FC B18187FC
Explanation: An error occurred in when closing a
connection. Explanation: Bad data was sent in through a
constructor .
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187F7 B18187F7
B18187FD B18187FD
Explanation: An error occurred when reading a
registry. Explanation: There was an error in creating an ivSSL
object using the SSL_new() function.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187F8 B18187F8
B18187FE B18187FE
Explanation: An error occurred in a sibling
connection. Explanation: An error occurred in setting a socket
option.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187F9 B18187F9
B18187FF B18187FF
Explanation: An error occurred when connecting to
the first interface. Explanation: The ssl connection timed out during the
open ssl operation.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B18187FA B18187FA
B1818801 B1818801
Explanation: There was an error when obtaining the
private key for SSL communications. Explanation: Failed to get access to shared memory.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 351
B1818802 • B181880D
B1818802 B1818802 B1818808 B1818808
Explanation: Failed to attach to shared memory area. Explanation: Failed to create shared memory.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818803 B1818803 B1818809 B1818809
Explanation: An invalid pointer was passed into a Explanation: Failed to start instructions on the
function. selected processor to run a service routine.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818804 B1818804 B181880A B181880A
Explanation: Failed to create a sychronization file that Explanation: Failed to write to the registry which
is used to inform other code modules about the serves as a flag to indicate a service routine is running.
completion of a signal handling operation.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181880B B181880B
B1818805 B1818805
Explanation: An invalid service routine was
Explanation: Failed to read a registry value. requested.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818806 B1818806 B181880C B181880C
Explanation: Failed to write to registry which serves Explanation: An invalid command was found in the
as a flag to indicate that a service routine is no longer attention memory area; it does not match the service
running. routine that was requested.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818807 B1818807 B181880D B181880D
Explanation: Failed to detach shared memory area. Explanation: Received a fatal attention during a
service routine run.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
352 System reference codes (Bxxx)
B181880E • B181881A
callouts detailed with the SRC to determine service
B181880E B181880E
actions.
Explanation: Failed to erase shared memory.
Response: If this is a tracking event, no service actions B1818815 B1818815
are required. Otherwise, use the FRU and procedure
Explanation: Failed to read the general purpose
callouts detailed with the SRC to determine service
registers.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181880F B181880F
callouts detailed with the SRC to determine service
Explanation: Failed to get the status of a thread. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818816 B1818816
callouts detailed with the SRC to determine service
Explanation: Failed to set up registers during the
actions.
setup to run service routines.
Response: If this is a tracking event, no service actions
B1818810 B1818810
are required. Otherwise, use the FRU and procedure
Explanation: No threads are functional on the callouts detailed with the SRC to determine service
requested processor core. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818817 B1818817
callouts detailed with the SRC to determine service
Explanation: Failed to read the special purpose
actions.
registers.
Response: If this is a tracking event, no service actions
B1818811 B1818811
are required. Otherwise, use the FRU and procedure
Explanation: A dependent process was not running. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818818 B1818818
actions.
Explanation: Failed to set up a register during the
setup to run service routines.
B1818812 B1818812
Response: If this is a tracking event, no service actions
Explanation: Failed to start a dependent process are required. Otherwise, use the FRU and procedure
which is required to run a service routine. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818819 B1818819
actions.
Explanation: Failed to save memory area during the
setup to run service routines.
B1818813 B1818813
Response: If this is a tracking event, no service actions
Explanation: A request was made to run a service are required. Otherwise, use the FRU and procedure
routine on a processor core that is not functional. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181881A B181881A
actions.
Explanation: Failed to get the proper fabric identity so
that storage could be read.
B1818814 B1818814
Response: If this is a tracking event, no service actions
Explanation: Failed to get selected processor core are required. Otherwise, use the FRU and procedure
functionality. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 353
B181881B • B1818827
B181881B B181881B B1818821 B1818821
Explanation: Failed to unmap the memory pointed to Explanation: Failed to intialize a buffer during the
by the processor control area addresses. setup to run a service routine.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181881C B181881C B1818822 B1818822
Explanation: Failed to get the processor control area Explanation: Failed to write the service routine
from the host data area. address into a general purpose register.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181881D B181881D B1818824 B1818824
Explanation: Failed to read memory during the setup Explanation: Failed to set up the special purpose
to run a service routine. registers.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181881E B181881E B1818825 B1818825
Explanation: Timed out waiting for the service routine Explanation: Failed to intialize a buffer during the
to finish. setup to run a service routine.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181881F B181881F B1818826 B1818826
Explanation: Failed to erase a synchronization file. Explanation: Failed to intialize a buffer during the
setup to run a service routine.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818820 B1818820
B1818827 B1818827
Explanation: Failed to get access to a structure
necessary to run a service routine. Explanation: Failed to set up the special purpose
registers to run a service routine.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
354 System reference codes (Bxxx)
B1818828 • B1818904
callouts detailed with the SRC to determine service
B1818828 B1818828
actions.
Explanation: Failed to save a register value during the
setup to run a service routine.
B1818832 B1818832
Response: If this is a tracking event, no service actions
Explanation: Failed to intialize a register during the
are required. Otherwise, use the FRU and procedure
setup to run a service routine.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181882A B181882A
actions.
Explanation: Failed to write the reset vector.
Response: If this is a tracking event, no service actions B1818833 B1818833
are required. Otherwise, use the FRU and procedure
Explanation: An invalid service routine address was
callouts detailed with the SRC to determine service
detected.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181882B B181882B
callouts detailed with the SRC to determine service
Explanation: Failed to get the thread status. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818834 B1818834
callouts detailed with the SRC to determine service
Explanation: Failed to write to service routine state in
actions.
the registry to indicate that a service routine is not
running.
B181882C B181882C
Response: If this is a tracking event, no service actions
Explanation: Failed to write the reset vector. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1818901 B1818901
Explanation: An error occurred when the service
B181882D B181882D processor synchronization (SINK) interface tried to read
firmware data.
Explanation: The service routine address was not
valid.
B1818902 B1818902
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: The service processor synchronization
callouts detailed with the SRC to determine service (SINK) interface timed out waiting for a firmware
actions. component to create a synchronization lock.
B1818830 B1818830 B1818903 B1818903
Explanation: Failed to write to memory during the Explanation: The service processor synchronization
setup to run a service routine. (SINK) interface timed out waiting for a firmware
component to establish a synchronization lock.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1818904 B1818904
actions.
Explanation: An invalid synchronization lock was
passed to the service processor synchronization (SINK)
B1818831 B1818831 interface.
Explanation: Failed to release a reserved ID.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 355
B1818905 • B181894E
B1818905 B1818905 B1818910 B1818910
Explanation: An invalid synchronization lock file was Explanation: An invalid parameter was passed to the
passed to the service processor synchronization (SINK) service processor synchronization (SINK) interface.
interface.
B1818911 B1818911
B1818906 B1818906
Explanation: The service processor synchronization
Explanation: A firmware component failed to create a (SINK) interface was not able to synchronize with a
synchronization lock. specific firmware component.
B1818907 B1818907 B1818912 B1818912
Explanation: The service processor synchronization Explanation: The service processor synchronization
(SINK) interface detected that another firmware server (SINK) interface timed out waiting for a
is currently running. synchronization lock to be established by another
firmware component.
B1818908 B1818908
B1818913 B1818913
Explanation: An error occurred when the service
processor synchronization (SIN K) interface tried to Explanation: An invalid file was passed to the service
delete a synchronization lock. processor synchronization (SINK) interface.
B181890A B181890A B1818914 B1818914
Explanation: An internal error occurred in the service Explanation: Invalid arguments were passed to the
processor synchronization (SINK) interface. service processor synchronization (SINK) interface.
B181890B B181890B B1818915 B1818915
Explanation: An error occurred when the service Explanation: The maximum number of files that are
processor synchronization (SINK) interface tried to read allowed to be created and open using process
firmware data. synchronization was exceeded.
B181890C B181890C B1818916 B1818916
Explanation: An invalid file was passed to the service Explanation: An invalid parameter was passed to the
processor synchronization (SINK) interface. service processor synchronization (SINK) interface.
B181890D B181890D B1818917 B1818917
Explanation: An error occurred when the service Explanation: The service processor synchronization
processor synchronization (SINK) interface tried to (SINK) interface timed out waiting for the power
build a directory path. interface to stabilize.
B181890E B181890E B1818918 B1818918
Explanation: An invalid file was passed to the service Explanation: The service processor synchronization
processor synchronization (SINK) interface. (SINK) interface detected a synchronization error
between two firmware components.
B181890F B181890F
B181894E B181894E
Explanation: A firmware component passed an invalid
file to the service processor synchronization (SINK) Explanation: The system controller received bad data
interface. back after sending a "hold sibling in reset command" to
a node controller.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
356 System reference codes (Bxxx)
B1818A02 • B1818A10
B1818A02 B1818A02 B1818A09 B1818A09
Explanation: The calling component requested an Explanation: Redudant "side" write operation failed
invalid key. due to a stream failure.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818A03 B1818A03 B1818A0A B1818A0A
Explanation: The calling component did not provide a Explanation: Util failed to accurately acquire the size
buffer large enough for reading the data. of a registry key due to an underlying building block
failure.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818A04 B1818A04
B1818A0B B1818A0B
Explanation: The util registry write operation failed
due to the an underlying building block failure. Explanation: A was failure detected when forming a
path to a registry key.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818A05 B1818A05
B1818A0E B1818A0E
Explanation: The platform extension information for
this registry key was not retrieved correctly. Explanation: The current util file operation failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818A06 B1818A06 B1818A0F B1818A0F
Explanation: Redudant "side" write operation failed. Explanation: The current util operation failed because
the file in question is not open.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818A07 B1818A07
B1818A10 B1818A10
Explanation: An operation to send a signal event for
the current registry key failed. Explanation: The current util operation failed due to
end-of-file being reached.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 357
B1818A11 • B1818A1D
B1818A11 B1818A11 B1818A18 B1818A18
Explanation: The memory pointer acquired from a Explanation: The semaphore operation failed; possible
caller is invalid. file system problems.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818A12 B1818A12 B1818A19 B1818A19
Explanation: An operation failed due to end-of-file Explanation: A semaphore initialization failure
being reached on the current stream. occurred due to system call failure; possible kernel
problem.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818A13 B1818A13
B1818A1A B1818A1A
Explanation: The operation to remove a file failed;
possible file system isssue. Explanation: The operation to dynamically load a
library failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818A14 B1818A14
B1818A1B B1818A1B
Explanation: The file lock operation failed to acquire
the lock that was requested; possible system-wide Explanation: A failure occurred when loading a
problem shared library symbol.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818A16 B1818A16 B1818A1C B1818A1C
Explanation: Failure to initialize a semaphore; possible Explanation: The operation to synchronize the current
kernel issue. registry key to the back-up failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818A17 B1818A17 B1818A1D B1818A1D
Explanation: Failure to initialize a semaphore; possible Explanation: Failed to get a value.
kernel problem.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
358 System reference codes (Bxxx)
B1818A1E • B1818B14
B1818A1E B1818A1E B1818A32 B1818A32
Explanation: The operation to read a registry key has Explanation: A binary semaphore was already
failed due to a failure in the underlying building block unlocked.
method.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B10 B1818B10
B1818A1F B1818A1F
Explanation: Unable to configure the virtual local area
Explanation: An operation failed to read a platform network (VLAN) adapter.
extension due to a failure in an underlying building
Response: If this is a tracking event, no service actions
block method.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818B11 B1818B11
Explanation: Unable to configure the virtual local area
B1818A20 B1818A20
network (VLAN) adapter.
Explanation: The operation to synchronize the file
Response: If this is a tracking event, no service actions
operation via RMGR has failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818B12 B1818B12
Explanation: An error occurred when reading the
B1818A21 B1818A21
valid bits.
Explanation: The operation failed while reading the
Response: If this is a tracking event, no service actions
file stream.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818B13 B1818B13
Explanation: An error occurred when setting the
B1818A2C B1818A2C
interface.
Explanation: Unable to open a firmware component.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B14 B1818B14
B1818A2D B1818A2D
Explanation: Unable to set the hostname.
Explanation: Unable to set bits in a register.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 359
B1818B15 • B1818B22
callouts detailed with the SRC to determine service
B1818B15 B1818B15
actions.
Explanation: Unable to add the virtual local area
network (VLAN) adapter to the system.
B1818B1D B1818B1D
Response: If this is a tracking event, no service actions
Explanation: A n error occurred when writing a
are required. Otherwise, use the FRU and procedure
variable.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818B16 B1818B16
actions.
Explanation: A problem occurred when resolving the
name of a domain name server.
B1818B1E B1818B1E
Response: If this is a tracking event, no service actions
Explanation: A network reset was issued as the pin
are required. Otherwise, use the FRU and procedure
value changed.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818B17 B1818B17
actions.
Explanation: Unable to write to the flash memory.
Response: If this is a tracking event, no service actions B1818B1F B1818B1F
are required. Otherwise, use the FRU and procedure
Explanation: Unable to add the VLAN adapter to the
callouts detailed with the SRC to determine service
system.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1818B18 B1818B18
callouts detailed with the SRC to determine service
Explanation: Unable to write to a file. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818B20 B1818B20
callouts detailed with the SRC to determine service
Explanation: Unable to set the hostname.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1818B19 B1818B19
callouts detailed with the SRC to determine service
Explanation: Unable to configure the adapter. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818B21 B1818B21
callouts detailed with the SRC to determine service
Explanation: An error occurred when reading the
actions.
valid bits.
Response: If this is a tracking event, no service actions
B1818B1A B1818B1A
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when writing the callouts detailed with the SRC to determine service
gateway address. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1818B22 B1818B22
callouts detailed with the SRC to determine service
Explanation: An error occurred when writing the
actions.
gateway address.
Response: If this is a tracking event, no service actions
B1818B1C B1818B1C
are required. Otherwise, use the FRU and procedure
Explanation: A n error occurred when writing the callouts detailed with the SRC to determine service
virtual local area network (VLAN) address. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
360 System reference codes (Bxxx)
B1818B23 • B1818B3B
B1818B23 B1818B23 B1818B32 B1818B32
Explanation: An error occurred when writing the Explanation: An error occurred when setting the
gateway address. virtual local area network (VLAN) enabled/disabled
flag to enabled .
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818B24 B1818B24
B1818B34 B1818B34
Explanation: An invalid network configuration was
specified. Explanation: Unable to set the hostname.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B25 B1818B25 B1818B35 B1818B35
Explanation: An error occurred when writing the Explanation: A virtual LAN was removed.
virtual local area network (VLAN) ID.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B36 B1818B36
B1818B26 B1818B26
Explanation: A virtual LAN was added.
Explanation: Unable to configure the adapter.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B39 B1818B39
B1818B2B B1818B2B
Explanation: A configuration file was opened.
Explanation: An invalid user error occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B3A B1818B3A
B1818B31 B1818B31
Explanation: A socket was opened.
Explanation: A network reset was issued because the
Response: If this is a tracking event, no service actions
pin value changed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818B3B B1818B3B
Explanation: Unable to open the device.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 361
B1818B40 • B1818B4F
B1818B40 B1818B40 B1818B48 B1818B48
Explanation: An ARP socked was opened. Explanation: An ARP binding failure occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B41 B1818B41 B1818B49 B1818B49
Explanation: An ARP socket binding failure occurred. Explanation: Failed to get the address.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B42 B1818B42 B1818B4A B1818B4A
Explanation: An ARP operation to get the IP address Explanation: Failed to get the IP address.
failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B4C B1818B4C
B1818B43 B1818B43
Explanation: A receive failure occurred.
Explanation: An ARP get IP address operation failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B4D B1818B4D
B1818B45 B1818B45
Explanation: A polling failure occurred.
Explanation: Failed to correctly route mailbox traffic.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B4E B1818B4E
B1818B46 B1818B46
Explanation: A failure occurred when creating a route.
Explanation: Failed to route mailbox traffic.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B4F B1818B4F
B1818B47 B1818B47
Explanation: An ARP failure occurred.
Explanation: An DHCP failure occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
362 System reference codes (Bxxx)
B1818B50 • B1818B62
B1818B50 B1818B50 B1818B58 B1818B58
Explanation: An ARP open failure occurred. Explanation: A machine type/model/serial number
mismatch occurred.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818B51 B1818B51
B1818B5C B1818B5C
Explanation: An error occurred with a daemon.
Explanation: An invalid IP address was found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818B52 B1818B52
B1818B5D B1818B5D
Explanation: An error occurred with a daemon.
Explanation: An invalid gateway was found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818B53 B1818B53
B1818B5E B1818B5E
Explanation: An error occurred when receiving a
message. Explanation: An internal error occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B54 B1818B54 B1818B60 B1818B60
Explanation: An internal error occurred. Explanation: Unable to write to a file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B55 B1818B55 B1818B61 B1818B61
Explanation: A machine type/model/serial number Explanation: Failed to set the gateway (IPv4).
mismatch occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B62 B1818B62
B1818B57 B1818B57
Explanation: An address was null.
Explanation: An I/O control failure occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 363
B1818B63 • B1818B77
B1818B63 B1818B63 B1818B72 B1818B72
Explanation: A subnet failure occurred (IPv4). Explanation: Failed to set the gateway.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B64 B1818B64 B1818B73 B1818B73
Explanation: A subnet mask was null. Explanation: The interface was not found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B65 B1818B65 B1818B74 B1818B74
Explanation: A broadcast address failure occurred Explanation: A hardware failure occurred when
(IPv4). getting the IP address.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B66 B1818B66 B1818B75 B1818B75
Explanation: A broadcast address was null. Explanation: A hardware failure occurred when
getting the subnet.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818B67 B1818B67
B1818B76 B1818B76
Explanation: The routing file was not found.
Explanation: A hardware failure occurred when
Response: If this is a tracking event, no service actions
getting the broadcast address.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818B68 B1818B68
Explanation: An IPv4 address failed.
B1818B77 B1818B77
Response: If this is a tracking event, no service actions
Explanation: Failed to set the IP address in the
are required. Otherwise, use the FRU and procedure
hardware.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818B70 B1818B70
actions.
Explanation: A listif command failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
364 System reference codes (Bxxx)
B1818B78 • B1818B93
B1818B78 B1818B78 B1818B87 B1818B87
Explanation: A hardware failure occurred when Explanation: A failure occurred when getting the
setting the subnet. hostname.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B79 B1818B79 B1818B88 B1818B88
Explanation: Failed to set the broadcast address. Explanation: A socket open failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B80 B1818B80 B1818B89 B1818B89
Explanation: An IPv6 address failed. Explanation: An unsupported link speed was found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B82 B1818B82 B1818B90 B1818B90
Explanation: An invalid prototype was found. Explanation: There was an error in the link speed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B83 B1818B83 B1818B91 B1818B91
Explanation: Getting the IF flags failed. Explanation: A link status error occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1818B84 B1818B84 B1818B92 B1818B92
Explanation: Setting the IF flags failed. Explanation: A failure occurred when processing a
file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1818B85 B1818B85
B1818B93 B1818B93
Explanation: No prototype was found.
Explanation: An IP address failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 365
B1818B94 • B1818BA1
B1818B94 B1818B94 B1818B9A B1818B9A
Explanation: The maximum number of DHCP Explanation: An invalid buffer type was found.
addresses was exceeded.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818B9B B1818B9B
B1818B95 B1818B95
Explanation: An address was not found (IPv4).
Explanation: The maximum number of static
Response: If this is a tracking event, no service actions
addresses was exceeded.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1818B9D B1818B9D
Explanation: The buffer was too small.
B1818B96 B1818B96
Response: If this is a tracking event, no service actions
Explanation: The maximum number of addresses was
are required. Otherwise, use the FRU and procedure
exceeded (IPv6).
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818B9E B1818B9E
actions.
Explanation: A null pointer was passed into a
function.
B1818B97 B1818B97
Response: If this is a tracking event, no service actions
Explanation: The maximum number of addresses was
are required. Otherwise, use the FRU and procedure
exceeded (IPv4).
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818B9F B1818B9F
actions.
Explanation: The interface configuration was invalid.
B1818B98 B1818B98 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An invalid address type was found.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818BA0 B1818BA0
actions.
Explanation: An invalid buffer size was found.
B1818B99 B1818B99 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An invalid version was found.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818BA1 B1818BA1
actions.
Explanation: The dynamic host (DH) client stopped.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
366 System reference codes (Bxxx)
B1818BA2 • B1818CAC
B1818BA2 B1818BA2 B1818C0F B1818C0F
Explanation: The dynamic host (DH) client was Explanation: An unknown card was found.
released.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1818C11 B1818C11
B1818BA4 B1818BA4
Explanation: The netv daemon was unable to open
Explanation: A DHCP directory failure occurred. the FSI device to get the side ID that is used to
determine which bulk power controller (BPC) the
Response: If this is a tracking event, no service actions
daemon was running on.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818BA5 B1818BA5
Explanation: A PID failure occurred.
B1818C12 B1818C12
Response: If this is a tracking event, no service actions
Explanation: The netv daemon determined that there
are required. Otherwise, use the FRU and procedure
are too many error logs to the be transferred to the
callouts detailed with the SRC to determine service
system client.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1818C09 B1818C09
callouts detailed with the SRC to determine service
Explanation: The netv daemon was unable to read the actions.
side ID that is used to determine which bulk power
controller (BPC) the daemon was running on.
B1818C57 B1818C57
Response: If this is a tracking event, no service actions
Explanation: The VLAN map configuration is not
are required. Otherwise, use the FRU and procedure
valid.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1818C0A B1818C0A
actions.
Explanation: Unable to determine which bulk power
controller (BPC) the netv daemon is running on.
B1818C58 B1818C58
Response: If this is a tracking event, no service actions
Explanation: The PVID configuration is not valid.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818C0B B1818C0B
Explanation: Unable to determine the type of
B1818CAC B1818CAC
enclosure.
Explanation: A host on the network has an invalid IP
Response: If this is a tracking event, no service actions
address.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 367
B1818CAE • B181900C
callouts detailed with the SRC to determine service
B1818CAE B1818CAE
actions.
Explanation: Duplicate IP addresses were detected;
the system firmware should be updated. If the
B1819005 B1819005
condition persists, replace the hardware that is
reporting the duplicate addresses. Explanation: An internal service processor error
occurred. Check for system firmware updates and
Response: If this is a tracking event, no service actions
apply if available before replacing the service processor.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1818CAF B1818CAF
Explanation: Duplicate MAC addresses were found on
B1819009 B1819009
Ethernet ports.
Explanation: An internal service processor error
Response: If this is a tracking event, no service actions
occurred. Check for system firmware updates and
are required. Otherwise, use the FRU and procedure
apply if available before replacing the service processor.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819001 B1819001
actions.
Explanation: An internal service processor error
occurred. Check for system firmware updates and
B181900A B181900A
apply if available before replacing the service processor.
Explanation: An internal service processor error
Response: If this is a tracking event, no service actions
occurred while trying to allocate memory. The service
are required. Otherwise, use the FRU and procedure
processor reset itself to recover from the error.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819002 B1819002
actions.
Explanation: An internal service processor error
occurred. Check for system firmware updates and
B181900B B181900B
apply if available before replacing the service processor.
Explanation: An internal service processor error
Response: If this is a tracking event, no service actions
occurred while trying to allocate memory. The service
are required. Otherwise, use the FRU and procedure
processor reset itself to recover from the error.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819003 B1819003
actions.
Explanation: An internal service processor error
occurred. Check for system firmware updates and
B181900C B181900C
apply if available before replacing the service processor.
Explanation: An internal service processor error
Response: If this is a tracking event, no service actions
occurred while trying to allocate memory. The service
are required. Otherwise, use the FRU and procedure
processor reset itself to recover from the error.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819004 B1819004
actions.
Explanation: An internal service processor error
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
368 System reference codes (Bxxx)
B181900F • B1819020
callouts detailed with the SRC to determine service
B181900F B181900F
actions.
Explanation: An internal service processor error
occurred. Check for system firmware updates and
B181901B B181901B
apply if available before replacing the service processor.
Explanation: An internal service processor error
Response: If this is a tracking event, no service actions
occurred. Check for system firmware updates and
are required. Otherwise, use the FRU and procedure
apply if available before replacing the service processor.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819010 B1819010
actions.
Explanation: An internal service processor error
occurred. Check for system firmware updates and
B181901C B181901C
apply if available before replacing the service processor.
Explanation: An internal service processor error
Response: If this is a tracking event, no service actions
occurred while configuring CEC memory. Check for
are required. Otherwise, use the FRU and procedure
system firmware updates and apply if available before
callouts detailed with the SRC to determine service
replacing the service processor.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1819011 B1819011
callouts detailed with the SRC to determine service
Explanation: An internal service processor error actions.
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
B181901D B181901D
Response: If this is a tracking event, no service actions
Explanation: An internal service processor error
are required. Otherwise, use the FRU and procedure
occurred. Check for system firmware updates and
callouts detailed with the SRC to determine service
apply if available before replacing the service processor.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1819012 B1819012
callouts detailed with the SRC to determine service
Explanation: An internal service processor error actions.
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
B181901F B181901F
Response: If this is a tracking event, no service actions
Explanation: An integrity check failed on data that the
are required. Otherwise, use the FRU and procedure
service processor retrieved from CEC memory.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819015 B1819015
actions.
Explanation: An internal service processor error
occurred. Check for system firmware updates and
B1819020 B1819020
apply if available before replacing the service processor.
Explanation: An internal service processor error
Response: If this is a tracking event, no service actions
occurred. Check for system firmware updates and
are required. Otherwise, use the FRU and procedure
apply if available before replacing the service processor.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819019 B1819019
actions.
Explanation: An internal service processor error
occurred. Check for system firmware updates and
apply if available before replacing the service processor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 369
B1819021 • B1819037
B1819021 B1819021 B181902A B181902A
Explanation: An internal service processor error Explanation: An integrity check failed on data that the
occurred. Check for system firmware updates and service processor retrieved from CEC memory.
apply if available before replacing the service processor.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181902B B181902B
B1819022 B1819022
Explanation: The current communications link to the
Explanation: The service processor could not find vital hypervisor (PSI) for a service processor was not found
product data (VPD) for a FRU. or is not functional.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1819023 B1819023 B181902C B181902C
Explanation: The service processor could not find the Explanation: The operation initiated by
vital product data (VPD) for a FRU. mboxmainprocess was unable to open the mbox device
driver within the allotted time.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1819024 B1819024
B181902D B181902D
Explanation: The service processor could not find vital
product data (VPD) for a FRU. Explanation: An attempt was made by a user to set
the hypervisor mode to a value that is not allowed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1819027 B1819027
B1819034 B1819034
Explanation: An internal service processor error
occurred. Check for system firmware updates and Explanation: An invalid SCOM address was found in
apply if available before replacing the service processor. the AVP test case list.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1819029 B1819029 B1819037 B1819037
Explanation: An internal service processor error Explanation: The load type of the test case structure
occurred. Check for system firmware updates and did not indicate a memory-type test case.
apply if available before replacing the service processor.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
370 System reference codes (Bxxx)
B181903B • B1819203
B181903B B181903B B1819044 B1819044
Explanation: A null functional unit pointer was found Explanation: The CEC cage number that was provided
while iterating through the list of core functional units did not match the CEC cage number that was expected.
that were found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181904E B181904E
B181903D B181903D
Explanation: A failure occurred while writing the test
Explanation: An error occurred in a routine. case data from a file into the data buffer.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181903E B181903E B1819051 B1819051
Explanation: The test did not finish in the allotted Explanation: Failed to get the instruction status for the
time. core.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181903F B181903F B1819054 B1819054
Explanation: The data in the status address is not Explanation: A null functional unit pointer was found
changing. If the test were running successfully, this while iterating through the list of core functional units
address should be changing. that were found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1819041 B1819041 B1819201 B1819201
Explanation: Unable to get the functional unit group Explanation: An I/O control operation failed when
for the CEC cage. trying to set the data terminal ready (DTR) pin.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1819043 B1819043 B1819203 B1819203
Explanation: A firmware error occurred. Explanation: Internal software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 371
B1819204 • B1819505
B1819204 B1819204 B181920E B181920E
Explanation: The operating system protocol does not Explanation: A failure occurred when reading data
match the currently-supported service processor from a serial port.
version.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181920F B181920F
B1819207 B1819207
Explanation: A write operation to the serial port
Explanation: The open operation on the requested failed.
device, a serial port, failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1819210 B1819210
B1819208 B1819208
Explanation: Internal software error.
Explanation: The firmware was asked to open a serial
Response: If this is a tracking event, no service actions
port that does not exist. The only valid serial ports are
are required. Otherwise, use the FRU and procedure
S1 and S2.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819212 B1819212
actions.
Explanation: The firmware got stuck for more than
two seconds when trying to write to a serial port. The
B181920A B181920A
write operation will be restarted and an error logged.
Explanation: Internal software error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1819502 B1819502
B181920B B181920B
Explanation: Unable to initialize the mutexes for
Explanation: A request was made for the modem locking classes.
control signal status but the port was not open.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1819505 B1819505
B181920C B181920C
Explanation: Failure to create a semaphore.
Explanation: An I/O control error occurred when
Response: If this is a tracking event, no service actions
trying to read the status register.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
372 System reference codes (Bxxx)
B1819506 • B1819518
B1819506 B1819506 B181950D B181950D
Explanation: The kernel call failed to create a thread Explanation: The size of the data sent exceeded the
maximum allowed size.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B1819507 B1819507
B181950E B181950E
Explanation: The service processor was unable to
make an entry in its error log that the hypervisor Explanation: Unable to start the timer to block code
requested update.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1819509 B1819509 B1819510 B1819510
Explanation: The kernel device driver returned an Explanation: The service processor was unable to
error writing hardware settings establish a virtual session on a serial port
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181950A B181950A B1819516 B1819516
Explanation: No bytes were r eturned by a mailbox Explanation: An invalid message received by the
read. service processor
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181950B B181950B B1819517 B1819517
Explanation: The mailbox daemon is not running, so Explanation: Unable to receive the error log from the
no attempt can be made to talk to the hypervisor. daemon.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181950C B181950C B1819518 B1819518
Explanation: The hypervisor requested the execution Explanation: Unable to initialize the processing
of a function in the service processor firmware, and the queues.
execution of that function resulted in an error
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 373
B1819519 • B181952A
B1819519 B1819519 B1819524 B1819524
Explanation: The service processor attempted to pass Explanation: The kernel device driver returned error
an invalid value to the hypervisor when setting or clearing bits
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181951A B181951A B1819525 B1819525
Explanation: The state manager returned bad status. Explanation: The hypervisor sent the service processor
an invalid SRC to display
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181951B B181951B
B1819526 B1819526
Explanation: The service processor (or system
controller) invalidated a dump because it was not a Explanation: Informational message: In a system with
platform or service processor (or system controller) redundant service processors (or system controllers),
dump. there are times when messages from the hypervisor are
blocked; this is expected. This occurred, and does not
Response: If this is a tracking event, no service actions
indicate a problem.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1819520 B1819520
Explanation: The service processor was unable to
B1819527 B1819527
complete state changes during a boot
Explanation: Informational message: In a system with
Response: If this is a tracking event, no service actions
redundant service processors (or system controllers),
are required. Otherwise, use the FRU and procedure
there are times when messages from the hypervisor are
callouts detailed with the SRC to determine service
blocked; this is expected. This occurred, and does not
actions.
indicate a problem.
Response: If this is a tracking event, no service actions
B1819521 B1819521
are required. Otherwise, use the FRU and procedure
Explanation: The HMC is trying to use an invalid ID callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1819528 B1819528
actions.
Explanation: The mailbox device driver failed to open.
Response: If this is a tracking event, no service actions
B1819522 B1819522
are required. Otherwise, use the FRU and procedure
Explanation: A message was sent to the hypervisor callouts detailed with the SRC to determine service
when the hypervisor was in an invalid state to receive actions.
messages
Response: If this is a tracking event, no service actions B181952A B181952A
are required. Otherwise, use the FRU and procedure
Explanation: No tone control block was created by the
callouts detailed with the SRC to determine service
device driver.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
374 System reference codes (Bxxx)
B181952B • B1819539
callouts detailed with the SRC to determine service
B1819533 B1819533
actions.
Explanation: Unable to reset the mailbox device
driver.
B181952B B181952B
Response: If this is a tracking event, no service actions
Explanation: The hypervisor's virtual NVRAM is not
are required. Otherwise, use the FRU and procedure
supported on this system
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819535 B1819535
actions.
Explanation: A duplicate message from the hypervisor
was received in the mailbox. The duplicate will be
B181952C B181952C
discarded, but this may indicate a problem with the PSI
Explanation: The hypervisor attempted to read past interface.
the end of a file
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1819536 B1819536
B181952D B181952D
Explanation: The firmware was unable to generate an
Explanation: An attempt was made to write past the audible sound on the speaker.
end of a file during a synchronization operation.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1819537 B1819537
B1819530 B1819530
Explanation: The hypervisor detected an error with a
Explanation: The hypervisor's virtual NVRAM has an PSI link. If this is predictive, follow the procedures
unexpected size called out in the FRU list in the error log entry. If this is
informational, it was not possible to tell if this
Response: If this is a tracking event, no service actions occurrence was a real error or not.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1819531 B1819531
Explanation: Clearing the hypervisor's NVRAM is not B1819538 B1819538
allowed while the system is running
Explanation: There is no working communication path
Response: If this is a tracking event, no service actions between the service processor and the operating
are required. Otherwise, use the FRU and procedure system.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819532 B1819532 actions.
Explanation: Unable to open the PSI device driver.
Response: If this is a tracking event, no service actions B1819539 B1819539
are required. Otherwise, use the FRU and procedure Explanation: The service processor application
callouts detailed with the SRC to determine service performed an invalid sequence of commands.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 375
B181953A • B1819548
callouts detailed with the SRC to determine service
B1819541 B1819541
actions.
Explanation: The device driver indicated that an error
occurred prior to his operation, so this operation
B181953A B181953A
should be retried.
Explanation: The service processor function is
Response: If this is a tracking event, no service actions
currently in use; repeat the operation later.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1819542 B1819542
Explanation: The VNVRAM block list was the wrong
B181953B B181953B
size during a partial synchronization attempt.
Explanation: The service processor application
Response: If this is a tracking event, no service actions
performed an invalid sequence of commands.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1819544 B1819544
Explanation: The mailbox server has forced an
B181953D B181953D
unlocking of VNVRAM.
Explanation: Informational message: The virtual
Response: If this is a tracking event, no service actions
NVRAM thread did not shut down in time. This might
are required. Otherwise, use the FRU and procedure
cause problems with the hypervisor's virtual NVRAM
callouts detailed with the SRC to determine service
the next time the system is booted.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1819545 B1819545
callouts detailed with the SRC to determine service
actions. Explanation: The error log data read back from the
hypervisor didn't match the data that was written.
B181953E B181953E Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An internal firmware error occurred.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819547 B1819547
actions.
Explanation: A dump notification was sent from the
service processor to the hypervisor.
B181953F B181953F
Response: If this is a tracking event, no service actions
Explanation: The mailbox function was told to
are required. Otherwise, use the FRU and procedure
terminate.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B1819548 B1819548
actions.
Explanation: The mailbox start-up data was not valid.
B1819540 B1819540 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Informational message: The mailbox was
callouts detailed with the SRC to determine service
told to terminate, and it did so without error.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
376 System reference codes (Bxxx)
B1819549 • B181A001
B1819549 B1819549 B1819906 B1819906
Explanation: The data read back from the flash Explanation: The service processor capacity on
memory for virtual NVRAM did not match the data demand (SCOD) interface does not recognize the
that was written. power-off IPL type.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B1819907 B1819907
callouts detailed with the SRC to determine service
Explanation: An error occurred when the service
actions.
processor capacity on demand interface was reading a
registry value.
B181954A B181954A
Response: If this is a tracking event, no service actions
Explanation: Mailbox data was missing. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B1819908 B1819908
Explanation: A firmware component tried to use the
B181954D B181954D service processor capacity on demand (SCOD) interface
in an invalid manner.
Explanation: A block number that is too large was
passed into the function.
B1819909 B1819909
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: An error occurred when the service
callouts detailed with the SRC to determine service processor capacity on demand interface was updating a
actions. firmware entry in the registry.
Response: If this is a tracking event, no service actions
B1819903 B1819903 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An invalid signal was received.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181990A B181990A
callouts detailed with the SRC to determine service
actions. Explanation: An error occurred when the service
processor capacity on demand interface was updating a
firmware entry in the registry.
B1819904 B1819904
Response: If this is a tracking event, no service actions
Explanation: Failed to read the IPL type from the
are required. Otherwise, use the FRU and procedure
registry.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181990B B181990B
actions.
Explanation: An error occurred when the service
processor capacity on demand interface was updating a
B1819905 B1819905
firmware entry in the registry.
Explanation: An error occurred when the service
Response: If this is a tracking event, no service actions
processor capacity on demand interface was writing
are required. Otherwise, use the FRU and procedure
firmware data to the registry.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A001 B181A001
actions.
Explanation: Failed to read a value from the registry.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 377
B181A002 • B181A00D
callouts detailed with the SRC to determine service
B181A008 B181A008
actions.
Explanation: The server is no longer available.
B181A002 B181A002 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to read a registry value.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A009 B181A009
actions.
Explanation: Failed to create the synchronization file
for clients.
B181A003 B181A003
Response: If this is a tracking event, no service actions
Explanation: Failed when trying to read the registry
are required. Otherwise, use the FRU and procedure
value to determine the state of the sibling service
callouts detailed with the SRC to determine service
processor.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A00A B181A00A
callouts detailed with the SRC to determine service
actions. Explanation: Failed to synchronize with the server
process for client commands.
B181A004 B181A004 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed when trying to read the registry to
callouts detailed with the SRC to determine service
determine the value of iplp/SysOpMode.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A00B B181A00B
callouts detailed with the SRC to determine service
actions. Explanation: Failed to create the panlmain daemon
synchronization file.
B181A005 B181A005 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed when trying to read the registry to
callouts detailed with the SRC to determine service
determine the value of panl/SysPwrDnTime.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A00C B181A00C
callouts detailed with the SRC to determine service
actions. Explanation: The panlmain daemon is already up and
running.
B181A006 B181A006 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to read the current power state of
callouts detailed with the SRC to determine service
the system.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A00D B181A00D
callouts detailed with the SRC to determine service
actions. Explanation: Failed to lock the firmware code lock
when trying to execute the desired action for the
decrement button.
B181A007 B181A007
Response: If this is a tracking event, no service actions
Explanation: Failed when trying to write the control
are required. Otherwise, use the FRU and procedure
panel information to the registry.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
378 System reference codes (Bxxx)
B181A00E • B181A020
callouts detailed with the SRC to determine service
B181A00E B181A00E
actions.
Explanation: Failed to lock the mutex.
Response: If this is a tracking event, no service actions B181A015 B181A015
are required. Otherwise, use the FRU and procedure
Explanation: An invalid argument was passed into the
callouts detailed with the SRC to determine service
attention monitor thread.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A00F B181A00F
callouts detailed with the SRC to determine service
Explanation: Failed to lock the mutex. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A016 B181A016
callouts detailed with the SRC to determine service
Explanation: Failed to initialize the desired attribute
actions.
for the thread that is being created.
Response: If this is a tracking event, no service actions
B181A010 B181A010
are required. Otherwise, use the FRU and procedure
Explanation: Failed to unlock the mutex. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181A017 B181A017
actions.
Explanation: Failed to initialize the thread attribute
object for the thread that is being created.
B181A011 B181A011
Response: If this is a tracking event, no service actions
Explanation: Timed out waiting for the mutex are required. Otherwise, use the FRU and procedure
conditional. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181A018 B181A018
actions.
Explanation: Failed to kill the thread holding the
mutex.
B181A012 B181A012
Response: If this is a tracking event, no service actions
Explanation: Failed to wait for mutex conditional. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B181A019 B181A019
Explanation: Failed to connect to the client socket.
B181A013 B181A013
Response: If this is a tracking event, no service actions
Explanation: Failed to wait the allotted idle time for are required. Otherwise, use the FRU and procedure
the worker thread. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181A020 B181A020
actions.
Explanation: Failed to create a socket.
Response: If this is a tracking event, no service actions
B181A014 B181A014
are required. Otherwise, use the FRU and procedure
Explanation: Failed to start the service processor callouts detailed with the SRC to determine service
dump function. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 379
B181A021 • B181A040
B181A021 B181A021 B181A034 B181A034
Explanation: Failed to bind to a socket. Explanation: Failed to close the listening socket.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A022 B181A022 B181A035 B181A035
Explanation: Failed to listen for messages. Explanation: Failed to create the server address socket
object.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A023 B181A023
B181A036 B181A036
Explanation: Failed to accept a socket.
Explanation: Failed to send the message through the
Response: If this is a tracking event, no service actions
accepted connection socket.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A030 B181A030
Explanation: Failed to assign a name to the socket that
B181A037 B181A037
was created.
Explanation: Failed to receive a message through the
Response: If this is a tracking event, no service actions
server-accepted connection socket.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A031 B181A031
Explanation: Failed to begin listening on the socket.
B181A038 B181A038
Response: If this is a tracking event, no service actions
Explanation: The client address socket doesn't exist.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A032 B181A032
Explanation: Failed to accept the connection from a
B181A040 B181A040
listening socket.
Explanation: Failed to send the action response to a
Response: If this is a tracking event, no service actions
concurrent maintenance operation.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A033 B181A033
Explanation: Failed to create or connect to the socket.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
380 System reference codes (Bxxx)
B181A041 • B181A04C
B181A041 B181A041 B181A047 B181A047
Explanation: Failed to receive a reply. Explanation: The reply message that was received
contained an error log.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A042 B181A042
B181A048 B181A048
Explanation: Failed to connect to the panel server to
send a message to be processed. Explanation: The response message was supposed to
contain data; it contained none.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A043 B181A043
B181A049 B181A049
Explanation: An incorrect data size was received for
the function action that was requested. Explanation: Received a response message that was
not the correct type for the message that was sent.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A044 B181A044
B181A04A B181A04A
Explanation: No data was passed into the function.
Explanation: Failed to send the message and receive
Response: If this is a tracking event, no service actions
the reply.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A045 B181A045
Explanation: The function received an invalid
B181A04B B181A04B
parameter.
Explanation: The reply message that was received
Response: If this is a tracking event, no service actions
contained more data than the buffer can hold.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A046 B181A046
Explanation: The reply message that was received did
B181A04C B181A04C
not have the same number of functions that was
requested. Explanation: A reply message was received that did
not contain the right data size.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 381
B181A04D • B181A071
B181A04D B181A04D B181A053 B181A053
Explanation: A power transition request failed. Explanation: The operation request is not allowed
because it was requested on the secondary service
Response: If this is a tracking event, no service actions
processor.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A04E B181A04E
Explanation: The user name in the message is not
B181A054 B181A054
recognized and cannot request a power transition.
Explanation: Failed to receive a message on the event
Response: If this is a tracking event, no service actions
message queue.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A04F B181A04F
Explanation: An invalid power transition type was
B181A060 B181A060
received.
Explanation: Failed to create a timer.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A050 B181A050
B181A061 B181A061
Explanation: Invalid request data was received with
the message. Explanation: Failed to delete a timer.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A051 B181A051 B181A062 B181A062
Explanation: No change flags were set for the system Explanation: Failed to set time for the timer.
dump parameters.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A070 B181A070
B181A052 B181A052
Explanation: The panel function is not active.
Explanation: An unsupported operation was
Response: If this is a tracking event, no service actions
requested.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A071 B181A071
Explanation: An invalid function was requested.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
382 System reference codes (Bxxx)
B181A072 • B181A088
callouts detailed with the SRC to determine service
B181A080 B181A080
actions.
Explanation: Failed to perform a lamp test on the
panel.
B181A072 B181A072
Response: If this is a tracking event, no service actions
Explanation: The subfunction is not supported.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A081 B181A081
Explanation: Failed to perform a lamp test via power.
B181A073 B181A073
Response: If this is a tracking event, no service actions
Explanation: Failed to execute the panel function.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A082 B181A082
Explanation: Failed to perform the power function
B181A074 B181A074
that was requested.
Explanation: The subfunction is invalid.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A083 B181A083
B181A075 B181A075
Explanation: Failed to send the initiate service tool
Explanation: Failed to get the minimum and command to the hypervisor.
maximum subfunction values for the power function.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A084 B181A084
B181A076 B181A076
Explanation: Failed to start a platform dump.
Explanation: The function that was requested has no
Response: If this is a tracking event, no service actions
subfunction capability.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A088 B181A088
Explanation: Failed to execute a service processor
B181A077 B181A077
dump.
Explanation: Failed to get the minimum and
Response: If this is a tracking event, no service actions
maximum subfunction values when trying to increment
are required. Otherwise, use the FRU and procedure
the function number on the control panel .
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 383
B181A089 • B181A094
B181A089 B181A089 B181A08F B181A08F
Explanation: Failed to get the dump firmware content. Explanation: The value of the dump hardware content
that was received is not valid.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A08A B181A08A
B181A090 B181A090
Explanation: Failed to get the dump hardware
content. Explanation: Failed to set the dump firmware content
to the requested value.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A08B B181A08B
B181A091 B181A091
Explanation: Failed to find out if dump is enabled or
not. Explanation: The value of the dump firmware content
that was received is not valid.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A08C B181A08C
B181A092 B181A092
Explanation: Failed to set the dump collection policy
to the requested value. Explanation: Failed to get the number of SRC entries
for the system status SRC trace function.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A08D B181A08D
B181A093 B181A093
Explanation: The value of the dump collection policy
that was received is not valid. Explanation: Failed to get the number of SRC entries
for the diagnostic status SRC trace function.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A08E B181A08E
B181A094 B181A094
Explanation: Failed to set the dump hardware content
to the requested value. Explanation: Failed to get the system trace SRC that
was requested.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
384 System reference codes (Bxxx)
B181A095 • B181A0A1
B181A095 B181A095 B181A09C B181A09C
Explanation: Failed to create the system trace object, Explanation: Failed to get the HMC information.
or there were no entries for system trace.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A09D B181A09D
B181A096 B181A096
Explanation: Failed to get the IP address for the
Explanation: Failed to initiate the IPL that was requested Ethernet port.
requested.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A09E B181A09E
B181A098 B181A098
Explanation: Failed to get the location code for the
Explanation: Failed to send the power on IPL request. requested Ethernet port.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A099 B181A099 B181A09F B181A09F
Explanation: Failed to send the power off IPL request. Explanation: Failed to get the installed resource IDs
for the HMC connectors.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A09A B181A09A
B181A0A0 B181A0A0
Explanation: Failed to send a reboot request to the
service processor. Explanation: Failed to get the maximum number of
resource IDs for the HMC connectors.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A09B B181A09B
B181A0A1 B181A0A1
Explanation: The current and next state of the system
will not allow a reboot of the service processor. Explanation: This SRC indicates that the panel
component is done with the input function.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 385
B181A0A2 • B181A0B5
B181A0A2 B181A0A2 B181A0B0 B181A0B0
Explanation: Invalid function number. Explanation: Failed to deactivate the panel function.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A0A3 B181A0A3 B181A0B1 B181A0B1
Explanation: The function requested is disabled. Explanation: The secondary service processor cannot
activate a panel.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A0A4 B181A0A4
B181A0B2 B181A0B2
Explanation: The function range is disabled.
Explanation: Failed to set the SRC displays for the
Response: If this is a tracking event, no service actions
panel.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A0A5 B181A0A5
Explanation: Failed to determine if a concurrent
B181A0B3 B181A0B3
maintenance operation is in progress.
Explanation: Failed to modify the panel display when
Response: If this is a tracking event, no service actions
the increment button was pushed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A0A6 B181A0A6
Explanation: An invalid sub-function was received.
B181A0B4 B181A0B4
Response: If this is a tracking event, no service actions
Explanation: Failed to send display data to the panel.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A0A8 B181A0A8
Explanation: Failed to build the display for the panel.
B181A0B5 B181A0B5
Response: If this is a tracking event, no service actions
Explanation: Failed to send the SRC display data to
are required. Otherwise, use the FRU and procedure
the panel.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A0A9 B181A0A9
actions.
Explanation: No sibling service processor was found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
386 System reference codes (Bxxx)
B181A0B6 • B181A0D0
B181A0B6 B181A0B6 B181A0BC B181A0BC
Explanation: Failed to create the worker thread. Explanation: Failed to subscribe to the event manager.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A0B7 B181A0B7 B181A0BD B181A0BD
Explanation: Failed to increase the work force when it Explanation: Failed to receive an event from the event
was determined it was needed. manager.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A0B8 B181A0B8 B181A0BE B181A0BE
Explanation: No panel is active. Explanation: Failed to create the event monitor thread.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A0B9 B181A0B9 B181A0C0 B181A0C0
Explanation: Failed to push a work message onto an Explanation: Function 26 was done before function 25
existing queue. was executed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A0BA B181A0BA B181A0C1 B181A0C1
Explanation: Failed to take appropriate action for the Explanation: Failed to get the current power state.
event that was received.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A0C2 B181A0C2
B181A0BB B181A0BB
Explanation: Failed to get the current service
Explanation: An event was received that is not processor dump enablement state.
supported by the panel.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A0D0 B181A0D0
Explanation: Failed to enable the scroll lock when
trying to increment the panel.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 387
B181A0D1 • B181A0E1
callouts detailed with the SRC to determine service
B181A0D7 B181A0D7
actions.
Explanation: Failed to set the time-out for the timer.
B181A0D1 B181A0D1 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to create the timer for the scroll
callouts detailed with the SRC to determine service
lock button.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A0D8 B181A0D8
callouts detailed with the SRC to determine service
actions. Explanation: Failed to delete the timer.
Response: If this is a tracking event, no service actions
B181A0D2 B181A0D2 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Failed to set the time-out for the scroll
actions.
lock timer.
Response: If this is a tracking event, no service actions
B181A0D9 B181A0D9
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to block client process
actions. synchronization.
Response: If this is a tracking event, no service actions
B181A0D3 B181A0D3 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Failed to start the power off timer.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A0DA B181A0DA
callouts detailed with the SRC to determine service
actions. Explanation: Failed to write to a panel.
Response: If this is a tracking event, no service actions
B181A0D4 B181A0D4 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Failed to take action after the power off
actions.
timer expired.
Response: If this is a tracking event, no service actions
B181A0DB B181A0DB
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to write to the registry.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A0D5 B181A0D5 callouts detailed with the SRC to determine service
actions.
Explanation: Failed to take the proper action after the
power off timer expired.
B181A0E0 B181A0E0
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Failed to change the power LED to a
callouts detailed with the SRC to determine service new state.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A0D6 B181A0D6 callouts detailed with the SRC to determine service
actions.
Explanation: Failed to create a timer.
Response: If this is a tracking event, no service actions
B181A0E1 B181A0E1
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The button action that was received is
actions. not valid.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
388 System reference codes (Bxxx)
B181A0F0 • B181A0FB
callouts detailed with the SRC to determine service
B181A0F6 B181A0F6
actions.
Explanation: Failed to create the panel attention
monitor thread.
B181A0F0 B181A0F0
Response: If this is a tracking event, no service actions
Explanation: Failed to allocate memory.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A0F7 B181A0F7
Explanation: Failed to set up the panel when
B181A0F1 B181A0F1
activating the requested panel.
Explanation: Failed to set up the decrement button on
Response: If this is a tracking event, no service actions
the control (operator) panel.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A0F8 B181A0F8
Explanation: Failed to get the number of possible
B181A0F2 B181A0F2
panels in the system.
Explanation: Failed to create a timer for the decrement
Response: If this is a tracking event, no service actions
button on the control (operator) panel.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A0F9 B181A0F9
Explanation: A control (operator) panel is already
B181A0F3 B181A0F3
active in the system.
Explanation: Failed to conduct the decrement action
Response: If this is a tracking event, no service actions
for the panel.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A0FA B181A0FA
Explanation: Another concurrent maintenance
B181A0F4 B181A0F4
operation is already in progress.
Explanation: Failed to perform the increment action
Response: If this is a tracking event, no service actions
for the panel.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A0FB B181A0FB
Explanation: The role of the service processor will not
B181A0F5 B181A0F5
allow the activation of the requested panel.
Explanation: Failed to read the panel function that
Response: If this is a tracking event, no service actions
was received.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 389
B181A0FC • B181A20A
callouts detailed with the SRC to determine service
B181A0FC B181A0FC
actions.
Explanation: More physical control (operator) panels
are in the system than is allowed. This is an invalid
B181A205 B181A205
configuration.
Explanation: The function that was requested is not
Response: If this is a tracking event, no service actions
supported.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A0FD B181A0FD
Explanation: The control (operator) panel is not
B181A206 B181A206
present.
Explanation: Failed to request IPL for the system.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A0FE B181A0FE
B181A207 B181A207
Explanation: An invalid resource ID was found.
Explanation: The panel lamp test failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A0FF B181A0FF
B181A208 B181A208
Explanation: No active panel was found.
Explanation: Failed to read the registry.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A201 B181A201
B181A209 B181A209
Explanation: An invalid command was received.
Explanation: Failed to write to the registry.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A202 B181A202
B181A20A B181A20A
Explanation: Invalid data was received.
Explanation: The operation that was requested cannot
Response: If this is a tracking event, no service actions
be performed on the secondary service processor.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A204 B181A204
Explanation: Unknown caller.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
390 System reference codes (Bxxx)
B181A20B • B181A401
callouts detailed with the SRC to determine service
B181A20B B181A20B
actions.
Explanation: An error was returned from the state
manager function.
B181A215 B181A215
Response: If this is a tracking event, no service actions
Explanation: The function that was requested is
are required. Otherwise, use the FRU and procedure
disabled.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A20C B181A20C
actions.
Explanation: An output parameter pointer is NULL.
Response: If this is a tracking event, no service actions B181A216 B181A216
are required. Otherwise, use the FRU and procedure
Explanation: Failure during a service processor dump.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A20D B181A20D
actions.
Explanation: A platform dump function call failed.
Response: If this is a tracking event, no service actions B181A217 B181A217
are required. Otherwise, use the FRU and procedure
Explanation: The requested sub-function is outside the
callouts detailed with the SRC to determine service
valid range.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A20E B181A20E
callouts detailed with the SRC to determine service
Explanation: The requested function is invalid. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A219 B181A219
callouts detailed with the SRC to determine service
Explanation: Failed to start the service processor
actions.
dump process.
Response: If this is a tracking event, no service actions
B181A20F B181A20F
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned from the mailbox callouts detailed with the SRC to determine service
function. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A236 B181A236
callouts detailed with the SRC to determine service
Explanation: The function requested is disabled or not
actions.
active.
Response: If this is a tracking event, no service actions
B181A211 B181A211
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned from the system callouts detailed with the SRC to determine service
power interface function. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A401 B181A401
callouts detailed with the SRC to determine service
Explanation: Failed to create the SVPD ML2 socket.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A214 B181A214
callouts detailed with the SRC to determine service
Explanation: The requesting owner does not own the actions.
requested function.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 391
B181A402 • B181A40E
callouts detailed with the SRC to determine service
B181A402 B181A402
actions.
Explanation: The ML2 failed to connect to a server
socket.
B181A409 B181A409
Response: If this is a tracking event, no service actions
Explanation: An error was encountered when trying
are required. Otherwise, use the FRU and procedure
read a file from persistency.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A403 B181A403
actions.
Explanation: The ML2 server failed on socket receiver.
Response: If this is a tracking event, no service actions B181A40A B181A40A
are required. Otherwise, use the FRU and procedure
Explanation: A function failed.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A404 B181A404
actions.
Explanation: There was a problem with the path to
the secondary system controller.
B181A40B B181A40B
Response: If this is a tracking event, no service actions
Explanation: An error was encountered when closing
are required. Otherwise, use the FRU and procedure
and/or unlocking the file for the given resource ID.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A405 B181A405
actions.
Explanation: The ML2 server failed on a socket send.
Response: If this is a tracking event, no service actions B181A40C B181A40C
are required. Otherwise, use the FRU and procedure
Explanation: An error was encountered trying to read
callouts detailed with the SRC to determine service
the SVPD state information file into the persistency.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A406 B181A406
callouts detailed with the SRC to determine service
Explanation: The ML2 failed to close a connection. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A40D B181A40D
callouts detailed with the SRC to determine service
Explanation: An error was found when firmware tried
actions.
to read the size of the registry key.
Response: If this is a tracking event, no service actions
B181A407 B181A407
are required. Otherwise, use the FRU and procedure
Explanation: An invalid operation was sent to an ML2 callouts detailed with the SRC to determine service
server. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A40E B181A40E
callouts detailed with the SRC to determine service
Explanation: A data mismatch, or read failure,
actions.
occurred.
Response: If this is a tracking event, no service actions
B181A408 B181A408
are required. Otherwise, use the FRU and procedure
Explanation: This function was called by the user with callouts detailed with the SRC to determine service
an invalid parameter. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
392 System reference codes (Bxxx)
B181A40F • B181A41C
B181A40F B181A40F B181A416 B181A416
Explanation: The data was not found. Explanation: A device reset occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A410 B181A410 B181A417 B181A417
Explanation: Unable to lock out all threads. Explanation: An error was encountered whne
synchronzing the file to the other service processor in
Response: If this is a tracking event, no service actions
the system.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A411 B181A411
Explanation: Unable to gain a lock on a VPD file.
B181A418 B181A418
Response: If this is a tracking event, no service actions
Explanation: Unable to locate a string in a file.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A412 B181A412
Explanation: Unable to lock the file.
B181A419 B181A419
Response: If this is a tracking event, no service actions
Explanation: An error occurred when generating the
are required. Otherwise, use the FRU and procedure
location code while trying to rebuild the RLCA table.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A413 B181A413
actions.
Explanation: Unable to unlock the threads.
Response: If this is a tracking event, no service actions B181A41A B181A41A
are required. Otherwise, use the FRU and procedure
Explanation: Failure to write to the registry.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A414 B181A414
actions.
Explanation: An error occurred when getting the
device type for the resource ID.
B181A41B B181A41B
Response: If this is a tracking event, no service actions
Explanation: A keyword error occurred.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A415 B181A415
Explanation: A device write failure occurred.
B181A41C B181A41C
Response: If this is a tracking event, no service actions
Explanation: A keyword error occurred.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 393
B181A41D • B181A428
callouts detailed with the SRC to determine service
B181A423 B181A423
actions.
Explanation: Invalid data in the module VPD file.
B181A41D B181A41D Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A failure was encountered when finding
callouts detailed with the SRC to determine service
or reading the module VPD file.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A424 B181A424
callouts detailed with the SRC to determine service
actions. Explanation: An error occurred when reading a file.
Response: If this is a tracking event, no service actions
B181A41E B181A41E are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The client failed on a socked send of
actions.
receive.
Response: If this is a tracking event, no service actions
B181A425 B181A425
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Failed to write raw VPD data into the
actions. registry.
Response: If this is a tracking event, no service actions
B181A41F B181A41F are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: This operation needs message data from
actions.
the client but there was no message data in the client
message
B181A426 B181A426
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: An error was encountered when writing
callouts detailed with the SRC to determine service NVRAM to VPD.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A420 B181A420 callouts detailed with the SRC to determine service
actions.
Explanation: An invalid state type was passed in by
the user.
B181A427 B181A427
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: There was a mismatch between the VPD
callouts detailed with the SRC to determine service data and the values in NVRAM.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A421 B181A421 callouts detailed with the SRC to determine service
actions.
Explanation: An invalid command was sent to the
ML3 server.
B181A428 B181A428
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Data read from the rlcainst table is
callouts detailed with the SRC to determine service invalid.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A422 B181A422 callouts detailed with the SRC to determine service
actions.
Explanation: The client failed to get message data
from the server when mesage data was expected.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
394 System reference codes (Bxxx)
B181A429 • B181A434
B181A429 B181A429 B181A42F B181A42F
Explanation: Firmware needs to add support for an Explanation: An error occurred when getting the field
additional resource to the given FRU type. replaceable unit (FRU) status for the resource ID in the
registry update function.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A42A B181A42A
B181A430 B181A430
Explanation: Failed to get FRU status for the given
RID in registry update function. Explanation: Invalid keyword data was input by the
user.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A42B B181A42B
B181A431 B181A431
Explanation: Failed trying to determine the resource
ID's associated with the given FRU type. Explanation: The user passed in a keyword size that is
greater than the actual keyword size in the VPD.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A42C B181A42C
B181A432 B181A432
Explanation: Failed to read the VPD and update the
registry entry for the input RID. Explanation: This system's machine ID is not
supported.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A42D B181A42D
B181A433 B181A433
Explanation: A failure occurred when reading the
Anchor (VPD) card. Explanation: A smaller number of bytes was written
to the I2C device than was expected.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A42E B181A42E
B181A434 B181A434
Explanation: Writing to the Anchor card I/O
multiplexer failed. Explanation: Failed to write to an I2C device.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 395
B181A435 • B181A441
callouts detailed with the SRC to determine service
B181A435 B181A435
actions.
Explanation: Unable to update the IN keyword in the
VRTN block.
B181A43C B181A43C
Response: If this is a tracking event, no service actions
Explanation: A function was called with an invalid
are required. Otherwise, use the FRU and procedure
parameter.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A436 B181A436
actions.
Explanation: Failed when updating one of the smart
chip blocks
B181A43D B181A43D
Response: If this is a tracking event, no service actions
Explanation: The data reference does not support
are required. Otherwise, use the FRU and procedure
keyword parsing.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A437 B181A437
actions.
Explanation: An invalid format was found.
Response: If this is a tracking event, no service actions B181A43E B181A43E
are required. Otherwise, use the FRU and procedure
Explanation: The files were not synchronized for this
callouts detailed with the SRC to determine service
request.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A438 B181A438
callouts detailed with the SRC to determine service
Explanation: A record is not found in the VPD data. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A43F B181A43F
callouts detailed with the SRC to determine service
Explanation: The two copies of the chips were
actions.
re-synchronized.
Response: If this is a tracking event, no service actions
B181A439 B181A439
are required. Otherwise, use the FRU and procedure
Explanation: An invalid length was found. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181A440 B181A440
actions.
Explanation: An attempt to read the module vital
product data (VPD) from the I2C device failed.
B181A43A B181A43A
Response: If this is a tracking event, no service actions
Explanation: Invalid offset for retrieving raw entry are required. Otherwise, use the FRU and procedure
data from the file. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181A441 B181A441
actions.
Explanation: An error occurred when setting the
mode attribute to hardware mode.
B181A43B B181A43B
Response: If this is a tracking event, no service actions
Explanation: An invalid operation was attempted. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
396 System reference codes (Bxxx)
B181A442 • B181A44F
B181A442 B181A442 B181A448 B181A448
Explanation: An error occurred when trying to Explanation: Failed to convert VPD format.
generate a location code.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A449 B181A449
B181A443 B181A443
Explanation: An error was encountered when
Explanation: An error was encountered duing VPD converting the VPD to multiple stanza format.
collection.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A44A B181A44A
B181A444 B181A444
Explanation: The BR keyword needs to be
Explanation: An error was encountered during VPD programmed.
collection.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A44B B181A44B
B181A445 B181A445
Explanation: The enclosure FC keyword needs to be
Explanation: An attempt to delete the old event queue programmed.
failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A44D B181A44D
B181A446 B181A446
Explanation: The ID keyword needs to be
Explanation: There was a failure in the firmware. programmed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A447 B181A447 B181A44F B181A44F
Explanation: Unable to find the input RID in our Explanation: The NN keyword needs to be
RLCA table. programmed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 397
B181A450 • B181A45C
B181A450 B181A450 B181A456 B181A456
Explanation: The RB keyword needs to be Explanation: The WN keyword needs to be
programmed. programmed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A451 B181A451 B181A457 B181A457
Explanation: The SG keyword needs to be Explanation: Failed to identify a RIO cable.
programmed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A458 B181A458
B181A452 B181A452
Explanation: Failed to read the I2C DP.
Explanation: The SU keyword needs to be
Response: If this is a tracking event, no service actions
programmed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A459 B181A459
Explanation: There was an error when synchronizing.
B181A453 B181A453
Response: If this is a tracking event, no service actions
Explanation: The SE keyword needs to be
are required. Otherwise, use the FRU and procedure
programmed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A45A B181A45A
actions.
Explanation: A send/receive failure occurred.
B181A454 B181A454 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The TM keyword needs to be
callouts detailed with the SRC to determine service
programmed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A45B B181A45B
callouts detailed with the SRC to determine service
actions. Explanation: No manufacturing flag was found.
Response: If this is a tracking event, no service actions
B181A455 B181A455 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The TN keyword needs to be
actions.
programmed.
Response: If this is a tracking event, no service actions
B181A45C B181A45C
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The manufacturing policy flag is not set.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
398 System reference codes (Bxxx)
B181A45D • B181A469
callouts detailed with the SRC to determine service
B181A45D B181A45D
actions.
Explanation: Updating the System p BR keyword is
not allowed.
B181A464 B181A464
Response: If this is a tracking event, no service actions
Explanation: A function call failed during vital
are required. Otherwise, use the FRU and procedure
product data (VPD) collection.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A45E B181A45E
actions.
Explanation: Updating the SSD BR keyword is not
allowed.
B181A465 B181A465
Response: If this is a tracking event, no service actions
Explanation: A function call failed during vital
are required. Otherwise, use the FRU and procedure
product data (VPD) collection.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A45F B181A45F
actions.
Explanation: Failed to open a directory.
Response: If this is a tracking event, no service actions B181A466 B181A466
are required. Otherwise, use the FRU and procedure
Explanation: Unable to lock out all threads.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A460 B181A460
actions.
Explanation: An unknown type of error occurred.
Response: If this is a tracking event, no service actions B181A467 B181A467
are required. Otherwise, use the FRU and procedure
Explanation: Unable to unlock the threads.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A461 B181A461
actions.
Explanation: An initialization operation failed.
Response: If this is a tracking event, no service actions B181A468 B181A468
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when closing a
callouts detailed with the SRC to determine service
handle.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A462 B181A462
callouts detailed with the SRC to determine service
Explanation: Failed to set a thread attribute. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A469 B181A469
callouts detailed with the SRC to determine service
Explanation: The type/model field has already been
actions.
updated once; the second update is not allowed
because the type part of the type/model data does not
B181A463 B181A463 match.
Explanation: Failed to create and initialize an attribute Response: If this is a tracking event, no service actions
object that was needed to create a thread. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 399
B181A46A • B181A475
B181A46A B181A46A B181A470 B181A470
Explanation: An update for the given keyword not Explanation: Invalid data was found in the registry.
allowed for the second time.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A471 B181A471
B181A46B B181A46B
Explanation: An untagged entry was found in the
Explanation: An error occurred when trying to read a resource ID tree.
pin.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A472 B181A472
B181A46C B181A46C
Explanation: Failed to read an I2C device.
Explanation: An error was encountered when trying
Response: If this is a tracking event, no service actions
to find the VSYS record from the sytem VPD.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A473 B181A473
Explanation: An error occurred when setting the bus
B181A46D B181A46D
speed attribute for reading or writing an I2C device.
Explanation: No valid service processor VPD was
Response: If this is a tracking event, no service actions
found on this system.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A474 B181A474
Explanation: Failed to read the system serial number
B181A46E B181A46E
on NVRAM, or invalid keyword length.
Explanation: An error occurred when collecting the
Response: If this is a tracking event, no service actions
system VPD to rebuild the VPD data.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181A475 B181A475
Explanation: There was an error when synchronizing
B181A46F B181A46F
files.
Explanation: Failed to write to a registry.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
400 System reference codes (Bxxx)
B181A476 • B181A482
callouts detailed with the SRC to determine service
B181A476 B181A476
actions.
Explanation: An error occurred when setting the
DIMM change flag.
B181A47D B181A47D
Response: If this is a tracking event, no service actions
Explanation: An error occurred when trying to
are required. Otherwise, use the FRU and procedure
synchronize the service processors (or system
callouts detailed with the SRC to determine service
controllers).
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A477 B181A477
callouts detailed with the SRC to determine service
Explanation: An error occurred when setting the actions.
speed attribute before reading a resource ID.
Response: If this is a tracking event, no service actions B181A47E B181A47E
are required. Otherwise, use the FRU and procedure
Explanation: The system VPD was not collected.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A478 B181A478
actions.
Explanation: An invalid device type was received.
Response: If this is a tracking event, no service actions B181A47F B181A47F
are required. Otherwise, use the FRU and procedure
Explanation: Failed to delete an entry from a table.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A479 B181A479
actions.
Explanation: The VPD is being recollected.
Response: If this is a tracking event, no service actions B181A480 B181A480
are required. Otherwise, use the FRU and procedure
Explanation: The processing of a table failed.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A47A B181A47A
actions.
Explanation: A synchronization error occurred.
Response: If this is a tracking event, no service actions B181A481 B181A481
are required. Otherwise, use the FRU and procedure
Explanation: Failed to load a table.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A47B B181A47B
actions.
Explanation: All of the VPD was not collected.
Response: If this is a tracking event, no service actions B181A482 B181A482
are required. Otherwise, use the FRU and procedure
Explanation: A problem occurred when collecting the
callouts detailed with the SRC to determine service
system VPD.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A47C B181A47C
callouts detailed with the SRC to determine service
Explanation: An error occurred when converting a actions.
string.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 401
B181A483 • B181A48F
B181A483 B181A483 B181A48A B181A48A
Explanation: Unable to create a FRU callout. Explanation: Failure during FRUM waiting on gpio
devices becoming present.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A484 B181A484
B181A48B B181A48B
Explanation: Verification of the path from the service
processor to the Anchor card cannot be done because Explanation: Failure when starting the background
the sibling service processor does not exist. svpd server process.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A486 B181A486 B181A48C B181A48C
Explanation: A recalculation failure occurred. Explanation: The svpd server process encountered a
problem and has terminated.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A487 B181A487
B181A48D B181A48D
Explanation: Failure in FRUM call to set up iomux for
the anchor card. Explanation: Failed to obtain the machine ID. It is
possible that the system firmware does not support this
Response: If this is a tracking event, no service actions
model.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A488 B181A488
Explanation: Failure during FRUM waiting on anchor
B181A48E B181A48E
card device.
Explanation: Vital product data (VPD) validation was
Response: If this is a tracking event, no service actions
successful during a keyword update
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A489 B181A489
Explanation: Failure during FRUM waiting on
B181A48F B181A48F
configuration being complete.
Explanation: Unable to find the IM keyword in the
Response: If this is a tracking event, no service actions
VPD record in this system's Anchor card. Reprogram
are required. Otherwise, use the FRU and procedure
the Anchor card with the correct VPD.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
402 System reference codes (Bxxx)
B181A490 • B181A49B
B181A490 B181A490 B181A496 B181A496
Explanation: The VPD was guarded. Explanation: An error occurred when trying to
dynamically rebuild the module VPD table.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A491 B181A491
B181A497 B181A497
Explanation: An untagged entry was found in the RID
tree. Explanation: An error occurred when trying to
dynamically rebuild the instance table.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A492 B181A492
B181A498 B181A498
Explanation: VPD is not collectible. Recollection of the
VPD will be attempted. Explanation: An error occurred when setting the vital
product data (VPD) state after a code or table check
Response: If this is a tracking event, no service actions
failure on the secondary service processor (or system
are required. Otherwise, use the FRU and procedure
controller).
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A493 B181A493
actions.
Explanation: A listening failure occurred.
Response: If this is a tracking event, no service actions B181A499 B181A499
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when trying to find a
callouts detailed with the SRC to determine service
record during system vital product data (VPD)
actions.
collection.
Response: If this is a tracking event, no service actions
B181A494 B181A494
are required. Otherwise, use the FRU and procedure
Explanation: A process message was received. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181A49A B181A49A
actions.
Explanation: Too many devices were in the list.
Response: If this is a tracking event, no service actions
B181A495 B181A495
are required. Otherwise, use the FRU and procedure
Explanation: A synchronization between the primary callouts detailed with the SRC to determine service
and secondary service processors was requested. This actions.
operation timed out before it was complete.
Response: If this is a tracking event, no service actions B181A49B B181A49B
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned by lstat() even
callouts detailed with the SRC to determine service
though the directory entry should have been valid.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 403
B181A49C • B181A4A8
B181A49C B181A49C B181A4A2 B181A4A2
Explanation: Two I2C hub devices are in the list Explanation: There was an error when trying to clear
consecutively. the data synchonization gzip file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A49D B181A49D B181A4A4 B181A4A4
Explanation: No I2C devices were present in the vital Explanation: The SCED read for the backup path
product data (VPD) table device string that was failed.
received.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A4A5 B181A4A5
B181A49E B181A49E
Explanation: There was an error in converting the
Explanation: An error occurred when trying to string for verification of the secondary service
dynamically rebuild the HVAT table. processor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A49F B181A49F B181A4A6 B181A4A6
Explanation: An RLCA table of size 0 was read from Explanation: There was an error in converting the
P1. string for verification of the secondary service
processor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A4A0 B181A4A0
B181A4A7 B181A4A7
Explanation: An RLCA table of size 0 was read from
P1. Explanation: Unable to find the IM keyword in the
VSBP VPD record in this system's anchor card. The
Response: If this is a tracking event, no service actions
anchor card must be programmed with VPD which
are required. Otherwise, use the FRU and procedure
contains this keyword.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A4A1 B181A4A1
actions.
Explanation: An RLCA table of size 0 was read from
P1.
B181A4A8 B181A4A8
Response: If this is a tracking event, no service actions
Explanation: There was an error when synchronizing
are required. Otherwise, use the FRU and procedure
with the server from the SVPD client side.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
404 System reference codes (Bxxx)
B181A4AA • B181A4BA
B181A4AA B181A4AA B181A4B0 B181A4B0
Explanation: Unable to find the parent CCIN of the Explanation: Failed to get the node ID from the device
resource ID. address.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A4AB B181A4AB B181A4B1 B181A4B1
Explanation: Unable to find a part number for a Explanation: Failed to get the device string from the
resource ID. device address.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A4AC B181A4AC B181A4B2 B181A4B2
Explanation: Unable to find a serial number for a Explanation: Failed to get the device string from the
resource ID. device address.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A4AD B181A4AD B181A4B7 B181A4B7
Explanation: Too many entries in this file; it could be Explanation: An error occurred when reading the file
the wrong file. in "util generate file name".
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A4AE B181A4AE B181A4B8 B181A4B8
Explanation: There was an invalid operation on the Explanation: There was an error returned from tmgt
VPD formatted for a blade system. when called from SVPD.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A4AF B181A4AF B181A4BA B181A4BA
Explanation: Configuration on the I2C DP failed. Explanation: The anchor card is tagged for concurrent
maintenance.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 405
B181A4BB • B181A4C9
callouts detailed with the SRC to determine service
B181A4BB B181A4BB
actions.
Explanation: Unable to obtain the anchor chip
resource IDs.
B181A4C4 B181A4C4
Response: If this is a tracking event, no service actions
Explanation: There was an error when setting the IPL
are required. Otherwise, use the FRU and procedure
speed to fast.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181A4BC B181A4BC
actions.
Explanation: Failed to read the file from RO/svpd.
Response: If this is a tracking event, no service actions B181A4C5 B181A4C5
are required. Otherwise, use the FRU and procedure
Explanation: There was an MDIA error when setting
callouts detailed with the SRC to determine service
the DIMM change flag.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A4BD B181A4BD
callouts detailed with the SRC to determine service
Explanation: The processing of the PD table failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A4C6 B181A4C6
callouts detailed with the SRC to determine service
Explanation: An error occurred when getting the RID
actions.
array while trying to rebuild the RLCA table.
Response: If this is a tracking event, no service actions
B181A4BE B181A4BE
are required. Otherwise, use the FRU and procedure
Explanation: "Process and store" on the LED table callouts detailed with the SRC to determine service
failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181A4C7 B181A4C7
callouts detailed with the SRC to determine service
Explanation: Failed to read the VPD collection status
actions.
flag from the RLCA table.
Response: If this is a tracking event, no service actions
B181A4C1 B181A4C1
are required. Otherwise, use the FRU and procedure
Explanation: Failed to load tables to p1/svpd. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181A4C8 B181A4C8
actions.
Explanation: The VPD data for the resource ID was
not found in p1.
B181A4C2 B181A4C2
Response: If this is a tracking event, no service actions
Explanation: RLCA INIT failed. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B181A4C9 B181A4C9
Explanation: The serial number and feature number
B181A4C3 B181A4C3 data in p1 are zero.
Explanation: There was an error when setting the IPL Response: If this is a tracking event, no service actions
speed to slow. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
406 System reference codes (Bxxx)
B181A4CA • B181A4D6
B181A4CA B181A4CA B181A4D1 B181A4D1
Explanation: The VPD read status was set to false in Explanation: Failed to add a file to the global
the RLCA; there was no VPD data in p1. synchronization list so that it can be scheduled for
deletion on the secondary service processor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A4CB B181A4CB
B181A4D2 B181A4D2
Explanation: The VPD data for the resource ID was
not found in p1. Explanation: Failed to add a file to the global
synchronization list so that it can be scheduled for
Response: If this is a tracking event, no service actions
synchronization with the secondary service processor.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A4CC B181A4CC
Explanation: A failure occurred during the renaming
B181A4D3 B181A4D3
of the module VPD file.
Explanation: The global HVAT table is null, so writing
Response: If this is a tracking event, no service actions
the table to p1 is not possible.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A4CD B181A4CD
Explanation: An error occured when trying to clear
B181A4D4 B181A4D4
the data synchronization gzip file.
Explanation: An error occurred when loading the
Response: If this is a tracking event, no service actions
table from p1.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181A4CF B181A4CF
Explanation: A failure occurred when reading the FN
B181A4D5 B181A4D5
value for the RID.
Explanation: The primary device address is null.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A4D0 B181A4D0
B181A4D6 B181A4D6
Explanation: A failure occurred when reading the
serial number value for the RID. Explanation: Unable to find the table in p1.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 407
B181A4D7 • B181A702
B181A4D7 B181A4D7 B181A4E4 B181A4E4
Explanation: The p1 table version does not match the Explanation: Firmware validation was successful.
NFS or RO/svpd.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A4E5 B181A4E5
B181A4D8 B181A4D8
Explanation: Firmware validation before a firmware
Explanation: The redundant device address value is installation was not successful.
null.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181A4E6 B181A4E6
B181A4D9 B181A4D9
Explanation: Firmware validation after a firmware
Explanation: Failed to rebuild VPD tables. installation was not successful.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A4DA B181A4DA B181A4FF B181A4FF
Explanation: There was a mismatch between the Explanation: An invalid command was encountered.
machine ID on the primary Anchor card and the
Response: If this is a tracking event, no service actions
secondary Anchor card. The secondary Anchor card
are required. Otherwise, use the FRU and procedure
will be guarded out and the machine ID on the
callouts detailed with the SRC to determine service
primary Anchor card will be used.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A701 B181A701
callouts detailed with the SRC to determine service
actions. Explanation: Request to get data for a service LED
failed due to a software error.
B181A4DB B181A4DB Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to delete an entry from the RLCA
callouts detailed with the SRC to determine service
table or its copy.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181A702 B181A702
callouts detailed with the SRC to determine service
actions. Explanation: Request to get data for a service LED
failed due to a software error.
B181A4E3 B181A4E3 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The system VPD was not collected.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
408 System reference codes (Bxxx)
B181A704 • B181A71E
B181A704 B181A704 B181A711 B181A711
Explanation: Request to obtain data for a service LED Explanation: Request to turn on, turn off, or blink a
failed due to a software error. service LED failed due to a software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A705 B181A705 B181A71A B181A71A
Explanation: Request to get data for a service LED Explanation: Request to turn on, turn off, or blink a
failed due to a software error. service LED failed due to a software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A707 B181A707 B181A71B B181A71B
Explanation: Request to turn on, turn off, or blink a Explanation: Request to turn on, turn off, or blink a
service LED failed due to a software error. service LED failed..
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A708 B181A708 B181A71C B181A71C
Explanation: Request to turn on, turn off, or blink a Explanation: Request to turn on, turn off, or blink a
service LED failed. service LED failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A70D B181A70D B181A71D B181A71D
Explanation: Request to turn on, turn off, or blink a Explanation: Request to turn on, turn off, or blink a
service LED failed due to a software error. service LED failed due to a device driver problem.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A710 B181A710 B181A71E B181A71E
Explanation: Error occured while locating an Explanation: Internal firmware error.
enclosure LED for the system.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 409
B181A71F • B181A72B
B181A71F B181A71F B181A726 B181A726
Explanation: Request to turn on, turn off, or blink a Explanation: An error was returned from a function
service LED failed. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A720 B181A720 B181A727 B181A727
Explanation: Request to turn on, turn off, or blink a Explanation: A call was made to get LED access data
service LED failed. based on the RID, but the call to malloc failed to
allocate memory.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A722 B181A722
B181A728 B181A728
Explanation: Request to turn on, turn off, or blink a
service LED failed. Explanation: A call was made to drive an LED to a
specific state, but an error was returned.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A723 B181A723
B181A729 B181A729
Explanation: Request to turn on, turn off, or blink a
service LED failed. Explanation: A call was made to drive an LED to a
specific state, but an error was returned.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A724 B181A724
B181A72A B181A72A
Explanation: Request to turn on, turn off, or blink a
service LED failed. Explanation: A call was made to drive an LED to a
specific state, but an error was returned.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181A725 B181A725
B181A72B B181A72B
Explanation: An error occured during first failure data
collection. Explanation: An error was returned from a
constructor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
410 System reference codes (Bxxx)
B181A802 • B181B011
B181A802 B181A802 B181B001 B181B001
Explanation: A failure occurred when retrieving an Explanation: A chip was in an invalid position on the
object reference. chain.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181A805 B181A805 B181B002 B181B002
Explanation: A failure occurred during code Explanation: No chips were in the chain.
execution.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B003 B181B003
B181A80B B181A80B
Explanation: The commands that were added
Explanation: A failure occurred during code exceeded the chain command size.
finalization.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B005 B181B005
B181A80E B181A80E
Explanation: A chip was not found in the chain.
Explanation: A failure occurred during code
Response: If this is a tracking event, no service actions
preparation.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B006 B181B006
Explanation: The ring buffer size was not valid.
B181A80F B181A80F
Response: If this is a tracking event, no service actions
Explanation: An internal firmware database error
are required. Otherwise, use the FRU and procedure
occurred in the service processor firmware.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B00B B181B00B
actions.
Explanation: Failure to release the lock.
B181A81A B181A81A Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: This is an informational SRC; no service
callouts detailed with the SRC to determine service
actions are required. It indicates that an internal
actions.
command was not successfully executed the first time
and had to be retried.
B181B011 B181B011
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Failure when getting the facility.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 411
B181B012 • B181B031
callouts detailed with the SRC to determine service
B181B012 B181B012
actions.
Explanation: An invalid device number was found.
Response: If this is a tracking event, no service actions B181B029 B181B029
are required. Otherwise, use the FRU and procedure
Explanation: An invalid use was made of the JTAG
callouts detailed with the SRC to determine service
interface.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B019 B181B019
callouts detailed with the SRC to determine service
Explanation: An abort was signalled. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181B02D B181B02D
callouts detailed with the SRC to determine service
Explanation: An unmatched cyclic redundancy check
actions.
(CRC) was found.
Response: If this is a tracking event, no service actions
B181B01B B181B01B
are required. Otherwise, use the FRU and procedure
Explanation: Failed to release a lock. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B02E B181B02E
actions.
Explanation: A chip detected cyclic redundancy check
(CRC) miscompares on scan-in.
B181B01C B181B01C
Response: If this is a tracking event, no service actions
Explanation: An attempt was made to release a lock are required. Otherwise, use the FRU and procedure
that was not held. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B02F B181B02F
actions.
Explanation: SCOM attentions were detected.
Response: If this is a tracking event, no service actions
B181B026 B181B026
are required. Otherwise, use the FRU and procedure
Explanation: An invalid command ID was found. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B030 B181B030
actions.
Explanation: Bad parity or an invalid command was
found.
B181B027 B181B027
Response: If this is a tracking event, no service actions
Explanation: The GetSCOM operation never are required. Otherwise, use the FRU and procedure
completed. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B031 B181B031
actions.
Explanation: An invalid flush operation code was
found.
B181B028 B181B028
Response: If this is a tracking event, no service actions
Explanation: An invalid use was made of the JTAG are required. Otherwise, use the FRU and procedure
interface. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
412 System reference codes (Bxxx)
B181B032 • B181B104
B181B032 B181B032 B181B03F B181B03F
Explanation: The last bits of the chip status command Explanation: Unable to find a processor node.
were not the expected value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B041 B181B041
B181B033 B181B033
Explanation: The chip ID that was scanned did not
Explanation: An invalid ring selection was found. match the chip ID that was restored.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B034 B181B034 B181B101 B181B101
Explanation: Failed to turn on a chip clock. Explanation: The domain pointer is of an unknown
type.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B035 B181B035
B181B102 B181B102
Explanation: Unable to stop the specified chip clock.
Explanation: An invalid operation was specified by
Response: If this is a tracking event, no service actions
the function caller.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B036 B181B036
Explanation: An invalid function call was made.
B181B103 B181B103
Response: If this is a tracking event, no service actions
Explanation: A node without cards of a certain type
are required. Otherwise, use the FRU and procedure
should not be on top of a node with those cards.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B037 B181B037
actions.
Explanation: An invalid function call was made.
Response: If this is a tracking event, no service actions B181B104 B181B104
are required. Otherwise, use the FRU and procedure
Explanation: The processor core functional unit in a
callouts detailed with the SRC to determine service
nonfunctional state.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B03E B181B03E
callouts detailed with the SRC to determine service
Explanation: A prohibited command was found actions.
during an IPL step.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 413
B181B105 • B181B111
B181B105 B181B105 B181B10C B181B10C
Explanation: The processor core is not functioning, or Explanation: The resources used to complete a
it cannot be detected. memory path are not functional.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B106 B181B106 B181B10D B181B10D
Explanation: There were no functional nodes found in Explanation: The resources used to complete a
the system. If this is a multi-processor-drawer system, memory path are not detectable .
the first node is not functioning.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B10E B181B10E
B181B107 B181B107
Explanation: The time-of-day clock is not functional,
Explanation: The processor clock is not active, or there or there is no active clock.
is no active clock.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B10F B181B10F
B181B108 B181B108
Explanation: The time-of-day clock is not functioning,
Explanation: The processor clock is not functioning, or or it cannot be detected, or there is no active clock.
it cannot be detected, or there is no active clock.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B110 B181B110
B181B109 B181B109
Explanation: The P5IOC2 was not functional.
Explanation: The object wasn't initialized.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B111 B181B111
B181B10B B181B10B
Explanation: The P5IOC2 is not functioning, or it
Explanation: No functional direct memory access cannot be detected.
(DMA) paths were found. The system cannot boot.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
414 System reference codes (Bxxx)
B181B112 • B181B12B
B181B112 B181B112 B181B123 B181B123
Explanation: Unsupported cards (designated by a Explanation: An error occurred with the hardware
CCIN of FFFF) were detected in the system. These access monitor.
cards have been deconfigured and are unusable system
Response: If this is a tracking event, no service actions
resources.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B126 B181B126
Explanation: The frequency for this clock card is
B181B113 B181B113
invalid.
Explanation: There was an error when using the rule
Response: If this is a tracking event, no service actions
facade classes.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B128 B181B128
Explanation: An invalid VPD port number was
B181B11E B181B11E
detected.
Explanation: A FRU was not found for this object.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B129 B181B129
B181B11F B181B11F
Explanation: The resource ID is invalid.
Explanation: A FRU or MRU was not found for this
Response: If this is a tracking event, no service actions
object.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B12A B181B12A
Explanation: An MCM has an invalid plug count.
B181B120 B181B120
Response: If this is a tracking event, no service actions
Explanation: An invalid value was passed into the
are required. Otherwise, use the FRU and procedure
function.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B12B B181B12B
actions.
Explanation: There is not enough hardware in the
system to boot.
B181B121 B181B121
Response: If this is a tracking event, no service actions
Explanation: The clock interface instance is null.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 415
B181B12C • B181B150
B181B12C B181B12C B181B142 B181B142
Explanation: An error occurred when creating a group Explanation: A light strip has been plugged in
object. incorrectly.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B12D B181B12D B181B143 B181B143
Explanation: An invalid unit id was detected. Explanation: A card is plugged into an invalid slot. If
this error occurred during a concurrent maintenance
Response: If this is a tracking event, no service actions
operation, it is possible that the system does not
are required. Otherwise, use the FRU and procedure
support adding this card concurrently.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B139 B181B139
actions.
Explanation: There is no mainstore memory
initialized; the size is zero.
B181B144 B181B144
Response: If this is a tracking event, no service actions
Explanation: An error occurred when using spif WBC
are required. Otherwise, use the FRU and procedure
commands.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B13B B181B13B
actions.
Explanation: A hole was detected in the plugging of
the nodes.
B181B145 B181B145
Response: If this is a tracking event, no service actions
Explanation: A chip is missing.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B13F B181B13F
Explanation: The SMP cables are plugged incorrectly,
B181B146 B181B146
or the SMP cables are the wrong type.
Explanation: The RTBL chip override key was set.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B140 B181B140
B181B150 B181B150
Explanation: The amount of memory that is
configured has changed since the last system boot, so Explanation: There was an error when attempting to
main storage cannot be preserved. create a group, and the function returned a null group
pointer.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
416 System reference codes (Bxxx)
B181B151 • B181B16B
B181B151 B181B151 B181B165 B181B165
Explanation: Zero chips were found on the new or Explanation: Memory cannot be preserved due to
replacement card. clock stop sequence.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B153 B181B153 B181B166 B181B166
Explanation: There was an error when attempting to Explanation: Error in performing a sendCmd
create a system domain, and a null pointer was operation.
returned.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B167 B181B167
B181B158 B181B158
Explanation: A processor chip was found to have zero
Explanation: The creation of a cage pointer failed. cores active, which is an invalid configuration for the
hypervisor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B15E B181B15E
B181B169 B181B169
Explanation: There was a problem in calculating the
clock multiplier and divider. Explanation: The SMP cables are plugged incorrectly.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B15F B181B15F B181B16A B181B16A
Explanation: An error was returned from Explanation: The cable data doesn't match a known
ecmdDataBuffer. value. Verify that the SMP cables are plugged in
securely.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B163 B181B163
B181B16B B181B16B
Explanation: An attention or checkstop was detected
on the chip. Explanation: An attempt was made to access an
invalid processor unit ID.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 417
B181B16C • B181B178
B181B16C B181B16C B181B173 B181B173
Explanation: A concurrent maintenance quiesce Explanation: An attempt was made to access a
operation failed. processor chip unit with an invalid ID.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B16D B181B16D B181B174 B181B174
Explanation: A concurrent maintenance switch Explanation: No functioning service processor (or
command failed. system controller) was found. The system boot must be
aborted.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B16E B181B16E
B181B175 B181B175
Explanation: A concurrent maintenance node hot add
operation failed. Explanation: The node configuration is invalid.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B170 B181B170 B181B176 B181B176
Explanation: The SMP cables, or the processor cards, Explanation: A system was found without a functional
are not plugged in correctly. TPMD card.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B171 B181B171 B181B177 B181B177
Explanation: An attempt was made to perform a Explanation: A functional TPMD card was not found
hardware operation without a valid hardware operation in a server that requires one.
lock.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B178 B181B178
B181B172 B181B172
Explanation: An abort signal was received.
Explanation: An invalid card record was found in
Response: If this is a tracking event, no service actions
persistent memory.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
418 System reference codes (Bxxx)
B181B17B • B181B2C4
B181B17B B181B17B B181B206 B181B206
Explanation: Not all DIMMs in the current power Explanation: Memory is not preserved.
domain have the same minimum voltage. DIMMs that
Response: If this is a tracking event, no service actions
do not have the lowest minimum voltage will be
are required. Otherwise, use the FRU and procedure
deconfigured.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B20B B181B20B
actions.
Explanation: An attempt was made to transmit data
to the LED lightstrip controller. The transmission failed
B181B17C B181B17C
due to an ADAL error.
Explanation: The DIMMs with the CCIN listed do not
Response: If this is a tracking event, no service actions
have a valid voltage in the DIMM definition file. Either
are required. Otherwise, use the FRU and procedure
the CCIN is corrupt or invalid, or not supported.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B2C1 B181B2C1
actions.
Explanation: Internal software error: invalid object
type passed to function
B181B19B B181B19B
Response: If this is a tracking event, no service actions
Explanation: The error analyzer detected a mailbox
are required. Otherwise, use the FRU and procedure
ADAL error.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B2C2 B181B2C2
actions.
Explanation: Internal software error: the hardware is
not in a valid state for the requested operation
B181B201 B181B201
Response: If this is a tracking event, no service actions
Explanation: Dynamic recalibration is not valid on
are required. Otherwise, use the FRU and procedure
this elastic interface bus.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B2C3 B181B2C3
actions.
Explanation: Internal software error: data buffer used
incorrectly
B181B204 B181B204
Response: If this is a tracking event, no service actions
Explanation: An unknown system type was found.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B2C4 B181B2C4
Explanation: Internal software error: the firmware is
B181B205 B181B205
in an invalid state for the requested operation
Explanation: The SMGR_NON_MS_RIPL recovery IPL
Response: If this is a tracking event, no service actions
is hung.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 419
B181B2C5 • B181B304
B181B2C5 B181B2C5 B181B2E7 B181B2E7
Explanation: One or more bus alignment errors Explanation: Chips that are not supported were
occurred; look for prior error log entries with with the found.
format B1xxB2DF and take the recommended actions
Response: If this is a tracking event, no service actions
for those entries.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B2EA B181B2EA
Explanation: An erepair was successful.
B181B2C6 B181B2C6
Response: If this is a tracking event, no service actions
Explanation: Internal software error: test routine failed
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B301 B181B301
Explanation: The firmware encountered an internal
B181B2CC B181B2CC
problem.
Explanation: Internal software error: invalid
Response: If this is a tracking event, no service actions
parameter passed into a function
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B302 B181B302
Explanation: The firmare encountered an internal
B181B2DC B181B2DC
problem.
Explanation: System attention line became active, but
Response: If this is a tracking event, no service actions
no chips appear to be activating it
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B303 B181B303
Explanation: The firmware encountered an internal
B181B2E3 B181B2E3
problem.
Explanation: Unable to find the other side of the
Response: If this is a tracking event, no service actions
interface.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B304 B181B304
Explanation: The firmware encountered an internal
B181B2E4 B181B2E4
error.
Explanation: Internal software error: an operation was
Response: If this is a tracking event, no service actions
attempted on deconfigured hardware
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
420 System reference codes (Bxxx)
B181B305 • B181B310
B181B305 B181B305 B181B30B B181B30B
Explanation: A chip-checker can only contain a Explanation: The firmware encountered a internal
pre-defined set of clock states, and the clock state of problem.
this chip-checker is not in this set.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B30C B181B30C
B181B306 B181B306
Explanation: The firmware encountered an internal
Explanation: The inversion mask of a ring can not be problem.
found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B30D B181B30D
B181B307 B181B307
Explanation: The firmware encountered an internal
Explanation: This is an internal firmware problem. problem.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B308 B181B308 B181B30E B181B30E
Explanation: The firmware encountered an internal Explanation: The firmware is unable to allocate
problem. memory to store a list of rings. in its database.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B309 B181B309 B181B30F B181B30F
Explanation: The firmware encountered an internal Explanation: This is an internal firmware problem.
problem.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B310 B181B310
B181B30A B181B30A
Explanation: The firmare encountered an internal
Explanation: The firmware encountered an internal problem.
problem.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 421
B181B311 • B181B31C
B181B311 B181B311 B181B317 B181B317
Explanation: The firmware encountered an internal Explanation: An internal firmware error occurred.
problem.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B318 B181B318
B181B312 B181B312
Explanation: The firmware encountered a problem.
Explanation: The firmare encountered an internal
Response: If this is a tracking event, no service actions
problem.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B319 B181B319
Explanation: The firmware encountered a problem.
B181B313 B181B313
Response: If this is a tracking event, no service actions
Explanation: The firmware detected a problem where
are required. Otherwise, use the FRU and procedure
the defined data of a chip-checker is not valid.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B31A B181B31A
actions.
Explanation: The firmware encountered an internal
problem.
B181B314 B181B314
Response: If this is a tracking event, no service actions
Explanation: This is an internal firmware problem.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B31B B181B31B
Explanation: The firmware has detected a problem
B181B315 B181B315
where a chip is accessed when the chip is not at an
Explanation: This is an internal firmware problem. appropriate clock state.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B316 B181B316 B181B31C B181B31C
Explanation: The parity checking of the chip data Explanation: The firmare encountered an internal
failed. problem.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
422 System reference codes (Bxxx)
B181B31F • B181B508
callouts detailed with the SRC to determine service
B181B31F B181B31F
actions.
Explanation: The scan ring's factory pointer is null.
Response: If this is a tracking event, no service actions B181B487 B181B487
are required. Otherwise, use the FRU and procedure
Explanation: The chiplet base address is not valid.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B481 B181B481
actions.
Explanation: The service processor was unable to turn
on a chip clock.
B181B501 B181B501
Response: If this is a tracking event, no service actions
Explanation: A function was illegally called.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B482 B181B482
Explanation: The service processor was unable to turn
B181B503 B181B503
off a chip clock.
Explanation: The tables were asked for information
Response: If this is a tracking event, no service actions
they didn't have.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B483 B181B483
Explanation: Failure of a chip clock operation.
B181B505 B181B505
Response: If this is a tracking event, no service actions
Explanation: An error was encountered while trying
are required. Otherwise, use the FRU and procedure
to create an object.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B484 B181B484
actions.
Explanation: Internal firmware error.
Response: If this is a tracking event, no service actions B181B507 B181B507
are required. Otherwise, use the FRU and procedure
Explanation: The node ID and domain ID did not
callouts detailed with the SRC to determine service
describe a unique entry in this table.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B485 B181B485
callouts detailed with the SRC to determine service
Explanation: The clock selection value is not actions.
supported on this system.
Response: If this is a tracking event, no service actions B181B508 B181B508
are required. Otherwise, use the FRU and procedure
Explanation: File failure or end-of-file detected while
callouts detailed with the SRC to determine service
reading the table.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B486 B181B486
callouts detailed with the SRC to determine service
Explanation: Internal firmware error. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 423
B181B509 • B181B711
B181B509 B181B509 B181B510 B181B510
Explanation: The end of the table was reached before Explanation: An unsupported HDCT formatVersion
it was expected. was found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B50A B181B50A B181B511 B181B511
Explanation: An invalid parameter was passed in or Explanation: There is no record of this card in the
detectd from the table. configuration of this system; unable to find a resource
ID for it.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B50B B181B50B
B181B51B B181B51B
Explanation: Unable to open the general purpose I/O
(GPIO) engine to read the slot ID. Explanation: The memory DIMMs in the system are
not supported by the system firmware. Check for a
Response: If this is a tracking event, no service actions
newer level of system firmware and apply if available.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B50C B181B50C
Explanation: Rule was unable to open, or access, the
B181B703 B181B703
library that was indicated in the table.
Explanation: Unable to find an object in the mapper
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B50D B181B50D
B181B710 B181B710
Explanation: A class indicated in the tables has not
been found in the shared libraries on this build. Explanation: An internal firmware error occurred - the
data cannot be flattened.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B50F B181B50F
B181B711 B181B711
Explanation: An error was error returned from
ecmdDataBuffer. Explanation: An internal firmware error occurred - the
buffer sizes were not consistent.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
424 System reference codes (Bxxx)
B181B712 • B181B71E
B181B712 B181B712 B181B719 B181B719
Explanation: An internal firmware error occurred - the Explanation: An internal firmware error occurred - the
data cannot be flattened. registry key was set to an invalid value.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B713 B181B713 B181B71A B181B71A
Explanation: An internal firmware error occurred - the Explanation: An internal software error occurred - a
data cannot be flattened. persistent data value was not set as expected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B715 B181B715 B181B71B B181B71B
Explanation: The "manual power off" setting is not Explanation: The firmware was not able to find a
allowed since there is only one node in the system. processor card in this system. Look for other error log
entries that indicate problems with VPD collection.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B716 B181B716
B181B71C B181B71C
Explanation: The IPL was restarted due to hardware
deconfiguration. This is an informational message; no Explanation: The VPD cannot be updated with the
action is required. new L2 line-delete information because the record is
already full.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B717 B181B717
B181B71D B181B71D
Explanation: An internal firmware error occurred -
there was a data buffer error. Explanation: There is no space left in the line delete
table.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B718 B181B718
B181B71E B181B71E
Explanation: Unable to find a functional
communication path between the service processor and Explanation: The VPD cannot be updated with the
the processor. Look at the error logs and guard records new L3 line-delete information because the record is
to isolate the failing or missing hardware. already full.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 425
B181B720 • B181B72E
B181B720 B181B720 B181B729 B181B729
Explanation: The VPD indicates less space for Explanation: There was a pattern mismatch during the
line-delete entries than the firmware expects. This is an DMA test between the service processor and the
informational message; no action is required. processor; memory could not be read from or written
to correctly.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B722 B181B722
B181B72A B181B72A
Explanation: An internal software error occurred -
there was a data size mismatch. Explanation: An error was received when attempting
a DMA operation between the service processor and
Response: If this is a tracking event, no service actions
the processor.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B723 B181B723
Explanation: An undefined memory channel was
B181B72B B181B72B
found.
Explanation: Am internal software error occurred;
Response: If this is a tracking event, no service actions
attempting to execute firmware on the secondary
are required. Otherwise, use the FRU and procedure
service processor to recover.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B724 B181B724
actions.
Explanation: The vital product data (VPD) already has
a failing bit for this interface.
B181B72C B181B72C
Response: If this is a tracking event, no service actions
Explanation: An internal error occurred - the
are required. Otherwise, use the FRU and procedure
hardware is in an unexpected state the for current
callouts detailed with the SRC to determine service
operation.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B727 B181B727
callouts detailed with the SRC to determine service
Explanation: An internal software error occurred - the actions.
part that was specified is already deconfigured.
Response: If this is a tracking event, no service actions B181B72D B181B72D
are required. Otherwise, use the FRU and procedure
Explanation: This is an error log entry created by a
callouts detailed with the SRC to determine service
debug routine.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B728 B181B728
callouts detailed with the SRC to determine service
Explanation: The VPD information was not valid. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181B72E B181B72E
callouts detailed with the SRC to determine service
Explanation: A CHIC abort was detected.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
426 System reference codes (Bxxx)
B181B72F • B181B73D
B181B72F B181B72F B181B737 B181B737
Explanation: An unsupported system type was found. Explanation: The firmware detected corruption of the
GX reservation are in P2.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B731 B181B731
B181B738 B181B738
Explanation: The secondary service processor cannot
be tested in its current state. Explanation: The system must be rebooted before
making a GX adapter slot reservation.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B732 B181B732
B181B739 B181B739
Explanation: An internal firmware error occurred.
Explanation: Not enough memory was available to
Response: If this is a tracking event, no service actions
reserve a GX adapter.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B733 B181B733
Explanation: An internal firmware error occurred
B181B73B B181B73B
when attempting to handle a hardware error. Look for
previous entries in the error logs indicating a hardware Explanation: The calling function passed an invalid
error and follow the recommended actions. resource ID.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B734 B181B734 B181B73C B181B73C
Explanation: The CHIC operation received a signal. Explanation: A potential deadlock was detected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B736 B181B736 B181B73D B181B73D
Explanation: Failed when writing data to a memory Explanation: A lock was held beyond the threshold.
buffer.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 427
B181B73E • B181B834
B181B73E B181B73E B181B766 B181B766
Explanation: No progress on the IPL due to locks Explanation: The threshold of correctable errors was
being held. exceeded on the control module.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B73F B181B73F B181B820 B181B820
Explanation: The CEC experienced a power line fault Explanation: Internal software error
or outage.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B825 B181B825
B181B740 B181B740
Explanation: Unable to stop instructions on a
Explanation: The secondary service processor is seeing processor
missing devices.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B82B B181B82B
B181B741 B181B741
Explanation: Internal software error
Explanation: A hardware object manager (HOM)
Response: If this is a tracking event, no service actions
operation exceeded the allotted time.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B82E B181B82E
Explanation: Internal software error: attempt to
B181B742 B181B742
perform operation from the wrong state
Explanation: The hardware object manager (HOM)
Response: If this is a tracking event, no service actions
firmware may be hung.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B830 B181B830
Explanation: Internal software error
B181B765 B181B765
Response: If this is a tracking event, no service actions
Explanation: Duplicate erepair entries were found in
are required. Otherwise, use the FRU and procedure
the control module vendor VPD.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B834 B181B834
actions.
Explanation: Internal software error: the hardware to
perform requested operation was not found
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
428 System reference codes (Bxxx)
B181B835 • B181B859
callouts detailed with the SRC to determine service
B181B83F B181B83F
actions.
Explanation: An ECMD returned a non-zero return
code.
B181B835 B181B835
Response: If this is a tracking event, no service actions
Explanation: Internal software error
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B841 B181B841
Explanation: Failure occurred while attempting to
B181B836 B181B836
flush caches out to main storage
Explanation: Internal software error
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B84C B181B84C
B181B838 B181B838
Explanation: Failed to complete self-synchronization.
Explanation: Internal software error: hardware in
Response: If this is a tracking event, no service actions
incorrect state for attempted operation
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B857 B181B857
Explanation: Unable to properly quiesce I/O
B181B839 B181B839
hardware
Explanation: Internal software error: invalid
Response: If this is a tracking event, no service actions
parameter passed into function
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B858 B181B858
Explanation: Internal software error: required data is
B181B83B B181B83B
missing
Explanation: Unable to start executing instructions on
Response: If this is a tracking event, no service actions
a processor
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B859 B181B859
Explanation: Internal software error: requried data
B181B83C B181B83C
missing
Explanation: Unable to step instructions on a
Response: If this is a tracking event, no service actions
processor
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 429
B181B85A • B181B88B
callouts detailed with the SRC to determine service
B181B85A B181B85A
actions.
Explanation: Internal software error: error received
from device driver
B181B87C B181B87C
Response: If this is a tracking event, no service actions
Explanation: Internal software error: attempted to call
are required. Otherwise, use the FRU and procedure
invalid function
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B85D B181B85D
actions.
Explanation: The memory queues are not empty.
Response: If this is a tracking event, no service actions B181B87D B181B87D
are required. Otherwise, use the FRU and procedure
Explanation: Internal software error: an operation was
callouts detailed with the SRC to determine service
attempted on deconfigured hardware
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B85E B181B85E
callouts detailed with the SRC to determine service
Explanation: A maintenance command timed out. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181B884 B181B884
callouts detailed with the SRC to determine service
Explanation: An unsupported operation was
actions.
attempted.
Response: If this is a tracking event, no service actions
B181B85F B181B85F
are required. Otherwise, use the FRU and procedure
Explanation: A memory operation failed callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B887 B181B887
actions.
Explanation: Internal software information log entry;
informationl message only.
B181B860 B181B860
Response: If this is a tracking event, no service actions
Explanation: A command was in progress while are required. Otherwise, use the FRU and procedure
trying to send a maintenance command. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B889 B181B889
actions.
Explanation: Hardware configuration is invalid
Response: If this is a tracking event, no service actions
B181B862 B181B862
are required. Otherwise, use the FRU and procedure
Explanation: Hardware SMP bus alignment did not callouts detailed with the SRC to determine service
complete successfully actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181B88B B181B88B
callouts detailed with the SRC to determine service
Explanation: An internal firmware error occurred.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B87B B181B87B
callouts detailed with the SRC to determine service
Explanation: Internal software error: required attribute actions.
not set
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
430 System reference codes (Bxxx)
B181B88D • B181B89A
callouts detailed with the SRC to determine service
B181B88D B181B88D
actions.
Explanation: Internal software error: data buffer used
incorrectly
B181B895 B181B895
Response: If this is a tracking event, no service actions
Explanation: A hardware time-out occurred when
are required. Otherwise, use the FRU and procedure
attempting to access a chip.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B88E B181B88E
actions.
Explanation: Internal software error
Response: If this is a tracking event, no service actions B181B896 B181B896
are required. Otherwise, use the FRU and procedure
Explanation: A hardware error was detected on the
callouts detailed with the SRC to determine service
LDC chip.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B890 B181B890
callouts detailed with the SRC to determine service
Explanation: Unable to initialize internal hardware actions.
bus
Response: If this is a tracking event, no service actions B181B897 B181B897
are required. Otherwise, use the FRU and procedure
Explanation: The information from wire test is not
callouts detailed with the SRC to determine service
available.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B891 B181B891
callouts detailed with the SRC to determine service
Explanation: Errors were detected on an internal bus actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181B898 B181B898
callouts detailed with the SRC to determine service
Explanation: T he hypervisor has not handed off the
actions.
bus. There may be a hardware problem with the
interrupt.
B181B892 B181B892
Response: If this is a tracking event, no service actions
Explanation: HEA (host ethernet adapter) SCOM did are required. Otherwise, use the FRU and procedure
not complete. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B899 B181B899
actions.
Explanation: Unable to determine a valid self-sync
delay value based on the system type and nest
B181B893 B181B893 frequency.
Explanation: An internal firmware error occurred. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B181B89A B181B89A
B181B894 B181B894 Explanation: A hot removal operation did not
complete successfully.
Explanation: A hardware timeout occurred during a
cache operation. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 431
B181B89B • B181B90B
callouts detailed with the SRC to determine service
B181B901 B181B901
actions.
Explanation: The firmware encountered an internal
problem: it can't create an engine object for the system.
B181B89B B181B89B
Response: If this is a tracking event, no service actions
Explanation: The value for the maximum number of
are required. Otherwise, use the FRU and procedure
threads per processor core was not valid.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181B904 B181B904
actions.
Explanation: The firmware detected an internal
problem where the JTAG lock usage counter has an
B181B89C B181B89C
error.
Explanation: The throttling bits were invalid.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B905 B181B905
B181B8F2 B181B8F2
Explanation: The firmware encountered an internal
Explanation: SMA microcode failed to execute problem when it created a JTAG engine object.
correctly
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B906 B181B906
B181B8F3 B181B8F3
Explanation: The firmware was unable to create a
Explanation: A hardware operation timed out JTAG chain object.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B8F6 B181B8F6 B181B907 B181B907
Explanation: Informational message: bootstrap was Explanation: The firmware detected an internal
successful, but the service processor (or system problem: it attempted a JTAG scan operation without a
controller) was not allowed to set the MP available JTAG lock being granted.
latch.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B90B B181B90B
B181B8F7 B181B8F7
Explanation: A duplicate device string was in the list
Explanation: A checkstop was detected on a chip of devices returned from the field replaceable unit
during a concurr ent maintenance operation (FRU) manager.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
432 System reference codes (Bxxx)
B181B90C • B181B91B
B181B90C B181B90C B181B915 B181B915
Explanation: An engine is missing. Explanation: The SCOM device driver is unable to
scan the data out from the ID register
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B910 B181B910
B181B916 B181B916
Explanation: The firmware is unable to collect the
FFDC data from the ADAL (access device abstraction Explanation: The firmware encountered an internal
layer). problem: a chip doesn't have a valid scan interface.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B911 B181B911 B181B917 B181B917
Explanation: The firmware is unable to unlock the Explanation: An ADAL SCOM error occurred.
FFDC data after collecting it from the ADAL (access
Response: If this is a tracking event, no service actions
device abstraction layer).
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B918 B181B918
Explanation: An ADAL PSI error occurred.
B181B912 B181B912
Response: If this is a tracking event, no service actions
Explanation: The firmware is unable to reset the
are required. Otherwise, use the FRU and procedure
ADAL (access device abstraction layer) after an error
callouts detailed with the SRC to determine service
condition.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B919 B181B919
callouts detailed with the SRC to determine service
actions. Explanation: An ADAL JTAG error occurred.
Response: If this is a tracking event, no service actions
B181B913 B181B913 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The firmware encounters an error when
actions.
opening an ADAL (access device abstraction layer) to a
chip.
B181B91A B181B91A
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Unable to find the appropriate ADAL
callouts detailed with the SRC to determine service interface for the device type.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B914 B181B914 callouts detailed with the SRC to determine service
actions.
Explanation: An error was encountered when the
firmware tried to close the SCAN/SCOM device driver.
B181B91B B181B91B
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: An error was detected.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 433
B181B91C • B181B929
callouts detailed with the SRC to determine service
B181B924 B181B924
actions.
Explanation: The firmware timed out when waiting
for a JTAG lock to be granted by the JTAG ADAL
B181B91C B181B91C
(access device abstraction layer).
Explanation: Failed to open the test of a JTAG device.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B925 B181B925
B181B91D B181B91D
Explanation: The firmware encountered an error when
Explanation: Failed to close the test of a JTAG device. requesting the JTAG ADAL (access device abstraction
layer) to release the JTAG lock.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B920 B181B920
B181B926 B181B926
Explanation: The firmware encountered an error when
shifting a command into a chip as part of a scan Explanation: The firmware is unable to set the JTAG
operation. TAP (test access port) controller to a desired state.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B921 B181B921 B181B927 B181B927
Explanation: The firmware encountered an error when Explanation: The JTAG device driver was unable to
shifting data into a chip as part of a scan operation. write to the scan register.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B922 B181B922 B181B928 B181B928
Explanation: The firmware encountered an error when Explanation: The JTAG device driver is unable to clear
shifting data out from a chip as part of a scan the scan register.
operation.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B929 B181B929
B181B923 B181B923
Explanation: The JTAG ADAL (access device
Explanation: The firmware encountered an error when abstraction layer) failed to perform an SSR (simple scan
shifting data out from the JTAG chain into a memory register) scan.
buffer.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
434 System reference codes (Bxxx)
B181B92A • B181B944
B181B92A B181B92A B181B930 B181B930
Explanation: The JTAG ADAL (access device Explanation: ADAL returned error from the call to
abstraction layer) failed to perform an STSR (storage rdal_jtag_force_lock.
scan register) scan.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B940 B181B940
B181B92B B181B92B
Explanation: The SCOM device driver encountered an
Explanation: The JTAG device driver encountered an error when trying to read the status register of a chip.
error when reading one of the registers inside the chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B941 B181B941
B181B92C B181B92C
Explanation: The firmware encountered an error when
Explanation: The JTAG device driver encountered an trying to read data from a ring inside a chip.
error when writing to one of the registers inside the
Response: If this is a tracking event, no service actions
chip.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B942 B181B942
Explanation: The firmware encountered an error when
B181B92D B181B92D
trying to read data from an SCOM register inside a
Explanation: The firmware was unable to reset the chip.
JTAG TAP (test access port) controller.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B943 B181B943
B181B92E B181B92E
Explanation: The firmware encountered an error when
Explanation: The JTAG device driver encountered an trying to write data to a ring inside a chip.
error when trying to scan the hardware level register
Response: If this is a tracking event, no service actions
out from a chip.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B944 B181B944
Explanation: The firmware encountered an error when
B181B92F B181B92F
trying to write data to an SCOM register inside a chip.
Explanation: JTAG device driver encountered an error
Response: If this is a tracking event, no service actions
when trying to shift data into or out of a chip
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 435
B181B945 • B181B959
B181B945 B181B945 B181B94B B181B94B
Explanation: The SCOM device driver encountered an Explanation: The SCAN/SCOM device driver
error when trying to read a GP (general purpose) encountered an error when trying to write to an
register of a chip. internal register of a chip.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B946 B181B946 B181B955 B181B955
Explanation: The SCOM device driver encountered an Explanation: The PSI (processor support interface)
error when trying to write to a GP (general purpose) device driver encountered an error when reading an
register of a chip. SCOM register from the service processor chip.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B947 B181B947 B181B956 B181B956
Explanation: The ADAL failed to send a command to Explanation: The PSI (processor support interface)
a chip to perform a specified operation. device driver encountered an error when writing to an
SCOM type register from the service processor chip.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181B948 B181B948
B181B957 B181B957
Explanation: Unable to start a data flushing process
on a chip. Explanation: The PSI (processor support interface)
device driver encountered an error when reading from
Response: If this is a tracking event, no service actions
an SCOM-type register on the service processor chip.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B949 B181B949
Explanation: Unable to stop a data flushing process
B181B958 B181B958
on a chip.
Explanation: The PSI (processor support interface)
Response: If this is a tracking event, no service actions
device driver encountered an error when writing to an
are required. Otherwise, use the FRU and procedure
elastic interface type register from the service processor
callouts detailed with the SRC to determine service
chip.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181B94A B181B94A
callouts detailed with the SRC to determine service
Explanation: The SCAN/SCOM device driver actions.
encountered an error when trying to read an internal
register on a chip.
B181B959 B181B959
Response: If this is a tracking event, no service actions
Explanation: There was an ADAL mailbox scratch
are required. Otherwise, use the FRU and procedure
read error.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
436 System reference codes (Bxxx)
B181B95A • B181B96B
callouts detailed with the SRC to determine service
B181B966 B181B966
actions.
Explanation: The firmware detected a CRC
miscompare error from the specified chip.
B181B95A B181B95A
Response: If this is a tracking event, no service actions
Explanation: A function call failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B967 B181B967
Explanation: The firmware detected either a parity
B181B961 B181B961
error or an invalid command attention raised from the
Explanation: The firmware detected an internal specified chip.
problem: it released a JTAG lock that wasn't granted to
Response: If this is a tracking event, no service actions
it.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B968 B181B968
Explanation: The firmware encountered an internal
B181B962 B181B962
problem: a request to send an invalid JTAG command
Explanation: The firmware encountered an internal to the chip was made.
problem: it can't create a chip status object for a chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B969 B181B969
B181B963 B181B963
Explanation: The firmware detected an error in the
Explanation: The firmware detected that the value CRC calculation from the last data scanned out from
scanned out from the Instruction status segister of the the chip.
chip is invalid.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B96A B181B96A
B181B964 B181B964
Explanation: The firmware detected an internal error:
Explanation: The firmware detected an SCOM a chip doesn't have a valid functional unit or rule
attention raised from the specified chip. facade.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B965 B181B965 B181B96B B181B96B
Explanation: The firmware detected a non-SCOM vital Explanation: The firmware encountered an error:
error from the specified chip. access to a ring that does not exist in the system data
base was requested.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions.
(B1xx) Reference codes 437
B181B96C • B181B989
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B96C B181B96C B181B984 B181B984
Explanation: The firmware detected an internal error: Explanation: The firmware encountered an internal
access to an invalid GP (general purpose) register was error: access to an invalid GP (general purpose) register
requested. is requested.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B96D B181B96D B181B985 B181B985
Explanation: The firmware encountered an internal Explanation: The firmware encountered an internal
problem: a request to send an invalid JTAG command error doing operations using the ECMD data buffer.
has been sent to the chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B986 B181B986
B181B980 B181B980
Explanation: The firmware cncounters an internal
Explanation: The firmware encountered an internal problem: the string that specifies the location of a chip
problem: it can't create a chip status object for a chip. is invalid.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B981 B181B981 B181B987 B181B987
Explanation: The firmware encountered an internal Explanation: An internal register address was not
problem: the number of SCAN and SCOM device valid.
strings doesn't agree.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B988 B181B988
B181B982 B181B982
Explanation: A scan register was not valid.
Explanation: The firmware has detected an SCOM
Response: If this is a tracking event, no service actions
attention raised from the specified chip.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B989 B181B989
Explanation: An SCOM register was not valid.
B181B983 B181B983
Response: If this is a tracking event, no service actions
Explanation: The firmware detected a parity attention
are required. Otherwise, use the FRU and procedure
raised from the specified chip.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
438 System reference codes (Bxxx)
B181B995 • B181B9B0
B181B995 B181B995 B181B9A0 B181B9A0
Explanation: The firmware encountered an internal Explanation: The same device string appeared more
error: access to an invalid service processsor register than once in the list returned from FRUM FRU
type is requested. mGetDeviceList().
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B996 B181B996 B181B9A1 B181B9A1
Explanation: The firmware encountered an internal Explanation: The firmware encountered an internal
error: access to a PSI (processor support interface) problem; it can't find a chip object that is supposed to
register with an incorrect offset was requested. be system.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B997 B181B997 B181B9A2 B181B9A2
Explanation: The firmware encountered an internal Explanation: The system has issued an abort request
error: access to an invalid service processsor register while a chip is being scanned.
address is requested.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B9A3 B181B9A3
B181B998 B181B998
Explanation: The virtual power on (VPO) GetSCOM
Explanation: The firmware encountered an internal operation never finished.
error: access to an invalid service processsor) register
Response: If this is a tracking event, no service actions
address was requested.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181B9A4 B181B9A4
Explanation: An illegal call to getChipIds for
B181B999 B181B999
hyperboot mode was made with a hyperboot registry
Explanation: An unsupported operation was key that was not enabled.
attempted.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181B9B0 B181B9B0
B181B99A B181B99A
Explanation: The firmware encountered an internal
Explanation: Calling out the service processor test. error: a chip command is sent in to the wrong type of
chips.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 439
B181B9B1 • B181B9D0
callouts detailed with the SRC to determine service
B181B9B1 B181B9B1
actions.
Explanation: The ivJtagEnginePtr pointer is NULL.
Response: If this is a tracking event, no service actions B181B9C2 B181B9C2
are required. Otherwise, use the FRU and procedure
Explanation: The firmware encountered an internal
callouts detailed with the SRC to determine service
error: the number of commands sent into the chips (in
actions.
a chain) exceeds the storage buffer size.
Response: If this is a tracking event, no service actions
B181B9B2 B181B9B2
are required. Otherwise, use the FRU and procedure
Explanation: The scan error type was invalid. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B9C4 B181B9C4
actions.
Explanation: The firmware encountered an internal
error: it can't locate a chip that is supposed to be on
B181B9B4 B181B9B4 specified JTAG chain.
Explanation: The firmware encountered an internal Response: If this is a tracking event, no service actions
problem: a request to send an invalid JTAG command are required. Otherwise, use the FRU and procedure
ID has been sent to the LDC chip. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181B9C5 B181B9C5
actions.
Explanation: The firmware encountered an internal
error: the size of the data buffer that was provide is not
B181B9B5 B181B9B5 large enough to hold the data scanned out from the
chip.
Explanation: The firmware encountered an internal
problem: it can't create a chip status object for a chip. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B181B9C7 B181B9C7
B181B9B6 B181B9B6 Explanation: The verification of the JTAG chains in
the system failed.
Explanation: The ivFspEnginePtr pointeris NULL.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service
actions.
actions.
B181B9CB B181B9CB
B181B9B7 B181B9B7
Explanation: An unsupported scan type was found.
Explanation: Failed to initialize a chip status object.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service
actions.
actions.
B181B9D0 B181B9D0
B181B9C0 B181B9C0
Explanation: The general purpose (GP) register
Explanation: The firmware encountered an internal
number was not valid.
error: the position of a chip in a JTAG chain is invalid.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
440 System reference codes (Bxxx)
B181B9D1 • B181C01A
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B9D1 B181B9D1 B181C00A B181C00A
Explanation: An error was detected. Explanation: CINI failed to verify the host PCI bus
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181B9D2 B181B9D2 B181C00C B181C00C
Explanation: A chip checkstop was detected. Explanation: CINI has detected an invalid sharing
configuration. Too many or too few memory controllers
Response: If this is a tracking event, no service actions
are present.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181B9D8 B181B9D8
Explanation: A P7 PCB PIB time out occurred.
B181C00F B181C00F
Response: If this is a tracking event, no service actions
Explanation: CINI was unable to find a system elastic
are required. Otherwise, use the FRU and procedure
interface table for this backplane.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181C002 B181C002
actions.
Explanation: CINI has encountered a software failure.
Response: If this is a tracking event, no service actions B181C010 B181C010
are required. Otherwise, use the FRU and procedure
Explanation: CINI was unable to find an elastic
callouts detailed with the SRC to determine service
interface ID entry for the chip.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C004 B181C004
callouts detailed with the SRC to determine service
Explanation: A clock failure occurred. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181C019 B181C019
callouts detailed with the SRC to determine service
Explanation: CINI tried to get an object that could not
actions.
be found.
Response: If this is a tracking event, no service actions
B181C005 B181C005
are required. Otherwise, use the FRU and procedure
Explanation: CINI detected a processor clock failure. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181C01A B181C01A
actions.
Explanation: CINI received a bad parameter from the
calling function.
B181C009 B181C009
Response: If this is a tracking event, no service actions
Explanation: CINI failed to enable the host PCI bus are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 441
B181C01B • B181C030
B181C01B B181C01B B181C025 B181C025
Explanation: CINI was unable to find the frequency Explanation: The CEC initialization interpreter failed.
data that was requested.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C026 B181C026
B181C01C B181C01C
Explanation: CINI has detected an attempt to execute
Explanation: CINI has detected an invalid hardware an operation that is unsupported.
configuration.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C027 B181C027
B181C01D B181C01D
Explanation: CINI has received invalid data.
Explanation: CINI has detected a user-overridden
Response: If this is a tracking event, no service actions
logical memory block (LMB) size that is not valid for
are required. Otherwise, use the FRU and procedure
the systems memory size. The CINI will instead use
callouts detailed with the SRC to determine service
the default LMB size.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C02C B181C02C
callouts detailed with the SRC to determine service
actions. Explanation: A CINI call to an ECMD function
returned an error.
B181C021 B181C021 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: CINI was unable to find a plugin object
callouts detailed with the SRC to determine service
for the functional unit object.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C02F B181C02F
callouts detailed with the SRC to determine service
actions. Explanation: No master time-of-day clock chip was
found.
B181C022 B181C022 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: CINI has received an object that is not
callouts detailed with the SRC to determine service
the correct type.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C030 B181C030
callouts detailed with the SRC to determine service
actions. Explanation: CINI has detected an SCOM attention on
a chip. This chip will be deconfigured.
B181C024 B181C024 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Before an object was initialized, a
callouts detailed with the SRC to determine service
function was called on it.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
442 System reference codes (Bxxx)
B181C031 • B181C042
B181C031 B181C031 B181C03B B181C03B
Explanation: CINI has detected an invalid frequency Explanation: No fabric path was found.
setting.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C03C B181C03C
B181C032 B181C032
Explanation: The time-of-day clock path was not
Explanation: CINI has received a chip ID that was not valid.
found in the elastic interface table.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C03D B181C03D
B181C037 B181C037
Explanation: CINI was unable to reach the requested
Explanation: CINI failed to find a connection to or clock frequency.
from the chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C03F B181C03F
B181C038 B181C038
Explanation: CINI was unable to obtain a
Explanation: CINI was unable to find the time-of-day phased-locked loop (PLL) lock.
wire delays.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C041 B181C041
B181C039 B181C039
Explanation: Setting the clock frequency failed.
Explanation: CINI was unable to find the card name
Response: If this is a tracking event, no service actions
for the CCIN that was passed in.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181C042 B181C042
Explanation: There is no memory available in the
B181C03A B181C03A
system.
Explanation: CINI has detected a time-of-day delay
Response: If this is a tracking event, no service actions
for a chip that is too large.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 443
B181C043 • B181C106
B181C043 B181C043 B181C04A B181C04A
Explanation: CINI was unable to place a TCE in Explanation: A failure occurred when getting the
available memory. configuration variable.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C044 B181C044 B181C101 B181C101
Explanation: CINI was unable to find the chip ID of Explanation: No object was found that describes and
the attached I/O hub. allows access to the hardware.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C045 B181C045 B181C102 B181C102
Explanation: CINI has received an unrecognized Explanation: The hardware that is being accessed is
logical memory block (LMB) size. marked "not functional".
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C046 B181C046 B181C103 B181C103
Explanation: Multiple requests were made for the Explanation: There is no way to determine the
same interleaving group for in-memory trace. hardware characteristics necessary to access it.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C047 B181C047 B181C105 B181C105
Explanation: CINI has received a request for Explanation: The proper setup was not done prior to
in-memory trace that is larger than the available accessing hardware.
memory in the group.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C106 B181C106
B181C048 B181C048
Explanation: The clocks must be on, and they are not
Explanation: CINI has received a request for on.
in-memory trace that would cover the first 64 MB of
Response: If this is a tracking event, no service actions
addressable memory.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
444 System reference codes (Bxxx)
B181C107 • B181C11E
B181C107 B181C107 B181C118 B181C118
Explanation: The clocks are still running; they must Explanation: An attempt was made to access the
not be running to access an array. processor hardware without the proper set up being
done.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C108 B181C108
B181C119 B181C119
Explanation: The functional unit target had not been
selected. Explanation: A function returned an error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C111 B181C111 B181C11A B181C11A
Explanation: Setup was done incorrectly prior to Explanation: Instruction execution timed out.
calling the firmware that accesses hardware.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C11B B181C11B
B181C112 B181C112
Explanation: Core-specific array access requires a core
Explanation: The input stage flags were not valid. unit ID; none was provided.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C116 B181C116 B181C11C B181C11C
Explanation: The proper setup was not done prior to Explanation: A funtion was called that is not
entering a mode. supported.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C117 B181C117 B181C11E B181C11E
Explanation: Setup was done incorrectly prior to Explanation: An error was detected when reading
attempting to access the general purpose register. system storage.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 445
B181C11F • B181C131
B181C11F B181C11F B181C12B B181C12B
Explanation: The clocks are off, and no scan method is Explanation: An invalid relative thread number was
available. detected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C120 B181C120 B181C12C B181C12C
Explanation: An invalid chip ID was found. Explanation: An invalid trace array type was detected.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C123 B181C123 B181C12D B181C12D
Explanation: An error occurred in a procedure. Explanation: An invalid chip ID for the I/O hub was
encountered.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C125 B181C125
B181C12E B181C12E
Explanation: An attempt was made to initialize
optimizations when optimizations are currently Explanation: An invalid chip ID was encountered.
enabled.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C12F B181C12F
B181C126 B181C126
Explanation: An invalid chip ID was encountered.
Explanation: Scanring caching is on; it must be off
Response: If this is a tracking event, no service actions
prior to accessing a scanring.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181C130 B181C130
Explanation: An internal address counter error was
B181C128 B181C128
detected while reading system storage.
Explanation: No trace arrays were found on a chip.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C131 B181C131
Explanation: A command error was detected while
reading system storage.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
446 System reference codes (Bxxx)
B181C132 • B181C218
callouts detailed with the SRC to determine service
B181C140 B181C140
actions.
Explanation: An attempt was made to enter RAM
mode with a processor core that is not functioning.
B181C132 B181C132
Response: If this is a tracking event, no service actions
Explanation: An error was detected when reading
are required. Otherwise, use the FRU and procedure
system storage.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181C141 B181C141
actions.
Explanation: An error occurred when attempting to
read main storage.
B181C133 B181C133
Response: If this is a tracking event, no service actions
Explanation: An invalid address range was detected.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181C142 B181C142
Explanation: An error occurred when attempting to
B181C134 B181C134
read main storage.
Explanation: An invalid starting address was detected.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C144 B181C144
B181C135 B181C135
Explanation: An error occurred when attempting to
Explanation: The number of bytes was invalid. read main storage.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C136 B181C136 B181C145 B181C145
Explanation: An invalid memory address was Explanation: An error occurred when attempting to
detected. write to main storage.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C137 B181C137 B181C218 B181C218
Explanation: An attempt was made to enter a mode Explanation: An unknown chip group was found.
with a thread that is not functioning.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 447
B181C220 • B181C350
B181C220 B181C220 B181C2B3 B181C2B3
Explanation: Parameter 1 was invalid. Explanation: The beginning istep name was not
found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C263 B181C263
B181C2B4 B181C2B4
Explanation: The valid bit was not set.
Explanation: An invalid istep name was found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C264 B181C264
B181C2B8 B181C2B8
Explanation: An invalid clock state was found.
Explanation: Ring cache is enabled.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C288 B181C288
B181C2C6 B181C2C6
Explanation: An unexpected signal was received.
Explanation: A memory address was not found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C29E B181C29E
B181C2CA B181C2CA
Explanation: RSN code authorization failed.
Explanation: A memory service routine failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C2B1 B181C2B1
B181C2EB B181C2EB
Explanation: The SMGR returned bad status.
Explanation: The licensed internal code sent incorrect
Response: If this is a tracking event, no service actions
command values.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181C2B2 B181C2B2
Explanation: An invalid istep was received.
B181C350 B181C350
Response: If this is a tracking event, no service actions
Explanation: The application received a signal.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
448 System reference codes (Bxxx)
B181C351 • B181C36A
callouts detailed with the SRC to determine service
B181C351 B181C351
actions.
Explanation: CHIC was aborted.
Response: If this is a tracking event, no service actions B181C35A B181C35A
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when sending a
callouts detailed with the SRC to determine service
message.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C352 B181C352
callouts detailed with the SRC to determine service
Explanation: The string parameter cannot be empty actions.
for this function type.
Response: If this is a tracking event, no service actions B181C35B B181C35B
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when receiving a
callouts detailed with the SRC to determine service
message.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C353 B181C353
callouts detailed with the SRC to determine service
Explanation: An error occurred when receiving a actions.
message.
Response: If this is a tracking event, no service actions B181C35E B181C35E
are required. Otherwise, use the FRU and procedure
Explanation: There was an error initializing the server
callouts detailed with the SRC to determine service
daemon.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C356 B181C356
callouts detailed with the SRC to determine service
Explanation: A function call failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181C35F B181C35F
callouts detailed with the SRC to determine service
Explanation: An error handle passed in was null.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C357 B181C357
callouts detailed with the SRC to determine service
Explanation: An invalid command was sent. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181C366 B181C366
callouts detailed with the SRC to determine service
Explanation: An error occurred when flattening data
actions.
for a call to the hardware object manager (HOM).
Response: If this is a tracking event, no service actions
B181C358 B181C358
are required. Otherwise, use the FRU and procedure
Explanation: A failure occurred when obtaining a lock callouts detailed with the SRC to determine service
in the serial thread. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181C36A B181C36A
callouts detailed with the SRC to determine service
Explanation: A parameter was missing.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C359 B181C359
callouts detailed with the SRC to determine service
Explanation: An error occurred when sending a actions.
message.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 449
B181C36B • B181C379
B181C36B B181C36B B181C372 B181C372
Explanation: An unrecognized command was Explanation: An invalid character was found.
received.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C373 B181C373
B181C36C B181C36C
Explanation: An unknown value was found.
Explanation: A function was not found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C374 B181C374
B181C36D B181C36D
Explanation: A buffer was too small.
Explanation: There were unused parameters.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C375 B181C375
B181C36E B181C36E
Explanation: An unknown output type was found.
Explanation: An unknown option was found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C376 B181C376
B181C36F B181C36F
Explanation: A network error occurred.
Explanation: A value was missing.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181C378 B181C378
B181C370 B181C370
Explanation: An unsupported HMC operation was
Explanation: An invalid function type was found. attempted.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C371 B181C371 B181C379 B181C379
Explanation: A variable was out of range. Explanation: An error occurred when flattening a data
buffer.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
450 System reference codes (Bxxx)
B181C37A • B181C734
B181C37A B181C37A B181C727 B181C727
Explanation: An error occurred when unflattening Explanation: The firmware failed to read the line
data returned from a call to the hardware object delete from VPD.
manager (HOM).
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, detailed with the are required. Otherwise, use the FRU and procedure
SRC to determine service actions. callouts detailed with the SRC to determine service
actions.
B181C6E9 B181C6E9
B181C72A B181C72A
Explanation: No ASIC found
Explanation: The RIO port speed is invalid.
Response: If this is a tracking event, detailed with the
SRC to determine service actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181C70B B181C70B
actions.
Explanation: The failed to get the time of day.
Response: If this is a tracking event, no service actions B181C72C B181C72C
are required. Otherwise, use the FRU and procedure
Explanation: The number of packets received did not
callouts detailed with the SRC to determine service
equal the number of packets sent, of the cyclic
actions.
redundancy check (CRC) did not = 0.
Response: If this is a tracking event, no service actions
B181C70C B181C70C
are required. Otherwise, use the FRU and procedure
Explanation: The memory controller object was not callouts detailed with the SRC to determine service
found. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181C72F B181C72F
callouts detailed with the SRC to determine service
Explanation: The physical status registers were not set
actions.
to link; the test cannot proceed.
Response: If this is a tracking event, no service actions
B181C70D B181C70D
are required. Otherwise, use the FRU and procedure
Explanation: The memory controller had been set to callouts detailed with the SRC to determine service
an invalid state. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181C730 B181C730
callouts detailed with the SRC to determine service
Explanation: T he number of packets received did not
actions.
equal the number of packets sent, of the cyclic
redundancy check (CRC) did not = 0.
B181C718 B181C718
Response: If this is a tracking event, no service actions
Explanation: The main storage diagnostics detected an are required. Otherwise, use the FRU and procedure
uncorrectable error on a DRAM. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181C734 B181C734
actions.
Explanation: An invalid address was found in the test
case list.
B181C719 B181C719
Response: If this is a tracking event, no service actions
Explanation: Too many correctable errors were are required. Otherwise, use the FRU and procedure
detected. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 451
B181C737 • B181C74E
B181C737 B181C737 B181C740 B181C740
Explanation: The load type of the test case structure Explanation: The L2 AVPS test has completed
did not indicate the memory type test case. successfully (informational message).
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C73B B181C73B B181C741 B181C741
Explanation: While iterating through the list of core Explanation: Failed to get the CEC cage functional
functional units, a null pointer was found. unit group.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181C73C B181C73C B181C743 B181C743
Explanation: Failed to get a pointer. Explanation: The test case number that was provided
was not valid.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C73D B181C73D
B181C744 B181C744
Explanation: The test did not complete within the
specified time. Explanation: The CEC cage number that was provided
did not match the expected value.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C73E B181C73E
B181C749 B181C749
Explanation: The test did not complete within the
specified time. Explanation: Unable to read AVPS data from a file
into ecmd data buffer
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181C73F B181C73F
B181C74E B181C74E
Explanation: The data in the status address is not
changing. Data should be changing if the test were Explanation: A failure occured while checking the
running correctly. status of the memory test case.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
452 System reference codes (Bxxx)
B181C750 • B181C822
B181C750 B181C750 B181C801 B181C801
Explanation: A failure occured while getting Explanation: Wire test detected a CST error.
instruction status from the core, but the attention
Response: If this is a tracking event, no service actions
handling routine didn't find any errors.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181C802 B181C802
Explanation: The wire test firmware detected an error.
B181C751 B181C751
Response: If this is a tracking event, no service actions
Explanation: The memory AVPS test has completed
are required. Otherwise, use the FRU and procedure
successfully (informational message).
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181C80F B181C80F
actions.
Explanation: The wire test error log is full.
B181C752 B181C752 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: There was no core in the EC range.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181C81A B181C81A
actions.
Explanation: A null pointer was found.
B181C753 B181C753 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: While iterating through the list of core
callouts detailed with the SRC to determine service
functional units, a null pointer was found.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C81B B181C81B
callouts detailed with the SRC to determine service
actions. Explanation: A problem was found with a hardware
object manager (HOM) unit ID.
B181C754 B181C754 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to get connected fabric functional
callouts detailed with the SRC to determine service
pointer.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C820 B181C820
callouts detailed with the SRC to determine service
actions. Explanation: The calling function provided an invalid
L3 chip hardware object manager (HOM) unit ID.
B181C76A B181C76A Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Informational message: An L3 line delete
callouts detailed with the SRC to determine service
occurred.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C822 B181C822
callouts detailed with the SRC to determine service
actions. Explanation: Informational message: An e-repair was
done successfully.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 453
B181C823 • B181CA02
callouts detailed with the SRC to determine service
B181C854 B181C854
actions.
Explanation: Wire test has detected an RDT error.
B181C823 B181C823 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The system processor group object was
callouts detailed with the SRC to determine service
not found.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C876 B181C876
callouts detailed with the SRC to determine service
actions. Explanation: An e-repair was successfully applied.
Response: If this is a tracking event, no service actions
B181C826 B181C826 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An error occurred.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181C877 B181C877
callouts detailed with the SRC to determine service
actions. Explanation: An e-repair was applied successfully.
Response: If this is a tracking event, no service actions
B181C82B B181C82B are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Service processor cable test failure:
actions.
wrong cable ID.
Response: If this is a tracking event, no service actions
B181C87C B181C87C
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: An error occurred when getting the
actions. functional unit for the receiver.
Response: If this is a tracking event, no service actions
B181C82D B181C82D are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Service processor cable test failure:
actions.
drawer not present.
Response: If this is a tracking event, no service actions
B181C953 B181C953
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: An error was detected by the operating
actions. system when communicating with the service
processor.
B181C851 B181C851 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Wire test detected more than 64 wire
callouts detailed with the SRC to determine service
errors; the log file is full.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181CA01 B181CA01
callouts detailed with the SRC to determine service
actions. Explanation: The resource was guarded out.
Response: If this is a tracking event, no service actions
B181C853 B181C853 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An error was detected by the operating
actions.
system when communicating with the service
processor.
B181CA02 B181CA02
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Informational only: Guard actions
callouts detailed with the SRC to determine service performed on items the system detected and guarded
actions. during runtime, or that were guarded out using the
ASMI.
454 System reference codes (Bxxx)
B181CA03 • B181CA12
Response: If this is a tracking event, no service actions
B181CA08 B181CA08
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: A bad return code was received from
actions. reading a utility file or seeking in a utility file when
trying to read the processor domain data from the
guard file.
B181CA03 B181CA03
Response: If this is a tracking event, no service actions
Explanation: The guard data did not exist because it
are required. Otherwise, use the FRU and procedure
was the first boot of this system, or NVRAM had been
callouts detailed with the SRC to determine service
cleared. Guard data is now available.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181CA0C B181CA0C
callouts detailed with the SRC to determine service
actions. Explanation: Failed to get the hardware object
manager (HOM) unit ID.
B181CA04 B181CA04 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Guard detected a new version of the
callouts detailed with the SRC to determine service
guard data area. The guard data area was reformatted
actions.
and the previous guard actions have been lost.
Response: If this is a tracking event, no service actions
B181CA0E B181CA0E
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: An error was received when trying to
actions. read a registry value.
Response: If this is a tracking event, no service actions
B181CA05 B181CA05 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The guard firmware detected corrupted
actions.
guard data. The guard data was reformatted and all
previous guard actions have been erased.
B181CA0F B181CA0F
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: An error log was received from the
callouts detailed with the SRC to determine service SVPD when trying to read the VPD for a given
actions. resource ID.
Response: If this is a tracking event, no service actions
B181CA06 B181CA06 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The guard function was not able to open
actions.
the guard memory file.
Response: If this is a tracking event, no service actions
B181CA11 B181CA11
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The resource ID was not found in the
actions. system guard data file.
Response: If this is a tracking event, no service actions
B181CA07 B181CA07 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A bad return code was received from
actions.
reading a utility file or seeking in a utility file when
trying to read the processor domain data from the
guard file. B181CA12 B181CA12
Response: If this is a tracking event, no service actions Explanation: Manual deconfiguration of the service
are required. Otherwise, use the FRU and procedure processor (or system controller) is not allowed because
callouts detailed with the SRC to determine service the service processor has already been deconfigured by
actions. the system, or the system is at runtime.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 455
B181CA15 • B181D00F
callouts detailed with the SRC to determine service
B181D005 B181D005
actions.
Explanation: The hypervisor reported an error when
turning off the parent indicator.
B181CA15 B181CA15
Response: If this is a tracking event, no service actions
Explanation: Unguarding the sibling service processor
are required. Otherwise, use the FRU and procedure
is not allowed at runtime.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D006 B181D006
actions.
Explanation: An unknown error occured when trying
to update the indicator status.
B181CC60 B181CC60
Response: If this is a tracking event, no service actions
Explanation: The oscillator (clock) card is not
are required. Otherwise, use the FRU and procedure
functional.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D007 B181D007
actions.
Explanation: There was a failure when getting the
SPIF data.
B181CD0A B181CD0A
Response: If this is a tracking event, no service actions
Explanation: The number of lane failures between the
are required. Otherwise, use the FRU and procedure
control module and the optical links exceeded the
callouts detailed with the SRC to determine service
threshold during an internal test.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D008 B181D008
callouts detailed with the SRC to determine service
actions. Explanation: Socket creation (for listening) failed.
Response: If this is a tracking event, no service actions
B181CD0B B181CD0B are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The number of lane failures between the
actions.
control module and the optical links exceeded the
threshold during an internal test.
B181D009 B181D009
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: A call to bind() failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D003 B181D003 actions.
Explanation: A nonzero status code was returned.
B181D00F B181D00F
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: A signal was received that not is handled
callouts detailed with the SRC to determine service by the ASMI.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D004 B181D004 callouts detailed with the SRC to determine service
actions.
Explanation: An unknown error occurred when trying
to obtain the indicator status.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
456 System reference codes (Bxxx)
B181D010 • B181D112
B181D010 B181D010 B181D10B B181D10B
Explanation: The service processor is being reset. Explanation: A null pointer was received from the
mapper; a pointer to the JTAG engine being used was
Response: If this is a tracking event, no service actions
expected.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D102 B181D102
Explanation: The write interface failed while
B181D10D B181D10D
initializing a file.
Explanation: The system failed to respond after a
Response: If this is a tracking event, no service actions
recoverable error was eliminated .
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D103 B181D103
Explanation: The read utility failed on a breakpoint
B181D10E B181D10E
attention
Explanation: A JTAG failed while waiting for an
Response: If this is a tracking event, no service actions
attention
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D104 B181D104
Explanation: The write operation failed when writing
B181D10F B181D10F
to the attnDataFile.
Explanation: DA alter failed during the write to main
Response: If this is a tracking event, no service actions
storage.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D108 B181D108
Explanation: Failed to initialize the HYSR flag.
B181D110 B181D110
Response: If this is a tracking event, no service actions
Explanation: There was a failure when reading a
are required. Otherwise, use the FRU and procedure
JTAG register.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D109 B181D109
actions.
Explanation: The read utility failed after a breakpoint
attention
B181D112 B181D112
Response: If this is a tracking event, no service actions
Explanation: Failed to enable attentions through the
are required. Otherwise, use the FRU and procedure
enable attentions interface.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 457
B181D113 • B181D120
callouts detailed with the SRC to determine service
B181D113 B181D113
actions.
Explanation: JTAG timed out while waiting for a lock.
Response: If this is a tracking event, no service actions B181D11B B181D11B
are required. Otherwise, use the FRU and procedure
Explanation: The write utility failed when writing the
callouts detailed with the SRC to determine service
termination flag.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D114 B181D114
callouts detailed with the SRC to determine service
Explanation: Disabling the attentions failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181D11C B181D11C
callouts detailed with the SRC to determine service
Explanation: An emergency power off (EPO) PLCK
actions.
failed.
Response: If this is a tracking event, no service actions
B181D116 B181D116
are required. Otherwise, use the FRU and procedure
Explanation: Failed to get P0 root path size. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181D11D B181D11D
actions.
Explanation: A spurious attention was detected after
attempting to clear all attentions for the ISR.
B181D117 B181D117
Response: If this is a tracking event, no service actions
Explanation: Failed to write a flag to the registry . are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B181D11E B181D11E
Explanation: CHIC timed out while getting a reserve
B181D118 B181D118 ID to process a processor checkstop.
Explanation: Failure when opening the Ahdata.dat file Response: If this is a tracking event, no service actions
for a write operation. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B181D11F B181D11F
Explanation: Failed while attempting to release the
B181D119 B181D119 CHIC reserve.
Explanation: The hypervisor wrote an invalid SRC in Response: If this is a tracking event, no service actions
the attention area. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions. B181D120 B181D120
Explanation: The processor runtime diagnostics failed
B181D11A B181D11A to create an error handle for a processor checkstop.
Explanation: A communications failure occurred on Response: If this is a tracking event, no service actions
the primary service processor. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
458 System reference codes (Bxxx)
B181D121 • B181D12F
B181D121 B181D121 B181D127 B181D127
Explanation: Failed to read main storage after a Explanation: DA display failed during the write to
breakpoint attention main storage.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D122 B181D122 B181D128 B181D128
Explanation: Failed to write to main storage after a Explanation: An EcmdDataBuffer set length failure.
breakpoint attention.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D12B B181D12B
B181D123 B181D123
Explanation: AH server processor failed.
Explanation: A bad return code was received from a
Response: If this is a tracking event, no service actions
write operation.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D12C B181D12C
Explanation: HYRS interface failure.
B181D124 B181D124
Response: If this is a tracking event, no service actions
Explanation: A JTAG lock cannot be released.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D12D B181D12D
Explanation: A CCSP interface failure.
B181D125 B181D125
Response: If this is a tracking event, no service actions
Explanation: CHIC failure when getting a functional
are required. Otherwise, use the FRU and procedure
group
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D12E B181D12E
actions.
Explanation: SBCU interface failure.
B181D126 B181D126 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: HDAT failed while mapping main storag
callouts detailed with the SRC to determine service
e to get attention areas.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D12F B181D12F
callouts detailed with the SRC to determine service
actions. Explanation: Disabling the attentions failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 459
B181D131 • B181D13F
B181D131 B181D131 B181D138 B181D138
Explanation: There was a failure of the mailbox Explanation: The hypervisor requested a TI; an error
interface on an asset protection attention . log is built with the terminating SRC
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D133 B181D133 B181D139 B181D139
Explanation: The CECserver firmware detected a Explanation: Manufacturing interface to read the
stopped clock due to an error attention. policy flag failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D134 B181D134 B181D13A B181D13A
Explanation: AH server process failed. Explanation: The call to generate an event failed
during a non-IO checkstop.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D135 B181D135
B181D13B B181D13B
Explanation: A function returned with a failure.
Explanation: A null pointer was received; a pointer to
Response: If this is a tracking event, no service actions
the functional unit group SystemProc was expected.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D136 B181D136
Explanation: The read utility failed to read the current
B181D13E B181D13E
IPL type from the state manager.
Explanation: The list of chips at attention came back
Response: If this is a tracking event, no service actions
empty; attention processing cannot continue.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D137 B181D137
Explanation: A chip was asked to service a special
B181D13F B181D13F
attention, but it doesn't support it .
Explanation: The read utility failed to read the current
Response: If this is a tracking event, no service actions
role of the service processor.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
460 System reference codes (Bxxx)
B181D140 • B181D14E
B181D140 B181D140 B181D146 B181D146
Explanation: An event timed out. Explanation: The incorrect object was used.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D141 B181D141 B181D147 B181D147
Explanation: The chip attention handler was asked to Explanation: Failed to create the FSI thread attribute
handle an invalid attention type . object.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D142 B181D142 B181D148 B181D148
Explanation: A master attention alone was detected. Explanation: F ailed to get a lock
This is a condition where the master attention bit is
Response: If this is a tracking event, no service actions
active when there are no valid attention types
are required. Otherwise, use the FRU and procedure
triggering this attention.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D149 B181D149
actions.
Explanation: The attention handler received an
unexpected signal .
B181D143 B181D143
Response: If this is a tracking event, no service actions
Explanation: A thread that isn't alive raised a special
are required. Otherwise, use the FRU and procedure
attention.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D14A B181D14A
actions.
Explanation: Error creating the chip ADAL strings file.
B181D144 B181D144 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: One or more lines are stuck low because
callouts detailed with the SRC to determine service
the value read back does not match the value
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D14D B181D14D
callouts detailed with the SRC to determine service
actions. Explanation: P5IOC attention-handling-in-progress set.
Response: If this is a tracking event, no service actions
B181D145 B181D145 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An scom attention was detected on the
actions.
current chip.
Response: If this is a tracking event, no service actions
B181D14E B181D14E
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: No attention line group object was found
actions. for this chip.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 461
B181D14F • B181D224
callouts detailed with the SRC to determine service
B181D15D B181D15D
actions.
Explanation: An empty list was found.
B181D14F B181D14F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to get the chip device strings
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D15F B181D15F
actions.
Explanation: An SCOM attention/checkstop scenario
was encountered.
B181D150 B181D150
Response: If this is a tracking event, no service actions
Explanation: Call out the chips on the attention line
are required. Otherwise, use the FRU and procedure
that caused the attention.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D160 B181D160
actions.
Explanation: The attention component is terminating.
B181D151 B181D151 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: There was a callout failure.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D161 B181D161
actions.
Explanation: A monitor failure occurred.
B181D154 B181D154 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The threads are not finished.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D165 B181D165
actions.
Explanation: A clock failure occurred.
B181D155 B181D155 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: There was a connection failure.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D223 B181D223
actions.
Explanation: A failure occurred when reading a
registry value.
B181D159 B181D159
Response: If this is a tracking event, no service actions
Explanation: An invalid register value was found.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D224 B181D224
Explanation: An unknown box value was found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
462 System reference codes (Bxxx)
B181D225 • B181D231
B181D225 B181D225 B181D22B B181D22B
Explanation: A failure occurred when reading a Explanation: An error occurred in a function.
registry value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D22C B181D22C
B181D226 B181D226
Explanation: A failure occurred when forking a child
Explanation: A failure occurred when reading a process.
registry value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D22D B181D22D
B181D227 B181D227
Explanation: Unable to signal the other processes to
Explanation: A failure occurred when reading a clean up via a system call.
registry value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D22E B181D22E
B181D228 B181D228
Explanation: The daemon may not be running.
Explanation: A failure occurred when trying to read
Response: If this is a tracking event, no service actions
the processor speed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D22F B181D22F
Explanation: The parser encountered too many of a
B181D229 B181D229
special character on a single line.
Explanation: An error occurred when a query was
Response: If this is a tracking event, no service actions
made of the power management mode.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D230 B181D230
Explanation: Unable to create a new daemon.
B181D22A B181D22A
Response: If this is a tracking event, no service actions
Explanation: Unable to configure a target.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D231 B181D231
Explanation: An error occurred in a system call.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 463
B181D232 • B181D23E
callouts detailed with the SRC to determine service
B181D238 B181D238
actions.
Explanation: An error occurred in a system call.
B181D232 B181D232 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A failure occurred in a function call.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D239 B181D239
actions.
Explanation: An error occurred in a system call.
B181D233 B181D233 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Unable to open the log file header after
callouts detailed with the SRC to determine service
two attempts.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D23A B181D23A
callouts detailed with the SRC to determine service
actions. Explanation: An error occurred in a system call.
Response: If this is a tracking event, no service actions
B181D234 B181D234 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Unable to open the log file after two
actions.
attempts. .
Response: If this is a tracking event, no service actions
B181D23B B181D23B
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The expected number of processors was
actions. not found.
Response: If this is a tracking event, no service actions
B181D235 B181D235 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: Unable to write the log file header.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D23C B181D23C
callouts detailed with the SRC to determine service
actions. Explanation: An invalid number of arguments was
received for a command.
B181D236 B181D236 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Unable to write the log file data.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D23D B181D23D
actions.
Explanation: The requested pass-through command
failed.
B181D237 B181D237
Response: If this is a tracking event, no service actions
Explanation: The stepsize is zero, which is invalid.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D23E B181D23E
Explanation: An invalid command was found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
464 System reference codes (Bxxx)
B181D23F • B181D303
callouts detailed with the SRC to determine service
B181D245 B181D245
actions.
Explanation: An error was returned from a slew
command.
B181D23F B181D23F
Response: If this is a tracking event, no service actions
Explanation: An internal error occurred when a query
are required. Otherwise, use the FRU and procedure
was made of the current power management mode.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D247 B181D247
actions.
Explanation: An error occurred when executing a
sweep command.
B181D240 B181D240
Response: If this is a tracking event, no service actions
Explanation: A failure occurred when forking a child
are required. Otherwise, use the FRU and procedure
process.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D248 B181D248
actions.
Explanation: Informational message: The
customer-requested power mode was changed outside
B181D241 B181D241
of this application's control. The power mode was
Explanation: The input argument was not a valid probably changed by an external entity.
string buffer.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D301 B181D301
B181D242 B181D242
Explanation: An internal error while accessing the
Explanation: An error occurred when updating the cluster machine type/model.
table iteration count.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D302 B181D302
B181D243 B181D243
Explanation: An operation on a session entry object
Explanation: An error occurred when executing a failed.
table command.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D303 B181D303
B181D244 B181D244
Explanation: Failed to construct a netc address object.
Explanation: An error occurred when writing the
Response: If this is a tracking event, no service actions
number of the currently-executing line.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 465
B181D304 • B181D30F
B181D304 B181D304 B181D30A B181D30A
Explanation: A call into a NETS component interface Explanation: The caller attempted to perform an
failed. operation on an invalid file type.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D305 B181D305 B181D30B B181D30B
Explanation: The mboxOpenHMCInterface call Explanation: A call to mkdir failed.
succeeded but the hypervisor returned an error when
Response: If this is a tracking event, no service actions
attempting to open a hypervisor session.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D30C B181D30C
Explanation: Failed trying to subscribe to, or signal,
B181D306 B181D306
an event.
Explanation: Failed to read or write data to or from a
Response: If this is a tracking event, no service actions
data buffer.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D30D B181D30D
Explanation: Memory allocation failure.
B181D307 B181D307
Response: If this is a tracking event, no service actions
Explanation: A mailbox component interface returned
are required. Otherwise, use the FRU and procedure
an error.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D30E B181D30E
actions.
Explanation: The hardware management console
(HMC) was unable to open a hypervisor session
B181D308 B181D308
because the service processor (or system controller)
Explanation: Failed to read or write a registry key. firmware determined that the hypervisor was not
running.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D309 B181D309
B181D30F B181D30F
Explanation: The caller attempted to create an event
broadcast object using an unknown broadcast type. Explanation: A call into spifWriteBlockCommand to
get the cage and frame number failed. The failure is not
Response: If this is a tracking event, no service actions
specified, so the service processor (or system controller)
are required. Otherwise, use the FRU and procedure
will return a generic failure status to the hardware
callouts detailed with the SRC to determine service
management console (HMC).
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
466 System reference codes (Bxxx)
B181D310 • B181D31B
B181D310 B181D310 B181D316 B181D316
Explanation: An error was received when trying to Explanation: The client was not able to obtain the
open the LEDs file. requested resource lock.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D311 B181D311 B181D317 B181D317
Explanation: Using the non-blocking mode for Explanation: The client was unable to release a
semaphore operations, it was determined that no resource lock.
operation was performed during the lock table
Response: If this is a tracking event, no service actions
command.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D318 B181D318
Explanation: UTIL component file-related operation
B181D312 B181D312
failed.
Explanation: The caller of an interface supplied an
Response: If this is a tracking event, no service actions
invalid parameter or the interface unexpectedly failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D319 B181D319
Explanation: The client that was attempting to
B181D313 B181D313
authenticate itself supplied an invalid password.
Explanation: Failed to calculate the timestamp stored
Response: If this is a tracking event, no service actions
in the session entry object.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D31A B181D31A
Explanation: An SMGR component operation failed.
B181D314 B181D314
Response: If this is a tracking event, no service actions
Explanation: Failed to acknowledge surveillance.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D31B B181D31B
Explanation: A command sent to the hypervisor failed
B181D315 B181D315
with a return status.
Explanation: The hardware management console
Response: If this is a tracking event, no service actions
(HMC) sent an invalid record.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 467
B181D31C • B181D328
B181D31C B181D31C B181D323 B181D323
Explanation: Unable to issue this command unless the Explanation: The CHIC component returned a failure
hypervisor is at standby. code.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D31D B181D31D B181D324 B181D324
Explanation: A SPIF component operation failed. Explanation: Informational message: No system
memory was found by the guard function, so the
Response: If this is a tracking event, no service actions
system has never been booted.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D31E B181D31E
Explanation: A failure occurred in an API.
B181D325 B181D325
Response: If this is a tracking event, no service actions
Explanation: Failed to perform the requested
are required. Otherwise, use the FRU and procedure
operation due to lack of access permissions.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D31F B181D31F
actions.
Explanation: An error occurred.
Response: If this is a tracking event, no service actions B181D326 B181D326
are required. Otherwise, use the FRU and procedure
Explanation: A concurrent maintenance interface
callouts detailed with the SRC to determine service
returned an error.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D320 B181D320
callouts detailed with the SRC to determine service
Explanation: The response data from SPIF was not actions.
valid.
Response: If this is a tracking event, no service actions B181D327 B181D327
are required. Otherwise, use the FRU and procedure
Explanation: Unable to initiate the node controller
callouts detailed with the SRC to determine service
dump due to the wrong target system.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D321 B181D321
callouts detailed with the SRC to determine service
Explanation: A validation error occurred. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181D328 B181D328
callouts detailed with the SRC to determine service
Explanation: A resource was not found.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D322 B181D322
callouts detailed with the SRC to determine service
Explanation: A code update (CUPD) error occurred. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
468 System reference codes (Bxxx)
B181D401 • B181D50B
callouts detailed with the SRC to determine service
B181D401 B181D401
actions.
Explanation: An error occurred.
Response: If this is a tracking event, no service actions B181D506 B181D506
are required. Otherwise, use the FRU and procedure
Explanation: An open operation failed on a device.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D402 B181D402
actions.
Explanation: Failed to spawn a process, or a failure
occurred in a Unix system call.
B181D507 B181D507
Response: If this is a tracking event, no service actions
Explanation: A close operation failed on a device.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D403 B181D403
Explanation: An error occurred.
B181D508 B181D508
Response: If this is a tracking event, no service actions
Explanation: A read operation failed on a device.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D406 B181D406
Explanation: An error occurred, but the reason for the
B181D509 B181D509
error was not determined.
Explanation: A write operation failed on a device.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D502 B181D502
B181D50A B181D50A
Explanation: An SDR record that was not type 2 or
type 3 was found. Explanation: A configuration operation failed on a
device.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D503 B181D503
B181D50B B181D50B
Explanation: Failure to read a registry value.
Explanation: Unable to open the general purpose I/O
Response: If this is a tracking event, no service actions
(GPIO) engine to read the slot ID.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D505 B181D505
Explanation: Unable to create the IPMI server process.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 469
B181D50C • B181D606
callouts detailed with the SRC to determine service
B181D50C B181D50C
actions.
Explanation: Unable to close the general purpose I/O
(GPIO) engine of a device.
B181D601 B181D601
Response: If this is a tracking event, no service actions
Explanation: Failed to read the path from the registry.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D50D B181D50D
Explanation: An error occurred when trying to read
B181D602 B181D602
the general purpose I/O (GPIO) pin.
Explanation: Failed to fork a daemon.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D50E B181D50E
B181D603 B181D603
Explanation: Unable to create a process.
Explanation: Failed to create a synchronization file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D50F B181D50F
B181D604 B181D604
Explanation: The dispatcher received a signal.
Explanation: An unexpected reply was received from
Response: If this is a tracking event, no service actions
a daemon.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D510 B181D510
Explanation: Unable to create the dispatcher thread.
B181D605 B181D605
Response: If this is a tracking event, no service actions
Explanation: A function call failed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D521 B181D521
Explanation: An IPMI command timed out.
B181D606 B181D606
Response: If this is a tracking event, no service actions
Explanation: A function call failed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D5FF B181D5FF
Explanation: An unrecognized IPMI command was
encountered.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
470 System reference codes (Bxxx)
B181D607 • B181D615
B181D607 B181D607 B181D60E B181D60E
Explanation: Failed to synchronize with a daemon. Explanation: The input parameters were not valid.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D608 B181D608 B181D60F B181D60F
Explanation: Failed to create the network client Explanation: Failed to lock a thread mutex.
address object.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D610 B181D610
B181D609 B181D609
Explanation: Failed to unlock a thread mutex.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D611 B181D611
B181D60B B181D60B
Explanation: Failed to initialize a mutex.
Explanation: Failed to establish the listening queue on
Response: If this is a tracking event, no service actions
the network server address.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181D612 B181D612
Explanation: A function call failed.
B181D60C B181D60C
Response: If this is a tracking event, no service actions
Explanation: Failed to bind the network server
are required. Otherwise, use the FRU and procedure
address.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D614 B181D614
actions.
Explanation: Failed to initialize a condition.
B181D60D B181D60D Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to create the network server
callouts detailed with the SRC to determine service
address object.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181D615 B181D615
callouts detailed with the SRC to determine service
actions. Explanation: A function call failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 471
B181D617 • B181D627
B181D617 B181D617 B181D61E B181D61E
Explanation: A partition dump request failed. Explanation: An unexpected maximum resource ID
(RID) was received.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D618 B181D618
B181D621 B181D621
Explanation: A function call failed.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D619 B181D619
B181D622 B181D622
Explanation: A function call failed.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D61A B181D61A
B181D623 B181D623
Explanation: A function call failed.
Explanation: Failed to create an event thread.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D61B B181D61B
B181D625 B181D625
Explanation: Unable to find the LED access record for
the requested LED. Explanation: A function call failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D61C B181D61C B181D626 B181D626
Explanation: Failed to drive an LED with the drive Explanation: An unrecognized event was received.
LED function.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181D627 B181D627
B181D61D B181D61D
Explanation: Failed to read a registry variable.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
472 System reference codes (Bxxx)
B181D628 • B181D638
B181D628 B181D628 B181D630 B181D630
Explanation: Failed to read the current state data. Explanation: A function call failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D629 B181D629 B181D633 B181D633
Explanation: Failed to read the current power state. Explanation: The initial attempt to submit "press"
control blocks failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D62A B181D62A
B181D634 B181D634
Explanation: Failed to open an engine on a device.
Explanation: Failure when waiting for the control
Response: If this is a tracking event, no service actions
blocks to complete.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D62B B181D62B
Explanation: Failed to write to the general purpose
B181D635 B181D635
(GP) I/O pin.
Explanation: An attempt to submit control blocks
Response: If this is a tracking event, no service actions
failed.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D62C B181D62C
Explanation: Failed to close the general purpose (GP)
B181D637 B181D637
I/O engine.
Explanation: Unable to set the pins to an
Response: If this is a tracking event, no service actions
unconfigured mode.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181D62D B181D62D
Explanation: Unable to create a context.
B181D638 B181D638
Response: If this is a tracking event, no service actions
Explanation: Unable to set the button debounce
are required. Otherwise, use the FRU and procedure
interval
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181D62F B181D62F
actions.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 473
B181D639 • B181E007
B181D639 B181D639 B181E002 B181E002
Explanation: Unable to configure the power good Explanation: Phone numbers for call home are not
(pgood) register. programmed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181D63A B181D63A B181E003 B181E003
Explanation: A function reported a failure. Explanation: Missing information in set up panel for
customer pager.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D63B B181D63B
B181E004 B181E004
Explanation: A function call failed.
Explanation: Dialing the customer pager failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D63C B181D63C
B181E005 B181E005
Explanation: Unable to determine if a power lock is
being held or not. Explanation: Missing account information in call
home setup.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181D63D B181D63D
B181E006 B181E006
Explanation: The general purpose (GP) I/O device
that the control (operator) panel did not show up Explanation: Missing information in the modem setup
within the allotted time panels. Make sure all fields are filled in.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E001 B181E001 B181E007 B181E007
Explanation: The snoop string was found. Explanation: Internal software error; the daemon
process failed to start.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
474 System reference codes (Bxxx)
B181E008 • B181E017
B181E008 B181E008 B181E010 B181E010
Explanation: Internal software error. Explanation: Internal software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E009 B181E009 B181E011 B181E011
Explanation: Internal software error Explanation: Internal software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E00A B181E00A B181E012 B181E012
Explanation: A child process failed. Explanation: Internal software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E00B B181E00B B181E014 B181E014
Explanation: Internal software error. Explanation: Internal software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E00C B181E00C B181E015 B181E015
Explanation: Internal software error; the call home Explanation: Internal software error; communications
process received a signal that was not handled. failure with service center.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E00D B181E00D B181E016 B181E016
Explanation: Internal software error; a process Explanation: Socket connection to service center
received a signal that was not handled. failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E00E B181E00E B181E017 B181E017
Explanation: Internal software error Explanation: Internal software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 475
B181E01E • B181E10A
B181E01E B181E01E B181E101 B181E101
Explanation: The customer initated a call home test. Explanation: The snoop string was found in the input
data; a system reboot has been requested.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181E105 B181E105
actions.
Explanation: Failed to write to a general purpose I/O
(GPIO) pin.
B181E01F B181E01F
Explanation: Call home test initiated by test methods. B181E106 B181E106
Response: If this is a tracking event, no service actions Explanation: An invalid return code was received
are required. Otherwise, use the FRU and procedure when opening the serial device used for UPS detection.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E020 B181E020 actions.
Explanation: Internal software error; process failed to
start. B181E107 B181E107
Response: If this is a tracking event, no service actions Explanation: Communication error with serial port;
are required. Otherwise, use the FRU and procedure unable to open the UART device.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E025 B181E025 actions.
Explanation: Internal software error.
B181E108 B181E108
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Internal software error communicating
callouts detailed with the SRC to determine service with the serial port.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E026 B181E026 callouts detailed with the SRC to determine service
actions.
Explanation: Internal software error
Response: If this is a tracking event, no service actions
B181E109 B181E109
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Internal hardware error while trying to
actions. clear the DTR signal on serial port 1 (while attempting
UPS detection).
B181E027 B181E027 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Communications problem with modem.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E10A B181E10A
actions.
Explanation: Internal hardware error while trying to
set the DTR signal on serial port 1 (while attempting
B181E028 B181E028
UPS detection).
Explanation: Internal software error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
476 System reference codes (Bxxx)
B181E201 • B181E31B
B181E201 B181E201 B181E30C B181E30C
Explanation: Error occurred during reboot attempt. Explanation: The LED control firmware was busy
handling another request; the semaphore was locked.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E202 B181E202
B181E30E B181E30E
Explanation: An error was received while waiting for
the secondary service processor to terminate. Explanation: Internal software error.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E203 B181E203 B181E311 B181E311
Explanation: There was a failure when reading the Explanation: Internal software error.
registry.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E312 B181E312
B181E204 B181E204
Explanation: Internal software error.
Explanation: There was a failure when reading the
Response: If this is a tracking event, no service actions
registry.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E315 B181E315
Explanation: The system power control network
B181E205 B181E205
(SPCN) command was retried, and failed again.
Explanation: RBOT was told to power the system
Response: If this is a tracking event, no service actions
back on, but the power wasn't off.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E319 B181E319
Explanation: The system power control network
B181E304 B181E304
(SPCN) command was retried, and failed again.
Explanation: Internal software error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E31B B181E31B
Explanation: Internal software error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 477
B181E31C • B181E436
callouts detailed with the SRC to determine service
B181E427 B181E427
actions.
Explanation: An attempt to accept a client request
failed.
B181E31C B181E31C
Response: If this is a tracking event, no service actions
Explanation: The system power control network
are required. Otherwise, use the FRU and procedure
(SPCN) command to collect the LED data did not
callouts detailed with the SRC to determine service
return any data.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E428 B181E428
callouts detailed with the SRC to determine service
actions. Explanation: An attempt to receive a client message
failed.
B181E31D B181E31D Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The system power control network
callouts detailed with the SRC to determine service
(SPCN) command to control the physical attention LED
actions.
failed. The LED and the NVRAM could be out of sync.
Response: If this is a tracking event, no service actions
B181E429 B181E429
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: A command failed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E31E B181E31E callouts detailed with the SRC to determine service
actions.
Explanation: The data transferred from the hypervisor
was incomplete. The data that was returned has been
truncated for some unknown reason. B181E42F B181E42F
Response: If this is a tracking event, no service actions Explanation: Unable to synchronize; another instance
are required. Otherwise, use the FRU and procedure of surveillance is already running.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E411 B181E411 actions.
Explanation: SURVserver daemon received a
unexpected signal B181E430 B181E430
Response: If this is a tracking event, no service actions Explanation: Failure when creating a thread.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B181E425 B181E425
Explanation: Failed to initialize a thread attribute. B181E432 B181E432
Response: If this is a tracking event, no service actions Explanation: A system call failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B181E426 B181E426
Explanation: Failed to initialize a thread attribute. B181E436 B181E436
Response: If this is a tracking event, no service actions Explanation: An error occurred.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
478 System reference codes (Bxxx)
B181E437 • B181E443
callouts detailed with the SRC to determine service
B181E43E B181E43E
actions.
Explanation: An event signal error was received.
B181E437 B181E437 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when connecting to a
callouts detailed with the SRC to determine service
daemon.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E43F B181E43F
callouts detailed with the SRC to determine service
actions. Explanation: An error occurred when attempting to
write a registry value.
B181E438 B181E438 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when sending and
callouts detailed with the SRC to determine service
receiving data from a daemon.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E440 B181E440
callouts detailed with the SRC to determine service
actions. Explanation: An error occurred when attempting to
read a registry value.
B181E439 B181E439 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when trying to
callouts detailed with the SRC to determine service
synchronize with an internal firmware server.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E441 B181E441
callouts detailed with the SRC to determine service
actions. Explanation: An error was returned from the mailbox
function when attempting to notify the hypervisor of a
change in a status flag.
B181E43B B181E43B
Response: If this is a tracking event, no service actions
Explanation: Unable to close the client socket.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E442 B181E442
Explanation: A function received an invalid client
B181E43C B181E43C
name.
Explanation: An error occurred when attempting to
Response: If this is a tracking event, no service actions
close a socket.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E443 B181E443
Explanation: A function received an invalid client
B181E43D B181E43D
type.
Explanation: Unable to read a value.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 479
B181E444 • B181E45D
B181E444 B181E444 B181E451 B181E451
Explanation: Unable to flatten the error log; unable to Explanation: A function call failed.
send the error log to the client.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E453 B181E453
B181E445 B181E445
Explanation: An attempt to bind the listening address
Explanation: An error occurred when attempting to failed.
extract flattened error data.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E454 B181E454
B181E446 B181E446
Explanation: An attempt to listen in failed.
Explanation: The client gateway was not able to
Response: If this is a tracking event, no service actions
communicate with the primary service processor (or
are required. Otherwise, use the FRU and procedure
system controller).
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E455 B181E455
actions.
Explanation: An attempt to open a directory failed.
B181E448 B181E448 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to create the gateway address to
callouts detailed with the SRC to determine service
send the surveillance heartbeat to the primary service
actions.
processor (or system controller).
Response: If this is a tracking event, no service actions
B181E458 B181E458
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The reason for this error is stored in the
actions. userdata1 portion of the error log entry.
Response: If this is a tracking event, no service actions
B181E449 B181E449 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: A function call failed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E45B B181E45B
callouts detailed with the SRC to determine service
actions. Explanation: An error occurred when creating an
address.
B181E44A B181E44A Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred when sending data.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E45D B181E45D
actions.
Explanation: An error was found in an address object.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
480 System reference codes (Bxxx)
B181E466 • B181E501
callouts detailed with the SRC to determine service
B181E46E B181E46E
actions.
Explanation: A call to a function failed.
B181E466 B181E466 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: rdal_psi_open call failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E46F B181E46F
actions.
Explanation: A call to a function failed.
B181E467 B181E467 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: rdal_psi_wait call failed
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E470 B181E470
actions.
Explanation: Opening a function failed.
B181E468 B181E468 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E471 B181E471
actions.
Explanation: rdal_psi_close failed.
B181E469 B181E469 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A call to a function failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E472 B181E472
actions.
Explanation: rdal_mbx_close failed.
B181E46B B181E46B Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Indicates that the adal_base_ffdc_wait for
callouts detailed with the SRC to determine service
the FSI mailbox device returned an error.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E473 B181E473
callouts detailed with the SRC to determine service
actions. Explanation: There was a PSI ADAL
first-failure-data-capture unlock failure.
B181E46C B181E46C Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: There was an FSI surveillance failure.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E501 B181E501
actions.
Explanation: There was a hardware-detected problem
due to the service processor firmware.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 481
B181E504 • B181E60A
B181E504 B181E504 B181E602 B181E602
Explanation: A hardware failure was detected in the Explanation: Unable to lock the sinkfile.
central electronics complex (CEC).
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E604 B181E604
B181E540 B181E540
Explanation: netcSendRecv returned error.
Explanation: There was a failure most likely
Response: If this is a tracking event, no service actions
attributable to the service processor firmware, but it
are required. Otherwise, use the FRU and procedure
could also be software-related or require further
callouts detailed with the SRC to determine service
support.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E606 B181E606
callouts detailed with the SRC to determine service
actions. Explanation: An invalid major op was recieved from
the service tags.
B181E550 B181E550 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: There was a service processor firmware
callouts detailed with the SRC to determine service
problem, but it could also be hardware-related or
actions.
require further support.
Response: If this is a tracking event, no service actions
B181E607 B181E607
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Error while attempting to create a
actions. listening socket.
Response: If this is a tracking event, no service actions
B181E560 B181E560 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The hardware detected a problem that
actions.
was caused by the service processor firmware. The
dump that was taken may need to be analyzed.
B181E608 B181E608
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Error returned by netsSend call.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E580 B181E580 actions.
Explanation: There was a failure in the service
processor firmware. B181E609 B181E609
Response: If this is a tracking event, no service actions Explanation: rmgrd application failed during a fork()
are required. Otherwise, use the FRU and procedure call.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E601 B181E601 actions.
Explanation: Error while attempting read the registry.
B181E60A B181E60A
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: The system call to initialize the thread
callouts detailed with the SRC to determine service parameters failed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
482 System reference codes (Bxxx)
B181E60B • B181E617
callouts detailed with the SRC to determine service
B181E611 B181E611
actions.
Explanation: The NectSendRecv call returned an error
when communicating with the rmgrd daemon.
B181E60B B181E60B
Response: If this is a tracking event, no service actions
Explanation: A system call to initialize thread
are required. Otherwise, use the FRU and procedure
parameters failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E612 B181E612
actions.
Explanation: The netcClose call failed.
B181E60C B181E60C Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A system call to create a posix thread
callouts detailed with the SRC to determine service
failed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E613 B181E613
callouts detailed with the SRC to determine service
actions. Explanation: Synchronization with server call failed.
Response: If this is a tracking event, no service actions
B181E60D B181E60D are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An error was returned a function call.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E614 B181E614
callouts detailed with the SRC to determine service
actions. Explanation: A call to bind returned an error.
Response: If this is a tracking event, no service actions
B181E60E B181E60E are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An error occurred when creating a
actions.
message queue.
Response: If this is a tracking event, no service actions
B181E615 B181E615
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: Listen call failed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E60F B181E60F callouts detailed with the SRC to determine service
actions.
Explanation: An invalid component type was received
when attempting to create a handler thread.
B181E616 B181E616
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: Error returned by netsConnectServer().
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions
actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E610 B181E610 actions.
Explanation: Error returned by netcConnect call.
B181E617 B181E617
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Explanation: The rmgrd daemon received a
callouts detailed with the SRC to determine service unexpected signal.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 483
B181E618 • B181E623
B181E618 B181E618 B181E61E B181E61E
Explanation: An error was encountered while Explanation: An error was returned from the
initializing mutex. initialization routine.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E619 B181E619 B181E61F B181E61F
Explanation: Error encountered while locking mutex. Explanation: An error was returned from spawning a
thread.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E61A B181E61A
B181E620 B181E620
Explanation: Error encountered while unlocking
mutex. Explanation: An invalid operation request was made
to the data correlation handler.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E61B B181E61B
B181E621 B181E621
Explanation: Error returned by netsClose call.
Explanation: An error was returned from initthread.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E61C B181E61C
B181E622 B181E622
Explanation: The daemon encountered an error while
attempting to return error log data. Explanation: An error was returned from the function
call to set the service processor role to primary.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E61D B181E61D
B181E623 B181E623
Explanation: An unknown minor operation id
received. Explanation: An error was returned from a function
call.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
484 System reference codes (Bxxx)
B181E624 • B181E630
B181E624 B181E624 B181E62B B181E62B
Explanation: A function call failed. Explanation: Error while attempting write the registry.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E625 B181E625 B181E62C B181E62C
Explanation: An invalid thread type has been sent by Explanation: Error while writing to the file.
the caller.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E62D B181E62D
B181E626 B181E626
Explanation: A data correlation command can only be
Explanation: A function call failed. issued by the secondary service processor (or system
controller).
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E627 B181E627
B181E62E B181E62E
Explanation: A non-existent registry variable was sent.
Explanation: Function returned error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E628 B181E628
B181E62F B181E62F
Explanation: The file that was requested for
synchronization does not exist. Explanation: An error was returned when the primary
service processor (or system controller) attempted to
Response: If this is a tracking event, no service actions
retrieve it's system firmware module level information.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181E629 B181E629
Explanation: Error attempting to open file for reading.
B181E630 B181E630
Response: If this is a tracking event, no service actions
Explanation: An error was returned when finding the
are required. Otherwise, use the FRU and procedure
size of a registry.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E62A B181E62A
actions.
Explanation: Error returned when reading a file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 485
B181E631 • B181E64B
B181E631 B181E631 B181E637 B181E637
Explanation: An error was returned when attempting Explanation: An error was returned a function call.
to read the size of the data key.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E638 B181E638
B181E632 B181E632
Explanation: An error was returned from the function
Explanation: An error was returned from the retrieving the redundancy value.
discovery function retrieving the FSI state.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E639 B181E639
B181E633 B181E633
Explanation: An error was returned from the function
Explanation: An error was returned when attempting retrieving the sibling service processor's state.
to create the event handler object.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E63A B181E63A
B181E634 B181E634
Explanation: An error was returned from the function
Explanation: An invalid event ID was received; retrieving the service processor position.
notification cannot be done.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E64A B181E64A
B181E635 B181E635
Explanation: An invalid operation requested a
Explanation: An error was encountered when function.
attempting to signal a service processor role change
Response: If this is a tracking event, no service actions
event.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E64B B181E64B
Explanation: The primary and secondary service
B181E636 B181E636
processors (or system controllers) do not have the same
Explanation: An error was returned from the function system firmware loaded.
retrieving the current service processor role.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
486 System reference codes (Bxxx)
B181E64C • B181E658
B181E64C B181E64C B181E653 B181E653
Explanation: An error was returned when attempting Explanation: An error occurred when writing a
to restore a flattened error log. registry value.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E64D B181E64D B181E654 B181E654
Explanation: An error occurred when unflattening the Explanation: An error was returned from a function
log sent by the primary service processor (or system call.
controller).
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E655 B181E655
B181E64F B181E64F
Explanation: An error was returned when attempting
Explanation: An administrative failover request was to create an event handler object.
sent to the service processor (or system controller) that
Response: If this is a tracking event, no service actions
did not have the primary role; the request was rejected.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E656 B181E656
Explanation: An error was returned from a function
B181E650 B181E650
call.
Explanation: An error was encountered when
Response: If this is a tracking event, no service actions
beginning an administrative failover at standby.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E657 B181E657
Explanation: An error was returned from a function
B181E651 B181E651
call.
Explanation: An error occurred when writing a
Response: If this is a tracking event, no service actions
registry value.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E658 B181E658
Explanation: This indicates the requested action failed
B181E652 B181E652
because the sibling service processor is not in the
Explanation: A network receiving operation from the working state.
sibling service processor failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 487
B181E659 • B181E664
B181E659 B181E659 B181E65F B181E65F
Explanation: plckIPLRequest call to initiate an Explanation: An invalid time-out was specified.
administrative failover at standby returned an error.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E660 B181E660
B181E65A B181E65A
Explanation: The system's state does not allow
Explanation: An error was returned from a function failover to be initiated.
call.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E661 B181E661
B181E65B B181E65B
Explanation: An error was returned when an
Explanation: The state manager did not return a valid operation was requested on the sibling service
failover type to be used. processor (or system controller).
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E65C B181E65C B181E662 B181E662
Explanation: A surveillance failure of the primary Explanation: smgrInitiateToolReset() call returned an
service processor (or system controller) was detected at error.
pre-standby.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E663 B181E663
B181E65D B181E65D
Explanation: A failover readiness check was
Explanation: Redundancy cannot be enabled because requested.
the secondary service processor is not at standby.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E664 B181E664
B181E65E B181E65E
Explanation: A forced termination and failover
Explanation: A command line option was incorrectly operation is requested.
removed or added.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
488 System reference codes (Bxxx)
B181E665 • B181E684
B181E665 B181E665 B181E66D B181E66D
Explanation: The attempt to terminate the service Explanation: An administrative failover request was
processor and failover failed. received from the primary service processor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E666 B181E666 B181E66F B181E66F
Explanation: smgrFspIplTypeRequest() returned error Explanation: An emergency failover is being
on a IPL request. performed by the secondary service processor. The
hypervisor requested the failover after resetting the
Response: If this is a tracking event, no service actions
primary service processor, or the primary service
are required. Otherwise, use the FRU and procedure
processor terminated due to a failure.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E667 B181E667
actions.
Explanation: An invalid IPL type was requested.
Response: If this is a tracking event, no service actions B181E672 B181E672
are required. Otherwise, use the FRU and procedure
Explanation: Call to fspinit_do_transition failed.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E669 B181E669
actions.
Explanation: An error was returned from a function
call.
B181E673 B181E673
Response: If this is a tracking event, no service actions
Explanation: A failover was requested when another
are required. Otherwise, use the FRU and procedure
was already in progress.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E66B B181E66B
actions.
Explanation: The redundancy manager is determining
the type of error that occurred during an administrative
B181E679 B181E679
fail-over.
Explanation: An invalid operation requested the
Response: If this is a tracking event, no service actions
rconUtil function.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181E66C B181E66C
Explanation: Informational message: the primary
B181E684 B181E684
service processor is performing an administrative
failover to the secondary service processor. Explanation: The secondary service processor returned
an error when starting to implement an administrative
Response: If this is a tracking event, no service actions
failover.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 489
B181E685 • B181E6A5
B181E685 B181E685 B181E68F B181E68F
Explanation: A failover block request was received. Explanation: The last known state of the primary
service processor was runtime, and the secondary is not
Response: If this is a tracking event, no service actions
at runtime.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181E686 B181E686
Explanation: A request to unblock a failover was
B181E693 B181E693
received.
Explanation: The synchronization of a nonexistent file
Response: If this is a tracking event, no service actions
was requested.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181E687 B181E687
Explanation: An error was encountered when sending
B181E694 B181E694
data to stop a message service of an HMC that is
failing. Explanation: The synchronization of a nonexistent
registry was requested
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E689 B181E689
B181E69E B181E69E
Explanation: Sibling returned an error on the
requested operation. Explanation: Surveillance communication with the
sibling service processor failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E68B B181E68B
B181E6A2 B181E6A2
Explanation: The secondary service processor (or
system controller) was asked to initiate a reset/reload. Explanation: rmgrremote daemon received an
unexpected signal.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E68D B181E68D
B181E6A5 B181E6A5
Explanation: A call to the function that switches from
one service processor to the other failed. Explanation: An operational error occurred on the
secondary service processor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
490 System reference codes (Bxxx)
B181E6A8 • B181E6C6
B181E6A8 B181E6A8 B181E6B0 B181E6B0
Explanation: SYNC should not have been called by Explanation: Failed to connect to the sibling service
the secondary service processor. processor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E6AB B181E6AB B181E6B1 B181E6B1
Explanation: The caller specified a non-existent target Explanation: Failure while attempting to send a
component. request to the sibling service processor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E6AC B181E6AC B181E6B2 B181E6B2
Explanation: Timed out waiting for a response from Explanation: rmgrUtilSync was called by a function
the sibling service processor. other than util.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E6AD B181E6AD B181E6B3 B181E6B3
Explanation: A n error was returned from a function Explanation: The position of the service processor has
call. not yet been determined; the mailbox cannot be
configured.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E6AE B181E6AE
B181E6BB B181E6BB
Explanation: An error was returned from a function
call. Explanation: Inforomational log entry: redundancy is
enabled.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E6AF B181E6AF
B181E6C6 B181E6C6
Explanation: Attempts to connect to the sibling service
processor failed on all links. Explanation: A function call during redundancy
enablement was rejected.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 491
B181E6C7 • B181E6E3
B181E6C7 B181E6C7 B181E6D9 B181E6D9
Explanation: An emergency service processor fail-over Explanation: An attempt was made to write a registry
(EFO) was requested when the system was in the key or file to the secondary service processor, which is
transitory state. This will cause termination of the an invalid operation.
secondary service processor first, then failover will
Response: If this is a tracking event, no service actions
begin.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E6DE B181E6DE
Explanation: An error was returned from a remote
B181E6C9 B181E6C9
deletion request
Explanation: Failover has been unblocked.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E6DF B181E6DF
B181E6CA B181E6CA
Explanation: No clock signals were detected on the
Explanation: Service processor failover is not sibling service processor's link.
supported in this system.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E6E1 B181E6E1
B181E6CF B181E6CF
Explanation: A hidden service processor error log
Explanation: An error was returned by guard when entry to help correlate with the dump will be generated
attempting to deconfigure the secondary service due to the recovery action.
processor.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E6E2 B181E6E2
B181E6D1 B181E6D1
Explanation: A stream was reqested on a file that is
Explanation: An administrative failover to the on the synchronization list.
secondary service processors not allowed at this time
Response: If this is a tracking event, no service actions
due to the state of the system.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E6E3 B181E6E3
Explanation: A call to dlsym() failed.
B181E6D4 B181E6D4
Response: If this is a tracking event, no service actions
Explanation: An error was returned from util when
are required. Otherwise, use the FRU and procedure
closing a file.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
492 System reference codes (Bxxx)
B181E6E4 • B181E705
B181E6E4 B181E6E4 B181E6ED B181E6ED
Explanation: An error was returned from Explanation: Service processor (or system controller)
utilfile.sync(). redundancy is disabled.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E6E7 B181E6E7 B181E6F1 B181E6F1
Explanation: A dumpForceSync call was made during Explanation: A persistant event timeout occurred.
a request to enable redundancy.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E702 B181E702
B181E6E8 B181E6E8
Explanation: An undefined error was returned when
Explanation: An error was returned from a function generating statistics on what should be a directory.
call.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E703 B181E703
B181E6E9 B181E6E9
Explanation: An error was returned from util when
Explanation: The secondary service processor (or opening a file.
system controller) was unable to communicate with the
Response: If this is a tracking event, no service actions
primary service processor (or system controller) for
are required. Otherwise, use the FRU and procedure
longer than one hour, and initiated a service processor
callouts detailed with the SRC to determine service
failover to assume system management.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E704 B181E704
callouts detailed with the SRC to determine service
actions. Explanation: An error was returned from util when
opening a file.
B181E6EB B181E6EB Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The notification was rejected.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E705 B181E705
actions.
Explanation: An error was returned from util when
checking to see if a file exists.
B181E6EC B181E6EC
Response: If this is a tracking event, no service actions
Explanation: A function call was rejected during
are required. Otherwise, use the FRU and procedure
redundancy enablement.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 493
B181E706 • B181E712
B181E706 B181E706 B181E70D B181E70D
Explanation: An error was returned from deleting a Explanation: An error was returned from a directory
file. synchronization call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E707 B181E707 B181E70E B181E70E
Explanation: An error was returned from util when Explanation: An error was returned from a file
opening a file. synchronization call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E708 B181E708 B181E70F B181E70F
Explanation: An undefined minor operation was Explanation: An error was returned from a registry
found. synchronization call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E709 B181E709 B181E710 B181E710
Explanation: An error was returned from util when Explanation: An error was returned from a send data
writing a file. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E70B B181E70B B181E711 B181E711
Explanation: The p3 registry does not exist. Explanation: An error occurred when opening a file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E70C B181E70C B181E712 B181E712
Explanation: An error was returned when checking Explanation: An error occurred when opening a file.
the redundancy policy.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
494 System reference codes (Bxxx)
B181E713 • B181E71F
callouts detailed with the SRC to determine service
B181E713 B181E713
actions.
Explanation: An error was returned from a function
call.
B181E71A B181E71A
Response: If this is a tracking event, no service actions
Explanation: An unsupported element was
are required. Otherwise, use the FRU and procedure
encountered during a directory synchronization.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E714 B181E714
actions.
Explanation: An error occurred when closing a file.
Response: If this is a tracking event, no service actions B181E71B B181E71B
are required. Otherwise, use the FRU and procedure
Explanation: A n error was returned from a function
callouts detailed with the SRC to determine service
call.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E715 B181E715
callouts detailed with the SRC to determine service
Explanation: Unable to pack the registry into an actions.
empty buffer.
Response: If this is a tracking event, no service actions B181E71C B181E71C
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned from a system
callouts detailed with the SRC to determine service
call.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E716 B181E716
callouts detailed with the SRC to determine service
Explanation: A function call failed. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181E71D B181E71D
callouts detailed with the SRC to determine service
Explanation: An error was returned from a stream
actions.
synchronization call.
Response: If this is a tracking event, no service actions
B181E717 B181E717
are required. Otherwise, use the FRU and procedure
Explanation: A function call failed. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181E71E B181E71E
actions.
Explanation: An error was returned from a function
call.
B181E718 B181E718
Response: If this is a tracking event, no service actions
Explanation: There was an error when reading a are required. Otherwise, use the FRU and procedure
directory entry. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181E71F B181E71F
actions.
Explanation: An error was returned from a function
call.
B181E719 B181E719
Response: If this is a tracking event, no service actions
Explanation: A function call failed on a directory are required. Otherwise, use the FRU and procedure
entry. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 495
B181E720 • B181E72B
B181E720 B181E720 B181E726 B181E726
Explanation: An attempt was made to pack data into Explanation: A request was made to synchronize a file
a butter that was not empty. that exceeds the maximum buffer size.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E721 B181E721 B181E727 B181E727
Explanation: An error was returned from a function Explanation: An error was returned from a function
call. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E722 B181E722 B181E728 B181E728
Explanation: An attempt was made to pack data into Explanation: An error was returned from a function
a butter that was not big enough for the data. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E723 B181E723 B181E729 B181E729
Explanation: An attempt was made to append fewer Explanation: An error was returned from a function
than zero, or zero, bytes to a buffer. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E724 B181E724 B181E72A B181E72A
Explanation: An attempt was made to pack a registry Explanation: An error was returned from a function
of an invalid size. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E725 B181E725 B181E72B B181E72B
Explanation: A request was made to sync a file that Explanation: An error was returned from a function
exceeds the maximum buffer size. call.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
496 System reference codes (Bxxx)
B181E72C • B181E739
B181E72C B181E72C B181E733 B181E733
Explanation: An error was returned from rolling the Explanation: A function call failed.
buffer.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E734 B181E734
B181E72D B181E72D
Explanation: A function call failed.
Explanation: The space allocated for the file data does
Response: If this is a tracking event, no service actions
not equal the amount of file data to transfer.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E735 B181E735
Explanation: A function call failed.
B181E72E B181E72E
Response: If this is a tracking event, no service actions
Explanation: A function call failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E736 B181E736
Explanation: A function call failed.
B181E72F B181E72F
Response: If this is a tracking event, no service actions
Explanation: A function call failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E737 B181E737
Explanation: A function call failed.
B181E730 B181E730
Response: If this is a tracking event, no service actions
Explanation: A function call failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181E738 B181E738
Explanation: An error occurred when trying to create
B181E731 B181E731
a directory.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E739 B181E739
B181E732 B181E732
Explanation: An attempt was made to synchronize a
Explanation: A function call failed. directory with something that isn't a directory.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 497
B181E73A • B181E745
B181E73A B181E73A B181E740 B181E740
Explanation: An error was returned from a p3 registry Explanation: A function call failed.
comparison.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E741 B181E741
B181E73B B181E73B
Explanation: An error was returned from the call to
Explanation: An error was returned from a p3 registry delete t he directory contents.
comparison.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E742 B181E742
B181E73C B181E73C
Explanation: An error occurred when trying to delete
Explanation: An error was returned when writing to a directory.
the registry.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E743 B181E743
B181E73D B181E73D
Explanation: An error was returned from a function
Explanation: An error was returned from a function call.
call.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E744 B181E744
B181E73E B181E73E
Explanation: An undefined error was returned when
Explanation: An error was returned from a function generating statistics on what should be a directory.
call.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E745 B181E745
B181E73F B181E73F
Explanation: An error was returned from a function
Explanation: An error was returned from a function call.
call.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
498 System reference codes (Bxxx)
B181E746 • B181E801
B181E746 B181E746 B181E7C2 B181E7C2
Explanation: An error was returned when attempting Explanation: The bulk power assembly (BPA) and its
to unlink an element . sibling have the same IP address.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E747 B181E747 B181E7C3 B181E7C3
Explanation: An error was returned from util when Explanation: Unable to open a synchronization file.
attempting to seek.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E7C4 B181E7C4
B181E748 B181E748
Explanation: A function call to lock returned an error.
Explanation: A stream counter overflow occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181E7C7 B181E7C7
B181E7B0 B181E7B0
Explanation: This bulk power assembly (BPA) does
Explanation: An invalid operation code was sent. not have an IP address stored for a sibling BPA for the
synchronization process to use. It is possible that there
Response: If this is a tracking event, no service actions
is no sibling BPA present.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181E7C0 B181E7C0
Explanation: This SRC indicates that the system ran
B181E7FF B181E7FF
for a long time with only one bulk power assembly
(BPA), and a large number of firmware updates were Explanation: An error was injected for debugging
done. Then a sibling BPA was added (or swapped in). purposes.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E7C1 B181E7C1 B181E801 B181E801
Explanation: A type other than time-of-day, HMC Explanation: A failure occurred in a utility register.
password, or CEC name was received.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
(B1xx) Reference codes 499
B181E802 • B181E810
B181E802 B181E802 B181E809 B181E809
Explanation: A synchronization failure occurred. Explanation: A CHIC failure occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E803 B181E803 B181E80A B181E80A
Explanation: A NETS failure occurred. Explanation: An invalid SMA system was found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E804 B181E804 B181E80B B181E80B
Explanation: A thread failure occurred. Explanation: Failed to load and boot the IPC.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E805 B181E805 B181E80C B181E80C
Explanation: A client failure occurred. Explanation: A null pointer was found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E806 B181E806 B181E80E B181E80E
Explanation: A code update (CUPD) failure occurred. Explanation: Failed to start the IPC.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E807 B181E807 B181E80F B181E80F
Explanation: A mailbox (MBOX) failure occurred. Explanation: Failed to perform a reset.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181E808 B181E808 B181E810 B181E810
Explanation: A direct memory access (DMA) failure Explanation: The reset was not valid.
occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
500 System reference codes (Bxxx)
B181E811 • B181E910
B181E811 B181E811 B181E907 B181E907
Explanation: A dump request failed. Explanation: Unable to read the reason for the reset
from the registry.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181E812 B181E812
B181E90A B181E90A
Explanation: The handle was not found.
Explanation: The service processor failed to clear bits
Response: If this is a tracking event, no service actions
in the device immediate status register (DISR).
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181E813 B181E813
Explanation: A dump was unexpectedly invalidated.
B181E90D B181E90D
Response: If this is a tracking event, no service actions
Explanation: The reset/reload function is called with
are required. Otherwise, use the FRU and procedure
an insufficient number of arguments.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181E814 B181E814
actions.
Explanation: A dump utility failure occurred.
Response: If this is a tracking event, no service actions B181E90E B181E90E
are required. Otherwise, use the FRU and procedure
Explanation: An invalid reset/reload routine was
callouts detailed with the SRC to determine service
called.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181E815 B181E815
callouts detailed with the SRC to determine service
Explanation: An event failure occurred. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181E90F B181E90F
callouts detailed with the SRC to determine service
Explanation: An unexpected signal was received when
actions.
reset/reload was running.
Response: If this is a tracking event, no service actions
B181E8FF B181E8FF
are required. Otherwise, use the FRU and procedure
Explanation: Informational message: an informational callouts detailed with the SRC to determine service
error log entry was generated. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181E910 B181E910
callouts detailed with the SRC to determine service
Explanation: The service processor failed to set the
actions.
bits in the device immediate status register (DISR),
which is used to communicate the reset/reload status
B181E902 B181E902 to the system.
Explanation: The service processor firmware was Response: If this is a tracking event, no service actions
unable to get the SRC from the irrecoverable error log. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 501
B181E911 • B181EA0B
B181E911 B181E911 B181EA06 B181EA06
Explanation: A service processor reset/reload Explanation: Failed to get the maximum number of
occurred. The error log for the error that caused the resource IDs (RIDs) for a given field replaceable unit
reset/reload could not be retrieved. Use other (FRU) type.
error/event logs or a service processor dump to gather
Response: If this is a tracking event, no service actions
error information.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181EA07 B181EA07
Explanation: A failure occurred when trying to enable
B181E913 B181E913
a panel.
Explanation: The HMC requested a reset/reload to
Response: If this is a tracking event, no service actions
termination.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181EA08 B181EA08
Explanation: There was a failure in the hardware
B181EA01 B181EA01
object manager (HOM) API.
Explanation: An XREF session entry failure occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EA09 B181EA09
B181EA03 B181EA03
Explanation: There was an RTIM API failure.
Explanation: There was an XREF API failure.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EA0A B181EA0A
B181EA04 B181EA04
Explanation: There was an XREF CCMM internal
Explanation: Failed to read the hypervisor state error.
registry.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EA0B B181EA0B
B181EA05 B181EA05
Explanation: There was an XREF CMD build failure.
Explanation: No CM lock was found.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
502 System reference codes (Bxxx)
B181EA0C • B181EA17
B181EA0C B181EA0C B181EA12 B181EA12
Explanation: There was a failure during concurrent Explanation: The event management component
maintenance recovery. returned an error when the concurrent maintenance
firmware tried to subscribe to the sibling service
Response: If this is a tracking event, no service actions
processor state change event.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181EA0D B181EA0D
Explanation: The concurrent maintenance firmware
B181EA13 B181EA13
encountered an unexpected failure when calling the
mailbox interface to disable the current time-of-day Explanation: No concurrent maintenance capability
topology. was found on the backup.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA0E B181EA0E B181EA14 B181EA14
Explanation: There was an XREF sequence error. Explanation: Unable to guard out the concurrent
maintenance service processor.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EA0F B181EA0F
B181EA15 B181EA15
Explanation: Failed to read a checkpoint; all are in
use. Explanation: The command line parser failed.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA10 B181EA10 B181EA16 B181EA16
Explanation: Failed to read the checkpoint registry. Explanation: A failure occurred when trying to run a
concurrent maintenance xml file.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EA11 B181EA11
B181EA17 B181EA17
Explanation: There was a code version mismatch.
Explanation: Failed to send a progress code.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 503
B181EA18 • B181EA25
B181EA18 B181EA18 B181EA20 B181EA20
Explanation: Failed to read the service processor role Explanation: Unable to convert an RID (resource ID)
from the redundance manager. to a HOM (hardware object manager) unit ID.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA19 B181EA19 B181EA21 B181EA21
Explanation: There was an XREF redundant service Explanation: No environment path was found.
processor failure.
Response: If this is a tracking event, no service actions
Response: Attention: Do not attempt to boot from the are required. Otherwise, use the FRU and procedure
secondary service processor during a concurrent callouts detailed with the SRC to determine service
maintenance operation. If this is a tracking event, no actions.
service actions are required. Otherwise, use the FRU
and procedure callouts detailed with the SRC to
B181EA22 B181EA22
determine service actions.
Explanation: The cross reference (XREF) file was not
found.
B181EA1A B181EA1A
Response: If this is a tracking event, no service actions
Explanation: An abort was detected.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181EA23 B181EA23
Explanation: Informational message: this platform
B181EA1B B181EA1B
does not support concurrent maintenance operations.
Explanation: There was an XREF invalid hardware
Response: If this is a tracking event, no service actions
failure.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181EA24 B181EA24
Explanation: Failure when creating a thread; aborting
B181EA1E B181EA1E
ccmmsrv
Explanation: There was an XREF condition failure.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EA25 B181EA25
B181EA1F B181EA1F
Explanation: The command request had invalid
Explanation: Unable to connect to the concurrent concurrency.
maintenance daemon.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
504 System reference codes (Bxxx)
B181EA26 • B181EA33
B181EA26 B181EA26 B181EA2D B181EA2D
Explanation: Unable to convert the resource ID to the Explanation: Failed to open a handle.
HOM (hardware object manager.) unit ID.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EA2E B181EA2E
B181EA28 B181EA28
Explanation: The concurrent maintenance firmware is
Explanation: Cannot load symbol. isolating the secondary service processor.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA29 B181EA29 B181EA2F B181EA2F
Explanation: While a concurrent maintenance Explanation: Unable to read an error log from the
operation was in progress, an API failure occurred. repository.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA2A B181EA2A B181EA31 B181EA31
Explanation: While a concurrent maintenance backup Explanation: An unhandled signal was received by
isolation operation was in progress, an API failure the concurrent maintenance firmware.
occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EA32 B181EA32
B181EA2B B181EA2B
Explanation: There was an XREF HMC disconnection
Explanation: Failed to open the buddy JTAG device. event.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA2C B181EA2C B181EA33 B181EA33
Explanation: Failed to open the buddy GPIO (general Explanation: This is a generic SRC logged to flag a
purpose I/O) device. recovery action.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 505
B181EA34 • B181EA3F
B181EA34 B181EA34 B181EA3A B181EA3A
Explanation: There was an XREF state change event. Explanation: There was an XREF system reset/reload
event.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EA35 B181EA35
B181EA3B B181EA3B
Explanation: There was an XREF power off event.
Explanation: There was an XREF failover during
Response: If this is a tracking event, no service actions
CMOP.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181EA36 B181EA36
Explanation: There was an attention API failure.
B181EA3C B181EA3C
Response: If this is a tracking event, no service actions
Explanation: The recovery director received a reason
are required. Otherwise, use the FRU and procedure
for recovery that was not recognized.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181EA37 B181EA37
actions.
Explanation: A concurrent maintenance operation was
aborted while the Anchor VPD card was not installed
B181EA3D B181EA3D
in the system.
Explanation: The recovery director received a reason
Response: If this is a tracking event, no service actions
for recovery that was not recognized.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181EA38 B181EA38
Explanation: The system level activation status
B181EA3E B181EA3E
received from the hypervisor was invalid, or indicated
an error. This usually indicates that a hypervisor error Explanation: The utility routime read 0 bytes from the
was detected during a concurrent maintenance service processor's state file.
operation.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EA3F B181EA3F
B181EA39 B181EA39
Explanation: There was no concurrent maintenance
Explanation: The concurrent maintenance firmware capability on the secondary service processor.
detected a ccmmsrv crash and will try to recover.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
506 System reference codes (Bxxx)
B181EA40 • B181EA4E
B181EA40 B181EA40 B181EA47 B181EA47
Explanation: An error occurred when clearing the IPL Explanation: There was a failure in an API.
speed override.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EA48 B181EA48
B181EA41 B181EA41
Explanation: There was a failure in an API.
Explanation: The attempt to unmask the FSI interrupts
Response: If this is a tracking event, no service actions
returned an error.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181EA49 B181EA49
Explanation: There was a failure in an API.
B181EA43 B181EA43
Response: If this is a tracking event, no service actions
Explanation: Failed to retrieve the HMC ID for the
are required. Otherwise, use the FRU and procedure
NCR action.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181EA4A B181EA4A
actions.
Explanation: The timer tick expired.
B181EA44 B181EA44 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: Failed to retrieve the HMC ID for the
callouts detailed with the SRC to determine service
NCR action.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181EA4B B181EA4B
callouts detailed with the SRC to determine service
actions. Explanation: There was a failure in an API.
Response: If this is a tracking event, no service actions
B181EA45 B181EA45 are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: An error occurred when trying to check
actions.
the power save mode.
Response: If this is a tracking event, no service actions
B181EA4C B181EA4C
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The step is done.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181EA46 B181EA46 callouts detailed with the SRC to determine service
actions.
Explanation: There was a failure in an API.
Response: If this is a tracking event, no service actions
B181EA4E B181EA4E
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Explanation: The target CCIN was not found
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 507
B181EA4F • B181EAFF
B181EA4F B181EA4F B181EA7F B181EA7F
Explanation: A registry read failure occurred. Explanation: A timer expired.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA51 B181EA51 B181EA87 B181EA87
Explanation: A time-out occurred while waiting for Explanation: A failure occurred when the secondary
the secondary system controller. service processor (or system controller) was reset.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA53 B181EA53 B181EAFB B181EAFB
Explanation: A PSI failure occurred with the query Explanation: The XML file was skipped.
active.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EAFC B181EAFC
B181EA54 B181EA54
Explanation: A module recovery creation error
Explanation: A failure occurred when disabling the occurred.
PSI link.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EAFE B181EAFE
B181EA55 B181EA55
Explanation: Informational message: A concurrent
Explanation: Rebooting a network controller failed. maintenance operation was started.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EA56 B181EA56 B181EAFF B181EAFF
Explanation: A node instance was found that is not Explanation: Informational message: A concurrent
recognized. maintenance operation was stopped.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
508 System reference codes (Bxxx)
B181EF01 • B181EF0E
B181EF01 B181EF01 B181EF07 B181EF07
Explanation: This error code is reserved. Explanation: An unknown dump content type was
found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EF02 B181EF02
B181EF08 B181EF08
Explanation: An error occurred during a service
processor (or system controller) dump. Explanation: An unsupported copy operation was
attempted.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EF03 B181EF03
B181EF09 B181EF09
Explanation: An error occured while attempting to
determine if a service processor dump exists. Explanation: Null global data was found.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF04 B181EF04 B181EF0A B181EF0A
Explanation: An error occurred during a file I/O Explanation: An error occured while attempting to
operation. denote a completed service processor dump as valid.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF05 B181EF05 B181EF0D B181EF0D
Explanation: A dump operation was attempted that Explanation: An error occured while attempting to
violated the dump policy. access a file.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF06 B181EF06 B181EF0E B181EF0E
Explanation: Failed to obtain or release a lock. Explanation: An error occurred when the service
processor attempted to notify the operating system that
Response: If this is a tracking event, no service actions
a service processor dump had been deleted.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 509
B181EF0F • B181EF28
B181EF0F B181EF0F B181EF16 B181EF16
Explanation: An error occurred when the service Explanation: An internal service procssor operation
processor attempted to notify the operating system that failed.
a service processor dump occurred.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EF17 B181EF17
B181EF10 B181EF10
Explanation: An internal service procssor operation
Explanation: An error occurred during a file I/O failed.
operation on a pipe.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EF1A B181EF1A
B181EF11 B181EF11
Explanation: An error occurred while attempting to
Explanation: An operation on a lock for a dump display a new progress code on the operator panel.
operation failed.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EF1F B181EF1F
B181EF12 B181EF12
Explanation: An error occurred while attempting to
Explanation: A system error was received. enable the service processor dump feature.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF13 B181EF13 B181EF26 B181EF26
Explanation: Informational message: The dump Explanation: An error occurred.
storage file system was formatted.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EF28 B181EF28
B181EF14 B181EF14
Explanation: An error occurred.
Explanation: Failed to write to the control (operator)
Response: If this is a tracking event, no service actions
panel.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
510 System reference codes (Bxxx)
B181EF2B • B181EF42
B181EF2B B181EF2B B181EF34 B181EF34
Explanation: An error occurred. Explanation: An error occurred while collecting a
service processor dump.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EF2D B181EF2D
B181EF36 B181EF36
Explanation: An error occurred while attempting to
notify the HMC that a service processor dump Explanation: An error occurred while collecting a
occurred. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF2E B181EF2E B181EF38 B181EF38
Explanation: An error occurred while attempting to Explanation: An error occurred.
notify the HMC that a service processor dump
Response: If this is a tracking event, no service actions
occurred.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181EF3E B181EF3E
Explanation: An error occurred while attempting to
B181EF2F B181EF2F
determine if the service processor dump feature is
Explanation: An error occurred while attempting to enabled.
notify the HMC that a service processor dump
Response: If this is a tracking event, no service actions
occurred.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181EF3F B181EF3F
Explanation: An error occurred while attempting to
B181EF32 B181EF32
determine if the service processor dump feature is
Explanation: An error occurred. enabled.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF33 B181EF33 B181EF42 B181EF42
Explanation: An error occurred. Explanation: An error occurred while collecting a
service processor dump.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 511
B181EF44 • B181EF56
B181EF44 B181EF44 B181EF4C B181EF4C
Explanation: An error occurred while collecting a Explanation: An error occurred while collecting a
service processor dump. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF45 B181EF45 B181EF4D B181EF4D
Explanation: An error occurred while collecting a Explanation: An error occurred while collecting a
service processor dump. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF46 B181EF46 B181EF52 B181EF52
Explanation: Dump files were deleted before they Explanation: An error occurred while collecting a
were captured in the dump. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF47 B181EF47 B181EF53 B181EF53
Explanation: An error occurred while collecting a Explanation: An error occurred.
service processor dump.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EF54 B181EF54
B181EF4A B181EF4A
Explanation: The service processor dump failed
Explanation: An error occurred while collecting a because there was not enough room left to store it.
service processor dump.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181EF56 B181EF56
B181EF4B B181EF4B
Explanation: An error occurred while processing a
Explanation: An error occurred while collecting a dump file
service processor dump.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
512 System reference codes (Bxxx)
B181EF5A • B181EF6A
B181EF5A B181EF5A B181EF62 B181EF62
Explanation: An error occurred while attempting to Explanation: A service processor dump operation did
determine the name of a service processor dump. not complete
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF5B B181EF5B B181EF65 B181EF65
Explanation: An error occurred while attempting to Explanation: Encountered an out-of-storage condition
determine the size of a service processor dump. while attempting to collect a service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF5C B181EF5C B181EF66 B181EF66
Explanation: An error occurred while attempting to Explanation: An error occurred while collecting a
determine the system serial number. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF5D B181EF5D B181EF67 B181EF67
Explanation: An error occurred while collecting a Explanation: An error occurred while collecting a
service processor dump. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF5E B181EF5E B181EF69 B181EF69
Explanation: An error occurred while collecting a Explanation: An error occurred while collecting a
service processor dump. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF5F B181EF5F B181EF6A B181EF6A
Explanation: An error occurred while attempting to Explanation: An error occurred while collecting a
determine the service processor hostname. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 513
B181EF6B • B181EF7D
B181EF6B B181EF6B B181EF75 B181EF75
Explanation: An error occurred while processing a Explanation: An error occurred while collecting a
dump. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF6C B181EF6C B181EF79 B181EF79
Explanation: An error occurred while processing a Explanation: An error occurred while collecting a
dump. service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF6D B181EF6D B181EF7A B181EF7A
Explanation: An error occurred while collecting a Explanation: An error occurred while retrieving a
service processor dump. dump
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF6E B181EF6E B181EF7B B181EF7B
Explanation: An error occurred Explanation: A failure occurred when opening the
dump device
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EF71 B181EF71
B181EF7C B181EF7C
Explanation: An error occured while attempting to
determine if a service processor dump exists. Explanation: A dump was attempted when another
dump was in progress.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EF73 B181EF73
B181EF7D B181EF7D
Explanation: An error occurred while collecting a
service processor dump. Explanation: An error occurred
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
514 System reference codes (Bxxx)
B181EF7E • B181EF90
B181EF7E B181EF7E B181EF88 B181EF88
Explanation: An error occurred Explanation: A service processor (or system controller)
plug-in dump was taken.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EF7F B181EF7F
B181EF8B B181EF8B
Explanation: An error occurred
Explanation: An error occurred while collecting a
Response: If this is a tracking event, no service actions
service processor dump.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181EF83 B181EF83
Explanation: An error occurred while attempting to
B181EF8D B181EF8D
delete a service processor dump.
Explanation: An error occurred.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EF84 B181EF84
B181EF8E B181EF8E
Explanation: An error occurred while attempting to
retrieve a service processor dump. Explanation: An error occurred while collecting a
service processor dump.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181EF86 B181EF86
B181EF8F B181EF8F
Explanation: An error occurred while collecting a
service processor dump. Explanation: An error occurred
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181EF87 B181EF87 B181EF90 B181EF90
Explanation: An error occurred while collecting a Explanation: An error occurred while attempting to
service processor dump. delete a service processor dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
(B1xx) Reference codes 515
B181EF91 • B181F009
callouts detailed with the SRC to determine service
B181EF91 B181EF91
actions.
Explanation: A service processor (or system controller)
dump was invalidated.
B181F003 B181F003
Response: If this is a tracking event, no service actions
Explanation: The PLID of the latest request did not
are required. Otherwise, use the FRU and procedure
match the PLID of the current request; unable to delete
callouts detailed with the SRC to determine service
the file.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181EF99 B181EF99
callouts detailed with the SRC to determine service
Explanation: An error occurred actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181F004 B181F004
callouts detailed with the SRC to determine service
Explanation: A hardware unit dump request was
actions.
received.
Response: If this is a tracking event, no service actions
B181EF9A B181EF9A
are required. Otherwise, use the FRU and procedure
Explanation: The dump storage device was full. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181F005 B181F005
actions.
Explanation: A system dump collection request was
received.
B181EF9B B181EF9B
Response: If this is a tracking event, no service actions
Explanation: An error occurred while collecting a are required. Otherwise, use the FRU and procedure
service processor dump. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181F007 B181F007
actions.
Explanation: Dump is disabled.
Response: If this is a tracking event, no service actions
B181EF9E B181EF9E
are required. Otherwise, use the FRU and procedure
Explanation: An invalid ID was found. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181F008 B181F008
actions.
Explanation: The file does not exist.
Response: If this is a tracking event, no service actions
B181EFA0 B181EFA0
are required. Otherwise, use the FRU and procedure
Explanation: An error occurred while collecting a callouts detailed with the SRC to determine service
service processor dump. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181F009 B181F009
callouts detailed with the SRC to determine service
Explanation: The MDRT source and destination tables
actions.
are incorrect.
Response: If this is a tracking event, no service actions
B181F002 B181F002
are required. Otherwise, use the FRU and procedure
Explanation: The system is not running on the callouts detailed with the SRC to determine service
primary service processor. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
516 System reference codes (Bxxx)
B181F00A • B181F018
B181F00A B181F00A B181F010 B181F010
Explanation: A new dump object could not be created Explanation: There is no location in which to store the
because one already exists. dump.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181F00B B181F00B B181F011 B181F011
Explanation: Deletion of the request block failed. Explanation: The dump is not complete and cannot be
extracted.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181F00C B181F00C
B181F012 B181F012
Explanation: There is no file in which to store the
request block. Explanation: Failed to create a memory the
DumpToExtract memory object.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181F00D B181F00D
B181F014 B181F014
Explanation: A post dump reboot is being requested
with bad chips in the system. Explanation: A dump collection is already in progress.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181F00E B181F00E B181F016 B181F016
Explanation: The system is not running on the Explanation: The system manager will not allow the
primary service processor. dump transition.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181F00F B181F00F B181F018 B181F018
Explanation: A dump buffer access error occurred. Explanation: The dump request is rejected because a
system dump is already present.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 517
B181F019 • B181F024
B181F019 B181F019 B181F01F B181F01F
Explanation: Dump was disabled by a manufacturing Explanation: The dump component has received a
flag. dump extraction request.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181F01A B181F01A B181F020 B181F020
Explanation: DMA operations are not allowed. Explanation: Collection of a dump has been
interrupted, usually by a reset/reload or service
Response: If this is a tracking event, no service actions
processor failover during the dump.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181F01B B181F01B
Explanation: DMA operations are now allowed; will
B181F021 B181F021
CTRM the system.
Explanation: The HMC has been notified that a
Response: If this is a tracking event, no service actions
hardware dump was just collected.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181F01C B181F01C
Explanation: A request to invalidate the dump was
B181F022 B181F022
received.
Explanation: Critical storage levels were exceeded,
Response: If this is a tracking event, no service actions
invalidating or deleting hardware unit dump collection.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181F01D B181F01D
Explanation: An invalid update dump request was
B181F023 B181F023
received.
Explanation: HOM detected a memory configuration
Response: If this is a tracking event, no service actions
change during a main store IPL and the dump has been
are required. Otherwise, use the FRU and procedure
marked complete without main storage.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F01E B181F01E
actions.
Explanation: An error was returned from the statfs
call.
B181F024 B181F024
Response: If this is a tracking event, no service actions
Explanation: The hardware unit dump collection was
are required. Otherwise, use the FRU and procedure
told to abort.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
518 System reference codes (Bxxx)
B181F025 • B181F0E7
B181F025 B181F025 B181F0E1 B181F0E1
Explanation: The service processor tried to abort the Explanation: There was a failure when determining
hardware unit dump, but it didn't stop in time. the number of processors.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181F026 B181F026 B181F0E2 B181F0E2
Explanation: A checkstop IPL was requested. Explanation: There was a failure of the DADA "get
array data" command.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181F027 B181F027
B181F0E3 B181F0E3
Explanation: No mapping was found for the unit ID
types. Explanation: Cannot determine whether the
hypervisor is active or not.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
B181F028 B181F028
B181F0E4 B181F0E4
Explanation: The code update component, or the
concurrent maintenance component, has the lock. Explanation: eCommand Failure
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B181F02D B181F02D B181F0E5 B181F0E5
Explanation: The dump request was rejected because Explanation: The creation of an object failed.
a dump was already in progress.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181F0E6 B181F0E6
B181F0E0 B181F0E0
Explanation: An invalid command was received.
Explanation: There was a failure when determining
Response: If this is a tracking event, no service actions
the number of processors.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181F0E7 B181F0E7
Explanation: An invalid hardware object manager unit
ID was found.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 519
B181F0E8 • B181F0F5
callouts detailed with the SRC to determine service
B181F0F0 B181F0F0
actions.
Explanation: There was an error reading the system
dump id from the registry.
B181F0E8 B181F0E8
Response: If this is a tracking event, no service actions
Explanation: A failure occurred during processor
are required. Otherwise, use the FRU and procedure
cleanup.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F0F1 B181F0F1
actions.
Explanation: An error was returned from
rtim_GetTimeOfDay.
B181F0E9 B181F0E9
Response: If this is a tracking event, no service actions
Explanation: The mailbox message to the hypervisor
are required. Otherwise, use the FRU and procedure
failed; the notification of invalidation was sent.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F0F2 B181F0F2
actions.
Explanation: RMGRGetFspRole failed; cannot
determine the service processor's role.
B181F0EA B181F0EA
Response: If this is a tracking event, no service actions
Explanation: The internal value that tracks whether or
are required. Otherwise, use the FRU and procedure
not the hypervisor in active is in the wrong state.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F0F3 B181F0F3
actions.
Explanation: There was a failure when notifying the
HMC that a hardware unit dump is ready.
B181F0EC B181F0EC
Response: If this is a tracking event, no service actions
Explanation: There was an error when retrieving the
are required. Otherwise, use the FRU and procedure
facility list from rules with the provided content.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F0F4 B181F0F4
actions.
Explanation: An error occurred when verifying that
panel function 42 is enabled.
B181F0ED B181F0ED
Response: If this is a tracking event, no service actions
Explanation: SMGR request (smgrIplTypeRequest)
are required. Otherwise, use the FRU and procedure
failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F0F5 B181F0F5
actions.
Explanation: Stopping the clock failed on the core.
B181F0EE B181F0EE Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: SrciSrc object construction failure.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
520 System reference codes (Bxxx)
B181F0F6 • B181F10A
B181F0F6 B181F0F6 B181F104 B181F104
Explanation: A failure was returned from Explanation: The call to adal_fsi_config failed.
hysrRunServiceRoutine.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B181F105 B181F105
B181F0F7 B181F0F7
Explanation: A local bus is not owned.
Explanation: Failure when trying to get the concurrent
Response: If this is a tracking event, no service actions
maintenance operation lock.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181F106 B181F106
Explanation: The call to watchdog_scan_dram failed.
B181F0F8 B181F0F8
Response: If this is a tracking event, no service actions
Explanation: An error occurred when calling a
are required. Otherwise, use the FRU and procedure
function.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F107 B181F107
actions.
Explanation: The threshold of new DRAM errors was
reached.
B181F101 B181F101
Response: If this is a tracking event, no service actions
Explanation: The call to adal_fsi_open failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181F108 B181F108
Explanation: The call to watchdog_scan_nvram failed.
B181F102 B181F102
Response: If this is a tracking event, no service actions
Explanation: The call to adal_fsi_wait failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181F109 B181F109
Explanation: The threshold of new NVRAM errors
B181F103 B181F103
was reached.
Explanation: The call to adal_fsi_config to determine
Response: If this is a tracking event, no service actions
the number of CFAMS failed.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181F10A B181F10A
Explanation: An NVRAM address has appeared
multiple times.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 521
B181F10B • B181F11A
callouts detailed with the SRC to determine service
B181F112 B181F112
actions.
Explanation: Call to statfs() failed.
B181F10B B181F10B Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The call to watchdog_fork failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F113 B181F113
actions.
Explanation: PCS usage has reached 90%.
B181F10C B181F10C Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The call to watchdog_file failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F114 B181F114
actions.
Explanation: PCS usage has reached 80%.
B181F10D B181F10D Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The threshold of bad blocks in the
callouts detailed with the SRC to determine service
NVRAM's flash memory was exceeded.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181F115 B181F115
callouts detailed with the SRC to determine service
actions. Explanation: A function call failed.
Response: If this is a tracking event, no service actions
B181F10E B181F10E are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
Explanation: The call to watchdog_open failed.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181F116 B181F116
callouts detailed with the SRC to determine service
actions. Explanation: FSI IRQ loop event occured; one or more
of this type event was not detectable.
B181F10F B181F10F Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: The call to watchdog_ping failed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F119 B181F119
actions.
Explanation: The user specified a link, or CFAM, but
not both.
B181F111 B181F111
Response: If this is a tracking event, no service actions
Explanation: A signal was received.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B181F11A B181F11A
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
522 System reference codes (Bxxx)
B181F11B • B181F201
B181F11B B181F11B B181F127 B181F127
Explanation: A call to a function failed. Explanation: The number of one-bit flips exceeded the
threshold. The service processor hardware will have to
Response: If this is a tracking event, no service actions
be replaced.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B181F121 B181F121
Explanation: A clean function failed.
B181F128 B181F128
Response: If this is a tracking event, no service actions
Explanation: The number of uncorrectable bit flips
are required. Otherwise, use the FRU and procedure
exceeded the threshold. The service processor hardware
callouts detailed with the SRC to determine service
will have to be replaced.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181F122 B181F122
callouts detailed with the SRC to determine service
Explanation: An error was returned when attempting actions.
to initialize the library load mutex.
Response: If this is a tracking event, no service actions B181F129 B181F129
are required. Otherwise, use the FRU and procedure
Explanation: The service processor kernel is reporting
callouts detailed with the SRC to determine service
that the system is running out of space in the flash
actions.
memory.
Response: If this is a tracking event, no service actions
B181F123 B181F123
are required. Otherwise, use the FRU and procedure
Explanation: An error was returned when attempting callouts detailed with the SRC to determine service
to lock the library load mutex. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181F12A B181F12A
callouts detailed with the SRC to determine service
Explanation: The service processor kernel is reporting
actions.
that there is not enough free space in flash memory to
boot the system.
B181F124 B181F124
Response: If this is a tracking event, no service actions
Explanation: An error was returned when attempting are required. Otherwise, use the FRU and procedure
to unlock the library load mutex. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181F12B B181F12B
actions.
Explanation: A local bus loss event occurred, but an
error was returned when attempting to determine
B181F126 B181F126 which bus was lost.
Explanation: An internal error occurred when Response: If this is a tracking event, no service actions
checking the health of the flash memory on the service are required. Otherwise, use the FRU and procedure
processor. This may or may not indicate a degredation callouts detailed with the SRC to determine service
of the flash memory performance. Check the details of actions.
the error log entry.
Response: If this is a tracking event, no service actions B181F201 B181F201
are required. Otherwise, use the FRU and procedure
Explanation: A PSI error has been detected.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 523
B181F202 • B181F20E
callouts detailed with the SRC to determine service
B181F202 B181F202
actions.
Explanation: Invalid HOM node information was
received.
B181F209 B181F209
Response: If this is a tracking event, no service actions
Explanation: The function call to get the maximum
are required. Otherwise, use the FRU and procedure
number of resource IDs returned zero.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F203 B181F203
actions.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions B181F20A B181F20A
are required. Otherwise, use the FRU and procedure
Explanation: The function call to get the resource IDs
callouts detailed with the SRC to determine service
returned zero.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181F204 B181F204
callouts detailed with the SRC to determine service
Explanation: An invalid PSI device was received. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B181F20B B181F20B
callouts detailed with the SRC to determine service
Explanation: No resource ID matches the resource ID
actions.
of the current service processor.
Response: If this is a tracking event, no service actions
B181F205 B181F205
are required. Otherwise, use the FRU and procedure
Explanation: GXHBC was not found. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181F20C B181F20C
actions.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
B181F206 B181F206
are required. Otherwise, use the FRU and procedure
Explanation: A function call failed. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B181F20D B181F20D
actions.
Explanation: A function call failed.
Response: If this is a tracking event, no service actions
B181F207 B181F207
are required. Otherwise, use the FRU and procedure
Explanation: The function call to get the DMA paths callouts detailed with the SRC to determine service
did not return a value corresponding to the current actions.
resource ID.
Response: If this is a tracking event, no service actions B181F20E B181F20E
are required. Otherwise, use the FRU and procedure
Explanation: A PSI error has been detected.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F208 B181F208
actions.
Explanation: The function call to get the DMA paths
did not return any primary DMA paths.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
524 System reference codes (Bxxx)
B181F20F • B1829026
callouts detailed with the SRC to determine service
B181F20F B181F20F
actions.
Explanation: Unable to read from the bulk power
controller (BPC).
B1829018 B1829018
Response: If this is a tracking event, no service actions
Explanation: SPIRA does not have sufficient space for
are required. Otherwise, use the FRU and procedure
the main store dump results table entries.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B181F7AA B181F7AA
actions.
Explanation: No functional processor clock was found.
Response: If this is a tracking event, no service actions B182901A B182901A
are required. Otherwise, use the FRU and procedure
Explanation: The hypervisor did not allocate enough
callouts detailed with the SRC to determine service
storage for the data structures being
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B181FB53 B181FB53
callouts detailed with the SRC to determine service
Explanation: Wire test found a failure in a path actions.
between a memory controller and a DIMM.
Response: If this is a tracking event, no service actions B182901D B182901D
are required. Otherwise, use the FRU and procedure
Explanation: An internal service processor error
callouts detailed with the SRC to determine service
occurred. Check for system firmware updates and
actions.
apply if available before replacing the service processor.
Response: If this is a tracking event, no service actions
B182104C B182104C
are required. Otherwise, use the FRU and procedure
Explanation: Communication paths on the service callouts detailed with the SRC to determine service
processor side are not enabled to do DMA operations. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure B182901E B182901E
callouts detailed with the SRC to determine service
Explanation: The service processor timed out while
actions.
waiting for the hypervisor to start.
Response: If this is a tracking event, no service actions
B182104D B182104D
are required. Otherwise, use the FRU and procedure
Explanation: The CEC side is not configured properly. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1829020 B1829020
actions.
Explanation: The service processor either retrieved
invalid data from CEC memory, or found that a
B1828438 B1828438 mainstore dump is invalid.
Explanation: Failure to validate the password. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure
actions.
callouts detailed with the SRC to determine service
actions.
B1829026 B1829026
B182880C B182880C Explanation: An internal service processor error
occurred. Check for system firmware updates and
Explanation: Detected a unexpected command after a
apply if available before replacing the service processor.
service routine run.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 525
B182902A • B1829514
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B182902A B182902A B182950C B182950C
Explanation: The data read from main storage is not Explanation: There was an invalid value in a message
the same as what was written to main storage. from the hypervisor to the service processor
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1829503 B1829503 B182950D B182950D
Explanation: The service processor attempted to send Explanation: The hypervisor did not provide enough
a message to the hypervisor when the hypervisor data to complete the function
message queue was already full
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1829511 B1829511
B1829504 B1829504
Explanation: Sending a message to the HMC took too
Explanation: Nobody was waiting on the message long
that was just received from the hypervisor.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1829512 B1829512
B1829507 B1829507
Explanation: The hypervisor attempted to add a
Explanation: The service processor was unable to already-existing buffer to the list of HMC buffers
make an entry in its error log that the hypervisor
Response: If this is a tracking event, no service actions
requested.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1829513 B1829513
Explanation: The hypervisor is garding out a
B1829508 B1829508
hardware resource
Explanation: The hypervisor did not provide a valid
Response: If this is a tracking event, no service actions
address to the service processor
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1829514 B1829514
Explanation: The communications path to the
B1829509 B1829509
hypervisor is currently disabled at the request of the
Explanation: The wrong number of bytes was written hypervisor
on the mailbox interface.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
actions.
526 System reference codes (Bxxx)
B1829515 • B1829541
B1829515 B1829515 B1829523 B1829523
Explanation: A request was made to disable Explanation: Failed while waiting on a message from
communications between the hypervisor and the the hypervisor; probably timed out.
service processor
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1829525 B1829525
B182951A B182951A
Explanation: The hypervisor sent the service processor
Explanation: The hypervisor sent the service processor an invalid SRC to display.
an invalid value during a boot operation
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1829538 B1829538
B182951C B182951C
Explanation: There are no valid PSI links that can be
Explanation: The hypervisor is not responding to used for mailbox activity. Check the guard records
messages from the service processor regarding DMA paths to see why there are no valid
links. Whatever took the PSI links down has already
Response: If this is a tracking event, no service actions
occurred.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B182951D B182951D
Explanation: The hypervisor attempted to use an
B182953C B182953C
invalid HMC buffer
Explanation: The hypervisor did not read messages
Response: If this is a tracking event, no service actions
from the service processor (or system controller) within
are required. Otherwise, use the FRU and procedure
the allotted time. Either the hypervisor is unresponsive
callouts detailed with the SRC to determine service
or the PSI links are down.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B182951E B182951E
callouts detailed with the SRC to determine service
Explanation: A function performed by the hypervisor actions.
ended with an error
Response: If this is a tracking event, no service actions B182953E B182953E
are required. Otherwise, use the FRU and procedure
Explanation: An internal firmware error occurred.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B182951F B182951F
actions.
Explanation: In a system with redundant service
processors, the secondary service processor is not
B1829541 B1829541
booting with the primary service processor
Explanation: The device driver indicated that an error
Response: If this is a tracking event, no service actions
occurred prior to his operation, so this operation
are required. Otherwise, use the FRU and procedure
should be retried.
callouts detailed with the SRC to determine service
actions. Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
(B1xx) Reference codes 527
B1829543 • B182E550
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1829543 B1829543
Explanation: Informational message: Due to
B182D005 B182D005
reset/reload or failover, the hypervisor is being told to
synchronize data to the secondary service processor. Explanation: A hypervisor occurred.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B1829546 B1829546 B182D006 B182D006
Explanation: The offset from the hypervisor was Explanation: An unknown error occurred when trying
beyond the size of the firmware update module being to update the indicator status.
read.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B182E501 B182E501
B182954B B182954B
Explanation: There was a hardware-detected problem
Explanation: The checksum calculated by the service due to the hypervisor firmware.
processor (or system controller) did not match the
Response: If this is a tracking event, no service actions
checksum in the hypervisor.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B182E504 B182E504
Explanation: A hardware failure was detected in the
B182954C B182954C
central electronics complex (CEC).
Explanation: It has taken the hypervisor a long time
Response: If this is a tracking event, no service actions
to pull a message off the mailbox hardware. Although
are required. Otherwise, use the FRU and procedure
this is below the 45 second predictive error limit, it can
callouts detailed with the SRC to determine service
cause HMC incompletes when it occurs a couple times.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B182E540 B182E540
callouts detailed with the SRC to determine service
actions. Explanation: There was a failure most likely
attributable to the hypervisor firmware, but it could
also be software-related or require further support.
B182B82E B182B82E
Response: If this is a tracking event, no service actions
Explanation: An internal firmware error occurred.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B182E550 B182E550
Explanation: There was a hypervisor firmware
B182B898 B182B898
problem, but it could also be hardware-related or
Explanation: The hypervisor has not handed off the require further support.
bus after forcing the link down; there must be a
Response: If this is a tracking event, no service actions
hypervisor problem.
are required. Otherwise, use the FRU and procedure
528 System reference codes (Bxxx)
B182E560 • B1868C0C
callouts detailed with the SRC to determine service
B185270E B185270E
actions.
Explanation: The daemon received a request while
running on the secondary system controller or service
B182E560 B182E560
processor.
Explanation: The hardware detected a problem that
Response: If this is a tracking event, no service actions
was caused by the hypervisor firmware. The dump that
are required. Otherwise, use the FRU and procedure
was taken may need to be analyzed.
callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
B18527C0 B18527C0
actions.
Explanation: The power off unit command failed.
B1852701 B1852701 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: An invalid voltage control command was
callouts detailed with the SRC to determine service
received.
actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
B1868C01 B1868C01
callouts detailed with the SRC to determine service
actions. Explanation: The bulk power controller (BPC) is
currently performing a validation operation. This
operation should be retried. If the condition persists it
B1852702 B1852702
is probably a firmware problem; the BPC firmware
Explanation: The daemon received a message with an should be updated.
invalid function field.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1868C02 B1868C02
B1852707 B1852707
Explanation: An invalid request was sent to the
Explanation: The POWER server was not ready for network validation daemon.
the command it was sent.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1868C08 B1868C08
B1852708 B1852708
Explanation: The version value sent in the message
Explanation: A resource ID was not in the table, doesn't to match the current version.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B185270B B185270B B1868C0C B1868C0C
Explanation: Invalid input was received. Explanation: The was a communication problem with
the remote bulk power controller (BPC).
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 529
B1868C10 • B1879534
B1868C10 B1868C10 B1868C59 B1868C59
Explanation: The network validation daemon received Explanation: The MAC address is not available.
a signal.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1868CAA B1868CAA
B1868C12 B1868C12
Explanation: A host's IP address on network side A
Explanation: The netv daemon determined that there does not match the IP address on side B.
are too many error logs to the transferred to the system
Response: If this is a tracking event, no service actions
client.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1873850 B1873850
Explanation: The multiplexer configuration key is not
B1868C55 B1868C55
valid with the sibling state change.
Explanation: The service processor was unable to
Response: If this is a tracking event, no service actions
collect the network data.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B187400B B187400B
Explanation: Unable to get the card type from the
B1868C56 B1868C56
environment.
Explanation: The PVID configuration is not valid.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1878408 B1878408
B1868C57 B1868C57
Explanation: The wrong function passed was in.
Explanation: The virtual LAN mapping was not
Response: If this is a tracking event, no service actions
correct.
are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions.
B1879534 B1879534
Explanation: The HMC is attempting to send a
B1868C58 B1868C58
message that exceeds the maximum size of a message
Explanation: The VLAN enablement configuration is between the service processor and the hypervisor.
not valid.
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
530 System reference codes (Bxxx)
B187E501 • B1A3A0C0
B187E501 B187E501 B1A33129 B1A33129
Explanation: There was a hardware-detected problem Explanation: The error log server received a syslog
due to the HMC firmware. message that requires attention.
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
B187E504 B187E504 B1A38426 B1A38426
Explanation: A hardware failure was detected in the Explanation: A power error was validated.
central electronics complex (CEC).
Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.
B1A38438 B1A38438
B187E540 B187E540
Explanation: BOOTP: Discovering the server timed
Explanation: There was a failure most likely out.
attributable to HMC firmware, but it could also be
Response: Refer to partition firmware progress codes
software-related or require further support.
using code CA00E174.
Response: If this is a tracking event, no service actions
Failing Item:
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service v FWHOST
actions.
B1A38B24 B1A38B24
B187E550 B187E550 Explanation: An invalid network configuration was
Explanation: There was an HMC firmware problem, entered by the user.
but it could also be hardware-related or require further Response: If this is a tracking event, no service actions
support. are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
callouts detailed with the SRC to determine service
actions. B1A3A0A7 B1A3A0A7
Explanation: Service switch error. Function 26 was
B187E560 B187E560 done before function 25.
Explanation: The hardware detected a problem that Response: If this is a tracking event, no service actions
was caused by the HMC firmware. The dump that was are required. Otherwise, use the FRU and procedure
taken may need to be analyzed. callouts detailed with the SRC to determine service
Response: If this is a tracking event, no service actions actions.
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service B1A3A0C0 B1A3A0C0
actions.
Explanation: There was a service switch error.
B1A31036 B1A31036 Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
Explanation: A DMA operation was attempted in TCE callouts detailed with the SRC to determine service
mode before setup for TCE mode was complete. actions.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
(B1xx) Reference codes 531
B1A3E006 • B1A3E550
B1A3E006 B1A3E006
Explanation: Customized data is missing.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1A3E01F B1A3E01F
Explanation: A lab test was performed.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1A3E501 B1A3E501
Explanation: There was a hardware-detected problem
due to the external environment or a user error.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1A3E504 B1A3E504
Explanation: A hardware failure was detected in the
central electronics complex (CEC).
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1A3E540 B1A3E540
Explanation: There was a failure most likely
attributable to the external environment or a user error,
but could also be software-related or require further
support.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
B1A3E550 B1A3E550
Explanation: There was an external environment
failure, most likely attributable to a software problem,
but it could also be hardware-related or require further
support.
Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service
actions.
532 System reference codes (Bxxx)
(B2xx) Reference codes
A B2xx reference code indicates that an event or error was detected and logged by virtual service
processor firmware.
The logical partition associated with the event or error can be identified from the "LP=pppp" ASCII string
found in the SRC word 1 extension field, where 'pppp' is the logical partition ID.
To resolve a B2xx reference code, determine if the SRC requires a service action.
If the SRC is listed in a serviceable event view, use the FRU list from the serviceable event view to
determine the actions to take.
If you do not find the SRC in a serviceable event view, then it is an informational event and does not
require service action.
Explanation: Mobility aborted due to a system white
B2001001 B2001001
button power off
Explanation: Unable to acquire a pre-allocated task
msg from the free queue.
B2001130 B2001130
Failing Item:
Explanation: A problem occurred during the
v LICCODE migration of a partition
Response: The partition ID is in extended word one
B2001020 B2001020 as LP=xxx in decimal format.
Explanation: Firmware for the specified function The user attempted to migrate a partition to a system
cannot be loaded. The firmware resource and all that has a power or thermal problem. The migration
associated virtual and/or physical devices will not be will not continue.
available until the issue is resolved.
Look for and fix power or thermal problems on this
Response: Generate a PHYP and FSP dump and system and then retry the migration.
contact the next level of support.
Failing Item:
Failing Item:
v SVCDOCS
v NEXTLVL
B2001131 B2001131
B2001051 B2001051
Explanation: A problem occurred during the
Explanation: During partition migration, the migration of a partition
Hypervisor encountered a problem saving state for the
source partition. Migration will be aborted. Response: The migration of a partition did not
complete. The partition ID is in extended word one as
Failing Item: LP=xxx in decimal format.
v LICCODE
Contact your next level of support.
Failing Item:
B2001052 B2001052
v NEXTLVL
Explanation: During partition migration, the
Hypervisor encountered a problem restoring the state
for the target partition. Migration will be aborted B2001132 B2001132
Failing Item: Explanation: A problem occurred during the IPL of a
partition.
v LICCODE
Response: The partition ID is in extended word one
as LP=xxx in decimal format.
B2001053 B2001053
© Copyright IBM Corp. 2010, 2013 533
B2001133 • B2001150
A platform LIC error occurred while it was trying to
B2001142 B2001142
allocate memory. The IPL will not continue.
Explanation: A problem occurred during the
Perform a platform dump and contact your next level
migration of a partition
of support.
Response: The migration of a partition did not
Failing Item:
complete. The partition ID is in extended word one as
v NEXTLVL LP=xxx in decimal format.
Contact your next level of support.
B2001133 B2001133
Failing Item:
Explanation: A problem occurred during the
v NEXTLVL
migration of a partition
Response: The migration of a partition did not
B2001143 B2001143
complete. The partition ID is in extended word one as
LP=xxx in decimal format. Explanation: A problem occurred during the
migration of a partition
Contact your next level of support.
Response: The migration of a partition did not
Failing Item:
complete. The partition ID is in extended word one as
v NEXTLVL LP=xxx in decimal format.
Contact your next level of support.
B2001134 B2001134
Failing Item:
Explanation: A problem occurred during the
v NEXTLVL
migration of a partition
Response: The migration of a partition did not
B2001144 B2001144
complete. The partition ID is in extended word one as
LP=xxx in decimal format. Explanation: A problem occurred during the
migration of a partition
Contact your next level of support.
Response: The migration of a partition did not
Failing Item:
complete. The partition ID is in extended word one as
v NEXTLVL LP=xxx in decimal format.
Contact your next level of support.
B2001140 B2001140
Failing Item:
Explanation: A problem occurred during the
v NEXTLVL
migration of a partition
Response: The migration of a partition did not
B2001148 B2001148
complete. The partition ID is in extended word one as
LP=xxx in decimal format. Explanation: A problem occurred during the
migration of a partition
Contact your next level of support.
Response: The migration of a partition did not
Failing Item:
complete. The partition ID is in extended word one as
v NEXTLVL LP=xxx in decimal format.
Contact your next level of support.
B2001141 B2001141
Failing Item:
Explanation: A problem occurred during the
v NEXTLVL
migration of a partition
Response: The migration of a partition did not
B2001150 B2001150
complete. The partition ID is in extended word one as
LP=xxx in decimal format. Explanation: A problem occurred during the IPL of a
partition.
Contact your next level of support.
Response: The partition ID is in extended word one
Failing Item:
as LP=xxx in decimal format.
v NEXTLVL
This is a partitioning configuration problem. The
LPARCFG Symbolic FRU will help correct the problem.
534 System reference codes (Bxxx)
B2001151 • B2001265
If the problem persists, call your next level of support. fully initializing. Retry the partition IPL after the
platform IPL has fully completed and the platform is
Failing Item:
not in standby mode. If that IPL fails, call your next
v LPARCFG level of support.
Failing Item:
B2001151 B2001151
v SVCDOCS
Explanation: A problem occurred during the
migration of a partition
B2001230 B2001230
Response: The migration of a partition did not
Explanation: A problem occurred during the IPL of a
complete. The partition ID is in extended word one as
partition.
LP=xxx in decimal format.
Response: The partition ID is in extended word one
Contact your next level of support.
as LP=xxx in decimal format.
Failing Item:
If word 3 of the SRC is 000000C9, it indicates a
v NEXTLVL firmware problem. Contact your next level of support.
Either a Platform System Dump should be initiated, or
B2001152 B2001152 else a PHYP remote connection should be set up while
at the B2001230 SRC.
Explanation: An attempt to migrate a vTPM enabled
LPAR has been blocked because the vTPM failed to Otherwise, if word 3 of the SRC is not 000000C9, this is
confirm in a reasonable amount of time that it is a partitioning configuration problem. The partition is
operating with the current trusted system key. lacking the necessary resources to IPL.
Response: An LPADUMP will be required for This error might occur when you shut down a partition
investigation. Two options exist if migration is still that is set to automatically IPL and then turn the
required. 1. Reboot the LPAR , the vTPM will restart managed system off and back on. When the partition
and should clear this error. 2. Delete the vTPM from automatically IPLs, it uses the resources specified in
the LPAR configuration. PHYP NVRAM, and this error occurs when the server
does not find the exact resources specified in NVRAM.
Problem determination: An emergency workaround is The solution is to activate the partition by using the
to delete the VTPM from the LPAR configuration. That partition profile on the HMC or SDMC. The HMC or
should allow migration but may leave any LPAR SDMC applies the values in the profile to NVRAM.
processes dependent on VTPM in a bad state. The When the partition IPLs, it uses the resources specified
PowerSC features will be lost. in the profile.
Failing Item: Failing Item:
v SVCDOCS v LPARCFG
v LICCODE v LICCODE
B2001170 B2001170 B2001260 B2001260
Explanation: A problem occurred during the IPL of a Explanation: A problem occurred during the IPL of a
partition. partition.
Response: The partition ID is in extended word one Response: The partition could not IPL at the Timed
as LP=xxx in decimal format. A failure occurred due to Power On setting because the IPL setting of the
a validation error. The IPL is terminated. partition was not set to Normal. The partition ID is in
extended word one as LP=xxx in decimal format.
Contact your next level of support.
Failing Item:
Failing Item:
v SVCDOCS
v NEXTLVL
B2001265 B2001265
B2001225 B2001225
Explanation: A problem occurred during the IPL of a
Explanation: A problem occurred during the IPL of a
partition.
partition.
Response: The partition could not IPL. The partition
Response: The partition ID is in extended word one
ID is in extended word one as LP=xxx in decimal
as LP=xxx in decimal format.
format.
The partition attempted to IPL prior to the platform
(B2xx) Reference codes 535
B2001266 • B2001321
An operating system MSD IPL was attempted with the abnormally terminated. Contact your next level of
IPL side on D-mode. This is not a valid operating support.
system IPL scenario, and the IPL will be halted. This
Failing Item:
SRC is usually seen when a D-mode SLIC install fails
and attempts an MSD. v NEXTLVL
Failing Item:
B2001283 B2001283
v SVCDOCS
Explanation: A slot containing an I/O Processor (IOP)
is assigned to the partition. Power 7 hardware does not
B2001266 B2001266
support IOP card causing the IPL of the partition to
Explanation: A problem occurred during the IPL of a fail.
partition.
Problem determination: The slot identified by the
Response: The partition could not IPL. The partition location code in the error log entry contains an I/O
ID is in extended word one as LP=xxx in decimal Processor (IOP). This slot must be removed from the
format. partition either by physically removing the IOP from
the slot or removing the slot from the partition's
You are attempting to IPL an operating system that is
configuration. After the IOP has been removed, retry
not supported or not enabled. On certain models the
the IPL.
IBM i Operating System operating system can be
enabled or disabled from the ASM menu. If you are Failing Item:
attempting to run IBM i Operating System in a v SVCDOCS
partition on such a model, check the ASM menu to
ensure that IBM i Operating System is enabled.
B2001310 B2001310
Failing Item:
Explanation: A problem occurred during the IPL of a
v SVCDOCS
partition.
Response: The partition ID is in extended word one
B2001280 B2001280
as LP=xxx in decimal format. No alternate (D-mode)
Explanation: A problem occurred during a partition IPL IOP was selected. The IPL will attempt to continue,
Main Storage Dump. but there may not be enough information to find the
correct D-mode load source.
Response: A mainstore dump IPL did not complete
due to configuration mismatch. Contact your next level Have the customer configure an alternate IPL IOP for
of support. the partition. Then retry the partition IPL.
Failing Item: Failing Item:
v NEXTLVL v SVCDOCS
B2001281 B2001281 B2001320 B2001320
Explanation: A partition memory error occurred Explanation: A problem occurred during the IPL of a
partition.
Response: An attempt to perform a partition dump
failed. A partition memory error occurred. The failed Response: The partition ID is in extended word one
memory will no longer be used. The partition dump as LP=xxx in decimal format. No default load source
was terminated. The partition ID is in extended word IOP was selected for an A/B-mode IPL. The IPL will
one as LP=xxx in decimal format. Re-IPL the partition. attempt to continue, but there may not be enough
information to find the correct load source.
Failing Item:
v SVCDOCS Have the customer configure a load source IOP for the
partition. Then retry the partition IPL.
B2001282 B2001282 Failing Item:
v SVCDOCS
Explanation: A problem occurred during the IPL of a
partition.
B2001321 B2001321
Response: The partition ID is in extended word one
as LP=xxx in decimal format. Explanation: A problem occurred during the IPL of a
partition.
A partition running on I/O reporting mode has
Response: The partition ID is in extended word one
536 System reference codes (Bxxx)
B2001322 • B2002300
as LP=xxx in decimal format. The IOA for the load
B2002210 B2002210
source device needed an IOP, and none was detected.
Check your LPAR configuration and make sure the Explanation: A partition property was set to default
correct slot is specified for the IPL load source. Then setting
retry the partition IPL.
Response: The partition ID is in extended word one
Failing Item: as LP=xxx in decimal format.
v SVCDOCS A partition property that was supported on the original
system is not supported on this system. The property
B2001322 B2001322 has been set to a default setting. Check all the partition
properties of the migrated partition and ensure they are
Explanation: A problem occurred during the IPL of a set to the desired values.
partition.
Response: The partition ID is in extended word one B2002220 B2002220
as LP=xxx in decimal format. During the partition IPL,
code tried to determine if the device in a slot was an Explanation: A partition property could not be
I/O Processor or an I/O Adapter. That check failed. transferred
Check your LPAR configuration and make sure that the Response: The partition ID is in extended word one
correct slot is specified for the IPL load source. Then as LP=xxx in decimal format.
retry the partition IPL. If this does not resolve the
problem, perform LICIP15. A partition property could not be transferred during a
partition migration. The partition migration continued.
Failing Item: No immediate action is necessary. At the earliest
v SVCDOCS convenient time or service window, re-IPL the partition
to restore partition properties.
B2002048 B2002048
B2002250 B2002250
Explanation: A problem occurred during a partition
Main Storage Dump. Explanation: A problem occurred during the IPL of a
partition.
Response: A mainstore dump IPL did not complete
due to a copy error. Contact your next level of support. Response: The partition ID is in extended word one
as LP=xxx in decimal format. A slot that was needed
Failing Item:
for the partition was unavailable. See the Symbolic FRU
v NEXTLVL SLOTUSE for more information on the cause of this
error.
B2002054 B2002054 Failing Item:
Explanation: A problem occurred during a partition v SLOTUSE
Main Storage Dump.
Response: A mainstore dump IPL did not complete B2002260 B2002260
due to a configuration mismatch.
Explanation: A problem occurred during the IPL of a
Failing Item: partition.
v NEXTLVL Response: The partition ID is in extended word one
as LP=xxx in decimal format.
B2002058 B2002058 A problem occurred when an attempt to power off a
Explanation: A problem occurred during a partition Virtual I/O slot was performed. Contact your next level
Main Storage Dump. of support.
Response: A mainstore dump IPL did not complete Failing Item:
due to a copy error. Contact your next level of support. v NEXTLVL
Failing Item:
v NEXTLVL B2002300 B2002300
Explanation: A problem occurred during the IPL of a
partition.
Response: The partition ID is in extended word one
as LP=xxx in decimal format. A slot that was needed
for the partition was unavailable. See the Symbolic FRU
(B2xx) Reference codes 537
B2002310 • B2003084
SLOTUSE for more information on the cause of this
B2002475 B2002475
error.
Explanation: A problem occurred during the IPL of a
Failing Item:
partition.
v SLOTUSE
Response: The partition ID is in extended word one
as LP=xxx in decimal format. A slot that was needed
B2002310 B2002310 for the partition was either empty or the device in the
Explanation: A problem occurred during the IPL of a slot has failed. See the Symbolic FRU SLOTUSE for
partition. more information on the cause of this error.
Response: The partition ID is in extended word one If you have a RAID enablement card (CCIN 5709) on
as LP=xxx in decimal format. The platform LIC for this your system, it will disable an embedded SCSI adapter.
partition attempted an operation. There was a failure. If that embedded slot is called out in the error, you can
Contact your next level of support. safely ignore this error.
Failing Item: Failing Item:
v NEXTLVL v SLOTUSE
B2002320 B2002320 B2002485 B2002485
Explanation: A problem occurred during the IPL of a Explanation: A problem occurred during the IPL of a
partition. partition.
Response: The partition ID is in extended word one Response: The partition ID is in extended word one
as LP=xxx in decimal format. The platform LIC for this as LP=xxx in decimal format. The platform LIC for this
partition attempted an operation. There was a failure. partition attempted an operation. There was a failure.
Contact your next level of support. Contact your next level of support.
Failing Item: Failing Item:
v NEXTLVL v NEXTLVL
B2002425 B2002425 B2003000 B2003000
Explanation: A problem occurred during the IPL of a Explanation: System log entry only, no service action
partition. required
Response: The partition ID is in extended word one Response: A user requested an immediate termination
as LP=xxx in decimal format. The platform LIC for this and main store dump of a partition. The partition ID is
partition attempted an operation. There was a failure. in extended word one as LP=xxx in decimal format.
Contact your next level of support.
Failing Item: B2003081 B2003081
v NEXTLVL Explanation: A problem occurred during the IPL of a
partition.
B2002426 B2002426 Response: IPL did not complete due to a copy error.
Contact your next level of support.
Explanation: A problem occurred during the IPL of a
partition. Failing Item:
Response: The partition ID is in extended word one v LICCODE
as LP=xxx in decimal format. The platform LIC for this
partition attempted an operation. There was a failure. B2003084 B2003084
Contact your next level of support.
Explanation: A problem occurred during the IPL of a
Failing Item: partition.
v NEXTLVL
Response: The adapter type might not be supported.
Contact your next level of support.
Failing Item:
v NEXTLVL
538 System reference codes (Bxxx)
B2003088 • B2003125
as LP=xxx in decimal format. A problem occurred on
B2003088 B2003088
the path to the load source for the partition.
Explanation: System log entry only, no service action
If present, look in the Serviceable Event View for a
required
B7xx xxxx during the partition's IPL. Correct that error
Response: The adapter type might not be supported. and retry the partition IPL.
Ensure that a valid I/O Load Source is tagged.
Failing Item:
v SVCDOCS
B200308C B200308C
Explanation: A problem occurred during the IPL of a B2003114 B2003114
partition.
Explanation: A problem occurred during the IPL of a
Response: The adapter type cannot be determined. partition.
Ensure that a valid I/O Load Source is tagged.
Response: The partition ID is in extended word one
If the problem persists, contact your next level of as LP=xxx in decimal format.
support.
The B2xx xxxx SRC Format is Word 1: B2xx3114, Word
Failing Item: 3: Bus, Word 4: Board, Word 5: Card.
v NEXTLVL
Failing Item:
v NEXTLVL
B2003090 B2003090
Explanation: A problem occurred during the IPL of a B2003115 B2003115
partition.
Explanation: The specified slot used for IBM i IPL is
Response: The partition ID is in extended word one not operational.
as LP=xxx in decimal format.
Contact your next level of support. B2003120 B2003120
Failing Item: Explanation: System log entry only, no service action
v NEXTLVL required
Response: The partition ID is in extended word one
B2003105 B2003105 as LP=xxx in decimal format. Retry count exceeded.
This is logged for each unsuccessful attempt to IPL
Explanation: A problem occurred during the IPL of a
with a loadsource candidate. If the IPL fails, look for
partition.
other serviceable errors.
Response: Verify that the tagged Load Source Slot is
supported for IPL. If it is, contact your next level of
B2003123 B2003123
support.
Explanation: System log entry only, no service action
Failing Item:
required
v LPARCFG
B2003125 B2003125
B2003110 B2003110
Explanation: A problem occurred during the IPL of a
Explanation: A problem occurred during the IPL of a partition.
partition.
Response: The partition ID is in extended word one
Response: The search for a valid load source device as LP=xxx in decimal format.
was exhausted. The partition ID is in extended word
one as LP=xxx in decimal format. Perform LICIP15. This is a platform LIC main store utilization problem.
The platform LIC could not obtain a segment of main
Failing Item: storage within the platform's main store to use for
v SVCDOCS managing the creation of a partition.
Failing Item:
B2003113 B2003113 v LICCODE
Explanation: A problem occurred during the IPL of a
partition.
Response: The partition ID is in extended word one
(B2xx) Reference codes 539
B2003128 • B2003145
v SVCDOCS
B2003128 B2003128
Explanation: A problem occurred during the IPL of a
B2003141 B2003141
partition.
Explanation: System log entry only, no service action
Response: The partition ID is in extended word one
required
as LP=xxx in decimal format. An unexpected failure
return code was returned when attempting to query the Response: The IOP in the slot used for the last
IOA slots that are assigned to an IOP. successful IPL of the operating system was replaced
with an I/O Adapter. The IPL will continue by
Look for B700 69xx errors in the Serviceable Event
searching for a valid load source device.
View and work those errors.
Check the LPAR configuration if required, and ensure
Failing Item:
that the tagged I/O for the partition is correct.
v NEXTLVL
B2003142 B2003142
B2003130 B2003130
Explanation: System log entry only, no service action
Explanation: A problem occurred during the IPL of a required
partition.
Response: The I/O Adapter in the slot used for the
Response: The partition ID is in extended word one last successful IPL of the operating system was
as LP=xxx in decimal format. If word 3 is zero, then replaced with an I/O Processor. The IPL will continue
this SRC is informational and can be ignored. by searching for a valid load source device.
Otherwise there is a problem in the platform LIC. A Check the LPAR configuration if required, and ensure
nonzero bus number has no associated bus object. that the tagged I/O for the partition is correct.
Look for B700 69xx errors in the Serviceable Event
View and work those errors. B2003143 B2003143
If there are no serviceable B700 69xx errors, or if Explanation: System log entry only, no service action
correcting the errors did not correct this problem, required
contact your next level of support.
Response: The I/O Adapter in the slot used for the
Failing Item: last successful IPL of the operating system was
v NEXTLVL removed. The IPL will continue by searching for a valid
load source device.
B2003135 B2003135 Check the LPAR configuration if required, and ensure
that the tagged I/O for the partition is correct.
Explanation: A problem occurred during the IPL of a
partition.
B2003144 B2003144
Response: The partition ID is in extended word one
as LP=xxx in decimal format. An unknown bus type Explanation: System log entry only, no service action
was detected. required
Failing Item: Response: The I/O Processor in the slot used for the
v NEXTLVL last successful IPL of the operating system was
removed. The IPL will continue by searching for a valid
load source device.
B2003140 B2003140
Check the LPAR configuration if required, and ensure
Explanation: A problem occurred during the IPL of a that the tagged I/O for the partition is correct.
partition.
Response: The partition ID is in extended word one B2003145 B2003145
as LP=xxx in decimal format. The load source IOP is
not owned by the partition. This is a configuration Explanation: System log entry only, no service action
problem in the partition. Have the customer required
reconfigure the partition to have the intended load Response: The virtual adapter type specified is
source IOP. invalid. The IPL will attempt to continue.
If there is not a configuration problem then contact Check the LPAR configuration, if required, and ensure
your next level of support. that the virtual adapter type selected for this partition
Failing Item: is valid.
540 System reference codes (Bxxx)
B2003200 • B2005117
B2003200 B2003200 B2005106 B2005106
Explanation: A problem occurred during the IPL of a Explanation: A problem occurred during the IPL of a
partition. partition.
Response: The partition ID is in extended word one Response: The partition ID is in extended word one
as LP=xxx in decimal format. as LP=xxx in decimal format. There is not enough
space to contain the partition main storage dump.
This error indicates a failure during a search for the
load source. There may be a number of these failures Contact your next level of support.
prior to finding a good load source. This is normal.
Failing Item:
Look for SRCs in the Serviceable Event View logged at v NEXTLVL
the time the partition was performing an IPL.
If a B2xx3110 error is logged, a B2xx3200 may be B2005109 B2005109
posted to the control panel. Work the B2xx3110 error in
the Serviceable Event View. If the system IPL hangs at Explanation: A problem occurred during the IPL of a
B2xx3200 and you cannot check the SRC history, partition.
perform the actions indicated for the B2xx3110 SRC. Response: The partition ID is in extended word one
as LP=xxx in decimal format. There was a partition
B2004158 B2004158 main storage dump problem. Contact your next level of
support.
Explanation: A problem occurred during the IPL of a
partition. Failing Item:
v NEXTLVL
Response: The partition ID is in extended word one
as LP=xxx in decimal format.
B2005114 B2005114
This error indicates a failure during a search for the
load source. It is usual for a number of these failures to Explanation: A problem occurred during the IPL of a
occur prior to finding a valid load source. This is partition.
normal.
Response: The partition ID is in extended word one
Look for SRCs in the Serviceable Event View logged at as LP=xxx in decimal format. There is not enough
the time the partition was performing an IPL. space to contain the partition main storage dump.
Contact your next level of support.
If a B2xx3110 error is logged, a B2xx3200 may be
posted to the control panel. Work the B2xx3110 error in Failing Item:
the Serviceable Event View. v NEXTLVL
If the system IPL hangs at B2xx3200 and you cannot
check the SRC history, perform the actions indicated for B2005115 B2005115
the B2xx3110 SRC.
Explanation: A problem occurred during the IPL of a
If there are other SRCs in the Serviceable Event View, partition.
then work those errors.
Response: The partition ID is in extended word one
If this SRC is posted on the control panel and there are as LP=xxx in decimal format. There was an error
no other SRCs listed in the Serviceable Event View, reading the partition's main storage dump from the
then perform LICIP15. partition's load source into main storage.
Failing Item:
B2004400 B2004400
v NEXTLVL
Explanation: A problem occurred during the IPL of a
partition.
B2005117 B2005117
Response: The partition ID is in extended word one
as LP=xxx in decimal format. Explanation: A problem occurred during the IPL of a
partition.
A failure occurred. Critical resources could not be
provided for this operation. The IPL is terminated. Response: The partition ID is in extended word one
as LP=xxx in decimal format. A partition main storage
Contact your next level of support. dump has occurred but cannot be written to the load
source device because a valid dump already exists.
Failing Item:
v NEXTLVL Use the Main Storage Dump Manager to rename or
copy the current main storage dump.
(B2xx) Reference codes 541
B2005121 • B2005149
Failing Item:
B2005135 B2005135
v SVCDOCS
Explanation: A problem occurred during the IPL of a
partition.
B2005121 B2005121
Response: The partition ID is in extended word one
Explanation: A problem occurred during the IPL of a as LP=xxx in decimal format. There was an error
partition. writing the partition's main storage dump to the
Response: The partition ID is in extended word one partition's load source.
as LP=xxx in decimal format. There was an error Failing Item:
writing the partition's main storage dump to the
v NEXTLVL
partition's load source.
Failing Item:
B2005137 B2005137
v NEXTLVL
Explanation: A problem occurred during the IPL of a
partition.
B2005122 B2005122
Response: The partition ID is in extended word one
Explanation: System log entry only, no service action as LP=xxx in decimal format. There was an error
required writing the partition's main storage dump to the
Response: A problem occurred during the IPL of a partition's load source.
partition. Failing Item:
The partition ID is in extended word one as LP=xxx in v NEXTLVL
decimal format.
An error occurred when writing the partition's main B2005145 B2005145
storage dump to the partition's load source. No service
Explanation: A problem occurred during the IPL of a
action required.
partition.
Response: The partition ID is in extended word one
B2005123 B2005123
as LP=xxx in decimal format. There was an error
Explanation: System log entry only, no service action writing the partition's main storage dump to the
required partition's load source.
Response: A problem occurred during the IPL of a Failing Item:
partition. v NEXTLVL
The partition ID is in extended word one as LP=xxx in
decimal format. B2005148 B2005148
An error occurred when writing the partition's main Explanation: A problem occurred during the IPL of a
storage dump to the partition's load source. No service partition.
action required.
Response: The partition ID is in extended word one
as LP=xxx in decimal format. An error occurred while
B2005127 B2005127 doing a main storage dump that would have caused
Explanation: Timeout occurred during a main store another main storage dump.
dump IPL Contact your next level of support.
Response: There was not enough memory available Failing Item:
for the dump to complete before the timeout occurred.
v NEXTLVL
The partition is currently in a failed state. Retry the
MSD IPL, or else power on the partition normally.
B2005149 B2005149
Failing Item:
v SVCDOCS Explanation: A problem occurred during the IPL of a
partition.
Response: The partition ID is in extended word one
as LP=xxx in decimal format. An error occurred while
doing a Firmware Assisted Dump that would have
caused another Firmware Assisted Dump.
Contact your next level of support.
542 System reference codes (Bxxx)
B200541A • B2006006
Failing Item: as LP=xxx in decimal format.
v NEXTLVL A Firmware Assisted Dump did not complete due to a
copy error. Contact your next level of Support.
B200541A B200541A Failing Item:
Explanation: A problem occurred during a partition v NEXTLVL
Firmware Assisted Dump
Response: The partition ID is in extended word one B200543C B200543C
as LP=xxx in decimal format.
Explanation: System log entry only, no service action
A Firmware Assisted Dump did not complete due to a required
copy error. Contact your next level of support.
Response: A problem occurred during a partition
Failing Item: Firmware Assisted Dump. The dump completed
v NEXTLVL successfully but register information might be missing.
The partition ID is in extended word one as LP=xxx in
B200542A B200542A decimal format.
Explanation: A problem occurred during a partition
Firmware Assisted Dump B200543D B200543D
Response: The partition ID is in extended word one Explanation: A problem occurred during a partition
as LP=xxx in decimal format. Firmware Assisted Dump
A Firmware Assisted Dump did not complete due to a Response: The partition ID is in extended word one
read error. Contact your next level of support. as LP=xxx in decimal format.
Failing Item: A Firmware Assisted Dump did not complete due to a
copy error. Contact your next level of support.
v NEXTLVL
Failing Item:
B200542B B200542B v NEXTLVL
Explanation: A problem occurred during a partition
Firmware Assisted Dump B2006003 B2006003
Response: The partition ID is in extended word one Explanation: Firmware for the specified function
as LP=xxx in decimal format. cannot be loaded. The firmware resource and all
associated virtual and/or physical devices will not be
A Firmware Assisted Dump did not complete due to a available until the issue is resolved.
copy error. Contact your next level of support.
Response: Generate a PHYP and FSP dump and
Failing Item: contact the next level of support.
v NEXTLVL
Failing Item:
v NEXTLVL
B200543A B200543A
Explanation: A problem occurred during a partition B2006006 B2006006
Firmware Assisted Dump
Explanation: A problem occurred during the IPL of a
Response: The partition ID is in extended word one partition.
as LP=xxx in decimal format.
Response: The partition ID is in extended word one
A Firmware Assisted Dump did not complete due to a as LP=xxx in decimal format. A platform LIC error
copy error. Contact your next level of support. occurred when the partition's memory initialized. The
Failing Item: IPL will not continue.
v NEXTLVL Contact your next level of support.
Failing Item:
B200543B B200543B v NEXTLVL
Explanation: A problem occurred during a partition
Firmware Assisted Dump
Response: The partition ID is in extended word one
(B2xx) Reference codes 543
B2006008 • B2006110
B2006008 B2006008 B2006012 B2006012
Explanation: During the IPL of the partition, an error Explanation: A problem occurred during the IPL of a
was detected while trying to setup the partition for partition.
firmware use. The IPL of the partition will not
Response: The partition ID is in extended word one
continue.
as LP=xxx in decimal format. The partition's LID failed
Failing Item: to completely load into the partition's mainstore area.
v LICCODE Contact your next level of support.
Failing Item:
B2006009 B2006009
v NEXTLVL
Explanation: An active memory sharing partition is
attempting to use a paging space device for which it
B2006015 B2006015
does not have ownership.
Explanation: A problem occurred during the IPL of a
Response: N/A
partition.
Problem determination: Verify that the paging space
Response: The partition ID is in extended word one
device is not in use by another CEC, and then follow
as LP=xxx in decimal format.
the instructions below to initialize the paging space
device. 1) Power off the partition. 2) Verify that the The load source media is corrupted or not valid.
paging device is not currently in another CEC's
Reserved Pool. 3) Clear the paging space header of the Failing Item:
hdisk assigned to the partition. 4) Remove the paging v LSERROR
space from the Reserved Pool. 5) Add the just removed
paging space back into the Reserved Pool. 6) Activate
B2006025 B2006025
the partition. If this does not resolve the problem,
contact your next level of support. Explanation: A problem occurred during the IPL of a
partition.
Failing Item:
v SVCDOCS Response: The partition ID is in extended word one
as LP=xxx in decimal format.
B200600A B200600A This is a problem with the load source media being
corrupt or not valid.
Explanation: A problem occurred during the IPL of a
partition. Failing Item:
v LSERROR
Response: The partition could not reserve the memory
required for IPL.
B2006027 B2006027
Contact your next level of support.
Explanation: A problem occurred during the IPL of a
Failing Item:
partition.
v NEXTLVL
Response: The partition ID is in extended word one
as LP=xxx in decimal format.
B2006010 B2006010
A failure occurred when allocating memory for an
Explanation: A UUID for a partition was not internal object used for LID load operations. Ensure the
generated in the time allowed. partition was allocated enough main storage, verify
Response: Delete and recreate the partition. If the that no memory leaks are present, and then retry the
same failure occurs, contact your service provider. operation.
Failing Item:
B2006011 B2006011 v NEXTLVL
Explanation: An error occurred when retrieving the
UUID for the partition. B2006110 B2006110
Response: Delete and recreate the partition. If the Explanation: A problem occurred during the IPL of a
same failuer occurs, contact your service provider. partition.
Response: The partition ID is in extended word one
as LP=xxx in decimal format. Error on load source
device.
544 System reference codes (Bxxx)
B2006115 • B2008111
Failing Item: loading the VPD areas of the partition. Possible causes
v LSERROR are:
v Corrupted/unsupported load source media
B2006115 B2006115 v Insufficient resources allocated to the partition
v Unsupported partition configuration by the operating
Explanation: The IBM i lids needed for IPL are
system
compressed.
If the problem is due to media, replace the load source
B200690A B200690A media. If the problem is due to insufficient resources,
allocate enough resources to the partition. If the
Explanation: A problem occurred during the IPL of a
problem is due to unsupported partition configuration,
partition.
correct the partition configuration.
Response: An error occurred while copying Open
Failing Item:
Firmware into the partition load area. Contact your
next level of support. v SVCDOCS
Failing Item:
B2008106 B2008106
v NEXTLVL
Explanation: A problem occurred during the IPL of a
partition.
B2007200 B2007200
Response: The partition ID is in extended word one
Explanation: System log entry only, no service action
as LP=xxx in decimal format.
required
The IPL is terminated. Contact your next level of
Response: The partition ID is in extended word one
support.
as LP=xxx in decimal format. An error condition was
encountered when communicating with the load source Failing Item:
I/O Processor for the partition identified in the xx field v NEXTLVL
of the B2xx SRC.
This informational error indicates a failure resetting the B2008107 B2008107
I/O Processor in the preceding B2xx3200 error. This
may be normal. If there is a hardware failure there will Explanation: A problem occurred during the IPL of a
be a different serviceable event. If the system IPL hangs partition.
at B2xx7200 and you cannot check the SRC history, Response: The partition ID is in extended word one
perform the actions indicated for the B2xx3110 SRC. as LP=xxx in decimal format. There was a problem
getting a segment of main storage in the platform's
B2008080 B2008080 main store.
Explanation: System log entry only, no service action Failing Item:
required v LICCODE
B2008081 B2008081 B2008109 B2008109
Explanation: A problem occurred during the IPL of a Explanation: A problem occurred during the IPL of a
partition. partition.
Response: The partition ID is in extended word one Response: The partition ID is in extended word one
as LP=xxx in decimal format. An internal LIC timeout as LP=xxx in decimal format. A failure occurred. The
has occurred. The partition may continue to IPL but it IPL is terminated. Ensure that there is enough memory
may experience problems while running. to IPL the partition.
Failing Item: Failing Item:
v LICCODE v LICCODE
B2008105 B2008105 B2008111 B2008111
Explanation: A problem occurred during the IPL of a Explanation: A problem occurred during the IPL of a
partition. partition.
Response: The partition ID is in extended word one Response: The partition ID is in extended word one
as LP=xxx in decimal format. There was a failure as LP=xxx in decimal format.
(B2xx) Reference codes 545
B2008112 • B2008125
Contact your next level of support.
B2008116 B2008116
Failing Item:
Explanation: The NvRam required for the partition
v NEXTLVL could not be obtained.
Problem determination: The amount of Nvram
B2008112 B2008112 needed to for the partition is unavailable. Free up some
Explanation: A problem occurred during the IPL of a nvram by deleting partitions that are not longer
partition. needed.
Response: The partition ID is in extended word one Failing Item:
as LP=xxx in decimal format. A failure occurred. The v SVCDOCS
IPL is terminated. v LICCODE
Failing Item:
v LICCODE B2008117 B2008117
Explanation: A problem occurred during the IPL of a
B2008113 B2008113 partition.
Explanation: A problem occurred during the IPL of a Response: Partition did not IPL due to platform
partition. Licensed Internal Code error.
Response: The partition ID is in extended word one Contact your next level of support.
as LP=xxx in decimal format. A problem occurred on
Failing Item:
the path to the load source for the partition.
v NEXTLVL
There was an error mapping memory for the partition's
IPL. Call your next level of support.
B2008121 B2008121
Failing Item:
Explanation: A problem occurred during the IPL of a
v LICCODE
partition.
Response: Partition did not IPL due to platform
B2008114 B2008114
Licensed Internal Code error.
Explanation: A problem occurred during the IPL of a
Contact your next level of support.
partition.
Failing Item:
Response: The partition ID is in extended word one
as LP=xxx in decimal format. A problem occurred on v NEXTLVL
the path to the load source for the partition.
There was a failure verifying VPD for the partition's B2008123 B2008123
resources during IPL. Call your next level of support. Explanation: A problem occurred during the IPL of a
Failing Item: partition.
v LICCODE Response: Partition did not IPL due to platform
Licensed Internal Code error.
B2008115 B2008115 Contact your next level of support.
Explanation: A problem occurred during the IPL of a Failing Item:
partition. v NEXTLVL
Response: The partition ID is in extended word one
as LP=xxx in decimal format. There was a low level B2008125 B2008125
partition to partition communication failure.
Explanation: A problem occurred during the IPL of a
Failing Item: partition.
v LICCODE
Response: Partition did not IPL due to platform
Licensed Internal Code error.
Contact your next level of support.
Failing Item:
v NEXTLVL
546 System reference codes (Bxxx)
B2008127 • B2008150
partition. The IPL continued without retrieving location
B2008127 B2008127
code information for a slot or a bus.
Explanation: A problem occurred during the IPL of a
The partition ID is in extended word one as LP=xxx in
partition.
decimal format. An error occurred while retrieving a
Response: Partition did not IPL due to platform location code.
Licensed Internal Code error.
Contact your next level of support. B2008142 B2008142
Failing Item: Explanation: System log entry only, no service action
v NEXTLVL required
Response: A problem occurred during the IPL of a
B2008129 B2008129 partition. The IPL continued without retrieving the port
location labels for an embedded slot.
Explanation: A problem occurred during the IPL of a
partition. The partition ID is in extended word one as LP=xxx in
decimal format.
Response: Partition did not IPL due to platform
Licensed Internal Code error.
B2008143 B2008143
Contact your next level of support.
Explanation: System log entry only, no service action
Failing Item: required
v NEXTLVL
Response: A problem occurred during the IPL of a
partition. The IPL continued without all available slot
B200813A B200813A information.
Explanation: A problem occurred during the IPL of a The partition ID is in extended word one as LP=xxx in
partition. decimal format.
Response: A problem occurred associating the
partition terminal to the console serial port. This B2008144 B2008144
association is only attempted when in Manufacturing
Explanation: System log entry only, no service action
Default Configuration (MDC) mode.
required
There may be a service processor problem. Check for
Response: A problem occurred during the IPL of a
firmware updates and install them. If there are no
partition. The IPL continued without all available
firmware updates available, look for and correct errors
processor information.
with SRCs of the form B1xxxxxx in the Serviceable
Event View. If that does not resolve the problem, The partition ID is in extended word one as LP=xxx in
contact your next level of support. decimal format.
Failing Item:
v SVCDOCS B2008145 B2008145
Explanation: System log entry only, no service action
B2008140 B2008140 required
Explanation: System log entry only, no service action Response: A problem occurred during the IPL of a
required partition. The IPL continued without all available
physical I/O information.
Response: A problem occurred during the IPL of a
partition. The IPL continued without the VPD The partition ID is in extended word one as LP=xxx in
information for a slot. decimal format.
The partition ID is in extended word one as LP=xxx in
decimal format. An error occurred while retrieving a B2008150 B2008150
location code. Explanation: Platform LIC detected an error
Response: The partition ID is in extended word one
B2008141 B2008141 as LP=xxx in decimal format. A platform Licensed
Explanation: System log entry only, no service action Internal Code error occurred.
required Perform a platform dump and contact your next level
Response: A problem occurred during the IPL of a of support.
(B2xx) Reference codes 547
B2008151 • B200A100
Failing Item: v NEXTLVL
v NEXTLVL
B2009108 B2009108
B2008151 B2008151 Explanation: Phyp Internal Error
Explanation: Platform LIC detected an error Failing Item:
Response: The partition ID is in extended word one v LICCODE
as LP=xxx in decimal format. A platform Licensed
Internal Code error occurred.
B2009114 B2009114
The partition assigned resources beyond its maximum
Explanation: Obtaining the VTPM trusted system key
capacity. Use HMC, SDMC, IVM or ASMI to increase
from the core of the hypervisor has failed.
the Logical Memory Block (LMB) size and/or use
HMC, SDMC or IVM to reduce the number of virtual Response: SYSDUMP will be required for debugging.
devices for the partition.
Failing Item:
Failing Item: v LICCODE
v SVCDOCS
B2009115 B2009115
B2008152 B2008152
Explanation: Sending a change key message to the
Explanation: No active system processors VTPM has failed.
Response: Contact your next level of support. Response: Verify that the VTPM is operational,
consider collecting an LPADUMP and contact the next
Failing Item:
support level.
v NEXTLVL
Failing Item:
v LICCODE
B2008153 B2008153
Explanation: An unrecoverable memory error caused
B2009116 B2009116
a partition IPL to fail.
Explanation: VTPM returned an error when a key
Response: If you find a B123E504 or other memory
change was requested. This is a communications level
related srcs that require a service action, perform the
error.
actions indicated to resolve the error. Then close this
problem. Problem determination: Verify the VTPM is
operational e.g. "/usr/bin/tpm_readpcr -n 1", retry the
Problem determination: The failing memory may
chtskey operation and if error persists contact next
have been automatically deallocated or resolved. Retry
level of support.
the partition IPL. If the problem repeats, contact your
next level of support.. Failing Item:
Failing Item: v SVCDOCS
v SVCDOCS v LICCODE
B2008160 B2008160 B2009117 B2009117
Explanation: A problem occurred during the Explanation: Sending a power-state changed message
migration of a partition to the VTPM internal resource failed.
Response: Contact your next level of support.
B200A100 B200A100
Failing Item:
Explanation: A problem occurred after a partition
v NEXTLVL
ended abnormally.
Response: The partition ID is in extended word one
B2008161 B2008161
as LP=xxx in decimal format. This partition could not
Explanation: A problem occurred during the stay running and shut itself down.
migration of a partition
Work any error logs in the Serviceable Event View. If
Response: Contact your next level of support. there are no errors, contact your next level of support.
Failing Item: Failing Item:
548 System reference codes (Bxxx)
B200A101 • B200F000
v SVCDOCS
B200C148 B200C148
Explanation: Unable to restore state after failed main
B200A101 B200A101
store dump, Dump data in memory is not for the failed
Explanation: A problem occurred after a partition main store dump.
ended abnormally.
Response: The partition ID is in extended word one B200C158 B200C158
as LP=xxx in decimal format. This partition could not
Explanation: Unable to restore the hypervisor page
stay running and shut itself down.
table after a failed main store dump.
Work any error logs in the Serviceable Event View. If
there are no errors, contact your next level of support.
B200C1F0 B200C1F0
Failing Item:
Explanation: A problem occurred during a power off
v SVCDOCS a partition
Response: Internal platform Licensed Internal Code
B200A140 B200A140 error occurred during partition shutdown or re-IPL.
Explanation: A partition terminated due to a bad Contact your next level of support.
processor
Failing Item:
Response: A lower priority partition lost a usable
v NEXTLVL
processor to supply it to a higher priority partition
with a bad processor.
B200D150 B200D150
The partition ID is in extended word one as LP=xxx in
decimal format. Explanation: A problem occurred after a partition
ended abnormally.
If the partition is an IBM i Operating System partition,
main store will be saved to disk. The partition will be Response: The partition ID is in extended word one
powered off after the process is completed. as LP=xxx in decimal format. There was a
communications problem between this partition and
For all other partition types, the partition will power
code that handles resource allocation. Call your next
off immediately.
level of support.
Evaluate the entire LPAR configuration. Adjust
Failing Item:
partition profiles with the new number of processors
available in the system. v LICCODE
Failing Item:
B200E0AA B200E0AA
v SVCDOCS
Explanation: A problem occurred during a power off
a partition
B200B07B B200B07B
Response: During the partition IPL, the partition
Explanation: System log entry only, no service action
terminal was associated to the console serial port.
required
During partition shutdown, the unassociation of the
partition terminal to the console serial port failed.
B200B215 B200B215
There may be a service processor problem. Check for
Explanation: A problem occurred after a partition firmware updates and install them. If there are no
ended abnormally. firmware updates available, look for and correct errors
with SRCs of the form B1xxxxxx in the Serviceable
Response: The partition ID is in extended word one Event View. If that does not resolve the problem,
as LP=xxx in decimal format. There was a contact your next level of support.
communications problem between this partition's
service processor and the platform's service processor. Failing Item:
The platform will need to be re-IPLed before that v SVCDOCS
partition can be used. Call your next level of support.
Failing Item: B200F000 B200F000
v NEXTLVL Explanation: Hypervisor Internal Error
Failing Item:
v LICCODE
(B2xx) Reference codes 549
B200F001 • B200F00B
for the partition's IPL timed out.
B200F001 B200F001
Work any error logs for this partition in the Serviceable
Explanation: A problem occurred during the IPL of a
Event View. If there are no errors, contact your next
partition.
level of support.
Response: The partition ID is in extended word one
Failing Item:
as LP=xxx in decimal format. An operation has timed
out. v SVCDOCS
Ignore this error if there are other serviceable errors.
Work those error logs for this partition and for the B200F007 B200F007
platform from the Serviceable Event View. If there are Explanation: A problem occurred during a power off
no errors, contact your next level of support. a partition
Failing Item: Response: The partition ID is in extended word one
v SVCDOCS as LP=xxx in decimal format. A problem occurred on
the path to the load source for the partition.
B200F003 B200F003 A timeout occurred during the process of trying to stop
a partition from running. Contact your next level of
Explanation: A problem occurred during the IPL of a
support.
partition.
Failing Item:
Response: The partition ID is in extended word one
as LP=xxx in decimal format. Partition processors did v LICCODE
not start LIC within the timeout window.
Capture a Partition Dump and call your next level of B200F008 B200F008
support. Explanation: A problem occurred during the IPL of a
Failing Item: partition.
v NEXTLVL Response: During an IPL, a timeout occurred while
waiting for a ready message from the partition.
B200F004 B200F004 Look for other errors. Re-IPL the partition to recover.
Explanation: System log entry only, no service action
required B200F009 B200F009
Response: A system request to power off a partition Explanation: System log entry only, no service action
failed. required
The partition ID is in extended word one as LP=xxx in Response: During an IPL, a timeout occurred while
decimal format. The partition did not respond to a waiting for a response to a message.
system request to power off the partition. This partition
had a communications problem. Look for other errors. Re-IPL the partition to recover.
If the partition is an IBM i Operating System partition,
capture a Partition Dump. Contact your next level of B200F00A B200F00A
support. Explanation: System log entry only, no service action
required
B200F005 B200F005 Response: During an IPL, a timeout occurred while
Explanation: System log entry only, no service action waiting for a response to a message.
required Look for other errors. If this SRC is displayed in the
Response: The partition ID is in extended word one operator panel, then panel function 34 might be used to
as LP=xxx in decimal format. The partition did not retry the current IPL while the partition is still in the
respond to a system request to power off the partition. failed state.
B200F006 B200F006 B200F00B B200F00B
Explanation: A problem occurred during the IPL of a Explanation: System log entry only, no service action
partition. required
Response: The partition ID is in extended word one Response: During an IPL, a timeout occurred while
as LP=xxx in decimal format. The code load operation waiting for a response to a message.
550 System reference codes (Bxxx)
B200F00C • B2D03004
Look for other errors. If this SRC is displayed in the
B200F011 B200F011
operator panel, then panel function 34 might be used to
retry the current IPL while the partition is still in the Explanation: A timeout has occured waiting for a
failed state. response to an internal message sent to the Hypervisor.
Failing Item:
B200F00C B200F00C v LICCODE
Explanation: System log entry only, no service action
required B2D03001 B2D03001
Response: During an IPL, a timeout occurred while Explanation: VSP-initiated RSCDUMP of RPA
waiting for a response to a message. partition's PFW content.
Look for other errors. If this SRC is displayed in the Response: No service action required.
operator panel, then panel function 34 might be used to
retry the current IPL while the partition is still in the
failed state. B2D03002 B2D03002
Explanation: VSP-initiated RSCDUMP of IBM i
B200F00D B200F00D partition's SLIC bootloader and PFW content.
Explanation: Timeout occurred during a main store Response: No service action required.
dump IPL
Response: If this SRC is displayed in the operator B2D03004 B2D03004
panel during a main store dump IPL, then panel Explanation: Hypervisor initiated an LPADUMP for
function 34 might be used to retry the current main an internal resource.
store dump IPL while the partition is in the failed state.
B200F00E B200F00E
Explanation: Hypervisor internal communication
failure.
B200F00F B200F00F
Explanation: Hypervisor internal communication
failure. LPADUMP initiated for the failed resource.
Response: Collect the LPADUMP and look for
additional B400xxxx Serviceable Events which occurred
around the same time as this SRC.
Failing Item:
v SVCDOCS
B200F010 B200F010
Explanation: PHYP detected that the specified
partition took too long to process the Integrated Fabric
Management (IFM) data. IFM operations for the
partition may not be complete.
Problem determination: A reboot of the offending
partition may clear up the error
Failing Item:
v LICCODE
(B2xx) Reference codes 551
552 System reference codes (Bxxx)
(B3xx) Reference codes
These error codes indicate a problem in the connection monitoring between the management console and
a partition that is running on the managed system.
The management console logs these error codes but does not report them to the operating systems
running on the managed system.
Explanation: HMC or partition connection monitoring
B3010001 B3010001
fault.
Explanation: Hardware Management Console (HMC)
Failing Item:
or partition connection monitoring fault
v NEXTLVL
Failing Item:
v NEXTLVL
B3010020 B3010020
Explanation: HMC or partition connection monitoring
B3010002 B3010002
fault.
Explanation: HMC or partition connection monitoring
Failing Item:
fault
v NEXTLVL
Response: Perform the following steps:
1. Verify the network between the HMC and the
B3010023 B3010023
partition by pinging in both directions. Correct any
problems that you detect. Explanation: HMC or partition connection monitoring
2. Reboot the HMC. fault.
Failing Item: Failing Item:
v PTNNTWK v NEXTLVL
B3010004 B3010004 B3010025 B3010025
Explanation: Hardware Management Console (HMC) Explanation: HMC or partition connection monitoring
or partition connection monitoring fault fault.
Failing Item: Failing Item:
v NEXTLVL v NEXTLVL
B3010012 B3010012 B3010026 B3010026
Explanation: HMC or partition connection monitoring Explanation: HMC or partition connection monitoring
fault. fault.
Failing Item: Failing Item:
v NEXTLVL v NEXTLVL
B3010013 B3010013 B3010027 B3010027
Explanation: HMC or partition connection monitoring Explanation: HMC or partition connection monitoring
fault. fault
Failing Item: Response: Before using the entry in the FRU List, do
the following:
v NEXTLVL
1. If you use short host names for the HMC and the
partitions, ensure that you have correctly set up the
B3010019 B3010019 short host names. For more information, see the
instructions in "Using Network Adapters to
© Copyright IBM Corp. 2010, 2013 553
B3010029 • B3030003
Communicate with Partitions" in the Installation and 4. The partition was cloned improperly and has the
Configuration Guide for the Hardware Management same Node Id as some other partition(s).
Console . Correct any problems that you find, then
verify that you can ping in both directions between For more information, see the instructions in "Using
the HMC and the partitions. Network Adapters to Communicate with Partitions" in
2. If you do not use short host names or if the the Installation and Configuration Guide for the
previous step does not correct the problem, use the Hardware Management Console
FRU List. Failing Item:
Failing Item: v NEXTLVL
v NEXTLVL
B3030001 B3030001
B3010029 B3010029 Explanation: The communication link between the
Explanation: HMC or partition connection monitoring service processor and the Hardware Management
fault. Console (HMC) failed.
Failing Item: Response:
v NEXTLVL
Note: Perform FSPSP33 . This error might be a
temporary condition caused by either the HMC or the
B301002B B301002B system that the HMC is connected, being shutdown,
restarted, upgraded or other intermittent conditions.
Explanation: HMC or partition connection monitoring
While attempts are made to only report these errors
fault.
when a connection has been lost. It is important to
Failing Item: follow the procedures in the symbolic FRU list to
v NEXTLVL determine if there is still a connection problem and
how to resolve the issue.
B301002C B301002C Failing Item:
v SPNETWK
Explanation: HMC or partition connection monitoring
fault.
B3030002 B3030002
Failing Item:
v NEXTLVL Explanation: A single partition HMC link failed.
Response: Perform FSPSP33
B301002D B301002D
Note: This error might be a temporary condition
Explanation: HMC or partition connection monitoring caused by either the HMC or the system that the HMC
fault. is connected, being shutdown, restarted, upgraded or
Failing Item: other intermittent conditions. While attempts are made
to only report these errors when a connection has been
v NEXTLVL
lost. It is important to follow the procedures in the
symbolic FRU list to determine if there is still a
B3020001 B3020001 connection problem and how to resolve the issue.
Explanation: Management Console (MC) RMC Failing Item:
connection to partition monitoring fault v SPNETWK
Response: The Management Console (MC) either has v PTNNTWK
no, or lost, RMC connection to the partition. Check for
the following possible causes:
B3030003 B3030003
1. The partition does not have network configured.
Explanation: Multiple partition HMC links failed.
2. The partition could be low on system resources.
Lacking space in /root or /var might cause no Response: Perform FSPSP33 .
RMC connection; extremely busy system would
cause network, and the RMC connection, to drop Note: This error might be a temporary condition
intermittently. caused by either the HMC or the system that the HMC
3. The firewall is not authenticated. This can be is connected, being shutdown, restarted, upgraded or
verified by ssh/telnet from the MC to the lpar and other intermittent conditions. While attempts are made
vice versa. to only report these errors when a connection has been
554 System reference codes (Bxxx)
B3030004 • B3030009
lost. It is important to follow the procedures in the symbolic FRU list to determine if there is still a
symbolic FRU list to determine if there is still a connection problem and how to resolve the issue.
connection problem and how to resolve the issue.
Failing Item:
Failing Item: v SPNETWK
v SPNETWK
v PTNNTWK B3030007 B3030007
v HMCMTWK
Explanation: A single HMC link to more than one
managed system occurred.
B3030004 B3030004
Response: Perform FSPSP33 .
Explanation: All partition links for a single system to
HMC failed. Note: This error might be a temporary condition
caused by either the HMC or the system that the HMC
Response: Perform FSPSP33 .
is connected, being shutdown, restarted, upgraded or
other intermittent conditions. While attempts are made
Note: This error might be a temporary condition
to only report these errors when a connection has been
caused by either the HMC or the system that the HMC
lost. It is important to follow the procedures in the
is connected, being shutdown, restarted, upgraded or
symbolic FRU list to determine if there is still a
other intermittent conditions. While attempts are made
connection problem and how to resolve the issue.
to only report these errors when a connection has been
lost. It is important to follow the procedures in the Failing Item:
symbolic FRU list to determine if there is still a v SPNETWK
connection problem and how to resolve the issue.
v HMCNTWK
Failing Item:
v SPNETWK B3030008 B3030008
v PTNNTWK
Explanation: One HMC link to another single HMC
failed.
B3030005 B3030005
Response: Perform FSPSP33 .
Explanation: All system links from one system to a
single HMC failed. Note: This error might be a temporary condition
caused by either the HMC or the system that the HMC
Response: Perform FSPSP33 .
is connected, being shutdown, restarted, upgraded or
other intermittent conditions. While attempts are made
Note: This error might be a temporary condition
to only report these errors when a connection has been
caused by either the HMC or the system that the HMC
lost. It is important to follow the procedures in the
is connected, being shutdown, restarted, upgraded or
symbolic FRU list to determine if there is still a
other intermittent conditions. While attempts are made
connection problem and how to resolve the issue.
to only report these errors when a connection has been
lost. It is important to follow the procedures in the Failing Item:
symbolic FRU list to determine if there is still a v SPNETWK
connection problem and how to resolve the issue.
v HMCNTWK
Failing Item:
v SPNETWK B3030009 B3030009
Explanation: One HMC link to more than one HMC
B3030006 B3030006 occurred.
Explanation: The links between a single HMC and a Response: Perform FSPSP33 .
single managed system failed.
Response: Perform FSPSP33 . Note: This error might be a temporary condition
caused by either the HMC or the system that the HMC
Note: This error might be a temporary condition is connected, being shutdown, restarted, upgraded or
caused by either the HMC or the system that the HMC other intermittent conditions. While attempts are made
is connected, being shutdown, restarted, upgraded or to only report these errors when a connection has been
other intermittent conditions. While attempts are made lost. It is important to follow the procedures in the
to only report these errors when a connection has been symbolic FRU list to determine if there is still a
lost. It is important to follow the procedures in the connection problem and how to resolve the issue.
(B3xx) Reference codes 555
B303000A • B303000F
Failing Item: v HMCMTWK
v SPNETWK
v HMCMTWK B303000D B303000D
Explanation: Multiple HMCs lost links to multiple
B303000A B303000A managed systems.
Explanation: The HMC lost links to all managed Response: Perform FSPSP33 .
systems.
Note: This error might be a temporary condition
Response: Perform FSPSP33 .
caused by either the HMC or the system that the HMC
is connected, being shutdown, restarted, upgraded or
Note: This error might be a temporary condition
other intermittent conditions. While attempts are made
caused by either the HMC or the system that the HMC
to only report these errors when a connection has been
is connected, being shutdown, restarted, upgraded or
lost. It is important to follow the procedures in the
other intermittent conditions. While attempts are made
symbolic FRU list to determine if there is still a
to only report these errors when a connection has been
connection problem and how to resolve the issue.
lost. It is important to follow the procedures in the
symbolic FRU list to determine if there is still a Failing Item:
connection problem and how to resolve the issue. v SPNETWK
Failing Item: v HMCMTWK
v SPNETWK
B303000E B303000E
B303000B B303000B Explanation: The Network Interface Card (NIC) failed.
Explanation: Multiple HMCs lost links to a single Response: Use the error codes offered in the HMC
managed system. Focal Point to diagnose and repair the problem. For
Response: Perform FSPSP33 . more information, see Using Service Focal Point .
Note: This error might be a temporary condition Note: This error might be a temporary condition
caused by either the HMC or the system that the HMC caused by either the HMC or the system that the HMC
is connected, being shutdown, restarted, upgraded or is connected, being shutdown, restarted, upgraded or
other intermittent conditions. While attempts are made other intermittent conditions. While attempts are made
to only report these errors when a connection has been to only report these errors when a connection has been
lost. It is important to follow the procedures in the lost. It is important to follow the procedures in the
symbolic FRU list to determine if there is still a symbolic FRU list to determine if there is still a
connection problem and how to resolve the issue. connection problem and how to resolve the issue.
Failing Item: Failing Item:
v SPNETWK v SYSNTWK
v HMCMTWK
B303000F B303000F
B303000C B303000C Explanation: A single partition HMC link failure
occurred on a redundant path.
Explanation: Multiple HMCs lost links to multiple
managed systems. Response: Perform FSPSP33 .
Response: Perform FSPSP33 .
Note: This error might be a temporary condition
caused by either the HMC or the system that the HMC
Note: This error might be a temporary condition
is connected, being shutdown, restarted, upgraded or
caused by either the HMC or the system that the HMC
other intermittent conditions. While attempts are made
is connected, being shutdown, restarted, upgraded or
to only report these errors when a connection has been
other intermittent conditions. While attempts are made
lost. It is important to follow the procedures in the
to only report these errors when a connection has been
symbolic FRU list to determine if there is still a
lost. It is important to follow the procedures in the
connection problem and how to resolve the issue.
symbolic FRU list to determine if there is still a
connection problem and how to resolve the issue. Failing Item:
Failing Item: v SPNETWK
v SPNETWK v PTNNTWK
556 System reference codes (Bxxx)
B3030010 • B3031006
v MAILBOX
B3030010 B3030010
Explanation: A single HMC link to one HMC failure
B3031000 B3031000
occurred on a redundant path.
Explanation: Customer reported a console problem
when creating a serviceable event on the HMC user
B3030011 B3030011
interface.
Explanation: Server firmware connection monitoring
Response: Contact the customer for more information
to the flexible service processor failed.
about the problem.
Response: Perform FSPSP33 .
B3031001 B3031001
Note: This error might be a temporary condition
caused by either the HMC or the system that the HMC Explanation: Customer reported a power problem
is connected, being shutdown, restarted, upgraded or when creating a serviceable event on the HMC user
other intermittent conditions. While attempts are made interface.
to only report these errors when a connection has been
Response: Contact the customer for more information
lost. It is important to follow the procedures in the
about the problem.
symbolic FRU list to determine if there is still a
connection problem and how to resolve the issue.
B3031002 B3031002
Failing Item:
v SPNETWK Explanation: Customer reported a processor problem
when creating a serviceable event on the HMC user
interface.
B3030012 B3030012
Response: Contact the customer for more information
Explanation: Flexible service processor connection about the problem.
monitoring of server firmware failed
Response: Perform FSPSP33 . B3031003 B3031003
Note: This error might be a temporary condition Explanation: Customer reported a LAN problem
caused by either the HMC or the system that the HMC when creating a serviceable event on the HMC user
is connected, being shutdown, restarted, upgraded or interface.
other intermittent conditions. While attempts are made Response: Contact the customer for more information
to only report these errors when a connection has been about the problem.
lost. It is important to follow the procedures in the
symbolic FRU list to determine if there is still a
connection problem and how to resolve the issue. B3031004 B3031004
Failing Item: Explanation: Customer reported a software problem
when creating a serviceable event on the HMC user
v SPNETWK
interface.
Response: Contact the customer for more information
B3030013 B3030013
about the problem.
Explanation: The communication path (mailbox)
between server firmware and the flexible service
B3031005 B3031005
processor failed.
Explanation: Customer reported a input/output (I/O)
Response: Perform FSPSP33 .
problem when creating a serviceable event on the HMC
user interface.
Note: This error might be a temporary condition
caused by either the HMC or the system that the HMC Response: Contact the customer for more information
is connected, being shutdown, restarted, upgraded or about the problem.
other intermittent conditions. While attempts are made
to only report these errors when a connection has been
B3031006 B3031006
lost. It is important to follow the procedures in the
symbolic FRU list to determine if there is still a Explanation: Customer reported a problem when
connection problem and how to resolve the issue. creating a serviceable event on the HMC user interface.
Failing Item: Response: Contact the customer for more information
v SPNETWK about the problem.
(B3xx) Reference codes 557
B3031007 • B3036601
B3031007 B3031007 B3031106 B3031106
Explanation: Customer tested problem reporting by Explanation: Customer reported a problem when
creating a serviceable event on the HMC user interface. creating a serviceable event on the HMC user interface.
Response: Contact the customer for more information Response: Contact the customer for more information
about the problem. about the problem.
B3031100 B3031100 B3031107 B3031107
Explanation: Customer reported a problem when Explanation: Customer tested problem reporting by
creating a serviceable event on the HMC user interface. creating a serviceable event on the HMC user interface.
Response: Contact the customer for more information Response: Contact the customer for more information
about the problem. about the problem.
B3031101 B3031101 B3036600 B3036600
Explanation: Customer reported a power problem Explanation: The HMC failed to retrieve a dump from
when creating a serviceable event on the HMC user a managed system. If you have a redundant HMC
interface. environment, a peer HMC might have retrieved the
dump. This might be a temporary problem.
Response: Contact the customer for more information
about the problem. Response: After receiving this error, perform the
following steps:
B3031102 B3031102 1. Ensure that there is connectivity between this HMC
and managed System reported.
Explanation: Customer reported a processor problem
2. Use the manage dumps utility to determine if
when creating a serviceable event on the HMC user
dumps have been received from the managed
interface.
system.
Response: Contact the customer for more information 3. If there is a peer HMC managing the same system,
about the problem. also check that HMC. Managed System Dumps can
be retrieved by any HMC connected to the system.
B3031103 B3031103 If there is a current dump from the managed system
reported in the error, than the available dump has
Explanation: Customer reported a LAN problem been retrieved.
when creating a serviceable event on the HMC user
interface.
B3036601 B3036601
Response: Contact the customer for more information
about the problem. Explanation: The HMC failed to retrieve a platform
system dump from the managed system. If you have a
redundant HMC environment, a peer HMC might have
B3031104 B3031104 retrieved the dump. This might be a temporary
problem.
Explanation: Customer reported a software problem
when creating a serviceable event on the HMC user Response: After receiving this error, perform the
interface. following steps:
Response: Contact the customer for more information 1. Use the manage dumps utility to determine if a
about the problem. dump of that type has been received from the
managed system.
2. If you have a peer HMC managing the same
B3031105 B3031105
system, also check that HMC. Managed System
Explanation: Customer reported a input/output (I/O) Dumps can be retrieved by any HMC connected to
problem when creating a serviceable event on the HMC the system. If there is a current dump of the type
user interface. that failed from the managed system reported in the
error, than the available dump of that type has been
Response: Contact the customer for more information
retrieved.
about the problem.
558 System reference codes (Bxxx)
B3036602 • B3112420
B3036602 B3036602 B3036625 B3036625
Explanation: The HMC failed to retrieve a dump from Explanation: Primary HMC arbitration failure for
the service processor. If you have a redundant HMC domain {0} with peers {1}.
environment, a peer HMC might have retrieved the
Response:
dump. This might be a temporary problem.
Response: After receiving this error, perform the Note: Domain indicates which domain the managed
following steps: system belongs to. Peers indicate what HMC are also
1. Use the manage dumps utility to determine if a connected to the service processor.
dump of that type has been received from the After receiving this error, perform the following steps:
managed system.
2. If you have a peer HMC managing the same This error code indicates that this HMC could not
system, also check that HMC. Managed System communicate with the service processor to either set
Dumps can be retrieved by any HMC connected to itself as a primary or to determine if other HMCs are
the system. If there is a current dump of the type connected. To resolve this issue ensure that there is
that failed from the managed system reported in the connectivity to the service processor and the other
error, than the available dump of that type has been HMC connected to the managed system.
retrieved.
B3100011 B3100011
B3036604 B3036604 Explanation: The DVD RW drive or disk has failed.
Explanation: The HMC failed to retrieve a power
subsystem dump from the managed system. If you B3100500 B3100500
have a redundant HMC environment, a peer HMC
might have retrieved the dump. This might be a Explanation: Ethernet network failure
temporary problem. Response: Do the following:
Response: After receiving this error, perform the 1. Reseat your Ethernet card.
following steps: 2. Check your Ethernet cable connections.
1. Use the manage dumps utility to determine if a 3. If the previous actions do not resolve the problem,
dump of that type has been received from the contact your next level of support.
managed system.
Failing Item:
2. If you have a peer HMC managing the same
system, also check that HMC. Managed System v NEXTLVL
Dumps can be retrieved by any HMC connected to
the system. If there is a current dump of the type B3112420 B3112420
that failed from the managed system reported in the
error, than the available dump of that type has been Explanation: Ethernet network failure
retrieved.
Response: Do the following:
1. Reseat your Ethernet card.
B3036620 B3036620
2. Check your Ethernet cable connections.
Explanation: Primary HMC arbitration failure for 3. If the previous actions do not resolve the problem,
domain {0} with peers {1}. contact your next level of support.
Response: Failing Item:
v NEXTLVL
Note: Domain indicates which domain the managed
system belongs to. Peers indicate what HMC are also
connected to the service processor.
After receiving this error, perform the following steps:
This error code indicates that this HMC did receive
primary information from a peer HMC. To resolve this
issue ensure that there is connectivity to the service
processor and the other HMC connected to the
managed system.
(B3xx) Reference codes 559
B3112420
560 System reference codes (Bxxx)
(B4xx) Reference codes
Explanation: A bad parameter was passed to a critical
B4000003 B4000003
function.
Explanation: An attempt to setup an I/O mapping
Response: Collect a resource dump for the firmware
with the Hypervisor has failed.
resource that logged the error.
Failing Item:
B4000100 B4000100
v SVCDOCS
Explanation: An interrupt source could not be masked
due to an error from the Hypervisor.
B4008101 B4008101
Response: Collect a resource dump for the firmware
resource that logged the error. Explanation: Not all error tracing sessions could be
instantiated.
Failing Item:
v SVCDOCS
B4008102 B4008102
Explanation: The current time could not be retrieved.
B4000101 B4000101
Response: Collect a resource dump for the firmware
Explanation: An interrupt source could not be
resource that logged the error.
unmasked due to an error from the Hypervisor.
Failing Item:
Response: Collect a resource dump for the firmware
resource that logged the error. v SVCDOCS
Failing Item:
B4008103 B4008103
v SVCDOCS
Explanation: The current timebase frequency could
not be retrieved.
B4000102 B4000102
Response: Collect a resource dump for the firmware
Explanation: The directory is full and a new entry
resource that logged the error.
could not be added.
Failing Item:
B4000201 B4000201 v SVCDOCS
Explanation: An allocation of memory has failed.
B400A000 B400A000
Response: Collect a resource dump for the firmware
resource that logged the error. Explanation: The close of a virtual device driver has
failed.
Failing Item:
Response: Collect a resource dump for the firmware
v SVCDOCS
resource that logged the error.
Failing Item:
B4000202 B4000202
v SVCDOCS
Explanation: An unrecoverable assert has occurred.
Response: Collect a resource dump for the firmware B400A001 B400A001
resource that logged the error.
Explanation: The schedule of a task for a virtual
Failing Item: device driver has failed.
v SVCDOCS
Response: Collect a resource dump for the firmware
resource that logged the error.
B4003004 B4003004
Failing Item:
Explanation: Firmware initiated LPADUMP v SVCDOCS
B4008001 B4008001 B400A0A0 B400A0A0
© Copyright IBM Corp. 2010, 2013 561
B400A0A1 • B400F104
Explanation: An invalid command was received by
B400F104 B400F104
the management channel.
Explanation: System firmware Error
B400A0A1 B400A0A1 Response: Send the resource dump to the next level of
support.
Explanation: Debug output failed to be sent to the
Hypervisor. Failing Item:
v SVCDOCS
B400A0A2 B400A0A2
Explanation: A debug handler for the management
channel failed to initialize.
Response: Collect a resource dump for the firmware
resource that logged the error.
Failing Item:
v SVCDOCS
B400B001 B400B001
Explanation: The Virtual Trusted Platform Module
(VTPM) could not seed its Psuedo-Random Number
Generator (PRNG).
Response: Collect a resource dump for the firmware
resource that logged the error.
Failing Item:
v SVCDOCS
B400B002 B400B002
Explanation: The Virtual Trusted Platform Module
(VTPM) initialization failed.
Response: Collect a resource dump for the firmware
resource that logged the error.
Failing Item:
v SVCDOCS
B400B003 B400B003
Explanation: The Virtual Trusted Platform Module
(VTPM) has entered the fail state.
Response: Collect a resource dump for the firmware
resource that logged the error.
Failing Item:
v SVCDOCS
B400B004 B400B004
Explanation: The Virtual Trusted Platform Module
(VTPM) communication channel failed to initialize.
Response: Collect a resource dump for the firmware
resource that logged the error.
Failing Item:
v SVCDOCS
562 System reference codes (Bxxx)
(B6xx) Reference codes
Failing Item:
B6000000 B6000000
v LICIP08
Explanation: Operating system status code
v AJDG301
Response: This reference code is for information only.
It is shown in the Product activity log as a side effect of
B6000107 B6000107
a condition that was detected by LIC.
Explanation: Main storage dump must be copied for
Normally, no action should be taken as a result of
service
information reference codes. However, to isolate the
root cause, use these suggestions: Response: The server detected an unrecoverable
1. Examine the date and time of the informational machine check condition.
reference code. Collect all the words of the SRC and the main store
2. Determine if any other reference codes have been dump and send to your system manufacturer for
logged at or before the same date and time. analysis.
3. Begin the service approach based on these other
logged errors. B6000109 B6000109
Explanation: An unrecoverable memory error
B6000102 B6000102 occurred
Explanation: A machine check occurred during IPL Response: Re-IPL the partition that terminated. Then,
Response: Words 2 to 9 of this SRC contain additional look for and correct errors with SRCs of the form
diagnostic information. Record SRC words 1 through 9 B1xxxxxx in the Serviceable Event View that indicate
before attempting to IPL again and report the problem the replacement of memory in the failing item list. If
to your Software Service Provider. there are no B1xxxxxx SRCs in the Serviceable Event
View that indicate a memory problem, perform a slow
boot by using Performing a slow boot in order to run
B6000103 B6000103 diagnostics on the memory. Then, look for and correct
Explanation: Main storage dump must be copied for errors with SRCs of the form B1xxxxxx in the
service Serviceable Event View.
Failing Item: Failing Item:
v LICIP01 v SVCDOCS
B6000104 B6000104 B6000202 B6000202
Explanation: Terminate Immediate reference code is Explanation: Unrecoverable read error
bad Response: Restore the Licensed Internal Code using
Failing Item: Utilities to install and restore IBM i Licensed Internal
Code.
v LICIP08
v AJDG301
B6000210 B6000210
B6000105 B6000105 Explanation: The system ASP has run out of disk
storage.
Explanation: More than one request to terminate the
system was issued Response: The out of storage condition in the system
ASP can be caused by an allocation failure in some
Failing Item: other system software. This could be a looping
v LICIP08 condition that continues to allocate storage. Contact
v AJDG301 your service representative for assistance with the Main
Storage Dump.
B6000106 B6000106
B6000231 B6000231
Explanation: Terminate Immediate data is not valid
© Copyright IBM Corp. 2010, 2013 563
B6000232 • B6000308
Explanation: Disk sanitize action completed v FI00302
successfully v FI00301
Response: No service action required. This entry is v AJDG301
logged for information only.
B6000299 B6000299
B6000232 B6000232
Explanation: Informational LIC state SRC.
Explanation: Disk sanitize action did not complete
successfully
B6000302 B6000302
Response: Provide the Product Activity Log entry to
Explanation: Recursion in exception handler
your next level of support for analysis.
Failing Item:
B6000244 B6000244 v LICIP08
v AJDG301
Explanation: Contact was lost with the device
indicated
B6000304 B6000304
Response: Do not power off the system.
Explanation: Component specific exception handler
Perform the procedure indicated in the failing item list.
return code not valid
Failing Item:
Failing Item:
v LICIP13
v LICIP08
v FI00580
v AJDG301
v FI00500
v FI00302
B6000305 B6000305
v FI00301
Explanation: Exception while storage management
v AJDG301
lock is held
Failing Item:
B6000255 B6000255
v LICIP08
Explanation: Contact was lost with the device
v AJDG301
indicated
Response: Do not power off the system.
B6000307 B6000307
Perform the procedure indicated in the failing item list.
Explanation: LIC exception code detected a problem
Failing Item:
Response: Component Specific Exception Handler
v LICIP13 recursion is detected in an IBM i Operating System
v FI00580 process.
v FI00500 Failing Item:
v FI00302 v LICIP08
v FI00301 v AJDG301
v AJDG301
B6000308 B6000308
B6000266 B6000266
Explanation: LIC exception code detected a problem
Explanation: Contact was lost with the device
Response: Component Specific Exception Handler
indicated
recursion is detected in an IBM i Operating System
Response: Do not power off the system. process.
Perform the procedure indicated in the failing item list. Failing Item:
Failing Item: v LICIP08
v LICIP13 v AJDG301
v FI00580
v FI00500
564 System reference codes (Bxxx)
B6000317 • B6000402
B6000317 B6000317 B6000329 B6000329
Explanation: Traceback for code not found Explanation: LIC exception code detected a problem
Failing Item: Failing Item:
v LICIP08 v LICIP08
v AJDG301 v AJDG301
B6000323 B6000323 B6000333 B6000333
Explanation: LIC exception code detected a problem Explanation: A branch to a bad address was
attempted
Failing Item:
v LICIP08 Failing Item:
v AJDG301 v LICIP08
v AJDG301
B6000324 B6000324
B6000334 B6000334
Explanation: LIC exception code detected a problem
Explanation: Exception Handler could not be removed
Failing Item:
v LICIP08 Failing Item:
v AJDG301 v LICIP08
v AJDG301
B6000325 B6000325
B6000335 B6000335
Explanation: LIC exception code detected a problem
Explanation: Code resumed to not valid address
Failing Item:
following exception
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6000326 B6000326
Explanation: LIC exception code detected a problem
B6000336 B6000336
Failing Item:
Explanation: LIC exception code detected a problem
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6000327 B6000327
Explanation: LIC exception code detected a problem
B6000401 B6000401
Failing Item:
Explanation: A machine check occurred during IPL
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6000328 B6000328
Explanation: LIC exception code detected a problem
B6000402 B6000402
Failing Item:
Explanation: A machine check occurred during
v LICIP08 authority initialization
v AJDG301
Failing Item:
v LICIP08
v AJDG301
(B6xx) Reference codes 565
B6000403 • B6000418
B6000403 B6000403 B6000411 B6000411
Explanation: Unhandled exception during IPL or Explanation: Unhandled exception in commit recovery
install
Failing Item:
Failing Item: v LICIP08
v LICIP08 v AJDG301
v AJDG301
B6000412 B6000412
B6000405 B6000405
Explanation: Unhandled exception in commit
Explanation: Unhandled exception in authority initialization
recovery
Failing Item:
Failing Item: v LICIP08
v LICIP08 v AJDG301
v AJDG301
B6000413 B6000413
B6000406 B6000406
Explanation: Rebuild of recovery object index failed
Explanation: Unhandled exception in data base
Failing Item:
recovery
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6000414 B6000414
Explanation: Install of operating system failed on read
B6000407 B6000407
from media
Explanation: Unhandled exception in data base
Failing Item:
initialization
v LICIP08
Failing Item:
v FI00300
v LICIP08
v AJDG301
B6000415 B6000415
Explanation: Create user profile failed
B6000408 B6000408
Failing Item:
Explanation: Unhandled exception in journal recovery
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6000417 B6000417
Explanation: Initiating the initial process failed
B6000409 B6000409
Failing Item:
Explanation: Unhandled exception in journal
synchronization v LICIP08
v AJDG301
Failing Item:
v LICIP08
B6000418 B6000418
v AJDG301
Explanation: The information loaded from the install
media is not valid
B6000410 B6000410
Failing Item:
Explanation: Unhandled exception in journal clean up
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
566 System reference codes (Bxxx)
B6000419 • B6000506
B6000419 B6000419 B6000440 B6000440
Explanation: The information loaded from the install Explanation: Termination code is not valid
media is not valid
Failing Item:
Failing Item: v LICIP08
v LICIP08 v AJDG301
v AJDG301
B6000441 B6000441
B6000420 B6000420
Explanation: Power off system command failed
Explanation: The information loaded from the install
Failing Item:
media is not valid
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6000443 B6000443
Explanation: Programmed IPL command failure
B6000421 B6000421
Failing Item:
Explanation: Bad return code creating a queue or
message v LICIP08
v AJDG301
Failing Item:
v LICIP08
B6000446 B6000446
v AJDG301
Explanation: Error during machine termination
B6000422 B6000422 Failing Item:
Explanation: The Load/Dump command failed v LICIP08
v AJDG301
Failing Item:
v LICIP08
B6000447 B6000447
v AJDG301
Explanation: Failure to reach MI boundary
B6000423 B6000423 Failing Item:
Explanation: LIC in IBMi has detected that the system v LICIP08
unit technology level or configuration is not supported v AJDG301
by the version and release of IBMi attemping to install.
The version and release of IBMi you are working with
will not install and not IPL on this system unit. B6000449 B6000449
Problem determination: Install on a system unit that Explanation: Exception in MI boundary manager
is supported by the version and release of IBMi that Failing Item:
you are working with.
v LICIP08
Failing Item: v AJDG301
v SVCDOCS
B6000506 B6000506
B6000439 B6000439
Explanation: Attempt to destroy a task with critical
Explanation: Opening the IPCF connection failed flag on
Failing Item: Failing Item:
v LICIP08 v LICIP08
v AJDG301 v AJDG301
(B6xx) Reference codes 567
B6000507 • B6000903
B6000507 B6000507 B6000801 B6000801
Explanation: A critical process terminated. This SRC Explanation: Invalid LID directory detected
will be in the LPAR's panel.
Response: During system IPL, the LIDMgr detected
LIC detected an attempt to terminate a process with its an I/O failure or media failure while trying to read the
critical flag set to ON. Normally this process will be LID directory.
SCPF.
Failing Item:
This is a secondary affect of the process termination v LICIP08
request for a critical process that was caused by a
v FI00070
system error condition that began process termination.
The system error condition that began process v FI00300
termination is most commonly a storage error or LIC v AJDG301
exception handling.
Response: Perform LICIP08 - save and send in the B6000802 B6000802
Main Store Dump, collect LIC and Product Activity
Logs. Explanation: LID directory unusable
Failing Item: Response: During system IPL, the LIDMgr detected
that the LID directory and associated Load Source is
v LICIP08 not usable.
v AJDG301
Reinstall the Licensed Internal Code by using Utilities
to install and restore IBM i Licensed Internal Code.
B6000607 B6000607
For more information, contact IBM Service Support.
Explanation: Maximum stack size exceeded in process
or task Failing Item:
v AJDG301
Failing Item:
v LICIP08
B6000901 B6000901
v AJDG301
Explanation: The LinkLoader has found its bad flag
ON
B6000620 B6000620
Response: This reference code is usually the result of
Explanation: Event management index is not usable a system termination while the LinkLoader is
Failing Item: performing its work.
v LICIP08 Reinstall the Licensed Internal Code by using Utilities
v AJDG301 to install and restore IBM i Licensed Internal Code.
B6000650 B6000650 B6000902 B6000902
Explanation: Resource management segment could Explanation: Unable to perform programmed IPL
not be created or extended Response: The LinkLoader was not successful in
Response: A main store dump was initiated. performing a programmed IPL.
Words 2 to 9 of this SRC contain additional diagnostic Perform a system IPL. If the problem persists, examine
information. Record SRC words 1 through 9. the main storage dump and determine the reason for
the failure of the programmed IPL.
Perform a system IPL and collect the Product activity
log and main store dump and provide them along with
the recorded SRC information to IBM Service Support. B6000903 B6000903
The problem may also be that there is not enough Explanation: The LinkLoader was not able to allocate
auxiliary storage. a segment
Failing Item: Response: Perform the D mode IPL again. If the
problem persists, there might be a memory problem.
v AJDG301
Contact your next level of support.
568 System reference codes (Bxxx)
B6000904 • B6001730
B6000904 B6000904 B6001215 B6001215
Explanation: The LinkLoader was not able to load a Explanation: Error in critical code sequence
critical LID
Failing Item:
Response: Perform the D mode IPL again. If the v LICIP08
problem persists, contact your next level of support.
v AJDG301
B6001001 B6001001
B6001219 B6001219
Explanation: Enqueuing a task to the TDQ which is
Explanation: A back leveled driver has been detected
already enqueued on TDQ
Failing Item:
Failing Item:
v LICIP08
v LICIP08
v AJDG301
v AJDG301
B6001604 B6001604
B6001103 B6001103
Explanation: Not able to create APPN task
Explanation: MISR not readable; must be readable for
Normal Mode install Response: An error occurred during task creation
which requires a power off of the system.
Response: MISR is not readable. Perform a manual
install to reinitialize the system. Failing Item:
v LICIP08
B6001104 B6001104 v AJDG301
Explanation: Failure reading media or not install
media B6001724 B6001724
Response: Determine that correct install media is Explanation: An attempt to create a segment failed
loaded. If correct install media is installed, media could
be corrupt. Obtain another copy of the install media Response: The create could fail for two reasons:
and re-attempt the install. If the install still fails, contact v A code problem. Perform the procedure indicated in
your service representative. the failing item list.
v No free auxiliary storage on the system. Add
B6001201 B6001201 additional DASD if the create failed because no
auxiliary storage was available.
Explanation: Critical database segment could not be
created Failing Item:
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6001730 B6001730
B6001204 B6001204 Explanation: An IPL is needed to restore system
performance
Explanation: Error in constraint enforcement
Response: Licensed Internal Code has detected a
Failing Item: condition that is impacting system performance. System
v LICIP08 operation can continue, but system performance may
be noticeably reduced until the next IPL.
v AJDG301
Look at the Product Activity Log entry, and find the
value at offset x'000180'. If the value equals x'00000122',
B6001210 B6001210
the error was caused by too much processor memory
Explanation: Object not found in the in-use table being installed.
Failing Item: For more information, contact IBM Service Support.
v LICIP08 Failing Item:
v AJDG301 v UPLF1
(B6xx) Reference codes 569
B6003000 • B6004421
B6003000 B6003000 B6004403 B6004403
Explanation: LPAR service function directed a Main Explanation: Storage Management failed to reach full
Storage Dump. paging.
Response: Copy the current main storage dump to Response: Copy the current main storage dump to
media. For more information on how to copy a Main media.
Storage Dump, refer to Copying a main storage dump.
For more information on how to perform a Main
Failing Item: Storage Dump, refer to Copying a main storage dump.
v AJDG301
B6004404 B6004404
B60041FC B60041FC Explanation: Auto copy failed or not attempted.
Explanation: Installation of LIC failed Response: Copy the current main storage dump. If
Response: Words 12 and 13 of this SRC contain copying to system ASP, existing copies may need to be
additional diagnostic information. deleted or renamed. Then exit the Main Storage Dump
Manager.
Install LIC using physical media.
For more information on how to perform a Main
To determine what caused the failure, collect SRC Storage Dump, refer to Copying a main storage dump.
information and contact your next level of support.
Failing Item: B6004405 B6004405
v SVCDOCS
Explanation: System ASP threshold exceeded after
auto copy done.
B60041FD B60041FD
Response: Delete other system ASP copies or exit the
Explanation: Installation of LIC failed Main Storage Dump Manager and then from DST copy
the Auto Copy to media and then delete the Auto Copy
Response: A main store dump was initiated. Words 12 in system ASP.
and 13 of this SRC contain additional diagnostic
information.
B6004420 B6004420
To recover the partition using the previously installed
LIC, perform a B-mode IPL. You can then re-try the Explanation: MSD Manager not configured to save
installation of LIC. Otherwise, install LIC using dump information
physical media.
Response: The platform produced dump data, but the
To determine what caused this failure, collect SRC Main Storage Dump (MSD) Manager was not
information and main store dump and contact your configured to automatically copy the dump to an
next level of support. Auxiliary Storage Pool (ASP). The dump will be lost if
the system power is lost. Use MSD Manager to
Failing Item: manually copy the current platform dump to media or
v SVCDOCS an ASP.
B6004401 B6004401 B6004421 B6004421
Explanation: Missing DASD units. Explanation: Insufficient space in the ASP to store a
platform dump
Response: Copy the current main storage dump to
media. Response: The platform produced dump data, and the
Main Storage Dump (MSD) Manager was configured to
For more information on how to perform a Main
automatically copy the dump to an Auxiliary Storage
Storage Dump, refer to Copying a main storage dump.
Pool (ASP), but there was not sufficient free space
available in the ASP. The dump will be lost if the
B6004402 B6004402 system power is lost. Manually copy the current
platform dump from the platform by performing one of
Explanation: Missing DASD units.
the following:
Response: Copy the current main storage dump to v Make room in the designated ASP and then use the
media. Then exit the Main Storage Dump Manager. MSD Manager to copy the current platform dump to
For more information on how to perform a Main ASP.
Storage Dump, refer to Copying a main storage dump.
570 System reference codes (Bxxx)
B6004422 • B6004715
v Use the MSD Manager to delete other dump copies,
B6004710 B6004710
then copy the current platform dump to ASP.
v Use the MSD Manager to copy the current platform Explanation: Processor On Demand error detected.
dump to a different ASP. Response: SPCN communication failure during
v Use the MSD Manager to copy the current platform Processor On Demand.
dump to media.
Look in the Product Activity Log for other SPCN errors
and perform the actions indicated for those errors.
B6004422 B6004422
Failing Item:
Explanation: A platform dump is saved in MSD v SPNLCRD
Manager
Response: The platform produced dump data. The B6004712 B6004712
dump data was copied to the Main Storage Dump
(MSD) Manager. Explanation: Processor On Demand error detected.
Failing Item: Response: Correct any Processor Capacity card or
SPCN failures.
v PLDUMP
Failing Item:
B6004601 B6004601 v CTLPNCD
Explanation: Unspecified LIC error.
B6004713 B6004713
Problem determination: Report this problem to your
next level of support. Explanation: Incorrect Processor Capacity Card
installed.
Failing Item:
Response: The Processor Capacity Card is the failing
v SVCDOCS
item since it has been swapped in from a different
system.
B6004700 B6004700
Put the Processor Capacity Card back in the system it
Explanation: Processor On Demand error detected. came from, and reinstall this system's original Processor
Capacity Card.
Response: Processor on Demand Data Block key is not
valid. Failing Item:
Replace the Processor Capacity card. v CTLPNCD
Failing Item:
B6004714 B6004714
v CTLPNCD
Explanation: The CUoD data is not present. A
problem may exist.
B6004701 B6004701
Response: The Processor Capacity Card was changed
Explanation: Processor On Demand error detected.
and there may be a problem.
Response: Processor On Demand Data Block contains
If the system did have any activated standby
data that does not match the expected data.
processors before the Processor Capacity Card was
Contact your service provider. replaced, then new processor on demand activation
codes must be obtained to restore the previous
Failing Item: activations.
v AJDG301
Contact your service provider.
B6004703 B6004703
B6004715 B6004715
Explanation: Processor On Demand error detected.
Explanation: Processor On Demand error detected.
Response: Processor On Demand Serialization has
failed during IPL. Response: Correct any Processor Capacity card or
SPCN failures.
Contact your service provider.
Failing Item:
Failing Item: v CTLPNCD
v AJDG301
(B6xx) Reference codes 571
B6004730 • B6005004
B6004730 B6004730 B6004747 B6004747
Explanation: Processor On Demand error detected. Explanation: 1 hour left in POD 14 day Trial
Activation Period.
Response: Processor On Demand standby processors
are in use. Response: If a new activation code was purchased, it
should be entered now. Otherwise, the system will
Contact your service provider.
revert back to its previous activation state at the end of
Failing Item: the Trial Activation Period.
v AJDG301
B6005001 B6005001
B6004731 B6004731 Explanation: DST received no response from a work
Explanation: Processor On Demand error detected. station controller
Response: The Processor On Demand Trial Activation Response: The workstation I/O processor for the
period is not valid. Contact your next level of support. system or partition console did not respond.
Failing Item: Failing Item:
v AJDG301 v RTRIP01
v FI00380
B6004733 B6004733 v AJDG301
Explanation: Processor On Demand error detected.
B6005002 B6005002
Response: Contact your service provider.
Explanation: DST problem attempting to use the
Failing Item: system console
v AJDG301 Response: A code problem occurred during an
attempt to use the system console.
B6004740 B6004740 Failing Item:
Explanation: Processor On Demand error detected. v LICIP03
Response: The Processor On Demand Activation code v AJDG301
just entered is not valid. v FI00380
Contact your next level of support.
B6005003 B6005003
Failing Item:
v AJDG301 Explanation: Service program failed
Response: The ASCII system console failed to
B6004741 B6004741 respond.
Explanation: Processor On Demand error detected. Failing Item:
v FI00320
Response: An invalid Processor On Demand
Activation code has been entered more than 5 v FI00602
consecutive times. Contact your service provider. v USER
Failing Item: v AJDG301
v AJDG301 v FI00380
B6004745 B6004745 B6005004 B6005004
Explanation: Processor Capacity card replaced on Explanation: DST console failed to respond
activated POD system. Response: The system console failed to respond.
Response: Contact IBM Support to order a Failing Item:
replacement Processor On Demand activation code.
v RTRIP02
v FI00320
v FI00602
v USER
572 System reference codes (Bxxx)
B6005005 • B6005008
v AJDG301 – The twinaxial-related SRC is represented by the
v FI00380 first 4 characters.
v yy where:
B6005005 B6005005 – 0A = No console tagged
v zz where:
Explanation: Service program failed
– 00 = Not defined by user (old default value)
Response: The workstation adapter system console
– 01 = Twinaxial
failed to respond.
– 02 = Operations Console (Direct) (obsolete)
Failing Item:
– 03 = Operations Console (LAN )
v WSAIP01
– 04 = Hardware Management Console (HMC) or
v FI00320 Thin Console
v FI00602
v USER If you are attempting to use Operations Console, the
local console on a network uses words 3, 4, and 5. Use
v AJDG301
words 3 through 5 to select the appropriate section in
v FI00380 the following list.
1. Word 3 is "1": No supported HW detected or HW
B6005007 B6005007 detected is not expected (for example, you replaced
the LAN IOA so the serial number is different) In
Explanation: Service program failed some cases the serial number of the expected
Response: The workstation adapter console failed to adapter may be shown in word 5.
respond. 2. Word 3 is "2": The LAN IOA failed to report.
Failing Item: 3. Word 3 is "3": Hardware error. Common error codes
in word 4:
v RTRIP07
v 53001A80 and 53002AC0: Network, cable or the
v FI00320
LAN adapter may not be operational. Word 5
v FI00602 may contain the card position or serial number of
v USER the adapter.
v AJDG301 v 00000000: This error code indicates the adapter
v FI00380 reported but has not been initialized yet. This is
not considered an error, at this time. The adapter
should be activated shortly. Word 5 may contain
B6005008 B6005008 the card position or serial number of the adapter.
Explanation: DST console failed to respond. If an IPL v CC10031A: Adapter was activated but did not
did not find a console and if the console type is set to reach LinkUp state. The card was given more
anything except a 1, the system will display code than a minute to link up to its partner (probably
A6005008. a switch) and it didn't do so. Likely conditions:
Response: If you just replaced the LAN adapter – The cable is unplugged on one end or the
associated with Operations Console (LAN), you need to other, or is defective.
wait at least 35 minutes for the system to find and use – The switch port is not operational.
the new LAN adapter. In this case, when the system is
Once this error code is received, the problem will
satisfied, it starts using the new adapter. The console
not resolve itself until something restarts the
should start, and the SRC is no longer shown.
device driver. Word 5 may contain the card
If you are attempting to use a twinaxial console the position or serial number of the adapter.
only data relevant in this SRC is word 6. Use the v For other error codes contact your service
information in the list below for the meaning of word 6 provider. Word 5 may contain the card position
to determine the twinaxial failure. The first 4 characters or serial number of the adapter.
of word 6 contains the last 4 characters of the original
4. Word 3 is "4": BOOTP status: Word 4 contains the
failure type. For example, if word 6 contained
number of attempts. If attempts are zero, then
50010001, the twinaxial-related SRC would be A6005001
BOOTP is ready, when called. If attempts have a
and the console type is set to use a twinaxial console.
value, then the PC did not respond. Word 5 may
Refer to that SRC. Word 6 in the form of xxxx yy zz
contain the card position or serial number of the
means the following:
adapter.
v xxxx where:
5. Word 3 is "5": The system's LAN connection is
active but the PC failed to connect. Are the PC and
(B6xx) Reference codes 573
B6005010 • B6005094
system on the same network and using the same
B6005082 B6005082
protocol? Can the PC ping the system? (ping
serverhostname). Word 4 contains the IP address. Explanation: DST lost contact with the console
Word 5 may contain the card position or serial
Response: A service program lost contact with the
number of the adapter.
system console.
Problem determination: Look at words 3-8 on the
Failing Item:
console. If words 3-5 are non-zero the failing item is
most likely an ASYNC card. If words 6-8 are non-zero v RTRIP03
the failing item is most likely a LAN card. v AJDG301
Word 7 meanings for the failure identified: v USER
v 1 Async card not detected.
v 2 No cables detected. Word 8 is the Card position. B6005083 B6005083
Word 9 is the card type. Explanation: IPL service function ended abnormally
v 3 Wrong cable detected. Word 8 is the card position.
Word 9 is the cable ID. Response: A service program lost contact with the
system console.
v 4 Port in use. Word 8 is the card position. Word 9 is
the card type. Failing Item:
v FA Not configured for direct cable v TWSIP01
v AJDG301
Note: It is expected that a D-mode IPL with a new load v USER
source direct access storage device (DASD) will show
the console type value of 00. Examples of when this
can occur might be that the copy of data from a failing B6005090 B6005090
DASD did not copy all data or you are installing a new
Explanation: System startup failed in unattended IPL
logical partition. Also, there are times when the DASD
mode
is late reporting and the console type value was not
retrieved in time. In these cases you can use the Response: Perform the following:
console service function to set a console type value or v If reference code A6xx5090 is displayed on the
attempt to contact the console again. control panel for more than 10 minutes, perform the
Failing Item: procedure indicated in the failing item list.
v OPCIP03 v For reference code B6xx5090, perform the procedure
indicated in the failing item list.
v FI00719
Failing Item:
B6005010 B6005010 v LICIP11
v FI00580
Explanation: IPL service function ended abnormally
v FI00500
Failing Item:
v FI00301
v LICIP04
v FI00021
v AJDG301
v FI00065
v AJDG301
B6005014 B6005014
Explanation: DST status. The Storage Management B6005092 B6005092
Dual Path Information Screen option to dump data to a
PAL has completed successfully. Explanation: System is in DASD migration mode
Response: Install Licensed Internal Code and Upgrade
B6005015 B6005015 Load Source was specified but the key is not in the
manual position. Change the key position to manual
Explanation: DST error. An error has occurred and perform a system IPL.
gathering data for the Storage Management Dual Path
Information Screen option to dump data to a PAL.
Contact your next level of support or hardware service B6005094 B6005094
provider. Explanation: IASP detected a failure during the vary
Failing Item: on operation
v NEXTLVL Failing Item:
574 System reference codes (Bxxx)
B60050FF • B6005127
v LICIP12
B6005123 B6005123
Explanation: LIC program exception occurred
B60050FF B60050FF
Response: System LIC detected an interface problem
Explanation: DST unrecoverable program error
with the IOP or an IOP programming problem for
Failing Item: which an IOP and main storage dump may have been
v LICIP03 initiated.
v AJDG301 Failing Item:
v FI00380 v LICIP01
v FI00130
B6005120 B6005120 v AJDG301
Explanation: System LIC detected a program v FI00131
exception
Response: System LIC detected a programming B6005124 B6005124
problem. If performance or other system degradation is Explanation: LIC program exception occurred
occurring, the system may be operating with reduced
resources. Response: System LIC detected a programming
problem for which a main storage dump may have
Check the Product activity log for related entries. If this been initiated. Collect the dump if available.
reference code is logged with an error class of
Informational, then no action is required. Collect the Product Activity Log entry for this and send
it to your next level of support. A problem log entry
Otherwise, perform the procedure indicated in the may be generated for this refcode.
failing item list.
Failing Item:
Failing Item:
v AJDG301
v LICIP01
v AJDG301
B6005126 B6005126
v FI00130
Explanation: Addressed device failed to respond to
selection
B6005121 B6005121
Failing Item:
Explanation: LIC program exception occurred
v DISKDRV
Response: System LIC detected a programming v STORIOA
problem for which a main storage dump may have
v DISKTRY
been initiated. Collect the dump if available.
v FI01106
A problem log entry may be generated for this refcode.
v FI01140
Failing Item: v FI01141
v LICIP01 v DEVTERM
v AJDG301 v BACKPLN
B6005122 B6005122 B6005127 B6005127
Explanation: LIC program exception occurred Explanation: IOP timed out a disk command
Response: System LIC detected an IOP programming Failing Item:
problem for which an IOP dump may have been
v DISKDRV
initiated.
v STORIOA
Failing Item:
v FI01106
v LICIP01
v DISKTRY
v FI00130
v FI01140
v AJDG301
v FI01141
v FI00131
v DEVTERM
v BACKPLN
(B6xx) Reference codes 575
B6005128 • B6005219
B6005128 B6005128 B6005194 B6005194
Explanation: I/O processor failure Explanation: Insufficient entitled memory for the I/O
configuration
Failing Item:
v FI01112 Response: Use the hardware management console to
increase the entitled memory capacity of the partition
v FI01107
and restart the partition.
Failing Item:
B600512D B600512D
v SVCDOCS
Explanation: An IOP dump was initiated
Response: Copy the IOP dump entry and any related B6005206 B6005206
entries from the Product Activity Log to suitable media,
and give to an IBM service representative. Explanation: System LIC detected a missing IOP LIC
code load
B600512E B600512E Response: System LIC detected a missing IOP LIC
code load during IPL of the IOP. This indicates that
Explanation: LIC program exception occurred either the IOP code load is not installed on the system
Response: The system was in a D IPL mode when the Load Source device or that system LIC was unable to
problem was detected. A main storage dump was not successfully read that load from the Load Source
taken. device.
Failing Item: Failing Item:
v LICIP01 v LICIP01
v AJDG301 v USER
v FI00130
B6005209 B6005209
B6005192 B6005192 Explanation: System LIC detected an IOP timeout
during IOP IPL
Explanation: Insufficient entitled memory for the I/O
configuration Response: Verify that all IOP cable connections are
secure, and check tape and other non-disk devices and
Response: Use the hardware management console to media to verify that they are in a ready state.
increase the entitled memory capacity of the partition
and restart the I/O adapter. To restart a storage I/O Failing Item:
adapter, use Hardware Service Manager to re-IPL the v LICIP01
virtual I/O processor that is associated with this I/O
v USER
adapter. To restart a communications I/O adapter, vary
the line off and vary it on using the vary configuration v FI00130
(VRYCFG) command. v AJDG301
Failing Item:
v SVCDOCS B6005219 B6005219
Explanation: LIC program exception occurred
B6005193 B6005193 Response: An IOP signaled to system LIC that it had
Explanation: Virtual adapter not supported in a entered a critical internal state. LIC automatically
shared memory partition attempted to restart the IOP.
Response: Use the hardware management console to This reference code is logged for information only. No
remove the virtual adapter from the partition. action is required.
Failing Item: Failing Item:
v SVCDOCS v FI00310
v FI00318
v FI00065
v FI00130
v AJDG301
576 System reference codes (Bxxx)
B6005275 • B6005341
v Non-configured disk unit which was previously a
B6005275 B6005275
load source on a partitioned system.
Explanation: The system issued a reset/reload to the v Load Source configuration data does not match
IOP. partition for which it is being used.
Response: System Licensed Internal Code detected v Load Source configuration data does not match
that an IOP Reset/Reload has occurred, and that the system serial number for which it is being used.
IOP successfully recovered. v Load Source configuration data is newer than
Users who were signed on to a Workstation device primary partition configuration data.
under the IOP will need to sign back on. Any Failing Item:
LAN/WAN communications lines under the IOP will
v LPRIP01
need to be restarted. Tape/Optical devices under the
IOP may need to be varied back on. v LPARSUP
To determine the cause of the IOP Reset/Reload, check
the Product Activity Log for additional entries logged B6005312 B6005312
with the same System Log ID, and perform any actions Explanation: LIC program exception occurred
indicated for those errors.
Response: LPAR configuration data informational
error.
B6005276 B6005276
The LPAR configuration data was found to be in error
Explanation: IOP Reset was issued or inconsistent on a secondary partition's Load Source.
Response: LIC has detected a problem with the The data was automatically updated to the current
Service Processor IOP and has reset it but has not system level.
initiated reload of the Service Processor.
If the Load Source is mirrored, some system operations B6005313 B6005313
may be able to continue normally. However, some Explanation: LIC program exception occurred
system service operations have been suspended and the
system should be scheduled for power down as soon Response: LPAR configuration data informational
as possible. error.
Failing Item: The LPAR configuration data was found to be
v RTRIP08 inconsistent on a primary partition and could only be
corrected with an older copy of the data.
v AJGLD01
v AJDG301 Failing Item:
v FI00021 v LPARCFG
B6005310 B6005310 B6005340 B6005340
Explanation: LIC program exception occurred Explanation: Secondary partition not running at
optimum.
Response: System LIC detected a logical partition
configuration data consistency error. Copy the Product Response: Check the Primary partition's Product
Activity Log data for this error and any related entries Activity Log for system processor entries from
and contact your next level of hardware service approximately the same time. Perform the actions
support. indicated for those entries.
Failing Item:
B6005341 B6005341
v LPARSUP
Explanation: Secondary partition not running at
optimum.
B6005311 B6005311
Response: Check the primary partition Product
Explanation: LIC program exception occurred Activity Log for system memory entries from
Response: LPAR configuration data does not match approximately the same time. Perform the actions
current system configuration. The system will not IPL indicated for those entries.
past DST until the problem is corrected.
Following is a list of problems which may have caused
this SRC to be reported:
(B6xx) Reference codes 577
B6005342 • B6006902
B6005342 B6005342 B6005390 B6005390
Explanation: Secondary partition not running at Explanation: LIC program exception occurred
optimum.
Response: Record the Product Activity Log (PAL) hex
Response: Check the Primary partition's Product data for this SRC or print the PAL entry.
Activity Log for system processor entries from
Contact your next level of support.
approximately the same time. Perform the actions
indicated for those entries. Failing Item:
v LPARSUP
B6005343 B6005343
Explanation: Secondary partition not running at B6005505 B6005505
optimum. Explanation: The copying of DASD log data to the
Response: Check the Primary partition's Product IOP log was successful
Activity Log for system memory errors from Response: IOP log data can be copied to a spool file
approximately the same time. Perform the actions for examination by the development lab.
indicated for those entries.
B6005555 B6005555
B6005344 B6005344
Explanation: SLIC I/O DASD subsystem error
Explanation: Secondary partition not running at recovery in progress.
optimum.
Response: The interactive performance specified in the B6005600 B6005600
configuration data for this partition could not be met.
Explanation: Unrecoverable read error
Contact your next level of support.
Response: VPD data could not be read.
Failing Item:
v LPARSUP Look for other errors implicating hardware. There is no
way to know what VPD read has failed, but the
resource is not usable and should generate an error.
B6005350 B6005350
If no such error occurred, call your next level of
Explanation: Secondary partition software release not support.
supported
Failing Item:
Response: The logical partition software version is v SVCDOCS
outside the supported release delta.
Check the Release Delta from the Primary partition B6006900 B6006900
"Display Partition Release Level" screen.
Explanation: System bus error
Check the LPAR documentation for the release level of
the Primary partition and determine what the Response: Contact your next level of support.
supported Release Delta is.
Failing Item:
v NEXTLVL
B6005380 B6005380
Explanation: LIC program exception occurred B6006901 B6006901
Response: Record the Product Activity Log (PAL) hex Explanation: Bus Expansion Adapter card failed
data for this SRC or print the PAL entry.
Response: Contact your next level of support.
Contact your next level of support.
Failing Item:
Failing Item:
v NEXTLVL
v LPARSUP
B6006902 B6006902
Explanation: Bus Expansion Adapter card failed
Response: Contact your next level of support.
Failing Item:
578 System reference codes (Bxxx)
B6006905 • B6006909
v NEXTLVL failing item list documented here. By following the
procedures in the symbolic FRUs listed here you will
isolate to the correct FRU list based on system model
B6006905 B6006905
and features installed.
Explanation: Optical bus failed
NOTE: A fiber optic cleaning kit may be required for
Response: Contact your next level of support. optical HSL connections.
Failing Item: Failing Item:
v NEXTLVL v SIIOADP
v OPT_CLN
B6006906 B6006906
Explanation: High Speed Link (HSL) I/O bridge B6006908 B6006908
failure Explanation: High Speed Link (HSL) I/O bridge
Response: LIC could not access part of the HSL I/O failure
bridge VPD. The bridge and HSL loop may be Response: LIC data in the I/O bus VPD could not be
prevented from becoming operational. accessed. The I/O Bus identified in the SRC may not
For this reference code the failing item list presented in have become operational.
the Service Action Log (SAL), or serviceable event If there is a B6xx 6906 reference code, close this
viewer you are working with, can be different from the problem in the serviceable event view you are working
failing item list documented here. That is due to the with and work the 6906 error.
differences in system models and features installed.
For this reference code the failing item list presented in
If the Service Action Log (SAL) or serviceable event the Service Action Log (SAL), or serviceable event view
view on the hardware management console is available you are working with, can be different from the failing
then use the failing item list presented there for item list documented here. That is due to the
servicing this reference code. differences in system models and features installed.
If a serviceable event view is not available then use the If the Service Action Log or serviceable event view on
failing item list documented here. By following the the hardware management console or service processor
procedures in the symbolic FRUs listed here you will is available then use the failing item list presented there
isolate to the correct FRU list based on system model for servicing this reference code.
and features installed.
If a serviceable event view is not available then use the
NOTE: A fiber optic cleaning kit may be required for failing item list documented here. By following the
optical HSL connections. procedures in the symbolic FRUs listed here you will
Failing Item: isolate to the correct FRU list based on system model
and features installed.
v SIIOADP
v OPT_CLN NOTE: A fiber optic cleaning kit may be required for
optical HSL connections.
B6006907 B6006907 Failing Item:
v SIIOADP
Explanation: High Speed Link (HSL) I/O bridge
failure v OPT_CLN
Response: LIC detected invalid data in the HSL I/O
bridge VPD. The bridge and HSL loop may not have B6006909 B6006909
become operational. Explanation: High Speed Link (HSL) I/O bridge
For this reference code the failing item list presented in failure
the Service Action Log (SAL), or serviceable event view Response: LIC detected invalid data in the I/O bus
you are working with, can be different from the failing VPD. The bus and resources associated with it may not
item list documented here. That is due to the be operational.
differences in system models and features installed.
For this reference code the failing item list presented in
If the Service Action Log (SAL) or serviceable event the Service Action Log (SAL), or serviceable event view
view on the hardware management console, is available you are working with, can be different from the failing
then use the failing item list presented there for item list documented here. That is due to the
servicing this reference code. differences in system models and features installed.
If a serviceable event view is not available then use the If the Service Action Log (SAL) or serviceable event
(B6xx) Reference codes 579
B600690A • B600690D
viewer on the hardware management console is
B600690C B600690C
available then use the failing item list presented there
for servicing this reference code. Explanation: Load Source bus failed to IPL. The IPL is
terminated.
If a serviceable event view is not available then use the
failing item list documented here. By following the The IPL of the PCI bus where the Load Source
procedures in the symbolic FRUs listed here you will IOP/IOA is has failed. The PCI bus cannot be used.
isolate to the correct FRU list based on system model
Response: Look for other problems in the path of the
and features installed.
Load Source.
If the serviceable event view only indicated a frame or
Problem determination: Contact your next level of
enclosure see the locations section for the frame or
support to determine what the problem is.
enclosure type. The location of the HSL I/O Bridge will
be given in the locations tables. To work around this problem move the Load Source
IOP/IOA to another PCI bus.
NOTE: A fiber optic cleaning kit may be required for
optical HSL connections. v If the Load Source is on a physical adapter and the
server has multiple LPARs, use the LPAR's definition
Failing Item: in the hardware management console to determine
v SIIOADP the location of the physical adapter where the Load
v OPT_CLN Source is. Look for other errors that indicate
problems with hardware in the path to the Load
Source.
B600690A B600690A
v If the Load Source is on a virtual adapter, then this
Explanation: Associated adapter not found in this could be a problem with the virtual adapter. Work
partition with the configuration of the Virtual I/O Server to
use a different path to the Load Source.
Failing Item:
v If the server does not have multiple LPARs then
v LICIP16 work with the customer to determine the location of
the Load Source adapter if you believe it is not in the
B600690B B600690B first bus in the server unit. Look for other errors that
indicate problems with hardware in the path to the
Explanation: Load Source IOP did not come up to Load Source.
operational status. The IPL is terminated.
Failing Item:
The IPL of the IOP where the Load Source is has failed.
v SVCDOCS
The IOP cannot be used.
Problem determination: Contact your next level of
B600690D B600690D
support to determine what the problem is.
Explanation: IPL to the point where the Load Source
To work around this problem move the Load Source to
adapter is configured has failed. The IPL is terminated.
another adapter.
v If the Load Source is on a physical adapter and the The IPL and configuration of the LIC managing the
server has multiple LPARs, use the LPAR's definition resources on the Load Source path failed. The Load
in the hardware management console to determine Source path cannot be used.
the location of the physical adapter where the Load Response: Look for other errors that indicate
Source is. Look for other errors that indicate problems with hardware in the path to the Load
problems with hardware in the path to the Load Source.
Source.
v If the Load Source is on a virtual adapter, then this Problem determination: Contact your next level of
could be a problem with the virtual adapter. Work support to determine what the problem is.
with the configuration of the Virtual I/O Server to To work around this problem move the Load Source to
use a different path to the Load Source. another adapter.
v If the server does not have multiple LPARs then
Either the LIC or the adapter is failing.
work with the customer to determine the location of
the Load Source adapter if you believe it is not in the v If the Load Source is on a physical adapter and the
first bus in the server unit. Look for other errors that server has multiple LPARs, use the LPAR's definition
indicate problems with hardware in the path to the in the hardware management console to determine
Load Source. the location of the physical adapter where the Load
Source is.
Failing Item:
v If the Load Source is on a virtual adapter, then this
v SVCDOCS could be a problem with the virtual adapter. Work
580 System reference codes (Bxxx)
B6006910 • B6006962
with the configuration of the Virtual I/O Server to Response: Slot unavailable due to 64 bit card in
use a different path to the Load Source. adjacent slot.
v If the server does not have multiple LPARs then One of the messages documented with the symbolic
work with the customer to determine the location of FRU will describe the problem. See SLOTERR symbolic
the Load Source adapter if you believe it is not in the FRU for a list of messages and corrective actions.
first bus in the server unit.
Failing Item:
Failing Item:
v SLOTERR
v SVCDOCS
B6006961 B6006961
B6006910 B6006910
Explanation: Multi-adapter bridge card slot error, do
Explanation: I/O processor failure not use card slot
Response: An I/O processor timed out, returned bad Response: LED control failure, do not use slot.
status, or is not following the system bus protocol.
The card location is not available for use. The Failing
Failing Item: Item with the card slot error is in the Failing Item list
v LICIP07 for this reference code.
v FI00310 See SLOTERR symbolic FRU for the list of messages
v FI00318 and a further description of the problem detected by
v FI00065 Licensed Internal Code.
v FI00130 For this reference code the failing item list presented in
v AJDG301 the Service Action Log (SAL), or serviceable event view
you are working with, can be different from the failing
item list documented here. That is due to the
B6006938 B6006938 differences in system models and features installed.
Explanation: Not valid system configuration detected If the Service Action Log or a serviceable event viewer
Response: This system model does not allow a on the hardware management console is available for
configuration of more than three (non-OptiConnect) this problem then use the failing item list presented
I/O Processors. there for servicing this reference code.
Power down the system and remove the extra If a serviceable event view is not available then use the
(non-OptiConnect) I/O Processor(s) so that there are failing item list documented here. By following the
three or less. Restart the system. procedures in the symbolic FRUs listed here you will
isolate to the correct FRU list based on system model
and features installed.
B6006944 B6006944
Failing Item:
Explanation: Missing or failed I/O processor cards v SLOTERR
Response: A system bus appears to be empty. If the v MASBUS
bus is not empty, two I/O processors in consecutive
slots may be missing or broken. If there are broken I/O
processors, then another more serious SRC has B6006962 B6006962
occurred. Otherwise find the bus number for this Explanation: Multi-adapter bridge card slot error, do
failure from the Product activity log and use the system not use card slot
configuration list to verify the configuration of the I/O
processors on that bus. Response: Power control failure, do not use slot.
Failing Item: If there is a Linux partition in the system, any IOPs
plugged into slots owned by a Linux partition will not
v FI00317
power on. This error will be logged. Correct the
v FI00316 situation by removing the IOP cards.
v AJDG301
The card location is not available for use. The Failing
Item with the card slot error is in the Failing Item list
B6006960 B6006960 for this reference code.
Explanation: Multi-adapter bridge card slot error, do See SLOTERR symbolic FRU for the list of messages
not use card slot and a further description of the problem detected by
Licensed Internal Code.
(B6xx) Reference codes 581
B6006963 • B6006966
For this reference code the failing item list presented in serviceable event viewer on the hardware management
the Service Action Log (SAL), or serviceable event view console or the service processor, then the correct FRU,
you are working with, can be different from the failing description and card position(s) will be listed. Use the
item list documented here. That is due to the FRUs and descriptions in the serviceable event view
differences in system models and features installed. you are working with to determine the problem.
If the Service Action Log, or serviceable event view on If you do not have access to the Service Action Log, or
the hardware management console is available then use serviceable event view on the hardware management
the failing item list presented there for servicing this console or service processor, then word 4 of the SRC
reference code. has more information. Examine the last 4 digits in word
4 to determine the problem by comparing them to the
If a serviceable event view is not available then use the
list below and using the FRU(s) listed here.
failing item list documented here. By following the
procedures in the symbolic FRUs listed here you will 1. xxxx2022 - IOP found in slots owned by a Linux
isolate to the correct FRU list based on system model partition. The Multi-adapter Bridge and PCI Bridge
and features installed. set that it controls are assigned to a Linux partition.
The IOP found in the SLOT indicated by the DSA in
Failing Item: word 7 will not be configured.
v SLOTERR 2. xxxx2014 - I/O adapters were found under the
v MASBUS Multi-adapter Bridge but there is no IOP to support
them. The adapters cannot be used.
B6006963 B6006963 3. xxxx2015 - An card type was found that cannot be
supported in the card position where it is located.
Explanation: Multi-adapter bridge card slot error, do
not use card slot See MABRCFG symbolic FRU for the list of messages, a
Response: Power control failure, do not use slot. further description of the problem detected by Licensed
Internal Code and the corrective action.
The card location is not available for use. The Failing
Item with the card slot error is in the Failing Item list Failing Item:
for this reference code. v MABRCFG
See SLOTERR symbolic FRU for the list of messages
and a further description of the problem detected by B6006965 B6006965
Licensed Internal Code.
Explanation: Multi-adapter bridge configuration
For this reference code the failing item list presented in change or error
the Service Action Log (SAL), or serviceable event
Response: Card type not supported in this slot.
viewer you are working with, can be different from the
failing item list documented here. That is due to the An I/O processor or I/O adapter card type is installed
differences in system models and features installed. in the location indicated in word 7 of the SRC. The
card type is not supported in that slot under the
If the Service Action Log or serviceable event viewer on
multi-adapter bridge. The card is unavailable.
the hardware management console is available then use
the failing item list presented there for servicing this See MABRCFG symbolic FRU for the list of messages, a
reference code. further description of the problem detected by Licensed
Internal Code and the corrective action.
If serviceable event view is not available then use the
failing item list documented here. By following the Failing Item:
procedures in the symbolic FRUs listed here you will v MABRCFG
isolate to the correct FRU list based on system model
and features installed.
B6006966 B6006966
Failing Item:
Explanation: Multi-adapter bridge configuration
v SLOTERR
change or error
v MASBUS
Response: I/O processor removed from multi-adapter
bridge card slot.
B6006964 B6006964
On the previous IPL an I/O processor was in the card
Explanation: Multi-adapter bridge configuration location specified in word 7 of the SRC. The I/O
change or error processor was not detected on this IPL.
Response: One of several errors or configuration See MABRCFG symbolic FRU for the list of messages, a
problems has occurred under a Multi-adapter bridge. If further description of the problem detected by Licensed
you are using the Service Action Log (SAL), or the Internal Code and the corrective action.
582 System reference codes (Bxxx)
B6006967 • B6006970
Failing Item:
B600696A B600696A
v MABRCFG
Explanation: Card slot test failed
B6006967 B6006967 Failing Item:
v LICIP14
Explanation: Multi-adapter bridge configuration
change or error v FI00131
v BACKPLN
Response: I/O adapter unavailable due to moved I/O
processor card.
B600696B B600696B
The I/O adapter specified in word 7 of the SRC is not
available. On the previous IPL there was an I/O Explanation: Card slot could not be validated
processor card the adapter was assigned to. The I/O
Response: This can be caused by "PCI error injection
processor was not detected on this IPL.
policy" being set to "YES" and an I/O Processor being
See MABRCFG symbolic FRU for the list of messages, a installed on the same Multi-adapter bridge domain as
further description of the problem detected by Licensed the I/O Adapter. Do one of the following:
Internal Code and the corrective action.
-- Using the hardware management console or a
Failing Item: customer PC with a Web browser access the Advanced
v MABRCFG System Management Interface (ASMI) and disable PCI
error injection policy.
B6006968 B6006968 OR
Explanation: Multi-adapter bridge configuration -- Vary off the I/O Adapter. Using Hardware Service
change or error manager in SST/DST, locate the I/O Adapter resource.
Using concurrent maintenance on the associated
Response: IOA removed from multi-adapter bridge packaging resource, remove the I/O Adapter and
slot. install it in a location that does not have I/O Processors
On the previous IPL an I/O adapter was in the card on the same Multi-adapter bridge domain.
slot specified in word 7 of the SRC. That I/O adapter OR
was not detected on this IPL.
-- Vary off the I/O Adapter. Use the concurrent
See MABRCFG symbolic FRU for the list of messages, a maintenance option in Hardware Service Manager in
further description of the problem detected by Licensed SST/DST to power off all I/O Processors located on the
Internal Code and the corrective action. same multi-adapter bridge domain as the I/O Adapter.
Failing Item: Use concurrent maintenance to power off and power
on the I/O Adapter. Then use concurrent maintenance
v MABRCFG to power on the I/O Processors located on the same
multi-adapter bridge domain as the I/O Adapter.
B6006969 B6006969
Explanation: Multi-adapter bridge configuration B6006970 B6006970
change or error Explanation: High Speed Link (HSL) resource failure
Response: I/O adapter replaced by I/O processor Response: A system PCI bus failure was detected.
card. Word 7 of the SRC contains the bus number.
On the previous IPL there was an I/O adapter in the This failure can occur when a tower in an HSL loop is
location specified in word 7 of the SRC. This IPL LIC powered off using concurrent maintenance. If this is the
detected that the IOA was replaced by an IOP in that case, close this problem.
location.
This error is most likely in the hardware that makes up
See MABRCFG symbolic FRU for the list of messages, a the PCI bus, the PCI bus side of the HSL I/O bridge or
further description of the problem detected by Licensed the multi-adapter bridge. In some cases it may be
Internal Code and the corrective action. caused by a failing IOP in the multi-adapter bridge's
Failing Item: domain. When an IOP is causing the problem, the
failing IOP cannot be identified.
v MABRCFG
NOTE: This SRC can occur for the PCI bus resource on
a PCI bus in an I/O expansion unit when the unit is
powered off for a concurrent maintenance action.
If the Service Action Log, or serviceable event view on
(B6xx) Reference codes 583
B6006971 • B6006976
the hardware management console or service processor, v MA_BRDG
is available then use the failing item list presented there
for servicing this reference code.
B6006973 B6006973
If a serviceable event view is not available then use the
Explanation: High Speed Link (HSL) resource failure
failing item list documented here.
Response: Multi-adapter Bridge has detected a
NOTE: A fiber optic cleaning kit may be required for
problem in the card installed in the location specified in
optical HSL connections.
word 7 of the SRC. Use the FRU list in the Service
Failing Item: Action Log (SAL), or serviceable event view you are
v SI_PHB working with. If you are working from this document's
FRU list use the Symbolic FRU BRDGSET to determine
v PRI_PCI
the failing items.
v MA_BRDG
Failing Item:
v MABIP03
v BRDGSET
v BRDGSET
v SIIOADP
v OPT_CLN
v MA_BRDG
B6006971 B6006971
B6006974 B6006974
Explanation: High Speed Link (HSL) resource failure
Explanation: Multi-adapter bridge configuration
Response: A failure occurred in a multi-adapter change or error
bridge or on the bus to the card location it controls.
Response: PCI I/O processor rejected the assignment
If a serviceable event view is available, use the failing of or the removal of an I/O adapter.
item list presented there for servicing this reference
code. Failing Item:
v MABRCFG
If a serviceable event view is not available, use the
failing item list documented here.
B6006975 B6006975
Failing Item:
v MABIP02 Explanation: The system issued a reset/reload to the
service processor.
v MA_BRDG
v MASBUS Response: Service processor error.
v PIOCARD Failing Item:
v AJDGP01
B6006972 B6006972
Explanation: High Speed Link (HSL) resource failure B6006976 B6006976
Response: Multi-adapter Bridge (MaB) failure Explanation: Service processor failure.
detected. Response: For this reference code the failing item list
For this reference code the failing item list presented in presented in the Service Action Log (SAL), or
the Service Action Log (SAL), or serviceable event serviceable event view you are working with, can be
viewer you are working with, can be different from the different from the failing item list documented here.
failing item list documented here. That is due to the That is due to the differences in system models and
differences in system models and features installed. features installed.
If the Service Action Log (SAL) or serviceable event If the Service Action Log (SAL) or a serviceable event
viewer on the hardware management console is viewer on the hardware management console is
available then use the failing item list presented there available then use the failing item list presented there
for servicing this reference code. for servicing this reference code.
If a serviceable event view is not available then use the If a serviceable event viewer is not available then use
failing item list documented here. By following the the failing item list documented here. By following the
procedures in the symbolic FRUs listed here you will procedures in the symbolic FRUs listed here you will
isolate to the correct FRU list based on system model isolate to the correct FRU list based on system model
and features installed. and features installed.
Failing Item: Failing Item:
v SVCPROC
584 System reference codes (Bxxx)
B6006980 • B6006984
B6006980 B6006980 B6006982 B6006982
Explanation: Network Interface Controller / IO Hub Explanation: High Speed Link (HSL) connection
failure. failure
Response: For Power5 and newer servers, service this Response: For Power5 and newer servers, service this
error using the B7006980 service information. error using the B7006982 service information.
Otherwise, continue with this information. Otherwise, continue with this information.
The FRU list displayed in the Service Action Log (SAL) If this SRC is not in the Service Action Log (SAL) or
or serviceable event view you are working with, may serviceable event view you are using, then it is
vary from the failing item list given in this document. informational or statistical only. It does not require a
Use the FRU list in the serviceable event view if it is service action.
available to you.
Otherwise, this is a connection failure on an HSL link.
NOTE: A fiber optic cleaning kit may be required for Perform the procedure indicated in the failing item list.
optical HSL connections.
Failing Item:
Failing Item: v RIOIP09
v SICNTRL v HSL_LNK
v OPT_CLN v SIIOADP
v SICNTRL
B6006981 B6006981 v REM_NIC
Explanation: High Speed Link (HSL) I/O bridge v OPT_CLN
failure
Response: For Power5 and newer servers, service this B6006983 B6006983
error using the B7006981 service information.
Explanation: An invalid High Speed Link (HSL)
Otherwise, continue with this information.
configuration was detected
Cycle power on the frame identified as the frame with
Response: For Power5 and newer servers, service this
failed HSL I/O Bridge prior to replacing FRUs.
error using the B7006983 service information.
The FRU list displayed in the Service Action Log (SAL), Otherwise, continue with this information.
or serviceable event view you are using, may vary from
An HSL loop has an invalid configuration. Word 4 of
the failing item list given in this document. Use the
the SRC contains the program return code (PRC) which
FRU list in the serviceable event view if it is available
identifies the problem with the loop's configuration.
to you.
Use the PRC and the FRU listed below to determine
If you find either a B6xx 6982 or B6xx 6984 SRC logged the problem.
at approximately the same time as this SRC then they
If you are using the Service Action Log (SAL) or
were caused by the same failure. If you find a 6982
serviceable event view you are working with, the FRU
SRC logged at approximately the same time then close
description may already indicate the configuration
this problem and service the 6982 SRC. The failing item
problem.
listed for this SRC is one of the failing items listed for
B6xx 6982. If the serviceable event view's entry for this Failing Item:
SRC has a location listed then record the location for v SIRGCFG
use in servicing the 6982 SRC.
NOTE: This SRC can occur for the HSL I/O Bridge B6006984 B6006984
resource in an I/O expansion unit when the unit is
powered off for a concurrent maintenance action. Explanation: High Speed Link (HSL) loop status
message
NOTE: A fiber optic cleaning kit may be required for
optical HSL connections. Response: For Power5 and newer servers, service this
error using the B7006984 service information.
Failing Item: Otherwise, continue with this information.
v SIIOADP
An HSL loop has switched to its alternate path. This is
v OPT_CLN an informational SRC only.
Word 7 of the SRC contains the loop number in the
leftmost 4 digits. The loop number is in hexadecimal
format. You must convert the hexadecimal loop number
(B6xx) Reference codes 585
B6006985 • B6006986
into decimal format to recognize the loop number in resources. Ignore B6xx 6982 and B6xx 6984
HSM. entries. If there are HSL failures on other
system(s) then continue with the steps that
This SRC can be caused by a tower on the HSL loop
follow, otherwise go to step 2.
powering off.
v Repair the problems on the other systems and
This SRC may also appear in the Service Action Log return to this step. After making repairs on the
(SAL), or serviceable event viewer you are using, with other system(s) check the Product Activity Log
a B6xx 6982 or B6xx 6981 logged at approximately the (PAL) of this system for a B6xx 6985 logged after
same time. In that case the other SRC is reporting a the repairs you made on the other system(s). If
failure and this SRC is reporting that the alternate HSL you find one then continue with the steps that
path is now being used. Service the other SRC if follow, otherwise go to step 2.
present.
v For the B6xx 6985 log you found, use FRU
SIRSTAT to determine if the loop is now
B6006985 B6006985 complete. If the loop is complete then this
problem has been resolved. Use RIOIP01 to verify
Explanation: High Speed Link (HSL) loop status that the loop is now working properly.
message Otherwise, go to step 2.
Response: For Power5 and newer servers, service this 2. Use the serviceable event's FRU list when it is
error using the B7006985 service information. available.
Otherwise, continue with this information. If this SRC appears in the Service Action Log (SAL),
If this SRC is not in the Service Action Log (SAL), or or the serviceable event view you are using, with
serviceable event view you are using, then it is the Symbolic FRU HSL_LNK or HSLxxxx listed as a
informational. Use FRU SIRSTAT to determine what FRU, then perform problem isolation procedure
this SRC means. Otherwise, continue with the RIOIP01. Otherwise exchange the FRUs listed in the
following steps: serviceable event view.
This error can appear as a serviceable event when a NOTE: A fiber optic cleaning kit may be required for
tower, or I/O unit or another system in the loop did optical HSL connections.
not complete powering on before LIC on this system
checked this loop for errors. Search the Product Failing Item:
Activity Log (PAL) for the last B6xx 6985 SRC logged v SIRSTAT
for this loop and use FRU SIRSTAT to determine if this
v HSL_LNK
error requires service. If the last entry indicates the
loop is functioning (determined by FRU SIRSTAT) then v SIIOADP
no service action is required, close this problem v SICNTRL
There may be multiple B6xx 6985 logs with xxxx 3205 v OPT_CLN
in word 4 errors for the same loop resource in the
serviceable event view. This is caused by retry and B6006986 B6006986
recovery attempts. If there is a B6xx 6985 with xxxx
3206 or xxxx 3208 in word 4 after the above B6xx 6985 Explanation: System bus error
entries in the PAL, then the recovery efforts were Response: For Power5 and newer servers, service this
successful. If this is the case, close all the B6xx 6985 error using the B7006986 service information.
entries for that loop resource in the serviceable event Otherwise, continue with this information.
view.
1. If you find a B6xx 6981 in the serviceable event During IPL, system LIC detected an HSL I/O bridge
view then close that problem and go to step 2. that was already initialized. The bridge should have
Otherwise perform the following: been in a flushed and uninitialized state after powering
on. There is a problem with SPCN components that
v Perform RIOIP06 to determine if any other prevented the tower from powering off after a previous
systems are connected to this loop and return power off was issued. The tower will not be configured
here. (HSL_LNK or HSLxxxx FRU in the Service for this IPL.
Action Log (SAL) entry, or serviceable event view
you are working with, indicates the loop This reference code is equivalent to 1xxx 90F0. When
number.) If there are other system(s) then referring to the "CBLALL" symbolic FRU in the Failing
continue with the steps that follow, otherwise go Item list, perform the "CBLALL" procedure using
to step 2. reference code "90F0".
v Check for HSL failures on the other system(s) Word 5 of the SRC identifies the frame. Determine the
before replacing parts. HSL failures are frame by breaking down word 5:
serviceable event entries with HSL I/O Bridge
and Network Interface Controller (NIC)
586 System reference codes (Bxxx)
B6006987 • B60069A8
Word 5 -> xxxx xxNN where: NN is the frame number
B6006991 B6006991
in hexadecimal format.
Explanation: Service processor failure.
Failing Item:
v TWRCARD Failing Item:
v CBLALL v AJDGP01
B6006987 B6006987 B6006992 B6006992
Explanation: High Speed Link (HSL) connection Explanation: Service processor failure.
failure Failing Item:
Response: For Power5 and newer servers, service this v AJDGP01
error using the B7006987 service information.
Otherwise, continue with this information.
B6006993 B6006993
Failures are occurring on the HSL link.
Explanation: Service processor failure.
There may be B6xx 6982 errors logged on the same
Response: A failure occurred with the service
loop and about the same time as this error. Close those
processor hardware or the service processor LIC.
errors and continue to correct the problem by working
this error. The FRU list displayed in the Service Action Log (SAL),
v If there is a cable FRU in the serviceable event entry: or serviceable event view you are working with, may
vary from the failing item list given in this document.
1. If the connection is copper and either end has a
Use the FRU list in the serviceable event view if it is
loose connection, re-seat the cable. To do this,
available to you.
disconnect the connection and wait a minimum
of 30 seconds. Then reconnect the cable and Failing Item:
complete the tightening process in at most 30 v SVCPROC
seconds. Repeat the process at the other end of
the cable. If the error persists, replace the FRUs in v AJDGP01
the Service Action Log (SAL), or serviceable event
view you are using. B6006994 B6006994
2. If the connection is optical, clean the connections
Explanation: Service processor failure.
at both ends of the cable. If the error persists,
replace the FRUs in the Service Action Log (SAL), Response: The FRU list displayed in the Service
serviceable event view you are using. Action Log (SAL) or serviceable event view you are
3. If the error persists, replace the FRUs at each end working with, may vary from the failing item list given
of the cable starting with the FROM FRU listed in in this document. Use the FRU list in the serviceable
the serviceable event view you are using. event view if it is available to you.
v If there was no cable in the Service Action Log Failing Item:
(SAL), or serviceable event view you are using, then v SVCPROC
replace the FRUs listed in the serviceable event view.
Failing Item: B600699C B600699C
v HSL_LNK
Explanation: Wrap plug is installed on Bus Expansion
v OPT_CLN Adapter card
Response: This reference code is for information only.
B6006990 B6006990 It indicates the presence of a wrap plug on the local
Explanation: Service processor failure. optical link card.
Response: The FRU list displayed in the Service
Action Log (SAL), or serviceable event view you are B60069A8 B60069A8
working with, may vary from the failing item list given Explanation: Informational bus reference code
in this document. Use the FRU list in the serviceable
event view if it is available to you. Response: This reference code is for information only
and might include the following:
Failing Item:
v Optical speed encode
v SVCPROC
v Broken optical links now operational
v Other information
(B6xx) Reference codes 587
B60069B8 • B60069C7
B60069B8 B60069B8 B60069C6 B60069C6
Explanation: Bus hardware configuration problem Explanation: HSL Opticonnect abnormal disconnect
from other sys. or partition.
Response: Contact your next level of support.
Response: The local system or partition disconnected
Failing Item:
from a remote system or partition due to an
v NEXTLVL unexpected event or failure. The problem is most likely
with the remote system or partition. Intervention at the
B60069C1 B60069C1 remote system is most likely required. Examine both
the local and remote HSL OptiConnected systems or
Explanation: A failure occurred communicating with partitions for problems on this HSL loop.
another LPAR or system participating in Opti-connect
with this LPAR or system. Starting with IBM i release Possible reasons include: A fatal error in software or
7.1 this event will be logged in the Product Activity hardware in the remote system or partition or a power
Log but it will not be in the Service Action Log or the failure in the remote system.
Problem Log. This event normally occurs when the If there was not a complete HSL loop before this error
other LPAR or system is powered off. If both LPARs or occurred then a failure or power down in an HSL
systems are running and have no Opti-connect errors component between the local system or partition and
then this event is indicating a possible problem with the remote system or partition could have caused this
Opti-connect. error. Check for a problem with: an HSL cable, HSL
Response: Contact your next level of support if you I/O bridge or a power problem in an expansion I/O
suspect an Opti-connect problem. Otherwise this is a tower or unit on this loop.
tracking event. Examine the Service Action Log (SAL), or serviceable
Failing Item: event view you are using on the local system or
partition for HSL failures on the same HSL loop at
v NEXTLVL approximately the same time this error occurred.
Examine the remote system or partition for problems. If
B60069C2 B60069C2 the remote system or partition is powered on and IPL'd
Explanation: HSL Opticonnect normal connect to then examine the Service Action Log (SAL), or
another sys. or partition. serviceable event view you are using, on the remote
system or partition for problems on the same HSL loop
Response: This reference code is informational only. at approximately the same time this error occurred.
HSL OptiConnect has established connection normally. Correct any problems you find with the remote and
The local system or partition is participating in HSL local systems or partitions that happened at
Opticonnect with other systems or partitions on the approximately the same time and involve HSL
same HSL loop. Opticonnect or HSL loop components or Network
Interface Controllers. When the remote system is IPL'd
B60069C3 B60069C3 it will automatically reconnect with this system or
partition.
Explanation: HSL Opticonnect normal disconnect from
other sys. or partition If there are no problems with the remote system or
partition and there are no problems with the local
Response: This reference code is informational only. system or partition then collect all the Product Activity
HSL Opticonnect disconnected normally from a remote Log information for this failure on both systems. Be
node. The local system or partition has stopped sure to record all words in the SRC. Contact your next
participating in HSL Opticonnect with the remote level of support.
system or partition on the same HSL loop. Possible Failing Item:
reasons include:
v REM_SYS
v A remote system or partition went off line due to a
normal power off or disable of HSL Opticonnect.
B60069C7 B60069C7
B60069C5 B60069C5 Explanation: HSL Opticonnect abnormal disconnect
from other sys. or partition.
Explanation: I/O processor failure
Response: The local system or partition disconnected
Response: Contact your next level of support. from a remote system or partition due to an
Failing Item: unexpected event or failure. LIC will attempt to recover
from the error. Intervention at the local or remote
v NEXTLVL system or partition may be required.
588 System reference codes (Bxxx)
B60069C8 • B60069C9
Possible causes are: time out, hang or hardware failure. the Network Interface Controller at approximately the
The problem may be with: the local system or partition same time this error occurred.
or the remote system or partition.
Correct any problems you find with the remote and
If there was not a complete HSL loop before this error
local systems or partitions that happened at
then a failure or power down in an HSL component
approximately the same time and involve HSL
between the local system or partition and the remote
Opticonnect or HSL loop components or Network
system or partition could have caused this error. Check
Interface Controllers.
for SRCs with FRUs like: HSL cables, HSL I/O bridge
or a power problem in an expansion I/O tower or unit
on this loop. If there are no problems with the remote system or
partition and there are no problems with the local
Examine the SAL or serviceable event view you are system or partition then collect all the Product Activity
working with on the local system or partition for Log information for this failure on all systems or
failures on the same loop, or with the Network partitions. Be sure to record all words in the SRCs.
Interface Controller at approximately the same time. Contact your next level of support.
Examine the remote system or partition for problems. Failing Item:
Correct any HSL or NIC problems you find with the v REM_SYS
remote and local systems or partitions.
v LOC_SYS
If there are no problems with the remote system or v AJDG301
partition and there are no problems with the local
system or partition then collect all the Product Activity
Log (PAL) information for this failure on both systems. B60069C9 B60069C9
Be sure to record all words in the SRC. Contact your
Explanation: HSL Opticonnect abnormal disconnect
next level of support.
from other sys. or partition.
Failing Item:
Response: The local system or partition disconnected
v REM_SYS from a remote system or partition due to an failure in a
v LOC_SYS LIC virtualized bus unit. LIC will attempt to recover
from the error. Possible causes are:
B60069C8 B60069C8 v LIC problem where the local bus unit is off line.
v LIC problem where the remote bus unit is off line.
Explanation: HSL Opticonnect abnormal disconnect
from other sys. or partition.
Examine the Service Action Log (SAL), or serviceable
Response: The local system or partition disconnected event view you are using, on the local system or
from a remote system or partition due to an partition for HSL Opticonnect failures that occurred at
unexpected event or failure. All of the HSL approximately the same time this error occurred.
OptiConnect connections on this loop will be in a failed
state. LIC will attempt to recover from the error. Examine the remote system or partition for problems.
Intervention at the local or remote system or partition Examine the Service Action Log (SAL), or the
may be required. Possible causes are: serviceable event view you are using, on the remote
v time out of a critical message system or partition for HSL Opticonnect problems that
occurred at approximately the same time this error
v LIC code / table problem
occurred.
v Network deadlock detected
Collect all the Product Activity Log information for this
The problem may be with: failure on all systems and partitions on this HSL loop.
v The local system or partition Be sure to record all words in the SRCs. Contact your
v The remote system or partition next level of support with the information you have
collected.
Examine the Service Action Log (SAL), or serviceable Failing Item:
event view you are using, on the local system or v AJDG301
partition for HSL failures on the same HSL loop, or
with the Network Interface Controller at approximately v REM_SYS
the same time this error occurred. v LOC_SYS
Examine the remote system or partition for problems.
Examine the Service Action Log (SAL), or serviceable
event view you are using, on the remote system or
partition for problems on the same HSL loop or with
(B6xx) Reference codes 589
B60069CF • B60069E8
B60069CF B60069CF B60069DB B60069DB
Explanation: HSL Opticonnect abnormal disconnect Explanation: LIC failure
from other sys. or partition.
Response: A Licensed Internal Code error occurred.
Response: LIC internal error. All systems participating The partition will continue to run with this Host
in HSL OptiConnect will be disconnected. The system Ethernet Adapter (HEA) disabled. Perform a partition
must be re-IPL'd to recover. Before re-IPL'ing the dump and then IPL the partition to recover the HEA.
system initiate a main store dump. Send the partition dump to your next level of support.
After getting the dump, examine the Service Action Failing Item:
Log (SAL), or serviceable event view you are using, on v SVCDOCS
the local system or partition for HSL Opticonnect
failures that occurred at approximately the same time
this error occurred. B60069DC B60069DC
Examine the remote systems or partitions for problems. Explanation: The HEA is not connected to the
Examine the Service Action Log (SAL), or serviceable Ethernet switch
event view you are using, on the remote systems or Response: The Host Ethernet Adapter (HEA) is not
partitions for HSL Opticonnect problems that occurred connected to the Ethernet switch. If the HEA
at approximately the same time this error occurred. connection is not needed, no service action is required.
Collect all the Product Activity Log information for this If the HEA connection is needed, verify that the cable is
failure on all systems and partitions on this HSL loop. connected and the switch is powered on. After
Be sure to record all words in the SRCs. Contact your repairing the problem, verify that the connection has
next level of support with the information you have been restored.
collected.
Failing Item: B60069DD B60069DD
v AJDG301
Explanation: The HEA connection to the Ethernet
switch has been restored
B60069D0 B60069D0
Response: System log entry only, no service action
Explanation: Bus Expansion Adapter card failed required.
Response: Contact your next level of support.
B60069DE B60069DE
Failing Item:
v NEXTLVL Explanation: HEA Media Interface Adapter Failure
Response: Firmware detected a failure in the HEA
B60069D8 B60069D8 Media Interface Adapter.
Explanation: Bus Expansion Adapter failed Failing Item:
v HEA
Response: Contact your next level of support.
v AJDG301
Failing Item:
v NEXTLVL
B60069E0 B60069E0
Explanation: Bus Expansion Adapter card failed
B60069D9 B60069D9
Response: Contact your next level of support.
Explanation: Host Ethernet Adapter (HEA) failure
Failing Item:
Response: Firmware detected a hardware failure in
the Host Ethernet Adapter (HEA). v NEXTLVL
Failing Item:
B60069E8 B60069E8
v HEA
Explanation: Bus Expansion Adapter failed
B60069DA B60069DA Response: Contact your next level of support.
Explanation: System log entry only, no service action Failing Item:
required v NEXTLVL
590 System reference codes (Bxxx)
B60069F0 • B6007703
B60069F0 B60069F0 B6007202 B6007202
Explanation: Bus Expansion Adapter failed Explanation: Utility power restored
Response: Contact your next level of support. Response: This reference code is for information only.
The Uninterruptible Power System (UPS) is reporting
Failing Item:
that utility power has been restored.
v NEXTLVL
B6007203 B6007203
B60069F8 B60069F8
Explanation: A battery low condition was detected
Explanation: Bus Expansion Adapter failed
Response: This reference code is for information only.
Response: Contact your next level of support. The Uninterruptible Power System (UPS) is reporting a
Failing Item: battery low condition.
v NEXTLVL
B6007204 B6007204
B6007001 B6007001 Explanation: Uninterruptible Power System reported a
bypass active
Explanation: ISDN call in rejected
Response: This reference code is for information only.
Failing Item: The Uninterruptible Power System (UPS) is reporting a
v UG3LB bypass is active.
B6007004 B6007004 B6007205 B6007205
Explanation: TCP/IP informational error Explanation: Battery low condition was reset
Response: This reference code is logged when the Response: This reference code is for information only.
TCP/IP Attribute Log Protocol Errors is set, and the The Uninterruptible Power System (UPS) is no longer
TCP/IP System LIC silently discards an in bound reporting a battery low condition.
datagram. Silently discard is defined to mean discard
the received datagram without reporting an error to the
originating host device. Examples of such datagrams B6007206 B6007206
are those with checksums or destination addresses Explanation: UPS reported bypass no longer active
which are not valid.
Response: This reference code is for information only.
This reference code is for information only. Normally The Uninterruptible Power System (UPS) is no longer
no action should be taken as a result of this reference reporting a bypass active condition.
code. It is generated in order to assist with remote
device or TCP/IP network problem determination.
B600720A B600720A
B6007055 B6007055 Explanation: Battery Power Unit replacement dates do
not match
Explanation: Statistics were logged, no service action
required Response: The replacement dates for one of the
Battery Power Units do not match. Run "Display
Response: This reference code is logged for Hardware Configuration" and verify that the dates
information only. match the labels on the batteries.
B6007102 B6007102 B6007703 B6007703
Explanation: APPN CP-CP session ended. Explanation: System LIC detected a program
exception
B6007201 B6007201 Response: Storage Management detected a DASD
Explanation: A utility failure occurred datacheck condition and the defective sector was
reallocated.
Response: This reference code is for information only.
The Uninterruptible Power System (UPS) is reporting a Perform a system IPL to restart the system.
utility failure.
(B6xx) Reference codes 591
B6007704 • B6009999
B6007704 B6007704 B6008003 B6008003
Explanation: General failure detected by HRI Explanation: External storage subsystem disk unit
component. connection was restored
Failing Item: Response: No action required.
v AJDG301
B6008004 B6008004
B6007777 B6007777 Explanation: An external storage subsystem disk unit
Explanation: Hardware configuration change detected connection failed
Response: A hardware resource is missing. The Response: Could not read configuration information
resource reported in to the system on a previous IPL, from the disk unit. Look for other errors in the Service
but has not reported in on the current IPL. This could Action Log, or serviceable event view you are working
occur for several different reasons. with, and fix them.
1. It could be a normal situation where the resource is
currently powered off. In this case, when the B6008005 B6008005
resource is powered back on, it will no longer be
Explanation: High performance connection failed
missing.
2. The hardware resource could also be missing if it Response: A high performance connection to an
has been removed from the system, for example, a external storage subsystem disk unit failed.
tape drive that was replaced with a different tape There are still two or more external storage subsystem
drive. The service representative should use the disk unit connections, but performance might be
Hardware service manager to remove the entry for degraded.
this resource.
3. The resource may not have reported in on this IPL Look for other errors in the Service Action Log, or
because it is failing. Perform problem analysis to serviceable event view you are working with, and fix
determine why the resource is failing. them.
B6008000 B6008000 B6008006 B6008006
Explanation: An external storage subsystem disk unit Explanation: High performance connection failed
connection failed Response: A high performance connection to an
Response: Look for other errors in the Service Action external storage subsystem disk unit failed.
Log (SAL), or serviceable event view you are working There is still one more external storage subsystem disk
with, and fix them. unit connection, but performance might be degraded.
Look for other errors in the Service Action Log, or
B6008001 B6008001 serviceable event view you are working with, and fix
Explanation: An external storage subsystem disk unit them.
connection failed
Response: Look for other errors in the Service Action B6008007 B6008007
Log, or serviceable event view you are working with, Explanation: High performance connection was
and fix them. restored
Response: A high performance connection to an
B6008002 B6008002 external storage subsystem disk unit was restored.
Explanation: Maximum number of redundant Performance is no longer degraded.
connections exceeded
No action required.
Response: An attempt to activate a connection from
another I/O adapter to an external storage subsystem
disk unit failed because the maximum number of B6009999 B6009999
connections are already active for this disk unit. No Explanation: Call home test SRC built into LIC for
action required. testing and verification. No service action is needed.
Problem determination: None, this SRC means that a
LIC call home test was triggered to determine if
problem reporting functions are set up correctly.
592 System reference codes (Bxxx)
B600999A • B600D4C4
Contact your hardware service provider.
B600999A B600999A
Failing Item:
Explanation: Notification test SRC built into LIC for
testing and verification. No service action is needed. v OPTLCBL
v DRVSWCH
Problem determination: None, this SRC means that a
LIC serviceable test was triggered to determine if
problem reporting functions are set up correctly. This B600CFFD B600CFFD
SRC will show up in the Problem Log but will not
automatically call home. Explanation: Optical drive failure
Failing Item:
B600B700 B600B700 v OPTLDRV
Explanation: A platform firmware error log was
signalled to LIC but could not be retrieved from B600CFFF B600CFFF
platform firmware. LIC created this event in the PAL
Explanation: Media determined to be bad in Optical
with SRC B600B700 to log the problem.
library
Problem determination: Contact your hardware
service provider. This is a platform firmware problem.
B600D4C1 B600D4C1
Failing Item:
Explanation: LIC detected a problem in error analysis
v NEXTLVL code.
Problem determination: Report this problem to your
B600CF00 B600CF00 service provider.
Explanation: Permanent error on removable media Failing Item:
device.
v SVCDOCS
Response: A type D IPL terminated because of a
removable media Load Source device failure. If the
B600D4C2 B600D4C2
removable media Load Source is an external device,
check the cables. If that does not correct the problem, Explanation: LIC detected a problem in error analysis
replace the device. If the removable media Load Source code.
is an internal device, replace the device. If the
Problem determination: Report this problem to your
removable media Load Source is a virtual device,
service provider.
ensure it is set up correctly.
Failing Item:
Failing Item:
v SVCDOCS
v SVCDOCS
B600D4C3 B600D4C3
B600CF01 B600CF01
Explanation: LIC detected a problem in error analysis
Explanation: Unsupported removable media device
code.
configuration.
Problem determination: Report this problem to your
Problem determination: A type D IPL terminated
service provider.
because of an unsupported removable media device
configuration. Retry the D-IPL with a different Failing Item:
removable media device. v SVCDOCS
Failing Item:
v SVCDOCS B600D4C4 B600D4C4
Explanation: LIC detected a problem in error analysis
B600CFFC B600CFFC code.
Explanation: Optical library device condition not Problem determination: Report this problem to your
expected service provider.
Response: The optical disk drive addressing within Failing Item:
the optical library is incorrect. This error is likely to be v SVCDOCS
the result of faulty cabling or switch setting following
service to an optical library.
(B6xx) Reference codes 593
B600D4C5 • B6xx0106
B600D4C5 B600D4C5 B6xx0000 B6xx0000
Explanation: LIC detected a problem in error analysis Explanation: Operating system status code
code.
Response: This reference code is for information only.
Problem determination: Report this problem to your It is shown in the Product activity log as a side effect of
service provider. a condition that was detected by LIC.
Failing Item: Normally, no action should be taken as a result of
v SVCDOCS information reference codes. However, to isolate the
root cause, use these suggestions:
1. Examine the date and time of the informational
B600F103 B600F103
reference code.
Explanation: Main storage dump must be copied for 2. Determine if any other reference codes have been
service logged at or before the same date and time.
Failing Item: 3. Begin the service approach based on these other
v LICIP01 logged errors.
B600F104 B600F104 B6xx0102 B6xx0102
Explanation: LPAR service function directed a Main Explanation: A machine check occurred during IPL
Storage Dump. Response: Words 2 to 9 of this SRC contain additional
Response: The Hypervisor terminated a partition with diagnostic information. Record SRC words 1 through 9
an unresponsive Operating System. A Main Store before attempting to IPL again and report the problem
Dump must be done for service. Call your next level of to your Software Service Provider.
support when the dump is complete.
Failing Item: B6xx0103 B6xx0103
v LICIP01 Explanation: Main storage dump must be copied for
service
B600F105 B600F105 Failing Item:
Explanation: Licensed Internal Code detected error v LICIP01
Failing Item:
B6xx0104 B6xx0104
v NEXTLVL
Explanation: Terminate Immediate reference code is
bad
B600FDC0 B600FDC0
Failing Item:
Explanation: LIC program reported informational
error v LICIP08
v AJDG301
Response: This reference code is logged for
information only. No action required.
B6xx0105 B6xx0105
B600FDC5 B600FDC5 Explanation: More than one request to terminate the
system was issued
Explanation: LIC program failed and data was
captured Failing Item:
Response: This reference code indicates first failure v LICIP08
data capture (FFDC) data was collected for a problem v AJDG301
reported by licensed internal code.
The user should dial IBM Software Support for B6xx0106 B6xx0106
assistance.
Explanation: Terminate Immediate data is not valid
Failing Item:
Failing Item:
v UG3AS
v LICIP08
v AJDG301
594 System reference codes (Bxxx)
B6xx0107 • B6xx0266
B6xx0107 B6xx0107 B6xx0232 B6xx0232
Explanation: Main storage dump must be copied for Explanation: Disk sanitize action did not complete
service successfully
Response: The server detected an unrecoverable Response: Provide the Product Activity Log entry to
machine check condition. your next level of support for analysis.
Collect all the words of the SRC and the main store
dump and send to your system manufacturer for B6xx0244 B6xx0244
analysis.
Explanation: Contact was lost with the device
indicated
B6xx0109 B6xx0109
Response: Do not power off the system.
Explanation: An unrecoverable memory error
Perform the procedure indicated in the failing item list.
occurred
Failing Item:
Response: Re-IPL the partition that terminated. Then,
look for and correct errors with SRCs of the form v LICIP13
B1xxxxxx in the Serviceable Event View that indicate v FI00580
the replacement of memory in the failing item list. If v FI00500
there are no B1xxxxxx SRCs in the Serviceable Event
View that indicate a memory problem, perform a slow v FI00302
boot by using Performing a slow boot in order to run v FI00301
diagnostics on the memory. Then, look for and correct v AJDG301
errors with SRCs of the form B1xxxxxx in the
Serviceable Event View.
B6xx0255 B6xx0255
Failing Item:
Explanation: Contact was lost with the device
v SVCDOCS
indicated
Response: Do not power off the system.
B6xx0202 B6xx0202
Perform the procedure indicated in the failing item list.
Explanation: Unrecoverable read error
Failing Item:
Response: Restore the Licensed Internal Code using
Utilities to install and restore IBM i Licensed Internal v LICIP13
Code. v FI00580
v FI00500
B6xx0210 B6xx0210 v FI00302
Explanation: The system ASP has run out of disk v FI00301
storage. v AJDG301
Response: The out of storage condition in the system
ASP can be caused by an allocation failure in some B6xx0266 B6xx0266
other system software. This could be a looping
Explanation: Contact was lost with the device
condition that continues to allocate storage. Contact
indicated
your service representative for assistance with the Main
Storage Dump. Response: Do not power off the system.
Perform the procedure indicated in the failing item list.
B6xx0231 B6xx0231
Failing Item:
Explanation: Disk sanitize action completed v LICIP13
successfully
v FI00580
Response: No service action required. This entry is v FI00500
logged for information only.
v FI00302
v FI00301
v AJDG301
(B6xx) Reference codes 595
B6xx0299 • B6xx0329
B6xx0299 B6xx0299 B6xx0323 B6xx0323
Explanation: Informational LIC state SRC. Explanation: LIC exception code detected a problem
Failing Item:
B6xx0302 B6xx0302 v LICIP08
Explanation: Recursion in exception handler v AJDG301
Failing Item:
v LICIP08 B6xx0324 B6xx0324
v AJDG301 Explanation: LIC exception code detected a problem
Failing Item:
B6xx0304 B6xx0304 v LICIP08
Explanation: Component specific exception handler v AJDG301
return code not valid
Failing Item: B6xx0325 B6xx0325
v LICIP08 Explanation: LIC exception code detected a problem
v AJDG301
Failing Item:
v LICIP08
B6xx0305 B6xx0305
v AJDG301
Explanation: Exception while storage management
lock is held
B6xx0326 B6xx0326
Failing Item:
Explanation: LIC exception code detected a problem
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6xx0307 B6xx0307
Explanation: LIC exception code detected a problem
B6xx0327 B6xx0327
Response: Component Specific Exception Handler
Explanation: LIC exception code detected a problem
recursion is detected in an IBM i Operating System
process. Failing Item:
Failing Item: v LICIP08
v LICIP08 v AJDG301
v AJDG301
B6xx0328 B6xx0328
B6xx0308 B6xx0308 Explanation: LIC exception code detected a problem
Explanation: LIC exception code detected a problem Failing Item:
Response: Component Specific Exception Handler v LICIP08
recursion is detected in an IBM i Operating System v AJDG301
process.
Failing Item: B6xx0329 B6xx0329
v LICIP08 Explanation: LIC exception code detected a problem
v AJDG301
Failing Item:
v LICIP08
B6xx0317 B6xx0317
v AJDG301
Explanation: Traceback for code not found
Failing Item:
v LICIP08
v AJDG301
596 System reference codes (Bxxx)
B6xx0333 • B6xx0411
B6xx0333 B6xx0333 B6xx0405 B6xx0405
Explanation: A branch to a bad address was Explanation: Unhandled exception in authority
attempted recovery
Failing Item: Failing Item:
v LICIP08 v LICIP08
v AJDG301 v AJDG301
B6xx0334 B6xx0334 B6xx0406 B6xx0406
Explanation: Exception Handler could not be removed Explanation: Unhandled exception in data base
recovery
Failing Item:
v LICIP08 Failing Item:
v AJDG301 v LICIP08
v AJDG301
B6xx0335 B6xx0335
B6xx0407 B6xx0407
Explanation: Code resumed to not valid address
following exception Explanation: Unhandled exception in data base
initialization
Failing Item:
v LICIP08 Failing Item:
v AJDG301 v LICIP08
v AJDG301
B6xx0336 B6xx0336
B6xx0408 B6xx0408
Explanation: LIC exception code detected a problem
Explanation: Unhandled exception in journal recovery
Failing Item:
v LICIP08 Failing Item:
v AJDG301 v LICIP08
v AJDG301
B6xx0401 B6xx0401
B6xx0409 B6xx0409
Explanation: A machine check occurred during IPL
Explanation: Unhandled exception in journal
Failing Item:
synchronization
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
B6xx0402 B6xx0402
Explanation: A machine check occurred during
B6xx0410 B6xx0410
authority initialization
Explanation: Unhandled exception in journal clean up
Failing Item:
v LICIP08 Failing Item:
v AJDG301 v LICIP08
v AJDG301
B6xx0403 B6xx0403
B6xx0411 B6xx0411
Explanation: Unhandled exception during IPL or
install Explanation: Unhandled exception in commit recovery
Failing Item: Failing Item:
v LICIP08 v LICIP08
v AJDG301 v AJDG301
(B6xx) Reference codes 597
B6xx0412 • B6xx0440
B6xx0412 B6xx0412 B6xx0420 B6xx0420
Explanation: Unhandled exception in commit Explanation: The information loaded from the install
initialization media is not valid
Failing Item: Failing Item:
v LICIP08 v LICIP08
v AJDG301 v AJDG301
B6xx0413 B6xx0413 B6xx0421 B6xx0421
Explanation: Rebuild of recovery object index failed Explanation: Bad return code creating a queue or
message
Failing Item:
v LICIP08 Failing Item:
v AJDG301 v LICIP08
v AJDG301
B6xx0414 B6xx0414
B6xx0422 B6xx0422
Explanation: Install of operating system failed on read
from media Explanation: The Load/Dump command failed
Failing Item: Failing Item:
v LICIP08 v LICIP08
v FI00300 v AJDG301
B6xx0415 B6xx0415 B6xx0423 B6xx0423
Explanation: Create user profile failed Explanation: LIC in IBMi has detected that the system
unit technology level or configuration is not supported
Failing Item:
by the version and release of IBMi attemping to install.
v LICIP08 The version and release of IBMi you are working with
v AJDG301 will not install and not IPL on this system unit.
Problem determination: Install on a system unit that
B6xx0417 B6xx0417 is supported by the version and release of IBMi that
you are working with.
Explanation: Initiating the initial process failed
Failing Item:
Failing Item:
v SVCDOCS
v LICIP08
v AJDG301
B6xx0439 B6xx0439
B6xx0418 B6xx0418 Explanation: Opening the IPCF connection failed
Explanation: The information loaded from the install Failing Item:
media is not valid v LICIP08
Failing Item: v AJDG301
v LICIP08
v AJDG301 B6xx0440 B6xx0440
Explanation: Termination code is not valid
B6xx0419 B6xx0419 Failing Item:
Explanation: The information loaded from the install v LICIP08
media is not valid v AJDG301
Failing Item:
v LICIP08
v AJDG301
598 System reference codes (Bxxx)
B6xx0441 • B6xx0801
The system error condition that began process
B6xx0441 B6xx0441
termination is most commonly a storage error or LIC
Explanation: Power off system command failed exception handling.
Failing Item: Response: Perform LICIP08 - save and send in the
v LICIP08 Main Store Dump, collect LIC and Product Activity
Logs.
v AJDG301
Failing Item:
B6xx0443 B6xx0443 v LICIP08
v AJDG301
Explanation: Programmed IPL command failure
Failing Item:
B6xx0607 B6xx0607
v LICIP08
Explanation: Maximum stack size exceeded in process
v AJDG301
or task
Failing Item:
B6xx0446 B6xx0446
v LICIP08
Explanation: Error during machine termination
v AJDG301
Failing Item:
v LICIP08 B6xx0620 B6xx0620
v AJDG301
Explanation: Event management index is not usable
Failing Item:
B6xx0447 B6xx0447
v LICIP08
Explanation: Failure to reach MI boundary
v AJDG301
Failing Item:
v LICIP08 B6xx0650 B6xx0650
v AJDG301
Explanation: Resource management segment could
not be created or extended
B6xx0449 B6xx0449
Response: A main store dump was initiated.
Explanation: Exception in MI boundary manager
Words 2 to 9 of this SRC contain additional diagnostic
Failing Item: information. Record SRC words 1 through 9.
v LICIP08 Perform a system IPL and collect the Product activity
v AJDG301 log and main store dump and provide them along with
the recorded SRC information to IBM Service Support.
B6xx0506 B6xx0506 The problem may also be that there is not enough
auxiliary storage.
Explanation: Attempt to destroy a task with critical
flag on Failing Item:
Failing Item: v AJDG301
v LICIP08
v AJDG301 B6xx0801 B6xx0801
Explanation: Invalid LID directory detected
B6xx0507 B6xx0507 Response: During system IPL, the LIDMgr detected
Explanation: A critical process terminated. This SRC an I/O failure or media failure while trying to read the
will be in the LPAR's panel. LID directory.
LIC detected an attempt to terminate a process with its Failing Item:
critical flag set to ON. Normally this process will be v LICIP08
SCPF. v FI00070
This is a secondary affect of the process termination v FI00300
request for a critical process that was caused by a v AJDG301
system error condition that began process termination.
(B6xx) Reference codes 599
B6xx0802 • B6xx1219
B6xx0802 B6xx0802 B6xx1103 B6xx1103
Explanation: LID directory unusable Explanation: MISR not readable; must be readable for
Normal Mode install
Response: During system IPL, the LIDMgr detected
that the LID directory and associated Load Source is Response: MISR is not readable. Perform a manual
not usable. install to reinitialize the system.
Reinstall the Licensed Internal Code by using Utilities
to install and restore IBM i Licensed Internal Code. B6xx1104 B6xx1104
For more information, contact IBM Service Support. Explanation: Failure reading media or not install
media
Failing Item:
v AJDG301 Response: Determine that correct install media is
loaded. If correct install media is installed, media could
be corrupt. Obtain another copy of the install media
B6xx0901 B6xx0901 and re-attempt the install. If the install still fails, contact
Explanation: The LinkLoader has found its bad flag your service representative.
ON
Response: This reference code is usually the result of B6xx1201 B6xx1201
a system termination while the LinkLoader is Explanation: Critical database segment could not be
performing its work. created
Reinstall the Licensed Internal Code by using Utilities Failing Item:
to install and restore IBM i Licensed Internal Code.
v LICIP08
v AJDG301
B6xx0902 B6xx0902
Explanation: Unable to perform programmed IPL B6xx1204 B6xx1204
Response: The LinkLoader was not successful in Explanation: Error in constraint enforcement
performing a programmed IPL.
Failing Item:
Perform a system IPL. If the problem persists, examine
v LICIP08
the main storage dump and determine the reason for
the failure of the programmed IPL. v AJDG301
B6xx0903 B6xx0903 B6xx1210 B6xx1210
Explanation: The LinkLoader was not able to allocate Explanation: Object not found in the in-use table
a segment Failing Item:
Response: Perform the D mode IPL again. If the v LICIP08
problem persists, there might be a memory problem. v AJDG301
Contact your next level of support.
B6xx1215 B6xx1215
B6xx0904 B6xx0904
Explanation: Error in critical code sequence
Explanation: The LinkLoader was not able to load a
critical LID Failing Item:
v LICIP08
Response: Perform the D mode IPL again. If the
problem persists, contact your next level of support. v AJDG301
B6xx1001 B6xx1001 B6xx1219 B6xx1219
Explanation: Enqueuing a task to the TDQ which is Explanation: A back leveled driver has been detected
already enqueued on TDQ Failing Item:
Failing Item: v LICIP08
v LICIP08 v AJDG301
v AJDG301
600 System reference codes (Bxxx)
B6xx1604 • B6xx4403
B6xx1604 B6xx1604 B6xx41FC B6xx41FC
Explanation: Not able to create APPN task Explanation: Installation of LIC failed
Response: An error occurred during task creation Response: Words 12 and 13 of this SRC contain
which requires a power off of the system. additional diagnostic information.
Failing Item: Install LIC using physical media.
v LICIP08 To determine what caused the failure, collect SRC
v AJDG301 information and contact your next level of support.
Failing Item:
B6xx1724 B6xx1724 v SVCDOCS
Explanation: An attempt to create a segment failed
Response: The create could fail for two reasons: B6xx41FD B6xx41FD
v A code problem. Perform the procedure indicated in Explanation: Installation of LIC failed
the failing item list.
Response: A main store dump was initiated. Words 12
v No free auxiliary storage on the system. Add and 13 of this SRC contain additional diagnostic
additional DASD if the create failed because no information.
auxiliary storage was available.
To recover the partition using the previously installed
Failing Item: LIC, perform a B-mode IPL. You can then re-try the
v LICIP08 installation of LIC. Otherwise, install LIC using
v AJDG301 physical media.
To determine what caused this failure, collect SRC
B6xx1730 B6xx1730 information and main store dump and contact your
next level of support.
Explanation: An IPL is needed to restore system
performance Failing Item:
v SVCDOCS
Response: Licensed Internal Code has detected a
condition that is impacting system performance. System
operation can continue, but system performance may B6xx4401 B6xx4401
be noticeably reduced until the next IPL.
Explanation: Missing DASD units.
Look at the Product Activity Log entry, and find the
Response: Copy the current main storage dump to
value at offset x'000180'. If the value equals x'00000122',
media.
the error was caused by too much processor memory
being installed. For more information on how to perform a Main
Storage Dump, refer to Copying a main storage dump.
For more information, contact IBM Service Support.
Failing Item:
B6xx4402 B6xx4402
v UPLF1
Explanation: Missing DASD units.
B6xx3000 B6xx3000 Response: Copy the current main storage dump to
media. Then exit the Main Storage Dump Manager.
Explanation: LPAR service function directed a Main
Storage Dump. For more information on how to perform a Main
Storage Dump, refer to Copying a main storage dump.
Response: Copy the current main storage dump to
media. For more information on how to copy a Main
Storage Dump, refer to Copying a main storage dump. B6xx4403 B6xx4403
Failing Item: Explanation: Storage Management failed to reach full
paging.
v AJDG301
Response: Copy the current main storage dump to
media.
For more information on how to perform a Main
Storage Dump, refer to Copying a main storage dump.
(B6xx) Reference codes 601
B6xx4404 • B6xx4710
B6xx4404 B6xx4404 B6xx4422 B6xx4422
Explanation: Auto copy failed or not attempted. Explanation: A platform dump is saved in MSD
Manager
Response: Copy the current main storage dump. If
copying to system ASP, existing copies may need to be Response: The platform produced dump data. The
deleted or renamed. Then exit the Main Storage Dump dump data was copied to the Main Storage Dump
Manager. (MSD) Manager.
For more information on how to perform a Main Failing Item:
Storage Dump, refer to Copying a main storage dump. v PLDUMP
B6xx4405 B6xx4405 B6xx4601 B6xx4601
Explanation: System ASP threshold exceeded after Explanation: Unspecified LIC error.
auto copy done.
Problem determination: Report this problem to your
Response: Delete other system ASP copies or exit the next level of support.
Main Storage Dump Manager and then from DST copy
the Auto Copy to media and then delete the Auto Copy Failing Item:
in system ASP. v SVCDOCS
B6xx4420 B6xx4420 B6xx4700 B6xx4700
Explanation: MSD Manager not configured to save Explanation: Processor On Demand error detected.
dump information
Response: Processor on Demand Data Block key is not
Response: The platform produced dump data, but the valid.
Main Storage Dump (MSD) Manager was not
configured to automatically copy the dump to an Replace the Processor Capacity card.
Auxiliary Storage Pool (ASP). The dump will be lost if Failing Item:
the system power is lost. Use MSD Manager to
v CTLPNCD
manually copy the current platform dump to media or
an ASP.
B6xx4701 B6xx4701
B6xx4421 B6xx4421 Explanation: Processor On Demand error detected.
Explanation: Insufficient space in the ASP to store a Response: Processor On Demand Data Block contains
platform dump data that does not match the expected data.
Response: The platform produced dump data, and the Contact your service provider.
Main Storage Dump (MSD) Manager was configured to
Failing Item:
automatically copy the dump to an Auxiliary Storage
Pool (ASP), but there was not sufficient free space v AJDG301
available in the ASP. The dump will be lost if the
system power is lost. Manually copy the current B6xx4703 B6xx4703
platform dump from the platform by performing one of
the following: Explanation: Processor On Demand error detected.
v Make room in the designated ASP and then use the Response: Processor On Demand Serialization has
MSD Manager to copy the current platform dump to failed during IPL.
ASP.
Contact your service provider.
v Use the MSD Manager to delete other dump copies,
then copy the current platform dump to ASP. Failing Item:
v Use the MSD Manager to copy the current platform v AJDG301
dump to a different ASP.
v Use the MSD Manager to copy the current platform B6xx4710 B6xx4710
dump to media.
Explanation: Processor On Demand error detected.
Response: SPCN communication failure during
Processor On Demand.
Look in the Product Activity Log for other SPCN errors
602 System reference codes (Bxxx)
B6xx4712 • B6xx4747
and perform the actions indicated for those errors. Failing Item:
Failing Item: v AJDG301
v SPNLCRD
B6xx4731 B6xx4731
B6xx4712 B6xx4712 Explanation: Processor On Demand error detected.
Explanation: Processor On Demand error detected. Response: The Processor On Demand Trial Activation
period is not valid. Contact your next level of support.
Response: Correct any Processor Capacity card or
SPCN failures. Failing Item:
Failing Item: v AJDG301
v CTLPNCD
B6xx4733 B6xx4733
B6xx4713 B6xx4713 Explanation: Processor On Demand error detected.
Explanation: Incorrect Processor Capacity Card Response: Contact your service provider.
installed.
Failing Item:
Response: The Processor Capacity Card is the failing v AJDG301
item since it has been swapped in from a different
system.
B6xx4740 B6xx4740
Put the Processor Capacity Card back in the system it
came from, and reinstall this system's original Processor Explanation: Processor On Demand error detected.
Capacity Card. Response: The Processor On Demand Activation code
Failing Item: just entered is not valid.
v CTLPNCD Contact your next level of support.
Failing Item:
B6xx4714 B6xx4714 v AJDG301
Explanation: The CUoD data is not present. A
problem may exist. B6xx4741 B6xx4741
Response: The Processor Capacity Card was changed Explanation: Processor On Demand error detected.
and there may be a problem.
Response: An invalid Processor On Demand
If the system did have any activated standby Activation code has been entered more than 5
processors before the Processor Capacity Card was consecutive times. Contact your service provider.
replaced, then new processor on demand activation
codes must be obtained to restore the previous Failing Item:
activations. v AJDG301
Contact your service provider.
B6xx4745 B6xx4745
B6xx4715 B6xx4715 Explanation: Processor Capacity card replaced on
Explanation: Processor On Demand error detected. activated POD system.
Response: Correct any Processor Capacity card or Response: Contact IBM Support to order a
SPCN failures. replacement Processor On Demand activation code.
Failing Item:
B6xx4747 B6xx4747
v CTLPNCD
Explanation: 1 hour left in POD 14 day Trial
Activation Period.
B6xx4730 B6xx4730
Response: If a new activation code was purchased, it
Explanation: Processor On Demand error detected. should be entered now. Otherwise, the system will
Response: Processor On Demand standby processors revert back to its previous activation state at the end of
are in use. the Trial Activation Period.
Contact your service provider.
(B6xx) Reference codes 603
B6xx5001 • B6xx5008
Failing Item:
B6xx5001 B6xx5001
v WSAIP01
Explanation: DST received no response from a work
v FI00320
station controller
v FI00602
Response: The workstation I/O processor for the
v USER
system or partition console did not respond.
v AJDG301
Failing Item:
v FI00380
v RTRIP01
v FI00380
B6xx5007 B6xx5007
v AJDG301
Explanation: Service program failed
B6xx5002 B6xx5002 Response: The workstation adapter console failed to
respond.
Explanation: DST problem attempting to use the
system console Failing Item:
v RTRIP07
Response: A code problem occurred during an
attempt to use the system console. v FI00320
v FI00602
Failing Item:
v USER
v LICIP03
v AJDG301
v AJDG301
v FI00380
v FI00380
B6xx5008 B6xx5008
B6xx5003 B6xx5003
Explanation: DST console failed to respond. If an IPL
Explanation: Service program failed
did not find a console and if the console type is set to
Response: The ASCII system console failed to anything except a 1, the system will display code
respond. A6005008.
Failing Item: Response: If you just replaced the LAN adapter
v FI00320 associated with Operations Console (LAN), you need to
wait at least 35 minutes for the system to find and use
v FI00602
the new LAN adapter. In this case, when the system is
v USER satisfied, it starts using the new adapter. The console
v AJDG301 should start, and the SRC is no longer shown.
v FI00380 If you are attempting to use a twinaxial console the
only data relevant in this SRC is word 6. Use the
B6xx5004 B6xx5004 information in the list below for the meaning of word 6
to determine the twinaxial failure. The first 4 characters
Explanation: DST console failed to respond of word 6 contains the last 4 characters of the original
failure type. For example, if word 6 contained
Response: The system console failed to respond.
50010001, the twinaxial-related SRC would be A6005001
Failing Item: and the console type is set to use a twinaxial console.
v RTRIP02 Refer to that SRC. Word 6 in the form of xxxx yy zz
means the following:
v FI00320
v xxxx where:
v FI00602
– The twinaxial-related SRC is represented by the
v USER
first 4 characters.
v AJDG301
v yy where:
v FI00380
– 0A = No console tagged
v zz where:
B6xx5005 B6xx5005
– 00 = Not defined by user (old default value)
Explanation: Service program failed – 01 = Twinaxial
Response: The workstation adapter system console – 02 = Operations Console (Direct) (obsolete)
failed to respond. – 03 = Operations Console (LAN )
604 System reference codes (Bxxx)
B6xx5010 • B6xx5082
– 04 = Hardware Management Console (HMC) or v 1 Async card not detected.
Thin Console v 2 No cables detected. Word 8 is the Card position.
Word 9 is the card type.
If you are attempting to use Operations Console, the
v 3 Wrong cable detected. Word 8 is the card position.
local console on a network uses words 3, 4, and 5. Use
Word 9 is the cable ID.
words 3 through 5 to select the appropriate section in
the following list. v 4 Port in use. Word 8 is the card position. Word 9 is
the card type.
1. Word 3 is "1": No supported HW detected or HW
detected is not expected (for example, you replaced v FA Not configured for direct cable
the LAN IOA so the serial number is different) In
some cases the serial number of the expected Note: It is expected that a D-mode IPL with a new load
adapter may be shown in word 5. source direct access storage device (DASD) will show
the console type value of 00. Examples of when this
2. Word 3 is "2": The LAN IOA failed to report.
can occur might be that the copy of data from a failing
3. Word 3 is "3": Hardware error. Common error codes DASD did not copy all data or you are installing a new
in word 4: logical partition. Also, there are times when the DASD
v 53001A80 and 53002AC0: Network, cable or the is late reporting and the console type value was not
LAN adapter may not be operational. Word 5 retrieved in time. In these cases you can use the
may contain the card position or serial number of console service function to set a console type value or
the adapter. attempt to contact the console again.
v 00000000: This error code indicates the adapter Failing Item:
reported but has not been initialized yet. This is
v OPCIP03
not considered an error, at this time. The adapter
should be activated shortly. Word 5 may contain v FI00719
the card position or serial number of the adapter.
v CC10031A: Adapter was activated but did not B6xx5010 B6xx5010
reach LinkUp state. The card was given more
than a minute to link up to its partner (probably Explanation: IPL service function ended abnormally
a switch) and it didn't do so. Likely conditions: Failing Item:
– The cable is unplugged on one end or the v LICIP04
other, or is defective.
v AJDG301
– The switch port is not operational.
Once this error code is received, the problem will B6xx5014 B6xx5014
not resolve itself until something restarts the
device driver. Word 5 may contain the card Explanation: DST status. The Storage Management
position or serial number of the adapter. Dual Path Information Screen option to dump data to a
PAL has completed successfully.
v For other error codes contact your service
provider. Word 5 may contain the card position
or serial number of the adapter. B6xx5015 B6xx5015
4. Word 3 is "4": BOOTP status: Word 4 contains the Explanation: DST error. An error has occurred
number of attempts. If attempts are zero, then gathering data for the Storage Management Dual Path
BOOTP is ready, when called. If attempts have a Information Screen option to dump data to a PAL.
value, then the PC did not respond. Word 5 may Contact your next level of support or hardware service
contain the card position or serial number of the provider.
adapter.
Failing Item:
5. Word 3 is "5": The system's LAN connection is
active but the PC failed to connect. Are the PC and v NEXTLVL
system on the same network and using the same
protocol? Can the PC ping the system? (ping B6xx5082 B6xx5082
serverhostname). Word 4 contains the IP address.
Word 5 may contain the card position or serial Explanation: DST lost contact with the console
number of the adapter.
Response: A service program lost contact with the
Problem determination: Look at words 3-8 on the system console.
console. If words 3-5 are non-zero the failing item is
Failing Item:
most likely an ASYNC card. If words 6-8 are non-zero
the failing item is most likely a LAN card. v RTRIP03
v AJDG301
Word 7 meanings for the failure identified:
v USER
(B6xx) Reference codes 605
B6xx5083 • B6xx5123
B6xx5083 B6xx5083 B6xx5120 B6xx5120
Explanation: IPL service function ended abnormally Explanation: System LIC detected a program
exception
Response: A service program lost contact with the
system console. Response: System LIC detected a programming
problem. If performance or other system degradation is
Failing Item:
occurring, the system may be operating with reduced
v TWSIP01 resources.
v AJDG301
Check the Product activity log for related entries. If this
v USER reference code is logged with an error class of
Informational, then no action is required.
B6xx5090 B6xx5090 Otherwise, perform the procedure indicated in the
Explanation: System startup failed in unattended IPL failing item list.
mode Failing Item:
Response: Perform the following: v LICIP01
v If reference code A6xx5090 is displayed on the v AJDG301
control panel for more than 10 minutes, perform the v FI00130
procedure indicated in the failing item list.
v For reference code B6xx5090, perform the procedure
B6xx5121 B6xx5121
indicated in the failing item list.
Explanation: LIC program exception occurred
Failing Item:
v LICIP11 Response: System LIC detected a programming
problem for which a main storage dump may have
v FI00580
been initiated. Collect the dump if available.
v FI00500
A problem log entry may be generated for this refcode.
v FI00301
v FI00021 Failing Item:
v FI00065 v LICIP01
v AJDG301 v AJDG301
B6xx5092 B6xx5092 B6xx5122 B6xx5122
Explanation: System is in DASD migration mode Explanation: LIC program exception occurred
Response: Install Licensed Internal Code and Upgrade Response: System LIC detected an IOP programming
Load Source was specified but the key is not in the problem for which an IOP dump may have been
manual position. Change the key position to manual initiated.
and perform a system IPL. Failing Item:
v LICIP01
B6xx5094 B6xx5094 v FI00130
Explanation: IASP detected a failure during the vary v AJDG301
on operation v FI00131
Failing Item:
v LICIP12 B6xx5123 B6xx5123
Explanation: LIC program exception occurred
B6xx50FF B6xx50FF
Response: System LIC detected an interface problem
Explanation: DST unrecoverable program error with the IOP or an IOP programming problem for
which an IOP and main storage dump may have been
Failing Item:
initiated.
v LICIP03
Failing Item:
v AJDG301
v LICIP01
v FI00380
v FI00130
v AJDG301
606 System reference codes (Bxxx)
B6xx5124 • B6xx5194
v FI00131
B6xx512D B6xx512D
Explanation: An IOP dump was initiated
B6xx5124 B6xx5124
Response: Copy the IOP dump entry and any related
Explanation: LIC program exception occurred
entries from the Product Activity Log to suitable media,
Response: System LIC detected a programming and give to an IBM service representative.
problem for which a main storage dump may have
been initiated. Collect the dump if available.
B6xx512E B6xx512E
Collect the Product Activity Log entry for this and send
Explanation: LIC program exception occurred
it to your next level of support. A problem log entry
may be generated for this refcode. Response: The system was in a D IPL mode when the
problem was detected. A main storage dump was not
Failing Item:
taken.
v AJDG301
Failing Item:
v LICIP01
B6xx5126 B6xx5126
v AJDG301
Explanation: Addressed device failed to respond to
v FI00130
selection
Failing Item:
B6xx5192 B6xx5192
v DISKDRV
Explanation: Insufficient entitled memory for the I/O
v STORIOA
configuration
v DISKTRY
Response: Use the hardware management console to
v FI01106
increase the entitled memory capacity of the partition
v FI01140 and restart the I/O adapter. To restart a storage I/O
v FI01141 adapter, use Hardware Service Manager to re-IPL the
v DEVTERM virtual I/O processor that is associated with this I/O
adapter. To restart a communications I/O adapter, vary
v BACKPLN the line off and vary it on using the vary configuration
(VRYCFG) command.
B6xx5127 B6xx5127 Failing Item:
Explanation: IOP timed out a disk command v SVCDOCS
Failing Item:
v DISKDRV B6xx5193 B6xx5193
v STORIOA Explanation: Virtual adapter not supported in a
v FI01106 shared memory partition
v DISKTRY Response: Use the hardware management console to
v FI01140 remove the virtual adapter from the partition.
v FI01141 Failing Item:
v DEVTERM v SVCDOCS
v BACKPLN
B6xx5194 B6xx5194
B6xx5128 B6xx5128 Explanation: Insufficient entitled memory for the I/O
Explanation: I/O processor failure configuration
Failing Item: Response: Use the hardware management console to
increase the entitled memory capacity of the partition
v FI01112
and restart the partition.
v FI01107
Failing Item:
v SVCDOCS
(B6xx) Reference codes 607
B6xx5206 • B6xx5311
IOP may need to be varied back on.
B6xx5206 B6xx5206
To determine the cause of the IOP Reset/Reload, check
Explanation: System LIC detected a missing IOP LIC
the Product Activity Log for additional entries logged
code load
with the same System Log ID, and perform any actions
Response: System LIC detected a missing IOP LIC indicated for those errors.
code load during IPL of the IOP. This indicates that
either the IOP code load is not installed on the system
B6xx5276 B6xx5276
Load Source device or that system LIC was unable to
successfully read that load from the Load Source Explanation: IOP Reset was issued
device.
Response: LIC has detected a problem with the
Failing Item: Service Processor IOP and has reset it but has not
v LICIP01 initiated reload of the Service Processor.
v USER If the Load Source is mirrored, some system operations
may be able to continue normally. However, some
system service operations have been suspended and the
B6xx5209 B6xx5209
system should be scheduled for power down as soon
Explanation: System LIC detected an IOP timeout as possible.
during IOP IPL
Failing Item:
Response: Verify that all IOP cable connections are v RTRIP08
secure, and check tape and other non-disk devices and
v AJGLD01
media to verify that they are in a ready state.
v AJDG301
Failing Item:
v FI00021
v LICIP01
v USER
B6xx5310 B6xx5310
v FI00130
Explanation: LIC program exception occurred
v AJDG301
Response: System LIC detected a logical partition
configuration data consistency error. Copy the Product
B6xx5219 B6xx5219
Activity Log data for this error and any related entries
Explanation: LIC program exception occurred and contact your next level of hardware service
support.
Response: An IOP signaled to system LIC that it had
entered a critical internal state. LIC automatically Failing Item:
attempted to restart the IOP. v LPARSUP
This reference code is logged for information only. No
action is required. B6xx5311 B6xx5311
Failing Item: Explanation: LIC program exception occurred
v FI00310
Response: LPAR configuration data does not match
v FI00318 current system configuration. The system will not IPL
v FI00065 past DST until the problem is corrected.
v FI00130 Following is a list of problems which may have caused
v AJDG301 this SRC to be reported:
v Non-configured disk unit which was previously a
B6xx5275 B6xx5275 load source on a partitioned system.
v Load Source configuration data does not match
Explanation: The system issued a reset/reload to the
partition for which it is being used.
IOP.
v Load Source configuration data does not match
Response: System Licensed Internal Code detected system serial number for which it is being used.
that an IOP Reset/Reload has occurred, and that the
v Load Source configuration data is newer than
IOP successfully recovered.
primary partition configuration data.
Users who were signed on to a Workstation device
Failing Item:
under the IOP will need to sign back on. Any
LAN/WAN communications lines under the IOP will v LPRIP01
need to be restarted. Tape/Optical devices under the v LPARSUP
608 System reference codes (Bxxx)
B6xx5312 • B6xx5505
approximately the same time. Perform the actions
B6xx5312 B6xx5312
indicated for those entries.
Explanation: LIC program exception occurred
Response: LPAR configuration data informational B6xx5344 B6xx5344
error.
Explanation: Secondary partition not running at
The LPAR configuration data was found to be in error optimum.
or inconsistent on a secondary partition's Load Source.
Response: The interactive performance specified in the
The data was automatically updated to the current
configuration data for this partition could not be met.
system level.
Contact your next level of support.
B6xx5313 B6xx5313 Failing Item:
Explanation: LIC program exception occurred v LPARSUP
Response: LPAR configuration data informational
error. B6xx5350 B6xx5350
The LPAR configuration data was found to be Explanation: Secondary partition software release not
inconsistent on a primary partition and could only be supported
corrected with an older copy of the data. Response: The logical partition software version is
Failing Item: outside the supported release delta.
v LPARCFG Check the Release Delta from the Primary partition
"Display Partition Release Level" screen.
B6xx5340 B6xx5340 Check the LPAR documentation for the release level of
the Primary partition and determine what the
Explanation: Secondary partition not running at
supported Release Delta is.
optimum.
Response: Check the Primary partition's Product
B6xx5380 B6xx5380
Activity Log for system processor entries from
approximately the same time. Perform the actions Explanation: LIC program exception occurred
indicated for those entries.
Response: Record the Product Activity Log (PAL) hex
data for this SRC or print the PAL entry.
B6xx5341 B6xx5341
Contact your next level of support.
Explanation: Secondary partition not running at
optimum. Failing Item:
v LPARSUP
Response: Check the primary partition Product
Activity Log for system memory entries from
approximately the same time. Perform the actions B6xx5390 B6xx5390
indicated for those entries.
Explanation: LIC program exception occurred
Response: Record the Product Activity Log (PAL) hex
B6xx5342 B6xx5342
data for this SRC or print the PAL entry.
Explanation: Secondary partition not running at
Contact your next level of support.
optimum.
Failing Item:
Response: Check the Primary partition's Product
Activity Log for system processor entries from v LPARSUP
approximately the same time. Perform the actions
indicated for those entries. B6xx5505 B6xx5505
Explanation: The copying of DASD log data to the
B6xx5343 B6xx5343 IOP log was successful
Explanation: Secondary partition not running at Response: IOP log data can be copied to a spool file
optimum. for examination by the development lab.
Response: Check the Primary partition's Product
Activity Log for system memory errors from
(B6xx) Reference codes 609
B6xx5555 • B6xx6908
For this reference code the failing item list presented in
B6xx5555 B6xx5555
the Service Action Log (SAL), or serviceable event
Explanation: SLIC I/O DASD subsystem error viewer you are working with, can be different from the
recovery in progress. failing item list documented here. That is due to the
differences in system models and features installed.
B6xx5600 B6xx5600 If the Service Action Log (SAL) or serviceable event
view on the hardware management console is available
Explanation: Unrecoverable read error
then use the failing item list presented there for
Response: VPD data could not be read. servicing this reference code.
Look for other errors implicating hardware. There is no If a serviceable event view is not available then use the
way to know what VPD read has failed, but the failing item list documented here. By following the
resource is not usable and should generate an error. procedures in the symbolic FRUs listed here you will
isolate to the correct FRU list based on system model
If no such error occurred, call your next level of and features installed.
support.
NOTE: A fiber optic cleaning kit may be required for
Failing Item: optical HSL connections.
v SVCDOCS
Failing Item:
v SIIOADP
B6xx6900 B6xx6900
v OPT_CLN
Explanation: System bus error
Response: Contact your next level of support. B6xx6907 B6xx6907
Failing Item: Explanation: High Speed Link (HSL) I/O bridge
v NEXTLVL failure
Response: LIC detected invalid data in the HSL I/O
B6xx6901 B6xx6901 bridge VPD. The bridge and HSL loop may not have
become operational.
Explanation: Bus Expansion Adapter card failed
For this reference code the failing item list presented in
Response: Contact your next level of support. the Service Action Log (SAL), or serviceable event view
Failing Item: you are working with, can be different from the failing
item list documented here. That is due to the
v NEXTLVL
differences in system models and features installed.
If the Service Action Log (SAL) or serviceable event
B6xx6902 B6xx6902
view on the hardware management console, is available
Explanation: Bus Expansion Adapter card failed then use the failing item list presented there for
servicing this reference code.
Response: Contact your next level of support.
If a serviceable event view is not available then use the
Failing Item: failing item list documented here. By following the
v NEXTLVL procedures in the symbolic FRUs listed here you will
isolate to the correct FRU list based on system model
and features installed.
B6xx6905 B6xx6905
NOTE: A fiber optic cleaning kit may be required for
Explanation: Optical bus failed
optical HSL connections.
Response: Contact your next level of support.
Failing Item:
Failing Item: v SIIOADP
v NEXTLVL v OPT_CLN
B6xx6906 B6xx6906 B6xx6908 B6xx6908
Explanation: High Speed Link (HSL) I/O bridge Explanation: High Speed Link (HSL) I/O bridge
failure failure
Response: LIC could not access part of the HSL I/O Response: LIC data in the I/O bus VPD could not be
bridge VPD. The bridge and HSL loop may be accessed. The I/O Bus identified in the SRC may not
prevented from becoming operational. have become operational.
610 System reference codes (Bxxx)
B6xx6909 • B6xx690C
If there is a B6xx 6906 reference code, close this
B6xx690A B6xx690A
problem in the serviceable event view you are working
with and work the 6906 error. Explanation: Associated adapter not found in this
partition
For this reference code the failing item list presented in
the Service Action Log (SAL), or serviceable event view Failing Item:
you are working with, can be different from the failing v LICIP16
item list documented here. That is due to the
differences in system models and features installed.
B6xx690B B6xx690B
If the Service Action Log or serviceable event view on
the hardware management console or service processor Explanation: Load Source IOP did not come up to
is available then use the failing item list presented there operational status. The IPL is terminated.
for servicing this reference code. The IPL of the IOP where the Load Source is has failed.
If a serviceable event view is not available then use the The IOP cannot be used.
failing item list documented here. By following the Problem determination: Contact your next level of
procedures in the symbolic FRUs listed here you will support to determine what the problem is.
isolate to the correct FRU list based on system model
and features installed. To work around this problem move the Load Source to
another adapter.
NOTE: A fiber optic cleaning kit may be required for
optical HSL connections. v If the Load Source is on a physical adapter and the
server has multiple LPARs, use the LPAR's definition
Failing Item: in the hardware management console to determine
v SIIOADP the location of the physical adapter where the Load
Source is. Look for other errors that indicate
v OPT_CLN
problems with hardware in the path to the Load
Source.
B6xx6909 B6xx6909 v If the Load Source is on a virtual adapter, then this
Explanation: High Speed Link (HSL) I/O bridge could be a problem with the virtual adapter. Work
failure with the configuration of the Virtual I/O Server to
use a different path to the Load Source.
Response: LIC detected invalid data in the I/O bus
v If the server does not have multiple LPARs then
VPD. The bus and resources associated with it may not
work with the customer to determine the location of
be operational.
the Load Source adapter if you believe it is not in the
For this reference code the failing item list presented in first bus in the server unit. Look for other errors that
the Service Action Log (SAL), or serviceable event view indicate problems with hardware in the path to the
you are working with, can be different from the failing Load Source.
item list documented here. That is due to the
Failing Item:
differences in system models and features installed.
v SVCDOCS
If the Service Action Log (SAL) or serviceable event
viewer on the hardware management console is
available then use the failing item list presented there B6xx690C B6xx690C
for servicing this reference code. Explanation: Load Source bus failed to IPL. The IPL is
If a serviceable event view is not available then use the terminated.
failing item list documented here. By following the The IPL of the PCI bus where the Load Source
procedures in the symbolic FRUs listed here you will IOP/IOA is has failed. The PCI bus cannot be used.
isolate to the correct FRU list based on system model
and features installed. Response: Look for other problems in the path of the
Load Source.
If the serviceable event view only indicated a frame or
enclosure see the locations section for the frame or Problem determination: Contact your next level of
enclosure type. The location of the HSL I/O Bridge will support to determine what the problem is.
be given in the locations tables. To work around this problem move the Load Source
NOTE: A fiber optic cleaning kit may be required for IOP/IOA to another PCI bus.
optical HSL connections. v If the Load Source is on a physical adapter and the
server has multiple LPARs, use the LPAR's definition
Failing Item:
in the hardware management console to determine
v SIIOADP the location of the physical adapter where the Load
v OPT_CLN
(B6xx) Reference codes 611
B6xx690D • B6xx6961
Source is. Look for other errors that indicate v FI00310
problems with hardware in the path to the Load v FI00318
Source.
v FI00065
v If the Load Source is on a virtual adapter, then this
v FI00130
could be a problem with the virtual adapter. Work
with the configuration of the Virtual I/O Server to v AJDG301
use a different path to the Load Source.
v If the server does not have multiple LPARs then B6xx6938 B6xx6938
work with the customer to determine the location of
the Load Source adapter if you believe it is not in the Explanation: Not valid system configuration detected
first bus in the server unit. Look for other errors that Response: This system model does not allow a
indicate problems with hardware in the path to the configuration of more than three (non-OptiConnect)
Load Source. I/O Processors.
Failing Item: Power down the system and remove the extra
v SVCDOCS (non-OptiConnect) I/O Processor(s) so that there are
three or less. Restart the system.
B6xx690D B6xx690D
B6xx6944 B6xx6944
Explanation: IPL to the point where the Load Source
adapter is configured has failed. The IPL is terminated. Explanation: Missing or failed I/O processor cards
The IPL and configuration of the LIC managing the Response: A system bus appears to be empty. If the
resources on the Load Source path failed. The Load bus is not empty, two I/O processors in consecutive
Source path cannot be used. slots may be missing or broken. If there are broken I/O
processors, then another more serious SRC has
Response: Look for other errors that indicate occurred. Otherwise find the bus number for this
problems with hardware in the path to the Load failure from the Product activity log and use the system
Source. configuration list to verify the configuration of the I/O
Problem determination: Contact your next level of processors on that bus.
support to determine what the problem is. Failing Item:
To work around this problem move the Load Source to v FI00317
another adapter. v FI00316
Either the LIC or the adapter is failing. v AJDG301
v If the Load Source is on a physical adapter and the
server has multiple LPARs, use the LPAR's definition B6xx6960 B6xx6960
in the hardware management console to determine
the location of the physical adapter where the Load Explanation: Multi-adapter bridge card slot error, do
Source is. not use card slot
v If the Load Source is on a virtual adapter, then this Response: Slot unavailable due to 64 bit card in
could be a problem with the virtual adapter. Work adjacent slot.
with the configuration of the Virtual I/O Server to
use a different path to the Load Source. One of the messages documented with the symbolic
FRU will describe the problem. See SLOTERR symbolic
v If the server does not have multiple LPARs then
FRU for a list of messages and corrective actions.
work with the customer to determine the location of
the Load Source adapter if you believe it is not in the Failing Item:
first bus in the server unit. v SLOTERR
Failing Item:
v SVCDOCS B6xx6961 B6xx6961
Explanation: Multi-adapter bridge card slot error, do
B6xx6910 B6xx6910 not use card slot
Explanation: I/O processor failure Response: LED control failure, do not use slot.
Response: An I/O processor timed out, returned bad The card location is not available for use. The Failing
status, or is not following the system bus protocol. Item with the card slot error is in the Failing Item list
for this reference code.
Failing Item:
v LICIP07 See SLOTERR symbolic FRU for the list of messages
612 System reference codes (Bxxx)
B6xx6962 • B6xx6964
and a further description of the problem detected by
B6xx6963 B6xx6963
Licensed Internal Code.
Explanation: Multi-adapter bridge card slot error, do
For this reference code the failing item list presented in
not use card slot
the Service Action Log (SAL), or serviceable event view
you are working with, can be different from the failing Response: Power control failure, do not use slot.
item list documented here. That is due to the
The card location is not available for use. The Failing
differences in system models and features installed.
Item with the card slot error is in the Failing Item list
If the Service Action Log or a serviceable event viewer for this reference code.
on the hardware management console is available for
See SLOTERR symbolic FRU for the list of messages
this problem then use the failing item list presented
and a further description of the problem detected by
there for servicing this reference code.
Licensed Internal Code.
If a serviceable event view is not available then use the
For this reference code the failing item list presented in
failing item list documented here. By following the
the Service Action Log (SAL), or serviceable event
procedures in the symbolic FRUs listed here you will
viewer you are working with, can be different from the
isolate to the correct FRU list based on system model
failing item list documented here. That is due to the
and features installed.
differences in system models and features installed.
Failing Item:
If the Service Action Log or serviceable event viewer on
v SLOTERR the hardware management console is available then use
v MASBUS the failing item list presented there for servicing this
reference code.
B6xx6962 B6xx6962 If serviceable event view is not available then use the
failing item list documented here. By following the
Explanation: Multi-adapter bridge card slot error, do
procedures in the symbolic FRUs listed here you will
not use card slot
isolate to the correct FRU list based on system model
Response: Power control failure, do not use slot. and features installed.
If there is a Linux partition in the system, any IOPs Failing Item:
plugged into slots owned by a Linux partition will not v SLOTERR
power on. This error will be logged. Correct the
v MASBUS
situation by removing the IOP cards.
The card location is not available for use. The Failing
B6xx6964 B6xx6964
Item with the card slot error is in the Failing Item list
for this reference code. Explanation: Multi-adapter bridge configuration
change or error
See SLOTERR symbolic FRU for the list of messages
and a further description of the problem detected by Response: One of several errors or configuration
Licensed Internal Code. problems has occurred under a Multi-adapter bridge. If
you are using the Service Action Log (SAL), or the
For this reference code the failing item list presented in
serviceable event viewer on the hardware management
the Service Action Log (SAL), or serviceable event view
console or the service processor, then the correct FRU,
you are working with, can be different from the failing
description and card position(s) will be listed. Use the
item list documented here. That is due to the
FRUs and descriptions in the serviceable event view
differences in system models and features installed.
you are working with to determine the problem.
If the Service Action Log, or serviceable event view on
If you do not have access to the Service Action Log, or
the hardware management console is available then use
serviceable event view on the hardware management
the failing item list presented there for servicing this
console or service processor, then word 4 of the SRC
reference code.
has more information. Examine the last 4 digits in word
If a serviceable event view is not available then use the 4 to determine the problem by comparing them to the
failing item list documented here. By following the list below and using the FRU(s) listed here.
procedures in the symbolic FRUs listed here you will 1. xxxx2022 - IOP found in slots owned by a Linux
isolate to the correct FRU list based on system model partition. The Multi-adapter Bridge and PCI Bridge
and features installed. set that it controls are assigned to a Linux partition.
Failing Item: The IOP found in the SLOT indicated by the DSA in
word 7 will not be configured.
v SLOTERR
2. xxxx2014 - I/O adapters were found under the
v MASBUS Multi-adapter Bridge but there is no IOP to support
them. The adapters cannot be used.
(B6xx) Reference codes 613
B6xx6965 • B6xx696B
3. xxxx2015 - An card type was found that cannot be v MABRCFG
supported in the card position where it is located.
B6xx6968 B6xx6968
See MABRCFG symbolic FRU for the list of messages, a
further description of the problem detected by Licensed Explanation: Multi-adapter bridge configuration
Internal Code and the corrective action. change or error
Failing Item: Response: IOA removed from multi-adapter bridge
v MABRCFG slot.
On the previous IPL an I/O adapter was in the card
B6xx6965 B6xx6965 slot specified in word 7 of the SRC. That I/O adapter
was not detected on this IPL.
Explanation: Multi-adapter bridge configuration
change or error See MABRCFG symbolic FRU for the list of messages, a
further description of the problem detected by Licensed
Response: Card type not supported in this slot. Internal Code and the corrective action.
An I/O processor or I/O adapter card type is installed Failing Item:
in the location indicated in word 7 of the SRC. The
v MABRCFG
card type is not supported in that slot under the
multi-adapter bridge. The card is unavailable.
B6xx6969 B6xx6969
See MABRCFG symbolic FRU for the list of messages, a
further description of the problem detected by Licensed Explanation: Multi-adapter bridge configuration
Internal Code and the corrective action. change or error
Failing Item: Response: I/O adapter replaced by I/O processor
v MABRCFG card.
On the previous IPL there was an I/O adapter in the
B6xx6966 B6xx6966 location specified in word 7 of the SRC. This IPL LIC
detected that the IOA was replaced by an IOP in that
Explanation: Multi-adapter bridge configuration location.
change or error
See MABRCFG symbolic FRU for the list of messages, a
Response: I/O processor removed from multi-adapter further description of the problem detected by Licensed
bridge card slot. Internal Code and the corrective action.
On the previous IPL an I/O processor was in the card Failing Item:
location specified in word 7 of the SRC. The I/O
v MABRCFG
processor was not detected on this IPL.
See MABRCFG symbolic FRU for the list of messages, a
B6xx696A B6xx696A
further description of the problem detected by Licensed
Internal Code and the corrective action. Explanation: Card slot test failed
Failing Item: Failing Item:
v MABRCFG v LICIP14
v FI00131
B6xx6967 B6xx6967 v BACKPLN
Explanation: Multi-adapter bridge configuration
change or error B6xx696B B6xx696B
Response: I/O adapter unavailable due to moved I/O Explanation: Card slot could not be validated
processor card.
Response: This can be caused by "PCI error injection
The I/O adapter specified in word 7 of the SRC is not policy" being set to "YES" and an I/O Processor being
available. On the previous IPL there was an I/O installed on the same Multi-adapter bridge domain as
processor card the adapter was assigned to. The I/O the I/O Adapter. Do one of the following:
processor was not detected on this IPL.
-- Using the hardware management console or a
See MABRCFG symbolic FRU for the list of messages, a customer PC with a Web browser access the Advanced
further description of the problem detected by Licensed System Management Interface (ASMI) and disable PCI
Internal Code and the corrective action. error injection policy.
Failing Item: OR
614 System reference codes (Bxxx)
B6xx6970 • B6xx6973
-- Vary off the I/O Adapter. Using Hardware Service
B6xx6971 B6xx6971
manager in SST/DST, locate the I/O Adapter resource.
Using concurrent maintenance on the associated Explanation: High Speed Link (HSL) resource failure
packaging resource, remove the I/O Adapter and
Response: A failure occurred in a multi-adapter
install it in a location that does not have I/O Processors
bridge or on the bus to the card location it controls.
on the same Multi-adapter bridge domain.
If a serviceable event view is available, use the failing
OR
item list presented there for servicing this reference
-- Vary off the I/O Adapter. Use the concurrent code.
maintenance option in Hardware Service Manager in
If a serviceable event view is not available, use the
SST/DST to power off all I/O Processors located on the
failing item list documented here.
same multi-adapter bridge domain as the I/O Adapter.
Use concurrent maintenance to power off and power Failing Item:
on the I/O Adapter. Then use concurrent maintenance v MABIP02
to power on the I/O Processors located on the same
multi-adapter bridge domain as the I/O Adapter. v MA_BRDG
v MASBUS
B6xx6970 B6xx6970 v PIOCARD
Explanation: High Speed Link (HSL) resource failure
B6xx6972 B6xx6972
Response: A system PCI bus failure was detected.
Word 7 of the SRC contains the bus number. Explanation: High Speed Link (HSL) resource failure
This failure can occur when a tower in an HSL loop is Response: Multi-adapter Bridge (MaB) failure
powered off using concurrent maintenance. If this is the detected.
case, close this problem. For this reference code the failing item list presented in
This error is most likely in the hardware that makes up the Service Action Log (SAL), or serviceable event
the PCI bus, the PCI bus side of the HSL I/O bridge or viewer you are working with, can be different from the
the multi-adapter bridge. In some cases it may be failing item list documented here. That is due to the
caused by a failing IOP in the multi-adapter bridge's differences in system models and features installed.
domain. When an IOP is causing the problem, the If the Service Action Log (SAL) or serviceable event
failing IOP cannot be identified. viewer on the hardware management console is
NOTE: This SRC can occur for the PCI bus resource on available then use the failing item list presented there
a PCI bus in an I/O expansion unit when the unit is for servicing this reference code.
powered off for a concurrent maintenance action. If a serviceable event view is not available then use the
If the Service Action Log, or serviceable event view on failing item list documented here. By following the
the hardware management console or service processor, procedures in the symbolic FRUs listed here you will
is available then use the failing item list presented there isolate to the correct FRU list based on system model
for servicing this reference code. and features installed.
If a serviceable event view is not available then use the Failing Item:
failing item list documented here. v MA_BRDG
NOTE: A fiber optic cleaning kit may be required for
optical HSL connections. B6xx6973 B6xx6973
Failing Item: Explanation: High Speed Link (HSL) resource failure
v SI_PHB Response: Multi-adapter Bridge has detected a
v PRI_PCI problem in the card installed in the location specified in
v MA_BRDG word 7 of the SRC. Use the FRU list in the Service
Action Log (SAL), or serviceable event view you are
v MABIP03 working with. If you are working from this document's
v BRDGSET FRU list use the Symbolic FRU BRDGSET to determine
v OPT_CLN the failing items.
Failing Item:
v BRDGSET
v SIIOADP
v MA_BRDG
(B6xx) Reference codes 615
B6xx6974 • B6xx6982
v SICNTRL
B6xx6974 B6xx6974
v OPT_CLN
Explanation: Multi-adapter bridge configuration
change or error
B6xx6981 B6xx6981
Response: PCI I/O processor rejected the assignment
of or the removal of an I/O adapter. Explanation: High Speed Link (HSL) I/O bridge
failure
Failing Item:
Response: For Power5 and newer servers, service this
v MABRCFG
error using the B7006981 service information.
Otherwise, continue with this information.
B6xx6975 B6xx6975
Cycle power on the frame identified as the frame with
Explanation: The system issued a reset/reload to the failed HSL I/O Bridge prior to replacing FRUs.
service processor.
The FRU list displayed in the Service Action Log (SAL),
Response: Service processor error. or serviceable event view you are using, may vary from
the failing item list given in this document. Use the
Failing Item:
FRU list in the serviceable event view if it is available
v AJDGP01 to you.
If you find either a B6xx 6982 or B6xx 6984 SRC logged
B6xx6976 B6xx6976 at approximately the same time as this SRC then they
Explanation: Service processor failure. were caused by the same failure. If you find a 6982
SRC logged at approximately the same time then close
Response: For this reference code the failing item list this problem and service the 6982 SRC. The failing item
presented in the Service Action Log (SAL), or listed for this SRC is one of the failing items listed for
serviceable event view you are working with, can be B6xx 6982. If the serviceable event view's entry for this
different from the failing item list documented here. SRC has a location listed then record the location for
That is due to the differences in system models and use in servicing the 6982 SRC.
features installed.
NOTE: This SRC can occur for the HSL I/O Bridge
If the Service Action Log (SAL) or a serviceable event resource in an I/O expansion unit when the unit is
viewer on the hardware management console is powered off for a concurrent maintenance action.
available then use the failing item list presented there
for servicing this reference code. NOTE: A fiber optic cleaning kit may be required for
optical HSL connections.
If a serviceable event viewer is not available then use
the failing item list documented here. By following the Failing Item:
procedures in the symbolic FRUs listed here you will v SIIOADP
isolate to the correct FRU list based on system model v OPT_CLN
and features installed.
Failing Item: B6xx6982 B6xx6982
v SVCPROC
Explanation: High Speed Link (HSL) connection
failure
B6xx6980 B6xx6980
Response: For Power5 and newer servers, service this
Explanation: Network Interface Controller / IO Hub error using the B7006982 service information.
failure. Otherwise, continue with this information.
Response: For Power5 and newer servers, service this If this SRC is not in the Service Action Log (SAL) or
error using the B7006980 service information. serviceable event view you are using, then it is
Otherwise, continue with this information. informational or statistical only. It does not require a
service action.
The FRU list displayed in the Service Action Log (SAL)
or serviceable event view you are working with, may Otherwise, this is a connection failure on an HSL link.
vary from the failing item list given in this document. Perform the procedure indicated in the failing item list.
Use the FRU list in the serviceable event view if it is
Failing Item:
available to you.
v RIOIP09
NOTE: A fiber optic cleaning kit may be required for
v HSL_LNK
optical HSL connections.
v SIIOADP
Failing Item:
v SICNTRL
616 System reference codes (Bxxx)
B6xx6983 • B6xx6985
v REM_NIC serviceable event view you are using, then it is
v OPT_CLN informational. Use FRU SIRSTAT to determine what
this SRC means. Otherwise, continue with the
following steps:
B6xx6983 B6xx6983
This error can appear as a serviceable event when a
Explanation: An invalid High Speed Link (HSL) tower, or I/O unit or another system in the loop did
configuration was detected not complete powering on before LIC on this system
Response: For Power5 and newer servers, service this checked this loop for errors. Search the Product
error using the B7006983 service information. Activity Log (PAL) for the last B6xx 6985 SRC logged
Otherwise, continue with this information. for this loop and use FRU SIRSTAT to determine if this
error requires service. If the last entry indicates the
An HSL loop has an invalid configuration. Word 4 of loop is functioning (determined by FRU SIRSTAT) then
the SRC contains the program return code (PRC) which no service action is required, close this problem
identifies the problem with the loop's configuration.
Use the PRC and the FRU listed below to determine There may be multiple B6xx 6985 logs with xxxx 3205
the problem. in word 4 errors for the same loop resource in the
serviceable event view. This is caused by retry and
If you are using the Service Action Log (SAL) or recovery attempts. If there is a B6xx 6985 with xxxx
serviceable event view you are working with, the FRU 3206 or xxxx 3208 in word 4 after the above B6xx 6985
description may already indicate the configuration entries in the PAL, then the recovery efforts were
problem. successful. If this is the case, close all the B6xx 6985
entries for that loop resource in the serviceable event
Failing Item:
view.
v SIRGCFG
1. If you find a B6xx 6981 in the serviceable event
view then close that problem and go to step 2.
B6xx6984 B6xx6984 Otherwise perform the following:
Explanation: High Speed Link (HSL) loop status v Perform RIOIP06 to determine if any other
message systems are connected to this loop and return
here. (HSL_LNK or HSLxxxx FRU in the Service
Response: For Power5 and newer servers, service this Action Log (SAL) entry, or serviceable event view
error using the B7006984 service information. you are working with, indicates the loop
Otherwise, continue with this information. number.) If there are other system(s) then
An HSL loop has switched to its alternate path. This is continue with the steps that follow, otherwise go
an informational SRC only. to step 2.
v Check for HSL failures on the other system(s)
Word 7 of the SRC contains the loop number in the before replacing parts. HSL failures are
leftmost 4 digits. The loop number is in hexadecimal serviceable event entries with HSL I/O Bridge
format. You must convert the hexadecimal loop number and Network Interface Controller (NIC)
into decimal format to recognize the loop number in resources. Ignore B6xx 6982 and B6xx 6984
HSM. entries. If there are HSL failures on other
This SRC can be caused by a tower on the HSL loop system(s) then continue with the steps that
powering off. follow, otherwise go to step 2.
v Repair the problems on the other systems and
This SRC may also appear in the Service Action Log
return to this step. After making repairs on the
(SAL), or serviceable event viewer you are using, with
other system(s) check the Product Activity Log
a B6xx 6982 or B6xx 6981 logged at approximately the
(PAL) of this system for a B6xx 6985 logged after
same time. In that case the other SRC is reporting a
the repairs you made on the other system(s). If
failure and this SRC is reporting that the alternate HSL
you find one then continue with the steps that
path is now being used. Service the other SRC if
follow, otherwise go to step 2.
present.
v For the B6xx 6985 log you found, use FRU
SIRSTAT to determine if the loop is now
B6xx6985 B6xx6985 complete. If the loop is complete then this
Explanation: High Speed Link (HSL) loop status problem has been resolved. Use RIOIP01 to verify
message that the loop is now working properly.
Otherwise, go to step 2.
Response: For Power5 and newer servers, service this
2. Use the serviceable event's FRU list when it is
error using the B7006985 service information.
available.
Otherwise, continue with this information.
If this SRC appears in the Service Action Log (SAL),
If this SRC is not in the Service Action Log (SAL), or or the serviceable event view you are using, with
(B6xx) Reference codes 617
B6xx6986 • B6xx6993
the Symbolic FRU HSL_LNK or HSLxxxx listed as a 1. If the connection is copper and either end has a
FRU, then perform problem isolation procedure loose connection, re-seat the cable. To do this,
RIOIP01. Otherwise exchange the FRUs listed in the disconnect the connection and wait a minimum
serviceable event view. of 30 seconds. Then reconnect the cable and
complete the tightening process in at most 30
NOTE: A fiber optic cleaning kit may be required for seconds. Repeat the process at the other end of
optical HSL connections. the cable. If the error persists, replace the FRUs in
the Service Action Log (SAL), or serviceable event
Failing Item: view you are using.
v SIRSTAT 2. If the connection is optical, clean the connections
v HSL_LNK at both ends of the cable. If the error persists,
v SIIOADP replace the FRUs in the Service Action Log (SAL),
serviceable event view you are using.
v SICNTRL
3. If the error persists, replace the FRUs at each end
v OPT_CLN
of the cable starting with the FROM FRU listed in
the serviceable event view you are using.
B6xx6986 B6xx6986 v If there was no cable in the Service Action Log
Explanation: System bus error (SAL), or serviceable event view you are using, then
replace the FRUs listed in the serviceable event view.
Response: For Power5 and newer servers, service this
error using the B7006986 service information. Failing Item:
Otherwise, continue with this information. v HSL_LNK
During IPL, system LIC detected an HSL I/O bridge v OPT_CLN
that was already initialized. The bridge should have
been in a flushed and uninitialized state after powering B6xx6990 B6xx6990
on. There is a problem with SPCN components that
prevented the tower from powering off after a previous Explanation: Service processor failure.
power off was issued. The tower will not be configured Response: The FRU list displayed in the Service
for this IPL. Action Log (SAL), or serviceable event view you are
This reference code is equivalent to 1xxx 90F0. When working with, may vary from the failing item list given
referring to the "CBLALL" symbolic FRU in the Failing in this document. Use the FRU list in the serviceable
Item list, perform the "CBLALL" procedure using event view if it is available to you.
reference code "90F0". Failing Item:
Word 5 of the SRC identifies the frame. Determine the v SVCPROC
frame by breaking down word 5:
Word 5 -> xxxx xxNN where: NN is the frame number B6xx6991 B6xx6991
in hexadecimal format.
Explanation: Service processor failure.
Failing Item:
Failing Item:
v TWRCARD
v AJDGP01
v CBLALL
B6xx6992 B6xx6992
B6xx6987 B6xx6987
Explanation: Service processor failure.
Explanation: High Speed Link (HSL) connection
failure Failing Item:
Response: For Power5 and newer servers, service this v AJDGP01
error using the B7006987 service information.
Otherwise, continue with this information. B6xx6993 B6xx6993
Failures are occurring on the HSL link. Explanation: Service processor failure.
There may be B6xx 6982 errors logged on the same Response: A failure occurred with the service
loop and about the same time as this error. Close those processor hardware or the service processor LIC.
errors and continue to correct the problem by working
this error. The FRU list displayed in the Service Action Log (SAL),
or serviceable event view you are working with, may
v If there is a cable FRU in the serviceable event entry:
vary from the failing item list given in this document.
618 System reference codes (Bxxx)
B6xx6994 • B6xx69C6
Use the FRU list in the serviceable event view if it is suspect an Opti-connect problem. Otherwise this is a
available to you. tracking event.
Failing Item: Failing Item:
v SVCPROC v NEXTLVL
v AJDGP01
B6xx69C2 B6xx69C2
B6xx6994 B6xx6994 Explanation: HSL Opticonnect normal connect to
Explanation: Service processor failure. another sys. or partition.
Response: The FRU list displayed in the Service Response: This reference code is informational only.
Action Log (SAL) or serviceable event view you are HSL OptiConnect has established connection normally.
working with, may vary from the failing item list given The local system or partition is participating in HSL
in this document. Use the FRU list in the serviceable Opticonnect with other systems or partitions on the
event view if it is available to you. same HSL loop.
Failing Item:
v SVCPROC B6xx69C3 B6xx69C3
Explanation: HSL Opticonnect normal disconnect from
B6xx699C B6xx699C other sys. or partition
Explanation: Wrap plug is installed on Bus Expansion Response: This reference code is informational only.
Adapter card
HSL Opticonnect disconnected normally from a remote
Response: This reference code is for information only. node. The local system or partition has stopped
It indicates the presence of a wrap plug on the local participating in HSL Opticonnect with the remote
optical link card. system or partition on the same HSL loop. Possible
reasons include:
B6xx69A8 B6xx69A8 v A remote system or partition went off line due to a
normal power off or disable of HSL Opticonnect.
Explanation: Informational bus reference code
Response: This reference code is for information only B6xx69C5 B6xx69C5
and might include the following:
Explanation: I/O processor failure
v Optical speed encode
v Broken optical links now operational Response: Contact your next level of support.
v Other information Failing Item:
v NEXTLVL
B6xx69B8 B6xx69B8
Explanation: Bus hardware configuration problem B6xx69C6 B6xx69C6
Response: Contact your next level of support. Explanation: HSL Opticonnect abnormal disconnect
from other sys. or partition.
Failing Item:
Response: The local system or partition disconnected
v NEXTLVL
from a remote system or partition due to an
unexpected event or failure. The problem is most likely
B6xx69C1 B6xx69C1 with the remote system or partition. Intervention at the
remote system is most likely required. Examine both
Explanation: A failure occurred communicating with the local and remote HSL OptiConnected systems or
another LPAR or system participating in Opti-connect partitions for problems on this HSL loop.
with this LPAR or system. Starting with IBM i release
7.1 this event will be logged in the Product Activity Possible reasons include: A fatal error in software or
Log but it will not be in the Service Action Log or the hardware in the remote system or partition or a power
Problem Log. This event normally occurs when the failure in the remote system.
other LPAR or system is powered off. If both LPARs or
If there was not a complete HSL loop before this error
systems are running and have no Opti-connect errors
occurred then a failure or power down in an HSL
then this event is indicating a possible problem with
component between the local system or partition and
Opti-connect.
the remote system or partition could have caused this
Response: Contact your next level of support if you error. Check for a problem with: an HSL cable, HSL
(B6xx) Reference codes 619
B6xx69C7 • B6xx69C8
I/O bridge or a power problem in an expansion I/O partition and there are no problems with the local
tower or unit on this loop. system or partition then collect all the Product Activity
Log (PAL) information for this failure on both systems.
Examine the Service Action Log (SAL), or serviceable
Be sure to record all words in the SRC. Contact your
event view you are using on the local system or
next level of support.
partition for HSL failures on the same HSL loop at
approximately the same time this error occurred. Failing Item:
Examine the remote system or partition for problems. If v REM_SYS
the remote system or partition is powered on and IPL'd v LOC_SYS
then examine the Service Action Log (SAL), or
serviceable event view you are using, on the remote
B6xx69C8 B6xx69C8
system or partition for problems on the same HSL loop
at approximately the same time this error occurred. Explanation: HSL Opticonnect abnormal disconnect
from other sys. or partition.
Correct any problems you find with the remote and
local systems or partitions that happened at Response: The local system or partition disconnected
approximately the same time and involve HSL from a remote system or partition due to an
Opticonnect or HSL loop components or Network unexpected event or failure. All of the HSL
Interface Controllers. When the remote system is IPL'd OptiConnect connections on this loop will be in a failed
it will automatically reconnect with this system or state. LIC will attempt to recover from the error.
partition. Intervention at the local or remote system or partition
may be required. Possible causes are:
If there are no problems with the remote system or
partition and there are no problems with the local v time out of a critical message
system or partition then collect all the Product Activity v LIC code / table problem
Log information for this failure on both systems. Be v Network deadlock detected
sure to record all words in the SRC. Contact your next
level of support.
The problem may be with:
Failing Item: v The local system or partition
v REM_SYS v The remote system or partition
B6xx69C7 B6xx69C7 Examine the Service Action Log (SAL), or serviceable
event view you are using, on the local system or
Explanation: HSL Opticonnect abnormal disconnect partition for HSL failures on the same HSL loop, or
from other sys. or partition. with the Network Interface Controller at approximately
Response: The local system or partition disconnected the same time this error occurred.
from a remote system or partition due to an
unexpected event or failure. LIC will attempt to recover Examine the remote system or partition for problems.
from the error. Intervention at the local or remote Examine the Service Action Log (SAL), or serviceable
system or partition may be required. event view you are using, on the remote system or
partition for problems on the same HSL loop or with
Possible causes are: time out, hang or hardware failure. the Network Interface Controller at approximately the
The problem may be with: the local system or partition same time this error occurred.
or the remote system or partition.
If there was not a complete HSL loop before this error Correct any problems you find with the remote and
then a failure or power down in an HSL component local systems or partitions that happened at
between the local system or partition and the remote approximately the same time and involve HSL
system or partition could have caused this error. Check Opticonnect or HSL loop components or Network
for SRCs with FRUs like: HSL cables, HSL I/O bridge Interface Controllers.
or a power problem in an expansion I/O tower or unit
on this loop. If there are no problems with the remote system or
partition and there are no problems with the local
Examine the SAL or serviceable event view you are system or partition then collect all the Product Activity
working with on the local system or partition for Log information for this failure on all systems or
failures on the same loop, or with the Network partitions. Be sure to record all words in the SRCs.
Interface Controller at approximately the same time. Contact your next level of support.
Examine the remote system or partition for problems. Failing Item:
Correct any HSL or NIC problems you find with the
v REM_SYS
remote and local systems or partitions.
v LOC_SYS
If there are no problems with the remote system or
620 System reference codes (Bxxx)
B6xx69C9 • B6xx69DC
v AJDG301 next level of support with the information you have
collected.
B6xx69C9 B6xx69C9 Failing Item:
Explanation: HSL Opticonnect abnormal disconnect v AJDG301
from other sys. or partition.
Response: The local system or partition disconnected B6xx69D0 B6xx69D0
from a remote system or partition due to an failure in a Explanation: Bus Expansion Adapter card failed
LIC virtualized bus unit. LIC will attempt to recover
from the error. Possible causes are: Response: Contact your next level of support.
v LIC problem where the local bus unit is off line. Failing Item:
v LIC problem where the remote bus unit is off line. v NEXTLVL
Examine the Service Action Log (SAL), or serviceable
B6xx69D8 B6xx69D8
event view you are using, on the local system or
partition for HSL Opticonnect failures that occurred at Explanation: Bus Expansion Adapter failed
approximately the same time this error occurred.
Response: Contact your next level of support.
Examine the remote system or partition for problems. Failing Item:
Examine the Service Action Log (SAL), or the v NEXTLVL
serviceable event view you are using, on the remote
system or partition for HSL Opticonnect problems that
occurred at approximately the same time this error B6xx69D9 B6xx69D9
occurred.
Explanation: Host Ethernet Adapter (HEA) failure
Collect all the Product Activity Log information for this Response: Firmware detected a hardware failure in
failure on all systems and partitions on this HSL loop. the Host Ethernet Adapter (HEA).
Be sure to record all words in the SRCs. Contact your
Failing Item:
next level of support with the information you have
collected. v HEA
Failing Item:
B6xx69DA B6xx69DA
v AJDG301
v REM_SYS Explanation: System log entry only, no service action
required
v LOC_SYS
B6xx69DB B6xx69DB
B6xx69CF B6xx69CF
Explanation: LIC failure
Explanation: HSL Opticonnect abnormal disconnect
from other sys. or partition. Response: A Licensed Internal Code error occurred.
The partition will continue to run with this Host
Response: LIC internal error. All systems participating
Ethernet Adapter (HEA) disabled. Perform a partition
in HSL OptiConnect will be disconnected. The system
dump and then IPL the partition to recover the HEA.
must be re-IPL'd to recover. Before re-IPL'ing the
Send the partition dump to your next level of support.
system initiate a main store dump.
Failing Item:
After getting the dump, examine the Service Action
Log (SAL), or serviceable event view you are using, on v SVCDOCS
the local system or partition for HSL Opticonnect
failures that occurred at approximately the same time B6xx69DC B6xx69DC
this error occurred.
Explanation: The HEA is not connected to the
Examine the remote systems or partitions for problems. Ethernet switch
Examine the Service Action Log (SAL), or serviceable
event view you are using, on the remote systems or Response: The Host Ethernet Adapter (HEA) is not
partitions for HSL Opticonnect problems that occurred connected to the Ethernet switch. If the HEA
at approximately the same time this error occurred. connection is not needed, no service action is required.
Collect all the Product Activity Log information for this If the HEA connection is needed, verify that the cable is
failure on all systems and partitions on this HSL loop. connected and the switch is powered on. After
Be sure to record all words in the SRCs. Contact your
(B6xx) Reference codes 621
B6xx69DD • B6xx7204
repairing the problem, verify that the connection has
B6xx7004 B6xx7004
been restored.
Explanation: TCP/IP informational error
B6xx69DD B6xx69DD Response: This reference code is logged when the
TCP/IP Attribute Log Protocol Errors is set, and the
Explanation: The HEA connection to the Ethernet
TCP/IP System LIC silently discards an in bound
switch has been restored
datagram. Silently discard is defined to mean discard
Response: System log entry only, no service action the received datagram without reporting an error to the
required. originating host device. Examples of such datagrams
are those with checksums or destination addresses
which are not valid.
B6xx69DE B6xx69DE
This reference code is for information only. Normally
Explanation: HEA Media Interface Adapter Failure no action should be taken as a result of this reference
Response: Firmware detected a failure in the HEA code. It is generated in order to assist with remote
Media Interface Adapter. device or TCP/IP network problem determination.
Failing Item:
B6xx7055 B6xx7055
v HEA
v AJDG301 Explanation: Statistics were logged, no service action
required
B6xx69E0 B6xx69E0 Response: This reference code is logged for
information only.
Explanation: Bus Expansion Adapter card failed
Response: Contact your next level of support. B6xx7102 B6xx7102
Failing Item: Explanation: APPN CP-CP session ended.
v NEXTLVL
B6xx7201 B6xx7201
B6xx69E8 B6xx69E8
Explanation: A utility failure occurred
Explanation: Bus Expansion Adapter failed
Response: This reference code is for information only.
Response: Contact your next level of support. The Uninterruptible Power System (UPS) is reporting a
utility failure.
Failing Item:
v NEXTLVL
B6xx7202 B6xx7202
B6xx69F0 B6xx69F0 Explanation: Utility power restored
Explanation: Bus Expansion Adapter failed Response: This reference code is for information only.
The Uninterruptible Power System (UPS) is reporting
Response: Contact your next level of support. that utility power has been restored.
Failing Item:
v NEXTLVL B6xx7203 B6xx7203
Explanation: A battery low condition was detected
B6xx69F8 B6xx69F8
Response: This reference code is for information only.
Explanation: Bus Expansion Adapter failed The Uninterruptible Power System (UPS) is reporting a
battery low condition.
Response: Contact your next level of support.
Failing Item: B6xx7204 B6xx7204
v NEXTLVL
Explanation: Uninterruptible Power System reported a
bypass active
B6xx7001 B6xx7001
Response: This reference code is for information only.
Explanation: ISDN call in rejected The Uninterruptible Power System (UPS) is reporting a
bypass is active.
Failing Item:
v UG3LB
622 System reference codes (Bxxx)
B6xx7205 • B6xx8005
3. The resource may not have reported in on this IPL
B6xx7205 B6xx7205
because it is failing. Perform problem analysis to
Explanation: Battery low condition was reset determine why the resource is failing.
Response: This reference code is for information only.
The Uninterruptible Power System (UPS) is no longer B6xx8000 B6xx8000
reporting a battery low condition.
Explanation: An external storage subsystem disk unit
connection failed
B6xx7206 B6xx7206
Response: Look for other errors in the Service Action
Explanation: UPS reported bypass no longer active Log (SAL), or serviceable event view you are working
with, and fix them.
Response: This reference code is for information only.
The Uninterruptible Power System (UPS) is no longer
reporting a bypass active condition. B6xx8001 B6xx8001
Explanation: An external storage subsystem disk unit
B6xx720A B6xx720A connection failed
Explanation: Battery Power Unit replacement dates do Response: Look for other errors in the Service Action
not match Log, or serviceable event view you are working with,
and fix them.
Response: The replacement dates for one of the
Battery Power Units do not match. Run "Display
Hardware Configuration" and verify that the dates B6xx8002 B6xx8002
match the labels on the batteries.
Explanation: Maximum number of redundant
connections exceeded
B6xx7703 B6xx7703
Response: An attempt to activate a connection from
Explanation: System LIC detected a program another I/O adapter to an external storage subsystem
exception disk unit failed because the maximum number of
connections are already active for this disk unit. No
Response: Storage Management detected a DASD
action required.
datacheck condition and the defective sector was
reallocated.
B6xx8003 B6xx8003
Perform a system IPL to restart the system.
Explanation: External storage subsystem disk unit
connection was restored
B6xx7704 B6xx7704
Response: No action required.
Explanation: General failure detected by HRI
component.
B6xx8004 B6xx8004
Failing Item:
v AJDG301 Explanation: An external storage subsystem disk unit
connection failed
B6xx7777 B6xx7777 Response: Could not read configuration information
from the disk unit. Look for other errors in the Service
Explanation: Hardware configuration change detected Action Log, or serviceable event view you are working
Response: A hardware resource is missing. The with, and fix them.
resource reported in to the system on a previous IPL,
but has not reported in on the current IPL. This could B6xx8005 B6xx8005
occur for several different reasons.
Explanation: High performance connection failed
1. It could be a normal situation where the resource is
currently powered off. In this case, when the Response: A high performance connection to an
resource is powered back on, it will no longer be external storage subsystem disk unit failed.
missing.
There are still two or more external storage subsystem
2. The hardware resource could also be missing if it disk unit connections, but performance might be
has been removed from the system, for example, a degraded.
tape drive that was replaced with a different tape
drive. The service representative should use the Look for other errors in the Service Action Log, or
Hardware service manager to remove the entry for serviceable event view you are working with, and fix
this resource. them.
(B6xx) Reference codes 623
B6xx8006 • B6xxD4C1
removable media Load Source device failure. If the
B6xx8006 B6xx8006
removable media Load Source is an external device,
Explanation: High performance connection failed check the cables. If that does not correct the problem,
replace the device. If the removable media Load Source
Response: A high performance connection to an
is an internal device, replace the device. If the
external storage subsystem disk unit failed.
removable media Load Source is a virtual device,
There is still one more external storage subsystem disk ensure it is set up correctly.
unit connection, but performance might be degraded.
Failing Item:
Look for other errors in the Service Action Log, or v SVCDOCS
serviceable event view you are working with, and fix
them.
B6xxCF01 B6xxCF01
B6xx8007 B6xx8007 Explanation: Unsupported removable media device
configuration.
Explanation: High performance connection was
restored Problem determination: A type D IPL terminated
because of an unsupported removable media device
Response: A high performance connection to an configuration. Retry the D-IPL with a different
external storage subsystem disk unit was restored. removable media device.
Performance is no longer degraded. Failing Item:
No action required. v SVCDOCS
B6xx9999 B6xx9999 B6xxCFFC B6xxCFFC
Explanation: Call home test SRC built into LIC for Explanation: Optical library device condition not
testing and verification. No service action is needed. expected
Problem determination: None, this SRC means that a Response: The optical disk drive addressing within
LIC call home test was triggered to determine if the optical library is incorrect. This error is likely to be
problem reporting functions are set up correctly. the result of faulty cabling or switch setting following
service to an optical library.
B6xx999A B6xx999A Contact your hardware service provider.
Explanation: Notification test SRC built into LIC for Failing Item:
testing and verification. No service action is needed. v OPTLCBL
Problem determination: None, this SRC means that a v DRVSWCH
LIC serviceable test was triggered to determine if
problem reporting functions are set up correctly. This
B6xxCFFD B6xxCFFD
SRC will show up in the Problem Log but will not
automatically call home. Explanation: Optical drive failure
Failing Item:
B6xxB700 B6xxB700 v OPTLDRV
Explanation: A platform firmware error log was
signalled to LIC but could not be retrieved from B6xxCFFF B6xxCFFF
platform firmware. LIC created this event in the PAL
with SRC B600B700 to log the problem. Explanation: Media determined to be bad in Optical
library
Problem determination: Contact your hardware
service provider. This is a platform firmware problem.
B6xxD4C1 B6xxD4C1
Failing Item:
Explanation: LIC detected a problem in error analysis
v NEXTLVL
code.
Problem determination: Report this problem to your
B6xxCF00 B6xxCF00
service provider.
Explanation: Permanent error on removable media
Failing Item:
device.
v SVCDOCS
Response: A type D IPL terminated because of a
624 System reference codes (Bxxx)
B6xxD4C2 • B6xxFDC5
B6xxD4C2 B6xxD4C2 B6xxF105 B6xxF105
Explanation: LIC detected a problem in error analysis Explanation: Licensed Internal Code detected error
code.
Failing Item:
Problem determination: Report this problem to your v NEXTLVL
service provider.
Failing Item: B6xxFDC0 B6xxFDC0
v SVCDOCS
Explanation: LIC program reported informational
error
B6xxD4C3 B6xxD4C3
Response: This reference code is logged for
Explanation: LIC detected a problem in error analysis information only. No action required.
code.
Problem determination: Report this problem to your B6xxFDC5 B6xxFDC5
service provider.
Explanation: LIC program failed and data was
Failing Item: captured
v SVCDOCS Response: This reference code indicates first failure
data capture (FFDC) data was collected for a problem
B6xxD4C4 B6xxD4C4 reported by licensed internal code.
Explanation: LIC detected a problem in error analysis The user should dial IBM Software Support for
code. assistance.
Problem determination: Report this problem to your Failing Item:
service provider. v UG3AS
Failing Item:
v SVCDOCS
B6xxD4C5 B6xxD4C5
Explanation: LIC detected a problem in error analysis
code.
Problem determination: Report this problem to your
service provider.
Failing Item:
v SVCDOCS
B6xxF103 B6xxF103
Explanation: Main storage dump must be copied for
service
Failing Item:
v LICIP01
B6xxF104 B6xxF104
Explanation: LPAR service function directed a Main
Storage Dump.
Response: The Hypervisor terminated a partition with
an unresponsive Operating System. A Main Store
Dump must be done for service. Call your next level of
support when the dump is complete.
Failing Item:
v LICIP01
(B6xx) Reference codes 625
626 System reference codes (Bxxx)
(B7xx) Reference codes
A B7xx reference code indicates that an event or error was detected and logged by platform firmware.
To resolve a B7xx reference code, determine if the SRC requires a service action.
If the SRC is listed in a serviceable event view, use the FRU list from the serviceable event view to
determine the actions to take.
If you do not find the SRC in a serviceable event view, then it is an informational event and does not
require service action.
Explanation: Platform LIC failure
B7000102 B7000102
Response: A secondary failure due to an invalid SRC
Explanation: Platform LIC detected an error
occurred when the platform attempted to terminate.
Response: A machine check occurred during IPL.
Collect all the SRC words and the platform system
Words 2 to 9 of this SRC contain additional diagnostic
dump, then contact your next level of support.
information. Record SRC words 1 through 9 before
attempting to IPL again and report the problem to next Failing Item:
level of support. v NEXTLVL
Failing Item:
v SVCDOCS B7000107 B7000107
Explanation: Platform LIC failure
B7000103 B7000103
Response: The server detected an unrecoverable
Explanation: Platform LIC failure machine check condition. Collect all the words of the
SRC and the platform dump and send to your system
Response: The platform Licensed Internal Code (LIC)
manufacturer for analysis.
detected an internal problem.
Failing Item:
Collect all the SRC words and the platform system
dump, then contact your next level of support. v SVCDOCS
Failing Item:
B7000200 B7000200
v NEXTLVL
Explanation: System firmware has experienced a low
storage condition
B7000104 B7000104
Response: As soon as possible, collect all ASMI logs,
Explanation: Platform LIC failure
IQQYLOGs and partition logs, if applicable. Work with
Response: Machine check, undefined error occurred. the customer to determine a convenient time to
perform a platform dump and re-IPL the platform.
Failing Item:
v LICCODE Record the firmware level of the system, and send the
platform dump and all logs to development. Check to
determine if the problem is already fixed in a newer
B7000105 B7000105 firmware level.
Explanation: Platform LIC detected an error Problem determination: No immediate action is
Response: More than one request to terminate the necessary.
system was issued. Continue running the system normally. If
Failing Item: firmware-related commands are not responding or are
failing, or firmware tasks have failed (e.g. SRC
v NEXTLVL B7000602), work with your service provider to take a
platform dump at the earliest convenient time or
B7000106 B7000106 service window.
© Copyright IBM Corp. 2010, 2013 627
B7000201 • B7000611
Failing Item:
B7000441 B7000441
v SVCDOCS
Explanation: Service processor failure
B7000201 B7000201 Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
Explanation: Platform firmware detected an error documented here to determine the parts to exchange.
Response: Work with the customer to determine a The platform encountered an error early in the IPL or
convenient time to perform a platform dump and termination process.
re-IPL the platform.
Failing Item:
Problem determination: No immediate action is
v SVCPROC
necessary.
v NEXTLVL
Continue running the system normally. At the earliest
convenient time or service window, work with your
service provider to take a platform dump. B7000443 B7000443
Failing Item: Explanation: Service processor failure
v SVCDOCS Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
documented here to determine the parts to exchange.
B7000202 B7000202
Failing Item:
Explanation: The paging VIOS did not respond
correctly to a LIC request. v SVCPROC
v NEXTLVL
Response: If the platform is HMC or SDMC managed:
1. If there are multiple VIOS servers running,
determine which one is acting as the paging VIOS B7000601 B7000601
by looking at the shared memory pool properties. Explanation: System log entry only, no service action
2. Validate that the paging VIOS is in 'Running' state required
via the HMC or SDMC GUI or Command Line.
Response: Support can use this SRC and associated
3. Verify you can access the paging VIOS console, and data to determine why the time of day for a partition
interact with the paging VIOS operating system. was lost. No corrective action is required.
4. If steps 2 or 3 are unsuccessful, look for other
errors and perform any actions indicated to resolve
B7000602 B7000602
those errors.
Explanation: Platform LIC detected an error
If the platform is not HMC or SDMC managed, or the
Response: Work with the FRU list in the serviceable
above steps do not resolve the problem, contact your
event view if there is one, otherwise use the FRU list
service provider.
documented here to determine the parts to exchange.
Failing Item:
Platform Licensed Internal Code (LIC) detected an error
v SVCDOCS condition. The second word indicates the severity of
the error and the specific error condition. If word 2 is
B7000302 B7000302 10000A01 then record the SRC words and call your
next level of support; otherwise this does not require
Explanation: Platform LIC failure service.
Response: Work with the FRU list in the serviceable Failing Item:
event view if there is one, otherwise use the FRU list
v NEXTLVL
documented here to determine the parts to exchange.
Perform a platform system dump and notify your
B7000611 B7000611
service provider. IPL the system.
Explanation: System clock problem
Failing Item:
v LICCODE Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
documented here to determine the parts to exchange.
For systems managed by an HMC or SDMC, use the
ASM interface to reset the system clock at power on
628 System reference codes (Bxxx)
B7000621 • B7000A10
standby. For systems without an HMC or SDMC, you
B7000803 B7000803
can ignore this error.
Explanation: System log entry only, no service action
If the error occurs a second time, call your next level of
required
support.
Failing Item:
B7000804 B7000804
v SVCDOCS
Explanation: System log entry only, no service action
required
B7000621 B7000621
Explanation: Informational event logged at each B7000A00 B7000A00
Platform IPL. System log entry only, no service action
required Explanation: A user request initiated an I/O
tower/drawer power off. System log entry only, no
service action required.
B7000641 B7000641
Explanation: Platform LIC detected an error B7000A01 B7000A01
Response: A platform LIC failure occurred. Perform a Explanation: Fault indicator activation failure
platform dump and contact your next level of support.
Response: A failure occurred while trying to activate a
Failing Item: fault indicator.
v SVCDOCS
Look for and correct errors in the Serviceable Event
View that were logged at approximately the same time
B7000650 B7000650 as this error.
Explanation: Platform LIC detected an error If this problem persists, contact your next level of
support.
Response: Resource management was unable to
allocate main storage. A platform dump was started.
B7000A02 B7000A02
Words 2 to 9 of this SRC contain additional diagnostic
information. Record SRC words 1 through 9. Collect the Explanation: A concurrent maintenance procedure has
platform dump and the configuration of the memory failed and left the system in an unknown state. It is
allocation for all partitions on this system. Provide the unsafe to do additional concurrent maintenance
platform dump, configuration data, and the recorded procedures until the system is powered off and back
SRC information to your next level of support. on. The system will prevent you from doing these
procedures. The system should be powered off and
Failing Item: back on as soon as possible.
v NEXTLVL
Response: The system must be powered off and back
on.
B7000651 B7000651
Failing Item:
Explanation: The system detected an error in the v SVCDOCS
system clock hardware
Response: This is a serviceable event only if this error B7000A10 B7000A10
appears in a serviceable event view.
Explanation: System log entry only, no service action
If this is a serviceable event, then work with the FRU required
list in the serviceable event view if there is one.
Otherwise, use the FRU list documented in the Failing Response: No action is required, unless the HMC or
Items column to determine the parts to exchange. SDMC indicates that the concurrent platform firmware
update failed. In that case, the system must be re-IPLed
If the system did not log this error as a serviceable in order for the firmware update to occur. Collect the
event, then no service action is required. error log data for this SRC and contact your next level
Failing Item: of support.
v CLCKMOD
(B7xx) Reference codes 629
B7001160 • B7001733
B7001160 B7001160 B7001731 B7001731
Explanation: Service processor failure Explanation: Platform LIC detected an error
Response: Work with the FRU list in the serviceable Response: The VPD for the system is not what was
event view if there is one, otherwise use the FRU list expected at IPL. The VPD on a memory DIMM is not
documented here to determine the parts to exchange. correct and the memory on the DIMM cannot be used,
resulting in reduced memory.
The platform encountered an error communicating with
the service processor. The platform code attempts a Work with the FRU list in the serviceable event view, if
graceful shutdown of partitions and powers off the there is one. Otherwise, use the FRU list documented
server after a certain time, or when the last partition here to determine the parts to exchange.
indicates shutdown, whichever comes first.
Failing Item:
Failing Item: v MEMDIMM
v LICCODE
v SVCPROC B7001732 B7001732
v PSI_LNK
Explanation: Platform LIC detected an error
Response: The VPD for the system is not what was
B7001161 B7001161
expected at IPL. The VPD on a processor card is not
Explanation: The platform encountered an event correct and the processor card cannot be used, resulting
indicating that the power status has changed. System in reduced processing power.
log entry only, no service action required
Work with the FRU list in the serviceable event view if
there is one. Otherwise, use the FRU list documented
B7001162 B7001162 here to determine the parts to exchange.
Explanation: A platform firmware timeout occured. A Failing Item:
resource dump will be created and the platform will v ANYPROC
continue running.
Failing Item: B7001733 B7001733
v LICCODE
Explanation: Platform LIC failure
Response: A Platform Licensed Internal Code error
B7001163 B7001163
occurred. The IPL will not continue.
Explanation: A platform firmware timeout occured. A
Look for and correct errors with SRCs of the form
resource dump already exists for this condition so a
B1xxxxxx in the Serviceable Event View.
duplicated resource dump will not be created. The
platform will continue running. If there are no serviceable B1xxxxxx errors, or if
correcting the errors did not correct this problem, reset
the server firmware settings.
B7001730 B7001730
Attention: Resetting the server firmware settings results
Explanation: Platform LIC detected an error
in the loss of all of the partition data that is stored on
Response: The VPD for the system is not what was the service processor. Before continuing with this
expected at IPL. operation, make sure that you manually record all
settings that you need to preserve. To reset the server
When word 9 is 00180003, a redundant VPD chip
firmware settings, your authority level must be
exists, and the system will continue to run. Replace the
Administrator or Authorized service provider.
VPD card at your next scheduled maintenance. When
word 9 is not 00180003 replace the VPD card On the ASMI Welcome pane, specify your user ID and
immediately. password, and click Log In. In the navigation area,
expand System Service Aids. Then select Factory
Work with the FRU list in the serviceable event view, if
Configuration. Select Reset server firmware settings
there is one. Otherwise, use the FRU list documented
and click Continue. The service processor will reboot
here to determine the parts to exchange.
after all settings have been reset.
Failing Item:
If that does not resolve the problem, replace the service
v CAPACTY processor.
Failing Item:
v SVCDOCS
630 System reference codes (Bxxx)
B700173A • B7004731
v NEXTLVL
B700173A B700173A
Explanation: A VPD collection overflow occurred
B7004480 B7004480
Response: Look for and resolve other errors in the
Explanation: Platform DUMP Manager event
serviceable event view. If that does not resolve the
problem, check for firmware updates and install them,
if available. If that does not resolve the problem, B70044C0 B70044C0
contact your next level of support.
Explanation: Platform DUMP Manager event
Failing Item:
v SVCDOCS B70044D0 B70044D0
Explanation: Platform DUMP Manager event
B700173B B700173B
Response: Collect all B70044xx logs and contact your
Explanation: Platform LIC detected an error service provider.
Response: A platform LIC failure occurred during Failing Item:
VPD collection.
v SVCDOCS
Look for and correct errors with SRCs of the form
B1xxxxxx in the Serviceable Event View. If that does
not correct the problem, contact your next level of B70044E0 B70044E0
support. Explanation: Platform DUMP Manager event
Failing Item: Response: Collect all B70044xx logs and contact your
v SVCDOCS service provider.
Failing Item:
B7004400 B7004400 v SVCDOCS
Explanation: There is a platform dump to collect
Response: Work with the FRU list in the serviceable B7004715 B7004715
event view if there is one, otherwise use the FRU list Explanation: Platform LIC detected an error
documented here to determine the parts to exchange.
Response: A problem occurred when initializing,
Use the operating system's interface designated to reading, or using system VPD.
collect platform dumps.
Look for errors with SRCs of the form B1xxxxxx in the
Failing Item: Serviceable Event View. Work those errors first. If that
v SVCDOCS does not correct the problem, replace the VPD card.
Work with the FRU list in the serviceable event view if
B7004401 B7004401 there is one, otherwise use the FRU list documented
here to determine the parts to exchange.
Explanation: Platform LIC failure
Failing Item:
Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list v SVCDOCS
documented here to determine the parts to exchange. v CAPACTY
The platform LIC detected an internal problem.
B7004731 B7004731
Contact your next level of support.
Explanation: Platform LIC detected an error
Failing Item:
v NEXTLVL Problem determination: The system has been running
with full Capacity on Demand resources activated. In
one hour, the system will terminate and unlicensed
B7004402 B7004402 resources will no longer be available. To prevent the
system from terminating, enter an activation code of all
Explanation: Platform LIC failure
zeroes. Then obtain the proper activation codes for the
Response: A platform LIC error occurred while resources being used or allocate fewer resources in the
attempting to allocate the memory necessary to create a LPAR configuration.
platform resource dump.
Failing Item:
Failing Item: v SVCDOCS
(B7xx) Reference codes 631
B7004733 • B7005191
B7004733 B7004733 B7005121 B7005121
Explanation: Platform LIC failure Explanation: Platform LIC failure
Response: The Capacity on Demand function is not Response: Licensed Internal Code program exception
available. If Capacity on Demand function is required, occurred.
re-IPL the system. If that does not correct the problem,
Platform Licensed Internal Code detected a
contact your next level of support.
programming problem for which a platform dump may
have been initiated.
B7004750 B7004750
Send the system error log and the platform dump, if it
Explanation: A Capacity on Demand change has been occurred, to your next level of support.
detected
Failing Item:
Response: Utility Capacity on Demand resources have v NEXTLVL
been activated.
B7005122 B7005122
B70047CB B70047CB
Explanation: Platform LIC detected an error
Explanation: Fast system IPL changed to slow system
IPL Response: Platform Licensed Internal Code detected
that an IOP request failed.
Response: The data obtained from the system is not
what was expected. The system will perform a slow This error indicates a failure during a search for the
IPL in order to obtain the correct data. If other errors load source. There may be a number of these failure
occur, contact your next level of support. prior to finding a good load source. This is normal. If a
B2xx3110 error is logged, a B2xx3200 or B7005122 may
be posted to the control panel. Work the B2xx3110 error
B70047CC B70047CC in the Serviceable Event View. If the system IPL hangs
Explanation: (N/A for external service docs) at B2xx3200 or B7005122 and you cannot check the SRC
history, perform the actions indicated for the B2xx3110
SRC.
B70047CD B70047CD
Failing Item:
Explanation: Platform LIC detected an error
v SVCDOCS
Response: The server detected a not valid Capacity
On Demand activation and terminated the system. The
B7005123 B7005123
allocated resources for the system might exceed those
that are available for use. Explanation: Platform LIC detected an error
Failing Item: Response: A Licensed Internal Code program
v SVCDOCS exception or data collection occurred. This may indicate
an IOP programming problem or an IO Adapter boot
problem. Look for other errors. If no other errors are
B70047DD B70047DD present, Licensed Internal Code has recovered from any
Explanation: (N/A for external service docs) exception conditions, or this SRC has logged
informational platform boto or hardware data.
B7005120 B7005120
B7005190 B7005190
Explanation: Platform LIC detected an error
Explanation: PHYP VIO has detected that partition
Response: Work with the FRU list in the serviceable software has created an error condition.
event view if there is one, otherwise use the FRU list
documented here to determine the parts to exchange.
B7005191 B7005191
If the system is not exhibiting problematic behavior,
this error may safely be ignored. Otherwise, contact Explanation: A virtual adapter configuration error
your next level of support. occurred.
Failing Item: A partition tried to use a virtual adapter which is
associated with another virtual adapter in a remote
v NEXTLVL partition and virtual slot. However, either no virtual
adapter is configured there, or the wrong kind of
virtual adapter is configured there.
632 System reference codes (Bxxx)
B7005209 • B7005306
The partition ID of the virtual adapter with the Failing Item:
problem is in word 4 of the SRC (in hexadecimal v SVCDOCS
format). The virtual slot number of the adapter with
the incorrect configuration is the last four digits of
word 6 of the SRC (in hexadecimal format). B7005302 B7005302
Problem determination: Use the HMC or SDMC to Explanation: An unsupported Preferred Operating
verify or reconfigure the incorrect virtual adapter System was detected
configuration. If the configuration is correct, contact Response: The Preferred Operating System specified is
your service provider. not supported. The IPL will not continue. Use ASMI to
Failing Item: select a supported Preferred Operating System and
then, re-IPL the system.
v SVCDOCS
v LICCODE Failing Item:
v SVCDOCS
B7005209 B7005209
B7005303 B7005303
Explanation: Platform LIC detected an error
Explanation: An unsupported Preferred Operating
Response: System Licensed Internal Code detected an
System was detected
IOP timeout during IOP IPL.
Response: The Preferred Operating System specified is
This may be caused by loose connections, improperly
not supported. The IPL will continue. Use ASMI to
seated cards, media, or removeable media drive not in
select a supported Preferred Operating System and
a ready state. Look for other errors.
then, re-IPL the system.
Failing Item:
B7005219 B7005219
v SVCDOCS
Explanation: Platform LIC detected an error.
Information only, no service action required.
B7005304 B7005304
B7005300 B7005300 Explanation: The number of available World Wide
Port Names (WWPN) is low.
Explanation: Platform LIC detected a failure while
partitioning resources Problem determination: To obtain an additional
WWPN root, please contact your system vendor.
Response: Platform partitioning code encountered an
error. This SRC represents a large number of possible Failing Item:
problems, most of which involve the platform Licensed v SVCDOCS
Internal Code (LIC). Work any error logs found in the
Serviceable Event View. If this fails to correct the
problem, or if there are no other errors, contact your B7005305 B7005305
next level of support. Explanation: There are no remaining World Wide Port
Names (WWPN).
B7005301 B7005301 Problem determination: To obtain an additional
Explanation: An LPAR configuration problem was WWPN root, please contact your system vendor.
detected. Failing Item:
Response: System detected a problem with the Logical v SVCDOCS
Partition (LPAR) Configuration.
Use the Hardware Management Console to reconfigure B7005306 B7005306
the LPAR configuration.
Explanation: There is insufficient licensed memory for
Check the HMC or SDMC partition state. firmware to support the manufacturing default
1. If in Recovery state then use the HMC or SDMC to configuration partition.
perform "Recovering partition data on a managed Problem determination: There are two possible
system". solutions to this issue: (A) Contact IBM or marketing
2. Use HMC or SDMC to activate partitions representative to obtain an activation code to license
more memory in the system; or (B) Use management
If the problem persists, collect a system dump and console to configure a partition with less memory.
contact your next level of support. Failing Item:
(B7xx) Reference codes 633
B7005400 • B7005603
v SVCDOCS
B7005600 B7005600
Explanation: System log entry only, no service action
B7005400 B7005400
required.
Explanation: Computational Gard has detected a
Response: An attempt to initialize, read or use system
flawed processor which will be shut off.
VPD was unsuccessful. No action is required for this
Response: Work with the FRU list in the serviceable SRC.
event view if there is one, otherwise use the FRU list
Look for other hardware errors in the Serviceable Event
documented here to determine the parts to exchange.
View and if present, perform the actions indicated.
The platform detected a problem with a processor. The
processor is not functional.
B7005601 B7005601
Look in the Serviceable Event View for a B1xx xxxx
Explanation: Platform LIC failure
error that implicates a processor.
Response: Work with the FRU list in the serviceable
If the Serviceable Event View contains no B1xx xxxx
event view if there is one, otherwise use the FRU list
error, or if resolving the error fails to correct the
documented here to determine the parts to exchange.
problem, contact your next level of support.
There was a problem initializing, reading, or using
Failing Item:
system VPD.
v SVCDOCS
Failing Item:
v NEXTLVL
B7005433 B7005433
Explanation: The requested memory to be mirrored is
B7005602 B7005602
now only partially mirrored due to a hardware issue.
Explanation: Platform LIC detected an error
Response: If a repair action was in progress, check for
deconfigured memory. If that memory was a part of the Response: The system has out-of-date VPD LIDs.
service action and was replaced, disregard this SRC. Contact IBM support for new VPD LIDs.
Otherwise, if no service action involving memory was
Failing Item:
being performed, check the serviceable event view for
memory-DIMM related errors and take the appropriate v NEXTLVL
service action for repair.
Failing Item: B7005603 B7005603
v SVCDOCS Explanation: Enclosure feature code and/or serial
number not valid.
B7005442 B7005442 Platform Licensed Internal Code detected invalid VPD
(feature code and/or serial number) for a System or
Explanation: Platform LIC detected an error
I/O Enclosure. The invalid VPD may prevent the use
Response: The system will terminate. of Concurrent Maintenance on any FRU in the
enclosure and prevent hardware errors from being
Collect all the SRC words and the platform system
reported correctly, so it should be fixed at the next
dump, and then contact your next level of support.
opportunity.
Failing Item:
Response: Look at the FRU callout list in the
v ANYPROC serviceable events view for the B7005603 SRC to obtain
v NEXTLVL the location information which contains the invalid
feature code and/or serial number.
B70054DD B70054DD Note: This SRC does not require a service action if the
location information is "U####.###.#######".
Explanation: System log entry only, no service action
required Next, find the System or I/O enclosure associated with
this location, and locate the enclosure's physical label
Response: A processor checkstop recovery occurred. A which contains the correct feature code and serial
previous error log should provide notification of the number.
failure, as well as any necessary service action.
Depending on whether the invalid VPD is for a System
This error log provides additional information or I/O Enclosure, use the procedure below to correct
regarding the detected reason for the failure and the the VPD.
recovery action taken.
634 System reference codes (Bxxx)
B7006900 • B7006913
If System enclosure: event does not appear in a serviceable event view, no
service action is required.
Note: the system must be powered off prior to
changing the System Enclosure VPD. Failing Item:
1. Using ASM, select: System Configuration -> v SIIOADP
Program Vital Product Data -> System Enclosures. v LICCODE
2. Update the feature code and/or serial number with
the correct value, and then Save the changes.
B7006908 B7006908
If I/O expansion unit: Explanation: System bus error
1. Using ASM, select: System Configuration -> Response: Work with the FRU list in the serviceable
Configure I/O Enclosures -> Change Settings. event view if there is one, otherwise use the FRU list
2. Update the feature code and/or serial number with documented here to determine the parts to exchange.
the correct value, and then Save the changes.
Failing Item:
If the problem has not been resolved, contact your next v SIIOADP
level of support. v MA_BRDG
Failing Item:
v SVCDOCS B7006909 B7006909
Explanation: System bus error
B7006900 B7006900 Response: Work with the FRU list in the serviceable
Explanation: PCI host bridge failure event view if there is one, otherwise use the FRU list
documented here to determine the parts to exchange.
Response: If you find a B7006981 SRC logged at about
same time and listing parts from same enclosure as one Failing Item:
of the FRUs here, then close this problem and work the v SIIOADP
B7006981 SRC. v MA_BRDG
Work with the FRU list in the serviceable event view, if v LICCODE
there is one. Otherwise, use the FRU list documented
here to determine the parts to exchange.
B7006911 B7006911
If the Serviceable Event View is not available, use the
Explanation: Platform LIC unable to find or retrieve
failing item list presented here for servicing this
VPD LID file.
reference code.
Response: Collect error logs and contact next level of
Failing Item:
support.
v PRI_PCI
Failing Item:
v MA_BRDG
v NEXTLVL
v MABIP50
v PIOCARD
B7006912 B7006912
B7006906 B7006906 Explanation: Platform LIC unable to find or retrieve
VPD LID file.
Explanation: System bus error
Response: Contact your next level of support.
Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list Failing Item:
documented here to determine the parts to exchange. v NEXTLVL
Failing Item:
v SIIOADP B7006913 B7006913
Explanation: VPD associated with an occupied PCI
B7006907 B7006907 slot does not contain a PCI slot power value.
Explanation: System bus error Response: Platform firmware update is required.
Response: If this event appears in a serviceable event Failing Item:
view, work with the failing item list found there. If this v LICCODE
(B7xx) Reference codes 635
B7006944 • B7006972
B7006944 B7006944 B7006955 B7006955
Explanation: Platform LIC detected an error Explanation: An NVRAM failure was detected.
Response: A system bus appears to be empty. If the
bus is not empty, a hardware or configuration problem B7006956 B7006956
might exist. Look for other errors.
Explanation: An NVRAM failure was detected.
Response: Contact your next level of support.
B7006950 B7006950
Failing Item:
Explanation: Platform LIC detected an error
v NEXTLVL
Response: A platform dump has occurred. The system
has lost all the configured system settings (such as the
HMC or SDMC access and ASMI passwords, time of B7006965 B7006965
day, network configuration, hardware deconfiguration Explanation: Platform LIC detected an error
policies, etc.) that you might have set through user
interfaces. Also, the system has lost the platform error Response: Unknown hardware detected. Look for
logs and partition-related information, and the service other errors.
processor is reset. Perform the recovery actions for the
SVCPROC FRU but do not replace the service
B7006970 B7006970
processor. The platform dump should be sent to your
service provider. Explanation: PCI host bridge failure
Failing Item: Response: If this event does not appear in a
v SVCDOCS serviceable event view, no service action is required.
If this event appears in a serviceable event view, and if
B7006951 B7006951 you find a B7006981 SRC logged at about the same
time and listing parts from the same enclosure as one
Explanation: Platform LIC detected an error of the FRUs listed in the serviceable event view for
Response: An error occurred because a partition B7006970, then close this problem and work the
needed more NVRAM than was available. B7006981 SRC. Otherwise, work on the B7006970 SRC.
The partition is still functional, but is operating in a Failing Item:
degraded mode. Configuration information may be lost v SIIOADP
at the next IPL. In order to make more NVRAM v MA_BRDG
available, delete one or more partitions.
v MABIP50
Failing Item: v PIOCARD
v SVCDOCS
B7006971 B7006971
B7006952 B7006952
Explanation: PCI secondary bus failure
Explanation: NVRAM was cleared. System log entry
Response: If this event appears in a serviceable event
only, no service action required
view, work with the failing item list found there. If this
event does not appear in a serviceable event view, no
B7006953 B7006953 service action is required.
Explanation: NVRAM unavailable following service Failing Item:
processor reset/reload. v MABIP51
Response: Contact your next level of support. v PIOCARD
Failing Item: v MASBUS
v NEXTLVL v MA_BRDG
B7006954 B7006954 B7006972 B7006972
Explanation: An NVRAM failure was detected. Explanation: System bus error
Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
documented here to determine the parts to exchange.
636 System reference codes (Bxxx)
B7006973 • B7006981
Failing Item:
B700697C B700697C
v MA_BRDG
Explanation: Connection from service processor to
v PRI_PCI
system processor failed
Response: Look for B1xxxxxx SRCs in the Serviceable
B7006973 B7006973
Event View and resolve them.
Explanation: System bus error
If there are no B1xxxxxx SRCs logged, then replace the
Response: If you find a B7006981 SRC logged on the failing items listed in the Serviceable Event View, if
same expansion unit as one of the FRUs here, then they are available. Otherwise, work with the failing
close this problem and work the B7006981 SRC. Use the items listed here.
unit value of the location codes to determine if the
Failing Item:
expansion unit is the same.
v SVCDOCS
Work with the FRU list in the serviceable event view, if
v PSI_LNK
there is one. Otherwise, use the FRU list documented
here to determine the parts to exchange.
B7006980 B7006980
Failing Item:
v PIOCARD Explanation: RIO, HSL or 12X controller failure
v MA_BRDG Response: If the serviceable event view contains a
v PRI_PCI FRU list, work with those FRUs. Otherwise, exchange
the failing items listed here.
v MASBUS
NOTE: A fiber optic cleaning kit may be required for
optical RIO or HSL connections.
B7006974 B7006974
A platform dump has occurred. Send the dump to your
Explanation: IOP rejected the assignment of an IOA
service provider.
Response: An I/O Processor rejected the assignment
Failing Item:
of an I/O Adapter during the IPL of an IBM i
Operating System partition. v SICNTRL
v LICCODE
If the partition IPLed successfully, this event is logged
for information only. No service action is required. v OPT_CLN
If the partition failed to IPL, replace the IOA. If that
does not resolve the problem, replace the IOP that B7006981 B7006981
controls the IOA. Explanation: RIO, HSL or 12X I/O bridge failure
The Direct Select Address (DSA) of the IOA is in word Response: If you find a 1xxx SRC (excluding SRC
7 of the SRC. In order to find the location of the IOA, 10009137) logged on the same expansion unit as one of
see DSA translation to get the unit type in which the the FRUs here, then close this problem and work the
IOA is located. Then using the DSA and unit type, find 1xxx SRC. Use the unit value of the location codes to
the location of the IOA. determine if the expansion unit is the same.
If the 4 rightmost characters of word 4 in the reference
B7006978 B7006978 code equals "3222", it indicates that this I/O bridge
Explanation: The Processor Serial Interface (PSI) link error occurred because of multiple node/processor
failed. Look for B1xx SRCs that were logged at failures. Close this problem, and look in the Serviceable
approximately the same time that this SRC occurred Event View for B1xx xxxx errors that implicate
and resolve them. System log entry only, no service processors and ensure that service action is taken to
action required. resolve the B1xx xxxx errors. If the Serviceable Event
View contains no B1xx xxxx errors, or if resolving those
errors fails to correct the problem, contact your next
B7006979 B7006979 level of support.
Explanation: System log entry only, no service action For all other cases, work with the FRU list in the
required serviceable event view, if there is one. Otherwise, use
the FRU list documented here to determine the parts to
exchange.
Failing Item:
v SVCDOCS
(B7xx) Reference codes 637
B7006982 • B7006983
v SIIOADP v xxxx 3212 indicates the HSL adapter hardware level
v HSL_LNK does not support HSL OptiConnect. Upgrade your
HSL adapter hardware to a supported level for HSL
OptiConnect.
B7006982 B7006982
v xxxx 3213 indicates that the switchable I/O
Explanation: RIO, HSL or 12X connection failure expansion unit configuration is not valid. Re-cable
your HSL OptiConnect so that it has a supported
Response: Work with the FRU list in the serviceable configuration.
event view if there is one, otherwise use the FRU list
documented here to determine the parts to exchange. v xxxx 3217 indicates there is a model 5791, 5792, or
5794 I/O expansion unit on a loop with clustered
NOTE: A fiber optic cleaning kit may be required for systems. This is not a supported configuration.
optical RIO or HSL connections. v xxxx 3218 indicates a concurrent I/O expansion unit
Failing Item: add is not allowed due to an incomplete loop. Look
for and resolve errors on the loop.
v RIOIP11
v xxxx 3219 indicates the 12X cable port connections to
v HSL_LNK
the backplane or riser card of the I/O expansion unit
v OPT_CLN have been reversed. Return the cables to their
v FRPORT previous port connections.
v TOPORT v xxxx 321A indicates that a 12X I/O backplane is
connected to two different I/O hubs. Correct the
cabling so that the 12X I/O backplane is connected
B7006983 B7006983
to only one I/O hub.
Explanation: An invalid RIO, HSL or 12X v xxxx 321B indicates that an I/O hub detected a
configuration was detected. different type of I/O hub on a 12X loop. This is not a
Response: The four rightmost characters of word 4 in supported configuration. Correct the cabling for the
the reference code represent the Program Return Code system.
(PRC), which describes the problem detected. The four v xxxx 321C indicates that an invalid 12X I/O
leftmost digits of word 7 represent the loop number in expansion unit remove was detected. A hot remove
hexadecimal format. Use the DSA translation procedure was performed for an I/O enclosure expansion unit
to convert the loop number to a location. that has slots owned by partitions. Replug the cables
before taking any other actions. If you had intended
To determine the problem, find the PRC in the list to perform a 12X I/O expansion unit remove, follow
below. the proper procedure.
Note: The FRU description in the serviceable event v xxxx 321D indicates that a 12X I/O expansion unit
view may already contain a message that identifies the add was not successful because previous 12X I/O
problem. expansion unit adds have resulted in reaching a
v xxxx 0000 indicates bus numbers were not assigned. resource limit, and no I/O expansion units can be
Contact your next level of support. added to this loop until after a platform IPL. The
loop is currently not complete. To return the loop to
v xxxx 0008 indicates the system serial number is not
the previous configuration, remove the 12X I/O
set. Set the serial number on the system unit. If the
expansion unit.
problem persists contact your next level of support.
v xxxx 321F indicates an invalid 12X I/O expansion
v xxxx 029A indicates an unsupported I/O expansion
unit replace was detected. This may occur if
unit hardware level. Upgrade the expansion unit
attempting to remove an I/O expansion unit on a
hardware to a supported level.
loop with other failed I/O expansion units. A remove
v xxxx 0454 indicates incompatible I/O expansion unit action is not supported when there are other failures
types have been detected on the same loop. To on the loop. If the loop is complete, it may have
correct the problem, remove the recently recovered. Verify the loop configuration is as
added/configured expansion unit from the loop. expected.
v xxxx 3201 indicates there are HSL OptiConnect
clustered systems on both RIO or HSL loops on the If the problem still exists, contact your next level of
same adapter. You will need to ensure that only one support.
RIO or HSL loop per adapter is used for HSL
OptiConnect. This ends the procedure.
v xxxx 3211 indicates two or more HSL adapters are
Failing Item:
connected to each other on the same system unit.
This is not a supported configuration. Re-cable the v SVCDOCS
system so that it has a supported configuration.
638 System reference codes (Bxxx)
B7006984 • B7006990
v PWRCBL
B7006984 B7006984
Explanation: System log entry only, no service action
B7006987 B7006987
required
Explanation: RIO, HSL or 12X connection failure
Response: A RIO, HSL or 12X loop has switched to its
alternate path. This is an informational SRC only. Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
If word 2 of the SRC contains "00000062", then word 7
documented here to determine the parts to exchange.
contains the loop number in the leftmost 4 digits. The
loop number is in hexadecimal format. You must If the Serviceable Event View is not available then use
convert the hexadecimal loop number into decimal the failing item list presented here for servicing this
format to recognize the loop number. reference code.
If word 2 of the SRC contains "00000072", then word 7 Failing Item:
contains the DRC index of the hub reporting the error. v HSL_LNK
This SRC can be caused by a tower on the RIO, HSL or v OPT_CLN
12X loop powering off.
This SRC may also appear in a Serviceable Event View B7006988 B7006988
you are using, with a B700 6982 or B700 6981 logged at
approximately the same time. In that case the other Explanation: An unrecoverable memory error caused
SRC is reporting a failure and this SRC is reporting that a tower failure.
the alternate RIO, HSL or 12X path is now being used. Response: Look for any B12xE500 SRCs which require
Service the other SRC if present. service action, and perform the actions indicated to
resolve the memory failure.
B7006985 B7006985 After completing those actions, you will need to power
Explanation: RIO, HSL or 12X loop status message the failing tower off/on to recover.
Response: This is a serviceable event only if this error Failing Item:
is in a serviceable event view. If this is a serviceable v SVCDOCS
event then perform RIOIP12. Otherwise if this is NOT a
serviceable event then to determine what this SRC
B7006989 B7006989
means use symbolic FRU SIRSTAT.
Explanation: I/O expansion drawer cables are
Work with the FRU list in the serviceable event view if
incorrectly connected.
there is one, otherwise use the FRU list documented
here to determine the parts to exchange. Response: Service should determine the 12X cable
configuration at the system connectors that existed
NOTE: A fiber optic cleaning kit may be required for
prior to the repair action and return the cables to the
optical RIO or HSL connections.
original position. System firmware will detect when the
Failing Item: cables have been returned to the proper position and
v SVCDOCS restart the affected I/O drawers. The location code of
the I/O hub is identified in the error log.
v HSL_LNK
v OPT_CLN Failing Item:
v FRPORT v SVCDOCS
v TOPORT
B7006990 B7006990
B7006986 B7006986 Explanation: Service processor failure
Explanation: System bus error Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
Response: Work with the FRU list in the serviceable documented here to determine the parts to exchange.
event view if there is one, otherwise use the FRU list
documented here to determine the parts to exchange. If the Serviceable Event View is not available then use
the failing item list presented here for servicing this
If the Serviceable Event View is not available then use reference code.
the failing item list presented here for servicing this
reference code. Failing Item:
Failing Item: v PSI_LNK
v TWRCARD
(B7xx) Reference codes 639
B7006991 • B70069C6
B7006991 B7006991 B70069C3 B70069C3
Explanation: Platform LIC failure Explanation: HSL OptiConnect disconnected normally
from a remote node. System log entry only, no service
Response: Work with the FRU list in the serviceable
action required.
event view if there is one, otherwise use the FRU list
documented here to determine the parts to exchange.
B70069C6 B70069C6
Failing Item:
v LICCODE Explanation: Platform LIC detected an error
Response: Abnormal or unexpected HSL OptiConnect
B7006993 B7006993 disconnection from a remote system or partition.
Explanation: Service processor failure The local system or partition disconnected from a
remote system or partition due to an unexpected event
Response: Work with the FRU list in the serviceable or failure. The problem, which most likely originates
event view if there is one, otherwise use the FRU list with the remote system or partition, probably requires
documented here to determine the parts to exchange. intervention at the remote system. Examine both the
Failing Item: local and remote HSL OptiConnected systems or
partitions for problems on this RIO or HSL loop.
v SVCPROC
v LICCODE Possible reasons include: A fatal software or hardware
error in the remote system or partition, or a power
failure in the remote system.
B7006994 B7006994
If a complete RIO or HSL loop did not exist before this
Explanation: Service processor failure error occurred, the cause of this error might be a failure
or power down in a RIO or HSL component between
Response: Work with the FRU list in the serviceable
the local system or partition and the remote system or
event view if there is one, otherwise use the FRU list
partition. Check for a problem with the following:
documented here to determine the parts to exchange.
v A RIO or HSL cable
If the Serviceable Event View is not available then use
v The RIO or HSL I/O bridge
the failing item list presented here for servicing this
reference code. v Power in an expansion I/O tower or unit on this
loop
Failing Item:
v SVCPROC On the local system or partition, examine the Service
Action Log (SAL) or serviceable event view. Look for
RIO or HSL failures that occurred on the same RIO or
B7006995 B7006995
HSL loop at approximately the same time as this error.
Explanation: User intervention required
Examine the remote system or partition for problems. If
Response: The system is in the process of terminating.
the remote system or partition is powered on and
When all the partitions have terminated, an SRC IPL'd, examine the SAL or serviceable event view on
indicating the exact cause will be shown on the the remote system or partition. Look for problems on
operator panel. the same RIO or HSL loop that occurred at
approximately the same time as this error.
If the system does not terminate in a reasonable
amount of time, one or more partitions may need to be
Correct any problems you find with the remote and
terminated manually. If this is not possible, re-IPL the
local systems or partitions that happened at
system and look for errors. If no errors are found,
approximately the same time and involve HSL
contact your next level of support.
Opticonnect or RIO or HSL loop components.
B70069C2 B70069C2 When the remote system is IPL'd, it will automatically
reconnect with this system or partition. If you find no
Explanation: HSL OptiConnect established a normal
problems with either the local or the remote systems or
connection to another system or partition. System log
partitions, collect all the Product Activity Log (PAL)
entry only, no service action required.
information for this failure on both systems. Be sure to
record all words in the SRC. Contact your next level of
support.
Failing Item:
v SVCDOCS
640 System reference codes (Bxxx)
B70069C7 • B70069C9
v LICCODE v Network deadlock detected
The problem may be with:
B70069C7 B70069C7
v The local system or partition
Explanation: Platform LIC detected an error
v The remote system or partition
Response: Abnormal or unexpected HSL OptiConnect
disconnection from a remote system or partition. On the local system or partition, examine the SAL or
serviceable event view. Look for RIO or HSL failures on
The local system or partition disconnected from a
the same RIO or HSL loop or with the RIO or HSL
remote system or partition due to an unexpected event
controller that occurred at approximately the same time
or failure. Licensed Internal Code will attempt to
as this error.
recover from the error. Intervention at the local or
remote system or partition might be required.
Examine the remote system or partition for problems.
Possible causes include time out, hang, or hardware On the remote system or partition, examine the SAL or
failure. The problem may be with the local system or serviceable event view. Look for problems on the same
partition or the remote system or partition. If a RIO or HSL loop or with the RIO or HSL controller that
complete RIO or HSL loop did not exist before this occurred at approximately the same time as this error.
error occurred, the cause of this error might be a failure
or power down in a RIO or HSL component between Correct any problems you find with the remote and
the local system or partition and the remote system or local systems or partitions that happened at
partition. Check for SRCs with FRUs that indicate approximately the same time and involve HSL
problems with the following: Opticonnect or RIO or HSL loop components.
v RIO or HSL cables
v The RIO or HSL I/O bridge If there are no problems with the remote system or
partition and there are no problems with the local
v Power in an expansion I/O tower or unit on this
system or partition then collect all the Product Activity
loop
Log information for this failure on all systems or
partitions. Be sure to record all words in the SRCs.
On the local system or partition, examine the SAL or Contact your next level of support.
serviceable event view. Look for failures on the same
loop or with the RIO or HSL controller that occurred at Failing Item:
approximately the same time as this error. v SVCDOCS
v LICCODE
Examine the remote system or partition for problems.
Correct any RIO or HSL controller problems you find
with the remote and local systems or partitions. If you B70069C9 B70069C9
find no problems with either the local or the remote
Explanation: Platform LIC detected an error
systems or partitions, collect all the PAL information
for this failure on both systems. Be sure to record all Response: Abnormal or unexpected HSL OptiConnect
words in the SRC. Contact your next level of support. disconnection from a remote system or partition.
Failing Item: The local system or partition disconnected from a
v SVCDOCS remote system or partition due to an failure in a
Licensed Internal Code virtualized bus unit. Licensed
v LICCODE
Internal Code will attempt to recover from the error.
Possible causes are:
B70069C8 B70069C8 v Licensed Internal Code problem where the local bus
Explanation: Platform LIC detected an error unit is offline.
v Licensed Internal Code problem where the remote
Response: Abnormal or unexpected HSL OptiConnect bus unit is offline.
disconnection from a remote system or partition.
The local system or partition disconnected from a On the local system or partition, examine the SAL or
remote system or partition due to an unexpected event the serviceable event view. Look for HSL Opticonnect
or failure. All of the HSL OptiConnect connections on failures that occurred at approximately the same time
this loop will be in a failed state. Licensed Internal as this error.
Code will attempt to recover from the error.
Intervention at the local or remote system or partition Examine the remote system or partition for problems.
might be required. Possible causes are: On the remote system or partition, examine the SAL or
v Time out of a critical message
v Licensed Internal Code code / table problem
(B7xx) Reference codes 641
B70069CF • B70069E3
the serviceable event view. Look for HSL Opticonnect v HSL_IB
problems that occurred at approximately the same time v FRPORT
as this error.
v TOPORT
Collect all the Product Activity Log information for this
failure on all systems and partitions on this RIO or B70069D9 B70069D9
HSL loop. Be sure to record all words in the SRCs.
Explanation: Host Ethernet Adapter (HEA) failure
Contact your next level of support.
Response: Firmware detected a hardware failure in
Failing Item:
the Host Ethernet Adapter (HEA).
v SVCDOCS
Failing Item:
v LICCODE
v HEA
B70069CF B70069CF
B70069DA B70069DA
Explanation: Platform LIC detected an error
Explanation: A non-terminating Host Ethernet
Response: Abnormal or unexpected HSL OptiConnect Adapter error was detected. System log entry only, no
disconnection from a remote system or partition. service action required
Licensed Internal Code internal error. All systems
participating in HSL OptiConnect will be disconnected. B70069DB B70069DB
You must re-IPL the system to recover. Before re-IPL'ing
the system, start a platform dump. Explanation: Platform LIC failure
On the local system or partition, after getting the Response: A Platform Licensed Internal Code error
dump, examine the SAL or the serviceable event view. occurred. The system will continue to run this Host
Look for HSL Opticonnect failures that occurred at Ethernet Adapter (HEA) disabled. Perform a platform
approximately the same time as this error. dump and then IPL the system to recover the HEA.
Send the platform dump to your next level of support.
Examine the remote systems or partitions for problems.
On the remote systems or partitions, examine the SAL Failing Item:
or the serviceable event view. Look for HSL v SVCDOCS
Opticonnect problems that occurred at approximately
the same time as this error.
B70069E1 B70069E1
Collect all the PAL information for this failure on all
systems and partitions on this RIO or HSL loop. Be Explanation: Host Channel Adapter (HCA) failure
sure to record all words in the SRCs. Contact your next Response: The 12X Host Channel Adapter has failed.
level of support.
Failing Item:
Failing Item:
v HCA
v SVCDOCS
v LICCODE
B70069E2 B70069E2
Explanation: Platform LIC failure
B70069D2 B70069D2
Response: A Platform Licensed Internal Code error
Explanation: The 12X link is noisy, and has hit a
occurred related to 12X technology. The system will
threshold on bad packets.
continue to run with this Host Channel Adapter
Response: If SRC B7006982 is in the serviceable event disabled. Perform a platform dump prior to IPLing the
view, perform the actions listed for that SRC. If system. An IPL is required to recover the Host Channel
B7006982 is not present, work with the SRC B70069D2 Adapter.
FRU list in the serviceable event view. For an Internal
Failing Item:
link failure, the I/O backplane (TWRBKPL) is the
probable cause. For an External link failure, the v LICCODE
probable FRUs are listed below.
Problem determination: For External links, unplug B70069E3 B70069E3
and replug the 12X cable to see if the problem corrects Explanation: System log entry only, no service action
itself. required
Failing Item: Response: Part of the HCA chip failed but was not
v SVCDOCS
642 System reference codes (Bxxx)
B70069E4 • B70069F1
terminating. When thresholded, these errors will result
B70069EB B70069EB
in a B70069E1.
Explanation: User intervention required
B70069E4 B70069E4 Response: A 12X configuration error was detected by
the HCA. Verify that the 12X configuration is correct at
Explanation: An invalid 12X configuration was
the HCA. The Port 1 and 2 configurations conflict.
detected
Failing Item:
Response: An error was detected in the 12X fabric.
Have the customer check for problems reported at the v SVCDOCS
IBM Network Manager. This includes cases such as
path migration, etc. B70069EC B70069EC
Failing Item: Explanation: User intervention required
v SVCDOCS
Response: A 12X adapter in the server does not
support connections to I/O enclosures.
B70069E5 B70069E5
Upgrade the adapter at the location given in the
Explanation: System log entry only, no service action serviceable event view to a new version. Contact
required support for assistance.
Response: A 12X communications error occurred. Failing Item:
Unrecognized command from Subnet Manager. Does v SVCDOCS
not require service.
B70069ED B70069ED
B70069E6 B70069E6
Explanation: RIO or 12X link is not operating at
Explanation: System log entry only, no service action optimal bandwidth
required
Response: An RIO 12X cable connection initialized to
Response: The cable connection to the 12X switch is a lower signal frequency. The link is operational but
broken. Verify that the cable is connected and the operating at a bandwidth below its rated capacity. This
switch is powered on. After repairing the problem, may lead to degraded I/O throughput.
verify that the connection has been restored by using
the IBM Network Manager. Does not require service. Perform the RIOIP56.
Work with the FRU list in the serviceable event view if
B70069E7 B70069E7 there is one, otherwise use the FRU list documented
here to determine the parts to exchange.
Explanation: System log entry only, no service action
required Failing Item:
v SVCDOCS
Response: The cable connection to the 12X switch has
been restored. No service action required. v HSL_IB
v FRPORT
B70069E9 B70069E9 v TOPORT
Explanation: System log entry only, no service action
required B70069EE B70069EE
Response: Initial communication has occurred with Explanation: I/O unit backplane is not operating at
the Subnet Manager. No service action required. The optimal bandwidth
CEC and switch firmware are now communicating. Response: Replace the I/O unit backplane at your
next scheduled maintenance.
B70069EA B70069EA Failing Item:
Explanation: System log entry only, no service action v TWRBKPL
required
Response: Subnet Manager connection is established. B70069F1 B70069F1
No service action required.
Explanation: I/O Controller had a permanent
unrecoverable failure.
This is a permanent HW failure of the Hub chip. The
(B7xx) Reference codes 643
B70069F2 • B70069F4
Location Code in the error log is the FRU that should downstream IO affected by this failure.
be replaced.
All downstream IO may have failed (EEH errors logged
All downstream IO is failed as a side-effect of this around time of I/O Controller failure). Use the I/O
failure. Any and all of these downstream failures Controller Location Code to determine the downstream
should be ignored and removed from the error log. Use IO affected by this failure. If there are errors logged for
the I/O Controller Location Code and procedure any of the downstream IO adapters or Bus Adapters,
MABIP57 to determine the downstream IO affected by close the errors.
this failure.
Response: Service should correlate this failure with all
Response: Collect Error Logs and Info Logs. Replace the EEH failures associated with it. From the Controller
the I/O Controller in the FRU list and send the failed identified, determine what IO backplanes or IB
FRU in for fault analysis with the error log data. Clear Switches (HCA configuration) are connected. For each
the error log of any IOA or Bus Adapters failures that IO backplane and all IOAs which are in failed states,
are downstream of the I/O controller. determine to which partitions the IOAs belong, The
partition/application may need to be restarted to
Failing Item:
recovery if it can run without the failed IOA(s). No
v SVCDOCS service action should be taked against the IOAs. The
v SICNTRL hub FRU should be replaced. Collect the error logs and
info logs around the time of failure and the IO
configuration.
B70069F2 B70069F2
Problem determination: Call next level of support.
Explanation: I/O Controller had a temporary failure
which has been recovered. Do not replace any FRUs. Failing Item:
Some or all downstream IO may have failed and loged v SVCDOCS
EEH errors logged around time of I/O Controller v SICNTRL
failure. In most cases, the recovery should complete
without any impact to IO. This error is logged as a
B70069F4 B70069F4
Serviceable Event to help correlate it with the EEH
errors, if they happen to get logged. Use the I/O Explanation: I/O Controller Failure, Controller not
Controller Location Code and procedure MABIP57 to responding or not reachable. All IO downstream of this
determine the downstream IO affected by this failure. Controller will be in a failed state. If there are any
Check to see if all the downstream I/O Adapters errors logged for those I/O Adapters, they should be
recovered. If there are I/O Adapters in a failed state, closed. Use the I/O Controller Location Code and
the partition to which the failed I/O adapter is procedure MABIP57 to determine the downstream IO
connected/owned may need to be re-IPLed to complete affected by this failure.
recovery. If there are errors logged for any of the
The I/O Controller is not responding. Look in the
downstream adapters or Bus Adapters, close the errors.
Serviceable Event View for B130E5xx SRCs logged at
Response: Service should correlate this recovered/self about the same time. If you find any, then close the
healed action with any possible EEH failures. From the B70069F4 SRC, and work to resolve the B130E5xx SRC.
Controller identified, determine what IO backplanes or
Response: Look in the Serviceable Event View for
IB Switches (HCA configuration) are connected. For
B130E5xx SRCs logged at about the same time. If you
each IO backplane, determine if any IOAs are in failed
find any, then close the B70069F4 SRC, and work to
states and to which partitions they belong. The
resolve the B130E5xx SRC. Otherwise, proceed as
partition may need to be restarted to complete the
indicated below.
recovery of a failed IOA. There may be no EEH errors,
in which case this error can be ignored. If there are errors logged against I/O Adapters on this
loop, do not replace any I/O Adapter hardware.
Failing Item:
v SVCDOCS Collect the loop configuration of the system. Then work
with your service provider to collect error logs. Work
with the FRU list in the Serviceable Event View if there
B70069F3 B70069F3 is one. Otherwise, use the FRU list documented here to
Explanation: I/O Controller failed. determine the parts to exchange.
The I/O Controller received repeated recoverable Failing Item:
failures (see B70069F2) in a short period of time v SVCDOCS
reaching a threshold limit, thus turning it into a v SICNTRL
Serviceable Event. The I/O Controller in the FRU list
should be replaced. Use the I/O Controller Location
Code and procedure MABIP57 to determine the
644 System reference codes (Bxxx)
B70069F5 • B7006A01
restart affected applications. Collect error logs which
B70069F5 B70069F5
occurred around the same time as this SRC, as well as
Explanation: I/O Controller failure the I/O configuration, and send to IBM.
I/O Controller (GX++ adapter) detected an invalid Failing Item:
firmware action, all downstream IO is failed. Possibly v SIADPCD
corrupted code. So either code has been/is corrupted or
is corrupted on the way to the HW or HW is
incorrectly diagnosing the problem. B70069FD B70069FD
All downstream IO is failed as a side-effect of this Explanation: 12X I/O Bridge failure
failure. Any and all of these downstream failures Response: If there are any Power Problems (SRC
should be ignored and removed from the error log. Use 1xxxxxxx) in the serviceable event view, perform the
the I/O Controller Location Code and procedure actions indicated. Otherwise, collect error logs and all
MABIP57 to determine the downstream IO affected by configuration data associated with the failing 12X I/O
this failure. Bridge adapter, including I/O backplanes and I/O
Response: The I/O Controller detected a failure. All adapters associated with the loop. Look for power
I/O Adapters connected to this controller will be in a faults for the related drawer/backplane. and check 12X
failed state. cables and power cables for good connections. If the
problem persists, contact your next level of support.
If there are errors logged against I/O Adapters
downstream of this Controller, do not replace any IO Failing Item:
Adapter hardware. This SRC is the root cause. v SVCDOCS
Work with your service provider to collect Error logs,
Info logs, platform dump. Then, check for and load B70069FE B70069FE
latest service pack. If that doesn't solve the problem,
replace I/O Controller FRU. Explanation: 12X I/O Bridge failure
Problem determination: N/A. Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
Failing Item: documented here to determine the parts to exchange. If
v SVCDOCS this does not resolve the problem, collect error logs,
work with the customer to collect a platform dump,
v SICNTRL
and check for firmware service pack updates.
v LICCODE
Failing Item:
v SIADPCD
B70069FA B70069FA
v LICCODE
Explanation: Unrecoverable 12X I/O Bridge failure.
Response: Collect error logs and info logs. Replace the B7006A00 B7006A00
12X I/O Bridge FRU in the I/O enclosure, and send the
failed FRU with the error log data to IBM for fault Explanation: P7-IH Hub (Power Bus Attachment) had
analysis. a permanent unrecoverable chip failure. All coherent
and non-coherent cluster traffic via the Host Fabric
Failing Item: Interface (HFI) as well as all PCIe traffic through this
v SIADPCD P7-IH Hub is disabled.
Failing Item:
B70069FB B70069FB v IH_HUB
Explanation: 12X I/O Bridge recovered; Do NOT
replace any FRUs. B7006A01 B7006A01
Explanation: P7-IH Hub Collectives Acceleration Unit
B70069FC B70069FC (CAU) had a catastrophic unrecoverable error. The
Explanation: 12X I/O Bridge recovery failure CAU is disabled and the P7-IH Hub can continue to
function with the exception of the performance
Response: The 12X I/O Bridge FRU should be enhancing collectives accelerator. PCIe traffic through
replaced. I/O slots associated with the 12X I/O Bridge this P7-IH Hub is unaffected.
FRU may have been affected, causing I/O adapters to
be in a failed state. No service action should be taken Failing Item:
against the I/O adapters, but partitions which were v IH_HUB
using these failed I/O adapters may require actions to
(B7xx) Reference codes 645
B7006A02 • B7006A24
Failing Item:
B7006A02 B7006A02
v SVCDOCS
Explanation: P7-IH Hub Nest Memory Management
Unit (NMMU) had a catastrophic unrecoverable error.
The NMMU is disabled thereby providing no further B7006A21 B7006A21
address translation capability for the HFI units. This Explanation: PCI-E Switch had a permanent
prevents non-coherent cluster traffic from flowing unrecoverable (internal) chip failure. All downstream
to/from the Integrated Switch Router (ISR) using I/O is failed.
HFI0/HFI1 window resources. P7-IH Hub can continue
to service coherent Power Bus traffic from octant to Response: Collect error logs and info logs. Replace the
octant, non-coherent traffic from the ISR to other PCI-E Switch FRU, and send the failed FRU with the
octants, as well as provide PCIe I/O Hub functionality error log data to IBM for fault analysis.
as an independent entity.
Failing Item:
Failing Item: v PCIE_SW
v IH_HUB
B7006A22 B7006A22
B7006A03 B7006A03
Explanation: PCI-E Switch had a recoverable failure;
Explanation: P7-IH Hub Host Fabric Interface 0 (HFI however, all downstream I/O had to be failed during
0) had a catastrophic unrecoverable error. The HFI 0 is recovery. Recovery for the PCI-E Switch failure is being
disabled thereby preventing any further non-coherent attempted. If the recovery is successful, no other SRC is
cluster traffic to/from the Integrated Switch Router logged.
(ISR) using HFI0 window resources. The loss of HFI0
Response: Once the PCI-E switch is recovered, the
disables the Collectives Acceleration Unit for this P7-IH
downstream I/O adapters should recover. The
Hub chip independent of HFI0 or HFI1 resources. The
partition/application associated with the failed
loss of HFI0 also disables broadcast support for this
downstream I/O may have to be restarted.
P7-IH Hub. This P7-IH Hub can continue to provide
coherent Power Bus traffic from octant to octant over Failing Item:
the power bus, non-coherent traffic using HFI1 v SVCDOCS
resources to/from the ISR, non-coherent traffic from the
ISR to other octants, as well as PCIe I/O Hub
functionality as an independent entity. B7006A23 B7006A23
Failing Item: Explanation: PCI-E Switch recovery failure. All
downstream I/O is failed.
v IH_HUB
Response: Exhaustive attempts to recover the PCI-E
Switch failed.
B7006A04 B7006A04
If there are AIX/LINUX errors logged against I/O
Explanation: P7-IH Hub Host Fabric Interface 1 (HFI
Adapters on this switch, do not replace any I/O
1) had a catastrophic unrecoverable error. The HFI1 is
Adapter hardware. This SRC is the root cause.
disabled thereby preventing any further non-coherent
cluster traffic to/from the Integrated Switch Router Work with your service provider to collect error logs.
(ISR) using HFI1 window resources. This P7-IH Hub Then work with the FRU list in the Serviceable Event
can continue to provide coherent HFI traffic from View if there is one; otherwise, use the FRU list
octant to octant over the power bus, non-coherent documented here to determine the parts to exchange.
traffic using HFI0 resources to/from the ISR, After the FRU has been replaced, the
non-coherent traffic from the ISR to other octants, as partition/application associated with the failed
well as PCIe I/O Hub functionality as an independent downstream I/O may have to be restarted.
entity.
Failing Item:
Failing Item: v PCIE_SW
v IH_HUB
B7006A24 B7006A24
B7006A20 B7006A20
Explanation: PCI-E Switch failure. All downstream
Explanation: Invalid/Unsupported Hardware I/O is failed.
configuration detected
Response: Collect error logs, informational logs, and
Response: Determine the unsupported HW configuration data associated with I/O adapters below
configuration. the PCI-E Switch. Replace the PCI-E Switch FRU, and
646 System reference codes (Bxxx)
B7006A25 • B7006A72
send the failed FRU along with the collected data to v PCIEBUS
IBM for fault analysis. v PIOCARD
Failing Item:
v PCIE_SW B7006A30 B7006A30
Explanation: This reference code indicates that a
B7006A25 B7006A25 PCI-E bus internal connection initialized to a lower bus
configuration than expected. The bus is operational but
Explanation: PCI-E Switch has detected an invalid
operating at a bandwidth below its rated capacity. This
firmware action. All downstream I/O is failed.
may lead to degraded I/O throughput.
Response: Collect Error Logs and Info Logs. Check for
Response: If this event appears in a serviceable event
firmware updates in the latest service pack. Otherwise,
view, work with the failing item list found there. If this
replace the PCI-E Switch FRU, and send the failed FRU
event does not appear in a serviceable event view, no
along with the collected data to IBM for fault analysis.
service action is required.
Failing Item:
Failing Item:
v LICCODE
v PCIEBUS
v PCIE_SW
B7006A70 B7006A70
B7006A28 B7006A28
Explanation: The PCI-E Primary Host Bus has
Explanation: PCI-E Switch had a correctable error, detected a failure.
Downstream IO is unaffected.
Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
B7006A2A B7006A2A documented here to determine the parts to exchange.
Explanation: PCI-E Switch downstream I/O bus had a Failing Item:
recoverable failure. A downstream I/O Adapter may be
v PCIEHB1
failed.
Response: Check the Serviceable Event view for other
B7006A71 B7006A71
SRCs logged at approximately the same time as this
SRC, and perform the actions indicated for those SRCs. Explanation: The failure is related to a PCI Express
(PCIe) connected drawer/enclosure.
If no other SRC was logged, then the PCI-E Switch
recovery was successful. Response: Work with the FRU list in the serviceable
event view if there is one, otherwise use the FRU list
In either case, determine if any downstream I/O
documented here to determine the parts to exchange.
Adapters are in failed states and to which partitions
they belong. The partition/application associated with Failing Item:
the failed downstream I/O may have to be restarted. v MABIP56
Failing Item: v PCIEAD1
v SVCDOCS v ADJ_PHY
v PCIEHB1
B7006A2B B7006A2B v PCIECB1
Explanation: PCI-E Switch downstream bus had
recoverable failure, but has reached the threshold of B7006A72 B7006A72
recovery attempts. The Downstream I/O Adapter is
Explanation: IO downstream from a PCI Host Bridge
failed.
(PHB) has been experiencing recoverable errors in a
Response: Collect error logs, informational logs, and volume which exceeds an expected threshold.
configuration data associated with I/O Adapters below
Response: No immediate action is necessary. There are
the PCI-E Switch. Work with the FRU list in the
two repair actions recommended prior to replacing
Serviceable Event View if there is one, otherwise, use
hardware identified by the FRU list. At the earliest
the FRU list documented here to determine the parts to
convenient time or service window complete the
exchange. After the FRU has been replaced, the
following actions. If performing these repair actions
partition/application associated with the failed
resolves the problem, there is no need to consider the
downstream I/O may have to be restarted.
additional FRUs in the FRU list. If the same SRC is
Failing Item: logged again as a serviceable event identifying the
same location code after these repair actions have been
(B7xx) Reference codes 647
B7006A73 • B700BAD1
completed, continue to the additional FRUs in the FRU
B7009900 B7009900
list.
Explanation: (N/A for external service docs)
If you have recently completed the first of these actions
for the failing FRU, continue to the second action. If
you have recently completed both of these actions for B7009901 B7009901
the failing FRU, continue to the next item in the FRU
Explanation: (N/A for external service docs)
list.
1. Reseat the IO adapter(s) at the location provided for
B7009902 B7009902
the failing FRU.
Explanation: (N/A for external service docs)
This will require a system power down for FRUs which
are not hot-pluggable PCI adapters.
B7009904 B7009904
If there is no location information provided, continue to
the FRU list. Explanation: (N/A for external service docs)
If the location provided is for a single embedded or
PCI adapter location, reseat the adapter at that location. B7009905 B7009905
If the location provided is for a FRU with multiple Explanation: (N/A for external service docs)
adapters plugged into it, such as an IO backplane,
reseat each of the adapters plugged into the FRU at the
location code provided. B7009906 B7009906
2. Update the firmware on the adapter. Explanation: (N/A for external service docs)
If the location provided is for a single embedded or
PCI adapter location, check for adapter firmware B7009907 B7009907
updates. Apply the update if one is available. Explanation: (N/A for external service docs)
If the location provided is for a FRU with multiple
adapters plugged into it, check for adapter firmware B700990F B700990F
updates for each of the adapters plugged into the FRU
at the location code provided. Apply the updates if any Explanation: (N/A for external service docs)
are available.
Failing Item: B7009999 B7009999
v SVCDOCS Explanation: (N/A for external service docs)
v PIOCARD
v MA_BRDG B70099FF B70099FF
Explanation: (N/A for external service docs)
B7006A73 B7006A73
Explanation: IO downstream from a PCI-E Host B700BA01 B700BA01
Bridge (PHB) cable-connected adapter has been
Explanation: During analysis of a previous serviceable
experiencing recoverable errors in a volume which
error, a request to activate a FRU Fault indicator was
exceeds an expected threshold. No immediate action is
not successful.
necessary. At the earliest convenient service window,
repair the FRUs in the FRU list. Response: Look in the serviceable event view to
determine the location of the FRU associated with the
Response: At the earliest convenient service window,
FRU Fault Indicator activate failure. If the problem
work with the FRU list in the serviceable event view if
persists after the FRU has been replaced, contact your
there is one, otherwise use the FRU list documented
next level of support.
here to determine the parts to exchange.
Failing Item:
Failing Item:
v SVCDOCS
v PCIERE1
v PCIEFW1
B700BAD1 B700BAD1
v PCIEAD1
v ADJ_PHY Explanation: Platform firmware detected an error
v PCIEHB1 Response: Platform firmware detected unexpected or
v PCIECB1 not valid data returned from non-platform firmware.
648 System reference codes (Bxxx)
B700BAD2 • B700F10A
Contact your next level of support. Failing Item:
Failing Item: v SVCDOCS
v NEXTLVL
B700F105 B700F105
B700BAD2 B700BAD2 Explanation: Platform LIC detected an error
Explanation: Platform firmware detected a condition Response: The platform LIC detected an internal
which may impact error reporting to a partition. problem.
Response: Collect the error logs and contact your next Collect all the SRC words and the platform system
level of support. dump, then contact your next level of support.
Failing Item: Failing Item:
v NEXTLVL v NEXTLVL
B700BAFD B700BAFD B700F106 B700F106
Explanation: Task flight recorder data logged prior to Explanation: Platform LIC detected an error
wrapping. No service action is required.
Response: The system will terminate.
Collect all the SRC words and then contact your next
B700F103 B700F103
level of support.
Explanation: Platform LIC failure
Failing Item:
Response: Work with the FRU list on the serviceable v ANYPROC
event view if there is one, otherwise, use the FRU list
v NEXTLVL
documented here to determine the parts to exchange.
The platform LIC detected an internal problem.
B700F107 B700F107
Collect all the SRC words and the platform system
Explanation: Dynamic replacement of checkstopped
dump, then contact your next level of support.
processor failed.
Failing Item:
Response: Collect all the SRC words and then contact
v LICCODE your next level of support.
Failing Item:
B700F104 B700F104
v NEXTLVL
Explanation: Operating System error
Response: Platform Licensed Internal Code terminated B700F108 B700F108
a partition.
Explanation: A firmware error caused the system to
If SRC word 3 is 0018, then a user may have initiated a terminate.
function 22 prior to the operating system completing
Response: Collect all the SRC words and the platform
the IPL. If a function 22 was not performed, or if SRC
system dump, and then contact your next level of
word 3 is not 0018, look for other serviceable errors
support.
which occurred at same time frame.
Problem determination: Perform a platform dump.
If SRC word 3 is 0017, it means that during partition
mobility an unrecoverable error occured after the Failing Item:
partition had resumed on the target system. Close this v SVCDOCS
problem and look for other serviceable errors that
occured around the same time. Perform any actions v NEXTLVL
indicated to resolve those errors.
If SRC word 3 is 0007 or 0009, then the failing partition B700F10A B700F10A
received a Machine Check without having a Machine Explanation: Platform LIC detected an error
Check handler enabled. This could be due to the
Machine Check occurring while the partition was in an Response: Look for errors with SRCs of the form B1xx
IPL. If an IPL was not in progress, or word 3 is xxxx in the Serviceable Event View. Work those errors
different, look for other serviceable errors which first. If that does not correct the problem, collect all the
occurred at approximately the same time, and contact SRC words and the platform system dump, then
your next level of support. contact your next level of support.
(B7xx) Reference codes 649
B700F10B • B700F130
Failing Item:
v SVCDOCS
B700F10B B700F10B
Explanation: A resource has been disabled due to
hardware problems
Response: The platform detected a problem with a
processor. The processor is not functional.
Work with the FRU list in the serviceable event view if
there is one, otherwise contact your next level of
support.
Failing Item:
v SVCDOCS
B700F10C B700F10C
Explanation: The platform LIC detected an internal
problem performing Partition Mobility
Response: Collect all the SRC words and the platform
system dump, then contact your next level of support.
Failing Item:
v NEXTLVL
B700F120 B700F120
Explanation: Platform firmware detected an error
Response: The platform is unable to support the
requested architecture options requested by the
operating system via ibm,client-architecture-support
interface.
B700F130 B700F130
Explanation: Thermal Power Management Device
firmware error was detected.
Response: Check for server firmware updates and
install them, if available. If that does not resolve the
problem, contact your next level of support.
Problem determination:
Failing Item:
v LICCODE
650 System reference codes (Bxxx)
(B9xx) Reference codes
A B9xx reference code indicates that an event or error was detected and logged by the IBM i operating
system.
B9003000 B9003000 B9003011 B9003011
Explanation: Unexpected exception in QINITT before Explanation: QSYINT2 could not find system object.
ICO exists.
Problem determination: Perform any actions given in
Problem determination: Perform any actions given in the console message associated with this SRC.
the console message associated with this SRC.
B9003012 B9003012
B9003001 B9003001
Explanation: Previously unmarked damage detected.
Explanation: Error in interface to console from
Problem determination: Perform any actions given in
QINITT.
the console message associated with this SRC.
Problem determination: Perform any actions given in
the console message associated with this SRC.
B9003013 B9003013
Explanation: INT1 program not found in QINSTALL
B9003004 B9003004
(after load).
Explanation: Wait time-out on 'console available'
Problem determination: Perform any actions given in
event.
the console message associated with this SRC.
Problem determination: Perform any actions given in
the console message associated with this SRC.
B9003014 B9003014
Explanation: Could not start CPF process.
B9003005 B9003005
Problem determination: Perform any actions given in
Explanation: Error in interface to console from INT1
the console message associated with this SRC.
program.
Problem determination: Perform any actions given in
B9003015 B9003015
the console message associated with this SRC.
Explanation: Terminating error message issued.
B9003007 B9003007 Problem determination: Perform any actions given in
the console message associated with this SRC.
Explanation: Unexpected exception in INT1 program.
Problem determination: Perform any actions given in
B9003016 B9003016
the console message associated with this SRC.
Explanation: Error during link/load of SLIC MRI.
B9003008 B9003008 Problem determination: Perform any actions given in
the console message associated with this SRC.
Explanation: Operator terminated in response to
message.
B9003017 B9003017
Problem determination: Perform any actions given in
the console message associated with this SRC. Explanation: Attempt to display message but ICO
pointer is null.
B9003010 B9003010 Problem determination: Perform any actions given in
the console message associated with this SRC.
Explanation: QSYINT2 could not find required user
profile.
B900308D B900308D
Problem determination: Perform any actions given in
the console message associated with this SRC. Explanation: Recursive invocation of Install Part 1
PDEH.
© Copyright IBM Corp. 2010, 2013 651
B900308F • B9003460
Problem determination: Perform any actions given in
the console message associated with this SRC.
B900308F B900308F
Explanation: Internal failure in install code.
Problem determination: Perform any actions given in
the console message associated with this SRC.
B9003460 B9003460
Explanation: Unexpected exception in INT1 program.
Problem determination: Perform any actions given in
the console message associated with this SRC.
652 System reference codes (Bxxx)
(BAxx) Reference codes
The partition firmware detected a failure.
The first eight characters in the display represent the SRC. Any additional characters represent the
associated location code. Record the location code as well as the reference code, then find the SRC in the
following list.
BA000010 BA000010 BA000034 BA000034
Explanation: The device data structure is corrupted Explanation: The firmware failed to exchange capacity
and allocate lpevents
Problem determination: Reboot the system or
partition. Problem determination: Reboot the system or
partition.
Failing Item:
v FWFLASH Failing Item:
v FWFLASH
BA000020 BA000020
BA000038 BA000038
Explanation: Incompatible firmware levels were found
Explanation: The firmware failed to exchange virtual
Problem determination: Reboot the system or
continuation events
partition.
Problem determination: Reboot the system or
Failing Item:
partition.
v FWFLASH
Failing Item:
v FWFLASH
BA000030 BA000030
Explanation: An lpevent communication failure
BA000040 BA000040
occurred
Explanation: The firmware was unable to obtain the
Problem determination: Reboot the system or
RTAS code lid details
partition.
Problem determination: Reboot the system or
Failing Item:
partition.
v FWFLASH
Failing Item:
v FWFLASH
BA000031 BA000031
Explanation: An lpevent communication failure
BA000050 BA000050
occurred
Explanation: The firmware was unable to load the
Problem determination: Reboot the system or
RTAS code lid
partition.
Problem determination: Reboot the system or
Failing Item:
partition.
v FWFLASH
Failing Item:
v FWFLASH
BA000032 BA000032
Explanation: The firmware failed to register the
BA000060 BA000060
lpevent queues
Explanation: The firmware was unable to obtain the
Problem determination: Reboot the system or
open firmware code lid details
partition.
Problem determination: Reboot the system or
Failing Item:
partition.
v FWFLASH
© Copyright IBM Corp. 2010, 2013 653
BA000070 • BA00E850
Failing Item:
BA000110 BA000110
v FWFLASH
Explanation: The registration of a partition firmware
platform dump failed. If a partition resource dump is
BA000070 BA000070 initaited, it may have incomplete or no data.
Explanation: The firmware was unable to load the Problem determination:
open firmware code lid
v Reboot the system or partition.
Problem determination: Reboot the system or v Look for server firmware updates; apply if available.
partition.
Failing Item: BA00E820 BA00E820
v FWFLASH
Explanation: An lpevent communication failure
occurred.
BA000080 BA000080
Problem determination: Reboot the system or
Explanation: The user did not accept the license partition.
agreement
Failing Item:
Problem determination: There is no further action v FWFLASH
required. If the user did not accept the license
agreement, the system will not function.
BA00E830 BA00E830
BA000081 BA000081 Explanation: Failure when initializing ibm,event-scan
Explanation: Failed to get the firmware license policy Problem determination: Reboot the system or
partition.
Problem determination: Reboot the system or
partition. Failing Item:
v FWFLASH
Failing Item:
v FWFLASH
BA00E840 BA00E840
BA000082 BA000082 Explanation: Failure when initializing PCI hot plug
Explanation: Failed to set the firmware license policy Problem determination: Reboot the system or
partition.
Problem determination: Reboot the system or
partition. Failing Item:
v FWFLASH
Failing Item:
v FWFLASH
BA00E843 BA00E843
BA000091 BA000091 Explanation: Failure when initializing interface to AIX
or Linux
Explanation: Unable to load a firmware code update
lid Problem determination: Reboot the system or
partition.
Problem determination: Reboot the system or
partition. Failing Item:
v FWFLASH
Failing Item:
v FWFLASH
BA00E850 BA00E850
BA000100 BA000100 Explanation: Failure when initializing dynamic
reconfiguration
Explanation: The partition firmware was not actually
updated and a reboot is required to recover. This SRC Problem determination: Reboot the system or
does call home. partition.
Problem determination: Reboot the system or Failing Item:
partition. v FWFLASH
654 System reference codes (Bxxx)
BA00E860 • BA01000D
BA00E860 BA00E860 BA010006 BA010006
Explanation: Failure when initializing sensors Explanation: A keyword was specified that is not
supported by the iSCSI booting extensions.
Problem determination: Reboot the system or
partition. Failing Item:
Failing Item: v FWADIPL
v FWFLASH
BA010007 BA010007
BA010000 BA010000 Explanation: The device does not have the required
device_type property.
Explanation: There is insufficient information to boot
the partition Response: Contact service support.
Failing Item:
v FWIPIPL BA010008 BA010008
Explanation: The device_type property for this device
BA010001 BA010001 is not supported by by the iSCSI booting extensions.
Explanation: The client IP address is already in use by Response: Contact service support.
another network device
Failing Item: BA010009 BA010009
v FWIPIPL Explanation: The arguments specified for the ping
function are invalid.
BA010002 BA010002 Response: Verify that all arguments comply with the
iSCSI initiator configuration specification.
Explanation: One or more of the keywords that was
specified is not supported by this device.
BA01000A BA01000A
Problem determination: Refer to partition firmware
progress codes using code CA00E174. Explanation: The itname parameter string exceeds the
maximum length allowed.
Failing Item:
v FWHOST Response: Verify that all arguments comply with the
iSCSI initiator configuration specification.
BA010003 BA010003
BA01000B BA01000B
Explanation: The specified (or default) discovery
protocols failed to return the parameters that are Explanation: The ichapid parameter string exceeds the
required to boot. maximum length allowed.
Problem determination: Refer to partition firmware Response: Verify that all arguments comply with the
progress codes using code CA00E174. iSCSI initiator configuration specification.
Failing Item:
BA01000C BA01000C
v FWHOST
Explanation: The ichappw parameter string exceeds
the maximum length allowed.
BA010004 BA010004
Response: Verify that all arguments comply with the
Explanation: The IP address specified for the
iSCSI initiator configuration specification.
discovery server was not a valid IPv6 address.
Problem determination: Refer to partition firmware
BA01000D BA01000D
progress codes using code CA00E174.
Explanation: The iname parameter string exceeds the
maximum length allowed.
BA010005 BA010005
Response: Verify that all arguments comply with the
Explanation: The IP address specified for the
iSCSI initiator configuration specification.
discovery server was not a valid IPv4 address.
Problem determination: Refer to partition firmware
progress codes using code CA00E174.
(BAxx) Reference codes 655
BA01000E • BA017021
BA01000E BA01000E BA010020 BA010020
Explanation: The LUN specified is not valid. Explanation: The value of the vlan tag parameter is
not valid.
Response: Verify that all arguments comply with the
iSCSI initiator configuration specification. Problem determination: Verify that the tag complies
with the IEEE 802.1Q specification.
BA01000F BA01000F
BA012010 BA012010
Explanation: The chapid parameter string exceeds the
maximum length allowed. Explanation: Opening the TCP node failed.
Response: Verify that all arguments comply with the Response: Look for server firmware updates; apply if
iSCSI initiator configuration specification. available.
BA010010 BA010010 BA012011 BA012011
Explanation: Partition firmware error during SMS Explanation: TCP failed to read from the network
menus
Response: Look for server firmware updates; apply if
Failing Item: available
v FWFLASH
BA012012 BA012012
BA010011 BA010011 Explanation: TCP failed to write to the network.
Explanation: SET-ROOT-PROP could not find the / Response: Look for server firmware updates; apply if
(root) package available.
Response: Look for server firmware updates; apply if
available. BA012013 BA012013
Explanation: Closing TCP failed.
BA010012 BA010012
Response: Look for server firmware updates; apply if
Explanation: The arguments specified for IP v6 are available.
invalid.
Response: Verify that all arguments comply with the BA012014 BA012014
iSCSI initiator configuration specification, and that the
server addresses are correct. Explanation: The TCP re-transmission count of 8 was
exceeded. This indicates a large number of lost packets
between this client and the boot or installation server.
BA010013 BA010013
Response:
Explanation: The information in the error log entry for
1. Look for problems or errors on the boot or
this SRC provides network trace data.
installation servers. If any are found, correct them.
Problem determination: Informational message: no 2. Look for problems or errors on the network
action is required. switches between the boot or installation server and
this client. If any proble ms are found, correct them.
BA010014 BA010014 3. Try another network adapter on the client.
Explanation: The information in the error log entry for
this SRC provides network trace data. BA017020 BA017020
Problem determination: Informational message: no Explanation: Failed to open the TFTP package
action is required.
Response: Verify that the TFTP parameters are correct.
BA010015 BA010015
BA017021 BA017021
Explanation: The information in the error log entry for
Explanation: Failed to load the TFTP file
this SRC provides network trace data.
Response: Verify the the TFTP server and network
Problem determination: Check for system firmware
connections are correct.
update. Contact your next level support for assistance.
656 System reference codes (Bxxx)
BA01B010 • BA01D052
BA01B010 BA01B010 BA01D030 BA01D030
Explanation: Opening the BOOTP node failed. Explanation: DHCP failed to write to the network
Response: Look for server firmware updates; apply if Response:
available. 1. Verify that the network cable is connected, and that
the network is active.
BA01B011 BA01B011 2. Look for server firmware updates; apply if
available.
Explanation: BOOTP failed to read from the network
Response: Refer to the actions for checkpoint
BA01D040 BA01D040
CA00E174.
Explanation: The DHCP discover server timed out
BA01B012 BA01B012 Response:
Explanation: BOOTP failed to write to the network 1. I nsure that the DHCP server has addresses
available.
Response: Refer to the actions for checkpoint
2. Insure that the DHCP server's configuration file is
CA00E174.
not overly constrained such that it was not able to
meet the configuration requested by the client.
BA01B013 BA01B013 3. Refer to the actions for checkpoint CA00E174.
Explanation: The discover mode is invalid
Response: Look for server firmware updates; apply if BA01D050 BA01D050
available. Explanation: DHCP::discover no good offer
Response: DHCP discover did not receive any DHCP
BA01B014 BA01B014 offers from the server(s) the meet the clients's
Explanation: Closing the BOOTP node failed requirements. Insure that the DHCP server's
configuration file is not overly constrained such that it
Response: Look for server firmware updates; apply if was not able to meet the configuration requested by the
available. client.
BA01B015 BA01B015 BA01D051 BA01D051
Explanation: The BOOTP discover server timed out Explanation: DHCP::discover DHCP request timed out
Response: Refer to the actions for checkpoint Response:
CA00E174. 1. DHCP discover did receive a DHCP offer from the
server(s) the meet the clients's requirements, but the
BA01D001 BA01D001 server did not send DHCP ack (the
acknowledgement) to the client's DHCP request. It
Explanation: Opening the DHCP node failed is possible that another client was using the address
Response: Look for server firmware updates; apply if that was served.
available. 2. Insure that the DHCP server has addresses
available.
BA01D020 BA01D020
BA01D052 BA01D052
Explanation: DHCP failed to read from the network
Explanation: DHCP::discover: 10 incabable servers
Response:
were found
1. Verify that the network cable is connected, and that
the network is active. Response: Ten DHCP servers have sent DHCP offers,
none of which met the requirements on the client.
2. Look for server firmware updates; apply if
Check the configuration that the client is requesting,
available.
and the server's DHCP configuration files, for
compatibility.
(BAxx) Reference codes 657
BA01D053 • BA040035
BA01D053 BA01D053 BA04000F BA04000F
Explanation: DHCP::discover received a reply, but Explanation: Selftest failed on device, no error and/or
without a message type location code information available
Response: Insure that the DHCP server is properly Problem determination: If there was a location code
configured. reported with the error, replace the device specified by
the location code.
BA01D054 BA01D054 Failing Item:
Explanation: DHCP::discover received a reply, but v NEXTLVL
without a message type
Response: BA040010 BA040010
1. DHCP discover did receive a DHCP offer from the Explanation: Self test failed on device; cannot locate
server(s) to meet the clients's requirements, but the package.
server did send DHCP (not acknowledged) to the
Failing Item:
client's DHCP request. (It is possible that another
client was using the address that was served.) This v NEXTLVL
usually occurs when there are multiple DHCP
servers on the same network, and server A does not BA040020 BA040020
know the subnet configuration of server B, and
vice-versa. This can also occur when the pool of Explanation: The machine type and model are not
addresses is not truly divided. The DHCP server's recognized by the server firmware.
configuration file should also be set to
Failing Item:
"authoritative".
v FWFLASH
2. Insure that the DHCP server is functioning properly.
BA040030 BA040030
BA01D055 BA01D055
Explanation: The firmware was not able to build the
Explanation: DHCP::discover: DHCP decline
UID properly for this system. As a result, problems
Response: may occur with the licensing of the AIX operating
1. DHCP discover did receive a DHCP offer from the system.
server(s) to meet the clients's requirements, but the Problem determination:
client performed an ARP test on the address and
1. Using the Advanced System Management Interface
found that another client was using the address.
(ASMI) menus, insure that the machine type, model,
DHCP decline was sent to the server, but no
and serial number in the VPD for this system are
additional DHCP offers were received by the client.
correct.
The client still does not have a valid address.
2. If this is a new system, check for server firmware
2. Insure that the DHCP server is functioning properly.
updates and apply them, if available.
BA01D056 BA01D056
BA040035 BA040035
Explanation: DHCP::discover: unknown DHCP
Explanation: The firmware was unable to find the
message
"plant of manufacture" in the VPD. This may cause
Response: DHCP discover received an unknown problems with the licensing of the AIX operating
DHCP message type. Insure that the DHCP server is system.
functioning properly.
Problem determination:
1. Using the Advanced System Management Interface
BA01D0FF BA01D0FF (ASMI) menus, insure that the machine type, model,
Explanation: Closing the DHCP node failed. and serial number in the VPD for this system are
correct.
Response: Look for server firmware updates; apply if 2. If this is a new system, check for server firmware
available. updates and apply them, if available.
658 System reference codes (Bxxx)
BA040040 • BA060040
v FWNIM
BA040040 BA040040
Explanation: Setting the machine type, model, and
BA060021 BA060021
serial number failed.
Explanation: The environment variable "boot-device"
Failing Item:
contained more than 5 entries.
v FWFWPBL
Failing Item:
v FWNIM
BA040041 BA040041
Explanation: Retrieving the machine type, model, and
BA060022 BA060022
serial number failed.
Explanation: The environment variable "boot-device"
Response: Look for server firmware updates; apply if
contained an entry that exceeded 255 characters.
available.
Failing Item:
BA040050 BA040050 v FWNIM
Explanation: The h-call to switch off the boot
watchdog timer failed. BA060023 BA060023
Failing Item: Explanation: The operating system does not support
the minimum processing unit that was specified.
v FWFWPBL
Failing Item:
BA040060 BA040060 v FWNIM
Explanation: Setting the firmware boot side for the
next boot failed. BA060030 BA060030
Failing Item: Explanation: Logical partitioning with shared
processors is enabled and the operating system does
v FWFWPBL
not support it.
Problem determination:
BA050001 BA050001
1. Install or boot a level of the operating system that
Explanation: Rebooting a partition in logical partition supports shared processors.
mode failed.
2. Disable logical partitioning with shared processors
Failing Item: in the operating system.
v FWFWPBL
BA060032 BA060032
BA050004 BA050004 Explanation: The operating system does not support
Explanation: Locating a service processor device tree active memory sharing (AMS).
node failed. Problem determination: Install or boot a version of
Failing Item: the operation system that supports AMS.
v FWFWPBL
BA060033 BA060033
BA05000A BA05000A Explanation: The operating system does not support
active memory expansion (AME).
Explanation: Failed to send boot failed message to the
service processor Problem determination: Install or boot a version of
the operation system that supports AME.
Failing Item:
v FWFWPBL
BA060040 BA060040
BA060020 BA060020 Explanation: The system or partition is configured to
use huge pages, but the operating system image does
Explanation: The environment variable "boot-device" not support huge pages.
exceeded the allowed character limit.
Problem determination: Do one of the following:
Failing Item:
(BAxx) Reference codes 659
BA060050 • BA070001
v Install a newer version of the operating system that
BA060075 BA060075
supports huge pages.
v Use the ASMI to remove the huge pages. Explanation: Client-arch-support firmware error.
Failing Item:
BA060050 BA060050 v FWFLASH
Explanation: The hypervisor supports dynamic
partitioning of the huge page-type of memory BA060200 BA060200
allocation, but dynamic partitioning of huge pages is
Explanation: Failed to set the operating system's boot
not supported.
list from the MM bootlist
Problem determination: Use the ASMI to disable
Problem determination:
dynamic partitioning of huge pages.
1. Verify that the bootlist in the MM is correct.
2. Check for firmware updates (MM, H8, system
BA060060 BA060060
firmware), and apply if available.
Explanation: The operating system expects an IOSP
partition, but the operating system failed to make the
BA060201 BA060201
transition to alpha mode.
Explanation: Failed to read VPD "boot path" field
Problem determination:
value
1. Insure that the alpha-mode operating system image
is intended for this partition. Problem determination: Check for firmware updates
(MM, H8, system firmware), and apply if available.
2. Insure that the configuration of the partition
supports an alpha-mode operating system.
BA060202 BA060202
BA060061 BA060061 Explanation: Failed to update VPD with new "boot
path" field value
Explanation: The operating system expects a
non-IOSP partition, but the operating system failed to Problem determination: Check for firmware updates
make the transition to MGC mode. (MM, H8, system firmware), and apply if available.
Problem determination:
1. Insure that the nonalpha-mode operating system BA060300 BA060300
image is intended for this partition. Explanation: An I/O error on the adapter from which
2. Insure that the configuration of the partition the boot was attempted prevented the operating system
supports a non-alpha-mode operating system. from being booted.
BA060070 BA060070 BA060411 BA060411
Explanation: The operating system does not support Explanation: Unable to resolved the MAC address
system's processor(s). that was specified; the boot list has not been changed.
Problem determination: Boot a newer version of the
operating system that supports the system's processors. BA070000 BA070000
Explanation: SCSI controller error
BA060071 BA060071
Problem determination: Do the following:
Explanation: Invalid number of vectors from the 1. Verify the SCSI cabling and termination
operating system.
2. Retry with minimal bus configuration to isolate the
Problem determination: Boot a newer version of the failing device.
operating system. 3. Replace the controller and/or device.
BA060072 BA060072 BA070001 BA070001
Explanation: Client-arch-support hcall error. Explanation: SCSI controller error
Failing Item: Response:
v FWFLASH 1. Verify the SCSI cabling and termination.
660 System reference codes (Bxxx)
BA080001 • BA090005
2. Retry with minimal bus configuration to isolate the
BA080014 BA080014
failing device.
3. Replace the controller and/or device. Explanation: The media has been changed
Problem determination: Retry the operation.
BA080001 BA080001 Failing Item:
Explanation: An IDE device remained busy for a v FWIDE1
longer period than the time out period.
Failing Item: BA080015 BA080015
v FWFWPBL Explanation: The packet command failed; the media
might not be readable.
BA080002 BA080002 Problem determination: Retry the operation.
Explanation: The IDE controller senses IDE devices Failing Item:
but with errors.
v FWIDE1
Problem determination:
v Verify that the IDE devices are correctly cabled and BA090001 BA090001
are firmly seated in the drive cage.
Explanation: SCSI disk unit: test unit ready failed;
v Replace the IDE controller (model-dependent).
hardware error
Failing Item:
BA080010 BA080010
v FWSCSI1
Explanation: An IDE device is busy longer than
specified time-out period.
BA090002 BA090002
Problem determination: Retry the operation.
Explanation: SCSI disk unit: test unit ready failed;
Failing Item: sense data available
v FWIDE1
Failing Item:
v FWSCSI2
BA080011 BA080011
Explanation: An IDE command timed out; command BA090003 BA090003
is exceeding the period allowed to complete.
Explanation: SCSI disk unit: send diagnostic failed;
Problem determination: Retry the operation. sense data available
Failing Item: Failing Item:
v FWIDE1 v FWSCSI3
BA080012 BA080012 BA090004 BA090004
Explanation: The ATA command failed Explanation: SCSI disk unit: send diagnostic failed:
Failing Item: devofl command
v FWIDE2 Failing Item:
v FWSCSI3
BA080013 BA080013
Explanation: The media is not present in the tray BA090005 BA090005
Problem determination: Place bootable media in tray Explanation: The virtual fibre channel boot driver had
and retry the opearation. an unexplained time out when trying to access the boot
media.
Failing Item:
Problem determination:
v FWIDE1
v Look for fibre channel errors in the virtual operating
system (VIOS) error log; resolve all that are found.
v Insure that the VIOS has the latest fibre channel
n_port ID virtualization (NPIV) driver updates.
(BAxx) Reference codes 661
BA090006 • BA090010
v Verify that the fibre channel storage server is
BA09000B BA09000B
working correctly. Correct any problems that are
found. Explanation: Generic SCSI sense error.
Problem determination: Generic SCSI sense error can
BA090006 BA090006 be:
Explanation: Unable to access the boot media due to v X4 - Hardware Error
"busy" response from the fibre channel storage server. v X5 - Illegal Request
Problem determination: v X7 - Data Protect
v Look for error log entries in the virtual operating v X8 - Blank Check
system (VIOS) that point to the fibre channel storage v X9 - Vendor Specific
server. Correct any problems that are found. v XA - Copy Aborted
v Reduce the load on the fibre channel server. v XB - Aborted Command
v XC - Equal
BA090007 BA090007 v XD - Volume Overflow
Explanation: An attempt to read the boot disk failed v XE - Miscompare
because of a reserve condition. v XF - RESERVED
Problem determination: Failing Item:
v Identify and remove any active RESERVES on the v FWSCSI1
fibre channel storage server.
BA09000C BA09000C
BA090008 BA090008
Explanation: The media are write-protected
Explanation: An attempt to send a command to the
fibre channel boot disk failed at the NPIV layer. Problem determination: Check the media and retry
the operation.
Problem determination:
v Look for fibre channel errors in the virtual operating
BA09000D BA09000D
system (VIOS) error log; resolve all that are found.
v Verify that the fibre channel storage server is Explanation: The media are unsupported or are
working correctly. Correct any problems that are unrecognizable.
found. Problem determination: Check the media and retry
the operation.
BA090009 BA090009
Explanation: An event happened on the virtual fibre BA09000E BA09000E
channel adapter that forced a full disconnection from Explanation: The media are not formatted correctly.
the fibre channel fabric.
Problem determination: Replace the media and retry
Problem determination: the operation.
v Insure that a firmware update was not occurring on
the fibre channel host bus adapter.
BA09000F BA09000F
v Insure that the cabling between the fibre channel
host bus adapter and the fibre channel storage server Explanation: The media are not present
is correct.
Problem determination: Insert or replace the media
v Insure that the virtual operating system (VIOS) has and retry the operation.
the latest fibre channel n_port ID virtualization
(NPIV) device driver updates.
BA090010 BA090010
BA09000A BA09000A Explanation: Request sense command failed
Explanation: Vendor specfication error Failing Item:
v FWSCSI1
Failing Item:
v NEXTLVL
662 System reference codes (Bxxx)
BA090011 • BA120010
BA090011 BA090011 BA110002 BA110002
Explanation: The number of times the retry command Explanation: SCSI changer: test unit ready failed;
has to be executed has exceeded the limit. sense data available.
Failing Item: Failing Item:
v FWSCSI1 v FWSCSI4
BA090012 BA090012 BA110003 BA110003
Explanation: The SCSI device type is not supported Explanation: SCSI changer: send diagnostic failed;
sense data available.
Problem determination: Replace the SCSI device with
a supported device. Failing Item:
v FWSCSI3
BA100001 BA100001
Explanation: SCSI tape: test unit ready failed; BA110004 BA110004
hardware error. Explanation: SCSI changer: send diagnostic failed:
Failing Item: devofl command.
v FWSCSI1 Failing Item:
v FWSCSI3
BA100002 BA100002
Explanation: SCSI tape: test unit ready failed; sense BA120001 BA120001
data available. Explanation: On an undetermined SCSI device, test
Failing Item: unit ready failed; hardware error.
v FWSCSI4 Failing Item:
v FWSCSI5
BA100003 BA100003
Explanation: SCSI tape: send diagnostic failed; sense BA120002 BA120002
data available. Explanation: On an undetermined SCSI device, test
Failing Item: unit ready failed; sense data available
v FWSCSI3 Failing Item:
v FWSCSI4
BA100004 BA100004
Explanation: SCSI tape: send diagnostic failed: devofl BA120003 BA120003
command. Explanation: On an undetermined SCSI device, send
Failing Item: diagnostic failed; sense data available
v FWSCSI3 Failing Item:
v FWSCSI4
BA110001 BA110001
Explanation: SCSI changer: test unit ready failed; BA120004 BA120004
hardware error Explanation: On an undetermined SCSI device, send
Problem determination: Before replacing any system diagnostic failed; devofl command
components refer to the notes in error code BA09xxxx. Failing Item:
1. Replace the SCSI device. v FWSCSI4
2. Replace the SCSI cable.
3. Replace the SCSI controller. BA120010 BA120010
Failing Item: Explanation: An I/O error on the adapter from which
v FWSCSI1 the boot was attempted prevented the operating system
from being booted.
(BAxx) Reference codes 663
BA120FFF • BA140004
Failing Item:
BA130012 BA130012
v FWFLASH
Explanation: USB CD-ROM: execution of ATA/ATAPI
command failed.
BA120FFF BA120FFF
Problem determination:
Explanation: SCSI device failed on 'inquiry' command
1. Verify that the power and signal cables going to the
Failing Item: USB CD-ROM are properly connected and are not
v FWSCSI1 damaged. If any problems are found, correct them,
then retry the operation.
2. If the problem persists, the CD in the USB CD-ROM
BA130001 BA130001 drive might not be readable. Remove the CD and
Explanation: SCSI CD-ROM: test unit ready failed; insert another CD.
hardware error. Failing Item:
Failing Item: v NEXTLVL
v FWSCSI1
BA130015 BA130015
BA130002 BA130002 Explanation: USB CD-ROM: ATA/ATAPI packet
Explanation: SCSI CD-ROM: test unit ready failed; command execution failed.
sense data available Problem determination: The CD in the USB CD-ROM
Failing Item: may not be readable. Try another CD.
v FWSCSI3 Failing Item:
v FWCD2
BA130003 BA130003
Explanation: SCSI CD-ROM: send diagnostic failed; BA140001 BA140001
sense data available. Explanation: SCSI read/write optical: test unit ready
Failing Item: failed; hardware error.
v FWSCSI3 Failing Item:
v FWSCSI1
BA130004 BA130004
Explanation: SCSI CD-ROM: send diagnostic failed: BA140002 BA140002
devofl command. Explanation: SCSI read/write optical: test unit ready
Failing Item: failed; sense data available.
v FWSCSI3 Failing Item:
v FWSCSI1
BA130010 BA130010
Explanation: USB CD-ROM: device remained busy BA140003 BA140003
longer than the time-out period. Explanation: SCSI read/write optical: send diagnostic
Problem determination: Retry the operation. failed; sense data available
Failing Item: Failing Item:
v FWFWPBL v FWSCSI3
BA130011 BA130011 BA140004 BA140004
Explanation: USB CD-ROM: execution of ATA/ATAPI Explanation: SCSI read/write optical: send diagnostic
command was not completed within the allowed time. failed; devofl command.
Problem determination: Retry the operation. Failing Item:
v FWSCSI3
Failing Item:
v FWCD1
664 System reference codes (Bxxx)
BA150001 • BA158003
BA150001 BA150001 BA154030 BA154030
Explanation: PCI Ethernet BNC/RJ-45 or PCI Ethernet Explanation: Bad argument from user
AUI/RJ-45 adapter: internal wrap test failure.
Problem determination: Check for system firmware
Problem determination: Replace the adapter specified update; apply if available.
by the location code.
BA154040 BA154040
BA151001 BA151001
Explanation: TFTP package open failed
Explanation: 10/100 MBPS Ethernet PCI adapter:
Problem determination: Check for system firmware
internal wrap test failure.
update; apply if available.
Problem determination: Replace the adapter specified
by the location code
BA154050 BA154050
Explanation: Transmit operation failed
BA151002 BA151002
Problem determination: Check for system firmware
Explanation: 10/100 MBPS Ethernet card
update; apply if available.
Failing Item:
v FWENET BA154060 BA154060
Explanation: Failed to initialize HEA port or queue
BA153002 BA153002
Problem determination: Check for system firmware
Explanation: Gigabit Ethernet adapter failure update; apply if available.
Problem determination: Verify that the MAC address
programmed in FLASH EEPROM is correct. BA154070 BA154070
Explanation: Receive operation failed
BA153003 BA153003
Problem determination: Check for system firmware
Explanation: Gigabit Ethernet adapter could not be update; apply if available.
mapped-in by system firmware
Problem determination: BA158001 BA158001
1. Check for adapter firmware updates; apply if
Explanation: VPD (vital product data) capability not
available.
found.
2. Remove other cards from the PHB in which the
gigabit Ethernet adapter is plugged and retry the Problem determination:
operation. If the operation is successful, plug the 1. Check for adapter microcode or firmware updates;
cards in again, one at a time, until the failing card is apply if available.
isolated. After you identify the failing card, replace 2. Replace the adapter specified by the location code
it. reported with the SRC.
3. Replace the adapter.
BA158002 BA158002
BA154010 BA154010
Explanation: A problem was found in the adapter's
Explanation: HEA h-call error VPD (vital product data).
Problem determination: Check for system firmware Problem determination:
update; apply if available. 1. Check for adapter microcode or firmware updates;
apply if available.
BA154020 BA154020 2. Replace the adapter specified by the location code
reported with the SRC.
Explanation: Required open firmware property not
found
BA158003 BA158003
Problem determination: Check for system firmware
update; apply if available. Explanation: VPD (vital product data) keyword error.
Additional error log data should show whether the
keyword was missing or invalid.
(BAxx) Reference codes 665
BA158004 • BA15A009
Problem determination:
BA15A005 BA15A005
1. Check for adapter microcode or firmware updates;
apply if available. Explanation: The flash register was not ready when
initially checked prior to reading the MAC address.
2. Replace the adapter specified by the location code
reported with the SRC. Problem determination:
1. Check for adapter microcode or firmware updates;
BA158004 BA158004 apply if available.
2. Replace the adapter specified by the location code
Explanation: Failed to allocate the VPD (vital product
reported with the SRC.
data) buffer.
Problem determination:
BA15A006 BA15A006
1. Check for adapter microcode or firmware updates;
apply if available. Explanation: The flash register was not ready
following the reading of the MAC transition.
2. Replace the adapter specified by the location code
reported with the SRC. Problem determination:
1. Check for adapter microcode or firmware updates;
BA15A001 BA15A001 apply if available.
2. Replace the adapter specified by the location code
Explanation: A registry property was not found.
reported with the SRC.
Problem determination:
1. Check for adapter microcode or firmware updates; BA15A007 BA15A007
apply if available.
Explanation: A parity error occurred when reading the
2. Replace the adapter specified by the location code
MAC address from the flash memory.
reported with the SRC.
Problem determination:
BA15A002 BA15A002 1. Check for adapter microcode or firmware updates;
apply if available.
Explanation: The assigned-address property was not
2. Replace the adapter specified by the location code
found.
reported with the SRC.
Problem determination:
1. Check for adapter microcode or firmware updates; BA15A008 BA15A008
apply if available.
Explanation: Initialization of the adapter chip set
2. Replace the adapter specified by the location code
failed.
reported with the SRC.
Problem determination:
BA15A003 BA15A003 1. Check for adapter microcode or firmware updates;
apply if available.
Explanation: Memory map-in failed for the control
2. Replace the adapter specified by the location code
register set memory region.
reported with the SRC.
Problem determination:
1. Check for adapter microcode or firmware updates; BA15A009 BA15A009
apply if available.
Explanation: Failed to open the OBP-TFTP package.
2. Replace the adapter specified by the location code
reported with the SRC. Problem determination:
1. Verify that the boot parameters in the SMS menus
BA15A004 BA15A004 are correct.
2. Check for adapter microcode or firmware updates;
Explanation: Failed to acquire the semaphore for the
apply if available.
flash register.
3. Replace the adapter specified by the location code
Problem determination: reported with the SRC.
1. Check for adapter microcode or firmware updates;
apply if available.
2. Replace the adapter specified by the location code
reported with the SRC.
666 System reference codes (Bxxx)
BA15B001 • BA160001
1. Retry the last firmware operation that was
BA15B001 BA15B001
attempted, such as an SMS ping, or network boot or
Explanation: Mailbox command failure. The error log installation attempt.
has additional information regarding the failure. 2. Check for adapter microcode or firmware updates;
Problem determination: apply if available.
1. Retry the last firmware operation that was 3. Replace the adapter specified by the location code
attempted, such as an SMS ping, or network boot or reported with the SRC.
installation attempt.
2. Check for adapter microcode or firmware updates; BA15B006 BA15B006
apply if available.
Explanation: Unexpected command response. The
3. Replace the adapter specified by the location code error log has additional information regarding the
reported with the SRC. failure.
Problem determination:
BA15B002 BA15B002
1. Retry the last firmware operation that was
Explanation: Error reading the PCI configuration attempted, such as an SMS ping, or network boot or
register. installation attempt.
Problem determination: 2. Check for adapter microcode or firmware updates;
apply if available.
1. Follow the repair actions for a freeze error that has
been reported on the adapter identified by the 3. Replace the adapter specified by the location code
location code. reported with the SRC.
2. Check for adapter microcode or firmware updates;
apply if available. BA15B007 BA15B007
3. Replace the adapter specified by the location code Explanation: A transmit operation timed out. The
reported with the SRC. error log has additional information regarding the
failure.
BA15B003 BA15B003 Problem determination:
Explanation: Initialization error. 1. Retry the last firmware operation that was
attempted, such as an SMS ping, or network boot or
Problem determination:
installation attempt.
1. Retry the last firmware operation that was
2. Check for adapter microcode or firmware updates;
attempted, such as an SMS ping, or network boot or
apply if available.
installation attempt.
3. Replace the adapter specified by the location code
2. Check for adapter microcode or firmware updates;
reported with the SRC.
apply if available.
3. Replace the adapter specified by the location code
reported with the SRC. BA15C001 BA15C001
Explanation: The command to retrieve the MAC
BA15B004 BA15B004 address from the adapter failed.
Explanation: Adapter VPD error. The error log entry Problem determination:
includes additional details. 1. Check for adapter microcode or firmware updates;
apply if available.
Problem determination:
2. Replace the adapter specified by the location code
1. Check for adapter microcode or firmware updates;
reported with the SRC.
apply if available.
2. Replace the adapter specified by the location code
reported with the SRC. BA160001 BA160001
3. Contact your next level of support. Explanation: PCI token ring adapter: failed to
complete hardware initialization.
BA15B005 BA15B005 Problem determination: Replace the adapter specified
by the location code.
Explanation: DMA allocation or mapping operation
failed. The error log has additional information
regarding the failure.
Problem determination:
(BAxx) Reference codes 667
BA161001 • BA180012
SMS menus to reenter the parameters for network
BA161001 BA161001
installation or boot.
Explanation: PCI token ring adapter: failed to
complete hardware initialization.
BA170998 BA170998
Problem determination: Replace the adapter specified
Explanation: NVRAMRC script evaluation error -
by the location code.
command line execution error.
Failing Item:
BA170100 BA170100
v FWNVR3
Explanation: NVRAM data validation check failed
Problem determination: Reboot the system or BA170999 BA170999
partition; this failure should correct itself.
Explanation: NVRAMRC script evaluation error -
Failing Item: stack unbalanced on completion.
v FWNVR2
Problem determination: This is a firmware debug
environment error. There is no user action or FRU
BA170201 BA170201 replacement for this error.
Explanation: The firmware was unable to expand the Failing Item:
target partition -saving configuration variable v NEXTLVL
Failing Item:
v FWNVR1 BA180008 BA180008
Explanation: PCI device FCode evaluation error.
BA170202 BA170202
Failing Item:
Explanation: The firmware was unable to expand the v FWPCI1
target partition - writing error log entry
Failing Item: BA180009 BA180009
v FWNVR1
Explanation: The FCode on a PCI adapter left a data
stack imbalance.
BA170203 BA170203
Problem determination: You should load the new
Explanation: The firmware was unable to expand the adapter Fcode before you use the adapter (specified by
target partition - writing VPD data the location code associated with this error) for booting.
Failing Item: Failing Item:
v FWNVR1 v FWPCI1
BA170220 BA170220 BA180010 BA180010
Explanation: The firmware was unable to write a Explanation: PCI probe error, bridge in freeze state.
variable value into NVRAM because not enough space
Failing Item:
exists in NVRAM.
v FWPCI2
Problem determination: Do the following:
v Reduce the number of partitions, if possible, so that
BA180011 BA180011
each of the remaining partitions has more NVRAM
allocated to it. Explanation: PCI bridge probe error, bridge is not
usable.
Failing Item:
v NEXTLVL Failing Item:
v FWPCI3
BA170221 BA170221
BA180012 BA180012
Explanation: The setenv/$setenv function had to
delete network boot information to free space in Explanation: PCI device runtime error, bridge in
NVRAM. freeze state.
Problem determination: You might need to use the Failing Item:
668 System reference codes (Bxxx)
BA180013 • BA201002
v FWPCI3
BA180100 BA180100
Explanation: FDDI Adapter FCode driver is not
BA180013 BA180013
supported on this system.
Explanation: A PCI adapter was found that this
Problem determination: This server does not support
machine type and model does not support.
the Fcode driver on this adapter. Service support might
Problem determination: Is this system an IBM have additional information.
Intellistation model?
v Yes: Complete the following steps. BA180101 BA180101
1. Check for and apply any available server
Explanation: Stack underflow from fibre-channel
firmware udpates.
adapter.
2. Replace the adapter at the location code that was
reported with the error. Failing Item:
v No: Remove the PCI adapter specified by the v FWFWPBL
location code.
BA188000 BA188000
BA180014 BA180014 Explanation: An unsupported adapter was found in a
Explanation: MSI software error PCI slot.
Failing Item: Problem determination: Remove the unsupported
adapter in the slot specified by the location code.
v FWFLASH
BA188001 BA188001
BA180015 BA180015
Explanation: EEH recovered a failing I/O adapter.
Explanation: PCI slot error operation recovery timed
out. Problem determination: This is an informational code
only, and no action is required. Since it is informational,
Failing Item:
no location code will be reported.
v FWPCI1
BA188002 BA188002
BA180020 BA180020
Explanation: EEH could not recover the failed I/O
Explanation: No responce was received from a PCI adapter.
slot during probing
Problem determination: Replace the adapter in the
Failing Item: slot specified by the location code.
v FWPCI1
BA191001 BA191001
BA180030 BA180030
Explanation: The hypervisor function to turn on the
Explanation: A PHB reset/recovery was successful. speaker reported an error.
Failing Item:
BA180031 BA180031 v FWFWPBL
Explanation: A PHB was reset more than once during
the boot or reboot of a system or partition. BA201001 BA201001
Explanation: The serial interface dropped data packets
BA180099 BA180099
Failing Item:
Explanation: PCI probe error, bridge in freeze state,
v FWFWPBL
slot in reset state.
Failing Item:
BA201002 BA201002
v FWFLASH
Explanation: The serial interface failed to open.
Problem determination: Check console settings to
ensure the console is defined to the correct port. Ensure
(BAxx) Reference codes 669
BA201003 • BA210100
the console cables are connected to the port that is
BA210005 BA210005
defined as the console.
Explanation: Open firmware free memory chain
Failing Item:
corruption detected and isolated.
v FWFWPBL
Problem determination: Check for system firmware
update. Contact your next level support for assistance.
BA201003 BA201003
Explanation: The firmware failed to handshake BA210010 BA210010
properly with the serial interface.
Explanation: The transfer of control to the SLIC loader
Problem determination: Check for system firmware failed.
update.
Failing Item:
Contact your next level support for assistance.
v FWFWPBL
Failing Item:
v FWFWPBL BA210011 BA210011
Explanation: The transfer of control to the I/O
BA210000 BA210000 reporter failed.
Explanation: Partition firmware reports a default Failing Item:
catch.
v FWFWPBL
Failing Item:
v FWFWPBL BA210012 BA210012
Explanation: NVRAMRC forced-boot problem; unable
BA210001 BA210001 to load operating system that was loaded on previous
Explanation: Partition firmware reports a stack boot.
underflow was caught. Problem determination: Use the bootlist menus in the
Failing Item: SMS to verify that the operating system image can still
be detected by firmware. If firmware does not see the
v FWFWPBL image, reload the operating system.
BA210002 BA210002 BA210013 BA210013
Explanation: Partition firmware was ready before Explanation: There was a partition firmware error
standout was ready. when in the SMS menus.
Failing Item: Response: Look for server firmware updates; apply if
v FWFWPBL available.
BA210003 BA210003 BA210020 BA210020
Explanation: Partition firmware detected a data Explanation: The I/O configuration exceeds the
storage error. maximum size allowed by partition firmware.
Failing Item: Problem determination: Increase the logical memory
v FWPCI1 block size to 256 megabytes (MB) and reboot the
managed system. (If the logical memory block size is
already 256 MB, contact your next level of support.)
BA210004 BA210004
Failing Item:
Explanation: An open firmware stack-depth assert
v NEXTLVL
failed .
Problem determination: Check for system firmware
BA210100 BA210100
update. Contact your next level support for assistance.
Explanation: The partition firmware was unable to log
an error with the server firmware. No reply was
received from the server firmware to an error log that
was sent previously.
670 System reference codes (Bxxx)
BA210101 • BA278003
Failing Item:
BA250010 BA250010
v NEXTLVL
Explanation: dlpar error in open firmware.
BA210101 BA210101 Failing Item:
v FWLPAR
Explanation: The partition firmware error log queue is
full.
BA250020 BA250020
Problem determination: Contact service support.
Explanation: dlpar error in open firmware due to an
Failing Item:
invalid dlpar entity. This error may have been caused
v NEXTLVL by an errant or hung operating system process.
Problem determination: Do the following:
BA210102 BA210102
1. Check for operating system updates that resolve
Explanation: There was a communication failure problems with dynamic logical partitioning (dlpar)
between partition firmware and the hypervisor. The and apply them, if available.
lpevent that was expected from the hypervisor was not 2. Check for server firmware updates and apply them,
received. if available.
Response:
1. Review the error logs for errors that occurred BA250030 BA250030
around the time of this error. Correct any errors that
Explanation: A hotplug operation in dynamic logical
are found and reboot the blade server.
partitioning (dlpar) was terminated for concurrent
2. Look for server firmware updates; apply if firmware update.
available.
Problem determination: Retry the hotplug operation
after the concurrent firmware update is complete.
BA210103 BA210103
Explanation: There was a communication failure BA250040 BA250040
between partition firmware and the hypervisor. There
was a failing return code with the lpevent Explanation: Unable to generate device-tree node for
acknowledgement from the hypervisor. partition migration
Response: Problem determination: After performing the
FWFLASH procedure, check for operating system
1. Review the error logs for errors that occurred
updates and apply them if available.
around the time of this error. Correct any errors that
are found and reboot the blade server. Failing Item:
2. Look for server firmware updates; apply if v FWFLASH
available.
BA278001 BA278001
BA220010 BA220010
Explanation: Failed to flash firmware; invalid image
Explanation: The partition firmware got an error file
during USB hotplug probing. USB hotplug may not
Problem determination: Obtain a valid firmware
work properly on this partition.
image for this system.
Problem determination: Do the following:
1. Check for EEH-related entries in the error logs and, BA278002 BA278002
if found, resolve them.
Explanation: Flash file is not designed for this eServer
2. Check for system firmware updates; apply if
platform.
available.
Problem determination: Obtain a valid firmware
image for this system.
BA220020 BA220020
Explanation: CRQ registration error; partner vslot not
BA278003 BA278003
valid.
Explanation: Unable to lock the firmware update lid
Problem determination: From the HMC, verify that
manager.
this client virtual-slot device has a valid server
virtual-slot device in a hosting partition. Problem determination: Do the following:
(BAxx) Reference codes 671
BA278004 • BA300020
1. Reboot the system. are found in the error logs, then retry the firmware
2. Make sure that the operating system is authorized flash.
to update the firmware. If the system is running
multiple partitions, verify that this partition has BA280000 BA280000
service authority.
Explanation: RTAS discovered an invalid operation
that may cause a hardware error.
BA278004 BA278004
Problem determination: Do not perform the action
Explanation: An invalid firmware update lid was again.
requested.
Failing Item:
Problem determination: Obtain a valid firmware
v NEXTLVL
image for this system.
BA290000 BA290000
BA278005 BA278005
Explanation: RTAS discovered an internal stack
Explanation: Failed to flash a firmware update lid.
overflow
Problem determination: Obtain a valid firmware
Failing Item:
image for this system.
v FWFWPBL
BA278006 BA278006
BA290001 BA290001
Explanation: Unable to unlock the firmware update
lid manager. Explanation: RTAS low memory corruption
Problem determination: Reboot the system. Failing Item:
v FWFWPBL
BA278007 BA278007
BA290002 BA290002
Explanation: Failed to reboot the system after a
firmware flash update. Explanation: RTAS low memory corruption
Problem determination: Manually reboot the system. Failing Item:
v FWFWPBL
BA278008 BA278008
Explanation: A server firmware update was attempted BA300010 BA300010
from the operating system. You must perform the Explanation: The partition exceeded the maximum
update by using the Hardware Management Console number of logical memory blocks allowed under the
(HMC). new memory allocation scheme.
Problem determination: Perform the flash update Problem determination: Reduce the total logical
from the HMC. memory block limit in the partition profile, then
reactivate the partition. (The maximum number of
BA278009 BA278009 logical memory blocks per partition is 128 kilobytes
(Kb) under the new memory allocation scheme.)
Explanation: The server firmware update management
tools for the version of Linux that you are running are
incompatible with this system. BA300020 BA300020
Problem determination: Go to the Service and Explanation: Function call to isolate a logical memory
productivity tools for Linux on POWER link and block failed under the standard memory allocation
download the latest service aids and productivity tools scheme.
for the version of Linux that you are running. Problem determination: Do the following:
1. Check for system firmware updates; apply if
BA27800A BA27800A available.
Explanation: Firmware flash failed due to hardware 2. Upgrade the operating system to a level that
error being reported. supports the new memory representation, or edit
the profile to have fewer logical memory blocks
Problem determination: Resolve any problems that than the 8K maximum.
3. Reboot the partition.
672 System reference codes (Bxxx)
BA300030 • BA330011
BA300030 BA300030 BA330000 BA330000
Explanation: Function call to make a logical memory Explanation: Memory allocation error in partition
block unusable failed under the standard memory firmware.
allocation scheme.
Problem determination:
Problem determination: Do the following: v Reboot partition
1. Check for system firmware updates; apply if v Reflash firmware
available.
2. Upgrade the operating system to a level that
BA330001 BA330001
supports the new memory representation, or edit
the profile to have fewer logical memory blocks Explanation: memory allocation error
than the 8K maximum.
Problem determination:
3. Reboot the partition.
v Reboot partition
v Reflash firmware
BA300040 BA300040
Explanation: The partition, which is running the BA330002 BA330002
traditional memory representation, exceeded the limit
of 8192 logical memory blocks allowed by the standard Explanation: memory allocation error
memory allocation scheme.
Problem determination:
Problem determination: Do the following: v Reboot partition
1. Upgrade the operating system to a level that v Reflash firmware
supports the new memory representation, or edit
the profile to have fewer logical memory blocks
than the 8K maximum. BA330003 BA330003
2. Reboot the partition. Explanation: memory allocation error
Problem determination:
BA310010 BA310010 v Reboot partition
Explanation: The firmware could not obtain the SRC v Reflash firmware
history.
Failing Item: BA330004 BA330004
v FWFLASH Explanation: memory allocation error
Problem determination:
BA310020 BA310020
1. Reboot the partition.
Explanation: The firmware received an invalid SRC 2. Check for system firmware updates; apply if
history. available.
Failing Item:
v FWFLASH BA330010 BA330010
Explanation: A virtual real memory (VRM) pin page
BA320030 BA320030 function call failed.
Explanation: The firmware operation to write the Problem determination:
MAC address to vital product data (VPD) failed 1. Check for the system firmware updates; apply if
Failing Item: available.
v FWFLASH 2. Contact your next level of support.
BA320060 BA320060 BA330011 BA330011
Explanation: Invalid vital product data (VPD): no Explanation: A virtual real memory (VRM) unpin
description was found. page function call failed.
Failing Item: Problem determination:
v FWFLASH 1. Check for the system firmware updates; apply if
available.
(BAxx) Reference codes 673
BA350000 • BA54505D
2. Contact your next level of support.
BA400002 BA400002
Explanation: DMA map-out size mismatch;
BA350000 BA350000
informational message.
Explanation: An error occurred when attempting to
Problem determination: Check for system firmware
create a system plan; this normally results in no system
updates; apply if available.
plan being created. This is an informational code;
typically, no hardware needs to be replaced. The
problem may be an intermittent hardware error, or may BA54504D BA54504D
be firmware-related.
Explanation: A Virtual Trusted Platform Module
Problem determination: (vTPM) driver entered a failure state.
1. Try again to create a system plan. If the retry is Problem determination: Check for system firmware
successful and the system plan is created, no other updates; apply if available.
action is required.
2. Check the error logs for hardware errors, and verify
BA54505D BA54505D
that I/O hardware is reporting correctly to the
server. If a problem is found, correct it, then try Explanation: An error occurred while trying to return
again to create a system plan. the Virtual Trusted Platform Module (vTPM) to the init
3. Check for and apply any available system firmware state.
update. Problem determination: Check for system firmware
4. Contact your next level of support. updates; apply if available.
BA350100 BA350100
Explanation: Informational message: the string
property value is longer than the buffer that was
allocated. The string has been truncated to fit in the
buffer space that was allocated.
BA350103 BA350103
Explanation: Failed to obtain the time and date from
firmware.
Problem determination:
1. Check for system firmware updates; apply if
available.
2. Reboot the system.
BA350104 BA350104
Explanation: An error occurred in the firmware
function that manages parent topology identifiers.
Problem determination:
1. Reboot the system.
2. Check for system firmware updates; apply if
available.
BA400001 BA400001
Explanation: DMA trace buffer overflow;
informational message.
Response: Check for system firmware updates; apply
if available.
674 System reference codes (Bxxx)
(BF67) Reference codes
The Linux operating system detected a failure in the emulex driver.
The first five characters (BFxxx) of these SRCs indicate the driver or subsystem responsible for the error,
and the last three characters specifies the error condition. The last three characters of the SRCs are
arranged such that 1xx is lowest severity and Fxx is highest severity.
Use the following list to locate the (BF67) Linux SRC that you want to find, then perform the suggested
actions.
Note: If the suggested action in the User Response field does not work (or if there is no suggested
action), use the action specified in the FRU List.
BF677800 BF677800 BF677803 BF677803
Explanation: An ELS IOCB command was posted to a Explanation: This error might indicate a software
ring and did not complete within ULP timeout seconds. driver, firmware or hardware problem.
Response: If no ELS command is going through the Response: This message indicates one of the following
adapter, reboot the system. conditions:
Failing Item: v Port rsp ring put index is greater than the size of rsp
ring
v NEXTLVL
v Port cmd ring get index is greater than the size of
cmd ring
BF677801 BF677801
v Port cmd ring get index is greater than the size of
Explanation: The driver attempted to issue cmd ring
READ_SPARAM mailbox command to the HBA but v The assigned I/O iotag is greater than the max
there were no buffer available. allowed
Response: This message indicates one of the following v The assigned I/O iotag is greater than the max
conditions: allowed
v A possible lack of memory resources. Try increasing Failing Item:
the lpfc num_bufs configuration parameter to allocate
v NEXTLVL
more buffers
v A possible driver buffer management problem
BF677804 BF677804
Failing Item:
Explanation: The Rctl/Type of a received frame did
v NEXTLVL
not match anyfor the configured masks for the
specified ring. This error might indicate a software
BF677802 BF677802 driver or firmware problem.
Explanation: The driver attempted to issue Failing Item:
REG_LOGIN mailbox command to the HBA but there v NEXTLVL
were no buffer available.
Response: This message indicates one of the following BF677805 BF677805
conditions:
Explanation: Received an unknown IOCB command
v A possible lack of memory resources. Try increasing
completion. Thiserror might indicate a software driver
the lpfc num_bufs configuration parameter to allocate
or firmware problem.
more buffers
v A possible driver buffer management problem Failing Item:
v NEXTLVL
Failing Item:
v NEXTLVL
BF677806 BF677806
© Copyright IBM Corp. 2010, 2013 675
BF677807 • BF677A05
Explanation: The driver wan unable to find a v ASCII string to hex conversion failed. The output
matching command forthe completion received on the buffer byte size is less than one-half of the input byte
specified ring. This error might indicate a software count. Every two input chars (bytes) require one
driver or firmware problem. output byte
Failing Item: Failing Item:
v NEXTLVL v NEXTLVL
BF677807 BF677807 BF677A00 BF677A00
Explanation: A unknown mailbox command Explanation: The driver decided to drop an ELS
completed. This error mightindicate a software driver, Response ring entry.This error might indicate a
firmware or hardware problem. software driver or firmware problem.
Failing Item: Failing Item:
v NEXTLVL v NEXTLVL
BF677808 BF677808 BF677A01 BF677A01
Explanation: The configuration parameter for Explanation: Received a mailbox completion interrupt
scan-down is out ofrange. Software driver error. and there areno outstanding mailbox commands. This
error might indicate a hardware or firmware problem.
Failing Item:
Update firmware.
v NEXTLVL
Failing Item:
v NEXTLVL
BF677809 BF677809
Explanation: The driver attempted to register the HBA
BF677A02 BF677A02
interrupt serviceroutine with the host operating system
but failed. This error might indicate a hardware or Explanation: The driver issued a CONFIG_LINK
driver problem. mbox command to theHBA that failed. This error might
indicate a firmware or hardware problem. Update
Failing Item:
firmware or replace adapter.
v NEXTLVL
Failing Item:
v NEXTLVL
BF67780A BF67780A
Explanation: The driver manages its own memory for
BF677A03 BF677A03
internal usage.This error indicates a problem occurred
in the driver memory management routines. This error Explanation: The driver issued a READ_SPARAM
might also indicate the host system in low on memory mbox command to theHBA that failed. This error might
resources. This error might indicate a driver or host indicate a firmware or hardware problem.
operating system problem.
Failing Item:
Failing Item: v NEXTLVL
v NEXTLVL
BF677A04 BF677A04
BF67780B BF67780B
Explanation: The driver issued a CLEAR_LA mbox
Explanation: This error might indicate a software command to the HBAthat failed. This error might
driver problem. indicate a firmware or hardware problem.
Response: This message indicates one of the following Failing Item:
conditions: v NEXTLVL
v ASCII string to hex conversion failed. Input byte
count less than 1
BF677A05 BF677A05
v ASCII string to hex conversion failed. Input byte
count greater than the max num Explanation: A read nvparams mailbox command
failed during configport. This error might indicate a
hardware or firmware problem.
Failing Item:
676 System reference codes (Bxxx)
BF677A06 • BF677A12
v NEXTLVL Failing Item:
v NEXTLVL
BF677A06 BF677A06
Explanation: The driver cannot find the specified BF677A0D BF677A0D
buffer in its mappingtable. This error might indicate a Explanation: Adapter initialization failed when
software driver or firmware problem. issuing CFG_RINGmailbox command. This error might
Failing Item: indicate a hardware or firmware problem.
v NEXTLVL Failing Item:
v NEXTLVL
BF677A07 BF677A07
Explanation: The adapter failed during power-up BF677A0E BF677A0E
diagnostics afterit was reset. This error might indicate a Explanation: Adapter initialization failed when
hardware or firmware problem. issuing CONFIG_LINKmailbox command. This error
Failing Item: might indicate a hardware or firmware problem.
v NEXTLVL Failing Item:
v NEXTLVL
BF677A08 BF677A08
Explanation: The adapter failed during power-up BF677A0F BF677A0F
diagnostics afterit was reset. This error might indicate a Explanation: Adapter initialization failed when
hardware or firmware problem. issuing READ_SPARMmailbox command. This error
Failing Item: might indicate a hardware or firmware problem.
v NEXTLVL Failing Item:
v NEXTLVL
BF677A09 BF677A09
Explanation: Adapter initialization failed when BF677A10 BF677A10
issuing READ_REVmailbox command. This error might Explanation: Adapter initialization failed when
indicate a hardware or firmware problem. issuing READ_CONFIGmailbox command. This error
Failing Item: might indicate a hardware or firmware problem.
v NEXTLVL Failing Item:
v NEXTLVL
BF677A0A BF677A0A
Explanation: Outdated firmware was detected during BF677A11 BF677A11
initialization.This error might indicate a hardware or Explanation: Adapter initialization failed when
firmware problem. Update firmware. issuing INIT_LINKmailbox command. This error might
Failing Item: indicate a hardware or firmware problem.
v NEXTLVL Failing Item:
v NEXTLVL
BF677A0B BF677A0B
Explanation: Adapter initialization failed when BF677A12 BF677A12
issuing DUMP_VPDmailbox command. This error Explanation: The driver received an interrupt
might indicate a hardware or firmware problem. indicting a possiblehardware problem. This error might
Failing Item: indicate a hardware or firmware problem.
v NEXTLVL Failing Item:
v NEXTLVL
BF677A0C BF677A0C
Explanation: Adapter initialization failed when
issuing CONFIG_PORTmailbox command. This error
might indicate a hardware or firmware problem.
(BF67) Reference codes 677
678 System reference codes (Bxxx)
(BF75) Reference codes
The Linux operating system detected a failure in the ipr driver.
The first five characters (BFxxx) of these SRCs indicate the driver or subsystem responsible for the error,
and the last three characters specifies the error condition. The last three characters of the SRCs are
arranged such that 1xx is lowest severity and Fxx is highest severity. For example:
v Errors that require you to check cables occur in the 5xx range
v Errors that require you to perform a microcode update occur in the Axx range
v Errors that require you to replace an adapter occur in the Fxx range
Use the following list to locate the (BF75) Linux SRC that you want to find, then perform the suggested
actions.
Note: If the suggested action in the User Response does not work (or if there is no suggested action), use
the action specified in the FRU list.
v NEXTLVL
BF751800 BF751800
Explanation: 8155: An unknown error was received.
BF751A04 BF751A04
Have the customerupdate the device driver.
Explanation: Microcode download required. Have the
Failing Item:
customer updatethe adapter microcode.
v NEXTLVL
Failing Item:
v NEXTLVL
BF751A00 BF751A00
Explanation: Firmware file %s not found. Have the
BF751A05 BF751A05
customer updatethe adapter microcode.
Explanation: Failed to map microcode download
Failing Item:
buffer. Have thecustomer update the adapter
v NEXTLVL microcode.
Failing Item:
BF751A01 BF751A01
v NEXTLVL
Explanation: Invalid microcode buffer. Have the
customer updatethe adapter microcode.
BF751A06 BF751A06
Failing Item:
Explanation: 8151: IOA microcode error. Have the
v NEXTLVL customer updatethe adapter microcode and the device
driver.
BF751A02 BF751A02 Failing Item:
Explanation: Microcode buffer allocation failed. Have v NEXTLVL
the customerupdate the adapter microcode.
Failing Item: BF751C00 BF751C00
v NEXTLVL Explanation: Adapter being reset due to command
timeout. Have thecustomer update the adapter
BF751A03 BF751A03 microcode.
Explanation: Microcode buffer copy to DMA buffer Failing Item:
failed. Have thecustomer update the adapter v IOADPTR
microcode.
Failing Item: BF751C01 BF751C01
© Copyright IBM Corp. 2010, 2013 679
BF751D00 • BF751D0B
Explanation: Invalid resource address. Have the
BF751D07 BF751D07
customer updatethe device driver.
Explanation: This message indicates one of the
Failing Item:
conditions below.
v IOADPTR
Problem determination:
v Array protection temporarily suspended
BF751D00 BF751D00
v IOA detected device error
Explanation: 7001: IOA sector reassignment successful.
v Cache data belongs to devices other than those
Media error.
attached
Failing Item: v Maximum number of arrays already exist
v IO_DEV v Incorrect hardware configuration change has been
detected
BF751D01 BF751D01
Perform MAP 3390 in the PCI-X SCSI RAID Controller
Explanation: Unsolicited device bus message received. Reference Guide for Linux .
Failing Item: Failing Item:
v IO_DEV v NEXTLVL
BF751D02 BF751D02 BF751D08 BF751D08
Explanation: Device hardware error. Explanation: IOA detected a SCSI bus configuration
Failing Item: error. Device bus error, message or command phase.
Perform MAP 3350 in the PCI-X SCSI RAID Controller
v IO_DEV Reference Guide for Linux .
Failing Item:
BF751D03 BF751D03
v NEXTLVL
Explanation: Predictive failure analysis.
Failing Item: BF751D09 BF751D09
v IO_DEV Explanation: IOA cache data exists for a missing or
failed device. Perform MAP 3332 in the PCI-X SCSI
BF751D04 BF751D04 RAID Controller Reference Guide for Linux .
Explanation: Device error. May occur normally during Failing Item:
concurrent maintenance. v NEXTLVL
Failing Item:
v IO_DEV BF751D0A BF751D0A
Explanation: Disk unit has been modified after the
BF751D05 BF751D05 last known status.Incorrect hardware configuration
change has been detected. Perform MAP 3333 in the
Explanation: Out of alternate sectors for disk storage. PCI-X SCSIRAID Controller Reference Guide for Linux .
Failing Item: Failing Item:
v IO_DEV v NEXTLVL
BF751D06 BF751D06 BF751D0B BF751D0B
Explanation: 9031: Array protection temporarily Explanation: A permanent cache battery pack failure
suspended, protectionresuming. Hardware occurred. Perform MAP 3300 in the PCI-X SCSI RAID
configuration error. Perform MAP 3310 in the PCI-X Controller Reference Guide for Linux .
SCSI RAID Controller Reference Guide for Linux .
Failing Item:
Failing Item:
v NEXTLVL
v NEXTLVL
680 System reference codes (Bxxx)
BF751D0C • BF751F07
BF751D0C BF751D0C BF751F00 BF751F00
Explanation: Cache data associated with attached Explanation: Permanent IOA failure.
devices cannot befound. Perform MAP 3320 in the
Failing Item:
PCI-X SCSI RAID Controller Reference Guide for Linux .
v IOADPTR
Failing Item:
v NEXTLVL
BF751F01 BF751F01
Explanation: Invalid response handle from IOA.
BF751D0D BF751D0D
Failing Item:
Explanation: Array missing two or more devices with
only one devicepresent. Perform MAP 3311 in the v IOADPTR
PCI-X SCSI RAID Controller Reference Guide for Linux .
Failing Item: BF751F02 BF751F02
v NEXTLVL Explanation: IOA unit check with no data.
Failing Item:
BF751D0E BF751D0E v IOADPTR
Explanation: One or more array members not at
required physical locations. Perform MAP 3312 in the BF751F03 BF751F03
PCI-X SCSI RAID Controller Reference Guide for Linux .
Explanation: IOA taken offline - error recovery failed.
Failing Item:
v NEXTLVL Failing Item:
v IOADPTR
BF751D0F BF751D0F
BF751F04 BF751F04
Explanation: Array is missing a device and parity is
out of sync. Perform MAP 3313 in the PCI-X SCSI Explanation: Adapter not supported in this hardware
RAID Controller Reference Guide for Linux . configuration.Remove the unsupported adapter from
the system.
Failing Item:
v NEXTLVL Failing Item:
v IOADPTR
BF751D10 BF751D10
BF751F05 BF751F05
Explanation: Required cache data cannot be located
for a disk unit. Perform MAP 3331 in the PCI-X SCSI Explanation: Failed to set PCI DMA mask.
RAID Controller Reference Guide for Linux .
Failing Item:
Failing Item: v IOADPTR
v NEXTLVL
BF751F06 BF751F06
BF751D11 BF751D11
Explanation: Write of cache line size failed.
Explanation: IOA resources not available due to
Failing Item:
previous problems. Perform MAP 3321 in the PCI-X
SCSI RAID Controller Reference Guide for Linux . v IOADPTR
Failing Item:
BF751F07 BF751F07
v NEXTLVL
Explanation: Failed to save PCI configuration space.
BF751D12 BF751D12 Failing Item:
Explanation: Disk unit requires initialization before v IOADPTR
use. Perform MAP 3334 in the PCI-X SCSIRAID
Controller Reference Guide for Linux .
Failing Item:
v NEXTLVL
(BF75) Reference codes 681
BF751F08 • BF751F09
BF751F08 BF751F08
Explanation: Soft PCI bus error.
Failing Item:
v IOADPTR
BF751F09 BF751F09
Explanation: Adapter hardware error.
Failing Item:
v IOADPTR
682 System reference codes (Bxxx)
(BF77) Reference codes
The Linux operating system detected a failure in a driver or subsystem.
The first five characters (BFyyy) of these SRCs indicate the driver or subsystem responsible for the error:
v BF77 0xxx specifies the olympic driver
v BF77 5xxx specifies the pcnet32 driver
v BF77 6xxx specifies the bcm 5700 driver
v BF77 7xxx specifies the e100 driver
v BF77 8xxx specifies the e1000 driver
The last three characters specify the error condition. The last three characters of the SRCs are arranged
such that 1xx is lowest severity and Fxx is highest severity. For example:
v Errors that require you to check cables occur in the 5xx range
v Errors that require you to perform a microcode update occur in the Axx range
v Errors that require you to replace an adapter occur in the Fxx range
Use the following list to locate the (BF77) Linux SRC that you want to find, then perform the suggested
actions:
Note: If the suggested action in the User Response field does not work (or if there is no suggested
action), use the action specified in the FRU List.
BF770800 BF770800 BF770F02 BF770F02
Explanation: The driver was unable to send a received Explanation: The Cardbus token ring adapter did not
packet to theupper layer protocols because there is respond to initializationcommands. Ensure that
insufficient free memory. The customer may need to Cardbus adapter is properly inserted.
increase system memory.
Failing Item:
Failing Item: v IOADPTR
v LPARCFG
BF770F03 BF770F03
BF770A00 BF770A00
Explanation: The token ring adapter was unable to
Explanation: Unrecognized command code or join the ring.Have the customer use the network
unrecognized buffer address. configuration tool supplied by the distributor to specify
a ring speed (instead of automatically detecting ring
Problem determination:
speed).
1. Reload the driver and reset the device to recover
lost buffers Failing Item:
2. Upgrade the driver v IOADPTR
Failing Item:
BF770F04 BF770F04
v NEXTLVL
Explanation: The adapter open request failed with the
specified errorcode.
BF770F01 BF770F01
Failing Item:
Explanation: The olympic driver was unable to
initialize the tokenring card. Corrective action may be v IOADPTR
possible depending upon the error code.
Failing Item: BF770F05 BF770F05
v IOADPTR Explanation: The specified hardware, PCI or parity
© Copyright IBM Corp. 2010, 2013 683
BF770F06 • BF775F01
error has occurred.Have the customer reset the adapter
BF775800 BF775800
Failing Item:
Explanation: The driver was unable to use 32-bit
v IOADPTR DMA. Have thecustomer verify the driver software
level.
BF770F06 BF770F06 Failing Item:
Explanation: The specified interrupt has occurred, but v NEXTLVL
was not expectedby the driver or a timeout occurred
during device close processing. For occasional
BF775801 BF775801
occurances, no action is required. For excessive
occurrences, have the customer reset the adapter. If Explanation: Memory allocation failed.
resetting the adapter does not work, perform the action
Problem determination:
specified in the Failing Item column.
1. Verify the driver software level
Failing Item:
2. Increase the memory on the system
v IOADPTR
Failing Item:
v NEXTLVL
BF770F07 BF770F07
Explanation: Unrecognized srb command or cannot
BF775802 BF775802
set mac/laa addresswhile card is open. Have the
customer reload the driver Explanation: Transmit timed out, resetting. Have the
customer verifythe driver software level.
Failing Item:
v IOADPTR Failing Item:
v NEXTLVL
BF770F08 BF770F08
BF775803 BF775803
Explanation: A short circuit has been detected.
Explanation: A FIFO error has occurred. Have the
Problem determination:
customer verifythe driver software level.
v Check and replace cables, if necessary
Failing Item:
v Check and replace peer stations on ring, if necessary
v NEXTLVL
Failing Item:
v IOADPTR
BF775804 BF775804
Explanation: The transmit pointers are out of
BF770F09 BF770F09
synchronization.Have the customer verify the driver
Explanation: An internal hardware error has been software level.
detected in thespecified adapter during auto removal
Failing Item:
processing. Have the customer reload the driver
v NEXTLVL
Failing Item:
v IOADPTR
BF775F00 BF775F00
Explanation: The driver could not enable the PCI
BF770F0A BF770F0A
device.
Explanation: An FDX protocol error has been
Failing Item:
detected. Have thecustomer reload the driver
v IOADPTR
Failing Item:
v IOADPTR
BF775F01 BF775F01
Explanation: The hardware did not request any IO
BF770F0B BF770F0B
resources.
Explanation: Invalid return code in asb. Have the
Failing Item:
customer upgradethe driver
v IOADPTR
Failing Item:
v IOADPTR
684 System reference codes (Bxxx)
BF775F02 • BF776800
BF775F02 BF775F02 BF776504 BF776504
Explanation: The IO addresses for the card are already Explanation: Memory allocation failed - buffer
allocated.Have the customer verify the driver software parameters may beset too high.
level.
Problem determination:
Failing Item: 1. Reduce the tx_pkt_desc_cnt parameter of the driver
v IOADPTR 2. Reduce the rx_std_desc_cnt parameter of the driver
3. Reduce the rx_jumbo_desc_cnt parameter of the
BF775F03 BF775F03 driver
Explanation: The chip can not be accessed in 32-bit or Failing Item:
16-bitmode. Have the customer verify the driver v NEXTLVL
software level.
Failing Item: BF776505 BF776505
v IOADPTR
Explanation: Conflicting rx_coalesce_ticks (0) and
rx_max_coalesce_frames(0) parameters.
BF776500 BF776500
Problem determination:
Explanation: Unable to find or create the directory 1. Change the rx_coalesce_ticks parameter of the
under /proc/net.Have the customer verify that procfs driver
is supported by the kernel.
2. Change the rx_max_coalesce_frames parameter of
Failing Item: the driver
v NEXTLVL Failing Item:
v NEXTLVL
BF776501 BF776501
Explanation: Insufficient kernel memory available for BF776506 BF776506
allocation.
Explanation: Conflicting tx_coalesce_ticks (0) and
Problem determination: tx_max_coalesce_frames(0) parameters.
v Increase the memory on the system Problem determination:
v Install the driver earlier in system bringup 1. Change the tx_coalesce_ticks parameter of the
Failing Item: driver
v NEXTLVL 2. Change the tx_max_coalesce_frames parameter of
the driver
BF776502 BF776502 Failing Item:
v NEXTLVL
Explanation: The driver was unable to use either
64-bit or 32-bitDMA. Have the customer verify driver
software level. BF776507 BF776507
Failing Item: Explanation: The value given to the
v NEXTLVL stats_coalesce_ticks parameteris invalid. Have the
customer change the stats_coalesce_ticks parameter of
the driver.
BF776503 BF776503
Failing Item:
Explanation: Linux does not support a hardware
v NEXTLVL
feature which has been enabled. Run diagnostics to
disable Turbo Teaming.
BF776800 BF776800
Failing Item:
v NEXTLVL Explanation: Either this adapter or the system does
not allow theuse of adapter based transmit descriptors.
Problem determination:
1. Verify the driver software level
2. Change the nic_tx_bd parameter
(BF77) Reference codes 685
BF776801 • BF777E01
Failing Item: v IOADPTR
v NEXTLVL
BF777800 BF777800
BF776801 BF776801 Explanation: Internal error in driver, kernel, or
Explanation: This adapter does not support hardware firmware.
checksum offload. Problem determination:
Problem determination: 1. Verify the driver software level.
1. Verify the driver software level 2. Run diagnostics.
2. Change the driver's rx_checksum parameter Failing Item:
3. Change the driver's tx_checksum parameter v NEXTLVL
Failing Item:
v NEXTLVL BF777801 BF777801
Explanation: Insufficient kernel memory is available
BF776802 BF776802 for the driver.
Explanation: This adapter does not support hardware Problem determination:
TSO. 1. Install more memory in the system
Problem determination: 2. Reconfigure the kernel to reduce memory
1. Verify the driver software level consumption
2. Change the driver's enable_tso parameter 3. Install the driver earlier in system bringup
Failing Item: Failing Item:
v NEXTLVL v NEXTLVL
BF776A00 BF776A00 BF777802 BF777802
Explanation: This adapter hardware does not support Explanation: Internal error in driver, kernel, or
frames sizesover 1500 bytes. Have the customer verify firmware.
the driver software level. If you replace the adapter, use Problem determination:
one that offers additional capablities
1. Verify the driver software level
Failing Item: 2. Run diagnostics
v IOADPTR
Failing Item:
v NEXTLVL
BF776F00 BF776F00
Explanation: Unable to read the adapter's NVRAM. BF777E00 BF777E00
Have the customerverify the driver software level
Explanation: Not enough memory for the driver.
Failing Item: Unable to initialize(or reinitialize) the adapter card.
v IOADPTR
Problem determination:
1. Verify the driver software level
BF776F01 BF776F01
2. Reconfigure the kernel to reduce memory
Explanation: Cannot get MAC addr from NVRAM. consumption, then reboot
Have the customerverify the driver software level
Failing Item:
Failing Item: v IOADPTR
v IOADPTR
BF777E01 BF777E01
BF776F02 BF776F02
Explanation: The BIOS has assigned conflicting
Explanation: Unable to read PCI Config space or address spaces todifferent devices.
NVRAM. Have thecustomer verify the driver software
Problem determination:
level
1. Run diagnostics
Failing Item:
2. Upgrade the BIOS
686 System reference codes (Bxxx)
BF777E02 • BF778F00
Failing Item:
BF778E01 BF778E01
v IOADPTR
Explanation: Unable to access PCI data area for
checksum value. However,the device id is valid.
BF777E02 BF777E02
Problem determination:
Explanation: The driver requested a DMA
v Verify the driver software level
configuration that your systemdoes not support.
v Run diagnostics
Problem determination:
v Replace board
1. Verify the driver software level
Failing Item:
2. Run diagnostics
v NEXTLVL
Failing Item:
v IOADPTR
BF778E02 BF778E02
Explanation: The MAC type is not ethernet as
BF777E03 BF777E03
expected.
Explanation: The adapter's MAC address is not a
Problem determination:
valid Ethernet address.
v Verify the driver software level
Problem determination:
v Run diagnostics
1. Verify the driver software level
Failing Item:
2. Run diagnostics
v IOADPTR
Failing Item:
v IOADPTR
BF778F00 BF778F00
Explanation: Adapter hardware failure.
BF777F00 BF777F00
Failing Item:
Explanation: The EEPROM on the network adapter
may be corrupted. v IOADPTR
Failing Item:
v IOADPTR
BF777F01 BF777F01
Explanation: The driver cannot enable the adapter as
a PCI device.
Failing Item:
v IOADPTR
BF777F02 BF777F02
Explanation: The network adapter failed its self-test.
Failing Item:
v IOADPTR
BF778E00 BF778E00
Explanation: Cannot enable DMA for either 32 bits or
64 bits.
Failing Item:
v NEXTLVL
(BF77) Reference codes 687
688 System reference codes (Bxxx)
Notices
This information was developed for products and services offered in the U.S.A.
The manufacturer may not offer the products, services, or features discussed in this document in other
countries. Consult the manufacturer's representative for information on the products and services
currently available in your area. Any reference to the manufacturer's product, program, or service is not
intended to state or imply that only that product, program, or service may be used. Any functionally
equivalent product, program, or service that does not infringe any intellectual property right of the
manufacturer may be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any product, program, or service.
The manufacturer may have patents or pending patent applications covering subject matter described in
this document. The furnishing of this document does not grant you any license to these patents. You can
send license inquiries, in writing, to the manufacturer.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: THIS PUBLICATION IS PROVIDED “AS IS” WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
The manufacturer may make improvements and/or changes in the product(s) and/or the program(s)
described in this publication at any time without notice.
Any references in this information to websites not owned by the manufacturer are provided for
convenience only and do not in any manner serve as an endorsement of those websites. The materials at
those websites are not part of the materials for this product and use of those websites is at your own risk.
The manufacturer may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
been made on development-level systems and there is no guarantee that these measurements will be the
same on generally available systems. Furthermore, some measurements may have been estimated through
extrapolation. Actual results may vary. Users of this document should verify the applicable data for their
specific environment.
Information concerning products not produced by this manufacturer was obtained from the suppliers of
those products, their published announcements or other publicly available sources. This manufacturer has
not tested those products and cannot confirm the accuracy of performance, compatibility or any other
claims related to products not produced by this manufacturer. Questions on the capabilities of products
not produced by this manufacturer should be addressed to the suppliers of those products.
All statements regarding the manufacturer's future direction or intent are subject to change or withdrawal
without notice, and represent goals and objectives only.
The manufacturer's prices shown are the manufacturer's suggested retail prices, are current and are
subject to change without notice. Dealer prices may vary.
© Copyright IBM Corp. 2010, 2013 689
This information is for planning purposes only. The information herein is subject to change before the
products described become available.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental.
If you are viewing this information in softcopy, the photographs and color illustrations may not appear.
The drawings and specifications contained herein shall not be reproduced in whole or in part without the
written permission of the manufacturer.
The manufacturer has prepared this information for use with the specific machines indicated. The
manufacturer makes no representations that it is suitable for any other purpose.
The manufacturer's computer systems contain mechanisms designed to reduce the possibility of
undetected data corruption or loss. This risk, however, cannot be eliminated. Users who experience
unplanned outages, system failures, power fluctuations or outages, or component failures must verify the
accuracy of operations performed and data saved or transmitted by the system at or near the time of the
outage or failure. In addition, users must establish procedures to ensure that there is independent data
verification before relying on such data in sensitive or critical operations. Users should periodically check
the manufacturer's support websites for updated information and fixes applicable to the system and
related software.
Homologation statement
This product may not be certified in your country for connection by any means whatsoever to interfaces
of public telecommunications networks. Further certification may be required by law prior to making any
such connection. Contact an IBM representative or reseller for any questions.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at
Copyright and trademark information at www.ibm.com/legal/copytrade.shtml.
INFINIBAND, InfiniBand Trade Association, and the INFINIBAND design marks are trademarks and/or
service marks of the INFINIBAND Trade Association.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or
its affiliates.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Electronic emission notices
When attaching a monitor to the equipment, you must use the designated monitor cable and any
interference suppression devices supplied with the monitor.
690 System reference codes (Bxxx)
Class A Notices
The following Class A statements apply to the IBM servers that contain the POWER7® processor and its
features unless designated as electromagnetic compatibility (EMC) Class B in the feature information.
Federal Communications Commission (FCC) statement
Note: This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with
the instruction manual, may cause harmful interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful interference, in which case the user will be
required to correct the interference at his own expense.
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission
limits. IBM is not responsible for any radio or television interference caused by using other than
recommended cables and connectors or by unauthorized changes or modifications to this equipment.
Unauthorized changes or modifications could void the user's authority to operate the equipment.
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and (2) this device must accept any interference
received, including interference that may cause undesired operation.
Industry Canada Compliance Statement
This Class A digital apparatus complies with Canadian ICES-003.
Avis de conformité à la réglementation d'Industrie Canada
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
European Community Compliance Statement
This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on
the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot
accept responsibility for any failure to satisfy the protection requirements resulting from a
non-recommended modification of the product, including the fitting of non-IBM option cards.
This product has been tested and found to comply with the limits for Class A Information Technology
Equipment according to European Standard EN 55022. The limits for Class A equipment were derived for
commercial and industrial environments to provide reasonable protection against interference with
licensed communication equipment.
European Community contact:
IBM Deutschland GmbH
Technical Regulations, Department M372
IBM-Allee 1, 71139 Ehningen, Germany
Tele: +49 7032 15 2941
email: lugi@de.ibm.com
Warning: This is a Class A product. In a domestic environment, this product may cause radio
interference, in which case the user may be required to take adequate measures.
Notices 691
VCCI Statement - Japan
The following is a summary of the VCCI Japanese statement in the box above:
This is a Class A product based on the standard of the VCCI Council. If this equipment is used in a
domestic environment, radio interference may occur, in which case, the user may be required to take
corrective actions.
Japanese Electronics and Information Technology Industries Association (JEITA)
Confirmed Harmonics Guideline (products less than or equal to 20 A per phase)
Japanese Electronics and Information Technology Industries Association (JEITA)
Confirmed Harmonics Guideline with Modifications (products greater than 20 A per
phase)
Electromagnetic Interference (EMI) Statement - People's Republic of China
Declaration: This is a Class A product. In a domestic environment this product may cause radio
interference in which case the user may need to perform practical action.
692 System reference codes (Bxxx)
Electromagnetic Interference (EMI) Statement - Taiwan
The following is a summary of the EMI Taiwan statement above.
Warning: This is a Class A product. In a domestic environment this product may cause radio interference
in which case the user will be required to take adequate measures.
IBM Taiwan Contact Information:
Electromagnetic Interference (EMI) Statement - Korea
Germany Compliance Statement
Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse A EU-Richtlinie zur
Elektromagnetischen Verträglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der
Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaaten und hält die
Grenzwerte der EN 55022 Klasse A ein.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu
betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM
übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne
Zustimmung von IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne
Empfehlung von IBM gesteckt/eingebaut werden.
Notices 693
EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden:
"Warnung: Dieses ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich
Funk-Störungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene
Maßnahmen zu ergreifen und dafür aufzukommen."
Deutschland: Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit von Geräten
(EMVG)“. Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von
Geräten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse A
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen
- CE - zu führen.
Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller:
International Business Machines Corp.
New Orchard Road
Armonk, New York 10504
Tel: 914-499-1900
Der verantwortliche Ansprechpartner des Herstellers in der EU ist:
IBM Deutschland GmbH
Technical Regulations, Abteilung M372
IBM-Allee 1, 71139 Ehningen, Germany
Tel: +49 7032 15 2941
email: lugi@de.ibm.com
Generelle Informationen:
Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse A.
Electromagnetic Interference (EMI) Statement - Russia
Class B Notices
The following Class B statements apply to features designated as electromagnetic compatibility (EMC)
Class B in the feature installation information.
Federal Communications Commission (FCC) statement
This equipment has been tested and found to comply with the limits for a Class B digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference in a residential installation.
694 System reference codes (Bxxx)
This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instructions, may cause harmful interference to radio communications. However,
there is no guarantee that interference will not occur in a particular installation.
If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the interference
by one or more of the following measures:
v Reorient or relocate the receiving antenna.
v Increase the separation between the equipment and receiver.
v Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
v Consult an IBM-authorized dealer or service representative for help.
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission
limits. Proper cables and connectors are available from IBM-authorized dealers. IBM is not responsible for
any radio or television interference caused by unauthorized changes or modifications to this equipment.
Unauthorized changes or modifications could void the user's authority to operate this equipment.
This device complies with Part 15 of the FCC rules. Operation is subject to the following two conditions:
(1) this device may not cause harmful interference, and (2) this device must accept any interference
received, including interference that may cause undesired operation.
Industry Canada Compliance Statement
This Class B digital apparatus complies with Canadian ICES-003.
Avis de conformité à la réglementation d'Industrie Canada
Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada.
European Community Compliance Statement
This product is in conformity with the protection requirements of EU Council Directive 2004/108/EC on
the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot
accept responsibility for any failure to satisfy the protection requirements resulting from a
non-recommended modification of the product, including the fitting of non-IBM option cards.
This product has been tested and found to comply with the limits for Class B Information Technology
Equipment according to European Standard EN 55022. The limits for Class B equipment were derived for
typical residential environments to provide reasonable protection against interference with licensed
communication equipment.
European Community contact:
IBM Deutschland GmbH
Technical Regulations, Department M372
IBM-Allee 1, 71139 Ehningen, Germany
Tele: +49 7032 15 2941
email: lugi@de.ibm.com
Notices 695
VCCI Statement - Japan
Japanese Electronics and Information Technology Industries Association (JEITA)
Confirmed Harmonics Guideline (products less than or equal to 20 A per phase)
Japanese Electronics and Information Technology Industries Association (JEITA)
Confirmed Harmonics Guideline with Modifications (products greater than 20 A per
phase)
IBM Taiwan Contact Information
Electromagnetic Interference (EMI) Statement - Korea
Germany Compliance Statement
Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse B EU-Richtlinie zur
Elektromagnetischen Verträglichkeit
696 System reference codes (Bxxx)
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2004/108/EG zur Angleichung der
Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaaten und hält die
Grenzwerte der EN 55022 Klasse B ein.
Um dieses sicherzustellen, sind die Geräte wie in den Handbüchern beschrieben zu installieren und zu
betreiben. Des Weiteren dürfen auch nur von der IBM empfohlene Kabel angeschlossen werden. IBM
übernimmt keine Verantwortung für die Einhaltung der Schutzanforderungen, wenn das Produkt ohne
Zustimmung von IBM verändert bzw. wenn Erweiterungskomponenten von Fremdherstellern ohne
Empfehlung von IBM gesteckt/eingebaut werden.
Deutschland: Einhaltung des Gesetzes über die elektromagnetische Verträglichkeit von Geräten
Dieses Produkt entspricht dem “Gesetz über die elektromagnetische Verträglichkeit von Geräten
(EMVG)“. Dies ist die Umsetzung der EU-Richtlinie 2004/108/EG in der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von
Geräten (EMVG) (bzw. der EMC EG Richtlinie 2004/108/EG) für Geräte der Klasse B
Dieses Gerät ist berechtigt, in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen
- CE - zu führen.
Verantwortlich für die Einhaltung der EMV Vorschriften ist der Hersteller:
International Business Machines Corp.
New Orchard Road
Armonk, New York 10504
Tel: 914-499-1900
Der verantwortliche Ansprechpartner des Herstellers in der EU ist:
IBM Deutschland GmbH
Technical Regulations, Abteilung M372
IBM-Allee 1, 71139 Ehningen, Germany
Tel: +49 7032 15 2941
email: lugi@de.ibm.com
Generelle Informationen:
Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 Klasse B.
Terms and conditions
Permissions for the use of these publications are granted subject to the following terms and conditions.
Applicability: These terms and conditions are in addition to any terms of use for the IBM website.
Personal Use: You may reproduce these publications for your personal, noncommercial use provided that
all proprietary notices are preserved. You may not distribute, display or make derivative works of these
publications, or any portion thereof, without the express consent of IBM.
Commercial Use: You may reproduce, distribute and display these publications solely within your
enterprise provided that all proprietary notices are preserved. You may not make derivative works of
these publications, or reproduce, distribute or display these publications or any portion thereof outside
your enterprise, without the express consent of IBM.
Rights: Except as expressly granted in this permission, no other permissions, licenses or rights are
granted, either express or implied, to the Publications or any information, data, software or other
intellectual property contained therein.
Notices 697
IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of
the publications is detrimental to its interest or, as determined by IBM, the above instructions are not
being properly followed.
You may not download, export or re-export this information except in full compliance with all applicable
laws and regulations, including all United States export laws and regulations.
IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE
PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF
MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE.
698 System reference codes (Bxxx)
Printed in USA
You might also like
- GE - 700-800T Advanced Service Manual - ASM100% (7)GE - 700-800T Advanced Service Manual - ASM224 pages
- Aquaponic Design Plans Everything You Needs to Know: Everything You Need to Know from Backyard to Profitable BusinessFrom EverandAquaponic Design Plans Everything You Needs to Know: Everything You Need to Know from Backyard to Profitable BusinessNo ratings yet
- GEHC Service Manual - PROCARE B40 B20 Monitor PDF75% (4)GEHC Service Manual - PROCARE B40 B20 Monitor PDF252 pages
- Diferentes Tipos de Erros Nos Servidores Powers e HMCNo ratings yetDiferentes Tipos de Erros Nos Servidores Powers e HMC738 pages
- GX Works2 Ver1 - Operating Manual (Simple Project, Function Block) SH (NA) - 080984-D (09.12)0% (1)GX Works2 Ver1 - Operating Manual (Simple Project, Function Block) SH (NA) - 080984-D (09.12)102 pages
- Fdocuments - in - Gehc Service Manual Procare b40 b20 Monitor PDF100% (1)Fdocuments - in - Gehc Service Manual Procare b40 b20 Monitor PDF252 pages
- En ACS800 07-17-37 Cab Options A ScrresNo ratings yetEn ACS800 07-17-37 Cab Options A Scrres42 pages
- ACS380 Machinery Control Program: Firmware Manual100% (1)ACS380 Machinery Control Program: Firmware Manual568 pages
- GE Healthcare ProCare B20-B40 Patient Monitor Manual Discount CardiologyNo ratings yetGE Healthcare ProCare B20-B40 Patient Monitor Manual Discount Cardiology252 pages
- GX Simulator - Operating Manual - Sh080468engkNo ratings yetGX Simulator - Operating Manual - Sh080468engk268 pages
- Wire Processing Software For Ecostrip 9380: Reference ManualNo ratings yetWire Processing Software For Ecostrip 9380: Reference Manual192 pages
- Firmware Manual: ACS380 Machinery Control ProgramNo ratings yetFirmware Manual: ACS380 Machinery Control Program542 pages
- Programming Manual: For Personal ComputerNo ratings yetProgramming Manual: For Personal Computer236 pages
- FX5 ProgrammingManual Instructions-StandardFunctions-FunctionBlocks JY997D55801-HNo ratings yetFX5 ProgrammingManual Instructions-StandardFunctions-FunctionBlocks JY997D55801-H1,096 pages
- Operation Manual: For XP2i Digital Test Gauge (Standard and Dual-Display (DD) )No ratings yetOperation Manual: For XP2i Digital Test Gauge (Standard and Dual-Display (DD) )42 pages
- Gsr7 Half Rate: Installation & Configuration Bss OptimizationNo ratings yetGsr7 Half Rate: Installation & Configuration Bss Optimization433 pages
- Futros720 s920 Esprimo A525l Operating Manual 112017 1206702No ratings yetFutros720 s920 Esprimo A525l Operating Manual 112017 120670271 pages
- Aquaponics Design Plans, Construction, Operation, and Income: Organic FoodFrom EverandAquaponics Design Plans, Construction, Operation, and Income: Organic FoodNo ratings yet
- Users Guide: Wyse USB Firmware Tool 1.19.0.4No ratings yetUsers Guide: Wyse USB Firmware Tool 1.19.0.434 pages
- Design, Construction, and Operation of A Small Homemade Wind Turbine BladesNo ratings yetDesign, Construction, and Operation of A Small Homemade Wind Turbine Blades49 pages
- Design of Naca63215 Airfoil For A Wind Turbine: N.Manikandan, B.StalinNo ratings yetDesign of Naca63215 Airfoil For A Wind Turbine: N.Manikandan, B.Stalin9 pages
- E3533s-2TCPU-22.318.23.00.00 Release Notes: Huawei Technologies Co., LTDNo ratings yetE3533s-2TCPU-22.318.23.00.00 Release Notes: Huawei Technologies Co., LTD7 pages
- Production & Industrial Pumps Operating & Service ManualNo ratings yetProduction & Industrial Pumps Operating & Service Manual71 pages
- JE-H (ST) HRH: BD Fire Warning Cable, FE 180/E 30 To E 90, Halogen-FreeNo ratings yetJE-H (ST) HRH: BD Fire Warning Cable, FE 180/E 30 To E 90, Halogen-Free1 page
- Fanuc I/O Unit-Model A: Connection and Maintenance ManualNo ratings yetFanuc I/O Unit-Model A: Connection and Maintenance Manual246 pages
- Cisco Wireless Solutions Software Compatibility Matrix - CiscoNo ratings yetCisco Wireless Solutions Software Compatibility Matrix - Cisco1 page
- Wind Load Provisions and Steel Specifications For Russia100% (1)Wind Load Provisions and Steel Specifications For Russia10 pages
- As 1288-2006 Glass in Buildings - Selection and Installation0% (2)As 1288-2006 Glass in Buildings - Selection and Installation10 pages
- VG-6653 Manual Call Point - QCD 05-2026.No ratings yetVG-6653 Manual Call Point - QCD 05-2026.2 pages