B7xxyyyy Licensed internal code SRCs

A B7xxyyyy system reference code (SRC) is an error code or event code that is related to licensed internal code.

Table 1 describes the system reference codes that might be displayed if system firmware detects a problem. Suggested actions to correct the problem are also listed.

Note: For problems persisting after completing the suggested actions, see Checkout procedure and Solving undetermined problems.
Table 1. B7xxyyy Licensed internal code SRCs
  • Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved. If an action solves the problem, then you can stop performing the remaining actions.
  • See Parts listing, type 7891 to determine which components are CRUs and which components are FRUs.
B700 xxxx Error Codes Description Action
0102 System firmware detected an error. A machine check occurred during startup.
  1. Collect the event log information.
  2. Go to Isolating firmware problems.
0103 System firmware detected a failure
  1. Collect the event log information.
  2. Collect the platform dump information.
  3. Go to Isolating firmware problems.
0104 System firmware failure. Machine check, undefined error occurred.
  1. Check for server firmware updates.
  2. Update the firmware.
0105 System firmware detected an error. More than one request to terminate the system was issued. Go to Isolating firmware problems.
0106 System firmware failure.
  1. Collect the event log information.
  2. Collect the platform dump information.
  3. Go to Isolating firmware problems.
0107 System firmware failure. The system detected an unrecoverable machine check condition.
  1. Collect the event log information.
  2. Collect the platform dump information.
  3. Go to Isolating firmware problems.
0200 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 IBM® Support to collect a platform dump and restart the system; then, go to Isolating firmware problems.
0201 System firmware detected an error. No immediate action is necessary.

Continue running the system normally. At the earliest convenient time or service window, work with IBM Support to collect a platform dump and restart the system; then, go to Isolating firmware problems.
0202 Informational system log entry only. No corrective action is required.
0302 System firmware failure
  1. Collect the platform dump information.
  2. Go to Isolating firmware problems.
0441 Service processor failure. The platform encountered an error early in the startup or termination process.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
0443 Service processor failure.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
0601 Informational system log entry only. No corrective action is required.
Note: This code and associated data can be used to determine why the time of day for a partition was lost.
0602 System firmware detected an error condition.
  1. Collect the event log information.
  2. Go to Isolating firmware problems.
0611 There is a problem with the system hardware clock; the clock time is invalid. Use the operating system to set the system clock.
0621 Informational system log entry only. No corrective action is required.
0641 System firmware detected an error.
  1. Collect the platform dump information.
  2. Go to Isolating firmware problems.
0650 System firmware detected an error. Resource management was unable to allocate main storage. A platform dump was initiated.
  1. Collect the event log.
  2. Collect the platform dump data.
  3. Collect the partition configuration information.
  4. Go to Isolating firmware problems.
0651 The system detected an error in the system clock hardware

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
0803 Informational system log entry only. No corrective action is required.
0804 Informational system log entry only. No corrective action is required.
0A00 Informational system log entry only. No corrective action is required.
0A01 Informational system log entry only. No corrective action is required.
0A10 Informational system log entry only. No corrective action is required.
1150 Informational system log entry only. No corrective action is required.
1151 Informational system log entry only. No corrective action is required.
1152 Informational system log entry only. No corrective action is required.
1160 Service processor failure
  1. Go to Isolating firmware problems.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
1161 Informational system log entry only. No corrective action is required.
1730 The VPD for the system is not what was expected at startup. Replace the management card, as described in Removing the tier 2 management card and Installing the tier 2 management card.
1731 The VPD on a memory DIMM is not correct and the memory on the DIMM cannot be used, resulting in reduced memory. Replace the MEMDIMM symbolic CRU, as described in Service processor problems.
1732 The VPD on a processor card is not correct and the processor card cannot be used, resulting in reduced processing power.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
1733 System firmware failure. The startup will not continue. Look for and correct B1xxxxxx errors. If there are no serviceable B1xxxxxx errors, or if correcting the errors does not correct the problem, contact IBM support to reset the server firmware settings.
Attention: Resetting the server firmware settings results in the loss of all of the partition data that is stored on the service processor. Before continuing with this operation, manually record all settings that you intend to preserve.

The service processor reboots after IBM Support resets the server firmware settings.

If the problem persists, Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
173A A VPD collection overflow occurred.
  1. Look for and resolve other errors.
  2. If there are no other errors:
    1. Update the firmware to the current level, as described in Updating the firmware.
    2. You might also have to update the management module firmware to a compatible level.
173B A system firmware failure occurred during VPD collection. Look for and correct other B1xxxxxx errors.
4091 Informational system log entry only. No corrective action is required.
4400 There is a platform dump to collect
  1. Collect the platform dump information.
  2. Go to Isolating firmware problems.
