BA000010 to BA400002 Partition firmware SRCs

The power-on self-test (POST) might display an error code that the partition firmware detects. Try to correct the problem with the suggested action.

Table 1 describes error codes that might be displayed if POST detects a problem. The description also includes suggested actions to correct the problem.

Note: For problems persisting after completing the suggested actions, see Checkout procedure and Solving undetermined problems.
Table 1. BA000010 to BA400002 Partition firmware 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.
Error code Description Action
BA000010 The device data structure is corrupted
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000020 Incompatible firmware levels were found
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000030 An lpevent communication failure occurred
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000031 An lpevent communication failure occurred
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000032 The firmware failed to register the lpevent queues
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000034 The firmware failed to exchange capacity and allocate lpevents
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000038 The firmware failed to exchange virtual continuation events
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000040 The firmware was unable to obtain the RTAS code lid details
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000050 The firmware was unable to load the RTAS code lid
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000060 The firmware was unable to obtain the open firmware code lid details
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000070 The firmware was unable to load the open firmware code lid
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000080 The user did not accept the license agreement Accept the license agreement and restart the blade server.
If the problem persists:
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000081 Failed to get the firmware license policy
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000082 Failed to set the firmware license policy
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA000091 Unable to load a firmware code update module
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA00E820 An lpevent communication failure occurred
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA00E830 Failure when initializing ibm,event-scan
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA00E840 Failure when initializing PCI hot-plug
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA00E843 Failure when initializing the interface to AIX® or Linux
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA00E850 Failure when initializing dynamic reconfiguration
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA00E860 Failure when initializing sensors
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010000 There is insufficient information to boot the systems
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010001 The client IP address is already in use by another network device Verify that all of the IP addresses on the network are unique; then, retry the operation.
BA010002 Cannot get gateway IP address
Perform the following actions that checkpoint CA00E174 describes:
  1. Verify that:
    • The bootp server is correctly configured; then, retry the operation.
    • The network connections are correct; then, retry the operation.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010003 Cannot get server hardware address
Perform the following actions that checkpoint CA00E174 describes:
  1. Verify that:
    • The bootp server is correctly configured; then, retry the operation.
    • The network connections are correct; then, retry the operation.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010004 Bootp failed
Perform the following actions that checkpoint CA00E174 describes:
  1. Verify that:
    • The bootp server is correctly configured; then, retry the operation.
    • The network connections are correct; then, retry the operation.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010005 File transmission (TFTP) failed
Perform the following actions that checkpoint CA00E174 describes:
  1. Verify that:
    • The bootp server is correctly configured; then, retry the operation.
    • The network connections are correct; then, retry the operation.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010006 The boot image is too large Start up from another device with a bootable image.
BA010007 The device does not have the required device_type property.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010008 The device_type property for this device is not supported by the iSCSI initiator configuration specification.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010009 The arguments specified for the ping function are invalid.

The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
BA01000A The itname parameter string exceeds the maximum length allowed.

The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
BA01000B The ichapid parameter string exceeds the maximum length allowed.

The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
BA01000C The ichappw parameter string exceeds the maximum length allowed.

The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
BA01000D The iname parameter string exceeds the maximum length allowed.

The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
BA01000E The LUN specified is not valid.

The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
BA01000F The chapid parameter string exceeds the maximum length allowed.

The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
BA010010 The chappw parameter string exceeds the maximum length allowed.

The embedded host Ethernet adapters (HEAs) help provide iSCSI, which is supported by iSCSI software device drivers on either AIX or Linux. Verify that all of the iSCSI configuration arguments on the operating system comply with the configuration for the iSCSI Host Bus Adapter (HBA), which is the iSCSI initiator.
BA010011 SET-ROOT-PROP could not find / (root) package
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA010013 The information in the error log entry for this SRC provides network trace data. Informational message. No action is required.
BA010014 The information in the error log entry for this SRC provides network trace data. Informational message. No action is required.
BA010015 The information in the error log entry for this SRC provides network trace data. Informational message. No action is required.
BA010020 A trace entry addition failed because of a bad trace type.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA012010 Opening the TCP node failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA012011 TCP failed to read from the network
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA012012 TCP failed to write to the network.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA012013 Closing TCP failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA017020 Failed to open the TFTP package

