Does the X540-T2 NIC supported on Windows Server 2016?

Hi,

I recently bought a (second hand) Intel X540-T2 network adapter for my DIY-NAS (my workstation already has one).

Unfortunately, it seems to have problems booting on my ASUS Maximus 6 Gene board (Post code 55). I've narrowed down the problem to Dell's memory mapping of the firmware. It is a known problem with Dell X540-T2's and the Intel Z87/Z97 chipset when using 4 DIMMs. It can be fixed by removing on DIMM from the board, after which the board POSTs and boots without any problems. The Dell X540 does boots without any issues on the H110 and Z370 chipsets, even with all four DIMM slots populated.

The card I intended to use for my workstation is a passive one (Intel OEM) and this one boots just fine of my ASUS M6G board. Considering both NICs have an identical board (aside from the fan header on the Dell one), I suspect that the Dell card will still work when I flash it with the unmodified Intel firmware, correct? This should solve the EFI memory mapping problem that I encounter on my NAS.

Is what I'm trying to achieve possible? Or should I just get rid of the Dell X540 and buy a new OEM Intel card? I got the dell really cheap - and genuine X540's often go for over $300 used (not counting the potentially compromised chinese knock-offs)

I've done a bit of Google-Fu, but couldn't find the native Intel firmware anywhere.

I'm trying to install the Proset driver and utilities but the installation says it cannot find any Intel adapters.

Windows 10 found the adapter just fine and installed the Windows Update version of the drivers but I was hoping to experiment with teaming on this system.

Is this board fully supported?

Windows 10 Build 1709

We have procured over a dozen NUC6i7KYK (mfg 07/2017) to act as a receiver of a moderate rate (~320Mbps) UDP stream of data. We have found that the I219-LM adapter is dropping packets. We have been able to replicate the issue using the iperf tool. For the application (and for my troubleshooting tests) the NUC will be direct connected to the data source via a new, short (~1m), patch cord.

We have the latest BIOS (KYSKLi70.86A.0050.2017.0831.1924) and we are using Ubuntu 16.04.3. We have also tried Ubuntu 16.04.2 and 17.10. We have tried the distro provided e1000e 3.2.6-k driver as well as the latest e1000e 3.3.6 driver.

We have set net.core.rmem_max to 33554432 and net.core.wmem_max to 576000.

We have set coalescence to zero: ethtool -C eno1 rx-usecs 0.

We have maxed the receive ring buffer: ethtool -G eno1 rx 4096.

We have ensured max CPU frequency via cpufreq setting it to "performance".

Data loss is non-deterministic and sometimes happens immediately, after several minutes, or several hours. Typically it is a single missing packet. We can not afford any lost data.

I had a ZBOX-CI323NANO with openSuSE 42.3 on it. This low performance device has Realtek RTL8111/8168/8411 PCIe GbE adapters. It received UDP data with zero losses. That's the sort of results I expect from this NUC.

It has net.core.rmem_max and net.core.wmem_max set to 16777216.

We also have used a Pluggable USB3.0 GbE adapter. It also runs with no lost data - however, it tends to "go away" after indeterminate periods of time - not sure if that's a NUC, OS, or pluggable issue.

I saw this thread that looks familiar to my problem:UDP packets frozen with at least I219-V, I219-LM and I217-LM

When I run wireshark, occasionally I see the interpacket gap be ~10ms instead of the typical handful of microseconds.

We have two Hyper-V 2016 servers in core mode, both have a pair of Intel X710 Adapters. Both have Hyper-V role enabled and the latest Intel firmware, drivers and Windows patches.

Using the PowerShell commands I see that the performance profile is "Standard server".  Normally if Hyper-V is detected the performance profile is automatically set to 'Virtualization' by the driver however this is not the case here.

I have tried to set this using this PowerShell command:

Set-IntelNetAdapterSetting -Name *X710* -RegistryKeyword PerformanceProfile -RegistryValue 5

But an error is thrown:

Set-IntelNetAdapterSetting : The setting could not be modified because the specified value is invalid for this device or setting.

Any suggestions please?

Hi,

I have a VM using SRIOV interfaces based on X710 interfaces. This VM is connected to a physical router through the VF.

I would like to enable vlan tagging on the VM.

I can ping the physical router from the VM if I'm not using VLAN tagging on the interface.

When I add VLAN tagging on the interface (on the VM and on the physical router), the network connectivity is broken.

The physical router correctly receives the packets/frames from the VM.

The VM receives the packets/frames but without a VLAN tag, it seems that the VLAN tag has been stripped.

Here are some informations on my setup:

[root@SLI-SRV3 sysadmin]# ethtool -i eth1

driver: i40e

version: 1.6.27-k

