Download Download Intel PROSet/Network Adapter Driver 27.7 for Server 2019 for Windows Server 2019 Free

What’s new in this release:

– The NVM Update Packages have been modified for the 700 Series (9.10) and E810 Series (4.10)
– Important: An issue has been identified with the NVM Update for the Intel Ethernet Network Adapter E810-XXVDA4T adapters. Customers – do not update the NVM at this time. If you must update the NVM, a power cycle reset to re-establish the link is required. However, updating to the Release 27.7 drivers is supported and recommended.

New Software Support:

– Support for Microsoft Windows 11 22H2
– Microsoft Azure Stack HCI, new feature release
– Support for FreeBSD 13.1 on most devices (not supported on Intel Ethernet E820 Series devices)

On Intel Ethernet 700 Series devices:

– i40e Linux driver allows speed adjustment with ethtool.
– FEC configuration through UEFI HII for 25G adapters
– Pruning of packets on bonded interfaces might be disabled.

On Intel Ethernet 810 Series devices:

– Support for Debug Dump feature on Windows, FreeBSD, and ESXi
– Support for Linux Real Time Kernel 5.x and 4.x
– Linux support for RDMA RoCEv2 link aggregation in dual-port active-backup configuration
– ICE driver support for GTP via switchdev and tc – OOT
– ICE driver support for VXLAN/GRE in switchdev mode

Miscellaneous:

– The auxiliary.ko filename has been changed to intel_auxiliary.ko. This was done to avoid potential conflicts with the kernel and other vendors. This change affects the following drivers: ice, version 1.9.7.1, i40e, version 2.20.10, iavf, version 4.6.0, rdma, version 1.10.5

Intel Ethernet 810 Series Fixed Issues:

– General: When RX/TX pause frames are enabled and the system is rebooted, or when the icen driver is unloaded, occasionally only one PF can be visible on ESX.
– General: Due to the previous bugs in PF-to-port mapping in both NVM and UEFI Driver, old NVMs are not compatible with the new UEFI driver. As it pertains to HII, NVMs can still be updated via FMP.
– Linux Driver: TC filters do not function correctly when the GPRS Tunnelling Protocol (GTP) encryption is enabled in the TC filter add command (enc_key_id 1) with ice driver version 1.10.X. This causes traffic to go to default TC 0.
– Linux Driver: The sense of PFC is lost through a link bounce because the number of TCs is 1.
– Linux Driver: Adding 16 MAC addresses to an untrusted VF that is attached to a VM, then changing the VF’s trust status to on and off again, could cause the added MAC addresses to become non-functional.
– Linux Driver: ADQ configuration commands that update settings on the interface (such as tc qdisc add and ethtool -L) cause the driver to close the associated RDMA interface and reopen it. This disrupts RDMA traffic on the interface. RDMA and ADQ configurations are not supported on the same interface simultaneously.
– Linux Driver: Resetting VF device might lead to memory corruption. If VF is being reset with no intervals between resets, it is possible for the VF driver to free DMA mapping, while NIC still transmits packets. This will lead to memory corruption. To avoid this, limit rate resets of VF. Memory corruption will happen on the OS that VF is assigned to.
– Linux Driver

