18
Brocade Adapters Troubleshooting Guide
53-1001582-01
General HBA and CNA problems
2
Driver and operating system installation failure on boot LUN
Installation fails when installing drivers with the driver update disk (DUD) and an installing
operating system to a remote LUN being used for booting over SAN.
Possible Cause: The appropriate driver update disk (DUD) may not have been used for the host
operating system and platform. For example, if the brocade_adapter_rhel53_x86_64 DUD is used
during RHEL 5.3 x86 installation, installation will fail.
Action: Download the appropriate dud for the host operating system from
or
BIOS boot problems
This section describes problems that may occur when using the Brocade adapter and Basic
Input/Output System (BIOS) for booting a host system from a remote storage device (boot over
SAN). Possible causes and recommended actions that may fix the problems are provided.
Driver and operating system installation failure on boot LUN
When installing drivers using the driver update disk (DUD) and an operating system to a remote
LUN being used for booting over SAN, the installation fails.
Possible Cause: The appropriate driver update disk (DUD) may not have been used for the host
operating system and platform. For example, if the brocade_adapter_rhel53_x86_64 DUD is used
during RHEL 5.3 x86 installation, installation will fail.
Action: Verify the DUD for your system using information in Chapter 1 of the
Brocade Adapters
Installation and Reference Manua
l. Using the correct DUD, reinstall appropriate drivers and the
operating system as necessary.
Target not visible from host
If the storage target configured for containing the boot LUN is not visible from the host, refer to the
following descriptions of possible causes and recommended actions to help resolve the problem.
1. Possible Cause: No fabric connectivity between adapter and target or target is not online.
Action: Execute the Fabric OS nsAllShow command on the attached switch to verify that the
target and the host are online in the fabric and registered in the name server.
2. Possible Cause: The target and the adapter are not on the same zone.
Action: Execute the Fabric OS cfgActvShow command on the attached switch and verify that
the host and target are in the same zone (either using domain area members, port area
members, or port or node WWNs).
3. Possible Cause: The adapter driver is not loaded.
Action: The adapter driver may not be loaded. Refer to
“Adapter driver installation verification”
on page 39 for methods to verify driver installation