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 17 of 18
9. Linux BASI installer creates a second backup copy of the initrd file. There is no
functional impact of having two copies.
10. On Linux systems, Brocade Adapter Software Installer doesn't check to see if
/boot is full and fails silently when updating initrd. Re-try installation after adding
or freeing up disk space in the /boot partition.
11. RHEL6.1 and SLES10 SP4 include 2.3.2.x based Inbox drivers. Use of Driver
Update Disk during Boot over SAN installation is not essential for the Brocade
legacy adapters and is only required to support BR-1860.
12. Boot over SAN is not supported with RHEL 4.0 on BR-1860 when one port is
configured in FC mode and the other port is configured in NIC or CNA mode.
13. For PXE installation on Remote SAN, inject the BNA Driver Update Disk followed
by BFA Driver Update Disk to avoid failure.
Solaris:
1. The Solaris driver installation (using silent installation) requires a manual reboot.
VMware:
1. The Brocade HCM Agent needs to be restarted if firewall settings on port# 514
changed in ESX 4.0. By default, ESX 4.0 blocks the syslog outgoing port 514. If
syslog Host configuration or DCFM/BNA integration is performed, open port 514
using the following command: esxcfg-firewall -o 514,udp,out,syslog.
2. While upgrading HBA from boot firmware version 1.1.0.x on a VMware ESX4.x
system, upgrade the boot firmware using LiveCD first to avoid server hang during
bootup.
Documentation Updates
• None at this time.