firmware-version: 6.00 0x800034e6 18.3.6

expansion-rom-version:

bus-info: 0000:19:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

[root@SLI-SRV3 sysadmin]# ip link show eth1

3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq portid 246e967eaabe state UP mode DEFAULT qlen 1000

    link/ether 24:6e:96:7e:aa:be brd ff:ff:ff:ff:ff:ff

    vf 0 MAC 52:54:00:5d:6a:60, spoof checking on, link-state auto, trust off

VIRSH network config:

    <interface type='hostdev' managed='yes'>

      <mac address='52:54:00:5d:6a:60'/>

      <driver name='vfio'/>

      <source>

        <address type='pci' domain='0x0000' bus='0x19' slot='0x02' function='0x0'/>

      </source>

      <alias name='hostdev0'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

    </interface>

Any idea about what could be the issue ?

Thanks,

Stephane

Using an updated driver, I cannot seem to get my interfaces up. Looks like the driver is not allowing the NIC to work due to the SFP+ module type, which worked previously on my Debian Stretch host. Clearly the NIC is detecting and reading the DAC, but I don't understand why it is not working. This is a 40G-breakout cable with 40-to-4x10G SFP+ DAC (TwinAx). I have tried adding the following to work around it, but it still does not work:

root@lab4:~# cat /etc/modprobe.d/i40e.conf

options i40e allow_unsupported_sfp=1

This was also discussed here, but there was no followup:

Intel Ethernet Drivers and Utilities / Mailing Lists

Output from dmesg:

[    4.439190] i40e 0000:08:00.3: PCI-Express: Speed 8.0GT/s Width x8

[    4.447918] i40e 0000:08:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 8 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA

[    4.453414] i40e 0000:08:00.2: Rx/Tx is disabled on this device because an unsupported SFP+ module type was detected.

[    4.465288] i40e 0000:08:00.2: Refer to the Intel(R) Ethernet Adapters and Devices User Guide for a list of supported modules.

Other pertinent output:

root@lab4:~# ethtool -m eth6

Identifier                                : 0x03 (SFP)

Extended identifier                       : 0x04 (GBIC/SFP defined by 2-wire interface ID)

Connector                                 : 0x21 (Copper pigtail)

Transceiver codes                         : 0x00 0x00 0x00 0x00 0x00 0x04 0x00 0x00

Transceiver type                          : FC: Copper Passive

Encoding                                  : 0x00 (unspecified)

BR, Nominal                               : 10300MBd

Rate identifier                           : 0x00 (unspecified)

Length (SMF,km)                           : 0km

Length (SMF)                              : 0m

Length (50um)                             : 0m

Length (62.5um)                           : 0m

Length (Copper)                           : 3m

Length (OM3)                              : 0m

Passive Cu cmplnce.                       : 0x01 (SFF-8431 appendix E) [SFF-8472 rev10.4 only]

Vendor name                               : Amphenol

Vendor OUI                                : 78:a7:14

Vendor PN                                 : 624400003

Vendor rev                                : A

Option values                             : 0x00 0x00

BR margin, max                            : 0%

BR margin, min                            : 0%

Vendor SN                                 : APF13470035GDT

Date code                                 : 131122

root@lab4:~# ethtool -i eth6

driver: i40e

version: 2.4.3

firmware-version: 6.01 0x800034af 1.1747.0

expansion-rom-version:

bus-info: 0000:08:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

root@lab4:~# ethtool eth6

Settings for eth6:

Supported ports: [ ]

Supported link modes:   Not reported

Supported pause frame use: Symmetric

Supports auto-negotiation: No

Advertised link modes:  Not reported

Advertised pause frame use: No

Advertised auto-negotiation: No

Speed: Unknown!

Duplex: Unknown! (255)

Port: Other

PHYAD: 0

Transceiver: internal

Auto-negotiation: off

Supports Wake-on: d

Wake-on: d

Current message level: 0x0000000f (15)

       drv probe link timer

Link detected: no

root@lab4:~# ip link show eth6

5: eth6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000

    link/ether 68:05:ca:2f:7c:b0 brd ff:ff:ff:ff:ff:ff

Like others, I bought an X550-T2 (direct from Amazon themselves) and the Yottamark is valid, but the MAC doesn’t match.

Is this going to be an on-going production problem?

Hello;

I have a Box (supermicro) with:

S.O :    FreeBSD 11.1-STABLE (FreeNAS)

NIC: - Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02).

- Intel(R) Ethernet Connection XL710/X722 Driver, Version - 1.7.12-k

- dev.ixl.0.fw_version: fw 5.0.40043 api 1.5 nvm 5.05 etid 80002a43 oem 1.261.0

