We have 8 brand new HPE DL380 Gen10 servers. Each of these servers has two HPE Ethernet 10Gb 2-port 562SFP+ Adapters. One is embedded and one on a PCI card. This card is based on the Intel X710 controller

HPE Ethernet 10Gb 2-port 562SFP+ Adapter OID8245220 | HPE™

We hooked two DAC cables, one from each card to our Juniper switch. The two ports on the Juniper switch are standard access ports. After installed the HPE customized version of ESXi 6.5 U1 we went into the console and added the two nics. We put in an IP address, gateway, mask, and DNS servers and then rebooted the host. During reboot we had a continuous ping going to the IP address of the ESXi management interface. The ping returned part way through the boot process and after fully booted the ping stopped. If I remove one of the 10Gb nics from the management network, the ping returns. If I use two of the 1Gb interfaces on this server which are based on a Broadcom chipset, the management interface works fine. The server has had all of its firmware upgraded. We are running driver version 1.5.8 and firmware version 10.2.5. The firmware came from here, I think it corresponds to VMWare's version of firmware 6.00

Drivers & Software - HPE Support Center.

I have a ticket opened with HPE but wanted to find out if Intel might have a solution for this

Could normal twisted-wire be used in x710 t4? Or some specific wire? And what is the main difference between the two products?

Hello Wired Ethernet Intel Community,

I have use INTEL I210,But I have some confused.

Because INTEL I210 (layout check list ) mention that for highly dense platforms PCIe design would be to have coupling capacitors in a staggered formation

but,in some INTEL document and non-INTEL document  mention that differential coupling capacitors in a staggered formation prohibited.

Which is Right?

thanks

Hi,

The i210 datasheet recommends to use certain flash devices. However their sizes are 512KB on wards only. There is mention in the datasheet that maximum of 8MB is supported.

I would like to know if lower memory sizes (128KB, 256KB) are supported or not.

Thanks.

Is possible that after 2 weeks intel ANS driver is still broken in win 1803? How many time i need to wait for this?

I can create the network LAG in LACP mode but i cant enable the interface. Is there any solution?

Embroidery is an ages-old craft coming all the way from the ancient Greeks. Even today embroidery is popular in its original form, it is widely used by many cultures for their national costumes, especially in the Slavic culture. However, the progress and development of technology introduces a way to digitize embroidery and implement it in many designing features. What’s even better, with further expanding of our knowledge we are gaining access to the personalization of the digitized embroidery.

The digitizing of embroidery gives us the opportunity of creativity with embroidered products. We can then efficiently bring embroidery to life but also customize it to suit our costumer's wishes and give it the modern look that is wanted today.

Thus, we come to the most popular ways to personalize with custom embroidery digitization and the advantages they bring.

Monogramming

One of these is monogramming and while the simplest way of customization it is widely used by companies designing products like T-shirts, scarfs, and even bathroom towels. These designs mainly include the costumer’s initials and along their wishes, special attention is given to custom fonts.

Family Events

Family events like baby showers where the baby’s blanket is embroidered, a wedding gift for a newlywed couple or graduation are examples where embroidered products might be the perfect gift. These show that embroidery is not easily pushed aside.

Sports Teams

The most important type of customization yet is logos and names that are used for sports teams. Trademarks and copyright here are very often so one should be careful not to copy anyone’s work and to always use proper licensing.

Corporate Uniforms

The last but certainly not the least way of customization are corporate uniforms. Widely popular are the embroidered logos of corporation uniforms. In this field, an expertise is highly needed and a holistic understanding of custom embroidery digitization.

Hello, I've been having trouble with this NIC not booting off of PXE.  I've already set the 10Gbe interface as a booting interface in the BIOS.  During PXE, I get the error message: PXE structure was not found in the UNDI driver code segment.  When it first didn't work, I used nvmupdate64e to update the NIC firmware.  nvmupdate now tells me my firmware is up to date (at version 6.01).  However, I still get the same exact error message at PXE boot.  I have also tried enabling PXE flash firmware for the interfaces.  But I still get the same error after all these driver installs and configuration enables. 

lspci -vv | grep -i 'Intel Corporation Ethernet Controller X710'

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

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

./bootutil64e

Port     Network Address     Location     Series     WOL     Flash Firmware          Version

3          6805CA385DF0      129:00.0     40GbE    N/A       UEFI,PXE Enabled     1.0.66

4          6805CA385DF1      129:00.1     40GbE    N/A       UEFI,PXE Enabled     1.0.66

ethtool -i eth2

