HI

I set 4000-4049 vlan filter to a vf:

for(vlanindex = 4000;vlanindex<=4049;vlanindex++)

        {

            diag = rte_eth_dev_vlan_filter(dev->port_id,vlanindex,1);

            if (diag) {

                VLOG_INFO("Interface %s vlan(%d) setup error: %s",

                          dev->up.name, vlanindex, rte_strerror(-diag));

                return diag;

            }

        }

2017-07-24T04:48:34.260Z|00076|dpdk|ERR|PMD: ixgbevf_vlan_filter_set(): Unable to set VF vlan

2017-07-24T04:48:34.260Z|00077|netdev_dpdk|INFO|Interface dpdk-trunk-0000.01.10.2 vlan(4003) setup error: Network is down

The error is in a random vlan filter set

dpdk version: 16.11

Same issue as seen elsewhere with the i218-V on a dozen Lenovo e550. Rather than going to two remote locations and popping the cmos on the lot, I'd like to give the ULP enable/disable utility a try.

Hi,

I am using a Dell PowerEdge R730 with Dual Xeon, each 22 cores, with 6 ixgbe compatible cards, on which I am running Linux with ixgbe driver version 4.4.0-k, using kernel versions both 4.7.10 and 4.9.6.
I am loading the ixgbe modules at boot time, bringing up the interfaces and setting smp_affinity to the cards, using the set_irq_affinity script, so all the possible RxTx IRQs are distributed between all the available cores.
The problem is that it happens, random, but quite often that the smp_affinity setting fails, and I need manually to re-run the script one or more times in order desired settings to be applied. There were also several occasions when the settings were not applied at all, and it took me several reboots to script to start working again.
The problem appears not only randomly as occurrence, but also at random NIC controllers, so I am excluding the possibility of failed HW, since I also changed NICs.

I added some debug messages to track the affinity setting in Linux kernel, and it turns out that most of the times when the setting fails the error that affinity setting function irq_do_set_affinity returns is EBUSY, but also sometimes it returns ENOSPC.

More investigation on the topic showed whenever EBUSY was returned the problem could be overcome with re-running the script. But if the error returned was ENOSPC, it takes several reboots for the problem to disappear.

In order to provide some more details on the system I am attaching two text files with the output of the modinfo of the ixgbe and lspci on the machine.

Hi All,

I am using RHEL7.3 with Intel-82599ES nic cards to launch VMs with SRIOV enabled nic cards. I am using configuring only one VF per PF. I am configuring this VF with vlan, trust mode on and disabling spoof chk.

But, when I am sending vlan tagged packets from Guest VM, I can see the "spoofed packet detected" message in dmesg for this PF card.

We have also disabled the rx/tx vlan offload using ethtool command.

Here are setup details:

Kernel version

# uname -r

3.10.0-514.el7.x86_64

PF/VF configuration:

# ip link show eth2

4: eth2: <BROADCAST,MULTICAST,ALLMULTI,PROMISC,UP,LOWER_UP> mtu 9192 qdisc mq state UP mode DEFAULT qlen 1000

    link/ether 90:e2:ba:a5:98:7c brd ff:ff:ff:ff:ff:ff

    vf 0 MAC fa:16:3e:73:12:6c, vlan 1500, spoof checking off, link-state auto, trust on

IXGBE version

# ethtool -i eth2

driver: ixgbe

version: 4.4.0-k-rh7.3

firmware-version: 0x61bd0001

expansion-rom-version:

bus-info: 0000:81:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: no

Messages from dmesg

[441100.018278] ixgbe 0000:81:00.0 eth2: 3 Spoofed packets detected

[441102.022383] ixgbe 0000:81:00.0 eth2: 2 Spoofed packets detected

[441104.026460] ixgbe 0000:81:00.0 eth2: 3 Spoofed packets detected

[441106.030516] ixgbe 0000:81:00.0 eth2: 2 Spoofed packets detected

LSPCI output

# lspci -nn | grep Ether | grep 82599

81:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)

81:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)

81:10.0 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)

Ethtool -k output

# ethtool -k eth2 | grep vlan

rx-vlan-offload: off

tx-vlan-offload: off

rx-vlan-filter: on

vlan-challenged: off [fixed]

tx-vlan-stag-hw-insert: off [fixed]

rx-vlan-stag-hw-parse: off [fixed]

rx-vlan-stag-filter: off [fixed]

Please let me know, if you any need any other information.

Regards

Pratik

Hello,

I am new to this community. I subscribed to ask a question here because I am really stuck.

My company makes electronic devices that use UDP 100 MB Ethernet communication with a PC (under Windows 7, 8.1 or 10).

It works perfectly with other brands of Ethernet adapters; but there is a strange behavious with the Intel NICs we tried (at least I219-V, I219-LM and I217-LM).

Basically, our electronic devices can be considered as cameras capturing about 150 images per second.

We send a small command on one socket via UDP to tell it to capture an image, then we receive the compressed image as a set of UDP packets on another socket.

Each packet contains up to 1444 bytes of data (to which one can add the data from the different layers of protocols, which in the end does not exceed the standard packet size => no need to use Jumbo packets).

The problem is that, sometimes (this varies from as often as every 5 seconds to as rarely as only once within a 10-mn period), I am waiting forever (until the defined UDP time out) for the data to arrive while it has been sent (I can see it by sniffing the data from another computer connected to the same switch). I could believe that the UDP packet was lost by the Intel NIC, but it has not been lost. If I send a new image capture command, the packets that I was waiting finally arrive, followed by the packets of the new image.

Why are those packets stuck?

Is there any advanced parameter that I could modify from the device driver's configuration window or from a Registry key?