4401 System firmware failure. The system firmware detected an internal problem. Go to Isolating firmware problems.
4402 A system firmware error occurred while attempting to allocate the memory necessary to create a platform dump. Go to Isolating firmware problems.
4705 System firmware failure. A problem occurred when initializing, reading, or using the system VPD. The Capacity on Demand function is not available. Restart the system.
4710 Informational system log entry only. No corrective action is required.
4714 Informational system log entry only. No corrective action is required.
4715 A problem occurred when initializing, reading, or using system VPD. Replace the management card, as described in Removing the tier 2 management card and Installing the tier 2 management card.
4750 Informational system log entry only. No corrective action is required.
4788 Informational system log entry only. No corrective action is required.
47CB Informational system log entry only. No corrective action is required.
5120 System firmware detected an error If the system is not exhibiting problematic behavior, you can ignore this error. Otherwise, go to Isolating firmware problems.
5121 System firmware detected a programming problem for which a platform dump may have been initiated.
  1. Collect the event log information.
  2. Collect the platform dump information.
  3. Go to Isolating firmware problems.
5122 An error occurred during a search for the load source. If the partition fails to startup, go to Isolating firmware problems. Otherwise, no corrective action is required.
5123 Informational system log entry only. No corrective action is required.
5190 Operating system error. The server firmware detected a problem in an operating system. Check for error codes in the partition that is reporting the error and take the appropriate actions for those error codes.
5191 System firmware detected a virtual I/O configuration error.
  1. Use the Integrated Virtualization Manager (IVM) or management console to verify or reconfigure the invalid virtual I/O configuration.
  2. Check for server firmware updates; then, install the updates if available.
5209 Informational system log entry only. No corrective action is required.
5219 Informational system log entry only. No corrective action is required.
5300 System firmware detected a failure while partitioning resources. The platform partitioning code encountered an error. Check the management-module event log for error codes; then, take the actions associated with those error codes.
5301 User intervention required. The system detected a problem with the partition configuration. Use the Integrated Virtualization Manager (IVM) or management console to reallocate the system resources.
5302 An unsupported Preferred Operating System was detected.

The Preferred Operating System specified is not supported. The IPL will not continue.

Work with IBM support to select a supported Preferred Operating System; then, re-IPL the system.
5303 An unsupported Preferred Operating System was detected.

The Preferred Operating System specified is not supported. The IPL will continue.

Work with IBM support to select a supported Preferred Operating System; then, re-IPL the system.
5304 The number of available World Wide Port Names (WWPN) is low. https://www-912.ibm.com/supporthome.nsf/document/51455410
5305 There are no remaining World Wide Port Names (WWPN). https://www-912.ibm.com/supporthome.nsf/document/51455410
5400 System firmware detected a problem with a processor.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
5442 System firmware detected an error.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
54DD Informational system log entry only. No corrective action is required.
5600 Informational system log entry only. No corrective action is required.
5601 System firmware failure. There was a problem initializing, reading, or using system location codes. Go to Isolating firmware problems.
5602 The system has out-of-date VPD LIDs. Check for server firmware updates; then, install the updates if available.
5603 Enclosure feature code and/or serial number not valid. Verify that the machine type, model, and serial number are correct for this server.
6900 PCI host bridge failure
  1. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
  2. If the problem persists, use the PCI expansion card (PIOCARD) problem isolation procedure to determine the failing component.
6906 System bus error

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6907 System bus error
  1. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
  2. Go to Isolating firmware problems.
6908 System bus error

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6909 System bus error
  1. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
  2. Go to Isolating firmware problems.
6911 Platform LIC unable to find or retrieve VPD LID file. Check for server firmware updates; then, install the updates if available.
6912 Platform LIC unable to find or retrieve VPD LID file. Check for server firmware updates; then, install the updates if available.
6944 Informational system log entry only. No corrective action is required.
6950 A platform dump has occurred.
  1. Collect the platform dump information.
  2. Go to Isolating firmware problems.
6951 An error occurred because a partition needed more NVRAM than was available. Use the Integrated Virtualization Manager (IVM) or management console to delete one or more partitions.
6952 Informational system log entry only. No corrective action is required.
6953 PHYP NVRAM is unavailable after a service processor reset and reload. Go to Isolating firmware problems.
6954 Informational system log entry only. No corrective action is required.
6955 Informational system log entry only. No corrective action is required.
6956 An NVRAM failure was detected. Go to Isolating firmware problems.
6965 Informational system log entry only. No corrective action is required.
6970 PCI host bridge failure
  1. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
  2. If the problem persists, use the PCI expansion card (PIOCARD) problem isolation procedure to determine the failing component.
6971 PCI bus failure
  1. Use the PCI expansion card (PIOCARD) problem isolation procedure to determine the failing component.
  2. If the problem persists, replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6972 System bus error

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6973 System bus error
  1. Use the PCI expansion card (PIOCARD) problem isolation procedure to determine the failing component.
  2. If the problem persists, replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6974 Informational system log entry only. No corrective action is required.
