You are on page 1of 494

Hardware Information

Reference codes

REFERENCE 86 A1 03EW 00

ESCALA POWER5

BLANK

ESCALA POWER5

Hardware Information
Reference codes

Hardware
July 2006
BULL CEDOC 357 AVENUE PATTON B.P.20845 49008 ANGERS CEDEX 01 FRANCE

REFERENCE 86 A1 03EW 00

The following copyright notice protects this book under Copyright laws which prohibit such actions as, but not limited to, copying, distributing, modifying, and making derivative works.

Copyright

Bull SAS 1992, 2006

Printed in France Suggestions and criticisms concerning the form, content, and presentation of this book are invited. A form is provided at the end of this book for this purpose. To order additional copies of this book or other Bull Technical Publications, you are invited to use the Ordering Form also provided at the end of this book.

Trademarks and Acknowledgements
We acknowledge the right of proprietors of trademarks mentioned in this book. AIX® is a registered trademark of International Business Machines Corporation, and is being used under licence. UNIX® is a registered trademark in the United States of America and other countries licensed exclusively through the Open Group. Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries

The information in this document is subject to change without notice. Bull will not be liable for errors contained herein, or for incidental or consequential damages in connection with the use of this material.

Reference codes

Table of Contents
Reference codes................................................................................................................................................1 List of system reference codes...............................................................................................................1 (1xxx) System power control network (SPCN) reference codes......................................................2 Using system reference codes.....................................................................................................266 Block replacement of FRUs.........................................................................................................267 List of service request numbers...................................................................................................267 Using service request numbers ....................................................................................................449 List of progress codes..................................................................................................................450 Using progress codes..................................................................................................................481 Reference codes that begin with a number sign (#) .....................................................................482

i

Reference codes

ii

Reference codes
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. If you were not directed to this page by another procedure, begin the troubleshooting process by using the following link: Start of call procedure 1. Does the reference code contain a hyphen (-), for example, 111-459? ♦ Yes: See List of service request numbers. ♦ No: Continue with the next step. 2. Does the reference code contain exactly 5 characters? ♦ Yes: See List of service request numbers. ♦ No: Continue with the next step. 3. Is the first character of the reference code a number sign (#)? ♦ Yes: See Reference codes that begin with a number sign (#). ♦ No: Continue with the next step. 4. Is the reference code a 3-digit hexadecimal number? ♦ Yes: Prepend 101 and a hyphen (-) to the number, then use that number to refer to the List of service request numbers. ♦ No: Continue with the next step. 5. Is the reference code a 4-digit hexadecimal number that begins with 0, 2, BC, D, or E? ♦ Yes: See Using progress codes. ♦ No: Continue with the next step. 6. Is the reference code an alphanumeric string that begins with HSC or a 6-digit number that begins with 0 and does not contain a hyphen (-)? ♦ Yes: See HMC error codes. ♦ No: See List of system reference codes. If you need more information about reference codes, such as reference code formats and how to use reference code information, see the following pages: Using service request numbers Using progress codes Using system reference codes

List of system reference codes
The system reference codes (SRCs) in this list represent reference code types and are organized by their first character, with numbers preceding letters. If you do not find the SRC that you are looking for in this list, ask your next level of support for assistance. For more information about SRCs, including details about using this list of SRCS, see Using system reference codes. Note: 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. 0 1 2 3 4 5 6 7 8 9 A B C D E F H #
Reference codes 1

Reference codes

1 1xxx 1400 1750 180A 2 2058 2746 2782 284B 20A8 2748 2787 287F 20Dx 2749 2793 2890 20EE 20FF 2102 2105 2107 220x 25Ax 25Cx 2602 2724 2742 2743 2744 2745 2750 2751 2757 2760 2761 2763 2765 2766 2767 2768 2771 2772 2778 2780 2803 2805 280D 280E 281x 2838 283C 283D 283F 2842 2843 2844 2847 2849 2892 28B9 28CB 28CC 28D2 28DB 28DF 2B2x

4 40xx 432x 4758 4764 4B20 5 506D 506E 5700 5701 5702 5703 5704 5706 5707 5708 5709 570B 571A 571B 571E 571F 573A 573B 573C 573D 573E 574F 57FF 6 6149 632x 6330 6331 6333 6336 6337 660x 671x 673x 6A59 A A1xx A2xx A7xx A9xx AAxx B B005 B006 B013 B015 B017 B026 B045 B1xx B2xx B3xx B7xx B9xx BAxx BBxx BCxx (For 4-digit codes that begin with BC, see List of progress codes.) BF67 BF75 BF77 C CBxx For all other codes that begin with C and for 4-digit codes that begin with a space character or a zero, see List of progress codes. D DAxx For codes that begin with D and for 4-digit codes that begin with a space character or a zero, see List of progress codes. E Exxx (For 4-digit codes that begin with E, see List of progress codes.) E2xx E3xx E302 E303 E332 E338 E355 E35A E35F E36C E3CA E3D4 E3F0 E4xx H For codes that begin with H, see HMC error codes. # For codes that begin with a number sign (#), see Reference codes that begin with a number sign (#).

(1xxx) System power control network (SPCN) reference codes

The system power control network (SPCN) detected a failure. 1. Look at the four rightmost characters of the SRC from Function 11. These characters are the unit reference code. 2. Find the unit reference code in the following table.
2 List of system reference codes

Reference codes

For details on the Failing Item column entries, see the SPCN Failing Items Detail table. Table 1. SPCN reference codes: Reference Code Description/Action Perform all actions before exchanging Failing Items 00A0 SPCN BATs in process No action required. This reference code is logged for information only. If this reference code is present for more than 1 minute, exchange the failing items. Download in process No action required. This reference code is logged for information only. Detected AC loss If system powers on normally or stays powered on after AC power failure, no replacement of parts may be needed. Service Processor Reset caused a system power off The system is running on the Battery Power Unit. No action required. This reference code is displayed for information only. Battery Power Unit test is in process. No action required. This reference code is displayed for information only. Thermal calibration in progress Remote EPO switch is OFF Detected AC loss Before replacing any parts, verify that the AC input voltage is correct. Power supply failure Power supply failure Power supply failure Detected AC loss Before replacing any parts, verify that the AC input voltage is correct. Power supply failure Power supply failure Power supply failure No Power Supplies Present The required power supplies are not installed, or if installed, defective. Power supply failure Detected AC loss Before replacing any parts, verify that the AC input voltage is correct. Power supply failure Power supply failure ACMODUL Failing Item TWRCARD

00AA 00AC

00AD 00BA

TWRCARD

00BC

00CA 00EF 1500 1501 1502 1503 1510 1511 1512 1513 to 1514 1516 1517 1520 1521 1522

PWRSPLY TWRCARD PWRSPLY TWRCARD PWRSPLY TWRCARD CBLALL PWRSPLY TWRCARD PWRSPLY TWRCARD PWRSPLY TWRCARD PWRSPLY TWRCARD CBLALL PWRSPLY TWRCARD PWRSPLY TWRCARD PWRSPLY TWRCARD PWRSPLY TWRCARD PWRSPLY TWRCARD PWRSPLY TWRCARD CBLALL
3

(1xxx) System power control network (SPCN) reference codes

Power supply failure PWRSPLY TWRCARD Detected AC loss PWRSPLY TWRCARD Before replacing any parts.5V bus PWR1904 TWRCARD FSP Card SS Fault CARDFLT OSC Card SS Fault CARDFLT Lightstrip SS Fault CARDFLT LITSTRP CABLEH MUX Card SS Fault CARDFLT IO Hub Card SS Fault CARDFLT (1xxx) System power control network (SPCN) reference codes .8/2.Reference codes 1523 to 1524 1526 1527 1530 1531 1532 1533 1611 1612 1613 1621 1622 1623 1631 1632 1633 1B01 1B02 1B03 1B04 1B05 1B06 1B0A 1B0F.3V bus PWR1900 TWRCARD Load fault on the -12V bus PWR1900 TWRCARD Load fault on the +1.5V bus PWR1904 TWRCARD Load Fault on the 1.8V bus PWR1904 TWRCARD Load fault on the +2. Power supply failure PWRSPLY TWRCARD Power supply failure PWRSPLY TWRCARD CBLALL Power supply failure PWRSPLY TWRCARD Regulator 1 Fault PWR1918 TWRCARD Regulator 1 Communication Fault PWR1918 TWRCARD Regulator 1 Domain Fault PWR1918 TWRCARD Regulator 2 Fault PWR1918 TWRCARD Regulator 2 Communication Fault PWR1918 TWRCARD Regulator 2 Domain Fault PWR1918 TWRCARD Regulator 3 Fault PWR1918 TWRCARD Regulator 3 Communication Fault PWR1918 TWRCARD Regulator 3 Domain Fault PWR1918 TWRCARD Load fault on the +12V bus PWR1900 TWRCARD Load fault on the +5V bus PWR1900 TWRCARD Load fault on the +3. defective.5V bus PWR1904 TWRCARD Load Fault on the +12V/-12v bus PWR1904 TWRCARD Load Fault on the +1. verify that the AC input voltage is correct.2V bus PWR1904 TWRCARD Load Fault on the +1. 1C02 1C04 1C06 1D00 to 1D01 1D02 to 1D03 1D04 to 1D05 1D10 1D11 to 1D18 4 Power supply failure No Power Supplies Present PWRSPLY TWRCARD PWRSPLY TWRCARD The required power supplies are not installed. or. if installed.

Reference codes 1D60 1D61 to 1D62 1D63 1F01 1F02 2600 to 2601 2602 2603 2605 to 2609 2612 2613 RIO/HSL Adapter Card Switch fault Removable Media Planar Switch fault RIO/HSL Adapter Card Switch fault TMS limit reached .log only SPCN trace information saved Power Good Fault Power Good Fault Power Good Fault Power Good Fault Optical Converter 5V Fault The SPCN detected a fault on the SPCN card optical converter 5V. Configuration Requires 200V Input Configuration now requires 200V AC power(both supplies need to be the same voltage). Regulator Fault Regulator Fault Regulator Fault Regulator Fault Regulator Fault I2C Bus Controller Communication fault I2C Bus 1 Communication fault I2C Bus 2 Communication fault I2C Bus 3 Communication fault I2C Bus 4 Communication fault I2C Bus 5 Communication fault I2C Bus 6 Communication fault I2C Bus Adapter Communication fault I2C Bus SPCN VPD Communication fault I2C Bus DASD Backplane 1 Communication fault I2C Bus DASD Backplane 2 Communication fault I2C Bus DASD Backplane 3 Communication fault I2C Bus Adapter Communication fault I2C Bus PCI Backplane Communication fault I2C Bus Panel Communication fault I2C Bus Fan Local Controller Communication fault SI_CARD TWRCARD DEVBPLN TWRCARD SI_CARD TWRCARD PGDPART PWR1918 TWRCARD PGDPART PWR1900 TWRCARD CBLALL TWRCARD CBLALL 2630 to 2632 2633 to 2635 2636 to 2637 2638 to 2639 2640 to 2642 3100 3101 3102 3103 3104 3105 3106 3109 310A to 310B 3110 3111 3112 3113 3114 3115 3116 PWR1918 TWRCARD SYSBKPL TWRCARD PWR1918 TWRCARD SYSBKPL PWR1918 TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD 5 (1xxx) System power control network (SPCN) reference codes .

Reference codes 3118 3120 3121 3122 to 3125 3200 3201 3202 3203 4201 4203 4212 4213 4221 4222 4225 4410 I2C Bus SPCN VPD Communication fault Voltage Adjust Failure I2C Bus 2 Communication fault I2C Bus SPCN VPD Communication fault MUX Hardware Failed Device select mux HW fail drawer1 Device select mux HW fail drawer 2 Device select mux HW fail drawer 3 Device select mux HW fail drawer 4 UPS Reported. 4414 Battery Charger Load fault 4415 4417 4600 to 4601 5000 to 5001 7110. I2CBUS TWRCARD SYSBKPL TWRCARD I2CBUS TWRCARD I2CBUS TWRCARD HMUX TWRCARD HMUX TWRCARD HMUX TWRCARD HMUX TWRCARD 4411 4412 Internal Battery Power Unit Charger Fault Internal Battery Power Unit Charger in the system has failed. Utility Failure On UPS Reported. 7120 7200 7201 7202 7203 Battery Power Unit missing Battery Charger Unit missing UPS Interface Failure FSP fail over failed due to configuration mismatch Power supply failure Thermal Sensor Fault Ambient temperature is out of range Ambient temperature is back in range Ambient temperature exceeded limit The system will shut down in 15 minutes. Internal Battery Power Unit Charger Fault Internal Battery Power Unit Charger in the system has failed. 4413 Internal Battery Power Unit Charger Fault Internal Battery Power Unit Charger in the system has failed. Battery Low On Config ID does not match HW BBU in wrong Location BBU Fault BBU Comm Fault BBU Expired Internal Battery Power Unit Fault Internal Battery Power Unit in the system has failed. PWR1917 BATRY BATRY BATRY TWRCARD CBLALL BATRY BATRY BATCHGR TWRCARD CBLALL BATCHGR TWRCARD CBLALL BATCHGR BATRY TWRCARD CBLALL BATRY BATCHGR TWRCARD CBLALL PWROC BATRY TWRCARD CBLALL BATRY TWRCARD CBLALL BATCHGR TWRCARD CBLALL UPSUNIT TWRCARD TWRCARD PWRSPLY TWRCARD AMBTEMP AMBTEMP AMBTEMP 6 (1xxx) System power control network (SPCN) reference codes .

Fan missing error A problem was detected with a Fan which can be caused by a Fan not being installed. Fan Fault The Fan is operating at the wrong speed. Install Fan if missing. Fan missing error A problem was detected with a Fan which can be caused by a Fan not being installed. Fan Fault The Fan is operating at the wrong speed. Fan Fault Fan missing error No VPD Found due to Invalid Bypass Unable to Collect VPD Processor Unit VPD Mismatch No Processor Installed SPCN Configuration mismatch SPCN Default Configuration loaded Invalid Processor VPD No Processor VPD Cable not connected Cable should not be present Secondary unit not present AMBTEMP AMBTMP1 AMBTMP2 PWRSPLY TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD AIRMOVR TWRCARD PWR1917 VPDPART TWRCARD VPDPART TWRCARD VPDPART TWRCARD IDPART TWRCARD IDPART TWRCARD VPDPART TWRCARD VPDPART TWRCARD IDPART TWRCARD IDPART TWRCARD 7620 7621 7630 7631 7640 7641 7650 7651 8400 8402 8404 to 8406 8409 840D 840E 8410 to 8417 8420 to 8427 8430 8431 8432 (1xxx) System power control network (SPCN) reference codes 7 . Fan Fault The Fan is operating at the wrong speed. Install Fan if missing. Install Fan if missing. replace if already installed. Fan missing error A problem was detected with a Fan which can be caused by a Fan not being installed. Power supply failure Fan Fault The Fan is operating at the wrong speed. Ambient temperature is out of range Ambient Temperature is above nominal for CPU performance.Reference codes 7205 7211 7212 7300 7610 7611 Ambient temperature exceeded limit The system will shut down in 20 seconds. Install Fan if missing. replace if already installed. Fan missing error A problem was detected with a Fan which can be caused by a Fan not being installed. replace if already installed. replace if already installed. Ambient temperature is back in range Ambient Temperature has returned to nominal.

AJDG301 TWRCARD 9016. A command from the system unit specified a unit address of D or E or had a frame address of 00. No action required. This reference code is logged for information only. no node books present to power on BPA Error collection failed BPC/HMC fault. A command to an SPCN node was rejected.3V fault External Netfinity Server Power Good fault Integrated Netfinity Adapter fault External Netfinity Server R485 Communication fault IO Power control changed to another system unit Received a bad return code Partition Firmware has detected a condition that may require attention. Addressed Unit not in frame. (1xxx) System power control network (SPCN) reference codes .Reference codes 8440 8450 to 8451 8455 to 8456 8460 8470 to 8477 8700 to 8701 8710 to 8711 8720 to 8721 8731 8732 8733 8734 8735 8740 to 8741 8910 8920 8930 8940 to 8943 8A00 9002 Invalid Dasd backplane SPCN Configuration mismatch Power Supply Missing All PWR nodes guarded Processor Unit VPD Mismatch BPC AC Loss DCA UART Communication Fault BPC ethernet Communication fault BPC critical fault. no present node books powered on BPC critical fault. A command has an invalid address mode. The address in the SPCN command does not match the secondary nodes assigned address. Address not valid. No BPC IP addresses BPC fault. Invalid Node Address. 9021 9022 8 Exchange the failing items in the system unit. IDPART TWRCARD PWR1915 PWR1918 TWRCARD PWRSPLY TWRCARD VPDPART TWRCARD PWR2402 DCA TWRCARD SYSBKPL CABLEH BPC TWRCARD CABLEH NEXTLVL CABLEH NEXTLVL CABLEH NEXTLVL CABLEH NEXTLVL BPC BPC ALTMANL TWRCARD TWRCARD ALTMANL TWRCARD TWRCARD CBLALL 9012 TWRCARD CBLALL 9013 Exchange the SPCN frame-to-frame cables to the failing frame. If this SRC persists contact next level of support. failed to reach standby External Netfinity Server 3. TWRCARD CBLALL 9014 Exchange the failing items for the SPCN node reporting the error. Check error log for other errors that may have been reported at the same time as this condition was reported. LIC command had a frame address that was not valid. ced cage id mismatch .cabling error BPC critical fault.

This reference code is logged for information only. Addressed Unit exists. Battery Power Unit is reporting a low charge. The transmission is attempted again. 9031 No action required. 9025 No action required. Battery Power Unit test was aborted. The code will be reloaded. 9029 No action required. The Licensed Internal Code in the primary node is not valid. This reference code is logged for error analysis only. rack to unit. This reference code is logged for error analysis only. This reference code is logged for information only. The battery power unit is not charged enough to run a test. This reference code is logged for error analysis only. 9023 No action required. 902C Exchange the failing items for the node reporting the failure. The battery power unit test was aborted. The addressed unit is in a frame that is powered off. This reference code is logged for error analysis only.Reference codes The addressed unit does not exist in the addressed frame. No action required. 9027 9028 No action required. SPCN Licensed Internal Code is not valid. The code will be reloaded. Battery Power Unit is defective. The frame detected a BCC error on a transmission from a secondary node to the frame. The addressed frame is not in the SPCN configuration table. (1xxx) System power control network (SPCN) reference codes 9 . This reference code is logged for information only. SPCN Licensed Internal Code not valid. 9032 No action required. This reference code is logged for information only. 9024 No action required. A secondary node detected a BCC error on a transmission from the frame. The Licensed Internal Code in one of the frames is not valid. 902D No action required. The transmission is attempted again. The Licensed Internal Code in one of the secondary nodes is not valid. This reference code is logged for information only. 9033 No action required. SPCN Communications Failure. The code will be reloaded. Frame-to-Frame Communications Failure The SPCN detected a BCC error on a transmission from another frame. This reference code is logged for error analysis only. 9026 No action required. SPCN VPD Damaged TWRCARD The VPD record in the EEPROM has bad data. This reference code is logged for information only. but the frame is powered off. unit to rack. SPCN Licensed Internal Code is not valid. SPCN Communications Failure. Addressed frame is not in SPCN configuration table. The transmission is attempted again.

The SPCN ROS and EEPROM LIC is not compatable. A secondary SPCN node did not respond to a command. Secondary SPCN node timeout. This reference code is logged for error analysis only. Undefined Status Code An SPCN node returned an unknown status code. QDS Packet Sequence Error The Packet Sequence number is wrong. A frame was dropped from the SPCN configuration. The operation was attempted again but was not successful. 9036 No action required. 903B No action required. This reference code is logged for error analysis only. but the wrong type of Licensed Internal Code was loaded. The LIC levels in the nodes ROS and EEPROM are not compatible. This reference code is logged for error analysis only. A frame was dropped from the SPCN configuration. Frame Timeout One or more frames did not respond to a command. Invalid Packet Length for data sent. The frame can also return this code if a secondary node returns more than 10 bytes to a PAS command. 9035 No action required. 9043 Exchange the SPCN node reported in the failure. EEPROM Failure TWRCARD The EEPROM in an SPCN node cannot be written successfully. TWRCARD 9046 9047 9048 Exchange the failing SPCN node. TWRCARD BACKPLN 90F0 Exchange the failing SPCN node. This reference code is logged for error analysis only. The command is attempted again. Download Failure The Licensed Internal Code download to an SPCN node was completed but was not successful. This is usually caused by a loss of ac power or a problem with the frame-to-frame cable. Invalid Load Type AJDG301 TWRCARD The down load was successful. The number of bytes sent or received does not match the number of bytes specified in the command. Unsupported Packet Size The receiving node detected a packet exceeding 70 bytes. 9041 9042 No action required. The download was stopped. QDS Block Sequence Error The Block Sequence number is wrong. This reference code is logged for error analysis only. TWRCARD TWRCARD TWRCARD AJDG301 9080 Exchange the failing items for the failing node. Exchange the failing items for the node reporting the fault. A frame was added to the SPCN configuration. The command was attempted again and failed. The download was stopped.Reference codes 9034 No action required. PWR1907 TWRCARD CBLALL 90F1 10 (1xxx) System power control network (SPCN) reference codes .

The reload failed because the code could not be found. The reload failed because the code could not be found.Reference codes 90F2 No action required. Frame SPCN node is reporting load damaged. The Licensed Internal Code for the primary SPCN node is damaged. This reference code is logged for information only. The battery power unit was not able to pass the capacity test. Load Damaged Timeout An SPCN node failed to enter the operational state. This reference code is logged for information only. 11 9115 (1xxx) System power control network (SPCN) reference codes . No action required. Secondary SPCN node is reporting load damaged. TWRCARD 9106 9107 9108 9109 Exchange the failing SPCN node. SPCN Command rejected by the Service Processor. The AROS part number field was not updated to the correct level after the system attempted to load new Licensed Internal Code. An SPCN microcode download is required. No action required. Download Initialize Timeout An SPCN node failed to enter the download state after an Initialize for Download command. SPCN is too large for VLIC. Assign Permanent Address command failure TWRCARD A node failed to perform an Assign Permanent Address command. TWRCARD 910A 910B 9110 9111 9112 BATRY AJDG301 TWRCARD 9113 TWRCARD 9114 The Licensed Internal Code for the secondary SPCN node is damaged. TWRCARD 9105 Exchange the failing SPCN node. Primary SPCN node is reporting load damaged. This reference code is logged for information only. TWRCARD 9104 Exchange the failing SPCN node. Download Completion Timeout An SPCN node failed to leave the download state. Slave disappeared A slave was dropped from the SPCN configuration. RIO Download Required Maximum number of retrys exceeded Battery Power Unit capacity test failed. A status change occured in one of the SPCN nodes. The SPCN failed to respond SVCPROC to a Licensed Internal Code command. This reference code is logged for error analysis only. The reload failed because the code could not be found. This is usually caused by a loss of ac power. No action required. There are more nodes in the network than VLIC can service. An SPCN LID was not found. (This is for a 24 inch rack) Slave reappeared VLIC-SPCN Timeout 90F3 9101 9102 9103 TWRCARD CTLPNL A Licensed Internal Code timeout occurred. TWRCARD The Licensed Internal Code for a SPCN node is damaged. Licensed Internal Code part number is not correct.

Reference codes The service processor rejected an SPCN command from the Licensed Internal Code.Control Panel interface failure. The SPCN to control panel interface is not working. 9116 9117 No action required. PHYP out of memory NVRAM Write Failed Too many racks attached Reduce the number of racks to maximum configuration on the system. Bad PCI Correlation Problem SPCN node not matched Bad Location Code Open SPCN loop resolved RIO download sent retry Goto ASMi to start a download manually All SPCN Downloads Complete RIO Download Complete Write VPD on next IPL Frame Address field not valid. The SPCN to control panel interface is now working.Control Panel interface is now working. The address in the SPCN command does not match the assigned address of the secondary node. SPCN . 9118 9119 911A 911B 911C 911D 911E 911F 9120 9131 9132 9133 9134 9135 9136 9137 9138 9139 913A 913B 91DD 91DE 91FB 9212 No action required. SPCN . A Licensed Internal Code command had a frame address that is not valid. SPCN CEC node code failure Two nodes have same VPD RIO Download Failure Temporary VPD written CEC not found Duplicate backplane VPD Invalid XM Return Code Node contains temporary VPD Bad PCI Correlation Problem PCI bus not matched PCI bus VPD error Check Error Log for B700 xxxx Reference Codes. Open SPCN Loop The manually started download was interrupted Needs to be Manually restarted. Invalid Address Mode status Invalid Address Mode occurred during Frame Command processing. Invalid Address status. This reference code is logged for information only. 12 (1xxx) System power control network (SPCN) reference codes AJDG301 TWRCARD AJDG301 VPDPART TWRCARD SI_CARD TWRCARD TWRCARD SYSBKPL CBLALL CBLALL TWRCARD CBLALL CBLALL PWR1907 TWRCARD TWRCARD TWRCARD AJDG301 . This reference code is logged for information only. 9213 Exchange the failing items for the failing node. secondary node. 9214 Exchange the failing items for the failing node.

Response Stack Overflow Too many responses were received during System Frame command processing. Unsupported Packet Size status TWRCARD CTLPNL Unsupported Packet Size occurred during STF and Secondary Node SVCPROC Command processing. Frame-to-Frame Communications Failure TWRCARD CBLALL A frame-to-frame communications failure occurred during STF processing. Frame Node Fault An internal error in the SPCN frame node prevents the running of a Frame command.Reference codes 9215 921B 922B Invalid Frame Command status TWRCARD AJDG301 9231 9232 9233 9234 9235 Invalid Frame Command occurred during Frame Command processing. SPCN Secondary Node Timeout status TWRCARD AJDG301 An SPCN Secondary Node Timeout occurred during Command CBLALL processing. Address Unassigned status TWRCARD AJDG301 A secondary node has no address assigned during Command processing. No Free Entries No free entries were found during System Frame processing. Secondary Node Fault An SPCN Secondary Node Fault occurred during Command processing. Intrarack Communications Failure TWRCARD CBLALL An SPCN frame to secondary node communications failure occurred during Command processing. Frame Timeout status An SPCN Frame Node Timeout occurred during Network post processing. Intrarack Communications Failure TWRCARD CBLALL An SPCN secondary node to frame communications failure occurred during Command processing. If the failing secondary node is in a 9337. Invalid Packet Length for data sent. TWRCARD AJDG301 System Unit Port Fault occurred during Command processing. An Invalid Packet Length occurred for data exchanged. Response Overrun Response Overrun occurred during System Frame processing. ARA Failure 9236 TWRCARD CBLALL TWRCARD AJDG301 TWRCARD AJDG301 TWRCARD AJDG301 AJDG301 TWRCARD CBLALL AJDG301 TWRCARD CBLALL AJDG301 TWRCARD CBLALL AJDG301 TWRCARD TWRCARD AJDG301 13 9238 9239 923A 923B 9280 9281 9282 9283 (1xxx) System power control network (SPCN) reference codes . System Unit SPCN Port Fault status. ASA Failure The frame address returned by a secondary node does not match the address of the frame. go to the "Analyzing Problems" section in the 9337 Disk Array Service Information manual.

See the service documentation for instructions. See the service documentation for instructions. APAR or LICTR See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. Service Functions. Invalid Packet Length occurred for data exchanged. SPCN failing items: Failing Item ACMODUL AIRMOVR AJDG301 ALTMANL AMBTEMP AMBTMP1 AMBTMP2 BACKPLN BATCHGR BATRY BPC CABLEH CARDFLT CBLALL CTLPNL DCA DEVBPLN HMUX 14 Description AC Module Fan and Blower assemblies Vertical Licensed Internal Code. EEPROM Failure TWRCARD AJDG301 TWRCARD AJDG301 TWRCARD AJDG301 AJDG301 TWRCARD TWRCARD CBLALL TWRCARD Table 2. See the service documentation for instructions. See the service documentation for (1xxx) System power control network (SPCN) reference codes . See the service documentation for instructions. Configuration Error A configuration error was detected during System Frame processing. See the service documentation for instructions. See the service documentation for instructions. Length Check Error. BCC Fault TWRCARD A BCC Error was detected during Network post processing. Length Check occurred during SPCN post processing. See the service documentation for instructions. See the service documentation for instructions. SPCN Network Fault An SPCN frame-to-frame communication failure was detected. Alternate Manual Required Ambient temperature exceeded limit Ambient temperature too high Ambient temperature is within range Back Plane Unit Battery Power Unit Charger Battery Power Unit BPC Fault cable all for 24 inch unit Card Fault Cable Failure Control Panel DCA fault Device backplane MUX Hardware fail Document Description See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. Invalid Packet Length for data sent.Reference codes 9284 9285 9286 9287 9288 9289 C62E CB15 An Assign Frame Address Failure occurred during ARA Preprocessing. Undefined status Undefined Status occurred during Command processing. Undefined status TWRCARD AJDG301 Undefined Status occurred during Frame or STF processing.

(1400) Bulk power subsystem reference codes For use by service providers. See the service documentation for instructions. See the service documentation for instructions. INFORMATION See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. The bulk power subsystem reference codes are issued from the 24-inch power subsystem and are meant to (1xxx) System power control network (SPCN) reference codes 15 . See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions.Reference codes I2CBUS IDPART LITSTRP NEXTLVL PGDPART PWR1900 PWR1902 PWR1903 PWR1904 PWR1906 PWR1907 PWR1908 PWR1909 PWR1911 PWR1915 PWR1916 PWR1917 PWR1918 PWR2402 PWROC PWRSPLY SI_CARD SVCPROC SYSBKPL TWRCARD UPSUNIT VPDPART I2C Bus Part Vital Product Data Parts Litestrip Call next level of support Power Good Part Power-PIP 1900 Power-PIP 1902 Power-PIP 1903 Power-PIP 1904 Power-PIP 1906 Power-PIP 1907 Power-PIP 1908 Power-PIP 1909 Power-PIP 1911 Power-PIP 1915 Power-PIP 1916 Power-PIP 1917 Power-PIP 1918 Power 2402 for 24 inch unit Power Supply overcurrent Power Supply System Interconnect controller Service Processor Card System unit backplane Card enclosure or backplane UPS unit part VPD Communication Part instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions.

Air Moving Device number five is defective. Reference Code 0058 0059 0060 0061 0062 0063 0064 0065 0072 0078 0079 007D 007E 0080 Failing Item BPJ-A BPJ-B MDAA-1 MSAA-1 MDAA-2 MSAA-2 MDAA-3 MSAA-3 MDAA-4 MSAA-4 MDAA-5 MSAA-5 MDAA-6 MSAA-6 NODE-ANY MCM1 MCM2 NODE-ANY 0081 0082 00A0 00A2 00A4 00A8 16 There is a problem with sensed and passed configuration of the MCMs that are installed in the system. Air Moving Device number three is defective. BPC-A BPE-BOARD-A BPR-1B BPR-2B The input power to BPA B has been BPR-3B lost or partially lost. including isolation procdures. Note: Serviceable actions for the following SRCs require that you use the Service focal point application on the HMC to access more specific information. UPS A-side is offline and Bypass is BPC-A active. LGA shorts test has failed.Reference codes be serviced through the Service focal point application on the Hardware Management Console (HMC). which provides instructions for using the Service focal point application to remove and replace parts for specific models. All the entries in the Failing Item column in the following table link to Removing and replacing parts. Power has been restored after the (1xxx) System power control network (SPCN) reference codes . This list of (1400) bulk power subsystem reference codes is included here for informational use only. The VPD (seeprom) in the FRU specified by the slot PIH value is ANY-SLOT defective. MAPs. BPR-1A BPR-2A The input power to BPA A has been BPR-3A PWRC-BPE-A-PWR lost or partially lost.The UPS is powering the system. PWRC-BPE-B-PWR BPC-B BPE-BOARD-B UPS A-side utility failure. Air Moving Device number one is defective. Table 1. There is a problem with the BPJ. UPS A-side battery is low. The ambient room temperature is out of specification. Air Moving Device number four is defective. (1400) Bulk power subsystem reference codes Description/Action Perform all actions before exchanging Failing Items There is a problem with the BPJ. Air Moving Device number two is defective. Air Moving Device number six is defective. Logic on a PU book has reached a warning level. All DCAs have detected a critical logic over temperature in the called PU book. and instruction on how to remove and replace parts.

The voltage on voltage level 7 has reached the warning undervoltage limit for the specified cage or drawer. UPS A-side status has changed from not available to installed. UPS B-side status has changed from installed to not available. The voltage on voltage level 5 has reached the warning undervoltage limit for the specified cage or drawer. (1xxx) System power control network (SPCN) reference codes 17 . The voltage on voltage level 4 has reached the warning undervoltage limit for the specified cage or drawer. UPS B-side battery is no longer low. UPS B-side battery is low. UPS B-side is active and Bypass has ended. UPS B-side utility failure-The UPS is powering the system. The voltage on voltage level 3 has reached the warning undervoltage limit for the specified cage or drawer. There has been an internal bulk power software error. UPS A-side is active and Bypass has ended. UPS B-side is offline and Bypass is BPC-B active. The voltage on the standby level has reached the warning undervoltage limit for the specified cage or drawer. UPS A-side battery is no longer low. The voltage on voltage level 8 has reached the warning undervoltage limit for the specified cage or drawer.Reference codes 00AA 00AC 00AE 00AF 0101 0102 0103 0104 0105 0106 0107 0108 0109 0135 01A0 01A2 01A4 01A8 01AA 01AC 01AE 01AF 0201 UPS on A-side was active. The voltage on voltage level 6 has reached the warning undervoltage limit for the specified cage or drawer. UPS B-side status has changed from not available to installed. The voltage on voltage level 2 has reached the warning undervoltage limit for the specified cage or drawer. The voltage on voltage level 1 has reached the warning undervoltage limit for the specified cage or drawer. UPS A-side status has changed from installed to not available. Power has been restored after the UPS on B-side was active.

The voltage on voltage level 3 has reached the warning over voltage limit for the specified cage or drawer. An over current condition has been detected for voltage level 5 for the specified cage or drawer. An over current condition has been detected for voltage level 4 level for the specified cage or drawer. The voltage on voltage level 4 has reached the warning over voltage limit for the specified cage or drawer. An over current condition has been detected for the standby voltage level for the specified cage or drawer. An over current condition has been detected for voltage level 7 for the specified cage or drawer. An over current condition has been detected on voltage level 1 for the specified cage or drawer. An over current condition has been detected for voltage level 2 for the specified cage or drawer. The voltage on the standby level has reached the warning over voltage limit for the specified cage or drawer. The voltage on voltage level 7 has reached the warning over voltage limit for the specified cage or drawer. FRULEVEL1 FRULEVEL2 FRULEVEL3 FRULEVEL4 FRULEVEL5 FRULEVEL6 FRULEVEL7 FRULEVEL8 FRULEVEL9 18 (1xxx) System power control network (SPCN) reference codes . The voltage on voltage level 5 has reached the warning over voltage limit for the specified cage or drawer. The voltage on voltage level 2 has reached the warning over voltage limit for the specified cage or drawer. The voltage on voltage level 8 has reached the warning over voltage limit for the specified cage or drawer. An over current condition has been detected for voltage level 8 for the specified cage or drawer. An over current condition has been detected for voltage level 3 for the specified cage or drawer. The voltage on voltage level 6 has reached the warning over voltage limit for the specified cage or drawer.Reference codes 0202 0203 0204 0205 0206 0207 0208 0209 0301 0302 0303 0304 0305 0306 0307 0308 0309 The voltage on voltage level 1 has reached the warning over voltage limit for the specified cage or drawer. An over current condition has been detected for voltage level 6 for the specified cage or drawer.

The is a switch riser card. 2nd right). An over voltage condition has been detected for voltage level 4 for the specified cage or drawer. The is a switch riser card. An over voltage condition has been detected for the standby level on the specified cage or drawer. The is a defective DASD on Backplane one (P3. An over voltage condition has been detected for voltage level 3 for the specified cage or drawer. A communication fault between BPC A and the load on port J01 has been detected. An over voltage condition has been detected for voltage level 2 for the specified cage or drawer. 2nd left). leftmost). A communication fault between BPC A and the load on port J05 has been detected. The DASD backplane is defective. The is a defective DASD on Backplane four (P6. A communication fault between BPC A and the load on port J07 FRULEVEL1 FRULEVEL2 FRULEVEL3 FRULEVEL4 FRULEVEL5 FRULEVEL6 FRULEVEL7 FRULEVEL8 FRULEVEL9 FRUVPDBUS FRUVPDMEMORY FRUVPDBUS ANY-DASDBACKPLN ANY-PLANAR ANY-DASD ANY-DASD ANY-DASD ANY-DASD ANY-RISER ANY-PLANAR BPCA-PORT-1 BPCA-PORT-4 BPCA-PORT-5 BPCA-PORT-6 BPCA-PORT-7 19 (1xxx) System power control network (SPCN) reference codes . The is a defective DASD on Backplane three (Power5. The VPD (seeprom) bus in the specified drawer can not be accessed. VPD resolution failure in the cage or drawer. The is a defective DASD on Backplane two (P4. A communication fault between BPC A and the load on port J06 has been detected. An over voltage condition has been detected for voltage level 5 for the specified cage or drawer. An over voltage condition has been detected for voltage level 7 for the specified cage or drawer.Reference codes 0401 0402 0403 0404 0405 0406 0407 0408 0409 1080 1081 1082 1301 1302 1304 1305 1306 1307 1308 1309 1A11 1A14 1A15 1A16 1A17 An over voltage condition has been detected for voltage level 1 for the specified cage or drawer. A communication fault between BPC A and the load on port J04 has been detected. rightmost). An over voltage condition has been detected for voltage level 8 specified cage or drawer. The IO planar is defective. An over voltage condition has been detected for voltage level 6 for the specified cage or drawer. The VPD in CEC main storage can not be accessed or has a problem that is preventing the CEC from powering on.

An over current has been detected on 350V between BPC B and the load on its port J05. An over current has been detected on 350V between BPC A and the load on its port J09. An over current has been detected on 350V between BPC B and the load on its port J08. An over current has been detected on 350V between BPC A and the load on its port J07. A communication fault between BPC A and the load on port J08 has been detected. A communication fault between BPC B and the load on port J04 has been detected. An over current has been detected on 350V between BPC A and the load on its port J08. An over current has been detected on 350V between BPC A and the load on its port J04.Reference codes 1A18 1A19 1A94 1A95 1A96 1A97 1A98 1A99 1B11 1B14 1B15 1B16 1B17 1B18 1B19 1B94 1B95 1B96 1B97 1B98 1B99 has been detected. An over current has been detected on 350V between BPC B and the BPCA-PORT-8 BPCA-PORT-9 BPCA-PORT-4 BPCA-PORT-5 BPCA-PORT-6 BPCA-PORT-7 BPCA-PORT-8 BPCA-PORT-9 BPCB-PORT-1 BPCB-PORT-4 BPCB-PORT-5 BPCB-PORT-6 BPCB-PORT-7 BPCB-PORT-8 BPCB-PORT-9 BPCB-PORT-4 BPCB-PORT-5 BPCB-PORT-6 BPCB-PORT-7 BPCB-PORT-8 BPCB-PORT-9 20 (1xxx) System power control network (SPCN) reference codes . A communication fault between BPC B and the load on port J06 has been detected. A communication fault between BPC B and the load on port J01 has been detected. An over current has been detected on 350V between BPC B and the load on its port J04. A communication fault between BPC B and the load on port J09 has been detected. A communication fault between BPC B and the load on port J05 has been detected. An over current has been detected on 350V between BPC B and the load on its port J07. An over current has been detected on 350V between BPC A and the load on its port J06. A communication fault between BPC B and the load on port J08 has been detected. A communication fault between BPC B and the load on port J07 has been detected. A communication fault between BPC A and the load on port J09 has been detected. An over current has been detected on 350V between BPC A and the load on its port J05. An over current has been detected on 350V between BPC B and the load on its port J06.

Make sure that there are no blocked or dirty air inlet or filters. BPC-A The bulk power fan is defective in BPF-B BPA-B. BPE-BOARD-A BPR-3A Communication error btween BPC BPC-A A and BPR 3A. DCA number one is defective. BPC-A BPR-1A Communication error btween BPC BPC-A A and BPR 1A. DCA-02 DCA number three is defective. BPC-A BPD-1A BPD-1 is defective in BPA-A.Make sure that there are no blocked or dirty air inlet or filters. BPD-3A BPR-2A BPR-3A BPE-BOARD-A The BPC in BPA-A is defective. A BPA has reported 'No airflow in cage'.Reference codes 2051 2052 2053 2054 2055 2069 2070 2071 2073 2074 2093 2095 2096 2097 209A 209B 209C 209D 209E 209F load on its port J09. BPR-1A BPC-A BPD-1A BPA-A BPR-1 is defective. BPE-BOARD-B BPR-2B Communication error btween BPC BPC-B B and BPR 2B. BPE-BOARD-A BPR-2A Communication error btween BPC BPC-A A and BPR 2A. BPD-2A BPD-3A IBF-1A BPE-BOARD-A BPR-1A BPD-1A BPC-A BPA-A has reported an BPD-2A over-current on the 350VDC bulk. BPC-B All DCAs reported 'No airflow in cage' . BPR-1A located in BPA-A has reported an 'Over Temperature' Make sure that the Air inlets are not BPR-1A blocked / filler books installed in empty locations and no heat source is located near the BPR ASM. BPR-1B located in BPA-B has reported an 'Over Temperature' Make sure that the Air inlets are not BPR-1B blocked / filler books installed in empty locations and no heat source is located near the BPR ASM. DCA-01 DCA number two is defective. DCA-03 The bulk power fan is defective in BPF-A BPA-A. BPE-BOARD-A BPR-1B Communication error btween BPC BPC-B B and BPR 1B.Make sure that there are no blocked or dirty air inlet or filters. A BPA has reported 'No airflow in cage' . BPE-BOARD-B Communication error btween BPC BPR-3B 21 (1xxx) System power control network (SPCN) reference codes .

BPC-A EPO-SWITCH The EPO panel or the cable CBL-BPCA-EPO between both BPCs and EPO panel CBL-BPCB-EPO is defective. DCA-11 DCA number two is defective. BPD-3A BPR-2A BPR-3A BPE-BOARD-A The BPC in BPA-B is defective. BPC-B BPD-2 is defective in BPA-A. BPC-A BPC-B The UEPO switch on the BPC A-side is defective or in the BPC-A BYPASS posistion. DCA-12 (1xxx) System power control network (SPCN) reference codes . 20A3 20A5 20A6 20A7 20B3 20B5 20B7 20B9 20C1 20C2 20C3 20C5 2151 2152 22 BPC-B BPE-BOARD-B BPR-2A BPC-A BPD-1A BPA-A BPR-2 is defective. BPD-3A BPR-1A BPR-3A BPE-BOARD-A BPD-3A BPD-3 is defective in BPA-A. CBL-BPCA-EPO BPR-3A BPD-1A BPC-A BPR-3A has reported an BPD-2A over-current on the 350VDC bulk. EPO-SWITCH BPC-A BPR-1A The BPC on the A-side has BPR-2A detected an open UEPO loop. BPR-3A CBL-BPCA-EPO BPE-BOARD-A EPO-SWITCH A-side BPC detects an open room BPC-A UEPO loop. BPD-2A BPC-A BPR-3A BPC-A BPD-1A BPA-A BPR-3 is defective.Reference codes B and BPR 3B. BPD-2A BPD-3A IBF-2A BPE-BOARD-A BPR-1A BPD-1A BPC-A BPR-1A has reported an BPD-2A over-current on the 350VDC bulk. BPD-3A BPR-1A BPR-2A BPE-BOARD-A DCA number one is defective. BPD-2A BPD-3A IBF-3A BPE-BOARD-A BPR-2A BPD-1A BPC-A BPR-2A has reported an BPD-2A over-current on the 350VDC bulk.

and that no heat source is located near the BPR ASM. BPC-B BPR-3B BPC-B BPD-1B BPA-B BPR-3 is defective. The BPC on the B-side has EPO-SWITCH detected an open UEPO loop. Make sure that the air inlets are not blocked. that filler books are BPR-2A installed in empty locations. BPD-3B BPC-B The UEPO switch on the BPC B-side is defective or in the BPC-B BYPASS posistion. BPD-3B BPR-1B BPR-3B BPE-BOARD-B BPD-3 is defective in BPA-B. Make sure that the air inlets are not blocked. DCA-13 BPR-2A located in BPA-A has reported an over temperature error. BPD-2B BPD-3B IBF-2B BPE-BOARD-B BPD-2B BPD-2 is defective in BPA-B. BPD-3B BPR-2B BPR-3B BPE-BOARD-B BPD-1 is defective in BPA-B. BPD-2B BPD-3B IBF-3B BPE-BOARD-B BPR-2B BPD-1B BPC-B BPR-2B has reported an BPD-2B over-current on the 350VDC bulk. BPR-2A located in BPA-A has reported an over temperature error. BPD-2B BPD-3B IBF-1B BPE-BOARD-B BPR-1B BPD-1B BPC-B BPD-2B BPA-B has reported an over-current on the 350VDC bulk. and that no heat source is located near the BPR ASM. that filler books are BPR-2B installed in empty locations. BPR-1B BPC-B BPD-1B BPA-B BPR-1 is defective.Reference codes 2153 2173 2174 2193 2195 2197 21A3 21A7 21B3 21B5 21B7 21C1 21C2 DCA number three is defective. BPD-1B BPC-B BPR-2B BPC-B BPD-1B BPA-B BPR-2 is defective. BPC-B BPR-1B BPR-2B BPR-3B CBL-BPCB-EPO 23 (1xxx) System power control network (SPCN) reference codes .

BPE-BOARD-A A communication fault between the BPD 1A and the load on port J00 BPD1A-PORT-0 has been detected. A communication fault between the BPD 1A and the load on port J02 BPD1A-PORT-2 has been detected. DCA-32 DCA number three is defective. that filler books are BPR-3A installed in empty locations. DCA number one is defective. A communication fault between the BPD 1A and the load on port J04 BPD1A-PORT-4 has been detected. BPR-3A located in BPA-A has reported an over temperature error. A communication fault between the BPD 1A and the load on port J01 BPD1A-PORT-1 has been detected. DCA-21 DCA number two is defective. that filler books are BPR-3B installed in empty locations. BPE-BOARD-A A communication fault between the BPD-3A BPC (BPA-A) and BPD 3A has BPC-A been detected. DCA-23 BPR-3A located in BPA-A has reported an over temperature error. BPD-3B BPR-2B BPR-3B BPE-BOARD-B A communication fault between the BPD-1A BPC (BPA-A) and BPD 1A has BPC-A been detected. DCA-33 BPR-1B BPD-1B BPC-B BPR-1B has reported an BPD-2B over-current on the 350VDC bulk. and that no heat source is located near the BPR ASM. (1xxx) System power control network (SPCN) reference codes .Reference codes 21C3 21C5 2251 2252 2253 2273 2274 2351 2352 2353 24A5 2A0A 2A0B 2A0C 2A10 2A11 2A12 2A13 2A14 24 BPE-BOARD-B EPO-SWITCH B-side BPC detects an open room BPC-B UEPO loop. BPD-3B BPR-1B BPR-2B BPE-BOARD-B DCA number one is defective. and that no heat source is located near the BPR ASM. DCA-22 DCA number three is defective. DCA-31 DCA number two is defective. Make sure that the air inlets are not blocked. A communication fault between the BPD 1A and the load on port J03 BPD1A-PORT-3 has been detected. Make sure that the air inlets are not blocked. BPE-BOARD-A A communication fault between the BPD-2A BPC (BPA-A) and BPD 2A has BPC-A been detected. CBL-BPCB-EPO BPR-3B BPD-1B BPC-B BPR-3A has reported an BPD-2B over-current on the 350VDC bulk.

A communication fault between the BPD 3A and the load on port J05 has been detected. A communication fault between the BPD 2A and the load on port J05 has been detected. A communication fault between the BPD 2A and the load on port J04 has been detected. A communication fault between the BPD 2A and the load on port J07 has been detected. A communication fault between the BPD 3A and the load on port J01 has been detected. A communication fault between the BPD 3A and the load on port J03 has been detected. A communication fault between the BPD 1A and the load on port J06 has been detected. BPD1A-PORT-5 BPD1A-PORT-6 BPD1A-PORT-7 BPD1A-PORT-8 BPD1A-PORT-9 BPD2A-PORT-0 BPD2A-PORT-1 BPD2A-PORT-2 BPD2A-PORT-3 BPD2A-PORT-4 BPD2A-PORT-5 BPD2A-PORT-6 BPD2A-PORT-7 BPD2A-PORT-8 BPD2A-PORT-9 BPD2A-PORT-0 BPD2A-PORT-1 BPD2A-PORT-2 BPD2A-PORT-3 BPD2A-PORT-4 BPD2A-PORT-5 (1xxx) System power control network (SPCN) reference codes 25 . A communication fault between the BPD 2A and the load on port J02 has been detected. A communication fault between the BPD 1A and the load on port J08 has been detected. A communication fault between the BPD 2A and the load on port J01 has been detected. A communication fault between the BPD 3A and the load on port J04 has been detected. A communication fault between the BPD 2A and the load on port J08 has been detected. A communication fault between the BPD 2A and the load on port J06 has been detected. A communication fault between the BPD 3A and the load on port J00 has been detected. A communication fault between the BPD 1A and the load on port J09 has been detected. A communication fault between the BPD 2A and the load on port J00 has been detected.Reference codes 2A15 2A16 2A17 2A18 2A19 2A20 2A21 2A22 2A23 2A24 2A25 2A26 2A27 2A28 2A29 2A30 2A31 2A32 2A33 2A34 2A35 A communication fault between the BPD 1A and the load on port J05 has been detected. A communication fault between the BPD 2A and the load on port J03 has been detected. A communication fault between the BPD 1A and the load on port J07 has been detected. A communication fault between the BPD 3A and the load on port J02 has been detected. A communication fault between the BPD 2A and the load on port J09 has been detected.

A communication fault between (BPA-A) BPC and (BPA-B) BPC.Reference codes 2A36 2A37 2A38 2A39 2A81 2A90 2A91 2A92 2A93 2A94 2A95 2A96 2A97 2A98 2A99 2AA0 2AA1 2AA2 2AA3 2AA4 2AA5 A communication fault between the BPD 3A and the load on port J06 has been detected. An over current has been detected on 350V between BPD 1A and the load on its port J08. An over current has been detected on 350V between BPD 2A and the load on its port J00. A communication fault between the BPD 3A and the load on port J07 has been detected. An over current has been detected on 350V between BPD 1A and the load on its port J04. An over current has been detected on 350V between BPD 1A and the load on its port J09. An over current has been detected on 350V between BPD 2A and the load on its port J03. An over current has been detected on 350V between BPD 1A and the load on its port J03. An over current has been detected on 350V between BPD 1A and the load on its port J00. An over current has been detected on 350V between BPD 2A and the load on its port J05. An over current has been detected on 350V between BPD 1A and the load on its port J06. A communication fault between the BPD 3A and the load on port J08 has been detected. An over current has been detected on 350V between BPD 1A and the load on its port J01. An over current has been detected on 350V between BPD 2A and the load on its port J02. An over current has been detected on 350V between BPD 2A and the load on its port J01. BPD2A-PORT-6 BPD2A-PORT-7 BPD2A-PORT-8 BPD2A-PORT-9 BPC-A NET-BPCA-BPCB BPC-B BPD1A-PORT-0 BPD1A-PORT-1 BPD1A-PORT-2 BPD1A-PORT-3 BPD1A-PORT-4 BPD1A-PORT-5 BPD1A-PORT-6 BPD1A-PORT-7 BPD1A-PORT-8 BPD1A-PORT-9 BPD2A-PORT-0 BPD2A-PORT-1 BPD2A-PORT-2 BPD2A-PORT-3 BPD2A-PORT-4 BPD2A-PORT-5 26 (1xxx) System power control network (SPCN) reference codes . An over current has been detected on 350V between BPD 2A and the load on its port J04. An over current has been detected on 350V between BPD 1A and the load on its port J07. An over current has been detected on 350V between BPD 1A and the load on its port J05. An over current has been detected on 350V between BPD 1A and the load on its port J02. A communication fault between the BPD 3A and the load on port J08 has been detected.

An over current has been detected on 350V between BPD 3A and the load on its port J03. An over current has been detected on 350V between BPD 3A and the load on its port J02. A communication fault between the BPC (BPA-B) and BPD 1B has been detected.Reference codes 2AA6 2AA7 2AA8 2AA9 2AB0 2AB1 2AB2 2AB3 2AB4 2AB5 2AB6 2AB7 2AB8 2AB9 2B0A 2B0B 2B0C 2B10 2B11 2B12 2B13 An over current has been detected on 350V between BPD 2A and the load on its port J06. An over current has been detected on 350V between BPD 2A and the load on its port J07. An over current has been detected on 350V between BPD 3A and the load on its port J07. An over current has been detected on 350V between BPD 3A and the load on its port J06. A communication fault between the BPC (BPA-B) and BPD 2B has been detected. An over current has been detected on 350V between BPD 2A and the load on its port J08. A communication fault between the BPD 1B and the load on port J02 has been detected. A communication fault between the BPD 1B and the load on port J01 has been detected. A communication fault between the BPD 1B and the load on port J03 has been detected. An over current has been detected on 350V between BPD 3A and the load on its port J09. A communication fault between the BPD 1B and the load on port J00 has been detected. An over current has been detected on 350V between BPD 3A and the load on its port J08. An over current has been detected on 350V between BPD 3A and the load on its port J00. BPD2A-PORT-6 BPD2A-PORT-7 BPD2A-PORT-8 BPD2A-PORT-9 BPD2A-PORT-0 BPD2A-PORT-1 BPD2A-PORT-2 BPD2A-PORT-3 BPD2A-PORT-4 BPD2A-PORT-5 BPD2A-PORT-6 BPD2A-PORT-7 BPD2A-PORT-8 BPD2A-PORT-9 BPD-1B BPC-B BPE-BOARD-B BPD-2B BPC-B BPE-BOARD-B BPD-3B BPC-B BPE-BOARD-B BPD1B-PORT-0 BPD1B-PORT-1 BPD1B-PORT-2 BPD1B-PORT-3 (1xxx) System power control network (SPCN) reference codes 27 . An over current has been detected on 350V between BPD 3A and the load on its port J05. A communication fault between the BPC (BPA-B) and BPD 3B has been detected. An over current has been detected on 350V between BPD 3A and the load on its port J04. An over current has been detected on 350V between BPD 3A and the load on its port J01. An over current has been detected on 350V between BPD 2A and the load on its port J08.

A communication fault between the BPD 1B and the load on port J05 has been detected. A communication fault between the BPD 1B and the load on port J09 has been detected. A communication fault between the BPD 2B and the load on port J01 has been detected. A communication fault between the BPD 2B and the load on port J07 has been detected. A communication fault between the BPD 3B and the load on port J03 has been detected. A communication fault between the BPD 2B and the load on port J02 has been detected. BPD1B-PORT-4 BPD1B-PORT-5 BPD1B-PORT-6 BPD1B-PORT-7 BPD1B-PORT-8 BPD1B-PORT-9 BPD2B-PORT-0 BPD2B-PORT-1 BPD2B-PORT-2 BPD2B-PORT-3 BPD2B-PORT-4 BPD2B-PORT-5 BPD2B-PORT-6 BPD2B-PORT-7 BPD2B-PORT-8 BPD2B-PORT-9 BPD2B-PORT-0 BPD2B-PORT-1 BPD2B-PORT-2 BPD2B-PORT-3 BPD2B-PORT-4 28 (1xxx) System power control network (SPCN) reference codes . A communication fault between the BPD 1B and the load on port J06 has been detected. A communication fault between the BPD 2B and the load on port J09 has been detected. A communication fault between the BPD 1B and the load on port J07 has been detected. A communication fault between the BPD 2B and the load on port J00 has been detected. A communication fault between the BPD 3B and the load on port J04 has been detected. A communication fault between the BPD 3B and the load on port J00 has been detected. A communication fault between the BPD 2B and the load on port J03 has been detected. A communication fault between the BPD 2B and the load on port J05 has been detected.Reference codes 2B14 2B15 2B16 2B17 2B18 2B19 2B20 2B21 2B22 2B23 2B24 2B25 2B26 2B27 2B28 2B29 2B30 2B31 2B32 2B33 2B34 A communication fault between the BPD 1B and the load on port J04 has been detected. A communication fault between the BPD 2B and the load on port J08 has been detected. A communication fault between the BPD 3B and the load on port J01 has been detected. A communication fault between the BPD 3B and the load on port J02 has been detected. A communication fault between the BPD 2B and the load on port J06 has been detected. A communication fault between the BPD 2B and the load on port J04 has been detected. A communication fault between the BPD 1B and the load on port J08 has been detected.

An over current has been detected on 350V between BPD 1B and the load on its port J03. An over current has been detected on 350V between BPD 1B and the load on its port J05. An over current has been detected on 350V between BPD 1B and the load on its port J01. A communication fault between the BPD 3B and the load on port J08 has been detected. An over current has been detected on 350V between BPD 1B and the load on its port J02. A communication fault between the BPD 3B and the load on port J06 has been detected. An over current has been detected on 350V between BPD 2B and the load on its port J01. A communication fault between (BPA-B) BPC and (BPA-A) BPC. An over current has been detected on 350V between BPD 2B and the load on its port J04. An over current has been detected on 350V between BPD 1B and the load on its port J09. An over current has been detected on 350V between BPD 1B and the load on its port J00. An over current has been detected on 350V between BPD 2B and the load on its port J03. A communication fault between the BPD 3B and the load on port J07 has been detected. An over current has been detected on 350V between BPD 1B and the load on its port J07. BPD2B-PORT-5 BPD2B-PORT-6 BPD2B-PORT-7 BPD2B-PORT-8 BPD2B-PORT-9 BPC-B NET-BPCB-BPCA BPC-A BPD1B-PORT-0 BPD1B-PORT-1 BPD1B-PORT-2 BPD1B-PORT-3 BPD1B-PORT-4 BPD1B-PORT-5 BPD1B-PORT-6 BPD1B-PORT-7 BPD1B-PORT-8 BPD1B-PORT-9 BPD2B-PORT-0 BPD2B-PORT-1 BPD2B-PORT-2 BPD2B-PORT-3 BPD2B-PORT-4 (1xxx) System power control network (SPCN) reference codes 29 . An over current has been detected on 350V between BPD 1B and the load on its port J08. A communication fault between the BPD 3B and the load on port J08 has been detected. An over current has been detected on 350V between BPD 1B and the load on its port J06. An over current has been detected on 350V between BPD 1B and the load on its port J04. An over current has been detected on 350V between BPD 2B and the load on its port J00.Reference codes 2B35 2B36 2B37 2B38 2B39 2B81 2B90 2B91 2B92 2B93 2B94 2B95 2B96 2B97 2B98 2B99 2BA0 2BA1 2BA2 2BA3 2BA4 A communication fault between the BPD 3B and the load on port J05 has been detected. An over current has been detected on 350V between BPD 2B and the load on its port J02.

BPC A side detects cabling order to a DCA different than to the other ANY-SLOT DCAs (This BPA sides view). An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-8 load on its port J08. An over current has been detected on 350V between BPD 3A and the BPD2B-PORT-5 load on its port J05. An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-3 load on its port J03. An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-6 load on its port J06. BPC A side detects cabling order to a MDA different than to the other ANY-SLOT MDAs (This BPA sides view). An over current has been detected on 350V between BPD 2B and the BPD2B-PORT-6 load on its port J06. An over current has been detected on 350V between BPD 2B and the BPD2B-PORT-9 load on its port J08. An over current has been detected on 350V between BPD 2B and the BPD2B-PORT-7 load on its port J07. BPC A side has detected ANY-SLOT miscabling to DCA port. IBF-1A BPR-1A BPC-A side detects that IBF-1A is CBL-IBF1A defective. BPC A side has detected unmatched FRUs in the same ANY-SLOT CageID. An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-0 load on its port J00. An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-2 load on its port J02. An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-9 load on its port J09. BPR-1B (1xxx) System power control network (SPCN) reference codes 30 . BPC-A BPE-BOARD-A BPC-B side detects that IBF-1B is IBF-1B defective. An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-7 load on its port J07. An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-1 load on its port J01. An over current has been detected on 350V between BPD 3B and the BPD2B-PORT-4 load on its port J04. An over current has been detected on 350V between BPD 2B and the BPD2B-PORT-8 load on its port J08.Reference codes 2BA5 2BA6 2BA7 2BA8 2BA9 2BB0 2BB1 2BB2 2BB3 2BB4 2BB5 2BB6 2BB7 2BB8 2BB9 3000 3005 3006 3007 3014 3015 An over current has been detected on 350V between BPD 2B and the BPD2B-PORT-5 load on its port J05.

BPC-A BPE-BOARD-A BPR-2B IBF-2B BPC-B side does not detect IBF-2B CBL-IBF2B or IBF CB open. BPC-A BPE-BOARD-A BPR-1B IBF-1B BPC-B side detects that IBF-1B is CBL-IBF1B disconnected. BPC-B BPE-BOARD-B IBF-1A BPA-A side detects that IBF-1A has BPR-1A dropped below a usable level. IBF-2B CBL-IBF2B 31 (1xxx) System power control network (SPCN) reference codes . BPC-B BPE-BOARD-B BPR-2A IBF-2A BPC-A side detects that IBF-2A is CBL-IBF2A disconnected. BPA-B side detects that IBF-1B has IBF-1B been charged to normal capcity. BPC B side has detected unmatched FRUs in the same ANY-SLOT CageID. BPR-2A IBF-2A BPC-A side does not detect IBF-2A CBL-IBF2A or IBF CB open. BPC-A BPE-BOARD-A BPC-B side detects that IBF-2B is BPR-2B disconnected. BPC-B BPE-BOARD-B IBF-2A BPR-2A BPC-A side detects that IBF-2A is CBL-IBF2A defective. BPC A side detects cabling order to a MDA different than to the other ANY-SLOT MDAs (This BPA sides view). BPC-B BPE-BOARD-B BPA-A side detects that IBF-1A has IBF-1A been charged to normal capcity. BPC-A BPE-BOARD-A IBF-2B BPR-2B BPC-B side detects that IBF-2B is CBL-IBF2B defective. BPC-A BPE-BOARD-A IBF-1B BPA-B side detects that IBF-1B has BPR-1B dropped below a usable level. BPC B side has detected ANY-SLOT miscabling to DCA port.Reference codes 3018 3019 301A 301B 301C 301D 3090 3095 3096 3097 3110 3111 3114 3115 3118 3119 CBL-IBF1B BPC-B BPE-BOARD-B BPR-1A IBF-1A BPC-A side detects that IBF-1A is CBL-IBF1A disconnected. BPC B side detects cabling order to a DCA different than to the other ANY-SLOT DCAs (This BPA sides view).

BPC-B BPE-BOARD-B IBF-3A BPR-3A BPC-A side detects that IBF-3A is CBL-IBF3A defective. The frame MTMS was not resolved by the time the BPC reached HMC standby. Contact your next level of support for assistance. BPA-B side detects that IBF-2B has IBF-2B been charged to normal capcity. BPC-B BPE-BOARD-B IBF-3A BPA-A side detects that IBF-3A has BPR-3A dropped below a usable level. (1xxx) System power control network (SPCN) reference codes . BPC-A BPE-BOARD-A IBF-3B BPA-B side detects that IBF-3B has BPR-3B dropped below a usable level. BPC-A BPE-BOARD-A BPR-3B IBF-3B BPC-B side detects that IBF-3B is CBL-IBF3B disconnected. BPC-A BPE-BOARD-A IBF-2B BPA-A side detects that IBF-2A has BPR-2B dropped below a usable level. The Auto-Code-Download (ACDL) of the power subsystem encountered an error. BPR-3A IBF-3A BPC-A side does not detect IBF-3A CBL-IBF3A or IBF CB open. BPC-B BPE-BOARD-B BPR-3A IBF-3A BPC-A side detects that IBF-3A is CBL-IBF3A disconnected.Reference codes 311A 311B 311C 311D 3210 3211 3214 3215 3218 3219 321A 321B 321C 321D 4001 4002 4003 32 BPC-B BPE-BOARD-B IBF-2A BPA-A side detects that IBF-2A has BPR-2A dropped below a usable level. BPC-A BPE-BOARD-A BPR-3B IBF-3B BPC-B side does not detect IBF-3B CBL-IBF3B or IBF CB open. BPC-B BPE-BOARD-B BPA-A side detects that IBF-2A has IBF-2A been charged to normal capcity. BPA-B side detects that IBF-3B has IBF-3B been charged to normal capcity. BPC-A BPE-BOARD-A IBF-3B BPR-3B BPC-B side detects that IBF-3B is CBL-IBF3B defective. BPC-B BPE-BOARD-B BPA-A side detects that IBF-3A has IBF-3A been charged to normal capcity.

Contact your next level of support for assistance. Contact your next level of support for assistance. For more on the Failing Item column entries. If the error is reported on the console. CAGE P/T Fru recovery. A send secure vpd command was received . the unit reference code is the 4 rightmost characters of word 1. A DHCP address was not assigned on Network A. If the error is reported on the control panel. A device replacement has occurred No action required. Table 1. see Table 2. verify the configuration. Contact your next level of support for assistance.Reference codes 4004 4005 8130 8131 8132 8133 8134 8135 The BPC found duplicate Mailbox IP addresses on Network A. 2. The BPC found duplicate Mailbox IP addresses on Network B. 2107) Disk unit reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 3002 Addressed device is not responding Failing Item FCPORT FCDEV FCIOA FCINTF OPT_CLN FCDEV FCIOA OPT_CLN FCDEV FCIOA OPT_CLN 3010 3020 3029 3100 Disk device returned wrong response to IOP Storage subsystem configuration error If an MES is being installed. There has been an internal bulk power software error. the unit reference code is characters 5 through 8 of the top 16 character line of function 11. (1750. 2107) Disk unit reference codes 1. 2105. This reference code is logged for information only. (1750. Fibre Channel interface error occurred 3109 IOP timed out a disk command FCINTF FCDEV FCIOA OPT_CLN FCDEV FCINTF FCIOA OPT_CLN 34FF Format in progress (1xxx) System power control network (SPCN) reference codes 33 . Disk unit failing items details. which follows the reference code table below. A TMS (60) was received Informational SRC. The UEPO switch has been used-This is an informational SRC. This contains an ACDL log Informational SRC. 2105. Find the unit reference code in the following table.Informational SRC.

Reference codes FFF3 FFF4 FFF5 FFF6 The device indicated that a format is in progress. the unit reference code is characters 5 through 8 of the top 16 character line of function 11. 28CB. If the error is reported on the console. For more information. Symbolic FRU Isolation Problem Analysis. which follows the reference code table below. 28D2. 506D. When the format is complete. Table 2. 28DB. 283F. If the error is reported on the control panel. 506E) Device backplane reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 1511 A non-fatal error occurred on power supply 1 Failing Item DISKPWR DISKFAN FI01106 DEVBPLN DISKPWR DISKFAN 1515 A fatal error occurred on power supply 1 34 (1xxx) System power control network (SPCN) reference codes . Symbolic FRU Isolation Problem Analysis. Symbolic FRU Isolation (180A. 283C. 283D. 283F. Temporary Fibre Channel interface error FCINTF FCDEV A disk unit service action is recommended only if the Service Action Log FCIOA contains an entry for this reference code. 283D. 28DF. 28DF. For more information. Find the unit reference code in the following table. 506D. 28CC. Symbolic FRU Isolation Problem Analysis. 28B9. 283C. Disk device wrong response was recovered by the IOP FCDEV FCIOA A disk unit service action is recommended only if the Service Action Log OPT_CLN contains an entry for this reference code. 28DB. This reference code is logged for information only. 28CB. see OPT_CLN Using the Service Action Log. Symbolic FRU Isolation Problem Analysis. 2. 28CC. (180A. Table 1. For more on the Failing Item column entries. the device should be useable. For more information. 28B9. No action is required. Device backplane failing items details. see Using the Service Action Log. Attention: The 673x is a read cache. see Using the Service Action Log. Disk media format bad Disk device problem Disk sector read error Disk device detected recoverable error FCDEV FCDEV FCDEV FCDEV FFFA FFFE A disk unit service action is recommended only if the Service Action Log contains an entry for this reference code. 506E) Device backplane reference codes 1. see Table 2. the unit reference code is the 4 rightmost characters of word 1. Symbolic FRU Isolation Problem Analysis. Perform all actions required for 673x as a disk drive and logic card except where separate 673x cache instructions are provided. 28D2. Disk Unit failing items details Failing Item FCDEV FCINTF FCIOA FCPORT IOP OPT_CLN Description Fibre Channel device Fibre Channel interface Fibre Channel IOA Port not operational I/O processor card Fiber optic cleaning kit Document Description Problem Analysis.

Device backplane failing items details Failing Item 08F5352 08F5361 17G2504 21F1511 21F1512 21F1512 21F1513 21F1514 21F1519 21F1530 21F1687 21F1688 21F1689 21F2070 Description Token-ring network adapter Document Description Repair and Parts. removal and installation procedures Internal power cable Repair and Parts. removal and installation procedures Communications input/output processor card Repair and Parts. removal and installation procedures Internal signal cable Repair and Parts. removal and installation procedures Internal power cable Repair and Parts. removal and installation procedures Diskette adapter card Repair and Parts. removal and installation procedures Bus cable 35 (1xxx) System power control network (SPCN) reference codes . removal and installation procedures Internal signal cable Repair and Parts. removal and installation procedures Card enclosure Repair and Parts. removal and installation procedures Internal power cable Repair and Parts. removal and installation procedures Internal power cable Repair and Parts. no service action required Device backplane problem FI01106 DEVBPLN DISKPWR DISKFAN FI01106 DEVBPLN DISKPWR DISKFAN FI01106 DEVBPLN DEVBPLN STORIOA FI01140 FI01106 DEVBPLN STORIOA FI01140 FI01106 DISKFAN DISKFAN DISKFAN DISKFAN DISKFAN DISKFAN DEVBPLN DEVBPLN STORIOA FI01140 FI01106 Table 2. removal and installation procedures Multiple function I/O processor card Repair and Parts.Reference codes 1521 A non-fatal error occurred on power supply 2 1525 A fatal error occurred on power supply 2 3002 Addressed device backplane failed to respond to selection 3109 I/O adapter timed out a device backplane command 7611 7614 7621 7624 7631 7634 8401 8404 FFF4 A fatal error occurred on redundant fan 1 A fatal error occurred on fan 1 A fatal error occurred on redundant fan 2 A fatal error occurred on fan 2 A fatal error occurred on redundant fan 3 A fatal error occurred on fan 3 Removable media power fault System log entry only. removal and installation procedures Multiple function I/O processor card Repair and Parts. removal and installation procedures Tape Unit Repair and Parts.

removal and installation procedures Repair and Parts.Reference codes 21F3986 21F4383 21F4493 21F4579 21F4863 21F4867 21F4868 21F4869 21F4882 21F4882 21F5620 21F5620 21F5650 21F5680 21F5772 21F5774 21F5774 21F5861 21F8566 21F8633 21F8719 21F8872 21F8890 21F9208 21F9215 21F9586 21F9907 21F9937 21F9951 21F9987 Tape I/O processor card Multiple function I/O processor card Ethernet controller card Disk drive logic card Magnetic storage device IOP card Communication adapter Communication adapter Token-ring controller card Diskette adapter card Diskette adapter card Disk unit power regulator Disk unit power regulator AC Module AC Module Control panel External signal cable Cable assembly Tape Unit Tape Unit Tape Unit Tape Unit Cable Carrier D/SE Module ISDN adapter card Power regulator card Cable assembly Cable assembly Cable assembly Tape Unit Tape unit IOP card Repair and Parts. removal and installation procedures (1xxx) System power control network (SPCN) reference codes 36 . removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts.

S. Asia External signal cable 9346 Service Guide. removal and installation procedures Planar board Repair and Parts. Recovery Procedures Communications input/output processor card Repair and Parts. removal and installation procedures Test diskette (5-1/4 inch) System operation information Diskette unit Repair and Parts. removal and installation procedures Planar board Repair and Parts. removal and installation procedures Multiple function I/O processor card Repair and Parts. removal and installation procedures Token-ring network adapter Repair and Parts. removal and installation procedures Work station attachment Repair and Parts. Mid-East. SY31-0688 Terminating plug Repair and Parts. removal and installation procedures Multiple interface adapter Repair and Parts. removal and installation procedures Diskette unit Repair and Parts. removal and installation procedures System operation information Repair and Parts. removal and installation procedures Disk drive and logic card Repair and Parts. removal and installation procedures Communications I/O processor card Repair and Parts. Europe. SY31-0688 Repair and Parts.. removal and installation procedures Tape unit IOP card Repair and Parts. SY31-0688 Terminating plug Repair and Parts. removal and installation procedures Disk drive logic card Repair and Parts. removal and installation procedures Power cord. removal and installation procedures Magnetic storage device IOP card Repair and Parts. removal and installation procedures Communications adapter card Repair and Parts. Installation and Removal. Installation and Removal. removal and installation procedures Diskette adapter card Repair and Parts. removal and installation procedures Disk drive and logic card Repair and Parts. removal and installation procedures Terminating plug 9346 Service Guide. removal and installation procedures Tape I/O processor card Repair and Parts. Recovery Procedures Disk drive logic card Repair and Parts. U. Americas group Test diskette (8 inch) Ethernet network adapter card 9346 Service Guide. removal and installation procedures Token-ring network adapter Repair and Parts. Installation and Removal. Asia-Pacific group. removal and installation procedures Token-ring network adapter Repair and Parts. removal and installation procedures Planar board 37 (1xxx) System power control network (SPCN) reference codes .Reference codes 2452557 26F5028 375892 4234002 46F4115 46F4239 55F5199 55F5209 59X4718 59X4723 59X4723 59X4723 59X4819 6369759 6369881 6462385 6495268 72X5631 72X5631 72X5631 72X6361 72X6374 72X6385 72X6386 72X6387 72X6388 72X6389 72X6390 72X6391 73F8987 73F8994 73F9138 73F9139 73F9166 Fan Communication adapter Power cord.A. removal and installation procedures Communications adapter card Repair and Parts.

removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures 9346 Service Guide. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. SY31-0688 Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts.Reference codes 73F9193 73F9232 73F9244 73F9267 73F9290 73F9290 73F9345 73F9393 74F1541 74F1542 74F1543 74F1544 74F1649 74F1760 74F2201 74F2232 79X3795 8266352 85F7295 85F7305 85F7405 85F7418 85F7646 85F7846 85F9785 85F9840 85F9845 92X3030 92X3080 92X4041 Power regulator card Cable assembly Disk unit power regulator ASCII work station IOP card Control panel Control panel Tape Unit Tape Unit Card enclosure Card enclosure Card enclosure Card enclosure Tape Unit DC Bulk Module Multiple function I/O processor card Multiple function I/O processor card Terminating plug Power supply Multiple function I/O processor card Multiple function I/O processor card Base power supply Cable assembly Magnetic storage device IOP card Terminating plug Control panel Internal signal cable Internal power cable Feature power supply Disk unit power regulator Diskette unit Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures (1xxx) System power control network (SPCN) reference codes 38 . removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. removal and installation procedures Repair and Parts. Installation and Removal. removal and installation procedures Repair and Parts.

See the service documentation for instructions.Reference codes 92X4044 92X4091 92X4143 92X6551 92X7512 92X7514 92X7515 92X7516 93X0901 93X0911 93X2520 93X2701 93X2730 93X2777 A0B00E1 AJDG301 AJEDA00 AJEDA00 AJEH901 AJGJQ01 AJSLC01 AJSLC01 BACKPLN CMPRES1 DEVBPLN DEVTERM DISKDRV DISKDRV DISKDRV DISKDRV DISKDRV DISKDRV DISKDRV DISKFAN DISKLC Cable assembly Cable assembly Planar board Planar board Flex cable Internal tape unit signal cable Internal signal cable Internal power cable Disk drive logic card Disk drive and logic card Disk drive and logic card I/O processor card 9346 IOP card I/O processor card Licensed Internal Code for programmable tape unit Vertical Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code Card enclosure or backplane Compressed device and compression IOA are not compatible Device backplane Device terminator Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive and logic card Fan assembly Disk drive logic card Repair and Parts. 39 (1xxx) System power control network (SPCN) reference codes . See the service documentation for instructions. See the service documentation for instructions. APAR or LICTR Service Functions. SY31-0688 9346 Service Guide. APAR or LICTR Service Functions. removal and installation procedures Service Functions. SY31-0688 9346 Service Guide. Installation and Removal. SY31-0688 9346 Service Guide. Installation and Removal. removal and installation procedures Repair and Parts. Installation and Removal. removal and installation procedures Repair and Parts. APAR or LICTR Service Functions. See the service documentation for instructions. removal and installation procedures Repair and Parts. See the service documentation for instructions. See the service documentation for instructions. Installation and Removal. See the service documentation for instructions. removal and installation procedures 9346 Service Guide. APAR or LICTR Service Functions. See the service documentation for instructions. See the service documentation for instructions. removal and installation procedures Repair and Parts. See the service documentation for instructions. SY31-0688 Repair and Parts. See the service documentation for instructions. APAR or LICTR Service Functions. See the service documentation for instructions. APAR or LICTR Service Functions. Recovery Procedures Repair and Parts. Recovery Procedures Repair and Parts. removal and installation procedures Repair and Parts. APAR or LICTR See the service documentation for instructions. removal and installation procedures Repair and Parts. APAR or LICTR Service Functions.

Table 1. Defective diskette System operation information Defective tape or damaged cartridge System operation information The data format is incorrect. Failing items details Failing Item IOA IOP 40 Description I/O adapter card I/O processor card Document Description See the service documentation for instructions. Power Supply See the service documentation for instructions. For more on the Failing Item column entries. Disk unit tray See the service documentation for instructions. Disk drive logic card See the service documentation for instructions.Reference codes DISKLC DISKLC DISKLC DISKLC DISKLC DISKLC DISKPWR DISKTRY DISKTRY DISKTRY DISKTRY DISKTRY DISKTRY DISKTRY MSEDMED MSETCAR MSETFOR MSETMED STORIOA SVCDOCS USEUSER See the service documentation for instructions. Disk drive logic card See the service documentation for instructions. (1xxx) System power control network (SPCN) reference codes . Failing items details. (2058) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B990 I/O adapter hardware error detected Failing Item IOA FI00130 IOP MA_BRDG Table 2. Disk unit tray See the service documentation for instructions. Customer engineer directed to system See the service documentation for problem analysis instructions. Disk unit tray See the service documentation for instructions. the tape cannot System operation information be read Defective removable media System operation information Storage I/O adapter See the service documentation for instructions. Disk unit tray See the service documentation for instructions. Disk unit tray See the service documentation for instructions. which follows the reference code table below. Disk drive logic card See the service documentation for instructions. Disk drive logic card See the service documentation for instructions. Disk drive logic card See the service documentation for instructions. Disk unit tray See the service documentation for instructions. Disk unit tray See the service documentation for instructions. see Table 2. System Operator/User System operation information Disk drive logic card (2058) Reference codes Find the unit reference code in the following table.

2B2x) Model ESCALA PL 245T/R reference (error) codes Use the following tables to find the system reference code (SRC) for your model ESCALA PL 245T/R: • 20A8 xxxx: The firmware could not perform a network boot of the system • 20Dx xxxx: A hardware problem caused a firmware failure. 25Cx. File transmission (TFTP) failed. Verify that the network addresses on the server and gateway are correct. 2602. Check the network connections. 220x. Verify that the bootp server is configured correctly for this client. Verify that the network addresses on the server and gateway are correct. Do the following: 1. Verify that the network addresses on the server and gateway are correct. 2102. 20EE. See the service documentation for instructions. Do the following: 1. Cannot get server hardware address. Boot image too large. Do the following: Failing Item 20A80001 20A80002 20A80003 20A80004 20A80005 20A80006 (1xxx) System power control network (SPCN) reference codes 41 .Reference codes MA_BRDG Multi-adapter bridge See the service documentation for instructions. (20A8) Model ESCALA PL 245T/R reference (error) codes Reference Code 20A80000 Description/Action Perform all actions before exchanging Failing Items Insufficient information to boot. 20FF. (20A8. Check the network connections. 2. then retry the operation. 2. Bootp failed. Cannot get gateway IP address. Verify that the bootp server is configured correctly for this client. 2803. Client IP address is already in use by another network device. 20Dx. Verify that the network addresses on the server and gateway are correct. then retry the operation. 25Ax. or firmware detected a hardware failure • 20EE xxxx: One of the following problems might have occurred: ♦ The system detected a problem in the firmware ♦ The system did not find an operating system on the devices specified in the boot list ♦ The system detected a problem in the com port settings ♦ The system encountered a problem when installing the firmware image • 20FF xxxx: The system detected a problem when the firmware was collecting VPD • 2102 xxxx: The system detected a problem with a USB-attached CD-ROM drive • 220x xxxx: The system detected a failure in a communications adapter • 25Ax xxxx: The system encountered failures because of a problem in NVRAM • 25Cx xxxx: The system detected a problem in one or more memory DIMMs. • 2602 xxxx: The system detected a problem with the microcode on a PCI adapter • 2803 xxxx: The system detected a problem with the time-of-day clock • 2B2x xxxx: The system encountered a hardware failure in a processor Table 1.

Replace the system backplane. If it was not. and apply if available. 2. If the problem persists. Follow the operating system procedure to reject the firmware update. Do the following: 1. and apply if available. Replace the memory DIMMs in the system. Replace the system backplane. Reinstall the latest system firmware. Do the following: 1. 2. 2. If a location code is specified. where xx is: SYSBKP2 xx Description ------------------0E. it indicates that the system was unable to boot from the temporary (A) firmware side. RTAS attempt to allocate memory failed. Do the following: 1. Failure to access VPD data. then retry the operation. 2. 11 System serial number 16. Replace the system backplane. this is an informational message. 17 Universal un 20D00011 20D008xx 20D00900 Failed to generate universal unique ID (UUID) SYSBKP2 value. Do SYSBKP2 the following: 1. Do the following: Failing Item SYSBKP2 20D00010 1. Do the following: (1xxx) System power control network (SPCN) reference codes 20D00901 20D00902 SYSBKP2 SYSBKP2 20D00903 42 . replace the device at that location. Replace the system backplane. If the system was already booting from the permanent (B) side. Check for system firmware updates. If a location code is reported with the error. Table 2. 2. Check for system firmware updates. Check the network connections. 3. Selftest failed on device. (20Dx) Model ESCALA PL 245T/R reference (error) codes Reference Code 20D0000F Description/Action Perform all actions before exchanging Failing Items Self-test failed on device. The error or location code information may not be available.Reference codes 1. 3. 2. replace the device at that location code. 0F Machine type or model 10. replace the system backplane. Cannot locate SYSBKP2 package. The system is booting from the permanent (B) firmware side. Failed to communicate with the BMC. Verify that the bootp server is configured correctly for this client. Replace the system backplane. The firmware was not able to find the SYSBKP2 /openprom package.

replace the system backplane. Do the following: 1. Failed to reboot system. Check for microcode updates for the fiber channel adapter. and apply if SYSBKP2 available. Failed to reboot system. 2. SYSBKP2 and apply if available. Failed to set the watchdog timer in the base motherboard controller. replace the system backplane. Failed to send boot failed message to the BMC. If the problem persists. 2. 2. Failed to locate BMC device tree node. replace the system backplane.Reference codes 1. If the problem persists. Do the following: 1. Check for system firmware updates. SYSBKP2 and apply if available. Do the following: 1. If the problem persists. 43 Failing Item NEXTLVL 20EE000B (1xxx) System power control network (SPCN) reference codes . replace the system backplane. Check for system firmware updates. 3. If the problem persists. (20EE) Model ESCALA PL 245T/R reference (error) codes Reference Code 20EE000A Description/Action Perform all actions before exchanging Failing Items Reserved Contact your next level of support for assistance. Replace the system backplane. Check for system firmware updates. 2. Do the following: 20D10004 1. SYSBKP2 and apply if available. SYSBKP2 and apply if available. SYSBKP2 and apply if available. Firmware error before stdout ready. contact your next level of support. 2. 2. and apply if available. Stack underflow from fiber channel adapter. If the problem persists. 2. Do the following: 1. If the problem persists. replace the system backplane. Check for system firmware updates. Check for system firmware updates. Check for system firmware updates. The system was not able to find an operating system on the devices in the boot list. If the problem persists. Check for system firmware updates. replace the system backplane. 2. Do the following: 1. Do the following: 1. Check for system firmware updates and apply if available. SYSBKP2 and apply if available. 20D10005 20D10006 20D10007 20D1000A 20D10010 20D10011 Table 3.

replace the system backplane. Do the following: SYSBKP2 20EE0010 20EE0011 1. replace the system backplane. If the problem persists. 2. 2. If the problem persists. SYSBKP2 Do the following: 1. If the problem persists. 2. If the problem persists. Unable to run the root vpd method. and apply if available. 2. 2. If the problem persists. Do the following: 1. Check for system firmware updates. Failed to update VPD with the new boot SYSBKP2 path field value. 2. replace the system backplane. Verify that the boot list is correct. Check for system firmware updates. Check for system firmware updates. If the problem persists. and apply if available. Unable to find the package node. replace the system backplane. 3. replace the system backplane. Do the following: 1. Do the following: 1. SYSBKP2 and apply if available. If the problem persists. If the problem persists. 3. 2. Do the SYSBKP2 following: 1. Do the following: 1. Check for system firmware updates. and apply if available. replace the system backplane. Failed to read VPD boot path field value. 2. The environment variable boot-device SYSBKP2 exceeds the allowed character limit. and apply if available. 20EE0012 20EE0015 20EE0016 20EE0020 20EE0021 44 (1xxx) System power control network (SPCN) reference codes . and apply if available. Verify that the boot list is correct. Check for system firmware updates. Check for system firmware updates. replace the system backplane. Check for system firmware updates. 3. The environment variable boot-device SYSBKP2 contained more than seven entries. and apply if available. Do the following: 1. Verify that the boot list is correct. and apply if available. Check for system firmware updates. 3.Reference codes 20EE000F Verify that the boot list contains at least one device with a valid operating system boot image. Unable to execute the mem-dimm-vpd SYSBKP2 method. replace the system backplane. Verify that the boot list is correct. Unable to execute the vpd method.

Check for system firmware updates. 2. Reset it to a valid SYSBKP2 value. Replace the system backplane. if necessary. 2. if necessary. Use the SMS menus to check the parity setting. and apply if available. Use the System Management Services (SMS) menus to check the SYSBKP2 baud rate. Reset it to a valid value. 2. An invalid number of data bits was specified for the com port. Check for system firmware updates. Verify that the boot list is correct. The Fcode driver of the adapter is not supported on this system. replace the system backplane. An invalid number of stop bits was specified for the com port. Check for system firmware updates. Replace the system backplane. Replace the system backplane. Do the following: 1. 2. 3. 3. Reset it to a valid value. Reset it to a valid SYSBKP2 value. Fcode resident on an I/O adapter is not supported on this system. If the problem persists. Additional information may be available from your next level of support. 2. do the following: 1. Do the following: 1. Reset it to a valid SYSBKP2 value. Do the following: 1. and apply if available. Use the SMS menus to check the handshake setting. and apply if available. not the functionality of the adapter under the operating system. but does not guarantee one. Check for system firmware updates. 20EE0101 20EE0102 20EE0103 20EE0104 20EE0105 (1xxx) System power control network (SPCN) reference codes 45 . 3. Use the SMS menus to check the stop bit setting. Check for system firmware updates. 2. if necessary. Use the SMS menus to check the data bit setting. Check for system firmware updates. Do the following: 1. and apply if available. The baud rate specified for the com port is invalid. 3. and apply if available. and apply if available. if necessary. 3. if necessary. An invalid parity setting was specified for the com port. Replace the system backplane.Reference codes 20EE0022 The environment variable boot-device contained an entry that exceeded 255 characters in length. This error code only affects boot-time operation. A compatible driver may be produced in the future. An invalid handshake setting was specified SYSBKP2 for the com port. SYSBKP2 20EE0100 Informational message. Do the following: 1.

Install the firmware using a known good image. Table 5. USB CD-ROM: execution of ATA/ATAPI SYSBKP2 command was not completed within the time allowed. 3. Replace the USB CD-ROM drive. Install the firmware. Installing an image to the permanent side is not allowed. 2. Retry the operation. Install the firmware using a known good image. Boot from the temporary side. then attempt to install the firmware again. (2102) Model ESCALA PL 245T/R reference (error) codes Reference Code 21020010 Description/Action Perform all actions Failing Item before exchanging Failing Items USB CD-ROM remained busy longer than the SYSBKP2 time allowed. Note: If the system firmware is corrupted. perform the system firmware rejection function. Do the following: 1. 21020012 46 Failing Item SYSBKP2 21020011 SYSBKP2 (1xxx) System power control network (SPCN) reference codes . the firmware may be corrupted. Note: If the system firmware is corrupted. Retry the operation. Do the following: 1. Do the following: 1. replace the system backplane. The format of the firmware installation image is not correct. Note: If you are not able to boot from the temp side. then attempt to install the firmware again. 3. and apply if available. Installing system firmware failed. If no location code is specified. 2. Replace the system backplane.Reference codes 3. 4. 2. then attempt to install the latest firmware. perform the system firmware rejection function in the operating system. Try another CD. Replace the USB CD-ROM drive. Installing the system firmware failed. Check for system firmware updates. the firmware may be corrupted. 4. The CD in the USB CD-ROM drive may not be readable. 2. Replace the part indicated by the location code. 20EE0200 20EE0201 20EE0210 20EE0220 Table 4. perform the system firmware rejection function. Replace the system backplane. Install the firmware using a known good image. Replace the system backplane. (20FF) Model ESCALA PL 245T/R reference (error) codes Reference Code 20FF0001 Description/Action Perform all actions before exchanging Failing Items Problem with VPD. Do the following: 1.

If the problem persists. If the problem persists. PCI Ethernet adapter failure 22001001 Replace the adapter. Replace the system backplane. 3. USB CD-ROM: bootable CD is missing from the CD-ROM drive. Gigabit Ethernet adapter failure • If the location code reported with the error specifies the adapter in the PCI SYSBKP2 slot. 3. Do the following: 1. Try another CD. continue with the next step. PCI Ethernet adapter failure 22001002 Replace the adapter. replace the system backplane. 3. Check for system firmware updates. 2. Retry the operation. Retry the operation. 5. Gigabit Ethernet adapter failure SYSBKP2 47 21020013 21020014 21020015 Failing Item 22003002 22003003 (1xxx) System power control network (SPCN) reference codes . Do the following: 1. continue with the next step. and correct any problems that you find. Place a bootable CD-ROM in the USB CD-ROM drive. Replace the USB CD-ROM drive. 4. and apply if available. • If the location code specifies the integrated Ethernet. 2. Table 6. Try another CD. Check the power and signal connectors going to the USB CD-ROM drive. Replace the USB CD-ROM drive. The CD in the USB CD-ROM drive may not be readable. Replace the system backplane. Replace the system backplane.Reference codes USB CD-ROM: execution of ATA/ATAPI command by the USB CD-ROM failed. (220x) Model ESCALA PL 245T/R reference (error) codes Reference Code 22000001 Description/Action Perform all actions before exchanging Failing Items PCI Ethernet adapter failure Replace the adapter. Check for system firmware updates. and apply if available. continue with the next step. replace that adapter. USB CD-ROM: ATA/ATAPI packed command SYSBKP2 execution by USB CD-ROM failed. 4. The CD in the USB CD-ROM drive may not be readable. do the following: 1. 2. 4. If the problem persists. Replace the USB CD-ROM drive. USB CD-ROM: the CD in the drive has been SYSBKP2 changed.

Table 7. • If this error code does not occur again. Unable to expand target partition: writing error log entry Refer to the actions for error code 25A80xxx. Do the following: 1. Then power the system back up. When one of these errors occurs. boot device list) information has been lost. device test failed Refer to the actions for error code 25A80xxx. NVRAM data validation check failed. 2. Unable to expand target partition: saving configuration variable Refer to the actions for error code 25A80xxx. remove it. replace the system backplane. • If this error code occurs again. these errors are SYSBKP2 warnings that the NVRAM data had to be reestablished and do not require any FRU replacement unless the error is persistent. NVRAM problems Errors reported against NVRAM can be caused by low battery voltage and (more rarely) power outages that occur during normal system usage. Before replacing any system component.Reference codes If there is an adapter plugged into the PCI slot in the system. and apply if available. Initialization failed. If the problem persists. any system customization (for example. 25A80xxx 25A80000 25A80100 25A80201 25A80202 48 (1xxx) System power control network (SPCN) reference codes . Do the following: Failing Item SYSBKP2 25A10001 1. PCI token ring adapter failure 22011001 Replace the adapter. (25Ax) Model ESCALA PL 245T/R reference (error) codes Reference Code 25A00001 Description/Action Perform all actions before exchanging Failing Items L2 cache controller failure. Check for system firmware updates. Cache L2 SRAM failure SYSBKP2 1. Replace the system backplane. replace the system backplane. and apply if available. refer to the actions for error code 25A80xxx. Replace the system backplane. 2. turn off and then turn on the system unit. replace the PCI adapter card that you removed. 2. Check for system firmware updates. With the exception of the 25A80000 error. If the error is persistent. retry the operation. Then. PCI token ring adapter failure 22010001 Replace the adapter.

NEXTLVL No user action or FRU replacement exists for this error. the operating system. Reseat them if necessary. Ensure that all DIMMs are properly seated. and device tree contents. Do the following: 1. 3. 2. Contact your next level of support for assistance. the current system configuration. Setenv/$Setenv parameter error: name contains a null character Refer to the actions for error code 25A80xxx. DIMM failure. a PCI adapter ROM code or utility. Replace the system backplane. or an operator (by using the open firmware script editing command nvedit). NVRAMRC script evaluation error: command line execution error Running of a command line within the nvram configuration variable nvramrc (script) resulted in a throw being run. Resolving the problem may not be possible without a detailed analysis of the NVRAM script.Reference codes 25A80203 Unable to expand target partition: writing VPD data Refer to the actions for error code 25A80xxx. call your next level of support. 25A80210 25A80211 25A80998 This script can be modified by the firmware SMS utilities. If this error persists. Replace the DIMMs one at a time until the failing DIMM is isolated. (25Cx) Model ESCALA PL 245T/R reference (error) codes Reference Code 25C00000 Description/Action Perform all actions before exchanging Failing Items No DIMMs detected. where xx and yy indicate: xx Description ------------------01 DIMM2 missing 10 DIMM1 missing 12 DIMM1 not supported 14 DIMM1 failed 21 DIMM2 not supported 22 DIMM1 and DIMM2 unsupported 41 DIMM2 failed 88 DIMM1 and DIMM2 mismatch yy Description ------------------01 DIMM4 missing 10 DIMM3 missing 12 DIMM3 not supported (1xxx) System power control network (SPCN) reference codes 49 Failing Item SYSBKP2 25C0xxyy SYSBKP2 . Table 8. Setenv/$Setenv parameter error: name contains a null character Refer to the actions for error code 25A80xxx. NVRAMRC script evaluation error: stack unbalanced on completion NEXTLVL 25A80999 This is a firmware debug environment error. and reboot the system.

If they are not. Replace the DIMM specified by the location code. Verify that the DIMMs are installed in pairs. then reboot the system. 3. Do the following: 1. replace the system backplane. properly install the DIMMs. (2602) Model ESCALA PL 245T/R reference (error) codes 50 (1xxx) System power control network (SPCN) reference codes . Reboot the system. Verify that the DIMMs in the system are supported. Replace all unsupported DIMMs. The companion (in the pair) of the memory DIMM specified by the location code is failing. missing. If the problem persists. If they are not. If the problem persists. If the problem persists. SYSBKP2 Memory DIMM failure 1. 4. 5. replace the system backplane. Verify that the DIMMs are installed in SYSBKP2 one or more pairs. then reboot the system. then reboot the system. replace the system backplane. reseat if necessary. 25C10001 25C10002 25C10003 Table 9. properly install the DIMMs. then reboot the system.Reference codes 14 21 22 41 88 DIMM3 DIMM4 DIMM3 DIMM4 DIMM3 failed not supported and DIMM4 unsupported failed and DIMM4 mismatch Do the following: 1. Memory DIMM is not supported 1. Replace the companion of the DIMM specified by the location code. 4. SYSBKP2 2. reseat if necessary. If they are not. then reboot the system. then reboot the system. 3. 3. Ensure that the DIMMs are properly seated. 2. then reboot the system. Verify that the DIMMs are installed in one or more pairs. properly install the DIMMs. Reboot the system. 3. Verify that the DIMMs in the system are supported. Insure that the DIMMs are properly seated. Replace the DIMM specified by the location code. or unmatched. 2. Reboot the system. unsupported. Verify that the DIMMs in the system are supported. Replace all unsupported DIMMs. Replace the companion DIMM in the pair. If the problem persists. 2. 4. Replace all unsupported DIMMs. replace the system backplane.

If no microcode updates are available. When one of these errors occurs. and apply if available. Note: This is normally an informational message. Check for adapter microcode updates. replace the PCI adapter. Replace the system battery. If the problem persists. Reset the server time and date through the installed operating system. 2.Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items PCI device fcode evaluation error. Set the time and date. or if installing new microcode does not correct the problem. replace the system backplane. Failing Item 26020008 SYSBKP2 26020009 Table 10. 2. The PCI adapter Fcode left a data stack imbalance. Replace the system backplane. Unless the error is persistent. Reseat the adapter and reboot the system. do the following: 1. and apply if available. 2. These errors are warnings that the real time clock data content needs to be reestablished. the system loses time and date SYSBKP2 information. Do the following: 1. and apply if available. • If the location code identifies a slot. If the problem persists. If the error is persistent. replace the 28030001 (1xxx) System power control network (SPCN) reference codes 51 . • If the location code identifies the system backplane. Real-time-clock not updating: real-time-clock SYSBKP2 initialization required. do the following: 1. 3. replace the system backplane. Failing Item 2803000A Errors reported against the real time clock might be caused by low battery voltage or (more rarely) power outages that occur during normal system usage. Replace the adapter. 3. these errors do not require any FRU replacement. Check for system firmware updates. 4. Note: Using the adapter for booting is not recommended until after you install the new adapter microcode. (2803) Model ESCALA PL 245T/R reference (error) codes Reference Code Description/Action Perform all actions before exchanging Failing Items The Hypervisor function to get or set the time-of-day (TOD) reported an error. Check for system firmware updates.

Check for system firmware updates. SYSBKP2 Real-time-clock battery error Replace the system backplane. Look at the last 8 characters of the top 16 character line of function 12 (word 3). An exception error has been reported on a processor The type of interrupt that caused the exception is specified by the x as follows: x Description ------------------0 Unknown interrupt 1 System reset interrupt (SRI) 2 Machine check interrupt (MCI) 3 Data storage interrupt (DSI) 4 Instruction storage interrupt (ISI) 5 External interrupt (EXI) 6 Alignment interrupt (ALI) 7 Program interrupt (SRI) 8 Floating unavailable interrupt (FUI) Failing Item SYSBKP2 2B2x00EE SYSBKP2 Do the following: 1. SYSBKP2 Replace the system backplane.Reference codes 28030002 system backplane. (2724. Bad time/date values Set the time and date. SYSBKP2 28030003 28030004 Note: This is normally an informational message. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). If the problem persists. 28030005 Table 11. (2B2x) Model ESCALA PL 245T/R reference (error) codes Reference Code 2B200x31 2B208888 Description/Action Perform all actions before exchanging Failing Items Processor x is faulty Replace the system backplane. data mode) changed. and apply if available. replace the system backplane. Real-time-clock not updating: not correctable. 2. The unit address portion of the card address is 52 (1xxx) System power control network (SPCN) reference codes . 6149) Reference codes 1. Replace the system backplane. These 8 characters are the direct select address of the card (BBBBCcbb). These 4 characters are the unit reference code. Set the time and date. 2. Operating system termination request received Informational message. Do the following: 1. 2744. 2. Refer to the actions under 28030001. Real-time-clock operating mode parameters (for example.

which follows the reference code table below. Failing items details. (2742. Card locations can be found using the 16 character address. Find the unit reference code in the following table. APAR or LICTR 53 (1xxx) System power control network (SPCN) reference codes . Failing items details. Look at the last 8 characters of the top 16 character line of function 12 (word 3). Table 1. See SRC Address Formats. For more on the Failing Item column entries. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Failing items details Failing Item AJDGP01 MA_BRDG Description Input/Output Processor Licensed Internal Code Multi-adapter bridge Document Description Service Functions. These 8 characters are the direct select address of the card (BBBBCcbb). These 4 characters are the unit reference code. Table 2. 2805) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B940 I/O adapter hardware error detected B941 One of the ports on the IOA has failed. 2. see Table 2. 3. Failing items details Failing Item AJDGP01 MA_BRDG Description Licensed Internal Code Multi-adapter bridge Document Description Service Functions. 2793. Failing Item FI00719 AJDGP01 MA_BRDG FI00719 AJDGP01 Table 2. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). 6149) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B904 I/O adapter Licensed Internal Code failed. see Table 2. 3. (2742. Find the unit reference code in the following table. 2744.Reference codes characters 1 through 8 of the bottom 16 character line of function 11 (word 4). I/O adapter hardware error detected Failing Item AJDGP01 FI00719 AJDGP01 FI00718 FI00719 FI00719 FI00718 AJDGP01 MA_BRDG FI00719 FI00718 B934 Incompatible hardware detected. See SRC Address Formats. 2793. Card locations can be found using the 16 character address. For more on the Failing Item column entries. 2805) Reference codes 1. B920 B921 I/O adapter Licensed Internal Code failed. APAR or LICTR See the service documentation for instructions. Table 1. which follows the reference code table below. (2724.

(2745) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B904 I/O adapter Licensed Internal Code failed. Find the unit reference code in the following table. (2743. Card locations can be found using the 16 character address. see Table 2. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Card locations can be found using the 16 character address. 3. Table 1. Look at the last 8 characters of the top 16 character line of function 12 (word 3). which follows the reference code table below. Find the unit reference code in the following table. 2. Failing items details Failing Item AJDGP01 MA_BRDG Description LIC . (2743. Failing items details. 2. These 8 characters are the direct select address of the card (BBBBCcbb). For more on the Failing Item column entries. Failing items details. See SRC Address Formats.Input/Output Processor Licensed Internal Code Multi-adapter bridge Document Description Service Functions.Reference codes See the service documentation for instructions. 2760) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B950 Licensed Internal Code error B951 I/O adapter hardware error detected Failing Item AJDGP01 FI00718 FI00719 FI00719 FI00718 AJDGP01 MA_BRDG Table 2. (2745) Reference Codes 1. I/O adapter hardware error detected (1xxx) System power control network (SPCN) reference codes . 3. Look at the last 8 characters of the top 16 character line of function 12 (word 3). See SRC Address Formats. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (word 4). These 4 characters are the unit reference code. 2760) Reference codes 1. which follows the reference code table below. see Table 2. For more on the Failing Item column entries. B934 B940 54 Failing Item AJDGP01 FI00719 FI00719 FI00718 Incompatible hardware detected. Table 1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). APAR or LICTR See the service documentation for instructions. These 8 characters are the direct select address of the card (BBBBCcbb). These 4 characters are the unit reference code.

Reference codes B941 to B942 One half of I/O adapter failed. Table 2. (2746) Twinaxial – workstation adapter reference codes 1. Workstation adapter failing items details Failing Item AJDGP01 MA_BRDG Description LIC .Input/Output Processor Licensed Internal Code Multi-adapter bridge Document Description Service Functions. 3. the unit reference code is characters 5 through 8 of the top 16 character line of function 11. Table 1. the unit reference code is the 4 rightmost characters of word 1. 5709) Reference codes If the error is reported on the control panel. APAR or LICTR See the service documentation for instructions. Workstation adapter failing items details. 2763. Card locations can be found using the 16 character address. which follows the reference code table below. These 4 characters are the unit reference code.Input/Output Processor Licensed Internal Code Multi-adapter bridge Document Description Service Functions. (2748. 5703. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). Look at the last 8 characters of the top 16 character line of function 12 (word 3). Failing items details Failing Item AJDGP01 MA_BRDG Description LIC . For more on the Failing Item column entries. (1xxx) System power control network (SPCN) reference codes 55 . 2. These 8 characters are the direct select address of the card (BBBBCcbb). APAR or LICTR See the service documentation for instructions. FI00719 FI00718 AJDGP01 MA_BRDG FI00719 FI00718 AJDGP01 Table 2. If the error is reported on the console. B934 B940 Incompatible hardware detected. (2746) Twinaxial – workstation adapter reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B904 I/O adapter Licensed Internal Code failed. 2780. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). 2782. 2757. See SRC Address Formats. see Table 2. I/O adapter hardware error detected Failing Item AJDGP01 FI00719 FI00719 FI00718 FI00719 FI00718 AJDGP01 MA_BRDG FI00719 FI00718 AJDGP01 B941 to B942 One half of I/O adapter failed. Find the unit reference code in the following table. 2778.

perform IOPIP17. I/O processor detected a SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 2. To correct or isolate a possible user error STORIOA or configuration error. Use the failing item (FI) codes to find failing devices. 2763. perform IOPIP17. I/O processor detected a SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 3. For more on the Failing Item column entries. I/O processor card detected interface error FI01107 STORIOA Error occurred on SCSI bus 1.Reference codes Find the unit reference code in the following table. 2782. FI01140 BACKPLN Perform IOPIP13. To correct or isolate a possible user error STORIOA or configuration error. 5703. see Table 2. (2748. To correct or isolate a possible user error STORIOA or configuration error. Use the failing item (FI) codes to find failing devices. I/O Processor detected that the bus is not operational 3121 SVCDOCS 56 (1xxx) System power control network (SPCN) reference codes . 2757. System bus error IOP ANYBUS STORIOA I/O processor detected a SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 0. 5709) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 1310 I/O processor resource not available Failing Item 3006 3020 3021 3022 3023 3100 3101 3102 3103 3120 The I/O processor error log is being filled faster than the errors are being reported to the system. Use the failing item (FI) codes to find failing devices. which follows the reference code table below. 2778. To correct or isolate a possible user error STORIOA or configuration error. I/O processor detected a SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 1. FI01140 BACKPLN Perform IOPIP13. Table 1. 2780. I/O processor card detected interface error FI01107 STORIOA Error occurred on SCSI bus 2. I/O processor card detected interface error FI01107 STORIOA Error occurred on SCSI bus 0. FI01140 BACKPLN Perform IOPIP13. FI01140 BACKPLN Perform IOPIP13. I/O Processor detected that the bus is not operational SVCDOCS A device was added to SCSI bus 0 of the I/O Adapter and caused the bus to become not operational. perform IOPIP17. Use the failing item (FI) codes to find failing devices. Check other errors reported to the system and correct them. Remove the device. I/O processor card detected interface error FI01107 STORIOA Error occurred on SCSI bus 3. Failing Items Details. perform IOPIP17.

I/O Processor detected that the bus is now operational SVCDOCS 3123 SVCDOCS 3140 3141 3142 3143 3150 This reference code and the 3123 reference code that occurred before it require no service action. I/O processor detected a SCSI bus configuration error SVCDOCS Internal and external SCSI cables are connected to SCSI bus 0 at the same time. Correct the SCSI bus 0 configuration. since SCSI bus 1 is now operational. I/O Processor detected that the bus is now operational This reference code and the 3121 reference code that occurred before it require no service action. This reference code is logged for information only. IOA detected recoverable device bus error An error occurred on SCSI bus 2. Correct the SCSI bus 1 configuration. No action is required. This reference code is logged for information only. I/O processor Licensed Internal Code error IOA detected recoverable device bus error An error occurred on SCSI bus 0. No action is required. Remove the device. Remove the device. since SCSI bus 2 is now operational. I/O processor card detected device error 3151 SVCDOCS 3400 3401 3501 3600 to 3601 8008 8009 8012 8100 8130 Device backplane problem I/O processor Licensed Internal Code error System log entry only. I/O Processor detected that the bus is not operational A device was added to SCSI bus 2 of the I/O Adapter and caused the bus to become not operational. no service action required A permanent cache battery pack failure occurred Impending cache battery pack failure Attached read cache devices exceed capacity supported by IOA Reduce the number of read caches on the IOA. since SCSI bus 3 is now operational. No action is required. FI02112 STORIOA FI01106 DEVTERM FI01140 DEVBPLN AJDGP01 IOP CACHBAT STORIOA CACHBAT SVCDOCS AJDGP01 IOP 8131 8132 (1xxx) System power control network (SPCN) reference codes 57 . IOA detected recoverable device bus error An error occurred on SCSI bus 1. This reference code is logged for information only. Remove the device. since SCSI bus 0 is now operational. I/O Processor detected that the bus is now operational This reference code and the 3122 reference code that occurred before it require no service action. I/O Processor detected that the bus is now operational This reference code and the 3120 reference code that occurred before it require no service action. I/O processor detected a SCSI bus configuration error Internal and external SCSI cables are connected to SCSI bus 1 at the same time. I/O Processor detected that the bus is not operational A device was added to SCSI bus 3 of the I/O Adapter and caused the bus to become not operational.Reference codes 3122 A device was added to SCSI bus 1 of the I/O Adapter and caused the bus to become not operational.

IOA detected recoverable device error No action is required. Other resources attached to the IOP may then need to be Varied On. If the Failing Item indicates I/O adapter. Mode jumper overridden due to cache data in conflicting mode See JOVERRIDE. If the I/O Processor is not operable and disk units are attached. A recoverable I/O processor error occurred. If the Failing Item indicates SVCDOCS. then do NOT replace the I/O adapter. Cache data belongs to devices other than those attached Perform IOPIP32. IOA detected recoverable device bus error No action is required. Perform the following for the I/O processor that the I/O adapter is attached to: 1. This reference code is logged for information only. Call your next level of support for assistance Cache data associated with attached devices cannot be found Perform IOPIP31. I/O processor Licensed Internal Code error I/O processor card detected device error I/O processor card detected device configuration error Perform IOPIP33. Array not functional due to present hardware configuration. use Hardware Service Manager to re-IPL the IOP. This reference code is logged for information only. If disk units are not attached. This is a recoverable error. 8140 8141 8145 8146 8150 8151 8155 to 8156 8157 8200 9000 9001 9002 AJDGP01 IOP FI01105 STORIOA SVCDOCS FI01105 STORIOA FI01140 BACKPLN FI01106 SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS 9008 9009 9010 9011 9014 9015 9020 to 9021 I/O card does not support functions expected by devices Perform IOPIP25. 58 (1xxx) System power control network (SPCN) reference codes . Mode jumper missing See JMISSING. This reference code is logged for information only. No action is required. 2. perform the VRYCFG RESET(*YES) command to reset the IOP and Vary On attached resources. Perform IOPIP20.Reference codes 8133 IOA detected recoverable device bus error An error occurred on SCSI bus 3. then replace the I/O adapter. STORIOA Disk device detected recoverable error FI01105 A permanent I/O processor failure occurred STORIOA ANYBRDG I/O processor Licensed Internal Code error AJDGP01 STORIOA A permanent I/O processor failure occurred AJDGP01 STORIOA I/O adapter card error SVCDOCS Display the Service Action Log entry for this SRC. I/O processor card detected device error Perform IOPIP16.

Array not functional due to present hardware configuration. IOP cache data exists for a missing or failed device. Either move all devices in an array to another IOP that supports arrays. Incorrect hardware configuration change has been detected. SVCDOCS Array no longer protected due to missing or failed disk unit Perform IOPIP21. If you cannot perform a type A or B IPL. perform IOPIP27. Disk unit is not supported at its physical location. Cache data exists for device that has been modified. SVCDOCS Power off the system and remove all new or replacement disk units. Incorrect hardware configuration change has been detected. Array not functional due to present hardware configuration. Perform IOPIP22. Perform IOPIP21.Reference codes 9022 to 9024 9025 9026 9027 9028 Array not functional due to present hardware configuration. SVCDOCS Contact your next level of support. IPL the system to DST. Background array parity check detected and corrected errors Call your next level of support to report the problem. perform a type D IPL from removable media. Array addendum Product Activity Log entry This entry contains additional array information for 90xx reference codes when the array contains more than 10 array members. and cannot perform a type A or B IPL. If so. Protection will be automatically restarted. perform a type D IPL from removable media. Required cache data cannot be located for a disk unit. Take action on other IOP reference codes which have surfaced. Array protection temporarily suspended No action required. IOP resources not available due to previous problems. If all configured units are missing. or stop an array on this IOP. Use the 90xx entry that occurred at the same time as this reference code as the starting point for this problem. perform the action indicated for the 9054 reference code. Look for Product Activity Log entries for other IOP reference codes and take action on them. a 9054 reference code may appear in the product activity log. Contact your next level of support. SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS 9029 902F Reduce the number of arrays on IOP. Perform IOPIP34. IOP resources not available due to previous problems. SVCDOCS SVCDOCS 9054 If you cannot get to SST or DST. Perform IOPIP22. Look for Product Activity Log entries for other IOP reference codes and take action on them. AJDGP01 SVCDOCS SVCDOCS 9030 9031. 9040 9041 9050 9051 9052 9053 Otherwise. Perform IOPIP30. Link from IOA to auxiliary cache IOA went operational 9071 (1xxx) System power control network (SPCN) reference codes 59 .

Read cache device not in correct format Contact your next level of support. See the service documentation for instructions. APAR or LICTR See the service documentation for instructions. If any reference codes are surfaced. contact your next level of support. 9091 If you cannot resolve the problem. Perform IOPIP26. (1xxx) System power control network (SPCN) reference codes 60 . Incompatible hardware detected. Incorrect hardware configuration change has been detected. Re-IPL the system. SVCDOCS FI01105 STORIOA FI01105 STORIOA FI01140 BACKPLN FI01106 SVCDOCS 9090 Disk unit has been modified after the last known status. Failing items details Failing Item AJDGP01 ANYBRDG ANYBUS BACKPLN CACHBAT DEVBPLN DEVTERM IOP PCIBUS STORIOA Description I/O processor Licensed Internal Code System I/O bus or any attached card IOP card bus error Card Enclosure or Planar Board Cache battery pack Device backplane Terminating plug I/O processor card Any PCI card on the PCI bus Storage I/O adapter Document Description Service Functions. See the service documentation for instructions. I/O processor card detected device error I/O processor card detected device error Perform IOPIP16. Disk unit requires initialization before use. See the service documentation for instructions.Reference codes 9072 9073 9081 9082 No service action required. If any reference codes are surfaced. go to List of system reference codes and use the new reference code as the entry point to the problem. See the service documentation for instructions. contact your next level of support. See the service documentation for instructions. Incompatible or non-operational auxiliary cache IOA attached Perform IOPIP40. See the service documentation for instructions. go to List of system reference codes and use the new reference code as the entry point to the problem. Re-IPL the system. See the service documentation for instructions. I/O adapter detected recoverable error I/O processor detected a recoverable system bus error SVCDOCS SVCDOCS STORIOA STORIOA ANYBRDG IOP ANYBUS Table 2. SVCDOCS 9092 9093 B934 FF3D FF6D If you cannot resolve the problem. Link from IOA to auxiliary cache IOA went non-operational No service action required. See the service documentation for instructions.

2767. 2768. 2842. Find the unit reference code in the following table. Other resources attached to the IOP may then need to be Varied On. 2843. Perform all actions required for 673x as a disk drive and logic card except where separate 673x cache instructions are provided.Reference codes SVCDOCS USER Customer engineer directed to system problem analysis System Operator/User See the service documentation for instructions. I/O processor card error SVCDOCS Display the Service Action Log entry for this SRC. 284B. I/O processor Licensed Internal Code error Removable media error during IPL Removable media error during IPL A permanent I/O processor failure occurred 2200 2201 2202 3000 AJDGP01 USER FI01105 FI00022 FI01105 FI01101 IOP 61 (1xxx) System power control network (SPCN) reference codes . 2768. If the I/O Processor is not operable and disk units are attached. (2749. 2842. This is a recoverable error. If the error is reported on the control panel. which follows the reference code table below. Table 1. see Table 2. If the Failing Item indicates SVCDOCS. Failing Items Details. the unit reference code is the 4 rightmost characters of word 1. then replace the IOP. the unit reference code is characters 5 through 8 of the top 16 character line of function 11. If the Failing Item indicates IOP. 2. See the service documentation for instructions. 570B) Reference codes 1. use Hardware Service Manager to re-IPL the IOP. 284B. Check other errors reported to the system and correct them. 5702. 2844. (2749. If disk units are not attached. Perform the following: 1. If the error is reported on the console. 2. 5702. then do NOT replace the IOP. 2767. perform the VRYCFG RESET(*YES) command to reset the IOP and Vary On attached resources. 2843. 2844. For more on the Failing Item column entries. Attention: The 673x is a read cache. 570B) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 0A17 A permanent I/O processor failure occurred Failing Item IOP MA_BRDG AJDGP01 AJDG301 AJDGP01 AJDG301 IOP MA_BRDG FI01105 AJDGP01 AJDG301 0A22 I/O processor detected a storage transfer error 102E 1307 1310 Out of alternate sectors for disk storage I/O processor resource not available I/O processor resource not available 1317 The I/O processor error log is being filled faster than the errors are being reported to the system.

FI01140 FI01141 FI01106 System bus error IOP ANYBUS FI01101 I/O processor detected a SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 0. Use the failing item (FI) codes to find failing devices. FI01140 BACKPLN Perform IOPIP13. Use the failing item (FI) codes to find failing devices. Addressed device failed to respond to selection MA_BRDG IOP AJDGP01 3002 3006 3020 3021 3022 3023 3080 3081 3084 3087 3100 3101 3102 3103 3109 62 FI01105 STORIOA Perform IOPIP16.Reference codes 3001 Not valid condition in I/O Processor Licensed Internal Code The Licensed Internal Code found a condition that should not have occurred. FI01140 BACKPLN Perform IOPIP13. I/O processor Licensed Internal Code error AJDGP01 System log entry only. I/O processor detected a SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 1. FI01140 BACKPLN Perform IOPIP13. I/O processor card detected interface error FI01107 STORIOA Error occurred on SCSI bus 2. I/O processor detected a SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 2. To correct or isolate a possible user error STORIOA or configuration error. perform IOPIP17. perform IOPIP17. perform IOPIP17. I/O processor detected a SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 3. I/O processor timed out a device command (1xxx) System power control network (SPCN) reference codes . FI01104 MA_BRDG I/O processor resource not available AJDGP01 AJDG301 The Licensed Internal Code could not allocate resources on the I/O IOACNFG processor card. FI01104 I/O processor card detected interface error FI01107 STORIOA Error occurred on SCSI bus 0. I/O processor card detected interface error FI01107 STORIOA Error occurred on SCSI bus 1. I/O processor card detected interface error FI01107 STORIOA Error occurred on SCSI bus 3. FI01140 BACKPLN Perform IOPIP13. To correct or isolate a possible user error STORIOA or configuration error. Use the failing item (FI) codes to find failing devices. To correct or isolate a possible user error STORIOA or configuration error. perform IOPIP17. Use the failing item (FI) codes to find failing devices. To correct or isolate a possible user error STORIOA or configuration error. no service action required I/O processor card or Licensed Internal Code error AJDGP01 IOP A microprocessor exception occurred on the I/O processor.

Correct the SCSI bus 1 configuration. 3110 I/O processor card detected interface error Perform IOPIP16. A tape/CD or disk device reported a failure 3151 SVCDOCS 3200 3203 3205. Remove the device. but the disk unit does not need to be replaced. since SCSI bus 3 is now operational. since SCSI bus 0 is now operational. USER Perform a D-IPL and work on errors found in the log. I/O Processor detected that the bus is not operational A device was added to SCSI bus 3 of the I/O Adapter and caused the bus to become not operational. I/O Processor detected that the bus is not operational A device was added to SCSI bus 1 of the I/O Adapter and caused the bus to become not operational. Remove the device. 3120 I/O Processor detected that the bus is not operational A device was added to SCSI bus 0 of the I/O Adapter and caused the bus to become not operational. I/O processor detected a SCSI bus configuration error SVCDOCS Internal and external SCSI cables are connected to SCSI bus 0 at the same time. (1xxx) System power control network (SPCN) reference codes 63 . I/O Processor detected that the bus is now operational This reference code and the 3121 reference code that occurred before it require no service action. I/O processor detected a SCSI bus configuration error Internal and external SCSI cables are connected to SCSI bus 1 at the same time. I/O Processor detected that the bus is not operational A device was added to SCSI bus 2 of the I/O Adapter and caused the bus to become not operational. I/O Processor detected that the bus is now operational FI01105 STORIOA FI01140 BACKPLN FI01106 FI01105 STORIOA FI01140 BACKPLN FI01106 SVCDOCS 3121 SVCDOCS 3122 SVCDOCS 3123 SVCDOCS 3136 3140 USER FI01105 3141 3142 3143 3150 This reference code and the 3123 reference code that occurred before it require no service action. Correct the SCSI bus 0 configuration. since SCSI bus 2 is now operational. 3215 Disk media format bad Disk sector read error FI01105 STORIOA IOP MEDIA FI01105 FI01105 3250 Disk unit data may need to be reloaded. I/O Processor detected that the bus is now operational This reference code and the 3122 reference code that occurred before it require no service action. since SCSI bus 1 is now operational. The removable media device is assigned elsewhere I/O Processor detected that the bus is now operational This reference code and the 3120 reference code that occurred before it require no service action. Disk unit requires initialization before use. Remove the device. Remove the device.Reference codes Perform IOPIP16.

CACHE STORIOA Note: DO NOT replace both FRUs at the same time. Exchange the FRUs one at a time in the order shown. AJDGP01 A permanent IOP or cache adaptor card failure occurred. Exchange the FRUs one at a time in the order shown. Exchange the FRUs one at a time in the order shown. No action is required. STORIOA CACHE Note: DO NOT replace both FRUs at the same time. no service action required IOP A permanent I/O processor failure occurred I/O processor Licensed Internal Code error AJDGP01 I/O processor Licensed Internal Code error AJDGP01 IOP IPL device not ready MEDIA FI01105 USER I/O processor resource not available AJDGP01 I/O processor card detected media error MEDIA AJDGP01 FI01105 I/O processor Licensed Internal Code error AJDGP01 IOP I/O processor Licensed Internal Code error AJDGP01 IOP MA_BRDG A permanent IOA hardware error occurred FCIOA OPT_CLN IOA LID is not valid AJDGP01 An I/O processor Licensed Internal Code error occurred. A permanent cache adaptor card failure occurred.Reference codes 3300 3400 3401 3501 3600 to 3601 6070 6071 6072 6073 6075 6076 6081 to 6083 6085 6200 6201 6602 8000 8002 8004 8005 8007 8010 to 8011 MEDIA FI00121 Perform IOPIP01. A permanent cache adaptor card failure occurred. IOA detected recoverable device bus error (1xxx) System power control network (SPCN) reference codes Storage unit detected a media problem 8100 8130 AJDGP01 IOP 8131 64 . FI01141 I/O processor card detected device error FI02112 STORIOA NOTE: If external devices are attached check EXTSCSI and DEVTERM FI01106 first. Exchange the FRUs one at a time in the order shown. CACHE STORIOA The cache adaptor card may be missing. broken or incompatible. Note: DO NOT replace both FRUs at the same time. Exchange the FRUs one at a time in the order shown. DEVTERM FI01140 Device backplane problem DEVBPLN I/O processor Licensed Internal Code error AJDGP01 IOP System log entry only. CACHE STORIOA Note: DO NOT replace both FRUs at the same time. FI01141 STORIOA A recoverable IOP or cache adaptor card error occurred. I/O processor Licensed Internal Code error IOA detected recoverable device bus error An error occurred on SCSI bus 0. STORIOA CACHE Note: DO NOT replace both FRUs at the same time. This reference code is logged for information only. Voltage drop detected on I/O processor 5 volt power supply. A recoverable cache adaptor card error occurred.

IOA detected recoverable device error No action is required. STORIOA Disk device detected recoverable error FI01105 A permanent I/O processor failure occurred STORIOA ANYBRDG I/O processor Licensed Internal Code error AJDGP01 STORIOA A permanent I/O processor failure occurred AJDGP01 STORIOA I/O adapter card error SVCDOCS Display the Service Action Log entry for this SRC. use Hardware Service Manager to re-IPL the IOP. Call your next level of support for assistance Cache data associated with attached devices cannot be found (1xxx) System power control network (SPCN) reference codes . 8133 8140 8141 8145 8146 8150 8151 8155 to 8156 8157 8200 8300 8301 AJDGP01 IOP STORIOA IOP AJDGP01 FI01101 AJDGP01 IOP AJDGP01 FI01105 STORIOA SVCDOCS FI01105 STORIOA FI01140 BACKPLN FI01106 SVCDOCS SVCDOCS SVCDOCS 65 8400 9000 9001 9002 9008 9009 9010 I/O card does not support functions expected by devices Perform IOPIP25. then do NOT replace the I/O adapter. IOA detected recoverable device bus error No action is required. No action is required. If the I/O Processor is not operable and disk units are attached. 2. If the Failing Item indicates SVCDOCS. A recoverable I/O processor error occurred. Perform the following for the I/O processor that the I/O adapter is attached to: 1. IOA detected recoverable device bus error An error occurred on SCSI bus 3. perform the VRYCFG RESET(*YES) command to reset the IOP and Vary On attached resources.Reference codes 8132 An error occurred on SCSI bus 1. This reference code is logged for information only. This reference code is logged for information only. This reference code is logged for information only. I/O processor Licensed Internal Code error I/O processor card or Licensed Internal Code error A microprocessor exception occurred on the I/O processor. This is a recoverable error. then replace the I/O adapter. I/O processor Licensed Internal Code error I/O processor card detected device error I/O processor card detected device configuration error Perform IOPIP33. Other resources attached to the IOP may then need to be Varied On. I/O processor card detected device error Perform IOPIP16. This reference code is logged for information only. Not valid condition in I/O Processor Licensed Internal Code The Licensed Internal Code found a condition that should not have occurred. If the Failing Item indicates I/O adapter. No action is required. This reference code is logged for information only. If disk units are not attached. IOA detected recoverable device bus error An error occurred on SCSI bus 2. No action is required.

SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS 9029 902F Reduce the number of arrays on IOP. 9040 9041 9050 9051 SVCDOCS 9052 9053 66 Otherwise. IOP cache data exists for a missing or failed device. Perform IOPIP20. Perform IOPIP28. Array not functional due to present hardware configuration.Reference codes 9011 9012 Perform IOPIP31. The cache adapter card is missing or broken. The IOP and attached cache adaptor card are not compatible. Use the 90xx entry that occurred at the same time as this reference code as the starting point for this problem. If so. Background array parity check detected and corrected errors Call your next level of support to report the problem. Perform IOPIP19. Disk unit is not supported at its physical location. SVCDOCS CACHE 9013 9020 to 9021 9022 to 9024 9025 9026 9027 9028 Perform IOPIP29. SVCDOCS Contact your next level of support. Array not functional due to present hardware configuration. SVCDOCS SVCDOCS (1xxx) System power control network (SPCN) reference codes . or stop an array on this IOP. Array addendum Product Activity Log entry This entry contains additional array information for 90xx reference codes when the array contains more than 10 members. IOP resources not available due to previous problems. Cache data exists for device that has been modified. Perform IOPIP22. perform IOPIP27. If all configured units are missing. Perform IOPIP30. Array not functional due to present hardware configuration. Array no longer protected due to missing or failed disk unit Perform IOPIP21. Perform IOPIP22. Array protection temporarily suspended No action required. a 9054 reference code may appear in the product activity log. Required cache data cannot be located for a disk unit. AJDGP01 SVCDOCS SVCDOCS 9030 9031. Perform IOPIP34. Cache data belongs to devices other than those attached Perform IOPIP32. Perform IOPIP21. Array not functional due to present hardware configuration. perform the action indicated for the 9054 reference code. Either move all devices in an array to another IOP that supports arrays. IOP requires a cache adaptor card but cannot find it. Protection will be automatically restarted. Incorrect hardware configuration change has been detected. Incorrect hardware configuration change has been detected.

contact your next level of support. SVCDOCS Re-IPL the system. Incorrect hardware configuration change has been detected. If any reference codes are surfaced. B935 Unknown hardware detected SVCDOCS IOP MA_BRDG IOP IOP IOP MA_BRDG STORIOA FI01107 FI01140 STORIOA DEVTERM FI01101 AJDGP01 IOP MA_BRDG AJDGP01 IOP FI01104 MA_BRDG STORIOA ANYBRDG IOP ANYBUS SVCDOCS 9054 9081 9082 9090 BE00 I/O processor detected a fault condition. go to List of system reference codes and use the new reference code as the entry point to the problem. FI01140 BACKPLN FI01106 Disk unit has been modified after the last known status. If you cannot perform a type A or B IPL. perform a type D IPL from removable media. Look for Product Activity Log entries for other IOP reference codes and take action on them. If any reference codes are surfaced. 9092 B3B1 to B3B7 B3B8 B3B9 B3E0 to B3E1 B410 to B411 B412 If you cannot resolve the problem. A permanent I/O processor failure occurred I/O processor detected a fault condition. A permanent I/O processor failure occurred Tape/CD or disk bus interface error occurred Perform IOPIP16. Failing items details (1xxx) System power control network (SPCN) reference codes 67 . Disk unit requires initialization before use. go to List of system reference codes and use the new reference code as the entry point to the problem. Look for Product Activity Log entries for other IOP reference codes and take action on them. Re-IPL the system. I/O processor card detected device error FI01105 STORIOA I/O processor card detected device error FI01105 STORIOA Perform IOPIP16. If you cannot get to SST or DST. contact your next level of support. Perform IOPIP26. IPL the system to DST. FF3D FF6D I/O adapter detected a recoverable error I/O processor detected a recoverable system bus error Table 2. 9091 If you cannot resolve the problem. A permanent I/O processor failure occurred Multi-adapter bridge error detected. IOP resources not available due to previous problems. perform a type D IPL from removable media.Reference codes Take action on other IOP reference codes which have surfaced. SVCDOCS Power off the system and remove all new or replacement disk units. and cannot perform a type A or B IPL.

(2750. I/O processor card See the service documentation for instructions. Fiber optic cleaning kit See the service documentation for instructions. Multi-adapter bridge See the service documentation for instructions. Cache battery pack See the service documentation for instructions. Control panel. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). APAR or LICTR Service Functions. See SRC Address Formats. These 8 characters are the direct select address of the card (BBBBCcbb). Find the unit reference code in the following table. 2751) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B980 to B983 I/O adapter hardware error detected Failing Item FI00719 FI00730 68 (1xxx) System power control network (SPCN) reference codes . Device backplane See the service documentation for instructions. Customer engineer directed to system See the service documentation for problem analysis instructions. Storage I/O adapter See the service documentation for instructions. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). or the interface to the Control See the service documentation for panel instructions. 2. APAR or LICTR Service Functions. Compressed device and compression IOA See the service documentation for are not compatible instructions. Cache adaptor card See the service documentation for instructions. IOP card bus error See the service documentation for instructions. These 4 characters are the unit reference code. 2751) Reference codes 1.Reference codes Failing Item AJDG301 AJDGP01 AJDGP01 ANYBRDG ANYBUS BACKPLN CACHBAT CACHE CMPRES1 CTLPNL DEVBPLN DEVTERM FCIOA IOACNFG IOP MA_BRDG MEDIA OPT_CLN PCIBUS STORIOA SVCDOCS USER Document Description Service Functions. Defective media See the service documentation for instructions. APAR or LICTR See the service documentation for instructions. Card locations can be found using the 16 character address. Configuration error See the service documentation for instructions. Look at the last 8 characters of the top 16 character line of function 12 (word 3). Any PCI card on the PCI bus See the service documentation for instructions. Card Enclosure or Planar Board See the service documentation for instructions. System Operator/User See the service documentation for instructions. Terminating plug See the service documentation for instructions. 3. Description Vertical Licensed Internal Code I/O card Licensed Internal Code I/O processor Licensed Internal Code System I/O bus or any attached card (2750. Fibre Channel IOA See the service documentation for instructions. Table 1.

If the error is reported on the console. These 4 characters are the unit reference code. 3. 280E.Reference codes (2761) Reference codes 1. the unit reference code is characters 5 through 8 of the top 16 character line of function 11. (2765. When the format is complete. 2787. No action is required. Table 1. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). Find the unit reference code in the following table. 280E. since the port is now operational. 280D. the device should be useable. I/O processor card detected interface error Failing Item SVCDOCS 3100 3120 I/O processor detected a port failure FCINTF ANYFC FCIOA OPT_CLN FCPORT FCIOA FCDEV OPT_CLN 3140 I/O Processor detected that a port is now operational This reference code and the 3120 reference code that occurred before it require no service action. 280D. (2761) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B980 to B983 I/O adapter hardware error detected Failing Item FI00719 FI00730 (2765. the unit reference code is the 4 rightmost characters of word 1. which follows the reference code table below. For more on the Failing Item column entries. These 8 characters are the direct select address of the card (BBBBCcbb). 5704) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 3020 I/O processor detected a configuration error Either too many devices or the wrong kind of devices have been configured under the IOA. 2766. Failing Items Details. Card locations can be found using the 16 character address. I/O processor card detected device error FCDEV FCINTF ANYFC FCIOA OPT_CLN Format in progress The device indicated that a format is in progress. 2787. see Table 2. 8140 (1xxx) System power control network (SPCN) reference codes . Recovered Fibre Channel interface error 69 3400 34FF 8130. Look at the last 8 characters of the top 16 character line of function 12 (word 3). See SRC Address Formats. This reference code is logged for information only. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (word 4). Change the configuration. 2. Table 1. 5704) Reference Codes If the error is reported on the control panel. Find the unit reference code in the following table. 2766.

Disk device detected recoverable error A permanent I/O processor failure occurred I/O processor Licensed Internal Code error FCIOA OPT_CLN FCDEV FCIOA ANYBRDG OPT_CLN AJDGP01 FCIOA IOP OPT_CLN AJDGP01 FCIOA OPT_CLN SVCDOCS 8155 to 8156 9091 to 9092 A permanent I/O processor failure occurred Incorrect hardware configuration change has been detected. Symbolic FRU Isolation Problem Analysis. For information about how to reset and IPL the I/O processor. This reference code is logged for information only. If an I/O processor reset and I/O processor IPL does not resolve the problem. Table 1. (2771. see Table 2. A recoverable I/O processor error occurred. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). Symbolic FRU Isolation Problem Analysis.Reference codes 8141 8145 8146 8150 8151 No action required. Failing items details. 2772) Reference codes 1. Look at the last 8 characters of the top 16 character line of function 12 (word 3). 2. 2772) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 70 Failing Item (1xxx) System power control network (SPCN) reference codes . which follows the reference code table below. IOA detected recoverable device error No action required. Symbolic FRU Isolation Problem Analysis. These 8 characters are the direct select address of the card (BBBBCcbb). Symbolic FRU Isolation (2771. Recovered IOA error FCIOA ANYBRDG OPT_CLN Table 2. Find the unit reference code in the following table. See SRC Address Formats. Symbolic FRU Isolation Problem Analysis. 3. This reference code is logged for information only. contact your next level of support. FF3D Reset the I/O processor and then IPL the I/O processor. Failing items details Failing Item AJDGP01 ANYBRDG ANYFC FCDEV FCINTF FCIOA FCPORT IOP OPT_CLN SVCDOCS Description I/O processor Licensed Internal Code System I/O bus or any attached card Any Fibre Channel device Fibre Channel device Fibre Channel interface Fibre Channel IOA Port not operational I/O processor card Fiber optic cleaning kit Customer engineer directed to system problem analysis Document Description Service Functions. Card locations can be found using the 16 character address. Symbolic FRU Isolation Problem Analysis. see Debug the resource. Symbolic FRU Isolation Problem Analysis. APAR or LICTR Problem Analysis. For more on the Failing Item column entries. Symbolic FRU Isolation Problem Analysis. Symbolic FRU Isolation Problem Analysis. These 4 characters are the unit reference code. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (Word 4).

Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). These 8 characters are the direct select address of the card (BBBBCcbb). AJDGP01 FI00719 FI00719 FI00718 FI00719 FI00718 AJDGP01 MA_BRDG FI00719 FI00718 AJDGP01 Table 2. 2849) Reference codes 1. 2849) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B904 I/O adapter Licensed Internal Code failed. (281x) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B910 I/O adapter hardware error detected Failing Item FI00719 FI00730 FI00718 (2838. Find the unit reference code in the following table. B930 I/O adapter Licensed Internal Code failed. Table 1. (281x) Reference codes 1. Look at the last 8 characters of the top 16 character line of function 12 (word 3). 71 Failing Item AJDGP01 FI00719 (1xxx) System power control network (SPCN) reference codes . Card locations can be found using the 16 character address. Card locations can be found using the 16 character address. See SRC Address Formats. Incompatible hardware detected. (2838. 3.Reference codes B904 B934 B940 I/O adapter Licensed Internal Code failed.Input/Output Processor Licensed Internal Code Multi-adapter bridge Document Description Service Functions. Look at the last 8 characters of the top 16 character line of function 12 (word 3). See SRC Address Formats. Failing items details. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). 3. see Table 2. These 8 characters are the direct select address of the card (BBBBCcbb). which follows the reference code table below. 2. 2. These 4 characters are the unit reference code. APAR or LICTR See the service documentation for instructions. I/O adapter hardware error detected B941 to B942 One half of I/O adapter failed. These 4 characters are the unit reference code. Failing items details Failing Item AJDGP01 MA_BRDG Description LIC . The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (word 4). Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). Find the unit reference code in the following table. Table 1. For more on the Failing Item column entries.

If the error is reported on the console.Input/Output Processor Licensed Internal Code Multi-adapter bridge Document Description Service Functions. Failing items details. FCIOA A permanent I/O processor failure occurred IOP MA_BRDG OPT_CLN Not valid condition in I/O Processor Licensed Internal Code IOP AJDGP01 The Licensed Internal Code found a condition that should not have occurred. (2847) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 0A17 A permanent I/O processor failure occurred Failing Item IOP MA_BRDG AJDGP01 AJDG301 AJDGP01 AJDG301 IOP MA_BRDG AJDGP01 AJDG301 0A22 I/O processor detected a storage transfer error 1307 1310 I/O processor resource not available I/O processor resource not available 3000 3001 3002 3006 72 The I/O processor error log is being filled faster than the errors are being reported to the system.Reference codes B931 I/O adapter hardware error detected B933 Incompatible hardware detected. Failing items details Failing Item AJDGP01 MA_BRDG Description LIC . Addressed device is not responding FCPORT FCDEV FCIOA FCINTF OPT_CLN System bus error (1xxx) System power control network (SPCN) reference codes . Check other errors reported to the system and correct them. the unit reference code is the 4 rightmost characters of word 1. Table 1. APAR or LICTR See the service documentation for instructions. Find the unit reference code in the following table. which follows the reference code table below. (2847) Reference codes If the error is reported on the control panel. see Table 2. the unit reference code is characters 5 through 8 of the top 16 character line of function 11. AJDGP01 FI00718 FI00719 FI00719 FI00718 AJDGP01 MA_BRDG FI00719 AJDGP01 Table 2. For more on the Failing Item column entries.

(1xxx) System power control network (SPCN) reference codes . I/O processor card detected interface error 3100 3109 I/O processor timed out a device command 3120 I/O processor detected a port failure 3200 A disk device reported a failure 3501 6070 6071 6072 6075 6076 6081 to 6083 6085 6200 6201 8100 8150 8155 to 8156 8200 8300 I/O processor Licensed Internal Code error A permanent I/O processor failure occurred I/O processor Licensed Internal Code error I/O processor Licensed Internal Code error I/O processor resource not available I/O processor card detected media error I/O processor Licensed Internal Code error I/O processor Licensed Internal Code error A permanent IOA hardware error occurred IOA LID is not valid I/O processor Licensed Internal Code error A permanent I/O processor failure occurred A permanent I/O processor failure occurred I/O processor Licensed Internal Code error I/O processor card or Licensed Internal Code error A microprocessor exception occurred on the I/O processor. no service action required I/O processor card or Licensed Internal Code error A microprocessor exception occurred on the I/O processor.Reference codes 3080 3081 3084 I/O processor Licensed Internal Code error System log entry only. IOP ANYBUS FCIOA OPT_CLN AJDGP01 AJDGP01 IOP FCIOA MA_BRDG OPT_CLN AJDGP01 AJDG301 FCIOA OPT_CLN FCINTF ANYFC FCIOA OPT_CLN FCDEV FCINTF FCIOA OPT_CLN FCPORT FCIOA FCDEV OPT_CLN FCDEV FCIOA IOP OPT_CLN AJDGP01 IOP IOP AJDGP01 AJDGP01 IOP AJDGP01 AJDG301 AJDGP01 FCDEV AJDGP01 IOP AJDGP01 IOP MA_BRDG FCIOA OPT_CLN AJDGP01 AJDGP01 IOP FCIOA ANYBRDG OPT_CLN AJDGP01 FCIOA OPT_CLN AJDGP01 IOP FCIOA IOP AJDGP01 OPT_CLN 73 3087 I/O processor resource not available The Licensed Internal Code could not allocate resources on the I/O processor card.

Port not operational See the service documentation for instructions.Reference codes 8301 Not valid condition in I/O Processor Licensed Internal Code The Licensed Internal Code found a condition that should not have occurred. Unknown hardware detected B3B1 to B3B7 B3B8 B3E0 to B3E1 B935 BE00 I/O processor detected a fault condition. Control panel. or the interface to the Control See the service documentation for panel instructions. Multi-adapter bridge See the service documentation for instructions. Cache adaptor card See the service documentation for instructions. A permanent I/O processor failure occurred Multi-adapter bridge error detected. Defective media See the service documentation for (1xxx) System power control network (SPCN) reference codes . APAR or LICTR See the service documentation for instructions. Any Fibre Channel device See the service documentation for instructions. Configuration error See the service documentation for instructions. Device backplane See the service documentation for instructions. I/O processor detected a fault condition. APAR or LICTR Service Functions. IOP card bus error See the service documentation for instructions. APAR or LICTR Service Functions. I/O processor card See the service documentation for instructions. Fibre Channel IOA See the service documentation for instructions. Card Enclosure or Planar Board See the service documentation for instructions. Terminating plug See the service documentation for instructions. Cache battery pack See the service documentation for instructions. Failing items details Failing Item AJDG301 AJDGP01 AJDGP01 ANYBRDG ANYBUS ANYFC BACKPLN CACHBAT CACHE CMPRES1 CTLPNL DEVBPLN DEVTERM FCDEV FCINTF FCIOA FCPORT IOACNFG IOP MA_BRDG MEDIA 74 Description Vertical Licensed Internal Code I/O processor Licensed Internal Code I/O card Licensed Internal Code System I/O bus or any attached card Document Description Service Functions. Fibre Channel interface See the service documentation for instructions. Fibre Channel device See the service documentation for instructions. FCIOA AJDGP01 IOP OPT_CLN IOP MA_BRDG IOP IOP MA_BRDG FCIOA AJDGP01 IOP MA_BRDG OPT_CLN AJDGP01 IOP FCIOA MA_BRDG OPT_CLN Table 2. Compressed device and compression IOA See the service documentation for are not compatible instructions.

(2890) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 0A17 A permanent I/O processor failure occurred Failing Item IOP MA_BRDG AJDG301 AJDGP01 AJDGP01 AJDG301 IOP MA_BRDG AJDGP01 AJDG301 75 0A22 Adapter card storage error 1307 I/O adapter resource not available. which follows the reference code table below.Reference codes OPT_CLN PCIBUS STORIOA SVCDOCS USER Fiber optic cleaning kit Any PCI card on the PCI bus Storage I/O adapter Customer engineer directed to system problem analysis System Operator/User instructions. Table 1. 3. Failing items details. See the service documentation for instructions. (287F) Reference codes 1. see Table 2. These 8 characters are the direct select address of the card (BBBBCcbb). Failing items details. which follows the reference code table below. For more on the Failing Item column entries. These 4 characters are the unit reference code. Failing items details Failing Item AJDGP01 Description Input/Output Processor Licensed Internal Code Document Description Service Functions. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). Find the unit reference code in the following table. (1xxx) System power control network (SPCN) reference codes . Look at the last 8 characters of the top 16 character line of function 12 (word 3). APAR or LICTR Failing Item FI00719 AJDGP01 (2890) Reference codes Find the unit reference code in the following table. Table 1. 2. See the service documentation for instructions. (287F) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B9A0 I/O adapter hardware error detected Table 2. Card locations can be found using the 16 character address. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (word 4). See the service documentation for instructions. see Table 2. For more on the Failing Item column entries. See the service documentation for instructions. See the service documentation for instructions. See SRC Address Formats.

An I/O adapter failure occurred.Reference codes 1310 I/O adapter resource not available. AJDGP01 I/O adapter Licensed Internal Code failed. AJDGP01 I/O adapter error. AJDGP01 I/O adapter Licensed Internal Code failed. AJDGP01 AJDG301 NTUSER IOA An I/O adapter failure occurred. IOP AJDGP01 An I/O adapter failure occurred. IOP AJDGP01 3000 3001 3006 3080 3081 3084 3087 6070 6071 6072 6075 6083 6085 6201 6202 6210 6221 6222 6223 6224 6225 6226 6227 6228 6501 6502 6530 6531 76 The INS processor error log is being filled faster than the errors are being reported to the system. logged only. IOP AJDGP01 I/O adapter Licensed Internal Code failed. IOP ANYBUS I/O adapter Licensed Internal Code failed. Check other errors reported to the system and correct them. AJDGP01 IOP I/O adapter resource not available. AJDGP01 IOP IOA MA_BRDG I/O adapter resource not available. An I/O adapter failure occurred. AJDGP01 IOP I/O adapter Licensed Internal Code failed. IOP I/O adapter Licensed Internal Code failed. AJDGP01 IOP MA_BRDG A permanent I/O processor failure occurred IOP AJDGP01 I/O processor Licensed Internal Code error AJDGP01 IOP I/O processor Licensed Internal Code error AJDGP01 I/O processor resource not available AJDG301 A permanent I/O processor failure occurred AJDGP01 IOP A permanent I/O processor failure occurred IOP AJDGP01 A permanent I/O processor failure occurred DISKIMG AJDGP01 IOP MEMORY A permanent I/O processor failure occurred AJDGP01 AJDG301 IOP I/O processor card detected device error AJDG301 AS4NTDD A HostLAN error was detected NTUSER AJDGP01 IOP Windows initiated a warm boot AJDGP01 IOP A Windows fatal error occurred IOP AJDGP01 A Windows fatal error occurred AJDGP01 IOP A Virtual SCSI error was detected NTVSCSI NTOPSYS A Virtual SCSI error was detected (1xxx) System power control network (SPCN) reference codes .

A permanent I/O processor failure occurred NTVSCSI AS4NTDD NTOPSYS AJDGP01 NTOPSYS AJDGP01 AS4NTDD NTUSER NTOPSYS AS4NTDD AS4NTDD AJDGP01 NTOPSYS NTUSER NTDEVDR AJDGP01 NTVSCSI NTOPSYS NTVSCSI AS4NTDD NTOPSYS AJDGP01 NTOPSYS AJDGP01 AS4NTDD NTUSER NTOPSYS AS4NTDD AS4NTDD AJDGP01 NTOPSYS NTUSER NTDEVDR AJDGP01 NTDEVDR NTOPSYS AJDG301 NTVSCSI AJDGP01 AJDG301 IOP AJDGP01 AJDG301 AJDGP01 NTOPSYS NTVSCSI DISKIMG IOP AJDGP01 NTLANDD NTOPSYS NTLANDD NTOPSYS AJDG301 NTDEVDR NTOPSYS AJDG301 AJDGP01 IOP IOP MA_BRDG IOP IOP 77 (1xxx) System power control network (SPCN) reference codes . A Windows fatal error occurred A Windows fatal error occurred A HostLAN error was detected A HostLAN error was detected A HostLAN error was detected An I/O adapter failure occurred. A permanent I/O processor failure occurred Multi-adapter bridge error detected.Reference codes 6532 6533 6534 6535 6538 6539 A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected 653A 653B 653C 653D 653F 6540 6541 6542 6543 6580 65B0 65B1 65B2 8301 B3B1 to B3B7 B3B8 B3B9 A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A permanent I/O processor failure occurred Licensed Internal Code error detected.

Adapter card storage error An I/O adapter failure occurred. (1xxx) System power control network (SPCN) reference codes 78 . I/O adapter hardware error detected I/O adapter hardware error detected Incompatible hardware detected. System bus See the service documentation for instructions. DIMM 0 See the service documentation for instructions. I/O adapter error. removal and installation procedures Multi-adapter bridge See the service documentation for instructions. Device Driver See the service documentation for instructions. Incompatible hardware detected. An I/O adapter failure occurred. logged only. removal and installation procedures Communications Input/Output Processor card Repair and Parts. removal and installation procedures I/O adapter card Repair and Parts. IOP MA_BRDG IOP MA_BRDG IOP IOP MEMORY IOP IOA IOP IOA MEMORY AJDGP01 IOP MEMORY IOP IOP IOP IOA MEMORY IOP AJDGP01 IOP IOA AJDGP01 IOP MA_BRDG AJDGP01 IOP IOA IOA IOP AJDGP01 AJDGP01 IOP IOA MA_BRDG Table 2. Adapter card storage error A permanent I/O processor failure occurred Incompatible hardware detected. I/O card Licensed Internal Code See the service documentation for instructions.Reference codes B3E0 B3E1 B4B0 B4B1 B4B2 B4B3 B4B4 B4B5 B4B8 B4B9 B4BC B4BE B904 B935 I/O processor detected a fault condition An I/O adapter failure occurred. I/O adapter hardware error detected An I/O adapter failure occurred. Server Storage Space Object See the service documentation for instructions. IOA Communications adapter card Repair and Parts. Failing items details Failing Item AJDG301 AJDGP01 ANYBUS AS4NTDD DISKIMG IOA IOP IOP MA_BRDG MEMORY Description Licensed Internal Code Document Description See the service documentation for instructions. B960 B961 BE00 I/O processor Licensed Internal Code error An error was detected on one of the attached adapter cards.

IOP AJDGP01 An I/O adapter failure occurred.Reference codes MEMORY MEMORY MEMORY MEMORY MEMORY NTDEVDR NTLANDD NTOPSYS NTUSER NTVSCSI Storage card DIMM in first populated DIMM position DIMM 3 DIMM 2 DIMM 1 Device Driver Device Driver Windows Operating System User-initiated action Device Driver See the service documentation for instructions. For more on the Failing Item column entries. See the service documentation for instructions. This is a recoverable error. Table 1. An I/O adapter failure occurred. then replace hardware. (2892) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 0A17 A permanent I/O processor failure occurred Failing Item IOP MA_BRDG AJDG301 AJDGP01 AJDGP01 AJDG301 IOP MA_BRDG AJDGP01 AJDG301 IOP AJDGP01 0A22 Adapter card storage error 1307 1310 I/O adapter resource not available. See the service documentation for instructions. which follows the reference code table below. Perform the VRYCFG command to Vary On the NWSD. (2892) Reference codes Find the unit reference code in the following table. If the Failing Item indicates to replace hardware. AJDGP01 79 3000 3001 3006 3080 (1xxx) System power control network (SPCN) reference codes . see Table 2. See the service documentation for instructions. If the Failing Item indicates SVCDOCS. I/O processor card error SVCDOCS Display the Service Action Log entry for this SRC. use Hardware Service Manager to re-IPL the resource. If the resource is not operable. See the service documentation for instructions. I/O adapter resource not available. then do NOT replace hardware. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. IOP AJDGP01 I/O adapter Licensed Internal Code failed. Failing items details. 1317 The INS processor error log is being filled faster than the errors are being reported to the system. See the service documentation for instructions. See the service documentation for instructions. IOP ANYBUS I/O adapter Licensed Internal Code failed. Check other errors reported to the system and correct them.

6070 6071 6072 6075 6083 6085 6201 6202 6204 6210 6221 6222 6223 6224 An I/O adapter failure occurred.Reference codes 3081 3084 I/O adapter error. I/O adapter Licensed Internal Code failed. I/O adapter Licensed Internal Code failed. I/O adapter resource not available. logged only. A permanent I/O processor failure occurred I/O processor Licensed Internal Code error I/O adapter failure due to a thermal condition I/O processor Licensed Internal Code error I/O processor resource not available A permanent I/O processor failure occurred A permanent I/O processor failure occurred A permanent I/O processor failure occurred 6225 6226 6227 6228 6501 6502 6530 6531 A permanent I/O processor failure occurred I/O processor card detected device error A HostLAN error was detected Windows initiated a warm boot A Windows fatal error occurred A Windows fatal error occurred A Virtual SCSI error was detected A Virtual SCSI error was detected 6532 6533 6534 A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected AJDGP01 IOP IOA MA_BRDG AJDGP01 AJDG301 NTUSER IOA IOP AJDGP01 AJDGP01 IOP AJDGP01 AJDGP01 IOP AJDGP01 IOP MA_BRDG IOP AJDGP01 AJDGP01 IOP IOP AJDGP01 AJDG301 AJDGP01 IOP IOP AJDGP01 DISKIMG AJDGP01 IOP MEMORY AJDGP01 AJDG301 IOP AJDG301 AS4NTDD NTUSER AJDGP01 IOP AJDGP01 IOP IOP AJDGP01 AJDGP01 IOP NTVSCSI NTOPSYS NTVSCSI AS4NTDD NTOPSYS AJDGP01 NTOPSYS AJDGP01 AS4NTDD NTUSER NTOPSYS AS4NTDD AS4NTDD AJDGP01 80 (1xxx) System power control network (SPCN) reference codes . An I/O adapter failure occurred. 3087 I/O adapter resource not available. I/O adapter Licensed Internal Code failed. I/O adapter Licensed Internal Code failed.

A permanent I/O processor failure occurred Multi-adapter bridge error detected. I/O adapter hardware error detected I/O adapter hardware error detected Incompatible hardware detected. A Windows fatal error occurred A Windows fatal error occurred A HostLAN error was detected A HostLAN error was detected A HostLAN error was detected An I/O adapter failure occurred. Incompatible hardware detected. I/O adapter hardware error detected NTOPSYS NTUSER NTDEVDR AJDGP01 NTVSCSI NTOPSYS NTVSCSI AS4NTDD NTOPSYS AJDGP01 NTOPSYS AJDGP01 AS4NTDD NTUSER NTOPSYS AS4NTDD AS4NTDD AJDGP01 NTOPSYS NTUSER NTDEVDR AJDGP01 NTDEVDR NTOPSYS AJDG301 NTVSCSI AJDGP01 AJDG301 IOP AJDGP01 AJDG301 AJDGP01 NTOPSYS NTVSCSI DISKIMG IOP AJDGP01 NTLANDD NTOPSYS NTLANDD NTOPSYS AJDG301 NTDEVDR NTOPSYS AJDG301 AJDGP01 IOP IOP MA_BRDG IOP IOP IOP MA_BRDG IOP MA_BRDG IOP IOP MEMORY IOP IOA IOP IOA 81 (1xxx) System power control network (SPCN) reference codes .Reference codes 6535 6538 6539 A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected 653A 653B 653C 653D 653F 6540 6541 6542 6543 6580 65B0 65B1 65B2 8301 B3B1 to B3B7 B3B8 B3B9 B3E0 B3E1 B4B0 B4B1 B4B2 B4B3 B4B4 A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A Virtual SCSI error was detected A permanent I/O processor failure occurred Licensed Internal Code error detected. A permanent I/O processor failure occurred I/O processor detected a fault condition An I/O adapter failure occurred.

logged only. Server Storage Space Object See the service documentation for instructions. MEMORY AJDGP01 IOP MEMORY IOP IOP IOP IOA MEMORY IOP AJDGP01 IOP IOA AJDGP01 IOP MA_BRDG AJDGP01 IOP IOA IOA IOP AJDGP01 AJDGP01 IOP IOA MA_BRDG Table 2. Storage card See the service documentation for instructions. Device Driver See the service documentation for instructions. DIMM 3 See the service documentation for instructions. I/O adapter error. IOA Communications adapter card Repair and Parts. removal and installation procedures Communications Input/Output Processor card Repair and Parts. Failing items details Failing Item AJDG301 AJDGP01 ANYBUS AS4NTDD DISKIMG IOA IOP IOP MA_BRDG MEMORY MEMORY MEMORY MEMORY MEMORY MEMORY MEMORY 82 Description Licensed Internal Code Document Description See the service documentation for instructions. removal and installation procedures I/O adapter card Repair and Parts. An I/O adapter failure occurred. Storage card See the service documentation for instructions. B960 B961 BE00 I/O processor Licensed Internal Code error An error was detected on one of the attached adapter cards. DIMM 0 See the service documentation for (1xxx) System power control network (SPCN) reference codes . DIMM in first populated DIMM position See the service documentation for DIMM 0 or DIMM 1 instructions. I/O card Licensed Internal Code See the service documentation for instructions. DIMM 2 See the service documentation for instructions. removal and installation procedures Multi-adapter bridge See the service documentation for instructions. Adapter card storage error An I/O adapter failure occurred.Reference codes B4B5 B4B8 B4B9 B4BC B4BE B904 B935 An I/O adapter failure occurred. System bus See the service documentation for instructions. Storage card See the service documentation for instructions. Adapter card storage error A permanent I/O processor failure occurred Incompatible hardware detected.

Reference codes

MEMORY NTDEVDR NTLANDD NTOPSYS NTUSER NTVSCSI SVCDOCS

DIMM 1 Device Driver Device Driver Windows Operating System User-initiated action Device Driver Customer engineer directed to system problem analysis

instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions.

(40xx) Model ESCALA PL 245T/R reference (error) codes

The system detected a power, voltage, or thermal problem. Table 1. (40xx) Model ESCALA PL 245T/R reference (error) codes Reference Code Description/Action Perform all actions before exchanging Failing Items Power supply failure Replace the power supply. (For more information, see Removing and replacing parts in the model ESCALA PL 245T/R.) VRM 1 failure VRM 2 failure VRM ECID setting The system detected a voltage problem Unfused board (ECID) The system detected a battery failure Replace the battery. (For more information, see Removing and replacing parts in the model ESCALA PL 245T/R.) Warning temperature reached Do the following: 1. Check the airflow to the fans, and correct any problems that you find. 2. Look in the operating system error log for error codes that indicate a problem with a fan. Take the appropriate action for the error codes that you find. Critical temperature reached The system will power itself down to standby when a critical temperature is reached. If this occurs, do the following: Failing Item

40100100 40100111 40100122 40100133 40100134 40100144 40110111

VRMOD SYSBKP2 VRMOD SYSBKP2 VRMOD SYSBKP2 VRMOD SYSBKP2 SYSBKP2

40200111

40200222

(1xxx) System power control network (SPCN) reference codes

83

Reference codes

1. Check the connections on the fan, and correct any problems that you find. 2. Verify that the airflow to the fan is not blocked, and correct any problems that you find. A fan was failing but recovered 40210100 Informational message. A replacement fan was hot-plugged in place of a failing fan. The system will clear the rollup card LED. A fan failed Look at the rollup LED card to identify the fan that failed, then do the following: 1. Check the connections on the fan, and correct any problems that you find. 2. Verify that the airflow to the fan is not blocked, and correct any problems that you find. 3. If you find no obvious problems, replace the fan. (For more information, see Removing and replacing parts in the model ESCALA PL 245T/R.) Loss of rollup LED card Reseat the rollup LED card. You can reseat the rollup LED card while the system is powered on, but the system might reset and reboot.

40210111

40500111

(432x, 660x, 671x, 673x) Disk unit reference codes

If the error is reported on the control panel, the unit reference code is characters 5 through 8 of the top 16 character line of function 11. If the error is reported on the console, the unit reference code is the 4 rightmost characters of word 1. Find the unit reference code in the following table. If the failing item is a disk unit, go to Start Disk Service.

Attention: The 673x is a read cache. Perform all actions required for 673x as a disk drive and logic card except where separate 673x cache instructions are provided.

For more on the Failing Item column entries, see Table 2. Disk unit failing items details, which follows the reference code table below. Table 1. (432x, 660x, 671x, 673x) Disk unit reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 102E Out of alternate sectors for disk storage 3002 Addressed device failed to respond to selection Failing Item DISKDRV DISKDRV STORIOA BACKPLN FI01106 FI01140

84

(1xxx) System power control network (SPCN) reference codes

Reference codes

3010

Disk device returned wrong response to IOA

3020

Storage subsystem configuration error If an MES is being installed, verify the configuration.

DISKDRV STORIOA FI01140 FI01141 DISKDRV FI01106 STORIOA FI01140

3029 3100

A device replacement has occurred No action required. This reference code is logged for information only. Tape/optical or disk bus interface error occurred Perform DSKIP03. DISKDRV STORIOA FI01106 FI01140 DISKDRV STORIOA FI01106 FI01140 STORIOA DISKDRV FI01106 FI01140 SVCDOCS

3109

IOA timed out a disk command

3110

Disk bus interface error occurred Perform DSKIP03.

3130

Device Licensed Internal Code The device is not supported with the level of code currently on the system. Contact your next level of support. Device or IOA Licensed Internal Code The device does not support a needed attribute and is running with degraded performance. Contact your next level of support. Disk sector read error No action required. This reference code is logged for information only. Temporary disk data error A disk unit service action is recommended only if the Service Action Log contains an entry for this reference code. For more information, see Using the Service Action Log. Device format error If the disk has not been formatted by the system, initialize and format the disk. See Work with disk unit recovery. System log entry only. No service action required. Data compression failure Contact your next level of support. Compressed device and compression IOA are not compatible Data compression warning Disk motor problem Disk media format not valid Disk device problem Disk sector read error

3131

SVCDOCS

7000 7001

DISKDRV DISKDRV

7003

7004 7050 7051 7052 FFF2 FFF3 FFF4 FFF5

SVCDOCS CMPRES1 SVCDOCS DISKDRV DISKDRV DISKDRV STORIOA DISKDRV

FFF6

A disk unit service action is recommended only if the Service Action Log contains an entry for this reference code. For more information, see Using the Service Action Log. Disk device detected recoverable error DISKDRV A disk unit service action is recommended only if the Service Action Log contains an entry for this reference code. For more information, see Using the Service Action Log.

(1xxx) System power control network (SPCN) reference codes

85

Reference codes

FFF7 FFF8 to FFF9

Temporary disk data error No action required. This reference code is logged for information only. Temporary disk data error

DISKDRV DISKDRV

FFFA

FFFB FFFE

A disk unit service action is recommended only if the Service Action Log contains an entry for this reference code. For more information, see Using the Service Action Log. Temporary disk bus error DISKDRV STORIOA A disk unit service action is recommended only if the Service Action Log FI01140 contains an entry for this reference code. For more information, see FI01141 Using the Service Action Log. BACKPLN SCSI bus reset occurred DISKDRV STORIOA A disk unit service action is recommended only if the Service Action Log FI01106 FI01140 contains an entry for this reference code. For more information, see Using the Service Action Log. No action required. This reference code is logged for information only. Temporary disk bus error

Table 2. Disk unit failing items details Failing Item 08F5352 08F5361 17G2504 21F1511 21F1512 21F1512 21F1513 21F1514 21F1519 21F1530 21F1687 21F1688 21F1689 21F2070 21F3986 21F4383 21F4493 21F4579 21F4863
86

Description Token-ring network adapter

Document Description Repair and Parts; removal and installation procedures Communications input/output processor card Repair and Parts; removal and installation procedures Tape Unit Repair and Parts; removal and installation procedures Internal power cable Repair and Parts; removal and installation procedures Internal power cable Repair and Parts; removal and installation procedures Internal power cable Repair and Parts; removal and installation procedures Internal signal cable Repair and Parts; removal and installation procedures Internal power cable Repair and Parts; removal and installation procedures Internal signal cable Repair and Parts; removal and installation procedures Card enclosure Repair and Parts; removal and installation procedures Diskette adapter card Repair and Parts; removal and installation procedures Multiple function I/O processor card Repair and Parts; removal and installation procedures Multiple function I/O processor card Repair and Parts; removal and installation procedures Bus cable Repair and Parts; removal and installation procedures Tape I/O processor card Repair and Parts; removal and installation procedures Multiple function I/O processor card Repair and Parts; removal and installation procedures Ethernet controller card Repair and Parts; removal and installation procedures Disk drive logic card Repair and Parts; removal and installation procedures Magnetic storage device IOP card
(1xxx) System power control network (SPCN) reference codes

Reference codes

21F4867 21F4868 21F4869 21F4882 21F4882 21F5620 21F5620 21F5650 21F5680 21F5772 21F5774 21F5774 21F5861 21F8566 21F8633 21F8719 21F8872 21F8890 21F9208 21F9215 21F9586 21F9907 21F9937 21F9951 21F9987 2452557 26F5028 375892 4234002 46F4115 46F4239

Communication adapter Communication adapter Token-ring controller card Diskette adapter card Diskette adapter card Disk unit power regulator Disk unit power regulator AC Module AC Module Control panel Cable assembly External signal cable Tape Unit Tape Unit Tape Unit Tape Unit Cable Carrier D/SE Module ISDN adapter card Power regulator card Cable assembly Cable assembly Cable assembly Tape Unit Tape unit IOP card Fan Communication adapter Power cord; U.S.A., Asia-Pacific group, Americas group Test diskette (8 inch) Ethernet network adapter card Token-ring network adapter

Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures 9346 Service Guide; Installation and Removal, SY31-0688 Repair and Parts; removal and installation procedures

System operation information Repair and Parts; removal and installation procedures

(1xxx) System power control network (SPCN) reference codes

87

Reference codes

55F5199 55F5209 59X4718 59X4723 59X4723 59X4723 59X4819 6369759 6369881 6462385 6495268 72X5631 72X5631 72X5631 72X6361 72X6374 72X6385 72X6386 72X6387 72X6388 72X6389 72X6390 72X6391 73F8987 73F8994 73F9138 73F9139 73F9166 73F9193 73F9232 73F9244 73F9267
88

Repair and Parts; removal and installation procedures Disk drive logic card Repair and Parts; removal and installation procedures Disk drive and logic card Repair and Parts; Recovery Procedures Communications input/output processor card Repair and Parts; removal and installation procedures Tape I/O processor card Repair and Parts; removal and installation procedures Token-ring network adapter Repair and Parts; removal and installation procedures Tape unit IOP card Repair and Parts; removal and installation procedures Multiple function I/O processor card Repair and Parts; removal and installation procedures Test diskette (5-1/4 inch) System operation information Diskette unit Repair and Parts; removal and installation procedures Power cord; Europe, Mid-East, Asia External signal cable 9346 Service Guide; Installation and Removal, SY31-0688 Terminating plug 9346 Service Guide; Installation and Removal, SY31-0688 Terminating plug Repair and Parts; removal and installation procedures Terminating plug Repair and Parts; removal and installation procedures Diskette unit Repair and Parts; removal and installation procedures Work station attachment Repair and Parts; removal and installation procedures Magnetic storage device IOP card Repair and Parts; removal and installation procedures Diskette adapter card Repair and Parts; removal and installation procedures Communications I/O processor card Repair and Parts; removal and installation procedures Communications adapter card Repair and Parts; removal and installation procedures Multiple interface adapter Repair and Parts; removal and installation procedures Communications adapter card Repair and Parts; removal and installation procedures Token-ring network adapter Repair and Parts; removal and installation procedures Disk drive and logic card Repair and Parts; Recovery Procedures Disk drive logic card Repair and Parts; removal and installation procedures Planar board Repair and Parts; removal and installation procedures Planar board Repair and Parts; removal and installation procedures Planar board Repair and Parts; removal and installation procedures Power regulator card Repair and Parts; removal and installation procedures Cable assembly Repair and Parts; removal and installation procedures Disk unit power regulator Repair and Parts; removal and installation procedures ASCII work station IOP card Repair and Parts; removal and installation procedures
(1xxx) System power control network (SPCN) reference codes

Reference codes

73F9290 73F9290 73F9345 73F9393 74F1541 74F1542 74F1543 74F1544 74F1649 74F1760 74F2201 74F2232 79X3795 8266352 85F7295 85F7305 85F7405 85F7418 85F7646 85F7846 85F9785 85F9840 85F9845 92X3030 92X3080 92X4041 92X4044 92X4091 92X4143 92X6551 92X7512

Control panel Control panel Tape Unit Tape Unit Card enclosure Card enclosure Card enclosure Card enclosure Tape Unit DC Bulk Module Multiple function I/O processor card Multiple function I/O processor card Terminating plug Power supply Multiple function I/O processor card Multiple function I/O processor card Base power supply Cable assembly Magnetic storage device IOP card Terminating plug Control panel Internal signal cable Internal power cable Feature power supply Disk unit power regulator Diskette unit Cable assembly Cable assembly Planar board Planar board Flex cable

Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures 9346 Service Guide; Installation and Removal, SY31-0688 Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures 9346 Service Guide; Installation and Removal, SY31-0688
89

(1xxx) System power control network (SPCN) reference codes

Reference codes

92X7514 92X7515 92X7516 93X0901 93X0911 93X2520 93X2701 93X2730 93X2777 A0B00E1 AJDG301 AJEDA00 AJEDA00 AJEH901 AJGJQ01 AJSLC01 AJSLC01 BACKPLN CMPRES1 DEVTERM DISKDRV DISKDRV DISKDRV DISKDRV DISKDRV DISKDRV DISKDRV DISKLC DISKLC DISKLC DISKLC DISKLC DISKLC DISKLC DISKTRY

Internal tape unit signal cable Internal signal cable Internal power cable Disk drive logic card Disk drive and logic card Disk drive and logic card I/O processor card 9346 IOP card I/O processor card Licensed Internal Code for programmable tape unit Vertical Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code Card enclosure or backplane Compressed device and compression IOA are not compatible Device terminator Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive and logic card Disk drive logic card Disk drive logic card Disk drive logic card Disk drive logic card Disk drive logic card Disk drive logic card Disk drive logic card Disk unit tray

9346 Service Guide; Installation and Removal, SY31-0688 9346 Service Guide; Installation and Removal, SY31-0688 9346 Service Guide; Installation and Removal, SY31-0688 Repair and Parts; removal and installation procedures Repair and Parts; Recovery Procedures Repair and Parts; Recovery Procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Repair and Parts; removal and installation procedures Service Functions; APAR or LICTR Service Functions; APAR or LICTR Service Functions; APAR or LICTR Service Functions; APAR or LICTR Service Functions; APAR or LICTR Service Functions; APAR or LICTR Service Functions; APAR or LICTR Service Functions; APAR or LICTR See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions.
(1xxx) System power control network (SPCN) reference codes

90

Reference codes

DISKTRY DISKTRY DISKTRY DISKTRY DISKTRY DISKTRY MFGDMED MFGTCAR MFGTFOR MFGTMED STORIOA SVCDOCS UFGUSER

Disk unit tray

See the service documentation for instructions. Disk unit tray See the service documentation for instructions. Disk unit tray See the service documentation for instructions. Disk unit tray See the service documentation for instructions. Disk unit tray See the service documentation for instructions. Disk unit tray See the service documentation for instructions. Defective diskette System operation information Defective tape or damaged cartridge System operation information The data format is incorrect; the tape cannot System operation information be read Defective removable media System operation information Storage I/O adapter See the service documentation for instructions. Customer engineer directed to system See the service documentation for problem analysis instructions. System Operator/User System operation information

(4758) Reference codes

Find the unit reference code in the following table. For more on the Failing Item column entries, see Table 2. Failing items details, which follows the reference code table below. Table 1. (4758) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B990 I/O adapter hardware error detected Failing Item IOA FI00130 IOP MA_BRDG IOA FI00130 IOP CARDTMP

B991 B992

Tampering of cryptographic card suspected. Operating voltage and/or temperature range limits exceeded. Correct any conditions in the physical environment which may have caused the voltage and/or temperature out-of-range error on the 4758 adapter card. After the conditions have been corrected, vary off and then vary back on the 4758 device description associated with the 4758 adapter card.

Table 2. Failing items details Failing Item CARDTMP IOA IOP MA_BRDG Description Operating voltage or temperature range limit exceeded I/O adapter card I/O processor card Multi-adapter bridge Document Description See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions.

(1xxx) System power control network (SPCN) reference codes

91

Processor 0 failed to initialize SYSBKP2 On a two-way system. (4B20) Model ESCALA PL 245T/R reference (error) codes Reference Code 4B200111 Description/Action Perform all actions before exchanging Failing Items A checkstop occurred Failing Item SYSBKP2 4B200120 If this error code only occurs once. this error implies that one processor is still functioning. Table 1. Correct any conditions in the physical environment which may have caused the voltage and/or temperature out-of-range error on the 4764 adapter card. At some point. (4764) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B990 I/O adapter hardware error detected B991 B992 Tampering of cryptographic card suspected. this error implies that one processor is still functioning. and the system will continue to operate in a degraded mode. I/O adapter card See the service documentation for instructions. Table 2. and the system will continue to operate in a degraded mode. see Table 2. Operating voltage or temperature range limit See the service documentation for exceeded instructions. vary off and then vary back on the 4764 device description associated with the 4764 adapter card. you should replace the system backplane. At some point. If this error code persists. Failing Item IOA AJDG301 IOA AJDG301 CARDTMP (4B20) Model ESCALA PL 245T/R reference (error) codes The system detected a problem with a processor. you should replace the system backplane. Operating voltage and/or temperature range limits exceeded. For more on the Failing Item column entries. which follows the reference code table below. 4B200121 92 (1xxx) System power control network (SPCN) reference codes .Reference codes (4764) Reference codes Find the unit reference code in the following table. Failing items details Failing Item AJDG301 CARDTMP IOA Description Licensed Internal Code Document Description See the service documentation for instructions. Table 1. After the conditions have been corrected. it is not a problem. Failing items details. Processor 1 failed to initialize SYSBKP2 On a two-way system. replace the system backplane.

which follows the reference code table below. Failing items details. (5700. 2. which follows the reference code table below. The unit address portion of the card address is characters 1 through 8 of the bottom 16 character line of function 11 (Word 4). APAR or LICTR See the service documentation for instructions. For more on the Failing Item column entries. See the service documentation for instructions. see Table 2.Reference codes 4B200122 No processors were detected SYSBKP2 (5700.Input/Output Processor Licensed Internal Code Licensed Internal Code Multi-adapter bridge Document Description Service Functions. 5701) Reference codes 1. Table 1. See SRC Address Formats. 93 Failing Item AJDGP01 IOA AJDGP01 (1xxx) System power control network (SPCN) reference codes . 5707) Reference codes Find the unit reference code in the following table. Look at the last 8 characters of the top 16 character line of function 12 (word 3). Find the unit reference code in the following table. 5707) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items A001 I/O adapter Licensed Internal Code error detected B9B0 I/O adapter hardware error detected Table 2. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). These 8 characters are the direct select address of the card (BBBBCcbb). (5706. Failing items details. see Table 2. For more on the Failing Item column entries. These 4 characters are the unit reference code. 5701) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items A001 I/O adapter Licensed Internal Code error detected B9A0 I/O adapter hardware error detected Failing Item AJDGP01 FI00719 FI00718 AJDGP01 MA_BRDG FI00719 LICCODE MA_BRDG B9B0 I/O adapter hardware error detected Table 2. Card locations can be found using the 16 character address. Failing items details Failing Item AJDGP01 Description I/O card Licensed Internal Code Document Description See the service documentation for instructions. Failing items details Failing Item AJDGP01 LICCODE MA_BRDG Description LIC . (5706. Table 1. 3.

see Table 2. then replace the I/O adapter. A recoverable error occurred AUXIOA A permanent failure occurred AUXIOA ANYBRDG Licensed Internal Code error PTFSRCH AUXIOA A permanent failure occurred PTFSRCH AUXIOA I/O adapter card error SVCDOCS Display the Service Action Log entry for this SRC. then do NOT replace the I/O adapter. IOA detected recoverable SCSI bus error No action is required. Interface error Error occurred on SCSI bus 1. If the I/O Processor is not operable and disk units are attached. the unit reference code is the 4 rightmost characters of word 1. If the error is reported on the console. Table 1. (5708. IOA detected recoverable SCSI resource error No action is required. For more on the Failing Item column entries. IOA detected recoverable SCSI bus error An error occurred on SCSI bus 1. This is a recoverable error. 575B) Reference codes If the error is reported on the control panel. This reference code is logged for information only. SCSI resource error A permanent cache battery pack failure occurred Impending cache battery pack failure IOA detected recoverable SCSI bus error An error occurred on SCSI bus 0. Failing items details. (5708. the unit reference code is characters 5 through 8 of the top 16 character line of function 11. 574F. Perform the following for the I/O processor that the I/O adapter is attached to: 1. This reference code is logged for information only. 574F. If the Failing Item indicates I/O adapter. No action is required. which follows the reference code table below. 575B) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 3006 System bus error 3100 3101 3400 8008 8009 8130 Interface error Error occurred on SCSI bus 0. Other resources attached 94 (1xxx) System power control network (SPCN) reference codes Failing Item AUXIOA ANYBRDG IOP AUXCBL AUXIOA PRIMIOA AUXCBL AUXIOA PRIMIOA AUXCBL PRIMIOA CACHBAT AUXIOA CACHBAT 8131 8140 8141 8145 8150 8151 8155 to 8156 8157 .Reference codes IOA Communications adapter card See the service documentation for instructions. If the Failing Item indicates SVCDOCS. No action is required. use Hardware Service Manager to re-IPL the IOP. This reference code is logged for information only. Find the unit reference code in the following table. This reference code is logged for information only.

See the service documentation for instructions. See the service documentation for instructions.Reference codes to the IOP may then need to be Varied On. See the service documentation for instructions. See the service documentation for instructions. See the service documentation for instructions. Link from IOA to auxiliary cache IOA went non-operational No service action required. See the service documentation for instructions. Failing items details Failing Item AJDGP01 ANYBRDG ANYBUS AUXCBL AUXIOA BACKPLN CACHBAT DEVBPLN DEVTERM IOP PCIBUS PRIMIOA PTFSRCH STORIOA SVCDOCS USER Description I/O processor Licensed Internal Code System I/O bus or any attached card IOP card bus error Cable assembly I/O adapter card Card Enclosure or Planar Board Cache battery pack Device backplane Terminating plug I/O processor card Any PCI card on the PCI bus Storage I/O adapter Licensed Internal Code Storage I/O adapter Customer engineer directed to system problem analysis System Operator/User Document Description Service Functions. Write cache data is available for attached storage IOA No service action required. See the service documentation for instructions. If disk units are not attached. APAR or LICTR See the service documentation for instructions. Disconnected. See the service documentation for instructions. See the service documentation for instructions. perform the VRYCFG RESET(*YES) command to reset the IOP and Vary On attached resources. See the service documentation for instructions. See the service documentation for instructions. incompatible. 95 (1xxx) System power control network (SPCN) reference codes . I/O adapter detected recoverable error SVCDOCS AUXIOA ANYBRDG 8300 8301 8302 9055 9071 9072 9073 FF3D AUXIOA ANYBRDG PTFSRCH PTFSRCH AUXIOA SVCDOCS AUXIOA Table 2. or non-operational storage IOA Perform IOPIP41. See the service documentation for instructions. Link from IOA to auxiliary cache IOA went operational No service action required. See the service documentation for instructions. See the service documentation for instructions. IOA hardware or PCI bus error Not valid condition in Licensed Internal Code Missing Licensed Internal Code Ensure that the code necessary to support this I/O adapter is loaded. 2.

571B. 3121 SVCDOCS 96 (1xxx) System power control network (SPCN) reference codes . perform IOPIP17. Interface error FI01107 STORIOA Error occurred on SCSI bus 2. FI01140 BACKPLN Perform IOPIP13. the unit reference code is the 4 rightmost characters of word 1. 571F. If the error is reported on the console. 573D. Interface error FI01107 STORIOA Error occurred on SCSI bus 3. To correct or isolate a possible user error STORIOA or configuration error. FI01140 BACKPLN Perform IOPIP13. Remove the device. SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 3. Bus is not operational Adding a device to SCSI bus 1 of the I/O Adapter caused the bus to become not operational. Interface error FI01107 STORIOA Error occurred on SCSI bus 0. FI01140 BACKPLN Perform IOPIP13.Reference codes (571A. Remove the device. Find the unit reference code in the following table. which follows the reference code table below. see Table 2. 571B. 573E. 57FF) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 3000 A permanent failure occurred 3006 3020 Failing Item 3021 3022 3023 3100 3101 3102 3103 3120 FI01101 ANYBRDG System bus error FI01101 ANYBRDG PTFSRCH SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 0. perform IOPIP17. For more on the Failing Item column entries. 571E. To correct or isolate a possible user error STORIOA or configuration error. Interface error FI01107 STORIOA Error occurred on SCSI bus 1. 573E. 571F. the unit reference code is characters 5 through 8 of the top 16 character line of function 11. Failing items details. perform IOPIP17. SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 1. FI01140 BACKPLN Perform IOPIP13. Table 1. Bus is not operational SVCDOCS Adding a device to SCSI bus 0 of the I/O Adapter caused the bus to become not operational. perform IOPIP17. (571A. To correct or isolate a possible user error STORIOA or configuration error. To correct or isolate a possible user error STORIOA or configuration error. 573D. SCSI bus configuration error USER FI01107 Error occurred on SCSI bus 2. 571E. 57FF) Reference codes If the error is reported on the control panel.

Correct the SCSI bus 1 configuration. Correct the SCSI bus 0 configuration. Bus is operational SVCDOCS 3123 SVCDOCS 3140 3141 3142 3143 3150 This reference code and the 3123 reference code that occurred before it require no service action because SCSI bus 3 is now operational. Bus is operational This reference code and the 3122 reference code that occurred before it require no service action because SCSI bus 2 is now operational. Device error 3151 SVCDOCS 3200 3202 FI01105 STORIOA MEDIA SVCDOCS 3400 3401 3501 3601 8008 8009 8100 8130 FI02112 STORIOA NOTE: If external devices are attached check EXTSCSI and DEVTERM FI01106 first. A tape/CD or disk device reported a failure Storage subsystem configuration error The device is not supported in the current configuration. System log entry only. SVCDOCS SCSI bus configuration error Internal and external SCSI cables are connected to SCSI bus 0 at the same time. IOA detected recoverable device bus error 97 8131 8132 (1xxx) System power control network (SPCN) reference codes . No action is required. Remove the device.Reference codes 3122 Bus is not operational Adding a device to SCSI bus 2 of the I/O Adapter caused the bus to become not operational. Bus is operational This reference code and the 3120 reference code that occurred before it require no service action because SCSI bus 0 is now operational. An I/O processor might be required. SCSI bus configuration error Internal and external SCSI cables are connected to SCSI bus 1 at the same time. IOA detected recoverable device bus error An error occurred on SCSI bus 1. Bus is not operational Adding a device to SCSI bus 3 of the I/O Adapter caused the bus to become not operational. No action is required. FI01140 Device backplane problem DEVBPLN Licensed Internal Code error FI01105 PTFSRCH The device type is either unsupported or the code has not been loaded to support it. This reference code is logged for information only. Remove the device. no service action required A permanent cache battery pack failure occurred CACHBAT STORIOA Impending cache battery pack failure CACHBAT Licensed Internal Code error PTFSRCH STORIOA IOA detected recoverable device bus error An error occurred on SCSI bus 0. This reference code is logged for information only. Bus is operational This reference code and the 3121 reference code that occurred before it require no service action because SCSI bus 1 is now operational.

no service action required Device error FI01105 STORIOA Device configuration error SVCDOCS Perform IOPIP33. IOA detected recoverable device error No action is required. IOA detected recoverable device bus error No action is required. Perform IOPIP21. Array not functional due to present hardware configuration. Cache data belongs to devices other than those attached Perform IOPIP32. Perform IOPIP20. Disk unit is not supported at its physical location. This reference code is logged for information only. Array not functional due to present hardware configuration. Licensed Internal Code error PTFSRCH System log entry only. IOA detected recoverable device bus error An error occurred on SCSI bus 3. This reference code is logged for information only. No action is required. Call your next level of support for assistance Cache data associated with attached devices cannot be found Perform IOPIP31. Perform IOPIP22. Device error Perform IOPIP16. No action is required. This reference code is logged for information only. FI01105 STORIOA FI01140 BACKPLN FI01106 SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS SVCDOCS 8140 8141 8145 8146 8150 8151 8155 to 8156 8300 8301 8302 8400 8404 9000 9001 9002 9008 9009 9010 9011 9020 to 9021 9022 to 9024 9025 9026 9027 98 I/O card does not support functions expected by devices Perform IOPIP25. This reference code is logged for information only.Reference codes 8133 An error occurred on SCSI bus 2. Array not functional due to present hardware configuration. (1xxx) System power control network (SPCN) reference codes . Perform IOPIP22. A recoverable error occurred STORIOA Disk device detected recoverable error FI01105 A permanent failure occurred STORIOA ANYBRDG Licensed Internal Code error PTFSRCH STORIOA A permanent failure occurred PTFSRCH STORIOA IOA hardware error or PCI bus error STORIOA ANYBRDG PTFSRCH Not valid condition in Licensed Internal Code PTFSRCH STORIOA Missing Licensed Internal Code SVCDOCS STORIOA Ensure that the code necessary to support this I/O adapter is loaded. Array not functional due to present hardware configuration.

FI02112 SVCDOCS 9030 9031 9032 FI02112 SVCDOCS 9040 9041 9042 9050 9051 Perform IOPIP21. SVCDOCS SVCDOCS 9054 If you cannot get to SST or DST. Link from IOA to auxiliary cache IOA went operational 99 9071 (1xxx) System power control network (SPCN) reference codes . perform a type D IPL from removable media. Array protection temporarily suspended No action required. IOA resources not available due to previous problems Take action on other reference codes which have surfaced.Reference codes 9028 Perform IOPIP34. SVCDOCS 9029 902F Reduce the number of arrays on this I/O adapter. Protection will be automatically restarted. perform the action indicated for the 9054 reference code. Contact your next level of support. IPL the system to DST. Either move all the devices in an array to another I/O adapter that supports arrays. PTFSRCH NEXTLVL SVCDOCS SVCDOCS 9052 9053 Otherwise. Array protection temporarily suspended No action required. but the disk unit should be replaced. Use the 90xx entry that occurred at the same time as this reference code as the starting point for this problem. If so. Array addendum Product Activity Log entry This entry contains additional array information for 90xx reference codes when the array contains more than 10 members. and cannot perform a type A or B IPL. perform a type D IPL from removable media. SVCDOCS Contact your next level of support. Perform IOPIP30. A disk unit in a RAID array is missing or failed The array is still protected. IOA resources not available due to previous problems SVCDOCS Power off the system and remove all new or replacement disk units. Look for Product Activity Log entries for other reference codes and take action on them. Array no longer protected due to missing or failed disk unit Perform IOPIP21. Cache data exists for device that has been modified. or stop an array on this I/O adapter. Protection will be automatically restarted. perform IOPIP27. Required cache data cannot be located for a disk unit. a 9054 reference code may appear in the product activity log. If you cannot perform a type A or B IPL. Incorrect hardware configuration change has been detected. Background array parity check detected and corrected errors Call your next level of support to report the problem. An array parity error has been detected and corrected Call your next level of support to report the problem. Look for Product Activity Log entries for other reference codes and take action on them. Cache data exists for a missing or failed device If all configured units are missing. Incorrect hardware configuration change has been detected.

System log entry only. Re-IPL the system. See the service documentation for instructions. APAR or LICTR Service Functions. This reference code is logged for information only. Licensed Internal Code error PTFSRCH Ask your next level of support for assistance. Incompatible or non-operational auxiliary cache IOA attached Perform IOPIP40. See the service documentation for instructions. (1xxx) System power control network (SPCN) reference codes 100 . SVCDOCS FI01105 STORIOA FI01105 STORIOA FI01140 BACKPLN FI01106 SVCDOCS 9090 Disk unit has been modified after the last known status. Perform IOPIP26. If any reference codes are surfaced. See the service documentation for instructions. APAR or LICTR See the service documentation for instructions. contact your next level of support. contact your next level of support.Reference codes 9072 9073 9081 9082 No service action required. Incorrect hardware configuration change has been detected. Device error Device error Perform IOPIP16. go to List of system reference codes and use the new reference code as the entry point to the problem. See the service documentation for instructions. Re-IPL the system. If any reference codes are surfaced. no service action required SVCDOCS No action is required. no service action required System log entry only. Link from IOA to auxiliary cache IOA went non-operational No service action required. I/O adapter detected a recoverable error Recoverable system bus error STORIOA ANYBRDG STORIOA ANYBRDG PTFSRCH Table 2. go to List of system reference codes and use the new reference code as the entry point to the problem. SVCDOCS 9092 9902 C000 C402 FF3D FF6D If you cannot resolve the problem. See the service documentation for instructions. 9091 If you cannot resolve the problem. APAR or LICTR Service Functions. Disk unit requires initialization before use. Failing items details Failing Item AJDG301 AJDGP01 AJDGP01 ANYBRDG ANYBUS BACKPLN CACHBAT CACHE CMPRES1 Description Vertical Licensed Internal Code I/O processor Licensed Internal Code I/O card Licensed Internal Code System I/O bus or any attached card IOP card bus error Card Enclosure or Planar Board Cache battery pack Cache adaptor card Compressed device and compression IOA are not compatible Document Description Service Functions.

System Operator/User See the service documentation for instructions. which follows the reference code table below. see Table 2. Defective media See the service documentation for instructions. (573A. Any PCI card on the PCI bus See the service documentation for instructions. For more on the Failing Item column entries. (573A. which follows the reference code table below. 576A) Reference codes Find the unit reference code in the following table. For more on the Failing Item column entries. See the service documentation for instructions. Failing items details Failing Item AJDG301 IOA Description Licensed Internal Code Communications adapter card Document Description See the service documentation for instructions. Terminating plug See the service documentation for instructions. (573B) Reference codes (1xxx) System power control network (SPCN) reference codes 101 . See the service documentation for instructions. Licensed Internal Code See the service documentation for instructions. 576A) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B9B0 I/O adapter hardware error detected Table 2. Customer engineer directed to system See the service documentation for problem analysis instructions.Reference codes CTLPNL DEVBPLN DEVTERM FCIOA IOACNFG IOP MA_BRDG MEDIA NEXTLVL OPT_CLN PCIBUS PTFSRCH STORIOA SVCDOCS USER Control panel. Failing items details. Fibre Channel IOA See the service documentation for instructions. see Table 2. Failing Item IOA AJDG301 (573B) Reference codes Find the unit reference code in the following table. Call your next level of support for assistance See the service documentation for instructions. Failing items details. Table 1. Storage I/O adapter See the service documentation for instructions. I/O processor card See the service documentation for instructions. or the interface to the Control panel Device backplane See the service documentation for instructions. Multi-adapter bridge See the service documentation for instructions. Configuration error See the service documentation for instructions. Fiber optic cleaning kit See the service documentation for instructions. Table 1.

I/O adapter hardware error detected I/O adapter hardware error detected I/O adapter hardware error detected Failing Item IOA FI00722 AJDG301 FI00722 UJE40 IOA IOA AJDG301 AJDG301 IOA IOA AJDG301 Table 2. see Table 2. Network or Network devices Document Description See the service documentation for instructions. See the service documentation for instructions. Failing items details Failing Item AJDG301 IOA UJE40 Description Licensed Internal Code Communications adapter card Network Termination. which follows the reference code table below. Network or Network devices Document Description See the service documentation for instructions. Failing items details.Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items A6D9 I/O adapter hardware error detected A6E3 B100 B200 B300 Ethernet adapter or network device cabling error. (573C) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items A6D9 I/O adapter hardware error detected A6E3 B100 B200 B300 Ethernet adapter or network device cabling error. Table 1. For more on the Failing Item column entries. Communications Configuration 102 (1xxx) System power control network (SPCN) reference codes . I/O adapter hardware error detected I/O adapter hardware error detected I/O adapter hardware error detected Failing Item IOA FI00722 AJDG301 FI00722 UJE40 IOA IOA AJDG301 AJDG301 IOA IOA AJDG301 Table 2. See the service documentation for instructions. Failing items details Failing Item AJDG301 IOA UJE40 Description Licensed Internal Code Communications adapter card Network Termination. Communications Configuration (573C) Reference codes Find the unit reference code in the following table.

6331. (632x. 6333. 6330. Search the problem log (WRKPRB) for a recent optical storage entry that may assist in analyzing the problem. If the system is available. Find the unit reference code in the following table. 6337) Optical storage unit reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items C000 System log entry only. For more on the Failing Item column entries. SCSI selection or reselection timeout occurred FI00870 FI01106 FI01112 MEDIA FI01140 FI01141 DEVTERM CDTRAY Undefined sense key returned by device FI00870 Device internal configuration error FI00870 SCSI bus command error occurred FI00870 FI01106 FI01112 MEDIA FI01140 FI01141 DEVTERM CDTRAY SCSI command timeout occurred FI00870 FI01106 FI01112 MEDIA FI01140 FI01141 DEVTERM CDTRAY Unexpected device condition recovered 103 (1xxx) System power control network (SPCN) reference codes . This reference code is logged for information only. 6336. Table 1. Does the operation complete successfully? ♦ Yes: The original optical media may be defective. no service action required C002 Failing Item C010 C020 C100 C110 C210 No action is required. or the problem may be intermittent.Reference codes (632x. This ends the procedure. Perform the following: 1. The WRKPRB entry will provide a unit reference code that can be found in the following table. 3. 6336. Notes: 1. 6331. use online diagnostic tests when possible. Optical storage unit failing items details. 6333. ♦ No: Look at the 4 rightmost characters of the Data display for word 1. attempt the failing operation again with an optical media that is known to be good. 6337) Optical storage unit reference codes An optical storage unit failure occurred. which follows the reference code table below. see Table 2. Attempt the failing operation again with the original optical media to verify. If the system is available. 6330. Use the Hardware Service Manager (HSM) verify function (via DST or SST) and verify that the unit is operating correctly. These 4 characters are the unit reference code. 2.

an 'out of spare sectors' condition was encountered. Media or device error occurred MEDIA FI00870 Perform the following: 1. C302 Clean the optical drive and the media contained in the drive. This reference code is logged for information only. C300 No action is required. If this does not correct the problem. Attempt the failing operation again. C303 C333 Clean the optical drive and the media contained in the drive. If the operation fails again with the same reference code. Recovered from device not ready . Media or device error occurred Dust check encountered. This reference code is logged for information only.Reference codes The device successfully recovered from a temporary error. Clean the disk. No action is required. This reference code is logged for information only. This reference code is logged for information only. This reference code is logged for information only.Start Unit issued The device successfully recovered from a temporary error. 2. Verify that the disk has a format that is given support. Recovered SCSI bus error The device successfully recovered from a temporary error. 2. clean the disk and attempt the failing operation again. FI00870 FI01106 FI01112 FI01140 FI01141 DEVTERM CDTRAY FI00130 CFF4 CFF6 No action is required. The media can no longer be written to but is still readable. 3. If the format is given support. CFF7 No action is required. Media had an unknown format No action required. ask your media source for a replacement disk. CFFE No action is required. 3. Optical media and/or drive's optical lens is dirty. Interface error detected by device MEDIA FI00870 C301 C400 C402 CFF2 I/O processor internal program error occurred Ask your next level of support for assistance. Media or device error occurred While writing to the media. Internal device error occurred FI00870 Device recovered from error after retries The device successfully recovered from a temporary error. Recovered device error The device successfully recovered from a temporary error. Incompatible media was detected Perform the following: 1. This reference code is logged for information only. 104 (1xxx) System power control network (SPCN) reference codes . exchange the failing items.

0BAB. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). These 4 characters are the unit reference code. 0BD0 to 0BD1 0BEE 0C10 0C20 0C30 0C40. 0C63 0C70. Find the unit reference code in the following table. 0BB0.Reference codes FF09 FF3D Licensed Internal Code for optical device was not upgraded This reference code is logged for information only. 0C53 0C60. see Table 2. This reference code is logged for information only. FF6D No action is required. Table 2. (6A59) Workstation adapter console reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 0AD2 to 0AD3 Communications adapter card test failed 0B25 Communications adapter card test failed 0BA0. which follows the reference code table below. 0C80 0C90 Communications adapter card test failed I/O card Licensed Internal Code ended abnormally Communications adapter card test failed Communications adapter card test failed Adapter card failed modem interface test Synchronous-data-link-control send-receive test failed Binary synchronous control send-receive test failed Asynchronous send-receive test failed Communications adapter card test failed Communications adapter card X. Symbolic FRU Isolation System operation information (6A59) Workstation adapter console reference codes The workstation adapter console detected a failure. Recovered I/O processor error The device successfully recovered from a temporary error. Workstation adapter console failing items Details. Table 1. No action is required.21 test failed 105 Failing Item FI00718 FI00719 FI00718 FI00727 FI00719 FI00718 FI00719 FI00718 FI00719 FI00718 FI00727 FI00719 FI00718 FI00719 FI00718 FI00719 FI00718 FI00719 FI00718 FI00719 FI00718 FI00719 FI00718 (1xxx) System power control network (SPCN) reference codes . Symbolic FRU Isolation Problem Analysis. 0C43 0C50. This reference code is logged for information only. Recovered System bus error The device successfully recovered from a temporary error. For more on the Failing Item column entries. Optical storage unit failing items details Failing Item CDTRAY DEVTERM MEDIA Description Flex cable on tray assembly Bus Terminator Optical Media Document Description Problem Analysis.

contains numbers that identify a particular action your server performs during initialization of firmware. 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. Symbolic FRU Isolation (A1xx) Service processor reference (attention) codes An A1xx system reference (attention) code is an attention code posted by the service processor. Confirm fast power-off (control panel function 08) FSPSPD1 A1003042 A1003043 A1008008 106 (1xxx) System power control network (SPCN) reference codes .Reference codes 0CA1. Click the failing item code only when you experience a hang condition on an attention code. Table 1. Description/Action. The A1xx table uses the following format: • The first column. An A1XX SRC offers information about a platform or service processor dump. offers a brief description about this SRC. Workstation adapter console failing items details Failing Item DPAC UNAUPPR Description Communications two-port adapter cable User suspected problem Document Description Problem Analysis. confirms a control panel function request. offers a link to instructions service actions for recovering from a hang on an attention code. scroll to function 42 again on the panel and press Enter to perform the platform dump. or indicates an issue with a service processor wake-on-LAN setting. Confirm service processor dump (control panel function 43) The control panel displays this attention code after a service processor FSPSPD1 dump (panel function 43) is requested. Confirm platform dump (control panel function 42) The control panel displays this attention code after you request a FSPSPD1 platform dump (panel function 42). error was detected User suspected communications problem. scroll to function 22 again on the panel and press Enter to perform the partition dump. For example. It may also contain instructions for continuing the problem analysis. • The third column. scroll to function 43 again on the panel and press Enter to perform the service processor dump. (A1xx) Service processor reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items A1003000 Platform dump was successful A1003001 Reserved (for platform dump) Confirm partition dump (control (operator) panel function 22) A1003022 Failing Item FSPSPD1 FSPSPD1 The control panel displays this attention code after you request a FSPSPD1 partition dump (panel function 22). When you see this code. FI00719 FI00718 FI00719 FI00718 FI00719 DPAC FI00718 UNAUPPR Table 2. • The second column. When you see this code. Failing Item. no errors detected Diagnostic wrap test completed. When you see this code. 0CC0 5007 5008 FFFF Communications adapter card test failed Diagnostic wrap test completed. Reference Code.

Beginning emergency power off (EPO) countdown FSPSPD1 Proceeding with EPO. (A2xx. If the SRC begins with A2xx. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). Characters 3 and 4 of word 1 are the partition ID of the logical partition with the problem. then the partition ID is in extended word one as LP=xxx (in decimal format). If that IPL fails. B2xx) Logical partition reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 1150 A problem occurred during the IPL of a partition. This is a partitioning configuration problem. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. you can find them in the Serviceable Event View or the view that you use to see informational logs (such as the Product Activity Log or ASM). A problem occurred during the IPL of a partition. B2xx) Logical partition reference codes When the server posts these SRCs. scroll to function 08 again on the panel and press Enter to perform the fast power-off. If characters 3 and 4 are both zero. The LPARCFG Symbolic FRU will help correct the problem.Reference codes A1008009 A100800A A1A3C100 This attention code is displayed on the control panel after you request a fast power-off (panel function 08). (A2xx. Invalid operational mode for remote power on (wake on LAN) Check the service processor settings for remote power on. it uses the resources specified in PHYP NVRAM. When you see this code. no service action is required. This error might occur when you shut down a partition that is set to automatically IPL and then turn the managed system off and back on. The partition attempted to IPL prior to the platform fully initializing. call your next level of support. 1225 If the problem persists. The solution is to activate the partition by using the partition profile on the HMC. When the partition automatically IPLs. then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred during the IPL of a partition. If the SRC begins with B2xx. call your next level of support. This is a partitioning configuration problem. The HMC applies the (1xxx) System power control network (SPCN) reference codes 107 Failing Item LPARCFG SVCDOCS 1230 . This SRC displays after the countdown has FSPSPD1 completed successfully. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). 2. The partition is lacking the necessary resources to IPL. 1. then the partition ID is in extended word one as LP=xxx (in decimal format). LPARCFG LICCODE The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). and this error occurs when the server does not find the exact resources specified in NVRAM. Retry the partition IPL after the platform IPL has fully completed and the platform is not in standby mode. find the next 4 characters of the SRC (called the unit reference code) in the following table. Table 1.

If characters 3 and 4 are both zero. Then retry the partition IPL. then the partition ID is in extended word one as LP=xxx (in decimal format). The IOA for the load source device needed an IOP. SVCDOCS 108 (1xxx) System power control network (SPCN) reference codes . 1266 1280 You are attempting to IPL an operating system that is not supported. then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred during the IPL of a partition. A problem occurred during the IPL of a partition. and the IPL will be halted. SVCDOCS The partition could not IPL. Have the customer configure a load source IOP for the partition. If characters 3 and 4 are both zero. SVCDOCS The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). No default load source IOP was selected for an A/B-mode IPL. An operating system MSD IPL was attempted with the IPL side on D-mode. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If characters 3 and 4 are both zero. This SRC is usually seen when a D-mode SLIC install fails and attempts an MSD. A problem occurred during the IPL of a partition. This is not a valid operating system IPL scenario. Have the customer configure an alternate IPL IOP for the partition. A problem occurred during the IPL of a partition. it uses the resources specified in the profile. A problem occurred during the IPL of a partition. If characters 3 and 4 are both zero. then the partition ID is in extended word one as LP=xxx (in decimal format). and none was detected. SVCDOCS The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format).Reference codes 1260 values in the profile to NVRAM. SVCDOCS 1265 The partition could not IPL at the Timed Power On setting because the IPL setting of the partition was not set to Normal. No alternate (D-mode) IPL IOP was selected. If characters 3 and 4 are both zero. The IPL will attempt to continue. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). Check your LPAR configuration and make sure the correct slot is specified for the IPL load source. but there may not be enough information to find the correct load source. 1320 1321 SVCDOCS 1322 The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). Contact your next level of support. SVCDOCS The partition could not IPL. then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred during the IPL of a partition. NEXTLVL 1310 A mainstore dump IPL did not complete due to configuration mismatch. A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred during a partition Main Storage Dump. Then retry the partition IPL. then the partition ID is in extended word one as LP=xxx (in decimal format). The IPL will attempt to continue. but there may not be enough information to find the correct D-mode load source. Then retry the partition IPL. If characters 3 and 4 are both zero. When the partition IPLs.

There was a failure. then the partition ID is in extended word one as LP=xxx (in decimal format). The platform LIC for this partition attempted an operation. That check failed. If characters 3 and 4 are both zero. IPL did not complete due to a copy error. If you have a RAID enablement card (CCIN 5709) on your system. Contact your next level of support. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). A problem occurred during the IPL of a partition. If characters 3 and 4 are both zero. A mainstore dump IPL did not complete due to a copy error. A problem occurred during the IPL of a partition. See the Symbolic FRU SLOTUSE for more information on the cause of this error. Contact your next level of support. If characters 3 and 4 are both zero. Contact your next level of support. Contact your next level of support. SVCDOCS The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). A problem occurred during the IPL of a partition. If characters 3 and 4 are both zero. then the partition ID is in extended word one as LP=xxx (in decimal format). NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If characters 3 and 4 are (1xxx) System power control network (SPCN) reference codes 109 . If that embedded slot is called out in the error. 2475 SLOTUSE 2485 3081 LICCODE 3110 SVCDOCS 3113 The search for a valid load source device was exhausted. A problem occurred during the IPL of a partition. The platform LIC for this partition attempted an operation. A problem occurred during the IPL of a partition. See the Symbolic FRU SLOTUSE for more information on the cause of this error. then the partition ID is in extended word one as LP=xxx (in decimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred during the IPL of a partition. 2425 to 2426 The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). Perform LICIP15. During the partition IPL. A slot that was needed for the partition was unavailable. Check your LPAR configuration and make sure that the correct slot is specified for the IPL load source. A problem occurred during the IPL of a partition. A problem occurred during a partition Main Storage Dump. code tried to determine if the device in a slot was an I/O Processor or an I/O Adapter. NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. perform LICIP15. There was a failure. 2320. then the partition ID is in extended word one as LP=xxx (in decimal format). The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). A mainstore dump IPL did not complete due to a copy error. Then retry the partition IPL. If this does not resolve the problem.Reference codes 2048 The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). 2300 SLOTUSE 2310. it will disable an embedded SCSI adapter. NEXTLVL 2058 NEXTLVL 2250. you can safely ignore this error. A problem occurred during a partition Main Storage Dump. Contact your next level of support. A slot that was needed for the partition was either empty or the device in the slot has failed.

A problem occurred on the path to the load source for the partition.Reference codes both zero. Word 5: Card. then this SRC is informational and can be ignored. If there are no serviceable B700 69xx errors. System log entry only. NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If characters 3 and 4 are both zero. This is a platform LIC main store utilization problem. If word 3 is zero. Correct that error and retry the partition IPL. If the IPL fails. A problem occurred during the IPL of a partition. look for other serviceable errors. Look for B700 69xx errors in the Serviceable Event View and work those errors. no service action required LICCODE A problem occurred during the IPL of a partition. or if correcting the errors did not correct this problem. Word 4: Board. Word 3: Bus. then the partition ID is in extended word one as LP=xxx (in decimal format). A nonzero bus number has no associated bus object. then the partition ID is in extended word one as LP=xxx (in decimal format). System log entry only. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). The B2xx xxxx SRC Format is Word 1: B2xx3114. no service action required The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). An unexpected failure return code was returned when attempting to query the IOA slots that are assigned to an IOP. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. If present. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). Look for B700 69xx errors in the Serviceable Event View and work those errors. This is logged for each unsuccessful attempt to IPL with a loadsource candidate. then the partition ID is in extended word one as LP=xxx (in 110 (1xxx) System power control network (SPCN) reference codes 3114 3120 3123 3125 3128 NEXTLVL 3130 NEXTLVL 3135 NEXTLVL . look in the Serviceable Event View for a B7xx xxxx during the partition's IPL. A problem occurred during the IPL of a partition. Otherwise there is a problem in the platform LIC. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). If characters 3 and 4 are both zero. The platform LIC could not obtain a segment of main storage within the platform's main store to use for managing the creation of a partition. A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). contact your next level of support. Retry count exceeded. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format).

Look for a SRC in the Serviceable Event View logged at the time the partition was performing an IPL. The IPL will continue by searching for a valid load source device.Reference codes 3140 decimal format). no service action required The I/O Processor in the slot used for the last successful IPL of the operating system was removed. a B2xx3200 may be posted to the control panel. System log entry only. System log entry only. no service action required The IOP in the slot used for the last successful IPL of the operating system was replaced with an I/O Adapter. If characters 3 and 4 are both zero. System log entry only. This is normal. no service action required The I/O Adapter in the slot used for the last successful IPL of the operating system was removed. This is a configuration problem in the partition. and ensure that the tagged I/O for the partition is correct. Work the B2xx3110 error in the Serviceable Event View. The load source IOP is not owned by the partition. If characters 3 and 4 are both zero. A problem occurred during the IPL of a partition. The IPL will continue by searching for a valid load source device. no service action required The I/O Adapter in the slot used for the last successful IPL of the operating system was replaced with an I/O Processor. If there is not a configuration problem then contact your next level of support. Check the LPAR configuration if required. and ensure that the tagged I/O for the partition is correct. perform the actions indicated for the B2xx3110 SRC. System log entry only. The IPL will continue by searching for a valid load source device. The IPL will continue by searching for a valid load source device. no service action required The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). System log entry only. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). An unknown bus type was detected. and ensure that the tagged I/O for the partition is correct. This error indicates a failure during a search for the load source. Check the LPAR configuration if required. If the system IPL hangs at B2xx3200 and you cannot check the SRC history. no service action required The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). Check the LPAR configuration if required. then the partition ID is in extended word one as LP=xxx (in decimal format). then the partition ID is in extended word one as LP=xxx (in SVCDOCS 3141 3142 3143 3144 3200 4158 (1xxx) System power control network (SPCN) reference codes 111 . If characters 3 and 4 are both zero. There may be a number of these failures prior to finding a good load source. System log entry only. If a B2xx3110 error is logged. and ensure that the tagged I/O for the partition is correct. Have the customer reconfigure the partition to have the intended load source IOP. Check the LPAR configuration if required.

NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). This is normal. then the partition ID is in extended word one as LP=xxx (in decimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred during the IPL of a partition. There was an error writing the partition's main storage dump to the partition's load source. Contact your next level of support. Work the B2xx3110 error in the Serviceable Event View. a B2xx3200 may be posted to the control panel. then the partition ID is in extended word one as LP=xxx (in decimal format). If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). Contact your next level of support. Look for a SRC in the Serviceable Event View logged at the time the partition was performing an IPL. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). The partition ID is characters 3 and 4 of the B2xx reference code in 5117 5121 NEXTLVL 5122 to 5123 112 (1xxx) System power control network (SPCN) reference codes . perform the actions indicated for the B2xx3110 SRC. If a B2xx3110 error is logged. This error indicates a failure during a search for the load source. A problem occurred during the IPL of a partition. SVCDOCS The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). A partition main storage dump has occurred but cannot be written to the load source device because a valid dump already exists. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. It is usual for a number of these failures to occur prior to finding a valid load source. A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). There was an error reading the partition's main storage dump from the partition's load source into main storage. NEXTLVL 5106 5114 NEXTLVL 5115 The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). A problem occurred during the IPL of a partition. System log entry only. Use the Main Storage Dump Manager to rename or copy the current main storage dump. There is not enough space to contain the partition main storage dump. If characters 3 and 4 are both zero. There was a partition main storage dump problem. If characters 3 and 4 are both zero. no service action required A problem occurred during the IPL of a partition. A problem occurred during the IPL of a partition. NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If the system IPL hangs at B2xx3200 and you cannot check the SRC history.Reference codes decimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). There is not enough space to contain the partition main storage dump. 5109 Contact your next level of support.

A problem occurred during the IPL of a partition. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. A problem occurred during the IPL of a partition. A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). No service action required. An error occurred when writing the partition's main storage dump to the partition's load source. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). A problem occurred during the IPL of a partition. LSERROR LSERROR NEXTLVL NEXTLVL 5135 5137 5145 5148 (1xxx) System power control network (SPCN) reference codes 113 . 6006 Contact your next level of support. then the partition ID is in extended word one as LP=xxx (in decimal format). NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). If characters 3 and 4 are both zero. NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). 6012 Contact your next level of support. then the partition ID is in extended word one as LP=xxx (in decimal format). There was an error writing the partition's main storage dump to the partition's load source. If characters 3 and 4 are both zero.Reference codes word 1 of the SRC (in hexadecimal format). 6015 Contact your next level of support. A problem occurred during the IPL of a partition. If characters 3 and 4 are both zero. 6025 The load source media is corrupted or not valid. The partition's LID failed to completely load into the partition's mainstore area. NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred during the IPL of a partition. A platform LIC error occurred when the partition's memory initialized. then the partition ID is in extended word one as LP=xxx (in decimal format). The IPL will not continue. If characters 3 and 4 are both zero. NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred during the IPL of a partition. An error occurred while doing a main storage dump that would have caused another main storage dump. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. There was an error writing the partition's main storage dump to the partition's load source. There was an error writing the partition's main storage dump to the partition's load source.

A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). If characters 3 and 4 are both zero. allocate enough resources to the partition.Reference codes The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If the system IPL hangs at B2xx7200 and you cannot check the SRC history. System log entry only. correct the partition configuration. then the partition ID is in extended word one as LP=xxx (in decimal format). SVCDOCS The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). Error on load source device. If characters 3 and 4 are both zero. LSERROR The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If the problem is due to unsupported partition configuration. then the partition ID is in extended word one as LP=xxx (in decimal format). This may be normal. no service action required A problem occurred during the IPL of a partition. A problem occurred during the IPL of a partition. This informational error indicates a failure resetting the I/O Processor in the preceding B2xx3200 error. verify that no memory leaks are present. An error occurred while copying Open Firmware into the partition load area. There was a failure loading the VPD areas of the partition. System log entry only. An internal LIC timeout has occurred. 6027 This is a problem with the load source media being corrupt or not valid. If there is a hardware failure there will be a different serviceable event. then the partition ID is in extended word one as LP=xxx (in decimal format). Contact your next level of support. A problem occurred during the IPL of a partition. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. Ensure the partition was allocated enough main storage. 114 (1xxx) System power control network (SPCN) reference codes 6110 690A NEXTLVL 7200 8080 8081 8105 . Possible causes are: • Corrupted/unsupported load source media • Insufficient resources allocated to the partition • Unsupported partition configuration by the operating system If the problem is due to media. replace the load source media. then the partition ID is in extended word one as LP=xxx (in decimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). NEXTLVL The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If characters 3 and 4 are both zero. A problem occurred during the IPL of a partition. An error condition was encountered when communicating with the load source I/O Processor for the partition identified in the xx field of the B2xx SRC. LICCODE The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). perform the actions indicated for the B2xx3110 SRC. The partition may continue to IPL but it may experience problems while running. If characters 3 and 4 are both zero. no service action required The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). and then retry the operation. A failure occurred when allocating memory for an internal object used for LID load operations. If the problem is due to insufficient resources.

Partition did not IPL due to platform Licensed Internal Code error. A problem occurred during the IPL of a partition. Re-IPL the partition. then the partition ID is in extended word one as LP=xxx (in decimal format). A problem occurred on the path to the load source for the partition. 8123. Contact your next level of support. There was an error mapping memory for the partition's IPL. If characters 3 and 4 are both zero. A problem occurred during the IPL of a partition. A problem occurred during the IPL of a partition. Ensure that the console device cables are connected properly. The IPL is terminated. A problem occurred after a partition ended abnormally.Reference codes 8107 A problem occurred during the IPL of a partition. If characters 3 and 4 are both zero. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). A failure occurred. There was a low level partition to partition communication failure. A problem occurred during the IPL of a partition. 8125. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). NEXTLVL SVCDOCS A100 to A101 SVCDOCS (1xxx) System power control network (SPCN) reference codes 115 . There was a failure verifying VPD for the partition's resources during IPL. contact your next level of support. A problem occurred during the IPL of a partition. Call your next level of support. A problem occurred during the IPL of a partition. 8129 813A Contact your next level of support. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. If characters 3 and 4 are both zero. A failure occurred. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If the cables are already connected properly. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). There was a problem getting a segment of main storage in the platform's main store. LICCODE 8109 LICCODE 8112 LICCODE 8113 LICCODE 8114 LICCODE 8115 LICCODE 8117 8121. Ensure that there is enough memory to IPL the partition. If characters 3 and 4 are both zero. If the problem reoccurs. A problem occurred during the IPL of a partition. then the partition ID is in extended word one as LP=xxx (in decimal format). replace the cables. A problem occurred on the path to the load source for the partition. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). 8127. then the partition ID is in extended word one as LP=xxx (in decimal format). The IPL is terminated. Partition did not IPL due to platform Licensed Internal Code error. Call your next level of support. then the partition ID is in extended word one as LP=xxx (in decimal format).

If characters 3 and 4 are both zero. NEXTLVL 116 (1xxx) System power control network (SPCN) reference codes . If there are no errors. If characters 3 and 4 are both zero. then the partition ID is in extended word one as LP=xxx (in decimal format). Partition processors did not start LIC within the timeout window. Re-IPL the partition. replace the cables. This partition could not stay running and shut itself down. The platform will need to be re-IPLed before that partition can be used. If characters 3 and 4 are both zero. Ignore this error if there are other serviceable errors. A problem occurred after a partition ended abnormally. then the partition ID is in extended word one as LP=xxx (in decimal format). Call your next level of support. If the cables are already connected properly. contact your next level of support. An operation has timed out. If characters 3 and 4 are both zero. A problem occurred during a power off a partition NEXTLVL Internal platform Licensed Internal Code error occurred during partition shutdown or re-IPL. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). contact your next level of support. contact your next level of support. If characters 3 and 4 are both zero. The partition did not respond to a system request to power off the partition. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format).Reference codes The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). then the partition ID is in extended word one as LP=xxx (in decimal format). This partition had a communications problem. If characters 3 and 4 are both zero. SVCDOCS Ensure that the console device cables are connected properly. There was a communications problem between this partition and code that handles resource allocation. System log entry only. A problem occurred during the IPL of a partition. no service action required A problem occurred after a partition ended abnormally. then the partition ID is in extended word one as LP=xxx (in decimal format). D150 Contact your next level of support. A system request to power off a partition failed The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). Call your next level of support. A problem occurred during the IPL of a partition. Work those error logs for this partition and for the platform from the Serviceable Event View. If the problem reoccurs. then the partition ID is in extended word one as LP=xxx (in decimal format). The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). If there are no errors. LICCODE B07B B215 NEXTLVL C1F0 E0AA The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). F001 SVCDOCS F003 NEXTLVL F004 Capture a Partition Dump and call your next level of support. There was a communications problem between this partition's service processor and the platform's service processor. then the partition ID is in extended word one as LP=xxx (in decimal format). Work any error logs in the Serviceable Event View. A problem occurred during the IPL of a partition.

Re-IPL the partition to recover. capture a Partition Dump. If characters 3 and 4 are both zero. A problem occurred during the IPL of a partition. If characters 3 and 4 are both zero. Look for other errors. The partition did not respond to a system request to power off the partition. a timeout occurred while waiting for a ready message from the partition. System log entry only. If this SRC is displayed in the operator panel. then panel function 34 might be used to retry the current IPL while the partition is still in the failed state. F00C (1xxx) System power control network (SPCN) reference codes 117 . a timeout occurred while waiting for a response to a message. If there are no errors. then the partition ID is in extended word one as LP=xxx (in decimal format).Reference codes F005 If the partition is an i5/OS partition. Work any error logs for this partition in the Serviceable Event View. then the partition ID is in extended word one as LP=xxx (in decimal format). F00A to F00B Look for other errors. no service action required During an IPL. The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). System log entry only. Re-IPL the partition to recover. Contact your next level of support. Contact your next level of support. A problem occurred on the path to the load source for the partition. If the partition is an i5/OS partition. A problem occurred during the IPL of a partition. a timeout occurred while waiting for a response to a message. then the partition ID is in extended word one as LP=xxx (in decimal format). a timeout occurred while waiting for a response to a message. A system request to power off a partition failed The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). contact your next level of support. During an IPL. The code load operation for the partition's IPL timed out. Look for other errors. no service action required During an IPL. capture a Partition Dump. then panel function 34 might be used to retry the current IPL while the partition is still in the failed state. This partition had a communications problem. no service action required During an IPL. A timeout occurred during the process of trying to stop a partition from running. Contact your next level of support. If characters 3 and 4 are both zero. If this SRC is displayed in the operator panel. A problem occurred during a power off a partition The partition ID is characters 3 and 4 of the B2xx reference code in word 1 of the SRC (in hexadecimal format). System log entry only. NEXTLVL F006 SVCDOCS F007 LICCODE F008 F009 Look for other errors.

Perform the following actions: 1. Perform the actions in the Description/Action column of the table. Platform LIC detected an error More than one request to terminate the system was issued. then contact your next level of support. undefined error occurred. In all cases. Collect all the words of the SRC and the platform dump and send to your system manufacturer for analysis. Words 2 to 9 of this SRC contain additional diagnostic information. then contact your next level of support. go to the locations table for the system you are working on to determine the location. Perform a platform system dump and notify your service provider. Find the unit reference code by looking at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). otherwise use the FRU list documented here to determine the parts to exchange. Platform LIC failure LICCODE Work with the FRU list in the serviceable event view if there is one. Collect all the SRC words and the platform system dump. Platform LIC failure LICCODE Work with the FRU list in the serviceable event view if there is one. These 4 characters are the unit reference code. Table 1. Platform LIC failure 0104 0105 0106 LICCODE NEXTLVL LICCODE 0107 SVCDOCS 0302 The server detected an unrecoverable machine check condition. Platform LIC failure Work with the FRU list in the serviceable event view if there is one. Collect all the SRC words and the platform system dump. otherwise use the FRU list documented here to determine the parts to exchange. once the failing item is determined. otherwise use the FRU list documented here to determine the parts to exchange. A secondary failure due to an invalid SRC occurred when the platform attempted to terminate. The platform Licensed Internal Code (LIC) detected an internal problem. B7xx) Licensed Internal Code reference codes Use this table for A7xx and B7xx reference codes. Look up the unit reference code in the following table. IPL the system. B7xx) Licensed Internal Code (LIC) Reference Codes Reference Code Description/Action Perform all actions before exchanging Failing Items 0102 Platform LIC detected an error Failing Item SVCDOCS 0103 A machine check occurred during IPL. Platform LIC failure Machine check. 2. 3.Reference codes (A7xx. Record SRC words 1 through 9 before attempting to IPL again and report the problem to next level of support. Service processor failure 0441 118 SVCPROC (1xxx) System power control network (SPCN) reference codes . (A7xx. and use the remove and replace procedure for the failing item.

Platform LIC detected an error Work with the FRU list in the serviceable event view if there is one. and the recorded SRC information to your next level of support. The second word indicates the severity of the error and the specific error condition. otherwise use the FRU list documented here to determine the parts to exchange. configuration data. No corrective action is required. use the ASM interface to reset the system clock at power on standby. call your next level of support. Provide the platform dump. If this is a serviceable event. 0621 0650 If the error occurs a second time. For systems managed by an HMC. A platform dump was started. use the FRU list documented in the Failing Items column to determine the parts to exchange. NEXTLVL 0443 0601 SVCPROC NEXTLVL SVCDOCS 0602 NEXTLVL 0611 Platform Licensed Internal Code (LIC) detected an error condition. otherwise use the FRU list documented here to determine the parts to exchange. no service action required A user request initiated an I/O tower/drawer power off. you can ignore this error. no service action required No service action required. then work with the FRU list in the serviceable event view if there is one. Platform LIC detected an error Resource management was unable to allocate main storage. Service processor failure System log entry only. Words 2 to 9 of this SRC contain additional diagnostic information. The system detected an error in the system clock hardware This is a serviceable event only if this error appears in a serviceable event view. If the system did not log this error as a serviceable event. No corrective action is required. The platform encountered an error early in the IPL or termination process. System clock problem SVCDOCS Work with the FRU list in the serviceable event view if there is one. then no service action is required.Reference codes Work with the FRU list in the serviceable event view if there is one. Collect the platform dump and the configuration of the memory allocation for all partitions on this system. no service action required NEXTLVL 0651 0A00 SVCDOCS 1150 to 1151 SVCDOCS (1xxx) System power control network (SPCN) reference codes 119 . Otherwise. otherwise this does not require service. System log entry only. If word 2 is 10000A01 then record the SRC words and call your next level of support. otherwise use the FRU list documented here to determine the parts to exchange. System log entry only. Record SRC words 1 through 9. no service action required Support can use this SRC and associated data to determine why the time of day for a partition was lost. System log entry only. For systems without an HMC.

Platform LIC detected an error If required Power On Demand functions are not available. The VPD on a memory DIMM is not correct and the memory on the DIMM cannot be used. System log entry only. Otherwise. if there is one. Otherwise. no service action required No service action is required for this event. Work with the FRU list in the serviceable event view. if there is one. a redundant VPD chip exists. The VPD on a processor card is not correct and the processor card cannot be used. If something more severe occurred there will be a SRC requiring a service action logged as well. then the service processor was reset automatically to correct for the communications problem. look for other errors in the serviceable event view. When word 9 is not 00180003 replace the VPD card immediately. no service action required. Note that this is A7xx only. resolve that error. resulting in reduced memory. and the system will continue to run. Service processor failure SVCPROC LICCODE Work with the FRU list in the serviceable event view if there is one. resulting in reduced processing power. The platform code attempts a graceful shutdown of partitions and powers off the server after a certain time.Reference codes 1152 No action needed unless a serviceable event was logged. use the FRU list documented here to determine the parts to exchange. System log entry only. Work with the FRU list in the serviceable event view. When word 9 is 00180003. Platform LIC detected an error CAPACTY The VPD for the system is not what was expected at IPL. Otherwise. Otherwise. System log entry only. Platform LIC detected an error ANYPROC The VPD for the system is not what was expected at IPL. use the FRU list documented here to determine the parts to exchange. otherwise use the FRU list documented here to determine the parts to exchange. Replace the VPD card at your next scheduled maintenance. The platform encountered an error communicating with the service processor. whichever comes first. no service action required The platform encountered a service processor event indicating that the power status has changed. If a system problem is suspected. SVCDOCS Platform LIC detected an error (1xxx) System power control network (SPCN) reference codes 1161 1730 1731 1732 1733 173A 173B 120 . Work with the FRU list in the serviceable event view if there is one. no service action is required. If a serviceable event was logged. or when the last partition indicates shutdown. use the FRU list documented here to determine the parts to exchange. re-IPL the system. SVCDOCS 1160 If there is a A7001150 src present. no service action required A VPD collection overflow occurred. Platform LIC detected an error MEMDIMM The VPD for the system is not what was expected at IPL.

or using system VPD. Contact your next level of support to verify your activation code. re-IPL the system. perform Restoring your server to factory settings. The firmware does not have partition configuration information. re-IPL the system. or no errors were found. Platform LIC failure A problem occurred when initializing. The IPL failed. reading. Work with the FRU list in the serviceable event view if there is one. look for and correct errors with SRCs of the form B1xxxxxxx in the Serviceable Event View. Platform LIC failure Work with the FRU list in the serviceable event view if there is one. reading. If Power On Demand function is required. Use the Hardware Management Console (HMC) to activate one or more partitions to change the system from a standby state to an operating state. replace the VPD card. If Power On Demand functions are required. contact your next level of support. There is a platform dump to collect SVCDOCS Work with the FRU list in the serviceable event view if there is one. If the HMC does not manage the server. (1xxx) System power control network (SPCN) reference codes 121 4091 4400 4401 NEXTLVL SVCDOCS CAPACTY 4701 CAPACTY 4703 LICCODE 4704 SVCDOCS 4705 . or using system VPD. The platform LIC detected an internal problem. reading. If Power On Demand function is required. Platform LIC failure A problem occurred when initializing. Platform LIC detected an error A problem occurred when initializing. Look for and correct errors with SRCs of the form B1xxxxxx in the Serviceable Event View. otherwise use the FRU list documented here to determine the parts to exchange. User intervention required The system power on has reached a standby state. reading. The Power On Demand function is not available. Platform LIC detected an error The Power On Demand function is no longer available. otherwise use the FRU list documented here to determine the parts to exchange. or using system VPD.Reference codes A platform LIC failure occurred during VPD collection. Use the operating system's interface designated to collect platform dumps. If that does not correct the problem. contact your next level of support. contact your next level of support. contact your next level of support. If that does not correct the problem. Power On Demand is not available because the stored activation code is not valid. If that does not correct the problem. The Power On Demand function is not available. 4700 Contact your next level of support. If that does not correct the problem. Platform LIC detected an error A problem occurred when initializing. If the activation code is valid. or using system VPD. otherwise use the FRU list documented here to determine the parts to exchange.

Enter a valid activation code. reading. Platform LIC detected an error The VPD card has been exchanged with a not valid card. Platform LIC detected an error 4713 SVCDOCS 4714 SVCDOCS 4715 SVCDOCS CAPACTY 4716 SVCDOCS LPARCFG 4730 SVCDOCS LPARCFG 4731 A problem occurred when configuring the logical partitions on the system. Look for errors with SRCs of the form B1xxxxxxx in the Serviceable Event View. contact your next level of support. Platform LIC detected an error SVCDOCS The system has been running with full Power On Demand resources activated. enter an activation code of all zeroes. otherwise use the FRU list documented here to determine the parts to exchange. Then obtain the proper activation codes for the resources being used or allocate fewer resources in the LPAR configuration. contact your next level of support. Platform LIC has detected a new VPD card The new VPD card requires new activation codes. Either obtain more capacity by obtaining new activation codes or allocate fewer resources in the LPAR configuration. Resources associated with this activation code have been disabled. Platform LIC detected an error A problem occurred when initializing. the system will terminate and unlicensed resources will no longer be available. Platform LIC detected an error An incorrect activation code has been detected. Work with the FRU list in the serviceable event view if there is one. User intervention required The Power On Demand activation code recovery period has been started. Platform LIC failure The Power On Demand function is not available. The Power On Demand function is not available. Either obtain more capacity by obtaining new activation codes or allocate fewer resources in the LPAR configuration. Work with the FRU list in the serviceable event view if there is one. Platform LIC detected the VPD card is missing CAPACTY A problem occurred when initializing. or using system VPD. If that does not correct the problem. look for errors with SRCs of the form B1xxxxxxx or B7xx69xx in the Serviceable Event View. or using system VPD. SVCDOCS 4712 If Power On Demand function is required. Work those errors. reading. To prevent the system from terminating. otherwise use the FRU list documented here to determine the parts to exchange. Work those errors first. Enter the new activation codes. 4733 4740 122 (1xxx) System power control network (SPCN) reference codes . If that does not correct the problem. replace the VPD card. Reinstall the original VPD card in the system. In one hour. More resources were allocated than there are available for use. If that does not correct the problem. If Power On Demand function is required.Reference codes 4710 Platform LIC detected an error A communications problem with the service processor occurred while initiating Power On Demand. re-IPL the system.

Permanently activate the temporary Power On Demand resources.Reference codes 4741 Platform LIC detected an error The number of allowable attempts to enter a valid activation code has been exceeded. If that does not correct the problem. Look for errors with SRCs of the form B1xx xxxx or B7xx69xx in the Serviceable Event View. contact your next level of support. A Power On Demand change has been detected A Reserve Power On Demand resource has been activated. contact your next level of support. contact your next level of support. If other errors occur. The system will continue to run. No Power On Demand changes can be made. User intervention required SVCDOCS One hour remains until the Reserve Power On Demand request expires. no service action required The data obtained from the system is not what was expected. If other errors occur. Work those errors first. Platform LIC detected an error The server detected a not valid Power On Demand activation and terminated the system. enter a new On/Off Power On Demand request for the temporary resources. No service action is required. Platform LIC detected an error A communications problem with the service processor occurred. The system will perform a slow IPL in order to obtain the correct data. Should other errors occur. In order to reactivate temporary resources. Platform LIC detected an error Work with the FRU list in the serviceable event view if there is one. The allocated resources for the system might exceed those that are available for use. Fast system IPL changed to slow system IPL The data obtained from the system is not what was expected. User intervention required SVCDOCS One hour remains until the On/Off Power On Demand request expires. If that does not correct the problem. no service action required The Power On Demand History Log has been written to the error log. re-IPL the system. contact your next level of support. The system will perform a slow IPL in order to obtain the correct data. Obtain a permanent activation code or remove all temporary resources from partitions before the request expires. System log entry only. 4742 SVCDOCS 4747 4748 4749 4750 4788 47C1 47CB 47CD SVCDOCS 47FF 5120 NEXTLVL (1xxx) System power control network (SPCN) reference codes 123 . User intervention required SVCDOCS One hour remains until the Trial Customer on Demand activation expires. but you can continue to run with the current Power On Demand resources. otherwise use the FRU list documented here to determine the parts to exchange. or remove all temporary resources from partitions before the request expires. System log entry only. The IPL will continue. a new Reserve Power On Demand enablement code is required. but a system IPL is required in order to retry entering a valid activation code. Power On Demand data mismatch The data obtained from the system is not what was expected.

to your next level of support. The platform detected a problem in an Operating System. An IOP signalled to system Licensed Internal Code that it had entered a critical internal state. If the system IPL hangs at B2xx3200 or B7005122 and you cannot check the SRC history. Platform LIC detected an error SVCDOCS Platform Licensed Internal Code detected that an IOP request failed. If a B2xx3110 error is logged. 5122 5123 5190 SVCDOCS 5191 SVCDOCS LICCODE 5209 5219 124 (1xxx) System power control network (SPCN) reference codes . improperly seated cards. or removeable media drive not in a ready state. or this SRC has logged informational platform boto or hardware data. Licensed Internal Code automatically attempted to restart the IOP. If configuration is correct. Platform Licensed Internal Code detected a programming problem for which a platform dump may have been initiated. contact your next level of support. or if you find no errors. Platform LIC failure NEXTLVL Licensed Internal Code program exception occurred. Licensed Internal Code program exception occurred. Platform LIC detected an error A Licensed Internal Code program exception or data collection occurred. Use the Hardware Management Console (HMC) to verify or reconfigure incorrect virtual I/O configuration. Operating System error Work with the FRU list in the serviceable event view if there is one. Send the system error log and the platform dump. There may be a number of these failure prior to finding a good load source. Platform LIC detected an error Information only.Reference codes 5121 If the system is not exhibiting problematic behavior. This is normal. Look for other errors. If no other errors are present. Work the B2xx3110 error in the Serviceable Event View. a B2xx3200 or B7005122 may be posted to the control panel. this error may safely be ignored. This may be caused by loose connections. if it occurred. media. Otherwise. If correcting those errors does not correct the problem. This error indicates a failure during a search for the load source. no service action required. Check for errors in the partition ID specified in word 4 of the SRC. Platform LIC detected an error Platform Licensed Internal Code detected a Virtual I/O configuration error. continue with the next FRU in the list. perform the actions indicated for the B2xx3110 SRC. This may indicate an IOP programming problem or an IO Adapter boot problem. Platform LIC detected an error System Licensed Internal Code detected an IOP timeout during IOP IPL. contact your next level of support. Licensed Internal Code has recovered from any exception conditions. otherwise use the FRU list documented here to determine the parts to exchange. Look for other errors.

contact your next level of support. At the earliest convenient time or service window work with your service provider to take a platform dump and reIPL the system. Use the Hardware Management Console to reconfigure the LPAR configuration. or if resolving the error fails to correct the problem. SVCDOCS 6900 Continue running the system normally. User intervention required System detected a problem with the Logical Partition (LPAR) Configuration. The processor is not functional. The platform detected a problem with a processor. or using system VPD. then close this problem PIOCARD and work the B7006981 SRC. Check Hardware Management Console (HMC) partition state. otherwise use the FRU list documented here to determine the parts to exchange. 5301 SVCDOCS 5400 SVCDOCS 5600 to 5601 5700 There was a problem initializing. reading. 1. 2. or if there are no other errors. otherwise use the FRU list documented here to determine the parts to exchange. Look in the Serviceable Event View for a B1xx xxxx error that implicates a processor. PCI host bridge failure PRIPCI MA_BRDG If you find a B7006981 SRC logged at about same time and listing parts MABIP50 from same enclosure as one of the FRUs here. Work with the FRU list in the serviceable event view.Reference codes 5300 Platform LIC detected a failure while partitioning resources Work with the FRU list in the serviceable event view if there is one. If in Recovery state then use the HMC to perform "Recovering partition data on a managed system". contact your next level of support. use the FRU list documented here to determine the parts to exchange. most of which involve the platform Licensed Internal Code (LIC). Use HMC to activate partitions A resource has been disabled due to hardware problems Work with the FRU list in the serviceable event view if there is one. Otherwise. (1xxx) System power control network (SPCN) reference codes 125 . System firmware has experienced a low storage condition No immediate action is necessary. If this fails to correct the problem. Platform LIC failure NEXTLVL Work with the FRU list in the serviceable event view if there is one. Work any error logs found in the Serviceable Event View. if there is one. Platform partitioning code encountered an error. This SRC represents a large number of possible problems. If the Serviceable Event View contains no B1xx xxxx error. otherwise use the FRU list documented here to determine the parts to exchange.

Look for other errors. In order to make more NVRAM available. Perform the recovery actions for the SVCPROC FRU but do not replace the service processor. the system has lost the platform error logs and partition-related information. System bus error Work with the FRU list in the serviceable event view if there is one. The system has lost all the configured system settings (such as the HMC access and ASMI passwords. The partition is still functional. If the bus is not empty. otherwise use the FRU list documented here to determine the parts to exchange. but is operating in a degraded mode. otherwise use the FRU list documented here to determine the parts to exchange. Work with the FRU list in the serviceable event view if there is one. delete one or more partitions. etc. otherwise use the FRU list documented here to determine the parts to exchange. a hardware or configuration problem might exist. hardware deconfiguration policies. and the service processor is reset. Also. System bus error Work with the FRU list in the serviceable event view if there is one. time of day.) that you might have set through user interfaces. Configuration information may be lost at the next IPL. otherwise use the FRU list documented here to determine the parts to exchange. System bus error Work with the FRU list in the serviceable event view if there is one. Platform LIC detected an error SVCDOCS A platform dump has occurred. otherwise use the FRU list documented here to determine the parts to 6951 6965 6970 6971 MABIP51 PIOCARD MASBUS MA_BRDG MA_BRDG PRIPCI 6972 126 (1xxx) System power control network (SPCN) reference codes . Platform LIC detected an error SVCDOCS An error occurred because a partition needed more NVRAM than was available. PCI host bridge failure PRIPCI MA_BRDG If you find a B7006981 SRC logged at about same time and listing parts MABIP50 from the same enclosure as one of the FRUs here. network configuration. then close this PIOCARD problem and work the B7006981 SRC. System bus error Work with the FRU list in the serviceable event view if there is one. Platform LIC detected an error SIIOADP 6907 SIIOADP LICCODE 6908 SIIOADP MA_BRDG 6909 SIIOADP MA_BRDG LICCODE 6944 6950 A system bus appears to be empty. System bus error Work with the FRU list in the serviceable event view if there is one. use the failing item list presented here for servicing this reference code.Reference codes 6906 If the Serviceable Event View is not available. The platform dump should be sent to your service provider. otherwise use the FRU list documented here to determine the parts to exchange. Look for other errors. otherwise use the FRU list documented here to determine the parts to exchange. PCI secondary bus failure Work with the FRU list in the serviceable event view if there is one. Platform LIC detected an error Unknown hardware detected.

The four rightmost characters of word 4 in the reference code represent the Program Return Code (PRC). If the first half of word 7 is not 0001. 6982 6983 SIRGCFG (1xxx) System power control network (SPCN) reference codes 127 . An invalid High Speed Link (HSL) configuration was detected 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. which describes the problem detected. Work with the FRU list in the serviceable event view. Use the unit value of the location codes to determine if the expansion unit is the same. 6974 MABRCFG PIOCARD 6980 SYSBKPL LICCODE 6981 A platform dump has occurred. Note: The FRU description in the serviceable event view may already contain a message that identifies the problem. If the problem persists contact your next level of support. Otherwise. Network Interface Controller (NIC) resource failure If the serviceable event view contains a FRU list. TOPORT otherwise use the FRU list documented here to determine the parts to exchange. NOTE: A fiber optic cleaning kit may be required for optical HSL connections. The four leftmost digits of word 7 represent the loop number in hexadecimal format. work with those FRUs. PRIPCI Use the unit value of the location codes to determine if the expansion MASBUS unit is the same. find the PRC in the list below. System bus error PIOCARD MA_BRDG If you find a B7006981 SRC logged on the same expansion unit as one SVCPROC of the FRUs here. exchange the failing items listed here.Reference codes 6973 exchange. if there is one. Convert the loop number to decimal format before comparing it to loop numbers shown in serviceable event views and service tools. Otherwise. otherwise use the FRU list documented here to determine the parts to exchange. Set the serial number on the system unit. Otherwise. Work with the FRU list in the serviceable event view. • xxxx 0008 indicates the system serial number is not set. then close this problem and work the 1xxx SRC. remove SVCPROC (the service processor) from the list of possible FRUs. Multi-adapter bridge configuration change or error Work with the FRU list in the serviceable event view if there is one. High Speed Link (HSL) connection failure SVCDOCS HSL_LNK Perform the RIOIP11 procedure. then close this problem and work the B7006970 SRC. High Speed Link (HSL) I/O bridge failure SIIOADP If you find a 1xxx SRC logged on the same expansion unit as one of the FRUs here. use the FRU list documented here to determine the parts to exchange. OPT_CLN FRPORT Work with the FRU list in the serviceable event view if there is one. if there is one. use the FRU list documented here to determine the parts to exchange. Send the dump to your service provider. To determine the problem.

Word 7 of the SRC contains the loop number in the leftmost 4 digits. Work with the FRU list in the serviceable event view if there is one. The loop number is in hexadecimal format. This SRC can be caused by a tower on the HSL loop powering off. Service the other SRC if present. You will need to ensure all clustered systems are on the same HSL/RIO loop. no service action required An HSL loop has switched to its alternate path. otherwise use the FRU list documented here to determine the parts to exchange. System log entry only. Service processor failure Work with the FRU list in the serviceable event view if there is one. 6984 This ends the procedure. This is an informational SRC only. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code. otherwise use the FRU list documented here to determine the parts to exchange. This SRC may also appear in a Serviceable Event View you are using. Otherwise if FRPORT this is NOT a serviceable event then to determine what this SRC means TOPORT use symbolic FRU SIRSTAT. with a B700 6982 or B700 6981 logged at approximately the same time. In that case the other SRC is reporting a failure and this SRC is reporting that the alternate RIO path is now being used. System bus error Work with the FRU list in the serviceable event view if there is one. High Speed Link (HSL) connection failure Work with the FRU list in the serviceable event view if there is one. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code. or 5794 IO drawer on a loop with clustered systems. otherwise use the FRU list documented here to determine the parts to exchange.Reference codes • xxxx 3201 indicates there are clustered systems on multiple HSL/RIO loops. You must convert the hexadecimal loop number into decimal format to recognize the loop number. If this is a serviceable event then perform RIOIP12. This is not a supported configuration. NOTE: A fiber optic cleaning kit may be required for optical HSL connections. • xxxx 3217 indicates there is a model 5791. High Speed Link (HSL) loop status message SVCDOCS HSL_LNK This is a serviceable event only if this error is in a serviceable event OPT_CLN view. 5792. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code. otherwise use the FRU list documented here to determine the parts to 128 (1xxx) System power control network (SPCN) reference codes SVCDOCS 6985 6986 TWRCARD PWRCBL 6987 HSL_LNK OPT_CLN 6990 SVCPROC 6991 to 6992 LICCODE . otherwise use the FRU list documented here to determine the parts to exchange. Platform LIC failure Work with the FRU list in the serviceable event view if there is one.

The local system or partition has stopped participating in HSL Opticonnect with the remote system or partition on the same HSL loop. Service processor failure Work with the FRU list in the serviceable event view if there is one. re-IPL the system and look for errors. User intervention required The system is in the process of terminating. Platform LIC detected an error SVCDOCS LICCODE Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. Possible reasons include: A fatal software or hardware error in the remote system or partition. If this is not possible. no service action required Information only. probably requires intervention at the remote system. no service action required Information only. (1xxx) System power control network (SPCN) reference codes 129 . HSL Opticonnect disconnected normally from a remote node. The local system or partition is participating in HSL Opticonnect with other systems or partitions on the same HSL loop. HSL OptiConnect normal connection to another system or partition. Opticonnect normal remote disconnection from OptiConnect participation. which most likely originates with the remote system or partition. no service action required. contact your next level of support. If the system does not terminate in a reasonable amount of time. otherwise use the FRU list documented here to determine the parts to exchange. or a power failure in the remote system. no service action required. HSL OptiConnect established connection normally. When all the partitions have terminated. System log entry only. an SRC indicating the exact cause will be shown on the operator panel. System log entry only. If no errors are found. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code. otherwise use the FRU list documented here to determine the parts to exchange. Examine both the local and remote HSL OptiConnected systems or partitions for problems on this HSL loop. Service processor failure Work with the FRU list in the serviceable event view if there is one. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code. The problem. The local system or partition disconnected from a remote system or partition due to an unexpected event or failure.Reference codes 6993 exchange. Possible reasons include: SVCPROC LICCODE 6994 SVCPROC 6995 69C2 69C3 69C6 • A remote system or partition went off line due to a normal power off or because HSL Opticonnect became disabled. one or more partitions may need to be terminated manually.

examine the Service Action Log (SAL) or serviceable event view. Correct any HSL or NIC problems you find with the remote and local systems or partitions. Look for problems on the same HSL loop that occurred at approximately the same time as this error. hang. Check for SRCs with FRUs that indicate problems with the following: • HSL cables • The HSL I/O bridge • Power in an expansion I/O tower or unit on this loop On the local system or partition. If a complete HSL loop did not exist before this error occurred. examine the SAL or serviceable event view on the remote system or partition. Look for HSL failures that occurred on the same HSL loop at approximately the same time as this error. If you find no problems with either the local or the remote systems or partitions. Be sure to record all words in the SRC. If you find no problems with either the local or the remote systems or partitions. Correct any problems you find with the remote and local systems or partitions that happened at approximately the same time and involve HSL Opticonnect or HSL loop components or Network Interface Controllers. it will automatically reconnect with this system or partition. Platform LIC detected an error Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. Look for failures on the same loop or with the Network Interface Controller that occurred at approximately the same time as this error. Examine the remote system or partition for problems. collect all the PAL information for this failure on both systems. Platform LIC detected an error SVCDOCS LICCODE Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. Licensed Internal Code will attempt to recover from the error. the cause of this error might be a failure or power down in an HSL component between the local system or partition and the remote system or partition. When the remote system is IPL'd. 69C7 SVCDOCS LICCODE 69C8 130 (1xxx) System power control network (SPCN) reference codes . or hardware failure. Examine the remote system or partition for problems. Possible causes include time out. collect all the Product Activity Log (PAL) information for this failure on both systems. The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. If the remote system or partition is powered on and IPL'd. Intervention at the local or remote system or partition might be required. The problem may be with the local system or partition or the remote system or partition. Contact your next level of support. Check for a problem with the following: • An HSL cable • The HSL I/O bridge • Power in an expansion I/O tower or unit on this loop On the local system or partition. the cause of this error might be a failure or power down in an HSL component between the local system or partition and the remote system or partition. examine the SAL or serviceable event view. Be sure to record all words in the SRC.Reference codes If a complete HSL loop did not exist before this error occurred. Contact your next level of support.

Platform LIC detected an error Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. Be sure to record all words in the SRCs. On the local system or partition. Examine the remote system or partition for problems. Collect all the Product Activity Log information for this failure on all systems and partitions on this HSL loop. Examine the remote system or partition for problems.Reference codes The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. examine the SAL or the serviceable event view. On the remote system or partition. Platform LIC detected an error 69C9 SVCDOCS LICCODE 69CF SVCDOCS LICCODE (1xxx) System power control network (SPCN) reference codes 131 . Possible causes are: • Licensed Internal Code problem where the local bus unit is offline. Licensed Internal Code will attempt to recover from the error. examine the SAL or serviceable event view. The local system or partition disconnected from a remote system or partition due to an failure in a Licensed Internal Code virtualized bus unit. Licensed Internal Code will attempt to recover from the error. examine the SAL or the serviceable event view. If there are no problems with the remote system or partition and there are no problems with the local system or partition then collect all the Product Activity Log information for this failure on all systems or partitions. All of the HSL OptiConnect connections on this loop will be in a failed state. examine the SAL or serviceable event view. Look for HSL failures on the same HSL loop or with the Network Interface Controller that occurred at approximately the same time as this error. Intervention at the local or remote system or partition might be required. Contact your next level of support. Look for problems on the same HSL loop or with the Network Interface Controller that occurred at approximately the same time as this error. • Licensed Internal Code problem where the remote bus unit is offline. Contact your next level of support. Be sure to record all words in the SRCs. Correct any problems you find with the remote and local systems or partitions that happened at approximately the same time and involve HSL Opticonnect or HSL loop components or Network Interface Controllers. Look for HSL Opticonnect problems that occurred at approximately the same time as this error. Possible causes are: • Time out of a critical message • Licensed Internal Code code / table problem • Network deadlock detected The problem may be with: • The local system or partition • The remote system or partition On the local system or partition. On the remote system or partition. Look for HSL Opticonnect failures that occurred at approximately the same time as this error.

On the local system or partition. On the remote systems or partitions. All systems participating in HSL OptiConnect will be disconnected.Reference codes Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. Verify that the cable is connected and the switch is powered on. When thresholded. This indicates the point where DMA can report changes in switch port states to SM via a TRAP and also that SM has received and accepted out responses to the initial gets. Look for HSL Opticonnect failures that occurred at approximately the same time as this error. This includes cases such as path migration. no service action required The cable connection to the Infiniband switch has been restored. System log entry only. No service action required. Look for HSL Opticonnect problems that occurred at approximately the same time as this error. System log entry only. Collect all the PAL information for this failure on all systems and partitions on this HSL loop. System log entry only. Does not require service. The system will contine to run with this Host Channel Adapter disabled. The CEC and switch firmware are now communicating. no service action required The cable connection to the Infiniband switch is broken. You must re-IPL the system to recover. no service action required Reported when the logical switch receives a setPortInfo for the switch management port that sets a new SM LID. examine the SAL or the serviceable event view. Before re-IPL'ing the system. Does not require service. System log entry only. start a platform dump. Licensed Internal Code internal error. An invalid High Speed Link (HSL) configuration was detected SVCDOCS An error was detected in the Infiniband fabric. After repairing the problem. Unrecognized command from Subnet Manager. verify that the connection has been restored by using the Infiniband Network Manager. Note that this will also tell us when a subnet merge has occurred and a new SM has issued a setPortInfo with an SMLID that differs from the previous one. This proves that there is 2-way communication. Contact your next level of support. Host Channel Adapter The Infiniband Host Channel Adapter has failed Platform LIC failure A Platform Licensed Internal Code error occurred related to Infiniband. 132 (1xxx) System power control network (SPCN) reference codes 69E1 69E2 HCA LICCODE 69E3 69E4 69E5 69E6 69E7 69E9 69EA . examine the SAL or the serviceable event view. Perform a platform dump prior to IPLing the system. No service action required. Be sure to record all words in the SRCs. Have the customer check for problems reported at the Infiniband Network Manager. no service action required Initial communication has occurred with the Subnet Manager. no service action required An Infiniband communications error occurred. no service action required Part of the HCA chip failed but was not terminating. System log entry only. Examine the remote systems or partitions for problems. after getting the dump. System log entry only. An IPL is required to recover the Host Channel Adapter. etc. these errors will result in a B70069E1.

Upgrade the adapter at the location given in the serviceable event view to a new version. The link is operational but operating at a bandwidth below its rated capacity. B9xx) Reference codes The A9xx and B9xx SRCs and their associated unit reference codes give information about the user program. look for other serviceable errors which occurred at same time frame. then a user may have initiated a function 22 prior to the operating system completing the IPL. Operating System error Platform Licensed Internal Code terminated a partition. Platform firmware detected an error Platform firmware detected unexpected or not valid data returned from non-platform firmware. This may lead to degraded I/O throughput. otherwise use the FRU list documented here to determine the parts to exchange. Verify that the Infiniband configuration is correct at the HCA. (1xxx) System power control network (SPCN) reference codes 133 . then contact your next level of support. then contact your next level of support. otherwise use the FRU list documented here to determine the parts to exchange. SVCDOCS 69EC SVCDOCS 69ED BAD1 NEXTLVL C2AC Contact your next level of support. LICCODE F104 SVCDOCS F105 If SRC word 3 is 0007. no service action required An InfiniBand cable connection initialized to a lower signal frequency. User intervention required An Infiniband configuration error was detected by the HCA. Collect all the SRC words and the platform system dump. System log entry only. System log entry only. SVCDOCS F103 No corrective action is required. The platform LIC detected an internal problem.Reference codes 69EB No service action required. Contact support for assistance. User intervention required An Infiniband adapter in the server does not support connections to I/O enclosures. or if SRC word 3 is not 0007. no service action required The Power On Demand License acceptance has completed. If a function 22 was not performed. Platform LIC detected an error NEXTLVL Work with the FRU list in the serviceable event view if there is one. (A9xx. The Port 1 and 2 configurations conflict. Platform LIC failure Work with the FRU list in the serviceable event view if there is one. The platform LIC detected an internal problem. Collect all the SRC words and the platform system dump.

• If you do not find a BAxx xxxx error code. Have the customer continue with the recommended recovery action. offers a link to instructions service actions for recovering from a hang on an attention code. see Working with Storage Dumps. • The second column. see (BAxx) Partition firmware reference (error) codes to find the code. The I/O configuration exceeds the recommended size. For example. It may also contain instructions for continuing the problem analysis. see Initial Program Load (IPL) Information. Note: If the logical memory block size is already 256 MB. (AAxx) Partition firmware reference (attention) codes Reference Code Description/Action Perform all actions before exchanging Failing Items AA00E158 Waiting for an SMS terminal to be created on the HMC AA00E159 Open a virtual terminal window on the HMC. 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. Support may need the information saved in this dump. Waiting for the serial connection to the service processor to be established Check the serial connection to the service processor. Note: Click the failing item code only when you experience a hang condition on an attention code. Waiting for the user to select the language and keyboard PFW1548 (1xxx) System power control network (SPCN) reference codes . Table 1. If a Licensed Internal Code error is suspected and the recovery action recommends an IPL. The AAxx table uses the following format: • The first column. such as opening a firmware console or checking serial connections. which offer information about the next target state for the platform firmware. These codes might also indicate that you need to perform an action. the user should contact the next level of support.Reference codes 1. (AAxx) Partition firmware reference (attention) codes Partition firmware posts AAxx system reference (attention) codes. contact your next level of support. AA00E175 Increase the logical memory block size to 256 megabytes (MB) and reboot the managed system. For additional help. see Problems with loading and starting the operating system (for AIXand Linux) to resolve the boot problem. • The third column. 3. which might indicate why the boot attempt failed. Refer the user to the Reference code list in Troubleshooting. then take a main storage dump to save the error conditions before the customer does an IPL. When you find a BAxx xxxx error code. offers a brief description about this SRC. Description/Action. 2. The system is booting to the open firmware prompt The system is booting to the System Management Services (SMS) menus. Reference Code. contains numbers that identify a particular action your server performs during initialization of firmware. Note: For a brief description of some of the C9xx codes. Failing Item. For more information. Some operating systems might crash when using this configuration. use the ASMI menus to inspect the progress code history: Failing Item AA00E1A8 AA00E1A9 PFW1548 PFW1548 AA00E1B0 134 • Look for a BAxx xxxx reference (error) code. Note: If the system or partition returns to the SMS menus (as indicated by this progress code) after a boot attempt failed. Correct all problems that are found. then follow the actions indicated to resolve the boot problem.

go to Problems with loading and starting the operating system. The firmware did not find an operating system image and it was unable to detect at least one hard disk in the boot list. 1. The system or partition was not able to find an operating system on any of the devices in the boot list. Verify that the boot list in the SMS menus is correct Bootable media is missing from a USB CD-ROM AA130013 AA130014 Put a bootable CD in the USB CD-ROM and retry the boot operation. of try another medium.Reference codes Select the language and keyboard. The media in the device in the bootlist was not found under the I/O adapter specified by the bootlist. Firmware is now retrying the entries in the boot list. Retry the operation. boot standalone AIX diagnostics from CD-ROM or a NIM server and run diagnostics against the device. AA060010 Increase the FAT partition size by 10% to keep the number of data clusters fewer than approximately 4080. Replace the media in the device with known-good media. enter the password for the admin user of the service processor A keyboard was not found Ensure that a keyboard is attached to the USB port assigned to the partition. Modify the boot list using the SMS menus so that it includes devices that are know to have a good copy of the operating system and retry the boot. Waiting for the user to accept or decline the license agreement AA00E1B1 Accept or decline the license agreement. Admin access password prompt AA00E1F3 On the firmware console. Verify that the boot disk belongs to the partition that is being booted 2. If AIX cannot be booted from another device. boot standalone AIX diagnostics from CD-ROM or a NIM server and run diagnostics against the device. If this problem persists. Verify that the medium (CD-ROM. The FAT file system on the boot disk is configured in a way that might cause a boot failure. The media in a device in the boot list was not bootable. (1xxx) System power control network (SPCN) reference codes 135 PFW1548 FWPWD AA060007 AA06000B AA06000C AA06000D AA06000E AA060011 . If is being booted. go to Problems with loading and starting the operating system. The adapter specified in the boot list is not present or is not functioning. If you are still unable to boot an operating system. do the following: 1. If you are still unable to boot an operating system or diagnostic CD-ROM. This error might occur before the initialization of an enclosure that contains the boot disk completes or when the boot disk belongs to another partition. then run online AIX diagnostics against the failing adapter. and can be booted from anther device. The media in a USB CD-ROM has been changed. If you are still unable to boot an operating system. do so. go to Problems with loading and starting the operating system. of modify the boot list to boot from another bootable device. If Linux is being booted. for example) from which you are trying to boot is bootable.

and serial number of the system. then retry the operation. and serial number. The system is waiting for someone to enter the machine type. check for server firmware updates and apply them. apply if available. 2. Find the unit reference code in the following table. if available. Failing items details. see Table 2. not serious Severe error detected by I/O card Licensed Internal Code Token-ring adapter card error Token-ring adapter card error (1xxx) System power control network (SPCN) reference codes . At the system prompt. PFW1548 Setenv/$setenv parameter error: the value contains a null character. Input value error in I/O card Licensed Internal Code A020 to A024 A025 Procedure error in I/O card Licensed Internal Code A027 Input value error in I/O card Licensed Internal Code A028 Input value error in I/O card Licensed Internal Code A029 Procedure error in I/O card Licensed Internal Code A02A to A02D Input value error in I/O card Licensed Internal Code A02E Wrong frame received from remote equipment A02F Input value error in I/O card Licensed Internal Code A201 Token-Ring controller storage not available A202 to A204 Input value error in I/O card Licensed Internal Code A205 I/O card Licensed Internal Code received unexpected response A206 to A20B Input value error in I/O card Licensed Internal Code A20C Input value error in I/O card Licensed Internal Code A213 to A214 A402 A403 A404 A405 to A406 A408 A409 A40A A40B to A40C 136 Failing Item PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH UJE39 PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH IOA PTFSRCH IOA IOA UJE37 IOA UJE37 IOA IOA IOA Severe error detected by I/O card Licensed Internal Code Token-ring adapter card error Token-ring adapter card error Token-ring adapter card error Token-ring adapter card error Ring status information logged. Use the operating system utility to set the system clock. model.Reference codes AA170210 AA170211 2. which follows the reference code table below. Check for server firmware updates. Setenv/$setenv parameter error: the name contains a null character. For more on the Failing Item column entries. Table 1. (B005) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items A000 to A002 Input value error in I/O card Licensed Internal Code A003 Procedure error in I/O card Licensed Internal Code A004 to A00C Input value error in I/O card Licensed Internal Code A00E Procedure error in Licensed Internal Code A010 to A012 Input value error in I/O card Licensed Internal Code A013 Wrong config data given to local area network controller A014 to A01F. If the problem persists. model. PFW1548 The server firmware function to get and set the time-of-day clock reported an error 1. AA190001 AA260001 (B005) Reference codes This SRC might indicate a communications error. type the machine type.

serious Ring status information logged. not serious Ring status information logged. not serious Wrong frame received from remote equipment Token-ring adapter card error Token-ring adapter card error Token-ring adapter card error Token-ring adapter card error Token-ring adapter card error Change the line speed parameter for the Token-ring card. serious Address not recognized. UJE37 FI00712 FI00701 IOA UJE33 UJE33 IOA FI00701 FI00712 IOA IOA FI00701 FI00712 UJE31 UJE37 UJE37 UJE37 IOA FI00712 FI00701 UJE37 FI00712 FI00701 FI00701 FI00712 IOA UJE37 IOA UJE37 UJE35 FI00712 IOA UJE35 UJE32 UJE37 UJE31 UJE37 PTFSRCH UJE37 FI00712 FI00701 USER A425 A426 A427 A428 A429 A42A Note: The card must be varied off before changing the line speed. not serious Ring status information logged. error limit per 256 reached Access priority not authorized. error limit per 256 reached Transmit beacon. The adapter does not support Full DUPLEX or did not detect Full Duplex. error limit per 256 reached Frame not copied. not serious Ring status information logged. error limit per 256 reached Transmit strip. error limit per 256 reached Frames not authorized. error limit per 256 reached A703 A710 A711 A712 A713 A714 A715 A716 IOA FI00701 UJE37 UJE37 IOA PTFSRCH UJE39 IOA PTFSRCH IOA UJE37 PTFSRCH PTFSRCH IOA UJE37 IOA UJE37 137 (1xxx) System power control network (SPCN) reference codes . serious Ring status information logged.Reference codes A410 A411 A412 A413 A414 A415 A416 A417 A420 A421 A422 A423 A424 Ring status information logged. error limit per 256 reached Temporary errors. Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Token-ring adapter card error Procedure error in I/O card Licensed Internal Code User suspected communications problem. serious Ring status information logged. Ring status information logged.

error limit per 256 reached Frames discarded. Nearest active upstream node See the service documentation for instructions. Token-ring network or remote station See the service documentation for (1xxx) System power control network (SPCN) reference codes . Token-ring network manager program See the service documentation for instructions. error limit per 256 reached Interrupts not expected. Local Communications Adapter configuration See the service documentation for instructions. ADPTADR value in CRTLINTRN command See the service documentation for instructions. Token-ring network manager program See the service documentation for instructions. Communications I/O processor card See the service documentation for instructions. I/O card Licensed Internal Code error Configuration report server is deactivating Configuration report server is activating Procedure error in Licensed Internal Code Output value error in Licensed Internal Code Configuration report server activation failed I/O card Licensed Internal Code error Procedure error in Licensed Internal Code Required I/O card Licensed Internal Code not active UJE38 PTFSRCH UJE38 IOA PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH FI00701 UJE35 UJE37 FI00712 IOA PTFSRCH C000 C003 C005 C010. Failing items details Failing Item IOA IOP PTFSRCH UJE31 UJE32 UJE33 UJE34 UJE35 UJE35 UJE37 138 Description Token-ring network adapter Document Description See the service documentation for instructions. error limit per 256 reached I/O card Licensed Internal Code error Procedure error in Licensed Internal Code Token-ring error monitor has stopped Procedure error in Licensed Internal Code Output value error in Licensed Internal Code Required I/O card Licensed Internal Code not active B300 B700 Procedure error in Licensed Internal Code Wrong frame received from remote equipment All unit reference codes that start with a value of B7 and end with any value from 00 through FF have the same meaning as this unit reference code. Licensed Internal Code See the service documentation for instructions. PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH PTFSRCH UJE34 FI00701 UJE35 UJE37 FI00712 IOA PTFSRCH USER Table 2.Reference codes A718 A719 A721 B000 B003 B006 B009 B00A to B00B B0C0 Status queue overrun. Local area network busy because of See the service documentation for maximum usage instructions. C0E6 C0E7 to C0E8 C0E9 to C0EB C0EE C0EF C0F4 C300 C700 to C701 C702 to C703 FFFF Procedure error in Licensed Internal Code Procedure error in Licensed Internal Code Wrong frame received from remote equipment User suspected communications problem.

(B006) Common Licensed Internal Code reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 1201 I/O processor resource not available A deactivation failed to get a resource controlled by Licensed Internal Code. For more on the Failing Item column entries. I/O processor resource not available A resource needed to perform a requested function is not available in the Licensed Internal Code. Table 1. Not valid condition in I/O Processor Licensed Internal Code An error in an activation or deactivation occurred. Not valid condition in I/O Processor Licensed Internal Code AJEQU00 AJDG301 FI00131 The Licensed Internal Code found a condition that should not have occurred. 2. see Table 2. Common Licensed Internal Code failing items details. See the service documentation for instructions.Reference codes UJE38 UJE39 USER Token-ring controller card work load exceeded Remote computer equipment User suspected communications problem. System bus error FI00131 ANYBUS AJEQU00 AJDG301 A permanent I/O processor failure occurred 139 1211 1212 (1xxx) System power control network (SPCN) reference codes . 1. Not valid condition in I/O Processor Licensed Internal Code Failing Item AJEQU00 AJDG301 AJEQU00 AJDG301 FI00131 AJEQU00 AJDG301 1202 1203 1204 1205 to 1206 1207 1208 1209 1210 AJEQU00 AJDG301 The Licensed Internal Code has recovered from a condition that was not FI00131 expected. I/O processor was not ready for interrupt that occurred AJEQU00 FI00131 I/O processor resource not available The I/O processor error log is being filled faster than the errors are being reported to the system. (B006) Common Licensed Internal Code reference codes The common Licensed Internal Code detected a failure. See the service documentation for instructions. These 4 characters are the unit reference code. Look at characters 5 through 8 of the top 16 character line of function 11 (4 rightmost characters of word 1). Check other errors reported to the system and correct them. I/O processor card or Licensed Internal Code error AJEQU00 FI00131 A microprocessor exception occurred on the I/O processor. Find the unit reference code in the following table. See the service documentation for instructions. instructions. FI00132 I/O processor resource not available AJEQU00 AJDG301 The Licensed Internal Code could not allocate memory resources on the I/O processor card. which follows the reference code table below.

Reference codes 1213 1214 to 1215 1301 System bus error I/O processor card or Licensed Internal Code error I/O processor resource not available An activation or deactivation failed to get a resource controlled by Licensed Internal Code. FI00132 Not valid condition in I/O Processor Licensed Internal Code AJDGP01 AJDG301 The Licensed Internal Code found a condition that should not have FI00131 occurred. Not valid condition in I/O Processor Licensed Internal Code An error in an activation or deactivation occurred. System bus error FI00131 ANYBUS AJDGP01 AJDG301 A permanent I/O processor failure occurred FI00131 AJDGP01 System bus error AJDG301 AJDGP01 FI00131 I/O processor card or Licensed Internal Code error AJDGP01 FI00132 FI00131 I/O processor card error SVCDOCS Display the Service Action Log entry for this SRC. Perform the following: 1311 1312 1313 1316 1317 140 (1xxx) System power control network (SPCN) reference codes . This is a recoverable error. I/O processor was not ready for interrupt that occurred AJDGP01 FI00131 FI00132 FI01117 I/O processor resource not available The I/O processor error log is being filled faster than the errors are being reported to the system. Not valid condition in I/O Processor Licensed Internal Code 1304 1305 to 1306 1307 1308 1309 1310 AJDGP01 AJDG301 The Licensed Internal Code has recovered from an unexpected FI00131 condition. If the Failing Item indicates IOP. then replace the IOP. Check other errors reported to the system and correct them. then do NOT replace the IOP. BACKPLN I/O processor resource not available AJDGP01 AJDG301 The Licensed Internal Code could not allocate memory resources on the IOACNFG I/O processor card. FI00132 I/O processor card or Licensed Internal Code error AJDGP01 FI00131 FI00132 A microprocessor exception occurred on the I/O processor. FI00131 AJEQU00 AJDG301 AJEQU00 FI00131 FI00131 AJEQU00 CDAWKLD AJDGP01 AJDG301 AJDGP01 AJDG301 FI00131 FI00132 IOACNFG AJDGP01 AJDG301 1302 1303 I/O processor resource not available A resource needed to perform a requested function is not available in the Licensed Internal Code. If the Failing Item indicates SVCDOCS.

(1xxx) System power control network (SPCN) reference codes 141 . FI00130 AJDG301 The Licensed Internal Code has recovered from a condition that was not FI00131 expected. FI00132 I/O processor resource not available FI00130 AJDG301 A resource that is needed to perform a requested function is not CDAWKLD available in the Licensed Internal Code. Recovered from condition in Licensed Internal Code.Reference codes 1. FI00132 I/O processor resource not available CDAWKLD FI00132 The Licensed Internal Code could not allocate memory resources on the FI00130 I/O processor card. FI00132 I/O processor card or Licensed Internal Code error FI00130 FI00131 A microprocessor exception occurred on the I/O processor. Other resources attached to the IOP may then need to be Varied On. 2. Service processor Licensed Internal Code failed 1318 1403 FI00131 AJDGP01 SVCPROC AJDGP01 SVCPROC AJDGP01 SVCPROC 1404 1405 1406 1407 1408 1409 1A01 1A02 1A03 1A04 1A05 to 1A06 1A07 1A08 1A09 AJDGP01 SVCPROC A microprocessor exception occurred on the Service processor. AJDG301 Service processor Licensed Internal Code failed AJDGP01 SVCPROC The Licensed Internal Code could not allocate resources on the Service AJDG301 processor. Service processor Licensed Internal Code error The Licensed Internal Code has recovered from an unexpected condition. Service processor Licensed Internal Code error A recoverable microcode condition occurred on the Service processor. AJDG301 Not valid condition in I/O Processor Licensed Internal Code FI00130 FI00131 The Licensed Internal Code found a condition that should not have FI00132 occurred. Service processor Licensed Internal Code failed AJDGP01 AJDG301 SVCPROC Service processor Licensed Internal Code failed AJDGP01 SVCPROC The Service processor was not ready for an interrupt that occurred. perform the VRYCFG RESET(*YES) command to reset the IOP and Vary On attached resources. If the I/O Processor is not operable and disk units are attached. If in communications. the line is still running. If disk units are not attached. use Hardware Service Manager to re-IPL the IOP. I/O processor resource not available CDAWKLD FI00130 A deactivation failed to get a resource controlled by Licensed Internal AJDG301 Code. Not valid condition in I/O Processor Licensed Internal Code FI00130 FI00131 An error in an activation or deactivation occurred. Threshold overflow FI00131 FI00132 The I/O processor card has detected a threshold of recoverable error FI01117 conditions. I/O processor card error Service processor Licensed Internal Code error A resource needed to perform a requested function is not available in the Licensed Internal Code. The errors are either wrong interruptions or memory error FI00130 corrections.

Operating voltage or temperature range limits exceeded. Symbolic FRU Isolation Problem Analysis. or a communications I/O processor code problem. Operating voltage or temperature range limits exceeded. After you correct the conditions. Table 1. see Table 2. Find the unit reference code in the following table. Table 2. Common Licensed Internal Code failing items details Failing Item AJDG301 AJDGP01 AJDGP01 AJEQU00 ANYBUS BACKPLN CDAWKLD IOACNFG SVCDOCS SVCPROC Description Licensed Internal Code Licensed Internal Code I/O processor Licensed Internal Code I/O processor Licensed Internal Code System bus Card enclosure or backplane Too many communications lines in use Configuration error Customer engineer directed to system problem analysis Service Processor Card Document Description Service Functions. Correct any conditions in the physical environment which might have caused the voltage or temperature out-of-range error on the 4758 adapter card. Symbolic FRU Isolation Problem Analysis. APAR or LICTR Problem Analysis. Symbolic FRU Isolation Problem Analysis. Failing items details. vary off and then vary back on the 4758 device description associated with the 4758 adapter card. Tampering of cryptographic card suspected.Reference codes 1A10 Note: If a large number of these errors occur during a short time. Error reported to system The I/O processor error log is being filled faster than the errors are being reported to the system. Check other errors reported to the system and correct them. APAR or LICTR Service Functions. a defective communications I/O processor card or modem. APAR or LICTR Service Functions. Symbolic FRU Isolation (B013) Reference codes This SRC might indicate a cryptographic adapter error. Symbolic FRU Isolation Problem Analysis. APAR or LICTR Service Functions. they may be caused by an electrically noisy environment. I/O adapter hardware error detected Tampering of cryptographic card suspected. For more on the Failing Item column entries. (B013) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 6601 I/O adapter hardware error detected 6602 6603 6604 An I/O processor Licensed Internal Code error occurred. Correct any conditions in the physical environment which might have 142 (1xxx) System power control network (SPCN) reference codes Failing Item IOA PTFSRCH IOP PTFSRCH IOA IOP IOA IOP PTFSRCH CARDTMP 6611 6613 6614 IOA PTFSRCH IOA PTFSRCH CARDTMP . which follows the reference code table below.

See the service documentation for instructions. (B015) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items A555. A5F5. which follows the reference code table below. A5F1 to A5F3. Failing items details Failing Item CARDTMP IOA IOP LOADCY1 PTFSRCH Description Operating voltage or temperature range limit exceeded I/O adapter card I/O processor card I/O card Licensed Internal Code Licensed Internal Code Document Description See the service documentation for instructions. After you correct the conditions. but should be replaced during the next scheduled maintenance of the system. See the service documentation for instructions. A837 A83C A83D Procedure error in Licensed Internal Code Procedure error in Licensed Internal Code Input value error in I/O card Licensed Internal Code Procedure error in Licensed Internal Code Procedure error in Licensed Internal Code Procedure error in Licensed Internal Code Failing Item FI00730 UJE36 AJDG301 FI00730 AJDG301 AJDG301 FI00730 AJDG301 AJDG301 AJDG301 FI00730 AJDG301 FI00730 143 (1xxx) System power control network (SPCN) reference codes . A5AA. A5EE. A5F9 to A5FA. LOADCY1 PTFSRCH IOA IOA PTFSRCH IOA PTFSRCH Table 2. A5FC A800 I/O card Licensed Internal Code failed A802 to A804 Input value error in I/O card Licensed Internal Code A807 Input value error in I/O card Licensed Internal Code A814 A820 A821. no service action required Adapter monitoring circuitry has failed. A5F7. System log entry only. (B015) Reference codes This SRC might indicate a communications error. Find the unit reference code in the following table. I/O card Licensed Internal Code failed A5DD. vary off and then vary back on the device description associated with the cryptographic adapter card. See the service documentation for instructions. Table 1. A823 A825. A5E1 to A5E2. Failing items details. The adapter can be varied on and used. Adapter monitoring circuitry has exceeded threshold. For more on the Failing Item column entries.Reference codes 6615 6616 6617 6618 caused the voltage or temperature out-of-range error on the cryptographic adapter card. see Table 2. Cryptographic adapter LIC not loaded or not valid. See the service documentation for instructions.

see Table 2. 9001 Information only.Reference codes A845 to A847 AA09 AA10 AA13. See the service documentation for instructions. Failing items details. See the service documentation for instructions. which follows the reference code table below. Find the unit reference code in the following table. AA16 AA17 to AA18 AF04 AF05. Failing Item CRYPBAT (B026) Reference codes This SRC might indicate a communications error. (B017) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 0001 Low battery condition detected on IOA. AF07 AF08 AF09 AFFF Input value error in I/O card Licensed Internal Code Response from I/O card Licensed Internal Code not expected Number of stations greater than allowed in configuration Procedure error in I/O card Licensed Internal Code I/O card Licensed Internal Code failed Wrong response received from I/O card Licensed Internal Code Local area network adapter. Failing items details Failing Item CRYPBAT Description Cryptographic adapter battery Document Description See the service documentation for instructions. which follows the reference code table below. remote station error Wrong response received from I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Procedure error in Licensed Internal Code AJDG301 FI00730 UJE35 FI00730 FI00730 AJDG301 UJE39 FI00730 FI00730 AJDG301 FI00730 UJE34 Table 2. (B026) Reference codes 144 (1xxx) System power control network (SPCN) reference codes . no service action required Table 2. See the service documentation for instructions. see Table 2. Failing items details. (B017) Reference codes This SRC might indicate a cryptographic adapter error. Find the unit reference code in the following table. Failing items details Failing Item AJDG301 UJE34 UJE35 UJE36 UJE39 Description Licensed Internal Code Local area network busy because of maximum usage MAXCTL value in CRTLINTRN command Lack of I/O processor resources Remote computer equipment Document Description See the service documentation for instructions. For more on the Failing Item column entries. For more on the Failing Item column entries. Table 1. See the service documentation for instructions. Table 1.

145 (1xxx) System power control network (SPCN) reference codes . See the service documentation for instructions. Failing Item FI00730 FI00730 AJDG301 FI00730 FI00730 FI00730 FI00730 IOA AJDG301 AJDG301 FI00730 AJDG301 FI00730 AJDG301 FI00730 AJDG301 FI00730 FI00730 AJDG301 FI00730 FI00730 FI00730 AJDG301 FI00730 AJDG301 AJDG301 FI00730 FI00730 FI00730 AJDG301 FI00730 AJDG301 AJDG301 AJDG301 FI00730 AJDG301 FI00730 FI00730 IOA IOP IOA AJDG301 AJDG301 AJDG301 AJDG301 FI00730 IOA USER Table 2. See the service documentation for instructions.Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items A000 I/O card Licensed Internal Code error A001 Input value error in I/O card Licensed Internal Code A002 A003 A013 A01B A01C A01D A01F A020 A022 A027 A028 A02A A02B A02C A02D A030 A201 A203 to A204 A205 A206 A209 A20A to A20B A20C A210 A213 A300 to A302 A40B A6C2 A6D4 A6D5 A6D6 A6D7 A710 FFFF Input value error in I/O card Licensed Internal Code Procedure error in I/O card Licensed Internal Code Address error on communications IOP card Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code I/O card Licensed Internal Code error Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Procedure error in I/O card Licensed Internal Code Communications adapter detected storage access error Input value error in I/O card Licensed Internal Code Licensed Internal Code received not correct response Input value error in I/O card Licensed Internal Code Procedure error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Procedure error in I/O card Licensed Internal Code I/O card Licensed Internal Code error I/O adapter hardware error detected Address error on communications IOP card I/O card Licensed Internal Code error Procedure error in I/O card Licensed Internal Code Input value error in I/O card Licensed Internal Code Adapter card detected not valid data Adapter card detected not valid data I/O adapter hardware error detected User suspected communications problem. Failing items details Failing Item AJDG301 IOA IOP Description Licensed Internal Code Communications adapter card Communications I/O processor card Document Description See the service documentation for instructions.

See (B1xx) Service processor firmware reference code descriptions for a description of the SRC. Table 1. configuration. How to determine the nature of a (B1xx) reference code Where you found the SRC (HMC) 146 How to determine the nature of the SRC (1xxx) System power control network (SPCN) reference codes . See Control Panel in the following table. Is the system console available? ♦ Yes: ◊ For AIX see AIX in the following table. ◊ For Integrated Virtualization Manager see Integrated Virtualization Manager in the following table. (B045) Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 0C00 I/O card Licensed Internal Code failed Failing Item FI00730 (B1xx) Service processor firmware reference codes A B1xx reference code indicates that an event or exception occurred in service processor firmware. determine if the SRC requires a service action or if it is for tracking purposes only.Reference codes UJ9GC UJ9GF USER configuration External devices or network User suspected communications problem. The system console is not available. Find the unit reference code in the following table. See Advanced System Management Interface (ASMI) in the following table. ♦ No: Continue. If you do not find the SRC in a serviceable event view then it is a tracking event only and does not require service." or "temp" in the and the Advanced System Manage Interface (ASMI). or ASMI listed under serviceable events. (B045) Reference codes This SRC might indicate a communications error. ♦ Otherwise work on the SRC from the control panel. the . installed features. model. ♦ No: Continue. Diagnostics analyze an event when it occurs to determine if the event requires service or if the event will only be recorded for tracking purposes and future reference. Determine whether service action is needed or not. ◊ For Linux see Linux in the following table. Is the system managed by an HMC? ♦ Yes: HMC. the system control panel. the . Tracking events appear as "informational" or "Misc. topology and activations at the time of the event. 2. the HMC Service Focal Point. then work on the SRC by looking at the Advanced System Management Interface (ASMI). it is based upon where to work with the B1xx SRC: 1. The determination is based on machine type. the Linux Diagnostic Messages Log. See Hardware Management Console (HMC) in the following table. the Integrated Virtualization Manager Service Focal Point. See the service documentation for instructions. ♦ If you have a PC you can attach to one of the HMC ports and launch a browser. 3. Table 1. See the service documentation for instructions. Serviceable event views are the AIX Diagnostics Results Log. See the service documentation for instructions. To resolve any B1xx reference code.

See (B1xx) Service processor firmware reference code callouts for instructions. (B1xx) Service processor reason codes' ranges. If the SRC is in the Miscellaneous event logs row. see (B1xx) Service processor firmware reference codes for instructions. B1xxyyyy where: xx= Indicates the subsystem where the event or error occurred. it is for tracking purposes only and does not require service. (B1xx) Service processor reason codes' ranges lists ranges of B1xx SRCs in the format B1xx yyyy. • If you do not find the SRC in the Diagnostics Message Log. • Table 3. it requires a service action. AIX • If you find the SRC in the Diagnostics Results Log. it requires a service action. (B1xx) Service processor subsystem IDs. see the table in Displaying error and event logs. Look in the Service Focal Point. • If you find the SRC in the Diagnostics Message Log. it requires a service action. it is for tracking purposes only and does not require service. If the SRC is in the Error logs row. (B1xx) SRC Descriptions lists B1xx SRCs and descriptions. • If you find the SRC in the Service Focal Point. To determine if the SRC requires repair action or not using ASMI. This table includes the reason code and a more detailed description of the exception in the firmware or in a firmware operation. (1xxx) System power control network (SPCN) reference codes 147 . where yyyy refers to a series of characters (called the reason code). it is for tracking purposes only and does not require service. • If you do not find the SRC in the Diagnostics Results Log. A B1xx reference code indicates that an event or exception occurred in a service processor firmware-detected operation. then service is needed. Collect SRC and system information (if possible). Select that log and Show Details to get the full detail format of the log. • If you do not find the SRC in the Service Focal point. Look in the diagnostics results log. • If you do not find the SRC in the Service Focal Point. Linux Integrated Virtualization Manager Advanced System Management Interface (ASMI) Control Panel (B1xx) Service processor firmware reference code descriptions If you wish to determine if the SRC requires a service action or if it is for tracking purposes only. • If you find the SRC in the Service Focal Point. See Using Service Focal Point for the HMC for help in using the Service Focal Point. (B1xx) SRC Descriptions for a list of B1xx SRCs and descriptions. See Using the control panel to collect reference codes and system information. For details. it requires a service action. The following tables describe the B1xx SRCs. • Table 2. See Table 3. yyyy= The reason for the event or error (reason code). • Table 1. Note: The Linux Service Aids must be installed to view the message log: If these Service Aids are not installed then the message log entries can not be viewed. it is for tracking purposes only and does not require service. Look in the diagnostics message log. then no repair action is needed. Then. See Table 1.Reference codes Search for the SRC in the Service Focal Point on the HMC. Note: See Table 2. see Using Service Focal Point for the Integrated Virtualization Manager. (B1xx) Service processor subsystem IDs lists ranges of B1xx Service processor subsystem IDs and gives a general description of the associated event or error. use the Callout section of the Error and Event Logs and (B1xx) Service processor firmware reference code callouts.

VPD device and interface event or error reported by the service processor. Removal media event or error reported by the service processor. Service processor event or error reported by the service processor. SMA hub event or error reported by the service processor. Connection monitoring error: service processor lost communication with the HMC. JTAG device and interface event or error reported by the service processor. Test tool event or error reported by the service processor. Control panel event or error reported by the service processor. Informational event reported by the service processor. Platform firmware event or error reported by the service processor. Processor Host Bridge (PHB) event or error reported by the service processor. Multiple subsystems event or error reported by the service processor. I/O device event or error reported by the service processor. Memory bus interface event or error reported by the service processor. Power/cooling subsystem and control event or error reported by the service processor. I/O hub (Remote I/O) event or error reported by the service processor. Fan or other air moving device event or error reported by the service processor. I/O adapter event or error reported by the service processor. Processor/system bus controller and interface event or error reported by the service processor. EADS/EADS-X global event or error reported by the service processor. Processor chip (including internal cache) event or error reported by the service processor. I/O processor event or error reported by the service processor. Memory subsystem event or error reported by the service processor. Remote I/O loop and associated I/O hub event or error reported by the service processor. Power supply event or error reported by the service processor. (B1xx) Service processor subsystem IDs Subsystem ID 10 11 12 13 14 20 21 22 23 24 25 30 31 32 33 34 35 36 37 38 39 3A 40 46 50 51 55 56 57 58 59 5A 5B 60 61 62 63 70 71 72 73 74 75 76 7B 7C 7D 80 148 Description Processor subsystem event or error reported by the service processor. Remote I/O loop and associated I/O bridge event or error reported by the service processor. I/O bus interface event or error reported by the service processor. External cache event or error reported by the service processor. Memory card/FRU event or error reported by the service processor. Clock and control event or error reported by the service processor. Connection monitoring error: HMC lost communication with a logical partition. I2C device and interface event or error reported by the service processor. Processor unit (CPU) event or error reported by the service processor. HMC subsystem and hardware event or error reported by the service processor. (1xxx) System power control network (SPCN) reference codes . System unit hardware event or error reported by the service processor. Power control hardware event or error reported by the service processor. Storage/memory device on service processor event or error reported by the service processor. EADS/EADS-X slot event or error reported by the service processor. invalid event or error reported by the service processor. I/O bridge event or error reported by the service processor. Time-of-day hardware (including the battery) event or error reported by the service processor. Connection monitoring error: service processor lost communication with the server firmware. Memory DIMM event or error reported by the service processor. Memory controller event or error reported by the service processor. I/O subsystem event or error reported by the service processor.Reference codes Table 1. Unknown. Processor FRU event or error reported by the service processor. Other event or error reported by the service processor.

HMC code or firmware event or error reported by the service processor. User error reported by the service processor. Software event or error reported by the service processor. Room (ambient) temperature event or error reported by the service processor. Bulk power firmware event or error reported by the service processor. Table 2. Server firmware event or error reported by the service processor. SPCN firmware event or error reported by the service processor. (B1xx) SRC Descriptions Reference Code B103F684 B104FAA9 B110E500 B110F138 B110F139 B110F141 B110F7B0 B110F7B1 B110F7B2 B110F7B3 B110F7B4 B110F7B5 B110F7B6 B110F7B7 B111E500 B111F64B B111F658 B111F665 B112E500 B112F64E B112F65B B112F66E B112F66F B112F670 B113E500 B114E500 B114F2DF B114F663 B114F66C B114F66D Description Action Xscoms are not supported Determine if service action or tracking event Failed trying to get pointer to functional unit Determine if service action or tracking event group for type Bad hardware Determine if service action or tracking event Scom attention detected on the current chip Determine if service action or tracking event Master Attention Alone detected Determine if service action or tracking event Indicates a potential problem with clock card Determine if service action or tracking event The interposer plug count for the MCM in the Determine if service action or tracking event callout has exceeded the limit The interposer plug count for the MCM in the Determine if service action or tracking event callout has exceeded the limit The interposer plug count for the MCM in the Determine if service action or tracking event callout has exceeded the limit The interposer plug count for the MCM in the Determine if service action or tracking event callout has exceeded the limit The interposer plug count for the MCM in the Determine if service action or tracking event callout has exceeded the limit The interposer plug count for the MCM in the Determine if service action or tracking event callout has exceeded the limit The interposer plug count for the MCM in the Determine if service action or tracking event callout has exceeded the limit The interposer plug count for the MCM in the Determine if service action or tracking event callout has exceeded the limit Bad hardware Determine if service action or tracking event Fabric latency calculation packet not received Determine if service action or tracking event on processor Invalid fabric rotation length Determine if service action or tracking event Processor's POR State Machine not at idle Determine if service action or tracking event after free running logic reset Bad hardware Determine if service action or tracking event PLL Health check failed on Trimaran Determine if service action or tracking event Invalid L2 Slice Configuration Determine if service action or tracking event Handling CE detected by the fabric firs and the Determine if service action or tracking event L3 firs Handle errors detected by L3 firs and the ebist Determine if service action or tracking event engine Handle CE detected by L3 firs Determine if service action or tracking event Bad hardware Determine if service action or tracking event Bad hardware Determine if service action or tracking event Fatal IAP Error Determine if service action or tracking event Fabric initialization failed on processor Determine if service action or tracking event Clock period from Fabric out of calculated Determine if service action or tracking event range Operation attempted on nonfunctional Determine if service action or tracking event Functional unit 149 (1xxx) System power control network (SPCN) reference codes . External environment event or error reported by the service processor Input power source (AC) event or error reported by the service processor.Reference codes 81 82 85 86 87 90 A0 A1 A2 A3 Service processor firmware event or error reported by the service processor.

so Determine if service action or tracking event they form an invalid memory group Fir bit UE (uncorrectable error) during maintenance scrub or L3 connections test Determine if service action or tracking event display Maintenance CE threshold exceeded during maintenance scrub or L3 connections test Determine if service action or tracking event display The DIMMS in the callout list are on a processor card that only allows quad stacked Determine if service action or tracking event DIMMs The system resource(s) in the callout list failed Determine if service action or tracking event a system configuration test Bad hardware Determine if service action or tracking event Failed JTAG function call Determine if service action or tracking event POR Complete not reached on SMI2. Maintenance command timed Determine if service action or tracking event out Handling CE detected by the Fabric firs and Determine if service action or tracking event the L3 firs This level of hardware does not support 8GB Determine if service action or tracking event DIMMs that require ranks 8-15 Fir bit indicates MC CE Determine if service action or tracking event The memory controller gets clock errors with Determine if service action or tracking event both clock inputs Bad hardware Determine if service action or tracking event The DIMMs in the callout list are part of an Determine if service action or tracking event incomplete group because of missing DIMMs The DIMMS in the callout list don't match. Chip is Determine if service action or tracking event most likely locked up PLL Lock Failure (PLL is unlocked) Determine if service action or tracking event SMI didn't exit power down mode after Exit Determine if service action or tracking event Power Down maintenance command executed Clock period from SMI out of calculated range Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .Reference codes B114F66E B114F6A1 B114F6A2 B114F6C1 B114F6D0 B114F6D1 B114F6D2 B114F6D3 B114F7A4 B114FB53 B120E500 B120F228 B120F667 B120F685 B121E500 B121F2DF B121F666 B121F66A B121F66B B121F66E B121F684 B121F690 B121F7A5 B123E500 B123F642 B123F643 B123F667 B123F669 B123F688 B123F7BB B124E500 B124F622 B124F62A B124F64E B124F65F B124F66C 150 Handling CE detected by the Fabric firs and Determine if service action or tracking event the L3 firs Processor chip didn't have all zeros in the ring Determine if service action or tracking event scanned Processor chip didn't have all ones in the ring Determine if service action or tracking event scanned Actual Processor chip lbist signature didn't Determine if service action or tracking event match the expected values Processor chip abist timeout Determine if service action or tracking event Processor chip abist fail Determine if service action or tracking event Processor chip missing fusemap data in VPD Determine if service action or tracking event No repairs found for pending array repair Determine if service action or tracking event Processor gets clock errors with each clock Determine if service action or tracking event input Wiretest has detected an EST error Determine if service action or tracking event Bad hardware Determine if service action or tracking event A memory block trying to be referenced is out Determine if service action or tracking event of range Fir bit UE (uncorrectable error) during maintenance scrub or L3 connections test Determine if service action or tracking event display Single-shot command never completed Determine if service action or tracking event Bad hardware Determine if service action or tracking event Undetermined failure on IAP Determine if service action or tracking event Fir bit indicates problem with memory Determine if service action or tracking event controller Cache line write buffer CEs after a flush if Determine if service action or tracking event Manufacturing mode set No fir bits on.

Reference codes B124F68D B124F68E B124F68F B124F690 B124F691 Fir bit indicates problem with SP code or SMI Determine if service action or tracking event Fir bit indicates interface problem with DIMMs Determine if service action or tracking event Fir bit indicates interface CEs with DIMMs Determine if service action or tracking event Fir bit indicates MC CE Determine if service action or tracking event SMI Masked Fir Bit On Determine if service action or tracking event SMI2 lbist signature didn't match the expected B124F6C7 Determine if service action or tracking event values B125E500 Bad hardware Determine if service action or tracking event B125F622 Failed JTAG function call Determine if service action or tracking event Timed out waiting for Trimaran LBIST to B125F62A Determine if service action or tracking event complete Clock period from Trimaran out of calculated B125F66C Determine if service action or tracking event range Handling CE detected by the Fabric firs and B125F66E Determine if service action or tracking event the L3 firs Handle errors detected by L3 firs and the ebist B125F66F Determine if service action or tracking event engine B125F670 Handle CE detected by L3 firs Determine if service action or tracking event B125F671 Trimaran not ready for ebist Command Determine if service action or tracking event Trimaran didn't pass setting the ring to all B125F6A7 Determine if service action or tracking event zeros B125F6A8 Trimaran didn't pass setting the ring to all ones Determine if service action or tracking event Trimaran lbist signature didn't match the B125F6C4 Determine if service action or tracking event expected values B125FAA1 Ebist engine timed out Determine if service action or tracking event B125FAA5 L3 Address to be deleted Determine if service action or tracking event B125FAA7 Error detected by EBIST engine Determine if service action or tracking event B130E500 Bad hardware Determine if service action or tracking event B130F2DF Fatal IAP Error Determine if service action or tracking event B131F138 Scom attention detected on the current chip Determine if service action or tracking event B131E500 Bad hardware Determine if service action or tracking event The part found in RID location is not supported B131F242 Determine if service action or tracking event in this configuration B131F2DF Fatal IAP Error Determine if service action or tracking event Auto TLAR calculation failed. Acknowledge B131F64B Determine if service action or tracking event never received B131F64E PLL Lock Failure (PLL is unlocked) Determine if service action or tracking event B131F657 Galaxy scom operation did not complete Determine if service action or tracking event B131F66C Clock period from chip out of calculated range Determine if service action or tracking event B131F6A3 Enterprise scanned ring to all 0 test failed Determine if service action or tracking event B131F6A4 Enterprise scanned ring to all 1 test failed Determine if service action or tracking event B131F6AF P5IOC scanned ring to all 0 test failed Determine if service action or tracking event B131F6B0 P5IOC scanned ring to all 1 test failed Determine if service action or tracking event Actual Enterprise chip lbist signature didn't B131F6C2 Determine if service action or tracking event match the expected values Actual P5IOC chip lbist signature didn't match B131F6C9 Determine if service action or tracking event the expected values B131F6D4 Enterprise failed abist test Determine if service action or tracking event B131F6DA P5IOC failed abist test Determine if service action or tracking event B132E500 Bad hardware Determine if service action or tracking event B132F6A5 Winnipeg didn't pass the scan test of all zeros Determine if service action or tracking event B132F6A6 Winnipeg didn't pass the scan test of all ones Determine if service action or tracking event Actual Winnipeg chip lbist signature didn't B132F6C3 Determine if service action or tracking event match the expected values B132F6D5 Winnipeg didn't pass abist test Determine if service action or tracking event B132F7A8 Failed to enable host PCI Determine if service action or tracking event B132F7A9 Failed to verify host PCI Determine if service action or tracking event B133E500 Bad hardware Determine if service action or tracking event B135E500 Bad hardware Determine if service action or tracking event B135F62A We timed out waiting for the PLLs to lock Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes 151 .

Fabric bus lost synchronization.Reference codes CanopusPlus didn't pass setting the ring to all zeros or ones ring LDC lbist signature didn't match the expected B135F6C8 values B135F6D8 CanopusPlus abist test failed B1431583 Failed to get input buffer from SCED B1503517 Failed to determine system type B150355A Error in determining FSP-A/B position B150355B Error in determining FSP-A/B position B15035D5 Failed to close I2C ADAL B150D133 Server process failed B150E500 Bad hardware Error in determining system type. which should B150F244 be present in the system. are not present in the system B150F620 Invalid bits set Error detected while waiting for Trimaran B150F627 display to complete B150F62A Timeout while waiting for display to complete Handle errors detected by the Fabric firs and B150F66D the L3 firs B150F805 Functional Unit procedure error B150F806 Procedure error B150F80e Error while stopping Core clocks B150F80f Error while stopping Fabric clocks B150F810 Error while starting Core clocks B150F811 Error while starting Fabric clocks B150F819 B135F6C6 152 Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes . We cannot B150E670 determine system type because gpio read gave unsupported values B150E675 Failed to open I2C ADAL B150E676 Failed to transmit data using I2C ADAL B150E678 Failed to obtain control of MUX B150E679 Failed to setup I2C ADAL configuration B150E67A Failed to obtain control of MUX B150E67B Failed to close I2C ADAL B150E67C Failed to receive data from I2C ADAL B150E67D Failed to transmit data using I2C ADAL B150E67E Failed to transmit data using I2C ADAL B150E67F Failed to receive data from I2C ADAL B150E680 Failed to setup GPIO pins B150E681 Failed to read GPIO pins B150E691 Failed to close I2C ADAL B150F12C Unmatched CRC There is a card in the system that is missing or B150F206 has corrupted VPD data B150F207 Detected a card in the system without chips B150F20A Failed to create daughter card object There was not enough functional nodes found B150F22A in the system to continue IPLing. IPL cannot B150F2C2 continue Elastic Interface Alignment Procedure never B150F2DE completed B150F2DF Fatal IAP Error B150F2E0 Non-fatal IAP Error/Warning There is a checkstop present prior to running B150F2E7 FOCR Sync B150F239 Detected a missing chip It seems that both clock cards.

Reference codes B150F81a B150F81c B150F81d B150FAA2 B150FB53 B150FB54 B150FB55 B150FB61 B150FB64 B150FD00 B150FD01 B1513598 B151E40A B151E40B B1523592 B1523599 B1551300 B1551301 B1551304 B1551305 B1551306 B1551307 B1551308 B1551310 B1551311 B1551312 B1551313 B1551320 B1551321 B1551322 B1551323 B1551324 B1551325 B1551326 B1551330 B1551331 B1551332 B1551333 B1551334 B1551340 B1551341 B1551342 B1551343 B1551344 B1551345 Error while reading data in from ring buffer or alias Error while writing ring buffers or alias to hardware Error reading from register Error writing to register Data Miscompare found in L3 Connections test but no Fir bit on Wiretest has detected an EST error RDT has detected a hardware error Processor group pointer is NULL Processor group pointer is NULL Processor group pointer is NULL GARD Actions were performed on all items that were marked to be gard'd by the system that are not resource recoverable GARD Actions were performed on all items that were marked as gard'd manually via the menus or system gard'd items that can be resource recovered Garding out FSPA due to communication fail Detected DRAM Recovered Errors Detected NVRAM Recovered Errors Sibling FSP is expected but not present Garding out FSPB due to communication fail First level of basic input parameter validation failed Second level of basic input parameter validation failed Machine model invalid Invalid offset type received in structure Number of devices is less than or equal to zero Can't open device list file Data pointer is NULL Failed to read root path from registry Failed to read device path from registry Read sink path failed Read check value failed No data returned from ADAL Maximum arbitration retries exceeded Error from the ADAL trying to set the device Master timeout Write to old hub failed Failed VPD dataport read Failed VPD dataport write Pass through to open file Failed to release I2C lock Failed to unlock I2C hub Error unlocking hub Error from ADAL trying to unlock the device behind the hub Error unlocking CHUNKY device Invalid operation type received in structure Invalid number of nodes received in structure Busy condition Lock on first address of the chunky device failed Error locking CHUNKY device Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 153 (1xxx) System power control network (SPCN) reference codes .

Reference codes B1551346 B1551350 B1551351 B1551352 B1551353 B1551354 B1551355 B1551356 B1551357 B1551358 B1551359 B155135A B155135B B1551360 B1551361 B1551362 B1551363 B1551364 B1551365 B1551366 B1551370 B1551371 B1551372 B1551373 B1551380 B1551381 B1551390 B1551392 B1551393 B1551394 B1551395 B1551396 B1551397 B1551398 B1551399 B155139A B155139B B155139C B155B006 B155B017 B155B028 B155B02C B155B036 B155B03D B155B03E 154 Error from ADAL trying to set the Master timeout Failed to get hub type Could not get the bus to start the transaction Error trying to close the bus Error from the ADAL trying to park the I2C mux Error from ADAL trying to set Master timeout value Error from ADAL trying to set device timeout value Error from ADAL trying to lock the device behind the hub Attempt to lock this device failed Failed to set I2C lock Error trying to set the bus speed in preparation for a retry Error trying to read the maximum memory size of the device from the ADAL Error trying to read the bus speed to see if it can be lowered for a retry Write to set new hub failed Write to new hub failed Write to set the device failed Write to set old hub failed Retry at lower bus speed also failed Retry after the bus reset still failed Retry after bus busy condition still failed Retry after loss of arbitration failed Receive from device failed Read from device failed Failed to receive data from hub Failed to receive data Error trying to write register to device Error trying to do the read Error trying to reset bus Error while closing an I2C bus or unlocking an I2C device or parking an I2C MUX Failed to create network client address Failed network connection between client and server Communication error while trying to send or receive Failed to unflatten server error log Failed to close network client Invalid input received from the caller Error while trying to unflatten the server error log Error while trying to unflatten the server error log Failed to turn on FRONT light strip Failed to turn on BACK light strip Failed to update the Module VPD Keyword can not be found in the VPD buffer We failed trying to read smart chip block There was a failure trying to update one of the smart chip blocks We failed trying to get smart chip block size Failed to write to I2C device Error reading from the device Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

Reference codes Reading thermal sensor data or RIO cable id Determine if service action or tracking event failed for the given FRU B155B048 ECC check failed on the given FRU Determine if service action or tracking event Checksum in the VPD data does not match B155B04D Determine if service action or tracking event calculated checksum The VPD data which describes the wiring path B155B058 Determine if service action or tracking event of a FRU is invalid No valid copy of System VPD was found on B155B05E Determine if service action or tracking event this system There was a mismatch in VINI record for B155B060 Determine if service action or tracking event primary and redundant root node VPD Unable to use either VPD Chip because we B155B061 Determine if service action or tracking event could not reach them or they are garded out B155B065 Reading all blocks from smart chip failed Determine if service action or tracking event B155B06D Failed to process VPD chip Determine if service action or tracking event No valid copy of Enclosure VPD was found on B155B06F Determine if service action or tracking event this system Invalid/Un-Programmed System Serial B155B070 Determine if service action or tracking event Number (SE) Invalid/Un-Programmed Serial Number in B155B071 Determine if service action or tracking event Enclosure Invalid/Un-Programmed System Storage B155B072 Determine if service action or tracking event Serial Number (SG) Invalid/Un-Programmed System Type Model B155B073 Determine if service action or tracking event (TM) Invalid/Un-Programmed System Storage Type B155B074 Determine if service action or tracking event Model (TN) Invalid/Un-Programmed System B155B075 Determine if service action or tracking event Manufacturing ID (MN) B155B076 Invalid/Un-Programmed System ID (ID) Determine if service action or tracking event Invalid/Un-Programmed System Unique ID B155B077 Determine if service action or tracking event (SU) Invalid/Un-Programmed World Wide Node B155B078 Determine if service action or tracking event Name (NN) B155B079 Invalid/Un-Programmed System Brand (BR) Determine if service action or tracking event Invalid/Un-Programmed Feature Code in B155B07D Determine if service action or tracking event Enclosure B155B083 Pin failure failed after root node mismatch Determine if service action or tracking event A device did not respond to an I2C or smartchip request but using other logic we B155B086 Determine if service action or tracking event found in firmware that the FRU is actually present on the system We had an error in trying to detect if this FRU B155B087 Determine if service action or tracking event was actually present or not on the system We failed trying to configure bits for 9555/9554 B155B08F Determine if service action or tracking event controllers B155B090 We failed trying to create smart chip block Determine if service action or tracking event Error occurred while locking/unlocking DASD B155B091 Determine if service action or tracking event device Unsupported bit definition found in the VPD B155B096 Determine if service action or tracking event data for record_99 B155B0AA Error reading from the device Determine if service action or tracking event B157E500 Bad hardware Determine if service action or tracking event B157F131 Last bits of chip command status are not 0x01 Determine if service action or tracking event The JTAG chain pointer was initialized to B157F20D Determine if service action or tracking event NULL and maybe do to an invalid input B157F244 A chip has been found to be missing Determine if service action or tracking event B158E500 Bad hardware Determine if service action or tracking event B158F7A3 Clock failure during test Determine if service action or tracking event Processor gets clock errors with each clock B158F7A4 Determine if service action or tracking event input B155B03F (1xxx) System power control network (SPCN) reference codes 155 .

contains the (1xxx) System power control network (SPCN) reference codes .Reference codes B158F7A5 B159A070 B15A5000 B15A5002 B15A5004 B1701001 B1701002 B1701003 B1701004 B1701005 B1701006 B1701007 B1701008 B1701009 B170100A B170100D B170100F B1701010 B1701012 B1701018 B1701019 B1701029 B170102A B170102B B1701040 B170901F B1709029 B170E500 B170F668 B1748812 B175E019 B175E01A 156 The memory controller gets clock errors with Determine if service action or tracking event both clock inputs Indicates that the Panel is being deactivated Determine if service action or tracking event There is a hardware problem with the RTC Determine if service action or tracking event One-time log stating that the FSP time is Determine if service action or tracking event invalid and needs to be reset The FSP battery needs replacing Determine if service action or tracking event DMA driver has encountered an error Determine if service action or tracking event DMA driver has encountered an error Determine if service action or tracking event DMA driver has encountered an error due to hardware checkstop during a read operation in Determine if service action or tracking event the IPL mode DMA driver has encountered an error due to a target abort in the IPL mode during a read Determine if service action or tracking event operation DMA driver has encountered an unknown Determine if service action or tracking event error in TCE mode during read operation DMA driver has encountered an error due to hardware checkstop during a write operation in Determine if service action or tracking event the IPL mode DMA driver has encountered an error due to a target abort in the IPL mode during a write Determine if service action or tracking event operation DMA driver has encountered an unknown Determine if service action or tracking event error in IPL mode during write operation DMA driver has encountered an error due to hardware checkstop during a read operation in Determine if service action or tracking event the TCE mode DMA driver has encountered an error due to a target abort in the TCE mode during a read Determine if service action or tracking event operation DMA driver has encountered an error due to a target abort in the TCE mode during a write Determine if service action or tracking event operation DMA driver returned a zero Determine if service action or tracking event User given data length doesn't match with the Determine if service action or tracking event amount of data being DMA'd User given data length doesn't match with the Determine if service action or tracking event amount of data being DMA'd Failed to verify host PCI Determine if service action or tracking event Failed to enable host PCI Determine if service action or tracking event Data which is written via DMA does not match with the data being read from the same Determine if service action or tracking event address using JTAG Data which is written via DMA does not match with the data being read from the same Determine if service action or tracking event address using DMA DMA verification failed while writing random Determine if service action or tracking event data at the host address Error occurred in code Determine if service action or tracking event SPIRA does not have sufficient space for the Determine if service action or tracking event data structure Data read from mainstore is not the same as Determine if service action or tracking event what was written to mainstore Bad hardware Determine if service action or tracking event Maintenance SUE during memory preserving Determine if service action or tracking event or exit/error state IPL A Fatal system attention was received so the Determine if service action or tracking event Service Routine failed to complete Communication with the IPAP failed Determine if service action or tracking event This entry is to record a successful Determine if service action or tracking event communication with RETAIN.

for some reason they did not ask for the first call data B175E01B packet.Reference codes PMH number and the response from retain regarding the call packet. so the system will Determine if service action or tracking event use the default LMB size for this configuration PHYP failed to send its heartbeat message B17BE434 Determine if service action or tracking event within the stipulated time Hardware Management Console failed to send B17CE433 its heartbeat message within the stipulated Determine if service action or tracking event time B1806003 Unable to complete fork operation Determine if service action or tracking event B1806006 Failed to allocate memory for object Determine if service action or tracking event B1806007 Error receiving message Determine if service action or tracking event B1806009 Invalid state set for State Manager Determine if service action or tracking event B180600A Invalid state set for State Manager Determine if service action or tracking event B180600C Error in the size of the registry value Determine if service action or tracking event B180600D Bad size of registry value Determine if service action or tracking event B180600E Could not read the registry Determine if service action or tracking event B180600F Failed to write to the registry Determine if service action or tracking event B1806010 Invalid current and next state Determine if service action or tracking event B1806011 Invalid file state Determine if service action or tracking event B1806013 Invalid state set for State Manager Determine if service action or tracking event B180601A Failed to reset the file open Determine if service action or tracking event B180601C Failed to decode reset values Determine if service action or tracking event B180601D Failed to allocate memory for object Determine if service action or tracking event B1806021 Failed to write to message in queue Determine if service action or tracking event B1806022 Failed to read from message in queue Determine if service action or tracking event B1806023 Failed to look up file from required type Determine if service action or tracking event B1806025 Failed to reboot Determine if service action or tracking event B1806026 Failed to open map file Determine if service action or tracking event Failed to read Manufacturing flag for B180602B Determine if service action or tracking event reset/reload B1806030 Invalid character Determine if service action or tracking event B1806031 Error receiving log from client library Determine if service action or tracking event Failed to synchronize with the State Manager B1806033 Determine if service action or tracking event server B1806035 Failed IPL type Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes 157 . since Determine if service action or tracking event we did not send the error data to RETAIN it's not a success. We sent the logon record and did not get a B175E01C Determine if service action or tracking event successful response We sent the user record and did not get a B175E01D successful response the machine may not be Determine if service action or tracking event entitled B175E500 Bad hardware Determine if service action or tracking event B1764020 Invalid data was found in the registry entry Determine if service action or tracking event The Hyperboot capability value is being B1764024 changed from ENABLED to CAPABLE due to Determine if service action or tracking event the value of Service Processor IPL type. we log this error and move on. B176501F Invalid data was found in the rtim registry entry Determine if service action or tracking event B1765020 The system time was changed Determine if service action or tracking event The Timed Power On was disabled due to B1765023 Determine if service action or tracking event invalid system time The rtiminit daemon received an invalid B1765024 Determine if service action or tracking event command in a socket message B176E500 Bad hardware Determine if service action or tracking event B176F687 Bit 2 set in Interrupt Register on Winnipeg Determine if service action or tracking event The user specified LMB size is not valid for B176F7BC this system's memory size. We sent the 20 record to RETAIN.

Failed to get processor state Current power state is undefined Timeout waiting for CEC debug data The MainStore address being written to is within a range which produces unpredictable results Bad command given when trying to send on I2C Failed to receive on slave I2C Failed to send on I2C Panel display line 1 data truncated Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .Reference codes B1806036 B1806037 B180E500 B1811013 B1811016 B1811017 B181101A B181101B B181101C B181101D B181101E B181101F B1811020 B1811021 B1811022 B1811026 B1811027 B1811028 B181102C B181102D B181102F B1811030 B1811031 B1811032 B1811033 B1811035 B1811036 B1811037 B1811038 B1811039 B181103A B181103B B181103D B181103E B181103F B1811040 B1811041 B1811044 B1811045 B1811101 B1811103 B1811104 B1811109 158 Validation of PCS failed Tool reset occurred Bad hardware Failed to open DMA driver Could not retrieve debug configuration information from the DMA driver Could not retrieve debug configuration information from the DMA driver User asking to do a zero length DMA User asking to do a zero length DMA Invalid FSP address received from user Invalid FSP address received from user Bad tag data Bad tag data Bad tag data Cannot DMA when FSP state is between Instruction Start and OLC Invalid value for bus controller There has been a power off just before or during the DMA Could not open file Could not open file Client thread that was supposed to collect DMA error data timed out Event Manager constructor failed Could not query the CHIC reserve identity DMA event listener deleted by another DMA thread Failed to wait for thread conditional Failed to join with thread Client thread that was supposed to collect DMA error data encountered some error TCE mode shouldn't have been set before PHYP lids are loaded No useful DMA error data returned No HOM ID for the enterprise chip found was returned Maximum number of Service Processor resource identities returned was zero Service Processor resource identities is zero No identity match for current FSP No corresponding DMA path was returned for the current resource identity No resource id for the enterprise chip found was returned No HOM ID for the node found was returned User gave an invalid TCE address. The upper 32 bits of the TCE token is non zero which is not a valid token.

Reference codes B1811110 B1811112 B1811114 B1811115 B1811117 B1811118 B1811119 B1811401 B1811402 B1811403 B1811404 B1811405 B1811406 B1811501 B1811502 B1811503 B1811504 B1811505 B1811506 B1811507 B1811508 B1811509 B181150a B181150b B181150c B181150d B181150e B181150f B1811510 B1811511 B1811512 B1811513 B1811514 B1811515 B1811516 B1811517 B1811518 B1811519 B181151a B181151b B181151c B181151d B181151e B181151f B1811520 B1811521 B1811522 B1811523 B1811524 B1811525 B1811526 B1811527 B1811528 B1811529 B181152a Panel display line 2 data truncated Checksum failure Failed to open I2C Failed to close I2C Button press/release sequence violated Failed to configure I2C Failed to receive on slave I2C Invalid parameter passed to function Failed to open I2C Failed to close I2C Failed to transmit on I2C Failed to configure I2C Message received from RPC was bigger than buffer Failed to set reset Failed chip select Failed to set wrap enable Failed to get present device Failed to set GPIO lines Failed to setup UART hardware to wrap Failed to open UART Failed to set timeout for UART Failed to set automatic transmit for UART Failed to set normal transmit for UART Failed to set received for UART Failed to write UART buffer Failed to read UART buffer Wrap test data compare failed Failed to set functioning device Failed to close UART Failed to get present device Failed to set reset Failed to receive input deglitch from SPCN via UART Failed to set present device Failed to set device unit representation Failed to set GPIO driver type to PUSHPULL Failed to set GPIO pin Failed to reset pins Failed to reset pin polarity Failed to set baud rate for UART Failed to set parity mode for UART Failed to set check mode for UART Failed to set stop bit length for UART Failed to set end of transmit timeout for UART Failed to set end of message timeout for UART Failed to select chip pins Failed to get chip pins Timeout waiting to receive message on UART Timeout waiting to receive message on UART Failed to write to UART Failed to select pins for function Failed to select pins for function Failed to select pins for function Failed to get address line setting Failed to get address pins polarity Failed to set address GPIO value Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 159 (1xxx) System power control network (SPCN) reference codes .

Reference codes B181152b B181152c B181152d B181152e B181152f B1811531 B1811532 B1811533 B1811534 B1811535 B1811536 B1811537 B1811538 B1811539 B181153a B181153b B181153c B181153d B181153e B181153f B1811541 B1811542 B1811543 B1811544 B1811545 B1811546 B1811547 B1811548 B1811549 B181154a B181154b B181154c B181154d B181154e B181154f B1811550 B1811551 B1811552 B1811553 B1811554 B1811555 B1811556 B1811557 B1811558 B1811559 B181155a B181155b B181155c B181155d B181155e B181155f B1811560 B1811561 B1811562 160 Failed to set address GPIO driver type to PUSHPULL Registry Read call returned an error Failed to set function line Failed to close UART Failed to open UART A non-present device was accessed Failed to prep for read/write Failed to get sequence retry count Failed to set next send/receive flag Failed to get next send/receive flag Requested transaction size too large Failed to set next send sequence bit Failed to set next receive sequence bit Received message from smart chip is invalid Failed to set next receive sequence bit Failed to set next send sequence bit Failed to set next send receive flag Failed to set next send sequence bit Failed to set next receive sequence bit Failed to set next send receive flag Failed to set next send sequence bit Failed to set next receive sequence bit Failed to execute wrap reset test Failed to execute transaction Failed to reset VPD devices Failed reset test Failed to zero all device sequence bits Failed to set valid configuration flag Failed to get next receive sequence bit Failed to get next send sequence bit Failed to reset devices Failed to get valid configuration flag Failed reading the configuration id from GPIO The configuration id read from the GPIO pins on this system is invalid Configuration registry read back test failed Failed to get reserve for sced Failed to reset Failed to release reserve for sced Non-zero response code returned The number of bytes read doesn't match the bytes requested Failed to send command No sender id detected in call Failed to get mux information from VPD Failed any bytes in or out Failed zero bytes in or out Registry write call returned an error Registry Read call returned an error Failed to get file name for GPIO configuration parser Failed to open file Failed to read number of entries from file Failed to read pin information from file Invalid pointer Received a undefined command type Received a undefined command type Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

Reference codes B1811563 B1811564 B1811565 B1811566 B1811567 B1811568 B181156a B181156b B181156e B181156f B1811570 B1811571 B1811572 B1811573 B1811574 B1811575 B1811576 B1811577 B1811578 B1811579 B181157a B181157b B181157c B181157d B181157e B181157f B1811580 B1811581 B1811590 B1811591 B1811596 B1811597 B181159A B181159D B1812000 B1812001 B1812002 B1812003 B1812004 B1812005 B1812006 B1812007 B1812008 B1812009 B181200a B181200b B181200c B1812017 B1812018 B1812019 B181201a B181201b B181201c B181201d GPIO pin file not loaded yet Determine if service action or tracking event Bad value in pin group Determine if service action or tracking event Registry Read call returned an error Determine if service action or tracking event Failed to set device present flag to false Determine if service action or tracking event GPIO pin file not loaded yet Determine if service action or tracking event Bad value in pin group Determine if service action or tracking event Error from sced internals Determine if service action or tracking event Error from network server address Determine if service action or tracking event Failed message control Determine if service action or tracking event Failed to get message Determine if service action or tracking event Failed to create thread for sced Determine if service action or tracking event Failed to create thread for event handling Determine if service action or tracking event Failed to get path from registry for Determine if service action or tracking event synchronization Failed to bind socket for network server Determine if service action or tracking event Failed to listen on socket for network server Determine if service action or tracking event Failed to synchronize with server for sced Determine if service action or tracking event Invalid pointer returned from synchronization Determine if service action or tracking event Failed to connect to network server Determine if service action or tracking event Failed to receive from network server Determine if service action or tracking event Failed to send message Determine if service action or tracking event Reached maximum number of failures for Determine if service action or tracking event attempts with network server Message Processing Request has an Determine if service action or tracking event unknown operation Failed to get path from registry Determine if service action or tracking event Invalid current packet number Determine if service action or tracking event Failed to reset type in and zero out Determine if service action or tracking event Failed to zero single device sequence bits Determine if service action or tracking event Failed to reset single device Determine if service action or tracking event Failed to reset single VPD device Determine if service action or tracking event Failed to get reserve for sced Determine if service action or tracking event Maximum number of pin failures has been Determine if service action or tracking event reached Failed to get reserve for sced Determine if service action or tracking event Failed to get reserve for sced Determine if service action or tracking event Parsing of return packet failed Determine if service action or tracking event Received an unexpected signal Determine if service action or tracking event Unexpected signal received Determine if service action or tracking event Failed to open file Determine if service action or tracking event Failed to initialize trace Determine if service action or tracking event No name for thread in trace Determine if service action or tracking event Error reading from registry Determine if service action or tracking event Error setting up iterator for SRCs Determine if service action or tracking event Failed to get SRC from SRC iterator Determine if service action or tracking event Invalid pointer Determine if service action or tracking event Failed to lock the mutex Determine if service action or tracking event Failed to unlock the mutex Determine if service action or tracking event Error from event manager constructor Determine if service action or tracking event Error from event management monitor Determine if service action or tracking event Error from event management signal Determine if service action or tracking event Could not initialize queue mutex Determine if service action or tracking event The condition variables could not be initialized Determine if service action or tracking event The condition variables could not be destroyed Determine if service action or tracking event Could not destroy queue mutex Determine if service action or tracking event A power fault has been detected Determine if service action or tracking event Failed to wait on thread conditional Determine if service action or tracking event Failed to write to registry Determine if service action or tracking event 161 (1xxx) System power control network (SPCN) reference codes .

Reference codes B181201e B181201f B1812020 B1812021 B1812023 B1812024 B1812025 B1812026 B1812027 B1812028 B1812029 B181202a B181202b B181202c B181202d B181202e B181202f B1812030 B1812031 B1812032 B1812033 B1812034 B1812035 B1812036 B1812037 B1812038 B1812039 B181203a B181203b B181203c B181203d B181203e B181203f B1812040 B1812041 B1812042 B1812043 B1812044 B1812045 B1812046 B1812047 B1812048 B1812049 B181204A B1812100 B1812102 B1812103 B1812104 162 Failed to signal on thread conditional Failed to create notify thread Failed to cancel the threads Failed to set cancel state of thread Failed to join to thread created Failed to communicate with SPCN Failed to stop communication with SPCN Thread is being canceled while in the middle of sending a command to SPCN Server has routed an acknowledgment message to the command queue The command was rejected by SPCN Could not send a message through the interface to SPCN Could not read a message from the interface to SPCN Failed to create network server object Failed to listen to socket for network server Failed process synchronization with client Failed to close network server Failed to connect to network server Failed to receive from network server Failed to bind to socket for network server Incorrect data received The delayed response has been aborted and the caller is prohibited from attempting to update the socket value Failed to get configuration ID from SPCN Failed to set configuration ID Failed to deattach thread Error getting subfunction ranges for SPCN panel function The notification cannot be sent to state manager because the fsp is not in a particular state Error from state manager power off notification Error from state manager power on notification The condition was not satisfied before specified interval Failed to wait for thread conditional Server queue is full Server queue is empty Already started server Unrecognized command Failed to get path from registry Failed direct command to SPCN Failed to get maximum number of RIDs from SVPD Unexpected SVPD data Failed to get RIDs from SVPD Failed to figure out which FSP running on Timed out waiting for an acknowledgment Failed to set UPS status for SPCN Error from SPCN when trying to power off I/O Error from SPCN command line handler Failed to initialize Failure creating thread Pipe system call failed System call failed Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

Reference codes

B1812105 B1812106 B1812107 B1812108 B1812109 B181210A B181210B B181210C B181210D B181210E B181210F B1812110 B1812111 B1812112 B1812113 B1812114 B1812115 B1812201 B1812202 B1812203 B1812204 B1812205 B1812206 B1812207 B1812208 B1812209 B181220A B181220B B181220C B181220D B181220E B181220F B1812210 B1812211 B1812212 B1812213 B1812214 B1812215 B1812216 B1812218 B1812219 B181221A B181221B

Select system call failed Determine if service action or tracking event Invalid parameter passed to function Determine if service action or tracking event Could not create message queue Determine if service action or tracking event Received invalid command from RPC device Determine if service action or tracking event Invalid function ID from message Determine if service action or tracking event Timeout receive though no timeout was given Determine if service action or tracking event Expected file descriptor not set after select call Determine if service action or tracking event Failed to do an I2C slave address change on a Determine if service action or tracking event redundant FSP failover Could not insert initial events into queue Determine if service action or tracking event Error removing message from queue Determine if service action or tracking event Failed to get power state Determine if service action or tracking event Failed IPL lock function Determine if service action or tracking event Failed to close network server Determine if service action or tracking event Error from Event Manager Determine if service action or tracking event Could not create token queue Determine if service action or tracking event Could not insert tokens into token queue Determine if service action or tracking event Over total thread threshold Determine if service action or tracking event Failed to open and lock the IPL Lock data file Determine if service action or tracking event Failed to unlock and/or close the IPL Lock Determine if service action or tracking event data file Failed to initialize the header of the IPL Lock Determine if service action or tracking event data file Failed to read from registry Determine if service action or tracking event Failed to position the cursor in the file or read Determine if service action or tracking event the header from the file Failed to position the cursor in the file or write Determine if service action or tracking event the lock information to the file Failed to read lock information Determine if service action or tracking event Failed to write the new lock information to the Determine if service action or tracking event IPL Lock data file Failed to read the header in the IPL Lock data Determine if service action or tracking event file Failed to update new header in IPL Lock data Determine if service action or tracking event file Invalid parameter passed into function Determine if service action or tracking event Invalid power state for IPL requested Determine if service action or tracking event Failed to get current power state of system Determine if service action or tracking event Failed to open and lock the IPL Lock data file Determine if service action or tracking event Failed to close and/or unlock the IPL Lock Determine if service action or tracking event data file No locks exist or the requested lock exceeds Determine if service action or tracking event the total number of locks that exist A lock by the requesting component still exists Determine if service action or tracking event and is active An error occurred trying to find the lock for the Determine if service action or tracking event component Failure to allocate memory for timer thread Determine if service action or tracking event structure Failure to create timer thread for lock Determine if service action or tracking event Failure to remove requested lock Determine if service action or tracking event Component requesting refresh does not have Determine if service action or tracking event a lock in the IPL Lock data file IPL requested is blocked due to an IPL lock Determine if service action or tracking event Value passed in to set Power IPL in Progress Determine if service action or tracking event to was out of range Emergency IPL was received and locks were Determine if service action or tracking event bypassed IPL was rejected by State Manager or the Determine if service action or tracking event acknowledge was not accepted
163

(1xxx) System power control network (SPCN) reference codes

Reference codes

B181221C B181221D B181221E B181221F B1812220 B1812221 B1812222 B1812223 B1812224 B1812225 B1812226 B1812227 B1812228 B1812229 B181222A B181222B B181222C B1812300 B1812301 B1812304 B1812305 B1812306 B1812307 B1812308 B1812309 B181230B B181230C B181230D B181230E B181230F B1812311 B1812401 B1812402 B1812403 B1812404 B1812405 B1812406 B1812407 B1812408 B1812409 B181240A B181240B B181240C B181240D
164

A Power IPL has already been requested and Determine if service action or tracking event queued Failed to send Power On event to Panel for Determine if service action or tracking event requested IPL Failed to send Power Off event to Panel Determine if service action or tracking event Failed fork system call Determine if service action or tracking event Failed to start IPL Power process due to not being able to replace current executable with Determine if service action or tracking event IPL Power process Invalid argument was passed into the timer Determine if service action or tracking event thread Invalid signal received Determine if service action or tracking event Failure to detach timer thread so memory resources will not be freed upon termination of Determine if service action or tracking event the timer thread A Power IPL is in progress Determine if service action or tracking event Failed to get Power IPL in Progress indicator Determine if service action or tracking event Failed to write to Power IPL in Progress Determine if service action or tracking event registry variable Failed to indicate that a Power IPL will be in Determine if service action or tracking event progress Failed to get current and next state Determine if service action or tracking event Failed to read current FSP Role from registry Determine if service action or tracking event An invalid pointer was passed into the function Determine if service action or tracking event Failed to determine the size of the IPL Lock Determine if service action or tracking event data file An error occurred trying to get current ticks Determine if service action or tracking event Unexpected signal received Determine if service action or tracking event Failed fork operation Determine if service action or tracking event Error while querying for CEC termination Determine if service action or tracking event Synchronization with State Manager failed Determine if service action or tracking event Failed to read maximum size of error Determine if service action or tracking event Failed to write to registry Determine if service action or tracking event Error creating termination iterator Determine if service action or tracking event Failed to read termination SRC Determine if service action or tracking event Failed to read path from registry Determine if service action or tracking event Error from event monitor Determine if service action or tracking event Server not ready or daemon is not running Determine if service action or tracking event Failed to synchronize with client Determine if service action or tracking event Error returned from IPL lock function Determine if service action or tracking event Error from event manager constructor Determine if service action or tracking event Failed to write WOL Policy to registry Determine if service action or tracking event Failed to read WOL Policy from registry Determine if service action or tracking event Failed to HIGH-LOW-HIGH the Wake on LAN Determine if service action or tracking event reset line Failure to setup Wake on LAN reset line Determine if service action or tracking event Failed to get current power state, so we were not able to activate the Wake on LAN Determine if service action or tracking event hardware Invalid signal received Determine if service action or tracking event Failed to activate Wake on LAN hardware Determine if service action or tracking event Failed to IPL the system via Wake on LAN Determine if service action or tracking event Failed to get Wake on LAN Policy Determine if service action or tracking event The value for the Wake on LAN Policy is out of Determine if service action or tracking event range for what is acceptable Failed fork system call Determine if service action or tracking event An error was returned as we tried to wait for Determine if service action or tracking event the Wake on LAN interrupt line An error occurred processing the Wake on Determine if service action or tracking event LAN interrupt
(1xxx) System power control network (SPCN) reference codes

Reference codes

B181240E B181240F B1812410 B1812411 B1812412 B1812413 B1812414 B1812415 B1813001 B1813002 B1813003 B1813006 B1813007 B1813008 B1813009 B181300A B181300C B181300D B181300E B181300F B1813010 B1813011 B1813012 B1813013 B1813014 B1813015 B1813016 B181301F B1813020 B1813022 B1813025 B1813028 B1813029 B181302A B1813030 B1813031 B1813034 B1813035 B1813036 B1813038 B1813039 B181303a B181303b B181303d B181303e B181303f B1813040 B1813041 B1813042 B1813043 B1813044

Failed to get root path from the registry. Determine if service action or tracking event A daemon is already up and running Determine if service action or tracking event Failed to create the daemon synchronization Determine if service action or tracking event file Due to the type of machine, the Wake on LAN Determine if service action or tracking event functionality is not supported Failed to read current state data from registry Determine if service action or tracking event Failed to read FSP Role from registry Determine if service action or tracking event Failed to read machine model type from Determine if service action or tracking event registry Failed to read operational mode from registry Determine if service action or tracking event Someone is already updating code Determine if service action or tracking event Registry read fails Determine if service action or tracking event Registry write fails Determine if service action or tracking event Lid Entry is not found. The specified Lid Determine if service action or tracking event number is not in the specified Masterlid file Invalid Lid number Determine if service action or tracking event Lid is not valid Determine if service action or tracking event Request to update the wrong lid Determine if service action or tracking event Requestor did not start the update Determine if service action or tracking event Type of code update is already set Determine if service action or tracking event Invalid flash side Determine if service action or tracking event In correct flash side Determine if service action or tracking event Header has invalid magic number Determine if service action or tracking event System command fails to remove a file Determine if service action or tracking event File open error Determine if service action or tracking event Lid does not exist Determine if service action or tracking event Someone is currently updating the specified lid Determine if service action or tracking event Request IPL lock or unlock fails Determine if service action or tracking event Lid class is invalid Determine if service action or tracking event Specified buffer is too small for the requesting Determine if service action or tracking event data Updating on the running side is not allowed Determine if service action or tracking event Update good flash side, when other side is Determine if service action or tracking event invalid CRC miscompare Determine if service action or tracking event Invalid data size is detected Determine if service action or tracking event IPL lock refresh fails Determine if service action or tracking event Invalid component id Determine if service action or tracking event Lid is currently being modified by someone Determine if service action or tracking event Invalid code type Determine if service action or tracking event Invalid Marker Lid version Determine if service action or tracking event Invalid operation state Determine if service action or tracking event Offset is exceeding the file size Determine if service action or tracking event Someone requests code update termination Determine if service action or tracking event Unable to create event Determine if service action or tracking event Unable to create thread to monitor the power Determine if service action or tracking event lock timeout Lid does not belong to FSP Determine if service action or tracking event The power log flag is not set Determine if service action or tracking event Invalid data Determine if service action or tracking event Function call fails Determine if service action or tracking event Reading offset to partition table failed Determine if service action or tracking event Write the partition name to a specific partition Determine if service action or tracking event table entry failed Seek file from the end of file failed Determine if service action or tracking event The status of the MTD device failed Determine if service action or tracking event Invalid Genus size Determine if service action or tracking event Incorrect file for update Determine if service action or tracking event
165

(1xxx) System power control network (SPCN) reference codes

Reference codes

B1813045 B1813047 B1813048 B1813049 B181304a B181304f B1813050 B1813501 B1813503 B1813509 B181350B B181350C B181350D B181350F B1813511 B1813515 B1813516 B1813519 B181351A B181351B B181351C B181351E B181351F B1813520 B1813521 B1813523 B1813524 B1813525 B1813527 B1813528 B1813529 B181352A B181352B B181352C B181352D B181352E B181352F B1813531 B1813532 B1813533 B1813534 B1813535 B1813536 B1813537 B1813538 B1813539 B181353A B181353B
166

Unable to find keyword that indicate bank id The system has redundant FSP The specified arguments for major/minor number are out of range The filename that is passed in does not start with a '/' The status of the MTD device failed Invalid operation Unknown signal Error in call to other component interface Error received from sibling FSP Error setting network parameters for various ethernet interface Error creating network client object We detected a sibling but the communication broke down in between Error configuring various ethernet interface Error in call to other component interface Error sending data to sibling Error obtaining mux information Error in interface call to other component Bad command received from sibling FSP Communication to sibling failed Error reading FSP State Error waiting for an event Error getting time of day Error setting time of day Error indicating that sibling FSP was already garded Error creating a event object Error creating network client object We detected a sibling but the communication broke down in between We detected a sibling but the communication broke down in between Failed to read from registry Failed to read size from registry We detected a sibling but the communication broke down in between Error reading registry entry size Error writing pass phrase to registry entry Error reading sibling ethernet port 0 registry entry Error writing to sibling ethernet port 0 registry entry Error reading sibling ethernet port 1 registry entry. Error writing to sibling ethernet port 1 registry entry. Error writing MTMS to file Error reading registry entry size Error reading registry entry Error reading/writing from file Error reading/writing from file Error reading/writing from file Error reading/writing from file Error reading/writing from file Error reading/writing from file Error reading/writing from file Error reading/writing from file

Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event
(1xxx) System power control network (SPCN) reference codes

Reference codes

B181353C B181353D B181353E B181353F B1813540 B1813541 B1813542 B1813543 B1813544 B1813545 B1813546 B1813547 B181354A B181354B B181354C B181354D B1813550 B1813551 B1813552 B1813553 B1813554 B1813555 B1813556 B1813557 B1813558 B1813559 B181355C B181355D B181355E B181355F B1813560 B1813561 B1813562 B1813563 B1813564 B1813569 B181356A B181356F B1813570 B1813579 B181357A B181357B B181357C B181357D B181357E B181357F B1813580 B1813581 B1813582 B1813583 B1813584 B1813585 B1813586 B1813587 B1813588 B1813589

Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in network operation Error in call to other component interface Error in network operation Error in call to other component interface Error in network operation Error in call to other component interface Error in network operation Error in call to other component interface Error in network operation Error in call to other component interface Error in network operation Error in network operation Error in reading FSP Role registry Error in call to other component interface Error in call to other component interface Error in call to other component interface Error in call to other component interface Error in call to other component interface Error in call to other component interface Error in call to other component interface Error in network operation Error in call to other component interface Error in call to other component interface Error in network operation Error writing MTMS to file Error reading/writing from file Error reading/writing from file Error setting network parameters for various ethernet interface Error in interface call to other component Error trying to setup initial communication between FSP's Error in call to other component interface Error in call to other component interface Error in interface call to other component Error starting Surveillance Error in call to other component interface Error in network operation Error in network operation Error in interface call to other component Error sending data to sibling Error sending data to sibling Error sending data to sibling Error sending data to sibling Error sending data to sibling Error sending data to sibling

Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event
167

(1xxx) System power control network (SPCN) reference codes

Reference codes

B181358A B181358B B181358C B181358D B181358F B1813591 B1813592 B1813593 B1813594 B1813595 B1813596 B1813597 B181359A B181359B B181359E B181359F B18135A0 B18135A1 B18135A2 B18135A3 B18135A4 B18135A5 B18135A6 B18135A7 B18135A8 B18135A9 B18135AA B18135AB B18135AC B18135AD B18135AE B18135AF B18135B0 B18135B1 B18135B2 B18135B3 B18135B4 B18135B5 B18135B6 B18135B7 B18135B8 B18135B9 B18135BA B18135BB B18135BC B18135BD B18135BE B18135BF B18135C0 B18135C1 B18135C2 B18135C3 B18135C4 B18135C5
168

Error in call to other component interface Error in call to other component interface Error in interface call to other component Error while making open call to I2C adal Error while making open call to I2C adal Error while making open call to I2C adal Sibling FSP is expected but not present Error in call to other component interface Error in call to other component interface Discovery abort was requested Error in call to other component interface Error in putting message in message queue Error while making open call to I2C adal Error while making open call to I2C adal Error setting up passwords Error closing client socket Error closing server socket Invalid request to Discovery thread Eth0 IP address on FSP-B was set to default Eth1 IP address on FSP-B was set to default Error while making open call to I2C adal Exceeded maximum number of retries for communication errors between FSP's in various states Error in interface call to other component Error in interface call to other component Error in interface call to other component Both FSPs were reset Both FSPs were reset Both FSPs were reset Error sending data to sibling Error reading registry Error exchanging data with sibling Error receiving data from sibling Error writing registry Error receiving data from sibling Error exchanging data to/from sibling Error in data received from sibling Error receiving data from sibling Error in call to other component interface Error in call to other component interface Error in call to other component interface Error receiving data from sibling Error receiving data from sibling Error sending data to sibling Error writing registry Error receiving data from sibling Error sending data to sibling Error receiving data from sibling Error receiving data from sibling Error receiving data from sibling Eth1 IP address on FSP-B was set to default Eth1 IP address on FSP-B was set to default Reset of both FSPs. Possible new role assigned to FSP-A Reset of both FSPs. Possible new role assigned to FSP-A Reset of both FSPs. Possible new role assigned to FSP-A

Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event
(1xxx) System power control network (SPCN) reference codes

Reference codes

Gard did not return back a status but indicated a failure in the output parameter of their routine B18135C9 Error in call to other component interface B18135CA Error in call to other component interface B18135CB Error in call to other component interface B18135CC Error in call to other component interface B18135CD Error in putting message in message queue B18135CE Error from network client gateway B18135CF Error from network client gateway Registry entry indicates that a serial B18135D0 communication error is to be simulated B18135D1 Error reading serial error injection registry B18135D2 Error in putting message in message queue B18135D3 Error in putting message in message queue B18135D4 Error in call to other component interface B18135D7 Error while making open call to I2C adal B18135D8 Error in interface call to other component B18135D9 Error in interface call to other component B18135DA Error in interface call to other component Error indicating that sibling FSP was already B18135DB garded B1814000 Invalid command B1814001 Missing argument B1814002 Invalid argument Invalid data received for process message B1814003 operation number Wrong number of arguments given to B1814004 command B1814005 An error occurred reserving the semaphore B1814006 Received unexpected signal B1814006 Receive unexpected signal A side switching IPL is not allowed for the B1814007 given type of CEC IPL A side switching IPL is needed, but the code is B1814008 not valid on that side A side switch reboot could not be performed B1814008 because the code is not valid on the new next side Invalid data was received for next system B1814016 operation mode Invalid data was received for system click to B1814016 accept state Invalid data was received for next platform IPL B1814017 side Invalid data was received for next system IPL B1814018 mode Invalid data was received for next platform IPL B1814019 speed Invalid data was received for next platform IPL B181401A speed override Invalid data was received for next Hypervisor B181401B IPL state Invalid data was received for next RPA B181401C partition IPL mode Invalid data was received for next CEC LMB B181401D size B1814021 The daemon could not get the lock B1814022 Failed fork system call B1814023 The daemon rebooted the FSP to Standby because the P2 registry data that controls B18135C8
(1xxx) System power control network (SPCN) reference codes

Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event
169

Reference codes

B1814025 B1815001 B1815005 B1815006 B1815007 B1815008 B181501B B181501C B181501D B181501E B1815021 B1815022 B1815025 B1815026

B1815027 B1815029 B1816009 B1816010 B181601C B1817000 B1817003 B1817004 B1817005 B1817006 B1817007 B1817008 B1817009 B181700A B181700D B1817010 B1817011 B1817012 B1817013 B1817015 B1817016 B1817018 B1817019 B181701A B181701B B181701C B181701D B181701E B181701F B1817020 B1817021
170

labeling of Permanent and Temporary Flash images was replaced with P3 registry backup data. Called interface not supported in context Received unexpected signal Invalid data received An attempt was made to write to the system clock without proper user authority The GPIO ADAL returned an error while reading the battery alert pin A registry read error occurred An undefined operation was requested Error reading using Time of Day ADAL Error writing using Time of Day ADAL Error writing using Time of Day ADAL The daemon could not get the lock Failed fork system call Failed to create thread The elapsed time since IPL Parameters time data was built was calculated with the RTC and TOD counter. The two results are off by more than 8 seconds. The TOD counter was checked after writing, and was off by more than 65536 ticks (0.524 sec). Failed to create RMGR synchronization thread Invalid state set for State Manager Invalid current and next state Failed to decode reset values Failure to create thread Failed network server connection Failed to receive message from network Failed to close network connection Failure to establish communications pipe PHYP was not ready to be communicated with Failed to write data Failure reading data Load SRC failed Failed to read from or write to registry Error reading data from server communications pipe Data size mismatch Error/Event notification throughout the system has failed for the given platform event log Failed to scan for error/event logs Error while attempting to change state Corrupt input data A log was picked up and the unique id assigned to it is zero Error received while attempting to turn on virtual platform service indicator The section identifier read from the data does not match the section id of the current object Invalid section size detected Section version mismatch Section count mismatch Failed to send or receive on network Unhandled signal received Invalid input or data File system failure

Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event

Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event
(1xxx) System power control network (SPCN) reference codes

Reference codes

B1817022 B1817024 B1817025 B1817026 B1817028 B1817029 B181702A B181702B B181703E B1817102 B1817107 B181710B B181710D B1817112 B1817113 B1817114 B1817115 B1817200 B1817201 B1817202 B1817203 B1817204 B1817205 B1817206 B1817209 B181720A B1818103 B1818106 B1818107 B1818108 B1818109 B181810A B181810B B181810C B181810D B181810E B181810F B1818110 B1818111 B1818114 B1818115 B1818116 B1818203 B1818204 B1818211 B1818212 B1818213 B1818214 B1818215 B1818216 B1818217

FSP call home attempt has failed Failed to initialize the history log, logging cannot continue if the physical file cannot be initialized Request to clear error/event logs has been processed Error/Event logging server started Error/Event log created from system log message Linux system call failed Error unloading virtual headers due to lack of file allocation space Timeout waiting for sibling FSP command to complete Unknown failure Failed to setup process error recovery Host driver or registry failure Event manager failed Event detection failed Software failure resulted in a signal Event loop exited Failed to change directory Failed to set session identity User requested to boot from a side that is marked invalid FSP had a kernel panic during last boot Both FSP code banks are marked invalid Error writing to Persistant Control Store (PCS) Error reading from PCS FSP Boot code failed during last boot causing the FSP to reset again FSP had a Unit check timer reset FSP had a Watchdog timeout reset FSP had an internal hardware error Failed to write to registry Invalid bus owner argument Invalid number of command line arguments No argument value for --r option Multiple -c arguments -s option specified with -c Multiple -s arguments -c options specified with -s Invalid command line option Non-option element(s) Null input numeric string Empty input numeric string Invalid character encountered in conversion Failed to stop instructions Failed to send signal for event manager Failed to get processor state Requested index is out of range Failed to open given directory Could not understand operation requested Unexpected result Invalid data Incorrect input size (too small or too large) A generic stream failure has been detected Failed to write to file The Callout substructure cannot be identified

Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event
171

(1xxx) System power control network (SPCN) reference codes

Couldn't retrieve the embedded SRC from error log Failed to initialize thread attributes Failed to set deattach state for thread Failed to bind socket Failed to lock the mutex Could not cancel all the client request processing threads Unknown error Could not unflatten log object from the received byte stream Log size maximum is less than the client data length Zero data length Failed to construct event manager Failed to bind socket Failed to create thread Cannot reset CEC termination in the middle of a power fault request Unknown FSP role returned Already in the terminated state with force failover option Currently processing an FSP terminate request with force failover option from another component Failed to flatten log Bad length on flattened log Server aborted or failed to connect to network Server aborted or failed to send or receive on the network Server not running P0 root path not defined Incorrect number of arguments The caller wanted to get event related data but the buffer pointer is invalid Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes . Will use default log to terminate system.Reference codes B1818218 B1818301 B1818302 B1818303 B1818304 B1818305 B1818307 B1818309 B181830B B181830D B181830E B1818310 B1818312 B1818313 B1818316 B1818317 B1818318 B181831A B181831C B181831D B181831E B1818320 B1818321 B1818322 B1818323 B1818328 B1818329 B181832A B181832C B1818330 B1818331 B1818333 B1818336 B1818337 B1818338 B1818341 B1818344 B1818345 B1818346 B1818347 B181834A B1818500 B1818501 B1818502 172 Unhandled signal received Already in the terminate state Already in the power off state Currently processing a power off request from SPCN Currently processing an FSP terminate request from another component Failed state manager termination request Failed power transition request Too many client connections Thread timed out while waiting for another busy thread to complete Client request thread started with invalid pointer Another instance of the server is already running Timed out waiting for thread conditional Failed to receive on network Failed to connect to server over network Failed to trace SRC on termination trace Failed to read the registry Could not update the CEC termination state No log passed in.

Reference codes B1818503 B1818504 B1818505 B1818507 B1818508 B1818509 B181850E B181850F B1818600 B181860D B181860E B181860F B1818610 B1818700 B1818701 B1818702 B1818703 B1818704 B1818705 B1818706 B1818708 B1818709 B181870A B181870B B181870C B181870D B181870F B1818711 B1818714 B1818718 B181871B B181871E B181871F B1818728 B181872A B181872C B181872E B1818730 B1818731 B1818736 B1818737 B1818738 B1818739 B181873A B181873B B181873C B181873D B181873F B1818740 B1818748 B181874C The daemon received a message with an invalid function field Error returned from another component Failed system call Failed fork system call Error trying to forward an event to 1 or more subscribers The id of a tool request is invalid Unexpected signal received The user specified a time limit to wait for an event and limit was reached Another thread is waiting Application has received an unexpected signal Application has not setup process error recovery Killing process without having process error recovery setup Process continues to get killed. Caught in a loop. Application has received an unexpected signal Error in selecting communicating socket Failed to listen to socket for network server Failed to bind to socket for network server Failed to bind for TCP/IP Error in accepting socket Error in processing message from serial Error in accepting socket Error creating unique key for message queue Error in creating message queue Error in queueing messages Error in receiving message from queue when processing message Failed to read registry Error in creating inbound thread Error in inbound connection Error in receiving messages Error processing message Error in send message in DVS Failed to destroy old message queue Error in IPC address creation Error in closing inbound socket Can't remove the previous mount Failed in registry read Failed in file write Can't activate user configuration setup file Error in writing system name Invalid user Failed to set user password Failed to validate password Error in initial outbound remote thread setup Failed to kill thread in outbound Failure from remote message object Failed to requeue message Error in operation should not kill Failed to destroy old message queue Failed to create thread Failed to create thread Failed to read from registry Serial message is invalid Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 173 (1xxx) System power control network (SPCN) reference codes .

Reference codes B1818752 B1818753 B1818755 B1818756 B1818759 B1818760 B1818762 B1818763 B1818764 B1818765 B1818767 B1818768 B1818769 B181876A B181876B B181876C B181876D B181876E B181876F B1818770 B1818771 B1818772 B1818773 B1818776 B1818777 B1818778 B1818780 B1818781 B1818782 B1818783 B1818785 B1818786 B1818787 B1818788 B181878A B181878C B181878D B181878E B181878F B1818791 B1818792 B1818793 B1818795 B1818796 B1818797 B1818799 B181879A B181879B B181879D B181879E B181879F B18187A0 B18187A1 B18187A2 B18187A3 174 Failed to open port for connection Failed to configure baud for UART Failed to set status field to failure for PHYP Failed to verify dynamic password Failed to write password signature Failed to write Manufacturing password signature Failed to configure parity for UART Failed to configure UART to transmit normal Failed to auto receive on UART Failed to configure UART to transmit automatically Error from perc Error in getting machine type VPD Error in getting machine serial number Error in reading machine brand name Error initializing network serial server daemon Failed to get a file descriptor Error from status of file Improper error path Failed to write Manufacturing password signature Illegal socket descriptor selected Improper error path Failed to get registry key status information Failed to get registry key status information Failed to configure UART Failed to configure UART for loop back Failed to configure UART Failed to read registry Failed to open file Failed to get file handle Socket creation failed Socket bind error Failed in socket listen Failed in file write Invalid client name length Failure to get free entry Failed in registry read Update session entry failure Session entry read failed Invalid lookup entry for maximum entry Failed to seek file offset Session entry not found Session entry read failed Failed to seek session entry Update session write failed Invalid process id value Invalid constructor area Failed in socket creation Failed to read path for socket from registry Failed to construct network client Failed to allocate memory for a message Failed to allocate memory for a message Length of the message buffer is incorrect Invalid pointer Invalid pointer Invalid pointer Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

Reference codes B18187A4 B18187A5 B18187A7 B18187A8 B18187AB B18187AC B18187AD B18187AF B18187B0 B18187B1 B18187B2 B18187B3 Invalid pointer Failed to get channel string id to server Failed to connect using UNIX Error in network connection using UNIX Failed to receive data from the network client Failed to connect using TCP/IP Failed to connect using UNIX Timed out waiting on connection Failed to get socket options Connection failed Failed to select socket Eth0 connection failure Failed to connect for network client serial B18187B4 connection to CMS Failed to send serial connection message to B18187B6 eth0 gateway B18187B7 Error in sending connection message Error in sending connection message to serial B18187B8 connection to CMS B18187B9 Failed to send data B18187BA Error in opening port number B18187BC Error writing to port B18187BD Failed to close UART B18187BE No object created B18187C0 Failed to receive data B18187C1 Failed to reset UART B18187CA Failed to close B18187CB Failed to close serial B18187CC Error closing eth0 connection B18187CD Error closing eth1 connection B18187D0 Unexpected signal received B18187D1 Error setting password B18187D6 Failed to send sdata B18187D7 Failed to send sdata B18187D8 Failed to configure UART B18187D9 Failed to configure UART B18187DA Failed to configure UART B18187DB Failed to configure UART B18187DC Failed to configure UART B18187DE Error receiving on serial interface B18187E5 Failed to read registry for network client B18187E6 Failed to connect for TCP/IP B18187E7 Socket error on select B18187E8 Timed out on select call B18187E9 Connect failed B18187EA Failed to close B18187EC Error in write operation B18187ED Error in select while waiting for data B18187EE Timeout in select while waiting for data B18187EF Error in receive operation B18187F0 Bad eyecatcher detected in the data packet B18187F1 Timeout in select while waiting for data B18187F2 Error in select while waiting for data B18187F3 Error in select Error in sending connection message to serial B18187F5 connection to CMS B18187F6 Error processing message for gateway B18187F7 Error sending or receiving message (1xxx) System power control network (SPCN) reference codes Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 175 .

Reference codes B18187FA B1818801 B1818802 B1818803 B1818806 B1818807 B1818808 B1818809 B181880A B181880B B181880C B181880D B181880E B181880F B1818810 B1818813 B1818814 B1818815 B1818816 B1818817 B1818818 B1818819 B181881A B181881B B181881C B181881D B181881E B181881F B1818820 B1818821 B1818822 B1818823 B1818824 B1818825 B1818826 B1818827 B1818828 B1818829 176 Data sent in through constructor is bad Determine if service action or tracking event Invalid Service Routine Determine if service action or tracking event Requested processor core is not functional Determine if service action or tracking event Failed to get selected processor core Determine if service action or tracking event functionality Failed to restore the Attention Area into Determine if service action or tracking event MainStore Failed to restore the SPRs Determine if service action or tracking event Failed to restore the GPRs Determine if service action or tracking event Failed to create shared memory for Attention Determine if service action or tracking event Area Failed to invalidate the I-Cache and Instruction Determine if service action or tracking event buffers for all processors Failed to read path from registry Determine if service action or tracking event Failed to start instructions to run the Service Determine if service action or tracking event Routine Failed to write to Service Routine State in registry to indicate that a Service Routine is Determine if service action or tracking event running Timed out waiting for the Service Routine to Determine if service action or tracking event finish Failed to write to Service Routine State in registry to indicate that a Service Routine is Determine if service action or tracking event not running Failed to attach to shared memory area for Determine if service action or tracking event Attention Area Failed to set bit for SPR register setup Determine if service action or tracking event Failed to read GPRs for thread in User Data 2 Determine if service action or tracking event of SRC so they could be saved Failed to set bits in setup map buffer to Determine if service action or tracking event indicate what register we wanted to set Failed to read SPRs for thread in User Data 4 Determine if service action or tracking event of SRC so they could be saved Failed to read Attention Area from MainStore Determine if service action or tracking event Failed to get CPU Control Area from Host Determine if service action or tracking event Data Area Failed to get Service Routine structure from Determine if service action or tracking event Host Data Area Failed to initialize Service Routine address Determine if service action or tracking event buffer Failed to write Service Routine address to Determine if service action or tracking event GPR3 for thread in User Data 2 of SRC Failed to read the current SPR values Determine if service action or tracking event Failed to initialize NIA buffer Determine if service action or tracking event Failed to setup SPR to run Service Routine Determine if service action or tracking event Failed to set NIA for Service Routine Determine if service action or tracking event Failed to initialize MSR buffer Determine if service action or tracking event Failed to set MSR for Service Routine Determine if service action or tracking event Failed to set LPCR for Service Routine Determine if service action or tracking event Failed to clear RMI bit in LPCR for Service Determine if service action or tracking event Routine Failed to get LPCR from SPR object Determine if service action or tracking event Invalid attention area pointer was passed into Determine if service action or tracking event function Failed to get shared memory area for Attention Determine if service action or tracking event Area Failed to deattach from shared memory area Determine if service action or tracking event for Attention Area Failed to create file to signify that the system Determine if service action or tracking event attention has been handled Failed to destroy file Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

Reference codes B181882A B181882B B181882C B181882D B181882E B181882F B1818830 B1818831 B1818901 B1818902 B1818903 B1818904 B1818905 B1818906 B1818907 B1818908 B181890A B181890B B181890C B181890D B181890E B181890F B1818910 B1818911 B1818912 B1818913 B1818914 B1818915 B1818916 B1818917 B1818A01 B1818A02 B1818A03 B1818A04 B1818A05 B1818A06 B1818A08 Failed to destroy shared memory for Attention Area Failed to get status of thread requested No threads are alive on the requested processor core Failed to get proper fabric identity so we could read MainStore Failed to get Attention Area data from MainStore object Timed out waiting for Attention Handler to begin running Failed to start Attention Handler Failed to unmap memory Failed to read from the registry The Server file does not exist and we have timed out The Server file exists. but it had invalid characters The command was passed improper arguments We have exceeded the maximum number of files that are allowed to be created and opened using Process Synchronization The Server file descriptor could not be found Failed to synchronize with requested file in time allotted Registry read or write failure due to an invalid key Registry read or write failure due to a size mismatch Building Block registry write failure Failed to determine the platform extension for the given write key Redundant write failed for the given key Event signal failure for the given write key Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 177 (1xxx) System power control network (SPCN) reference codes . but is not locked and we have timed out The file failed to open The Server file failed to be created and opened The Server file that was created/opened failed to lock The Server file that was opened is already locked by another Server process The Server file failed to be unlinked (destroyed) The List file is at the end of file The List file failed to read a line due to a reading error The List file is in an invalid format Failed to read the base path from the List file The timeout value read from the List file was too small or too large Failed to read the relative path of the file to be checked from the List file Failed to read the timeout of the file to be checked from the List file Failed to synchronize with a file from List file Failed to synchronize with requested file in time allotted A line was read from the List file.

Reference codes B1818A09 B1818A0A B1818A0D B1818A0E B1818A0F B1818A10 B1818A11 B1818A12 B1818A13 B1818A15 B1818A16 B1818A17 B1818A18 B1818A19 B1818A1A B1818A1B B1818A1D B1818A1E B1819002 B1819003 B1819004 B1819008 B1819009 B181900A B181900B B181900C B181900E B181900F B1819010 B1819011 B1819014 B1819018 B181901A B181901B B181901C B181901F B1819020 B1819021 B1819022 B1819023 B1819026 B1819027 B1819028 B181904F 178 Redundant registry write failure due to stream failure Building Block registry failure Error forming the registry path Requested system operation failed File not open Reached end of file Bad memory receive pointer Stream is at end of file File removal failed in the underlying layer File lock failure with given parameters Semaphore initialization cannot complete due to failure getting semaphore Semaphore initialization cannot complete due to control failure of semaphore Semaphore operation failed Semaphore initialization cannot complete due to failure getting file token Loading of a shared library has failed Loading of a shared library symbol has failed Failed to execute the synchronization immediate platform extension during a registry operation Building Block registry read failure Error reading platform extension for the given registry key Invalid number of arguments were passed Incorrect number of arguments Failed trying to make a directory Failed trying to get status of a file Failed attempting to allocate memory Failed trying to allocate memory Failed trying to allocate memory Failed trying to memory map a file Failed trying to memory map a file Failed trying to unmap a file Failure from memory unmap Unexpected signal received Size of registry entry is not correct LID's file size is too large Failed trying to add another entry to an array Attempted to add a RAM FRU for an invalid mainstore area Failed trying to get status of primary LID's file More PHYP LIDs have been added to the build for FSP to load and an array is not large enough to accommodate the new LIDs Size of file cannot contain the amount of memory we want to map VPD says a required FRU does not exist Attempted to allocate memory but it failed No resource ids were returned for a required FRU VPD collection was not complete and it did not complete in a reasonable time An error occurred trying to DMA a LID to mainstore The number of I/O paths to the primary FSP is not valid Another component had a failure Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

if the bits are actually Determine if service action or tracking event set Unable to display SRC for PHYP Determine if service action or tracking event On redundant FSPs. there are times when messages from PHYP are blocked and this is Determine if service action or tracking event one of those times Invalid signal received Determine if service action or tracking event An error occurred reading a registry variable Determine if service action or tracking event Failure to write to registry variable Determine if service action or tracking event Unrecognized power off IPL type Determine if service action or tracking event Invalid value read from registry variable Determine if service action or tracking event Invalid value trying to set registry variable to Determine if service action or tracking event An error occurred writing to the registry Determine if service action or tracking event 179 (1xxx) System power control network (SPCN) reference codes .Reference codes B1819200 B1819202 B1819203 B1819206 B1819207 B1819209 B181920A B181920B B181920D B181920E B181920F B1819211 B1819502 B1819505 B1819506 B1819509 B181950A B181950B B181950D B181950E B1819510 B1819516 B1819517 B1819518 B1819519 B181951A B181951B B1819520 B1819521 B1819522 B1819524 B1819525 B1819526 B1819527 B1819902 B1819903 B1819904 B1819905 B1819906 B1819907 B1819908 I/O control failed trying to set the DTR pin Determine if service action or tracking event HVSI received a response to the version query Determine if service action or tracking event but did not get any data OS protocol version does not match currently Determine if service action or tracking event supported FSP version The open on the requested device failed Determine if service action or tracking event HVSI was asked to open a port that did not Determine if service action or tracking event exist Invalid action requested or invalid data passed Determine if service action or tracking event Request for modem control signal status but Determine if service action or tracking event the port is not open Error trying to read status register data Determine if service action or tracking event We failed reading data from the serial port Determine if service action or tracking event Write to the serial port failed Determine if service action or tracking event Failed to close Determine if service action or tracking event Stuck trying to write to serial port for more than Determine if service action or tracking event 2 seconds Unable to unlock an HMC queue mutex Determine if service action or tracking event Unable to post semaphore to wake up Determine if service action or tracking event processing thread Couldn't create the thread Determine if service action or tracking event The wrong number of bytes were written on Determine if service action or tracking event mailbox interface No bytes were returned on mailbox read Determine if service action or tracking event Failed to send message to PHYP Determine if service action or tracking event The size of data being sent exceeds the TCE size or the TCE's have never been allocated Determine if service action or tracking event and written to the registry Unable to start timer to block code update on Determine if service action or tracking event DPO Bad status in network response message Determine if service action or tracking event Got a socket message that doesn't belong to Determine if service action or tracking event this sender Unable to receive the error/event log from the Determine if service action or tracking event daemon Failed operating system call Determine if service action or tracking event Bad parameter for function Determine if service action or tracking event IPL handshake failed Determine if service action or tracking event Dump other than platform or FSP is being Determine if service action or tracking event invalidated State manager never made it to desired state Determine if service action or tracking event in time we waited HMC ID is too big Determine if service action or tracking event Daemon is down Determine if service action or tracking event Unable to clear bits in DSISR so PHYP may stop talking to the FSP. there are times when messages to PHYP are blocked and this is Determine if service action or tracking event one of those times On redundant FSPs.

Probably invalid function number Unexpected signal received An unsupported event id was received Failed to select socket Timed out waiting for select Failed to select socket Timed out waiting for select The client has gone away The server has gone away Failure building the display Error while attempting to program panel buttons or displaying to Panel Failed to read path from registry Failed to remove an old message queue Event message queue send failed Event message queue receive failed Failed to allocate memory for event Failed thread conditional broadcast Failed to create thread Failed to synchronize with server process An error occurred while reading a Registry value Failed to synchronize with client process VPNL returned error while executing the specified function Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .Reference codes B1819909 B181990A B181A000 B181A001 B181A004 B181A005 B181A006 B181A007 B181A008 B181A009 B181A00A B181A00B B181A00E B181A00E B181A00F B181A010 B181A012 B181A013 B181A015 B181A016 B181A017 B181A018 B181A019 B181A01C B181A01D B181A01E B181A01F B181A021 B181A024 B181A025 B181A027 B181A028 B181A029 B181A02A B181A02B B181A02C B181A02E B181A02F B181A031 B181A032 B181A033 B181A036 B181A038 B181A039 B181A03A B181A040 B181A041 B181A042 B181A043 B181A044 B181A049 180 Failure to write to registry for Controlled Power Off Failure to write to registry for Loss of AC Power Input parameter is incorrect Socket connect failure Send system call has failed Send length not equal to the message length Received length not equal to the server message length Invalid parameter Socket system call failed for server socket Bind system call has failed for server socket Listen system call has failed for server socket Failed to accept socket Failed to receive message Failed to receive message Socket connect failure Send system call failure An error occurred reading the P0 root path from the registry Trying to set invalid power state Response doesn't match request Incorrect mode Function requested is disabled Invalid subfunction number Function range is disabled Sequence error Timer creation error Resetting timer has failed Resetting scroll lock has failed Error in starting process as a daemon Failure to start thread Type undefined for given function.

MLx system with the new FSP cables Failure to initialize thread attribute variable Determine if service action or tracking event Failure to set thread attribute variable Determine if service action or tracking event Failure to cancel thread Determine if service action or tracking event Failed to get VPD state Determine if service action or tracking event Failed to get the maximum number of RIDs Determine if service action or tracking event from VPD Failed to get RID number from VPD Determine if service action or tracking event More than one op-panel is physically present Determine if service action or tracking event in the system The caller's array is too small to contain all the Determine if service action or tracking event data Experienced a problem while trying to detect Determine if service action or tracking event old message queue Timed out waiting for the thread to exit Determine if service action or tracking event Error while waiting for thread to exit Determine if service action or tracking event Error waiting on the 'CCM complete' condition Determine if service action or tracking event Only the primary FSP can activate an op-panel Determine if service action or tracking event Failed to get power state Determine if service action or tracking event An error occurred trying to extract the Display SRC function symbol from the panel client Determine if service action or tracking event library An error occurred trying to setup the environment to have the correct library path for Determine if service action or tracking event finding the panel client library Error reading VPD Determine if service action or tracking event Invalid RID count Determine if service action or tracking event No sibling FSP found Determine if service action or tracking event Invalid field update specified in request Determine if service action or tracking event An unsupported operation was requested Determine if service action or tracking event Failed IPL request Determine if service action or tracking event Error returned from IPL lock function Determine if service action or tracking event Failed lamp test Determine if service action or tracking event Error returned while reading registry Determine if service action or tracking event Registry write failure Determine if service action or tracking event The operation request is not allowed because Determine if service action or tracking event it was requested on the backup FSP Invalid request from caller Determine if service action or tracking event This request has NULL output data pointer Determine if service action or tracking event Error returned from dump function Determine if service action or tracking event The requested function is not within the valid Determine if service action or tracking event range or it is an unsupported function Error from mailbox Determine if service action or tracking event 181 (1xxx) System power control network (SPCN) reference codes .Reference codes B181A050 B181A051 B181A054 B181A055 B181A056 B181A057 B181A058 B181A059 B181A05A B181A061 B181A062 B181A063 B181A064 B181A065 B181A066 B181A069 B181A071 B181A072 B181A073 B181A074 B181A075 B181A076 B181A077 B181A078 B181A079 B181A07A B181A07B B181A07C B181A201 B181A203 B181A204 B181A206 B181A207 B181A208 B181A209 B181A20A B181A20B B181A20C B181A20D B181A20E B181A20F Error getting function state Determine if service action or tracking event The caller has elected to NOT wait for VPD Determine if service action or tracking event collection to complete The specified RID does not correspond to a Determine if service action or tracking event physically present op-panel An op-panel is currently active. and therefore the 'deactivate' request cannot be Determine if service action or tracking event performed This event indicates that the panel will not be activated for the system because it is a Determine if service action or tracking event Redundant FSP. and therefore Determine if service action or tracking event the 'activate' request cannot be performed Another concurrent maintenance operation is Determine if service action or tracking event in progress Failure to lock a mutex Determine if service action or tracking event Failure to unlock a mutex Determine if service action or tracking event An op-panel is not currently active.

Reference codes B181A211 B181A214 B181A215 B181A216 B181A217 B181A219 B181B000 B181B001 B181B004 B181B005 B181B006 B181B009 B181B00A B181B00B B181B00C B181B00E B181B00F B181B010 B181B011 B181B012 B181B013 B181B014 B181B015 B181B016 B181B017 B181B01B B181B01C B181B01D B181B01E B181B01F B181B020 B181B024 B181B027 B181B028 B181B02A B181B02C B181B030 B181B031 B181B032 B181B033 B181B035 B181B036 B181B037 B181B038 B181B03A 182 Rejected specified function/ subfunction Determine if service action or tracking event request The requested function is not within the valid Determine if service action or tracking event range or it is an unsupported function SPCN Panel function (07) is disabled Determine if service action or tracking event FSP dump failed Determine if service action or tracking event Requested subfunction is outside the valid Determine if service action or tracking event range Invalid signal received by process Determine if service action or tracking event Invalid parameter passed by the user Determine if service action or tracking event Update for the given keyword not allowed for Determine if service action or tracking event second time Cannot find given record Determine if service action or tracking event VTOC record not found Determine if service action or tracking event Failure reading / finding the module VPD file Determine if service action or tracking event RLCA Index greater than number of RLCA Determine if service action or tracking event entries Invalid length of parameter Determine if service action or tracking event Failure to read VPD File Path registry Determine if service action or tracking event Error reading NVRAM entry Determine if service action or tracking event We had an error opening the file for the given Determine if service action or tracking event resource ID We were unable to gain a lock on a VPD file Determine if service action or tracking event We had an error reading the VPD file Determine if service action or tracking event We were unable to unlock the file Determine if service action or tracking event Unable to build location code for the FRU Determine if service action or tracking event Error trying to locate the file Determine if service action or tracking event Invalid format for the VPD Determine if service action or tracking event Error renaming file Determine if service action or tracking event We had an error closing and/or unlocking the Determine if service action or tracking event file Cannot find given keyword in the block Determine if service action or tracking event Cannot read VPD node for the given RID Determine if service action or tracking event Cannot find PT keyword in the VTOC record Determine if service action or tracking event Invalid input buffer length Determine if service action or tracking event Error while writing to the registry Determine if service action or tracking event Failure reading configurated id of machine Determine if service action or tracking event model registry Invalid parameter passed by the user Determine if service action or tracking event Error reading ECC for VHDR block Determine if service action or tracking event Invalid VTOC record length Determine if service action or tracking event We failed trying to get smart chip block size Determine if service action or tracking event Error initializing smart chips Determine if service action or tracking event There was a failure trying to update one of the Determine if service action or tracking event smart chip blocks Unable to find input resource ID in the RID Determine if service action or tracking event table Cannot find rlca index for the given location Determine if service action or tracking event code We were trying to generate a FRU callout because we had an error in one of the external Determine if service action or tracking event interface and in process of generating that error we ran into another error Cannot find MF tag for 1002 slotmap Determine if service action or tracking event Error writing Machine Brand registry Determine if service action or tracking event We failed trying to get smart chip block size Determine if service action or tracking event Invalid length for the keyword in the VPD Determine if service action or tracking event Invalid Block id passed by the user Determine if service action or tracking event Unable to find input resource ID in the RID Determine if service action or tracking event table (1xxx) System power control network (SPCN) reference codes .

Found zero number of VSRC entries Zero plug count found for the given RID Unsupported Resource Type Unsupported Record Type Offset is greater than buffer size Invalid 200A Slotmap Cannot find rlca index for the given slca index Cannot find rlca index Failure to write Registry with Raw VPD data Unable to use either VPD Chip because we could not reach them or they are garded out Incorrect size passed in by user Caller has asked us to update an invalid type of FRU Failed to read anchor card VPD Error converting to multiple stanza format converged VPD Error converting to multiple stanza format keyword format VPD Failed to process VPD chip Failed to get RLCA index for a resource ID We read an invalid Machine Type Model from the VPD Legacy SC buffer greater than original buffer Cannot find old file in directory Failed to write RLCA table No valid Service Processor VPD was found on this system No VPD collected for given processor card Pin failure failed after root node mismatch Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 183 (1xxx) System power control network (SPCN) reference codes .Reference codes B181B03B B181B03C B181B03D B181B03E B181B03F B181B040 B181B041 B181B043 B181B044 B181B045 B181B046 B181B049 B181B04A B181B04B B181B04C B181B04E B181B04F B181B050 B181B051 B181B052 B181B053 B181B054 B181B055 B181B056 B181B057 B181B059 B181B05A B181B05B B181B05C B181B05D B181B061 B181B063 B181B064 B181B065 B181B067 B181B068 B181B06D B181B06E B181B073 B181B07A B181B07C B181B07E B181B080 B181B082 B181B083 Cannot find data port node for VRM information Error initializing I2C devices Writing to I2C device failed Error trying to read the module VPD from the I2C Chip Reading thermal sensor data failed for the given FRU Invalid controller type for frequency controller Someone has requested the SMP cable ID on a non MLx system Invalid RID or invalid FSP ID The Input RID does not have a redundant resource associated with it Invalid bit definition for 9551 controllers Invalid bit definition for 9552 controllers Invalid data Invalid keyword format VPD Invalid description length for keyword format VPD Invalid offset found in the keyword format VPD Invalid offset No 0x84 tag found Invalid offset for the PT keyword in VTOC record Invalid VTOC record offset Invalid VHDR record size Error reading "PR" keyword from the VINI record for the given RID Invalid IN keyword size.

Reference codes B181B084 B181B085 B181B086 B181B087 B181B088 B181B089 B181B08A B181B08B B181B08C B181B08D B181B08E B181B08F B181B090 B181B091 B181B092 B181B093 B181B094 B181B095 B181B097 B181B098 B181B099 B181B09A B181B09B B181B09C B181B09D B181B09E B181B09F B181B0A0 B181B0A1 B181B0A2 B181B0A3 B181B0A4 B181B0A5 184 Pin failure is successful after root node Determine if service action or tracking event mismatch Invalid FRU Detect Data Port Type Found in Determine if service action or tracking event VPD We failed when trying to read the SMP cable Determine if service action or tracking event ID from the 9552 controller on this MLx system VPD Firmware had an error in trying to detect if this FRU was actually present or not on the Determine if service action or tracking event system No plug detect node found for this RID but the Determine if service action or tracking event RLCA table said there should be Error in finding out which FSP it is Determine if service action or tracking event We were unable to determine the maximum number of Resource ID's for the input FRU Determine if service action or tracking event type Failed trying to determine the Resource ID's Determine if service action or tracking event associated with the given FRU type We had a failure finding the LED node for this Determine if service action or tracking event processor card We had a failure reading the SMP cable ID on Determine if service action or tracking event a processor card We had a mismatch in the cable ID between Determine if service action or tracking event two processor cards There was a failure trying to configure Determine if service action or tracking event 9555/9554 controller There was a failure trying to create smart chip Determine if service action or tracking event blocks Error occurred while locking/unlocking DASD Determine if service action or tracking event device VPD Firmware had an error in trying to read Determine if service action or tracking event the size of a registry key Failed to open source directory while copying Determine if service action or tracking event a directory Locking the VPD file has failed Determine if service action or tracking event Unlocking the VPD file has failed Determine if service action or tracking event Cannot find DR keyword in the given record Determine if service action or tracking event while updating legacy smart chip VPD TM field is already updated once. Second update for the given keyword not allowed Determine if service action or tracking event because TYPE part of MTM does not match Firmware needs to add support for an Determine if service action or tracking event additional resource to the given FRU type Failed to get FRU status for the given RID in Determine if service action or tracking event registry update function Failed to read the VPD and update the registry Determine if service action or tracking event entry for the input RID Error writing NVRAM to VPD Determine if service action or tracking event Mismatch in VPD vs NVRAM Determine if service action or tracking event Failed to write System NVRAM values out to Determine if service action or tracking event VPD Failed to write Enclosure NVRAM values out Determine if service action or tracking event to VPD Unable to add FRU to the rlcaTable because instanceTable shows no more FRU addition Determine if service action or tracking event allowed Invalid algorithm type found in the VPD node Determine if service action or tracking event for the given RID in the rlcaTable Failed to update GARD with a resource ID Determine if service action or tracking event Failed to GARD out a resource ID Determine if service action or tracking event Failed to determine if chip is garded out or not Determine if service action or tracking event A chip on the Anchor card has been garded Determine if service action or tracking event out (1xxx) System power control network (SPCN) reference codes .

but the buffer provided is not large enough to hold a maximum length location code Location code for the associated resource ID has a length mismatch Call made to read location code. but the buffer reference provided was a NULL pointer Failed to get number of headers from VPD Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 185 (1xxx) System power control network (SPCN) reference codes .Reference codes B181B0A7 B181B0A8 B181B0A9 B181B0AA B181B0AB B181B0AD B181B0AF B181B0B5 B181B0B6 B181B0B7 B181B0B8 B181B0B9 B181B0BB B181B0BC B181B0BD B181B0BE B181B0BF B181B0C0 B181B0C1 B181B0C2 B181B0C4 B181B0C5 B181B0C6 B181B0C7 B181B0C8 B181B0C9 B181B0CA B181B0CB B181B0CC B181B101 B181B102 B181B103 B181B104 B181B105 B181B106 B181B107 B181B108 B181B109 B181B10B Failure to write registry for update status Failure attempting to read the system configuration file Failed to input line from system file Mismatch SN or PN between primary and redundant fsp recollect during VPD verification Error reading smart chip legacy block size Error reading Raw Machine type model registry Failed to process message for VPD Cannot find RID for FRU_SP for this FSP Error synchronizing file to the other FSP Error reading system type registry Error converting FRU type Error converting FRU type Sibling FSP state is set to NOT working Unable to locate string in file Invalid number of processor cards are present Checksum in the VPD data does not match calculated checksum Someone tries to read/write a keyword in corrupt VPD Failure in getting the other RID from the system configuration file Error in updating CCMM registry with the new primary RID VPD is not collected both for primary RID and redundant RID or its child RID Failed to read GPIO pin value from FSP extender Invalid number rlcaTable entries New value has been written to the hyperboot capability registry Error while getting the hyperboot capability registry value VPD could not collect more Oppanel VPD for ASMI No Oppanels present in system Invalid raw brand name Failed to copy or rename directory Failed to remove directory VPD indicates that no VPD headers are available Location code for the associated resource ID not found in the VPD header array Location code for the associated resource ID is not NULL terminated Parent location code of resource ID being processed is not null terminated The length of the location code being built is going to exceed the maximum allowed Call made to read location code for a resource ID of zero Call made to read location code.

but the input location code was not NULL terminated Call was made drive an LED to a specific state but the class controller type is invalid or not supported Failed to open I2C bus Failed to close I2C bus Failed to transmit data on I2C bus Failed to transmit data to the LED lightstrip controller Failed to lock the I2C hub The specified LED state is not valid Failed to get GMNOL from VPD Failed to get GAL from VPD Call was made to read the number of enclosure LEDs. no "VV" entry was found in the rlca An FRU_ID "VV" root was being processed and an error was returned An enclosure was being processed and an error was returned User input invalid parameter Error returned from reading VPD registry Could not find VPD registry entry Call was made to read location codes. but a NULL buffer pointer was provided Call was made to read location codes. However. but the input buffer provided is not large enough to hold all the LED location codes Call was made to get LED access data. but none was found Failed to read LED location codes Failed to drive LED to specified state Failed to drive LED to specified state Failed to transmit data to the I2C hub Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes . but the input location code pointer was NULL Call was made to get LED access data.Reference codes B181B10C B181B10D B181B10E B181B10F B181B110 B181B111 B181B112 B181B113 B181B114 B181B115 B181B116 B181B117 B181B118 B181B119 B181B11A B181B11B B181B11C B181B11D B181B11E B181B11F B181B120 B181B121 B181B201 B181B202 B181B204 B181B205 B181B207 B181B208 B181B209 B181B20A B181B20B B181B20C B181B20D B181B20E B181B20F B181B210 B181B211 B181B212 B181B213 B181B214 186 Failed to get all headers from VPD Failed to process a resource ID Failed to get maximum number of RIDs for enclosure Failed to get RID numbers for enclosure Failed to get enclosure number and index using RID Error reading enclosure Feature Code and model data Error reading system Type/Model data Error reading system serial number data Error updating location code Failed to get RID number of children Maximum number of RIDs returned is zero Data length mismatch while reading enclosure Feature Code and model data Data length mismatch while reading enclosure serial number data Data length mismatch while reading system type/model data Data length mismatch while reading system serial number data Failed to read rlca table from VPD The rlca was searched for a FRU_ID of "VV" which is the starting point of the VPD tree.

Reference codes B181B215 B181C000 B181C001 B181C002 B181C003 B181C004 B181C005 B181C006 B181C007 B181C008 B181C009 B181C00A B181C00B B181C00C B181C00D B181C00E B181C00F B181C010 B181C011 B181C012 B181C013 B181C014 B181C015 B181C016 B181C017 B181C018 B181C019 B181C01A B181C01B B181C01C B181C01D B181C01E B181C01F B181C020 B181C021 B181C022 B181C023 B181C024 B181C025 B181D101 B181D102 B181D103 B181D107 B181D108 Failed to transmit park data to the I2C hub Determine if service action or tracking event VPD failure Determine if service action or tracking event Session entry failure Determine if service action or tracking event Failed network client call Determine if service action or tracking event Invalid authentication level or requestor was Determine if service action or tracking event set PHyp returned an error when attempting to Determine if service action or tracking event open a PHyp session Data buffer error Determine if service action or tracking event Failed Mailbox function call Determine if service action or tracking event Failed to read from or write to a registry entry Determine if service action or tracking event Internal event error Determine if service action or tracking event Internal file error Determine if service action or tracking event Internal VTTY error Determine if service action or tracking event Failed to signal a broadcast event Determine if service action or tracking event Failed to successfully create a virtual serial object while running the virtual serial open Determine if service action or tracking event command A virtual serial client attempted to open a virtual serial session before PHYP reached Determine if service action or tracking event standby/runtime state The DMA component returned an error log Determine if service action or tracking event while attempting to read the VTTY buffer Received an error while trying to access the Determine if service action or tracking event leds file Received an error while accessing the semaphore object for the leds table during the Determine if service action or tracking event lock table command API error Determine if service action or tracking event Failure to calculate the timestamp stored in the Determine if service action or tracking event session entry object Failed to acknowledge surveillance Determine if service action or tracking event Internal lock error Determine if service action or tracking event Failed to obtain file lock Determine if service action or tracking event Failed to release file lock Determine if service action or tracking event Failed to access a file through the utility Determine if service action or tracking event Unable to authenticate password for an Determine if service action or tracking event authorized virtual serial session Failed to reset reload Determine if service action or tracking event PHYP status error Determine if service action or tracking event HMC/FSP interface protocol violation Determine if service action or tracking event Internal error Determine if service action or tracking event Protocol error Determine if service action or tracking event Failed to get the cage and frame number Determine if service action or tracking event Did not receive a valid data length or ack value Determine if service action or tracking event MP command cannot be executed since MP Determine if service action or tracking event state is incorrect Failed to write partial lid for code update Determine if service action or tracking event Internal error Determine if service action or tracking event Precondition failure Determine if service action or tracking event Request to open a PHyp connection was denied because the tool type is not allowed to Determine if service action or tracking event perform that operation Concurrent maintenance lock access failure Determine if service action or tracking event Failed to write to file Determine if service action or tracking event Failed to read breakpoint attention Determine if service action or tracking event File write operation failed Determine if service action or tracking event Failed to initialize the Hypervisor service Determine if service action or tracking event routine flag Failed to read from registry Determine if service action or tracking event 187 (1xxx) System power control network (SPCN) reference codes .

power off or dump transition Manufacturing interface to read the policy flag failed Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .Reference codes B181D10A B181D10C B181D10D B181D10E B181D10F B181D110 B181D111 B181D112 B181D113 B181D115 B181D116 B181D117 B181D118 B181D119 B181D11A B181D11C B181D11D B181D11E B181D11F B181D120 B181D121 B181D122 B181D123 B181D124 B181D125 B181D126 B181D127 B181D128 B181D129 B181D12A B181D12B B181D12C B181D12D B181D12E B181D130 B181D131 B181D132 B181D133 B181D134 B181D135 B181D136 B181D137 B181D138 B181D139 188 Null pointer while trying to enable attentions Failure in Unmask attentions interface JTAG failed while waiting for attention Failed to write to MainStore JTAG read failure while reading the Interrupt Status Register Fail to get the Hardware level in the JTAG controller Failed to enable attentions Timeout while waiting for JTAG lock Request for system dump failed after getting attention Utility read failure on a breakpoint attention Utility write failure while writing the terminate flag Failure while trying to open a file on a breakpoint attention Phyp wrote an invalid SRC in the attention area in MainStore Master FSP Communications failure Utility write failure while writing the terminate flag Spurious attention detected after attempt to clear all attentions for ISR Failed to get the reserve Failed while attempting to release the reserve No error created on a processor checkstop Failed to read mainstore after a breakpoint attention Failed to write to mainstore after a breakpoint attention Failed to write the ISR back to the JTAG controller Failed to release the JTAG lock Failure when getting functional group Failure while mapping mainstore to get attention area Failed while reading the mainstore area Get data failure Failure to instantiate an object Attentions not found exceeded threshold Server process failed Interface failure Interface failure Interface failure Disable attentions failed Interface failure on an asset protection attention A trace trigger attention was detected Detected a clock stop on error attention Server process failed Failed to synchronize with client process Utility read failed to read the current state of the State Manager Invalid type of attention A TI was detected during either dump.

Reference codes Call to generate event failed during a Non IO checkstop Utility read failed to read the current role of the B181D13A Determine if service action or tracking event FSP B181D13B FSP Dump event timed out Determine if service action or tracking event Reset reload while handling P5IOC recovered B181D13C Determine if service action or tracking event error Call home enabled but no destination phone B181E001 Determine if service action or tracking event numbers programmed B181E002 Failed to receive message Determine if service action or tracking event B181E003 Pager data was not programmed Determine if service action or tracking event B181E004 Error writing to serial port Determine if service action or tracking event The customer AGN account information is B181E005 Determine if service action or tracking event missing B181E006 Missing data from setup Determine if service action or tracking event B181E007 Failed fork system call Determine if service action or tracking event B181E008 Failed to rebuild the error log during call home Determine if service action or tracking event B181E009 Failed fork system call Determine if service action or tracking event B181E00A Child process failed Determine if service action or tracking event B181E00B Child process failed Determine if service action or tracking event B181E00C Child process died due to unhandled signal Determine if service action or tracking event B181E00D Child process died due to unhandled signal Determine if service action or tracking event Failed trying to put the symptom string B181E00E Determine if service action or tracking event together B181E010 Serial port open failed Determine if service action or tracking event B181E011 The file descriptor was is not valid Determine if service action or tracking event B181E012 Failed select system call Determine if service action or tracking event B181E015 Sending message on socket failed Determine if service action or tracking event B181E016 Failed to get socket Determine if service action or tracking event B181E017 Failed to get socket Determine if service action or tracking event B181E01E Call home test Determine if service action or tracking event B181E01F User issued a call home test Determine if service action or tracking event B181E025 Failed serial port echo Determine if service action or tracking event B181E026 Failed serial port echo Determine if service action or tracking event Trying to do call home test on same port that B181E027 Determine if service action or tracking event ASMI is active on Trying to do call home test on same port that B181E028 Determine if service action or tracking event ASMI is active on String was found in the input data and the B181E101 Determine if service action or tracking event system reIPL has been requested B181E201 Received an error and did not attempt a reboot Determine if service action or tracking event Received an error waiting for the backup FSP B181E202 Determine if service action or tracking event to terminate B181E303 Invalid modifier Determine if service action or tracking event B181E30B Cannot Query for LED Table Determine if service action or tracking event The request sent in is not a valid request type B181E30D Determine if service action or tracking event for this function B181E310 Invalid request type Determine if service action or tracking event B181E315 Failed on retry for SPCN command Determine if service action or tracking event B181E31B Failed to get LED state control Determine if service action or tracking event SPCN PRS command to collect LED data did B181E31C Determine if service action or tracking event not return any data SPCN command to control the physical B181E31D Determine if service action or tracking event attention LED has failed B181E31E Failed to get location code table from PHYP Determine if service action or tracking event B181E400 Attempt to open file failed Determine if service action or tracking event B181E401 Attempt to open file failed Determine if service action or tracking event B181E402 Attempt to open file failed Determine if service action or tracking event B181E403 Attempt to close file failed Determine if service action or tracking event B181E404 Attempt to close file failed Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes 189 .

Reference codes B181E405 B181E406 B181E407 B181E408 B181E409 B181E40A B181E40B B181E40C B181E40D B181E40E B181E40F B181E411 B181E412 B181E425 B181E426 B181E427 B181E428 B181E429 B181E42A B181E42F B181E430 B181E432 B181E436 B181E437 B181E438 B181E439 B181E43A B181E43B B181E43C B181E43D B181E43E B181E43F B181E440 B181E441 B181E443 B181E444 B181E445 B181E446 B181E448 B181E449 B181E44A B181E44F B181E451 B181E453 B181E454 B181E455 B181E457 190 Attempt to open file failed Determine if service action or tracking event Attempt to open file failed Determine if service action or tracking event Attempt to open file failed Determine if service action or tracking event Attempt to close file failed Determine if service action or tracking event Attempt to close file failed Determine if service action or tracking event Detected DRAM Recovered Errors Determine if service action or tracking event Detected NVRAM Recovered Errors Determine if service action or tracking event Failed to get statistics Determine if service action or tracking event Attempt to open directory failed Determine if service action or tracking event Attempt to open file failed Determine if service action or tracking event File system corrupted Determine if service action or tracking event Failed to get the maximum number of RIDs Determine if service action or tracking event from VPD Failed to get the RID from VPD Determine if service action or tracking event Failed to initialize thread attributes Determine if service action or tracking event Failed to set thread to deattached state Determine if service action or tracking event Attempt to accept a client request failed Determine if service action or tracking event Attempt to receive client message failed Determine if service action or tracking event Failed to send response to client Determine if service action or tracking event Unknown client command received Determine if service action or tracking event Another instance of the process is already Determine if service action or tracking event running Failed thread call Determine if service action or tracking event System call for mutex failed Determine if service action or tracking event Client failed to send its heartbeat message Determine if service action or tracking event within the stipulated time Error while trying to connect to the daemon Determine if service action or tracking event Error while trying send or receive data with the Determine if service action or tracking event daemon Failed to synchronize with server Determine if service action or tracking event Failed fork system call Determine if service action or tracking event Could not close the client socket Determine if service action or tracking event Error while attempting to close server address Determine if service action or tracking event socket Failed to read path from registry Determine if service action or tracking event Error while trying to signal event to notify HMC Determine if service action or tracking event of the change in the HMC Surveillance Flag Error returned while attempting to write to the Determine if service action or tracking event registry Error returned when attempting to read the Determine if service action or tracking event registry Error trying to notify PHYP of the change in Determine if service action or tracking event HMC flag Invalid type Determine if service action or tracking event Could not flatten log to send to client Determine if service action or tracking event Error while attempting to extract flattened log Determine if service action or tracking event sent from the daemon Client gateway was not able to talk to the Determine if service action or tracking event master FSP Gateway address creation to send surveillance Determine if service action or tracking event heart beat to master FSP failed Failed to connect to client gateway Determine if service action or tracking event Failed to kill the Common Message Server of Determine if service action or tracking event a failed HMC client Error while trying to reset the watchdog timer Determine if service action or tracking event Failed to query managed information Determine if service action or tracking event Attempt to bind to the listening address failed Determine if service action or tracking event Attempt to listen in server address failed Determine if service action or tracking event Attempt to open directory failed Determine if service action or tracking event The mux id requested to ping is not valid Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

Reference codes B181E458 B181E45B B181E45C B181E45D B181E460 B181E462 B181E463 B181E464 B181E500 B181E601 B181E602 B181E604 B181E606 B181E607 B181E608 B181E609 B181E60A B181E60B B181E60C B181E60F B181E610 B181E611 B181E612 B181E613 B181E614 B181E615 B181E616 B181E618 B181E619 B181E61A B181E61B B181E61C B181E61D B181E620 B181E621 B181E622 B181E623 B181E625 B181E627 B181E628 B181E629 B181E62A B181E62B B181E62C B181E62D B181E62F B181E633 B181E634 B181E635 Another component had an error Error while attempting to create listening socket Invalid Response Interval sent Error while trying to create server address Failed to set thread schedule policy Failed to get the maximum allowed thread priority Failed to get the scheduling parameter Failed to set scheduling parameter to thread Bad hardware Error while attempting to read registry Another process is already running Network client failed to send or receive Invalid major operation received Error while attempting to create listening socket Failed to send from network server Failed fork system call Error returned while initializing a thread attribute Error returned while setting a thread attribute Error returned while creating a thread Received an invalid component type while attempting to create handler thread Network client failed to connect Network client failed to send or receive Network client failed to close Failed to synchronize with server Failed to bind to socket Failed to listen to socket Network server failed to connect Failed to initialize mutex Error encountered while locking mutex Error encountered while unlocking mutex Network server failed to close Failed to return log Unknown minor operation id received Invalid operation requested to data correlation handler Failed to create object Network client failed to close Network client failed to send or receive No file name sent in by client Non existent registry variable sent File does not exist Error attempting to open file for reading or writing Error while reading file Error while attempting write registry Error while writing to the file Backup is not running from the same flash side as primary FSP Sibling returned error on the requested operation Error returned while attempting to create event handler object Invalid event id was received Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 191 (1xxx) System power control network (SPCN) reference codes .

Reference codes B181E64A B181E64B B181E64C B181E64D B181E64F B181E650 B181E656 B181E657 B181E659 B181E65B B181E65C B181E65F B181E660 B181E661 B181E663 B181E664 B181E665 B181E666 B181E667 B181E669 B181E66D B181E66E B181E66F B181E678 B181E67B B181E683 B181E684 B181E686 B181E687 B181E689 B181E68A B181E68B B181E68C B181E68F B181E690 B181E692 B181E693 192 Error while attempting to signal Fsp Role Change event Backup FSP has a different level that the primary FSP Primary and backup FSP have different lid levels loaded Error returned when a flattened log was attempted to be restored Error unflattening the log sent by primary FSP Invalid role in the FSP Invalid fail-over type requested MUX control could not be taken Unrecognized routing type received Requested IPL failed Failed to determine fail-over type Surveillance failure of primary FSP detected at pre-standby state Error attempting to determine if the current platform can support redundant FSP The system is in a state where fail-over operation cannot be initiated Sibling returned error on the requested operation Fail-over operation is not allowed Force Terminate and fail-over operation is requested Failed to terminate and force a fail-over Requested FSP IPL failed Invalid IPL type Failed to determine fail-over type AFO request received from primary FSP EFO operation is being performed by backup to take control of the host system Non I/O Path fail EFO operation is being performed by backup to take control of the host system Error while obtaining mux control Failed to close I2C ADAL Error while attempting to read Fsp Role registry Sibling returned error on the requested operation Error in connecting to address to talk to the Common Message Server of a failed HMC client Failed to kill the Common Message Server of a failed HMC client Sibling returned error on the requested operation The fail-over enable key has been changed by HMC Sibling has requested to initiate reset/reload operation Powering off primary FSP to get the hardware muxes released Backup FSP is not at Runtime Fail-over cannot be enabled at runtime without having a backup that has not IPLed the system even once Error trying to get FSP alpha version key Failed check for fail-over capable Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

and Feature Code Failure in attempting to signal event Test of log failed Reset/reload occurred No SRC in log Unable to clear bits in the DISR No routine for reset/reload call Invalid routine for reset/reload call Received unexpected signal Unable to set bits in the DISR Reset/reload occurred Unable to create a session entry object for the specified HMC index Error while packaging outbound payload data for the HMC Failure occurred with another component API Failed to read from or write to registry No Concurrent Maintenance lock found Unable to convert location code to RID Failure occurred with another component API Failure occurred with another component API Failure occurred with another component API Invalid RID for Concurrent Maintenance request Machine type or state incorrect for Concurrent Maintenance operations Node or GX resource failed during hot add Failure occurred with another component API Sequencing failure or cannot write checkpoint because system is transitioning Not enough memory to reserve a GX adapter Failed to read path from registry Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 193 (1xxx) System power control network (SPCN) reference codes .Reference codes B181E699 B181E69D B181E801 B181E802 B181E803 B181E804 B181E805 B181E806 B181E807 B181E808 B181E809 B181E80A B181E80B B181E80C B181E80D B181E80E B181E80F B181E810 B181E811 B181E812 B181E813 B181E814 B181E815 B181E81F B181E901 B181E902 B181E90a B181E90d B181E90e B181E90f B181E910 B181E911 B181EA00 B181EA01 B181EA02 B181EA03 B181EA04 B181EA05 B181EA06 B181EA07 B181EA08 B181EA09 B181EA0A B181EA0B B181EA0C B181EA0D B181EA0E B181EA0F Unknown HMC command received Attempt to restart discovery command received Failure to read from or write to registry Failed to synchronize with client Failure with network server Thread failure Client failure Failure when calling Code Update Failure from Mailbox function Failure to read or write using DMA for SMA Dump Header The SMAs that were selected to perform an MP Fatal Dump did not all complete successfully System Type was not recognized Failure in Load IPC Bootstrap execution Null pointer while iterating through the SMAs Received invalid initialization type input The MP reset procedure failed The MP reset procedure failed The MP reset procedure failed The MP reset procedure failed Failure to find a matching SMA Handle for the inputted SMA id Received a command to invalidate an SMA Dump when no SMA Dump was present Failure in dump utility that reads and formats System Type. Model.

but they are not the appropriate Determine if service action or tracking event ones Concurrent Maintenance operation started Determine if service action or tracking event Concurrent Maintenance operation stopped Determine if service action or tracking event Only one active object is allowed per process Determine if service action or tracking event Failed to detect error in normal path Determine if service action or tracking event Check for valid FSP dump failure Determine if service action or tracking event External failure writing registry Determine if service action or tracking event Inconsistency in saved data header Determine if service action or tracking event Failure reading or writing a file Determine if service action or tracking event Notify PHYP failure Determine if service action or tracking event Failed to update headers Determine if service action or tracking event Failed to update headers Determine if service action or tracking event Failed to update headers Determine if service action or tracking event Failed to seek correct position in file Determine if service action or tracking event Failed to display status to Panel Determine if service action or tracking event Failed to enable FSP dump Determine if service action or tracking event I/O controller error Determine if service action or tracking event Failed to signal for HMC notification Determine if service action or tracking event Internal HMC notify failure Determine if service action or tracking event HMC notify failure Determine if service action or tracking event Failed to initialize I/O controller Determine if service action or tracking event Failed to close I/O controller Determine if service action or tracking event Failed to check inputs Determine if service action or tracking event Failed to check inputs Determine if service action or tracking event Failed to setup for command Determine if service action or tracking event Failed to setup for command Determine if service action or tracking event Failed to trace command Determine if service action or tracking event Failed to trace command Determine if service action or tracking event Failed to display status to Panel Determine if service action or tracking event Failed to read registry Determine if service action or tracking event Failed to write registry Determine if service action or tracking event Failed to trace command Determine if service action or tracking event Failed to trace command Determine if service action or tracking event NULL command specified Determine if service action or tracking event Failed default command Determine if service action or tracking event Failed to zip memory Determine if service action or tracking event Failed to collect data Determine if service action or tracking event Failed to read registry Determine if service action or tracking event Failed to write registry Determine if service action or tracking event Failed to complete headers Determine if service action or tracking event Failed to complete dumped headers Determine if service action or tracking event Invalid input for FSP dump Determine if service action or tracking event No data to gather for FSP dump specified Determine if service action or tracking event Not enough room left on flash Determine if service action or tracking event Not enough room left on flash Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .Reference codes B181EA10 B181EA11 B181EA12 B181EA13 B181EA14 B181EA15 B181EA16 B181EA17 B181EA18 B181EA19 B181EA1A B181EA1E B181EA1F B181EF01 B181EF02 B181EF03 B181EF0A B181EF0C B181EF0D B181EF0F B181EF11 B181EF12 B181EF13 B181EF17 B181EF1A B181EF1F B181EF28 B181EF2D B181EF2E B181EF2F B181EF32 B181EF33 B181EF34 B181EF35 B181EF36 B181EF37 B181EF38 B181EF39 B181EF3D B181EF3E B181EF3F B181EF40 B181EF41 B181EF42 B181EF44 B181EF45 B181EF46 B181EF4A B181EF4B B181EF4C B181EF4D B181EF52 B181EF53 B181EF54 B181EF55 194 Detected corruption of the GX reservation area Determine if service action or tracking event Failed to send activation asynchronization Determine if service action or tracking event message Failed to create session entry object Determine if service action or tracking event Unable to gard the FSP Determine if service action or tracking event Failed to unlock file mutex Determine if service action or tracking event FSP aborted the transition file Determine if service action or tracking event Failed to send progress code Determine if service action or tracking event Unable to read sibling FSP state data Determine if service action or tracking event Failed to activate power domain Determine if service action or tracking event Abort detected Determine if service action or tracking event The system has new FSP cables attached to the system.

terminate FSP dump sequence FSP dump controller failure Failed I/O boundary device Failed to write FSP dump Failed to check for valid FSP dump Failed to start FSP dump due to not finding FSP dump file Failed to start FSP dump due to not finding FSP dump file Failed to start FSP dump Failed to increment device bank Failed opening FSP dump device for initial navigation Failed to lock FSP dump device Failed to close FSP dump device Failed initial device navigation Failed to close device navigation Code updated forced clear of all pending and existing FSP dumps Failed FSP dump cancellation checking Cancelled dump due to Code update Failed to invalidate FSP dump Failed to retrieve FSP dump A FSP Dump occurred Failed to read registry Failed to set lid for FSP dump A user or surveillance initiated a FSP dump Failed to set header value Failed to check boot watchdog sideswitch Failed to get dynamic MTD sizing Failure in creating a buffer about a critical FSP dump operation FSP dump was invalidated Cannot enable degraded mode as FSP dump device is locked Temporarily disabled function due to code update Code update deallocated part of FSP dump data and user is trying to access them Can't enable degraded mode because there are FSP dumps pending Degraded partition interface error Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 195 (1xxx) System power control network (SPCN) reference codes .Reference codes B181EF56 B181EF57 B181EF5A B181EF5B B181EF5C B181EF5D B181EF5E B181EF5F B181EF62 B181EF63 B181EF64 B181EF65 B181EF66 B181EF67 B181EF69 B181EF6C B181EF6D B181EF71 B181EF73 B181EF75 B181EF79 B181EF7A B181EF7B B181EF7C B181EF7D B181EF7E B181EF7F B181EF80 B181EF81 B181EF82 B181EF83 B181EF84 B181EF85 B181EF86 B181EF87 B181EF88 B181EF8B B181EF8D B181EF8F B181EF90 B181EF91 B181EF93 B181EF94 B181EF95 B181EF96 B181EF97 B181EF98 Moving backwards in the FSP dump file caused error Moving backwards in the FSP dump file caused error Failed to get FSP dump id Failed to get FSP dump length Failed to read registry Failed to read registry Failed to execute Panel function 20 Failed to read registry Failed to execute FSP dump Failed to execute FSP dump Failed to execute FSP dump Out of flash failure FSP dump controller failure acknowledged. must continue FSP dump controller failure acknowledged.

Reference codes Inconsistency in the persistent storage area in flash was detected B181EF99 Multiple FSP dump support logic failure B181EF9A Out of FSP dump storage B181EF9B Failed to open file B181EF9C Failed to read registry B181EF9D Confirm bank enablement failure B181EF9E Persistent storage area was reinitialized General failure during initialization of FSP B181EF9F dump B181F000 Failed to remove directory B181F003 Not able to create directory B181F004 Error return from file open command B181F005 Error return trying to read from a file B181F006 Error returned trying to write to a file B181F007 Failed to get status of file B181F009 Error returned trying to seek offset file B181F00E Error returned from a DMA Write attempt B181F00F Failed to get next file space B181F010 Illegal MDRT section size detected B181F012 Failed to determine size of registry variable B181F013 Error return trying to read from the registry B181F014 Error returned trying to write to the registry B181F015 Error returned from thread function B181F017 Error return from another function B181F018 Received an unexpected signal B181F019 Object not found or returned The requested Policy value is not in the B181F01A bounds Unable to stop Clocks within the dump B181F01B hardware collection Control Block not valid size or invalid flattened B181F01C control block B181F01E Status failure in call to create SRC object B181F022 No file spaces left to store dump memory on System busy or there is no dump pending flag B181F029 set Override Content has change dump type to B181F02C NO DUMP B181F02D A No Dump request was made Manufacturing Policy Flag has set NO DUMP B181F02E policy B181F02F No dump correctable error file present B181F030 Mainstore dump not taken A correctable error was encountered while B181F031 invalidating dump B181F038 Termination of the system to occur Requested to invalidate the dump on the B181F039 system It was determined that no exit error state IPL B181F03B would be needed because no mainstore dump is required B181F03C Mainstore dump not taken Non-user requested dump and the dump B181F03D policy is set to NO DUMP Dump pending. Must invalidate dump before B181F03E another dump can be called B181F100 Invalid position on chain B181F101 No chips in chain B181F102 196 Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes .

Reference codes B181F104 B181F105 B181F10A B181F110 B181F111 B181F118 B181F11A B181F11B B181F125 B181F126 B181F127 B181F128 B181F12C B181F12D B181F12E B181F12F B181F130 B181F131 B181F132 B181F133 B181F134 B181F135 B181F136 B181F138 B181F139 B181F13A B181F13B B181F13D B181F13E B181F140 B181F141 B181F142 B181F200 B181F201 B181F202 B181F206 B181F208 B181F209 B181F20A B181F20B B181F20C B181F20D B181F20E B181F211 B181F212 B181F217 Commands added exceed chain command size Chip not found Invalid Ring buffer size Failure to release lock Failure with controller device driver Invalid device number Abort signaled Failure to release lock Attempt to release lock that is not held Invalid command ID Invalid use of get scom JTAG interface Invalid use of put scom JTAG interface Invalid use of flush JTAG interface Unmatched CRC Chip detected CRC miscompare on scan-in Detected scom attentions Bad parity or invalid command Invalid flush operation code Last bits of chip command status are not 0x01 Invalid ring selection Clocks did not start Could not stop clocks Invalid call to enable drivers Invalid call to disable drivers Scom attention detected on the current chip Master Attention Alone detected Unrecognized attention type condition Invalid function call to attentions Prohibited command found during initialize scom IPL step Unable to find CEC cage Data shows invalid ECID value Indicates a potential problem with clock card Could not get valid hom id of active clock card Configuration failure The HOM unit ID is not present in this system The mainstore memory size has not been properly initialized There is a card in the system that is missing or has corrupted VPD data Avoid following the NULL rule facade pointer The specified card object was not found The call to create a card returned a NULL pointer An error occurred while creating a system domain and returned a NULL pointer There was an error while attempting to create a group and the function returned a NULL group pointer There is an inconsistency between the size of the JTAG chain and the number of JTAG chains counted The chip rule facade pointer created was returned as NULL Creation of a cage pointer failed The cage rule facade pointer was not found An error occurred while attempting to create the JTAG controller object and returned a NULL instance pointer Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 197 (1xxx) System power control network (SPCN) reference codes .

Reference codes B181F21C B181F21D B181F21E B181F21F B181F220 B181F222 B181F225 B181F227 B181F228 B181F22A B181F22B B181F22C B181F239 B181F23E B181F23F B181F241 B181F242 B181F243 B181F244 B181F245 B181F25E B181F2C0 B181F2C1 B181F2CC B181F2CD B181F2DC B181F2DE B181F2DF B181F2E0 B181F2E3 B181F2E4 B181F2E5 B181F2E6 B181F301 B181F304 B181F305 B181F306 198 The instance variable for the JTAG chains is NULL even after successful creation of the chains The FRU was not found or does not exist The MRU or FRU was not found or does not exist Invalid input The functional unit for a JTAG operation was not found The functional unit has experienced a hardware monitor error Attempting to write an invalid frequency to a clock card An invalid VPD port number was encountered A memory block trying to be referenced is out of range There was not enough functional hardware found in the system to continue IPLing A memory controller group pointer was initialized to NULL by the cvMapper Got an invalid unit id Detected a missing chip There is a mismatch between the number of nodes present and the type of SMP cable being used The mainstore configuration changed from the previous IPL. are not present in the system This is an unrecognized cable state for this machine Cannot get a pointer to the System Fabric Group Function pointer from dynamic load is NULL Functional Unit of wrong type Invalid parameter passed in to function Failed trying to release JTAG Controller lock after reading the JTAG Controller's interrupt registers Received an empty list of Chips at attention Elastic Interface Alignment Procedure never completed Fatal IAP Error Non-fatal IAP Error/Warning Couldn't get pointer object Selected elastic interface is Non-functional One or more lines are stuck low for the ISR because the value read back does not match FF's The attention line stuck high test failed to clear all the FSP attention lines Object not initialized Object attributes not set Failed to set scom register attributes Attributes are not set Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes . mainstore cannot be preserved Light strips have not been plugged correctly The slot specified should NOT be turned on PRS data returned indicates that the Light Strip attempting to be powered off was not powered off It seems that both clock cards. which should be present in the system.

it Determine if service action or tracking event should always be positive or zero Failure while trying to open the attention Determine if service action or tracking event handler data file for write operation The bits active in the Special Attention register Determine if service action or tracking event are not supported Object pointer returned NULL Determine if service action or tracking event Clocks need to be on or off but mode says not Determine if service action or tracking event to change state Bad parameter passed into function Determine if service action or tracking event Instructions failed to start Determine if service action or tracking event Instructions failed to step Determine if service action or tracking event Unexpected NULL pointer for Fabric Determine if service action or tracking event Functional unit An attention is active from a thread which is Determine if service action or tracking event not alive Cannot process special attention since Determine if service action or tracking event Memory controller object is null XScom is busy or has errors Determine if service action or tracking event FOCR state machine wasn't idle after clearing Determine if service action or tracking event 199 (1xxx) System power control network (SPCN) reference codes .Reference codes B181F308 B181F309 B181F30A B181F30B B181F30F B181F310 B181F311 B181F312 B181F401 B181F405 B181F407 B181F408 B181F409 B181F40a B181F40b B181F40c B181F40d B181F500 B181F501 B181F502 B181F504 B181F505 B181F506 B181F507 B181F620 B181F621 B181F625 B181F62A B181F62B B181F62E B181F630 B181F633 B181F634 B181F636 B181F638 B181F639 B181F63B B181F63C B181F63D B181F647 B181F648 B181F649 B181F64A Attributes not yet set Determine if service action or tracking event Could not find a Functional Unit that used the Determine if service action or tracking event specified ring or register Data not extracted Determine if service action or tracking event Data not inserted Determine if service action or tracking event Incorrect buffer size Determine if service action or tracking event Incorrect buffer size Determine if service action or tracking event Required register or ring not present Determine if service action or tracking event File open error Determine if service action or tracking event Illegally calling this function Determine if service action or tracking event Could not create cage rule facade for this cage Determine if service action or tracking event Could not find a unique or default entry for this Determine if service action or tracking event combination of inputs Could not read card slot table .end of file or Determine if service action or tracking event file failure End of file reached before row number found Determine if service action or tracking event Size of array needed exceeds size of array Determine if service action or tracking event passed in Number exceeded maximum number allowed Determine if service action or tracking event Could not open library for the object to create Determine if service action or tracking event or unflatten Could not open class for the object to create or Determine if service action or tracking event unflatten File IO error occurred Determine if service action or tracking event The specified HOM Object was not found Determine if service action or tracking event Specified HOM Object does not exist Determine if service action or tracking event The requested function is invalid Determine if service action or tracking event User attempted to save a HOM signature into a data buffer that was too small for the amount Determine if service action or tracking event of data to be saved Got an invalid unit id Determine if service action or tracking event A thread failed to start Determine if service action or tracking event Failure with functional unit Determine if service action or tracking event Scom bus busy after timeout Determine if service action or tracking event Timed out waiting for instructions to stop Determine if service action or tracking event Timeout reached on scom poll Determine if service action or tracking event Tried a clock operation which isn't supported Determine if service action or tracking event on this functional unit Trying to instruction step while they are still Determine if service action or tracking event running I2C lock counter is a negative number.

but doesn't have B181F7AC any attached memory Memory group contains chip in Bus Trace B181F7AD Mode.Reference codes B181F64B B181F64C B181F64D The GR GX auto TLAR calculation failed Failed to complete self synchronization Error encountered during self synchronization Address + entries exceeds maximum SMA B181F64F External SRAM size B181F653 Service buffer timed out while writing data An attention not supported has been detected B181F654 in SMA hardware B181F658 Invalid data Not able to find master or slave target time B181F659 data for a chip GS Figtree database not loaded for this object B181F65A or Functional Unit B181F65D Memory queues are not idle B181F65E Maintenance command timed out B181F65F Maintenance command failed Command in progress while trying to send B181F660 maintenance command Instruction start or stop attempted on non alive B181F661 thread B181F662 Fabric initialization failed on processor B181F663 Fabric initialization failed on processor B181F664 Fabric Quiesce failed B181F67B Got an invalid unit id or NULL pointer B181F67C Calling function on invalid object Operation attempted on nonfunctional B181F67D Functional unit B181F686 Can't get the associated FRU ID B181F689 Could not find associated Chip Unsupported bit(s) set in the local special B181F68C attention register B181F68D Fir bit indicates problem with SP code or SMI B181F6F2 Microcode failed to execute B181F6F3 Microcode failed to execute Bootstrap executed successfully. but base address is zero B181F7AE No system EI table found for bus No entry in system EI data table for bus and B181F7AF master chip position B181F7B8 Resource pointer was NULL B181F7B9 The passed in buffer pointer was NULL B181F7BA Couldn't find frequency data type requested The system resource(s) in the callout list failed B181F7BB a system configuration test 200 Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event (1xxx) System power control network (SPCN) reference codes . but FSP was B181F6F6 not permitted to set MP Available latch The dump file contains a dump and cannot be read by the saved configuration for fast boot B181F7A0 feature to examine the previous system configuration B181F7A1 Figtree library call failed B181F7A2 No TCE region found for GX Controller No valid MC PLL Multiplier found when MC B181F7A7 uses internal clock source B181F7A8 Host PCI enable failed B181F7A9 Host PCI verify failed Memory Sharing Group is an invalid B181F7AB configuration A chip is in Bus Trace Mode.

Does not map to any memory B181F814 location B181F815 Invalid Data Length specified B181F816 NULL Rule Chip Facade Pointer B181F817 Error encountered while reading array entry B181F818 Error encountered while writing array entry B181F81b Mismatch data error Unable to allocate buffer or NULL pointer B181F81e detected B181F950 received an unexpected signal B181F951 Error from abort message Buffer is NULL or is too small to hold B181F952 information B181F953 Failed to receive message B181F954 Error creating serial thread in cec server B181F955 Error creating listener thread in cec server B181F956 Failed to get token in cec server B181F957 Invalid command received B181F958 Failure obtaining mutex lock in serial thread B181F959 Error while sending message B181F95A Error while sending message B181F95B Error receiving message in serial thread B181F95E Error initializing cec server daemon B181F95F Invalid arguments B181F966 Error while unflattening HOM data B181F968 Error writing to bit buffer B181F96A Not enough parameters B181F96B No function specified B181F96C Specified function not found B181F96D Too many parameters supplied B181F96E Unknown option specified Some value required for these options is B181F96F missing B181F970 Unknown parameter type B181F971 Input value out of range B181F972 Invalid input character B181F973 String not found in lookup table B181F974 Buffer too small B181F975 Unknown output type B181F978 An HMC requested operation is not supported B181FAA3 Invalid parameter to function Number of packets sent does not equal B181FAA4 number received or CRC not zero B181FAA9 Can't get the sharing group for this Chip (1xxx) System power control network (SPCN) reference codes Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event Determine if service action or tracking event 201 .Reference codes The user specified LMB size is not valid for B181F7BC this system's memory size. so the system will use the default LMB size for this configuration B181F801 NULL Functional Unit Pointer B181F802 Not enough space B181F803 Not enough space B181F804 Index out of bounds B181F805 Failed to read the number of memory chips B181F806 Procedure error using display/alter B181F807 Invalid thread selected for FPSCR B181F809 Unable to associate array ID for address B181F80a Invalid operation specified Unable to Create or remap Logical to Physical B181F80b Mapper B181F80c Could not create server object instance Invalid address.

Determine if service action or tracking event modifier or HMC index PHYP didn't provide enough data to write the LID or the first TCE is too small to contain the Determine if service action or tracking event LID header (although the latter is less likely) (1xxx) System power control network (SPCN) reference codes 202 .Reference codes B181FAB0 B181FAB1 B181FAB2 B181FAB3 B181FB51 B181FB54 B181FD00 B181FD01 B181FD02 B181FD03 B181FD04 B181FD05 B181FD06 B181FD07 B181FD0A B181FD0B B181FD0D B181FD0E B181FD10 B181FD11 B181FD12 B181FD13 B181FD14 B1828811 B182901C B182901D B182901F B1829025 B1829503 B1829504 B1829507 B1829508 B182950C B182950D Physical Status registers not set to link up. test Determine if service action or tracking event can not proceed Number of packets sent does not equal Determine if service action or tracking event number received or CRC not zero RIO test failure Determine if service action or tracking event Galaxy test failed during communication stage Determine if service action or tracking event Maximum number of wire test errors has been Determine if service action or tracking event reached RDT has detected a hardware error Determine if service action or tracking event An FSP or DMA path was GARDed out Determine if service action or tracking event The command line was used to manually Determine if service action or tracking event configure or deconfigure a resource GARD Data did not exist because either it was the first IPL on this machine or NVRAM had Determine if service action or tracking event been cleared GARD detected a new version of the gard data Determine if service action or tracking event area GARD detected corrupt gard date Determine if service action or tracking event GARD could not open the Gard Memory File Determine if service action or tracking event Error trying to read a file Determine if service action or tracking event Error trying to write IO Data to the Gard file Determine if service action or tracking event Failed setting the rank status in the HOM Determine if service action or tracking event Failed setting functional status of a non-rank Determine if service action or tracking event unit Failed to read registry Determine if service action or tracking event Failed to read the VPD data for a given Determine if service action or tracking event resource id The input Resource ID is not an FSP that can Determine if service action or tracking event have its GARD state changed Manual deconfiguration of FSP is not allowed because FSP is already System Deconfigured Determine if service action or tracking event or because we are at runtime This interface was called with more than the Determine if service action or tracking event allowed number of DMA Paths The input DMA path did not match any stored Determine if service action or tracking event in VPD Ungarding the sibling FSP is not allowed at Determine if service action or tracking event Runtime Incorrect command in Attention Area memory as it does not match up with the requested Determine if service action or tracking event Service Routine Failed trying to get status of the LID file Determine if service action or tracking event Failed to get OLC or CONTINUE ACK Determine if service action or tracking event response from PHYP SPIRA does not have sufficient space for the Determine if service action or tracking event data structure Event id which satisfied the monitor was Determine if service action or tracking event incorrect The FSP has queued its maximum number of Determine if service action or tracking event messages to the send queue There is nobody waiting on the message we Determine if service action or tracking event just received from PHYP Unable to write error\event log that PHYP Determine if service action or tracking event wanted PHYP passed the FSP a zero TCE or a TCE Determine if service action or tracking event with something in the top 4 bytes Indicates that PHYP sent the FSP a bad size.

Hardware VPD update facilities are also provided. The dump component also uses DMAE for collecting dumps. we make this Determine if service action or tracking event one up Wrong modifier received on OLC command Determine if service action or tracking event PHYP didn't acknowledge the message that the FSP sent to it within the architected Determine if service action or tracking event timeout value PHYP tried to use a HMC buffer that they Determine if service action or tracking event haven't defined or they don't own PHYP returned non-zero status in the Determine if service action or tracking event acknowledge message Failed on setup for reset/reload Determine if service action or tracking event Failed to get enclosure list Determine if service action or tracking event Failed to set drawer information Determine if service action or tracking event Bad hardware Determine if service action or tracking event Bad TCE returned Determine if service action or tracking event Error function not available Determine if service action or tracking event Bad hardware Determine if service action or tracking event Bad hardware Determine if service action or tracking event Table 3. IRPC manages the low-level IIC bus interface to remote power controllers (RPCs) on some types of servers. Hardware VPD update facilities are also provided. IVPD collects and reports vital product data (VPD) found in the system unit hardware. Data collected from the hardware is analyzed and stored file system of the service processor. Data collected from the hardware is analyzed and stored in the file system of the service processor. The system power interface (SPIF) component provides a communication interface between service processor components and the system power control 203 Control Panel I2C EDAL VPD I2C EDAL '1100'x through '111F'x '1300'x through '13FF'x RPC I2C EDAL Smart Chip VPD EDAL '1400'x through '141F'x '1500'x through '15AF'x Power control code ranges Power Control '2000'x through '204F'x Interface (1xxx) System power control network (SPCN) reference codes . SCED collects and reports VPD found in the system unit hardware.Reference codes B1829511 B1829512 B1829513 B182951A B182951C B182951D B182951E B1829523 B182D004 B182D005 B182E500 B182F023 B1878707 B187E500 B1A3E500 Warning that HMC message has reached Determine if service action or tracking event timeout limit PHYP tried adding an existing HMC buffer to Determine if service action or tracking event the list PHYP is garding the anchor card and since we don't get any SRC from them. VPD collection and reporting provides a system-wide view of the current hardware configuration. DMAE is normally used by the Hypervisor data initialization (HDAT) component during boot. (B1xx) Service processor reason codes' ranges Reason codes for Range End Device Abstraction Layer (EDAL) ranges DMA EDAL '1000'x through '10FF'x Description The direct memory access EDAL component (DMAE ) is a shared library that allow applications to transfer data between system memory and the service processor's address space. The PANL component uses IPNL extensively. IPNL provides an interface to the control panel hardware and handles all of the internal communication details. VPD collection and reporting provides a system-wide view of the current hardware configuration.

which might occur when a user does not follow the update process The DSCV component manages dual service processors in those systems that can have a primary and a secondary service processor. After the code updates successfully and the system reboots from the new code side. This component's functionality is configured by the customer. • During the booting of the managed system. • When the service processor reboots after a code update. this component automatically performs a power-on reboot following an unexpected loss of power. You might see this code when the error occurs: • During the code update (flash) process. It performs this synchronization by evaluating the system when a boot is requested. Writing to flash memory is an example of a dependent operation. If enabled. a user might use the code promote command to copy the new code from the temporary (or T side) to the permanent (or P) side. Note: A dependent operation is an operation that requires that no boot transition request of a certain type be allowed while the operation is being performed. which is when the code update process attempts to verify flash image during the power on process for the system unit. The error can be caused by: • A bad or invalid system firmware image • A service processor failure.Reference codes Remote Power Control IPL Lock '2100'x through '211F'x '2200'x through '222F'x Auto Power On Restart Remote Platform Power On '2300'x through '231F'x '2400'x through '241F'x Thermal Management '2600'x through '261F'x network (SPCN). DSCV exchanges the required information between the service (1xxx) System power control network (SPCN) reference codes System infrastructure ranges Code Update '3000'x through '305F'x Discovery '3500'x through '35FF'x 204 . CUPD controls the updating of firmware on the service processor. for providing an interface which firmware uses to read processor temperatures. and for handling thermal alerts generated by the processor's thermal sensors. which leads to the firmware being unable to perform the code update • Corruption of the update file. The server uses SPIF to obtain the system power state and other data. which is when the service processor makes the redundant boot code. • During the code promotion process. The thermal management component is responsible for reading processor thermal calibration data. The remote platform power on component allows a user to remotely power on a system using the wake on LAN capability (which is accessed via the ASMI) when the system is powered off. REMP manages the high-level communication protocol between the service processor and the RPCs on some types of servers. which occurs when the file is sent from the Hardware Management Console (HMC) or the Hypervisor • An internal code problem • A problem with the network issue • A user error. The IPL lock component synchronizes dependent operations with boot transition requests.

manufacturing and the HMC use to talk to the servers and other applications running on the service processors. When an application encounters a fatal error (that the application determines should lead to system termination). the application uses its error log to call CTRM. After being called. The SBCU component manages the PCI bus switch state in the registry. and so on. The IPLP component manages some of the service processor registry data that is transferred to the Hypervisor at boot time. The PERC component allows a service processor application to collect some flight recorder information (FFDC) when the service processor receives an unexpected signal. The PPIN component monitors for power events. powering on or powering off the system unit. NETC provides wrappers for the TCP/IP and sockets API and serial traffic APIs. such as IPL speed. The NETC component is the client interface plug-in that applications running on the service processor. and so on). performing a platform dump.Reference codes IPL Parameters '4000'x through '402F'x RTC Application '5000'x through '503F'x State Manager State Transition Manager '6000'x through '603F'x '6500'x through '651F'x Error Logging Primary PCI bus Initialization Boot Plug-in '7000'x through '703F'x '7100'x through '711F'x '7200'x through '721F'x processors to establish the various communication links between them. It determines the validity of an IPL request and attempts to IPL the system. The EVEN component provides the facilities to signal and monitor for the occurrence of specified events. It also 205 Service processor firmware utilities ranges Switch BCU utility '8100'x through '811F'x SRC Interface '8200'x through '821F'x CEC Termination '8300'x through '834F'x NVRAM Initialization Event Notification '8400'x through '841F'x '8500'x through '853F'x Process Error Context '8600'x through '861F'x Network Server Network Client '8700'x through '877F'x '8780'x through '87FF'x (1xxx) System power control network (SPCN) reference codes . The NVRI component used to initialize and configure the service processor. and trace SRCs • Retrieve SRC entries from an SRC trace The CTRM (CEC Termination) component terminates the service processor. Note: Two switch states are possible: • The service processor owns the PCI bus • The system unit owns the PCI bus The SRCI component is a service processor utility that allows the user to do the following: • Create. CTRM displays the terminating SRC on the panel and records the error. It is one way of performing interprocess communication within the service processor firmware. entry management. display. such as power on and power off. The STTR component contains the various transition files that the system uses to make the transition from one state to another (for example. The BOOT component reads user preferences and determines which service processor flash side to boot from. logical memory block size. The ERRL component provides data logging. The RTIM component manages the battery-backed real time clock hardware on the service processor. and the reporting of application errors to the operating system. The SMGR component is responsible for supervising the IPL. The NETS code component dynamically loads libraries for the operations and functions that it services. which is the source of the system-level time-of-day (TOD) clock.

regulators and blowers and collects and reports power status. The POWR component controls the power supplies. The UTIL component provides common functionality throughout the service processor environment. such as common file. Typical uses of a Hypervisor service routine include validating a system storage address and performing a system storage dump for a platform dump. so that they can communicate to each other at runtime. The MBOX component handles certain hardware on the service processor (called the mailbox) that is accessible to both the operating system and the service processor. The SINK component synchronizes the time when a server process is ready to interact with a client process. Other components can use the VLED routines to drive the LEDs to the desired state. power VPD. which allows the host operating system to use the serial ports of the service processor as if they were the native serial ports. The VLOC component builds the location code table that the Hypervisor uses. Data collected from the hardware is analyzed and stored in file system of the service processor. The HMCX component provides the communications interface between the HMC and the service processor of the managed system. The mailbox enables the system to transfer small amounts of data between the service processor and operating system. The VLED component provides library routines to drive the LEDs of the system unit. The PANL component processes the pressing of control panel buttons and updates the control panel display appropriately. registry. and temperatures of the system (1xxx) System power control network (SPCN) reference codes External firmware interfaces ranges Hypervisor Data '9000'x through '904F'x Initialization Host Virtual Serial Interface Mailbox Handling '9200'x through '921F'x '9500'x through '952F'x Service Processor Power On Demand Panel Virtual Panel Vital Product Data (VPD) '9900'x through '991F'x 'A000'x through 'A07F'x 'A200'x through 'A21F'x 'B000'x through 'B0FF'x VPD Location Codes 'B100'x through 'B11F'x VPD LED Access 'B200'x through 'B21F'x HMC Interface Power Management 'C000'x through 'C03F'x 'C100'x through 'C1FF'x 206 . The SVPD component collects and reports VPD found in the hardware of the system unit. The HDAT component does the following: • Loads the Hypervisor code into system storage • Gathers various pieces of information that describe the hardware configuration and various boot parameters and loads that data into the main storage • Starts the execution of the processors that run the Hypervisor and the partition firmware The HVSI component provides the host virtual serial interface. VLED uses the SVPD component to provide the bus mapping information. SVPD also provides hardware VPD update facilities. which provides a system-wide view of the current hardware configuration. The VPNL component implements the virtual control panel functions in the firmware. The SCOD component provides information about the state of the previous power off and whether the system lost AC power after the power off. and semaphore manipulation. The HYSR component allows the user to run a Hypervisor service routine from the service processor.Reference codes Hypervisor Service Routine '8800'x through '883F'x Process Synchronization Utility Component '8900'x through '891F'x '8A00'x through '8A1F'x provides a common message format for communication and data packets.

Reference codes

unit and I/O towers and drawers. The MENU component provides both a Web browser interface and a legacy TTY (text based) interface (both are known as the Advanced System Management Interface, or ASMI). The ASMI enables users to configure the service processor, change selected system-level settings, and access certain service processor resources. Attention Handler 'D100'x through 'D13F'x The ATTN component processes the checkstops, recovered errors, and special attentions that come from the hardware. ATTN also makes appropriate calls to components like processor runtime diagnostics (PRD) so that the system properly handles attentions. Reliability, Availability, and Serviceability (RAS) ranges Call-in/Call-out 'E000'x through 'E02F'x The CALL component provides remote service functions (like call home, call in, and call out) and SRC display on serial ports. Snoop/Wrap 'E100'x through 'E11F'x The SNOP component provides the serial port snoop function. SNOP can be used only when the system is in single partition mode. This component also detects the legacy UPS, if present, and reports the number of serial ports available to the operating system. CEC Reboot 'E200'x through 'E21F'x The RBOT component determines if an system unit re-IPL needs to occur after a termination. LED Management 'E300'x through 'E31F'x The LEDS component supports the service indicators (used by to identify failing FRUs) and controls the system attention indicator. Surveillance 'E400'x through 'E460'x The SURV component detects the failures of critical components, such as the Hypervisor or the HMC, and takes the appropriate actions. Processor Runtime 'E500'x through 'E51F'x When the service processor receives an attention from Diagnostics system hardware, PRDF examines the error registers in the system to determine what happened and creates an error log entry that calls out one or more failing items. Note: The E500 code denotes a hardware error, or an error in software other than processor runtime diagnostics. The E501 code is reserved for PRD code errors. Redundancy Manager 'E600'x through 'E6A0'x The RMGR component controls the interactions between the primary and the secondary service processors on a model ESCALA PL 450T/R, ESCALA PL 3250R, or ESCALA PL 6450R system. Synchronization of 'E700'x through 'E71F'x The SYNC component, which is part of the RMGR Redundant Service component, performs data synchronization between Processors the primary and the secondary service processors on a model ESCALA PL 450T/R, ESCALA PL 3250R, or ESCALA PL 6450R system. SMA Dump 'E800'x through 'E81F'x The SDMP component controls the sequencing of the initialization of SMA adapters to the message passing available state. Reset/Reload 'E900'x through 'E91F'x The RSRL component saves the most recent critical error log in the event of a reset or reload event (on the assumption that this log best explains the reason for the reset). In cases where the reset or reload event terminates the system, RSRL sends its error log to the administrator. Concurrent 'EA00'x through 'EA1F'x The CCMM component provides the interface Maintenance between the concurrent maintenance program (which is part of Service Focal Point) on the HMC and the service processor of the managed system . Service Processor 'EF00'x through 'EFCF'x The BDMP component dumps data that the system Dump (Belly-up can use to debug a failure that occurs when the DuMP) service processor and bulk power subsystems encounter an error on servers that are housed in Service Processor Menus 'D000'x through 'D03F'x
(1xxx) System power control network (SPCN) reference codes 207

Reference codes

24-inch racks. The following service processor or bulk power subsystem errors might cause this type of dump: • An application failure that leads to a core dump • A panic of the service processor kernel • An unexpected reset of the service processor or bulk power subsystem • A user-injected dump on the service processor or bulk power subsystem that captures the state of the entire subsystem at a given moment in time After the system detects a checkstop or other hardware error condition, the DUMP component gathers required hardware and possibly system memory contents to facilitate error recreation and analysis. The HJTG component provides an interface for scanning data from firmware into the actual chips or from the chips into the firmware. The JtagInterface object represents the physical JTAG interface that is internal to each hardware chip. Firmware uses this piece of chip logic to communicate with the chip, and it is used anytime a JTAG operation is performed. The HPKU component is a package management class that holds and manages the system hardware object model. The HFUG component provides procedural support for chip functionality. The HREG (HOM register) component provides a firmware object that represents a scan ring, SCOM register, or an alias, with its unique characteristics (address, length, etc.) in order to scan chips. HREG also provides the data storage area (called a bit buffer) that holds the data to be scanned as well as the algorithms the system uses to manipulate the data stored in the buffer. The RULE component provides access to certain configuration and engineering data that is stored in the esw_rtbl component. The system uses the data stored in the edw_rtbl component to model the system and to read from the hardware. The RTBL component holds data. The HUTL component provides common utility functions used by all of the hardware access code. HUTL also handles error logging and recovery actions for the system unit hardware during booting and execution of high-level boot steps related to initializing the system unit. The HFUS component provides internal access to the chip functionality. The CINI component initializes the chips in the system unit, based on the system configuration. These actions include configuring system memory and address ranges, chip modes, and communicating from chip to chip. CINI also determines and sets the processor and bus frequencies. The DADA component accesses (reads) and manipulates (writes) user information inside the system unit hardware by using the JTAG interfaces. Several hardware components use this functionality, including the certain CPU chips, L3 cache devices,
(1xxx) System power control network (SPCN) reference codes

Dump

'F000'x through 'F03F'x

Hardware Object Model (HOM) ranges HOM JTAG Interface 'F100'x through 'F16F'x

HOM Packaging Units 'F200'x through 'F25F'x HOM Groups HOM Scan Rings 'F2C0'x through 'F2FF'x 'F300'x through 'F31F'x

HOM Rules

'F400'x through 'F41F'x

HOM Rules Tables HOM Utilities

'F450'x through 'F46F'x 'F500'x through 'F51F'x

HOM Functional Units 'F620'x through 'F6FF'x Central Electronics Complex (CEC) ranges CEC Chip Initialization 'F700'x through 'F7FF'x

Display/Alter

'F800'x through 'F81F'x

208

Reference codes

Hardware Interface Commands Automated Built-in Self-Test (ABIST)

'F950'x through 'F98F'x

'FA00'x through 'FA1F'x

Logic Built-in Self-Test 'FA50'x through 'FA6F'x (LBIST)

Memory Diagnostics

'FAA0'x through 'FABF'x

SIBATS Wiretest

'FB00'x through 'FB1F'x 'FB50'x through 'FB6F'x

Ring API (CEC Utility) 'FC00'x through 'FC1F'x Resource Guard 'FD00'x through 'FD1F'x

and I/O controllers. The CHIC component provides the mechanism that allows a call made in an external service processor application to execute inside the system unit server application. The ABST component runs internal chip diagnostics as part of the system boot process. ABST tests the logic and arrays in each chip (as applicable) and peforms array repair (bit sparing) for processor chips, if necessary. The LBST component runs internal chip diagnostics as part of the system IPL process. LBST tests the logic and arrays in each chip (as applicable) and performs array repair (bit sparing) for processor chips, if necessary. The MDIA component performs diagnostics on the system memory and L3 cache during the boot process by writing patterns into and reading the patterns back from system storage and L3 cache. The SBAT component is part of the LBIST component. The WIRE component, a diagnostic routine used when the system is booted in slow mode, verifies the continuity and independence of interconnections in the system unit. WIRE checks for open and short circuits on the testable nets between chips. The RAPI component does not display reason codes. The GARD component provides the repeat GARD functionality for all "gardable" items (memory and processors) that are deconfigured and then marked "garded out" either at IPL or runtime. GARD also provides system configuration information to the menu system about system configuration.

(B1xx) Service processor firmware reference code callouts

A B1xx reference code indicates that an error occurred in a service processor firmware-detected operation. To resolve any B1xx reference code, use the following procedure: 1. Does the reference code have a format of B151 72xx or B181 72xx that displays during the power-on process after power was connected to the server but before the server reaches the Power On Standby state? ♦ Yes: See the description in Table 1. (B1xx) Service processor early termination reference codes. Perform Failing Item FSPSP02. ♦ No: Continue with the next step. 2. Perform the following: a. Using the callout list provided with the error replace the first or next FRU or perform the first or next isolation procedure in the list starting with the highest priority. For more information, see the following: ◊ Finding part locations for links to removal and replacement information ◊ Service processor isolation procedures for links to service processor isolation procedures ◊ (B1xx) Service processor firmware reference code descriptions for a description of the SRC b. Perform a slow-boot IPL. Did the same error code appear? ♦ No: Go to Verifying the repair. This ends the procedure. ♦ Yes: Continue with the next step. 3. Is the new error code the same as the one that brought you to this procedure? ♦ Yes: Replace the next FRU or perform the next procedure in the list. ♦ No: Go to the Start of call procedure to service this new error code. This ends the procedure.

(1xxx) System power control network (SPCN) reference codes

209

Reference codes

Table 1. (B1xx) Service processor early termination reference codes Reference Description Code B1517200 Invalid boot request B1517201 Service processor failure The permanent and temporary firmware sides B1517202 are both marked invalid B1517203 Error setting boot parameters B1517204 Error reading boot parameters B1517205 Boot code error B1517206 Unit check timer was reset Power-off reset occurred. FipsDump should be B151720A analyzed: Possible hardware problem B1817200 Invalid boot request B1817201 Service processor failure The permanent and temporary firmware sides B1817202 are both marked invalid B1817203 Error setting boot parameters B1817204 Error reading boot parameters B1817205 Boot code error B1817206 Unit check timer was reset B1817207 Error reading from NVRAM B1817208 Error writing to NVRAM The service processor boot watchdog timer expired and forced the service processor to B1817209 attempt a boot from the other firmware image in the service processor flash memory Power-off reset occurred. FipsDump should be B181720A analyzed: Possible software problem Action FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02 FSPSP02

(B3xx) Connection monitoring reference codes

These error codes indicate a problem in the connection monitoring between the Hardware Management Console and a partition that is running on the managed system. The HMC posts these error codes into the error log in Service Focal Point but does not report them to the operating systems running on the managed system. Use the following links to display the appropriate B3xx reference code table: • B301 • B302 • B303 • B31x Table 1. (B301) Connection monitoring reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B3010001 Hardware Management Console (HMC) or partition connection monitoring fault B3010002 HMC or partition connection monitoring fault Perform the following steps: 1. Verify the network between the HMC and the partition by pinging in both directions. Correct any problems that you detect. 2. Reboot the HMC. HMC or partition connection monitoring fault NEXTLVL
210 (1xxx) System power control network (SPCN) reference codes

Failing Item NEXTLVL PTNNTWK

Reference codes

B3010012, B3010013, B3010019, B3010020, B3010023, B3010025, B3010026 B3010027

HMC or partition connection monitoring fault Before using the entry in the Failing Items column, do the following:

NEXTLVL

B3010029, B301002B, B301002C, B301002D Table 2. (B302) Connection monitoring reference codes

1. If you use short host names for the HMC and the partitions, ensure that you have correctly set up the short host names. Correct any problems that you find, then verify that you can ping in both directions between the HMC and the partitions. 2. If you do not use short host names or if the previous step does not correct the problem, use the Failing Item column. HMC or partition connection monitoring fault NEXTLVL

Reference Code Description/Action Perform all actions before exchanging Failing Items Hardware Management Console (HMC) or partition connection monitoring fault Before using the entry in the Failing Items column, do the following:

Failing Item

1. If you use short host names for the HMC and the partitions, NEXTLVL ensure that you have correctly set up the short host names. . Correct any problems that you find, then verify that you can ping in both directions between the HMC and the partitions. 2. If you do not use short host names or if the previous step does not correct the problem, use the Failing Item column. Table 3. (B303) Connection monitoring reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items B3030001 The communication link between the service processor and the Hardware Management Console (HMC) failed B3030002 A single partition HMC link failed B3030003 B3030004 B3030005 B3030006 B3030007 B3030008 B3030009 Multiple partition HMC links failed All partition links for a single system to HMC failed All system links from one system to a single HMC failed The links between a single HMC and a single managed system failed A single HMC link to more than one managed system occurred One HMC link to another single HMC failed One HMC link to more than one HMC occurred Failing Item FSPSP33 SPNETWK FSPSP33 SPNETWK PTNNTWK FSPSP33 SPNETWK PTNNTWK FSPSP33 SPNETWK PTNNTWK FSPSP33 SPNETWK FSPSP33 SPNETWK FSPSP33 SPNETWK HMCNTWK FSPSP33 SPNETWK HMCMTWK FSPSP33 SPNETWK HMCNTWK
211

B3020001

(1xxx) System power control network (SPCN) reference codes

Reference codes

B303000A B303000B B303000C B303000D B303000E

The HMC lost links to all managed systems Multiple HMCs lost links to a single managed system Multiple HMCs lost links to multiple managed systems Multiple HMCs lost links to multiple managed systems The Network Interface Card (NIC) failed Use the error codes offered in the HMC Focal Point to diagnose and repair the problem. For more information, see Using Service Focal Point. A single partition HMC link failure occurred on a redundant path A single HMC link to one HMC failure occurred on a redundant path Server firmware connection monitoring to the flexible service processor failed Flexible service processor connection monitoring of server firmware failed The communication path (mailbox) between server firmware and the flexible service processor failed Customer reported a console problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a power problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a processor problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a LAN problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a software problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a input/output (I/O) problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer tested problem reporting by creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a power problem when creating a serviceable event on the HMC user interface.

FSPSP33 SPNETWK FSPSP33 SPNETWK FSPSP33 SPNETWK FSPSP33 SPNETWK HMCNTWK SYSNTWK

B303000F B3030010 B3030011 B3030012 B3030013

FSPSP33 SPNETWK PTNNTWK FSPSP33 SPNETWK FSPSP33 SPNETWK FSPSP33 SPNETWK MAILBOX

B3031000

B3031001

B3031002

B3031003

B3031004

B3031005

B3031006

B3031007

B3031100 B3031101

212

(1xxx) System power control network (SPCN) reference codes

Reference codes

B3031102

Contact the customer for more information about the problem. Customer reported a processor problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a LAN problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a software problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a input/output (I/O) problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer reported a problem when creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. Customer tested problem reporting by creating a serviceable event on the HMC user interface. Contact the customer for more information about the problem. The HMC failed to retrieve a platform system dump from the managed system. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem. After receiving this error, perform the following steps:

B3031103

B3031104

B3031105

B3031106

B3031107

B3036601

1. Use the manage dumps utility to determine if a dump of that type has been received from the managed system. 2. If you have a peer HMC managing the same system, also check that HMC. Managed System Dumps can be retrieved by any HMC connected to the system. If there is a current dump of the type that failed from the managed system reported in the error, than the available dump of that type has been retrieved. The HMC failed to retrieve a dump from the service processor. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem. This might be a temporary problem. After receiving this error, perform the following steps:

B3036602

1. Use the manage dumps utility to determine if a dump of that type has been received from the managed system. 2. If you have a peer HMC managing the same system, also check that HMC. Managed System Dumps can be retrieved by any HMC connected to the system. If there is a current dump of the type that failed from the managed system reported in the error, than the available dump of that type has been retrieved. The HMC failed to retrieve a power subsystem dump from the managed system. If you have a redundant HMC environment, a peer HMC might have retrieved the dump. This might be a temporary problem. After receiving this error, perform the following steps:

B3036604

1. Use the manage dumps utility to determine if a dump of that type has been received from the managed system. 2. If you have a peer HMC managing the same system, also check that HMC. Managed System Dumps can be retrieved by any HMC connected to the system. If there is a current dump of the type that failed from the managed system reported in the error, than the available dump of that type has been retrieved.
213

(1xxx) System power control network (SPCN) reference codes

Reference codes

Table 4. (B31x) Connection monitoring reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items Ethernet network failure Do the following: B3100500, B3112420 1. Reseat your Ethernet card. 2. Check your Ethernet cable connections. 3. If the previous actions do not resolve the problem, contact your next level of support. NEXTLVL Failing Item

(BAxx) Partition firmware reference (error) codes

The partition firmware detected a failure. The first eight characters in the display represent the SRC. Any additional characters represent the associated location code. Record the location code as well as the reference code, then find the SRC in the following table. Table 1. (BAxx) Partition firmware reference (error) codes Reference Code Description/Action Perform all actions before exchanging Failing Items BA000010 The device data structure is corrupted BA000020 Incompatible firmware levels were found BA000030 BA000032 BA000034 BA000038 BA000040 BA000050 BA000060 BA000070 BA000080 BA000081 BA000082 BA010000 BA010001 BA010002 Reflash the platform firmware. An lpevent communication failure occurred The firmware failed to register the lpevent queues The firmware failed to exchange capacity and allocate lpevents The firmware failed to exchange virtual continuation events The firmware was unable to obtain the RTAS code lid details The firmware was unable to load the RTAS code lid The firmware was unable to obtain the open firmware code lid details The firmware was unable to load the open firmware code lid The user did not accept the license agreement There is no further action required. If the user did not accept the license agreement, the system will not function. Failed to get the firmware license policy Failed to set the firmware license policy There is insufficient information to boot the partition The client IP address is already in use by another network device Cannot get gateway IP address Failing Item FWFLASH

FWFLASH FWFLASH FWFLASH FWFLASH FWFLASH FWFLASH FWFLASH FWFLASH

FWFLASH FWFLASH FWIPIPL FWIPIPL FWHOST

BA010003

If the system is a model ESCALA PL 245T/R, refer to partition firmware progress code E174. For all other systems, refer to partition firmware progress code CA00E174. Cannot get server hardware address FWHOST If the system is a model ESCALA PL 245T/R, refer to partition firmware progress code E174. For all other systems, refer to partition firmware progress code CA00E174. Bootp failed File transmission (TFTP) failed FWHOST FWADIPL Refer to partition firmware progress code CA00E174 The boot image is too large FWADIPL Partition firmware password entry error

BA010004 BA010005 BA010006 BA020001

214

(1xxx) System power control network (SPCN) reference codes

Reference codes

BA020009

Reenter the password. Invalid password entered - system locked A password was entered incorrectly three times. Deactivate the partition using the HMC, then reactivate it. When asked for the password, enter the correct password. RTAS attempt to allocate memory failed FWFWPBL Self test failed on device; no error or location code information available NEXTLVL If there was a location code reported with the error, replace the device specified by the location code. Self test failed on device; cannot locate package NEXTLVL The machine type and model are not recognized by the server firmware NEXTLVL Check for server firmware updates, and apply them, if available. The firmware was not able to build the UID properly for this system. As a result, problems may occur with the licensing of the AIX operating system. 1. Using the Advanced System Management Interface (ASMI) menus, ensure that the machine type, model, and serial number in the VPD for this system are correct. 2. If this is a new system, check for server firmware updates and apply them, if available. The firmware was unable to find the "plant of manufacture" in the VPD. This may cause problems with the licensing of the AIX operating system. Verify the that machine type, model, and serial number are correct for this system. If this is a new system, check for server firmware updates and apply them, if available. Setting the machine type, model, and serial number failed. The h-call to switch off the boot watchdog timer failed. Setting the firmware boot side for the next boot failed. Rebooting a partition in logical partition mode failed. Locating a service processor device tree node failed. Failed to send boot failed message to the service processor IP parameter requires 3 period (.) characters Enter a valid IP parameter. Example: 000.000.000.000 Invalid IP parameter Enter a valid IP parameter. Example: 000.000.000.000 Invalid IP parameter (>255) Enter a valid IP parameter. Example: 000.000.000.000 A keyboard was not found 1. Make sure that a keyboard is attached to the USB port that is assigned to the partition. 2. Replace the USB card to which the keyboard is attached. No configurable adapters found by the remote IPL menu in the System FWRIPL Management Services (SMS) utilities This error occurs when the remote IPL menu in the SMS utilities cannot locate any LAN adapters that are supported by the remote IPL function. The system was not able to find an operating system on the devices in the boot list.

BA030011 BA04000F

BA040010 BA040020

BA040030

BA040035

BA040040 BA040050 BA040060 BA050001 BA050004 BA05000A BA060003 BA060004 BA060005 BA060007

FWFWPBL FWFWPBL FWFWPBL FWFWPBL FWFWPBL FWFWPBL

BA060008

BA06000B BA06000C BA060020 See Problems with loading and starting the operating system (AIX and Linux) A pointer to the operating system was found in non-volatile storage. FWPTR FWNIM
215

(1xxx) System power control network (SPCN) reference codes

Ensure that the alpha-mode operating system image is intended for this partition. 2. the media might not be readable. Install or boot a level of the operating system that supports shared processors. Do one of the following: • Install a newer version of the operating system that supports huge pages. but dynamic partitioning of huge pages is not supported. The media has been changed Retry the operation. An IDE command timed out. but the operating system failed to make the transition to MGC mode. Use the ASMI to disable dynamic partitioning of huge pages. Retry the operation. SCSI controller failure An IDE device remained busy for a longer period than the time out period The IDE controller senses IDE devices but with errors. but the operating system image does not support huge pages. • Verify that the IDE devices are properly seated and cabled correctly • Replace the IDE controller (model-dependent) An IDE device is busy longer than specified time-out period.Reference codes BA060021 BA060022 The boot-device environment variable exceeded the allowed character limit. • Use the ASMI to remove the huge pages. 2. Retry the operation. Ensure that the configuration of the partition supports a nonalpha-mode operating system. Disable logical partitioning with shared processors in the operating system. 2. but the operating system failed to make the transition to alpha mode. Ensure that the nonalpha-mode operating system image is intended for this partition. FWIDE2 FWIDE1 FWIDE1 FWIDE1 BA080012 BA080013 BA080014 BA080015 216 (1xxx) System power control network (SPCN) reference codes . The operating system expects an IOSP partition. Ensure that the configuration of the partition supports an alpha-mode operating system. command is exceeding the period allowed FWIDE1 to complete. 1. The boot-device environment variable contained more than five entries. BA060030 BA060040 BA060050 BA060060 1. The operating system expects a non-IOSP partition. BA060061 BA07xxxx BA080001 FWSCSI1 FWFWPBL BA080002 BA080010 BA080011 FWIDE1 Retry the operation. The system or partition is configured to use huge pages. 1. FWNIM The boot-device environment variable contained an entry that exceeded FWNIM 255 characters in length Logical partitioning with shared processors is enabled and the operating system does not support it. The packet command failed. The ATA command failed The media is not present in the tray Retry the operation. The Hypervisor supports dynamic partitioning of the huge page-type of memory allocation.

send diagnostic failed. Reject the firmware image on the temporary side. sense data available On an undetermined SCSI device. then retry the operation. hardware error SCSI changer: test unit ready failed. Retry the operation. sense data available SCSI tape: send diagnostic failed. Plug in the USB keyboard and reboot the partition. USB CD-ROM: execution of ATA/ATAPI command failed. USB CD-ROM: the media in the USB CD-ROM drive has been changed. sense data available SCSI tape: send diagnostic failed: devofl command SCSI changer: test unit ready failed. This checkpoint might remain in the control panel for up to 15 minutes If the checkpoint persists longer than 15 minutes. send diagnostic failed. Power off the server and reboot from the permanent side. test unit ready failed. sense data available On an undetermined SCSI device. before replacing any components. Verify that the power and signal cables going to the USB CD-ROM are properly connected and are not damaged. sense data available SCSI CD-ROM: send diagnostic failed. the CD in the USB CD-ROM drive might not be readable. If any problems are found. Retry the operation. Check for system firmware updates and apply them. correct them. test unit ready failed. sense data available SCSI disk unit: send diagnostic failed. 2. USB CD-ROM: ATA/ATAPI packet command execution failed. hardware error SCSI tape: test unit ready failed. If the problem persists. hardware error On an undetermined SCSI device. refer to the actions for BA090001. BA130014 FWCD2 BA130015 FWCD2 BA131010 1. USB CD-ROM: execution of ATA/ATAPI command was not completed within the allowed time. The USB keyboard was removed. 217 (1xxx) System power control network (SPCN) reference codes . 2. devofl command SCSI CD-ROM: test unit ready failed. sense data available SCSI disk unit: send diagnostic failed: devofl command SCSI tape: test unit ready failed. Remove the CD and insert another CD. sense data available SCSI changer: send diagnostic failed: devofl command On an undetermined SCSI device. USB CD-ROM: bootable media is missing from the drive FWCD1 Insert a bootable CD-ROM in the USB CD-ROM drive. sense data available SCSI changer: send diagnostic failed. do the following: 1. hardware error SCSI disk unit: test unit ready failed. BA090001 BA090002 BA090003 BA090004 BA100001 BA100002 BA100003 BA100004 BA110001 BA110002 BA110003 BA110004 BA120001 BA120002 BA120003 BA120004 BA130001 BA130002 BA130003 BA130004 BA130010 BA130011 FWSCSI1 FWSCSI2 FWSCSI3 FWSCSI3 FWSCSI1 FWSCSI4 FWSCSI3 FWSCSI3 FWSCSI1 FWSCSI4 FWSCSI3 FWSCSI3 FWSCSI5 FWSCSI4 FWSCSI4 FWSCSI4 FWSCSI1 FWSCSI3 FWSCSI3 FWSCSI3 FWFWPBL FWCD1 BA130012 NEXTLVL BA130013 1. Remove the CD and insert another CD. hardware error SCSI CD-ROM: test unit ready failed. If the problem persists. if available. 2. sense data available SCSI CD-ROM: send diagnostic failed: devofl command USB CD-ROM: device remained busy longer than the time-out period Retry the operation. If the problem persists. SCSI disk unit: test unit ready failed.Reference codes BA09xxxx SCSI controller failure. then retry the operation. the CD in the USB CD-ROM drive might not be readable.

Replace the adapter specified by the location code. FWNVR3 NEXTLVL BA180008 218 FWPCI1 (1xxx) System power control network (SPCN) reference codes . There is no user action or FRU replacement for this error. Remove other cards from the PHB in which the gigabit Ethernet adapter is plugged and retry the operation. FWSCSI1 FWSCSI1 FWSCSI3 FWSCSI3 BA151001 BA151002 BA153002 FWENET BA153003 BA160001 BA161001 BA170xxx BA170000 BA170100 BA170201 BA170202 BA170203 BA170210 BA170211 FWNVR1 FWNVR2 FWNVR2 FWNVR1 FWNVR1 FWNVR1 FWNVR1 FWNVR1 BA170220 BA170221 BA170998 BA170999 You might need to use the SMS menus to reenter the parameters for network installation or boot. Do the following: 1. 10/100 MBPS Ethernet PCI adapter: internal wrap test failure Replace the adapter specified by the location code. If the operation is successful. NVRAMRC script evaluation error . The setenv/$setenv function had to delete network boot information to free space in NVRAM. Check for adapter firmware updates. 3. devofl command PCI Ethernet BNC/RJ-45 or PCI Ethernet AUI/RJ-45 adapter: internal wrap test failure Replace the adapter specified by the location code. so that each of the remaining partitions has more NVRMA allocated to it. if possible. Reduce the number of partitions. NVRAMRC script evaluation error .value contains a null character The firmware was not able to write a variable value into NVRAM because not enough space exists in NVRAM. PCI device Fcode evaluation error. 2. hardware error SCSI read/write optical: test unit ready failed. PCI token ring adapter: failed to complete hardware initialization.command line execution error. apply if available. one at a time. 2.writing error log entry The firmware was unable to expand target partition . device test failed NVRAM data validation check failed Turn off. until the failing card is isolated. Gigabit Ethernet adapter failure 1. sense data available SCSI read/write optical: send diagnostic failed. NVRAM problems NVRAMRC initialization failed. The firmware was unable to expand target partition . Replace the adapter. sense data available SCSI read/write optical: send diagnostic failed. Replace the adapter specified by the location code. plug the cards in again. 10/100 MBPS Ethernet card Gigabit Ethernet adapter failure Verify that the MAC address programmed in the FLASH/EEPROM is correct. then turn on the system.Reference codes BA140001 BA140002 BA140003 BA140004 BA150001 SCSI read/write optical: test unit ready failed.name contains a null character Setenv/$Setenv parameter error .saving configuration variable The firmware was unable to expand target partition .writing VPD data Setenv/$Setenv parameter error . After you identify the failing card. replace it.stack unbalanced on completion. Contact your next level of support. PCI auto LANstreamer token ring adapter: failed to complete hardware initialization. This is a firmware debug environment error.

Note: If the logical memory block size is already 256 MB. 1. Check for server firmware updates and apply them. Service support might have additional information. FWFLASH FWFWPBL FWFWPBL FWFWPBL FWFWPBL FWFWPBL FWFWPBL FWFWPBL FWFWPBL FWFWPBL FWPCI1 FWPCI2 FWPCI3 FWPCI3 FWFLASH BA180101 BA188000 FWFWPBL BA188001 BA188002 BA190001 BA191001 BA201001 BA201002 BA201003 BA210000 BA210001 BA210002 BA210010 BA210020 BA210100 BA210101 BA250010 BA250020 BA250030 BA250040 (1xxx) System power control network (SPCN) reference codes 219 . bridge in freeze state A PCI adapter was found that this machine type and model does not support. Remove the PCI adapter specified by the location code. if available. bridge is not usable PCI device runtime error. EEH could not recover the failed I/O adapter Replace the adapter in the slot identified by the location code. Increase the logical memory block size to 256 megabytes (MB) and reboot the managed system. Check for operating system updates that resolve problems with dynamic logical partitioning (dlpar) and apply them. PCI probe error. no location code will be reported.Reference codes The Fcode on a PCI adapter left a data stack imbalance BA180009 BA180010 BA180011 BA180012 BA180013 BA180014 BA180100 You should load the new adapter Fcode before you use the adapter (specified by the location code associated with this error) for booting. The partition firmware was unable to log an error with the server firmware. No reply was received from the server firmware to an error log NEXTLVL that was sent previously The partition firmware error log queue is full NEXTLVL dlpar error in open firmware FWLPAR dlpar error in open firmware due to an invalid dlpar entity. 2. if available. Retry the hotplug operation after the concurrent firmware update is complete. Firmware function to get/set time-of-day reported an error The server firmware function to turn on the speaker reported an error The serial interface dropped data packets The serial interface failed to open The firmware failed to handshake properly with the serial interface Partition firmware reports a default catch Partition firmware reports a stack underflow was caught Partition firmware was ready before standout was ready The transfer of control to the SLIC loader failed The I/O configuration exceeds the maximum size allowed by partition firmware. The firmware was unable to generate a device tree node After you perform the FRU indicated in the Failing Items column. bridge in freeze state PCI bridge probe error. Since it is informational. if available. A hotplug operation in dynamic logical partitioning (dlpar) was terminated for concurrent firmware update. EEH recovered a failing I/O adapter This is an informational code only. check for operating system updates and apply them. contact your next level of support. Stack underflow from fibre-channel adapter An unsupported adapter was found in a PCI slot Remove the unsupported adapter in the slot identified by the location code. This error may have been caused by an errant or hung operating system process. and no action is required. MSI software error FDDI adapter Fcode driver is not supported on this system. This server does not support the Fcode driver of this adapter.

or edit the profile to have fewer logical 220 (1xxx) System power control network (SPCN) reference codes . Unable to unlock the firmware update lid manager Reboot the system. Reduce the total logical memory block limit in the partition profile. Note: The maximum number of logical memory blocks per partition is 128 kilobytes (K) under the new memory allocation scheme. Reboot the system. BA278004 BA278005 BA278006 BA278007 BA278008 BA278009 BA280000 BA290000 Go to the support site for your distribution and download the latest service aids and productivity tools for the version of Linux that you are running. Upgrade the firmware of the managed system to the latest level. Upgrade the firmware of the managed system to the latest level. Upgrade the operating system to a level that supports the new memory representation. Make sure that the operating system is authorized to update the firmware. Failed to flash a firmware update lid Obtain a valid firmware update (flash) image for this system. 2. Do the following: BA300010 BA300020 BA300030 1. verify that this partition has service authority. 2. Unable to lock the firmware update lid manager 1. Failed to reboot the system after a firmware flash update Reboot the system. Reboot the partition.Reference codes BA278001 BA278002 BA278003 Failed to flash firmware: invalid image file Obtain a valid firmware update (flash) image for this system. if a newer level is available. An invalid firmware update lid was requested Obtain a valid firmware update (flash) image for this system. 3. Upgrade the operating system to a level that supports the new memory representation. You must perform the update by using the Hardware Management Console (HMC). The server firmware update management tools for the version of Linux that you are running are incompatible with this system. Perform the server firmware update by using the HMC. or edit the profile to have fewer logical memory blocks than the 8K maximum. then reactivate the partition. RTAS discovered an invalid operation that may cause a hardware error NEXTLVL RTAS discovered an internal stack overflow FWFWPBL The partition exceeded the maximum number of logical memory blocks allowed under the new memory allocation scheme. Function call to make a logical memory block unusable failed under the standard memory allocation scheme. Function call to isolate a logical memory block failed under the standard memory allocation scheme. if a newer level is available. A server firmware update was attempted from the operating system. Do the following: 1. 2. If the system is running multiple partitions. Flash file is not designed for this platform Obtain a valid firmware update (flash) image for this system.

(BF67) Linux reference codes The Linux operating system detected a failure in the emulex driver. If no ELS command is going through the adapter. Record the location code as well as the reference code. 2. The firmware could not obtain the SRC history The firmware received an invalid SRC history The firmware operation to write the MAC address to vital product data (VPD) failed BA310010 BA310020 BA310030 FWFLASH FWFLASH FWFLASH (BBxx) High performance switch reference codes The high performance switch detected a failure. and Service for POWER5 technology based servers manual. This message indicates one of the following conditions: 7802 • A possible lack of memory resources. Upgrade the operating system to one that supports the new memory representation. then perform the suggested actions. Table 1. Try increasing the lpfc num_bufs configuration parameter to allocate more buffers • A possible driver buffer management problem (1xxx) System power control network (SPCN) reference codes 221 Reference Code 7800 Failing Item NEXTLVL NEXTLVL NEXTLVL . or edit the profile to have fewer than 8192 logical memory blocks. BA300040 Do the following: 1. Reboot the partition. (BF67) Linux reference codes Description/Action Perform all actions before exchanging Failing Items An ELS IOCB command was posted to a ring and did not complete within ULP timeout seconds.Reference codes memory blocks than the 8K maximum. For example: Use the following table to locate the last four characters of the (BF67) Linux SRC that you want to find. Installation. exceeded the limit of 8192 logical memory blocks allowed by the standard memory allocation scheme. Try increasing the lpfc num_bufs configuration parameter to allocate more buffers • A possible driver buffer management problem The driver attempted to issue REG_LOGIN mailbox command to the HBA but there were no buffer available. This message indicates one of the following conditions: 7801 • A possible lack of memory resources. The partition. then find the SRC in the 45H/W4 Switch Planning. The first five characters (BFxxx) of these SRCs indicate the driver or subsystem responsible for the error. which is running the traditional memory representation. Note: If the suggested action in the Description/Action column does not work (or if that column does not contain a suggested action). Reboot the partition. and the last three characters specifies the error condition. use the action specified in the Failing Item column. reboot the system. The driver attempted to issue READ_SPARAM mailbox command to the HBA but there were no buffer available. 3. The last three characters of the SRCs are arranged such that 1xx is lowest severity and Fxx is highest severity.

7A02 This error might indicate a firmware or hardware problem. 7807 This error might indicate a software driver. Received an unknown IOCB command completion. firmware or hardware problem. The driver manages its own memory for internal usage. The driver issued a READ_SPARAM mbox command to the HBA that failed. This error indicates a problem occurred in the driver memory management routines. This error might indicate a software driver or firmware problem. Software driver error. The Rctl/Type of a received frame did not match any for the configured masks for the specified ring. The configuration parameter for scan-down is out of range. The driver wan unable to find a matching command for the completion received on the specified ring. Input byte count greater than the max <num> NEXTLVL • ASCII string to hex conversion failed. NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL 7803 NEXTLVL 7804 NEXTLVL 7806 NEXTLVL 7808 NEXTLVL 7809 NEXTLVL 780A NEXTLVL 780B 7A03 222 NEXTLVL (1xxx) System power control network (SPCN) reference codes .Reference codes This message indicates one of the following conditions: • Port rsp ring put index is greater than the size of rsp ring • Port cmd ring get index is greater than the size of cmd ring • Port cmd ring get index is greater than the size of cmd ring • The assigned I/O iotag is greater than the max allowed • The assigned I/O iotag is greater than the max allowed This error might indicate a software driver. This message indicates one of the following conditions: • ASCII string to hex conversion failed. Received a mailbox completion interrupt and there are no outstanding mailbox commands. The driver decided to drop an ELS Response ring entry. This error might indicate a driver or host operating system problem. This error might also indicate the host system in low on memory resources. The driver issued a CONFIG_LINK mbox command to the HBA that failed. Update firmware. Input byte count less than 1 • ASCII string to hex conversion failed. Every two input chars (bytes) require one output byte This error might indicate a software driver problem. This error might indicate a software driver or firmware problem. firmware or hardware problem. 7A00 This error might indicate a software driver or firmware problem. The output buffer byte size is less than one-half of the input byte count. Update firmware or replace adapter. A unknown mailbox command completed. 7805 This error might indicate a software driver or firmware problem. This error might indicate a hardware or driver problem. The driver attempted to register the HBA interrupt service routine with the host operating system but failed. 7A01 This error might indicate a hardware or firmware problem.

Adapter initialization failed when issuing READ_CONFIG mailbox command. 7A11 This error might indicate a hardware or firmware problem. Adapter initialization failed when issuing READ_SPARM mailbox command. The adapter failed during power-up diagnostics after it was reset. The driver issued a CLEAR_LA mbox command to the HBA that failed. The driver received an interrupt indicting a possible hardware problem. This error might indicate a hardware or firmware problem. Adapter initialization failed when issuing CFG_RING mailbox command. This error might indicate a hardware or firmware problem. Adapter initialization failed when issuing READ_REV mailbox command. 7A05 This error might indicate a hardware or firmware problem. 7A04 This error might indicate a firmware or hardware problem. 7A08 This error might indicate a hardware or firmware problem. Adapter initialization failed when issuing CONFIG_PORT mailbox command. Outdated firmware was detected during initialization. 7A07 This error might indicate a hardware or firmware problem. NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL 7A09 NEXTLVL 7A0B NEXTLVL 7A0C NEXTLVL 7A0E NEXTLVL 7A0F NEXTLVL 7A10 NEXTLVL (BF75) Linux reference codes The Linux operating system detected a failure in the ipr driver. Adapter initialization failed when issuing INIT_LINK mailbox command. 7A06 This error might indicate a software driver or firmware problem. 7A12 This error might indicate a hardware or firmware problem. This error might indicate a hardware or firmware problem. The driver cannot find the specified buffer in its mapping table. A read nvparams mailbox command failed during config port. This error might indicate a hardware or firmware problem. 7A0D This error might indicate a hardware or firmware problem. Adapter initialization failed when issuing CONFIG_LINK mailbox command.Reference codes This error might indicate a firmware or hardware problem. This error might indicate a hardware or firmware problem. The adapter failed during power-up diagnostics after it was reset. The first five characters (BFxxx) of these SRCs indicate the driver or subsystem responsible for the error. Update firmware. This error might indicate a hardware or firmware problem. For example: (1xxx) System power control network (SPCN) reference codes 223 . 7A0A This error might indicate a hardware or firmware problem. Adapter initialization failed when issuing DUMP_VPD mailbox command. and the last three characters specifies the error condition. The last three characters of the SRCs are arranged such that 1xx is lowest severity and Fxx is highest severity.

(BF75) Linux reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items 8155: An unknown error was received. 1D00 7001: IOA sector reassignment successful. Microcode buffer allocation failed. 1A04 Have the customer update the adapter microcode. 8151: IOA microcode error. 1A06 Have the customer update the adapter microcode and the device driver. 1C00 Have the customer update the adapter microcode. Failed to map microcode download buffer. then perform the suggested actions. 1A01 Have the customer update the adapter microcode. protection resuming. message or command phase. May occur normally during concurrent maintenance. Microcode download required. 1A00 Have the customer update the adapter microcode. Invalid microcode buffer.Reference codes • Errors that require you to check cables occur in the 5xx range • Errors that require you to perform a microcode update occur in the Axx range • Errors that require you to replace an adapter occur in the Fxx range Use the following table to locate the last four characters of the (BF75) Linux SRC that you want to find. Adapter being reset due to command timeout. 1D04 Device error. Device bus error. Table 1. 1800 Have the customer update the device driver. 9031: Array protection temporarily suspended. 1A05 Have the customer update the adapter microcode. 1A03 Have the customer update the adapter microcode. 1D02 Device hardware error. Note: If the suggested action in the Description/Action column does not work (or if that column does not contain a suggested action). 1D05 Out of alternate sectors for disk storage. 1D03 Predictive failure analysis. Microcode buffer copy to DMA buffer failed. 1C01 Have the customer update the device driver. 1A02 Have the customer update the adapter microcode. This message indicates one of the following conditions: 1D07 • Array protection temporarily suspended • IOA detected device error • Cache data belongs to devices other than those attached • Maximum number of arrays already exist • Incorrect hardware configuration change has been detected IOA detected a SCSI bus configuration error. use the action specified in the Failing Item column. Failing Item NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL IOADPTR IOADPTR IO_DEV IO_DEV IO_DEV IO_DEV IO_DEV IO_DEV NEXTLVL NEXTLVL 1D08 NEXTLVL 224 (1xxx) System power control network (SPCN) reference codes . 1D01 Unsolicited device bus message received. Media error. 1D06 Hardware configuration error. Invalid resource address. Firmware file %s not found.

(BF77 5xxx) Linux reference codes (pcnet32 driver) • Table 3. (BF77 0xxx) Linux reference codes (olympic driver) Reference Code Description/Action Perform all actions before exchanging Failing Items (1xxx) System power control network (SPCN) reference codes Failing Item 225 . Failed to save PCI configuration space. Table 1. Array is missing a device and parity is out of sync. A permanent cache battery pack failure occurred. then perform the suggested actions: • Table 1. (BF77 7xxx) Linux reference codes (e100 driver) • Table 5. NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL IOADPTR IOADPTR IOADPTR IOADPTR IOADPTR IOADPTR IOADPTR IOADPTR IOADPTR IOADPTR IOADPTR (BF77) Linux reference codes The Linux operating system detected a failure in a driver or subsystem. Invalid response handle from IOA. (BF77 0xxx) Linux reference codes (olympic driver) • Table 2. IOA resources not available due to previous problems. IOA unit check with no data. PCI bus error. Failed to set PCI DMA mask. The last three characters of the SRCs are arranged such that 1xx is lowest severity and Fxx is highest severity. Cache data associated with attached devices cannot be found. Adapter not supported in this hardware configuration. (BF77 6xxx) Linux reference codes (bcm 5700 driver) • Table 4. Disk unit requires initialization before use. use the action specified in the Failing Item column. Required cache data cannot be located for a disk unit. Incorrect hardware configuration change has been detected.Reference codes 1D09 1D0A 1D0B 1D0C 1D0D 1D0E 1D0F 1D10 1D11 1D12 1F00 1F01 1F02 1F03 1F04 1F05 1F06 1F07 1F08 1F08 1F09 IOA cache data exists for a missing or failed device. One or more array members not at required physical locations. Adapter hardware error.error recovery failed. Disk unit has been modified after the last known status. IOA taken offline . The first five characters (BFyyy) of these SRCs indicate the driver or subsystem responsible for the error: • BF77 0xxx specifies the olympic driver • BF77 5xxx specifies the pcnet32 driver • BF77 6xxx specifies the bcm 5700 driver • BF77 7xxx specifies the e100 driver • BF77 8xxx specifies the e1000 driver The last three characters specify the error condition. Write of cache line size failed. (BF77 8xxx) Linux reference codes (e1000 driver) Note: If the suggested action in the Description/Action column in any of the following tables does not work (or if that column does not contain a suggested action). For example: • Errors that require you to check cables occur in the 5xx range • Errors that require you to perform a microcode update occur in the Axx range • Errors that require you to replace an adapter occur in the Fxx range Use the following table to locate the last four characters of the (BF77) Linux SRC that you want to find. Array missing two or more devices with only one device present. Remove the unsupported adapter from the system. Permanent IOA failure. Soft PCI bus error.

0F05 Have the customer reset the adapter The specified interrupt has occurred. For excessive IOADPTR occurrences. The customer may need to increase system memory. Reload the driver and reset the device to recover lost buffers 2. NEXTLVL NEXTLVL (1xxx) System power control network (SPCN) reference codes . resetting. IOADPTR Have the customer reload the driver A short circuit has been detected. Unrecognized srb command or cannot set mac/laa address while card is open. The driver was unable to send a received packet to the upper layer protocols because there is insufficient free memory. 0F06 For occasional occurances. if necessary • Check and replace peer stations on ring. (BF77 5xxx) Linux reference codes (pcnet32 driver) Reference Code Description/Action Perform all actions before exchanging Failing Items The driver was unable to use 32-bit DMA. perform the action specified in the Failing Item column. If resetting the adapter does not work. no action is required. Have the customer do the following: 0A00 1. The specified hardware.Reference codes Unrecognized command code or unrecognized buffer address. Upgrade the driver The olympic driver was unable to initialize the token ring card. The adapter open request failed with the specified error code. but was not expected by the driver or a timeout occurred during device close processing. The token ring adapter was unable to join the ring. 0F03 0F04 0800 Have the customer use the network configuration tool supplied by the distributor to specify a ring speed (instead of automatically detecting ring speed). 0F0B Have the customer upgrade the driver Table 2. The Cardbus token ring adapter did not respond to initialization commands. Have the customer do the following: 0F08 • Check and replace cables. Have the customer do the following: 5801 5802 226 NEXTLVL IOADPTR 0F02 IOADPTR IOADPTR IOADPTR LPARCFG IOADPTR 0F07 IOADPTR 0F09 IOADPTR IOADPTR IOADPTR Failing Item NEXTLVL 1. if necessary An internal hardware error has been detected in the specified adapter during auto removal processing. PCI or parity error has occurred. Ensure that Cardbus adapter is properly inserted. 0F01 Corrective action may be possible depending upon the error code. Memory allocation failed. Verify the driver software level 2. Increase the memory on the system Transmit timed out. Have the customer reload the driver An FDX protocol error has been detected. 5800 Have the customer verify the driver software level. have the customer reset the adapter. 0F0A Have the customer reload the driver Invalid return code in asb.

5804 5F00 5F01 5F02 Have the customer verify the driver software level. The IO addresses for the card are already allocated. Have the customer do the following: 6501 • Increase the memory on the system • Install the driver earlier in system bringup The driver was unable to use either 64-bit or 32-bit DMA. Verify the driver software level 2. Table 3. Verify the driver software level (1xxx) System power control network (SPCN) reference codes 227 NEXTLVL NEXTLVL Have the customer verify the driver software level. Have the customer do the following: 1. Have the customer do the following: 6506 1. 5F03 Have the customer verify the driver software level.Reference codes Have the customer verify the driver software level. A FIFO error has occurred. Reduce the rx_jumbo_desc_cnt parameter of the driver Conflicting rx_coalesce_ticks (0) and rx_max_coalesce_frames (0) parameters. (BF77 6xxx) Linux reference codes (bcm 5700 driver) Reference Code Description/Action Perform all actions before exchanging Failing Items Unable to find or create the directory under /proc/net. 6502 Have the customer verify driver software level. 5803 Have the customer verify the driver software level. The driver could not enable the PCI device. Reduce the rx_std_desc_cnt parameter of the driver 3. IOADPTR IOADPTR IOADPTR IOADPTR Failing Item NEXTLVL NEXTLVL NEXTLVL NEXTLVL NEXTLVL 6505 NEXTLVL NEXTLVL NEXTLVL 6800 6801 NEXTLVL NEXTLVL . Memory allocation failed . The chip can not be accessed in 32-bit or 16-bit mode. 6507 Have the customer change the stats_coalesce_ticks parameter of the driver. The hardware did not request any IO resources. Change the nic_tx_bd parameter This adapter does not support hardware checksum offload. Have the customer do the following: 6504 1.buffer parameters may be set too high. Change the tx_coalesce_ticks parameter of the driver 2. Either this adapter or the system does not allow the use of adapter based transmit descriptors. The transmit pointers are out of synchronization. Insufficient kernel memory available for allocation. 6500 Have the customer verify that procfs is supported by the kernel. Linux does not support a hardware feature which has been enabled. Have the customer do the following: 1. 6503 Run diagnostics to disable Turbo Teaming. Have the customer do the following: 1. Reduce the tx_pkt_desc_cnt parameter of the driver 2. Change the rx_coalesce_ticks parameter of the driver 2. Change the rx_max_coalesce_frames parameter of the driver Conflicting tx_coalesce_ticks (0) and tx_max_coalesce_frames (0) parameters. Change the tx_max_coalesce_frames parameter of the driver The value given to the stats_coalesce_ticks parameter is invalid.

or firmware. 6F02 Have the customer verify the driver software level Table 4. Have the customer do the following: 6802 1. Have the customer do the following: 7801 1. Verify the driver software level 2. Run diagnostics The adapter's MAC address is not a valid Ethernet address. 6A00 Have the customer verify the driver software level If you replace the adapter. Have the customer do the following: 1. Run diagnostics Not enough memory for the driver. Have the customer do the following: 7E00 1. Verify the driver software level 2. Install the driver earlier in system bringup Internal error in driver. Unable to initialize (or reinitialize) the adapter card. Install more memory in the system 2. Verify the driver software level 2. Have the customer do the following: 7E02 7E03 1. Run diagnostics 2. Have the customer do the following: 7800 NEXTLVL 1. kernel. Verify the driver software level 2. (BF77 7xxx) Linux reference codes (e100 driver) Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items SRC Probable Causes Actions Internal error in driver. Change the driver's rx_checksum parameter 3. Change the driver's enable_tso parameter This adapter hardware does not support frames sizes over 1500 bytes. then reboot The BIOS has assigned conflicting address spaces to different devices. use one that offers additional capablities Unable to read the adapter's NVRAM. Have the customer do the following: 1. Verify the driver software level. Verify the driver software level 228 (1xxx) System power control network (SPCN) reference codes NEXTLVL IOADPTR IOADPTR IOADPTR IOADPTR NEXTLVL 7802 NEXTLVL IOADPTR 7E01 IOADPTR IOADPTR IOADPTR . Run diagnostics. Insufficient kernel memory is available for the driver. 6F01 Have the customer verify the driver software level Unable to read PCI Config space or NVRAM. Reconfigure the kernel to reduce memory consumption. Have the customer do the following: 1. Reconfigure the kernel to reduce memory consumption 3. or firmware. 2. Upgrade the BIOS The driver requested a DMA configuration that your system does not support. Change the driver's tx_checksum parameter This adapter does not support hardware TSO. 6F00 Have the customer verify the driver software level Cannot get MAC addr from NVRAM.Reference codes 2. kernel.

and you will not receive any indication that the service call was not generated. IOADPTR IOADPTR IOADPTR Table 5. Note: Reference codes based on events detected by the InfiniBand (IB) switches (CBxxxxxxx) do not support the Call Home feature.Reference codes 7F00 7F01 7F02 2. if available. The driver cannot enable the adapter as a PCI device. Unable to access PCI data area for checksum value. Have the customer do the following: 8E01 • Verify the driver software level • Run diagnostics • Replace board The MAC type is not ethernet as expected. However. (BF77 8xxx) Linux reference codes (e1000 driver) Reference Code Description/Action Perform all actions before exchanging Failing Items 8E00 Cannot enable DMA for either 32 bits or 64 bits. The network adapter failed its self-test. Reference Code Description/Event name CB201800 linkDown CB102800 authenticationFailure CB108800 tsCardDown CB109800 tsPowerSupplyDown CB10A000 tsFanDown CB10B800 tsCardRemove CB10C100 tsEvent::ibSmSlaveToMaster(4) CB10C1C0 tsEvent::ibSmNodeDeleted(7) CB10C4C0 tsEvent::ibSmDbSyncNotSupported(19) CB10C500 tsEvent::ibSmDbSyncNotEnabled(20) CB10C540 tsEvent::ibSmDbSyncNoStandby(21) CB10C580 tsEvent::ibSmDbSyncDbVersionMismatch(22) CB10C5C0 tsEvent::ibSmDbSyncColdSyncTimeout(23) CB10C600 tsEvent::ibSmDbSyncSessionTimeout(24) CB10C641 tsEvent::hardwareError(25)::local I2C error::1 CB10C642 tsEvent::hardwareError(25)::remote I2C error::2 CB10C643 tsEvent::hardwareError(25)::card seeprom error::3 CB10C644 tsEvent::hardwareError(25)::DiskOnChipError::4 CB10C645 tsEvent::hardwareError(25)::single bit memory error::5 CB10C646 tsEvent::hardwareError(25)::double bit memory error::6 CB10C647 tsEvent::hardwareError(25)::real-time clock stopped::7 CB10C648 tsEvent::hardwareError(25)::real-time clock sync::8 CB10C649 tsEvent::hardwareError(25)::no fan error::9 CB10C64A tsEvent::hardwareError(25)::FPGA error::10 (1xxx) System power control network (SPCN) reference codes Failing Item IBNSLNK IBNSAUT IBNSREM IBNSPOW IBNSFAN IBNSREM IBNSNLS IBNSNLS IBNSNLS IBNSDBS IBNSNLS IBNSSMU IBNSSMR IBNSDBT IBNSDIG IBNSDGA IBNSDIG IBNSDIG IBNSDIG IBNSDIG IBNSBAT IBNSBAT IBNSFAN IBNSDIG 229 . Failing Item NEXTLVL NEXTLVL 8E02 8F00 IOADPTR IOADPTR (CBxx) Network Manager reference codes The Network Manager detected a failure. Run diagnostics The EEPROM on the network adapter may be corrupted. the device id is valid. it will not successfully generate a service call. then find the Failing item in Guide to Clustering systems using InfiniBand (IB) hardware. Record the reference code and the location code. They will not be called home. If you attempt to use the manual function to initiate Call Home. Have the customer do the following: • Verify the driver software level • Run diagnostics Adapter hardware failure.

assertion::2 tsEvent::softwareInitiatedReboot(27). out-of-memory::3 tsEvent::softwareInitiatedReboot(27). Record the location code as well as the reference code. The first eight characters in the display represent the SRC. no working fan::4 tsEvent::hardwareInitiatedReboot(28).Report this side Network Manager Diagnostics Event . then find the SRC in the following table.Reference codes CB10C64B CB10C64C CB10C64D CB10C64E CB10C64F CB10C650 CB10C651 CB10C652 CB10C653 CB10C654 CB10C655 CB10C656 CB10C657 CB10C658 CB10C659 CB10C65A CB10C65B CB10C65C CB10C65D CB10C65E CB10C65F CB10C660 CB10C661 CB10C662 CB10C663 CB10C664 CB10C665 CB10C666 CB10C667 CB10C6C1 CB10C6C2 CB10C6C3 CB10C6C4 CB10C701 CB20C740 CB20C780 CB20C7C0 CB20C230 CB100001 CB100002 CB100003 CBFF0000 CBFF0001 CBFF0002 CBFF00FF CB10FF00 tsEvent::hardwareError(25)::IB switch ASIC error::11 tsEvent::hardwareError(25)::IB switch firmware error::12 tsEvent::hardwareError(25)::voltage/current error::13 tsEvent::hardwareError(25)::cpu ext bus error::14 tsEvent::hardwareError(25)::cpu bus error::15 tsEvent::hardwareError(25)::fru error::16 tsEvent::hardwareError(25)::local ethernet error::17 tsEvent::hardwareError(25)::management ethernet error::18 tsEvent::hardwareError(25)::cpu error::19 tsEvent::hardwareError(25)::na::20 tsEvent::hardwareError(25)::na::21 tsEvent::hardwareError(25)::na::22 tsEvent::hardwareError(25)::na::23 tsEvent::hardwareError(25)::na::24 tsEvent::hardwareError(25)::na::25 tsEvent::hardwareError(25)::na::26 tsEvent::hardwareError(25)::na::27 tsEvent::hardwareError(25)::na::28 tsEvent::hardwareError(25)::na::29 tsEvent::hardwareError(25)::na::30 tsEvent::hardwareError(25)::na::31 tsEvent::hardwareError(25)::na::32 tsEvent::hardwareError(25)::na::33 tsEvent::hardwareError(25)::na::34 tsEvent::hardwareError(25)::na::35 tsEvent::hardwareError(25)::na::36 tsEvent::hardwareError(25)::na::37 tsEvent::hardwareError(25)::na::38 tsEvent::hardwareError(25)::na::39 tsEvent::softwareInitiatedReboot(27). watchdog::1 tsEvent::ibPmPortMonitorThresholdErrorChange(29) tsEvent::ibPmPortMonitorThresholdUtilChange(30) tsEvent::ibPmConnectionMonitorErrorChange(31) tsEvent::ibPmConnectionMonitorUtilChange(32) tsSensor::(tsSensor::tsDevSensorTemperature=warning)::1 tsSensor::(tsSensor::tsDevSensorTemperature=normal)::2 tsSensor::(tsSensor::tsDevSensorTemperature=critical)::3 Network Manager Diagnostics Event . Any additional characters represent the associated location code. (DAxx) Partition firmware reference (error) codes Reference Code Description/Action Perform all actions before exchanging Failing Items 230 Failing Item (1xxx) System power control network (SPCN) reference codes . Table 1.Report cable Unrecognized Unit Model VPD problem IBNSDIG IBNSDIG IBNSPOW IBNSDIG IBNSDIG IBNSDIG IBNSDIG IBNSDIG IBNSDIG IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWE IBNSSWP IBNSSWP IBNSSWP IBNSFAN IBNSSWP IBNSLNK IBNSLNK IBNSLNK IBNSLNK IBNSTHM IBNSTHM IBNSTHM IBNNMD IBNNMD IBNNMD IBNNURM IBNSVPD (DAxx) Partition firmware reference (error) codes The partition firmware detected a failure.Report other side Network Manager Diagnostics Event . watchdog::1 tsEvent::softwareInitiatedReboot(27).

Retry the operation. • Verify that the IDE devices are seated properly and cabled correctly • Replace the IDE controller (model-dependent) An IDE device is busy longer than specified time-out period. If possible. • E302: The HMC encountered a problem during an update of the firmware for the managed system. The log manager cannot read the expected amount of data from the log file. the media might not be readable. There is no other action required. Retry the operation. This is usually the result of the system syslog being shutdown. • E355: See (E355) errors. (E3xx) Licensed Internal Code error codes The Hardware Management Console (HMC) generates E3xx error codes when it encounters a Licensed Internal Code problem. An IDE command timed out. See (E302) Firmware update error codes. FWIDE2 FWIDE1 FWIDE1 FWIDE1 DA080012 DA080013 DA080014 DA080015 (E2xx) Licensed Internal Code error codes The Hardware Management Console generates E2xx error codes when it encounters a Licensed Internal Code problem.Reference codes DA080001 An IDE device remained busy for a longer period than the time out period The IDE controller senses IDE devices but with errors. command is exceeding the period allowed FWIDE1 to complete. Licensed Internal Code failure on the HMC. and copy the error log to the new log file. The media has been changed Retry the operation. collect the iqyysave. When this occurs. (1xxx) System power control network (SPCN) reference codes 231 . the log manager will copy the current log file to E2FF450F iqyysave. See (E332) Licensed Internal Code error codes. You will need to shut down and restart the HMC. The ATA command failed The media is not present in the tray Retry the operation. FWFWPBL DA080002 DA080010 DA080011 FWIDE1 Retry the operation.log.log file with the error data for reference. The packet command failed. • E303: See (E303) Formatting media error codes. E2xxxxxx NEXTLVL Contact your service provider. • E332: Licensed Internal Code error codes. Table 1. start a new log file. (E2xx) Licensed Internal Code progress codes Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items The system monitor that checks for HMC hardware failures has E2BB1250 shutdown. • E338: An error occurred during the initialization of the components required for performing guided maintenance from Service Focal Point. • E35A: See(E35A) HMC code level. See (E338) Licensed Internal Code error in guided maintenance in Service Focal Point.

Table 1. use the following table. Then repeat the operation. Contact your service provider. The request to get a list of code updates failed because the request timed out. (E3xx) Licensed Internal Code error codes Reference Code Description/Action Perform all actions before exchanging Failing Items E3xxxxxx Licensed Internal Code failure on the HMC. An exception was thrown from the PIHSCCECCIMClient createInstance code. (E302) Licensed Internal Code error codes Reference Code Description/Action Perform all actions before exchanging Failing Items Licensed Internal Code failure on the HMC. the DVD. password. See (E3CA) Error regarding a media device. If the problem occurs again. • E3CA: Error regarding a media device. Failing Item NEXTLVL (E302) Firmware update error codes The Hardware Management Console generates E302 error codes when it encounters a problem during an update of the firmware for the managed system. • E3D4: See (E3D4) Call home errors. or the hard drive. contact your next level of support. the support Web site. Verify that the support system has accepted the 232 (1xxx) System power control network (SPCN) reference codes Failing Item E302F801 E302F802 E302F803 E302F804 . An error occurred while attempting to find one of the directories used to store data for the firmware update application.Reference codes • E35F: See (E35F) Persistence error codes. user. Verify that you correctly entered valid values for the FTP site. Table 1. Then repeat the operation. then retry the update. or operating). The survey from an FTP site failed when downloading the list of files from the FTP repository failed. standby. Licensed Internal Code failure on the HMC. The survey from the repository method was called. E302F000 to E302F7xx Contact your service provider. contact your next level of support. E302F800 An error occurred while attempting to create a provider instance of the service processor interface code as a PIHSCCECCIMClient. but the repository selected was not support. and directory. • E36C: See (E36C) HMC scheduled task errors. If the problem occurs again. Reboot the HMC and try the operation again. For all other E3xx SRCs. Use the HMC graphical user interface (GUI) to reselect the source for code updates. power off. Go to the Server and Partition display. refresh the screen and ensure the system is in a good state (for example. • E3F0: See (E3F0) Trace failure. E302Exxx Contact your service provider. Verify that the HMC is properly configured to communicate with the support system.

If it fails. Reboot the HMC and retry the operation.Reference codes administrative information for your HMC. Unable to FTP the cover letter from the specified repository to the staging area. If the problem occurs again. or set. Ensure that your connection to the support system is set up correctly and repeat the operation. If it fails again. or operating). refresh the screen and ensure the system is in a good state (for example. Something is wrong with the selected target. and and directory. consider replacing the disk drive of the HMC. If it fails.. No phone server was available to service the request to get a list of code updates. the support Web site. but an I/O exception occurred when closing the list that was written to the hard file. Go to the Server and Partition display. If it fails again. An error occurred while attempting to run the code to get the service processor to run a query. password. The request to get information from support timed out. An invalid object was used while attempting to create an owner for the update. The request to get a list of code updates failed with an exception. the DVD. E302F805 E302F806 E302F807 E302F808 E302F809 E302F80A E302F80B E302F80C E302F80D E302F80E E302F80F E302F810 E302F811 (1xxx) System power control network (SPCN) reference codes 233 . Reboot the HMC and retry the operation. consider replacing the disk drive of the HMC. and then retry the operation. If it fails again. Verify that the FTP site is still up. or the hard drive. user. Failure when attempting to close a file. Reboot the HMC and retry the operation. The request to get a list of code updates failed with an error code. the current IPL side or the next IPL side. The list of code updates was retrieved from the support system. Repeat the operation. If the problem persists contact your next level of support. consider replacing the disk drive of the HMC. The list of code updates was retrieved from the support system. but an I/O exception occurred when the list was written to the hard file. consider replacing the disk drive in the HMC. Then repeat the operation. Failure when attempting to read a file. Reboot the HMC and retry the operation. call your next level of support. standby. contact your next level of support. If it fails again. but the repository selected was not the support system. Reboot the HMC and retry the operation. call your next level of support. Repeat the operation. Unable to get the name of the HMC while preparing to create a service processor client. If it fails again. and then retry the update. Then repeat the operation. then repeat the operation. The method to import the stageable cover letter was called. Reboot the HMC and retry the operation. Use the HMC GUI to reselect the source for code updates. contact your next level of support. power off. Verify that you correctly entered valid values for the FTP site.

Verify that your LAN connection is set up properly. Then repeat the operation. Then repeat the operation. power off. A query of the next IPL side failed. power off. If the problem occurs again. or operating). Retry the operation. standby. The request to get information from support failed with an exception. or operating). The CD or DVD may be faulty. Then retry the operation. refresh the screen and ensure the system is in a good state (for example. Then repeat the operation. power off. Verify that your connection to the support system is set up correctly and is operational. Retry the operation. (1xxx) System power control network (SPCN) reference codes E302F813 E302F814 E302F815 E302F816 E302F817 E302F818 E302F819 E302F81A E302F81B E302F81C E302F81D E302F81E 234 . Go to the Server and Partition display. Go to the Server and Partition display. Then repeat the operation. Reboot the HMC. refresh the screen and ensure the system is in a good state (for example. standby. An exception occurred during a query of the current IPL side. Then repeat the operation. Go to the Server and Partition display. Go to the Server and Partition display. standby. The request to get information from support failed with an error code.Reference codes E302F812 Verify that your connection to the support system is set up correctly and is operational. A query of the current IPL side failed. refresh the screen and ensure the system is in a good state (for example. refresh the screen and ensure the system is in a good state (for example. Verify that your connection to the support system is set up correctly and is operational. Failure of a survey from an FTP site occurred when a connection to the site was unavailable. refresh the screen and ensure the system is in a good state (for example. Then repeat the operation. power off. or operating). A query of the current IPL side returned a null. Go to the Server and Partition display. or operating). An error occurred when attempting to get the service processor to run a query of its state. No phone server was available to service the request to get information from support. Retry the operation. or operating). A query of the next IPL side returned a null. If the problem occurs again. contact your next level of support. Failure during an attempt to copy the information from the support Web site to the staging area on the hard file. power off. Go to the Server and Partition display. standby. An exception occurred during a query of the next IPL side. or operating). Configure the HMC as a phone server and retry the operation. power off. Try another one. power off. Go to the Server and Partition display. contact your next level of support. standby. contact your next level of support. or operating). refresh the screen and ensure the system is in a good state (for example. If the problem occurs again. standby. Failure when attempting to copy the information from the DVD to the staging area on the hard file. Then repeat the operation. standby. refresh the screen and ensure the system is in a good state (for example.

If the problem occurs again. E302F81F E302F820 Ensure that the login parameters are correct. standby. contact your next level of support. Reboot the HMC and try the operation again. An error occurred while attempting to read the common marker firmware update file from flash memory to the hard file. Reboot the HMC and try the operation again. Then repeat the operation. E302F82F (1xxx) System power control network (SPCN) reference codes . contact your next level of support. An exception was thrown from the PIHSCCECCIMClient createInstance code. power off. An error occurred while attempting to read the common marker firmware update file from the hard file into memory. If the problem occurs again. and then retry the operation. If the problem occurs again. standby. Go to the Server and Partition display. contact your next level of support. Ensure that all firewall authentications are successfully performed if needed. An error occurred while attempting to read the header of the common marker firmware update file from flash memory to the hard drive. An error occurred while attempting to create a provider instance of the secondary service processor interface code as a PIHSCCECCIMClient. Reboot the HMC and try the operation again. If the problem occurs again. Go to the Server and Partition display. An error occurred while attempting to read the master firmware update file from the hard drive into memory. Failure of a survey from an FTP site occurred when logging into the site was unsuccessful. or operating). refresh the screen and ensure the system is in a good state (for example. If the problem occurs again contact your next level of support. An error occurred while attempting to find one of the directories used to store data for the firmware update application. If the problem occurs again. Licensed Internal Code failure on the HMC. An error occurred while attempting to find one of the directories used to store data for the firmware update application. contact your next level of support. An error occurred while attempting to read the header of the master firmware update file from flash memory to the hard file. contact your next level of support. Reboot the HMC and retry the operation. Reboot the HMC and try the operation again. contact your next level of support. If the problem occurs again. or power on). Contact your service provider. Licensed Internal Code failure on the HMC. and then retry the operation. Reboot the HMC and try the operation again. E302F82D Reboot the HMC and try the operation again.Reference codes Ensure that the FTP site is reachable on the network from the HMC and that the site is up and running properly. refresh the screen and ensure that the system is in a good state (power off. Contact your service provider. Then repeat the operation. An error occurred while attempting to read the master firmware update file from flash memory to the hard drive. 235 E302F821 E302F822 E302F823 to E302F827 E302F828 E302F829 E302F82A E302F82B E302F82C E302F82E. If the problem occurs again contact your next level of support.

Try the operation again. If the problem occurs again. Try the operation again. An error occurred while attempting to issue a "code update complete" action to the master service processor. If the problem occurs again. but the repository selected was not the support system or the support Web site. E302F831 E302F832 Follow the HMC procedures to remove dump files from the HMC disk drive. If the problem occurs again.) Then reboot the HMC and try the operation again. Try the operation again. The "import from a remote repository" code routine was called. An error occurred while attempting to get the engineering change streams in order to retrieve all of the updates from removable media. contact your next level of support. Reboot the HMC and try the operation again. Verify that the cover letter is correct and has not been corrupted. An error occurred while trying to create a private staging area directory for firmware update files on the HMC disk drive.Reference codes E302F830 An error occurred while attempting to read a flash firmware update file from the hard file into memory. Contact your service provider. If the problem occurs again. Reboot the HMC and try the operation again. contact your next level of support. If the problem occurs again. verify that your test firmware update files are correct. E302F833 E302F834 to E302F837 E302F838 E302F839 to E302F83F E302F840 E302F841 E302F842 E302F843 E302F844 E302F845 E302F846 236 (1xxx) System power control network (SPCN) reference codes . contact your next level of support. If you are using nondisruptive microcode. Follow the procedures for E302F832. Licensed Internal Code failure on the HMC. Reboot the HMC and try the operation again. If the problem occurs again. An error occurred while attempting to issue a start code update command to the master service processor. especially if this error occurs with E302F832. consider replacing the disk drive of the HMC. (The HMC disk drive is used for the private staging area and it may be full. A file that was supposed to be a firmware update file either does not exist or is too small to contain a valid header. An error occurred while trying to change file permissions in the private staging area directory for firmware update files. Otherwise contact your next level of support. contact your next level of support. Licensed Internal Code failure on the HMC. contact your next level of support. contact your next level of support. contact your next level of support. If the problem occurs again. If the problem occurs again. This error might indicate that the files in the private staging area were not created. contact your next level of support. An error occurred while attempting to reboot the service processor Try the operation again. Contact your service provider. Use the HMC GUI to reselect the source for code updates. If the problem occurs again. An error occurred while attempting to read the information about the code update out of the cover letter. An error occurred while attempting to issue a write firmware update file command to the master service processor.

but no such engineering change stream exists for the targeted object. An error occurred while trying to copy the RPM files from the media repository to the hard file. consider replacing the disk drive of your HMC. contact your next level of support. If the problem occurs again. Try the operation again. A request to import the code updates and information failed. contact your next level of support. If the problem occurs again. The CD or DVD may be faulty.rpm rpm -qp rpmfilename (where rpmfilename is the name of the file returned by the ls command) rpm -e rpm packagename (where packagename is the name of the package returned by the rpm -e command) E302F851 (1xxx) System power control network (SPCN) reference codes 237 E302F847 E302F848 E302F849 E302F84A E302F84B E302F84C E302F84D E302F84E E302F84F E302F850 . Failure during an attempt to close the surveyed list of code updates. Reboot the HMC and try the operation again. An error occurred in a method because one of the file arrays had a length of zero. Try another one. Retry the operation. contact your next level of support. contact your next level of support. there was a problem that can be corrected with commands from the Linux command line as follows: ls -l /opt/ccfw/data/*. If the problem occurs again. Reboot the HMC and try the operation again. In the HMC code released before August 2004. An error occurred in a removable media code routine because the file types were null. If the problem reoccurs. If the problem occurs again. consider replacing the disk drive of your HMC. Retry the operation.Reference codes An error occurred while attempting to swap the T and P sides of the service processor. An error occurred while attempting to get the engineering change streams in order to list all of the updates available on the removable media. If the problem occurs again. If the problem occurs again. If the problem reoccurs. Reboot the HMC and try the operation again. Verify that your connection to the support system is set up correctly and is operational. Reboot the HMC and try the operation again. contact your next level of support. Verify that your connection to the support system is set up correctly and is operational. Reboot the HMC and try the operation again. An engineering change stream was passed between components. A failure occurred while trying to unpack the RPM file in the "complete concurrently" code routine. If the problem occurs again. Reboot the HMC and try the operation again. Failure during an attempt to read the surveyed list of code updates. A request to import the code updates and information timed out. contact your next level of support. contact your next level of support. Reboot the HMC and try the operation again.

No phone server was available to serve the request to retrieve code updates. contact your next level of support. Configure the HMC as a phone server and retry the operation. A failure occurred when trying to query the name of the image in the RPM file. An exception occurred while trying to unpack the RPM file in the "complete concurrently" code routine. An error occurred while attempting to find the directory where firmware update files are stored for testing with the non disruptive application panel. and then choose Accept to copy the T side to the P side. If the problem occurs again. contact your next level of support. The level of code requested is most likely activated on the targeted system. contact your next level of support. Try the operation again. contact your next level of support. contact your next level of support. An exception occurred while trying to import updates from the DVD.Reference codes The request to retrieve code updates from the support system failed with an error code. If the problem occurs again. Then IPL the system unit if desired. An exception occurred while attempting to issue the runact API. If the problem occurs again. contact your next level of support. An exception occurred while trying to query the name of the image in the RPM file. If the problem occurs again. If the problem occurs again. contact your next level of support. Verify that your connection to the support system is set up correctly and is operational. Try another one. If the problem occurs again. Verify the activated level through System Information. If the problem occurs again. Try the operation again. An error occurred while attempting to issue a read firmware update file command to a service processor Try the operation again. The CD or DVD may be faulty. choose Select advanced features. contact your next level of support. Importing from an FTP site failed when the files from the FTP repository were not retrieved. Try the operation again. If the problem occurs again. Try the operation again. E302F852 E302F853 E302F854 E302F855 E302F856 E302F857 E302F858 E302F859 E302F85A E302F85B E302F85C E302F85D E302F85E 238 (1xxx) System power control network (SPCN) reference codes . An error occurred while attempting to copy the T side to the P side. If the problem occurs again. contact your next level of support. If the problem occurs again. In the Licensed Internal Code Update panels. contact your next level of support. Reboot the HMC and try the operation again. Try the operation again. Try the operation again. An error occurred while attempting to power on the system unit. Retry the operation. An error occurred while attempting to IPL the system unit. A failure occurred while attempting to issue the runact API.

Verify the activated level through System Information. An error occurred while attempting to power off the system unit. but not loaded into the hypervisor. If the activated level is what is expected. The CD or DVD may be faulty. Verify the activated level through System Information. The level of code requested is most likely activated on the targeted system.Reference codes E302F85F The level of code requested is most likely activated on the targeted system. The level of code requested is most likely activated on the targeted system. If the activated level is what is expected. schedule a time to IPL the system. The level of code requested is most likely activated on the targeted system. but not loaded into the hypervisor. • For systems using HMC firmware before V5R1. schedule a time to IPL the system. If the activated level is what is expected. If the activated level is what is expected. If the activated level is what is expected. Verify the activated level through System Information. schedule a time to IPL the system. An exception occurred during the query to see if a hypervisor firmware update has completed. The hypervisor firmware update timed out. Verify the activated level through System Information. Try powering off the system unit manually and doing the code update while the system is in the platform standby state. The level of code requested is most likely activated on the targeted system. An error occurred while trying to import updates to the DVD during an export command. Verify the activated level through System Information. A failure occurred while querying the status after a firmware update. E302F860 E302F861 E302F862 E302F863 E302F864 E302F865 E302F866 E302F867 E302F868 (1xxx) System power control network (SPCN) reference codes 239 . but not loaded into the server firmware. Verify the activated level through System Information. Verify the activated level through System Information. An error occurred while issuing a start code update command to the secondary service processor. If this does not occur. The level of code requested is most likely activated on the targeted system. the secondary service processor will be synchronized in the next code update. schedule a time to IPL the system. If the activated level is what is expected. An error occurred while attempting to write the hypervisor diff file to the hypervisor.1. contact your next level of support. but not loaded into the hypervisor. An error occurred while attempting to close the hypervisor firmware diff file after writing it to the server firmware. If the activated level is what is expected. An interruption occurred while waiting for the hypervisor firmware update. The level of code requested is most likely activated on the targeted system. but not loaded into the server firmware. Then power on the system unit if desired. The level of code requested is most likely activated on the targeted system. schedule a time to IPL the system. Verify the activated level through System Information. schedule a time to IPL the system. but not loaded into the hypervisor. but not loaded into the server firmware. Try another one. An error occurred while attempting to open the hypervisor diff file prior to writing. schedule a time to IPL the system.

The level of code requested is most likely activated on the targeted system. If the activated level is what is expected. If this does not occur. Ensure that you set up the service processor failover feature as desired after you complete the replace and verify procedure. A code update did not contain a diff firmware update file. but not loaded into the server firmware. follow the appropriate replace and verify procedure to synchronize the secondary service processor firmware to the primary firmware.1 (or newer) HMC firmware. follow the appropriate replace and verify procedure to synchronize the secondary service processor firmware to the primary firmware. If this does not occur. The level of code requested is most likely activated on the targeted system. but not loaded into the hypervisor firmware. the secondary service processor will be synchronized in the next code update. schedule a time to IPL the system. • For systems using HMC firmware before V5R1.Reference codes E302F869 • For systems using V5R1. or no diff firmware update file was found in the firmware update file directory. Verify the activated level through System Information.1. (1xxx) System power control network (SPCN) reference codes E302F86A E302F86B E302F86C E302F86D E302F86E E302F86F E302F870 240 . Verify the activated level through System Information. Verify the activated level through System Information. An error occurred during a call to a code module while attempting to write the hypervisor firmware diff file to flash memory. but not loaded into the server firmware. but not loaded into the server firmware. • For systems using V5R1. If the activated level is what is expected. An exception occurred while issuing a runact API to query the partitions and their status. the secondary service processor will be synchronized in the next code update. The level of code requested is most likely activated on the targeted system.1. but not loaded into the hypervisor firmware. If the activated level is what is expected. An error occurred during a call to a code module after writing the hypervisor firmware diff file to flash memory. • For systems using V5R1. Verify the activated level through System Information. If the activated level is what is expected. schedule a time to restart the partitions. • For systems using HMC firmware before V5R1. Ensure that you set up the service processor failover feature as desired after you complete the replace and verify procedure. schedule a time to IPL the system. for nondisruptive firmware application. Verify the activated level through System Information. contact your next level of support. Ensure that you set up the service processor failover feature as desired after you complete the replace and verify procedure. The level of code requested is most likely activated on the targeted system.1 (or newer) HMC firmware. contact your next level of support. The level of code requested is most likely activated on the targeted system.1 (or newer) HMC firmware. An error occurred during a call to a code module while preparing to write the hypervisor firmware diff file to flash memory. An error occurred while issuing a write firmware update file command to the secondary service processor. schedule a time to IPL the system. schedule a time to restart the partitions. An error occurred issuing a code update complete command to the secondary service processor. If the activated level is what is expected. A failure occurred while issuing a runact API to query the partitions and their status. follow the appropriate replace and verify procedure to synchronize the secondary service processor firmware to the primary firmware.

Reference codes E302F871 The level of code requested is most likely activated on the targeted system. refresh the screen and ensure the system is in a good state (for example. Verify the activated level through System Information. check System Information to ensure the code update was applied. schedule a time to IPL the system. If the problem occurs again. An error occurred while attempting to query (at standby) in an attempt to retrieve all of the updates from the removable media. A failure occurred trying to erase an RPM file. If the code update fails again. 241 E302F872 E302F873 E302F874 E302F875 E302F876 E302F877 E302F878 E302F879 E302F87A E302F87B (1xxx) System power control network (SPCN) reference codes . Rebooting the service processor was executed. An error occurred during the call to start firmware update to concurrently patch firmware. Rebooting the service processor was executed. contact your next level of support. but the system unit did not return to its original state within a reasonable amount of time. Verify the activated level through System Information. An exception occurred trying to erase an RPM file. schedule a time to IPL the system. If it is not in a good state. Go to the Server and Partition display. If the activated level is what is expected. then take the necessary steps to put it in a good state. An exception occurred while trying to query the name of the image in the RPM file. If the activated level is what is expected. To do this. contact your next level of support. contact your next level of support. Reboot the HMC and try the operation again. An exception occurred while trying to change the permissions of an image file after it had been pulled from an RPM package. If the problem occurs again. A failure occurred while trying to change the permissions of an image file after it had been pulled from an RPM package. but not loaded into the server firmware. but the system unit did not return to the state where the T side was active within a reasonable amount of time. or operating). contact your next level of support. If the problem occurs again. Querying status after a firmware update did not return the proper number of elements in the vector. standby. contact your next level of support. but not loaded into the server firmware. contact your next level of support. If the problem occurs again. select Select Advanced Features and then select Install And Activate. The level of code requested is most likely activated on the targeted system. schedule a time to IPL the system. Reboot the HMC and try the operation again. Reboot the HMC and try the operation again. The level of code requested is most likely activated on the targeted system. Reboot the HMC and try the operation again. Try another one. but not loaded into the hypervisor firmware. power off. repeat the operation. Reboot the HMC and try the operation again. Verify the activated level through System Information. After it is in a good state. The CD or DVD may be faulty. This generally means that the system was not successful when coming up with the new code level and went back to the older code level Retry the operation. A failure occurred while trying to query the name of the image in the RPM file. If the problem occurs again. If it is now in a good state but the update is not applied. If the activated level is what is expected.

contact your next level of support. contact your next level of support. contact your next level of support. When in a good state. power off. Go to the Server and Partition display. but the managed system was placed in an error state. After it is in a good state. check System Information to E302F87D E302F87E E302F87F E302F880 E302F881 E302F882 E302F883 E302F884 242 (1xxx) System power control network (SPCN) reference codes . or operating). An IPL of the service processor was executed as part of a disruptive firmware update. but it did not put the service processor in a powered on state within a reasonable amount of time.1. standby. take the necessary steps to put it in a good state. standby. • For systems using V5R1. contact your next level of support. After it is in a good state. power off. A failure occurred importing I/O microcode. power off. repeat the code update operation. refresh the screen and ensure the system is in a good state (for example. • For systems using HMC firmware before V5R1. Powering off the service processor was executed as part of a disruptive firmware update. If it is not in a good state. or operating). or operating). After the flash write to the primary service processor was complete. Ensure that you set up the service processor failover feature as desired after you complete the replace and verify procedure. If this message occurs. If this does not occur. If the problem occurs again. contact your next level of support. but the managed system was placed in an error state. standby. The service processor was rebooted during a firmware update.1 (or newer) HMC firmware. If it is not in a good state. refresh the screen and ensure the system is in a good state (for example. refresh the screen and ensure the system is in a good state (for example. take the necessary steps to put it in a good state. contact your next level of support. follow the appropriate replace and verify procedure to synchronize the secondary service processor firmware to the primary firmware. but it did not put the service processor in a "not connected" state within a reasonable amount of time. Go to the Server and Partition display. If this message occurs. If it is not in a good state. Go to the Server and Partition display. standby. but it did not put the service processor in a powered off state within a reasonable amount of time. check System Information to ensure the code update was applied. If the problem occurs again. Try the operation again. A power off was executed as part of a disruptive firmware update. refresh the screen and ensure the system is in a good state (for example. If it is not in a good state. take the necessary steps to put it in a good state.Reference codes E302F87C Reboot the HMC and try the operation again. the secondary service processor will be synchronized in the next code update. power off. If this message occurs. After it is in a good state. but it did not put the system in its original state within a reasonable amount of time. Go to the Server and Partition display. Powering on the service processor was executed as part of a disruptive firmware update. A power on was executed as part of a disruptive firmware update. An IPL was executed as part of a disruptive firmware update. but the managed system was placed in an error state. the secondary service processor did not complete operations within half an hour. take the necessary steps to put it in a good state. or operating). check System Information to ensure the code update was applied.

If the problem occurs again. Contact the next level of support for assistance in getting the HMC to communicate with the service processor again. but it failed. If another error occurs before this message. However. A general error occurred while processing a hardware upgrade. follow the action for that error. Failure when attempting to import an RPM package from the support Web site. follow the action for that error. contact your next level of support. follow the action for that error. contact your next level of support. A general error occurred while applying code. this action did not clear the "not connected" state within a reasonable amount of time. Reboot the HMC and try the operation again. An exception occurred during execution of the synchronous apply staged updates program while applying code from the hard file staging area. If the problem occurs again. contact your next level of support. The service processor was rebooted during a firmware update. Verify that your LAN connections are set up properly and retry the operation. If this message occurs. A general error occurred while committing code. but it was a concurrent request. If another error occurs before this message. An error occurred while attempting to find the directory used as temporary storage. If this message occurs by itself. then repeat the operation. If this message occurs by itself. Powering off the system unit has started. E302F886 E302F887 E302F888 E302F889 E302F88A E302F88B E302F88C E302F88D E302F88E E302F88F E302F890 E302F891 E302F892 E302F893 E302F894 E302F895 (1xxx) System power control network (SPCN) reference codes 243 . Restoring of the firmware update files to the P side has started. Rebooting the service processor has started. contact your next level of support. An exception occurred after a chsyscfg command was issued to change the next IPL side. contact your next level of support. Reboot the HMC and try the operation again. Powering on the system unit has started. This operation can only be performed disruptively. contact your next level of support.Reference codes E302F885 ensure the code update was applied. contact your next level of support. Retry the operation during that scheduled time. Reboot the HMC and schedule time for a disruptive update. If the problem occurs again. If the problem occurs again. which put the service processor in a "not connected" state. Reboot the HMC and try the operation again. If another error occurs before this message. contact your next level of support. If this message occurs by itself. contact your next level of support. A chsyscfg command was issued to change the next IPL side. If this message occurs. A request was received to take the service processor back to an earlier level. If the problem occurs again. Writing of the firmware update files has started. Reading of the firmware update files has started. If it is now in a good state but the update is not applied. contact your next level of support. An exception occurred during execution of the synchronous import program while retrieving code from a repository.

contact your next level of support. Ensure that you set up the service processor failover feature as desired after you complete the replace and verify procedure. follow the action for that error. contact your next level of support. If another error occurs before this message. contact your next level of support. • For systems using V5R1. the secondary service processor will be synchronized in the next code update. An error occurred while copying the T to the P side on the secondary service processor. Allow all currently running code update processes to end successfully on all of the associated HMCs. If another error occurs before this message. If this message occurs by itself. If this message occurs by itself. A general error occurred while importing code.1 (or newer) HMC firmware. If this message occurs by itself. Ensure that all frame numbering. The BPA is locked by another process. the secondary service processor will be synchronized in the next code update. contact your next level of support. follow the appropriate replace and verify procedure to synchronize the secondary service processor firmware to the primary firmware. contact your next level of support. An error occurred while swapping the T and P sides of the secondary service processor. 3. and repair and verify processes that also use BPA locking end successfully on all of the associated HMCs. If this message occurs by itself. follow the action for that error. contact your next level of support. frame initialization. If another error occurs before this message. An attempt to set a lock on a BPA frame failed. A general error occurred while rejecting code.1 (or newer) HMC firmware. An attempt was made to update the hypervisor firmware. E302F897 E302F898 E302F899 E302F89A E302F89B E302F89C E302F89D E302F89E E302F89F If another error occurs before this message. contact your next level of support. follow the appropriate replace and verify procedure to synchronize the secondary service processor firmware to the primary firmware. A general error occurred while updating the flash on a service processor.Reference codes E302F896 A general error occurred while exporting code to the DVD. If this message occurs by itself. but the hypervisor reported that it is already at that level. Make sure that you do not select multiple managed systems (that are associated with the same power frame) for simultaneous managed system and power code update or upgrade. contact your next level of support. 2. • For systems using V5R1. Ensure that you set up the service processor failover feature as desired after you complete the replace and verify procedure. follow the action for that error. If another error occurs before this message. • For systems using HMC firmware before V5R1. If another error occurs before this message. follow the action for that error. • For systems using HMC firmware before V5R1. follow the action for that error. Do the following as applicable: 1. A failure occurred while trying to erase a file. or rebooting them after writing the firmware. If this does not occur. A failure occurred either writing the firmware to the bulk power assemblies (BPAs). 244 (1xxx) System power control network (SPCN) reference codes .1.1. If this message occurs by itself. If this does not occur. follow the action for that error.

If the error occurs again. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. contact your next level of support. An error occurred while trying to close the list of code updates that was surveyed. An error occurred while trying to read the list of code updates that was surveyed. An error occurred when attempting to copy the P-side flash memory to the T-side on the master service processor. Querying to see if the service firmware diff file is in memory did not return the proper number of elements in the vector. contact your next level of support. If the error occurs again. Retry the operation. Licensed Internal Code failure on the HMC. If the error occurs again. contact your next level of support. An exception occurred while querying to see if the HMC is the code update owner. 245 E302F8AA E302F8AB (1xxx) System power control network (SPCN) reference codes . If the error occurs again. If this message occurs by itself. E302F8A1 E302F8A2 E302F8A3 E302F8A4 E302F8A5 E302F8A6 E302F8A7 E302F8A8 Contact your service provider. If the error occurs again. use the following command from the HMC: rmlock -e Frame*MTMS E302F8A0 where Frame*MTMS is the machine-type. If the problem occurs again. Try the operation again. model. Try the operation again. An error occurred when attempting to copy the P-side flash memory to the T-side on the secondary service processor. remove the BPA lock. A general error occurred while rebooting. An exception occurred while querying to see if the server firmware diff file is in memory. E302F8A9 If another error occurs before this message. Try the operation again. An error occurred while querying to see if the server firmware diff file is in memory. If the problem occurs again. consider replacing the disk drive of the HMC. contact your next level of support. To remove the BPA lock. Try the operation again. 5. If the error occurs again. contact your next level of support. An exception occurred while setting the HMC to be the code update owner. consider replacing the disk drive of the HMC. If the error occurs again.Reference codes 4. contact your next level of support. follow the action for that error. If the error occurs again. An error occurred while attempting to update the server firmware. Try the operation again. After all the operations are finished and a retargeting to one of the managed systems still results in this error. Try the operation again. and serial number of the affected BPA. contact your next level of support. contact your next level of support. Try the operation again.

The file was not found at the Web site. An error occurred while surveying the support Web site.Reference codes E302F8AC to E302F8CF E302F8D0 Try the operation again. The survey from an FTP site failed when the control program was not able to change the directory to that of the user. Contact the network administrator for your installation to determine if a firewall or other network security process must be opened for the HMC to access the Internet. If the HMC is on a private network. E302F8D1 E302F8D2 to E302F8EF E302F8F0 E302F8F1 E302F8F2 E302F8F3 If another error occurs before this message. contact your next level of support. An exception occurred while copying the XML file to the cover letter during importation from the Web site. the support Web site will not be available as a repository. Contact your service provider. If the problem occurs again. If the problem occurs again. contact your next level of support. Retry the operation again after you successfully access the support Web site. Licensed Internal Code failure on the HMC. If this message occurs by itself. If the error occurs again. Contact your service provider. Contact your service provider. contact your next level of support. If the problem occurs again. Verify that the HMC connection to the support Web site is working. If the problem occurs again. Verify that the FTP site directory specified is correct and that any firewall authentications were completed. Try the operation again. An error occurred while writing a firmware update file that was read from a code update to disk. Two hour wait period exceeded for the updating of firmware on the service processor in the bulk power assembly. follow the action for that error. If the problem occurs again. If the error occurs again. contact your next level of support. Licensed Internal Code failure on the HMC. Reboot the HMC and retry the operation. Licensed Internal Code failure on the HMC. A query of the current boot side of the secondary processor returned a null. if necessary. Use the Update Managed System Password field under the Server and Partition panels 246 (1xxx) System power control network (SPCN) reference codes E302F8F4 E302F8F5 to E302F8FF E302F900 E302F901 . An I/O error occurred while reading the code update image. Verify that your LAN connections are set up properly and retry the operation. Verify that your LAN connections are set up properly and retry the operation. If the problem occurs again. An exception occurred while surveying the support Web site. contact your next level of support. Verify that your LAN connections are set up properly and retry the operation. Reboot the HMC and retry the operation. Verify that the authentication passwords for the service processors are synchronized and that the TCP/IP addresses of the service processors are not in the HMC DHCP server's removed list. An error occurred while surveying the support Web site. contact your next level of support. contact your next level of support. consider replacing the disk drive in the HMC. contact your next level of support. before performing the update.

contact your next level of support. Retry the operation. Choose Select advanced features. This is a requirement. One of the bulk power assemblies targeted for firmware update has an auto-code download (ACDL) pending. Retry the operation. Verify that both the primary and secondary service processors for the bulk power assembly (or assemblies) are configured properly and available for communication with the HMC. contact your next level of support. Depending on the number of FRUs being loaded. contact your next level of support. If the problem occurs again. Wait two hours for that auto-code download to complete. Perform an Install and activate (implied Retrieve) Specific Level update to the current level of power (1xxx) System power control network (SPCN) reference codes 247 E302F902 E302F903 to E302F90F E302F910 E302F911 E302F912 E302F913 E302F914 . try the original operation again. Use the restricted shell "mksysconn -o auto" command to reset the HMC DHCP server's removed list and reconnect the affected service processors. If the problem occurs again. If the problem occurs again. contact your next level of support. Licensed Internal Code failure on the HMC. Verify that both the primary and secondary service processors for the bulk power assembly (or assemblies) are configured properly and available for communication with the HMC. do the following: 1. Verify that the authentication passwords for the service processors are synchronized and that the TCP/IP addresses of the service processors are not in the HMC DHCP server's removed list. Verify that both the primary and secondary service processors for the bulk power assembly (or assemblies) are configured properly and available for communication with the HMC. contact your next level of support. If the problem occurs again. then try the original operation again. After two hours. Perform a "Disruptive Activate" using the Select advanced features panels. contact your next level of support. Use the restricted shell "mksysconn -o auto" command to reset the HMC DHCP server's removed list and reconnect the affected service processors. • For systems using V5R2 (or newer) HMC firmware. A failure occurred when querying to find out if the bulk power assembly was N-mode. An exception occurred when attempting to start the auto-code download (ACDL) on a bulk power assembly. If the problem occurs again. An exception occurred when querying to find out if the bulk power assembly was N-mode. A code update cannot be performed while a service processor in the bulk power assembly is running an auto-code download process. A query of the next boot side of the secondary processor returned a null. If the failure occurs again. One of the bulk power assemblies targeted for firmware update has N-mode power. • For systems using HMC firmware before V5R2. wait two hours and manually point the next re-IPL of the service processor to the "P" side by using the Flash Side Selection panels. 2. Contact your service provider. this process might take a significantly long time.Reference codes to reset the password if necessary. If the problem occurs again. This is a requirement. This is a requirement. contact your next level of support. Use the Update Managed System Password pulldown under the Server and Partition panels to reset the password if necessary. Retry the operation.

and then finish the code update. Click Change Levels. Click Change Levels. contact your next level of support. Leave the Managed System code level as None. do the following: 1. If the problem occurs again. • For systems using V5R2 (or newer) HMC firmware. • For systems using V5R2 (or newer) HMC firmware. 248 (1xxx) System power control network (SPCN) reference codes E302F915 E302F916 E302F917 E302F918 . Choose Select advanced features. (Choose Automatically Accept. Perform an Install and activate (implied Retrieve) Specific Level update to the current level of power firmware on the hard drive repository. Click Change Levels. contact your next level of support. (Choose Automatically Accept.) 3. and change None to the current level of power firmware. A failure occurred when attempting to start the auto-code download (ACDL) on a bulk power assembly. contact your next level of support. 2. and then finish the code update. contact your next level of support. Leave the Managed System code level as None. • For systems using HMC firmware before V5R2.) 3. 2. A failure occurred when attempting to determine how many FRUs were completed during an auto-code download (ACDL). and then finish the code update.Reference codes firmware on the hard drive repository.) 3. 4. An exception occurred when attempting to determine how many FRUs were completed during an auto-code download (ACDL). 2. do the following: 1. If the problem occurs again. • For systems using HMC firmware before V5R2. • For systems using HMC firmware before V5R2. Perform an Install and activate (implied Retrieve) Specific Level update to the current level of power firmware on the hard drive repository. and change None to the current level of power firmware. (Choose Automatically Accept. 4. The auto-code download (ACDL) took too long on one side of the bulk power assembly. Choose Select advanced features. • For systems using V5R2 (or newer) HMC firmware. contact your next level of support. 4. Perform an Install and activate (implied Retrieve) Specific Level update to the current level of power firmware on the hard drive repository. contact your next level of support. and change None to the current level of power firmware. • For systems using HMC firmware before V5R2. contact your next level of support. do the following: 1. do the following: 1. 4.) 3. contact your next level of support. If the problem occurs again. and change None to the current level of power firmware. Choose Select advanced features. Choose Select advanced features. If the problem occurs again. and then finish the code update. Leave the Managed System code level as None. • For systems using V5R2 (or newer) HMC firmware. (Choose Automatically Accept. Leave the Managed System code level as None. Click Change Levels.

if necessary.Reference codes E302F919 2. Contact your service provider. 4. If the error occurs again. If the error occurs again. E302F91B Reboot the HMC and retry the operation. The auto-code download (ACDL) began but did not complete successfully. This operation also accepts the system unit code. E302F91A Reboot the HMC and retry the operation. If the error occurs again. Licensed Internal Code failure on the HMC.lst file in /opt/ccfw/data directory. contact your next level of support. After you clear the file space. E302F922 (1xxx) System power control network (SPCN) reference codes 249 . An I/O error occurred when attempting to write the power FRU code levels to a file. If the error occurs again. If the problem occurs again. Follow the actions listed for E302F918. E302F91F Reboot the HMC and retry the operation.frus. If the error occurs again. Reboot the HMC and retry the operation. contact your next level of support. execute the dlslic command again as a user with root authority. contact your next level of support. An I/O error occurred when attempting to close the file containing the Power FRU code levels. contact your next level of support. and change None to the current level of power firmware. Ensure the following: • That ample space exists in the file system that contains the /opt/ccfw directory • That the a user with root authority executes the following command: dlslic -e Frame*MTMS E302F91D E302F91E E302F920 Note: The dlslic command is a diagnostic aid that obtains ACDL status and creates the bpa. A failure occurred when trying to deactivate a bulk power assembly. (Choose Automatically Accept.) 3. If the problem occurs again. and then finish the code update. contact your next level of support. Perform an Install and activate (implied Retrieve) Specific Level update to the current level of power firmware on the hard drive repository. E302F91C Perform an "Accept" operation using the Select advanced features panels. E302F921 Perform the actions for error code E302 F920. A failure occurred when attempting to query the state of the system unit after receiving an asynchronous report that the state had changed. contact your next level of support. contact your next level of support. If the error occurs again. An exception occurred when trying to deactivate a bulk power assembly. Leave the Managed System code level as None. An error occurred in the service processor support code during a query of the state of a service processor for a frame. contact your next level of support. A failure occurred while copying the firmware from the T side to the P side after a successful update of the bulk power controller code. Click Change Levels.

A firmware update reboot of the secondary service processor placed it into a not connected state. Follow the actions listed for E302F925. • If another error occurs before this message. contact your next level of support. If the error occurs again. An exception occurred when attempting to set the service processor failover state with the chsyscfg command. correct the condition that caused the Health Check to fail and retry the operation. • If another error occurs before this message. contact your next level of support. E302F928 Check to see if a long running DLPAR operation is in progress to the same managed system. A failure occurred when attempting to set the service processor failover state with the chsyscfg command. A failure occurred during a query of the current service processor failover state. contact your next level of support. An error occurred when attempting to acquire the service processor lock. E302F927 Reboot the HMC and retry the operation. follow the action for that error.Reference codes An exception occurred when attempting to set or release a lock on a bulk power adapter frame. follow the action for that error. contact your next level of support. • If this message occurs during a code update Health Check. but it did not clear that state in a reasonable amount of time. • If this message occurs during a code update Health Check. • If this message occurs by itself. contact your next level of support. An exception occurred during the query of the current service processor failover state. contact your next level of support. A timeout error occurred when attempting to acquire the service processor lock. follow the action for that error. If there is. E302F92A Informational message. An error occurred when attempting to release the service processor lock. Dynamic service processor failover has been disabled. • If this message occurs by itself. • If this message occurs during a code update Health Check. If the error occurs again. correct the condition that caused the Health Check to fail and retry the operation. If the error occurs again. Perform the actions for error code E302 F89F. correct the condition that caused the Health Check to fail and retry the operation. wait for that operation to complete and then perform a Disruptive Activate. Dynamic service processor failover has been enabled. Reboot the HMC and retry the operation. • If this message occurs by itself. contact your next level of support. (1xxx) System power control network (SPCN) reference codes E302F923 E302F924 E302F925 E302F926 E302F929 250 . If the error occurs again. • If another error occurs before this message. E302F92B E302F92C Informational message.

Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. an exception occurred in the getRedundantFspInfoExt() method when attempting to determine the state of the secondary service processor. During readiness checking. Reboot the HMC and retry the operation. contact your next level of support. During readiness checking. If the error occurs again. an exception occurred in the readBPAPowerStatus() method when attempting to determine the status of the power subsystem. If the error occurs again. Reboot the HMC and retry the operation. contact your next level of support. During readiness checking. Reboot the HMC and retry the operation. During readiness checking. an exception occurred in the isNModePower() method when attempting to determine the state of the power subsystem.Reference codes E302F92D Contact the next level of support for assistance in getting the HMC to talk to the service processor again. contact your next level of support. If the error occurs again. During readiness checking. contact your next level of support. 251 E302F936 E302F937 (1xxx) System power control network (SPCN) reference codes . a null value was returned by the getConnectionStatus() method when attempting to determine the status of service processor connections. an exception occurred in the getConnectionStatus() method when attempting to determine the status of service processor connections. Reboot the HMC and retry the operation. contact your next level of support. Reboot the HMC and retry the operation. During readiness checking. If the error occurs again. a null value was returned by the readBPAPowerStatus() method when attempting to determine the status of the power subsystem. a null value was returned by the getRedundantFspInfoExt() method when attempting to determine the state of the secondary service processor. contact your next level of support. a null value was returned by the getConnectionStatus() method when attempting to determine the status of power subsystem connections. If the error occurs again. During readiness checking. If the error occurs again. During readiness checking. contact your next level of support. an exception occurred in the getState() method when attempting to determine the state of the power subsystem. contact your next level of support. If the error occurs again. If the error occurs again. During readiness checking. During readiness checking. contact your next level of support. contact your next level of support. During readiness checking. an exception occurred in the getState() method when attempting to determine the state of the managed system. E302F92E E302F92F E302F930 E302F931 E302F932 E302F933 E302F934 E302F935 Reboot the HMC and retry the operation. an exception occurred in the getConnectionStatus() method when attempting to determine the status of power subsystem connections. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. If the error occurs again. If the error occurs again.

contact your next level of support. An error occurred during the processing for the advanced features task when trying to run a tasklet exit on the client to display the license panel. If the error occurs again. An error occurred during the processing for the update licensed internal code MES select level panel handler. The task is terminated. An error occurred during the processing for the update licensed internal code main repository panel handler. E302F9AE Reboot the HMC and retry the operation. contact your next level of support. If the problem occurs again. Error during processing for the Change Internal Code Wizard Reboot the HMC and retry the operation. If the error occurs again. If the error occurs again. If the problem occurs again. contact your next level of support. 252 (1xxx) System power control network (SPCN) reference codes E302F9AF E302F9B0 E302F9B1 E302F9B2 E302F9B3 E302F9B4 to E302F9B6 E302F9B7 E302F9B8 . If the error occurs again. If the error occurs again. An error occurred during the processing for the MES upgrade task when trying to run a tasklet exit on the client to display the license panel. contact your next level of support. An error occurred during the processing for the update licensed internal code FTPpanel panel handler. E302F9AD Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. contact your next level of support. Reboot the HMC and retry the operation. If the problem occurs again. If the problem occurs again. Error during processing for an internal panel handler. Error during processing of the server side of the scheduleable update task. contact your next level of support.Reference codes E302F938 to E302F9AA Reboot the HMC and retry the operation. If the error occurs again. An error occurred during the processing for the change internal code wizard when trying to run a tasklet exit on the client to display the license panel. Error during processing for an internal code method. contact your next level of support. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. E302F9AB E302F9AC Reboot the HMC and retry the operation. If the error occurs again. Contact your service provider. Reboot the HMC and retry the operation. If the error occurs again. contact your next level of support. contact your next level of support. If the problem occurs again. Licensed Internal Code failure on the HMC. The task is terminated. The task is terminated. contact your next level of support. Reboot the HMC and retry the operation. An error occurred during the processing for the update licensed internal code changeFTP panel handler. Error trying to perform processing in a hardware upgrade code path. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support.

Reference codes E302F9B9 Error during the main "service" processing for the server side of the hardware upgrade task. Reboot the HMC and retry the operation. The progress panel for the affected target is updated with error message. Reboot the HMC and retry the operation. contact your next level of support. contact your next level of support. contact your next level of support. E302F9BA E302F9BB E302F9BC E302F9BD E302F9BE E302F9BF E302F9C0 E302F9C1 E302F9C2 E302F9C3 E302F9C4 E302F9C5 (1xxx) System power control network (SPCN) reference codes 253 . contact your next level of support. contact your next level of support. Error during the main "service" processing for the server side of the change internal code wizard cecdetails panel handler. contact your next level of support. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. Error during the processing of the actual non disruptive firmware update task. Reboot the HMC and retry the operation. Error during the main "service" processing for the server side of the change internal code wizard subtasklet. The task continues to execute. Reboot the HMC and retry the operation. Error during the main "service" processing for the server side of the change internal code wizard license panel handler. If the problem occurs again. If the problem occurs again. If the problem occurs again. If the problem occurs again. If the problem occurs again. contact your next level of support. Reboot the HMC and retry the operation. Error during the main "service" processing for the server side of the change internal code wizard3 panel handler. Error during the main "service" processing for the server side of the change internal code wizard fix details panel handler. The task has been terminated. contact your next level of support. contact your next level of support. Reboot the HMC and retry the operation. Error during the main "service" processing for the server side of the change internal code wizard4 panel handler. If the problem occurs again. contact your next level of support. If the problem occurs again. Reboot the HMC and retry the operation. Error during the main processing for the server side of the hardware upgrade task. contact your next level of support. contact your next level of support. If the problem occurs again. If the problem occurs again. Reboot the HMC and retry the operation. If the problem occurs again. Error during the main "service" processing for the server side of the change internal code wizard1 panel handler. Error during the main processing for the client side of the hardware upgrade task. Error during the main "service" processing for the server side of the change internal code wizard cecconcurrency panel handler. Error during the main "service" processing for the server side of the change internal code wizard2 panel handler. The task has been terminated. If the problem occurs again. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. If the problem occurs again.

contact your next level of support. Reboot the HMC and retry the operation. contact your next level of support. Error during the main "service" processing for the server side of the advanced features subtasklet. Reboot the HMC and retry the operation. If the problem occurs again. If the problem occurs again. Error during processing for the advanced features panel handler. Error during processing for the advanced features select change levels panel handler. contact your next level of support. contact your next level of support. Reboot the HMC and retry the operation. If the problem occurs again. Error during processing for the advanced features fix details panel handler. contact your next level of support. Error during processing for the advanced features confirm panel handler. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. Error during the main "service" processing for the server side of the change internal code wizard leveldetails panel handler. The task is terminated. If the problem occurs again. If the problem occurs again.Reference codes E302F9C6 Reboot the HMC and retry the operation. contact your next level of support. If the problem occurs again. Error during the main processing for the server side of the flash side selection task. contact your next level of support. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. Error during processing for the advanced features implied retrieve panel handler. contact your next level of support. contact your next level of support. If the problem occurs again. Reboot the HMC and retry the operation. E302F9C7 E302F9C8 E302F9C9 E302F9CA E302F9CB E302F9CC E302F9CD E302F9CE E302F9CF E302F9D0 E302F9D1 E302F9D2 254 (1xxx) System power control network (SPCN) reference codes . contact your next level of support. Error during processing for the advanced features retrieve panel handler. Error during processing for the advanced features install type panel handler. Error during processing for the advanced features level details panel handler. Reboot the HMC and retry the operation. If the problem occurs again. contact your next level of support. Error during processing for the advanced features change levels panel handler. If the problem occurs again. If the problem occurs again. Reboot the HMC and retry the operation. If the problem occurs again. If the problem occurs again. If the problem occurs again. Error during the main "service" processing for the server side of the change internal code task. Reboot the HMC and retry the operation.

Error during processing change internal code MainPanel panel handler. Reboot the HMC and retry the operation. If the problem occurs again. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. If the problem occurs again. contact your next level of support. contact your next level of support. contact your next level of support. contact your next level of support. Error during the main processing for the server side of the system information task. contact your next level of support. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. Error during the processing for the server side SysInfoEcTasklet system information subtask. Reboot the HMC and retry the operation. contact your next level of support. Error trying to do the main processing for the client side of the flash side selection task. If the problem occurs again. Error trying to assign values from a SysInfoEcInternalCodeData object. Reboot the HMC and retry the operation. If the problem occurs again. Error during processing change internal code InbandMessage panel handler. The task is terminated. Error during processing change internal code MainRepos panel handler. Error during processing change internal code ChangeFTP panel handler. Error during processing change internal code FtpPanel panel handler. If the problem occurs again. If the problem occurs again. contact your next level of support.Reference codes E302F9D3 Reboot the HMC and retry the operation. contact your next level of support. The task has been terminated. Error from getting null presentation task parameters in the system information task. Reboot the HMC and retry the operation. E302F9D4 E302F9D5 E302F9D6 E302F9D7 E302F9D8 E302F9D9 E302F9DA E302F9DB E302F9DC E302F9DD E302F9DE E302F9DF (1xxx) System power control network (SPCN) reference codes 255 . If the problem occurs again. The task has been terminated. If the problem occurs again. The task is terminated. Reboot the HMC and retry the operation. The task is terminated. contact your next level of support. contact your next level of support. Error trying to do the main processing for the client side of the change internal code task. Error during the main processing for the server side of the advanced features subtask. The task is terminated. The task has been terminated. If the problem occurs again. If the problem occurs again. Reboot the HMC and retry the operation. Error trying to do the main processing for the client side of the non disruptive firmware update task. contact your next level of support. If the problem occurs again. contact your next level of support. If the problem occurs again. The task is terminated. Reboot the HMC and retry the operation. If the problem occurs again. Reboot the HMC and retry the operation.

contact your next level of support. If the problem occurs again. The bean attempts to close the panel. This bean attempts to close the panel. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. If the problem occurs again. Error during the main processing for the server side of the Nondisruptive Firmware Update task. Error in the specify levels bean panelAction method. If the problem occurs again. Reboot the HMC and retry the operation. This bean attempts to close the panel. Error trying to perform some processing in the Advanced Targeting for Frames Bean panelAction() method. contact your next level of support. Error trying to perform some processing in the Advanced Targeting for System Bean panelAction() method. If the problem occurs again. The bean attempts to close the panel. If the problem occurs again. contact your next level of support. Reboot the HMC and retry the operation. (1xxx) System power control network (SPCN) reference codes E302F9E1 E302F9E2 E302F9E3 E302F9E4 E302F9E5 E302F9E6 E302F9E7 E302F9E8 E302F9E9 E302F9EA E302F9EB 256 . Error in the change FTP directory bean panelAction method. Reboot the HMC and retry the operation. Error in the CEC/power concurrency bean panelAction method. Reboot the HMC and retry the operation. The bean attempts to close the panel. This bean attempts to close the panel. If the problem occurs again. This could be the result of an exception being caught by the underlying tasklet infrastructure. This bean attempts to close the panel. If the problem occurs again. Error in the CEC/power level details bean panelAction method. This bean attempts to close the panel. contact your next level of support. Error trying to perform some processing in the Advanced Features Bean panelAction() method. contact your next level of support. Error during the main processing for the server side of the Change Internal Code Wizard subtask. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. If the problem occurs again. contact your next level of support. If the problem occurs again. Reboot the HMC and retry the operation. Error during the main processing for the server side of the advanced targeting subtask.Reference codes E302F9E0 Reboot the HMC and retry the operation. This could be the result of an exception being caught by the underlying tasklet infrastructure. Reboot the HMC and retry the operation. Error in the select advanced targeting type bean panelAction method. This could be the result of an exception being caught by the underlying tasklet infrastructure. Error during the main processing for the server side of the Change Internal Code task. contact your next level of support. contact your next level of support. If the problem occurs again. contact your next level of support. contact your next level of support. If the problem occurs again. Reboot the HMC and retry the operation. If the problem occurs again.

Reboot the HMC and retry the operation. If the problem occurs again. This bean attempts to close the panel. Error in the FTP site access bean panelAction method. Error in the advanced features confirm bean panelAction method. If the problem occurs again. contact your next level of support. Reboot the HMC and retry the operation. contact your next level of support. This bean attempts to close the panel. Reboot the HMC and retry the operation. contact your next level of support. Reboot the HMC and retry the operation. If the problem occurs again. If the problem occurs again. contact your next level of support. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. If the problem occurs again. If the problem occurs again. Reboot the HMC and retry the operation. This bean attempts to close the panel. contact your next level of support. This bean attempts to close the panel. Error in the confirmation level details bean panelAction method. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. Error in the advanced features select installation type bean panelAction method.Reference codes E302F9EC Reboot the HMC and retry the operation. contact your next level of support. 257 E302F9ED E302F9EE E302F9EF E302F9F0 E302F9F1 E302F9F2 E302F9F3 E302F9F4 E302F9F5 E302F9F6 E302F9F7 E302F9F8 (1xxx) System power control network (SPCN) reference codes . contact your next level of support. If the problem occurs again. Error in the advanced features retrieve bean panelAction method. Error in the change internal code main bean panelAction method. If the problem occurs again. Error in the flash side selection bean panelAction method. Error in the license agreement bean panelAction method. If the problem occurs again. This bean attempts to close the panel. This bean attempts to close the panel. This bean attempts to close the panel. contact your next level of support. Error in the LIC details bean panelAction method. contact your next level of support. Reboot the HMC and retry the operation. This bean attempts to close the panel. If the problem occurs again. If the problem occurs again. If the problem occurs again. This bean attempts to close the panel. This bean attempts to close the panel. If the problem occurs again. Error in the nondisruptive firmware update bean panelAction method. Error in the advanced features install and activate (implied retrieval) bean panelAction method. Error in the change internal code main repos bean panelAction method. This bean attempts to close the panel. contact your next level of support. contact your next level of support. contact your next level of support. Error in the inband configuration detected bean panelAction method. This bean attempts to close the panel. This bean attempts to close the panel.

This bean attempts to close the panel. If the problem occurs again. This bean attempts to close the panel. Error in the change internal code wizard2 bean panelAction method. Error in the system information bean panelAction method. Reboot the HMC and retry the operation. contact your next level of support. If the problem occurs again. E302FA02 Ensure that the entire repair and verify procedure executed correctly and that the new service processor is communicating properly. Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. contact your next level of support. If the problem occurs again. contact your next level of support. An error occurred while attempting to create a targeted service processor object during a repair and verify operation. contact your next level of support. Ensure that the entire repair and verify procedure executed correctly and that the new service processor is communicating properly. contact your next level of support.Reference codes E302F9F9 Reboot the HMC and retry the operation. Reboot the HMC and retry the operation. Error in the change internal code wizard3 bean panelAction method. Reboot the HMC and retry the operation. If the error continues to occur. If the problem occurs again. E302FA00 Ensure that the entire repair and verify procedure executed correctly and that the new service processor is communicating properly. If the error continues to occur. If the problem occurs again. contact your next level of support. contact your next level of support. contact your next level of support. This bean attempts to close the panel. An error occurred while attempting to determine which service processor is the source and which one is the destination for a repair and verify operation. Error in the change internal code wizard4 bean panelAction method. This bean attempts to close the panel. If the error continues to occur. E302F9FF E302FA01 E302FA03 to E302FFFF 258 (1xxx) System power control network (SPCN) reference codes . Error in the change internal code wizard1 bean panelAction method. If the problem occurs again. If the problem occurs again. contact your next level of support. Error in the advanced features select level bean panelAction method. Error in the select advanced targeting frame choice bean panelAction method. This bean attempts to close the panel. contact your next level of support. This bean attempts to close the panel. Licensed Internal Code failure on the HMC. contact your next level of support. E302F9FA E302F9FB E302F9FC E302F9FD E302F9FE Reboot the HMC and retry the operation. If the problem occurs again. Contact your service provider. This bean attempts to close the panel. Reboot the HMC and retry the operation. An error occurred while attempting to synchronize one service processor to the other during a repair and verify operation.

Retry the operation 3. This error occurs when the HMC receives notification that a particular Java code string is corrupted. (E332) Licensed Internal Code error codes Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items The HMC failed to retrieve a platform system dump from the managed E3326601 system. If you have the call home feature enabled. the media being formatted may be defective. The HMC failed to retrieve a dump from the service processor. If it still fails. (E332) Licensed Internal Code error codes Table 1. 2. (E338) Licensed Internal Code error in guided maintenance in Service Focal Point An error occurred during the initialization of the components required for performing guided maintenance from Service Focal Point. Licensed Internal Code failure on the HMC. (E338) Licensed Internal Code error in Guided Maintenance in Service Focal Point Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items An error occurred during the initialization of the components required for E3380001 NEXTLVL performing guided maintenance from Service Focal Point. For details. Try a different media.Reference codes (E303) Formatting media error codes Table 1. refer to reference code B3036604. refer to reference code B3036601. (E303) Formatting media error codes Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items Format Media application had an error trying to display a format message panel on the screen. Exit or Cancel the Format Media application. Perform the following steps: E3033011 1. For E33326602 details. E3380004 Contact your service provider. Licensed Internal Code failure on the Hardware Management Console (HMC). An error occurred during the initialization of the components required for E3380002 NEXTLVL performing guided maintenance from Service Focal Point. refer to reference code B3036601. Table 1. For details. (1xxx) System power control network (SPCN) reference codes 259 . The support organization will examine the JavaCore file. you can retry the task. E3380003 Contact your service provider. E332FFFF the failure information (including the JavaCore) will be transmitted to service and support. Check the media to see if it is inserted correctly. Otherwise. The HMC failed to retrieve a power subsystem dump from the managed E3326604 system. 2. Retry the operation Format Media encountered a problem accessing the removable media it is trying to format. Perform the following steps: E303300D 1.

The settings task has been ended. An error log is created to determine which code failed to handle the exception. There was an IO exception on the socket communication between a client and the manager. 260 (1xxx) System power control network (SPCN) reference codes . Depending on the type of E3550037 exception. Look at the logged E355049F exception for information about the error. An out of memory exception has been caught in the Java Virtual Machine (JVM). E3550046 The secondary data block with ID "81" should be analyzed to determine the code that is in error. E3550550 Error found in the EventSummary tasklet. An error log is created to determine which code failed to handle the exception. Error trying to do the main processing for client side of the network settings task. but it may not function as expected. An uncaught exception has been caught by the thread group. Anything that causes a socket communication exception can cause this log entry. Although it is possible the out of memory condition will correct itself. Error performing processing in the settings task action handler. Error trying to do the main processing for server side of the settings E3550950 task. but it may not function as expected. This is the result of an exception being caught by the E3550956 underlying Tasklet infrastructure. This is the result of an exception being caught by the underlying Tasklet infrastructure. E3550959 The network settings task will likely continue to run. The client or manager programs E3550832 might have ended abruptly or the connection between the two might have been physically broken. Exception caught in updateChildrenOfGroup (). E3550551 Error reading the log file. The network settings task has been ended. In addition to the log being created. Examine the actual exception to E3550830 determine the source and severity of the problem.Reference codes (E355) errors Table 1. Examine the actual IO exception and the environment in which it occurred to determine the source and severity of the exception. E355095C Error performing a firewall operation. the task might terminate. Error with configuration data. a dump of the JVM E355004D has been forced for this condition as well. The secondary E3550423 data block with ID "81" should be analyzed to determine the code that is in error. An error occurred when updating the console tasks performed E3550996 information. The E3550958 settings task will likely continue to run. the console application will be restarted by problem analysis when this problem is analyzed. Error launching a task. An unexpected internal error occurred. An error log is created to determine why the task E3550813 cannot be launched. Error performing processing in the network settings task action handler. (E355) errors Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items Error initializing and or running a task. An uncaught exception has been caught. An error log is created to determine which E3550790 configuration data is in error. E3550792 Error persisting an object or reading an object from persistence.

Reference codes (E35A) HMC code level Table 1. (E36C) HMC scheduled task errors Reference Code Description/Action Perform all actions before exchanging Failing Items An error occurred during tasklet processing. The PersistenceManager cannot reconstitute an object from the persistent data store. For E35F000 example. The object is invalidated and subsequent calls are rejected. the path to the persistent data store could not be created. This error is logged when during the read of an object an error occurs. an exception is thrown for any following calls to the PersistenceManager. Error reading an object by the PersistenceManager.0. That is. The PersistenceManager cannot reconstitute an object from the persistent data store. (E35F) Persistence error codes Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items Error creating a new PersistenceManager. This error is logged when the constructor of the PersistenceManager is called but the PersistenceManager object could not be initialized correctly. This error is logged when during the reconstitution the required constructor to create a Persistable from PersistentData was not found. For details. Contact your next level of E36C0101 support. E35A003 Check your HMC machine code level and update it to a minimum of 9FEAA097 V4. The E35F0010 PersistenceManager cannot reconstitute an object from the persistent data store. Error reconstituting an object by the PersistenceManager. Your HMC restarts but the code it is running is Version 4 R4 or earlier. Failing Item (E35F) Persistence error codes Table 1. (E36C) HMC scheduled task errors Table 1. The PersistenceManager cannot reconstitute an object from the persistent data store.R5. The class object that was not found is the object describing the stored PersistentData or Persistable. see Determining your HMC machine code version and release. E36C0103 Contact your next level of support. Error reconstituting an object by the PersistenceManager. Retry the task. This error is logged when during the reconstitution an unsupported version of the 261 E35F0012 E35F0013 E35F0014 (1xxx) System power control network (SPCN) reference codes . (E35A) HMC code level error Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items E35A003 The code did not function as designed. This error is logged when during the reconstitution a class object was not found. Error decoding an object by the PersistenceManager. E35F0011 This error is logged when during the decoding of an object an error occurs (the error is usually an IOException). Error reconstituting an object by the PersistenceManager. An error occurred while working with persisted scheduled operations.

check the logs.trm file. The current code does not support this version. perform tests on the media device to see whether the device is defective. Try to determine which media device reported this failure.mount files in /tmp/console/mediasvc to determine which device failed and for which of the reasons previously listed reasons. A parsing error occurred trying to parse the xml files representing deployment preferences. Determine what specific task was being performed when the error occurred. Error performing the restoreUpgradeData method. Look in the trace for a description of the parsing error that occurred. 3. E35F0032 (E3CA) Error regarding a media device Table 1. including diskette. 6. or memory stick. (E3CA) Error regarding a media device Reference Code Description/Action Perform all actions before exchanging Failing Items E3CA026B An error occurred mounting a media device for one of the following cases: • An unknown reason. This error is logged when during the encoding of an object an error occurs (the error is usually an IOException). The PersistenceManager cannot create the encoded form for an object. Error encoding an object by the PersistenceManager. The PersistenceManager cannot reconstitute an object from the persistent data store. The xml files reside in the directory named by the "deploymentPrefs" file control nickname. there are also XMDA entries in the iqzdtrac. 5. The parsing occurs the first time a call is made to Deployment. If necessary. Retry the task with new or reformatted media to see if that solves the problem. This error is logged when during the saveUpgradeData task an error in the PersistenceManager occurs. Error performing the saveUpgradeData method. Error writing an object by the PersistenceManager. When you know which media device failed. The object to be reconstituted was written by a different version of the PersistenceManager. If the problem does not appear to be with removable media. CD. The PersistenceManager cannot reconstitute an object from the persistent data store.log or for . 2. 262 (1xxx) System power control network (SPCN) reference codes Failing Item .getPreferences(). This error is logged when during the restoreUpgradeData task an error in the PersistenceManager occurs. • The mount command reported an incorrect major or minor number Perform the following steps: 1.Reference codes E35F0020 E35F0021 E35F0030 E35F0031 PersistenceManager code was detected. The log contains additional information on the error. The log contains additional information on the error. determine whether there were problems with the removable media. DVD. Check for entries in the /tmp/console/mediasvc/mediascvs. • The device is mounted and cannot be unmounted. If tracing was also running. 4. This error is logged when during the write of an object an error occurs.

5.log or for . Perform the following steps: E3CA026C E3CA0274 E3CA0278 (1xxx) System power control network (SPCN) reference codes 263 . unknown error occurred. Note: The media services log file is stored in the /tmp folder and is lost when the HMC is rebooted. Other than unexpected Java exceptions. there are also XMDA entries in the iqzdtrac.log to show details on how the format failed. Otherwise it reports an IOException "the unmount operation failed. Note: The media services log file is stored in the /tmp folder and is lost when the HMC is rebooted. or memory stick. perform tests on the media device to see whether the device is defective. the media device code reports this exception when it gets a non 0 return code from running the unmount media script: if it gets rc = 203. An error occurred while trying to unmount a media device." 2. If tracing was also running. return code = 203". Check for entries in the /tmp/console/mediasvc/mediascvs. Ensure that the new or different DVD is the same type of DVD as the one that failed to format. If tracing was also running. 1. If necessary. 6. If the problem does not appear to be with removable media. 4. Other than unexpected Java exceptions. An error occurred formating a USB flash memory drive. When you know which media device failed. return code = x" where x is the return code from the unmount script. If the problem does not appear to be with DVD media. check the logs. CD. determine whether there were problems with the removable media.log before rebooting. 4. the media device code reports this exception when it gets an error running the format dvd script and will report a MediaDeviceException "Failure to format media. there are also XMDA entries in the iqzdtrac. Be sure to first save the /tmp/console/mediasvc/mediasvcs. 3. 5. Try to determine which media device reported this failure.Reference codes Note: The media services log file is stored in the /tmp folder and is lost when the HMC is rebooted. 8. Try the format operation with a new or different DVD to see if the problem is due to the DVD media itself.log before rebooting. Retry the task with new or reformatted media to see if that solves the problem. Be sure to first save the /tmp/console/mediasvc/mediasvcs. 7. Determine what specific task was being performed when the error occurred. Check the console log entry to see if an exception was reported for this problem. you might need to reboot the HMC to release that device and the media. 3. Check the console log entry to see what exception was reported for this problem. perform tests on the media device to see whether the device is defective. If there is removable media in the device that cannot be removed (such as a DVD that will not eject). This means the unmount script could not be run with root privileges. you might need to reboot the HMC to release that device and the media.trm file. If there is DVD media in the DVD device that cannot be ejected. An error occurred formatting a DVD.mount files in /tmp/console/mediasvc to determine which device failed and for which of the previously listed reasons. 2. Check for entries in the /tmp/console/mediasvc/mediascvs. including diskette. Perform the following steps: 1. most likely a USB memory stick.trm file. DVD. it reports a MediaDeviceException "runAsRoot setuid error.

An error occurred mounting a media device for one of the following cases: • An unknown reason • The device is mounted and cannot be unmounted • The mount command reported an incorrect major or minor number Perform the following steps: 1. check the logs. 5. If tracing was also running.Reference codes 1. Check for entries in the /tmp/console/mediasvc/mediascvs.log or for . Check for entries in the /tmp/console/mediasvc/mediascvs. Check the console log entry to see what exception was reported for this problem. 4. Format a new or different USB memory stick to see if the problem is due to the media itself. If the problem does not appear to be with the USB media itself. perform tests on the media device to see whether the device is defective. there are also XMDA entries in the iqzdtrac. 4. including diskette. CD. E3D43104 Error obtaining credentials for the call home request. proceed with whatever the existing protocol is for performing tests on the specific media device itself to see whether the device itself is defective. When you know which media device failed. If tracing was also running. Determine what specific task was being performed when the error occurred.mount files in /tmp/console/mediasvc to determine which device failed and for which of the previously listed reasons. 3. 6. If necessary. (E3D4) Call home errors Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items E3D43100 Error occurred while obtaining from call home request all data required for RETAIN. E3CA027E (E3D4) Call home errors Table 1. 2. 264 (1xxx) System power control network (SPCN) reference codes .trm file. E3D43103 Error returning result for the call home request. Try to determine which media device reported this failure. E3D43105 Error obtaining data needed for credentials for the call home request. Unsupported encoding error occurred while building the RETAIN login E3D43102 information for the call home request. Note: The media services log file is stored in the /tmp folder and is lost when the HMC is rebooted." 2. Note: The media services log file is stored in the /tmp folder and is lost when the HMC is rebooted. Other than unexpected Java exceptions. 3. or memory stick. the media device code reports this exception when it gets an error running the format USB script and will report a MediaDeviceException "Failure to format media. Retry the task with new or reformatted media to see if that solves the problem. determine whether there were problems with the removable media. unknown error occurred.trm file. DVD. there are also XMDA entries in the iqzdtrac.log for details on how the format failed. E3D43101 Error building the RETAIN login information for the call home request. If the problem does not appear to be with removable media.

Retry the task. Error occurred during submission of call home request. (E4xx) Licensed Internal Code progress codes (1xxx) System power control network (SPCN) reference codes 265 .Reference codes E3D43106 E3D43107 E3D43108 E3D43108 E3D4310A E3D4310B E3D4310C E3D4310D E3D4310E E3D4310F E3D46F01 E3D46F10 E3D46F21 E3D46F22 E3D46F23 E3D46F25 E3D46F2D E3D46F2E E3D46F2F E3D46F40 E3D46F41 E3D46F42 E3D46F43 E3D46F46 E3D46F71 E3D46F72 E3D46FB0 E3D46FFF Successful credential password update operation. Remote connection services might have returned an error. Error adding the rsfstatusListener for the call home request. Error occurred communicating with service data receiver. (E3F0) Trace failure Reference Code Description/Action Perform all actions before exchanging Failing Failing Item Items E3F00004 The 'Perform Console Trace' task located in Console Actions encountered an error that caused it to end. Error occurred while formatting the request parameters for RETAIN. Error occurred connecting to RETAIN. Error occurred compacting a file to be sent to RETAIN. (E3F0) Trace failure Table 1. Error occurred sending or receiving from RETAIN. Perform the following steps: 1. Error occurred getting the call home authentication token using system credentials. Error occurred writing a file sent from RETAIN. Error reported from RETAIN for the call home request. 2. Error getting the credentials from persistence for the call home request. Error occurred reading a file to be sent to RETAIN. Error with system authentication using system credentials. Error occurred during remote program execution associated with the call home request. Error occurred while performing local file path query. Table 1. Error occurred while parsing the command from RETAIN for the call home request. Successful system credential update operation. Error occurred writing a file sent from RETAIN. Error occurred during file transfer associated with the call home request. Error occurred retrieving a file to send to RETAIN. Need to update the credentials with new machine information. Successful call home progress update. Information SDR communication progressing. you must be a member of the service representative role. If the problem persists. (E4xx) Licensed Internal Code error codes The Hardware Management Console generates E4xx error codes when it encounters a Licensed Internal Code problem.log to your next level of support for analysis. Note: Do not interrupt the task while it is running. Internal error occurred while calling home. Information RETAIN call home progressing. Successful new credential operation. send the iqyylog. Error occurred executing a command issues from RETAIN. Note: To use the 'Perform Console Trace' task.

the SRC tables contain the following columns: • The Reference Code column contains numbers that represent the unit reference code (URC). the term URC does not apply. characters 1 through 4 of word 1 designate the reference code type and characters 5 through 8 of word 1 designate the URC. Each entry in the list represents the first four characters (the reference code type) of the SRC. If the reference code provided contains only 4 or 6 characters. with numeric characters listed before alphabetic characters. unless it fits one of the following conditions: • An 8-character code that begins with a C (except CB) or D (except DA) is a progress code • An 8-character code that begins with an H is a Hardware Management Console (HMC) error code or message • A 6-character code that begins with a zero (0) and does not include a hyphen is an HMC error code • A code that begins with a number sign character (#) represents an AIX diagnostics message. When the SRC table appears. Failing Item NEXTLVL Using system reference codes System reference codes (SRCs) indicate a server hardware or software problem that can originate in hardware. Perform the action indicated for the URC in the Description/Action column of the table. The tables list URCs in hexadecimal sequence. 2. • The Description/Action column offers a brief description of the failure that this SRC represents. SRC formats SRCs are strings of either six or eight alphanumeric characters. Click the item in the list of system reference codes that matches the reference code type that you want to find. To use the list of system reference codes. When available. typically a table that lists the URCs that are associated with that reference code type. and DAxx) and service processor SRCs (A1xx and B1xx). select the appropriate URC from the first column of the table. in Licensed Internal Code. Note: The SRC tables support only 8-character reference code formats. An SRC identifies the component that detected the error code and describes the error condition. only the first two characters of the SRC indicate the necessary action. • For SRCs displayed on software displays. The entries link to more information. complete the following steps: 1. Using the list of reference codes The list of system reference codes is organized in hexadecimal sequence. the first four characters designate the reference code type and the second four characters designate the URC. 3. or in the operating system. only the first character indicates the necessary action. A reference code that is 6 or 8 characters long and appears in either of the following formats (xxxxxx or xxxxxxxx) is an SRC.Reference codes Reference Code Description/Action Perform all actions before exchanging Failing Items E4xxxxxx Licensed Internal Code failure on the Hardware Management Console (HMC). In these cases. Note: For partition firmware SRCs (AAxx. The characters in the SRC typically represent the reference code type and the unit reference code (URC): • For SRCs displayed on the control panel. with numeric characters listed before alphabetic characters. Unless specified otherwise on a particular SRC page. contact your next level of support for assistance. 266 Using system reference codes . • The Failing Item column represents functional areas of the system unit. A server component generates an error code when it detects a problem. the failing function code links to the FRU that contains this function for each specific system unit. Use the SRC information to identify a list of possible failing items and to find information about any additional isolation procedures. It may also contain instructions for continuing the problem analysis. For partition firmware SRCs that begin with 2xxx. Contact your service provider. BAxx.

For more information. see Using the Service Action Log or use the help function for the SAL view. For more information. Replace all high priority or mandatory FRU or procedure callouts at the same time (as a block). Block replacement of FRUs Sometimes. ♦ Continue to exchange and reinstall the failing items. ♦ Exchange the failing item listed first. Use the following instructions to exchange failing items: Note: Some failing items are required to be exchanged in groups until the problem is solved. If you do not find the reference code that you are looking for in this list.SRC: • Advanced System Management Interface (ASMI): The ASMI shows a priority with each callout in the log. • Service Action Log: In the SAL. Finally. if the problem still persists after replacing or performing all the medium priority callouts. see Using service request numbers. see Block replacement of FRUs. • 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 • Hardware Management Console (HMC): In the Service Focal Point on the HMC. The priorities of the FRU and procedure callouts are shown in the following ways. or C. then replace or perform the low priority FRU or procedure callouts one at a time. multiple FRUs or procedures are called out for replacement by an SRC listed in the service action log (SAL). 3. List of service request numbers The service request number (SRN) list is in numeric order. Do the following: 1. exchange the failing items or parts listed in the Failing Item column in the order that they are listed. means that you need to replace all the FRUs or procedures in that group at the same time (as a block). Each FRU or procedure has a priority. refer to the List of system reference codes. and so on. ♦ If exchanging the first failing item does not correct the problem. For more information about how to interpret the part action code. shown with an A. from highest to lowest priority. one at a time. If the problem persists after replacing or performing the high priority callouts. the view of the problem data for a serviceable event displays the FRU replacement priority as High. If the table entry does not indicate an action or if performing the action does not correct the problem. until the problem is corrected. even if the problem appears to have been repaired. reinstall the original item and exchange the next failing item listed. and procedures are always in priority order. B. For information about using this list of SRNs and about SRNs in general. then replace or perform the medium priority FRU or procedure callouts one at a time unless a medium grouping priority is associated with the callout. 2. ask your next level of support for assistance. Other failing items are flagged as mandatory exchange and must be exchanged before the service action is complete. Medium. ask your next level of support for assistance. depending on how you view the SAL. If exchanging the failing items does not correct the problem. A medium grouping priority.Reference codes 4. • Five-Digit SRNs 10104 through SSA03 • SRNs 101-000 through 59D-xxx • SRNs 60B-xxx through 69D-203 Block replacement of FRUs 267 . the Part Action for the FRU in the view of the event shows the replacement priority.

Async code 06 was received. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Async code 02 was received. Async code 06 was received. a software error occurred. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. An SSA Threshold Exceeded link error was detected. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Async code 03 was received. A format operation ended before it completed. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Disk drive module error. an x represents a digit 0 through F. This code indicates that a disk drive module detected the loss of redundant power or cooling. An open SSA loop was detected. Probably. This code indicates that multiple disk drive modules detected loss of redundant power or cooling. Format Degraded. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User's Guide and Maintenance Information for the SSA adapter. Failing Function Codes Description and Action Format in progress. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User's Guide and Maintenance Information for the SSA adapter. Async code 04 was received. Probably. Probably. a software error occurred. Note: In this SRN. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User's Guide and Maintenance Information for the SSA adapter. Async code 05 was received. Abbreviation in Table PAA AA SSA Address Service Request Number 10104 10112 SRN Src.Reference codes • SRNs 700-xxx through 7C1-117 • SRNs 801-xxxx through 899-xxx • SRNs 900-001 through xxxxxxxx • SRNs A00-FF0 through A25-001 • SRNs 2512-101 through 25D0-108 • SRNs 2600-101 through 2640-136 • SCSI Devices SRNs (ssss-102 to ssss-640) Five-Digit SRNs 10104 through SSA03 Replace FRU parts in the order by which the "Failing Function Codes" are listed. List of service request numbers Definition P Adapter port number 1xxxx 20PAA 21PAA to 29PAA 2A002 2A003 2A004 2A005 2A006 2A106 268 . a software error occurred. This code indicates that a disk drive module detected the loss of redundant power or cooling. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive.

Excessive link reconfigurations were detected. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User's Guide and Maintenance Information for the SSA adapter. The disk drive might be going to fail. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The disk drive was reset by the adapter. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User's Guide and Maintenance Information for the SSA adapter. A module on the adapter card failed. A module on the adapter card failed. A module on the adapter card failed. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An async code that is not valid was received. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. A module on the adapter card failed. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A module on the adapter failed. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A module on the adapter card failed. An SCSI status that is not valid was received. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. A module on the adapter card failed. A disk drive Microcode Error was detected. A disk drive module detected the loss of redundant power or cooling.Reference codes 2A206 2FFFF 300C0 301C0 303FE 303FF 31000 33PAA 40000 40004 40008 40016 40032 40064 40128 41004 41008 41016 41032 List of service request numbers Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A disk drive module detected that one of its SSA links failed the POST. 269 . Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. A module on the adapter card failed. A module on the adapter card failed. Multiple disk drive modules detected the loss of redundant power or cooling. The SSA adapter card failed.

Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The supply voltage to the fast-write cache option card is low. A module on the adapter card failed. This adapter does not support the SSA Fast-Write Cache Option. An SSA fast-write cache option card failure was detected. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An SSA fast-write cache failure was detected. The fast-write cache is disabled. A fast-write disk drive (or drives) contains unsynchronized data. A module on the adapter card failed. A fast-write SSA disk drive has been detected that was previously unsynchronized. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. but the fast-write cache option card cannot be detected. but has since been configured on a different adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An SSA adapter is attempting to use its fast-write cache. Other adapters on the SSA loop are using levels of microcode that are not compatible.Reference codes 41064 41128 42000 42200 42500 42510 42515 42520 42521 42522 42523 42524 42525 42526 42527 42528 42529 4252A A module on the adapter failed. Not enough DRAM available to run an SSA fast-write cache. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. List of service request numbers 270 . Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The card has switched to Self-Refresh mode. The battery is charging. A fast-write problem occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A incorrect version number was detected in the fast-write cache option card. but a fast-write cache card is not installed. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A module on the adapter card failed. A dormant SSA fast-write cache entry exists. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An SSA adapter detected a failure in its fast-write cache. An SSA fast-write cache option card failure was detected. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter.

Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive or to the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The array filter detected a link configuration that is not valid. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive or to the User's Guide and Maintenance Information for the SSA adapter. A disk drive module has a Failed status. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A RAID array is in the Off-Line state because more than one disk drive is not available. An attempt was made to store in the SSA adapter the details of more than 32 RAID arrays. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Action: Refer to the SRN table in the User's Guide and 271 List of service request numbers . One member disk drive of an array is not on the SSA loop that contains the other member disk drives of the array. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The SSA adapter detected a link configuration that is not valid. An SSA device on the loop is preventing the completion of the loop configuration. One cache. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The SSA adapter has detected an open SSA loop. An array is in the Off-Line state because the split/join procedure was not performed correctly. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The battery to the fast-write cache option card needs to be exchanged for a new one. An array is in the Off-Line state because the primary or secondary half of the array is not present. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive or to the User's Guide and Maintenance Information for the SSA adapter. Two or more member disk drives of an SSA array are on different loops. A member disk drive is missing from a SSA array or the original SSA adapter is not available.Reference codes 4252B 4252C 42540 43PAA 44PAA 45PAA 46000 46500 47000 47500 48000 48500 48600 48700 48750 48755 48760 The battery to the fast-write cache option card no longer has the power to maintain data. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Two-way fast-write cache is configured to operate only when both caches are available. is not available. however. Part of the RAID array data might have been lost. The SSA adapter is unknown to the array. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter.

Reference codes

48800 48900 48950 49000 49100

49500

49510 49520

49530

49540 49700 49800 4A100

4BPAA

50000 50001 50002 50004 50005 50006

Maintenance Information for the SSA adapter. The Invalid-Strip table is full. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An SSA array is not available; a multiple-device error occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A disk drive caused an Array-Build operation to fail. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A RAID array is in the Degraded state. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A RAID array is in the Exposed state. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. No hot-spare disk drives are available for an array that is configured for hot-spare disk drives. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Hot-spare configuration is not synchronized. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Hot-spare tuning has been lost. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The number of disk drives that remain in a hot-spare pool is less than the specified number. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Adapters that do not support hot-spare pools were detected. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The parity for the RAID array is not complete. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A different adapter was detected on each loop. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The adapter cannot initialize an SSA disk drive. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An SSA disk drive at PAA cannot be configured, because its UID cannot be read. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The SSA adapter failed to respond to the device driver. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A Data Parity error occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An SSA adapter DMA error occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A Channel Check occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A software error occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. A Channel Check occurred. Action: Refer to the SRN table in the User's Guide and
List of service request numbers

272

Reference codes

50007

50008

50010 50012 50013

50100

50200 50411 50422 50425 504xx 60000

60200

60210

60220

60230

Maintenance Information for the SSA adapter. The IOCC detected an internal error. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Unable to read or write the POS registers or PCI configuration space. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An SSA adapter or device-driver protocol error occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The SSA adapter microcode hung. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The SSA adapter card failed. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An attempt was made to log an error against a pdisk that is not available to the using system. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Duplicate SSA cluster number detected. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. SSA adapter detected a SS_SIC_CLASS1 error. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. SSA adapter detected a SS_TIMEOUT error. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. SSA adapter detected a SS_LINK_CONFIG_FAILED error. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The SSA adapter microcode hung. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The SSA adapter is missing from the expected configuration. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The SSA unit cannot be turned on. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself), use the SRN table in the system unit's service guide to find this SRN and do the action indicated there. A disk drive module has its Check light On. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself), use the SRN table in the system unit's service guide to find this SRN and do the action indicated there. A fan-and-power-supply assembly has its Check light On. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself), use the SRN table in the system unit's service guide to find this SRN and do the action indicated there. The SSA unit has an unexpected Check light On. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model
273

List of service request numbers

Reference codes

60240

7xxxx

8xxxx

D0000 D0100

D0101

D0200

D0300

D0400

D0450

D0460 D4000 D4100 D4300

D44xx D6PAA

type from the system unit itself), use the SRN table in the system unit's service guide to find this SRN and do the action indicated there. An SSA configuration problem occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter or if the system service guide contains integrated SSA (without a distinct model type from the system unit itself), use the SRN table in the system unit's service guide to find this SRN and do the action indicated there. An SSA disk drive is missing from the expected configuration of the SSA loop. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and to the User's Guide and Maintenance Information for the SSA adapter. Note: In this SRN, an x represents a digit 0 through F. A Configuration Error occurred. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Note: In this SRN, an x represents a digit 0 through F. The using system cannot configure the disk drive module. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. Unable to clear a disk drive module reservation. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. The disk drive module has been reserved since the diagnostics started. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. The disk drive module timed out while the diagnostics were running. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. The disk drive module failed the diagnostic test. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. The disk drive module is Not Ready while the diagnostics are running. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. The Format operation that was started on this disk drive module has not finished. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. A Format operation was degraded. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive. The diagnostics cannot configure the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The diagnostics cannot open the SSA adapter. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The diagnostics have detected an SSA adapter POST failure. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The diagnostics detected that the SSA adapter has corrupted microcode, but cannot download a new version of the microcode. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. Note: In this SRN, an x represents a digit 0 through F. A high-speed SSA link is running at low speed. Action: Refer to the SRN table in the User's Guide and
List of service request numbers

274

Reference codes

DFFFF

SSA01

SSA02 SSA03

Maintenance Information for the SSA adapter. Note: The description and action for this SRN are valid only if you ran the diagnostics on the SSA attachment. A command or parameter that was sent or received is not valid. Action: Refer to the SRN table in the Service Guide for the unit containing the disk drive and to the User's Guide and Maintenance Information for the SSA adapter. There is not enough using-system memory available for this service aid to continue. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. An unknown error occurred. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter. The service aid was unable to open a hdisk. Action: Refer to the SRN table in the User's Guide and Maintenance Information for the SSA adapter.

SRNs 101-000 through 59D-xxx

Replace FRU parts in the order by which the "Failing Function Codes" are listed. Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-). Service Request Number 101-000 101-185 101-517 Failing Function Codes Description and Action The system hung while attempting to configure a device. Action: Use PFW1540: Problem isolation procedures. A checkstop occurred. Action: Use PFW1540: Problem isolation procedures. The system unit failed to IPL. Action: Use PFW1540: Problem isolation procedures. CD-ROM read problems after boot. Note: The boot record was read from the CD-ROM disk. However, errors occurred when trying to mount the CD-ROM file system. This problem can be caused by SCSI device addressing, SCSI terminator, open PTC, SCSI cable, etc. Action: Go to SCSI Bus Problems. The configuration manager detected an error. Action: If you are running the diagnostics from a disk, try running standalone diagnostics. If standalone diagnostics run correctly, the problem may be damaged data on the disk. Contact your software support facility. If a different problem occurs when you run standalone diagnostics, correct that problem. If you were running standalone at first, have the same problem running standalone diagnostics that you had when running diagnostics from disk, or these actions did not resolve the problem, go PFW1540: Problem isolation procedures. Disk read problems occurred after booting. Note: The boot record was read from the disk. However, errors occurred when trying to open the disk drive. This problem can be caused by SCSI device addressing, SCSI terminator, open PTC, SCSI cable, etc. Action: Go to SCSI Bus Problems. The system hung while loading the software. This can be caused by a hardware or software problem. Action: Run the standalone diagnostics. If the standalone diagnostics run correctly, the problem may be a damaged disk data. Consider having the customer contact Software Support before reinstalling the operating system on the disk. Otherwise, go to Problem determination procedure. If a different problem occurs when you run the standalone diagnostics, correct that problem. If the standalone diagnostics still produces the same SRN, go to PFW1540: Problem isolation
275

101-518

101-521 to 101-538

101-544 101-551 to 101-557

List of service request numbers

Reference codes

101-558

101-559 to 101-599

procedures. There is not enough memory to execute diagnostics. Action: There must be a minimum of 16 MB of installed memory. If the system has 16 MB or more of memory installed, suspect a problem with a memory card. The system halted while software was loading. This problem may be attributed to either hardware or software. Action: Use the standalone diagnostics if not yet used. If the same SRN is generated from standalone diagnostics, go to PFW1540: Problem isolation procedures for problem isolation. If a different problem occurs when you run the standalone diagnostics, correct that problem. If the SRN is not generated running standalone diagnostics, suspect a problem with the system's software. An unexpected system interrupt. Action: Use PFW1540: Problem isolation procedures. The system hung while trying to configure an unknown resource. Action: Run standalone diagnostics. Start at Problem determination procedure, Step 14. If you still get the same SRN, refer to Failing Function Code List and find the FFC that matches the last three digits of the SRN. Suspect the device adapter or device itself. If more than one adapter or device is installed, isolate the failing resource by removing the adapters or devices one at a time and checking if the system stops with the same value in the three-digit display. Note: xxx corresponds to the last three digits of the SRN. The system hung while trying to configure an asynchronous adapter. Action: Use PFW 1540: Problem isolation procedures. Suspect a problem with one of the async adapters. The system unit halted while configuring an audio subsystem. Action: Go to General problem resolution. A potential problem with an SSA device exists. If the system has external SSA devices refer to the SSA Adapters User's Guide and Maintenance Information. If the system has internal SSA devices, go to the SSA MAP in either the system unit's service guide or user's guide. An unexpected system interrupt. Action: Use PFW 1540: Problem isolation procedures. Suspect either a SCSI adapter or integrated SCSI if so equipped. The system does not IPL. Action: Go to General problem resolution. The system hung while indicating that a direct-attached display was selected as the console. Action: Use PFW 1540: Problem isolation procedures. Suspect the graphics adapter being used for the display console first. The system hung while indicating that a TTY terminal is the system console. Action: Use PFW 1540: Problem isolation procedures. Suspect the graphics adapter being used for the display console first. A problem was encountered mounting the CD-ROM. Action: Use PFW 1540: Problem isolation procedures. Maximum memory size of partition is too large with respect to the current partition memory size. Action: Specify a maximum memory size for the partition no larger than 64 times the starting memory size of the partition. The system hung while trying to configure the Infiniband communication manager. This problem may be attributed to software. Action: Report this problem to the AIX support center. The system hung while trying to configure the Infiniband TCP/IP interface. This problem may be attributed to software. Action: Report this problem to the AIX support center. The system hung while configuring a resource. The last three or four digits after the dash (-) identify the failing function code for the resource being configured.
List of service request numbers

101-662

101-711 to 101-726

xxx

101-727 101-7C1 101-80c 7C1 80c

101-840 101-888 210 227 E10

101-c32

101-c33 101-c70 101-2004

101-2020 101-2021 101-xxxx xxxx E10

276

Reference codes

103-151 109-200 110-101

151

Action: Go to System hangs during resource configuration. The time-of-day battery failed. Action: Go to General problem resolution. The system crashed while being run by the customer. Action: Use Problem determination procedure, and get a new SRN. The diagnostics did not detect an installed resource. Action: If this SRN appeared when running concurrent diagnostics, then run concurrent using the diag -a command, otherwise use Missing resource problem resolution. The system halted while diagnostics were executing. Action: Go to General problem resolution. The system halted while diagnostics were executing. Note: xxx corresponds to the last three digits of the SRN. Action: Go to General problem resolution. The system halted while diagnostics were executing. Action: Go to General problem resolution. The system halted while diagnostics were executing. Action: Go to General problem resolution. The system halted while diagnostics were executing. Note: xxxx corresponds to the last three or four digits of the SRN following the dash (-). If your 110 SRN is not listed, substitute the last three or four digits of the SRN for xxxx, then proceed to the FFC table using the substituted digits as your FFC.. Action: Go to General problem resolution. A machine check occurred. Action: Go to Problem determination procedure. An encoded SRN was displayed. Action: Go to Problem determination procedure. There is a display problem. Action: Do problem determination on the display. Action: Go to General problem resolution. Cannot display readable information on the terminal. Action: Go to Console and keyboard problem resolution Entry 3. Cannot display readable information on the display. Note: Suspect the display adapter attached to the console display. Action: Go to Console and keyboard problem resolution. The keyboard does not respond. Action: Go to Console and keyboard problem resolution Entry 1. I/O bus problem. Action: Go to General problem resolution. Note: PCI adapter refers to the adapters you made note of when using Console and keyboard problem resolution. Cannot display readable information on the display. Action: Go to Console and keyboard problem resolution Entry 2. The keyboard does not respond. Action: Go to Console and keyboard problem resolution Entry 1. The keyboard does not respond. Action: Go to Console and keyboard problem resolution Entry 1. The keyboard does not respond. Action: Go to Console and keyboard problem resolution Entry 1. System beeper not functioning correctly. Action: Go to General problem resolution. System does not perform a soft reset. Action: Go to General problem resolution. A critical failure has occurred on an undefined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. Non-critical failure has occurred on an undefined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. An unrecoverable failure has occurred on an undefined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A critical power supply failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START.
277

110-908 110-921 to 110-926 110-935 110-946

908 C33 C36 xxx 812 935 812 946 221

110-xxxx

xxxx 221

111-107 111-108 111-121 111-259 111-725 111-736 111-78C 111-82C 111-921 111-922 111-923 111-947 111-999 199-102 199-103 199-104 199-122 921 821 922 821 923 821 221 210 199 199 199 152 725 736 821 PCI adapter 227 E10

List of service request numbers

Reference codes

199-123 199-124 199-132 199-133 199-134 199-148 199-149 199-152 199-153 199-154 199-162 199-163 199-164 199-172 199-173 199-174 199-182 199-183 199-184 199-192 199-193 199-194 199-201 199-202 199-203 199-204 199-205 2E6-101 2E6-102 2E6-103 2E6-212
278

152 152 166 199 166 199 166 199 166 199 166 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 199 891 199 891 199 891 152 166 152 166 221 293 2E6 221 2E6

A non-critical power supply failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. An unrecoverable power supply failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A critical fan failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A non-critical fan failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. An unrecoverable fan failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. The enclosure indicates a temperature threshold warning. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. The enclosure indicates a temperature threshold failure. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A critical repeater card failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A non-critical repeater card failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. An unrecoverable repeater card failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A critical VPD module failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A non-critical VPD module failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. An unrecoverable VPD module failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A critical enclosure services failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A non-critical enclosure services failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. An unrecoverable enclosure services failure has occurred. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A critical failure has occurred on a user defined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A non-critical failure has occurred on a user defined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. An unrecoverable failure has occurred on a user defined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A critical failure has occurred on a user defined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. A non-critical failure has occurred on a user defined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. An unrecoverable failure has occurred on a user defined element. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. Device configuration error. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. The enclosure failed to open. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. The enclosure failed to return inquiry data. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. There is a critical power supply or fan failure. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. There is a redundant power supply or fan failure. Action: Go to MAP 2010: 7031-D24 or 7031-T24 START. Enhanced error handling failure on the bus. Action: Go to General problem resolution. Enhanced error handling failure on a PCI-PCI Bridge. Action: Go to General problem resolution. Enhanced error handling failure on the adapter. Action: Go to General problem resolution. FIFO empty bit set. Action: Go to General problem resolution.
List of service request numbers

Reference codes

2E6-213 2E6-214 2E6-215 2E6-216 2E6-217 2E6-218 2E6-219 2E6-220 2E6-221 2E6-222 2E6-223 2E6-224 2E6-225 2E6-226 2E6-227 2E6-230 2E6-231 2E6-232 2E6-240 2E6-242 2E6-301 2E6-701 2E6-801

2E6 2E6 2E6 2E6 2E6 2E6 2E6 2E6 2E6 221 2E6 2E6 2E6 221 2E6

2E6 221

2E6 221 2E6

2E6-802

2E6-803

2E7-101 2E7-102

221 293

FIFO empty bit clear. Action: Go to General problem resolution. FIFO full bit set. Action: Go to General problem resolution. FIFO full bit clear. Action: Go to General problem resolution. FIFO data miscompare. Action: Go to General problem resolution. SCSI FIFO data miscompare. Action: Go to General problem resolution. SCSI FIFO underflow. Action: Go to General problem resolution. SCSI parity error. Action: Go to SCSI bus problems. SCSI FIFO flags error. Action: Go to General problem resolution. Miscompare during the write/read of the configuration register. Action: Go to General problem resolution. Error during the write/read of the memory register. Action: Go to General problem resolution. Miscompare during the write/read of the memory I/O register. Action: Go to SCSI Bus Problems. SCSI configuration register read or write error. Action: Go to General problem resolution. Adapter POST failed. Action: Go to General problem resolution. SCSI wrap or PTC failure. Action: Go to SCSI Bus Problems. SCSI adapter test failure. Action: Go to General problem resolution. Arbitration test failed. Action: Go to SCSI Bus Problems. Function could not complete. Action: Go to SCSI Bus Problems. SCSI bus data miscompare. Action: Go to SCSI Bus Problems. No terminal power. Action: Go to SCSI Bus Problems. SCSI bus problem. Action: Go to SCSI Bus Problems. The parent device open failed. Action: Go to General problem resolution. Error log analysis indicates a PCI SCSI adapter failure. Action: Go to General problem resolution. Error log analysis indicates a terminator problem. Action: Run the diagnostics on the adapter in system verification mode. If an SRN is reported, use the SRN to resolve the problem. If an SRN is not reported, use the SCSI service hints in General SCSI configuration checks to resolve the problem. Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. Action: Run the diagnostics on the adapter in system verification mode. If an SRN is reported, use the SRN to resolve the problem. If an SRN is not reported, use the SCSI service hints in General SCSI configuration checks to resolve the problem. Error log analysis indicates that multiple SCSI bus errors have occurred. Action: Run the diagnostics on the adapter in system verification mode. If an SRN is reported, use the SRN to resolve the problem. If an SRN is not reported, use the SCSI service hints in General SCSI configuration checks to resolve the problem. Enhanced error handling failure on the bus. Action: Go to General problem resolution.
279

List of service request numbers

Reference codes

2E7-103 2E7-212 2E7-213 2E7-214 2E7-215 2E7-216 2E7-217 2E7-218 2E7-219 2E7-220 2E7-221 2E7-222 2E7-223 2E7-224 2E7-225 2E7-226 2E7-227 2E7-230 2E7-231 2E7-232 2E7-240 2E7-242 2E7-301 2E7-701 2E7-801

2E7 221 2E7 2E7 2E7 2E7 2E7 2E7 2E7

2E7 2E7 221 2E7 2E7 2E7 221 2E7

2E7 221

2E7 2E7

2E7-802

2E7-803
280

Enhanced error handling failure on a PCI-PCI Bridge. Action: Go to General problem resolution. Enhanced error handling failure on the adapter. Action: Go to General problem resolution. FIFO empty bit set. Action: Go to General problem resolution. FIFO empty bit clear. Action: Go to General problem resolution. FIFO full bit set. Action: Go to General problem resolution. FIFO full bit clear. Action: Go to General problem resolution. FIFO data miscompare. Action: Go to General problem resolution. SCSI FIFO data miscompare. Action: Go to General problem resolution. SCSI FIFO underflow. Action: Go to General problem resolution. SCSI parity error. Action: Go to SCSI Bus problems. SCSI FIFO flags error. Action: Go to General problem resolution. Miscompare during the write/read of the configuration register. Action: Go to General problem resolution. Error during the write/read of the memory register. Action: Go to General problem resolution. Miscompare during the write/read of the memory I/O register. Action: Go to SCSI Bus problems. SCSI configuration register read or write error. Action: Go to General problem resolution. Adapter POST failed. Action: Go to General problem resolution. SCSI wrap or PTC failure. Action: Go to SCSI Bus problems. SCSI adapter test failure. Action: Go to General problem resolution. Arbitration test failed. Action: Go to SCSI Bus problems. Function could not complete. Action: Go to SCSI Bus problems. SCSI bus data miscompare. Action: Go to SCSI Bus problems. No terminal power. Action: Go to SCSI Bus problems. SCSI bus problem. Action: Go to SCSI Bus problems. Configuration open failed for parent bus. Action: Go to General problem resolution. Error log analysis indicates a PCI SCSI adapter failure. Action: Go to General problem resolution. Error log analysis indicates a terminator problem. Action: Run the diagnostics on the adapter in system verification mode. If an SRN is reported, use the SRN to resolve the problem. If an SRN is not reported, use the SCSI service hints in General SCSI configuration checks to resolve the problem. Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. Action: Run the diagnostics on the adapter in system verification mode. If an SRN is reported, use the SRN to resolve the problem. If an SRN is not reported, use the SCSI service hints in General SCSI configuration checks to resolve the problem. Error log analysis indicates that multiple SCSI bus errors have occurred.
List of service request numbers

Action: Go to MAP 0210: General problem resolution. Internal adapter test failed. See SCSI Devices SRN (ssss-102 through ssss-640). Internal adapter test failed. EEH failure on Eads chip. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. Action: Go to General problem resolution. External wrap test failed on port 0. Action: Go to MAP 0210: General problem resolution. External wrap test failed on port 1. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. Enhanced error handling failure on bus. Action: Go to MAP 0210: General problem resolution. Error log analysis indicates that this adapter has failed to initialize due to enhanced error handling errors. Action: Go to MAP 0210: General problem resolution. Error log analysis indicates a hardware problem. Action: Go to MAP 0210: General problem resolution. If an SRN is not reported. External wrap test failed on port 1. use the SRN to resolve the problem. External wrap test failed on port 1. Enhanced error handling failure on bus. 2C3 444 2C3 444 227 227 444 776 646 776 646 776 646 444 227 444 227 444 227 2C3 444 2C3 444 2C3 444 software 2C3 444 software 444 227 444 227 software 444 227 software 444 227 software 2C3 444 software 2C3 444 software 444 software 444 227 External wrap test failed on port 0. External wrap test failed on port 1. 281 List of service request numbers . Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. If an SRN is reported. Enhanced error handling failure opening the adapter. Action: Go to MAP 0210: General problem resolution. External wrap test failed on port 1. Enhanced error handling failure on adapter. Action: Go to MAP 0210: General problem resolution. Post indicates an adapter failure. Enhanced error handling failure on adapter. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. External wrap test failed on port 0. Action: Go to MAP 0210: General problem resolution. External wrap test failed on port 0. Action: Go to MAP 0210: General problem resolution. External wrap test failed on port 0. External wrap test failed on port 0. Enhanced error handling failure on Eads chip. Action: Go to MAP 0210: General problem resolution.Reference codes 2EF-101 440-xxx to 443-xxx 444-101 444-102 444-103 444-104 444-105 444-106 444-107 444-108 444-201 444-202 444-203 444-204 444-205 444-206 444-207 444-208 444-301 444-302 444-303 444-304 444-305 444-700 444-701 751 Action: Run the diagnostics on the adapter in system verification mode. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. use the SCSI service hints in General SCSI configuration checks to resolve the problem. External wrap test failed on port 1. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution.

Action: Use MAP 0210: General problem resolution. Failure to adhere to this action could result in data being read or written incorrectly or in the loss of data.Reference codes 446-xxx 447-101 447-102 447-103 447-104 447-105 447-106 447-107 447-109 447-110 447-201 447-202 447-203 447-204 447-205 447-701 447-703 447-704 447-705 447 447 447 447 447 447 447 221 447 447 221 447 221 447 221 447 221 447 221 447 221 447 447 447 447-706 451-xxx 453-xxx 458-110 458-120 458-130 458-135 458-140 458-150 458-160 458-169 282 447 458 458 458 media 458 media 458 458 media 458 media 458 media See SCSI Devices SRN (ssss-102 through ssss-640). Enhanced Error Handling Failure on EADs chip. The DMA test failed. The Fibre Channel Adapter configuration failed. Action: Use MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. A parity error has been detected. The Send Diagnostic command failed. The PCI Wrap test failed. Action: Go to MAP 0210: General problem resolution. The adapter must be replaced immediately. Action: Go to MAP 0210: General problem resolution. The Inquiry command failed. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. The Load command failed. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. The Register test failed. Action: Go to MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The SRAM test failed. Error log analysis indicates that an unknown adapter error has occurred. Action: Go to MAP 0210: General problem resolution. Gigabaud Link Module (GLM) Wrap Test Failure. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Internal Wrap test failed. The Unload command failed. The Mode Select command failed. Error log analysis indicates that an error has occurred with the adapter. See SCSI Devices SRN (ssss-102 through ssss-640). The Interrupt test failed. The Reserve command failed. The Send Diagnostic command failed. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Reset test failed. See SCSI Devices SRN (ssss-102 through ssss-640). The Configuration Register test failed. Action: Go to MAP 0210: General problem resolution. Enhanced Error Handling Failure on adapter. It will remain offline until reconfigured or the system is rebooted. This adapter must be replaced and not brought back online. List of service request numbers . Action: Use MAP 0210: General problem resolution. Action: Go to MAP 0210: General problem resolution. The Test Unit Ready command failed. I/O error on a read/write operation. Action: Go to MAP 0210: General problem resolution. Error log analysis indicates that an adapter error has occurred. Action: Go to MAP 0210: General problem resolution. The External Wrap test failed. This adapter was successfully taken offline. Action: Use MAP 0210: General problem resolution. A fatal hardware error has occurred. Action: Use MAP 0210: General problem resolution. Failure to do so could result in data being read or written incorrectly.

Action: Use MAP 0210: General problem resolution. The Mode Select command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The device configuration failed. Action: Use MAP 0210: General problem resolution. The Unload command failed. Write and Compare test failed. The Release command failed. The device configuration failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Mode Select command failed.Reference codes 458-170 458-180 458-185 458-190 458-200 458-210 458-220 458-230 458-240 458-300 458-310 458-320 458-411 to 458-423 458-511 to 458-523 458-611 to 458-623 458-711 to 458-723 459-110 459-120 459-130 459-135 459-140 459-150 459-160 459-169 459-170 459-180 459-185 459-190 458 B88 media 458 media 458 media 458 458 media 458 B88 458 458 458 458 software B88 458 software 458 media 458 B88 software 458 B88 458 B88 software 458 B88 software 459 459 459 media 459 media 459 459 media 459 media 459 media 459 B88 media 459 media 459 media 459 The Read. Action: Use MAP 0210: General problem resolution. An adapter or bus I/O error occurred. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. A reservation conflict occurred. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. A device timeout error occurred. SCSI adapter configuration failed. The Send Diagnostic command failed. The Load command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Mode Select command failed. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. The Openx command failed. Write and Compare test failed. The Send Diagnostic command failed. The Read. Action: Use MAP 0210: General problem resolution. The Unload command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Error log analysis indicates a failure. 283 List of service request numbers . The Unload command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Request Sense command failed. Action: Use MAP 0210: General problem resolution. The Load command failed. The Load command failed. The drive returned bad or non-extended sense data. The Inquiry command failed. The Reserve command failed. Action: Use MAP 0210: General problem resolution.

The device configuration failed. Action: Use MAP 0210: General problem resolution. Error log analysis indicates a failure. SCSI adapter configuration failed. List of service request numbers . The Send Diagnostic command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Inquiry command failed. Action: Use MAP 0210: General problem resolution. The Release command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Unload command failed. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. Write and Compare test failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. The drive returned bad or non-extended sense data. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Reserve command failed. The Unload command failed. The Send Diagnostic command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. An adapter or bus I/O error occurred. Action: Use MAP 0210: General problem resolution. The Mode Select command failed. Action: Use MAP 0210: General problem resolution. The device configuration failed. The Test Unit Ready command failed. The device configuration failed. Action: Use MAP 0210: General problem resolution. The Mode Select command failed. The Request Sense command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Load command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Load command failed. A device timeout error occurred. Action: Use MAP 0210: General problem resolution.Reference codes 459-200 459-210 459-220 459-230 459-240 459-300 459-310 459-320 459-411 to 459-423 459-511 to 459-523 459-611 to 459-623 459-711 to 459-723 45d-110 45d-120 45d-130 45d-135 45d-140 45d-150 45d-160 45d-169 45d-170 45d-180 45d-185 45d-190 45d-200 45d-210 45d-220 45d-230 284 459 media 459 B88 459 459 459 459 software B88 459 software 459 media 459 B88 software 459 B88 459 B88 software 459 B88 software 45d 45d 45d media 45d media 45d 45d media 45d media 45d media 45d B88 media 45d media 45d media 45d 45d media 45d B88 45d 45d Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Openx command failed. Action: Use MAP 0210: General problem resolution. The Read. Action: Use MAP 0210: General problem resolution. The Release command failed. A reservation conflict occurred.

See SCSI Devices SRNs. The drive returned bad or non-extended sense data. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The device configuration failed. SRNs 60B-xxx through 69D-203 Replace FRU parts in the order by which the "Failing Function Codes" are listed. An 8mm 60GB tape device problem has occurred. 285 613 636 636 List of service request numbers . An 8-mm 80-GB VXA-2 tape device problem has occurred. Action: Use MAP 0210: General problem resolution. See SCSI Devices SRNs.Reference codes 45d-240 45d-300 45d-310 45d-320 45d-411 to 45d-423 45d-511 to 45d-523 45d-611 to 45d-623 45d-711 to 45d-723 541-xxx 542-xxx 56B-xxx 56D-xxx 57B-xxx 57D-xxx 58B-xxx 58D-xxx 59B-xxx 59D-xxx 45d 45d software B88 45d software 45d media 45d B88 software 45d B88 45d B88 software 45d B88 software 541 542 The Request Sense command failed. See SCSI Devices SRNs. Service Request Number 60B-xxx 601-xxx 613-xxx 61B-xxx 61D-xxx 61E-xxx 621-xxx 623-xxx 624-xxx 62D-xxx 62E-xxx 636-101 636-102 Failing Function Codes Description and Action See SCSI Devices SRNs. A reservation conflict occurred. Action: Use MAP 0210: General problem resolution. A DLT tape device problem has occurred. See SCSI Devices SRN (ssss-102 through ssss-640). See SCSI Devices SRNs. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. See SCSI Devices SRN (ssss-102 through ssss-640). See SCSI Devices SRNs. See SCSI Devices SRNs. Action: Use MAP 0210: General problem resolution. SCSI adapter configuration failed. See SCSI Devices SRNs. Action: Use MAP 0210: General problem resolution. See SCSI Devices SRN (ssss-102 through ssss-640). The Openx command failed. An adapter or bus I/O error occurred. See SCSI Devices SRNs. See SCSI Devices SRN (ssss-102 through ssss-640). Action: Refer to the 8mm 60GB tape device documentation. Error log analysis indicates a failure. Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-). See SCSI Devices SRNs. EPROM test failure. See SCSI Devices SRN (ssss-102 through ssss-640). See SCSI Devices SRN (ssss-102 through ssss-640). Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. See SCSI Devices SRN (ssss-102 through ssss-640). See SCSI Devices SRN (ssss-102 through ssss-640). A device timeout error occurred. Action: Refer to the DLT tape device documentation.

Enhanced error handling failure on the adapter. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. See SCSI devices SRNs ssss-102 through ssss-640. Action: Use MAP 0210: General problem resolution. External Test Failure. External Test Failure. Enhanced error handling failure opening the adapter. Adapter memory test failure. External Test Failure. Wrap Test Failure.Reference codes 636-103 636-104 636-105 636-106 636-107 636-108 636-109 636-110 636-111 636-201 636-202 636-203 636-204 636-701 638-xxx 639-xxx 63A-xxx to 63F-xxx 640-xxx 643-xxx 644-xxx 646-101 646-102 646-103 646-104 646-105 646-106 646-107 646-108 646-201 646-202 646-204 646-205 286 636 636 636 636 636 636 221 221 636 636 221 636 221 636 221 636 221 636 Adapter SDRAM failure. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on the Eads chip. I/O Test Failure. External Test Failure. Action: Use MAP 0210: General problem resolution. ELA indicates an I/O failure on the adapter. Internal loop-back test failure. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on adapter. See SCSI devices SRNs ssss-102 through ssss-640. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter checksum failure. Action: Use MAP 0210: General problem resolution. Wrap Test Failure. Action: Use MAP 0210: General problem resolution. External wrap test failure. Interrupt test failure. Action: Use MAP 0210: General problem resolution. EEH failure on PCI-PCI bridge chip. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. See SCSI devices SRNs ssss-102 through ssss-640. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter On-card Test Failure. Action: Use MAP 0210: General problem resolution. See SCSI devices SRNs ssss-102 through ssss-640. Action: Run advanced diagnostics with wrap test for this resource to List of service request numbers D46 240 646 646 221 646 646 646 646 646 221 646 221 D46 240 D46 646 . See SCSI devices SRNs ssss-102 through ssss-640. Adapter DMA test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter cache test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on bus. See SCSI devices SRNs ssss-102 through ssss-640. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on the bus. Configuration Register Test Failure. Action: Use MAP 0210: General problem resolution. Adapter buffer test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Hardware failure opening adapter.

See SCSI devices SRNs ssss-102 through ssss-640. Error log analysis indicates that an adapter error has occurred. 650 165 221 software 657 657 software 657 227 657 Monitor/ Cable 657 227 Monitor/ Cable Disk drive configuration failed. Display character test failed. Error log analysis indicates that a Programmed I/O error has occurred. Action: Use MAP 0210: General problem resolution. FIFO empty bit set. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Error log analysis indicates that an adapter check has occurred. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on a PCI-PCI Bridge. External Test Failure. See SCSI devices SRNs ssss-102 through ssss-640. Adapter failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution.Reference codes 646-206 646-302 646-303 240 646 240 D46 221 D46 646 221 240 D46 646 221 646 646 646 221 646 221 646 221 646 646 646-401 646-701 646-702 646-703 646-704 646-705 646-706 646-707 64A-xxx to 64F-xxx 650-xxx 651-140 657-001 657-002 657-003 657-004 obtain a correct problem resolution. External Test Failure. Action: Use MAP 0210: General problem resolution. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter failure. Action: Use MAP 0210: General problem resolution. ELA indicates a command write failure occurred. Display failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. 287 List of service request numbers . Action: Use MAP 0210: General problem resolution Software error. ELA indicates an internal adapter error has occurred. FIFO full bit set. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. Enhanced error handling failure on the adapter. Error log analysis indicates that a DMA failure has occurred. Action: Use MAP 0210: General problem resolution. 657-005 65A-xxx to 65F-xxx 662-101 662-102 662-103 662-212 662-213 662-214 221 293 662 221 662 662 662 Enhanced error handling failure on the bus. Action: Run advanced diagnostics with wrap test for this resource to obtain a correct problem resolution. Adapter failure. Error log analysis indicates that a PCI Bus error has occurred. External Test Failure. Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. FIFO empty bit clear. External Test Failure. Action: Use MAP 0210: General problem resolution.

Action: Go to SCSI Bus Problems. No terminal power. Action: Go to SCSI Bus Problems. Action: Go to SCSI Bus Problems. Action: Use MAP 0210: General problem resolution. If an SRN is reported. Error log analysis indicates that multiple SCSI bus errors have occurred. Action: Use MAP 0210: General problem resolution. If an SRN is not reported. SCSI bus problem. Action: Use MAP 0210: General problem resolution. If an SRN is reported. Action: Go to SCSI Bus Problems. Error during the write/read of the memory register. Action: Go to SCSI Bus Problems. SCSI adapter test failure. Action: Use MAP 0210: General problem resolution. SCSI bus data miscompare. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Function could not complete. Miscompare during the write/read of the memory I/O register. Action: Use MAP 0210: General problem resolution.Reference codes 662-215 662-216 662-217 662-218 662-219 662-220 662-221 662-222 662-223 662-224 662-225 662-226 662-227 662-230 662-231 662-232 662-240 662-242 662-301 662-701 662-801 662 662 662 662 662 662 221 662 662 662 221 662 662 221 662 221 662 662-802 662-803 FIFO full bit clear. SCSI configuration register read or write error. FIFO data miscompare. use the SRN to resolve the problem. The parent device open failed. Action: Go to SCSI Bus Problems. ARTIC960RxD or RxF PCI Adapter Timer test failure. If an SRN is not reported. SCSI FIFO underflow. Arbitration test failed. use the SCSI service hints in General SCSI configuration checks to resolve the problem. Error log analysis indicates a PCI SCSI adapter failure. Action: Use MAP 0210: General problem resolution. If an SRN is reported. Action: Use MAP 0210: General problem resolution. Action: Run the diagnostics on the adapter in system verification mode. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Go to SCSI Bus Problems. SCSI parity error. Action: Go to SCSI Bus Problems. Miscompare during the write/read of the configuration register. Error log analysis indicates a terminator problem. Action: Run the diagnostics on the adapter in system verification mode. If an SRN is not reported. use the SCSI service hints in General SCSI configuration checks to resolve the problem. Action: Use MAP 0210: General problem resolution. SCSI FIFO flags error. Action: Use MAP 0210: General problem resolution. ARTIC960RxD or RxF PCI Adapter Central Processing Unit test failure. use the SCSI service hints in General SCSI configuration checks to resolve the problem. 663-101 663-102 663-103 288 663 C94 C95 663 C94 C95 List of service request numbers . use the SRN to resolve the problem. use the SRN to resolve the problem. Action: Run the diagnostics on the adapter in system verification mode. SCSI FIFO data miscompare. Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. SCSI wrap or PTC failure. Action: Use MAP 0210: General problem resolution. Adapter POST failed.

Enhanced error handling failure on bus. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on Eads chip. Action: Use MAP 0210: General problem resolution. Adapter memory test failure. Failure and error in determining which type of ARTIC960RxD PCI Adapter. Action: Use MAP 0210: General problem resolution. ARTIC960RxD or RxF PCI Adapter Memory Protection test failure. Enhanced error handling failure on adapter. Action: Before going to MAP 210. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. I/O register test failure. use SRN 66C-201 instead. If the label is A-A.Reference codes 663-104 663-105 663-106 663-107 663-110 663-123 663-150 663-151 663-152 663 C94 C95 C94 663 C95 663 C94 C95 663 C94 C95 C95663 C97 C94 663 C95 C95 663 C94 663 software 227 663 software 227 663 663 227 C94 software C94 663 C95 663 C94 C95 C95 663 C94 C98 C97 C95 221 221 669 669 221 669 669 669 669 ARTIC960RxD or RxF PCI Adapter Bus Interface test failure. ARTIC960RxD or RxF PCI Adapter Dynamic Random Access Memory test failure. look at the label on the adapter. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. 289 663-153 663-154 663-155 663-156 663-157 669-101 669-102 669-103 669-201 669-202 669-203 669-204 669-205 List of service request numbers . ARTIC960RxD or RxF PCI Adapter initialization failure. Interface board non-wrap test failure. Adapter initialization test failure. Action: Use MAP 0210: General problem resolution. ARTIC960RxD PCI Adapter Debug Port test failure. Device configuration failure. Internal loopback test failure. Interface board wrap test failure. ARTIC960RxD or RxF PCI Adapter initialization failure. ARTIC960RxD or RxF PCI Adapter initialization failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Cable wrap test failure. ARTIC960RxD or RxF PCI Adapter Download Diagnostics test failure. Action: Use MAP 0210: General problem resolution. Device driver indicates a hardware failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Configuration register test failure. Action: Use MAP 0210: General problem resolution. and go to MAP 0210: General problem resolution. Error log analysis indicates a ARTIC960RxD or RxF PCI Adapter failure. Action: Use the errpt command to check error log. Action: Use MAP 0210: General problem resolution.

The POST indicates an adapter channel failure. The POST indicates an adapter failure. External wrap test failure (10 Mbps). Error Log Analysis indicates that this device failed to initialize because it is not the IBM version of this adapter. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on adapter. The POST indicates a defective backplane or external enclosure. List of service request numbers . Action: Use MAP 0210: General problem resolution. Action: Use MAP 0270: SCSI RAID problem resolution and verification. The POST indicates a defective cable. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0270: SCSI RAID problem resolution and verification. External wrap test failure (1000 Mbps). Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0210: General problem resolution. Diagnostics indicates adapter configuration failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Error Log Analysis indicates that this device has failed to initialize due to a self-test failure. Internal loopback test failure. Error Log Analysis indicates that this device has failed to initialize due to firmware download error.Reference codes 669-206 669-701 669 669 669-702 669-703 669-704 669 669 669 66A-101 66C-101 66C-102 66C-103 66C-201 66C-202 66C-203 66C-204 66C-205 66C-206 66C-207 66C-208 66C-702 66C-703 66C-704 66D-101 66D-102 66D-103 66D-104 66D-105 66D-106 66D-108 290 221 221 66C 66C 221 66C 66C 66C 66C 66C 66C 66C 66C 66C 66C 66D 227 66D E2A 66D 190 B3A 722 221 External wrap test failure (1000 Mbps). Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on Eads chip. Adapter memory test failure. The POST indicates the last disk drive reconnected caused a channel failure. Adapter initialization test failure. Action: Use MAP 0210: General problem resolution. Error Log Analysis indicates that this device failed to initialize due to a problem with the EEPROM on the adapter. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on bus. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on bus. External wrap test failure (100 Mbps). Action: Use MAP 0210: General problem resolution. AIX operating system cannot configure this non-IBM version of the adapter. Action: Use MAP 0210: General problem resolution. The PCI wrap test failed. Error Log Analysis indicates that this device has failed to initialize due to a self-test failure. Configuration register test failure. Action: Use MAP 0210: General problem resolution. I/O register test failure. Action: Use MAP 0210: General problem resolution. Error Log Analysis indicates that this device failed to initialize due to a problem with the EEPROM on the adapter. Error Log Analysis indicates that this device has failed to initialize due to firmware download error. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution.

Adapter test indicates that write cache is missing. Action: Use MAP 0210: General problem resolution. Error Log Analysis indicates an enhanced error handling error. Adapter test indicates that the cache battery is low on power. Unable to configure the parent device. Adapter test indicates a cache failure. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0210: General problem resolution. SCSI command Mode Sense has failed. Action: Use MAP 0210: General problem resolution. SCSI command Inquiry has failed. ELA indicates that the cache battery is either low on power or has failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0270: SCSI RAID problem resolution and verification. SCSI command Mode Select has failed. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The disk drive has been failed by the adapter. 66D-701 66E-100 66E-102 66E-103 66E-104 66E-105 66E-106 66E-107 66E-108 66E-109 66E-10A 66E-10B List of service request numbers 291 . Action: Use MAP 0270: SCSI RAID problem resolution and verification. Failed to disable data scrub. SCSI command Send Diagnostic has failed. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Adapter test indicates cache battery failure. ELA indicates that the disk reported a hard equipment error. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0210: General problem resolution. ELA indicates a cache failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0270: SCSI RAID problem resolution and verification. The disk reported a Predictive Failure Analysis error (PFA). Action: Use MAP 0210: General problem resolution. SCSI command Allow Media Removal has failed. Adapter test indicates that cache size is invalid. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Enhanced error handling failure on PCI-PCI Bridge. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0270: SCSI RAID problem resolution and verification. SCSI command Start Stop Unit has failed. Unable to get Additional Vital Product Data. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on adapter. SCSI command Test Unit Ready has failed. The POST test indicates a channel failure.Reference codes 66D-109 66D-110 66D-111 66D-112 66D-113 66D-114 66D-115 66D-116 66D-117 66D-118 66D-119 66D-120 66D-121 66D-122 66D-123 66D-124 66D-125 66D-400 66D 722 722 722 722 E2A E3A 66D E2A E2A E2A E2A E3A E3A 66D 221 66D 221 66D 190 B3A 722 66D 221 66E 66E 66E 66E 66E 66E 66E 66E 66E 66E 66E The test indicates an adapter failure. SCSI command Prevent Media Removal has failed. Action: Use MAP 0270: SCSI RAID problem resolution and verification. POST indicates cache failure. Action: Use MAP 0210: General problem resolution. SCSI command Reserve has failed. ELA indicates that the disk reported a hard data error. Action: Use MAP 0270: SCSI RAID problem resolution and verification. Action: Use MAP 0270: SCSI RAID problem resolution and verification. ELA indicates an adapter failure.

Action: Verify that the test medium is inserted properly. to replace the defective DVD-ROM drive. Clean the drive. Undetermined hardware error has occurred. use MAP 0210: General problem resolution. The Random Read Test has detected a hardware error while testing the CD-ROM test medium. to replace the defective DVD-ROM drive. Action: Use MAP 0210: General problem resolution. Action: Run Diagnostic on this drive with another DVD-RAM test medium. SCSI command timeout has occurred. ELA indicates an irrecoverable hardware error. Action: Run Diagnostic on this drive with another CD-ROM test medium. DVD-RAM drive is unable to load the tray. Use MAP 0210: General problem resolution. Otherwise. Run Diagnostic on this drive with another DVD-RAM test medium. Otherwise .Reference codes 66E-10F 66E-200 66E-201 66E 66E B88 media 66E media 66E media 66E 66E B88 media 66E 66E media media 66E 66E media media 66E media 66E 66E-202 66E-203 66E-204 66E-205 66E-206 66E-207 66E-208 66E-209 66E-20A 66E-20B media 66E 66E B88 190 B88 190 66E 66E 66E 66E-300 66E-301 66E-700 66E-701 670-xxx to 673-xxx 674-101 292 SCSI command Release has failed. use MAP 0210: General problem resolution. Action: Verify that the DVD-RAM test medium is inserted properly. Action: Use MAP 0210: General problem resolution. Action: Verify that no external object prevents the drive from ejecting the tray. A SCSI reservation conflict has occurred. Clean the drive. DVD-RAM drive is unable to eject the tray. Action: Use MAP 0210: General problem resolution. DVD-RAM drive is unable to detect the test medium. List of service request numbers . See SCSI devices SRNs ssss-102 through ssss-640. Action: Use MAP 0210: General problem resolution. If the test fails with the new test media. Action: Run Diagnostic on this drive with another CD-ROM test medium. Action: Run Diagnostic on this drive with another DVD-RAM test medium. Otherwise. Verify that no media is stuck inside the drive. Action: Use MAP 0210: General problem resolution. Action: Verify that no external object prevents the drive from loading the tray. Use MAP 0210: General problem resolution. 674 C94 ARTIC960Rx PCI Adapter Central Processing Unit (CPU) test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. DVD-RAM drive has detected a media error. Run the test with another test medium. The Random Read Test has detected a medium error while testing the CD-ROM test medium. DVD-RAM drive has faulty write-protect-detection mechanism. use MAP 0210: General problem resolution. Use MAP 0210: General problem resolution. Run Diagnostic on this drive with another test medium. ELA indicates an undetermined hardware error. DVD-RAM drive is unable to determine the media type. Unable to configure the device. Run Diagnostic on this drive with another DVD-RAM test medium. Unit Attention has occurred. Action: Use MAP 0210: General problem resolution. use MAP 0210: General problem resolution. The Random Write/Read/Compare Test has detected a hardware error while testing the DVD-RAM test medium. The Random Write/Read/Compare Test has detected a medium error while testing the DVD-RAM test medium. Use MAP 0210: General problem resolution. Use MAP 0210: General problem resolution. UseMAP 0210: General problem resolution. Verify that the test medium is inserted properly in the tray. Action: Use MAP 0210: General problem resolution. Action: Verify that the proper test medium is inserted. Action: Verify that the DVD-RAM test medium is not write-protected.

ARTIC960Hx Adapter Bus Interface test failure. ARTIC960Rx PCI Adapter initialization failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Failure and error in determining which type of ARTIC960Rx PCI Adapter. ARTIC960Rx PCI Adapter Dynamic Random Access Memory (DRAM) test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution.Reference codes 674-102 674-103 674-104 674-105 674-106 674-107 674-110 674-123 674-150 674-151 674-152 C95 674 C94 C95 674 C94 C95 C94 674 C95 674 C94 C95 674 C94 C95 C95 674 C97 C94 674 C95 C95 C97 674 software 227 674 software 227 674 674 227 C94 software C94 674 C95 674 C94 C95 C95 674 C94 C97 C95 675 C94 C95 675 C94 C95 675 C94 C95 C94 675 C95 675 C94 C95 ARTIC960Rx PCI Adapter Timer test failure. ARTIC960Rx PCI Adapter initialization failure. Cable wrap test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. ARTIC960Rx PCI Adapter Memory Protection test failure. Device configuration failure. 293 674-153 674-154 674-155 674-156 674-157 675-101 675-102 675-103 675-104 675-105 List of service request numbers . Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Interface board non-wrap test failure. ARTIC960Hx Adapter Dynamic Random Access Memory (DRAM) test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. ARTIC960Hx Adapter Memory Protection test failure. Action: Use MAP 0210: General problem resolution. Action: Use the errpt command to check error log. Action: Use MAP 0210: General problem resolution. Interface board wrap test failure. Action: Use MAP 0210: General problem resolution. Error log analysis indicates a ARTIC960Rx PCI Adapter failure. ARTIC960Hx Adapter Central Processing Unit (CPU) test failure. ARTIC960Rx PCI Adapter Download Diagnostics test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. ARTIC960Rx PCI Adapter Debug Port test failure. ARTIC960Hx Adapter Timer test failure. Device driver indicates a hardware failure. ARTIC960Rx PCI Adapter initialization failure. ARTIC960Rx PCI Adapter Bus Interface test failure.

Interface board non-wrap test failure. Action: Use the MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use the MAP 0210: General problem resolution. Cable wrap test failure. Action: Use the MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The DMA test failed. Action: Use MAP 0210: General problem resolution.MAP 0210: General problem resolution. Action: Use the MAP 0210: General problem resolution. Action: Use the MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use the MAP 0210: General problem resolution. Action: Use the MAP 0210: General problem resolution. The Interrupt test failed. Action: Use the MAP 0210: General problem resolution. Device driver indicates a hardware failure. ARTIC960Hx Adapter initialization failure. Action: Use the MAP 0210: General problem resolution. Device configuration failure. Action: Use the MAP 0210: General problem resolution. Action: Use the MAP 0210: General problem resolution. Failure and error in determining which type of ARTIC960Hx Adapter. Action: Use the MAP 0210: General problem resolution. The SRAM test failed. Enhanced Error Handling Failure on adapter. ARTIC960Hx Adapter initialization failure.Reference codes 675-106 675-107 675-110 675-123 675-150 675-151 675-152 675-153 675 C94 C95 C95 675 C97 C94 675 C95 C95 675 C94 675 software 227 675 software 227 675 675 227 C94 software C94 675 C95 675 C94 C95 C95 675 C94 C98 C97 C95 677 677 677 677 677 677 677 221 677 677 221 677 221 677 221 677 221 ARTIC960Hx Adapter Debug Port test failure. Action: Use MAP 0210: General problem resolution. ARTIC960Hx Adapter initialization failure. Interface board wrap test failure. The Internal Wrap test failed. Action: Use the MAP 0210: General problem resolution. The Configuration Register test failed. The Reset test failed. The External Wrap test failed. Action: Use the MAP 0210: General problem resolution. Action: Use the errpt command to check error log. Action: Use MAP 0210: General problem resolution. The PCI Wrap test failed. Action: Use the MAP 0210: General problem resolution. The Register test failed. Action: Use the MAP 0210: General problem resolution. Enhanced Error Handling Failure on EADs chip. Error log analysis indicates a ARTIC960Hx Adapter failure. List of service request numbers 675-154 675-155 675-156 675-157 677-101 677-102 677-103 677-104 677-105 677-106 677-107 677-109 677-110 677-201 677-202 677-203 677-204 677-205 294 . ARTIC960Hx Adapter Download Diagnostics test failure. The Fibre Channel Adapter configuration failed. The Gigabaud Link Module (GLM) Wrap Test Failure. Action: Use MAP 0210: General problem resolution. Action: Use the MAP 0210: General problem resolution.

Action: Use MAP 0210: General problem resolution. The Reserve command failed. Invalid condition from the drive after a reserve. The SCSI device indicates a reservation conflict. Error log analysis indicates that an adapter error has occurred. The adapter must be replaced immediately. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. A parity error has been detected.Reference codes 677-701 677-703 677-704 677-705 677 221 677 221 677 677 677 677-706 677 678-098 678-099 678-101 678-102 678-103 678-104 678-105 678-107 678-110 678-111 678-112 678-113 678-114 678-120 678-130 678-134 678-135 678-140 678-150 678-160 678-161 678-163 678-164 678 678 B88 678 678 678 678 678 678 678 678 678 678 678 678 678 media B88 software 678 media 678 678 media 678 media 678 B88 678 B88 I/O error on a read/write operation. Action: Use MAP 0210: General problem resolution. Error log analysis indicates that an error has occurred with the adapter. An error is detected in request sense data. The adapter failed to configure. Invalid condition from drive after a request sense. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. A fatal hardware error has occurred. Action: Use MAP 0210: General problem resolution. Failure to do so could result in data being read or written incorrectly. Sense data from the SCSI drive has unexpected data. List of service request numbers 295 . Action: Use MAP 0210: General problem resolution. The SCSI device indicates a check condition. Action: Use MAP 0210: General problem resolution. This adapter was successfully taken offline. The Send Diagnostic command failed. Tape drive not found. Timeout while attempting to communicate with the SCSI device. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The write-protect sensor test failed. The Test Unit Ready command failed. The Inquiry command failed. Invalid condition from the drive after a request sense. The Unload command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Load command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Tape drive indicates an error. Action: Use the MAP 0210: General problem resolution. It will remain offline until reconfigured or the system is rebooted. Action: Use the MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Failure to adhere to this action could result in data being read or written incorrectly or in the loss of data. Action: Use the MAP 0210: General problem resolution. The Mode Select command failed. This adapter must be replaced and not brought back online. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Timeout while attempting to communicate with SCSI device. The SCSI device indicates busy. Action: Use MAP 0210: General problem resolution. Invalid condition from the drive after a reserve. Action: Use MAP 0210: General problem resolution. Error log analysis indicates that an unknown adapter error has occurred. Action: Use MAP 0210: General problem resolution.

The Release command failed. The device configuration failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. An unexpected SCSI error occurred. The Test Unit Ready command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The device open failed. The device configuration failed. The Mode Select command failed. A reservation conflict occurred. A device timeout error occurred. Action: Use MAP 0210: General problem resolution. Read and Compare Test failed. List of service request numbers . Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. SCSI adapter configuration failed. The Read. The Openx command failed. Error diagnosed from error log analysis. Write and Compare test failed. The Unload command failed. Error log analysis indicates a failure. The device open failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The adapter failed to configure. An adapter or bus I/O error occurred. The drive returned bad or non-extended sense data. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The device configuration failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. POST failed: Catastrophic error detected. Action: Use MAP 0210: General problem resolution. See SCSI devices SRNs ssss-102 through ssss-640. Write. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Send Diagnostic command failed. Action: Use MAP 0210: General problem resolution. The Load command failed.Reference codes 678-165 678-166 678-167 678-168 678-169 678-170 678-180 678-185 678-190 678-200 678-201 678-210 678-211 678-220 678-230 678-240 678-260 678-261 678-300 678-310 678-320 678-411 to 678-423 678-511 to 678-523 678-611 to 678-623 678-711 to 678-723 679-xxx 67B-100 296 678 B88 678 B88 276 678 B88 software 678 B88 B88 software 678 media 678 B88 media 678 media 678 media 678 678 media 678 B88 678 B88 678 B88 678 678 678 678 678 678 software B88 678 software 678 media 678 B88 software 678 B88 678 B88 software 678 B88 software 67B Timeout while attempting to communicate with the SCSI device. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Request Sense command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Unable to configure the device.

ELA indicates the coprocessor is held in a reset condition. Action: Use MAP 0210: General problem resolution. Adapter problem. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution 297 67E-001 67E-002 67E-003 67E-004 681-xxx 683-128 686-114 686-124 686-152 686-153 686-252 686-253 686-501 686-511 686-512 686-513 686-514 686-521 686-522 686-523 686-524 686-526 List of service request numbers . Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution Adapter Reset failed Action: Use MAP 0210: General problem resolution Adapter to host memory test failed (byte tag test). Action: Use MAP 0210: General problem resolution.tamper. Action: Use MAP 0210: General problem resolution The modem control line test failed. ELA indicates an out-of-temperature specification. Error Log Analysis Indicates hardware failure VSS2105 Model B09. ELA indicates a +3. Action: Use MAP 0210: General problem resolution Adapter to host memory test failed (word tag test). Action: Use MAP 0210: General problem resolution. Display problem. Action: Use MAP 0210: General problem resolution Adapter to host memory test failed (word pattern test). Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution The modem control line test failed. Action: Use MAP 0210: General problem resolution Adapter BIOS POST CPU failed. Action: Use MAP 0210: General problem resolution The adapter RAM verification test failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution The data wrap communication test failed. ELA indicates a X-ray or dead battery condition.Reference codes 67B-601 67B-602 67B-603 67B-604 67B-605 67B-606 67B-607 11A 67B 67B 67B 67B 67B 67B 67E 221 Monitor/ Cable 67E Monitor/ Cable software 67E 67E Monitor/ Cable 683 686 686 686 D57 686 686 686 686 686 686 686 686 686 686 686 686 686 Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The register verification test failed. The monitor test failed. Action: Use MAP 0210: General problem resolution The data wrap communication test failed. Action: Use MAP 0210: General problem resolution Adapter BIOS POST Timer failed. Action: Use MAP 0210: General problem resolution Adapter BIOS POST Async Ports failed. Action: Use MAP 0210: General problem resolution Adapter BIOS POST Checksum failed. Software error. Action: Use MAP 0210: General problem resolution. +5. SCSI devices SRNs ssss-102 through ssss-640. Action: Use MAP 0210: General problem resolution. ELA indicates: Intrusion latch. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution Adapter to host memory test failed (byte pattern test). ELA indicates a mesh violation . Action: Use MAP 0210: General problem resolution Adapter BIOS POST RAM failed. or +12 V over-voltage condition. ELA indicates a low battery warning.

use MAP 0210: General problem resolution with a FFC of 686. Action: Run diagnostics from a source other than from the disk or a network. suspect a software problem. Action: Use MAP 0210: General problem resolution List of service request numbers . Action: Use MAP 0210: General problem resolution Adapter BIOS Reset failed. use MAP 0210: General problem resolution with a FFC of 686. The adapter failed to configure software Action: Use MAP 0210: General problem resolution An unexpected error occurred that can be attributed to software or hardware. The controller register test failed. Action: Use MAP 0210: General problem resolution Port async external loopback test failed (no response from port).Reference codes 686-527 686-528 686-529 686-531 686-533 686-534 686-541 686-542 686-551 686-552 686-553 686-554 686-555 686-901 to 686-920 686-921 686 686 686 686 686 686 686 686 686 686 686 686 686 software 686 686 software 686-922 to 686-924 software 686 686-925 686 686-926 to 686-950 software 686 687-111 687-114 687-124 687-144 687-152 687-153 298 687 687 687 687 837 684 687 152 687 Adapter BIOS test failed. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Action: Use MAP 0210: General problem resolution Port async external loopback test failed (modem signals). Action: Use MAP 0210: General problem resolution Port async external loopback test failed (data signals). suspect a software problem. otherwise. otherwise. Action: Use MAP 0210: General problem resolution An unexpected error occurred that can be attributed to software or hardware. Action: Use MAP 0210: General problem resolution Port async internal loopback test failed (no response from the port). otherwise. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Action: Use MAP 0210: General problem resolution Port async internal loopback test failed (general). Action: Use MAP 0210: General problem resolution The data wrap communication test failed. Action: Use MAP 0210: General problem resolution Adapter BIOS Timer test failed. Action: Use MAP 0210: General problem resolution Port async external loopback test failed (control signals). Action: Use MAP 0210: General problem resolution An unexpected error occurred that can be attributed to software or hardware. Action: Use MAP 0210: General problem resolution Adapter BIOS RAM test failed. Action: Use MAP 0210: General problem resolution Port async external loopback test failed (general). The adapter failed to configure. Action: Use MAP 0210: General problem resolution Adapter BIOS Download failed. use MAP 210 with a FFC of 686. Action: Use MAP 0210: General problem resolution The sync line test failed. Action: Use MAP 0210: General problem resolution The adapter RAM verification test failed. Action: Run diagnostics from a source other than from the disk or a network. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. suspect a software problem. Action: Run diagnostics from a source other than from the disk or a network. Action: Use MAP 0210: General problem resolution The register verification test failed. Action: Use MAP 0210: General problem resolution Adapter BIOS Command failed.

Action: Use MAP 0210: General problem resolution An unexpected error occurred that can be attributed to software or hardware. Action: Use MAP 0210: General problem resolution Adapter Fuse failed. Action: Use MAP 0210: General problem resolution Adapter to host memory test failed (word tag test). Action: Use MAP 0210: General problem resolution Adapter BIOS POST Checksum failed.Reference codes 687-244 687-252 687-253 687-501 687-502 687-511 687-512 687-513 687-514 687-521 687-522 687-523 687-524 687-525 687-527 687-528 687-529 687-531 687-533 687-534 687-541 687-551 687-600 687-700 687 687 687 687 687 687 687 687 687 687 687 687 687 687 687 687 687 687 687 687 687 687 837 684 687-901 to 687-920 software 687 687-921 687-922 to 687-924 software 687 software 687 The modem control line test failed. Action: Run diagnostics from a source other than from the disk or a network. Action: Use MAP 0210: General problem resolution Adapter BIOS POST RAM failed. Action: Use MAP 0210: General problem resolution Adapter to host memory test failed (byte pattern test). Action: Use MAP 0210: General problem resolution Adapter to host memory test failed (byte tag test). Action: Use MAP 0210: General problem resolution 232RAN status test failed. Action: Use MAP 0210: General problem resolution Port sync external loopback test failed. Action: Use MAP 0210: General problem resolution The sync line test failed. Action: Use MAP 0210: General problem resolution An unexpected error occurred that can be attributed to software or hardware. The adapter failed to configure. Action: Use MAP 0210: General problem resolution Adapter BIOS Reset failed. Action: Use MAP 0210: General problem resolution Adapter to host memory test failed (word pattern test). use MAP 0210: General problem resolution with a FFC of 687. Action: Use MAP 0210: General problem resolution Adapter BIOS RAM test failed. Action: Use MAP 0210: General problem resolution Adapter BIOS POST Timer failed. suspect a software problem. Action: Use MAP 0210: General problem resolution The modem control line test failed. Action: Use MAP 0210: General problem resolution Adapter BIOS Download failed. Action: Use MAP 0210: General problem resolution Adapter BIOS POST CPU failed. Action: Use MAP 0210: General problem resolution Adapter Reset failed. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. Action: Use MAP 0210: General problem resolution Adapter BIOS POST Sync Line failed. Action: Use MAP 0210: General problem resolution Adapter BIOS Command failed. Action: Use MAP 0210: General problem resolution Adapter BIOS Timer test failed. Action: Use MAP 0210: General problem resolution The data wrap communication test failed. Action: Run diagnostics from a source other than from the disk or a network. Action: Use MAP 0210: General problem resolution Port sync internal loopback test failed. otherwise. Action: Use MAP 0210: General problem resolution Adapter BIOS test failed. If the same error occurs or if the original SRN was not 299 List of service request numbers . Action: Use MAP 0210: General problem resolution 422RAN status test failed.

See SCSI devices SRNs ssss-102 through ssss-640. use MAP 0210: General problem resolution with a FFC of 687. suspect a software problem. List of service request numbers 300 . Action: Use MAP 0210: General problem resolution The Reserve command failed. Action: Run diagnostics from a source other than from the disk or a network. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution The adapter failed to configure. Read and Compare Test failed. Write. The SCSI device indicates a reservation conflict. otherwise. Action: Use MAP 0210: General problem resolution The Load command failed. An unexpected SCSI error occurred. Action: Use MAP 0210: General problem resolution. Invalid condition from the drive after a reserve. Action: Use MAP 0210: General problem resolution.Reference codes 687-925 687-926 to 687-950 689-xxx 68C-101 68C-102 68C-103 68C-104 68C-105 68C-107 68C-110 68C-111 68C-112 68C-113 68C-114 68C-120 68C-130 68C-134 68C-135 68C-140 68C-150 68C-160 68C-161 68C-163 68C-164 68C-165 68C-166 68C-167 687 software software 687 68C 68C 68C 68C 68C 68C 68C 68C 68C 68C 68C 68C 68C media B88 software 68C media 68C 68C media 68C media 68C B88 68C B88 68C B88 68C B88 276 68C B88 software 68C B88 obtained from disk or a network based diagnostics. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution The Mode Select command failed. Action: Use MAP 0210: General problem resolution The Send Diagnostic command failed. Sense data from the SCSI drive has unexpected data. Action: Use MAP 0210: General problem resolution. An error is detected in request sense data. otherwise. If the same error occurs or if the original SRN was not obtained from disk or a network based diagnostics. use MAP 0210: General problem resolution with a FFC of 687. The SCSI device indicates a check condition. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution The Unload command failed. The adapter failed to configure. Action: Use MAP 0210: General problem resolution The Test Unit Ready command failed. suspect a software problem. Invalid condition from the drive after a request sense. Action: Use MAP 0210: General problem resolution An unexpected error occurred that can be attributed to software or hardware. Action: Use MAP 0210: General problem resolution The SCSI device indicates busy. Action: Use MAP 0210: General problem resolution. Timeout while attempting to communicate with the SCSI device. Action: Use MAP 0210: General problem resolution The write-protect sensor test failed. Action: Use MAP 0210: General problem resolution Invalid condition from drive after a request sense. Unable to configure the device. Action: Use MAP 0210: General problem resolution Invalid condition from the drive after a reserve. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution Timeout while attempting to communicate with the SCSI device. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution The Inquiry command failed. Timeout while attempting to communicate with SCSI device. Action: Use MAP 0210: General problem resolution.

Action: Use MAP 0210: General problem resolution. Adapter failure. The device open failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Send Diagnostic command failed. A device timeout error occurred. Action: Use MAP 0210: General problem resolution. Write and Compare test failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Request Sense command failed. Action: Use MAP 0210: General problem resolution. The drive returned bad or non-extended sense data. The Read. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The device configuration failed. Action: Use MAP 0210: General problem resolution. SCSI adapter configuration failed. An adapter or bus I/O error occurred. Action: Use MAP 0210: General problem resolution. The device open failed. Action: Use MAP 0210: General problem resolution. The Mode Select command failed. The device configuration failed. Action: Use MAP 0210: General problem resolution. The Load command failed. Display failure. Action: Use MAP 0210: General problem resolution. List of service request numbers 301 . Error log analysis indicates a failure. A reservation conflict occurred. Action: Use MAP 0210: General problem resolution. The Release command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution.Reference codes 68C-168 68C-169 68C-170 68C-180 68C-185 68C-190 68C-200 68C-201 68C-210 68C-211 68C-220 68C-230 68C-240 68C-260 68C-261 68C-300 68C-310 68C-320 68C-411 to 68C-423 68C-511 to 68C-523 68C-611 to 68C-623 68C-711 to 68C-723 68E-001 68E-002 68E-003 68E-004 68E-005 B88 software 68C media 68C B88 media 68C media 68C media 68C 68C media 68C B88 68C B88 68C B88 68C 68C 68C 68C 68C 68C software B88 68C software 68C media 68C B88 software 68C B88 68C B88 software 68C B88 software Software 68E 68E Software 68E 227 68E Monitor/ Cable 68E 227 Monitor/ Cable The adapter failed to configure. Action: Use MAP 0210: General problem resolution. The Unload command failed. Action: Use MAP 0210: General problem resolution. Adapter failure. The device configuration failed. Action: Use MAP 0210: General problem resolution. Software error. The Test Unit Ready command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Error diagnosed from error log analysis. The Openx command failed. Adapter failure.

The device configuration failed. A reservation conflict occurred. Write and Compare test failed. Action: Use MAP 0210: General problem resolution. Adapter config register test failed. Action: Use MAP 0210: General problem resolution. Adapter open failed. The Inquiry command failed. Action: Use MAP 0210: General problem resolution.Reference codes 690-xxx 692-110 692-120 692-130 692-135 692-140 692-150 692-160 692-169 692-170 692-180 692-185 692-190 692-200 692-210 692-220 692-230 692-240 692-300 692-310 692-320 692-411 to 692-423 692-511 to 692-523 692-611 to 692-623 692-711 to 692-723 693-100 693-101 693-102 693-103 302 692 692 692 media 692 media 692 692 media 692 media 692 media 692 B88 media 692 media 692 media 692 692 media 692 B88 692 692 692 692 software B88 692 software 692 media 692 B88 software 692 B88 692 B88 software 692 B88 software 693 227 693 227 693 227 See SCSI devices SRNs ssss-102 through ssss-640. Action: Use MAP 0210: General problem resolution. The Load command failed. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. The Send Diagnostic command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Unload command failed. The Reserve command failed. SCSI adapter configuration failed. List of service request numbers . An adapter or bus I/O error occurred. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Send Diagnostic command failed. The Mode Select command failed. The Openx command failed. Action: Use MAP 0210: General problem resolution. A device timeout error occurred. Action: Use MAP 0210: General problem resolution. Error log analysis indicates a failure. The Mode Select command failed. Adapter reset failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The drive returned bad or non-extended sense data. Action: Use MAP 0210: General problem resolution. The Release command failed. The Load command failed. The Read. The device configuration failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Unload command failed. The Request Sense command failed. Action: Use MAP 0210: General problem resolution.

Action: Use MAP 0210: General problem resolution. External Loopback failed Action: Check wrap plug installation. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Charm memory write failure. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on EADS chip Action: Use MAP 0210: General problem resolution. Loss of light detected in Link test. Packet memory error. Charm memory read failure. PCI configuration register write failure. Enhanced Error Handling failure on bus Action: Use MAP 0210: General problem resolution. List of service request numbers 303 . Control memory failure. Action: Use MAP 0210: General problem resolution. Link-R detected bad parity. Adapter checksum failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on adapter Action: Use MAP 0210: General problem resolution. Klog error Action: Use MAP 0210: General problem resolution. Suni initialization failure. EPROM checksum failed Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Check wrap plug installation. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Internal Loopback failed. Internal wrap test failure Action: Use MAP 0210: General problem resolution. Suni detected bad parity. Action: Use MAP 0210: General problem resolution. Adapter microcode download test failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter internal wrap test failed. Action: Use MAP 0210: General problem resolution. Adapter memory test failure. Action: Use MAP 0210: General problem resolution. External wrap test failure Action: Use MAP 0210: General problem resolution. Charm software reset failure. Adapter close failed.Reference codes 693-104 693-105 693-106 697-100 697-101 697-102 697-103 697-104 697-105 697-106 697-107 697-108 697-109 697-10B 697-10C 697-10D 697-121 697-122 697-123 697-124 697-125 697-126 697-127 697-1FF 697-200 697-201 693 227 693 227 693 227 693 227 697 software 227 697 software 227 697 software 227 697 software 227 697 software 227 697 software 227 697 697 697 Wrap Plug 697 Wrap Plug 697 697 software 227 697 227 software 697 697 697 697 221 221 697 697 software 227 software 697 227 Adapter I/O register test failed. DMS failed.

Action: Use MAP 0210: General problem resolution. ODM Initialization error Action: Use MAP 0210: General problem resolution.Reference codes 697-202 697-203 697-205 697-206 697-221 697-222 697-223 697-224 697-701 697-702 698-100 698-101 698-102 698-103 698-104 698-105 698-106 698-107 698-108 698-109 698-10B 698-10C 698-10D 698-121 304 software 697 227 software 697 227 software 697 227 software 697 227 software 697 227 697 221 697 221 697 221 697 221 697 221 697 698 software 227 698 software 227 698 software 227 698 software 227 698 software 227 698 software 227 698 698 698 Wrap Plug 698 Wrap Plug 698 698 software 227 698 227 software 698 ASL error Action: Use MAP 0210: General problem resolution. Loss of light detected in Link test. Action: Use MAP 0210: General problem resolution. DMS failed. Action: Use MAP 0210: General problem resolution. Action: Check wrap plug installation. Error Log Analysis indicates an unrecovered interrupt error. Interrupt test failure Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Diagnostic configuration failure. Error Log Analysis indicates an I/O failure on the adapter. Link-R detected bad parity. Charm memory read failure. Adapter memory test failure. Action: Use MAP 0210: General problem resolution. External Loopback failed Action: Check wrap plug installation. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Suni initialization failure. Action: Use MAP 0210: General problem resolution. Charm software reset failure. Charm memory write failure. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure opening the adapter Action: Use MAP 0210: General problem resolution. Hardware failure opening the adapter Action: Use MAP 0210: General problem resolution. Internal Loopback failed. Action: Use MAP 0210: General problem resolution. List of service request numbers . Action: Use MAP 0210: General problem resolution. PCI configuration register write failure. Error in releasing adapter Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Control memory failure. Suni detected bad parity. Error in diag open. Action: Use MAP 0210: General problem resolution. Adapter DMA test failure Action: Use MAP 0210: General problem resolution. Packet memory error Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution.

External wrap test failure. Action: Use MAP 0210: General problem resolution. Klog error. Enhanced Error Handling failure opening the adapter. Adapter SDRAM failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. ASL error. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution.Reference codes 698-122 698-123 698-124 698-125 698-126 698-127 698-1FF 698-200 698-201 698-202 698-203 698-205 698-206 698-221 698-222 698-223 698-224 698-701 698-702 69b-101 69b-102 69b-103 69b-104 69b-105 69b-106 69b-107 69b-108 69b-109 698 698 698 221 221 698 698 software 227 software 698 227 software 698 227 software 698 227 software 698 227 software 698 227 software 698 227 698 221 698 221 698 221 698 221 698 221 698 69b 69b 69b 69b 69b 69b 69b 69b 221 Adapter checksum failure. Action: Use MAP 0210: General problem resolution. Adapter DMA test failure. Adapter memory test failure. Error Log Analysis indicates an I/O failure on the adapter. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on adapter. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. ODM Initialization error. Enhanced Error Handling failure on EADS chip. Action: Use MAP 0210: General problem resolution. Interrupt test failure. Action: Use MAP 0210: General problem resolution. Internal loopback test failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Error Log Analysis indicates an unrecovered interrupt error. Action: Use MAP 0210: General problem resolution. Diagnostic configuration failure. Adapter checksum failure. EPROM checksum failed. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on bus. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Hardware failure opening the adapter. Error in diag open. Action: Use MAP 0210: General problem resolution. EPROM test failure. 305 List of service request numbers . Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on bus. Internal wrap test failure. Action: Use MAP 0210: General problem resolution. External wrap test failure. Adapter buffer test failure. Action: Use MAP 0210: General problem resolution. Error in releasing adapter. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter cache test failure. Action: Use MAP 0210: General problem resolution.

Enhanced Error Handling failure on Eads chip. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter buffer test failure. External wrap test failure. Interrupt test failure. Action: Use MAP 0210: General problem resolution. Adapter memory test failure. See SCSI devices SRNs (ssss-102 to ssss-640. Enhanced error handling failure opening the adapter. 722 723 List of service request numbers . Error Log Analysis indicates an I/O failure on the adapter. Adapter SDRAM failure. Action: Use MAP 0210: General problem resolution. Adapter cache test failure. Adapter checksum failure. Service Request Number 700-xxx to 707-xxx 721-xxx 722-xxx 723-xxx 306 Failing Function Codes Description and Action See SCSI devices SRNs (ssss-102 to ssss-640. Enhanced Error Handling failure on Eads chip. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Hardware failure opening adapter.Reference codes 69b-110 69b-111 69b-201 69b-202 69b-203 69b-204 69b-701 69d-101 69d-102 69d-103 69d-104 69d-105 69d-106 69d-107 69d-108 69d-109 69d-110 69d-111 69d-201 69d-202 69d-203 69d-204 69d-701 221 69b 69b 221 69b 221 69b 221 69b 221 69b 69d 69d 69d 69d 69d 69d 69d 69d 221 221 69d 69d 221 69d 221 69d 221 69d 221 69d Action: Use MAP 0210: General problem resolution. Enhanced error handling failure opening the adapter. Action: Use MAP 0210: General problem resolution. SRNs 700-xxx through 7C1-117 Note: Some SRNs in this chapter may have 4 rather than 3 digits after the dash (-). Action: Use MAP 0210: General problem resolution. Hardware failure opening adapter. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on adapter. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter DMA test failure. EPROM test failure. Unknown disk drive type is failing. Adapter DMA test failure. Action: Use MAP 0210: General problem resolution. Internal loopback test failure. Action: Use MAP 0210: General problem resolution. Enhanced Error Handling failure on adapter. Enhanced Error Handling failure on bus. Action: Use MAP 0210: General problem resolution. Interrupt test failure. Error Log Analysis indicates an I/O failure on the adapter. Action: Use MAP 0210: General problem resolution.

Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. or the Unload command failed. The Reserve command failed. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. Action: Use MAP 0210: General problem resolution. The Mode Select command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. The device configuration failed. Unknown keyboard. or bus I/O error occurred. Action: Use MAP 0210: General problem resolution. The keyboard light-on test failed. The device configuration failed.Reference codes 724-xxx 733-110 to 733-120 733-130 to 733-135 733-140 733-150 to 733-169 733-170 733-180 to 733-185 733-190 733-200 733-210 733-220 to 733-240 733-300 733-310 733-320 733-411 to 733-423 733-511 to 733-523 733-611 to 733-723 736-101 736-102 736-103 736-104 736-105 736-106 736-201 736-202 736-203 724 733 733 media 733 733 media 733 B88 media 733 media 733 733 media 733 B88 733 733 software B88 733 software 733 media 733 B88 software 733 B88 733 B88 software 821 736 821 736 821 736 736 821 736 821 821 736 821 Unknown CD-ROM type is failing. The drive returned bad or non-extended sense data. 140 GB 8 mm tape drive failed. The keyboard reset failed. An unexpected adapter error occurred. An unexpected adapter error occurred. An adapter. SCSI adapter configuration failed. A reservation conflict occurred. or the Send Diagnostic command failed. Action: Use MAP 0210: General problem resolution. The Load command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. or the Unload command failed. 307 List of service request numbers . Action: Use MAP 0210: General problem resolution. Unknown tape drive failure. Error log analysis indicates a failure. or the Inquiry command failed. Action: Use MAP 0210: General problem resolution. device. Action: Use MAP 0210: General problem resolution. The Read. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. An unexpected device or adapter error occurred. Action: Use MAP 0210: General problem resolution. Write and Compare test failed. Action: Use MAP 0210: General problem resolution. The Load command failed. An unexpected device or adapter error occurred. Action: Use MAP 0210: General problem resolution. The keyboard light-off test failed. The Mode Select command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution.

Unable to recognize the keyboard. The error log analysis indicates an unknown failure. refer to the tape autoloader service information. refer to the tape autoloader service information. Action: Use MAP 0210: General problem resolution. See SCSI devices SRNs (ssss-102 to ssss-640.Reference codes 736 821 736-204 736-205 736-206 736-301 736-302 736-303 736-304 736-401 736-402 736-403 736-404 736-701 736-901 736-902 736-903 741-xxx 745-100 745-200 745-300 to 745-350 745-400 745-410 to 745-435 745-440 745-441 to 745-443 745-444 media 745 media 745 media 745 745 magazine media 745 media 745 SCSI Adapter 745 media 745 environment media clean media drive 745 magazine media 736 736 821 736 821 821 736 821 736 736 821 736 821 736 736 821 736 821 821 736 821 736 821 The read keyboard ID test failed. Action: Use MAP 0210: General problem resolution. 4-mm Tape Auto Loader problem. refer to the tape autoloader service information. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. refer to the tape autoloader service information. Magazine Movement Failure Action: Check magazine and media. The keyboard echo test failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. refer to the tape autoloader service information. SCSI Hardware Failure. refer to the tape autoloader service information. The error log analysis indicates a device failure. An unexpected device or adapter error occurred. Action: Use MAP 0210: General problem resolution. refer to the tape autoloader service information. clean drive. Action: Use MAP 0210: General problem resolution. clean rollers. General Hardware Failure. Action: Use MAP 0210: General problem resolution. clean drive. Drive Not Ready. Action: Replace media. 4-mm Tape Auto Loader problem. Internal Hardware Failure Action: Replace drive. Error configuring the device. replace media. Drive Requires Cleaning Action: Clean drive. An error occurred in turning off the lamps. Action: Replace drive. Action: No action required. refer to the tape autoloader service information. An unexpected device or adapter error occurred. The select scan code set test failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Install media. replace media. refer to the tape autoloader service information. Action: Use MAP 0210: General problem resolution. List of service request numbers 745-445 745-460 to 745-465 308 . The keyboard is failing. Recovered error. An error occurred in turning on the lamps. The error log analysis indicates an adapter failure. Action: Use MAP 0210: General problem resolution. An unexpected adapter error occurred. Action: Replace drive. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Replace media. The keyboard layout ID test failed. Humidity too High Action: Lower humidity. An unexpected adapter error occurred.

SCSI Interface Failure Action: Check SCSI interface. refer to the tape autoloader service information. FIFO full bit set. SCSI FIFO data miscompare. FIFO empty bit clear. FIFO full bit clear. Action: Use MAP 0210: General problem resolution. Miscompare during the write/read of the configuration register. Enhanced error handling failure on a PCI-PCI Bridge. refer to the tape autoloader service information. SCSI parity error. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter POST failed. SCSI wrap or PTC failure. Action: Use MAP 0210: General problem resolution. FIFO empty bit set. Action: Use MAP 0210: General problem resolution. Enhanced error handling failure on the adapter. refer to the tape autoloader service information. Unit Attention Action: Software conflict. refer to the tape autoloader service information. FIFO data miscompare. Action: Use MAP 0210: General problem resolution. Not Writeable Action: Check media for write-protect. Action: Use MAP 0050: SCSI bus problems. SCSI adapter test failure. Action: Use MAP 0210: General problem resolution. Error during the write/read of the memory register. Action: Use MAP 0050: SCSI bus problems SCSI FIFO flags error. refer to the tape autoloader service information. media changed. Action: Use MAP 0210: General problem resolution. Drawer Open/Close Failure Action: Check magazine and media. Enhanced error handling failure on the bus.Reference codes 745-470 to 745-475 745-480 to 745-485 745-500 745-600 745-700 745-800 745-B00 745-D00 746-101 746-102 746-103 746-212 746-213 746-214 746-215 746-216 746-217 746-218 746-219 746-220 746-221 746-222 746-223 746-224 746-225 746-226 746-227 746-230 745 magazine media 745 magazine media 745 system 745 system 745 media 745 media 745 SCSI Adapter 745 media 221 293 746 221 746 746 746 746 746 746 746 746 746 221 746 746 746 221 746 746 221 Media Insert/Eject Failure Action: Check clean magazine and media. Action: Use MAP 0050: SCSI bus problems. Action: Use MAP 0210: General problem resolution. Illegal request to drive Action: Software conflict. Action: Use MAP 0210: General problem resolution. SCSI configuration register read or write error. Action: Use MAP 0210: General problem resolution. Arbitration test failed. clean rollers. refer to the tape autoloader service information. Action: Use MAP 0210: General problem resolution. Miscompare during the write/read of the memory I/O register. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. 309 List of service request numbers . SCSI FIFO underflow. Tape Full Action: Check replace media. Action: Use MAP 0210: General problem resolution. Blank Media Action: Check media. Action: Use MAP 0210: General problem resolution. refer to the tape autoloader service information. refer to the tape autoloader service information.

Action: Use MAP 0210: General problem resolution. use the SCSI service hints in General SCSI configuration checks to resolve the problem. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0050: SCSI bus problems SCSI FIFO flags error. SCSI FIFO data miscompare. Action: Use MAP 0210: General problem resolution. SCSI bus error. Action: Use MAP 0050: SCSI bus problems. Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. SCSI FIFO underflow. Action: Use MAP 0050: SCSI bus problems.Reference codes 746-231 746-232 746-240 746-242 746-301 746-701 746-801 746 221 746 746-802 746-803 747-101 747-102 747-103 747-212 747-213 747-214 747-215 747-216 747-217 747-218 747-219 747-220 747-221 747-222 747-223 747-224 747-225 310 221 293 747 221 747 747 747 747 747 747 747 747 747 221 747 747 747 221 747 Action: Use MAP 0050: SCSI bus problems. SCSI parity error. Error log analysis indicates a PCI SCSI adapter failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0050: SCSI bus problems. Function could not complete. use the SRN to resolve the problem. Adapter POST failed. Action: Use MAP 0210: General problem resolution. FIFO full bit set. Action: Use MAP 0210: General problem resolution. FIFO full bit clear. If an SRN is reported. Enhanced error handling failure on a PCI-PCI Bridge. Miscompare during the write/read of the configuration register. If an SRN is reported. No terminal power. SCSI bus data miscompare. Enhanced error handling failure on the bus. Action: Use MAP 0210: General problem resolution. Action: Run the diagnostics on the adapter in system verification mode. Action: Use MAP 0210: General problem resolution. If an SRN is not reported. Action: Use MAP 0050: SCSI bus problems. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The parent device open failed. use the SCSI service hints in General SCSI configuration checks to resolve the problem. Action: Run the diagnostics on the adapter in system verification mode. SCSI configuration register read or write error. FIFO data miscompare. Action: Use MAP 0210: General problem resolution. use the SCSI service hints in General SCSI configuration checks to resolve the problem. Error log analysis indicates that multiple SCSI bus errors have occurred. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. List of service request numbers . use the SRN to resolve the problem. If an SRN is not reported. Enhanced error handling failure on the adapter. use the SRN to resolve the problem. If an SRN is reported. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Error log analysis indicates a terminator problem. FIFO empty bit set. Miscompare during the write/read of the memory I/O register. Error during the write/read of the memory register. If an SRN is not reported. FIFO empty bit clear. Action: Run the diagnostics on the adapter in System Verification mode. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0050: SCSI bus problems.

Action: Use MAP 0210: General problem resolution. SCSI bus error. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0050: SCSI bus problems. If an SRN is reported. 311 List of service request numbers . Action: Run the diagnostics on the adapter in system verification mode. Error log analysis indicates a PCI SCSI adapter failure. No terminal power. Action: Run the diagnostics on the adapter in system verification mode. Action: Run the diagnostics on the adapter in system verification mode. use the SRN to resolve the problem. use the SCSI service hints in General SCSI configuration checks to resolve the problem. Function could not complete. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0050: SCSI bus problems. The Load command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Refer to service documentation for this device. Action: Use MAP 0210: General problem resolution. Arbitration test failed. If an SRN is not reported. Action: Use MAP 0050: SCSI bus problems. The Mode Select command failed. If an SRN is not reported. The Inquiry command failed.Reference codes 747-226 747-227 747-230 747-231 747-232 747-240 747-242 747-301 747-701 747-801 747 221 747 747 221 747-802 747-803 749-xxx 757-110 757-120 757-130 757-135 757-140 757-150 757-160 757-169 757-170 757-180 757-185 757-190 757-200 749 757 757 757 media 757 media 757 757 media 757 media 757 media 757 B88 media 757 media 757 media 757 757 media SCSI wrap or PTC failure. use the SCSI service hints in General SCSI configuration checks to resolve the problem. The Unload command failed. Error log analysis indicates that multiple attempts to reset the SCSI bus have timed out. If an SRN is reported. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0050: SCSI bus problems. SCSI adapter test failure. If an SRN is not reported. The Test Unit Ready command failed. 7331 Model 205 Tape Library. Action: Use MAP 0210: General problem resolution. The Mode Select command failed. Write and Compare test failed. The Reserve command failed. If an SRN is reported. Error log analysis indicates a terminator problem. Action: Use MAP 0210: General problem resolution. SCSI bus data miscompare. Action: Use MAP 0210: General problem resolution. The Test Unit Ready command failed. Error log analysis indicates that multiple SCSI bus errors have occurred. Action: Use MAP 0050: SCSI bus problems. Action: Use MAP 0210: General problem resolution. The Send Diagnostic command failed. use the SRN to resolve the problem. Action: Use MAP 0050: SCSI bus problems. use the SRN to resolve the problem. The Send Diagnostic command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The Load command failed. The Unload command failed. use the SCSI service hints in General SCSI configuration checks to resolve the problem. Action: Use MAP 0210: General problem resolution. The Read. Action: Use MAP 0210: General problem resolution. The parent device open failed.

SRAM test failed. SCSI adapter configuration failed. Notes: 1. Interrupt test failed. Action: Use MAP 0210: General problem resolution. The drive returned bad or non-extended sense data. The Openx command failed. 2. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. An adapter or bus I/O error occurred. Action: Use MAP 0210: General problem resolution. 763 software 221 ext clock 763 wrap plug 763 763 221 763 software 763 763 763 763 763 221 Switchcable 763 terminator Switchcable wrap plug Problem detected with a device or device data corrupted. TBIC test failed. Error log analysis indicates a failure. Action: Use MAP 0210: General problem resolution. Card wrap test failed.css software. Note: Refer to your SP Maintenance Information for the switch cable FRU part number. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. The wrap plug FRU part number is listed under the 763 FFC. Refer to your SP Maintenance Information for the switch cable FRU part number. A device timeout error occurred. FIFO test failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Notes: 1.Reference codes 757-210 757-220 757-230 757-240 757-300 757-310 757-320 757-411 to 757-423 757-511 to 757-523 757-611 to 757-623 757-711 to 757-723 759-xxx 763-1xx 763-200 to 763-299 763-2A0 to 763-2A9 763-3xx 763-4xx 763-5xx 763-6xx 763-7xx 763-8xx 763-9xx 757 B88 757 757 757 757 software B88 757 software 757 media 757 B88 software 757 B88 757 B88 software 757 B88 software The device configuration failed. Action: Use MAP 0210: General problem resolution. Problem detected with the POS registers. Card wrap test failed. Note: The terminator FRU part number is listed under the 763 FFC. Action: Use MAP 0210: General problem resolution. Microprocessor test failed. Refer to your SP Maintenance Information for the external clock FRU part number. The Release command failed. Problem detected with the external clock (SP switch). Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Note: You may need to reinstall ssp. Action: Use MAP 0210: General problem resolution. The device configuration failed. The Request Sense command failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. List of service request numbers 763-Ax3 763-Ax4 312 . See SCSI Devices SRNs (ssss-102 to ssss-640). Action: Use MAP 0210: General problem resolution. Problem detected with the internal clock. Action: Use MAP 0210: General problem resolution. DMA engine test failed. A reservation conflict occurred.

SRAM test failed. Interrupt test failed. Enhanced error handling failure on adapter. Action: Use MAP 0210: General problem resolution.Reference codes 763-xx2 764-1xx 763 764 software 221 ext clock 764 wrap plug 764 764 221 764 software 764 764 764 764 764 221 switchcable 764 terminator Switchcable wrap plug 764 2. 2. Wrap Test Failure. Enhanced error handling failure on Eads chip. Action: Use MAP 0210: General problem resolution. The wrap plug FRU part number is listed under the 763 FFC. Refer to your SP Maintenance Information for the external clock FRU part number. Action: Use MAP 0210: General problem resolution. Refer to your SP Maintenance Information for the switch cable FRU part number. (except for SRN 764-282) Action: Replace the SP Switch MX Adapter. Action: Use MAP 0210: General problem resolution. Adapter On-card Test Failure. Wrap Test Failure. Note: You may need to reinstall ssp. Problem detected with a device or device data corrupted. Problem detected with the internal clock. Problem detected with the external clock (SP switch). TBIC test failed. Action: Use MAP 0210: General problem resolution. 764-Ax4 764-xx2 772-xxx to 774-xxx 776-101 776-102 776-103 776-104 776-105 776-106 776-106 776-107 776-108 776-201 776-202 D46 240 776 776 221 776 D46 776 776 776 776 221 External Test Failure. Card wrap test failed. Configuration Register Test Failure. Problem detected with the POS registers. Action: Use MAP 0210: General problem resolution. The wrap plug FRU part number is listed under the 763 FFC. (except for SRN 763-282) Action: Replace the SP Switch MX Adapter. Action: Use MAP 0210: General problem resolution. Notes: 1. Notes: 764-200 to 764-299 764-2A0 to 764-2A9 764-3xx 764-4xx 764-5xx 764-6xx 764-7xx 764-8xx 764-9xx 764-Ax3 1. I/O Test Failure.css software. Action: Use MAP 0210: General problem resolution. Bad adapter card. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Bad adapter card. The wrap plug FRU part number is listed under the 763 FFC. Enhanced error handling failure on bus. Action: Use MAP 0210: General problem resolution. Card wrap test failed. 2. External Test Failure. DMA engine test failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. FIFO test failed. Action: Use MAP 0210: General problem resolution. See SCSI devices SRNs (ssss-102 to ssss-640. Microprocessor test failed. Action: Use MAP 0210: General problem resolution. Note: The terminator FRU part number is listed under the 763 FFC. Note: Refer to your SP Maintenance Information for the switch cable FRU part number. 313 List of service request numbers .

Action: Use MAP 0210: General problem resolution. Wrap Test Failure. Connect Test Failure. External Test Failure. This failure occurs if not connected to a functional Token-Ring network. External Test Failure. ELA indicates an adapter check occurred. Action: Run advanced diagnostics for this resource to obtain correct problem isolation. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Run advanced diagnostics with wrap test for this resource to obtain correct problem isolation. Connect Wrap Test Failure. ELA indicates a DMA failure occurred. ELA indicates an adapter error occurred. Action: Run advanced diagnostics for this resource to obtain correct problem isolation. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution.Reference codes 776-203 776-204 776-205 776-206 776-301 776-302 776-303 776-304 776-305 776-306 776 221 D46 776 776 221 D46 776 776 221 D46 240 776 D46 776 221 240 D46 776 D46 776 221 D46 776 221 D46 776 221 240 D46 776 221 240 D46 776 221 240 D46 776 221 240 D46 776 221 240 D46 776 221 240 D46 776 221 240 D46 776 221 776 776 221 776 221 Wrap Test Failure. Action: Use MAP 0210: General problem resolution. List of service request numbers 776-401 776-404 776-405 776-406 776-414 776-415 776-416 776-701 776-702 776-703 314 . External Test Failure. Action: Run advanced diagnostics with wrap test for this resource to obtain correct problem isolation. This failure occurs if not connected to a functional Token-Ring network. Action: Use MAP 0210: General problem resolution. External Test Failure. Wrap Test Failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Run advanced diagnostics with wrap test for this resource to obtain correct problem isolation. Wrap Test Failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Run advanced diagnostics with wrap test for this resource to obtain correct problem isolation. Action: Run advanced diagnostics for this resource to obtain correct problem isolation. External Test Failure. Wrap Test Failure. Wrap Test Failure. Connect Test Failure. This failure occurs if not connected to a functional Token-Ring network. Wrap Test Failure. Wrap Test Failure. Wrap Test Failure. Connect Test Failure.

Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Software error. Action: Use MAP 0210: General problem resolution. Adapter error. Adapter failure. Software error. Adapter error. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. ELA indicates a command write failure occurred. Adapter failure. Action: Use MAP 0210: General problem resolution. Software error. Adapter failure. Action: Use MAP 0210: General problem resolution. Software error. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. 315 List of service request numbers . Software error. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Software error. Action: Use MAP 0210: General problem resolution. Software error. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter failure.Reference codes 776-704 776-705 776-706 776-707 778-002 778-004 778-009 778-011 778-017 778-019 778-030 778-032 778-033 778-035 778-036 to 778-072 778-073 778-075 778-076 778-301 to 778-D02 778-E01 778-E02 to 778-1401 778-1402 778-1403 to 778-1405 778-1500 778-1600 to 778-1604 778-2501 to 778-2508 778-2509 to 778-2511 778-2601 776 221 776 221 776 776 software 778 software 778 software 778 software 778 software 778 778 software 778 221 software 778 software 778 778 software software 778 778 221 software 778 778 software 778 221 software 778 778 221 software 778 778 221 778 software 778 902 778 221 software 778 778 ELA indicates a PCI bus failure occurred. ELA indicates an internal adapter error has occurred. Action: Use MAP 0210: General problem resolution. Software error. Action: Use MAP 0210: General problem resolution. Adapter failure. Adapter failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Software error. Action: Use MAP 0210: General problem resolution. Software error. Adapter failure. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Adapter failure. Action: Use MAP 0210: General problem resolution. ELA indicates a Programmed I/O failure occurred. Software error. Adapter failure. Action: Use MAP 0210: General problem resolution. Software error. Software error. Action: Use MAP 0210: General problem resolution.

A software error was caused by a hardware failure. Adapter Serial Communication Controller (SCC) test failure. An error was found on the adapter. The adapter card hardware failed. The adapter card hardware failed. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: General problem resolution. Action: Use MAP 0210: Gene