driver: i40e

version: 1.5.10-k

firmware-version: 6.01 0x80003483 1.1747.0

bus-info: 0000:81:00.0

./nvmupdate64e

Num      Description                                                       Ver.      DevId     S:B          Status

01          Intel (R) I350 Gigabit Network Connection      1.99      1521      00:0001   Update not available

02          Intel(R) Ethernet Converged Network             6.01      1572      00:129     Up to date

              Adapter X710-2

Any idea what I need to do to get this interface to PXEboot?  eth2 is the interface that I am using.

Hello,

We want to update our network infrastructure to 10GB/s. Therefor we have to buy new networkcards for our existing servers.

The distance between server and networkswitch is more than 7meter. So we want to use 10m active direct attached cables.

On the support site of the X520 (SFP+ Modules, SFP Modules, and Cables Compatible with Intel® Ethernet... ) we saw that active cables are supported:

     Are active and passive direct attach cables both supported on the Intel® Ethernet Converged Network Adapter X520 Series?

• Both passive and active cables are supported.
• Active cables require Intel® Network Connections software version 15.3 or later.

But when I looked closer to the readme of the driver it say´s active cables are not supportetd. (https://downloadmirror.intel.com/14687/eng/readme.txt )

     Active direct attach cables are not supported. 

What is the truth now? Does any one has experience with X520 and active direct attached cables?

Regards,

manuel

Hello,
Sometime ago Intel incorporated Lantiq. I tried a lot of seaches, but no results.

Does anyone knows how can I findLantiq PEB 98010 FALCON-D documentation + SDK ?

Marcin

Adaptive Load Balancing, Windows 7/x64

2 NICs/team (X520-T2 and X540-T2), 4 nodes with one team each.

2 xs708ev2 switches, one connection per team per switch.

One NIC is always inactive.

Running current releases of Intel's Fortran and MPI on both CentOS7 and Windows 7 on the same nodes. Using one or the other system, not intermixing.

On same gear, CentOS 7 makes use of both NICs.

Same benchmark on Windows 7 (Class D FT, NPB) walltime=400s. On CentOS 7, walltime = 308s.

Running the same code on a single node using 16 cores to avoid network traffic (all messaging uses SHM):

Windows 7 walltime = 370s.

CentOS 7 walltime = 370s.

Casual observation of the switches: Windows 7 doesn't make use of the second switch but CentOS 7 does.

Here's my team_config entry for CentOS 7:

TEAM_CONFIG='{"runner": {"fast_rate": true, "name": "loadbalance","tx_hash": ["ipv4"],"tx-balancer": {"name": "basic"}}, "ports": {"enp2s0f0": {}, "enp2s0f1": {}}}'

Would like to make use of both NICs in each team under Windows.  Oh, if both of the team's NICs are connected to the same switch, then both NICs will be actively used.

Message was edited by: Art Lazanoff each switch is configured with VLAN and LAG disabled. When both connections in a ALB are connected the same switch, both NICs are active, Windows task manager shows a 20gbps data rate, and clock time for the test program improves by about 40s. The ALB's "test switch" diagnostic reports no errors.  Individually both switches perform the same way. When a team is connected using NIC-1 to switch 1 and NIC-2 to switch 2, The ALB "test switch" diagnostic reports "The switch is configured with aggregated ports, but the team type does not support port aggregation. The switch is configured with VLAN tagging, but the team has no VLANs. Reconfigure the switch for link aggregation, or disable VLAN tagging on the switch. "

After the last 2 Windows Updates , windows kicks out my Ethernet Controller from Device Manager

Maybe its KB 890830, but I don't know for sure.

After restore the System from last Recovery Point the network works as supposed.

Means I have a network device again and an internet connection.

Device Manager w/o Win Update:

Device Manager after Win Update

The Driver Version is Intel ProSet Version 15.6.25.0

It's a bit old, I know. I didn't updated it since I bought the system.

But, I tried to Update the Windows driver for 82579v and d/l PROWinx64Legacy.

But update cancelled. Tells me i have to deinstall the intel driver.

I deinstalled the driver in the device Manager and still this message appears

I installed "Intel Driver and Support Assistant" too, but it say no updates available.

Any ideas?

How to tell windows to not delete Device drivers?

How do I update Device Driver w/o crashing system completely?

Any other ideas?

Thanks in advance

Peter

Operating System:  Win7 64

Sorry, english is not the best and not my mother tongue. My German is a lot better ;-)

Hi

I want to run Ethernet Compliance Tests 10/100Mbps with I210-AT.