Note that I tried updating the Intel driver to recent versions (last one is 22.4.0.1). It seems to perform a little better that some other versions I tried (like the one installed by default in Windows), but none of the versions I tried work perfectly.

Many thanks in advance if you can help me understand what is wrong (either from me or from the driver). I have been struggling on this problem for months and we have to equip our customers who own a laptop with an Intel NIC with USB adapters with a NIC made by another brand to bypass the problem.

Karl

Hi:

I am using the i40e_4.4.0 driver for XL710 Network Card. Currently, I am trying to loopback the connections.

For this purpose, I had to set the two ports on promiscuous mode. Thus, using my application, I crated custom UDP packets.

For the Rx Queue setting, I have set the flow director as:

ethtool -N ens1f0 flow-type udp4 dst-port 319 action 3 loc

ethtool -N ens1f1 flow-type udp4 dst-port 319 action 3 loc

Essentially, I want all the packets with this dst-port to be forwarded to Queue 3. I can also see the rule has been inserted.

But, as seen in the attached picture, the flow director is not able to match the incoming packet. Thus, it does not forward the incoming packet to my desired queue.

Is this error due to promiscuous mode that I had set on the NIC ports ?

I am not sure what's creating this issue. Also, I have verified that the incoming packet is destined for Port 319.

I will be able to provide other details, if needed !

I would appreciate any help.

Thanks !

I have an Asus Z170 Pro Gaming motherboard with the I219-V LAN port but even on a fresh Windows 7 or Windows 10 installation, the port always shows up as having the (2) prefix even though its the only LAN port available and its the first time drivers have been installed for it (for that OS installation after formatting the HDD). The driver version I'm currently using is 12.15.25.6 from earlier this year.

I'm pretty sure that at some stage I've seen it as simply Intel(R) Ethernet Connection I219-V and I'd like to get back to that but how? FWIW the hardware is working fine, I'm just fussy about my system configuration and would like this to be as originally intended.

I'm trying to configure Wake on Lan on my Windows 10 Pro 64bit HP Pavilion Elite HPE.  I've configured my "lesser" machines just fine, but this one has the 82567V-2 gigabit card which doesn't show any wake on magic packet options in advanced properties.  I've tried many different options but the card still won't stay awake when powered down.  I have unchecked allow the computer to power it down, enabled wake on lan in bios, disabled fast boot and hibernate.  Driver is up to date from windows update. I also searched for a specific driver on intel's website but there isn't one for Windows 10 64 bit.  Your help is appreciated.  Thank you.

Has anyone ran into a similar issue. After a yum update to kernel 2.6.32-696.3.2.el6.x86_64 or 2.6.32-696. My bond2 interface stops working correctly.

After that I am unable to set speed settings and unable to ping anything. This is causing my NFS shares to stop working, as they are being mounted via that nic.

When I roll back to 2.6.32-642.13.1.el6.x86_64 starts working right away.

from dmesg it looks like the kernel is unable to detect that we are using 10Gbps cards. How do I proceed with reporting this bug?

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

2.6.32-696.3.2.el6.x86_64

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

# modinfo i40e

filename:       /lib/modules/2.6.32-696.3.2.el6.x86_64/kernel/drivers/net/i40e/i40e.ko

version:        1.5.10-k

license:        GPL

description:    Intel(R) Ethernet Connection XL710 Network Driver

author:         Intel Corporation, <e1000-devel@lists.sourceforge.net>

srcversion:     B5DC8E286FEFB9414076D56

alias:          pci:v00008086d00001588sv*sd*bc*sc*i*

alias:          pci:v00008086d00001587sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D4sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D3sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D2sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D1sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D0sv*sd*bc*sc*i*

alias:          pci:v00008086d000037CFsv*sd*bc*sc*i*

alias:          pci:v00008086d000037CEsv*sd*bc*sc*i*

alias:          pci:v00008086d00001587sv*sd*bc*sc*i*

alias:          pci:v00008086d00001589sv*sd*bc*sc*i*

alias:          pci:v00008086d00001586sv*sd*bc*sc*i*

alias:          pci:v00008086d00001585sv*sd*bc*sc*i*

alias:          pci:v00008086d00001584sv*sd*bc*sc*i*

alias:          pci:v00008086d00001583sv*sd*bc*sc*i*

alias:          pci:v00008086d00001581sv*sd*bc*sc*i*

alias:          pci:v00008086d00001580sv*sd*bc*sc*i*

alias:          pci:v00008086d00001574sv*sd*bc*sc*i*

alias:          pci:v00008086d00001572sv*sd*bc*sc*i*

depends:        ptp

vermagic:       2.6.32-696.3.2.el6.x86_64 SMP mod_unload modversions

parm:           debug:Debug level (0=none,...,16=all) (int)

# grep i40e /tmp/dmesg-2.6.32-696.3.2.el6.x86_64

i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.5.10-k

i40e: Copyright (c) 2013 - 2014 Intel Corporation.

i40e 0000:0b:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16

i40e 0000:0b:00.0: setting latency timer to 64

i40e 0000:0b:00.0: fw 4.50.37442 api 1.4 nvm 4.60 0x80001f47 1.3072.0

i40e 0000:0b:00.0: MAC address: <REDACTED>

i40e 0000:0b:00.0: irq 85 for MSI/MSI-X

i40e 0000:0b:00.0: irq 86 for MSI/MSI-X

i40e 0000:0b:00.0: irq 87 for MSI/MSI-X

i40e 0000:0b:00.0: irq 88 for MSI/MSI-X

i40e 0000:0b:00.0: irq 89 for MSI/MSI-X

i40e 0000:0b:00.0: irq 90 for MSI/MSI-X

i40e 0000:0b:00.0: irq 91 for MSI/MSI-X

i40e 0000:0b:00.0: irq 92 for MSI/MSI-X

