Intel PROSet/Network Adapter Driver 29.0 for Server 2016

Changes:

- Updated Linux drivers and Firmware/NVM versions.
- Fixed issue for Linux driver when creating new VLAN devices or setting the port VLAN.
- Added Azure Stack HCI 23H2 OS Support in section 1.1.2.

Intel Ethernet 810 Series Fixed Issues:

Linux Driver:
- Previously, upon creating new VLAN devices or setting the port VLAN for the VF device, and the irdma module is also loaded, a system hang might occur. Try to unload the irdma module ("modprobe -r irdma").
- Previously, when using devlink-rate and custom TX scheduler tree topology in switch mode, setting a node's/leaf's tx_priority ('devlink port function rate set pci// tx_priority 1') along with a BW limitation (for example, tx_max - 'devlink port function rate set pci// tx_max 1Gbit' - on the parent node) could result in starvation of the node/leaf (0 BW on Tx), with a lower priority set, and trigger a Tx hang detection.
- Resolved an issue when DCB configuration was changed to use the firmware agent in willing mode on the first port of a two port card, lldpad core dumps, and the second port of the reported the following messages: [3784.370726] ice 0000:af:00.1: Commit DCB Configuration to the hardware, [3784.393109] INFO: Flow control is disabled for this traffic class (0) on this vsi, [3784.458480] 8021q: Adding VLAN 0 to HW filter on device eth3. The messages would repeat forever.
- Previously, with the 810 Series 3.2 NVM in the Intel Ethernet Network Adapter E810-CQDA2 card, if the 810 Series 2.2 iavf driver was installed, a fatal error was generated related to pci-aspm.h, and the installation failed.
- Resolved an issue where double VLAN traffic might RSS into the first queue. If configuring VLAN interfaces on PF in a way that results in double VLAN tagging, received double VLAN packets would be concentrated on the first queue of interface.
- Fixed a firmware issue that could result in a firmware reset when some, but not all, ports have flow control enabled.
- Previously, there were unexpected FW logs during some special environments, such as tx_timeout or NVM update.
- Improved driver's robustness when bringing interface up/down with link-down-on-close flag is set and recoverable non-critical error occurs.
- Corrected an issue where upon creating new VLAN devices or setting the port VLAN for the VF device, and the irdma module is also loaded, a system hang might occur.

Firmware/NVM/NVM Update:
- Previously, the PLDM Type 5 Command "Activate Firmware" could potentially cause a subsequent PLDM Type 2 event.
- Resolved an issue where during an ActiveFirmware request coming from Update Agent (BMC) PLDM Type2, a PlatformEventMessage was generated by the Firmware Device (Network Adapter). As a result, the response did not happen, and Update Agent (BMC) treated it as Update Failed.
- Fixed an issue where the UEFI HII interface could not save the setting of virtualization mode.
- Previously, in PLDM Platform Monitoring and Control, the sensor_data_size field of SFP thermal sensor PDR was containing wrong value: unsigned instead of signed char/byte.
- Previously, during ActiveFirmware request coming from Update Agent (BMC) PLDM Type2 PlatformEventMessage was generated by our Firmware Device (Network Adapter). As a result, response did not happen and Update Agent (BMC) treated it as Update Failed.
- Firmware now acquires semaphore before "Load Factory Settings to PFA" and releases it immediately after.
- Firmware now returns PLDM_ERROR_NOT_READY Completion Code instead of generic 0x01(PLDM Base: Error) when firmware is not fully ready after platform reboot.
- Previously, when BMC subscribed to PLDM events, the NIC issued two equivalent redfish events for the different origins (Network Adapter and Port) caused by the same trigger (link state change for given port). This issue caused unnecessary redfish event flood. The resolution was to change firmware design in order to avoid sending multiple redfish events for the same trigger.
- Previously, in Network Controller Sideband Interface after EnableChannel command invoked, the OEM command IANA=0x02A2 GetLldp occasionally returned LLDP TLVs with missing mandatory values for chassis_id and port_id.
- Set packageID SDP to correct values for E810-CQDA1.
- Now the patched property of NetworkDeviceFunction.Ethernet.MACAddress is persistent during reboot. Users can restore to PermanentMACAddress with ResetSettingsToDefaults.

Application Device Queues (ADQ):
- Previously, ADQ dynamically registered and unregistered queue group-specific devlink parameters. Newer kernels (6.2.x and later) expect all devlink parameters to be registered during probe time and unregistered upon device removal. As a result, warning messages were to be expected when ADQ queue groups were created or destroyed for the first time.

Intel Ethernet 820 Series Fixed Issues:

Firmware/NVM/NVM Update:
- Resolved an issue where promiscuous mode did not see all packets; it saw only those packets arriving over the wire; that is, not sent from the same physical function (PF) but a different virtual function (VF).
- Previously, the DCB-MAP Configuration was not displaying on the SUT Interface from the Extreme Switch after enabling the firmware Mode in the SUT.
- Previously, using the EPCT tool to change port configuration required 2 reboots to complete the programming process. Blank mode or PTP initialization failures may be observed after a single reboot and will be resolved after performing a second reboot.
- Resolved an issue where the Get LLDP command (0x28) response used to contain only 2 TLV types. The new implementation requires a third TLV type, which contains a copy of the whole LLDP frame payload.
- Resolved an issue where the BMC was unable to receive packets when DHCPv6 server to client multicast filter is enabled.