6978 Informational system log entry only. No corrective action is required.
6979 Informational system log entry only. No corrective action is required.
697C Connection from service processor to system processor failed.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6980 RIO, HSL or 12X controller failure

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6981 System bus error.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6984 Informational system log entry only. No corrective action is required.
6985 Remote I/O (RIO), high-speed link (HSL), or 12X loop status message.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6987 Remote I/O (RIO), high-speed link (HSL), or 12X connection failure.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6990 Service processor failure.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6991 System firmware failure Go to Isolating firmware problems.
6993 Service processor failure
  1. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
  2. Go to Isolating firmware problems.
6994 Service processor failure.

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
6995 Informational system log entry only. No corrective action is required.
69C2 Informational system log entry only. No corrective action is required.
69C3 Informational system log entry only. No corrective action is required.
6A21 PCI-E switch had a permanent unrecoverable (internal) chip failure. All downstream I/O is failed.
  1. Collect error logs and info logs.
  2. Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly. Send the failed FRU and the data to IBM for fault analysis.
6A22 PCI-E switch had a recoverable failure, however, all downstream I/O had to be failed during recovery. Recovery for the PCI-E switch failure is being attempted. If the recovery is successful, no other SRC is logged. Once the PCI-E switch is recovered, the downstream I/O adapters should recover. The partition or application associated with the failed downstream I/O might have to be restarted.
6A23 PCI-E switch recovery failure. All downstream I/O is failed. If there are any AIX® or Linux errors logged against I/O adapters on this switch, do not replace any I/O adapter hardware. This PCI-E switch failure is the root cause.
  1. Collect error logs and info logs.
  2. Collect the configuration data for the IOAs downstream of the PCI-E switch.
  3. Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
  4. Although the partition or application might have continued to run after the I/O adapter failures, it might need to be restarted to recover.
6A24 PCI-E switch had an unrecoverable failure. All downstream I/O is failed.
  1. Collect error logs and info logs.
  2. Collect the configuration data for the IOAs downstream of the PCI-E switch.
  3. Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly. Send the failed FRU and the data to IBM for fault analysis.
6A25 PCI-E switch has detected a firmware action that was not valid. All downstream I/O is failed.
  1. Collect error logs and info logs.
  2. Collect the configuration data for the IOAs downstream of the PCI-E switch.
  3. Update the firmware to the current level, as described in Updating the firmware.
  4. If the problem persists, replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly. Send the failed FRU and the data to IBM for fault analysis.
6A28 PCI-E switch had a correctable error. Downstream I/O is not affected. No corrective action is required.
6A2A PCI-E switch downstream I/O bus had a recoverable failure. The downstream IOA might be failed. Look for and resolve other errors. If there were no other errors, then the PCI-E switch recovery was successful. In either case, determine if any downstream I/O adapters are in failed states and to which partitions they belong. The partition or application associated with the failed downstream I/O might have to be restarted.
6A2B PCI-E switch downstream bus had recoverable failure, but has reached the threshold of recovery attempts. The downstream IOA is failed.
  1. Collect error logs and info logs.
  2. Collect the configuration data for the IOAs downstream of the PCI-E switch.
  3. Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly. Send the failed FRU and the data to IBM for fault analysis.
  4. After the FRU has been replaced, the partition or application associated with the failed downstream I/O might have to be restarted.
6A30 A PCI-E bus internal connection initialized to a lower bus configuration than expected. The bus is operational, but operating at a bandwidth below its rated capacity. This might lead to degraded I/O throughput. Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
BA01 During analysis of a previous serviceable error, a request to activate a FRU fault indicator was not successful. Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
BAD1 The platform firmware detected an error. Go to Isolating firmware problems.
BAD2 System firmware detected an error.
  1. Collect the event log information.
  2. Go to Isolating firmware problems.
F103 System firmware failure
  1. Collect the event log information.
  2. Collect the platform dump information.
  3. Go to Isolating firmware problems.
F104 Operating system error. System firmware terminated a partition. Check the management-module event log for partition firmware error codes (especially BA00F104); then, take the appropriate actions for those error codes.
F105 System firmware detected an internal error
  1. Collect the event log information.
  2. Collect the platform dump information.
  3. Go to Isolating firmware problems.
F106 System firmware detected an error

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
F107 System firmware detected an error.
  1. Collect the event log information.
  2. Go to Isolating firmware problems.
F108 A firmware error caused the system to terminate.
  1. Collect the event log information.
  2. Go to Isolating firmware problems.
F10A System firmware detected an error Look for and correct B1xxxxxx errors.
F10B A processor resource has been disabled due to hardware problems

Replace the system-board and chassis assembly, as described in Replacing the FRU system-board and chassis assembly.
F10C The platform LIC detected an internal problem performing Partition Mobility.
  1. Collect the event log information.
  2. Go to Isolating firmware problems.
F120 Informational system log entry only. No corrective action is required.
F130 Thermal Power Management Device firmware error was detected. Check for server firmware updates; then, install the updates if available.
Parent topic: System reference codes (SRCs)

Notices | Terms of use | Privacy | Support