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?

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!

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.

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

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

I want to create Multi vlan for network card I210 and I217-LM on my PC.

but I always got "one or more VLAN(s) could not be created, Please check the adapter status and try again", meanwhile network card disabled.

my operation system is windows 764bit Ultimate.

after I tried several times, there were several virtual network card created, but no vlan. I even can not uninstall the created virtual network card.

anybody can give some suggestion?

hello

I designed a Thunderbolt dock with i210AT LAN. I want to know how to modify the "subsystem vender ID” and “subsystem ID.” I tried to run lanconfw64e.exe but cannot save.

Appreciate your help

Anderson

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.

Hello,

I have a network adapter "EXPI9301CTBLK", which I wanted to flash now.

I have entered the following commands "BootUtil -SAVEIMAGE -FILE = Backup.FLB" and "BootUtil -FE -ALL". Then I wanted to flash the new firmware with "BootUtil -UP = EFI -ALL-FILE = BOOTIMG.FLB".

Unfortunately, something went wrong.

First came a message that the Nic can not be initialized.

And now the adapter is no longer recognized, so I can not flash back.

Is the adapter still somehow save?

Please excuse my bad English, I write with translator.

Thanks in advance.

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,

Can I please ask clarifications on XL710 on VLAN steering. I have few questions regarding it on top of what was asked before. Really appreciate for your valuable input please

1. 7.4.8.4 "VEB/VEPA Switching Algorithm" states that filtering happens by MAC+VLAN. It is impossible to perform filtering by VLAN only, as I understand it is HW limitation.

XL710 has something called "7.4.8.2 S-comp Forwarding Algorithm" which looks like exactly what we want. It does forwarding of packets to specific VSI based on S-tag. S-tag is a part of "7.4.9.5.5.1 Add VSI (0x0210)" command. I guess we can configure several VSIs for expected S-tags. Can you help us understand how to use this algorithm please?

As I understood "port virtualizer" (7.4.2.4.3 "Cascaded VEB and port virtualizers") supposed to be configured to use this switching algorithm. In i40e driver (kernel or DPDK) I do not see anything related to configuration of "port virtualizers", except "i40e_aq_add_pvirt" function which is not used anywhere.

Is it possible to configure "port virtualizer" with existing latest i40e driver?

