ibm x3400m2 Broadcom NetXtreme II BMC5709 网卡驱动

Broadcom (R) NetXtreme II (TM) Ethernet Software CD for IBM eServer BladeCenter and System x NetXtreme II Gigabit and 10 Gigabit Ethernet products RELEASE 5.2.17.0d (06/10/2010) ===================================================================================== This software release package is based on the Broadcom T5.2.4.7 Drivers Software Kit. The CD provides all device drivers and associated software for all IBM BladeCenter and System x Broadcom-based NetXtreme II Ethernet products, including 1Gb Ethernet and 10Gb Ethernet for both on-board Ethernet and adapter options. The Microsoft Windows device drivers are Microsoft digitally signed. WARNING: Any x3850M2/x3950M2 server is required to be updated to Version 1.05 (Build A3E145A) system BIOS, or later, prior to any device driver software update. CONTENTS -------- 1.0 Overview 2.0 Drivers Software Details 3.0 Installation and Configuration 4.0 Web Sites and Support Phone Number 5.0 Trademarks and Notices 6.0 License and Disclaimer 1.0 Overview _____________ This software CD includes device drivers, related software, and installation guide for all IBM BladeCenter and System x Broadcom-based NetXtreme II products, across 1Gb Ethernet and 10Gb Ethernet, for both on-board Ethernet and options. The supported Broadcom (R) NetXtreme II (TM) chipsets include BCM5706, BCM5706S, BCM5708, BCM5708S, BCM5709, BCM5709S, BCM57710, and BCM57711. The supported adapter options include: 39Y6066 - NetXtreme II 1000 Express Ethernet Adapter 42C1780 - NetXtreme II 1000 Express Dual Port Ethernet Adapter 42C1790 - NetXtreme II 10 GigE Express Fiber SR Adapter 44W4479 - 2/4 Port Ethernet Expansion Card CFFh for IBM BladeCenter 44W4465 - 2/4 Port 10Gb Ethernet Expansion Card CFFh for IBM BladeCenter The operating systems supported include Windows 2003, Windows 2008 and Windows 2008 R2. The server platforms supported include x86, x64, and AMD64. 2.0 Drivers Software Details ______________________________ Key Fixes & Enhancements with this T5.2.4.7 sw CD release include: =================================================================== - NX2 1Gbps VBD : fixed BSOD caused by incorrect detection of processor count on some systems. - NX2 1Gbps VBD : fixed problem servicing interrupts on systems with more than 64 CPUs. - added new NX2 10Gbps eVBD that addresses several critical issues - added new NX2 1Gbps Linux bnx2 driver that improves performance as well as fixes an MSI-x specific problem - NX2 10Gbps eVBD: reduced NPP pool usage by close to ~450KB per offloaded connection - NX2 1Gbps VBD : detect and prevent internal FIFO data overflow (L4 only) - 57711 boot code: decrease EFI driver load time NOTES: (1) When updating drivers via UXSPi, the utility will prompt version number(s) of drivers loaded on system that are pertinent to the Operating System being updated. After the utility completes and drivers are updated, there may be some driver version(s) where the New Version does not match the Installed Version. This may be because the adapter corresponding to the driver is not installed. Adapters must be installed to gain proper version numbers from the utility. Please disregard version numbers that do not pertain to the adapter(s) you have installed. (2) When extracting files from this package, Windows 2008 R2 extract to floppy may not work. This is due to change in Windows security settings, and may become a limitation. (3) Microsoft Windows 2008 Server Support BACS3 will require .NET to be pre-installed prior to launching the application. When hot adding an adapter with BASP6 Jumbo frame is only supported with all members running the same MTU size. The latest drivers can also be downloaded from: http://www.ibm.com/support/us. (4) The Broadcom VBD architecture supports Windows 2003 and Windows 2008 Server platforms. The software components under "b06bdrv" and "l2nd" from \W2K are designed to run normal L2 NDIS traffic for NDIS 5.0. The software components under "b06bdrv" and "l2nd" from \W2K3_W2K8 and \W2K3_W2K8_64 are designed to run normal L2 NDIS traffic for NDIS 5.2 and NDIS 6.0. The software components under "b06bdrv" and "l4nd" from \W2K3_W2K8 and \W2K3_W2K8_64 are designed to run normal L4 NDIS traffic for NDIS 5.2 for BCM5706, 5708 and some BCM 5709 devices. (5) The NetXtreme II drivers have two parts, the VBD driver and the NDIS Client driver. (6) 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. (7) 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.� (8) When loading drivers through the PNP (Plug and Play) method, users can occasionally end up loading the RIS drivers accidently. 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. This 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�re 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. (9) 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. (10) 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 th