(A7xxxxxx) Licensed Internal Code (LIC) reference codes

For use by service providers.

Use this table for A7xxxxxx reference codes.

Perform the following actions:

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). These 4 characters are the unit reference code.
Look up the unit reference code in the following table.
Perform the actions in the Description/Action column of the table.

In all cases, once the failing item is determined, go to the locations table for the system you are working on to determine the location, and use the remove and replace procedure for the failing item.

If you do not find an SRC in the table that follows, contact your next level of support for assistance.

Notes:

The SRCs on this page are from the Power Systems hardware documentation, and the Descriptions apply to a single CEC enclosure or I/O enclosure. The Action and Failing Item fields are modified as appropriate for DS8000® architecture and repair methods.
SRCs missing from the following tables might be found on the Power Systems online documentation. You can use the SRC description as is to define the problem. Do not use the Action and Failing Item without contacting the next level of support first.
To display the Power Systems hardware online documentation, go to the Web site http://www-01.ibm.com/support/knowledgecenter/.
- In the IBM Systems Hardware Information right content pane, click POWER6 reference codes listing.

Table 1. (A7xxxxxx) Licensed Internal Code (LIC) Reference Codes
SRC	Description/Action	Failing Item
A7xx0102	Platform LIC detected an error A machine check occurred during IPL. Words 2 to 9 of this SRC contain additional diagnostic information. Record SRC words 1 through 9 before attempting to IPL again and report the problem to next level of support.	SVCDOCS
A7xx0103	Platform LIC failure 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. The platform Licensed Internal Code (LIC) detected an internal problem. Collect all the SRC words and the platform system dump, and then contact your next level of support.	LICCODE
A7xx0104	Platform LIC failure Machine check, undefined error occurred.	LICCODE
A7xx0105	Platform LIC detected an error More than one request to terminate the system was issued.	NEXTLVL
A7xx0106	Platform LIC failure 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. A secondary failure due to an invalid SRC occurred when the platform attempted to terminate. Collect all the SRC words and the platform system dump, and then contact your next level of support.	LICCODE
A7xx0107	Platform LIC failure The server detected an unrecoverable machine check condition. Collect all the words of the SRC and the platform dump and send to your system manufacturer for analysis.	SVCDOCS
A7xx0200	System firmware has experienced a low storage condition No immediate action is necessary. Continue running the system normally. At the earliest convenient time or service window, work with your service provider to take a platform dump and reIPL the system.	SVCDOCS
A7xx0302	Platform LIC failure 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. Perform a platform system dump and notify your service provider. IPL the system.	LICCODE
A7xx0441	Service processor failure 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. The platform encountered an error early in the IPL or termination process.	SVCPROC NEXTLVL
A7xx0443	Service processor failure	SVCPROC NEXTLVL
A7xx0601	System log entry only, no service action required Support can use this SRC and associated data to determine why the time of day for a partition was lost. No corrective action is required.
A7xx0602	Platform LIC detected an error 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. Platform Licensed Internal Code (LIC) detected an error condition. The second word indicates the severity of the error and the specific error condition. If word 2 is not 10000A01 the error is informational only. If word 2 is 10000A01 then record the SRC words and call your next level of support.	NEXTLVL
A7xx0611	System clock problem Work with the FRU list in the serviceable event view if there is one, otherwise use the FRU list documented here to determine the parts to exchange. For systems managed by an HMC, use the ASM interface to reset the system clock at power on standby. For systems without an HMC, you can ignore this error. If the error occurs a second time, call your next level of support.	SVCDOCS
A7xx0621	System log entry only, no service action required No service action required.	SVCDOCS
A7xx0641	Platform LIC detected an error. A platform LIC failure occurred. Perform a platform dump and contact your next level of support.	SVCDOCS
A7xx0650	Platform LIC detected an error Resource management was unable to allocate main storage. A platform dump was started. Words 2 to 9 of this SRC contain additional diagnostic information. Record SRC words 1 through 9. Collect the platform dump and the configuration of the memory allocation for all partitions on this system. Provide the platform dump, configuration data, and the recorded SRC information to your next level of support.	NEXTLVL
A7xx0651	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 this is a serviceable event, then work with the FRU list in the serviceable event view if there is one. Otherwise, use the FRU list documented in the Failing Items column to determine the parts to exchange. If the system did not log this error as a serviceable event, then no service action is required.
A7xx0803 to 0804	System log entry only, no service action required.
A7xx0A00	System log entry only, no service action required A user request initiated an I/O tower/drawer power off. No corrective action is required.
A7xx0A10	System log entry only, no service action required No action is required, unless the Hardware Management Console (HMC) indicates that the concurrent platform firmware update failed. In that case, the system must be re-IPLed in order for the firmware update to occur. Collect the error log data for this SRC and contact PHYP development to debug the problem.	NEXTLVL
A7xx1150 to A7xx1151	System log entry only, no service action required No action needed unless a serviceable event was logged. If a serviceable event was logged, resolve that error.	SVCDOCS
A7xx1152	System log entry only, no service action required No service action is required for this event. If there is a A7001150 SRC present, then the service processor was reset automatically to correct for the communications problem. If something more severe occurred there will be a SRC requiring a service action logged as well.
A7xx1160	Service processor failure 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. The platform encountered an error communicating with the service processor. The platform code attempts a graceful shutdown of partitions and powers off the server after a certain time, or when the last partition indicates shutdown, whichever comes first.	SVCPROC LICCODE
A7xx1161	System log entry only, no service action required The platform encountered a service processor event indicating that the power status has changed. Note that this is A7xxxxxx only.
A7xx1730	Platform LIC detected an error 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. The VPD for the system is not what was expected at IPL. The IPL will not continue. Call your next level of support.	CAPACTY
A7xx1731	Platform LIC detected an error 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. The VPD for the system is not what was expected at IPL. Call your next level of support.	MEMDIMM
A7xx1732	Platform LIC detected an error 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. The VPD for the system is not what was expected at IPL. The VPD on a processor card is not correct. Call your next level of support.	NEXTLVL
A7xx1733	Platform LIC detected an error 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. The VPD for the system is not what was expected at IPL. The VPD on a memory card is not correct. Call your next level of support.	NEXTLVL
A7xx173A	System log entry only, no service action required A VPD collection overflow occurred, no service action required. If a system problem is suspected, look for other errors in the serviceable event view.	NEXTLVL
A7xx173B	Platform LIC detected an error A platform LIC failure occurred during VPD collection. Look for and correct errors with SRCs of the form B1xxxxxx in the Serviceable Event View. If that does not correct the problem, contact your next level of support.	SVCDOCS
A7xx4091	User intervention required The system power on has reached a standby state. The firmware does not have partition configuration information. Call the next level of support. They may need to activate one or more partitions to change the system from a standby state to an operating state.
A7xx4400	There is a platform dump to collect 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. Use the operating system's interface designated to collect platform dumps.	SVCDOCS
A7xx4401	Platform LIC failure 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. The platform LIC detected an internal problem. Contact your next level of support.	NEXTLVL
A7xx4402	Platform LIC detected an error A platform LIC error occurred while attempting to allocate the memory necessary to create a platform resource dump.	NEXTLVL
A7xx4700	Platform LIC detected an error A problem occurred when initializing, reading, or using system VPD. Capacity on Demand is not available because the stored activation code is not valid. Contact your next level of support to verify your activation code. If the activation code is valid, replace the VPD card.	SVCDOCS CAPACTY
A7xx4701	Platform LIC detected an error A problem occurred when initializing, reading, or using system VPD. The IPL failed. 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.	CAPACTY
A7xx4703	Platform LIC failure 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. A problem occurred when initializing, reading, or using system VPD.	LICCODE
A7xx4704	Platform LIC detected an error The Capacity on Demand function is no longer available. Look for and correct errors with SRCs of the form 1xxxxxxx in the Serviceable Event View. If that does not correct the problem, or no errors were found, contact your next level of support.	SVCDOCS
A7xx4705	Platform LIC failure 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. A problem occurred when initializing, reading, or using system VPD.	LICCODE
A7xx4710	Platform LIC detected an error This SRC is always of the form A700xxxx. A communications problem with the service processor occurred. Look for errors with SRCs of the form 1xxxxxxx or A7xx69xx in the Serviceable Event View. Work those errors. If no such errors are present, no service action is required.	SVCDOCS LICCODE CAPACTY
A7xx4712	Platform LIC detected an error 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. A problem occurred when initializing, reading, or using system VPD.	CAPACTY
A7xx4713	Platform LIC has detected an error The VPD card has been exchanged with a not valid card. Reinstall the original VPD card in the system.	SVCDOCS
A7xx4714	Platform LIC has detected a new VPD card The new VPD card requires new activation codes. Enter the new activation codes.	SVCDOCS
A7xx4715	Platform LIC detected an error A problem occurred when initializing, reading, or using system VPD. 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. Look for errors with SRCs of the form 1xxxxxxx in the Serviceable Event View. Work those errors first. If that does not correct the problem, contact your next level of support.	SVCDOCS CAPACTY SVCPROC
A7xx4716	User intervention required The Capacity on Demand activation code recovery period has been started. Either obtain more capacity or allocate fewer resources.	SVCDOCS
A7xx4730	Platform LIC detected an error This SRC is always of the form A700xxxx. A problem occurred when configuring the logical partitions on the system. More resources were allocated than there are available for use. Either obtain more capacity or allocate fewer resources.	SVCDOCS LPARCFG
A7xx4731	Platform LIC detected an error This SRC is always of the form A700xxxx. A problem occurred initializing, reading, or using system VPD. No service action is required.	CAPACTY
A7xx4733	Platform LIC failure This SRC is always of the form A700xxxx. A problem occurred initializing, reading, or using system VPD. No service action is required.	LICCODE
A7xx4740	Platform LIC detected an error An incorrect activation code has been detected. Resources associated with this activation code have been disabled. Enter a valid activation code.	SVCDOCS
A7xx4741	Platform LIC detected an error The number of allowable attempts to enter a valid activation code has been exceeded. A system IPL is required in order to retry entering a valid activation code.	SVCDOCS
A7xx4742	Platform LIC detected an error A communications problem with the service processor occurred. No Capacity on Demand changes can be made. Look for errors with SRCs of the form A1xxxxxx or A7xx69xx in the Serviceable Event View. Work those errors first. If that does not correct the problem, contact your next level of support.	SVCDOCS
A7xx4747	User intervention required One hour remains until the On/Off Capacity on Demand request expires. All temporary resources should be removed from partitions before the request expires.	SVCDOCS
A7xx4748	User intervention required One hour remains until the Reserve Capacity on Demand request expires. In order to reactivate temporary resources, a new Reserve Capacity on Demand enablement code is required.	SVCDOCS
A7xx4749	User intervention required One hour remains until the Trial Customer on Demand activation expires. All temporary resources should be removed from partitions before the request expires.	SVCDOCS
A7xx4750	A Capacity on Demand change has been detected A Reserve Capacity on Demand resource has been activated.	SVCDOCS
A7xx4788	System log entry only, no service action required The data obtained from the system is not what was expected. The IPL will continue. Should other errors occur, call your next level of support.
A7xx47C1	Capacity on Demand data mismatch The data obtained from the system is not what was expected. The system will perform a slow IPL in order to obtain the correct data. If other errors occur, contact your next level of support.
A7xx47CB	Fast system IPL changed to slow system IPL. The data obtained from the system is not what was expected. The system will perform a slow IPL in order to obtain the correct data. If other errors occur, contact your next level of support.
A7xx47CD	Platform LIC detected an error. The server detected a not valid Capacity On Demand activation and terminated the system. The allocated resources for the system might exceed those that are available for use.	SVCDOCS
A7xx47FF	System log entry only, no service action required. The Capacity on Demand History Log has been written to the error log. No service action is required.	SVCDOCS
A7xx5120	Platform LIC detected an error 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. If the system is not exhibiting problematic behavior, this error can safely be ignored. Otherwise, contact your next level of support.	NEXTLVL
A7xx5121	Platform LIC failure A Licensed Internal Code program exception occurred. Platform Licensed Internal Code detected a programming problem for which a platform dump may have been initiated. Send the system error log and the platform dump, if it occurred, to your next level of support.	NEXTLVL
A7xx5122	Platform LIC detected an error Platform Licensed Internal Code detected that an IOP request failed. This error indicates a failure during a search for the load source. There may be a number of these failure prior to finding a good load source. This is normal. If a B2xx3110 error is logged, a B2xx3200 or B7005122 may be posted to the control panel. Work the B2xx3110 error in the Serviceable Event View. If the system IPL hangs at B2xx3200 or B7005122 and you cannot check the SRC history, perform the actions indicated for the B2xx3110 SRC.	SVCDOCS
A7xx5123	Platform LIC detected an error. A Licensed Internal Code program exception or data collection occurred. This may indicate an IOP programming problem or an IO Adapter boot problem. Look for other errors. If no other errors are present, Licensed Internal Code has recovered from any exception conditions, or this SRC has logged informational platform boto or hardware data.
A7xx5190	Operating System error 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. The platform detected a problem in an Operating System. Check for errors in the partition ID specified in word 4 of the SRC. If correcting those errors does not correct the problem, or if you find no errors, contact your next level of support.	SVCDOCS
A7xx5191	Platform LIC detected an error. A virtual adapter configuration error occurred A partition tried to use a virtual adapter which is associated with another virtual adapter in a remote partition and virtual slot. However, either no virtual adapter is configured there, or the wrong kind of virtual adapter is configured there. The partition ID of the virtual adapter with the problem is in word 4 of the SRC (in hexadecimal format). The virtual slot number of the adapter with the incorrect configuration is the last four digits of word 6 of the SRC (in hexadecimal format). Use the Hardware Management Console (HMC) to verify or reconfigure the incorrect virtual adapter configuration. If the configuration is correct, continue with the next failing item in the list.	SVCDOCS LICCODE
A7xx5209	Platform LIC detected an error. System Licensed Internal Code detected an IOP timeout during IOP IPL. This may be caused by loose connections, improperly seated cards, media, or removable media drive not in a ready state. Look for other errors.
A7xx5219	Platform LIC detected an error. Information only, no service action required. Licensed Internal Code program exception occurred. An IOP signalled to system Licensed Internal Code that it had entered a critical internal state. Licensed Internal Code automatically attempted to restart the IOP.
A7xx5300	Platform LIC detected a failure while partitioning resources 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. Platform partitioning code encountered an error. This SRC represents a large number of possible problems, most of which involve the platform Licensed Internal Code (LIC). Work any error logs found in the Serviceable Event View. If this fails to correct the problem, or if there are no other errors, contact your next level of support.
A7xx5301	User intervention required. System detected a problem with the Logical Partition (LPAR) Configuration. Use the Hardware Management Console to reconfigure the LPAR configuration. If in Recovery state then use the HMC to perform "Recovering partition data on a managed system". Use HMC to activate partitions.	SVCDOCS
A7xx5400	A resource has been disabled due to hardware problems 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. The platform detected a problem with a processor. The processor is not functional. Look in the Serviceable Event View for a A1xxxxxx error that implicates a processor. If the Serviceable Event View contains no A1xxxxxx error, or if resolving the error fails to correct the problem, contact your next level of support.	SVCDOCS
A7xx5600	Problem initializing, reading or using system VPD Look for other errors in the Serviceable Event View. If no other errors have been logged, contact your next level of support.	NEXTLVL
A7xx5601	Platform LIC failure 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. There was a problem initializing, reading, or using system VPD.	NEXTLVL
A7xx6900	PCI host bridge failure 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. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.	SIIOADP PRI_PCI MA_BRDG MABIP50 PIOCARD
A7xx6906	System bus error 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.	SIIOADP
A7xx6907	System bus error 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.	SIIOADP LICCODE
A7xx6908	System bus error 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.	PRI_PCI
A7xx6909	System bus error 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.	PRI_PCI LICCODE
A7xx6944	Platform LIC detected an error. A system bus appears to be empty. If the bus is not empty, a hardware or configuration problem might exist. Look for other errors.
A7xx6950	Platform LIC detected an error. A platform dump has occurred. The system has lost all the configured system settings (such as the HMC access and ASMI passwords, time of day, network configuration, hardware deconfiguration policies, etc.) that you might have set through user interfaces. Also, the system has lost the platform error logs and partition-related information, and the service processor is reset. Perform the recovery actions for the SVCPROC FRU but do not replace the service processor. The platform dump should be sent to your service provider.	SVCDOCS
A7xx6951	Platform LIC detected an error. An error occurred because a partition needed more NVRAM than was available. The partition is still functional, but is operating in a degraded mode. Configuration information may be lost at the next IPL. To make more NVRAM available, delete one or more partitions.	SVCDOCS
A7xx6970	PCI host bridge failure 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.	SIIOADP PRI_PCI MA_BRDG MABIP50
A7xx6971	PCI secondary bus failure 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.	MABIP50 MA_BRDG MASBUS PIOCARD
A7xx6972	System bus error 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.	MA_BRDG PRI_PCI
A7xx6973	System bus error 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. If the first half of word 7 is not 0001, remove SVCPROC (the service processor) from the list of possible FRUs.	PIOCARD MA_BRDG SVCPROC PRI_PCI MASBUS
A7xx6974	IOP rejected the assignment of an IOA An I/O Processor rejected the assignment of an I/O Adapter during the IPL of an i5/OS partition. If the partition IPLed successfully, this event is logged for information only. No service action is required. If the partition failed to IPL, replace the IOA. If that does not resolve the problem, replace the IOP that controls the IOA. The Direct Select Address (DSA) of the IOA is in word 7 of the SRC. In order to find the location of the IOA, see DSAXlate to get the unit type in which the IOA is located. Then, using the DSA and unit type, go to Table 3 Table 4 to find the location of the IOA.
A7xx6980	Network Interface Controller (NIC) resource failure 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. Note: A fiber optic cleaning kit might be required for optical HSL connections.	SICNTRL OPT_CLN
A7xx6981	High Speed Link (HSL) I/O bridge failure If you find a A1xxxxxx SRC logged on the same tower as one of the FRUs here, and then close this problem and work the A1xxxxxx SRC. Use the unit value of the location codes to determine if the tower is the same. 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.	SIIOADP
A7xx6982	High Speed Link (HSL) connection failure Perform the RIOIP11 procedure. 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. Note: A fiber optic cleaning kit might be required for optical HSL connections.	SVCDOCS HSL_LNK OPT_CLN FRPORT TOPORT
A7xx6983	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. The four rightmost characters of word 4 in the reference code represent the Program Return Code (PRC), which describes the problem detected. The four leftmost digits of word 7 represent the loop number in hexadecimal format. Convert the loop number to decimal format before comparing it to loop numbers shown in serviceable event views and service tools. To determine the problem, find the PRC in the list below. Note: The FRU description in the serviceable event view might already contain a message that identifies the problem. xxxx0008 indicates the system serial number is not set. Set the serial number on the system unit. If the problem persists contact your next level of support. xxxx3201 indicates there are clustered systems on multiple HSL/RIO loops. You will need to ensure all clustered systems are on the same HSL/RIO loop. xxxx3217 indicates there is a model 5791, 5792, or 5794 IO drawer on a loop with clustered systems. This is not a supported configuration. This ends the procedure.	SVCDOCS
A7xx6984	System log entry only, no service action required An HSL loop has switched to its alternate path. This is an informational SRC only. Word 7 of the SRC contains the loop number in the leftmost 4 digits. The loop number is in hexadecimal format. You must convert the hexadecimal loop number into decimal format to recognize the loop number. This SRC can be caused by a tower on the HSL loop powering off. This SRC might also appear in a Serviceable Event View you are using, with a A7006982 or A7006981 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. Service the other SRC if present.
A7xx6985	High Speed Link (HSL) loop status message This is a serviceable event only if this error is in a serviceable event view such as the Service Focal Point on HMC, the SAL on i5/OS, the Diagnostic Results Log on AIX® or Linux®, or the ASMI Error Log. If this is a serviceable event then perform RIOIP12. Otherwise if this is NOT a serviceable event then to determine what this SRC means use symbolic FRU SIRSTAT. 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. Note: A fiber optic cleaning kit might be required for optical HSL connections.	SVCDOCS HSL_LNK OPT_CLN FRPORT TOPORT
A7xx6986	System bus error 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. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.	TWRCARD PWRCBL
A7xx6987	High Speed Link (HSL) connection failure 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. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.	HSL_LNK OPT_CLN
A7xx6990	Service processor failure 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. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.	SVCPROC
A7xx6991 t	Platform LIC failure 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.	LICCODE
A7xx6992	Service processor reset occurred If this SRC does not appear in a serviceable event view then no service action is required. The service processor reset was successful. If this SRC appears in a serviceable event view, the service processor reset failed. The system will continue to run if a redundant service processor was available. If a redundant service processor was not available, the system terminated. Look for and correct errors with SRCs of the form B1xx xxxx in the Serviceable Event View that were logged within approximately one hour of the time this SRC occurred. If there are no B1xx xxxx SRCs, or they do not resolve the problem, do the following: If there is only one service processor, replace it. Ensure that the firmware is at the most recent code level. If there is more than one service processor, use the Advanced Server Management Interface (ASMI) to find the Garded service processor (the one currently not being used) and replace it. Ensure that the firmware is at the most recent code level.	SVCDOCS
A7xx6993	Service processor failure 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. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.	SVCPROC LICCODE
A7xx6994	Service processor failure 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. If the Serviceable Event View is not available then use the failing item list presented here for servicing this reference code.	SVCPROC
A7xx6995	User intervention required The system is in the process of terminating. When all the partitions have terminated, an SRC indicating the exact cause will be shown on the operator panel. If the system does not terminate in a reasonable amount of time, one or more partitions may need to be terminated manually. If this is not possible, re-IPL the system and look for errors. If no errors are found, contact your next level of support.	SVCPROC
A7xx69C2	System log entry only, no service action required. Information only, no service action required. HSL OptiConnect normal connection to another system or partition. HSL OptiConnect established connection normally. The local system or partition is participating in HSL Opticonnect with other systems or partitions on the same HSL loop.
A7xx69C3	System log entry only, no service action required. Information only, no service action required. Opticonnect normal remote disconnection from OptiConnect participation. HSL Opticonnect disconnected normally from a remote node. The local system or partition has stopped participating in HSL Opticonnect with the remote system or partition on the same HSL loop. Possible reasons include: A remote system or partition went off line due to a normal power off or because HSL Opticonnect became disabled.
A7xx69C6	Platform LIC detected an error. Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. The problem, which most likely originates with the remote system or partition, probably requires intervention at the remote system. Examine both the local and remote HSL OptiConnected systems or partitions for problems on this HSL loop. Possible reasons include: A fatal software or hardware error in the remote system or partition, or a power failure in the remote system. If a complete HSL loop did not exist before this error occurred, 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. 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, examine the Service Action Log (SAL) or serviceable event view. Look for HSL failures that occurred on the same HSL loop at approximately the same time as this error. Examine the remote system or partition for problems. If the remote system or partition is powered on and IPL'd, examine the SAL or serviceable event view on the remote system or partition. Look for problems on the same HSL loop that occurred at approximately the same time as this error. 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. When the remote system is IPL'd, it will automatically reconnect with this system or partition. If you find no problems with either the local or the remote systems or partitions, collect all the Product Activity Log (PAL) information for this failure on both systems. Be sure to record all words in the SRC. Contact your next level of support.	SVCDOCS LICCODE
A7xx69C7	Platform LIC detected an error. Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. Licensed Internal Code will attempt to recover from the error. Intervention at the local or remote system or partition might be required. Possible causes include time out, hang, or hardware failure. The problem may be with the local system or partition or the remote system or partition. If a complete HSL loop did not exist before this error occurred, 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. Check for SRCs with FRUs that indicate problems 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, examine the SAL or serviceable event view. 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. Correct any HSL or NIC problems you find with the remote and local systems or partitions. If you find no problems with either the local or the remote systems or partitions, collect all the PAL information for this failure on both systems. Be sure to record all words in the SRC. Contact your next level of support.	SVCDOCS LICCODE
A7xx69C8	Platform LIC detected an error. Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. The local system or partition disconnected from a remote system or partition due to an unexpected event or failure. All of the HSL OptiConnect connections on this loop will be in a failed state. Licensed Internal Code will attempt to recover from the error. Intervention at the local or remote system or partition might be required. 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, 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. Examine the remote system or partition for problems. On the remote system or partition, examine the SAL or serviceable event view. Look for problems on the same HSL loop or with the Network Interface Controller that occurred at approximately the same time as this error. 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. 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. Be sure to record all words in the SRCs. Contact your next level of support.	SVCDOCS LICCODE
A7xx69C9	Platform LIC detected an error. Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. 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. Possible causes are: Licensed Internal Code problem where the local bus unit is offline. Licensed Internal Code problem where the remote bus unit is offline. On the local system or partition, examine the SAL or the serviceable event view. Look for HSL Opticonnect failures that occurred at approximately the same time as this error. Examine the remote system or partition for problems. On the remote system or partition, examine the SAL or the serviceable event view. Look for HSL Opticonnect problems that occurred at approximately the same time as this error. Collect all the Product Activity Log information for this failure on all systems and partitions on this HSL loop. Be sure to record all words in the SRCs. Contact your next level of support.	SVCDOCS LICCODE
A7xx69CF	Platform LIC detected an error. Abnormal or unexpected HSL OptiConnect disconnection from a remote system or partition. Licensed Internal Code internal error. All systems participating in HSL OptiConnect will be disconnected. You must re-IPL the system to recover. Before re-IPL'ing the system, start a platform dump. On the local system or partition, after getting the dump, examine the SAL or the serviceable event view. Look for HSL Opticonnect failures that occurred at approximately the same time as this error. Examine the remote systems or partitions for problems. On the remote systems or partitions, examine the SAL or the serviceable event view. Look for HSL Opticonnect problems that occurred at approximately the same time as this error. Collect all the PAL information for this failure on all systems and partitions on this HSL loop. Be sure to record all words in the SRCs. Contact your next level of support.	SVCDOCS LICCODE
A7xx69E1	Host Channel Adapter The 12X Host Channel Adapter has failed.	SVCDOCS
A7xx69E2	Platform LIC failure A Platform Licensed Internal Code error occurred related to 12X technology. The system will continue to run with this Host Channel Adapter disabled. Perform a platform dump prior to IPLing the system. An IPL is required to recover the Host Channel Adapter.	LICCODE
A7xx69E3	System log entry only, no service action required Part of the HCA chip failed but was not terminating. When thresholded, these errors will result in a A70069E1.
A7xx69E4	An invalid High Speed Link (HSL) configuration was detected An error was detected in the fabric. Have the customer check for problems reported at the IBM Network Manager. This includes cases such as path migration, etc.	SVCDOCS
A7xx69E5	System log entry only, no service action required A 12X communications error occurred. Unrecognized command from Subnet Manager. Does not require service.
A7xx69E6	System log entry only, no service action required The cable connection to the switch is broken. Verify that the cable is connected and the switch is powered on. After repairing the problem, verify that the connection has been restored by using the IBM Network Manager. Does not require service.
A7xx69E7	System log entry only, no service action required The cable connection to the switch has been restored. No service action required.
A7xx69E9	System log entry only, no service action required Initial communication has occurred with the Subnet Manager. No service action required. The CEC and switch firmware are now communicating.
A7xx69EA	System log entry only, no service action required Reported when the logical switch receives a setPortInfo for the switch management port that sets a new SM LID. 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. This proves that there is 2-way communication. 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. No service action required.
A7xx69EB	User intervention required A 12X configuration error was detected by the HCA. Verify that the configuration is correct at the HCA. The Port 1 and 2 configurations conflict.	SVCDOCS
A7xx69EC	User intervention required A 12X adapter in the server does not support connections to I/O enclosures. Upgrade the adapter at the location given in the serviceable event view to a new version. Contact support for assistance.	SVCDOCS
A7xx69ED	System log entry only, no service action required A 12X cable connection initialized to a lower signal frequency. The link is operational but operating at a bandwidth below its rated capacity. This may lead to degraded I/O throughput.
A7xxBAD1	Platform firmware detected an error Platform firmware detected unexpected or not valid data returned from non-platform firmware. Contact your next level of support.	NEXTLVL
A7xxC2AC	System log entry only, no service action required The Capacity on Demand License acceptance has completed. No corrective action is required.	SVCDOCS
A7xxF103	Platform LIC failure 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. The platform LIC detected an internal problem. Collect all the SRC words and the platform system dump, and then contact your next level of support.	LICCODE
A7xxF104	Operating System error Platform LIC terminated a partition. Platform LIC terminated a partition with an unresponsive Operating System. Collect all the SRC words and the platform system dump, and then contact your next level of support.	NEXTLVL
A7xxF105	Platform LIC detected an error 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. The platform LIC detected an internal problem. Collect all the SRC words and the platform system dump, and then contact your next level of support.	NEXTLVL
A7xxF10A	Platform LIC detected an error. Look for errors with SRCs of the form B1xx xxxx in the Serviceable Event View. Work those errors first. If that does not correct the problem, collect all the SRC words and the platform system dump, then contact your next level of support.	SVCDOCS
A7xxF10B	A resource has been disabled due to hardware problems. 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. The platform detected a problem with a processor. The processor is not functional. Look in the Serviceable Event View for a B1xx xxxx error that implicates a processor. If the Serviceable Event View contains no B1xx xxxx error, or if resolving the error fails to correct the problem, contact your next level of support	ANYPROC
A7xxF120	Platform firmware detected an error. The platform is unable to support the requested architecture options requested by the operating system with ibm.client-architecture-support interface.