Verify that the Trivial File Transfer Protocol (TFTP) parameters are correct.
BA017021 Failed to load the TFTP file Verify that the TFTP server and network connections are correct.
BA01B010 Opening the BOOTP node failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01B011 BOOTP failed to read from the network
Perform the following actions that checkpoint CA00E174 describes:
  1. Verify that:
    • The bootp server is correctly configured; then, retry the operation.
    • The network connections are correct; then, retry the operation.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01B012 BOOTP failed to write to the network
Perform the following actions that checkpoint CA00E174 describes:
  1. Verify that:
    • The bootp server is correctly configured; then, retry the operation.
    • The network connections are correct; then, retry the operation.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01B013 The discover mode is invalid
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01B014 Closing the BOOTP node failed
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01B015 The BOOTP discover server timed out
Perform the following actions that checkpoint CA00E174 describes:
  1. Verify that:
    • The bootp server is correctly configured; then, retry the operation.
    • The network connections are correct; then, retry the operation.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01D001 Opening the DHCP node failed
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01D020 DHCP failed to read from the network
  1. Verify that the network cable is connected, and that the network is active.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01D030 DHCP failed to write to the network
  1. Verify that the network cable is connected, and that the network is active.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01D040 The DHCP discover server timed out
  1. Verify that the DHCP server has addresses available.
  2. Verify that the DHCP server configuration file is not overly constrained. An over-constrained file might prevent a server from meeting the configuration requested by the client.
  3. Perform the following actions that checkpoint CA00E174 describes:
    1. Verify that:
      • The bootp server is correctly configured; then, retry the operation.
      • The network connections are correct; then, retry the operation.
    2. If the problem persists:
      1. Go to Checkout procedure.
      2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA01D050 DHCP::discover no good offer DHCP discovery did not receive any DHCP offers from the servers that meet the client requirements.

Verify that the DHCP server configuration file is not overly constrained. An over-constrained file might prevent a server from meeting the configuration requested by the client.
BA01D051 DHCP::discover DHCP request timed out DHCP discovery did receive a DHCP offer from a server that met the client requirements, but the server did not send the DHCP acknowledgement (DHCP ack) to the client DHCP request.

Another client might have used the address that was served.

Verify that the DHCP server has addresses available.
BA01D052 DHCP::discover: 10 incapable servers were found Ten DHCP servers have sent DHCP offers, none of which met the requirements of the client. Check the compatibility of the configuration that the client is requesting and the server DHCP configuration files.
BA01D053 DHCP::discover received a reply, but without a message type Verify that the DHCP server is properly configured.
BA01D054 DHCP::discover: DHCP nak received DHCP discovery did receive a DHCP offer from a server that meets the client requirements, but the server sent a DHCP not acknowledged (DHCP nak) to the client DHCP request.

Another client might be using the address that was served.

This situation can occur when there are multiple DHCP servers on the same network, and server A does not know the subnet configuration of server B, and vice-versa.

This situation can also occur when the pool of addresses is not truly divided.

Set the DHCP server configuration file to "authoritative".

Verify that the DHCP server is functioning properly.
BA01D055 DHCP::discover: DHCP decline DHCP discovery did receive a DHCP offer from one or more servers that meet the client requirements. However, the client performed an ARP test on the address and found that another client was using the address.

The client sent a DHCP decline to the server, but the client did not receive an additional DHCP offer from a server. The client still does not have a valid address.