i40e 0000:0b:00.0: irq 93 for MSI/MSI-X

i40e 0000:0b:00.0: irq 94 for MSI/MSI-X

i40e 0000:0b:00.0: irq 95 for MSI/MSI-X

i40e 0000:0b:00.0: irq 96 for MSI/MSI-X

i40e 0000:0b:00.0: irq 97 for MSI/MSI-X

i40e 0000:0b:00.0: irq 98 for MSI/MSI-X

i40e 0000:0b:00.0: irq 99 for MSI/MSI-X

i40e 0000:0b:00.0: irq 100 for MSI/MSI-X

i40e 0000:0b:00.0: irq 101 for MSI/MSI-X

i40e 0000:0b:00.0: irq 102 for MSI/MSI-X

i40e 0000:0b:00.0: irq 103 for MSI/MSI-X

i40e 0000:0b:00.0: irq 104 for MSI/MSI-X

i40e 0000:0b:00.0: irq 105 for MSI/MSI-X

i40e 0000:0b:00.0: irq 106 for MSI/MSI-X

i40e 0000:0b:00.0: irq 107 for MSI/MSI-X

i40e 0000:0b:00.0: irq 108 for MSI/MSI-X

i40e 0000:0b:00.0: irq 109 for MSI/MSI-X

i40e 0000:0b:00.0: irq 110 for MSI/MSI-X

i40e 0000:0b:00.0: PCI-Express: Speed 8.0GT/s Width x8

i40e 0000:0b:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 QP: 16 RX: 1BUF RSS FD_ATR FD_SB NTUPLE VxLAN PTP VEPA

i40e 0000:0b:00.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16

i40e 0000:0b:00.1: setting latency timer to 64

i40e 0000:0b:00.1: fw 4.50.37442 api 1.4 nvm 4.60 0x80001f47 1.3072.0

i40e 0000:0b:00.1: MAC address: <REDACTED>

i40e 0000:0b:00.1: irq 111 for MSI/MSI-X

i40e 0000:0b:00.1: irq 112 for MSI/MSI-X

i40e 0000:0b:00.1: irq 113 for MSI/MSI-X

i40e 0000:0b:00.1: irq 114 for MSI/MSI-X

i40e 0000:0b:00.1: irq 115 for MSI/MSI-X

i40e 0000:0b:00.1: irq 116 for MSI/MSI-X

i40e 0000:0b:00.1: irq 117 for MSI/MSI-X

i40e 0000:0b:00.1: irq 118 for MSI/MSI-X

i40e 0000:0b:00.1: irq 119 for MSI/MSI-X

i40e 0000:0b:00.1: irq 120 for MSI/MSI-X

i40e 0000:0b:00.1: irq 121 for MSI/MSI-X

i40e 0000:0b:00.1: irq 122 for MSI/MSI-X

i40e 0000:0b:00.1: irq 123 for MSI/MSI-X

i40e 0000:0b:00.1: irq 124 for MSI/MSI-X

i40e 0000:0b:00.1: irq 125 for MSI/MSI-X

i40e 0000:0b:00.1: irq 126 for MSI/MSI-X

i40e 0000:0b:00.1: irq 127 for MSI/MSI-X

i40e 0000:0b:00.1: irq 128 for MSI/MSI-X

i40e 0000:0b:00.1: irq 129 for MSI/MSI-X

i40e 0000:0b:00.1: irq 130 for MSI/MSI-X

i40e 0000:0b:00.1: irq 131 for MSI/MSI-X

i40e 0000:0b:00.1: irq 132 for MSI/MSI-X

i40e 0000:0b:00.1: irq 133 for MSI/MSI-X

i40e 0000:0b:00.1: irq 134 for MSI/MSI-X

i40e 0000:0b:00.1: irq 135 for MSI/MSI-X

i40e 0000:0b:00.1: irq 136 for MSI/MSI-X

i40e 0000:0b:00.1: PCI-Express: Speed 8.0GT/s Width x8

i40e 0000:0b:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 QP: 16 RX: 1BUF RSS FD_ATR FD_SB NTUPLE VxLAN PTP VEPA

i40e 0000:0b:00.0: eth8: already using mac address <REDACTED>

i40e 0000:0b:00.1: eth9: set new mac address <REDACTED>

# ethtool -i bond2

driver: bonding

version: 3.7.1

firmware-version: 2

bus-info:

supports-statistics: no

supports-test: no

supports-eeprom-access: no

supports-register-dump: no

supports-priv-flags: no

# cat /proc/net/bonding/bond2

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)

Primary Slave: None

Currently Active Slave: None

MII Status: down

MII Polling Interval (ms): 100

Up Delay (ms): 0

Down Delay (ms): 0

Slave Interface: eth9

MII Status: down

Speed: Unknown

Duplex: Unknown

Link Failure Count: 0

Permanent HW addr:  <REDACTED>

Slave queue ID: 0

Slave Interface: eth8

MII Status: down

Speed: Unknown

Duplex: Unknown

Link Failure Count: 0

Permanent HW addr:  <REDACTED>

Slave queue ID: 0

ethtool -s bond2 speed 10000 duplex full autoneg off

Cannot set new settings: Operation not supported

  not setting speed

  not setting duplex

  not setting autoneg

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

2.6.32-642.13.1.el6.x86_64

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

# modinfo i40e

filename:       /lib/modules/2.6.32-642.13.1.el6.x86_64/kernel/drivers/net/i40e/i40e.ko

version:        1.4.7-k

license:        GPL

description:    Intel(R) Ethernet Connection XL710 Network Driver

author:         Intel Corporation, <e1000-devel@lists.sourceforge.net>

srcversion:     B91F227B49241127F18771D