: Linux ice driver 1.2.1 cannot be compiled with E810 3.2 NVM images. The version on the kernel is 5.15.2.
– Linux Driver: On RHEL8.5, l2-fwd-offload cannot be turned on.
– Linux Driver: If the rpmbuild command of the new iavf version fails due to the existing auxiliary files installed, please use –define “_unpackaged_files_terminate_build 0” with the rpmbuild command.
– Linux Driver: Usage/Workaround will look like rpmbuild -tb iavf-4.4.0_rc53.tar.gz –define “_unpackaged_files_terminate_build 0” “.
– Linux Driver: When Double VLAN is created on a Virtual Machine, tx_tcp_cso [TX TCP Checksum Offload] and tx_udp_cso [TX UDP Checksum Offload] statistics might not increment correctly.
– Linux Driver: On Intel Ethernet Network Adapter E810-XXVDA4T, the driver might not link at 1000BASE-T and 1000BASE-X. The link might go down after advertising 1G.
– Linux RDMA Driver: With Intel Ethernet 800 Series Network Adapter iwarp, ib_write_bw fails with the a RDMA_CM_EVENT_REJECTED with at least 1000 QPs.
– Linux RDMA Driver: When the ECN congestion control feature for rocev2 is enabled the code transmits the ECN codepoint as ’00’ in ACK packets instead of ’10’. This marking causes fabric switches to drop RC ACK packets, drastically impacting performance when congestion is present and causing RC retries and aborted QP connections. This is the exact opposite of the intent of the feature and the subsequent retransmissions due to ACK drops makes congestion worse. The issue is seen with multiple switch vendors.
– Firmware: Per the specification, the Get LLDP command (0x28) response might contain only 2 TLVs (instead of 3).
– Firmware: When software is requesting from firmware the port parameters on Port 0 (via AQ the connectivity type), the response is BACKPLANE_CONNECTIVITY, when it should be CAGE_CONNECTIVITY.
– Firmware: Health status messages are not cleared with a PF reset, even after the reported issue is resolved.
– FreeBSD Driver: When using 100G SR4 optics or active optical cables, it is possible for the adapter to fail to link if the advertise_speed sysctl is set to only link at 50G speeds.
– VMware Driver: On VMware ESXi vSphere 6.7 and Linux VM with Kernel version higher than 5.14, after performing warm reboot, traffic on SR-IOV VF adapters will be dropped. Workaround: reload VF driver when issue occurs or instead of warm reboot perform power cycle from ESXi hypervisor.
– ADQ VF: When ADQ is enabled on VFs, TC filters on the VF TCO (default TC) are not supported and will not pass traffic. It is not expected to add TC filters to TCO since it is reserved for non-filtered default traffic.
– ADQ VF: VF Max Transmit Rate: TC qdisc add command on a VF interface does not verify that max_rate value(s) for the TCs are specified in increments of 500 Kbps. TC max_rate is expected to be a multiple of (or equal to) 500 Kbps.
– ADQ VF: VF Max Transmit Rate: When ADQ is enabled on a VF interface, the tc qdisc add command causes the VF connection (ping) to drop when using ice-1.8.X and iavf-4.4.X. Workaround: Use previous versions of the ice and iavf drivers for ADQ VF (ice-1.7.16 with iavf-4.3.19).
– ADQ VF: VF Max Transmit Rate: When a maximum TX transmit rate is specified in the tc qdisc add command on a VF interface, the maximum rate does not get applied correctly, causing an inconsistent TX rate limit for some applications.
– ADQ VF: Configuring ADQ traffic classes with an odd number of hardware queues on a VF interface might result in a system hang in the iavf driver. Workaround: To specify an even number of queues in the TC qdisc add the dev command for ADQ.

Intel Ethernet 820 Series Fixed Issues:

– Firmware: No link displayed on the 827 QSFP after setting to 50G.
– Firmware: Asymmetrical link flow control is not functioning as expected with Tx=ON and Rx=OFF. Works fine with Flow control set to TX=ON and RX=ON.
– Firmware: When performing an NVM Update/inventory for a device running in recovery mode, the system returns Exitcode 8 (No access to flash) instead of Exitcode 0. Even if the wrong Exitcode is observed, that device can still be initialized, perform updates, and exit from recovery mode.
– Firmware: Current hardware and firmware limits the SFP cages to 1W (Power class 1). As a result, all optical modules that require power level 2 (1.5W) will not work with the ICX-D HCC Beta LEK images.
– Linux Driver: If a Virtual Function (VF) is not in trusted mode and eight or more VLANs are created on one VF, the VLAN that is last created might be non-functional and an error might be seen in dmesg.
– Linux Driver: VXLAN traffic is not passing through on the expected queues.
– Linux Driver: In DCB mode, when switching from IEEE to CEE mode, configurations are not applied. Workaround: Either start in CEE mode or enter unwilling mode to perform configurations.
– Linux Driver: When Double VLAN Mode is enabled on the host, disabling then re-enabling a Virtual Function attached to a Windows guest might cause error messages to be shown in dmesg. This behavior is not expected to affect functionality.
– Linux Driver: Setting the MAC address of a VF to 00:00:00:00:00:00 from the host should reset the VF, not change the MAC address. We have observed the MAC address to appear as 00:00:00:00:00:00 from the host and the correct value from the VM.
– Linux Driver: During RSS testing, incorrect values are displayed in OIDs for Maximum Number of RSS Queues and Processors.
– Linux Driver: When all of the interfaces configured for VLAN traffic are connected to a vmSwitch port, and after reattaching one of the vmNICs to another port, it loses connectivity (i.e., cannot ping). The ability to ping is recovered after reattaching another vmNICs to the vmSwitch (where first vmNIC was attached).
– Linux Driver: After a bond is created on two interfaces and the primary is disabled, the next “primary/secondary” will gain the MAC of the bond interface. The MAC of the bond always stays the same.
– Windows RDMA Driver: After enabling QoS for iWarp, no RDMA traffic is observed. This issue is not seen on RoCEv2.
– NVM Update Tool: If a device goes into recovery mode, a stripped image must be used to perform an update.

Intel Ethernet 700 Series Fixed Issues:

– VMware Driver: When using a driver in ENS polling mode along with SR-IOV, packets might not come out from VF virtual machine. The issue appears after a PF reset or link down/up execution. Workaround: Reboot VM or reboot host
– VMware Driver: When using driver in ENS polling mode along with SR-IOV, there might be no traffic between VF and VM adapters on single host. Workaround: None
– VMware Driver: When using driver in ENS interrupt mode along with SR-IOV, there might be no traffic between VF and VM adapters with default MTU setting. Workaround: Reboot VM or change MTU to any value, then change back to default.
– Linux Driver: Intel Ethernet Flow Director cloud filters: Outer MAC, Tenant ID, Inner MAC might not direct traffic to queues/VFs on the latest “Red Hat Enterprise Linux 9.0 (Plow)” 5.14.0-70.13.1.el9_0.x86_64.

This download is valid for the products listed below:

– Intel Ethernet Connection I218-LM
– Intel 82579LM Gigabit Ethernet PHY
– Intel Ethernet Connection I217-LM
– Intel Ethernet Connection I219-LM
– Intel Ethernet Server Adapter I210-T1
– Intel Ethernet Converged Network Adapter X540-T2
– Intel Ethernet Converged Network Adapter X540-T1
– Intel Ethernet Controller I225-LM
– Intel Ethernet Controller X540-AT2
– Intel Ethernet Converged Network Adapter X520-DA1
– Intel Ethernet Converged Network Adapter X550-T1
– Intel Ethernet Converged Network Adapter XL710-QDA1
– Intel Ethernet Network Adapter XXV710-DA2
– Intel Ethernet Controller I350-AM2
– Intel Ethernet Controller I350-BT2
– Intel Ethernet Controller I350-AM4
– Intel Ethernet Controller X540-BT2
– Intel Ethernet Controller E810-CAM1
– Intel Ethernet Controller E810-CAM2
– Intel Ethernet Controller E810-XXVAM2
– Intel Ethernet Server Adapter X520-DA1 for Open Compute Project
– Intel Ethernet Server Adapter X520-DA2 for Open Compute Project
– Intel Ethernet Converged Network Adapter X710-DA4
– Intel Ethernet Controller X550-AT2
– Intel Ethernet Controller X550-BT2
– Intel Ethernet Converged Network Adapter X710-T4
– Intel Ethernet Server Adapter I350-F2
– Intel Ethernet Server Adapter I350-T4V2
– Intel Ethernet Converged Network Adapter X710-DA2
– Intel Ethernet Converged Network Adapter X550-T2
– Intel Ethernet Network Adapter XXV710-DA1
– Intel Ethernet Controller X710-AT2
– Intel Ethernet Controller I225-IT
– Intel Ethernet Network Adapter E810-2CQDA2
– Intel Ethernet Network Adapter E810-CQDA2 for OCP 3.0
– Intel Ethernet Network Adapter E810-CQDA2
– Intel Ethernet Network Adapter X710-DA2 for OCP 3.0
– Intel Ethernet Controller X710-TM4
– Intel Ethernet Network Adapter X710-T2L
– Intel Ethernet Network Adapter X710-T2L for OCP 3.0
– Intel Ethernet Network Adapter X710-T4L
– Intel Ethernet Server Adapter XL710-QDA1 for Open Compute Project
– Intel Ethernet Server Adapter XL710-QDA2 for Open Compute Project
– Intel Ethernet Controller I210-CL
– Intel Ethernet Converged Network Adapter X520-SR2
– Intel Ethernet Converged Network Adapter XL710-QDA2
– Intel Ethernet Converged Network Adapter X520-DA2
– Intel Ethernet Converged Network Adapter X520-LR1
– Intel Ethernet Converged Network Adapter X520-T2
– Intel Ethernet Network Adapter E810-CQDA1 for OCP 3.0
– Intel Ethernet Network Adapter E810-XXVDA4 for OCP 3.0
– Intel Ethernet Network Adapter E810-XXVDA2 for OCP 3.0
– Intel Ethernet Controller I210-AS
– Intel Ethernet Controller I210-IS
– Intel Ethernet Controller XL710-BM1
– Intel Ethernet Controller XL710-BM2
– Intel Ethernet Controller X710-BM2
– Intel Ethernet Network Adapter E810-XXVDA4
– Intel Ethernet Network Adapter E810-CQDA1
– Intel Ethernet Network Adapter E810-XXVDA2
– Intel Ethernet Network Adapter X710-DA4 for OCP 3.0
– Intel Ethernet Network Adapter X710-T4L for OCP 3.0
– Intel Ethernet Controller I210-AT
– Intel Ethernet Server Adapter I350-T2V2
– Intel Ethernet Network Adapter E810-CQDA1 for OCP
– Intel Ethernet Server Adapter X710-DA2 for OCP
– Intel Ethernet Controller X550-AT
– Intel Ethernet Controller XXV710-AM1
– Intel 82599EN 10 Gigabit Ethernet Controller
– Intel 82599ES 10 Gigabit Ethernet Controller
– Intel Ethernet Converged Network Adapter X520-QDA1
– Intel Ethernet Server Adapter I350-F4
– Intel Ethernet Controller I210-IT
– Intel Ethernet Controller XL710-AM2
– Intel Ethernet Controller X710-AM2
– Intel 82599EB 10 Gigabit Ethernet Controller
– Intel Ethernet Controller I210-CS
– Intel Ethernet Converged Network Adapter X520-SR1
– Intel Ethernet Controller XXV710-AM2
– Intel Ethernet Controller XL710-AM1
– Intel Ethernet Server Adapter X520-DA2
– Intel Ethernet Connection X557-AT

About Network Adapter Drivers:

When connected, the operating system usually installs a generic driver that helps the computer to recognize the newly attached device.

However, proper software must be applied if you want to make use of all features that the network adapter has available. This task also allows computers to properly recognize all device characteristics such as manufacturer, chipset, technology, and others.

Updating the adapter’s drivers and utilities version might improve overall performance and stability, increase transfer speeds, fix different compatibility problems and several network-related errors, as well as bring various other changes.

To install this release, simply get the package, extract it if necessary, run the setup, and follow the instructions displayed on-screen. When done, don’t forget to perform a system restart and reconnect the network adapter to make sure that all changes take effect properly.

Without further ado, if you intend to apply this version, click the download button and install the package. Moreover, check with our website as often as possible so that you don’t miss a single new release.