Intel® Ethernet Adapters and Devices

User Guide
Release 28.3
December 15, 2023

705831
Intel® Ethernet Adapters and Devices User Guide

1. Overview
Welcome to the User Guide for Intel® Ethernet Adapters and devices. This guide covers hardware and
software installation, setup procedures, and troubleshooting tips for Intel network adapters, connections,
and other devices.

1.1 Intended Audience

This document is intended for information technology professionals with a high level of knowledge,
experience, and competency in Ethernet networking technology.

1.2 Supported Operating Systems

The drivers in this release have been tested with the following operating systems (OSs). Additional OSs
may function with our drivers but are not tested.

NOTE: Not all devices support all operating systems listed. Refer to the release notes for
detailed OS support information for your device.

Microsoft* Windows Server*, Azure Stack HCI, and Windows*

l Microsoft Windows Server 2022
l Microsoft Windows Server 2019, Version 1903
l Microsoft Windows Server 2016
l Microsoft Azure Stack HCI
l Microsoft Windows 11
l Microsoft Windows 10 version 21H2 (build 19044)
l Microsoft Windows 10 RS5, Version 1809 (build 17763)
l Microsoft Windows 10 RS1, Version 1607 (build 14393)

NOTE:
l Devices based on the following do not support Microsoft Windows or Windows Server:
l Intel® Ethernet Connection E822-C
l Intel® Ethernet Connection E822-L
l Microsoft Windows 32-bit operating systems are only supported on Intel 1GbE Ethernet
Adapters.
l Some older Intel Ethernet adapters do not have full software support for the most recent
versions of Microsoft Windows. Many older Intel Ethernet adapters have base drivers
supplied by Microsoft Windows.

VMware* ESXi*
l VMWare ESXi 8.0
l VMware ESXi 7.0

Please refer to VMWare's download site for the latest ESXi drivers for Intel® Ethernet® devices.

705831 2
Intel® Ethernet Adapters and Devices User Guide

Linux*
l Linux Real Time Kernel 5.x and 4.x (only on Intel Ethernet E810 Series)
l Linux, v2.4 kernel or higher
l Red Hat* Enterprise Linux* (RHEL) 9.3
l Red Hat Enterprise Linux 8.9
l SUSE* Linux Enterprise Server (SLES) 15 SP5
l SUSE Linux Enterprise Server 12 SP5
l Canonical* Ubuntu* 22.04 LTS
l Canonical Ubuntu 20.04 LTS
l Debian* 11

FreeBSD*
l FreeBSD 14.0
l FreeBSD 13.1

Oracle* Solaris*
l Basic software and drivers are supported on Oracle Solaris. Drivers and support are provided by the
operating system vendor.

Discontinued OS Support

NOTE: See "Discontinued Support" on page 156 for information on the last release to support
particular versions of an operating system.

1.3 Supported Devices

For help identifying your network device and finding supported devices, click the link below:

http://www.intel.com/support

Compatibility Notes

NOTE: Available features and settings are dependent on your device and operating system. Not all
settings described in this user guide are available on every device/OS combination.

In addition, note the following limitations for Intel Ethernet devices and connections.

Device Family Details

Intel Ethernet 800 Series l Devices based on the Intel® Ethernet Controller E810-C have an expected
total throughput for the entire device of 100 Gb/s in each direction if one
100G cable is connected or if two 100G cables are connected.
l Devices based on the Intel® Ethernet 800 Series do not support RDMA when
operating in multiport mode with more than 4 ports.

Intel Ethernet 700 Series l Devices based on the Intel® Ethernet Controller XL710 (4x10 GbE, 1x40 GbE,
and 2x40 GbE) have an expected total throughput for the entire device of 40
Gb/s in each direction.

705831 3
Intel® Ethernet Adapters and Devices User Guide

l The first port of Intel® Ethernet 700 Series adapters will display the correct
branding string. All other ports on the same device will display a generic
branding string.
l For an Intel® Ethernet 700 Series adapter to reach its full potential, you
must install it in a PCIe Gen3 x8 slot. Installing it in a shorter slot, or a Gen2
or Gen1 slot, will limit the throughput of the adapter.
l Devices based on the Intel® Ethernet Controller X722 do not support the
following features:
l Intel® PROSet for Windows* Device Manager
l
l Intel® Advanced Network Services (Intel® ANS) teams or VLANs
(LBFO is supported)

Intel Ethernet 500 Series l Devices based on the Intel® Ethernet Connection X552 and Intel® Ethernet
Connection X553 do not support the following features:
l Energy Efficient Ethernet (EEE)
l Intel PROSet for Windows Device Manager
l Intel ANS teams or VLANs (LBFO is supported)
l Data Center Bridging (DCB)
l IPSec Offloading
l MACSec Offloading

In addition, SFP+ devices based on the Intel Ethernet Connection X552 and
Intel Ethernet Connection X553 do not support the following features:
l Speed and duplex auto-negotiation
l Wake on LAN
l 1000BASE-T SFP Modules

1.4 Related Documentation

The following files are available in the download for this software release.

Document Description Location

readme.txt Release-specific information Root folder of software download package

license.pdf Licenses pertaining to this software release Root folder of software download package

You can find additional resources, configuration guides, and technical documentation for Intel Ethernet
products on the Intel Resource & Documentation Center. Some documents may require a login.

1.4.1 Release Notes

Release notes for this software release are available on the Intel Resource & Documentation Center. Please
see the following document for details about new or removed features, supported operating systems per
device family, and known issues and limitations:
l Intel® Ethernet Controller Products Release Notes

1.4.2 User Guides for Specific Devices

Some adapters and devices have user guides with detailed configuration and setup information. You can
access public versions of these documents in the Intel Resource & Documentation Center.

705831 4
Intel® Ethernet Adapters and Devices User Guide

Refer to the following documentation for advanced configuration.

Type of Document + Link Affected Products

User guide Intel® Ethernet Network Adapter E810-XXV-4T

User guide Intel® Ethernet Network Adapter E810-C-Q2T

1.4.3 Feature Support Matrix

See the following documents for additional details on supported features, cables, media types, operating
systems, and more.

Device Family Available Documents

Intel Ethernet 800 Series Intel® Ethernet Controller E810 Feature Support Matrix

Intel Ethernet 700 Series Intel® Ethernet Controller X710/XXV710/XL710 Feature Support Matrix

Intel® Ethernet Connection X722 Feature Support Matrix

Intel® Ethernet Controller X710-TM4/AT2 and V710-AT2 Feature Support Matrix

Intel Ethernet 500 Series Intel® Ethernet Controller X550 Feature Support Matrix

1.5 Customer Support

Intel support is available on the web or by phone. Support offers the most up-to-date information about
Intel products, including installation instructions, troubleshooting tips, and general product information.

1.5.1 Web and Internet Sites

Support: http://www.intel.com/support

Corporate Site for Network Products: http://www.intel.com/products/ethernet/overview.htm

Intel Wired Networking project hosted by Sourceforge: http://sourceforge.net/projects/e1000

705831 5
Intel® Ethernet Adapters and Devices User Guide

2. Installation
This chapter covers how to install Intel Ethernet adapters, drivers, and other software.

At a high level, installation involves the following steps, which are covered in more detail later in this
chapter.

If you are installing a network adapter, follow this procedure from step 1.
If you are upgrading the driver software, start with step 5.

NOTE: If you update the firmware, you must update the driver software to the same family
version.

1. Make sure that you are installing the latest driver software for your adapter. Visit Intel's support
website to download the latest drivers.
2. Review system requirements.
3. Insert the adapter(s) in the computer.
4. Attach the copper or fiber network cable(s).
5. Install the driver.
6. For Windows systems, install the Intel® PROSet software.

If you have any problems with basic installation, see Troubleshooting.

You can now set up advanced features, if necessary. The available features and the configuration process
varies with the device and your operating system. Refer to "Device Features" on page 25 for more
information; for Linux and FreeBSD drivers, refer to the README file inside the driver tarball.

2.1 Hardware Compatibility

Before installing the adapter, check your system for the following:
l The latest BIOS for your system
l One open PCI Express slot

NOTE:
l For devices that support bifurcation, make sure PCI slot bifurcation is enabled in your
system's BIOS.
l The Intel® 10 Gigabit AT Server Adapter will only fit into x8 or larger PCI Express slots.
Some systems have physical x8 PCI Express slots that actually support lower speeds. Please
check your system manual to identify the slot.

2.2 Installing the Adapter

2.2.1 Select the Correct Slot

One open PCI-Express slot, x4, x8, or x16, depending on your adapter.

NOTE: Some systems have physical x8 PCI Express slots that actually only support lower speeds.
Please check your system manual to identify the slot.

705831 6
Intel® Ethernet Adapters and Devices User Guide

2.2.2 Insert the Adapter into the Computer

1. If your computer supports PCI Hot Plug, see your computer documentation for special installation
instructions.
2. Turn off and unplug your computer. Then remove the cover.

CAUTION: Turn off and unplug the power before removing the computer's cover. Failure
to do so could endanger you and may damage the adapter or computer.

3. Remove the cover bracket from an available slot.

4. Insert the adapter, pushing it into the slot until the adapter is firmly seated. You can install a smaller
PCI Express adapter in a larger PCI Express slot.

CAUTION: Some PCI Express adapters may have a short connector, making them
more fragile than PCI adapters. Excessive force could break the connector. Use
caution when pressing the board in the slot.

5. Secure the adapter bracket with a screw, if required.

6. Replace the computer cover and plug in the power cord.
7. Power on the computer.

2.2.3 PCI Hot Plug Support

Most Intel® Ethernet Server Adapters are enabled for use in selected servers equipped with Hot Plug
support. Exceptions: Intel Gigabit Quad Port Server adapters do not support Hot Plug operations.

If you replace an adapter in a Hot Plug slot, do not place the removed adapter back into the same network
until the server has rebooted (unless you return it to the same slot and same team as before). This
prevents a conflict in having two of the same Ethernet addresses on the same network.

The system will require a reboot if you

l Change the primary adapter designator.
l Add a new adapter to an existing team and make the new adapter the primary adapter.
l Remove the primary adapter from the system and replace it with a different type of adapter.

705831 7
Intel® Ethernet Adapters and Devices User Guide

NOTE: To replace an existing SLA-teamed adapter in a Hot Plug slot, first unplug the adapter
cable. When the adapter is replaced, reconnect the cable.

2.2.3.1 PCI Hot Plug Support for Microsoft* Windows* Operating Systems
Intel® network adapters are enabled for use in selected servers equipped with PCI Hot Plug support and
running Microsoft* Windows* operating systems. For more information on setting up and using PCI Hot
Plug support in your server, see your hardware and/or Hot Plug support documentation for details. PCI Hot
Plug only works when you hot plug an identical Intel network adapter.

NOTES:
l The MAC address and driver from the removed adapter will be used by the replacement
adapter unless you remove the adapter from the team and add it back in. If you do not
remove and restore the replacement adapter from the team, and the original adapter is
used elsewhere on your network, a MAC address conflict will occur.
l For SLA teams, ensure that the replacement NIC is a member of the team before
connecting it to the switch.

2.3 Connecting Network Cables

Connect the appropriate network cable, as described in the following sections.

2.3.1 Supported SFP+, SFP28, QSFP+, and QSFP28 Modules

Devices Based on the Intel Ethernet 800 Series and Intel Ethernet 700 Series
See "Feature Support Matrix" on page 5 for more information on supported media types for your device.

NOTES:
l Some Intel branded network adapters based on the X710/XL710 controller only support
Intel branded modules. On these adapters, other modules are not supported and will not
function.
l For connections based on the 710 series of controllers, support is dependent on your system
board. Please see your vendor for details.
l In all cases Intel recommends using Intel optics; other modules may function but are not
validated by Intel. Contact Intel for supported media types.
l In systems that do not have adequate airflow to cool the adapter and optical modules, you
must use high temperature optical modules.
l For XXV710 based SFP+ adapters, Intel recommends using Intel optics and cables. Other
modules may function but are not validated by Intel. Contact Intel for supported media
types.

705831 8
Intel® Ethernet Adapters and Devices User Guide

82599-Based Adapters

NOTES:
l If your 82599-based Intel® Network Adapter came with Intel optics, or is an Intel®
Ethernet Server Adapter X520-2, then it only supports Intel optics and/or the direct attach
cables listed below.
l 82599-Based adapters support all passive and active limiting direct attach cables that
comply with SFF-8431 v4.1 and SFF-8472 v10.4 specifications.

Supplier Type Part Numbers

SR Modules

Intel DUAL RATE 1G/10G SFP+ SR (bailed) AFBR-703SDZ-IN2

Intel DUAL RATE 1G/10G SFP+ SR (bailed) FTLX8571D3BCV-IT

Intel DUAL RATE 1G/10G SFP+ SR (bailed) AFBR-703SDDZ-IN1

LR Modules

Intel DUAL RATE 1G/10G SFP+ LR (bailed) FTLX1471D3BCV-IT

Intel DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDZ-IN2

Intel DUAL RATE 1G/10G SFP+ LR (bailed) AFCT-701SDDZ-IN1

QSFP Modules

Intel TRIPLE RATE 1G/10G/40G QSFP+ SR (bailed) (40G not supported on 82599) E40GQSFPSR

The following is a list of 3rd party SFP+ modules that have received some testing. Not all modules are
applicable to all devices.

Supplier Type Part Numbers

Finisar SFP+ SR bailed, 10G single rate FTLX8571D3BCL

Avago SFP+ SR bailed, 10G single rate AFBR-700SDZ

Finisar SFP+ LR bailed, 10G single rate FTLX1471D3BCL

Finisar DUAL RATE 1G/10G SFP+ SR (No Bail) FTLX8571D3QCV-IT

Avago DUAL RATE 1G/10G SFP+ SR (No Bail) AFBR-703SDZ-IN1

Finisar DUAL RATE 1G/10G SFP+ LR (No Bail) FTLX1471D3QCV-IT

705831 9
Intel® Ethernet Adapters and Devices User Guide

Avago DUAL RATE 1G/10G SFP+ LR (No Bail) AFCT-701SDZ-IN1

Finisar 1000BASE-T SFP FCLF8522P2BTL

Avago 1000BASE-T SFP ABCU-5710RZ

HP 1000BASE-SX SFP 453153-001

82598-Based Adapters

NOTES:

l Intel® Network Adapters that support removable optical modules only support their original
module type (i.e., the Intel® 10 Gigabit SR Dual Port Express Module only supports SR
optical modules). If you plug in a different type of module, the driver will not load.
l 82598-Based adapters support all passive direct attach cables that comply with SFF-8431
v4.1 and SFF-8472 v10.4 specifications. Active direct attach cables are not supported.
l Hot Swapping/hot plugging optical modules is not supported.
l Only single speed, 10 Gigabit modules are supported.
l LAN on Motherboard (LOMs) may support DA, SR, or LR modules. Other module types are
not supported. Please see your system documentation for details.

The following is a list of SFP+ modules and direct attach cables that have received some testing. Not all
modules are applicable to all devices.

Supplier Type Part Numbers

Finisar SFP+ SR bailed, 10G single rate FTLX8571D3BCL

Avago SFP+ SR bailed, 10G single rate AFBR-700SDZ

Finisar SFP+ LR bailed, 10G single rate FTLX1471D3BCL

Molex 1m - Twin-ax cable 74752-1101

Molex 3m - Twin-ax cable 74752-2301

Molex 5m - Twin-ax cable 74752-3501

Molex 10m - Twin-ax cable 74752-9004

Tyco 1m - Twin-ax cable 2032237-2

705831 10
Intel® Ethernet Adapters and Devices User Guide

Tyco 3m - Twin-ax cable 2032237-4

Tyco 5m - Twin-ax cable 2032237-6

Tyco 10m - Twin-ax cable 1-2032237-1

THIRD PARTY OPTIC MODULES AND CABLES REFERRED TO ABOVE ARE LISTED ONLY FOR THE PURPOSE OF HIGHLIGHTING THIRD
PARTY SPECIFICATIONS AND POTENTIAL COMPATIBILITY, AND ARE NOT RECOMMENDATIONS OR ENDORSEMENT OR SPONSORSHIP OF
ANY THIRD PARTY'S PRODUCT BY INTEL. INTEL IS NOT ENDORSING OR PROMOTING PRODUCTS MADE BY ANY THIRD PARTY AND THE
THIRD PARTY REFERENCE IS PROVIDED ONLY TO SHARE INFORMATION REGARDING CERTAIN OPTIC MODULES AND CABLES WITH THE
ABOVE SPECIFICATIONS. THERE MAY BE OTHER MANUFACTURERS OR SUPPLIERS, PRODUCING OR SUPPLYING OPTIC MODULES AND
CABLES WITH SIMILAR OR MATCHING DESCRIPTIONS. CUSTOMERS MUST USE THEIR OWN DISCRETION AND DILIGENCE TO PURCHASE
OPTIC MODULES AND CABLES FROM ANY THIRD PARTY OF THEIR CHOICE. CUSTOMERS ARE SOLELY RESPONSIBLE FOR ASSESSING
THE SUITABILITY OF THE PRODUCT AND/OR DEVICES AND FOR THE SELECTION OF THE VENDOR FOR PURCHASING ANY PRODUCT. THE
OPTIC MODULES AND CABLES REFERRED TO ABOVE ARE NOT WARRANTED OR SUPPORTED BY INTEL. INTEL ASSUMES NO LIABILITY
WHATSOEVER, AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF SUCH THIRD PARTY
PRODUCTS OR SELECTION OF VENDOR BY CUSTOMERS.

2.3.2 Connect the Direct Attach Cable

Insert the Direct Attach network cable as shown below.

The following table shows the types of direct attached cabling you can use.

Max Cable
Speed Cable Type Length Notes

100 Gbps QSFP28 Direct Attach Cable 5 meters

40 Gbps SFP+ Direct Attached Cable (Twinaxial) 7 meters

25 Gbps SFP28 Direct Attached Cable (Twinaxial) 5 meters For optimal performance, must use CA-
25G-L with RS-FEC and 25GBASE-C.

10 Gbps SFP+ Direct Attached Cable (Twinaxial) 7 meters

705831 11
Intel® Ethernet Adapters and Devices User Guide

2.3.3 Connect the RJ-45 Network Cable

Connect the RJ-45 network cable as shown:

The following table shows the maximum lengths for each cable type at a given transmission speed.

Speed Category 5 Category 6 Category 6a Category 7

1 Gbps 100m 100m 100m 100m

10 Gbps NA 55m 100m 100m

25 Gbps NA NA NA 50m

40 Gbps NA NA NA 50m

CAUTION: If using less than 4-pair cabling, you must manually configure the speed
and duplex setting of the adapter and the link partner. In addition, with 2- and 3-
pair cabling the adapter can only achieve speeds of up to 100Mbps.

NOTE: For the Intel® 10 Gigabit AT Server Adapter, to ensure compliance with CISPR 24 and the
EU’s EN55024, this product should be used only with Category 6a shielded cables that are properly
terminated according to the recommendations in EN50174-2.

In all cases:
l The adapter must be connected to a compatible link partner, preferably set to auto-negotiate speed
and duplex for Intel gigabit adapters.
l Intel Gigabit and 10 Gigabit Server Adapters using copper connections automatically accommodate
either MDI or MDI-X connections. The auto-MDI-X feature of Intel gigabit copper adapters allows
you to directly connect two adapters without using a cross-over cable.

705831 12
Intel® Ethernet Adapters and Devices User Guide

2.3.4 Connect the Fiber Optic Network Cable

CAUTION: The fiber optic ports contain a Class 1 laser device. When the ports are disconnected, always
cover them with the provided plug. If an abnormal fault occurs, skin or eye damage may result if in close
proximity to the exposed ports.

Remove and save the fiber optic connector cover. Insert a fiber optic cable into the ports on the network
adapter bracket as shown below.

Most connectors and ports are keyed for proper orientation. If the cable you are using is not keyed, check
to be sure the connector is oriented properly (transmit port connected to receive port on the link partner,
and vice versa).

The adapter must be connected to a compatible link partner operating at the same laser wavelength as the
adapter.

Conversion cables to other connector types (such as SC-to-LC) may be used if the cabling matches the
optical specifications of the adapter, including length limitations.

Insert the fiber optic cable as shown below.

The following table shows the connection requirements for fiber optic cables.

Connector Max Cable

Device Laser Wavelength Type Cable Type Length

Intel Ethernet LR Server 1310 nanometer (not LC Single-mode fiber with 9.0µm 10 kilometers
Adapters visible) core diameter

Intel Ethernet 10 Gigabit SR 850 nanometer (not LC or SC Multi-mode fiber with 62.5µm 33 meters
Server Adapters visible) core diameter

Multi-mode fiber with 50µm core 300 meters

diameter

Intel Ethernet Gigabit SR Server 850 nanometer (not LC or SC Multi-mode fiber with 62.5µm 275 meters
Adapters visible) core diameter

Multi-mode fiber with 50µm core 550 meters

diameter

705831 13
Intel® Ethernet Adapters and Devices User Guide

2.4 Install Drivers and Software

2.4.1 On Windows Operating Systems

There are two ways to install device drivers and software on Microsoft Windows:
l Download and install the complete driver pack. This option will install Windows drivers and
Intel® PROSet but is a very large download.
l Download and install only Windows drivers and Intel PROSet tools. This option will
require you to download and install two separate packages but is a much smaller download.

You must have administrative rights to the operating system to install the drivers and software.

Refer to the following for more detailed information:

l "About Intel PROSet®" on page 15
l "Microsoft* Windows* Driver and Software Installation and Configuration" on page 84

2.4.2 On Linux

2.4.2.1 Installing Linux Drivers from Source Code

1. Download and expand the driver tar file.
2. Compile the driver module.
3. Install the module using the modprobe command.
4. Assign an IP address using the ifconfig command.

2.4.2.2 Installing Linux Drivers from RPMs

1. Download and expand the driver tar file.
2. Install the driver using the rpm command or another software management tool appropriate for
your distribution.

705831 14
Intel® Ethernet Adapters and Devices User Guide

3. About Intel PROSet®

Intel PROSet is a suite of software tools to configure Intel Ethernet devices on Microsoft Windows operating
systems. Intel PROSet software includes the following:

Component Description

Intel® PROSet for Windows* Device An extension to the Windows Device Manager. When you install Intel PROSet for
Manager Windows Device Manager, additional tabs are automatically added to Device Man-
ager.

Intel® PROSet Adapter Configuration A graphical user interface that allows you to configure and manage supported Intel
Utility (Intel® PROSet ACU) Ethernet adapters.

Intel® PROSet for Windows Power- Software that contains several cmdlets that allow you to configure and manage the
Shell* software Intel Ethernet adapters and devices present in your system.

For more information on installing or using Intel PROSet, refer to the following:
l "Compatibility Notes for Intel Ethernet Cmdlets and Intel PROSet" below
l "Installing Intel PROSet" on page 17
l "Configuring Device Features in Microsoft Windows" on page 20

NOTES:
l You must have administrator rights to install or use Intel PROSet.
l Intel PROSet requires the latest driver and software package for your Intel Ethernet
devices.

3.1 About Intel® Ethernet Cmdlets

In addition to Intel PROSet, Intel provides Ethernet cmdlets for Windows PowerShell to:
l Display information about Intel Ethernet devices in the system
l Configure device settings
l Configure and gather firmware logs for debugging supported devices
l Blink the LED on the specified port of an Intel Ethernet device for a defined number of seconds

These Ethernet cmdlets do not require Intel PROSet to be installed on the system. For more information on
installing or using Intel Ethernet cmdlets, refer to the following:
l "Compatibility Notes for Intel Ethernet Cmdlets and Intel PROSet" below
l "Installing Intel Ethernet Cmdlets" on page 17
l "Configuring with Windows PowerShell" on page 21
l "Firmware Logging" on page 104

3.2 Compatibility Notes for Intel Ethernet Cmdlets and Intel PROSet
Note the following compatibility requirements for Intel Ethernet cmdlets and Intel PROSet. For Intel
PROSet, the installer will automatically detect and install the components compatible with your operating
system.

705831 15
Intel® Ethernet Adapters and Devices User Guide

3.2.1 Device Compatibility

The following devices either do not support Intel Ethernet cmdlets, Intel PROSet, or some of its
components.

Ethernet
Cmdlets Intel PROSet

PowerShell
Device No Support No Support1 Only2

Any platform with a System on a Chip (SoC) processor Varies X3

Intel® Ethernet Connection E822 X4 X4

Intel® Ethernet 500 Series and lower X

Intel® 82567V-3 Gigabit Network Connection X X

Notes:

1. No support for Intel PROSet or any of its components.

2. Supports only Intel PROSet for Windows PowerShell software. Does not support Intel PROSet ACU or Intel PROSet for
Windows Device Manager.
3. This includes a platform with either a server controller (designated by an initial E or X, such as X552 or X722) or
both a server and client controller (designated by an initial I, such as I218).
4. This device or family does not support any Microsoft operating systems. As a result, it also does not support Intel
Ethernet cmdlets and/or Intel PROSet.

NOTE: On recent operating systems, older hardware may not support Intel PROSet. In this case,
the Intel PROSet tabs may not be displayed in the Windows Device Manager user interface, and the
Windows PowerShell cmdlets may display an error message stating that the device does not have
an Intel driver installed.

3.2.2 Operating System Compatibility

The following table lists compatible operating systems for Intel Ethernet cmdlets, Intel PROSet, or its
components. Not all OS versions listed in the following table are supported in the newest
releases of Intel Ethernet software; refer to "Supported Operating Systems" on page 2 for currently
supported versions.

NOTE: Intel PROSet is not supported on Microsoft Windows 11. Microsoft Windows 10 is the last
Windows operating system that supports Intel PROSet.

705831 16
Intel® Ethernet Adapters and Devices User Guide

Component Operating System Compatibility

Intel Ethernet cmdlets Microsoft Windows Server 2016 and later

Microsoft Azure Stack HCI

Microsoft Windows PowerShell version 5.1 and later

Intel PROSet for Windows PowerShell software Any supported version of Microsoft Windows Server

Any supported version of Microsoft Windows

Microsoft Azure Stack HCI

Intel PROSet Adapter Configuration Utility Microsoft Windows Server 2019 and later

Microsoft Windows 10 Version 1809, and later versions of Microsoft

Windows 10

Intel PROSet for Windows Device Manager Microsoft Windows Server 2016, and earlier versions

Microsoft Windows 10 Version 1709, and earlier versions

3.3 Installing Intel Ethernet Cmdlets

NOTE: We strongly recommend you install the latest base driver and NVM before installing Intel
Ethernet cmdlets, or functionality could be reduced.

To install Intel Ethernet cmdlets:

1. Download the zip file with the adapter cmdlets from the Intel Download Center.
2. Save the zip file to the system you're trying to configure or debug.
3. Extract files from the zip file.
4. In the extracted files, double-click on the .exe file. The cmdlets will automatically install to the
current user's PowerShell module directory (for example, to
C:\Users\Administrator\Documents\WindowsPowerShell\Modules\IntelEthernetCmdlets).

After installation, you can run the cmdlets at the PowerShell prompt without manually importing the
module.

Refer to the following for more information:

l The readme.txt file included in the download
l The cmdlet help in PowerShell
l In this user guide:
l "Configuring with Windows PowerShell" on page 21
l "Firmware Logging" on page 104

3.4 Installing Intel PROSet

NOTES:
l Intel PROSet is not installed by default when you install only the device drivers. You must
install device drivers before installing Intel PROSet.
l You must have administrator rights to install or use Intel PROSet.

705831 17
Intel® Ethernet Adapters and Devices User Guide

l You must install Intel PROSet if you want to use Intel® Advanced Network Services (Intel®
ANS) or VLANs. Intel ANS teams and VLANs are not supported on all operating systems or
devices. Refer to "Adapter Teaming" on page 25 and "Virtual LANs" on page 80 for more
information.
l Intel PROSet requires the latest driver and software package for your Intel Ethernet devices.

To download and install only Intel PROSet:

1. After the driver installation has finished, download and extract the Wired_PROSet_XX.X_*.zip
file for your version of Windows, where XX.X is the release number. This file will install Intel PROSet
on your system.
l If you are running a 32-bit operating system, download Wired_PROSet_XX.X_32.zip.
l If you are running a 64-bit operating system, download Wired_PROSet_XX.X_x64.zip.
2. In the extracted files, double-click on the .exe file to launch the installation of Intel PROSet.
3. In the install wizard that opens, follow the onscreen prompts to select the features you want to
install.
4. The Intel PROSet software will install. Click Finish when prompted.

NOTE: You can also run DxSetup.exe from the files downloaded from Customer Support. Refer to
"Command Line Installation for Intel PROSet" below for details.

If Intel PROSet was installed without Intel ANS support, you can install support by running DxSetup.exe,
and then selecting the Modify option when prompted. From the Setup Options window, select Intel®
Advanced Network Services then click Next to continue with the installation wizard.

3.4.1 Command Line Installation for Intel PROSet

The install utility DxSetup.exe allows unattended installation of Intel PROSet from a command line.

NOTES:
l Intel PROSet cannot be installed with msiexec.exe. You must use DxSetup.exe.
l If the operating system and installed adapters do not support a given feature, that feature
will not be installed even if the command line option specifies it for installation.

DxSetup.exe Command Line Options

By setting the parameters in the command line, you can enable and disable management applications. If
software is already installed and parameters are not specified, only existing components are updated.

You can also use DxSetup.exe to modify or upgrade software. If a feature is already installed, the public
property for that feature will default to 1 and if a feature is not installed, the public property for that feature
will default to 0. Running DxSetup.exe without specifying properties will upgrade all installed software. You
can remove installed software (except for base drivers) by setting the property to 0. If you uninstall Intel
PROSet (PROSET=0), all features that rely on Intel PROSet will also be removed.

DxSetup.exe supports the following command line parameters for fresh installations, modifying an
installation, or upgrading the software:

705831 18
Intel® Ethernet Adapters and Devices User Guide

Parameter Definition

PROSET Intel PROSet for Windows Device Manager or Intel PROSet ACU depending on operating system.

"0", do not install Intel PROSet. If Intel PROSet is already installed, it will be uninstalled.

"1", install Intel PROSet feature.

NOTE: If PROSET=0, Intel ANS will not be installed. If PROSET=0 and Intel PROSet and Intel
ANS are already installed, Intel PROSet and Intel ANS will be uninstalled.

ANS Intel Advanced Network Services

"0", do not install Intel ANS. If Intel ANS is already installed, it will be uninstalled.

"1", install Intel ANS. The ANS parameter requires PROSET=1.

NOTE: If the ANS parameter is set to ANS=1, both Intel PROSet and Intel ANS will be
installed.

ISCSI iSCSI

"0", do not install iSCSI. If iSCSI is already installed, it will be uninstalled.

"1", install iSCSI. The iSCSI parameter requires PROSET=1.

PROSet_ACU_ If Intel PROSet ACU is installed, create or update the "Intel® PROSet Adapter Configuration Utility"
Shortcut desktop shortcut.

"0", do not create or update the "Intel® PROSet Adapter Configuration Utility" desktop shortcut.

"1", create or update the "Intel® PROSet Adapter Configuration Utility" desktop shortcut.

If this parameter is not specified, the shortcut will only be created or updated if it was created by a
previous software installation.

RDMA_ROUTING RDMA routing

"0", do not install RDMA routing.

"1", install RDMA routing.

IWARP_FIREWALL Installs the iWARP firewall rule.

"0", do not install iWARP firewall rule.

"1", install iWARP firewall rule. If "1" is selected, the following parameters are allowed in addition to
IWARP_FIREWALL.
l IWARP_FIREWALL_DOMAIN [0|1] - Applies firewall rule to corporate domains.
l IWARP_FIREWALL_PUBLIC [0|1] - Applies firewall rule to public networks
l IWARP_FIREWALL_PRIVATE [0|1] - Applies firewall rule to private networks

FORCE "0", check that the installed device supports a feature (for example, iSCSI) and only install the feature
if such a device is found.

"1", install the specified features regardless of the presence of supporting devices.

/q[r|n] /q --- silent install options

r Reduced GUI Install (only displays critical warning messages)

705831 19
Intel® Ethernet Adapters and Devices User Guide

Parameter Definition

n Silent install

/l[i|w|e|a] /l --- log file option for PROSet installation. Following are log switches:

i log status messages.

w log non-fatal warnings.

e log error messages.

a log the start of all actions.

/l* Use the log file ability of SetupBD.exe. If you do not specify the path and filename, DxSetup.exe
<path\filename> creates a log file (named SetupBD_<timestamp>.log, for example SetupBD_18-04-2022_14-29-
20.log) in the same directory as the DxSetup/MSI log.

/uninstall Uninstall Intel PROSet.

/x

NOTES:
l You must include a space between parameters.
l If you specify a path for the log file, the path must exist. If you do not specify a complete
path, the install log will be created in the current directory.
l You do not need to specify default values. To install Intel ANS and Intel PROSet, the
following examples are equivalent:
DxSetup.exe
DxSetup.exe PROSET=1 ANS=1
l The ANS parameter should only be set to ANS=1 if PROSET=1 is set.
l Even if ISCSI=1 is passed, iSCSI using DCB will not be installed if the operating system and
installed adapters do not support it. If FORCE=1 is also passed, iSCSI will be installed if the
operating system supports it.
l Public properties are not case sensitive. No white space is allowed between characters. For
example:
DxSetup.exe /qn PROSET=1

Any white space in "PROSET=1" makes the setting invalid.

3.5 Configuring Device Features in Microsoft Windows

This section describes how to use Intel Ethernet cmdlets or Intel PROSet to configure device features on
supported Windows operating systems.

For an overview or installation information, refer to the following:

705831 20
Intel® Ethernet Adapters and Devices User Guide

l "About Intel PROSet®" on page 15

l "About Intel® Ethernet Cmdlets" on page 15
l "Compatibility Notes for Intel Ethernet Cmdlets and Intel PROSet" on page 15
l "Installing Intel PROSet" on page 17

3.5.1 Configuring with Windows PowerShell

You can configure and manage the Intel Ethernet devices present in your system using the following:
l Intel Ethernet cmdlets
l Intel PROSet for Windows PowerShell software

NOTES: Refer to "Compatibility Notes for Intel Ethernet Cmdlets and Intel PROSet" on page 15 for
information on support limitations.

Module Names
The following table lists the module name in Windows PowerShell for each component.

Component Module Name Additional Information

Intel Ethernet cmdlets IntelEthernetCmdlets "Installing Intel Ethernet Cmdlets" on page 17

"Firmware Logging" on page 104

Intel PROSet for Windows PowerShell software IntelNetCmdlets "Installing Intel PROSet" on page 17

Importing New Cmdlets

After installing Intel PROSet, use the Import-Module cmdlet to import the new cmdlets. You may need to
restart Windows PowerShell to access the newly installed cmdlets. Refer to "Module Names" above for the
available cmdlet modules.

To use the Import-Module cmdlet, you must specify the path. For example:
PS c:\> Import-Module -Name "C:\Program Files\Intel\Wired Networking\IntelNetCmdlets"