alias:          pci:v00008086d00001588sv*sd*bc*sc*i*

alias:          pci:v00008086d00001587sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D2sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D1sv*sd*bc*sc*i*

alias:          pci:v00008086d000037D0sv*sd*bc*sc*i*

alias:          pci:v00008086d00001587sv*sd*bc*sc*i*

alias:          pci:v00008086d00001589sv*sd*bc*sc*i*

alias:          pci:v00008086d00001586sv*sd*bc*sc*i*

alias:          pci:v00008086d00001585sv*sd*bc*sc*i*

alias:          pci:v00008086d00001584sv*sd*bc*sc*i*

alias:          pci:v00008086d00001583sv*sd*bc*sc*i*

alias:          pci:v00008086d00001581sv*sd*bc*sc*i*

alias:          pci:v00008086d00001580sv*sd*bc*sc*i*

alias:          pci:v00008086d0000157Fsv*sd*bc*sc*i*

alias:          pci:v00008086d00001574sv*sd*bc*sc*i*

alias:          pci:v00008086d00001572sv*sd*bc*sc*i*

depends:        ptp

vermagic:       2.6.32-642.13.1.el6.x86_64 SMP mod_unload modversions

parm:           debug:Debug level (0=none,...,16=all) (int)

grep i40e /tmp/dmesg-2.6.32-642.13.1.el6.x86_64

i40e: Intel(R) Ethernet Connection XL710 Network Driver - version 1.4.7-k

i40e: Copyright (c) 2013 - 2014 Intel Corporation.

i40e 0000:0b:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16

i40e 0000:0b:00.0: setting latency timer to 64

i40e 0000:0b:00.0: fw 4.50.37442 api 1.4 nvm 4.60 0x80001f47 1.3072.0

i40e 0000:0b:00.0: MAC address: <REDACTED>

i40e 0000:0b:00.0: irq 85 for MSI/MSI-X

i40e 0000:0b:00.0: irq 86 for MSI/MSI-X

i40e 0000:0b:00.0: irq 87 for MSI/MSI-X

i40e 0000:0b:00.0: irq 88 for MSI/MSI-X

i40e 0000:0b:00.0: irq 89 for MSI/MSI-X

i40e 0000:0b:00.0: irq 90 for MSI/MSI-X

i40e 0000:0b:00.0: irq 91 for MSI/MSI-X

i40e 0000:0b:00.0: irq 92 for MSI/MSI-X

i40e 0000:0b:00.0: irq 93 for MSI/MSI-X

i40e 0000:0b:00.0: irq 94 for MSI/MSI-X

i40e 0000:0b:00.0: irq 95 for MSI/MSI-X

i40e 0000:0b:00.0: irq 96 for MSI/MSI-X

i40e 0000:0b:00.0: irq 97 for MSI/MSI-X

i40e 0000:0b:00.0: irq 98 for MSI/MSI-X

i40e 0000:0b:00.0: irq 99 for MSI/MSI-X

i40e 0000:0b:00.0: irq 100 for MSI/MSI-X

i40e 0000:0b:00.0: irq 101 for MSI/MSI-X

i40e 0000:0b:00.0: irq 102 for MSI/MSI-X

i40e 0000:0b:00.0: irq 103 for MSI/MSI-X

i40e 0000:0b:00.0: irq 104 for MSI/MSI-X

i40e 0000:0b:00.0: irq 105 for MSI/MSI-X

i40e 0000:0b:00.0: irq 106 for MSI/MSI-X

i40e 0000:0b:00.0: irq 107 for MSI/MSI-X

i40e 0000:0b:00.0: irq 108 for MSI/MSI-X

i40e 0000:0b:00.0: irq 109 for MSI/MSI-X

i40e 0000:0b:00.0: irq 110 for MSI/MSI-X

i40e 0000:0b:00.0: PCI-Express: Speed 8.0GT/s Width x8

i40e 0000:0b:00.0: Features: PF-id[0] VFs: 64 VSIs: 66 QP: 16 RX: 1BUF RSS FD_ATR FD_SB NTUPLE VxLAN PTP VEPA

i40e 0000:0b:00.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16

i40e 0000:0b:00.1: setting latency timer to 64

i40e 0000:0b:00.1: fw 4.50.37442 api 1.4 nvm 4.60 0x80001f47 1.3072.0

i40e 0000:0b:00.1: MAC address: <REDACTED>

i40e 0000:0b:00.1: irq 111 for MSI/MSI-X

i40e 0000:0b:00.1: irq 112 for MSI/MSI-X

i40e 0000:0b:00.1: irq 113 for MSI/MSI-X

i40e 0000:0b:00.1: irq 114 for MSI/MSI-X

i40e 0000:0b:00.1: irq 115 for MSI/MSI-X

i40e 0000:0b:00.1: irq 116 for MSI/MSI-X

i40e 0000:0b:00.1: irq 117 for MSI/MSI-X

i40e 0000:0b:00.1: irq 118 for MSI/MSI-X

i40e 0000:0b:00.1: irq 119 for MSI/MSI-X

i40e 0000:0b:00.1: irq 120 for MSI/MSI-X

i40e 0000:0b:00.1: irq 121 for MSI/MSI-X

i40e 0000:0b:00.1: irq 122 for MSI/MSI-X

i40e 0000:0b:00.1: irq 123 for MSI/MSI-X

i40e 0000:0b:00.1: irq 124 for MSI/MSI-X

i40e 0000:0b:00.1: irq 125 for MSI/MSI-X

i40e 0000:0b:00.1: irq 126 for MSI/MSI-X

i40e 0000:0b:00.1: irq 127 for MSI/MSI-X

i40e 0000:0b:00.1: irq 128 for MSI/MSI-X

