Hi Intel,

I'd like to get the ULP tool.

Best Regards,

naok

Hi Everyone, Im trying to track down an issue with my LAN port,,My motherboard uses a Intel i219V controller and this is a new htpc mini itx build.

So far Ive looked over a few things such as downloading the latest drivers for the chipset and updating the bios on the asus board,,from the very first post

I have been skeptical of a hardware issue due to a lack of any port activity via the normal lights one expects to see from the ethernet port, in my limited experience

I usually see a light in or near the port no matter if it is active or not, this boards port has been silent of any lights so far,,however I thought i might run this by the

community here just in case someone else might have encountered a lan issue with this controller or a problem with Asus ROG products in respect to the network

controller, i am open to suggestions and have a fair amount experience with PC hardware and sometimes do repairs for friends and family.

any troubleshooting suggestions ? I hope maybe I would be so lucky as to have missed an option in the bios setup, but I havent looked into that yet,

Wireless on the asus board appears to work well and uses a qualcomm Atheros Dual band adapter and antenna. So far it performs well in any part of my home

but I prefer old school wired networking if at all possible,

This was motherboard number 2 as the first board came with some bent pins and had signs of being an open box,,this board however came packaged sealed and everything

checked out ok, first post went well after breadboarding it just to confirm it wasnt DOA,,anyone who has built into a small form factor case knows how much trouble this can save you.

So is the i219v have any current issues that might cause a ethernet port to appear dead ?

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.

Hi,

* In summary:

When I run iperf3 between 2 machines throgh SRIO VFs interface and I got the following error in dmesg:

TX driver issue detected, PF reset issued

* How to setup and detail results

+ I got 2 machines each with 1 X710 4ports 10G cards.  These 2 X710 cards has direct cable connect between them.

+ On machine 1, I run the following commands to create VF0 and setup its IP. VF0 has pci address of 0000:04:0a.0

    $ echo 1 > /sys/bus/pci/devices/0000\:04\:00.2/sriov_numvfs

    $ ifconfig enp4s0f2 mtu 9700

    $ ifconfig enp4s10 1.1.1.1 netmask 255.255.255.0 mtu 9216

  $ echo 'msg_enable 0xffff' > /sys/kernel/debug/i40e/0000\:04\:00.2/command

+ On machine 2, I run the following commands to create VF0 and setup its IP. VF0 has pci address of 0000:04:0a.0

    $ echo 1 > /sys/bus/pci/devices/0000\:04\:00.2/sriov_numvfs

    $ ifconfig enp4s0f2 mtu 9700

    $ ifconfig enp4s10 1.1.1.2 netmask 255.255.255.0 mtu 9216

+ I was able to ping 1.1.1.2 from machine 1 and ping 1.1.1.1 from machine 2

+ On machine 2, start iperf3 server:

   $ iperf3 -s -p 8000

+ On machine 1, start iperf3 client:

   $ iperf3 -c 1.1.1.12 -p 8000 -l 64 -p 4

   $ dmesg

[ 5895.270158] i40e 0000:04:00.2: Malicious Driver Detection event 0x00 on TX queue 68 PF number 0x02 VF number 0x40

[ 5895.270166] i40e 0000:04:00.2: TX driver issue detected, PF reset issued

[ 5895.270170] i40e 0000:04:00.2: TX driver issue detected on VF 0

[ 5895.270173] i40e 0000:04:00.2: Too many MDD events on VF 0, disabled

[ 5895.270176] i40e 0000:04:00.2: Use PF Control I/F to re-enable the VF

[ 5895.284494] i40evf 0000:04:0a.0: PF reset warning received

[ 5895.284500] i40evf 0000:04:0a.0: Scheduling reset task

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

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

[ 5895.612086] i40e 0000:04:00.2: Malicious Driver Detection event 0x00 on TX queue 67 PF number 0x02 VF number 0x40

[ 5895.612096] i40e 0000:04:00.2: Too many MDD events on VF 0, disabled

[ 5895.612098] i40e 0000:04:00.2: Use PF Control I/F to re-enable the VF

[ 5895.640978] i40e 0000:04:00.2: Invalid message from VF 0, opcode 3, len 4

* X710 card ports info

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)

