Broadcom (R) Corporation Broadcom Ethernet Software Kit RELEASE T7.6.4.2 Gold (Thursday, March 28, 2013) Software Compatibility ====================== This release of software supports: - BCM5709C NetXtreme II Gigabit Ethernet Adapter - BCM5709S NetXtreme II Gigabit Ethernet Adapter - BCM5716C NetXtreme II Gigabit Ethernet Adapter - BCM5718 NetXtreme Gigabit Ethernet Adapter - BCM5719 NetXtreme Gigabit Ethernet Adapter - BCM5720 NetXtreme Gigabit Ethernet Adapter - BCM5722 NetXtreme Gigabit Ethernet Adapter - BCM57711 NetXtreme II Gigabit Ethernet Adapter - BCM57712 NetXtreme II Gigabit Ethernet Adapter - BCM57800 NetXtreme II Gigabit Ethernet Adapter - BCM57810 NetXtreme II Gigabit Ethernet Adapter - BCM57840 NetXtreme II Gigabit Ethernet Adapter Contents of the CD ================== **** Release Version Information Table **** Product Version 1. Windows 2003/Windows 2008 Drivers Windows Server 2008 x86/x64 (NX1) 15.6.0.10* Windows 2008/R2 NDIS Driver (NX2) 7.6.51.0* iSCSI Crash Dump Driver 7.6.50 FCoE Crash Dump Driver 7.6.1 bxDiag 7.6.5.0* VBD Driver 7.6.2.0* VBD Driver NX2_Ev 7.6.59.0* Windows iSCSI Driver NX2 7.6.2.0* FCoE Offload Driver 7.6.3.0* 2. Linux Drivers Linux DKMS NX1 3.129d-1 Linux DKMS NX2/NX2_Ev 7.6.62-1 Linux Driver NX2 2.2.3n Linux Driver NX2_Ev 1.76.54 Linux iSCSI Driver NX2 2.7.6.1d Linux Driver CNIC 2.5.16g Linux FCoE Driver NX2 2.3.4 Linux uIP Driver 0.7.6.1g Linux Tg3 3.129d 3. Teaming software BASP Windows Server 2008/R2 1.6.6* 4. Utilities Dos b57udiag (NX1) 15.6.03 DOS uxDiag (NX2) 7.6.0 DOS ueDiag (NX2_EV) 7.6.52 Firmware Upgrade for Linux NX1 2.4.11 Firmware Upgrade for VMWare NX1 2.4.10 Firmware Upgrade for Windows NX1 7.4.11.0 Firmware Upgrade for Linux NX2 2.5.5 Firmware Upgrade for VMWare NX2 2.5.4 Firmware Upgrade for Windows NX2 2.5.6.0 Linux Diagnostic NX1 15.6.1 Linux Online Diagnostic 3.0.0.87_1 Windows Online Diagnostic 3.0.0.89 5. Documentation HTML User Guide for NetXtreme 2CS57XX-CDUM507-R HTML User Guide for NetXtreme II 2CSINGSRVT76-CDUM100-R 6. Management Apps BACS 15.6.31.0 BACS for Linux 15.6.31 BACS Command Line Interface 15.6.31.0 BMAPI 7.30.13.0 BMAPI Linux 6.19.1 SNMP-Basp 7.1.7.0 SNMP-Extensible-Agent 7.1.7.0 CIM for Windows 15.6.18.0 CMPI provider for Linux 2.3.16 7. Installer Umbrella Installer 15.6.4.9 8. Pre-Boot MBA/PXE (NX1) 15.6.50 MBA/PXE (NX2) 7.6.50 MBA/PXE (NX2_Ev) 7.6.53 uEFI (NX1) 15.6.53 uEFI (NX2) 6.2.3 uEFI (NX2_Ev) 7.6.56 iSCSI Boot 7.6.50 FCoE Boot 7.6.52 Note: An asterisk (*) following a version number represents a Windows certified driver. * Third-party trademarks and copyrights are the property of their respective owners. Broadcom, Broadcom Advanced Server Program, Broadcom Advanced Server Control Suite, and Smart Load Balance are registered trademarks of Broadcom Corporation. Optics and Direct Attach Cable Support Summary =============== BCM57711 #OPTIC MODULES FINISAR CORP, FTLX8571D3BCL AVAGO, AFBR-707SDZ-D1 AVAGO, AFBR-703SDZ-D1 Intel Corp, FTLX8571D3BCV-IT #DIRECT ATTACH CABLES CISCO-MOLEX INC, 74752-9093 CISCO-MOLEX INC, 74752-9094 CISCO-MOLEX INC, 74752-9096 CISCO-MOLEX INC, 74752-9098 BCM57800 and BCM57810 #OPTIC MODULES (SR) AVAGO, AFBR-703SDZ-D1 FINISAR CORP, FTLX8571D3BCL Intel Corp, AFBR-703SDZ-IN2 Intel Corp, FTLX8571D3BCV-IT #DIRECT ATTACH CABLES CISCO-MOLEX INC, 74752-9093 CISCO-MOLEX INC, 74752-9094 CISCO-MOLEX INC, 74752-9096 CISCO-MOLEX INC, 74752-9098 BROCADE, 58-1000026-01 BROCADE, 58-1000027-01 BROCADE, 58-1000023-01 Amphenol, 599700002 Amphenol, 616740001 Amphenol, 599700006 Amphenol, 616740003 Amphenol, 599700004 Amphenol, 616740005 BCM57840 #OPTIC MODULES (SR) Intel Corp, AFBR-703SDZ-IN2 Intel Corp, FTLX8571D3BCV-IT #DIRECT ATTACH CABLES CISCO-MOLEX INC, 74752-9093 CISCO-MOLEX INC, 74752-9094 CISCO-MOLEX INC, 74752-9096 CISCO-MOLEX INC, 74752-9098 BROCADE, 58-1000026-01 BROCADE, 58-1000027-01 BROCADE, 58-1000023-01 Amphenol, 599700002 Amphenol, 616740001 Amphenol, 599700006 Amphenol, 616740003 Amphenol, 599700004 Amphenol, 616740005 Intel Corp, AFBR-703SDZ-IN2 Intel Corp, FTLX8571D3BCV-IT Feature Summary =============== - Added Nic Partitioning feature to new 57712 Ethernet controller chip. - The drivers for NetXtreme II 1 Gb, NetXtreme II 10 Gb, and iSCSI offload are combined in the KMP RPM packages provided for SUSE Linux Enterprise Server 11 SP1. - The Broadcom driver and management apps installer now provides the ability to select whether to enable the TCP Offload Engine (TOE) in Windows Server 2008 R2 when only the NetXtreme II 1 Gb device is present. - Added Hyper-V Live Migration features with BASP teaming - Added new Comprehensive Configuration Management to manage all MBA enabled adapters from a single banner popup. - TCP/IP and iSCSI Offload performance improvement in a congested network. - Added VMQ support for NetXtremeII 1G and 10G devices. - EOL Windows 2003 support - Added SR-IOV features support for 57712 and 578xx - Added EEE support for 1G and 10G Base-T adapters - Added FCoE support for 57800/57810 adapters - No FCoE support for 57800/57810 10GBase-T adapters - Added support for 57840 adapters Fixes: =============== - Display FCoE statistics in management - 57800_1Gig ports displays FCoE boot version in HII - 5720 DriverHealthProtocol status - R720 - Broadcom 5719 PCI MAC address set to null 00-00-00-00-00-00 when using LAG in PCI slots 1-4 - NIC.FrmwImgMenu.1 is not displaying Controller BIOS Object. - Broadcom 10 Gigabit Ethernet Driver fails EFI_DEVICE_ERROR with drvdiag - Add ability to change TCP Delayed ACK setting on Broadcom 57711 - Add support for OOB WOL using virtual mac address - Add support for BACS to Allow Simultaneous Multiple vPort Creation - Broadcom 5720 NDC fail to support the VLAN tagging in UEFI - Broadcom 57810S-k iSoE ESXi performance issue during large block Seq IO - Remove additional MAC address displaying in device configuration menu - Change BACS display string of 'iSCSI' to 'iSCSI HBA' in DCB menu - Update BACs DCB description field to add details on where to enable DCB ******************************************************************************************* Currently known issues and limitations with Broadcom NetXtreme 1 and 2 drivers and devices. ******************************************************************************************* 1. BASP (the Broadcom Advanced Server Program) will appear to be bound to all adapters in the system once loaded. This binding is normal and is used only to determine compatibility with BASP. The binding is not active, as indicated by the gray background of the selection box. This pre-binding will not interfere with bindings to other software protocols. 2. Customer may not see improvements with TOE when running web traffic with short-lived connections. When Webbench 5.0 uses short-lived connections to generate web traffic, TOE throughput is ~3% lower than non-TOE. CPU utilization is 100% in both cases. This is due to the fact that Microsoft Windows Server 2003 Scalable Networking Pack and Broadcom NetXtreme II drivers aren't fully optimized to handle uploading and offloading of short-lived http connections. TOE demonstrates performance advantages with long-lived connections. 3. The NetXtreme II drivers have two parts, the VBD driver and the NDIS Client driver. This combination of drivers can be used for WinPE installations as long as the WinPE image is built with the /PnP option. WinPE images that are booted with the -miniNT option will only load the NDIS driver so NetXtreme II network devices will not be functional in this environment. Use the -winpe option instead of the -minint option to boot WinPE when using NetXtreme II devices or use the special RIS driver contained in the distribution package in the NX2_W2K3_8_(processor architecture)_RIS_Drivers directory of the unpacked files. For NetXtreme 2 1G, please select the driver in the b06nd51 directory. For 10G, please select the driver in evnd51. 4. Specifying network settings for NetXtreme II devices using the Microsoft unattended answer file does not work using the PCI Bus/Device/Function designation to specify adapters. This is due to the NDIS personality of the NetXtreme II device being a virtual device which means it does not have a physical Bus/Device/Function address. MAC address designation does work and may be used in conjunction with Bus/Device/Function for a complete solution. A program called netset.exe from Microsoft, available in the Windows 2000 Server Resource Kit, can also be used to apply network settings after the unattended install. Netset.exe uses the answer file to apply the network settings specified to the adapters in the system. See Microsoft Knowledge Base article 268781 for more information on netset.exe. 5. The first time diagnostics are run in a Windows environment on NetXtreme II devices, the diagnostic driver must be installed. Windows will either automatically install the driver, in which case, no action is required by the user, or Windows will ask to be directed to the INF file for the diagnostic driver. If you are prompted to install the driver, please direct the Windows dialog to search for the driver in the directory where the Broadcom driver package was unzipped. You may also search your hard drive for the file “bxdiag.inf.” If the file “bxdiag.inf” does not exist on your hard drive, you can run the Broadcom Installer “setup.exe” from the zip package included on the DSA Service Mode CD, or from the zip package downloaded from www.support.dell.com. Running the installer will place the diagnostic driver on your hard drive and prepare it for automatic install the next time it is needed by the Broadcom diagnostics. 6. When loading drivers through the PNP (Plug and Play) method, users can occasionally end up loading the RIS drivers accidentally. Generally this occurs when a user is asked to point to the proper driver for the device, and the user selects the folder containing the RIS drivers as the driver for the device. One indication that this had occurred is while loading the driver, a pop-up message should come up indicating that the driver is not digitally signed. Loading the RIS driver can result in network connections that fail to communicate across the network, as the NDIS driver will fail to bind to the devices. The most obvious way to identify the problem scenario is to open BACS and look at the network adapters displayed. Adapters that have the RIS drivers installed will be grayed out. Observing the driver loaded for the System Device portion of the Broadcom NetXtreme II devices will show that the RIS driver is loaded. Additionally, attempts to load the drivers using the installer will result in NDIS drivers displaying a yellow bang, as they are not able to bind to the VBD driver. The easiest way to correct the problem is to run add/remove programs on all installed Broadcom devices, and then re-run the installer. 7. Windows Pre-installation Environment (WinPE for short) does not contain native support for 5708, 5709, 5716, 57710,57711 and 57712 devices on operating systems prior to Windows Server 2008 R2. In order to “inject” driver support into Windows PE, refer to the steps provided by Microsoft at: http://support.microsoft.com/kb/923834/en-us. Broadcom 5708 Network Controller support is available as a native driver package in the Windows Server 2008 OS. 8. Network Teaming limitation with iSCSI offload: When iSCSI offload is enabled on Broadcom NetXtreme II NIC's or LOM's, only SLB teaming mode is supported. In order to create other teaming modes like 802.3ad and FEC/GEC, you will need to disable iSCSI offload. You can disable the iSCSI offload by a. launching the Broadcom Advanced control suite 3 (BACS 3). b. select the adapter you want to add to the team c. click the configurations tab, extend resource reservations. d. Uncheck iSCSI resource. 9. When iSCSI devices are installed on Windows Server 2003 or Server 2008, they will have same friendly name. View devices "by connections" in BACS3 on for managing iSCSI devices. 10. Restoring the team configuration with static IPv6 addresses may fail. Use either DHCP addresses for team configuration or restore team and re-apply the IP address manually if this issue is encountered. 11. If a DHCP supplied IP address cannot be acquired after performing an installation of RHEL5/RHEL4 on Dell PowerEdge servers, add an entry similar to the following into the ifcfg-ethx (where x is the interface being used) configuration file: LINKDELAY=12 This will add 12 seconds of timeout delay 13. When working in BACS while being logged into W2K3 x86 with a non-administrator account, the same icon that is used for a non-teamed adapter is being displayed for a teamed adapter. This is due to the fact the non admin account cannot query the driver due to insufficient privileges. 14. In order to ensure full functionality for the Broadcom 10G adapter, a minimum of 512 MB of system memory is required per network interface. Optimal performance may be achieved when there is 4-6 GB of memory or more per network interface depending on the system capabilities. 15. NetXtreme I and II Wake on LAN (WoL) and Linux -------------------------------------------------------------------- NetXtreme I and II WoL for use with Linux can be enabled in one of two ways: 1. By using ethtool from within the Linux operating system. 2. By using uxdiag.exe from DOS. Use of ethtool to enable WoL is only effective in cases where the relevant network interface is shut down before the server is powered off. If the network interface is not shut down before the server is powered off, then the system will not wake in response to receipt of a Magic Packet. Typically, during a graceful system shutdown, network interfaces are shut down before the system is halted. Network interfaces are known to not be shut down in the following cases. 1. When the iscsid service is enabled in Red Hat Enterprise Linux 5.x. 2. When the root filesystem resides on remote storage. 3. When the system is not shut down cleanly (e.g. removing main power while the system is running). 16. Windows Server 2008 R2 is expected to support the ability to utilize the TCP Offload Engine (TOE) on child partitions for supported Guest operating systems. However, the stack supporting this feature was not fully matured upon the completion of this Windows drivers release. As a result, we do not recommend enabling this capability with these drivers until an update to resolve these issues are released. 17. iSCSI Boot with an adapter not configured with an iBFT during initial remote install of Windows Server 2008 R2 will result in a BSOD. Please refer to the following Microsoft Knowledge Base article that addresses this behavior: http://support.microsoft.com/kb/976042/EN-US. 18. Remote install of Windows Server 2008 R2 over non-offload path (MSFT stack) with new Broadcom adapters, i.e. 57711/57712, which are not supported by the inbox driver will fail. The problem is due to a conflict between the inbox (boot.wim) driver not able to support the new adapters. Although the installer provides a newer driver externally during the installation, the OS reverts back to the inbox. Please refer to the workaround provided through the following link: http://attachments.wetpaintserv.us/JA9hJcVpHrEi11mJ19vYVg%3D%3D23856. Alternatively, Microsoft's propose solution is to build a custom install DVD by extracting the boot.wim and overwrite the .INF and .SYS files with Broadcom's newer driver set. Please read Microsoft's WAIK documentation for instruction process. Note: Remote install of Windows Server 2008 R2 over Broadcom iSCSI Offload path does not have an issue. 19. Receive Side Scaling (RSS) on TCP offloaded connections require a minimum of 8 gigabyte of RAM and only works for the 64-bit version of Windows Server 2008 and Windows Server 2008 R2. This feature is not supported in Windows Server 2003 due to a limitation in this operating system. RSS on non-offloaded connections, however, is supported for Windows 2003 SP2 and later. 20. After completing an installation in Windows server 2008 R2 on an iSCSI target, a system event may occur (source = VolMgr) where the description shows "The system could not successfully load the crash dump driver." The iSCSI crash dump driver must be enabled in the BACS3 application in order to suppress this message for the device being used for iSCSI boot. 21. The dual port 10Gb performance may not achieve full possible throughput for 57710 and 577111 devices, due to hardware limitations. 57712 does not have this hardware limitation and can achieve dual port 10G full throughput. In order to achieve optimal dual port performance on a Broadcom 10G adapter, a user should use a PCIE Gen2 x8 slot and the latest operating systems like Windows 2008 R2, RHEL5.5 and SLES11sp1. 22. If flow control is set to "Auto" and Jumbo frames are used, 57710/57711 devices will not advertise flow control. In order to enable flow control advertisement, please set flow control to TX & RX enabled. 23. When the optional 57711 device is present in the PowerEdge R910, using the force downgrade option provide in previous installers is not supported. 24. Downloading a large file using the VFlash feature from an NFS connection may terminate unexpectedly after booting up into an operating system. Disabling the driver in the operating system will allow for the download to resume. 25. Please read Linux 'linux_readme.txt' regarding usage of NetXtremeII driver package support. 26. W2K8 R2 Uninstall Chimney Offload State not being restored to the original value 27. An event appears in the Windows System Event Log after running the hardware diagnostics on some 5709/5708 LOMs of several systems on the first test. 28. Teaming backup and restore no longer defaults with BCG extension. Filename can be save as 'any' format and/or extension as end user would like to use. 29. Limited testing and support with IOMMU enabled systems. 30. 57810 SFP+ NIC WOL is only is only supported on 1 physical port, which is the port furthest away from the PCIe edge fingers (Port1). This board and requires 5.0W from 3.3V Aux for WOL operate correctly. 31. T7.2 linux driver set will not support FCoE for RH6.0. If FCoE support for 57712LRC is required for RH6.0, please use the software components from T6.4 CD 32. After the MFW is upgraded, FlexAddresses are lost on a PCIe reset. A cold reboot or complete AC power cycle is required 33. If SRIOV is enabled, system device may yellow bang after driver install. A system reboot is required. 34. Downgrading from the 7.6.x firmware to the 7.4.x firmware via Lifecyle Controler or USC will fail due to issues that exist in the 7.4.x Dell Update Package. Downgrade must be done from within a Linux or Windows OS if it is needed. 35. BACS for Linux does not work if Dell's OMSA (Open Manage Server Admistrator) is installed due to a conflict between OMSA and OpenPegasus. 36. BACS for Linux is not supported on SLES11 SP2 due to a conflict between OpenPegasus and OpenWBEM. OpenWBEM is a standard part of the SLES11 SP2 installation.