i40e 0000:0b:00.1: irq 129 for MSI/MSI-X

i40e 0000:0b:00.1: irq 130 for MSI/MSI-X

i40e 0000:0b:00.1: irq 131 for MSI/MSI-X

i40e 0000:0b:00.1: irq 132 for MSI/MSI-X

i40e 0000:0b:00.1: irq 133 for MSI/MSI-X

i40e 0000:0b:00.1: irq 134 for MSI/MSI-X

i40e 0000:0b:00.1: irq 135 for MSI/MSI-X

i40e 0000:0b:00.1: irq 136 for MSI/MSI-X

i40e 0000:0b:00.1: PCI-Express: Speed 8.0GT/s Width x8

i40e 0000:0b:00.1: Features: PF-id[1] VFs: 64 VSIs: 66 QP: 16 RX: 1BUF RSS FD_ATR FD_SB NTUPLE VxLAN PTP VEPA

i40e 0000:0b:00.0: eth8: already using mac address <REDACTED>

i40e 0000:0b:00.0: eth8: NIC Link is Up 10 Gbps Full Duplex, Flow Control: None

i40e 0000:0b:00.1: eth9: set new mac address <REDACTED>

i40e 0000:0b:00.1: eth9: NIC Link is Up 10 Gbps Full Duplex, Flow Control: None

# ethtool -i bond2

driver: bonding

version: 3.7.1

firmware-version: 2

bus-info:

supports-statistics: no

supports-test: no

supports-eeprom-access: no

supports-register-dump: no

supports-priv-flags: no

# cat /proc/net/bonding/bond2

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup)

Primary Slave: None

Currently Active Slave: eth8

MII Status: up

MII Polling Interval (ms): 100

Up Delay (ms): 0

Down Delay (ms): 0

Slave Interface: eth8

MII Status: up

Speed: 10000 Mbps

Duplex: full

Link Failure Count: 0

Permanent HW addr:  <REDACTED>

Slave queue ID: 0

Slave Interface: eth9

MII Status: up

Speed: 10000 Mbps

Duplex: full

Link Failure Count: 0

Permanent HW addr:  <REDACTED>

Slave queue ID: 0

Hi Intel comunity,

We have serious problem with intel cards (X710 and XL170). 

The linux server (Dell Power Edge 630) don’t see them completely under RedHat 7.2. I dont see the interfaces under linux ifconfig -a.

I have installed the last drivers (ixgbe-5.1.3 and i40e-2.0.26) but didnt succedded to update the firmware (if it is the problem).

Here below the output of my server:

• From "modinfo" I get the following output:

[root@TBOS ~]# modinfo i40e

filename: /lib/modules/3.10.0-327.el7.x86_64/updates/drivers/net/ethernet/intel/i40e/i40e.ko

version: 2.0.26

license: GPL

description: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver

author: Intel Corporation, <e1000-devel@lists.sourceforge.net>

rhelversion: 7.2

srcversion: F49696A466EC36F89F8FE86

alias: pci:v00008086d0000158Bsv*sd*bc*sc*i*

alias: pci:v00008086d0000158Asv*sd*bc*sc*i*

alias: pci:v00008086d000037D3sv*sd*bc*sc*i*

alias: pci:v00008086d000037D2sv*sd*bc*sc*i*

alias: pci:v00008086d000037D1sv*sd*bc*sc*i*

alias: pci:v00008086d000037D0sv*sd*bc*sc*i*

alias: pci:v00008086d000037CFsv*sd*bc*sc*i*

alias: pci:v00008086d000037CEsv*sd*bc*sc*i*

alias: pci:v00008086d0000374Csv*sd*bc*sc*i*

alias: pci:v00008086d00001588sv*sd*bc*sc*i*

alias: pci:v00008086d00001587sv*sd*bc*sc*i*

alias: pci:v00008086d00001589sv*sd*bc*sc*i*

alias: pci:v00008086d00001586sv*sd*bc*sc*i*

alias: pci:v00008086d00001585sv*sd*bc*sc*i*

alias: pci:v00008086d00001584sv*sd*bc*sc*i*

alias: pci:v00008086d00001583sv*sd*bc*sc*i*

alias: pci:v00008086d00001581sv*sd*bc*sc*i*

alias: pci:v00008086d00001580sv*sd*bc*sc*i*

alias: pci:v00008086d00001574sv*sd*bc*sc*i*

alias: pci:v00008086d00001572sv*sd*bc*sc*i*

depends: ptp,vxlan

vermagic: 3.10.0-327.el7.x86_64 SMP mod_unload modversions

parm: debug:Debug level (0=none,...,16=all) (int)

[root@TBOS ~]#

• From ifconfig –a, we don’t see the port at all !!!

• When I want to update the firmware, I get
  • [root@TBOS Linux_x64]# ./nvmupdate64e

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.28.19.4

Copyright (C) 2013 - 2016 Intel Corporation.

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [*|........]

Num Description Ver. DevId S:B    Status

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

01) Intel(R) Ethernet Converged Network 1572 00:004 Access error

Adapter X710

Tool execution completed with the following status: Device not found

Press any key to exit.

• Dmesg output:

[root@TBOS ~]# dmesg| grep i40

[ 3.549403] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network Driver - version 2.0.26

[ 3.549405] i40e: Copyright(c) 2013 - 2017 Intel Corporation.

[ 3.578751] i40e 0000:04:00.0: fw 4.33.31377 api 1.2 nvm 4.41 0x80001869 16.5.10

[ 3.578754] i40e 0000:04:00.0: The driver for the device detected an older version of the NVM image than expected. Please update the NVM image.

[ 3.822134] i40e 0000:04:00.0: MAC address: 3c:fd:fe:0c:cb:e0