Verify that the DHCP server is functioning properly.
BA01D056 DHCP::discover: unknown DHCP message DHCP discovery received an unknown DHCP message type. Verify that the DHCP server is functioning properly.
BA01D0FF Closing the DHCP node failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA030011 RTAS attempt to allocate memory failed
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA04000F Self test failed on device; no error or location code information available
  1. If a location code is identified with the error, replace the device specified by the location code.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA040010 Self test failed on device; can't locate package.
  1. If a location code is identified with the error, replace the device specified by the location code.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA040020 The machine type and model are not recognized by the blade server firmware.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA040030 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. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA040035 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 that the machine type, model, and serial number are correct for this server. If this is a new server, check for server firmware updates; then, install the updates if available.
BA040040 Setting the machine type, model, and serial number failed.
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA040050 The h-call to switch off the boot watchdog timer failed.
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA040060 Setting the firmware boot side for the next boot failed.
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA050001 Failed to reboot a partition in logical partition mode
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA050004 Failed to locate service processor device tree node.
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA05000A Failed to send boot failed message
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060008 No configurable adapters found by the Remote IPL menu in the SMS utilities This error occurs when the firmware cannot locate any LAN adapters that are supported by the remote IPL function. Verify that the devices in the remote IPL device list are correct using the SMS menus.
BA06000B The system was not able to find an operating system on the devices in the boot list. Go to Boot problem resolution.
BA06000C A pointer to the operating system was found in non-volatile storage.
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060020 The environment variable “boot-device” exceeded the allowed character limit.
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060021 The environment variable “boot-device” contained more than five entries.
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060022 The environment variable “boot-device” contained an entry that exceeded 255 characters in length
  1. Using the SMS menus, set the boot list to the default boot list.
  2. Shut down; then, start up the blade server.
  3. Use SMS menus to customize the boot list as required.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060030 Logical partitioning with shared processors is enabled and the operating system does not support it.
  1. Install or boot a level of the operating system that supports shared processors.
  2. Disable logical partitioning with shared processors in the operating system.
  3. If the problem remains:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060060 The operating system expects an IOSP partition, but it failed to make the transition to alpha mode.
  1. Verify that:
    • The alpha-mode operating system image is intended for this partition.
    • The configuration of the partition supports an alpha-mode operating system.
  2. If the problem remains:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060061 The operating system expects a non-IOSP partition, but it failed to make the transition to MGC mode.
  1. Verify that:
    • The alpha-mode operating system image is intended for this partition.
    • The configuration of the partition supports an alpha-mode operating system.
  2. If the problem remains:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060070 The operating system does not support this system's processor(s)

Boot a supported version of the operating system.
BA060071 An invalid number of vectors was received from the operating system

Boot a supported version of the operating system.
BA060072 Client-arch-support hcall error
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060075 Client-arch-support firmware error
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060200 Failed to set the operating system boot list from the management module boot list
  1. Using the SMS menus, set the boot list to the default boot list.
  2. Shut down; then, start up the blade server.
  3. Use SMS menus to customize the boot list as required.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060201 Failed to read the VPD "boot path" field value
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060202 Failed to update the VPD with the new "boot path" field value
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA060300 An I/O error on the adapter from which the boot was attempted prevented the operating system from being booted.
  1. Using the SMS menus, select another adapter from which to boot the operating system, and reboot the system.
  2. Attempt to reboot the system.
  3. Go to Boot problem resolution.
