Hello experts,

We are currently testing SR-IOV, and one of our concern is:

Are the randomly generated MAC Addresses after each reboot unique from one PF to another PF (and i mean world wide)?

I assume that on the same PF all the VFs have a different MAC Address, but if we have many SR-IOV ready NICs, aren't at risk to have a duplicate mac address in the network? Or there is a smart algorithm that generates the VF mac addresses based on the PF Mac address?

We are also looking into the forcing of MAC Addresses, but we would like to avoid that solution, it doesn't seem stable in our environement, the dom0 detects MAC Address spoofing even though I've followed the procedure of rebooting the VM (reloading the vf driver). If i pursue this route, i read on an Intel doc that IPROUTE2 and a kernel 2.6.39+ were required, but on another documentation from intel: http://www.intel.com/content/dam/www/public/us/en/documents/technology-briefs/ethernet-x520-sr-iov-red-hat-tech-brief.pdf

they don't mention iproute2 (just iproute) and not limit on the kernel version...

Thanks in advance for your insights!

Raymond

Hi.

Is it possible to change mac address on virtual NICs associated with VLANs created under Windows 10 using last Intel drivers for i210?

I cant find the way to do it.

Thanks.

Hello, I am using following Ethernet controller on one of our systems, and once in a while I run into following error after bootup, resulting in the port not sending/receiving packets. 

2016-12-13T01:06:55.499000+00:00 kernel: i40e 0000:20:00.3: eeprom check failed (-2), Tx/Rx traffic disabled

Following is the current version we use (which is quite old; we are in process of upgrading).  But does anyone know if this is a known issue and may be fixed in an upgraded driver and/or NVM?

System# lspci -s 0000:20:00.3

20:00.3 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GBASE-T (rev 01)

System# ethtool -i eth1

driver: i40e

version: 1.3.47

firmware-version: 4.43 0x80001c3f 1.1018.0

bus-info: 0000:20:00.3

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

System#

Thank you very much!

We are working on a Network Switch and we have I210 as a management OOB port.

We need to INVM program for this we need the source code for eepromARMtool.

The Card is recognize as a PCI 01:00.0 Class 0200: 8086:1531 we need to initialize this NIC with 157b DEVID.

Can you please help with the source code for eepromARMtool?

Regards,

Marian.

Upon reading your documentation for the XL710 and the driver and the Linux Kernel ( ) , it appears that HW Timestamping exists for the XL710 on transmit.  Specifically , Intel's driver uses it to implement PTP protocol in the driver file i40e_ptp.c for the Linux i40e driver.  My question is a follow up to anther poster's question ( Suresh ) in conjunction with explaining some of the uncertainties about the driver spec and the Linux kernel spec:  if one specifies the socket option SOF_TIMESTAMPING_TX_HARDWARE  ( with SO_TIMESTAMP also specified ) how is timestamp  included when "the packet is provided to the Network adapter" as defined in https://www.kernel.org/doc/Documentation/networking/timestamping.txt  ?

My question pertains to this timestamping functionality, which according to linuxptp.sourceforge.net,  is considered to be applied at the MAC level and not the PHY. Can you let me know what that means ?  Are these timestamps always incrementing for packets as they are sent out over the wire or is there the potential that these timestamps will not be "strictly increasing" for consecutive packets sent out by the XL710 NIC ? 

I am working on a project that doesn't care about the packets received, only that we know the ordering of the packets sent out.  If we know that two consecutive packets arriving at MAC layer will always have the first packet leaving and timestamped with a lower timestamp than it's successor, then we are happy.  Is this the case ? I wasn't sure i there is some reordering that my occur in the NIC between the MAC layer and Phy submission.

Thank you for your feedback,

-Jimi

I have use SR-IOV in my proxmox, and I was passthrough 2 virtual Function NIC card to my vm-pfsense

[code]

root@pve:~# lspci |grep Eth|grep I350

07:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)

07:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)

08:10.0 Ethernet controller: Intel Corporation I350 Ethernet Controller Virtual Function (rev 01)

08:10.1 Ethernet controller: Intel Corporation I350 Ethernet Controller Virtual Function (rev 01)