[    3.835115] i40e 0000:04:00.0: Query for DCB configuration failed, err I40E_ERR_ADMIN_QUEUE_ERROR aq_err I40E_AQ_RC_EPERM

[ 3.835118] i40e 0000:04:00.0: DCB init failed -53, disabled

[ 3.835166] i40e 0000:04:00.0: irq 91 for MSI/MSI-X

…..

[ 3.836118] i40e 0000:04:00.0: irq 148 for MSI/MSI-X

[ 4.050907] i40e 0000:04:00.0: Added LAN device PF0 bus=0x04 dev=0x00 func=0x00

[ 4.050912] i40e 0000:04:00.0: PCI-Express: Speed 8.0GT/s Width x8

[ 4.080877] i40e 0000:04:00.0: Features: PF-id[0] VFs: 32 VSIs: 34 QP: 48 RSS FD_ATR FD_SB NTUPLE CloudF VxLAN Geneve NVGRE PTP VEPA

[ 4.094861] i40e 0000:04:00.1: fw 4.33.31377 api 1.2 nvm 4.41 0x80001869 16.5.10

[ 4.094864] i40e 0000:04:00.1: The driver for the device detected an older version of the NVM image than expected. Please update the NVM image.

[ 4.339689] i40e 0000:04:00.1: MAC address: 3c:fd:fe:0c:cb:e2

[    4.349612] i40e 0000:04:00.1: Query for DCB configuration failed, err I40E_ERR_ADMIN_QUEUE_ERROR aq_err I40E_AQ_RC_EPERM

[ 4.349615] i40e 0000:04:00.1: DCB init failed -53, disabled

[ 4.349684] i40e 0000:04:00.1: irq 150 for MSI/MSI-X

……

[ 4.350710] i40e 0000:04:00.1: irq 207 for MSI/MSI-X

[ 4.499464] i40e 0000:04:00.1: Added LAN device PF1 bus=0x04 dev=0x00 func=0x01

[ 4.499469] i40e 0000:04:00.1: PCI-Express: Speed 8.0GT/s Width x8

[ 4.529440] i40e 0000:04:00.1: Features: PF-id[1] VFs: 32 VSIs: 34 QP: 48 RSS FD_ATR FD_SB NTUPLE CloudF VxLAN Geneve NVGRE PTP VEPA

[ 4.543425] i40e 0000:04:00.2: fw 4.33.31377 api 1.2 nvm 4.41 0x80001869 16.5.10

[ 4.543427] i40e 0000:04:00.2: The driver for the device detected an older version of the NVM image than expected. Please update the NVM image.

[ 4.989984] i40e 0000:04:00.2: MAC address: 3c:fd:fe:0c:cb:e4

[ 5.000011] i40e 0000:04:00.2: Query for DCB configuration failed, err I40E_ERR_ADMIN_QUEUE_ERROR aq_err I40E_AQ_RC_EPERM

[ 5.000014] i40e 0000:04:00.2: DCB init failed -53, disabled

[ 5.000085] i40e 0000:04:00.2: irq 208 for MSI/MSI-X

…..

[ 5.001379] i40e 0000:04:00.2: irq 265 for MSI/MSI-X

[ 5.228749] i40e 0000:04:00.2: Added LAN device PF2 bus=0x04 dev=0x00 func=0x02

[ 5.228754] i40e 0000:04:00.2: PCI-Express: Speed 8.0GT/s Width x8

[ 5.263716] i40e 0000:04:00.2: Features: PF-id[2] VFs: 32 VSIs: 34 QP: 48 RSS FD_ATR FD_SB NTUPLE CloudF VxLAN Geneve NVGRE PTP VEPA

[ 5.277703] i40e 0000:04:00.3: fw 4.33.31377 api 1.2 nvm 4.41 0x80001869 16.5.10

[ 5.277705] i40e 0000:04:00.3: The driver for the device detected an older version of the NVM image than expected. Please update the NVM image.

[ 5.566417] i40e 0000:04:00.3: MAC address: 3c:fd:fe:0c:cb:e6

[ 5.576408] i40e 0000:04:00.3: Query for DCB configuration failed, err I40E_ERR_ADMIN_QUEUE_ERROR aq_err I40E_AQ_RC_EPERM

[ 5.576411] i40e 0000:04:00.3: DCB init failed -53, disabled

[ 5.576487] i40e 0000:04:00.3: irq 266 for MSI/MSI-X

……

[ 5.577839] i40e 0000:04:00.3: irq 323 for MSI/MSI-X

[ 5.725374] i40e 0000:04:00.3: Added LAN device PF3 bus=0x04 dev=0x00 func=0x03

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

[ 5.755339] i40e 0000:04:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 48 RSS FD_ATR FD_SB NTUPLE CloudF VxLAN Geneve NVGRE PTP VEPA

[   67.004064] i40e 0000:04:00.0: removed PHC from p2p1

[   67.040316] i40e 0000:04:00.0: Deleted LAN device PF0 bus=0x04 dev=0x00 func=0x00

[   70.039865] i40e 0000:04:00.1: removed PHC from p2p2

[   70.070096] i40e 0000:04:00.1: Deleted LAN device PF1 bus=0x04 dev=0x00 func=0x01

[   73.240777] i40e 0000:04:00.2: removed PHC from p2p3

[   73.279308] i40e 0000:04:00.2: Deleted LAN device PF2 bus=0x04 dev=0x00 func=0x02

[   74.650315] i40e 0000:04:00.3: removed PHC from p2p4

[   74.690215] i40e 0000:04:00.3: Deleted LAN device PF3 bus=0x04 dev=0x00 func=0x03

[root@TBOS ~]#