Are there any information available? I can not find anything in the datasheet.

E.g. create 100Mbps MLT-3 Random Test Pattern.

I can only find Test Mode Register Bits (15:13) in 1000Base-T Control Register (Page 0, Register 9) for Gigabit.

What is the purpose of 100 MB test select bits 3:2 of Copper Specific Control Register 3 - Page 0, Register 23 ?

What can I do with the PRBS Control - Page 26, Register 23 ?

Thanks for your help

Andrija

I had a pair of I210 NICs (a dual-NIC motherboard) teamed via Static Link Aggregation and all was working fine until today when Windows 10 x64 decided to apply the April 2018 cumulative update. The page providing the respective drivers with ANS support (https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=64399) states that the latest version is 23.1 (dated 2018-02-21). Even with this latest driver, however, I can re-create the team, but it cannot be enabled. The only way to keep things in a sort of working state is to disable one of the NICs as well as the virtual team interface and keep only the other NIC active (i.e., not an ideal scenario).

Is there any chance that a new version of the driver will be available soon?

Thanks.

nvx

Hi,

I got an XL710 where it is sitting on 4.16 on which I'm unable to update its firmware. I've tried firmware update tools from 4.42 to 6.05 which are saying "update not available".

I need to update its driver so that I can run latest Cisco Trex version's for pumping traffic.

here are the card details:

#lspci -vvv

84:00.0 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 01)

        Subsystem: Intel Corporation Ethernet Converged Network Adapter XL710-Q2

        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: 32 bytes

        Interrupt: pin A routed to IRQ 63

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

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

        Expansion ROM at c9200000 [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=8 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 256 bytes, MaxReadReq 4096 bytes

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

                LnkCap: Port #0, Speed 8GT/s, Width x8, ASPM not supported, 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 8GT/s, Width x8, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-

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

                DevCtl2: Completion Timeout: 65ms to 210ms, TimeoutDis-, LTR-, OBFF Disabled

                LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-

                         Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-

                         Compliance De-emphasis: -6dB

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

#./nvmupdate64e -i -l

[00:132:00:00]: Intel(R) Ethernet Converged Network Adapter XL710-Q2

    Vendor                 : 8086

    Device                 : 1583

    Subvendor              : 8086

    Subdevice              : 1

    Revision               : 1

    LAN MAC                : 6805CA27C4E8

    Alt MAC                : 000000000000

    SAN MAC                : 6805CA27C4EE

    ETrackId               : 800010E0

    NVM Version            : 4.16

    VPD status             : Valid

    VPD size               : 63

    NVM update             : No config file entry

      checksum             : Valid

    OROM update            : No config file entry

      CIVD                 : 0.0.0

[00:132:00:01]: Intel(R) Ethernet Converged Network Adapter XL710-Q2

    Vendor                 : 8086

    Device                 : 1583

    Subvendor              : 8086

    Subdevice              : 0

    Revision               : 1

    LAN MAC                : 6805CA27C4E9

    Alt MAC                : 000000000000

    SAN MAC                : 6805CA27C4EF

    ETrackId               : 800010E0

    NVM Version            : 4.16

    VPD status             : Valid

    VPD size               : 63

    NVM update             : No config file entry

      checksum             : Valid

    OROM update            : No config file entry

      CIVD                 : 0.0.0

card details (details present on the card):

6805CA27BFD8

012  181407

H29452--005

I've already tried modifying the nvmupdate.cfg file but I'm concerned that I might brick the card.

Please let me know how to go about updating this card.

Thanks

Ganesh.

Hi,

For my new project I am designing an Ethernet switch card. For that there is a requirement for PTP and PRP protocols in the module. I am in serious confusion among these two protocols. I need to clarify whether PTP and PRP are purely software protocol or I need to choose an Ethernet switch IC which supports these two protocols. The confusion is whether PTP and PRP are hardware or software dependent.

Regards

Hafiz

What is the MTBF for the 8391GT network adapter?

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!

Hello,i have a server with old network driver dated (m-d-2015) , i have downloaded new driver 22.2 (07/06/2017)

then i have installed the new driver but when checking the driver to confirm the update  i still see the old one .

i have ran the .exe and followed the wizard.

can you tell what is the problem please?

Regards

What installs it and is it relevant with Intel Network Connections 21.1.30.0?  We are very security conscience and want to remove this software if it has no purpose. I am wondering if this was installed by an older version of Intel Network Connections and is no longer needed. Is this just a registry file that can be removed?

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