Linux Driver:
- Previously, it had been observed in certain scenarios where inner VLAN traffic would concentrate on a single queue, creating packet drops.
- Resolved an issue where drop action was not properly offloaded in hardware when setting was done using Open vSwitch.

Windows Driver:
- Previously, with a Windows host and Linux virtual machine (VM), the last transmit (Tx) queue might not increment when there are multiple Tx queues.
- Fixed an issue when using hardware timestamp an incorrect behavior was observed on the receive (Rx) side. Timestamp was received and no error messages were reported, however its value was 0 and therefore was considered as faulty.

FreeBSD Driver:
- Previously, when a driver was loaded with an empty cage, an Admin Queue (AQ) error was recorded instead of the expected AHS link messages.

LANConf Tool:
- Resolved a limitation of the LANConf tool that only allowed the user to program ID EEPROM on Quad 0. This also meant that each attempt to program ID EEPROM on Quad 1 would cause an update on Quad 0.

Intel Ethernet 700 Series Fixed Issues:

Linux Driver:
- Resolved an issue where the DMARemappingCompatible registry was missing in the previous driver.
- Resolved an issue that failed to detect temperature status with latest OOB driver. 

Firmware/NVM/NVM Update:
- Previously, for XXV710DA2_9p30_CFGID12p0_OEMGEN_J65979 the configuration files did not contain mention of 0x8000DECD, which is the original factory program image.
- Resolved an issue where POST to the NetworkAdapter.ResetSettingsToDefault looked successful from postman, but after reboot the adapter's Port 1 LLDP setting did not reset to default.
- Previously, there were cases of Fortville disappearing from the PCIe bus during reboot stress testing reported on Icelake-based platforms. These platforms performed a PCIe Hot Reset before asserting PERST# as part of the warm reboot cycle. PERST# is asserted at approximately the end of the Hot Reset, but due mostly to the Fortville LCB implementation, there was a variation in the relative timing of about 65 us, so many edge cases could occur.
- Fixed a wrong demsg message from i40e driver of unsupported SFP+ module type was detected when eeupdate upgrade NVM of x710t2l or x710t4l.

Windows Driver:
- Previously, setting PHY debug mode with disabling link during initialization caused link to go down.
- Previously, during the NVM update the adapter was getting disabled for a long time due to lock in OID_INTEL_FLASH_INFO. As result, the driver was unable to access the NVM timed out quickly.
- Resolved an issue where a rare PCI speed degradation with Gen3 to Gen2 had been seen during extensive link tests after a reset was caused by a core reset on an ICX-D platform.
- NDIS i40eb (X722 NIC) component now supports Japanese in advanced tab language.
- Resolved an issue in Windows Server 2022 where the E1R driver didn't disable auto-negotiation when choosing a specific speed and duplex setting.

This download is valid for the products listed below:

- Intel 82579LM Gigabit Ethernet PHY
- Intel Ethernet Connection I217-LM
- Intel Ethernet Connection I218-LM
- Intel Ethernet Server Adapter I210-T1
- Intel Ethernet Converged Network Adapter X540-T2
- Intel Ethernet Converged Network Adapter X540-T1
- 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 Controller X550-BT2
- 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 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 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 Network Adapter X710-T2L
- Intel Ethernet Network Adapter X710-T2L for OCP 3.0
- Intel Ethernet Network Adapter X710-T4L
- Intel Ethernet Controller X710-TM4
- 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-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 82599ES 10 Gigabit Ethernet Controller
- Intel Ethernet Controller X550-AT
- Intel Ethernet Controller XXV710-AM1
- Intel 82599EN 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 Controller XXV710-AM2
- Intel Ethernet Controller XL710-AM1
- Intel Ethernet Server Adapter X520-DA2
- Intel Ethernet Connection X557-AT
- Intel Ethernet Converged Network Adapter X520-SR1

About Ethernet Drivers:

Windows platforms generally apply a generic driver that allows motherboards to recognize the Ethernet component.

However, in order to make use of all network card (adapter) features, you must install a proper LAN driver that enables the hardware. This task enables systems to connect to a network, as well as collect all component characteristics such as manufacturer and chipset.

If you intend to update the driver version, know that this process can add support for new OSes, fix different compatibility problems, resolve related errors encountered during the product's lifetime, as well as include various other changes.

When it comes to the actual installation procedure, we should note that most producers try to make it as easy as possible, so following the steps should be a breeze: just get the downloadable package, run the setup, and follow the on-screen instructions.

There is a chance that other OSes could also be suitable, but it is not advisable that you install this release on platforms other than the specified ones. Remember to perform a system reboot once done, to allow all changes to take effect properly.

Therefore, if you wish to apply this version, click on the download button and enable your network card. To stay up to speed with the latest updates, check back with our website as often as possible.