Intel(R) Network Adapter Software Release Notes
===============================================
July 7th, 2008
Contents
========
- Supported Operating Systems
- Viewing the User Guide
- Intel(R) PROSet for Windows* Device Manager
- Upgrading to Intel PROSet for Windows Device Manager
- Intel Fiber Optic Adapters
- Saving and Restoring Adapter Settings
- Connecting Intel PRO/1000 PT and PRO/1000 PT Dual Port Server
Adapters Back-to-Back
- Intel I/O Accelerated Technology
- Teaming Notes
- Jumbo Frames and Jumbo Packets
- Microsoft Windows Server 2008 Notes
- Microsoft Windows Server 2003 x64 Notes
- Microsoft Windows Server 2003 Notes
- Quad Port Server Adapter Notes
- Using Wake on LAN and Intel PRO/1000 PT, PT Dual Port, and
PF Server Adapters
- Known Issues
- Customer Support
- Supported Adapters
- Legal / Disclaimers
- File and Driver Versions
New in this release
===================
1. Microsoft Windows Server 2008 Driver support for DPN (Dell Part Number) YT674
Intel Gigabit VT Quad Port Server Adapter
Supported Operating Systems
===========================
This CD contains software and drivers for Microsoft* Windows Server
2008*, Windows Server 2003*.
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 Server 2003 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.
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.
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 Gigabit and 10GbE network 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. The Restore operation requires the same OS as when the
configuration was Saved.
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 Power Saver Option 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(R) I/O Acceleration Technology
====================================
Intel I/OAT requires the following to operate on Microsoft Windows
Operating Systems:
- A server chipset and BIOS that are Intel I/OAT capable
- Microsoft Windows Server 2008 or
- Microsoft Windows Server 2003 with Service Pack 1 or 2 installed
- The Scalable Networking Pack from Microsoft (this is installed as part
of Service Pack 2 or Windows Server 2008)
- An adapter or network connection that is Intel I/OAT-capable
- The RSS advanced setting must be enabled
- Under TCP/IP Offloading Options, both Offload Receive IP Checksum and
Offload Receive TCP Checksum must be enabled.
For more information about the Scalable Networking Pack, please see
http://support.microsoft.com/kb/912222/article
I/OAT Known Issues
------------------
No DMA activity on Intel I/OAT-capable ports
--------------------------------------------
At least one Intel I/OAT-capable port must be enabled when your system
starts up. If no Intel I/OAT-capable ports are enabled at system startup,
the IOATDMA driver will not register with NDIS and Intel I/OAT-capable
ports enabled after system startup will show no DMA activity. Enable an
Intel I/OAT-capable port and reboot to resolve this issue.
DMA copies are lower than expected
----------------------------------
Some software applications do not utilize the full range of performance
enhancements available with Intel I/OAT. Please check with your software
vendor for an updated version.
CPU utilization is not balanced across all CPUs
-----------------------------------------------
CPU and DMA channel load may be unbalanced under the following conditions:
- The system is using Intel I/OAT, and
- There are multiple PCI Express LAN ports (both Intel I/OAT or
non-Intel I/OAT) in the system, and
- One or more of the PCI Express ports are not utilized or not enabled
for Intel I/OAT
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.
IEEE 802.3ad teaming on Cisco trunks
------------------------------------
When implementing 802.3ad teams on Cisco switch ports in trunking mode,
set the native/untagged VLAN for these ports to ID 1. Otherwise, you may
experience traffic loss or lack of failover between aggregators. See your
Cisco documentation for information about setting the native VLAN ID.
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.
Removing a teamed adapter from a hot-plug system
------------------------------------------------
When you physically remove an adapter that is part of a team or a VLAN,
you must reboot or reload the team/VLAN before using that adapter in the
same network. This will prevent Ethernet address conflicts.
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.
Compatibility notes for Multi Vendor Teaming
--------------------------------------------
Attempting to hot-add a non-Intel adapter to a team may cause system
instability. If you do hot-add a non-Intel adapter to a team, make sure
you restart the computer or reload the team.
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.
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.
Jumbo Frames and Jumbo Packets
==============================
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, 82572EI, and 82575EB
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
Intel Gigabit VT Quad Port Server Adapter
Microsoft Windows Server 2008 Notes
===================================
Bug checks and system instability when passing traffic with misconfigured
Jumbo Packets setting
-------------------------------------------------------------------------
If you are experiencing bug checks or system instability when passing traffic,
please check your Jumbo Packet settings. If Jumbo Packets are not configured
correctly, a mis-sized packet may be sent to the affected system. This results
in the bug checks and system instability.
Uninstall does not uninstall driver
-----------------------------------
When the drivers are uninstalled on Microsoft Windows Vista or Windows
Server 2008, the operating system immediately re-installs the in-box drivers.
This will cause a number to be appended to the device's displayed name.
Interrupt Test not supported on adapters supporting MSI-X
---------------------------------------------------------
The Interrupt Test is not supported in the diagnostics in DMIX.
FIFO Test not supported on Intel 10 Gigabit Server Adapters
-----------------------------------------------------------
The FIFO Test is not supported in the diagnostics in DMIX.
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.
Assigning Multiple IP Addresses in Windows
------------------------------------------
If you assign multiple IP addresses to a single network connection in a Windows
Server 2003 system, you must also set the Wait for Link Advanced tab parameter
to On.
Quad Port Server Adapter Notes
==============================
Hot Plug operations are not supported by Intel Quad Port Server Adapters.
Downshifting
------------
When connecting to any Gigabit switch via a faulty CAT 5 cable where
one pair is broken, the adapter does not downshift from 1 Gig to
100Mbps. For the adapter to downshift, it must identify two broken
pairs in the cable.
Installing the Base Driver on systems running Windows XP
or Windows Server 2003
--------------------------------------------------------
After inserting the adapter in the system, you must install the base
driver. This is true even if you previously installed base drivers
for other Intel Ethernet adapters.
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
============
Dropped Receive Packets on Half-duplex 10/100 Networks
------------------------------------------------------
If you have an Intel PCI Express adapter installed, running at 10 or
100 Mbps, half-duplex, with TCP Segment Offload (TSO) enabled, you may
observe occasional dropped receive packets. To work around this
problem, disable TSO, or update the network to operate in full-duplex
and/or 1 Gbps.
Lost SOL and IDER sessions
--------------------------
SOL and IDER sessions may be lost if spanning tree is enabled. Turn off
spanning tree protocol on switch ports connected to devices configured
for SOL and IDER access.
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
----------------------------------------------------------------------
The Intel PROSet install process 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.
<http://support.microsoft.com/default.aspx?scid=kb;en-us;819586>
"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.
Windows Code 10 Error Message on Driver Install or Upgrade
----------------------------------------------------------
If you encounter a Windows Code 10 error message when installing or
upgrading drivers, reboot to resolve the issue.
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.
No settings available on the Intel(R) Boot Options tab in Windows Device
Manager after flashing an EFI image
----------------------------------------------------------------------
The settings have been hidden because the EFI environment does not make
use of them.
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 Gigabit Network Adapters (copper only) do not detect active
link during load time
-----------------------------------------------------------------
Some Intel Gigabit Network 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 and PRO/1000 PF Server Adapters support WOL
but use fiber media.
Intel PRO/1000 Adapter will not have Link when forced to operate at
10 or 100 Mbps with a link partner 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.
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.
iSCSI Boot Diskless OS Install Fails
------------------------------------
An iSCSI Boot Diskless OS Install in Windows 2003 may occur because the
iSSetup.cat file could not be found.
Copy iSSetup.cat, iSSetup.inf, iSSetup.sys and txtsetup.oem files from
the Intel iSCSI Boot Media to a Floppy Disk before starting the
installation procedure.
A Windows Reboot message appears when changing settings
-------------------------------------------------------
When iSCSI Boot is installed on an Intel PCI Express network adapter but
not enabled, the reboot message posted in Windows can be disregarded when
teams or VLANs are created or when configuration changes are made to
any base driver advanced feature.
iSCSI Boot: Connecting back-to-back to a target with a Broadcom LOM
-------------------------------------------------------------------
Connecting an iSCSI boot host to a target through a Broadcom LOM may occationally
cause the connection to fail. Use a switch between the host and target to avoid
this.
Advanced Properties Settings Changes while Traffic is Running
-------------------------------------------------------------
In the Advanced Properties tab of Intel(R) PROSet, parameters should not
be modified when transmit traffic is present or a reboot may be required
to make the changes effective.
WOL Enabled on both Port A and Port B of Intel VT Quad Port NIC
---------------------------------------------------------------
If you have an Intel PCI Express VT Quad Port adapter driver installed using PnP,
you may notice WOL is enabled on both Port A and Port B. WOL is only
supported on Port A.
Customer Support
================
- Main Dell web support site: http://www.support.dell.com
Supported Adapters
==================
Copper Adapters
---------------
- Intel PRO/1000 PT Server Adapter
- Intel PRO/1000 PT Dual Port Server Adapter
- Intel Gigabit VT Quad Port Server Adapter
- Intel 10 Gigabit AT Server Adapter
Fiber Optic Adapters
--------------------
- Intel PRO/1000 PF Server Adapter
- Intel 10 Gigabit XF SR Server Adapter
Legal / Disclaimers
===================
Copyright (C) 2002-2008, 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
========================
