Release Notes HP Fast Ethernet and Gigabit Server Adapters Release Notes for Software Version 8.37 ============================================ -------- CONTENTS -------- I. OVERVIEW SOFTWARE VERSION 8.37 II. PRODUCT SUPPORT FOR SOFTWARE VERSION 8.37 III. SOFTWARE RELEASE NOTES IV. HARDWARE RELEASE NOTES --------------------------------- I. OVERVIEW SOFTWARE VERSION 8.37 --------------------------------- The drivers and applications on Version 8.37 of the software are compatible with previously released adapters, upgrade modules, and operating systems unless as noted elsewhere in the documents. --------------------------------------------- II. PRODUCT SUPPORT FOR SOFTWARE VERSION 8.37 --------------------------------------------- The adapters and upgrade modules listed below are supported options for selected HP ProLiant servers. Stand-alone adapters: --------------------- --HP NC150T PCI 4-port Gigabit Combo Switch Adapter --HP NC310F PCI-X Gigabit Server Adapter --HP NC320T PCI Express Gigabit Server Adapter --HP NC340T PCI-X Quad-Port Gigabit Server Adapter --HP NC370T PCI-X Multifunction Server Adapter --HP NC370F PCI-X Multifunction Server Adapter --HP NC373F PCI Express Multifunction Gigabit Server Adapter --HP NC380T PCI Express Dual Port Multifunction Gigabit Server Adapter --HP NC1020 Cu Gigabit Server Adapter 32 PCI Single Port --HP NC3122 Fast Ethernet Server Adapter * --HP NC3123 Fast Ethernet Server Adapter * --HP NC3131 Fast Ethernet Server Adapter (Dual Base 10/100) * --HP NC3132 Fast Ethernet Upgrade Module (Dual 10/100) for the NC3131 and NC3134 Server Adapters * --HP NC3133 100FX Upgrade Module for the NC3131 and NC3134 Server Adapters * --HP NC3134 Fast Ethernet Server Adapter (Dual Base 10/100) * --HP NC3135 Fast Ethernet Upgrade Module (Dual 10/100) for the NC3131 and NC3134 Server Adapters * --HP NC6132 1000 SX Gigabit Upgrade Module for the NC3131 and NC3134 Server Adapters * --HP NC6133 1000 LX Gigabit Upgrade Module for the NC3131 and NC3134 Server Adapters * --HP NC6134 Gigabit Server Adapter (PCI 1000 SX) --HP NC6136 Gigabit Server Adapter (PCI 1000 SX) --HP NC6170 Dual-Port PCI-X Gigabit Server Adapter --HP NC6770 PCI-X Gigabit Server Adapter --HP NC7131 Gigabit Ethernet Server Adapter --HP NC7132 Gigabit Ethernet Upgrade Module for the NC3131 and NC3134 Server Adapters * --HP NC7170 Dual-Port PCI-X Gigabit Server Adapter --HP NC7770 PCI-X Gigabit Server Adapter --HP NC7771 PCI-X Gigabit Server Adapter Embedded adapters: ------------------ --HP NC320i PCI Express Gigabit Server Adapter --HP NC320m PCI Express Dual Port 1Gb Server Adapter for c-Class BladeSystem --HP NC324i Dual Port PCI Express Gigabit Server Adapter --HP NC325i PCI Express Dual Port Gigabit Server Adapter --HP NC326i PCI Express Dual Port Gigabit Server Adapter --HP NC326m PCI Express Dual Port 1Gb Server Adapter for c-Class BladeSystem --HP NC370i PCI-X Multifunction Gigabit Server Adapter --HP NC371i PCI-X Multifunction Gigabit Server Adapter --HP NC373i PCI Express Multifunction Gigabit Server Adapter --HP NC373m PCI Express Dual Port Multifunction Gigabit Server Adapter for c-Class BladeSystem --HP NC374m PCI Express Dual Port Multifunction Gigabit Server Adapter for c-Class BladeSystem --HP NC3161 Fast Ethernet Server Adapter * --HP NC3163 Fast Ethernet Server Adapter * --HP NC7760 PCI-X Gigabit Server Adapter --HP NC7761 PCI Gigabit Server Adapter --HP NC7780 Gigabit Server Adapter --HP NC7781 PCI-X Gigabit Server Adapter --HP NC7782 Dual Port PCI-X Gigabit Server Adapter * Not supported in Windows Server 2003 x64 --------------------------- III. SOFTWARE RELEASE NOTES ---------------------------- A. General ---------- Ensure your Switch Complies with Latest Upgrades ------------------------------------------------ --For reliable Gigabit Ethernet networking connectivity, contact your switch vendor and ensure that your switch complies with their latest firmware/hardware upgrades. Configure iSCSI VLAN with Static IP Address ---------------------------------------------------------------------- --When configuring the iSCSI VLAN on a Multifunction Server Adapter, it must have a static IP address. Currently, when a VLAN for the iSCSI adapter is enabled, the iSCSI VLAN adapter cannot receive addresses from the DHCP server. This option will be enabled in an upcoming release. Configuring for Jumbo Frames Using Maximum Frame Size Option ------------------------------------------------------------ --When configuring your HP NCXXXX series server adapters for Jumbo Frames using the "Maximum Frame Size" option, the displayed Maximum Frame size does not include the 4-byte CRC/FCS on the frames to be transmitted that is greater than 1514 bytes. Due to the interpretation of the IEEE specification by some switch vendors, the CRC/FCS bytes may or may not be included in their Jumbo Frame configuration. If allowed, you must adjust the Jumbo Frame size on the switch to at least 4 bytes larger than the maximum frame size set on the adapter. (It is acceptable to have the frame size larger on the switch than on the adapter.) If your switch does not allow for the granular manipulation of frame sizes, do not enable the maximum frame size (Jumbo Frames) for your adapters and contact your switch vendor for further assistance. Jumbo Frames is not supported on NC150T, NC1020, and NC7761 server adapters. NC71XX Server Adapters -- HP ProLiant 6500 and 7000 Servers --------------------------------------------------------------- --For HP ProLiant 6500 and 7000 servers--when using NC71XX server adapters ensure that the IOQ (in order queue) is set to one (1) by using the HP setup program F10 (advanced mode Ctrl+A). Recommendations Before Using Hotplug ------------------------------------ --HP recommends that the server adapter software be updated to the latest version before attempting Hotplug add, replace, or remove of server adapters. Creating Floppy Disks for Installations --------------------------------------- --If you need to use a floppy disk to install the adapter drivers, use the MAKEDISK.BAT utility located in the root directory on this CD-ROM. When you run the utility, it prompts for operating system type and drive locations. NC6132 Upgrade Module -- Identifying the ASIC Version for PCI Hot Plug ---------------------------------------------------------------------- --PCI hot plug replace may not operate on an NC6132 upgrade module running Windows NT(R) 4.0 and NetWare(R). This is because the NC6132 can contain two different revisions of the ASIC chip. If you replace one revision of the NC6132 with a different revision containing a different ASIC, the NC6132 will not power up. For PCI hot plug to work on an NC6132 upgrade module, the vendor ID, device ID, revision ID, and subsystem ID must be identical to the original upgrade module. To identify "like" boards for replacement, match the ASIC part number, either 695314-001 or 695314-003. You can locate the ASIC on the upgrade module at U2. It is labeled "LSI." B. Microsoft(R) NT 4.0, Microsoft Windows(R) 2000, Microsoft Windows Server(TM) 2003, and Microsoft Windows Server(TM) 2003 x64 ------------------------------------------------------------------------------- Installation of Multifunction (NC37x/NC38x) Gigabit Server Adapters using Remote Installation Services (RIS) Requires RIS Drive ------------------------------------------------------------------------------- --When performing RIS installations on Multifunction Gigabit Server adapters, you must use the RIS driver located in the \RIS sub-directory for your operating system on the HP Software and Documenation CD. Multifunction Gigabit Server Adapter Driver Component for Windows Server 2003 x64 ------------------------------------------------------------------------------- --CP006388.exe, which provides drivers for the family of multifunction adapters, is not signed by Microsoft’s WHQL process. Consequently, you will receive several pop-ups when installing this software and when running diagnostics the first time. The pop-ups will say that the software has not been certified by Microsoft. Please select "Yes" every time when asked while installing the software. Windows Server 2003 and Windows Server 2003 x64 -- Enabling TCP/IP Offload Engine and Receive Side Scaling (RSS) ------------------------------------------------------------------------------- --TOE and RSS capabilities are only available through adapters running Microsoft Scalable Networking Pack (SNP) on Window Server 2003 SP1 and above or Windows Server 2003 x64. Windows Server 2003 and Windows Server 2003 x64 -- Teaming an adapter with TOE or RSS enabled ------------------------------------------------------------------------------- --Adding a TOE- or RSS-enabled adapter to a team disables TOE and RSS, repectively for that adapter. TOE and RSS teaming is not supported in this release. Windows 2000, Windows Server 2003, and Windows Server 2003 x64 Driver Components -------------------------------------------------------------------------------- --Network driver files (in flat file format) have been replaced by individual .EXE files corresponding to the various HP Network Driver Components for Microsoft Windows 2000 and Windows Server 2003. If necessary, these components can be installed individually or their contents extracted to a floppy disk or hard drive for manual installation. HP Network Configuration Utility -- DO NOT IGNORE REBOOT REQUESTS ----------------------------------------------------------------------- --DO NOT IGNORE ANY REBOOT REQUESTS from the HP Network Configuration Utility. A reboot may be required after making changes using this Utility. Windows 2000, Windows Server 2003, and Windows Server 2003 x64 -- Installing two or more iSCSI-enabled Multifunction adapters in your system ---------------------------------------------------------------------------- --When installing two or more Multifunction adapters that have iSCSI enabled on them, the number of free system page table entries can become low, which can cause system instability. Recommended memory requirements are as follows: One Multifunction adapter: Minimum memory—500M Recommended memory—1G Two or more Multifunction adapters: Minimum memory—1G Recommended memory—2G These RAM requirements do not apply if the adapters are not iSCSI enabled. NT4 -- NC3134 Adapter Installed and Teamed in a DL360 ---------------------------------------------- --An NC3134 adapter installed and teamed in a DL360 will not allow the user to log in and it locks up Windows NT. This is an unsupported adapter in this platform. NT4 -- Control Register Test ---------------------------- --The NC7131 Control Register Test may fail when you run Diagnostics while a ping is running on the server. This is expected behavior. Run Diagnostics without any other programs running. NT4 -- Error Counters --------------------- --The NC7131 statistics may show Receive CRC Errors increment then decrement back to 0 and not maintain a running counter. After running Diagnostics, the NC7131 Receives CRC Error counter increments steadily with no traffic running. NT4 -- Statistics on NC31xx Adapters ---------------------------------- --Statistics on NC31xx adapters and teamed adapters do not work after Diagnostics have been run on the adapter. NT4 -- Unsupported Adapters ---------------------------------- --NT4 is only supported on adapters that shipped before January 1, 2003. PCI Hot Plug Utility -- "HP Ethernet, Fast Ethernet or Gigabit Upgrade Module" -------------------------------------------------------------------------------- --HP PCI Hot Plug utility may identify an upgrade module with its generic definition of "HP Ethernet, Fast Ethernet or Gigabit Upgrade Module" instead of the precise model number. Windows -- Jumbo Frames ------------------------ --HP recommends only using IP version 4 with Jumbo Frames. Windows 2000 -- Jumbo Frames ---------------------------- --Changing the Jumbo Frame size in the HP Network Configuration Utility should not be performed while Netmon is running. Windows 2000 -- Silent Upgrade of Teaming ----------------------------------------- --When updating Teaming drivers (CPQTEAM.SYS v6.21621.3 and less) via a silent install method, the update is not complete if a network team is being utilized on the server being upgraded. The teaming software must be evoked via the Tray icon after the upgrade's initial reboot in order to support "Advanced Settings." A pop-up message appears advising that the Cancel button will be disabled and changes applied. The user does not need to invoke the Teaming software to have a team that works with the newly-installed software. Windows 2000 - NCU Online Help File Distorted in 256 colors ------------------------------------------------------------- --Viewing the NCU online help file in 256 colors causes images to be distorted and illegible. Change your monitor's display color quality property to either 16-bit or 32-bit. Windows Server NT 4.0 -- SmartSwitch Teams --------------------------------------------------------- --Configured SmartSwitch teams may switch from the Primary adapter to the Secondary adapter continuously if not connected to the same physical switch. All SmartSwitch teams should be terminated to a single physical switch. NC3133 FX Server Adapter -- Cable Test Diagnostics -------------------------------------------------- --Cable test diagnostics for the NC3133 FX server adapter are not available. Windows 2000, Windows Server 2003, and Windows Server 2003 x64 -- Network Adapter Scripting -------------------------------------------------------------------------------- --The HP Network Configuration Utility enables configuration of network adapters and teams of network adapters. The scripting feature of the utility provides the ability to perform adapter configuration using a batch process. Refer to "Network Adapter Scripting" on the NICSCRPT.PDF file for more information. Windows 2000, Windows Server 2003, and Windows Server 2003 x64 -- Automatic Team Type -------------------------------------------------------------------------------- --Selecting "Auto" team type for a team that includes a Gigabit adapter and a Fast Ethernet adapter will set the team type to TLB with only the Gigabit adapter transmitting and receiving. This provides the best performance based on the adapters capabilities. This is the expected behavior. HP Network Configuration Utility Recommended -------------------------------------------- --HP recommends you use the HP Network Configuration Utility for the configuration of any HP server adapter. There will be differences between this utility and the Microsoft Network and Dial-up Connections interface. Windows 2000, Windows Server 2003, and Windows Server 2003 x64 -- Team State Stays Degraded ---------------------------------------------------------------------------- --When Diagnostics are run on adapters configured with a team, the HP Network Configuration Utility shows the tested adapter as degraded. This is expected behavior. Windows 2000 and Windows Server 2003 -- Receive Overruns -------------------------------------------------------- --An NC3123 operating in an SLB team may register Receive Overruns in the statistics for the adapter. Receive Overruns are common but if excessive contact Customer Support. Windows 2000, Windows Server 2003, and Windows Server 2003 x64 -- Incorrect IRQ Information --------------------------------------------------------------------------- --The HP Network Configuration Utility may display incorrect IRQ information on dual port HP adapters. The correct IRQ information can be found using the systems configuration utility or through the Microsoft user interface for networking. Teaming Redundant Adapter Pairs ---------------------------------- --In upgrading to Windows 2000, certain steps are necessary to maintain teaming for redundant adapter pairs. This is because several different utilities manage teaming under Windows NT 4.0. The necessary steps are described in \DOCS\REFERENCE\PRIMER.HTM. Using the "Unplug or Eject Hardware" Icon -------------------------------------------- --In a system supporting PCI hot plug, some servers do not have a power switch on the slot where the adapter is installed. In this case, you cannot remove/stop an adapter using the Windows Server 2003/Windows 2000 Unplug or Eject Hardware icon without first doing a server cold reboot. This means you must turn the server off and then back on. If you power down an adapter with the intention of permanently removing it, unteam the adapter (drop it from the team). It will disappear from the list of adapters in the NCU Main window of the HP Network Configuration Utility. This only occurs on servers without the power switch on the adapter slot. These include HP ProLiant TM 6500 and ProLiant 7000 servers. Using the Primer Utility --------------------------- --Primer is a HP utility that lets you remove unsupported Windows 2000 utilities before or after upgrading your OS. Before running Primer, we recommend that you record all Windows NT 4.0 teaming configuration settings. After you run Primer and upgrade the OS to Windows 2000, you can install the new "HP Network Configuration" utility for Windows 2000 and re-configure the adapter teams. To locate the Primer executable, PRIMER.EXE refer to the HP Softpaq #10652 at http://h18007.www1.hp.com/support/files/server/us/download/10776.html. NT4 Teaming ----------- --Updating drivers using the upgrade option on the HP Teaming and Configuration Utility version 6.X will not update to the new utility properly. The only recommended upgrade procedure is to run “Install” from the HP CD NT4 directory. --Several statistics counters may increment even without cables attached to the NIC. Total Heartbeats, Total Transmits, and Total Receives counters may increment when cables are not connected. The Heartbeat count is being captured on transmits only and not receives. The Transmit and Receive counters will increment due to internal transmits and receives between the teaming driver and the base driver. Windows 2000 Teaming -------------------- --The component list in a Windows 2000 Local Area Connection Property Sheet is different for HP Network Configuration Utility when upgrading from NCDE 6.x to 8.x than when installing a fresh copy of NCDE 8.x. When upgrading an NCDE 6.x installation to 8.x, the HP Network Configuration protocol has the check box enabled. When NCDE 8.x is freshly installed, the HP Network Configuration protocol has the check box disabled. This has no practical consequence because the protocol cannot be bound or unbound using the Local Area Connection property sheet. When the check box is enabled and the user attempts to change the state (selected or unselected), a dialog displays informing the user that the HP Network Configuration Utility must be used to bind or unbind the protocol to a network connection. --If QOS is configured in the HP Network Configuration Utility Version 6.X and you are attempting to upgrade to 8.X of the utility, the QOS configuration will not migrate properly. QOS must be reconfigured for Version 8.X. C. Novell NetWare ----------------- --If you receive a “Relinquish Control Error,” it can be safely ignored. Set “Display Relinquish Control Alerts”= OFF if you do not want to see these error messages. --If you set Probes=ON with Ethernet 802.2 or Ethernet 802.3, you MUST load Ethernet_II as well. You do not have to bind any protocol to Ethernet_II. --DHCP failures occur when upgrading NW5.1 and NW6.0 to SP5 and SP2 respectively. There is a Novell document, TID10074067 entitled, "Communication problems after applying NW5.1 SP5 or NW6.0 SP2." This TID explains that after update of Service Packs, the B57.lan driver causes several problems, including communications problems, all UDP traffic only generated from NICs, client not getting DHCP addresses, NFS Mount request time outs, RPC time outs, CLNTRUST failures, Groupwise shows no new mail without refresh or busysearch is running very slow, or loading Groupwise MTA or POA taking over 10 minutes to complete. There is a workaround in the TID that states to set the parameter of CHECKSUM=OFF on the first loading driver. If using INETCFG.nlm, the NETINFO.CFG file will need to be modified manually in order to enter CHECKSUM=OFF on the command line for the first loading driver. Then, modify NETINFO.CHK and change the CHECKSUM value to 0. Note that With this workaround, rebooting the server will reset this setting. D. DOS Diagnostics ------------------ --Running the DOS diagnostics with the -bus option specifies testing of all devices on the specified bus. Specification of a unique card using the bb:dd notation for bus number and device number is no longer supported. --Running the DOS diagnostic external loop back tests on the NC1020 and NC77XX using Q57diag driver with the “-T D3” option will fail at 1000Mbps. A loop back connector is not supplied for gigabit connections. --Running the DOS diagnostics for the NC1020, NC67xx, and NC77XX series NICs will fail the “External SRAM” test. This is expected behavior due to the unavailability of SRAM on the adapters. Avoid using the –B6 option. --On LOM designed NICs, PXE and WOL can only be enabled or disabled through ROM- Based Set Up (RBSU) utility and not through the user diagnostics. --Running the DOS diagnostics from a CD will generate a DOS error (GENERAL FAILURE WRITING DRIVE A) for some of the tests that require the diagnostic to write back to the drive. To run DOS diagnostics on servers that do not have floppy drives, it is recommended that a RAM drive or a virtual floppy drive be used. -------------------------- IV. HARDWARE RELEASE NOTES -------------------------- A. Cabling for Gigabit Over Copper ---------------------------------- The NC150T, NC320T, NC340T, NC370T, NC380T, NC1020, NC71xx, NC77xx adapters,LOMs, and Mezzanine cards use existing CAT5 cabling. For new cabling installations, the IEEE 802.3ab Standard recommends using CAT5e (enhanced Category 5) cabling.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.