BA07xxxx self configuring SCSI device (SCSD) controller failure
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA090001 SCSD DASD: test unit ready failed; hardware error
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA090002 SCSD DASD: test unit ready failed; sense data available
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA090003 SCSD DASD: send diagnostic failed; sense data available
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA090004 SCSD DASD: send diagnostic failed: devofl cmd
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA09000A There was a vendor specification error.
  1. Check the vendor specification for additional information.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA09000B Generic SCSD sense error
  1. Verify that the SCSD cables and devices are properly plugged.
  2. Correct any problems that are found.
  3. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA09000C The media is write-protected
  1. Change the setting of the media to allow writing, then retry the operation.
  2. Insert new media of the correct type.
  3. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA09000D The media is unsupported or not recognized.
  1. Insert new media of the correct type.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA09000E The media is not formatted correctly.
  1. Insert the media.
  2. Insert new media of the correct type.
  3. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA09000F Media is not present
  1. Insert new media with the correct format.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA090010 The request sense command failed.
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA090011 The retry limit has been exceeded.
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA090012 There is a SCSD device that is not supported.
  1. Replace the SCSD device that is not supported with a supported device.
  2. If the problem persists:
    1. Troubleshoot the SCSD devices.
    2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
    3. Replace the SCSD cables and devices.
    4. If the problem persists:
      1. Go to Checkout procedure.
      2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA120001 On an undetermined SCSD device, test unit ready failed; hardware error
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA120002 On an undetermined SCSD device, test unit ready failed; sense data available
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA120003 On an undetermined SCSD device, send diagnostic failed; sense data available
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA120004 On an undetermined SCSD device, send diagnostic failed; devofl command
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA120010 Failed to generate the SAS device physical location code. The event log entry has the details.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA130010 USB CD-ROM in the media tray: device remained busy longer than the time-out period
  1. Retry the operation.
  2. Reboot the blade server.
  3. Troubleshoot the media tray and CD-ROM drive.
  4. Replace the USB CD or DVD drive.
  5. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA130011 USB CD-ROM in the media tray: execution of ATA/ATAPI command was not completed with the allowed time.
  1. Retry the operation.
  2. Reboot the blade server.
  3. Troubleshoot the media tray and CD-ROM drive.
  4. Replace the USB CD or DVD drive.
  5. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA130012 USB CD-ROM in the media tray: execution of ATA/ATAPI command failed.
  1. Retry the operation.
  2. Reboot the blade server.
  3. Troubleshoot the media tray and CD-ROM drive.
  4. Replace the USB CD or DVD drive.
  5. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA130013 USB CD-ROM in the media tray: bootable media is missing from the drive
  1. Insert a bootable CD in the drive and retry the operation.
  2. If the problem persists:
    1. Retry the operation.
    2. Reboot the blade server.
    3. Troubleshoot the media tray and CD-ROM drive.
    4. Replace the USB CD or DVD drive.
    5. If the problem persists:
      1. Go to Checkout procedure.
      2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA130014 USB CD-ROM in the media tray: the media in the USB CD-ROM drive has been changed.
  1. Retry the operation.
  2. Reboot the blade server.
  3. Troubleshoot the media tray and CD-ROM drive.
  4. Replace the USB CD or DVD drive.
  5. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA130015 USB CD-ROM in the media tray: ATA/ATAPI packet command execution failed.
  1. Ensure the media tray is assigned to the blade and contains bootable media.
  2. Remove the CD or DVD in the drive and replace it with a known-good disk.
  3. If the problem persists:
    1. Retry the operation.
    2. Reboot the blade server.
    3. Troubleshoot the media tray and CD-ROM drive.
    4. Replace the USB CD or DVD drive.
    5. If the problem persists:
      1. Go to Checkout procedure.
      2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA131010 The USB keyboard has been removed.
  1. Reseat the keyboard cable in the management module USB port.
  2. Check for server firmware updates; then, install the updates if available.
BA140001 The SCSD read/write optical test unit ready failed; hardware error.
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA140002 The SCSD read/write optical test unit ready failed; sense data available.
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA140003 The SCSD read/write optical send diagnostic failed; sense data available.
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA140004 The SCSD read/write optical send diagnostic failed; devofl command.
  1. Troubleshoot the SCSD devices.
  2. Verify that the SCSD cables and devices are properly plugged. Correct any problems that are found.
  3. Replace the SCSD cables and devices.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA150001 PCI Ethernet BNC/RJ-45 or PCI Ethernet AUI/RJ-45 adapter: internal wrap test failure Replace the adapter specified by the location code.
