P9eai src1

Power Systems
System reference codes (1xxx - Axxx)
IBM
Power Systems
System reference codes (1xxx - Axxx)
IBM
Note
Before using this information and the product it supports, read the information in “Safety notices” on page ix, “Notices” on
page 1105, the IBM Systems Safety Notices manual, G229-9054, and the IBM Environmental Notices and User Guide, Z125–5823.
This edition applies to IBM Power Systems™ servers that contain the POWER9™ processor and to all associated
models.
© Copyright IBM Corporation 2018.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Safety notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
System reference codes (1xxx - Axxx) overview . . . . . . . . . . . . . . . . . . 1

Block replacement of FRUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
(1000) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
(1100) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
(169C) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
(1750) Reference codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
(198B) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
(198D) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
(198E) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
(19A1) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
(19B0) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
(2058) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
(2105) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
(2107) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
(2145) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
(266F) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
(2689) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
(2742) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
(2743) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
(2744) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
(2745) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
(2746) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
(2749) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
(2757) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
(2760) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
(2763) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
(2765) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
(2766) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
(2767) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
(2768) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
(2771) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
(2772) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
(2782) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
(2787) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
(2793) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
(2805) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
(2838) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
(2842) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
(2843) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
© Copyright IBM Corp. 2018 iii

(2844) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
(2847) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
(2849) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
(2875) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
(2876) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
(2890) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
(2892) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
(28CB) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
(28CC) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
(2B0F) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
(2B4C) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
(2B5A) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
(2B9B) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
(2BBE) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
(2BD6) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
(2BE0) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
(2BE1) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
(2BF3) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
(2BF4) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
(2C4C) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
(2C4D) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
(2CE3) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
(2CE4) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
(2CEC) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
(2D34) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
(3494) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
(3580) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
(3592) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
(4320) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
(4322) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
(4323) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
(4325) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
(4326) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
(4327) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
(4328) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
(4329) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
(4685) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
(4758) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
(4764) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
(4765) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
(4812) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
iv Power Systems: System reference codes (1xxx - Axxx)

(509A) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372
(50AD) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
(5619) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
(5638) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
(5675) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
(5700) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
(5701) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
(5702) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
(5703) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
(5704) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
(5706) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
(5707) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
(5708) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
(5709) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
(5746) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
(5755) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
(5767) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
(5768) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
(5774) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
(57BB) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
(57C3) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
(57CB) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Contents v
(57CD) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
(57CE) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
(57CF) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
(57FC) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
(57FE) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
(57FF) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
(58BB) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
(58F8) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
(58FA) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
(58FB) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
(5907) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
(59BE) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
(59CD) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
(59CE) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
(59CF) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
(59DA) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 784
(59DB) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787
(59DD) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
(59DE) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
(59E0) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 796
(59EA) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
(59EB) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
(59FC) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
(59FD) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
(5B0E) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
(5B0F) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
vi Power Systems: System reference codes (1xxx - Axxx)

(5B1A) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
(5B2D) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 890
(6258) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
(6279) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
(6320) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
(6321) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
(6330) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
(6331) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
(6333) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947
(6336) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
(6337) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953
(6382) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
(6383) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
(6384) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965
(6386) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
(6387) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
(63BC) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
(6600) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
(6607) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
(6713) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
(6714) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
(6717) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
(6718) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
(6719) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
(7207) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
(9429) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
Contents vii
(A1xx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
(AAxx) Reference codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105
Accessibility features for IBM Power Systems servers. . . . . . . . . . . . . . . . . . . . . 1106
Privacy policy considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107
Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
Electronic emission notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
Class A Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
Class B Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
Terms and conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
viii Power Systems: System reference codes (1xxx - Axxx)

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.
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 If IBM supplied the power cord(s), 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.
– For AC power, disconnect all power cords from their AC power source.
– For racks with a DC power distribution panel (PDP), disconnect the customer’s DC power source to
the PDP.
v When connecting power to the product ensure all power cables are properly connected.
© Copyright IBM Corp. 2018 ix

– For racks with AC power, 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.
– For racks with a DC power distribution panel (PDP), connect the customer’s DC power source to
the PDP. Ensure that the proper polarity is used when attaching the DC power and DC power
return wiring.
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 Do not attempt to switch on power to the machine until all possible unsafe conditions are corrected.
v Assume that an electrical safety hazard is present. Perform all continuity, grounding, and power checks
specified during the subsystem installation procedures to ensure that the machine meets safety
requirements.
v Do not continue with the inspection if any unsafe conditions are present.
v Before you open the device covers, unless instructed otherwise in the installation and configuration
procedures: Disconnect the attached AC power cords, turn off the applicable circuit breakers located in
the rack power distribution panel (PDP), and disconnect any telecommunications systems, networks,
and modems.
DANGER:
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. For AC power, remove the power cords from the outlets.
3. For racks with a DC power distribution panel (PDP), turn off the circuit breakers located in the
PDP and remove the power from the Customer's DC power source.
4. Remove the signal cables from the connectors.
5. 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. For AC power, attach the power cords to the outlets.
5. For racks with a DC power distribution panel (PDP), restore the power from the Customer's DC
power source and turn on the circuit breakers located in the PDP.
6. Turn on the devices.
Sharp edges, corners and joints may be present in and around the system. Use care when handling
equipment to avoid cuts, scrapes and pinching. (D005)
(R001 part 1 of 2):
DANGER: 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. In addition, do not lean on rack mounted devices and do not use them to
stabilize your body position (for example, when working from a ladder).
x Power Systems: System reference codes (1xxx - Axxx)

v Each rack cabinet might have more than one power cord.
– For AC powered racks, be sure to disconnect all power cords in the rack cabinet when directed to
disconnect power during servicing.
– For racks with a DC power distribution panel (PDP), turn off the circuit breaker that controls the
power to the system unit(s), or disconnect the customer’s DC power source, 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.
(R001 part 2 of 2):
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.
Safety notices xi
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 (compliance ID RACK-001 or 22U (compliance ID RR001)
and above.
– Ensure that the heaviest devices are installed in the bottom of the rack cabinet.
– Ensure that there are little-to-no empty U-levels between devices installed in the rack cabinet
below the 32U (compliance ID RACK-001 or 22U (compliance ID RR001) level, unless the
received configuration specifically allowed it.
v If the rack cabinet you are relocating is part of a suite of rack cabinets, detach the rack cabinet from
the suite.
v If the rack cabinet you are relocating was supplied with removable outriggers they must be
reinstalled before the cabinet is relocated.
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)
DANGER: Hazardous voltage, current, or energy levels are present inside any component that has this
label attached. Do not open any cover or barrier that contains this label. (L001)
(L002)
xii Power Systems: System reference codes (1xxx - Axxx)

DANGER: Rack-mounted devices are not to be used as shelves or work spaces. (L002)
(L003)
1 2
or
!
1
or
3 4
1 2
or
Safety notices xiii

1
2
3
4
or
DANGER: Multiple power cords. The product might be equipped with multiple AC power cords or
multiple DC power cables. To remove all hazardous voltages, disconnect all power cords and power
cables. (L003)
(L007)
CAUTION: A hot surface nearby. (L007)
(L008)
xiv Power Systems: System reference codes (1xxx - Axxx)

CAUTION: Hazardous moving parts nearby. (L008)
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)
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. Although shining light into one end and looking into the other end of
a disconnected optical fiber to verify the continuity of optic fibers may not injure the eye, this
procedure is potentially dangerous. Therefore, verifying the continuity of optical fibers by shining
light into one end and looking at the other end is not recommended. To verify continuity of a fiber
optic cable, use an optical light source and power meter. (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)
Safety notices xv
CAUTION:
Regarding IBM provided VENDOR LIFT TOOL:
v Operation of LIFT TOOL by authorized personnel only.
v LIFT TOOL intended for use to assist, lift, install, remove units (load) up into rack elevations. It is
not to be used loaded transporting over major ramps nor as a replacement for such designated tools
like pallet jacks, walkies, fork trucks and such related relocation practices. When this is not
practicable, specially trained persons or services must be used (for instance, riggers or movers).
v Read and completely understand the contents of LIFT TOOL operator's manual before using.
Failure to read, understand, obey safety rules, and follow instructions may result in property
damage and/or personal injury. If there are questions, contact the vendor's service and support.
Local paper manual must remain with machine in provided storage sleeve area. Latest revision
manual available on vendor's web site.
v Test verify stabilizer brake function before each use. Do not over-force moving or rolling the LIFT
TOOL with stabilizer brake engaged.
v Do not move LIFT TOOL while platform is raised, except for minor positioning.
v Do not exceed rated load capacity. See LOAD CAPACITY CHART regarding maximum loads at
center versus edge of extended platform.
v Only raise load if properly centered on platform. Do not place more than 200 lb (91 kg) on edge of
sliding platform shelf also considering the load's center of mass/gravity (CoG).
v Do not corner load the platform tilt riser accessory option. Secure platform riser tilt option to main
shelf in all four (4x) locations with provided hardware only, prior to use. Load objects are designed
to slide on/off smooth platforms without appreciable force, so take care not to push or lean. Keep
riser tilt option flat at all times except for final minor adjustment when needed.
v Do not stand under overhanging load.
v Do not use on uneven surface, incline or decline (major ramps).
v Do not stack loads.
v Do not operate while under the influence of drugs or alcohol.
v Do not support ladder against LIFT TOOL.
v Tipping hazard. Do not push or lean against load with raised platform.
v Do not use as a personnel lifting platform or step. No riders.
v Do not stand on any part of lift. Not a step.
v Do not climb on mast.
v Do not operate a damaged or malfunctioning LIFT TOOL machine.
v Crush and pinch point hazard below platform. Only lower load in areas clear of personnel and
obstructions. Keep hands and feet clear during operation.
v No Forks. Never lift or move bare LIFT TOOL MACHINE with pallet truck, jack or fork lift.
v Mast extends higher than platform. Be aware of ceiling height, cable trays, sprinklers, lights, and
other overhead objects.
v Do not leave LIFT TOOL machine unattended with an elevated load.
v Watch and keep hands, fingers, and clothing clear when equipment is in motion.
v Turn Winch with hand power only. If winch handle cannot be cranked easily with one hand, it is
probably over-loaded. Do not continue to turn winch past top or bottom of platform travel.
Excessive unwinding will detach handle and damage cable. Always hold handle when lowering,
unwinding. Always assure self that winch is holding load before releasing winch handle.
v A winch accident could cause serious injury. Not for moving humans. Make certain clicking sound
is heard as the equipment is being raised. Be sure winch is locked in position before releasing
handle. Read instruction page before operating this winch. Never allow winch to unwind freely.
Freewheeling will cause uneven cable wrapping around winch drum, damage cable, and may cause
serious injury. (C048)
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:
xvi Power Systems: System reference codes (1xxx - Axxx)

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.
The dc-powered system is intended to be installed in a common bonding network (CBN) as described in
GR-1089-CORE.
Safety notices xvii

xviii Power Systems: System reference codes (1xxx - Axxx)
System reference codes (1xxx - Axxx) 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.
(1000) Reference codes

are required. Otherwise, use the FRU and procedure
100000AC
callouts detailed with the SRC to determine service
Explanation: An AC loss was detected. actions.
Response: If this is a tracking event, no service actions Problem determination: The system may have
© Copyright IBM Corp. 2018 1

100000C6 • 10001510
experienced an AC Power Loss external to the system

10001300
such as utility or building power and the sy stem may
have recovered. Explanation: Power Supply power fault (PS1)
1. If there was a utility, building or room power loss Response: If this is a tracking event, no service actions
that would have affected the system at the same are required. Otherwise, use the FRU and procedure
time this SRC was reported then you can ignore callouts detailed with the SRC to determine service
and close this event. No service is required. actions.
Otherwise continue with the next step in this
procedure.
10001301
2. Ensure the line cords are properly connected and
seated on both ends. For help in locating the line Explanation: Power Supply power fault (PS2)
cords of the power supply reporting thi s problem
use the location code in the serviceable event or the Response: If this is a tracking event, no service actions
symbolic FRU in the failing items list below. are required. Otherwise, use the FRU and procedure
3. If the system was just installed or moved, verify the actions.
AC input voltage is correct.
4. If the problem is not resolved then report this
problem to your service provider. 10001400
Explanation: Domain Fault allocated to node (PS1)
100000C6 Response: If this is a tracking event, no service actions
Explanation: The PCIe3 expansion drawer has are required. Otherwise, use the FRU and procedure
powered on. callouts detailed with the SRC to determine service
actions.
Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service 10001401
actions. Explanation: Domain Fault allocated to node (PS2)
100000EF are required. Otherwise, use the FRU and procedure
Explanation: An emergency power off occurred. callouts detailed with the SRC to determine service
actions.
actions. Explanation: Power Supply AC fault (PS1)
10001100 are required. Otherwise, use the FRU and procedure
Explanation: Power Supply non power fault (PS1) callouts detailed with the SRC to determine service
actions.
10001101 are required. Otherwise, use the FRU and procedure
Explanation: Power Supply non power fault (PS2) callouts detailed with the SRC to determine service
actions.
actions.
Failing Item:
2 Power Systems: System reference codes (1xxx - Axxx)

10001511 • 10001526
v PWRSPLY
10001520
v TWRCARD
Explanation: Power Supply AC fault (PS2)
10001511 Response: The FRU callouts are calculated at the time

of the failure. See the error log for the actual
Explanation: Power Supply power fault (PS1) replacement strategy.
Response: If this is a tracking event, no service actions Failing Item:
v PWRSPLY
actions. v TWRCARD
Failing Item:
10001521
v PWRSPLY
v TWRCARD Explanation: Power Supply power fault (PS2)
Response: The FRU callouts are calculated at the time
10001512 of the failure. See the error log for the actual
replacement strategy.
Explanation: Power Supply non power fault (PS1)
Failing Item:
v PWRSPLY
callouts detailed with the SRC to determine service v TWRCARD
actions.
Failing Item: 10001522
v PWRSPLY Explanation: Power Supply non power fault (PS2)
v TWRCARD Response: The FRU callouts are calculated at the time
v CBLALL of the failure. See the error log for the actual
10001513 Failing Item:
Explanation: Domain Fault allocated to node (PS1) v PWRSPLY
v TWRCARD
of the failure. See the error log for the actual v CBLALL
v PWRSPLY Explanation: Domain Fault allocated to node (PS2)
10001516 replacement strategy.
Explanation: Power Supply missing (PS1) Failing Item:

v PWRSPLY
of the failure. See the error log for the actual v TWRCARD
v PWRSPLY Explanation: Power Supply missing (PS2)
1000151F replacement strategy.
Explanation: Fan Fault - PS1 MPS fault bit set Failing Item:
v PWRSPLY
of the failure. See the error log for the actual v TWRCARD
System reference codes (1xxx - Axxx) overview 3

1000152F • 10002641
1000152F 10002611
Explanation: Fan Fault - PS2 MPS fault bit set Explanation: P2 IO Bay VRM not plugged
Response: The FRU callouts are calculated at the time Response: If this is a tracking event, no service actions
of the failure. See the error log for the actual are required. Otherwise, use the FRU and procedure
replacement strategy. callouts detailed with the SRC to determine service
actions.
10001600
10002620
Explanation: Power Supply missing (PS1)
Explanation: P1 IO Bay 3.3VCS Pgood Fault
are required. Otherwise, use the FRU and procedure Response: If this is a tracking event, no service actions
callouts detailed with the SRC to determine service are required. Otherwise, use the FRU and procedure
actions. callouts detailed with the SRC to determine service
actions.
10001601
10002621
Explanation: Power Supply missing (PS2)
actions.
10001700
10002630
Explanation: Fan Fault - PS1 MPS fault bit set
Explanation: P1 IO Bay 1.2VCS Module Pgood Fault
actions.
10001701
10002631
Explanation: Fan Fault - PS2 MPS fault bit set
actions.
10001F02
10002640
Explanation: An ILOG threshold was reached.
Explanation: P1 IO Bay 1.2VCS Module B Pgood Fault
actions.
10002610
10002641
Explanation: P1 IO Bay VRM not plugged
actions.

10002650 • 100026B1
10002650 10002681
Explanation: P1 IO Bay 12V SS PGood Fault Explanation: P2 IO Bay 1.0V Pgood Fault B
Response: If this is a tracking event, no service actions Response: If this is a tracking event, no service actions
are required. Otherwise, use the FRU and procedure are required. Otherwise, use the FRU and procedure
callouts detailed with the SRC to determine service callouts detailed with the SRC to determine service
actions. actions.
10002651 10002690
Explanation: P2 IO Bay 12V SS PGood Fault Explanation: P1 IO Bay VRM is in "N-Mode"
actions. actions.
10002660 10002691
Explanation: P1 IO Bay VRM NON-VCS Pgood Fault Explanation: P2 IO Bay VRM is in "N-Mode"
actions. actions.
10002661 100026A0
Explanation: P2 IO Bay VRM NON-VCS Pgood Fault Explanation: P1 IO Bay VRM is in "N+1 Mode" INFO
actions. actions.
10002670 100026A1
Explanation: P1 IO Bay 1.0V Pgood Fault Explanation: P2 IO Bay VRM is in "N+1 Mode" INFO
actions. actions.
10002671 100026B0
Explanation: P2 IO Bay 1.0V Pgood Fault Explanation: P1 IO Bay VRM is in "N+1 Mode" CRIT
actions. actions.
10002680 100026B1
Explanation: P1 IO Bay 1.0V Pgood Fault B Explanation: P2 IO Bay VRM is in "N+1 Mode" CRIT
actions. actions.

100026C0 • 100026D2
100026C0 100026C7
Explanation: P1 IO Bay voltage regulator module Explanation: P1 IO Bay 1.0V Pgood Fault B
(VRM) not plugged
Response: The FRU callouts are calculated at the time of the failure. See the error log for the actual
of the failure. See the error log for the actual replacement strategy.
100026C8
100026C1
Explanation: P1 IO Bay voltage regulator module
Explanation: P1 IO Bay 3.3VCS Pgood Fault (VRM) is in "N-Mode"
Response: The FRU callouts are calculated at the time Response: The FRU callouts are calculated at the time
of the failure. See the error log for the actual of the failure. See the error log for the actual
replacement strategy. replacement strategy.
100026C2 100026C9
Explanation: P1 IO Bay 1.2VCS Module Pgood Fault Explanation: P1 IO Bay voltage regulator module
(VRM) is in "N+1 Mode" INFO
of the failure. See the error log for the actual Response: The FRU callouts are calculated at the time
replacement strategy. of the failure. See the error log for the actual
100026C3
100026CA
(VRM) is in "N+1 Mode" CRIT
replacement strategy. Response: The FRU callouts are calculated at the time
100026C4
Explanation: P1 IO Bay 12V SS PGood Fault. Please
100026D0
check your PCIE adapter configuration for errors.
(VRM) not plugged
replacement strategy. Response: The FRU callouts are calculated at the time
100026C5
100026D1
(VRM) NON-VCS Pgood Fault
100026C6
100026D2
Explanation: P1 IO Bay 1.0V Pgood Fault

100026D3 • 10003105
100026D3 100026DA
Explanation: P2 IO Bay 1.2VCS Module B Pgood Fault Explanation: P2 IO Bay voltage regulator module
(VRM) is in "N+1 Mode" CRIT
100026D4
10003100
Explanation: P2 IO Bay 12V SS PGood Fault. Please
check your PCIE adapter configuration for errors. Explanation: An I2C bus error occurred.
actions.
100026D5
10003101
(VRM) NON-VCS Pgood Fault Explanation: An I2C bus error occurred.
actions.
100026D6
10003102
Explanation: P2 IO Bay 1.0V Pgood Fault
Explanation: An I2C bus error occurred.
of the failure. See the error log for the actual Response: If this is a tracking event, no service actions
replacement strategy. are required. Otherwise, use the FRU and procedure
actions.
100026D7
Explanation: P2 IO Bay 1.0V Pgood Fault B
10003103
replacement strategy. Response: If this is a tracking event, no service actions
100026D8
actions.
(VRM) is in "N-Mode"
10003104
100026D9
actions.
(VRM) is in "N+1 Mode" INFO
10003105
actions.

10003106 • 10003113
10003106 1000310D
Explanation: An I2C bus error occurred. Explanation: An I2C bus error occurred.
actions. actions.
10003107 1000310E
actions. actions.
10003108 1000310F
actions. actions.
10003109 10003110
actions. actions.
1000310A 10003111
actions. actions.
1000310B 10003112
actions. actions.
1000310C 10003113
actions. actions.

10003114 • 10003121
10003114 1000311B
actions. actions.
10003115 1000311C
actions. actions.
10003116 1000311D
actions. actions.
10003117 1000311E
actions. actions.
10003118 1000311F
actions. actions.
10003119 10003120
actions. actions.
1000311A 10003121
actions. actions.

10003122 • 1000322B
10003122 100031FF
Explanation: An I2C bus error occurred. Explanation: I2C Bus 1 Fault SDA and/or SCL Stuck
Low
actions.
10003123
10003226
actions.
10003124
10003227
actions.
10003125
10003228
actions.
10003140
10003229
Explanation: An I2C device error occurred.
actions.
10003146
1000322A
10003155
actions.
Response: The FRU callouts are calculated at the time 1000322B
actions.

1000322C • 10003239
1000322C 10003233
actions. actions.
1000322D 10003234
actions. actions.
1000322E 10003235
actions. actions.
1000322F 10003236
actions. actions.
10003230 10003237
actions. actions.
10003231 10003238
actions. actions.
10003232 10003239
actions. actions.

1000323A • 10003247
1000323A 10003241
actions. actions.
1000323B 10003242
actions. actions.
1000323C 10003243
actions. actions.
1000323D 10003244
actions. actions.
1000323E 10003245
actions. actions.
1000323F 10003246
actions. actions.
10003240 10003247
actions. actions.

10003248 • 10007600

10003248
actions.
Response: If this is a tracking event, no service actions 10007100
Explanation: Sensor Fault - BMP 180 was detected.
actions. Response: If this is a tracking event, no service actions
10003249
actions.
Response: If this is a tracking event, no service actions 10007201
Explanation: High Temperature Warning
actions. Response: If this is a tracking event, no service actions
100032FF
actions.
Explanation: I2C Bus 2 Fault SDA and/or SCL Stuck
Low
10007202
Explanation: Temperature Warning Reset
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
actions.
1000334A
Explanation: I2C Error device POWER_SUPPLY_1
10007210
Explanation: High Altitude Warning
callouts detailed with the SRC to determine service Response: If this is a tracking event, no service actions
actions. are required. Otherwise, use the FRU and procedure
actions.
100033FF
10007500
Low
Explanation: Fan Controller Fault - ADT 7470 1
actions.
1000344B
10007501
Explanation: I2C Error device POWER_SUPPLY_0
Explanation: Fan Controller Fault - ADT 7470 2
actions.
100034FF
10007600
Low Explanation: Fan Fault - PS1 Fan Rotor 1

10007601 • 10007620
actions. actions.
10007601 10007608
Explanation: Fan Fault - PS1 Fan Rotor 2 Explanation: Fan Fault - System Fan 3, Rotor 1
actions. actions.
10007602 10007609
actions. actions.
10007603 1000760A
actions. actions.
10007604 1000760B
Explanation: Fan Fault - System Fan 1, Rotor 1 Explanation: Fan Fault - System Fan 4, Rotor 2
actions. actions.
10007605 10007610
Explanation: Fan Fault - System Fan 1, Rotor 2 Explanation: Fan Fault - System Fan 1, Rotor 1
Response: If this is a tracking event, no service actions Response: The FRU callouts are calculated at the time
are required. Otherwise, use the FRU and procedure of the failure. See the error log for the actual
callouts detailed with the SRC to determine service replacement strategy.
actions.
10007611
10007606
Explanation: Fan Missing - System Fan 1
Explanation: Fan Fault - System Fan 2, Rotor 1
Response: If this is a tracking event, no service actions of the failure. See the error log for the actual
are required. Otherwise, use the FRU and procedure replacement strategy.
actions.
10007620
10007607
Response: If this is a tracking event, no service actions replacement strategy.

10007621 • 10007901

10007621
actions.
Response: The FRU callouts are calculated at the time 1000770A
10007630
Explanation: Fan Fault - System Fan 3, Rotor 1 actions.
of the failure. See the error log for the actual 10007800
Explanation: Fan Communication Error - PS1 Rotor1.
10007631
Explanation: Fan Missing - System Fan 3 callouts detailed with the SRC to determine service
actions.
replacement strategy. 10007801
10007640
Explanation: Fan Fault - System Fan 4, Rotor 1 are required. Otherwise, use the FRU and procedure
actions.
10007802
10007641 Explanation: Fan Communication Error - PS2 Rotor1.
Explanation: Fan Missing - System Fan 4 Response: If this is a tracking event, no service actions
actions.
10007803
10007704
actions.
actions.
10007900
10007706
Explanation: An I/O module failure was detected.
actions.
10007901
10007708 Explanation: An I/O module was removed with
system powered on. No service action is requred.

10007902 • 10008409
10007902 10008404
Explanation: Unable to determine IO Bay 0 type. Explanation: VRM1 has chkum errors in VPD.
actions.
10007910
10008405
Explanation: An I/O module failure was detected.
Explanation: Midplane has ECC errors or other bad
VPD.
10007911
actions.
Explanation: An I/O module was removed with
system powered on. No service action is required.
10008406
Explanation: IOBAY0 has ECC errors or other bad
VPD.
10007912
Explanation: Unable to determine IO Bay 1 type. actions.
of the failure. See the error log for the actual 10008407
Explanation: IOBAY1 has ECC errors or other bad
VPD.
10008401
Explanation: Failure reading I2C VPD. are required. Otherwise, use the FRU and procedure
Response: If this is a tracking event, no service actions actions.
actions. 10008408
Explanation: PINEY has ECC errors or other bad
10008402 VPD.
Explanation: CMC Card VPD content problem. Response: If this is a tracking event, no service actions
Response: If this is a tracking event, no service actions callouts detailed with the SRC to determine service
are required. Otherwise, use the FRU and procedure actions.
actions.
10008409
10008403 Explanation: Midplane redundant VPD has ECC

errors or other bad VPD.
Explanation: VRM0 has chkum errors in VPD.
Response: If this is a tracking event, no service actions are required. Otherwise, use the FRU and procedure
are required. Otherwise, use the FRU and procedure callouts detailed with the SRC to determine service
callouts detailed with the SRC to determine service actions.
actions.

1000840F • 100084C9
1000840F 100084C4
Explanation: CMC Card VPD content problem. Explanation: Valid midplane VPD not collected.
actions. actions.
100084B5 100084C5
Explanation: LX VPD Keyword missing from the I/O Explanation: Valid midplane VPD not collected.
module.
Response: The FRU callouts are calculated at the time are required. Otherwise, use the FRU and procedure
of the failure. See the error log for the actual callouts detailed with the SRC to determine service
replacement strategy. actions.
100084C0 100084C6
Explanation: Machine Type/Model keyword not Explanation: Failure updating Machine Type/Model
found in midplane VPD. keyword in midplane VPD.
actions. actions.
100084C1 100084C7
Explanation: Machine Type/Model keyword not Explanation: Failure updating Machine Type/Model
actions. actions.
100084C2 100084C8
Explanation: Machine Serial Number keyword not Explanation: Failure updating Machine Serial Number
actions. actions.
100084C3 100084C9
Explanation: Machine Serial Number keyword not Explanation: Failure updating Machine Serial Number
actions. actions.

100084CA • 100084F4
100084CA 100084D0
Explanation: Failure updating Machine Serial Number Explanation: The Machine Type, Model, and Serial
keyword in midplane VPD due to I2C error. Number was overwritten in the CMC card flash with
values from 1 midplane VPD chip.
actions.
100084CB
100084D1
Explanation: Failure updating Machine Serial Number
keyword in midplane VPD due to I2C error. Explanation: The Machine Type, Model, and Serial
Number values cannot be determined.
actions.
100084CC
100084F0
Explanation: CMC Card Non-volatile storage problem.
Explanation: Failure reading I2C VPD
are required. Otherwise, use the FRU and procedure Response: The FRU callouts are calculated at the time
callouts detailed with the SRC to determine service of the failure. See the error log for the actual
actions. replacement strategy.
100084CD 100084F1
Explanation: The Machine Type, Model, and Serial Explanation: FPGA Device is not supported in VPD
Number values cannot be determined.
Response: If this is a tracking event, no service actions of the failure. See the error log for the actual
are required. Otherwise, use the FRU and procedure replacement strategy.
actions.
100084F2
Explanation: VRM0 has errors in VPD
100084CE
Explanation: The Machine Type, Model, and Serial
Number was overwritten in the CMC card flash.
100084F3
actions. Explanation: VRM1 has errors in VPD
100084CF of the failure. See the error log for the actual
Explanation: The Machine Type, Model, and Serial
Number was overwritten in the CMC card flash with
values from 1 midplane VPD chip. 100084F4
Response: If this is a tracking event, no service actions Explanation: Midplane has ECC errors or other bad
are required. Otherwise, use the FRU and procedure VPD
actions. Response: The FRU callouts are calculated at the time

100084F5 • 10009002
100084F5 10008B11
Explanation: An I/O module has ECC errors or other Explanation: LX VPD Keyword missing from IO Bay
bad VPD 1.
actions.
100084F6
10008B20
Explanation: An I/O module has ECC errors or other
bad VPD Explanation: VINI VPD record is too large on IO Bay
0.
actions.
100084F7
Explanation: ECC errors or other bad VPD was
10008B21
detected.
Explanation: VINI VPD record is too large on IO Bay
1.
100084F8
actions.
Explanation: Midplane redundant VPD has ECC
errors or other bad VPD
10008B30
Explanation: IO Bay 0 was removed with system
powered on.
10008B00
Explanation: IO Bay 0 FPGA fail. actions.
are required. Otherwise, use the FRU and procedure 10008B31
Explanation: IO Bay 1 was removed with system
actions.
powered on.
10008B01
Explanation: IO Bay 1 FPGA fail. callouts detailed with the SRC to determine service
actions.
actions.
Explanation: Received a bad return code
Response: The power firmware has detected a
10008B10
condition that may require attention. Check error log
Explanation: LX VPD Keyword missing from IO Bay for other errors that may have been reported at the
0. same time as this condition was reported. If this SRC
persists contact next level of support.
actions.

10009005 • 10009019
a unit address of D or E or had a frame address of 00.

10009005
Exchange the failing items in the system unit. Follow
Explanation: Received a bad return code the instructions for the items listed in the FRU List.
Response: The power firmware has detected a Failing Item:
condition that may require attention. Check error log v LICCODE
for other errors that may have been reported at the
v TWRCARD
same time as this condition was reported. If this SRC
10009015
10009006 Explanation: An invalid rack command was
encountered.
Explanation: I/O Expansion Unit firmware download
failed waiting for I/O Expansion Unit to be ready. Response: Informational message: The command is
invalid for the addressed rack and has not been
executed. This status is also returned if the address
mode is not valid for the command. The information
found in this error log entry may be used by product
engineering to debug failures.
10009016
10009007
Explanation: A command to an system node was
Explanation: Unable to obtain CEC VPD data.
rejected.
Response: No action required. This reference code is
logged for information only.
persists contact next level of support. 10009018
Explanation: An invalid modifier was found in a
10009012 command.
Explanation: Address not valid. Response: Informational message: This status is used
by the slave, rack and CEC to identify invalid
Response: LIC command had a frame address that
command modifier values in commands directed to the
was not valid. Follow the instructions for the items
node. An APX command will be rejected by the CEC
listed in the FRU List.
without transmission on the network if the modifier
Failing Item: field contains an invalid address. The information
v TWRCARD found in this error log entry may be used by product
v LICCODE
10009019
10009013
Explanation: An invalid command was encountered.
Explanation: Invalid Node Address.
Response: Informational message: The command is
Response: The address in the command does not
not valid for transmission on the network. The
match the secondary nodes assigned address. Exchange
following conditions are detected by the CEC node
the failing items for the system node reporting the
during hypervisor command processing. The command
error. Follow the instructions for the items listed in the
is rejected directly by the CEC node for the following
FRU List.
reasons:
Failing Item: v The command from the hypervisor was not defined.
v TWRCARD v The RPF or RPN command from the hypervisor
v LICCODE specified R = 0. (Programming cannot power the
system off via this mechanism).
10009014 v The LSP subset command (0x'1X') was not addressed
to a specific node.
Explanation: A command has an invalid address v The APX command was not addressed to
mode. RRRR=01-3FFF, UU=0.
Response: A command from the system unit specified

1000901A • 10009031
v A QSX command was not addressed to RRRR=0 ,

10009024
UU=D.
Explanation: I/O Expansion Unit Licensed Internal
The information found in this error log entry may be Code not valid.
used by product engineering to debug failures.
Response: The Licensed Internal Code in one of the
secondary nodes is not valid. The code will be
1000901A reloaded. No action required. This reference code is
logged for error analysis only.
Explanation: An invalid command was encountered.
Response: Informational message: The command is 10009025
not valid for transmission on the network. The
information found in this error log entry may be used Explanation: I/O Expansion Unit Licensed Internal
by product engineering to debug failures. Code is not valid.
Response: The Licensed Internal Code in one of the
1000901B frames is not valid. The code will be reloaded. No
action required. This reference code is logged for error
Explanation: A CEC port addressing problem was analysis only.
found.
Response: Informational message: This status is 10009028
inserted by the primary rack on broadcast commands
to identify the location of the CEC node. This response Explanation: I/O Expansion Unit Licensed Internal
is returned to node specific commands addressed to the Code is not valid.
CEC node using the CEC physical RRRRUU value. The
Response: The Licensed Internal Code in an I/O
CEC cannot be addressed with this address. The
Expansion Unit is not valid. The code will be reloaded.
information found in this error log entry may be used
No action required. This reference code is logged for
by product engineering to debug failures.
error analysis only.
1000901C
10009029
Explanation: An invalid data field was found in a
Explanation: System node VPD Damaged.
command.
Response: The VPD record in the EEPROM has bad
Response: Informational message: The information
data. This reference code is logged for error analysis
found in this error log entry may be used by product
only.
1000902D
10009021
Explanation: Addressed frame is not in system power
Explanation: A command to an system node was not
configuration table.
processed due to the current system state..
Response: The addressed frame is not in the system
power configuration table. No action required. This
reference code is logged for information only.
10009022
1000902F
Explanation: Addressed Unit not in frame.
Explanation: A command is already in progress.
Response: The addressed unit does not exist in the
Response: A system power comand is already in
addressed frame. No action required. This reference
progress to the target system unit.. No action required.
code is logged for information only.
This reference code is logged for information only.
10009023
10009031
Explanation: Addressed Unit exists, but the frame is
Explanation: Frame-to-Frame Communications Failure
powered off.
Response: The system detected an error on a
Response: The addressed unit is in a frame that is
transmission from another frame. The transmission is
powered off. No action required. This reference code is
attempted again. No action required. This reference
code is logged for error analysis only.

10009032 • 10009043
10009032 10009038
Explanation: System Communications Failure, unit to Explanation: An internal slave error prevented the
rack. execution of a command.
Response: The frame detected an error on a Response: An internal slave error has prevented the
transmission from a secondary node to the frame. The execution of a command. The command is attempted
transmission is attempted again. No action required. again. No action required. This reference code is logged
This reference code is logged for error analysis only. for error analysis only.
10009033 10009039
Explanation: System Communications Failure, rack to Explanation: An internal rack error prevented the
unit. execution of a command.
Response: A secondary node detected an error on a Response: An internal rack error has prevented the
transmission from the frame. The transmission is execution of a command. The command is attempted
attempted again. No action required. This reference again. No action required. This reference code is logged
code is logged for error analysis only. for error analysis only.
10009034 1000903B
Explanation: Unsupported Packet Size Explanation: Invalid Packet Length for data sent.
Response: The receiving node detected a packet Response: The number of bytes sent or received does
exceeding 70 bytes. The frame can also return this code not match the number of bytes specified in the
if a secondary node returns more than 10 bytes to a command. No action required. This reference code is
PAS command. No action required. This reference code logged for error analysis only.
is logged for error analysis only.
10009041
10009035
Explanation: Invalid Load Type
Explanation: Secondary system node timeout.
Response: The I/O Expansion Unit firmware
Response: A secondary system node did not respond download was successful, but the wrong type of
to a command. The command was attempted again and Licensed Internal Code was loaded. The operation was
failed. No action required. This reference code is logged attempted again but was not successful.. Follow the
for error analysis only. instructions for the items listed in the FRU List.
Failing Item:
10009036 v LICCODE
Explanation: Frame Timeout v TWRCARD
Response: One or more frames did not respond to a
command. The command is attempted again. No action 10009042
required. This reference code is logged for error
Explanation: EEPROM Failure
analysis only.
Response: The EEPROM in an system node cannot be
written successfully. Follow the instructions for the
10009037
items listed in the FRU List.
Explanation: An internal CEC error prevented the
Failing Item:
execution of a command.
v TWRCARD
Response: An internal CEC error has prevented the
execution of a command. The command is attempted
again. No action required. This reference code is logged 10009043
for error analysis only. Explanation: Download Failure
Response: The Licensed Internal Code download to
an I/O Expansion Unit was completed but was not
successful. Follow the instructions for the items listed
in the FRU List.
Failing Item:

10009044 • 10009066
v TWRCARD
10009061
Explanation: The service communication path to an
10009044
I/O Expansion Unit was not ready.
Explanation: Download Failure due to invalid load
Response: The service communication path to an I/O
size
Expansion Unit was not ready. The command is
Response: The Licensed Internal Code download to attempted again. No action required. This reference
an I/O Expansion Unit failed due to an invalid load code is logged for error analysis only.
size. Follow the instructions for the items listed in the
FRU List.
10009062
Failing Item:
v TWRCARD I/O Expansion Unit was busy.
10009045 Expansion Unit was busy. The command is attempted
Explanation: Download Failure due to invalid block again. No action required. This reference code is logged
size for error analysis only.
Response: The Licensed Internal Code download to

an I/O Expansion Unit failed due to an invalid block 10009063
size. Follow the instructions for the items listed in the Explanation: The service communication path to an
FRU List. I/O Expansion Unit had a checksum failure.
Failing Item: Response: The service communication path to an I/O
v TWRCARD Expansion Unit had a checksum failure. The command
is attempted again. No action required. This reference
code is logged for error analysis only.
10009046
Explanation: QDS Packet Sequence Error 10009064
Response: The Packet Sequence number is wrong. The Explanation: The service communication path to an
download was stopped. Follow the instructions for the I/O Expansion Unit encountered a device error.
items listed in the FRU List.
Failing Item: Expansion Unit encountered a device error. The
v TWRCARD command is attempted again. No action required. This
reference code is logged for error analysis only.
10009047
10009065
Explanation: QDS Block Sequence Error
Response: The Block Sequence number is wrong. The
I/O Expansion Unit had a synchronization error.
download was stopped. Follow the instructions for the
items listed in the FRU List. Response: The service communication path to an I/O
Expansion Unit had a synchronization error. The
Failing Item:
command is attempted again. No action required. This
v TWRCARD reference code is logged for error analysis only.
10009048 10009066
Explanation: The system ROS and EEPROM LIC is Explanation: The service communication path to an
not compatible. I/O Expansion Unit had a synchronization error.
Response: The LIC levels in the nodes ROS and Response: The service communication path to an I/O
EEPROM are not compatible. Exchange the failing Expansion Unit had a synchronization error. The
items for the failing node. Follow the instructions for command is attempted again. No action required. This
the items listed in the FRU List. reference code is logged for error analysis only.
Failing Item:
v TWRCARD
v LICCODE

10009067 • 10009109
maintenance operation, it is informational only and can

10009067
be ignored.
I/O Expansion Unit encountered a busy condition.
100090F3
Explanation: Slave reappeared
Expansion Unit encountered a busy condition. The
command is attempted again. No action required. This Response: No action required. This reference code is
reference code is logged for error analysis only. logged for information only.
10009080 10009102
Explanation: Undefined Status Code Explanation: Assign Permanent Address command
failure
Response: A system node returned an unknown status
code. Follow the instructions for the items listed in the Response: A node failed to perform an Assign
FRU List. Permanent Address command. Follow the instructions
for the items listed in the FRU List.
Failing Item:
v TWRCARD Failing Item:
v TWRCARD
10009088
10009104
Explanation: A problem was found in the system
power firmware. Explanation: Download Completion Timeout
Response: Informational message: A problem was Response: A system node failed to leave the
found in the system power firmware. The information download state. Follow the instructions for the items
found in this error log entry may be used by product listed in the FRU List.
Failing Item:
v TWRCARD
100090F0
Explanation: A frame was dropped from the system 10009105
configuration.
Explanation: Load Damaged Timeout
Response: A frame was dropped from the system
configuration. This is usually caused by a loss of ac Response: A system node failed to enter the
power or a problem with the frame-to-frame cables. operational state. Follow the instructions for the items
Check for other B700xxxx serviceable events that may listed in the FRU List.
have been reported at the same time as this error was
Failing Item:
reported. Contact the next level of support if no other
serviceable events are found or if this error persists v TWRCARD
after following the service procedures for these other
events. 10009106
Failing Item: Explanation: An system firmware LID was not found.
v SVCDOCS
100090F1
Explanation: A frame was added to the system 10009109
configuration.
Explanation: Licensed Internal Code part number is
Response: No action required. This reference code is not correct.
Response: The AROS part number field was not
updated to the correct level after the system attempted
100090F2 to load new Licensed Internal Code. Follow the
instructions for the items listed in the FRU List.
Explanation: Slave disappeared
Failing Item:
Response: A slave was dropped from the system
configuration. This is usually caused by a loss of ac v TWRCARD
power. If this SRC is logged during a concurrent

1000910A • 10009134
v VPDPART
1000910A
Explanation: System firmware download required
1000911D
Explanation: System firmware download failure
1000910B
Explanation: Maximum number of retries exceeded
1000911E
Explanation: Temporary VPD written
Response: Follow the instructions for the items listed
in the FRU List.
10009111
Failing Item:
Explanation: The number of nodes in the system is
too large for hypervisor. v PWRVPD
Response: There are more nodes in the network than

the hypervisor can service. Go to System Configuration 10009120
in ASMI . Under Configure I/O Enclosures select Clear Explanation: Duplicate backplane VPD
Inactive Enclosures. If the error persists follow the
instructions for the items listed in the FRU List. Response: Follow the instructions for the items listed
in the FRU List.
Failing Item:
v LICCODE Failing Item:
v SYSBKPL
10009115
10009132
Explanation: Command rejected by the firmware.
Explanation: Node contains temporary VPD
Response: The service processor rejected a power
subsystem command from the Licensed Internal Code. Response: No action required. This reference code is
No action required. This reference code is logged for logged for information only.
information only.
10009133
10009118
Explanation: Bad PCI Correlation Problem
Explanation: Hypervisor out of memory
Response: PCI bus not matched. If this is a serviceable
Response: Follow the instructions for the items listed event, check for other B700xxxx Serviceable Events that
in the FRU List. may have been reported at the same time as this error
was reported. Contact the next level of support if no
Failing Item: other serviceable events are found or if this error
v LICCODE persists after following the service procedures for these
other events. If this SRC is logged during a concurrent
1000911B
be ignored.
Explanation: System CEC node code failure
Failing Item:
Response: Follow the instructions for the items listed v SVCDOCS
in the FRU List.
v LICCODE
Explanation: PCI bus VPD error
1000911C
Explanation: Two nodes have same VPD
in the FRU List.
Failing Item:

10009136 • 1000CB15
10009136 1000913C
Explanation: A system firmware update for an I/O Explanation: Invalid I/O Expansion Unit Platform
Expansion Unit was interrupted Error Log detected.
Response: No action is required. The firmware will Response: No action required. This reference code is
automatically re-attempt to download the system logged for information only.
firmware to the I/O Expansion Unit.
1000913D
10009137
Explanation: A PCI Correlation Problem has been
Explanation: Bad PCI Correlation Problem corrected.
Response: System node not matched to PCI bus. If Response: No action required. This reference code is
this is a serviceable event, check for other B700xxxx logged for information only.
Serviceable Events that may have been reported at the
same time as this error was reported. Contact the next
1000913E
level of support if no other serviceable events are found
or if this error persists after following the service Explanation: A PCI Correlation Problem has been
procedures for these other events. If this SRC is logged corrected.
during a concurrent maintenance operation, it is
informational only and can be ignored. Response: No action required. This reference code is
Failing Item:
v SVCDOCS 10009160
Explanation: VPD collection failed for I/O Expansion
10009138 Unit.
Explanation: Bad location code detected in system Response: No action required. Other B700xxxx errors
firmware will be logged as serviceable events for this problem.
Response: The system has detected a bad location This reference code is logged for information only.
code or vital product data. If this is a serviceable event,
check for other B700xxxx Serviceable Events that may 100091DE
have been reported at the same time as this error was
reported. Contact the next level of support if no other Explanation: I/O Expansion Unit firmware download
serviceable events are found or if this error persists complete
after following the service procedures for these other
events. If this SRC is logged during a concurrent
be ignored.
1000CB15
Failing Item:
v SVCDOCS Explanation: An PEROM error was detected.
1000913A are required. Otherwise, use the FRU and procedure
Explanation: System firmware download sent retry actions.
1000913B
Explanation: An I/O Expansion Unit firmware
download was prevented by the firmware update
policy.
in the FRU List.
Failing Item:
v PWR1907

110000AC • 11001513

time this SRC was reported then you can ignore
110000AC
and close this event. No service is required.
Explanation: Detected AC loss Otherwise continue with the next step in this
procedure.
Response: If system powers on normally or stays
powered on after AC power failure, no replacement of 2. Ensure the line cords are properly connected and
parts may be needed. Follow the instructions for the seated on both ends. For help in locating the line
items listed in the FRU List. cords of the power supply reporting thi s problem
use the location code in the serviceable event or the
Problem determination: The system may have symbolic FRU in the failing items list below.
3. If the system was just installed or moved, verify the
such as utility or building power and the sy stem may
have recovered.
1. If there was a utility, building or room power loss
problem to your service provider.
that would have affected the system at the same
time this SRC was reported then you can ignore Failing Item:
and close this event. No service is required. v PWRSPLY
v TWRCARD
procedure.
seated on both ends. For help in locating the line 11001511
cords of the power supply reporting thi s problem Explanation: Power supply failure
symbolic FRU in the failing items list below. Response: Follow the instructions for the items listed
3. If the system was just installed or moved, verify the in the FRU List.
AC input voltage is correct. Problem determination: No additional problem
4. If the problem is not resolved then report this determination.
Failing Item:
Failing Item: v PWRSPLY
v ACMODUL v TWRCARD
110000AD 11001512
Explanation: A reset of the service processor caused Explanation: Power supply failure
the system to power off.
Response: Follow the instructions for the items listed in the FRU List.
in the FRU List.
Problem determination: No additional problem
Problem determination: No additional problem determination.
determination.
Failing Item:
Failing Item:
v PWRSPLY
v TWRCARD
v TWRCARD
v CBLALL
11001510
Explanation: Detected AC loss 11001513
Response: Before replacing any parts, verify that the Explanation: Power supply failure
AC input voltage is correct. Follow the instructions for
the items listed in the FRU List. Response: Follow the instructions for the items listed
in the FRU List.
Problem determination: The system may have
experienced an AC Power Loss external to the system Problem determination: No additional problem
such as utility or building power and the sy stem may determination.
have recovered. Failing Item:
1. If there was a utility, building or room power loss v PWRSPLY
v TWRCARD

11001514 • 11001523

11001514
Explanation: Power supply failure such as utility or building power and the sy stem may
have recovered.
in the FRU List. 1. If there was a utility, building or room power loss
Problem determination: No additional problem time this SRC was reported then you can ignore
determination. and close this event. No service is required.
Failing Item: Otherwise continue with the next step in this
procedure.
v PWRSPLY
v TWRCARD seated on both ends. For help in locating the line
cords of the power supply reporting thi s problem
11001515 use the location code in the serviceable event or the
symbolic FRU in the failing items list below.
Explanation: A power supply mismatch was detected.
Response: Before replacing any parts, verify that the AC input voltage is correct.
AC input voltage is correct. Follow the instructions for 4. If the problem is not resolved then report this
the items listed in the FRU List. problem to your service provider.
Problem determination: No additional problem Failing Item:
determination.
v PWRSPLY
v TWRCARD
1100151E
Explanation: The power supply fan on Un-E1 11001521
experienced a short stoppage, but recovered. The
power supply should be replaced as soon as possible Explanation: Power supply failure
before the fan fails permanently. Response: Follow the instructions for the items listed
in the FRU List. Problem determination: No additional problem
determination. Failing Item:
Failing Item: v PWRSPLY
v PWRSPLY v TWRCARD
v TWRCARD
11001522
1100151F Explanation: Power supply failure
Explanation: The power supply fan on Un-E1 failed. Response: Follow the instructions for the items listed
The power supply should be replaced as soon as in the FRU List.
possible.
Response: Follow the instructions for the items listed determination.
in the FRU List.
Failing Item:
determination. v PWRSPLY
v TWRCARD
Failing Item:
v CBLALL
v PWRSPLY
v TWRCARD
11001523
11001520 Explanation: Power supply failure
Explanation: Detected AC loss Response: Follow the instructions for the items listed
in the FRU List.
Response: Before replacing any parts, verify that the
AC input voltage is correct. Follow the instructions for Problem determination: No additional problem
the items listed in the FRU List. determination.

11001524 • 11001533
Failing Item: 1. If there was a utility, building or room power loss

v PWRSPLY that would have affected the system at the same
time this SRC was reported then you can ignore
v TWRCARD
and close this event. No service is required.
11001524 procedure.
Explanation: Power supply failure 2. Ensure the line cords are properly connected and
seated on both ends. For help in locating the line
Response: Follow the instructions for the items listed cords of the power supply reporting thi s problem
in the FRU List. use the location code in the serviceable event or the
determination. 3. If the system was just installed or moved, verify the
Failing Item:
v PWRSPLY problem to your service provider.
v TWRCARD
Failing Item:
v PWRSPLY
1100152E
v TWRCARD
Explanation: The power supply fan on Un-E2
experienced a short stoppage, but recovered. The
11001531
power supply should be replaced as soon as possible
before the fan fails permanently. Explanation: Power supply failure
Response: Follow the instructions for the items listed Response: Follow the instructions for the items listed
in the FRU List. in the FRU List.
Problem determination: No additional problem Problem determination: No additional problem
determination. determination.
Failing Item: Failing Item:
v PWRSPLY v PWRSPLY
v TWRCARD v TWRCARD
1100152F 11001532
Explanation: The power supply fan on Un-E2 failed. Explanation: A power supply failure occurred.
The power supply should be replaced as soon as
possible. Response: Follow the instructions for the items listed
in the FRU List.
determination.
v PWRSPLY
Failing Item:
v TWRCARD
v PWRSPLY
v CBLALL
v TWRCARD
11001533
11001530
Explanation: Power supply failure
Explanation: Detected AC loss.
Response: Before replacing any parts, verify that the in the FRU List.
the items listed in the FRU List. Problem determination: No additional problem
determination.
experienced an AC Power Loss external to the system Failing Item:
such as utility or building power and the sy stem may v PWRSPLY
have recovered.
v TWRCARD

11001534 • 1100154F
11001534 11001541
Explanation: Power supply failure Explanation: Power supply failure
v PWRSPLY v PWRSPLY
v TWRCARD v TWRCARD
1100153F 11001542
Explanation: The power supply fan on Un-E3 failed. Explanation: A power supply failure occurred.
The power supply should be replaced as soon as
possible.
in the FRU List.
in the FRU List.
determination.
Failing Item:
determination.
v PWRSPLY
Failing Item:
v TWRCARD
v PWRSPLY
v CBLALL
v TWRCARD
11001543
11001540
Explanation: Detected AC loss
Response: Before replacing any parts, verify that the in the FRU List.
the items listed in the FRU List. Problem determination: No additional problem
determination.
experienced an AC Power Loss external to the system Failing Item:
such as utility or building power and the sy stem may v PWRSPLY
have recovered. v TWRCARD
1. If there was a utility, building or room power loss
time this SRC was reported then you can ignore 11001544
and close this event. No service is required. Explanation: A power supply failure occurred.
procedure. Response: Follow the instructions for the items listed
in the FRU List.
seated on both ends. For help in locating the line Problem determination: No additional problem
cords of the power supply reporting thi s problem determination.
Failing Item:
v PWRSPLY
AC input voltage is correct. v TWRCARD
4. If the problem is not resolved then report this v CBLALL
Failing Item: 1100154F
v PWRSPLY Explanation: The power supply fan on Un-E4 failed.
v TWRCARD The power supply should be replaced as soon as
possible.

11001611 • 11001633
Response: Follow the instructions for the items listed v TWRCARD

in the FRU List.
Problem determination: No additional problem 11001622
determination.
Explanation: Regulator 2 Communication Fault
Failing Item:
v PWRSPLY in the FRU List.
v TWRCARD
determination.
11001611
Failing Item:
Explanation: Regulator 1 Fault v PWR1918
in the FRU List.
determination.
Explanation: Regulator 2 Domain Fault
Failing Item:
v PWR1918 in the FRU List.
v TWRCARD
determination.
11001612
Failing Item:
Explanation: Regulator 1 Communication Fault v PWR1918
in the FRU List.
determination.
Explanation: Regulator 3 Fault
Failing Item:
v TWRCARD
determination.
11001613
Failing Item:
Explanation: Regulator 1 Domain Fault v PWR1918
in the FRU List.
determination.
Explanation: Regulator 3 Communication Fault
Failing Item:
v TWRCARD
determination.
11001621
Failing Item:
Explanation: Regulator 2 Fault v PWR1918
in the FRU List.
determination.
Explanation: Regulator 3 Domain Fault
Failing Item:

110016A0 • 110016F1

110016B0
determination.
Explanation: A CEC drawer connection card is
Failing Item:
missing.
v PWR1918
v TWRCARD
in the FRU List.
110016A0
determination.
Explanation: A system control drawer connection card
Failing Item:
is missing.
v PWRSPLY
in the FRU List.
110016B1
determination. Explanation: A CEC drawer connection card is
missing.
Failing Item:
v PWRSPLY
in the FRU List.
110016A1
determination.
Failing Item:
is missing.
v PWRSPLY
in the FRU List.
110016B2
missing.
Failing Item:
v PWRSPLY
in the FRU List.
110016A2
determination.
Failing Item:
is missing.
v PWRSPLY
in the FRU List.
110016B3
missing.
Failing Item:
v PWRSPLY
in the FRU List.
110016A3
determination.
Failing Item:
is missing.
v PWRSPLY
in the FRU List.
110016F1
determination. Explanation: No power supplies detected in drawer
number 1
Failing Item:
Response: Perform the following in order:
v PWRSPLY
v Check for system firmware updates; apply if
available.
v Replace the primary service processor.

110016F2 • 11001B06
v Replace the backplane in the failing drawer.

11001B01
v Replace all of the power supplies in the failing
drawer. Explanation: Level 1 load fault (+12V)
Problem determination: No additional problem Response: Follow the instructions for the items listed
determination. in the FRU List.
110016F2 determination.
Explanation: No power supplies detected in drawer Failing Item:

number 2 v PWR1900
v Check for system firmware updates; apply if 11001B02
available. Explanation: Load fault on the +5V bus
v Replace the primary service processor.
v Replace the backplane in the failing drawer. in the FRU List.
v Replace all of the power supplies in the failing
drawer.
determination.
Failing Item:
determination.
v PWR1900
v TWRCARD
110016F3
Explanation: No power supplies detected in drawer
11001B03
number 3
Explanation: Load fault on the +3.3V bus
v Check for system firmware updates; apply if Response: Follow the instructions for the items listed
available. in the FRU List.
v Replace the primary service processor. Problem determination: No additional problem
v Replace the backplane in the failing drawer. determination.
v Replace all of the power supplies in the failing Failing Item:
drawer. v PWR1900
Problem determination: No additional problem v TWRCARD
determination.
11001B05
110016F4
Explanation: Load fault on the +1.8V bus
Explanation: No power supplies detected in drawer
number 4 Response: Follow the instructions for the items listed
in the FRU List.
v Check for system firmware updates; apply if determination.
available.
v Replace the primary service processor. Failing Item:
v Replace the backplane in the failing drawer. v PWR1904
v Replace all of the power supplies in the failing v TWRCARD
drawer.
Problem determination: No additional problem 11001B06
determination. Explanation: Load fault on the +2.5V bus
in the FRU List.
determination.
Failing Item:

11001B0A • 11001C15
v PWR1904 Problem determination: No additional problem

v TWRCARD determination.
Failing Item:
11001B0A v PWR1904
Explanation: Load Fault on the +12V/-12v bus v TWRCARD

in the FRU List. 11001C12
Problem determination: No additional problem Explanation: Regulator Level 2 Load Fault (1.8)
determination. Response: Follow the instructions for the items listed
Failing Item: in the FRU List.
Failing Item:
11001B0F v PWR1904
Explanation: Load Fault on the +1.2V bus v TWRCARD

Problem determination: No additional problem Explanation: Regulator Level 2 Load Fault (1.2A)
Failing Item:
11001BFF v PWR1904
Explanation: A backplane short fault occurred. v TWRCARD

Problem determination: No additional problem Explanation: Regulator Level 2 Load Fault (1.25)
v PGDPART Problem determination: No additional problem
determination.
11001C10 Failing Item:
Explanation: Regulator Level 1 Load Fault (1.1A) v PWR1904
v TWRCARD
in the FRU List.
11001C15
determination. Explanation: Regulator Level 2 Load Fault (1.2B)
Failing Item: Response: Follow the instructions for the items listed
v TWRCARD Problem determination: No additional problem
determination.
Explanation: Regulator Level 2 Load Fault (1.1B) v PWR1904
v TWRCARD
in the FRU List.

11001D12 • 11001F02
v TWRCARD
11001D12
Explanation: I/O hub card 1 fault.
11001D68
Explanation: HEA adapter card 2 softswitch fault
in the FRU List.
in the FRU List.
determination.
determination.
11001D13
11001E00
Explanation: An open device failed.
in the FRU List.
determination.
determination.
11001D14
11001E01
Explanation: A write device failed.
in the FRU List.
determination.
determination.
11001D15
11001E03
Explanation: A read device failed.
in the FRU List.
determination.
determination.
11001D60
Explanation: RIO adapter card 1 softswitch fault
11001F01
Explanation: TMS limit reached - log only
in the FRU List.
determination.
Failing Item:
determination.
v SI_CARD
v TWRCARD
11001F02
Explanation: SPCN trace information saved
11001D63
Explanation: RIO adapter card 2 softswitch fault
in the FRU List.
determination.
determination.
Failing Item:
v SI_CARD

11001F03 • 11002614

11001F03
determination.
Explanation: Invalid TMS or location code; log only.
Failing Item:
Response: No action required. This reference code is v PGDPART
determination.
Explanation: A power signal failure has been detected
11001F04 Response: Follow the instructions for the items listed

in the FRU List.
Explanation: A power good latched event; log only.
Response: No action required. This reference code is determination.
Failing Item:
v SYSBKPL
determination.
v USBPGD
11001F05
11002611
Explanation: All power supplies reporting current out
fault; log only. Explanation: A power signal failure has been detected
Response: No action required. This reference code is Response: Follow the instructions for the items listed
logged for information only. in the FRU List.

Failing Item:
11002600 v SYSBKPL
Explanation: Power Good Fault
11002613
in the FRU List. Explanation: An input voltage type fault was
detected.
in the FRU List.
Failing Item:
v PGDPART Problem determination: No additional problem
determination.

v CBLALL
v SYSBKPL
in the FRU List.
11002614
determination. Explanation: The power supplies are mismatched; one
is ac, and one is dc.
Failing Item:
v PWR1918
in the FRU List.
v TWRCARD
determination.
11002603
Failing Item:
v PWRSPLY
in the FRU List.

11002615 • 1100262B
11002615 11002625
Explanation: 1925W power supplies are required in Explanation: 3.3V power-good input fault
this system.
in the FRU List.
determination.
Failing Item:
Failing Item: v PWR1918
v PWRSPLY
11002626
11002620
Explanation: 2.5V power-good input fault
Explanation: A power-good fault was detected.
in the FRU List.
determination.
Failing Item:
v SYSBKPL
11002627
11002622
Explanation: GX slot 1 pgood fault.
Explanation: 1.52V power-good input fault
in the FRU List.
determination.
v PWR1918 Explanation: P_GOOD fault on the I/O backplane.
11002623 in the FRU List.
Explanation: 1.8V power-good input fault Problem determination: No additional problem
in the FRU List. Failing Item:
Problem determination: No additional problem v SYSBKPL
determination.
Failing Item: 1100262A
v PWR1918 Explanation: GX slot 2 pgood fault.
11002624 in the FRU List.
Explanation: 5.0V power-good input fault Problem determination: No additional problem
in the FRU List.
Problem determination: No additional problem 1100262B
determination. Explanation: P_GOOD fault on the I/O backplane.
in the FRU List.

1100262C • 11002635

Failing Item:
v SYSBKPL 11002632
Explanation: Processor 1 VRM2 array power-good
1100262C fault
Explanation: DASD 5V regulator P_GOOD fault. Response: Follow the instructions for the items listed
in the FRU List.
determination.
v PWR1918
Failing Item:
v ANYPROC
v PWR1918
v SYSBKPL
1100262D
11002633
Explanation: P_GOOD fault on the I/O backplane.
Explanation: Processor 1 1.2V VRM power-good fault
in the FRU List. Response: Follow the instructions for the items listed
in the FRU List.
determination. Problem determination: No additional problem
determination.
Failing Item:
Failing Item:
v SYSBKPL
v PWR1918
v SYSBKPL
1100262E
Explanation: P_GOOD fault on the I/O backplane.
11002634
Explanation: Processor 1 1.8V VRM or processor 1
in the FRU List.
power-good fault
determination.
in the FRU List.
Failing Item:
v SYSBKPL determination.
Failing Item:
1100262F
v ANYPROC
Explanation: P_GOOD fault on the I/O backplane. v SYSBKPL
in the FRU List. 11002635
Problem determination: No additional problem Explanation: VRM fault on the processor card.
determination.
v SYSBKPL
determination.
11002630
Failing Item:
Explanation: Processor 1 P7_VRM pgood fault v PWR1918
(pluggable)
in the FRU List.

11002636 • 1100264B

11002636
determination.
Explanation: VRM fault on the processor card.
Failing Item:
Response: Follow the instructions for the items listed v PWR1918
in the FRU List.
v ANYPROC
Problem determination: No additional problem v SYSBKPL
determination.
v PWR1918
Explanation: Processor 2 1.8V VRM or processor 2
power-good fault
1100263A
Explanation: Memory card 1 pgood fault. in the FRU List.
Response: Follow the instructions for the items listed Problem determination: No additional problem
in the FRU List. determination.
Problem determination: Look for a 1100xxxx SRC that Failing Item:
was logged before this SRC. If an SRC is found, resolve v ANYPROC
that SRC first. If the problem is not corrected, follow
v SYSBKPL
the instructions for the items listed in the FRU list for
this SRC.
11002645
1100263B Explanation: VRM fault on the processor card.
Explanation: Memory card 1 pgood fault. Response: Follow the instructions for the items listed
in the FRU List.
determination.
v PWR1918
1100263C
Explanation: Memory card 1 pgood fault. 1100264A
Response: Follow the instructions for the items listed Explanation: Memory card 2 pgood fault.
Problem determination: No additional problem in the FRU List.
determination. Problem determination: Look for a 1100xxxx SRC that
was logged before this SRC. If an SRC is found, resolve
11002640 that SRC first. If the problem is not corrected, follow
the instructions for the items listed in the FRU list for
Explanation: Processor 2 P7_VRM pgood fault this SRC.
(pluggable)
Response: Follow the instructions for the items listed 1100264B
in the FRU List.
Explanation: Memory card 2 pgood fault.
in the FRU List.
11002642 Problem determination: No additional problem

determination.
Explanation: Processor 2 VRM2 array power-good
fault
in the FRU List.

1100264C • 11002662

1100264C
determination.
Failing Item:
Response: Follow the instructions for the items listed v ANYPROC
in the FRU List.
v SYSBKPL
determination.
1100265A
11002650
Explanation: Processor 3 VRM 1A or 1B power-good
in the FRU List.
fault
Problem determination: Look for a 1100xxxx SRC that
in the FRU List.
that SRC first. If the problem is not corrected, follow
Problem determination: No additional problem the instructions for the items listed in the FRU list for
determination. this SRC.
Failing Item:
v PWR1918 1100265B
v ANYPROC Explanation: Memory card 3 pgood fault.
v SYSBKPL Response: Follow the instructions for the items listed
in the FRU List.
Explanation: Processor 3 VRM2 array power-good determination.
fault
Response: Follow the instructions for the items listed 1100265C
in the FRU List. Explanation: Memory card 3 pgood fault.
determination. in the FRU List.
Failing Item: Problem determination: No additional problem
v PWR1918 determination.
v ANYPROC
v SYSBKPL 11002660
Explanation: Processor 4 VRM 1A or 1B power-good
11002653 fault
Explanation: Processor 3 1.2V VRM power-good fault Response: Follow the instructions for the items listed
in the FRU list.
in the FRU list. Problem determination: No additional problem
determination.
v PWR1918 v ANYPROC
v SYSBKPL v SYSBKPL
11002654 11002662
Explanation: Processor 3 1.8V VRM or processor 3 Explanation: Processor 4 VRM2 array power-good
power-good fault fault
in the FRU list. in the FRU list.

11002663 • 110026A1

1100266C
determination.
Failing Item:
v PWR1918 Response: Follow the instructions for the items listed
in the FRU List.
v ANYPROC
v SYSBKPL Problem determination: No additional problem
determination.
11002663
11002690
Explanation: Processor 4 1.2V VRM power-good fault
Explanation: Processor 1 and 2 VDDA pgood fault.
in the FRU list. Response: Follow the instructions for the items listed
in the FRU List.
determination.
Failing Item:
v PWR1918
11002691
v SYSBKPL
Explanation: Processor 1 and 2 VSN pgood fault.
11002664 Response: Follow the instructions for the items listed

in the FRU List.
Explanation: Processor 4 1.8V VRM failed or processor
4 power-good fault Problem determination: No additional problem
determination.
in the FRU list. Failing Item:
v PWR1918
determination.
110026A0
Failing Item:
v ANYPROC Explanation: A 12Vcs power good failure occurred on
the system control drawer connection card.
v SYSBKPL
in the FRU List.
1100266A
determination.
Failing Item:
in the FRU list.
v CBLALL
Problem determination: Look for a 1100xxxx SRC that
that SRC first. If the problem is not corrected, follow 110026A1
the instructions for the items listed in the FRU list for Explanation: A 12Vcs power good failure occurred on
this SRC. the system control drawer connection card.
1100266B in the FRU List.
Explanation: Memory card 4 pgood fault. Problem determination: No additional problem
Problem determination: No additional problem v CBLALL
determination.

110026A2 • 11002703
Failing Item:
110026A2
v CBLALL
Explanation: A 12Vcs power good failure occurred on
110026B3
in the FRU List. Explanation: A 12V power good failure occurred on
in the FRU List.
Failing Item:
v CBLALL
determination.
Failing Item:
110026A3
v CBLALL
Explanation: A 12Vcs power good failure occurred on
11002700
in the FRU List. Explanation: A voltage regulator module (VRM) fault
has occurred.
in the FRU List.
Failing Item:
v CBLALL
determination.
110026B0
11002701
Explanation: A 12V power good failure occurred on
Explanation: Informational monitoring event in the
power subsystem. No service is required.
in the FRU List.
in the FRU List.
determination.
determination.
Failing Item:
v CBLALL 11002702
Explanation: VRM fault on the DASD backplane.
110026B1 DASD backplane replacement is required.
Explanation: A 12V power good failure occurred on Response: Follow the instructions for the items listed
the system control drawer connection card. in the FRU List.
determination. 11002703
Failing Item: Explanation: Informational monitoring event in the
v CBLALL power subsystem. No service is required.
110026B2 in the FRU List.
Explanation: A 12V power good failure occurred on Problem determination: No additional problem
the system control drawer connection card. determination.
in the FRU List.
determination.

11002704 • 11004600
11002704 11003114
Explanation: VRM fault on the I/O backplane. Explanation: Service processor I2C failure
Failing Item:
11002705 v I2CBUS
Explanation: Informational monitoring event in the v SYSBKPL
power subsystem. No service is required. v TWRCARD
Problem determination: No additional problem Explanation: I2C failure: blower control chip
determination.
in the FRU List.
11002800
Explanation: The system was automatically shut down determination.
because the top cover was removed.
Failing Item:
v SYSBKPL
in the FRU List.
11003120
determination.
Explanation: VRM failure
Failing Item:
v LDSWTCH Response: Follow the instructions for the items listed
in the FRU list in the error log entry.

determination.
Explanation: Service processor I2C failure
Response: Follow the instructions for the items listed 11004201
in the FRU list.
Explanation: UPS reported: utility failure signal is on
determination. Response: No action required. This reference code is
Failing Item:
v I2CBUS
determination.
v TWRCARD
11004203
11003105
Explanation: UPS reported: battery low signal is on
Explanation: Service processor I2C failure.
Response: Follow the instructions for the items listed logged for information only.
in the FRU List.
determination.
v TWRCARD
Explanation: UPS interface failure
in the FRU List.

11004601 • 11007200

11007110
determination.
Failing Item:
v UPSUNIT Response: Follow the instructions for the items listed
in the FRU List.
v TWRCARD
determination.
11004601
Failing Item:
Explanation: UPS interface failure
v PWRSPLY
v TWRCARD
in the FRU List.
11007120
determination.
Failing Item:
v UPSUNIT Response: Follow the instructions for the items listed
in the FRU List.
v TWRCARD
determination.
11005000
Failing Item:
Explanation: Service processor fail over failed due to
configuration mismatch v PWRSPLY
v TWRCARD
in the FRU List.
11007130
determination. Explanation: Power supply failure
v TWRCARD in the FRU List.
11005001 determination.
Explanation: Service processor fail over failed due to Failing Item:

configuration mismatch v PWRSPLY
in the FRU List.
determination. Explanation: Power supply failure
Explanation: SPCN ports not present. mismatch Failing Item:
Response: Follow the instructions for the items listed v PWRSPLY
in the FRU List. v TWRCARD
determination. 11007200
Failing Item: Explanation: The system is located at an altitude
v CBLALL greater than 4000 meters (13,120 feet). This is outside
the range of the system specifications.
in the FRU List.

11007201 • 11007210
Problem determination: No additional problem 4. If the above steps did not resolve the problem then
determination. report the problem to your service provider.
v ALTTUDE v AMBTEMP
11007201 11007204
Explanation: Ambient temperature is out of range Explanation: Ambient temperature is back in range
Response: Follow the procedure for the items listed in Response: Follow the procedure for the items listed in
the FRU List. the FRU List.
Problem determination: Problem determination: No additional problem
1. Verify that adequate cooling exists in the system's determination.
environment. Failing Item:
2. If there was a cooling failure at about the same time v AMBBACK
these SRCs were logged, these errors can be ignored
and closed.Otherwise continue with the next step in
this procedure. 11007205
3. Verify that the air temperature around the system's Explanation: Ambient temperature exceeded limit
intakes, including exhaust air blowing at the system
from nearby equipment, is within th e system's Response: The system will shut down in 20 seconds.
environmental limits. Follow the instructions for the items listed in the FRU
list.
4. If the above steps did not resolve the problem then
report the problem to your service provider. Problem determination: No additional problem
determination.
Failing Item:
v AMBTEMP Failing Item:
v AMBTEMP
11007202
11007207
Explanation: Ambient temperature is back in range
Explanation: Ambient temperature has dropped below
Response: Follow the procedure for the items listed in the low temperature limit.
the FRU List.
determination.
Failing Item: determination.
v AMBBACK
Failing Item:
v AMBTEMP
11007203
Explanation: Ambient temperature exceeded limit 11007210
Response: The system will shut down in 15 minutes. Explanation: The system is located at an altitude that
Follow the instructions for the items listed in the FRU is outside the range of the system performance
List. specification.
Problem determination: Response: The system is located at an altitude that is
1. Verify that adequate cooling exists in the system's not within the range of the system specification.
environment.
2. If there was a cooling failure at about the same time determination.
and closed.Otherwise continue with the next step in Failing Item:
this procedure. v ALTTUDE
3. Verify that the air temperature around the system's
from nearby equipment, is within th e system's
environmental limits.

11007211 • 11007231
Response: The ambient temperature is outside the

11007211
range of the system performance specification, and the
Explanation: Ambient temperature is out of range thermal/power management firmware may reduce
performance in heavy workload situations.
Response: Ambient temperature is above nominal for
CPU performance. Follow the instructions for the items Problem determination:
listed in the FRU List. 1. Verify that adequate cooling exists in the system's
Problem determination: environment.
1. Verify that adequate cooling exists in the system's 2. If there was a cooling failure at about the same time
environment. these SRCs were logged, these errors can be ignored
2. If there was a cooling failure at about the same time
this procedure.
and closed.Otherwise continue with the next step in 3. Verify that the air temperature around the system's
this procedure. intakes, including exhaust air blowing at the system
from nearby equipment, is within th e system's 4. If the above steps did not resolve the problem then
environmental limits. report the problem to your service provider.
4. If the above steps did not resolve the problem then Failing Item:
report the problem to your service provider. v AMBPERF
Failing Item:
v AMBTMP1 11007222
Explanation: The ambient temperature is back in
11007212 range.
Explanation: Ambient temperature is back in range Response: No action required. This reference code is
Response: Ambient temperature has returned to
nominal. Problem determination: No additional problem
determination.
determination.
11007230
Failing Item:
v AMBTMP2 Explanation: The ambient temperature is out of range.
11007220 logged for information only.
Explanation: The system is located at an altitude that Problem determination:

is outside the range of the system performance 1. Verify that adequate cooling exists in the system's
specification, and the thermal/power management environment.
firmware may reduce performance in heavy workload 2. If there was a cooling failure at about the same time
situations. these SRCs were logged, these errors can be ignored
Response: The system is located at an altitude that is and closed.Otherwise continue with the next step in
within the range of the system specification, but the this procedure.
thermal/power management firmware may reduce 3. Verify that the air temperature around the system's
performance due to the altitude. intakes, including exhaust air blowing at the system
determination.
Failing Item: report the problem to your service provider.
v ALTPERF
11007231
11007221
Explanation: The ambient temperature is out of range.
Explanation: The ambient temperature is outside the
range of the system performance specification, and the
thermal/power management firmware may reduce
performance in heavy workload situations. Problem determination:

11007232 • 11007610
1. Verify that adequate cooling exists in the system's

11007404
environment.
2. If there was a cooling failure at about the same time Explanation: A drawer is missing power.
these SRCs were logged, these errors can be ignored Failing Item:
v DRWRPWR
this procedure.
intakes, including exhaust air blowing at the system 11007411
from nearby equipment, is within th e system's Explanation: The drawer latched detected a power
environmental limits. loss forcing the service processor to reset.
report the problem to your service provider. Response: No action required. This reference code is

determination.
Explanation: The ambient temperature is out of range.
Response: No action required. This reference code is 11007412
Explanation: The drawer latched detected a power
Problem determination: loss forcing the service processor to reset.
1. Verify that adequate cooling exists in the system's Response: No action required. This reference code is
environment. logged for information only.
2. If there was a cooling failure at about the same time
these SRCs were logged, these errors can be ignored Problem determination: No additional problem
and closed.Otherwise continue with the next step in determination.
this procedure.
3. Verify that the air temperature around the system's 11007413
loss forcing the service processor to reset.
4. If the above steps did not resolve the problem then Response: No action required. This reference code is
report the problem to your service provider. logged for information only.
Explanation: A drawer is missing power.

11007414
Failing Item:
v DRWRPWR
loss forcing the service processor to reset.
11007402
Explanation: A drawer is missing power.
v DRWRPWR
11007610
11007403 Explanation: Fan fault
Explanation: A drawer is missing power. Response: The fan is operating at the wrong speed.
Failing Item: Follow the instructions for the items listed in the FRU
List.
v DRWRPWR
determination.
Failing Item:
v AIRMOVR
v TWRCARD

11007611 • 11007650
11007611 11007631
Explanation: Fan missing error Explanation: A problem was detected with a fan
which can be caused by a fan not being installed.
Response: A problem was detected with a fan which
Install the fan if it is missing; replace it if already
can be caused by a fan not being installed. Install fan if
installed. Follow the instructions for the items listed in
missing, replace if already installed. Follow the
the FRU list.
in the FRU List.
determination.
Failing Item:
determination.
v AIRMOVR
Failing Item:
v TWRCARD
v AIRMOVR
v TWRCARD
11007620
Explanation: Fan fault
11007640
Response: The fan is operating at the wrong speed.
Explanation: A fan is operating at the wrong speed.
Follow the instructions for the items listed in the FRU
List.
list.
determination.
in the FRU List.
Failing Item:
v AIRMOVR determination.
v TWRCARD
Failing Item:
v AIRMOVR
11007621
v TWRCARD
Explanation: Fan missing error
Response: A problem was detected with a fan which 11007641
can be caused by a fan not being installed. Install fan if
Explanation: A problem was detected with a fan
missing, replace if already installed. Follow the
Install the fan if it is missing; replace it if already
Problem determination: No additional problem installed. Follow the instructions for the items listed in
determination. the FRU list.
v AIRMOVR in the FRU List.

determination.
Explanation: A fan is operating at the wrong speed. v AIRMOVR
Follow the instructions for the items listed in the FRU v TWRCARD
list.
in the FRU List.
Problem determination: No additional problem Follow the instructions for the items listed in the FRU
determination. list.
v AIRMOVR in the FRU List.
determination.
Failing Item:

11007651 • 11007681
v AIRMOVR Problem determination: No additional problem

Failing Item:
11007651 v AIRMOVR
Explanation: A problem was detected with a fan v TWRCARD
Install the fan if it is missing; replace it if already 11007671
the FRU list. Explanation: A problem was detected with a fan
Response: Follow the instructions for the items listed Install the fan if it is missing; replace it if already
in the FRU List. installed. Follow the instructions for the items listed in
Problem determination: No additional problem the FRU list.
Failing Item:
11007660 v AIRMOVR
Explanation: A fan is operating at the wrong speed. v TWRCARD
list. 11007680
Response: Follow the instructions for the items listed Explanation: A fan is operating at the wrong speed.
in the FRU List. Follow the instructions for the items listed in the FRU
Problem determination: No additional problem list.
Failing Item:
11007661 v AIRMOVR
Explanation: A problem was detected with a fan v TWRCARD
Install the fan if it is missing; replace it if already 11007681
the FRU list. Explanation: A problem was detected with a fan
Problem determination: No additional problem the FRU list.
Failing Item:
11007670 v AIRMOVR
Explanation: A fan is operating at the wrong speed. v TWRCARD
list.
in the FRU List.

11007690 • 11008400
v AIRMOVR
11007690
v TWRCARD
list. 110076B0
Response: Follow the instructions for the items listed Explanation: A problem was detected with a fan.
in the FRU List. Follow the instructions for the items listed in the FRU
list.
in the FRU List.
Failing Item:
v AIRMOVR
determination.
v TWRCARD
Failing Item:
v AIRMOVR
11007691
v TWRCARD
Explanation: A problem was detected with a fan
Install the fan if it is missing; replace it if already 110076B1
installed. Follow the instructions for the items listed in Explanation: A problem was detected with a fan
the FRU list. which can be caused by a fan not being installed.
the FRU list.
in the FRU List.
Failing Item:
v AIRMOVR
determination.
v TWRCARD
Failing Item:
v AIRMOVR
110076A0
v TWRCARD
Explanation: A problem was detected with a fan.
list. 110076C0
Response: Follow the instructions for the items listed Explanation: Fan fault on a GX++ adapter card
v AIRMOVR
v TWRCARD 110076C1
Explanation: Fan fault on a GX++ adapter card
110076A1 Response: Follow the instructions for the items listed
Explanation: A problem was detected with a fan in the FRU List.
which can be caused by a fan not being installed. Problem determination: No additional problem
Install the fan if it is missing; replace it if already determination.
the FRU list.
11008400
in the FRU List. Explanation: No VPD was found due to invalid
bypass
in the FRU List.
Failing Item:

11008402 • 11008416

11008409
determination.
Explanation: No processor installed
Failing Item:
v AJDG301 Response: Follow the instructions for the items listed
in the FRU List.

determination.
Explanation: Unable to collect VPD
Failing Item:
v VPDPART
in the FRU List.
v TWRCARD
determination.
11008413
Failing Item:
Explanation: Invalid processor VPD
v VPDPART
v TWRCARD Response: Follow the instructions for the items listed
in the FRU List.

determination.
Explanation: Processor unit VPD mismatch
Failing Item:
v VPDPART
in the FRU List.
v TWRCARD
determination.
11008414
Failing Item:
Explanation: Invalid processor VPD
v VPDPART
in the FRU List.

determination.
Failing Item:
v VPDPART
in the FRU List.
v TWRCARD
determination.
11008415
Failing Item:
Explanation: Invalid processor 3 VPD
v VPDPART
in the FRU List.

determination.
Failing Item:
v ANYPROC
in the FRU List.
11008416
determination.
Explanation: Invalid processor 4 VPD
Failing Item:
v VPDPART Response: Follow the instructions for the items listed
in the FRU List.
v TWRCARD
determination.
Failing Item:

11008423 • 11008451
v ANYPROC Problem determination: No additional problem

determination.
Explanation: No processor VPD v VPDPART

Problem determination: No additional problem Explanation: A drawer was added to a system that
determination. has TurboMode enabled, but the newly-added drawer
is not TurboMode-capable.
Failing Item:
v VPDPART
in the FRU List.
v TWRCARD
determination.
11008424
Failing Item:
Explanation: No processor VPD
v VPDPART
in the FRU List.
11008444
Explanation: A TurboMode register failed.
determination.
Failing Item:
in the FRU List.
v VPDPART
v TWRCARD
determination.
Failing Item:
11008430
v VPDPART
Explanation: The configuration ID is incorrect.
in the FRU List.
Explanation: SPCN configuration mismatch
in the FRU List.
Failing Item:
v IDPART
determination.
Failing Item:
11008432
v PWR1918
Explanation: The configuration ID is incorrect.
v TWRCARD
in the FRU List.
11008451
Explanation: SPCN configuration mismatch
determination.
Failing Item:
in the FRU List.
v IDPART
determination.
11008442
Failing Item:
Explanation: An attempt was made to enable
v PWR1918
TurboMode, but one or more processor cards in the
system is not TurboMode-capable. v TWRCARD

in the FRU List.

11008452 • 110084A1

11008452
determination.
Explanation: Wrong power supply installed.
Failing Item:
in the FRU List.
v TWRCARD
determination.
11008457
Failing Item:
Explanation: A power supply is missing or
v PWRSPLY incompatible.
v TWRCARD
in the FRU List.
11008453
Explanation: There is an extra processor voltage determination.
regulator in the system.
Failing Item:
in the FRU List.
determination.
Explanation: A power supply is missing or
Failing Item: incompatible.
v PWR1918
Explanation: A fan is installed at location Un-A3 in a Failing Item:
single-socket system. This configuration is not valid.
v PWRSPLY
in the FRU List.
11008460
Explanation: All PWR nodes guarded
determination.
Failing Item:
v PWR1918
v TWRCARD
determination.
11008455
11008480
Explanation: Power supply missing
Explanation: The DIMM or DIMM controller ID data
Response: Follow the instructions for the items listed is missing or corrupt.
in the FRU List.
Problem determination: No additional problem logged for information only.
determination.
v PWRSPLY Failing Item:
v TWRCARD v FSPSP04
11008456 110084A1
Explanation: Power supply missing Explanation: Invalid power distribution backplane
Response: Follow the instructions for the items listed VPD
in the FRU List.

110084A2 • 11008704

11008700
in the FRU List.
Explanation: An error on the path validation occurred.
in the FRU list.
Failing Item:
v VPDPART Problem determination: No additional problem
determination.
110084A2 Failing Item:

v PWR2402
Explanation: Power distribution backplane mismatch
11008701
in the FRU List.
in the FRU list.
Failing Item:
v VPDPART Problem determination: No additional problem
determination.
v TWRCARD
Failing Item:
110084A3 v PWR2402
Explanation: Invalid service processor card VPD

11008702
in the FRU List. Explanation: An error on the path validation occurred.
determination. in the FRU list.
Failing Item: Problem determination: No additional problem

determination.
v VPDPART
v TWRCARD Failing Item:
v PWR2402
110084A4
11008703
Explanation: Service processor card mismatch.
in the FRU list.
determination.
Failing Item:
v VPDPART Failing Item:
v TWRCARD v PWR2402
110084B0 11008704
Explanation: An error occurred during drawer Explanation: A pin state mis-match, normal presence
recovery. detected.
in the FRU List. in the FRU list.

Failing Item:
v PWR2402

11008710 • 1100871D

11008710
determination.
Explanation: DCA 1 UART communication fault
in the FRU list.
determination.
in the FRU list.
11008711
determination.
in the FRU list.
determination.
in the FRU list.
11008712
determination.
Response: Follow the instructions for the items listed 1100871A
in the FRU list.
determination.
in the FRU list.
11008713
determination.
Response: Follow the instructions for the items listed 1100871B
in the FRU list.
determination.
in the FRU list.
11008714
determination.
Response: Follow the instructions for the items listed 1100871C
in the FRU list.
determination.
in the FRU list.
11008715
determination.
Response: Follow the instructions for the items listed 1100871D
in the FRU list.
determination.
in the FRU list.
11008716
determination.
in the FRU list.

1100871E • 1100B002
1100871E 11008803
Explanation: DCA 15 UART communication fault Explanation: A UPIC cable to the system control
drawer connection card is missing.
in the FRU list. Response: Follow the instructions for the items listed
in the FRU List.
determination.
1100871F Failing Item:
Explanation: DCA 16 UART communication fault v CBLALL

in the FRU list. 1100A000
Problem determination: No additional problem Explanation: A def file read failure occurred.
in the FRU List.
Explanation: A UPIC cable to the system control determination.
drawer connection card is missing. Failing Item:
Response: Follow the instructions for the items listed v FSPSP04
in the FRU List.
determination.
Explanation: Enable mismatch on the power supply.
Failing Item:
v CBLALL in the FRU List.
Explanation: A UPIC cable to the system control Failing Item:
v FSPSP04
in the FRU List.
1100B001
determination.
Failing Item:
in the FRU List.
v CBLALL
determination.
11008802
Failing Item:
Explanation: A UPIC cable to the system control
v FSPSP04
1100B002
in the FRU List.
in the FRU List.
Failing Item:
v CBLALL Problem determination: No additional problem
determination.
Failing Item:
v FSPSP04

1100B003 • 1100B00C
1100B003 1100B008
Explanation: Enable mismatch on the power supply. Explanation: Enable mismatch on the power supply.
v FSPSP04 v FSPSP04
1100B004 1100B009
v FSPSP04 v FSPSP04
1100B005 1100B00A
v FSPSP04 v FSPSP04
1100B006 1100B00B
v FSPSP04 v FSPSP04
1100B007 1100B00C
v FSPSP04 v FSPSP04

1100B00D • 1100B089

1100B00D
determination.
Response: Follow the instructions for the items listed 1100B084
in the FRU List.
determination.
in the FRU List.
Failing Item:
v FSPSP04 determination.
1100B00E 1100B085
Failing Item:
v FSPSP04 1100B086
1100B00F
Explanation: Enable mismatch on the power supply. in the FRU List.
determination. 1100B087
Failing Item: Explanation: Enable mismatch on the power supply.
v FSPSP04 Response: Follow the instructions for the items listed
in the FRU List.
1100B080 Problem determination: No additional problem
Explanation: Enable mismatch on the power supply. determination.

in the FRU List. 1100B088
Problem determination: No additional problem Explanation: Enable mismatch on the power supply.
in the FRU List.

Problem determination: No additional problem Explanation: Enable mismatch on the power supply.
in the FRU List.

in the FRU List.

1100B08A • 1100B103

1100B08A
determination.
Failing Item:
Response: Follow the instructions for the items listed v FSPSP04
in the FRU List.
determination.
Explanation: Enable mismatch on voltage regulator
module (VRM).
1100B08B
Explanation: Enable mismatch on the power supply. in the FRU List.
Problem determination: No additional problem Failing Item:
determination.
v FSPSP04
1100B08C
1100B101
Response: Follow the instructions for the items listed module (VRM).
in the FRU List.
determination.
determination.
1100B08D
Failing Item:
Explanation: Enable mismatch on the power supply. v FSPSP04
Problem determination: No additional problem Explanation: Enable mismatch on voltage regulator
determination. module (VRM).
1100B08E in the FRU List.
Explanation: Enable mismatch on the power supply. Problem determination: No additional problem
Problem determination: No additional problem v FSPSP04
determination.
1100B103
1100B08F
Explanation: Enable mismatch on the power supply. module (VRM).
Failing Item:
1100B0FF v FSPSP04
in the FRU List.

1100B104 • 1100B10D
Failing Item:
1100B104
v FSPSP04
module (VRM).
1100B109
in the FRU List. Explanation: Enable mismatch on voltage regulator
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B105
v FSPSP04
module (VRM).
1100B10A
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B106
v FSPSP04
module (VRM).
1100B10B
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B107
v FSPSP04
module (VRM).
1100B10C
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B108
v FSPSP04
module (VRM).
1100B10D
module (VRM).
determination.

1100B10E • 1100B116

1100B112
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B10E
Failing Item:
v FSPSP04
module (VRM).
1100B113
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B10F
Failing Item:
v FSPSP04
module (VRM).
1100B114
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B110
Failing Item:
v FSPSP04
module (VRM).
1100B115
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B111
Failing Item:
v FSPSP04
module (VRM).
1100B116
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.

1100B117 • 1100B125
v FSPSP04 in the FRU List.
1100B117 determination.
Explanation: Enable mismatch on voltage regulator Failing Item:

module (VRM). v FSPSP04





1100B126 • 1100B12F
Failing Item:
1100B126
v FSPSP04
module (VRM).
1100B12B
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B127
v FSPSP04
module (VRM).
1100B12C
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B128
v FSPSP04
module (VRM).
1100B12D
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B129
v FSPSP04
module (VRM).
1100B12E
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B12A
v FSPSP04
module (VRM).
1100B12F
module (VRM).
determination.

1100B130 • 1100B180

1100B134
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B130
Failing Item:
v FSPSP04
module (VRM).
1100B135
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B131
Failing Item:
v FSPSP04
module (VRM).
1100B136
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B132
Failing Item:
v FSPSP04
module (VRM).
1100B137
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B133
Failing Item:
v FSPSP04
module (VRM).
1100B180
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.

1100B181 • 1100B189






1100B18A • 1100B193
Failing Item:
1100B18A
v FSPSP04
module (VRM).
1100B18F
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B18B
v FSPSP04
module (VRM).
1100B190
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B18C
v FSPSP04
module (VRM).
1100B191
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B18D
v FSPSP04
module (VRM).
1100B192
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B18E
v FSPSP04
module (VRM).
1100B193
module (VRM).
determination.

1100B194 • 1100B19C

1100B198
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B194
Failing Item:
v FSPSP04
module (VRM).
1100B199
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B195
Failing Item:
v FSPSP04
module (VRM).
1100B19A
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B196
Failing Item:
v FSPSP04
module (VRM).
1100B19B
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B197
Failing Item:
v FSPSP04
module (VRM).
1100B19C
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.

1100B19D • 1100B1A5
1100B19D determination.

in the FRU List. 1100B1A2
1100B19E determination.

1100B19F determination.

1100B1A0 determination.

1100B1A1 determination.


1100B1A6 • 1100B1AF
Failing Item:
1100B1A6
v FSPSP04
module (VRM).
1100B1AB
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B1A7
v FSPSP04
module (VRM).
1100B1AC
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B1A8
v FSPSP04
module (VRM).
1100B1AD
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B1A9
v FSPSP04
module (VRM).
1100B1AE
module (VRM).
in the FRU List.
Failing Item:
v FSPSP04
determination.
Failing Item:
1100B1AA
v FSPSP04
module (VRM).
1100B1AF
module (VRM).
determination.

1100B1B0 • 1100B1FF

1100B1B4
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B1B0
Failing Item:
v FSPSP04
module (VRM).
1100B1B5
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B1B1
Failing Item:
v FSPSP04
module (VRM).
1100B1B6
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B1B2
Failing Item:
v FSPSP04
module (VRM).
1100B1B7
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.
1100B1B3
Failing Item:
v FSPSP04
module (VRM).
1100B1FF
in the FRU List.
module (VRM).
determination.
Failing Item:
in the FRU List.
v FSPSP04
determination.

1100C000 • 1100D007
Failing Item:
1100D002
v FSPSP04
Explanation: A digital power system sweep (DPSS)
primary power on sequence timeout occurred.
1100C000
Explanation: A thermal object creation failure in the FRU List.
occurred.
in the FRU List.
Problem determination: No additional problem 1100D003
determination.
Failing Item: secondary power on sequence failure occurred.
v FSPSP04
in the FRU List.
1100C001
Explanation: A fan creation failure occurred. determination.
in the FRU List. 1100D004
Problem determination: No additional problem Explanation: A digital power system sweep (DPSS)
determination. secondary power on sequence timeout occurred.
1100C002 determination.
Explanation: A cooling zone creation failed.

1100D005
in the FRU List. Explanation: A digital power system sweep (DPSS)
secondary power off sequence failure occurred.
in the FRU List.
Failing Item:
v FSPSP04 determination.
1100D000 1100D006
Explanation: A digital power system sweep (DPSS) Explanation: A digital power system sweep (DPSS)
power sequencing logic failure occurred. secondary power off sequence timeout occurred.
1100D001 1100D007
Explanation: A digital power system sweep (DPSS) Explanation: A digital power system sweep (DPSS)
primary power on sequence failure occurred. power off sequence failure occurred.

1100D008 • 169C3029

1100D008
determination.
power off sequence timeout occurred.
1100D00C
in the FRU List.
code corruption was detected.
determination.
1100D009
determination.
access failure occurred.
1100D00D
in the FRU List.
PGOOD fault agreement failure occurred.
determination.
1100D00A
determination.
read failure occurred.
1100D00E
Explanation: A digital power system sweep (DPSS) is
in the FRU List.
missing.
determination.
1100D00B
determination.
write failure occurred.
in the FRU List.
(169C) Reference codes

Explanation: Disk device returned wrong response to
169C102E
IOA.
Explanation: Out of alternate sectors for disk storage.
Failing Item:
Failing Item: v DISKDRV
v DISKDRV v STORIOA
v SASCABL
169C3002 v SASEXP
Explanation: Addressed device failed to respond to
selection. 169C3020
Failing Item: Explanation: Replacement device is not supported.
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v DEVBPLN
v STORIOA
v SASCABL
v SASCABL
v SASEXP
169C3029
169C3010

169C3100 • 169C4100
Explanation: A device replacement has occurred.

169C3130
Explanation: Device Licensed Internal Code.
Response: The device is not supported with the level
of code currently on the system. Contact your next
169C3100
level of support.
Explanation: Device bus interface error occurred.
Failing Item:
Failing Item: v SVCDOCS
v DISKDRV
v STORIOA 169C34FF
v SASCABL
Explanation: Format in progress.
v SASEXP
169C3109
Explanation: IOA timed out a disk command. 169C4041
Failing Item: Explanation: Incomplete multipath connection.
v DISKDRV
Response: Incomplete multipath connection between
v STORIOA device backplane and device.
v SASCABL
Failing Item:
v SASEXP
v SIP3146
169C310C
169C4060
Explanation: Device bus error.
Explanation: Multipath redundancy level reduced.
Failing Item:
Response: A redundant disk unit connection has
v SIP3250 failed.
v DISKDRV
Failing Item:
v STORIOA
v SIP3153
v SASCABL
169C310D
v SASEXP
Failing Item: 169C4061
v SIP3250 Explanation: Multipath redundancy level increased.
v DISKDRV
Response: A redundant disk unit connection has been
v STORIOA restored. No service action is required.
169C3110 169C4100
Explanation: Device bus interface error occurred. Explanation: Device bus fabric error.
v DISKDRV v SIP3152
v STORIOA v SASCABL
v SASCABL v SASEXP
v SASEXP v DEVBPLN
v STORIOA
v DISKDRV

169C7000 • 169CFFFC
169C7000 169CFFF7
Explanation: Disk sector read error. Explanation: Temporary disk data error.
Response: No action required. This reference code is Response: If this event appears in a serviceable event
logged for information only. view, work with the failing item list found there. If this
event does not appear in a serviceable event view, no
service action is required.
169C7001
Failing Item:
Explanation: Temporary disk data error.
v DISKDRV
Response: If this event appears in a serviceable event
view, work with the failing item list found there. If this
event does not appear in a serviceable event view, no 169CFFF9
service action is required. Explanation: Temporary disk data error.
Failing Item: Response: If this event appears in a serviceable event
v DISKDRV view, work with the failing item list found there. If this
169C70DD
Failing Item:
Explanation: System log entry only, no service action
required. v DISKDRV
169CFFF3 169CFFFA
Explanation: Disk media format not valid. Explanation: Temporary disk bus error.

v DISKDRV
169CFFF4
Failing Item:
Explanation: Disk device problem. v DISKDRV
Failing Item: v STORIOA
v DISKDRV v SASCABL
v STORIOA v SASEXP
169CFFF5 169CFFFB
Explanation: Disk sector read error. Explanation: SAS bus reset occurred.
Response: If this event appears in a serviceable event Response: No action required. This reference code is
view, work with the failing item list found there. If this logged for information only.
169CFFFC
Failing Item:
Explanation: Soft device bus error.
v DISKDRV
169CFFF6 event does not appear in a serviceable event view, no
Explanation: Disk device detected recoverable error. service action 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 SIP3250
event does not appear in a serviceable event view, no v DISKDRV
v STORIOA
Failing Item:
v DISKDRV

169CFFFD • 17503162
169CFFFD 169CFFFE
Explanation: Soft device bus error. Explanation: Temporary disk bus error.
Response: If this event appears in a serviceable event Response: If this event appears in a serviceable event
view, work with the failing item list found there. If this view, work with the failing item list found there. If this
event does not appear in a serviceable event view, no event does not appear in a serviceable event view, no
service action is required. service action is required.
v SIP3250 v SIP3150
v DISKDRV
v STORIOA

Explanation: Fibre Channel interface error occurred.
17503002
Failing Item:
Explanation: Addressed device is not responding.
v FCINTF
Failing Item:
v FCDEV
v FCPORT
v FCIOA
v FCDEV
v OPT_CLN
v FCIOA
v FCINTF
17503109
v OPT_CLN
Explanation: IOP timed out a disk command.

v FCDEV
IOP. v FCINTF
v FCIOA
Failing Item:
v OPT_CLN
v FCDEV
v FCIOA
17503160
v OPT_CLN
Explanation: The volume in use is no longer
accessible.
17503020
Response: The storage subsystem configuration was
Explanation: Storage subsystem configuration error.
changed, causing the volume in use to no longer be
Response: If an MES is being installed, verify the accessible.
configuration.
Failing Item:
Failing Item: v FCDEV
v FCDEV
v FCIOA 17503161
v OPT_CLN
accessible.
17503029
Response: Storage subsystem copy services functions
Explanation: This SRC is surfaced when the IOP have caused the volume in use to no longer be
detects that a device has changed Serial numbers. A accessible.
device replacement has occurred.
Failing Item:
Response: No action required. This reference code is v FCDEV
17503162
17503100
Explanation: The volume has been released.

175034FF • 198B3020
The storage subsystem configuration was changed. The Response: If this event appears in a serviceable event
volume that was not in use was removed and is no view, work with the failing item list found there. If this
longer accessible. event does not appear in a serviceable event view, no
logged for information only. Failing Item:
v FCDEV
175034FF
Explanation: Format in progress. 1750FFFA
Response: The device indicated that a format is in Explanation: Disk device wrong response was
progress. When the format is complete, the device recovered by the IOP.
should be usable. No action is required. This reference Response: If this event appears in a serviceable event
code is logged for information only. view, work with the failing item list found there. If this
1750FFF3 service action is required.
Explanation: Disk media format bad. Failing Item:

v FCDEV
Failing Item:
v FCIOA
v FCDEV
v OPT_CLN
1750FFF4
1750FFFE
Explanation: Disk device problem.
Explanation: Temporary Fibre Channel interface error.
Failing Item:
v FCDEV
Explanation: Disk sector read error. Failing Item:

Failing Item: v FCINTF
v FCDEV v FCDEV
v FCIOA
1750FFF6 v OPT_CLN
Explanation: Disk device detected recoverable error.
(198B) Reference codes

198B102E 198B3010
Explanation: Out of alternate sectors for disk storage. Explanation: Disk device returned wrong response to
IOA.
Failing Item:
v DISKDRV Failing Item:
v DISKDRV
198B3002 v STORIOA
v SASCABL
selection. v SASEXP
Failing Item:
198B3020
v DISKDRV
v STORIOA Explanation: Replacement device is not supported.
v DEVBPLN Failing Item:
v SASCABL v DISKDRV
v SASEXP v STORIOA

198B3029 • 198B4100
v SASCABL
198B3130
198B3029
Response: No action required. This reference code is level of support.
Failing Item:
v SVCDOCS
198B3100
Explanation: Device bus interface error occurred. 198B34FF
Failing Item: Explanation: Format in progress.
v DISKDRV
v STORIOA logged for information only.
v SASCABL
v SASEXP 198B4041
Explanation: Incomplete multipath connection.
198B3109
Explanation: IOA timed out a disk command. device backplane and device.
v DISKDRV v SIP3146
v STORIOA
v SASCABL 198B4060
v SASEXP
198B310C
failed.
Failing Item:
Failing Item: v SIP3153
v SIP3250 v SASCABL
v DISKDRV v SASEXP
v STORIOA
198B4061
198B310D
Explanation: Multipath redundancy level increased.
Failing Item: restored. No service action is required.
v SIP3250
v DISKDRV 198B4100
v STORIOA Explanation: Device bus fabric error.
Failing Item:
198B3110
v SIP3152
Explanation: Device bus interface error occurred. v SASCABL
Failing Item: v SASEXP
v DISKDRV v DEVBPLN
v STORIOA v STORIOA
v SASCABL v DISKDRV
v SASEXP

198B7000 • 198BFFFC
198B7000 198BFFF7
198B7001
Failing Item:
v DISKDRV
event does not appear in a serviceable event view, no 198BFFF9
198B70DD
Failing Item:
required. v DISKDRV
198BFFF3 198BFFFA

v DISKDRV
198BFFF4
Failing Item:
v DISKDRV v SASCABL
v STORIOA v SASEXP
198BFFF5 198BFFFB
198BFFFC
Failing Item:
v DISKDRV
198BFFF6 event does not appear in a serviceable event view, no

v STORIOA
Failing Item:
v DISKDRV

198BFFFD • 198C3110
198BFFFD 198BFFFE
v SIP3250 v SIP3150
v DISKDRV
v STORIOA

198C102E
198C3100
Failing Item:
v DISKDRV
Failing Item:
v DISKDRV
198C3002
v STORIOA
v SASCABL
selection.
v SASEXP
Failing Item:
v DISKDRV
198C3109
v STORIOA
Explanation: IOA timed out a disk command.
v DEVBPLN
v SASCABL Failing Item:
v SASEXP v DISKDRV
v STORIOA
198C3010 v SASCABL
v SASEXP
IOA.
198C310C
Failing Item:
v DISKDRV Explanation: Device bus error.
v STORIOA Failing Item:
v SASCABL v SIP3250
v SASEXP v DISKDRV
v STORIOA
198C3020
Explanation: Replacement device is not supported. 198C310D
Failing Item: Explanation: Device bus error.

v STORIOA v SIP3250
v SASCABL v DISKDRV
v STORIOA
198C3029
Explanation: A device replacement has occurred. 198C3110
Response: No action required. This reference code is Explanation: Device bus interface error occurred.

198C3130 • 198CFFF6
Failing Item: v DEVBPLN

v DISKDRV v STORIOA
v STORIOA v DISKDRV
v SASCABL
v SASEXP 198C7000
Explanation: Disk sector read error.
198C3130
Explanation: Device Licensed Internal Code. logged for information only.
of code currently on the system. Contact your next 198C7001
level of support.
Failing Item:
v SVCDOCS view, work with the failing item list found there. If this
198C34FF service action is required.
Explanation: Format in progress. Failing Item:

v DISKDRV
198C70DD
198C4041 Explanation: System log entry only, no service action
required.
198CFFF3
device backplane and device.
Explanation: Disk media format not valid.
Failing Item:
v SIP3146 Failing Item:
v DISKDRV
198C4060
198CFFF4
failed. Failing Item:
v SIP3153 v STORIOA
v SASCABL
v SASEXP 198CFFF5
198C4061 Response: If this event appears in a serviceable event
Explanation: Multipath redundancy level increased. view, work with the failing item list found there. If this
Response: A redundant disk unit connection has been service action is required.
restored. No service action is required.
Failing Item:
v DISKDRV
198C4100
Explanation: Device bus fabric error.
198CFFF6
Failing Item:
v SIP3152
v SASCABL
v SASEXP

198CFFF7 • 198D3010
event does not appear in a serviceable event view, no Explanation: SAS bus reset occurred.
Failing Item: logged for information only.
v DISKDRV
198CFFFC
198CFFF7 Explanation: Soft device bus error.
Explanation: Temporary disk data error. Response: If this event appears in a serviceable event
Response: If this event appears in a serviceable event view, work with the failing item list found there. If this
view, work with the failing item list found there. If this event does not appear in a serviceable event view, no
event does not appear in a serviceable event view, no service action is required.
service action is required. Failing Item:
v DISKDRV v DISKDRV
v STORIOA
198CFFF9
Explanation: Temporary disk data error. 198CFFFD
Response: If this event appears in a serviceable event Explanation: Soft device bus error.
view, work with the failing item list found there. If this Response: If this event appears in a serviceable event
event does not appear in a serviceable event view, no view, work with the failing item list found there. If this
service action is required. event does not appear in a serviceable event view, no
Failing Item: service action is required.
v SIP3250
198CFFFA v DISKDRV
Explanation: Temporary disk bus error. v STORIOA

view, work with the failing item list found there. If this 198CFFFE
event does not appear in a serviceable event view, no Explanation: Temporary disk bus error.
Failing Item: view, work with the failing item list found there. If this
v DISKDRV event does not appear in a serviceable event view, no
v STORIOA service action is required.
v SASEXP v SIP3150
198CFFFB
(198D) Reference codes

v DISKDRV
198D102E
v STORIOA
v DEVBPLN
Failing Item: v SASCABL
v DISKDRV v SASEXP
198D3002 198D3010
Explanation: Addressed device failed to respond to Explanation: Disk device returned wrong response to
selection. IOA.

198D3020 • 198D4061
v DISKDRV
198D3110
v STORIOA
v SASCABL
v SASEXP Failing Item:
v DISKDRV
198D3020 v STORIOA
v SASCABL
Explanation: Replacement device is not supported.
v SASEXP
Failing Item:
v DISKDRV
198D3130
v STORIOA
v SASCABL
198D3029
level of support.
Failing Item:
Response: No action required. This reference code is v SVCDOCS
198D34FF
198D3100
v DISKDRV
v STORIOA 198D4041
v SASCABL
v SASEXP
198D3109
Failing Item:
v SIP3146
Failing Item:
v DISKDRV 198D4060
v STORIOA
v SASCABL
v SASEXP
failed.
Failing Item:
198D310C
v SIP3153
v SASCABL
v SIP3250
v DISKDRV 198D4061
v STORIOA
198D310D
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

198D4100 • 198DFFFB
v DISKDRV
198D4100
198DFFF6
Failing Item:
v SIP3152
v SASCABL
v SASEXP event does not appear in a serviceable event view, no
v DEVBPLN service action is required.
v DISKDRV v DISKDRV
198D7000 198DFFF7
198D7001 service action is required.
Explanation: Temporary disk data error. Failing Item:

v DISKDRV
event does not appear in a serviceable event view, no 198DFFF9
Failing Item:
198D70DD service action is required.
Explanation: System log entry only, no service action Failing Item:

required. v DISKDRV
198DFFF3 198DFFFA
198DFFF4
Failing Item:
v DISKDRV
v DISKDRV v SASCABL
v STORIOA v SASEXP
198DFFF5 198DFFFB
Failing Item:

198DFFFC • 198E310C

198DFFFC
Failing Item:
Response: If this event appears in a serviceable event v SIP3250
v DISKDRV
service action is required. v STORIOA
Failing Item:
198DFFFE
v SIP3250
v DISKDRV Explanation: Temporary disk bus error.
v STORIOA Response: If this event appears in a serviceable event
198DFFFD
Failing Item:
(198E) Reference codes

v SASCABL
198E102E
198E3029
Failing Item:
v DISKDRV
198E3002
Explanation: Addressed device failed to respond to 198E3100
selection.
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v DEVBPLN
v SASCABL
v SASCABL
v SASEXP
v SASEXP
198E3109
198E3010
IOA. Failing Item:
v DISKDRV v STORIOA
v STORIOA v SASCABL
v SASCABL v SASEXP
v SASEXP
198E310C
198E3020 Explanation: Device bus error.
Explanation: Replacement device is not supported. Failing Item:
v DISKDRV v DISKDRV
v STORIOA v STORIOA

198E310D • 198EFFF4
198E310D 198E4061
Explanation: Device bus error. Explanation: Multipath redundancy level increased.
Failing Item: Response: A redundant disk unit connection has been
v SIP3250 restored. No service action is required.
v DISKDRV
v STORIOA 198E4100
198E3110 Failing Item:
Explanation: Device bus interface error occurred. v SIP3152
v DISKDRV v SASEXP
v STORIOA v DEVBPLN
v SASCABL v STORIOA
v SASEXP v DISKDRV
198E3130 198E7000
Explanation: Device Licensed Internal Code. Explanation: Disk sector read error.
Response: The device is not supported with the level Response: No action required. This reference code is
of code currently on the system. Contact your next logged for information only.
level of support.
Failing Item: 198E7001
v SVCDOCS Explanation: Temporary disk data error.
198E34FF view, work with the failing item list found there. If this
Failing Item:
v DISKDRV
198E4041
198E70DD
Response: Incomplete multipath connection between required.
Failing Item: 198EFFF3
v SIP3146
Failing Item:
198E4060
v DISKDRV
Response: A redundant disk unit connection has 198EFFF4
failed.
Failing Item:
Failing Item:
v SIP3153
v DISKDRV
v SASCABL
v STORIOA
v SASEXP

198EFFF5 • 19A13002
Failing Item:
198EFFF5
v DISKDRV
v STORIOA
Response: If this event appears in a serviceable event v SASCABL
v SASEXP
198EFFFB
Failing Item:
v DISKDRV Explanation: SAS bus reset occurred.
198EFFF6 logged for information only.

198EFFFC
view, work with the failing item list found there. If this Explanation: Soft device bus error.
event does not appear in a serviceable event view, no Response: If this event appears in a serviceable event
service action is required. view, work with the failing item list found there. If this
Failing Item: event does not appear in a serviceable event view, no
v DISKDRV
Failing Item:
198EFFF7 v SIP3250
v DISKDRV
v STORIOA
event does not appear in a serviceable event view, no 198EFFFD
service action is required. Explanation: Soft device bus error.
198EFFF9
Failing Item:
v SIP3250
v DISKDRV
event does not appear in a serviceable event view, no v STORIOA
Failing Item: 198EFFFE
198EFFFA view, work with the failing item list found there. If this
Explanation: Temporary disk bus error.
Failing Item:
event does not appear in a serviceable event view, no v SIP3150
(19A1) Reference codes

v DISKDRV
19A1102E
19A13002
Failing Item:

19A13010 • 19A14041

19A1310C
selection.
Failing Item:
v STORIOA v SIP3250
v DEVBPLN v DISKDRV
v SASCABL v STORIOA
v SASEXP
19A1310D
19A13010 Explanation: Device bus error.
Explanation: Disk device returned wrong response to Failing Item:
IOA. v SIP3250
v DISKDRV v STORIOA
v STORIOA
v SASCABL 19A13110
v SASEXP Explanation: Device bus interface error occurred.
Failing Item:
19A13020
v DISKDRV
Explanation: Replacement device is not supported. v STORIOA
v DISKDRV v SASEXP
v STORIOA
v SASCABL 19A13130
19A13029
Explanation: A device replacement has occurred. of code currently on the system. Contact your next
level of support.
v SVCDOCS
19A13100
Explanation: Device bus interface error occurred. 19A134FF

v DISKDRV Response: No action required. This reference code is
v SASCABL
v SASEXP 19A14041
19A13109 Response: Incomplete multipath connection between

v DISKDRV v SIP3146
v STORIOA
v SASCABL
v SASEXP

19A14060 • 19A1FFFA
19A14060 19A1FFF4
Explanation: Multipath redundancy level reduced. Explanation: Disk device problem.
Response: A redundant disk unit connection has Failing Item:
failed. v DISKDRV
v SIP3153
v SASCABL 19A1FFF5
v SASEXP Explanation: Disk sector read error.
19A14061 view, work with the failing item list found there. If this
Explanation: Multipath redundancy level increased. event does not appear in a serviceable event view, no
restored. No service action is required. Failing Item:
v DISKDRV
19A14100
19A1FFF6
Failing Item:
v SIP3152 Response: If this event appears in a serviceable event
v SASCABL
v SASEXP service action is required.
v DEVBPLN
Failing Item:
v STORIOA
v DISKDRV
v DISKDRV
19A1FFF7
19A17000
Response: No action required. This reference code is view, work with the failing item list found there. If this
logged for information only. event does not appear in a serviceable event view, no
Explanation: Temporary disk data error. v DISKDRV
view, work with the failing item list found there. If this 19A1FFF9
Failing Item:
19A170DD Failing Item:
Explanation: System log entry only, no service action v DISKDRV
required.
19A1FFFA
19A1FFF3

19A1FFFB • 19A33109
Failing Item:
19A1FFFD
v DISKDRV
v STORIOA
v SASCABL Response: If this event appears in a serviceable event
v SASEXP
19A1FFFB
Failing Item:
Explanation: SAS bus reset occurred. v SIP3250
Response: No action required. This reference code is v DISKDRV
logged for information only. v STORIOA
19A1FFFC 19A1FFFE
v SIP3250 v SIP3150
v DISKDRV
v STORIOA

19A3102E 19A33020
Explanation: Out of alternate sectors for disk storage. Explanation: Replacement device is not supported.
v DISKDRV v DISKDRV
v STORIOA
19A33002 v SASCABL
selection. 19A33029
Failing Item: Explanation: A device replacement has occurred.
v DEVBPLN
v SASCABL 19A33100
Failing Item:
19A33010
v DISKDRV
Explanation: Disk device returned wrong response to v STORIOA
IOA.
v SASCABL
v DISKDRV
v STORIOA 19A33109
v SASCABL
v SASEXP
Failing Item:

19A3310C • 19A3FFF3
v DISKDRV
19A34060
v STORIOA
v SASCABL
v SASEXP Response: A redundant disk unit connection has
failed.
19A3310C Failing Item:

v SIP3153
v SASCABL
Failing Item:
v SASEXP
v SIP3250
v DISKDRV
19A34061
v STORIOA
19A3310D Response: A redundant disk unit connection has been

Failing Item: 19A34100
v SIP3250
v DISKDRV
Failing Item:
v STORIOA
v SIP3152
v SASCABL
19A33110
v SASEXP
v DEVBPLN
v DISKDRV v DISKDRV
v STORIOA
v SASCABL 19A37000
v SASEXP
19A33130
Response: The device is not supported with the level 19A37001
level of support.
Failing Item:
v SVCDOCS event does not appear in a serviceable event view, no
19A334FF Failing Item:
Explanation: Format in progress. v DISKDRV
logged for information only. 19A370DD
19A34041 required.

19A3FFF3
device backplane and device. Explanation: Disk media format not valid.

v SIP3146 v DISKDRV

19A3FFF4 • 19A3FFFE
Failing Item:
19A3FFF4
v DISKDRV
v STORIOA
v DISKDRV v SASEXP
v STORIOA
19A3FFFB
19A3FFF5
Explanation: SAS bus reset occurred.
Response: If this event appears in a serviceable event logged for information only.
19A3FFFC
Failing Item:
v DISKDRV Response: If this event appears in a serviceable event
19A3FFF6 service action is required.
Explanation: Disk device detected recoverable error. Failing Item:
view, work with the failing item list found there. If this v DISKDRV
v STORIOA
Failing Item:
19A3FFFD
v DISKDRV
19A3FFF7 Response: If this event appears in a serviceable event

Explanation: Temporary disk data error. event does not appear in a serviceable event view, no
Response: If this event appears in a serviceable event service action is required.
view, work with the failing item list found there. If this Failing Item:
v SIP3250
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
19A3FFFE
19A3FFF9
Failing Item:
Failing Item:
v SIP3150
v DISKDRV
19A3FFFA

19A4102E • 19A434FF

19A4102E 19A43109
Explanation: Out of alternate sectors for disk storage. Explanation: IOA timed out a disk command.
v DISKDRV v DISKDRV
v STORIOA
19A43002 v SASCABL
Explanation: Addressed device failed to respond to v SASEXP
selection.
Failing Item: 19A4310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
19A43010 19A4310D
Explanation: Disk device returned wrong response to Explanation: Device bus error.
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
19A43110
19A43020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
19A43130
19A43029
Response: No action required. This reference code is of code currently on the system. Contact your next
logged for information only. level of support.
Failing Item:
19A43100
v SVCDOCS
Failing Item: 19A434FF
v DISKDRV Explanation: Format in progress.
v STORIOA
v SASCABL logged for information only.
v SASEXP

19A44041 • 19A4FFF9
19A44041 19A470DD
Explanation: Incomplete multipath connection. Explanation: System log entry only, no service action
required.
19A4FFF3
Failing Item:
v SIP3146 Explanation: Disk media format not valid.
Failing Item:
19A44060 v DISKDRV
19A4FFF4
failed. Explanation: Disk device problem.
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
19A4FFF5
19A44061 Explanation: Disk sector read error.
Explanation: Multipath redundancy level increased. Response: If this event appears in a serviceable event
Response: A redundant disk unit connection has been view, work with the failing item list found there. If this
restored. No service action is required. event does not appear in a serviceable event view, no

v DISKDRV
Failing Item:
19A4FFF6
v SIP3152
v SASCABL
v SASEXP Response: If this event appears in a serviceable event
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
19A47000
Explanation: Disk sector read error. 19A4FFF7
Response: No action required. This reference code is Explanation: Temporary disk data error.
19A47001 event does not appear in a serviceable event view, no
Explanation: Temporary disk data error. service action is required.

19A4FFF9
Failing Item:
v DISKDRV

19A4FFFA • 19A4FFFE

19A4FFFE
Failing Item:
19A4FFFA service action is required.
Explanation: Temporary disk bus error. Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
19A4FFFB
19A4FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
19A4FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

19B0102E • 19B034FF
(19B0) Reference codes

19B0102E 19B03109
v DISKDRV v DISKDRV
v STORIOA
19B03002 v SASCABL
selection.
Failing Item: 19B0310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
19B03010 19B0310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
19B03110
19B03020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
19B03130
19B03029
Failing Item:
19B03100
v SVCDOCS
Failing Item: 19B034FF
v STORIOA
v SASEXP

19B04041 • 19B0FFF9
19B04041 19B070DD
required.
19B0FFF3
Failing Item:
Failing Item:
19B04060 v DISKDRV
19B0FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
19B0FFF5
19B04061 Explanation: Disk sector read error.
19B04100 Failing Item:

v DISKDRV
Failing Item:
19B0FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
19B07000
Explanation: Disk sector read error. 19B0FFF7
19B07001 event does not appear in a serviceable event view, no

19B0FFF9
Failing Item:
v DISKDRV

19B0FFFA • 19B0FFFE

19B0FFFE
Failing Item:
19B0FFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
19B0FFFB
19B0FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
19B0FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

19B1102E • 19B134FF

19B1102E 19B13109
v DISKDRV v DISKDRV
v STORIOA
19B13002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
19B13010 19B1310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
19B13110
19B13020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
19B13130
19B13029
Failing Item:
19B13100
v SVCDOCS
v STORIOA
v SASEXP

19B14041 • 19B1FFF9
19B14041 19B170DD
required.
19B1FFF3
Failing Item:
Failing Item:
19B14060 v DISKDRV
19B1FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
19B1FFF5

v DISKDRV
Failing Item:
19B1FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
19B17000

19B1FFF9
Failing Item:
v DISKDRV


19B1FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
19B1FFFB
19B1FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
19B1FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

19B3102E • 19B334FF

19B3102E 19B33109
v DISKDRV v DISKDRV
v STORIOA
19B33002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
19B33010 19B3310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
19B33110
19B33020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
19B33130
19B33029
Failing Item:
19B33100
v SVCDOCS
v STORIOA
v SASEXP

19B34041 • 19B3FFF9
19B34041 19B370DD
required.
19B3FFF3
Failing Item:
Failing Item:
19B34060 v DISKDRV
19B3FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
19B3FFF5

v DISKDRV
Failing Item:
19B3FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
19B37000

19B3FFF9
Failing Item:
v DISKDRV


19B3FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
19B3FFFB
19B3FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
19B3FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

19B4102E • 19B434FF

19B4102E 19B43109
v DISKDRV v DISKDRV
v STORIOA
19B43002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
19B43010 19B4310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
19B43110
19B43020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
19B43130
19B43029
Failing Item:
19B43100
v SVCDOCS
v STORIOA
v SASEXP

19B44041 • 19B4FFF9
19B44041 19B470DD
required.
19B4FFF3
Failing Item:
Failing Item:
19B44060 v DISKDRV
19B4FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
19B4FFF5

v DISKDRV
Failing Item:
19B4FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
19B47000

19B4FFF9
Failing Item:
v DISKDRV


19B4FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
19B4FFFB
19B4FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
19B4FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

19B5102E • 19B534FF

19B5102E 19B53109
v DISKDRV v DISKDRV
v STORIOA
19B53002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
19B53010 19B5310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
19B53110
19B53020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
19B53130
19B53029
Failing Item:
19B53100
v SVCDOCS
v STORIOA
v SASEXP

19B54041 • 19B5FFF9
19B54041 19B570DD
required.
19B5FFF3
Failing Item:
Failing Item:
19B54060 v DISKDRV
19B5FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
19B5FFF5

v DISKDRV
Failing Item:
19B5FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
19B57000

19B5FFF9
Failing Item:
v DISKDRV


19B5FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
19B5FFFB
19B5FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
19B5FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

19B7102E • 19B734FF

19B7102E 19B73109
v DISKDRV v DISKDRV
v STORIOA
19B73002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
19B73010 19B7310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
19B73110
19B73020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
19B73130
19B73029
Failing Item:
19B73100
v SVCDOCS
v STORIOA
v SASEXP

19B74041 • 19B7FFF9
19B74041 19B770DD
required.
19B7FFF3
Failing Item:
Failing Item:
19B74060 v DISKDRV
19B7FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
19B7FFF5

v DISKDRV
Failing Item:
19B7FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
19B77000

19B7FFF9
Failing Item:
v DISKDRV


19B7FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
19B7FFFB
19B7FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
19B7FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

2058B990 • 210534FF

v FI00130
2058B990
v IOP
Explanation: I/O adapter hardware error detected.
v MA_BRDG
Failing Item:
v IOA

v FCIOA
21053002
v OPT_CLN
v FCPORT
v FCDEV
Failing Item:
v FCIOA
v FCDEV
v FCINTF
v FCINTF
v OPT_CLN
v FCIOA
v OPT_CLN
21053010
21053160
IOP.
Failing Item:
accessible.
v FCDEV
v FCIOA
v OPT_CLN accessible.
Failing Item:
21053020
v FCDEV
Response: If an MES is being installed, verify the 21053161
configuration.
Failing Item: accessible.
v FCDEV Response: Storage subsystem copy services functions
v FCIOA have caused the volume in use to no longer be
Failing Item:
21053029 v FCDEV
Explanation: This SRC is surfaced when the IOP
detects that a device has changed Serial numbers. A 21053162
The storage subsystem configuration was changed. The
volume that was not in use was removed and is no
longer accessible.
21053100
Explanation: Fibre Channel interface error occurred. logged for information only.
Failing Item:
v FCINTF 210534FF
v FCDEV Explanation: Format in progress.

2105FFF3 • 21073100
Response: The device indicated that a format is in Failing Item:

progress. When the format is complete, the device v FCDEV
should be usable. No action is required. This reference
2105FFFA
2105FFF3 Explanation: Disk device wrong response was

recovered by the IOP.
Explanation: Disk media format bad.
v FCDEV event does not appear in a serviceable event view, no
2105FFF4 Failing Item:
Explanation: Disk device problem. v FCDEV
v FCIOA
Failing Item:
v OPT_CLN
v FCDEV
2105FFFE
2105FFF5
Failing Item:
v FCDEV event does not appear in a serviceable event view, no
Explanation: Disk device detected recoverable error. v FCINTF
Response: If this event appears in a serviceable event v FCDEV

view, work with the failing item list found there. If this v FCIOA
event does not appear in a serviceable event view, no v OPT_CLN

21073002
Response: If an MES is being installed, verify the
configuration.
Failing Item:
Failing Item:
v FCPORT
v FCDEV
v FCDEV
v FCIOA
v FCIOA
v OPT_CLN
v FCINTF
v OPT_CLN
21073029
21073010
detects that a device has changed Serial numbers. A
Explanation: Disk device returned wrong response to device replacement has occurred.
IOP.
v FCDEV
v FCIOA 21073100
v OPT_CLN Explanation: Fibre Channel interface error occurred.
Failing Item:
21073020
v FCINTF

21073109 • 2107FFFE
v FCDEV
2107FFF3
v FCIOA
v OPT_CLN
Failing Item:
21073109 v FCDEV

2107FFF4
Failing Item:
v FCDEV
v FCINTF Failing Item:
v FCIOA v FCDEV
v OPT_CLN
2107FFF5
21073160 Explanation: Disk sector read error.
Explanation: The volume in use is no longer Failing Item:
accessible. v FCDEV
changed, causing the volume in use to no longer be 2107FFF6
accessible.
Failing Item:
v FCDEV
21073161 service action is required.
Explanation: The volume in use is no longer Failing Item:
accessible. v FCDEV
have caused the volume in use to no longer be 2107FFFA
accessible.
Explanation: Disk device wrong response was
Failing Item: recovered by the IOP.
v FCDEV
21073162 event does not appear in a serviceable event view, no
Failing Item:
The storage subsystem configuration was changed. The
volume that was not in use was removed and is no v FCDEV
longer accessible. v FCIOA
Response: No action required. This reference code is v OPT_CLN
2107FFFE
210734FF Explanation: Temporary Fibre Channel interface error.
Explanation: Format in progress. Response: If this event appears in a serviceable event
Response: The device indicated that a format is in view, work with the failing item list found there. If this
progress. When the format is complete, the device event does not appear in a serviceable event view, no
should be usable. No action is required. This reference service action is required.
code is logged for information only. Failing Item:
v FCINTF
v FCDEV
v FCIOA
v OPT_CLN

21453002 • 2145FFF4

v FCDEV
21453002
v FCINTF
v FCIOA
Failing Item: v OPT_CLN
v FCPORT
v FCDEV 21453160
v FCIOA
v FCINTF accessible.
v OPT_CLN
21453010 accessible.
IOP. v FCDEV
Failing Item:
v FCDEV 21453161
v FCIOA Explanation: The volume in use is no longer
21453020 have caused the volume in use to no longer be
accessible.
Failing Item:
configuration. v FCDEV
Failing Item:
21453162
v FCDEV
v FCIOA Explanation: The volume has been released.
v OPT_CLN The storage subsystem configuration was changed. The
volume that was not in use was removed and is no
longer accessible.
21453029
detects that a device has changed Serial numbers. A
214534FF
logged for information only. Explanation: Format in progress.
Response: The device indicated that a format is in
21453100 progress. When the format is complete, the device
Explanation: Fibre Channel interface error occurred.
Failing Item:
v FCINTF 2145FFF3
v FCDEV
v FCIOA
Failing Item:
v OPT_CLN
v FCDEV
21453109
2145FFF4
Failing Item:
Failing Item:

2145FFF5 • 266FB904
v FCDEV view, work with the failing item list found there. If this
2145FFF5
Failing Item:
v FCDEV
Failing Item:
v FCIOA
v FCDEV
v OPT_CLN
2145FFF6
2145FFFE
Failing Item:
Failing Item:
v FCDEV
v FCINTF
v FCDEV
2145FFFA
v FCIOA
Explanation: Disk device wrong response was v OPT_CLN
recovered by the IOP.

266DA001
Failing Item:
Explanation: I/O adapter Licensed Internal Code error
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
266DB9B0

266EA001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
266EB9B0
(266F) Reference codes

266FA001 266FB904
Explanation: I/O adapter Licensed Internal Code error Explanation: I/O Adapter Licensed Internal Code
detected. failed.
v AJDG301 v AJDGP01
v FI00719

266FB934 • 26893080
v FI00719
266FB934
v FI00718
Explanation: Incompatible hardware detected.
v AJDGP01
Failing Item:
v FI00719 266FB942
v FI00718
Explanation: One half of I/O adapter failed.
Failing Item:
266FB940
v FI00719
v FI00718
Failing Item: v AJDGP01
v FI00719
v FI00718 266FB9B0
v AJDGP01
v MA_BRDG
Failing Item:
v IOA
266FB941
v AJDG301
Failing Item:

Check other errors reported to the system and correct
26890A17
them.
Explanation: A permanent I/O processor failure
Failing Item:
occurred.
v IOA
Failing Item:
v AJDGP01
v IOA
v AJDG301
26893000
v AJDGP01
Explanation: An I/O adapter failure occurred.

v IOA
Explanation: Adapter card storage error.
v AJDGP01
Failing Item:
v AJDGP01
26893001
v AJDG301
Explanation: I/O adapter Licensed Internal Code
v IOA
failed.
Failing Item:
26891307
v IOA
Explanation: I/O adapter resource not available.
v AJDGP01
Failing Item:
v AJDGP01 26893006
v AJDG301
Failing Item:
26891310
v IOA
v ANYBUS
Response: The INA processor error log is being filled
faster than the errors are being reported to the system.
26893080

26893081 • 26896210

26896083
failed.
Failing Item:
failed.
v AJDGP01
Failing Item:
v AJDGP01
26893081
v IOA
Explanation: I/O adapter error; logged only.
26896085
26893084
Explanation: An I/O adapter failure occurred. failed.
v AJDGP01 v AJDGP01
v IOA v IOA
26893087 26896201
Explanation: I/O adapter resource not available. Explanation: A permanent I/O processor failure
Failing Item: occurred.
v AJDGP01 Failing Item:
v AJDG301 v IOA
v NTUSER v AJDGP01
26896070 26896202
Explanation: An I/O adapter failure occurred. Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
v IOA Failing Item:
v AJDGP01
26896071 v IOA

failed. 26896203
Failing Item: Explanation: A permanent I/O processor failure

occurred.
v AJDGP01
Failing Item:
26896072 v NETSERV
v IOA
failed. v AJDGP01
Failing Item:
26896210
v AJDGP01
v IOA Explanation: I/O processor Licensed Internal Code
error.

v NETSERV
v AJDGP01
Failing Item:
v AJDGP01

26896222 • 26896534
v AJDGP01
26896222
26896502
occurred.
Explanation: A Windows fatal error occurred.
Failing Item:
v IOA v AJDGP01
v IOA
26896223
26896530
occurred. Explanation: A Virtual SCSI error was detected.
v IOA v NTVSCSI
v AJDGP01 v NTOPSYS
26896225 26896531
Explanation: A permanent I/O processor failure Explanation: A Virtual SCSI error was detected.
occurred.
Failing Item:
Failing Item: v NTVSCSI
v AJDGP01 v AS4NTDD
v AJDG301 v NTOPSYS
v IOA v AJDGP01
26896226 26896532
Explanation: I/O processor card detected device error. Explanation: A Virtual SCSI error was detected.
v AJDG301 v NTOPSYS
v AS4NTDD v AJDGP01
v AS4NTDD
26896227
Explanation: A HostLAN error was detected. 26896533
Failing Item: Explanation: A Virtual SCSI error was detected.
v NTUSER Failing Item:
v AJDGP01 v NTUSER
v IOA v NTOPSYS
v AS4NTDD
26896228
Explanation: Windows initiated a warm boot. 26896534
v IOA v AS4NTDD
v AJDGP01
26896501 v NTOPSYS
Failing Item:
v IOA

26896535 • 26896544
26896535 2689653D
Explanation: A Virtual SCSI error was detected. Explanation: A Virtual SCSI error was detected.
v NTUSER v NTUSER
v NTDEVDR v NTDEVDR
v AJDGP01 v AJDGP01
26896538 2689653F
v NTVSCSI v NTDEVDR
v NTOPSYS v NTOPSYS
v AJDG301
26896539
Explanation: A Virtual SCSI error was detected. 26896540

v NTVSCSI Failing Item:
v AS4NTDD v NTVSCSI
v NTOPSYS v AJDGP01
v AJDGP01 v AJDG301
2689653A 26896541
Explanation: A Virtual SCSI error was detected. Explanation: A permanent I/O processor failure
occurred.
Failing Item:
v NTOPSYS Failing Item:
v AJDGP01 v IOA
v AS4NTDD v AJDGP01
2689653B 26896542
Explanation: A Virtual SCSI error was detected. Explanation: Licensed Internal Code error detected.

v NTUSER v AJDG301
v NTOPSYS v AJDGP01
v AS4NTDD
26896543
2689653C Explanation: A Windows fatal error occurred.
Explanation: A Virtual SCSI error was detected. Failing Item:
Failing Item: v NTOPSYS
v AS4NTDD v NTVSCSI
v AJDGP01
v NTOPSYS 26896544
Explanation: A Virtual SCSI error was detected.
Failing Item:
v NTVSCSI
v NTOPSYS

26896580 • 2689B3B9
26896580 2689B3B2
Explanation: A Windows fatal error occurred. Explanation: A permanent I/O processor failure
occurred.
Failing Item:
v DISKIMG Failing Item:
v IOA v IOA
v AJDGP01
2689B3B3
26896590 Explanation: A permanent I/O processor failure
occurred.
Explanation: A Netfinity Server error was detected.
Failing Item:
268965B0 v IOA
Explanation: A HostLAN error was detected.

2689B3B4
Failing Item:
v NTLANDD
occurred.
v NTOPSYS
Failing Item:
v IOA
268965B1
2689B3B5
Failing Item:
v NTLANDD occurred.
v NTOPSYS
Failing Item:
v AJDG301
v IOA
268965B2
2689B3B6
v NTDEVDR Failing Item:
v NTOPSYS v IOA
v AJDG301
2689B3B7
26898301
Explanation: An I/O adapter failure occurred. occurred.
v AJDGP01 v IOA
v IOA
2689B3B8
2689B3B1 Explanation: An I/O adapter failure occurred.
Explanation: A permanent I/O processor failure Failing Item:
occurred.
v IOA
Failing Item:
v IOA 2689B3B9
occurred.
Failing Item:
v IOA

2689B3E0 • 2689BE00
2689B3E0 2689B935
Explanation: I/O processor detected a fault condition. Explanation: Incompatible hardware detected.
v IOA v AJDGP01
v IOA
2689B3E1
Explanation: An I/O adapter failure occurred. 2689B960
Failing Item: Explanation: I/O processor Licensed Internal Code

error.
v IOA
Failing Item:
2689B4B0 v AJDGP01
v IOA
Failing Item:
2689BE00
v IOA
2689B4B1 Failing Item:

v AJDGP01
v IOA
Failing Item:
v NETSERV
v AJDGP01
2689B4B9
Failing Item:
v IOA
2689B4BC
Failing Item:
v NETSERV
2689B4BF
Failing Item:
v NSCABLE
2689B904
occurred.
Failing Item:
v AJDGP01
v IOA

2742A001 • 2745B934

v FI00719
2742A001
v AJDGP01
Explanation: Communications I/O adapter software
v MA_BRDG
error or failure configuring hardware.
Failing Item:
2742B941
v NEXTLVL
Explanation: One of the ports on the IOA has failed.

v FI00719
v AJDGP01
Failing Item:

2743B950
Failing Item:
Explanation: Licensed Internal Code error.
v FI00719
Failing Item:
v FI00718
v AJDGP01
v AJDGP01
v FI00718
v MA_BRDG
v FI00719
2743B951

2744B904 2744B921
Explanation: I/O adapter Licensed Internal Code Explanation: I/O adapter hardware error detected.
failed.
Failing Item:
Failing Item: v FI00719
v AJDGP01 v FI00718
v FI00719 v AJDGP01
v MA_BRDG
2744B920
Explanation: I/O adapter Licensed Internal Code 2744B934
failed.
Failing Item:
Failing Item:
v AJDGP01
v FI00719
v FI00718
v FI00718
v FI00719

2745B904 2745B934
Explanation: I/O Adapter Licensed Internal Code Explanation: Incompatible hardware detected.
failed.
Failing Item:
v AJDGP01 v FI00718
v FI00719

2745B940 • 27491306
v FI00719
2745B940
v FI00718
v AJDGP01
Failing Item:
v FI00719 2745B942
v FI00718
v AJDGP01
Failing Item:
v MA_BRDG
v FI00719
v FI00718
2745B941
v AJDGP01
Failing Item:

v FI00718
2746B904
v AJDGP01
Explanation: I/O Adapter Licensed Internal Code
v MA_BRDG
failed.
Failing Item:
2746B941
v AJDGP01
v FI00719
Failing Item:
2746B934 v FI00719
v FI00718
v AJDGP01
Failing Item:
v FI00719
2746B942
v FI00718

v FI00719
v FI00718
Failing Item:
v AJDGP01
v FI00719

v AJDGP01
27490A17
v AJDG301
v IOP
occurred.
v MA_BRDG
Failing Item:
v IOP
2749102E
v MA_BRDG
v AJDGP01
v AJDG301 Failing Item:
v FI01105
27490A22
27491306
Explanation: I/O processor detected a storage transfer
error. Explanation: I/O processor card or Licensed Internal
Code error.
Failing Item:

27491307 • 27493006
Response: A microprocessor exception occurred on the v FI01105

I/O processor.
v AJDGP01 Explanation: Removable media error during IPL.
v IOP
Failing Item:
v FI01104
v FI00022
v BACKPLN
v FI01105
27491307
27493000
Explanation: I/O processor resource not available.
v AJDG301 v FI01101
v IOP
27491310 v MA_BRDG
Response: The I/O processor error log is being filled 27493001
faster than the errors are being reported to the system. Explanation: Not valid condition in I/O Processor
Check other errors reported to the system and correct Licensed Internal Code.
them.
Response: The Licensed Internal Code found a
condition that should not have occurred.
27491317
Failing Item:
Explanation: I/O processor card error.
v IOP
Response: Display the Service Action Log entry for v AJDGP01
this SRC. If the Failing Item indicates IOP, then replace
the IOP. If the Failing Item indicates SVCDOCS, then
do NOT replace the IOP. This is a recoverable error. 27493002
Perform the following: Explanation: Addressed device failed to respond to
1. If the I/O Processor is not operable and disk units selection.
are attached, use Hardware Service Manager to re-IPL Failing Item:
the IOP. Other resources attached to the IOP may then
need to be Varied On. v IOPIP16
v FI01105
2. If disk units are not attached, perform the VRYCFG
RESET(*YES) command to reset the IOP and Vary On v STORIOA
attached resources. v FI01140
v SVCDOCS v FI01106
27492200 27493006
Explanation: I/O processor Licensed Internal Code Explanation: System bus error.
error. Failing Item:
Failing Item: v IOP
v AJDGP01 v ANYBUS
v FI01101
27492201
Explanation: Removable media error during IPL.
Failing Item:
v USER

27493020 • 27493101
27493020 27493081
Explanation: I/O processor detected a SCSI bus Explanation: System log entry only, no service action
configuration error. required.
Response: Error occurred on SCSI bus 0.
27493084
Failing Item:
v IOPIP17 Explanation: I/O processor card or Licensed Internal
Code error.
v USER
v FI01107 Response: A microprocessor exception occurred on the
I/O processor.
v STORIOA
Failing Item:
27493021 v AJDGP01
v IOP
Explanation: I/O processor detected a SCSI bus
configuration error. v FI01104
v MA_BRDG
Failing Item:
27493087
v IOPIP17
v USER
v FI01107 Response: The Licensed Internal Code could not
allocate resources on the I/O processor card.
v STORIOA
Failing Item:
27493022 v AJDGP01
v AJDG301
configuration error. v IOACNFG
v FI01104
Failing Item:
27493100
v IOPIP17
Explanation: I/O processor card detected interface
v USER
error.
v FI01107
v STORIOA
Failing Item:
27493023 v IOPIP13
v FI01107
configuration error. v STORIOA
v FI01140
v DEVBPLN
Failing Item:
v IOPIP17
27493101
v USER
v FI01107
error.
v STORIOA

v IOPIP13
Explanation: I/O processor Licensed Internal Code
error. v FI01107
v STORIOA
Failing Item:
v FI01140
v AJDGP01
v DEVBPLN

27493102 • 27493140
27493102 27493120
Explanation: I/O processor card detected interface Explanation: I/O Processor detected that the bus is
error. not operational.
Response: Error occurred on SCSI bus 2. Response: A device was added to SCSI bus 0 of the
I/O Adapter and caused the bus to become not
Failing Item:
operational. Remove the device.
v IOPIP13
Failing Item:
v FI01107
v SVCDOCS
v STORIOA
v FI01140
27493121
v DEVBPLN
Explanation: I/O Processor detected that the bus is
not operational.
27493103
Response: A device was added to SCSI bus 1 of the
error.
Failing Item:
v IOPIP13
v FI01107 27493122
v STORIOA
v FI01140 not operational.
v DEVBPLN
27493109 operational. Remove the device.
Explanation: I/O processor timed out a device Failing Item:

command. v SVCDOCS
Failing Item:
v IOPIP16 27493123
v FI01105 Explanation: I/O Processor detected that the bus is
v STORIOA not operational.
v FI01140 Response: A device was added to SCSI bus 3 of the
v BACKPLN I/O Adapter and caused the bus to become not
v FI01106 operational. Remove the device.
Failing Item:
27493110 v SVCDOCS

error. 27493136
Failing Item: Explanation: The removable media device is assigned
v IOPIP16 elsewhere.
v FI01105 Failing Item:
v STORIOA v USER
v FI01140 v FI01105
v BACKPLN
v FI01106 27493140
now operational.
Response: This reference code and the 3120 reference
code that occurred before it require no service action,

27493141 • 27493400
since SCSI bus 0 is now operational.

27493203
27493141
Failing Item:
now operational. v FI01105

code that occurred before it require no service action, 27493205
since SCSI bus 1 is now operational. Explanation: Disk sector read error.
Response: Disk unit data may need to be reloaded,
27493142 but the disk unit does not need to be replaced.
Explanation: I/O Processor detected that the bus is Failing Item:
now operational.
v FI01105
27493215
27493143 Response: Disk unit data may need to be reloaded,
but the disk unit does not need to be replaced.
now operational. Failing Item:
Response: This reference code and the 3123 reference v FI01105
since SCSI bus 3 is now operational. 27493250
Explanation: Disk unit requires initialization before
27493150 use.
Explanation: I/O processor detected a SCSI bus Response: Perform a D-IPL and work on errors found
configuration error. in the log.
Response: Internal and external SCSI cables are Failing Item:
connected to SCSI bus 0 at the same time. Correct the
SCSI bus 0 configuration. v USER
Failing Item:
27493300
v SVCDOCS
Explanation: Storage unit detected a media problem.
Explanation: I/O processor detected a SCSI bus v IOPIP01
configuration error. v MEDIA
Response: Internal and external SCSI cables are v FI00121

connected to SCSI bus 1 at the same time. Correct the v FI01141
SCSI bus 1 configuration.
v SVCDOCS Explanation: I/O processor card detected device error.
Response: NOTE: If external devices are attached
27493200 check EXTSCSI and DEVTERM first.
Explanation: A tape/CD or disk device reported a Failing Item:
failure.
v FI02112
v FI01105 v FI01106
v STORIOA v DEVTERM
v IOP v FI01140
v MEDIA

27493401 • 27496200
27493401 27496075
Explanation: Device backplane problem. Explanation: I/O processor resource not available.
v DEVBPLN v AJDGP01
27493501 27496076
Explanation: I/O processor Licensed Internal Code Explanation: I/O processor card detected media error.
error.
Failing Item:
Failing Item: v MEDIA
v AJDGP01 v AJDGP01
v IOP v FI01105
27493600 27496081
Explanation: System log entry only, no service action Explanation: I/O processor Licensed Internal Code
required. error.
Failing Item:
27493601
v AJDGP01
Explanation: System log entry only, no service action v IOP
required.
27496082
27496070
Explanation: A permanent I/O processor failure error.
occurred.
Failing Item:
Failing Item:
v AJDGP01
v IOP
v IOP
27496071
27496083
error.
error.
Failing Item:
Failing Item:
v AJDGP01
v AJDGP01
v IOP
27496072
Explanation: I/O processor Licensed Internal Code 27496085
error.
Failing Item: error.
v AJDGP01
Failing Item:
v IOP
v AJDGP01
v IOP
27496073
v MA_BRDG
Explanation: IPL device not ready.
v MEDIA Explanation: A permanent IOA hardware error
v FI01105 occurred.
v USER Failing Item:
v FCIOA

27496201 • 27498130
v OPT_CLN v STORIOA
v CACHE
27496201
Explanation: IOA LID is not valid. 27498007
Failing Item: Explanation: A recoverable cache adapter card error

occurred.
v AJDGP01
Response: DO NOT replace both FRUs at the same
time. Exchange the FRUs one at a time in the order
27496602
shown.
Explanation: An I/O processor Licensed Internal Code
Failing Item:
error occurred.
v CACHE
Failing Item:
v STORIOA
v AJDGP01
27498010
27498000
Explanation: A permanent cache adapter card failure
Explanation: A permanent IOP or cache adapter card occurred.
failure occurred.
Response: The cache adapter card may be missing,
Response: DO NOT replace both FRUs at the same broken or incompatible.
shown. DO NOT replace both FRUs at the same time.
Exchange the FRUs one at a time in the order shown.
Failing Item:
Failing Item:
v STORIOA
v CACHE
v CACHE
v STORIOA
27498002
27498011
occurred. Explanation: A permanent cache adapter card failure
occurred.
time. Exchange the FRUs one at a time in the order Response: The cache adapter card may be missing,
shown. broken or incompatible.
Failing Item: DO NOT replace both FRUs at the same time.

v CACHE
v CACHE
27498004 v STORIOA
Explanation: Voltage drop detected on I/O processor

5 volt power supply. 27498100

error.
v FI01141
v AJDGP01
27498005 v IOP
Explanation: A recoverable IOP or cache adapter card

error occurred. 27498130
Response: DO NOT replace both FRUs at the same Explanation: IOA detected recoverable device bus
time. Exchange the FRUs one at a time in the order error.
shown. Response: An error occurred on SCSI bus 0. No action
Failing Item: is required. This reference code is logged for
information only.

27498131 • 27498200
v STORIOA
27498131
v ANYBRDG
Explanation: IOA detected recoverable device bus
error.
27498151
Response: An error occurred on SCSI bus 1. No action
is required. This reference code is logged for Explanation: I/O processor Licensed Internal Code
information only. error.
Failing Item:
27498132 v AJDGP01
Explanation: IOA detected recoverable device bus v STORIOA
error.
Response: An error occurred on SCSI bus 2. No action 27498155
is required. This reference code is logged for Explanation: A permanent I/O processor failure
information only. occurred.
Failing Item:
27498133
v AJDGP01
error.
is required. This reference code is logged for
information only. Explanation: A permanent I/O processor failure
occurred.
Explanation: IOA detected recoverable device bus v AJDGP01
error. v STORIOA
Response: No action is required. This reference code
is logged for information only. 27498157
Explanation: I/O adapter card error.
27498141
Response: Display the Service Action Log entry for
Explanation: IOA detected recoverable device error. this SRC. If the Failing Item indicates I/O adapter, then
replace the I/O adapter. If the Failing Item indicates
Response: No action is required. This reference code SVCDOCS, then do NOT replace the I/O adapter. This
is logged for information only. is a recoverable error. Perform the following for the
I/O processor that the I/O adapter is attached to:
27498145 1. If the I/O Processor is not operable and disk units
Explanation: A recoverable I/O processor error are attached, use Hardware Service Manager to re-IPL
occurred. the IOP. Other resources attached to the IOP may then
need to be Varied On.
Failing Item:
v STORIOA
RESET(*YES) command to reset the IOP and Vary On
attached resources.
27498146
Failing Item:
Explanation: Disk device detected recoverable error. v SVCDOCS
Failing Item:
v FI01105 27498200
27498150 error.
occurred. v AJDGP01
Failing Item: v IOP

27498300 • 27499020
v FI01106
27498300
Explanation: I/O processor card or Licensed Internal
27499008
Code error.
Explanation: I/O card does not support functions
Response: A microprocessor exception occurred on the
expected by devices.
I/O processor.
Failing Item:
Failing Item:
v IOPIP25
v STORIOA
v IOP
27499009
v AJDGP01
Explanation: Call your next level of support for
assistance.
27498301
Failing Item:
Explanation: Not valid condition in I/O Processor
Licensed Internal Code. v SVCDOCS

condition that should not have occurred. 27499010
Failing Item: Explanation: Cache data associated with attached

devices cannot be found.
v FI01101
v IOP v IOPIP31
27498400 27499011
Explanation: I/O processor Licensed Internal Code Explanation: Cache data belongs to devices other than
error. those attached.

v AJDGP01 v IOPIP32
27499000 27499012
Explanation: I/O processor card detected device error. Explanation: IOP requires a cache adapter card but
cannot find it.
Failing Item:
Response: The cache adapter card is missing or
v FI01105
broken.
v STORIOA
Failing Item:
v IOPIP29
27499001
v CACHE
Explanation: I/O processor card detected device
configuration error.
27499013
Failing Item:
Explanation: The IOP and attached cache adapter card
v IOPIP33
are not compatible.
Failing Item:
27499002
v IOPIP19
Explanation: I/O processor card detected device error.
v IOPIP16
Explanation: Array not functional due to present
v FI01105 hardware configuration.
v STORIOA
Failing Item:
v FI01140
v IOPIP20
v BACKPLN

27499021 • 27499041
move all devices in an array to another IOP that

27499021
supports arrays, or stop an array on this IOP.
Failing Item:
hardware configuration.
v SVCDOCS
Failing Item:
v IOPIP20
27499029
Explanation: Incorrect hardware configuration change
27499022
has been detected.
Response: Contact your next level of support.
Failing Item:
Failing Item:
v SVCDOCS
v IOPIP22
2749902F
27499023
Explanation: Array addendum Product Activity Log
entry.
Response: This entry contains additional array
Failing Item:
information for 90xx reference codes when the array
v IOPIP22 contains more than 10 members. Use the 90xx entry
that occurred at the same time as this reference code as
27499024 the starting point for this problem.

hardware configuration. 27499030
Failing Item: Explanation: Array no longer protected due to

missing or failed disk unit.
v IOPIP22
Failing Item:
27499025 v IOPIP21
Explanation: Disk unit is not supported at its physical

location. 27499031
Failing Item: Explanation: Automatic rebuild initiated for array.

v IOPIP21 Response: Either a previous rebuild was interrupted
and was automatically restarted, or a hot spare disk
unit was used to automatically rebuild the array. Look
27499026
for other reference codes and take action on them.
27499040
Failing Item:
Explanation: Array protection temporarily suspended.
v IOPIP22
Response: No action required. Protection will be
automatically restarted.
27499027
Explanation: Array not functional due to present 27499041
Explanation: Background array parity check detected
Failing Item: and corrected errors.
v IOPIP34
Response: Call your next level of support to report
the problem.
27499028
Failing Item:
Explanation: Incorrect hardware configuration change v AJDGP01
has been detected.
Response: Reduce the number of arrays on IOP. Either

27499050 • 27499092
27499050 27499081
Explanation: Required cache data cannot be located Explanation: I/O processor card detected device error.
for a disk unit.
Failing Item:
v IOPIP30 v STORIOA
27499051 27499082
Explanation: IOP cache data exists for a missing or Explanation: I/O processor card detected device error.
failed device.
Failing Item:
Response: If all configured units are missing, a 9054
v IOPIP16
reference code may appear in the product activity log.
If so, perform the action indicated for the 9054 v FI01105
reference code. v STORIOA
Otherwise, perform the procedure indicated in the v FI01140
failing item list. v BACKPLN
v IOPIP27
27499090
27499052 Explanation: Disk unit has been modified after the
last known status.
Explanation: Cache data exists for device that has
been modified. Response: Re-IPL the system. If any reference codes
are surfaced, use the new reference code to resolve the
Failing Item:
problem.
v IOPIP28
If you cannot resolve the problem, contact your next
level of support.
27499053
Failing Item:
Explanation: IOP resources not available due to
v SVCDOCS
previous problems.
Response: Take action on other IOP reference codes
27499091
which have surfaced.
If you cannot get to SST or DST, and cannot perform a
has been detected.
type A or B IPL, perform a type D IPL from removable
media. Look for Product Activity Log entries for other Response: Re-IPL the system. If any reference codes
IOP reference codes and take action on them. are surfaced, use the new reference code to resolve the
problem.
Failing Item:
v SVCDOCS If you cannot resolve the problem, contact your next
level of support.

v SVCDOCS
previous problems.
27499092
Response: Power off the system and remove all new
or replacement disk units. IPL the system to DST. If Explanation: Disk unit requires initialization before
you cannot perform a type A or B IPL, perform a type use.
D IPL from removable media.
Failing Item:
Look for Product Activity Log entries for other IOP v IOPIP26
reference codes and take action on them.
Failing Item:
v SVCDOCS

2749B3B1 • 2749B935
v IOP
2749B3B1
2749B3B9
occurred.
Failing Item:
occurred.
v IOP
Failing Item:
v IOP
2749B3B2
2749B3E0
occurred.
Explanation: I/O processor detected a fault condition.
Failing Item:
v IOP Failing Item:
v IOP
2749B3B3 v MA_BRDG

occurred. 2749B3E1
Failing Item: Explanation: I/O processor detected a fault condition.

v IOP Failing Item:
v IOP
2749B3B4 v MA_BRDG
occurred. 2749B410
v IOP occurred.
Failing Item:
2749B3B5 v STORIOA
occurred. 2749B411
v IOP occurred.
Failing Item:
2749B3B6 v STORIOA
occurred. 2749B412
Failing Item: Explanation: Tape/CD or disk bus interface error
v IOP occurred.
Failing Item:
2749B3B7 v IOPIP16
Explanation: A permanent I/O processor failure v FI01107
occurred. v FI01140
v IOP v DEVTERM
2749B3B8 2749B935
Explanation: Multi-adapter Bridge error detected. Explanation: Unknown hardware detected.

v MA_BRDG v FI01101

2749BE00 • 27573100
v AJDGP01 Explanation: I/O adapter detected recoverable error.

v IOP Failing Item:
v MA_BRDG v STORIOA
v ANYBRDG
2749BE00
Explanation: I/O processor detected a fault condition. 2749FF6D
Failing Item: Explanation: I/O processor detected a recoverable
v AJDGP01 system bus error.
v IOP Failing Item:
v FI01104 v IOP
v MA_BRDG v ANYBUS
2749FF3D

v FI01107
27571310
v STORIOA
Response: The I/O processor error log is being filled 27573022
Check other errors reported to the system and correct Explanation: I/O processor detected a SCSI bus
them. configuration error.
Explanation: System bus error. v IOPIP17
Failing Item: v USER
v IOP v FI01107
v ANYBUS v STORIOA
v STORIOA
27573023
27573020 Explanation: I/O processor detected a SCSI bus
configuration error. Response: Error occurred on SCSI bus 3.
Response: Error occurred on SCSI bus 0. Failing Item:
Failing Item: v IOPIP17
v IOPIP17 v USER
v USER v FI01107
v FI01107 v STORIOA
v STORIOA
27573100
27573021 Explanation: I/O processor card detected interface
error.
configuration error. Response: Error occurred on SCSI bus 0.
v IOPIP17 v FI01107
v USER v STORIOA

27573101 • 27573142
v FI01140
27573121
v DEVBPLN
not operational.
27573101
Explanation: I/O processor card detected interface I/O Adapter and caused the bus to become not
error. operational. Remove the device.
v IOPIP13
v FI01107 27573122
v STORIOA Explanation: I/O Processor detected that the bus is
v DEVBPLN Response: A device was added to SCSI bus 2 of the
Explanation: I/O processor card detected interface Failing Item:

error. v SVCDOCS
27573123
Failing Item:
v IOPIP13 Explanation: I/O Processor detected that the bus is
not operational.
v FI01107
v STORIOA Response: A device was added to SCSI bus 3 of the
v DEVBPLN
Failing Item:
v SVCDOCS
27573103
Explanation: I/O processor card detected interface 27573140
error.
Response: Error occurred on SCSI bus 3. now operational.
Failing Item: Response: This reference code and the 3120 reference
v IOPIP13 code that occurred before it require no service action,
v FI01107 since SCSI bus 0 is now operational.
v STORIOA
v FI01140 27573141
v DEVBPLN Explanation: I/O Processor detected that the bus is
now operational.
27573120 Response: This reference code and the 3121 reference
not operational.
27573142
operational. Remove the device. Explanation: I/O Processor detected that the bus is
now operational.
Failing Item:
v SVCDOCS Response: This reference code and the 3122 reference

27573143 • 27578130
27573143 27573600
Explanation: I/O Processor detected that the bus is Explanation: System log entry only, no service action
now operational. required.
code that occurred before it require no service action, 27573601
required.
27573150
Explanation: I/O processor detected a SCSI bus 27578008
Explanation: A permanent cache battery pack failure
Response: Internal and external SCSI cables are occurred.
Response: NOTE: Under a certain configuration, this
SRC may not represent an error that requires a service
Failing Item: action. Depending on the configuration of the system,
v SVCDOCS the Storage IOA may have been altered and/or the
Storage IOA Cache may have been disabled to allow
attachment of OEM Storage that emulates a Load
27573151 Source drive. If this is the case, this error will be posted
Explanation: I/O processor detected a SCSI bus each time the IOA is IPLed and it can be ignored.
configuration error. Failing Item:
Response: Internal and external SCSI cables are v CACHBAT
connected to SCSI bus 1 at the same time. Correct the v STORIOA
v SVCDOCS
Explanation: Impending cache battery pack failure.
Failing Item:
27573400
v CACHBAT
v FI02112
Explanation: Attached read cache devices exceed
v STORIOA capacity supported by IOA.
v FI01106
Response: Reduce the number of read caches on the
v DEVTERM IOA.
v FI01140
Failing Item:
v SVCDOCS
27573401
Explanation: Device backplane problem. 27578100
v DEVBPLN error.
Failing Item:
27573501 v AJDGP01
Explanation: I/O processor Licensed Internal Code v IOP
error.
v AJDGP01 Explanation: IOA detected recoverable device bus
v IOP error.

27578131 • 27578157

27578150
information only.
occurred.
27578131
error.
action. Depending on the configuration of the system,
Response: An error occurred on SCSI bus 1. No action the Storage IOA may have been altered and/or the
is required. This reference code is logged for Storage IOA Cache may have been disabled to allow
information only. attachment of OEM Storage that emulates a Load
Source drive. If this is the case, this error will be posted
each time the IOA is IPLed and it can be ignored.
27578132
Failing Item:
error. v STORIOA
v ANYBRDG
information only. 27578151
27578133 error.
Explanation: IOA detected recoverable device bus Failing Item:
error. v AJDGP01
Response: An error occurred on SCSI bus 3. No action v STORIOA
information only.
27578155
27578140
occurred.
Failing Item:
error.
v AJDGP01
v STORIOA
is logged for information only.
27578156
27578141
Explanation: IOA detected recoverable device error.
occurred.
Failing Item:
v AJDGP01
v STORIOA
27578145
Explanation: A recoverable I/O processor error
27578157
occurred.
Failing Item:
v STORIOA Response: Display the Service Action Log entry for
this SRC. If the Failing Item indicates I/O adapter, then
27578146 SVCDOCS, then do NOT replace the I/O adapter. This
Explanation: Disk device detected recoverable error. is a recoverable error. Perform the following for the
Failing Item:
1. If the I/O Processor is not operable and disk units
v FI01105 are attached, use Hardware Service Manager to re-IPL

27578200 • 27579025

27579010
attached resources.
Explanation: Cache data associated with attached
Failing Item:
v SVCDOCS
Failing Item:
v IOPIP31
27578200
27579011
error.
Explanation: Cache data belongs to devices other than
Failing Item:
those attached.
v AJDGP01
Failing Item:
v IOP
v IOPIP32
27579000
27579020
Failing Item: hardware configuration.
v FI01105
Failing Item:
v STORIOA
v IOPIP20
27579001
27579021
Failing Item:
Failing Item:
v IOPIP33
v IOPIP20
27579002
27579022
v IOPIP16 Failing Item:
v FI01105 v IOPIP22
v STORIOA
v FI01140 27579023
v BACKPLN
Failing Item:
27579008
v IOPIP22
27579024
Failing Item:
v IOPIP25 hardware configuration.
Failing Item:
27579009
v IOPIP22
assistance.
27579025
Failing Item:
v SVCDOCS location.
Failing Item:

27579026 • 27579050
v IOPIP21
27579031
Explanation: Automatic rebuild initiated for array.
27579026
Response: Either a previous rebuild was interrupted
Failing Item: for other reference codes and take action on them.
v IOPIP22
27579032
27579027 Explanation: A disk unit in a RAID array is missing
Explanation: Array not functional due to present or failed.
hardware configuration. Response: The array is still protected, but the disk
Failing Item: unit should be replaced.
v FI02112
27579028 v IOPIP21
has been detected. 27579040
Response: Reduce the number of arrays on IOP. Either Explanation: Array protection temporarily suspended.
Failing Item:
v SVCDOCS 27579041
27579029 and corrected errors.
Explanation: Incorrect hardware configuration change Response: Call your next level of support to report
has been detected. the problem.
Response: Contact your next level of support. Failing Item:
v SVCDOCS
27579042
2757902F Explanation: An array parity error has been detected
Explanation: Array addendum Product Activity Log and corrected.
entry. Response: Call your next level of support to report
Response: This entry contains additional array the problem.
information for 90xx reference codes when the array Failing Item:
contains more than 10 array members. Use the 90xx
v NEXTLVL
entry that occurred at the same time as this reference
code as the starting point for this problem.
27579050
27579030 Explanation: Required cache data cannot be located
for a disk unit.
Explanation: Array no longer protected due to
missing or failed disk unit. Failing Item:
v IOPIP21

27579051 • 27579091
27579051 27579072
Explanation: IOP cache data exists for a missing or Explanation: Link from IOA to auxiliary cache IOA
failed device. went non-operational.
Response: If all configured units are missing, a 9054 Response: No service action required.
If so, perform the action indicated for the 9054
27579073
reference code.
Explanation: Incompatible or non-operational
Otherwise, perform the procedure indicated in the
auxiliary cache IOA attached.
failing item list.
Failing Item:
Failing Item:
v IOPIP40
v IOPIP27
27579081
27579052
been modified. Failing Item:
Response: Contact your next level of support. v FI01105
v STORIOA
Failing Item:
v SVCDOCS
27579082
27579053 Explanation: I/O processor card detected device error.
Explanation: IOP resources not available due to Failing Item:

previous problems. v IOPIP16
Response: Take action on other IOP reference codes v FI01105
which have surfaced. v STORIOA
If you cannot get to SST or DST, and cannot perform a v FI01140
type A or B IPL, perform a type D IPL from removable v BACKPLN
media. Look for Product Activity Log entries for other v FI01106
IOP reference codes and take action on them.
v SVCDOCS
Explanation: Disk unit has been modified after the
last known status.
27579054
Response: Re-IPL the system. If any reference codes
Explanation: IOP resources not available due to are surfaced, use the new reference code to resolve the
previous problems. problem.
Response: Power off the system and remove all new If you cannot resolve the problem, contact your next
or replacement disk units. IPL the system to DST. If level of support.
you cannot perform a type A or B IPL, perform a type
D IPL from removable media. Failing Item:
v SVCDOCS
Look for Product Activity Log entries for other IOP
27579091
Failing Item:
v SVCDOCS Explanation: Incorrect hardware configuration change
has been detected.
27579071 Response: Re-IPL the system. If any reference codes

Explanation: Link from IOA to auxiliary cache IOA problem.
went operational.
Response: No service action required. level of support.

27579092 • 27633022
Failing Item: Explanation: Incompatible hardware detected.

v SVCDOCS Failing Item:
v STORIOA
27579092
Explanation: Disk unit requires initialization before 2757FF3D
use.
Explanation: I/O adapter detected recoverable error.
Failing Item:
Failing Item:
v IOPIP26
v STORIOA
v ANYBRDG
27579093
Explanation: Read cache device not in correct format. 2757FF6D
Response: Contact your next level of support. Explanation: I/O processor detected a recoverable
Failing Item: system bus error.
v IOP
2757B934 v ANYBUS

2760B950
Failing Item:
v FI00719
Failing Item:
v FI00718
v AJDGP01
v AJDGP01
v FI00718
v MA_BRDG
v FI00719
2760B951

Failing Item:
27631310
v IOPIP17
v USER
Response: The I/O processor error log is being filled v FI01107
v STORIOA
them.
27633021
27633006 Explanation: I/O processor detected a SCSI bus
Explanation: System bus error.
Failing Item:
v IOP Failing Item:
v ANYBUS v IOPIP17
v STORIOA v USER
v FI01107
27633020 v STORIOA

configuration error. 27633022

27633023 • 27633122
Explanation: I/O processor detected a SCSI bus v IOPIP13

Response: Error occurred on SCSI bus 2. v STORIOA
v IOPIP17 v DEVBPLN
v USER
v FI01107 27633103
v STORIOA Explanation: I/O processor card detected interface
error.
27633023 Response: Error occurred on SCSI bus 3.
Explanation: I/O processor detected a SCSI bus Failing Item:
configuration error. v IOPIP13
Response: Error occurred on SCSI bus 3. v FI01107
v IOPIP17 v FI01140
v USER v DEVBPLN
v FI01107
v STORIOA 27633120
27633100 not operational.
Explanation: I/O processor card detected interface Response: A device was added to SCSI bus 0 of the
error. I/O Adapter and caused the bus to become not
Failing Item:
Failing Item:
v SVCDOCS
v IOPIP13
v FI01107
27633121
v STORIOA
v FI01140
not operational.
v DEVBPLN
error.
v SVCDOCS
v FI01140 I/O Adapter and caused the bus to become not
v DEVBPLN operational. Remove the device.
Failing Item:
27633102 v SVCDOCS
error.
Failing Item:

27633123 • 27638008
27633123 27633151
Explanation: I/O Processor detected that the bus is Explanation: I/O processor detected a SCSI bus
not operational. configuration error.
Response: A device was added to SCSI bus 3 of the Response: Internal and external SCSI cables are
I/O Adapter and caused the bus to become not connected to SCSI bus 1 at the same time. Correct the
operational. Remove the device. SCSI bus 1 configuration.
v SVCDOCS v SVCDOCS
27633140 27633400
Explanation: I/O Processor detected that the bus is Explanation: I/O processor card detected device error.
now operational.
Failing Item:
v STORIOA
v FI01106
v DEVTERM
27633141
v FI01140
now operational.
27633401
code that occurred before it require no service action, Explanation: Device backplane problem.
since SCSI bus 1 is now operational. Failing Item:
v DEVBPLN
27633142
Explanation: I/O Processor detected that the bus is 27633501
now operational.
Response: This reference code and the 3122 reference error.
v AJDGP01
27633143 v IOP

now operational. 27633600
Response: This reference code and the 3123 reference Explanation: System log entry only, no service action
code that occurred before it require no service action, required.
27633601
27633150 Explanation: System log entry only, no service action
Explanation: I/O processor detected a SCSI bus required.
Response: Internal and external SCSI cables are 27638008
connected to SCSI bus 0 at the same time. Correct the Explanation: A permanent cache battery pack failure
SCSI bus 0 configuration. occurred.
Failing Item: Response: NOTE: Under a certain configuration, this
v SVCDOCS SRC may not represent an error that requires a service
the Storage IOA may have been altered and/or the

27638009 • 27638151

27638133
Failing Item:
v CACHBAT error.
v STORIOA
27638009 information only.
27638140
Failing Item:
v CACHBAT Explanation: IOA detected recoverable device bus
error.
27638012 Response: No action is required. This reference code

capacity supported by IOA.
27638141
IOA. Explanation: IOA detected recoverable device error.
Failing Item: Response: No action is required. This reference code

v SVCDOCS
27638145
27638100
Explanation: I/O processor Licensed Internal Code occurred.
error.
Failing Item:
Failing Item:
v STORIOA
v AJDGP01
v IOP
27638146
27638130 Explanation: Disk device detected recoverable error.

error. v FI01105
is required. This reference code is logged for 27638150
information only.
occurred.
27638131
Explanation: IOA detected recoverable device bus SRC may not represent an error that requires a service
error. action. Depending on the configuration of the system,
Response: An error occurred on SCSI bus 1. No action Storage IOA Cache may have been disabled to allow
is required. This reference code is logged for attachment of OEM Storage that emulates a Load
information only. Source drive. If this is the case, this error will be posted
error. v ANYBRDG
information only.
error.
Failing Item:

27638155 • 27639020
v AJDGP01
27639001
v STORIOA
27638155
Failing Item:
v IOPIP33
occurred.
Failing Item:
27639002
v AJDGP01
v STORIOA
Failing Item:
27638156 v IOPIP16
v FI01105
occurred. v STORIOA
v FI01140
Failing Item:
v BACKPLN
v AJDGP01
v FI01106
v STORIOA
27639008
27638157
Failing Item:
replace the I/O adapter. If the Failing Item indicates v IOPIP25
SVCDOCS, then do NOT replace the I/O adapter. This
is a recoverable error. Perform the following for the 27639009
1. If the I/O Processor is not operable and disk units assistance.
are attached, use Hardware Service Manager to re-IPL
the IOP. Other resources attached to the IOP may then Failing Item:
need to be Varied On. v SVCDOCS
RESET(*YES) command to reset the IOP and Vary On 27639010
attached resources.
Failing Item: devices cannot be found.
v IOPIP31
27638200
error.
Failing Item: those attached.
v IOP v IOPIP32
27639000 27639020
Explanation: I/O processor card detected device error. Explanation: Array not functional due to present
v STORIOA v IOPIP20

27639021 • 27639040

27639021
Failing Item:
v SVCDOCS
Failing Item:
v IOPIP20
27639029
27639022
has been detected.
Failing Item:
Failing Item:
v SVCDOCS
v IOPIP22
2763902F
27639023
entry.
Failing Item:
v IOPIP22 contains more than 10 array members. Use the 90xx
27639024 code as the starting point for this problem.


v IOPIP22
Failing Item:
27639025 v IOPIP21

location. 27639031
Failing Item: Explanation: Automatic rebuild initiated for array.

27639026
27639032
Failing Item:
Explanation: A disk unit in a RAID array is missing
v IOPIP22 or failed.
Response: The array is still protected, but the disk
27639027 unit should be replaced.
Explanation: Array not functional due to present Failing Item:
v FI02112
v IOPIP34
27639040
27639028
has been detected.

27639041 • 27639082

27639041
media. Look for Product Activity Log entries for other
Explanation: Background array parity check detected IOP reference codes and take action on them.
and corrected errors.
Failing Item:
Response: Call your next level of support to report v SVCDOCS
the problem.
v AJDGP01
previous problems.
27639042
Explanation: An array parity error has been detected or replacement disk units. IPL the system to DST. If
and corrected. you cannot perform a type A or B IPL, perform a type
the problem. Look for Product Activity Log entries for other IOP
Failing Item:
v NEXTLVL Failing Item:
v SVCDOCS
27639050
27639071
Explanation: Required cache data cannot be located
for a disk unit. Explanation: Link from IOA to auxiliary cache IOA
went operational.
Failing Item:
v IOPIP30 Response: No service action required.
27639051 27639072
Explanation: IOP cache data exists for a missing or Explanation: Link from IOA to auxiliary cache IOA
failed device. went non-operational.
If so, perform the action indicated for the 9054 27639073
reference code.
Otherwise, perform the procedure indicated in the auxiliary cache IOA attached.
failing item list.
Failing Item:
Failing Item:
v IOPIP40
v IOPIP27
27639081
27639052
v FI01105
v STORIOA
Failing Item:
v SVCDOCS
27639082
27639053
Failing Item:
v FI01105
which have surfaced. v STORIOA
v FI01140

27639090 • 27653120
v BACKPLN Failing Item:

v FI01106 v IOPIP26
27639090 27639093
Explanation: Disk unit has been modified after the Explanation: Read cache device not in correct format.
last known status.
Failing Item:
problem. v SVCDOCS

level of support. 2763B934
Failing Item: Explanation: Incompatible hardware detected.

v STORIOA
27639091
Explanation: Incorrect hardware configuration change 2763FF3D
has been detected. Explanation: I/O adapter detected recoverable error.
Response: Re-IPL the system. If any reference codes Failing Item:
problem. v STORIOA
v ANYBRDG
level of support.
2763FF6D
Failing Item:
v SVCDOCS Explanation: I/O processor detected a recoverable
system bus error.

v IOP
use. v ANYBUS

27651310
error.
Explanation: I/O processor or I/O adapter resource
Failing Item:
not available.
v FCINTF
Response: The I/O processor or I/O adapter error log
v ANYFC
is being filled faster than the errors are being reported
to the system. Check other errors reported to the v FCIOA
system and correct them. v OPT_CLN
27653020 27653120
Explanation: I/O processor detected a configuration Explanation: An open port was detected on port 0.
error.
Problem determination: Perform the following steps:
Response: Either too many devices or the wrong kind 1. Check for a missing cable or wrap connector.
of devices have been configured under the IOA.
Change the configuration. 2. This error can occur when a shared device is being
moved from one LPAR to another LPAR and the
Failing Item: port was left open.
v SVCDOCS 3. This error can occur if there is a port or link failure.
If you have eliminated the above possibilities
contact your next level of support.
27653100

27653140 • 27658156
Failing Item:
27658141
v FCPORT
v FCIOA
v FCDEV Response: No action required. This reference code is
v OPT_CLN
27658145
27653140
Explanation: I/O Processor detected that a port is
occurred.
now operational.
Failing Item:
code that occurred before it require no service action, v FCIOA
since the port is now operational. v OPT_CLN
27653200 27658146
Explanation: A disk device reported a failure. Explanation: Disk device detected recoverable error.
v FCDEV v FCDEV
v FCIOA
v IOP 27658150
v OPT_CLN Explanation: A permanent I/O processor failure
occurred.
Explanation: I/O processor card detected device error. v FCIOA
Failing Item: v ANYBRDG
v FCDEV v OPT_CLN
v FCINTF
v ANYFC 27658151
v FCIOA Explanation: I/O processor Licensed Internal Code
v OPT_CLN error.
Failing Item:
276534FF v AJDGP01
Explanation: Format in progress. v FCIOA
v IOP
progress. When the format is complete, the device v OPT_CLN
should be useable. No action is required. This reference
code is logged for information only. 27658155
27658130 occurred.
Explanation: Recovered Fibre Channel interface error. Failing Item:
Response: No action required. This reference code is v AJDGP01
logged for information only. v FCIOA
v OPT_CLN
27658140
Explanation: Recovered Fibre Channel interface error. 27658156
Response: No action required. This reference code is Explanation: A permanent I/O processor failure
logged for information only. occurred.
Failing Item:

27659091 • 27663200
v AJDGP01 Response: Reset the I/O processor and then IPL the
v FCIOA I/O processor. For information about how to reset and
IPL the I/O processor, see Debug the resource. If an
v OPT_CLN
I/O processor reset and I/O processor IPL does not
resolve the problem, contact your next level of support.
27659091
Failing Item:
Explanation: Incorrect hardware configuration change v SVCDOCS
has been detected.
Response: Reset the I/O processor and then IPL the 2765FF3D
I/O processor. For information about how to reset and
IPL the I/O processor, see Debug the resource. If an Explanation: Recovered IOA error.
I/O processor reset and I/O processor IPL does not Failing Item:
v FCIOA
v SVCDOCS v OPT_CLN
27659092
has been detected.

27661310
1. Check for a missing cable or wrap connector.
2. This error can occur when a shared device is being
not available.
Response: The I/O processor or I/O adapter error log port was left open.
is being filled faster than the errors are being reported 3. This error can occur if there is a port or link failure.
to the system. Check other errors reported to the If you have eliminated the above possibilities
system and correct them. contact your next level of support.
Failing Item:
27663020
v FCPORT
Explanation: I/O processor detected a configuration v FCIOA
error.
v FCDEV
Response: Either too many devices or the wrong kind v OPT_CLN
Change the configuration.
27663140
Failing Item:
v SVCDOCS
now operational.
27663100
Explanation: I/O processor card detected interface since the port is now operational.
error.
v FCINTF Explanation: A disk device reported a failure.
v ANYFC
Failing Item:
v FCIOA
v FCDEV
v OPT_CLN
v FCIOA
v IOP
27663120
v OPT_CLN
Explanation: An open port was detected on port 0.

27663400 • 27669091
27663400 27668150
Explanation: I/O processor card detected device error. Explanation: A permanent I/O processor failure
occurred.
Failing Item:
v FCDEV Failing Item:
v FCINTF v FCIOA
v ANYFC v ANYBRDG
v FCIOA v OPT_CLN
v OPT_CLN
27668151
276634FF Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
progress. When the format is complete, the device v AJDGP01
should be useable. No action is required. This reference v FCIOA
code is logged for information only. v IOP
v OPT_CLN
27668130
Failing Item:
27668140 v AJDGP01
Explanation: Recovered Fibre Channel interface error. v FCIOA
27668156
Explanation: IOA detected recoverable device error. occurred.
Response: No action required. This reference code is Failing Item:

logged for information only. v AJDGP01
v FCIOA
27668145 v OPT_CLN
occurred. 27669091
Failing Item: Explanation: Incorrect hardware configuration change
v FCIOA has been detected.
v OPT_CLN Response: Reset the I/O processor and then IPL the
27668146
Explanation: Disk device detected recoverable error. resolve the problem, contact your next level of support.

v FCDEV v SVCDOCS

27669092 • 27672201
v SVCDOCS
27669092
2766FF3D
has been detected.
Explanation: Recovered IOA error.
Response: Reset the I/O processor and then IPL the
I/O processor. For information about how to reset and Failing Item:
IPL the I/O processor, see Debug the resource. If an v FCIOA
resolve the problem, contact your next level of support. v ANYBRDG
v OPT_CLN
Failing Item:

27670A17
Failing Item:
occurred. v AJDGP01
v AJDG301
Failing Item:
v IOP
27671310
v MA_BRDG
v AJDGP01 Explanation: I/O processor resource not available.
v AJDG301 Response: The I/O processor error log is being filled
27670A22
them.
error.
27671317
Failing Item:
v AJDGP01
v AJDG301
v IOP the IOP. If the Failing Item indicates SVCDOCS, then
v MA_BRDG do NOT replace the IOP. This is a recoverable error.
Perform the following:
2767102E 1. If the I/O Processor is not operable and disk units
Failing Item: need to be Varied On.
v FI01105 2. If disk units are not attached, perform the VRYCFG
27671306 attached resources.
Explanation: I/O processor card or Licensed Internal Failing Item:

Code error. v SVCDOCS
I/O processor. 27672200
v AJDGP01 error.
v IOP Failing Item:

v FI01104 v AJDGP01
v BACKPLN
27672201
27671307 Explanation: Removable media error during IPL.

27672202 • 27673080
Failing Item:
27673020
v USER
v FI01105
27672202
Failing Item:
v IOPIP17
Failing Item:
v USER
v FI00022
v FI01107
v FI01105
v STORIOA
27673000
27673021
occurred.
Failing Item:
v FI01101
Failing Item:
v IOP
v IOPIP17
v MA_BRDG
v USER
v FI01107
27673001
v STORIOA
Licensed Internal Code.
27673022
condition that should not have occurred. Explanation: I/O processor detected a SCSI bus
Failing Item:
v IOP
v IOPIP17
27673002 v USER
v FI01107
selection. v STORIOA
Failing Item:
27673023
v IOPIP16
v FI01105 Explanation: I/O processor detected a SCSI bus
v STORIOA
v FI01140 Response: Error occurred on SCSI bus 3.
v FI01106 v IOPIP17
v USER
27673006 v FI01107
Explanation: System bus error. v STORIOA
Failing Item:
27673080
v IOP
v ANYBUS Explanation: I/O processor Licensed Internal Code
error.
v FI01101
Failing Item:
v AJDGP01

27673081 • 27673110
27673081 27673102
Explanation: System log entry only, no service action Explanation: I/O processor card detected interface
required. error.
27673084
Failing Item:
Explanation: I/O processor card or Licensed Internal v IOPIP13
Code error.
v FI01107
Response: A microprocessor exception occurred on the v STORIOA
I/O processor.
v FI01140
v AJDGP01
v IOP 27673103
v FI01104
v MA_BRDG error.
27673087
Failing Item:
v IOPIP13
Response: The Licensed Internal Code could not v FI01107
v STORIOA
v AJDGP01 v DEVBPLN
v AJDG301
v IOACNFG 27673109
v FI01104
Explanation: I/O processor timed out a device
command.
27673100
Failing Item:
Explanation: I/O processor card detected interface v IOPIP16
error.
v FI01105
v IOPIP13 v BACKPLN
v FI01107 v FI01106
v STORIOA
v FI01140 27673110
v DEVBPLN Explanation: I/O processor card detected interface
error.
error. v FI01105
v IOPIP13 v BACKPLN
v FI01107 v FI01106
v STORIOA
v FI01140
v DEVBPLN

27673120 • 27673200

27673120
27673141
not operational.
now operational.
operational. Remove the device. Response: This reference code and the 3121 reference
Failing Item:
v SVCDOCS
27673142
27673121
Explanation: I/O Processor detected that the bus is now operational.
not operational.
Response: A device was added to SCSI bus 1 of the code that occurred before it require no service action,
I/O Adapter and caused the bus to become not since SCSI bus 2 is now operational.
v SVCDOCS
now operational.
27673122
Explanation: I/O Processor detected that the bus is code that occurred before it require no service action,
not operational. since SCSI bus 3 is now operational.
I/O Adapter and caused the bus to become not 27673150
Failing Item: configuration error.
v SVCDOCS Response: Internal and external SCSI cables are
27673123 SCSI bus 0 configuration.

not operational. v SVCDOCS
Explanation: The removable media device is assigned Failing Item:

elsewhere. v SVCDOCS
Failing Item:
v USER 27673200
v FI01105 Explanation: A tape/CD or disk device reported a
failure.
Explanation: I/O Processor detected that the bus is v FI01105
now operational. v STORIOA
Response: This reference code and the 3120 reference v IOP
code that occurred before it require no service action, v MEDIA

27673203 • 27676073
27673203 27673401
Explanation: Disk media format bad. Explanation: Device backplane problem.
v FI01105 v DEVBPLN
27673205 27673501
Explanation: Disk sector read error. Explanation: I/O processor Licensed Internal Code
error.
but the disk unit does not need to be replaced. Failing Item:
v FI01105 v IOP
27673215 27673600
Explanation: Disk sector read error. Explanation: System log entry only, no service action
required.
27673601
Failing Item:
v FI01105
required.
27673250
27676070
use.
occurred.
Response: Perform a D-IPL and work on errors found
Failing Item:
in the log.
v IOP
Failing Item:
v USER
27676071
27673300
error.
Failing Item:
v IOPIP01
v MEDIA 27676072
v FI00121
v FI01141 error.
Failing Item:
27673400
v AJDGP01
Explanation: I/O processor card detected device error. v IOP
check EXTSCSI and DEVTERM first. 27676073
Failing Item: Explanation: IPL device not ready.
v FI02112
Failing Item:
v STORIOA
v MEDIA
v FI01106
v FI01105
v DEVTERM
v USER
v FI01140

27676075 • 27678005
v OPT_CLN
27676075
27676201
Failing Item:
Explanation: IOA LID is not valid.
v AJDGP01
Failing Item:
v AJDGP01
27676076
Explanation: I/O processor card detected media error.
27676602
Failing Item:
v MEDIA error occurred.
v AJDGP01
Failing Item:
v FI01105
v AJDGP01
27676081
27678000
Explanation: A permanent IOP or cache adapter card
error.
failure occurred.
Failing Item:
v AJDGP01 time. Exchange the FRUs one at a time in the order
v IOP shown.
Failing Item:
27676082 v STORIOA
Explanation: I/O processor Licensed Internal Code v CACHE
error.
v AJDGP01 Explanation: A permanent cache adapter card failure
v IOP occurred.
27676083 time. Exchange the FRUs one at a time in the order
shown.
Failing Item: v CACHE
v AJDGP01 v STORIOA
v IOP
27678004
27676085 Explanation: Voltage drop detected on I/O processor
5 volt power supply.
v AJDGP01 v STORIOA
v IOP
v MA_BRDG 27678005
27676200 error occurred.
Explanation: A permanent IOA hardware error Response: DO NOT replace both FRUs at the same
occurred. time. Exchange the FRUs one at a time in the order
shown.
Failing Item:
Failing Item:
v FCIOA

27678007 • 27678150
v STORIOA
27678131
v CACHE
error.
27678007
Explanation: A recoverable cache adapter card error is required. This reference code is logged for
occurred. information only.
time. Exchange the FRUs one at a time in the order 27678132
shown.
v CACHE
v STORIOA is required. This reference code is logged for
information only.
27678010
Explanation: A permanent cache adapter card failure 27678133
occurred. Explanation: IOA detected recoverable device bus
Response: The cache adapter card may be missing, error.
broken or incompatible. Response: An error occurred on SCSI bus 3. No action
DO NOT replace both FRUs at the same time. is required. This reference code is logged for
Exchange the FRUs one at a time in the order shown. information only.
Failing Item:
27678140
v CACHE
v STORIOA Explanation: IOA detected recoverable device bus
error.

occurred.
27678141
broken or incompatible. Explanation: IOA detected recoverable device error.
DO NOT replace both FRUs at the same time. Response: No action is required. This reference code
Exchange the FRUs one at a time in the order shown. is logged for information only.
Failing Item:
27678145
v CACHE
v STORIOA Explanation: A recoverable I/O processor error
occurred.

v STORIOA
error.
27678146
Failing Item:
v AJDGP01 Explanation: Disk device detected recoverable error.
v IOP Failing Item:
v FI01105
27678130
Explanation: IOA detected recoverable device bus 27678150
error. Explanation: A permanent I/O processor failure
Response: An error occurred on SCSI bus 0. No action occurred.
is required. This reference code is logged for Failing Item:
information only.

27678151 • 27679002
v STORIOA
27678300
v ANYBRDG
Code error.
27678151
Explanation: I/O processor Licensed Internal Code I/O processor.
error.
Failing Item:
Failing Item:
v STORIOA
v AJDGP01
v IOP
v STORIOA
v AJDGP01
27678155
27678301
occurred.
Failing Item:
v AJDGP01 condition that should not have occurred.
v STORIOA
Failing Item:
v FI01101
27678156
v AJDGP01
Explanation: A permanent I/O processor failure v IOP
occurred.
v AJDGP01
v STORIOA error.
Failing Item:
27678157
v AJDGP01
Response: Display the Service Action Log entry for 27679000
SVCDOCS, then do NOT replace the I/O adapter. This Failing Item:
is a recoverable error. Perform the following for the v FI01105
v STORIOA
27679001
need to be Varied On. Explanation: I/O processor card detected device
RESET(*YES) command to reset the IOP and Vary On Failing Item:
attached resources. v IOPIP33
Failing Item:
v SVCDOCS 27679002
27678200
Failing Item:
Explanation: I/O processor Licensed Internal Code v IOPIP16
error.
v FI01105
v AJDGP01 v FI01140
v IOP v BACKPLN

27679008 • 27679028
v FI01106
27679021
27679008
Failing Item:
v IOPIP20
Failing Item:
v IOPIP25
27679022
27679009
Failing Item:
assistance.
v IOPIP22
Failing Item:
v SVCDOCS
27679023
27679010
Failing Item:
v IOPIP22
Failing Item:
v IOPIP31
27679024
27679011
Failing Item:
those attached.
v IOPIP22
Failing Item:
v IOPIP32
27679025
27679012
location.
Explanation: IOP requires a cache adapter card but
Failing Item:
cannot find it.
v IOPIP21
broken.
27679026
Failing Item:
v IOPIP29
v CACHE
Failing Item:
v IOPIP22
27679013
27679027
are not compatible.
Failing Item:
v IOPIP19
Failing Item:
v IOPIP34
27679020
27679028
Failing Item:
has been detected.
v IOPIP20

27679029 • 27679054

27679050
Failing Item:
for a disk unit.
v SVCDOCS
Failing Item:
v IOPIP30
27679029
27679051
has been detected.
Explanation: IOP cache data exists for a missing or
failed device.
Failing Item:
v SVCDOCS reference code may appear in the product activity log.
2767902F reference code.
Explanation: Array addendum Product Activity Log Otherwise, perform the procedure indicated in the
entry. failing item list.
Response: This entry contains additional array Failing Item:

information for 90xx reference codes when the array v IOPIP27
contains more than 10 members. Use the 90xx entry
27679052
the starting point for this problem.
been modified.
27679030
Failing Item:
missing or failed disk unit. v IOPIP28
Failing Item:
27679053
v IOPIP21
previous problems.
27679031
Failing Item:
27679040
v SVCDOCS
Response: No action required. Protection will be 27679054
previous problems.
27679041
Explanation: Background array parity check detected or replacement disk units. IPL the system to DST. If
and corrected errors. you cannot perform a type A or B IPL, perform a type
Response: Call your next level of support to report D IPL from removable media.
Failing Item: reference codes and take action on them.
v SVCDOCS

27679081 • 2767B3B8
27679081 2767B3B1
occurred.
Failing Item:
v STORIOA v IOP
27679082 2767B3B2
occurred.
Failing Item:
Failing Item:
v IOPIP16
v IOP
v FI01105
v STORIOA
2767B3B3
v FI01140
v BACKPLN Explanation: A permanent I/O processor failure
occurred.
v FI01106
Failing Item:
27679090 v IOP

last known status. 2767B3B4
Response: Re-IPL the system. If any reference codes Explanation: A permanent I/O processor failure
are surfaced, use the new reference code to resolve the occurred.
problem. Failing Item:
If you cannot resolve the problem, contact your next v IOP
level of support.
Failing Item: 2767B3B5
v SVCDOCS Explanation: A permanent I/O processor failure
occurred.
Explanation: Incorrect hardware configuration change v IOP
has been detected.
Response: Re-IPL the system. If any reference codes 2767B3B6
problem.
occurred.
Failing Item:
level of support.
v IOP
Failing Item:
v SVCDOCS
2767B3B7
27679092
occurred.
Failing Item:
use.
v IOP
Failing Item:
v IOPIP26
2767B3B8
Explanation: Multi-adapter Bridge error detected.
Failing Item:
v MA_BRDG

2767B3B9 • 27680A22
v IOP Failing Item:

v IOPIP16
2767B3B9 v FI01107
occurred. v STORIOA
Failing Item: v DEVTERM
v IOP
2767B935
2767B3E0 Explanation: Unknown hardware detected.
Explanation: I/O processor detected a fault condition. Failing Item:
v IOP v AJDGP01
v MA_BRDG v IOP
v MA_BRDG
2767B3E1
2767BE00
Failing Item:
v IOP Failing Item:
v MA_BRDG v AJDGP01
v IOP
2767B410 v FI01104
v MA_BRDG
occurred.
2767FF3D
Failing Item:
v STORIOA Explanation: I/O adapter detected recoverable error.
Failing Item:
2767B411 v STORIOA
Explanation: A permanent I/O processor failure v ANYBRDG
occurred.
Failing Item: 2767FF6D
v STORIOA Explanation: I/O processor detected a recoverable
system bus error.
Explanation: Tape/CD or disk bus interface error v IOP
occurred. v ANYBUS

27680A17 27680A22
Explanation: A permanent I/O processor failure Explanation: I/O processor detected a storage transfer
occurred. error.
v IOP v AJDGP01
v MA_BRDG v AJDG301
v AJDGP01 v IOP
v AJDG301 v MA_BRDG

2768102E • 27683002
2768102E 27682200
Explanation: Out of alternate sectors for disk storage. Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
v AJDGP01
27681306
27682201
Code error. Explanation: Removable media error during IPL.
Response: A microprocessor exception occurred on the Failing Item:
I/O processor. v USER
v AJDGP01
v IOP 27682202
v FI01104 Explanation: Removable media error during IPL.
v BACKPLN
Failing Item:
v FI00022
27681307
v FI01105
v AJDGP01 Explanation: A permanent I/O processor failure
v AJDG301 occurred.
Failing Item:
27681310 v FI01101
Explanation: I/O processor resource not available. v IOP
Response: The I/O processor error log is being filled v MA_BRDG
Check other errors reported to the system and correct 27683001
them.
27681317
Explanation: I/O processor card error. condition that should not have occurred.
Response: Display the Service Action Log entry for Failing Item:
v IOP
do NOT replace the IOP. This is a recoverable error. v AJDGP01
1. If the I/O Processor is not operable and disk units 27683002
are attached, use Hardware Service Manager to re-IPL Explanation: Addressed device failed to respond to
the IOP. Other resources attached to the IOP may then selection.
Failing Item:
RESET(*YES) command to reset the IOP and Vary On v IOPIP16
v SVCDOCS v FI01140
v FI01141
v FI01106

27683006 • 27683101
27683006 27683080
Explanation: System bus error. Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
v IOP Failing Item:
v ANYBUS v AJDGP01
v FI01101
27683081
required.
27683084
Failing Item:
Code error.
v IOPIP17
v USER
I/O processor.
v FI01107
Failing Item:
v STORIOA
v AJDGP01
v IOP
27683021
v FI01104
v MA_BRDG
27683087
Failing Item:
v IOPIP17
Response: The Licensed Internal Code could not
v USER
v FI01107
Failing Item:
v STORIOA
v AJDGP01
v AJDG301
27683022
v IOACNFG
v FI01104
27683100
Failing Item:
v IOPIP17 error.
v USER
v FI01107
Failing Item:
v STORIOA
v IOPIP13
v FI01107
27683023
v STORIOA
v FI01140
v DEVBPLN
v IOPIP17
v USER error.
v FI01107
v STORIOA

27683102 • 27683136

v IOPIP13 v BACKPLN
v FI01107 v FI01106
v STORIOA
v FI01140 27683120
not operational.
27683102 Response: A device was added to SCSI bus 0 of the

v SVCDOCS
Failing Item:
v IOPIP13
27683121
v FI01107
not operational.
v FI01140
27683103
Failing Item:
v SVCDOCS
error.
27683122
Failing Item:
v IOPIP13 not operational.
v FI01107
v STORIOA I/O Adapter and caused the bus to become not
v SVCDOCS
27683109
Explanation: I/O processor timed out a device 27683123
command.
Failing Item: not operational.
v IOPIP16 Response: A device was added to SCSI bus 3 of the
v STORIOA operational. Remove the device.

v BACKPLN v SVCDOCS
v FI01106
27683136
27683110 Explanation: The removable media device is assigned
Explanation: I/O processor card detected interface elsewhere.
v IOPIP16 v FI01105
v FI01105
v STORIOA

27683140 • 27683300
27683140 27683200
Explanation: I/O Processor detected that the bus is Explanation: A tape/CD or disk device reported a
now operational. failure.
Response: This reference code and the 3120 reference Failing Item:
code that occurred before it require no service action, v FI01105
v STORIOA
v IOP
27683141
v MEDIA
now operational.
27683203
v FI01105
27683142
now operational. Explanation: Disk sector read error.
Response: This reference code and the 3122 reference Response: Disk unit data may need to be reloaded,
code that occurred before it require no service action, but the disk unit does not need to be replaced.
Failing Item:
27683143 v FI01105

Response: This reference code and the 3123 reference Explanation: Disk sector read error.
code that occurred before it require no service action, Response: Disk unit data may need to be reloaded,
since SCSI bus 3 is now operational. but the disk unit does not need to be replaced.
Failing Item:
27683150
v FI01105
27683250
Response: Internal and external SCSI cables are
use.
Failing Item:
in the log.
v SVCDOCS
Failing Item:
v USER
27683151
27683300
connected to SCSI bus 1 at the same time. Correct the Failing Item:
SCSI bus 1 configuration. v IOPIP01
v SVCDOCS v FI00121
v FI01141

27683400 • 27686083
27683400 27686072
Explanation: I/O processor card detected device error. Explanation: I/O processor Licensed Internal Code
error.
check EXTSCSI and DEVTERM first. Failing Item:
v FI02112 v IOP
v STORIOA
v FI01106 27686073
v DEVTERM Explanation: IPL device not ready.
v MEDIA
27683401 v FI01105
Explanation: Device backplane problem. v USER
Failing Item:
v DEVBPLN 27686075
Explanation: I/O processor Licensed Internal Code v AJDGP01
error.
v AJDGP01 Explanation: I/O processor card detected media error.
v IOP
Failing Item:
v MEDIA
27683600
v AJDGP01
Explanation: System log entry only, no service action v FI01105
required.
27686081
27683601
Explanation: System log entry only, no service action error.
required.
Failing Item:
v AJDGP01
27686070
v IOP
occurred.
27686082
Failing Item:
v IOP
error.
Failing Item:
27686071
v AJDGP01
v IOP
error.
Failing Item:
27686083
v AJDGP01
error.
Failing Item:
v AJDGP01
v IOP

27686085 • 27688011
27686085 27688004
Explanation: I/O processor Licensed Internal Code Explanation: Voltage drop detected on I/O processor
error. 5 volt power supply.
v AJDGP01 v FI01141
v IOP v STORIOA
v MA_BRDG
27688005
27686200 Explanation: A recoverable IOP or cache adapter card
Explanation: A permanent IOA hardware error error occurred.
occurred. Response: DO NOT replace both FRUs at the same
Failing Item: time. Exchange the FRUs one at a time in the order
shown.
v FCIOA
v OPT_CLN Failing Item:
v STORIOA
27686201 v CACHE

27688007
Failing Item:
Explanation: A recoverable cache adapter card error
v AJDGP01
occurred.
27686602
Explanation: An I/O processor Licensed Internal Code shown.
error occurred.
Failing Item:
v AJDGP01 v STORIOA
27688000 27688010
Explanation: A permanent IOP or cache adapter card Explanation: A permanent cache adapter card failure
failure occurred. occurred.
Response: DO NOT replace both FRUs at the same Response: The cache adapter card may be missing,
time. Exchange the FRUs one at a time in the order broken or incompatible.
shown.
DO NOT replace both FRUs at the same time.
Failing Item: Exchange the FRUs one at a time in the order shown.
v STORIOA
Failing Item:
v CACHE
v CACHE
v STORIOA
27688002
occurred.
Response: DO NOT replace both FRUs at the same occurred.
shown. Response: The cache adapter card may be missing,
broken or incompatible.
Failing Item:
v CACHE
v STORIOA
Failing Item:
v CACHE

27688100 • 27688157
v STORIOA
27688145
27688100
occurred.
Failing Item:
error.
v STORIOA
Failing Item:
v AJDGP01
27688146
v IOP

v FI01105
error.
27688150
Failing Item:
27688131 v STORIOA
Explanation: IOA detected recoverable device bus v ANYBRDG
error.
information only.
error.
Failing Item:
27688132
v AJDGP01
v STORIOA
error.
27688155
occurred.
error. v STORIOA
information only.
occurred.
27688140
Failing Item:
error.
v STORIOA
27688157
27688141 Explanation: I/O adapter card error.
Explanation: IOA detected recoverable device error. Response: Display the Service Action Log entry for
Response: No action is required. This reference code replace the I/O adapter. If the Failing Item indicates
is logged for information only. SVCDOCS, then do NOT replace the I/O adapter. This
is a recoverable error. Perform the following for the

27688200 • 27689012
1. If the I/O Processor is not operable and disk units v STORIOA

27689001
attached resources. Failing Item:
v SVCDOCS
27689002
Explanation: I/O processor Licensed Internal Code Failing Item:
error. v IOPIP16
v AJDGP01 v STORIOA
v IOP v FI01140
v BACKPLN
27688300 v FI01106
Code error. 27689008
Response: A microprocessor exception occurred on the Explanation: I/O card does not support functions
I/O processor. expected by devices.
v STORIOA v IOPIP25
v IOP
v AJDGP01 27689009
27688301 assistance.
Explanation: Not valid condition in I/O Processor Failing Item:
v FI01101 devices cannot be found.
v IOP v IOPIP31
27688400 27689011
v AJDGP01 v IOPIP32
27689000 27689012
Failing Item: cannot find it.
v FI01105 Response: The cache adapter card is missing or
broken.

27689013 • 27689031
Failing Item:
27689026
v IOPIP29
v CACHE
Failing Item:
27689013
v IOPIP22
are not compatible.
27689027
Failing Item:
v IOPIP19
Failing Item:
27689020
v IOPIP34
27689028
Failing Item:
v IOPIP20
has been detected.
27689021
Explanation: Array not functional due to present supports arrays, or stop an array on this IOP.
Failing Item:
v IOPIP20
27689029
27689022
Explanation: Array not functional due to present has been detected.
Failing Item:
Failing Item:
v IOPIP22
v SVCDOCS
27689023
2768902F
entry.
Failing Item:
v IOPIP22 information for 90xx reference codes when the array
27689024 that occurred at the same time as this reference code as
27689030
Failing Item:
v IOPIP22 missing or failed disk unit.
Failing Item:
27689025
v IOPIP21
location.
27689031
Failing Item:
v IOPIP21

27689040 • 27689091
unit was used to automatically rebuild the array. Look IOP reference codes and take action on them.
Failing Item:
v SVCDOCS
27689040
Explanation: Array protection temporarily suspended. 27689054
Response: No action required. Protection will be Explanation: IOP resources not available due to
automatically restarted. previous problems.
27689041 or replacement disk units. IPL the system to DST. If
Explanation: Background array parity check detected you cannot perform a type A or B IPL, perform a type
and corrected errors. D IPL from removable media.
Response: Call your next level of support to report Look for Product Activity Log entries for other IOP
the problem. reference codes and take action on them.

v AJDGP01 v SVCDOCS
27689050 27689081
for a disk unit. Failing Item:
v IOPIP30 v STORIOA
27689051 27689082
failed device.
Failing Item:
Response: If all configured units are missing, a 9054 v IOPIP16
v FI01105
v FI01140
v FI01106
Failing Item:
v IOPIP27
27689090

last known status.
Failing Item: problem.
v IOPIP28
level of support.
27689053
Failing Item:
Explanation: IOP resources not available due to v SVCDOCS
previous problems.
Response: Take action on other IOP reference codes 27689091
If you cannot get to SST or DST, and cannot perform a has been detected.

27689092 • 2768B410

2768B3B6
problem.
occurred.
level of support.
Failing Item:
Failing Item:
v IOP
v SVCDOCS
2768B3B7
27689092
occurred.
use.
Failing Item:
Failing Item:
v IOP
v IOPIP26
2768B3B8
2768B3B1
occurred. Failing Item:
Failing Item: v MA_BRDG
v IOP v IOP
2768B3B2 2768B3B9
Explanation: A permanent I/O processor failure Explanation: A permanent I/O processor failure
occurred. occurred.

v IOP v IOP
2768B3B3 2768B3E0
Explanation: A permanent I/O processor failure Explanation: I/O processor detected a fault condition.
Failing Item: v IOP
v IOP v MA_BRDG
2768B3B4 2768B3E1
occurred.
Failing Item:
Failing Item: v IOP
v IOP v MA_BRDG
2768B3B5 2768B410
occurred. occurred.
v IOP v STORIOA

2768B411 • 2771B942
v MA_BRDG
2768B411
2768BE00
occurred.
Failing Item:
v AJDGP01
2768B412 v IOP
v FI01104
Explanation: Tape/CD or disk bus interface error
occurred. v MA_BRDG
Failing Item:
2768FF3D
v IOPIP16
v FI01107 Explanation: I/O adapter detected recoverable error.
v STORIOA v STORIOA
v DEVTERM v ANYBRDG
2768B935 2768FF6D
Explanation: Unknown hardware detected. Explanation: I/O processor detected a recoverable
system bus error.
Failing Item:
v AJDGP01 v IOP
v IOP v ANYBUS

2771B904 2771B941
Explanation: I/O Adapter Licensed Internal Code Explanation: One half of I/O adapter failed.
failed.
Failing Item:
v AJDGP01 v FI00718
v FI00719 v AJDGP01
2771B934 2771B942
Explanation: Incompatible hardware detected. Explanation: One half of I/O adapter failed.
v FI00719 v FI00719
v FI00718 v FI00718
v AJDGP01
2771B940
Failing Item:
v FI00719
v FI00718
v AJDGP01
v MA_BRDG

2772B904 • 27823023

v FI00718
2772B904
v AJDGP01
v MA_BRDG
failed.
Failing Item:
2772B941
v AJDGP01
v FI00719
Failing Item:
2772B934 v FI00719
v FI00718
v AJDGP01
Failing Item:
v FI00719
2772B942
v FI00718

v FI00719
v FI00718
Failing Item:
v AJDGP01
v FI00719

27821310
Response: The I/O processor error log is being filled
Failing Item:
Check other errors reported to the system and correct v IOPIP17
them. v USER
v FI01107
27823006 v STORIOA
27823022
Failing Item:
v IOP Explanation: I/O processor detected a SCSI bus
v ANYBUS
v STORIOA Response: Error occurred on SCSI bus 2.
Failing Item:
27823020 v IOPIP17
Explanation: I/O processor detected a SCSI bus v USER
Failing Item:
27823023
v IOPIP17
v USER Explanation: I/O processor detected a SCSI bus
v FI01107
v STORIOA Response: Error occurred on SCSI bus 3.
Failing Item:
27823021 v IOPIP17

27823100 • 27823140
v USER v DEVBPLN
v FI01107
v STORIOA 27823120
27823100 not operational.
Explanation: I/O processor card detected interface Response: A device was added to SCSI bus 0 of the
error. I/O Adapter and caused the bus to become not
Failing Item:
Failing Item:
v SVCDOCS
v IOPIP13
v FI01107
27823121
v STORIOA
not operational.
v DEVBPLN
27823101
Failing Item:
error.
v SVCDOCS
v IOPIP13
v STORIOA
v DEVBPLN operational. Remove the device.
Failing Item:
27823102 v SVCDOCS
error. 27823123
Response: Error occurred on SCSI bus 2. Explanation: I/O Processor detected that the bus is
v STORIOA
v DEVBPLN v SVCDOCS
27823103 27823140
error. now operational.
Response: Error occurred on SCSI bus 3. Response: This reference code and the 3120 reference
Failing Item: since SCSI bus 0 is now operational.
v IOPIP13
v FI01107
v STORIOA
v FI01140

27823141 • 27828012
27823141 27823401
Explanation: I/O Processor detected that the bus is Explanation: Device backplane problem.
now operational.
Failing Item:
Response: This reference code and the 3121 reference v DEVBPLN
27823501
27823142 Explanation: I/O processor Licensed Internal Code

error.
v AJDGP01
code that occurred before it require no service action, v IOP
27823600
Explanation: I/O Processor detected that the bus is required.
now operational.
Response: This reference code and the 3123 reference 27823601
code that occurred before it require no service action, Explanation: System log entry only, no service action
since SCSI bus 3 is now operational. required.
27823150 27828008
Explanation: I/O processor detected a SCSI bus Explanation: A permanent cache battery pack failure
configuration error. occurred.
Response: Internal and external SCSI cables are Response: NOTE: Under a certain configuration, this
connected to SCSI bus 0 at the same time. Correct the SRC may not represent an error that requires a service
SCSI bus 0 configuration. action. Depending on the configuration of the system,
Failing Item: the Storage IOA may have been altered and/or the
v SVCDOCS
27823151 each time the IOA is IPLed and it can be ignored.
Explanation: I/O processor detected a SCSI bus Failing Item:
configuration error. v CACHBAT
Response: Internal and external SCSI cables are v STORIOA
27828009
Failing Item:
v SVCDOCS
Failing Item:
v CACHBAT
27823400
27828012
Failing Item:
v FI02112 capacity supported by IOA.
v STORIOA
v FI01106 IOA.
v DEVTERM
Failing Item:
v FI01140
v SVCDOCS

27828100 • 27828156
27828100 27828145
Explanation: I/O processor Licensed Internal Code Explanation: A recoverable I/O processor error
error. occurred.
v AJDGP01 v STORIOA
v IOP
27828146
27828130 Explanation: Disk device detected recoverable error.
error.
v FI01105
27828150
information only.
occurred.
27828131
error.
Response: An error occurred on SCSI bus 1. No action the Storage IOA may have been altered and/or the
is required. This reference code is logged for Storage IOA Cache may have been disabled to allow
information only. attachment of OEM Storage that emulates a Load
27828132
Failing Item:
error. v STORIOA
v ANYBRDG
27828133 error.
error. v AJDGP01
Response: An error occurred on SCSI bus 3. No action v STORIOA
information only.
27828155
27828140
occurred.
Failing Item:
error.
v AJDGP01
v STORIOA
27828156
27828141
occurred.
Failing Item:
v AJDGP01
v STORIOA

27828157 • 27829023
27828157 27829008
Explanation: I/O adapter card error. Explanation: I/O card does not support functions
this SRC. If the Failing Item indicates I/O adapter, then Failing Item:
replace the I/O adapter. If the Failing Item indicates v IOPIP25
I/O processor that the I/O adapter is attached to: 27829009
1. If the I/O Processor is not operable and disk units Explanation: Call your next level of support for
are attached, use Hardware Service Manager to re-IPL assistance.
v SVCDOCS
attached resources. 27829010

v SVCDOCS
Failing Item:
27828200 v IOPIP31

error. 27829011
Failing Item: Explanation: Cache data belongs to devices other than

those attached.
v AJDGP01
v IOP Failing Item:
v IOPIP32
27829000
27829020
v FI01105
Failing Item:
v STORIOA
v IOPIP20
27829001
27829021
configuration error. Explanation: Array not functional due to present
Failing Item:
Failing Item:
v IOPIP33
v IOPIP20
27829002
27829022
v FI01105 v IOPIP22
v STORIOA
v FI01140 27829023
v BACKPLN
Failing Item:

27829024 • 27829042
v IOPIP22 contains more than 10 array members. Use the 90xx

code as the starting point for this problem.
27829024
27829030
Failing Item:
v IOPIP22
Failing Item:
v IOPIP21
27829025
27829031
location.
Failing Item:
27829026 for other reference codes and take action on them.
Failing Item: Explanation: A disk unit in a RAID array is missing
v IOPIP22 or failed.
27829027 unit should be replaced.
Explanation: Array not functional due to present Failing Item:
hardware configuration. v FI02112
v IOPIP34
27829040
27829028 Explanation: Array protection temporarily suspended.
Explanation: Incorrect hardware configuration change Response: No action required. Protection will be
has been detected. automatically restarted.
move all devices in an array to another IOP that 27829041
Failing Item: and corrected errors.
v SVCDOCS
the problem.
27829029
Failing Item:
Explanation: Incorrect hardware configuration change v AJDGP01
has been detected.
Response: Contact your next level of support. 27829042
Failing Item: Explanation: An array parity error has been detected
v SVCDOCS and corrected.
2782902F the problem.
Explanation: Array addendum Product Activity Log Failing Item:
entry. v NEXTLVL

27829050 • 27829090
27829050 27829071
Explanation: Required cache data cannot be located Explanation: Link from IOA to auxiliary cache IOA
for a disk unit. went operational.
Failing Item: Response: No service action required.
v IOPIP30
27829072
27829051 Explanation: Link from IOA to auxiliary cache IOA
Explanation: IOP cache data exists for a missing or went non-operational.
failed device. Response: No service action required.
reference code may appear in the product activity log. 27829073
reference code. Explanation: Incompatible or non-operational
failing item list. Failing Item:
v IOPIP40
Failing Item:
v IOPIP27
27829081
Explanation: Cache data exists for device that has Failing Item:
been modified. v FI01105
Response: Contact your next level of support. v STORIOA
Failing Item:
27829082
v SVCDOCS
Explanation: IOP resources not available due to v IOPIP16
previous problems. v FI01105
Response: Take action on other IOP reference codes v STORIOA
which have surfaced. v FI01140
If you cannot get to SST or DST, and cannot perform a v BACKPLN
type A or B IPL, perform a type D IPL from removable v FI01106
27829090
Failing Item:
v SVCDOCS last known status.
27829054 are surfaced, use the new reference code to resolve the
Explanation: IOP resources not available due to problem.
previous problems. If you cannot resolve the problem, contact your next
Response: Power off the system and remove all new level of support.
or replacement disk units. IPL the system to DST. If Failing Item:
D IPL from removable media. v SVCDOCS

Failing Item:
v SVCDOCS

27829091 • 27873140
v SVCDOCS
27829091
2782B934
has been detected.
are surfaced, use the new reference code to resolve the Failing Item:
problem. v STORIOA
level of support. 2782FF3D
Failing Item: Explanation: I/O adapter detected recoverable error.
v SVCDOCS
Failing Item:
v STORIOA
27829092
v ANYBRDG
use.
2782FF6D
Failing Item:
Explanation: I/O processor detected a recoverable
v IOPIP26 system bus error.
Failing Item:
27829093
v IOP
Explanation: Read cache device not in correct format. v ANYBUS
Failing Item:

v OPT_CLN
27871310
27873120
not available.
is being filled faster than the errors are being reported Problem determination: Perform the following steps:
to the system. Check other errors reported to the 1. Check for a missing cable or wrap connector.
system and correct them.
27873020 port was left open.
Explanation: I/O processor detected a configuration 3. This error can occur if there is a port or link failure.
error. If you have eliminated the above possibilities
Response: Either too many devices or the wrong kind
of devices have been configured under the IOA. Failing Item:
Change the configuration. v FCPORT
Failing Item: v FCIOA
v SVCDOCS v FCDEV
v OPT_CLN
27873100
27873140
error. Explanation: I/O Processor detected that a port is
now operational.
Failing Item:
v FCINTF Response: This reference code and the 3120 reference
v ANYFC
since the port is now operational.
v FCIOA

27873200 • 27879091
27873200 27878146
Explanation: A disk device reported a failure. Explanation: Disk device detected recoverable error.
v FCDEV v FCDEV
v FCIOA
v IOP 27878150
v OPT_CLN Explanation: A permanent I/O processor failure
occurred.
Explanation: I/O processor card detected device error. v FCIOA
v FCDEV v OPT_CLN
v FCINTF
v ANYFC 27878151
v FCIOA Explanation: I/O processor Licensed Internal Code
v OPT_CLN error.
Failing Item:
278734FF v AJDGP01
Explanation: Format in progress. v FCIOA
v IOP
progress. When the format is complete, the device v OPT_CLN
code is logged for information only. 27878155
27878130 occurred.
Explanation: Recovered Fibre Channel interface error. Failing Item:
v OPT_CLN
27878140
Failing Item:
27878141 v AJDGP01
Explanation: IOA detected recoverable device error. v FCIOA
27879091
27878145 Explanation: Incorrect hardware configuration change
Explanation: A recoverable I/O processor error has been detected.
occurred. Response: Reset the I/O processor and then IPL the
Failing Item: I/O processor. For information about how to reset and
v FCIOA
v OPT_CLN resolve the problem, contact your next level of support.
Failing Item:

27879092 • 280D3100
v SVCDOCS v SVCDOCS
27879092 2787FF3D
Explanation: Incorrect hardware configuration change Explanation: Recovered IOA error.
has been detected.
Failing Item:
Response: Reset the I/O processor and then IPL the v FCIOA
v ANYBRDG
I/O processor reset and I/O processor IPL does not v OPT_CLN
Failing Item:

v FI00719
2793A001
v AJDGP01
v MA_BRDG
Failing Item:
2793B941
v NEXTLVL

v FI00719
v AJDGP01
Failing Item:

v FI00719
2805A001
v AJDGP01
v MA_BRDG
Failing Item:
2805B941
v NEXTLVL

v FI00719
v AJDGP01
Failing Item:

280D1310
Explanation: I/O processor or I/O adapter resource Change the configuration.
not available.
Failing Item:
Response: The I/O processor or I/O adapter error log v SVCDOCS
to the system. Check other errors reported to the
system and correct them. 280D3100
280D3020 error.
Explanation: I/O processor detected a configuration Failing Item:

error. v FCINTF

280D3120 • 280D8151
v ANYFC
280D34FF
v FCIOA
v OPT_CLN
progress. When the format is complete, the device
280D3120
Explanation: An open port was detected on port 0. code is logged for information only.
1. Check for a missing cable or wrap connector. 280D8130
2. This error can occur when a shared device is being Explanation: Recovered Fibre Channel interface error.
port was left open.
3. This error can occur if there is a port or link failure.
contact your next level of support. 280D8140
Failing Item: Explanation: Recovered Fibre Channel interface error.

v FCPORT Response: No action required. This reference code is
v FCIOA logged for information only.
v FCDEV
v OPT_CLN 280D8141
280D3140 Response: No action required. This reference code is
Explanation: I/O Processor detected that a port is logged for information only.
now operational.
Response: This reference code and the 3120 reference 280D8145
code that occurred before it require no service action, Explanation: A recoverable I/O processor error
since the port is now operational. occurred.
Failing Item:
280D3200
v FCIOA
Explanation: A disk device reported a failure. v OPT_CLN
Failing Item:
v FCDEV 280D8146
v FCIOA Explanation: Disk device detected recoverable error.
v IOP
Failing Item:
v OPT_CLN
v FCDEV
280D3400
280D8150
v FCDEV Failing Item:
v FCINTF v FCIOA
v ANYFC v ANYBRDG
v FCIOA v OPT_CLN
v OPT_CLN
280D8151
error.
Failing Item:

280D8155 • 280E3140
v AJDGP01 Response: Reset the I/O processor and then IPL the
v FCIOA I/O processor. For information about how to reset and
v IOP
v OPT_CLN resolve the problem, contact your next level of support.
Failing Item:
280D8155
v SVCDOCS
occurred.
280D9092
Failing Item:
v AJDGP01 has been detected.
v FCIOA
v OPT_CLN I/O processor. For information about how to reset and
280D8156 I/O processor reset and I/O processor IPL does not
v SVCDOCS
Failing Item:
v AJDGP01
280DFF3D
v FCIOA
v OPT_CLN Explanation: Recovered IOA error.
Failing Item:
280D9091 v FCIOA
Explanation: Incorrect hardware configuration change v ANYBRDG
has been detected. v OPT_CLN

v FCINTF
280E1310
v ANYFC
v FCIOA
not available.
v OPT_CLN
to the system. Check other errors reported to the 280E3120
system and correct them. Explanation: An open port was detected on port 0.
280E3020
Explanation: I/O processor detected a configuration 2. This error can occur when a shared device is being
error. moved from one LPAR to another LPAR and the
Response: Either too many devices or the wrong kind port was left open.
of devices have been configured under the IOA. 3. This error can occur if there is a port or link failure.
Change the configuration. If you have eliminated the above possibilities
Failing Item:
v FCPORT
280E3100 v FCIOA
v FCDEV
error. v OPT_CLN
Failing Item:
280E3140

280E3200 • 280E8156

280E8145
now operational.
occurred.
since the port is now operational. Failing Item:
v FCIOA
280E3200 v OPT_CLN
Explanation: A disk device reported a failure.
280E8146
Failing Item:
v FCDEV Explanation: Disk device detected recoverable error.
v FCIOA Failing Item:
v IOP v FCDEV
v OPT_CLN
280E8150
280E3400 Explanation: A permanent I/O processor failure
Explanation: I/O processor card detected device error. occurred.

v FCDEV v FCIOA
v FCINTF v ANYBRDG
v ANYFC v OPT_CLN
v FCIOA
v OPT_CLN 280E8151
280E34FF error.

v AJDGP01
progress. When the format is complete, the device v FCIOA
should be useable. No action is required. This reference v IOP
code is logged for information only. v OPT_CLN
280E8130 280E8155
Explanation: Recovered Fibre Channel interface error. Explanation: A permanent I/O processor failure
Response: No action required. This reference code is occurred.
v AJDGP01
280E8140 v FCIOA
Explanation: Recovered Fibre Channel interface error. v OPT_CLN
logged for information only. 280E8156
280E8141 occurred.
Explanation: IOA detected recoverable device error. Failing Item:
v OPT_CLN

280E9091 • 283C1525

280E9091
Explanation: Incorrect hardware configuration change IPL the I/O processor, see Debug the resource. If an
has been detected. I/O processor reset and I/O processor IPL does not
I/O processor. For information about how to reset and Failing Item:
IPL the I/O processor, see Debug the resource. If an v SVCDOCS
280EFF3D
Failing Item:
v SVCDOCS
Failing Item:
280E9092 v FCIOA
v ANYBRDG
has been detected. v OPT_CLN

2838B904 2838B931
failed.
Failing Item:
v AJDGP01 v FI00718
v FI00719 v AJDGP01
v MA_BRDG
2838B930
failed.
Failing Item:
Failing Item:
v AJDGP01
v FI00719
v FI00718
v AJDGP01
v FI00719

v FI01106
283C1511
v DEVBPLN
Explanation: A non-fatal error occurred on power
supply 1.
283C1521
Failing Item:
v DISKPWR
supply 2.
v DISKFAN
Failing Item:
v FI01106
v DISKPWR
v DEVBPLN
v DISKFAN
v FI01106
283C1515
v DEVBPLN
Explanation: A fatal error occurred on power supply
1.
283C1525
Failing Item:
v DISKPWR
2.
v DISKFAN

283C3002 • 283CFFF4
Failing Item:
283C7631
v DISKPWR
Explanation: A fatal error occurred on redundant fan
v DISKFAN
3.
v FI01106
Failing Item:
v DEVBPLN
v DISKFAN
283C3002
283C7634
Explanation: Addressed device backplane failed to
respond to selection. Explanation: A fatal error occurred on fan 3.

v DEVBPLN v DISKFAN
v STORIOA
v FI01140 283C8401
v FI01106 Explanation: Removable media power fault.
Failing Item:
283C3109 v DEVBPLN
Explanation: I/O adapter timed out a device
backplane command. 283C8404
Failing Item: Explanation: System log entry only, no service action
v DEVBPLN required.
v STORIOA
v FI01140 283CFFF4
v FI01106 Explanation: Device backplane problem.
Failing Item:
283C7611
v DEVBPLN
Explanation: A fatal error occurred on redundant fan v STORIOA
1.
v FI01140
v DISKFAN
283C7614
Explanation: A fatal error occurred on fan 1.
Failing Item:
v DISKFAN
283C7621
2.
Failing Item:
v DISKFAN
283C7624
Failing Item:
v DISKFAN

283D1511 • 283D7634

283D1511 283D3109
Explanation: A non-fatal error occurred on power Explanation: I/O adapter timed out a device
supply 1. backplane command.
v DISKPWR v DEVBPLN
v DISKFAN v STORIOA
v FI01106 v FI01140
v DEVBPLN v FI01106
283D1515 283D7611
Explanation: A fatal error occurred on power supply Explanation: A fatal error occurred on redundant fan
1. 1.
v DISKPWR v DISKFAN
v DISKFAN
v FI01106 283D7614
v DEVBPLN Explanation: A fatal error occurred on fan 1.
Failing Item:
283D1521
v DISKFAN
supply 2.
283D7621
Failing Item:
v DISKPWR 2.
v DISKFAN
Failing Item:
v FI01106
v DISKFAN
v DEVBPLN
283D7624
283D1525
2. Failing Item:
v DISKFAN
Failing Item:
v DISKPWR
283D7631
v DISKFAN
v FI01106 Explanation: A fatal error occurred on redundant fan
3.
v DEVBPLN
Failing Item:
283D3002 v DISKFAN

respond to selection. 283D7634
Failing Item: Explanation: A fatal error occurred on fan 3.

v STORIOA v DISKFAN
v FI01140
v FI01106

283D8401 • 28422201
283D8401 283DFFF4
Explanation: Removable media power fault. Explanation: Device backplane problem.
v DEVBPLN v DEVBPLN
v STORIOA
283D8404 v FI01140
required.

Failing Item:
28420A17
v AJDGP01
v AJDG301
occurred.
Failing Item:
28421310
v IOP
v MA_BRDG
v AJDGP01 Response: The I/O processor error log is being filled
v AJDG301
them.
28420A22
Explanation: I/O processor detected a storage transfer 28421317
error.
Failing Item:
v AJDGP01 this SRC. If the Failing Item indicates IOP, then replace
v AJDG301 the IOP. If the Failing Item indicates SVCDOCS, then
v IOP do NOT replace the IOP. This is a recoverable error.
v MA_BRDG
2842102E
Explanation: Out of alternate sectors for disk storage. need to be Varied On.
Failing Item: 2. If disk units are not attached, perform the VRYCFG
v FI01105 RESET(*YES) command to reset the IOP and Vary On
attached resources.

v SVCDOCS
Code error.
28422200
I/O processor. Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
v IOP v AJDGP01
v FI01104
v BACKPLN 28422201
Explanation: I/O processor resource not available. v USER

28422202 • 28423080
v FI01105
28423020
28422202
Failing Item:
Failing Item:
v FI00022
v IOPIP17
v FI01105
v USER
v FI01107
28423000
v STORIOA
occurred.
28423021
Failing Item:
v FI01101 configuration error.
v IOP
v MA_BRDG
Failing Item:
v IOPIP17
28423001
v USER
v FI01107
v STORIOA
28423022
Failing Item:
v IOP
v AJDGP01

v IOPIP17
selection. v USER
v FI01107
Failing Item:
v STORIOA
v IOPIP16
v FI01105
28423023
v STORIOA
v FI01141
Failing Item:
28423006 v IOPIP17
Explanation: System bus error. v USER
v FI01107
Failing Item:
v STORIOA
v IOP
v ANYBUS
28423080
v FI01101
error.
Failing Item:
v AJDGP01

28423081 • 28423110
28423081 28423102
Explanation: System log entry only, no service action Explanation: I/O processor card detected interface
required. error.
28423084
Failing Item:
Explanation: I/O processor card or Licensed Internal v IOPIP13
Code error.
v FI01107
Response: A microprocessor exception occurred on the v STORIOA
I/O processor.
v FI01140
v AJDGP01
v IOP 28423103
v FI01104
v MA_BRDG error.
28423087
Failing Item:
v IOPIP13
Response: The Licensed Internal Code could not v FI01107
v STORIOA
v AJDGP01 v DEVBPLN
v AJDG301
v IOACNFG 28423109
v FI01104
command.
28423100
Failing Item:
error.
v FI01105
v IOPIP13 v BACKPLN
v FI01107 v FI01106
v STORIOA
v FI01140 28423110
v DEVBPLN Explanation: I/O processor card detected interface
error.
error. v FI01105
v IOPIP13 v BACKPLN
v FI01107 v FI01106
v STORIOA
v FI01140
v DEVBPLN

28423120 • 28423200

28423120
28423141
not operational.
now operational.
Failing Item:
v SVCDOCS
28423142
28423121
not operational.
v SVCDOCS
now operational.
28423122

not operational. v SVCDOCS
Explanation: The removable media device is assigned Failing Item:

elsewhere. v SVCDOCS
Failing Item:
v USER 28423200
v FI01105 Explanation: A tape/CD or disk device reported a
failure.
Explanation: I/O Processor detected that the bus is v FI01105
now operational. v STORIOA
Response: This reference code and the 3120 reference v IOP
code that occurred before it require no service action, v MEDIA

28423203 • 28426073
28423203 28423401
v FI01105 v DEVBPLN
28423205 28423501
error.
v FI01105 v IOP
28423215 28423600
required.
28423601
Failing Item:
v FI01105
required.
28423250
28426070
use.
occurred.
Failing Item:
in the log.
v IOP
Failing Item:
v USER
28426071
28423300
error.
Failing Item:
v IOPIP01
v MEDIA 28426072
v FI00121
v FI01141 error.
Failing Item:
28423400
v AJDGP01
check EXTSCSI and DEVTERM first. 28426073
v FI02112
Failing Item:
v STORIOA
v MEDIA
v FI01106
v FI01105
v DEVTERM
v USER
v FI01140

28426075 • 28428005
v OPT_CLN
28426075
28426201
Failing Item:
v AJDGP01
Failing Item:
v AJDGP01
28426076
28426602
Failing Item:
v MEDIA error occurred.
v AJDGP01
Failing Item:
v FI01105
v AJDGP01
28426081
28428000
Explanation: A permanent IOP or cache adapter card
error.
failure occurred.
Failing Item:
v AJDGP01 time. Exchange the FRUs one at a time in the order
v IOP shown.
Failing Item:
28426082 v STORIOA
Explanation: I/O processor Licensed Internal Code v CACHE
error.
v AJDGP01 Explanation: A permanent cache adapter card failure
v IOP occurred.
28426083 time. Exchange the FRUs one at a time in the order
shown.
v AJDGP01 v STORIOA
v IOP
28428004
28426085 Explanation: Voltage drop detected on I/O processor
v AJDGP01 v STORIOA
v IOP
v MA_BRDG 28428005
28426200 error occurred.
Explanation: A permanent IOA hardware error Response: DO NOT replace both FRUs at the same
occurred. time. Exchange the FRUs one at a time in the order
shown.
Failing Item:
Failing Item:
v FCIOA

28428007 • 28428150
v STORIOA
28428131
v CACHE
error.
28428007
Explanation: A recoverable cache adapter card error is required. This reference code is logged for
time. Exchange the FRUs one at a time in the order 28428132
shown.
v CACHE
v STORIOA is required. This reference code is logged for
information only.
28428010
occurred. Explanation: IOA detected recoverable device bus
Response: The cache adapter card may be missing, error.
broken or incompatible. Response: An error occurred on SCSI bus 3. No action
DO NOT replace both FRUs at the same time. is required. This reference code is logged for
Exchange the FRUs one at a time in the order shown. information only.
Failing Item:
28428140
v CACHE
error.

occurred.
28428141
broken or incompatible. Explanation: IOA detected recoverable device error.
DO NOT replace both FRUs at the same time. Response: No action is required. This reference code
Exchange the FRUs one at a time in the order shown. is logged for information only.
Failing Item:
28428145
v CACHE
v STORIOA Explanation: A recoverable I/O processor error
occurred.

v STORIOA
error.
28428146
Failing Item:
v AJDGP01 Explanation: Disk device detected recoverable error.
v IOP Failing Item:
v FI01105
28428130
Explanation: IOA detected recoverable device bus 28428150
error. Explanation: A permanent I/O processor failure
Response: An error occurred on SCSI bus 0. No action occurred.
information only.

28428151 • 28429002
v STORIOA
28428300
v ANYBRDG
Code error.
28428151
error.
Failing Item:
Failing Item:
v STORIOA
v AJDGP01
v IOP
v STORIOA
v AJDGP01
28428155
28428301
occurred.
Failing Item:
v STORIOA
Failing Item:
v FI01101
28428156
v AJDGP01
occurred.
v AJDGP01
v STORIOA error.
Failing Item:
28428157
v AJDGP01
Response: Display the Service Action Log entry for 28429000
v STORIOA
28429001
Failing Item:
v SVCDOCS 28429002
28428200
Failing Item:
error.
v FI01105
v AJDGP01 v FI01140
v IOP v BACKPLN

28429008 • 28429028
v FI01106
28429021
28429008
Failing Item:
v IOPIP20
Failing Item:
v IOPIP25
28429022
28429009
Failing Item:
assistance.
v IOPIP22
Failing Item:
v SVCDOCS
28429023
28429010
Failing Item:
v IOPIP22
Failing Item:
v IOPIP31
28429024
28429011
Failing Item:
those attached.
v IOPIP22
Failing Item:
v IOPIP32
28429025
28429012
location.
Failing Item:
cannot find it.
v IOPIP21
broken.
28429026
Failing Item:
v IOPIP29
v CACHE
Failing Item:
v IOPIP22
28429013
28429027
are not compatible.
Failing Item:
v IOPIP19
Failing Item:
v IOPIP34
28429020
28429028
Failing Item:
has been detected.
v IOPIP20

28429029 • 28429054

28429050
Failing Item:
for a disk unit.
v SVCDOCS
Failing Item:
v IOPIP30
28429029
28429051
has been detected.
failed device.
Failing Item:
2842902F reference code.

28429052
been modified.
28429030
Failing Item:
Failing Item:
28429053
v IOPIP21
previous problems.
28429031
Failing Item:
28429040
v SVCDOCS
Response: No action required. Protection will be 28429054
previous problems.
28429041
v SVCDOCS

28429081 • 2842B3B8
28429081 2842B3B1
occurred.
Failing Item:
v STORIOA v IOP
28429082 2842B3B2
occurred.
Failing Item:
Failing Item:
v IOPIP16
v IOP
v FI01105
v STORIOA
2842B3B3
v FI01140
occurred.
v FI01106
Failing Item:
28429090 v IOP

last known status. 2842B3B4
level of support.
occurred.
has been detected.
Response: Re-IPL the system. If any reference codes 2842B3B6
problem.
occurred.
Failing Item:
level of support.
v IOP
Failing Item:
v SVCDOCS
2842B3B7
28429092
occurred.
Failing Item:
use.
v IOP
Failing Item:
v IOPIP26
2842B3B8
Failing Item:
v MA_BRDG

2842B3B9 • 28430A22
v IOP Failing Item:

v IOPIP16
2842B3B9 v FI01107
occurred. v STORIOA
v IOP
2842B935
2842B3E0 Explanation: Unknown hardware detected.
v IOP v AJDGP01
v MA_BRDG v IOP
v MA_BRDG
2842B3E1
2842BE00
Failing Item:
v IOP Failing Item:
v MA_BRDG v AJDGP01
v IOP
2842B410 v FI01104
v MA_BRDG
occurred.
2842FF3D
Failing Item:
Failing Item:
2842B411 v STORIOA
occurred.
system bus error.
occurred. v ANYBUS

28430A17 28430A22
Explanation: A permanent I/O processor failure Explanation: I/O processor detected a storage transfer
occurred. error.
v IOP v AJDGP01
v MA_BRDG v AJDG301
v AJDGP01 v IOP
v AJDG301 v MA_BRDG

2843102E • 28433002
2843102E 28432200
Explanation: Out of alternate sectors for disk storage. Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
v AJDGP01
28431306
28432201
Code error. Explanation: Removable media error during IPL.
I/O processor. v USER
v AJDGP01
v IOP 28432202
v FI01104 Explanation: Removable media error during IPL.
v BACKPLN
Failing Item:
v FI00022
28431307
v FI01105
v AJDGP01 Explanation: A permanent I/O processor failure
v AJDG301 occurred.
Failing Item:
28431310 v FI01101
Response: The I/O processor error log is being filled v MA_BRDG
Check other errors reported to the system and correct 28433001
them.
28431317
Explanation: I/O processor card error. condition that should not have occurred.
Response: Display the Service Action Log entry for Failing Item:
v IOP
are attached, use Hardware Service Manager to re-IPL Explanation: Addressed device failed to respond to
the IOP. Other resources attached to the IOP may then selection.
Failing Item:
v SVCDOCS v FI01140
v FI01141
v FI01106

28433006 • 28433101
28433006 28433080
Explanation: System bus error. Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
v IOP Failing Item:
v ANYBUS v AJDGP01
v FI01101
28433081
required.
28433084
Failing Item:
Code error.
v IOPIP17
v USER
I/O processor.
v FI01107
Failing Item:
v STORIOA
v AJDGP01
v IOP
28433021
v FI01104
v MA_BRDG
28433087
Failing Item:
v IOPIP17
v USER
v FI01107
Failing Item:
v STORIOA
v AJDGP01
v AJDG301
28433022
v IOACNFG
v FI01104
28433100
Failing Item:
v IOPIP17 error.
v USER
v FI01107
Failing Item:
v STORIOA
v IOPIP13
v FI01107
28433023
v STORIOA
v FI01140
v DEVBPLN
v IOPIP17
v USER error.
v FI01107
v STORIOA

28433102 • 28433136

v IOPIP13 v BACKPLN
v FI01107 v FI01106
v STORIOA
v FI01140 28433120
not operational.
28433102 Response: A device was added to SCSI bus 0 of the

v SVCDOCS
Failing Item:
v IOPIP13
28433121
v FI01107
not operational.
v FI01140
28433103
Failing Item:
v SVCDOCS
error.
28433122
Failing Item:
v IOPIP13 not operational.
v FI01107
v STORIOA I/O Adapter and caused the bus to become not
v SVCDOCS
28433109
command.

v BACKPLN v SVCDOCS
v FI01106
28433136
v IOPIP16 v FI01105
v FI01105
v STORIOA

28433140 • 28433300
28433140 28433200
Explanation: I/O Processor detected that the bus is Explanation: A tape/CD or disk device reported a
now operational. failure.
v STORIOA
v IOP
28433141
v MEDIA
now operational.
28433203
v FI01105
28433142
now operational. Explanation: Disk sector read error.
Response: This reference code and the 3122 reference Response: Disk unit data may need to be reloaded,
code that occurred before it require no service action, but the disk unit does not need to be replaced.
Failing Item:
28433143 v FI01105

Response: This reference code and the 3123 reference Explanation: Disk sector read error.
code that occurred before it require no service action, Response: Disk unit data may need to be reloaded,
since SCSI bus 3 is now operational. but the disk unit does not need to be replaced.
Failing Item:
28433150
v FI01105
28433250
use.
Failing Item:
in the log.
v SVCDOCS
Failing Item:
v USER
28433151
28433300
SCSI bus 1 configuration. v IOPIP01
v SVCDOCS v FI00121
v FI01141

28433400 • 28436083
28433400 28436072
Explanation: I/O processor card detected device error. Explanation: I/O processor Licensed Internal Code
error.
check EXTSCSI and DEVTERM first. Failing Item:
v FI02112 v IOP
v STORIOA
v FI01106 28436073
v DEVTERM Explanation: IPL device not ready.
v MEDIA
28433401 v FI01105
Explanation: Device backplane problem. v USER
Failing Item:
v DEVBPLN 28436075
error.
v AJDGP01 Explanation: I/O processor card detected media error.
v IOP
Failing Item:
v MEDIA
28433600
v AJDGP01
required.
28436081
28433601
Explanation: System log entry only, no service action error.
required.
Failing Item:
v AJDGP01
28436070
v IOP
occurred.
28436082
Failing Item:
v IOP
error.
Failing Item:
28436071
v AJDGP01
v IOP
error.
Failing Item:
28436083
v AJDGP01
error.
Failing Item:
v AJDGP01
v IOP

28436085 • 28438011
28436085 28438004
Explanation: I/O processor Licensed Internal Code Explanation: Voltage drop detected on I/O processor
error. 5 volt power supply.
v AJDGP01 v FI01141
v IOP v STORIOA
v MA_BRDG
28438005
28436200 Explanation: A recoverable IOP or cache adapter card
Explanation: A permanent IOA hardware error error occurred.
occurred. Response: DO NOT replace both FRUs at the same
Failing Item: time. Exchange the FRUs one at a time in the order
shown.
v FCIOA
v STORIOA
28436201 v CACHE

28438007
Failing Item:
Explanation: A recoverable cache adapter card error
v AJDGP01
occurred.
28436602
Explanation: An I/O processor Licensed Internal Code shown.
error occurred.
Failing Item:
v AJDGP01 v STORIOA
28438000 28438010
shown.
v STORIOA
Failing Item:
v CACHE
v CACHE
v STORIOA
28438002
occurred.
shown. Response: The cache adapter card may be missing,
Failing Item:
v CACHE
v STORIOA
Failing Item:
v CACHE

28438100 • 28438157
v STORIOA
28438145
28438100
occurred.
Failing Item:
error.
v STORIOA
Failing Item:
v AJDGP01
28438146
v IOP

v FI01105
error.
28438150
Failing Item:
28438131 v STORIOA
Explanation: IOA detected recoverable device bus v ANYBRDG
error.
information only.
error.
Failing Item:
28438132
v AJDGP01
v STORIOA
error.
28438155
occurred.
error. v STORIOA
information only.
occurred.
28438140
Failing Item:
error.
v STORIOA
28438157
Explanation: IOA detected recoverable device error. Response: Display the Service Action Log entry for
Response: No action is required. This reference code replace the I/O adapter. If the Failing Item indicates
is logged for information only. SVCDOCS, then do NOT replace the I/O adapter. This

28438200 • 28439012
1. If the I/O Processor is not operable and disk units v STORIOA

28439001
attached resources. Failing Item:
v SVCDOCS
28439002
error. v IOPIP16
v AJDGP01 v STORIOA
v IOP v FI01140
v BACKPLN
28438300 v FI01106
Code error. 28439008
Response: A microprocessor exception occurred on the Explanation: I/O card does not support functions
I/O processor. expected by devices.
v STORIOA v IOPIP25
v IOP
v AJDGP01 28439009
28438301 assistance.
Explanation: Not valid condition in I/O Processor Failing Item:
v FI01101 devices cannot be found.
v IOP v IOPIP31
28438400 28439011
v AJDGP01 v IOPIP32
28439000 28439012
Failing Item: cannot find it.
v FI01105 Response: The cache adapter card is missing or
broken.

28439013 • 28439031
Failing Item:
28439026
v IOPIP29
v CACHE
Failing Item:
28439013
v IOPIP22
are not compatible.
28439027
Failing Item:
v IOPIP19
Failing Item:
28439020
v IOPIP34
28439028
Failing Item:
v IOPIP20
has been detected.
28439021
Explanation: Array not functional due to present supports arrays, or stop an array on this IOP.
Failing Item:
v IOPIP20
28439029
28439022
Explanation: Array not functional due to present has been detected.
Failing Item:
Failing Item:
v IOPIP22
v SVCDOCS
28439023
2843902F
entry.
Failing Item:
28439024 that occurred at the same time as this reference code as
28439030
Failing Item:
v IOPIP22 missing or failed disk unit.
Failing Item:
28439025
v IOPIP21
location.
28439031
Failing Item:
v IOPIP21

28439040 • 28439091
unit was used to automatically rebuild the array. Look IOP reference codes and take action on them.
Failing Item:
v SVCDOCS
28439040
Explanation: Array protection temporarily suspended. 28439054
Response: No action required. Protection will be Explanation: IOP resources not available due to
automatically restarted. previous problems.
28439041 or replacement disk units. IPL the system to DST. If
Explanation: Background array parity check detected you cannot perform a type A or B IPL, perform a type
and corrected errors. D IPL from removable media.
Response: Call your next level of support to report Look for Product Activity Log entries for other IOP
the problem. reference codes and take action on them.

v AJDGP01 v SVCDOCS
28439050 28439081
for a disk unit. Failing Item:
v IOPIP30 v STORIOA
28439051 28439082
failed device.
Failing Item:
v FI01105
v FI01140
v FI01106
Failing Item:
v IOPIP27
28439090

last known status.
v IOPIP28
level of support.
28439053
Failing Item:
previous problems.

28439092 • 2843B410

2843B3B6
problem.
occurred.
level of support.
Failing Item:
Failing Item:
v IOP
v SVCDOCS
2843B3B7
28439092
occurred.
use.
Failing Item:
Failing Item:
v IOP
v IOPIP26
2843B3B8
2843B3B1
v IOP v IOP
2843B3B2 2843B3B9
occurred. occurred.

v IOP v IOP
2843B3B3 2843B3E0
Failing Item: v IOP
v IOP v MA_BRDG
2843B3B4 2843B3E1
occurred.
Failing Item:
Failing Item: v IOP
v IOP v MA_BRDG
2843B3B5 2843B410
occurred. occurred.
v IOP v STORIOA

2843B411 • 28441310
v MA_BRDG
2843B411
2843BE00
occurred.
Failing Item:
v AJDGP01
2843B412 v IOP
v FI01104
Explanation: Tape/CD or disk bus interface error
occurred. v MA_BRDG
Failing Item:
2843FF3D
v IOPIP16
v FI01107 Explanation: I/O adapter detected recoverable error.
v STORIOA v STORIOA
v DEVTERM v ANYBRDG
2843B935 2843FF6D
Explanation: Unknown hardware detected. Explanation: I/O processor detected a recoverable
system bus error.
Failing Item:
v AJDGP01 v IOP
v IOP v ANYBUS

28440A17 28441306
Explanation: A permanent I/O processor failure Explanation: I/O processor card or Licensed Internal
occurred. Code error.
Failing Item: Response: A microprocessor exception occurred on the
v IOP I/O processor.
v MA_BRDG Failing Item:
v AJDGP01 v AJDGP01
v AJDG301 v IOP
v FI01104
28440A22 v BACKPLN
error. 28441307
Failing Item: Explanation: I/O processor resource not available.
v AJDG301 v AJDGP01
v IOP v AJDG301
v MA_BRDG
28441310
2844102E
Failing Item: faster than the errors are being reported to the system.
v FI01105

28441317 • 28443021

28443001
them.
28441317
Failing Item:
the IOP. If the Failing Item indicates SVCDOCS, then v IOP
selection.
Failing Item:
v SVCDOCS v FI01140
v FI01141
28442200 v FI01106

error. 28443006
Failing Item: Explanation: System bus error.

v IOP
28442201 v ANYBUS
Explanation: Removable media error during IPL. v FI01101
Failing Item:
28443020
v USER
Explanation: Removable media error during IPL. Failing Item:

v IOPIP17
Failing Item:
v USER
v FI00022
v FI01107
v FI01105
v STORIOA
28443000
28443021
occurred. Explanation: I/O processor detected a SCSI bus
Failing Item:
v FI01101
v IOP Failing Item:
v MA_BRDG v IOPIP17
v USER
v FI01107
v STORIOA

28443022 • 28443103
v AJDGP01
28443022
v AJDG301
v IOACNFG
v FI01104
v IOPIP17
v USER error.
v FI01107
v STORIOA
Failing Item:
v IOPIP13
28443023
v FI01107
v STORIOA
v FI01140
v DEVBPLN
Failing Item:
v IOPIP17 28443101
v USER
v FI01107 error.
v STORIOA
Failing Item:
28443080
v IOPIP13
v FI01107
error.
v STORIOA
Failing Item:
v FI01140
v AJDGP01
v DEVBPLN
28443081
28443102
required.
error.
28443084
Failing Item:
Code error. v IOPIP13
v FI01107
I/O processor. v STORIOA
v FI01140
Failing Item:
v DEVBPLN
v AJDGP01
v IOP
28443103
v FI01104
v MA_BRDG Explanation: I/O processor card detected interface
error.
Explanation: I/O processor resource not available. Failing Item:

v IOPIP13
allocate resources on the I/O processor card. v FI01107
v STORIOA
Failing Item:

28443109 • 28443143

v SVCDOCS
28443109
command.
v BACKPLN v SVCDOCS
v FI01106
28443136
v IOPIP16 v FI01105
v FI01105
v STORIOA 28443140
v BACKPLN now operational.
v FI01106 Response: This reference code and the 3120 reference
28443120 since SCSI bus 0 is now operational.

not operational. 28443141
Response: A device was added to SCSI bus 0 of the Explanation: I/O Processor detected that the bus is
I/O Adapter and caused the bus to become not now operational.
Failing Item: code that occurred before it require no service action,
v SVCDOCS
28443142
28443121
now operational.
not operational.
Failing Item:
28443143
v SVCDOCS
now operational.
28443122

28443150 • 28443600
28443150 28443250
Explanation: I/O processor detected a SCSI bus Explanation: Disk unit requires initialization before
configuration error. use.
Response: Internal and external SCSI cables are Response: Perform a D-IPL and work on errors found
connected to SCSI bus 0 at the same time. Correct the in the log.
Failing Item:
v SVCDOCS
28443300
28443151
Failing Item:
v IOPIP01
v MEDIA
SCSI bus 1 configuration. v FI00121
v FI01141
Failing Item:
v SVCDOCS
28443400
Explanation: A tape/CD or disk device reported a Response: NOTE: If external devices are attached
failure. check EXTSCSI and DEVTERM first.

v FI01105 v FI02112
v STORIOA v STORIOA
v IOP v FI01106
v MEDIA v DEVTERM
v FI01140
28443203
28443401
Explanation: Device backplane problem.
Failing Item:
v DEVBPLN
28443205
28443501
error.
Failing Item:
Failing Item:
v AJDGP01
v FI01105
v IOP
28443215
28443600
Response: Disk unit data may need to be reloaded, required.
Failing Item:
v FI01105

28443601 • 28446602
28443601 28446081
required. error.
Failing Item:
28446070 v AJDGP01
occurred.
v IOP Explanation: I/O processor Licensed Internal Code
error.
error. v IOP
Failing Item:
v AJDGP01 28446083
28446072 error.
error. v AJDGP01
Failing Item: v IOP
v AJDGP01
v IOP 28446085
28446073 error.
Explanation: IPL device not ready. Failing Item:
v MEDIA v IOP
v FI01105 v MA_BRDG
v USER
28446200
28446075 Explanation: A permanent IOA hardware error
occurred.
Failing Item:
Failing Item:
v FCIOA
v AJDGP01
v OPT_CLN
28446076
28446201
Failing Item:
Failing Item:
v MEDIA
v AJDGP01
v AJDGP01
v FI01105
28446602
error occurred.
Failing Item:
v AJDGP01

28448000 • 28448132
28448000 28448010
shown.
v CACHE v CACHE
v STORIOA
28448002
occurred.
shown.
Failing Item:
v CACHE Exchange the FRUs one at a time in the order shown.
v STORIOA
Failing Item:
v CACHE
28448004
v STORIOA
28448100
Failing Item:
v FI01141 error.
v STORIOA
Failing Item:
v AJDGP01
28448005
v IOP
error occurred.
28448130
error.
shown.
Failing Item:
v STORIOA information only.
v CACHE
28448131
28448007
Explanation: A recoverable cache adapter card error error.
occurred.
Response: DO NOT replace both FRUs at the same is required. This reference code is logged for
time. Exchange the FRUs one at a time in the order information only.
shown.
v CACHE Explanation: IOA detected recoverable device bus
v STORIOA error.

28448133 • 28448300

28448155
information only.
occurred.
28448133
Failing Item:
error. v AJDGP01
v STORIOA
28448140 occurred.
error. v AJDGP01
Response: No action is required. This reference code v STORIOA
28448157
28448141
Response: No action is required. This reference code this SRC. If the Failing Item indicates I/O adapter, then
is logged for information only. replace the I/O adapter. If the Failing Item indicates
28448145
occurred.
Failing Item: the IOP. Other resources attached to the IOP may then
v STORIOA need to be Varied On.
28448146 RESET(*YES) command to reset the IOP and Vary On
attached resources.
Failing Item:
v FI01105
28448200
28448150
occurred.
Failing Item:
v STORIOA v IOP
v ANYBRDG
28448300
28448151
Explanation: I/O processor Licensed Internal Code Code error.
error.
Failing Item: I/O processor.
v STORIOA v STORIOA
v IOP
v AJDGP01

28448301 • 28449021
28448301 28449009
Explanation: Not valid condition in I/O Processor Explanation: Call your next level of support for
Licensed Internal Code. assistance.
Response: The Licensed Internal Code found a Failing Item:
condition that should not have occurred. v SVCDOCS
Failing Item:
v FI01101 28449010
v AJDGP01 Explanation: Cache data associated with attached
v IOP devices cannot be found.
Failing Item:
28448400 v IOPIP31
error. 28449011
v AJDGP01 those attached.
Failing Item:
28449000 v IOPIP32
v FI01105 Explanation: IOP requires a cache adapter card but
v STORIOA cannot find it.
28449001 broken.
Explanation: I/O processor card detected device Failing Item:

v IOPIP33
28449013
28449002 Explanation: The IOP and attached cache adapter card
are not compatible.
Failing Item:
Failing Item:
v IOPIP19
v IOPIP16
v FI01105
28449020
v STORIOA
v FI01140 Explanation: Array not functional due to present
v BACKPLN
v IOPIP20
28449008
28449021
expected by devices. Explanation: Array not functional due to present
Failing Item:
v IOPIP20

28449022 • 28449050
28449022 28449029
Explanation: Array not functional due to present Explanation: Incorrect hardware configuration change
hardware configuration. has been detected.
Failing Item: Response: Contact your next level of support.
v SVCDOCS
28449023
Explanation: Array not functional due to present 2844902F
Failing Item: entry.
v IOPIP22 Response: This entry contains additional array
28449024 contains more than 10 members. Use the 90xx entry
Explanation: Array not functional due to present the starting point for this problem.
v IOPIP22
28449025
Failing Item:
Explanation: Disk unit is not supported at its physical v IOPIP21
location.
v IOPIP21
28449026
Explanation: Array not functional due to present unit was used to automatically rebuild the array. Look
hardware configuration. for other reference codes and take action on them.
Failing Item:
v IOPIP22 28449040
28449027 Response: No action required. Protection will be
Explanation: Array not functional due to present automatically restarted.
v IOPIP34 Explanation: Background array parity check detected

28449028 Response: Call your next level of support to report
the problem.
has been detected. Failing Item:
Response: Reduce the number of arrays on IOP. Either v AJDGP01

supports arrays, or stop an array on this IOP. 28449050
Failing Item: Explanation: Required cache data cannot be located
v SVCDOCS for a disk unit.
Failing Item:
v IOPIP30

28449051 • 2844B3B1
28449051 28449082
failed device.
Failing Item:
v FI01105
v FI01140
v FI01106
Failing Item:
v IOPIP27
28449090

last known status.
v IOPIP28
level of support.
28449053
Failing Item:
previous problems.
problem.
Failing Item:
v SVCDOCS
level of support.
Failing Item:
28449054
v SVCDOCS
previous problems.
28449092
occurred.
Failing Item:
v FI01105
v STORIOA

2844B3B2 • 2844B935
v IOP
2844B3B2
2844B3E0
occurred.
Failing Item:
v IOP Failing Item:
v IOP
2844B3B3 v MA_BRDG

occurred. 2844B3E1

v IOP Failing Item:
v IOP
2844B3B4 v MA_BRDG
occurred. 2844B410
v IOP occurred.
Failing Item:
2844B3B5 v STORIOA
occurred. 2844B411
v IOP occurred.
Failing Item:
2844B3B6 v STORIOA
occurred. 2844B412
v IOP occurred.
Failing Item:
2844B3B7 v IOPIP16
occurred. v FI01140
v IOP v DEVTERM
2844B3B8 2844B935

v MA_BRDG v FI01101
v IOP v AJDGP01
v IOP
2844B3B9 v MA_BRDG

occurred.
Failing Item:

2844BE00 • 28473080
Failing Item:
2844BE00
v STORIOA
v ANYBRDG
Failing Item:
v AJDGP01 2844FF6D
v IOP
v FI01104 system bus error.
v MA_BRDG
Failing Item:
v IOP
2844FF3D
v ANYBUS

Failing Item:
28470A17
v FCIOA
v IOP
occurred.
v MA_BRDG
Failing Item:
v OPT_CLN
v IOP
v MA_BRDG
28473001
v AJDGP01
v AJDG301
28470A22
Failing Item:
error.
v IOP
Failing Item:
v AJDGP01
v AJDGP01
v AJDG301
28473002
v IOP
v MA_BRDG
Failing Item:
28471307 v FCPORT
v FCDEV
v FCIOA
Failing Item:
v FCINTF
v AJDGP01
v OPT_CLN
v AJDG301
28473006
28471310
Failing Item:
v IOP
Check other errors reported to the system and correct v ANYBUS
them. v FCIOA
v OPT_CLN
28473000
Explanation: A permanent I/O processor failure 28473080
occurred.

28473081 • 28476072
Explanation: I/O processor Licensed Internal Code v OPT_CLN

error.
v AJDGP01 Explanation: I/O processor detected a port failure.
Failing Item:
28473081
v FCPORT
Explanation: System log entry only, no service action v FCIOA
required.
v FCDEV
v OPT_CLN
28473084
Explanation: I/O processor card or Licensed Internal 28473200
Code error.
I/O processor. Failing Item:
v FCDEV
Failing Item:
v FCIOA
v AJDGP01
v IOP
v IOP
v OPT_CLN
v FCIOA
v MA_BRDG
28473501
v OPT_CLN
error.
28473087
Failing Item:
v AJDGP01
v IOP
Failing Item:
28476070
v AJDGP01
v AJDG301
occurred.
v FCIOA
Failing Item:
v OPT_CLN
v IOP
28473100
28476071
error. Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
Failing Item:
v FCINTF
v AJDGP01
v ANYFC
v FCIOA
28476072
v OPT_CLN
error.
28473109
Failing Item:
command. v AJDGP01
v IOP
Failing Item:
v FCDEV
v FCINTF
v FCIOA

28476075 • 28478200
v OPT_CLN
28476075
28476201
Failing Item:
v AJDGP01
Failing Item:
v AJDGP01
28476076
28478100
Failing Item:
v AJDG301 error.
v AJDGP01
Failing Item:
v FCDEV
v AJDGP01
v IOP
28476081
error.
v AJDGP01
Failing Item:
v IOP
v FCIOA
v ANYBRDG
28476082
v OPT_CLN
error.
28478155
Failing Item:
v AJDGP01 occurred.
v IOP
Failing Item:
v AJDGP01
28476083
v FCIOA
Explanation: I/O processor Licensed Internal Code v OPT_CLN
error.
v AJDGP01
v IOP occurred.
Failing Item:
28476085
v AJDGP01
Explanation: I/O processor Licensed Internal Code v FCIOA
error.
v OPT_CLN
Failing Item:
v AJDGP01 28478200
v IOP
v MA_BRDG error.
Failing Item:
28476200
v AJDGP01
Explanation: A permanent IOA hardware error v IOP
occurred.
Failing Item:
v FCIOA

28478300 • 2847B935
28478300 2847B3B5
Explanation: I/O processor card or Licensed Internal Explanation: A permanent I/O processor failure
Code error. occurred.
I/O processor. v IOP
Failing Item:
v FCIOA 2847B3B6
v IOP Explanation: A permanent I/O processor failure
v AJDGP01 occurred.
v IOP
28478301
Explanation: Not valid condition in I/O Processor 2847B3B7
Response: The Licensed Internal Code found a occurred.
Failing Item:
Failing Item: v IOP
v FCIOA
v AJDGP01 2847B3B8
v IOP
v OPT_CLN
Failing Item:
v MA_BRDG
2847B3B1
v IOP
occurred.
2847B3E0
Failing Item:
v IOP
Failing Item:
2847B3B2 v IOP
v MA_BRDG
occurred.
2847B3E1
Failing Item:
v IOP Explanation: I/O processor detected a fault condition.
Failing Item:
2847B3B3 v IOP
Explanation: A permanent I/O processor failure v MA_BRDG
occurred.
Failing Item: 2847B935
v IOP Explanation: Unknown hardware detected.
Failing Item:
2847B3B4 v FCIOA
Explanation: A permanent I/O processor failure v AJDGP01
occurred. v IOP
v IOP v OPT_CLN

2847BE00 • 284B1310
v IOP
2847BE00
v FCIOA
v MA_BRDG
v AJDGP01

2849B904 2849B931
failed.
Failing Item:
v AJDGP01 v FI00718
v FI00719 v AJDGP01
v MA_BRDG
2849B930
failed.
Failing Item:
Failing Item:
v AJDGP01
v FI00719
v FI00718
v AJDGP01
v FI00719

284B0A17 284B1306
Explanation: A permanent I/O processor failure Explanation: I/O processor card or Licensed Internal
occurred. Code error.
Failing Item: Response: A microprocessor exception occurred on the
v IOP I/O processor.
v AJDGP01 v AJDGP01
v AJDG301 v IOP
v FI01104
284B0A22 v BACKPLN
error. 284B1307
Failing Item: Explanation: I/O processor resource not available.
v AJDG301 v AJDGP01
v IOP v AJDG301
v MA_BRDG
284B1310
284B102E
v FI01105 Check other errors reported to the system and correct
them.

284B1317 • 284B3021

284B1317
Failing Item:
v IOP
v AJDGP01
do NOT replace the IOP. This is a recoverable error. 284B3002
1. If the I/O Processor is not operable and disk units selection.
need to be Varied On. v IOPIP16
2. If disk units are not attached, perform the VRYCFG v FI01105
RESET(*YES) command to reset the IOP and Vary On v STORIOA
v SVCDOCS v FI01106
284B2200 284B3006
Explanation: I/O processor Licensed Internal Code Explanation: System bus error.
error.
Failing Item:
Failing Item: v IOP
v AJDGP01 v ANYBUS
v FI01101
284B2201
Explanation: Removable media error during IPL. 284B3020
Failing Item: Explanation: I/O processor detected a SCSI bus

v USER configuration error.
Failing Item:
284B2202 v IOPIP17
Explanation: Removable media error during IPL. v USER
v FI00022 v STORIOA
v FI01105
284B3021
284B3000 Explanation: I/O processor detected a SCSI bus
occurred. Response: Error occurred on SCSI bus 1.

v FI01101 v IOPIP17
v IOP v USER
v MA_BRDG v FI01107
v STORIOA
284B3001

284B3022 • 284B3103
v AJDGP01
284B3022
v AJDG301
v IOACNFG
v FI01104
v IOPIP17
v USER error.
v FI01107
v STORIOA
Failing Item:
v IOPIP13
284B3023
v FI01107
v STORIOA
v FI01140
v DEVBPLN
Failing Item:
v IOPIP17 284B3101
v USER
v FI01107 error.
v STORIOA
Failing Item:
284B3080
v IOPIP13
v FI01107
error.
v STORIOA
Failing Item:
v FI01140
v AJDGP01
v DEVBPLN
284B3081
284B3102
required.
error.
284B3084
Failing Item:
Code error. v IOPIP13
v FI01107
I/O processor. v STORIOA
v FI01140
Failing Item:
v DEVBPLN
v AJDGP01
v IOP
284B3103
v FI01104
error.
284B3087 Response: Error occurred on SCSI bus 3.

v IOPIP13
v STORIOA
Failing Item:

284B3109 • 284B3143

v SVCDOCS
284B3109
Explanation: I/O processor timed out a device 284B3123
command.
v BACKPLN v SVCDOCS
v FI01106
284B3136
284B3110 Explanation: The removable media device is assigned
v IOPIP16 v FI01105
v FI01105
v STORIOA 284B3140
v FI01106 Response: This reference code and the 3120 reference
284B3120 since SCSI bus 0 is now operational.

not operational. 284B3141
v SVCDOCS
284B3142
284B3121
now operational.
not operational.
Failing Item:
284B3143
v SVCDOCS
now operational.
284B3122

284B3150 • 284B3600
284B3150 284B3250
Explanation: I/O processor detected a SCSI bus Explanation: Disk unit requires initialization before
configuration error. use.
Response: Internal and external SCSI cables are Response: Perform a D-IPL and work on errors found
connected to SCSI bus 0 at the same time. Correct the in the log.
Failing Item:
v SVCDOCS
284B3300
284B3151
Failing Item:
v IOPIP01
v MEDIA
v FI01141
Failing Item:
v SVCDOCS
284B3400
284B3200 Explanation: I/O processor card detected device error.
Explanation: A tape/CD or disk device reported a Response: NOTE: If external devices are attached
failure. check EXTSCSI and DEVTERM first.

v FI01105 v FI02112
v STORIOA v STORIOA
v IOP v FI01106
v MEDIA v DEVTERM
v FI01140
284B3203
284B3401
Failing Item:
v DEVBPLN
284B3205
284B3501
error.
Failing Item:
Failing Item:
v AJDGP01
v FI01105
v IOP
284B3215
284B3600
Response: Disk unit data may need to be reloaded, required.
Failing Item:
v FI01105

284B3601 • 284B6602
284B3601 284B6081
required. error.
Failing Item:
284B6070 v AJDGP01
occurred.
v IOP Explanation: I/O processor Licensed Internal Code
error.
error. v IOP
Failing Item:
v AJDGP01 284B6083
284B6072 error.
error. v AJDGP01
Failing Item: v IOP
v AJDGP01
v IOP 284B6085
284B6073 error.
Explanation: IPL device not ready. Failing Item:
v MEDIA v IOP
v FI01105 v MA_BRDG
v USER
284B6200
284B6075 Explanation: A permanent IOA hardware error
occurred.
Failing Item:
Failing Item:
v FCIOA
v AJDGP01
v OPT_CLN
284B6076
284B6201
Failing Item:
Failing Item:
v MEDIA
v AJDGP01
v AJDGP01
v FI01105
284B6602
error occurred.
Failing Item:
v AJDGP01

284B8000 • 284B8132
284B8000 284B8010
shown.
v CACHE v CACHE
v STORIOA
284B8002
Explanation: A permanent cache adapter card failure 284B8011
occurred.
shown.
Failing Item:
v STORIOA
Failing Item:
v CACHE
284B8004
v STORIOA
284B8100
Failing Item:
v FI01141 error.
v STORIOA
Failing Item:
v AJDGP01
284B8005
v IOP
error occurred.
284B8130
error.
shown.
Failing Item:
v CACHE
284B8131
284B8007
occurred.
shown.
v STORIOA error.

284B8133 • 284B8300

284B8155
information only.
occurred.
284B8133
Failing Item:
error. v AJDGP01
v STORIOA
information only. 284B8156
284B8140 occurred.
error. v AJDGP01
284B8157
284B8141
284B8145
occurred.
284B8146 RESET(*YES) command to reset the IOP and Vary On
attached resources.
Failing Item:
v FI01105
284B8200
284B8150
occurred.
Failing Item:
v STORIOA v IOP
v ANYBRDG
284B8300
284B8151
error.
v STORIOA v STORIOA
v IOP
v AJDGP01

284B8301 • 284B9021
284B8301 284B9009
Failing Item:
v FI01101 284B9010
Failing Item:
284B8400 v IOPIP31
error. 284B9011
Failing Item:
284B9000 v IOPIP32
284B9001 broken.

v IOPIP33
284B9013
284B9002 Explanation: The IOP and attached cache adapter card
are not compatible.
Failing Item:
Failing Item:
v IOPIP19
v IOPIP16
v FI01105
284B9020
v STORIOA
v BACKPLN
v IOPIP20
284B9008
284B9021
Failing Item:
v IOPIP20

284B9022 • 284B9050
284B9022 284B9029
v SVCDOCS
284B9023
Explanation: Array not functional due to present 284B902F
284B9024 contains more than 10 members. Use the 90xx entry
v IOPIP22
284B9025
Failing Item:
location.
v IOPIP21
284B9026
Failing Item:
v IOPIP22 284B9040
284B9027 Response: No action required. Protection will be

284B9028 Response: Call your next level of support to report
the problem.

supports arrays, or stop an array on this IOP. 284B9050
Failing Item:
v IOPIP30

284B9051 • 284BB3B1
284B9051 284B9082
failed device.
Failing Item:
v FI01105
v FI01140
v FI01106
Failing Item:
v IOPIP27
284B9090
284B9052 Explanation: Disk unit has been modified after the

last known status.
v IOPIP28
level of support.
284B9053
Failing Item:
previous problems.
Response: Take action on other IOP reference codes 284B9091
problem.
Failing Item:
v SVCDOCS
level of support.
Failing Item:
284B9054
v SVCDOCS
previous problems.
284B9092
Failing Item: 284BB3B1
occurred.
Failing Item:
v FI01105
v STORIOA

284BB3B2 • 284BB935
v IOP
284BB3B2
284BB3E0
occurred.
Failing Item:
v IOP Failing Item:
v IOP
284BB3B3 v MA_BRDG

occurred. 284BB3E1

v IOP Failing Item:
v IOP
284BB3B4 v MA_BRDG
occurred. 284BB410
v IOP occurred.
Failing Item:
284BB3B5 v STORIOA
occurred. 284BB411
v IOP occurred.
Failing Item:
284BB3B6 v STORIOA
occurred. 284BB412
v IOP occurred.
Failing Item:
284BB3B7 v IOPIP16
occurred. v FI01140
v IOP v DEVTERM
284BB3B8 284BB935

v MA_BRDG v FI01101
v IOP v AJDGP01
v IOP
284BB3B9 v MA_BRDG

occurred.
Failing Item:

284BBE00 • 28753109
Failing Item:
284BBE00
v STORIOA
v ANYBRDG
Failing Item:
v AJDGP01 284BFF6D
v IOP
v MA_BRDG
Failing Item:
v IOP
284BFF3D
v ANYBUS

28751511
2.
Problem determination: This SRC can be the result of
supply 1.
a loss of utility power, battery back up or UPS power
Failing Item: to the I/O storage unit. The unit and power supply
v DISKPWR that detected the problem are in the FRU list of the
serviceable event. Before starting a repair action for this
v DEVBPLN
problem verify that utility power, BBU or UPS to the
v SASEXP unit was not interrupted at the time the SRC was
logged. If there was an interruption to power at about
28751515 the same time then no service is required and this
problem can be closed.
1. Failing Item:
v DISKPWR
a loss of utility power, battery back up or UPS power v DEVBPLN
to the I/O storage unit. The unit and power supply v SASEXP
that detected the problem are in the FRU list of the
28753002
unit was not interrupted at the time the SRC was Explanation: Addressed device backplane failed to
logged. If there was an interruption to power at about respond to selection.
the same time then no service is required and this
Problem determination: If there are multiple xxxx3002
reference codes logged from the same disk expansion
Failing Item: unit at about the same time suspect an input power
v DISKPWR failure. Verify that input power to the expansion unit
power supplies was active at the time of the error. If
v DEVBPLN
input power to the expansion unit failed the expansion
v SASEXP unit was not able to log a reference code for the input
power failure. Restore power to the expansion unit and
28751521 close the xxxx3002 problems. Otherwise work the
xxxx3002 reference codes.
supply 2. Failing Item:
v SASEXP
Failing Item:
v SASCABL
v DISKPWR
v STORIOA
v DEVBPLN
v DEVBPLN
v SASEXP
28753109
28751525

28757614 • 28761525
Explanation: I/O adapter timed out a device Failing Item:

backplane command. v DISKFAN
Failing Item:
v SASEXP 28757644
v SASCABL Explanation: A fatal error occurred on fan 4.
v STORIOA
Failing Item:
v DEVBPLN
v DISKFAN
28757614
28758404
Failing Item: required.
v DISKFAN
2875FFF4
28757624 Explanation: Device backplane problem.
Explanation: A fatal error occurred on fan 2. Failing Item:
v DISKFAN v SASCABL
v STORIOA
28757634 v DEVBPLN

28761511 28761521
Explanation: A non-fatal error occurred on power Explanation: A non-fatal error occurred on power
supply 1. supply 2.
v DISKPWR v DISKPWR
v DEVBPLN v DEVBPLN
v SASEXP v SASEXP
28761515 28761525
Explanation: A fatal error occurred on power supply Explanation: A fatal error occurred on power supply
1. 2.
Problem determination: This SRC can be the result of Problem determination: This SRC can be the result of
a loss of utility power, battery back up or UPS power a loss of utility power, battery back up or UPS power
to the I/O storage unit. The unit and power supply to the I/O storage unit. The unit and power supply
that detected the problem are in the FRU list of the that detected the problem are in the FRU list of the
serviceable event. Before starting a repair action for this serviceable event. Before starting a repair action for this
problem verify that utility power, BBU or UPS to the problem verify that utility power, BBU or UPS to the
unit was not interrupted at the time the SRC was unit was not interrupted at the time the SRC was
logged. If there was an interruption to power at about logged. If there was an interruption to power at about
the same time then no service is required and this the same time then no service is required and this
problem can be closed. problem can be closed.
v DISKPWR v DISKPWR
v DEVBPLN v DEVBPLN
v SASEXP v SASEXP

28763002 • 28901310
v DISKFAN
28763002
28767624
respond to selection.
reference codes logged from the same disk expansion Failing Item:
unit at about the same time suspect an input power v DISKFAN
failure. Verify that input power to the expansion unit
input power to the expansion unit failed the expansion 28767634
unit was not able to log a reference code for the input
close the xxxx3002 problems. Otherwise work the Failing Item:
xxxx3002 reference codes. v DISKFAN
Failing Item:
v SASEXP 28767644
v SASCABL Explanation: A fatal error occurred on fan 4.
v STORIOA
Failing Item:
v DEVBPLN
v DISKFAN
28763109
28768404
backplane command.
required.
Failing Item:
v SASEXP 2876FFF4
v SASCABL
v STORIOA
Failing Item:
v DEVBPLN
v SASEXP
v SASCABL
28767614
v STORIOA
v DEVBPLN
Failing Item:

v MA_BRDG
28900A17
28901307
occurred.
Failing Item:
v IOP Failing Item:
v MA_BRDG v AJDGP01
v AJDG301 v AJDG301
v AJDGP01
28901310
28900A22 Explanation: I/O adapter resource not available.
Explanation: Adapter card storage error. Response: The INS processor error log is being filled
Failing Item:
v AJDGP01 them.
v AJDG301
Failing Item:
v IOP

28903000 • 28906201
v IOP
28906070
v AJDGP01

v IOP
Failing Item:
28906071
v IOP
v AJDGP01
failed.
Failing Item:
28903001
v AJDGP01
failed.
28906072
Failing Item:
v IOP
failed.
v AJDGP01
Failing Item:
v AJDGP01
28903006
v IOP
v IOP
v ANYBUS
Failing Item:
v AJDGP01
28903080
28906083
failed.
Failing Item:
failed.
v AJDGP01
Failing Item:
v AJDGP01
28903081
v IOP
28906085
28903084
Explanation: An I/O adapter failure occurred. failed.
v AJDGP01 v AJDGP01
v IOP v IOP
v IOA v MA_BRDG
v MA_BRDG
28906201
28903087
Explanation: I/O adapter resource not available. occurred.

v AJDGP01 v IOP
v AJDG301 v AJDGP01
v NTUSER
v IOA

28906202 • 28906531
v AJDG301
28906202
v IOP
error.
28906226
Failing Item:
v AJDGP01
v IOP Failing Item:
v AJDG301
28906210 v AS4NTDD

error. 28906227
Failing Item: Explanation: A HostLAN error was detected.

v NTUSER
28906221 v AJDGP01
Failing Item:
28906228
v AJDG301
Explanation: Windows initiated a warm boot.
occurred. v IOP
Failing Item:
v AJDGP01 28906501
v IOP Explanation: A Windows fatal error occurred.
Failing Item:
28906223 v IOP
occurred.
v AJDGP01
Failing Item:
v AJDGP01
28906224
v IOP
occurred.
28906530
Failing Item:
v DISKIMG
v IOP v NTVSCSI
v MEMORY v NTOPSYS
28906225 28906531
v AJDGP01 v AS4NTDD

28906532 • 28906540
v NTOPSYS
2890653A
v AJDGP01

v NTOPSYS
v AJDGP01
Failing Item:
v AS4NTDD
v NTOPSYS
v AJDGP01
2890653B
v AS4NTDD

v NTUSER
v NTOPSYS
Failing Item:
v AS4NTDD
v NTUSER
v NTOPSYS
2890653C
v AS4NTDD

v AS4NTDD
v AJDGP01
Failing Item:
v NTOPSYS
v AS4NTDD
v AJDGP01
2890653D
v NTOPSYS

v NTUSER
v NTDEVDR
Failing Item:
v AJDGP01
v NTUSER
v NTDEVDR
2890653F
v AJDGP01

v NTDEVDR
v NTOPSYS
Failing Item:
v AJDG301
v NTVSCSI
v NTOPSYS
28906540
28906539
Failing Item:
v NTVSCSI
Failing Item:
v AJDGP01
v NTVSCSI
v AJDG301
v AS4NTDD
v NTOPSYS
v AJDGP01

28906541 • 2890B3B7
28906541 28908301
Explanation: A permanent I/O processor failure Explanation: An I/O adapter failure occurred.
occurred.
Failing Item:
v IOP v IOP
v AJDGP01
2890B3B1
28906542
Explanation: Licensed Internal Code error detected. occurred.
v AJDG301 v IOP
v AJDGP01
2890B3B2
Explanation: A Windows fatal error occurred. occurred.

v NTOPSYS v IOP
v NTVSCSI
2890B3B3
occurred.
Failing Item:
Failing Item:
v IOP
v DISKIMG
v IOP
2890B3B4
v AJDGP01
occurred.
289065B0
Failing Item:
v IOP
Failing Item:
v NTLANDD
2890B3B5
v NTOPSYS
occurred.
289065B1
Failing Item:
v IOP
Failing Item:
v NTLANDD 2890B3B6
v NTOPSYS
v AJDG301 occurred.
Failing Item:
289065B2
v IOP
v NTDEVDR Explanation: A permanent I/O processor failure
v NTOPSYS occurred.

2890B3B8 • 2890B4BE
v IOP
2890B4B3
2890B3B8
Failing Item:
Explanation: Multi-adapter bridge error detected.
v IOA
Failing Item:
v MA_BRDG
2890B4B4
v IOP

v IOP
occurred. v IOA
v MEMORY
Failing Item:
v IOP
2890B4B5
2890B3E0 Explanation: An I/O adapter failure occurred.

v AJDGP01
Failing Item:
v IOP
v IOP
v MA_BRDG
2890B4B8
2890B3E1 Explanation: Adapter card storage error.
Explanation: An I/O adapter failure occurred. Failing Item:

v MEMORY
Failing Item:
v IOP
v IOP
v MA_BRDG
2890B4B9
Explanation: I/O adapter hardware error detected. Failing Item:

v IOP
Failing Item:
v IOP
2890B4BC
2890B4B1 Explanation: I/O adapter error; logged only.

v IOP
Failing Item:
v IOA
v IOP
v MEMORY
2890B4BE
2890B4B2 Explanation: Adapter card storage error.
Explanation: Incompatible hardware detected. Failing Item:

v MEMORY
Failing Item:
v IOP
v IOP

2890B904 • 28923000
v AJDGP01
2890B904
v IOP
v IOA
occurred.
Failing Item:
2890B961
v AJDGP01
Explanation: An error was detected on one of the
v IOP
attached adapter cards.
Failing Item:
2890B935
v IOA
v IOP
v IOA
v AJDGP01 2890BE00
v IOP
v MA_BRDG
Failing Item:
v AJDGP01
2890B960
v IOP
v IOA
error.
v MA_BRDG
Failing Item:

28920A17
Response: The INS processor error log is being filled
occurred.
Failing Item: them.
v IOP Failing Item:
v MA_BRDG v IOP
v AJDG301 v AJDGP01
v AJDGP01
28921317
28920A22
Failing Item: this SRC. If the Failing Item indicates to replace
v AJDGP01 hardware, then replace hardware. If the Failing Item
indicates SVCDOCS, then do NOT replace hardware.
v AJDG301
This is a recoverable error. If the resource is not
v IOP operable, use Hardware Service Manager to re-IPL the
v MA_BRDG resource. Perform the VRYCFG command to Vary On
the NWSD.
Explanation: I/O adapter resource not available. v SVCDOCS
Failing Item:
28923000
v AJDGP01
v AJDG301 Explanation: An I/O adapter failure occurred.
Failing Item:
28921310 v IOP

28923001 • 28926202
v AJDGP01
28926071
28923001
failed.
Failing Item:
failed.
v AJDGP01
Failing Item:
v IOP
28926072
v AJDGP01
failed.
28923006
Failing Item:
v AJDGP01
Failing Item: v IOP
v IOP
v ANYBUS 28926075
28923080
Failing Item:
v AJDGP01
failed.
Failing Item:
28926083
v AJDGP01
failed.
28923081
Failing Item:
v AJDGP01
v IOP
28923084
Explanation: An I/O adapter failure occurred. 28926085
Failing Item: Explanation: I/O adapter Licensed Internal Code
v AJDGP01 failed.
v IOP Failing Item:
v IOA v AJDGP01
v MA_BRDG v IOP
v MA_BRDG
28923087
Explanation: I/O adapter resource not available. 28926201

v AJDGP01 occurred.
v NTUSER v IOP
v IOA v AJDGP01
28926070 28926202
Explanation: An I/O adapter failure occurred. Explanation: I/O processor Licensed Internal Code
error.
Failing Item:
v IOP Failing Item:
v AJDGP01
v IOP

28926204 • 28926531
v IOP
28926204
Explanation: I/O adapter failure due to a thermal
28926226
condition.
Failing Item:
v IOP Failing Item:
v AJDG301
28926210 v AS4NTDD

error. 28926227
Failing Item: Explanation: A HostLAN error was detected.

v NTUSER
28926221 v AJDGP01
Failing Item:
28926228
v AJDG301
occurred. v IOP
Failing Item:
v AJDGP01 28926501
Failing Item:
28926223 v IOP
occurred.
v AJDGP01
Failing Item:
v AJDGP01
28926224
v IOP
occurred.
28926530
Failing Item:
v DISKIMG
v IOP v NTVSCSI
v MEMORY v NTOPSYS
28926225 28926531
v AJDGP01 v AS4NTDD
v AJDG301 v NTOPSYS

28926532 • 28926540
v AJDGP01
2892653A
28926532
Failing Item:
v NTOPSYS
Failing Item:
v AJDGP01
v NTOPSYS
v AS4NTDD
v AJDGP01
v AS4NTDD
2892653B
28926533
Failing Item:
v NTUSER
Failing Item:
v NTOPSYS
v NTUSER
v AS4NTDD
v NTOPSYS
v AS4NTDD
2892653C
28926534
Failing Item:
v AS4NTDD
Failing Item:
v AJDGP01
v AS4NTDD
v NTOPSYS
v AJDGP01
v NTOPSYS
2892653D
28926535
Failing Item:
v NTUSER
Failing Item:
v NTDEVDR
v NTUSER
v AJDGP01
v NTDEVDR
v AJDGP01
2892653F
28926538
Failing Item:
v NTDEVDR
Failing Item:
v NTOPSYS
v NTVSCSI
v AJDG301
v NTOPSYS
28926540
28926539
Failing Item:
Failing Item:
v NTVSCSI
v NTVSCSI
v AJDGP01
v AS4NTDD
v AJDG301
v NTOPSYS
v AJDGP01

28926541 • 2892B3B7
28926541 28928301
Explanation: A permanent I/O processor failure Explanation: An I/O adapter failure occurred.
occurred.
Failing Item:
v IOP v IOP
v AJDGP01
2892B3B1
28926542
Explanation: Licensed Internal Code error detected. occurred.
v AJDG301 v IOP
v AJDGP01
2892B3B2
Explanation: A Windows fatal error occurred. occurred.

v NTOPSYS v IOP
v NTVSCSI
2892B3B3
occurred.
Failing Item:
Failing Item:
v IOP
v DISKIMG
v IOP
2892B3B4
v AJDGP01
occurred.
289265B0
Failing Item:
v IOP
Failing Item:
v NTLANDD
2892B3B5
v NTOPSYS
occurred.
289265B1
Failing Item:
v IOP
Failing Item:
v NTLANDD 2892B3B6
v NTOPSYS
v AJDG301 occurred.
Failing Item:
289265B2
v IOP
v NTDEVDR Explanation: A permanent I/O processor failure
v NTOPSYS occurred.

2892B3B8 • 2892B4BE
v IOP
2892B4B3
2892B3B8
Failing Item:
Explanation: Multi-adapter bridge error detected.
v IOA
Failing Item:
v MA_BRDG
2892B4B4
v IOP

v IOP
occurred. v IOA
v MEMORY
Failing Item:
v IOP
2892B4B5
2892B3E0 Explanation: An I/O adapter failure occurred.

v AJDGP01
Failing Item:
v IOP
v IOP
v MA_BRDG
2892B4B8
2892B3E1 Explanation: Adapter card storage error.
Explanation: An I/O adapter failure occurred. Failing Item:

v MEMORY
Failing Item:
v IOP
v IOP
v MA_BRDG
2892B4B9

v IOP
Failing Item:
v IOP
2892B4BC
2892B4B1 Explanation: I/O adapter error; logged only.

v IOP
Failing Item:
v IOA
v IOP
v MEMORY
2892B4BE
2892B4B2 Explanation: Adapter card storage error.

v MEMORY
Failing Item:
v IOP
v IOP

2892B904 • 28A63002
v AJDGP01
2892B904
v IOP
v IOA
occurred.
Failing Item:
2892B961
v AJDGP01
Explanation: An error was detected on one of the
v IOP
attached adapter cards.
Failing Item:
2892B935
v IOA
v IOP
v IOA
v AJDGP01 2892BE00
v IOP
v MA_BRDG
Failing Item:
v AJDGP01
2892B960
v IOP
v IOA
error.
v MA_BRDG
Failing Item:

28A61511
supply 2.
Failing Item:
supply 1.
v DISKPWR
Failing Item:
v DEVBPLN
v DISKPWR
v SASEXP
v DEVBPLN
v SASEXP
28A61525
28A61515
2.
1.
Problem determination: This SRC can be the result of to the I/O storage unit. The unit and power supply
a loss of utility power, battery back up or UPS power that detected the problem are in the FRU list of the
to the I/O storage unit. The unit and power supply serviceable event. Before starting a repair action for this
that detected the problem are in the FRU list of the problem verify that utility power, BBU or UPS to the
serviceable event. Before starting a repair action for this unit was not interrupted at the time the SRC was
problem verify that utility power, BBU or UPS to the logged. If there was an interruption to power at about
unit was not interrupted at the time the SRC was the same time then no service is required and this
logged. If there was an interruption to power at about problem can be closed.
Failing Item:
v DISKPWR
Failing Item:
v DEVBPLN
v DISKPWR
v SASEXP
v DEVBPLN
v SASEXP
28A63002
28A61521

28A63109 • 28A6FFF4

28A68404
required.
unit at about the same time suspect an input power
failure. Verify that input power to the expansion unit 28A6FFF4
unit was not able to log a reference code for the input Failing Item:
power failure. Restore power to the expansion unit and v SASEXP
close the xxxx3002 problems. Otherwise work the
xxxx3002 reference codes. v SASCABL
v STORIOA
Failing Item:
v DEVBPLN
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
28A63109
backplane command.
Failing Item:
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
28A67614
Failing Item:
v DISKFAN
28A67624
Failing Item:
v DISKFAN
28A67634
Failing Item:
v DISKFAN
28A67644
Failing Item:
v DISKFAN

28A81511 • 28A87634

v DEVBPLN
28A81511
v SASEXP
supply 1.
28A83002
Failing Item:
v DISKPWR
v DEVBPLN
v SASEXP
28A81515 failure. Verify that input power to the expansion unit
1.
Problem determination: This SRC can be the result of power failure. Restore power to the expansion unit and
a loss of utility power, battery back up or UPS power close the xxxx3002 problems. Otherwise work the
to the I/O storage unit. The unit and power supply xxxx3002 reference codes.
Failing Item:
problem verify that utility power, BBU or UPS to the v SASEXP
unit was not interrupted at the time the SRC was v SASCABL
logged. If there was an interruption to power at about v STORIOA
v DEVBPLN
Failing Item:
28A83109
v DISKPWR
v DEVBPLN
backplane command.
v SASEXP
Failing Item:
v SASEXP
28A81521
v SASCABL
v STORIOA
supply 2.
v DEVBPLN
Failing Item:
v DISKPWR
28A87614
v DEVBPLN
v SASEXP
Failing Item:
28A81525 v DISKFAN

2. 28A87624
Problem determination: This SRC can be the result of Explanation: A fatal error occurred on fan 2.
a loss of utility power, battery back up or UPS power Failing Item:
to the I/O storage unit. The unit and power supply
that detected the problem are in the FRU list of the v DISKFAN
problem verify that utility power, BBU or UPS to the 28A87634
unit was not interrupted at the time the SRC was
logged. If there was an interruption to power at about Explanation: A fatal error occurred on fan 3.
the same time then no service is required and this Failing Item:
v DISKFAN
Failing Item:
v DISKPWR

28A87644 • 28B97624
28A87644 28A8FFF4
Explanation: A fatal error occurred on fan 4. Explanation: Device backplane problem.
v DISKFAN v SASEXP
v SASCABL
28A88404 v STORIOA
Explanation: System log entry only, no service action v DEVBPLN
required.

28B91511 28B93002
Explanation: A non-fatal error occurred on power Explanation: Addressed device backplane failed to
supply 1. respond to selection.
v DISKPWR v DEVBPLN
v DISKFAN v STORIOA
v FI01106 v FI01140
v DEVBPLN v FI01106
28B91515 28B93109
Explanation: A fatal error occurred on power supply Explanation: I/O adapter timed out a device
1. backplane command.
v DISKPWR v DEVBPLN
v DISKFAN v STORIOA
v FI01106 v FI01140
v DEVBPLN v FI01106
28B91521 28B97611
Explanation: A non-fatal error occurred on power Explanation: A fatal error occurred on redundant fan
supply 2. 1.
v DISKPWR v DISKFAN
v DISKFAN
v FI01106 28B97614
v DEVBPLN Explanation: A fatal error occurred on fan 1.
Failing Item:
28B91525
v DISKFAN
2.
28B97621
Failing Item:
v DISKPWR 2.
v DISKFAN
Failing Item:
v FI01106
v DISKFAN
v DEVBPLN
28B97624

28B97631 • 28CB7611
Explanation: A fatal error occurred on fan 2. Explanation: Removable media power fault.
v DISKFAN v DEVBPLN
28B97631 28B98404
Explanation: A fatal error occurred on redundant fan Explanation: System log entry only, no service action
3. required.
Failing Item:
v DISKFAN 28B9FFF4
Explanation: A fatal error occurred on fan 3. v DEVBPLN
v DISKFAN v FI01140
v FI01106
28B98401
(28CB) Reference codes

28CB1511
2.
Failing Item:
supply 1.
v DISKPWR
Failing Item:
v DISKFAN
v DISKPWR
v FI01106
v DISKFAN
v DEVBPLN
v FI01106
v DEVBPLN
28CB3002
28CB1515
Failing Item:
1.
v DEVBPLN
Failing Item:
v STORIOA
v DISKPWR
v FI01140
v DISKFAN
v FI01106
v FI01106
v DEVBPLN
28CB3109
28CB1521
backplane command.
Failing Item:
supply 2.
v DEVBPLN
Failing Item:
v STORIOA
v DISKPWR
v FI01140
v DISKFAN
v FI01106
v FI01106
v DEVBPLN
28CB7611
28CB1525
1.

28CB7614 • 28CC3002
Failing Item: v DISKFAN

v DISKFAN
28CB7634
28CB7614 Explanation: A fatal error occurred on fan 3.
Explanation: A fatal error occurred on fan 1. Failing Item:
Failing Item: v DISKFAN
v DISKFAN
28CB8401
28CB7621 Explanation: Removable media power fault.
Explanation: A fatal error occurred on redundant fan Failing Item:
2.
v DEVBPLN
Failing Item:
v DISKFAN 28CB8404
28CB7624 required.
Failing Item: 28CBFFF4
v DISKFAN Explanation: Device backplane problem.
Failing Item:
28CB7631 v DEVBPLN
Explanation: A fatal error occurred on redundant fan v STORIOA
3. v FI01140
(28CC) Reference codes

Failing Item:
28CC1511
v DISKPWR
v DISKFAN
supply 1.
v FI01106
Failing Item:
v DEVBPLN
v DISKPWR
v DISKFAN
28CC1525
v FI01106
v DEVBPLN
2.
Failing Item:
28CC1515
v DISKPWR
v DISKFAN
1.
v FI01106
Failing Item:
v DEVBPLN
v DISKPWR
v DISKFAN
28CC3002
v FI01106
v DEVBPLN
Failing Item:
28CC1521
v DEVBPLN
v STORIOA
supply 2.

28CC3109 • 28CCFFF4
v FI01140
28CC8401
v FI01106
Explanation: Removable media power fault.
28CC3109 Failing Item:

v DEVBPLN
backplane command.
28CC8404
Failing Item:
v DEVBPLN Explanation: System log entry only, no service action
required.
v STORIOA
v FI01140
28CCFFF4
v FI01106
Explanation: A fatal error occurred on redundant fan v DEVBPLN
1. v STORIOA
v DISKFAN v FI01106
28CC7614
Failing Item:
v DISKFAN
28CC7621
2.
Failing Item:
v DISKFAN
28CC7624
Failing Item:
v DISKFAN
28CC7631
3.
Failing Item:
v DISKFAN
28CC7634
Failing Item:
v DISKFAN

293C1511 • 293C7634

v DEVBPLN
293C1511
v SASEXP
supply 1.
293C3002
Failing Item:
v DISKPWR
v DEVBPLN
v SASEXP
293C1515 failure. Verify that input power to the expansion unit
1.
Failing Item:
v DEVBPLN
Failing Item:
293C3109
v DISKPWR
v DEVBPLN
backplane command.
v SASEXP
Failing Item:
v SASEXP
293C1521
v SASCABL
v STORIOA
supply 2.
v DEVBPLN
Failing Item:
v DISKPWR
293C7614
v DEVBPLN
v SASEXP
Failing Item:
293C1525 v DISKFAN

2. 293C7624
problem verify that utility power, BBU or UPS to the 293C7634
v DISKFAN
Failing Item:
v DISKPWR

293C7644 • 293D3109
293C7644 293CFFF4
v DISKFAN v SASEXP
v SASCABL
293C8404 v STORIOA
required.

293D1511
Explanation: A non-fatal error occurred on power that detected the problem are in the FRU list of the
supply 1. serviceable event. Before starting a repair action for this
Failing Item:
v DISKPWR logged. If there was an interruption to power at about
v DEVBPLN the same time then no service is required and this
v SASEXP problem can be closed.
Failing Item:
293D1515 v DISKPWR
Explanation: A fatal error occurred on power supply v DEVBPLN

1. v SASEXP
a loss of utility power, battery back up or UPS power 293D3002
problem verify that utility power, BBU or UPS to the Problem determination: If there are multiple xxxx3002
unit was not interrupted at the time the SRC was reference codes logged from the same disk expansion
logged. If there was an interruption to power at about unit at about the same time suspect an input power
the same time then no service is required and this failure. Verify that input power to the expansion unit
problem can be closed. power supplies was active at the time of the error. If
Failing Item:
v DISKPWR power failure. Restore power to the expansion unit and
v DEVBPLN close the xxxx3002 problems. Otherwise work the
v SASEXP xxxx3002 reference codes.
Failing Item:
293D1521 v SASEXP
Explanation: A non-fatal error occurred on power v SASCABL
supply 2. v STORIOA

v DISKPWR
v DEVBPLN 293D3109
v SASEXP Explanation: I/O adapter timed out a device
backplane command.
293D1525 Failing Item:
Explanation: A fatal error occurred on power supply v SASEXP
2. v SASCABL
Problem determination: This SRC can be the result of v STORIOA

293D7614 • 297D3002
v DEVBPLN
293D7644
293D7614
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
293D8404
293D7624
required.
Failing Item: 293DFFF4
Failing Item:
293D7634
v SASEXP
Explanation: A fatal error occurred on fan 3. v SASCABL
v DISKFAN v DEVBPLN

Failing Item:
297D1511
v DISKPWR
v DEVBPLN
supply 1.
v SASEXP
Failing Item:
v DISKPWR
297D1525
v DEVBPLN
v SASEXP
2.
297D1515
Explanation: A fatal error occurred on power supply to the I/O storage unit. The unit and power supply
1. that detected the problem are in the FRU list of the
unit was not interrupted at the time the SRC was Failing Item:
logged. If there was an interruption to power at about v DISKPWR
v DEVBPLN
v SASEXP
Failing Item:
v DISKPWR
297D3002
v DEVBPLN
v SASEXP
297D1521
Explanation: A non-fatal error occurred on power unit at about the same time suspect an input power
supply 2. failure. Verify that input power to the expansion unit

297D3109 • 297DFFF4

297DFFF4
power failure. Restore power to the expansion unit and Explanation: Device backplane problem.
Failing Item:
v SASEXP
Failing Item:
v SASCABL
v SASEXP
v STORIOA
v SASCABL
v DEVBPLN
v STORIOA
v DEVBPLN
297D3109
backplane command.
Failing Item:
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
297D7614
Failing Item:
v DISKFAN
297D7624
Failing Item:
v DISKFAN
297D7634
Failing Item:
v DISKFAN
297D7644
Failing Item:
v DISKFAN
297D8404
required.

2A391511 • 2A397634

v DEVBPLN
2A391511
v SASEXP
supply 1.
2A393002
Failing Item:
v DISKPWR
v DEVBPLN
v SASEXP
2A391515 failure. Verify that input power to the expansion unit
1.
Failing Item:
v DEVBPLN
Failing Item:
2A393109
v DISKPWR
v DEVBPLN
backplane command.
v SASEXP
Failing Item:
v SASEXP
2A391521
v SASCABL
v STORIOA
supply 2.
v DEVBPLN
Failing Item:
v DISKPWR
2A397614
v DEVBPLN
v SASEXP
Failing Item:
2A391525 v DISKFAN

2. 2A397624
problem verify that utility power, BBU or UPS to the 2A397634
v DISKFAN
Failing Item:
v DISKPWR

2A397644 • 2B0F8404
2A397644 2A39FFF4
v DISKFAN v SASEXP
v SASCABL
2A398404 v STORIOA
required.

Failing Item:
2B093002
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
failure. Verify that input power to the expansion unit 2B098404
input power to the expansion unit failed the expansion Explanation: System log entry only, no service action
unit was not able to log a reference code for the input required.
close the xxxx3002 problems. Otherwise work the 2B09FFF4
Failing Item:
Failing Item:
v SASEXP
v SASEXP
v SASCABL
v SASCABL
v STORIOA
v STORIOA
v DEVBPLN
v DEVBPLN
2B093109
backplane command.
(2B0F) Reference codes

v STORIOA
2B0F3002
v DEVBPLN
2B0F3109
reference codes logged from the same disk expansion Explanation: I/O adapter timed out a device
unit at about the same time suspect an input power backplane command.
failure. Verify that input power to the expansion unit Failing Item:
input power to the expansion unit failed the expansion v SASEXP
unit was not able to log a reference code for the input v SASCABL
power failure. Restore power to the expansion unit and v STORIOA
v DEVBPLN
Failing Item:
2B0F8404
v SASEXP
v SASCABL

2B0FFFF4 • 2B4C4010

required. v SASEXP
v SASCABL
2B0FFFF4 v STORIOA
Explanation: Device backplane problem. v DEVBPLN
(2B4C) Reference codes

v STORIOA
2B4C1310
v SASCABL
Explanation: The I/O adapter resource not available.
Response: The I/O adapter error log is being filled 2B4C3401
Check other errors reported to the system and correct Explanation: Device backplane problem.
them. Failing Item:
v SASEXP
2B4C3000 v DEVBPLN
Explanation: A permanent failure occurred.
Failing Item: 2B4C3405
v STORIOA Explanation: An error occurred during task
v ANYBRDG initialization for a removable media device. This SRC is
logged when an error occurs and the removable media
device driver cannot determine the device type or
2B4C3020 model.
Explanation: Storage subsystem configuration error. Response: Perform the following:
Failing Item: v Check the Product Activity Log for other entries that
v SIP4150 indicate interface problems and work those
problems.
v Check the device firmware level and apply the latest
2B4C3100
PTFs.
Explanation: Device bus interface error occurred. v Check for LIC logs with major code 2E00. Contact
Failing Item: your next level of support with the information you
have gathered.
v SIP4150
Problem determination: IPL the IOP to retry the
device identification process. If the error persists then
2B4C3140 contact your service provider.
Explanation: System log entry only. No service action Failing Item:
required.
v PTFSRCH
2B4C3202
2B4C34FF
Response: The device is not supported in the current
configuration. An I/O processor might be required. Response: No action required. This reference code is
Failing Item:
v SVCDOCS 2B4C3601
Explanation: System log entry only. No service action
2B4C3400 required.
Explanation: Unknown resource error.
v SIP4150 Explanation: Configuration error.
v FI02112

2B4C4020 • 2B4C4160
Response: Incorrect connection between cascaded

2B4C4061
enclosures.
Failing Item:
v SIP3142 Response: A redundant disk unit connection has been
2B4C4020
2B4C4070
Explanation: Configuration error.
Response: Number of connections exceed I/O adapter required.
design limits.
v SIP3143
Failing Item:
2B4C4030
v SIP4152
v SASCABL
Response: Incorrect multipath connection. v SASEXP
v SIP4144 v STORIOA
v FI01105
2B4C4040
Explanation: Configuration error. 2B4C4101
Response: Incomplete multipath connection between Explanation: Temporary device bus fabric error.
I/O adapter and enclosure. Failing Item:
v SIP4144
2B4C4110
2B4C4041 Explanation: Unsupported enclosure function
Explanation: Incomplete multipath connection. detected.
Response: Incomplete multipath connection between Failing Item:

device backplane and device. v SIP3145
Failing Item:
v SIP3146 2B4C4150
Explanation: I/O adapter detected PCI bus error.
2B4C4050 Response: If this event appears in a serviceable event
Explanation: Enclosure does not support required view, work with the failing item list found there. If this
multipath function. event does not appear in a serviceable event view, no
Failing Item:
Failing Item:
v SIP3148
v BACKPLN
v STORIOA
2B4C4060
Explanation: Multipath redundancy level reduced. 2B4C4160
Response: A redundant disk unit connection has Explanation: I/O adapter detected and recovered a
failed. PCI bus error.
v SIP4153 view, work with the failing item list found there. If this
v SASCABL event does not appear in a serviceable event view, no
v SASEXP

2B4C70DD • 2B4C8151
Failing Item:
2B4C8140
v BACKPLN
v STORIOA
error.
2B4C70DD
Explanation: Disrupt device command completed event does not appear in a serviceable event view, no
successfully. service action is required.
Failing Item:
2B4C8008 v SIP4150
Explanation: A permanent failure has occurred in the
cache battery pack or capacitive cache power card. 2B4C8141
Response: Under a certain configuration, this SRC Explanation: IOA detected recoverable device error.
may not represent an error that requires a service
action. Depending on the configuration of the system, Response: No action is required. This reference code
the Storage IOA may have been altered and/or the is logged for information only.
attachment of OEM Storage that emulates a Load 2B4C8145
each time the IOA is IPLed and it can be ignored. Explanation: Disk device detected recoverable error.
Failing Item: Response: This error is logged against the storage

controller resource. Contact your next level of support
v CACHBAT
to determine the part number and location code of the
v STORIOA device.
v FEATCRD
Failing Item:
v NEXTLVL
2B4C8009
Explanation: Impending failure in the cache battery 2B4C8146
pack or capacitive cache power card.
Failing Item:
Failing Item:
v CACHBAT
v FI01105
2B4C8100
2B4C8150
Failing Item:
Response: Under a certain configuration, this SRC
v PTFSRCH
v STORIOA action. Depending on the configuration of the system,
2B4C8130 Storage IOA Cache may have been disabled to allow
Explanation: IOA detected recoverable device bus Source drive. If this is the case, this error will be posted
error. each time the IOA is IPLed and it can be ignored.
v STORIOA
service action is required. v ANYBRDG
Failing Item:
2B4C8151
v SIP4150
Failing Item:
v PTFSRCH
v STORIOA

2B4C8155 • 2B4C8300
to manually re-IPL the virtual I/O processor and

2B4C8155
Vary On attached resources.
Explanation: A permanent failure occurred. v If manually reIPL-ing the virtual I/O processor
Failing Item: fails then contact your next level of support. This
ends the procedure.
v PTFSRCH
3. If the Failing Item indicates an I/O adapter, then
v STORIOA
contact your next level of support to replace the
I/O adapter.
2B4C8156
Failing Item:
Explanation: A permanent failure occurred. v SVCDOCS
v PTFSRCH
v STORIOA 2B4C8300
Explanation: IOA hardware error or PCI bus error.
2B4C8157
Problem determination: Perform the following:
Explanation: I/O adapter card error. The actions and 1. Examine the location code of the adapter to
Failing Item list in the Service Action Log will vary determine if the adapter is in the system unit or an
based on the conditions this event was logged for. expansion unit. If the adapter is in an expansion
Response: The FRU list in the Service Action Log will unit, continue with the next step. Otherwise this
vary based on the conditions this event was logged for. ends the procedure.
Perform the following: 2. If multiple storage adapters in the same expansion
1. Display the Service Action Log entry for this SRC. unit logged reference code xxxx8300 as a serviceable
event at about the same time, continue with the
2. If the Failing Item indicates SVCDOCS, then next step. Otherwise this ends the procedure.
continue with this step. Otherwise go to the next
step. Do NOT replace the I/O adapter. This is a 3. Suspect a problem with the connection to the
recoverable error. enclosure. The problem may have been temporary
while working on the unit or while working on the
v LIC will automatically re-IPL the virtual I/O connection or cable(s) to the unit. If the adapter
processor associated with the adapter. Other problems were created while working on the unit or
resources attached to the virtual I/O processor working on the connection to the unit, go to step 5.
may need to be Varied On.
4. Search for problems logged at about the same time
v If the virtual I/O processor or adapter are not and call out the FRUs that connect the expansion
operational then use Hardware Service Manager unit to the system unit including the cable(s). Work
to manually re-IPL the virtual I/O processor and those problems first, then return to the next step in
Vary On attached resources. this procedure.
v If manually reIPL-ing the virtual I/O processor 5. Use Hardware Service Manager (HSM) to verify
fails then contact your next level of support. This that the adapters have returned to operational
ends the procedure. status. Close reference code xxxx8300 problems for
3. If the Failing Item indicates an I/O adapter, then adapters that have returned to operational status.
replace the I/O adapter. Check the list below to Expansion units attached to system units using
determine if the adapter type you are replacing has Light Path service indicators may have activated the
multiple physical parts. FRU fault indicators for those adapters. Use the
Service Action Log (SAL) to turn off the FRU fault
indicators for adapters that have returned to
1. Display the Service Action Log entry for this SRC. operational status.
2. If the Failing Item indicates SVCDOCS, then 6. Work reference code xxxx8300 problems for any
continue with this step. Otherwise go to the next adapters that have not returned to operational
step. Do NOT replace the I/O adapter. This is a status. This ends the procedure.
recoverable error.
Failing Item:
v LIC will automatically re-IPL the virtual I/O
processor associated with the adapter. Other v STORIOA
resources attached to the virtual I/O processor v ANYBRDG
may need to be Varied On. v PTFSRCH
v If the virtual I/O processor or adapter are not
operational then use Hardware Service Manager

2B4C8301 • 2B4C9025
2B4C8301 2B4C9010
Explanation: Not valid condition in Licensed Internal Explanation: Cache data associated with attached
Code. devices cannot be found.
v PTFSRCH v SIP3120
v STORIOA
2B4C9011
2B4C8302 Explanation: Cache data belongs to devices other than
Explanation: Missing Licensed Internal Code. those attached.
Response: Ensure that the code necessary to support Failing Item:

this I/O adapter is loaded. v NEXTLVL
Failing Item:
v SVCDOCS 2B4C9020
v STORIOA Explanation: Two or more disk units missing from
RAID-5 or RAID-6 array.
2B4C8400 Failing Item:
Explanation: Licensed Internal Code error. v SIP3111
Failing Item:
2B4C9021
v PTFSRCH
Explanation: Two or more disk units missing from
2B4C8404
Failing Item:
required. v SIP3111
2B4C9000 2B4C9022
Explanation: Device error. Explanation: Two or more disk units missing from
Failing Item:
Failing Item:
v FI01105
v SIP3111
v STORIOA
2B4C9023
2B4C9001
Explanation: One or more array members not in
Explanation: Device configuration error.
required physical locations.
Failing Item:
Failing Item:
v NEXTLVL
v SIP3112
2B4C9002
2B4C9024
Explanation: Device error.
Explanation: Array member physical location conflicts
Failing Item: with another array.
v NEXTLVL
2B4C9008
Explanation: I/O card does not support functions 2B4C9025
Explanation: Incompatible device.
Failing Item:
Response: An incompatible device is at the physical
v SIP3130

2B4C9026 • 2B4C9050
location of the device which is causing the array to be

2B4C9031
exposed.
Failing Item:
v SIP3110 Response: Either a previous rebuild was interrupted
v FI02112
2B4C9026
Explanation: Disk unit not found at required physical 2B4C9032
location.
Explanation: A disk unit in an array is missing or
Response: A previously exposed disk unit in an array failed.
was not found at the required physical location.
v SIP3110
2B4C9027 v FI02112
Explanation: Array not functional due to parity out of
synchronization. 2B4C9040
Response: Array is or would become exposed and Explanation: Re-synchronization of array parity was
parity data is out of synchronization. initiated.
Failing Item: Response: No action required.
v SIP3113
2B4C9041
2B4C9028
Explanation: Maximum number of functional arrays and corrected errors.
has been exceeded.
Response: Reduce the number of arrays on this I/O the problem.
adapter. Either move all the devices in an array to
Failing Item:
another I/O adapter that supports arrays, or stop an
array on this I/O adapter. v NEXTLVL
Failing Item:
2B4C9042
v SVCDOCS
Explanation: Background parity check corrected errors
on disk unit.
2B4C9029
Explanation: Maximum number of functional array
the problem.
members has been exceeded.
Failing Item:
v NEXTLVL
Failing Item:
v NEXTLVL
2B4C9050
Explanation: Required cache data not found for one or
2B4C9030
more disk units.
Failing Item:
v SIP3131
Failing Item:
v SIP3110
v FI02112

2B4C9051 • 2B4C9090
2B4C9051 2B4C9074
Explanation: Cache data exists for one or more Explanation: Multiple I/O adapters connected in a not
missing or failed devices. valid configuration.
Failing Item: Response: Multiple I/O adapters not capable of
v SIP3132 similar functions or controlling the same set of devices.
Failing Item:
2B4C9052 v SIP4141
Explanation: Cache data exists for one or more
modified devices. 2B4C9075
Response: Contact your next level of support. Explanation: Incomplete multipath connection
between IOA and remote IOA.
Failing Item:
v SIP4149
2B4C9054
2B4C9076
Explanation: IOA resources not available due to
previous problems. Explanation: Missing auxiliary IOA or remote IOA.
v SIP3121 v SIP4147
2B4C9055 2B4C9081
Explanation: Write cache data is available for attached Explanation: Device error.
storage IOA.
Failing Item:
Response: No service action required. v FI01105
v STORIOA
2B4C9070
Explanation: System log entry only. No service action 2B4C9082
required.
Failing Item:
2B4C9071
v FI01105
Explanation: Link from IOA to auxiliary or remote
v STORIOA
IOA is operational.
Response: No service action required.
2B4C9083
2B4C9072
required.
IOA is non-operational.
2B4C9084
required.
2B4C9073
Explanation: Multiple I/O adapters connected in a not 2B4C9090
valid configuration.
Failing Item: last known status.
v SIP4140 Response: Use Hardware Service Manager to re-IPL
the virtual I/O processor that is associated with this
I/O adapter. Other resources attached to the virtual
I/O processor may then need to be Varied On.

2B4C9091 • 2B57B9B0
If any reference codes are surfaced, use the new Explanation: Internal program error in driver code.
reference code to resolve the problem.
Failing Item:
If you cannot resolve the problem, contact your next v PTFSRCH
level of support.
v SVCDOCS
Explanation: Tape device information was logged.
Informational event, no service required.
2B4C9091
Explanation: Incorrect hardware configuration change 2B4CC000
detected.
Response: Use Hardware Service Manager to re-IPL required.
If any reference codes are surfaced, use the new
2B4CC402
level of support. Response: Ask your next level of support for
assistance.
Failing Item:
v PTFSRCH
2B4C9092
2B4CFF3D
use. Explanation: I/O adapter detected a recoverable error.
v SIP3134 v STORIOA
v ANYBRDG
2B4C9500

2B56A001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
2B56B9B0

2B57A001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
2B57B9B0

2B5A3002 • 2B74A001
(2B5A) Reference codes

Failing Item:
2B5A3002
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
failure. Verify that input power to the expansion unit 2B5A8404
close the xxxx3002 problems. Otherwise work the 2B5AFFF4
Failing Item:
Failing Item:
v SASEXP
v SASEXP
v SASCABL
v SASCABL
v STORIOA
v STORIOA
v DEVBPLN
v DEVBPLN
2B5A3109
backplane command.

v FI00718
2B6CB904
v AJDGP01
v MA_BRDG
failed.
Failing Item:
2B6CB941
v AJDGP01
v FI00719
Failing Item:
2B6CB934 v FI00719
v FI00718
v AJDGP01
Failing Item:
v FI00719
2B6CB942
v FI00718
2B6CB940 Failing Item:

v FI00719
v FI00718
Failing Item:
v AJDGP01
v FI00719

Failing Item:
2B74A001
v AJDG301
detected.

2B74B9B0 • 2B933400
v IOA
2B74B9B0
v AJDG301
Failing Item:

Failing Item:
2B933020
v FCPORT
Explanation: Configuration error on port 0.
v FCIOA
Response: Too many devices have been configured on v FCDEV
port 0. Change the configuration.
v OPT_CLN
Failing Item:
v SVCDOCS 2B933121
2B933021
Response: Too many devices have been configured on 2. This error can occur when a shared device is being
port 1. Change the configuration. moved from one LPAR to another LPAR and the
v SVCDOCS 3. This error can occur if there is a port or link failure.
2B933100
Failing Item:
Explanation: Interface error on port 0.
v FCPORT
v FCINTF v FCDEV
v ANYFC v OPT_CLN
v FCIOA
v OPT_CLN 2B933140
Explanation: Port 0 is now operational.
2B933101
Explanation: Interface error on port 1. code that occurred before it require no service action,
Failing Item: since the port is now operational.
v FCINTF
v ANYFC 2B933141
v FCIOA Explanation: Port 1 is now operational.
v OPT_CLN Response: This reference code and the 3121 reference
2B933120 since the port is now operational.

2B933400
2. This error can occur when a shared device is being Failing Item:
moved from one LPAR to another LPAR and the v FCDEV
port was left open. v FCINTF
3. This error can occur if there is a port or link failure. v ANYFC
v FCIOA
v OPT_CLN

2B933405 • 2B938302
2B933405 2B938131
Explanation: An error occurred during task Explanation: Recovered Fibre Channel interface error
initialization for a removable media device. This SRC is on port 1.
model.
Response: Perform the following:
2B938150
v Check the Product Activity Log for other entries that
indicate interface problems and work those Explanation: A permanent I/O adapter failure
problems. occurred.
v Check the device firmware level and apply the latest Failing Item:
PTFs. v FCIOA
v Check for LIC logs with major code 2E00. Contact v ANYBRDG
your next level of support with the information you
have gathered. v OPT_CLN

device identification process. If the error persists then 2B938151
contact your service provider. Explanation: Licensed Internal Code error.
v PTFSRCH v PTFSRCH
v FCIOA
2B9334FF
Explanation: Format in progress. 2B938300
Response: The device indicated that a format is in Explanation: IOA hardware error or PCI bus error.
Failing Item:
code is logged for information only. v FCIOA
v ANYBRDG
2B934150 v PTFSRCH
v OPT_CLN
2B938301
event does not appear in a serviceable event view, no Explanation: Not valid condition in Licensed Internal
service action is required. Code.
v BACKPLN v PTFSRCH
v FCIOA v FCIOA
v OPT_CLN
2B938100
Explanation: Licensed Internal Code error. 2B938302
Failing Item: Explanation: Missing Licensed Internal Code.

v PTFSRCH Response: Ensure that the code necessary to support
v FCIOA this I/O adapter is loaded.
Failing Item:
2B938130 v SVCDOCS
Explanation: Recovered Fibre Channel interface error v FCIOA
on port 0. v OPT_CLN

2B939500 • 2B9B3120

2B939500
Failing Item:
Explanation: Internal program error in driver code.
v PTFSRCH
Failing Item:
v PTFSRCH
2B93B9B0
2B939903
Failing Item:
Informational event, no service required. v IOA
v AJDG301
2B93A001
2B93C000
detected. Explanation: System log entry only, no service action
required.
Failing Item:
v AJDG301 Response: No action is required. This reference code
2B93B000
2B93C402
required. Explanation: Licensed Internal Code error.
Response: No action is required. This reference code Failing Item:

is logged for information only. v PTFSRCH
2B93B402
(2B9B) Reference codes

2B9B3020 2B9B3101
Explanation: Configuration error on port 0. Explanation: Interface error on port 1.
Response: Too many devices have been configured on Failing Item:
port 0. Change the configuration. v FCINTF
Failing Item: v ANYFC
v SVCDOCS v FCIOA
v OPT_CLN
2B9B3021
Explanation: Configuration error on port 1. 2B9B3120
Response: Too many devices have been configured on Explanation: An open port was detected on port 0.
port 1. Change the configuration. Problem determination: Perform the following steps:
Failing Item: 1. Check for a missing cable or wrap connector.
v SVCDOCS 2. This error can occur when a shared device is being
port was left open.
2B9B3100
Explanation: Interface error on port 0. If you have eliminated the above possibilities
Failing Item: contact your next level of support.
v ANYFC v FCPORT
v FCIOA v FCIOA
v OPT_CLN v FCDEV

2B9B3121 • 2B9B8131
v OPT_CLN v Check the device firmware level and apply the latest
PTFs.
2B9B3121 v Check for LIC logs with major code 2E00. Contact
Explanation: An open port was detected on port 1. have gathered.
Problem determination: Perform the following steps: Problem determination: IPL the IOP to retry the
1. Check for a missing cable or wrap connector. device identification process. If the error persists then
2. This error can occur when a shared device is being contact your service provider.
moved from one LPAR to another LPAR and the Failing Item:
port was left open.
v PTFSRCH
contact your next level of support. 2B9B34FF

v FCPORT Response: The device indicated that a format is in
v FCIOA progress. When the format is complete, the device
v FCDEV
v OPT_CLN
2B9B4150
2B9B3140
Response: This reference code and the 3120 reference view, work with the failing item list found there. If this
code that occurred before it require no service action, event does not appear in a serviceable event view, no
since the port is now operational. service action is required.
Failing Item:
2B9B3141
v BACKPLN
Explanation: Port 1 is now operational. v FCIOA
code that occurred before it require no service action, 2B9B8100

v PTFSRCH
v FCIOA
Failing Item:
v FCDEV
2B9B8130
v FCINTF
Explanation: Recovered Fibre Channel interface error
v ANYFC
on port 0.
v FCIOA
v OPT_CLN
2B9B3405
2B9B8131
Explanation: An error occurred during task
initialization for a removable media device. This SRC is
on port 1.
device driver cannot determine the device type or Response: No action required. This reference code is
model. logged for information only.
indicate interface problems and work those
problems.

2B9B8150 • 2B9BC402
2B9B8150 2B9B9903
Explanation: A permanent I/O adapter failure Explanation: Tape device information was logged.
occurred. Informational event, no service required.
Failing Item:
v FCIOA 2B9BB000
v ANYBRDG Explanation: System log entry only, no service action
v OPT_CLN required.
2B9B8151 is logged for information only.

2B9BB402
Failing Item:
v PTFSRCH
v PTFSRCH
2B9B8300
2B9BC000
Failing Item:
required.
v FCIOA
v ANYBRDG
v PTFSRCH
v OPT_CLN
2B9BC402
2B9B8301
Failing Item:
Explanation: Not valid condition in Licensed Internal
Code. v PTFSRCH
Failing Item:
v PTFSRCH
v FCIOA
v OPT_CLN
2B9B8302
Explanation: Missing Licensed Internal Code.
Response: Ensure that the code necessary to support
this I/O adapter is loaded.
Failing Item:
v SVCDOCS
v FCIOA
v OPT_CLN
2B9B9500
Failing Item:
v PTFSRCH

2BBE1511 • 2BBE7634
(2BBE) Reference codes

v DEVBPLN
2BBE1511
v SASEXP
supply 1.
2BBE3002
Failing Item:
v DISKPWR
v DEVBPLN
v SASEXP
2BBE1515 failure. Verify that input power to the expansion unit
1.
Failing Item:
v DEVBPLN
Failing Item:
2BBE3109
v DISKPWR
v DEVBPLN
backplane command.
v SASEXP
Failing Item:
v SASEXP
2BBE1521
v SASCABL
v STORIOA
supply 2.
v DEVBPLN
Failing Item:
v DISKPWR
2BBE7614
v DEVBPLN
v SASEXP
Failing Item:
2BBE1525 v DISKFAN

2. 2BBE7624
problem verify that utility power, BBU or UPS to the 2BBE7634
v DISKFAN
Failing Item:
v DISKPWR

2BBE7644 • 2BD63109
2BBE7644 2BBEFFF4
v DISKFAN v SASEXP
v SASCABL
2BBE8404 v STORIOA
required.
(2BD6) Reference codes

2BD61511
Failing Item:
Failing Item:
2BD61515 v DISKPWR

1. v SASEXP
a loss of utility power, battery back up or UPS power 2BD63002
Failing Item:
Failing Item:
2BD61521 v SASEXP
supply 2. v STORIOA

v DISKPWR
v DEVBPLN 2BD63109
backplane command.
2BD61525 Failing Item:
2. v SASCABL

2BD67614 • 2BD83002
v DEVBPLN
2BD67644
2BD67614
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
2BD68404
2BD67624
required.
Failing Item: 2BD6FFF4
Failing Item:
2BD67634
v SASEXP
Explanation: A fatal error occurred on fan 3. v SASCABL
v DISKFAN v DEVBPLN

Failing Item:
2BD81511
v DISKPWR
v DEVBPLN
supply 1.
v SASEXP
Failing Item:
v DISKPWR
2BD81525
v DEVBPLN
v SASEXP
2.
2BD81515
Explanation: A fatal error occurred on power supply to the I/O storage unit. The unit and power supply
1. that detected the problem are in the FRU list of the
unit was not interrupted at the time the SRC was Failing Item:
logged. If there was an interruption to power at about v DISKPWR
v DEVBPLN
v SASEXP
Failing Item:
v DISKPWR
2BD83002
v DEVBPLN
v SASEXP
2BD81521
Explanation: A non-fatal error occurred on power unit at about the same time suspect an input power
supply 2. failure. Verify that input power to the expansion unit

2BD83109 • 2BD8FFF4

2BD8FFF4
power failure. Restore power to the expansion unit and Explanation: Device backplane problem.
Failing Item:
v SASEXP
Failing Item:
v SASCABL
v SASEXP
v STORIOA
v SASCABL
v DEVBPLN
v STORIOA
v DEVBPLN
2BD83109
backplane command.
Failing Item:
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
2BD87614
Failing Item:
v DISKFAN
2BD87624
Failing Item:
v DISKFAN
2BD87634
Failing Item:
v DISKFAN
2BD87644
Failing Item:
v DISKFAN
2BD88404
required.

2BD91310 • 2BD94020

2BD91310 2BD93401
Explanation: The I/O adapter resource not available. Explanation: Device backplane problem.
Response: The I/O adapter error log is being filled Failing Item:
faster than the errors are being reported to the system. v SASEXP
v DEVBPLN
them.
2BD93405
2BD93000
Failing Item: logged when an error occurs and the removable media
v STORIOA device driver cannot determine the device type or
model.
v ANYBRDG
2BD93020 v Check the Product Activity Log for other entries that
Explanation: Storage subsystem configuration error. problems.
Failing Item: v Check the device firmware level and apply the latest
v SIP4150 PTFs.
v Check for LIC logs with major code 2E00. Contact
2BD93100 have gathered.
Explanation: Device bus interface error occurred. Problem determination: IPL the IOP to retry the
Failing Item: device identification process. If the error persists then
contact your service provider.
v SIP4150
Failing Item:
2BD93140 v PTFSRCH

required. 2BD934FF
2BD93202 Response: No action required. This reference code is
Explanation: Storage subsystem configuration error. logged for information only.

configuration. An I/O processor might be required. 2BD93601
Failing Item: Explanation: System log entry only. No service action

required.
v SVCDOCS
2BD94010
2BD93400
Failing Item:
enclosures.
v SIP4150
Failing Item:
v FI02112
v SIP3142
v STORIOA
v SASCABL
2BD94020

2BD94030 • 2BD94160
Response: Number of connections exceed I/O adapter

2BD94070
design limits.
Failing Item:
required.
v SIP3143
2BD94100
2BD94030
Failing Item:
Response: Incorrect multipath connection.
v SIP4152
v SIP4144 v SASEXP
v DEVBPLN
2BD94040 v STORIOA
Explanation: Configuration error. v FI01105
I/O adapter and enclosure. 2BD94101
Failing Item: Explanation: Temporary device bus fabric error.

v SIP4152
2BD94041
Explanation: Incomplete multipath connection. 2BD94110
Response: Incomplete multipath connection between Explanation: Unsupported enclosure function
device backplane and device. detected.
v SIP3146 v SIP3145
2BD94050 2BD94150
Explanation: Enclosure does not support required Explanation: I/O adapter detected PCI bus error.
multipath function.
v SIP3148 event does not appear in a serviceable event view, no

v BACKPLN
v STORIOA
failed.
2BD94160
Failing Item:
Explanation: I/O adapter detected and recovered a
v SIP4153 PCI bus error.
v SASCABL
v SASEXP view, work with the failing item list found there. If this
2BD94061 service action is required.
Explanation: Multipath redundancy level increased. Failing Item:

v BACKPLN
restored. No service action is required. v STORIOA

2BD970DD • 2BD98155
Failing Item:
2BD970DD
v SIP4150
Explanation: Disrupt device command completed
successfully.
2BD98141
2BD98008 Explanation: IOA detected recoverable device error.
Explanation: A permanent failure has occurred in the Response: No action is required. This reference code
cache battery pack or capacitive cache power card. is logged for information only.

may not represent an error that requires a service 2BD98145
action. Depending on the configuration of the system, Explanation: Disk device detected recoverable error.
Storage IOA Cache may have been disabled to allow Response: This error is logged against the storage
attachment of OEM Storage that emulates a Load controller resource. Contact your next level of support
Source drive. If this is the case, this error will be posted to determine the part number and location code of the
each time the IOA is IPLed and it can be ignored. device.
v CACHBAT v NEXTLVL
v STORIOA
v FEATCRD 2BD98146
2BD98009
Failing Item:
Explanation: Impending failure in the cache battery v FI01105
Failing Item: 2BD98150
v CACHBAT
2BD98100
Explanation: Licensed Internal Code error. action. Depending on the configuration of the system,
Failing Item: Storage IOA Cache may have been disabled to allow
v PTFSRCH attachment of OEM Storage that emulates a Load
v STORIOA Source drive. If this is the case, this error will be posted

v STORIOA
error. v ANYBRDG

view, work with the failing item list found there. If this 2BD98151
event does not appear in a serviceable event view, no Explanation: Licensed Internal Code error.
Failing Item:
Failing Item:
v PTFSRCH
v SIP4150
v STORIOA
2BD98140
2BD98155
error. Explanation: A permanent failure occurred.

view, work with the failing item list found there. If this v PTFSRCH

2BD98156 • 2BD98301
Failing Item:
2BD98156
v SVCDOCS
v STORIOA
Failing Item:
v PTFSRCH 2BD98300
v STORIOA
2BD98157
1. Examine the location code of the adapter to
Explanation: I/O adapter card error. The actions and determine if the adapter is in the system unit or an
Failing Item list in the Service Action Log will vary expansion unit. If the adapter is in an expansion
based on the conditions this event was logged for. unit, continue with the next step. Otherwise this
Response: The FRU list in the Service Action Log will ends the procedure.
vary based on the conditions this event was logged for. 2. If multiple storage adapters in the same expansion
Perform the following: unit logged reference code xxxx8300 as a serviceable
1. Display the Service Action Log entry for this SRC. event at about the same time, continue with the
next step. Otherwise this ends the procedure.
2. If the Failing Item indicates SVCDOCS, then
continue with this step. Otherwise go to the next 3. Suspect a problem with the connection to the
step. Do NOT replace the I/O adapter. This is a enclosure. The problem may have been temporary
recoverable error. while working on the unit or while working on the
connection or cable(s) to the unit. If the adapter
problems were created while working on the unit or
processor associated with the adapter. Other
working on the connection to the unit, go to step 5.
resources attached to the virtual I/O processor
may need to be Varied On. 4. Search for problems logged at about the same time
and call out the FRUs that connect the expansion
unit to the system unit including the cable(s). Work
those problems first, then return to the next step in
this procedure.
5. Use Hardware Service Manager (HSM) to verify
v If manually reIPL-ing the virtual I/O processor
that the adapters have returned to operational
fails then contact your next level of support. This
status. Close reference code xxxx8300 problems for
ends the procedure.
adapters that have returned to operational status.
3. If the Failing Item indicates an I/O adapter, then Expansion units attached to system units using
replace the I/O adapter. Check the list below to Light Path service indicators may have activated the
determine if the adapter type you are replacing has FRU fault indicators for those adapters. Use the
multiple physical parts. Service Action Log (SAL) to turn off the FRU fault
Problem determination: Perform the following: indicators for adapters that have returned to
operational status.
1. Display the Service Action Log entry for this SRC.
6. Work reference code xxxx8300 problems for any
2. If the Failing Item indicates SVCDOCS, then adapters that have not returned to operational
continue with this step. Otherwise go to the next status. This ends the procedure.
step. Do NOT replace the I/O adapter. This is a
recoverable error. Failing Item:
v LIC will automatically re-IPL the virtual I/O v STORIOA
processor associated with the adapter. Other v ANYBRDG
v PTFSRCH
operational then use Hardware Service Manager 2BD98301
to manually re-IPL the virtual I/O processor and Explanation: Not valid condition in Licensed Internal
Vary On attached resources. Code.
Failing Item:
ends the procedure. v PTFSRCH
3. If the Failing Item indicates an I/O adapter, then v STORIOA
I/O adapter.

2BD98302 • 2BD99025
2BD98302 2BD99011
Explanation: Missing Licensed Internal Code. Explanation: Cache data belongs to devices other than
those attached.
this I/O adapter is loaded. Failing Item:
Failing Item: v NEXTLVL
v SVCDOCS
v STORIOA 2BD99020
2BD98400 RAID-5 or RAID-6 array.
Explanation: Licensed Internal Code error. Failing Item:

v SIP3111
Failing Item:
v PTFSRCH
2BD99021
2BD98404 Explanation: Two or more disk units missing from

required. Failing Item:
v SIP3111
2BD99000
2BD99022
Failing Item:
v FI01105
Failing Item:
v STORIOA
v SIP3111
2BD99001
2BD99023
Failing Item: required physical locations.
v NEXTLVL
Failing Item:
v SIP3112
2BD99002
Explanation: Device error. 2BD99024
Failing Item: Explanation: Array member physical location conflicts
v NEXTLVL with another array.
Failing Item:
2BD99008 v NEXTLVL
expected by devices. 2BD99025
Failing Item: Explanation: Incompatible device.
v SIP3130
2BD99010 exposed.
Explanation: Cache data associated with attached Failing Item:

devices cannot be found. v SIP3110
v SIP3120

2BD99026 • 2BD99052
2BD99026 2BD99032
Explanation: Disk unit not found at required physical Explanation: A disk unit in an array is missing or
location. failed.
Response: A previously exposed disk unit in an array Response: The array is still protected, but the disk
was not found at the required physical location. unit should be replaced.
v NEXTLVL v SIP3110
v FI02112
2BD99027
Explanation: Array not functional due to parity out of 2BD99040
synchronization. Explanation: Re-synchronization of array parity was
Response: Array is or would become exposed and initiated.
parity data is out of synchronization. Response: No action required.
Failing Item:
v SIP3113 2BD99041
2BD99028 and corrected errors.
Explanation: Maximum number of functional arrays Response: Call your next level of support to report
has been exceeded. the problem.
Response: Reduce the number of arrays on this I/O Failing Item:
adapter. Either move all the devices in an array to v NEXTLVL
array on this I/O adapter.
2BD99042
Failing Item:
v SVCDOCS
on disk unit.
2BD99029
the problem.
Failing Item:
v NEXTLVL
v NEXTLVL
more disk units.
2BD99030
Failing Item:
Explanation: Array no longer protected due to v SIP3131
v SIP3110
v FI02112 missing or failed devices.
Failing Item:
2BD99031
v SIP3132
Response: Either a previous rebuild was interrupted 2BD99052
modified devices.

2BD99054 • 2BD99091
Failing Item:
2BD99076
v NEXTLVL
Explanation: Missing auxiliary IOA or remote IOA.

v SIP4147
previous problems.
2BD99081
Failing Item:
v SIP3121 Explanation: Device error.
Failing Item:
2BD99055 v FI01105
Explanation: Write cache data is available for attached v STORIOA
storage IOA.
Response: No service action required. 2BD99082
Explanation: System log entry only. No service action v FI01105
required. v STORIOA
2BD99071 2BD99083
Explanation: Link from IOA to auxiliary or remote Explanation: System log entry only. No service action
IOA is operational. required.
2BD99084
2BD99072 Explanation: System log entry only. No service action
Explanation: Link from IOA to auxiliary or remote required.
Response: No service action required. 2BD99090
2BD99073 last known status.
Explanation: Multiple I/O adapters connected in a not Response: Use Hardware Service Manager to re-IPL
valid configuration. the virtual I/O processor that is associated with this
Failing Item: I/O processor may then need to be Varied On.
v SIP4140
2BD99074
Explanation: Multiple I/O adapters connected in a not level of support.
Failing Item:
Response: Multiple I/O adapters not capable of v SVCDOCS
similar functions or controlling the same set of devices.
v SIP4141
detected.
2BD99075
Response: Use Hardware Service Manager to re-IPL
Explanation: Incomplete multipath connection the virtual I/O processor that is associated with this
between IOA and remote IOA. I/O adapter. Other resources attached to the virtual
Failing Item:
v SIP4149 If any reference codes are surfaced, use the new

2BD99092 • 2BE03401

2BD9C000
level of support.
required.
Failing Item:
v SVCDOCS is logged for information only.
2BD99092 2BD9C402
Explanation: Disk unit requires initialization before Explanation: Licensed Internal Code error.
use.
Response: Ask your next level of support for
Failing Item: assistance.
v SIP3134
Failing Item:
v PTFSRCH
2BD99500
Explanation: Internal program error in driver code. 2BD9FF3D
Failing Item: Explanation: I/O adapter detected a recoverable error.
v PTFSRCH
Failing Item:
v STORIOA
2BD99903
v ANYBRDG
(2BE0) Reference codes

2BE01310
required.
Response: The I/O adapter error log is being filled 2BE03202
them. Response: The device is not supported in the current
configuration. An I/O processor might be required.
2BE03000 Failing Item:
Failing Item:
2BE03400
v STORIOA
v ANYBRDG Explanation: Unknown resource error.
Failing Item:
2BE03020 v SIP4150
Explanation: Storage subsystem configuration error. v FI02112
v STORIOA
Failing Item:
v SASCABL
v SIP4150
2BE03401
2BE03100
Failing Item:
Failing Item:
v SASEXP
v SIP4150
v DEVBPLN
2BE03140

2BE03405 • 2BE04100
v SIP4144
2BE03405
2BE04040
logged when an error occurs and the removable media Explanation: Configuration error.
model. Response: Incomplete multipath connection between
I/O adapter and enclosure.
Failing Item:
indicate interface problems and work those v SIP4144
problems.
v Check the device firmware level and apply the latest 2BE04041
PTFs.
your next level of support with the information you Response: Incomplete multipath connection between
have gathered. device backplane and device.
Problem determination: IPL the IOP to retry the Failing Item:

device identification process. If the error persists then v SIP3146
Failing Item: 2BE04050
v PTFSRCH Explanation: Enclosure does not support required
multipath function.
2BE034FF Failing Item:
Explanation: Format in progress. v SIP3148
logged for information only. 2BE04060
2BE03601
Explanation: System log entry only. No service action failed.
required.
Failing Item:
v SIP4153
2BE04010
v SASCABL
Explanation: Configuration error. v SASEXP
enclosures. 2BE04061
Failing Item: Explanation: Multipath redundancy level increased.
v SIP3142
2BE04020
Explanation: Configuration error. 2BE04070
Response: Number of connections exceed I/O adapter Explanation: System log entry only. No service action
design limits. required.
Failing Item:
v SIP3143 2BE04100
Explanation: Configuration error. v SIP4152
Response: Incorrect multipath connection. v SASCABL
v SASEXP
Failing Item:

2BE04101 • 2BE08141
v DEVBPLN Source drive. If this is the case, this error will be posted
v STORIOA each time the IOA is IPLed and it can be ignored.
v CACHBAT
2BE04101 v STORIOA
Explanation: Temporary device bus fabric error. v FEATCRD
Failing Item:
2BE08009
v SIP4152
Explanation: Impending failure in the cache battery
2BE04110
Failing Item:
Explanation: Unsupported enclosure function
detected. v CACHBAT
Failing Item:
2BE08100
v SIP3145
Explanation: I/O adapter detected PCI bus error. v PTFSRCH
v STORIOA
event does not appear in a serviceable event view, no 2BE08130
v BACKPLN Response: If this event appears in a serviceable event
v STORIOA view, work with the failing item list found there. If this
2BE04160
Failing Item:
PCI bus error. v SIP4150

view, work with the failing item list found there. If this 2BE08140
event does not appear in a serviceable event view, no Explanation: IOA detected recoverable device bus
service action is required. error.
v BACKPLN view, work with the failing item list found there. If this
v STORIOA event does not appear in a serviceable event view, no
2BE070DD Failing Item:

v SIP4150
successfully.
2BE08141
2BE08008 Explanation: IOA detected recoverable device error.

2BE08145 • 2BE08157
2BE08145 2BE08157
Explanation: Disk device detected recoverable error. Explanation: I/O adapter card error. The actions and
Failing Item list in the Service Action Log will vary
Response: This error is logged against the storage
based on the conditions this event was logged for.
to determine the part number and location code of the Response: The FRU list in the Service Action Log will
device. vary based on the conditions this event was logged for.
Failing Item:
v NEXTLVL
2BE08146 step. Do NOT replace the I/O adapter. This is a
Explanation: Disk device detected recoverable error. recoverable error.
Failing Item: processor associated with the adapter. Other
v FI01105 resources attached to the virtual I/O processor
2BE08150 v If the virtual I/O processor or adapter are not
Explanation: A permanent failure occurred. to manually re-IPL the virtual I/O processor and
Response: Under a certain configuration, this SRC Vary On attached resources.
may not represent an error that requires a service v If manually reIPL-ing the virtual I/O processor
action. Depending on the configuration of the system, fails then contact your next level of support. This
the Storage IOA may have been altered and/or the ends the procedure.
Storage IOA Cache may have been disabled to allow 3. If the Failing Item indicates an I/O adapter, then
attachment of OEM Storage that emulates a Load replace the I/O adapter. Check the list below to
Source drive. If this is the case, this error will be posted determine if the adapter type you are replacing has
each time the IOA is IPLed and it can be ignored. multiple physical parts.
Failing Item: Problem determination: Perform the following:
v STORIOA 1. Display the Service Action Log entry for this SRC.
v ANYBRDG 2. If the Failing Item indicates SVCDOCS, then
2BE08151 step. Do NOT replace the I/O adapter. This is a
recoverable error.
v PTFSRCH resources attached to the virtual I/O processor
v STORIOA
2BE08155 to manually re-IPL the virtual I/O processor and
v PTFSRCH ends the procedure.
v STORIOA 3. If the Failing Item indicates an I/O adapter, then
I/O adapter.
2BE08156
Failing Item:
v SVCDOCS
Failing Item:
v STORIOA
v PTFSRCH
v STORIOA

2BE08300 • 2BE09011
Failing Item:
2BE08300
v SVCDOCS
v STORIOA
1. Examine the location code of the adapter to 2BE08400
determine if the adapter is in the system unit or an
expansion unit. If the adapter is in an expansion Explanation: Licensed Internal Code error.
unit, continue with the next step. Otherwise this Failing Item:
ends the procedure.
v PTFSRCH
2. If multiple storage adapters in the same expansion
unit logged reference code xxxx8300 as a serviceable
event at about the same time, continue with the 2BE08404
3. Suspect a problem with the connection to the required.
enclosure. The problem may have been temporary
connection or cable(s) to the unit. If the adapter 2BE09000
problems were created while working on the unit or Explanation: Device error.
Failing Item:
and call out the FRUs that connect the expansion v FI01105
unit to the system unit including the cable(s). Work v STORIOA
this procedure.
2BE09001
that the adapters have returned to operational Explanation: Device configuration error.
Failing Item:
Expansion units attached to system units using v NEXTLVL
Light Path service indicators may have activated the
FRU fault indicators for those adapters. Use the 2BE09002
indicators for adapters that have returned to Explanation: Device error.
operational status. Failing Item:
6. Work reference code xxxx8300 problems for any v NEXTLVL
adapters that have not returned to operational
status. This ends the procedure.
2BE09008
Failing Item:
v STORIOA Explanation: I/O card does not support functions
v ANYBRDG
v PTFSRCH Failing Item:
v SIP3130
2BE08301
2BE09010
Code. Explanation: Cache data associated with attached
Failing Item:
v STORIOA v SIP3120
2BE08302 2BE09011
those attached.
v NEXTLVL

2BE09020 • 2BE09032
2BE09020 2BE09027
Explanation: Two or more disk units missing from Explanation: Array not functional due to parity out of
RAID-5 or RAID-6 array. synchronization.
Failing Item: Response: Array is or would become exposed and
v SIP3111 parity data is out of synchronization.
Failing Item:
2BE09021 v SIP3113
RAID-5 or RAID-6 array. 2BE09028
Failing Item: Explanation: Maximum number of functional arrays
v SIP3111 has been exceeded.
Response: Reduce the number of arrays on this I/O
2BE09022 adapter. Either move all the devices in an array to
Explanation: Two or more disk units missing from array on this I/O adapter.
Failing Item:
Failing Item:
v SVCDOCS
v SIP3111
2BE09029
2BE09023
Explanation: One or more array members not in members has been exceeded.
Failing Item:
Failing Item:
v SIP3112
v NEXTLVL
2BE09024
2BE09030
with another array. Explanation: Array no longer protected due to
Failing Item:
Failing Item:
v NEXTLVL
v SIP3110
v FI02112
2BE09025
2BE09031
exposed. Response: Either a previous rebuild was interrupted
Failing Item:
v SIP3110 for other reference codes and take action on them.
v FI02112
2BE09032
2BE09026
Explanation: Disk unit not found at required physical failed.
location.
Response: A previously exposed disk unit in an array unit should be replaced.
Failing Item:
v NEXTLVL v FI02112

2BE09040 • 2BE09076
2BE09040 2BE09055
Explanation: Re-synchronization of array parity was Explanation: Write cache data is available for attached
initiated. storage IOA.
Response: No action required. Response: No service action required.
2BE09041 2BE09070
Explanation: Background array parity check detected Explanation: System log entry only. No service action
and corrected errors. required.
the problem. 2BE09071
Failing Item: Explanation: Link from IOA to auxiliary or remote
v NEXTLVL IOA is operational.
2BE09042
Explanation: Background parity check corrected errors 2BE09072
on disk unit. Explanation: Link from IOA to auxiliary or remote
Response: Call your next level of support to report IOA is non-operational.
the problem. Response: No service action required.
Failing Item:
v NEXTLVL 2BE09073
Explanation: Multiple I/O adapters connected in a not
2BE09050 valid configuration.
Explanation: Required cache data not found for one or Failing Item:
more disk units. v SIP4140
Failing Item:
v SIP3131 2BE09074
2BE09051 valid configuration.
Explanation: Cache data exists for one or more Response: Multiple I/O adapters not capable of
missing or failed devices. similar functions or controlling the same set of devices.
v SIP3132 v SIP4141
2BE09052 2BE09075
Explanation: Cache data exists for one or more Explanation: Incomplete multipath connection
modified devices. between IOA and remote IOA.
v NEXTLVL
2BE09076
2BE09054 Explanation: Missing auxiliary IOA or remote IOA.
Explanation: IOA resources not available due to Failing Item:
previous problems. v SIP4147
Failing Item:
v SIP3121

2BE09081 • 2BE13000

2BE09081
Failing Item: level of support.
v STORIOA v SVCDOCS
2BE09082 2BE09092
Explanation: Device error. Explanation: Disk unit requires initialization before
Failing Item: use.
v STORIOA v SIP3134
2BE09083 2BE09500
Explanation: System log entry only. No service action Explanation: Internal program error in driver code.
required.
Failing Item:
v PTFSRCH
2BE09084
Explanation: System log entry only. No service action 2BE09903
required.
2BE09090
Explanation: Disk unit has been modified after the 2BE0C000
last known status.
I/O adapter. Other resources attached to the virtual Response: No action is required. This reference code
I/O processor may then need to be Varied On. is logged for information only.

reference code to resolve the problem. 2BE0C402
If you cannot resolve the problem, contact your next Explanation: Licensed Internal Code error.
v PTFSRCH
2BE09091
Explanation: Incorrect hardware configuration change 2BE0FF3D
detected. Explanation: I/O adapter detected a recoverable error.
Response: Use Hardware Service Manager to re-IPL Failing Item:
I/O adapter. Other resources attached to the virtual v STORIOA
I/O processor may then need to be Varied On. v ANYBRDG
(2BE1) Reference codes

2BE11310
them.
Response: The I/O adapter error log is being filled 2BE13000

2BE13020 • 2BE13401

2BE13100
Response: If you are working with one of the card
types below, the adapter has multiple physical parts.
Choose the card type to identify the physical parts of Failing Item:
the storage adapter. v SIP4150
Card type 2BE1 (feature RAID enablement card for
embedded IOA) read the following: When working the 2BE13140
FRUs from the serviceable event or the failing item list
here, the embedded storage adapter (failing item Explanation: System log entry only. No service action
STORIOA) has three physical parts: required.
v The embedded storage adapter on the I/O
backplane. 2BE13202
v The RAID enablement card. Explanation: Storage subsystem configuration error.
v The Battery charger and carrier card.
v See symbolic FRU FEATCRD for the location codes configuration. An I/O processor might be required.
of the FRUs if they are not listed in the serviceable
event or if you are working the failing item list here. Failing Item:
v SVCDOCS
Card type 57CB (embedded IOA with 2BCF battery
card for embedded IOA) read the following: When
working the FRUs from the serviceable event or the 2BE13400
failing item list here, the embedded storage adapter Explanation: Unknown resource error.
(failing item STORIOA) has two physical parts:
Response: For card type 2BE1 (feature RAID
enablement card for embedded IOA) read the
backplane.
following: When working the FRUs from the
v The Battery charger and carrier card. serviceable event or the failing item list here, the
v See symbolic FRU FEATCRD for the location codes embedded storage adapter (failing item STORIOA) has
of the FRUs if they are not listed in the serviceable three physical parts:
event or if you are working the failing item list here. 1. The embedded storage adapter on the I/O
backplane.
Card type 57CF (embedded IOAs on DASD backplane 2. The RAID enablement card.
with 2BC2 dual battery charger and carrier card for the
embedded IOAs) read the following: When working 3. The Battery charger and carrier card.
the FRUs from the serviceable event or the failing item 4. See symbolic FRU FEATCRD for the location codes
list here, the embedded storage adapter (failing item of the FRUs if they are not listed in the serviceable
STORIOA) has two physical parts: event or if you are working the failing item list
v The embedded storage adapter on the DASD here.
backplane. Failing Item:
v The dual battery charger and carrier card. To v SIP4150
determine which battery is connected to which
v FI02112
embedded IOA use the bus number of the IOA with
symbolic FRU CACHBAT. v STORIOA
v See symbolic FRU FEATCRD for the location code of v SASCABL
the dual battery charger and carrier card if it is not
listed in the serviceable event or if you are working 2BE13401
the failing item list here.
Failing Item:
Failing Item:
v STORIOA
v SASEXP
v ANYBRDG
v DEVBPLN
2BE13020
Failing Item:
v SIP4150

2BE13405 • 2BE14100
v SIP4144
2BE13405
2BE14040
Failing Item:
problems.
v Check the device firmware level and apply the latest 2BE14041
PTFs.

multipath function.
2BE134FF Failing Item:
logged for information only. 2BE14060
2BE13601
required.
Failing Item:
v SIP4153
2BE14010
v SASCABL
enclosures. 2BE14061
v SIP3142
2BE14020
Explanation: Configuration error. 2BE14070
Failing Item:
v SIP3143 2BE14100
2BE14030 Response: For card type 2BE1 (feature RAID
Explanation: Configuration error. enablement card for embedded IOA) read the
following: When working the FRUs from the
Response: Incorrect multipath connection. serviceable event or the failing item list here, the
Failing Item:

2BE14101 • 2BE14160
embedded storage adapter (failing item STORIOA) has v See symbolic FRU FEATCRD for the location codes
three physical parts: of the FRUs if they are not listed in the serviceable
1. The embedded storage adapter on the I/O event or if you are working the failing item list here.
backplane.
2. The RAID enablement card.
3. The Battery charger and carrier card. working the FRUs from the serviceable event or the
failing item list here, the embedded storage adapter
See symbolic FRU FEATCRD for the location codes of (failing item STORIOA) has two physical parts:
the FRUs if they are not listed in the serviceable event
or if you are working the failing item list here.
backplane.
Failing Item: v The Battery charger and carrier card.
v SIP4152 v See symbolic FRU FEATCRD for the location codes
v SASCABL of the FRUs if they are not listed in the serviceable
v SASEXP event or if you are working the failing item list here.
v DEVBPLN
Card type 57CF (embedded IOAs on DASD backplane
v STORIOA with 2BC2 dual battery charger and carrier card for the
v FI01105 embedded IOAs) read the following: When working
the FRUs from the serviceable event or the failing item
list here, the embedded storage adapter (failing item
2BE14101 STORIOA) has two physical parts:
Explanation: Temporary device bus fabric error. v The embedded storage adapter on the DASD
backplane.
Failing Item:
v The dual battery charger and carrier card. To
v SIP4152
2BE14110 symbolic FRU CACHBAT.
Explanation: Unsupported enclosure function v See symbolic FRU FEATCRD for the location code of
detected. the dual battery charger and carrier card if it is not
listed in the serviceable event or if you are working
Failing Item: the failing item list here.
v SIP3145
Failing Item:
v BACKPLN
2BE14150
v STORIOA
Response: If this event appears in a serviceable event 2BE14160
PCI bus error.
If you are working with one of the card types below,
the adapter has multiple physical parts. Choose the
card type to identify the physical parts of the storage
adapter.
embedded IOA) read the following: When working the
adapter.
here, the embedded storage adapter (failing item
STORIOA) has three physical parts: Card type 2BE1 (feature RAID enablement card for
v The embedded storage adapter on the I/O embedded IOA) read the following: When working the
backplane. FRUs from the serviceable event or the failing item list
v The RAID enablement card.
STORIOA) has three physical parts:
backplane.

2BE170DD • 2BE18009
v The Battery charger and carrier card. card type to identify the physical parts of the storage
v See symbolic FRU FEATCRD for the location codes adapter.
of the FRUs if they are not listed in the serviceable Card type 2BE1 (feature RAID enablement card for
event or if you are working the failing item list here. embedded IOA) read the following: When working the
Card type 57CB (embedded IOA with 2BCF battery here, the embedded storage adapter (failing item
card for embedded IOA) read the following: When STORIOA) has three physical parts:
working the FRUs from the serviceable event or the
backplane.
backplane. v The Battery charger and carrier card.
v The Battery charger and carrier card. v See symbolic FRU FEATCRD for the location codes
v See symbolic FRU FEATCRD for the location codes
event or if you are working the failing item list here.
card) read the following: When working the FRUs from
the serviceable event or the failing item list here, the
embedded storage adapter (failing item STORIOA) has
embedded IOAs) read the following: When working
two physical parts:
list here, the embedded storage adapter (failing item v The embedded storage adapter on the I/O
STORIOA) has two physical parts: backplane.
v The embedded storage adapter on the DASD v The Battery charger and carrier card.
backplane. v See symbolic FRU FEATCRD for the location codes
v The dual battery charger and carrier card. To of the FRUs if they are not listed in the serviceable
determine which battery is connected to which event or if you are working the failing item list here.
symbolic FRU CACHBAT. Card type 57CF (embedded IOAs on DASD backplane
with 2BC2 dual battery charger and carrier card) read
v See symbolic FRU FEATCRD for the location code of
the following: When working the FRUs from the
serviceable event or the failing item list here, the
two physical parts:
Failing Item: v The embedded storage adapter on the DASD
v BACKPLN backplane.
v STORIOA v The dual battery charger and carrier card. To
2BE170DD
symbolic FRU CACHBAT.
Explanation: Disrupt device command completed v See symbolic FRU FEATCRD for the location code of
successfully. the dual battery charger and carrier card if it is not
2BE18008 the failing item list here.
Explanation: A permanent failure has occurred in the Failing Item:

cache battery pack or capacitive cache power card. v CACHBAT
Response: Under a certain configuration, this SRC v STORIOA
may not represent an error that requires a service v FEATCRD
2BE18009
attachment of OEM Storage that emulates a Load Explanation: Impending failure in the cache battery
Source drive. If this is the case, this error will be posted pack or capacitive cache power card.
Failing Item:
If you are working with one of the card types below, v CACHBAT

2BE18100 • 2BE18150
2BE18100 2BE18130
Explanation: Licensed Internal Code error. Explanation: IOA detected recoverable device bus
error.
types below, the adapter has multiple physical parts. Response: If this event appears in a serviceable event
Choose the card type to identify the physical parts of view, work with the failing item list found there. If this
the storage adapter. event does not appear in a serviceable event view, no
embedded IOA) read the following: When working the Failing Item:
FRUs from the serviceable event or the failing item list v SIP4150
2BE18140
backplane. Explanation: IOA detected recoverable device bus
v The RAID enablement card. error.
v The Battery charger and carrier card. Response: If this event appears in a serviceable event
v See symbolic FRU FEATCRD for the location codes view, work with the failing item list found there. If this
of the FRUs if they are not listed in the serviceable event does not appear in a serviceable event view, no
event or if you are working the failing item list here. service action is required.
Failing Item:
v SIP4150
failing item list here, the embedded storage adapter 2BE18141
backplane. Response: No action is required. This reference code
v The Battery charger and carrier card. is logged for information only.

of the FRUs if they are not listed in the serviceable 2BE18145
Card type 57CF (embedded IOAs on DASD backplane Response: This error is logged against the storage
with 2BC2 dual battery charger and carrier card for the controller resource. Contact your next level of support
embedded IOAs) read the following: When working to determine the part number and location code of the
the FRUs from the serviceable event or the failing item device.
Failing Item:
STORIOA) has two physical parts:
v NEXTLVL
v The embedded storage adapter on the DASD
backplane.
v The dual battery charger and carrier card. To 2BE18146
determine which battery is connected to which Explanation: Disk device detected recoverable error.
symbolic FRU CACHBAT. Failing Item:
v See symbolic FRU FEATCRD for the location code of v FI01105
Failing Item:
v PTFSRCH Response: Under a certain configuration, this SRC

2BE18151 • 2BE18155
If you are working with one of the card types below, Card type 2BE1 (feature RAID enablement card for
the adapter has multiple physical parts. Choose the embedded IOA) read the following: When working the
card type to identify the physical parts of the storage FRUs from the serviceable event or the failing item list
adapter. here, the embedded storage adapter (failing item
embedded IOA) read the following: When working the v The embedded storage adapter on the I/O
FRUs from the serviceable event or the failing item list backplane.
here, the embedded storage adapter (failing item v The RAID enablement card.
STORIOA) has three physical parts: v The Battery charger and carrier card.
v The embedded storage adapter on the I/O v See symbolic FRU FEATCRD for the location codes
backplane. of the FRUs if they are not listed in the serviceable
v The RAID enablement card. event or if you are working the failing item list here.
card for embedded IOA) read the following: When v The embedded storage adapter on the I/O
working the FRUs from the serviceable event or the backplane.
failing item list here, the embedded storage adapter v The Battery charger and carrier card.
(failing item STORIOA) has two physical parts: v See symbolic FRU FEATCRD for the location codes
v The embedded storage adapter on the I/O of the FRUs if they are not listed in the serviceable
backplane. event or if you are working the failing item list here.
embedded IOAs) read the following: When working v The embedded storage adapter on the DASD
the FRUs from the serviceable event or the failing item backplane.
list here, the embedded storage adapter (failing item v The dual battery charger and carrier card. To
STORIOA) has two physical parts: determine which battery is connected to which
v The embedded storage adapter on the DASD embedded IOA use the bus number of the IOA with
backplane. symbolic FRU CACHBAT.
v The dual battery charger and carrier card. To v See symbolic FRU FEATCRD for the location code of
determine which battery is connected to which the dual battery charger and carrier card if it is not
embedded IOA use the bus number of the IOA with listed in the serviceable event or if you are working
symbolic FRU CACHBAT. the failing item list here.
v See symbolic FRU FEATCRD for the location code of Failing Item:
the dual battery charger and carrier card if it is not v PTFSRCH
v STORIOA
Failing Item:
2BE18155
v STORIOA
v ANYBRDG
2BE18151
Choose the card type to identify the physical parts of
Explanation: Licensed Internal Code error. the storage adapter.
Response: If you are working with one of the card Card type 2BE1 (feature RAID enablement card for
types below, the adapter has multiple physical parts. embedded IOA) read the following: When working the
Choose the card type to identify the physical parts of FRUs from the serviceable event or the failing item list
the storage adapter. here, the embedded storage adapter (failing item

2BE18156 • 2BE18157
STORIOA) has three physical parts: v The RAID enablement card.

v The embedded storage adapter on the I/O v The Battery charger and carrier card.
v The RAID enablement card. of the FRUs if they are not listed in the serviceable
v The Battery charger and carrier card. event or if you are working the failing item list here.
working the FRUs from the serviceable event or the v The embedded storage adapter on the I/O
failing item list here, the embedded storage adapter backplane.
(failing item STORIOA) has two physical parts: v The Battery charger and carrier card.
the FRUs from the serviceable event or the failing item v The embedded storage adapter on the DASD
list here, the embedded storage adapter (failing item backplane.
STORIOA) has two physical parts: v The dual battery charger and carrier card. To
v The embedded storage adapter on the DASD determine which battery is connected to which
backplane. embedded IOA use the bus number of the IOA with
determine which battery is connected to which v See symbolic FRU FEATCRD for the location code of
embedded IOA use the bus number of the IOA with the dual battery charger and carrier card if it is not
symbolic FRU CACHBAT. listed in the serviceable event or if you are working
the dual battery charger and carrier card if it is not Failing Item:
listed in the serviceable event or if you are working v PTFSRCH
v STORIOA
Failing Item:
v PTFSRCH 2BE18157
v STORIOA
Explanation: I/O adapter card error. The actions and
2BE18156 based on the conditions this event was logged for.
Explanation: A permanent failure occurred. Response: The FRU list in the Service Action Log will
vary based on the conditions this event was logged for.
Choose the card type to identify the physical parts of 1. Display the Service Action Log entry for this SRC.
the storage adapter. 2. If the Failing Item indicates SVCDOCS, then
recoverable error.
here, the embedded storage adapter (failing item v LIC will automatically re-IPL the virtual I/O
STORIOA) has three physical parts: processor associated with the adapter. Other
backplane.

2BE18300
v If the virtual I/O processor or adapter are not v See symbolic FRU FEATCRD for the location code of
operational then use Hardware Service Manager the dual battery charger and carrier card if it is not
to manually re-IPL the virtual I/O processor and listed in the serviceable event or if you are working
Vary On attached resources. the failing item list here.
v If manually reIPL-ing the virtual I/O processor Problem determination: Perform the following:
ends the procedure.
replace the I/O adapter. Check the list below to
determine if the adapter type you are replacing has
recoverable error.
multiple physical parts.
If you are replacing the I/O adapter and you are processor associated with the adapter. Other
working with one of the card types below, the adapter resources attached to the virtual I/O processor
has multiple physical parts. Choose the card type to may need to be Varied On.
identify the physical parts of the storage adapter. v If the virtual I/O processor or adapter are not
Card type 2BE1 (feature RAID enablement card for to manually re-IPL the virtual I/O processor and
embedded IOA) read the following: When working the Vary On attached resources.
FRUs from the serviceable event or the failing item list v If manually reIPL-ing the virtual I/O processor
here, the embedded storage adapter (failing item fails then contact your next level of support. This
STORIOA) has three physical parts: ends the procedure.
v The embedded storage adapter on the I/O 3. If the Failing Item indicates an I/O adapter, then
backplane. contact your next level of support to replace the
v The RAID enablement card. I/O adapter.
v The Battery charger and carrier card. Failing Item:
v See symbolic FRU FEATCRD for the location codes v SVCDOCS
v STORIOA
Card type 57CB (embedded IOA with 2BCF battery 2BE18300

failing item list here, the embedded storage adapter Response: If you are working with one of the card
(failing item STORIOA) has two physical parts: types below, the adapter has multiple physical parts.
v The embedded storage adapter on the I/O Choose the card type to identify the physical parts of
backplane. the storage adapter.
v The Battery charger and carrier card. Card type 2BE1 (feature RAID enablement card for
v See symbolic FRU FEATCRD for the location codes embedded IOA) read the following: When working the
of the FRUs if they are not listed in the serviceable FRUs from the serviceable event or the failing item list
event or if you are working the failing item list here. here, the embedded storage adapter (failing item
Card type 57CF (embedded IOAs on DASD backplane v The embedded storage adapter on the I/O
with 2BC2 dual battery charger and carrier card for the backplane.
embedded IOAs) read the following: When working v The RAID enablement card.
STORIOA) has two physical parts: v See symbolic FRU FEATCRD for the location codes
backplane.
v The dual battery charger and carrier card. To Card type 57CB (embedded IOA with 2BCF battery
determine which battery is connected to which card for embedded IOA) read the following: When
embedded IOA use the bus number of the IOA with working the FRUs from the serviceable event or the
symbolic FRU CACHBAT. failing item list here, the embedded storage adapter
backplane.

2BE18301 • 2BE18302
v See symbolic FRU FEATCRD for the location codes of the FRUs if they are not listed in the serviceable
of the FRUs if they are not listed in the serviceable event or if you are working the failing item list here.
Card type 57CF (embedded IOAs on DASD backplane with 2BC2 dual battery charger and carrier card for the
with 2BC2 dual battery charger and carrier card for the embedded IOAs) read the following: When working
embedded IOAs) read the following: When working the FRUs from the serviceable event or the failing item
the FRUs from the serviceable event or the failing item list here, the embedded storage adapter (failing item
list here, the embedded storage adapter (failing item STORIOA) has two physical parts:
STORIOA) has two physical parts: v The embedded storage adapter on the DASD
v The embedded storage adapter on the DASD backplane.
backplane. v The dual battery charger and carrier card. To
v The dual battery charger and carrier card. To determine which battery is connected to which
determine which battery is connected to which embedded IOA use the bus number of the IOA with
embedded IOA use the bus number of the IOA with symbolic FRU CACHBAT.
symbolic FRU CACHBAT. v See symbolic FRU FEATCRD for the location code of
v See symbolic FRU FEATCRD for the location code of the dual battery charger and carrier card if it is not
the dual battery charger and carrier card if it is not listed in the serviceable event or if you are working
listed in the serviceable event or if you are working the failing item list here.
the failing item list here. Failing Item:
Failing Item: v PTFSRCH
v STORIOA v STORIOA
v ANYBRDG
v PTFSRCH 2BE18302
2BE18301
Explanation: Not valid condition in Licensed Internal this I/O adapter is loaded.
Code.
Response: If you are working with one of the card the adapter has multiple physical parts. Choose the
types below, the adapter has multiple physical parts. card type to identify the physical parts of the storage
Choose the card type to identify the physical parts of adapter.
the storage adapter.
Card type 2BE1 (feature RAID enablement card for embedded IOA) read the following: When working the
embedded IOA) read the following: When working the FRUs from the serviceable event or the failing item list
FRUs from the serviceable event or the failing item list here, the embedded storage adapter (failing item
here, the embedded storage adapter (failing item STORIOA) has three physical parts:
STORIOA) has three physical parts: v The embedded storage adapter on the I/O
v The embedded storage adapter on the I/O backplane.
backplane. v The RAID enablement card.
v The RAID enablement card. v The Battery charger and carrier card.
Card type 57CB (embedded IOA with 2BCF battery card for embedded IOA) read the following: When
card for embedded IOA) read the following: When working the FRUs from the serviceable event or the
working the FRUs from the serviceable event or the failing item list here, the embedded storage adapter
failing item list here, the embedded storage adapter (failing item STORIOA) has two physical parts:
(failing item STORIOA) has two physical parts: v The embedded storage adapter on the I/O

2BE18400 • 2BE19008
v See symbolic FRU FEATCRD for the location codes Card type 57CB (embedded IOA with 2BCF battery
of the FRUs if they are not listed in the serviceable card for embedded IOA) read the following: When
event or if you are working the failing item list here. working the FRUs from the serviceable event or the
Card type 57CF (embedded IOAs on DASD backplane (failing item STORIOA) has two physical parts:
with 2BC2 dual battery charger and carrier card for the v The embedded storage adapter on the I/O
embedded IOAs) read the following: When working backplane.
STORIOA) has two physical parts: v See symbolic FRU FEATCRD for the location codes
backplane.
v The dual battery charger and carrier card. To Card type 57CF (embedded IOAs on DASD backplane
determine which battery is connected to which with 2BC2 dual battery charger and carrier card for the
embedded IOA use the bus number of the IOA with embedded IOAs) read the following: When working
symbolic FRU CACHBAT. the FRUs from the serviceable event or the failing item
v See symbolic FRU FEATCRD for the location code of list here, the embedded storage adapter (failing item
the dual battery charger and carrier card if it is not STORIOA) has two physical parts:
listed in the serviceable event or if you are working v The embedded storage adapter on the DASD
the failing item list here. backplane.
Failing Item: v The dual battery charger and carrier card. To
v SVCDOCS determine which battery is connected to which
v STORIOA
2BE18400 the dual battery charger and carrier card if it is not
Explanation: Licensed Internal Code error. listed in the serviceable event or if you are working
Failing Item:
Failing Item:
v PTFSRCH
v FI01105
v STORIOA
2BE18404
Explanation: System log entry only. No service action 2BE19001
required.
Explanation: Device error. v NEXTLVL

types below, the adapter has multiple physical parts. 2BE19002
Choose the card type to identify the physical parts of Explanation: Device error.
Failing Item:
v NEXTLVL
here, the embedded storage adapter (failing item 2BE19008
v The embedded storage adapter on the I/O expected by devices.
backplane.
Failing Item:
v SIP3130

2BE19010 • 2BE19030

2BE19010
exposed.
Failing Item:
v SIP3110
Failing Item:
v FI02112
v SIP3120
2BE19026
2BE19011
Explanation: Disk unit not found at required physical
Explanation: Cache data belongs to devices other than location.
those attached.
Response: A previously exposed disk unit in an array
Failing Item: was not found at the required physical location.
v NEXTLVL
Failing Item:
v NEXTLVL
2BE19020
Explanation: Two or more disk units missing from 2BE19027
Failing Item: synchronization.
v SIP3111
Response: Array is or would become exposed and
parity data is out of synchronization.
2BE19021
Failing Item:
Explanation: Two or more disk units missing from v SIP3113
v SIP3111
Explanation: Maximum number of functional arrays
has been exceeded.
2BE19022
Explanation: Two or more disk units missing from adapter. Either move all the devices in an array to
RAID-5 or RAID-6 array. another I/O adapter that supports arrays, or stop an
Failing Item:
v SVCDOCS
2BE19023
2BE19029
required physical locations. Explanation: Maximum number of functional array
Failing Item:
v SIP3112 Response: Contact your next level of support.
Failing Item:
2BE19024 v NEXTLVL
with another array. 2BE19030
v NEXTLVL missing or failed disk unit.
Failing Item:
2BE19025 v SIP3110
Explanation: Incompatible device. v FI02112

2BE19031 • 2BE19073
2BE19031 2BE19051
Explanation: Automatic rebuild initiated for array. Explanation: Cache data exists for one or more
missing or failed devices.
and was automatically restarted, or a hot spare disk Failing Item:
unit was used to automatically rebuild the array. Look v SIP3132
2BE19052
2BE19032
Explanation: A disk unit in an array is missing or modified devices.
failed.
unit should be replaced. Failing Item:
v NEXTLVL
Failing Item:
v SIP3110
2BE19054
v FI02112
previous problems.
2BE19040
Failing Item:
Explanation: Re-synchronization of array parity was
initiated. v SIP3121
Response: No action required.

2BE19055
2BE19041 Explanation: Write cache data is available for attached

storage IOA.
and corrected errors. Response: No service action required.

the problem. 2BE19070

required.
v NEXTLVL
2BE19071
2BE19042
IOA is operational.
on disk unit.
the problem.
2BE19072
Failing Item:
v NEXTLVL Explanation: Link from IOA to auxiliary or remote
2BE19050 Response: No service action required.

more disk units. 2BE19073
Failing Item: Explanation: Multiple I/O adapters connected in a not

v SIP3131
Failing Item:
v SIP4140

2BE19074 • 2BE19082

2BE19074
Explanation: Multiple I/O adapters connected in a not embedded IOAs) read the following: When working
valid configuration. the FRUs from the serviceable event or the failing item
Response: Multiple I/O adapters not capable of
Failing Item: backplane.
v SIP4141 v The dual battery charger and carrier card. To
2BE19075 embedded IOA use the bus number of the IOA with
Explanation: Incomplete multipath connection v See symbolic FRU FEATCRD for the location code of
between IOA and remote IOA. the dual battery charger and carrier card if it is not
Failing Item: listed in the serviceable event or if you are working
v SIP4149
Failing Item:
2BE19076 v FI01105
v STORIOA
Failing Item:
2BE19082
v SIP4147
2BE19081 Response: If you are working with one of the card

Explanation: Device error. Choose the card type to identify the physical parts of
Response: If you are working with one of the card the storage adapter.
types below, the adapter has multiple physical parts. Card type 2BE1 (feature RAID enablement card for
Choose the card type to identify the physical parts of embedded IOA) read the following: When working the
the storage adapter. FRUs from the serviceable event or the failing item list
Card type 2BE1 (feature RAID enablement card for here, the embedded storage adapter (failing item
embedded IOA) read the following: When working the STORIOA) has three physical parts:
FRUs from the serviceable event or the failing item list v The embedded storage adapter on the I/O
here, the embedded storage adapter (failing item backplane.
STORIOA) has three physical parts: v The RAID enablement card.
v The embedded storage adapter on the I/O v The Battery charger and carrier card.
backplane.
v The RAID enablement card. of the FRUs if they are not listed in the serviceable
of the FRUs if they are not listed in the serviceable Card type 57CB (embedded IOA with 2BCF battery
event or if you are working the failing item list here. card for embedded IOA) read the following: When
Card type 57CB (embedded IOA with 2BCF battery failing item list here, the embedded storage adapter
card for embedded IOA) read the following: When (failing item STORIOA) has two physical parts:
working the FRUs from the serviceable event or the v The embedded storage adapter on the I/O
of the FRUs if they are not listed in the serviceable Card type 57CF (embedded IOAs on DASD backplane
event or if you are working the failing item list here. with 2BC2 dual battery charger and carrier card for the

2BE19083 • 2BE1FF3D
list here, the embedded storage adapter (failing item v SVCDOCS

v The embedded storage adapter on the DASD 2BE19092
backplane.
use.
embedded IOA use the bus number of the IOA with Failing Item:
symbolic FRU CACHBAT. v SIP3134
the failing item list here. Explanation: Internal program error in driver code.
v FI01105 v PTFSRCH
v STORIOA
2BE19903
2BE19083
Explanation: System log entry only. No service action Informational event, no service required.
required.
2BE1C000
2BE19084
Explanation: System log entry only. No service action required.
required.
2BE19090
Explanation: Disk unit has been modified after the 2BE1C402
last known status.
assistance.
I/O processor may then need to be Varied On. Failing Item:
If any reference codes are surfaced, use the new v PTFSRCH
If you cannot resolve the problem, contact your next 2BE1FF3D
level of support. Explanation: I/O adapter detected a recoverable error.
Failing Item: Response: If you are working with one of the card
v SVCDOCS types below, the adapter has multiple physical parts.
2BE19091
detected.
Response: Use Hardware Service Manager to re-IPL here, the embedded storage adapter (failing item
the virtual I/O processor that is associated with this STORIOA) has three physical parts:
I/O adapter. Other resources attached to the virtual v The embedded storage adapter on the I/O
I/O processor may then need to be Varied On. backplane.
If any reference codes are surfaced, use the new v The RAID enablement card.
reference code to resolve the problem. v The Battery charger and carrier card.
If you cannot resolve the problem, contact your next v See symbolic FRU FEATCRD for the location codes
level of support. of the FRUs if they are not listed in the serviceable
Failing Item:

2BF3A001 • 2C4DB9B0
Card type 57CB (embedded IOA with 2BCF battery list here, the embedded storage adapter (failing item
card for embedded IOA) read the following: When STORIOA) has two physical parts:
working the FRUs from the serviceable event or the v The embedded storage adapter on the DASD
v The embedded storage adapter on the I/O determine which battery is connected to which
v The Battery charger and carrier card. symbolic FRU CACHBAT.
v See symbolic FRU FEATCRD for the location codes v See symbolic FRU FEATCRD for the location code of
of the FRUs if they are not listed in the serviceable the dual battery charger and carrier card if it is not
event or if you are working the failing item list here. listed in the serviceable event or if you are working
Failing Item:
embedded IOAs) read the following: When working v STORIOA
the FRUs from the serviceable event or the failing item v ANYBRDG
(2BF3) Reference codes

2BF3A001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
2BF3B9B0
(2BF4) Reference codes

2BF4A001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
2BF4B9B0
(2C4C) Reference codes

2C4CA001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
2C4CB9B0
(2C4D) Reference codes

Failing Item:
2C4DA001
v AJDG301
detected.
2C4DB9B0

2CE3A001 • 2D343109
Explanation: I/O adapter hardware error detected. v IOA

Failing Item: v AJDG301
(2CE3) Reference codes

could not be updated. No service is required. This SRC
2CE3A001
is logged as informational.
detected.
2CE3B9B0
Failing Item:
v AJDG301
Failing Item:
v IOA
2CE3A6F6
v AJDG301
(2CE4) Reference codes

2CE4A001
detected.
2CE4B9B0
Failing Item:
v AJDG301
Failing Item:
v IOA
2CE4A6F6
v AJDG301
(2CEC) Reference codes

2CECA001
detected.
2CECB9B0
Failing Item:
v AJDG301
Failing Item:
v IOA
2CECA6F6
v AJDG301
(2D34) Reference codes

Failing Item:
2D343002
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
failure. Verify that input power to the expansion unit 2D343109
input power to the expansion unit failed the expansion Explanation: I/O adapter timed out a device
unit was not able to log a reference code for the input backplane command.
power failure. Restore power to the expansion unit and Failing Item:
v SASEXP

2D348404 • 2D35FFF4
v SASCABL Explanation: Device backplane problem.

v DEVBPLN v SASEXP
v SASCABL
2D348404 v STORIOA
required.
2D34FFF4

Failing Item:
2D353002
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
failure. Verify that input power to the expansion unit 2D358404
close the xxxx3002 problems. Otherwise work the 2D35FFF4
Failing Item:
Failing Item:
v SASEXP
v SASEXP
v SASCABL
v SASCABL
v STORIOA
v STORIOA
v DEVBPLN
v DEVBPLN
2D353109
backplane command.

A tape or tape library device failure occurred.
Note: Use this table to handle reference codes that might be displayed during a type D IPL to install the
operating system. If you are not performing a type D IPL of the operating system, consult any error logs
that you find in the serviceable event view. If you cannot locate an error log in the serviceable event view
that corresponds with the failure, run a verification test for the tape unit.
1. Verify that the device has power.
2. Check the 3494 Library Manager console for error indications. Refer to the 3494 service information to
resolve any error indications.
3. Attempt the failing operation again.
4. Does the operation complete successfully?
Yes: The problem has been corrected. This ends the procedure.
No: Look at the 4 rightmost characters of the Data display for Function 11, which represents the
unit reference code. Find the unit reference code in the following table.

34942301 • 34942321
Information and follow the procedures for analyzing a

34942301
"LIBRARY MANAGER HARDWARE PROBLEM".
Explanation: Library device failure.
Failing Item:
Response: Library attachment facility equipment v LIB3494
check.
Use the 3494 Tape Library Dataserver Maintenance 34942309
"LIBRARY PROBLEM - NO ERROR MESSAGE." Explanation: Library device failure.
Failing Item: Response: Library equipment check.

v LIB3494 Use the 3494 Tape Library Dataserver Maintenance
"LIBRARY PROBLEM - NO ERROR MESSAGE."
34942303
Failing Item:
v LIB3494
Response: Device control unit and library manager
Licensed Internal Code are incompatible.
34942310
Use the 3494 Tape Library Dataserver Maintenance
Information and follow the procedures for analyzing a Explanation: Library device requires operator
"LIBRARY PROBLEM - NO ERROR MESSAGE." intervention.
Failing Item: Response: Put the library into pause mode and
perform the intervention indicated on the library
v LIB3494
manager console.
34942306
34942311
Explanation: Library device requires operator
Response: Library vision failure. intervention.
Use the 3494 Tape Library Dataserver Maintenance Response: Put the library into pause mode and
Information and follow the procedures for analyzing a perform the intervention indicated on the library
"LIBRARY PROBLEM - NO ERROR MESSAGE." manager console.
Failing Item:
v LIB3494 34942319
Explanation: Tape unit failure.
34942307 Response: Use the tape unit service information to
Explanation: Library device failure. analyze the failure.
Response: Library vision failure. Failing Item:

v FI00851
Use the 3494 Tape Library Dataserver Maintenance
"LIBRARY PROBLEM - NO ERROR MESSAGE." 34942321
Failing Item: Explanation: Library enclosure environmental alert
v LIB3494 was detected.
Response: Use the 3494 Tape Library Dataserver
34942308 Maintenance Information and follow the procedures for
analyzing a "LIBRARY PROBLEM - NO ERROR
Explanation: Library device failure. MESSAGE."
Response: Library manager equipment check. Failing Item:
Use the 3494 Tape Library Dataserver Maintenance v LIB3494


35803000 • 35809101
found in the serviceable event view. If you cannot locate an error log in the serviceable event view that
corresponds with the failure, run a verification test for the tape unit.
2. Check the device for any error indications. Refer to the device service information to resolve any error
indications.
3. Clean the recording head in the tape device.
4. Attempt the failing operation again. Does the operation complete successfully?
Yes: You have corrected the problem. This ends the procedure.
No: Look at the 8 rightmost characters of the Data display for Function 11, which represent the
reference code. Find the reference code in the following list.
v FI00871
35803000
v PTFSRCH
v FI01112
Explanation: Interface error detected by system or by
tape unit.
35803202
Response: If the attached device is an external device,
Explanation: Tape unit configuration error. do the following before exchanging any parts:
Response: Before exchanging any parts, verify that the 1. Ensure that the signal cable is seated correctly, and
following condition is not present: that there are no bent or damaged pins on the cable.
v The attached device type or model is only 2. For a SCSI attached device ensure that a
supported on an I/O adapter that is attached to an terminating plug is attached to the device end of
I/O processor. the cable.
Failing Item: If the attached tape device is owned by a Virtual I/O

v TAPCNFG Server partition refer to Troubleshooting the Virtual
v FI00871 I/O Server to determine the parts to replace.
Failing Item:
35803400 v FI00871
Explanation: Device error has occurred. v FI01112
v FI00872
Failing Item:
v DEVTERM
v FI00872
v DEVTERM
35809101
v FI00871
v FI01103 Explanation: Fibre Channel interface error detected.
v FI01106 Response: If the attached device is an external device,
do the following before exchanging any parts:
35809020 1. Ensure that the Fibre Channel cable is correctly
connected to the ports.
Explanation: Tape unit configuration error.
2. Clean the Fibre Channel connectors.
Response: Before exchanging any parts, verify that the 3. If there is a switch or hub attached, verify that it is
following conditions are not present: operational.
v Tape and DASD devices attached to an I/O 4. If there is a gateway device attached, refer to the
Processor that does not support Tape and Dasd gateway device service documentation for
devices at the same time. additional problem analysis procedures.
v An unsupported device type or model is attached. 5. refer to the tape device service documentation for
Failing Item: additional problem analysis procedures.
v TAPCNFG

35809102 • 35809202
If the attached tape device is owned by a Virtual I/O v USB_IOA

Server partition refer to Troubleshooting the Virtual v USB_CBL
I/O Server to determine the parts to replace.
v FCIOA
Explanation: Tape unit is not responding.
v FCDEV
v FCCABLE
1. Ensure that the device is powered on.
35809102
2. Ensure that the signal cable is seated correctly, and
Explanation: Gateway device detected a SCSI interface that there are no bent or damaged pins on the cable.
error. 3. For a SCSI attached device ensure that a
Response: Use the gateway device service terminating plug is attached to the device end of
documentation to analyze the problem. the SCSI cable.

v FI00871 Server partition refer to Troubleshooting the Virtual
v FCGATE I/O Server to determine the parts to replace.
v DEVTERM v FI00871
v FI01112
35809103 v FI00872
Explanation: Interface error detected by system or by v DEVTERM
tape unit.
Response: If the attached device is an external tape 35809201
device, do the following before exchanging any parts: Explanation: Tape unit command timeout.
1. Ensure that the SAS cable is correctly connected to
the ports.
2. Ensure that the device has power.
If the attached tape device is owned by a Virtual I/O 2. If an interposer is required, make sure that it is
Server partition refer to Troubleshooting the Virtual connected between the I/O processor and the SCSI
I/O Server to determine the parts to replace. cable.
Failing Item:
that there are no bent or damaged pins on the SCSI
v FI00871 cable.
v FI01112 4. Ensure that a terminating plug is attached to the
v SASCABL device end of the SCSI cable.
5. If the attached tape device is owned by a Virtual
35809104 I/O Server partition it may be necessary to reset the
virtual IOP to recover from the error.
tape unit. Failing Item:
v FI00871
Response: If the attached device is an external tape
device, do the following before exchanging any parts: v FI01112
1. Ensure that the USB cable is correctly connected to v FI00872

the ports. v DEVTERM
2. Ensure that the device has power. v MEDIA
If the attached tape device is owned by a Virtual I/O 35809202

Server partition refer to Troubleshooting the Virtual
I/O Server to determine the parts to replace. Explanation: Tape unit failed after Licensed Internal
Code was loaded.
Failing Item:
v USB_DEV Response: If the attached device is an external device,

35809210 • 35809304

35809221
Explanation: I/O path change occurred.
2. If an interposer is required, make sure that it is
connected between the I/O processor and the SCSI Response: No action required. This reference code is
cable. logged for information only.
3. Ensure that the SCSI cable is seated correctly, and
that there are no bent or damaged pins on the SCSI 35809300
cable.
4. Ensure that a terminating plug is attached to the
device end of the SCSI cable. Failing Item:
v FI00871
v FI01112 35809301
v FI00872 Explanation: Tape device failure, redundancy lost.
v DEVTERM Response: The tape unit detected a hardware failure
that does not prevent the tape unit from completing the
35809210 current operation.
Explanation: Illegal or unsupported tape unit Failing Item:

response. v FI00871
Failing Item:
v FI00871 35809302
v FI01112 Explanation: Tape device failure or media error.
v PTFSRCH Response: The tape unit detected a failure that may
be caused by a hardware failure or a media error.
35809211 Refer to the tape unit service information for possible
Explanation: Gateway device detected a bus protocol information on diagnositic tests that can be run to
error. isolate between hardware and media failures.
Response: Use the gateway device service Failing Item:

documentation to analyze the problem. v MEDIA
v FCGATE
v FCIOA 35809303
v FI00871 Explanation: Gateway device failure.
v ANYFC Response: Use the gateway device service
v FCCABLE documenation to analyze the problem.
v DEVTERM v FCGATE
35809220 35809304
Explanation: Hardware configuration change detected. Explanation: Tape unit failure.
Response: The tape device or tape library device has Response: Before exchanging any parts, do the
reported a configuration change that requires the I/O following:
processor to be reset. Reset the I/O processor before
using the device. 1. Ensure that the EKM/TKLM server is operational
and properly configured.
2. Ensure that the mounted cartridge is in the
EKM/TKLM server database.
Failing Item:
v USER

35809310 • 35809802
v FI00871
35809355
Explanation: The data format is incorrect; the tape
35809310
cannot be read.
Explanation: Licensed Internal Code for the tape unit
Response: The tape unit has detected that the data
is not correct.
format on the tape media is not supported or that the
Failing Item: tape media is defective. Do the following before
v PTFSRCH exchanging any parts:
v FI00871 1. Initialize the tape to a different format.
2. Clean the tape unit.
35809320
If the operation continues to fail, use a different tape
Explanation: Tape device Licensed Internal Code cartridge.
failure.
Failing Item:
v FI00130 v MEDIA
v FI00871 v TAPCLN
v FI00871
35809321
Explanation: Gateway device Licensed Internal Code 35809500
error.
Response: Use the gateway device service
Response: If the system is operational, perform a
documenation to analyze the problem.
dump of the I/O processor data.
Failing Item:
Failing Item:
v FCCODE
v PTFSRCH
35809350
35809501
Explanation: Tape unit detected a read or write error
on tape medium.
Failing Item:
Response: A permanent read or write error occurred.
Clean the tape unit and retry the operation. v PTFSRCH
If cleaning the tape unit does not correct the problem,

exchange the tape media. 35809800
Failing Item: Explanation: System successfully recovered from

temporary I/O error.
v MEDIA
v TAPCLN Response: No action required. This reference code is
v FI00871
35809801
35809351
Explanation: System successfully recovered from
Explanation: Tape with excessive error rate was
mounted in tape device.
Response: The tape unit detected that the mounted
tape cartridge has a history of excessive read and write
errors. It is recommended that you exchange the tape
cartridge. 35809802
v MEDIA temporary I/O error.
v FI00871 logged for information only.

35809803 • 3580FFF6
or the problem was corrected.

35809803
35809900
Explanation: Licensed Internal Code for tape unit was
not upgraded.
Response: The I/O processor loading of Licensed
Internal Code (LIC) to the programmable tape unit was
35809804
not completed.
The tape unit will continue to operate with the
previous LIC. You may do either of the following:
Response: No action required. This reference code is v Wait for next IPL when the system will attempt to
logged for information only. load the LIC for the tape drive again.
v Perform TUPIP04 to reset the IOP and the tape unit.
35809805 When the IOP is reset, if the device has the wrong
level of LIC, the IOP will attempt to load the new
LIC.
Failing Item:
logged for information only. v USER
35809806 35809901
Explanation: System successfully recovered from Explanation: Tape performance statistics logged.
temporary I/O error. Response: No action required. This reference code is
Response: No action required. This reference code is logged for information only.
35809902
35809810 Explanation: An IOP dump was initiated.
Explanation: Problem analysis has determined a part Response: No action required.
should be replaced.
Response: This reference code is used for ending 35809903
Online Problem Analysis with a list of failing items.
(Information Only.) Explanation: Tape device information logged.
Explanation: Problem analysis completed, the problem

has been corrected. 3580FFF6
Response: This reference code is used for ending Explanation: Tape volume statistics logged (no action
Online Problem Analysis when no problem was found required).

indications.

35923000 • 35929102
35923000
that there are no bent or damaged pins on the cable.
Explanation: I/O adapter hardware error detected. 2. For a SCSI attached device ensure that a
Failing Item: terminating plug is attached to the device end of
the cable.
v FI01112
If the attached tape device is owned by a Virtual I/O
35923202 Server partition refer to Troubleshooting the Virtual
Failing Item:
Response: Before exchanging any parts, verify that the
following condition is not present: v FI00871
v The attached device type or model is only v FI01112
supported on an I/O adapter that is attached to an v FI00872
I/O processor. v DEVTERM
Failing Item:
v TAPCNFG 35929101
35923400 do the following before exchanging any parts:
Explanation: Device error has occurred. 1. Ensure that the Fibre Channel cable is correctly
Failing Item:
v FI00872
3. If there is a switch or hub attached, verify that it is
v DEVTERM
operational.
v FI00871
4. If there is a gateway device attached, refer to the
v FI01103 gateway device service documentation for
v FI01106 additional problem analysis procedures.
5. refer to the tape device service documentation for
35929020 additional problem analysis procedures.
Explanation: Tape unit configuration error. If the attached tape device is owned by a Virtual I/O
Response: Before exchanging any parts, verify that the Server partition refer to Troubleshooting the Virtual
following conditions are not present: I/O Server to determine the parts to replace.
v Tape and DASD devices attached to an I/O Failing Item:

Processor that does not support Tape and Dasd v FCIOA
devices at the same time.
v FCDEV
v An unsupported device type or model is attached.
v FCCABLE
Failing Item:
v TAPCNFG 35929102
v FI00871
Explanation: Gateway device detected a SCSI interface
v PTFSRCH error.
35929100 documentation to analyze the problem.
Explanation: Interface error detected by system or by Failing Item:
tape unit.
v FI00871
Response: If the attached device is an external device, v FCGATE

35929103 • 35929202

v DEVTERM v FI00871
v FI01112
35929103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871

Code was loaded.
Failing Item:
v USB_IOA
v USB_CBL
connected between the I/O processor and the SCSI
35929200 cable.
Explanation: Tape unit is not responding. 3. Ensure that the SCSI cable is seated correctly, and
Response: If the attached device is an external device, cable.
1. Ensure that the device is powered on. device end of the SCSI cable.
Failing Item:
v FI00871
3. For a SCSI attached device ensure that a
terminating plug is attached to the device end of v FI01112
the SCSI cable. v FI00872
v DEVTERM

35929210 • 35929320
35929210 35929302
Explanation: Illegal or unsupported tape unit Explanation: Tape device failure or media error.
response.
Response: The tape unit detected a failure that may
Failing Item: be caused by a hardware failure or a media error.
v FI00871 Refer to the tape unit service information for possible
v FI01112 information on diagnositic tests that can be run to
v PTFSRCH isolate between hardware and media failures.
Failing Item:
35929211 v MEDIA
Explanation: Gateway device detected a bus protocol v FI00871
error.
Response: Use the gateway device service 35929303
documentation to analyze the problem. Explanation: Gateway device failure.
Failing Item: Response: Use the gateway device service
v FCGATE documenation to analyze the problem.
v FI00871 v FCGATE
v ANYFC
v FCCABLE 35929304
v FI00872
v DEVTERM
Response: Before exchanging any parts, do the
following:
35929220
1. Ensure that the EKM/TKLM server is operational
Explanation: Hardware configuration change detected. and properly configured.
Response: The tape device or tape library device has 2. Ensure that the mounted cartridge is in the
reported a configuration change that requires the I/O EKM/TKLM server database.
processor to be reset. Reset the I/O processor before Failing Item:
using the device.
v USER
v FI00871
35929221
Explanation: I/O path change occurred. 35929310
Response: No action required. This reference code is Explanation: Licensed Internal Code for the tape unit
logged for information only. is not correct.
Failing Item:
35929300
v PTFSRCH
Explanation: Tape unit failure. v FI00871
Failing Item:
v FI00871 35929320
Explanation: Tape device Licensed Internal Code
35929301 failure.
Explanation: Tape device failure, redundancy lost. Failing Item:
Response: The tape unit detected a hardware failure v FI00130
that does not prevent the tape unit from completing the v FI00871
current operation.
Failing Item:
v FI00871

35929321 • 35929804
v FI00871
35929321
Explanation: Gateway device Licensed Internal Code
35929500
error.
documenation to analyze the problem. Response: If the system is operational, perform a
Failing Item:
v FCCODE Failing Item:
v PTFSRCH
35929350
35929501
on tape medium. Explanation: Licensed Internal Code error.
Response: A permanent read or write error occurred. Failing Item:
35929351 35929801
Explanation: Tape with excessive error rate was Explanation: System successfully recovered from
mounted in tape device. temporary I/O error.
Response: The tape unit detected that the mounted Response: No action required. This reference code is
tape cartridge has a history of excessive read and write logged for information only.
cartridge.
35929802
Failing Item:
v TAPCLN
35929355 35929803
Explanation: The data format is incorrect; the tape Explanation: System successfully recovered from
cannot be read. temporary I/O error.
Response: The tape unit has detected that the data Response: No action required. This reference code is
format on the tape media is not supported or that the logged for information only.
tape media is defective. Do the following before
exchanging any parts:
1. Initialize the tape to a different format. 35929804
2. Clean the tape unit. Explanation: System successfully recovered from

If the operation continues to fail, use a different tape Response: No action required. This reference code is
cartridge. logged for information only.
Failing Item:
v USER
v MEDIA
v TAPCLN

35929805 • 3592FFF6
35929805 35929902
Explanation: System successfully recovered from Explanation: An IOP dump was initiated.
35929903
Explanation: Tape device information logged.
35929806
3592FFF6
Explanation: Tape volume statistics logged (no action
required).
35929810
Explanation: Problem analysis has determined a part
should be replaced.
Response: This reference code is used for ending
(Information Only.)
35929899
has been corrected.
Online Problem Analysis when no problem was found
35929900
not upgraded.
not completed.
v Wait for next IPL when the system will attempt to
load the LIC for the tape drive again.
When the IOP is reset, if the device has the wrong
LIC.
Failing Item:
v USER
35929901
Explanation: Tape performance statistics logged.

4320102E • 43207000

v DISKDRV
4320102E
v STORIOA
v FI01106
v DISKDRV
43203109
43203002
Failing Item:
selection.
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v FI01106
v STORIOA
v FI01140
v BACKPLN
v FI01106
43203110
v FI01140
Explanation: Disk bus interface error occurred.

v DSKIP03
IOA. v STORIOA
v DISKDRV
Failing Item:
v FI01106
v DISKDRV
v FI01140
v STORIOA
v FI01140
43203130
v FI01141
43203020 Response: The device is not supported with the level
level of support.
Failing Item:
configuration.
v SVCDOCS
Failing Item:
v DISKDRV
43203131
v FI01106
Explanation: Device or IOA Licensed Internal Code.
v STORIOA
v FI01140 Response: The device does not support a needed
attribute and is running with degraded performance.
Contact your next level of support.
43203029
Failing Item:
v SVCDOCS
43207000
Explanation: Recoverable disk sector read error.
43203100
Explanation: Tape/optical or disk bus interface error
occurred.
If this reference code appears in a serviceable event
Failing Item:
view then service is required, work the faling items list.
v DSKIP03 Otherwise this event can be ignored.

43207001 • 4320FFFA

v DISKDRV service action is required.
Failing Item:
43207001 v DISKDRV
4320FFF6
view, work with the failing item list found there. If this Explanation: Disk device detected recoverable error.
Failing Item:
43207003 v DISKDRV
Explanation: Device format error.
4320FFF7
Response: If the disk has not been formatted by the
system, initialize and format the disk. See Work with Explanation: Temporary disk data error.
disk unit recovery.
43207004
Explanation: System log entry only. No service action view then service is required, work the faling items list.
required. Otherwise this event can be ignored.
Failing Item:
432070DD v DISKDRV
required. 4320FFF8
4320FFF2
Explanation: Disk motor problem. view, work with the failing item list found there. If this
v DISKDRV
Failing Item:
4320FFF3 v DISKDRV

4320FFF9
Failing Item:
v DISKDRV
4320FFF4
Explanation: Disk device problem. service action is required.
v DISKDRV v DISKDRV
v STORIOA
4320FFFA
4320FFF5 Explanation: Temporary disk bus error.
Explanation: Disk sector read error. Response: If this event appears in a serviceable event

4320FFFB • 43223110
Failing Item: Explanation: Temporary disk bus error.

v FI01140 event does not appear in a serviceable event view, no
v FI01141
v DISKDRV
4320FFFB v STORIOA
v FI01106
Explanation: SCSI bus reset occurred.
v FI01140
4320FFFE

v STORIOA
4322102E
v FI01140
v DISKDRV
43223002
selection.
43223100
Failing Item:
v DISKDRV occurred.
v STORIOA
Failing Item:
v BACKPLN
v DSKIP03
v FI01106
v DISKDRV
v FI01140
v STORIOA
v FI01106
43223010
v FI01140
IOA.
43223109
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v FI01140
v STORIOA
v FI01141
v FI01106
v FI01140
43223020
43223110
configuration.
Failing Item:
Failing Item:
v DSKIP03
v DISKDRV
v STORIOA
v FI01106
v DISKDRV

43223130 • 4322FFF7
v FI01106
43227004
v FI01140
required.
43223130
Explanation: Device Licensed Internal Code. 432270DD
Response: The device is not supported with the level Explanation: System log entry only, no service action
of code currently on the system. Contact your next required.
level of support.
Failing Item: 4322FFF2
v SVCDOCS
Explanation: Disk motor problem.
Failing Item:
43223131
v DISKDRV
Response: The device does not support a needed 4322FFF3
Contact your next level of support. Explanation: Disk media format not valid.

v SVCDOCS v DISKDRV
43227000 4322FFF4
Explanation: Recoverable disk sector read error. Explanation: Disk device problem.

logged for information only. v DISKDRV
If this reference code appears in a serviceable event v STORIOA
Otherwise this event can be ignored. 4322FFF5
Failing Item: Explanation: Disk sector read error.
v DISKDRV
Failing Item:
service action is required. 4322FFF6
Failing Item: Explanation: Disk device detected recoverable error.
v DISKDRV
Failing Item:
system, initialize and format the disk. See Work with v DISKDRV
disk unit recovery.
4322FFF7

4322FFF8 • 43233029
If this reference code appears in a serviceable event view, work with the failing item list found there. If this
view then service is required, work the faling items list. event does not appear in a serviceable event view, no
Otherwise this event can be ignored. service action is required.
v DISKDRV v DISKDRV
v STORIOA
4322FFF8 v FI01140
Explanation: Temporary disk data error. v FI01141
v BACKPLN
event does not appear in a serviceable event view, no 4322FFFB
Failing Item:
v DISKDRV logged for information only.
4322FFF9 4322FFFE
Explanation: Temporary disk data error. Explanation: Temporary disk bus error.
v DISKDRV v DISKDRV
v STORIOA
4322FFFA v FI01106
Explanation: Temporary disk bus error. v FI01140

Failing Item:
4323102E
v DISKDRV
v STORIOA
v DISKDRV v FI01141
43233002 43233020
Explanation: Addressed device failed to respond to Explanation: Storage subsystem configuration error.
selection.
Failing Item: configuration.
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v BACKPLN
v FI01106
v FI01106
v STORIOA
v FI01140
v FI01140
43233010
43233029
IOA.

43233100 • 4323FFF3

43237000
43233100 Response: No action required. This reference code is
occurred. If this reference code appears in a serviceable event
Failing Item:
Otherwise this event can be ignored.
v DSKIP03
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
v FI01106
43237001
v FI01140
43233109 Response: If this event appears in a serviceable event
v STORIOA v DISKDRV
v FI01106
v FI01140 43237003
43233110
Explanation: Disk bus interface error occurred. system, initialize and format the disk. See Work with
Failing Item: disk unit recovery.
v DSKIP03
v STORIOA 43237004
v DISKDRV Explanation: System log entry only. No service action

v FI01106 required.
v FI01140
432370DD
required.
Response: The device is not supported with the level 4323FFF2
level of support. Explanation: Disk motor problem.
v SVCDOCS v DISKDRV
43233131 4323FFF3
Explanation: Device or IOA Licensed Internal Code. Explanation: Disk media format not valid.
Response: The device does not support a needed Failing Item:
attribute and is running with degraded performance. v DISKDRV
Failing Item:
v SVCDOCS

4323FFF4 • 43253002
v DISKDRV
4323FFF4
4323FFF9
Failing Item:
v DISKDRV
v STORIOA
Response: If this event appears in a serviceable event v DISKDRV
event does not appear in a serviceable event view, no 4323FFFA
Failing Item:
v DISKDRV
view, work with the failing item list found there. If this v STORIOA
event does not appear in a serviceable event view, no v FI01140
v FI01141
Failing Item: v BACKPLN
v DISKDRV
4323FFFB
4323FFF7
If this reference code appears in a serviceable event 4323FFFE
Failing Item:
Response: If this event appears in a serviceable event v STORIOA
view, work with the failing item list found there. If this v FI01106
Failing Item:

v DISKDRV
4325102E
43253002
Failing Item:

43253010 • 43257001
Explanation: Addressed device failed to respond to v STORIOA

selection. v FI01106
v DISKDRV
v STORIOA 43253110
v BACKPLN Explanation: Disk bus interface error occurred.
v FI01106
Failing Item:
v FI01140
v DSKIP03
v STORIOA
43253010
v DISKDRV
Explanation: Disk device returned wrong response to v FI01106
IOA.
v FI01140
Failing Item:
v DISKDRV 43253130
v STORIOA
v FI01140
v FI01141
level of support.
43253020
Failing Item:
Explanation: Storage subsystem configuration error. v SVCDOCS
configuration. 43253131
Failing Item: Explanation: Device or IOA Licensed Internal Code.
v DISKDRV
Response: The device does not support a needed
v FI01106 attribute and is running with degraded performance.
v STORIOA Contact your next level of support.
v SVCDOCS
43253029
Explanation: A device replacement has occurred. 43257000
Response: No action required. This reference code is Explanation: Recoverable disk sector read error.
43253100
Explanation: Tape/optical or disk bus interface error view then service is required, work the faling items list.
occurred. Otherwise this event can be ignored.
v DSKIP03 v DISKDRV
v DISKDRV
v STORIOA 43257001
v FI01106 Explanation: Temporary disk data error.
v FI01140
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV

43257003 • 4325FFFB
v DISKDRV
43257003
4325FFF7
system, initialize and format the disk. See Work with
disk unit recovery. Response: No action required. This reference code is
43257004 If this reference code appears in a serviceable event
required.
Failing Item:
432570DD v DISKDRV

required. 4325FFF8
4325FFF2 Response: If this event appears in a serviceable event
v DISKDRV
Failing Item:
v DISKDRV
4325FFF3
Explanation: Disk media format not valid. 4325FFF9
Failing Item: Explanation: Temporary disk data error.
v DISKDRV
4325FFF4 event does not appear in a serviceable event view, no
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
4325FFFA
Response: If this event appears in a serviceable event event does not appear in a serviceable event view, no
view, work with the failing item list found there. If this service action is required.
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v FI01140
v FI01141
4325FFF6
v BACKPLN
Response: If this event appears in a serviceable event 4325FFFB
event does not appear in a serviceable event view, no Explanation: SCSI bus reset occurred.
service action is required. Response: No action required. This reference code is

4325FFFE • 43263131
Failing Item:
4325FFFE
v DISKDRV
v STORIOA
Response: If this event appears in a serviceable event v FI01106
v FI01140

4326102E 43263100
Explanation: Out of alternate sectors for disk storage. Explanation: Tape/optical or disk bus interface error
occurred.
Failing Item:
v DSKIP03
43263002 v DISKDRV
v STORIOA
v FI01140
Failing Item:
v DISKDRV
43263109
v STORIOA
v BACKPLN Explanation: IOA timed out a disk command.
v FI01140 v DISKDRV
v STORIOA
43263010 v FI01106
IOA.
v DISKDRV Explanation: Disk bus interface error occurred.
v FI01140 v DSKIP03
v FI01141 v STORIOA
v DISKDRV
43263020 v FI01106
Failing Item: Explanation: Device Licensed Internal Code.
v DISKDRV Response: The device is not supported with the level
v FI01106 of code currently on the system. Contact your next
v STORIOA level of support.
v SVCDOCS
43263029
Response: No action required. This reference code is Explanation: Device or IOA Licensed Internal Code.
logged for information only. Response: The device does not support a needed

43267000 • 4326FFF9

4326FFF4
Failing Item:
v DISKDRV
43267000 v STORIOA

4326FFF5
logged for information only. Explanation: Disk sector read error.
If this reference code appears in a serviceable event Response: If this event appears in a serviceable event
view then service is required, work the faling items list. view, work with the failing item list found there. If this
Otherwise this event can be ignored. event does not appear in a serviceable event view, no
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
43267001
4326FFF6
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
43267003
4326FFF7
system, initialize and format the disk. See Work with Response: No action required. This reference code is
disk unit recovery. logged for information only.
43267004 view then service is required, work the faling items list.
v DISKDRV
432670DD
4326FFF8
required. Explanation: Temporary disk data error.
4326FFF2 view, work with the failing item list found there. If this
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
4326FFF3
4326FFF9
Failing Item:

4326FFFA • 43273109

4326FFFB
Failing Item:
4326FFFA
4326FFFE
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v FI01140
v FI01106
v FI01141
v FI01140
v BACKPLN

Failing Item:
4327102E
v DISKDRV
v FI01106
v DISKDRV v FI01140
43273002 43273029
Explanation: Addressed device failed to respond to Explanation: A device replacement has occurred.
selection.
v DISKDRV
v STORIOA 43273100
v BACKPLN
v FI01106 occurred.
v FI01140
Failing Item:
v DSKIP03
43273010
v DISKDRV
IOA.
v FI01106
v DISKDRV
v STORIOA 43273109
v FI01140
v FI01141
Failing Item:
v DISKDRV
43273020
v STORIOA
v FI01106
Response: If an MES is being installed, verify the v FI01140
configuration.

43273110 • 4327FFF6
43273110 43277003
Explanation: Disk bus interface error occurred. Explanation: Device format error.
Failing Item: Response: If the disk has not been formatted by the
v DSKIP03 system, initialize and format the disk. See Work with
disk unit recovery.
v STORIOA
v DISKDRV
43277004
v FI01106
v FI01140 Explanation: System log entry only. No service action
required.
43273130
432770DD
Response: The device is not supported with the level required.
level of support.
4327FFF2
Failing Item:
v SVCDOCS
Failing Item:
43273131 v DISKDRV

4327FFF3
attribute and is running with degraded performance. Explanation: Disk media format not valid.
Contact your next level of support. Failing Item:
v SVCDOCS
4327FFF4
43277000 Explanation: Disk device problem.
Explanation: Recoverable disk sector read error. Failing Item:
view then service is required, work the faling items list. 4327FFF5
Failing Item:
v DISKDRV
event does not appear in a serviceable event view, no 4327FFF6
Failing Item:
v DISKDRV
Failing Item:

4327FFF7 • 43283020

Failing Item:
v DISKDRV
v STORIOA
Otherwise this event can be ignored. v FI01140
v FI01141
Failing Item:
v BACKPLN
v DISKDRV
4327FFFB
4327FFF8
service action is required. 4327FFFE
Failing Item:
v DISKDRV
service action is required. v FI01106
v DISKDRV
4327FFFA

4328102E 43283010
Explanation: Out of alternate sectors for disk storage. Explanation: Disk device returned wrong response to
IOA.
Failing Item:
v DISKDRV
43283002 v STORIOA
v FI01140
Failing Item:
43283020
v DISKDRV
v STORIOA Explanation: Storage subsystem configuration error.
v BACKPLN Response: If an MES is being installed, verify the
v FI01106 configuration.

43283029 • 4328FFF2
v DISKDRV
43283131
v FI01106
v STORIOA
43283029
Failing Item:
v SVCDOCS
43287000
43283100
occurred.
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v FI01106
v FI01140
43287001
43283109

v FI01106 v DISKDRV
v FI01140
43287003
43283110 Explanation: Device format error.
Explanation: Disk bus interface error occurred. Response: If the disk has not been formatted by the
Failing Item: system, initialize and format the disk. See Work with
disk unit recovery.
v DSKIP03
v STORIOA
43287004
v DISKDRV
required.
v FI01140
432870DD
43283130
Explanation: Device Licensed Internal Code. required.
of code currently on the system. Contact your next 4328FFF2
level of support.
Failing Item:
v DISKDRV

4328FFF3 • 4328FFFE
4328FFF3 4328FFF9
Explanation: Disk media format not valid. Explanation: Temporary disk data error.
4328FFF4
Failing Item:
v DISKDRV
Failing Item:
v DISKDRV 4328FFFA
v STORIOA
4328FFF5
Explanation: Disk sector read error. event does not appear in a serviceable event view, no
v STORIOA
v DISKDRV v FI01141
v BACKPLN
4328FFF6
Explanation: Disk device detected recoverable error. 4328FFFB
Response: If this event appears in a serviceable event Explanation: SCSI bus reset occurred.
Failing Item:
4328FFFE
v DISKDRV

Response: No action required. This reference code is service action is required.
If this reference code appears in a serviceable event v DISKDRV
view then service is required, work the faling items list. v STORIOA
v FI01106
v DISKDRV
4328FFF8
Failing Item:
v DISKDRV

4329102E • 43297000

v DISKDRV
4329102E
v STORIOA
v FI01106
v DISKDRV
43293109
43293002
Failing Item:
selection.
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v FI01106
v STORIOA
v FI01140
v BACKPLN
v FI01106
43293110
v FI01140

v DSKIP03
IOA. v STORIOA
v DISKDRV
Failing Item:
v FI01106
v DISKDRV
v FI01140
v STORIOA
v FI01140
43293130
v FI01141
level of support.
Failing Item:
configuration.
v SVCDOCS
Failing Item:
v DISKDRV
43293131
v FI01106
v STORIOA
43293029
Failing Item:
v SVCDOCS
43297000
43293100
occurred.
Failing Item:

43297001 • 4329FFFA

Failing Item:
43297001 v DISKDRV
4329FFF6
Failing Item:
43297003 v DISKDRV
4329FFF7
disk unit recovery.
43297004
Failing Item:
432970DD v DISKDRV
required. 4329FFF8
4329FFF2
v DISKDRV
Failing Item:
4329FFF3 v DISKDRV

4329FFF9
Failing Item:
v DISKDRV
4329FFF4
v DISKDRV v DISKDRV
v STORIOA
4329FFFA

4329FFFB • 433B310D

v FI01141
v DISKDRV
4329FFFB v STORIOA
v FI01106
v FI01140
4329FFFE

433B102E 433B3029
Explanation: Out of alternate sectors for disk storage. Explanation: A device replacement has occurred.
Failing Item: Response: No action required. This reference code is
433B3002 433B3100
Explanation: Addressed device failed to respond to Explanation: Device bus interface error occurred.
selection. Failing Item:
v DISKDRV v STORIOA
v STORIOA v SASCABL
v DEVBPLN v SASEXP
v SASCABL
v SASEXP 433B3109
433B3010
Failing Item:
Explanation: Disk device returned wrong response to v DISKDRV
IOA.
v STORIOA
v DISKDRV v SASEXP
v STORIOA
v SASCABL 433B310C
v SASEXP
Failing Item:
433B3020
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA 433B310D
v SASCABL
Failing Item:

433B3110 • 433BFFF5
v SIP3250
433B4100
v DISKDRV
v STORIOA
Failing Item:
433B3110 v SIP3152
v SASCABL
v SASEXP
Failing Item:
v DEVBPLN
v DISKDRV
v STORIOA
v STORIOA
v DISKDRV
v SASCABL
v SASEXP
433B7000
433B3130
433B7001
level of support.
Failing Item:
v SVCDOCS Response: If this event appears in a serviceable event
433B34FF service action is required.
433B70DD
433B4041
Explanation: Incomplete multipath connection. required.

device backplane and device. 433BFFF3
Failing Item: Explanation: Disk media format not valid.
v DISKDRV
433B4060
Explanation: Multipath redundancy level reduced. 433BFFF4
Response: A redundant disk unit connection has Explanation: Disk device problem.
failed.
Failing Item:
v SIP3153 v STORIOA
v SASCABL
v SASEXP 433BFFF5
433B4061
Response: A redundant disk unit connection has been event does not appear in a serviceable event view, no
restored. No service action is required. service action is required.
Failing Item:

433BFFF6 • 433BFFFE
v DISKDRV
433BFFFC
433BFFF6
Failing Item:
v SIP3250
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
433BFFF7
433BFFFD
Failing Item:
Failing Item:
v DISKDRV
v SIP3250
v DISKDRV
433BFFF9
v STORIOA
Response: If this event appears in a serviceable event 433BFFFE
service action is required. Response: If this event appears in a serviceable event
Failing Item:
Failing Item:
433BFFFA
v SIP3150
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
433BFFFB

433C102E • 433C34FF

433C102E 433C3109
v DISKDRV v DISKDRV
v STORIOA
433C3002 v SASCABL
selection.
Failing Item: 433C310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
433C3010 433C310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
433C3110
433C3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
433C3130
433C3029
Failing Item:
433C3100
v SVCDOCS
Failing Item: 433C34FF
v STORIOA
v SASEXP

433C4041 • 433CFFF9
433C4041 433C70DD
required.
433CFFF3
Failing Item:
Failing Item:
433C4060 v DISKDRV
433CFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
433CFFF5
433C4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
433CFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
433C7000
Explanation: Disk sector read error. 433CFFF7
433C7001 event does not appear in a serviceable event view, no

433CFFF9
Failing Item:
v DISKDRV

433CFFFA • 433CFFFE

433CFFFE
Failing Item:
433CFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
433CFFFB
433CFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
433CFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

433D102E • 433D34FF

433D102E 433D3109
v DISKDRV v DISKDRV
v STORIOA
433D3002 v SASCABL
selection.
Failing Item: 433D310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
433D3010 433D310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
433D3110
433D3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
433D3130
433D3029
Failing Item:
433D3100
v SVCDOCS
Failing Item: 433D34FF
v STORIOA
v SASEXP

433D4041 • 433DFFF9
433D4041 433D70DD
required.
433DFFF3
Failing Item:
Failing Item:
433D4060 v DISKDRV
433DFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
433DFFF5
433D4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
433DFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
433D7000
Explanation: Disk sector read error. 433DFFF7
433D7001 event does not appear in a serviceable event view, no

433DFFF9
Failing Item:
v DISKDRV

433DFFFA • 433DFFFE

433DFFFE
Failing Item:
433DFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
433DFFFB
433DFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
433DFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA


46853000 • 46859101
indications.
v FI00871
46853000
v PTFSRCH
v FI01112
tape unit.
46853202

Failing Item:
46853400 v FI00871
v FI00872
Failing Item:
v DEVTERM
v FI00872
v DEVTERM
46859101
v FI00871
v TAPCNFG

46859102 • 46859202

v FCIOA
v FCDEV
v FCCABLE
46859102

v DEVTERM v FI00871
v FI01112
46859103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871


Code was loaded.
Failing Item:

46859210 • 46859304

46859221
cable.
v FI00871
v FI01112 46859301

response. v FI00871
Failing Item:
v FI00871 46859302

v FCGATE
v FCIOA 46859303
v DEVTERM v FCGATE
46859220 46859304
Failing Item:
v USER

46859310 • 46859802
v FI00871
46859355
46859310
cannot be read.
is not correct.
46859320
failure.
Failing Item:
v FI00130 v MEDIA
v FI00871 v TAPCLN
v FI00871
46859321
error.
Failing Item:
Failing Item:
v FCCODE
v PTFSRCH
46859350
46859501
on tape medium.
Failing Item:


v MEDIA
v FI00871
46859801
46859351
cartridge. 46859802

46859803 • 4758B992

46859803
46859900
not upgraded.
46859804
not completed.
LIC.
Failing Item:
46859806 46859901
46859902
should be replaced.


Explanation: Tampering of cryptographic card
4758B990
suspected.
Failing Item:
Failing Item: v IOA
v IOA v FI00130
v FI00130 v IOP
v IOP
v MA_BRDG 4758B992
Explanation: Operating voltage and/or temperature
4758B991 range limits exceeded.

4764B990 • 4765B992
Response: Correct any conditions in the physical description associated with the 4758 adapter card.
environment which may have caused the voltage
Failing Item:
and/or temperature out-of-range error on the 4758
adapter card. After the conditions have been corrected, v CARDTMP
vary off and then vary back on the 4758 device

4764B990 4764B992
Explanation: I/O adapter hardware error detected. Explanation: Operating voltage and/or temperature
range limits exceeded.
Failing Item:
v IOA Response: Correct any conditions in the physical
v AJDG301
and/or temperature out-of-range error on the 4764 /
4765 adapter card. After the conditions have been
4764B991 corrected, vary off and then vary back on the 4764 /
4765 device description associated with the 4764 / 4765
Explanation: Tampering of cryptographic card adapter card.
suspected.
Failing Item:
Failing Item:
v CARDTMP
v IOA
v AJDG301

v AJDG301
4765B990
4765B991
Response: If the secondary code for this error is
Explanation: Tampering of cryptographic card
F0F08038 do not work the failing item list unless you
suspected.
are directed to by your next level of support. This ends
the procedure. Failing Item:
Problem determination: Perform the following steps: v IOA
1. Go to SST/DST. v AJDG301
2. View this error in the Product Activity Log (PAL) or
the Service Action Log (SAL) under Hardware 4765B992
Service Manager.
Explanation: Operating voltage and/or temperature
3. Is the secondary code F0F08038? range limits exceeded.
v No - There is no additional problem
determination. This ends the procedure. Response: Correct any conditions in the physical
v Yes - Certain cryptographic coprocessor cards of and/or temperature out-of-range error on the 4764 /
type 4765 may not function correctly in certain 4765 adapter card. After the conditions have been
I/O enclosures. In order to avoid intermittent corrected, vary off and then vary back on the 4764 /
errors Licensed Internal Code (LIC) prevents an 4765 device description associated with the 4764 / 4765
affected 4765 card from being used when it is adapter card.
installed in an I/O enclosure where it may not
function correctly. This PAL entry was made with Failing Item:
SRC 4765B990 and secondary code F0F08038 v CARDTMP
because LIC detected that the card may not
function correctly in the I/O enclosure it is
installed in. The location code of the 4765 card
will be listed in the SAL. If you see this error
contact IBM customer support to resolve this
issue. This ends the procedure.
Failing Item:
v IOA

48126201 • 48126502

v FI00730
48126201
48126225
occurred.
Failing Item:
occurred.
v IOA
Failing Item:
v FI00730
v FI00730
v AJDG301
48126202
v IOA
error.
48126226
Failing Item:
v FI00730
v IOA Failing Item:
v AJDG301
48126204 v AS4NTDD
v FI00584
Explanation: I/O adapter failure due to a thermal
condition.
48126227
Failing Item:
v IOA Explanation: Windows initiated a warm boot.
Failing Item:
48126210 v NTUSER
Explanation: I/O processor Licensed Internal Code v FI00730
error. v IOA
Failing Item:
v FI00730 48126228
Explanation: I/O processor resource not available. v FI00730
Failing Item: v IOA
v AJDG301
v DISKIMG 48126501
Explanation: A permanent I/O processor failure v IOA
occurred. v FI00730
Failing Item:
v FI00730 48126502
v IOA Explanation: A Windows fatal error occurred.
Failing Item:
48126223
v FI00730
Explanation: A permanent I/O processor failure v IOA
occurred.
Failing Item:
v IOA

48126530 • 4812653D
48126530 48126538
v NTVSCSI v NTVSCSI
v NTOPSYS v NTOPSYS
48126531 48126539
v NTVSCSI v NTVSCSI
v AS4NTDD v AS4NTDD
v NTOPSYS v NTOPSYS
v FI00730 v FI00730
48126532 4812653A
v NTOPSYS v NTOPSYS
v FI00730 v FI00730
v AS4NTDD v AS4NTDD
48126533 4812653B
v NTUSER v NTUSER
v NTOPSYS v NTOPSYS
v AS4NTDD v AS4NTDD
48126534 4812653C
v AS4NTDD v AS4NTDD
v FI00730 v FI00730
v NTOPSYS v NTOPSYS
48126535 4812653D
v NTUSER v NTUSER
v NTDEVDR v NTDEVDR
v FI00730 v FI00730

4812653F • 4812B4BE
4812653F 4812B4B0
Explanation: A Virtual SCSI error was detected. Explanation: I/O adapter hardware error detected.
v NTDEVDR v IOA
v NTOPSYS
v AJDG301 4812B4B1
48126540
Failing Item:
Explanation: A Virtual SCSI error was detected. v IOA
Failing Item: v MEMORY
v NTVSCSI
v FI00730 4812B4B4
v AJDG301 Explanation: I/O adapter hardware error detected.
Failing Item:
48126541
v IOA
Explanation: A permanent I/O processor failure v MEMORY
occurred.
v IOA
v FI00730
Failing Item:
v FI00730
48126542
v IOA
Explanation: Licensed Internal Code error detected.
v AJDG301
v FI00730
Failing Item:
v MEMORY
48126543
v IOA
v NTOPSYS
v NTVSCSI
Failing Item:
v IOA
48126580
4812B4BC
Failing Item:
v NTOPSYS
Failing Item:
v NTVSCSI
v IOA
v DISKIMG
v IOA
4812B4BE
v FI00730
Failing Item:
v MEMORY
v IOA

4812B904 • 506D7624
4812B904 4812B960
Explanation: A permanent I/O processor failure Explanation: I/O processor Licensed Internal Code
occurred. error.
v FI00730 v FI00730
v IOA v IOP

506D1511
Failing Item:
supply 1.
v DEVBPLN
Failing Item:
v STORIOA
v DISKPWR
v FI01140
v DISKFAN
v FI01106
v FI01106
v DEVBPLN
506D3109
506D1515
backplane command.
Failing Item:
1.
v DEVBPLN
Failing Item:
v STORIOA
v DISKPWR
v FI01140
v DISKFAN
v FI01106
v FI01106
v DEVBPLN
506D7611
506D1521
1.
Failing Item:
supply 2.
v DISKFAN
Failing Item:
v DISKPWR
506D7614
v DISKFAN
v FI01106
v DISKFAN
506D1525
506D7621
2. Explanation: A fatal error occurred on redundant fan
2.
Failing Item:
v DISKPWR Failing Item:
v DISKFAN v DISKFAN
v FI01106
v DEVBPLN 506D7624
v DISKFAN

506D7631 • 506E7611
v DEVBPLN
506D7631
506D8404
3.
Failing Item:
required.
v DISKFAN
506DFFF4
506D7634
Failing Item:
Failing Item:
v DEVBPLN
v DISKFAN
v STORIOA
v FI01140
506D8401
v FI01106
Explanation: Removable media power fault.
Failing Item:

Failing Item:
506E1511
v DISKPWR
v DISKFAN
supply 1.
v FI01106
Failing Item:
v DEVBPLN
v DISKPWR
v DISKFAN
506E3002
v FI01106
v DEVBPLN
Failing Item:
506E1515
v DEVBPLN
v STORIOA
1.
v FI01140
Failing Item:
v FI01106
v DISKPWR
v DISKFAN
506E3109
v FI01106
v DEVBPLN
backplane command.
Failing Item:
506E1521
v DEVBPLN
v STORIOA
supply 2.
v FI01140
Failing Item:
v FI01106
v DISKPWR
v DISKFAN
506E7611
v FI01106
v DEVBPLN
1.
Failing Item:
506E1525
v DISKFAN
2.

506E7614 • 509A1525
506E7614 506E7634
Explanation: A fatal error occurred on fan 1. Explanation: A fatal error occurred on fan 3.
v DISKFAN v DISKFAN
506E7621 506E8401
Explanation: A fatal error occurred on redundant fan Explanation: Removable media power fault.
2.
Failing Item:
v DISKFAN
506E8404
506E7624
Explanation: A fatal error occurred on fan 2. required.
Failing Item:
v DISKFAN 506EFFF4
Explanation: A fatal error occurred on redundant fan v DEVBPLN
3. v STORIOA
v DISKFAN v FI01106
(509A) Reference codes

v SASEXP
509A1511
509A1521
supply 1.
Failing Item:
supply 2.
v DISKPWR
Failing Item:
v DEVBPLN
v DISKPWR
v SASEXP
v DEVBPLN
v SASEXP
509A1515
509A1525
1.
2.
to the I/O storage unit. The unit and power supply Problem determination: This SRC can be the result of
that detected the problem are in the FRU list of the a loss of utility power, battery back up or UPS power
serviceable event. Before starting a repair action for this to the I/O storage unit. The unit and power supply
problem verify that utility power, BBU or UPS to the that detected the problem are in the FRU list of the
unit was not interrupted at the time the SRC was serviceable event. Before starting a repair action for this
logged. If there was an interruption to power at about problem verify that utility power, BBU or UPS to the
the same time then no service is required and this unit was not interrupted at the time the SRC was
problem can be closed. logged. If there was an interruption to power at about
Failing Item:
v DISKPWR
Failing Item:
v DEVBPLN
v DISKPWR

509A3002 • 509AFFF4
v DEVBPLN condition. The fan should be replaced at the customer's

v SASEXP earliest convenience.
Failing Item:
509A3002 v DISKFAN
respond to selection. 509A7624
Problem determination: If there are multiple xxxx3002 Explanation: A fatal error occurred on fan 2.
Failing Item:
failure. Verify that input power to the expansion unit v DISKFAN
input power to the expansion unit failed the expansion 509A7633
power failure. Restore power to the expansion unit and Explanation: Fan 3 has failed or is operating below
close the xxxx3002 problems. Otherwise work the optimum. Enough redundant cooling capacity remains
xxxx3002 reference codes. in the I/O enclosure to avoid an over temperature
condition. The fan should be replaced at the customer's
Failing Item: earliest convenience.
v SASEXP
Failing Item:
v SASCABL
v DISKFAN
v STORIOA
v DEVBPLN
509A7634
509A3109 Explanation: A fatal error occurred on fan 3.
Explanation: I/O adapter timed out a device Failing Item:

backplane command. v DISKFAN
Failing Item:
v SASEXP 509A7643
v SASCABL Explanation: Fan 4 has failed or is operating below
v STORIOA optimum. Enough redundant cooling capacity remains
in the I/O enclosure to avoid an over temperature
v DEVBPLN condition. The fan should be replaced at the customer's
earliest convenience.
Explanation: Fan 1 has failed or is operating below v DISKFAN
optimum. Enough redundant cooling capacity remains
condition. The fan should be replaced at the customer's 509A7644
earliest convenience. Explanation: A fatal error occurred on fan 4.
v DISKFAN v DISKFAN
509A7614 509A8404
Explanation: A fatal error occurred on fan 1. Explanation: System log entry only, no service action
v DISKFAN
509AFFF4
509A7623 Explanation: Device backplane problem.
Explanation: Fan 2 has failed or is operating below Failing Item:
optimum. Enough redundant cooling capacity remains v SASEXP
v SASCABL

509D1511 • 50A41525
v STORIOA v DEVBPLN

509D1511
backplane command.
Failing Item:
supply 1.
v SASEXP
Failing Item:
v SASCABL
v DISKPWR
v STORIOA
v SASEXP
509D7614
509D1515
1. Failing Item:
v DISKFAN
Failing Item:
v DISKPWR
509D8404
v SASEXP
required.
509D3002
509DFFF4
Failing Item:
v SASCABL v SASEXP
v STORIOA v SASCABL
v STORIOA
509D3109

50A41511
Failing Item:
supply 1.
v DISKPWR
Failing Item:
v DEVBPLN
v DISKPWR
v SASEXP
v DEVBPLN
v SASEXP
50A41521
50A41515
supply 2.
Failing Item:
1.
v DISKPWR
v DEVBPLN
to the I/O storage unit. The unit and power supply v SASEXP
serviceable event. Before starting a repair action for this 50A41525
unit was not interrupted at the time the SRC was Explanation: A fatal error occurred on power supply
logged. If there was an interruption to power at about 2.

50A43002 • 50A4FFF4

50A47624
that detected the problem are in the FRU list of the Explanation: A fatal error occurred on fan 2.
Failing Item:
unit was not interrupted at the time the SRC was v DISKFAN
the same time then no service is required and this 50A47634
Failing Item:
v DEVBPLN v DISKFAN
v SASEXP
50A47644
50A43002 Explanation: A fatal error occurred on fan 4.
Explanation: Addressed device backplane failed to Failing Item:
respond to selection. v DISKFAN
reference codes logged from the same disk expansion 50A48404
failure. Verify that input power to the expansion unit Explanation: System log entry only, no service action
power supplies was active at the time of the error. If required.
unit was not able to log a reference code for the input 50A4FFF4
close the xxxx3002 problems. Otherwise work the Explanation: Device backplane problem.
xxxx3002 reference codes. Failing Item:
v SASEXP v SASCABL
v SASCABL v STORIOA
v STORIOA v DEVBPLN
v DEVBPLN
50A43109
backplane command.
Failing Item:
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
50A47614
Failing Item:
v DISKFAN

50AD1511 • 50AD7634
(50AD) Reference codes

v DEVBPLN
50AD1511
v SASEXP
supply 1.
50AD3002
Failing Item:
v DISKPWR
v DEVBPLN
v SASEXP
50AD1515 failure. Verify that input power to the expansion unit
1.
Failing Item:
v DEVBPLN
Failing Item:
50AD3109
v DISKPWR
v DEVBPLN
backplane command.
v SASEXP
Failing Item:
v SASEXP
50AD1521
v SASCABL
v STORIOA
supply 2.
v DEVBPLN
Failing Item:
v DISKPWR
50AD7614
v DEVBPLN
v SASEXP
Failing Item:
50AD1525 v DISKFAN

2. 50AD7624
problem verify that utility power, BBU or UPS to the 50AD7634
v DISKFAN
Failing Item:
v DISKPWR

50AD7644 • 50B13109
50AD7644 50ADFFF4
v DISKFAN v SASEXP
v SASCABL
50AD8404 v STORIOA
required.

50B11511
Failing Item:
Failing Item:
50B11515 v DISKPWR

1. v SASEXP
a loss of utility power, battery back up or UPS power 50B13002
Failing Item:
Failing Item:
50B11521 v SASEXP
supply 2. v STORIOA

v DISKPWR
v DEVBPLN 50B13109
backplane command.
2. v SASCABL

50B17604 • 50B18404
v DEVBPLN
50B17684
50B17604
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
50B17694
50B17614
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
50B176A4
50B17624
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
50B176B4
50B17634
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
50B176C4
50B17644
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
50B176D4
50B17654
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
50B176E4
50B17664
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
50B176F4
50B17674
Failing Item:
v DISKFAN
Failing Item:
v DISKFAN
50B18404
required.

50B1FFF4 • 56199100
v SASCABL
50B1FFF4
v STORIOA
v DEVBPLN
Failing Item:
v SASEXP

indications.
56193000
following conditions are not present:
Failing Item: v Tape and DASD devices attached to an I/O
v FI01112 Processor that does not support Tape and Dasd
56193202 v An unsupported device type or model is attached.
Explanation: Tape unit configuration error. Failing Item:

v TAPCNFG
v The attached device type or model is only v PTFSRCH
supported on an I/O adapter that is attached to an
I/O processor. 56199100
Failing Item: Explanation: Interface error detected by system or by
v TAPCNFG tape unit.
56193400 1. Ensure that the signal cable is seated correctly, and
Explanation: Device error has occurred.
v FI00872 the cable.
v DEVTERM
v FI00871
v FI01106
Failing Item:
v FI00871
56199020
v FI01112

56199101 • 56199201
v FI00872 v FI00871
v DEVTERM v FI01112
v SASCABL
56199101
Explanation: Fibre Channel interface error detected. 56199104
Response: If the attached device is an external device, Explanation: Interface error detected by system or by
do the following before exchanging any parts: tape unit.
1. Ensure that the Fibre Channel cable is correctly Response: If the attached device is an external tape
connected to the ports. device, do the following before exchanging any parts:
2. Clean the Fibre Channel connectors. 1. Ensure that the USB cable is correctly connected to
3. If there is a switch or hub attached, verify that it is the ports.
operational. 2. Ensure that the device has power.
gateway device service documentation for If the attached tape device is owned by a Virtual I/O
additional problem analysis procedures. Server partition refer to Troubleshooting the Virtual
additional problem analysis procedures. Failing Item:
v USB_DEV
v USB_IOA
I/O Server to determine the parts to replace. v USB_CBL
Failing Item:
56199200
v FCIOA
v FCDEV Explanation: Tape unit is not responding.
v FCCABLE Response: If the attached device is an external device,
56199102 1. Ensure that the device is powered on.
error.
Failing Item:
v FI00871
v FI00872
Failing Item:
v DEVTERM
v FI00871
v FI01112
56199103
v FI00872
tape unit.
device, do the following before exchanging any parts:
Explanation: Tape unit command timeout.
the ports. Response: If the attached device is an external device,
2. Ensure that the device has power. do the following before exchanging any parts:
Failing Item:

56199202 • 56199302
3. Ensure that the signal cable is seated correctly, and v FCGATE

that there are no bent or damaged pins on the SCSI v FCIOA
cable.
v FI00871
v ANYFC
device end of the SCSI cable.
v FCCABLE
I/O Server partition it may be necessary to reset the v FI00872
virtual IOP to recover from the error. v DEVTERM
Failing Item:
v FI00871 56199220
v FI01112 Explanation: Hardware configuration change detected.
v FI00872 Response: The tape device or tape library device has
v DEVTERM reported a configuration change that requires the I/O
v MEDIA processor to be reset. Reset the I/O processor before
using the device.
56199202
56199221
Explanation: Tape unit failed after Licensed Internal
Code was loaded. Explanation: I/O path change occurred.
Response: If the attached device is an external device, Response: No action required. This reference code is
do the following before exchanging any parts: logged for information only.
2. If an interposer is required, make sure that it is 56199300
connected between the I/O processor and the SCSI Explanation: Tape unit failure.
cable.
3. Ensure that the SCSI cable is seated correctly, and Failing Item:
that there are no bent or damaged pins on the SCSI v FI00871
cable.
4. Ensure that a terminating plug is attached to the 56199301
Explanation: Tape device failure, redundancy lost.
Failing Item:
Response: The tape unit detected a hardware failure
v FI00871
v FI01112 current operation.
v FI00872
Failing Item:
v DEVTERM
v FI00871
56199210
56199302
Explanation: Illegal or unsupported tape unit
Explanation: Tape device failure or media error.
response.
Failing Item:
v FI00871
Refer to the tape unit service information for possible
v FI01112
information on diagnositic tests that can be run to
Failing Item:
56199211
v MEDIA
error.
documentation to analyze the problem.
Failing Item:

56199303 • 56199501

56199303
exchange the tape media.
Explanation: Gateway device failure.
Failing Item:
Response: Use the gateway device service v MEDIA
v TAPCLN
v FCGATE
56199351
56199304
Explanation: Tape unit failure. mounted in tape device.
Response: Before exchanging any parts, do the Response: The tape unit detected that the mounted
following: tape cartridge has a history of excessive read and write
1. Ensure that the EKM/TKLM server is operational errors. It is recommended that you exchange the tape
and properly configured. cartridge.
2. Ensure that the mounted cartridge is in the Failing Item:
EKM/TKLM server database. v MEDIA
Failing Item: v TAPCLN
v USER v FI00871
v FI00871
56199355
56199310 Explanation: The data format is incorrect; the tape
Explanation: Licensed Internal Code for the tape unit cannot be read.
is not correct. Response: The tape unit has detected that the data
Failing Item: format on the tape media is not supported or that the
v PTFSRCH
v FI00871
1. Initialize the tape to a different format.
56199320
Explanation: Tape device Licensed Internal Code If the operation continues to fail, use a different tape
failure. cartridge.

v FI00130 v USER
v FI00871 v MEDIA
v TAPCLN
56199321 v FI00871

error. 56199500
Response: Use the gateway device service Explanation: Licensed Internal Code error.
Failing Item: dump of the I/O processor data.
v PTFSRCH
56199350
Explanation: Tape unit detected a read or write error 56199501
Clean the tape unit and retry the operation.
v PTFSRCH

56199800 • 5619FFF6

56199800
Explanation: System successfully recovered from (Information Only.)
Response: No action required. This reference code is 56199899
has been corrected.
56199801
Explanation: System successfully recovered from Online Problem Analysis when no problem was found
temporary I/O error. or the problem was corrected.
logged for information only. 56199900
56199802 not upgraded.
Explanation: System successfully recovered from Response: The I/O processor loading of Licensed
temporary I/O error. Internal Code (LIC) to the programmable tape unit was
not completed.
logged for information only. The tape unit will continue to operate with the
56199803 v Wait for next IPL when the system will attempt to
Response: No action required. This reference code is level of LIC, the IOP will attempt to load the new
logged for information only. LIC.
Failing Item:
56199804 v USER
temporary I/O error. 56199901
Response: No action required. This reference code is Explanation: Tape performance statistics logged.
56199805
Explanation: System successfully recovered from 56199902
Explanation: An IOP dump was initiated.
logged for information only. Response: No action required.
56199806 56199903
Explanation: System successfully recovered from Explanation: Tape device information logged.
5619FFF6
56199810 Explanation: Tape volume statistics logged (no action
Explanation: Problem analysis has determined a part required).
should be replaced.


56383000 • 56389101
indications.
v FI00871
56383000
v PTFSRCH
v FI01112
tape unit.
56383202

Failing Item:
56383400 v FI00871
v FI00872
Failing Item:
v DEVTERM
v FI00872
v DEVTERM
56389101
v FI00871
v TAPCNFG

56389102 • 56389202

v FCIOA
v FCDEV
v FCCABLE
56389102

v DEVTERM v FI00871
v FI01112
56389103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871


Code was loaded.
Failing Item:

56389210 • 56389304

56389221
cable.
v FI00871
v FI01112 56389301

response. v FI00871
Failing Item:
v FI00871 56389302

v FCGATE
v FCIOA 56389303
v DEVTERM v FCGATE
56389220 56389304
Failing Item:
v USER

56389310 • 56389802
v FI00871
56389355
56389310
cannot be read.
is not correct.
56389320
failure.
Failing Item:
v FI00130 v MEDIA
v FI00871 v TAPCLN
v FI00871
56389321
error.
Failing Item:
Failing Item:
v FCCODE
v PTFSRCH
56389350
56389501
on tape medium.
Failing Item:


v MEDIA
v FI00871
56389801
56389351
cartridge. 56389802

56389803 • 5638FFF6

56389803
56389900
not upgraded.
56389804
not completed.
LIC.
Failing Item:
56389806 56389901
56389902
should be replaced.


indications.

56753000 • 56759102
56753000
the cable.
v FI01112
Failing Item:
Failing Item:
v TAPCNFG 56759101
Failing Item:
v FI00872
v DEVTERM
operational.
v FI00871

v FCDEV
v FCCABLE
Failing Item:
v TAPCNFG 56759102
v FI00871
v PTFSRCH error.
tape unit.
v FI00871

56759103 • 56759202

v DEVTERM v FI00871
v FI01112
56759103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871

Code was loaded.
Failing Item:
v USB_IOA
v USB_CBL
56759200 cable.
Failing Item:
v FI00871
v DEVTERM

56759210 • 56759320
56759210 56759302
response.
Failing Item:
56759211 v MEDIA
error.
v FI00871 v FCGATE
v ANYFC
v FCCABLE 56759304
v FI00872
v DEVTERM
following:
56759220
using the device.
v USER
v FI00871
56759221
Failing Item:
56759300
v PTFSRCH
Failing Item:
v FI00871 56759320
56759301 failure.
current operation.
Failing Item:
v FI00871

56759321 • 56759804
v FI00871
56759321
56759500
error.
Failing Item:
v PTFSRCH
56759350
56759501
56759351 56759801
cartridge.
56759802
Failing Item:
v TAPCLN
56759355 56759803

Failing Item:
v USER
v MEDIA
v TAPCLN

56759805 • 5675FFF6
56759805 56759902
56759903
56759806
5675FFF6
required).
56759810
should be replaced.
(Information Only.)
56759899
has been corrected.
56759900
not upgraded.
not completed.
LIC.
Failing Item:
v USER
56759901

5700A001 • 57021307

v FI00718
5700A001
v AJDGP01
v MA_BRDG
detected.
Failing Item:
5700B9B0
v AJDGP01
5700B9A0 Failing Item:

v FI00719
v AJDG301
Failing Item:
v MA_BRDG
v FI00719

v FI00718
5701A001
v AJDGP01
v MA_BRDG
detected.
Failing Item:
5701B9B0
v AJDGP01

v FI00719
v AJDG301
Failing Item:
v MA_BRDG
v FI00719

57020A17
Failing Item:
occurred. v FI01105
Failing Item:
57021306
v IOP
v MA_BRDG Explanation: I/O processor card or Licensed Internal
Code error.
v AJDGP01
v AJDG301 Response: A microprocessor exception occurred on the
I/O processor.

v AJDGP01
error. v IOP
v FI01104
Failing Item:
v BACKPLN
v AJDGP01
v AJDG301
57021307
v IOP
v MA_BRDG Explanation: I/O processor resource not available.
Failing Item:
5702102E v AJDGP01

57021310 • 57023021
v AJDG301 v FI01101
v IOP
57021310 v MA_BRDG
57023001
faster than the errors are being reported to the system. Explanation: Not valid condition in I/O Processor
Check other errors reported to the system and correct Licensed Internal Code.
them.
57021317
Failing Item:
Explanation: I/O processor card error. v IOP
Response: Display the Service Action Log entry for v AJDGP01
57023002
do NOT replace the IOP. This is a recoverable error.
Perform the following: Explanation: Addressed device failed to respond to
selection.
are attached, use Hardware Service Manager to re-IPL Failing Item:
the IOP. Other resources attached to the IOP may then v IOPIP16
v FI01105
2. If disk units are not attached, perform the VRYCFG v STORIOA
v FI01141
Failing Item:
v FI01106
v SVCDOCS
57023006
57022200
Failing Item: v IOP
v AJDGP01 v ANYBUS
v FI01101
57022201
57023020
v USER
v FI01105
Failing Item:
57022202 v IOPIP17
v USER
v FI01107
v FI00022
v FI01105 57023021
57023000 configuration error.
Explanation: A permanent I/O processor failure Response: Error occurred on SCSI bus 1.
occurred.
Failing Item:
Failing Item:

57023022 • 57023102
v IOPIP17
57023087
v USER
v FI01107
v STORIOA Response: The Licensed Internal Code could not

v AJDGP01
configuration error. v AJDG301
v IOACNFG
v FI01104
Failing Item:
v IOPIP17
57023100
v USER
v FI01107
error.
v STORIOA

v IOPIP13
v STORIOA
v FI01140
Failing Item:
v DEVBPLN
v IOPIP17
v USER
57023101
v FI01107
v STORIOA
error.
57023080
Failing Item:
error. v IOPIP13
v FI01107
Failing Item:
v STORIOA
v AJDGP01
v FI01140
v DEVBPLN
57023081
57023102
required.
error.
57023084
Code error. Failing Item:
Response: A microprocessor exception occurred on the v IOPIP13
I/O processor. v FI01107
v AJDGP01 v FI01140
v IOP v DEVBPLN
v FI01104
v MA_BRDG

57023103 • 57023142

57023103
Failing Item:
error. v SVCDOCS

57023122
Failing Item:
v IOPIP13
not operational.
v FI01107
v STORIOA
v DEVBPLN
Failing Item:
v SVCDOCS
57023109
command.
v IOPIP16
v BACKPLN v SVCDOCS
v FI01106
57023136
57023110
Explanation: The removable media device is assigned
error.
Failing Item:
v IOPIP16 v FI01105
v FI01105
v STORIOA 57023140
v FI01140
v FI01106
v SVCDOCS since SCSI bus 1 is now operational.
57023121 57023142
Explanation: I/O Processor detected that the bus is Explanation: I/O Processor detected that the bus is
not operational. now operational.
Response: A device was added to SCSI bus 1 of the Response: This reference code and the 3122 reference
I/O Adapter and caused the bus to become not code that occurred before it require no service action,

57023143 • 57023501

57023215
57023143
now operational.
Failing Item:
57023250
57023150 Explanation: Disk unit requires initialization before
Explanation: I/O processor detected a SCSI bus use.
configuration error. Response: Perform a D-IPL and work on errors found
Response: Internal and external SCSI cables are in the log.
v USER
Failing Item:
v SVCDOCS 57023300
57023151
Failing Item:
v IOPIP01
v MEDIA
v FI00121
Failing Item:
57023400
v SVCDOCS
57023200 Response: NOTE: If external devices are attached
check EXTSCSI and DEVTERM first.
Explanation: A tape/CD or disk device reported a
failure. Failing Item:
v FI01105 v STORIOA
v STORIOA v FI01106
v IOP v DEVTERM
v MEDIA v FI01140
57023203 57023401

v FI01105 v DEVBPLN
57023205 57023501
error.
v AJDGP01
Failing Item:
v IOP
v FI01105

57023600 • 57026602
57023600 57026081
required. error.
Failing Item:
57023601 v AJDGP01
Explanation: System log entry only, no service action v IOP
required.
57026082
57026070
occurred.
Failing Item:
v IOP v IOP
57026071 57026083
Explanation: I/O processor Licensed Internal Code Explanation: I/O processor Licensed Internal Code
error. error.
v AJDGP01 v AJDGP01
v IOP
57026072
error.
v IOP v AJDGP01
v IOP
57026073 v MA_BRDG
Explanation: IPL device not ready.
v MEDIA Explanation: A permanent IOA hardware error
v FI01105 occurred.
v FCIOA
57026075 v OPT_CLN
57026201
Failing Item:
v AJDGP01 Explanation: IOA LID is not valid.
Failing Item:
57026076 v AJDGP01
57026602
Failing Item:
v MEDIA Explanation: An I/O processor Licensed Internal Code
error occurred.
v AJDGP01
v AJDGP01

57028000 • 57028132
57028000 57028010
shown.
v CACHE v CACHE
v STORIOA
57028002
occurred.
shown.
Failing Item:
v STORIOA
Failing Item:
v CACHE
57028004
v STORIOA
57028100
Failing Item:
v FI01141 error.
v STORIOA
Failing Item:
v AJDGP01
57028005
v IOP
error occurred.
57028130
error.
shown.
Failing Item:
v CACHE
57028131
57028007
occurred.
shown.
v STORIOA error.

57028133 • 57028300

57028155
information only.
occurred.
57028133
Failing Item:
error. v AJDGP01
v STORIOA
57028140 occurred.
error. v AJDGP01
57028157
57028141
57028145
occurred.
57028146 RESET(*YES) command to reset the IOP and Vary On
attached resources.
Failing Item:
v FI01105
57028200
57028150
occurred.
Failing Item:
v STORIOA v IOP
v ANYBRDG
57028300
57028151
error.
v STORIOA v STORIOA
v IOP
v AJDGP01

57028301 • 57029021
57028301 57029009
Failing Item:
v FI01101 57029010
Failing Item:
57028400 v IOPIP31
error. 57029011
Failing Item:
57029000 v IOPIP32
57029001 broken.

v IOPIP33
57029013
57029002 Explanation: The IOP and attached cache adapter card
are not compatible.
Failing Item:
Failing Item:
v IOPIP19
v IOPIP16
v FI01105
57029020
v STORIOA
v BACKPLN
v IOPIP20
57029008
57029021
Failing Item:
v IOPIP20

57029022 • 57029050
57029022 57029029
v SVCDOCS
57029023
Explanation: Array not functional due to present 5702902F
57029024 contains more than 10 members. Use the 90xx entry
v IOPIP22
57029025
Failing Item:
location.
v IOPIP21
57029026
Failing Item:
v IOPIP22 57029040
57029027 Response: No action required. Protection will be

57029028 Response: Call your next level of support to report
the problem.

supports arrays, or stop an array on this IOP. 57029050
Failing Item:
v IOPIP30

57029051 • 5702B3B1
57029051 57029082
failed device.
Failing Item:
v FI01105
v FI01140
v FI01106
Failing Item:
v IOPIP27
57029090

last known status.
v IOPIP28
level of support.
57029053
Failing Item:
previous problems.
problem.
Failing Item:
v SVCDOCS
level of support.
Failing Item:
57029054
v SVCDOCS
previous problems.
57029092
occurred.
Failing Item:
v FI01105
v STORIOA

5702B3B2 • 5702B935
v IOP
5702B3B2
5702B3E0
occurred.
Failing Item:
v IOP Failing Item:
v IOP
5702B3B3 v MA_BRDG

occurred. 5702B3E1

v IOP Failing Item:
v IOP
5702B3B4 v MA_BRDG
occurred. 5702B410
v IOP occurred.
Failing Item:
5702B3B5 v STORIOA
occurred. 5702B411
v IOP occurred.
Failing Item:
5702B3B6 v STORIOA
occurred. 5702B412
v IOP occurred.
Failing Item:
5702B3B7 v IOPIP16
occurred. v FI01140
v IOP v DEVTERM
5702B3B8 5702B935

v MA_BRDG v FI01101
v IOP v AJDGP01
v IOP
5702B3B9 v MA_BRDG

occurred.
Failing Item:

5702BE00 • 57033101
Failing Item:
5702BE00
v STORIOA
v ANYBRDG
Failing Item:
v AJDGP01 5702FF6D
v IOP
v MA_BRDG
Failing Item:
v IOP
5702FF3D
v ANYBUS

57031310 57033022
Explanation: I/O processor resource not available. Explanation: I/O processor detected a SCSI bus
faster than the errors are being reported to the system. Response: Error occurred on SCSI bus 2.
Failing Item:
them.
v IOPIP17
v USER
57033006
v FI01107
v STORIOA
Failing Item:
v IOP 57033023
v ANYBUS
v STORIOA configuration error.
57033020
Failing Item:
v IOPIP17
v USER
v FI01107
v IOPIP17
v USER 57033100
v FI01107
v STORIOA error.
57033021
Failing Item:
v IOPIP13
v FI01107
v STORIOA
v IOPIP17 v DEVBPLN
v USER
v FI01107 57033101
v STORIOA

57033102 • 57033143

error. v SVCDOCS
v DEVBPLN
Failing Item:
57033102 v SVCDOCS

error. 57033123
Response: Error occurred on SCSI bus 2. Explanation: I/O Processor detected that the bus is
not operational.
Failing Item:
v IOPIP13
v STORIOA
Failing Item:
v FI01140
v SVCDOCS
v DEVBPLN
57033140
57033103
Explanation: I/O processor card detected interface now operational.
error.
Response: Error occurred on SCSI bus 3. code that occurred before it require no service action,
v IOPIP13
v FI01107 57033141
v FI01140 now operational.
v DEVBPLN Response: This reference code and the 3121 reference

57033120
not operational.
Response: A device was added to SCSI bus 0 of the now operational.
v SVCDOCS
57033143
57033121
not operational.

57033150 • 57038130
57033150 57033601
Explanation: I/O processor detected a SCSI bus Explanation: System log entry only, no service action
configuration error. required.
connected to SCSI bus 0 at the same time. Correct the 57038008
v SVCDOCS Response: NOTE: Under a certain configuration, this
57033151 action. Depending on the configuration of the system,
Explanation: I/O processor detected a SCSI bus Storage IOA Cache may have been disabled to allow
configuration error. attachment of OEM Storage that emulates a Load
Response: Internal and external SCSI cables are Source drive. If this is the case, this error will be posted
connected to SCSI bus 1 at the same time. Correct the each time the IOA is IPLed and it can be ignored.
SCSI bus 1 configuration. Failing Item:
Failing Item: v CACHBAT
v SVCDOCS v STORIOA
57033400 57038009
Explanation: I/O processor card detected device error. Explanation: Impending cache battery pack failure.
v FI02112 v CACHBAT
v STORIOA
v FI01106 57038012
v DEVTERM Explanation: Attached read cache devices exceed
57033401 IOA.
Explanation: Device backplane problem. Failing Item:

v DEVBPLN
57038100

error.
v AJDGP01 v IOP
v IOP
57038130
57033600 Explanation: IOA detected recoverable device bus
error.
required. Response: An error occurred on SCSI bus 0. No action
information only.

57038131 • 57038157

57038131
Explanation: IOA detected recoverable device bus Storage IOA Cache may have been disabled to allow
error. attachment of OEM Storage that emulates a Load
information only. Failing Item:
v STORIOA
57038132 v ANYBRDG
error. 57038151
Response: An error occurred on SCSI bus 2. No action Explanation: I/O processor Licensed Internal Code
is required. This reference code is logged for error.
information only.
Failing Item:
v AJDGP01
57038133
v STORIOA
error.
57038155
occurred.
information only.
Failing Item:
57038140 v AJDGP01
v STORIOA
error.
57038156
is logged for information only. Explanation: A permanent I/O processor failure
occurred.
Explanation: IOA detected recoverable device error. v AJDGP01
v STORIOA
57038157
Explanation: A recoverable I/O processor error Response: Display the Service Action Log entry for
occurred. this SRC. If the Failing Item indicates I/O adapter, then
Failing Item:
v STORIOA is a recoverable error. Perform the following for the
57038146 1. If the I/O Processor is not operable and disk units
Explanation: Disk device detected recoverable error. are attached, use Hardware Service Manager to re-IPL
Failing Item: need to be Varied On.
v FI01105
57038150 attached resources.
occurred. v SVCDOCS

57038200 • 57039026
57038200 57039011
v AJDGP01 v IOPIP32
v IOP
57039020
57039000 Explanation: Array not functional due to present
Explanation: I/O processor card detected device error. hardware configuration.

v FI01105 v IOPIP20
v STORIOA
57039021
configuration error. Failing Item:
v IOPIP33
57039022
Failing Item:
Failing Item:
v IOPIP22
v IOPIP16
v FI01105
57039023
v STORIOA
v BACKPLN
v IOPIP22
57039008
57039024
Failing Item:
v IOPIP22
57039009
57039025
assistance. Explanation: Disk unit is not supported at its physical
location.
Failing Item:
v IOPIP21
57039010
57039026
devices cannot be found. Explanation: Array not functional due to present
Failing Item:

57039027 • 57039051
v IOPIP22
57039032
57039027
or failed.
unit should be replaced.
Failing Item:
Failing Item:
v IOPIP34
v FI02112
v IOPIP21
57039028
Explanation: Incorrect hardware configuration change 57039040
has been detected.
move all devices in an array to another IOP that Response: No action required. Protection will be
supports arrays, or stop an array on this IOP. automatically restarted.
Failing Item:
57039041
v SVCDOCS
57039029
the problem.
has been detected.
Failing Item:
v AJDGP01
Failing Item:
v SVCDOCS
57039042
Explanation: An array parity error has been detected
5703902F
and corrected.
entry.
the problem.
Failing Item:
contains more than 10 array members. Use the 90xx v NEXTLVL
code as the starting point for this problem. 57039050
57039030 for a disk unit.
Explanation: Array no longer protected due to Failing Item:
v IOPIP30
Failing Item:
v IOPIP21 57039051
57039031 failed device.
Explanation: Automatic rebuild initiated for array. Response: If all configured units are missing, a 9054
Response: Either a previous rebuild was interrupted reference code may appear in the product activity log.
and was automatically restarted, or a hot spare disk If so, perform the action indicated for the 9054
unit was used to automatically rebuild the array. Look reference code.
for other reference codes and take action on them. Otherwise, perform the procedure indicated in the
failing item list.
Failing Item:
v IOPIP27

57039052 • 57039092
57039052 57039081
Explanation: Cache data exists for device that has Explanation: I/O processor card detected device error.
been modified.
Failing Item:
Response: Contact your next level of support. v FI01105
v SVCDOCS
57039082
Explanation: IOP resources not available due to Failing Item:
previous problems.
v IOPIP16
Response: Take action on other IOP reference codes v FI01105
v STORIOA
If you cannot get to SST or DST, and cannot perform a v FI01140
v BACKPLN
IOP reference codes and take action on them. v FI01106
Failing Item:
57039090
v SVCDOCS
last known status.
57039054
previous problems.
problem.
or replacement disk units. IPL the system to DST. If
level of support.
Look for Product Activity Log entries for other IOP v SVCDOCS
v SVCDOCS Explanation: Incorrect hardware configuration change
has been detected.
57039071 Response: Re-IPL the system. If any reference codes
Explanation: Link from IOA to auxiliary cache IOA
problem.
went operational.
level of support.
Failing Item:
57039072
v SVCDOCS
went non-operational.
57039092
use.
57039073
Failing Item:
v IOPIP26
Failing Item:
v IOPIP40

57039093 • 57043400

57039093
Failing Item:
Explanation: Read cache device not in correct format.
v STORIOA
v ANYBRDG
Failing Item:
v SVCDOCS 5703FF6D
5703B934 system bus error.
Failing Item: v IOP
v STORIOA v ANYBUS
5703FF3D

57041310
Explanation: I/O processor or I/O adapter resource port was left open.
not available. 3. This error can occur if there is a port or link failure.
Response: The I/O processor or I/O adapter error log If you have eliminated the above possibilities
is being filled faster than the errors are being reported contact your next level of support.
to the system. Check other errors reported to the Failing Item:
system and correct them.
v FCPORT
v FCIOA
57043020
v FCDEV
Explanation: I/O processor detected a configuration v OPT_CLN
error.
Response: Either too many devices or the wrong kind 57043140
Change the configuration. Explanation: I/O Processor detected that a port is
now operational.
Failing Item:
v SVCDOCS
57043100
Explanation: I/O processor card detected interface 57043200
error.
Failing Item:
Failing Item:
v FCINTF
v FCDEV
v ANYFC
v FCIOA
v FCIOA
v IOP
v OPT_CLN
v OPT_CLN
57043120
57043400
Failing Item:
v FCDEV
v FCINTF
v ANYFC

570434FF • 57049092
v FCIOA
57048151
v OPT_CLN
error.
570434FF
Failing Item:
v AJDGP01
Response: The device indicated that a format is in v FCIOA
v IOP
57048130 57048155
Explanation: Recovered Fibre Channel interface error. Explanation: A permanent I/O processor failure
occurred.
v AJDGP01
57048140 v FCIOA
v OPT_CLN
Explanation: Recovered Fibre Channel interface error.
57048156
occurred.
57048141
Failing Item:
v AJDGP01
v FCIOA
v OPT_CLN
57048145
57049091
occurred. Explanation: Incorrect hardware configuration change
has been detected.
Failing Item:
v FCIOA
v OPT_CLN IPL the I/O processor, see Debug the resource. If an
57048146 resolve the problem, contact your next level of support.

v SVCDOCS
Failing Item:
v FCDEV
57049092
57048150 Explanation: Incorrect hardware configuration change

has been detected.
occurred. Response: Reset the I/O processor and then IPL the
Failing Item: IPL the I/O processor, see Debug the resource. If an
v FCIOA I/O processor reset and I/O processor IPL does not
v ANYBRDG
v SVCDOCS

5704FF3D • 57088008
v FCIOA
5704FF3D
v ANYBRDG
v OPT_CLN
Failing Item:

5706A001
Failing Item:
detected. v IOA
v AJDGP01
Failing Item:
v AJDGP01
5706B9B0

5707A001
Failing Item:
detected. v IOA
v AJDGP01
Failing Item:
v AJDGP01
5707B9B0

57081310 57083101
Explanation: I/O adapter resource not available. Explanation: Interface error.
Response: The I/O adapter error log is being filled Response: Error occurred on SCSI bus 1.
Failing Item:
them. v AUXCBL
v AUXIOA
57083006 v PRIMIOA

57083400
Failing Item:
Explanation: SCSI resource error.
v AUXIOA
v ANYBRDG Failing Item:
v IOP v AUXCBL
v PRIMIOA
57083100
57086075
Explanation: Interface error.
Failing Item:
Failing Item:
v PTFSRCH
v AUXCBL
v AUXIOA
57088008
v PRIMIOA

57088009 • 57088157

57088150
occurred.
SRC may not represent an error that requires a service Response: NOTE: Under a certain configuration, this
action. Depending on the configuration of the system, SRC may not represent an error that requires a service
the Storage IOA may have been altered and/or the action. Depending on the configuration of the system,
Storage IOA Cache may have been disabled to allow the Storage IOA may have been altered and/or the
attachment of OEM Storage that emulates a Load Storage IOA Cache may have been disabled to allow
Source drive. If this is the case, this error will be posted attachment of OEM Storage that emulates a Load
each time the IOA is IPLed and it can be ignored. Source drive. If this is the case, this error will be posted
Failing Item:
v CACHBAT Failing Item:
v AUXIOA v AUXIOA
v ANYBRDG
57088009
57088151
Failing Item:
v CACHBAT Failing Item:
v PTFSRCH
57088130 v AUXIOA
Explanation: IOA detected recoverable SCSI bus error.

57088155
is required. This reference code is logged for Explanation: A permanent failure occurred.
v PTFSRCH
57088131 v AUXIOA
information only.
Failing Item:
v PTFSRCH
57088140
v AUXIOA
Response: No action is required. This reference code 57088157
Explanation: I/O adapter card temporary error.
57088141 Response: Display the Service Action Log entry for

Explanation: IOA detected recoverable SCSI resource replace the I/O adapter. If the Failing Item indicates
error. SVCDOCS, then do NOT replace the I/O adapter. This
Response: No action is required. This reference code is a recoverable error. Perform the following for the
is logged for information only. I/O processor that the I/O adapter is attached to:
57088145 are attached, use Hardware Service Manager to re-IPL
Explanation: A recoverable error occurred. need to be Varied On.
Failing Item: 2. If disk units are not attached, perform the VRYCFG
v AUXIOA RESET(*YES) command to reset the IOP and Vary On
attached resources.
Failing Item:

57088300 • 5708FF3D
v SVCDOCS
5708FF3D
57088300
Failing Item:
Explanation: IOA hardware or PCI bus error.
v AUXIOA
Failing Item:
v ANYBRDG
v AUXIOA
v ANYBRDG
v PTFSRCH
57088301
Code.
Failing Item:
v PTFSRCH
v AUXIOA
57088302
Failing Item:
v SVCDOCS
v AUXIOA
57089055
Explanation: Write cache data is available for attached
storage IOA.
57089071
went operational.
57089072
57089073
Explanation: Disconnected, incompatible, or
non-operational storage IOA.
Failing Item:
v IOPIP41

57091310 • 57093102

57091310 57093023
Explanation: I/O processor resource not available. Explanation: I/O processor detected a SCSI bus
faster than the errors are being reported to the system. Response: Error occurred on SCSI bus 3.
Failing Item:
them.
v IOPIP17
v USER
57093006
v FI01107
v STORIOA
Failing Item:
v IOP 57093100
v ANYBUS
v STORIOA error.
57093020
Failing Item:
v IOPIP13
v FI01107
v STORIOA
v IOPIP17 v DEVBPLN
v USER
v FI01107 57093101
v STORIOA
error.
57093021
Failing Item:
v IOPIP13
v FI01107
v IOPIP17 v FI01140
v USER v DEVBPLN
v FI01107
v STORIOA 57093102
57093022 error.
Explanation: I/O processor detected a SCSI bus Response: Error occurred on SCSI bus 2.
Failing Item:
v IOPIP13
v IOPIP17 v STORIOA
v USER v FI01140
v FI01107 v DEVBPLN
v STORIOA

57093103 • 57093151
57093103 57093140
error. now operational.
Response: Error occurred on SCSI bus 3. Response: This reference code and the 3120 reference
Failing Item:
v IOPIP13
v FI01107
57093141
v STORIOA
v FI01140
now operational.
v DEVBPLN
v SVCDOCS since SCSI bus 2 is now operational.
57093121 57093143
operational. Remove the device. since SCSI bus 3 is now operational.
Failing Item:
v SVCDOCS 57093150
Explanation: I/O Processor detected that the bus is Response: Internal and external SCSI cables are
not operational. connected to SCSI bus 0 at the same time. Correct the
I/O Adapter and caused the bus to become not Failing Item:
operational. Remove the device. v SVCDOCS
Failing Item:
v SVCDOCS 57093151
Explanation: I/O Processor detected that the bus is Response: Internal and external SCSI cables are
not operational. connected to SCSI bus 1 at the same time. Correct the
I/O Adapter and caused the bus to become not Failing Item:
operational. Remove the device. v SVCDOCS
Failing Item:
v SVCDOCS

57093400 • 57098133
57093400 57098009
Explanation: I/O processor card detected device error. Explanation: Impending cache battery pack failure.
v FI02112 v CACHBAT
v STORIOA
v FI01106 57098012
v DEVTERM Explanation: Attached read cache devices exceed
57093401 IOA.
Explanation: Device backplane problem. Failing Item:
v DEVBPLN
57098100
error.
v AJDGP01 v IOP
v IOP
57098130
57093600 Explanation: IOA detected recoverable device bus
error.
required. Response: An error occurred on SCSI bus 0. No action
information only.
57093601
57098131
required.
error.
57098008
occurred.
information only.
57098132
the Storage IOA may have been altered and/or the Explanation: IOA detected recoverable device bus
Storage IOA Cache may have been disabled to allow error.
information only.
Failing Item:
v CACHBAT 57098133
v STORIOA
error.
information only.

57098140 • 57099000
57098140 57098155
Explanation: IOA detected recoverable device bus Explanation: A permanent I/O processor failure
error. occurred.
is logged for information only. v AJDGP01
v STORIOA
57098141
Explanation: IOA detected recoverable device error. 57098156
Response: No action is required. This reference code Explanation: A permanent I/O processor failure
is logged for information only. occurred.
Failing Item:
57098145 v AJDGP01
Explanation: A recoverable I/O processor error v STORIOA
occurred.
v STORIOA Explanation: I/O adapter card error.
57098146 this SRC. If the Failing Item indicates I/O adapter, then
Explanation: Disk device detected recoverable error. replace the I/O adapter. If the Failing Item indicates
Failing Item: is a recoverable error. Perform the following for the
v FI01105 I/O processor that the I/O adapter is attached to:
57098150 are attached, use Hardware Service Manager to re-IPL
Explanation: A permanent I/O processor failure need to be Varied On.
occurred.
Response: NOTE: Under a certain configuration, this RESET(*YES) command to reset the IOP and Vary On
SRC may not represent an error that requires a service attached resources.
the Storage IOA may have been altered and/or the Failing Item:
Storage IOA Cache may have been disabled to allow v SVCDOCS
each time the IOA is IPLed and it can be ignored. 57098200

error.
v STORIOA
v AJDGP01
57098151 v IOP

error. 57099000
Failing Item: Explanation: I/O processor card detected device error.

v STORIOA v FI01105
v STORIOA

57099001 • 57099028
57099001 57099021
Explanation: I/O processor card detected device Explanation: Array not functional due to present
configuration error. hardware configuration.
v IOPIP33 v IOPIP20
57099002 57099022
Explanation: I/O processor card detected device error. Explanation: Array not functional due to present
Failing Item:
v FI01105 v IOPIP22
v STORIOA
v FI01140 57099023
v BACKPLN Explanation: Array not functional due to present
Failing Item:
57099008 v IOPIP22
expected by devices. 57099024
Failing Item: Explanation: Array not functional due to present
Failing Item:
57099009 v IOPIP22
assistance. 57099025
Failing Item: Explanation: Disk unit is not supported at its physical
v SVCDOCS location.
Failing Item:
57099010 v IOPIP21
devices cannot be found. 57099026
Failing Item:
57099011 v IOPIP22
those attached. 57099027
Failing Item:
57099020 v IOPIP34
v IOPIP20 has been detected.

57099029 • 57099053

57099041
Failing Item:
v SVCDOCS
the problem.
57099029
Failing Item:
v AJDGP01
has been detected.
57099042
Failing Item:
Explanation: An array parity error has been detected
v SVCDOCS and corrected.
5709902F the problem.
Explanation: Array addendum Product Activity Log Failing Item:
entry.
v NEXTLVL
57099050
contains more than 10 array members. Use the 90xx
entry that occurred at the same time as this reference Explanation: Required cache data cannot be located
code as the starting point for this problem. for a disk unit.
Failing Item:
57099030 v IOPIP30
missing or failed disk unit. 57099051
Failing Item: Explanation: IOP cache data exists for a missing or
v IOPIP21 failed device.
57099031 reference code may appear in the product activity log.
reference code.
failing item list.
for other reference codes and take action on them. Failing Item:
v IOPIP27
57099032
Explanation: A disk unit in a RAID array is missing 57099052
or failed. Explanation: Cache data exists for device that has
Response: The array is still protected, but the disk been modified.
unit should be replaced. Response: Contact your next level of support.
v FI02112 v SVCDOCS
v IOPIP21
57099053
57099040
Explanation: Array protection temporarily suspended. previous problems.
Response: No action required. Protection will be Response: Take action on other IOP reference codes
automatically restarted. which have surfaced.

57099054 • 5709FF3D

v SVCDOCS
last known status.
57099054
Explanation: IOP resources not available due to are surfaced, use the new reference code to resolve the
Failing Item:
v SVCDOCS
57099091
Failing Item:
v SVCDOCS
has been detected.
57099071
went operational.
Failing Item:
57099072 v SVCDOCS
went non-operational. 57099092
Response: No service action required. Explanation: Disk unit requires initialization before
use.
Explanation: Incompatible or non-operational v IOPIP26
v IOPIP40 Explanation: Read cache device not in correct format.
57099081
Failing Item:
v SVCDOCS
Failing Item:
v FI01105 5709B934
v STORIOA
Failing Item:
57099082
v STORIOA
v IOPIP16
v FI01105
Failing Item:
v STORIOA
v STORIOA
v FI01140

5709FF6D • 570B2202

v IOP
5709FF6D v ANYBUS
system bus error.

570B0A17 570B1310
Explanation: A permanent I/O processor failure Explanation: I/O processor resource not available.
occurred.
v IOP Check other errors reported to the system and correct
them.
v MA_BRDG
v AJDGP01
570B1317
v AJDG301
570B0A22 Response: Display the Service Action Log entry for
error.
do NOT replace the IOP. This is a recoverable error.
Failing Item: Perform the following:
v AJDGP01 1. If the I/O Processor is not operable and disk units
v AJDG301 are attached, use Hardware Service Manager to re-IPL
v IOP the IOP. Other resources attached to the IOP may then
v MA_BRDG
570B102E attached resources.
Explanation: Out of alternate sectors for disk storage. Failing Item:
v FI01105
570B2200
570B1306 Explanation: I/O processor Licensed Internal Code
Explanation: I/O processor card or Licensed Internal error.
Code error. Failing Item:
Response: A microprocessor exception occurred on the v AJDGP01
I/O processor.
v AJDGP01 Explanation: Removable media error during IPL.
v IOP
Failing Item:
v FI01104
v USER
v BACKPLN
v FI01105
570B1307
570B2202
Failing Item:
Failing Item:
v AJDGP01
v FI00022
v AJDG301
v FI01105

570B3000 • 570B3084
570B3000 570B3021
Explanation: A permanent I/O processor failure Explanation: I/O processor detected a SCSI bus
occurred. configuration error.
Failing Item: Response: Error occurred on SCSI bus 1.
v IOP v IOPIP17
v MA_BRDG v USER
v FI01107
570B3001 v STORIOA
Licensed Internal Code. 570B3022
Response: The Licensed Internal Code found a Explanation: I/O processor detected a SCSI bus
condition that should not have occurred. configuration error.
v IOP
Failing Item:
v AJDGP01
v IOPIP17
v USER
570B3002
v FI01107
selection.
v IOPIP16
v FI01105 configuration error.
v STORIOA
v FI01140
Failing Item:
v FI01141
v IOPIP17
v FI01106
v USER
v FI01107
570B3006
v STORIOA
v IOP
v ANYBUS error.
v FI01101
Failing Item:
v AJDGP01
570B3020
Explanation: I/O processor detected a SCSI bus 570B3081
Response: Error occurred on SCSI bus 0. required.
Failing Item:
v IOPIP17 570B3084
v USER Explanation: I/O processor card or Licensed Internal
v FI01107 Code error.
v STORIOA Response: A microprocessor exception occurred on the
I/O processor.
Failing Item:

570B3087 • 570B3120
v AJDGP01 v DEVBPLN
v IOP
v FI01104 570B3103
error.
570B3087 Response: Error occurred on SCSI bus 3.
Response: The Licensed Internal Code could not v IOPIP13
v AJDGP01 v FI01140
v AJDG301 v DEVBPLN
v IOACNFG
v FI01104 570B3109
570B3100 command.
error. v IOPIP16
v IOPIP13 v FI01140
v FI01107 v BACKPLN
v STORIOA v FI01106
v FI01140
v DEVBPLN 570B3110
570B3101 error.

error. v IOPIP16
v STORIOA
Failing Item:
v FI01140
v IOPIP13
v BACKPLN
v FI01107
v FI01106
v STORIOA
v FI01140
570B3120
v DEVBPLN
not operational.
570B3102
error.
Failing Item:
v IOPIP13
v FI01107
v STORIOA
v FI01140

570B3121 • 570B3203
570B3121 570B3142
operational. Remove the device. since SCSI bus 2 is now operational.
Failing Item:
v SVCDOCS 570B3143
570B3122 now operational.
Explanation: I/O Processor detected that the bus is Response: This reference code and the 3123 reference
not operational. code that occurred before it require no service action,
operational. Remove the device. 570B3150

v SVCDOCS
570B3123
Failing Item:
not operational.
v SVCDOCS
operational. Remove the device. 570B3151

v SVCDOCS
570B3136
Explanation: The removable media device is assigned
Failing Item:
elsewhere.
v SVCDOCS
Failing Item:
v USER
570B3200
v FI01105
failure.
570B3140
Failing Item:
v FI01105
now operational.
v STORIOA
v IOP
since SCSI bus 0 is now operational. v MEDIA
570B3141 570B3203
Explanation: I/O Processor detected that the bus is Explanation: Disk media format bad.

570B3205 • 570B6075
570B3205 570B3501
error.
v FI01105 v IOP
570B3215 570B3600
required.
570B3601
Failing Item:
v FI01105
required.
570B3250
570B6070
use.
occurred.
Failing Item:
in the log.
v IOP
Failing Item:
v USER
570B6071
570B3300
error.
Failing Item:
v IOPIP01
v MEDIA 570B6072
v FI00121
v FI01141 error.
Failing Item:
570B3400
v AJDGP01
check EXTSCSI and DEVTERM first. 570B6073
v FI02112
Failing Item:
v STORIOA
v MEDIA
v FI01106
v FI01105
v DEVTERM
v USER
v FI01140
570B6075
570B3401
Failing Item:
Failing Item:
v AJDGP01
v DEVBPLN

570B6076 • 570B8005
570B6076 570B6201
Explanation: I/O processor card detected media error. Explanation: IOA LID is not valid.
v MEDIA v AJDGP01
v AJDGP01
v FI01105 570B6602
570B6081 error occurred.
error. v AJDGP01
Failing Item:
v AJDGP01 570B8000
v IOP Explanation: A permanent IOP or cache adapter card
failure occurred.
570B6082 Response: DO NOT replace both FRUs at the same
Explanation: I/O processor Licensed Internal Code time. Exchange the FRUs one at a time in the order
error. shown.

v AJDGP01 v STORIOA
v IOP v CACHE
570B6083 570B8002
Explanation: I/O processor Licensed Internal Code Explanation: A permanent cache adapter card failure
error. occurred.
Failing Item: Response: DO NOT replace both FRUs at the same

v AJDGP01
shown.
v IOP
Failing Item:
v CACHE
570B6085
v STORIOA
error.
570B8004
Failing Item:
v AJDGP01
v IOP
Failing Item:
v MA_BRDG
v FI01141
v STORIOA
570B6200
Explanation: A permanent IOA hardware error
570B8005
occurred.
Failing Item:
error occurred.
v FCIOA
v OPT_CLN
shown.
Failing Item:
v STORIOA
v CACHE

570B8007 • 570B8150
570B8007 570B8131
Explanation: A recoverable cache adapter card error Explanation: IOA detected recoverable device bus
occurred. error.
Response: DO NOT replace both FRUs at the same Response: An error occurred on SCSI bus 1. No action
time. Exchange the FRUs one at a time in the order is required. This reference code is logged for
shown. information only.
Failing Item:
v CACHE 570B8132
error.
570B8010 Response: An error occurred on SCSI bus 2. No action
information only.
occurred.
570B8133
error.
Failing Item:
v CACHE information only.
v STORIOA
570B8140
570B8011
Explanation: A permanent cache adapter card failure error.
occurred.
Response: The cache adapter card may be missing, is logged for information only.
DO NOT replace both FRUs at the same time. 570B8141
Failing Item:
v CACHE is logged for information only.
v STORIOA
570B8145
570B8100
Explanation: I/O processor Licensed Internal Code occurred.
error.
Failing Item:
v AJDGP01
v IOP 570B8146
570B8130
Failing Item:
v FI01105
error.
570B8150
occurred.
Failing Item:

570B8151 • 570B9002
v STORIOA
570B8300
v ANYBRDG
Code error.
570B8151
error.
Failing Item:
Failing Item:
v STORIOA
v AJDGP01
v IOP
v STORIOA
v AJDGP01
570B8155
570B8301
occurred.
Failing Item:
v STORIOA
Failing Item:
v FI01101
570B8156
v AJDGP01
occurred.
v AJDGP01
v STORIOA error.
Failing Item:
570B8157
v AJDGP01
Response: Display the Service Action Log entry for 570B9000
v STORIOA
570B9001
Failing Item:
v SVCDOCS 570B9002
570B8200
Failing Item:
error.
v FI01105
v AJDGP01 v FI01140
v IOP v BACKPLN

570B9008 • 570B9028
v FI01106
570B9021
570B9008
Failing Item:
v IOPIP20
Failing Item:
v IOPIP25
570B9022
570B9009
Failing Item:
assistance.
v IOPIP22
Failing Item:
v SVCDOCS
570B9023
570B9010
Failing Item:
v IOPIP22
Failing Item:
v IOPIP31
570B9024
570B9011
Failing Item:
those attached.
v IOPIP22
Failing Item:
v IOPIP32
570B9025
570B9012
location.
Failing Item:
cannot find it.
v IOPIP21
broken.
570B9026
Failing Item:
v IOPIP29
v CACHE
Failing Item:
v IOPIP22
570B9013
570B9027
are not compatible.
Failing Item:
v IOPIP19
Failing Item:
v IOPIP34
570B9020
570B9028
Failing Item:
has been detected.
v IOPIP20

570B9029 • 570B9054

570B9050
Failing Item:
for a disk unit.
v SVCDOCS
Failing Item:
v IOPIP30
570B9029
570B9051
has been detected.
failed device.
Failing Item:
570B902F reference code.

570B9052
been modified.
570B9030
Failing Item:
Failing Item:
570B9053
v IOPIP21
previous problems.
570B9031
Failing Item:
570B9040
v SVCDOCS
Response: No action required. Protection will be 570B9054
previous problems.
570B9041
v SVCDOCS

570B9081 • 570BB3B8
570B9081 570BB3B1
occurred.
Failing Item:
v STORIOA v IOP
570B9082 570BB3B2
occurred.
Failing Item:
Failing Item:
v IOPIP16
v IOP
v FI01105
v STORIOA
570BB3B3
v FI01140
occurred.
v FI01106
Failing Item:
570B9090 v IOP

last known status. 570BB3B4
level of support.
Failing Item: 570BB3B5
occurred.
has been detected.
Response: Re-IPL the system. If any reference codes 570BB3B6
problem.
occurred.
Failing Item:
level of support.
v IOP
Failing Item:
v SVCDOCS
570BB3B7
570B9092
occurred.
Failing Item:
use.
v IOP
Failing Item:
v IOPIP26
570BB3B8
Failing Item:
v MA_BRDG

570BB3B9 • 571A3006
v IOP Failing Item:

v IOPIP16
570BB3B9 v FI01107
occurred. v STORIOA
v IOP
570BB935
570BB3E0 Explanation: Unknown hardware detected.
v IOP v AJDGP01
v MA_BRDG v IOP
v MA_BRDG
570BB3E1
570BBE00
Failing Item:
v IOP Failing Item:
v MA_BRDG v AJDGP01
v IOP
570BB410 v FI01104
v MA_BRDG
occurred.
570BFF3D
Failing Item:
Failing Item:
570BB411 v STORIOA
occurred.
Failing Item: 570BFF6D
system bus error.
570BB412 Failing Item:
occurred. v ANYBUS

Failing Item:
571A1310
v FI01101
v ANYBRDG
Response: The I/O adapter error log is being filled
571A3006
them. Explanation: System bus error.
Failing Item:
571A3000 v FI01101
Explanation: A permanent failure occurred. v ANYBRDG

571A3020 • 571A3121
v PTFSRCH v FI01140
v DEVBPLN
571A3020
Explanation: SCSI bus configuration error. 571A3101
Response: Error occurred on SCSI bus 0. Explanation: Interface error.

v USER v IOPIP13
v FI01107 v FI01107
v STORIOA v STORIOA
v FI01140
571A3021 v DEVBPLN
Explanation: SCSI bus configuration error.
571A3102
Failing Item:
v IOPIP17 Response: Error occurred on SCSI bus 2.
v FI01107 v IOPIP13
v STORIOA v FI01107
v STORIOA
571A3022 v FI01140
Explanation: SCSI bus configuration error. v DEVBPLN

571A3103
Failing Item:
v IOPIP17
v USER Response: Error occurred on SCSI bus 3.
v STORIOA v IOPIP13
v FI01107
571A3023 v STORIOA
Explanation: SCSI bus configuration error. v FI01140
v DEVBPLN
Failing Item:
571A3120
v IOPIP17
Explanation: Bus is not operational.
v USER
v FI01107 Response: Adding a device to SCSI bus 0 of the I/O
Adapter caused the bus to become not operational.
v STORIOA
Remove the device.
Failing Item:
571A3100
v SVCDOCS
Response: Error occurred on SCSI bus 0. 571A3121
Failing Item: Explanation: Bus is not operational.
v IOPIP13
Response: Adding a device to SCSI bus 1 of the I/O
v FI01107 Adapter caused the bus to become not operational.
v STORIOA Remove the device.

571A3122 • 571A3405

v SVCDOCS v SVCDOCS
571A3122 571A3151
Explanation: Bus is not operational. Explanation: SCSI bus configuration error.
Response: Adding a device to SCSI bus 2 of the I/O Response: Internal and external SCSI cables are
Adapter caused the bus to become not operational. connected to SCSI bus 1 at the same time. Correct the
Remove the device. SCSI bus 1 configuration.
v SVCDOCS v SVCDOCS
571A3123 571A3200
Explanation: Bus is not operational. Explanation: A tape/CD or disk device reported a
failure.
Adapter caused the bus to become not operational. Failing Item:
Remove the device. v FI01105
v SVCDOCS v MEDIA
571A3140 571A3202
Explanation: Bus is operational. Explanation: Storage subsystem configuration error.
Response: This reference code and the 3120 reference Response: The device is not supported in the current
code that occurred before it require no service action configuration. An I/O processor might be required.
because SCSI bus 0 is now operational.
Failing Item:
v SVCDOCS
571A3141
Explanation: Bus is operational. 571A3400
Response: This reference code and the 3121 reference Explanation: Device error.
code that occurred before it require no service action
because SCSI bus 1 is now operational. Response: NOTE: If external devices are attached
check EXTSCSI and DEVTERM first.

v FI02112
Explanation: Bus is operational.
v STORIOA
v FI01106
because SCSI bus 2 is now operational. v FI01140
571A3143 571A3401
Explanation: Bus is operational. Explanation: Device backplane problem.
code that occurred before it require no service action v DEVBPLN
571A3405
571A3150
Explanation: SCSI bus configuration error. initialization for a removable media device. This SRC is
model.

571A34FF • 571A4160
Response: Perform the following: v The RAID enablement card.

v Check the Product Activity Log for other entries that v The Battery charger and carrier card.
problems. See symbolic FRU FEATCRD for the location codes of
v Check the device firmware level and apply the latest the FRUs if they are not listed in the serviceable event
PTFs. or if you are working the failing item list here.
your next level of support with the information you Card type 57CB (embedded IOA with 2BCF battery
have gathered. card for embedded IOA) read the following: When
Problem determination: IPL the IOP to retry the failing item list here, the embedded storage adapter
device identification process. If the error persists then (STORIOA) has two physical parts:
contact your service provider. v The embedded storage adapter on the I/O
Failing Item: backplane.
v PTFSRCH v The Battery charger and carrier card.
See symbolic FRU FEATCRD for the location codes of

571A34FF the FRUs if they are not listed in the serviceable event
Explanation: A device on this adapter is being or if you are working the failing item list here.
formatted. Wait for the formatting to complete.
Failing Item: with 2BC2 dual battery charger and carrier card for the
v SVCDOCS embedded IOAs) read the following: When working
list here, the embedded storage adapters (STORIOA)
571A3501
have two physical parts:
Explanation: Licensed Internal Code error. v The embedded storage adapter on the DASD
Response: The device type is either unsupported or backplane.
the code has not been loaded to support it. v The dual battery charger and carrier card. To
Failing Item:
v FI01105 symbolic FRU CACHBAT.
v PTFSRCH
See symbolic FRU FEATCRD for the location code of
571A3601
listed in the serviceable event or if you are working the
Explanation: System log entry only. No service action failing item list here.
required.
Failing Item:
v BACKPLN
571A4150
v STORIOA
Response: If this event appears in a serviceable event 571A4160
PCI bus error.
adapter.
adapter.
here, the embedded storage adapter (STORIOA) has
three physical parts: Card type 2BE1 (feature RAID enablement card for

571A8008 • 571A8140
here, the embedded storage adapter (STORIOA) has Failing Item:

three physical parts: v CACHBAT
v The embedded storage adapter on the I/O v STORIOA
backplane.
571A8009
See symbolic FRU FEATCRD for the location codes of Failing Item:
v CACHBAT
Card type 57CB (embedded IOA with 2BCF battery 571A8100

failing item list here, the embedded storage adapter Failing Item:
(STORIOA) has two physical parts: v PTFSRCH
backplane.
571A8130
See symbolic FRU FEATCRD for the location codes of Explanation: IOA detected recoverable device bus
the FRUs if they are not listed in the serviceable event error.
information only.
the FRUs from the serviceable event or the failing item 571A8131
have two physical parts: Explanation: IOA detected recoverable device bus
error.
backplane. Response: An error occurred on SCSI bus 1. No action
v The dual battery charger and carrier card. To is required. This reference code is logged for
determine which battery is connected to which information only.
symbolic FRU CACHBAT. 571A8132
See symbolic FRU FEATCRD for the location code of Explanation: IOA detected recoverable device bus
the dual battery charger and carrier card if it is not error.
listed in the serviceable event or if you are working the Response: An error occurred on SCSI bus 2. No action
failing item list here. is required. This reference code is logged for
Failing Item: information only.
v BACKPLN
v STORIOA 571A8133
571A8008 error.
Explanation: A permanent cache battery pack failure Response: An error occurred on SCSI bus 3. No action
occurred. is required. This reference code is logged for
information only.
action. Depending on the configuration of the system, 571A8140
Source drive. If this is the case, this error will be posted Response: No action is required. This reference code
each time the IOA is IPLed and it can be ignored. is logged for information only.

571A8141 • 571A8400
571A8141 571A8157
Explanation: IOA detected recoverable device error. Explanation: I/O adapter card error.
Response: No action is required. This reference code Response: Display the Service Action Log entry for
is logged for information only. this SRC. If the Failing Item indicates an I/O adapter,
then replace the I/O adapter. If the Failing Item
indicates SVCDOCS, then do NOT replace the I/O
571A8145
adapter. This is a recoverable error. Perform the
Explanation: A recoverable error occurred. following for the I/O processor that the I/O adapter is
attached to:
Failing Item:
1. If the I/O processor is not operable and disk units
v STORIOA are attached, use Hardware Service Manager to
re-IPL the IOP. Other resources attached to the IOP
571A8146 may then need to be Varied On.
2. If disk units are not attached, perform the "VRYCFG
RESET(*YES)" command to reset the IOP and Vary
Failing Item: On attached resources.
v SVCDOCS
571A8150
Explanation: A permanent failure occurred. 571A8300
Response: NOTE: Under a certain configuration, this Explanation: IOA hardware error or PCI bus error.
Failing Item:
the Storage IOA may have been altered and/or the v STORIOA
Storage IOA Cache may have been disabled to allow v ANYBRDG
attachment of OEM Storage that emulates a Load v PTFSRCH
571A8301
Failing Item:
v STORIOA Explanation: Not valid condition in Licensed Internal
Code.
v ANYBRDG
Failing Item:
571A8151 v PTFSRCH
v STORIOA
v PTFSRCH
v STORIOA
571A8155
Failing Item:
v SVCDOCS
v PTFSRCH
v STORIOA 571A8400
571A8156
Failing Item:
v PTFSRCH
Failing Item:
v PTFSRCH
v STORIOA

571A8404 • 571A9026
571A8404 571A9011
Explanation: System log entry only. No service action Explanation: Cache data belongs to devices other than
required. those attached.
Failing Item:
571A9000 v IOPIP32
v STORIOA hardware configuration.
Failing Item:
571A9001 v IOPIP20
571A9021
Failing Item:
v IOPIP33 Explanation: Array not functional due to present

v IOPIP20
Failing Item:
571A9022
v IOPIP16
v FI01105
v STORIOA
Failing Item:
v FI01140
v IOPIP22
v BACKPLN
v FI01106
571A9023
571A9008 Explanation: Array not functional due to present

expected by devices. Failing Item:
v IOPIP22
Failing Item:
v IOPIP25
571A9024
571A9009 Explanation: Array not functional due to present

assistance. Failing Item:
v IOPIP22
Failing Item:
v SVCDOCS
571A9025
571A9010 Explanation: Disk unit is not supported at its physical

location.
devices cannot be found. Failing Item:
v IOPIP21
Failing Item:
v IOPIP31
571A9026
Failing Item:

571A9027 • 571A9051
v IOPIP22
571A9032
571A9027
or failed.
unit should be replaced. Replace the device first if a
Failing Item: device is listed first in the Service Action Log. If a
v IOPIP34 device is not listed first in the Service Action Log then
perform the procedure.

v FI02112
detected. v IOPIP21

adapter. Either move all the devices in an array to 571A9040
another I/O adapter that supports arrays, or stop an Explanation: Array protection temporarily suspended.
Failing Item: automatically restarted.
v SVCDOCS
571A9041
571A9029
Explanation: Incorrect hardware configuration change and corrected errors.
detected.
Response: Contact your next level of support. the problem.
v SVCDOCS v PTFSRCH
571A902F 571A9042
Explanation: Array addendum Product Activity Log Explanation: An array parity error has been detected
entry. and corrected.
Response: This entry contains additional array Response: Call your next level of support to report
information for 90xx reference codes when the array the problem.
Failing Item:
the starting point for this problem. v NEXTLVL
571A9030 571A9050
Explanation: Array no longer protected due to Explanation: Required cache data cannot be located
missing or failed disk unit. for a disk unit.

v FI02112 v IOPIP30
v IOPIP21
571A9051
571A9031 Explanation: Cache data exists for a missing or failed
device.
reference code.
failing item list.

571A9052 • 571A9091
Failing Item:
571A9073
v IOPIP27
571A9052
Failing Item:
v IOPIP40
been modified.
571A9081
Failing Item:
v SVCDOCS
Failing Item:
v FI01105
571A9053
v STORIOA
previous problems.
571A9082
Response: Take action on other reference codes which
have surfaced. Explanation: Device error.
If you cannot get to SST or DST, and cannot perform a Failing Item:
type A or B IPL, perform a type D IPL from removable v IOPIP16
v STORIOA
v SVCDOCS v BACKPLN
v FI01106
571A9054
Explanation: IOA resources not available due to 571A9090
previous problems.
Response: Power off the system and remove all new last known status.
or replacement disk units. IPL the system to DST. If
problem.
Look for Product Activity Log entries for other
level of support.
Failing Item:
Failing Item:
v SVCDOCS
v SVCDOCS
571A9071
571A9091
went operational.
detected.
571A9072 problem.
Explanation: Link from IOA to auxiliary cache IOA If you cannot resolve the problem, contact your next
went non-operational. level of support.
Response: No service action required. Failing Item:
v SVCDOCS

571A9092 • 571AFF6D
571A9092 571AFF6D
Explanation: Disk unit requires initialization before Explanation: Recoverable system bus error.
use.
Failing Item:
v IOPIP26 v ANYBRDG
v PTFSRCH
571A9500
Failing Item:
v PTFSRCH
571A9902
required.
571A9903
571AC000
required.
571AC100
required.
571AC402
assistance.
Failing Item:
v PTFSRCH
571AFF3D
Explanation: I/O adapter detected a recoverable error.
Failing Item:
v STORIOA
v ANYBRDG

571B1310 • 571B3102

v USER
571B1310
v FI01107
v STORIOA
571B3023
them. Explanation: SCSI bus configuration error.
571B3000
Failing Item:
Explanation: A permanent failure occurred. v IOPIP17
v FI01101 v FI01107
v ANYBRDG v STORIOA
571B3006 571B3100
Explanation: System bus error. Explanation: Interface error.
v ANYBRDG v IOPIP13
v PTFSRCH v FI01107
v STORIOA
571B3020 v FI01140
Explanation: SCSI bus configuration error. v DEVBPLN
571B3101
Failing Item:
v IOPIP17 Explanation: Interface error.
v USER Response: Error occurred on SCSI bus 1.
v STORIOA v IOPIP13
v FI01107
571B3021 v STORIOA
Explanation: SCSI bus configuration error. v FI01140
Response: Error occurred on SCSI bus 1. v DEVBPLN
Failing Item:
571B3102
v IOPIP17
v USER Explanation: Interface error.
v IOPIP13
571B3022 v FI01107
Explanation: SCSI bus configuration error. v STORIOA
v DEVBPLN
Failing Item:
v IOPIP17

571B3103 • 571B3200

571B3103
571B3141
Failing Item:
v IOPIP13 code that occurred before it require no service action
v FI01107 because SCSI bus 1 is now operational.
v STORIOA
v FI01140 571B3142
v DEVBPLN Explanation: Bus is operational.
571B3120 code that occurred before it require no service action
Explanation: Bus is not operational. because SCSI bus 2 is now operational.

Adapter caused the bus to become not operational. 571B3143
Remove the device. Explanation: Bus is operational.
v SVCDOCS code that occurred before it require no service action
571B3121
571B3150
Adapter caused the bus to become not operational. Response: Internal and external SCSI cables are
Remove the device. connected to SCSI bus 0 at the same time. Correct the
Failing Item:
v SVCDOCS
571B3122
571B3151
Adapter caused the bus to become not operational. Response: Internal and external SCSI cables are
Remove the device. connected to SCSI bus 1 at the same time. Correct the
Failing Item:
v SVCDOCS
571B3123
571B3200
failure.
Remove the device. Failing Item:
v SVCDOCS v STORIOA
v MEDIA
571B3140

571B3202 • 571B4150
571B3202 571B3501
Explanation: Storage subsystem configuration error. Explanation: Licensed Internal Code error.
Response: The device is not supported in the current Response: The device type is either unsupported or
configuration. An I/O processor might be required. the code has not been loaded to support it.
v SVCDOCS v FI01105
v PTFSRCH
571B3400
Explanation: Device error. 571B3601
Response: NOTE: If external devices are attached Explanation: System log entry only. No service action
check EXTSCSI and DEVTERM first. required.
Failing Item:
571B4150
v FI02112
v STORIOA Explanation: I/O adapter detected PCI bus error.
v FI01106 Response: If this event appears in a serviceable event
v FI01140 view, work with the failing item list found there. If this
571B3401
Explanation: Device backplane problem. the adapter has multiple physical parts. Choose the
Failing Item: card type to identify the physical parts of the storage
adapter.
v DEVBPLN
571B3405 FRUs from the serviceable event or the failing item list
Explanation: An error occurred during task here, the embedded storage adapter (STORIOA) has
initialization for a removable media device. This SRC is three physical parts:
logged when an error occurs and the removable media v The embedded storage adapter on the I/O
device driver cannot determine the device type or backplane.
model. v The RAID enablement card.
Response: Perform the following: v The Battery charger and carrier card.
indicate interface problems and work those See symbolic FRU FEATCRD for the location codes of
problems. the FRUs if they are not listed in the serviceable event
v Check the device firmware level and apply the latest or if you are working the failing item list here.
PTFs.
have gathered.
Problem determination: IPL the IOP to retry the (STORIOA) has two physical parts:
device identification process. If the error persists then v The embedded storage adapter on the I/O
contact your service provider. backplane.
v PTFSRCH
571B34FF or if you are working the failing item list here.
Explanation: A device on this adapter is being
formatted. Wait for the formatting to complete. Card type 57CF (embedded IOAs on DASD backplane
Failing Item: embedded IOAs) read the following: When working
v SVCDOCS

571B4160 • 571B8130
the FRUs from the serviceable event or the failing item Card type 57CF (embedded IOAs on DASD backplane
list here, the embedded storage adapters (STORIOA) with 2BC2 dual battery charger and carrier card for the
have two physical parts: embedded IOAs) read the following: When working
v The embedded storage adapter on the DASD the FRUs from the serviceable event or the failing item
backplane. list here, the embedded storage adapters (STORIOA)
determine which battery is connected to which v The embedded storage adapter on the DASD
embedded IOA use the bus number of the IOA with backplane.
symbolic FRU CACHBAT. v The dual battery charger and carrier card. To
See symbolic FRU FEATCRD for the location code of embedded IOA use the bus number of the IOA with
the dual battery charger and carrier card if it is not symbolic FRU CACHBAT.
failing item list here. See symbolic FRU FEATCRD for the location code of
Failing Item:
v BACKPLN failing item list here.
v STORIOA
Failing Item:
v BACKPLN
571B4160
v STORIOA
PCI bus error.
571B8008
occurred.
service action is required. Response: NOTE: Under a certain configuration, this
adapter.
Card type 2BE1 (feature RAID enablement card for Source drive. If this is the case, this error will be posted
embedded IOA) read the following: When working the each time the IOA is IPLed and it can be ignored.
Failing Item:
three physical parts: v CACHBAT
backplane.
v The RAID enablement card. 571B8009
v The Battery charger and carrier card. Explanation: Impending cache battery pack failure.
See symbolic FRU FEATCRD for the location codes of Failing Item:
the FRUs if they are not listed in the serviceable event v CACHBAT
571B8100
card for embedded IOA) read the following: When Explanation: Licensed Internal Code error.
Failing Item:
(STORIOA) has two physical parts: v PTFSRCH
backplane.
v The Battery charger and carrier card. 571B8130
error.
or if you are working the failing item list here. Response: An error occurred on SCSI bus 0. No action

571B8131 • 571B8157

571B8150
information only.
571B8131 Response: NOTE: Under a certain configuration, this
error.
Response: An error occurred on SCSI bus 1. No action Storage IOA Cache may have been disabled to allow
is required. This reference code is logged for attachment of OEM Storage that emulates a Load
information only. Source drive. If this is the case, this error will be posted
error. v ANYBRDG
is required. This reference code is logged for 571B8151
information only.
Failing Item:
571B8133
v PTFSRCH
v STORIOA
error.
571B8155
information only. Explanation: A permanent failure occurred.
Failing Item:
571B8140 v PTFSRCH
error.
Response: No action is required. This reference code 571B8156
Failing Item:
571B8141
v PTFSRCH
v STORIOA
571B8157
571B8145
Explanation: A recoverable error occurred.
this SRC. If the Failing Item indicates an I/O adapter,
Failing Item: then replace the I/O adapter. If the Failing Item
v STORIOA indicates SVCDOCS, then do NOT replace the I/O
following for the I/O processor that the I/O adapter is
571B8146 attached to:
Explanation: Disk device detected recoverable error. 1. If the I/O processor is not operable and disk units
are attached, use Hardware Service Manager to
Failing Item: re-IPL the IOP. Other resources attached to the IOP
v FI01105 may then need to be Varied On.
On attached resources.
Failing Item:

571B8300 • 571B9021
v SVCDOCS
571B9002
571B8300
Failing Item:
v IOPIP16
Failing Item:
v FI01105
v STORIOA
v STORIOA
v ANYBRDG
v FI01140
v PTFSRCH
v BACKPLN
v FI01106
571B8301
Explanation: Not valid condition in Licensed Internal 571B9008
Code.
Failing Item: expected by devices.
v PTFSRCH
Failing Item:
v STORIOA
v IOPIP25
571B8302
571B9009
Response: Ensure that the code necessary to support assistance.
Failing Item:
v SVCDOCS
v STORIOA 571B9010
571B8400 devices cannot be found.
v PTFSRCH
571B9011
571B8404 Explanation: Cache data belongs to devices other than
Explanation: System log entry only. No service action those attached.
v IOPIP32
571B9000
v IOPIP20
571B9001
Explanation: Device configuration error. 571B9021

v IOPIP33
Failing Item:
v IOPIP20

571B9022 • 571B9040
571B9022 571B9029
hardware configuration. detected.
v SVCDOCS
571B9023
Explanation: Array not functional due to present 571B902F
571B9024 contains more than 10 members. Use the 90xx entry
v IOPIP22
571B9025
Failing Item:
Explanation: Disk unit is not supported at its physical v FI02112
location.
v IOPIP21
Failing Item:
v IOPIP21 571B9031
571B9026
Explanation: Array not functional due to present and was automatically restarted, or a hot spare disk
hardware configuration. unit was used to automatically rebuild the array. Look
Failing Item: for other reference codes and take action on them.
v IOPIP22
571B9032
571B9027 Explanation: A disk unit in a RAID array is missing

or failed.
hardware configuration. Response: The array is still protected, but the disk
Failing Item: device is listed first in the Service Action Log. If a
v IOPIP34 device is not listed first in the Service Action Log then
Explanation: Incorrect hardware configuration change v FI02112
detected. v IOPIP21
adapter. Either move all the devices in an array to 571B9040
array on this I/O adapter. Explanation: Array protection temporarily suspended.
Failing Item: Response: No action required. Protection will be

v SVCDOCS

571B9041 • 571B9082

571B9041
Explanation: Background array parity check detected reference codes and take action on them.
Failing Item:
Response: Call your next level of support to report v SVCDOCS
the problem.
v PTFSRCH
previous problems.
571B9042
Explanation: An array parity error has been detected or replacement disk units. IPL the system to DST. If
and corrected. you cannot perform a type A or B IPL, perform a type
the problem. Look for Product Activity Log entries for other
Failing Item:
v SVCDOCS
571B9050
571B9071
for a disk unit. Explanation: Link from IOA to auxiliary cache IOA
went operational.
Failing Item:
v IOPIP30 Response: No service action required.
571B9051 571B9072
Explanation: Cache data exists for a missing or failed Explanation: Link from IOA to auxiliary cache IOA
device. went non-operational.
If so, perform the action indicated for the 9054 571B9073
reference code.
Otherwise, perform the procedure indicated in the auxiliary cache IOA attached.
failing item list.
Failing Item:
Failing Item:
v IOPIP40
v IOPIP27
571B9081
571B9052
v FI01105
v STORIOA
Failing Item:
v SVCDOCS
571B9082
571B9053
Failing Item:
v FI01105
have surfaced. v STORIOA
v FI01140

571B9090 • 571BFF6D
v BACKPLN
571BC000
v FI01106
required.
571B9090
Explanation: Disk unit has been modified after the is logged for information only.
last known status.
Response: Re-IPL the system. If any reference codes 571BC100
problem. Explanation: System log entry only. No service action
required.
level of support. Response: No action is required. This reference code
Failing Item:
v SVCDOCS
571BC402
571B9091
assistance.
detected.
Failing Item:
are surfaced, use the new reference code to resolve the v PTFSRCH
problem.
If you cannot resolve the problem, contact your next 571BFF3D
v SVCDOCS v STORIOA
v ANYBRDG
571B9092
Explanation: Disk unit requires initialization before 571BFF6D
use.
Explanation: Recoverable system bus error.
Failing Item:
Failing Item:
v IOPIP26
v STORIOA
v ANYBRDG
571B9500
v PTFSRCH
Failing Item:
v PTFSRCH
571B9902
required.
571B9903

572A1310 • 572A4020

572A1310 572A3401
v DEVBPLN
them.
572A3405
572A3000
model.
v ANYBRDG
572A3020 v Check the Product Activity Log for other entries that
v SIP3150 PTFs.
572A3100 have gathered.
v SIP3150
Failing Item:
572A3140 v PTFSRCH

required. 572A34FF
572A3202 Response: No action required. This reference code is

configuration. An I/O processor might be required. 572A3601

required.
v SVCDOCS
572A4010
572A3400
Failing Item:
enclosures.
v SIP3150
Failing Item:
v FI02112
v SIP3142
v STORIOA
v SASCABL
572A4020

572A4030 • 572A4160

572A4070
design limits.
Failing Item:
required.
v SIP3143
572A4100
572A4030
Failing Item:
v SIP3152
v SIP3144 v SASEXP
v DEVBPLN
572A4040 v STORIOA
I/O adapter and enclosure. 572A4101

v SIP3152
572A4041
Explanation: Incomplete multipath connection. 572A4110
v SIP3146 v SIP3145
572A4050 572A4150
multipath function.

v BACKPLN
v STORIOA
failed.
572A4160
Failing Item:
v SASCABL
572A4061 service action is required.

v BACKPLN

572A70DD • 572A8155
Failing Item:
572A70DD
v SIP3150
successfully.
572A8141
572A8008 Explanation: IOA detected recoverable device error.

may not represent an error that requires a service 572A8145
v CACHBAT v NEXTLVL
v STORIOA
v FEATCRD 572A8146
572A8009
Failing Item:
v CACHBAT
572A8100

v STORIOA
error. v ANYBRDG

view, work with the failing item list found there. If this 572A8151
Failing Item:
Failing Item:
v PTFSRCH
v SIP3150
v STORIOA
572A8140
572A8155


572A8156 • 572A8301
Failing Item:
572A8156
v SVCDOCS
v STORIOA
Failing Item:
v PTFSRCH 572A8300
v STORIOA
572A8157
this procedure.
ends the procedure.
operational status.
v PTFSRCH
operational then use Hardware Service Manager 572A8301
Failing Item:
I/O adapter.

572A8302 • 572A9025
572A8302 572A9011
those attached.
v SVCDOCS
v STORIOA 572A9020
572A8400 RAID-5 or RAID-6 array.

v SIP3111
Failing Item:
v PTFSRCH
572A9021
572A8404 Explanation: Two or more disk units missing from

v SIP3111
572A9000
572A9022
Failing Item:
v FI01105
Failing Item:
v STORIOA
v SIP3111
572A9001
572A9023
v NEXTLVL
Failing Item:
v SIP3112
572A9002
Explanation: Device error. 572A9024
Failing Item:
572A9008 v NEXTLVL
expected by devices. 572A9025
v SIP3130
572A9010 exposed.

v SIP3120

572A9026 • 572A9052
572A9026 572A9032
location. failed.
v NEXTLVL v SIP3110
v FI02112
572A9027
Explanation: Array not functional due to parity out of 572A9040
Failing Item:
v SIP3113 572A9041
572A9028 and corrected errors.
572A9042
Failing Item:
v SVCDOCS
on disk unit.
572A9029
the problem.
Failing Item:
v NEXTLVL
v NEXTLVL
more disk units.
572A9030
Failing Item:
v SIP3110
Failing Item:
572A9031
v SIP3132
Response: Either a previous rebuild was interrupted 572A9052
modified devices.

572A9054 • 572A9091
Failing Item:
572A9076
v NEXTLVL

v SIP3147
previous problems.
572A9081
Failing Item:
Failing Item:
572A9055 v FI01105
storage IOA.
Response: No service action required. 572A9082
required. v STORIOA
572A9071 572A9083
572A9084
572A9072 Explanation: System log entry only. No service action
Response: No service action required. 572A9090
572A9073 last known status.
v SIP3140
572A9074
Failing Item:
v SIP3141
detected.
572A9075
Failing Item:

572A9092 • 572B3401

572AC000
level of support.
required.
Failing Item:
572A9092 572AC402
use.
v SIP3134
Failing Item:
v PTFSRCH
572A9500
Explanation: Internal program error in driver code. 572AFF3D
v PTFSRCH
Failing Item:
v STORIOA
572A9903
v ANYBRDG

572B1310
required.
Response: The I/O adapter error log is being filled 572B3202
Failing Item:
572B3400
v STORIOA
Failing Item:
572B3020 v SIP3150
v STORIOA
Failing Item:
v SASCABL
v SIP3150
572B3401
572B3100
Failing Item:
Failing Item:
v SASEXP
v SIP3150
v DEVBPLN
572B3140

572B3405 • 572B4100
v SIP3144
572B3405
572B4040
Failing Item:
problems.
v Check the device firmware level and apply the latest 572B4041
PTFs.

multipath function.
572B34FF Failing Item:
logged for information only. 572B4060
572B3601
required.
Failing Item:
v SIP3153
572B4010
v SASCABL
enclosures. 572B4061
v SIP3142
572B4020
Explanation: Configuration error. 572B4070
Failing Item:
v SIP3143 572B4100
Explanation: Configuration error. v SIP3152
Response: Incorrect multipath connection. v SASCABL
v SASEXP
Failing Item:

572B4101 • 572B8141
v CACHBAT
572B4101 v STORIOA
Failing Item:
572B8009
v SIP3152
572B4110
Failing Item:
detected. v CACHBAT
Failing Item:
572B8100
v SIP3145
Explanation: I/O adapter detected PCI bus error. v PTFSRCH
v STORIOA
event does not appear in a serviceable event view, no 572B8130
572B4160
Failing Item:
PCI bus error. v SIP3150

view, work with the failing item list found there. If this 572B8140
event does not appear in a serviceable event view, no Explanation: IOA detected recoverable device bus
572B70DD Failing Item:

v SIP3150
successfully.
572B8141
572B8008 Explanation: IOA detected recoverable device error.

572B8145 • 572B8157
572B8145 572B8157
Explanation: Disk device detected recoverable error. Explanation: I/O adapter card error. The actions and
to determine the part number and location code of the Response: The FRU list in the Service Action Log will
device. vary based on the conditions this event was logged for.
Failing Item:
v NEXTLVL
572B8146 step. Do NOT replace the I/O adapter. This is a
Explanation: Disk device detected recoverable error. recoverable error.
v FI01105 resources attached to the virtual I/O processor
572B8150 v If the virtual I/O processor or adapter are not
Response: Under a certain configuration, this SRC Vary On attached resources.
572B8151 step. Do NOT replace the I/O adapter. This is a
recoverable error.
v STORIOA
572B8155 to manually re-IPL the virtual I/O processor and
I/O adapter.
572B8156
Failing Item:
v SVCDOCS
Failing Item:
v STORIOA
v PTFSRCH
v STORIOA

572B8300 • 572B9011
Failing Item:
572B8300
v SVCDOCS
v STORIOA
1. Examine the location code of the adapter to 572B8400
ends the procedure.
v PTFSRCH
event at about the same time, continue with the 572B8404
3. Suspect a problem with the connection to the required.
connection or cable(s) to the unit. If the adapter 572B9000
Failing Item:
this procedure.
572B9001
Failing Item:
FRU fault indicators for those adapters. Use the 572B9002
572B9008
Failing Item:
v STORIOA Explanation: I/O card does not support functions
v ANYBRDG
v SIP3130
572B8301
572B9010
Failing Item:
v STORIOA v SIP3120
572B8302 572B9011
those attached.
v NEXTLVL

572B9020 • 572B9032
572B9020 572B9027
Explanation: Two or more disk units missing from Explanation: Array not functional due to parity out of
RAID-5 or RAID-6 array. synchronization.
Failing Item: Response: Array is or would become exposed and
Failing Item:
572B9021 v SIP3113
RAID-5 or RAID-6 array. 572B9028
Failing Item: Explanation: Maximum number of functional arrays
572B9022 adapter. Either move all the devices in an array to
Failing Item:
Failing Item:
v SVCDOCS
v SIP3111
572B9029
572B9023
Failing Item:
Failing Item:
v SIP3112
v NEXTLVL
572B9024
572B9030
Failing Item:
Failing Item:
v NEXTLVL
v SIP3110
v FI02112
572B9025
572B9031
exposed. Response: Either a previous rebuild was interrupted
Failing Item:
v SIP3110 for other reference codes and take action on them.
v FI02112
572B9032
572B9026
Explanation: Disk unit not found at required physical failed.
location.
Response: A previously exposed disk unit in an array unit should be replaced.
Failing Item:
v NEXTLVL v FI02112

572B9040 • 572B9076
572B9040 572B9055
572B9041 572B9070
the problem. 572B9071
572B9042
Explanation: Background parity check corrected errors 572B9072
Failing Item:
v NEXTLVL 572B9073
572B9050 valid configuration.
Explanation: Required cache data not found for one or Failing Item:
Failing Item:
v SIP3131 572B9074
572B9051 valid configuration.
Explanation: Cache data exists for one or more Response: Multiple I/O adapters not capable of
missing or failed devices. similar functions or controlling the same set of devices.
v SIP3132 v SIP3141
572B9052 572B9075
Explanation: Cache data exists for one or more Explanation: Incomplete multipath connection
modified devices. between IOA and remote IOA.
v NEXTLVL
572B9076
572B9054 Explanation: Missing auxiliary IOA or remote IOA.
Explanation: IOA resources not available due to Failing Item:
previous problems. v SIP3147
Failing Item:
v SIP3121

572B9081 • 572C3000

572B9081
v STORIOA v SVCDOCS
572B9082 572B9092
Explanation: Device error. Explanation: Disk unit requires initialization before
Failing Item: use.
v STORIOA v SIP3134
572B9083 572B9500
Explanation: System log entry only. No service action Explanation: Internal program error in driver code.
required.
Failing Item:
v PTFSRCH
572B9084
Explanation: System log entry only. No service action 572B9903
required.
572B9090
Explanation: Disk unit has been modified after the 572BC000
last known status.
I/O adapter. Other resources attached to the virtual Response: No action is required. This reference code
I/O processor may then need to be Varied On. is logged for information only.

reference code to resolve the problem. 572BC402
If you cannot resolve the problem, contact your next Explanation: Licensed Internal Code error.
v PTFSRCH
572B9091
Explanation: Incorrect hardware configuration change 572BFF3D
detected. Explanation: I/O adapter detected a recoverable error.
Response: Use Hardware Service Manager to re-IPL Failing Item:
I/O adapter. Other resources attached to the virtual v STORIOA
I/O processor may then need to be Varied On. v ANYBRDG

572C1310
them.
Response: The I/O adapter error log is being filled 572C3000

572C3020 • 572C4030
Explanation: A permanent failure occurred. Response: Perform the following:

Failing Item: v Check the Product Activity Log for other entries that
v STORIOA
problems.
v ANYBRDG
PTFs.
572C3020 v Check for LIC logs with major code 2E00. Contact
Explanation: Storage subsystem configuration error. your next level of support with the information you
have gathered.
Failing Item:
v SIP3150 device identification process. If the error persists then
Explanation: Device bus interface error occurred. v PTFSRCH
Failing Item:
v SIP3150 572C34FF
572C3140 Response: No action required. This reference code is
Explanation: System log entry only. No service action logged for information only.
required.
572C3601
572C3202 Explanation: System log entry only. No service action
Explanation: Storage subsystem configuration error. required.

configuration. An I/O processor might be required. 572C4010
Failing Item: Explanation: Configuration error.

v SVCDOCS Response: Incorrect connection between cascaded
enclosures.
Explanation: Unknown resource error. v SIP3142
Failing Item:
572C4020
v SIP3150
v FI02112 Explanation: Configuration error.
v STORIOA Response: Number of connections exceed I/O adapter
v SASCABL design limits.
Failing Item:
572C3401 v SIP3143
572C4030
Failing Item:
v SASEXP Explanation: Configuration error.
v DEVBPLN Response: Incorrect multipath connection.
Failing Item:
572C3405 v SIP3144
model.

572C4040 • 572C8008
v FI01105
572C4040
572C4101
Explanation: Temporary device bus fabric error.
Failing Item:
Failing Item:
v SIP3152
v SIP3144
572C4110
572C4041
detected.
Failing Item:
v SIP3145
Failing Item:
v SIP3146
572C4150
572C4050
Explanation: Enclosure does not support required
multipath function.
v BACKPLN
572C4060 v STORIOA
Response: A redundant disk unit connection has 572C4160
failed. Explanation: I/O adapter detected and recovered a
Failing Item: PCI bus error.
v SASCABL view, work with the failing item list found there. If this
v SASEXP
Failing Item:
572C4061
v BACKPLN
v STORIOA
572C70DD
572C4070
successfully.
required.
572C8008
572C4100
cache battery pack or capacitive cache power card.
Failing Item: may not represent an error that requires a service
v SIP3152 action. Depending on the configuration of the system,
v SASCABL Storage IOA Cache may have been disabled to allow
v SASEXP attachment of OEM Storage that emulates a Load
v STORIOA

572C8009 • 572C8157

v CACHBAT v NEXTLVL
v STORIOA
v FEATCRD 572C8146
572C8009
Failing Item:
v CACHBAT
572C8100
Failing Item:

error. v ANYBRDG
view, work with the failing item list found there. If this 572C8151
Failing Item:
Failing Item:
v PTFSRCH
v SIP3150
v STORIOA
572C8140
572C8155

v SIP3150
Failing Item:
572C8141
v PTFSRCH
v STORIOA
572C8157
572C8145
Explanation: Disk device detected recoverable error. based on the conditions this event was logged for.
Response: This error is logged against the storage Response: The FRU list in the Service Action Log will
controller resource. Contact your next level of support vary based on the conditions this event was logged for.
to determine the part number and location code of the Perform the following:
device. 1. Display the Service Action Log entry for this SRC.

572C8300 • 572C8400
2. If the Failing Item indicates SVCDOCS, then 3. Suspect a problem with the connection to the
continue with this step. Otherwise go to the next enclosure. The problem may have been temporary
step. Do NOT replace the I/O adapter. This is a while working on the unit or while working on the
recoverable error. connection or cable(s) to the unit. If the adapter
v LIC will automatically re-IPL the virtual I/O problems were created while working on the unit or
processor associated with the adapter. Other working on the connection to the unit, go to step 5.
resources attached to the virtual I/O processor 4. Search for problems logged at about the same time
may need to be Varied On. and call out the FRUs that connect the expansion
v If the virtual I/O processor or adapter are not unit to the system unit including the cable(s). Work
operational then use Hardware Service Manager those problems first, then return to the next step in
to manually re-IPL the virtual I/O processor and this procedure.
Vary On attached resources. 5. Use Hardware Service Manager (HSM) to verify
v If manually reIPL-ing the virtual I/O processor that the adapters have returned to operational
fails then contact your next level of support. This status. Close reference code xxxx8300 problems for
ends the procedure. adapters that have returned to operational status.
Expansion units attached to system units using
FRU fault indicators for those adapters. Use the
Problem determination: Perform the following: operational status.
1. Display the Service Action Log entry for this SRC. 6. Work reference code xxxx8300 problems for any
step. Do NOT replace the I/O adapter. This is a Failing Item:
recoverable error.
v STORIOA
v ANYBRDG
resources attached to the virtual I/O processor v PTFSRCH
v If the virtual I/O processor or adapter are not 572C8301
Code.
v If manually reIPL-ing the virtual I/O processor Failing Item:
fails then contact your next level of support. This v PTFSRCH
ends the procedure. v STORIOA
I/O adapter. 572C8302

v SVCDOCS Response: Ensure that the code necessary to support
v STORIOA this I/O adapter is loaded.
Failing Item:
572C8300 v SVCDOCS
Explanation: IOA hardware error or PCI bus error. v STORIOA

572C8400
determine if the adapter is in the system unit or an Explanation: Licensed Internal Code error.
expansion unit. If the adapter is in an expansion
Failing Item:
unit, continue with the next step. Otherwise this

572C8404 • 572C9027
572C8404 572C9021
Explanation: System log entry only. No service action Explanation: Two or more disk units missing from
required. RAID-5 or RAID-6 array.
Failing Item:
572C9000 v SIP3111
v FI01105 Explanation: Two or more disk units missing from
v STORIOA RAID-5 or RAID-6 array.
Failing Item:
572C9001 v SIP3111
572C9023
Failing Item:
v NEXTLVL Explanation: One or more array members not in

v SIP3112
Failing Item:
572C9024
v NEXTLVL
with another array.
572C9008
Failing Item:
v NEXTLVL
Failing Item:
572C9025
v SIP3130
572C9010 Response: An incompatible device is at the physical

Explanation: Cache data associated with attached exposed.
Failing Item:
Failing Item:
v SIP3110
v SIP3120
v FI02112
572C9011
572C9026
those attached.
location.
Failing Item:
v NEXTLVL was not found at the required physical location.
Failing Item:
572C9020
v NEXTLVL
572C9027
Failing Item:
v SIP3111 synchronization.

572C9028 • 572C9055
Failing Item:
572C9041
v SIP3113
572C9028
Explanation: Maximum number of functional arrays the problem.
has been exceeded.
Failing Item:
v NEXTLVL
array on this I/O adapter. 572C9042
Failing Item: Explanation: Background parity check corrected errors
v SVCDOCS on disk unit.
572C9029 the problem.
Explanation: Maximum number of functional array Failing Item:

members has been exceeded. v NEXTLVL
572C9050
Failing Item:
v NEXTLVL Explanation: Required cache data not found for one or
more disk units.

v SIP3131
572C9051
Failing Item:
v SIP3110 Explanation: Cache data exists for one or more
v FI02112
Failing Item:
572C9031 v SIP3132

572C9052
and was automatically restarted, or a hot spare disk Explanation: Cache data exists for one or more
unit was used to automatically rebuild the array. Look modified devices.
for other reference codes and take action on them. Response: Contact your next level of support.
Failing Item:
572C9032
v NEXTLVL
failed.
572C9054
previous problems.
Failing Item:
Failing Item:
v SIP3110
v SIP3121
v FI02112
572C9055
572C9040
Explanation: Re-synchronization of array parity was storage IOA.
initiated.

572C9070 • 572C9092
572C9070 572C9082
Explanation: System log entry only. No service action Explanation: Device error.
required.
Failing Item:
v FI01105
572C9071
v STORIOA
IOA is operational.
572C9083
required.
572C9072
Explanation: Link from IOA to auxiliary or remote 572C9084
Response: No service action required. required.
572C9073 572C9090
Explanation: Multiple I/O adapters connected in a not Explanation: Disk unit has been modified after the
valid configuration. last known status.
Failing Item: Response: Use Hardware Service Manager to re-IPL
v SIP3140 the virtual I/O processor that is associated with this
572C9074
Explanation: Multiple I/O adapters connected in a not reference code to resolve the problem.
Response: Multiple I/O adapters not capable of level of support.
Failing Item:
Failing Item:
v SVCDOCS
v SIP3141
572C9091
572C9075
Explanation: Incomplete multipath connection detected.
Failing Item: the virtual I/O processor that is associated with this
v SIP3149 I/O adapter. Other resources attached to the virtual
572C9076 If any reference codes are surfaced, use the new
v SIP3147
Failing Item:
v SVCDOCS
572C9081
Explanation: Device error. 572C9092
Failing Item: Explanation: Disk unit requires initialization before
v FI01105 use.
v SIP3134

572C9500 • 573BB300
572C9500 572CC402
Explanation: Internal program error in driver code. Explanation: Licensed Internal Code error.
Failing Item: Response: Ask your next level of support for
v PTFSRCH assistance.
Failing Item:
572C9903 v PTFSRCH
Informational event, no service required. 572CFF3D
572CC000
Failing Item:
Explanation: System log entry only. No service action v STORIOA
required.
v ANYBRDG

573AA001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
573AB9B0

573BA6D9 573BB200
Explanation: I/O adapter hardware error detected. Explanation: I/O adapter hardware error detected.
v IOA v AJDG301
v FI00722 v IOA
v AJDG301
573BB300
573BA6E3 Explanation: An I/O adapter hardware error was
Explanation: Ethernet adapter or network device detected.
cabling error. Response: Work the Failing Item list from the
Failing Item: serviceable event view if it is available, otherwise use
this Failing Item list.
v FI00722
v UJE40 Problem determination: Varying off and then varying
on the resource may resolve the problem. If that does
v IOA
not resolve the problem then have the service provider
work the problem.
573BB100
Failing Item:
v IOA
v AJDG301

573CA6D9 • 573D3023

Failing Item:
573CA6D9
v IOA
v AJDG301
Failing Item:
v IOA 573CB200
v FI00722
v AJDG301
Failing Item:
v AJDG301
573CA6E3
v IOA
Explanation: Ethernet adapter or network device
cabling error.
573CB300
Failing Item:
v FI00722
v UJE40 Failing Item:
v IOA v IOA
v AJDG301
573CB100

v IOPIP17
573D1310
v USER
v FI01107
Response: The I/O adapter error log is being filled v STORIOA
them. 573D3021
573D3000 Response: Error occurred on SCSI bus 1.
Explanation: A permanent failure occurred. Failing Item:
v FI01101 v USER
v ANYBRDG v FI01107
v STORIOA
573D3006
Explanation: System bus error. 573D3022
Failing Item: Explanation: SCSI bus configuration error.

v PTFSRCH v IOPIP17
v USER
573D3020 v FI01107
Explanation: SCSI bus configuration error. v STORIOA
573D3023
Failing Item:

573D3100 • 573D3141
Response: Error occurred on SCSI bus 3. v DEVBPLN

Failing Item:
v IOPIP17 573D3120
v USER Explanation: Bus is not operational.
v STORIOA Adapter caused the bus to become not operational.
Remove the device.
Explanation: Interface error. v SVCDOCS

573D3121
Failing Item:
v IOPIP13
v STORIOA
Remove the device.
v FI01140
Failing Item:
v DEVBPLN
v SVCDOCS
573D3101
573D3122
Failing Item: Adapter caused the bus to become not operational.
v IOPIP13 Remove the device.
v STORIOA v SVCDOCS
v FI01140
v DEVBPLN 573D3123
573D3102
Explanation: Interface error. Adapter caused the bus to become not operational.
Response: Error occurred on SCSI bus 2. Remove the device.
v IOPIP13 v SVCDOCS
v FI01107
v STORIOA 573D3140
v FI01140 Explanation: Bus is operational.
573D3103 because SCSI bus 0 is now operational.

573D3141
Failing Item:
v STORIOA
v FI01140

573D3142 • 573D3501
573D3142 573D3400
Explanation: Bus is operational. Explanation: Device error.
Response: This reference code and the 3122 reference Response: NOTE: If external devices are attached
code that occurred before it require no service action check EXTSCSI and DEVTERM first.
Failing Item:
v FI02112
573D3143
v STORIOA
Explanation: Bus is operational. v FI01106
573D3401
573D3150
Failing Item:
v DEVBPLN
SCSI bus 0 configuration. 573D3405
Failing Item: Explanation: An error occurred during task

v SVCDOCS
573D3151 model.
Explanation: SCSI bus configuration error. Response: Perform the following:
Response: Internal and external SCSI cables are v Check the Product Activity Log for other entries that
connected to SCSI bus 1 at the same time. Correct the indicate interface problems and work those
SCSI bus 1 configuration. problems.
Failing Item:
PTFs.
v SVCDOCS
573D3200 have gathered.
Explanation: A tape/CD or disk device reported a Problem determination: IPL the IOP to retry the
failure. device identification process. If the error persists then
Failing Item:
v STORIOA v PTFSRCH
v MEDIA
573D34FF
573D3202 Explanation: A device on this adapter is being

formatted. Wait for the formatting to complete.
Failing Item:
configuration. An I/O processor might be required. v SVCDOCS
Failing Item:
573D3501
v SVCDOCS
Response: The device type is either unsupported or
the code has not been loaded to support it.
Failing Item:
v FI01105

573D3601 • 573D4160
v PTFSRCH See symbolic FRU FEATCRD for the location code of

573D3601
failing item list here.
Failing Item:
required.
v BACKPLN
v STORIOA
573D4150
573D4160
PCI bus error.
adapter. If you are working with one of the card types below,
adapter.
here, the embedded storage adapter (STORIOA) has Card type 2BE1 (feature RAID enablement card for
three physical parts: embedded IOA) read the following: When working the
v The embedded storage adapter on the I/O FRUs from the serviceable event or the failing item list
backplane. here, the embedded storage adapter (STORIOA) has
three physical parts:
backplane.
See symbolic FRU FEATCRD for the location codes of v The RAID enablement card.
the FRUs if they are not listed in the serviceable event v The Battery charger and carrier card.
Card type 57CB (embedded IOA with 2BCF battery the FRUs if they are not listed in the serviceable event
card for embedded IOA) read the following: When or if you are working the failing item list here.
failing item list here, the embedded storage adapter Card type 57CB (embedded IOA with 2BCF battery
(STORIOA) has two physical parts: card for embedded IOA) read the following: When
v The embedded storage adapter on the I/O working the FRUs from the serviceable event or the
backplane. failing item list here, the embedded storage adapter
(STORIOA) has two physical parts:
See symbolic FRU FEATCRD for the location codes of backplane.
the FRUs if they are not listed in the serviceable event v The Battery charger and carrier card.
Card type 57CF (embedded IOAs on DASD backplane the FRUs if they are not listed in the serviceable event
with 2BC2 dual battery charger and carrier card for the or if you are working the failing item list here.
the FRUs from the serviceable event or the failing item Card type 57CF (embedded IOAs on DASD backplane
list here, the embedded storage adapters (STORIOA) with 2BC2 dual battery charger and carrier card for the
have two physical parts: embedded IOAs) read the following: When working
v The embedded storage adapter on the DASD the FRUs from the serviceable event or the failing item
backplane. list here, the embedded storage adapters (STORIOA)
determine which battery is connected to which v The embedded storage adapter on the DASD
embedded IOA use the bus number of the IOA with backplane.

573D8008 • 573D8150

573D8131
embedded IOA use the bus number of the IOA with Explanation: IOA detected recoverable device bus
symbolic FRU CACHBAT. error.
information only.
573D8132
Failing Item:
v BACKPLN Explanation: IOA detected recoverable device bus
error.
v STORIOA
573D8008
information only.
occurred.
573D8133
error.
the Storage IOA may have been altered and/or the Response: An error occurred on SCSI bus 3. No action
Storage IOA Cache may have been disabled to allow is required. This reference code is logged for
attachment of OEM Storage that emulates a Load information only.
573D8140
Failing Item:
v CACHBAT error.
v STORIOA
573D8009
Explanation: Impending cache battery pack failure. 573D8141
Failing Item: Explanation: IOA detected recoverable device error.
v CACHBAT Response: No action is required. This reference code
573D8100
Explanation: Licensed Internal Code error. 573D8145
Failing Item: Explanation: A recoverable error occurred.

v STORIOA v STORIOA
573D8130 573D8146
Explanation: IOA detected recoverable device bus Explanation: Disk device detected recoverable error.
error.
Failing Item:
Response: An error occurred on SCSI bus 0. No action v FI01105
information only.
573D8150

573D8151 • 573D9001

573D8300
Source drive. If this is the case, this error will be posted Explanation: IOA hardware error or PCI bus error.
Failing Item:
v STORIOA v ANYBRDG
v ANYBRDG v PTFSRCH
573D8151 573D8301
Explanation: Licensed Internal Code error. Explanation: Not valid condition in Licensed Internal
Failing Item: Code.
v STORIOA v PTFSRCH
v STORIOA
573D8155
Explanation: A permanent failure occurred. 573D8302

v PTFSRCH Response: Ensure that the code necessary to support
Failing Item:
573D8156 v SVCDOCS
Explanation: A permanent failure occurred. v STORIOA
Failing Item:
573D8400
v PTFSRCH
v STORIOA Explanation: Licensed Internal Code error.
Failing Item:
573D8157 v PTFSRCH
573D8404
this SRC. If the Failing Item indicates an I/O adapter, Explanation: System log entry only. No service action
then replace the I/O adapter. If the Failing Item required.
indicates SVCDOCS, then do NOT replace the I/O
573D9000
following for the I/O processor that the I/O adapter is
attached to: Explanation: Device error.
1. If the I/O processor is not operable and disk units Failing Item:
re-IPL the IOP. Other resources attached to the IOP v FI01105
may then need to be Varied On. v STORIOA
RESET(*YES)" command to reset the IOP and Vary 573D9001
Failing Item:
Failing Item:
v SVCDOCS
v IOPIP33

573D9002 • 573D9028
573D9002 573D9022
Explanation: Device error. Explanation: Array not functional due to present
Failing Item:
v FI01105 v IOPIP22
v STORIOA
v FI01140 573D9023
v BACKPLN Explanation: Array not functional due to present
Failing Item:
573D9008 v IOPIP22
expected by devices. 573D9024
Failing Item:
573D9009 v IOPIP22
assistance. 573D9025
Failing Item: Explanation: Disk unit is not supported at its physical
v SVCDOCS location.
Failing Item:
573D9010 v IOPIP21
devices cannot be found. 573D9026
Failing Item:
573D9011 v IOPIP22
those attached. 573D9027
Failing Item:
573D9020 v IOPIP34
hardware configuration. 573D9028
v IOPIP20 detected.
573D9021 adapter. Either move all the devices in an array to
Explanation: Array not functional due to present array on this I/O adapter.
Failing Item:
Failing Item:
v SVCDOCS
v IOPIP20

573D9029 • 573D9053
573D9029 573D9041
Explanation: Incorrect hardware configuration change Explanation: Background array parity check detected
detected. and corrected errors.
Response: Contact your next level of support. Response: Call your next level of support to report
the problem.
Failing Item:
v PTFSRCH
573D902F
573D9042
entry. Explanation: An array parity error has been detected
and corrected.
information for 90xx reference codes when the array Response: Call your next level of support to report
contains more than 10 members. Use the 90xx entry the problem.
Failing Item:
v NEXTLVL
573D9030
573D9050
missing or failed disk unit. Explanation: Required cache data cannot be located
for a disk unit.
Failing Item:
Failing Item:
v FI02112
v IOPIP30
v IOPIP21
573D9051
573D9031
Explanation: Cache data exists for a missing or failed
device.
reference code.
573D9032
failing item list.
Failing Item:
or failed.
v IOPIP27
device is listed first in the Service Action Log. If a 573D9052
device is not listed first in the Service Action Log then Explanation: Cache data exists for device that has
perform the procedure. been modified.
v FI02112
Failing Item:
v IOPIP21
v SVCDOCS
573D9040
573D9053
Response: No action required. Protection will be previous problems.
have surfaced.

573D9054 • 573D9903

Failing Item: 573D9090
v SVCDOCS
last known status.
573D9054
Explanation: IOA resources not available due to are surfaced, use the new reference code to resolve the
Failing Item:
v SVCDOCS
Look for Product Activity Log entries for other
573D9091
Failing Item:
v SVCDOCS
detected.
573D9071
went operational.
Failing Item:
573D9072 v SVCDOCS
went non-operational. 573D9092
use.
Explanation: Incompatible or non-operational v IOPIP26
v IOPIP40 Explanation: Internal program error in driver code.
Failing Item:
573D9081
v PTFSRCH
v STORIOA required.
573D9082 573D9903
Explanation: Device error. Explanation: Tape device information was logged.
Failing Item:
v IOPIP16
v FI01105
v STORIOA
v FI01140

573DC000 • 573E3023
Failing Item:
573DC000
v PTFSRCH
required.
573DFF3D
is logged for information only. Explanation: I/O adapter detected a recoverable error.
Failing Item:
573DC100 v STORIOA
Explanation: System log entry only. No service action v ANYBRDG
required.
Response: No action is required. This reference code 573DFF6D
is logged for information only. Explanation: Recoverable system bus error.
Failing Item:
573DC402
v STORIOA
Explanation: Licensed Internal Code error. v ANYBRDG
Response: Ask your next level of support for v PTFSRCH
assistance.

573E1310 573E3021
Explanation: I/O adapter resource not available. Explanation: SCSI bus configuration error.
Failing Item:
them. v IOPIP17
v USER
573E3000 v FI01107
v STORIOA
Failing Item:
573E3022
v FI01101
v ANYBRDG
v USER
Failing Item:
v FI01107
v FI01101
v STORIOA
v ANYBRDG
v PTFSRCH
573E3023
573E3020 Explanation: SCSI bus configuration error.
Explanation: SCSI bus configuration error. Response: Error occurred on SCSI bus 3.

v IOPIP17
Failing Item:
v USER
v IOPIP17
v FI01107
v USER
v STORIOA
v FI01107
v STORIOA

573E3100 • 573E3142
Failing Item:
573E3100
v SVCDOCS
Response: Error occurred on SCSI bus 0. 573E3121
Failing Item: Explanation: Bus is not operational.
v IOPIP13
v FI01107 Adapter caused the bus to become not operational.
v DEVBPLN v SVCDOCS
573E3101 573E3122
Explanation: Interface error. Explanation: Bus is not operational.
Response: Error occurred on SCSI bus 1. Response: Adding a device to SCSI bus 2 of the I/O
Remove the device.
v IOPIP13
v STORIOA v SVCDOCS
v FI01140
v DEVBPLN 573E3123
573E3102 Response: Adding a device to SCSI bus 3 of the I/O
Remove the device.
Failing Item:
Failing Item:
v SVCDOCS
v IOPIP13
v FI01107
573E3140
v STORIOA
v FI01140
573E3103
Explanation: Interface error. 573E3141
Response: Error occurred on SCSI bus 3. Explanation: Bus is operational.
v STORIOA
v FI01140 573E3142
573E3120 code that occurred before it require no service action
Remove the device.

573E3143 • 573E4150
573E3143 573E3401
Explanation: Bus is operational. Explanation: Device backplane problem.
code that occurred before it require no service action v DEVBPLN
573E3405
573E3150
Explanation: SCSI bus configuration error. initialization for a removable media device. This SRC is
Response: Internal and external SCSI cables are logged when an error occurs and the removable media
connected to SCSI bus 0 at the same time. Correct the device driver cannot determine the device type or
SCSI bus 0 configuration. model.
Failing Item: Response: Perform the following:

v SVCDOCS v Check the Product Activity Log for other entries that
problems.
573E3151
Explanation: SCSI bus configuration error. PTFs.
Response: Internal and external SCSI cables are v Check for LIC logs with major code 2E00. Contact
connected to SCSI bus 1 at the same time. Correct the your next level of support with the information you
SCSI bus 1 configuration. have gathered.
Failing Item: Problem determination: IPL the IOP to retry the

v SVCDOCS contact your service provider.
Failing Item:
573E3200
v PTFSRCH
failure.
573E34FF
Failing Item:
Explanation: A device on this adapter is being
v FI01105 formatted. Wait for the formatting to complete.
v STORIOA
Failing Item:
v MEDIA
v SVCDOCS
573E3202
573E3501
configuration. An I/O processor might be required. Response: The device type is either unsupported or
the code has not been loaded to support it.
Failing Item:
Failing Item:
v SVCDOCS
v FI01105
v PTFSRCH
573E3400
Explanation: Device error. 573E3601
Response: NOTE: If external devices are attached Explanation: System log entry only. No service action
check EXTSCSI and DEVTERM first. required.
Failing Item:
v FI02112 573E4150
v STORIOA Explanation: I/O adapter detected PCI bus error.
v FI01106
v FI01140 view, work with the failing item list found there. If this

573E4160

573E4160
PCI bus error.
card type to identify the physical parts of the storage Response: If this event appears in a serviceable event
adapter. view, work with the failing item list found there. If this
FRUs from the serviceable event or the failing item list If you are working with one of the card types below,
here, the embedded storage adapter (STORIOA) has the adapter has multiple physical parts. Choose the
three physical parts: card type to identify the physical parts of the storage
v The embedded storage adapter on the I/O adapter.
backplane. Card type 2BE1 (feature RAID enablement card for
v The RAID enablement card. embedded IOA) read the following: When working the
v The Battery charger and carrier card. FRUs from the serviceable event or the failing item list
See symbolic FRU FEATCRD for the location codes of three physical parts:
the FRUs if they are not listed in the serviceable event v The embedded storage adapter on the I/O
or if you are working the failing item list here. backplane.
Card type 57CB (embedded IOA with 2BCF battery v The Battery charger and carrier card.
backplane. Card type 57CB (embedded IOA with 2BCF battery
v The Battery charger and carrier card. card for embedded IOA) read the following: When
See symbolic FRU FEATCRD for the location codes of failing item list here, the embedded storage adapter
the FRUs if they are not listed in the serviceable event (STORIOA) has two physical parts:
or if you are working the failing item list here. v The embedded storage adapter on the I/O
backplane.
Card type 57CF (embedded IOAs on DASD backplane v The Battery charger and carrier card.
v The embedded storage adapter on the DASD Card type 57CF (embedded IOAs on DASD backplane
backplane. with 2BC2 dual battery charger and carrier card for the
v The dual battery charger and carrier card. To embedded IOAs) read the following: When working
determine which battery is connected to which the FRUs from the serviceable event or the failing item
embedded IOA use the bus number of the IOA with list here, the embedded storage adapters (STORIOA)
symbolic FRU CACHBAT. have two physical parts:
See symbolic FRU FEATCRD for the location code of backplane.
Failing Item: symbolic FRU CACHBAT.
v BACKPLN
v STORIOA
Failing Item:

573E8008 • 573E8151
v BACKPLN
573E8133
v STORIOA
error.
573E8008
Explanation: A permanent cache battery pack failure is required. This reference code is logged for
SRC may not represent an error that requires a service 573E8140
attachment of OEM Storage that emulates a Load Response: No action is required. This reference code
Source drive. If this is the case, this error will be posted is logged for information only.
v CACHBAT
v STORIOA
573E8009
Explanation: Impending cache battery pack failure. 573E8145
Failing Item: Explanation: A recoverable error occurred.
v CACHBAT
Failing Item:
v STORIOA
573E8100
Explanation: Licensed Internal Code error. 573E8146
v PTFSRCH
Failing Item:
v STORIOA
v FI01105
573E8130
573E8150
error.
information only.
573E8131 attachment of OEM Storage that emulates a Load
error.
Failing Item:
is required. This reference code is logged for v STORIOA
information only. v ANYBRDG
573E8132 573E8151
Explanation: IOA detected recoverable device bus Explanation: Licensed Internal Code error.
error.
Failing Item:
Response: An error occurred on SCSI bus 2. No action v PTFSRCH
v STORIOA
information only.

573E8155 • 573E9008
573E8155 573E8302
Explanation: A permanent failure occurred. Explanation: Missing Licensed Internal Code.
Failing Item: Response: Ensure that the code necessary to support
v PTFSRCH this I/O adapter is loaded.
v SVCDOCS
573E8156 v STORIOA
573E8400
Failing Item:
v PTFSRCH Explanation: Licensed Internal Code error.
v PTFSRCH
573E8157
Explanation: I/O adapter card error. 573E8404
Response: Display the Service Action Log entry for Explanation: System log entry only. No service action
this SRC. If the Failing Item indicates an I/O adapter, required.
indicates SVCDOCS, then do NOT replace the I/O 573E9000
following for the I/O processor that the I/O adapter is Explanation: Device error.
attached to: Failing Item:
1. If the I/O processor is not operable and disk units v FI01105
re-IPL the IOP. Other resources attached to the IOP v STORIOA
may then need to be Varied On.
2. If disk units are not attached, perform the "VRYCFG 573E9001
Failing Item:
Failing Item:
v IOPIP33
v SVCDOCS
573E9002
573E8300
Failing Item:
Failing Item:
v IOPIP16
v STORIOA
v FI01105
v ANYBRDG
v STORIOA
v PTFSRCH
v FI01140
v BACKPLN
573E8301
v FI01106
Code.
573E9008
Failing Item:
v PTFSRCH
v STORIOA
Failing Item:
v IOPIP25

573E9009 • 573E902F
v IOPIP22
573E9009
573E9025
assistance.
Failing Item:
location.
v SVCDOCS
Failing Item:
v IOPIP21
573E9010
573E9026
Failing Item:
v IOPIP31
Failing Item:
v IOPIP22
573E9011
573E9027
those attached.
Failing Item:
v IOPIP32
Failing Item:
v IOPIP34
573E9020
573E9028
Failing Item:
detected.
v IOPIP20
573E9021 another I/O adapter that supports arrays, or stop an
hardware configuration. Failing Item:
v IOPIP20
573E9029
573E9022 Explanation: Incorrect hardware configuration change
Explanation: Array not functional due to present detected.
hardware configuration. Response: Contact your next level of support.
v IOPIP22 v SVCDOCS
573E9023 573E902F
Explanation: Array not functional due to present Explanation: Array addendum Product Activity Log
hardware configuration. entry.
Failing Item: Response: This entry contains additional array
573E9024
Failing Item:

573E9030 • 573E9054
573E9030 573E9050
v FI02112 v IOPIP30
v IOPIP21
573E9051
573E9031 Explanation: Cache data exists for a missing or failed
Explanation: Automatic rebuild initiated for array. device.
Response: Either a previous rebuild was interrupted Response: If all configured units are missing, a 9054
and was automatically restarted, or a hot spare disk reference code may appear in the product activity log.
unit was used to automatically rebuild the array. Look If so, perform the action indicated for the 9054
for other reference codes and take action on them. reference code.
573E9032 failing item list.
Explanation: A disk unit in a RAID array is missing Failing Item:

or failed. v IOPIP27
unit should be replaced. Replace the device first if a 573E9052
device is listed first in the Service Action Log. If a
device is not listed first in the Service Action Log then
been modified.
Failing Item:
v IOPIP21 v SVCDOCS
573E9040 573E9053
Explanation: Array protection temporarily suspended. Explanation: IOA resources not available due to
previous problems.
automatically restarted. Response: Take action on other reference codes which
have surfaced.
573E9041 If you cannot get to SST or DST, and cannot perform a

Explanation: Background array parity check detected media. Look for Product Activity Log entries for other
and corrected errors. reference codes and take action on them.
Response: Call your next level of support to report Failing Item:
the problem.
v SVCDOCS
Failing Item:
v PTFSRCH 573E9054
573E9042 previous problems.
Explanation: An array parity error has been detected Response: Power off the system and remove all new
and corrected. or replacement disk units. IPL the system to DST. If
Response: Call your next level of support to report you cannot perform a type A or B IPL, perform a type
the problem. D IPL from removable media.
Failing Item: Look for Product Activity Log entries for other
v NEXTLVL
Failing Item:
v SVCDOCS

573E9071 • 573EC402
573E9071 573E9091
Explanation: Link from IOA to auxiliary cache IOA Explanation: Incorrect hardware configuration change
went operational. detected.
Response: No service action required. Response: Re-IPL the system. If any reference codes
problem.
573E9072
level of support.
Failing Item:
v SVCDOCS
573E9073
573E9092
auxiliary cache IOA attached. Explanation: Disk unit requires initialization before
use.
Failing Item:
Failing Item:
v IOPIP40
v IOPIP26
573E9081
573E9500
Failing Item:
Failing Item:
v FI01105
v PTFSRCH
v STORIOA
573E9902
573E9082
required.
Failing Item:
v IOPIP16 573E9903
v FI01105
v STORIOA Informational event, no service required.
v FI01140
v BACKPLN 573EC000
v FI01106
required.
573E9090
last known status.
Response: Re-IPL the system. If any reference codes 573EC100
problem.
required.
level of support.
Failing Item:
v SVCDOCS 573EC402
assistance.
Failing Item:

573EFF3D • 57469100
v PTFSRCH
573EFF6D
573EFF3D
Failing Item:
v STORIOA
Failing Item:
v ANYBRDG
v STORIOA
v PTFSRCH
v ANYBRDG

indications.
57463000 57469020
Explanation: I/O adapter hardware error detected. Explanation: Tape unit configuration error.
Failing Item: Response: Before exchanging any parts, verify that the
v FI01112 following conditions are not present:
v Tape and DASD devices attached to an I/O
Processor that does not support Tape and Dasd
57463202
Explanation: Tape unit configuration error. v An unsupported device type or model is attached.
Response: Before exchanging any parts, verify that the Failing Item:
following condition is not present:
v TAPCNFG
v The attached device type or model is only
v FI00871
I/O processor. v PTFSRCH
Failing Item:
57469100
v TAPCNFG
v FI00871 Explanation: Interface error detected by system or by
tape unit.
57463400 Response: If the attached device is an external device,

Failing Item: that there are no bent or damaged pins on the cable.
v FI00872 2. For a SCSI attached device ensure that a
v DEVTERM terminating plug is attached to the device end of
the cable.
v FI00871
v FI01103
v FI01106

57469101 • 57469200
If the attached tape device is owned by a Virtual I/O 2. Ensure that the device has power.
I/O Server to determine the parts to replace. If the attached tape device is owned by a Virtual I/O
Failing Item:
v FI00871
Failing Item:
v FI01112
v FI00871
v FI00872
v FI01112
v DEVTERM
v SASCABL
57469101
57469104
Explanation: Fibre Channel interface error detected.
Response: If the attached device is an external device, tape unit.
1. Ensure that the Fibre Channel cable is correctly
1. Ensure that the USB cable is correctly connected to
the ports.
operational.
4. If there is a gateway device attached, refer to the If the attached tape device is owned by a Virtual I/O
gateway device service documentation for Server partition refer to Troubleshooting the Virtual
additional problem analysis procedures. I/O Server to determine the parts to replace.
additional problem analysis procedures. Failing Item:
v USB_DEV
v FCIOA
v FCDEV
v FCCABLE Response: If the attached device is an external device,
57469102

v DEVTERM v FI00871
v FI01112
57469103 v FI00872
tape unit.
the ports.

57469201 • 57469302
v PTFSRCH
57469201
Explanation: Tape unit command timeout.
57469211
Explanation: Gateway device detected a bus protocol
error.
cable. Failing Item:
3. Ensure that the signal cable is seated correctly, and v FCGATE
that there are no bent or damaged pins on the SCSI v FCIOA
cable.
v FI00871
device end of the SCSI cable. v ANYFC
5. If the attached tape device is owned by a Virtual v FCCABLE
I/O Server partition it may be necessary to reset the v FI00872
virtual IOP to recover from the error. v DEVTERM
Failing Item:
v FI00871 57469220
v FI01112 Explanation: Hardware configuration change detected.
v FI00872
Response: The tape device or tape library device has
v DEVTERM reported a configuration change that requires the I/O
v MEDIA processor to be reset. Reset the I/O processor before
using the device.
57469202
57469221
Explanation: Tape unit failed after Licensed Internal
Code was loaded. Explanation: I/O path change occurred.
Response: If the attached device is an external device, Response: No action required. This reference code is
do the following before exchanging any parts: logged for information only.
2. If an interposer is required, make sure that it is 57469300
cable.
3. Ensure that the SCSI cable is seated correctly, and Failing Item:
that there are no bent or damaged pins on the SCSI v FI00871
cable.
4. Ensure that a terminating plug is attached to the 57469301
Explanation: Tape device failure, redundancy lost.
Failing Item:
Response: The tape unit detected a hardware failure
v FI00871
v FI01112 current operation.
v FI00872
Failing Item:
v DEVTERM
v FI00871
57469210
57469302
Explanation: Tape device failure or media error.
response.
Failing Item:
v FI00871
v FI01112
information on diagnositic tests that can be run to

57469303 • 57469500
isolate between hardware and media failures.

57469350
Failing Item:
v MEDIA on tape medium.
v FI00871
Clean the tape unit and retry the operation.
57469303
Explanation: Gateway device failure. exchange the tape media.

documenation to analyze the problem. v MEDIA
v FCGATE v FI00871
57469304 57469351
Explanation: Tape unit failure. Explanation: Tape with excessive error rate was
following: Response: The tape unit detected that the mounted
1. Ensure that the EKM/TKLM server is operational tape cartridge has a history of excessive read and write
and properly configured. errors. It is recommended that you exchange the tape
cartridge.
EKM/TKLM server database. Failing Item:
v USER v TAPCLN
v FI00871 v FI00871
57469310 57469355
Explanation: Licensed Internal Code for the tape unit Explanation: The data format is incorrect; the tape
is not correct. cannot be read.
Failing Item: Response: The tape unit has detected that the data
v PTFSRCH tape media is defective. Do the following before
v FI00871 exchanging any parts:
57469320 2. Clean the tape unit.
failure. If the operation continues to fail, use a different tape
cartridge.
Failing Item:
Failing Item:
v FI00130
v USER
v FI00871
v MEDIA
v TAPCLN
57469321
v FI00871
error.
57469500
documenation to analyze the problem. Explanation: Licensed Internal Code error.
Failing Item: Response: If the system is operational, perform a

v FCCODE
Failing Item:
v PTFSRCH

57469501 • 57469903
57469501 57469810
Explanation: Licensed Internal Code error. Explanation: Problem analysis has determined a part
should be replaced.
Failing Item:
v PTFSRCH Response: This reference code is used for ending
(Information Only.)
57469800
Response: No action required. This reference code is has been corrected.
57469801 or the problem was corrected.
temporary I/O error. 57469900
Response: No action required. This reference code is Explanation: Licensed Internal Code for tape unit was
logged for information only. not upgraded.
57469802 Internal Code (LIC) to the programmable tape unit was
Explanation: System successfully recovered from not completed.
temporary I/O error. The tape unit will continue to operate with the
Response: No action required. This reference code is previous LIC. You may do either of the following:
logged for information only. v Wait for next IPL when the system will attempt to
57469803 v Perform TUPIP04 to reset the IOP and the tape unit.
Explanation: System successfully recovered from level of LIC, the IOP will attempt to load the new
temporary I/O error. LIC.
57469804 57469901
57469902
57469805
temporary I/O error. Response: No action required.
57469806
Explanation: System successfully recovered from logged for information only.

5746FFF6 • 574E4010
5746FFF6
required).

v SASCABL
574E1310
574E3401
Check other errors reported to the system and correct Failing Item:
them. v SASEXP
v DEVBPLN
574E3000
Explanation: A permanent failure occurred. 574E3405
v STORIOA initialization for a removable media device. This SRC is
v ANYBRDG
model.
574E3020
Explanation: Storage subsystem configuration error. v Check the Product Activity Log for other entries that
Failing Item: indicate interface problems and work those
problems.
v SIP3150
PTFs.
574E3100
Explanation: Device bus interface error occurred. your next level of support with the information you
have gathered.
Failing Item:
v SIP3150 Problem determination: IPL the IOP to retry the
574E3140
Failing Item:
Explanation: System log entry only. No service action v PTFSRCH
required.
574E34FF
574E3202
Response: The device is not supported in the current logged for information only.
v SVCDOCS
required.
574E3400
Explanation: Unknown resource error. 574E4010
v SIP3150 Response: Incorrect connection between cascaded
v FI02112 enclosures.

574E4020 • 574E4160
v SIP3142
574E4061
574E4020
design limits.
574E4070
Failing Item:
v SIP3143 required.
574E4030 574E4100
Explanation: Configuration error. Explanation: Device bus fabric error.
Response: Incorrect multipath connection. Failing Item:
v SIP3144 v SASCABL
v SASEXP
574E4040 v DEVBPLN
Explanation: Configuration error. v STORIOA
v FI01105
574E4101
Failing Item:
v SIP3144 Explanation: Temporary device bus fabric error.
Failing Item:
574E4041 v SIP3152
574E4110
device backplane and device. Explanation: Unsupported enclosure function
detected.
Failing Item:
v SIP3145
574E4050
574E4150
multipath function. Explanation: I/O adapter detected PCI bus error.
574E4060
Failing Item:
Explanation: Multipath redundancy level reduced. v BACKPLN
Response: A redundant disk unit connection has v STORIOA
failed.
v SIP3153 Explanation: I/O adapter detected and recovered a
v SASCABL PCI bus error.

574E70DD • 574E8151
Failing Item:
574E8140
v BACKPLN
v STORIOA
error.
574E70DD
Explanation: Disrupt device command completed event does not appear in a serviceable event view, no
successfully. service action is required.
Failing Item:
574E8008 v SIP3150
cache battery pack or capacitive cache power card. 574E8141
Response: Under a certain configuration, this SRC Explanation: IOA detected recoverable device error.
action. Depending on the configuration of the system, Response: No action is required. This reference code
the Storage IOA may have been altered and/or the is logged for information only.
attachment of OEM Storage that emulates a Load 574E8145
each time the IOA is IPLed and it can be ignored. Explanation: Disk device detected recoverable error.

v CACHBAT
v STORIOA device.
v FEATCRD
Failing Item:
v NEXTLVL
574E8009
Explanation: Impending failure in the cache battery 574E8146
Failing Item:
Failing Item:
v CACHBAT
v FI01105
574E8100
574E8150
Failing Item:
v PTFSRCH
574E8130 Storage IOA Cache may have been disabled to allow
Explanation: IOA detected recoverable device bus Source drive. If this is the case, this error will be posted
error. each time the IOA is IPLed and it can be ignored.
v STORIOA
Failing Item:
574E8151
v SIP3150
Failing Item:
v PTFSRCH
v STORIOA

574E8155 • 574E8300

574E8155
ends the procedure.
v PTFSRCH
v STORIOA
I/O adapter.
574E8156
Failing Item:
v PTFSRCH
v STORIOA 574E8300
574E8157
operational then use Hardware Service Manager unit to the system unit including the cable(s). Work
to manually re-IPL the virtual I/O processor and those problems first, then return to the next step in
Vary On attached resources. this procedure.
v If manually reIPL-ing the virtual I/O processor 5. Use Hardware Service Manager (HSM) to verify
fails then contact your next level of support. This that the adapters have returned to operational
ends the procedure. status. Close reference code xxxx8300 problems for
3. If the Failing Item indicates an I/O adapter, then adapters that have returned to operational status.
replace the I/O adapter. Check the list below to Expansion units attached to system units using
determine if the adapter type you are replacing has Light Path service indicators may have activated the
multiple physical parts. FRU fault indicators for those adapters. Use the
1. Display the Service Action Log entry for this SRC. operational status.
recoverable error.
Failing Item:
processor associated with the adapter. Other v STORIOA

574E8301 • 574E9025
574E8301 574E9010
Explanation: Not valid condition in Licensed Internal Explanation: Cache data associated with attached
Code. devices cannot be found.
v PTFSRCH v SIP3120
v STORIOA
574E9011
574E8302 Explanation: Cache data belongs to devices other than
Explanation: Missing Licensed Internal Code. those attached.

this I/O adapter is loaded. v NEXTLVL
Failing Item:
v SVCDOCS 574E9020
v STORIOA Explanation: Two or more disk units missing from
Explanation: Licensed Internal Code error. v SIP3111
Failing Item:
574E9021
v PTFSRCH
574E8404
Failing Item:
required. v SIP3111
574E9000 574E9022
Explanation: Device error. Explanation: Two or more disk units missing from
Failing Item:
Failing Item:
v FI01105
v SIP3111
v STORIOA
574E9023
574E9001
Failing Item:
Failing Item:
v NEXTLVL
v SIP3112
574E9002
574E9024
v NEXTLVL
574E9008
Explanation: I/O card does not support functions 574E9025
Failing Item:
v SIP3130

574E9026 • 574E9050

574E9031
exposed.
Failing Item:
v FI02112
574E9026
Explanation: Disk unit not found at required physical 574E9032
location.
v SIP3110
574E9027 v FI02112
synchronization. 574E9040
v SIP3113
574E9041
574E9028
has been exceeded.
Failing Item:
Failing Item:
574E9042
v SVCDOCS
on disk unit.
574E9029
the problem.
Failing Item:
v NEXTLVL
Failing Item:
v NEXTLVL
574E9050
574E9030
more disk units.
Failing Item:
v SIP3131
Failing Item:
v SIP3110
v FI02112

574E9051 • 574E9090
574E9051 574E9074
Failing Item:
574E9052 v SIP3141
modified devices. 574E9075
Failing Item:
v SIP3149
574E9054
574E9076
v SIP3121 v SIP3147
574E9055 574E9081
storage IOA.
Failing Item:
v STORIOA
574E9070
Explanation: System log entry only. No service action 574E9082
required.
Failing Item:
574E9071
v FI01105
v STORIOA
IOA is operational.
574E9083
574E9072
required.
574E9084
required.
574E9073
Explanation: Multiple I/O adapters connected in a not 574E9090
Failing Item: last known status.
v SIP3140 Response: Use Hardware Service Manager to re-IPL

574E9091 • 574F3400
If any reference codes are surfaced, use the new Explanation: Internal program error in driver code.
Failing Item:
level of support.
v SVCDOCS
574E9091
Explanation: Incorrect hardware configuration change 574EC000
detected.
574EC402
assistance.
Failing Item:
v PTFSRCH
574E9092
574EFF3D
use. Explanation: I/O adapter detected a recoverable error.
v SIP3134 v STORIOA
v ANYBRDG
574E9500

Failing Item:
574F1310
v AUXCBL
v AUXIOA
Response: The I/O adapter error log is being filled v PRIMIOA
them. 574F3101
574F3006 Response: Error occurred on SCSI bus 1.
Explanation: System bus error. Failing Item:
Failing Item: v AUXCBL
v AUXIOA v AUXIOA
v ANYBRDG v PRIMIOA
v IOP
574F3400
574F3100 Explanation: SCSI resource error.
Explanation: Interface error. Failing Item:
Response: Error occurred on SCSI bus 0. v AUXCBL

574F6075 • 574F8157
v PRIMIOA is logged for information only.
574F6075 574F8145
Explanation: I/O processor resource not available. Explanation: A recoverable error occurred.
v PTFSRCH v AUXIOA
574F8008 574F8150
Explanation: A permanent cache battery pack failure Explanation: A permanent failure occurred.
occurred.
Response: NOTE: Under a certain configuration, this SRC may not represent an error that requires a service
SRC may not represent an error that requires a service action. Depending on the configuration of the system,
action. Depending on the configuration of the system, the Storage IOA may have been altered and/or the
the Storage IOA may have been altered and/or the Storage IOA Cache may have been disabled to allow
Storage IOA Cache may have been disabled to allow attachment of OEM Storage that emulates a Load
attachment of OEM Storage that emulates a Load Source drive. If this is the case, this error will be posted
Source drive. If this is the case, this error will be posted each time the IOA is IPLed and it can be ignored.
Failing Item:
Failing Item: v AUXIOA
v CACHBAT v ANYBRDG
v AUXIOA
574F8151
574F8009
Failing Item:
v CACHBAT v AUXIOA
574F8130 574F8155
Explanation: IOA detected recoverable SCSI bus error. Explanation: A permanent failure occurred.
Response: An error occurred on SCSI bus 0. No action Failing Item:
v PTFSRCH
information only.
v AUXIOA
574F8131
574F8156
information only. v PTFSRCH
v AUXIOA
574F8140
Explanation: IOA detected recoverable SCSI bus error. 574F8157
Response: No action is required. This reference code Explanation: I/O adapter card temporary error.
is logged for information only. Response: Display the Service Action Log entry for
574F8141 replace the I/O adapter. If the Failing Item indicates
Explanation: IOA detected recoverable SCSI resource is a recoverable error. Perform the following for the
error. I/O processor that the I/O adapter is attached to:
Response: No action is required. This reference code 1. If the I/O Processor is not operable and disk units

574F8300 • 574FFF3D

574F9073
need to be Varied On. Explanation: Disconnected, incompatible, or
non-operational storage IOA.
Failing Item:
v SVCDOCS 574FFF3D
574F8300
Failing Item:
Explanation: IOA hardware or PCI bus error. v AUXIOA
v AUXIOA
v ANYBRDG
v PTFSRCH
574F8301
Code.
Failing Item:
v PTFSRCH
v AUXIOA
574F8302
Failing Item:
v SVCDOCS
v AUXIOA
574F9055
storage IOA.
574F9071
went operational.
574F9072

57553000 • 57559101

indications.
57553000
Failing Item:
v TAPCNFG
Failing Item:
v FI00871
v FI01112
v PTFSRCH
57553202
57559100
Response: Before exchanging any parts, verify that the tape unit.
v The attached device type or model is only do the following before exchanging any parts:
I/O processor.
Failing Item: 2. For a SCSI attached device ensure that a
v TAPCNFG terminating plug is attached to the device end of

Explanation: Device error has occurred. I/O Server to determine the parts to replace.

v FI00872 v FI00871
v DEVTERM v FI01112
v FI00871 v FI00872
v FI01103 v DEVTERM
v FI01106
57559101
57559020 Explanation: Fibre Channel interface error detected.
Explanation: Tape unit configuration error. Response: If the attached device is an external device,
following conditions are not present: 1. Ensure that the Fibre Channel cable is correctly
Processor that does not support Tape and Dasd 2. Clean the Fibre Channel connectors.

57559102 • 57559201
3. If there is a switch or hub attached, verify that it is 1. Ensure that the USB cable is correctly connected to
operational. the ports.
4. If there is a gateway device attached, refer to the 2. Ensure that the device has power.
gateway device service documentation for
additional problem analysis procedures. If the attached tape device is owned by a Virtual I/O
5. refer to the tape device service documentation for Server partition refer to Troubleshooting the Virtual
Failing Item:
v USB_DEV
I/O Server to determine the parts to replace. v USB_IOA
v USB_CBL
Failing Item:
v FCIOA
57559200
v FCDEV
v FCCABLE Explanation: Tape unit is not responding.
error. 2. Ensure that the signal cable is seated correctly, and
terminating plug is attached to the device end of
Failing Item: the SCSI cable.
v FI00871
v FCGATE
v DEVTERM
Failing Item:
v FI00871
57559103
v FI01112
Explanation: Interface error detected by system or by v FI00872
tape unit.
v DEVTERM
57559201
the ports. Explanation: Tape unit command timeout.
2. Ensure that the device has power. Response: If the attached device is an external device,
If the attached tape device is owned by a Virtual I/O 1. Ensure that the device is powered on.
Failing Item: cable.
v FI00871 3. Ensure that the signal cable is seated correctly, and
v FI01112 that there are no bent or damaged pins on the SCSI
cable.
v SASCABL
57559104
Explanation: Interface error detected by system or by I/O Server partition it may be necessary to reset the
tape unit. virtual IOP to recover from the error.
Response: If the attached device is an external tape Failing Item:
v FI01112

57559202 • 57559303
v FI00872
57559220
v DEVTERM
Explanation: Hardware configuration change detected.
v MEDIA
reported a configuration change that requires the I/O
57559202
Explanation: Tape unit failed after Licensed Internal using the device.
Code was loaded.
Response: If the attached device is an external device, 57559221
cable.
3. Ensure that the SCSI cable is seated correctly, and 57559300
that there are no bent or damaged pins on the SCSI Explanation: Tape unit failure.
cable.
Failing Item:
device end of the SCSI cable. v FI00871
Failing Item:
57559301
v FI00871
v FI00872 Response: The tape unit detected a hardware failure
v DEVTERM that does not prevent the tape unit from completing the
current operation.

v FI00871
response.
57559302
Failing Item:
v FI01112 Response: The tape unit detected a failure that may
v PTFSRCH be caused by a hardware failure or a media error.
57559211 information on diagnositic tests that can be run to
v MEDIA
documentation to analyze the problem. v FI00871
Failing Item:
57559303
v FCGATE
v FCIOA Explanation: Gateway device failure.
v FI00871 Response: Use the gateway device service
v ANYFC documenation to analyze the problem.
v FCCABLE Failing Item:
v FI00872 v FCGATE
v DEVTERM

57559304 • 57559800
57559304 57559351
cartridge.
v USER v TAPCLN
v FI00871 v FI00871
57559310 57559355
v PTFSRCH
cartridge.
Failing Item:
Failing Item:
v FI00130
v USER
v FI00871
v MEDIA
v TAPCLN
57559321
v FI00871
error.
57559500

v FCCODE
Failing Item:
57559350 v PTFSRCH

on tape medium. 57559501
Response: A permanent read or write error occurred. Explanation: Licensed Internal Code error.
Clean the tape unit and retry the operation. Failing Item:
If cleaning the tape unit does not correct the problem, v PTFSRCH
v MEDIA Explanation: System successfully recovered from
v TAPCLN temporary I/O error.
v FI00871 Response: No action required. This reference code is

57559801 • 5767B9B0
57559801 57559899
Explanation: System successfully recovered from Explanation: Problem analysis completed, the problem
temporary I/O error. has been corrected.
Response: No action required. This reference code is Response: This reference code is used for ending
logged for information only. Online Problem Analysis when no problem was found
57559802
57559900
temporary I/O error. Explanation: Licensed Internal Code for tape unit was
not upgraded.
logged for information only. Response: The I/O processor loading of Licensed
not completed.
57559803
Response: No action required. This reference code is load the LIC for the tape drive again.
57559804 level of LIC, the IOP will attempt to load the new
LIC.
temporary I/O error. Failing Item:
Response: No action required. This reference code is v USER
57559901
57559805 Explanation: Tape performance statistics logged.
Explanation: System successfully recovered from Response: No action required. This reference code is
temporary I/O error. logged for information only.
57559806
57559903
logged for information only. Explanation: Tape device information logged.

should be replaced. 5755FFF6
Online Problem Analysis with a list of failing items. required).
(Information Only.)

Failing Item:
5767A001
v AJDGP01
detected.
5767B9B0

5768A001 • 576B3121


5768A001
Failing Item:
detected. v IOA
v AJDGP01
Failing Item:
v AJDGP01
5768B9B0

576AA001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
576AB9B0

576B3020
Failing Item:
v FCINTF
Response: Too many devices have been configured on
v ANYFC
v FCIOA
Failing Item:
v OPT_CLN
v SVCDOCS
576B3120
576B3021
Failing Item: moved from one LPAR to another LPAR and the
v SVCDOCS port was left open.
576B3100 If you have eliminated the above possibilities
Failing Item:
Failing Item:
v FCPORT
v FCINTF
v FCIOA
v ANYFC
v FCDEV
v FCIOA
v OPT_CLN
v OPT_CLN
576B3121
576B3101

576B3140 • 576B8150
Explanation: An open port was detected on port 1. v Check for LIC logs with major code 2E00. Contact
have gathered.
port was left open.
3. This error can occur if there is a port or link failure. Failing Item:
If you have eliminated the above possibilities v PTFSRCH
v FCPORT Explanation: Format in progress.
v FCIOA
v FCDEV progress. When the format is complete, the device
v OPT_CLN should be usable. No action is required. This reference
576B3140
576B4150
code that occurred before it require no service action, Response: If this event appears in a serviceable event
since the port is now operational. view, work with the failing item list found there. If this
576B3141
Failing Item:
v BACKPLN
v FCIOA
576B8100
576B3400 Explanation: Licensed Internal Code error.
Explanation: Device error. Failing Item:
v FCDEV v FCIOA
v FCINTF
v ANYFC 576B8130
v FCIOA Explanation: Recovered Fibre Channel interface error
v OPT_CLN on port 0.
576B3405 logged for information only.

initialization for a removable media device. This SRC is 576B8131
logged when an error occurs and the removable media Explanation: Recovered Fibre Channel interface error
device driver cannot determine the device type or on port 1.
model.
Response: Perform the following: logged for information only.
576B8150
problems.
v Check the device firmware level and apply the latest Explanation: A permanent I/O adapter failure
PTFs. occurred.
Failing Item:

576B8151 • 576BC402
v FCIOA
576BB000
v ANYBRDG
v OPT_CLN
required.
576B8151
Failing Item: 576BB402
v FCIOA
Failing Item:
v PTFSRCH
576B8300
Explanation: IOA hardware error or PCI bus error. 576BC000
Failing Item: Explanation: System log entry only, no service action
v FCIOA required.
v ANYBRDG Response: No action is required. This reference code
v PTFSRCH is logged for information only.
v OPT_CLN
576BC402
Explanation: Not valid condition in Licensed Internal Failing Item:
Code.
v PTFSRCH
Failing Item:
v PTFSRCH
v FCIOA
v OPT_CLN
576B8302
Failing Item:
v SVCDOCS
v FCIOA
v OPT_CLN
576B9500
Failing Item:
v PTFSRCH
576B9903

576CA001 • 576FB9B0

v FI00719
576CA001
v AJDGP01
v MA_BRDG
Failing Item:
576CB941
v NEXTLVL
576CB940 Failing Item:

v FI00719
v AJDGP01
Failing Item:

576DA001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
576DB9B0

576EA001
Failing Item:
detected. v IOA
v AJDG301
Failing Item:
v AJDG301
576EB9B0

576FA001 576FB9B0
Explanation: I/O adapter Licensed Internal Code error Explanation: I/O adapter hardware error detected.
detected.
Failing Item:
v AJDGP01 v AJDG301
v MA_BRDG
576FB9A0
Failing Item:
v FI00719
v FI00718
v AJDGP01
v MA_BRDG

57743020 • 57743405

v OPT_CLN
57743020
57743121
Failing Item:
v SVCDOCS
57743021 port was left open.
Explanation: Configuration error on port 1. 3. This error can occur if there is a port or link failure.
Failing Item:
Failing Item:
v FCPORT
v SVCDOCS
v FCIOA
v FCDEV
57743100
v OPT_CLN
v FCINTF
v ANYFC
v FCIOA
v OPT_CLN since the port is now operational.
57743101 57743141
Explanation: Interface error on port 1. Explanation: Port 1 is now operational.
v FCINTF code that occurred before it require no service action,
v ANYFC since the port is now operational.
v FCIOA
v OPT_CLN 57743400
Explanation: An open port was detected on port 0. v FCDEV
Problem determination: Perform the following steps: v FCINTF
1. Check for a missing cable or wrap connector. v ANYFC
2. This error can occur when a shared device is being v FCIOA
moved from one LPAR to another LPAR and the v OPT_CLN
port was left open.
3. This error can occur if there is a port or link failure. 57743405
contact your next level of support. Explanation: An error occurred during task
v FCPORT device driver cannot determine the device type or
v FCIOA model.
v FCDEV Response: Perform the following:

577434FF • 57749500

57748150
problems. Explanation: A permanent I/O adapter failure
v Check the device firmware level and apply the latest occurred.
PTFs. Failing Item:
v Check for LIC logs with major code 2E00. Contact v FCIOA
v ANYBRDG
have gathered.
v OPT_CLN
contact your service provider. 57748151
Failing Item: Explanation: Licensed Internal Code error.

v PTFSRCH
577434FF v FCIOA
57748300
progress. When the format is complete, the device Explanation: IOA hardware error or PCI bus error.
v FCIOA
57744150 v ANYBRDG
v PTFSRCH
v OPT_CLN
event does not appear in a serviceable event view, no 57748301
service action is required. Explanation: Not valid condition in Licensed Internal
Failing Item: Code.
v FCIOA v PTFSRCH
v FCIOA
57748100 v OPT_CLN
57748302
Failing Item:
v PTFSRCH Explanation: Missing Licensed Internal Code.
v FCIOA Response: Ensure that the code necessary to support
Explanation: Recovered Fibre Channel interface error v SVCDOCS

on port 0. v FCIOA
57749500
57748131 Explanation: Internal program error in driver code.
Explanation: Recovered Fibre Channel interface error Failing Item:
on port 1.
v PTFSRCH

57749903 • 577D3121
v PTFSRCH
57749903
5774C000
required.
5774B000
required.
5774C402
Explanation: Licensed Internal Code error. v PTFSRCH
Failing Item:

577D3020 577D3120
Explanation: Configuration error on port 0. Explanation: An open port was detected on port 0.
Response: Too many devices have been configured on Problem determination: Perform the following steps:
port 0. Change the configuration. 1. Check for a missing cable or wrap connector.
Failing Item: 2. This error can occur when a shared device is being
v SVCDOCS moved from one LPAR to another LPAR and the
port was left open.
577D3021
Explanation: Configuration error on port 1. contact your next level of support.
port 1. Change the configuration. v FCPORT
v SVCDOCS v FCDEV
v OPT_CLN
577D3100
Explanation: Interface error on port 0. 577D3121
Failing Item: Explanation: An open port was detected on port 1.

v FCINTF Problem determination: Perform the following steps:
v ANYFC 1. Check for a missing cable or wrap connector.
v FCIOA 2. This error can occur when a shared device is being
v OPT_CLN moved from one LPAR to another LPAR and the
port was left open.
577D3101 If you have eliminated the above possibilities
Explanation: Interface error on port 1. contact your next level of support.

v FCINTF v FCPORT
v ANYFC v FCIOA
v FCIOA v FCDEV
v OPT_CLN v OPT_CLN

577D3140 • 577D8300
577D3140 577D4150
Explanation: Port 0 is now operational. Explanation: I/O adapter detected PCI bus error.
Response: This reference code and the 3120 reference Response: If this event appears in a serviceable event
code that occurred before it require no service action, view, work with the failing item list found there. If this
since the port is now operational. event does not appear in a serviceable event view, no
Explanation: Port 1 is now operational. v BACKPLN
v FCIOA
since the port is now operational. 577D8100
577D3400
Failing Item:
Explanation: Device error. v PTFSRCH
v FCDEV
v FCINTF 577D8130
v ANYFC Explanation: Recovered Fibre Channel interface error
v FCIOA on port 0.
v OPT_CLN Response: No action required. This reference code is
577D3405
Explanation: An error occurred during task 577D8131
initialization for a removable media device. This SRC is Explanation: Recovered Fibre Channel interface error
logged when an error occurs and the removable media on port 1.
model. Response: No action required. This reference code is
577D8150
problems. Explanation: A permanent I/O adapter failure
v Check the device firmware level and apply the latest occurred.
PTFs. Failing Item:
v Check for LIC logs with major code 2E00. Contact v FCIOA
have gathered. v ANYBRDG
v OPT_CLN
contact your service provider. 577D8151
Failing Item: Explanation: Licensed Internal Code error.
v PTFSRCH
577D34FF v FCIOA
Response: The device indicated that a format is in 577D8300
progress. When the format is complete, the device Explanation: IOA hardware error or PCI bus error.
v FCIOA

577D8301 • 577F3120
v ANYBRDG Explanation: Tape device information was logged.

v PTFSRCH Informational event, no service required.
v OPT_CLN
577DB000
577D8301 Explanation: System log entry only, no service action
required.
Code. Response: No action is required. This reference code
Failing Item:
v PTFSRCH
577DB402
v FCIOA
v OPT_CLN Explanation: Licensed Internal Code error.
Failing Item:
577D8302 v PTFSRCH
577DC000
this I/O adapter is loaded. Explanation: System log entry only, no service action
required.
Failing Item:
v SVCDOCS Response: No action is required. This reference code
v FCIOA
v OPT_CLN
577DC402
577D9500 Explanation: Licensed Internal Code error.
Explanation: Internal program error in driver code. Failing Item:

v PTFSRCH
Failing Item:
v PTFSRCH
577D9903

Failing Item:
577F3020
v FCINTF
v ANYFC
Response: Too many devices have been configured on v FCIOA
v OPT_CLN
Failing Item:
v SVCDOCS 577F3101
577F3021
Failing Item:
v FCINTF
Response: Too many devices have been configured on v ANYFC
v FCIOA
v SVCDOCS
577F3120
577F3100

577F3121 • 577F8100

577F3405
moved from one LPAR to another LPAR and the Explanation: An error occurred during task
port was left open. initialization for a removable media device. This SRC is
model.
Failing Item:
v FCPORT
v FCIOA problems.
v FCDEV v Check the device firmware level and apply the latest
v OPT_CLN PTFs.
577F3121 your next level of support with the information you
have gathered.
Problem determination: Perform the following steps: device identification process. If the error persists then
1. Check for a missing cable or wrap connector. contact your service provider.
2. This error can occur when a shared device is being Failing Item:
moved from one LPAR to another LPAR and the v PTFSRCH
port was left open.
If you have eliminated the above possibilities 577F34FF
contact your next level of support. Explanation: Format in progress.
Failing Item: Response: The device indicated that a format is in
v FCPORT progress. When the format is complete, the device
v FCIOA should be usable. No action is required. This reference
v FCDEV
v OPT_CLN
577F4150
577F3140 Explanation: I/O adapter detected PCI bus error.
Explanation: Port 0 is now operational. Response: If this event appears in a serviceable event
Response: This reference code and the 3120 reference event does not appear in a serviceable event view, no
code that occurred before it require no service action, service action is required.
Failing Item:
v BACKPLN
577F3141
v FCIOA
Response: This reference code and the 3121 reference 577F8100
since the port is now operational. Explanation: Licensed Internal Code error or
unexpected condition in LIC.
577F3400 Problem determination: If this SRC appears in a

serviceable event view then service is required. If this
Explanation: Device error. event does not appear in a serviceable event view then
no service is required. The condition was temporary
Failing Item:
and it has been corrected.
v FCDEV
Failing Item:
v FCINTF
v PTFSRCH
v ANYFC
v FCIOA
v FCIOA
v OPT_CLN

577F8130 • 578E3020
577F8130 577F8302
Explanation: Recovered Fibre Channel interface error Explanation: Missing Licensed Internal Code.
on port 0.
Response: No action required. This reference code is this I/O adapter is loaded.
Failing Item:
v SVCDOCS
577F8131
v FCIOA
Explanation: Recovered Fibre Channel interface error v OPT_CLN
on port 1.
Response: No action required. This reference code is 577F9500
577F8150 Failing Item:

v PTFSRCH
Explanation: A permanent I/O adapter failure
occurred.
577F9903
Failing Item:
v FCIOA Explanation: Tape device information was logged.
v ANYBRDG
v OPT_CLN
577FB000
577F8151 Explanation: System log entry only, no service action

required.
Failing Item: is logged for information only.
v PTFSRCH
v FCIOA 577FB402
577F8300
Failing Item:
v PTFSRCH
Failing Item:
v FCIOA 577FC000
v ANYBRDG
v PTFSRCH required.
v OPT_CLN
577F8301
Explanation: Not valid condition in Licensed Internal 577FC402
Code.
Failing Item:
Failing Item:
v PTFSRCH
v PTFSRCH
v FCIOA
v OPT_CLN

578E3020
Failing Item:
v SVCDOCS

578E3021 • 578E3122
578E3021 578E3103
Explanation: Configuration error on port 1. Explanation: Interface error on port 3.
port 1. Change the configuration. v FCINTF
Failing Item: v ANYFC
v SVCDOCS v FCIOA
v OPT_CLN
578E3022
Explanation: Configuration error on port 2. 578E3120
Response: Too many devices have been configured on Explanation: An open port was detected on port 0.
port 2. Change the configuration. Problem determination: Perform the following steps:
Failing Item: 1. Check for a missing cable or wrap connector.
v SVCDOCS 2. This error can occur when a shared device is being
port was left open.
578E3023
Explanation: Configuration error on port 3. If you have eliminated the above possibilities
Response: Too many devices have been configured on contact your next level of support.
port 3. Change the configuration. Failing Item:
Failing Item: v FCPORT
v SVCDOCS v FCIOA
v FCDEV
578E3100 v OPT_CLN
578E3121
Failing Item:
v FCINTF Explanation: An open port was detected on port 1.
v ANYFC Problem determination: Perform the following steps:
v FCIOA 1. Check for a missing cable or wrap connector.
v OPT_CLN 2. This error can occur when a shared device is being
port was left open.
578E3101
Explanation: Interface error on port 1. If you have eliminated the above possibilities
Failing Item:
v ANYFC v FCPORT
v FCIOA v FCIOA
v OPT_CLN v FCDEV
v OPT_CLN
578E3102
578E3122
Failing Item:
v FCINTF Problem determination: Perform the following steps:
v ANYFC 1. Check for a missing cable or wrap connector.
v FCIOA 2. This error can occur when a shared device is being
v OPT_CLN
port was left open.

578E3123 • 578E4150

578E3400
contact your next level of support. Explanation: Device error.
v FCPORT v FCDEV
v FCIOA v FCINTF
v FCDEV v ANYFC
v OPT_CLN v FCIOA
v OPT_CLN
578E3123
Explanation: An open port was detected on port 3. 578E3405
Problem determination: Perform the following steps: Explanation: An error occurred during task
2. This error can occur when a shared device is being device driver cannot determine the device type or
moved from one LPAR to another LPAR and the model.
port was left open.
If you have eliminated the above possibilities v Check the Product Activity Log for other entries that
contact your next level of support. indicate interface problems and work those
problems.
Failing Item:
v FCPORT PTFs.
v FCIOA v Check for LIC logs with major code 2E00. Contact
v FCDEV your next level of support with the information you
v OPT_CLN have gathered.
578E3140 device identification process. If the error persists then
Failing Item:
Response: This reference code and the 3120 reference v PTFSRCH
578E34FF
578E3141 Explanation: Format in progress.
Explanation: Port 1 is now operational. Response: The device indicated that a format is in
Response: This reference code and the 3121 reference should be usable. No action is required. This reference
code that occurred before it require no service action, code is logged for information only.
578E4150
578E3142
Response: This reference code and the 3122 reference view, work with the failing item list found there. If this
code that occurred before it require no service action, event does not appear in a serviceable event view, no
since the port is now operational. service action is required.
Failing Item:
578E3143
v BACKPLN
Explanation: Port 3 is now operational. v FCIOA

578E8100 • 578EB000
578E8100 578E8151
Explanation: Licensed Internal Code error or Explanation: Licensed Internal Code error.
Failing Item:
Problem determination: If this SRC appears in a v PTFSRCH
serviceable event view then service is required. If this
v FCIOA
event does not appear in a serviceable event view then
and it has been corrected. 578E8300
Failing Item: Explanation: IOA hardware error or PCI bus error.
v FCIOA v FCIOA
v ANYBRDG
578E8130 v PTFSRCH
on port 0.
Response: No action required. This reference code is 578E8301
Code.
578E8131
Failing Item:
Explanation: Recovered Fibre Channel interface error v PTFSRCH
on port 1.
v FCIOA
578E8302
578E8132
on port 2. Response: Ensure that the code necessary to support
v SVCDOCS
578E8133 v FCIOA

on port 3.
Response: No action required. This reference code is 578E9500
logged for information only. Explanation: Internal program error in driver code.
Failing Item:
578E8150
v PTFSRCH
Explanation: A permanent I/O adapter failure
occurred.
578E9903
Failing Item:
v FCIOA Informational event, no service required.
v ANYBRDG
v OPT_CLN 578EB000
required.

578EB402 • 578F3141

578EB402
Failing Item: 578EC402
Failing Item:
578EC000
v PTFSRCH
required.

578F3020
Explanation: Configuration error on port 0. port was left open.
Response: Too many devices have been configured on 3. This error can occur if there is a port or link failure.
port 0. Change the configuration. If you have eliminated the above possibilities
Failing Item:
Failing Item:
v SVCDOCS
v FCPORT
v FCIOA
578F3021
v FCDEV
v OPT_CLN
578F3121
Failing Item:
v SVCDOCS
578F3100
Explanation: Interface error on port 0. moved from one LPAR to another LPAR and the
v FCINTF 3. This error can occur if there is a port or link failure.
v ANYFC contact your next level of support.
v FCIOA
Failing Item:
v OPT_CLN
v FCPORT
v FCIOA
578F3101
v FCDEV
Explanation: Interface error on port 1. v OPT_CLN
Failing Item:
v FCINTF 578F3140
v ANYFC Explanation: Port 0 is now operational.
v FCIOA
v OPT_CLN code that occurred before it require no service action,
578F3120
Explanation: An open port was detected on port 0. 578F3141
Problem determination: Perform the following steps: Explanation: Port 1 is now operational.
1. Check for a missing cable or wrap connector. Response: This reference code and the 3121 reference

578F3400 • 578F8300

578F8100
Explanation: Licensed Internal Code error or
578F3400
Problem determination: If this SRC appears in a
Failing Item: serviceable event view then service is required. If this
v FCDEV event does not appear in a serviceable event view then
v FCINTF and it has been corrected.
v ANYFC
Failing Item:
v FCIOA
v PTFSRCH
v OPT_CLN
v FCIOA
578F3405
578F8130
initialization for a removable media device. This SRC is Explanation: Recovered Fibre Channel interface error
logged when an error occurs and the removable media on port 0.
device driver cannot determine the device type or Response: No action required. This reference code is
model. logged for information only.
v Check the Product Activity Log for other entries that 578F8131
problems.
on port 1.
PTFs. Response: No action required. This reference code is
have gathered. 578F8150
Problem determination: IPL the IOP to retry the Explanation: A permanent I/O adapter failure
device identification process. If the error persists then occurred.
Failing Item:
v PTFSRCH v ANYBRDG
v OPT_CLN
578F34FF
Explanation: Format in progress. 578F8151
Response: The device indicated that a format is in Explanation: Licensed Internal Code error.
Failing Item:
code is logged for information only. v PTFSRCH
v FCIOA
578F4150
578F8300
event does not appear in a serviceable event view, no v FCIOA
v ANYBRDG
v BACKPLN v OPT_CLN
v FCIOA

578F8301 • 578FC402
578F8301 578FC402
Explanation: Not valid condition in Licensed Internal Explanation: Licensed Internal Code error.
Code.
Failing Item:
v PTFSRCH
v FCIOA
v OPT_CLN
578F8302
Failing Item:
v SVCDOCS
v FCIOA
v OPT_CLN
578F9500
Failing Item:
v PTFSRCH
578F9903
578FB000
required.
578FB402
Failing Item:
v PTFSRCH
578FC000
required.

57B11310 • 57B14020

57B11310 57B13401
v DEVBPLN
them.
57B13405
57B13000
model.
v ANYBRDG
57B13020 v Check the Product Activity Log for other entries that
v SIP3150 PTFs.
57B13100 have gathered.
v SIP3150
Failing Item:
57B13140 v PTFSRCH

required. 57B134FF
57B13202 Response: No action required. This reference code is

configuration. An I/O processor might be required. 57B13601

required.
v SVCDOCS
57B14010
57B13400
Failing Item:
enclosures.
v SIP3150
Failing Item:
v FI02112
v SIP3142
v STORIOA
v SASCABL
57B14020

57B14030 • 57B14110

57B14070
design limits.
Failing Item:
required.
v SIP3143
57B14080
57B14030
Explanation: Storage controller thermal error. The
Explanation: Configuration error. controller exceeded the maximum operating
Response: Incorrect multipath connection. temperature.
Failing Item: Problem determination: Verify that the storage

controller is placed in a valid location for this type of
v SIP3144 controller and enclosure. Perform the procedure listed
in the failing items to determine the problem and
57B14040 corrective action.
Explanation: Configuration error. Failing Item:

v SIP3295
57B14085
Failing Item:
v SIP3144 Explanation: Storage controller detected error. Contact
your next level of support or hardware service provider
for more information before replacing any hardware.
57B14041
Failing Item:
v NEXTLVL
57B14100
Failing Item:
v SIP3146
Failing Item:
v SIP3152
57B14050
v SASCABL
v SASEXP
multipath function.
v DEVBPLN
Failing Item:
v STORIOA
v SIP3148
v FI01105
57B14060
57B14101
Failing Item:
failed.
v SIP3152
Failing Item:
v SIP3153
57B14110
v SASCABL
v SASEXP
detected.
Failing Item:
57B14061
v SIP3145

57B14120 • 57B18145
57B14120 57B18009
Explanation: SAS cable VPD cannot be read. Explanation: Impending failure in the cache battery
Failing Item:
v CACHBAT
57B14121
57B18100
Explanation: SAS cable is missing.
Failing Item:
v PTFSRCH
57B14123 v STORIOA
Explanation: Configuration error, invalid cable Vital

Product Data. The storage controller detected invalid 57B18130
VPD on the SAS cable. This is most likely caused by a Explanation: IOA detected recoverable device bus
non IBM cable or a wrap plug. The system will error.
continue to run.
Problem determination: Verify that wrap plugs have view, work with the failing item list found there. If this
been removed and the cable is an IBM part. If the event does not appear in a serviceable event view, no
problem persists contact your next level of support. service action is required.
v SASCABL v SIP3150
57B14150 57B18140
Explanation: I/O adapter detected PCI bus error. Explanation: IOA detected recoverable device bus
Response: If this event appears in a serviceable event error.
v STORIOA v SIP3150
57B14160 57B18141
Explanation: I/O adapter detected and recovered a Explanation: IOA detected recoverable device error.
PCI bus error.
Response: If this event appears in a serviceable event is logged for information only.
57B18145
Failing Item:
v BACKPLN Response: This error is logged against the storage
v STORIOA
device.
57B170DD
Failing Item:
Explanation: Disrupt device command completed v NEXTLVL
successfully.

57B18146 • 57B18300

57B18146
Explanation: Disk device detected recoverable error. v If manually reIPL-ing the virtual I/O processor
ends the procedure.
v FI01105
57B18150 determine if the adapter type you are replacing has
Explanation: A permanent failure occurred. multiple physical parts.

57B18151 recoverable error.
Explanation: Licensed Internal Code error. v LIC will automatically re-IPL the virtual I/O
Failing Item: resources attached to the virtual I/O processor
v PTFSRCH may need to be Varied On.
v STORIOA v If the virtual I/O processor or adapter are not
57B18155
ends the procedure.
v PTFSRCH
v STORIOA contact your next level of support to replace the
I/O adapter.
v PTFSRCH
v STORIOA 57B18300
57B18157 Problem determination: Perform the following:
Response: The FRU list in the Service Action Log will
ends the procedure.
3. Suspect a problem with the connection to the
recoverable error.

57B18301 • 57B19022

this procedure.
57B19001
status. Close reference code xxxx8300 problems for Failing Item:
57B19008
Failing Item:
v STORIOA
v ANYBRDG
Failing Item:
v PTFSRCH
v SIP3130
57B18301
57B19010
Failing Item:
Failing Item:
v PTFSRCH
v SIP3120
v STORIOA
57B19011
57B18302
those attached.
Failing Item:
v NEXTLVL
Failing Item:
v SVCDOCS
57B19020
v STORIOA
57B18400
Failing Item:
v SIP3111
Failing Item:
v PTFSRCH 57B19021
57B18404 RAID-5 or RAID-6 array.
required.
v SIP3111
57B19000
57B19022
Failing Item: RAID-5 or RAID-6 array.

57B19023 • 57B19041
v SIP3111 v SVCDOCS
57B19023 57B19029
Explanation: One or more array members not in Explanation: Maximum number of functional array
required physical locations. members has been exceeded.
v NEXTLVL
57B19024
Explanation: Array member physical location conflicts 57B19030
with another array.
Failing Item: missing or failed disk unit.
v SIP3110
57B19025 v FI02112
Response: An incompatible device is at the physical 57B19031
location of the device which is causing the array to be Explanation: Automatic rebuild initiated for array.
exposed.
Failing Item: and was automatically restarted, or a hot spare disk
v SIP3110 unit was used to automatically rebuild the array. Look
v FI02112 for other reference codes and take action on them.
57B19026 57B19032
location. failed.

v NEXTLVL v SIP3110
v FI02112
57B19027
57B19040
initiated.
Failing Item:
v SIP3113 57B19041
57B19028 and corrected errors.

Failing Item:

57B19042 • 57B19082
57B19042 57B19072
Explanation: Background parity check corrected errors Explanation: Link from IOA to auxiliary or remote
on disk unit. IOA is non-operational.
Response: Call your next level of support to report Response: No service action required.
the problem.
v NEXTLVL Explanation: Multiple I/O adapters connected in a not
Explanation: Required cache data not found for one or v SIP3140
more disk units.
v SIP3131 Explanation: Multiple I/O adapters connected in a not
57B19051 Response: Multiple I/O adapters not capable of
Explanation: Cache data exists for one or more similar functions or controlling the same set of devices.
missing or failed devices. Failing Item:
v SIP3132
57B19075
57B19052 Explanation: Incomplete multipath connection
Explanation: Cache data exists for one or more between IOA and remote IOA.
modified devices. Failing Item:
Response: Contact your next level of support. v SIP3149
Failing Item:
v NEXTLVL 57B19076
Explanation: IOA resources not available due to v SIP3147
previous problems.
Failing Item:
57B19055
v FI01105
storage IOA.
Response: No service action required. 57B19082
57B19070
Failing Item:
v FI01105
required.
v STORIOA
57B19071
IOA is operational.

57B19083 • 57B1FF3D
57B19083 57B19903
Explanation: System log entry only. No service action Explanation: Tape device information was logged.
required. Informational event, no service required.
57B19084 57B1C000
Explanation: System log entry only. No service action Explanation: System log entry only. No service action
required. required.
57B19090 is logged for information only.
last known status. 57B1C402
Response: Use Hardware Service Manager to re-IPL Explanation: Licensed Internal Code error.
assistance.
Failing Item:
reference code to resolve the problem. v PTFSRCH

level of support. 57B1FF3D

v STORIOA
57B19091 v ANYBRDG
detected.
level of support.
Failing Item:
v SVCDOCS
57B19092
use.
Failing Item:
v SIP3134
57B19500
Failing Item:
v PTFSRCH

57B21310 • 57B24020

57B21310 57B23401
v DEVBPLN
them.
57B23405
57B23000
model.
v ANYBRDG
v SIP3150 PTFs.
v SIP3150
Failing Item:
57B23140 v PTFSRCH

required. 57B234FF


required.
v SVCDOCS
57B24010
57B23400
Failing Item:
enclosures.
v SIP3150
Failing Item:
v FI02112
v SIP3142
v STORIOA
v SASCABL
57B24020

57B24030 • 57B24110

57B24070
design limits.
Failing Item:
required.
v SIP3143
57B24080
57B24030

57B24040 corrective action.

v SIP3295
57B24085
Failing Item:
v SIP3144 Explanation: Storage controller detected error. Contact
57B24041
Failing Item:
v NEXTLVL
57B24100
Failing Item:
v SIP3146
Failing Item:
v SIP3152
57B24050
v SASCABL
v SASEXP
multipath function.
v DEVBPLN
Failing Item:
v STORIOA
v SIP3148
v FI01105
57B24060
57B24101
Failing Item:
failed.
v SIP3152
Failing Item:
v SIP3153
57B24110
v SASCABL
v SASEXP
detected.
Failing Item:
57B24061
v SIP3145

57B24120 • 57B28140
57B24120 57B28008
Explanation: SAS cable VPD cannot be read. Explanation: A permanent failure has occurred in the
Failing Item:
v SASCABL Response: Under a certain configuration, this SRC
57B24121 the Storage IOA may have been altered and/or the
Explanation: SAS cable is missing. Storage IOA Cache may have been disabled to allow
Failing Item: Source drive. If this is the case, this error will be posted
v SASCABL each time the IOA is IPLed and it can be ignored.
Failing Item:
57B24123 v CACHBAT
Explanation: Configuration error, invalid cable Vital v STORIOA
Product Data. The storage controller detected invalid v FEATCRD
VPD on the SAS cable. This is most likely caused by a
non IBM cable or a wrap plug. The system will
continue to run. 57B28009
Problem determination: Verify that wrap plugs have Explanation: Impending failure in the cache battery
been removed and the cable is an IBM part. If the pack or capacitive cache power card.
problem persists contact your next level of support. Failing Item:
v SASCABL
57B28100
Explanation: I/O adapter detected PCI bus error. Failing Item:
Response: If this event appears in a serviceable event v PTFSRCH
57B28130
Failing Item:
v BACKPLN
error.
v STORIOA
Explanation: I/O adapter detected and recovered a service action is required.
PCI bus error. Failing Item:
57B28140
Failing Item:
error.
v BACKPLN
v STORIOA
57B270DD service action is required.
Explanation: Disrupt device command completed Failing Item:
successfully. v SIP3150

57B28141 • 57B28157
57B28141 57B28156
Explanation: IOA detected recoverable device error. Explanation: A permanent failure occurred.
v STORIOA
57B28145
Explanation: Disk device detected recoverable error. 57B28157
Response: This error is logged against the storage Explanation: I/O adapter card error. The actions and
controller resource. Contact your next level of support Failing Item list in the Service Action Log will vary
to determine the part number and location code of the based on the conditions this event was logged for.
device.
Failing Item: vary based on the conditions this event was logged for.
v NEXTLVL Perform the following:
57B28146 2. If the Failing Item indicates SVCDOCS, then
Explanation: Disk device detected recoverable error. step. Do NOT replace the I/O adapter. This is a
Failing Item: recoverable error.
v FI01105 v LIC will automatically re-IPL the virtual I/O
57B28150 may need to be Varied On.
Explanation: A permanent failure occurred. v If the virtual I/O processor or adapter are not
Response: Under a certain configuration, this SRC to manually re-IPL the virtual I/O processor and
may not represent an error that requires a service Vary On attached resources.
ends the procedure.
Source drive. If this is the case, this error will be posted 3. If the Failing Item indicates an I/O adapter, then
each time the IOA is IPLed and it can be ignored. replace the I/O adapter. Check the list below to
Failing Item: multiple physical parts.
v STORIOA
v ANYBRDG
57B28151 continue with this step. Otherwise go to the next
Explanation: Licensed Internal Code error. step. Do NOT replace the I/O adapter. This is a
recoverable error.
Failing Item:
v PTFSRCH processor associated with the adapter. Other
v STORIOA resources attached to the virtual I/O processor
Failing Item:
v PTFSRCH
v STORIOA ends the procedure.
I/O adapter.

57B28300 • 57B29010
Failing Item:
57B28302
v SVCDOCS
v STORIOA
57B28300
Failing Item:
v SVCDOCS
v STORIOA
expansion unit. If the adapter is in an expansion 57B28400
unit, continue with the next step. Otherwise this Explanation: Licensed Internal Code error.
ends the procedure.
Failing Item:
unit logged reference code xxxx8300 as a serviceable v PTFSRCH
next step. Otherwise this ends the procedure. 57B28404
enclosure. The problem may have been temporary Explanation: System log entry only. No service action
while working on the unit or while working on the required.
problems were created while working on the unit or 57B29000
and call out the FRUs that connect the expansion Failing Item:
unit to the system unit including the cable(s). Work v FI01105
v STORIOA
this procedure.
that the adapters have returned to operational 57B29001
status. Close reference code xxxx8300 problems for Explanation: Device configuration error.
Expansion units attached to system units using Failing Item:
Light Path service indicators may have activated the v NEXTLVL
indicators for adapters that have returned to 57B29002
operational status. Explanation: Device error.
Failing Item:
status. This ends the procedure. v NEXTLVL
Failing Item:
57B29008
v STORIOA
v ANYBRDG Explanation: I/O card does not support functions
v PTFSRCH
Failing Item:
57B28301 v SIP3130

Code. 57B29010

v PTFSRCH
v SIP3120

57B29011 • 57B29031
57B29011 57B29026
Explanation: Cache data belongs to devices other than Explanation: Disk unit not found at required physical
those attached. location.
Failing Item: Response: A previously exposed disk unit in an array
Failing Item:
57B29020 v NEXTLVL
RAID-5 or RAID-6 array. 57B29027
Failing Item: Explanation: Array not functional due to parity out of
57B29021 parity data is out of synchronization.
Explanation: Two or more disk units missing from Failing Item:

RAID-5 or RAID-6 array. v SIP3113
Failing Item:
v SIP3111 57B29028
57B29022 has been exceeded.
Explanation: Two or more disk units missing from Response: Reduce the number of arrays on this I/O
RAID-5 or RAID-6 array. adapter. Either move all the devices in an array to
Failing Item: array on this I/O adapter.
v SIP3111
Failing Item:
v SVCDOCS
57B29023
Explanation: One or more array members not in 57B29029
Failing Item: members has been exceeded.
v SIP3112
Failing Item:
57B29024
v NEXTLVL
with another array.
57B29030
Failing Item:
v NEXTLVL
Failing Item:
57B29025
v SIP3110
v FI02112
57B29031
exposed.
Failing Item:
v FI02112

57B29032 • 57B29075
Failing Item:
57B29032
v NEXTLVL
failed.
57B29054
unit should be replaced. Explanation: IOA resources not available due to
previous problems.
Failing Item:
Failing Item:
v SIP3110
v SIP3121
v FI02112
57B29055
57B29040
storage IOA.
initiated.
57B29070
57B29041
required.
57B29071
the problem.
Failing Item:
IOA is operational.
v NEXTLVL
57B29042
57B29072
Failing Item:
57B29073
v NEXTLVL
57B29050
Failing Item:
Failing Item:
57B29074
v SIP3131
57B29051
Failing Item:
Failing Item:
v SIP3141
v SIP3132
57B29075
57B29052
Explanation: Incomplete multipath connection
modified devices.
Failing Item:
v SIP3149

57B29076 • 57B2FF3D

57B29076
level of support.
Failing Item:
Failing Item:
v SIP3147
v SVCDOCS
57B29081
57B29092
Failing Item: use.
v STORIOA v SIP3134
57B29082 57B29500
Explanation: Device error. Explanation: Internal program error in driver code.
v FI01105 v PTFSRCH
v STORIOA
57B29903
57B29083
required.
57B2C000
57B29084
required.
57B29090
Explanation: Disk unit has been modified after the 57B2C402
last known status.
assistance.
If you cannot resolve the problem, contact your next 57B2FF3D
v SVCDOCS v STORIOA
v ANYBRDG
57B29091
detected.

57B31310 • 57B34020

57B31310 57B33401
v DEVBPLN
them.
57B33405
57B33000
model.
v ANYBRDG
v SIP3150 PTFs.
v SIP3150
Failing Item:
57B33140 v PTFSRCH

required. 57B334FF


required.
v SVCDOCS
57B34010
57B33400
Failing Item:
enclosures.
v SIP3150
Failing Item:
v FI02112
v SIP3142
v STORIOA
v SASCABL
57B34020

57B34030 • 57B34160

57B34070
design limits.
Failing Item:
required.
v SIP3143
57B34100
57B34030
Failing Item:
v SIP3152
v SIP3144 v SASEXP
v DEVBPLN
57B34040 v STORIOA
I/O adapter and enclosure. 57B34101

v SIP3152
57B34041
Explanation: Incomplete multipath connection. 57B34110
v SIP3146 v SIP3145
57B34050 57B34150
multipath function.

v BACKPLN
v STORIOA
failed.
57B34160
Failing Item:
v SASCABL
57B34061 service action is required.

v BACKPLN

57B370DD • 57B38155
Failing Item:
57B370DD
v SIP3150
successfully.
57B38141

may not represent an error that requires a service 57B38145
v CACHBAT v NEXTLVL
v STORIOA
v FEATCRD 57B38146
57B38009
Failing Item:
v CACHBAT
57B38100

v STORIOA
error. v ANYBRDG

Failing Item:
Failing Item:
v PTFSRCH
v SIP3150
v STORIOA
57B38140
57B38155


57B38156 • 57B38301
Failing Item:
57B38156
v SVCDOCS
v STORIOA
Failing Item:
v PTFSRCH 57B38300
v STORIOA
57B38157
this procedure.
ends the procedure.
operational status.
v PTFSRCH
operational then use Hardware Service Manager 57B38301
Failing Item:
I/O adapter.

57B38302 • 57B39025
57B38302 57B39011
those attached.
v SVCDOCS
v STORIOA 57B39020

v SIP3111
Failing Item:
v PTFSRCH
57B39021
57B38404 Explanation: Two or more disk units missing from

v SIP3111
57B39000
57B39022
Failing Item:
v FI01105
Failing Item:
v STORIOA
v SIP3111
57B39001
57B39023
v NEXTLVL
Failing Item:
v SIP3112
57B39002
Failing Item:
57B39008 v NEXTLVL
expected by devices. 57B39025
v SIP3130
57B39010 exposed.

v SIP3120

57B39026 • 57B39052
57B39026 57B39032
location. failed.
v NEXTLVL v SIP3110
v FI02112
57B39027
Explanation: Array not functional due to parity out of 57B39040
Failing Item:
v SIP3113 57B39041
57B39042
Failing Item:
v SVCDOCS
on disk unit.
57B39029
the problem.
Failing Item:
v NEXTLVL
v NEXTLVL
more disk units.
57B39030
Failing Item:
v SIP3110
Failing Item:
57B39031
v SIP3132
Response: Either a previous rebuild was interrupted 57B39052
modified devices.

57B39054 • 57B39091
Failing Item:
57B39076
v NEXTLVL

v SIP3147
previous problems.
57B39081
Failing Item:
Failing Item:
57B39055 v FI01105
storage IOA.
required. v STORIOA
57B39071 57B39083
57B39084
57B39072 Explanation: System log entry only. No service action
57B39073 last known status.
v SIP3140
57B39074
Failing Item:
v SIP3141
detected.
57B39075
Failing Item:

57B39092 • 57B43401

57B3C000
level of support.
required.
Failing Item:
57B39092 57B3C402
use.
v SIP3134
Failing Item:
v PTFSRCH
57B39500
Explanation: Internal program error in driver code. 57B3FF3D
v PTFSRCH
Failing Item:
v STORIOA
57B39903
v ANYBRDG

57B41310
required.
Response: The I/O adapter error log is being filled 57B43202
Failing Item:
57B43400
v STORIOA
Failing Item:
57B43020 v SIP3150
v STORIOA
Failing Item:
v SASCABL
v SIP3150
57B43401
57B43100
Failing Item:
Failing Item:
v SASEXP
v SIP3150
v DEVBPLN
57B43140

57B43405 • 57B44080
v SIP3144
57B43405
57B44040
Failing Item:
problems.
v Check the device firmware level and apply the latest 57B44041
PTFs.

multipath function.
logged for information only. 57B44060
57B43601
required.
Failing Item:
v SIP3153
57B44010
v SASCABL
enclosures. 57B44061
v SIP3142
57B44020
Failing Item:
v SIP3143 57B44080
57B44030 controller exceeded the maximum operating
temperature.
Problem determination: Verify that the storage
Response: Incorrect multipath connection. controller is placed in a valid location for this type of
Failing Item: controller and enclosure. Perform the procedure listed

57B44085 • 57B48100

57B44123
corrective action.
Failing Item:
Product Data. The storage controller detected invalid
v SIP3295 VPD on the SAS cable. This is most likely caused by a
57B44085 continue to run.
Explanation: Storage controller detected error. Contact Problem determination: Verify that wrap plugs have
your next level of support or hardware service provider been removed and the cable is an IBM part. If the
for more information before replacing any hardware. problem persists contact your next level of support.

v NEXTLVL v SASCABL
57B44100 57B44150
Explanation: Device bus fabric error. Explanation: I/O adapter detected PCI bus error.

v SASCABL service action is required.
v DEVBPLN v BACKPLN
v STORIOA v STORIOA
v FI01105
57B44160
57B44101
Explanation: Temporary device bus fabric error. PCI bus error.
57B44110
Failing Item:
v BACKPLN
detected.
v STORIOA
Failing Item:
v SIP3145
57B470DD
57B44120
successfully.
Explanation: SAS cable VPD cannot be read.
v SASCABL Explanation: Impending failure in the cache battery
Explanation: SAS cable is missing. v CACHBAT
Failing Item:
v SASCABL 57B48100
Failing Item:
v PTFSRCH
v STORIOA

57B48130 • 57B48157
57B48130 57B48151
Explanation: IOA detected recoverable device bus Explanation: Licensed Internal Code error.
error.
Failing Item:
v STORIOA
57B48155
Failing Item:
v SIP3150 Explanation: A permanent failure occurred.
Failing Item:
57B48140 v PTFSRCH
error.
Response: If this event appears in a serviceable event 57B48156
view, work with the failing item list found there. If this Explanation: A permanent failure occurred.
v SIP3150 v STORIOA
57B48141 57B48157
Explanation: IOA detected recoverable device error. Explanation: I/O adapter card error. The actions and
Response: No action is required. This reference code based on the conditions this event was logged for.
57B48145 Perform the following:
Explanation: Disk device detected recoverable error. 1. Display the Service Action Log entry for this SRC.
recoverable error.
device.
v NEXTLVL resources attached to the virtual I/O processor
Explanation: Disk device detected recoverable error. to manually re-IPL the virtual I/O processor and
Failing Item: Vary On attached resources.
v FI01105 v If manually reIPL-ing the virtual I/O processor
ends the procedure.
57B48150 3. If the Failing Item indicates an I/O adapter, then
Explanation: A permanent failure occurred. replace the I/O adapter. Check the list below to
Failing Item: multiple physical parts.
v STORIOA
v ANYBRDG

57B48300 • 57B49001
recoverable error.
Failing Item:
v STORIOA
Vary On attached resources. Explanation: Not valid condition in Licensed Internal
v If manually reIPL-ing the virtual I/O processor Code.
fails then contact your next level of support. This Failing Item:
ends the procedure.
v PTFSRCH
v STORIOA
I/O adapter.
57B48302
Failing Item:
v SVCDOCS Explanation: Missing Licensed Internal Code.
v STORIOA Response: Ensure that the code necessary to support
Explanation: IOA hardware error or PCI bus error. v SVCDOCS
v STORIOA
determine if the adapter is in the system unit or an 57B48400
ends the procedure. Failing Item:
2. If multiple storage adapters in the same expansion v PTFSRCH
event at about the same time, continue with the 57B48404
3. Suspect a problem with the connection to the Explanation: System log entry only. No service action
enclosure. The problem may have been temporary required.
connection or cable(s) to the unit. If the adapter 57B49000
working on the connection to the unit, go to step 5. Explanation: Device error.
4. Search for problems logged at about the same time Failing Item:
v STORIOA
this procedure.
5. Use Hardware Service Manager (HSM) to verify 57B49001
adapters that have returned to operational status. Failing Item:
operational status.

57B49002 • 57B49029
57B49002 57B49024
Explanation: Device error. Explanation: Array member physical location conflicts
with another array.
Failing Item:
v NEXTLVL
57B49008
57B49025
expected by devices. Explanation: Incompatible device.
Failing Item: Response: An incompatible device is at the physical
v SIP3130 location of the device which is causing the array to be
exposed.

v SIP3110
devices cannot be found. v FI02112
Failing Item:
57B49026
v SIP3120
location.
57B49011
those attached.
Failing Item:
Failing Item:
v NEXTLVL
v NEXTLVL
57B49027
57B49020
synchronization.
Failing Item:
v SIP3111
Failing Item:
v SIP3113
57B49021
57B49028
Failing Item:
has been exceeded.
v SIP3111
57B49022 another I/O adapter that supports arrays, or stop an
RAID-5 or RAID-6 array. Failing Item:
v SIP3111
57B49029
57B49023 Explanation: Maximum number of functional array
required physical locations. Response: Contact your next level of support.
v SIP3112 v NEXTLVL

57B49030 • 57B49072
57B49030 57B49050
Explanation: Array no longer protected due to Explanation: Required cache data not found for one or
missing or failed disk unit. more disk units.
v SIP3110 v SIP3131
v FI02112
57B49051
57B49031 Explanation: Cache data exists for one or more
Explanation: Automatic rebuild initiated for array. missing or failed devices.
Response: Either a previous rebuild was interrupted Failing Item:

and was automatically restarted, or a hot spare disk v SIP3132
57B49052
57B49032
modified devices.
failed.
Failing Item:
unit should be replaced. v NEXTLVL
Failing Item:
57B49054
v SIP3110
v FI02112 Explanation: IOA resources not available due to
previous problems.

v SIP3121
initiated.
57B49055
storage IOA.
57B49041
57B49070
the problem. Explanation: System log entry only. No service action
required.
Failing Item:
v NEXTLVL
57B49071
57B49042 Explanation: Link from IOA to auxiliary or remote

IOA is operational.
on disk unit. Response: No service action required.

the problem. 57B49072

v NEXTLVL

57B49073 • 57B4C000
57B49073 57B49090
57B49074
Failing Item:
Failing Item:
v SVCDOCS
v SIP3141
57B49091
57B49075
57B49076 If any reference codes are surfaced, use the new

v SIP3147
Failing Item:
v SVCDOCS
57B49081
v FI01105 use.
v SIP3134
57B49082
Failing Item: Explanation: Internal program error in driver code.
v STORIOA v PTFSRCH
57B49083 57B49903
57B49084 57B4C000
required. required.

57B4C402 • 57B53601
57B4C402 57B4FF3D
Explanation: Licensed Internal Code error. Explanation: I/O adapter detected a recoverable error.
Response: Ask your next level of support for Failing Item:
assistance. v STORIOA
v PTFSRCH

v SIP3150
57B51310
v FI02112
v STORIOA
Response: The I/O adapter error log is being filled v SASCABL
them. 57B53401
Explanation: A permanent failure occurred. v SASEXP
v STORIOA
v ANYBRDG 57B53405
57B53020 initialization for a removable media device. This SRC is
Explanation: Storage subsystem configuration error. device driver cannot determine the device type or
Failing Item: model.
v SIP3150 Response: Perform the following:
57B53100 indicate interface problems and work those
problems.
Failing Item: PTFs.
v SIP3150 v Check for LIC logs with major code 2E00. Contact
have gathered.
57B53140
Explanation: System log entry only. No service action device identification process. If the error persists then
required. contact your service provider.
Failing Item:
57B53202
v PTFSRCH
Response: The device is not supported in the current 57B534FF
Failing Item:
v SVCDOCS logged for information only.
57B53400 57B53601
Explanation: Unknown resource error. Explanation: System log entry only. No service action

57B54010 • 57B54101
v SIP3153
57B54010
v SASCABL
v SASEXP
enclosures.
57B54061
Failing Item:
v SIP3142
57B54020
Failing Item:
v SIP3143 57B54080
57B54030 controller exceeded the maximum operating
temperature.
v SIP3144 in the failing items to determine the problem and
corrective action.

v SIP3295
Response: Incomplete multipath connection between 57B54085
Explanation: Storage controller detected error. Contact
Failing Item: your next level of support or hardware service provider
v SIP3144 for more information before replacing any hardware.
Failing Item:
57B54041 v NEXTLVL
Response: Incomplete multipath connection between 57B54100
device backplane and device. Explanation: Device bus fabric error.
v SIP3146 v SIP3152
v SASCABL
57B54050 v SASEXP
Explanation: Enclosure does not support required v DEVBPLN
multipath function. v STORIOA
v SIP3148
57B54101
57B54060 Explanation: Temporary device bus fabric error.
Explanation: Multipath redundancy level reduced. Failing Item:
Response: A redundant disk unit connection has v SIP3152
failed.
Failing Item:

57B54110 • 57B58145
57B54110 57B570DD
Explanation: Unsupported enclosure function Explanation: Disrupt device command completed
detected. successfully.
Failing Item:
v SIP3145 57B58100
Explanation: SAS cable VPD cannot be read. v PTFSRCH
v SASCABL
57B58130
57B54121 Explanation: IOA detected recoverable device bus
error.
Failing Item:
Explanation: Configuration error, invalid cable Vital v SIP3150
57B58140
continue to run. Explanation: IOA detected recoverable device bus
error.
Problem determination: Verify that wrap plugs have
been removed and the cable is an IBM part. If the Response: If this event appears in a serviceable event
problem persists contact your next level of support. view, work with the failing item list found there. If this
Failing Item:
v SASCABL
Failing Item:
v SIP3150
57B54150
57B58141
event does not appear in a serviceable event view, no Response: No action is required. This reference code
service action is required. is logged for information only.
Failing Item:
v BACKPLN 57B58145
v STORIOA Explanation: Disk device detected recoverable error.
57B54160 controller resource. Contact your next level of support
device.
PCI bus error.
Failing Item:
view, work with the failing item list found there. If this v NEXTLVL
Failing Item:
v BACKPLN
v STORIOA

57B58146 • 57B58300

57B58146
Explanation: Disk device detected recoverable error. v If manually reIPL-ing the virtual I/O processor
ends the procedure.
v FI01105
57B58150 determine if the adapter type you are replacing has

57B58151 recoverable error.
57B58155
ends the procedure.
v PTFSRCH
v STORIOA contact your next level of support to replace the
I/O adapter.
v PTFSRCH
v STORIOA 57B58300
57B58157 Problem determination: Perform the following:
ends the procedure.
recoverable error.

57B58301 • 57B59023

this procedure.
57B59001
57B59008
Failing Item:
v STORIOA
v ANYBRDG
Failing Item:
v PTFSRCH
v SIP3130
57B58301
57B59011
Code. Explanation: Cache data belongs to devices other than
those attached.
Failing Item:
Failing Item:
v PTFSRCH
v NEXTLVL
v STORIOA
57B59020
57B58302
Failing Item:
v SIP3111
Failing Item:
v SVCDOCS
57B59021
v STORIOA
57B58400
Failing Item:
v SIP3111
Failing Item:
v PTFSRCH 57B59022
required.
v SIP3111
57B59000
57B59023

57B59024 • 57B59042

v NEXTLVL
57B59024
Explanation: Array member physical location conflicts 57B59030
v SIP3110
57B59025 v FI02112
57B59031
exposed.
v FI02112
57B59032
57B59026
failed.
location.
Failing Item:
Failing Item:
v SIP3110
v NEXTLVL
v FI02112
57B59027
57B59040
initiated.
Failing Item:
57B59041
v SIP3113
57B59028
the problem.
has been exceeded.
Failing Item:
array on this I/O adapter. 57B59042
57B59029 the problem.

57B59050 • 57B59084
57B59050 57B59073
Explanation: Required cache data not found for one or Explanation: Multiple I/O adapters connected in a not
more disk units. valid configuration.
v SIP3131 v SIP3140
57B59051 57B59074
Failing Item:
57B59052 v SIP3141
modified devices. 57B59075
Failing Item:
v SIP3149
57B59054
57B59076
v SIP3121 v SIP3147
57B59055 57B59081
storage IOA.
Failing Item:
v STORIOA
57B59070
Explanation: System log entry only. No service action 57B59082
required.
Failing Item:
57B59071
v FI01105
v STORIOA
IOA is operational.
57B59083
57B59072
required.
57B59084
required.

57B59090 • 57B74100
v SIP3134
57B59090
57B59500
last known status.
the virtual I/O processor that is associated with this Failing Item:
I/O adapter. Other resources attached to the virtual v PTFSRCH
If any reference codes are surfaced, use the new 57B59903
If you cannot resolve the problem, contact your next Informational event, no service required.
level of support.
v SVCDOCS
required.
57B59091
Explanation: Incorrect hardware configuration change is logged for information only.
detected.
Response: Use Hardware Service Manager to re-IPL 57B5C402
I/O adapter. Other resources attached to the virtual Explanation: Licensed Internal Code error.
I/O processor may then need to be Varied On. Response: Ask your next level of support for
If any reference codes are surfaced, use the new assistance.
reference code to resolve the problem. Failing Item:
level of support.
Failing Item: 57B5FF3D
v SVCDOCS Explanation: I/O adapter detected a recoverable error.
Failing Item:
57B59092
v STORIOA
Explanation: Disk unit requires initialization before v ANYBRDG
use.
Failing Item:

57B71310 57B73400
Explanation: I/O adapter resource not available. Explanation: Unknown resource error.
faster than the errors are being reported to the system. v PRIMIOA
v AUXIOA
them.
v BACKPLN
57B73100
57B74100
Failing Item:
Failing Item:
v AUXIOA
v SIP3152
v PRIMIOA
v SASCABL
v BACKPLN
v SASEXP

57B74101 • 57B78150
v DEVBPLN
57B78009
v STORIOA
v FI01105
Failing Item:
57B74101 v CACHBAT

57B78100
Failing Item:
v SIP3152
Failing Item:
57B74150 v PTFSRCH
v AUXIOA
57B78130
event does not appear in a serviceable event view, no Explanation: I/O adapter detected recoverable bus
v AUXIOA
Failing Item:
57B74160
v PRIMIOA
v AUXIOA
PCI bus error.
v BACKPLN
event does not appear in a serviceable event view, no 57B78140
service action is required. Explanation: I/O adapter detected recoverable bus
v AUXIOA view, work with the failing item list found there. If this
57B78008
Failing Item:
v PRIMIOA
occurred.
v AUXIOA
v BACKPLN
the Storage IOA may have been altered and/or the 57B78150
Source drive. If this is the case, this error will be posted Response: NOTE: Under a certain configuration, this
each time the IOA is IPLed and it can be ignored. SRC may not represent an error that requires a service
Failing Item:
v CACHBAT Storage IOA Cache may have been disabled to allow
v AUXIOA attachment of OEM Storage that emulates a Load
Failing Item:
v AUXIOA
v ANYBRDG

57B78151 • 57B7FF3D
57B78151 57B78302
Explanation: Licensed Internal Code error. Explanation: Missing Licensed Internal Code.
v AUXIOA Failing Item:
v SVCDOCS
57B78155 v AUXIOA
57B79055
Failing Item:
v PTFSRCH Explanation: Write cache data is available for attached
storage IOA.
v AUXIOA
57B78156
57B79071
Failing Item:
went operational.
v PTFSRCH
v AUXIOA
57B79072
57B78157
SVCDOCS, then do NOT replace the I/O adapter. This 57B79073
is a recoverable error. Use Hardware Service Manager
to re-IPL the virtual I/O processor that is associated
with this I/O adapter.
Failing Item:
Failing Item:
v SIP3140
v SVCDOCS
57B79076
57B78300
Explanation: Missing remote I/O adapter.
Explanation: IOA hardware or PCI bus error.
Failing Item:
Failing Item:
v SIP3147
v AUXIOA
v PRIMIOA
v ANYBRDG
v AUXIOA
v PTFSRCH
v BACKPLN
57B78301
57B7FF3D
Code. Explanation: I/O adapter detected recoverable error.

v PTFSRCH
v AUXIOA service action is required.
Failing Item:
v AUXIOA
v ANYBRDG

57B81310 • 57B84020

57B81310 57B83401
v DEVBPLN
them.
57B83405
57B83000
model.
v ANYBRDG
v SIP3150 PTFs.
v SIP3150
Failing Item:
57B83140 v PTFSRCH

required. 57B834FF


required.
v SVCDOCS
57B84010
57B83400
Failing Item:
enclosures.
v SIP3150
Failing Item:
v FI02112
v SIP3142
v STORIOA
v SASCABL
57B84020

57B84030 • 57B84160

57B84070
design limits.
Failing Item:
required.
v SIP3143
57B84100
57B84030
Failing Item:
v SIP3152
v SIP3144 v SASEXP
v DEVBPLN
57B84040 v STORIOA
I/O adapter and enclosure. 57B84101

v SIP3152
57B84041
Explanation: Incomplete multipath connection. 57B84110
v SIP3146 v SIP3145
57B84050 57B84150
multipath function.

v BACKPLN
v STORIOA
failed.
57B84160
Failing Item:
v SASCABL

v BACKPLN

57B870DD • 57B88155
Failing Item:
57B870DD
v SIP3150
successfully.
57B88141

may not represent an error that requires a service 57B88145
v CACHBAT v NEXTLVL
v STORIOA
v FEATCRD 57B88146
57B88009
Failing Item:
v CACHBAT
57B88100

v STORIOA
error. v ANYBRDG

Failing Item:
Failing Item:
v PTFSRCH
v SIP3150
v STORIOA
57B88140
57B88155


57B88156 • 57B88301
Failing Item:
57B88156
v SVCDOCS
v STORIOA
Failing Item:
v PTFSRCH 57B88300
v STORIOA
57B88157
this procedure.
ends the procedure.
operational status.
v PTFSRCH
Failing Item:
I/O adapter.

57B88302 • 57B89025
57B88302 57B89011
those attached.
v SVCDOCS
v STORIOA 57B89020

v SIP3111
Failing Item:
v PTFSRCH
57B89021
57B88404 Explanation: Two or more disk units missing from

v SIP3111
57B89000
57B89022
Failing Item:
v FI01105
Failing Item:
v STORIOA
v SIP3111
57B89001
57B89023
v NEXTLVL
Failing Item:
v SIP3112
57B89002
Failing Item:
57B89008 v NEXTLVL
expected by devices. 57B89025
v SIP3130
57B89010 exposed.

v SIP3120

57B89026 • 57B89052
57B89026 57B89032
location. failed.
v NEXTLVL v SIP3110
v FI02112
57B89027
Explanation: Array not functional due to parity out of 57B89040
Failing Item:
v SIP3113 57B89041
57B89042
Failing Item:
v SVCDOCS
on disk unit.
57B89029
the problem.
Failing Item:
v NEXTLVL
v NEXTLVL
more disk units.
57B89030
Failing Item:
v SIP3110
Failing Item:
57B89031
v SIP3132
Response: Either a previous rebuild was interrupted 57B89052
modified devices.

57B89054 • 57B89091
Failing Item:
57B89076
v NEXTLVL

v SIP3147
previous problems.
57B89081
Failing Item:
Failing Item:
57B89055 v FI01105
storage IOA.
required. v STORIOA
57B89071 57B89083
57B89084
57B89072 Explanation: System log entry only. No service action
57B89073 last known status.
v SIP3140
57B89074
Failing Item:
v SIP3141
detected.
57B89075
Failing Item:

57B89092 • 57BB3401

57B8C000
level of support.
required.
Failing Item:
57B89092 57B8C402
use.
v SIP3134
Failing Item:
v PTFSRCH
57B89500
Explanation: Internal program error in driver code. 57B8FF3D
v PTFSRCH
Failing Item:
v STORIOA
57B89903
v ANYBRDG
(57BB) Reference codes

57BB1310
required.
Response: The I/O adapter error log is being filled 57BB3202
Failing Item:
57BB3400
v STORIOA
Failing Item:
57BB3020 v SIP3150
v STORIOA
Failing Item:
v SASCABL
v SIP3150
57BB3401
57BB3100
Failing Item:
Failing Item:
v SASEXP
v SIP3150
v DEVBPLN
57BB3140

57BB3405 • 57BB4080
v SIP3144
57BB3405
57BB4040
Failing Item:
problems.
v Check the device firmware level and apply the latest 57BB4041
PTFs.

multipath function.
57BB34FF Failing Item:
logged for information only. 57BB4060
57BB3601
required.
Failing Item:
v SIP3153
57BB4010
v SASCABL
enclosures. 57BB4061
v SIP3142
57BB4020
Explanation: Configuration error. 57BB4070
Failing Item:
v SIP3143 57BB4080
57BB4030 controller exceeded the maximum operating
temperature.

57BB4085 • 57BB8130

57BB4123
corrective action.
Failing Item:
v SIP3295 VPD on the SAS cable. This is most likely caused by a
57BB4085 continue to run.
Explanation: Storage controller detected error. Contact Problem determination: Verify that wrap plugs have
your next level of support or hardware service provider been removed and the cable is an IBM part. If the
for more information before replacing any hardware. problem persists contact your next level of support.

v NEXTLVL v SASCABL
57BB4100 57BB4150
Explanation: Device bus fabric error. Explanation: I/O adapter detected PCI bus error.

v SASCABL service action is required.
v DEVBPLN v BACKPLN
v STORIOA v STORIOA
v FI01105
57BB4160
57BB4101
Explanation: Temporary device bus fabric error. PCI bus error.
57BB4110
Failing Item:
v BACKPLN
detected.
v STORIOA
Failing Item:
v SIP3145
57BB70DD
57BB4120
successfully.
v SASCABL Explanation: Licensed Internal Code error.
Failing Item:
57BB4121
v PTFSRCH
Explanation: SAS cable is missing. v STORIOA
Failing Item:
v SASCABL 57BB8130
error.

57BB8140 • 57BB8157

57BB8155
Failing Item:
v PTFSRCH
57BB8140 v STORIOA

error. 57BB8156
Response: If this event appears in a serviceable event Explanation: A permanent failure occurred.
v PTFSRCH
v STORIOA
Failing Item:
v SIP3150
57BB8157
57BB8141
Explanation: IOA detected recoverable device error. based on the conditions this event was logged for.
Response: No action is required. This reference code Response: The FRU list in the Service Action Log will
is logged for information only. vary based on the conditions this event was logged for.
57BB8145 1. Display the Service Action Log entry for this SRC.
Response: This error is logged against the storage step. Do NOT replace the I/O adapter. This is a
controller resource. Contact your next level of support recoverable error.
to determine the part number and location code of the v LIC will automatically re-IPL the virtual I/O
device. processor associated with the adapter. Other
v NEXTLVL
57BB8146 to manually re-IPL the virtual I/O processor and
v FI01105 ends the procedure.
57BB8150 replace the I/O adapter. Check the list below to
57BB8151 step. Do NOT replace the I/O adapter. This is a
recoverable error.
v PTFSRCH
v STORIOA

57BB8300 • 57BB9008

57BB8301
v If manually reIPL-ing the virtual I/O processor Explanation: Not valid condition in Licensed Internal
fails then contact your next level of support. This Code.
3. If the Failing Item indicates an I/O adapter, then v PTFSRCH
v STORIOA
I/O adapter.
Failing Item:
57BB8302
v SVCDOCS
v STORIOA
57BB8300
Failing Item:
v SVCDOCS
v STORIOA
expansion unit. If the adapter is in an expansion 57BB8400
ends the procedure.
2. If multiple storage adapters in the same expansion Failing Item:
57BB8404
problems were created while working on the unit or 57BB9000
this procedure. v STORIOA

that the adapters have returned to operational 57BB9001
indicators for adapters that have returned to 57BB9002
adapters that have not returned to operational Failing Item:
Failing Item:
v STORIOA 57BB9008

v PTFSRCH expected by devices.
Failing Item:
v SIP3130

57BB9011 • 57BB9031
57BB9011 57BB9026
Failing Item:
57BB9020 v NEXTLVL
RAID-5 or RAID-6 array. 57BB9027
57BB9021 parity data is out of synchronization.

Failing Item:
v SIP3111 57BB9028
57BB9022 has been exceeded.
v SIP3111
Failing Item:
v SVCDOCS
57BB9023
Explanation: One or more array members not in 57BB9029
v SIP3112
Failing Item:
57BB9024
v NEXTLVL
with another array.
57BB9030
Failing Item:
v NEXTLVL
Failing Item:
57BB9025
v SIP3110
v FI02112
57BB9031
exposed.
Failing Item:
v FI02112

57BB9032 • 57BB9074
Failing Item:
57BB9032
v NEXTLVL
failed.
57BB9054
previous problems.
Failing Item:
Failing Item:
v SIP3110
v SIP3121
v FI02112
57BB9055
57BB9040
storage IOA.
initiated.
57BB9070
57BB9041
required.
57BB9071
the problem.
Failing Item:
IOA is operational.
v NEXTLVL
57BB9042
57BB9072
Failing Item:
57BB9073
v NEXTLVL
57BB9050
Failing Item:
Failing Item:
57BB9074
v SIP3131
57BB9051
Problem determination: The 57BB storage adapter has
been paired with another storage adapter that is not
capable of similar functions or controlling the same set
Failing Item: of devices. Cache on both adapters has been disabled.
v SIP3132 The adapters will run together without cache. To run
with cache install compatible storage adapters.

v SIP3141
modified devices.

57BB9075 • 57BBFF3D
57BB9075 57BB9091
Explanation: Incomplete multipath connection Explanation: Incorrect hardware configuration change
between IOA and remote IOA. detected.
57BB9076
Explanation: Missing auxiliary IOA or remote IOA. reference code to resolve the problem.
Failing Item: If you cannot resolve the problem, contact your next
v SIP3147 level of support.
Failing Item:
57BB9081 v SVCDOCS
v FI01105 Explanation: Disk unit requires initialization before

v STORIOA use.
Failing Item:
57BB9082 v SIP3134
57BB9500
Failing Item:
v FI01105 Explanation: Internal program error in driver code.
v PTFSRCH
57BB9083
Explanation: System log entry only. No service action 57BB9903
required. Explanation: Tape device information was logged.
57BB9084
Explanation: System log entry only. No service action 57BBC000
required. Explanation: System log entry only. No service action
required.
57BB9090 Response: No action is required. This reference code
last known status.
Response: Use Hardware Service Manager to re-IPL 57BBC402
the virtual I/O processor that is associated with this Explanation: Licensed Internal Code error.
I/O processor may then need to be Varied On. Response: Ask your next level of support for
assistance.
reference code to resolve the problem. Failing Item:
v PTFSRCH
level of support.
57BBFF3D
Failing Item:
v SVCDOCS Explanation: I/O adapter detected a recoverable error.
Failing Item:
v STORIOA

57C31310 • 57C33100
v ANYBRDG
(57C3) Reference codes

57C31310
Explanation: The I/O adapter resource not available. serviceable event. Before starting a repair action for this
them.
Failing Item:
57C31511
v DISKPWR
v DEVBPLN
supply 1.
v SASEXP
Failing Item:
v DISKPWR
57C33000
v DEVBPLN
v SASEXP
Failing Item:
57C31515 v STORIOA
v ANYBRDG
1.
57C33002
a loss of utility power, battery back up or UPS power Explanation: Addressed device backplane failed to
to the I/O storage unit. The unit and power supply respond to selection.
Failing Item: power failure. Restore power to the expansion unit and
v DISKPWR close the xxxx3002 problems. Otherwise work the
v DEVBPLN
v SASEXP
57C31521 v SASCABL
v STORIOA
supply 2. v DEVBPLN
Failing Item:
57C33020
v DISKPWR
v DEVBPLN Explanation: Storage subsystem configuration error.
v SIP3150
57C31525
Explanation: A fatal error occurred on power supply 57C33100
2. Explanation: Device bus interface error occurred.
Problem determination: This SRC can be the result of Failing Item:
v SIP3150

57C33109 • 57C34040

57C33109
Explanation: I/O adapter timed out a device have gathered.
backplane command.
v SASEXP contact your service provider.
v STORIOA v PTFSRCH
v DEVBPLN
57C334FF
57C33140 Explanation: Format in progress.
Explanation: System log entry only. No service action Response: No action required. This reference code is
required. logged for information only.
57C33202 57C33601
Explanation: Storage subsystem configuration error. Explanation: System log entry only. No service action
Response: The device is not supported in the current required.
v SVCDOCS Explanation: Configuration error.
57C33400 enclosures.
Explanation: Unknown resource error. Failing Item:
v SIP3150
v FI02112 57C34020
v STORIOA Explanation: Configuration error.
v SASCABL Response: Number of connections exceed I/O adapter
design limits.
Explanation: Device backplane problem. v SIP3143
Failing Item:
v SASEXP 57C34030
v DEVBPLN Explanation: Configuration error.
57C33405
Failing Item:
Explanation: An error occurred during task v SIP3144
device driver cannot determine the device type or 57C34040
model. Explanation: Configuration error.
Response: Perform the following: Response: Incomplete multipath connection between
v Check the Product Activity Log for other entries that I/O adapter and enclosure.
problems. Failing Item:
v Check the device firmware level and apply the latest v SIP3144
PTFs.

57C34041 • 57C34123
Failing Item:
57C34041
v NEXTLVL
Response: Incomplete multipath connection between 57C34100
Failing Item:
Failing Item:
v SIP3146
v SIP3152
v SASCABL
57C34050
v SASEXP
v DEVBPLN
multipath function.
v STORIOA
Failing Item:
v FI01105
v SIP3148
57C34101
57C34060
Failing Item:
v SIP3152
failed.
Failing Item:
57C34102
v SIP3153
Explanation: Internal device bus fabric performance
v SASCABL
degradation.
v SASEXP
Failing Item:
v SIP3254
57C34061
57C34110
detected.
Failing Item:
57C34070
v SIP3145
required.
57C34120
57C34080 Explanation: SAS cable VPD cannot be read.
Explanation: Storage controller thermal error. The Failing Item:

controller exceeded the maximum operating v SASCABL
temperature.
Problem determination: Verify that the storage 57C34121
controller and enclosure. Perform the procedure listed Explanation: SAS cable is missing.
in the failing items to determine the problem and Failing Item:
corrective action.
v SASCABL
Failing Item:
v SIP3295 57C34123
57C34085 Product Data. The storage controller detected invalid
Explanation: Storage controller detected error. Contact VPD on the SAS cable. This is most likely caused by a
your next level of support or hardware service provider non IBM cable or a wrap plug. The system will
for more information before replacing any hardware. continue to run.

57C34150 • 57C376B4

57C37634
been removed and the cable is an IBM part. If the
problem persists contact your next level of support. Explanation: A fatal error occurred on fan 3.
v SASCABL v DISKFAN
57C34150 57C37644
Explanation: I/O adapter detected PCI bus error. Explanation: A fatal error occurred on fan 4.
view, work with the failing item list found there. If this v DISKFAN
57C37654
Failing Item:
v BACKPLN
v DISKFAN
57C34160
57C37664
PCI bus error. Explanation: A fatal error occurred on fan 6.
view, work with the failing item list found there. If this v DISKFAN
57C37674
Failing Item:
v BACKPLN Explanation: A fatal error occurred on fan 7.
v DISKFAN
57C370DD
Explanation: Disrupt device command completed 57C37684
successfully. Explanation: A fatal error occurred on fan 8.
Failing Item:
57C37604
v DISKFAN
v DISKFAN Explanation: A fatal error occurred on fan 9.
Failing Item:
57C37614
v DISKFAN
Failing Item: 57C376A4
Failing Item:
57C37624
v DISKFAN
Failing Item: 57C376B4
Failing Item:
v DISKFAN

57C376C4 • 57C38156
57C376C4 57C38141
Explanation: A fatal error occurred on fan 12. Explanation: IOA detected recoverable device error.
v DISKFAN is logged for information only.
57C376D4 57C38145
Explanation: A fatal error occurred on fan 13. Explanation: Disk device detected recoverable error.

v DISKFAN
device.
57C376E4
Failing Item:
Explanation: A fatal error occurred on fan 14. v NEXTLVL
Failing Item:
v DISKFAN 57C38146
57C376F4
Failing Item:
Explanation: A fatal error occurred on fan 15. v FI01105
Failing Item:
v DISKFAN 57C38150
57C38100
Failing Item:
Explanation: Licensed Internal Code error. v STORIOA
v PTFSRCH
v STORIOA 57C38151
57C38130
Failing Item:
Explanation: IOA detected recoverable device bus v PTFSRCH
error.
v STORIOA
57C38155
service action is required. Explanation: A permanent failure occurred.
v SIP3150 v PTFSRCH
v STORIOA
57C38140
Explanation: IOA detected recoverable device bus 57C38156
v PTFSRCH
Failing Item:
v SIP3150

57C38157 • 57C38302
57C38157 57C38300
Explanation: I/O adapter card error. The actions and Explanation: IOA hardware error or PCI bus error.
Response: The FRU list in the Service Action Log will determine if the adapter is in the system unit or an
vary based on the conditions this event was logged for. expansion unit. If the adapter is in an expansion
Perform the following: unit, continue with the next step. Otherwise this
1. Display the Service Action Log entry for this SRC. ends the procedure.
2. If the Failing Item indicates SVCDOCS, then 2. If multiple storage adapters in the same expansion
continue with this step. Otherwise go to the next unit logged reference code xxxx8300 as a serviceable
step. Do NOT replace the I/O adapter. This is a event at about the same time, continue with the
recoverable error. next step. Otherwise this ends the procedure.
v LIC will automatically re-IPL the virtual I/O 3. Suspect a problem with the connection to the
processor associated with the adapter. Other enclosure. The problem may have been temporary
resources attached to the virtual I/O processor while working on the unit or while working on the
may need to be Varied On. connection or cable(s) to the unit. If the adapter
v If the virtual I/O processor or adapter are not problems were created while working on the unit or
operational then use Hardware Service Manager working on the connection to the unit, go to step 5.
to manually re-IPL the virtual I/O processor and 4. Search for problems logged at about the same time
Vary On attached resources. and call out the FRUs that connect the expansion
v If manually reIPL-ing the virtual I/O processor unit to the system unit including the cable(s). Work
fails then contact your next level of support. This those problems first, then return to the next step in
ends the procedure. this procedure.
3. If the Failing Item indicates an I/O adapter, then 5. Use Hardware Service Manager (HSM) to verify
replace the I/O adapter. Check the list below to that the adapters have returned to operational
determine if the adapter type you are replacing has status. Close reference code xxxx8300 problems for
multiple physical parts. adapters that have returned to operational status.
Problem determination: Perform the following: Light Path service indicators may have activated the
1. Display the Service Action Log entry for this SRC. FRU fault indicators for those adapters. Use the
2. If the Failing Item indicates SVCDOCS, then Service Action Log (SAL) to turn off the FRU fault
continue with this step. Otherwise go to the next indicators for adapters that have returned to
step. Do NOT replace the I/O adapter. This is a operational status.
recoverable error. 6. Work reference code xxxx8300 problems for any
v LIC will automatically re-IPL the virtual I/O adapters that have not returned to operational
processor associated with the adapter. Other status. This ends the procedure.
resources attached to the virtual I/O processor Failing Item:
v STORIOA
v ANYBRDG
to manually re-IPL the virtual I/O processor and v PTFSRCH
v If manually reIPL-ing the virtual I/O processor 57C38301
ends the procedure.
Code.
contact your next level of support to replace the Failing Item:
I/O adapter. v PTFSRCH
v SVCDOCS
v STORIOA 57C38302

57C38400 • 57C39027
Failing Item:
57C39021
v SVCDOCS
v STORIOA
Failing Item:
57C38400
v SIP3111
v PTFSRCH
57C38404
Failing Item:
Explanation: System log entry only. No service action v SIP3111
required.
57C39023
57C39000
Explanation: Device error. required physical locations.
v FI01105 v SIP3112
v STORIOA
57C39024
57C39001
Explanation: Device configuration error. with another array.
v NEXTLVL v NEXTLVL
57C39002 57C39025
Explanation: Device error. Explanation: Incompatible device.
Failing Item: Response: An incompatible device is at the physical
v NEXTLVL location of the device which is causing the array to be
exposed.

v SIP3110
expected by devices. v FI02112
Failing Item:
57C39026
v SIP3130
location.
57C39011
Explanation: Cache data belongs to devices other than was not found at the required physical location.
those attached.
Failing Item:
Failing Item:
v NEXTLVL
v NEXTLVL
57C39027
57C39020
Explanation: Two or more disk units missing from synchronization.
Failing Item: parity data is out of synchronization.
v SIP3111

57C39028 • 57C39055
Failing Item:
57C39041
v SIP3113
57C39028
Explanation: Maximum number of functional arrays the problem.
has been exceeded.
Failing Item:
v NEXTLVL
array on this I/O adapter. 57C39042
57C39029 the problem.

57C39050
Failing Item:
v NEXTLVL Explanation: Required cache data not found for one or
more disk units.

v SIP3131
57C39051
Failing Item:
v SIP3110 Explanation: Cache data exists for one or more
v FI02112
Failing Item:
57C39031 v SIP3132

57C39052
and was automatically restarted, or a hot spare disk Explanation: Cache data exists for one or more
unit was used to automatically rebuild the array. Look modified devices.
for other reference codes and take action on them. Response: Contact your next level of support.
Failing Item:
57C39032
v NEXTLVL
failed.
57C39054
previous problems.
Failing Item:
Failing Item:
v SIP3110
v SIP3121
v FI02112
57C39055
57C39040
Explanation: Re-synchronization of array parity was storage IOA.
initiated.

57C39070 • 57C39092
57C39070 57C39082
required.
Failing Item:
v FI01105
57C39071
v STORIOA
IOA is operational.
57C39083
required.
57C39072
Explanation: Link from IOA to auxiliary or remote 57C39084
57C39073 57C39090
57C39074
Failing Item:
Failing Item:
v SVCDOCS
v SIP3141
57C39091
57C39075
57C39076 If any reference codes are surfaced, use the new
v SIP3147
Failing Item:
v SVCDOCS
57C39081
Explanation: Device error. 57C39092
v FI01105 use.
v SIP3134

57C39500 • 57C43405
Failing Item:
57C39500
v PTFSRCH
Failing Item: 57C3FF3D
v PTFSRCH
Failing Item:
57C39903
v STORIOA
v ANYBRDG
57C3FFF4
57C3C000
Response: No action is required. This reference code v SASEXP
is logged for information only. v SASCABL
v STORIOA
57C3C402 v DEVBPLN
assistance.

57C41310
required.
Response: The I/O adapter error log is being filled 57C43202
Failing Item:
57C43400
v STORIOA
Failing Item:
57C43020 v SIP3150
v STORIOA
Failing Item:
v SASCABL
v SIP3150
57C43401
57C43100
Failing Item:
Failing Item:
v SASEXP
v SIP3150
v DEVBPLN
57C43140
57C43405

57C434FF • 57C44080

57C44040
model.
Failing Item:
v SIP3144
problems.
v Check the device firmware level and apply the latest 57C44041
PTFs. Explanation: Incomplete multipath connection.

multipath function.
57C434FF Failing Item:
logged for information only. 57C44060
57C43601
required.
Failing Item:
v SIP3153
57C44010
v SASCABL
enclosures. 57C44061
v SIP3142
57C44020
Explanation: Configuration error. 57C44070
Failing Item:
v SIP3143 57C44080
57C44030 controller exceeded the maximum operating
temperature.
controller and enclosure. Perform the procedure listed
Failing Item:
v SIP3144 corrective action.

57C44085 • 57C48130
Failing Item: Problem determination: Verify that wrap plugs have

v SIP3295 been removed and the cable is an IBM part. If the
problem persists contact your next level of support.

v SASCABL
for more information before replacing any hardware. 57C44150
Failing Item: Explanation: I/O adapter detected PCI bus error.
v NEXTLVL Response: If this event appears in a serviceable event
Failing Item:
Failing Item:
v BACKPLN
v SIP3152
v STORIOA
v SASCABL
v SASEXP
57C44160
v DEVBPLN
v STORIOA
PCI bus error.
v FI01105
Explanation: Temporary device bus fabric error. service action is required.

v SIP3152 v BACKPLN
v STORIOA
57C44110
57C470DD
detected. Explanation: Disrupt device command completed
successfully.
Failing Item:
v SIP3145
57C48009
57C44120 Explanation: Impending failure in the cache battery

Failing Item:
v SASCABL
57C48100
57C44121
Failing Item:
v SASCABL v STORIOA
57C44123 57C48130
Explanation: Configuration error, invalid cable Vital Explanation: IOA detected recoverable device bus
Product Data. The storage controller detected invalid error.
non IBM cable or a wrap plug. The system will Response: If this event appears in a serviceable event
continue to run. view, work with the failing item list found there. If this

57C48140 • 57C48157

57C48155
Failing Item:
v PTFSRCH
57C48140 v STORIOA

error. 57C48156
Response: If this event appears in a serviceable event Explanation: A permanent failure occurred.
v PTFSRCH
v STORIOA
Failing Item:
v SIP3150
57C48157
57C48141
Explanation: IOA detected recoverable device error. based on the conditions this event was logged for.
Response: No action is required. This reference code Response: The FRU list in the Service Action Log will
is logged for information only. vary based on the conditions this event was logged for.
57C48145 1. Display the Service Action Log entry for this SRC.
Response: This error is logged against the storage step. Do NOT replace the I/O adapter. This is a
controller resource. Contact your next level of support recoverable error.
to determine the part number and location code of the v LIC will automatically re-IPL the virtual I/O
device. processor associated with the adapter. Other
v NEXTLVL
57C48146 to manually re-IPL the virtual I/O processor and
v FI01105 ends the procedure.
57C48150 replace the I/O adapter. Check the list below to
57C48151 step. Do NOT replace the I/O adapter. This is a
recoverable error.
v PTFSRCH
v STORIOA

57C48300 • 57C49008

57C48301
v If manually reIPL-ing the virtual I/O processor Explanation: Not valid condition in Licensed Internal
fails then contact your next level of support. This Code.
v STORIOA
I/O adapter.
Failing Item:
57C48302
v SVCDOCS
v STORIOA
57C48300
Failing Item:
v SVCDOCS
v STORIOA
expansion unit. If the adapter is in an expansion 57C48400
ends the procedure.
2. If multiple storage adapters in the same expansion Failing Item:
57C48404
problems were created while working on the unit or 57C49000
this procedure. v STORIOA

that the adapters have returned to operational 57C49001
indicators for adapters that have returned to 57C49002
adapters that have not returned to operational Failing Item:
Failing Item:
v STORIOA 57C49008

v PTFSRCH expected by devices.
Failing Item:
v SIP3130

57C49010 • 57C49030

57C49010
exposed.
Failing Item:
v SIP3110
Failing Item:
v FI02112
v SIP3120
57C49026
57C49011
Explanation: Cache data belongs to devices other than location.
those attached.
Failing Item: was not found at the required physical location.
v NEXTLVL
Failing Item:
v NEXTLVL
57C49020
Explanation: Two or more disk units missing from 57C49027
Failing Item: synchronization.
v SIP3111
57C49021
Failing Item:
Explanation: Two or more disk units missing from v SIP3113
v SIP3111
has been exceeded.
57C49022
Explanation: Two or more disk units missing from adapter. Either move all the devices in an array to
RAID-5 or RAID-6 array. another I/O adapter that supports arrays, or stop an
Failing Item:
v SVCDOCS
57C49023
57C49029
required physical locations. Explanation: Maximum number of functional array
Failing Item:
v SIP3112 Response: Contact your next level of support.
Failing Item:
57C49024 v NEXTLVL
with another array. 57C49030
v NEXTLVL missing or failed disk unit.
Failing Item:
57C49025 v SIP3110
Explanation: Incompatible device. v FI02112

57C49031 • 57C49073
57C49031 57C49051
Explanation: Automatic rebuild initiated for array. Explanation: Cache data exists for one or more
and was automatically restarted, or a hot spare disk Failing Item:
unit was used to automatically rebuild the array. Look v SIP3132
57C49052
57C49032
Explanation: A disk unit in an array is missing or modified devices.
failed.
unit should be replaced. Failing Item:
v NEXTLVL
Failing Item:
v SIP3110
57C49054
v FI02112
previous problems.
57C49040
Failing Item:
initiated. v SIP3121

57C49055
57C49041 Explanation: Write cache data is available for attached

storage IOA.
and corrected errors. Response: No service action required.

the problem. 57C49070

required.
v NEXTLVL
57C49071
57C49042
IOA is operational.
on disk unit.
the problem.
57C49072
Failing Item:
v NEXTLVL Explanation: Link from IOA to auxiliary or remote
57C49050 Response: No service action required.

more disk units. 57C49073
Failing Item: Explanation: Multiple I/O adapters connected in a not

v SIP3131
Failing Item:
v SIP3140

57C49074 • 57C4C402

57C49074
level of support.
Failing Item:
v SVCDOCS
Failing Item:
v SIP3141
57C49091
57C49075
detected.
Failing Item: I/O adapter. Other resources attached to the virtual
v SIP3149 I/O processor may then need to be Varied On.
57C49076 reference code to resolve the problem.
Explanation: Missing auxiliary IOA or remote IOA. If you cannot resolve the problem, contact your next
level of support.
Failing Item:
Failing Item:
v SIP3147
v SVCDOCS
57C49081
57C49092
Failing Item: use.
v FI01105
Failing Item:
v STORIOA
v SIP3134
57C49082
57C49500
Failing Item:
Failing Item:
v FI01105
v PTFSRCH
v STORIOA
57C49903
57C49083
required.
57C4C000
57C49084
required.
57C49090
Explanation: Disk unit has been modified after the 57C4C402
last known status.
the virtual I/O processor that is associated with this Response: Ask your next level of support for
I/O adapter. Other resources attached to the virtual assistance.

57C4FF3D • 57C64010

v STORIOA
57C4FF3D v ANYBRDG

v SASCABL
57C61310
57C63401
Check other errors reported to the system and correct Failing Item:
them. v SASEXP
v DEVBPLN
57C63000
Explanation: A permanent failure occurred. 57C63405
v STORIOA initialization for a removable media device. This SRC is
v ANYBRDG
model.
57C63020
Explanation: Storage subsystem configuration error. v Check the Product Activity Log for other entries that
Failing Item: indicate interface problems and work those
problems.
v SIP3150
PTFs.
57C63100
Explanation: Device bus interface error occurred. your next level of support with the information you
have gathered.
Failing Item:
v SIP3150 Problem determination: IPL the IOP to retry the
57C63140
Failing Item:
Explanation: System log entry only. No service action v PTFSRCH
required.
57C634FF
57C63202
Response: The device is not supported in the current logged for information only.
v SVCDOCS
required.
57C63400
Explanation: Unknown resource error. 57C64010
v SIP3150 Response: Incorrect connection between cascaded
v FI02112 enclosures.
v STORIOA

57C64020 • 57C64110
Failing Item:
57C64061
v SIP3142
57C64020 Response: A redundant disk unit connection has been

Response: Number of connections exceed I/O adapter 57C64070
design limits.
v SIP3143
57C64080
57C64030
temperature.
Failing Item: controller is placed in a valid location for this type of
corrective action.
57C64040
Failing Item:
v SIP3295
57C64085
Failing Item:
v SIP3144
57C64041
Failing Item:
Explanation: Incomplete multipath connection. v NEXTLVL
device backplane and device. 57C64100
Failing Item: Explanation: Device bus fabric error.
v SIP3146
Failing Item:
v SIP3152
57C64050
v SASCABL
Explanation: Enclosure does not support required v SASEXP
multipath function.
v DEVBPLN
v SIP3148 v FI01105
57C64060 57C64101
Explanation: Multipath redundancy level reduced. Explanation: Temporary device bus fabric error.
failed.
v SIP3152
Failing Item:
v SIP3153 57C64110
v SASCABL
v SASEXP detected.
Failing Item:

57C64120 • 57C68140
v SIP3145
57C670DD
57C64120
successfully.
v SASCABL Explanation: A permanent failure has occurred in the
57C64121 Response: Under a certain configuration, this SRC
Explanation: SAS cable is missing. may not represent an error that requires a service
Failing Item: the Storage IOA may have been altered and/or the
v SASCABL Storage IOA Cache may have been disabled to allow
57C64123 each time the IOA is IPLed and it can be ignored.
Explanation: Configuration error, invalid cable Vital Failing Item:
v CACHBAT
non IBM cable or a wrap plug. The system will v STORIOA
continue to run. v FEATCRD
been removed and the cable is an IBM part. If the 57C68009
Failing Item: pack or capacitive cache power card.
v CACHBAT
57C64150
Explanation: I/O adapter detected PCI bus error. 57C68100
Response: If this event appears in a serviceable event Explanation: Licensed Internal Code error.
event does not appear in a serviceable event view, no Failing Item:
service action is required. v PTFSRCH
v BACKPLN
v STORIOA 57C68130
57C64160 error.
Explanation: I/O adapter detected and recovered a Response: If this event appears in a serviceable event
PCI bus error. view, work with the failing item list found there. If this
service action is required. v SIP3150
Failing Item:
v BACKPLN 57C68140

error.

57C68141 • 57C68157
Failing Item:
57C68156
v SIP3150

v PTFSRCH
v STORIOA
57C68157
57C68145 Explanation: I/O adapter card error. The actions and

Explanation: Disk device detected recoverable error. based on the conditions this event was logged for.
Response: This error is logged against the storage Response: The FRU list in the Service Action Log will
controller resource. Contact your next level of support vary based on the conditions this event was logged for.
to determine the part number and location code of the Perform the following:
device.
Failing Item: 2. If the Failing Item indicates SVCDOCS, then
v NEXTLVL continue with this step. Otherwise go to the next
recoverable error.
57C68146
Explanation: Disk device detected recoverable error. processor associated with the adapter. Other
Failing Item:
v FI01105
Response: Under a certain configuration, this SRC fails then contact your next level of support. This
may not represent an error that requires a service ends the procedure.
each time the IOA is IPLed and it can be ignored. Problem determination: Perform the following:
Failing Item: 1. Display the Service Action Log entry for this SRC.
v STORIOA 2. If the Failing Item indicates SVCDOCS, then
v ANYBRDG
recoverable error.
57C68151 v LIC will automatically re-IPL the virtual I/O
Explanation: Licensed Internal Code error. processor associated with the adapter. Other
Failing Item: may need to be Varied On.
v PTFSRCH v If the virtual I/O processor or adapter are not
v STORIOA operational then use Hardware Service Manager
57C68155
Explanation: A permanent failure occurred. fails then contact your next level of support. This
ends the procedure.
Failing Item:
v PTFSRCH
v STORIOA I/O adapter.

57C68300 • 57C69010
Failing Item:
57C68302
v SVCDOCS
v STORIOA
57C68300
Failing Item:
v SVCDOCS
v STORIOA
expansion unit. If the adapter is in an expansion 57C68400
ends the procedure.
Failing Item:
next step. Otherwise this ends the procedure. 57C68404
problems were created while working on the unit or 57C69000
v STORIOA
this procedure.
that the adapters have returned to operational 57C69001
status. Close reference code xxxx8300 problems for Explanation: Device configuration error.
indicators for adapters that have returned to 57C69002
Failing Item:
Failing Item:
57C69008
v STORIOA
v PTFSRCH
Failing Item:
57C68301 v SIP3130

Code. 57C69010

v PTFSRCH
v SIP3120

57C69011 • 57C69031
57C69011 57C69026
Failing Item:
57C69020 v NEXTLVL
RAID-5 or RAID-6 array. 57C69027
57C69021 parity data is out of synchronization.

Failing Item:
v SIP3111 57C69028
57C69022 has been exceeded.
v SIP3111
Failing Item:
v SVCDOCS
57C69023
Explanation: One or more array members not in 57C69029
v SIP3112
Failing Item:
57C69024
v NEXTLVL
with another array.
57C69030
Failing Item:
v NEXTLVL
Failing Item:
57C69025
v SIP3110
v FI02112
57C69031
exposed.
Failing Item:
v FI02112

57C69032 • 57C69075
Failing Item:
57C69032
v NEXTLVL
failed.
57C69054
previous problems.
Failing Item:
Failing Item:
v SIP3110
v SIP3121
v FI02112
57C69055
57C69040
storage IOA.
initiated.
57C69070
57C69041
required.
57C69071
the problem.
Failing Item:
IOA is operational.
v NEXTLVL
57C69042
57C69072
Failing Item:
57C69073
v NEXTLVL
57C69050
Failing Item:
Failing Item:
57C69074
v SIP3131
57C69051
Failing Item:
Failing Item:
v SIP3141
v SIP3132
57C69075
57C69052
modified devices.
Failing Item:
v SIP3149

57C69076 • 57C6FF3D

57C69076
level of support.
Failing Item:
Failing Item:
v SIP3147
v SVCDOCS
57C69081
57C69092
Failing Item: use.
v STORIOA v SIP3134
57C69082 57C69500
Explanation: Device error. Explanation: Internal program error in driver code.
v FI01105 v PTFSRCH
v STORIOA
57C69903
57C69083
required.
57C6C000
57C69084
required.
57C69090
Explanation: Disk unit has been modified after the 57C6C402
last known status.
assistance.
If you cannot resolve the problem, contact your next 57C6FF3D
v SVCDOCS v STORIOA
v ANYBRDG
57C69091
detected.

57C71310 • 57C73405

57C71310
backplane.
Explanation: The I/O adapter resource not available. v The Battery charger and carrier card.
Response: The I/O adapter error log is being filled v See symbolic FRU FEATCRD for the location codes
faster than the errors are being reported to the system. of the FRUs if they are not listed in the serviceable
Check other errors reported to the system and correct event or if you are working the failing item list here.
them.
with 2BC2 dual battery charger and carrier card). When
57C73000
Explanation: A permanent failure occurred. failing item list here, the embedded storage adapter
Failing Item:
v STORIOA
backplane.
v ANYBRDG
57C73020 embedded IOA use the bus number of the IOA with
Failing Item: the dual battery charger and carrier card if it is not
v SIP4050 listed in the serviceable event or if you are working

v SIP4050
v FI02112
Failing Item:
v STORIOA
v SIP4050
v SASCABL
57C73140
57C73401
required.
Failing Item:
57C73202 v SASEXP
v DEVBPLN
57C73405
Failing Item:
v SVCDOCS logged when an error occurs and the removable media
57C73400 model.
Explanation: Unknown resource error. Response: Perform the following:

problems.
the storage adapter. v Check the device firmware level and apply the latest
PTFs.
card). When working the FRUs from the serviceable
event or the failing item list here, the embedded
have gathered.
storage adapter (failing item STORIOA) has two
physical parts: Problem determination: IPL the IOP to retry the

57C734FF • 57C74110
contact your service provider. v SIP3146

Failing Item:
v PTFSRCH 57C74050
57C734FF multipath function.

v SIP3148
57C74060
57C73601 Explanation: Multipath redundancy level reduced.
Explanation: System log entry only. No service action Response: A redundant disk unit connection has
required. failed.
Failing Item:
57C74010 v SIP4053
Explanation: Configuration error. v SASCABL
Response: Incorrect connection between cascaded v SASEXP
enclosures.
v SIP3142 Explanation: Multipath redundancy level increased.
57C74020 restored. No service action is required.
57C74070
design limits. Explanation: System log entry only. No service action
required.
Failing Item:
v SIP3143
57C74100
57C74030 Explanation: Device bus fabric error.

v SIP4052
v SASCABL
Failing Item:
v SASEXP
v SIP4044
v DEVBPLN
v STORIOA
57C74040
v FI01105
Response: Incomplete multipath connection between 57C74101
Failing Item:
Failing Item:
v SIP4044
v SIP4052
57C74041
57C74110
Response: Incomplete multipath connection between detected.
Failing Item:

57C74150 • 57C78146
57C74150 57C78100
Explanation: I/O adapter detected PCI bus error. Explanation: Licensed Internal Code error.
v STORIOA
Failing Item:
57C78130
v BACKPLN
v STORIOA
error.
57C74160
Explanation: I/O adapter detected and recovered a event does not appear in a serviceable event view, no
PCI bus error. service action is required.
57C78140
Failing Item:
v BACKPLN
error.
v STORIOA
57C770DD event does not appear in a serviceable event view, no
Explanation: Disrupt device command completed service action is required.
successfully. Failing Item:
v SIP4050
57C78008
Explanation: A permanent failure has occurred in the 57C78141
Storage IOA Cache may have been disabled to allow 57C78145
Source drive. If this is the case, this error will be posted Explanation: Disk device detected recoverable error.
each time the IOA is IPLed and it can be ignored. Response: This error is logged against the storage
Failing Item: controller resource. Contact your next level of support
v CACHBAT device.
v STORIOA
Failing Item:
v FEATCRD
v NEXTLVL
57C78009
57C78146
pack or capacitive cache power card. Explanation: Disk device detected recoverable error.

v CACHBAT v FI01105

57C78150 • 57C78300

57C78150
57C78151
recoverable error.
I/O adapter.
57C78156
Failing Item:
v SVCDOCS
v PTFSRCH
v STORIOA 57C78300
57C78157
2. If the Failing Item indicates SVCDOCS, then event at about the same time, continue with the
continue with this step. Otherwise go to the next next step. Otherwise this ends the procedure.
v LIC will automatically re-IPL the virtual I/O while working on the unit or while working on the
processor associated with the adapter. Other connection or cable(s) to the unit. If the adapter
resources attached to the virtual I/O processor problems were created while working on the unit or
may need to be Varied On. working on the connection to the unit, go to step 5.

57C78301 • 57C79022

this procedure.
57C79001
FRU fault indicators for those adapters. Use the 57C79002
57C79008
Failing Item:
v STORIOA
v ANYBRDG
Failing Item:
v PTFSRCH
v SIP3130
57C78301
57C79010
Failing Item:
Failing Item:
v PTFSRCH
v SIP3120
v STORIOA
57C79011
57C78302
those attached.
Failing Item:
v NEXTLVL
Failing Item:
v SVCDOCS
57C79020
v STORIOA
57C78400
Failing Item:
v SIP3111
Failing Item:
v PTFSRCH 57C79021
57C78404 RAID-5 or RAID-6 array.
required.
v SIP3111
57C79000
57C79022
Failing Item: RAID-5 or RAID-6 array.

57C79023 • 57C79041
v SIP3111 v SVCDOCS
57C79023 57C79029
v NEXTLVL
57C79024
Explanation: Array member physical location conflicts 57C79030
with another array.
v SIP3110
57C79025 v FI02112
Response: An incompatible device is at the physical 57C79031
exposed.
57C79026 57C79032
location. failed.

v NEXTLVL v SIP3110
v FI02112
57C79027
57C79040
initiated.
Failing Item:
v SIP3113 57C79041
57C79028 and corrected errors.

Failing Item:

57C79042 • 57C79082
57C79042 57C79072
the problem.
more disk units.
57C79051 Response: Multiple I/O adapters not capable of
v SIP3132
57C79075
57C79052 Explanation: Incomplete multipath connection
Failing Item:
v NEXTLVL 57C79076
previous problems.
Failing Item:
57C79055
v FI01105
storage IOA.
Response: No service action required. 57C79082
57C79070
Failing Item:
v FI01105
required.
v STORIOA
57C79071
IOA is operational.

57C79083 • 57C7FF3D
57C79083 57C79903
57C79084 57C7C000
required. required.
57C79090 is logged for information only.
last known status. 57C7C402
assistance.
Failing Item:

level of support. 57C7FF3D

v STORIOA
57C79091 v ANYBRDG
detected.
level of support.
Failing Item:
v SVCDOCS
57C79092
use.
Failing Item:
v SIP3134
57C79500
Failing Item:
v PTFSRCH

57CB1310 • 57CB3400
(57CB) Reference codes

57CB1310
Explanation: The I/O adapter resource not available. listed in the serviceable event or if you are working
faster than the errors are being reported to the system. Failing Item:
Check other errors reported to the system and correct v STORIOA
them.
v ANYBRDG
57CB3000
57CB3020
Failing Item:
Choose the card type to identify the physical parts of v SIP4050
Card type 2BE1 (feature RAID enablement card for 57CB3100
embedded IOA) read the following: When working the Explanation: Device bus interface error occurred.
here, the embedded storage adapter (failing item Failing Item:
STORIOA) has three physical parts: v SIP4050
backplane.
57CB3140
required.
event or if you are working the failing item list here. 57CB3202
card for embedded IOA) read the following: When Response: The device is not supported in the current
working the FRUs from the serviceable event or the configuration. An I/O processor might be required.
failing item list here, the embedded storage adapter Failing Item:
v SVCDOCS
backplane.
57CB3400
v See symbolic FRU FEATCRD for the location codes Explanation: Unknown resource error.
of the FRUs if they are not listed in the serviceable Response: If you are working with one of the card
event or if you are working the failing item list here. types below, the adapter has multiple physical parts.
Card type 57CF (embedded IOAs on DASD backplane the storage adapter.
embedded IOAs) read the following: When working Card type 57CB (embedded IOA with 2BCF battery
the FRUs from the serviceable event or the failing item card). When working the FRUs from the serviceable
list here, the embedded storage adapter (failing item event or the failing item list here, the embedded
STORIOA) has two physical parts: storage adapter (failing item STORIOA) has two
physical parts:
backplane. v The embedded storage adapter on the I/O
backplane.
determine which battery is connected to which v The Battery charger and carrier card.
embedded IOA use the bus number of the IOA with v See symbolic FRU FEATCRD for the location codes
symbolic FRU CACHBAT. of the FRUs if they are not listed in the serviceable

57CB3401 • 57CB4041

57CB34FF
working the FRUs from the serviceable event or the Explanation: Format in progress.
backplane.
57CB3601
determine which battery is connected to which Explanation: System log entry only. No service action
embedded IOA use the bus number of the IOA with required.
v See symbolic FRU FEATCRD for the location code of 57CB4010
listed in the serviceable event or if you are working Explanation: Configuration error.
Failing Item: enclosures.
v FI02112 v SIP3142
v STORIOA
v SASCABL 57CB4020
57CB3401
Explanation: Device backplane problem. design limits.
v SASEXP v SIP3143
v DEVBPLN
57CB4030
57CB3405
logged when an error occurs and the removable media Failing Item:
device driver cannot determine the device type or v SIP4044
model.
Response: Perform the following: 57CB4040
problems. Response: Incomplete multipath connection between
v Check the device firmware level and apply the latest I/O adapter and enclosure.
PTFs. Failing Item:
v Check for LIC logs with major code 2E00. Contact v SIP4044
have gathered.
57CB4041
device identification process. If the error persists then Explanation: Incomplete multipath connection.
Failing Item: device backplane and device.
v SIP3146

57CB4050 • 57CB4150

57CB4050
Explanation: Enclosure does not support required embedded IOA use the bus number of the IOA with
multipath function. symbolic FRU CACHBAT.
Failing Item: v See symbolic FRU FEATCRD for the location code of
v SIP3148
57CB4060
Failing Item:
Explanation: Multipath redundancy level reduced. v SIP4052
Response: A redundant disk unit connection has v SASCABL
failed. v SASEXP
v SIP4053 v STORIOA
v SASCABL v FI01105
v SASEXP
57CB4101
57CB4061 Explanation: Temporary device bus fabric error.
Response: A redundant disk unit connection has been v SIP4052
57CB4110
57CB4070
Explanation: System log entry only. No service action detected.
required.
Failing Item:
v SIP3145
57CB4100
Explanation: Device bus fabric error. 57CB4150
Response: If you are working with one of the card Explanation: I/O adapter detected PCI bus error.
Choose the card type to identify the physical parts of Response: If this event appears in a serviceable event
the storage adapter. view, work with the failing item list found there. If this
Card type 57CB (embedded IOA with 2BCF battery service action is required.
working the FRUs from the serviceable event or the If you are working with one of the card types below,
failing item list here, the embedded storage adapter the adapter has multiple physical parts. Choose the
(failing item STORIOA) has two physical parts: card type to identify the physical parts of the storage
adapter.
backplane. Card type 2BE1 (feature RAID enablement card for
v The Battery charger and carrier card. embedded IOA) read the following: When working the
Card type 57CF (embedded IOAs on DASD backplane backplane.
with 2BC2 dual battery charger and carrier card for the v The RAID enablement card.
embedded IOAs) read the following: When working v The Battery charger and carrier card.
backplane.

57CB4160 • 57CB8008
Card type 57CB (embedded IOA with 2BCF battery v See symbolic FRU FEATCRD for the location codes
card for embedded IOA) read the following: When of the FRUs if they are not listed in the serviceable
working the FRUs from the serviceable event or the event or if you are working the failing item list here.
(failing item STORIOA) has two physical parts: Card type 57CB (embedded IOA with 2BCF battery
v The embedded storage adapter on the I/O card for embedded IOA) read the following: When
backplane. working the FRUs from the serviceable event or the
backplane.
Card type 57CF (embedded IOAs on DASD backplane v See symbolic FRU FEATCRD for the location codes
with 2BC2 dual battery charger and carrier card for the of the FRUs if they are not listed in the serviceable
embedded IOAs) read the following: When working event or if you are working the failing item list here.
list here, the embedded storage adapter (failing item Card type 57CF (embedded IOAs on DASD backplane
STORIOA) has two physical parts: with 2BC2 dual battery charger and carrier card for the
v The embedded storage adapter on the DASD embedded IOAs) read the following: When working
backplane. the FRUs from the serviceable event or the failing item
embedded IOA use the bus number of the IOA with v The embedded storage adapter on the DASD
symbolic FRU CACHBAT. backplane.
v See symbolic FRU FEATCRD for the location code of v The dual battery charger and carrier card. To
the dual battery charger and carrier card if it is not determine which battery is connected to which
listed in the serviceable event or if you are working embedded IOA use the bus number of the IOA with
the failing item list here. symbolic FRU CACHBAT.
Failing Item:
v BACKPLN listed in the serviceable event or if you are working
v STORIOA the failing item list here.
Failing Item:
57CB4160 v BACKPLN
Explanation: I/O adapter detected and recovered a v STORIOA
PCI bus error.
Response: If this event appears in a serviceable event 57CB70DD
successfully.
57CB8008
card type to identify the physical parts of the storage Explanation: A permanent failure has occurred in the
adapter. cache battery pack or capacitive cache power card.
Card type 2BE1 (feature RAID enablement card for Response: Under a certain configuration, this SRC
embedded IOA) read the following: When working the may not represent an error that requires a service
FRUs from the serviceable event or the failing item list action. Depending on the configuration of the system,
here, the embedded storage adapter (failing item the Storage IOA may have been altered and/or the
STORIOA) has three physical parts: Storage IOA Cache may have been disabled to allow
v The embedded storage adapter on the I/O attachment of OEM Storage that emulates a Load
backplane. Source drive. If this is the case, this error will be posted
v The Battery charger and carrier card. If you are working with one of the card types below,
adapter.

57CB8009 • 57CB8100

57CB8100
FRUs from the serviceable event or the failing item list Explanation: Licensed Internal Code error.
v The Battery charger and carrier card. embedded IOA) read the following: When working the
v See symbolic FRU FEATCRD for the location codes FRUs from the serviceable event or the failing item list
of the FRUs if they are not listed in the serviceable here, the embedded storage adapter (failing item
event or if you are working the failing item list here. STORIOA) has three physical parts:
Card type 57CB (embedded IOA with 2BCF battery backplane.
card) read the following: When working the FRUs from
the serviceable event or the failing item list here, the
embedded storage adapter (failing item STORIOA) has v The Battery charger and carrier card.
two physical parts: v See symbolic FRU FEATCRD for the location codes
v The embedded storage adapter on the I/O of the FRUs if they are not listed in the serviceable
backplane. event or if you are working the failing item list here.
v See symbolic FRU FEATCRD for the location codes card for embedded IOA) read the following: When
of the FRUs if they are not listed in the serviceable working the FRUs from the serviceable event or the
event or if you are working the failing item list here. failing item list here, the embedded storage adapter
with 2BC2 dual battery charger and carrier card) read
backplane.
the following: When working the FRUs from the
serviceable event or the failing item list here, the v The Battery charger and carrier card.
embedded storage adapter (failing item STORIOA) has v See symbolic FRU FEATCRD for the location codes
two physical parts: of the FRUs if they are not listed in the serviceable
v The embedded storage adapter on the DASD event or if you are working the failing item list here.
backplane.
v See symbolic FRU FEATCRD for the location code of STORIOA) has two physical parts:
backplane.
Failing Item: determine which battery is connected to which
v CACHBAT embedded IOA use the bus number of the IOA with
v STORIOA symbolic FRU CACHBAT.
v FEATCRD v See symbolic FRU FEATCRD for the location code of
57CB8009 the failing item list here.
Explanation: Impending failure in the cache battery Failing Item:
v PTFSRCH
v CACHBAT

57CB8130 • 57CB8151

57CB8130
Explanation: IOA detected recoverable device bus card type to identify the physical parts of the storage
error. adapter.
Response: If this event appears in a serviceable event Card type 2BE1 (feature RAID enablement card for
view, work with the failing item list found there. If this embedded IOA) read the following: When working the
event does not appear in a serviceable event view, no FRUs from the serviceable event or the failing item list
service action is required. here, the embedded storage adapter (failing item
Failing Item:
v SIP4050
backplane.
57CB8140
Explanation: IOA detected recoverable device bus v See symbolic FRU FEATCRD for the location codes
error. of the FRUs if they are not listed in the serviceable
Response: If this event appears in a serviceable event event or if you are working the failing item list here.
event does not appear in a serviceable event view, no Card type 57CB (embedded IOA with 2BCF battery
service action is required. card for embedded IOA) read the following: When
Failing Item: failing item list here, the embedded storage adapter
v SIP4050 (failing item STORIOA) has two physical parts:
57CB8141 backplane.
Response: No action is required. This reference code of the FRUs if they are not listed in the serviceable
is logged for information only. event or if you are working the failing item list here.
57CB8145 Card type 57CF (embedded IOAs on DASD backplane

Explanation: Disk device detected recoverable error. embedded IOAs) read the following: When working
device. v The embedded storage adapter on the DASD
backplane.
Failing Item:
v NEXTLVL determine which battery is connected to which
57CB8146 symbolic FRU CACHBAT.
Failing Item: listed in the serviceable event or if you are working
v FI01105 the failing item list here.
Failing Item:
57CB8150 v STORIOA
Explanation: A permanent failure occurred. v ANYBRDG

may not represent an error that requires a service 57CB8151
action. Depending on the configuration of the system, Explanation: Licensed Internal Code error.
Storage IOA Cache may have been disabled to allow Response: If you are working with one of the card
attachment of OEM Storage that emulates a Load types below, the adapter has multiple physical parts.
Source drive. If this is the case, this error will be posted Choose the card type to identify the physical parts of
each time the IOA is IPLed and it can be ignored. the storage adapter.

57CB8155 • 57CB8156
Card type 2BE1 (feature RAID enablement card for STORIOA) has three physical parts:
Card type 57CB (embedded IOA with 2BCF battery (failing item STORIOA) has two physical parts:
card for embedded IOA) read the following: When v The embedded storage adapter on the I/O
working the FRUs from the serviceable event or the backplane.
backplane.
v See symbolic FRU FEATCRD for the location codes Card type 57CF (embedded IOAs on DASD backplane
of the FRUs if they are not listed in the serviceable with 2BC2 dual battery charger and carrier card for the
event or if you are working the failing item list here. embedded IOAs) read the following: When working
Card type 57CF (embedded IOAs on DASD backplane list here, the embedded storage adapter (failing item
with 2BC2 dual battery charger and carrier card for the STORIOA) has two physical parts:
Failing Item:
listed in the serviceable event or if you are working v PTFSRCH
the failing item list here. v STORIOA
Failing Item:
v PTFSRCH 57CB8156
v STORIOA Explanation: A permanent failure occurred.
57CB8155 types below, the adapter has multiple physical parts.
Card type 2BE1 (feature RAID enablement card for STORIOA) has three physical parts:

57CB8157
v The RAID enablement card. v If the virtual I/O processor or adapter are not
v The Battery charger and carrier card. operational then use Hardware Service Manager
event or if you are working the failing item list here. v If manually reIPL-ing the virtual I/O processor
Card type 57CB (embedded IOA with 2BCF battery ends the procedure.
card for embedded IOA) read the following: When 3. If the Failing Item indicates an I/O adapter, then
working the FRUs from the serviceable event or the replace the I/O adapter. Check the list below to
failing item list here, the embedded storage adapter determine if the adapter type you are replacing has
(failing item STORIOA) has two physical parts: multiple physical parts.
backplane. If you are replacing the I/O adapter and you are
working with one of the card types below, the adapter
has multiple physical parts. Choose the card type to
v See symbolic FRU FEATCRD for the location codes identify the physical parts of the storage adapter.
event or if you are working the failing item list here. Card type 2BE1 (feature RAID enablement card for
Card type 57CF (embedded IOAs on DASD backplane FRUs from the serviceable event or the failing item list
with 2BC2 dual battery charger and carrier card for the here, the embedded storage adapter (failing item
embedded IOAs) read the following: When working STORIOA) has three physical parts:
backplane.
v The dual battery charger and carrier card. To v See symbolic FRU FEATCRD for the location codes
determine which battery is connected to which of the FRUs if they are not listed in the serviceable
embedded IOA use the bus number of the IOA with event or if you are working the failing item list here.
Failing Item: v The embedded storage adapter on the I/O
v PTFSRCH backplane.
v STORIOA v The Battery charger and carrier card.
57CB8157 of the FRUs if they are not listed in the serviceable
Failing Item list in the Service Action Log will vary Card type 57CF (embedded IOAs on DASD backplane
based on the conditions this event was logged for. with 2BC2 dual battery charger and carrier card for the
Response: The FRU list in the Service Action Log will embedded IOAs) read the following: When working
vary based on the conditions this event was logged for. the FRUs from the serviceable event or the failing item
Perform the following: list here, the embedded storage adapter (failing item
backplane.
step. Do NOT replace the I/O adapter. This is a v The dual battery charger and carrier card. To
recoverable error. determine which battery is connected to which

57CB8300 • 57CB8301
v See symbolic FRU FEATCRD for the location code of v The Battery charger and carrier card.
the dual battery charger and carrier card if it is not v See symbolic FRU FEATCRD for the location codes
listed in the serviceable event or if you are working of the FRUs if they are not listed in the serviceable
the failing item list here. event or if you are working the failing item list here.
2. If the Failing Item indicates SVCDOCS, then embedded IOAs) read the following: When working
continue with this step. Otherwise go to the next the FRUs from the serviceable event or the failing item
step. Do NOT replace the I/O adapter. This is a list here, the embedded storage adapter (failing item
recoverable error. STORIOA) has two physical parts:
v LIC will automatically re-IPL the virtual I/O v The embedded storage adapter on the DASD
processor associated with the adapter. Other backplane.
v If the virtual I/O processor or adapter are not embedded IOA use the bus number of the IOA with
operational then use Hardware Service Manager symbolic FRU CACHBAT.
v If manually reIPL-ing the virtual I/O processor listed in the serviceable event or if you are working
fails then contact your next level of support. This the failing item list here.
ends the procedure.
Failing Item:
contact your next level of support to replace the v STORIOA
I/O adapter. v ANYBRDG
v SVCDOCS
v STORIOA 57CB8301
57CB8300 Code.
Explanation: IOA hardware error or PCI bus error. Response: If you are working with one of the card
Response: If you are working with one of the card Choose the card type to identify the physical parts of
types below, the adapter has multiple physical parts. the storage adapter.
the storage adapter. Card type 2BE1 (feature RAID enablement card for
Card type 2BE1 (feature RAID enablement card for FRUs from the serviceable event or the failing item list
embedded IOA) read the following: When working the here, the embedded storage adapter (failing item
FRUs from the serviceable event or the failing item list STORIOA) has three physical parts:
backplane.
backplane.
v See symbolic FRU FEATCRD for the location codes event or if you are working the failing item list here.
event or if you are working the failing item list here. Card type 57CB (embedded IOA with 2BCF battery
Card type 57CB (embedded IOA with 2BCF battery working the FRUs from the serviceable event or the
card for embedded IOA) read the following: When failing item list here, the embedded storage adapter
working the FRUs from the serviceable event or the (failing item STORIOA) has two physical parts:
backplane.
backplane.

57CB8302 • 57CB9000
v See symbolic FRU FEATCRD for the location codes v See symbolic FRU FEATCRD for the location codes
of the FRUs if they are not listed in the serviceable of the FRUs if they are not listed in the serviceable
event or if you are working the failing item list here. event or if you are working the failing item list here.
Card type 57CF (embedded IOAs on DASD backplane Card type 57CF (embedded IOAs on DASD backplane
with 2BC2 dual battery charger and carrier card for the with 2BC2 dual battery charger and carrier card for the
embedded IOAs) read the following: When working embedded IOAs) read the following: When working
the FRUs from the serviceable event or the failing item the FRUs from the serviceable event or the failing item
list here, the embedded storage adapter (failing item list here, the embedded storage adapter (failing item
STORIOA) has two physical parts: STORIOA) has two physical parts:
v The embedded storage adapter on the DASD v The embedded storage adapter on the DASD
backplane. backplane.
v The dual battery charger and carrier card. To v The dual battery charger and carrier card. To
determine which battery is connected to which determine which battery is connected to which
embedded IOA use the bus number of the IOA with embedded IOA use the bus number of the IOA with
symbolic FRU CACHBAT. symbolic FRU CACHBAT.
v See symbolic FRU FEATCRD for the location code of v See symbolic FRU FEATCRD for the location code of
the dual battery charger and carrier card if it is not the dual battery charger and carrier card if it is not
listed in the serviceable event or if you are working listed in the serviceable event or if you are working
the failing item list here. the failing item list here.
v PTFSRCH v SVCDOCS
v STORIOA v STORIOA
57CB8302 57CB8400
Explanation: Missing Licensed Internal Code. Explanation: Licensed Internal Code error.
this I/O adapter is loaded. v PTFSRCH
the adapter has multiple physical parts. Choose the 57CB8404
adapter. Explanation: System log entry only. No service action
required.
FRUs from the serviceable event or the failing item list 57CB9000
here, the embedded storage adapter (failing item Explanation: Device error.
v The embedded storage adapter on the I/O Response: If you are working with one of the card
backplane. types below, the adapter has multiple physical parts.
v The RAID enablement card. the storage adapter.
backplane.
failing item list here, the embedded storage adapter v The RAID enablement card.

57CB9001 • 57CB9025

57CB9010
working the FRUs from the serviceable event or the Explanation: Cache data associated with attached
failing item list here, the embedded storage adapter devices cannot be found.
Failing Item:
v SIP3120
backplane.
57CB9011
of the FRUs if they are not listed in the serviceable Explanation: Cache data belongs to devices other than
event or if you are working the failing item list here. those attached.
Failing Item:
with 2BC2 dual battery charger and carrier card for the v NEXTLVL
the FRUs from the serviceable event or the failing item 57CB9020
STORIOA) has two physical parts: Explanation: Two or more disk units missing from
v The embedded storage adapter on the DASD RAID-5 or RAID-6 array.
backplane. Failing Item:
v The dual battery charger and carrier card. To v SIP3111
symbolic FRU CACHBAT. 57CB9021
v See symbolic FRU FEATCRD for the location code of Explanation: Two or more disk units missing from
the dual battery charger and carrier card if it is not RAID-5 or RAID-6 array.
Failing Item:
v SIP3111
Failing Item:
v FI01105
57CB9022
v STORIOA
57CB9001
Failing Item:
v SIP3111
Failing Item:
v NEXTLVL 57CB9023
57CB9002 required physical locations.
v NEXTLVL
57CB9024
57CB9008 Explanation: Array member physical location conflicts
Explanation: I/O card does not support functions with another array.
expected by devices. Failing Item:
v SIP3130
57CB9025

57CB9026 • 57CB9050

57CB9031
exposed.
Failing Item:
v FI02112
57CB9026
Explanation: Disk unit not found at required physical 57CB9032
location.
v SIP3110
57CB9027 v FI02112
synchronization. 57CB9040
v SIP3113
57CB9041
57CB9028
has been exceeded.
Failing Item:
Failing Item:
57CB9042
v SVCDOCS
on disk unit.
57CB9029
the problem.
Failing Item:
v NEXTLVL
Failing Item:
v NEXTLVL
57CB9050
57CB9030
more disk units.
Failing Item:
v SIP3131
Failing Item:
v SIP3110
v FI02112

57CB9051 • 57CB9081
57CB9051 57CB9074
Failing Item:
57CB9052 v SIP4041
modified devices. 57CB9075
Failing Item:
v SIP4049
57CB9054
57CB9076
v SIP3121 v SIP4047
57CB9055 57CB9081
storage IOA.
Response: No service action required. types below, the adapter has multiple physical parts.
57CB9070
required.
57CB9071 STORIOA) has three physical parts:
Explanation: Link from IOA to auxiliary or remote v The embedded storage adapter on the I/O
IOA is operational. backplane.
Explanation: Link from IOA to auxiliary or remote event or if you are working the failing item list here.
Response: No service action required. card for embedded IOA) read the following: When
57CB9073 failing item list here, the embedded storage adapter
backplane.
v SIP4040 v See symbolic FRU FEATCRD for the location codes

57CB9082 • 57CB9091
Card type 57CF (embedded IOAs on DASD backplane list here, the embedded storage adapter (failing item
with 2BC2 dual battery charger and carrier card for the STORIOA) has two physical parts:
Failing Item:
listed in the serviceable event or if you are working v FI01105
the failing item list here. v STORIOA
Failing Item:
v FI01105 57CB9083
v STORIOA Explanation: System log entry only. No service action
required.
57CB9082
57CB9084
required.
the storage adapter. 57CB9090
Card type 2BE1 (feature RAID enablement card for Explanation: Disk unit has been modified after the
embedded IOA) read the following: When working the last known status.
here, the embedded storage adapter (failing item Response: Use Hardware Service Manager to re-IPL
STORIOA) has three physical parts: the virtual I/O processor that is associated with this
v The embedded storage adapter on the I/O I/O processor may then need to be Varied On.
backplane.
v The RAID enablement card. If any reference codes are surfaced, use the new
v See symbolic FRU FEATCRD for the location codes If you cannot resolve the problem, contact your next
of the FRUs if they are not listed in the serviceable level of support.
event or if you are working the failing item list here. Failing Item:
v SVCDOCS
working the FRUs from the serviceable event or the 57CB9091
detected.
backplane. Response: Use Hardware Service Manager to re-IPL
v See symbolic FRU FEATCRD for the location codes I/O processor may then need to be Varied On.
event or if you are working the failing item list here. If any reference codes are surfaced, use the new
Card type 57CF (embedded IOAs on DASD backplane If you cannot resolve the problem, contact your next
with 2BC2 dual battery charger and carrier card for the level of support.
the FRUs from the serviceable event or the failing item Failing Item:

57CB9092 • 57CC3020
v SVCDOCS embedded IOA) read the following: When working the

57CB9092
Explanation: Disk unit requires initialization before v The embedded storage adapter on the I/O
use. backplane.
Failing Item: v The RAID enablement card.
v SIP3134 v The Battery charger and carrier card.
Failing Item: Card type 57CB (embedded IOA with 2BCF battery
v PTFSRCH working the FRUs from the serviceable event or the
57CB9903 (failing item STORIOA) has two physical parts:
backplane.
57CBC000
Explanation: System log entry only. No service action event or if you are working the failing item list here.
required.
57CBC402 list here, the embedded storage adapter (failing item
Response: Ask your next level of support for backplane.
assistance.
Failing Item: determine which battery is connected to which
v PTFSRCH embedded IOA use the bus number of the IOA with
57CBFF3D the dual battery charger and carrier card if it is not
Explanation: I/O adapter detected a recoverable error. listed in the serviceable event or if you are working
types below, the adapter has multiple physical parts. Failing Item:
Choose the card type to identify the physical parts of v STORIOA
the storage adapter. v ANYBRDG

57CC1310
Failing Item:
v STORIOA
v ANYBRDG
them. 57CC3020
57CC3000

57CC3100 • 57CC4041

v SIP3150 device identification process. If the error persists then

v PTFSRCH
Failing Item:
57CC34FF
v SIP3150
57CC3140 Response: No action required. This reference code is

required.
57CC3601
57CC3202 Explanation: System log entry only. No service action

required.
Response: The device is not supported in the current 57CC4010
Failing Item:
v SVCDOCS
enclosures.
Failing Item:
57CC3400
v SIP3142
Failing Item: 57CC4020
v SIP3150
v FI02112
v STORIOA
design limits.
v SASCABL
Failing Item:
v SIP3143
57CC3401
57CC4030
Failing Item:
v SASEXP
v DEVBPLN
Failing Item:
57CC3405 v SIP3144

initialization for a removable media device. This SRC is 57CC4040
Failing Item:
problems.
v Check the device firmware level and apply the latest 57CC4041
PTFs.

57CC4050 • 57CC8009

v SIP3146
57CC4150
57CC4050 Explanation: I/O adapter detected PCI bus error.
Explanation: Enclosure does not support required Response: If this event appears in a serviceable event
multipath function. view, work with the failing item list found there. If this
v SIP3148
Failing Item:
57CC4060 v BACKPLN
v STORIOA
57CC4160
failed.
Failing Item:
PCI bus error.
v SIP3153
v SASCABL
Explanation: Multipath redundancy level increased. v BACKPLN
Response: A redundant disk unit connection has been v STORIOA
57CC70DD
57CC4070 Explanation: Disrupt device command completed
Explanation: System log entry only. No service action successfully.
required.
57CC8008
57CC4100 Explanation: A permanent failure has occurred in the
Explanation: Device bus fabric error. cache battery pack or capacitive cache power card.
Failing Item: Response: Under a certain configuration, this SRC

v SIP3152 action. Depending on the configuration of the system,
v SASCABL the Storage IOA may have been altered and/or the
v SASEXP Storage IOA Cache may have been disabled to allow
v DEVBPLN
v FI01105
Failing Item:
v CACHBAT
57CC4101
v STORIOA
Failing Item:
v SIP3152 57CC8009
57CC4110 pack or capacitive cache power card.
Explanation: Unsupported enclosure function Failing Item:
detected. v CACHBAT
Failing Item:

57CC8100 • 57CC8157
57CC8100 57CC8150
Explanation: Licensed Internal Code error. Explanation: A permanent failure occurred.
Failing Item: Response: Under a certain configuration, this SRC
v PTFSRCH may not represent an error that requires a service
v STORIOA
57CC8130 attachment of OEM Storage that emulates a Load
Explanation: IOA detected recoverable device bus each time the IOA is IPLed and it can be ignored.
error.
Failing Item:
event does not appear in a serviceable event view, no v ANYBRDG
v SIP3150 Explanation: Licensed Internal Code error.
Failing Item:
57CC8140
v PTFSRCH
error.
Response: If this event appears in a serviceable event 57CC8155
event does not appear in a serviceable event view, no Explanation: A permanent failure occurred.
v SIP3150 v STORIOA
57CC8141 57CC8156
Explanation: IOA detected recoverable device error. Explanation: A permanent failure occurred.
v STORIOA
57CC8145
Explanation: Disk device detected recoverable error. 57CC8157
Response: This error is logged against the storage Explanation: I/O adapter card error. The actions and
controller resource. Contact your next level of support Failing Item list in the Service Action Log will vary
to determine the part number and location code of the based on the conditions this event was logged for.
device.
Failing Item: vary based on the conditions this event was logged for.
v NEXTLVL Perform the following:
57CC8146 2. If the Failing Item indicates SVCDOCS, then
Explanation: Disk device detected recoverable error. step. Do NOT replace the I/O adapter. This is a
v FI01105 v LIC will automatically re-IPL the virtual I/O


57CC8300 • 57CC9000
Failing Item:
recoverable error.
v STORIOA
v If the virtual I/O processor or adapter are not 57CC8301
ends the procedure.
v STORIOA
I/O adapter. 57CC8302

Failing Item:
57CC8300 v SVCDOCS
1. Examine the location code of the adapter to 57CC8400
unit logged reference code xxxx8300 as a serviceable 57CC8404
next step. Otherwise this ends the procedure. Explanation: System log entry only. No service action
required.
while working on the unit or while working on the 57CC9000
working on the connection to the unit, go to step 5. Failing Item:
4. Search for problems logged at about the same time v FI01105

57CC9001 • 57CC9028
v STORIOA v SIP3111
57CC9001 57CC9023
Explanation: Device configuration error. Explanation: One or more array members not in
Failing Item:
v SIP3112
57CC9002
57CC9024
Failing Item:
with another array.
v NEXTLVL
Failing Item:
v NEXTLVL
57CC9008
57CC9025
Failing Item:
v SIP3130 Response: An incompatible device is at the physical
exposed.
57CC9010
Failing Item:
v SIP3110
v FI02112
Failing Item:
v SIP3120
57CC9026
57CC9011
location.
those attached.
Failing Item:
Failing Item:
v NEXTLVL
v NEXTLVL
57CC9020
57CC9027
synchronization.
Failing Item:
Failing Item:
57CC9021
v SIP3113
57CC9028
Failing Item:
57CC9022 adapter. Either move all the devices in an array to
Explanation: Two or more disk units missing from another I/O adapter that supports arrays, or stop an
RAID-5 or RAID-6 array. array on this I/O adapter.

57CC9029 • 57CC9071
v SVCDOCS
57CC9042
57CC9029
on disk unit.
the problem.
Failing Item:
v NEXTLVL
57CC9050
57CC9030
Explanation: Array no longer protected due to more disk units.
Failing Item:
v SIP3110
v FI02112 57CC9051
57CC9031 missing or failed devices.
Explanation: Automatic rebuild initiated for array. Failing Item:
Response: Either a previous rebuild was interrupted v SIP3132
57CC9052
modified devices.
57CC9032
Response: The array is still protected, but the disk v NEXTLVL
v SIP3110 Explanation: IOA resources not available due to
v FI02112 previous problems.
Failing Item:
57CC9040 v SIP3121
initiated. 57CC9055
Response: No action required. Explanation: Write cache data is available for attached
storage IOA.
57CC9041 Response: No service action required.
and corrected errors. 57CC9070
Response: Call your next level of support to report Explanation: System log entry only. No service action
the problem. required.
Failing Item:
v NEXTLVL 57CC9071
IOA is operational.

57CC9072 • 57CC9500
57CC9072 57CC9083
IOA is non-operational. required.
57CC9084
57CC9073 Explanation: System log entry only. No service action
required.
57CC9090
Failing Item:
v SIP3140 Explanation: Disk unit has been modified after the
last known status.
57CC9074 Response: Use Hardware Service Manager to re-IPL

Explanation: Multiple I/O adapters connected in a not I/O adapter. Other resources attached to the virtual
valid configuration. I/O processor may then need to be Varied On.
Response: Multiple I/O adapters not capable of If any reference codes are surfaced, use the new
similar functions or controlling the same set of devices. reference code to resolve the problem.
Failing Item: If you cannot resolve the problem, contact your next
v SIP3141 level of support.
Failing Item:
57CC9075 v SVCDOCS
between IOA and remote IOA. 57CC9091
v SIP3149 detected.
57CC9076 the virtual I/O processor that is associated with this
Explanation: Missing auxiliary IOA or remote IOA. I/O processor may then need to be Varied On.
Failing Item: If any reference codes are surfaced, use the new
v SIP3147 reference code to resolve the problem.
57CC9081 level of support.
v FI01105
v STORIOA 57CC9092
57CC9082 use.

v SIP3134
Failing Item:
v FI01105
57CC9500
v STORIOA
Failing Item:
v PTFSRCH

57CC9903 • 57CD3002

57CC9903
assistance.
Failing Item:
v PTFSRCH
57CCC000
57CCFF3D
required. Explanation: I/O adapter detected a recoverable error.

is logged for information only. v STORIOA
v ANYBRDG
57CCC402
(57CD) Reference codes

57CD1310
supply 2.
Failing Item:
Response: The I/O adapter error log is being filled v DISKPWR
v DEVBPLN
them. v SASEXP
57CD1511 57CD1525
Explanation: A non-fatal error occurred on power Explanation: A fatal error occurred on power supply
supply 1. 2.
Failing Item: Problem determination: This SRC can be the result of

v DISKPWR
v DEVBPLN that detected the problem are in the FRU list of the
v SASEXP serviceable event. Before starting a repair action for this
57CD1515
Explanation: A fatal error occurred on power supply the same time then no service is required and this
1. problem can be closed.

a loss of utility power, battery back up or UPS power v DISKPWR
v DEVBPLN
serviceable event. Before starting a repair action for this v SASEXP
unit was not interrupted at the time the SRC was 57CD3000
the same time then no service is required and this Explanation: A permanent failure occurred.
problem can be closed. Failing Item:
v DISKPWR v ANYBRDG
v DEVBPLN
v SASEXP 57CD3002
57CD1521 respond to selection.

57CD3020 • 57CD4010

57CD3400
unit at about the same time suspect an input power Explanation: Unknown resource error.
Failing Item:
input power to the expansion unit failed the expansion v SIP3150
unit was not able to log a reference code for the input v FI02112
power failure. Restore power to the expansion unit and v STORIOA
xxxx3002 reference codes. v SASCABL
Failing Item:
57CD3401
v SASEXP
v SASCABL Explanation: Device backplane problem.
v DEVBPLN v SASEXP
v DEVBPLN
57CD3020
Explanation: Storage subsystem configuration error. 57CD3405

v SIP3150 logged when an error occurs and the removable media
57CD3100 model.
Explanation: Device bus interface error occurred. Response: Perform the following:
Failing Item:
v SIP3150 problems.
57CD3109 PTFs.
Explanation: I/O adapter timed out a device v Check for LIC logs with major code 2E00. Contact
backplane command. your next level of support with the information you
have gathered.
Failing Item:
v SASEXP
v SASCABL contact your service provider.
v STORIOA
Failing Item:
v DEVBPLN
v PTFSRCH
57CD3140
57CD34FF
required.
57CD3202
57CD3601
required.
Failing Item:
v SVCDOCS 57CD4010
enclosures.

57CD4020 • 57CD4160
Failing Item:
57CD4061
v SIP3142
57CD4020 Response: A redundant disk unit connection has been

Response: Number of connections exceed I/O adapter 57CD4070
design limits.
v SIP3143
57CD4100
57CD4030
Failing Item:
Response: Incorrect multipath connection. v SIP3152
v SIP3144 v SASEXP
v DEVBPLN
57CD4040 v STORIOA

I/O adapter and enclosure. 57CD4101

v SIP3152
57CD4041
Explanation: Incomplete multipath connection. 57CD4110


v SIP3146 v SIP3145
57CD4050 57CD4150
multipath function. Response: If this event appears in a serviceable event
v SIP3148 service action is required.
Failing Item:
57CD4060
v BACKPLN
Explanation: Multipath redundancy level reduced. v STORIOA
failed. 57CD4160
Failing Item: Explanation: I/O adapter detected and recovered a

57CD70DD • 57CD8155
Failing Item:
57CD8141
v BACKPLN
v STORIOA
57CD70DD
57CD8145
successfully.
57CD7614 Response: This error is logged against the storage
Failing Item: device.
v DISKFAN Failing Item:
v NEXTLVL
57CD7624
Explanation: A fatal error occurred on fan 2. 57CD8146
v DISKFAN Failing Item:
v FI01105
57CD8100
Explanation: Licensed Internal Code error. 57CD8150
Failing Item: Explanation: A permanent failure occurred.

v PTFSRCH Response: Under a certain configuration, this SRC
v STORIOA may not represent an error that requires a service
57CD8130 Storage IOA Cache may have been disabled to allow
Explanation: IOA detected recoverable device bus attachment of OEM Storage that emulates a Load
error. Source drive. If this is the case, this error will be posted
Failing Item:
v SIP3150 57CD8151
57CD8140
Failing Item:
error.
v STORIOA
event does not appear in a serviceable event view, no 57CD8155
v SIP3150 v PTFSRCH
v STORIOA

57CD8156 • 57CD8301
Failing Item:
57CD8156
v SVCDOCS
v STORIOA
Failing Item:
v PTFSRCH 57CD8300
v STORIOA
57CD8157
this procedure.
ends the procedure.
operational status.
v PTFSRCH
operational then use Hardware Service Manager 57CD8301
Failing Item:
I/O adapter.

57CD8302 • 57CD9025
57CD8302 57CD9011
those attached.
v SVCDOCS
v STORIOA 57CD9020
57CD8400 RAID-5 or RAID-6 array.

v SIP3111
Failing Item:
v PTFSRCH
57CD9021
57CD8404 Explanation: Two or more disk units missing from

v SIP3111
57CD9000
57CD9022
Failing Item:
v FI01105
Failing Item:
v STORIOA
v SIP3111
57CD9001
57CD9023
v NEXTLVL
Failing Item:
v SIP3112
57CD9002
Explanation: Device error. 57CD9024
Failing Item:
57CD9008 v NEXTLVL
expected by devices. 57CD9025
v SIP3130
57CD9010 exposed.

v SIP3120

57CD9026 • 57CD9052
57CD9026 57CD9032
location. failed.
v NEXTLVL v SIP3110
v FI02112
57CD9027
Explanation: Array not functional due to parity out of 57CD9040
Failing Item:
v SIP3113 57CD9041
57CD9028 and corrected errors.
57CD9042
Failing Item:
v SVCDOCS
on disk unit.
57CD9029
the problem.
Failing Item:
v NEXTLVL
Failing Item: 57CD9050
v NEXTLVL
more disk units.
57CD9030
Failing Item:
v SIP3110
Failing Item:
57CD9031
v SIP3132
Response: Either a previous rebuild was interrupted 57CD9052
modified devices.

57CD9054 • 57CD9091
Failing Item:
57CD9076
v NEXTLVL
57CD9054 Failing Item:

v SIP3147
previous problems.
57CD9081
Failing Item:
Failing Item:
57CD9055 v FI01105
storage IOA.
Response: No service action required. 57CD9082
required. v STORIOA
57CD9071 57CD9083
57CD9084
57CD9072 Explanation: System log entry only. No service action
Response: No service action required. 57CD9090
57CD9073 last known status.
v SIP3140
57CD9074
Failing Item:
v SIP3141
detected.
57CD9075
Failing Item:

57CD9092 • 57CE3400
reference code to resolve the problem. Response: No action is required. This reference code
level of support.
57CDC402
Failing Item:
v SVCDOCS Explanation: Licensed Internal Code error.
57CD9092 assistance.
Explanation: Disk unit requires initialization before Failing Item:

use. v PTFSRCH
Failing Item:
v SIP3134 57CDFF3D
Explanation: Internal program error in driver code. v STORIOA
v PTFSRCH
57CDFFF4
57CD9903 Explanation: Device backplane problem.
Explanation: Tape device information was logged. Failing Item:
Informational event, no service required. v SASEXP
v SASCABL
57CDC000 v STORIOA
Explanation: System log entry only. No service action v DEVBPLN
required.
(57CE) Reference codes

Failing Item:
57CE1310
v SIP3150
Response: The I/O adapter error log is being filled 57CE3140
Check other errors reported to the system and correct Explanation: System log entry only. No service action
them. required.
57CE3000 57CE3202
Explanation: A permanent failure occurred. Explanation: Storage subsystem configuration error.
Failing Item: Response: The device is not supported in the current

v STORIOA
v SVCDOCS
57CE3020
57CE3400
Failing Item:
v SIP3150
57CE3100 v FI02112
v STORIOA

57CE3401 • 57CE4060
v SASCABL
57CE4020
57CE3401
design limits.
Failing Item:
Failing Item:
v SASEXP
v SIP3143
v DEVBPLN
57CE4030
57CE3405
initialization for a removable media device. This SRC is Response: Incorrect multipath connection.
logged when an error occurs and the removable media Failing Item:
v SIP3144
model.
57CE4040
indicate interface problems and work those Explanation: Configuration error.
problems. Response: Incomplete multipath connection between
v Check the device firmware level and apply the latest I/O adapter and enclosure.
PTFs.
Failing Item:
your next level of support with the information you v SIP3144
have gathered.
Problem determination: IPL the IOP to retry the 57CE4041
device identification process. If the error persists then Explanation: Incomplete multipath connection.
Failing Item: device backplane and device.
v PTFSRCH
Failing Item:
v SIP3146
57CE34FF
Explanation: Format in progress. 57CE4050
Response: No action required. This reference code is Explanation: Enclosure does not support required
logged for information only. multipath function.
Failing Item:
57CE3601
v SIP3148
required.
57CE4060
57CE4010
failed.
Failing Item:
enclosures.
v SIP3153
Failing Item:
v SASCABL
v SIP3142
v SASEXP

57CE4061 • 57CE4160
v SIP3145
57CE4061
57CE4120
Failing Item:
57CE4070 v SASCABL

required. 57CE4121
57CE4080 Failing Item:
Explanation: Storage controller thermal error. The v SASCABL
controller exceeded the maximum operating
temperature.
57CE4123
controller is placed in a valid location for this type of Explanation: Configuration error, invalid cable Vital
controller and enclosure. Perform the procedure listed Product Data. The storage controller detected invalid
in the failing items to determine the problem and VPD on the SAS cable. This is most likely caused by a
corrective action. non IBM cable or a wrap plug. The system will
continue to run.
Failing Item:
v SIP3295 been removed and the cable is an IBM part. If the
Explanation: Storage controller detected error. Contact v SASCABL
57CE4150
Failing Item:
v NEXTLVL
57CE4100 event does not appear in a serviceable event view, no
Explanation: Device bus fabric error. service action is required.

v SIP3152 v BACKPLN
v SASCABL v STORIOA
v SASEXP
v DEVBPLN 57CE4160
v STORIOA Explanation: I/O adapter detected and recovered a
v FI01105 PCI bus error.
57CE4101 view, work with the failing item list found there. If this
Explanation: Temporary device bus fabric error. service action is required.
v SIP3152 v BACKPLN
v STORIOA
57CE4110
detected.
Failing Item:

57CE70DD • 57CE8157
57CE70DD 57CE8146
Explanation: Disrupt device command completed Explanation: Disk device detected recoverable error.
successfully.
Failing Item:
v FI01105
57CE8100
Explanation: Licensed Internal Code error. 57CE8150
Failing Item: Explanation: A permanent failure occurred.
v PTFSRCH
Failing Item:
v STORIOA
v STORIOA
v ANYBRDG
57CE8130
Explanation: IOA detected recoverable device bus 57CE8151
error.
event does not appear in a serviceable event view, no v PTFSRCH
Failing Item:
v SIP3150 57CE8155
57CE8140
Failing Item:
error.
v STORIOA
event does not appear in a serviceable event view, no 57CE8156
v SIP3150 v PTFSRCH
v STORIOA
57CE8141
Explanation: IOA detected recoverable device error. 57CE8157
Response: No action is required. This reference code Explanation: I/O adapter card error. The actions and
is logged for information only. Failing Item list in the Service Action Log will vary
57CE8145 Response: The FRU list in the Service Action Log will
Explanation: Disk device detected recoverable error. Perform the following:
Response: This error is logged against the storage 1. Display the Service Action Log entry for this SRC.
controller resource. Contact your next level of support 2. If the Failing Item indicates SVCDOCS, then
to determine the part number and location code of the continue with this step. Otherwise go to the next
device. step. Do NOT replace the I/O adapter. This is a
v NEXTLVL v LIC will automatically re-IPL the virtual I/O

57CE8300 • 57CE9000
to manually re-IPL the virtual I/O processor and unit to the system unit including the cable(s). Work
Vary On attached resources. those problems first, then return to the next step in
v If manually reIPL-ing the virtual I/O processor this procedure.
fails then contact your next level of support. This 5. Use Hardware Service Manager (HSM) to verify
ends the procedure. that the adapters have returned to operational
3. If the Failing Item indicates an I/O adapter, then status. Close reference code xxxx8300 problems for
replace the I/O adapter. Check the list below to adapters that have returned to operational status.
determine if the adapter type you are replacing has Expansion units attached to system units using
multiple physical parts. Light Path service indicators may have activated the
Problem determination: Perform the following: Service Action Log (SAL) to turn off the FRU fault
1. Display the Service Action Log entry for this SRC. indicators for adapters that have returned to
2. If the Failing Item indicates SVCDOCS, then operational status.
continue with this step. Otherwise go to the next 6. Work reference code xxxx8300 problems for any
step. Do NOT replace the I/O adapter. This is a adapters that have not returned to operational
recoverable error. status. This ends the procedure.
v LIC will automatically re-IPL the virtual I/O Failing Item:
v STORIOA
may need to be Varied On. v ANYBRDG
v If the virtual I/O processor or adapter are not v PTFSRCH
to manually re-IPL the virtual I/O processor and 57CE8301
Code.
contact your next level of support to replace the v STORIOA
I/O adapter.
Failing Item: 57CE8302
v SVCDOCS
v STORIOA
57CE8300
Failing Item:
v SVCDOCS
Problem determination: Perform the following: v STORIOA
expansion unit. If the adapter is in an expansion 57CE8400
ends the procedure.
Failing Item:
next step. Otherwise this ends the procedure. 57CE8404
required.
problems were created while working on the unit or 57CE9000
v FI01105

57CE9001 • 57CE9029
v STORIOA v SIP3112
57CE9001 57CE9024
Explanation: Device configuration error. Explanation: Array member physical location conflicts
with another array.
Failing Item:
v NEXTLVL
57CE9002
57CE9025
Failing Item:
v NEXTLVL Response: An incompatible device is at the physical
exposed.
57CE9008
Failing Item:
v SIP3110
v FI02112
Failing Item:
v SIP3130
57CE9026
57CE9011
location.
those attached.
Failing Item:
Failing Item:
v NEXTLVL
v NEXTLVL
57CE9020
57CE9027
synchronization.
Failing Item:
Failing Item:
57CE9021
v SIP3113
57CE9028
Failing Item:
57CE9022 adapter. Either move all the devices in an array to
Explanation: Two or more disk units missing from another I/O adapter that supports arrays, or stop an
RAID-5 or RAID-6 array. array on this I/O adapter.
v SIP3111 v SVCDOCS
57CE9023 57CE9029

57CE9030 • 57CE9072
Failing Item:
57CE9050
v NEXTLVL
more disk units.
57CE9030
Failing Item:
v SIP3131
Failing Item:
57CE9051
v SIP3110
v FI02112
Failing Item:
57CE9031
v SIP3132
Response: Either a previous rebuild was interrupted 57CE9052
unit was used to automatically rebuild the array. Look Explanation: Cache data exists for one or more
for other reference codes and take action on them. modified devices.
Explanation: A disk unit in an array is missing or v NEXTLVL
failed.
Response: The array is still protected, but the disk 57CE9054
Failing Item: previous problems.
v FI02112 v SIP3121
57CE9040 57CE9055
57CE9041 57CE9070
the problem. 57CE9071
57CE9042
Explanation: Background parity check corrected errors 57CE9072
on disk unit.
the problem.
Failing Item:
v NEXTLVL

57CE9073 • 57CEC000
57CE9073 57CE9090
57CE9074
Failing Item:
Failing Item:
v SVCDOCS
v SIP3141
57CE9091
57CE9075
57CE9076 If any reference codes are surfaced, use the new

v SIP3147
Failing Item:
v SVCDOCS
57CE9081
Explanation: Device error. 57CE9092
v FI01105 use.
v SIP3134
57CE9082
Explanation: Device error. 57CE9500
Failing Item: Explanation: Internal program error in driver code.
v STORIOA v PTFSRCH
57CE9083 57CE9903
57CE9084 57CEC000
required. required.

57CEC402 • 57CF3400
57CEC402 57CEFF3D
Explanation: Licensed Internal Code error. Explanation: I/O adapter detected a recoverable error.
Response: Ask your next level of support for Failing Item:
assistance. v STORIOA
v PTFSRCH
(57CF) Reference codes

57CF1310
backplane.
Explanation: The I/O adapter resource not available. v The dual battery charger and carrier card. To
Response: The I/O adapter error log is being filled determine which battery is connected to which
faster than the errors are being reported to the system. embedded IOA use the bus number of the IOA with
Check other errors reported to the system and correct symbolic FRU CACHBAT.
them. v See symbolic FRU FEATCRD for the location code of
57CF3000
Failing Item:
Response: If you are working with one of the card v STORIOA
v ANYBRDG
57CF3020
embedded IOA) read the following: When working the Explanation: Storage subsystem configuration error.
Failing Item:
STORIOA) has three physical parts: v SIP4050
backplane. 57CF3100
v The RAID enablement card. Explanation: Device bus interface error occurred.
Failing Item:
of the FRUs if they are not listed in the serviceable v SIP4050
57CF3140
card for embedded IOA) read the following: When Explanation: System log entry only. No service action
working the FRUs from the serviceable event or the required.
(failing item STORIOA) has two physical parts: 57CF3202
backplane.
v The Battery charger and carrier card. Response: The device is not supported in the current
of the FRUs if they are not listed in the serviceable Failing Item:
event or if you are working the failing item list here. v SVCDOCS

with 2BC2 dual battery charger and carrier card for the 57CF3400
embedded IOAs) read the following: When working Explanation: Unknown resource error.
list here, the embedded storage adapter (failing item Response: If you are working with one of the card
STORIOA) has two physical parts: types below, the adapter has multiple physical parts.

57CF3401 • 57CF4040
Choose the card type to identify the physical parts of v Check for LIC logs with major code 2E00. Contact
the storage adapter. your next level of support with the information you
have gathered.
card). When working the FRUs from the serviceable Problem determination: IPL the IOP to retry the
event or the failing item list here, the embedded device identification process. If the error persists then
storage adapter (failing item STORIOA) has two contact your service provider.
physical parts:
Failing Item:
v PTFSRCH
backplane.
57CF34FF
of the FRUs if they are not listed in the serviceable Explanation: Format in progress.
working the FRUs from the serviceable event or the 57CF3601
(failing item STORIOA) has two physical parts: Explanation: System log entry only. No service action
required.
backplane.
v The dual battery charger and carrier card. To 57CF4010
determine which battery is connected to which Explanation: Configuration error.
symbolic FRU CACHBAT. Response: Incorrect connection between cascaded
enclosures.
listed in the serviceable event or if you are working v SIP3142
Failing Item: 57CF4020
v SIP4050
v FI02112
v STORIOA
design limits.
v SASCABL
Failing Item:
v SIP3143
57CF3401
57CF4030
Failing Item:
v SASEXP
v DEVBPLN
Failing Item:
57CF3405 v SIP4044

initialization for a removable media device. This SRC is 57CF4040
v Check the Product Activity Log for other entries that Failing Item:
problems.
PTFs.

57CF4041 • 57CF4150

57CF4041
Explanation: Incomplete multipath connection. embedded IOAs) read the following: When working
Failing Item: v The embedded storage adapter on the DASD
v SIP3146 backplane.
57CF4050 determine which battery is connected to which
Explanation: Enclosure does not support required symbolic FRU CACHBAT.
multipath function. v See symbolic FRU FEATCRD for the location code of
v SIP3148
Failing Item:
57CF4060
v SIP4052
v SASCABL
Response: A redundant disk unit connection has v SASEXP
failed.
v DEVBPLN
v SIP4053 v FI01105
v SASCABL
v SASEXP 57CF4101
57CF4061
Failing Item:
v SIP4052
57CF4110
57CF4070
detected.
Failing Item:
required.
v SIP3145
57CF4100
57CF4150
types below, the adapter has multiple physical parts. Response: If this event appears in a serviceable event
Choose the card type to identify the physical parts of view, work with the failing item list found there. If this
the storage adapter. event does not appear in a serviceable event view, no
card for embedded IOA) read the following: When If you are working with one of the card types below,
working the FRUs from the serviceable event or the the adapter has multiple physical parts. Choose the
failing item list here, the embedded storage adapter card type to identify the physical parts of the storage
(failing item STORIOA) has two physical parts: adapter.
v The embedded storage adapter on the I/O Card type 2BE1 (feature RAID enablement card for
backplane. embedded IOA) read the following: When working the
v The Battery charger and carrier card. FRUs from the serviceable event or the failing item list

57CF4160 • 57CF8008
v The embedded storage adapter on the I/O STORIOA) has three physical parts:
v The RAID enablement card. backplane.
v The Battery charger and carrier card. v The RAID enablement card.
v See symbolic FRU FEATCRD for the location codes v The Battery charger and carrier card.
of the FRUs if they are not listed in the serviceable v See symbolic FRU FEATCRD for the location codes
event or if you are working the failing item list here. of the FRUs if they are not listed in the serviceable
card for embedded IOA) read the following: When Card type 57CB (embedded IOA with 2BCF battery
working the FRUs from the serviceable event or the card for embedded IOA) read the following: When
failing item list here, the embedded storage adapter working the FRUs from the serviceable event or the
(failing item STORIOA) has two physical parts: failing item list here, the embedded storage adapter
v The embedded storage adapter on the I/O (failing item STORIOA) has two physical parts:
v The Battery charger and carrier card. backplane.
v See symbolic FRU FEATCRD for the location codes v The Battery charger and carrier card.
of the FRUs if they are not listed in the serviceable v See symbolic FRU FEATCRD for the location codes
event or if you are working the failing item list here. of the FRUs if they are not listed in the serviceable
with 2BC2 dual battery charger and carrier card for the Card type 57CF (embedded IOAs on DASD backplane
embedded IOAs) read the following: When working with 2BC2 dual battery charger and carrier card for the
the FRUs from the serviceable event or the failing item embedded IOAs) read the following: When working
list here, the embedded storage adapter (failing item the FRUs from the serviceable event or the failing item
STORIOA) has two physical parts: list here, the embedded storage adapter (failing item
v The embedded storage adapter on the DASD STORIOA) has two physical parts:
backplane. v The embedded storage adapter on the DASD
v The dual battery charger and carrier card. To backplane.
determine which battery is connected to which v The dual battery charger and carrier card. To
embedded IOA use the bus number of the IOA with determine which battery is connected to which
symbolic FRU CACHBAT. embedded IOA use the bus number of the IOA with
v See symbolic FRU FEATCRD for the location code of symbolic FRU CACHBAT.
the dual battery charger and carrier card if it is not v See symbolic FRU FEATCRD for the location code of
listed in the serviceable event or if you are working the dual battery charger and carrier card if it is not
the failing item list here. listed in the serviceable event or if you are working
Failing Item: the failing item list here.
v STORIOA v BACKPLN
v STORIOA
57CF4160
Explanation: I/O adapter detected and recovered a 57CF70DD
PCI bus error. Explanation: Disrupt device command completed
Response: If this event appears in a serviceable event successfully.
event does not appear in a serviceable event view, no 57CF8008
If you are working with one of the card types below, cache battery pack or capacitive cache power card.
card type to identify the physical parts of the storage Response: Under a certain configuration, this SRC
adapter. may not represent an error that requires a service
Card type 2BE1 (feature RAID enablement card for the Storage IOA may have been altered and/or the
embedded IOA) read the following: When working the Storage IOA Cache may have been disabled to allow
FRUs from the serviceable event or the failing item list attachment of OEM Storage that emulates a Load

57CF8009 • 57CF8100

57CF8009
card type to identify the physical parts of the storage Failing Item:
adapter. v CACHBAT
embedded IOA) read the following: When working the 57CF8100
here, the embedded storage adapter (failing item Explanation: Licensed Internal Code error.
STORIOA) has three physical parts: Response: If you are working with one of the card
v The embedded storage adapter on the I/O types below, the adapter has multiple physical parts.
backplane. Choose the card type to identify the physical parts of
v The RAID enablement card. the storage adapter.
v The Battery charger and carrier card. Card type 2BE1 (feature RAID enablement card for
Card type 57CB (embedded IOA with 2BCF battery v The embedded storage adapter on the I/O
card) read the following: When working the FRUs from backplane.
the serviceable event or the failing item list here, the v The RAID enablement card.
two physical parts:
backplane.
Card type 57CF (embedded IOAs on DASD backplane (failing item STORIOA) has two physical parts:
with 2BC2 dual battery charger and carrier card) read v The embedded storage adapter on the I/O
the following: When working the FRUs from the backplane.
serviceable event or the failing item list here, the
two physical parts: v See symbolic FRU FEATCRD for the location codes
backplane.
v The dual battery charger and carrier card. To Card type 57CF (embedded IOAs on DASD backplane
determine which battery is connected to which with 2BC2 dual battery charger and carrier card for the
embedded IOA use the bus number of the IOA with embedded IOAs) read the following: When working
symbolic FRU CACHBAT. the FRUs from the serviceable event or the failing item
v See symbolic FRU FEATCRD for the location code of list here, the embedded storage adapter (failing item
the dual battery charger and carrier card if it is not STORIOA) has two physical parts:
listed in the serviceable event or if you are working v The embedded storage adapter on the DASD
the failing item list here. backplane.
Failing Item: v The dual battery charger and carrier card. To
v CACHBAT determine which battery is connected to which
v STORIOA
v FEATCRD
Failing Item:

57CF8130 • 57CF8150
v PTFSRCH Storage IOA Cache may have been disabled to allow

v STORIOA attachment of OEM Storage that emulates a Load
57CF8130
Explanation: IOA detected recoverable device bus the adapter has multiple physical parts. Choose the
error. card type to identify the physical parts of the storage
Response: If this event appears in a serviceable event adapter.
view, work with the failing item list found there. If this Card type 2BE1 (feature RAID enablement card for
event does not appear in a serviceable event view, no embedded IOA) read the following: When working the
service action is required. FRUs from the serviceable event or the failing item list
Failing Item: here, the embedded storage adapter (failing item
v SIP4050
backplane.
57CF8140 v The RAID enablement card.
Explanation: IOA detected recoverable device bus v The Battery charger and carrier card.
error. v See symbolic FRU FEATCRD for the location codes
Response: If this event appears in a serviceable event of the FRUs if they are not listed in the serviceable
view, work with the failing item list found there. If this event or if you are working the failing item list here.
service action is required. Card type 57CB (embedded IOA with 2BCF battery
Failing Item: working the FRUs from the serviceable event or the
v SIP4050 failing item list here, the embedded storage adapter
57CF8141 v The embedded storage adapter on the I/O
backplane.
Response: No action is required. This reference code v See symbolic FRU FEATCRD for the location codes
is logged for information only. of the FRUs if they are not listed in the serviceable
57CF8145
Explanation: Disk device detected recoverable error. with 2BC2 dual battery charger and carrier card for the
Response: This error is logged against the storage embedded IOAs) read the following: When working
controller resource. Contact your next level of support the FRUs from the serviceable event or the failing item
to determine the part number and location code of the list here, the embedded storage adapter (failing item
device. STORIOA) has two physical parts:
Failing Item:
backplane.
v NEXTLVL
57CF8146 embedded IOA use the bus number of the IOA with
v FI01105 listed in the serviceable event or if you are working
57CF8150 Failing Item:

v STORIOA
v ANYBRDG

57CF8151 • 57CF8155
57CF8151 57CF8155
Explanation: Licensed Internal Code error. Explanation: A permanent failure occurred.
Response: If you are working with one of the card Response: If you are working with one of the card
types below, the adapter has multiple physical parts. types below, the adapter has multiple physical parts.
Choose the card type to identify the physical parts of Choose the card type to identify the physical parts of
the storage adapter. the storage adapter.
Card type 2BE1 (feature RAID enablement card for Card type 2BE1 (feature RAID enablement card for
embedded IOA) read the following: When working the embedded IOA) read the following: When working the
FRUs from the serviceable event or the failing item list FRUs from the serviceable event or the failing item list
here, the embedded storage adapter (failing item here, the embedded storage adapter (failing item
STORIOA) has three physical parts: STORIOA) has three physical parts:
v The embedded storage adapter on the I/O v The embedded storage adapter on the I/O
v The RAID enablement card. v The RAID enablement card.
v The Battery charger and carrier card. v The Battery charger and carrier card.
Card type 57CB (embedded IOA with 2BCF battery Card type 57CB (embedded IOA with 2BCF battery
card for embedded IOA) read the following: When card for embedded IOA) read the following: When
working the FRUs from the serviceable event or the working the FRUs from the serviceable event or the
failing item list here, the embedded storage adapter failing item list here, the embedded storage adapter
(failing item STORIOA) has two physical parts: (failing item STORIOA) has two physical parts:
v The embedded storage adapter on the I/O v The embedded storage adapter on the I/O
v The Battery charger and carrier card. v The Battery charger and carrier card.
Card type 57CF (embedded IOAs on DASD backplane Card type 57CF (embedded IOAs on DASD backplane
with 2BC2 dual battery charger and carrier card for the with 2BC2 dual battery charger and carrier card for the
embedded IOAs) read the following: When working embedded IOAs) read the following: When working
the FRUs from the serviceable event or the failing item the FRUs from the serviceable event or the failing item
list here, the embedded storage adapter (failing item list here, the embedded storage adapter (failing item
STORIOA) has two physical parts: STORIOA) has two physical parts:
v The embedded storage adapter on the DASD v The embedded storage adapter on the DASD
v The dual battery charger and carrier card. To v The dual battery charger and carrier card. To
determine which battery is connected to which determine which battery is connected to which
embedded IOA use the bus number of the IOA with embedded IOA use the bus number of the IOA with
symbolic FRU CACHBAT. symbolic FRU CACHBAT.
v See symbolic FRU FEATCRD for the location code of v See symbolic FRU FEATCRD for the location code of
the dual battery charger and carrier card if it is not the dual battery charger and carrier card if it is not
listed in the serviceable event or if you are working listed in the serviceable event or if you are working
the failing item list here. the failing item list here.
v PTFSRCH v PTFSRCH
v STORIOA v STORIOA

57CF8156 • 57CF8157
57CF8156 57CF8157
Explanation: A permanent failure occurred. Explanation: I/O adapter card error. The actions and
Choose the card type to identify the physical parts of Response: The FRU list in the Service Action Log will
the storage adapter. vary based on the conditions this event was logged for.
embedded IOA) read the following: When working the 1. Display the Service Action Log entry for this SRC.
FRUs from the serviceable event or the failing item list 2. If the Failing Item indicates SVCDOCS, then
here, the embedded storage adapter (failing item continue with this step. Otherwise go to the next
STORIOA) has three physical parts: step. Do NOT replace the I/O adapter. This is a
v The embedded storage adapter on the I/O recoverable error.
backplane. v LIC will automatically re-IPL the virtual I/O
v The RAID enablement card. processor associated with the adapter. Other
card for embedded IOA) read the following: When v If manually reIPL-ing the virtual I/O processor
working the FRUs from the serviceable event or the fails then contact your next level of support. This
failing item list here, the embedded storage adapter ends the procedure.
(failing item STORIOA) has two physical parts: 3. If the Failing Item indicates an I/O adapter, then
v The embedded storage adapter on the I/O replace the I/O adapter. Check the list below to
backplane. determine if the adapter type you are replacing has
v See symbolic FRU FEATCRD for the location codes If you are replacing the I/O adapter and you are
of the FRUs if they are not listed in the serviceable working with one of the card types below, the adapter
event or if you are working the failing item list here. has multiple physical parts. Choose the card type to
identify the physical parts of the storage adapter.
with 2BC2 dual battery charger and carrier card for the Card type 2BE1 (feature RAID enablement card for
embedded IOAs) read the following: When working embedded IOA) read the following: When working the
the FRUs from the serviceable event or the failing item FRUs from the serviceable event or the failing item list
list here, the embedded storage adapter (failing item here, the embedded storage adapter (failing item
STORIOA) has two physical parts: STORIOA) has three physical parts:
v The embedded storage adapter on the DASD v The embedded storage adapter on the I/O
v The dual battery charger and carrier card. To v The RAID enablement card.
symbolic FRU CACHBAT. v See symbolic FRU FEATCRD for the location codes
Failing Item: working the FRUs from the serviceable event or the
v PTFSRCH failing item list here, the embedded storage adapter
v STORIOA
backplane.

57CF8300 • 57CF8301
v See symbolic FRU FEATCRD for the location codes v The embedded storage adapter on the I/O
of the FRUs if they are not listed in the serviceable backplane.
event or if you are working the failing item list here. v The RAID enablement card.
with 2BC2 dual battery charger and carrier card for the v See symbolic FRU FEATCRD for the location codes
embedded IOAs) read the following: When working of the FRUs if they are not listed in the serviceable
the FRUs from the serviceable event or the failing item event or if you are working the failing item list here.
STORIOA) has two physical parts: Card type 57CB (embedded IOA with 2BCF battery
backplane.
v The dual battery charger and carrier card. To (failing item STORIOA) has two physical parts:
backplane.
the dual battery charger and carrier card if it is not v See symbolic FRU FEATCRD for the location codes
listed in the serviceable event or if you are working of the FRUs if they are not listed in the serviceable
the failing item list here. event or if you are working the failing item list here.
Problem determination: Perform the following: Card type 57CF (embedded IOAs on DASD backplane
1. Display the Service Action Log entry for this SRC. with 2BC2 dual battery charger and carrier card for the
2. If the Failing Item indicates SVCDOCS, then embedded IOAs) read the following: When working
continue with this step. Otherwise go to the next the FRUs from the serviceable event or the failing item
step. Do NOT replace the I/O adapter. This is a list here, the embedded storage adapter (failing item
recoverable error. STORIOA) has two physical parts:
v LIC will automatically re-IPL the virtual I/O v The embedded storage adapter on the DASD
processor associated with the adapter. Other backplane.
resources attached to the virtual I/O processor v The dual battery charger and carrier card. To
may need to be Varied On. determine which battery is connected to which
v If the virtual I/O processor or adapter are not embedded IOA use the bus number of the IOA with
operational then use Hardware Service Manager symbolic FRU CACHBAT.
to manually re-IPL the virtual I/O processor and v See symbolic FRU FEATCRD for the location code of
Vary On attached resources. the dual battery charger and carrier card if it is not
v If manually reIPL-ing the virtual I/O processor listed in the serviceable event or if you are working
fails then contact your next level of support. This the failing item list here.
I/O adapter. v ANYBRDG
v PTFSRCH
Failing Item:
v SVCDOCS
57CF8301
v STORIOA
Code.
57CF8300
Explanation: IOA hardware error or PCI bus error. types below, the adapter has multiple physical parts.
Response: If you are working with one of the card Choose the card type to identify the physical parts of
types below, the adapter has multiple physical parts. the storage adapter.
Choose the card type to identify the physical parts of Card type 2BE1 (feature RAID enablement card for
the storage adapter. embedded IOA) read the following: When working the
Card type 2BE1 (feature RAID enablement card for FRUs from the serviceable event or the failing item list
embedded IOA) read the following: When working the here, the embedded storage adapter (failing item
FRUs from the serviceable event or the failing item list STORIOA) has three physical parts:
here, the embedded storage adapter (failing item v The embedded storage adapter on the I/O
STORIOA) has three physical parts: backplane.

57CF8302 • 57CF9000
v The RAID enablement card. v The Battery charger and carrier card.
Card type 57CB (embedded IOA with 2BCF battery card for embedded IOA) read the following: When
card for embedded IOA) read the following: When working the FRUs from the serviceable event or the
working the FRUs from the serviceable event or the failing item list here, the embedded storage adapter
failing item list here, the embedded storage adapter (failing item STORIOA) has two physical parts:
(failing item STORIOA) has two physical parts: v The embedded storage adapter on the I/O
Card type 57CF (embedded IOAs on DASD backplane with 2BC2 dual battery charger and carrier card for the
with 2BC2 dual battery charger and carrier card for the embedded IOAs) read the following: When working
embedded IOAs) read the following: When working the FRUs from the serviceable event or the failing item
the FRUs from the serviceable event or the failing item list here, the embedded storage adapter (failing item
list here, the embedded storage adapter (failing item STORIOA) has two physical parts:
STORIOA) has two physical parts: v The embedded storage adapter on the DASD
v The embedded storage adapter on the DASD backplane.
backplane. v The dual battery charger and carrier card. To
v The dual battery charger and carrier card. To determine which battery is connected to which
determine which battery is connected to which embedded IOA use the bus number of the IOA with
embedded IOA use the bus number of the IOA with symbolic FRU CACHBAT.
symbolic FRU CACHBAT. v See symbolic FRU FEATCRD for the location code of
v See symbolic FRU FEATCRD for the location code of the dual battery charger and carrier card if it is not
the dual battery charger and carrier card if it is not listed in the serviceable event or if you are working
listed in the serviceable event or if you are working the failing item list here.
the failing item list here. Failing Item:
v PTFSRCH v STORIOA
v STORIOA
57CF8400
57CF8302 Explanation: Licensed Internal Code error.
Explanation: Missing Licensed Internal Code. Failing Item:
Response: Ensure that the code necessary to support v PTFSRCH
If you are working with one of the card types below, 57CF8404
required.
adapter.
57CF9000
FRUs from the serviceable event or the failing item list Explanation: Device error.
STORIOA) has three physical parts: Response: If you are working with one of the card

57CF9001 • 57CF9024

57CF9008
here, the embedded storage adapter (failing item Explanation: I/O card does not support functions
STORIOA) has three physical parts: expected by devices.
v The embedded storage adapter on the I/O Failing Item:
backplane.
v SIP3130
57CF9010
of the FRUs if they are not listed in the serviceable Explanation: Cache data associated with attached
event or if you are working the failing item list here. devices cannot be found.
Failing Item:
v SIP3120
failing item list here, the embedded storage adapter 57CF9011
v The embedded storage adapter on the I/O those attached.
backplane.
v The Battery charger and carrier card. Failing Item:
v See symbolic FRU FEATCRD for the location codes v NEXTLVL
event or if you are working the failing item list here. 57CF9020
Card type 57CF (embedded IOAs on DASD backplane Explanation: Two or more disk units missing from
with 2BC2 dual battery charger and carrier card for the RAID-5 or RAID-6 array.
embedded IOAs) read the following: When working Failing Item:
v SIP3111
v The embedded storage adapter on the DASD 57CF9021
backplane. Explanation: Two or more disk units missing from
v The dual battery charger and carrier card. To RAID-5 or RAID-6 array.
Failing Item:
symbolic FRU CACHBAT. v SIP3111
the dual battery charger and carrier card if it is not 57CF9022
the failing item list here. Explanation: Two or more disk units missing from
Failing Item:
Failing Item:
v FI01105
v SIP3111
v STORIOA
57CF9023
57CF9001
Explanation: Device configuration error. required physical locations.
v NEXTLVL v SIP3112
57CF9002 57CF9024
Explanation: Device error. Explanation: Array member physical location conflicts

57CF9025 • 57CF9042
v NEXTLVL
57CF9030
57CF9025
Failing Item:
Response: An incompatible device is at the physical v SIP3110
v FI02112
exposed.
Failing Item:
57CF9031
v SIP3110
v FI02112
57CF9026
Explanation: Disk unit not found at required physical for other reference codes and take action on them.
location.
Response: A previously exposed disk unit in an array 57CF9032
Failing Item: failed.
v NEXTLVL Response: The array is still protected, but the disk
Explanation: Array not functional due to parity out of v SIP3110
synchronization. v FI02112
parity data is out of synchronization. 57CF9040
Failing Item: Explanation: Re-synchronization of array parity was
v SIP3113 initiated.
57CF9028
Explanation: Maximum number of functional arrays 57CF9041
has been exceeded.
Response: Reduce the number of arrays on this I/O and corrected errors.
the problem.
Failing Item:
Failing Item:
v NEXTLVL
v SVCDOCS
57CF9042
57CF9029
on disk unit.
the problem.
Failing Item:
Failing Item:
v NEXTLVL
v NEXTLVL

57CF9050 • 57CF9081
57CF9050 57CF9073
Explanation: Required cache data not found for one or Explanation: Multiple I/O adapters connected in a not
more disk units. valid configuration.
v SIP3131 v SIP4040
57CF9051 57CF9074
Failing Item:
57CF9052 v SIP4041
modified devices. 57CF9075
Failing Item:
v SIP4049
57CF9054
57CF9076
v SIP3121 v SIP4047
57CF9055 57CF9081
storage IOA.
Response: No service action required. types below, the adapter has multiple physical parts.
57CF9070
required.
57CF9071 STORIOA) has three physical parts:
Explanation: Link from IOA to auxiliary or remote v The embedded storage adapter on the I/O
IOA is operational. backplane.
57CF9072 of the FRUs if they are not listed in the serviceable
Explanation: Link from IOA to auxiliary or remote event or if you are working the failing item list here.
Response: No service action required. card for embedded IOA) read the following: When

57CF9082 • 57CF9091
the FRUs from the serviceable event or the failing item v The embedded storage adapter on the DASD
list here, the embedded storage adapter (failing item backplane.
STORIOA) has two physical parts: v The dual battery charger and carrier card. To
v The embedded storage adapter on the DASD determine which battery is connected to which
determine which battery is connected to which v See symbolic FRU FEATCRD for the location code of
embedded IOA use the bus number of the IOA with the dual battery charger and carrier card if it is not
symbolic FRU CACHBAT. listed in the serviceable event or if you are working
listed in the serviceable event or if you are working v FI01105
v STORIOA
Failing Item:
v FI01105 57CF9083
v STORIOA
required.
57CF9082
Explanation: Device error. 57CF9084
Response: If you are working with one of the card Explanation: System log entry only. No service action
types below, the adapter has multiple physical parts. required.
57CF9090
last known status.
here, the embedded storage adapter (failing item Response: Use Hardware Service Manager to re-IPL
STORIOA) has three physical parts: the virtual I/O processor that is associated with this
v The embedded storage adapter on the I/O I/O adapter. Other resources attached to the virtual
backplane. I/O processor may then need to be Varied On.
v The RAID enablement card. If any reference codes are surfaced, use the new
v The Battery charger and carrier card. reference code to resolve the problem.
v See symbolic FRU FEATCRD for the location codes If you cannot resolve the problem, contact your next
of the FRUs if they are not listed in the serviceable level of support.
Failing Item:
Card type 57CB (embedded IOA with 2BCF battery v SVCDOCS
working the FRUs from the serviceable event or the 57CF9091
(failing item STORIOA) has two physical parts: Explanation: Incorrect hardware configuration change
v The embedded storage adapter on the I/O detected.
backplane. Response: Use Hardware Service Manager to re-IPL
v The Battery charger and carrier card. the virtual I/O processor that is associated with this

57CF9092 • 57D2B940
I/O processor may then need to be Varied On. types below, the adapter has multiple physical parts.
level of support.
Failing Item: here, the embedded storage adapter (failing item
v SVCDOCS STORIOA) has three physical parts:
backplane.
57CF9092
Explanation: Disk unit requires initialization before v The Battery charger and carrier card.
use.
Failing Item: of the FRUs if they are not listed in the serviceable
v SIP3134 event or if you are working the failing item list here.

57CF9500 card for embedded IOA) read the following: When
Explanation: Internal program error in driver code. working the FRUs from the serviceable event or the
Failing Item: (failing item STORIOA) has two physical parts:
v PTFSRCH v The embedded storage adapter on the I/O
backplane.
57CF9903 v The Battery charger and carrier card.
Explanation: Tape device information was logged. v See symbolic FRU FEATCRD for the location codes
Informational event, no service required. of the FRUs if they are not listed in the serviceable
57CFC000 Card type 57CF (embedded IOAs on DASD backplane

Explanation: System log entry only. No service action with 2BC2 dual battery charger and carrier card for the
required. embedded IOAs) read the following: When working
Response: No action is required. This reference code list here, the embedded storage adapter (failing item
is logged for information only. STORIOA) has two physical parts:
57CFC402 backplane.
Explanation: Licensed Internal Code error. v The dual battery charger and carrier card. To
Response: Ask your next level of support for embedded IOA use the bus number of the IOA with
assistance. symbolic FRU CACHBAT.
Failing Item: v See symbolic FRU FEATCRD for the location code of
v PTFSRCH
57CFFF3D
Failing Item:
Explanation: I/O adapter detected a recoverable error. v STORIOA
Response: If you are working with one of the card v ANYBRDG

57D2A001 57D2B940
Explanation: Communications I/O adapter software Explanation: I/O adapter hardware error detected.
Problem determination: View the error details in the
Failing Item: service action log or the product activity log. If the
v NEXTLVL secondary code is 00004009 or 4009, the adapter is in a

57D2B941 • 57D331BX
physical location that does not support the adapter

57D2B941
type. Move the adapter to a physical location that
supports the adapter type. Otherwise, continue with Explanation: One of the ports on the IOA has failed.
the next failing item in the failing item list.
Failing Item:
v FI00719 v AJDGP01
v AJDGP01
v MA_BRDG

Problem determination: USB port numbers start with
57D33000
'1' and are in the hexadecimal range of 1 through F for
Explanation: USB optical device information was each USB port on an adapter.
logged. Informational event, no service required.
For the USB port identified by the last digit of the
URC, there is a problem with the power being drawn
57D33002 by the device. If the device is within operating
specifications it may work properly when plugged into
Explanation: Unexpected USB device disconnect
another USB port or another USB adapter. If the device
detected.
is moved to a different port and this error is logged
Failing Item: against the port where the device is plugged then the
v USB_DEV device may be failing. Try moving the device to a
different adapter.
57D33010 If the device operates properly on another USB port or

on another system then the problem is with the USB
Explanation: USB undefined device response. adapter or the adapter's USB port.
Failing Item: Remove the device on the port given in the location
v USB_DEV code of symbolic FRU "USBPORT" and look for a
xxxx31By SRC to be logged where "xxxx" are the same
characters as the first four characters of this SRC and 'y'
57D33020 is the same as the last character of this SRC.
Explanation: USB configuration error. Too many USB v If the xxxx31By SRC is logged at about the same
devices are plugged. The internal device map is full. time that you removed the device then examine the
location code of symbolic FRU "USBPORT" for the
Problem determination: Remove USB devices one at a
xxxx31By SRC. If the location code for "USBPORT" is
time until the problem is resolved. In the Service Action
the same as the adapter and port location called out
Log (SAL) the location of the device that caused this
by this SRC then the problem at this port has been
error is listed with the FRU.
corrected. The device may be failing. The device may
Failing Item: function properly on another USB port or another
v SVCDOCS system.
v USB_DEV v If the xxxx31By SRC is not logged then work the

failing item list in the serviceable event view or from
the list below.
57D33100
Failing Item:
Explanation: USB device bus error. v SVCDOCS
Failing Item: v USBPORT
v USB_CBL v USB_DEV
v USB_DEV v USB_IOA
v USB_IOA
57D331BX
57D331AX Explanation: USB port over current error removed.
Explanation: USB port over current error detected. Problem determination: An over current condition
The port location is listed in the serviceable event view that previously existed on this port has been resolved.
with the "USBPORT" symbolic FRU. The logical port The port is operating normally. The port location is
number is the last character of the URC.

57D33202 • 57D3FFFE
listed with symbolic FRU "SVCDOCS" in the v USB_IOA

serviceable event view. The logical port number is the
last character of the SRC.
57D38301
Failing Item:
Explanation: USB program error.
v SVCDOCS
Failing Item:
v AJDGP01
57D33202
Explanation: USB optical device information was
57D38303
Explanation: USB port enumerator error.
Explanation: USB unknown device or unexpected v AJDGP01
device removal. If this SRC appears in a serviceable v USB_IOA
event view then it requires service. Otherwise no
service is required.
57D3C000
Problem determination: Did this error occur during
an IPL? Explanation: USB optical device information was
v Yes - The device may have been initializing when an
access occurred. Reset / reload the adapter or retry
the IPL. If the problem persists then the device is 57D3C402
failing.
Explanation: USB optical device LIC information was
v No - The device is unknown or was unexpectedly logged. Informational event, no service required.
removed.
Failing Item: 57D3FF3D
v USB_DEV
Explanation: USB optical device successfully
v USB_CBL recovered from a temporary error. No action is
required. This reference code is logged for information
57D34150 only.
Explanation: USB IOA hard PCI error.

57D3FFF3
Failing Item:
Explanation: USB media format corrupted.
v USB_IOA
v MEDIA
57D38100 v USB_DEV
Explanation: USB IOA manager program error.

57D3FFF4
Failing Item:
Explanation: USB internal device error.
v AJDGP01
Failing Item:
57D38150 v USB_DEV
Explanation: USB hard IOA or device hardware error.

57D3FFFE
Failing Item:
Explanation: USB temporary bus error.
v USB_DEV
v USB_IOA
57D38300
Explanation: USB IOA hardware error, IOA reset
issued.
Failing Item:

57D4A001 • 57D73405

supports the adapter type. Otherwise, continue with
57D4A001
the next failing item in the failing item list.
Failing Item:
v FI00719
Failing Item:
v AJDGP01
v NEXTLVL
v MA_BRDG
57D4B940
57D4B941
Problem determination: View the error details in the
Failing Item:
the product activity log. If the card type is 57D2 and
the secondary code is 00004009 or 4009, the adapter is v FI00719
in a physical location that does not support the adapter v AJDGP01
type. Move the adapter to a physical location that

57D71310
Failing Item:
Response: The I/O adapter error log is being filled v SVCDOCS
them. 57D73400
Explanation: A permanent failure occurred. v SIP3150
v STORIOA v STORIOA
v ANYBRDG v SASCABL
57D73020 57D73401
Explanation: Storage subsystem configuration error. Explanation: Device backplane problem.

v SIP3150 v SASEXP
v DEVBPLN
57D73100
57D73405
Failing Item:
v SIP3150 logged when an error occurs and the removable media
57D73140 model.
Explanation: System log entry only. No service action Response: Perform the following:
required. v Check the Product Activity Log for other entries that
problems.
57D73202
Explanation: Storage subsystem configuration error. PTFs.

57D734FF • 57D74100

57D74041
have gathered. Explanation: Incomplete multipath connection.
Problem determination: IPL the IOP to retry the Response: Incomplete multipath connection between
device identification process. If the error persists then device backplane and device.
Failing Item:
v PTFSRCH
57D74050
57D734FF
Explanation: Format in progress. multipath function.
logged for information only. v SIP3148
57D73601 57D74060
Explanation: System log entry only. No service action Explanation: Multipath redundancy level reduced.
required.
failed.
57D74010
Failing Item:
v SIP3153
Response: Incorrect connection between cascaded v SASCABL
enclosures.
v SASEXP
Failing Item:
v SIP3142 57D74061
57D74020
Explanation: Configuration error. restored. No service action is required.
design limits. 57D74070
v SIP3143 required.
57D74030 57D74080
Explanation: Configuration error. Explanation: Storage controller thermal error. The
controller exceeded the maximum operating
temperature.
Failing Item:
v SIP3144 controller is placed in a valid location for this type of
controller and enclosure. Perform the procedure listed
57D74040 in the failing items to determine the problem and
corrective action.
Failing Item:
Response: Incomplete multipath connection between v SIP3295
v SIP3144
Failing Item:
v SIP3152

57D74101 • 57D78146
v SASCABL
57D78100
v SASEXP
v DEVBPLN
v FI01105 v PTFSRCH
v STORIOA
57D74101
57D78130
Failing Item:
error.
v SIP3152
Explanation: Unsupported enclosure function service action is required.
detected. Failing Item:
v SIP3145
57D78140
57D74150 Explanation: IOA detected recoverable device bus
Explanation: I/O adapter detected PCI bus error. error.

v BACKPLN v SIP3150
v STORIOA
57D78141
57D74160 Explanation: IOA detected recoverable device error.

Explanation: I/O adapter detected and recovered a Response: No action is required. This reference code
PCI bus error. is logged for information only.
view, work with the failing item list found there. If this 57D78145
Failing Item:
v BACKPLN to determine the part number and location code of the
v STORIOA device.
Failing Item:
57D770DD v NEXTLVL
successfully. 57D78146
57D78009
Failing Item:
v FI01105
Failing Item:
v CACHBAT

57D78150 • 57D78300

57D78150
Explanation: A permanent failure occurred. determine if the adapter type you are replacing has
Failing Item:
v STORIOA Problem determination: Perform the following:
v ANYBRDG 1. Display the Service Action Log entry for this SRC.
57D78151
Explanation: Licensed Internal Code error. recoverable error.
Failing Item: v LIC will automatically re-IPL the virtual I/O
v STORIOA may need to be Varied On.
57D78155 operational then use Hardware Service Manager
Explanation: A permanent failure occurred. Vary On attached resources.
Failing Item: v If manually reIPL-ing the virtual I/O processor
v PTFSRCH fails then contact your next level of support. This
ends the procedure.
v STORIOA
57D78156 I/O adapter.
Explanation: A permanent failure occurred. Failing Item:
v PTFSRCH v STORIOA
v STORIOA
57D78300
57D78157 Explanation: IOA hardware error or PCI bus error.
Explanation: I/O adapter card error. The actions and Problem determination: Perform the following:
Response: The FRU list in the Service Action Log will expansion unit. If the adapter is in an expansion
vary based on the conditions this event was logged for. unit, continue with the next step. Otherwise this
Perform the following: ends the procedure.
1. Display the Service Action Log entry for this SRC. 2. If multiple storage adapters in the same expansion
2. If the Failing Item indicates SVCDOCS, then unit logged reference code xxxx8300 as a serviceable
continue with this step. Otherwise go to the next event at about the same time, continue with the
step. Do NOT replace the I/O adapter. This is a next step. Otherwise this ends the procedure.
recoverable error. 3. Suspect a problem with the connection to the
v LIC will automatically re-IPL the virtual I/O enclosure. The problem may have been temporary
processor associated with the adapter. Other while working on the unit or while working on the
resources attached to the virtual I/O processor connection or cable(s) to the unit. If the adapter
may need to be Varied On. problems were created while working on the unit or
operational then use Hardware Service Manager 4. Search for problems logged at about the same time
to manually re-IPL the virtual I/O processor and and call out the FRUs that connect the expansion
Vary On attached resources. unit to the system unit including the cable(s). Work
v If manually reIPL-ing the virtual I/O processor this procedure.
ends the procedure. 5. Use Hardware Service Manager (HSM) to verify

57D78301 • 57D79022

57D79001
FRU fault indicators for those adapters. Use the Explanation: Device configuration error.
Failing Item:
operational status. v NEXTLVL
adapters that have not returned to operational 57D79002
Failing Item:
Failing Item:
v STORIOA
v NEXTLVL
v ANYBRDG
v PTFSRCH
57D79008
57D78301 Explanation: I/O card does not support functions

Code. Failing Item:
v SIP3130
Failing Item:
v PTFSRCH
57D79010
v STORIOA
57D78302
Failing Item:
v SIP3120
57D79011
Failing Item:
v SVCDOCS those attached.
v STORIOA
Failing Item:
v NEXTLVL
57D78400
Explanation: Licensed Internal Code error. 57D79020
Failing Item: Explanation: Two or more disk units missing from
v PTFSRCH RAID-5 or RAID-6 array.
Failing Item:
57D78404 v SIP3111
required. 57D79021
57D79000 RAID-5 or RAID-6 array.
v FI01105
v STORIOA 57D79022
Failing Item:
v SIP3111

57D79023 • 57D79041
57D79023 57D79029
v NEXTLVL
57D79024
Explanation: Array member physical location conflicts 57D79030
with another array.
v SIP3110
57D79025 v FI02112
Response: An incompatible device is at the physical 57D79031
exposed.
57D79026 57D79032
location. failed.

v NEXTLVL v SIP3110
v FI02112
57D79027
57D79040
initiated.
Failing Item:
v SIP3113 57D79041
57D79028 and corrected errors.

Failing Item:
v SVCDOCS

57D79042 • 57D79082
57D79042 57D79072
the problem.
more disk units.
57D79051 Response: Multiple I/O adapters not capable of
v SIP3132
57D79075
57D79052 Explanation: Incomplete multipath connection
Failing Item:
v NEXTLVL 57D79076
previous problems.
Failing Item:
57D79055
v FI01105
storage IOA.
Response: No service action required. 57D79082
57D79070
Failing Item:
v FI01105
required.
v STORIOA
57D79071
IOA is operational.

57D79083 • 57D7FF3D
57D79083 57D79903
57D79084 57D7C000
required. required.
57D79090 is logged for information only.
last known status. 57D7C402
assistance.
Failing Item:

level of support. 57D7FF3D

v STORIOA
57D79091 v ANYBRDG
detected.
level of support.
Failing Item:
v SVCDOCS
57D79092
use.
Failing Item:
v SIP3134
57D79500
Failing Item:
v PTFSRCH

57D81310 • 57D84020

57D81310 57D83401
v DEVBPLN
them.
57D83405
57D83000
model.
v ANYBRDG
57D83020 v Check the Product Activity Log for other entries that
v SIP3150 PTFs.
57D83100 have gathered.
v SIP3150
Failing Item:
57D83140 v PTFSRCH

required. 57D834FF
57D83202 Response: No action required. This reference code is

configuration. An I/O processor might be required. 57D83601

required.
v SVCDOCS
57D84010
57D83400
Failing Item:
enclosures.
v SIP3150
Failing Item:
v FI02112
v SIP3142
v STORIOA
v SASCABL
57D84020

57D84030 • 57D84150

57D84070
design limits.
Failing Item:
required.
v SIP3143
57D84080
57D84030

57D84040 corrective action.

v SIP3295
57D84100
Failing Item:
v SIP3144 Explanation: Device bus fabric error.
Failing Item:
57D84041 v SIP3152
Explanation: Incomplete multipath connection. v SASCABL
v SASEXP
device backplane and device. v DEVBPLN
v STORIOA
Failing Item:
v FI01105
v SIP3146
57D84101
57D84050
multipath function. Failing Item:
v SIP3148
57D84110
57D84060 Explanation: Unsupported enclosure function
detected.
Failing Item:
failed. v SIP3145
Failing Item:
57D84150
v SIP3153
v SASCABL Explanation: I/O adapter detected PCI bus error.
57D84061
Failing Item:
Response: A redundant disk unit connection has been v BACKPLN
v STORIOA

57D84160 • 57D88157
57D84160 57D88145
Explanation: I/O adapter detected and recovered a Explanation: Disk device detected recoverable error.
PCI bus error.
Response: If this event appears in a serviceable event controller resource. Contact your next level of support
view, work with the failing item list found there. If this to determine the part number and location code of the
event does not appear in a serviceable event view, no device.
Failing Item:
v BACKPLN
v STORIOA 57D88146
57D870DD
Failing Item:
v FI01105
successfully.
57D88150
57D88100
Failing Item:
Failing Item:
v STORIOA
v PTFSRCH
v ANYBRDG
v STORIOA
57D88151
57D88130
57D88155
Failing Item:
v SIP3150
Failing Item:
57D88140 v PTFSRCH
v STORIOA
error.
57D88156
view, work with the failing item list found there. If this Explanation: A permanent failure occurred.
Failing Item:
v PTFSRCH
Failing Item:
v STORIOA
v SIP3150
57D88157
57D88141
Explanation: IOA detected recoverable device error. Failing Item list in the Service Action Log will vary
Response: No action is required. This reference code based on the conditions this event was logged for.
is logged for information only. Response: The FRU list in the Service Action Log will

57D88300 • 57D88400
2. If the Failing Item indicates SVCDOCS, then 3. Suspect a problem with the connection to the
continue with this step. Otherwise go to the next enclosure. The problem may have been temporary
step. Do NOT replace the I/O adapter. This is a while working on the unit or while working on the
recoverable error. connection or cable(s) to the unit. If the adapter
v LIC will automatically re-IPL the virtual I/O problems were created while working on the unit or
processor associated with the adapter. Other working on the connection to the unit, go to step 5.
resources attached to the virtual I/O processor 4. Search for problems logged at about the same time
may need to be Varied On. and call out the FRUs that connect the expansion
step. Do NOT replace the I/O adapter. This is a Failing Item:
recoverable error.
v STORIOA
v ANYBRDG
v If the virtual I/O processor or adapter are not 57D88301
Code.
ends the procedure. v STORIOA
I/O adapter. 57D88302

Failing Item:
57D88300 v SVCDOCS

57D88400
Failing Item:

57D88404 • 57D89027
57D88404 57D89022
Explanation: System log entry only. No service action Explanation: Two or more disk units missing from
required. RAID-5 or RAID-6 array.
Failing Item:
57D89000 v SIP3111
v FI01105 Explanation: One or more array members not in
v STORIOA required physical locations.
Failing Item:
57D89001 v SIP3112
57D89024
Failing Item:
v NEXTLVL Explanation: Array member physical location conflicts
with another array.

v NEXTLVL
Failing Item:
57D89025
v NEXTLVL
57D89008 Response: An incompatible device is at the physical

Explanation: I/O card does not support functions exposed.
Failing Item:
Failing Item:
v SIP3110
v SIP3130
v FI02112
57D89011
57D89026
those attached.
location.
Failing Item:
Failing Item:
57D89020
v NEXTLVL
57D89027
Failing Item:
57D89021 parity data is out of synchronization.
v SIP3113
Failing Item:
v SIP3111

57D89028 • 57D89055
57D89028 57D89041
Explanation: Maximum number of functional arrays Explanation: Background array parity check detected
has been exceeded. and corrected errors.
Response: Reduce the number of arrays on this I/O Response: Call your next level of support to report
adapter. Either move all the devices in an array to the problem.
Failing Item:
v NEXTLVL
Failing Item:
v SVCDOCS
57D89042
57D89029
on disk unit.
the problem.
Failing Item:
v NEXTLVL
57D89050
57D89030
Explanation: Array no longer protected due to more disk units.
Failing Item:
v SIP3110
v FI02112 57D89051
57D89031 missing or failed devices.
Explanation: Automatic rebuild initiated for array. Failing Item:
Response: Either a previous rebuild was interrupted v SIP3132
57D89052
modified devices.
57D89032
Response: The array is still protected, but the disk v NEXTLVL
v SIP3110 Explanation: IOA resources not available due to
v FI02112 previous problems.
Failing Item:
57D89040 v SIP3121
initiated. 57D89055
Response: No action required. Explanation: Write cache data is available for attached
storage IOA.

57D89070 • 57D89092
57D89070 57D89082
required.
Failing Item:
v FI01105
57D89071
v STORIOA
IOA is operational.
57D89083
required.
57D89072
Explanation: Link from IOA to auxiliary or remote 57D89084
57D89073 57D89090
57D89074
Failing Item:
Failing Item:
v SVCDOCS
v SIP3141
57D89091
57D89075
57D89076 If any reference codes are surfaced, use the new
v SIP3147
Failing Item:
v SVCDOCS
57D89081
Explanation: Device error. 57D89092
v FI01105 use.
v SIP3134

57D89500 • 57FC3103
57D89500 57D8C402
Explanation: Internal program error in driver code. Explanation: Licensed Internal Code error.
Failing Item: Response: Ask your next level of support for
v PTFSRCH assistance.
Failing Item:
57D89903 v PTFSRCH
Informational event, no service required. 57D8FF3D
57D8C000
Failing Item:
Explanation: System log entry only. No service action v STORIOA
required.
v ANYBRDG
(57FC) Reference codes

57FC3020
Failing Item:
v FCINTF
v ANYFC
v FCIOA
Failing Item:
v OPT_CLN
v SVCDOCS
57FC3101
57FC3021
Failing Item:
v FCINTF
v ANYFC
Failing Item:
v FCIOA
v SVCDOCS
v OPT_CLN
57FC3022
57FC3102
Failing Item:
v FCINTF
Failing Item:
v ANYFC
v SVCDOCS
v FCIOA
v OPT_CLN
57FC3023
Explanation: Configuration error on port 3. 57FC3103
Response: Too many devices have been configured on Explanation: Interface error on port 3.
Failing Item:
Failing Item:
v FCINTF
v SVCDOCS
v ANYFC
v FCIOA
57FC3100
v OPT_CLN

57FC3120 • 57FC3400
57FC3120 57FC3123
Explanation: An open port was detected on port 0. Explanation: An open port was detected on port 3.
Problem determination: Perform the following steps: Problem determination: Perform the following steps:
1. Check for a missing cable or wrap connector. 1. Check for a missing cable or wrap connector.
2. This error can occur when a shared device is being 2. This error can occur when a shared device is being
moved from one LPAR to another LPAR and the moved from one LPAR to another LPAR and the
port was left open. port was left open.
3. This error can occur if there is a port or link failure. 3. This error can occur if there is a port or link failure.
If you have eliminated the above possibilities If you have eliminated the above possibilities
contact your next level of support. contact your next level of support.
v FCPORT v FCPORT
v FCIOA v FCIOA
v FCDEV v FCDEV
v OPT_CLN v OPT_CLN
57FC3121 57FC3140
Explanation: An open port was detected on port 1. Explanation: Port 0 is now operational.
Problem determination: Perform the following steps: Response: This reference code and the 3120 reference
1. Check for a missing cable or wrap connector. code that occurred before it require no service action,
port was left open. 57FC3141
3. This error can occur if there is a port or link failure. Explanation: Port 1 is now operational.
contact your next level of support. Response: This reference code and the 3121 reference
Failing Item: since the port is now operational.
v FCPORT
v FCIOA 57FC3142
v FCDEV
v OPT_CLN
57FC3122 since the port is now operational.
Problem determination: Perform the following steps: 57FC3143
1. Check for a missing cable or wrap connector. Explanation: Port 3 is now operational.
2. This error can occur when a shared device is being Response: This reference code and the 3123 reference
moved from one LPAR to another LPAR and the code that occurred before it require no service action,
port was left open. since the port is now operational.
57FC3400
Failing Item:
v FCPORT Failing Item:
v FCIOA v FCDEV
v FCDEV v FCINTF
v OPT_CLN v ANYFC
v FCIOA
v OPT_CLN

57FC3405 • 57FC8301
57FC3405 57FC8131
Explanation: An error occurred during task Explanation: Recovered Fibre Channel interface error
initialization for a removable media device. This SRC is on port 1.
model.
57FC8132
indicate interface problems and work those Explanation: Recovered Fibre Channel interface error
problems. on port 2.
v Check the device firmware level and apply the latest Response: No action required. This reference code is
PTFs. logged for information only.
your next level of support with the information you 57FC8133
have gathered.
Problem determination: IPL the IOP to retry the on port 3.
contact your service provider. Response: No action required. This reference code is
Failing Item:
v PTFSRCH
57FC8150
57FC34FF Explanation: A permanent I/O adapter failure

occurred.
Failing Item:
Response: The device indicated that a format is in v FCIOA
should be usable. No action is required. This reference v ANYBRDG
57FC4150 57FC8151
Explanation: I/O adapter detected PCI bus error. Explanation: Licensed Internal Code error.
v FCIOA
Failing Item:
57FC8300
v BACKPLN
v FCIOA
Failing Item:
57FC8100 v FCIOA
v ANYBRDG
v PTFSRCH
Failing Item:
v OPT_CLN
v PTFSRCH
v FCIOA
57FC8301
57FC8130
Code.
Failing Item:
on port 0.
v PTFSRCH
v FCIOA

57FC8302 • 57FE31AX
v OPT_CLN Explanation: System log entry only, no service action

required.
57FC8302 Response: No action is required. This reference code
57FCB402
Failing Item:
v FCIOA v PTFSRCH
v OPT_CLN
57FCC000
57FC9500 Explanation: System log entry only, no service action
required.
Failing Item:
v PTFSRCH
57FCC402
57FC9903
Informational event, no service required. Failing Item:
v PTFSRCH
57FCB000
(57FE) Reference codes

v SVCDOCS
57FE3000
v USB_DEV
57FE3100
57FE3002 Explanation: USB device bus error.
Explanation: Unexpected USB device disconnect Failing Item:

detected. v USB_CBL
Failing Item: v USB_DEV
v USB_DEV v USB_IOA
57FE3010 57FE31AX
Explanation: USB undefined device response. Explanation: USB port over current error detected.
The port location is listed in the serviceable event view
Failing Item: with the "USBPORT" symbolic FRU. The logical port
v USB_DEV number is the last character of the URC.
57FE3020 '1' and are in the hexadecimal range of 1 through F for
each USB port on an adapter.
Explanation: USB configuration error. Too many USB
devices are plugged. The internal device map is full. For the USB port identified by the last digit of the
URC, there is a problem with the power being drawn
by the device. If the device is within operating
time until the problem is resolved. In the Service Action
specifications it may work properly when plugged into
Log (SAL) the location of the device that caused this
error is listed with the FRU.
Failing Item: against the port where the device is plugged then the

57FE31BX • 57FE8303
device may be failing. Try moving the device to a v Yes - The device may have been initializing when an
different adapter. access occurred. Reset / reload the adapter or retry
the IPL. If the problem persists then the device is
If the device operates properly on another USB port or
failing.
adapter or the adapter's USB port. v No - The device is unknown or was unexpectedly
removed.
Remove the device on the port given in the location
code of symbolic FRU "USBPORT" and look for a Failing Item:
xxxx31By SRC to be logged where "xxxx" are the same v USB_DEV
characters as the first four characters of this SRC and 'y' v USB_CBL
is the same as the last character of this SRC.
v If the xxxx31By SRC is logged at about the same
57FE4150
time that you removed the device then examine the
location code of symbolic FRU "USBPORT" for the Explanation: USB IOA hard PCI error.
xxxx31By SRC. If the location code for "USBPORT" is
the same as the adapter and port location called out Failing Item:
by this SRC then the problem at this port has been v USB_IOA
corrected. The device may be failing. The device may v ANYBRDG
function properly on another USB port or another
system.
57FE8100
v If the xxxx31By SRC is not logged then work the
failing item list in the serviceable event view or from Explanation: USB IOA manager program error.
the list below.
Failing Item:
v SVCDOCS
v USBPORT 57FE8150
v USB_DEV
v USB_IOA
Failing Item:
v USB_DEV
57FE31BX
v USB_IOA
Explanation: USB port over current error removed.
Problem determination: An over current condition 57FE8300
that previously existed on this port has been resolved.
The port is operating normally. The port location is Explanation: USB IOA hardware error, IOA reset
listed with symbolic FRU "SVCDOCS" in the issued.
serviceable event view. The logical port number is the Failing Item:
last character of the SRC.
v USB_IOA
Failing Item:
v SVCDOCS 57FE8301
57FE3202
Failing Item:
logged. Informational event, no service required. v AJDGP01
57FE3400 57FE8303
Explanation: USB unknown device or unexpected Explanation: USB port enumerator error.
device removal. If this SRC appears in a serviceable Failing Item:
event view then it requires service. Otherwise no
v AJDGP01
service is required.
v USB_IOA
an IPL?

57FEC000 • 57FF3100

57FEC000
Failing Item:
logged. Informational event, no service required. v MEDIA
v USB_DEV
57FEC402
57FEFFF4
logged. Informational event, no service required. Explanation: USB internal device error.
Failing Item:
57FEFF3D v USB_DEV
recovered from a temporary error. No action is 57FEFFFE
required. This reference code is logged for information
only. Explanation: USB temporary bus error.
57FEFFF3
(57FF) Reference codes

57FF1310 57FF3021
Explanation: I/O adapter resource not available. Explanation: SCSI bus configuration error.
Failing Item:
them. v IOPIP17
v USER
57FF3000 v FI01107
v STORIOA
Failing Item:
57FF3022
v FI01101
v ANYBRDG
57FF3006 Failing Item:
v USER
Failing Item:
v FI01107
v FI01101
v STORIOA
v ANYBRDG
v PTFSRCH
57FF3023
57FF3020 Explanation: SCSI bus configuration error.
Explanation: SCSI bus configuration error. Response: Error occurred on SCSI bus 3.

v IOPIP17
Failing Item:
v USER
v IOPIP17
v FI01107
v USER
v STORIOA
v FI01107
v STORIOA
57FF3100

57FF3101 • 57FF3143

57FF3121
Failing Item:
v IOPIP13
v FI01107
v FI01140
Failing Item:
v DEVBPLN
v SVCDOCS
57FF3101
57FF3122
v IOPIP13 Remove the device.
v STORIOA v SVCDOCS
v FI01140
v DEVBPLN 57FF3123
57FF3102
Remove the device.
Failing Item:
Failing Item:
v SVCDOCS
v IOPIP13
v FI01107
57FF3140
v STORIOA
v FI01140 Explanation: Bus is operational.
57FF3103
Explanation: Interface error. 57FF3141
Response: Error occurred on SCSI bus 3. Explanation: Bus is operational.
v STORIOA
v FI01140 57FF3142
57FF3120 code that occurred before it require no service action
57FF3143
Remove the device. Explanation: Bus is operational.
v SVCDOCS code that occurred before it require no service action

57FF3150 • 57FF4150
57FF3150 57FF3405
Explanation: SCSI bus configuration error. Explanation: An error occurred during task
model.
Failing Item:
v SVCDOCS
57FF3151 problems.
Explanation: SCSI bus configuration error. v Check the device firmware level and apply the latest
PTFs.
Response: Internal and external SCSI cables are v Check for LIC logs with major code 2E00. Contact
connected to SCSI bus 1 at the same time. Correct the your next level of support with the information you
SCSI bus 1 configuration. have gathered.
v SVCDOCS device identification process. If the error persists then
Explanation: A tape/CD or disk device reported a v PTFSRCH
failure.
Failing Item: 57FF34FF
v FI01105 Explanation: A device on this adapter is being
v STORIOA formatted. Wait for the formatting to complete.
v MEDIA Failing Item:
v SVCDOCS
57FF3202
Explanation: Storage subsystem configuration error. 57FF3501
Response: The device is not supported in the current Explanation: Licensed Internal Code error.
configuration. An I/O processor might be required. Response: The device type is either unsupported or
Failing Item: the code has not been loaded to support it.
v FI01105
57FF3400 v PTFSRCH
57FF3601
check EXTSCSI and DEVTERM first. Explanation: System log entry only. No service action
required.
Failing Item:
v FI02112
57FF4150
v STORIOA
v FI01106 Explanation: I/O adapter detected PCI bus error.
v FI01140 Response: If this event appears in a serviceable event
57FF3401
Failing Item: the adapter has multiple physical parts. Choose the
v DEVBPLN card type to identify the physical parts of the storage
adapter.

57FF4160
Card type 2BE1 (feature RAID enablement card for If you are working with one of the card types below,
embedded IOA) read the following: When working the the adapter has multiple physical parts. Choose the
FRUs from the serviceable event or the failing item list card type to identify the physical parts of the storage
here, the embedded storage adapter (STORIOA) has adapter.
three physical parts:
v The RAID enablement card. here, the embedded storage adapter (STORIOA) has
v The Battery charger and carrier card. three physical parts:
See symbolic FRU FEATCRD for the location codes of backplane.
the FRUs if they are not listed in the serviceable event v The RAID enablement card.
v The embedded storage adapter on the I/O card for embedded IOA) read the following: When
backplane. working the FRUs from the serviceable event or the
v The Battery charger and carrier card. failing item list here, the embedded storage adapter
See symbolic FRU FEATCRD for the location codes of v The embedded storage adapter on the I/O
the FRUs if they are not listed in the serviceable event backplane.
v The embedded storage adapter on the DASD embedded IOAs) read the following: When working
backplane. the FRUs from the serviceable event or the failing item
v The dual battery charger and carrier card. To list here, the embedded storage adapters (STORIOA)
determine which battery is connected to which have two physical parts:
embedded IOA use the bus number of the IOA with v The embedded storage adapter on the DASD
symbolic FRU CACHBAT. backplane.
Failing Item: See symbolic FRU FEATCRD for the location code of
v BACKPLN the dual battery charger and carrier card if it is not
v STORIOA
Failing Item:
57FF4160
v BACKPLN
v STORIOA
PCI bus error.

57FF8008 • 57FF8151
57FF8008 57FF8133
Explanation: A permanent cache battery pack failure Explanation: IOA detected recoverable device bus
occurred. error.
Response: NOTE: Under a certain configuration, this Response: An error occurred on SCSI bus 3. No action
SRC may not represent an error that requires a service is required. This reference code is logged for
action. Depending on the configuration of the system, information only.
57FF8140
Source drive. If this is the case, this error will be posted Explanation: IOA detected recoverable device bus
each time the IOA is IPLed and it can be ignored. error.
v CACHBAT is logged for information only.
v STORIOA
57FF8141
57FF8009 Explanation: IOA detected recoverable device error.
Explanation: Impending cache battery pack failure. Response: No action is required. This reference code
Failing Item:
v CACHBAT
57FF8145
57FF8100 Explanation: A recoverable error occurred.

v STORIOA
Failing Item:
v PTFSRCH
57FF8146
v STORIOA
Explanation: IOA detected recoverable device bus v FI01105
error.
Response: An error occurred on SCSI bus 0. No action 57FF8150
information only.
57FF8131 action. Depending on the configuration of the system,
Explanation: IOA detected recoverable device bus the Storage IOA may have been altered and/or the
error. Storage IOA Cache may have been disabled to allow
Response: An error occurred on SCSI bus 1. No action Source drive. If this is the case, this error will be posted
is required. This reference code is logged for each time the IOA is IPLed and it can be ignored.
information only.
Failing Item:
v STORIOA
57FF8132
v ANYBRDG
error.
57FF8151
is required. This reference code is logged for Explanation: Licensed Internal Code error.
v PTFSRCH
v STORIOA

57FF8155 • 57FF9008
57FF8155 57FF8302
Explanation: A permanent failure occurred. Explanation: Missing Licensed Internal Code.
v SVCDOCS
57FF8156 v STORIOA
57FF8400
Failing Item:
v PTFSRCH
57FF8157
Explanation: I/O adapter card error. 57FF8404
Response: Display the Service Action Log entry for Explanation: System log entry only. No service action
this SRC. If the Failing Item indicates an I/O adapter, required.
indicates SVCDOCS, then do NOT replace the I/O 57FF9000
following for the I/O processor that the I/O adapter is Explanation: Device error.
attached to: Failing Item:
1. If the I/O processor is not operable and disk units v FI01105
re-IPL the IOP. Other resources attached to the IOP v STORIOA
may then need to be Varied On.
2. If disk units are not attached, perform the "VRYCFG 57FF9001
Failing Item:
Failing Item:
v IOPIP33
v SVCDOCS
57FF9002
57FF8300
Failing Item:
Failing Item:
v IOPIP16
v STORIOA
v FI01105
v ANYBRDG
v STORIOA
v PTFSRCH
v FI01140
v BACKPLN
57FF8301
v FI01106
Code.
57FF9008
Failing Item:
v PTFSRCH
v STORIOA
Failing Item:
v IOPIP25

57FF9009 • 57FF902F
v IOPIP22
57FF9009
57FF9025
assistance.
Failing Item:
location.
v SVCDOCS
Failing Item:
v IOPIP21
57FF9010
57FF9026
Failing Item:
v IOPIP31
Failing Item:
v IOPIP22
57FF9011
57FF9027
those attached.
Failing Item:
v IOPIP32
Failing Item:
v IOPIP34
57FF9020
57FF9028
Failing Item:
detected.
v IOPIP20
57FF9021 another I/O adapter that supports arrays, or stop an
hardware configuration. Failing Item:
v IOPIP20
57FF9029
57FF9022 Explanation: Incorrect hardware configuration change
Explanation: Array not functional due to present detected.
hardware configuration. Response: Contact your next level of support.
v IOPIP22 v SVCDOCS
57FF9023 57FF902F
Explanation: Array not functional due to present Explanation: Array addendum Product Activity Log
hardware configuration. entry.
Failing Item: Response: This entry contains additional array
57FF9024
Failing Item:

57FF9030 • 57FF9054
57FF9030 57FF9050
v FI02112 v IOPIP30
v IOPIP21
57FF9051
57FF9031 Explanation: Cache data exists for a missing or failed
Explanation: Automatic rebuild initiated for array. device.
Response: Either a previous rebuild was interrupted Response: If all configured units are missing, a 9054
and was automatically restarted, or a hot spare disk reference code may appear in the product activity log.
unit was used to automatically rebuild the array. Look If so, perform the action indicated for the 9054
for other reference codes and take action on them. reference code.
57FF9032 failing item list.
Explanation: A disk unit in a RAID array is missing Failing Item:

or failed. v IOPIP27
unit should be replaced. Replace the device first if a 57FF9052
device is listed first in the Service Action Log. If a
device is not listed first in the Service Action Log then
been modified.
Failing Item:
v IOPIP21 v SVCDOCS
57FF9040 57FF9053
Explanation: Array protection temporarily suspended. Explanation: IOA resources not available due to
previous problems.
automatically restarted. Response: Take action on other reference codes which
have surfaced.
57FF9041 If you cannot get to SST or DST, and cannot perform a

Explanation: Background array parity check detected media. Look for Product Activity Log entries for other
and corrected errors. reference codes and take action on them.
Response: Call your next level of support to report Failing Item:
the problem.
v SVCDOCS
Failing Item:
v PTFSRCH 57FF9054
57FF9042 previous problems.
Explanation: An array parity error has been detected Response: Power off the system and remove all new
and corrected. or replacement disk units. IPL the system to DST. If
Response: Call your next level of support to report you cannot perform a type A or B IPL, perform a type
the problem. D IPL from removable media.
Failing Item: Look for Product Activity Log entries for other
v NEXTLVL
Failing Item:
v SVCDOCS

57FF9070 • 57FFC402
57FF9070 57FF9091
Explanation: System log entry only. No service action Explanation: Incorrect hardware configuration change
required. detected.
57FF9071 are surfaced, use the new reference code to resolve the
problem.
went operational. If you cannot resolve the problem, contact your next
level of support.
Failing Item:
57FF9072 v SVCDOCS

went non-operational. 57FF9092
use.

v IOPIP26
57FF9500
Failing Item:
v IOPIP40 Explanation: Internal program error in driver code.
Failing Item:
57FF9081 v PTFSRCH
57FF9902
Failing Item:
required.
v STORIOA
57FF9903
57FF9082
Failing Item:
v IOPIP16 57FFC000
v FI01105
v STORIOA required.
v FI01140
v BACKPLN is logged for information only.
v FI01106
57FFC100
57FF9090
Explanation: Disk unit has been modified after the required.
last known status.
Response: Re-IPL the system. If any reference codes is logged for information only.
problem.
57FFC402
level of support.
Failing Item:
assistance.
v SVCDOCS
Failing Item:

57FFFF3D • 58B03110
v PTFSRCH
57FFFF6D
57FFFF3D
Failing Item:
v STORIOA
Failing Item:
v ANYBRDG
v STORIOA
v PTFSRCH
v ANYBRDG

58B0102E
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v SASEXP
58B03002
Explanation: Addressed device failed to respond to 58B03109
selection.
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v DEVBPLN
v SASCABL
v SASCABL
v SASEXP
v SASEXP
58B0310C
58B03010
IOA. Failing Item:
v DISKDRV v DISKDRV
v STORIOA v STORIOA
v SASCABL
v SASEXP 58B0310D
Explanation: Replacement device is not supported. v SIP3250
v DISKDRV v STORIOA
v STORIOA
v SASCABL 58B03110
Explanation: A device replacement has occurred. v DISKDRV
Response: No action required. This reference code is v STORIOA
logged for information only. v SASCABL
v SASEXP
58B03100

58B03130 • 58B0FFF6
58B03130 58B07000
level of support.
58B034FF view, work with the failing item list found there. If this
Explanation: Format in progress. event does not appear in a serviceable event view, no
v DISKDRV
58B04041
58B070DD
required.
Failing Item:
58B0FFF3
v SIP3146

v DISKDRV
58B0FFF4
failed.
Failing Item:
v SASCABL v DISKDRV
v SASEXP v STORIOA
58B04061 58B0FFF5
Explanation: Multipath redundancy level increased. Explanation: Disk sector read error.
Response: A redundant disk unit connection has been Response: If this event appears in a serviceable event
restored. No service action is required. view, work with the failing item list found there. If this
58B04100
Failing Item:
v DISKDRV
Failing Item:
v SIP3152 58B0FFF6
v SASCABL
v SASEXP
v DEVBPLN
Failing Item:
v DISKDRV

58B0FFF7 • 58B0FFFE
58B0FFF7 58B0FFFD
Explanation: Temporary disk data error. Explanation: Soft device bus error.
v DISKDRV v SIP3250
v DISKDRV
58B0FFF9 v STORIOA
58B0FFFE
view, work with the failing item list found there. If this Explanation: Temporary disk bus error.
Failing Item:
58B0FFFA v SIP3150
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58B0FFFB
58B0FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58B2102E • 58B234FF

58B2102E 58B23109
v DISKDRV v DISKDRV
v STORIOA
58B23002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
58B23010 58B2310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
58B23110
58B23020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
58B23130
58B23029
Failing Item:
58B23100
v SVCDOCS
v STORIOA
v SASEXP

58B24041 • 58B2FFF9
58B24041 58B270DD
required.
58B2FFF3
Failing Item:
Failing Item:
58B24060 v DISKDRV
58B2FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
58B2FFF5

v DISKDRV
Failing Item:
58B2FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
58B27000

58B2FFF9
Failing Item:
v DISKDRV


58B2FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58B2FFFB
58B2FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
58B2FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58B3102E • 58B334FF

58B3102E 58B33109
v DISKDRV v DISKDRV
v STORIOA
58B33002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
58B33010 58B3310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
58B33110
58B33020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
58B33130
58B33029
Failing Item:
58B33100
v SVCDOCS
v STORIOA
v SASEXP

58B34041 • 58B3FFF9
58B34041 58B370DD
required.
58B3FFF3
Failing Item:
Failing Item:
58B34060 v DISKDRV
58B3FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
58B3FFF5

v DISKDRV
Failing Item:
58B3FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
58B37000

58B3FFF9
Failing Item:
v DISKDRV


58B3FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58B3FFFB
58B3FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
58B3FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58B4102E • 58B434FF

58B4102E 58B43109
v DISKDRV v DISKDRV
v STORIOA
58B43002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
58B43010 58B4310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
58B43110
58B43020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
58B43130
58B43029
Failing Item:
58B43100
v SVCDOCS
v STORIOA
v SASEXP

58B44041 • 58B4FFF9
58B44041 58B470DD
required.
58B4FFF3
Failing Item:
Failing Item:
58B44060 v DISKDRV
58B4FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
58B4FFF5

v DISKDRV
Failing Item:
58B4FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
58B47000

58B4FFF9
Failing Item:
v DISKDRV


58B4FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58B4FFFB
58B4FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
58B4FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58B5102E • 58B534FF

58B5102E 58B53109
v DISKDRV v DISKDRV
v STORIOA
58B53002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
58B53010 58B5310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
58B53110
58B53020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
58B53130
58B53029
Failing Item:
58B53100
v SVCDOCS
v STORIOA
v SASEXP

58B54041 • 58B5FFF9
58B54041 58B570DD
required.
58B5FFF3
Failing Item:
Failing Item:
58B54060 v DISKDRV
58B5FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
58B5FFF5

v DISKDRV
Failing Item:
58B5FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
58B57000

58B5FFF9
Failing Item:
v DISKDRV


58B5FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58B5FFFB
58B5FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
58B5FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58B6102E • 58B634FF

58B6102E 58B63109
v DISKDRV v DISKDRV
v STORIOA
58B63002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
58B63010 58B6310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
58B63110
58B63020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
58B63130
58B63029
Failing Item:
58B63100
v SVCDOCS
v STORIOA
v SASEXP

58B64041 • 58B6FFF9
58B64041 58B670DD
required.
58B6FFF3
Failing Item:
Failing Item:
58B64060 v DISKDRV
58B6FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
58B6FFF5

v DISKDRV
Failing Item:
58B6FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
58B67000

58B6FFF9
Failing Item:
v DISKDRV


58B6FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58B6FFFB
58B6FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
58B6FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58B8102E • 58B834FF

58B8102E 58B83109
v DISKDRV v DISKDRV
v STORIOA
58B83002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
58B83010 58B8310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
58B83110
58B83020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
58B83130
58B83029
Failing Item:
58B83100
v SVCDOCS
v STORIOA
v SASEXP

58B84041 • 58B8FFF9
58B84041 58B870DD
required.
58B8FFF3
Failing Item:
Failing Item:
58B84060 v DISKDRV
58B8FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
58B8FFF5

v DISKDRV
Failing Item:
58B8FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
58B87000

58B8FFF9
Failing Item:
v DISKDRV


58B8FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58B8FFFB
58B8FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
58B8FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58B9102E • 58B934FF

58B9102E 58B93109
v DISKDRV v DISKDRV
v STORIOA
58B93002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
58B93010 58B9310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
58B93110
58B93020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
58B93130
58B93029
Failing Item:
58B93100
v SVCDOCS
v STORIOA
v SASEXP

58B94041 • 58B9FFF9
58B94041 58B970DD
required.
58B9FFF3
Failing Item:
Failing Item:
58B94060 v DISKDRV
58B9FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
58B9FFF5

v DISKDRV
Failing Item:
58B9FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
58B97000

58B9FFF9
Failing Item:
v DISKDRV


58B9FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58B9FFFB
58B9FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
58B9FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58BB102E • 58BB34FF
(58BB) Reference codes

58BB102E 58BB3109
v DISKDRV v DISKDRV
v STORIOA
58BB3002 v SASCABL
selection.
Failing Item: 58BB310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
58BB3010 58BB310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
58BB3110
58BB3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
58BB3130
58BB3029
Failing Item:
58BB3100
v SVCDOCS
Failing Item: 58BB34FF
v STORIOA
v SASEXP

58BB4041 • 58BBFFF9
58BB4041 58BB70DD
required.
58BBFFF3
Failing Item:
Failing Item:
58BB4060 v DISKDRV
58BBFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
58BBFFF5
58BB4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
58BBFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
58BB7000
Explanation: Disk sector read error. 58BBFFF7
58BB7001 event does not appear in a serviceable event view, no

58BBFFF9
Failing Item:
v DISKDRV

58BBFFFA • 58BBFFFE

58BBFFFE
Failing Item:
58BBFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
58BBFFFB
58BBFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
58BBFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

58F83000 • 58F83400
(58F8) Reference codes

against the port where the device is plugged then the
58F83000
device may be failing. Try moving the device to a
Explanation: USB optical device information was different adapter.
58F83002 adapter or the adapter's USB port.
Explanation: Unexpected USB device disconnect Remove the device on the port given in the location
detected. code of symbolic FRU "USBPORT" and look for a
Failing Item:
v USB_DEV is the same as the last character of this SRC.
58F83010 time that you removed the device then examine the
Explanation: USB undefined device response. xxxx31By SRC. If the location code for "USBPORT" is
Failing Item: the same as the adapter and port location called out
v USB_DEV
58F83020 system.
Explanation: USB configuration error. Too many USB v If the xxxx31By SRC is not logged then work the
devices are plugged. The internal device map is full. failing item list in the serviceable event view or from
the list below.
time until the problem is resolved. In the Service Action Failing Item:
Log (SAL) the location of the device that caused this v SVCDOCS
error is listed with the FRU. v USBPORT
v SVCDOCS v USB_IOA
v USB_DEV
58F831BX
58F83100 Explanation: USB port over current error removed.
Explanation: USB device bus error. Problem determination: An over current condition
Failing Item: that previously existed on this port has been resolved.
The port is operating normally. The port location is
v USB_CBL
listed with symbolic FRU "SVCDOCS" in the
v USB_DEV serviceable event view. The logical port number is the
v USB_IOA last character of the SRC.
Failing Item:
58F831AX v SVCDOCS
Explanation: USB port over current error detected.
The port location is listed in the serviceable event view 58F83202
with the "USBPORT" symbolic FRU. The logical port
number is the last character of the URC. Explanation: USB optical device information was
each USB port on an adapter. 58F83400
For the USB port identified by the last digit of the Explanation: USB unknown device or unexpected
URC, there is a problem with the power being drawn device removal. If this SRC appears in a serviceable
by the device. If the device is within operating event view then it requires service. Otherwise no
specifications it may work properly when plugged into service is required.

58F84150 • 58F8FFFE

58F8C000
an IPL?
v Yes - The device may have been initializing when an Explanation: USB optical device information was
access occurred. Reset / reload the adapter or retry logged. Informational event, no service required.
failing. 58F8C402
v No - The device is unknown or was unexpectedly
removed.
Failing Item:
v USB_DEV 58F8FF3D
v USB_CBL
recovered from a temporary error. No action is
58F84150 required. This reference code is logged for information
only.
Failing Item:
58F8FFF3
v USB_IOA
v ANYBRDG
Failing Item:
58F88100 v MEDIA
v USB_DEV
Failing Item:
58F8FFF4
v AJDGP01

v USB_DEV
Failing Item:
58F8FFFE
v USB_DEV
v USB_IOA
58F88300
issued.
Failing Item:
v USB_IOA
58F88301
Failing Item:
v AJDGP01
58F88303
Failing Item:
v AJDGP01
v USB_IOA

58F93000 • 58F93400

against the port where the device is plugged then the
58F93000
device may be failing. Try moving the device to a
Explanation: USB optical device information was different adapter.
58F93002 adapter or the adapter's USB port.
Explanation: Unexpected USB device disconnect Remove the device on the port given in the location
detected. code of symbolic FRU "USBPORT" and look for a
Failing Item:
v USB_DEV is the same as the last character of this SRC.
58F93010 time that you removed the device then examine the
Explanation: USB undefined device response. xxxx31By SRC. If the location code for "USBPORT" is
Failing Item: the same as the adapter and port location called out
v USB_DEV
58F93020 system.
Explanation: USB configuration error. Too many USB v If the xxxx31By SRC is not logged then work the
devices are plugged. The internal device map is full. failing item list in the serviceable event view or from
the list below.
time until the problem is resolved. In the Service Action Failing Item:
Log (SAL) the location of the device that caused this v SVCDOCS
error is listed with the FRU. v USBPORT
v SVCDOCS v USB_IOA
v USB_DEV
58F931BX
58F93100 Explanation: USB port over current error removed.
Explanation: USB device bus error. Problem determination: An over current condition
Failing Item: that previously existed on this port has been resolved.
The port is operating normally. The port location is
v USB_CBL
listed with symbolic FRU "SVCDOCS" in the
v USB_DEV serviceable event view. The logical port number is the
v USB_IOA last character of the SRC.
Failing Item:
58F931AX v SVCDOCS
Explanation: USB port over current error detected.
The port location is listed in the serviceable event view 58F93202
with the "USBPORT" symbolic FRU. The logical port
number is the last character of the URC. Explanation: USB optical device information was
each USB port on an adapter. 58F93400
For the USB port identified by the last digit of the Explanation: USB unknown device or unexpected
URC, there is a problem with the power being drawn device removal. If this SRC appears in a serviceable
by the device. If the device is within operating event view then it requires service. Otherwise no
specifications it may work properly when plugged into service is required.

58F94150 • 58F9FFFE

58F9C000
an IPL?
v Yes - The device may have been initializing when an Explanation: USB optical device information was
access occurred. Reset / reload the adapter or retry logged. Informational event, no service required.
failing. 58F9C402
v No - The device is unknown or was unexpectedly
removed.
Failing Item:
v USB_DEV 58F9FF3D
v USB_CBL
recovered from a temporary error. No action is
58F94150 required. This reference code is logged for information
only.
Failing Item:
58F9FFF3
v USB_IOA
v ANYBRDG
Failing Item:
58F98100 v MEDIA
v USB_DEV
Failing Item:
58F9FFF4
v AJDGP01

v USB_DEV
Failing Item:
58F9FFFE
v USB_DEV
v USB_IOA
58F98300
issued.
Failing Item:
v USB_IOA
58F98301
Failing Item:
v AJDGP01
58F98303
Failing Item:
v AJDGP01
v USB_IOA

58FAA001 • 59073400
(58FA) Reference codes

58FAA001
detected.
58FAB9B0
Failing Item:
v AJDG301
Failing Item:
v IOA
58FAA6F6
v AJDG301
(58FB) Reference codes

58FBA001
detected.
58FBB9B0
Failing Item:
v AJDG301
Failing Item:
v IOA
58FBA6F6
v AJDG301

indications.
59073000
Explanation: I/O adapter hardware error detected. I/O processor.
v FI01112 v TAPCNFG
v FI00871
59073202
Explanation: Tape unit configuration error. 59073400
Response: Before exchanging any parts, verify that the Explanation: Device error has occurred.
following condition is not present: Failing Item:
v FI00872

59079020 • 59079104
v DEVTERM 5. refer to the tape device service documentation for

v FI01103
Explanation: Tape unit configuration error. v FCIOA
Response: Before exchanging any parts, verify that the v FCDEV
following conditions are not present: v FCCABLE
Processor that does not support Tape and Dasd 59079102
error.
Failing Item:
v TAPCNFG documentation to analyze the problem.
v FI00871
Failing Item:
v PTFSRCH
v FI00871
v FCGATE
59079100
v FI00872
tape unit.
tape unit.
2. For a SCSI attached device ensure that a Response: If the attached device is an external tape
terminating plug is attached to the device end of device, do the following before exchanging any parts:
the cable. 1. Ensure that the SAS cable is correctly connected to
the ports.
If the attached tape device is owned by a Virtual I/O 2. Ensure that the device has power.
I/O Server to determine the parts to replace. If the attached tape device is owned by a Virtual I/O
Failing Item: Server partition refer to Troubleshooting the Virtual
v FI00871
v FI00872 v FI00871
v DEVTERM v FI01112
v SASCABL
59079101
59079104
tape unit.
1. Ensure that the Fibre Channel cable is correctly Response: If the attached device is an external tape
connected to the ports. device, do the following before exchanging any parts:
2. Clean the Fibre Channel connectors. 1. Ensure that the USB cable is correctly connected to
the ports.
operational. 2. Ensure that the device has power.
additional problem analysis procedures.

59079200 • 59079220

59079202
Code was loaded.
Failing Item:
v USB_IOA
v USB_CBL
59079200 cable.
that there are no bent or damaged pins on the cable. Failing Item:
3. For a SCSI attached device ensure that a v FI00871
v DEVTERM
I/O Server to determine the parts to replace. 59079210
Failing Item: Explanation: Illegal or unsupported tape unit
v FI00871 response.
v FI00872 v FI00871
v DEVTERM v FI01112
v PTFSRCH
59079201
Explanation: Tape unit command timeout. 59079211
Response: If the attached device is an external device, Explanation: Gateway device detected a bus protocol
do the following before exchanging any parts: error.
1. Ensure that the device is powered on. Response: Use the gateway device service
2. If an interposer is required, make sure that it is documentation to analyze the problem.
connected between the I/O processor and the SCSI Failing Item:
cable.
v FCGATE
v FCIOA
cable. v FI00871
4. Ensure that a terminating plug is attached to the v ANYFC
device end of the SCSI cable. v FCCABLE
5. If the attached tape device is owned by a Virtual v FI00872
I/O Server partition it may be necessary to reset the v DEVTERM
v FI00871
v FI01112
v FI00872
v DEVTERM processor to be reset. Reset the I/O processor before
v MEDIA using the device.

59079221 • 59079351
v FI00871
59079221
59079310
is not correct.
Failing Item:
59079300
v PTFSRCH
v FI00871
Failing Item:
v FI00871 59079320
59079301 failure.
current operation.
v FI00871
error.
59079302
Explanation: Tape device failure or media error. documenation to analyze the problem.
Response: The tape unit detected a failure that may Failing Item:
be caused by a hardware failure or a media error. v FCCODE
information on diagnositic tests that can be run to 59079350
Failing Item: on tape medium.
v MEDIA
v FI00871 Clean the tape unit and retry the operation.
59079303 exchange the tape media.
Explanation: Gateway device failure. Failing Item:
documenation to analyze the problem. v TAPCLN
v FCGATE
59079351
59079304 Explanation: Tape with excessive error rate was
cartridge.
v USER v FI00871

59079355 • 59079900
59079355 59079803
59079804
Failing Item:
v USER 59079805
59079500
59079806
Failing Item:
v PTFSRCH
59079810
59079501
Explanation: Licensed Internal Code error. should be replaced.
Failing Item: Response: This reference code is used for ending
v PTFSRCH Online Problem Analysis with a list of failing items.
(Information Only.)
59079800
59079899
temporary I/O error. Explanation: Problem analysis completed, the problem
has been corrected.
logged for information only. Response: This reference code is used for ending
59079801
Response: No action required. This reference code is not upgraded.
59079802 not completed.
Explanation: System successfully recovered from The tape unit will continue to operate with the
temporary I/O error. previous LIC. You may do either of the following:

59079901 • 59BE310D
v Perform TUPIP04 to reset the IOP and the tape unit. Explanation: An IOP dump was initiated.
LIC.
59079903
Failing Item:
v USER Explanation: Tape device information logged.

5907FFF6
logged for information only. Explanation: Tape volume statistics logged (no action
required).
59079902
(59BE) Reference codes

59BE102E
Failing Item:
v DISKDRV 59BE3100
59BE3002
Failing Item:
v DISKDRV
selection.
v STORIOA
Failing Item:
v SASCABL
v DISKDRV
v SASEXP
v STORIOA
v DEVBPLN
59BE3109
v SASCABL
v SASEXP
Failing Item:
59BE3010 v DISKDRV
v STORIOA
IOA. v SASCABL
v SASEXP
Failing Item:
v DISKDRV
59BE310C
v STORIOA
v SASCABL Explanation: Device bus error.
v SIP3250
59BE3020 v DISKDRV
Failing Item:
59BE310D
v DISKDRV
v STORIOA Explanation: Device bus error.
v SIP3250
59BE3029 v DISKDRV

59BE3110 • 59BEFFF5
v STORIOA
59BE4100
59BE3110
Failing Item:
v SIP3152
Failing Item:
v SASCABL
v DISKDRV
v SASEXP
v STORIOA
v DEVBPLN
v SASCABL
v STORIOA
v SASEXP
v DISKDRV
59BE3130
59BE7000
level of support.
Failing Item:
59BE7001
v SVCDOCS
59BE34FF Response: If this event appears in a serviceable event

v DISKDRV
59BE4041
Explanation: Incomplete multipath connection. 59BE70DD
Response: Incomplete multipath connection between Explanation: System log entry only, no service action
device backplane and device. required.
Failing Item:
v SIP3146 59BEFFF3
Explanation: Multipath redundancy level reduced. v DISKDRV
failed. 59BEFFF4
Failing Item: Explanation: Disk device problem.
v SASCABL v DISKDRV
v SASEXP v STORIOA
59BE4061 59BEFFF5
Failing Item:

59BEFFF6 • 59BEFFFE
v DISKDRV
59BEFFFC
59BEFFF6
Failing Item:
v SIP3250
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
59BEFFF7
59BEFFFD
Failing Item:
Failing Item:
v DISKDRV
v SIP3250
v DISKDRV
59BEFFF9
v STORIOA
Response: If this event appears in a serviceable event 59BEFFFE
Failing Item:
Failing Item:
59BEFFFA
v SIP3150
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59BEFFFB

59C0102E • 59C034FF

59C0102E 59C03109
v DISKDRV v DISKDRV
v STORIOA
59C03002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59C03010 59C0310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59C03110
59C03020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59C03130
59C03029
Failing Item:
59C03100
v SVCDOCS
v STORIOA
v SASEXP

59C04041 • 59C0FFF9
59C04041 59C070DD
required.
59C0FFF3
Failing Item:
Failing Item:
59C04060 v DISKDRV
59C0FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59C0FFF5

v DISKDRV
Failing Item:
59C0FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59C07000
Explanation: Disk sector read error. 59C0FFF7

59C0FFF9
Failing Item:
v DISKDRV

59C0FFFA • 59C0FFFE

59C0FFFE
Failing Item:
59C0FFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59C0FFFB
59C0FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59C0FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59C2102E • 59C234FF

59C2102E 59C23109
v DISKDRV v DISKDRV
v STORIOA
59C23002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59C23010 59C2310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59C23110
59C23020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59C23130
59C23029
Failing Item:
59C23100
v SVCDOCS
v STORIOA
v SASEXP

59C24041 • 59C2FFF9
59C24041 59C270DD
required.
59C2FFF3
Failing Item:
Failing Item:
59C24060 v DISKDRV
59C2FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59C2FFF5

v DISKDRV
Failing Item:
59C2FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59C27000

59C2FFF9
Failing Item:
v DISKDRV


59C2FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59C2FFFB
59C2FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59C2FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59C3102E • 59C334FF

59C3102E 59C33109
v DISKDRV v DISKDRV
v STORIOA
59C33002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59C33010 59C3310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59C33110
59C33020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59C33130
59C33029
Failing Item:
59C33100
v SVCDOCS
v STORIOA
v SASEXP

59C34041 • 59C3FFF9
59C34041 59C370DD
required.
59C3FFF3
Failing Item:
Failing Item:
59C34060 v DISKDRV
59C3FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59C3FFF5

v DISKDRV
Failing Item:
59C3FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59C37000

59C3FFF9
Failing Item:
v DISKDRV


59C3FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59C3FFFB
59C3FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59C3FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59C8102E • 59C834FF

59C8102E 59C83109
v DISKDRV v DISKDRV
v STORIOA
59C83002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59C83010 59C8310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59C83110
59C83020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59C83130
59C83029
Failing Item:
59C83100
v SVCDOCS
v STORIOA
v SASEXP

59C84041 • 59C8FFF9
59C84041 59C870DD
required.
59C8FFF3
Failing Item:
Failing Item:
59C84060 v DISKDRV
59C8FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59C8FFF5

v DISKDRV
Failing Item:
59C8FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59C87000

59C8FFF9
Failing Item:
v DISKDRV


59C8FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59C8FFFB
59C8FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59C8FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59C9102E • 59C934FF

59C9102E 59C93109
v DISKDRV v DISKDRV
v STORIOA
59C93002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59C93010 59C9310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59C93110
59C93020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59C93130
59C93029
Failing Item:
59C93100
v SVCDOCS
v STORIOA
v SASEXP

59C94041 • 59C9FFF9
59C94041 59C970DD
required.
59C9FFF3
Failing Item:
Failing Item:
59C94060 v DISKDRV
59C9FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59C9FFF5

v DISKDRV
Failing Item:
59C9FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59C97000

59C9FFF9
Failing Item:
v DISKDRV


59C9FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59C9FFFB
59C9FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59C9FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59CC102E • 59CC34FF

59CC102E 59CC3109
v DISKDRV v DISKDRV
v STORIOA
59CC3002 v SASCABL
selection.
Failing Item: 59CC310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59CC3010 59CC310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59CC3110
59CC3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59CC3130
59CC3029
Failing Item:
59CC3100
v SVCDOCS
Failing Item: 59CC34FF
v STORIOA
v SASEXP

59CC4041 • 59CCFFF9
59CC4041 59CC70DD
required.
59CCFFF3
Failing Item:
Failing Item:
59CC4060 v DISKDRV
59CCFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59CCFFF5
59CC4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
59CCFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59CC7000
Explanation: Disk sector read error. 59CCFFF7
59CC7001 event does not appear in a serviceable event view, no

59CCFFF9
Failing Item:
v DISKDRV

59CCFFFA • 59CCFFFE

59CCFFFE
Failing Item:
59CCFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59CCFFFB
59CCFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59CCFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59CD102E • 59CD34FF
(59CD) Reference codes

59CD102E 59CD3109
v DISKDRV v DISKDRV
v STORIOA
59CD3002 v SASCABL
selection.
Failing Item: 59CD310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59CD3010 59CD310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59CD3110
59CD3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59CD3130
59CD3029
Failing Item:
59CD3100
v SVCDOCS
Failing Item: 59CD34FF
v STORIOA
v SASEXP

59CD4041 • 59CDFFF9
59CD4041 59CD70DD
required.
59CDFFF3
Failing Item:
Failing Item:
59CD4060 v DISKDRV
59CDFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59CDFFF5
59CD4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
59CDFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59CD7000
Explanation: Disk sector read error. 59CDFFF7
59CD7001 event does not appear in a serviceable event view, no

59CDFFF9
Failing Item:
v DISKDRV

59CDFFFA • 59CDFFFE

59CDFFFE
Failing Item:
59CDFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59CDFFFB
59CDFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59CDFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59CE102E • 59CE34FF
(59CE) Reference codes

59CE102E 59CE3109
v DISKDRV v DISKDRV
v STORIOA
59CE3002 v SASCABL
selection.
Failing Item: 59CE310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59CE3010 59CE310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59CE3110
59CE3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59CE3130
59CE3029
Failing Item:
59CE3100
v SVCDOCS
Failing Item: 59CE34FF
v STORIOA
v SASEXP

59CE4041 • 59CEFFF9
59CE4041 59CE70DD
required.
59CEFFF3
Failing Item:
Failing Item:
59CE4060 v DISKDRV
59CEFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59CEFFF5
59CE4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
59CEFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59CE7000
Explanation: Disk sector read error. 59CEFFF7
59CE7001 event does not appear in a serviceable event view, no

59CEFFF9
Failing Item:
v DISKDRV

59CEFFFA • 59CEFFFE

59CEFFFE
Failing Item:
59CEFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59CEFFFB
59CEFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59CEFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59CF102E • 59CF34FF
(59CF) Reference codes

59CF102E 59CF3109
v DISKDRV v DISKDRV
v STORIOA
59CF3002 v SASCABL
selection.
Failing Item: 59CF310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59CF3010 59CF310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59CF3110
59CF3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59CF3130
59CF3029
Failing Item:
59CF3100
v SVCDOCS
Failing Item: 59CF34FF
v STORIOA
v SASEXP

59CF4041 • 59CFFFF9
59CF4041 59CF70DD
required.
59CFFFF3
Failing Item:
Failing Item:
59CF4060 v DISKDRV
59CFFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59CFFFF5
59CF4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
59CFFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59CF7000
Explanation: Disk sector read error. 59CFFFF7
59CF7001 event does not appear in a serviceable event view, no

59CFFFF9
Failing Item:
v DISKDRV

59CFFFFA • 59CFFFFE

59CFFFFE
Failing Item:
59CFFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59CFFFFB
59CFFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59CFFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59D0102E • 59D034FF

59D0102E 59D03109
v DISKDRV v DISKDRV
v STORIOA
59D03002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59D03010 59D0310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59D03110
59D03020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59D03130
59D03029
Failing Item:
59D03100
v SVCDOCS
v STORIOA
v SASEXP

59D04041 • 59D0FFF9
59D04041 59D070DD
required.
59D0FFF3
Failing Item:
Failing Item:
59D04060 v DISKDRV
59D0FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59D0FFF5

v DISKDRV
Failing Item:
59D0FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59D07000
Explanation: Disk sector read error. 59D0FFF7

59D0FFF9
Failing Item:
v DISKDRV

59D0FFFA • 59D0FFFE

59D0FFFE
Failing Item:
59D0FFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59D0FFFB
59D0FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59D0FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59D2102E • 59D234FF

59D2102E 59D23109
v DISKDRV v DISKDRV
v STORIOA
59D23002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59D23010 59D2310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59D23110
59D23020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59D23130
59D23029
Failing Item:
59D23100
v SVCDOCS
v STORIOA
v SASEXP

59D24041 • 59D2FFF9
59D24041 59D270DD
required.
59D2FFF3
Failing Item:
Failing Item:
59D24060 v DISKDRV
59D2FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59D2FFF5

v DISKDRV
Failing Item:
59D2FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59D27000

59D2FFF9
Failing Item:
v DISKDRV


59D2FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59D2FFFB
59D2FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59D2FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59D3102E • 59D334FF

59D3102E 59D33109
v DISKDRV v DISKDRV
v STORIOA
59D33002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59D33010 59D3310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59D33110
59D33020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59D33130
59D33029
Failing Item:
59D33100
v SVCDOCS
v STORIOA
v SASEXP

59D34041 • 59D3FFF9
59D34041 59D370DD
required.
59D3FFF3
Failing Item:
Failing Item:
59D34060 v DISKDRV
59D3FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59D3FFF5

v DISKDRV
Failing Item:
59D3FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59D37000

59D3FFF9
Failing Item:
v DISKDRV


59D3FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59D3FFFB
59D3FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59D3FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59D8102E • 59D834FF

59D8102E 59D83109
v DISKDRV v DISKDRV
v STORIOA
59D83002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59D83010 59D8310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59D83110
59D83020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59D83130
59D83029
Failing Item:
59D83100
v SVCDOCS
v STORIOA
v SASEXP

59D84041 • 59D8FFF9
59D84041 59D870DD
required.
59D8FFF3
Failing Item:
Failing Item:
59D84060 v DISKDRV
59D8FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59D8FFF5

v DISKDRV
Failing Item:
59D8FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59D87000

59D8FFF9
Failing Item:
v DISKDRV


59D8FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59D8FFFB
59D8FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59D8FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59DA102E • 59DA34FF
(59DA) Reference codes

59DA102E 59DA3109
v DISKDRV v DISKDRV
v STORIOA
59DA3002 v SASCABL
selection.
Failing Item: 59DA310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59DA3010 59DA310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59DA3110
59DA3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59DA3130
59DA3029
Failing Item:
59DA3100
v SVCDOCS
Failing Item: 59DA34FF
v STORIOA
v SASEXP

59DA4041 • 59DAFFF9
59DA4041 59DA70DD
required.
59DAFFF3
Failing Item:
Failing Item:
59DA4060 v DISKDRV
59DAFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59DAFFF5
59DA4061 Explanation: Disk sector read error.
59DA4100 Failing Item:

v DISKDRV
Failing Item:
59DAFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59DA7000
Explanation: Disk sector read error. 59DAFFF7
59DA7001 event does not appear in a serviceable event view, no

59DAFFF9
Failing Item:
v DISKDRV

59DAFFFA • 59DAFFFE

59DAFFFE
Failing Item:
59DAFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59DAFFFB
59DAFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59DAFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59DB102E • 59DB34FF
(59DB) Reference codes

59DB102E 59DB3109
v DISKDRV v DISKDRV
v STORIOA
59DB3002 v SASCABL
selection.
Failing Item: 59DB310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59DB3010 59DB310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59DB3110
59DB3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59DB3130
59DB3029
Failing Item:
59DB3100
v SVCDOCS
Failing Item: 59DB34FF
v STORIOA
v SASEXP

59DB4041 • 59DBFFF9
59DB4041 59DB70DD
required.
59DBFFF3
Failing Item:
Failing Item:
59DB4060 v DISKDRV
59DBFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59DBFFF5
59DB4061 Explanation: Disk sector read error.
59DB4100 Failing Item:

v DISKDRV
Failing Item:
59DBFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59DB7000
Explanation: Disk sector read error. 59DBFFF7
59DB7001 event does not appear in a serviceable event view, no

59DBFFF9
Failing Item:
v DISKDRV

59DBFFFA • 59DBFFFE

59DBFFFE
Failing Item:
59DBFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59DBFFFB
59DBFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59DBFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59DD102E • 59DD34FF
(59DD) Reference codes

59DD102E 59DD3109
v DISKDRV v DISKDRV
v STORIOA
59DD3002 v SASCABL
selection.
Failing Item: 59DD310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59DD3010 59DD310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59DD3110
59DD3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59DD3130
59DD3029
Failing Item:
59DD3100
v SVCDOCS
Failing Item: 59DD34FF
v STORIOA
v SASEXP

59DD4041 • 59DDFFF9
59DD4041 59DD70DD
required.
59DDFFF3
Failing Item:
Failing Item:
59DD4060 v DISKDRV
59DDFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59DDFFF5
59DD4061 Explanation: Disk sector read error.
59DD4100 Failing Item:

v DISKDRV
Failing Item:
59DDFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59DD7000
Explanation: Disk sector read error. 59DDFFF7
59DD7001 event does not appear in a serviceable event view, no

59DDFFF9
Failing Item:
v DISKDRV

59DDFFFA • 59DDFFFE

59DDFFFE
Failing Item:
59DDFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59DDFFFB
59DDFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59DDFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59DE102E • 59DE34FF
(59DE) Reference codes

59DE102E 59DE3109
v DISKDRV v DISKDRV
v STORIOA
59DE3002 v SASCABL
selection.
Failing Item: 59DE310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59DE3010 59DE310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59DE3110
59DE3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59DE3130
59DE3029
Failing Item:
59DE3100
v SVCDOCS
Failing Item: 59DE34FF
v STORIOA
v SASEXP

59DE4041 • 59DEFFF9
59DE4041 59DE70DD
required.
59DEFFF3
Failing Item:
Failing Item:
59DE4060 v DISKDRV
59DEFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59DEFFF5
59DE4061 Explanation: Disk sector read error.
59DE4100 Failing Item:

v DISKDRV
Failing Item:
59DEFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59DE7000
Explanation: Disk sector read error. 59DEFFF7
59DE7001 event does not appear in a serviceable event view, no

59DEFFF9
Failing Item:
v DISKDRV

59DEFFFA • 59DEFFFE

59DEFFFE
Failing Item:
59DEFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59DEFFFB
59DEFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59DEFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59E0102E • 59E034FF
(59E0) Reference codes

59E0102E 59E03109
v DISKDRV v DISKDRV
v STORIOA
59E03002 v SASCABL
selection.
Failing Item: 59E0310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59E03010 59E0310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59E03110
59E03020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59E03130
59E03029
Failing Item:
59E03100
v SVCDOCS
Failing Item: 59E034FF
v STORIOA
v SASEXP

59E04041 • 59E0FFF9
59E04041 59E070DD
required.
59E0FFF3
Failing Item:
Failing Item:
59E04060 v DISKDRV
59E0FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59E0FFF5
59E04061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
59E0FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59E07000
Explanation: Disk sector read error. 59E0FFF7
59E07001 event does not appear in a serviceable event view, no

59E0FFF9
Failing Item:
v DISKDRV

59E0FFFA • 59E0FFFE

59E0FFFE
Failing Item:
59E0FFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59E0FFFB
59E0FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59E0FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59E1102E • 59E134FF

59E1102E 59E13109
v DISKDRV v DISKDRV
v STORIOA
59E13002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59E13010 59E1310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59E13110
59E13020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59E13130
59E13029
Failing Item:
59E13100
v SVCDOCS
v STORIOA
v SASEXP

59E14041 • 59E1FFF9
59E14041 59E170DD
required.
59E1FFF3
Failing Item:
Failing Item:
59E14060 v DISKDRV
59E1FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59E1FFF5

v DISKDRV
Failing Item:
59E1FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59E17000

59E1FFF9
Failing Item:
v DISKDRV


59E1FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59E1FFFB
59E1FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59E1FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59E4102E • 59E434FF

59E4102E 59E43109
v DISKDRV v DISKDRV
v STORIOA
59E43002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59E43010 59E4310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59E43110
59E43020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59E43130
59E43029
Failing Item:
59E43100
v SVCDOCS
v STORIOA
v SASEXP

59E44041 • 59E4FFF9
59E44041 59E470DD
required.
59E4FFF3
Failing Item:
Failing Item:
59E44060 v DISKDRV
59E4FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59E4FFF5

v DISKDRV
Failing Item:
59E4FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59E47000

59E4FFF9
Failing Item:
v DISKDRV


59E4FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59E4FFFB
59E4FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59E4FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59E5102E • 59E534FF

59E5102E 59E53109
v DISKDRV v DISKDRV
v STORIOA
59E53002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59E53010 59E5310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59E53110
59E53020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59E53130
59E53029
Failing Item:
59E53100
v SVCDOCS
v STORIOA
v SASEXP

59E54041 • 59E5FFF9
59E54041 59E570DD
required.
59E5FFF3
Failing Item:
Failing Item:
59E54060 v DISKDRV
59E5FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59E5FFF5

v DISKDRV
Failing Item:
59E5FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59E57000

59E5FFF9
Failing Item:
v DISKDRV


59E5FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59E5FFFB
59E5FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59E5FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59E6102E • 59E634FF

59E6102E 59E63109
v DISKDRV v DISKDRV
v STORIOA
59E63002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59E63010 59E6310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59E63110
59E63020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59E63130
59E63029
Failing Item:
59E63100
v SVCDOCS
v STORIOA
v SASEXP

59E64041 • 59E6FFF9
59E64041 59E670DD
required.
59E6FFF3
Failing Item:
Failing Item:
59E64060 v DISKDRV
59E6FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59E6FFF5

v DISKDRV
Failing Item:
59E6FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59E67000

59E6FFF9
Failing Item:
v DISKDRV


59E6FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59E6FFFB
59E6FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59E6FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59E8102E • 59E834FF

59E8102E 59E83109
v DISKDRV v DISKDRV
v STORIOA
59E83002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59E83010 59E8310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59E83110
59E83020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59E83130
59E83029
Failing Item:
59E83100
v SVCDOCS
v STORIOA
v SASEXP

59E84041 • 59E8FFF9
59E84041 59E870DD
required.
59E8FFF3
Failing Item:
Failing Item:
59E84060 v DISKDRV
59E8FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59E8FFF5

v DISKDRV
Failing Item:
59E8FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59E87000

59E8FFF9
Failing Item:
v DISKDRV


59E8FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59E8FFFB
59E8FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59E8FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59E9102E • 59E934FF

59E9102E 59E93109
v DISKDRV v DISKDRV
v STORIOA
59E93002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59E93010 59E9310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59E93110
59E93020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59E93130
59E93029
Failing Item:
59E93100
v SVCDOCS
v STORIOA
v SASEXP

59E94041 • 59E9FFF9
59E94041 59E970DD
required.
59E9FFF3
Failing Item:
Failing Item:
59E94060 v DISKDRV
59E9FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59E9FFF5

v DISKDRV
Failing Item:
59E9FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59E97000

59E9FFF9
Failing Item:
v DISKDRV


59E9FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59E9FFFB
59E9FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59E9FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59EA102E • 59EA34FF
(59EA) Reference codes

59EA102E 59EA3109
v DISKDRV v DISKDRV
v STORIOA
59EA3002 v SASCABL
selection.
Failing Item: 59EA310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59EA3010 59EA310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59EA3110
59EA3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59EA3130
59EA3029
Failing Item:
59EA3100
v SVCDOCS
Failing Item: 59EA34FF
v STORIOA
v SASEXP

59EA4041 • 59EAFFF9
59EA4041 59EA70DD
required.
59EAFFF3
Failing Item:
Failing Item:
59EA4060 v DISKDRV
59EAFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59EAFFF5
59EA4061 Explanation: Disk sector read error.
59EA4100 Failing Item:

v DISKDRV
Failing Item:
59EAFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59EA7000
Explanation: Disk sector read error. 59EAFFF7
59EA7001 event does not appear in a serviceable event view, no

59EAFFF9
Failing Item:
v DISKDRV

59EAFFFA • 59EAFFFE

59EAFFFE
Failing Item:
59EAFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59EAFFFB
59EAFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59EAFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59EB102E • 59EB34FF
(59EB) Reference codes

59EB102E 59EB3109
v DISKDRV v DISKDRV
v STORIOA
59EB3002 v SASCABL
selection.
Failing Item: 59EB310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59EB3010 59EB310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59EB3110
59EB3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59EB3130
59EB3029
Failing Item:
59EB3100
v SVCDOCS
Failing Item: 59EB34FF
v STORIOA
v SASEXP

59EB4041 • 59EBFFF9
59EB4041 59EB70DD
required.
59EBFFF3
Failing Item:
Failing Item:
59EB4060 v DISKDRV
59EBFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59EBFFF5
59EB4061 Explanation: Disk sector read error.
59EB4100 Failing Item:

v DISKDRV
Failing Item:
59EBFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59EB7000
Explanation: Disk sector read error. 59EBFFF7
59EB7001 event does not appear in a serviceable event view, no

59EBFFF9
Failing Item:
v DISKDRV

59EBFFFA • 59EBFFFE

59EBFFFE
Failing Item:
59EBFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59EBFFFB
59EBFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59EBFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59F6102E • 59F634FF

59F6102E 59F63109
v DISKDRV v DISKDRV
v STORIOA
59F63002 v SASCABL
selection.
Failing Item: 59F6310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59F63010 59F6310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59F63110
59F63020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59F63130
59F63029
Failing Item:
59F63100
v SVCDOCS
Failing Item: 59F634FF
v STORIOA
v SASEXP

59F64041 • 59F6FFF9
59F64041 59F670DD
required.
59F6FFF3
Failing Item:
Failing Item:
59F64060 v DISKDRV
59F6FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59F6FFF5
59F64061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
59F6FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59F67000
Explanation: Disk sector read error. 59F6FFF7
59F67001 event does not appear in a serviceable event view, no

59F6FFF9
Failing Item:
v DISKDRV

59F6FFFA • 59F6FFFE

59F6FFFE
Failing Item:
59F6FFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59F6FFFB
59F6FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59F6FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59F7102E • 59F734FF

59F7102E 59F73109
v DISKDRV v DISKDRV
v STORIOA
59F73002 v SASCABL
selection.
Failing Item: 59F7310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59F73010 59F7310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59F73110
59F73020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59F73130
59F73029
Failing Item:
59F73100
v SVCDOCS
Failing Item: 59F734FF
v STORIOA
v SASEXP

59F74041 • 59F7FFF9
59F74041 59F770DD
required.
59F7FFF3
Failing Item:
Failing Item:
59F74060 v DISKDRV
59F7FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59F7FFF5
59F74061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
59F7FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59F77000
Explanation: Disk sector read error. 59F7FFF7
59F77001 event does not appear in a serviceable event view, no

59F7FFF9
Failing Item:
v DISKDRV

59F7FFFA • 59F7FFFE

59F7FFFE
Failing Item:
59F7FFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59F7FFFB
59F7FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59F7FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59FC102E • 59FC34FF
(59FC) Reference codes

59FC102E 59FC3109
v DISKDRV v DISKDRV
v STORIOA
59FC3002 v SASCABL
selection.
Failing Item: 59FC310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59FC3010 59FC310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59FC3110
59FC3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59FC3130
59FC3029
Failing Item:
59FC3100
v SVCDOCS
Failing Item: 59FC34FF
v STORIOA
v SASEXP

59FC4041 • 59FCFFF9
59FC4041 59FC70DD
required.
59FCFFF3
Failing Item:
Failing Item:
59FC4060 v DISKDRV
59FCFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59FCFFF5
59FC4061 Explanation: Disk sector read error.
59FC4100 Failing Item:

v DISKDRV
Failing Item:
59FCFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59FC7000
Explanation: Disk sector read error. 59FCFFF7
59FC7001 event does not appear in a serviceable event view, no

59FCFFF9
Failing Item:
v DISKDRV

59FCFFFA • 59FCFFFE

59FCFFFE
Failing Item:
59FCFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59FCFFFB
59FCFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59FCFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

59FD102E • 59FD34FF
(59FD) Reference codes

59FD102E 59FD3109
v DISKDRV v DISKDRV
v STORIOA
59FD3002 v SASCABL
selection.
Failing Item: 59FD310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
59FD3010 59FD310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
59FD3110
59FD3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
59FD3130
59FD3029
Failing Item:
59FD3100
v SVCDOCS
Failing Item: 59FD34FF
v STORIOA
v SASEXP

59FD4041 • 59FDFFF9
59FD4041 59FD70DD
required.
59FDFFF3
Failing Item:
Failing Item:
59FD4060 v DISKDRV
59FDFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
59FDFFF5
59FD4061 Explanation: Disk sector read error.
59FD4100 Failing Item:

v DISKDRV
Failing Item:
59FDFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
59FD7000
Explanation: Disk sector read error. 59FDFFF7
59FD7001 event does not appear in a serviceable event view, no

59FDFFF9
Failing Item:
v DISKDRV

59FDFFFA • 59FDFFFE

59FDFFFE
Failing Item:
59FDFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
59FDFFFB
59FDFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
59FDFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B0E102E • 5B0E34FF
(5B0E) Reference codes

5B0E102E 5B0E3109
v DISKDRV v DISKDRV
v STORIOA
5B0E3002 v SASCABL
selection.
Failing Item: 5B0E310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B0E3010 5B0E310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B0E3110
5B0E3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B0E3130
5B0E3029
Failing Item:
5B0E3100
v SVCDOCS
Failing Item: 5B0E34FF
v STORIOA
v SASEXP

5B0E4041 • 5B0EFFF9
5B0E4041 5B0E70DD
required.
5B0EFFF3
Failing Item:
Failing Item:
5B0E4060 v DISKDRV
5B0EFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B0EFFF5
5B0E4061 Explanation: Disk sector read error.
5B0E4100 Failing Item:

v DISKDRV
Failing Item:
5B0EFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B0E7000
Explanation: Disk sector read error. 5B0EFFF7
5B0E7001 event does not appear in a serviceable event view, no

5B0EFFF9
Failing Item:
v DISKDRV

5B0EFFFA • 5B0EFFFE

5B0EFFFE
Failing Item:
5B0EFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B0EFFFB
5B0EFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B0EFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B0F102E • 5B0F34FF
(5B0F) Reference codes

5B0F102E 5B0F3109
v DISKDRV v DISKDRV
v STORIOA
5B0F3002 v SASCABL
selection.
Failing Item: 5B0F310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B0F3010 5B0F310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B0F3110
5B0F3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B0F3130
5B0F3029
Failing Item:
5B0F3100
v SVCDOCS
Failing Item: 5B0F34FF
v STORIOA
v SASEXP

5B0F4041 • 5B0FFFF9
5B0F4041 5B0F70DD
required.
5B0FFFF3
Failing Item:
Failing Item:
5B0F4060 v DISKDRV
5B0FFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B0FFFF5
5B0F4061 Explanation: Disk sector read error.
5B0F4100 Failing Item:

v DISKDRV
Failing Item:
5B0FFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B0F7000
Explanation: Disk sector read error. 5B0FFFF7
5B0F7001 event does not appear in a serviceable event view, no

5B0FFFF9
Failing Item:
v DISKDRV

5B0FFFFA • 5B0FFFFE

5B0FFFFE
Failing Item:
5B0FFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B0FFFFB
5B0FFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B0FFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B10102E • 5B1034FF

5B10102E 5B103109
v DISKDRV v DISKDRV
v STORIOA
5B103002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B103010 5B10310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B103110
5B103020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B103130
5B103029
Failing Item:
5B103100
v SVCDOCS
v STORIOA
v SASEXP

5B104041 • 5B10FFF9
5B104041 5B1070DD
required.
5B10FFF3
Failing Item:
Failing Item:
5B104060 v DISKDRV
5B10FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B10FFF5

v DISKDRV
Failing Item:
5B10FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B107000

5B10FFF9
Failing Item:
v DISKDRV


5B10FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B10FFFB
5B10FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B10FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B11102E • 5B1134FF

5B11102E 5B113109
v DISKDRV v DISKDRV
v STORIOA
5B113002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B113010 5B11310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B113110
5B113020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B113130
5B113029
Failing Item:
5B113100
v SVCDOCS
v STORIOA
v SASEXP

5B114041 • 5B11FFF9
5B114041 5B1170DD
required.
5B11FFF3
Failing Item:
Failing Item:
5B114060 v DISKDRV
5B11FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B11FFF5

v DISKDRV
Failing Item:
5B11FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B117000

5B11FFF9
Failing Item:
v DISKDRV


5B11FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B11FFFB
5B11FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B11FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B12102E • 5B1234FF

5B12102E 5B123109
v DISKDRV v DISKDRV
v STORIOA
5B123002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B123010 5B12310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B123110
5B123020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B123130
5B123029
Failing Item:
5B123100
v SVCDOCS
v STORIOA
v SASEXP

5B124041 • 5B12FFF9
5B124041 5B1270DD
required.
5B12FFF3
Failing Item:
Failing Item:
5B124060 v DISKDRV
5B12FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B12FFF5

v DISKDRV
Failing Item:
5B12FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B127000

5B12FFF9
Failing Item:
v DISKDRV


5B12FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B12FFFB
5B12FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B12FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B13102E • 5B1334FF

5B13102E 5B133109
v DISKDRV v DISKDRV
v STORIOA
5B133002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B133010 5B13310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B133110
5B133020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B133130
5B133029
Failing Item:
5B133100
v SVCDOCS
v STORIOA
v SASEXP

5B134041 • 5B13FFF9
5B134041 5B1370DD
required.
5B13FFF3
Failing Item:
Failing Item:
5B134060 v DISKDRV
5B13FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B13FFF5

v DISKDRV
Failing Item:
5B13FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B137000

5B13FFF9
Failing Item:
v DISKDRV


5B13FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B13FFFB
5B13FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B13FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B14102E • 5B1434FF

5B14102E 5B143109
v DISKDRV v DISKDRV
v STORIOA
5B143002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B143010 5B14310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B143110
5B143020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B143130
5B143029
Failing Item:
5B143100
v SVCDOCS
v STORIOA
v SASEXP

5B144041 • 5B14FFF9
5B144041 5B1470DD
required.
5B14FFF3
Failing Item:
Failing Item:
5B144060 v DISKDRV
5B14FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B14FFF5

v DISKDRV
Failing Item:
5B14FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B147000

5B14FFF9
Failing Item:
v DISKDRV


5B14FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B14FFFB
5B14FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B14FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B15102E • 5B1534FF

5B15102E 5B153109
v DISKDRV v DISKDRV
v STORIOA
5B153002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B153010 5B15310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B153110
5B153020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B153130
5B153029
Failing Item:
5B153100
v SVCDOCS
v STORIOA
v SASEXP

5B154041 • 5B15FFF9
5B154041 5B1570DD
required.
5B15FFF3
Failing Item:
Failing Item:
5B154060 v DISKDRV
5B15FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B15FFF5

v DISKDRV
Failing Item:
5B15FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B157000

5B15FFF9
Failing Item:
v DISKDRV


5B15FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B15FFFB
5B15FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B15FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B16102E • 5B1634FF

5B16102E 5B163109
v DISKDRV v DISKDRV
v STORIOA
5B163002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B163010 5B16310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B163110
5B163020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B163130
5B163029
Failing Item:
5B163100
v SVCDOCS
v STORIOA
v SASEXP

5B164041 • 5B16FFF9
5B164041 5B1670DD
required.
5B16FFF3
Failing Item:
Failing Item:
5B164060 v DISKDRV
5B16FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B16FFF5

v DISKDRV
Failing Item:
5B16FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B167000

5B16FFF9
Failing Item:
v DISKDRV


5B16FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B16FFFB
5B16FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B16FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B17102E • 5B1734FF

5B17102E 5B173109
v DISKDRV v DISKDRV
v STORIOA
5B173002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B173010 5B17310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B173110
5B173020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B173130
5B173029
Failing Item:
5B173100
v SVCDOCS
v STORIOA
v SASEXP

5B174041 • 5B17FFF9
5B174041 5B1770DD
required.
5B17FFF3
Failing Item:
Failing Item:
5B174060 v DISKDRV
5B17FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B17FFF5

v DISKDRV
Failing Item:
5B17FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B177000

5B17FFF9
Failing Item:
v DISKDRV


5B17FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B17FFFB
5B17FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B17FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B18102E • 5B1834FF

5B18102E 5B183109
v DISKDRV v DISKDRV
v STORIOA
5B183002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B183010 5B18310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B183110
5B183020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B183130
5B183029
Failing Item:
5B183100
v SVCDOCS
v STORIOA
v SASEXP

5B184041 • 5B18FFF9
5B184041 5B1870DD
required.
5B18FFF3
Failing Item:
Failing Item:
5B184060 v DISKDRV
5B18FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B18FFF5

v DISKDRV
Failing Item:
5B18FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B187000

5B18FFF9
Failing Item:
v DISKDRV


5B18FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B18FFFB
5B18FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B18FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B19102E • 5B1934FF

5B19102E 5B193109
v DISKDRV v DISKDRV
v STORIOA
5B193002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B193010 5B19310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B193110
5B193020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B193130
5B193029
Failing Item:
5B193100
v SVCDOCS
v STORIOA
v SASEXP

5B194041 • 5B19FFF9
5B194041 5B1970DD
required.
5B19FFF3
Failing Item:
Failing Item:
5B194060 v DISKDRV
5B19FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B19FFF5

v DISKDRV
Failing Item:
5B19FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B197000

5B19FFF9
Failing Item:
v DISKDRV


5B19FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B19FFFB
5B19FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B19FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B1A102E • 5B1A34FF
(5B1A) Reference codes

5B1A102E 5B1A3109
v DISKDRV v DISKDRV
v STORIOA
5B1A3002 v SASCABL
selection.
Failing Item: 5B1A310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B1A3010 5B1A310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B1A3110
5B1A3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B1A3130
5B1A3029
Failing Item:
5B1A3100
v SVCDOCS
Failing Item: 5B1A34FF
v STORIOA
v SASEXP

5B1A4041 • 5B1AFFF9
5B1A4041 5B1A70DD
required.
5B1AFFF3
Failing Item:
Failing Item:
5B1A4060 v DISKDRV
5B1AFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B1AFFF5
5B1A4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
5B1AFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B1A7000
Explanation: Disk sector read error. 5B1AFFF7
5B1A7001 event does not appear in a serviceable event view, no

5B1AFFF9
Failing Item:
v DISKDRV

5B1AFFFA • 5B1AFFFE

5B1AFFFE
Failing Item:
5B1AFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B1AFFFB
5B1AFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B1AFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B1B102E • 5B1B34FF

5B1B102E 5B1B3109
v DISKDRV v DISKDRV
v STORIOA
5B1B3002 v SASCABL
selection.
Failing Item: 5B1B310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B1B3010 5B1B310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B1B3110
5B1B3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B1B3130
5B1B3029
Failing Item:
5B1B3100
v SVCDOCS
Failing Item: 5B1B34FF
v STORIOA
v SASEXP

5B1B4041 • 5B1BFFF9
5B1B4041 5B1B70DD
required.
5B1BFFF3
Failing Item:
Failing Item:
5B1B4060 v DISKDRV
5B1BFFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B1BFFF5
5B1B4061 Explanation: Disk sector read error.

v DISKDRV
Failing Item:
5B1BFFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B1B7000
Explanation: Disk sector read error. 5B1BFFF7
5B1B7001 event does not appear in a serviceable event view, no

5B1BFFF9
Failing Item:
v DISKDRV

5B1BFFFA • 5B1BFFFE

5B1BFFFE
Failing Item:
5B1BFFFA service action is required.
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B1BFFFB
5B1BFFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B1BFFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B20102E • 5B2034FF

5B20102E 5B203109
v DISKDRV v DISKDRV
v STORIOA
5B203002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B203010 5B20310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B203110
5B203020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B203130
5B203029
Failing Item:
5B203100
v SVCDOCS
v STORIOA
v SASEXP

5B204041 • 5B20FFF6
5B204041 5B2070DD
required.
5B20FFF3
Failing Item:
Failing Item:
5B204060 v DISKDRV
5B20FFF4
failed. Explanation: Read Intensive (RI) SSD status change or
device problem.
Failing Item:
v SIP3153 Problem determination: The RI SSD may be reporting
a status change in the number of write operations it
v SASCABL
supports. The device may have reached the limit for
v SASEXP the number of write operations the device supports.
Perform the steps in symbolic FRU RI_SSD to
5B204061 determine if this SRC is a status change or a drive
failure.
Failing Item:
Response: A redundant disk unit connection has been v RI_SSD
v DISKDRV
v STORIOA
5B204100
Explanation: Device bus fabric error. 5B20FFF5
v SIP3152
v DISKDRV v DISKDRV
5B207000 5B20FFF6
Explanation: Disk sector read error. Explanation: Read Intensive (RI) SSD status change or
device problem.
logged for information only. Response: If this event appears in a serviceable event
view, work with the failing item list found there to
determine the part number and location of the RI SSD.
5B207001
If this event does not appear in a serviceable event
Explanation: Temporary disk data error. view, no service action is required.
Response: If this event appears in a serviceable event Problem determination: The RI SSD may be reporting
view, work with the failing item list found there. If this a status change in the number of write operations it
event does not appear in a serviceable event view, no supports. The device may be nearing the limit for the
service action is required. number of write operations the device supports.
Failing Item:
determine if this SRC is a status change or a drive
v DISKDRV problem.
Failing Item:
v RI_SSD

5B20FFF7 • 5B213010

5B20FFF7
5B20FFFC
Failing Item:
v SIP3250
5B20FFF9 v DISKDRV
v STORIOA
5B20FFFD
event does not appear in a serviceable event view, no Explanation: Soft device bus error.
5B20FFFA Failing Item:

v SIP3250
v DISKDRV
v STORIOA
service action is required. 5B20FFFE
v SASEXP
Failing Item:
5B20FFFB v SIP3150

v DEVBPLN
5B21102E
v SASCABL
v SASEXP
Failing Item:
v DISKDRV 5B213010
5B213002 IOA.
Explanation: Addressed device failed to respond to Failing Item:
selection.
v DISKDRV
v DISKDRV v SASCABL
v STORIOA v SASEXP

5B213020 • 5B214061
5B213020 5B213110
Explanation: Replacement device is not supported. Explanation: Device bus interface error occurred.
v DISKDRV v DISKDRV
v STORIOA v STORIOA
v SASCABL v SASCABL
v SASEXP
5B213029
Explanation: A device replacement has occurred. 5B213130
Response: No action required. This reference code is Explanation: Device Licensed Internal Code.
logged for information only. Response: The device is not supported with the level
5B213100 level of support.
Explanation: Device bus interface error occurred. Failing Item:

v SVCDOCS
Failing Item:
v DISKDRV
5B2134FF
v STORIOA
v SASCABL Explanation: Format in progress.
v SASEXP Response: No action required. This reference code is
5B213109
5B214041
Failing Item:
v DISKDRV Response: Incomplete multipath connection between
v STORIOA
v SASEXP v SIP3146
5B21310C 5B214060
Explanation: Device bus error. Explanation: Multipath redundancy level reduced.
Failing Item: Response: A redundant disk unit connection has

failed.
v SIP3250
v STORIOA v SIP3153
v SASCABL
5B21310D v SASEXP

5B214061
Failing Item:
v SIP3250
v DISKDRV Response: A redundant disk unit connection has been
v STORIOA

5B214100 • 5B21FFF9
5B214100 5B21FFF5
Explanation: Device bus fabric error. Explanation: Disk sector read error.
v SASCABL
v SASEXP
Failing Item:
v DEVBPLN
v DISKDRV
v STORIOA
v DISKDRV
5B21FFF6
5B217000 Explanation: Read Intensive (RI) SSD status change or

device problem.
Response: No action required. This reference code is view, work with the failing item list found there to
logged for information only. determine the part number and location of the RI SSD.
5B217001 view, no service action is required.
Explanation: Temporary disk data error. Problem determination: The RI SSD may be reporting
Response: If this event appears in a serviceable event supports. The device may be nearing the limit for the
view, work with the failing item list found there. If this number of write operations the device supports.
event does not appear in a serviceable event view, no Perform the steps in symbolic FRU RI_SSD to
service action is required. determine if this SRC is a status change or a drive
problem.
Failing Item:
v RI_SSD
5B2170DD v DISKDRV

required. 5B21FFF7
5B21FFF3 Response: If this event appears in a serviceable event
Explanation: Disk media format not valid. view, work with the failing item list found there. If this
v DISKDRV
Failing Item:
v DISKDRV
5B21FFF4
Explanation: Read Intensive (RI) SSD status change or 5B21FFF9
device problem.
Problem determination: The RI SSD may be reporting
a status change in the number of write operations it Response: If this event appears in a serviceable event
supports. The device may have reached the limit for view, work with the failing item list found there. If this
the number of write operations the device supports. event does not appear in a serviceable event view, no
Perform the steps in symbolic FRU RI_SSD to service action is required.
determine if this SRC is a status change or a drive Failing Item:
failure.
v DISKDRV
Failing Item:
v RI_SSD
v DISKDRV
v STORIOA

5B21FFFA • 5B293100
v SIP3250
5B21FFFA
v DISKDRV
v STORIOA
5B21FFFD
v STORIOA
v SASCABL
Failing Item:
v SASEXP
v SIP3250
v DISKDRV
5B21FFFB
v STORIOA
Response: No action required. This reference code is 5B21FFFE
5B21FFFC Response: If this event appears in a serviceable event

Explanation: Soft device bus error. event does not appear in a serviceable event view, no
v SIP3150
Failing Item:

v STORIOA
5B29102E
v SASCABL
v SASEXP
Failing Item:
v DISKDRV 5B293020
5B293002
Failing Item:
v DISKDRV
selection.
v STORIOA
Failing Item:
v SASCABL
v DISKDRV
v STORIOA
5B293029
v DEVBPLN
v SASCABL
5B293010
5B293100
IOA. Explanation: Device bus interface error occurred.

v DISKDRV v DISKDRV

5B293109 • 5B297001
v STORIOA
5B294041
v SASCABL
v SASEXP
5B293109
Failing Item:
v SIP3146
Failing Item:
v DISKDRV
5B294060
v STORIOA
v SASCABL
failed.
5B29310C Failing Item:

v SIP3153
v SASCABL
Failing Item:
v SASEXP
v SIP3250
v DISKDRV
5B294061
v STORIOA
5B29310D Response: A redundant disk unit connection has been

v SIP3250
v DISKDRV
Failing Item:
v STORIOA
v SIP3152
v SASCABL
5B293110
v SASEXP
v DEVBPLN
v DISKDRV v DISKDRV
v STORIOA
v SASCABL 5B297000
v SASEXP
5B293130
Response: The device is not supported with the level 5B297001
level of support.
Failing Item:

5B2970DD • 5B29FFFC
v DISKDRV
5B2970DD
5B29FFF7
required.
v DISKDRV
5B29FFF4
Explanation: Read Intensive (RI) SSD status change or 5B29FFF9
device problem.
the number of write operations the device supports.
failure. v DISKDRV
Failing Item:
v RI_SSD 5B29FFFA
v STORIOA
5B29FFF5 event does not appear in a serviceable event view, no
Failing Item:
service action is required. v SASCABL
v DISKDRV
5B29FFFB
5B29FFF6 Explanation: SAS bus reset occurred.
Explanation: Read Intensive (RI) SSD status change or Response: No action required. This reference code is
device problem. logged for information only.
view, work with the failing item list found there to 5B29FFFC
If this event does not appear in a serviceable event Explanation: Soft device bus error.
view, no service action is required.
Problem determination: The RI SSD may be reporting view, work with the failing item list found there. If this
a status change in the number of write operations it event does not appear in a serviceable event view, no
supports. The device may be nearing the limit for the service action is required.
number of write operations the device supports.
Failing Item:
determine if this SRC is a status change or a drive v SIP3250
problem. v DISKDRV
v RI_SSD

5B29FFFD • 5B2B3110
5B29FFFD 5B29FFFE
v SIP3250 v SIP3150
v DISKDRV
v STORIOA

5B2B102E
5B2B3100
Failing Item:
v DISKDRV
Failing Item:
v DISKDRV
5B2B3002
v STORIOA
v SASCABL
selection.
v SASEXP
Failing Item:
v DISKDRV
5B2B3109
v STORIOA
v DEVBPLN
v SASEXP v DISKDRV
v STORIOA
5B2B3010 v SASCABL
v SASEXP
IOA.
5B2B310C
Failing Item:
v SASCABL v SIP3250
v SASEXP v DISKDRV
v STORIOA
5B2B3020
Explanation: Replacement device is not supported. 5B2B310D

v STORIOA v SIP3250
v SASCABL v DISKDRV
v STORIOA
5B2B3029
Explanation: A device replacement has occurred. 5B2B3110

5B2B3130 • 5B2BFFF5

v DISKDRV v STORIOA
v STORIOA v DISKDRV
v SASCABL
v SASEXP 5B2B7000
5B2B3130
of code currently on the system. Contact your next 5B2B7001
level of support.
Failing Item:
5B2B34FF service action is required.

v DISKDRV
5B2B70DD
5B2B4041 Explanation: System log entry only, no service action
required.
5B2BFFF3
Failing Item:
v DISKDRV
5B2B4060
5B2BFFF4
Explanation: Read Intensive (RI) SSD status change or
device problem.
failed.
Failing Item:
v SIP3153 supports. The device may have reached the limit for
v SASCABL the number of write operations the device supports.
v SASEXP Perform the steps in symbolic FRU RI_SSD to
failure.
5B2B4061
Failing Item:
Explanation: Multipath redundancy level increased. v RI_SSD
Response: A redundant disk unit connection has been v DISKDRV
5B2B4100 5B2BFFF5
v SASEXP

5B2BFFF6 • 5B2BFFFE

v DISKDRV
5B2BFFFB
5B2BFFF6 Explanation: SAS bus reset occurred.
Explanation: Read Intensive (RI) SSD status change or Response: No action required. This reference code is
device problem. logged for information only.
view, work with the failing item list found there to 5B2BFFFC
If this event does not appear in a serviceable event Explanation: Soft device bus error.
view, no service action is required. Response: If this event appears in a serviceable event
Problem determination: The RI SSD may be reporting view, work with the failing item list found there. If this
a status change in the number of write operations it event does not appear in a serviceable event view, no
supports. The device may be nearing the limit for the service action is required.
number of write operations the device supports. Failing Item:
determine if this SRC is a status change or a drive v SIP3250
problem. v DISKDRV
v RI_SSD
v DISKDRV 5B2BFFFD
5B2BFFF7 Response: If this event appears in a serviceable event
Explanation: Temporary disk data error. view, work with the failing item list found there. If this
service action is required. v SIP3250
v DISKDRV v STORIOA
5B2BFFF9 5B2BFFFE

v DISKDRV v SIP3150
5B2BFFFA
Failing Item:
v DISKDRV
v STORIOA
v SASCABL

5B2C102E • 5B2C34FF

5B2C102E 5B2C3109
v DISKDRV v DISKDRV
v STORIOA
5B2C3002 v SASCABL
selection.
Failing Item: 5B2C310C
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B2C3010 5B2C310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B2C3110
5B2C3020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B2C3130
5B2C3029
Failing Item:
5B2C3100
v SVCDOCS
Failing Item: 5B2C34FF
v STORIOA
v SASEXP

5B2C4041 • 5B2CFFF6
5B2C4041 5B2C70DD
required.
5B2CFFF3
Failing Item:
Failing Item:
5B2C4060 v DISKDRV
5B2CFFF4
failed. Explanation: Read Intensive (RI) SSD status change or
device problem.
Failing Item:
v SIP3153 Problem determination: The RI SSD may be reporting
v SASCABL
v SASEXP the number of write operations the device supports.
5B2C4061 determine if this SRC is a status change or a drive
failure.
Failing Item:
Response: A redundant disk unit connection has been v RI_SSD
v DISKDRV
v STORIOA
5B2C4100
Explanation: Device bus fabric error. 5B2CFFF5
v SIP3152
v DISKDRV v DISKDRV
5B2C7000 5B2CFFF6
Explanation: Disk sector read error. Explanation: Read Intensive (RI) SSD status change or
device problem.
logged for information only. Response: If this event appears in a serviceable event
view, work with the failing item list found there to
5B2C7001
Explanation: Temporary disk data error. view, no service action is required.
Response: If this event appears in a serviceable event Problem determination: The RI SSD may be reporting
view, work with the failing item list found there. If this a status change in the number of write operations it
event does not appear in a serviceable event view, no supports. The device may be nearing the limit for the
service action is required. number of write operations the device supports.
Failing Item:
v DISKDRV problem.
Failing Item:
v RI_SSD

5B2CFFF7 • 5B2D3010

5B2CFFF7
5B2CFFFC
Failing Item:
v SIP3250
5B2CFFF9 v DISKDRV
v STORIOA
5B2CFFFD
5B2CFFFA Failing Item:

v SIP3250
v DISKDRV
v STORIOA
service action is required. 5B2CFFFE
v SASEXP
Failing Item:
5B2CFFFB v SIP3150
(5B2D) Reference codes

v DEVBPLN
5B2D102E
v SASCABL
v SASEXP
Failing Item:
v DISKDRV 5B2D3010
5B2D3002 IOA.
Explanation: Addressed device failed to respond to Failing Item:
selection.
v DISKDRV
v DISKDRV v SASCABL
v STORIOA v SASEXP

5B2D3020 • 5B2D4061
5B2D3020 5B2D3110
Explanation: Replacement device is not supported. Explanation: Device bus interface error occurred.
v DISKDRV v DISKDRV
v STORIOA v STORIOA
v SASCABL v SASCABL
v SASEXP
5B2D3029
Explanation: A device replacement has occurred. 5B2D3130
Response: No action required. This reference code is Explanation: Device Licensed Internal Code.
logged for information only. Response: The device is not supported with the level
5B2D3100 level of support.
Explanation: Device bus interface error occurred. Failing Item:

v SVCDOCS
Failing Item:
v DISKDRV
5B2D34FF
v STORIOA
v SASCABL Explanation: Format in progress.
5B2D3109
5B2D4041
Failing Item:
v DISKDRV Response: Incomplete multipath connection between
v STORIOA
v SASEXP v SIP3146
5B2D310C 5B2D4060
Explanation: Device bus error. Explanation: Multipath redundancy level reduced.
Failing Item: Response: A redundant disk unit connection has

failed.
v SIP3250
v STORIOA v SIP3153
v SASCABL
5B2D310D v SASEXP

5B2D4061
Failing Item:
v SIP3250
v DISKDRV Response: A redundant disk unit connection has been
v STORIOA

5B2D4100 • 5B2DFFF9
5B2D4100 5B2DFFF5
v SASCABL
v SASEXP
Failing Item:
v DEVBPLN
v DISKDRV
v STORIOA
v DISKDRV
5B2DFFF6
5B2D7000 Explanation: Read Intensive (RI) SSD status change or

device problem.
Response: No action required. This reference code is view, work with the failing item list found there to
logged for information only. determine the part number and location of the RI SSD.
5B2D7001 view, no service action is required.
Explanation: Temporary disk data error. Problem determination: The RI SSD may be reporting
Response: If this event appears in a serviceable event supports. The device may be nearing the limit for the
view, work with the failing item list found there. If this number of write operations the device supports.
event does not appear in a serviceable event view, no Perform the steps in symbolic FRU RI_SSD to
service action is required. determine if this SRC is a status change or a drive
problem.
Failing Item:
v RI_SSD
5B2D70DD v DISKDRV

required. 5B2DFFF7
5B2DFFF3 Response: If this event appears in a serviceable event
Explanation: Disk media format not valid. view, work with the failing item list found there. If this
v DISKDRV
Failing Item:
v DISKDRV
5B2DFFF4
Explanation: Read Intensive (RI) SSD status change or 5B2DFFF9
device problem.
a status change in the number of write operations it Response: If this event appears in a serviceable event
supports. The device may have reached the limit for view, work with the failing item list found there. If this
the number of write operations the device supports. event does not appear in a serviceable event view, no
Perform the steps in symbolic FRU RI_SSD to service action is required.
failure.
v DISKDRV
Failing Item:
v RI_SSD
v DISKDRV
v STORIOA

5B2DFFFA • 5B303100
v SIP3250
5B2DFFFA
v DISKDRV
v STORIOA
5B2DFFFD
v STORIOA
v SASCABL
Failing Item:
v SASEXP
v SIP3250
v DISKDRV
5B2DFFFB
v STORIOA
Response: No action required. This reference code is 5B2DFFFE
5B2DFFFC Response: If this event appears in a serviceable event

Explanation: Soft device bus error. event does not appear in a serviceable event view, no
v SIP3150
Failing Item:

v STORIOA
5B30102E
v SASCABL
v SASEXP
Failing Item:
v DISKDRV 5B303020
5B303002
Failing Item:
v DISKDRV
selection.
v STORIOA
Failing Item:
v SASCABL
v DISKDRV
v STORIOA
5B303029
v DEVBPLN
v SASCABL
5B303010
5B303100
IOA. Explanation: Device bus interface error occurred.

v DISKDRV v DISKDRV

5B303109 • 5B307001
v STORIOA
5B304041
v SASCABL
v SASEXP
5B303109
Failing Item:
v SIP3146
Failing Item:
v DISKDRV
5B304060
v STORIOA
v SASCABL
failed.

v SIP3153
v SASCABL
Failing Item:
v SASEXP
v SIP3250
v DISKDRV
5B304061
v STORIOA

v SIP3250
v DISKDRV
Failing Item:
v STORIOA
v SIP3152
v SASCABL
5B303110
v SASEXP
v DEVBPLN
v DISKDRV v DISKDRV
v STORIOA
v SASCABL 5B307000
v SASEXP
5B303130
level of support.
Failing Item:

5B3070DD • 5B30FFFD

5B3070DD
Failing Item:
required.
v DISKDRV
5B30FFF3
5B30FFFA
Failing Item:
v DISKDRV
5B30FFF4 service action is required.
Explanation: Disk device problem. Failing Item:
v DISKDRV v STORIOA
v STORIOA v SASCABL
v SASEXP
5B30FFF5
5B30FFFB
view, work with the failing item list found there. If this Response: No action required. This reference code is
event does not appear in a serviceable event view, no logged for information only.
Failing Item: 5B30FFFC
v DISKDRV Explanation: Soft device bus error.
5B30FFF6 view, work with the failing item list found there. If this
Explanation: Disk device detected recoverable error. event does not appear in a serviceable event view, no
service action is required. v DISKDRV
v DISKDRV
5B30FFFD
5B30FFF7 Explanation: Soft device bus error.
v DISKDRV v DISKDRV
v STORIOA
5B30FFF9

5B30FFFE • 5B313130

5B30FFFE
Failing Item:

v DISKDRV
5B31102E
v STORIOA
v SASCABL
v DISKDRV
5B313109
5B313002
Failing Item:
selection.
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v DEVBPLN
v SASCABL
5B31310C
v SASEXP

v SIP3250
IOA. v DISKDRV
v STORIOA
Failing Item:
v DISKDRV
5B31310D
v STORIOA
v SASCABL Explanation: Device bus error.
v SIP3250
5B313020 v DISKDRV
Failing Item:
5B313110
v DISKDRV
v STORIOA Explanation: Device bus interface error occurred.
v DISKDRV
5B313029 v STORIOA
Explanation: A device replacement has occurred. v SASCABL
v SASEXP
5B313130
5B313100 Explanation: Device Licensed Internal Code.
Explanation: Device bus interface error occurred. Response: The device is not supported with the level
Failing Item:
level of support.

5B3134FF • 5B31FFF7
Failing Item:
5B317001
v SVCDOCS
5B3134FF Response: If this event appears in a serviceable event

v DISKDRV
5B314041
Explanation: Incomplete multipath connection. 5B3170DD
Response: Incomplete multipath connection between Explanation: System log entry only, no service action
device backplane and device. required.
Failing Item:
v SIP3146 5B31FFF3
Explanation: Multipath redundancy level reduced. v DISKDRV
failed. 5B31FFF4
Failing Item: Explanation: Disk device problem.
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B314061 5B31FFF5
Explanation: Device bus fabric error. Failing Item:

v DISKDRV
Failing Item:
v SIP3152
5B31FFF6
v SASCABL
v SASEXP Explanation: Disk device detected recoverable error.
v DEVBPLN Response: If this event appears in a serviceable event

Failing Item:
5B317000
v DISKDRV
Response: No action required. This reference code is 5B31FFF7

5B31FFF9 • 5B323020
5B31FFF9 Failing Item:

v SIP3250
v DISKDRV
v STORIOA
service action is required. 5B31FFFD
Failing Item: Explanation: Soft device bus error.
5B31FFFA event does not appear in a serviceable event view, no
Failing Item:
v SIP3250
Failing Item:
v DISKDRV 5B31FFFE
v STORIOA Explanation: Temporary disk bus error.
5B31FFFB
Failing Item:
v SIP3150
5B31FFFC

v SASEXP
5B32102E
5B323010
Failing Item:
v DISKDRV IOA.
Failing Item:
5B323002
v DISKDRV
selection.
v SASCABL
v DISKDRV
v STORIOA 5B323020
v DEVBPLN
v SASCABL

5B323029 • 5B324100

v DISKDRV
v STORIOA 5B323130
v SASCABL Explanation: Device Licensed Internal Code.
5B323029 of code currently on the system. Contact your next
Explanation: A device replacement has occurred. level of support.

logged for information only. v SVCDOCS
5B323100 5B3234FF
Explanation: Device bus interface error occurred. Explanation: Format in progress.
Failing Item: Response: No action required. This reference code is
v STORIOA
v SASCABL 5B324041
v SASEXP Explanation: Incomplete multipath connection.
5B323109 device backplane and device.
Explanation: IOA timed out a disk command. Failing Item:
v DISKDRV
v STORIOA 5B324060
v SASCABL Explanation: Multipath redundancy level reduced.
failed.
Explanation: Device bus error. v SIP3153
v SIP3250 v SASEXP
v DISKDRV
v STORIOA 5B324061
Explanation: Device bus error. restored. No service action is required.
Failing Item:
5B324100
v SIP3250
v DISKDRV Explanation: Device bus fabric error.
v SIP3152
5B323110 v SASCABL
Explanation: Device bus interface error occurred. v SASEXP
v DEVBPLN
Failing Item:
v STORIOA
v DISKDRV
v DISKDRV
v STORIOA
v SASCABL

5B327000 • 5B32FFFC
5B327000 5B32FFF7
5B327001
Failing Item:
v DISKDRV
event does not appear in a serviceable event view, no 5B32FFF9
5B3270DD
Failing Item:
required. v DISKDRV
5B32FFF3 5B32FFFA

v DISKDRV
5B32FFF4
Failing Item:
v DISKDRV v SASCABL
v STORIOA v SASEXP
5B32FFF5 5B32FFFB
5B32FFFC
Failing Item:
v DISKDRV
5B32FFF6 event does not appear in a serviceable event view, no

v STORIOA
Failing Item:
v DISKDRV

5B32FFFD • 5B333110
5B32FFFD 5B32FFFE
v SIP3250 v SIP3150
v DISKDRV
v STORIOA

5B33102E
5B333100
Failing Item:
v DISKDRV
Failing Item:
v DISKDRV
5B333002
v STORIOA
v SASCABL
selection.
v SASEXP
Failing Item:
v DISKDRV
5B333109
v STORIOA
v DEVBPLN
v SASEXP v DISKDRV
v STORIOA
5B333010 v SASCABL
v SASEXP
IOA.
5B33310C
Failing Item:
v SASCABL v SIP3250
v SASEXP v DISKDRV
v STORIOA
5B333020
Explanation: Replacement device is not supported. 5B33310D

v STORIOA v SIP3250
v SASCABL v DISKDRV
v STORIOA
5B333029
Explanation: A device replacement has occurred. 5B333110

5B333130 • 5B33FFF6

v DISKDRV v STORIOA
v STORIOA v DISKDRV
v SASCABL
v SASEXP 5B337000
5B333130
of code currently on the system. Contact your next 5B337001
level of support.
Failing Item:
5B3334FF service action is required.

v DISKDRV
5B3370DD
5B334041 Explanation: System log entry only, no service action
required.
5B33FFF3
Failing Item:
v DISKDRV
5B334060
5B33FFF4
v SIP3153 v STORIOA
v SASCABL
v SASEXP 5B33FFF5
5B334061 Response: If this event appears in a serviceable event
Response: A redundant disk unit connection has been service action is required.
Failing Item:
v DISKDRV
5B334100
5B33FFF6
Failing Item:
v SIP3152
v SASCABL
v SASEXP

5B33FFF7 • 5B343010
event does not appear in a serviceable event view, no Explanation: SAS bus reset occurred.
v DISKDRV
5B33FFFC
5B33FFF7 Explanation: Soft device bus error.
v DISKDRV v DISKDRV
v STORIOA
5B33FFF9
Explanation: Temporary disk data error. 5B33FFFD
Response: If this event appears in a serviceable event Explanation: Soft device bus error.
v SIP3250
5B33FFFA v DISKDRV
Explanation: Temporary disk bus error. v STORIOA

view, work with the failing item list found there. If this 5B33FFFE
event does not appear in a serviceable event view, no Explanation: Temporary disk bus error.
v SASEXP v SIP3150
5B33FFFB

v DISKDRV
5B34102E
v STORIOA
v DEVBPLN
v DISKDRV v SASEXP
5B343002 5B343010
Explanation: Addressed device failed to respond to Explanation: Disk device returned wrong response to
selection. IOA.

5B343020 • 5B344061
v DISKDRV
5B343110
v STORIOA
v SASCABL
v DISKDRV
5B343020 v STORIOA
v SASCABL
v SASEXP
Failing Item:
v DISKDRV
5B343130
v STORIOA
v SASCABL
5B343029
level of support.
Failing Item:
Response: No action required. This reference code is v SVCDOCS
5B3434FF
5B343100
v DISKDRV
v STORIOA 5B344041
v SASCABL
v SASEXP
5B343109
Failing Item:
v SIP3146
Failing Item:
v DISKDRV 5B344060
v STORIOA
v SASCABL
v SASEXP
failed.
Failing Item:
5B34310C
v SIP3153
v SASCABL
v SIP3250
v DISKDRV 5B344061
v STORIOA
5B34310D
Failing Item:
v SIP3250
v DISKDRV
v STORIOA

5B344100 • 5B34FFFB
v DISKDRV
5B344100
5B34FFF6
Failing Item:
v SIP3152
v SASCABL
v DISKDRV v DISKDRV
5B347000 5B34FFF7

v DISKDRV
event does not appear in a serviceable event view, no 5B34FFF9
Failing Item:
5B3470DD service action is required.

required. v DISKDRV
5B34FFF3 5B34FFFA
5B34FFF4
Failing Item:
v DISKDRV
v DISKDRV v SASCABL
v STORIOA v SASEXP
5B34FFF5 5B34FFFB
Failing Item:

5B34FFFC • 5B41310C

5B34FFFC
Failing Item:
v DISKDRV
Failing Item:
5B34FFFE
v SIP3250
v STORIOA Response: If this event appears in a serviceable event
5B34FFFD
Failing Item:

v SASCABL
5B41102E
5B413029
Failing Item:
v DISKDRV
5B413002
Explanation: Addressed device failed to respond to 5B413100
selection.
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v DEVBPLN
v SASCABL
v SASCABL
v SASEXP
v SASEXP
5B413109
5B413010
IOA. Failing Item:
v DISKDRV v STORIOA
v STORIOA v SASCABL
v SASCABL v SASEXP
v SASEXP
5B41310C
5B413020 Explanation: Device bus error.
Explanation: Replacement device is not supported. Failing Item:
v DISKDRV v DISKDRV
v STORIOA v STORIOA

5B41310D • 5B41FFF4
5B41310D 5B414061
Explanation: Device bus error. Explanation: Multipath redundancy level increased.
Failing Item: Response: A redundant disk unit connection has been
v SIP3250 restored. No service action is required.
v DISKDRV
v STORIOA 5B414100
Explanation: Device bus interface error occurred. v SIP3152
v DISKDRV v SASEXP
v STORIOA v DEVBPLN
v SASCABL v STORIOA
v SASEXP v DISKDRV
5B413130 5B417000
level of support.
5B4134FF view, work with the failing item list found there. If this
Failing Item:
v DISKDRV
5B414041
5B4170DD
Response: Incomplete multipath connection between required.
Failing Item: 5B41FFF3
v SIP3146
Failing Item:
5B414060
v DISKDRV
Response: A redundant disk unit connection has 5B41FFF4
failed.
Failing Item:
Failing Item:
v SIP3153
v DISKDRV
v SASCABL
v STORIOA
v SASEXP

5B41FFF5 • 5B433002
Failing Item:
5B41FFF5
v DISKDRV
v STORIOA
Response: If this event appears in a serviceable event v SASCABL
v SASEXP
5B41FFFB
Failing Item:
v DISKDRV Explanation: SAS bus reset occurred.
5B41FFF6 logged for information only.

5B41FFFC
view, work with the failing item list found there. If this Explanation: Soft device bus error.
event does not appear in a serviceable event view, no Response: If this event appears in a serviceable event
service action is required. view, work with the failing item list found there. If this
v DISKDRV
Failing Item:
5B41FFF7 v SIP3250
v DISKDRV
v STORIOA
event does not appear in a serviceable event view, no 5B41FFFD
5B41FFF9
Failing Item:
v SIP3250
v DISKDRV
Failing Item: 5B41FFFE
5B41FFFA view, work with the failing item list found there. If this
Failing Item:

v DISKDRV
5B43102E
5B433002
Failing Item:

5B433010 • 5B434041

5B43310C
selection.
Failing Item:
v STORIOA v SIP3250
v DEVBPLN v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B43310D
5B433010 Explanation: Device bus error.
IOA. v SIP3250
v DISKDRV v STORIOA
v STORIOA
v SASCABL 5B433110
Failing Item:
5B433020
v DISKDRV
v DISKDRV v SASEXP
v STORIOA
v SASCABL 5B433130
5B433029
Explanation: A device replacement has occurred. of code currently on the system. Contact your next
level of support.
v SVCDOCS
5B433100
Explanation: Device bus interface error occurred. 5B4334FF

v SASCABL
v SASEXP 5B434041
5B433109 Response: Incomplete multipath connection between

v DISKDRV v SIP3146
v STORIOA
v SASCABL
v SASEXP

5B434060 • 5B43FFFA
5B434060 5B43FFF4
Explanation: Multipath redundancy level reduced. Explanation: Disk device problem.
failed. v DISKDRV
v SIP3153
v SASCABL 5B43FFF5
v SASEXP Explanation: Disk sector read error.
5B434061 view, work with the failing item list found there. If this
Explanation: Multipath redundancy level increased. event does not appear in a serviceable event view, no
restored. No service action is required. Failing Item:
v DISKDRV
5B434100
5B43FFF6
Failing Item:
v SASCABL
v SASEXP service action is required.
v DEVBPLN
Failing Item:
v STORIOA
v DISKDRV
v DISKDRV
5B43FFF7
5B437000
Response: No action required. This reference code is view, work with the failing item list found there. If this
logged for information only. event does not appear in a serviceable event view, no
view, work with the failing item list found there. If this 5B43FFF9
Failing Item:
5B4370DD Failing Item:
Explanation: System log entry only, no service action v DISKDRV
required.
5B43FFFA
5B43FFF3

5B43FFFB • 5B453109
Failing Item:
5B43FFFD
v DISKDRV
v STORIOA
v SASEXP
5B43FFFB
Failing Item:
Explanation: SAS bus reset occurred. v SIP3250
5B43FFFC 5B43FFFE
v SIP3250 v SIP3150
v DISKDRV
v STORIOA

5B45102E 5B453020
v DISKDRV v DISKDRV
v STORIOA
5B453002 v SASCABL
selection. 5B453029
v DEVBPLN
v SASCABL 5B453100
Failing Item:
5B453010
v DISKDRV
IOA.
v SASCABL
v DISKDRV
v STORIOA 5B453109
v SASCABL
v SASEXP
Failing Item:

5B45310C • 5B45FFF3
v DISKDRV
5B454060
v STORIOA
v SASCABL
failed.

v SIP3153
v SASCABL
Failing Item:
v SASEXP
v SIP3250
v DISKDRV
5B454061
v STORIOA

v SIP3250
v DISKDRV
Failing Item:
v STORIOA
v SIP3152
v SASCABL
5B453110
v SASEXP
v DEVBPLN
v DISKDRV v DISKDRV
v STORIOA
v SASCABL 5B457000
v SASEXP
5B453130
level of support.
Failing Item:
logged for information only. 5B4570DD
5B454041 required.

5B45FFF3
device backplane and device. Explanation: Disk media format not valid.

v SIP3146 v DISKDRV

5B45FFF4 • 5B45FFFE
Failing Item:
5B45FFF4
v DISKDRV
v STORIOA
v DISKDRV v SASEXP
v STORIOA
5B45FFFB
5B45FFF5
Response: If this event appears in a serviceable event logged for information only.
5B45FFFC
Failing Item:
5B45FFF6 service action is required.
v STORIOA
Failing Item:
5B45FFFD
v DISKDRV

v SIP3250
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
5B45FFFE
5B45FFF9
Failing Item:
Failing Item:
v SIP3150
v DISKDRV
5B45FFFA

5B47102E • 5B4734FF

5B47102E 5B473109
v DISKDRV v DISKDRV
v STORIOA
5B473002 v SASCABL
selection.
v DEVBPLN v SIP3250
v SASCABL v DISKDRV
v SASEXP v STORIOA
5B473010 5B47310D
IOA.
Failing Item:
Failing Item:
v SIP3250
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v SASCABL
v SASEXP
5B473110
5B473020
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v SASCABL
v STORIOA
v SASEXP
v SASCABL
5B473130
5B473029
Failing Item:
5B473100
v SVCDOCS
v STORIOA
v SASEXP

5B474041 • 5B47FFF9
5B474041 5B4770DD
required.
5B47FFF3
Failing Item:
Failing Item:
5B474060 v DISKDRV
5B47FFF4
v SIP3153 v DISKDRV
v SASCABL v STORIOA
v SASEXP
5B47FFF5

v DISKDRV
Failing Item:
5B47FFF6
v SIP3152
v SASCABL
v DEVBPLN
v DISKDRV
Failing Item:
v DISKDRV
5B477000

5B47FFF9
Failing Item:
v DISKDRV


5B47FFFE
Failing Item:
Failing Item:
v DISKDRV
v STORIOA
v SASCABL
v SASEXP
5B47FFFB
5B47FFFC
Failing Item:
v SIP3250
v DISKDRV
v STORIOA
5B47FFFD
Failing Item:
v SIP3250
v DISKDRV
v STORIOA


62583000 • 62589101
indications.
v FI00871
62583000
v PTFSRCH
v FI01112
tape unit.
62583202

Failing Item:
62583400 v FI00871
v FI00872
Failing Item:
v DEVTERM
v FI00872
v DEVTERM
62589101
v FI00871
v TAPCNFG

62589102 • 62589202

v FCIOA
v FCDEV
v FCCABLE
62589102

v DEVTERM v FI00871
v FI01112
62589103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871


Code was loaded.
Failing Item:

62589210 • 62589304

62589221
cable.
v FI00871
v FI01112 62589301

response. v FI00871
Failing Item:
v FI00871 62589302

v FCGATE
v FCIOA 62589303
v DEVTERM v FCGATE
62589220 62589304
Failing Item:
v USER

62589310 • 62589802
v FI00871
62589355
62589310
cannot be read.
is not correct.
62589320
failure.
Failing Item:
v FI00130 v MEDIA
v FI00871 v TAPCLN
v FI00871
62589321
error.
Failing Item:
Failing Item:
v FCCODE
v PTFSRCH
62589350
62589501
on tape medium.
Failing Item:


v MEDIA
v FI00871
62589801
62589351
cartridge. 62589802

62589803 • 6258FFF6

62589803
62589900
not upgraded.
62589804
not completed.
LIC.
Failing Item:
62589806 62589901
62589902
should be replaced.


indications.

62793000 • 62799102
62793000
the cable.
v FI01112
Failing Item:
Failing Item:
v TAPCNFG 62799101
Failing Item:
v FI00872
v DEVTERM
operational.
v FI00871

v FCDEV
v FCCABLE
Failing Item:
v TAPCNFG 62799102
v FI00871
v PTFSRCH error.
tape unit.
v FI00871

62799103 • 62799202

v DEVTERM v FI00871
v FI01112
62799103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871

Code was loaded.
Failing Item:
v USB_IOA
v USB_CBL
62799200 cable.
Failing Item:
v FI00871
v DEVTERM

62799210 • 62799320
62799210 62799302
response.
Failing Item:
62799211 v MEDIA
error.
v FI00871 v FCGATE
v ANYFC
v FCCABLE 62799304
v FI00872
v DEVTERM
following:
62799220
using the device.
v USER
v FI00871
62799221
Failing Item:
62799300
v PTFSRCH
Failing Item:
v FI00871 62799320
62799301 failure.
current operation.
Failing Item:
v FI00871

62799321 • 62799804
v FI00871
62799321
62799500
error.
Failing Item:
v PTFSRCH
62799350
62799501
62799351 62799801
cartridge.
62799802
Failing Item:
v TAPCLN
62799355 62799803

Failing Item:
v USER
v MEDIA
v TAPCLN

62799805 • 6279FFF6
62799805 62799902
62799903
62799806
6279FFF6
required).
62799810
should be replaced.
(Information Only.)
62799899
has been corrected.
62799900
not upgraded.
not completed.
LIC.
Failing Item:
v USER
62799901

6320C000 • 6320C023

An optical storage unit failure occurred.
Notes:
1. If the system is available, use online diagnostic tests when possible.
2. Use the Hardware Service Manager (HSM) verify function (via DST or SST) and verify that the unit is
operating correctly.
3. Search the problem log (WRKPRB) for a recent optical storage entry that might assist in analyzing the
problem. The WRKPRB entry will provide a reference code that can be found in the following table.
If the system is available, attempt the failing operation again with an optical media that is known to be
good. Does the operation complete successfully?
Yes: The original optical media may be defective, or the problem may be intermittent. Attempt the
failing operation again with the original optical media to verify. This ends the procedure.
No: Look at the 8 rightmost characters of the Data display for word 1. These 8 characters are the
reference code. Find the reference code in the following table.
capabilities. Reported media support may be
6320C000
inaccurate. Function may be reduced.
required.
v If this device is a client virtual optical device:
1. If no function reduction exists, no action is
6320C002
required.
Explanation: SCSI Selection or Reselection timeout – Note: Inaccuracies in media support reporting
occurred. is not likely to cause a functional problem.
Failing Item: 2. Verify that the backing device on the server is
v FI00870 varied on, operational, and not in exclusive use
by another partition. Once these things are
v CNVTCRD
verified, IPL the virtual IOP on the client
v FI01106 partition or vary the server partition's NWSD off
v STORIOA and on.
v MEDIA 3. Ensure that the latest optical LIC PTFs have been
v FI01141 applied to both the client and server partitions.
v FI01140 v If this device is NOT a client virtual optical device:
required.
6320C010
2. This is likely a secondary error. Other PAL entries
Explanation: Undefined sense key returned by device. logged at approximately the same time as this
one may explain the problem (e.g., interface
Failing Item:
errors may have prevented identification of
v FI00870 device characteristics.)
3. Ensure that the latest optical LIC PTFs have been
6320C020 applied.
6320C023
Failing Item:
v FI00870 Explanation: Unable to determine all of the device
capabilities or the device characteristics are not
supported with the current LIC. Writes will be blocked
6320C022 for this device. If a write is attempted, the device will
Explanation: Unable to determine all device be marked failed.

6320C100 • 6320C333
Response: No action is required. This reference code 2. Attempt the failing operation again.
is logged for information only. 3. If this does not correct the problem, exchange the
Problem determination: Perform the following: failing items.
1. If the device doesn't support writing to media, no Failing Item:
action is required. v MEDIA
2. If any enabling PTFs have been specified for this v FI00870
device feature, verify they have been applied.
3. This may be a secondary error. Other PAL entries
6320C301
logged at approximately the same time as this one
may explain the problem (e.g., interface errors may Explanation: Media or device error occurred.
have prevented identification of device
characteristics.) Response: Dust check encountered. The optical media
or the optical lens of the drive is dirty.
4. Ensure that the latest optical LIC PTFs have be
applied. Clean the optical drive and the media contained in the
drive.
6320C100
6320C302
Explanation: SCSI Bus error occurred.
Explanation: Media or device error occurred.
Failing Item:
v FI00870 Response: The device encountered an 'out of spare
sectors' condition when writing to the media. The
v CNVTCRD media can no longer be written to but is still readable.
v FI01106
Clean the optical drive and the media contained in the
v STORIOA drive.
v MEDIA
v FI01141 6320C303
v FI01140
Explanation: Media had an unknown format.

Explanation: SCSI command timeout occurred.
v FI00870 Explanation: Media or device error occurred.
v CNVTCRD
Response: The device encountered an 'out of spare
v FI01106 sectors' condition when writing to the media. The
v STORIOA media can no longer be written to but is still readable.
v MEDIA Clean the optical drive and the media contained in the
v FI01141 drive.
v FI01140
6320C333
6320C210 Explanation: Incompatible media.
Explanation: Unxpected device condition. Response: Perform the following:
Response: The device successfully recovered from a 1. Verify that the disk has a supported format.
temporary error. 2. If the format is supported, clean the disk and
No action is required. This reference code is logged for attempt the failing operation again.
information only. 3. If the operation fails again and results in the same
reference code, ask your media source for a
replacement disk.
6320C300
Failing Item:
v MEDIA
v FI00870
1. Clean the disk.

6320C400 • 6320FF6D
6320C400 6320CFFE
Explanation: Physical link error detected by device. Explanation: Recovered SCSI bus error.
Failing Item: Response: The device successfully recovered from a
v FI00870 temporary error.
v CNVTCRD No action is required. This reference code is logged for
v FI01106 information only.
v STORIOA
v FI01140 6320FF09
v FI01141 Explanation: Licensed Internal Code for optical device
was not upgraded.
6320C402 Response: This reference code is logged for
information only.
6320FF3D
assistance.
Failing Item:
v FI00130 Response: The device successfully recovered from a
temporary error.
6320CFF2 No action is required. This reference code is logged for

information only.
Explanation: Device not ready - Start Unit issued.
The device successfully recovered from a temporary 6320FF6D
error.
Explanation: Recovered SPD bus error.
No action is required. This reference code is logged for
information only. Response: The device successfully recovered from a
temporary error.

information only.
Explanation: Internal device error occurred.
Failing Item:
v FI00870
v MEDIA
6320CFF6
Explanation: Device successfully recovered from a
temporary error.
6320CFF7
Explanation: Recovered device error.
Response: The device successfully recovered from a
temporary error.
information only.

6321C000 • 6321C023

Notes:
6321C000
required.
6321C002
required.
v CNVTCRD
v STORIOA and on.
required.
6321C010
Failing Item:
6321C020 applied.
6321C023
Failing Item:

6321C100 • 6321C333
6321C301
drive.
6321C100
6321C302
Failing Item:
v FI01106
v STORIOA drive.
v MEDIA
v FI01141 6321C303
v FI01140

v CNVTCRD
v FI01141 drive.
v FI01140
6321C333
replacement disk.
6321C300
Failing Item:
v MEDIA
v FI00870
1. Clean the disk.

6321C400 • 6321FF6D
6321C400 6321CFFE
v STORIOA
v FI01140 6321FF09
was not upgraded.
information only.
6321FF3D
assistance.
Failing Item:
temporary error.

information only.
error.
temporary error.

information only.
Failing Item:
v FI00870
v MEDIA
6321CFF6
temporary error.
6321CFF7
temporary error.
information only.

632AC000 • 632AC100

Notes:
632AC000
required. 1. If no function reduction exists, no action is required.
may explain the problem (e.g., interface errors may
632AC002 characteristics.)
Explanation: Device selection or reselection timeout 3. Ensure that the latest optical LIC PTFs have been
occurred. applied.

632AC023
v Before replacing parts, ensure that the device is
connected to a USB port that supports this device. Explanation: Unable to determine all device
capabilities, or device characteristics are not supported
Failing Item:
with the current LIC. Writes will be blocked for this
v USB_CBL device. If a write is attempted, the device will be
v USB_DEV marked failed.
v USB_IOA Response: No action is required. This reference code
v MEDIA is logged for information only.
632AC020 1. If the device doesn't support writing to media, no
Explanation: Configuration error. action is required.
2. If any enabling PTFs have been specified for this
Response: Perform the following: device feature, verify they have been applied.
v Before replacing parts, ensure that the device is 3. This may be a secondary error. Other PAL entries
connected to a USB port that supports this device. logged at approximately the same time as this one
Failing Item: may explain the problem (e.g., interface errors may
v USB_DEV
characteristics.)
632AC022 applied.
Explanation: Unable to determine all device
capabilities. Reported media support may be 632AC100
Explanation: Bus error occurred.

632AC110 • 632AC400

632AC302
connected to a USB port that supports this device. Explanation: Media or device error occurred.
Failing Item: Response: The device encountered an 'out of spare

v USB_CBL
media can no longer be written to but is still readable.
v USB_DEV
v USB_IOA
drive.
v MEDIA
632AC303
632AC110
Explanation: Device command timeout occurred.
Response: Perform the following: logged for information only.
connected to a USB port that supports this device.
632AC332
Failing Item:
v USB_CBL
v USB_DEV
v USB_IOA media can no longer be written to but is still readable.
v MEDIA
drive.
632AC210
Explanation: Unxpected device condition. 632AC333
Response: The device successfully recovered from a Explanation: Incompatible media.
temporary error.
No action is required. This reference code is logged for 1. Verify that the disk has a supported format.
information only.
2. If the format is supported, clean the disk and
attempt the failing operation again.
632AC300 3. If the operation fails again and results in the same
Explanation: Media or device error occurred. reference code, ask your media source for a
replacement disk.
Response: Perform the following: 4. If cleaning or replacing the disk does not correct the
v Before replacing parts, ensure that the device is problem, exchange the failing items.
connected to a USB port that supports this device. 5. Before replacing parts, ensure that the device is
Failing Item: connected to a USB port that supports this device.
v USB_DEV v MEDIA
v USB_DEV
632AC301
Explanation: Media or device error occurred. 632AC400
Response: Dust check encountered. The optical media Explanation: Physical link error detected by device.
or the optical lens of the drive is dirty. Response: Perform the following:
Clean the optical drive and the media contained in the v Before replacing parts, ensure that the device is
drive. connected to a USB port that supports this device.
Failing Item:
v USB_CBL
v USB_DEV
v USB_IOA

632AC401 • 632BCFC2

632AC401
Explanation: Device LIC reporting physical link error
between USB IOA and USB optical device. v Before replacing parts, ensure that the device is
Failing Item:
1. Look for USB adapter errors logged at about the
same time as this event. The location code of the v USB_DEV
USB IOA may be given in the serviceable event v MEDIA
view that you are working with. If there is a
serviceable event for the USB IOA then work that
problem and close this problem. Otherwise continue 632ACFF6
with the next step. Explanation: Device successfully recovered from a
2. Before replacing parts, ensure that the device is temporary error.
Failing Item: is logged for information only.
v SVCDOCS
v USB_CBL 632ACFF7
v USB_DEV Explanation: Recovered device error.
v USB_IOA
v AJDGP01 temporary error.
632AC402 information only.
Response: Ask your next level of support for 632ACFFE
assistance. Explanation: Recovered bus error.
632ACFF2 information only.

632AFF3D
The device successfully recovered from a temporary
error. Explanation: Recovered IOA error.
No action is required. This reference code is logged for Response: The device successfully recovered from a
information only. temporary error.
632ACFF4 information only.

v SVCDOCS
632BCFC1
Explanation: Virtual media list access problem.
632BCFC2
Response: A virtual optical device cannot access the
Explanation: Error reading virtual volume list.
file containing the list of volumes.
1. On this partition and the Network File System Response: A non-recoverable error was detected while
server, ensure the proper file is specified and proper reading the list of volumes.
authority is granted. If that does not resolve the Check for errors on the Network File System server
problem continue with the next step. and resolve them. Then retry the operation. If the
2. Collect vlogs for major code 3A00 and send them to failure reoccurs, contact your hardware service
your next level of support. provider.

632BCFC3 • 632CC022
v SVCDOCS v SVCDOCS
632BCFC3 632BCFC6
Explanation: Virtual media volume list is not valid. Explanation: Virtual optical volume is not valid.
Response: The data in the list of volumes is not valid. Response: The file specified does not contain data that
can be processed as a virtual optical volume.
On the Network File System server, ensure that the
proper file is specified, that all files are entered On the Network File System server, ensure all the files
correctly, that there are no blank lines, and that the specified in the list of optical volumes are correct.
character set used is valid.
Failing Item:
v SVCDOCS
632BCFC7
632BCFC4
Explanation: Virtual optical device detected error.
Explanation: Virtual optical volume access problem.
Response: A virtual optical device detected an error
Response: A virtual optical device cannot access the reported by the Network File System server that cannot
file containing the specified optical volume. be recovered.
On the Network File System server, ensure the proper Check for errors on the Network File System server
file is specified in the list of volumes, and that the and resolve them. Then retry the operation. If the
proper authority is granted. failure reoccurs, contact your hardware service
provider.
Failing Item:
v SVCDOCS
632BCFC5
632BCFC8
Explanation: Error reading virtual optical volume.
Explanation: Virtual optical device error.
Response: A non-recoverable error was detected while
reading a virtual optical volume. Response: A virtual optical device encountered a
non-recoverable error.
Check for errors on the Network File System server
and resolve them. Then retry the operation. If the Contact your next level of support for assistance.
failure reoccurs, contact your hardware service
Failing Item:
provider.
v NEXTLVL
Failing Item:

Response: Refer to the hosting partition for problem
632CC000
analysis.
required.
632CC020
analysis.
632CC002
Explanation: SCSI Selection or Reselection timeout
632CC022
occurred.
analysis.
632CC010
Explanation: Undefined sense key returned by device.

632CC023 • 632CC400

632CC110
required. Explanation: SCSI command timeout occurred.
– Note: Inaccuracies in media support reporting Response: Refer to the hosting partition for problem
is not likely to cause a functional problem. analysis.
2. Verify that the backing device on the server is
varied on, operational, and not in exclusive use 632CC210
verified, IPL the virtual IOP on the client Explanation: Unxpected device condition.
partition or vary the server partition's NWSD off Response: The device successfully recovered from a
and on. temporary error.
applied to both the client and server partitions. No action is required. This reference code is logged for
information only.
v If this device is NOT a client virtual optical device:
required. 632CC300
2. This is likely a secondary error. Other PAL entries Explanation: Media or device error occurred.
logged at approximately the same time as this
analysis.
device characteristics.)
3. Ensure that the latest optical LIC PTFs have been 632CC301
applied. Explanation: Media or device error occurred.
632CC023 analysis.
capabilities or device characteristics are not supported 632CC302
device. If a write is attempted, the device will be Explanation: Media or device error occurred.
marked failed. Response: Refer to the hosting partition for problem
Response: No action is required. This reference code analysis.
Problem determination: Perform the following: 632CC303
1. If the device doesn't support writing to media, no Explanation: Media had an unknown format.
action is required.
2. If any enabling PTFs have been specified for this logged for information only.
logged at approximately the same time as this one 632CC333
may explain the problem (e.g., interface errors may Explanation: Incompatible media.
characteristics.) Response: Perform the following:
4. Ensure that the latest optical LIC PTFs have be 1. Verify that the disk has a format that is given
applied. support.
2. If the format is given support, clean the disk and
attempt the failing operation again.
632CC100
3. If the operation fails again with the same reference
Explanation: SCSI Bus error occurred. code, ask your media source for a replacement disk.
analysis. 632CC400
Explanation: Physical link error detected by device.
analysis.

632CC402 • 6330C002

632CC402
Explanation: Licensed Internal Code program error
temporary error.
occurred.
information only.
assistance.
Failing Item:
632CCFFE
v PTFSRCH
Explanation: Recovered SCSI bus error.
632CCFF2 Response: The device successfully recovered from a

temporary error.
Response: The device successfully recovered from a information only.
temporary error.
No action is required. This reference code is logged for 632CFF3D
information only.
632CCFF4 Response: The device successfully recovered from a

temporary error.
Response: Refer to the hosting partition for problem information only.
analysis.
632CFF6D
632CCFF6
Explanation: The device successfully recovered from a
temporary error. Response: The device successfully recovered from a
temporary error.
is logged for information only. No action is required. This reference code is logged for
information only.
632CCFF7

Notes:
6330C000
required.
6330C002

6330C010 • 6330C110
Explanation: SCSI Selection or Reselection timeout 3. Ensure that the latest optical LIC PTFs have been
occurred. applied.
Failing Item:
v FI00870 6330C023
v CNVTCRD Explanation: Unable to determine all of the device
v FI01106 capabilities or the device characteristics are not
v STORIOA
for this device. If a write is attempted, the device will
v MEDIA be marked failed.
v FI01141
v FI01140 is logged for information only.
6330C010
1. If the device doesn't support writing to media, no
Explanation: Undefined sense key returned by device. action is required.
Failing Item: 2. If any enabling PTFs have been specified for this
v FI00870
6330C020 may explain the problem (e.g., interface errors may
characteristics.)
Failing Item: 4. Ensure that the latest optical LIC PTFs have be
v FI00870 applied.
6330C022 6330C100
Explanation: Unable to determine all device Explanation: SCSI Bus error occurred.
Failing Item:
v FI00870
v CNVTCRD
v FI01106
v STORIOA
v MEDIA
v FI01141
required.
v FI01140
– Note: Inaccuracies in media support reporting
is not likely to cause a functional problem.
2. Verify that the backing device on the server is 6330C110
varied on, operational, and not in exclusive use Explanation: SCSI command timeout occurred.
verified, IPL the virtual IOP on the client Failing Item:
partition or vary the server partition's NWSD off v FI00870
and on.
v CNVTCRD
v FI01106
applied to both the client and server partitions.
v STORIOA
v MEDIA
required. v FI01141
2. This is likely a secondary error. Other PAL entries v FI01140
device characteristics.)

6330C210 • 6330CFF4
6330C210 6330C333
Explanation: Unxpected device condition. Explanation: Incompatible media.
Response: The device successfully recovered from a Response: Perform the following:
temporary error. 1. Verify that the disk has a supported format.
No action is required. This reference code is logged for 2. If the format is supported, clean the disk and
information only. attempt the failing operation again.
3. If the operation fails again and results in the same
6330C300 reference code, ask your media source for a
replacement disk.
Failing Item:
v MEDIA
1. Clean the disk.
v FI00870
3. If this does not correct the problem, exchange the
6330C400
failing items.
Failing Item:
v FI00870 v FI00870
v CNVTCRD
6330C301 v FI01106
v STORIOA
v FI01140
Response: Dust check encountered. The optical media
v FI01141
6330C402
drive.
6330C302 Response: Ask your next level of support for
assistance.
Failing Item:
sectors' condition when writing to the media. The v FI00130
Clean the optical drive and the media contained in the 6330CFF2
drive. Explanation: Device not ready - Start Unit issued.
The device successfully recovered from a temporary
6330C303 error.
Explanation: Media had an unknown format. No action is required. This reference code is logged for
Response: No action required. This reference code is information only.
6330CFF4
6330C332 Explanation: Internal device error occurred.
Explanation: Media or device error occurred. Failing Item:
Response: The device encountered an 'out of spare v FI00870
sectors' condition when writing to the media. The v MEDIA
drive.

6330CFF6 • 6331C002
6330CFF6 6330FF09
Explanation: Device successfully recovered from a Explanation: Licensed Internal Code for optical device
temporary error. was not upgraded.
Response: No action is required. This reference code Response: This reference code is logged for
is logged for information only. information only.
6330CFF7 6330FF3D
Explanation: Recovered device error. Explanation: Recovered IOA error.
Response: The device successfully recovered from a Response: The device successfully recovered from a
temporary error. temporary error.
No action is required. This reference code is logged for No action is required. This reference code is logged for
information only. information only.
6330CFFE 6330FF6D
Explanation: Recovered SCSI bus error. Explanation: Recovered SPD bus error.
Response: The device successfully recovered from a Response: The device successfully recovered from a
temporary error. temporary error.

Notes:
1. Determine the device model using one of the
6331C000
methods below.
Explanation: System log entry only, no service action v If you are viewing this SRC from the Service
required. Action Log (SAL) then search for the symbolic
Response: No action is required. This reference code FRU callout "OPTD005". If "OPTD005" is listed
is logged for information only. then the device is a model 005 optical device.
Continue with the next step in this procedure.
v If you are viewing this SRC from the Product
6331C002
Activity Log (PAL) then the model will be listed
Explanation: SCSI Selection or Reselection timeout near the top of the screen when view the details
occurred. for the PAL entry. Record the model and Contine
with the next step in this procedure.
v Record the resource name logged for the SRC. Go
to Hardware Service Manager in SST/DST and

6331C010 • 6331C022
select "Locate resource by resource name". Enter – FI00870

the resource name you recorded. Select "Display
detail" for that resource and record the model.
6331C020
2. Is the device a model 005?
v Yes - the device is a USB attached optical device
being reported as a 6331 model 005 optical Response: Perform the following:
device. Before replacing parts ensure that the 1. Determine the device model using one of the
device has power from other than the USB cable. methods below.
Use the following failing item list:
v If you are viewing this SRC from the Service
– USB_CBL Action Log (SAL) then search for the symbolic
– USBCNVT FRU callout "OPTD005". If "OPTD005" is listed
– OPTD005 then the device is a model 005 optical device.
– USB_IOA
– MEDIA
v No - the device is a 6331 optical device. Use the near the top of the screen when view the details
following failing item list: for the PAL entry. Record the model and Contine
– FI00870 with the next step in this procedure.
– CNVTCRD v Record the resource name logged for the SRC. Go
– FI01106 to Hardware Service Manager in SST/DST and
select "Locate resource by resource name". Enter
– STORIOA
– MEDIA detail" for that resource and record the model.
– FI01141 2. Is the device a model 005?
– FI01140 v Yes - the device is a USB attached optical device
being reported as a 6331 model 005 optical
6331C010 device. Before replacing parts ensure that the
device has power from other than the USB cable.
Explanation: Undefined sense key returned by device. Use the following failing item list:
Response: Perform the following: – OPTD005
1. Determine the device model using one of the v No - the device is a 6331 optical device. Use the
methods below. following failing item list:
v If you are viewing this SRC from the Service – FI00870
Action Log (SAL) then search for the symbolic
FRU callout "OPTD005". If "OPTD005" is listed 6331C022
then the device is a model 005 optical device.
Continue with the next step in this procedure. Explanation: Unable to determine all device
v If you are viewing this SRC from the Product capabilities. Reported media support may be
Activity Log (PAL) then the model will be listed inaccurate. Function may be reduced.
near the top of the screen when view the details Response: No action is required. This reference code
for the PAL entry. Record the model and Contine is logged for information only.
to Hardware Service Manager in SST/DST and v If this device is a client virtual optical device:
select "Locate resource by resource name". Enter 1. If no function reduction exists, no action is
the resource name you recorded. Select "Display required.
detail" for that resource and record the model. – Note: Inaccuracies in media support reporting
2. Is the device a model 005? is not likely to cause a functional problem.
v Yes - the device is a USB attached optical device 2. Verify that the backing device on the server is
being reported as a 6331 model 005 optical varied on, operational, and not in exclusive use
device. Before replacing parts ensure that the by another partition. Once these things are
device has power from other than the USB cable. verified, IPL the virtual IOP on the client
Use the following failing item list: partition or vary the server partition's NWSD off
– OPTD005 and on.
v No - the device is a 6331 optical device. Use the 3. Ensure that the latest optical LIC PTFs have been
following failing item list: applied to both the client and server partitions.

6331C023 • 6331C110
v If this device is NOT a client virtual optical device: v Yes - the device is a USB attached optical device
1. If no function reduction exists, no action is being reported as a 6331 model 005 optical
required. device. Before replacing parts ensure that the
one may explain the problem (e.g., interface – USB_CBL
errors may have prevented identification of – USBCNVT
device characteristics.) – OPTD005
3. Ensure that the latest optical LIC PTFs have been – USB_IOA
applied.
– MEDIA
v No - the device is a 6331 optical device. Use the
6331C023 following failing item list:
Explanation: Unable to determine all device – FI00870
capabilities or device characteristics are not supported – CNVTCRD
– FI01106
device. If a write is attempted, the device will be
marked failed. – STORIOA
– MEDIA
is logged for information only. – FI01141
– FI01140
1. If the device doesn't support writing to media, no
action is required. 6331C110
2. If any enabling PTFs have been specified for this Explanation: SCSI command timeout occurred.
logged at approximately the same time as this one 1. Determine the device model using one of the
may explain the problem (e.g., interface errors may methods below.
have prevented identification of device v If you are viewing this SRC from the Service
characteristics.) Action Log (SAL) then search for the symbolic
4. Ensure that the latest optical LIC PTFs have be FRU callout "OPTD005". If "OPTD005" is listed
applied. then the device is a model 005 optical device.
6331C100 Activity Log (PAL) then the model will be listed
Explanation: SCSI Bus error occurred. near the top of the screen when view the details
for the PAL entry. Record the model and Contine
Response: Perform the following: with the next step in this procedure.
1. Determine the device model using one of the v Record the resource name logged for the SRC. Go
methods below. to Hardware Service Manager in SST/DST and
v If you are viewing this SRC from the Service select "Locate resource by resource name". Enter
Action Log (SAL) then search for the symbolic the resource name you recorded. Select "Display
FRU callout "OPTD005". If "OPTD005" is listed detail" for that resource and record the model.
then the device is a model 005 optical device. 2. Is the device a model 005?
v Yes - the device is a USB attached optical device
v If you are viewing this SRC from the Product being reported as a 6331 model 005 optical
Activity Log (PAL) then the model will be listed device. Before replacing parts ensure that the
near the top of the screen when view the details device has power from other than the USB cable.
for the PAL entry. Record the model and Contine Use the following failing item list:
– USB_CBL
– USBCNVT
select "Locate resource by resource name". Enter – OPTD005
the resource name you recorded. Select "Display – USB_IOA
detail" for that resource and record the model. – MEDIA
2. Is the device a model 005? v No - the device is a 6331 optical device. Use the
following failing item list:

6331C210 • 6331C333
– FI00870 v No - the device is a 6331 optical device. Use the

– CNVTCRD following failing item list:
– FI01106 – MEDIA
– STORIOA – FI00870
– MEDIA
– FI01141 6331C301
– FI01140 Explanation: Media or device error occurred.
Response: Dust check encountered. The optical media
6331C210 or the optical lens of the drive is dirty.
Explanation: Unxpected device condition. Clean the optical drive and the media contained in the
drive.
temporary error.
6331C302
information only. Explanation: Media or device error occurred.
6331C300 sectors' condition when writing to the media. The
drive.
1. Clean the disk.
6331C303
3. If the problem is corrected this ends the procedure.
Otherwise continue with the next step in this Explanation: Media had an unknown format.
procedure. Response: No action required. This reference code is
4. If cleaning the disk does not correct the problem, logged for information only.
exchange the failing items. Determine the failing
items with the following steps.
6331C332
methods below. Explanation: Media or device error occurred.
v If you are viewing this SRC from the Service Response: The device encountered an 'out of spare
Action Log (SAL) then search for the symbolic sectors' condition when writing to the media. The
FRU callout "OPTD005". If "OPTD005" is listed media can no longer be written to but is still readable.
Continue with the next step in this procedure. Clean the optical drive and the media contained in the
drive.
near the top of the screen when view the details 6331C333
for the PAL entry. Record the model and Contine
Explanation: Incompatible media.
v Record the resource name logged for the SRC. Go Response: Perform the following:
to Hardware Service Manager in SST/DST and 1. Verify that the disk has a supported format.
select "Locate resource by resource name". Enter 2. If the format is supported, clean the disk and
the resource name you recorded. Select "Display attempt the failing operation again.
detail" for that resource and record the model.
3. If the operation fails again and results in the same
6. Is the device a model 005? reference code, ask your media source for a
v Yes - the device is a USB attached optical device replacement disk.
being reported as a 6331 model 005 optical 4. If cleaning or replacing the disk does not correct the
device. Before replacing the device ensure that problem, exchange the failing items. Determine the
the device has power from other than the USB failing items with the following steps.
cable. Use the following failing item list:
– MEDIA methods below.
– OPTD005 v If you are viewing this SRC from the Service

6331C400 • 6331C402
FRU callout "OPTD005". If "OPTD005" is listed – USB_IOA

then the device is a model 005 optical device. v No - the device is a 6331 optical device. Use the
Continue with the next step in this procedure. following failing item list:
v If you are viewing this SRC from the Product – FI00870
– CNVTCRD
near the top of the screen when view the details
for the PAL entry. Record the model and Contine – FI01106
with the next step in this procedure. – STORIOA
v Record the resource name logged for the SRC. Go – FI01140
to Hardware Service Manager in SST/DST and – FI01141
detail" for that resource and record the model. 6331C401
6. Is the device a model 005? Explanation: Device LIC reporting physical link error
v Yes - the device is a USB attached optical device between USB IOA and USB attached SATA optical
being reported as a 6331 model 005 optical device.
device. Before replacing parts ensure that the
Use the following failing item list: 1. Look for USB adapter errors logged at about the
same time as this event. The location code of the
– MEDIA
USB IOA may be given in the serviceable event
– OPTD005 view that you are working with. If there is a
v No - the device is a 6331 optical device. Use the serviceable event for the USB IOA then work that
following failing item list: problem and close this problem. Otherwise continue
– MEDIA with the next step.
– FI00870 2. The device is a USB attached optical device being
reported as a 6331 model 005 optical device. Before
replacing parts ensure that the device has power
6331C400 from other than the USB cable. Power is supplied
from the enclosure where the device is located. If
the enclosure is a 9119-MxE system control unit
Response: Perform the following: then the device power and device service indicators
1. Determine the device model using one of the are managed from the ASMI interface. If you have
methods below. verified that the device has power then work the
failing item list.
v If you are viewing this SRC from the Service
Action Log (SAL) then search for the symbolic Failing Item:
FRU callout "OPTD005". If "OPTD005" is listed v SVCDOCS
v USB_CBL
v USBCNVT
Activity Log (PAL) then the model will be listed v OPTD005
near the top of the screen when view the details v USB_IOA
for the PAL entry. Record the model and Contine v AJDGP01
to Hardware Service Manager in SST/DST and 6331C402
select "Locate resource by resource name". Enter Explanation: Licensed Internal Code error.
detail" for that resource and record the model. Response: Ask your next level of support for
assistance.
v Yes - the device is a USB attached optical device Failing Item:
being reported as a 6331 model 005 optical v FI00130
– USB_CBL
– USBCNVT
– OPTD005

6331CFF2 • 6331FF6D
6331CFF2 6331CFF7
Explanation: Device not ready - Start Unit issued. Explanation: Recovered device error.
The device successfully recovered from a temporary Response: The device successfully recovered from a
error. temporary error.
6331CFF4 6331CFFE
Explanation: Internal device error occurred. Explanation: Recovered SCSI bus error.
Response: Response: The device successfully recovered from a
1. Determine the failing items with the following temporary error.
steps. No action is required. This reference code is logged for
2. Determine the device model using one of the information only.
methods below.
v If you are viewing this SRC from the Service 6331FF09
FRU callout "OPTD005". If "OPTD005" is listed Explanation: Licensed Internal Code for optical device
then the device is a model 005 optical device. was not upgraded.
Continue with the next step in this procedure. Response: This reference code is logged for
v If you are viewing this SRC from the Product information only.
near the top of the screen when view the details
for the PAL entry. Record the model and Contine 6331FF3D
with the next step in this procedure. Explanation: Recovered IOA error.
temporary error.
the resource name you recorded. Select "Display No action is required. This reference code is logged for
detail" for that resource and record the model. information only.
v Yes - the device is a USB attached optical device 6331FF6D
being reported as a 6331 model 005 optical
Explanation: Recovered bus error.
device has power from other than the USB cable. Response: The device successfully recovered from a
Use the following failing item list: temporary error.
– OPTD005 No action is required. This reference code is logged for
– MEDIA information only.
v No - the device is a 6331 optical device. Use the
following failing item list:
– FI00870
– MEDIA
6331CFF6
temporary error.

6333C000 • 6333C023

Notes:
6333C000
required.
6333C002
required.
v CNVTCRD
v STORIOA and on.
required.
6333C010
Failing Item:
6333C020 applied.
6333C023
Failing Item:

6333C100 • 6333C333
6333C301
drive.
6333C100
6333C302
Failing Item:
v FI01106
v STORIOA drive.
v MEDIA
v FI01141 6333C303
v FI01140

v CNVTCRD
v FI01141 drive.
v FI01140
6333C333
replacement disk.
6333C300
Failing Item:
v MEDIA
v FI00870
1. Clean the disk.

6333C400 • 6333FF6D
6333C400 6333CFFE
v STORIOA
v FI01140 6333FF09
was not upgraded.
information only.
6333FF3D
assistance.
Failing Item:
temporary error.

information only.
error.
temporary error.

information only.
Failing Item:
v FI00870
v MEDIA
6333CFF6
temporary error.
6333CFF7
temporary error.
information only.

6336C000 • 6336C023

Notes:
6336C000
required.
6336C002
required.
v CNVTCRD
v STORIOA and on.
required.
6336C010
Failing Item:
6336C020 applied.
6336C023
Failing Item:

6336C100 • 6336C333
6336C301
drive.
6336C100
6336C302
Failing Item:
v FI01106
v STORIOA drive.
v MEDIA
v FI01141 6336C303
v FI01140

v CNVTCRD
v FI01141 drive.
v FI01140
6336C333
replacement disk.
6336C300
Failing Item:
v MEDIA
v FI00870
1. Clean the disk.

6336C400 • 6336FF6D
6336C400 6336CFFE
v STORIOA
v FI01140 6336FF09
was not upgraded.
information only.
6336FF3D
assistance.
Failing Item:
temporary error.

information only.
error.
temporary error.

information only.
Failing Item:
v FI00870
v MEDIA
6336CFF6
temporary error.
6336CFF7
temporary error.
information only.

6337C000 • 6337C023

Notes:
6337C000
required.
6337C002
required.
v CNVTCRD
v STORIOA and on.
required.
6337C010
Failing Item:
6337C020 applied.
6337C023
Failing Item:

6337C100 • 6337C333
6337C301
drive.
6337C100
6337C302
Failing Item:
v FI01106
v STORIOA drive.
v MEDIA
v FI01141 6337C303
v FI01140

v CNVTCRD
v FI01141 drive.
v FI01140
6337C333
replacement disk.
6337C300
Failing Item:
v MEDIA
v FI00870
1. Clean the disk.

6337C400 • 6337FF6D
6337C400 6337CFFE
v STORIOA
v FI01140 6337FF09
was not upgraded.
information only.
6337FF3D
assistance.
Failing Item:
temporary error.

information only.
error.
temporary error.

information only.
Failing Item:
v FI00870
v MEDIA
6337CFF6
temporary error.
6337CFF7
temporary error.
information only.

63823000 • 63829101

indications.
63823000
Failing Item:
v TAPCNFG
Failing Item:
v FI00871
v FI01112
v PTFSRCH
63823202
63829100
I/O processor.


v FI00872 v FI00871
v DEVTERM v FI01112
v FI00871 v FI00872
v FI01103 v DEVTERM
v FI01106
63829101

63829102 • 63829201
Failing Item:
v USB_DEV
v USB_CBL
Failing Item:
v FCIOA
63829200
v FCDEV
v FI00871
v FCGATE
v DEVTERM
Failing Item:
v FI00871
63829103
v FI01112
tape unit.
v DEVTERM
63829201
cable.
v SASCABL
63829104
v FI01112

63829202 • 63829303
v FI00872
63829220
v DEVTERM
v MEDIA
63829202
Code was loaded.
cable.
cable.
Failing Item:
Failing Item:
63829301
v FI00871
current operation.

v FI00871
response.
63829302
Failing Item:
v MEDIA
Failing Item:
63829303
v FCGATE
v FI00872 v FCGATE
v DEVTERM

63829304 • 63829800
63829304 63829351
cartridge.
v USER v TAPCLN
v FI00871 v FI00871
63829310 63829355
v PTFSRCH
cartridge.
Failing Item:
Failing Item:
v FI00130
v USER
v FI00871
v MEDIA
v TAPCLN
63829321
v FI00871
error.
63829500

v FCCODE
Failing Item:
63829350 v PTFSRCH


63829801 • 6382FFF6
63829801 63829899
63829802
63829900
not upgraded.
not completed.
63829803
LIC.
63829901
63829806
63829903

(Information Only.)


63833000 • 63839101
indications.
v FI00871
63833000
v PTFSRCH
v FI01112
tape unit.
63833202

Failing Item:
63833400 v FI00871
v FI00872
Failing Item:
v DEVTERM
v FI00872
v DEVTERM
63839101
v FI00871
v TAPCNFG

63839102 • 63839202

v FCIOA
v FCDEV
v FCCABLE
63839102

v DEVTERM v FI00871
v FI01112
63839103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871


Code was loaded.
Failing Item:

63839210 • 63839304

63839221
cable.
v FI00871
v FI01112 63839301

response. v FI00871
Failing Item:
v FI00871 63839302

v FCGATE
v FCIOA 63839303
v DEVTERM v FCGATE
63839220 63839304
Failing Item:
v USER

63839310 • 63839802
v FI00871
63839355
63839310
cannot be read.
is not correct.
63839320
failure.
Failing Item:
v FI00130 v MEDIA
v FI00871 v TAPCLN
v FI00871
63839321
error.
Failing Item:
Failing Item:
v FCCODE
v PTFSRCH
63839350
63839501
on tape medium.
Failing Item:


v MEDIA
v FI00871
63839801
63839351
cartridge. 63839802

63839803 • 6383FFF6

63839803
63839900
not upgraded.
63839804
not completed.
LIC.
Failing Item:
63839806 63839901
63839902
should be replaced.


indications.

63843000 • 63849102
63843000
the cable.
v FI01112
Failing Item:
Failing Item:
v TAPCNFG 63849101
Failing Item:
v FI00872
v DEVTERM
operational.
v FI00871

v FCDEV
v FCCABLE
Failing Item:
v TAPCNFG 63849102
v FI00871
v PTFSRCH error.
tape unit.
v FI00871

63849103 • 63849202

v DEVTERM v FI00871
v FI01112
63849103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871

Code was loaded.
Failing Item:
v USB_IOA
v USB_CBL
63849200 cable.
Failing Item:
v FI00871
v DEVTERM

63849210 • 63849320
63849210 63849302
response.
Failing Item:
63849211 v MEDIA
error.
v FI00871 v FCGATE
v ANYFC
v FCCABLE 63849304
v FI00872
v DEVTERM
following:
63849220
using the device.
v USER
v FI00871
63849221
Failing Item:
63849300
v PTFSRCH
Failing Item:
v FI00871 63849320
63849301 failure.
current operation.
Failing Item:
v FI00871

63849321 • 63849804
v FI00871
63849321
63849500
error.
Failing Item:
v PTFSRCH
63849350
63849501
63849351 63849801
cartridge.
63849802
Failing Item:
v TAPCLN
63849355 63849803

Failing Item:
v USER
v MEDIA
v TAPCLN

63849805 • 6384FFF6
63849805 63849902
63849903
63849806
6384FFF6
required).
63849810
should be replaced.
(Information Only.)
63849899
has been corrected.
63849900
not upgraded.
not completed.
LIC.
Failing Item:
v USER
63849901

63863000 • 63869101

indications.
63863000
Failing Item:
v TAPCNFG
Failing Item:
v FI00871
v FI01112
v PTFSRCH
63863202
63869100
I/O processor.


v FI00872 v FI00871
v DEVTERM v FI01112
v FI00871 v FI00872
v FI01103 v DEVTERM
v FI01106
63869101

63869102 • 63869201
Failing Item:
v USB_DEV
v USB_CBL
Failing Item:
v FCIOA
63869200
v FCDEV
v FI00871
v FCGATE
v DEVTERM
Failing Item:
v FI00871
63869103
v FI01112
tape unit.
v DEVTERM
63869201
cable.
v SASCABL
63869104
v FI01112

63869202 • 63869303
v FI00872
63869220
v DEVTERM
v MEDIA
63869202
Code was loaded.
cable.
cable.
Failing Item:
Failing Item:
63869301
v FI00871
current operation.

v FI00871
response.
63869302
Failing Item:
v MEDIA
Failing Item:
63869303
v FCGATE
v FI00872 v FCGATE
v DEVTERM

63869304 • 63869800
63869304 63869351
cartridge.
v USER v TAPCLN
v FI00871 v FI00871
63869310 63869355
v PTFSRCH
cartridge.
Failing Item:
Failing Item:
v FI00130
v USER
v FI00871
v MEDIA
v TAPCLN
63869321
v FI00871
error.
63869500

v FCCODE
Failing Item:
63869350 v PTFSRCH


63869801 • 6386FFF6
63869801 63869899
63869802
63869900
not upgraded.
not completed.
63869803
LIC.
63869901
63869806
63869903

(Information Only.)


63873000 • 63879101
indications.
v FI00871
63873000
v PTFSRCH
v FI01112
tape unit.
63873202

Failing Item:
63873400 v FI00871
v FI00872
Failing Item:
v DEVTERM
v FI00872
v DEVTERM
63879101
v FI00871
v TAPCNFG

63879102 • 63879202

v FCIOA
v FCDEV
v FCCABLE
63879102

v DEVTERM v FI00871
v FI01112
63879103 v FI00872
tape unit.
the ports.
Failing Item:
v FI00871 cable.
v FI00871


Code was loaded.
Failing Item:

63879210 • 63879304

63879221
cable.
v FI00871
v FI01112 63879301

response. v FI00871
Failing Item:
v FI00871 63879302

v FCGATE
v FCIOA 63879303
v DEVTERM v FCGATE
63879220 63879304
Failing Item:
v USER

63879310 • 63879802
v FI00871
63879355
63879310
cannot be read.
is not correct.
63879320
failure.
Failing Item:
v FI00130 v MEDIA
v FI00871 v TAPCLN
v FI00871
63879321
error.
Failing Item:
Failing Item:
v FCCODE
v PTFSRCH
63879350
63879501
on tape medium.
Failing Item:


v MEDIA
v FI00871
63879801
63879351
cartridge. 63879802

63879803 • 6387FFF6

63879803
63879900
not upgraded.
63879804
not completed.
LIC.
Failing Item:
63879806 63879901
63879902
should be replaced.


indications.

63A03000 • 63A09102
63A03000
the cable.
v FI01112
63A03202 Server partition refer to Troubleshooting the Virtual
Failing Item:
Failing Item:
v TAPCNFG 63A09101
63A03400 do the following before exchanging any parts:
Failing Item:
v FI00872
v DEVTERM
operational.
v FI00871
63A09020 additional problem analysis procedures.

v FCDEV
v FCCABLE
Failing Item:
v TAPCNFG 63A09102
v FI00871
v PTFSRCH error.
63A09100 documentation to analyze the problem.
tape unit.
v FI00871

63A09103 • 63A09202

v DEVTERM v FI00871
v FI01112
63A09103 v FI00872
tape unit.
Response: If the attached device is an external tape 63A09201
the ports.
Failing Item:
v FI00871 cable.
63A09104 I/O Server partition it may be necessary to reset the
v FI00871
If the attached tape device is owned by a Virtual I/O 63A09202

Code was loaded.
Failing Item:
v USB_IOA
v USB_CBL
63A09200 cable.
Failing Item:
v FI00871
v DEVTERM

63A09210 • 63A09320
63A09210 63A09302
response.
Failing Item:
63A09211 v MEDIA
error.
Response: Use the gateway device service 63A09303
v FI00871 v FCGATE
v ANYFC
v FCCABLE 63A09304
v FI00872
v DEVTERM
following:
63A09220
using the device.
v USER
v FI00871
63A09221
Explanation: I/O path change occurred. 63A09310
Failing Item:
63A09300
v PTFSRCH
Failing Item:
v FI00871 63A09320
63A09301 failure.
current operation.
Failing Item:
v FI00871

63A09321 • 63A09804
v FI00871
63A09321
63A09500
error.
Failing Item:
v PTFSRCH
63A09350
63A09501
exchange the tape media. 63A09800
63A09351 63A09801
cartridge.
63A09802
Failing Item:
v TAPCLN
63A09355 63A09803
1. Initialize the tape to a different format. 63A09804

Failing Item:
v USER
v MEDIA
v TAPCLN

63A09805 • 63A0FFF6
63A09805 63A09902
63A09903
63A09806
63A0FFF6
required).
63A09810
should be replaced.
(Information Only.)
63A09899
has been corrected.
63A09900
not upgraded.
not completed.
LIC.
Failing Item:
v USER
63A09901

63A13000 • 63A19101

indications.
63A13000
Failing Item:
v TAPCNFG
Failing Item:
v FI00871
v FI01112
v PTFSRCH
63A13202
63A19100
I/O processor.

63A13400 Server partition refer to Troubleshooting the Virtual

v FI00872 v FI00871
v DEVTERM v FI01112
v FI00871 v FI00872
v FI01103 v DEVTERM
v FI01106
63A19101
63A19020 Explanation: Fibre Channel interface error detected.

63A19102 • 63A19201
Failing Item:
v USB_DEV
v USB_CBL
Failing Item:
v FCIOA
63A19200
v FCDEV
63A19102 do the following before exchanging any parts:
v FI00871
v FCGATE
v DEVTERM
Failing Item:
v FI00871
63A19103
v FI01112
tape unit.
v DEVTERM
63A19201
cable.
v SASCABL
63A19104
v FI01112

63A19202 • 63A19303
v FI00872
63A19220
v DEVTERM
v MEDIA
63A19202
Code was loaded.
Response: If the attached device is an external device, 63A19221
cable.
3. Ensure that the SCSI cable is seated correctly, and 63A19300
cable.
Failing Item:
Failing Item:
63A19301
v FI00871
current operation.

v FI00871
response.
63A19302
Failing Item:
63A19211 information on diagnositic tests that can be run to
v MEDIA
Failing Item:
63A19303
v FCGATE
v FI00872 v FCGATE
v DEVTERM

63A19304 • 63A19800
63A19304 63A19351
cartridge.
v USER v TAPCLN
v FI00871 v FI00871
63A19310 63A19355
v PTFSRCH
63A19320 2. Clean the tape unit.
cartridge.
Failing Item:
Failing Item:
v FI00130
v USER
v FI00871
v MEDIA
v TAPCLN
63A19321
v FI00871
error.
63A19500

v FCCODE
Failing Item:
63A19350 v PTFSRCH

on tape medium. 63A19501

63A19801 • 63B8C000
63A19801 63A19899
63A19802
63A19900
not upgraded.
not completed.
63A19803
63A19804 level of LIC, the IOP will attempt to load the new
LIC.
63A19901
63A19805 Explanation: Tape performance statistics logged.
logged for information only. 63A19902
63A19806
63A19903
63A19810 logged for information only.

should be replaced. 63A1FFF6
(Information Only.)

v STGDOCK
63B83202
Explanation: Unsupported device or storage dock.
63B8C000
Failing Item:

63B8C002 • 63B8C333
Explanation: This event is informational only. No v STGDOCK

service required.
63B8C110
63B8C002
Explanation: Driver abort, device not responding.
Explanation: Selection time-out, device not there or
not responding.
1. If the storage dock is remote then verify that the
Failing Item: cable is seated correctly at the adapter or system
v SVCDOCS unit and at the storage dock. If that does not resolve
the problem continue with the next step.
63B8C020 2. If the storage dock is remote then power off and
power on the storage dock. Verify that the device
Explanation: Configuration error. has power. If that does not resolve the problem
Failing Item: continue with the next step.
v SVCDOCS 3. Verify that the cartridge is not stuck or jammed. If
the cartridge is stuck or jammed and you cannot
free the cartridge then report this problem to your
63B8C022 service provider. Otherwise continue with the next
step.
capabilities. Reported media support may be 4. Report this problem to your service provider when
inaccurate. Function may be reduced. you have determined that the cable (if the device is
cable attached) is correctly seated and the device
Response: No action is required. This reference code has power.
Failing Item:
v SVCDOCS
v USB_CBL
v STGDOCK
required.
is not likely to cause a functional problem. 63B8C210
2. Verify that the backing device on the server is Explanation: Unexpected device condition.
varied on, operational, and not in exclusive use
by another partition. Once these things are Failing Item:
verified, IPL the virtual IOP on the client v STGCART
partition or vary the server partition's NWSD off v STGDOCK
and on.
63B8C300
v If this device is NOT a client virtual optical device: Explanation: Cartridge or dock error.
1. If no function reduction exists, no action is Failing Item:
required. v STGCART
2. This is likely a secondary error. Other PAL entries v STGDOCK
errors may have prevented identification of 63B8C304
device characteristics.) Explanation: Cartridge or media error.
applied. Failing Item:
v STGCART
63B8C100
63B8C333
Explanation: Bus error reported by device or the
device unexpectedly reset. Explanation: Medium incompatible.
v CHECK v STGCART

63B8C400 • 63B8CFF6
4. Unplug then replug connectors and cables using the

63B8C400
following procedure:
Explanation: Device or device interface error. v Disconnect the USB cable from the RDX docking
Failing Item: station so that the device can power off completely. If
the location of the adapter's USB port is not listed in
v STGDOCK
the Service Action Log (SAL) as part of the cable or
v STGCART device location use symbolic FRU USB_CBL to
determine the location of the USB port and cable or
63B8C401 device.
v Disconnect the power source for the RDX docking
Explanation: USB transport error. station.
Problem determination: If this refcode does not v Connect the RDX docking station to the power
appear in a serviceable event view then no service is source.
required. The event was logged when a device v After the power source is connected, connect the USB
disappeared while the USB transport did not appear to cable to the RDX docking station.
be in use. The device may have been unplugged or
powered off. Otherwise perform the following: v Try the device again before exchanging hardware.
1. Is the system a model S814 with feature EUA3? Failing Item:
v Yes - The storage dock is either the internal dock v CHECK

integrated into the front of the system unit or an v SVCDOCS
additional dock attached with an external USB cable. v USB_CBL
Licensed internal code (LIC) cannot tell the difference
v STGDOCK
but assumes the problem is with the internal dock.
The SRC is flagged for automatic call home and the v STORIOA
USB cable FRU will not appear in the serviceable v AJDGP01
event view. Work the failing items list and skip the
USB cable failing item if the dock is internal. If the
63B8C402
dock is internal this ends the procedure. Otherwise
continue with step 3. Explanation: Licensed Internal Code error.
v No - Continue with step 3 of this procedure. Failing Item:
v Don't know - Continue with the next step in this v AJDGP01
procedure.
2. Is the secondary code in the Product Activity Log 63B8CFF2

(PAL) or in the Service Action Log (SAL) 9913? Explanation: Device not ready.
v Yes - The storage dock is either the internal dock
integrated into the front of the system unit or an Failing Item:
additional dock attached with an external USB cable. v SVCDOCS
Licensed internal code (LIC) cannot tell the difference
but assumes the problem is with the internal dock.
63B8CFF4
The SRC is flagged for automatic call home and the
USB cable FRU will not appear in the serviceable Explanation: Unrecoverable device error.
event view. Work the failing items list and skip the
Failing Item:
USB cable failing item if the dock is internal. If the
dock is internal this ends the procedure. Otherwise v STGDOCK
continue with step 3.
v No - Continue with step 3 of this procedure. 63B8CFF6
Explanation: Temporary device error. If this event
3. Is the USB device an RDX storage dock?
appears in a serviceable event view then a service
v Yes - Continue with step 4 of this procedure. action is required. Otherwise this event is informational
v No - Unplug and replug connectors and cables. If the statistical only and no service is required.
location of the adapter's USB port is not listed in the
Failing Item:
Service Action Log (SAL) as part of the cable or
device location use symbolic FRU USB_CBL to v STGDOCK
determine the location of the USB port and cable or
device. Try the device again before exchanging
hardware. This ends the procedure.

63B8CFF7 • 63BCC023

63B8CFF7
action is required. Otherwise this event is informational
Explanation: Temporary device error. If this event statistical only and no service is required.
Failing Item:
statistical only and no service is required. v STGDOCK
Failing Item:
63B8FF09
v STGDOCK
Explanation: Device firmware update failed.
63B8CFF9 Problem determination: Examine the Secondary Code
for the event in the IBM i Service Action Log (SAL) or
Explanation: Cartridge or media error.
the IBM i Product Activity Log (PAL).
Failing Item:
Is the Secondary Code zero?
v STGCART
v NO - Remove the media in the dock and retry the
operation. If the problem persists work the failing
63B8CFFB item list.
Explanation: This event is informational only. No v YES - Work the failing item list.
service required. Failing Item:
v STGDOCK
63B8CFFE v AJDGP01
(63BC) Reference codes

63BC3202
Explanation: Unsupported device.
Failing Item:
v USB_DEV required.
63BCC000 is not likely to cause a functional problem.
Explanation: This event is informational only. No 2. Verify that the backing device on the server is
service required. varied on, operational, and not in exclusive use
63BCC002 partition or vary the server partition's NWSD off
Explanation: Selection time-out, device not there or and on.
not responding. 3. Ensure that the latest optical LIC PTFs have been
Failing Item:
v SVCDOCS
required.
63BCC020 2. This is likely a secondary error. Other PAL entries
Explanation: Configuration error. logged at approximately the same time as this
Failing Item: errors may have prevented identification of
v SVCDOCS device characteristics.)
63BCC022 applied.

capabilities. Reported media support may be 63BCC023
inaccurate. Function may be reduced. Explanation: Unable to determine all of the device
Response: No action is required. This reference code capabilities or the device characteristics are not

63BCC100 • 63BCC402

63BCC300
for this device. If a write is attempted, the device will
be marked failed. Explanation: Storage media or device error.
Problem determination: Optical device SRC xxxxC023 Failing Item:
is normally logged as informational. However, if the v USB_DEV
device is a USB DVD that is missing or not operational,
this SRC may be reported as a serviceable event with a
63BC storage device type. Ensure that the USB cable is 63BCC304
attached to the device and that the device has power. Explanation: Media error.
v SVCDOCS v USB_DEV
63BCC100 63BCC333
Explanation: Bus error reported by device or the Explanation: Medium incompatible.
device unexpectedly reset.
Failing Item:
Failing Item:
v USB_DEV
v USB_DEV
63BCC400
63BCC110
Explanation: Device or device interface error.
Explanation: Driver abort, device not responding.
Failing Item:
Problem determination: Use the following list of
possible causes as a guide. Some items may not apply v USB_DEV
to your device. Work down the list to eliminate
problem possibilities. 63BCC401
v If there is a cable from the adapter or system unit to
Explanation: USB transport error.
the device then verify that the cable is seated
correctly at both ends before replacing parts. Problem determination: If this refcode does not
v If the device has its own power source then power appear in a serviceable event view then no service is
off and power on the device. Verify that the device required. The event was logged when a device
has power before replacing parts. disappeared while the USB transport did not appear to
be in use. The device may have been unplugged or
v Try a different device in the same USB connection. If
powered off. Otherwise perform the following:
the different device functions properly then suspect
that the original device is either not supported or Unplug and replug connectors and cables. If the
failing. location of the adapter's USB port is not listed in the
Service Action Log (SAL) as part of the cable or device
If you have determined that none of the above are the location use symbolic FRU USB_CBL to determine the
cause of the problem then work the failing item list. location of the USB port and cable or device. Try the
device again before exchanging hardware. This ends
Failing Item: the procedure.
v SVCDOCS
Failing Item:
v USB_CBL
v SVCDOCS
v USB_DEV
v USB_CBL
v USB_DEV
63BCC210
v AJDGP01
Explanation: Unexpected device condition.
Failing Item: 63BCC402
v USB_DEV Explanation: Licensed Internal Code error.
Failing Item:
v AJDGP01

63BCCFF2 • 66003109

63BCCFF2
statistical only and no service is required.
Explanation: Device not ready.
Failing Item:
v SVCDOCS
63BCCFF9
63BCCFF4
Explanation: Media error.
Explanation: Unrecoverable device error.
Failing Item:
v USB_DEV
63BCCFFB
63BCCFF6
Explanation: This event is informational only. No
Explanation: Temporary device error. If this event service required.
63BCCFFE
Failing Item:
v USB_DEV action is required. Otherwise this event is informational
63BCCFF7 Failing Item:
Explanation: Temporary device error. If this event v USB_DEV

6600102E 66003020
v DISKDRV v DISKDRV
v STORIOA
66003002 v SASCABL
selection. 66003029
v DEVBPLN
v SASCABL 66003100
Failing Item:
66003010
v DISKDRV
IOA.
v SASCABL
v DISKDRV
v STORIOA 66003109
v SASCABL
v SASEXP

6600310C • 660070DD

v DISKDRV
v STORIOA 66004060
v SASCABL Explanation: Multipath redundancy level reduced.
v SASEXP
failed.
6600310C
Failing Item:
Explanation: Device bus error. v SIP3153
v SIP3250 v SASEXP
v DISKDRV
v STORIOA 66004061
6600310D
Explanation: Device bus error. restored. No service action is required.
Failing Item:
v SIP3250 66004100
v DISKDRV Explanation: Device bus fabric error.
v SIP3152
66003110 v SASCABL
Explanation: Device bus interface error occurred. v SASEXP
v DISKDRV v STORIOA
v STORIOA v DISKDRV
v SASCABL
v SASEXP 66007000

of code currently on the system. Contact your next 66007001
level of support. Explanation: Temporary disk data error.
660034FF
Failing Item:
v DISKDRV
660070DD

required.
Failing Item:

6600FFF3 • 6600FFFE
6600FFF3 6600FFFA
6600FFF4
Failing Item:
v DISKDRV
v DISKDRV v SASCABL
v STORIOA v SASEXP
6600FFF5 6600FFFB
6600FFFC
Failing Item:
v DISKDRV
6600FFF6
v DISKDRV
v STORIOA
Failing Item:
v DISKDRV
6600FFFD
6600FFF7
Failing Item:
v SIP3250
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
6600FFF9
6600FFFE
Failing Item:
Failing Item:
v DISKDRV
v SIP3150

6607102E • 66077000

v DISKDRV
6607102E
v STORIOA
v FI01106
v DISKDRV
66073109
66073002
Failing Item:
selection.
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v FI01106
v STORIOA
v FI01140
v BACKPLN
v FI01106
66073110
v FI01140

v DSKIP03
IOA. v STORIOA
v DISKDRV
Failing Item:
v FI01106
v DISKDRV
v FI01140
v STORIOA
v FI01140
66073130
v FI01141
level of support.
Failing Item:
configuration.
v SVCDOCS
Failing Item:
v DISKDRV
66073131
v FI01106
v STORIOA
66073029
Failing Item:
v SVCDOCS
66077000
66073100
occurred.
Failing Item:

66077001 • 6607FFFA

Failing Item:
66077001 v DISKDRV
6607FFF6
Failing Item:
66077003 v DISKDRV
6607FFF7
disk unit recovery.
66077004
Failing Item:
660770DD v DISKDRV
required. 6607FFF8
6607FFF2
v DISKDRV
Failing Item:
6607FFF3 v DISKDRV

6607FFF9
Failing Item:
v DISKDRV
6607FFF4
v DISKDRV v DISKDRV
v STORIOA
6607FFFA

6607FFFB • 67133110

v FI01141
v DISKDRV
6607FFFB v STORIOA
v FI01106
v FI01140
6607FFFE

v STORIOA
6713102E
v FI01140
v DISKDRV
67133002
selection.
67133100
Failing Item:
v DISKDRV occurred.
v STORIOA
Failing Item:
v BACKPLN
v DSKIP03
v FI01106
v DISKDRV
v FI01140
v STORIOA
v FI01106
67133010
v FI01140
IOA.
67133109
Failing Item:
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v FI01140
v STORIOA
v FI01141
v FI01106
v FI01140
67133020
67133110
configuration.
Failing Item:
Failing Item:
v DSKIP03
v DISKDRV
v STORIOA
v FI01106
v DISKDRV

67133130 • 6713FFF7
v FI01106
67137004
v FI01140
required.
67133130
Explanation: Device Licensed Internal Code. 671370DD
Response: The device is not supported with the level Explanation: System log entry only, no service action
of code currently on the system. Contact your next required.
level of support.
Failing Item: 6713FFF2
v SVCDOCS
Failing Item:
67133131
v DISKDRV
Response: The device does not support a needed 6713FFF3
Contact your next level of support. Explanation: Disk media format not valid.

v SVCDOCS v DISKDRV
67137000 6713FFF4
Explanation: Recoverable disk sector read error. Explanation: Disk device problem.

logged for information only. v DISKDRV
If this reference code appears in a serviceable event v STORIOA
Otherwise this event can be ignored. 6713FFF5
v DISKDRV
Failing Item:
service action is required. 6713FFF6
v DISKDRV
Failing Item:
system, initialize and format the disk. See Work with v DISKDRV
disk unit recovery.
6713FFF7

6713FFF8 • 67143029
If this reference code appears in a serviceable event view, work with the failing item list found there. If this
view then service is required, work the faling items list. event does not appear in a serviceable event view, no
Otherwise this event can be ignored. service action is required.
v DISKDRV v DISKDRV
v STORIOA
6713FFF8 v FI01140
Explanation: Temporary disk data error. v FI01141
v BACKPLN
event does not appear in a serviceable event view, no 6713FFFB
Failing Item:
6713FFF9 6713FFFE
v DISKDRV v DISKDRV
v STORIOA
6713FFFA v FI01106
Explanation: Temporary disk bus error. v FI01140

Failing Item:
6714102E
v DISKDRV
v STORIOA
v DISKDRV v FI01141
67143002 67143020
Explanation: Addressed device failed to respond to Explanation: Storage subsystem configuration error.
selection.
Failing Item: configuration.
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v BACKPLN
v FI01106
v FI01106
v STORIOA
v FI01140
v FI01140
67143010
67143029
IOA.

67143100 • 6714FFF3

67147000
occurred. If this reference code appears in a serviceable event
Failing Item:
v DSKIP03
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
v FI01106
67147001
v FI01140
67143109 Response: If this event appears in a serviceable event
v STORIOA v DISKDRV
v FI01106
v FI01140 67147003
67143110
Explanation: Disk bus interface error occurred. system, initialize and format the disk. See Work with
Failing Item: disk unit recovery.
v DSKIP03
v STORIOA 67147004
v DISKDRV Explanation: System log entry only. No service action

v FI01106 required.
v FI01140
671470DD
required.
Response: The device is not supported with the level 6714FFF2
level of support. Explanation: Disk motor problem.
v SVCDOCS v DISKDRV
67143131 6714FFF3
Explanation: Device or IOA Licensed Internal Code. Explanation: Disk media format not valid.
Response: The device does not support a needed Failing Item:
attribute and is running with degraded performance. v DISKDRV
Failing Item:
v SVCDOCS

6714FFF4 • 67173002
v DISKDRV
6714FFF4
6714FFF9
Failing Item:
v DISKDRV
v STORIOA
event does not appear in a serviceable event view, no 6714FFFA
Failing Item:
v DISKDRV
v FI01141
Failing Item: v BACKPLN
v DISKDRV
6714FFFB
6714FFF7
If this reference code appears in a serviceable event 6714FFFE
Failing Item:
Response: If this event appears in a serviceable event v STORIOA
view, work with the failing item list found there. If this v FI01106
Failing Item:

v DISKDRV
6717102E
67173002
Failing Item:

67173010 • 67177001

v DISKDRV
v STORIOA 67173110
v BACKPLN Explanation: Disk bus interface error occurred.
v FI01106
Failing Item:
v FI01140
v DSKIP03
v STORIOA
67173010
v DISKDRV
IOA.
v FI01140
Failing Item:
v DISKDRV 67173130
v STORIOA
v FI01140
v FI01141
level of support.
67173020
Failing Item:
Explanation: Storage subsystem configuration error. v SVCDOCS
Failing Item: Explanation: Device or IOA Licensed Internal Code.
v DISKDRV
v FI01106 attribute and is running with degraded performance.
v STORIOA Contact your next level of support.
v SVCDOCS
67173029
Response: No action required. This reference code is Explanation: Recoverable disk sector read error.
67173100
Explanation: Tape/optical or disk bus interface error view then service is required, work the faling items list.
occurred. Otherwise this event can be ignored.
v DSKIP03 v DISKDRV
v DISKDRV
v STORIOA 67177001
v FI01106 Explanation: Temporary disk data error.
v FI01140
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV

67177003 • 6717FFFB
v DISKDRV
67177003
6717FFF7
system, initialize and format the disk. See Work with
disk unit recovery. Response: No action required. This reference code is
67177004 If this reference code appears in a serviceable event
required.
Failing Item:
671770DD v DISKDRV

required. 6717FFF8
v DISKDRV
Failing Item:
v DISKDRV
6717FFF3
Explanation: Disk media format not valid. 6717FFF9
Failing Item: Explanation: Temporary disk data error.
v DISKDRV
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
6717FFFA
v DISKDRV
Failing Item:
v STORIOA
v DISKDRV
v FI01140
v FI01141
6717FFF6
v BACKPLN
Response: If this event appears in a serviceable event 6717FFFB
event does not appear in a serviceable event view, no Explanation: SCSI bus reset occurred.
service action is required. Response: No action required. This reference code is

6717FFFE • 67183131
Failing Item:
6717FFFE
v DISKDRV
v STORIOA
Response: If this event appears in a serviceable event v FI01106
v FI01140

6718102E 67183100
Explanation: Out of alternate sectors for disk storage. Explanation: Tape/optical or disk bus interface error
occurred.
Failing Item:
v DSKIP03
67183002 v DISKDRV
v STORIOA
v FI01140
Failing Item:
v DISKDRV
67183109
v STORIOA
v BACKPLN Explanation: IOA timed out a disk command.
v FI01140 v DISKDRV
v STORIOA
67183010 v FI01106
IOA.
v DISKDRV Explanation: Disk bus interface error occurred.
v FI01140 v DSKIP03
v FI01141 v STORIOA
v DISKDRV
67183020 v FI01106
Failing Item: Explanation: Device Licensed Internal Code.
v DISKDRV Response: The device is not supported with the level
v FI01106 of code currently on the system. Contact your next
v STORIOA level of support.
v SVCDOCS
67183029
Response: No action required. This reference code is Explanation: Device or IOA Licensed Internal Code.
logged for information only. Response: The device does not support a needed

67187000 • 6718FFF9

6718FFF4
Failing Item:
v DISKDRV
67187000 v STORIOA

6718FFF5
logged for information only. Explanation: Disk sector read error.
If this reference code appears in a serviceable event Response: If this event appears in a serviceable event
view then service is required, work the faling items list. view, work with the failing item list found there. If this
Otherwise this event can be ignored. event does not appear in a serviceable event view, no
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
67187001
6718FFF6
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
67187003
6718FFF7
system, initialize and format the disk. See Work with Response: No action required. This reference code is
disk unit recovery. logged for information only.
67187004 view then service is required, work the faling items list.
v DISKDRV
671870DD
6718FFF8
required. Explanation: Temporary disk data error.
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
6718FFF3
6718FFF9
Failing Item:

6718FFFA • 67193109

6718FFFB
Failing Item:
6718FFFA
6718FFFE
Failing Item:
Failing Item:
v DISKDRV
v DISKDRV
v STORIOA
v STORIOA
v FI01140
v FI01106
v FI01141
v FI01140
v BACKPLN

Failing Item:
6719102E
v DISKDRV
v FI01106
v DISKDRV v FI01140
67193002 67193029
Explanation: Addressed device failed to respond to Explanation: A device replacement has occurred.
selection.
v DISKDRV
v STORIOA 67193100
v BACKPLN
v FI01106 occurred.
v FI01140
Failing Item:
v DSKIP03
67193010
v DISKDRV
IOA.
v FI01106
v DISKDRV
v STORIOA 67193109
v FI01140
v FI01141
Failing Item:
v DISKDRV
67193020
v STORIOA
v FI01106
Response: If an MES is being installed, verify the v FI01140
configuration.

67193110 • 6719FFF6
67193110 67197003
Explanation: Disk bus interface error occurred. Explanation: Device format error.
Failing Item: Response: If the disk has not been formatted by the
v DSKIP03 system, initialize and format the disk. See Work with
disk unit recovery.
v STORIOA
v DISKDRV
67197004
v FI01106
required.
67193130
671970DD
Response: The device is not supported with the level required.
level of support.
6719FFF2
Failing Item:
v SVCDOCS
Failing Item:
67193131 v DISKDRV

6719FFF3
attribute and is running with degraded performance. Explanation: Disk media format not valid.
Contact your next level of support. Failing Item:
v SVCDOCS
6719FFF4
67197000 Explanation: Disk device problem.
Explanation: Recoverable disk sector read error. Failing Item:
view then service is required, work the faling items list. 6719FFF5
Failing Item:
v DISKDRV
event does not appear in a serviceable event view, no 6719FFF6
Failing Item:
v DISKDRV
Failing Item:

6719FFF7 • 6A590BAB

Failing Item:
v DISKDRV
v STORIOA
Otherwise this event can be ignored. v FI01140
v FI01141
Failing Item:
v BACKPLN
v DISKDRV
6719FFFB
6719FFF8
service action is required. 6719FFFE
Failing Item:
v DISKDRV
service action is required. v FI01106
v DISKDRV
6719FFFA

v FI00719
6A590AD2
v FI00718
Explanation: Communications adapter card test failed.
v FI00727
Failing Item:
v FI00718 6A590BA0
6A590AD3
Failing Item:
v FI00719
v FI00718
6A590BAB
6A590B25
Failing Item:

6A590BB0 • 6A590C70
v FI00718
6A590C40
Explanation: Synchronous-data-link-control
6A590BB0
send-receive test failed.
Failing Item:
v FI00719 v FI00718
v FI00718
6A590C43
6A590BD0
Explanation: Synchronous-data-link-control
Explanation: Communications adapter card test failed. send-receive test failed.

v FI00719 v FI00719
v FI00718 v FI00718
6A590BD1 6A590C50
Explanation: Communications adapter card test failed. Explanation: Binary synchronous control send-receive
test failed.
Failing Item:
v FI00718 v FI00719
v FI00718
6A590BEE
6A590C53
Explanation: I/O card Licensed Internal Code ended
abnormally. Explanation: Binary synchronous control send-receive
test failed.
Failing Item:
v FI00718 v FI00719
v FI00718
6A590C10
6A590C60
Explanation: Asynchronous send-receive test failed.
Failing Item:
v FI00718 v FI00719
v FI00727 v FI00718
6A590C20 6A590C63
Explanation: Communications adapter card test failed. Explanation: Asynchronous send-receive test failed.

v FI00719 v FI00719
v FI00718 v FI00718
6A590C30 6A590C70
Explanation: Adapter card failed modem interface Explanation: Communications adapter card test failed.
test. Failing Item:
v FI00719 v FI00718
v FI00718

6A590C80 • 6B253100
Failing Item:
6A590C80
v FI00719
v FI00718
Failing Item:
v FI00719 6A595007
v FI00718
Explanation: Diagnostic wrap test completed; no
errors detected.
6A590C90
Explanation: Communications adapter card X.21 test 6A595008
failed.
Explanation: Diagnostic wrap test completed; error
Failing Item: was detected.
v FI00718 v FI00719
v DPAC
6A590CA1 v FI00718
Failing Item: 6A59FFFF
v FI00719 Explanation: User suspected problem.
v USER
6A590CC0

Failing Item:
6B22XXXX
v VIRTDRV
Explanation: Event logged in client for a virtual drive
being provide by an I/O host.

Failing Item:
6B23XXXX
v VIRTDRV

Failing Item:
6B24XXXX
v VIRTDRV

v SVCDOCS
6B253020
Explanation: VIOS hosted, I/O processor detected a
6B253100
Explanation: VIOS hosted, I/O processor card
detected interface error. If this event appears in a
serviceable event view then it requires service.
Change the configuration.
Otherwise it can be ignored.
Failing Item:

6B253120 • 6B259903
This event will be logged as informational during v Check the Product Activity Log for other entries that
LPAR migrations and can be ignored. indicate interface problems and work those
problems.
Failing Item:
v VIOSLOG
PTFs.
v FCINTF
v ANYFC your next level of support with the information you
v FCIOA have gathered.
v OPT_CLN Problem determination: IPL the IOP to retry the
6B253120 contact your service provider.
Explanation: VIOS hosted, I/O processor detected a Failing Item:

port failure. If this event appears in a serviceable event v PTFSRCH
view then it requires service. Otherwise it can be
ignored.
6B258100
This event may be logged as informational during
Explanation: VIOS hosted, recovered Fibre Channel
LPAR migrations and can be ignored.
interface error.
Failing Item:
Failing Item:
v FCCABLE
v AJDGP01
v FCPORT
v FCIOA
6B258130
v VIOSLOG
Explanation: VIOS hosted, recovered Fibre Channel
v FCDEV
interface error.
v OPT_CLN
6B253140
Explanation: VIOS hosted, I/O Processor detected that 6B258301
a port is now operational.
Explanation: VIOS hosted, unexpected fibre channel
Response: This reference code and the 3120 reference error detected.
since the port is now operational. Failing Item:
v NEXTLVL
6B253400
6B259500
Explanation: VIOS hosted, I/O processor card
detected device error. Explanation: Internal program error in driver code.
v FCDEV v PTFSRCH
v FCINTF
v ANYFC 6B259903
v FCIOA Explanation: Tape device information was logged.
v OPT_CLN Informational event, no service required.
6B253405
model.

6B643002 • 72073400

Failing Item:
6B643002
v SASEXP
v SASCABL
v STORIOA
v DEVBPLN
failure. Verify that input power to the expansion unit 6B648404
close the xxxx3002 problems. Otherwise work the 6B64FFF4
Failing Item:
Failing Item:
v SASEXP
v SASEXP
v SASCABL
v SASCABL
v STORIOA
v STORIOA
v DEVBPLN
v DEVBPLN
6B643109
backplane command.

indications.
72073000
Explanation: I/O adapter hardware error detected. I/O processor.
v FI01112 v TAPCNFG
v FI00871
72073202
Explanation: Tape unit configuration error. 72073400
Response: Before exchanging any parts, verify that the Explanation: Device error has occurred.

72079020 • 72079104
Failing Item: 4. If there is a gateway device attached, refer to the

v DEVTERM
v FI00871
v FI01103
v FI01106 If the attached tape device is owned by a Virtual I/O
72079020
Failing Item:
v FCIOA
v FCDEV
v FCCABLE
Processor that does not support Tape and Dasd
devices at the same time. 72079102
v An unsupported device type or model is attached. Explanation: Gateway device detected a SCSI interface
v TAPCNFG Response: Use the gateway device service
v FI00871 documentation to analyze the problem.
v FI00871
72079100 v FCGATE
tape unit. v DEVTERM
do the following before exchanging any parts: 72079103
1. Ensure that the signal cable is seated correctly, and Explanation: Interface error detected by system or by
that there are no bent or damaged pins on the cable. tape unit.
the cable.
If the attached tape device is owned by a Virtual I/O the ports.
Server partition refer to Troubleshooting the Virtual 2. Ensure that the device has power.
Failing Item:
v FI01112
Failing Item:
v FI00872
v FI00871
v DEVTERM
v FI01112
v SASCABL
72079101
Explanation: Fibre Channel interface error detected. 72079104
Response: If the attached device is an external device, Explanation: Interface error detected by system or by
do the following before exchanging any parts: tape unit.
1. Ensure that the USB cable is correctly connected to
3. If there is a switch or hub attached, verify that it is the ports.
operational.

72079200 • 72079220

72079202
Code was loaded.
Failing Item:
v USB_IOA
v USB_CBL
72079200 cable.
that there are no bent or damaged pins on the cable. Failing Item:
3. For a SCSI attached device ensure that a v FI00871
v DEVTERM
I/O Server to determine the parts to replace. 72079210
Failing Item: Explanation: Illegal or unsupported tape unit
v FI00871 response.
v FI00872 v FI00871
v DEVTERM v FI01112
v PTFSRCH
72079201
Explanation: Tape unit command timeout. 72079211
Response: If the attached device is an external device, Explanation: Gateway device detected a bus protocol
do the following before exchanging any parts: error.
1. Ensure that the device is powered on. Response: Use the gateway device service
2. If an interposer is required, make sure that it is documentation to analyze the problem.
connected between the I/O processor and the SCSI Failing Item:
cable.
v FCGATE
v FCIOA
cable. v FI00871
4. Ensure that a terminating plug is attached to the v ANYFC
device end of the SCSI cable. v FCCABLE
5. If the attached tape device is owned by a Virtual v FI00872
I/O Server partition it may be necessary to reset the v DEVTERM
v FI00871
v FI01112
v FI00872
v DEVTERM processor to be reset. Reset the I/O processor before
v MEDIA using the device.

72079221 • 72079351
v FI00871
72079221
72079310
is not correct.
Failing Item:
72079300
v PTFSRCH
v FI00871
Failing Item:
v FI00871 72079320
72079301 failure.
current operation.
v FI00871
error.
72079302
Explanation: Tape device failure or media error. documenation to analyze the problem.
Response: The tape unit detected a failure that may Failing Item:
be caused by a hardware failure or a media error. v FCCODE
information on diagnositic tests that can be run to 72079350
Failing Item: on tape medium.
v MEDIA
v FI00871 Clean the tape unit and retry the operation.
72079303 exchange the tape media.
Explanation: Gateway device failure. Failing Item:
documenation to analyze the problem. v TAPCLN
v FCGATE
72079351
72079304 Explanation: Tape with excessive error rate was
cartridge.
v USER v FI00871

72079355 • 72079900
72079355 72079803
72079804
Failing Item:
v USER 72079805
72079500
72079806
Failing Item:
v PTFSRCH
72079810
72079501
Explanation: Licensed Internal Code error. should be replaced.
Failing Item: Response: This reference code is used for ending
v PTFSRCH Online Problem Analysis with a list of failing items.
(Information Only.)
72079800
72079899
temporary I/O error. Explanation: Problem analysis completed, the problem
has been corrected.
logged for information only. Response: This reference code is used for ending
72079801
Response: No action required. This reference code is not upgraded.
72079802 not completed.
Explanation: System successfully recovered from The tape unit will continue to operate with the
temporary I/O error. previous LIC. You may do either of the following:

72079901 • 78D11518
v Perform TUPIP04 to reset the IOP and the tape unit. Explanation: An IOP dump was initiated.
LIC.
72079903
Failing Item:
v USER Explanation: Tape device information logged.

7207FFF6
logged for information only. Explanation: Tape volume statistics logged (no action
required).
72079902

78D11511
Explanation: An over temperature warning occurred that detected the problem are in the FRU list of the
on power supply 1. serviceable event. Before starting a repair action for this
Problem determination: Check for other fan failure
errors from the same enclosure. If you find any fan
errors from the same power supply in the same
enclosure logged at about the same time then close this
problem and work those errors. Otherwise work the
failing items. Failing Item:
Failing Item: v DISKPWR
v AMBTMP1 v DEVBPLN
v DISKPWR v SASEXP
78D11515 78D11517
Explanation: A fatal error occurred on power supply Explanation: A fatal error occurred on power supply
1. 1.

to the I/O storage unit. The unit and power supply v DEVBPLN
v SASEXP
unit was not interrupted at the time the SRC was 78D11518
the same time then no service is required and this Explanation: An over temperature error occurred on
problem can be closed. power supply 1.
Failing Item: Problem determination: Check for other fan failure

errors from the same enclosure. If you find any fan
v DISKPWR errors from the same power supply in the same
v DEVBPLN enclosure logged at about the same time then close this
v SASEXP problem and work those errors. Otherwise work the
failing items.

v AMBTMP1
1. v DISKPWR

78D11519 • 78D11529
78D11519 78D11526
Explanation: An AC loss was detected on power Explanation: A fatal error occurred on power supply
supply 1. 2.
Problem determination: Verify that AC power was Problem determination: This SRC can be the result of
present for power supply 1 at the time this error was a loss of utility power, battery back up or UPS power
logged and is currently present. If you determine that to the I/O storage unit. The unit and power supply
this problem was due to the loss of AC power then that detected the problem are in the FRU list of the
work that issue and close this problem. Otherwise serviceable event. Before starting a repair action for this
work the failing items. problem verify that utility power, BBU or UPS to the
Failing Item:
v PWRCORD the same time then no service is required and this
v DISKPWR problem can be closed.
Failing Item:
78D1151A v DISKPWR
1. v SASEXP
Failing Item:
v DISKPWR 78D11527
78D11521 2.
Explanation: An over temperature warning occurred Failing Item:
on power supply 2. v DISKPWR
Problem determination: Check for other fan failure v DEVBPLN
errors from the same enclosure. If you find any fan v SASEXP
problem and work those errors. Otherwise work the 78D11528
failing items. Explanation: An over temperature error occurred on
Failing Item: power supply 2.
v AMBTMP1 Problem determination: Check for other fan failure
v DISKPWR errors from the same enclosure. If you find any fan
78D11525 problem and work those errors. Otherwise work the
Explanation: A fatal error occurred on power supply failing items.
2. Failing Item:
Problem determination: This SRC can be the result of v AMBTMP1
serviceable event. Before starting a repair action for this 78D11529
problem verify that utility power, BBU or UPS to the Explanation: An AC loss was detected on power
unit was not interrupted at the time the SRC was supply 2.
the same time then no service is required and this Problem determination: Verify that AC power was
problem can be closed. present for power supply 2 at the time this error was
logged and is currently present. If you determine that
Failing Item: this problem was due to the loss of AC power then
v DISKPWR work that issue and close this problem. Otherwise
v DEVBPLN work the failing items.
v PWRCORD

78D1152A • 78D17325
v DISKPWR
78D17313
Explanation: Over temperature error on power supply
78D1152A
1, Un-P1-E1.
Failing Item:
2.
v DISKPWR
Failing Item:
v DISKPWR
78D17315
78D13002
1, Un-P1-E1.
Failing Item:
v DISKPWR
unit at about the same time suspect an input power 78D17316
failure. Verify that input power to the expansion unit Explanation: Over temperature error on power supply
power supplies was active at the time of the error. If 1, Un-P1-E1.
unit was not able to log a reference code for the input Failing Item:
power failure. Restore power to the expansion unit and v DISKPWR
78D17317
Failing Item:
v SASEXP 1, Un-P1-E1.
v SASCABL
Failing Item:
v STORIOA
v DISKPWR
v DEVBPLN
78D17321
78D13109
Explanation: I/O adapter timed out a device 2, Un-P1-E2.
backplane command.
Failing Item:
Failing Item:
v DISKPWR
v SASEXP
v SASCABL
78D17322
v STORIOA
v DEVBPLN Explanation: Over temperature error on power supply
2, Un-P1-E2.

v DISKPWR
1, Un-P1-E1.
78D17323
Failing Item:
v DISKPWR Explanation: Over temperature error on power supply
2, Un-P1-E2.

v DISKPWR
1, Un-P1-E1.
78D17325
Failing Item:
v DISKPWR Explanation: Over temperature error on power supply
2, Un-P1-E2.
Failing Item:

78D17326 • 78D17431
v DISKPWR
78D17421
Explanation: Over temperature error on enclosure
78D17326
services manager (ESM) 2 at location Un-P1-C2.
Failing Item:
2, Un-P1-E2.
v SASEXP
Failing Item:
v DISKPWR
78D17422
78D17327
Failing Item:
2, Un-P1-E2.
v SASEXP
Failing Item:
v DISKPWR
78D17425
78D17411
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D17426
78D17412
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D17427
Explanation: Over temperature error on midplane,
78D17413
Un-P1.
Explanation: Over temperature error on midplane,
Failing Item:
Un-P1.
v DEVBPLN
Failing Item:
v DEVBPLN
78D17431
Explanation: The enclosure services manager (ESM) at
78D17415
location Un-P1-C1 failed to communicate with the ESM
Explanation: Over temperature error on enclosure at location Un-P1-C2.
Failing Item: 1. If reference code 78D17441 is in the service action
v SASEXP log (SAL) with a status of "NEW" and it was
logged at about the same time as this reference
code and is listing FRUs for the same enclosure go
78D17416 to step 3. Otherwise continue with the next step.
Explanation: Over temperature error on enclosure 2. Replace the ESM at location Un-P1-C1. If the
services manager (ESM) 1 at location Un-P1-C1. problem persists, replace the ESM at location
Un-P1-C2. If the problem persists after you
Failing Item:
replaced both ESMs, replace the midplane
v SASEXP assembly at location Un-P1. This ends the
procedure.
3. Each ESM is having a problem communicating
with the other ESM. Both reference codes may
have been logged with the same resource identifier

78D17432 • 78D17441
or with unique resource identifiers. Examine the

78D17441
fault indicators for both ESMs at locations
Un-P1-C1 and Un-P1-C2. Explanation: The enclosure services manager (ESM) at
4. If both fault indicators are active (amber LEDs are location Un-P1-C2 failed to communicate with the ESM
on solid) or neither of the fault indicators are at location Un-P1-C1.
active (amber LEDs are not on solid but may be Response: Perform the following:
blinking) go to step 6. Otherwise continue with the
1. If reference code 78D17431 is in the service action
next step.
log (SAL) with a status of "NEW" and it was
5. Only one of the fault indicators is active. Replace logged at about the same time as this reference
the ESM with the active fault indicator using the code and is listing FRUs for the same enclosure go
exchange procedure in Knowledge Center. If the to step 3. Otherwise continue with the next step.
problem persists, replace the other ESM. If the
2. Replace the ESM at location Un-P1-C2. If the
problem persists after you replaced both ESMs,
problem persists, replace the ESM at location
replace the midplane assembly at location Un-P1.
Un-P1-C1. If the problem persists after you
This ends the procedure.
6. Record the enclosure type, model and serial assembly at location Un-P1. This ends the
number of the ESM location code in one of the procedure.
two service action log (SAL) entries.
3. Each ESM is having a problem communicating
7. Go to SST/DST in the logical partition that with the other ESM. Both reference codes may
reported the problems. have been logged with the same resource identifier
8. Select Start a service tool. or with unique resource identifiers. Examine the
9. Select Hardware service manager. fault indicators for both ESMs at locations
Un-P1-C1 and Un-P1-C2.
10. Select Packaging hardware resources.
4. If both fault indicators are active (amber LEDs are
11. Locate the enclosure using the type, model and
on solid) or neither of the fault indicators are
serial number of the ESM that you recorded from
active (amber LEDs are not on solid but may be
one of the SAL entries.
blinking) go to step 6. Otherwise continue with the
12. Select the Hardware contained within package next step.
option for the disk expansion unit you recorded.
5. Only one of the fault indicators is active. Replace
13. For each packaging resource with the description the ESM with the active fault indicator using the
"Device Services" in locations P1-C1 and P1-C2 exchange procedure in Knowledge Center. If the
select the "Associated logical resource(s)" option. problem persists, replace the other ESM. If the
14. Examine the status of both ESM resources with the problem persists after you replaced both ESMs,
description "Device Services". replace the midplane assembly at location Un-P1.
15. If one of the ESM resources does not have a status This ends the procedure.
of "Operational", continue with the next step. 6. Record the enclosure type, model and serial
Otherwise, go to step 17. number of the ESM location code in one of the
16. Replace the ESM that does not have a status of two service action log (SAL) entries.
"Operational" using the exchange procedure in 7. Go to SST/DST in the logical partition that
Knowledge Center. If the problem persists, replace reported the problems.
the other ESM. If the problem persists after you 8. Select Start a service tool.
9. Select Hardware service manager.
assembly at location Un-P1. This ends the
procedure. 10. Select Packaging hardware resources.
17. Close the 78D17441 SAL entry. Go to step 2. 11. Locate the enclosure using the type, model and
serial number of the ESM that you recorded from
Failing Item: one of the SAL entries.
v SASEXP 12. Select the Hardware contained within package
v DEVBPLN option for the disk expansion unit you recorded.
13. For each packaging resource with the description
78D17432 "Device Services" in locations P1-C1 and P1-C2
select the "Associated logical resource(s)" option.
Explanation: VPD read failure in enclosure services 14. Examine the status of both ESM resources with the
manager (ESM) 1 at location Un-P1-C1. description "Device Services".
Failing Item: 15. If one of the ESM resources does not have a status
v SASEXP of "Operational", continue with the next step.
Otherwise, go to step 17.

78D17442 • 78D1751C
16. Replace the ESM that does not have a status of

78D17515
"Operational" using the exchange procedure in
Knowledge Center. If the problem persists, replace Explanation: Under voltage sensor error in enclosure
the other ESM. If the problem persists after you services manager (ESM) 1 at location Un-P1-C1.
Failing Item:
assembly at location Un-P1. This ends the
procedure. v SASEXP
17. Close the 78D17431 SAL entry. Go to step 2.
78D17516
Failing Item:
v SASEXP Explanation: Over voltage sensor error in enclosure
v DEVBPLN
Failing Item:
78D17442 v SASEXP
Explanation: VPD read failure in enclosure services

manager (ESM) 2 at location Un-P1-C2. 78D17517
Failing Item: Explanation: Under voltage sensor error in enclosure

v SASEXP
Failing Item:
78D17510 v SASEXP
Explanation: Over voltage sensor error in enclosure

services manager (ESM) 1 at location Un-P1-C1. 78D17518
Failing Item: Explanation: Over voltage sensor error in enclosure

v SASEXP
Failing Item:
78D17511 v SASEXP
Explanation: Under voltage sensor error in enclosure

services manager (ESM) 1 at location Un-P1-C1. 78D17519

v SASEXP
Failing Item:
78D17512 v SASEXP

services manager (ESM) 1 at location Un-P1-C1. 78D1751A

v SASEXP
Failing Item:
78D17513 v SASEXP

services manager (ESM) 1 at location Un-P1-C1. 78D1751B

v SASEXP
Failing Item:
78D17514 v SASEXP

services manager (ESM) 1 at location Un-P1-C1. 78D1751C

v SASEXP
Failing Item:

78D1751D • 78D1752B
v SASEXP
78D17524
78D1751D
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D17525
78D1751E
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D17526
78D1751F
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D17527
78D17520
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D17528
78D17521
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D17529
78D17522
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D1752A
78D17523
Failing Item:
v SASEXP
Failing Item:
v SASEXP
78D1752B
Failing Item:

78D1752C • 78D17542
v SASEXP
78D17532
78D1752C
manager (ESM).
Response: If there was a power supply problem
logged at about the same time then close this SRC and
Failing Item: work the power supply problem. Otherwise perform
v SASEXP the following for failing item SASEXP:
Replace the ESM at location Un-P1-C2. If the problem
78D1752D persists, replace the ESM at location Un-P1-C1. If the
problem persists after you replaced both ESMs,
Explanation: Under voltage sensor error in enclosure continue with the next failing item.
Problem determination: A failure was detected
Failing Item: reading ESM 2 VPD at location Un-P1-C2. The failure
v SASEXP may have happened when ESM 1 at location Un-P1-C1
was attempting to read the VPD in ESM 2 at location
Un-P1-C2. If there was a power supply problem logged
78D1752E at about the same time then close this SRC and work
Explanation: Over voltage sensor error in enclosure the power supply problem.
services manager (ESM) 2 at location Un-P1-C2. Failing Item:
v SASEXP v DISKPWR
v DEVBPLN
78D1752F
Explanation: Under voltage sensor error in enclosure 78D17541
services manager (ESM) 2 at location Un-P1-C2. Explanation: VPD read failure in enclosure services
Failing Item: manager (ESM).
v SASEXP Response: If there was a power supply problem
work the power supply problem. Otherwise perform
78D17531
the following for failing item SASEXP:
manager (ESM).
persists, replace the ESM at location Un-P1-C1. If the
Response: If there was a power supply problem problem persists after you replaced both ESMs,
logged at about the same time then close this SRC and continue with the next failing item.
reading ESM 2 VPD at location Un-P1-C2. The failure
Replace the ESM at location Un-P1-C1. If the problem may have happened when ESM 1 at location Un-P1-C1
persists, replace the ESM at location Un-P1-C2. If the was attempting to read the VPD in ESM 2 at location
problem persists after you replaced both ESMs, Un-P1-C2. If there was a power supply problem logged
continue with the next failing item. at about the same time then close this SRC and work
the power supply problem.
reading ESM 1 VPD at location Un-P1-C1. The failure Failing Item:
may have happened when ESM 2 at location Un-P1-C2 v SASEXP
was attempting to read the VPD in ESM 1 at location
v DISKPWR
at about the same time then close this SRC and work v DEVBPLN
v SASEXP Explanation: VPD read failure in enclosure services
v DISKPWR manager (ESM).
v DEVBPLN Response: If there was a power supply problem

78D17600 • 78D176C4

78D17644
persists, replace the ESM at location Un-P1-C2. If the Failing Item:
problem persists after you replaced both ESMs, v DISKFAN
continue with the next failing item.
Problem determination: A failure was detected 78D17654
reading ESM 1 VPD at location Un-P1-C1. The failure
may have happened when ESM 2 at location Un-P1-C2 Explanation: A fatal error occurred on fan 5.
was attempting to read the VPD in ESM 1 at location Failing Item:
at about the same time then close this SRC and work v DISKFAN
v SASEXP Explanation: A fatal error occurred on fan 6.
v DEVBPLN v DISKFAN
78D17600 78D17674
Explanation: Fan status. Explanation: A fatal error occurred on fan 7.
Failing Item:
78D17601
v DISKFAN
Explanation: Fan status.
78D17684
78D17603
Explanation: Fan status.
Failing Item:
v DISKFAN
78D17604
Explanation: A fatal error occurred on fan 16. 78D17694
v DISKFAN
Failing Item:
v DISKFAN
78D17614
Explanation: A fatal error occurred on fan 1. 78D176A4
v DISKFAN
Failing Item:
v DISKFAN
78D17624
Explanation: A fatal error occurred on fan 2. 78D176B4
v DISKFAN
Failing Item:
v DISKFAN
78D17634
Explanation: A fatal error occurred on fan 3. 78D176C4
v DISKFAN
Failing Item:
v DISKFAN

78D176D4 • 94299020
Explanation: System log entry. SES enclosure dump

78D176D4
created.
Problem determination: If this SRC appears in
Failing Item: serviceable event view then collect the dump for
v DISKFAN analysis by the next level of support if requested.
Otherwise no service action is required.
78D176E4 Failing Item:

v DMPFILE
Failing Item:
78D1FFF4
v DISKFAN
78D176F4 Failing Item:

v SASEXP
v SASCABL
Failing Item:
v STORIOA
v DISKFAN
v DEVBPLN
78D18405

To resolve the device failure, complete the following steps:

2. Check the device for any error indications. To resolve errors, see the device maintenance information.
Yes: You corrected the problem. This ends the procedure.
No: If a reference code is in the serviceable event view, complete the service action that is
indicated in the following table for the reference code.
94293000
Explanation: I/O adapter hardware error detected. v An unsupported device type or model is attached.
v FI00131 v TAPCNFG
v TAPMLB
94293202 v FI01103
Explanation: Tape library configuration error. v FI01106
following conditions are not present: 94299020
v The attached tape library device type or model is Explanation: Tape library configuration error.
only supported on an I/O adapter that is attached to
an I/O processor. Response: Before exchanging any parts, verify that the
Failing Item:
Failing Item:
v TAPCNFG
v TAPCNFG
v TAPMLB
94293400
v PTFSRCH

94299100 • 94299201
If the attached tape library is owned by a Virtual I/O

94299100
Explanation: Interface error detected by system or by I/O Server to determine the parts to replace.
tape library.
Failing Item:
Response: Do the following before exchanging any v TAPMLB
parts:
v FI01112
v SASCABL
terminating plug is attached to the device end of 94299200
the cable. Explanation: Tape library is not responding.
If the attached tape library is owned by a Virtual I/O Response: Do the following before exchanging any
Server partition refer to Troubleshooting the Virtual parts:
I/O Server to determine the parts to replace. 1. Ensure that the device is powered on.
Failing Item: 2. Ensure that the signal cable is seated correctly, and
v TAPMLB
v FI01112
v FI00872 the SCSI cable.
v DEVTERM
94299101
Failing Item:
Response: Do the following before exchanging any v TAPMLB
parts:
v FI01112
v FI00872
v DEVTERM
operational. 94299201
4. Refer to the tape library service documentation for Explanation: Tape library command timeout.
Response: Do the following before exchanging any
parts:
Server partition refer to Troubleshooting the Virtual 1. Ensure that the device is powered on.
I/O Server to determine the parts to replace. 2. If an interposer is required, make sure that it is
Failing Item:
cable.
v FCIOA
v FCDEV that there are no bent or damaged pins on the SCSI
v FCCABLE cable.
94299103 device end of the SCSI cable.
5. If the attached tape library is owned by a Virtual
I/O Server partition it may be necessary to reset the
tape library.
Response: Do the following before exchanging any
Failing Item:
parts:
v TAPMLB
the ports. v FI01112
2. Ensure that the device has power. v FI00872
v DEVTERM
v MEDIA

94299202 • 94299501
94299202 94299301
Explanation: Tape library failed after Licensed Internal Explanation: Library device failure, redundancy lost.
Code was loaded.
Response: The tape library device detected a
Response: Do the following before exchanging any hardware failure that does not prevent the tape library
parts: device from completing the current operation.
1. Ensure that the device is powered on. Failing Item:
2. If an interposer is required, make sure that it is v TAPMLB
cable.
94299310
that there are no bent or damaged pins on the SCSI Explanation: Licensed Internal Code for the tape
cable. library is not correct.
4. Ensure that a terminating plug is attached to the Failing Item:
v PTFSRCH
Failing Item: v TAPMLB
v TAPMLB
v FI01112 94299320
v FI00872
Explanation: Tape library Licensed Internal Code
v DEVTERM failure.
Failing Item:
94299210
v FI00130
Explanation: Illegal or unsupported tape library v TAPMLB
response.
v TAPMLB
Explanation: The media type is incorrect; the tape
v FI01112 cannot be used.
v PTFSRCH
Response: The tape library has detected that the
specified cartridge does not have a supported media
94299220 type or that the tape media is defective.
Explanation: Hardware configuration change detected. Use a different tape cartridge.
Response: The tape device or tape library device has Failing Item:
reported a configuration change that requires the I/O v MEDIA
using the device. v TAPMLB
94299221 94299500
Explanation: I/O path change occurred. Explanation: Licensed Internal Code error.
Response: No action required. This reference code is Response: If the system is operational, perform a
logged for information only. dump of the I/O processor data.
Failing Item:
94299300 v PTFSRCH
94299501
Failing Item:
v TAPMLB Explanation: Licensed Internal Code error.
Failing Item:
v PTFSRCH

94299800 • 94299903

94299800
94299900
Explanation: Licensed Internal Code for tape library
was not upgraded.
94299801
Internal Code (LIC) to the programmable tape library
Explanation: System successfully recovered from was not completed.
The tape library will continue to operate with the
Response: No action required. This reference code is previous LIC. You may do either of the following:
logged for information only. v Wait for next IPL when the system will attempt to
94299802 v Perform TUPIP04 to reset the IOP and the tape
library. When the IOP is reset, if the device has the
wrong level of LIC, the IOP will attempt to load the
new LIC.
Failing Item:
v USER
94299803
94299901
temporary I/O error. Explanation: Tape performance statistics logged.
Response: No action required. This reference code is Response: No action required. This reference code is
logged for information only. logged for information only.
94299804 94299902
temporary I/O error. Response: No action required.
Explanation: Tape library information logged.
94299805
Explanation: System successfully recovered from logged for information only.
(A1xx) Reference codes

An A1xx system reference (attention) code is an attention code posted by the service processor. An A1xx
SRC offers information about a platform or service processor dump, confirms a control panel function
request, or indicates an issue with a service processor wake-on-LAN setting. The A1xx table uses the
following format:
v The reference code contains numbers that identify a particular action your server performs during
initialization of firmware.
v The description offers a brief description about this SRC. It may also contain instructions for
continuing the problem analysis.
v The FRU List offers a link to instructions or service actions for recovering from a hang on an attention
code. Click the FRU List only when you experience a hang condition on an attention code. For
example, a hang condition occurs when your server performs a requested action but the SRC in the
control panel display does not change for several minutes and the service processor appears to be
hung.

A1003000 • A1A3C100
A1003000 A1008008
Explanation: Informational message: the platform Explanation: Confirm fast power-off (control panel
dump was successful. If the system hangs on this function 08)
progress code, perform FSPSPC1.
Response: This attention code is displayed on the
control panel after you request a fast power-off (panel
A1003001 function 08). When you see this code, scroll to function
08 again on the panel and press Enter to perform the
Explanation: Reserved (for platform dump). If the
fast power-off. If the system hangs on this progress
system hangs on this progress code, perform FSPSPC1.
code, perform isolation procedure FSPSPC1.
A1003022
A1008009
Explanation: Confirm partition dump (control
Explanation: Beginning emergency power off (EPO)
(operator) panel function 22).
countdown. If the system hangs on this progress code,
Response: The control panel displays this attention perform isolation procedure FSPSPC1.
code after you request a partition dump (panel function
22). When you see this code, scroll to function 22 again
A100800A
on the panel and press Enter to perform the partition
dump. If the system hangs on this progress code, Explanation: Proceeding with EPO. This SRC displays
perform FSPSPC1. after the countdown has completed successfully. If the
system hangs on this progress code, perform isolation
procedure FSPSPC1.
A1003042
Explanation: Confirm platform dump (control panel
A1703000
function 42)
Explanation: A user-initiated Platform System Dump
Response: The control panel displays this attention
was requested.
code after you request a platform dump (panel function
42). When you see this code, scroll to function 42 again
on the panel and press Enter to perform the platform A181D000
dump. If the system hangs on this progress code,
Explanation: The hypervisor did not respond to a
perform isolation procedure FSPSPC1.
ROLE or FAILOVER message. If the system hangs on
this progress code, perform isolation procedure
A1003043 FSPSPC1.
Explanation: Confirm service processor dump (control
panel function 43) A181D001
Response: The control panel displays this attention Explanation: The hypervisor did not post an Xdown
code after a service processor dump (panel function 43) interrupt when a reset/reload occurred. If the system
is requested. When you see this code, scroll to function hangs on this progress code, perform isolation
43 again on the panel and press Enter to perform the procedure FSPSPC1.
service processor dump. If the system hangs on this
progress code, perform isolation procedure FSPSPC1.
A1A3C100
Explanation: Invalid operational mode for remote
A1008003
power on (wake onLAN)
Explanation: Confirm restart IPL control (operator)
Response: Check the service processor settings for
panel function 03.
remote power on. If the system hangs on this progress
Response: The control panel displays this attention code, perform isolation procedure FSPSPC1.
code after a restart IPL (panel function 03) is requested.
When this SRC is displayed, scroll to function 03 again
on the panel and press enter to perform the restart IPL.
If the system hangs on this progress code, perform
isolation procedure FSPSPC1.

A2002250 • A2002485

No service action is required.
as LP=xxx in decimal format. The platform LIC for this
A2002250
partition attempted an operation. There was a failure.
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 v NEXTLVL
as LP=xxx in decimal format. A slot that was needed
for the partition was unavailable. See the Symbolic FRU
SLOTUSE for more information on the cause of this A2002426
error. Explanation: A problem occurred during the IPL of a
Failing Item: partition.
v SLOTUSE Response: The partition ID is in extended word one
A2002300
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. A slot that was needed
for the partition was unavailable. See the Symbolic FRU A2002475
SLOTUSE for more information on the cause of this Explanation: A problem occurred during the IPL of a
error. partition.
Failing Item: Response: The partition ID is in extended word one
v SLOTUSE as LP=xxx in decimal format. A slot that was needed
for the partition was either empty or the device in the
slot has failed. See the Symbolic FRU SLOTUSE for
A2002310
more information on the cause of this error.
If you have a RAID enablement card (CCIN 5709) on
partition.
your system, it will disable an embedded SCSI adapter.
Response: The partition ID is in extended word one If that embedded slot is called out in the error, you can
as LP=xxx in decimal format. The platform LIC for this safely ignore this error.
Failing Item:
v SLOTUSE
Failing Item:
v NEXTLVL
A2002477
A2002320
partition.
partition.
Response: The partition ID is in extended word one
A2002479
partition attempted an operation. There was a failure. Explanation: A problem occurred during the IPL of a
Contact your next level of support. partition.
Failing Item: Response: No service action required.
v NEXTLVL
A2002485
A2002425 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

A2002820 • A2009005

A2006068
Explanation: An update of adapter firmware or
Failing Item:
firmware managing system resources is available.
v NEXTLVL
A2006070
A2002820
Explanation: The mapping load identifier changed for
Explanation: A problem occurred during the IPL of a a firmware resource.
partition.
Response: No service action required. A2006072
Explanation: The Physical Function firmware resource
A2002830 configuration load identifier changed.
partition. A2006074
Response: No service action required. Explanation: The Virtual Function firmware resource
configuration load identifier changed.
A2002840
Explanation: A problem occurred during the IPL of a A2006076
partition. Explanation: A firmware resource configuration load
Response: No service action required. identifier changed.
A2002850 A2006078
Explanation: A problem occurred during the IPL of a Explanation: A firmware resource load identifier
partition. changed.

A2008080
A2002875 Explanation: System log entry only, no service action

required
partition. Response: No service action required.

A2008108
A20028B0 Explanation: A problem occurred during the IPL of a

partition.
partition.
A200811F
Explanation: The IPL of a partition has been stopped
for debug.
A20028C0
partition.
A2009005
Explanation: A system firmware resource is waiting
for a parent partition to indicate that it is ready for the
A2003123 system firmware resource to become active.
Explanation: System log entry only, no service action Response: No service action required.
required

A2009010 • A2D03006
A2009010 A200B07B
Explanation: A problem occurred during the IPL of a Explanation: System log entry only, no service action
partition. required
A2009015
Explanation: The IPL of a partition is waiting during A200C220
recovery of memory.
partition.
A2009020
Explanation: A problem occurred during the IPL of a A200C225
partition.
partition.
A2009030
Explanation: The IPL of a partition is waiting for A200C230
reserved memory.
partition.
A2009040
Explanation: The IPL of a partition is waiting for an A2D03000
adapter physical function to become available.
Explanation: User-initiated immediate termination and
MSD of a partition.
A2009050
Explanation: The IPL of a partition is waiting for an
adapter virtual function to become availble.
A2D03001
Explanation: User-initiated RSCDUMP of RPA
A2009055
partition's PFW content.
Explanation: The IPL of a partition is waiting
firmware resources to become available.
A2D03002
A2009060
Explanation: User-initiated RSCDUMP of IBM i
Explanation: The firmware is dumping migration
partition's SLIC bootloader and PFW content.
memory.
A2009065
A2D03004
Explanation: The firmware is waiting for a coherently
attached accelerator to report ready. Explanation: User-initiated LPADUMP for the
firmware resource.
A2009070
A2D03005
Explanation: The firmware is waiting for a valid
Universal Unique Identifier (UUID). Explanation: User-initiated non-disruptive LPADUMP
for the firmware resource.
A200A205
A2D03006
Explanation: The firmware is waiting for a the power
off message from the partition. Explanation: User-initiated update of adapter
firmware or firmware update of the firmware
managing system resources.

A2D03008 • A6000210
A2D03008 A2D03010
Explanation: User-initiated forced termination and Explanation: The Hypervisor initiated an LPADUMP.
MSD of a partition.

Explanation: Terminate Immediate data is not valid.
A6000000
Failing Item:
Explanation: Operating system status code.
v LICIP08
Response: This reference code is for information only.
v AJDG301
It is shown in the Product activity log as a side effect of
a condition that was detected by LIC.
A6000107
Normally, no action should be taken as a result of
information reference codes. However, to isolate the Explanation: Main storage dump must be copied for
root cause, use these suggestions: service.
1. Examine the date and time of the informational Response: The server detected an unrecoverable
reference code. machine check condition.
2. Determine if any other reference codes have been
logged at or before the same date and time. Collect all the words of the SRC and the main store
dump and send to your system manufacturer for
3. Begin the service approach based on these other analysis.
logged errors.
A6000109
A6000102
Explanation: An unrecoverable memory error
Explanation: A machine check occurred during IPL. occurred.
Response: Words 2 to 9 of this SRC contain additional Response: Re-IPL the partition that terminated. Then,
diagnostic information. Record SRC words 1 through 9 look for and correct errors with SRCs of the form
before attempting to IPL again and report the problem B1xxxxxx in the Serviceable Event View that indicate
to your Software Service Provider. the replacement of memory in the failing item list. If
there are no B1xxxxxx SRCs in the Serviceable Event
A6000103 View that indicate a memory problem, perform a slow
boot by using Performing a slow boot in order to run
Explanation: Main storage dump must be copied for diagnostics on the memory. Then, look for and correct
service. errors with SRCs of the form B1xxxxxx in the
Failing Item: Serviceable Event View.
v LICIP01 Failing Item:
v SVCDOCS
A6000104
Explanation: Terminate Immediate reference code is A6000202
bad. Explanation: Unrecoverable read error.
Failing Item: Response: Restore the Licensed Internal Code using
v LICIP08 Utilities to install and restore IBM i Licensed Internal
v AJDG301 Code.
A6000105 A6000210
Explanation: More than one request to terminate the Explanation: The system ASP has run out of disk
system was issued. storage.
Failing Item: Response: The out of storage condition in the system

ASP can be caused by an allocation failure in some
v LICIP08
other system software. This could be a looping
v AJDG301 condition that continues to allocate storage. Contact
your service representative for assistance with the Main
A6000106 Storage Dump.

A6000231 • A6000308
v FI00500
A6000231
v FI00302
Explanation: Disk sanitize action completed
v FI00301
successfully.
v AJDG301
Response: No service action required. This entry is
A6000299
A6000232 Explanation: Informational LIC state SRC.
Explanation: Disk sanitize action did not complete

successfully. A6000302
Response: Provide the Product Activity Log entry to Explanation: Recursion in exception handler.
your next level of support for analysis. This SRC is an IBM i software event. If this SRC was
reported as a serviceable event or if this SRC appears
A6000244 on the IBM i LPAR's panel then report the SRC as an
IBM i software problem.
Explanation: Contact was lost with the device
indicated. Failing Item:
v LICIP08
Response: Do not power off the system.
v AJDG301
Perform the procedure indicated in the failing item list.
Failing Item: A6000304
v LICIP13
Explanation: Component specific exception handler
v FI00580 return code not valid.
v FI00500
Failing Item:
v FI00302
v LICIP08
v FI00301
v AJDG301
v AJDG301
A6000305
A6000255
Explanation: Exception while storage management
Explanation: Contact was lost with the device lock is held.
indicated.
Failing Item:
v LICIP08
Perform the procedure indicated in the failing item list. v AJDG301
Failing Item:
v LICIP13 A6000307
v FI00580 Explanation: LIC exception code detected a problem.
v FI00500
Response: Component Specific Exception Handler
v FI00302 recursion is detected in an IBM i Operating System
v FI00301 process.
v LICIP08
A6000266 v AJDG301
Explanation: Contact was lost with the device
indicated. A6000308
Response: Do not power off the system. Explanation: LIC exception code detected a problem.
Perform the procedure indicated in the failing item list. Response: Component Specific Exception Handler
Failing Item: recursion is detected in an IBM i Operating System
process.
v LICIP13

A6000317 • A6000402
v LICIP08
A6000329
v AJDG301
Explanation: LIC exception code detected a problem.
A6000317 Failing Item:

v LICIP08
Explanation: Traceback for code not found.
v AJDG301
Failing Item:
v LICIP08
A6000333
v AJDG301
Explanation: A branch to a bad address was
attempted.
A6000323
Failing Item:
v LICIP08
v LICIP08
v AJDG301 A6000334
Explanation: Exception Handler could not be
A6000324 removed.
Explanation: LIC exception code detected a problem. Failing Item:
Failing Item: v LICIP08
v LICIP08 v AJDG301
v AJDG301
A6000335
A6000325 Explanation: Code resumed to not valid address
Explanation: LIC exception code detected a problem. following exception.

v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6000326 A6000336
Explanation: LIC exception code detected a problem. Explanation: LIC exception code detected a problem.
v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6000327 A6000401
Explanation: LIC exception code detected a problem. Explanation: A machine check occurred during IPL.

v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6000328 A6000402
Explanation: LIC exception code detected a problem. Explanation: A machine check occurred during
authority initialization.
Failing Item:
Failing Item:
v LICIP08
v LICIP08
v AJDG301
v AJDG301

A6000403 • A6000418
A6000403 A6000411
Explanation: Unhandled exception during IPL or Explanation: Unhandled exception in commit
install. recovery.
v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6000405 A6000412
Explanation: Unhandled exception in authority Explanation: Unhandled exception in commit
recovery. initialization.
v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6000406 A6000413
Explanation: Unhandled exception in data base Explanation: Rebuild of recovery object index failed.
recovery.
Failing Item:
v LICIP08 v AJDG301
v AJDG301
A6000414
A6000407
Explanation: Install of operating system failed on read
Explanation: Unhandled exception in data base from media.
initialization.
Failing Item:
v LICIP08 v FI00300
v AJDG301
A6000415
A6000408
Explanation: Create user profile failed.
Explanation: Unhandled exception in journal recovery.
Failing Item:
v LICIP08 v AJDG301
v AJDG301
A6000417
A6000409
Explanation: Initiating the initial process failed.
Explanation: Unhandled exception in journal
Failing Item:
synchronization.
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
A6000418
Explanation: The information loaded from the install
A6000410
media is not valid.
Explanation: Unhandled exception in journal clean up.
Failing Item:
v LICIP08 v AJDG301
v AJDG301

A6000419 • A6000507
A6000419 A6000443
Explanation: The information loaded from the install Explanation: Programmed IPL command failure.
media is not valid.
Failing Item:
v LICIP08 v AJDG301
v AJDG301
A6000446
A6000420
Explanation: Error during machine termination.
Explanation: The information loaded from the install
Failing Item:
media is not valid.
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
A6000447
Explanation: Failure to reach MI boundary.
A6000421
Failing Item:
Explanation: Bad return code creating a queue or
message. v LICIP08
v AJDG301
Failing Item:
v LICIP08
A6000449
v AJDG301
Explanation: Exception in MI boundary manager.
Explanation: The Load/Dump command failed. v LICIP08
v AJDG301
Failing Item:
v LICIP08
A6000506
v AJDG301
Explanation: Attempt to destroy a task with critical
flag on.
A6000439
Failing Item:
Explanation: Opening the IPCF connection failed.
v LICIP08
Failing Item:
v AJDG301
v LICIP08
v AJDG301
A6000507
Explanation: A critical process terminated. This SRC
A6000440
will be in the LPAR's panel.
Explanation: Termination code is not valid.
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 AJDG301 This is a secondary affect of the process termination
request for a critical process that was caused by a
system error condition that began process termination.
A6000441
The system error condition that began process
Explanation: Power off system command failed. termination is most commonly a storage error or LIC
exception handling.
Failing Item:
v LICIP08 Response: Perform LICIP08 - save and send in the
Main Store Dump, collect LIC and Product Activity
v AJDG301 Logs.
Failing Item:

A6000607 • A6001103
v LICIP08 to install and restore IBM i Licensed Internal Code.

v AJDG301 For more information, contact IBM Service Support.
Failing Item:
A6000607
v AJDG301
Explanation: Maximum stack size exceeded in process
or task.
A6000901
Failing Item:
Explanation: The LinkLoader has found its bad flag
v LICIP08 ON.
v AJDG301
Response: This reference code is usually the result of
a system termination while the LinkLoader is
A6000620 performing its work.
Explanation: Event management index is not usable. Reinstall the Licensed Internal Code by using Utilities
to install and restore IBM i Licensed Internal Code.
Failing Item:
v LICIP08
A6000902
v AJDG301
Explanation: Unable to perform programmed IPL.
A6000650 Response: The LinkLoader was not successful in
performing a programmed IPL.
Explanation: Resource management segment could
not be created or extended. Perform a system IPL. If the problem persists, examine
the main storage dump and determine the reason for
Response: A main store dump was initiated.
the failure of the programmed IPL.
Words 2 to 9 of this SRC contain additional diagnostic
information. Record SRC words 1 through 9.
A6000903
Perform a system IPL and collect the Product activity
Explanation: The LinkLoader was not able to allocate
log and main store dump and provide them along with
a segment.
the recorded SRC information to IBM Service Support.
Response: Perform the D mode IPL again. If the
The problem may also be that there is not enough
problem persists, there might be a memory problem.
auxiliary storage.
Failing Item:
v AJDG301 A6000904
Explanation: The LinkLoader was not able to load a
A6000801 critical LID.
Explanation: Invalid LID directory detected. Response: Perform the D mode IPL again. If the
Response: During system IPL, the LIDMgr detected problem persists, contact your next level of support.
an I/O failure or media failure while trying to read the
LID directory. A6001001
Failing Item: Explanation: Enqueuing a task to the TDQ which is
v LICIP08 already enqueued on TDQ.
v FI00300 v LICIP08
v AJDG301 v AJDG301
A6000802 A6001103
Explanation: LID directory unusable. Explanation: MISR not readable; must be readable for
Response: During system IPL, the LIDMgr detected Normal Mode install.
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

A6001104 • A60041FC
v AJDG301
A6001104
Explanation: Failure reading media or not install
A6001724
media.
Explanation: An attempt to create a segment failed.
Response: Determine that correct install media is
loaded. If correct install media is installed, media could Response: The create could fail for two reasons:
be corrupt. Obtain another copy of the install media v A code problem. Perform the procedure indicated in
and re-attempt the install. If the install still fails, contact the failing item list.
your service representative.
v No free auxiliary storage on the system. Add
additional DASD if the create failed because no
A6001201 auxiliary storage was available.
Explanation: Critical database segment could not be Failing Item:
created. v LICIP08
v LICIP08
v AJDG301 A6001730
Explanation: An IPL is needed to restore system
A6001204 performance.
Explanation: Error in constraint enforcement. Response: Licensed Internal Code has detected a
condition that is impacting system performance. System
Failing Item:
operation can continue, but system performance may
v LICIP08 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',
A6001210 the error was caused by too much processor memory
being installed.
Explanation: Object not found in the in-use table.
For more information, contact IBM Service Support.
Failing Item:
v AJDG301 v UPLF1
A6001215 A6003000
Explanation: Error in critical code sequence. Explanation: LPAR service function directed a Main
Storage Dump.
Failing Item:
Response: Copy the current main storage dump to
v LICIP08
media. For more information on how to copy a Main
v AJDG301 Storage Dump, refer to Copying a main storage dump.
Failing Item:
A6001219
v AJDG301
Explanation: A back leveled driver has been detected.
Failing Item: A60041FC
v LICIP08 Explanation: Installation of LIC failed.
v AJDG301
Response: Words 12 and 13 of this SRC contain
additional diagnostic information.
A6001604
Install LIC using physical media.
Explanation: Not able to create APPN task.
To determine what caused the failure, collect SRC
Response: An error occurred during task creation information and contact your next level of support.
which requires a power off of the system.
Failing Item:
v LICIP08

A60041FD • A6004422
A60041FD A6004405
Explanation: Installation of LIC failed. Explanation: System ASP threshold exceeded after
auto copy done.
Response: A main store dump was initiated. Words 12
and 13 of this SRC contain additional diagnostic Response: Delete other system ASP copies or exit the
information. Main Storage Dump Manager and then from DST copy
the Auto Copy to media and then delete the Auto Copy
To recover the partition using the previously installed
in system ASP.
LIC, perform a B-mode IPL. You can then re-try the
installation of LIC. Otherwise, install LIC using
physical media. A6004420
To determine what caused this failure, collect SRC Explanation: MSD Manager not configured to save
information and main store dump and contact your dump information.
next level of support.
Response: The platform produced dump data, but the
Failing Item: Main Storage Dump (MSD) Manager was not
v SVCDOCS configured to automatically copy the dump to an
Auxiliary Storage Pool (ASP). The dump will be lost if
the system power is lost. Use MSD Manager to
A6004401 manually copy the current platform dump to media or
Explanation: Missing DASD units. an ASP.

media. A6004421
For more information on how to perform a Main Explanation: Insufficient space in the ASP to store a
Storage Dump, refer to Copying a main storage dump. platform dump.
Response: The platform produced dump data, and the
A6004402 Main Storage Dump (MSD) Manager was configured to
automatically copy the dump to an Auxiliary Storage
Explanation: Missing DASD units. Pool (ASP), but there was not sufficient free space
available in the ASP. The dump will be lost if the
system power is lost. Manually copy the current
media. Then exit the Main Storage Dump Manager.
platform dump from the platform by performing one of
For more information on how to perform a Main the following:
Storage Dump, refer to Copying a main storage dump. v Make room in the designated ASP and then use the
MSD Manager to copy the current platform dump to
A6004403 ASP.
v Use the MSD Manager to delete other dump copies,
Explanation: Storage Management failed to reach full
then copy the current platform dump to ASP.
paging.
v Use the MSD Manager to copy the current platform
Response: Copy the current main storage dump to dump to a different ASP.
media.
For more information on how to perform a Main dump to media.
Storage Dump, refer to Copying a main storage dump.
A6004422
A6004404
Explanation: A platform dump is saved in MSD
Explanation: Auto copy failed or not attempted. Manager.
Response: Copy the current main storage dump. If Response: The platform produced dump data. The
copying to system ASP, existing copies may need to be dump data was copied to the Main Storage Dump
deleted or renamed. Then exit the Main Storage Dump (MSD) Manager.
Manager.
Failing Item:
For more information on how to perform a Main v PLDUMP

A6004700 • A6004733
item since it has been swapped in from a different

A6004700
system.
Explanation: Processor On Demand error detected.
Put the Processor Capacity Card back in the system it
Response: Processor on Demand Data Block key is not came from, and reinstall this system's original Processor
valid. Capacity Card.
Replace the Processor Capacity card. Failing Item:
Failing Item: v CTLPNCD
v CTLPNCD
A6004714
A6004701 Explanation: The CUoD data is not present. A
problem may exist.
Response: The Processor Capacity Card was changed
Response: Processor On Demand Data Block contains
and there may be a problem.
data that does not match the expected data.
If the system did have any activated standby
Contact your service provider.
processors before the Processor Capacity Card was
Failing Item: replaced, then new processor on demand activation
v AJDG301 codes must be obtained to restore the previous
activations.
A6004703 Contact your service provider.

A6004715
Response: Processor On Demand Serialization has
failed during IPL. Explanation: Processor On Demand error detected.
Contact your service provider. Response: Correct any Processor Capacity card or
SPCN failures.
Failing Item:
Failing Item:
v AJDG301
v CTLPNCD
A6004710
A6004730
Response: SPCN communication failure during
Processor On Demand. Response: Processor On Demand standby processors
are in use.
Look in the Product Activity Log for other SPCN errors
and perform the actions indicated for those errors. Contact your service provider.

v SPNLCRD v AJDG301
A6004712 A6004731
Explanation: Processor On Demand error detected. Explanation: Processor On Demand error detected.
Response: Correct any Processor Capacity card or Response: The Processor On Demand Trial Activation
SPCN failures. period is not valid. Contact your next level of support.

v CTLPNCD v AJDG301
A6004713 A6004733
Explanation: Incorrect Processor Capacity Card Explanation: Processor On Demand error detected.
installed. Response: Contact your service provider.
Response: The Processor Capacity Card is the failing Failing Item:
v AJDG301

A6004740 • A6005007
v AJDG301
A6004740
v FI00380
Response: The Processor On Demand Activation code A6005003
just entered is not valid.
Explanation: Service program failed.
Response: The ASCII system console failed to
Failing Item: respond.
v AJDG301
Failing Item:
v FI00320
A6004741
v FI00602
Explanation: Processor On Demand error detected. v USER
Response: An invalid Processor On Demand v AJDG301
Activation code has been entered more than 5 v FI00380
consecutive times. Contact your service provider.
Failing Item: A6005004
v AJDG301
Explanation: DST console failed to respond.
Response: The system console failed to respond.
A6004745
Failing Item:
Explanation: Processor Capacity card replaced on
activated POD system. v RTRIP02
v FI00320
Response: Contact IBM Support to order a
replacement Processor On Demand activation code. v FI00602
v USER
A6004747 v AJDG301
v FI00380
Explanation: 1 hour left in POD 14 day Trial
Activation Period.
A6005005
Response: If a new activation code was purchased, it
should be entered now. Otherwise, the system will Explanation: Service program failed.
revert back to its previous activation state at the end of
the Trial Activation Period. Response: The workstation adapter system console
failed to respond.

v WSAIP01
Explanation: DST received no response from a work
station controller. v FI00320
v FI00602
Response: The workstation I/O processor for the
system or partition console did not respond. v USER
v AJDG301
Failing Item:
v FI00380
v RTRIP01
v FI00380
A6005007
v AJDG301
A6005002 Response: The workstation adapter console failed to
respond.
Explanation: DST problem attempting to use the
system console. Failing Item:
Response: A code problem occurred during an v RTRIP07
attempt to use the system console. v FI00320
v LICIP03 v USER

A6005008
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
A6005008 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
– The twinaxial-related SRC is represented by the active but the PC failed to connect. Are the PC and
first 4 characters. system on the same network and using the same
v yy where: protocol? Can the PC ping the system? (ping
– 0A = No console tagged serverhostname). Word 4 contains the IP address.
Word 5 may contain the card position or serial
v zz where: number of the adapter.
– 00 = Not defined by user (old default value)
Problem determination: Look at words 3-8 on the
– 01 = Twinaxial console. If words 3-5 are non-zero the failing item is
– 02 = Operations Console (Direct) (obsolete) most likely an ASYNC card. If words 6-8 are non-zero
– 03 = Operations Console (LAN ) the failing item is most likely a LAN card.
– 04 = Hardware Management Console (HMC) or Word 7 meanings for the failure identified:
Thin Console v 1 Async card not detected.
v 2 No cables detected. Word 8 is the Card position.
If you are attempting to use Operations Console, the
Word 9 is the card type.
local console on a network uses words 3, 4, and 5. Use
words 3 through 5 to select the appropriate section in v 3 Wrong cable detected. Word 8 is the card position.
the following list. Word 9 is the cable ID.
1. Word 3 is "1": No supported HW detected or HW v 4 Port in use. Word 8 is the card position. Word 9 is
detected is not expected (for example, you replaced the card type.
the LAN IOA so the serial number is different) In v FA Not configured for direct cable
some cases the serial number of the expected
adapter may be shown in word 5. Note: It is expected that a D-mode IPL with a new load
2. Word 3 is "2": The LAN IOA failed to report. source direct access storage device (DASD) will show
3. Word 3 is "3": Hardware error. Common error codes the console type value of 00. Examples of when this
in word 4: can occur might be that the copy of data from a failing
DASD did not copy all data or you are installing a new
v 53001A80 and 53002AC0: Network, cable or the logical partition. Also, there are times when the DASD
LAN adapter may not be operational. Word 5 is late reporting and the console type value was not
may contain the card position or serial number of retrieved in time. In these cases you can use the
the adapter. console service function to set a console type value or
attempt to contact the console again.

A6005010 • A6005120
Failing Item: v If reference code A6xx5090 is displayed on the

v OPCIP03 control panel for more than 10 minutes, perform the
procedure indicated in the failing item list.
v FI00719
v For reference code B6xx5090, perform the procedure
indicated in the failing item list.
A6005010
Failing Item:
Explanation: IPL service function ended abnormally.
v LICIP11
v LICIP04 v FI00500
v AJDG301 v FI00301
v FI00021
A6005014 v FI00065
Explanation: DST status. The Storage Management v AJDG301
Dual Path Information Screen option to dump data to a
PAL has completed successfully.
A6005092
Explanation: System is in DASD migration mode.
A6005015
Response: Install Licensed Internal Code and Upgrade
Explanation: DST error. An error has occurred
Load Source was specified but the key is not in the
gathering data for the Storage Management Dual Path
manual position. Change the key position to manual
Information Screen option to dump data to a PAL.
and perform a system IPL.
Contact your next level of support or hardware service
provider.
A6005094
Failing Item:
v NEXTLVL Explanation: IASP detected a failure during the vary
on operation.

v LICIP12
Explanation: DST lost contact with the console.
Response: A service program lost contact with the
A60050FF
system console.
Explanation: DST unrecoverable program error.
Failing Item:
v RTRIP03 Failing Item:
v AJDG301 v LICIP03
v USER v AJDG301
v FI00380
A6005083
A6005120
Explanation: IPL service function ended abnormally.
Explanation: System LIC detected a program
Response: A service program lost contact with the
exception.
system console.
Response: System LIC detected a programming
Failing Item:
problem. If performance or other system degradation is
v TWSIP01 occurring, the system may be operating with reduced
v AJDG301 resources.
v USER Check the Product activity log for related entries. If this
reference code is logged with an error class of
A6005090 Informational, then no action is required.
Explanation: System startup failed in unattended IPL Otherwise, perform the procedure indicated in the
mode. failing item list.
Response: Perform the following: Failing Item:

v LICIP01
v AJDG301

A6005121 • A6005192
v FI00130
A6005127
A6005121
Failing Item:
Explanation: LIC program exception occurred.
v DISKDRV
v STORIOA
problem for which a main storage dump may have
been initiated. Collect the dump if available. v FI01106
v DISKTRY
A problem log entry may be generated for this refcode.
v FI01140
Failing Item:
v FI01141
v LICIP01
v DEVTERM
v AJDG301
v BACKPLN
A6005122
A6005128
Explanation: I/O processor failure.
Response: System LIC detected an IOP programming
Failing Item:
problem for which an IOP dump may have been
initiated. v FI01112
v FI01107
Failing Item:
v LICIP01
A600512D
v FI00130
v AJDG301 Explanation: An IOP dump was initiated.
v FI00131 Response: Copy the IOP dump entry and any related
entries from the Product Activity Log to suitable media,
and give to an IBM service representative.
A6005123
A600512E
Response: System LIC detected an interface problem
with the IOP or an IOP programming problem for
which an IOP and main storage dump may have been Response: The system was in a D IPL mode when the
initiated. problem was detected. A main storage dump was not
taken.
Failing Item:
v FI00130 v LICIP01
v AJDG301 v AJDG301
v FI00131 v FI00130
A6005126 A6005192
Explanation: Addressed device failed to respond to Explanation: Insufficient entitled memory for the I/O
selection. configuration.
Failing Item: Response: Use the hardware management console to

increase the entitled memory capacity of the partition
v DISKDRV
and restart the I/O adapter. To restart a storage I/O
v STORIOA adapter, use Hardware Service Manager to re-IPL the
v DISKTRY virtual I/O processor that is associated with this I/O
v FI01106 adapter. To restart a communications I/O adapter, vary
the line off and vary it on using the vary configuration
v FI01140 (VRYCFG) command.
v FI01141
Failing Item:
v DEVTERM
v SVCDOCS
v BACKPLN

A6005193 • A6005310
This reference code is logged for information only. No

A6005193
action is required.
Explanation: Virtual adapter not supported in a
shared memory partition.
Response: Use the hardware management console to Otherwise this event can be ignored.
remove the virtual adapter from the partition.
Failing Item:
v SVCDOCS v FI00318
v FI00065
A6005194 v FI00130
Explanation: Insufficient entitled memory for the I/O v AJDG301
configuration.
Response: Use the hardware management console to A6005275
Explanation: The system issued a reset/reload to the
and restart the partition.
IOP.
Failing Item:
Response: System Licensed Internal Code detected
v SVCDOCS that an IOP Reset/Reload has occurred, and that the
IOP successfully recovered.
A6005206 Users who were signed on to a Workstation device
Explanation: System LIC detected a missing IOP LIC under the IOP will need to sign back on. Any
code load. LAN/WAN communications lines under the IOP will
need to be restarted. Tape/Optical devices under the
Response: System LIC detected a missing IOP LIC IOP may need to be varied back on.
code load during IPL of the IOP. This indicates that
either the IOP code load is not installed on the system To determine the cause of the IOP Reset/Reload, check
Load Source device or that system LIC was unable to the Product Activity Log for additional entries logged
successfully read that load from the Load Source with the same System Log ID, and perform any actions
device. indicated for those errors.
Failing Item:
A6005276
v LICIP01
v USER Explanation: IOP Reset was issued.
Response: LIC has detected a problem with the
A6005209 Service Processor IOP and has reset it but has not
initiated reload of the Service Processor.
Explanation: System LIC detected an IOP timeout
during IOP IPL. If the Load Source is mirrored, some system operations
may be able to continue normally. However, some
Response: Verify that all IOP cable connections are system service operations have been suspended and the
secure, and check tape and other non-disk devices and system should be scheduled for power down as soon
media to verify that they are in a ready state. as possible.
v LICIP01 v RTRIP08
v USER v AJGLD01
v FI00130 v AJDG301
v AJDG301 v FI00021
A6005219 A6005310
Explanation: LIC program exception occurred. Explanation: LIC program exception occurred.
Response: An IOP signaled to system LIC that it had Response: System LIC detected a logical partition
entered a critical internal state. LIC automatically configuration data consistency error. Copy the Product
attempted to restart the IOP. Activity Log data for this error and any related entries

A6005311 • A6005350
and contact your next level of hardware service approximately the same time. Perform the actions
support. indicated for those entries.
Failing Item:
v LPARSUP A6005341
Explanation: Secondary partition not running at
A6005311 optimum.
Explanation: LIC program exception occurred. Response: Check the primary partition Product
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 A6005342
this SRC to be reported:
v Non-configured disk unit which was previously a
optimum.
load source on a partitioned system.
v Load Source configuration data does not match Response: Check the Primary partition's Product
partition for which it is being used. Activity Log for system processor entries from
approximately the same time. Perform the actions
v Load Source configuration data does not match
indicated for those entries.
system serial number for which it is being used.
v Load Source configuration data is newer than
primary partition configuration data. A6005343
Failing Item: Explanation: Secondary partition not running at

optimum.
v LPRIP01
v LPARSUP Response: Check the Primary partition's Product
Activity Log for system memory errors from
A6005312 indicated for those entries.
Response: LPAR configuration data informational A6005344
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.

v LPARSUP
Response: LPAR configuration data informational
A6005350
error.
Explanation: Secondary partition software release not
The LPAR configuration data was found to be
supported.
inconsistent on a primary partition and could only be
corrected with an older copy of the data. Response: The logical partition software version is
outside the supported release delta.
Failing Item:
v LPARCFG Check the Release Delta from the Primary partition
"Display Partition Release Level" screen.
A6005340 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
Activity Log for system processor entries from

A6005380 • A6006906
A6005380 A6006901
Explanation: LIC program exception occurred. Explanation: Bus Expansion Adapter card failed.
Response: Record the Product Activity Log (PAL) hex Response: Contact your next level of support.
data for this SRC or print the PAL entry.
Failing Item:
Contact your next level of support. v NEXTLVL
Failing Item:
v LPARSUP A6006902
Explanation: Bus Expansion Adapter card failed.
A6005390
Failing Item:
Response: Record the Product Activity Log (PAL) hex v NEXTLVL
Contact your next level of support. A6006905
Failing Item: Explanation: Optical bus failed.
v LPARSUP
Failing Item:
A6005505
v NEXTLVL
Explanation: The copying of DASD log data to the
IOP log was successful.
A6006906
Response: IOP log data can be copied to a spool file
for examination by the development lab. Explanation: High Speed Link (HSL) or PCI bridge
card slot I/O bridge failure.
A6005555 Response: LIC could not access part of the HSL I/O
bridge VPD. The bridge and HSL loop may be
Explanation: SLIC I/O DASD subsystem error prevented from becoming operational.
recovery in progress.
For this reference code the failing item list presented in
the Service Action Log (SAL), or serviceable event
A6005600 viewer you are working with, can be different from the
Explanation: Unrecoverable read error. failing item list documented here. That is due to the
differences in system models and features installed.
Response: VPD data could not be read.
If the Service Action Log (SAL) or serviceable event
Look for other errors implicating hardware. There is no view on the hardware management console is available
way to know what VPD read has failed, but the then use the failing item list presented there for
resource is not usable and should generate an error. servicing this reference code.
If no such error occurred, call your next level of If a serviceable event view is not available then use the
support. failing item list documented here. By following the
Failing Item: procedures in the symbolic FRUs listed here you will
isolate to the correct FRU list based on system model
v SVCDOCS and features installed.
NOTE: A fiber optic cleaning kit may be required for
A6006900 optical HSL connections.
Explanation: System bus error. Failing Item:
Response: Contact your next level of support. v SIIOADP
v NEXTLVL

A6006907 • A6006910
Failing Item:
A6006907
v SIIOADP
Explanation: High Speed Link (HSL) or PCI bridge
v OPT_CLN
Response: LIC detected invalid data in the HSL I/O
A6006909
bridge VPD. The bridge and HSL loop may not have
become operational. Explanation: High Speed Link (HSL) or PCI bridge
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.
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
failing item list documented here. By following the viewer on the hardware management console is
procedures in the symbolic FRUs listed here you will 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:
v SIIOADP
If the serviceable event view only indicated a frame or
v OPT_CLN
enclosure see the locations section for the frame or
enclosure type. The location of the HSL I/O Bridge will
A6006908 be given in the locations tables.
Explanation: High Speed Link (HSL) or PCI bridge NOTE: A fiber optic cleaning kit may be required for
card slot I/O bridge failure. optical HSL connections.
Response: LIC data in the I/O bus VPD could not be Failing Item:
accessed. The I/O Bus identified in the SRC may not v SIIOADP
have become operational.
v OPT_CLN
If there is a B6xx 6906 reference code, close this
problem in the serviceable event view you are working
A600690A
with and work the 6906 error.
Explanation: Associated adapter not found in this
partition.
the Service Action Log (SAL), or serviceable event view
you are working with, can be different from the failing Failing Item:
item list documented here. That is due to the v LICIP16
If the Service Action Log or serviceable event view on A6006910
the hardware management console or service processor
is available then use the failing item list presented there Explanation: I/O processor failure.
for servicing this reference code.
Response: An I/O processor timed out, returned bad
If a serviceable event view is not available then use the status, or is not following the system bus protocol.
failing item list documented here. By following the
Failing Item:
procedures in the symbolic FRUs listed here you will
isolate to the correct FRU list based on system model v LICIP07
and features installed. v FI00310
NOTE: A fiber optic cleaning kit may be required for v FI00318
optical HSL connections. v FI00065
v FI00130

A6006938 • A6006963
v AJDG301 item list documented here. That is due to the

A6006938 If the Service Action Log or a serviceable event viewer
on the hardware management console is available for
Explanation: Not valid system configuration detected.
this problem then use the failing item list presented
Response: This system model does not allow a there for servicing this reference code.
configuration of more than three (non-OptiConnect)
I/O Processors.
Power down the system and remove the extra procedures in the symbolic FRUs listed here you will
(non-OptiConnect) I/O Processor(s) so that there are isolate to the correct FRU list based on system model
three or less. Restart the system. and features installed.
Failing Item:
A6006944 v SLOTERR
Explanation: Missing or failed I/O processor cards. v MASBUS
Response: A system bus appears to be empty. If the
bus is not empty, two I/O processors in consecutive A6006962
slots may be missing or broken. If there are broken I/O
Explanation: Multi-adapter Bridge or PCI Bridge card
processors, then another more serious SRC has
slot error, do not use card slot.
occurred. Otherwise find the bus number for this
failure from the Product activity log and use the system Response: Power control failure, do not use slot.
configuration list to verify the configuration of the I/O
If there is a Linux partition in the system, any IOPs
processors on that bus.
plugged into slots owned by a Linux partition will not
Failing Item: power on. This error will be logged. Correct the
v FI00317 situation by removing the IOP cards.
v FI00316 The card location is not available for use. The Failing
v AJDG301 Item with the card slot error is in the Failing Item list
for this reference code.
A6006960 See SLOTERR symbolic FRU for the list of messages

and a further description of the problem detected by
Explanation: Multi-adapter Bridge or PCI Bridge card Licensed Internal Code.
slot error, do not use card slot.
Response: Slot unavailable due to 64 bit card in the Service Action Log (SAL), or serviceable event view
adjacent slot. you are working with, can be different from the failing
One of the messages documented with the symbolic item list documented here. That is due to the
FRU will describe the problem. See SLOTERR symbolic differences in system models and features installed.
FRU for a list of messages and corrective actions. If the Service Action Log, or serviceable event view on
Failing Item: the hardware management console is available then use
the failing item list presented there for servicing this
v SLOTERR reference code.
A6006961 failing item list documented here. By following the
Explanation: Multi-adapter Bridge or PCI Bridge card procedures in the symbolic FRUs listed here you will
slot error, do not use card slot. isolate to the correct FRU list based on system model
Response: LED control failure, do not use slot.
Failing Item:
The card location is not available for use. The Failing
v SLOTERR
Item with the card slot error is in the Failing Item list
for this reference code. v MASBUS
See SLOTERR symbolic FRU for the list of messages

and a further description of the problem detected by A6006963
Licensed Internal Code. Explanation: Multi-adapter Bridge or PCI Bridge card
For this reference code the failing item list presented in slot error, do not use card slot.
the Service Action Log (SAL), or serviceable event view Response: Power control failure, do not use slot.
you are working with, can be different from the failing

A6006964 • A6006967
The card location is not available for use. The Failing See MABRCFG symbolic FRU for the list of messages, a
Item with the card slot error is in the Failing Item list further description of the problem detected by Licensed
for this reference code. Internal Code and the corrective action.
See SLOTERR symbolic FRU for the list of messages Failing Item:
and a further description of the problem detected by v MABRCFG
For this reference code the failing item list presented in A6006965
viewer you are working with, can be different from the Explanation: Multi-adapter Bridge or PCI Bridge
failing item list documented here. That is due to the configuration change or error.
differences in system models and features installed. Response: Card type not supported in this slot.
If the Service Action Log or serviceable event viewer on An I/O processor or I/O adapter card type is installed
the hardware management console is available then use in the location indicated in word 7 of the SRC. The
the failing item list presented there for servicing this card type is not supported in that slot under the
reference code. Multi-adapter Bridge or PCI Bridge. The card is
If serviceable event view is not available then use the unavailable.
failing item list documented here. By following the See MABRCFG symbolic FRU for the list of messages, a
procedures in the symbolic FRUs listed here you will further description of the problem detected by Licensed
isolate to the correct FRU list based on system model Internal Code and the corrective action.
Failing Item:
Failing Item:
v MABRCFG
v SLOTERR
v MASBUS
A6006966
A6006964 Explanation: Multi-adapter Bridge or PCI Bridge

configuration change or error.
Explanation: Multi-adapter Bridge or PCI Bridge
configuration change or error. Response: I/O processor removed from Multi-adapter
Bridge or PCI Bridge card slot.
Response: One of several errors or configuration
problems has occurred under a Multi-adapter Bridge or On the previous IPL an I/O processor was in the card
PCI Bridge. If you are using the Service Action Log location specified in word 7 of the SRC. The I/O
(SAL), or the serviceable event viewer on the hardware processor was not detected on this IPL.
management console or the service processor, then the See MABRCFG symbolic FRU for the list of messages, a
correct FRU, description and card position(s) will be further description of the problem detected by Licensed
listed. Use the FRUs and descriptions in the serviceable Internal Code and the corrective action.
event view you are working with to determine the
v MABRCFG
If you do not have access to the Service Action Log, or
serviceable event view on the hardware management
console or service processor, then word 4 of the SRC A6006967
has more information. Examine the last 4 digits in word
4 to determine the problem by comparing them to the
list below and using the FRU(s) listed here.
1. xxxx2022 - IOP found in slots owned by a Linux Response: I/O adapter unavailable due to moved I/O
partition. The Multi-adapter Bridge or PCI Bridge processor card.
and PCI Bridge set that it controls are assigned to a The I/O adapter specified in word 7 of the SRC is not
Linux partition. The IOP found in the SLOT available. On the previous IPL there was an I/O
indicated by the DSA in word 7 will not be processor card the adapter was assigned to. The I/O
configured. processor was not detected on this IPL.
2. xxxx2014 - I/O adapters were found under the
Multi-adapter Bridge or PCI Bridge but there is no See MABRCFG symbolic FRU for the list of messages, a
IOP to support them. The adapters cannot be used. further description of the problem detected by Licensed
Internal Code and the corrective action.
3. xxxx2015 - An card type was found that cannot be
supported in the card position where it is located. Failing Item:
v MABRCFG

A6006968 • A6006970
-- Vary off the I/O Adapter. Using Hardware Service

A6006968
manager in SST/DST, locate the I/O Adapter resource.
Explanation: Multi-adapter Bridge or PCI Bridge Using concurrent maintenance on the associated
configuration change or error. packaging resource, remove the I/O Adapter and
install it in a location that does not have I/O Processors
Response: IOA removed from Multi-adapter Bridge or
on the same Multi-adapter bridge domain.
PCI Bridge slot.
OR:
On the previous IPL an I/O adapter was in the card
slot specified in word 7 of the SRC. That I/O adapter -- Vary off the I/O Adapter. Use the concurrent
was not detected on this IPL. maintenance option in Hardware Service Manager in
SST/DST to power off all I/O Processors located on the
See MABRCFG symbolic FRU for the list of messages, a
same Multi-adapter Bridge or PCI Bridge domain as
further description of the problem detected by Licensed
the I/O Adapter. Use concurrent maintenance to power
Internal Code and the corrective action.
off and power on the I/O Adapter. Then use
Failing Item: concurrent maintenance to power on the I/O
v MABRCFG Processors located on the same Multi-adapter Bridge or
PCI Bridge domain as the I/O Adapter.
A6006969
A6006970
configuration change or error. Explanation: High Speed Link (HSL) or PCI bridge
card slot resource failure.
Response: I/O adapter replaced by I/O processor
card. Response: A system PCI bus failure was detected.
Word 7 of the SRC contains the bus number.
On the previous IPL there was an I/O adapter in the
location specified in word 7 of the SRC. This IPL LIC This failure can occur when a tower in an HSL loop is
detected that the IOA was replaced by an IOP in that powered off using concurrent maintenance. If this is the
location. case, close this problem.
See MABRCFG symbolic FRU for the list of messages, a This error is most likely in the hardware that makes up
further description of the problem detected by Licensed the PCI bus, the PCI bus side of the HSL I/O bridge or
Internal Code and the corrective action. the Multi-adapter Bridge or PCI Bridge. In some cases
it may be caused by a failing IOP in the Multi-adapter
Failing Item: Bridge or PCI Bridge domain. When an IOP is causing
v MABRCFG the problem, the failing IOP cannot be identified.
NOTE: This SRC can occur for the PCI bus resource on
A600696A a PCI bus in an I/O expansion unit when the unit is
powered off for a concurrent maintenance action.
Explanation: Card slot test failed.
If the Service Action Log, or serviceable event view on
Failing Item: the hardware management console or service processor,
v LICIP14 is available then use the failing item list presented there
v FI00131 for servicing this reference code.
v BACKPLN If a serviceable event view is not available then use the
failing item list documented here.
A600696B NOTE: A fiber optic cleaning kit may be required for
optical HSL connections.
Explanation: Card slot could not be validated.
Failing Item:
Response: This can be caused by "PCI error injection
policy" being set to "YES" and an I/O Processor being v SI_PHB
installed on the same Multi-adapter Bridge or PCI v PRI_PCI
Bridge domain as the I/O Adapter. Do one of the v MA_BRDG
following. Either:
v MABIP03
-- Using the hardware management console or a v BRDGSET
customer PC with a Web browser access the Advanced
v OPT_CLN
System Management Interface (ASMI) and disable PCI
error injection policy.
OR:

A6006971 • A6006980
v BRDGSET
A6006971
v SIIOADP
v MA_BRDG
Response: A failure occurred in a Multi-adapter
A6006974
Bridge or PCI Bridge or on the bus to the card location
it controls. Explanation: Multi-adapter Bridge or PCI Bridge
If a serviceable event view is available, use the failing
item list presented there for servicing this reference Response: PCI I/O processor rejected the assignment
code. of or the removal of an I/O adapter.
If a serviceable event view is not available, use the Failing Item:
failing item list documented here. v MABRCFG
Failing Item:
v MABIP02 A6006975
v MA_BRDG Explanation: The system issued a reset/reload to the
v MASBUS service processor.
v PIOCARD Response: Service processor error.
Failing Item:
A6006972
v AJDGP01
A6006976
Response: Multi-adapter Bridge (MaB) or PCI Bridge
failure detected. Explanation: Service processor failure.
For this reference code the failing item list presented in Response: For this reference code the failing item list
the Service Action Log (SAL), or serviceable event presented in the Service Action Log (SAL), or
viewer you are working with, can be different from the serviceable event view you are working with, can be
failing item list documented here. That is due to the different from the failing item list documented here.
differences in system models and features installed. That is due to the differences in system models and
features installed.
viewer on the hardware management console is If the Service Action Log (SAL) or a serviceable event
available then use the failing item list presented there viewer on the hardware management console is
for servicing this reference code. available then use the failing item list presented there
failing item list documented here. By following the If a serviceable event viewer is not available then use
procedures in the symbolic FRUs listed here you will the failing item list documented here. By following the
isolate to the correct FRU list based on system model procedures in the symbolic FRUs listed here you will
and features installed. isolate to the correct FRU list based on system model
Failing Item:
Failing Item:
v MA_BRDG
v SVCPROC
A6006973
A6006980
card slot resource failure. Explanation: Network Interface Controller / IO Hub
failure.
Response: Multi-adapter Bridge or PCI Bridge has
detected a problem in the card installed in the location Response: For Power5 and newer servers, service this
specified in word 7 of the SRC. Use the FRU list in the error using the B7006980 service information.
Service Action Log (SAL), or serviceable event view Otherwise, continue with this information.
you are working with. If you are working from this The FRU list displayed in the Service Action Log (SAL)
document's FRU list use the Symbolic FRU BRDGSET or serviceable event view you are working with, may
to determine the failing items. vary from the failing item list given in this document.
Failing Item: Use the FRU list in the serviceable event view if it is
available to you.

A6006981 • A6006984
NOTE: A fiber optic cleaning kit may be required for v HSL_LNK

optical HSL connections. v SIIOADP
Failing Item: v SICNTRL
v SICNTRL v REM_NIC
v OPT_CLN v OPT_CLN
A6006981 A6006983
Explanation: High Speed Link (HSL) or PCI bridge Explanation: A High Speed Link (HSL) / RIO / 12X
card slot I/O bridge failure. loop configuration event was detected. The loop may
have an unsupported configuration or a configuration
Response: For Power5 and newer servers, service this
that is not valid or the loop is in a state that LIC is
error using the B7006981 service information.
logging for potential future reference.
Otherwise, continue with this information.
Problem determination: LIC is reporting an event
Cycle power on the frame identified as the frame with
about the state of a RIO / HSL / 12X loop. Word 4 of
failed HSL I/O Bridge prior to replacing FRUs.
the SRC contains the program return code (PRC)
The FRU list displayed in the Service Action Log (SAL), which. identifies the state or problem with the loop.
or serviceable event view you are using, may vary from
For Power5 and newer servers, if this event appears in
the failing item list given in this document. Use the
a serviceable event view then a service action is
FRU list in the serviceable event view if it is available
required. This SRC may also be logged as informational
to you.
when it is recording information about the loop that is
If you find either a B6xx 6982 or B6xx 6984 SRC logged not a problem for the LPAR.
at approximately the same time as this SRC then they
were caused by the same failure. If you find a 6982
view then no service is required. To determine what the
SRC logged at approximately the same time then close
event meaning is record the PRC in word 4 of the SRC
this problem and service the 6982 SRC. The failing item
then use symbolic FRU SIRGCFG. This completes the
listed for this SRC is one of the failing items listed for
procedure.
B6xx 6982. If the serviceable event view's entry for this
SRC has a location listed then record the location for If this event appears in a serviceable event view then
use in servicing the 6982 SRC. search for a B7006983 serviceable event logged at about
the same time.
NOTE: This SRC can occur for the HSL I/O Bridge
resource in an I/O expansion unit when the unit is Did you find a B7006983 serviceable event logged at
powered off for a concurrent maintenance action. about the same time in the LPAR?
NOTE: A fiber optic cleaning kit may be required for v YES - Service this error by working the B7006983
optical HSL connections. error.
v NO - Continue working this SRC. If you are using
Failing Item:
the Service Action Log (SAL) the FRU description
v SIIOADP may already indicate the configuration problem.
v OPT_CLN Otherwise record the PRC in word 4 of the SRC. Use
symbolic FRU SIRGCFG to determine the problem.
Explanation: High Speed Link (HSL) connection v SIRGCFG
failure.
Response: For Power5 and newer servers, service this A6006984
error using the B7006982 service information. Explanation: High Speed Link (HSL) loop status
Otherwise, continue with this information. message.
If this SRC is not in the Service Action Log (SAL) or Response: For Power5 and newer servers, service this
serviceable event view you are using, then it is error using the B7006984 service information.
informational or statistical only. It does not require a Otherwise, continue with this information.
service action.
An HSL loop has switched to its alternate path. This is
Otherwise, this is a connection failure on an HSL link. an informational SRC only.
Word 7 of the SRC contains the loop number in the
Failing Item: leftmost 4 digits. The loop number is in hexadecimal
v RIOIP09 format. You must convert the hexadecimal loop number

A6006985 • A6006986
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
A6006985 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. If this SRC appears in the Service Action
Otherwise, continue with this information. Log (SAL), or the serviceable event view you are
using, with the Symbolic FRU HSL_LNK or
If this SRC is not in the Service Action Log (SAL), or
HSLxxxx listed as a FRU, then perform problem
serviceable event view you are using, then it is
isolation procedure RIOIP01. Otherwise exchange
informational. Use FRU SIRSTAT to determine what
the FRUs listed in the serviceable event view.
this SRC means. Otherwise, continue with the
following steps:
This error can appear as a serviceable event when a optical HSL connections.
tower, or I/O unit or another system in the loop did
not complete powering on before LIC on this system Failing Item:
checked this loop for errors. Search the Product v SIRSTAT
Activity Log (PAL) for the last B6xx 6985 SRC logged v HSL_LNK
for this loop and use FRU SIRSTAT to determine if this
v SIIOADP
error requires service. If the last entry indicates the
loop is functioning (determined by FRU SIRSTAT) then v SICNTRL
no service action is required, close this problem v OPT_CLN
There may be multiple B6xx 6985 logs with xxxx 3205
in word 4 errors for the same loop resource in the A6006986
serviceable event view. This is caused by retry and
recovery attempts. If there is a B6xx 6985 with xxxx
3206 or xxxx 3208 in word 4 after the above B6xx 6985 Response: For Power5 and newer servers, service this
entries in the PAL, then the recovery efforts were error using the B7006986 service information.
successful. If this is the case, close all the B6xx 6985 Otherwise, continue with this information.
entries for that loop resource in the serviceable event
view. During IPL, system LIC detected an HSL I/O bridge
that was already initialized. The bridge should have
1. If you find a B6xx 6981 in the serviceable event been in a flushed and uninitialized state after powering
view then close that problem and go to step 2. on. There is a problem with SPCN components that
Otherwise perform the following: prevented the tower from powering off after a previous
v Perform RIOIP06 to determine if any other power off was issued. The tower will not be configured
systems are connected to this loop and return for this IPL.
here. (HSL_LNK or HSLxxxx FRU in the Service
Action Log (SAL) entry, or serviceable event view This reference code is equivalent to 1xxx 90F0. When
you are working with, indicates the loop referring to the "CBLALL" symbolic FRU in the Failing
number.) If there are other system(s) then Item list, perform the "CBLALL" procedure using
continue with the steps that follow, otherwise go reference code "90F0".
to step 2. Word 5 of the SRC identifies the frame. Determine the
v Check for HSL failures on the other system(s) frame by breaking down word 5:
before replacing parts. HSL failures are
Word 5 -> xxxx xxNN where: NN is the frame number
serviceable event entries with HSL I/O Bridge
in hexadecimal format.
and Network Interface Controller (NIC)

A6006987 • A600699C
Failing Item:
A6006990
v TWRCARD
Explanation: Service processor failure.
v CBLALL
Response: The FRU list displayed in the Service
Action Log (SAL), or serviceable event view you are
A6006987
working with, may vary from the failing item list given
Explanation: High Speed Link (HSL) connection in this document. Use the FRU list in the serviceable
failure. event view if it is available to you.
Response: For Power5 and newer servers, service this Failing Item:
error using the B7006987 service information. v SVCPROC
Failures are occurring on the HSL link. A6006991
There may be B6xx 6982 errors logged on the same Explanation: Service processor failure.
loop and about the same time as this error. Close those
errors and continue to correct the problem by working Failing Item:
this error. v AJDGP01
v If there is a cable FRU in the serviceable event entry:
1. If the connection is copper and either end has a A6006992
loose connection, re-seat the cable. To do this,
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 AJDGP01
seconds. Repeat the process at the other end of
the cable. If the error persists, replace the FRUs in
the Service Action Log (SAL), or serviceable event A6006993
view you are using.
2. If the connection is optical, clean the connections
at both ends of the cable. If the error persists, Response: A failure occurred with the service
replace the FRUs in the Service Action Log (SAL), processor hardware or the service processor LIC.
serviceable event view you are using. The FRU list displayed in the Service Action Log (SAL),
3. If the error persists, replace the FRUs at each end or serviceable event view you are working with, may
of the cable starting with the FROM FRU listed in vary from the failing item list given in this document.
the serviceable event view you are using. Use the FRU list in the serviceable event view if it is
v If there was no cable in the Service Action Log available to you.
(SAL), or serviceable event view you are using, then Failing Item:
replace the FRUs listed in the serviceable event view.
v SVCPROC
v HSL_LNK
v OPT_CLN A6006994
A6006988
Response: The FRU list displayed in the Service
Explanation: A High Speed Link (HSL / HSL2) or Action Log (SAL) or serviceable event view you are
RIO / RIO-G loop was detected on the system this working with, may vary from the failing item list given
LPAR is running on. This version of the operating in this document. Use the FRU list in the serviceable
system does not support resources on an HSL / HSL2 event view if it is available to you.
/ RIO / RIO-G loop. If resources on the loop are
assigned to this LPAR, for example in the partition Failing Item:
profile, the resources will not show up in this IBM i v SVCPROC
LPAR.
A600699C
Explanation: Wrap plug is installed on Bus Expansion
Adapter card.

A60069A8 • A60069C6
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:
A60069A8 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 A60069C5
and might include the following:
v Optical speed encode.
v Broken optical links now operational. Response: Contact your next level of support.
v Other information. Failing Item:
v NEXTLVL
A60069B8
Explanation: Bus hardware configuration problem. A60069C6
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
A60069C1 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
suspect an Opti-connect problem. Otherwise this is a I/O bridge or a power problem in an expansion I/O
tracking event. tower or unit on this loop.
Failing Item: Examine the Service Action Log (SAL), or serviceable
v NEXTLVL event view you are using on the local system or
partition for HSL failures on the same HSL loop at
approximately the same time this error occurred.
A60069C2
Examine the remote system or partition for problems. If
Explanation: HSL Opticonnect normal connect to the remote system or partition is powered on and IPL'd
another sys. or partition. then examine the Service Action Log (SAL), or
serviceable event view you are using, on the remote
Response: This reference code is informational only.
system or partition for problems on the same HSL loop
HSL OptiConnect has established connection normally. at approximately the same time this error occurred.
The local system or partition is participating in HSL
Correct any problems you find with the remote and
Opticonnect with other systems or partitions on the
local systems or partitions that happened at
same HSL loop.
approximately the same time and involve HSL
Opticonnect or HSL loop components or Network
A60069C3 Interface Controllers. When the remote system is IPL'd
it will automatically reconnect with this system or
Explanation: HSL Opticonnect normal disconnect from
partition.
other sys. or partition.
If there are no problems with the remote system or
Response: This reference code is informational only.
partition and there are no problems with the local
HSL Opticonnect disconnected normally from a remote system or partition then collect all the Product Activity
node. The local system or partition has stopped Log information for this failure on both systems. Be

A60069C7 • A60069C9
sure to record all words in the SRC. Contact your next v Network deadlock detected
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
A60069C7 Examine the Service Action Log (SAL), or serviceable

Explanation: HSL Opticonnect abnormal disconnect event view you are using, on the local system or
from other sys. or partition. partition for HSL failures on the same HSL loop, or
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
Possible causes are: time out, hang or hardware failure. partition for problems on the same HSL loop or with
The problem may be with: the local system or partition the Network Interface Controller at approximately the
or the remote system or partition. same time this error occurred.
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
Examine the SAL or serviceable event view you are partition and there are no problems with the local
working with on the local system or partition for system or partition then collect all the Product Activity
failures on the same loop, or with the Network Log information for this failure on all systems or
Interface Controller at approximately the same time. partitions. Be sure to record all words in the SRCs.
Examine the remote system or partition for problems.
Correct any HSL or NIC problems you find with the Failing Item:
remote and local systems or partitions. v REM_SYS
If there are no problems with the remote system or v LOC_SYS
partition and there are no problems with the local v AJDG301
system or partition then collect all the Product Activity
Log (PAL) information for this failure on both systems.
Be sure to record all words in the SRC. Contact your A60069C9
next level of support. Explanation: HSL Opticonnect abnormal disconnect
Failing Item: from other sys. or partition.
v REM_SYS Response: The local system or partition disconnected
v LOC_SYS from a remote system or partition due to an failure in a
LIC virtualized bus unit. LIC will attempt to recover
from the error. Possible causes are:
A60069C8
v LIC problem where the local bus unit is off line.
Explanation: HSL Opticonnect abnormal disconnect v LIC problem where the remote bus unit is off line.
Response: The local system or partition disconnected Examine the Service Action Log (SAL), or serviceable
from a remote system or partition due to an event view you are using, on the local system or
unexpected event or failure. All of the HSL partition for HSL Opticonnect failures that occurred at
OptiConnect connections on this loop will be in a failed approximately the same time this error occurred.
state. LIC will attempt to recover from the error.
Intervention at the local or remote system or partition Examine the remote system or partition for problems.
may be required. Possible causes are: Examine the Service Action Log (SAL), or the
v time out of a critical message
v LIC code / table problem

A60069CF • A60069DE
system or partition for HSL Opticonnect problems that

A60069D9
occurred at approximately the same time this error
occurred. Explanation: Host Ethernet Adapter (HEA) failure.
Response: Firmware detected a hardware failure in
Collect all the Product Activity Log information for this
the Host Ethernet Adapter (HEA).
failure on all systems and partitions on this HSL loop.
Be sure to record all words in the SRCs. Contact your Failing Item:
next level of support with the information you have v HEA
collected.
Failing Item: A60069DA
v AJDG301
v REM_SYS required.
v LOC_SYS
A60069DB
A60069CF
Explanation: LIC failure.
Explanation: HSL Opticonnect abnormal disconnect
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 v SVCDOCS
Log (SAL), or serviceable event view you are using, on
the local system or partition for HSL Opticonnect
failures that occurred at approximately the same time A60069DC
this error occurred. Explanation: The Host Ethernet Adapter (HEA) is not
Examine the remote systems or partitions for problems. connected to the Ethernet switch.
Examine the Service Action Log (SAL), or serviceable Response: The Host Ethernet Adapter (HEA) is not
event view you are using, on the remote systems or connected to the Ethernet switch. If the HEA
partitions for HSL Opticonnect problems that occurred connection is not needed, no service action is required.
at approximately the same time this error occurred.
If the HEA connection is needed, verify that the cable is
Collect all the Product Activity Log information for this connected and the switch is powered on. After
failure on all systems and partitions on this HSL loop. repairing the problem, verify that the connection has
Be sure to record all words in the SRCs. Contact your been restored.
next level of support with the information you have
collected.
A60069DD
Failing Item:
v AJDG301 Explanation: The Host Ethernet Adapter (HEA)
connection to the Ethernet switch has been restored.
A60069D0 Response: System log entry only, no service action

required.
Response: Contact your next level of support. A60069DE
Failing Item: Explanation: Host Ethernet Adapter (HEA) Media
v NEXTLVL Interface Adapter Failure.
Response: Firmware detected a failure in the HEA
A60069D8 Media Interface Adapter.
Explanation: Bus Expansion Adapter failed. Failing Item:

v HEA
v AJDG301
Failing Item:
v NEXTLVL

A60069E0 • A6007101
datagram. Silently discard is defined to mean discard

A60069E0
the received datagram without reporting an error to the
Explanation: Bus Expansion Adapter card failed. originating host device. Examples of such datagrams
are those with checksums or destination addresses
which are not valid.
Failing Item:
This reference code is for information only. Normally
v NEXTLVL no action should be taken as a result of this reference
code. It is generated in order to assist with remote
A60069E8 device or TCP/IP network problem determination.
Explanation: Bus Expansion Adapter failed.

A6007055
Explanation: Statistics were logged, no service action
v NEXTLVL Response: This reference code is logged for
information only.
A60069F0
Explanation: Bus Expansion Adapter failed. A6007100
Response: Contact your next level of support. Explanation: APPN session initiation attempt has
timed out.
Failing Item:
Response: This reference code is used to indicate that
v NEXTLVL
LIC timed out on a request to initiate a session.
The user must run problem analysis for this reference
A60069F8
code. If this indicates a software problem, the user
Explanation: Bus Expansion Adapter failed. should dial IBM Software Support for assistance.
Response: Contact your next level of support. The Problem Determination Procedure (PDP) will
indicate whether the original timeout condition still
Failing Item:
exists and what the corrective actions should be.
v NEXTLVL
Failing Item:
v AJDG301
A6007001
v UPLF3
Explanation: ISDN call in rejected.
v UPLF1
Failing Item: v UPLF2
v UG3LB
A6007101
A6007002
Explanation: APPN session initiation attempt has
Explanation: Lines not selected. failed.
Failing Item: Response: This reference code is used to indicate that
v UG3LB LIC attempted to satisfy a session initiation request, but
some failure condition was detected by LIC. The failure
condition could be a configuration or operational
A6007003 problem in the network.
Explanation: Network interfaces not selected. The user must run problem analysis for this reference
Failing Item:
should dial IBM Software Support for assistance.
v UG3LB
The Problem Determination Procedure (PDP) will
A6007004 exists and what the corrective actions should be.
Explanation: TCP/IP informational error. Failing Item:
Response: This reference code is logged when the v UPLF4
TCP/IP Attribute Log Protocol Errors is set, and the v UPLF5
TCP/IP System LIC silently discards an in bound

A6007102 • A6008001
v UPLF6 Hardware Configuration" and verify that the dates

v AJDG301 match the labels on the batteries.
A6007102 A6007703
Explanation: APPN CP-CP session ended. Explanation: System LIC detected a program
exception.
A6007201 Response: Storage Management detected a DASD

datacheck condition and the defective sector was
Explanation: A utility failure occurred. reallocated.
Response: This reference code is for information only. Perform a system IPL to restart the system.
The Uninterruptible Power System (UPS) is reporting a
utility failure.
A6007704
A6007202 Explanation: General failure detected by HRI

component.
Explanation: Utility power restored.
Failing Item:
v AJDG301
The Uninterruptible Power System (UPS) is reporting
that utility power has been restored.
A6007777
A6007203 Explanation: Hardware configuration change detected.
Explanation: A battery low condition was detected. Response: A hardware resource is missing. The
resource reported in to the system on a previous IPL,
but has not reported in on the current IPL. This could
occur for several different reasons.
battery low condition.
1. It could be a normal situation where the resource is
currently powered off. In this case, when the
A6007204 resource is powered back on, it will no longer be
Explanation: Uninterruptible Power System reported a missing.
bypass active. 2. The hardware resource could also be missing if it
has been removed from the system, for example, a
Response: This reference code is for information only. tape drive that was replaced with a different tape
The Uninterruptible Power System (UPS) is reporting a drive. The service representative should use the
bypass is active. Hardware service manager to remove the entry for
this resource.
A6007205 3. The resource may not have reported in on this IPL
because it is failing. Perform problem analysis to
Explanation: Battery low condition was reset.
determine why the resource is failing.
The Uninterruptible Power System (UPS) is no longer
A6008000
reporting a battery low condition.
Explanation: A storage subsystem disk unit
connection failed.
A6007206
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
Response: This reference code is for information only. with, and fix them.
reporting a bypass active condition.
A6008001
A600720A
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,
Response: The replacement dates for one of the and fix them.
Battery Power Units do not match. Run "Display

A6008002 • A600CFFC
No action required.
A6008002
Explanation: Maximum number of redundant
A600B700
connections exceeded.
Explanation: A platform firmware error log was
Response: An attempt to activate a connection from
signalled to LIC but could not be retrieved from
another I/O adapter to a storage subsystem disk unit
platform firmware. LIC created this event in the PAL
failed because the maximum number of connections are
with SRC B600B700 to log the problem.
already active for this disk unit. No action required.
Problem determination: Contact your hardware
service provider. This is a platform firmware problem.
A6008003
Failing Item:
connection was restored. v NEXTLVL

A600CF00
A6008004 Explanation: Permanent error on removable media

device.
connection failed. Response: A type D IPL terminated because of a
removable media Load Source device failure. If the
Response: Could not read configuration information removable media Load Source is an external device,
from the disk unit. Look for other errors in the Service check the cables. If that does not correct the problem,
Action Log, or serviceable event view you are working replace the device. If the removable media Load Source
with, and fix them. is an internal device, replace the device. If the
removable media Load Source is a virtual device,
A6008005 ensure it is set up correctly.
Explanation: High performance connection failed. Failing Item:

v SVCDOCS
Response: A high performance connection to an
external storage subsystem disk unit failed.
A600CF01
There are still two or more external storage subsystem
disk unit connections, but performance might be Explanation: Unsupported removable media device
degraded. configuration.
Look for other errors in the Service Action Log, or Problem determination: A type D IPL terminated
serviceable event view you are working with, and fix because of an unsupported removable media device
them. configuration. Retry the D-IPL with a different
removable media device.
Explanation: High performance connection failed. v SVCDOCS

external storage subsystem disk unit failed. A600CFFC
There is still one more external storage subsystem disk Explanation: Optical library device condition not
unit connection, but performance might be degraded. expected.
Look for other errors in the Service Action Log, or Response: The optical disk drive addressing within
serviceable event view you are working with, and fix the optical library is incorrect. This error is likely to be
them. the result of faulty cabling or switch setting following
service to an optical library.
A6008007 Contact your hardware service provider.
Explanation: High performance connection was Failing Item:

restored. v OPTLCBL
Response: A high performance connection to an v DRVSWCH
external storage subsystem disk unit was restored.
Performance is no longer degraded.

A600CFFD • A6xx0105
A600CFFD A6D1BD62
Explanation: Optical drive failure. Explanation: Platform firmware event with a non IBM
i LPAR.
Failing Item:
v OPTLDRV Problem determination: Report this problem to your
next level of support.
A600CFFF Failing Item:

v SVCDOCS
Explanation: Media determined to be bad in Optical
library.
A6xx0000
A600F103 Explanation: Operating system status code.
Explanation: Main storage dump must be copied for Response: This reference code is for information only.
service. It is shown in the Product activity log as a side effect of
a condition that was detected by LIC.
Failing Item:
v LICIP01 Normally, no action should be taken as a result of
information reference codes. However, to isolate the
root cause, use these suggestions:
A600F104
1. Examine the date and time of the informational
Explanation: LPAR service function directed a Main reference code.
Storage Dump. 2. Determine if any other reference codes have been
Response: The Hypervisor terminated a partition with logged at or before the same date and time.
an unresponsive Operating System. A Main Store 3. Begin the service approach based on these other
Dump must be done for service. Call your next level of logged errors.
support when the dump is complete.
Failing Item: A6xx0102
v LICIP01 Explanation: A machine check occurred during IPL.
Response: Words 2 to 9 of this SRC contain additional
A600F105 diagnostic information. Record SRC words 1 through 9
Explanation: Licensed Internal Code detected error. before attempting to IPL again and report the problem
to your Software Service Provider.
Failing Item:
v NEXTLVL A6xx0103
Explanation: Main storage dump must be copied for
A600FDC0 service.
Explanation: LIC program reported informational Failing Item:
error.
v LICIP01
Response: This reference code is logged for
information only. No action required.
A6xx0104
A600FDC5 Explanation: Terminate Immediate reference code is

bad.
Explanation: LIC program failed and data was
captured. Failing Item:
v LICIP08
Response: This reference code indicates first failure
data capture (FFDC) data was collected for a problem v AJDG301
reported by licensed internal code.
The user should dial IBM Software Support for A6xx0105
assistance. Explanation: More than one request to terminate the
Failing Item: system was issued.
v UG3AS Failing Item:
v LICIP08

A6xx0106 • A6xx0266
v AJDG301
A6xx0231
Explanation: Disk sanitize action completed
A6xx0106
successfully.
Explanation: Terminate Immediate data is not valid.
Response: No service action required. This entry is
v LICIP08
v AJDG301 A6xx0232
Explanation: Disk sanitize action did not complete
A6xx0107 successfully.
Explanation: Main storage dump must be copied for Response: Provide the Product Activity Log entry to
service. your next level of support for analysis.
Response: The server detected an unrecoverable
machine check condition. A6xx0244
Collect all the words of the SRC and the main store Explanation: Contact was lost with the device
dump and send to your system manufacturer for indicated.
analysis.
A6xx0109
Failing Item:
Explanation: An unrecoverable memory error
occurred. v LICIP13
v FI00580
Response: Re-IPL the partition that terminated. Then,
look for and correct errors with SRCs of the form v FI00500
B1xxxxxx in the Serviceable Event View that indicate v FI00302
the replacement of memory in the failing item list. If v FI00301
there are no B1xxxxxx SRCs in the Serviceable Event
v AJDG301
View that indicate a memory problem, perform a slow
boot by using Performing a slow boot in order to run
diagnostics on the memory. Then, look for and correct A6xx0255
errors with SRCs of the form B1xxxxxx in the
Serviceable Event View. Explanation: Contact was lost with the device
indicated.
Failing Item:
v SVCDOCS
A6xx0202 Failing Item:
Explanation: Unrecoverable read error. v LICIP13
v FI00580
Response: Restore the Licensed Internal Code using
Utilities to install and restore IBM i Licensed Internal v FI00500
Code. v FI00302
v FI00301
A6xx0210 v AJDG301
Explanation: The system ASP has run out of disk
storage. A6xx0266
Response: The out of storage condition in the system Explanation: Contact was lost with the device
ASP can be caused by an allocation failure in some indicated.
other system software. This could be a looping
condition that continues to allocate storage. Contact
your service representative for assistance with the Main Perform the procedure indicated in the failing item list.
Storage Dump.
Failing Item:
v LICIP13
v FI00580

A6xx0299 • A6xx0328
v FI00500 v LICIP08
v FI00302 v AJDG301
v FI00301
v AJDG301 A6xx0317
Explanation: Traceback for code not found.
A6xx0299
Failing Item:
Explanation: Informational LIC state SRC. v LICIP08
v AJDG301
A6xx0302
Explanation: Recursion in exception handler. A6xx0323
This SRC is an IBM i software event. If this SRC was Explanation: LIC exception code detected a problem.
reported as a serviceable event or if this SRC appears
Failing Item:
on the IBM i LPAR's panel then report the SRC as an
IBM i software problem. v LICIP08
v AJDG301
Failing Item:
v LICIP08
A6xx0324
v AJDG301
A6xx0304 Failing Item:
Explanation: Component specific exception handler v LICIP08
return code not valid. v AJDG301
Failing Item:
v LICIP08 A6xx0325
v AJDG301 Explanation: LIC exception code detected a problem.
Failing Item:
A6xx0305 v LICIP08
Explanation: Exception while storage management v AJDG301
lock is held.
v LICIP08 Explanation: LIC exception code detected a problem.
v AJDG301
Failing Item:
v LICIP08
A6xx0307
v AJDG301
Response: Component Specific Exception Handler A6xx0327
recursion is detected in an IBM i Operating System
process. Explanation: LIC exception code detected a problem.

v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6xx0308 A6xx0328
Explanation: LIC exception code detected a problem. Explanation: LIC exception code detected a problem.
Response: Component Specific Exception Handler Failing Item:

recursion is detected in an IBM i Operating System v LICIP08
process. v AJDG301
Failing Item:

A6xx0329 • A6xx0410
A6xx0329 A6xx0403
Explanation: LIC exception code detected a problem. Explanation: Unhandled exception during IPL or
install.
Failing Item:
v AJDG301 v LICIP08
v AJDG301
A6xx0333
A6xx0405
Explanation: A branch to a bad address was
attempted. Explanation: Unhandled exception in authority
recovery.
Failing Item:
v AJDG301 v LICIP08
v AJDG301
A6xx0334
A6xx0406
Explanation: Exception Handler could not be
removed. Explanation: Unhandled exception in data base
recovery.
Failing Item:
v AJDG301 v LICIP08
v AJDG301
A6xx0335
A6xx0407
Explanation: Code resumed to not valid address
following exception. Explanation: Unhandled exception in data base
initialization.
Failing Item:
v AJDG301 v LICIP08
v AJDG301
A6xx0336
A6xx0408
Explanation: Unhandled exception in journal recovery.
Failing Item:
v AJDG301 v LICIP08
v AJDG301
A6xx0401
A6xx0409
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
A6xx0402
Explanation: A machine check occurred during
A6xx0410
authority initialization.
Explanation: Unhandled exception in journal clean up.
Failing Item:
v AJDG301 v LICIP08
v AJDG301

A6xx0411 • A6xx0441
A6xx0411 A6xx0419
Explanation: Unhandled exception in commit Explanation: The information loaded from the install
recovery. media is not valid.
v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6xx0412 A6xx0420
Explanation: Unhandled exception in commit Explanation: The information loaded from the install
initialization. media is not valid.
v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6xx0413 A6xx0421
Explanation: Rebuild of recovery object index failed. Explanation: Bad return code creating a queue or
message.
Failing Item:
v AJDG301 v LICIP08
v AJDG301
A6xx0414
A6xx0422
Explanation: Install of operating system failed on read
from media. Explanation: The Load/Dump command failed.
v LICIP08 v LICIP08
v FI00300 v AJDG301
A6xx0415 A6xx0439
Explanation: Create user profile failed. Explanation: Opening the IPCF connection failed.
v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6xx0417 A6xx0440
Explanation: Initiating the initial process failed. Explanation: Termination code is not valid.
v LICIP08 v LICIP08
v AJDG301 v AJDG301
A6xx0418 A6xx0441
Explanation: The information loaded from the install Explanation: Power off system command failed.
media is not valid.
Failing Item:
v LICIP08 v AJDG301
v AJDG301

A6xx0443 • A6xx0802
v LICIP08
A6xx0443
v AJDG301
Explanation: Programmed IPL command failure.
v LICIP08
Explanation: Maximum stack size exceeded in process
v AJDG301 or task.
Failing Item:
A6xx0446
v LICIP08
Explanation: Error during machine termination. v AJDG301
Failing Item:
v LICIP08 A6xx0620
v AJDG301 Explanation: Event management index is not usable.
Failing Item:
A6xx0447
v LICIP08
Explanation: Failure to reach MI boundary. v AJDG301
Failing Item:
v LICIP08 A6xx0650
v AJDG301 Explanation: Resource management segment could
not be created or extended.
A6xx0449 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.
A6xx0506 The problem may also be that there is not enough

auxiliary storage.
Explanation: Attempt to destroy a task with critical
flag on. Failing Item:
v AJDG301
Failing Item:
v LICIP08
A6xx0801
v AJDG301
Explanation: Invalid LID directory detected.
A6xx0507 Response: During system IPL, the LIDMgr detected
an I/O failure or media failure while trying to read the
Explanation: A critical process terminated. This SRC
LID directory.
will be in the LPAR's panel.
Failing Item:
LIC detected an attempt to terminate a process with its
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.
The system error condition that began process
A6xx0802
termination is most commonly a storage error or LIC
exception handling. Explanation: LID directory unusable.
Response: Perform LICIP08 - save and send in the Response: During system IPL, the LIDMgr detected
Main Store Dump, collect LIC and Product Activity that the LID directory and associated Load Source is
Logs. not usable.
Failing Item: Reinstall the Licensed Internal Code by using Utilities

A6xx0901 • A6xx1604
to install and restore IBM i Licensed Internal Code.

A6xx1104
For more information, contact IBM Service Support.
Explanation: Failure reading media or not install
Failing Item: media.
v AJDG301 Response: Determine that correct install media is
loaded. If correct install media is installed, media could
A6xx0901 be corrupt. Obtain another copy of the install media
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 A6xx1201
a system termination while the LinkLoader is
performing its work. Explanation: Critical database segment could not be
created.
Reinstall the Licensed Internal Code by using Utilities
to install and restore IBM i Licensed Internal Code. Failing Item:
v LICIP08
A6xx0902 v AJDG301
Explanation: Unable to perform programmed IPL.

A6xx1204
Response: The LinkLoader was not successful in
performing a programmed IPL. Explanation: Error in constraint enforcement.
Perform a system IPL. If the problem persists, examine Failing Item:

the main storage dump and determine the reason for v LICIP08
the failure of the programmed IPL. v AJDG301
A6xx0903 A6xx1210
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.
Contact your next level of support. v AJDG301
A6xx0904 A6xx1215
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
A6xx1001 A6xx1219
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
A6xx1604
A6xx1103
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

A6xx1724 • A6xx4404
v AJDG301
A6xx41FD
Explanation: Installation of LIC failed.
A6xx1724
Response: A main store dump was initiated. Words 12
Explanation: An attempt to create a segment failed.
and 13 of this SRC contain additional diagnostic
Response: The create could fail for two reasons: information.
v A code problem. Perform the procedure indicated in To recover the partition using the previously installed
the failing item list. LIC, perform a B-mode IPL. You can then re-try the
v No free auxiliary storage on the system. Add installation of LIC. Otherwise, install LIC using
additional DASD if the create failed because no physical media.
auxiliary storage was available.
To determine what caused this failure, collect SRC
Failing Item: information and main store dump and contact your
v LICIP08 next level of support.
v SVCDOCS
A6xx1730
Explanation: An IPL is needed to restore system A6xx4401
performance. Explanation: Missing DASD units.
Response: Licensed Internal Code has detected a Response: Copy the current main storage dump to
condition that is impacting system performance. System media.
operation can continue, but system performance may
be noticeably reduced until the next IPL. For more information on how to perform a Main
Look at the Product Activity Log entry, and find the
value at offset x'000180'. If the value equals x'00000122',
the error was caused by too much processor memory A6xx4402
being installed. Explanation: Missing DASD units.
For more information, contact IBM Service Support. Response: Copy the current main storage dump to
Failing Item: media. Then exit the Main Storage Dump Manager.
v UPLF1 For more information on how to perform a Main
A6xx3000
A6xx4403
Explanation: LPAR service function directed a Main
Storage Dump. Explanation: Storage Management failed to reach full
paging.
media. For more information on how to copy a Main Response: Copy the current main storage dump to
Storage Dump, refer to Copying a main storage dump. media.
Failing Item: For more information on how to perform a Main
v AJDG301 Storage Dump, refer to Copying a main storage dump.
A6xx41FC A6xx4404
Explanation: Installation of LIC failed. Explanation: Auto copy failed or not attempted.
Response: Words 12 and 13 of this SRC contain Response: Copy the current main storage dump. If
additional diagnostic information. copying to system ASP, existing copies may need to be
deleted or renamed. Then exit the Main Storage Dump
Install LIC using physical media. Manager.
To determine what caused the failure, collect SRC For more information on how to perform a Main
information and contact your next level of support. Storage Dump, refer to Copying a main storage dump.
Failing Item:
v SVCDOCS

A6xx4405 • A6xx4713
A6xx4405 A6xx4700
Explanation: System ASP threshold exceeded after Explanation: Processor On Demand error detected.
auto copy done.
Response: Processor on Demand Data Block key is not
Response: Delete other system ASP copies or exit the valid.
Main Storage Dump Manager and then from DST copy
Replace the Processor Capacity card.
the Auto Copy to media and then delete the Auto Copy
in system ASP. Failing Item:
v CTLPNCD
A6xx4420
Explanation: MSD Manager not configured to save A6xx4701
dump information. Explanation: Processor On Demand error detected.
Response: The platform produced dump data, but the Response: Processor On Demand Data Block contains
Main Storage Dump (MSD) Manager was not data that does not match the expected data.
configured to automatically copy the dump to an
Auxiliary Storage Pool (ASP). The dump will be lost if Contact your service provider.
the system power is lost. Use MSD Manager to
Failing Item:
manually copy the current platform dump to media or
an ASP. v AJDG301
A6xx4421 A6xx4703
Explanation: Insufficient space in the ASP to store a Explanation: Processor On Demand error detected.
platform dump. Response: Processor On Demand Serialization has
Response: The platform produced dump data, and the failed during IPL.
Main Storage Dump (MSD) Manager was configured to Contact your service provider.
automatically copy the dump to an Auxiliary Storage
Pool (ASP), but there was not sufficient free space Failing Item:
available in the ASP. The dump will be lost if the v AJDG301
system power is lost. Manually copy the current
platform dump from the platform by performing one of
the following: A6xx4710
v Make room in the designated ASP and then use the Explanation: Processor On Demand error detected.
MSD Manager to copy the current platform dump to
Response: SPCN communication failure during
ASP.
Processor On Demand.
v Use the MSD Manager to delete other dump copies,
then copy the current platform dump to ASP. Look in the Product Activity Log for other SPCN errors
and perform the actions indicated for those errors.
dump to a different ASP. Failing Item:
v Use the MSD Manager to copy the current platform v SPNLCRD
dump to media.
A6xx4712
A6xx4422
Explanation: A platform dump is saved in MSD
Response: Correct any Processor Capacity card or
Manager.
SPCN failures.
Response: The platform produced dump data. The
Failing Item:
dump data was copied to the Main Storage Dump
(MSD) Manager. v CTLPNCD
Failing Item:
A6xx4713
v PLDUMP
Explanation: Incorrect Processor Capacity Card
installed.
Response: The Processor Capacity Card is the failing

A6xx4714 • A6xx5002
item since it has been swapped in from a different

A6xx4740
system.
Put the Processor Capacity Card back in the system it
came from, and reinstall this system's original Processor Response: The Processor On Demand Activation code
Capacity Card. just entered is not valid.
Failing Item: Contact your next level of support.
v CTLPNCD Failing Item:
v AJDG301
A6xx4714
Explanation: The CUoD data is not present. A A6xx4741
problem may exist.
Response: The Processor Capacity Card was changed
Response: An invalid Processor On Demand
and there may be a problem.
Activation code has been entered more than 5
If the system did have any activated standby consecutive times. Contact your service provider.
processors before the Processor Capacity Card was
Failing Item:
replaced, then new processor on demand activation
codes must be obtained to restore the previous v AJDG301
activations.
Contact your service provider. A6xx4745
Explanation: Processor Capacity card replaced on
A6xx4715 activated POD system.
Explanation: Processor On Demand error detected. Response: Contact IBM Support to order a
replacement Processor On Demand activation code.
Response: Correct any Processor Capacity card or
SPCN failures.
A6xx4747
Failing Item:
Explanation: 1 hour left in POD 14 day Trial
v CTLPNCD
Activation Period.
Response: If a new activation code was purchased, it
A6xx4730
should be entered now. Otherwise, the system will
Explanation: Processor On Demand error detected. revert back to its previous activation state at the end of
the Trial Activation Period.
Response: Processor On Demand standby processors
are in use.
A6xx5001
Contact your service provider.
Explanation: DST received no response from a work
Failing Item:
station controller.
v AJDG301
Response: The workstation I/O processor for the
system or partition console did not respond.
A6xx4731
Failing Item:
v RTRIP01
Response: The Processor On Demand Trial Activation v FI00380
period is not valid. Contact your next level of support.
v AJDG301
Failing Item:
v AJDG301 A6xx5002
Explanation: DST problem attempting to use the
A6xx4733 system console.
Explanation: Processor On Demand error detected. Response: A code problem occurred during an
Response: Contact your service provider. attempt to use the system console.
v AJDG301 v LICIP03

A6xx5003 • A6xx5008
v AJDG301 v AJDG301
v FI00380 v FI00380
A6xx5003 A6xx5008
Explanation: Service program failed. Explanation: DST console failed to respond. If an IPL
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
v FI00602 wait at least 35 minutes for the system to find and use
v USER the new LAN adapter. In this case, when the system is
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
A6xx5004 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
Response: The system console failed to respond. failure type. For example, if word 6 contained
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
v FI00320 means the following:
v FI00602 v xxxx where:
v USER – The twinaxial-related SRC is represented by the
v AJDG301 first 4 characters.
v FI00380 v yy where:
– 0A = No console tagged
A6xx5005 v zz where:
– 00 = Not defined by user (old default value)
– 01 = Twinaxial
Response: The workstation adapter system console – 02 = Operations Console (Direct) (obsolete)
failed to respond.
– 03 = Operations Console (LAN )
Failing Item: – 04 = Hardware Management Console (HMC) or
v WSAIP01 Thin Console
v FI00320
v FI00602 If you are attempting to use Operations Console, the
local console on a network uses words 3, 4, and 5. Use
v USER words 3 through 5 to select the appropriate section in
v AJDG301 the following list.
v FI00380 1. Word 3 is "1": No supported HW detected or HW
detected is not expected (for example, you replaced
the LAN IOA so the serial number is different) In
A6xx5007
some cases the serial number of the expected
Explanation: Service program failed. adapter may be shown in word 5.
Response: The workstation adapter console failed to 2. Word 3 is "2": The LAN IOA failed to report.
respond. 3. Word 3 is "3": Hardware error. Common error codes
in word 4:
Failing Item:
v 53001A80 and 53002AC0: Network, cable or the
v RTRIP07
LAN adapter may not be operational. Word 5
v FI00320 may contain the card position or serial number of
v FI00602 the adapter.
v USER

A6xx5010 • A6xx5090
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
v FI00719
should be activated shortly. Word 5 may contain
the card position or serial number of the adapter.
v CC10031A: Adapter was activated but did not A6xx5010
reach LinkUp state. The card was given more Explanation: IPL service function ended abnormally.
than a minute to link up to its partner (probably
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 A6xx5014
not resolve itself until something restarts the
Explanation: DST status. The Storage Management
device driver. Word 5 may contain the card
Dual Path Information Screen option to dump data to a
position or serial number of the adapter.
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. A6xx5015
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
v NEXTLVL
active but the PC failed to connect. Are the PC and
system on the same network and using the same
protocol? Can the PC ping the system? (ping A6xx5082
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
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.
A6xx5083
Word 9 is the card type.
v 3 Wrong cable detected. Word 8 is the card position. Explanation: IPL service function ended abnormally.
Word 9 is the cable ID. Response: A service program lost contact with the
v 4 Port in use. Word 8 is the card position. Word 9 is system console.
the card type.
Failing Item:
v FA Not configured for direct cable
v TWSIP01
Note: It is expected that a D-mode IPL with a new load v AJDG301
source direct access storage device (DASD) will show v USER
the console type value of 00. Examples of when this
can occur might be that the copy of data from a failing
A6xx5090
DASD did not copy all data or you are installing a new
logical partition. Also, there are times when the DASD Explanation: System startup failed in unattended IPL
is late reporting and the console type value was not mode.
retrieved in time. In these cases you can use the
console service function to set a console type value or Response: Perform the following:
attempt to contact the console again.

A6xx5092 • A6xx5126
v If reference code A6xx5090 is displayed on the v FI00130

control panel for more than 10 minutes, perform the
procedure indicated in the failing item list.
A6xx5121
v For reference code B6xx5090, perform the procedure
indicated in the failing item list. Explanation: LIC program exception occurred.
Failing Item: Response: System LIC detected a programming

problem for which a main storage dump may have
v LICIP11
been initiated. Collect the dump if available.
v FI00580
A problem log entry may be generated for this refcode.
v FI00500
v FI00021 v LICIP01
v FI00065 v AJDG301
v AJDG301
A6xx5122
A6xx5092 Explanation: LIC program exception occurred.
Explanation: System is in DASD migration mode. Response: System LIC detected an IOP programming
problem for which an IOP dump may have been
Response: Install Licensed Internal Code and Upgrade
initiated.
Load Source was specified but the key is not in the
manual position. Change the key position to manual Failing Item:
and perform a system IPL. v LICIP01
v FI00130
A6xx5094 v AJDG301
Explanation: IASP detected a failure during the vary v FI00131
on operation.
v LICIP12 Explanation: LIC program exception occurred.
Response: System LIC detected an interface problem
A6xx50FF with the IOP or an IOP programming problem for
Explanation: DST unrecoverable program error. which an IOP and main storage dump may have been
initiated.
Failing Item:
Failing Item:
v LICIP03
v LICIP01
v AJDG301
v FI00130
v FI00380
v AJDG301
v FI00131
A6xx5120
A6xx5126
exception.
selection.
problem. If performance or other system degradation is
occurring, the system may be operating with reduced Failing Item:
resources. v DISKDRV
Check the Product activity log for related entries. If this v STORIOA
reference code is logged with an error class of v DISKTRY
Informational, then no action is required.
v FI01106
Otherwise, perform the procedure indicated in the v FI01140
failing item list.
v FI01141
v LICIP01 v BACKPLN
v AJDG301

A6xx5127 • A6xx5219
A6xx5127 A6xx5193
Explanation: IOP timed out a disk command. Explanation: Virtual adapter not supported in a
shared memory partition.
Failing Item:
v DISKDRV Response: Use the hardware management console to
remove the virtual adapter from the partition.
v STORIOA
v DISKTRY v SVCDOCS
v FI01140
v FI01141 A6xx5194
v DEVTERM Explanation: Insufficient entitled memory for the I/O
v BACKPLN configuration.
Response: Use the hardware management console to
A6xx5128 increase the entitled memory capacity of the partition
and restart the partition.
Failing Item:
Failing Item:
v SVCDOCS
v FI01112
v FI01107
A6xx5206
Explanation: System LIC detected a missing IOP LIC
A6xx512D
code load.
Response: System LIC detected a missing IOP LIC
Response: Copy the IOP dump entry and any related code load during IPL of the IOP. This indicates that
entries from the Product Activity Log to suitable media, either the IOP code load is not installed on the system
and give to an IBM service representative. Load Source device or that system LIC was unable to
successfully read that load from the Load Source
device.
A6xx512E
Failing Item:
v LICIP01
Response: The system was in a D IPL mode when the v USER
problem was detected. A main storage dump was not
taken.
A6xx5209
Failing Item:
v LICIP01 Explanation: System LIC detected an IOP timeout
during IOP IPL.
v AJDG301
v FI00130 Response: Verify that all IOP cable connections are
secure, and check tape and other non-disk devices and
media to verify that they are in a ready state.
A6xx5192
Failing Item:
Explanation: Insufficient entitled memory for the I/O v LICIP01
configuration.
v USER
Response: Use the hardware management console to v FI00130
and restart the I/O adapter. To restart a storage I/O v AJDG301
adapter, use Hardware Service Manager to re-IPL the
virtual I/O processor that is associated with this I/O A6xx5219
adapter. To restart a communications I/O adapter, vary
the line off and vary it on using the vary configuration Explanation: LIC program exception occurred.
(VRYCFG) command. Response: An IOP signaled to system LIC that it had
Failing Item: entered a critical internal state. LIC automatically
attempted to restart the IOP.
v SVCDOCS

A6xx5275 • A6xx5340
This reference code is logged for information only. No and contact your next level of hardware service
action is required. support.
If this reference code appears in a serviceable event Failing Item:
view then service is required, work the faling items list. v LPARSUP
v FI00310
v FI00318
Response: LPAR configuration data does not match
v FI00065
current system configuration. The system will not IPL
v FI00130 past DST until the problem is corrected.
v AJDG301
Following is a list of problems which may have caused
this SRC to be reported:
A6xx5275 v Non-configured disk unit which was previously a
Explanation: The system issued a reset/reload to the load source on a partitioned system.
IOP. v Load Source configuration data does not match
partition for which it is being used.
Response: System Licensed Internal Code detected
that an IOP Reset/Reload has occurred, and that the v Load Source configuration data does not match
IOP successfully recovered. system serial number for which it is being used.
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
LAN/WAN communications lines under the IOP will Failing Item:
need to be restarted. Tape/Optical devices under the v LPRIP01
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
A6xx5312
with the same System Log ID, and perform any actions
indicated for those errors. Explanation: LIC program exception occurred.
Response: LPAR configuration data informational
A6xx5276 error.
Explanation: IOP Reset was issued. The LPAR configuration data was found to be in error
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
A6xx5313
may be able to continue normally. However, some
system service operations have been suspended and the Explanation: LIC program exception occurred.
system should be scheduled for power down as soon
as possible. Response: LPAR configuration data informational
error.
Failing Item:
The LPAR configuration data was found to be
v RTRIP08 inconsistent on a primary partition and could only be
v AJGLD01 corrected with an older copy of the data.
v FI00021 v LPARCFG
A6xx5310 A6xx5340
Explanation: LIC program exception occurred. Explanation: Secondary partition not running at
Response: System LIC detected a logical partition optimum.
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

A6xx5341 • A6xx6900

A6xx5380
A6xx5341 Response: Record the Product Activity Log (PAL) hex
optimum. Contact your next level of support.
Response: Check the primary partition Product Failing Item:
Activity Log for system memory entries from v LPARSUP
A6xx5390
A6xx5342 Explanation: LIC program exception occurred.
Explanation: Secondary partition not running at Response: Record the Product Activity Log (PAL) hex
optimum. data for this SRC or print the PAL entry.
Response: Check the Primary partition's Product Contact your next level of support.
Activity Log for system processor entries from Failing Item:
indicated for those entries. v LPARSUP
A6xx5343 A6xx5505
Explanation: Secondary partition not running at Explanation: The copying of DASD log data to the
optimum. IOP log was successful.
Response: Check the Primary partition's Product Response: IOP log data can be copied to a spool file
Activity Log for system memory errors from for examination by the development lab.
indicated for those entries. A6xx5555
Explanation: SLIC I/O DASD subsystem error
A6xx5344 recovery in progress.
optimum. A6xx5600
Response: The interactive performance specified in the Explanation: Unrecoverable read error.
configuration data for this partition could not be met.
Response: VPD data could not be read.
Look for other errors implicating hardware. There is no
Failing Item: way to know what VPD read has failed, but the
v LPARSUP resource is not usable and should generate an error.
If no such error occurred, call your next level of
A6xx5350 support.
Explanation: Secondary partition software release not Failing Item:
supported. v SVCDOCS
Response: The logical partition software version is
outside the supported release delta. A6xx6900
Check the Release Delta from the Primary partition Explanation: System bus error.
"Display Partition Release Level" screen.
Check the LPAR documentation for the release level of
the Primary partition and determine what the Failing Item:
supported Release Delta is. v NEXTLVL

A6xx6901 • A6xx6908
A6xx6901 A6xx6907
Explanation: Bus Expansion Adapter card failed. Explanation: High Speed Link (HSL) or PCI bridge
Response: LIC detected invalid data in the HSL I/O
Failing Item:
bridge VPD. The bridge and HSL loop may not have
v NEXTLVL become operational.
A6xx6902 the Service Action Log (SAL), or serviceable event view
Explanation: Bus Expansion Adapter card failed. you are working with, can be different from the failing
item list documented here. That is due to the
Response: Contact your next level of support. differences in system models and features installed.
Failing Item: If the Service Action Log (SAL) or serviceable event
v NEXTLVL view on the hardware management console, is available
then use the failing item list presented there for
servicing this reference code.
A6xx6905
Explanation: Optical bus failed. failing item list documented here. By following the
Response: Contact your next level of support. procedures in the symbolic FRUs listed here you will
Failing Item: and features installed.
v NEXTLVL
A6xx6906
Failing Item:
Explanation: High Speed Link (HSL) or PCI bridge v SIIOADP
v OPT_CLN
Response: LIC could not access part of the HSL I/O
bridge VPD. The bridge and HSL loop may be
A6xx6908
prevented from becoming operational.
viewer you are working with, can be different from the Response: LIC data in the I/O bus VPD could not be
failing item list documented here. That is due to the accessed. The I/O Bus identified in the SRC may not
differences in system models and features installed. have become operational.
If the Service Action Log (SAL) or serviceable event If there is a B6xx 6906 reference code, close this
view on the hardware management console is available problem in the serviceable event view you are working
then use the failing item list presented there for with and work the 6906 error.
servicing this reference code.
If a serviceable event view is not available then use the the Service Action Log (SAL), or serviceable event view
failing item list documented here. By following the you are working with, can be different from the failing
procedures in the symbolic FRUs listed here you will item list documented here. That is due to the
isolate to the correct FRU list based on system model differences in system models and features installed.
If the Service Action Log or serviceable event view on
NOTE: A fiber optic cleaning kit may be required for the hardware management console or service processor
optical HSL connections. is available then use the failing item list presented there
Failing Item:
v SIIOADP If a serviceable event view is not available then use the
v OPT_CLN

A6xx6909 • A6xx6961

v SIIOADP
v OPT_CLN A6xx6938
Explanation: Not valid system configuration detected.
A6xx6909
Response: This system model does not allow a
Explanation: High Speed Link (HSL) or PCI bridge configuration of more than three (non-OptiConnect)
card slot I/O bridge failure. I/O Processors.
Response: LIC detected invalid data in the I/O bus Power down the system and remove the extra
VPD. The bus and resources associated with it may not (non-OptiConnect) I/O Processor(s) so that there are
be operational. three or less. Restart the system.
the Service Action Log (SAL), or serviceable event view A6xx6944
you are working with, can be different from the failing
Explanation: Missing or failed I/O processor cards.
item list documented here. That is due to the
differences in system models and features installed. Response: A system bus appears to be empty. If the
bus is not empty, two I/O processors in consecutive
slots may be missing or broken. If there are broken I/O
viewer on the hardware management console is
processors, then another more serious SRC has
available then use the failing item list presented there
occurred. Otherwise find the bus number for this
failure from the Product activity log and use the system
If a serviceable event view is not available then use the configuration list to verify the configuration of the I/O
failing item list documented here. By following the processors on that bus.
Failing Item:
and features installed. v FI00317
v FI00316
If the serviceable event view only indicated a frame or
enclosure see the locations section for the frame or v AJDG301
enclosure type. The location of the HSL I/O Bridge will
be given in the locations tables. A6xx6960
NOTE: A fiber optic cleaning kit may be required for Explanation: Multi-adapter Bridge or PCI Bridge card
optical HSL connections. slot error, do not use card slot.
Failing Item: Response: Slot unavailable due to 64 bit card in
v SIIOADP adjacent slot.
v OPT_CLN One of the messages documented with the symbolic
FRU will describe the problem. See SLOTERR symbolic
A6xx690A FRU for a list of messages and corrective actions.
Explanation: Associated adapter not found in this Failing Item:

partition. v SLOTERR
Failing Item:
v LICIP16 A6xx6961
Explanation: Multi-adapter Bridge or PCI Bridge card
A6xx6910 slot error, do 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
Failing Item:
v LICIP07
v FI00310 Licensed Internal Code.
v FI00318
v FI00065 the Service Action Log (SAL), or serviceable event view
v FI00130 you are working with, can be different from the failing

A6xx6962 • A6xx6964
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
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
the failing item list presented there for servicing this
v MASBUS
reference code.
If serviceable event view is not available then use the
A6xx6962
Explanation: Multi-adapter Bridge or PCI Bridge card procedures in the symbolic FRUs listed here you will
slot error, do not use card slot. isolate to the correct FRU list based on system model
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 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 A6xx6964
Item with the card slot error is in the Failing Item list
Response: One of several errors or configuration
problems has occurred under a Multi-adapter Bridge or
PCI Bridge. If you are using the Service Action Log
For this reference code the failing item list presented in (SAL), or the serviceable event viewer on the hardware
the Service Action Log (SAL), or serviceable event view management console or the service processor, then the
you are working with, can be different from the failing correct FRU, description and card position(s) will be
item list documented here. That is due to the listed. Use the FRUs and descriptions in the serviceable
differences in system models and features installed. event view you are working with to determine the
problem.
If the Service Action Log, or serviceable event view on
the hardware management console is available then use If you do not have access to the Service Action Log, or
the failing item list presented there for servicing this serviceable event view on the hardware management
reference code. console or service processor, then word 4 of the SRC
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.
isolate to the correct FRU list based on system model 1. xxxx2022 - IOP found in slots owned by a Linux
and features installed. partition. The Multi-adapter Bridge or PCI Bridge
and PCI Bridge set that it controls are assigned to a
Failing Item: Linux partition. The IOP found in the SLOT
v SLOTERR indicated by the DSA in word 7 will not be
configured.
v MASBUS
2. xxxx2014 - I/O adapters were found under the
Multi-adapter Bridge or PCI Bridge but there is no
A6xx6963 IOP to support them. The adapters cannot be used.
Explanation: Multi-adapter Bridge or PCI Bridge card 3. xxxx2015 - An card type was found that cannot be
slot error, do not use card slot. supported in the card position where it is located.
Response: Power control failure, do not use slot.

A6xx6965 • A6xx696B

A6xx6968
Internal Code and the corrective action. Explanation: Multi-adapter Bridge or PCI Bridge
Failing Item:
v MABRCFG Response: IOA removed from Multi-adapter Bridge or
PCI Bridge slot.
A6xx6965 On the previous IPL an I/O adapter was in the card

slot specified in word 7 of the SRC. That I/O adapter
Explanation: Multi-adapter Bridge or PCI Bridge was not detected on this IPL.
Response: Card type not supported in this slot. further description of the problem detected by Licensed
An I/O processor or I/O adapter card type is installed Internal Code and the corrective action.
in the location indicated in word 7 of the SRC. The Failing Item:
card type is not supported in that slot under the
v MABRCFG
Multi-adapter Bridge or PCI Bridge. The card is
unavailable.
A6xx6969
further description of the problem detected by Licensed Explanation: Multi-adapter Bridge or PCI Bridge
Internal Code and the corrective action. configuration 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
A6xx6966 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 or PCI Bridge location.
Response: I/O processor removed from Multi-adapter further description of the problem detected by Licensed
Bridge or PCI 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.
A6xx696A
Internal Code and the corrective action. Explanation: Card slot test failed.
v MABRCFG v LICIP14
v FI00131
A6xx6967 v BACKPLN
configuration change or error. A6xx696B
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 or PCI
processor card the adapter was assigned to. The I/O Bridge domain as the I/O Adapter. Do one of the
processor was not detected on this IPL. following. Either:
See MABRCFG symbolic FRU for the list of messages, a -- Using the hardware management console or a
further description of the problem detected by Licensed customer PC with a Web browser access the Advanced
Internal Code and the corrective action. System Management Interface (ASMI) and disable PCI
error injection policy.
Failing Item:
v MABRCFG OR:

A6xx6970 • A6xx6973
-- Vary off the I/O Adapter. Using Hardware Service

A6xx6971
manager in SST/DST, locate the I/O Adapter resource.
Using concurrent maintenance on the associated Explanation: High Speed Link (HSL) or PCI bridge
packaging resource, remove the I/O Adapter and card slot resource failure.
install it in a location that does not have I/O Processors
Response: A failure occurred in a Multi-adapter
on the same Multi-adapter bridge domain.
Bridge or PCI Bridge or on the bus to the card location
OR: it controls.
-- Vary off the I/O Adapter. Use the concurrent If a serviceable event view is available, use the failing
maintenance option in Hardware Service Manager in item list presented there for servicing this reference
SST/DST to power off all I/O Processors located on the code.
same Multi-adapter Bridge or PCI Bridge domain as
If a serviceable event view is not available, use the
the I/O Adapter. Use concurrent maintenance to power
failing item list documented here.
off and power on the I/O Adapter. Then use
concurrent maintenance to power on the I/O Failing Item:
Processors located on the same Multi-adapter Bridge or v MABIP02
PCI Bridge domain as the I/O Adapter.
v MA_BRDG
v MASBUS
A6xx6970
v PIOCARD
A6xx6972
Response: A system PCI bus failure was detected.
Word 7 of the SRC contains the bus number. Explanation: High Speed Link (HSL) or PCI bridge
This failure can occur when a tower in an HSL loop is
powered off using concurrent maintenance. If this is the Response: Multi-adapter Bridge (MaB) or PCI Bridge
case, close this problem. failure detected.
This error is most likely in the hardware that makes up For this reference code the failing item list presented in
the PCI bus, the PCI bus side of the HSL I/O bridge or the Service Action Log (SAL), or serviceable event
the Multi-adapter Bridge or PCI Bridge. In some cases viewer you are working with, can be different from the
it may be caused by a failing IOP in the Multi-adapter failing item list documented here. That is due to the
Bridge or PCI Bridge domain. When an IOP is causing differences in system models and features installed.
the problem, the failing IOP cannot be identified. If the Service Action Log (SAL) or serviceable event
NOTE: This SRC can occur for the PCI bus resource on viewer on the hardware management console is
a PCI bus in an I/O expansion unit when the unit is available then use the failing item list presented there
powered off for a concurrent maintenance action. for servicing this reference code.
If the Service Action Log, or serviceable event view on If a serviceable event view is not available then use the
the hardware management console or service processor, failing item list documented here. By following the
is available then use the failing item list presented there procedures in the symbolic FRUs listed here you will
for servicing this reference code. isolate to the correct FRU list based on system model
failing item list documented here. Failing Item:
v MA_BRDG
A6xx6973
Failing Item:
v SI_PHB Explanation: High Speed Link (HSL) or PCI bridge
v PRI_PCI
v MA_BRDG Response: Multi-adapter Bridge or PCI Bridge has
detected a problem in the card installed in the location
v MABIP03 specified in word 7 of the SRC. Use the FRU list in the
v BRDGSET Service Action Log (SAL), or serviceable event view
v OPT_CLN you are working with. If you are working from this
document's FRU list use the Symbolic FRU BRDGSET
to determine the failing items.
Failing Item:

A6xx6974 • A6xx6982
v BRDGSET NOTE: A fiber optic cleaning kit may be required for

v SIIOADP optical HSL connections.
v SICNTRL
A6xx6974 v OPT_CLN
configuration change or error. A6xx6981
Response: PCI I/O processor rejected the assignment Explanation: High Speed Link (HSL) or PCI bridge
of or the removal of an I/O adapter. card slot I/O bridge failure.
Failing Item: Response: For Power5 and newer servers, service this
v MABRCFG error using the B7006981 service information.
A6xx6975 Cycle power on the frame identified as the frame with

failed HSL I/O Bridge prior to replacing FRUs.
Explanation: The system issued a reset/reload to the
service processor. The FRU list displayed in the Service Action Log (SAL),
or serviceable event view you are using, may vary from
Response: Service processor error. the failing item list given in this document. Use the
Failing Item: FRU list in the serviceable event view if it is available
to you.
v AJDGP01
If you find either a B6xx 6982 or B6xx 6984 SRC logged
at approximately the same time as this SRC then they
A6xx6976 were caused by the same failure. If you find a 6982
Explanation: Service processor failure. SRC logged at approximately the same time then close
this problem and service the 6982 SRC. The failing item
Response: For this reference code the failing item list listed for this SRC is one of the failing items listed for
presented in the Service Action Log (SAL), or B6xx 6982. If the serviceable event view's entry for this
serviceable event view you are working with, can be SRC has a location listed then record the location for
different from the failing item list documented here. use in servicing the 6982 SRC.
That is due to the differences in system models and
features installed. NOTE: This SRC can occur for the HSL I/O Bridge
resource in an I/O expansion unit when the unit is
If the Service Action Log (SAL) or a serviceable event powered off for a concurrent maintenance action.
viewer on the hardware management console is
available then use the failing item list presented there NOTE: A fiber optic cleaning kit may be required for
for servicing this reference code. optical HSL connections.
If a serviceable event viewer is not available then use Failing Item:

the failing item list documented here. By following the v SIIOADP
procedures in the symbolic FRUs listed here you will v OPT_CLN
A6xx6982
Failing Item:
v SVCPROC Explanation: High Speed Link (HSL) connection
failure.
A6xx6980 Response: For Power5 and newer servers, service this

Explanation: Network Interface Controller / IO Hub Otherwise, continue with this information.
failure.
If this SRC is not in the Service Action Log (SAL) or
Response: For Power5 and newer servers, service this serviceable event view you are using, then it is
error using the B7006980 service information. informational or statistical only. It does not require a
Otherwise, continue with this information. service action.
The FRU list displayed in the Service Action Log (SAL) Otherwise, this is a connection failure on an HSL link.
or serviceable event view you are working with, may Perform the procedure indicated in the failing item list.
vary from the failing item list given in this document.
Use the FRU list in the serviceable event view if it is Failing Item:
available to you. v RIOIP09

A6xx6983 • A6xx6985
v HSL_LNK into decimal format to recognize the loop number in

v SIIOADP HSM.
v SICNTRL This SRC can be caused by a tower on the HSL loop
v REM_NIC powering off.
v OPT_CLN This SRC may also appear in the Service Action Log
(SAL), or serviceable event viewer you are using, with
a B6xx 6982 or B6xx 6981 logged at approximately the
A6xx6983
same time. In that case the other SRC is reporting a
Explanation: A High Speed Link (HSL) / RIO / 12X failure and this SRC is reporting that the alternate HSL
loop configuration event was detected. The loop may path is now being used. Service the other SRC if
have an unsupported configuration or a configuration present.
that is not valid or the loop is in a state that LIC is
logging for potential future reference.
A6xx6985
Problem determination: LIC is reporting an event
Explanation: High Speed Link (HSL) loop status
about the state of a RIO / HSL / 12X loop. Word 4 of
message.
the SRC contains the program return code (PRC)
which. identifies the state or problem with the loop. Response: For Power5 and newer servers, service this
For Power5 and newer servers, if this event appears in
a serviceable event view then a service action is
required. This SRC may also be logged as informational If this SRC is not in the Service Action Log (SAL), or
when it is recording information about the loop that is serviceable event view you are using, then it is
not a problem for the LPAR. informational. Use FRU SIRSTAT to determine what
this SRC means. Otherwise, continue with the
following steps:
view then no service is required. To determine what the
event meaning is record the PRC in word 4 of the SRC This error can appear as a serviceable event when a
then use symbolic FRU SIRGCFG. This completes the tower, or I/O unit or another system in the loop did
procedure. not complete powering on before LIC on this system
checked this loop for errors. Search the Product
If this event appears in a serviceable event view then
Activity Log (PAL) for the last B6xx 6985 SRC logged
search for a B7006983 serviceable event logged at about
for this loop and use FRU SIRSTAT to determine if this
the same time.
error requires service. If the last entry indicates the
Did you find a B7006983 serviceable event logged at loop is functioning (determined by FRU SIRSTAT) then
about the same time in the LPAR? no service action is required, close this problem
v YES - Service this error by working the B7006983 There may be multiple B6xx 6985 logs with xxxx 3205
error. in word 4 errors for the same loop resource in the
v NO - Continue working this SRC. If you are using serviceable event view. This is caused by retry and
the Service Action Log (SAL) the FRU description recovery attempts. If there is a B6xx 6985 with xxxx
may already indicate the configuration problem. 3206 or xxxx 3208 in word 4 after the above B6xx 6985
Otherwise record the PRC in word 4 of the SRC. Use entries in the PAL, then the recovery efforts were
symbolic FRU SIRGCFG to determine the 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.
A6xx6984 Otherwise perform the following:
v Perform RIOIP06 to determine if any other
Explanation: High Speed Link (HSL) loop status
systems are connected to this loop and return
message.
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
continue with the steps that follow, otherwise go
An HSL loop has switched to its alternate path. This is
to step 2.
an informational SRC only.
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)

A6xx6986 • A6xx6988
resources. Ignore B6xx 6982 and B6xx 6984 Failing Item:

entries. If there are HSL failures on other v TWRCARD
system(s) then continue with the steps that
v CBLALL
follow, otherwise go to step 2.
v Repair the problems on the other systems and
return to this step. After making repairs on the A6xx6987
other system(s) check the Product Activity Log Explanation: High Speed Link (HSL) connection
(PAL) of this system for a B6xx 6985 logged after failure.
the repairs you made on the other system(s). If
you find one then continue with the steps that Response: For Power5 and newer servers, service this
follow, otherwise go to step 2. error using the B7006987 service information.
v For the B6xx 6985 log you found, use FRU Otherwise, continue with this information.
SIRSTAT to determine if the loop is now Failures are occurring on the HSL link.
complete. If the loop is complete then this
problem has been resolved. Use RIOIP01 to verify There may be B6xx 6982 errors logged on the same
that the loop is now working properly. loop and about the same time as this error. Close those
Otherwise, go to step 2. errors and continue to correct the problem by working
this error.
2. Use the serviceable event's FRU list when it is
available. If this SRC appears in the Service Action v If there is a cable FRU in the serviceable event entry:
Log (SAL), or the serviceable event view you are 1. If the connection is copper and either end has a
using, with the Symbolic FRU HSL_LNK or loose connection, re-seat the cable. To do this,
HSLxxxx listed as a FRU, then perform problem disconnect the connection and wait a minimum
isolation procedure RIOIP01. Otherwise exchange of 30 seconds. Then reconnect the cable and
the FRUs listed in the serviceable event view. complete the tightening process in at most 30
seconds. Repeat the process at the other end of
NOTE: A fiber optic cleaning kit may be required for the cable. If the error persists, replace the FRUs in
optical HSL connections. the Service Action Log (SAL), or serviceable event
view you are using.
Failing Item:
2. If the connection is optical, clean the connections
v SIRSTAT at both ends of the cable. If the error persists,
v HSL_LNK replace the FRUs in the Service Action Log (SAL),
v SIIOADP serviceable event view you are using.
v SICNTRL 3. If the error persists, replace the FRUs at each end
of the cable starting with the FROM FRU listed in
v OPT_CLN
the serviceable event view you are using.
v If there was no cable in the Service Action Log
A6xx6986 (SAL), or serviceable event view you are using, then
Explanation: System bus error. replace the FRUs listed in the serviceable event view.
Response: For Power5 and newer servers, service this Failing Item:
error using the B7006986 service information. v HSL_LNK
Otherwise, continue with this information. v OPT_CLN
During IPL, system LIC detected an HSL I/O bridge
that was already initialized. The bridge should have A6xx6988
been in a flushed and uninitialized state after powering
on. There is a problem with SPCN components that Explanation: A High Speed Link (HSL / HSL2) or
prevented the tower from powering off after a previous RIO / RIO-G loop was detected on the system this
power off was issued. The tower will not be configured LPAR is running on. This version of the operating
for this IPL. system does not support resources on an HSL / HSL2
/ RIO / RIO-G loop. If resources on the loop are
This reference code is equivalent to 1xxx 90F0. When assigned to this LPAR, for example in the partition
referring to the "CBLALL" symbolic FRU in the Failing profile, the resources will not show up in this IBM i
Item list, perform the "CBLALL" procedure using LPAR.
reference code "90F0".
Word 5 of the SRC identifies the frame. Determine the
frame by breaking down word 5:
Word 5 -> xxxx xxNN where: NN is the frame number
in hexadecimal format.

A6xx6990 • A6xx69C3
It indicates the presence of a wrap plug on the local

A6xx6990
optical link card.
Response: The FRU list displayed in the Service A6xx69A8
Action Log (SAL), or serviceable event view you are
Explanation: Informational bus reference code.
in this document. Use the FRU list in the serviceable Response: This reference code is for information only
event view if it is available to you. and might include the following:
Failing Item: v Optical speed encode.
v SVCPROC v Broken optical links now operational.
v Other information.
A6xx6991
A6xx69B8
Explanation: Bus hardware configuration problem.
Failing Item:
v AJDGP01 Response: Contact your next level of support.
Failing Item:
A6xx6992 v NEXTLVL
A6xx69C1
Failing Item:
v AJDGP01 Explanation: A failure occurred communicating with
another LPAR or system participating in Opti-connect
with this LPAR or system. Starting with IBM i release
A6xx6993 7.1 this event will be logged in the Product Activity
Explanation: Service processor failure. Log but it will not be in the Service Action Log or the
Problem Log. This event normally occurs when the
Response: A failure occurred with the service other LPAR or system is powered off. If both LPARs or
processor hardware or the service processor LIC. systems are running and have no Opti-connect errors
The FRU list displayed in the Service Action Log (SAL), then this event is indicating a possible problem with
or serviceable event view you are working with, may Opti-connect.
vary from the failing item list given in this document. Response: Contact your next level of support if you
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.
v SVCPROC v NEXTLVL
v AJDGP01
A6xx69C2
A6xx6994
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.
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 A6xx69C3
Explanation: HSL Opticonnect normal disconnect from
A6xx699C 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

A6xx69C5 • A6xx69C8
participating in HSL Opticonnect with the remote sure to record all words in the SRC. Contact your next
system or partition on the same HSL loop. Possible level of support.
reasons include:
Failing Item:
v A remote system or partition went off line due to a
v REM_SYS
normal power off or disable of HSL Opticonnect.
A6xx69C7
A6xx69C5
Failing Item: from a remote system or partition due to an
v NEXTLVL unexpected event or failure. LIC will attempt to recover
from the error. Intervention at the local or remote
system or partition may be required.
A6xx69C6
Possible causes are: time out, hang or hardware failure.
Explanation: HSL Opticonnect abnormal disconnect The problem may be with: the local system or partition
from other sys. or partition. or the remote system or partition.
Response: The local system or partition disconnected If there was not a complete HSL loop before this error
from a remote system or partition due to an then a failure or power down in an HSL component
unexpected event or failure. The problem is most likely between the local system or partition and the remote
with the remote system or partition. Intervention at the system or partition could have caused this error. Check
remote system is most likely required. Examine both for SRCs with FRUs like: HSL cables, HSL I/O bridge
the local and remote HSL OptiConnected systems or or a power problem in an expansion I/O tower or unit
partitions for problems on this HSL loop. on this loop.
Possible reasons include: A fatal error in software or Examine the SAL or serviceable event view you are
hardware in the remote system or partition or a power working with on the local system or partition for
failure in the remote system. failures on the same loop, or with the Network
If there was not a complete HSL loop before this error Interface Controller at approximately the same time.
occurred then a failure or power down in an HSL Examine the remote system or partition for problems.
component between the local system or partition and Correct any HSL or NIC problems you find with the
the remote system or partition could have caused this remote and local systems or partitions.
error. Check for a problem with: an HSL cable, HSL
I/O bridge or a power problem in an expansion I/O If there are no problems with the remote system or
tower or unit on this loop. partition and there are no problems with the local
Examine the Service Action Log (SAL), or serviceable Log (PAL) information for this failure on both systems.
event view you are using on the local system or Be sure to record all words in the SRC. Contact your
partition for HSL failures on the same HSL loop at next level of support.
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
then examine the Service Action Log (SAL), or v LOC_SYS
system or partition for problems on the same HSL loop A6xx69C8
at approximately the same time this error occurred.
Correct any problems you find with the remote and from other sys. or partition.
local systems or partitions that happened at
approximately the same time and involve HSL Response: The local system or partition disconnected
Opticonnect or HSL loop components or Network from a remote system or partition due to an
Interface Controllers. When the remote system is IPL'd unexpected event or failure. All of the HSL
it will automatically reconnect with this system or OptiConnect connections on this loop will be in a failed
partition. state. LIC will attempt to recover from the error.
Intervention at the local or remote system or partition
If there are no problems with the remote system or may be required. Possible causes are:
partition and there are no problems with the local
v time out of a critical message
Log information for this failure on both systems. Be v LIC code / table problem

A6xx69C9 • A6xx69D8
v Network deadlock detected system or partition for HSL Opticonnect problems that
occurred at approximately the same time this error
The problem may be with: occurred.
v The local system or partition
v The remote system or partition
failure on all systems and partitions on this HSL loop.
Be sure to record all words in the SRCs. Contact your
Examine the Service Action Log (SAL), or serviceable next level of support with the information you have
event view you are using, on the local system or collected.
partition for HSL failures on the same HSL loop, or
with the Network Interface Controller at approximately Failing Item:
the same time this error occurred. v AJDG301
v REM_SYS
Examine the Service Action Log (SAL), or serviceable v LOC_SYS
event view you are using, on the remote system or
partition for problems on the same HSL loop or with A6xx69CF
the Network Interface Controller at approximately the
same time this error occurred. Explanation: HSL Opticonnect abnormal disconnect
Correct any problems you find with the remote and Response: LIC internal error. All systems participating
local systems or partitions that happened at in HSL OptiConnect will be disconnected. The system
approximately the same time and involve HSL must be re-IPL'd to recover. Before re-IPL'ing the
Opticonnect or HSL loop components or Network system initiate a main store dump.
Interface Controllers.
After getting the dump, examine the Service Action
If there are no problems with the remote system or Log (SAL), or serviceable event view you are using, on
partition and there are no problems with the local the local system or partition for HSL Opticonnect
system or partition then collect all the Product Activity failures that occurred at approximately the same time
Log information for this failure on all systems or this error occurred.
partitions. Be sure to record all words in the SRCs. Examine the remote systems or partitions for problems.
Contact your next level of support. Examine the Service Action Log (SAL), or serviceable
Failing Item: event view you are using, on the remote systems or
partitions for HSL Opticonnect problems that occurred
v REM_SYS at approximately the same time this error occurred.
v LOC_SYS
v AJDG301 failure on all systems and partitions on this HSL loop.
Be sure to record all words in the SRCs. Contact your
A6xx69C9 next level of support with the information you have
collected.
from other sys. or partition. Failing Item:
v AJDG301
from a remote system or partition due to an failure in a
LIC virtualized bus unit. LIC will attempt to recover A6xx69D0
from the error. Possible causes are:
v LIC problem where the local bus unit is off line.
v LIC problem where the remote bus unit is off line. Response: Contact your next level of support.
Failing Item:
Examine the Service Action Log (SAL), or serviceable v NEXTLVL
event view you are using, on the local system or
partition for HSL Opticonnect failures that occurred at
approximately the same time this error occurred. A6xx69D8
Examine the Service Action Log (SAL), or the Response: Contact your next level of support.
Failing Item:
v NEXTLVL

A6xx69D9 • A6xx7004
A6xx69D9 A6xx69E0
Explanation: Host Ethernet Adapter (HEA) failure. Explanation: Bus Expansion Adapter card failed.
Response: Firmware detected a hardware failure in Response: Contact your next level of support.
the Host Ethernet Adapter (HEA).
Failing Item:
v HEA
A6xx69E8
A6xx69DA
required.
Failing Item:
A6xx69DB v NEXTLVL
Explanation: LIC failure.

A6xx69F0
Response: A Licensed Internal Code error occurred.
The partition will continue to run with this Host Explanation: Bus Expansion Adapter failed.
Ethernet Adapter (HEA) disabled. Perform a partition Response: Contact your next level of support.
dump and then IPL the partition to recover the HEA.
Send the partition dump to your next level of support. Failing Item:
v SVCDOCS
A6xx69F8
A6xx69DC Explanation: Bus Expansion Adapter failed.
Explanation: The Host Ethernet Adapter (HEA) is not Response: Contact your next level of support.
connected to the Ethernet switch.
Failing Item:
Response: The Host Ethernet Adapter (HEA) is not v NEXTLVL
connected to the Ethernet switch. If the HEA
connection is not needed, no service action is required.
A6xx7001
If the HEA connection is needed, verify that the cable is
connected and the switch is powered on. After Explanation: ISDN call in rejected.
repairing the problem, verify that the connection has Failing Item:
been restored.
v UG3LB
A6xx69DD
A6xx7002
Explanation: The Host Ethernet Adapter (HEA)
Explanation: Lines not selected.
connection to the Ethernet switch has been restored.
Failing Item:
Response: System log entry only, no service action
required. v UG3LB
A6xx69DE A6xx7003
Explanation: Host Ethernet Adapter (HEA) Media Explanation: Network interfaces not selected.
Interface Adapter Failure. Failing Item:
Response: Firmware detected a failure in the HEA v UG3LB
Media Interface Adapter.
v HEA Explanation: TCP/IP informational error.
v AJDG301
Response: This reference code is logged when the
TCP/IP Attribute Log Protocol Errors is set, and the
TCP/IP System LIC silently discards an in bound

A6xx7055 • A6xx720A
datagram. Silently discard is defined to mean discard v UPLF6

the received datagram without reporting an error to the v AJDG301
originating host device. Examples of such datagrams
are those with checksums or destination addresses
which are not valid. A6xx7102
This reference code is for information only. Normally Explanation: APPN CP-CP session ended.
no action should be taken as a result of this reference
code. It is generated in order to assist with remote A6xx7201
device or TCP/IP network problem determination.
Explanation: A utility failure occurred.
A6xx7055 Response: This reference code is for information only.

Explanation: Statistics were logged, no service action utility failure.
required.
Response: This reference code is logged for A6xx7202
information only.
Explanation: Utility power restored.
A6xx7100 Response: This reference code is for information only.

The Uninterruptible Power System (UPS) is reporting
Explanation: APPN session initiation attempt has that utility power has been restored.
timed out.
Response: This reference code is used to indicate that A6xx7203
LIC timed out on a request to initiate a session.
Explanation: A battery low condition was detected.
code. If this indicates a software problem, the user Response: This reference code is for information only.
should dial IBM Software Support for assistance. The Uninterruptible Power System (UPS) is reporting a
battery low condition.
exists and what the corrective actions should be. A6xx7204
Failing Item: Explanation: Uninterruptible Power System reported a

v AJDG301 bypass active.
v UPLF3 Response: This reference code is for information only.
v UPLF1 The Uninterruptible Power System (UPS) is reporting a
bypass is active.
v UPLF2
A6xx7205
A6xx7101
Explanation: Battery low condition was reset.
Explanation: APPN session initiation attempt has
failed. Response: This reference code is for information only.
Response: This reference code is used to indicate that reporting a battery low condition.
LIC attempted to satisfy a session initiation request, but
some failure condition was detected by LIC. The failure
condition could be a configuration or operational A6xx7206
problem in the network.
Explanation: UPS reported bypass no longer active.
should dial IBM Software Support for assistance.
reporting a bypass active condition.
A6xx720A
exists and what the corrective actions should be.
Explanation: Battery Power Unit replacement dates do
Failing Item:
not match.
v UPLF4
Response: The replacement dates for one of the
v UPLF5
Battery Power Units do not match. Run "Display

A6xx7703 • A6xx8007
Hardware Configuration" and verify that the dates

A6xx8002
match the labels on the batteries.
Explanation: Maximum number of redundant
connections exceeded.
A6xx7703
Response: An attempt to activate a connection from
another I/O adapter to a storage subsystem disk unit
exception.
failed because the maximum number of connections are
Response: Storage Management detected a DASD already active for this disk unit. No action required.
datacheck condition and the defective sector was
reallocated.
A6xx8003
Perform a system IPL to restart the system.
connection was restored.
A6xx7704
Explanation: General failure detected by HRI
component.
A6xx8004
Failing Item:
v AJDG301 connection failed.
Response: Could not read configuration information
A6xx7777 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
with, and fix them.
Response: A hardware resource is missing. The
resource reported in to the system on a previous IPL,
but has not reported in on the current IPL. This could A6xx8005
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
external storage subsystem disk unit failed.
resource is powered back on, it will no longer be
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 Look for other errors in the Service Action Log, or
drive. The service representative should use the serviceable event view you are working with, and fix
Hardware service manager to remove the entry for them.
this resource.
3. The resource may not have reported in on this IPL
A6xx8006
because it is failing. Perform problem analysis to
determine why the resource is failing. Explanation: High performance connection failed.
A6xx8000 external storage subsystem disk unit failed.
Explanation: A storage subsystem disk unit There is still one more external storage subsystem disk
connection failed. unit connection, but performance might be degraded.
Response: Look for other errors in the Service Action Look for other errors in the Service Action Log, or
Log (SAL), or serviceable event view you are working serviceable event view you are working with, and fix
with, and fix them. them.
A6xx8001 A6xx8007
Explanation: A storage subsystem disk unit Explanation: High performance connection was
connection failed. restored.
Response: Look for other errors in the Service Action Response: A high performance connection to an
Log, or serviceable event view you are working with, external storage subsystem disk unit was restored.
and fix them.
Performance is no longer degraded.

A6xxB700 • A6xxFDC5
No action required.
A6xxCFFD
Explanation: Optical drive failure.
A6xxB700
Failing Item:
Explanation: A platform firmware error log was
signalled to LIC but could not be retrieved from v OPTLDRV
platform firmware. LIC created this event in the PAL
with SRC B600B700 to log the problem. A6xxCFFF
Problem determination: Contact your hardware Explanation: Media determined to be bad in Optical
service provider. This is a platform firmware problem. library.
Failing Item:
v NEXTLVL A6xxF103
Explanation: Main storage dump must be copied for
A6xxCF00 service.
Explanation: Permanent error on removable media Failing Item:
device. v LICIP01
Response: A type D IPL terminated because of a
removable media Load Source device failure. If the A6xxF104
removable media Load Source is an external device,
check the cables. If that does not correct the problem, Explanation: LPAR service function directed a Main
replace the device. If the removable media Load Source Storage Dump.
is an internal device, replace the device. If the Response: The Hypervisor terminated a partition with
removable media Load Source is a virtual device, an unresponsive Operating System. A Main Store
ensure it is set up correctly. Dump must be done for service. Call your next level of
Failing Item: support when the dump is complete.
v LICIP01
A6xxCF01
Explanation: Unsupported removable media device A6xxF105
configuration. Explanation: Licensed Internal Code detected error.
Problem determination: A type D IPL terminated Failing Item:
because of an unsupported removable media device
configuration. Retry the D-IPL with a different v NEXTLVL
removable media device.
Failing Item: A6xxFDC0
v SVCDOCS Explanation: LIC program reported informational

error.
A6xxCFFC Response: This reference code is logged for
information only. No action required.
Explanation: Optical library device condition not
expected.
A6xxFDC5
Response: The optical disk drive addressing within
the optical library is incorrect. This error is likely to be Explanation: LIC program failed and data was
the result of faulty cabling or switch setting following captured.
service to an optical library.
Response: This reference code indicates first failure
Contact your hardware service provider. data capture (FFDC) data was collected for a problem
reported by licensed internal code.
Failing Item:
v OPTLCBL The user should dial IBM Software Support for
assistance.
v DRVSWCH
Failing Item:
v UG3AS

A7001150 • A7003003

An A7xx reference code indicates that an event or error was detected and logged by platform firmware.
To resolve an A7xx 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.
Response: The platform encountered a service
A7001150
processor event indicating that the power status has
Explanation: System log entry only, no service action changed. Note that this is A7xx only.
required.
Response: No action needed unless a serviceable A7001730
event was logged. If a serviceable event was logged,
Explanation: Platform LIC detected an error.
resolve that error.
Response: The VPD for the system is not what was
expected at IPL.
A7001151
When word 9 is 00180003, a redundant VPD chip
exists, and the system will continue to run. Replace the
required.
VPD card at your next scheduled maintenance. When
Response: No action needed unless a serviceable word 9 is not 00180003 replace the VPD card
event was logged. If a serviceable event was logged, immediately.
resolve that error.
Work with the FRU list in the serviceable event view, if
there is one. Otherwise, use the FRU list documented
A7001152 here to determine the parts to exchange.
Explanation: Platform firmware detected a timeout Failing Item:
condition. v CAPACTY
Response: A reset/reload of the service processor has
cleared the timeout condition. A700173A
If a service processor dump exists, it should be Explanation: A VPD collection overflow occurred.
collected for IBM Service.
Response: Look for and resolve other errors in the
Failing Item: serviceable event view. If that does not resolve the
v NEXTLVL problem, check for firmware updates and install them,
if available. If that does not resolve the problem,
A7001160
Failing Item:
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. A700173C
The platform encountered an error communicating with Explanation: Generic Asset Protection Event. No
the service processor. The platform code attempts a service action is required.
graceful shutdown of partitions and powers off the
server after a certain time, or when the last partition A7003000
indicates shutdown, whichever comes first.
Explanation: User-initiated PHYP-generated
Failing Item: SYSDUMP.
v LICCODE
v SVCPROC
v PSI_LNK
A7003003
Explanation: User-initiated PHYP-content RSCDUMP.
A7001161
required.

A7004091 • A7004712
A7004091 A7004704
Explanation: User intervention required. Explanation: Platform LIC detected an error.
Response: The system power on has reached a Response: The Capacity on Demand function is no
standby state. The firmware does not have partition longer available. If Capacity on Demand functions are
configuration information. required, look for and correct errors with SRCs of the
form B1xxxxxx in the Serviceable Event View. If that
Use the HMC OR SDMC to activate one or more
does not correct the problem, or no errors were found,
partitions to change the system from a standby state to
an operating state. If the HMC or SDMC does not
manage the server, perform Restoring your server to Failing Item:
factory settings. v SVCDOCS
Failing Item:
v SVCDOCS A7004705
Explanation: Platform LIC failure.
A7004700
Response: A problem occurred when initializing,
Explanation: Platform LIC detected an error. reading, or using system VPD. The Capacity on
Demand function is not available. If Capacity on
Response: A problem occurred when initializing,
Demand function is required, re-IPL the system. If that
reading, or using system VPD.
does not correct the problem, contact your next level of
Capacity on Demand is not available because the stored support.
activation code is not valid. Contact your next level of
Failing Item:
support to verify your activation code. If the activation
code is valid, replace the VPD card. v SVCDOCS
Failing Item:
A7004710
v SVCDOCS
v CAPACTY Explanation: Platform LIC detected an error.
Response: A communications problem with the
A7004701 service processor occurred while initiating Capacity on
Demand. The Capacity on Demand function is not
Explanation: Platform LIC detected an error. available.
Response: A problem occurred when initializing, If Capacity on Demand function is required, look for
reading, or using system VPD. The IPL failed. errors with SRCs of the form B1xxxxxx or B7xx69xx in
Work with the FRU list in the serviceable event view if the Serviceable Event View. Work those errors. If that
there is one, otherwise use the FRU list documented does not correct the problem, proceed with the failing
here to determine the parts to exchange. items listed in the serviceable event view for this SRC.
v CAPACTY v SVCDOCS
v CAPACTY
A7004703
A7004712
Explanation: Platform LIC failure.
Explanation: Platform LIC detected the VPD card is
Response: A problem occurred when initializing, missing.
reading, or using system VPD. The Capacity on
Demand function is not available. If Capacity on Response: A problem occurred when initializing,
Demand function is required, re-IPL the system. If that reading, or using system VPD.
does not correct the problem, contact your next level of
Work with the FRU list in the serviceable event view if
support.
there is one, otherwise use the FRU list documented
Failing Item: here to determine the parts to exchange.
v LICCODE Failing Item:
v CAPACTY

A7004713 • A7004736
Failing Item:
A7004713
v SVCDOCS
Response: The VPD card has been exchanged with a A7004730
not valid card. Reinstall the original VPD card in the
system. Explanation: Platform LIC detected an error.
Failing Item: Response: A problem occurred when configuring the

logical partitions on the system. More resources were
v SVCDOCS
allocated than there are available for use. Either obtain
more capacity by obtaining new activation codes or
A7004714 allocate fewer resources in the LPAR configuration.
Explanation: Platform LIC has detected a new VPD Failing Item:
card. v SVCDOCS
Response: The new VPD card requires new activation v LPARCFG
codes. Enter the new activation codes.
A7004731
A7004715
Response: The system has been running with full
Response: A problem occurred when initializing, Capacity on Demand resources activated. In one hour,
reading, or using system VPD during concurrent the system will terminate and unlicensed resources will
maintenance. no longer be available. To prevent the system from
terminating, enter an activation code of all zeroes. Then
Look for errors with SRCs of the form B1xxxxxx in the
obtain the proper activation codes for the resources
Serviceable Event View. Work those errors first. If that
being used or allocate fewer resources in the LPAR
does not correct the problem, replace the VPD card.
configuration.
Work with the FRU list in the serviceable event view if
Failing Item:
there is one, otherwise use the FRU list documented
here to determine the parts to exchange. v SVCDOCS
Failing Item:
A7004733
v SVCDOCS
v CAPACTY Explanation: Platform LIC failure.
Response: The Capacity on Demand function is not
A7004716 available. If Capacity on Demand function is required,
re-IPL the system. If that does not correct the problem,
Explanation: User intervention required. contact your next level of support.
Response: The Capacity on Demand activation code
recovery period has been started. Either obtain more A7004735
capacity by obtaining new activation codes or allocate
fewer resources in the LPAR configuration. Explanation: Use of Processors for General Purpose
work has exceeded number of licensed General
Failing Item: Purpose Processors.
v SVCDOCS
v LPARCFG A7004736
Explanation: Use of processors for general purpose
A7004721 work has exceeded number of licensed general purpose
Explanation: The World Wide Port Name (WWPN) processors, for long enough that the server is calling in
Prefix is not valid. to IBM to report this issue.
Response: Contact your hardware service provider to Failing Item:

obtain a valid World-Wide Port Name (WWPN). Once v LNUXOVR
you have obtained a valid WWPN value, go to ASM
and select: System_Configuration->
Program_Vital_Product_Data-> System_Keywords. On
the System_Keyword menu, enter the value for the
'WN' keyword.

A7004739 • A7004761
A7004739 A7004748
Explanation: The server was operating with Power Explanation: User intervention required.
Enterprise Pool resources prior to this Initial Program
Response: One hour remains until the Utility Capacity
Load (IPL). During this IPL, the Management Console
on Demand enablement expires. In order to reactivate
did not give the server the same amount of Power
temporary resources, a new Utility Capacity on
Enterprise Pool resources.
Demand enablement code is required.
Failing Item:
A7004740
v SVCDOCS
Response: An incorrect activation code has been A7004749
detected. Resources associated with this activation code
have been disabled. Enter a valid activation code. Explanation: User intervention required.
Response: One hour remains until the Trial Customer
A7004741 on Demand activation expires. Obtain a permanent
activation code or remove all temporary resources from
Explanation: Platform LIC detected an error. partitions before the request expires.
Response: The number of allowable attempts to enter Failing Item:
a valid activation code has been exceeded. Further
v SVCDOCS
attempts to enter an activation code will be temporarily
blocked. Wait for one hour and then enter a valid
activation code. A700474A
Explanation: System has Active Memory Mirroring
A7004742 (AMM) ON, but is not licensed for AMM use.
Explanation: Generally represents a temporary Problem determination: The HMC interface has been
communications failure between Server firmware and used to set AMM to "ON" for the system. However, at
the VPD Card. IPL time, the system does not have a valid license for
AMM. The customer needs to contact IBM or a Partner
Response: A communications session between the
Sales representative to purchase and enter an
server's firmware and the VPD Card in the FSP could
Activation Code for this feature. If this is not possible,
not be established or was interrupted.
then turn off the system; use the HMC interface to turn
An isolated occurrence of this type of error can safely AMM "OFF"; and re-IPL.
be ignored. However if these errors become fairly
Failing Item:
frequent, are clustered together, or are accompanied by
other related (A70047xx) errors that they would require v SVCDOCS
closer scrutiny to determine if a serviceable problem
exists. A7004750
Failing Item: Explanation: A Capacity on Demand change has been
v SVCDOCS detected.
v CAPACTY Response: Utility Capacity on Demand resources have
been activated.
A7004747
Explanation: User intervention required. A7004760
Response: One hour remains until the On/Off Explanation: The server's update access key is
Capacity on Demand request expires. Permanently approaching expiration.
activate the temporary Capacity on Demand resources,
enter a new On/Off Capacity on Demand request for A7004761
the temporary resources, or remove all temporary
resources from partitions before the request expires. Explanation: The server's update access key has
expired.
Failing Item:
v FMWREXP

A7004762 • A7013003
A7004762 A70047FF
Explanation: The activation code for the server's Explanation: System log entry only, no service action
update access key could not be found. The system required.
cannot start without an activation code.
Response: The Capacity on Demand History Log has
Failing Item: been written to the error log. No service action is
v FMWREXP required.
A7004788 A700C2AC
Explanation: System log entry only, no service action Explanation: System log entry only, no service action
required. required.
Response: The data obtained from the system is not Response: The Capacity on Demand License
what was expected. The IPL will continue. Should other acceptance has completed.
errors occur, contact your next level of support. No corrective action is required.
Failing Item:
A70047C1
v SVCDOCS
Explanation: Capacity on Demand data mismatch.
Response: The data obtained from the system is not A7013003
what was expected. The system will perform a slow
Explanation: Partition-initiated PHYP-content
IPL in order to obtain the correct data. If other errors
RSCDUMP.
occur, contact your next level of support.
A70047CB
Explanation: Fast system IPL changed to slow system
IPL.
Response: The data obtained from the system is not
what was expected. The system will perform a slow
IPL in order to obtain the correct data. If other errors
occur, contact your next level of support.
A70047CD
Response: The server detected a not valid Capacity
On Demand activation and terminated the system. The
allocated resources for the system might exceed those
that are available for use.
Failing Item:
v SVCDOCS
A70047DD
Explanation: A dump of the Capacity On Demand
data has been requested and is contained within this
platform event log.
Response: No recovery action is required. This
platform event log should be collected by service.
Failing Item:
v NEXTLVL

AA00E158 • AA060011
(AAxx) Reference codes

Partition firmware posts AAxx system reference (attention) codes, which offer information about the next
target state for the platform firmware. These codes might also indicate that you need to perform an
action, such as opening a firmware console or checking serial connections.
Note: Click the failing item in the FRU list only when you experience a hang condition on an attention
code. For example, a hang condition occurs when your server performs a requested action but the SRC in
the control panel display does not change for several minutes and the partition firmware appears to be
hung.
AA00E158 AA060007
Explanation: Waiting for virtual terminal (VTERM) to Explanation: A keyboard was not found
be opened on the HMC.
AA06000B
AA00E159
Explanation: The system or partition was not able to
Explanation: Waiting for serial connection to the find an operating system on any of the devices in the
service processor to be established boot list.
AA00E175 AA06000C
Explanation: The I/O configuration exceeds the Explanation: The media specified in a device in the
recommended size. Some operating systems might bootlist was not bootable
crash when using this configuration.
Failing Item: AA06000D
v FWFLASH Explanation: The media in the device in the bootlist
not found under the I/O adapter specified by the boot
AA00E1A8 list.
Explanation: The system is booting to the open

firmware prompt AA06000E
Failing Item: Explanation: The adapter specified in the boot list is

not present or not functioning.
v FWFLASH
AA060010
AA00E1A9
Explanation: The FAT filesystem on the bootdisk is
Explanation: The system is booting to the SMS menus
configured in a way that may cause a boot failure.
Failing Item:
v FWFLASH AA060011
Explanation: The firmware did not find the operating
AA00E1B0 system image and is was unable to detect at least one
Explanation: Waiting for the user to select language hard disk in the boot list. Firmware is now retrying the
and keyboard. entries in the boot list. This often occurs when the boot
disk enclosure is not yet fully initialized or if the boot
disk belongs to a server partition.
AA00E1B1
Problem determination: This error might occur before
Explanation: Waiting for the user to accept or decline the initialization of an enclosure that contains the boot
the license agreement. disk is complete or when the boot disk belongs to
another partition.
AA00E1F3 If this problem persists, do the following:
Explanation: Admin access password prompt 1. Verify that the boot disk belongs to the partition
that is being booted.
Failing Item:
2. Verify that the boot list in the SMS menus is correct.
v FWPWD

AA060012 • AA260005
AA060012 AA260003
Explanation: Firmware retry of bootlist exceeded the Explanation: The system is waiting for the system
time limit of one hour. This often occurs when partition unique ID number to be entered.
is left for a retry to boot from a non-bootable device in
Response: Enter the system unique ID number at the
the device list and the retry exceeds the time limit of
prompt.
one hour.
AA260004
AA130013
Explanation: The system is waiting for the worldwide
Explanation: Bootable media is missing from a
port number to be entered.
USB-attached CD-ROM.
Response: Enter the worldwide port number at the
prompt.
AA130014
Explanation: The media in the USB CD-ROM drive
AA260005
has been changed.
Explanation: The system is waiting for the brand
number to be entered.
AA170210
Response: Enter the brand number at the prompt.
Explanation: Setenv/$setenv parameter error - the
name contains a null character.
Failing Item:
v FWFLASH
AA170211
Explanation: Setenv/$Setenv parameter error - value
contains a null character
Failing Item:
v FWFLASH
AA170212
Explanation: Setenv/$Setenv parameter error: name is
null or too long. The name length is limited to 31
characters.
Failing Item:
v FWFLASH
AA190001
Explanation: The server firmware function to get and
set the time-of-day reported an error.
AA260002
Explanation: The system is waiting for the serial
number to be entered.
Response: Enter the serial number of the system at
the prompt

Notices
This information was developed for products and services offered in the US.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program,
or service that does not infringe any IBM intellectual property right may be used instead. However, it is
the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or
service.
IBM 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:
IBM Director of Licensing

IBM Corporation
North Castle Drive, MD-NC119
Armonk, NY 10504-1785
US
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "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 jurisdictions 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.
IBM 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 non-IBM websites 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 IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you provide in any way it believes appropriate without
incurring any obligation to you.
The performance data and client examples cited are presented for illustrative purposes only. Actual
performance results may vary depending on specific configurations and operating conditions.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,
and represent goals and objectives only.
© Copyright IBM Corp. 2018 1105

All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without
notice. Dealer prices may vary.
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 actual people or business enterprises 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 IBM.
IBM has prepared this information for use with the specific machines indicated. IBM makes no
representations that it is suitable for any other purpose.
IBM'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 IBM'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.
Accessibility features for IBM Power Systems servers

Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to
use information technology content successfully.
Overview
The IBM Power Systems servers include the following major accessibility features:
v Keyboard-only operation
v Operations that use a screen reader
The IBM Power Systems servers use the latest W3C Standard, WAI-ARIA 1.0 (www.w3.org/TR/wai-aria/
), to ensure compliance with US Section 508 (www.access-board.gov/guidelines-and-standards/
communications-and-it/about-the-section-508-standards/section-508-standards) and Web Content
Accessibility Guidelines (WCAG) 2.0 (www.w3.org/TR/WCAG20/). To take advantage of accessibility
features, use the latest release of your screen reader and the latest web browser that is supported by the
IBM Power Systems servers.
The IBM Power Systems servers online product documentation in IBM Knowledge Center is enabled for
accessibility. The accessibility features of IBM Knowledge Center are described in the Accessibility section
of the IBM Knowledge Center help (www.ibm.com/support/knowledgecenter/doc/
kc_help.html#accessibility).

Keyboard navigation
This product uses standard navigation keys.
Interface information
The IBM Power Systems servers user interfaces do not have content that flashes 2 - 55 times per second.
The IBM Power Systems servers web user interface relies on cascading style sheets to render content
properly and to provide a usable experience. The application provides an equivalent way for low-vision
users to use system display settings, including high-contrast mode. You can control font size by using the
device or web browser settings.
The IBM Power Systems servers web user interface includes WAI-ARIA navigational landmarks that you
can use to quickly navigate to functional areas in the application.
Vendor software
The IBM Power Systems servers include certain vendor software that is not covered under the IBM
license agreement. IBM makes no representation about the accessibility features of these products. Contact
the vendor for accessibility information about its products.
Related accessibility information
In addition to standard IBM help desk and support websites, IBM has a TTY telephone service for use by
deaf or hard of hearing customers to access sales and support services:
TTY service
800-IBM-3383 (800-426-3383)
(within North America)
For more information about the commitment that IBM has to accessibility, see IBM Accessibility
(www.ibm.com/able).
Privacy policy considerations

IBM Software products, including software as a service solutions, (“Software Offerings”) may use cookies
or other technologies to collect product usage information, to help improve the end user experience, to
tailor interactions with the end user, or for other purposes. In many cases no personally identifiable
information is collected by the Software Offerings. Some of our Software Offerings can help enable you to
collect personally identifiable information. If this Software Offering uses cookies to collect personally
identifiable information, specific information about this offering’s use of cookies is set forth below.
This Software Offering does not use cookies or other technologies to collect personally identifiable
information.
If the configurations deployed for this Software Offering provide you as the customer the ability to collect
personally identifiable information from end users via cookies and other technologies, you should seek
your own legal advice about any laws applicable to such data collection, including any requirements for
notice and consent.
For more information about the use of various technologies, including cookies, for these purposes, see
IBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement at
http://www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and Other
Technologies” and the “IBM Software Products and Software-as-a-Service Privacy Statement” at
http://www.ibm.com/software/info/product-privacy.
Notices 1107
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.
Class A Notices
The following Class A statements apply to the IBM servers that contain the POWER9 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
CAN ICES-3 (A)/NMB-3(A)
European Community Compliance Statement
This product is in conformity with the protection requirements of EU Council Directive 2014/30/EU 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.

European Community contact:
IBM Deutschland GmbH
Technical Regulations, Abteilung M456
IBM-Allee 1, 71139 Ehningen, Germany
Tel: +49 800 225 5426
email: [email protected]
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.
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.
Japan Electronics and Information Technology Industries Association Statement
This statement explains the Japan JIS C 61000-3-2 product wattage compliance.
This statement explains the Japan Electronics and Information Technology Industries Association (JEITA)
statement for products less than or equal to 20 A per phase.
This statement explains the JEITA statement for products greater than 20 A, single phase.
Notices 1109
This statement explains the JEITA statement for products greater than 20 A per phase, three-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.
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 2014/30/EU zur Angleichung der
Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaatenund hält die
Grenzwerte der EN 55022 / EN 55032 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.
EN 55022 / EN 55032 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 2014/30/EU in der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von
Geräten (EMVG) (bzw. der EMC Richtlinie 2014/30/EU) 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
Notices 1111
Armonk, New York 10504
Tel: 914-499-1900
Der verantwortliche Ansprechpartner des Herstellers in der EU ist:

Technical Relations Europe, Abteilung M456
Tel: +49 (0) 800 225 5426
Generelle Informationen:
Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022 / EN 55032 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.
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
CAN ICES-3 (B)/NMB-3(B)
European Community Compliance Statement
This product is in conformity with the protection requirements of EU Council Directive 2014/30/EU 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.
European Community contact:

Technical Regulations, Abteilung M456
Tel: +49 800 225 5426
VCCI Statement - Japan
Japan Electronics and Information Technology Industries Association Statement

This statement explains the Japan JIS C 61000-3-2 product wattage compliance.
This statement explains the Japan Electronics and Information Technology Industries Association (JEITA)
statement for products less than or equal to 20 A per phase.
This statement explains the JEITA statement for products greater than 20 A, single phase.
Notices 1113
This statement explains the JEITA statement for products greater than 20 A per phase, three-phase.
IBM Taiwan Contact Information
Germany Compliance Statement
Deutschsprachiger EU Hinweis: Hinweis für Geräte der Klasse B EU-Richtlinie zur

Elektromagnetischen Verträglichkeit
Dieses Produkt entspricht den Schutzanforderungen der EU-Richtlinie 2014/30/EU zur Angleichung der
Rechtsvorschriften über die elektromagnetische Verträglichkeit in den EU-Mitgliedsstaatenund hält die
Grenzwerte der EN 55022/ EN 55032 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 2014/30/EU in der Bundesrepublik Deutschland.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von
Geräten (EMVG) (bzw. der EMC Richtlinie 2014/30/EU) 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:

Technical Relations Europe, Abteilung M456
Tel: +49 (0) 800 225 5426
Generelle Informationen:
Das Gerät erfüllt die Schutzanforderungen nach EN 55024 und EN 55022/ EN 55032 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.
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.
Notices 1115
IBM®

P9eai src1

Uploaded by

Copyright:

Available Formats

P9eai src1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

P9eai src1

Uploaded by

Copyright:

Available Formats

Power Systems

System reference codes (1xxx - Axxx)

System reference codes (1xxx - Axxx)

System reference codes (1xxx - Axxx) overview . . . . . . . . . . . . . . . . . . 1

© Copyright IBM Corp. 2018 iii

iv Power Systems: System reference codes (1xxx - Axxx)

vi Power Systems: System reference codes (1xxx - Axxx)

viii Power Systems: System reference codes (1xxx - Axxx)

World Trade safety information

German safety information

Laser safety information

IBM servers may be installed inside or outside of an IT equipment rack.

© Copyright IBM Corp. 2018 ix

(R001 part 1 of 2):

x Power Systems: System reference codes (1xxx - Axxx)

xii Power Systems: System reference codes (1xxx - Axxx)

Safety notices xiii

CAUTION: A hot surface nearby. (L007)

xiv Power Systems: System reference codes (1xxx - Axxx)

Power and cabling information for NEBS (Network Equipment-Building System)

xvi Power Systems: System reference codes (1xxx - Axxx)

Safety notices xvii

Block replacement of FRUs

(1000) Reference codes

© Copyright IBM Corp. 2018 1

experienced an AC Power Loss external to the system

2 Power Systems: System reference codes (1xxx - Axxx)

10001511 Response: The FRU callouts are calculated at the time

Explanation: Power Supply missing (PS1) Failing Item:

System reference codes (1xxx - Axxx) overview 3

4 Power Systems: System reference codes (1xxx - Axxx)

System reference codes (1xxx - Axxx) overview 5

6 Power Systems: System reference codes (1xxx - Axxx)

System reference codes (1xxx - Axxx) overview 7

8 Power Systems: System reference codes (1xxx - Axxx)

System reference codes (1xxx - Axxx) overview 9

10 Power Systems: System reference codes (1xxx - Axxx)

System reference codes (1xxx - Axxx) overview 11

12 Power Systems: System reference codes (1xxx - Axxx)

callouts detailed with the SRC to determine service

System reference codes (1xxx - Axxx) overview 13

14 Power Systems: System reference codes (1xxx - Axxx)

callouts detailed with the SRC to determine service

System reference codes (1xxx - Axxx) overview 15

10008403 Explanation: Midplane redundant VPD has ECC

16 Power Systems: System reference codes (1xxx - Axxx)

System reference codes (1xxx - Axxx) overview 17

18 Power Systems: System reference codes (1xxx - Axxx)

System reference codes (1xxx - Axxx) overview 19

a unit address of D or E or had a frame address of 00.

20 Power Systems: System reference codes (1xxx - Axxx)

v A QSX command was not addressed to RRRR=0 ,

System reference codes (1xxx - Axxx) overview 21

22 Power Systems: System reference codes (1xxx - Axxx)

Response: The Licensed Internal Code download to

System reference codes (1xxx - Axxx) overview 23

maintenance operation, it is informational only and can

24 Power Systems: System reference codes (1xxx - Axxx)

Response: There are more nodes in the network than