I have issues with the connection  Flapping on the interfaces 10G and a lot of messages "ixl0: Malicious Driver Detection event 2 on TX queue 2, pf number 0"

I m trying to Upgrade the Firmware to 6.0.1; but the procedure (./nvmupdate64e) says:

Num Description                               Ver. DevId S:B    Status

=== ======================================== ===== ===== ====== ===============

01) Intel(R) I350 Gigabit Network Connection  1.99  1521 00:001     Update not

                                                                                                             available

02) Intel(R) Ethernet Controller X710 for     5.05  1572 00:002     Update not

    10GbE SFP+                                                                                  available

Tool execution completed with the following status: Device not found.

Please tell me the correct way to write a new hardware MAC address and load firmware into a blank Intel 82574L Gigabit Ethernet Controller Chip under Windows 10 Embedded.

Windows would be running on a Qseven module board, and the 82574 chip is on an adapter module board attached to the Qseven module.

I have a Intel(R) 82579LM Gigabit Network Connection adapter

I run Windows 10

My network keeps disconnecting while in hibernate mode, and while working as well

I installed PROWinx64.exe

I disabled the function Energy Efficient Ethernet

Both to try to solve the problem.

But it does not work

The strange thing is that there is nog yellow triangle or red cross and it says there is internet access.

Can someone please help me, this is very annoying

I have the same issue with FreeNAS 11.1-U1. I created a bug report for FreeNAS and they are looking into it, but they were a little perplexed that a newer driver for FreeBSD was available but wasn't imported into the FreeBSD repository even though Intel is supposed to have FreeBSD committers.

02) Intel(R) Ethernet Converged Network       5.05  1572 00:005 Update

    Adapter X710-2                                              available

I am updating the firmware now to 6.01... But I am fairly certain that will not work. From what I can see in the bug tracking and googling, this has been going on for a while and either keeps coming back or never gets fixed.

From what I can see, the responsibility is on Intel to fix this for good and get the committers to imported the latest drivers in the FreeBSD head.

Intel, can we please get a permanent fix please?

Hello,

my question is directed to Intel NIC developers - we (CDN77) are using your X520-DA2 cards in thousands of servers - we have discovered that two different X520-DA2 NICs we have in our network do use the SAME MAC address.

The conflicting MAC is 00:1b:21:bc:32:15.

Is this something what 'can happen from time to time'? It would be a real flaw in the design - this makes makes me think the duplicate MAC is caused by some Chinese copy of the genuine Intel NIC.

You can imagine what mess can this cause.

If it helps, I can send more detail information regarding both NICs.

Thank you!

Hi,

We are working on a i210 flash-less design in which the i210 operates in Serdes/1000Base-BX mode attached to an external optical module. We have already validated the design as it has passed all acceptance tests.

Our application requires changing the value of one register (Fiber Specific Control Register 2). This that can only be done from the driver. We have successfully tested it under Linux. We would like to make it also work under Windows 7 Embedded Edition. Is it possible for us to have access to the source code of the Windows version of the driver?

Thanks in advance.

Best regards,

Manuel

Hi All,

I am using two DELL Poweredge R430 servers and each server has one dual port XL710-QDA2 [1]. Now we want to connect these two NICs directly using XLDACBL3 [2] cable, but we are not sure if the setup will work. On  server 1, we are running DPDK based L2Fwd application and on the other server DPDK-pktgen is generating the packets. Server 1 returns the packets back to server 2.

So can we use XLDACBL3 cables to connect these NICs directly and will they work in full-duplex mode?

[1]: Intel® Ethernet Converged Network Adapter XL710 10/40 GbE

[2]: QSFP+ Modules/Cables Compatible with Intel® Ethernet Server Adapter...

Thanks,

Anmol

Hi,

I recently bought a (second hand) Intel X540-T2 network adapter for my DIY-NAS (my workstation already has one).

Unfortunately, it seems to have problems booting on my ASUS Maximus 6 Gene board (Post code 55). I've narrowed down the problem to Dell's memory mapping of the firmware. It is a known problem with Dell X540-T2's and the Intel Z87/Z97 chipset when using 4 DIMMs. It can be fixed by removing on DIMM from the board, after which the board POSTs and boots without any problems. The Dell X540 does boots without any issues on the H110 and Z370 chipsets, even with all four DIMM slots populated.

The card I intended to use for my workstation is a passive one (Intel OEM) and this one boots just fine of my ASUS M6G board. Considering both NICs have an identical board (aside from the fan header on the Dell one), I suspect that the Dell card will still work when I flash it with the unmodified Intel firmware, correct? This should solve the EFI memory mapping problem that I encounter on my NAS.

