BROCADE 10 Gbps Fibre Channel over Ethernet PCIe Converged Network Adapter and 8 Gbps & 4 Gbps Fibre Channel PCIe Host Bus Adapter Release Notes - Software Release 2.3.0.3 (March 2011)

Brocade Adapter v2.3.0.3 Release Notes Page 15 of 19
10. In RHEL 5.x systems, when serial console redirection is used, the system
might report “soft lockups” with the following message in the
/var/log/messages:
“May 11 19:59:10 sysname kernel: BUG: soft lockup - CPU#0 stuck
for 10s! [multipathd:15307]”
It is recommended to remove serial console redirection to work around
this issue.
11. In SLES11 systems with multipath enabled, dev_loss_tmo may reset (by the
SLES 11 OS) to 10secs when an rport (target) is offline for greater than
dev_loss_tmo.
12. When using Linux's Device Mapper, MPIO timeout value may not be applied
consistently to all devices. The first device goes offline from the Device
Mapper within the first 10 seconds, whereas the rest of the devices go offline
at the expiry of MPIO timeout Value.
13. In SLES10, some array's control LUN is not assigned a /dev/sd* entry. This is
a display only issue and does not affect any functionality.
14. Currently the Brocade installer is inadvertently backing up the .syslog and
install.log files from /root to /var/log/brocade folder. This has no functional
impact and will be addressed in the next release.
15. In a configuration with a large number of LUNS and multipath enabled, Boot
from SAN could be slow if there is not enough physical memory on the server.
If you encounter this problem you may need to increase the physical memory
on the server.
Solaris:
1. The Solaris driver installation (using silent installation) requires a manual reboot.
2. On Solaris 10 SPARC systems with CNAs, in rare cases, might log spurious
interrupt messages file while running IO. These messages have no functional
impact other than increase in /var/adm/messages file size.
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 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.