Brocade Adapter Release Notes - Software Release v3.0.0.0 Update 3 (October 2011)

Brocade Adapter v3.0.0.0 Release Notes Update 3 Page 12 of 18
Important Notes
General:
1. Brocade HBAs support a direct-attach configuration to storage in Point-to-Point
(P2P) mode only (not in Arbitrated Loop mode).
2. In a configuration with HBAs and CNAs in the same server, the latest revision of
boot code should be updated on all the adapters after upgrading to the latest
drivers. The boot image can be updated on all the adapters using the command
“bcu boot –update <boot-firmware> -a” to update the boot firmware. LiveCD can
also be used to update the boot code. Refer to the boot section of the “Brocade
Adapters Installation and Reference Manual” for details.
3. UEFI FC and FCoE Boot over SAN are supported on UEFI-capable servers for
Windows 2008 x64, Windows 2008 R2, SLES11.x and RHEL6.x Operating
Systems (see “Brocade Adapters Installation and Reference Manual v3.0.0.0” for
details).
4. While configuring FC Trunking, it is advisable to configure trunking on both HBA
and Switch side before bringing the link up. This will avoid configuration
mismatch that normally leads to switch port persistent disable. A persistently
disabled switch port can be re-enabled by port persistent enable. If you wish to
enable FC trunking when the links are already established follow these steps:
• Disable switch ports to be trunked
• Enable FC trunking on switch ports
• Enable FC trunking on HBA ports
• Enable switch ports
5. Target Rate Limiting is not supported in conjunction with FC Trunking.
6. The current BIOS retry mechanism uses a timeout of five seconds and max of six
retries for SCSI control commands. If the boot device fails to respond within this
timeout period and all the retries are exhausted, the boot from this device will fail.
7. When multiple boot paths are defined sometimes all paths may not be
discovered. In some cases the boot process may fail. Re-discovery of the paths
can be initiated from the Boot Device Page and by selecting appropriate Boot
Device, followed by a reboot.
8. When configuring HBA BIOS for Boot from SAN, the HBA WWPN may not
appear in the fabric’s name server. To register the WWPN in the Name Server,
use the BIOS Configuration Utility and select one HBA port at a time from the
Adapter list and select target discovery for that port from Boot Device Settings
page.
9. For some IBM servers (3250M2, 3400, 3455B, 3650, 3655B, 3755B, 3950 M2), a
resource issue may not properly display the Brocade BIOS config during the
POST phase. It is recommended to disable any onboard disk controllers and
PXE boot option.