• From lspci| egrep -i "Network|Ethernet" we see the following output:
  • 04:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
  • 04:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
  • 04:00.2 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)
  • 04:00.3 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)

Please help ...

Thanks

Hi,

Just checking if GT desktop adapter supports Windows 10? Thanks,

Hi, I have several X710-DA4 that I purchased at different times, and some of them I was able to grab the latest firmware (5.05) and upgrade them. nvmupdate64e and ethool show this on the good ones:

driver: i40e

version: 1.6.42

firmware-version: 5.05 0x8000289d 1.1568.0

bus-info: 0000:85:00.2

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [.........*]

Num Description                               Ver. DevId S:B    Status

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

01) Intel(R) Ethernet Converged Network       5.05  1572 00:004 Up to date

    Adapter X710-4

02) Intel(R) I350 Gigabit Network Connection  1.99  1521 00:129 Update not

                                                                available

03) Intel(R) Ethernet Converged Network       5.05  1572 00:133 Up to date

    Adapter X710-4

On the other box, it will not let me upgrade:

driver: i40e

version: 2.0.23

firmware-version: 4.10 0x800011c5 0.0.0

bus-info: 0000:01:00.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

WARNING: To avoid damage to your device, do not stop the update or reboot or power off the system during this update.

Inventory in progress. Please wait [|.........]

Num Description                               Ver. DevId S:B    Status

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

01) Intel(R) Ethernet Converged Network       4.10  1572 00:001 Update not

    Adapter X710-4                                              available

02) Intel(R) I350 Gigabit Network Connection  1.99  1521 00:129 Update not

                                                                available

03) Intel(R) Ethernet Converged Network       4.10  1572 00:130 Update not

    Adapter X710-4                                              available

Does anyone know what's wrong?

Hi

How about Windows 2012?

thanks

What are the differences between them?

Intel Gigabit CT Desktop Adapter

and

Intel Gigabit CT2 Desktop Adapter

HI Everyone,

We are using XL710 hardware on Linux 4.1.20 kernel.

We have an issue where the following behavior is noticed.

• When we send a simple loop back traffic to the XL710, it works fine.
• When a specific PPPoE packet is sent from an external port to the XL710, on Linux we notice that the XL710 driver has no response. There is no interrupt is raised for this received packet.
• After the above condition, XL710 stops receiving any packet.

Here is the packet contents for a good packet and the failing packet.

I can send any number of good packets, and XL710 is able to received it.

After I send a single failing packet, XL710 stop receiving packets. In fact, it does not receive even the good packets after this.

Good Packet:

Frame 2: 128 bytes on wire (1024 bits), 124 bytes captured (992 bits) on interface 0

    Interface id: 0 (\\.\pipe\view_capture_172-27-5-51_6_89_07182017_154149)

    Encapsulation type: Ethernet (1)

    Arrival Time: Jul 18, 2017 15:41:13.680293000 India Standard Time

    [Time shift for this packet: 0.000000000 seconds]

    Epoch Time: 1500372673.680293000 seconds

    [Time delta from previous captured frame: 0.496532000 seconds]

    [Time delta from previous displayed frame: 0.496532000 seconds]

    [Time since reference or first frame: 0.496532000 seconds]

    Frame Number: 2

    Frame Length: 128 bytes (1024 bits)

    Capture Length: 124 bytes (992 bits)

    [Frame is marked: False]

    [Frame is ignored: False]

    [Protocols in frame: eth:ethertype:mpls:pwethheuristic:pwethcw:eth:ethertype:vlan:ethertype:vlan:ethertype:pppoes:ppp:ipcp]

Ethernet II, Src: Performa_00:00:02 (00:10:94:00:00:02), Dst: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

    Destination: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

        Address: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)

    Source: Performa_00:00:02 (00:10:94:00:00:02)

        Address: Performa_00:00:02 (00:10:94:00:00:02)

        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)

    Type: MPLS label switched packet (0x8847)

MultiProtocol Label Switching Header, Label: 1 (Router Alert), Exp: 0, S: 1, TTL: 64

    0000 0000 0000 0000 0001 .... .... .... = MPLS Label: Router Alert (1)

    .... .... .... .... .... 000. .... .... = MPLS Experimental Bits: 0

    .... .... .... .... .... ...1 .... .... = MPLS Bottom Of Label Stack: 1

    .... .... .... .... .... .... 0100 0000 = MPLS TTL: 64

PW Ethernet Control Word

    Sequence Number: 0

Ethernet II, Src: Performa_00:00:03 (00:10:94:00:00:03), Dst: Superlan_00:00:01 (00:00:01:00:00:01)

    Destination: Superlan_00:00:01 (00:00:01:00:00:01)

        Address: Superlan_00:00:01 (00:00:01:00:00:01)

        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)

    Source: Performa_00:00:03 (00:10:94:00:00:03)

        Address: Performa_00:00:03 (00:10:94:00:00:03)

        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)

    Type: 802.1Q Virtual LAN (0x8100)

802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 100

    000. .... .... .... = Priority: Best Effort (default) (0)

    ...0 .... .... .... = CFI: Canonical (0)

    .... 0000 0110 0100 = ID: 100

    Type: 802.1Q Virtual LAN (0x8100)

802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 100

    000. .... .... .... = Priority: Best Effort (default) (0)

    ...0 .... .... .... = CFI: Canonical (0)

    .... 0000 0110 0100 = ID: 100

    Type: PPPoE Session (0x8864)

PPP-over-Ethernet Session

    0001 .... = Version: 1

    .... 0001 = Type: 1

    Code: Session Data (0x00)

    Session ID: 0x0001

    Payload Length: 74

Point-to-Point Protocol

    Protocol: Internet Protocol Control Protocol (0x8021)