BA151001 10/100 Mbps Ethernet PCI adapter: internal wrap test failure Replace the adapter specified by the location code.
BA151002 10/100 Mbps Ethernet card failure
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA153002 Gigabit Ethernet adapter failure Verify that the MAC address programmed in the FLASH/EEPROM is correct.
BA153003 Gigabit Ethernet adapter failure
  1. Check for server firmware updates; then, install the updates if available.
  2. Replace the Gigabit Ethernet adapter.
BA154010 HEA software error
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA154020 The required open firmware property was not found.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA154030 Invalid parameters were passed to the HEA device driver.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA154040 The TFTP package open failed
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA154050 The transmit operation failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA154060 Failed to initialize the HEA port or queue
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA154070 The receive operation failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170000 NVRAMRC initialization failed; device test failed
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170100 NVRAM data validation check failed
  1. Shut down the blade server; then, restart it.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170201 The firmware was unable to expand target partition - saving configuration variable
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170202 The firmware was unable to expand target partition - writing event log entry
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170203 The firmware was unable to expand target partition - writing VPD data
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170210 Setenv/$Setenv parameter error - name contains a null character
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170211 Setenv/$Setenv parameter error - value contains a null character
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170220 Unable to write a variable value to NVRAM due to lack of free memory in NVRAM.
  1. Reduce the number of partitions, if possible, to add more NVRAM memory to this partition.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA170221 Setenv/$setenv had to delete stored firmware network boot settings to free memory in NVRAM. Enter the adapter and network parameters again for the network boot or network installation.
BA170998 NVRAMRC script evaluation error - command line execution error.
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180008 PCI device Fcode evaluation error
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180009 The Fcode on a PCI adapter left a data stack imbalance
  1. Reseat the PCI adapter card.
  2. Check for adapter firmware updates; then, install the updates if available.
  3. Check for server firmware updates; then, install the updates if available.
  4. Replace the PCI adapter card.
  5. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180010 PCI probe error, bridge in freeze state
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180011 PCI bridge probe error, bridge is not usable
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180012 PCI device runtime error, bridge in freeze state
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180014 MSI software error
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180020 No response was received from a slot during PCI probing.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180099 PCI probe error; bridge in freeze state, slot in reset state
  1. Reseat the PCI adapter card.
  2. Check for adapter firmware updates; then, install the updates if available.
  3. Check for server firmware updates; then, install the updates if available.
  4. Replace the PCI adapter card.
  5. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA180100 The FDDI adapter Fcode driver is not supported on this server. IBM® may produce a compatible driver in the future, but does not guarantee one.
BA180101 Stack underflow from fibre-channel adapter
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA190001 Firmware function to get/set time-of-day reported an error
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA201001 The serial interface dropped data packets
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA201002 The serial interface failed to open
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA201003 The firmware failed to handshake properly with the serial interface
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210000 Partition firmware reports a default catch
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210001 Partition firmware reports a stack underflow was caught
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210002 Partition firmware was ready before standout was ready
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210003 A data storage error was caught by partition firmware
  1. If the location code reported with the error points to an adapter, check for adapter firmware updates.
  2. Apply any available updates.
  3. Check for server firmware updates.
  4. Apply any available updates.
  5. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210004 An open firmware stack-depth assert failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210010 The transfer of control to the SLIC loader failed
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210011 The transfer of control to the IO Reporter failed
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210012 There was an NVRAMRC forced-boot problem; unable to load the previous boot's operating system image
  1. Use the SMS menus to verify that the partition firmware can still detect the operating system image.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210013 There was a partition firmware error when in the SMS menus.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210020 I/O configuration exceeded the maximum size allowed by partition firmware.
  1. Increase the logical memory block size to 256 MB and restart the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210100 An error may not have been sent to the management module event log.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210101 The partition firmware event log queue is full
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210102 There was a communication failure between partition firmware and the hypervisor. The lpevent that was expected from the hypervisor was not received.
  1. Review the event log for errors that occurred around the time of this error.
  2. Correct any errors that are found and reboot the blade server.
  3. If the problem persists:
    1. Reboot the blade server.
    2. If the problem persists:
      1. Go to Checkout procedure.
      2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA210103 There was a communication failure between partition firmware and the hypervisor. There was a failing return code with the lpevent acknowledgement from the hypervisor.
  1. Review the event log for errors that occurred around the time of this error.
  2. Correct any errors that are found and reboot the blade server.
  3. If the problem persists:
    1. Reboot the blade server.
    2. If the problem persists:
      1. Go to Checkout procedure.
      2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA220010 There was a partition firmware error during a USB hotplug probing. USB hotplug may not work properly on this partition.
  1. Look for EEH-related errors in the event log.
  2. Resolve any EEH event log entries that are found.
  3. Correct any errors that are found and reboot the blade server.
  4. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA220020 CRQ registration error; partner vslot may not be valid Verify that this client virtual slot device has a valid server virtual slot device in a hosting partition.