* This is driver info of PF X710:

driver: i40e

version: 1.4.25-k

firmware-version: 5.04 0x80002549 0.0.0

expansion-rom-version:

bus-info: 0000:04:00.2

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

* This is the PF X710 card info:

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

  Subsystem: Intel Corporation Ethernet Converged Network Adapter X710

  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+

  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

  Latency: 0, Cache Line Size: 256 bytes

  Interrupt: pin A routed to IRQ 35

  Region 0: Memory at dc800000 (64-bit, prefetchable) [size=8M]

  Region 3: Memory at dc7f8000 (64-bit, prefetchable) [size=32K]

  Expansion ROM at df380000 [disabled] [size=512K]

  Capabilities: [40] Power Management version 3

  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)

  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-

  Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+

  Address: 0000000000000000  Data: 0000

  Masking: 00000000  Pending: 00000000

  Capabilities: [70] MSI-X: Enable+ Count=129 Masked-

  Vector table: BAR=3 offset=00000000

  PBA: BAR=3 offset=00001000

  Capabilities: [a0] Express (v2) Endpoint, MSI 00

  DevCap: MaxPayload 2048 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us

  ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+

  DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+

  RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop- FLReset-

  MaxPayload 128 bytes, MaxReadReq 512 bytes

  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-

  LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L1, Exit Latency L0s <2us, L1 <16us

  ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+

  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

  LnkSta: Speed 5GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

  DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported

  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled

  LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-

  EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-

  Capabilities: [e0] Vital Product Data

  Product Name: XL710 40GbE Controller

  Read-only fields:

  [PN] Part number:

  [EC] Engineering changes:

  [FG] Unknown:

  [LC] Unknown:

  [MN] Manufacture ID:

  [PG] Unknown:

  [SN] Serial number:

  [V0] Vendor specific:

  [RV] Reserved: checksum good, 0 byte(s) reserved

  Read/write fields:

  [V1] Vendor specific:

  End

  Capabilities: [100 v2] Advanced Error Reporting

  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-

  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-

  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+

  CEMsk: RxErr+ BadTLP+ BadDLLP+ Rollover+ Timeout+ NonFatalErr+

  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-

  Capabilities: [140 v1] Device Serial Number 90-9c-a4-ff-ff-fe-fd-3c

  Capabilities: [150 v1] Alternative Routing-ID Interpretation (ARI)

  ARICap: MFVC- ACS-, Next Function: 3

  ARICtl: MFVC- ACS-, Function Group: 0

  Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV)

  IOVCap: Migration-, Interrupt Message Number: 000

  IOVCtl: Enable+ Migration- Interrupt- MSE+ ARIHierarchy-

  IOVSta: Migration-

  Initial VFs: 32, Total VFs: 32, Number of VFs: 1, Function Dependency Link: 02

  VF offset: 78, stride: 1, Device ID: 154c

  Supported Page Size: 00000553, System Page Size: 00000001

  Region 0: Memory at 00000000dc400000 (64-bit, prefetchable)

  Region 3: Memory at 00000000dc380000 (64-bit, prefetchable)

  VF Migration: offset: 00000000, BIR: 0

  Capabilities: [1a0 v1] Transaction Processing Hints

  Device specific mode supported

  No steering table available

  Capabilities: [1b0 v1] Access Control Services

  ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  Kernel driver in use: i40e

  Kernel modules: i40e

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

  Subsystem: Intel Corporation Ethernet Converged Network Adapter X710

  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+

  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

  Latency: 0, Cache Line Size: 256 bytes

  Interrupt: pin A routed to IRQ 35

  Region 0: Memory at dc800000 (64-bit, prefetchable) [size=8M]

  Region 3: Memory at dc7f8000 (64-bit, prefetchable) [size=32K]

  Expansion ROM at df380000 [disabled] [size=512K]

  Capabilities: [40] Power Management version 3

  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)

  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-

  Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+

  Address: 0000000000000000  Data: 0000

  Masking: 00000000  Pending: 00000000

  Capabilities: [70] MSI-X: Enable+ Count=129 Masked-

  Vector table: BAR=3 offset=00000000

  PBA: BAR=3 offset=00001000

  Capabilities: [a0] Express (v2) Endpoint, MSI 00

  DevCap: MaxPayload 2048 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us

  ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+

  DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+

  RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop- FLReset-

  MaxPayload 128 bytes, MaxReadReq 512 bytes

  DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-

  LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L1, Exit Latency L0s <2us, L1 <16us

  ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+

  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+

  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

  LnkSta: Speed 5GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

  DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported

  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled

  LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-

  EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-

  Capabilities: [e0] Vital Product Data

  Product Name: XL710 40GbE Controller

  Read-only fields:

  [PN] Part number:

  [EC] Engineering changes:

  [FG] Unknown:

  [LC] Unknown:

  [MN] Manufacture ID:

  [PG] Unknown:

  [SN] Serial number:

  [V0] Vendor specific:

  [RV] Reserved: checksum good, 0 byte(s) reserved

  Read/write fields:

  [V1] Vendor specific:

  End

  Capabilities: [100 v2] Advanced Error Reporting

  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq+ ACSViol-

  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-

  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+

  CEMsk: RxErr+ BadTLP+ BadDLLP+ Rollover+ Timeout+ NonFatalErr+

  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-

  Capabilities: [140 v1] Device Serial Number 90-9c-a4-ff-ff-fe-fd-3c

  Capabilities: [150 v1] Alternative Routing-ID Interpretation (ARI)

  ARICap: MFVC- ACS-, Next Function: 3

  ARICtl: MFVC- ACS-, Function Group: 0

  Capabilities: [160 v1] Single Root I/O Virtualization (SR-IOV)

  IOVCap: Migration-, Interrupt Message Number: 000

  IOVCtl: Enable+ Migration- Interrupt- MSE+ ARIHierarchy-

  IOVSta: Migration-

  Initial VFs: 32, Total VFs: 32, Number of VFs: 1, Function Dependency Link: 02

  VF offset: 78, stride: 1, Device ID: 154c

  Supported Page Size: 00000553, System Page Size: 00000001

  Region 0: Memory at 00000000dc400000 (64-bit, prefetchable)

  Region 3: Memory at 00000000dc380000 (64-bit, prefetchable)

  VF Migration: offset: 00000000, BIR: 0

  Capabilities: [1a0 v1] Transaction Processing Hints

  Device specific mode supported

  No steering table available

  Capabilities: [1b0 v1] Access Control Services

  ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  Kernel driver in use: i40e

  Kernel modules: i40e

