Intel S2600WT2 Server Board Ethernet Driver 25.4 for Server 2016

What's New in This Release

- Support for FreeBSD 11.4.
- Removed DOS tools.
- Support for the Intel Ethernet Controller E810-XXV
- Support for the Intel Ethernet Controller E810-XXV for backplane
- Support for the Intel Ethernet Controller E810-XXV for QSFP
- Support for the Intel Ethernet Controller E810-XXV for SFP
- Support for the Intel Ethernet Network Adapter E810-XXV-2
- Support for the Intel Ethernet Network Adapter E810-XXV-2 for OCP 3.0
- Linux support for the Intel Ethernet Network Adapter E810-C-Q1 for OCP
- Support for the Intel Ethernet Network Adapter E810-C-Q2 for OCP 3.0
- Microsoft Windows support for Intel Ethernet Controller (3) I225-IT
- Microsoft Windows support for Intel Ethernet Controller (3) I225-LM
- Microsoft Windows support for Intel Ethernet Controller (3) I225-LMvP
- Microsoft Windows support for Intel Ethernet Controller (3) I225-V
- Support for Red Hat Enterprise Linux 7.9. Drivers are no longer tested on RHEL 7.8.

Intel Ethernet 800 Series Changes:

- Fixed: Reading the module temperature sensor with NVM 2.10/2.12 gives an incorrect value for all methods that rely on firmware, including NCSI and PLDM. Users can expect reported temperature ranges from 0 to 255 with no consistency.
- QSFP modules with a temperature sensor whose module EEPROMs are aligned to specification SFF-8636, Revision 2.8 or newer could result in port shutdown that is only recoverable with a power cycle and a change of module.

Intel Ethernet 700 Series Changes:

- Fixed: The Intel Ethernet Network Adapter X710-T2L/T4L and the Intel Ethernet Network Adapter X710-2/X710-4 pull-up in GLOBR creates a false FAN_ON_AUX.
- Fixed: Device returns different version of supported PLDM type 6.
- Fixed: Devices do not return Network Port schema data.
- Fixed: The FAN_ON_AUX signal doesn't change status when temperature crosses warning threshold.
- Fixed: Intel Ethernet Converged Network Adapter XL710-Q1/Q2 recovery fails on FreeBSD.
- Fixed: RDE device reports wrong MaxFrameSize value.
- Fixed: PCIeDevice PDR (recordHandle 4003) is missing in the list of retrieved PDRs.
- Fixed: RdeOperationInit on NetworkPort1 returns SUCCESS and didn't return BEJ.
- Fixed: For the Intel Ethernet Controller X710-TM4/AT2, setting the Link NCSI command to 2.5G/5G speed doesn't change the link properly.
- Fixed: The NCSI Get Temperature command might try to read temperature from a module that doesn't support temperature readings. This could lead to incorrect temperature handling as well as having an impact for handling platform events.
- Fixed: On Windows Server 2012 R2 the host might suffer a BSOD after modifying ANS team type with tagged VLAN. It can be reproduced both with GUI or a Powershell command.
- Fixed: MAC VLAN filters are not freed when the number of VFs changes. It is observed only when a limit of MAC VLAN filters have been reached before VF changes.
- Fixed: When the number of multicast MAC addresses configured on the VF reaches the limit of the network adapter, the VF cannot receive all multicast packets.
- Fixed: Maximum number of SR-IOV VFs is 62 (instead of 63) per port. This behavior is observed when the RSS and VMDq settings are disabled. It might be observed only when using ESX-ixgben driver.
- Fixed: Packets with assigned VLAN are not redirected to the correct queue set by the Intel Flow Director (FD) rule.
- Fixed: After setting DCB on Intel Ethernet Controller X710 adapters, traffic is not tagged with a priority tag.
- Fixed: When the second subordinate interface is added to the bonding, its MAC address becomes the same as the first added subordinate and bond interface. Reloading the PF driver and creating VFs again is needed to restore the MAC addresses.
- Fixed: Promiscuous mode trusted VF with VLAN port for unicast packets receiving additional Tx traffic of every other VFs assigned to the same PF.
- Fixed: Minimum Security (Rollback) Revision (MinSREV) values and Security (Rollback) Revision (SREV) are not reported in unified (hexadecimal) format via the NVM Update Tool.
- Fixed: Use Default button in the UI is missing from the Locally Administered Address tab.

Intel Ethernet 500 Series Changes:

- Fixed: FAN 7 rotates non-stop when 562FLR is installed and while in AUX power.
- Fixed: Maximum number of SR-IOV VFs is 62 (instead of 63) per port. This behavior is observed when the RSS and VMDq settings are disabled. It is observed only when using the ESX-ixgben driver. Fixed: Firmware installation failed for 562FLR-T.

Intel Ethernet 300 Series Changes:

- Fixed: The Wake on LAN (WoL) feature doesn’t work on the Intel Ethernet Server Adapter I350 and Intel Ethernet Network Adapter I350 OCP 3.0. This issue occurs on ports 2 through 4. 

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.

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.