BA278001 Failed to flash firmware: invalid image file Download a new firmware update image and retry the update.
BA278002 Flash file is not designed for this platform Download a new firmware update image and retry the update.
BA278003 Unable to lock the firmware update lid manager
  1. Restart the blade server.
  2. Verify that the operating system is authorized to update the firmware. If the system is running multiple partitions, verify that this partition has service authority.
BA278004 An invalid firmware update lid was requested Download a new firmware update image and retry the update.
BA278005 Failed to flash a firmware update lid Download a new firmware update image and retry the update.
BA278006 Unable to unlock the firmware update lid manager Restart the blade server.
BA278007 Failed to reboot the system after a firmware flash update Restart the blade server.
BA278009 The operating system's server firmware update management tools are incompatible with this system. Go to the IBM download site at www14.software.ibm.com/webapp/set2/sas/f/lopdiags/home.html to download the latest version of the service aids package for Linux.
BA27800A The firmware installation failed due to a hardware error that was reported.
  1. Look for hardware errors in the event log.
  2. Resolve any hardware errors that are found.
  3. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA280000 RTAS discovered an invalid operation that may cause a hardware error
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA290000 RTAS discovered an internal stack overflow
  1. Go to Checkout procedure.
  2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA290001 RTAS low memory corruption was detected
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA290002 RTAS low memory corruption was detected
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA310010 Unable to obtain the SRC history
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA310020 An invalid SRC history was obtained.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA310030 Writing the MAC address to the VPD failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA330000 Memory allocation error.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA330001 Memory allocation error.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA330002 Memory allocation error.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA330003 Memory allocation error.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA330004 Memory allocation error.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340001 There was a logical partition event communication failure reading the BladeCenter open fabric manager parameter data structure from the service processor.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340002 There was a logical partition event communication failure reading the BladeCenter open fabric manager location code mapping data from the service processor.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340003 An internal firmware error occurred; unable to allocate memory for the open fabric manager location code mapping data.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340004 An internal firmware error occurred; the open fabric manager parameter data was corrupted.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340005 An internal firmware error occurred; the location code mapping table was corrupted.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340006 An LP event communication failure occurred reading the system initiator capability data from the service processor.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340007 An internal firmware error occurred; the open fabric manager system initiator capability data was corrupted.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340008 An internal firmware error occurred; the open fabric manager system initiator capability data version was not correct.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340009 An internal firmware error occurred; the open fabric manager system initiator capability processing encountered an unexpected error.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340010 An internal firmware error was detected during open fabric manager processing.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340011 Assignment of fabric ID to the I/O adapter failed.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340020 A logical partition event communication failure occurred when writing the BladeCenter open fabric manager parameter data to the service processor.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA340021 A logical partition event communication failure occurred when writing the BladeCenter open fabric manager system initiator capabilities data to the service processor.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA400001 Informational message: DMA trace buffer full.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
BA400002 Informational message: DMA map-out size mismatch.
  1. Reboot the blade server.
  2. If the problem persists:
    1. Go to Checkout procedure.
    2. Replace the system-board, as described in Replacing the FRU system-board and chassis assembly.
Parent topic: System reference codes (SRCs)

Notices | Terms of use | Privacy | Support