* This is the VF X710 card info:

04:0a.0 Ethernet controller: Intel Corporation XL710/X710 Virtual Function (rev 01)

  Subsystem: Intel Corporation XL710/X710 Virtual Function

  Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-

  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-

  Latency: 0

  Region 0: [virtual] Memory at dc400000 (64-bit, prefetchable) [size=64K]

  Region 3: [virtual] Memory at dc380000 (64-bit, prefetchable) [size=16K]

  Capabilities: [70] MSI-X: Enable+ Count=5 Masked-

  Vector table: BAR=3 offset=00000000

  PBA: BAR=3 offset=00002000

  Capabilities: [a0] Express (v2) Endpoint, MSI 00

  DevCap: MaxPayload 2048 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us

  ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset+

  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-

  RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-

  MaxPayload 128 bytes, MaxReadReq 128 bytes

  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-

  LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM L1, Exit Latency L0s <2us, L1 <16us

  ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+

  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-

  ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-

  LnkSta: Speed unknown, Width x0, TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-

  DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported

  DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled

  LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-

  EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-

  Capabilities: [100 v2] Advanced Error Reporting

  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  UESvrt: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-

  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-

  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-

  AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-

  Capabilities: [150 v1] Alternative Routing-ID Interpretation (ARI)

  ARICap: MFVC- ACS-, Next Function: 0

  ARICtl: MFVC- ACS-, Function Group: 0

  Capabilities: [1a0 v1] Transaction Processing Hints

  Device specific mode supported

  No steering table available

  Capabilities: [1d0 v1] Access Control Services

  ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans-

  Kernel driver in use: i40evf

  Kernel modules: i40evf

* This is driver info of VF X710:

driver: i40evf

version: 1.4.15-k

firmware-version: N/A

expansion-rom-version:

bus-info: 0000:04:0a.0

supports-statistics: yes

supports-test: no

supports-eeprom-access: no

supports-register-dump: no

supports-priv-flags: yes

* OS info:

DISTRIB_ID=Ubuntu

DISTRIB_RELEASE=16.04

DISTRIB_CODENAME=xenial

DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS"

Please let me know if you need more info.

Thanks!

Hi there,

I have 2x the same setup of one X540-T1 network card in a Logic Supply MK100B-50 (ASRock IMB-181-D Motherboard) and in both computers, after a certain amount of usage, the X540-T1 card stops working. When I go in the Windows Device Manager it says "Windows has stopped this device because it has reported problems. (code 43)"

I can disable and re-enable the device to make it work but only temporarly. The problem comes back.

I've also installed the latest intel driver. It says it is version 4.0.215.0 which was installed with the file: IntelNetworkDrivers-PROWinx64.exe.

Should this work?

Any ideas of how to fix this?

Thank you.

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.

Hello,

I am using the newest driver for the Intel I219-LM network adapter in Windows 7. I need to change the size of the receive and
transmit buffers to: 

Receive buffers : 512

Transmit buffers: 128

I can’t seem to find the option to change the parameters !  

For the Intel 82579LM the option is easily available under the “advanced tab” for “network connection properties”.

Any suggestions?

Thanks 

Regards

Jonas

Hi, I have an Acer Aspire X3960 small desktop with Intel 82579V. Ever since upgrading to Windows 10 from Windows 7 I have had problems with dropped connections. I have tried various drivers from Intel and Microsoft, old and new, without any success (currently on driver version 12.15.22.6 from Microsoft from 2016, which seems to be the most stable. Still, the connection is dropping almost every hour. It usually picks up after waiting a few minutes, otherwise I need to go through disabling and enabling the network adapter to get it going again.

Any suggestions?

Hi ,

I was  trying to set up Intel XL710 in 2x40 mode using the QCU but I am getting the error ""QSFP+ Configuration modification is not supported by this adapter."

Although If I try to check the current configuration it shows the mode as N/A.

All the steps that I followed:

[root@ndr730l:/tmp/EFIx64] ./qcu64e /devices

Intel(R) QSFP+ Configuration Utility

QCU version: v2.27.10.01

Copyright(C) 2016 by Intel Corporation.

Software released under Intel Proprietary License.

NIC Seg:Bus Ven-Dev Mode    Adapter Name

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

1) 000:005 8086-1583 N/A Intel(R) Ethernet Converged Network Adapter XL710-

[root@ndr730l:/tmp/EFIx64] ./qcu64e /info /nic=1

Intel(R) QSFP+ Configuration Utility

QCU version: v2.27.10.01

Copyright(C) 2016 by Intel Corporation.

Software released under Intel Proprietary License.

QSFP+ Configuration modification is not supported by this adapter.

MAC Address: 3CFDFE16FE80

Serial Number: XL710QDA2BLK

Firmware details:

ethtool -i vmnic4

driver: i40e

version: 1.4.28

firmware-version: 5.04 0x800024d8 17.5.10

bus-info: 0000:05:00.0

Facing one weird issue on the Intel setup (We have 2 machines having Intel card -both side we have Intel xl710 having 40G speed).We are seeing just 1 Gbps of throughput with netperf,iperf etc using ESXi 6.5

Setup has ESXi 6.5 (latest VMware Tools install with adapter VMXNET3) on both DUT/Partner each having a VM on which we ran Netperf/iPerf.

We have updated latest driver and firmware on Intel.

Additionally we have tried throughput in loopback mode with both Intel interfaces on same machine connected (below) just to make sure that its an Intel adapter issue on a particular machine but it doesn't seem to be the case

VM1---vSwitch1--Intel-1

                                 |

                                 |

VM2---vSwitch2--Intel-1

Intel Driver used: i40e-2.0.6-2494585-5301661

@ https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI60-INTEL-I40E-206&productId=638&download=true&fileId=b21…

esxcli software vib install -d /tmp/i40e-2.0.6-2494585-offline_bundle-5301661.zip

FW: 5.04