PPP IP Control Protocol

    Code: Configuration Request (1)

    Identifier: 2 (0x02)

    Length: 10

    Options: (6 bytes), IP address

        IP address: 0.0.0.0

            Type: IP address (3)

            Length: 6

            IP Address: 0.0.0.0

Failing Packet:

Frame 1: 128 bytes on wire (1024 bits), 124 bytes captured (992 bits) on interface 0

    Interface id: 0 (\\.\pipe\view_capture_172-27-5-51_6_89_07182017_154149)

    Encapsulation type: Ethernet (1)

    Arrival Time: Jul 18, 2017 15:41:13.183761000 India Standard Time

    [Time shift for this packet: 0.000000000 seconds]

    Epoch Time: 1500372673.183761000 seconds

    [Time delta from previous captured frame: 0.000000000 seconds]

    [Time delta from previous displayed frame: 0.000000000 seconds]

    [Time since reference or first frame: 0.000000000 seconds]

    Frame Number: 1

    Frame Length: 128 bytes (1024 bits)

    Capture Length: 124 bytes (992 bits)

    [Frame is marked: False]

    [Frame is ignored: False]

    [Protocols in frame: eth:ethertype:mpls:pwethheuristic:pwethcw:eth:ethertype:vlan:ethertype:vlan:ethertype:pppoes:ppp:ipcp]

Ethernet II, Src: Performa_00:00:02 (00:10:94:00:00:02), Dst: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

    Destination: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

        Address: DeltaNet_f9:28:42 (00:30:ab:f9:28:42)

        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)

    Source: Performa_00:00:02 (00:10:94:00:00:02)

        Address: Performa_00:00:02 (00:10:94:00:00:02)

        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)

    Type: MPLS label switched packet (0x8847)

MultiProtocol Label Switching Header, Label: 1 (Router Alert), Exp: 0, S: 1, TTL: 64

    0000 0000 0000 0000 0001 .... .... .... = MPLS Label: Router Alert (1)

    .... .... .... .... .... 000. .... .... = MPLS Experimental Bits: 0

    .... .... .... .... .... ...1 .... .... = MPLS Bottom Of Label Stack: 1

    .... .... .... .... .... .... 0100 0000 = MPLS TTL: 64

PW Ethernet Control Word

    Sequence Number: 0

Ethernet II, Src: Performa_00:00:03 (00:10:94:00:00:03), Dst: Superlan_00:00:01 (00:00:01:00:00:01)

    Destination: Superlan_00:00:01 (00:00:01:00:00:01)

        Address: Superlan_00:00:01 (00:00:01:00:00:01)

        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)

    Source: Performa_00:00:03 (00:10:94:00:00:03)

        Address: Performa_00:00:03 (00:10:94:00:00:03)

        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)

        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)

    Type: 802.1Q Virtual LAN (0x8100)

802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 100

    000. .... .... .... = Priority: Best Effort (default) (0)

    ...0 .... .... .... = CFI: Canonical (0)

    .... 0000 0110 0100 = ID: 100

    Type: 802.1Q Virtual LAN (0x8100)

802.1Q Virtual LAN, PRI: 0, CFI: 0, ID: 100

    000. .... .... .... = Priority: Best Effort (default) (0)

    ...0 .... .... .... = CFI: Canonical (0)

    .... 0000 0110 0100 = ID: 100

    Type: PPPoE Session (0x8864)

PPP-over-Ethernet Session

    0001 .... = Version: 1

    .... 0001 = Type: 1

    Code: Session Data (0x00)

    Session ID: 0x0001

    Payload Length: 74

Point-to-Point Protocol

    Protocol: Internet Protocol Control Protocol (0x8021)

PPP IP Control Protocol

    Code: Configuration Request (1)

    Identifier: 2 (0x02)

    Length: 10

    Options: (6 bytes), IP address

        IP address: 20.6.0.23

            Type: IP address (3)

            Length: 6

            IP Address: 20.6.0.23

Regards,

Sadashivan

I was trying to install an intel pro/1000 pt dual-port card into a Ubuntu linux server computer and ran into the "NVM Checksum is Invalid" message.  I tried to run the bootutil utility on the card, but now only ports 1 & 2 show and the mac addresses are gone.  Is this card salvageable or is it bricked?  I ordered another single-port card, but does anyone know the proper way to handle this issue?

Brian

i'm in project with i350 develop.

is it possible that accsess empty eeprom through pcie?

i wondering that factory default I350 can recognize pcie link? with empty eeprom?

Dear Intel Ethernet Driver Experts,

The following is the good news.

In a nutshell, in the field, there was a challenge with MTU and it was blocking progress.

This is with respect to X710 and i40e driver.

Doing ethtool -r interface cleared the MTU block.

Wanted to learn in X710 i40e driver the hooks that we, Intel provided for ethtool -r.

Contact for Driver Expert will helpful.

Who is the expert contact please?

Much appreciated.

Dear all,

I have a Intel Nic 10 Gb X540-T2 on a Dell R610 with Windows 2012 R2.

It seams that it does not work well, I downloaded the latest drivers (22.4.0.1 - Date 16/06/2017) from Intel website but from Windows Device Manager I see another driver version and date.

In attachment the screenshot shows.

Why? How can I resolve this?

Thanks in advance

Mario

Dear all,

the Intel PRO 1000 CT Desktop Adapter (EXPI9301CT ) is supporting WOL.

But it does not work when you try to use it in a Windows 10 machine.

I think the reason is the Driver. Because Intel does not provide a Driver for Windows 10.

The inbox Driver is used instead.

The Intel Driver has it's own tab for the powermanagement, where the WOL Options can be set.

The Windows inbox Driver only has the Default Windows Settings.

Has anybody an idea how to use WOL with the PRO 1000 CT Adapter?

Thanks.