Troubleshooting
Problem
During the initial boot of a new partition, the system builds a default boot list. With certain Fibre Channel adapters assigned to the partition, running at certain levels of adapter microcode, the scan for bootable resources on the Fibre Channel adapter can throw an exception, causing the scan and boot to fail.
Symptom
During the initial boot of a new partition (containing 577F, 578E, or 578F adapters), the boot might fail with one of the following reference codes: BA210001, BA218001, BA210003, or BA218003.
Cause
If the adapter microcode for 577F, 578E, or 578F adapters is in the range of 00011000040041500010
(11.4.415.10) up to 00011000040041500028 (11.4.415.28), or 00012000040025700015 (12.4.257.15) up to 00012000040025700027 (12.4.257.27), the commands sent to the adapter during scanning might fail. Partition Firmware (PFW), which contains SMS, would catch the error, log an event (BA210001, BA218001, BA210003, or BA218003), and fail the boot.Environment
Issue is seen with the following conditions:
1. The initial boot of a new partition, which has no default boot list set, is being performed.
2. The new partition owns one or more CCIN 577F, 578E, or 578F adapters. The issue occurs when one or more of the adapters is running an adapter microcode level 00011000040041500010
3. Attempt to boot the partition fails with BA210001, BA218001, BA210003, or BA218003.
1. The initial boot of a new partition, which has no default boot list set, is being performed.
2. The new partition owns one or more CCIN 577F, 578E, or 578F adapters. The issue occurs when one or more of the adapters is running an adapter microcode level 00011000040041500010
(11.4.415.10) up to 00011000040041500029 (11.4.415.29), or 00012000040025700015 (12.4.257.15) up to 00012000040025700027 (12.4.257.27). Determining the adapter code level might not be possible on some new installs, where there is no opportunity to assign the adapter to an already operational partition.3. Attempt to boot the partition fails with BA210001, BA218001, BA210003, or BA218003.
Resolving The Problem
In order to bypass the Fibre Channel adapter scan at initial boot, a work-around can be performed:
1. Shut down the partition
2. Change the partition's profile to remove all CCIN 577F, 578E, or 578F Fibre Channel adapters
Other IO adapters and network cards can be left in the partition profile. **See note if the partition is an All Resources partition.
3. Activate the partition from HMC, being sure to explicitly activate from the updated partition profile.
4. If there is no console terminal opened, the boot process should seem to wait at either a reference code of AA00E158 or AA00E1A9. If the console is opened, the boot finishes to the SMS menus. If the partition boot stops with a BA21xxxx reference code, there is likely still a problem that needs to be addressed.
5. Once boot process stops at the wait on AA00E158 or AA00E1A9 or at the SMS menu, a default boot list should have been created, and the partition should be shut down.
6. Modify the partition profile to add one or more desired Fibre Channel adapters back in to the configuration.
7. Activate the partition, being sure to specify the partition profile with the Fibre Channel adapters present.
8. Make sure the partition boot does not stop with a BA21xxxx type error. The boot should go to SMS (if the console is opened) or to a wait at AA00E158 or AA00E1A9 (if the console is not opened). Once a console is opened and SMS is reached, the OS installation process can be started.
2. Change the partition's profile to remove all CCIN 577F, 578E, or 578F Fibre Channel adapters
Other IO adapters and network cards can be left in the partition profile. **See note if the partition is an All Resources partition.
3. Activate the partition from HMC, being sure to explicitly activate from the updated partition profile.
4. If there is no console terminal opened, the boot process should seem to wait at either a reference code of AA00E158 or AA00E1A9. If the console is opened, the boot finishes to the SMS menus. If the partition boot stops with a BA21xxxx reference code, there is likely still a problem that needs to be addressed.
5. Once boot process stops at the wait on AA00E158 or AA00E1A9 or at the SMS menu, a default boot list should have been created, and the partition should be shut down.
6. Modify the partition profile to add one or more desired Fibre Channel adapters back in to the configuration.
7. Activate the partition, being sure to specify the partition profile with the Fibre Channel adapters present.
8. Make sure the partition boot does not stop with a BA21xxxx type error. The boot should go to SMS (if the console is opened) or to a wait at AA00E158 or AA00E1A9 (if the console is not opened). Once a console is opened and SMS is reached, the OS installation process can be started.
**note: If the partition is configured as an All Resources partition ('Assign all system resources' selected on partition creation or this is the default All Resources partition), you cannot remove the adapter(s) from the configuration to perform the work-around steps. Another partition will need to be created. It can be configured with all resources (except for the Fiber Channel Adapters), and follow steps 3-8. Until all Fibre Channel adapter microcode levels are updated, All Resource partition boots will fail, due to the problem microcode failing before the default list is created.
**note: If the server is a true stand-alone, with no HMC attached or managing the server, the affected adapter types would need to be physically removed from the server temporarily, to perform a system boot to the SMS menu. That is sufficient to set the initial bootlist without these adapters being queried. The server can then be shut off, adapters re-installed, and then boot to SMS again, and install as normal.
Fibre Channel Adapter microcode 12.4.257.15 addresses this issue:
- Fixed Memory Address Not Aligned issue caused by FLOGI retry loop. Initial partition boot may fail with one of the following reference codes: BA210001, BA218001, BA210003, or BA218003.
A separate issue was found in 12.4.257.15 and 12.4.257.27 that has the same symptoms, and the same work-around. It is fixed in 12.4.257.30 and later.
The work-around is still needed for adapters that were shipped with the failing microcode, and where there are no active partitions to be able to load the new microcode to the adapter.
Document Location
Worldwide
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"HW1A1","label":"IBM Power Systems"},"Component":"","Platform":[{"code":"PF002","label":"AIX"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}},{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"HW1A1","label":"IBM Power Systems"},"Component":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB57","label":"Power"}}]
Was this topic helpful?
Document Information
Modified date:
26 October 2021
UID
ibm11367103