Driver and FW are compatible as per the compatibility list @ VMware Compatibility Guide - I/O Device Search

I have configured host with two PF and 16 x2 VF in debian system. It worked well if I use the PF/VF as standalone NIC, but not functional with OVS bridge.

The testing scenario as below:

eth0 (PF): 10.250.11.103/24

eth11 (VF 9): 10.250.11.113/24

   Bridge "vmbr1"

        Port "eth10"

            Interface "eth10" (VF 8)

        Port "vmbr1"

            Interface "vmbr1"

                type: internal

        Port "in1"

            Interface "in1"

                type: internal

    ovs_version: "2.6.0"

in1: 10.250.11.34/24

I try the following icmp test:

ping 10.250.11.254 (reply good)

ping 10.250.11.254 -I eth11 (reply good)

ping 10.250.11.254 -I in1 (NO response)

ip link show my VF as:

-------------------------------

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

    link/ether 0c:c4:7a:df:36:c6 brd ff:ff:ff:ff:ff:ff

    vf 0 MAC 6e:74:9e:65:58:eb, spoof checking on, link-state auto

    vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 2 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 3 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 4 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 5 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 6 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 7 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 8 MAC da:c7:06:0b:5b:1f, spoof checking on, link-state auto

    vf 9 MAC ea:97:12:4e:b4:6b, spoof checking on, link-state auto

    vf 10 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 11 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 12 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 13 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 14 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

    vf 15 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

arp table shown as:

-------------------------------

Address                  HWtype  HWaddress           Flags Mask            Iface

10.250.11.254            ether   6c:3b:6b:e9:7c:e1   C                     eth11

10.250.11.254            ether   6c:3b:6b:e9:7c:e1   C                     eth0

10.250.11.254            ether   6c:3b:6b:e9:7c:e1   C                     in1

But arp is not stable, it disappear very quickly:

------------------------------------------------------------

Address                  HWtype  HWaddress           Flags Mask            Iface

10.250.11.254                   (incomplete)                              in1

10.250.11.254            ether   6c:3b:6b:e9:7c:e1   C                     eth0

10.250.11.254            ether   6c:3b:6b:e9:7c:e1   C                     eth11

The strange thing is:

ping via in1 will not fill up the arp table for in1 Iface (always show incomplete), but ping via other two iface seems fill the mac address into in1 some time.

I have tcpdump to in1 and found it send out ARP request broadcast, but did not get any ARP reply from host 254.

ovs-appctl fdb/show vmbr1:

-----------------------------------------

port  VLAN  MAC                Age

    2     0  72:fc:b4:3a:e6:0f   78

    1     0  6c:3b:6b:e9:7c:e1   38

    1     0  6c:3b:6b:f5:96:e6    3

    1     0  88:43:e1:dd:9c:80    1

This looks persist and will not change whatever I ping via any Iface.

I have also try to change VF port, but seems none of them work with OVS bridge.

But the bridge worked if assigned the port to eth0 or eth1 PF.

uname -a:

Linux pve3 4.4.62-1-pve #1 SMP PVE 4.4.62-88 (Thu, 18 May 2017 09:18:43 +0200) x86_64 GNU/Linux

/etc/network/interfaces:

----------------------------------

auto eth0

iface eth0 inet static

        address  10.250.11.103

        netmask  255.255.255.0

        gateway  10.250.11.254

auto eth11

iface eth11 inet static

        address  10.250.11.113

        netmask  255.255.255.0

allow-vmbr1 eth10

iface eth10 inet manual

        ovs_type OVSPort

        ovs_bridge vmbr1

auto vmbr1

iface vmbr1 inet manual

        ovs_type OVSBridge

        ovs_ports eth10 in1

allow-vmbr1 in1

iface in1 inet static

        address  10.250.11.34

        netmask  255.255.255.0

        ovs_type OVSIntPort

        ovs_bridge vmbr1

Here is ethtool info for eth10:

-------------------------------

# ethtool -i eth10

driver: ixgbevf

version: 2.12.1-k

firmware-version:

bus-info: 0000:05:12.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: no

supports-register-dump: yes

supports-priv-flags: no

#ethtool -k eth10

Features for eth10:

rx-checksumming: on