NOTE:
l If you include a trailing backslash ("\") at the end of the Import-Module command, the
import operation will fail. In Microsoft Windows 10 and Windows Server 2016, the auto-
complete function appends a trailing backslash. If you use auto-complete when entering the
Import-Module command, delete the trailing backslash from the path before pressing
Return to execute the command.
l If you encounter issues with Intel Ethernet cmdlets, you may need to manually import the
module using the instructions provided above.

See Microsoft TechNet for more information about the Import-Module cmdlet.

Changing Intel Ethernet Settings via Microsoft Windows PowerShell

You can use Windows PowerShell software to change most Intel Ethernet settings.

To configure Intel Ethernet device features using Windows PowerShell software, follow these general
steps:

705831 21
Intel® Ethernet Adapters and Devices User Guide

1. Install Intel PROSet or Intel Ethernet cmdlets, if you haven’t already. See the following for more
information:
l "Installing Intel Ethernet Cmdlets" on page 17
l "Installing Intel PROSet" on page 17
2. Open PowerShell.
3. At the PowerShell prompt, run your desired cmdlet.

Help Information for PowerShell Cmdlets

To get help information for both Intel Ethernet cmdlets and Intel PROSet for Windows PowerShell
software:
l For a complete list of the cmdlets and their descriptions, type the following at the Windows
PowerShell prompt. Refer to "Module Names" on the previous page for the available cmdlet
modules.

PS C:\> get-help <module name>

l For detailed usage information for each cmdlet (including examples), type the following at the
Windows PowerShell prompt:

PS C:\> get-help <cmdlet_name> -full

l To show only examples for a cmdlet, type the following at the Windows PowerShell prompt:

PS C:\> get-help <cmdlet_name> -examples

l To use the Minihelp property for any cmdlet in the module, append | Select Minihelp. For
example:

PS C:\> Get-IntelNetAdapterSetting -Name "<adapter_name>" -

RegistryKeyword *RSS | Select Minihelp

NOTE: Online help (get-help -online) is not supported.

Additional Notes for Intel PROSet for Windows PowerShell Software

l IntelNetCmdlets are digitally signed. Microsoft Windows operating systems check digital signatures
online. Depending on your internet connection, this may result in a delay before any cmdlet
operation (including get-help). If you have not already done so, make sure you use Import-Module
to import the IntelNetCmdlets.
l If an adapter is bound to an Intel ANS team, do not change settings using the Set–
NetAdapterAdvanceProperty cmdlet from Windows PowerShell, or any other cmdlet not provided by
Intel. Doing so may cause the team to stop using that adapter to pass traffic. You may see this as
reduced performance or the adapter being disabled in the Intel ANS team. You can resolve this issue
by changing the setting back to its previous state, or by removing the adapter from the Intel ANS
team and then adding it back.
l The Get-IntelNetAdapterStatus -Status General cmdlet may report the status "Link Up - This device
is not linked at its maximum capable speed". In that case, if your device is set to auto-negotiate,
you can adjust the speed of the device's link partner to the device's maximum speed. If the device is
not set to auto-negotiate, you can adjust the device's speed manually, but you must ensure the link
partner is set at the same speed.

705831 22
Intel® Ethernet Adapters and Devices User Guide

3.5.2 Configuring with Intel PROSet Adapter Configuration Utility

The Intel PROSet Adapter Configuration Utility (Intel PROSet ACU) is a graphical user interface that allows
you to configure and manage supported Intel Ethernet Adapters.

NOTE: Refer to "Compatibility Notes for Intel Ethernet Cmdlets and Intel PROSet" on page 15 for
information on support limitations.

To configure Intel Ethernet device features using Intel PROSet ACU, follow these general steps:

1. Select an adapter in the Adapter Selection panel.

2. Select a setting to configure from the Adapter Settings panel.
3. Select or enter the desired value(s) for the selected setting.
4. Click the "Apply Changes" button.

3.5.3 Configuring with Intel PROSet for Windows Device Manager

NOTE: Refer to "Compatibility Notes for Intel Ethernet Cmdlets and Intel PROSet" on page 15 for
information on support limitations.

To configure Intel Ethernet adapter features using Intel PROSet for Windows Device Manager:

1. Open Device Manager in Windows.

2. Configure your desired settings in the appropriate tab in Device Manager.

Intel PROSet for Windows Device Manager uses the following additional Windows Device Manager tabs:

Tab Name Description

Link Speed Allows you to change the adapter's speed and duplex setting, run diagnostics, and use the
identify adapter feature.

Advanced Allows you to customize how the adapter handles QoS packet tagging, Jumbo Packets, Off-
loading, and other capabilities. Some of the features might not be available depending on the
operating system you are running, the specific adapters installed, and the specific platform
you are using.

VLANs Allows you to create, modify, and delete VLANs. You must install Intel Advanced Network Ser-
vices in order to see this tab and use the feature.

Teaming Allows you to create, modify, and delete adapter teams. You must install Intel Advanced Net-
work Services in order to see this tab and use the feature.

Power Management Replaces the standard Microsoft Windows Power Management tab in Device Manager. The
standard Windows power management functionality is included on the Intel PROSet tab.

NOTE:
l The options available on the Power Management tab are adapter and system
dependent. Not all adapters will display all options. There may be BIOS or operating
system settings that need to be enabled for your system to wake up. In particular,
this is true for Wake from S5 (also referred to as Wake from power off).
l The Intel® 10 Gigabit Network Adapters do not support power management.
l If your system has a Manageability Engine, the Link LED may stay lit even if WoL is
disabled.

705831 23
Intel® Ethernet Adapters and Devices User Guide

3.5.4 Changing Intel Ethernet Settings Under Windows Server Core

You can use the Intel PROSet for Windows PowerShell software or Intel Ethernet cmdlets to change most
Intel Ethernet settings under Windows Server Core. Please refer to their cmdlet help in PowerShell for
more information.

For iSCSI Crash Dump configuration, use the Intel PROSet for Windows PowerShell software and refer to
the aboutIntelNetCmdlets.help.txt help file. iSCSI Crash Dump configuration is not supported in Intel
Ethernet cmdlets.

705831 24
Intel® Ethernet Adapters and Devices User Guide

4. Device Features
This chapter describes the features available on Intel Ethernet devices. Major features are organized
alphabetically.

NOTE:
l Available settings are dependent on your device and operating system. Not all settings are
available on every device/OS combination.
l Some features in this section refer to Intel PROSet, Intel PROSet for Windows Device
Manager, Intel PROSet Adapter Configuration Utility (Intel PROSet ACU), or Intel PROSet for
Windows PowerShell* software. Refer to "About Intel PROSet®" on page 15 for more
information.

4.1 Adapter Teaming

Intel® Advanced Network Services (Intel® ANS) Teaming lets you take advantage of multiple
adapters in a system by grouping them together. Intel ANS teaming can use features like fault tolerance
and load balancing to increase throughput and reliability.

Before creating a team or adding team members, make sure each team member has been configured
similarly. Settings to check include VLANs and QoS Packet Tagging, Jumbo Packets, and the various
offloads. Pay particular attention when using different adapter models or adapter versions, as adapter
capabilities vary.

Refer to the following subsections for more information on adapter teaming:

l "Configuration and Compatibility Notes" below
l "Configuring Teams with Intel PROSet" on page 28
l "Teaming Modes" on page 31

For more information on VLANs, refer to "Virtual LANs" on page 80.

4.1.1 Configuration and Compatibility Notes

l Microsoft Windows 10 is the last Windows operating system version that supports Intel ANS. Intel
ANS is not supported on Microsoft Windows 11 and later.
l Intel ANS is not supported on Microsoft Windows Server 2016 and later.
l To configure teams in Linux, use Channel Bonding, available in supported Linux kernels. For more
information see the channel bonding documentation within the kernel source.
l Not all team types are available on all operating systems.
l Be sure to use the latest available drivers on all adapters.
l Not all Intel devices support Intel ANS. Intel adapters that do not support Intel ANS may still be
included in a team. However, they are restricted in the same way non-Intel adapters are. See
"Multi-Vendor Teaming" on page 37 for more information.
l You cannot create a team that includes both Intel X710/XL710-based devices and Intel® I350-
based devices. These devices are incompatible together in a team and will be blocked during team
setup.

705831 25
Intel® Ethernet Adapters and Devices User Guide

l NDIS 6.2 introduced new RSS data structures and interfaces. Because of this, you cannot enable
RSS on teams that contain a mix of adapters that support NDIS 6.2 RSS and adapters that do not.
l If a team is bound to a Hyper-V virtual NIC, you cannot change the Primary or Secondary adapter.
l To assure a common feature set, some advanced features, including hardware offloading, are
automatically disabled when an adapter that does not support the feature is added to a team.
l Hot Plug operations in a Multi-Vendor Team may cause system instability. We recommended that
you restart the system or reload the team after performing Hot Plug operations with a Multi-Vendor
Team. 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.
l Spanning tree protocol (STP) should be disabled on switch ports connected to teamed adapters in
order to prevent data loss when the primary adapter is returned to service (failback). Alternatively,
an activation delay may be configured on the adapters to prevent data loss when spanning tree is
used.
l Data Center Bridging will be automatically disabled when an adapter is added to a team with non-
DCB capable adapters.
l NLB will not work when Receive Load Balancing (RLB) is enabled. This occurs because NLB and iANS
both attempt to set the server's multicast MAC address, resulting in an ARP table mismatch.
l Teaming with the Intel® 10 Gigabit AF DA Dual Port Server Adapter is only supported with similar
adapter types and models or with switches using a Direct Attach connection.
l If you want to set up VLANs on a team, you must first create the team.
l After adding a VLAN to the team, the Network Connections window shows the team as disabled or
network cable unplugged. 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.

4.1.1.1 Teaming and VLAN Considerations When Replacing Adapters

After installing an adapter in a specific slot, Windows treats any other adapter of the same type as a new
adapter. Also, if you remove the installed adapter and insert it into a different slot, Windows recognizes it as
a new adapter. Make sure that you follow the instructions below carefully.

1. If the adapter is part of a team remove the adapter from the team.
2. Shut down the system and unplug the power cable.
3. Disconnect the network cable from the adapter.
4. Open the case and remove the adapter.
5. Insert the replacement adapter. (Use the same slot, otherwise Windows assumes that there is a
new adapter.)
6. Reconnect the network cable.
7. Close the case, reattach the power cable, and power-up the server.

4.1.1.2 Microsoft Load Balancing and Failover (LBFO) Teams

Intel ANS teaming and VLANs are not compatible with Microsoft's LBFO teams. Intel PROSet will block a
member of an LBFO team from being added to an Intel ANS team or VLAN. You should not add a port that
is already part of an Intel ANS team or VLAN to an LBFO team, as this may cause system instability. If you
use an Intel ANS team member or VLAN in an LBFO team, perform the following procedure to restore your
configuration:

705831 26
Intel® Ethernet Adapters and Devices User Guide

1. Reboot the machine

2. Remove LBFO team. Even though LBFO team creation failed, after a reboot Server Manager will
report that LBFO is Enabled, and the LBFO interface is present in the 'NIC Teaming' GUI.
3. Remove the Intel ANS teams and VLANs involved in the LBFO team and recreate them. This is an
optional (all bindings are restored when the LBFO team is removed ), but strongly recommended
step

NOTES:
l If you add an Intel AMT enabled port to an LBFO team, do not set the port to Standby in the
LBFO team. If you set the port to Standby you may lose AMT functionality.
l DCB is incompatible with Microsoft Server LBFO Teams. Do not create an LBFO team when
DCB is installed. Do not install DCB if you use LBFO teaming. Install failures and persistent
link loss may occur if DCB and LBFO are used on the same port.

4.1.1.3 Supported Adapters

Teaming options are supported on Intel server adapters. Selected adapters from other manufacturers are
also supported. If you are using a Windows-based computer, adapters that appear in Intel PROSet may be
included in a team.

NOTE: In order to use adapter teaming, you must have at least one Intel server adapter in your
system. Furthermore, all adapters must be linked to the same switch or hub.

Conditions that may prevent you from teaming a device

During team creation or modification, the list of available team types or list of available devices may not
include all team types or devices. This may be caused by any of several conditions, including:
l The device does not support the desired team type or does not support teaming at all.
l The operating system does not support the desired team type.
l The devices you want to team together use different driver versions.
l TOE (TCP Offload Engine) enabled devices cannot be added to an Intel ANS team and will not appear
in the list of available adapters.
l You can add Intel® Active Management Technology (Intel® AMT) enabled devices to Adapter Fault
Tolerance (AFT), Switch Fault Tolerance (SFT), and Adaptive Load Balancing (ALB) teams. All other
team types are not supported. The Intel AMT enabled device must be designated as the primary
adapter for the team.
l The device's MAC address is overridden by the Locally Administered Address advanced setting.
l The device has "OS Controlled" or "Enabled" selected on the Data Center tab.
l The device has a virtual NIC bound to it.
l The device is part of a Microsoft Load Balancing and Failover (LBFO) team.

4.1.1.4 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 the Device Manager first, a phantom team or phantom VLAN will appear in Device Manager.

705831 27
Intel® Ethernet Adapters and Devices User Guide

Preventing the Creation of Phantom Devices

Make sure you perform these steps before physically removing an adapter from the system:

1. Remove the adapter from any teams using the Settings tab on the team properties dialog box.
2. Remove any VLANs from the adapter using the VLANs tab on the adapter properties dialog box.
3. Uninstall the adapter from Device Manager.

You do not need to follow these steps in hot-replace scenarios.

4.1.2 Configuring Teams with Intel PROSet

This section describes how to configure Intel ANS teams using Intel PROSet. Refer to the following
subsections for more specific information:
l "Configuring Teams with Intel PROSet for Windows Device Manager" below
l "Configuring Teams with Windows PowerShell" on the next page
l "Configuring Teams with Intel PROSet ACU" on page 30

4.1.2.1 Configuring Teams with Intel PROSet for Windows Device Manager

Creating a Team
1. Launch Windows Device Manager
2. Expand Network Adapters.
3. Double-click on one of the adapters that will be a member of the team.
The adapter properties dialog box appears.
4. Click the Teaming tab.
5. Click Team with other adapters.
6. Click New Team.
7. Type a name for the team, then click Next.
8. Click the checkbox of any adapter you want to include in the team, then click Next.
9. Select a teaming mode, then click Next.
10. Click Finish.

The Team Properties window appears, showing team properties and settings.

Once a team has been created, it appears in the Network Adapters category in the Computer Management
window as a virtual adapter. The team name also precedes the adapter name of any adapter that is a
member of the team.

Changing Which Adapters Are In a Team

1. Launch Windows Device Manager.
2. Open the Team Properties dialog box by double-clicking on a team listing in the Computer
Management window.
3. Click the Settings tab.
4. Click Modify Team, then click the Adapters tab.

705831 28
Intel® Ethernet Adapters and Devices User Guide

5. Select the adapters that will be members of the team.

l Click the checkbox of any adapter that you want to add to the team.
l Clear the checkbox of any adapter that you want to remove from the team.
6. Click OK.

Renaming a Team
1. Open the Team Properties dialog box by double-clicking on a team listing in the Computer
Management window.
2. Click the Settings tab.
3. Click Modify Team, then click the Name tab.
4. Type a new team name, then click OK.

NOTE: 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 Team
1. Open the Team Properties dialog box by double-clicking on a team listing in the Computer
Management window.
2. Click the Settings tab.
3. Select the team you want to remove, then click Remove Team.
4. Click Yes when prompted.

NOTE: If you defined a VLAN or QoS Prioritization on an adapter joining a team, you may have to
redefine it when it is returned to a stand-alone mode.

Specifying a Preferred Primary or Secondary Adapter

You must specify a primary adapter before you can specify a secondary adapter.

1. In the Team Properties dialog box's Settings tab, click Modify Team.
2. On the Adapters tab, select an adapter.
3. Click Set Primary or Set Secondary.
4. Click OK.

The adapter's preferred setting appears in the Priority column on Intel PROSet's Team Configuration
tab. A "1" indicates a preferred primary adapter, and a "2" indicates a preferred secondary adapter.

4.1.2.2 Configuring Teams with Windows PowerShell

Using non-Intel cmdlets, such as the Set-NetAdapterAdvancedProperty cmdlet provided in Microsoft
PowerShell*, to change settings for an ANS-teamed adapter may cause the team to stop using that
adapter to pass traffic. You may see this as reduced performance or the adapter being disabled in the
PROSet Teaming GUI. You can repair the issue by changing the setting back to its previous state, or by
removing the adapter from the ANS team and then adding it back.

705831 29
Intel® Ethernet Adapters and Devices User Guide

Creating a Team
Use the New-IntelNetTeam cmdlet. For example:
New-IntelNetTeam -TeamMemberNames "<adapter1_name>", "<adapter2_name>" -TeamMode
AdapterFaultTolerance -TeamName "<team_name>"

Changing Which Adapters Are In a Team

Use the Add-IntelNetTeamMember or Remove-IntelNetTeamMember cmdlet. For example:
Add-IntelNetTeamMember -TeamName "<team_name>" -Name "<adapter_name>"

Renaming a Team
Use the Set-IntelNetTeam cmdlet. For example
Set-IntelNetTeam -TeamName "<team_name>" -NewTeamName "<new_team_name>"

Removing a Team
Use the Remove-IntelNetTeam cmdlet. For example
Remove-IntelNetTeamMember -Name "<adapter_name>"

NOTE: If you defined a VLAN or QoS Prioritization on an adapter joining a team, you may have to
redefine it when it is returned to a stand-alone mode.

Specifying a Preferred Primary or Secondary Adapter

Use the Set-IntelNetTeam cmdlet. For example
Set-IntelNetTeam -TeamName "Team 1" -PrimaryAdapterName "<adapter1_name>" -
SecondaryAdapterName "<adapter2_name>"

4.1.2.3 Configuring Teams with Intel PROSet ACU

Creating a Team with Intel PROSet ACU

1. Launch the Intel PROSet ACU.
2. Select an adapter to start the team.
3. Click the Teaming/VLANs tab.
4. In the Teaming panel, click Create Team.
5. Select the adapters to include in the team, then click Next.
6. Type a name for the team.
7. Select the teaming mode, then click Next.
8. [Optional] Designate Primary and Secondary adapters for the team.
9. Click Finish.

705831 30
Intel® Ethernet Adapters and Devices User Guide

Changing Which Adapters Are In a Team

1. Launch the Intel PROSet ACU.
2. Select the team you wish to modify.
3. In the Team Members panel, click Modify Members.
4. Select the adapters that will be members of the team
5. Click Apply Changes.

Renaming a Team
1. Launch the Intel PROSet ACU.
2. Select the team you wish to modify.
3. In the Team Information panel, type a new team name..
4. Click Apply Changes.

Removing a Team
1. Launch the Intel PROSet ACU.
2. Select the team you wish to remove.
3. Click Remove Team.

NOTE: If you defined a VLAN or QoS Prioritization on an adapter joining a team, you may have to
redefine it when it is returned to a stand-alone mode.

Specifying a Preferred Primary or Secondary Adapter

You must specify a primary adapter before you can specify a secondary adapter.

1. Launch the Intel PROSet ACU.

2. Select the team you wish to modify.
3. Select your preferred Primary Adapter.
4. Select your preferred Secondary Adapter.
5. Click Apply Changes.

4.1.3 Teaming Modes

4.1.3.1 Overview
The following table explains the available teaming modes. Follow the links in the left column to view details
about that mode.

705831 31
Intel® Ethernet Adapters and Devices User Guide

Mode Description

Adapter Fault Tolerance (AFT) Provides automatic redundancy for a server's network connection. If the primary
adapter fails, the secondary adapter takes over. Adapter Fault Tolerance supports
two to eight adapters per team. This teaming type works with any hub or switch.
All team members must be connected to the same subnet.

Switch Fault Tolerance (SFT) Provides failover between two adapters connected to separate switches. Switch
Fault Tolerance supports two adapters per team. Spanning Tree Protocol (STP)
must be enabled on the switch when you create an SFT team. When SFT teams
are created, the Activation Delay is automatically set to 60 seconds. This
teaming type works with any switch or hub. All team members must be connected
to the same subnet.

Adaptive Load Balancing (ALB) Provides load balancing of transmit traffic and adapter fault tolerance. In
Microsoft* Windows* operating systems, you can also enable or disable receive
load balancing (RLB) in ALB teams (by default, RLB is enabled).

Virtual Machine Load Balancing (VMLB) Provides transmit and receive traffic load balancing across Virtual Machines
bound to the team interface, as well as fault tolerance in the event of switch port,
cable, or adapter failure. This teaming type works with any switch.

Static Link Aggregation (SLA) Provides increased transmission and reception throughput in a team of two to
eight adapters. This team type replaces the following team types from prior
software releases: Fast EtherChannel*/Link Aggregation (FEC) and Gigabit
EtherChannel*/Link Aggregation (GEC). This type also includes adapter fault
tolerance and load balancing (only routed protocols). This teaming type requires
a switch with Intel Link Aggregation, Cisco* FEC or GEC, or IEEE 802.3ad Static
Link Aggregation capability.

NOTE: All adapters in a Link Aggregation team running in static mode must run at
the same speed and must be connected to a Static Link Aggregation capable
switch. If the speed capability of adapters in a Static Link Aggregation team are
different, the speed of the team is dependent on the lowest common
denominator.

IEEE 802.3ad Dynamic Link Aggregation Creates one or more teams using Dynamic Link Aggregation with mixed-speed
adapters. Like the Static Link Aggregation teams, Dynamic 802.3ad teams
increase transmission and reception throughput and provide fault tolerance. This
teaming type requires a switch that fully supports the IEEE 802.3ad standard.

Multi-Vendor Teaming (MVT) Adds the capability to include adapters from selected other vendors in a team. If
you are using a Windows-based computer, you can team adapters that appear in
the Intel PROSet teaming wizard.

705831 32
Intel® Ethernet Adapters and Devices User Guide

IMPORTANT:
l Be sure to use the latest available drivers on all adapters.
l Before creating a team, adding or removing team members, or changing advanced
settings of a team member, make sure each team member has been configured similarly.
Settings to check include VLANs and QoS Packet Tagging, Jumbo Frames, and the various
offloads. These settings are available in Intel PROSet's Advanced tab. Pay particular
attention when using different adapter models or adapter versions, as adapter capabilities
vary.
l If team members implement Advanced features differently, failover and team
functionality will be affected. To avoid team implementation issues:
l Create teams that use similar adapter types and models.
l Reload the team after adding an adapter or changing any Advanced features. One
way to reload the team is to select a new preferred primary adapter. Although there
will be a temporary loss of network connectivity as the team reconfigures, the team
will maintain its network addressing schema.

NOTES:
l Hot Plug operations for an adapter that is part of a team are only available in Windows
Server.
l For SLA teams, all team members must be connected to the same switch. For AFT, ALB, and
RLB teams, all team members must belong to the same subnet. The members of an SFT
team must be connected to a different switch.
l Teaming only one adapter port is possible, but provides no benefit.

4.1.3.2 Primary and Secondary Adapters

Teaming modes that do not require a switch with the same capabilities (AFT, SFT, ALB (with RLB)) use a
primary adapter. In all of these modes except RLB, the primary is the only adapter that receives traffic. RLB
is enabled by default on an ALB team.

If the primary adapter fails, another adapter will take over its duties. If you are using more than two
adapters, and you want a specific adapter to take over if the primary fails, you must specify a secondary
adapter. If an Intel AMT enabled device is part of a team, it must be designated as the primary adapter for
the team.

There are two types of primary and secondary adapters:

l Default primary adapter: If you do not specify a preferred primary adapter, the software will
choose an adapter of the highest capability (model and speed) to act as the default primary. If a
failover occurs, another adapter becomes the primary. Once the problem with the original primary is
resolved, the traffic will not automatically restore to the default (original) primary adapter in most
modes. The adapter will, however, rejoin the team as a non-primary.
l Preferred Primary/Secondary adapters: You can specify a preferred adapter. Under normal
conditions, the Primary adapter handles all traffic. The Secondary adapter will receive traffic if the
primary fails. If the Preferred Primary adapter fails, but is later restored to an active status, control is
automatically switched back to the Preferred Primary adapter. Specifying primary and secondary
adapters adds no benefit to SLA and IEEE 802.3ad dynamic teams, but doing so forces the team to
use the primary adapter's MAC address.

705831 33
Intel® Ethernet Adapters and Devices User Guide

4.1.3.3 Failover and Failback

When a link fails, either because of port or cable failure, team types that provide fault tolerance will
continue to send and receive traffic. Failover is the initial transfer of traffic from the failed link to a good
link. Failback occurs when the original adapter regains link. You can use the Activation Delay setting
(located on the Advanced tab of the team's properties in Device Manager) to specify a how long the failover
adapter waits before becoming active. If you don't want your team to failback when the original adapter
gets link back, you can set the Allow Failback setting to disabled (located on the Advanced tab of the team's
properties in Device Manager).

4.1.3.4 Adapter Fault Tolerance (AFT)

Adapter Fault Tolerance (AFT) provides automatic recovery from a link failure caused from a failure in an
adapter, cable, switch, or port by redistributing the traffic load across a backup adapter.

Failures are detected automatically, and traffic rerouting takes place as soon as the failure is detected. The
goal of AFT is to ensure that load redistribution takes place fast enough to prevent user sessions from being
disconnected. AFT supports two to eight adapters per team. Only one active team member transmits and
receives traffic. If this primary connection (cable, adapter, or port) fails, a secondary, or backup, adapter
takes over. After a failover, if the connection to the user-specified primary adapter is restored, control
passes automatically back to that primary adapter.

AFT is the default mode when a team is created. This mode does not provide load balancing.

NOTES:
l AFT teaming requires that the switch not be set up for teaming and that spanning tree
protocol is turned off for the switch port connected to the NIC or LOM on the server.
l All members of an AFT team must be connected to the same subnet.

4.1.3.5 Switch Fault Tolerance (SFT)

Switch Fault Tolerance (SFT) supports only two NICs in a team connected to two different switches. In SFT,
one adapter is the primary adapter and one adapter is the secondary adapter. During normal operation, the
secondary adapter is in standby mode. In standby, the adapter is inactive and waiting for failover to occur.
It does not transmit or receive network traffic. If the primary adapter loses connectivity, the secondary
adapter automatically takes over. When SFT teams are created, the Activation Delay is automatically set to
60 seconds.

In SFT mode, the two adapters creating the team can operate at different speeds.

NOTE: SFT teaming requires that the switch not be set up for teaming and that spanning tree
protocol is turned on.

Configuration Monitoring
You can set up monitoring between an SFT team and up to five IP addresses. This allows you to detect link
failure beyond the switch. You can ensure connection availability for several clients that you consider
critical. If the connection between the primary adapter and all of the monitored IP addresses is lost, the
team will failover to the secondary adapter.

705831 34
Intel® Ethernet Adapters and Devices User Guide

4.1.3.6 Adaptive/Receive Load Balancing (ALB/RLB)

Adaptive Load Balancing (ALB) is a method for dynamic distribution of data traffic load among multiple
physical channels. The purpose of ALB is to improve overall bandwidth and end station performance. In
ALB, multiple links are provided from the server to the switch, and the intermediate driver running on the
server performs the load balancing function. The ALB architecture utilizes knowledge of Layer 3
information to achieve optimum distribution of the server transmission load.

ALB is implemented by assigning one of the physical channels as Primary and all other physical channels as
Secondary. Packets leaving the server can use any one of the physical channels, but incoming packets can
only use the Primary Channel. With Receive Load Balancing (RLB) enabled, it balances IP receive traffic.
The intermediate driver analyzes the send and transmit loading on each adapter and balances the rate
across the adapters based on destination address. Adapter teams configured for ALB and RLB also provide
the benefits of fault tolerance.

NOTES:
l ALB teaming requires that the switch not be set up for teaming and that spanning tree
protocol is turned off for the switch port connected to the network adapter in the server.
l ALB does not balance traffic when protocols such as NetBEUI and IPX* are used.
l You may create an ALB team with mixed speed adapters. The load is balanced according to
the adapter's capabilities and bandwidth of the channel.
l All members of ALB and RLB teams must be connected to the same subnet.
l Virtual NICs cannot be created on a team with Receive Load Balancing enabled. Receive
Load Balancing is automatically disabled if you create a virtual NIC on a team.

4.1.3.7 Virtual Machine Load Balancing

Virtual Machine Load Balancing (VMLB) provides transmit and receive traffic load balancing across Virtual
Machines bound to the team interface, as well as fault tolerance in the event of switch port, cable, or
adapter failure.

The driver analyzes the transmit and receive load on each member adapter and balances the traffic across
member adapters. In a VMLB team, each Virtual Machine is associated with one team member for its TX
and RX traffic.

If only one virtual NIC is bound to the team, or if Hyper-V is removed, then the VMLB team will act like an
AFT team.

NOTES:
l VMLB does not load balance non-routed protocols such as NetBEUI and some IPX* traffic.
l VMLB supports from two to eight adapter ports per team.
l You can create a VMLB team with mixed speed adapters. The load is balanced according to
the lowest common denominator of adapter capabilities and the bandwidth of the channel.
l You cannot use and Intel AMT enabled adapter a VMLB team.

4.1.3.8 Static Link Aggregation

Static Link Aggregation (SLA) is very similar to ALB, taking several physical channels and combining them
into a single logical channel.

This mode works with:

705831 35
Intel® Ethernet Adapters and Devices User Guide

l Cisco EtherChannel capable switches with channeling mode set to "on"

l Intel switches capable of Link Aggregation
l Other switches capable of static 802.3ad

NOTES:
l All adapters in a Static Link Aggregation team must run at the same speed and must be
connected to a Static Link Aggregation-capable switch. If the speed capabilities of adapters
in a Static Link Aggregation team are different, the speed of the team is dependent on the
switch.
l Static Link Aggregation teaming requires that the switch be set up for Static Link
Aggregation teaming and that spanning tree protocol is turned off.
l An Intel AMT enabled adapter cannot be used in an SLA team.

4.1.3.9 IEEE 802.3ad: Dynamic Link Aggregation

IEEE 802.3ad is the IEEE standard. Teams can contain two to eight adapters. You must use 802.3ad
switches (in dynamic mode, aggregation can go across switches). Adapter teams configured for IEEE
802.3ad also provide the benefits of fault tolerance and load balancing. Under 802.3ad, all protocols can be
load balanced.

Dynamic mode supports multiple aggregators. Aggregators are formed by port speed connected to a
switch. For example, a team can contain adapters running at 1 Gbps and 10 Gbps, but two aggregators will
be formed, one for each speed. Also, if a team contains 1 Gbps ports connected to one switch, and a
combination of 1 Gbps and 10 Gbps ports connected to a second switch, three aggregators would be
formed. One containing all the ports connected to the first switch, one containing the 1 Gbps ports
connected to the second switch, and the third containing the 10Gbps ports connected to the second
switch.

NOTES:
l IEEE 802.3ad teaming requires that the switch be set up for IEEE 802.3ad (link
aggregation) teaming and that spanning tree protocol is turned off.
l Once you choose an aggregator, it remains in force until all adapters in that aggregation
team lose link.
l In some switches, copper and fiber adapters cannot belong to the same aggregator in an
IEEE 802.3ad configuration. If there are copper and fiber adapters installed in a system, the
switch might configure the copper adapters in one aggregator and the fiber-based adapters
in another. If you experience this behavior, for best performance you should use either only
copper-based or only fiber-based adapters in a system.
l An Intel AMT enabled adapter cannot be used in a DLA team.

Before you begin

l Verify that the switch fully supports the IEEE 802.3ad standard.
l Check your switch documentation for port dependencies. Some switches require pairing to start on
a primary port.
l Check your speed and duplex settings to ensure the adapter and switch are running at full duplex,
either forced or set to auto-negotiate. Both the adapter and the switch must have the same speed
and duplex configuration. The full-duplex requirement is part of the IEEE 802.3ad specification:
http://standards.ieee.org/. If needed, change your speed or duplex setting before you link the

705831 36
Intel® Ethernet Adapters and Devices User Guide

adapter to the switch. Although you can change speed and duplex settings after the team is
created, Intel recommends you disconnect the cables until settings are in effect. In some cases,
switches or servers might not appropriately recognize modified speed or duplex settings if settings
are changed when there is an active link to the network.
l If you are configuring a VLAN, check your switch documentation for VLAN compatibility notes. Not
all switches support simultaneous dynamic 802.3ad teams and VLANs. If you do choose to set up
VLANs, configure teaming and VLAN settings on the adapter before you link the adapter to the
switch. Setting up VLANs after the switch has created an active aggregator affects VLAN
functionality.

4.1.3.10 Multi-Vendor Teaming

Multi-Vendor Teaming (MVT) allows teaming with a combination of Intel and non-Intel adapters.

If you are using a Windows-based computer, adapters that appear in the Intel PROSet teaming wizard can
be included in a team.

MVT Design Considerations

l In order to activate MVT, you must have at least one Intel adapter or integrated connection in the
team, which must be designated as the primary adapter.
l A multi-vendor team can be created for any team type.
l All members in an MVT must operate on a common feature set (lowest common denominator).
l Manually verify that the frame setting for the non-Intel adapter is the same as the frame settings
for the Intel adapters.
l If a non-Intel adapter is added to a team, its RSS settings must match the Intel adapters in the
team.

4.2 Adaptive Inter-Frame Spacing

Compensates for excessive Ethernet packet collisions on the network.

The default setting works best for most computers and networks. By enabling this feature, the network
adapter dynamically adapts to the network traffic conditions. However, in some rare cases you might
obtain better performance by disabling this feature. This setting forces a static gap between packets.

To change this setting in Intel PROSet

Range l Enabled
l Disabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Adaptive Inter-Frame
Spacing" -DisplayValue "Enabled"

705831 37
Intel® Ethernet Adapters and Devices User Guide

4.3 Data Center Bridging (DCB)

Data Center Bridging (DCB) is a collection of standards-based extensions to classical Ethernet. It provides a
lossless data center transport layer that enables the convergence of LANs and SANs onto a single unified
fabric.

Furthermore, DCB is a configuration Quality of Service implementation in hardware. It uses the VLAN
priority tag (802.1p) to filter traffic. That means that there are 8 different priorities that traffic can be
filtered into. It also enables priority flow control (802.1Qbb) which can limit or eliminate the number of
dropped packets during network stress. Bandwidth can be allocated to each of these priorities, which is
enforced at the hardware level (802.1Qaz).

DCB includes the following capabilities:

l Priority-based flow control (PFC; IEEE 802.1Qbb)
l Enhanced transmission selection (ETS; IEEE 802.1Qaz)
l Congestion notification (CN)
l Extensions to the Link Layer Discovery Protocol (LLDP) standard (IEEE 802.1AB) that enable Data
Center Bridging Capability Exchange Protocol (DCBX)

Adapter firmware implements LLDP and DCBX protocol agents as per 802.1AB and 802.1Qaz respectively.

There are two supported versions of DCBX.

l CEE Version: The specification can be found as a link within the following document:
http://www.ieee802.org/1/files/public/docs2008/dcb-baseline-contributions-1108-v1.01.pdf
l IEEE Version: The specification can be found as a link within the following document:
https://standards.ieee.org/findstds/standard/802.1Qaz-2011.html

NOTE: The OS DCBX stack defaults to the CEE version of DCBX, and if a peer is transmitting IEEE
TLVs, it will automatically transition to the IEEE version.

For more information on DCB, including the DCB Capability Exchange Protocol Specification, go to
http://www.ieee802.org/1/pages/dcbridges.html

4.3.1 DCB for Windows Configuration

To change this setting in Intel PROSet

This setting is found on the Data Center tab of the device's Device Manager property sheet or in the Data
Center panel in Intel PROSet Adapter Configuration Utility.

You can use Intel PROSet to perform the following tasks:

l Display Status:
l Enhanced Transmission Selection
l Priority Flow Control

Non-operational status: If the Status indicator shows that DCB is non-operational, there
may be a number of possible reasons:
l DCB is not enabled - select the checkbox to enable DCB.
l One or more of the DCB features is in a non-operational state.

705831 38
Intel® Ethernet Adapters and Devices User Guide

A non-operational status is most likely to occur when Use Switch Settings is selected or
Using Advanced Settings is active. This is generally a result of one or more of the DCB
features not getting successfully exchanged with the switch. Possible problems include:
l One of the features is not supported by the switch.
l The switch is not advertising the feature.
l The switch or host has disabled the feature (this would be an advanced setting for the
host).
l Disable/enable DCB
l Troubleshooting information

NOTES:
l On X710 based devices running Microsoft Windows, DCB is only supported on NVM version
4.52 and newer. Older NVM versions must be updated before the adapter is capable of DCB
support in Windows.
l On systems running a Microsoft Windows Server operating system, enabling *QoS/priority
flow control will disable link level flow control.
l If *QOS/DCB is not available, it may be for one of the following reasons:
l The Firmware LLDP (FW-LLDP) agent was disabled from a pre-boot environment
(typically UEFI).
l This device is based on the Intel® Ethernet Controller X710 and the current link
speed is 2.5 Gbps or 5 Gbps.

4.3.1.1 Hyper-V (DCB and VMQ)

NOTE: Configuring a device in the VMQ + DCB mode reduces the number of VMQs available for
guest OSes.

4.3.2 DCB for Linux

Intel Ethernet drivers support firmware-based or software-based DCBX in Linux, depending on the
underlying PF device. The following table summarizes DCBX support by driver.

Linux Driver Firmware-Based DCBX Software-Based DCBX

ice Supported Supported

i40e Supported Supported

ixgbe Not supported Supported

In firmware-based mode, firmware intercepts all LLDP traffic and handles DCBX negotiation
transparently for the user. In this mode, the adapter operates in "willing" DCBX mode, receiving DCB
settings from the link partner (typically a switch). The local user can only query the negotiated DCB
configuration.

In software-based mode, LLDP traffic is forwarded to the network stack and user space, where a
software agent can handle it. In this mode, the adapter can operate in either "willing" or "nonwilling" DCBX

705831 39
Intel® Ethernet Adapters and Devices User Guide

mode and DCB configuration can be both queried and set locally. Software-based mode requires the FW-
based LLDP Agent to be disabled and kernel CONFIG_DCB enabled.

NOTES:
l Only one LLDP/DCBX agent can be active on a single interface at a time.
l Software-based and firmware-based DCBX modes are mutually exclusive.
l When the firmware DCBX agent is active, software agents will not be able to receive or
transmit LLDP frames. See "Firmware Link Layer Discovery Protocol (FW-LLDP)" on
page 42, as well as the Linux driver readme in your installation, for information on enabling
or disabling the FW-LLDP agent.
l In software-based DCBX mode, you can configure DCB parameters using software
LLDP/DCBX agents that interface with the Linux kernel's DCB Netlink API. We recommend
using OpenLLDP as the DCBX agent when running in software mode. For more information,
see the OpenLLDP man pages and https://github.com/intel/openlldp.
l For information on configuring DCBX parameters on a switch, please consult the switch
manufacturer's documentation.

4.3.3 iSCSI Over DCB

Intel® Ethernet adapters support iSCSI software initiators that are native to the underlying operating
system. Data Center Bridging is most often configured at the switch. If the switch is not DCB capable, the
DCB handshake will fail but the iSCSI connection will not be lost.

NOTE: DCB does not install in a VM. iSCSI over DCB is only supported in the base OS. An iSCSI
initiator running in a VM will not benefit from DCB ethernet enhancements.

4.3.3.1 Microsoft Windows Configuration

iSCSI installation includes the installation of the iSCSI DCB Agent (iscsidcb.exe) user mode service. The
Microsoft iSCSI Software Initiator enables the connection of a Windows host to an external iSCSI storage
array using an Intel Ethernet adapter. Please consult your operating system documentation for
configuration details.

To change this setting in Intel PROSet

This setting is found on the Data Center tab of the device's Device Manager property sheet or in the Data
Center panel in Intel PROSet Adapter Configuration Utility.

This setting provides feedback as to the DCB state, operational or non-operational, as well as providing
additional details should it be non-operational.

NOTE: On Microsoft Windows Server operating systems, if you configure Priority using IEEE, the
iSCSI policy may not be created automatically. To create the iSCSI policy manually, use Powershell
and type:
New-NetQosPolicy -Name "UP4" -PriorityValue 8021 Action 4 –iSCSI

705831 40
Intel® Ethernet Adapters and Devices User Guide

Using iSCSI over DCB with Intel ANS Teaming

The Intel® iSCSI Agent is responsible for maintaining all packet filters for the purpose of priority tagging
iSCSI traffic flowing over DCB-enabled adapters. The iSCSI Agent will create and maintain a traffic filter for
an Intel ANS Team if at least one member of the team has an "Operational" DCB status. However, if any
adapter on the team does not have an "Operational" DCB status, the iSCSI Agent will log an error in the
Windows Event Log for that adapter. These error messages are to notify the administrator of configuration
issues that need to be addressed, but do not affect the tagging or flow of iSCSI traffic for that team, unless
it explicitly states that the TC Filter has been removed.

4.3.3.2 Linux Configuration

In the case of Open Source distributions, virtually all distributions include support for an Open iSCSI
Software Initiator and Intel® Ethernet adapters will support them. Please consult your distribution
documentation for additional configuration details on their particular Open iSCSI initiator.

Intel® 82599-based adapters support iSCSI within a Data Center Bridging cloud. Used in conjunction with
switches and targets that support the iSCSI/DCB application TLV, this solution can provide guaranteed
minimum bandwidth for iSCSI traffic between the host and target. This solution enables storage
administrators to segment iSCSI traffic from LAN traffic. Previously, iSCSI traffic within a DCB supported
environment was treated as LAN traffic by switch vendors. Please consult your switch and target vendors
to ensure that they support the iSCSI/DCB application TLV.

4.4 Direct Memory Access (DMA) Coalescing

DMA (Direct Memory Access) allows the network device to move packet data directly to the system's
memory, reducing CPU utilization. However, the frequency and random intervals at which packets arrive
do not allow the system to enter a lower power state. DMA Coalescing allows the NIC to collect packets
before it initiates a DMA event. This may increase network latency but also increases the chances that the
system will consume less energy. Adapters and network devices based on the Intel® Ethernet Controller
I350 (and later controllers) support DMA Coalescing.

Higher DMA Coalescing values result in more energy saved but may increase your system's network
latency. If you enable DMA Coalescing, you should also set the Interrupt Moderation Rate to 'Minimal'. This
minimizes the latency impact imposed by DMA Coalescing and results in better peak network throughput
performance. You must enable DMA Coalescing on all active ports in the system. You may not gain any
energy savings if it is enabled only on some of the ports in your system. There are also several BIOS,
platform, and application settings that will affect your potential energy savings. A white paper containing
information on how to best configure your platform is available on the Intel website.

To change this setting in Intel PROSet

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "DMA Coalescing" -
DisplayValue "Enabled"

4.5 Dynamic Device Personalization (DDP)

Adapters based on the Intel® Ethernet 800 Series require a Dynamic Device Personalization (DDP)
package file to enable advanced features (such as dynamic tunneling, Intel Ethernet Flow Director, RSS,
and ADQ). DDP allows you to change the packet processing pipeline of a device by applying a profile package

705831 41
Intel® Ethernet Adapters and Devices User Guide

to the device at runtime. Profiles can be used to, for example, add support for new protocols, change
existing protocols, or change default settings. DDP profiles can also be rolled back without rebooting the
system.

The DDP package loads during device initialization or driver runtime, depending on the operating system.
The driver checks to see if the DDP package is present and compatible. If this file exists, the driver will load
it into the device. If not, the driver will go into Safe Mode where it will use the configuration contained in
the device's NVM.

Safe Mode disables advanced and performance features, and supports only basic traffic and minimal
functionality, such as updating the NVM or downloading a new driver or DDP package. For more
information, see "Safe Mode" on page 114.

A general-purpose, default DDP package is automatically installed with all supported Intel Ethernet 800
Series drivers on supported operating systems. Additional DDP packages are available to address needs for
specific market segments or targeted solutions.

Refer to the Intel® Ethernet Controller E810 Dynamic Device Personalization (DDP) Technology Guide for
more information on configuring DDP.

NOTES:
l If you are using DPDK, see the DPDK documentation for installation instructions and more
information.
l In ESXi:
l Support for DDP packages for specific market segments requires the following:
l Driver: icen 1.9.1.x or higher
l Tool: intnet 1.8.3.x or higher
l Use esxcli to load and unload DDP packages for specific market segments during
driver runtime.
l A package update is not persistent between device resets or system reboots.

4.6 Firmware Link Layer Discovery Protocol (FW-LLDP)

Devices based on the Intel® Ethernet 800 and 700 Series use a Link Layer Discovery Protocol (LLDP)
agent that runs in the firmware. When it is running, it prevents the operating system and applications
from receiving LLDP traffic from the network adapter.
l The FW-LLDP setting is per port and persists across reboots.
l The FW-LLDP Agent is required for DCB to function.

Adapters Based on the Intel® Ethernet 800 Series

FW-LLDP is disabled in NVM by default. To enable/disable the FW-LLDP Agent:

l Linux: Use ethtool to persistently set or show the fw-lldp-agent private flag.
l FreeBSD: Use sysctl to persistently set or show the fw_lldp_agent flag.
l ESX: Use the esxcli command to persistently set or get the fw-lldp-agent setting.
l Microsoft Windows: The base driver does not persistently change FW-LLDP. Use the LLDP Agent
attribute in UEFI HII to persistently change the FW-LLDP setting. If you enable DCB when FW-LLDP
is disabled, the base driver temporarily starts the LLDP Agent while DCB functionality is enabled.

705831 42
Intel® Ethernet Adapters and Devices User Guide

Adapters Based on the Intel® Ethernet 700 Series

FW-LLDP is enabled in NVM by default. To enable/disable the FW-LLDP Agent:

l Linux: Use ethtool to set or show the disable-fw-lldp private flag.
l FreeBSD: Use sysctl to set or show the fw_lldp flag.
l ESX: Use the esxcfg-module command to set or get the LLDP module parameter.
l Microsoft Windows: Use the LLDP Agent attribute in UEFI HII to change the FW-LLDP setting.
Note: You must enable the UEFI HII "LLDP AGENT" attribute for the FW-LLDP setting to take effect.
If "LLDP AGENT" is set to disabled in UEFI HII, you cannot enable FW-LLDP from the OS.
l You must enable the LLDP Agent from UEFI HII to use DCB.

4.7 Firmware Logs and Advanced Debugging

Intel Ethernet 800 Series devices support the ability to generate firmware logs or other information, to
debug issues with Customer Support. Refer to the following for more information:
l "Firmware Logging" on page 104
l "Debug Dump" on page 108
l "Health Status Messages" on page 113

4.8 Forward Error Correction (FEC) Mode

Allows you to set the Forward Error Correction (FEC) mode. FEC improves link stability, but increases
latency. Many high quality optics, direct attach cables, and backplane channels provide a stable link
without FEC.

The driver allows you to set the following FEC Modes:

l Auto FEC - Sets the FEC Mode based on the capabilities of the attached cable.
l CL108 RS-FEC - Selects only RS-FEC ability and request capabilities.
l CL74 FC-FEC/BASE-R - Selects only BASE-R ability and request capabilities.
l No FEC - Disables FEC.

705831 43
Intel® Ethernet Adapters and Devices User Guide

NOTES:
l For devices to benefit from this feature, link partners must have FEC enabled.
l Intel® Ethernet 800 Series devices only enable Forward Error Correction (FEC)
configurations that are supported by the connected media and which are expected to yield
healthy Bit Error Rate (BER) connections.
l If you enable the registry keyword AllowNoFECModulesInAuto, Auto FEC negotiation
will include 'No FEC' in case your link partner does not have FEC enabled or is not FEC
capable.
l To change this setting in Windows PowerShell, use the Set-
IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -
RegistryKeyword AllowNoFECModulesInAuto -RegistryValue 1
l To change this setting in Linux, use ethtool. For example:
# ethtool --set-priv-flags <ethX> allow-no-fec-modules-in-auto on
l If you are having link issues (including no link) at link speeds faster than 10 Gbps, check
your switch configuration and/or specifications. Many optical connections and direct attach
cables require RS-FEC for connection speeds faster than 10 Gbps. One of the following may
resolve the issue:
l Configure your switch to use RS-FEC mode.
l Specify a 10 Gbps, or slower, link speed connection.
l If you are attempting to connect at 25 Gbps, try using an SFP28 CA-S or CS-N Direct
Attach cable. These cables do not require RS-FEC.
l If your switch does not support RS-FEC mode, check with your switch vendor for the
availability of a SW or FW upgrade.

To change this setting in Intel PROSet

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "FEC Mode" -DisplayValue
"Auto FEC"

4.9 Flow Control

Enables adapters to more effectively regulate traffic. Adapters generate flow control frames when their
receive queues reach a pre-defined limit. Generating flow control frames signals the transmitter to slow
transmission. Adapters respond to flow control frames by pausing packet transmission for the time
specified in the flow control frame.

By enabling adapters to adjust packet transmission, flow control helps prevent dropped packets. You may
improve RDMA performance by enabling flow control on all nodes and on the switch they are connected to.

705831 44
Intel® Ethernet Adapters and Devices User Guide

NOTES:
l For adapters to benefit from this feature, link partners must support flow control frames.
l On systems running a Microsoft Windows Server operating system, enabling *QoS/priority
flow control will disable link level flow control.
l Some devices support Auto Negotiation. Selecting this will cause the device to advertise the
value stored in its NVM (usually "Disabled").

To change this setting in Intel PROSet

Range l Disabled
l RX Enabled
l TX Enabled
l RX & TX Enabled
l Auto Negotiation (only available on some
adapters)

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Flow Control" -
DisplayValue "Rx Enabled"

4.10 Gigabit PHY Mode

Determines whether the adapter or link partner is designated as the primary. The other device is
designated as the secondary. By default, the IEEE 802.3ab specification defines how conflicts are handled.
Multi-port devices such as switches have higher priority over single port devices and are assigned as the
primary. If both devices are multi-port devices, the one with higher seed bits becomes the primary. This
default setting is called "Hardware Default."

NOTE: In most scenarios, we recommended the default value of this feature.

Setting this to any value other than "Auto Detect" overrides the hardware default.

To change this setting in Intel PROSet

Range l Force Primary Mode

l Force Secondary Mode
l Auto Detect

NOTE: When Gigabit PHY Mode is forced to Primary mode on both the Intel adapter and its link
partner, the link speed obtained by the Intel adapter may be lower than expected or link may not
be established.

705831 45
Intel® Ethernet Adapters and Devices User Guide

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Gigabit PHY Mode" -
DisplayValue "Auto Detect"

4.11 Interrupt Moderation Rate

Sets the Interrupt Throttle Rate (ITR). This setting moderates the rate at which Transmit and Receive
interrupts are generated.

When an event such as packet receiving occurs, the adapter generates an interrupt. The interrupt
interrupts the CPU and any application running at the time, and calls on the driver to handle the packet. At
greater link speeds, more interrupts are created, and CPU rates also increase. This results in poor system
performance. When you use a higher ITR setting, the interrupt rate is lower and the result is better CPU
performance.

NOTE: A higher ITR rate also means that the driver has more latency in handling packets. If the
adapter is handling many small packets, it is better to lower the ITR so that the driver can be more
responsive to incoming and outgoing packets.

Altering this setting may improve traffic throughput for certain network and system configurations,
however the default setting is optimal for common network and system configurations. Do not change this
setting without verifying that the desired change will have a positive effect on network performance.

To change this setting in Intel PROSet

Range l Adaptive
l Extreme
l High
l Medium
l Low
l Minimal
l Off

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Interrupt Moderation
Rate" -DisplayValue "Adaptive"

4.12 Jumbo Frames

Enables or disables Jumbo Packet capability. The standard Ethernet frame size is about 1514 bytes, while
Jumbo Packets are larger than this. Jumbo Packets can increase throughput and decrease CPU utilization.
However, additional latency may be introduced.

705831 46
Intel® Ethernet Adapters and Devices User Guide

Enable Jumbo Packets only if ALL devices across the network support them and are configured to use the
same frame size. When setting up Jumbo Packets on other network devices, be aware that network
devices calculate Jumbo Packet sizes differently. Some devices include the frame size in the header
information while others do not. Intel adapters do not include frame size in the header information.

Jumbo Packets can be implemented simultaneously with VLANs and teaming. If a team contains one or
more non-Intel adapters, the Jumbo Packets feature for the team is not supported. Before adding a non-
Intel adapter to a team, make sure that you disable Jumbo Packets for all non-Intel adapters using the
software shipped with the adapter.

Restrictions
l Jumbo frames are not supported in multi-vendor team configurations.
l Supported protocols are limited to IP (TCP, UDP).
l Jumbo frames require compatible switch connections that forward Jumbo Frames. Contact your
switch vendor for more information.
l When standard-sized Ethernet frames (64 to 1518 bytes) are used, there is no benefit to
configuring Jumbo Frames.
l The Jumbo Packets setting on the switch must be set to at least 8 bytes larger than the adapter
setting for Microsoft Windows operating systems, and at least 22 bytes larger for all other operating
systems.
l Jumbo Frames are not supported over Intel ANS VLANs under Microsoft Windows 10.

To change this setting in Intel PROSet

Range l Disabled (1514 bytes)

l 4088 Bytes
l 9014 Bytes

(Set the switch 4 bytes higher for CRC, plus 4 bytes if using VLANs.)

NOTES:
l End-to-end hardware must support this capability; otherwise, packets will be dropped.
l Intel adapters that support Jumbo Packets have a frame size limit of 9238 bytes, with a
corresponding MTU size limit of 9216 bytes.

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Jumbo Packet" -
DisplayValue "4088 Bytes"

4.13 Link State on Interface Down

Sets if link is enabled or disabled when the interface is brought down. If this is set to Disabled and you
bring an interface down (using an administrative tool, or in another way), then the port will lose link. This
allows an attached switch to detect that the interface is no longer up. However, if Wake on LAN or
manageability is enabled on this port, link will remain up.

705831 47
Intel® Ethernet Adapters and Devices User Guide

To change this setting in Intel PROSet

Range l Enabled
l Disabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Link State on Interface
Down" -DisplayValue "Enabled"

4.14 Locally Administered Address

Overrides the initial MAC address with a user-assigned MAC address. To enter a new network address, type
a 12-digit hexadecimal number in this box.

To change this setting in Intel PROSet

Range 0000 0000 0001 - FFFF FFFF FFFD

Exceptions:
l Do not use a multicast address (Least Significant Bit of the high byte = 1). For
example, in the address 0Y123456789A, "Y" cannot be an odd number. (Y must be
0, 2, 4, 6, 8, A, C, or E.)
l Do not use all zeros or all Fs.

If you do not enter an address, the address is the original network address of the adapter.

For example,

Multicast: 0123 4567 8999 Broadcast: FFFF FFFF FFFF

Unicast (legal): 0070 4567 8999

NOTE: In a team, Intel PROSet uses either:

l The primary adapter's permanent MAC address if the team does not have an LAA configured,
or
l The team's LAA if the team has an LAA configured.

Intel PROSet does not use an adapter's LAA if the adapter is the primary adapter in a team and the
team has an LAA.

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Locally Administered
Address" -DisplayValue "<desired address>"

705831 48
Intel® Ethernet Adapters and Devices User Guide

4.15 Log Link State Event

This setting is used to enable/disable the logging of link state changes. If enabled, a link up change event or
a link down change event generates a message that is displayed in the system event logger. This message
contains the link's speed and duplex. Administrators view the event message from the system event log.

The following events are logged.

l The link is up.
l The link is down.
l Mismatch in duplex.
l Spanning Tree Protocol detected.

To change this setting in Intel PROSet

Range l Enabled
l Disabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Log Link State Event" -
DisplayValue "Enabled"

4.16 Low Latency Interrupts

LLI enables the network device to bypass the configured interrupt moderation scheme based on the type
of data being received. It configures which arriving TCP packets trigger an immediate interrupt, enabling
the system to handle the packet more quickly. Reduced data latency enables some applications to gain
faster access to network data.

NOTE: When LLI is enabled, system CPU utilization may increase.

LLI can be used for data packets containing a TCP PSH flag in the header or for specified TCP ports.
l Packets with TCP PSH Flag - Any incoming packet with the TCP PSH flag will trigger an
immediate interrupt. The PSH flag is set by the sending device.
l TCP Ports - Every packet received on the specified ports will trigger an immediate interrupt. Up to
eight ports may be specified.

To change this setting in Intel PROSet

Range l Disabled
l PSH Flag-Based
l Port-Based

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:

705831 49
Intel® Ethernet Adapters and Devices User Guide

Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Low Latency Interrupts" -

DisplayValue "Port-Based"

4.17 Malicious Driver Detection (MDD) for VFs

Some Intel Ethernet devices use Malicious Driver Detection (MDD) to detect malicious traffic from the VF
and disable Tx/Rx queues or drop the offending packet until a VF driver reset occurs. You can view MDD
messages in the PF's event log.
l If the device supports automatic VF resets and the driver detects an MDD event on the receive path,
the PF will automatically reset the VF and reenable queues. If automatic VF resets are disabled, the
PF will not automatically reset the VF when it detects MDD events. See the table below for
supported MDD features.
l If the PF driver logs MDD events from the VF, confirm that the correct VF driver is installed.
l To restore functionality, you can manually reload the VF or VM or, if supported by the device, enable
automatic VF resets.

The following table shows MDD capabilities by device family.

Feature Intel Ethernet Intel Ethernet Intel Ethernet Intel I350 Gigabit Net-
800 Series 700 Series 500 Series work Connection

Automatically resets the VF and reen- If enabled If enabled Yes Yes

ables queues after MDD events

Can disable automatic VF reset after Yes Yes No No

MDD events

4.17.1 MDD Auto Reset VFs

Automatically resets the virtual machine immediately after the adapter detects a Malicious Driver
Detection (MDD) event on the receive path.

To change this setting in Intel PROSet

Range l Disabled
l Enabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "MDD Auto Reset VFs" -
DisplayValue "Enabled"

4.18 Max Number of RSS Queues Per Vport

Sets the maximum number of Receive Side Scaling (RSS) queue pairs per VF.

705831 50
Intel® Ethernet Adapters and Devices User Guide

To change this setting in Intel PROSet

Range l 2 Queues
l 4 Queues
l 8 Queues
l 16 Queues

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Max Number of RSS Queues
Per Vport" -DisplayValue "4 Queues"

4.19 Offloads
In addition to the offloads included this subsection, see the following pages for related information:
l "Priority & VLAN Tagging " on page 63
l "Virtual Machine Queue Offloading" on page 77

4.19.1 IPv4 Checksum Offload

This allows the adapter to compute the IPv4 checksum of incoming and outgoing packets. This feature
enhances IPv4 receive and transmit performance and reduces CPU utilization.

With Offloading off, the operating system verifies the IPv4 checksum.

With Offloading on, the adapter completes the verification (on RX) and computation (on TX) for the
operating system.

To change this setting in Intel PROSet

Range l Disabled
l RX Enabled
l TX Enabled
l RX & TX Enabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "IPv4 Checksum Offload" -
DisplayValue "Tx Enabled"

4.19.2 Large Send Offload (IPv4 and IPv6)

Sets the adapter to offload the task of segmenting TCP messages into valid Ethernet frames. The
maximum frame size limit for large send offload is set to 64,000 bytes.

705831 51
Intel® Ethernet Adapters and Devices User Guide

Since the adapter hardware is able to complete data segmentation much faster than operating system
software, this feature may improve transmission performance. In addition, the adapter uses fewer CPU
resources.

To change this setting in Intel PROSet

Range l Enabled
l Disabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Large Send Offload V2
(IPv4)" -DisplayValue "Enabled"

4.19.3 NVGRE Encapsulated Task Offload

Network Virtualization using Generic Routing Encapsulation (NVGRE) increases the efficient routing of
network traffic within a virtualized or cloud environment. Some Intel® Ethernet Network devices perform
NVGRE processing, offloading it from the operating system. This reduces CPU utilization.

To change this setting in Intel PROSet

Range l Enabled
l Disabled

This setting is found in the Adapter Settings panel in Intel PROSet Adapter Configuration Utility. On the
device's Device Manager property sheet, it is found on the Advanced tab, under the Offloading Options >
Encapsulated Task Offload setting.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "NVGRE Encapsulated Task
Offload" -DisplayValue "Enabled"

4.19.4 QoS Offload

Configures the Quality of Service (QoS) offload setting for the miniport adapter. This feature allows you to
set a bandwidth cap and reservation to one or more virtual machines on a physical device, including both
software VMs and SR-IOV interfaces.

To change this setting in Intel PROSet

Range l Disabled
l Enabled

This setting is found on the Adapter tab and in the Adapter Settings panel of the Intel® PROSet Adapter
Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:

705831 52
Intel® Ethernet Adapters and Devices User Guide

Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "QoS Offload" -

DisplayValue "Enabled"

4.19.5 TCP Checksum Offload (IPv4 and IPv6)

Allows the adapter to verify the TCP checksum of incoming packets and compute the TCP checksum of
outgoing packets. This feature enhances receive and transmit performance and reduces CPU utilization.

With Offloading off, the operating system verifies the TCP checksum.

With Offloading on, the adapter completes the verification for the operating system.

To change this setting in Intel PROSet

Range l Disabled
l RX Enabled
l TX Enabled
l RX & TX Enabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "TCP Checksum Offload
(IPv4)" -DisplayValue "Tx Enabled"

4.19.6 UDP Checksum Offload (IPv4 and IPv6)

Allows the adapter to verify the UDP checksum of incoming packets and compute the UDP checksum of
outgoing packets. This feature enhances receive and transmit performance and reduces CPU utilization.

With Offloading off, the operating system verifies the UDP checksum.

With Offloading on, the adapter completes the verification for the operating system.

To change this setting in Intel PROSet

Range l Disabled
l RX Enabled
l TX Enabled
l RX & TX Enabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "UDP Checksum Offload
(IPv4)" -DisplayValue "Tx Enabled"

705831 53
Intel® Ethernet Adapters and Devices User Guide

4.19.7 UDP Segmentation Offload (IPv4 and IPv6)

Allows the adapter to segmenting UDP packets with payloads up to 64K into valid Ethernet frames.
Because the adapter hardware is able to complete data segmentation much faster than operating system
software, this feature may improve transmission performance. In addition, the adapter may use fewer CPU
resources.

With Offloading off, the operating system segments UDP packets into valid Ethernet frames.

With Offloading on, the adapter segments UDP packets for the operating system.

NOTE: UDP Segmentation Offload requires:

l Microsoft* Windows Server* 2019, Version 1903, or later
l Linux* kernel 4.18, or later

To change this setting in Intel PROSet

Range l Disabled
l Enabled

To change this setting in Windows PowerShell, use the Set_IntelNetAdapterSetting cmdlet. For example:
Set_IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "UDP Segmentation Offload
(IPv4)" -DisplayValue "Enabled"

4.19.8 VXLAN Encapsulated Task Offload

Virtual Extensible LAN (VXLAN) allows you to extend an L2 network over an L3 network, which may be
useful in a virtualized or cloud environment. Some Intel Ethernet devices perform VXLAN processing,
offloading it from the operating system. This reduces CPU utilization.

VXLAN may be useful in multi-tenant environments such as cloud service providers where the number of
VLANs exceeds the 4094 limit imposed by the 12-bit VLAN ID used in Ethernet data frames.

To change this setting in Intel PROSet

Range l Enabled
l Disabled

This setting is found in the Adapter Settings panel in Intel PROSet Adapter Configuration Utility. On the
device's Device Manager property sheet, it is found on the Advanced tab, under the Offloading Options >
Encapsulated Task Offload setting.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "VXLAN Encapsulated Task
Offload" -DisplayValue "Enabled"

705831 54
Intel® Ethernet Adapters and Devices User Guide

4.20 Performance Options

4.20.1 Optimizing Performance

You can configure Intel network adapter advanced settings to help optimize server performance. This
section provides tips for:
l "General Optimization" below
l "Optimization for Specific Usage Models" on the next page

NOTES:
l Linux users, see the README file in the Linux driver package for Linux-specific performance
enhancement details.
l The recommendations below are guidelines and should be treated as such. Additional factors
such as installed applications, bus type, network topology, and operating system also affect
system performance.
l These adjustments should be performed by a highly skilled network administrator. They are
not guaranteed to improve performance. Not all settings shown here may be available
through network driver configuration, operating system or system BIOS.
l When using performance test software, refer to the documentation of the application for
optimal results.

4.20.1.1 General Optimization

l Install the adapter in an appropriate slot.

NOTE: Some PCIe x8 slots are actually configured as x4 slots. These slots have insufficient
bandwidth for full line rate with some dual port devices. The driver can detect this situation
and will write the following message in the system log: “PCI-Express bandwidth available for
this card is not sufficient for optimal performance. For optimal performance a x8 PCI-Express
slot is required.” If this error occurs, moving your adapter to a true x8 slot will resolve the
issue.

l For an Intel® Ethernet 700 Series adapter to reach its full potential, you must install it in a PCIe
Gen3 x8 slot. Installing it in a shorter slot, or a Gen2 or Gen1 slot, will impact the throughput the
adapter can attain.
l Use the proper cabling for your device.
l Increase the number of TCP and Socket resources from the default value. For Windows based
systems, we have not identified system parameters other than the TCP Window Size which
significantly impact performance.
l Increase the allocation size of Driver Resources (transmit/receive buffers). However, most TCP
traffic patterns work best with the transmit buffer set to its default value, and the receive buffer set
to its minimum value.

Jumbo Frames
Enabling jumbo frames may increase throughput. You must enable jumbo frames on all of your network
components to get any benefit.

705831 55
Intel® Ethernet Adapters and Devices User Guide

RSS Queues
If you have multiple 10 Gbps (or faster) ports installed in a system, the RSS queues of each adapter port
can be adjusted to use non-overlapping sets of processors within the adapter's local Non-Uniform Memory
Access (NUMA) Node/Socket. Change the RSS Base Processor Number for each adapter port so that the
combination of the base processor and the max number of RSS processors settings ensure non-
overlapping cores. For Microsoft Windows systems, do the following:

1. Identify the adapter ports to be adjusted and inspect their RssProcessorArray using the
Get-NetAdapterRSS PowerShell cmdlet.
2. Identify the processors with NUMA distance 0. These are the cores in the adapter's local NUMA
Node/Socket and will provide the best performance.
3. Adjust the RSS Base processor on each port to use a non-overlapping set of processors within the
local set of processors. You can do this manually or using the following PowerShell command:
Set-NetAdapterAdvancedProperty -Name <Adapter Name> -DisplayName "RSS Base
Processor Number" -DisplayValue <RSS Base Proc Value>
4. Use the Get-NetAdapterAdvancedproperty cmdlet to check that the right values have been set:
Get-NetAdapterAdvancedproperty -Name <Adapter Name>

For Example: For a 4 port adapter with Local processors 0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26,
28, 30, and 'Max RSS processor' of 8, set the RSS base processors to 0, 8, 16 and 24.

CPU Affinity
When passing traffic on multiple network ports using an I/O application that runs on most or all of the
cores in your system, consider setting the CPU Affinity for that application to fewer cores. This should
reduce CPU utilization and in some cases may increase throughput for the device. The cores selected for
CPU Affinity must be local to the affected network device's Processor Node/Group. You can use the
PowerShell command Get-NetAdapterRSS to list the cores that are local to a device. You may need to
increase the number of cores assigned to the application to maximize throughput. Refer to your operating
system documentation for more details on setting the CPU Affinity.

4.20.1.2 Optimization for Specific Usage Models

The following table provides guidance for additional server usage models.

705831 56
Intel® Ethernet Adapters and Devices User Guide

Optimize For Useful For Optimization Tasks

Quick response Video, audio, and High Performance l Minimize or disable interrupt moderation rate
and low latency Computing Cluster (HPCC) servers
l Disable offload TCP segmentation
l Disable jumbo packets
l Increase transmit descriptors
l Increase receive descriptors
l Increase RSS queues

Throughput Data backup/retrieval and file serv- l Enable jumbo packets

ers
l Increase transmit descriptors
l Increase receive descriptors.
l On systems that support NUMA, set the Preferred NUMA
Node on each adapter to achieve better scaling across
NUMA nodes

CPU utilization Application, web, mail, and database l Maximize interrupt moderation rate
servers
l Keep the default setting for the number of receive
descriptors; avoid setting large numbers of receive
descriptors
l Decrease RSS queues
l In Hyper-V environments, decrease the max number of
RSS CPUs

4.20.2 Tuning Performance with SR-IOV

When SR-IOV is enabled in Hyper-V, the following steps can help to improve performance between VM to
VM and VM to Host.

From host OSes on both Host 1 and Host 2:

1. Enable RSS on the PF and vSwitch.

Enable-NetAdapterRss -name "ADAPTER_NAME"

2. Enable 4 queues per VF:

Set-VMNetworkAdapter -VMName "YOUR_TEST_VM_NAME"
-IovQueuePairsRequested 4
Get-VmNetworkAdapter -VMName * | where {$_.SwitchName -eq "YOUR_TEST_
SWITCH_NAME"} | Set-VmNetworkAdapter -IovQueuePairsRequested 4

3. Ensure the VMs have at least twice as many vCPUs as RSS queues. In this case, set the number of
total processors in the VM to 8. To do this:
a. Turn off the VM.
b. In the VM, click Settings.
c. Under Hardware, select Processor.
d. Change the value of Number of virtual processors to 8.
e. Apply the change.

705831 57
Intel® Ethernet Adapters and Devices User Guide

4. For Windows Server 2022, issue the following command while the VM is in the off state:

Set-VMProcessor -VMName "YOUR_VM_Name" -HwThreadCountPerCore 1

-Count 8

In both guest OSes VM1 and VM2:

1. Set RSS queues to 4 for all VFs in the guest OSes:
Set-NetAdapterRss -InterfaceDescription *adaptive*
-NumberOfReceiveQueues 4

2. Update the number of queues in the guest OS:

Set-NetAdapterAdvancedProperty -Name "your_adapter_name_from_guest_os" -
DisplayName "Maximum Number of RSS Queues" -DisplayValue "8 Queues"

NOTE: In the locations where there are settings for the number of queues, that value can be
anything from 1 to 16. If you want more total throughput, increase the number of queues. When
updating the number of queues, you must set IovQueuePairsRequested to a value that is equal to
or greater than the number of queues you want to use in the VM.

4.20.3 Transmit Balancing

Some Intel® Ethernet 800 Series devices allow you to enable a transmit balancing feature to improve
transmit performance under certain conditions. When the feature is enabled, you should experience more
consistent transmit performance across queues and/or PFs and VFs.

By default, transmit balancing is disabled in the NVM. To enable this feature, use one of the following to
persistently change the setting for the device:
l Use the Ethernet Port Configuration Tool (EPCT) to enable the tx_balancing option. Refer to the
EPCT readme for more information.
l Enable the Transmit Balancing device setting in UEFI HII.
l Enable transmit balancing via Linux devlink. Refer to the Linux readme inside the driver tarball for
more information.

When the driver loads, it reads the transmit balancing setting from the NVM and configures the device
accordingly.

NOTE:
l The user selection for transmit balancing in EPCT, HII, or Linux devlink is persistent across
reboots. You must reboot the system for the selected setting to take effect.
l This setting is device wide.
l The driver, NVM, and DDP package must all support this functionality to enable the feature.

4.20.4 Performance Profile

Performance Profiles are supported on Intel® 10GbE adapters and allow you to quickly optimize the
performance of your Intel® Ethernet Adapter. Selecting a performance profile will automatically adjust
some Advanced Settings to their optimum setting for the selected application. For example, a standard

705831 58
Intel® Ethernet Adapters and Devices User Guide

server has optimal performance with only two RSS (Receive-Side Scaling) queues, but a web server
requires more RSS queues for better scalability.

To change this setting in Intel PROSet

You must install Intel PROSet to use Performance profiles.

Profiles l Standard Server – This profile is optimized for typical servers.

l Web Server – This profile is optimized for IIS and HTTP-based web servers.
l Virtualization Server – This profile is optimized for Microsoft’s Hyper-V virtualization
environment.
l Storage Server – This profile is optimized for Fibre Channel over Ethernet or for
iSCSI over DCB performance. Selecting this profile will disable SR-IOV and VMQ.
l Storage + Virtualization – This profile is optimized for a combination of storage and
virtualization requirements.
l Low Latency – This profile is optimized to minimize network latency.

NOTES:
l Not all options are available on all adapter/operating system combinations.
l If you have selected the Virtualization Server profile or the Storage + Virtualization profile,
and you uninstall the Hyper-V role, you should select a new profile.

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Profile" -DisplayValue
"Standard Server"

Teaming Considerations

When you create a team with all members of the team supporting Performance Profiles, you will be asked
which profile to use at the time of team creation. The profile will be synchronized across the team. If there
is not a profile that is supported by all team members then the only option will be Use Current Settings.
The team will be created normally. Adding an adapter to an existing team works in much the same way.

If you attempt to team an adapter that supports performance profiles with an adapter that doesn't, the
profile on the supporting adapter will be set to Custom Settings and the team will be created normally.

This feature is not configurable through Intel PROSet ACU. On Microsoft Windows Server 2019, Microsoft
Windows* 10 Version 1809, and later, use Windows PowerShell.

4.21 Power Options

The Power Management tab in the device's Device Manager property sheet or the Adapter Settings panel in
Intel PROSet ACU includes several settings that control the device's power consumption. For example, you
can set the adapter to reduce its power consumption if the cable is disconnected.

705831 59
Intel® Ethernet Adapters and Devices User Guide

4.21.1 ACPI Power States

Advanced Configuration and Power Interface (ACPI) supports a variety of power states. Each state
represents a different level of power, from fully powered up to completely powered down, with partial levels
of power in each intermediate state.

The following table describes the ACPI power states.

Power
State Description

S0 On and fully operational

S1 System is in low-power mode (sleep mode). The CPU clock is stopped, but RAM is powered on and being
refreshed.

S2 Similar to S1, but power is removed from the CPU.

S3 Suspend to RAM (standby mode). Most components are shut down. RAM remains operational.

S4 Suspend to disk (hibernate mode). The memory contents are swapped to the disk drive and then reloaded into
RAM when the system is awakened.

S5 Power off

Microsoft Windows Server is ACPI-capable. It does not support waking from a power-off (S5) state, only
from standby (S3) or hibernate (S4). When shutting down the system, these states shut down ACPI
devices, including Intel Ethernet adapters. This disarms the adapter's remote wake-up capability.
However, in some ACPI-capable computers, the BIOS may have a setting that allows you to override the
operating system and wake from an S5 state anyway. If there is no support for wake from S5 state in your
BIOS settings, you are limited to Wake From Standby when using these operating systems in ACPI
computers.

4.21.2 Wake on LAN (WoL) Options

The ability to remotely wake computers is an important development in computer management. This
feature has evolved from a simple remote power-on capability to a complex system interacting with a
variety of device and operating system power states.

The Intel PROSet Power Management tab or the Adapter Settings panel in Intel PROSet ACU includes
Wake on Magic Packet and Wake on directed packet settings. These control the type of packets that
wake up the system from standby.

For some adapters, the Power Management tab in Intel PROSet or the Adapter Settings panel in Intel
PROSet ACU includes a setting called Wake on Magic Packet from power off state. Enable this setting
to explicitly allow wake-up with a Magic Packet* from shutdown under APM power management mode.

NOTES:
l To use the Wake on Directed Packet feature, WoL must first be enabled in the EEPROM using
BootUtil.
l If Reduce speed during standby is enabled, then Wake on Magic Packet and/or
Wake on directed packet must be enabled. If both of these options are disabled, power is
removed from the adapter during standby.
l Wake on Magic Packet from power off state has no effect on this option.

705831 60
Intel® Ethernet Adapters and Devices User Guide

4.21.2.1 WoL Supported Devices

All devices support Wake on LAN on all ports, with the exceptions listed in the following table:

Family Device Adapter Port(s) supporting WoL

Intel Ethernet Intel® Ethernet Network Adapter E810-2C-Q2 Do not support WoL
800 Series
Intel® Ethernet Network Adapter E810-C-Q2

Intel® Ethernet Network Adapter E810-C-Q2T

Intel® Ethernet Network Adapter E810-XXV-4

Intel® Ethernet Network Adapter E810-XXV-4T

Intel® Ethernet Network Adapter E810-XXV-2

Intel Ethernet Intel® Ethernet Network Adapter I710-T4L for Do not support WoL
700 Series OCP 3.0

Intel® Ethernet Network Adapter I710-T4L

Intel® Ethernet Converged Network Adapter

X710-2

Intel® Ethernet Converged Network Adapter

X710-4

Intel® Ethernet Converged Network Adapter

X710-T4

Intel® Ethernet Converged Network Adapter

X710

Intel® Ethernet Converged Network

Adapter XL710-Q1

Intel® Ethernet Converged Network Adapter

XL710-Q2

Intel® Ethernet Network Adapter X710-T2L

Intel® Ethernet Network Adapter X710-T4L

Intel® Ethernet Network Adapter X710-TL

Intel Ethernet Intel® Ethernet Server Adapter X520-2 Do not support WoL
500 Series
Intel® Ethernet Server Adapter X520-1 Note: Most Intel 10GbE Network Adapters do
not support Wake on LAN on any port.
Intel® Ethernet Server Adapter X540-T1
The following 10GbE Network Adapters do
Intel® Ethernet Converged Network Adapter support Wake on LAN on all ports:
X540-T2
l Intel® Ethernet Server Adapter X550-
Intel® Ethernet Converged Network Adapter T2 for OCP
X540-T1
l Intel® Ethernet Server Adapter X550-
T1 for OCP

Intel Ethernet Intel® Ethernet Server Adapter I350-T2 Support WoL only on Port A
300 Series
Intel® Ethernet Server Adapter I350-T4

Intel® Ethernet Server Adapter I340-T2

Intel® Ethernet Server Adapter I340-T4

Intel® Ethernet Server Adapter I340-F4

705831 61
Intel® Ethernet Adapters and Devices User Guide

4.21.2.2 Wake from S0ix on Magic Packet

Enables this device to bring the system out of an S0ix power state when the device receives a Magic
Packet.

Range l Disabled
l Enabled

4.21.3 Reduce Power if Cable Disconnected & Reduce Link Speed During
Standby
Enables the adapter to reduce power consumption when the LAN cable is disconnected from the adapter
and there is no link. When the adapter regains a valid link, adapter power usage returns to its normal state
(full power usage).

The Hardware Default option is available on some adapters. If this option is selected, the feature is disabled
or enabled based on the system hardware.

Range The range varies with the operating system and adapter.

4.21.4 Ultra Low Power Mode When Cable is Disconnected

Enabling Ultra Low Power (ULP) mode significantly reduces power consumption when the network cable is
disconnected from the device.

NOTE: If you experience link issues when two ULP-capable devices are connected back to back,
disable ULP mode on one of the devices.

4.21.5 Selective Suspend

Enables the device to enter a low power state when the network is idle.

Range l Disabled
l Enabled

4.21.6 Selective Suspend Idle Timeout

Sets the length of time that the network is idle before the device enters a low power state. You must
enable Selective Suspend for this setting to take effect.

Range 1 - 60 in seconds

4.21.7 Energy Efficient Ethernet

The Energy Efficient Ethernet (EEE) feature allows a capable device to enter Low-Power Idle between
bursts of network traffic. Both ends of a link must have EEE enabled for any power to be saved. Both ends
of the link will resume full power when data needs to be transmitted. This transition may introduce a small
amount of network latency.

705831 62
Intel® Ethernet Adapters and Devices User Guide

NOTES:
l Both ends of the EEE link must automatically negotiate link speed.
l EEE is not supported on every adapter.

4.22 Priority & VLAN Tagging

Enables the adapter to offload the insertion and removal of priority and VLAN tags for transmit and receive.

To change this setting in Intel PROSet

Range l Priority & VLAN Disabled

l Priority Enabled
l VLAN Enabled
l Priority & VLAN Enabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To set this in Windows Powershell, first disable DCB, then set priority and VLAN tagging. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "DCB" -DisplayValue
"Disabled"
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Packet Priority & VLAN" -
DisplayValue "VLAN Enabled"

4.23 Quality of Service

Quality of Service (QoS) allows the adapter to send and receive IEEE 802.3ac tagged frames. 802.3ac
tagged frames include 802.1p priority-tagged frames and 802.1Q VLAN-tagged frames. In order to
implement QoS, the adapter must be connected to a switch that supports and is configured for QoS.
Priority-tagged frames allow programs that deal with real-time events to make the most efficient use of
network bandwidth. High priority packets are processed before lower priority packets.

To change this setting in Intel PROSet

Tagging is enabled and disabled using the following fields:

l Windows Server: Use the "QoS Packet Tagging" field in the Advanced tab in Intel PROSet or in the
Adapter Settings panel in Intel PROSet ACU
l Other versions of Windows: Use the "Priority/VLAN Tagging" setting on the Advanced tab in Intel
PROSet or in the Adapter Settings panel in Intel PROSet ACU

To set this in Windows Powershell, first disable DCB, then set QoS using the Priority and VLAN tagging
DisplayName in the cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "DCB" -DisplayValue
"Disabled"
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Packet Priority & VLAN" -
DisplayValue "VLAN Enabled"

Once QoS is enabled, you can specify levels of priority based on IEEE 802.1p/802.1Q frame tagging.

705831 63
Intel® Ethernet Adapters and Devices User Guide

The supported operating systems, including Windows Server, have a utility for 802.1p packet prioritization.
For more information, see the Windows system help and Microsoft's knowledge base.

NOTE: The first generation Intel® PRO/1000 Gigabit Server Adapter (PWLA 8490) does not
support QoS frame tagging.

4.24 Receive Buffers

Defines the number of Receive Buffers, which are data segments. They are allocated in the host memory
and used to store the received packets. Each received packet requires at least one Receive Buffer, and each
buffer uses 2KB of memory.

You might choose to increase the number of Receive Buffers if you notice a significant decrease in the
performance of received traffic. If receive performance is not an issue, use the default setting appropriate
to the adapter.

To change this setting in Intel PROSet

Range 128-4096, in intervals of 64, for all adapters.

Recommended Value Teamed adapter: 256

Using IPSec and/or multiple features: 352

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Receive Buffers" -
DisplayValue "256"

4.25 Receive Side Scaling

When Receive Side Scaling (RSS) is enabled, all of the receive data processing for a particular TCP
connection is shared across multiple processors or processor cores. Without RSS all of the processing is
performed by a single processor, resulting in less efficient system cache utilization.

4.25.1 LAN RSS

LAN RSS applies to a particular TCP connection.

NOTE: This setting has no effect if your system has only one processing unit.

4.25.1.1 LAN RSS Configuration

If your adapter does not support RSS, or if the SNP or SP2 is not installed, the RSS setting will not be
displayed. If RSS is supported in your system environment, the following will be displayed:

705831 64
Intel® Ethernet Adapters and Devices User Guide

l Port NUMA Node. This is the NUMA node number of a device.

l Starting RSS CPU. This setting allows you to set the preferred starting RSS processor. Change this
setting if the current processor is dedicated to other processes. The setting range is from 0 to the
number of logical CPUs - 1.
l Max number of RSS CPU. This setting allows you to set the maximum number of CPUs assigned
to an adapter and is primarily used in a Hyper-V environment. By decreasing this setting in a Hyper-
V environment, the total number of interrupts is reduced which lowers CPU utilization. The default
is 8 for Gigabit adapters and 16 for 10 Gigabit, or faster, adapters.
l Preferred NUMA Node. This setting allows you to choose the preferred NUMA (Non-Uniform
Memory Access) node to be used for memory allocations made by the network adapter. In addition,
the system will attempt to use the CPUs from the preferred NUMA node first for the purposes of
RSS. On NUMA platforms, memory access latency is dependent on the memory location. Allocation
of memory from the closest node helps improve performance. The Windows Task Manager shows
the NUMA Node ID for each processor.

NOTES:
l This setting only affects NUMA systems. It will have no effect on non-NUMA systems.
l Choosing a value greater than the number of NUMA nodes present in the system
selects the NUMA node closest to the device.

l Receive Side Scaling Queues. This setting configures the number of RSS queues, which
determine the space to buffer transactions between the network adapter and CPU(s).

To change this setting in Intel PROSet

Range l 1 queue is used when low CPU utilization is required.

l 2 queues are used when good throughput and low CPU utilization are required.
l 4 or more queues are used for applications that demand maximum throughput and
transactions per second.

NOTES:
l Not all settings are available on all adapters.
l 8, or more, queues are only available when Intel PROSet for Windows Device
Manager or Intel PROSet ACU is installed. If Intel PROSet is not installed, only
4 queues are available.
l Using 8 or more queues requires the system to reboot.

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Receive Side Scaling" -
DisplayValue "Enabled"

705831 65
Intel® Ethernet Adapters and Devices User Guide

4.25.1.2 LAN RSS and Teaming

l If RSS is not enabled for all adapters in a team, RSS will be disabled for the team.
l If an adapter that does not support RSS is added to a team, RSS will be disabled for the team.
l If you create a multi-vendor team, you must manually verify that the RSS settings for all adapters
in the team are the same.

4.26 Remote Direct Memory Access (RDMA)

Remote Direct Memory Access, or RDMA, allows a network device to transfer data directly to and from
application memory on another system, increasing throughput and lowering latency in certain networking
environments.
l Intel® Ethernet 800 Series devices support both iWARP and RoCEv2.
l Intel® Ethernet X722 Series devices only support iWARP.

The major difference is that iWARP performs RDMA over TCP, while RoCEv2 uses UDP.

On devices with RDMA capabilities, RDMA is supported on the following operating systems (refer to
"Supported Operating Systems" on page 2 for currently supported versions):
l Linux
l FreeBSD
l ESXi
l Windows Server

To avoid performance degradation from dropped packets, enable link level flow control or priority flow
control on all network interfaces and switches.

NOTES:
l On systems running a Microsoft Windows Server operating system, enabling *QoS/priority
flow control will disable link level flow control.
l Devices based on the Intel® Ethernet 800 Series do not support RDMA when operating in
multiport mode with more than 4 ports.
l On Linux systems, RDMA and link aggregation (LAG, also known as bonding) are not
compatible on most devices. If RDMA is enabled, bonding will not be functional.
l On Intel Ethernet 810 Series devices, RDMA and LAG are compatible if all the
following are true:
l RDMA technology is set to RoCEv2.
l LAG configuration is active-backup.
l Bonding is between two ports within the same device.
l The QoS configuration of the two ports matches prior to the bonding of the
devices.

4.26.1 RDMA on Linux or FreeBSD

For Intel Ethernet devices that support RDMA on Linux or FreeBSD, use the drivers shown in the following
table.

705831 66
Intel® Ethernet Adapters and Devices User Guide

Linux FreeBSD

Device Base Driver RDMA Driver Base Driver RDMA Driver Supported Protocols

Intel® Ethernet 800 Series ice irdma ice irdma RoCEv2, iWARP

Intel® Ethernet X722 Series i40e irdma ixl not supported iWARP

Basic Installation Instructions

At a high level, installing and configuring RDMA on Linux or FreeBSD consists of the following steps. See
the README file inside the appropriate RDMA driver tarball for full details.

1. Install the base driver.

2. Install the RDMA driver.
3. Install and patch any user-mode RDMA libraries. Exact steps will vary by operating system; refer to
the RDMA driver readme for details.
4. Enable flow control on your device. Refer to the base driver README for details and supported
modes.
5. If you are using RoCE, enable flow control (PFC or LFC) on the device and endpoint your system is
connected to. See your switch documentation and, for Linux, the Intel® Ethernet 800 Series Linux
Flow Control Configuration Guide for RDMA Use Cases for details.

4.26.1.1 RDMA for Virtualized Environments in Linux

Devices based on the Intel Ethernet 800 Series support RDMA in a Linux VF on supported Windows or
Linux hosts. Refer to the README file inside the Linux RDMA driver tarball for more information on how to
load and configure RDMA in a Linux VF.

4.26.2 RDMA on Microsoft Windows

4.26.2.1 RDMA for Network Direct (ND) User-Mode Applications

Network Direct (ND) allows user-mode applications to use RDMA features.

NOTE: User mode applications may have prerequisites such as Microsoft HPC Pack or Intel MPI
Library, refer to your application documentation for more details.

RDMA User Mode Installation

The Intel® Ethernet User Mode RDMA Provider is supported on Microsoft Windows Server.

Follow the steps below to install user-mode Network Direct features.

1. Download the software package you want for the release. See "Install Drivers and Software" on
page 14 for more information.
A. If you are installing via the complete driver pack:
i. In the extracted files from the download, navigate to \APPS\PROSETDX and then the
Windows subfolder corresponding to your version of Windows (32-bit or 64-bit).
ii. Inside the Winx64 or Win32 folder, double-click on DxSetup.exe to launch the install
wizard.

705831 67
Intel® Ethernet Adapters and Devices User Guide

B. If you are installing via the separate webpacks for base drivers and Intel PROSet:
i. Download and extract the webpack for Intel PROSet.
ii. In the extracted files, double-click on the .exe file to launch the install wizard.
2. On the Setup Options screen, select "Intel® Ethernet User Mode RDMA Provider".
3. On the RDMA Configuration Options screen, select "Enable RDMA routing across IP Subnets" if
desired. Note that this option is displayed during base driver installation even if user mode RDMA
was not selected, as this option is applicable to Network Direct Kernel functionality as well.
4. If Windows Firewall is installed and active, select "Create an Intel® Ethernet RDMA Port Mapping
Service rule in Windows Firewall" and the networks to which to apply the rule.

NOTE: If Windows Firewall is disabled or you are using a third party firewall, you will need to
add this rule manually.

5. Continue with driver and software installation.

4.26.2.2 RDMA Network Direct Kernel (NDK)

RDMA Network Direct Kernel (NDK) functionality is included in the Intel base networking drivers and
requires no additional features to be installed.

RDMA Routing Across IP Subnets

If you want to allow NDK's RDMA functionality across subnets, you will need to select "Enable RDMA
routing across IP Subnets" on the RDMA Configuration Options screen during base driver installation.

4.26.2.3 Enabling Priority Flow Control (PFC) on a Microsoft Windows Server Oper-
ating System
To avoid performance degradation from dropped packets, enable priority flow control (PFC) or link level flow
control on all network interfaces and switches.

NOTE: On systems running a Microsoft Windows Server operating system, enabling *QoS/priority
flow control will disable link level flow control.

Use the following PowerShell commands to enable PFC on Microsoft Windows Server:
Install-WindowsFeature -Name Data-Center-Bridging -IncludeManagementTools
New-NetQoSPolicy "SMB" -NetDirectPortMatchCondition 445 -PriorityValue8021Action 3
Enable-NetQosFlowControl -Priority 3
Disable-NetQosFlowControl -Priority 0,1,2,4,5,6,7
New-NetQosTrafficClass -Name "SMB" -Priority 3 -BandwidthPercentage 60 -Algorithm ETS
Set-NetQosDcbxSetting -Willing $FALSE
Enable-NetAdapterQos -Name "Slot1 4 2 Port 1"

4.26.2.4 Verifying RDMA Operation with Microsoft PowerShell

You can check that RDMA is enabled on the network interfaces using the following Microsoft PowerShell
command:
Get-NetAdapterRDMA

Use the following PowerShell command to check if the network interfaces are RDMA capable and
multichannel is enabled:

705831 68
Intel® Ethernet Adapters and Devices User Guide

Get-SmbClientNetworkInterface

Use the following PowerShell command to check if Network Direct is enabled in the operating system:
Get-NetOffloadGlobalSetting | Select NetworkDirect

Use netstat to make sure each RDMA-capable network interface has a listener at port 445 (Windows Client
OSs that support RDMA may not post listeners). For example:
netstat.exe -xan | ? {$_ -match "445"}

4.26.2.5 RDMA for Virtualized Environments in Windows

To enable RDMA functionality on virtual adapter(s) connected to a VMSwitch, you must:
l Enable SR-IOV (Single Root IO Virtualization) and VMQ (Virtual Machine Queues) advanced
properties on each port.
l Set the number of VFs to enable with RDMA capabilities. You can enable up to 32 VFs with RDMA
capabilities.

Under certain circumstances, you may disable these settings by default. You can manually set these
options in the Adapter Settings panel of Intel PROSet ACU, in the Advanced tab of the adapter properties
dialog box, or with the following PowerShell commands:
Set-NetAdapterAdvancedProperty -Name <nic_name> -RegistryKeyword *SRIOV -RegistryValue 1
Set-NetAdapterAdvancedProperty -Name <nic_name> -RegistryKeyword *VMQ -RegistryValue 1
Set-NetAdapterAdvancedProperty -Name <nic_name> -RegistryKeyword RdmaMaxVfsEnabled -
RegistryValue <1-32>

4.26.2.6 Configuring RDMA Guest Support (NDK Mode 3)

NDK Mode 3 allows kernel mode Windows components to use RDMA features inside Hyper-V guest
partitions. To enable NDK mode 3 on an Intel Ethernet device, do the following:

1. Enable SR-IOV in your system's BIOS or uEFI.

2. Enable the SR-IOV advanced setting on the device.
3. Enable SR-IOV on the VMSwitch bound to the device by performing the following for all physical
functions on the same device:
New-VMSwitch -Name <switch_name> -NetAdapterName <device_name>
-EnableIov $true
4. Configure the number of RDMA virtual functions (VFs) on the device by setting the
"RdmaMaxVfsEnabled" advanced setting. All physical functions must be set to the same value. The
value is the maximum number of VFs that can be capable of RDMA at one time for the entire device.
Enabling more VFs will restrict RDMA resources from physical functions (PFs) and other VFs.
Set-NetAdapterAdvancedProperty -Name <device_name> -RegistryKeyword
RdmaMaxVfsEnabled -RegistryValue <Value: 0 - 32>
5. Disable all PF adapters on the host and re-enable them. This is required when the registry keyword
"RdmaMaxVfsEnabled" is changed or when creating or destroying a VMSwitch.
Get-NetAdapterRdma | Disable-NetAdapter
Get-NetAdapterRdma | Enable-NetAdapter
6. Create VM Network Adapters for VMs that require RDMA VF support.
Add-VMNetworkAdapter -VMName <vm_name> -VMNetworkAdapterName <device_name> -
SwitchName <switch_name>

705831 69
Intel® Ethernet Adapters and Devices User Guide

7. If you plan to use Microsoft Windows 10 Creators Update (RS2) or later on a guest partition, set the
RDMA weight on the VM Network Adapter by entering the following command on the host:
Set-VMNetworkAdapterRdma -VMName <vm_name> -VMNetworkAdapterName <device_name> -
RdmaWeight 100
8. Set SR-IOV weight on the VM Network Adapter (Note: SR-IOV weight must be set to 0 before
setting the RdmaWeight to 0):
Set-VMNetworkAdapter -VMName <vm_name> -VMNetworkAdapterName <device_name> -
IovWeight 100
9. Install the VF network adapter with the PROSET Installer in the VM.
10. Enable RDMA on the VF driver and Hyper-V Network Adapter using PowerShell in the VM:
Set-NetAdapterAdvancedProperty -Name <device_name> -RegistryKeyword RdmaVfEnabled -
RegistryValue 1
Get-NetAdapterRdma | Enable-NetAdapterRdma

4.26.2.7 RDMA for NDK Features such as SMB Direct (Server Message Block)
NDK allows Windows components (such as SMB Direct storage) to use RDMA features.

Testing NDK: Microsoft Windows SMB Direct with DiskSPD

This section outlines the recommended way to test RDMA for Intel Ethernet functionality and performance
on Microsoft Windows operating systems.

Note that since SMB Direct is a storage workload, the performance of the benchmark may be limited to the
speed of the storage device rather than the network interface being tested. Intel recommends using the
fastest storage possible in order to test the true capabilities of the network device(s) under test.

Test instructions:

1. Set up and connect at least two servers running a supported Microsoft Windows Server operating
system, with at least one RDMA-capable Intel® Ethernet device per server.
2. On the system designated as the SMB server, set up an SMB share. Note that the performance of
the benchmark may be limited to the speed of the storage device rather than the network interface
being tested. Storage setup is outside of the scope of this document. You can use the following
PowerShell command:
New-SmbShare -Name <SMBsharename> -Path <SMBsharefilepath> -FullAccess
<domainname>\Administrator,Everyone

For Example:
New-SmbShare -Name RAMDISKShare -Path R:\RAMDISK -FullAccess
group\Administrator,Everyone

3. Download and install the Diskspd Microsoft utility from here:

https://gallery.technet.microsoft.com/DiskSpd-a-robust-storage-6cd2f223
4. Using CMD or Powershell, cd to the DiskSpd folder and run tests. (Refer to Diskspd documentation
for more details on parameters)

For Example: Set the block size to 4K, run the test for 60 seconds, disable all hardware and software
caching, measure and display latency statistics, leverage 16 overlapped IOs and 16 threads per
target, random 0% writes and 100% reads and create a 10GB test file at
"\\<SMBserverTestIP>\<SMBsharename>\test.dat" :
.\diskspd.exe -b4K -d60 -h -L -o16 -t16 -r -w0 -c10G
\\<SMBserverTestIP>\<SMBsharename>\test.dat

705831 70
Intel® Ethernet Adapters and Devices User Guide

5. Verify that RDMA traffic is running using perfmon counters such as "RDMA Activity" and "SMB Direct
Connection". Refer to Microsoft documentation for more details.

4.26.2.8 RDMA Windows Performance Monitoring

You can use perfmon, or other performance monitoring tool, to monitor and display RDMA counters and
statistics. Refer to Microsoft documentation for more details. Use the Register-
IntelEthernetRDMACounterSet cmdlet registers the RDMA statistics counters for the specific device with
perfmon. Refer to "Configuring with Windows PowerShell" on page 21 for more information about how to
install and use Intel Ethernet cmdlets. You can use the following PowerShell command to register the
RDMA statistics for all supported devices:
Register-IntelEthernetRDMACounterSet

You can use the following PowerShell cmdlet to unregister the RDMA statistics:
Unregister-IntelEthernetRDMACounterSet

4.26.3 Accessing Remote NVM Express* Drives Using RDMA

RDMA provides a high throughput, low latency means to directly access NVM Express* (NVMe*) drives on a
remote server.

Refer to the following for details on supported operating systems and how to set up and configure your
server and client systems:
l NVM Express over TCP for Intel® Ethernet Products Configuration Guide
l NVM Express over Fabrics for Intel® Ethernet Products with RDMA Configuration Guide

Both guides are available on the Intel Technical Library.

4.27 Setting Speed and Duplex

The Link Speed and Duplex setting lets you choose how the adapter sends and receives data packets over
the network.

In the default mode, an Intel network adapter using copper connections will attempt to auto-negotiate
with its link partner to determine the best setting. If the adapter cannot establish link with the link partner
using auto-negotiation, you may need to manually configure the adapter and link partner to the identical
setting to establish link and pass packets. This should only be needed when attempting to link with an older
switch that does not support auto-negotiation or one that has been forced to a specific speed or duplex
mode.

Auto-negotiation is disabled by selecting a discrete speed and duplex mode in the adapter properties sheet.
The settings available when auto-negotiation is disabled are dependent on your device. Not all speeds are
available on all devices. Your link partner must match the setting you choose.

705831 71
Intel® Ethernet Adapters and Devices User Guide

NOTES:
l Only experienced network administrators should force speed and duplex manually.
l Fiber-based adapters operate only in full duplex at their native speed. You cannot change
the speed or duplex of Intel adapters that use fiber cabling.
l Some devices may list 10 Mbps and 100 Mbps in full or half duplex as options. These settings
are not recommended.
l Link speed information in Intel PROSet may display a blue informational icon with a mouse-
over message "This device is not linked at its maximum capable speed". In that case, if your
device is set to auto-negotiate, you can adjust the speed of the device's link partner to the
device's maximum speed. If the device is not set to auto-negotiate, you can adjust the
device's speed manually, but you must ensure the link partner is set at the same speed.
l Auto-negotiation and Auto-Try are not supported on devices based on the Intel® Ethernet
Connection X552 and Intel® Ethernet Connection X553.

4.27.1 Manually Configuring Duplex and Speed Settings

CAUTION: The settings at the switch must always match the adapter settings. Adapter performance may suf-
fer, or your adapter might not operate correctly if you configure the adapter differently from your switch.

The default setting is for auto-negotiation to be enabled. Only change this setting to match your link
partner's speed and duplex setting if you are having trouble connecting.

To change this setting in Intel PROSet

In Intel PROSet for Windows Device Manager:

1. In Windows Device Manager, double-click the adapter you want to configure.

2. On the Link Speed tab, select a speed and duplex option from the Speed and Duplex drop-down
menu.
3. Click OK.

In Intel PROSet ACU, link speed is reported on the Adapter Information panel. Change speed and duplex in
the Adapter Settings panel.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Speed & Duplex" -
DisplayValue "Auto Negotiation"

4.28 Thermal Monitoring

Adapters and network controllers based on the Intel® Ethernet Controller I350 (and later controllers) can
display temperature data and automatically reduce the link speed if the controller temperature gets too
hot.

NOTE: This feature is enabled and configured by the equipment manufacturer. It is not available
on all adapters and network controllers. There are no user configurable settings.

705831 72
Intel® Ethernet Adapters and Devices User Guide

4.28.1 Monitoring and Reporting

Temperature information is displayed on the Link tab in Intel PROSet for Windows Device Manager or in the
Adapter Information panel in Intel PROSet ACU. There are three possible conditions:
l Temperature: Normal
Indicates normal operation.
l Temperature: Overheated, Link Reduced
Indicates that the device has reduced link speed to lower power consumption and heat.
l Temperature: Overheated, Adapter Stopped
Indicates that the device is too hot and has stopped passing traffic so it is not damaged.

If either of the overheated events occur, the device driver writes a message to the system event log.

4.29 Timestamps

4.29.1 PTP Hardware Timestamp

Allows applications that use PTPv2 (Precision Time Protocol) to use hardware generated timestamps to
synchronize clocks throughout your network. If this setting is enabled, it takes precedence over the
Software Timestamp setting.

To change this setting in Intel PROSet

Range l Enabled
l Disabled

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "PTP Hardware Timestamp" -
DisplayValue "Enabled"

4.29.2 Software Timestamp

Allows applications that use PTPv2 (Precision Time Protocol) to use software generated timestamps to
synchronize clocks throughout your network. If the PTP Hardware Timestamp setting is enabled, it takes
precedence over this setting.

To change this setting in Intel PROSet

Range l Disabled
l RxAll
l TxAll
l RxAll & TxAll
l TaggedTx
l RxAll & TaggedTx

705831 73
Intel® Ethernet Adapters and Devices User Guide

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Software Timestamp" -
DisplayValue "RxAll"

4.30 Transmit Buffers

Defines the number of Transmit Buffers, which are data segments that enable the adapter to track
transmit packets in the system memory. Depending on the size of the packet, each transmit packet
requires one or more Transmit Buffers.

You might choose to increase the number of Transmit Buffers if you notice a possible problem with
transmit performance. Although increasing the number of Transmit Buffers can enhance transmit
performance, Transmit Buffers do consume system memory. If transmit performance is not an issue, use
the default setting. This default setting varies with the type of adapter.

To change this setting in Intel PROSet

Range 128-16384, in intervals of 64, for 10 Gigabit Server Adapters.

128-4096, in intervals of 64, for all other adapters.

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Transmit Buffers" -
DisplayValue "128"

4.31 Virtualization Support

Virtualization makes it possible for one or more operating systems to run simultaneously on the same
physical system as virtual machines. This allows you to consolidate several servers onto one system, even
if they are running different operating systems. Intel® Network Adapters work with, and within, virtual
machines with their standard drivers and software.

NOTES:
l Some virtualization options are not available on some adapter/operating system
combinations.
l The jumbo frame setting inside a virtual machine must be the same, or lower than, the
setting on the physical port.
l When you attach a Virtual Machine to a tenant overlay network through the Virtual NIC
ports on a Virtual Switch, the encapsulation headers increase the Maximum Transmission
Unit (MTU) size on the virtual port. The Encapsulation Overhead feature automatically
adjusts the physical port's MTU size to compensate for this increase.

705831 74
Intel® Ethernet Adapters and Devices User Guide

4.31.1 Single Root I/O Virtualization (SR-IOV)

4.31.1.1 SR-IOV Overview

Single Root I/O Virtualization (SR-IOV) is a PCI SIG specification allowing PCI Express devices to appear as
multiple separate physical PCI Express devices. SR-IOV allows efficient sharing of PCI devices among
Virtual Machines (VMs). It manages and transports data without the use of a hypervisor by providing
independent memory space, interrupts, and DMA streams for each virtual machine.

SR-IOV architecture includes two functions:

l Physical Function (PF) is a full featured PCI Express function that can be discovered, managed and
configured like any other PCI Express device.
l Virtual Function (VF) is similar to PF but cannot be configured and only has the ability to transfer
data in and out. The VF is assigned to a Virtual Machine.

SR-IOV Benefits
SR-IOV has the ability to increase the number of virtual machines supported per physical host, improving
I/O device sharing among virtual machines for higher overall performance:
l Provides near native performance due to direct connectivity to each VM through a virtual function
l Preserves VM migration
l Increases VM scalability on a virtualized server
l Provides data protection

705831 75
Intel® Ethernet Adapters and Devices User Guide

4.31.1.2 Configuring SR-IOV

SR-IOV lets a single network port appear to be several virtual functions in a virtualized environment. If you
have an SR-IOV capable NIC, each port on that NIC can assign a virtual function to several guest partitions.
The virtual functions bypass the Virtual Machine Manager (VMM), allowing packet data to move directly to a
guest partition's memory, resulting in higher throughput and lower CPU utilization. SR-IOV also allows you
to move packet data directly to a guest partition's memory. See your operating system documentation for
system requirements.

For devices that support it, SR-IOV is enabled in the host partition. Some devices may need to have SR-IOV
enabled in a preboot environment.

NOTES:
l Configuring SR-IOV for improved network security: In a virtualized environment, on
Intel® Server Adapters that support SR-IOV or Intel® Scalable I/O Virtualization (Intel®
Scalable IOV), the virtual function (VF) may be subject to malicious behavior. Software-
generated layer two frames, like IEEE 802.3x (link flow control), IEEE 802.1Qbb (priority
based flow-control), and others of this type, are not expected and can throttle traffic
between the host and the virtual switch, reducing performance. To resolve this issue, and to
ensure isolation from unintended traffic streams, configure all SR-IOV or Intel Scalable IOV
enabled ports for VLAN tagging from the administrative interface on the PF. This
configuration allows unexpected, and potentially malicious, frames to be dropped.
l SR-IOV must be enabled in the BIOS.
l You must enable VMQ for SR-IOV to function.
l For best performance, on the host use 'Set-VMNetworkAdapter -IovQueuePairsRequested 4'
on the VF to allow the virtual network to use 4 queues (maximum supported value) and
assign 4 or more virtual CPUs to the connected VM. In the VM, set 'Maximum number of
Receive Queues" in the VF's adapter properties to 4.
l Binding more than two virtual functions (VFs) to a virtual machine (VM) is not
recommended. Binding more VFs to a VM may cause system instability.
l SR-IOV is not supported with Intel ANS teams.
l VMWare ESXi does not support SR-IOV on 1GbE ports.

To change this setting in Intel PROSet

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "SR-IOV" -DisplayValue
"Enabled"

4.31.2 Intel® Scalable I/O Virtualization Support

Intel® Scalable I/O Virtualization (Intel® Scalable IOV) allows you to share a physical device across
multiple virtual machines and applications. Intel Scalable IOV provides your system the ability to share
device resources with different address domains using different abstractions. For example, application
processes may access a device using system calls and VMs may access a device through virtual device
interfaces.

705831 76
Intel® Ethernet Adapters and Devices User Guide

Intel Scalable IOV and SR-IOV (Single Root I/O Virtualization) are mutually exclusive. If both are enabled
on your system, and all of the Intel Scalable IOV requirements are met, the PF driver will use Intel Scalable
IOV. If the Intel Scalable IOV requirements are not met, the PF driver will use SR-IOV.

For more information, please refer to the Intel Scalable I/O Virtualization Technical Specification (login
required).

Intel Scalable IOV is not available in the kernel driver. Download and install the current driver to use this
feature. Refer to the Customer Support section for where to download the current driver.

4.31.2.1 Requirements
l Your system platform must support Intel Scalable IOV
l A network device based on an Intel(R) Ethernet 800 Series controller
l The host operating system must be a Linux distro using kernel version 5.12 - 5.15
l The host PF driver must be version 1.9.0, or later
l The guest operating system must be Linux
l The guest iAVF driver must be version 4.5.0, or later

4.31.2.2 Enabling Intel ® Scalable IOV

You can use Intel's Ethernet Port Configuration Tool (EPCT) to enable Intel Scalable IOV. If the EPCT tool is
not available, you can also enable Intel Scalable IOV through your system's HII interface (if it has one). The
recommended method is to use the EPCT tool. To enable or disable Intel Scalable IOV using the EPCT tool,
use one of these commands:

# epct -nic=1 -set 'siov enable'

# epct -nic=1 -set 'siov disable'

Where -nic=1 specifies the Intel Ethernet device. See the EPCT tool documentation for
instructions on how to determine the NIC number of your device.

If the EPCT tool is not available, and your system has an HII interface, you can use the HII interface to
enable/disable Intel Scalable IOV. Find the 'Intel Scalable IOV (Scalable IOV)' setting and select your
desired value.

4.31.3 Virtual Machine Queue Offloading

Enabling VMQ offloading increases receive and transmit performance, as the adapter hardware is able to
perform these tasks faster than the operating system. Offloading also frees up CPU resources. Filtering is
based on MAC and/or VLAN filters.

Each Intel® Ethernet Adapter has a pool of virtual ports that are split between the various features, such
as VMQ Offloading, SR-IOV, and Data Center Bridging (DCB). Increasing the number of virtual ports used
for one feature decreases the number available for other features. On devices that support it, enabling DCB
reduces the total pool available for other features to 32.

NOTE: This does not apply to devices based on the Intel® Ethernet X710 or XL710 controllers.

For devices that support it, VMQ offloading is enabled in the host partition in the Adapter Settings panel in
Intel PROSet Adapter Configuration Utility or on the Advanced tab of the adapter's Device Manager
property sheet, under Virtualization properties. Virtualization properties also displays the number of virtual

705831 77
Intel® Ethernet Adapters and Devices User Guide

ports available for virtual functions, and allows you to set the distribution of available virtual ports between
VMQ and SR-IOV.

4.31.3.1 Teaming Considerations

l If VMQ is not enabled for all adapters in a team, VMQ will be disabled for the team.
l If an adapter that does not support VMQ is added to a team, VMQ will be disabled for the team.
l Virtual NICs cannot be created on a team with Receive Load Balancing enabled. Receive Load
Balancing is automatically disabled if you create a virtual NIC on a team.
l If a team is bound to a Hyper-V virtual NIC, you cannot change the Primary or Secondary adapter.

4.31.3.2 Virtual Machine Multiple Queues

Virtual Machine Multiple Queues (VMMQ) enables Receive Side Scaling (RSS) for virtual ports attached to a
physical port. This allows RSS to be used with SR-IOV and inside a VMQ virtual machine, and offloads the
RSS processing to the network adapter. RSS balances receive traffic across multiple CPUs or CPU cores.
This setting has no effect if your system has only one processing unit.

4.31.4 Using Intel® Network Adapters in a Microsoft* Hyper-V* Envir-

onment
When a Hyper-V Virtual NIC (VNIC) interface is created in the host OS, the VNIC takes on the MAC address
of the underlying physical NIC (PF, or physical function). The same is true when a VNIC is created on a
team or VLAN. Since the VNIC uses the MAC address of the underlying interface, any operation that
changes the MAC address of the interface (for example, setting LAA on the interface), will cause the VNIC
to lose connectivity. In order to prevent this loss of connectivity, Intel PROSet will not allow you to change
settings that change the MAC address.

NOTES:
l When sent from inside a virtual machine, LLDP and LACP packets may be a security risk. The
Intel® Virtual Function driver blocks the transmission of such packets.
l The Virtualization setting on the Advanced tab of the adapter's Device Manager property
sheet is not available if the Hyper-V role is not installed.

4.31.4.1 The Virtual Machine Switch

The virtual machine switch is part of the network I/O data path. It sits between the physical NIC and the
virtual machine NICs and routes packets to the correct MAC address. Enabling Virtual Machine Queue
(VMQ) offloading in Intel PROSet will automatically enable VMQ in the virtual machine switch. For driver-
only installations, you must manually enable VMQ in the virtual machine switch.

NOTE: Intel ANS VLANs are not compatible with the Microsoft Hyper-V virtual machine switch. If
you want to bind the virtual machine switch to a VLAN, you must create the VLAN from within the
Virtual Switch Manager.

4.31.4.2 Using Intel ANS VLANs

If you create Intel ANS VLANs in the host OS, and you then create a Hyper-V Virtual NIC interface on an
Intel ANS VLAN, then the Virtual NIC interface must have the same VLAN ID as the VLAN. Using a

705831 78
Intel® Ethernet Adapters and Devices User Guide

different VLAN ID or not setting a VLAN ID on the Virtual NIC interface will result in loss of communication
on that interface.

Virtual Switches bound to an Intel ANS VLAN will have the same MAC address as the VLAN, which will have
the same address as the underlying NIC or team. If you have several VLANs bound to a team and bind a
virtual switch to each VLAN, all of the virtual switches will have the same MAC address. Clustering the
virtual switches together will cause a network error in Microsoft’s cluster validation tool. In some cases,
ignoring this error will not impact the performance of the cluster. However, such a cluster is not supported
by Microsoft. Using Device Manager to give each of the virtual switches a unique address will resolve the
issue. See the Microsoft TechNet article Configure MAC Address Spoofing for Virtual Network Adapters for
more information.

Virtual Machine Queues (VMQ) and SR-IOV cannot be enabled on a Hyper-V Virtual NIC interface bound to
a VLAN configured using the VLANs tab in Windows Device Manager.

4.31.4.3 Using an Intel ANS Team or VLAN as a Virtual NIC

If you want to use a team or VLAN as a virtual NIC, you must follow these steps:

NOTES:
l This applies only to virtual NICs created on a team or VLAN. Virtual NICs created on a
physical adapter do not require these steps.
l Receive Load Balancing (RLB) is not supported in Hyper-V. Disable RLB when using Hyper-
V.

1. Use Intel PROSet to create the team or VLAN.

2. Open the Network Control Panel.
3. Open the team or VLAN.
4. On the General Tab, uncheck all of the protocol bindings and click OK.
5. Create the virtual NIC. (If you check the "Allow management operating system to share the
network adapter." box you can do the following step in the host OS.)
6. Open the Network Control Panel for the Virtual NIC.
7. On the General Tab, check the protocol bindings that you desire.

NOTE: This step is not required for the team. When the Virtual NIC is created, its protocols
are correctly bound.

4.31.4.4 Command Line for Microsoft Windows Server Core

Microsoft Windows Server Core does not have a GUI interface. If you want to use an Intel ANS Team or
VLAN as a Virtual NIC, you must use Microsoft Windows PowerShell to set up the configuration. Use
Windows PowerShell to create the team or VLAN.

The following is an example of how to set up the configuration using Microsoft Windows PowerShell.

1. Get all the adapters on the system and store them into a variable.

$a = Get-IntelNetAdapter

705831 79
Intel® Ethernet Adapters and Devices User Guide

2. Create a team by referencing the indexes of the stored adapter array.

New-IntelNetTeam -TeamMembers $a[1],$a[2] -TeamMode

VirtualMachineLoadBalancing -TeamName “Team1”

4.32 Virtual LANs

4.32.1 Overview

NOTES:
l For more information on Intel ANS, refer to "Adapter Teaming" on page 25.
l Intel ANS is not supported on Microsoft Windows Server 2016 and later.
l Microsoft Windows 10 is the last Windows operating system version that supports Intel ANS.
Intel ANS is not supported on Microsoft Windows 11 and later.
l You must install the latest Microsoft Windows 10 updates before you can create Intel ANS
Teams or VLANs on Windows 10 systems. Any Intel ANS Teams or VLANs created with a
previous software/driver release on a Windows 10 system will be corrupted and cannot be
upgraded. The installer will remove these existing teams and VLANs.
l If you are running Windows 10 Anniversary edition (RS1) you will need to install Intel
LAN software v22.1 or newer.
l If you are running Windows 10 Creators Update (RS2) you will need to install Intel
LAN software v22.3 or newer.

NOTE: If you are running Windows 10 Creators Update (RS2) and are using
Intel LAN software release v22.1 or v22.2, then Intel ANS will not function
until you update to the Intel LAN software v22.3 or newer.

l Intel ANS VLANs are not compatible with Microsoft's Load Balancing and Failover (LBFO)
teams. Intel PROSet will block a member of an LBFO team from being added to an Intel ANS
VLAN. You should not add a port that is already part of an Intel ANS VLAN to an LBFO team,
as this may cause system instability.

The term VLAN (Virtual Local Area Network) refers to a collection of devices that communicate as if they
were on the same physical LAN. Any set of ports (including all ports on the switch) can be considered a
VLAN. LAN segments are not restricted by the hardware that physically connects them.

VLANs offer the ability to group computers together

into logical workgroups. This can simplify network
administration when connecting clients to servers
that are geographically dispersed across the building,
campus, or enterprise network.

Typically, VLANs consist of co-workers within the

same department but in different locations, groups
of users running the same network protocol, or a
cross-functional team working on a joint project.

By using VLANs on your network, you can:

705831 80
Intel® Ethernet Adapters and Devices User Guide

l Improve network performance

l Limit broadcast storms
l Improve LAN configuration updates (adds, moves, and changes)
l Minimize security problems
l Ease your management task

4.32.2 Other Considerations

l Configuring SR-IOV for improved network security: In a virtualized environment, on Intel®
Server Adapters that support SR-IOV or Intel® Scalable I/O Virtualization (Intel® Scalable IOV), the
virtual function (VF) may be subject to malicious behavior. Software-generated layer two frames,
like IEEE 802.3x (link flow control), IEEE 802.1Qbb (priority based flow-control), and others of this
type, are not expected and can throttle traffic between the host and the virtual switch, reducing
performance. To resolve this issue, and to ensure isolation from unintended traffic streams,
configure all SR-IOV or Intel Scalable IOV enabled ports for VLAN tagging from the administrative
interface on the PF. This configuration allows unexpected, and potentially malicious, frames to be
dropped.
l The VF is not aware of the VLAN configuration if you use LBFO to configure VLANs in a Windows
guest. VLANs configured using LBFO on a VF driver may result in failure to pass traffic. You must use
Windows Hyper-V on the host to configure VLANs on a Windows guest.
l Intel ANS VLANs are not compatible with the Microsoft Hyper-V virtual machine switch. If you want
to bind the virtual machine switch to a VLAN, you must create the VLAN from within the Virtual
Switch Manager.
l To set up IEEE VLAN membership (multiple VLANs), the adapter must be attached to a switch with
IEEE 802.1Q VLAN capability.
l A maximum of 64 VLANs per network port or team are supported by Intel software.
l Intel ANS VLANs can co-exist with Intel ANS teams (if the adapter supports both). If you do this, the
team must be defined first, then you can set up your VLAN.
l You can set up only one untagged VLAN per adapter or team. You must have at least one tagged
VLAN before you can set up an untagged VLAN.
l Jumbo Frames are not supported over Intel ANS VLANs under Microsoft Windows 10.

CAUTION: When using IEEE 802 VLANs, settings must match between the switch and those
adapters using the VLANs.

4.32.3 Configuring VLANs in Microsoft Windows

4.32.3.1 Using Intel PROSet for Windows Device Manager

This setting is found on the VLANs tab of the device's Device Manager property sheet or in the VLANs panel
in Intel PROSet Adapter Configuration Utility.

705831 81
Intel® Ethernet Adapters and Devices User Guide

CAUTION: Do not use the Network Connections dialog box to enable or disable
VLANs. Otherwise, the VLAN driver may not be correctly enabled or disabled.

NOTES:
l The VLAN ID keyword is supported. The VLAN ID must match the VLAN ID configured on
the switch. Adapters with VLANs must be connected to network devices that support IEEE
802.1Q.
l In most environments, a maximum of 64 VLANs per network port or team are supported
by Intel ANS.
l Intel ANS VLANs are not supported on adapters and teams that have VMQ enabled.
However, VLAN filtering with VMQ is supported via the Microsoft Hyper-V VLAN interface.
For more information, see Using Intel® Network Adapters in a Microsoft* Hyper-V*
Environment.
l You can have different VLAN tags on a child partition and its parent. Those settings are
separate from one another, and can be different or the same. The only instance where the
VLAN tag on the parent and child MUST be the same is if you want the parent and child
partitions to be able to communicate with each other through that VLAN. For more
information, see Using Intel® Network Adapters in a Microsoft* Hyper-V* Environment.

4.32.3.2 Using Windows PowerShell

To add a VLAN use the Add-IntelNetVLAN cmdlet. For example
Add-IntelNetVLAN -ParentName "Name" -VLANID "1"

To remove a VLAN use the Remove-IntelNetVLAN cmdlet. For example:

Remove-IntelNetVLAN -ParentName "Name" -VLANID "1"

4.32.3.3 Using Intel PROSet ACU

On the Teaming/VLANs tab, use the VLANs panel.

4.33 Wait for Link

Determines whether the driver waits for auto-negotiation to be successful before reporting the link state.
If this feature is off, the driver does not wait for auto-negotiation. If the feature is on, the driver does wait
for auto-negotiation.

If this feature is on and the speed is not set to auto-negotiation, the driver will wait for a short time for link
to be established before reporting the link state.

If the feature is set to Auto Detect, this feature is automatically set to On or Off depending on speed and
adapter type when the driver is installed. The setting is:
l Off for copper Intel gigabit adapters with a speed of "Auto"
l On for copper Intel gigabit adapters with a forced speed and duplex
l On for fiber Intel gigabit adapters with a speed of "Auto"

705831 82
Intel® Ethernet Adapters and Devices User Guide

To change this setting in Intel PROSet

Range l On
l Off
l Auto Detect

This setting is found on the Advanced tab of the device's Device Manager property sheet or in the Adapter
Settings panel in Intel PROSet Adapter Configuration Utility.

To change this setting in Windows PowerShell, use the Set-IntelNetAdapterSetting cmdlet. For example:
Set-IntelNetAdapterSetting -Name "<adapter_name>" -DisplayName "Wait for Link" -
DisplayValue "Off"

705831 83
Intel® Ethernet Adapters and Devices User Guide

5. Microsoft* Windows* Driver and Software Installation

and Configuration
This chapter explains the following in more detail:
l How to install device drivers on supported versions of Microsoft Windows
l How to save and restore a device's configuration settings

Refer to "About Intel PROSet®" on page 15 for an overview of this software, how to install it, and how to
use it to configure device features in Microsoft Windows.

5.1 Installing Windows Drivers and Software

There are multiple installation options:
l Install via the complete driver pack. This option will install Windows drivers and Intel PROSet but is a
very large download.
l Install device drivers and Intel PROSet software separately.
l Install device drivers or Intel PROSet via a command line interface.

NOTE: To successfully install or uninstall the drivers or software, you must have administrative
privileges on the computer completing installation.

This section describes how to install the base drivers. Refer to "Installing Intel PROSet" on page 17 for
additional instructions.

NOTES:
l This will update the drivers for all supported Intel® network adapters in your system.
l The Roll Back Driver feature of Windows Server (available on the Adapter Properties dialog's
Driver tab) will not work correctly if an adapter team or Intel PROSet are present on the
system. Before you use the Roll Back Driver feature, remove any teams. Then remove Intel
PROSet using Programs and Features from the Control Panel of Windows. See "Installing
Intel PROSet" on page 17 for details regarding Intel PROSet.
l Using Microsoft Windows Update to upgrade or downgrade your Ethernet network drivers is
not supported. Please download the latest driver package from the support website.

Before installing or updating the drivers, insert your adapter(s) in the computer and plug in the network
cable. When Windows discovers the new adapter, it attempts to find an acceptable Windows driver already
installed with the operating system.

If found, the driver is installed without any user intervention. If Windows cannot find the driver, the Found
New Hardware Wizard window is displayed.

Regardless of whether Windows finds the driver, it is recommended that you follow the procedures below
to install the driver. Drivers for all Intel adapters supported by this software release are installed.

5.1.1 Install via the Complete Driver Pack

To download and install via the complete driver pack:

705831 84
Intel® Ethernet Adapters and Devices User Guide

1. Download the latest software package from the support website and transfer it to the system.
2. Extract the downloaded software package to your hard drive.
3. If the Found New Hardware Wizard screen is displayed, click Cancel.
4. Navigate in your extracted files to \APPS\SETUPBD and then the Windows subfolder corresponding to
your version of Windows (32-bit or 64-bit).
5. Inside the Winx64 or Win32 folder, double-click on SetupBD.exe.
6. Complete the steps in the installation wizard.
7. If you want to install Intel PROSet, navigate to \APPS\PROSETDX and then the Windows subfolder
corresponding to your version of Windows (32-bit or 64-bit).
8. Inside the Winx64 or Win32 folder, double-click on DxSetup.exe.
9. Complete the steps in the installation wizard.

5.1.2 Install Only Windows Drivers

To download and install only Windows drivers:

1. Download and extract the Wired_driver_XX.X_*.zip file for your version of Windows, where XX.X
is the release number. This file will install the base driver(s) for your system.
l If you are running a 32-bit operating system, download Wired_driver_XX.X_32.zip.
l If you are running a 64-bit operating system, download Wired_driver_XX.X_x64.zip.
2. In the extracted driver files, double-click on the .exe file to launch the installation.
3. In the dialog box that opens, click on OK to install the drivers.
4. The device driver(s) will install. Click Close when prompted.

NOTE: This method does not install Intel PROSet. See "Installing Intel PROSet" on page 17 for
additional instructions.

5.1.3 Command Line Options for Installing Base Drivers

SetupBD.exe supports the following command line switches.

NOTE: You must include a space between switches.

Switch Description

/h Displays help file for SetupBD

/l Create a log file with the specified path and filename. If you do not specify the path and filename,
<path\filename> SetupBD creates a log file (named SetupBD_<timestamp>.log, for example SetupBD_18-04-2022_14-
29-20.log) in the current directory.

/m Non-interactive install. This still displays the installation GUI, but you cannot interact with it. Use the
/s switch to suppress the GUI.

/n Ignore INF excludes and force scan all .inf files.

705831 85
Intel® Ethernet Adapters and Devices User Guide

Switch Description

/nr No reboot (must be used with the /s switch. This switch is ignored if it is included with the /r switch)

/r Force reboot (must be used with the /s switch)

/s Silent install

Examples:

Option Description

SetupBD Installs and/or updates the driver(s) and displays the GUI.

SetupBD /s Installs and/or updates the driver(s) silently.

SetupBD /s /l c:\temp\install.log Installs and/or updates the driver(s) silently and creates a log file in c:\temp

SetupBD /s /r Installs and/or updates the driver(s) silently and forces a reboot.

SetupBD /s /r /nr Installs and/or updates the driver(s) silently and forces a reboot (/nr is ignored).

5.2 Saving and Restoring an Adapter's Configuration Settings

The Save and Restore Command Line Tool allows you to copy the current adapter and team settings into a
standalone file (such as on a USB drive) as a backup measure. In the event of a hard drive failure, you can
reinstate most of your former settings.

The system on which you restore network configuration settings must have the same configuration as the
one on which the save was performed. A saved configuration file can be used to restore adapter settings
after an operating system upgrade. However, all adapter configuration settings may not be restored
depending on the features supported by the new operating system or adapter configuration software.

NOTES:
l You must have Administrator privileges to run scripts. If you do not have Administrator
privileges, you will not receive an error, the script just will not run.
l Only adapter settings are saved (these include Intel ANS teaming and VLANs). The adapter's
driver is not saved.
l Restore using the script only once. Restoring multiple times may result in unstable
configuration.
l Intel PROSet must be installed for the SaveRestore.ps1 script to run.
l For systems running a 64-bit OS, be sure to run the 64-bit version of Windows PowerShell,
not the 32-bit (x86) version, when running the SaveRestore.ps1 script.

5.2.1 Command Line Syntax

SaveRestore.ps1 –Action save|restore [-ConfigPath] [-BDF]

SaveRestore.ps1 has the following command line options:

705831 86
Intel® Ethernet Adapters and Devices User Guide

Option Description

-Action Required. Valid values: save | restore.

The save option saves adapter and team settings that have been changed from the default settings. When
you restore with the resulting file, any settings not contained in the file are assumed to be the default.

The restore option restores the settings.

-ConfigPath Optional. Specifies the path and filename of the main configuration save file. If not specified, it is the script
path and default filename (saved_config.txt).

-BDF Optional. Default configuration file names are saved_config.txt and Saved_StaticIP.txt.

If you specify -BDF during a restore, the script attempts to restore the configuration based on the PCI
Bus:Device:Function:Segment values of the saved configuration. If you removed, added, or moved a NIC to
a different slot, this may result in the script applying the saved settings to a different device.

NOTES:
l If the restore system is not identical to the saved system, the script may not restore any settings
when the -BDF option is specified.
l Virtual Function devices do not support the -BDF option.

5.2.2 Examples

Save Example

To save the adapter settings to a file on a removable media device, do the following.

1. Open a Windows PowerShell Prompt.

2. Navigate to the directory where SaveRestore.ps1 is located (generally c:\Program
Files\Intel\Wired Networking\PROSET).
3. Type the following:
SaveRestore.ps1 –Action Save –ConfigPath e:\settings.txt

Restore Example

To restore the adapter settings from a file on removable media, do the following:

1. Open a Windows PowerShell Prompt.

2. Navigate to the directory where SaveRestore.ps1 is located (generally c:\Program
Files\Intel\Wired Networking\PROSET).
3. Type the following:
SaveRestore.ps1 –Action Restore –ConfigPath e:\settings.txt

705831 87
Intel® Ethernet Adapters and Devices User Guide

6. Remote Boot
Remote Boot allows you to boot a system using only an Ethernet adapter. You connect to a server that
contains an operating system image and use that to boot your local system.

6.1 Flash Images

"Flash" is a generic term for nonvolatile RAM (NVRAM), firmware, and option ROM (OROM). Depending on
the device, it can be on the NIC or on the system board.

NOTE: You cannot update the flash of a device in the "Pending Reboot" state. Reboot your system
before attempting to update the device's flash.

6.1.1 Updating the Flash in Microsoft Windows

Intel PROSet for Windows Device Manager can update the flash on an Intel Ethernet network adapter.
However, if you need to enable or disable the Boot ROM use BootUtil.

Intel PROSet for Windows Device Manager can only be used to program add-in Intel Ethernet network
adapters. LOM (LAN On Motherboard) network connections cannot be programmed with the UEFI network
driver option ROM.

6.1.1.1 Using Intel PROSet to flash the UEFI Network Driver Option ROM
Intel PROSet for Windows Device Manager can install the UEFI network driver on an Intel network
adapter's option ROM. The UEFI network driver will load automatically during system UEFI boot when
installed in the option ROM. UEFI specific *.FLB images are included in the downloaded release media. The
"Boot Options" tab in Intel PROSet for Windows Device Manager will allow the UEFI *.FLB image to be
installed on the network adapter.

6.1.2 Updating the Flash from Linux

The BootUtil command line utility can update the flash on an Intel Ethernet network adapter. Run BootUtil
with the following command line options to update the flash on all supported Intel network adapters. For
example, enter the following command line:

bootutil64e –up=efi –all

BootUtil can only be used to program add-in Intel network adapters. LOM (LAN On Motherboard) network
connections cannot be programmed with the UEFI network driver option ROM.

See the bootutil.txt file for details on using BootUtil.

6.1.3 Installing the UEFI Network Driver Option ROM from the UEFI Shell
The BootUtil command line utility can install the UEFI network driver on an Intel network adapter's option
ROM. The UEFI network driver will load automatically during system UEFI boot when installed into the
option ROM. For example, run BootUtil with the following command line options to install the UEFI network
driver on all supported Intel network adapters:

FS0:\>bootutil64e –up=efi –all

705831 88
Intel® Ethernet Adapters and Devices User Guide

BootUtil can only be used to program add-in Intel Ethernet network adapters. LOM (LAN On Motherboard)
network connections cannot be programmed with the UEFI network driver option ROM.

See the bootutil.txt file for details on using BootUtil.

6.2 Enable Remote Boot

If you have an Intel Desktop Adapter installed in your client computer, the flash ROM device is already
available in your adapter, and no further installation steps are necessary. For Intel Server Adapters, the
flash ROM can be enabled using the BootUtil utility. For example, from the command line type:

BOOTUTIL -E
BOOTUTIL -NIC=1 -FLASHENABLE

The first line will enumerate the ports available in your system. Choose a port. Then type the second line,
selecting the port you wish to enable. For more details, see the bootutil.txt file.

6.3 UEFI Network Device Driver for Intel® Ethernet Network Con-
nections

6.3.1 UEFI Network Stack

As of UEFI 2.1 there are two network stack configurations under UEFI. The most common configuration is
the PXE based network stack. The alternate network stack provides IPv4 TCP, UDP, and MTFTP network
protocol support. As of UEFI 2.1 the PXE and IP-based network stacks cannot be loaded or operate
simultaneously. The following two sections describe each UEFI network stack configuration.

Reference implementations of the PXE and IP based network stack source code are available for download
at www.tianocore.org.

6.3.2 Loading the UEFI Network Driver

The network driver can be loaded using the UEFI shell "load" command:
load e3040e2.efi

6.3.3 Configuring UEFI Network Stack for PXE

The PXE (Preboot eXecution Environment) based UEFI network stack provides support for UEFI network
boot loaders downloaded from a WFM compliant PXE server. Services which can be enabled include
Windows Deployment Services (WDS), Linux network installation (Elilo), and TFTP file transfers. To enable
UEFI PXE services the following network protocol drivers must be loaded with: snp.efi, bc.efi, and
pxedhcp4.efi. These drivers can be loaded from the UEFI "load" shell command, but are often included as
part of the UEFI system firmware. The UEFI shell command "drivers" can be used to determine if the UEFI
PXE drivers are included in the UEFI implementation. The drivers command will output a table listing
drivers loaded in the system. The following entries must be present in order to network boot a UEFI system
over PXE:

DRV VERSION TYPE CFG DIAG #D #C DRIVER NAME IMAGE NAME

F5 00000010 D - - 2 - Simple Network Protocol Driver SNP

F7 00000010 D - - 2 - PXE Base Code Driver BC

705831 89
Intel® Ethernet Adapters and Devices User Guide

F9 00000010 D - - 2 - PXE DHCPv4 Driver PxeDhcp4

FA 03004000 B X X 2 2 Intel(R) Network Connection 3.0.00 /e3000e2.efi

A network boot option will appear in the boot options menu when the UEFI PXE network stack and Intel
UEFI network driver have been loaded. Selecting this
boot option will initiate a PXE network boot.

6.3.4 Configuring UEFI Network Stack for TCP/UDP/MTFTP

An IP-based network stack is available to applications requiring IP-based network protocols such as TCP,
UDP, or MTFTP. The following UEFI network drivers must be built into the UEFI platform implementation to
enable this stack: SNP (Simple Network Protocol), MNP (Managed Network Protocol), ARP, DHCP4, IPv4,
ip4config, TCPv4, UDPv4, and MTFTPv4. These drivers will show up in the UEFI "drivers" command output
if they are included in the platform UEFI implementation:

DRV VERSION TYPE CFG DIAG #D #C DRIVER NAME IMAGE NAME

F5 00000010 D - - 2 - IP4 CONFIG Network Service Driver Ip4Config

F7 00000010 D - - 2 - Simple Network Protocol Driver SNP

F8 00000010 D - - 2 - ARP Network Service Driver Arp

F9 00000010 D - - 2 - Tcp Network Service Driver Tcp4

FA 00000010 D - - 2 - IP4 Network Service Driver Ip4

FB 00000010 D - - 2 - DHCP Protocol Driver Dhcp4

FC 00000010 D - - 6 - UDP Network Service Driver Udp4

FD 00000010 D - - 2 - MTFTP4 Network Service Mtftp4

FE 00000010 B - - 2 6 MNP Network Service Driver /mnp.efi

FF 03099900 B X X 2 2 Intel(R) Network Connection 3.0.00 /e3000e2.efi

The ifconfig UEFI shell command must be used to configure each network interface. Running "ifconfig -?"
from the UEFI shell will display usage instructions for ifconfig.

6.3.5 Unloading the UEFI Network Driver

To unload a network driver from memory the UEFI "unload" command is used. The syntax for using the
unload command is as follows: "unload [driver handle]", where driver handle is the number assigned to the
driver in the far left column of the "drivers" output screen.

6.3.6 Force Speed and Duplex

The UEFI network driver supports forced speed and duplex capability. The force speed and duplex menu
can be accessed with UEFI shell command "drvcfg":

drvcfg -s [driver handle] [control handle]

The following speed and duplex configurations can be selected:

705831 90
Intel® Ethernet Adapters and Devices User Guide

l Autonegotiate (recommended)
l 100 Mbps, full duplex
l 100 Mbps, half duplex
l 10 Mbps, full duplex
l 10 Mbps, half duplex

The speed and duplex setting selected must match the speed and duplex setting of the connecting network
port. A speed and duplex mismatch between ports will result in dropped packets and poor network
performance. It is recommended to set all ports on a network to autonegotiate. Connected ports must be
set to autonegotiate in order to establish a 1 gigabit per second connection.

Fiber-optic and 10 gigabit ethernet adapters do not support forced speed and duplex.

6.3.7 Diagnostic Capability

The UEFI network driver features built in hardware diagnostic tests. The diagnostic tests are called with the
UEFI shell drvdiag command.

drvdiag -s -Performs a basic hardware register test.

drvdiag -e -Performs an internal loopback transmit and receive test.

6.3.8 UEFI Known Issues

6.3.8.1 Long Initialization Times

Long initialization times observed with Intel’s UEFI driver are caused when the UNDI.Initialize command is
called with the PXE_OPFLAGS_INITIALIZE_CABLE_DETECT flag set. In this case, UNDI.Initialize will try to
detect the link state.

If the port is connected and link is up, initialize will generally finish in about 3.5 seconds (the time needed
to establish link, dependent on link conditions, link speed and controller type) and returns PXE_
STATFLAGS_COMMAND_COMPLETE. If the port is disconnected (link is down), initialize will complete in
about 5 seconds and return PXE_STATFLAGS_INIIALIZED_NO_MEDIA (driver initializes hardware then
waits for link and timeouts when link is not establish in 5 seconds).

When UNDI.Initialize is called with PXE_OPFLAGS_INITIALIZE_DO_NOT_DETECT_CABLE the function will

not try to detect link status and will take less than 1 second to complete.

The behavior of UNDI.Initialize is described in UEFI specs 2.3.1: Initializing the network device will take up
to four seconds for most network devices and in some extreme cases (usually poor cables) up to twenty
seconds. Control will not be returned to the caller and the COMMAND_COMPLETE status flag will not be set
until the adapter is ready to transmit.

6.4 Intel® Boot Agent

The Intel® Boot Agent is a software product that allows your networked client computer to boot using a
program code image supplied by a remote server. Intel Boot Agent complies with the Pre-boot eXecution
Environment (PXE) Version 2.1 Specification. It is compatible with legacy boot agent environments that
use BOOTP protocol.

6.4.1 Intel Boot Agent Client Configuration

The Intel Boot Agent software provides configuration options that allow you to customize the behavior of

705831 91
Intel® Ethernet Adapters and Devices User Guide

the Intel Boot Agent software. You can configure the Intel Boot Agent in any of the following
environments:
l A Microsoft Windows environment
l A preboot environment (before operating system is loaded)

The Intel Boot Agent supports PXE in preboot and Microsoft Windows environments. In each of these
environments, a single user interface allows you to configure PXE protocols on Intel Ethernet Adapters.

CAUTION: If spanning tree protocol is enabled on a switch port through which a

port is trying to use PXE, the delay before the port starts forwarding can cause a
DHCP timeout. Either disable spanning tree or turn on the feature that allows the
port to begin forwarding of packets immediately ('port fast learning' for Cisco
switches), rather than wait until the spanning tree discovery is complete.

6.4.1.1 Configuring the Intel® Boot Agent in a Microsoft Windows Environment

If you use the Windows operating system on your client computer, you can use Intel® PROSet for
Windows* Device Manager to configure and update the Intel Boot Agent software. Intel PROSet is available
through the device manager. Intel PROSet provides a special tab, called the Boot Options tab, used for
configuring and updating the Intel Boot Agent software.

To access the Boot Options tab:

1. Open Intel PROSet for Windows Device Manager by opening the System Control Panel. On the
Hardware tab, click Device Manager.

2. Select the appropriate adapter and click the Boot Options tab. If the tab does not appear, update
your network driver.

3. The Boot Options tab shows a list of current configuration parameters and their corresponding
values. Corresponding configuration values appear for the selected setting in a drop-down box.

4. Select a setting you want to change from the Settings selection box.

5. Select a value for that setting from the Value drop-down list.

6. Repeat the preceding two steps to change any additional settings.

7. Once you have completed your changes, click Apply Changes to update the adapter with the new
values.

6.4.1.2 Configuring the Intel® Boot Agent in a Preboot PXE Environment

NOTE: Intel Boot Agent may be disabled in the BIOS.

You can customize the behavior of the Intel Boot Agent software through a preboot (operating system
independent) configuration setup program contained within the adapter's flash ROM. You can access this
preboot configuration setup program each time the client computer cycles through the boot process.

When the boot process begins, the screen clears and the computer begins its Power On Self Test (POST)
sequence. Shortly after completion of the POST, the Intel Boot Agent software stored in flash ROM
executes. The Intel Boot Agent then displays an initialization message, similar to the one below, indicating
that it is active:

Initializing Intel(R) Boot Agent Version X.X.XX

705831 92
Intel® Ethernet Adapters and Devices User Guide

PXE 2.0 Build 083

NOTE: This display may be hidden by the manufacturer's splash screen. Consult your
manufacturer's documentation for details.

The configuration setup menu shows a list of configuration settings on the left and their corresponding
values on the right. Key descriptions near the bottom of the menu indicate how to change values for the
configuration settings. For each selected setting, a brief "mini-Help" description of its function appears just
above the key descriptions.

1. Highlight the setting you need to change by using the arrow keys.
2. Once you have accessed the setting you want to change, press the spacebar until the desired value
appears.
3. Once you have completed your changes, press F4 to update the adapter with the new values. Any
changed configuration values are applied as the boot process resumes.

The table below provides a list of configuration settings, their possible values, and their detailed
descriptions:

Configuration Setting Possible Values Description

Network Boot Protocol PXE (Preboot eXecution Select PXE for use with Network management programs,
Environment) such as LANDesk* Management Suite.

NOTE: Depending on the configuration of the Intel Boot

Agent, this parameter may not be changeable.

Boot Order Use BIOS Setup Boot Order Sets the boot order in which devices are selected during
boot up if the computer does not have its own control
Try network first, then local method.
drives
If your client computer's BIOS supports the BIOS Boot
Try local drives first, then Specification (BBS), or allows PnP-compliant selection of
network the boot order in the BIOS setup program, then this
setting will always be Use BIOS Setup Boot Order and
Try network only
cannot be changed. In this case, refer to the BIOS setup
Try local drives only manual specific to your client computer to set up boot
options.

If your client computer does not have a BBS- or PnP-

compliant BIOS, you can select any one of the other
possible values listed for this setting except for Use
BIOS Setup Boot Order.

Legacy OS Wakeup Support 0 = Disabled (Default Value) If set to 1, the Intel Boot Agent will enable PME in the
(For 82559-based adapter’s PCI configuration space during initialization.
adapters only) 1 = Enabled This allows remote wakeup under legacy operating
systems that don’t normally support it. Note that
enabling this makes the adapter technically non-
compliant with the ACPI specification, which is why the
default is disabled.

705831 93
Intel® Ethernet Adapters and Devices User Guide

NOTE: If, during PXE boot, more than one adapter is installed in a computer and you want to boot
from the boot ROM located on a specific adapter, you can do so by moving the adapter to the top of
the BIOS Boot Order or by disabling the flash on the other adapters.

While the configuration setup menu is displayed, diagnostics information is also displayed in the lower half
of the screen. This information can be helpful during interaction with Intel Customer Support personnel or
your IT team members. For more information about how to interpret the information displayed, refer to
Diagnostics Information for Preboot PXE Environments.

6.4.2 Intel Boot Agent Target/Server Setup

For the Intel Boot Agent software to perform its intended job, there must be a server set up on the same
network as the client computer. That server must recognize and respond to the PXE or BOOTP boot
protocols that are used by the Intel Boot Agent software.

NOTE: When the Intel Boot Agent software is installed as an upgrade for an earlier version boot
ROM, the associated server-side software may not be compatible with the updated Intel Boot
Agent. Contact your system administrator to determine if any server updates are necessary.

6.4.2.1 Linux Server Setup

Consult your Linux vendor for information about setting up the Linux Server.

6.4.2.2 Windows Deployment Services

Nothing is needed beyond the standard driver files supplied on the media. Microsoft owns the process and
associated instructions for Windows Deployment Services. For more information on Windows Deployment
Services perform a search of Microsoft articles at: http://technet.microsoft.com/en-us/library/default.aspx

6.4.3 Intel Boot Agent Messages

Message Text Cause

Invalid PMM func- PMM is not installed or is not working correctly. Try updating the BIOS.
tion number.

PMM allocation PMM could not or did not allocate the requested amount of memory for driver usage.
error.

Option ROM ini- This may be caused by the system BIOS assigning a 64-bit BAR (Base Address Register) to the
tialization error. network port. Running the BootUtil utility with the -64d command line option may resolve this
64-bit PCI BAR issue.
addresses not sup-
ported, AX=

PXE-E00: This sys- System does not have enough free memory to run PXE image. The Intel Boot Agent was unable to
tem does not have find enough free base memory (below 640K) to install the PXE client software. The system cannot
enough free con- boot via PXE in its current configuration. The error returns control to the BIOS and the system does
ventional memory. not attempt to remote boot. If this error persists, try updating your system's BIOS to the most-
The Intel Boot recent version. Contact your system administrator or your computer vendor's customer support to
Agent cannot con- resolve the problem.

705831 94
Intel® Ethernet Adapters and Devices User Guide

Message Text Cause

tinue.

PXE-E01: PCI Image vendor and device ID do not match those located on the card. Make sure the correct flash
Vendor and Device image is installed on the adapter.
IDs do not match!

PXE-E04: Error PCI configuration space could not be read. Machine is probably not PCI compliant. The Intel Boot
reading PCI con- Agent was unable to read one or more of the adapter's PCI configuration registers. The adapter
figuration space. may be mis-configured, or the wrong Intel Boot Agent image may be installed on the adapter. The
The Intel Boot Intel Boot Agent will return control to the BIOSand not attempt to remote boot. Try to update the
Agent cannot con- flash image. If this does not solve the problem, contact your system administrator or Customer Sup-
tinue. port.

PXE-E05: The LAN The adapter's EEPROM is corrupted. The Intel Boot Agent determined that the adapter EEPROM
adapter's con- checksum is incorrect. The agent will return control to the BIOS and not attempt to remote boot.
figuration is cor- Try to update the flash image. If this does not solve the problem, contact your system admin-
rupted or has not istrator or Customer Support.
been initialized.
The Intel Boot
Agent cannot con-
tinue.

PXE-E06: Option The system BIOS does not support DDIM. The BIOS does not support the mapping of the PCI expan-
ROM requires DDIM sion ROMs into upper memory as required by the PCI specification. The Intel Boot Agent cannot func-
support. tion in this system. The Intel Boot Agent returns control to the BIOS and does not attempt to
remote boot. You may be able to resolve the problem by updating the BIOS on your system. If
updating your system's BIOS does not fix the problem, contact your system administrator or your
computer vendor's customer support to resolve the problem.

PXE-E07: PCI BIOS BIOS-level PCI services not available. Machine is probably not PCI compliant.
calls not sup-
ported.

PXE-E09: Unex- The UNDI loader returned an unknown error status. xx is the status returned.
pected UNDI
loader error.
Status == xx

PXE-E0C: Firmware The adapter is in firmware recovery mode. Refer to the “Firmware Recovery Mode” section of this
recovery mode document for details.
detected. Ini-
tialization failed.

PXE-E20: BIOS BIOS could not move the image into extended memory.
extended memory
copy error.

PXE-E20: BIOS Error occurred while trying to copy the image into extended memory. xx is the BIOS failure code.
extended memory
copy error. AH ==
xx

705831 95
Intel® Ethernet Adapters and Devices User Guide

Message Text Cause

PXE-E51: No DHCP The Intel Boot Agent did not receive any DHCP or BOOTP responses to its initial request. Please
or BOOTP offers make sure that your DHCP server (and/or proxyDHCP server, if one is in use) is properly configured
received. and has sufficient IP addresses available for lease. If you are using BOOTP instead, make sure that
the BOOTP service is running and is properly configured.

PXE-E53: No boot The Intel Boot Agent received a DHCP or BOOTP offer, but has not received a valid filename to
filename received. download. If you are using PXE, please check your PXE and BINL configuration. If using BOOTP, be
sure that the service is running and that the specific path and filename are correct.

PXE-E61: Media The adapter does not detect link. Please make sure that the cable is good and is attached to a work-
test failure. ing hub or switch. The link light visible from the back of the adapter should be lit.

PXE-EC1: Base- No base code could be located. An incorrect flash image is installed or the image has become cor-
code ROM ID struc- rupted. Try to update the flash image.
ture was not found.

PXE-EC3: BC ROM Base code could not be installed. An incorrect flash image is installed or the image has become cor-
ID structure is rupted. Try to update the flash image.
invalid.

PXE-EC4: UNDI ID UNDI ROM ID structure signature is incorrect. An incorrect flash image is installed or the image has
structure was not become corrupted. Try to update the flash image.
found.

PXE-EC5: UNDI The structure length is incorrect. An incorrect flash image is installed or the image has become cor-
ROM ID structure is rupted. Try to update the flash image.
invalid.

PXE-EC6: UNDI The UNDI driver image signature was invalid. An incorrect flash image is installed or the image has
driver image is become corrupted. Try to update the flash image.
invalid.

PXE-EC8: !PXE The Intel Boot Agent could not locate the needed !PXE structure resource. An incorrect flash image
structure was not is installed or the image has become corrupted. Try to update the flash image.
found in UNDI
driver code seg- This may also be caused by the system BIOS assigning a 64-bit BAR (Base Address Register) to the
ment. network port. Running the BootUtil utility with the -64d command line option may resolve this
issue.

PXE-EC9: PXENV + The Intel Boot Agent could not locate the needed PXENV+ structure. An incorrect flash image is
structure was not installed or the image has become corrupted. Try to update the flash image.
found in UNDI
driver code seg-
ment.

PXE-M0F: Exiting Ending execution of the ROM image.

Intel Boot Agent.

This option has You attempted to change a configuration setting that has been locked by your system admin-
been locked and istrator. This message can appear either from within Intel® PROSet's Boot Options tab when oper-
cannot be ating under Windows* or from the Configuration Setup Menu when operating in a stand-alone
changed. environment. If you think you should be able to change the configuration setting, consult your sys-

705831 96
Intel® Ethernet Adapters and Devices User Guide

Message Text Cause

tem administrator.

PXE-M0E: Retrying The Intel Boot Agent did not successfully complete a network boot due to a network error (such as
network boot; not receiving a DHCP offer). The Intel Boot Agent will continue to attempt to boot from the network
press ESC to can- until successful or until canceled by the user. This feature is disabled by default. For information on
cel. how to enable this feature, contact Customer Support.

6.4.4 Intel Boot Agent Troubleshooting

6.4.4.1 Common Issues

The following list of problems and associated solutions covers a representative set of problems that you
might encounter while using the Intel Boot Agent.

After booting, my computer experiences problems

After the Intel Boot Agent product has finished its sole task (remote booting), it no longer has any effect on
the client computer operation. Thus, any issues that arise after the boot process is complete are most likely
not related to the Intel Boot Agent product.

If you are having problems with the local (client) or network operating system, contact the operating
system manufacturer for assistance. If you are having problems with some application program, contact
the application manufacturer for assistance. If you are having problems with any of your computer's
hardware or with the BIOS, contact your computer system manufacturer for assistance.

Cannot change boot order

If you are accustomed to redefining your computer's boot order using the motherboard BIOS setup
program, the default settings of the Intel Boot Agent setup program can override that setup. To change
the boot sequence, you must first override the Intel Boot Agent setup program defaults. A configuration
setup menu appears allowing you to set configuration values for the Intel Boot Agent. To change your
computer's boot order setting, see Configuring the Boot Agent in a Pre-boot PXE Environment.

My computer does not complete POST

If your computer fails to boot with an adapter installed, but does boot when you remove the adapter, try
moving the adapter to another computer and using BootUtil to disable the Flash ROM.

If this does not work, the problem may be occurring before the Intel Boot Agent software even begins
operating. In this case, there may be a BIOS problem with your computer. Contact your computer
manufacturer's customer support group for help in correcting your problem.

There are configuration/operation problems with the boot process

If your PXE client receives a DHCP address, but then fails to boot, you know the PXE client is working
correctly. Check your network or PXE server configuration to troubleshoot the problem. Contact Customer
Support if you need further assistance.

705831 97
Intel® Ethernet Adapters and Devices User Guide

PXE option ROM does not follow the PXE specification with respect to the final
"discover" cycle
In order to avoid long wait periods, the option ROM no longer includes the final 32-second discover cycle. (If
there was no response in the prior 16-second cycle, it is almost certain that there will be none in the final
32-second cycle.

6.4.4.2 Diagnostics Information for Preboot PXE Environments

Anytime the configuration setup menu is displayed (see Configuring the Boot Agent in a Preboot PXE
Environment), diagnostics information is also displayed on the lower portion of the screen. The information
displayed appears similar to that shown in the lower half of the screen image below. This information can
be helpful during interaction with Intel Customer Support personnel or your IT team members.

NOTE: Actual diagnostics information may vary, depending upon the adapter(s) installed in your
computer.

Diagnostics information may include the following items:

Item Description

PWA Number The Printed Wire Assembly number identifies the adapter's model and version.

MAC Address The unique Ethernet address assigned to the device.

Memory The memory address assigned by the BIOS for memory-mapped adapter access.

I/O The I/O port address assigned by the BIOS for I/O-mapped adapter access.

705831 98
Intel® Ethernet Adapters and Devices User Guide

Item Description

IRQ The hardware interrupt assigned by the system BIOS.

UNB The address in upper memory where the Boot Agent is installed by the BIOS.

PCI ID The set of PCI identification values from the adapter in the form:

VendorID/DeviceID/SubvendorID/SubdeviceID/Revision

Slot The PCI bus address (slot number)reported by the BIOS.

NOTE: The number displayed is the BIOS version of the PCI slot number. Therefore,
actual positions of NICs within physical slots may not be displayed as expected. Slots
are not always enumerated in an obvious manner, and this will only report what is
indicated by the BIOS.

Flags A set of miscellaneous data either read from the adapter EEPROM or calculated by the
Boot Agent initialization code. This information varies from one adapter to the next
and is only intended for use by Intel customer support.

6.4.4.3 Known Issues

Incorrect port numbering in the Boot Options Menu

On certain platforms, some device entries in the legacy PXE option ROM Boot Option Menu are pre-pended
with identical port number information (first part of the string that comes from BIOS). This is not an option
ROM issue. The first device option ROM to be initialized on a platform exposes all boot options for the device.
This is misinterpreted by BIOS. The second part of the string from the option ROM indicates the correct slot
(port) numbers.

705831 99
Intel® Ethernet Adapters and Devices User Guide

7. Firmware
Firmware is a layer of software that is programmed into a device's memory. It provides low level
functionality for the device. In most cases you will not notice the firmware on your device at all. Firmware
error states usually occur because of an unsuccessful update.

7.1 Firmware Security

Intel or your equipment manufacturer will occasionally release a firmware security patch. We recommend
that you update your firmware to the latest version available for your device to take advantage of these
security patches. Firmware updates for Intel Ethernet devices will have a Security Revision number
(SRev).

7.1.1 Minimum Security Revision Enforcement

Firmware security updates can be undone if you install a previous version of the firmware onto your device.
Intel firmware releases include a Minimum Security Revision (MinSRev) enforcement feature. This means
you can block someone from installing a lower revision of the firmware onto your device. This will limit the
rollback capabilities of your device. The firmware update process will block the update if the supplied
firmware has a lower security revision (SRev) than the MinSRev value of the firmware currently loaded on
the device. Only update the MinSRev value if you are certain you will not need to roll the firmware back to
an earlier version.

You can update the MinSRev value during the firmware update process, locking the current security
version in as the new MinSRev baseline, by using the -optinminsrev command line option.

CAUTION: The MinSRev value on a device can never be decreased. Once the
MinSRev is increased, NVM downgrades attempting to install a lower Security
revision (SRev) than the current MinSRev will be rejected by the device. Users who
want to downgrade firmware without regard to security revisions should not use
this feature.

7.1.2 SRev and MinSRev Examples

7.1.2.1 View your device's current SRev and MinSRev

You can use the nvmupdate tool's inventory mode to view your device's current SRev and MinSRev values
as follows:

Windows: nvmupdatew64e -i -l update.log -o results.xml -c nvmupdate.cfg -optinminsrev

Linux: nvmupdate64e -i -l update.log -o results.xml -c nvmupdate.cfg

Where:

-i -- Sets nvmupdate to inventory mode.

-l update.log -- Specifies the name of the log file.

-o results.xml -- Specifies the name of the results file. This is an XML file that
contains the inventory/update results.

705831 100
Intel® Ethernet Adapters and Devices User Guide

-c nvmupdate.cfg -- Specifies the name of the configuration file. This is a text

file that contains descriptions of networking devices and firmware versions for
those devices.

-optinminsrev -- Specifies that the MinSRev and SRev values are included in
the results.xml file.

Examine the results.xml file for the SRev and MinSRev values.

NOTE: Make sure you specify -i for inventory mode. If you specify -u, the tool will update the
MinSRev value, rather than simply disclose it. You can achieve the same results by specifying
MINSREV:TRUE in the configuration file.

7.1.2.2 Update your device's MinSRev

Download and extract the NVM Update Package for your device. Use the command line to update your
device's MinSRev:

Windows: nvmupdatew64e -u -optinminsrev -l update.log -o results.xml -c nvmupdate.cfg

Linux: nvmupdate64e -u -optinminsrev -l update.log -o results.xml -c nvmupdate.cfg

Where:

-u -- Sets nvmupdate to update mode.

-optinminsrev -- Tells the tool to update the MinSRev value.

-l update.log -- Specifies the name of the log file.

-o results.xml -- Specifies the name of the results file. This is an XML file that
contains the inventory/update results.

-c nvmupdate.cfg -- Specifies the name of the configuration file. This is a text

file that contains descriptions of networking devices and firmware versions for
those devices.

7.2 Firmware Rollback Mode

When a port is in firmware rollback mode it may have reduced functionality. Usually a device enters
firmware rollback mode when a firmware update does not complete correctly. Rebooting or power cycling
the system may allow the port to use the previous firmware. You may need to reapply the firmware update
to regain full functionality on the device. Use the appropriate NVM Update Package to update the device's
firmware. Download the latest NVM Update Package from your vendor's support website and follow the
instructions in it. After restoring the NVM image, you may need to perform an A/C power cycle of the
system.

7.3 Firmware Recovery Mode

A device will enter Firmware Recovery mode if it detects a problem that requires the firmware to be
reprogrammed. When a device is in Firmware Recovery mode it will not pass traffic or allow any
configuration; you can only attempt to recover the device's firmware.

705831 101
Intel® Ethernet Adapters and Devices User Guide

7.3.1 Recovery Mode Detection

During initialization, a device can enter recovery mode if the device firmware detects a problem with the
LAN device, mandating NVM reprogramming to restore normal operation. After thorough internal testing
of the NVM (typically less than 10 minutes, but in some cases longer), the NIC enters Recovery Mode.

7.3.2 Firmware Recovery Mode Errors and Messages

When a device is in Firmware Recovery mode, the device drivers, preboot software, and utilities may log or
display messages such as the following:
l Firmware recovery mode detected. Limiting functionality. Refer to the Intel® Ethernet
Adapters and Devices User Guide for details on firmware recovery mode.
l Firmware recovery mode detected. The underlying hardware has been deactivated.
Refer to the Intel® Ethernet Adapters and Devices User Guide for details on firmware
recovery mode.
l Firmware recovery mode detected. Initialization failed.
l Firmware recovery mode detected. Limiting functionality.
l Initialization failure due to repeated FW resets. This message is usually an indication that
the device is about to enter Recovery Mode. The device may be able to return to normal
functionality without intervention. This may take several minutes. No action is required unless the
device does enter Recovery Mode.

7.3.3 Resolving Firmware Recovery Mode Issues

If your device is in Firmware Recovery mode, you can restore it to factory defaults using the latest NVM
Update Package. Download the latest NVM Update Package from your vendor's support website and follow
the instructions in it.

The process for resolution of Firmware Recovery Mode Issues is outlined in the sub-sections below.

7.3.3.1 NVM Self Check

The process begins after power-on or reboot. At this time, the firmware will perform tests to assess
whether there is damage or corruption of the device NVM image.

Actions:
l If NVM image damage or corruption is not detected, the device will initialize and operate normally.
No further action is required.
l If NVM image damage or corruption is detected, the device will not initialize. Proceed with the
additional recovery steps listed under Recovery Mode below.

7.3.3.2 Recovery Mode

The device NVM image has exhibited damage or corruption.

705831 102
Intel® Ethernet Adapters and Devices User Guide

Actions:
1. Wait 10 minutes for the NVM self-check process to complete. If during this period normal operation
is achieved, the device will initialize and operate normally. No further action is required.
2. If after 10 minutes normal operation is not achieved:
a. Check the System Event log for Windows OSs or driver message and kernel logs for Linux and
ESXi based distributions. Recovery Mode is confirmed by presence of message/log entries as
listed in the Firmware Recovery Mode Errors and Messages section above.
b. Reboot the system and proceed with the additional recovery steps listed under NVM Image
Restoration below.

NOTES:
l While in Recovery Mode, for Windows OSs, clicking on the adapter in device manager may
present a dialog box indicating that Firmware Recovery Mode is active.
l Once the dialog is dismissed, while the device appears to be functioning normally, it is
in fact limited to only enable NVM image recovery.
l If the system is rebooted (versus power cycled), the driver status may not show a Code
10/yellow bang status as expected. Refer to events logged in System Event log for Windows
OSs or driver message and kernel logs for Linux and ESXi based distributions to accurately
assess the adapter status.
l When the adapter is in recovery mode, the link LED will not be lit and the adapter will not
appear in the following locations:
l F2 System Setup > Device Settings
l System BIOS as a NIC for PXE Boot in UEFI boot mode

7.3.3.3 NVM Image Restoration

At this point, the device is in Firmware Recovery mode and its functionality is limited to only supporting
restoration of the NVM image.

Actions:
1. Before initiating device recovery, the integrity of the host operating system, device drivers and
firmware utilities must be verified and reinstalled if necessary. Fully functional operating system,
device drivers and tools are required for device recovery. Please consult your operating system
specific instructions on how to scan and repair potentially damaged system files.
2. If your device is in Firmware Recovery mode, you can restore it to factory defaults using the latest
NVM Update Package. Download the latest NVM Update Package from your vendor's support website
and follow the instructions in it.
3. After restoring the NVM image, perform an A/C power cycle of the system. Details for this are in the
Other General Notes section below.

NOTES:
l User configured settings (i.e. iSCSI target information, user defined port/alternate MAC
addresses) will not be restored to pre-recovery mode values.

705831 103
Intel® Ethernet Adapters and Devices User Guide

7.3.3.4 Other General Notes

NOTES:
l To perform an AC power cycle, do the following:
l Shut down the system if its is powered up.
l Unplug all AC power cords from the system.
l Leave the AC power cords unplugged for 15 seconds to allow the system power
supply to discharge completely.
l Plug in AC power cords to the system.

7.4 Using Devlink to Update a Device's NVM

On a Linux system, when you update the NVM on some devices, the update may use the devlink interface,
rather than the ethtool interface. This will happen if the following are true:
l You are updating an Intel Ethernet 800 Series device.
l Your system is running a distro that supports the "devlink dev flash" command.
l The firmware currently installed on the device supports it.
l The new NVM conforms to the correct PLDM format.

Most of the functionality and commands are the same with the following exceptions:
l You cannot update a device in Recovery Mode. (To update a device in recovery mode, you must
download and install the Intel Ethernet driver set.)
l You cannot update the OROM or Netlist as a separate update, only as part of a full NVM update.
l If you specified a preservation level of PRESERVE_ALL, the system will immediately perform an
EMPR reset after the NVM update.

On devices that support it, you can also use the devlink command line directly to update the device NVM.
However, we recommend that you use NVMUpdate.

# devlink dev flash pci/0000:3b:00.0 file filename.bin

Where :
l pci/0000:3b:00.0 – The device you wish to update. You can get a list of devices with the "devlink
dev info" command.
l filename.bin – The file that contains the new NVM image.

7.5 Firmware Logging

Intel® Ethernet 800 Series devices allow you to generate firmware logs for supported categories of events,
to help debug complex issues with Customer Support. Firmware logging is enabled by default.

NOTE:
l Both the device and the driver need to support firmware logging for the functionality to
work. If you are not able to set the configuration and the problem persists, reinstall the
driver.
l You must have the latest base driver and NVM installed.
l Firmware logging events and levels are device-wide settings. Changing the log configuration
on one port will apply it to all ports on a device.

705831 104
Intel® Ethernet Adapters and Devices User Guide

7.5.1 Capturing a Firmware Log

To capture a firmware log, you must do the following:

1. Set the configuration for the firmware log. See the following for more information:
l "Configuring Settings for Firmware Logs" below
l "Tips for Firmware Logs" on the next page
l "OS-Specific Information" on page 107
2. Perform the necessary steps to generate the issue you’re trying to debug.
3. Capture the firmware log. (Exact steps will vary by operating system.)
4. Stop capturing the firmware log.
5. Reset your firmware log settings as needed.
6. Work with Customer Support to debug your issue.

NOTE: Firmware logs are generated in a binary format and must be decoded by Customer Support.
Information collected is related only to firmware and hardware for debug purposes.

7.5.2 Configuring Settings for Firmware Logs

Firmware logs capture information about different categories of events (called "modules"). A module
corresponds to a general category of functionality, such as link topology detection or manageability.

The device’s NVM sets default verbosity levels for each module. You can change the verbosity level per
module; refer to "OS-Specific Information" on page 107 for more details. You can set only one log level per
module, and each level includes the verbosity levels lower than it. Available verbosity levels are:
l 0 = none
l 1 = error
l 2 = warning
l 3 = normal
l 4 = verbose

If you see errors or suspect the issue could fall into the below categories, setting the firmware logs to
capture more verbosity for the corresponding module(s) in the right column will provide more information
in the firmware log.

Category of Event Corresponding Module

Initialization Control

NVM NVM

Authentication

VPD

I/O I2C

SDP

MDIO

Link Management Link Management

705831 105
Intel® Ethernet Adapters and Devices User Guide

Category of Event Corresponding Module

Link Control Technology

Link Topology Detection

Rx Parser

Switch

ACL

Post

Tx Scheduler

Tx Queue Management

AQ Interface Admin Queue

HDMA

Manageability Manageability

Protocols LLDP

DCBx

Infrastructure Watchdog

Task Dispatcher

General

IOSF

PF Registration

Module Versions

XLR XLR

QoS DCB

Diagnostics SyncE

Health

TimeSync Time Sync

7.5.3 Tips for Firmware Logs

l Firmware logs are for the hardest issues to debug. If you are experiencing issues, refer to the
following sections for preliminary methods to diagnose problems:
l "Firmware" on page 100
l "Troubleshooting" on page 111
l "Health Status Messages" on page 113
l We generally do not recommend to capture firmware logs at all times. If you suspect an issue, set
the module(s) for the suspected event to a higher verbosity level, capture the firmware log, and
then stop the log.
l Collecting firmware logs should not materially impact performance or CPU utilization.

705831 106
Intel® Ethernet Adapters and Devices User Guide

l In general, set the logging level to Verbose only for the configuration group(s) or module(s) you
need to debug. Setting too many modules to Verbose can overrun the buffer.
l You can try writing logs to a remote location or an external storage device, if your disk is full or your
system does not have sufficient storage.

7.5.4 OS-Specific Information

Linux and FreeBSD

Refer to the README in the driver tarball for more information on configuring firmware logs.

NOTE: In FreeBSD, the driver can register/unregister to receive events per PF.

Windows

In Windows, you use PowerShell and Intel Ethernet cmdlets to configure firmware logging and capture
firmware logs. At a high level, do the following to capture a firmware log in Windows:

1. Set the configuration for the firmware log, using the Set-IntelEthernetLogConfig cmdlet in
PowerShell.
2. Perform the necessary steps to generate the issue you're trying to debug.
3. Start capturing the firmware log, using the Start-IntelEthernetLog cmdlet.
4. Stop capturing the firmware log, using the Stop-IntelEthernetLog cmdlet.
5. Work with Customer Support to decode your firmware log file and debug the issue.

NOTE: Firmware logs will be captured in the file you designated with Start-
IntelEthernetLog.

NOTE: To disable firmware logging, use the Disable-IntelEthernetLogConfig cmdlet. To verify

that firmware logging is disabled, run the Get-IntelEthernetLogConfig cmdlet; its results should
say "Disabled."

Refer to the following for more information:

l "About Intel® Ethernet Cmdlets" on page 15
l The cmdlet help for Intel Ethernet cmdlets (see "Help Information for PowerShell Cmdlets" on
page 22)
l The readme file inside the Intel Ethernet cmdlet zip file

ESXi

In ESXi, use esxcfg-module to set the configuration for firmware logs. Firmware logs are printed to kernel
logs, with the tag FWLOG; use dmesg or read the file at /var/log/vmkernel.log.

At a high level, do the following to capture a firmware log in ESXi:

NOTE: Refer to the table after these steps for all commands and parameters.

705831 107
Intel® Ethernet Adapters and Devices User Guide

1. Set the configuration for the firmware log, using esxcfg-module. The ESXi driver uses the following
module parameters for firmware logging:
l FWLogEnable: Enables firmware logging functionality on the designated PF (0 = Disable, 1 =
Enable). Use commas to separate the values for each PF; the first value is for PF0, second for
PF1, and so on.
l FWLogEvents: Designates the firmware events to log, using a bitmask. Binary math is
required to set.
l FWLogLevel: Sets the verbosity level for the firmware event's log.
2. Redirect the kernel log or dmesg to a separate file for capturing the firmware log.
3. Reboot the system for changes to take effect.
4. After the system has rebooted, perform the necessary steps to generate the issue you’re trying to
debug.
5. Work with Customer Support to decode your firmware log file and debug the issue.

NOTE: Firmware logs will be captured in the file you designated in step 2.

Use the following commands in ESXi for tasks related to firmware logging:

Task Example Code

Enable firmware logging and set the verbosity # esxcfg-module icen -s 'FWLogEnable=<values>
level for your desired events FWLogEvents=<bitmask> FWLogLevel=<value>'

For example, to enable firmware logging on PF0 and set all events to
log warning messages, use:

# esxcfg-module icen -s 'FWLogEnable=1,0,0,0,0,0,0,0

FWLogEvents=255 FWLogLevel=2'

Show the current configuration of the firmware # esxcfg-module -g <driver name>

log parameters
NOTE: If firmware logging is disabled, the FWLogEnable parameter
should say “0” (disabled).

Show a description of module parameters for firm- # esxcfg-module -i <driver name>

ware logging
NOTE: Look for the parameters that begin with FWLog.

Redirect the firmware log to a file # tail -f /var/log/vmkernel.log > filename.log

Disable firmware logging # esxcfg-module icen -s 'FWLogEnable=0 FWLogEvents=0

FWLogLevel=0'

7.6 Debug Dump

Intel Ethernet 810 Series devices support debug dump, which allows you to obtain runtime register values
from the firmware for "clusters" of events and then write the results to a single dump file, for debugging
complicated issues in the field.

This debug dump contains a snapshot of the device and its existing hardware configuration, such as switch
tables, transmit scheduler tables, and other information. Debug dump captures the current state of the
specified cluster(s) and is a stateless snapshot of the whole device.

705831 108
Intel® Ethernet Adapters and Devices User Guide

NOTE:
l Like with firmware logs, the contents of the debug dump are not human-readable. You must
work with Customer Support to decode the file.
l Debug dump is per device, not per PF.
l Debug dump writes all information to a single file.
l This feature is not currently supported on Linux.

Exact steps will vary by OS, but do the following to generate a debug dump log file:

1. Using the method appropriate for your OS (see "OS-Specific Information" below), specify one or
more clusters that you want to dump the hardware configuration for.
l NOTE: Firmware will return an error if you call the command without specifying at least one
cluster. Available clusters include:
l Switch
l ACL
l Tx Scheduler
l Profile Configuration
l Link
l DCB
l L2P
2. Specify the path and filename for the dump file to be written to (optional depending on your OS).
3. Execute the command to write the debug dump file.
4. After the log file is written, work with Customer Support to decode the dump file.

7.6.1 OS-Specific Information

Use the following tools or commands to write the debug dump results to a dump file:

OS Method to Generate Debug Dump File

Windows Server Use either of the following:

Azure Stack HCI l Write-IntelEthernetDebugDump Ethernet cmdlet in PowerShell (see the cmdlet help for more
information)
l Intel® Ethernet Inspector

Windows Not supported

Linux Not supported

ESXi Use esxcli (see below)

FreeBSD Use sysctl (see the FreeBSD base driver README for more information)

ESXi

NOTE: For this functionality to work, you must have installed version 1.10.x or higher of the intnet
tool, which is a plugin to the esxcli tool. You can download the latest version from the Intel
Download Center here.

705831 109
Intel® Ethernet Adapters and Devices User Guide

In esxcli, use the following command to generate the debug dump file for your specified cluster(s):

# esxcli intnet debug fw dump <Cmd options>

Where <Cmd options> include:

l -n|--vmnic <string>: Specifies the vmnic name to operate on. NOTE: This field is
required.
l -c|--clusters <string>: Specifies the clusters to dump. You must specify at least
one cluster.
l To specify multiple clusters, enclose a single string in quotes, separated by
commas with no spaces. For example:
# esxcli intnet debug fw dump -n vmnic0 --clusters "ACL,L2P"
l -l|--list: Displays the complete list of valid clusters on the screen.

To show the complete list of valid clusters, use the following:

# esxcli intnet debug fw dump -n <vmnicX> -l

esxcli will output the debug dump results to a single file in the /scratch/core directory. The file naming
convention is vmnicX-<time-stamp>-dump.bin, where vmnicX is the VMware device alias of the affected
device.

705831 110
Intel® Ethernet Adapters and Devices User Guide

8. Troubleshooting

8.1 Common Problems and Solutions

There are many simple, easy-to-fix problems related to network problems. Review each one of these before
going further.
l Check for recent changes to hardware, software, or the network that may have disrupted
communications.
l Check the driver software.
l Make sure you are using the latest appropriate drivers for your adapter from the Intel support
website.
l Disable (or unload), then re-enable (reload) the driver or adapter.
l Check for conflicting settings. Disable advanced settings such as teaming or VLANs to see if it
corrects the problem.
l Re-install the drivers.
l Check the cable. Use the best available cabling for the intended data rate.
l Check that the cable is securely attached at both points.
l Make sure the cable length does not exceed specifications.
l Perform a cable test.
l Replace the cable.
l Check the link partner (switch, hub, etc.).
l Make sure the link partner is active and can send and receive traffic.
l Make sure the adapter and link partner settings match one another, or are set to auto-
negotiate.
l Make sure the port is enabled.
l Re-connect to another available port or another link partner.
l Look for adapter hardware problems.
l Re-seat the adapter.
l Insert the adapter in another slot.
l Check for conflicting or incompatible hardware devices and settings.
l Replace the adapter.
l Check the Intel support website for possible documented issues.
l Select your adapter from the adapter family list.
l Check the Frequently Asked questions section.
l Check the Knowledge Base.
l Check your process monitor and other system monitors.
l Check to see that there is sufficient processor and memory capacity to perform networking
activity.
l Look for any unusual activity (or lack of activity).
l Use network testing programs to check for basic connectivity.

705831 111
Intel® Ethernet Adapters and Devices User Guide

l Check your BIOS version and settings.

l Use the latest appropriate BIOS for your computer.
l Make sure the settings are appropriate for your computer.

The following troubleshooting table assumes that you have already reviewed the common problems and
solutions.

Problem Solution

Your computer cannot find the adapter Make sure your adapter slots are compatible for the type of adapter you
are using.

Diagnostics pass but the connection fails Make sure the cable is securely attached, is the proper type and does not
exceed the recommended lengths.

Make sure the duplex mode and speed setting on the adapter matches
the setting on the switch.

Adapter unable to connect to switch at correct This is applicable only to copper-based connections.
speed. Gigabit adapter connects at 100 Mbps
and 10 gigabit adapter connects at 1000 Mbps. Make sure the adapter and the link partner are set to auto-negotiate.

Verify that you are running the latest operating system revision for your
switch and that the switch is compliant with the proper IEEE standard:
l IEEE 802.3ad-compliant (gigabit over copper)
l IEEE 802.3an-compliant (10 gigabit over copper)

The device does not connect at the expected When Gigabit PHY Mode is forced to Primary mode on both the Intel
speed. adapter and its link partner, the link speed obtained by the Intel adapter
may be lower than expected or link may not be established.

The adapter stops working without apparent Run the adapter and network tests described in "Diagnostics in Intel
cause PROSet" on page 115.

The Link indicator light is off Run the adapter and network tests described in "Diagnostics in Intel
PROSet" on page 115.

Make sure the proper (and latest) driver is loaded.

Make sure that the link partner is configured to auto-negotiate (or forced
to match adapter)

Verify that the switch is IEEE 802.3ad-compliant.

The link light is on, but communications are not Make sure the proper (and latest) driver is loaded.
properly established
Both the adapter and its link partner must be set to either auto-detect or
manually set to the same speed and duplex settings.

NOTE: The adapter's link indicator light may be on even if com-

munications between the adapter and its link partner have not
been properly established. Technically, the link indicator light
represents the presence of a carrier signal but not necessarily
the ability to properly communicate with a link partner. This is
expected behavior and is consistent with IEEE's specification for
physical layer operation.

RX or TX light is off Network may be idle; try creating traffic while monitoring the lights.

The diagnostic utility reports the adapter is The PCI BIOS isn't configuring the adapter correctly. See "PCI / PCI-X /

705831 112
Intel® Ethernet Adapters and Devices User Guide

Problem Solution

"Not enabled by BIOS" PCI Express Configuration" later in this table.

The computer hangs when the drivers are Try changing the PCI BIOS interrupt settings. See "PCI / PCI-X / PCI
loaded Express Configuration" later in this table.

The Fan Fail LED of the 10 Gigabit AT Server The fan cooling solution is not functioning properly. Contact customer
Adapter is on (red) support for further instructions.

PCI / PCI-X / PCI Express Configuration If the adapter is not recognized by your OS or if it does not work you may
need to change some BIOS settings. Try the following only if you are
having problems with the adapter and are familiar with BIOS settings.
l Check to see that the "Plug-and-Play" setting is compatible with
the operating system you are using.
l Make sure the slot is enabled.
l Configure interrupts for level-triggering, as opposed to edge-
triggering.
l Reserve interrupts and/or memory addresses. This prevents
multiple buses or bus slots from using the same interrupts.
Check the BIOS for IRQ options for PCI / PCI-X / PCIe.

Driver message: "Rx/Tx is disabled on this You installed an unsupported module in the device. See "Supported
device because an unsupported SFP+ module SFP+, SFP28, QSFP+, and QSFP28 Modules" on page 8 for a list of sup-
type was detected." ported modules.

8.2 Multiple Adapters

When configuring a multi-adapter environment, you must upgrade all Intel adapters in the computer to
the latest software.

If the computer has trouble detecting all adapters, consider the following:
l If you enable Wake on LAN* (WoL) on more than two adapters, the Wake on LAN feature may
overdraw your system’s auxiliary power supply, resulting in the inability to boot the system and
other unpredictable problems. For multiple desktop/management adapters, it is recommended that
you install one adapter at a time and use the IBAUtil utility (ibautil.exe in \APPS\BOOTAGNT) to
disable the WoL feature on adapters that do not require WoL capabilities. On server adapters, the
WoL feature is disabled by default.
l Adapters with Intel Boot Agent enabled will require a portion of the limited start up memory for each
adapter enabled. Disable the service on adapters that do not need to boot Pre-Boot Execution
Environment (PXE).

8.3 Health Status Messages

Intel® Ethernet 800 Series devices support asynchronous health status messages, which help you to
debug system-level issues and diagnostics in the field. This feature is enabled by default and cannot be
shut off.

When the firmware detects an abnormal event during initialization, it will push health status information
to the base driver’s system event log, such as dmesg or the Windows Event Log. Health status messages
could encompass issues related to:

705831 113
Intel® Ethernet Adapters and Devices User Guide

l Unsupported modules
l The NVM or option ROM
l Invalid link configuration
l Port speed
l Link partner
l Other issues

The system log will identify the device experiencing the issue, list information about the problem, and
suggest a possible solution, such as updating to the latest NVM image or checking the cable or module.

See your system log for more information, if you are experiencing issues on Intel Ethernet 800 Series
devices.

8.4 Safe Mode

Adapters based on the Intel® Ethernet 800 Series require a Dynamic Device Personalization (DDP)
package file to enable advanced and performance features. If the driver detects a missing or incompatible
DDP package file, the driver will go into Safe Mode. Safe Mode supports only basic traffic and minimal
functionality, such as updating the NVM or downloading a new driver or DDP package.

NOTES:
l Safe Mode only applies to the affected physical function and does not impact any
other PFs.
l Firmware Recovery Mode takes precedence over Safe Mode.

8.4.1 Safe Mode Errors and Messages

When the driver is in Safe Mode, the device drivers and utilities may log or display messages to help with
troubleshooting. The following conditions may cause the driver to enter Safe Mode:
l The DDP package file was not found or couldn't be read.
l The DDP package file's version number, signature, or other metadata aren't valid or aren't
supported by the driver.
l An unknown error occurred when loading the DDP package.
l The driver couldn't load the DDP package file because a compatible DDP package is already present
on the device.
l The device has a DDP package that isn't supported by the driver.

8.4.2 Resolving Safe Mode Issues

The device drivers and utilities may display the action to take to get out of Safe Mode, depending on the
underlying cause. Possible actions could include the following:
l Wait for the device to reset.
l Install the latest driver.
l Download a new DDP package.
l Restart the adapter. If the problem persists, install the latest driver.
l Reboot the system. If the problem persists, update the NVM.

You can download the latest drivers and DDP packages from the Intel support website.

705831 114
Intel® Ethernet Adapters and Devices User Guide

8.5 PF Message Queue Overflow

The device driver can detect some types of anomalous behavior. When it does, it will log the VF MAC
address and associated PF MAC address. Using this information, you can check the virtual machine (VM)
that is using the VF MAC address to ensure that the VM is operating correctly.

8.6 Possible Misconfiguration of the Ethernet Port

You may see an informational message stating that a potential misconfiguration of the Ethernet port was
detected. This is to alert you that your device is being underutilized. If this was intentional, you may ignore
this message. For example, setting your Intel® Ethernet Network Adapter E810-C-Q2 adapter to 2x2x25
is valid, but it does not use the full capabilities of the device. If you see this message, and the configuration
was not intentional, you may use the Ethernet Port Configuration Tool (EPCT) to correct the configuration.

8.7 Other Performance Issues

Attaining the best speed requires that many components are operating at peak efficiency. Among them
are the following:
l Cable quality and length - Do not exceed the maximum recommended length for your cable
type. Shorter lengths often provide better results. Check for loose or damaged connectors. Check
the cable for kinked or damaged sections.
l Bus speed and traffic - The PCI bus speed accommodates the slowest PCI card installed. Check to
see if you have a card that is slowing down your system.
l Processor and Memory - Check your performance monitoring programs to see if traffic is being
affected by your processor speed, available memory or other processes.
l Transmission frame size - Your network performance may be enhanced by adjusting or
maximizing the transmission frame size. Operating systems, switches and adapters will impose
varying limits on maximum frame size. See the discussion on Jumbo Frames for your OS.
l Operating System - Networking feature implementation will vary by operating system version,
such as offloading and multiprocessor threading.

8.8 Diagnostics
Multiple utilities are available to help troubleshoot and diagnose issues with your Intel Ethernet devices.

8.8.1 Linux Diagnostics

Intel Ethernet drivers use the ethtool interface for driver configuration and diagnostics, as well as
displaying statistical information. The latest ethtool version is required for this functionality. Download it at
https://kernel.org/pub/software/network/ethtool/.

8.8.2 Diagnostics in Intel PROSet

Intel's diagnostic software lets you test the adapter to see if there are problems with the adapter hardware,
the cabling, or the network connection. Refer to "About Intel PROSet®" on page 15 for an overview of this
software.

Intel PROSet allows you to run the following types of diagnostic tests on supported Windows operating
systems.

705831 115
Intel® Ethernet Adapters and Devices User Guide

Type of Test Description

Connection Test Verifies network connectivity by pinging the DHCP server,

WINS server, and gateway.

Cable Tests Provides information about cable properties.1

Hardware Tests Determines if the adapter is functioning properly.2

Note:
l The Cable Test is not supported on all adapters and will not run on Direct Attached Cables (DAC) or Fiber. The Cable
Test will only be available on adapters that support it.

To access these tests, select the adapter in Windows Device Manager, click the Link tab, and click
Diagnostics. A Diagnostics window displays tabs for each type of test. Click the appropriate tab and run
the test.

In Intel PROSet ACU, use the Diagnostics panel.

The availability of these tests is dependent on the adapter and operating system. Tests may be disabled if:
l The port is used as a manageability port.
l The tests are being run from a virtual machine.

NOTE: At this time, Windows diagnostics are not supported on ports based on an Intel Ethernet
Controller I225 and will fail.

8.8.2.1 Testing from Windows PowerShell

Intel provides two PowerShell cmdlets for testing your device.
l Test-IntelNetDiagnostics runs the specified test suite on the specified device. See the Test-
IntelNetDiagnostics help inside PowerShell plus the following table for more information.

l Test-IntelNetIdentifyAdapter blinks the LED on the specified device.

The following table describes the possible result codes from the Test-IntelNetDiagnostics cmdlet (where
<X> below indicates a value returned in the message).

Result
Code Description

00 Successfully pinged gateway address <X>.

01 Successfully pinged DHCP address <X>.

02 Successfully pinged DNS address <X>.

03 Successfully pinged WINS address <X>.

04 An instance of this test is already running. You can only have one test running at a time.

05 TCP/IP protocol is not configured. To run this test, configure this connection to use the TCP/IP protocol.

07 The IP address for this connection is invalid. Possible cause: The system may be waiting for a response from a
DHCP server.

705831 116
Intel® Ethernet Adapters and Devices User Guide

Result
Code Description

09 The IP address for this connection is invalid.

18 You cannot run this test while the device is included in a team or VLAN.

19 Auto-negotiation is not enabled on the device. The device has been configured to force a lower speed.

20 Auto-negotiation is not complete on this device. Please wait and try again later.

21 A Category 5 (or better) cable is required to run at 1 Gbps. The cable connected to the device either is not Cat-
egory 5 (or better) or has faulty wires.

22 Link speed: <X> Mbps. The link partner is not capable of higher speeds.

23 The link partner is not advertising a compatible speed. Please check that the link partner supports 1 Gbps.

24 Link speed has been reduced because a Power Saver option is enabled. Disable power saving in your OS settings
and run the test again.

25 The device is configured to force a lower speed.

26 No cable problems detected.

27 Could not run the test at this time. Please try again later.

33 The test detected a bad connection. Distance to problem: <X> meters.

34 Passed

35 Failed

36 Cable quality is unknown.

37 Passed

38 Failed

39 Cable quality is unknown.

40 Cable polarity is normal.

41 Cable polarity is reversed.

42 Cable length: <X> meters.

43 This device is running at full speed.

44 Cable quality is poor or no cable is connected. Possible causes: Faulty cable, faulty connector, or a speed/duplex
mismatch. Verify that the speed/duplex setting on the switch/hub is configured for auto-negotiation.

45 Cable quality is poor or no cable is connected. Possible causes: Faulty cable, faulty connector, or a speed/duplex
mismatch.

46 Cable quality is adequate.

47 Cable quality is good.

705831 117
Intel® Ethernet Adapters and Devices User Guide

Result
Code Description

48 Cable quality is excellent.

49 Cable quality is unknown.

50 The test detected a frequency response that does not meet IEEE specifications.

51 This device does not have link. Make sure the cable is connected and the speed and duplex settings are configured
correctly on the device and link partner.

52 Passed

53 Passed

54 Passed

55 Passed

56 Passed

57 Passed

58 Failed

59 Failed

60 Failed

61 Failed

62 Failed

63 Failed

64 Passed

65 Failed

66 This device requires a restart.

67 Could not run the test at this time. The device may be connected to a remote target. Disconnecting the cable will
enable the test.

68 Could not run the test at this time. This device is used as a manageability port. Disconnecting the cable will
enable the test.

69 The device does not support this test.

70 This test relies on a response from a gateway, DNS, DHCP, or WINS server and no such response was received. Any
such server for this connection may be unavailable or misconfigured.

71 Cable integrity is unknown.

72 This test relies on a response from a gateway, DNS, DHCP, or WINS server and no such response was received. Any
such server for this connection may be unavailable or misconfigured.

This device is configured to automatically obtain an IP address but no DHCP server is present on the network.

705831 118
Intel® Ethernet Adapters and Devices User Guide

Result
Code Description

Windows selected an IP address using alternate private IP addressing.

73 Temperature is normal.

74 Possible values:

The device overheated and was stopped.

The device overheated. Link speed was reduced.

705831 119
Intel® Ethernet Adapters and Devices User Guide

9. Known Issues
Known issues are no longer included in this user guide. See the Release Notes for this release for all known
issues and fixed issues.

705831 120
Intel® Ethernet Adapters and Devices User Guide

10. Regulatory Compliance Statements

10.1 FCC Class A Products

l Intel® Ethernet Network Adapter E810-2C-Q2
l Intel® Ethernet Network Adapter E810-C-Q1
l Intel® Ethernet Network Adapter E810-C-Q1 for OCP
l Intel® Ethernet Network Adapter E810-C-Q1 for OCP 3.0
l Intel® Ethernet Network Adapter E810-C-Q2 for OCP 3.0
l Intel® Ethernet Network Adapter E810-C-Q2T
l Intel® Ethernet Network Adapter E810-L-Q2 for OCP 3.0
l Intel® Ethernet Network Adapter E810-XXV-2 for OCP 3.0
l Intel® Ethernet Network Adapter E810-XXV-4 for OCP 3.0
l Intel® Ethernet Network Adapter E810-XXV-4T
l Intel® Ethernet Network Adapter I710-T4L for OCP 3.0
l Intel® Ethernet Network Adapter X710-T2L for OCP 3.0
l Intel® Ethernet Network Adapter X710-T4L for OCP 3.0
l Intel® Ethernet Network Adapter XXV710-DA2 for OCP 3.0
l Intel® Ethernet Network Adapter XXV710
l Intel® Ethernet Network Adapter XXV710-1
l Intel® Ethernet Network Adapter XXV710-2
l Intel® Ethernet Network Adapter X722-2
l Intel® Ethernet Network Adapter X722-4
l Intel® Ethernet Server Adapter XL710-Q1OCP
l Intel® Ethernet Server Adapter XL710-Q2OCP
l Intel® Ethernet Network Adapter X710-2 for OCP NIC 3.0
l Intel® Ethernet Network Adapter X710-4 for OCP NIC 3.0
l Intel® Ethernet Converged Network Adapter X710
l Intel® Ethernet I/O Module XL710-Q1
l Intel® Ethernet I/O Module XL710-Q2
l Intel® Ethernet Server Adapter X550-T2 for OCP
l Intel® Ethernet Server Adapter X550-T1 for OCP
l Intel® Ethernet Server Bypass Adapter X540-T2
l Intel® Ethernet Converged Network Adapter X540-T2
l Intel® Ethernet Converged Network Adapter X540-T1
l Intel® Ethernet OCP Server Adapter X520-1
l Intel® Ethernet OCP Server Adapter X520-2
l Intel® Ethernet Server Bypass Adapter X520-SR2
l Intel® Ethernet Server Adapter X520-T2

705831 121
Intel® Ethernet Adapters and Devices User Guide

l Intel® Ethernet X520 10GbE Dual Port KX4 Mezz

l Intel® 10 Gigabit AT2 Server Adapter
l Intel® 10 Gigabit SR Dual Port Express Module
l Intel® 10 Gigabit AT Server Adapter
l Intel® Ethernet Network Adapter I350-T4 for OCP NIC 3.0
l Intel® PRO/1000 MT Quad Port Server Adapter

10.2 FCC Class B Products

l Intel® Ethernet Network Adapter E810-C-Q2
l Intel® Ethernet Network Adapter E810-XXV-4
l Intel® Ethernet Network Adapter E810-XXV-2
l Intel® Ethernet Network Adapter I710-T4L
l Intel® Ethernet Network Adapter X710-T2L
l Intel® Ethernet Network Adapter X710-T4L
l Intel® Ethernet Network Adapter X710-TL
l Intel® Ethernet Converged Network Adapter X710-2
l Intel® Ethernet Converged Network Adapter X710-4
l Intel® Ethernet Converged Network Adapter X710-T4
l Intel® Ethernet Converged Network Adapter XL710-Q1
l Intel® Ethernet Converged Network Adapter XL710-Q2
l Intel® Ethernet Converged Network Adapter X550-T1
l Intel® Ethernet Converged Network Adapter X550-T2
l Intel® Ethernet Server Adapter X520-1
l Intel® Ethernet Server Adapter X520-2
l Intel® Ethernet SFP+ LR Optics RMN FTLX1471
l Intel® Ethernet Converged Network Adapter X520-4
l Intel® Ethernet Converged Network Adapter X520-Q1
l Intel® 10 Gigabit AF DA Dual Port Server Adapter
l Intel® 10 Gigabit CX4 Dual Port Server Adapter
l Intel® 10 Gigabit XF SR Dual Port Server Adapter
l Intel® 10 Gigabit XF SR Server Adapter
l Intel® 10 Gigabit XF LR Server Adapter
l Intel® Ethernet Network Adapter I225-T1
l Intel® Ethernet Server Adapter I340-T2
l Intel® Ethernet Server Adapter I340-T4
l Intel® Ethernet Server Adapter I350-T2
l Intel® Ethernet Server Adapter I350-T4
l Intel® Ethernet Server Adapter I210-T1
l Intel® Ethernet Server Adapter I340-F4
l Intel® PRO/1000 MT Server Adapter

705831 122
Intel® Ethernet Adapters and Devices User Guide

l Intel® PRO/1000 MT Dual Port Server Adapter

l Intel® PRO/1000 GT Dual Port Server Adapter
l Intel® PRO/1000 PT Server Adapter
l Intel® PRO/1000 PT Dual Port Server Adapter
l Intel® PRO/1000 GT Quad Port Server Adapter
l Intel® PRO/1000 PT Quad Port Server Adapter
l Intel® PRO/1000 PT Quad Port LP Server Adapter
l Intel® PRO/1000 GT Desktop Adapter
l Intel® PRO/1000 PT Desktop Adapter
l Intel® PRO/1000 MF Server Adapter
l Intel® PRO/1000 MF Dual Port Server Adapter
l Intel® PRO/1000 PF Server Adapter
l Intel® PRO/1000 PF Dual Port Server Adapter
l Intel® PRO/1000 PF Quad Port Server Adapter

10.3 Safety Compliance

The following safety standards apply to all products listed above:
l UL 60950-1, 2nd Edition, 2011-12-19 (Information Technology Equipment - Safety - Part 1:
General Requirements)
l UL 62368-1 2nd Edition (Information Technology Equipment - Safety requirements)
l CSA C22.2 No. 60950-1-07, 2nd Edition, 2011-12 (Information Technology Equipment - Safety -
Part 1: General Requirements)
l CAN/CSA C22.2 European Group Differences and National Differences according to 62368-1-14 -
Audio/video, information and communication technology equipment - Part 1: Safety requirements
l EN 60950-1:2006/A11:2009/A1:2010/A12:2011 (European Union)
l IEC 60950-1:2005 (2nd Edition); Am 1:2009 (International)
l EU LVD Directive 2006/95/EC

10.4 EMC Compliance

The following standards may apply.

10.4.1 Class A Products

l FCC Part 15 – Radiated & Conducted Emissions (USA)
l CAN ICES-3(A)/NMB-3(A) – Radiated & Conducted Emissions (Canada)
l CISPR 22 – Radiated & Conducted Emissions (International)
l EN55022: 2010 – Radiated & Conducted Emissions (European Union)
l EN55024: 2010 +A1:2001+A2:2003 – Immunity (European Union)
l EN55032: 2015 Class A Radiated and Conducted Emissions requirements (European Union)
l EMC Directive 2004/108/EC (European Union)
l VCCI (Class A)– Radiated & Conducted Emissions (Japan)
l CNS13438 – Radiated & Conducted Emissions (Taiwan)

705831 123
Intel® Ethernet Adapters and Devices User Guide

l AS/NZS CISPR 22:2009 + A1:2010 Class A and CISPR 32:2015 for Radiated and Conducted
Emissions requirements (Australia/New Zealand)
l NRRA No. 2012-13 (2012.06.28), NRRA Notice No. 2012-14 (2012.06.28) (Korea)

10.4.2 Class B Products

l FCC Part 15 (Class B) – Radiated & Conducted Emissions (USA)
l CAN ICES-3(B)/NMB-3(B) – Radiated & Conducted Emissions (Canada)
l CISPR 22 – Radiated & Conducted Emissions (International)
l EN55022: 2010 – Radiated & Conducted Emissions (European Union)
l EN55024: 2010 – Immunity (European Union)
l EN55032: 2015 Class B Radiated and Conducted Emissions requirements (European Union)
l EMC Directive 2004/108/EC (European Union)
l VCCI (Class B)– Radiated & Conducted Emissions (Japan) (excluding optics)
l CNS13438 (Class B)-2006 – Radiated & Conducted Emissions (Taiwan) (excluding optics)
l AS/NZS CISPR 22:2009 + A1:2010 Class B and CISPR 32:2015 for Radiated and Conducted
Emissions requirements (Australia/New Zealand)
l KN22; KN24 – Korean emissions and immunity
l NRRA No. 2012-13 (2012.06.28), NRRA Notice No. 2012-14 (2012.06.28) (Korea)

10.5 Hazardous Substances Compliance

The following standards may apply:
l EU REACH directive
l EU WEEE directive
l EU RoHS directive
l China RoHS directive
l BSMI CNS15663: Taiwan RoHS

10.6 Regulatory Compliance Markings

When required, these products are provided with the following Product Certification Markings:
l UL Recognition Mark for USA and Canada
l CE Mark
l EU WEEE Logo
l FCC markings
l VCCI marking
l Australian C-Tick Mark
l Korea MSIP mark
l Taiwan BSMI mark
l People's Republic of China "EFUP" mark

705831 124
Intel® Ethernet Adapters and Devices User Guide

10.7 FCC Class A User Information

The Class A products listed above comply with Part 15 of the FCC Rules. Operation is subject to the
following two conditions:

1. This device may not cause harmful interference.

2. This device must accept any interference received, including interference that may cause undesired
operation.

NOTE: This equipment has been tested and found to comply with the limits for a Class A digital
device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at his own
expense.

CAUTION: If the device is changed or modified without permission from Intel, the user may void
his or her authority to operate the equipment.

10.7.1 Canadian Compliance (Industry Canada)

CAN ICES-3(A)/NMB-3(A)

10.7.2 VCCI Class A Statement

10.7.3 BSMI Class A Statement

705831 125
Intel® Ethernet Adapters and Devices User Guide

10.7.4 KCC Notice Class A (Republic of Korea Only)

10.7.5 BSMI Class A Notice (Taiwan)

10.8 FCC Class B User Information

This equipment has been tested and found to comply with the limits for a Class B digital device pursuant to
Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful
interference in a residential installation. This equipment generates, uses and can radiate radio frequency
energy and, if not installed and used in accordance with the instructions, may cause harmful interference
to radio communications. However, there is no guarantee that interference will not occur in a particular
installation.

If this equipment does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try to correct the interference
by one or more of the following measures:
l Reorient or relocate the receiving antenna.
l Increase the separation between the equipment and receiver.
l Connect the equipment into an outlet on a circuit different from that to which the receiver is
connected.
l Consult the dealer or an experienced radio/TV technician for help.

CAUTION: If the device is changed or modified without permission from Intel, the user may void
his or her authority to operate the equipment.

705831 126
Intel® Ethernet Adapters and Devices User Guide

NOTE: This device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions: (1) this device may not cause harmful interference, and (2) this device must accept
any interference received, including interference that may cause undesired operation.

10.8.1 Electromagnetic Compatibility Notices

10.8.1.1 FCC Declaration of Conformity Statement

The following products have been tested to Comply with FCC Standards for Home or Office Use:

PRO/1000 PT, PRO/1000 GT, Gigabit PT, I210-T1, I340-T2/T4, and I350-T2/T4.

10.8.1.2 Canadian Compliance (Industry Canada)

CAN ICES-3 (B)/NMB-3 (B)

10.8.2 VCCI Class B Statement (Japan)

10.8.3 KCC Notice Class B (Republic of Korea Only)

705831 127
Intel® Ethernet Adapters and Devices User Guide

10.9 EU WEEE Logo

10.10 Manufacturer Declaration European Community

10.10.1 Manufacturer Declaration

Intel Corporation declares that the equipment described in this document is in conformance with the
requirements of the European Council Directive listed below:
l Low Voltage Directive 2006/95/EC
l EMC Directive2004/108/EC
l RoHS Directive 2011/65/EU

These products follow the provisions of the European Directive 1999/5/EC.

Dette produkt er i overensstemmelse med det europæiske direktiv 1999/5/EC.

Dit product is in navolging van de bepalingen van Europees Directief 1999/5/EC.

Tämä tuote noudattaa EU-direktiivin 1999/5/EC määräyksiä.

Ce produit est conforme aux exigences de la Directive Européenne 1999/5/EC.

Dieses Produkt entspricht den Bestimmungen der Europäischen Richtlinie 1999/5/EC.

Þessi vara stenst reglugerð Evrópska Efnahags Bandalagsins númer 1999/5/EC.

Questo prodotto è conforme alla Direttiva Europea 1999/5/EC.

Dette produktet er i henhold til bestemmelsene i det europeiske direktivet 1999/5/EC.

Este produto cumpre com as normas da Diretiva Européia 1999/5/EC.

Este producto cumple con las normas del Directivo Europeo 1999/5/EC.

Denna produkt har tillverkats i enlighet med EG-direktiv 1999/5/EC.

This declaration is based upon compliance of the Class A products listed above to the following standards:
EN 55022:2010 (CISPR 22 Class A) RF Emissions Control.
EN 55024:2010 (CISPR 24) Immunity to Electromagnetic Disturbance.
EN 60950-1:2006/A11:2009A1:2010/A12:2011 Information Technology Equipment- Safety-Part 1:
General Requirements.
EN 50581:2012 - Technical documentation for the assessment of electrical and electronic products with
respect to the restriction of hazardous substances.

This declaration is based upon compliance of the Class B products listed above to the following standards:
EN 55022:2010 (CISPR 22 Class B) RF Emissions Control.
EN 55024:2010 (CISPR 24) Immunity to Electromagnetic Disturbance.
EN 60950-1:2006/A11:2009/A1:2010/A12:2011 Information Technology Equipment- Safety-Part 1:

705831 128
Intel® Ethernet Adapters and Devices User Guide

General Requirements.
EN 50581:2012 - Technical documentation for the assessment of electrical and electronic products with
respect to the restriction of hazardous substances.

WARNING: In a domestic environment, Class A products may cause radio interference, in which case the user may
be required to take adequate measures.

Responsible Party

Intel Corporation, Mailstop JF3-446

5200 N.E. Elam Young Parkway
Hillsboro, OR 97124-6497
Phone 1-800-628-8686

10.11 China RoHS Declaration

10.12 Class 1 Laser Products

Server adapters listed above may contain laser devices for communication use. These devices are
compliant with the requirements for Class 1 Laser Products and are safe in the intended use. In normal
operation the output of these laser devices does not exceed the exposure limit of the eye and cannot cause
harm.

For continued safe operation in case of an abnormal circumstance, always have the provided laser
connector cover in place or a compatible fiber optics cable properly connected when power is available to
the product.

705831 129
Intel® Ethernet Adapters and Devices User Guide

The Laser device must be factory serviced ONLY by the responsible manufacturer! NO adjustments, service
or maintenance is to be performed otherwise.

CAUTION: Use of controls or adjustments or performance of procedures other than those

specified herein may result in hazardous radiation exposure.

These Class 1 Laser devices:

Comply with FDA/CDRH per CFR21, subchapter J.

Comply with IEC 60825-1:2007

10.13 End-of-Life / Product Recycling

Product recycling and end-of-life take-back systems and requirements vary by country.

Contact the retailer or distributor of this product for information about product recycling and/or take-back.

705831 130
Intel® Ethernet Adapters and Devices User Guide

11. Specifications

11.1 Indicator Lights

Intel Ethernet adapters feature indicator lights on the adapter backplate that serve to indicate activity and
the status of the adapter board. The following tables define the meaning for the possible states of the
indicator lights for each adapter board.

Subsections are organized by number of ports and types of connections.

All drawings are representational.

11.1.1 Single Port QSFP28 Adapters

Drawing Label Indication Meaning

Green Linked at maximum port speed

Yellow Linked at less than maximum port speed

ACT/LNK

Blinking On/Off Actively transmitting or receiving data

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-C-Q1

705831 131
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Operating at maximum port speed

LNK
Yellow Linked at less than maximum port speed

Green Flashing Data activity

ACT
Off No activity

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-C-Q1 for OCP

Intel® Ethernet Network Adapter E810-C-Q1 for OCP 3.0

11.1.2 Single Port QSFP+ Adapters

Drawing Label Indication Meaning

Green Linked at 40 Gb

Yellow Linked at 1/10 Gb

ACT/LNK

Blinking On/Off Actively transmitting or receiving data

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter XL710-Q1

705831 132
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Linked at 10 Gb

Yellow Linked at 1 Gb

ACT/LNK

Blinking On/Off Actively transmitting or receiving data

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter X520-Q1

11.1.3 Dual Port QSFP28 Adapters

Drawing Label Indication Meaning

Green Operating at maximum port speed

Link

Yellow Operating at less than maximum port speed

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-C-Q2T

705831 133
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Linked at maximum port speed

GRN 100G

Yellow Linked at less than maximum port speed

Blinking On/Off Actively transmitting or receiving data

ACTIVITY

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-2C-Q2

Drawing Label Indication Meaning

Green Linked at maximum port speed

Yellow Linked at less than maximum port speed

ACT/LNK

Blinking On/Off Actively transmitting or receiving data

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-C-Q2

705831 134
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Operating at maximum port speed

LNK
Yellow Linked at less than maximum port speed

Green flashing Data activity

ACT
Off No activity

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-C-Q2 for OCP 3.0

Intel® Ethernet Network Adapter E810-L-Q2 for OCP 3.0

11.1.4 Dual Port QSFP+ Adapters

Drawing Label Indication Meaning

Green Linked at 40 Gb

Yellow Linked at 1/10 Gb

ACT/LNK

Blinking On/Off Actively transmitting or receiving data

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter XL710-Q2

705831 135
Intel® Ethernet Adapters and Devices User Guide

11.1.5 Dual Port SFP28 Adapters

Drawing Label Indication Meaning

Green Linked at maximum port speed

GRN 25G

Yellow Linked at less than maximum port speed

Blinking On/Off Actively transmitting or receiving data

ACTIVITY

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-XXV-2

Drawing Label Indication Meaning

Green Operating at maximum port speed

LNK
Yellow Linked at less than maximum port speed

Green flashing Data activity

ACT
Off No activity

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-XXV-2 for OCP 3.0

Intel® Ethernet Network Adapter XXV710-DA2 for OCP 3.0

705831 136
Intel® Ethernet Adapters and Devices User Guide

11.1.6 Dual Port SFP/SFP+ Adapters

Drawing Label Indication Meaning

Green Operating at maximum port speed

LNK
Yellow Linked at less than maximum port speed

Green flashing Data activity

ACT
Off No activity

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter X710-2 for OCP NIC 3.0

Drawing Label Indication Meaning

Green Linked at 10 Gb

LNK

Yellow Linked at 1 Gb

Blinking On/Off Actively transmitting or receiving data

ACT

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter X710-2

705831 137
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

On Linked to the LAN

GRN 10G
(A or B): Green
Off Not linked to the LAN

Blinking On/Off Actively transmitting or receiving data

ACT/LNK
(A or B): Green
Off No link

These indicator lights apply to the following devices:

Intel® 10 Gigabit AF DA Dual Port Server Adapter

Intel® Ethernet Server Adapter X520 series of adapters

Intel® Ethernet Network Adapter X722-2

11.1.7 Quad Port SFP28 Adapters

Drawing Label Indication Meaning

Green Linked at 25 Gb

GRN 25G

Yellow Linked at 10 Gb or 1 Gb

Blinking On/Off Actively transmitting or receiving data

ACTIVITY

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-XXV-4

705831 138
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Operating at maximum port speed

Link

Yellow Operating at less than maximum port speed

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-XXV-4T

Drawing Label Indication Meaning

Green Linked at maximum port speed

Link

Yellow Linked at less than maximum port speed

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter E810-XXV-4 for OCP 3.0

705831 139
Intel® Ethernet Adapters and Devices User Guide

11.1.8 Quad Port SFP/SFP+ Adapters

Drawing Label Indication Meaning

Green Linked at maximum port speed

Link

Yellow Linked at less than maximum port speed

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter X710-4 for OCP NIC 3.0

Drawing Label Indication Meaning

Green Linked at 10 Gb

LNK

Yellow Linked at 1 Gb

Blinking On/Off Actively transmitting or receiving data

ACT

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter X710-4

705831 140
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Linked at 10 Gb

Yellow Linked at 1 Gb

ACT/LNK

Blinking On/Off Actively transmitting or receiving data

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter X520-4

Intel® Ethernet Network Adapter X722-4

11.1.9 Single Port Copper Adapters

Drawing Label Indication Meaning

Green Linked at 10 Gb

Link Yellow Linked at 1 Gb

Off Linked at 100 Mbps

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter X550-T1

705831 141
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Linked at 10 Gb

Link Yellow Linked at 1 Gb

Off No link

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter X540-T1

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

Green
Data activity
blinking

ACT/LNK
Off No link

Identity. Use the "Identify Adapter" button in Intel PROSet or the

Green
BLINK command in IBAUtil to control blinking. See Intel PROSet Help
blinking
for more information.

Green 10 Gbps

1Gig/10Gig Yellow 1 Gbps

Off No link

Over temperature event occurred. The adapter will be shut down to

FAN FAIL Red
avoid damage.

These indicator lights apply to the following devices:

Intel® 10 Gigabit AT Server Adapter

705831 142
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Linked at 2.5 Gbps

Link Speed Amber Linked at 1 Gbps

Off Linked at 100 Mbps or 10 Mbps

Green Linked

Activity Green flashing Actively transmitting or receiving data

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter I225-T1

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

Green
ACT/LNK Data activity
flashing

Off No link

Off 10 Mbps

Green 100 Mbps

10=OFF
100=GRN
1000=ORG Orange 1000 Mbps

Orange Identity. Use the "Identify Adapter" button in Intel PROSet to control
flashing blinking. See Intel PROSet Help for more information.

These indicator lights apply to the following devices:

Intel® PRO/1000 PT Server Adapter

705831 143
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

Green
Data activity
flashing
ACT/LNK
Off No link

Yellow Identity. Use the "Identify Adapter" button in Intel PROSet to

flashing control blinking. See Intel PROSet Help for more information.

Off 10 Mbps
10=OFF
100=GRN Green 100 Mbps
1000=ORG
Orange 1000 Mbps

These indicator lights apply to the following devices:

Intel® PRO/1000 MT Server Adapter

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

Green
Data activity
flashing
ACT/LNK
Off No link

Yellow Identity. Use the "Identify Adapter" button in Intel PROSet to

flashing control blinking. See Intel PROSet Help for more information.

Off 10 Mbps

10/100/1000 Green 100 Mbps

Orange 1000 Mbps

These indicator lights apply to the following devices:

PRO/1000 T, and PRO/1000 MT Desktop Adapters

705831 144
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

Green
Data activity
flashing
ACT/LNK
Off No link

Yellow Identity. Use the "Identify Adapter" button in Intel PROSet to

flashing control blinking. See Intel PROSet Help for more information.

Off 10 Mbps

10/100/1000 Green 100 Mbps

Yellow 1000 Mbps

These indicator lights apply to the following devices:

Intel® PRO/1000 XT Server Adapter

Drawing Label Indication Meaning

Identity. Use the "Identify Adapter" button in Intel PROSet to

not labeled Flashing
control blinking. See Intel PROSet Help for more information.

On The adapter is connected to a valid link partner

LNK
Off No link

On Data is being transmitted or received

ACT
Off No data activity

Off 10 Mbps

10/100/1000 Green 100 Mbps

Yellow 1000 Mbps

These indicator lights apply to the following devices:

Intel® PRO/1000 T Server Adapter

705831 145
Intel® Ethernet Adapters and Devices User Guide

11.1.10 Dual Port Copper Adapters

Drawing Label Indication Meaning

Green Linked at 10 Gbps

Link Yellow Linked at slower than 10 Gbps

Off No link

Blinking On/Off Actively transmitting or receiving data

Activity
Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter X710-T2L for OCP 3.0

Drawing Label Indication Meaning

Green Linked at 10 Gbps

Link Yellow Linked at slower than 10 Gbps

Off No link

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter X710-T2L

705831 146
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Linked at 10 Gbps

Link Yellow Linked at slower than 10 Gbps

Off No link

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter X550-T2

Drawing Label Indication Meaning

Green Linked at 10 Gb

Link Yellow Linked at slower than 10 Gb

Off No link

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Server Adapter X520-T2

705831 147
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

ACT/LNK Green flashing Data activity

Off No link

Off 10 Mbps

Green 100 Mbps

10/100/1000
Yellow 1000 Mbps

Orange Identity. Use the "Identify Adapter" button in Intel PROSet to

flashing control blinking. See Intel PROSet Help for more information.

These indicator lights apply to the following devices:

Intel® Ethernet Server Adapter I350-T2, I340-T2, PRO/1000 P, and PT Dual Port Server Adapters

Drawing Label Indication Meaning

Green on The port is connected to a valid link partner

Green
Data activity
flashing
ACT/LNK
Yellow Identity. Use the "Identify Adapter" button in Intel PROSet to control
flashing blinking. See Intel PROSet Help for more information.

Off No link

Orange 1000 Mbps

10=OFF
100=GRN Green 100 Mbps
1000=ORG
Off 10 Mbps

These indicator lights apply to the following devices:

Intel® PRO/1000 MT and GT Dual Port Server Adapters

705831 148
Intel® Ethernet Adapters and Devices User Guide

11.1.11 Quad Port Copper Adapters

Drawing Label Indication Meaning

Green Linked at 1 Gbps

Link Yellow Linked at slower than 1 Gbps

Off No link

Blinking On/Off Actively transmitting or receiving data

Activity
Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter I350-T4 for OCP NIC 3.0

Drawing Label Indication Meaning

Green Linked at 10 Gbps

Link Yellow Linked at slower than 1 Gbps

Off No link

Blinking On/Off Actively transmitting or receiving data

Activity
Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter X710-T4L for OCP 3.0

Intel® Ethernet Network Adapter I710-T4L for OCP 3.0

705831 149
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green Linked at 10 Gbps

Link Yellow Linked at slower than 10 Gbps

Off No link

Blinking On/Off Actively transmitting or receiving data

Activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Network Adapter X710-T4L

Intel® Ethernet Network Adapter I710-T4L

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

ACT Green flashing Data activity

Off No link

Green 10 Gbps

LNK Yellow 1 Gbps

Off 100 Mbps

These indicator lights apply to the following devices:

Intel® Ethernet Converged Network Adapter X710-T4

705831 150
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

ACT/LNK Green flashing Data activity

Off No link

Green 100 Mbps

Yellow 1000 Mbps

10/100/1000
Orange Identity. Use the "Identify Adapter" button in Intel® PROSet to
flashing control blinking. See Intel PROSet Help for more information.

Off 10 Mbps

These indicator lights apply to the following devices:

Intel® Ethernet Server Adapter I350-T4, I340-T4, and PRO/1000 PT Quad Port LP Server Adapters

Drawing Label Indication Meaning

Green on The port is connected to a valid link partner

Green
Data activity
Top LED flashing

ACT/LNK Orange Identity. Use the "Identify Adapter" button in Intel® PROSet to control
flashing blinking. See Intel PROSet Help for more information

Off No link

Orange 1000 Mbps

Bottom LED
Green 100 Mbps
10/100/1000
Off 10 Mbps

These indicator lights apply to the following devices:

Intel® PRO/1000 MT, GT and PT Quad Port Server Adapters

705831 151
Intel® Ethernet Adapters and Devices User Guide

11.1.12 Single Port Fiber Adapters

Drawing Label Indication Meaning

On The adapter is connected to a valid link partner

Adapter is actively passing traffic.

ACT/LNK Blinking Identity. Use the "Identify Adapter" button in Intel PROSet to control
blinking. See Intel PROSet Help for more information.

Off No link

These indicator lights apply to the following devices:

Intel® 10 Gigabit XF SR and LR Server Adapters

Drawing Label Indication Meaning

On The adapter is connected to a valid link partner

Adapter is actively passing traffic.

ACT/LNK Blinking Identity. Use the "Identify Adapter" button in Intel PROSet to
control blinking. See Intel PROSet Help for more information.

Off No link

These indicator lights apply to the following devices:

Intel® PRO/1000 MF and PF Server Adapters

705831 152
Intel® Ethernet Adapters and Devices User Guide

Drawing Label Indication Meaning

On The adapter is connected to a valid link partner

LNK

Off No link

On Data is being transmitted or received

ACT

Off No data activity

not Identity. Use the "Identify Adapter" button in Intel PROSet to

Flashing
labeled control blinking. See Intel PROSet Help for more information.

These indicator lights apply to the following devices:

Intel® PRO/1000 XF Server Adapter

Drawing Label Indication Meaning

TX On The adapter is sending data

RX On The adapter is receiving data

The adapter is connected to a valid link partner and is receiving

On
link pulses
LNK

Off No link

not Identity. Use the "Identify Adapter" button in Intel PROSet to

Flashing
labeled control blinking. See Intel PROSet Help for more information.

These indicator lights apply to the following devices:

Intel® PRO/1000F Server Adapter

705831 153
Intel® Ethernet Adapters and Devices User Guide

11.1.13 Dual Port Fiber Adapters

Drawing Label Indication Meaning

On The adapter is connected to a valid link partner

Adapter is actively passing traffic.

ACT/LNK Blinking Identity. Use the "Identify Adapter" button in Intel PROSet to control
blinking. See Intel PROSet Help for more information.

Off No link

These indicator lights apply to the following devices:

Intel® 10 Gigabit XF SR Dual Port Server Adapters

Drawing Label Indication Meaning

On The adapter is connected to a valid link partner

Adapter is actively passing traffic.

ACT/LNK Blinking Identity. Use the "Identify Adapter" button in Intel PROSet to
control blinking. See Intel PROSet Help for more information.

Off No link

These indicator lights apply to the following devices:

Intel® PRO/1000 MF, and PF Dual Port Server Adapters

705831 154
Intel® Ethernet Adapters and Devices User Guide

11.1.14 Quad Port Fiber Adapters

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

GRN=1G Green flashing Data activity

Off No link

These indicator lights apply to the following devices:

Intel® Ethernet Server Adapter I340-F4

Drawing Label Indication Meaning

Green on The adapter is connected to a valid link partner

ACT/LNK Green flashing Data activity

Off No link

These indicator lights apply to the following devices:

Intel® PRO/1000 PF Quad Port Server Adapter

705831 155
Intel® Ethernet Adapters and Devices User Guide

12. Discontinued Support

The following table lists features, devices, or operating systems that were discontinued in a particular
release. Subsequent releases will not support the discontinued feature.

705831 156
Intel® Ethernet Adapters and Devices User Guide

Release What Was Discontinued

Release End of support for:

28.3
l Microsoft Windows Server 2012 and Windows Server 2012 R2
l Intel® I354 Gigabit Ethernet Controller and the e1s driver
l Autorun.exe and its associated files

Release 28.2.3 is the last release that includes drivers for these OSs and devices.

Release End of support for RSS on Microsoft Windows operating systems for the following devices:
28.1
l Intel® Ethernet Connection I217-LM
l Intel® Ethernet Connection I218-LM
l Intel® Ethernet Connection (2) I218-LM
l Intel® Ethernet Connection (3) I218-LM
l Intel® Ethernet Connection I218-LM
l Intel® Ethernet Connection I218-V
l Intel® Ethernet Connection (2) I218-V
l Intel® Ethernet Connection (3) I218-V
l Intel® Ethernet Connection I218-V
l Intel® Ethernet Connection I217-V
l Intel® Ethernet Network Adapter I226-T1
l Intel® Ethernet Network Adapter I226-T1
l Intel® Ethernet Network Adapter I225-T1
l Intel® Ethernet Network Adapter I225-T1
l Intel® Ethernet Controller (2) I225-IT
l Intel® Killer(TM) E3100X 2.5 Gigabit Ethernet Controller
l Intel® Ethernet Controller (2) I225-LM
l Intel® Ethernet Controller (2) I225-LMvP
l Intel® Ethernet Controller (2) I225-V
l Intel® Ethernet Controller (3) I225-IT
l Intel® Killer(TM) E3100X 2.5 Gigabit Ethernet Controller
l Intel® Ethernet Controller (3) I225-LM
l Intel® Ethernet Controller (3) I225-LMvP
l Intel® Ethernet Controller (3) I225-V
l Intel® Ethernet Controller I226-IT
l Intel® Killer(TM) E3100X 2.5 Gigabit Ethernet Controller (3)
l Intel® Ethernet Controller I226-LM
l Intel® Ethernet Controller I226-LMvP
l Intel® Ethernet Controller I226-V
l Intel® Ethernet Controller I225-LM
l Intel® Ethernet Controller I225-V
l Intel® Ethernet Connection (2) I219-LM
l Intel® Ethernet Connection (2) I219-V
l Intel® Ethernet Connection (3) I219-LM
l Intel® Ethernet Connection (4) I219-LM
l Intel® Ethernet Connection (4) I219-V

705831 157
Intel® Ethernet Adapters and Devices User Guide

Release What Was Discontinued

l Intel® Ethernet Connection (5) I219-LM

l Intel® Ethernet Connection (5) I219-V
l Intel® Ethernet Connection I219-LM
l Intel® Ethernet Connection (10) I219-LM
l Intel® Ethernet Connection (11) I219-LM
l Intel® Ethernet Connection (12) I219-LM
l Intel® Ethernet Connection (13) I219-LM
l Intel® Ethernet Connection (14) I219-LM
l Intel® Ethernet Connection (15) I219-LM
l Intel® Ethernet Connection (16) I219-LM
l Intel® Ethernet Connection (17) I219-LM
l Intel® Ethernet Connection (18) I219-LM
l Intel® Ethernet Connection (19) I219-LM
l Intel® Ethernet Connection (20) I219-LM
l Intel® Ethernet Connection (22) I219-LM
l Intel® Ethernet Connection (23) I219-LM
l Intel® Ethernet Connection (24) I219-LM
l Intel® Ethernet Connection (25) I219-LM
l Intel® Ethernet Connection (26) I219-LM
l Intel® Ethernet Connection (27) I219-LM
l Intel® Ethernet Connection (6) I219-LM
l Intel® Ethernet Connection (7) I219-LM
l Intel® Ethernet Connection (8) I219-LM
l Intel® Ethernet Connection (9) I219-LM
l Intel® Ethernet Connection I219-V
l Intel® Ethernet Connection (10) I219-V
l Intel® Ethernet Connection (11) I219-V
l Intel® Ethernet Connection (12) I219-V
l Intel® Ethernet Connection (13) I219-V
l Intel® Ethernet Connection (14) I219-V
l Intel® Ethernet Connection (16) I219-V
l Intel® Ethernet Connection (17) I219-V
l Intel® Ethernet Connection (18) I219-V
l Intel® Ethernet Connection (19) I219-V
l Intel® Ethernet Connection (20) I219-V
l Intel® Ethernet Connection (22) I219-V
l Intel® Ethernet Connection (23) I219-V
l Intel® Ethernet Connection (24) I219-V
l Intel® Ethernet Connection (25) I219-V
l Intel® Ethernet Connection (26) I219-V
l Intel® Ethernet Connection (27) I219-V
l Intel® Ethernet Connection (6) I219-V
l Intel® Ethernet Connection (7) I219-V

705831 158
Intel® Ethernet Adapters and Devices User Guide

Release What Was Discontinued

l Intel® Ethernet Connection (8) I219-V

l Intel® Ethernet Connection (9) I219-V
l Intel® Ethernet Connection (3) I218-LM
l Intel® Ethernet Connection (3) I218-V

Release Release 27.9 is the last release that supports the following:
27.9
l Microsoft Windows 8.1
l Microsoft Windows 10 Version 20H2 (build 19042)
l Microsoft Windows 10 Version 21H1 (build 19043)
l VMWare ESXi 6.5
l VMWare ESXi 6.7
l iw_ixl FreeBSD driver

Release Release 27.5 is the last release that includes the Microsoft e1q driver in your download package. Release 27.6
27.5 removed the e1q driver from the installation package. This affects the following devices:
l Intel® 82575EB Gigabit Network Connection
l Intel® 82575EB Gigabit Backplane Connection
l Intel® Gigabit VT Quad Port Server Adapter
l Intel® 82575EB Multi-Function Network Device
l Intel® 82574L Gigabit Network Connection
l Intel® 82583V Gigabit Network Connection
l Intel® Gigabit CT Desktop Adapter
l Intel® Gigabit CT2 Desktop Adapter
l Intel® 82576 Gigabit Dual Port Network Connection
l Intel® Gigabit ET Dual Port Server Adapter
l Intel® 82576NS Gigabit Ethernet Controller
l Intel® 82576NS Gigabit Network Connection
l Intel® 82576NS SerDes Gigabit Ethernet Controller
l Intel® Gigabit EF Dual Port Server Adapter
l Intel® 82576 Gigabit Dual Port Server Network Connection
l Intel® Gigabit ET Quad Port Server Adapter
l Intel® Gigabit ET2 Quad Port Server Adapter
l Intel® 82576 Gigabit Dual Port Network Connection
l Intel® Gigabit ET Quad Port Mezzanine Card

Release Release 27.0 is the last release that supports the Microsoft Windows v1q driver. This driver will no longer be
27.0 tested or updated. The driver may still be provided in your download package or on your install media for your
convenience.

Release Release 26.7 is the last release that supports Intel® Ethernet Network Adapter E810-XXV-2 for OCP 2.0.
26.7

Release Release 26.4 is the last release that supports the following:
26.4
l SUSE Linux Enterprise Server 11.
l Canonical Ubuntu 16.04
l The Microsoft Windows e1q driver and devices. These drivers will no longer be tested or updated. This
affects devices based on the following:

705831 159
Intel® Ethernet Adapters and Devices User Guide

Release What Was Discontinued

l Intel® 82574L Gigabit Network Connection

l Intel® Gigabit ET2 Quad Port Server Adapter
l Intel® 82575EB Gigabit Backplane Connection
l Intel® 82575EB Gigabit Network Connection
l Intel® 82576 Gigabit Dual Port Network Connection
l Intel® 82576 Gigabit Dual Port Server Network Connection
l Intel® 82576NS Gigabit Ethernet Controller
l Intel® 82576NS SerDes Gigabit Ethernet Controller
l Intel® 82583V Gigabit Network Connection
l Intel® Gigabit CT Desktop Adapter
l Intel® Gigabit CT2 Desktop Adapter
l Intel® Gigabit EF Dual Port Server Adapter
l Intel® Gigabit ET Dual Port Network Connection
l Intel® Gigabit ET Dual Port Server Adapter
l Intel® Gigabit ET Quad Port Mezzanine Card
l Intel® Gigabit ET Quad Port Server Adapter
l Intel® Gigabit VT Quad Port Server Adapter
l Starting with Release 26.4, the following adapters and devices will no longer be tested or updated. The
drivers may still be provided in your download package or on your install media for your convenience.
l Intel® Ethernet Controller X540-AT2
l Intel® Ethernet Controller X540-AT1
l Intel® Ethernet Converged Network Adapter X540-T2
l Intel® Ethernet Converged Network Adapter X540-T1
l Intel® X540 Virtual Function

Release Release 26.3 is the last release that supports the following:
26.3
l Microsoft Windows 10, Version 1803
l Microsoft Windows 10, Version 1903
l Red Hat* Enterprise Linux* (RHEL) 6.x
l The FreeBSD em driver. Maintenance for this driver will be continued by the community.

Release Release 25.2 is the last release that supports the following:
25.2
l DOS tools and diagnostics.
l The 32-bit Microsoft Windows 10 e1d driver. 64-bit Microsoft Windows 10 is still supported. This affects
devices based on the following controllers:
l Intel® Ethernet Connection I217-LM
l Intel® Ethernet Connection I217-V
l Intel® Ethernet Connection I218-LM
l Intel® Ethernet Connection I218-V
l Intel® Ethernet Connection I219-LM
l Intel® Ethernet Connection I219-V
l The Linux e1000e driver. Maintenance for this driver will be continued by the community.

Release Release 25.0 is the last release to support:

25.0
l Microsoft* Windows* 7

705831 160
Intel® Ethernet Adapters and Devices User Guide

Release What Was Discontinued

l Microsoft* Windows Server* 2008 R2

l Intel® QSFP+ Configuration Utility (QCU)
l IOUtil

Release Release 24.4 removed the following from the installation package:
24.4
l Support for PRO/100 devices
l DOS drivers
l UEFI driver support for PCI/PCI-X devices
l Support for WinCE
l Microsoft* Windows* 10 RS3 (NDIS65) Universal Drivers. Please use the NDIS68 drivers.
l Support for FCoE

Release Starting with Release 23.5, the drivers for the following adapters and devices will no longer be tested or updated.
23.5 The drivers may still be provided in your download package or on your install media for your convenience.
l Intel® 82566MM Gigabit Network Connection
l Intel® PRO/1000 PB Dual Port Server Connection
l Intel® PRO/1000 EB Network Connection with I/O Acceleration
l Intel® PRO/1000 EB1 Network Connection with I/O Acceleration
l Intel® PRO/1000 EB Backplane Connection with I/O Acceleration
l Intel® 82567V-3 Gigabit Network Connection
l Intel® 82567V-4 Gigabit Network Connection
l Intel® 82567LM-4 Gigabit Network Connection
l Intel® 82567LF Gigabit Network Connection
l Intel® 82567V Gigabit Network Connection
l Intel® 82567LM-2 Gigabit Network Connection
l Intel® 82567LF-2 Gigabit Network Connection
l Intel® 82567V-2 Gigabit Network Connection
l Intel® 82567LM-3 Gigabit Network Connection
l Intel® 82567LF-3 Gigabit Network Connection
l Intel® 82577LM Gigabit Network Connection
l Intel® 82577LC Gigabit Network Connection
l Intel® 82578DM Gigabit Network Connection
l Intel® 82578DC Gigabit Network Connection
l Intel® 82567LM Gigabit Network Connection
l Intel® 82566DM Gigabit Network Connection
l Intel® 82566DC Gigabit Network Connection
l Intel® 82566MC Gigabit Network Connection
l Intel® PRO/1000 PT Dual Port Network Connection
l Intel® PRO/1000 PT Dual Port Server Adapter
l Intel® PRO/1000 PT Dual Port Server Connection
l Intel® PRO/1000 PF Dual Port Server Adapter
l Intel® PRO/1000 PT Network Connection
l Intel® PRO/1000 PT Server Adapter
l Intel® PRO/1000 PF Network Connection

705831 161
Intel® Ethernet Adapters and Devices User Guide

Release What Was Discontinued

l Intel® PRO/1000 PF Server Adapter

l Intel® PRO/1000 PB Server Connection
l Intel® PRO/1000 PM Network Connection
l Intel® PRO/1000 PL Network Connection
l Intel® PRO/1000 PT Quad Port Server Adapter
l Intel® PRO/1000 PF Quad Port Server Adapter
l Intel® PRO/1000 PT Desktop Adapter
l Intel® PRO/1000 EB1 Backplane Connection with I/O Acceleration
l Intel® PRO/1000 PT Quad Port LP Server Adapter
l Intel® 82566DM-2 Gigabit Network Connection
l Intel® 82562V 10/100 Network Connection
l Intel® 82562V-2 10/100 Network Connection
l Intel® 82562G-2 10/100 Network Connection
l Intel® 82562GT-3 10/100 Network Connection
l Intel® 82562GT-2 10/100 Network Connection
l Intel® 82562GT 10/100 Network Connection
l Intel® 82562G 10/100 Network Connection
l Intel® Gigabit PT Quad Port Server ExpressModule
l Intel® 82566DC-2 Gigabit Network Connection
l Intel® 82598EB 10 Gigabit AF Dual Port Network Connection
l Intel® 10 Gigabit XF SR Dual Port Server Adapter
l Intel® 10 Gigabit XF SR Server Adapter
l Intel® 82598EB 10 Gigabit AF Network Connection
l Intel® 10 Gigabit AT Server Adapter
l Intel® 82598EB 10 Gigabit AT Network Connection
l Intel® 10 Gigabit AT2 Server Adapter
l Intel® 82598EB 10 Gigabit AT2 Network Connection
l Intel® 82598EB 10 Gigabit AT CX4 Network Connection
l Intel® 10 Gigabit SR Dual Port Express Module
l Intel® 10 Gigabit CX4 Dual Port Server Adapter
l Intel® 82598EB 10 Gigabit KX4 Network Connection
l Intel® 10 Gigabit AF DA Dual Port Server Adapter
l Intel® 10 Gigabit XF LR Server Adapter
l Intel® 82598EB 10 Gigabit Dual Port Network Connection

705831 162
Intel® Ethernet Adapters and Devices User Guide

13. Legal Disclaimers

13.1 Software License Agreements

13.1.1 Intel Software Licenses

INTEL SOFTWARE LICENSE AGREEMENT

IMPORTANT - READ BEFORE COPYING, INSTALLING OR USING.

Do not copy, install, or use this software and any associated materials (collectively, the
"Software") provided under this license agreement ("Agreement") until you have carefully
read the following terms and conditions.

By copying, installing, or otherwise using the Software, you agree to be bound by the terms
of this Agreement. If you do not agree to the terms of this Agreement, do not copy, install, or
use the Software.

LICENSES

Please Note:
l If you are a network or system administrator, the "Site License" below shall apply to you.
l If you are an end user, the "Single User License" shall apply to you.
l If you are an original equipment manufacturer (OEM), the "OEM License" shall apply to you.

SITE LICENSE: You may copy the Software onto your organization's computers for your organization's
use, and you may make a reasonable number of back-up copies of the Software, subject to these
conditions:

1. This Software is licensed for use only in conjunction with (a) physical Intel
component products, and (b) virtual ("emulated") devices designed to appear as Intel
component products to a Guest operating system running within the context of a
virtual machine. Any other use of the Software, including but not limited to use with
non-Intel component products, is not licensed hereunder.
2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to
you a non-exclusive, non-assignable, copyright license to use the Software.
3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as
provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
4. You may not reverse engineer, decompile, or disassemble the Software.
5. The Software may include portions offered on terms differing from those set out here, as set out in a
license accompanying those portions.

SINGLE USER LICENSE: You may copy the Software onto a single computer for your personal use, and
you may make one back-up copy of the Software, subject to these conditions:

1. This Software is licensed for use only in conjunction with (a) physical Intel
component products, and (b) virtual ("emulated") devices designed to appear as Intel
component products to a Guest operating system running within the context of a
virtual machine. Any other use of the Software, including but not limited to use with
non-Intel component products, is not licensed hereunder.

705831 163
Intel® Ethernet Adapters and Devices User Guide

2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to
you a non-exclusive, non-assignable, copyright license to use the Software.
3. You may not copy, modify, rent, sell, distribute, or transfer any part of the Software except as
provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
4. You may not reverse engineer, decompile, or disassemble the Software.
5. The Software may include portions offered on terms differing from those set out here, as set out in a
license accompanying those portions.

OEM LICENSE: You may reproduce and distribute the Software only as an integral part of or incorporated
in your product, as a standalone Software maintenance update for existing end users of your products,
excluding any other standalone products, or as a component of a larger Software distribution, including but
not limited to the distribution of an installation image or a Guest Virtual Machine image, subject to these
conditions:

1. This Software is licensed for use only in conjunction with (a) physical Intel
component products, and (b) virtual ("emulated") devices designed to appear as Intel
component products to a Guest operating system running within the context of a
virtual machine. Any other use of the Software, including but not limited to use with
non-Intel component products, is not licensed hereunder.
2. Subject to all of the terms and conditions of this Agreement, Intel Corporation ("Intel") grants to
you a non-exclusive, non-assignable, copyright license to use the Software.
3. You may not copy, modify, rent, sell, distribute or transfer any part of the Software except as
provided in this Agreement, and you agree to prevent unauthorized copying of the Software.
4. You may not reverse engineer, decompile, or disassemble the Software.
5. You may only distribute the Software to your customers pursuant to a written license agreement.
Such license agreement may be a "break-the-seal" license agreement. At a minimum such license
shall safeguard Intel's ownership rights to the Software.
6. You may not distribute, sublicense or transfer the Source Code form of any components of the
Software and derivatives thereof to any third party without the express written consent of Intel.
7. The Software may include portions offered on terms differing from those set out here, as set out in a
license accompanying those portions.

LICENSE RESTRICTIONS. You may NOT: (i) use or copy the Software except as provided in this
Agreement; (ii) rent or lease the Software to any third party; (iii) assign this Agreement or transfer the
Software without the express written consent of Intel; (iv) modify, adapt, or translate the Software in
whole or in part except as provided in this Agreement; (v) reverse engineer, decompile, or disassemble the
Software; (vi) attempt to modify or tamper with the normal function of a license manager that regulates
usage of the Software; (vii) distribute, sublicense or transfer the Source Code form of any components of
the Software and derivatives thereof to any third party without the express written consent of Intel; (viii)
permit, authorize, license or sublicense any third party to view or use the Source Code; (ix) modify or
distribute the Source Code or Software so that any part of it becomes subject to an Excluded License. (An
"Excluded License" is one that requires, as a condition of use, modification, or distribution, that (a) the
code be disclosed or distributed in source code form; or (b) others have the right to modify it.); (x) use or
include the Source Code or Software in deceptive, malicious or unlawful programs.

NO OTHER RIGHTS. No rights or licenses are granted by Intel to you, expressly or by implication, with
respect to any proprietary information or patent, copyright, mask work, trademark, trade secret, or other
intellectual property right owned or controlled by Intel, except as expressly provided in this Agreement.
Except as expressly provided herein, no license or right is granted to you directly or by implication,

705831 164
Intel® Ethernet Adapters and Devices User Guide

inducement, estoppel, or otherwise. Specifically, Intel grants no express or implied right to you under Intel
patents, copyrights, trademarks, or other intellectual property rights.

OWNERSHIP OF SOFTWARE AND COPYRIGHTS. The Software is licensed, not sold. Title to all copies
of the Software remains with Intel. The Software is copyrighted and protected by the laws of the United
States and other countries and international treaty provisions. You may not remove any copyright notices
from the Software. You agree to prevent any unauthorized copying of the Software. Intel may make
changes to the Software, or to items referenced therein, at any time without notice, but is not obligated to
support or update the Software.

ADDITIONAL TERMS FOR PRE-RELEASE SOFTWARE. If the Software you are installing or using
under this Agreement is pre-commercial release or is labeled or otherwise represented as "alpha-" or
"beta-" versions of the Software ("pre-release Software"), then the following terms apply. To the extent
that any provision in this Section conflicts with any other term(s) or condition(s) in this Agreement with
respect to pre-release Software, this Section shall supersede the other term(s) or condition(s), but only to
the extent necessary to resolve the conflict. You understand and acknowledge that the Software is pre-
release Software, does not represent the final Software from Intel, and may contain errors and other
problems that could cause data loss, system failures, or other errors. The pre-release Software is provided
to you "as-is" and Intel disclaims any warranty or liability to you for any damages that arise out of the use
of the pre-release Software. You acknowledge that Intel has not promised that pre-release Software will be
released in the future, that Intel has no express or implied obligation to you to release the pre-release
Software and that Intel may not introduce Software that is compatible with the pre-release Software. You
acknowledge that the entirety of any research or development you perform that is related to the pre-
release Software or to any product making use of or associated with the pre-release Software is done at
your own risk. If Intel has provided you with pre-release Software pursuant to a separate written
agreement, your use of the pre-release Software is also governed by such agreement.

LIMITED MEDIA WARRANTY. If the Software has been delivered by Intel on physical media, Intel
warrants the media to be free from material physical defects for a period of ninety days after delivery by
Intel. If such a defect is found, return the media to Intel for replacement or alternate delivery of the
Software as Intel may select.

EXCLUSION OF OTHER WARRANTIES. EXCEPT AS PROVIDED ABOVE, THE SOFTWARE IS

PROVIDED "AS IS" WITHOUT ANY EXPRESS OR IMPLIED WARRANTY OF ANY KIND
INCLUDING WARRANTIES OF MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A
PARTICULAR PURPOSE. Intel does not warrant or assume responsibility for the accuracy or
completeness of any information, text, graphics, links, or other items contained within the Software.

LIMITATION OF LIABILITY. IN NO EVENT SHALL INTEL OR ITS SUPPLIERS BE LIABLE FOR

ANY DAMAGES WHATSOEVER (INCLUDING, WITHOUT LIMITATION, LOST PROFITS,
BUSINESS INTERRUPTION, OR LOST INFORMATION) ARISING OUT OF THE USE OF OR
INABILITY TO USE THE SOFTWARE, EVEN IF INTEL HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME JURISDICTIONS PROHIBIT EXCLUSION OR
LIMITATION OF LIABILITY FOR IMPLIED WARRANTIES OR CONSEQUENTIAL OR
INCIDENTAL DAMAGES, SO THE ABOVE LIMITATION MAY NOT APPLY TO YOU. YOU MAY
ALSO HAVE OTHER LEGAL RIGHTS THAT VARY FROM JURISDICTION TO JURISDICTION. In
the event that you use the Software in conjunction with a virtual ("emulated") device designed to appear
as an Intel component product, you acknowledge that Intel is neither the author nor the creator of the
virtual ("emulated") device. You understand and acknowledge that Intel makes no representations about
the correct operation of the Software when used with a virtual ("emulated") device, that Intel did not
design the Software to operate in conjunction with the virtual ("emulated") device, and that the Software
may not be capable of correct operation in conjunction with the virtual ("emulated") device. You agree to
assume the risk that the Software may not operate properly in conjunction with the virtual ("emulated")
device. You agree to indemnify and hold Intel and its officers, subsidiaries and affiliates harmless against all

705831 165
Intel® Ethernet Adapters and Devices User Guide

claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly,
any claim of product liability, personal injury or death associated with the use of the Software in
conjunction with the virtual ("emulated") device, even if such claim alleges that Intel was negligent
regarding the design or manufacture of the Software.

UNAUTHORIZED USE.THE SOFTWARE IS NOT DESIGNED, INTENDED, OR AUTHORIZED FOR

USE IN ANY TYPE OF SYSTEM OR APPLICATION IN WHICH THE FAILURE OF THE SOFTWARE
COULD CREATE A SITUATION WHERE PERSONAL INJURY OR DEATH MAY OCCUR (E.G
MEDICAL SYSTEMS, LIFE SUSTAINING OR LIFE SAVING SYSTEMS). If you use the Software for
any such unintended or unauthorized use, you shall indemnify and hold Intel and its officers, subsidiaries
and affiliates harmless against all claims, costs, damages, and expenses, and reasonable attorney fees
arising out of, directly or indirectly, any claim of product liability, personal injury or death associated with
such unintended or unauthorized use, even if such claim alleges that Intel was negligent regarding the
design or manufacture of the part.

TERMINATION OF THIS AGREEMENT. Intel may terminate this Agreement at any time if you violate
its terms. Upon termination, you will immediately destroy the Software or return all copies of the Software
to Intel.

APPLICABLE LAWS. Claims arising under this Agreement shall be governed by the laws of the State of
California, without regard to principles of conflict of laws. You agree that the terms of the United Nations
Convention on Contracts for the Sale of Goods do not apply to this Agreement. You may not export the
Software in violation of applicable export laws and regulations. Intel is not obligated under any other
agreements unless they are in writing and signed by an authorized representative of Intel.

GOVERNMENT RESTRICTED RIGHTS. The enclosed Software and documentation were developed at
private expense, and are provided with "RESTRICTED RIGHTS." Use, duplication, or disclosure by the
Government is subject to restrictions as set forth in FAR 52.227-14 and DFARS 252.227-7013 et seq. or
its successor. The use of this product by the Government constitutes acknowledgment of Intel’s
proprietary rights in the Software. Contractor or Manufacturer is Intel.

LANGUAGE; TRANSLATIONS. In the event that the English language version of this Agreement is
accompanied by any other version translated into any other language, such translated version is provided
for convenience purposes only and the English language version shall control.

13.1.2 Third-Party Licenses

Portions of this release may include software distributed under the following licenses.

13.1.2.1 Open Toolkit Library (OpenTK)

The Open Toolkit library license

Copyright (c) 2006 - 2009 The Open Toolkit library.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without
limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so, subject to the following
conditions

The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR

705831 166
Intel® Ethernet Adapters and Devices User Guide

PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE

LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

Third parties

* The Open Toolkit library includes portions of the Mono class library, which are covered by the following
license:

Copyright (c) 2004 Novell, Inc.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without
limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the
Software, and to permit persons to whom the Software is furnished to do so, subject to the following
conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions
of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT
OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

* Half-to-Single and Single-to-Half conversions are covered by the following license:

Copyright (c) 2002, Industrial Light & Magic, a division of Lucas Digital Ltd. LLC. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided
that the following conditions are met:
l Redistributions of source code must retain the above copyright notice, this list of conditions and the
following disclaimer.
l Redistributions in binary form must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials provided with the distribution.
l Neither the name of Industrial Light & Magic nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

13.1.2.2 RSA Data Security-MD5 Message

RSA Data Security

Copyright (C) 1991-2, RSA Data Security, Inc. Created 1991. All rights reserved.

705831 167
Intel® Ethernet Adapters and Devices User Guide

License to copy and use this software is granted provided that it is identified as the "RSA Data Security, Inc.
MD5 Message-Digest Algorithm" in all material mentioning or referencing this software or this function.

License is also granted to make and use derivative works provided that such works are identified as
"derived from the RSA Data Security, Inc. MD5 Message-Digest Algorithm" in all material mentioning or
referencing the derived work.

RSA Data Security, Inc. makes no representations concerning either the merchantability of this software
or the suitability of this software for any particular purpose. It is provided "as is" without express or implied
warranty of any kind.

These notices must be retained in any copies of any part of this documentation and/or software.

13.2 Copyright and Legal Disclaimers

Copyright © 2002 - 2023 Intel Corporation. All rights reserved.

Intel Corporation, 5200 N.E. Elam Young Parkway, Hillsboro, OR 97124-6497 USA

Intel Corporation assumes no responsibility for errors or omissions in this document. Nor does Intel make
any commitment to update the information contained herein.

Intel and the Intel logo are trademarks of Intel Corporation or its subsidiaries in the U.S. and/or other
countries.

*Other names and brands may be claimed as the property of others.

13.3 Warranty Information

This section describes the Limited Lifetime Hardware Warranty for Retail Intel® Ethernet Adapters.

13.3.1 Warranty Change Effective January 1, 2018

Intel Adapters that are discontinued will adhere to a 5-year warranty period from the date of Intel’s
announcement of end of life or discontinuance. Discontinued adapters that currently fall outside the 5-
year period are no longer under Warranty. This change will be retroactive for all Intel Adapters.

Follow this link to view a full list of discontinued Intel Adapters that fall outside the 5-year warranty period
and are no longer under Warranty: List of Discontinued Retail Intel® Ethernet Adapters

Intel Adapters that are still active and shipping will continue to adhere to the Limited Lifetime Warranty
policy.

NOTE: If you are a consumer under the Australian Consumer Law, this warranty does not apply to
you.

Visit Australian Limited Lifetime Hardware Warranty to view the limited warranty applicable to
Australian consumers.

13.3.2 INTEL® TERMS AND CONDITIONS OF WARRANTY, SUPPORT AND

SERVICES
These Intel® Terms and Conditions of Warranty, Support and Services (“Terms and Conditions of Service”)
govern the warranty and support services provided by Intel to the original end-user (“Customer”) that has
purchased Intel® Adapter Products (“Products”) directly from Intel Corporation (“Intel”) or indirectly from
an authorized reseller or distributor of Intel (“Authorized Seller”). Unless otherwise agreed in writing by

705831 168
Intel® Ethernet Adapters and Devices User Guide

Intel, any request by Customer for warranty and support services for Products will be accepted only on the
terms and conditions herein, notwithstanding any terms or conditions contained in or referenced on any
pre-printed Customer purchase order or similar order documentation. Except to the extent set forth in
these Terms and Conditions of Service, the Authorized Reseller’s purchase agreement or terms and
conditions of sale, or in the absence of such documents, Intel’s Terms and Conditions of Sale located at
Terms of Use shall govern the warranty and support services for Products. Intel reserves the right to
change the terms of Intel’s Terms and Conditions of Sale and these Terms and Conditions of Service,
including without limitation, the right to discontinue offering warranty and support services for the
Product, at any time without notice and without incurring any liability. These Terms and Conditions of
Service do not apply to custom products purchased directly or indirectly from Intel.

13.3.3 Limited Lifetime Hardware Warranty for Retail Intel® Ethernet

Adapters

13.3.3.1 Intel warranty is limited to 5 years from the date of Intel’s announce-
ment of end of life or discontinuance of the adapter products.
Intel warrants to the original owner that the adapter product delivered in this package will be free from
defects in material and workmanship. This warranty does not cover the adapter product if it is damaged in
the process of being installed or improperly used.

THE WARRANTY IS IN LIEU OF ANY OTHER WARRANTY, WHETHER EXPRESS, IMPLIED OR STATUTORY,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF NONINFRINGEMENT OF INTELLECTUAL PROPERTY,
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE ARISING OUT OF ANY PROPOSAL,
SPECIFICATION, OR SAMPLE.

This warranty does not cover replacement of adapter products damaged by abuse, accident, misuse,
neglect, alteration, repair, disaster, improper installation, or improper testing. If the adapter product is
found to be defective, Intel, at its option, will replace or repair the hardware product at no charge except as
set forth below, or refund your purchase price provided that you deliver the adapter product along with a
Return Material Authorization (RMA) number (see below), along with proof of purchase (if not registered),
either to the dealer from whom you purchased it or to Intel with an explanation of any deficiency. If you
ship the adapter product, you must assume the risk of damage or loss in transit. You must use the original
container (or the equivalent) and pay the shipping charge.

Intel may replace or repair the adapter product with either new or reconditioned parts, and any adapter
product, or part thereof replaced by Intel becomes Intel's property. Repaired or replaced adapter products
will be returned to you at the same revision level as received or higher, at Intel's option. Intel reserves the
right to replace discontinued adapter products with an equivalent current generation adapter product.

13.3.3.2 Intel ® Adapter money-back guarantee (North America only)

Intel wants you to be completely satisfied with the Intel adapter product that you have purchased. Any
time within ninety (90) days of purchase, you may return your Intel adapter to the original place of
purchase for a full refund of the purchase price from your dealer. Resellers and distributors, respectively,
accepting returns and refunding money back to their customers may return Intel adapters to their original
place of purchase. Intel guarantees that it will accept returns under this policy and refund the original
purchase price to customers purchasing directly from Intel.

13.3.3.3 Limitation of liability and remedies

INTEL'S SOLE LIABILITY HEREUNDER SHALL BE LIMITED TO DIRECT, OBJECTIVELY MEASURABLE
DAMAGES. IN NO EVENT SHALL INTEL HAVE ANY LIABILITY FOR ANY INDIRECT OR SPECULATIVE

705831 169
Intel® Ethernet Adapters and Devices User Guide

DAMAGES (INCLUDING, WITHOUT LIMITING THE FOREGOING, CONSEQUENTIAL, INCIDENTAL, AND

SPECIAL DAMAGES) INCLUDING, BUT NOT LIMITED TO, INFRINGEMENT OF INTELLECTUAL PROPERTY,
REPROCUREMENT COSTS, LOSS OF USE, BUSINESS INTERRUPTIONS, LOSS OF GOODWILL, AND LOSS OF
PROFITS, WHETHER ANY SUCH DAMAGES ARISE OUT OF CONTRACT NEGLIGENCE, TORT, OR UNDER ANY
WARRANTY, IRRESPECTIVE OF WHETHER INTEL HAS ADVANCE NOTICE OF THE POSSIBILITY OF ANY
SUCH DAMAGES. NOTWITHSTANDING THE FOREGOING, INTEL'S TOTAL LIABILITY FOR ALL CLAIMS
UNDER THIS AGREEMENT SHALL NOT EXCEED THE PRICE PAID FOR THE PRODUCT. THESE LIMITATIONS
ON POTENTIAL LIABILITIES WERE AN ESSENTIAL ELEMENT IN SETTING THE PRODUCT PRICE. INTEL
NEITHER ASSUMES NOR AUTHORIZES ANYONE TO ASSUME FOR IT ANY OTHER LIABILITIES.

Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above
limitations may not apply to you.

13.3.3.4 Critical control applications

Intel specifically disclaims liability for use of the adapter product in critical control applications (including, for
example only, safety or health care control systems, nuclear energy control systems, or air or ground
traffic control systems) by Licensee or Sublicensees, and such use is entirely at the user's risk. Licensee
agrees to defend, indemnify, and hold Intel harmless from and against any and all claims arising out of use
of the adapter product in such applications by Licensee or Sublicensees.

13.3.3.5 Software
Software provided with the adapter product is not covered under the hardware warranty described above.
See the applicable software license agreement which shipped with the adapter product for details on any
software warranty.

13.3.3.6 Submit an RMA request

Contact Intel Customer Support.

705831 170