08:10.4 Ethernet controller: Intel Corporation I350 Ethernet Controller Virtual Function (rev 01)

08:10.5 Ethernet controller: Intel Corporation I350 Ethernet Controller Virtual Function (rev 01)

08:11.1 Ethernet controller: Intel Corporation I350 Ethernet Controller Virtual Function (rev 01)

[/code]

But one of ethernet port have to tag 2 vlan id

[code]

root@pve:~# ip link show eth11

6: eth11: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000

    link/ether 0c:c4:7a:c3:9f:07 brd ff:ff:ff:ff:ff:ff

    vf 0 MAC 7e:ba:b6:b5:ec:13, spoof checking on, link-state auto

    vf 1 MAC 7e:ba:b6:b5:ec:14, spoof checking on, link-state auto

    vf 2 MAC 7e:ba:b6:b5:ec:15, vlan 300, spoof checking on, link-state auto

[/code]

I was use Trunk port in DGS-1510 switch, and I can see 7e:ba:b6:b5:ec:15 this mac tag vlan id 300 on switch web gui.

Any in pfsense, I can see 7e:ba:b6:b5:ec:15 this interface status was up. so I set static ip 192.168.55.1 on this interface.

But DGS-1510 and pfsense cannot ping each other.

How can I solve this error?

Got Supoermicro server from supplier  with X710-DA2 Card

I'm install FreeBSD 11, update to stable and have next messages:

ixl0: <Intel(R) Ethernet Connection XL710/X722 Driver, Version - 1.6.6-k> mem 0xf8000000-0xf8ffffff,0xf9008000-0xf900ffff irq 32 at device 0.0 on pci3

ixl0: Using MSIX interrupts with 9 vectors

ixl0: fw 4.33.31377 api 1.2 nvm 4.41 etid 80001866 oem 16.4096.10

ixl0: The driver for the device detected an older version of the NVM image than expected.

So I try update NVM under FreeBSD:

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.26.17.11

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 [Segmentation fault (core dumped)

Then I try update NVM under Ubuntu, download and install driver

# ethtool -i enp2s0f0

driver: i40e

version: 1.5.25

firmware-version: 4.41 0x80001866 16.5.10

expansion-rom-version:

bus-info: 0000:02:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

 

# lspci |grep 710

02:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)

02:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 01)

 

and got

XL710/Linux_x64# ./nvmupdate64e

 

Intel(R) Ethernet NVM Update Tool

NVMUpdate version 1.26.17.11

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                            Device-Id B:D   Adapter Status

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

01) Intel(R) Ethernet Converged Network Ad 8086-1572 02:00 Update not available

02) Intel(R) I350 Gigabit Network Connecti 8086-1521 05:00 Update not available

 

 

Tool execution completed with the following status: Device not found

Press any key to exit.

lspci -v with serial number attached

Tried uninstalling and reinstalling from Intel site for this device but nothing seems to correct the code 10 error.

I have I.7 90 @ 2.67 GHZ  HP

Any suggestions appreciated.

#first server

root@sdb-1 ~]# fcoeadm -i p6p2.1002-fcoe

    Description:      82599ES 10-Gigabit SFI/SFP+ Network Connection

    Revision:         01

    Manufacturer:     Intel Corporation

    Serial Number:    90E2BA26EE3E

    Driver:           ixgbe 3.21.2

    Number of Ports:  1

        Symbolic Name:     fcoe v0.1 over p6p2.1002-fcoe

        OS Device Name:    host11

        Node Name:         0x1000001B2194DC83

        Port Name:         0x2000001B2194DC83

        FabricName:        0x100050EB1AF120AC

        Speed:             10 Gbit

        Supported Speed:   1 Gbit, 10 Gbit

        MaxFrameSize:      2048

        FC-ID (Port ID):   0x050000

        State:             Online

#second server