tx-checksumming: on

        tx-checksum-ipv4: off [fixed]

        tx-checksum-ip-generic: on

        tx-checksum-ipv6: off [fixed]

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

        tx-checksum-sctp: on

scatter-gather: on

        tx-scatter-gather: on

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

tcp-segmentation-offload: on

        tx-tcp-segmentation: on

        tx-tcp-ecn-segmentation: off [fixed]

        tx-tcp6-segmentation: on

udp-fragmentation-offload: off [fixed]

generic-segmentation-offload: on

generic-receive-offload: on

large-receive-offload: off [fixed]

rx-vlan-offload: on [fixed]

tx-vlan-offload: on [fixed]

ntuple-filters: off [fixed]

receive-hashing: off [fixed]

highdma: on [fixed]

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: off [fixed]

tx-ipip-segmentation: off [fixed]

tx-sit-segmentation: off [fixed]

tx-udp_tnl-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: on [fixed]

hw-tc-offload: off [fixed]

-------------------------------

Is there any advice?

When can we expect a revised driver which includes teaming on Windows 10 RS 2?

I'm really confused. I'm getting conflicting answers. I just need to know if NIC teaming works with the latest versions of Windows (1703)

from the driver page for the 1219:

Download Intel® Network Adapter Driver for Windows® 10*

" Intel® ANS is only supported on the Windows 10 Anniversary Update"

However, referencing this page, it looks like it IS working? for some people?

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

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 have X540-T2 adapter on ubuntu 14.04 server and netgear xs708e swich  but at last one time in 24h I have link down messasge in console.

ixgbe 0000:04:00.0: eth0: NIC Link is Down

ixgbe 0000:04:00.0: eth0: NIC Link is Up 10 Gbps, Flow Control: RX/TX

ixgbe 0000:04:00.0: eth1: NIC Link is Down

ixgbe 0000:04:00.0: eth1: NIC Link is Up 10 Gbps, Flow Control: RX/TX

I updated to latest driver and firmware but no luck.

How to fix this problem?

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

I can't replicate the issue but every few weeks my NIC disables itself and I have to restart my computer to get it to work again since disabling / re enabling in Device Manager stalls.

From searching online, "Receive Side Scaling" is the reason.  Why would this be the case?   Would this be due to the manufacturer of the motherboard or Intel?  I tried Asus' drivers and also tried the latest Intel drivers - doesn't matter.

Hi Everyone, Im trying to track down an issue with my LAN port,,My motherboard uses a Intel i219V controller and this is a new htpc mini itx build.

So far Ive looked over a few things such as downloading the latest drivers for the chipset and updating the bios on the asus board,,from the very first post

I have been skeptical of a hardware issue due to a lack of any port activity via the normal lights one expects to see from the ethernet port, in my limited experience

I usually see a light in or near the port no matter if it is active or not, this boards port has been silent of any lights so far,,however I thought i might run this by the

community here just in case someone else might have encountered a lan issue with this controller or a problem with Asus ROG products in respect to the network

controller, i am open to suggestions and have a fair amount experience with PC hardware and sometimes do repairs for friends and family.

any troubleshooting suggestions ? I hope maybe I would be so lucky as to have missed an option in the bios setup, but I havent looked into that yet,

Wireless on the asus board appears to work well and uses a qualcomm Atheros Dual band adapter and antenna. So far it performs well in any part of my home

but I prefer old school wired networking if at all possible,

This was motherboard number 2 as the first board came with some bent pins and had signs of being an open box,,this board however came packaged sealed and everything

checked out ok, first post went well after breadboarding it just to confirm it wasnt DOA,,anyone who has built into a small form factor case knows how much trouble this can save you.

So is the i219v have any current issues that might cause a ethernet port to appear dead ?

Hi Intel,

I would like to read-out the module eeprom of QSFP transceiver connected to a XL710-QDA1 NIC.

The naive approach failed:  ethtool -m eth0. It reports: "Cannot get module EEPROM information: Operation not supported"

Is this feature supported by the NIC and the Intel driver i40e?

I am using the following driver and firmware:

driver version: 2.0.23

firmware-version: 5.05 0x800028a2 1.1568.0

Thanks and kind regards

Thomas Dey