Brocade Adapters Troubleshooting Guide 2553-1002145-01General adapter problems 2No target devices found or link down message displays in Brocade BIOSConfiguration menu“No target devices found or link down” message displays on Brocade BIOS configuration menuduring boot device discovery.1. Possible Cause: There is no fabric connectivity between the Brocade adapter and target, or thetarget is not online.Action: Execute the Fabric OS nsAllShow command on the attached switch to verify that thetarget and the host are online in the fabric and registered in the name server.2. Possible Cause: The target and the adapter port are not on the same zone.Action: Execute the Fabric OS cfgActvShow command on the attached switch and verify thatthe host and target are in the same zone by using either domain area members, port areamembers, or port or node WWNs.3. Possible Cause: The link between the adapter port and target is not active yet.Action: Check that the speeds for the adapter port and the connected switch port match. Thebest approach is to set both speeds to “auto” or “autonegotiate.”Unable to boot from the stored boot device settings in the adapterThe host is unable to boot from the boot device settings stored in the adapter. A “No boot LUNsconfigured” message will display next to the adapter value when booting.1. Possible Cause: In the Brocade BIOS Configuration Utility, the Boot LUN field In the AdapterSettings screen is set to Auto Discover or First LUN.Action: Change the Boot LUN setting on the Adapters Settings screen to Flash Values. Refer tothe Boot Code chapter in the Brocade Adapters Installation and Reference Manual for details.2. Possible Cause: In HCM, the boot option is set to Auto Discovered from Fabric or First VisibleLUN in the Boot over SAN dialog box.Action: Change the boot options to User Configured LUNs in the Boot Over SAN dialog box.Refer to the “Boot Code” chapter in the Brocade Adapters Installation and Reference Manualfor details.Remote LUNs are not visible to the hostIf LUNs from which the host system will boot are not visible from the host system, refer to thefollowing descriptions of possible causes and recommended actions to help resolve the problem.1. Possible Cause: The driver update disk (DUD) used to install the driver and necessary filestructure on remote LUNs for boot over SAN operation is not correct for the host operatingsystem being installed on the LUN.Action: Download and install the correct the driver update disk for the OS that is being installedfrom the Brocade adapters website using the following steps:a. Go to the adapters website at www.brocade.com/adapters.b. Navigate to the adapters Downloads page.c. Select your operating system from the Downloads list to display appropriate downloads.
