Hi

How about Windows 2012?

thanks

Our proprietary motherboards have two i210-AT NIC's.  Our vendor currently supplies the boards with both NIC NVRAM's loaded with firmware version 3.16. 

We are trying to update the NIC's to firmware version 3.25 in our production process using Windows PE, but have encountered a strange intermittent problem.

The EEUPDATE command ("EEUPDATEW64e.exe  /All /D I210_Ver.3.25_20171012.bin") appears to be successful, per this output:

EEUPDATE v5.30.22.00

Copyright (C) 1995 - 2017 Intel Corporation

Intel (R) Confidential and not for general distribution.

NIC Bus Dev Fun Vendor-Device  Branding string

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

  1   1  00  00   8086-1533    Intel(R) I210 Gigabit Network Connection

  2   2  00  00   8086-1533    Intel(R) I210 Gigabit Network Connection

1: EEPROM Image Version: 3.25

2: EEPROM Image Version: 3.25

After cycling power to the board, we can confirm the NIC firmware version displayed in our BIOS settings.  Usually, we will see 3.25 for both NIC's, as expected. 

However on some units, the 2nd NIC will still report version 3.16 in the BIOS settings.  (As I understand, the BIOS code is reading the firmware version via an offset to PCI BAR1 address.)  In this case, the EEUPDATE tool does report firmware version 3.25 is installed.  It is not clear which is correct, EEUPDATE or the BIOS.

We can usually repair this problem when it happens by simply rerunning the same EEUPDATE command as above.  But this should not be necessary.

Any idea how we are getting this contradictory result, and what to do about it?

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?

I work in IT at a corporation where almost all of our current computers have the Intel Ethernet Connection l218-LM network adapters. I have seen 5 computers in the last 2 months come up with the error where this network suddenly stops working and produces Error Code 10: this device cannot start. I have searched high and low for a solution, and the ULP enable/disable utility is the only thing I haven't tried yet. Can someone please send the utility to me?

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

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 DPDK (16.04) and also 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  <<<<<<<<<<<<


Thanks,
Ananda

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

Hi,

I have a XL710QDA2 40GB NIC and I also have the INTEL Ethernet QSFP+ cable. I have two problems:

1- This NIC does not get IPV4 address automatically. What should I do to force it to get IPV4 address upon boot?

2- I have tried to send packets through this NIC to other devices, but it can not forward any packet (IPV4, IPV6, or even broadcast packets). How can I enable the packet forwarding and receiving of this NIC?

Thanks for your time. I would appreciate it if you could help me out.

Best,

Marjan

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

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

Hello,

We are having an issue with updating the firmware of our X710 network cards, here is the output of the nvmupdaten64e command:

Num Description                               Ver. DevId S:B    Status

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

01) Intel(R) Ethernet 10G 4P X710 SFP+ rNDC   6.00  1572 00:001 Update not available

02) Intel(R) Gigabit 4P I350-t Adapter       1.103  1521 00:129 Update not available

We are running 9 hosts with ESXi 6.5U1 7388607

Please advise.

Version 22.9 not installing (or not being flagged as installed ?)

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.

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

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

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

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!

Good morning!

I have a problem with the 82579LM card.

Let me start with a description of the situation, we have been producing mining machines for the explosion-risk zone for years. We have been using an Ethernet connection of a PLC with a PC for about 10 years. The connection is 4-core 10Mb. Between the PC and the PLC, ethernet separators (EI-0D2-10Y-10B from pepperl-fuchs) are used. These barriers are "transparent".

For many years, this configuration works with an industrial PC of B & R APC620, which has an Intel PRO / 100 VE card. Currently, its production has ended, therefore I am installing a newer APC910 model. This model has an INTEL 82579LM network card.

Unfortunately, I can not configure it to work in this configuration.

If I omit the Ethernet separators, the connection works.

If I apply the switch between the PC and the barrier, the connection works.

If I install a USB Ethernet card to the computer, the connection works.

If I put an older type of computer in place of the new one, it also works.

If I connect the computer in accordance with the diagram in place of the old one, the system detects the network, however with a mistake.

The system is Windows 7 Standard Embedded.

The most up-to-date Bios, the most up-to-date drivers.

Please help

Regards

Lukasz

Hello all,

I am not able to setup Flow Director to filter flow type ipv4. It did not seems to have this issue when flow type is specified as tcp.

Its on Linux(4.9.27), freshly download driver off kernel. Below there is output of the driver version, firmware and the ntuple filter  I want to apply on.

No error shown anywhere.

Thank you!

ethtool -i i40e1

driver: i40e

version: 2.0.23

firmware-version: 5.05 0x80002927 1.1313.0

expansion-rom-version:

bus-info: 0000:05:00.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

ethtool -k i40e1

Features for i40e1:

rx-checksumming: off

tx-checksumming: off

        tx-checksum-ipv4: off

        tx-checksum-ip-generic: off [fixed]

        tx-checksum-ipv6: off

        tx-checksum-fcoe-crc: off [fixed]

        tx-checksum-sctp: off

scatter-gather: on

        tx-scatter-gather: on

        tx-scatter-gather-fraglist: off [fixed]

tcp-segmentation-offload: off

        tx-tcp-segmentation: off

        tx-tcp-ecn-segmentation: off

        tx-tcp-mangleid-segmentation: off

        tx-tcp6-segmentation: off

udp-fragmentation-offload: off [fixed]

generic-segmentation-offload: off

generic-receive-offload: off

large-receive-offload: off [fixed]

rx-vlan-offload: on

tx-vlan-offload: on

ntuple-filters: on

receive-hashing: on

highdma: on

rx-vlan-filter: on [fixed]

vlan-challenged: off [fixed]

tx-lockless: off [fixed]

netns-local: off [fixed]

tx-gso-robust: off [fixed]

tx-fcoe-segmentation: off [fixed]

tx-gre-segmentation: on

tx-gre-csum-segmentation: off [fixed]

tx-ipxip4-segmentation: on

tx-ipxip6-segmentation: off [fixed]

tx-udp_tnl-segmentation: on

tx-udp_tnl-csum-segmentation: off [fixed]

tx-gso-partial: off [fixed]

tx-sctp-segmentation: off [fixed]

fcoe-mtu: off [fixed]

tx-nocache-copy: off

loopback: off [fixed]

rx-fcs: off [fixed]

rx-all: off [fixed]

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

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

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

l2-fwd-offload: off [fixed]

busy-poll: off [fixed]

hw-tc-offload: off [fixed]

i40e version:        2.0.23

#ethtool -U i40e1 flow-type ip4 action -1 loc 1