[root@dct1 ~]# fcoeadm -i p6p2.1002-fcoe

    Description:      82599ES 10-Gigabit SFI/SFP+ Network Connection

    Revision:         01

    Manufacturer:     Intel Corporation

    Serial Number:    90E2BA0DE616

    Driver:           ixgbe 3.21.2

    Number of Ports:  1

        Symbolic Name:     fcoe v0.1 over p6p2.1002-fcoe

        OS Device Name:    host11

        Node Name:         0x1000001B2194DC83

        Port Name:         0x2000001B2194DC83

        FabricName:        0x0000000000000000

        Speed:             10 Gbit

        Supported Speed:   1 Gbit, 10 Gbit

        MaxFrameSize:      2048

        FC-ID (Port ID):   0x000000

        State:             Linkdown

When I install the driver ver 21.1 Download Intel® Network Adapter Driver for Windows® 10  I get a message

"Important Note:  Creating Intel® ANS teams and VLANs on Microsoft Windows® 10 is currently not supported.  As a result, when created, teams and VLANs do not pass traffic.  We expect that ANS will be supported on Microsoft Windows 10 client in a future release"

I dont need teaming etc...but once the driver is installed, I dont see WOL in the ADVANCED option  ???

Where is the WOL feature???

Thanks,

Hello,

after the update to Windows 10 (x64, Build 10240) the creation of a teaming group (static or IEEE802.3ad) with a I211+I217-V NIC fails.

Drivers have been upgraded to the latest version available and multiple reinstallations with reboots din't help either. Whenever the group creation wizzard is used and a groupname (several tried), the adapters and LACP have been selected, a Windows pop-up appears to tell me group creation has failed.

However the Windows Device Manager shows a newly created "Intel Advanced Network Services Virtual Adapter", so some kind of configuration seems to get done.

Using Windows 7 SP1 x64 the exact same setup worked flawlessly for months, so Win10/the driver are the likely culprit.

Is anyone experiencing similar problems and/or is this a known bug? Feedback on this issue is greatly appreciated.

Thanks in advance!

Kind regards,

Famaku

@Having a problem with Intel Driver Update Utility giving me repeatedly the same driver version like "Intel Network Adapter Driver V 12.15.23.7" than I install it after when ready I restart my PC. When I see the Windows screen and I repeat to open application again with Intel Update Driver Utility it will give me again the same driver version "Intel Network Adapter Driver V 12.15.23.7" and again I will repeat and hangs again in the Utility!

I followed the log file directory and send you a screenshot report of it so maybe it will help you!

On the download page it is clearly presented a download link for Intel(R) Ethernet Connection (2) I219-V...

The issue(s) are:

1. SSU.exe does not detect the HW too but presented at the device manager as a missing HW & driver

2. Installed a fresh MS Server 2012 with equal issue!

3. Installed Win 10 Pro and using the installer it shows the net1ic64.inf with 12.15.23.7 version

4. on same path are drivers for Win64/ NDIS62...NDIS65 meaning drivers for the WIn7....Win10

While using a brand new main-board with B150N chipset

Any help is welcome

Hp

Is there any possibility to get an 540-T2 running on Windows 10 1607?

After Driverinstallation i got an Code 10, Driver could not be startet Error.

Thanks for any Help.

I have two NICs that are suppose to be the same part number, however, one is recognized as a dual port server adapter, while the other is recognized as a dual port network connector. Can anyone tell me why?

Thanks,

Johnathon

I have downloaded Intel NIC driver for “Intel(R) Gigabit 4P
I350-t rNDC“ NIC adapter for Windows 10 OS from below link

https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapters-Connections-CD?product=59679

Below are the steps I performed for driver installation

1. Extracted 21_1_cd.zip
   file to C drive on the target system.
2. Open
   command prompt in administrative mode.
3. Go to C:\21_1_cd\APPS\PROSETDX\Winx64
   path. (21_1_cd is the extracted folder name in C drive)
4. Execute
   below command to install the driver
   1. Start /w DxSetup.exe /qn /norestart

The driver does not get installed including proset software. If I
don’t pass /norestart, the driver and proset gets installed but it reboot
automatically.

I want to know how to install the driver and proset without
auto-rebooting. I will take care of rebooting the system immediately after the
driver is installed.

HI!

I have the adapter X710  DA2 and X710  DA4, using LR SFP+ Module (Intel DUAL RATE 1G/10G SFP+ LR (bailed) FTLX1471D3BCV-IT),