Is what I'm trying to achieve possible? Or should I just get rid of the Dell X540 and buy a new OEM Intel card? I got the dell really cheap - and genuine X540's often go for over $300 used (not counting the potentially compromised chinese knock-offs)

I've done a bit of Google-Fu, but couldn't find the native Intel firmware anywhere.

I compiled and installed the network adapter driver for PCIe 40 Gb Ethernet(version 3.4.2). The driver is also loaded in the kernel successfully (Ubuntu 16.04). However, when I connect QSFP+ cables I am getting the following error message:

Rx/Tx is disabled on this device because an unsupported SFP+ module type was detected.

Is this because I am not using Intel QSFP+ cables?

Is there any way to allow unsupported SFP?

Best,

Marjan

I have got that problem on few laptops Dell Precision 3150. I have tried different versions of drivers, bios and clean Windows installation and problem still persist.

Using an updated driver, I cannot seem to get my interfaces up. Looks like the driver is not allowing the NIC to work due to the SFP+ module type, which worked previously on my Debian Stretch host. Clearly the NIC is detecting and reading the DAC, but I don't understand why it is not working. This is a 40G-breakout cable with 40-to-4x10G SFP+ DAC (TwinAx). I have tried adding the following to work around it, but it still does not work:

root@lab4:~# cat /etc/modprobe.d/i40e.conf

options i40e allow_unsupported_sfp=1

This was also discussed here, but there was no followup:

Intel Ethernet Drivers and Utilities / Mailing Lists

Output from dmesg:

[    4.439190] i40e 0000:08:00.3: PCI-Express: Speed 8.0GT/s Width x8

[    4.447918] i40e 0000:08:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 8 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA

[    4.453414] i40e 0000:08:00.2: Rx/Tx is disabled on this device because an unsupported SFP+ module type was detected.

[    4.465288] i40e 0000:08:00.2: Refer to the Intel(R) Ethernet Adapters and Devices User Guide for a list of supported modules.

Other pertinent output:

root@lab4:~# ethtool -m eth6

Identifier                                : 0x03 (SFP)

Extended identifier                       : 0x04 (GBIC/SFP defined by 2-wire interface ID)

Connector                                 : 0x21 (Copper pigtail)

Transceiver codes                         : 0x00 0x00 0x00 0x00 0x00 0x04 0x00 0x00

Transceiver type                          : FC: Copper Passive

Encoding                                  : 0x00 (unspecified)

BR, Nominal                               : 10300MBd

Rate identifier                           : 0x00 (unspecified)

Length (SMF,km)                           : 0km

Length (SMF)                              : 0m

Length (50um)                             : 0m

Length (62.5um)                           : 0m

Length (Copper)                           : 3m

Length (OM3)                              : 0m

Passive Cu cmplnce.                       : 0x01 (SFF-8431 appendix E) [SFF-8472 rev10.4 only]

Vendor name                               : Amphenol

Vendor OUI                                : 78:a7:14

Vendor PN                                 : 624400003

Vendor rev                                : A

Option values                             : 0x00 0x00

BR margin, max                            : 0%

BR margin, min                            : 0%

Vendor SN                                 : APF13470035GDT

Date code                                 : 131122

root@lab4:~# ethtool -i eth6

driver: i40e

version: 2.4.3

firmware-version: 6.01 0x800034af 1.1747.0

expansion-rom-version:

bus-info: 0000:08:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

root@lab4:~# ethtool eth6

Settings for eth6:

Supported ports: [ ]

Supported link modes:   Not reported

Supported pause frame use: Symmetric

Supports auto-negotiation: No

Advertised link modes:  Not reported

Advertised pause frame use: No

Advertised auto-negotiation: No

Speed: Unknown!

Duplex: Unknown! (255)

Port: Other

PHYAD: 0

Transceiver: internal

Auto-negotiation: off

Supports Wake-on: d

Wake-on: d

Current message level: 0x0000000f (15)

       drv probe link timer

Link detected: no

root@lab4:~# ip link show eth6

5: eth6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000

    link/ether 68:05:ca:2f:7c:b0 brd ff:ff:ff:ff:ff:ff

We have two Hyper-V 2016 servers in core mode, both have a pair of Intel X710 Adapters. Both have Hyper-V role enabled and the latest Intel firmware, drivers and Windows patches.

Using the PowerShell commands I see that the performance profile is "Standard server".  Normally if Hyper-V is detected the performance profile is automatically set to 'Virtualization' by the driver however this is not the case here.

I have tried to set this using this PowerShell command:

Set-IntelNetAdapterSetting -Name *X710* -RegistryKeyword PerformanceProfile -RegistryValue 5

But an error is thrown:

Set-IntelNetAdapterSetting : The setting could not be modified because the specified value is invalid for this device or setting.

Any suggestions please?