Intel(R) Network Adapter Software 9.0 Release Notes =================================================== Contents ======== - Viewing the user guide - Intel(R) PROSet for Windows* Device Manager - Intel PROSet for Windows Device Manager does not support previous release base drivers - Upgrading to Intel PROSet for Windows Device Manager - Connecting Intel PRO/1000 PT and PRO/1000 PT Dual Port Server Adapters Back-to-Back - Intel Fiber Optic Adapters - Saving and Restoring Adapter Settings - Installing Support for Teaming and VLANs - Teaming Notes - Removing Phantom Teams and Phantom VLANs - VLAN Creation Fails on a Team that Includes a Non-Intel Phantom Adapter - Preventing the Creation of Phantom Devices - Jumbo Frames - An Integrated Port Fails Offline Diagnostics in Linux* - Microsoft Windows Server 2003 x64 Notes - Microsoft Windows Server 2003 Notes - Microsoft Windows 2000 Notes - Novell NetWare* Notes - Assigning multiple IP addresses in Windows - Using Wake on LAN and Intel PRO/1000 PT, PT Dual Port, and PF Server Adapters - Known Issues - Customer support - File and driver Versions Viewing the user guide ======================= Additional information can be found in the User's Guide. To access it: 1. Click "View User Guides" from the autorun screen or navigate to the MANUAL directory and double-click index.htm OR 2. Go to Dell web support site: http://www.support.dell.com Intel(R) PROSet for Windows* Device Manager =========================================== Intel PROSet functionality is now integrated with the Windows Device Manager. To configure Intel adapters on Windows 2000 systems or newer, open the Windows Device Manager. Do not open adapter, team, or VLAN properties from the network control panel, as you may be prompted to reboot your system. You must have administrator rights to install or use Intel PROSet for Windows Device Manager. Intel PROSet for Windows Device Manager does not support previous release base drivers ================================================================= If you have installed Intel PROSet for Windows Device Manager and then install base drivers from a previous software release, Intel's custom Device Manager tabs will no longer appear. To correct this issue, reinstall Intel PROSet for Windows Device Manager. After clicking Install Base Drivers and Software, choose the Repair option in the Program Maintenance dialog box. Upgrading to Intel PROSet for Windows Device Manager ==================================================== If you upgrade from the previous version of Intel PROSet to Intel PROSet for Windows Device Manager, and any network adapters in the system have static IP addresses, make sure the adapters have link during the upgrade. If an adapter does not have link during the process, it will lose any static IP addresses assigned to it. Connecting Intel PRO/1000 PT and PRO/1000 PT Dual Port Server Adapters Back-to-Back ====================================================================== When connecting any combination of two Intel PRO/1000 PT or PRO/1000 PT Dual Port Server Adapters back-to-back, make sure both connected ports do not have the Smart Power Down feature set to "Reduce power when cable disconnected." If this option is selected on both adapter ports, they may not be able to establish link. Intel Fiber Optic Adapters ========================== Caution: The fiber optic ports may utilize Class 1 or Class 1M laser devices. Do not stare into the end of a fiber optic connector connected to a "live" system. Do not use optical instruments to view the laser output. Using optical instruments increases eye hazard. Laser radiation is hazardous and may cause eye injury. To inspect a connector, receptacle or adapter end, be sure that the fiber optic device or system is turned off, or the fiber cable is disconnected from the "live" system. The Intel PRO/1000 adapters with fiber optic connections operate only at their native speed and only at full-duplex. Therefore you do not need to make any adjustments. Use of controls or adjustments or performance of procedures other than those specified herein may result in hazardous radiation exposure. The laser module contains no serviceable parts. Saving and Restoring Adapter Settings ===================================== You can save and then restore adapter settings through the script SavResDX.vbs. Intel PROSet is required for SavResDX.vbs to function correctly. Installing Support for Teaming and VLANs ======================================== You must install Intel PROSet for Windows Device Manager if you want to use adapter teams or VLANs. Install Intel PROSet for Windows Device Manager by clicking Install Base Drivers and Software on the installation CD's autorun screen or running [operating system directory]\PROSETDX\PROSETDX.msi from the installation CD or downloaded files. Follow the instructions in the wizard and be sure to check Advanced Network Services on the Install Options screen. Teaming Notes ============= Team setup requirement ---------------------- Before creating a team, make sure each adapter is configured similarly. Check each adapter's settings in Intel PROSet. Settings to check include QoS Packet Tagging, Jumbo Frames, and the various offloads. If team members implement Advanced features differently, the team will align the settings with the least capable adapter. Changing Offload Settings for an Adapter in an ANS Team ------------------------------------------------------- When you disable an offload setting for an adapter in an ANS team, the team reloads and the team capabilities are recalculated. As a result, the offload setting is disabled for the remaining adapters in the team. Intel PROSet does not reflect the fact that the offload setting is disabled for the remaining adapters in the team. If you re-enable the offload setting for the original adapter in the team, the settings will not be applied until the system is rebooted or the team is reloaded. Teaming Known Issues -------------------- Network Connections window shows the team as disabled or network cable unplugged ---------------------------------------------------------------- After adding a VLAN to the team, this is normal. The connection protocols are now bound to the VLAN on the team. You can configure the connection protocols in the Properties for the VLAN. Team name doesn't change in Device Manager ------------------------------------------ If you modify a team name from the team property sheet, it may take several minutes for the name to change in Device Manager. Closing and opening Device Manager will load the new name. Changing speed and duplex of adapters in a team ----------------------------------------------- When you add an adapter to a Link Aggregation team using Intel PROSet, make sure that the adapter is running at the same speed and duplex of the other adapters in the team. IEEE 802.3ad teaming with Foundry switches ------------------------------------------ Foundry switches require an even number of ports in an aggregated link. If you remove an adapter from an 802.3ad team connected to a Foundry switch, make sure you maintain an even number of adapters in the team. QoS Load Balancing on ANS Teams without prioritizing packets is not Recommended ------------------------------------------------------------------- Enabling QoS load balancing on ANS teams without prioritizing packets will result in reduced performance. Non-Intel adapter not added to team ----------------------------------- A non-Intel adapter might not be added correctly to a team if the following has occurred: The non-Intel adapter was previously removed (via Device Manager) from a team, and a VLAN was later added to that team. Subsequently the team was uninstalled from Device Manager. If you create a new team that includes the non-Intel adapter, and the non-Intel adapter is not successfully added to that team, follow these steps to add the adapter: Click Modify Team on the Settings tab of the team properties dialog box. On the Adapters tab, select the non-Intel adapter, then click OK. Removing Phantom Teams and Phantom VLANs ======================================== If you physically remove all adapters that are part of a team or VLAN from the system without removing them via Device Manager first, a phantom team or phantom VLAN will appear in Device Manager. Follow these instructions to remove a phantom team or VLAN: Phantom team: Go to Team Properties, click the Settings tab, then click Remove Team. Phantom VLAN: In Device Manager, right-click the phantom VLAN icon and choose Uninstall. VLAN Creation Fails on a Team that Includes a Non-Intel Phantom Adapter ======================================================================= If you are unable to create a VLAN on a team that includes a non-Intel phantom adapter, use Device Manager to remove the team, then recreate the team without the phantom adapter, and add the VLAN to the team. Preventing the Creation of Phantom Devices ========================================== To prevent the creation of phantom devices, make sure you perform these steps before physically removing an adapter from the system: - Remove the adapter from any teams using the Settings tab on the team properties dialog box. - Remove any VLANs from the adapter using the VLANs tab on the adapter properties dialog box. - Uninstall the adapter from Device Manager. You do not need to follow these steps in hot-replace scenarios. Jumbo Frames ============ Some Intel gigabit adapters that support Jumbo Frames have a frame size limit of 9238 bytes, with a corresponding MTU size limit of 9216 bytes. The adapters with this limitation are based on the Intel 82571EB and 82572EI controllers, which also have these product names: Intel PRO/1000 PT Server Adapter Intel PRO/1000 PF Server Adapter Intel PRO/1000 PT Dual Port Server Adapter An Integrated Port Fails Offline Diagnostics in Linux ===================================================== In some cases, one port of a two-port integrated network connection Configuration based on the Intel 82541 Ethernet controller might fail when running offline diagnostics in Linux. If you stop the network service and then run offline diagnostics using a tool such as Ethtool or Dell OpenManage Server Administrator, one of the interfaces may fail the diagnostics. Run the diagnostics again to correct the problem. Microsoft Windows Server 2003 x64 Notes ======================================= Microsoft Windows Server 2003 x64 Known Issues ----------------------------------------------------------------- Traffic interruptions when creating a VLAN or team -------------------------------------------------- Creating a VLAN or a team temporarily interrupts traffic on all VLANs and teams on a Windows Server 2003 x64 system. Newly teamed adapter is disabled -------------------------------- If you add an adapter to a team with a VLAN, and the adapter has lower offloading capabilities than the team, then the adapter will appear disabled. Rebooting resolves this issue. Microsoft Windows Server 2003 Notes =================================== Microsoft Windows Server 2003 Known Issues ------------------------------------------ Traffic interruptions when creating a VLAN or team -------------------------------------------------- Creating a VLAN or a team temporarily interrupts traffic on all VLANs and teams on a Windows Server 2003 system with Service Pack 1 installed. WinMgmt warning messages in Event Viewer ---------------------------------------- Several warning messages are displayed in the Event Viewer after installing Intel PROSet. This occurs because Intel PROSet installs WMI classes. Intel PROSet has installed correctly. Microsoft Windows 2000 Notes ============================= Service Pack 4 Required for Microsoft Windows 2000 -------------------------------------------------- Windows 2000 Service Pack 4 is required for Intel network drivers and software to function correctly. Microsoft Windows 2000 Known Issues ----------------------------------- Incorrect command line parameters when running DXSetup.exe ---------------------------------------------------------- The version of Windows Installer in the base install of Windows 2000 is out of date. Please update to version 3.0 or 3.1. They can be found on the Microsoft website http://www.microsoft.com/downloads/ Novell NetWare* Notes ====================== Novell NetWare support for PCI Express devices ---------------------------------------------- PCI Express devices are supported in NetWare version 6.5 Assigning multiple IP addresses in Windows ========================================== If you assign multiple IP addresses to a single network connection in a Windows 2000 or Windows Server 2003 system, you must create a new DWORD value in the Registry: 1. Using the Registry Editor, browse to this registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318} 2. Under this key you will see multiple instances of four-digit incrementing numeric values, i.e. 0000, 0001, 0002, etc. Click on each of the values within this key and find the key(s) of the Intel adapter(s) in the system. You can identify the Intel adapters by checking the value of the DriverDesc string value. 3. Add a new DWORD value in the key for each Intel adapter that will use multiple IP addresses. (Click Edit > New > DWORD Value.) 4. Name the new DWORD "WaitAutoNegComplete". This DWORD is case-sensitive. 5. Set the WaitAutoNegComplete value to 1. Using Wake on LAN and Intel PRO/1000 PT, PT Dual Port, and PF Server Adapters ============================================================================= Wake on LAN (WOL) is disabled by default on these adapters. Before allowing a system containing one of these adapters to go into hibernation, use IBAUtil to enable Wake on LAN (WOL) on the adapter. Once the system is in a hibernate state, only a magic packet will wake it up. Other directed packets will have no effect. See the Intel Boot Agent Guide for more information on using IBAUtil. Known Issues ============ Procedure for installing and upgrading drivers and utilities ------------------------------------------------------------ Intel does not recommend installing or upgrading drivers and Intel(R) PROSet software over a network connection. Instead, install or upgrade drivers and utilities from each system. To install or upgrade drivers and utilities, follow the instructions in the User Guide. Installing Intel PROSet and Intel PROSet for Windows Device Manager on the same system ---------------------------------------------------------------------- Intel prevents installing both Intel PROSet and Intel PROSet for Windows Device Manager on the same system. When you install Intel PROSet for Windows Device Manager, prior versions of PROSet are uninstalled automatically. "Malicious script detected" warning from Norton AntiVirus during PROSet Uninstall ---------------------------------------------------------------- The Intel PROSet uninstall process uses a Visual Basic script as part of the process. Norton AntiVirus and other virus scanning software may mistakenly flag this as a malicious or dangerous script. Letting the script run allows the uninstall process to complete normally. "The Location You Specified Does Not Exist or Cannot Be Reached" Error during driver installation ---------------------------------------------------------------------- This is a known issue with Windows Server 2003. Please see Microsoft Knowledge Base article 819586 for workarounds and a possible patch. "Out Of Disk Space" Message during Installation ----------------------------------------------- The boot partition requires a minimum of 15 MB free space in order to install Intel PROSet, regardless of which drive you specify for installation. If there is insufficient space on the partition you will see this error message, and the product will not install. Throughput reduction after Hot-Replace -------------------------------------- If an Intel gigabit adapter is under extreme stress and is hot-swapped, throughput may significantly drop. This may be due to the PCI property configuration by the Hot-Plug software. If this occurs, throughput can be restored by restarting the system. System Wakes-Up from a Removed VLAN ----------------------------------- If a system goes into standby mode, and a directed packet is sent to the IP address of the removed VLAN, the system will wake-up. This occurs because a directed packet bypasses VLAN filtering. Intel PRO Adapters ignore consecutive Wake Up signals while transitioning into standby mode ----------------------------------------------------------- While sending a system into standby, occasionally a wake up packet arrives before the system completes the transition into standby mode. When this happens, the system ignores consecutive wake up signals and remains in standby mode until manually powered up using the mouse, keyboard, or power button. Intel PRO/1000 Adapters (copper only) do not detect active link during load time --------------------------------------------------------------- Some Intel PRO/1000 adapters, especially copper adapters, cannot detect an active link during load time. To resolve this issue, try the following workarounds. - Re-attach to the server without reloading the driver. - For DOS-based installations, add a delay of 4 to 5 seconds in the batch file after the load driver command. - Load the configuration by manually entering commands. - Set adapter to link at 1000 Mbps only. WOL and Standby options not available when connecting to a Gigabit Only switch (copper adapters only) ----------------------------------------------------------------------- When a copper media adapter is connected to a Gigabit-only switch, the WOL and Standby features are unavailable. This is due to the power consumption level of the adapter. The Intel PRO/1000 MF Server Adapter supports WOL, but uses fiber media. TCP Segmentation for Windows 2000 --------------------------------- The advanced feature TCP segmentation is not supported in Windows 2000 for Intel(R) PRO/1000 Server adapters. Windows Server 2003 does support this feature for Intel PRO/1000 Server Adapters. Intel PRO/1000 Adapter will not have Link when forced to operate at 10 or 100 Mbps with a link partner is also forced to the same state ------------------------------------------------------------------- Unless copper Gigabit Adapters are set to auto-negotiate, they are not MDI/MDI-X aware. When an Intel PRO/1000 Adapter is forced to operate at 10 or 100 Mbps, the adapter will not have a link with the link partner under the following circumstances: - If a link partner is also forced to operate at 10 or 100 Mbps, is connected back to back, and is connected using a regular cable instead of a crossover cable. - If a link partner is also forced to operate at 10 or 100 Mbps, connected to a switch, and connected using a crossover cable instead of a regular cable. Using Intel PRO/1000 XT Adapters and e1000ODI.COM Driver -------------------------------------------------------- In some cases, an Intel PRO/1000 XT adapter using the e1000ODI.COM driver will not receive traffic. You can fix this problem by disabling Wake On LAN (WOL) in the adapter hardware before connecting to the network. VLAN Creation Fails on a Team that Includes a Non-Intel Phantom Adapter ----------------------------------------------------------------------- If you are unable to create a VLAN on a team that includes a non-Intel phantom adapter, use Device Manager to remove the team, then recreate the team without the phantom adapter, and add the team to the VLAN. Customer Support ================ - Main Dell web support site: http://www.dell.com Legal / Disclaimers =================== Copyright (C) 2002-2006, Intel Corporation. All rights reserved. Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make any commitment to update the information contained herein. * Other product and corporate names may be trademarks of other companies and are used only for explanation and to the owners' benefit, without intent to infringe. File and driver versions ======================== Windows base drivers -------------------- Windows 2000 Gigabit Ethernet (e1e5032.sys): 9.2.24.1 Windows Server 2003 Gigabit Ethernet (e1e5132.sys): 9.2.24.1 Windows Server 2003 EM64T Gigabit Ethernet (e1e5132e.sys): 9.2.24.1 Windows ANS drivers ------------------- Windows 2000 (iansw2k.sys): 8.1.25.1 Windows Server 2003 (ianswxp.sys): 8.1.25.1 Windows Server 2003 EM64T (iansw32e.sys): 8.1.25.1 Windows applications -------------------- Intel DMIX for Windows (dxsetup.exe): 10.2.78.5 Intel DMIX for Windows EM64T (DxSetup.exe): 10.2.78.5 Intel SNMP agent (ILanSnmp.dll): 1.64.0.2000 Intel SNMP agent EM64T (ILanSnmp.dll): 1.64.0.0 Red Hat Linux base drivers -------------------------- Gigibit Ethernet (e1000.o): 6.2.15.6 DOS base drivers ---------------- Gigabit Ethernet NDIS2(e1000.dos): 4.55 Gigabit Ethernet DOS ODI (e1000odi.com): 3.58 IBA images ---------- Gigabit Ethernet IBA (BA1230M2.FLB): GE v1.2.30