does not UP ethernet link in mode 1G between devices.

Also can notdump the settingsto the EEPROMof the SFP module in response to receiving

Cannot get module EEPROM information: Operation not supported

When you try to off auto-negotiationor changespeedto1000 alsohave

Cannot get current device settings: No such device

  not setting speed

  not setting duplex

  not setting autoneg

below information about

driver information:

driver: i40e

version: 1.5.16

firmware-version: 4.42 0x80001921 0.0.0

bus-info: 0000:0a:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

interface status :

p2p1      Link encap:Ethernet  HWaddr 3c:fd:fe:9d:40:38

          inet addr:xxx.xxx.xxx.xxx  Bcast:xxx.xxx.xxx.xxx  Mask:255.255.255.0

          inet6 addr: fe80::3efd:feff:fe9d:4038/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:4358 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:728252 (728.2 KB)

Settings for p2p1:

        Supported ports: [ FIBRE ]

        Supported link modes:   1000baseT/Full

                                10000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: No

        Advertised link modes:  10000baseT/Full

        Advertised pause frame use: No

        Advertised auto-negotiation: No

        Speed: 10000Mb/s

        Duplex: Full

        Port: FIBRE

        PHYAD: 0

        Transceiver: external

        Auto-negotiation: off

        Supports Wake-on: d

        Wake-on: d

        Current message level: 0x0000000f (15)

                              drv probe link timer

        Link detected: yes

Is it possible the work of these SFP+ when using the adapter X710 DA2 in 1GB mode?

If so,why do I havetheseconflictswith modules?

Hi!

Neededhelp!

I have the adapter X710DA4 and  X710DA2, and using LR SFP Modules Intel DUAL RATE 1G/10G SFP+ LR (bailed) FTLX1471D3BCV-IT.

There is a problem for inclusion in Juniper switch, link is down 1GB mode between devices.

Try to off auto-negotiation or/and change speed to 1000 get:

@ubuntu:~$ sudo ethtool -s p2p1 autoneg off speed 1000 duplex full

Cannot get current device settings: No such device

  not setting speed

  not setting duplex

  not setting autoneg

@ubuntu:~$ sudo ethtool -i p2p1

driver information:

driver: i40e

version: 1.5.16

firmware-version: 4.42 0x80001921 0.0.0

bus-info: 0000:0a:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

It is in the caseof a loopbetween the interfaceson the X710:

@ubuntu:~$ sudo ethtool p2p1

        Supported ports: [ FIBRE ]

        Supported link modes:   1000baseT/Full

                                            10000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: No

        Advertised link modes:  10000baseT/Full

        Advertised pause frame use: No

        Advertised auto-negotiation: No

        Speed: 10000Mb/s

        Duplex: Full

        Port: FIBRE

        PHYAD: 0

        Transceiver: external

        Auto-negotiation: off

        Supports Wake-on: d

        Wake-on: d

        Current message level: 0x0000000f (15)

                               drv probe link timer

        Link detected: yes

Need a solution what to do to make the link between the X710 and Juniper stood up to the work, if possible.

hi, i would like to report that the new intel nic drivers version 19.3 that just released recently has huge 6000+ dpc latency spike once in a few secs.

my specs

Intel(R) 82579LM Gigabit Network Connection

windows 7 SP1 32bit + lastest windows update

i downgrade to intel nic drivers previous version 19.1 and the problem is just gone.

Same issue - we are connecting to a 1000Base-LX device with an Intel XL710 and a E10GLR optic.

We are using the latest driver and the latest NVM. Machine is a Dell R330 with firmware supplied by Dell.

configuration: autonegotiation=off broadcast=yes driver=i40e driverversion=1.5.25 duplex=full firmware=5.04 0x800024c9 17.5.11 latency=0 link=yes multicast=yes port=fibre speed=10Gbit/s

Oddly, if the remote side is a X520-DA2 with a E10GLR optics, and a force that side to 1G, I get link and can ping. However, no 3rd party 1000Base-LX devices get link.

We are also deeply disappointed that DOM (ethtool -m) support has not been written into the i40e driver.

Please advise.