Another question is about "i40e_aq_set_vsi_uc_promisc_on_vlan" function in i40e driver (7.4.9.5.9.5 "Set VSI Promiscuous Modes"). It enables promiscuous mode for unicast packets with specific VLAN, so all packets with that VLAN will be replicated to configured VSI. In XL710 datasheet I`ve found that it works only in "Cloud VEB algorithm" (7.4.8.6). Can we somehow enable this algorithm with existing i40e drivers?

Thannk you so much

Hi,

I am observing a strange issue with i354 when auto-negotiation is turned off.

The device I have has 6 ethernet ports. Port 1 and 2 are based on i210 and port

3 to 6 are based on i354 (connected thru an external PHY). The CPU is Atom

Rangeley (4 core).

I have connected ports 3 and 4 back to back with an external cable. When the

link is forced to 100M/Full duplex with auto-negotiation off on both the ports,

the link does not come up.

Whereas the link comes up fine when eth3 (i354) and eth1 (i210) are connected

back to back and forced to 100M/Full duplex with auto-negotiation off.

This issue is seen with linux kernel (ubuntu 14.04).

Is this a known issue ?

Following are logs when running the test using ethtool from linux

admin@Ananda-Desk:~$ lspci | grep Ethernet

00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth2

00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth3

00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth4

00:14.3 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth5

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection

(rev 03) - eth0

02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection

(rev 03) - eth1

admin@Ananda-Desk:~$ ethtool -i eth3

driver: igb

version: 5.2.13-k

firmware-version: 0.0.0

bus-info: 0000:00:14.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: no

[Force 100M/Full on eth3]

admin@Ananda-Desk:~$ sudo ethtool -s eth3 autoneg off duplex full speed 100

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes

admin@Ananda-Desk:~$ ethtool eth4

Settings for eth4:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: Yes

        Speed: 100Mb/s

        Duplex: Half

        Port: Twisted Pair

        PHYAD: 2

        Transceiver: internal

        Auto-negotiation: on

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes

[Force 100M/Full on eth4]

admin@Ananda-Desk:~$ sudo ethtool -s eth4 autoneg off duplex full speed 100

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ ethtool eth4

Settings for eth4:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: Unknown!

        Duplex: Unknown! (255)

        Port: Twisted Pair

        PHYAD: 2

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: no <<<<<<<<<<<<<<

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: Unknown!

        Duplex: Unknown! (255)

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: no <<<<<<<<<<<

[Connect cables between eth1 and eth3]

[Force 100M/Full on eth1]

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ sudo ethtool -s eth1 autoneg off duplex full speed 100

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ ethtool eth1

Settings for eth1:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes <<<<<<<<<<<<

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes <<<<<<<<<<<<

Hej,

I am looking for the NIC 82551IT for a Win 10 (IoT Enterprise) driver. We Need either the driver as binary or the source code. Any ideas?

We have hands on the source code of an INTEL NIC i210IT driver for Win 10. Would it make sense to take an old Linux driver and integrate it in the Win driver?

We use the INTEL NIC 82551IT in our hardware. The 82551IT is directly connected to PCI. Currently we operate a Microsoft WES with INTEL's original driver.

Best Regards,

Jürgen

Hi.

I am having problems with I219-V VLAN tag. Whan adding  a tag I get blue screen every single time., reason Bad_pool_caller.

First step I am adding new VLAN in VLAN tab from Intel Ethernet conection I219-V:

And when adding new VLAN tag, let's say 13 it crashes:

I don't even get a chance to press second OK in Intel window, it crashes right here. It says Configuring for two seconds, maybe tree and the blue screen. I can make it anytime I want.
I tried with versions 12.17.8.7 and 12.15.25.6:

I have Lenovo T470s. Any help would be gratefull.

Regards

hi,

I am currently using a network adapter from Intel.I can see some information from the command line "lspci" and it is "Intel Corporation 82576 Gigabit Network Connection", so I think it is "Intel® 82576 Gigabit Ethernet Controller" but it seems there are two types of adapters under this category, one is 82576EB and the other one 82576NS. Are there any ways can allow customer to further find out what exact model of network adapter they are using? I have the Serial Number:"1CA2CE0341ADG18771-002" but I just done know how to use this number to search on the Intel website.

Thanks

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

I want to create Multi vlan for network card I210 and I217-LM on my PC.

but I always got "one or more VLAN(s) could not be created, Please check the adapter status and try again", meanwhile network card disabled.

my operation system is windows 764bit Ultimate.

after I tried several times, there were several virtual network card created, but no vlan. I even can not uninstall the created virtual network card.

anybody can give some suggestion?

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 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

Hi,

  We are observing that when Intel NIC I350 AAP (PCIE Endpoint) is used with Nvidia PCIE Root port, PCIE link fails to enter into L2 states in some cases.

Failure Scenario:

The application software initiates lower power sequence to bring the  PCIE link to enter into L2 state by first bringing the endpoint device into D3hot state followed by PME_Turn_Off request from Nvidia Root port to the endpoint device(NIC).

It is observed that  the endpoint device(NIC) does bring the link into L1 and also responds with PME_TO_ACK as expected but it does not initiate L2 entry request. So the PCIE Link (Root port) fails to enter into L2 state.

Details of the failure sequence and observations:

There seems to be some issue with the NIC I350 AAP during the L2 entry using Sequence-1 below, whereas same sequence works for the  NIC -  I350AM4. The Sequence-1 followed for the L2 entry and device details are described below.

Sequence-1 (Failing Sequence): L0 → L1 → L0 → L2/L3 Ready: Intel NIC I350 AAP Failing while   NIC - I350AM4 works fine.
1. Device is in L0 and System software directs all Functions of a Downstream component to D3hot.
2. The Downstream component then initiates the transition of the Link to L1 as required.
3. System software then causes the Root Complex to broadcast the PME_Turn_Off Message in preparation for removing the main power source.
4. This Message causes the subject Link to transition back to L0 in order to send it and to enable the Downstream component to respond with PME_TO_Ack.
5. After sending the PME_TO_Ack, the Downstream component initiates the L2/L3 Ready transition protocol. (Intel NIC I350 AAP fails in this step)

Failing Device Details :

I210T1BLK - Single Port NIC ( I350 AAP)

Date of Manufacture : 05/2014

Device 8086:1533 (rev 03)

Working Device Details :

Dual Port NIC -  I350AM4

Date of Manufacture  :  06/2013

Device 8086:1521 (rev 01)

It is also observed that bothIntel NIC I350 AAP and NIC   I350AM4 enter into L2 without any issue while following sequence-2 below.

Sequence-2 (passing sequence):
1. Device is in L0 and system software causes the Root Complex to broadcast the PME_Turn_Off Message in preparation for removing the main power source.
2. The Downstream components respond with PME_TO_Ack.
3. After sending the PME_TO_Ack, the Downstream component initiates the L2/L3 Ready transition protocol.

I am looking for help from your team if there is any known issue with Intel NIC I350 AAP related to  Link entering into L2 while following Sequence-1 describe above.

Please also suggest how can we proceed further to root cause the issue and avoid the failure for the L2 entry while following the sequence-1.

Thanks & Regards,

Alap

Baltazar