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

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.

We have 2 servers using X70 nics (Debian Jessie, Kernel 4.14.15).

On each interface we have two ip on same subnet.

Randomly, the secondary ip address doesn’t answer to arp request anymore.

The only solution we have to fix the problem is to manually send arp announcements over the network using a script (while true, sendarp).

There is no proxy arp on neighbors.

# ethtool -i eth0

driver: i40e

version: 2.1.14-k

firmware-version: 6.01 0x80003485 1.1747.0

bus-info: 0000:82:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

This issue occurs on both servers, and we have same software configuration on a lot  sites, and the problem appear only when there is X710 nics.

Anyone already had this problem ?

Kind regards

Hi Sharon and Ninwardspiral,

We are having similar problems with the exact same NIC, and by coincidence with the same breakout cable (although we tested many).

Driver and firmware are updated to the latest versions available (2.4.3 and 6.01 respectively):

version: 2.4.3

firmware-version: 6.01 0x800034af 1.1853.0

First cable that does not work: ( QSFP to 4x10G SFP+, amphenol, 2m)

From the manufacturer website: Each QSFP-SFP+ splitter cable features a single QSFP+ connector (SFF-8436) rated for 40-Gbps on one end and (4) SFP+ connectors (SFF-8431), each rated for 10-Gbps, on the other.

SF-QSFP4SFPPS-002 Amphenol Commercial Products | Cable Assemblies | DigiKey (exact cable we bought)

ethtool -m output:

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) : 2m

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

Vendor rev : A

Option values : 0x00 0x00

BR margin, max : 0%

BR margin, min : 0%

Vendor SN : APF1718002044N

Date code : 170513

ethtool <intf> output (after bringing interfaces up):

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

Second cable that does not work: ( QSFP to 4x10G SFP+, generic brand):

2m(6.6ft) 40G QSFP+ to 4SFP+ Passive Breakout DAC Cable | FS.COM

ethtool -m <intf> output:

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) : 2m

Length (OM3) : 0m

Passive Cu cmplnce. : 0x03 (unknown) [SFF-8472 rev10.4 only]

Vendor name : FIBERSTORE

Vendor OUI : 00:00:00

Vendor PN : QSFP-4SFP10G-DAC

Vendor rev :

Third Cable, it does work but its not what we need:

https://www.brack.ch/delock-direct-attach-kabel-330520

As a way to see if the NICs work, we also bought a SFP+ to SFP+ cable that is supposed to support SFP MSA and SFF-8431, but not SFF-8472. What is impressive is that this cable is detected and allows us to bring the link up

and even exchange some data at 10gbps. However, that is not what we need.

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) : 1m

Length (OM3) : 0m

Active Cu cmplnce. : 0x0c (unknown) [SFF-8472 rev10.4 only]

Vendor name : CISCO-TYCO

Vendor OUI : 00:40:20

Vendor PN : 2127493-1

Vendor rev : A

Option values : 0x00 0x12

Option : RX_LOS implemented

Option : TX_DISABLE implemented

BR margin, max : 0%

BR margin, min : 0%

Vendor SN : 164800277_______

Settings for ens787f3:

Supported ports: [ FIBRE ]

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: 10000Mb/s

Duplex: Full

Port: Direct Attach Copper

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

Fourth Cable (to be delivered):

Intel X4DACBL3 40G QSFP+ Breakout DAC Cable | FS.COM

We are waiting for a fourth cable (this time is supposed to be intel compatible, but we dont know if it will be compatible with our switch...).

Why is the amphenol cable not working if the output of ethernet says: (SFF-8431 appendix E) [SFF-8472 rev10.4 only] which as stated in : Compatible SFP+ Modules, SFP Modules, and Cables for Intel® Ethernet...  should be enough to be compatible. Why

only SFP+ to SFP+ cables work? What should we do? We spent to many resources and time buying different cables.

And to finish, would this NIC Intel® Ethernet Network Adapter XXV710-DA2 Product Specifications  give us better results?

Thanks.

Edgar

Here is some information about my environment :

Hardware :

Supermicro X10SRi-F motherboard with Onboard i350 controller;

Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz;

Intel Corporation 82576 Gigabit Network Adapter;

System:

Centos 7

Kernel:4.15.4-1.el7.elrepo.x86_64

Hypervisor:KVM

So far, vt-d and SR-IOV are all enabled on the BIOS and intel_iommu=on is enabled on the host system and it is verify by virt-host-validate command line.

Both onboard i350 controller and intel 82576 are virtualized into different virtual functions(vf). Things are getting different about iommu group. Each vf from i350 could successfully be in individual iommu group, but vf from intel 82576 are grouped into the same iommu.

Since all the vfs from intel 82576 are in the same IOMMU group, whenever I want to attach any of them to VM, it will generate the error as below:

“

…

2018-02-23T17:16:18.202445Z qemu-kvm: -device vfio-pci,host=04:10.1,id=hostdev0,bus=pci.0,addr=0x9: vfio: error, group 34 is not viable, please ensure all devices within the iommu_group are bound to their vfio bus driver.

…

“

As for the i350, I don’t have this problem.

I have read some posts, saying that this is maybe the ACS problem but my cpu does support that:

“

00:01.0 PCI bridge: Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D PCI Express Root Port 1 (rev 01) (prog-if 00 [Normal decode])

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

….

        Capabilities: [100 v1] Vendor Specific Information: ID=0002 Rev=0 Len=00c <?>

        Capabilities: [110 v1] Access Control Services

…

“

From Intel 82576 specification, it says it supports SR-IOV, however, it does not work unless each VF has its own individual IOMMU group.Does anyone know how to do it?

Thank you!

Hi.

I am having problems with I219-V VLAN tag. Whan adding  a tag I get blue screen every single time., reason Bad_pool_caller.

First step I am adding new VLAN in VLAN tab from Intel Ethernet conection I219-V:

And when adding new VLAN tag, let's say 13 it crashes:

I don't even get a chance to press second OK in Intel window, it crashes right here. It says Configuring for two seconds, maybe tree and the blue screen. I can make it anytime I want.
I tried with versions 12.17.8.7 and 12.15.25.6:

I have Lenovo T470s. Any help would be gratefull.

Regards

Hi.

I am having problems with 82574L

Hardware :

03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

04:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

05:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

06:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

System:

Centos 7.3   kernel：3.10.0-514.el7.x86_64

Output from message

Feb 26 20:50:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 26 20:50:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 26 22:10:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 26 22:10:04 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 26 22:40:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 26 22:40:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 26 23:20:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 26 23:20:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 26 23:30:02 localhost kernel: e1000e: slot0_GE2 NIC Link is Down

Feb 26 23:30:02 localhost kernel: e1000e: slot0_GE2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 27 01:10:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 27 01:10:04 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

Feb 27 03:10:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Down

Feb 27 03:10:02 localhost kernel: e1000e: slot0_GE4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

modinfo

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

version:        3.3.6-NAPI

license:        GPL

description:    Intel(R) PRO/1000 Network Driver

author:         Intel Corporation, <linux.nics@intel.com>

rhelversion:    7.3

srcversion:     6453212B70344504D53DE09

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

depends:        ptp

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

parm:           copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)

parm:           TxIntDelay:Transmit Interrupt Delay (array of int)

parm:           TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)

parm:           RxIntDelay:Receive Interrupt Delay (array of int)

parm:           RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)

parm:           InterruptThrottleRate:Interrupt Throttling Rate (array of int)

parm:           IntMode:Interrupt Mode (array of int)

parm:           SmartPowerDownEnable:Enable PHY smart power down (array of int)

parm:           KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)

parm:           CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)

parm:           EEE:Enable/disable on parts that support the feature (array of int)

parm:           Node:[ROUTING] Node to allocate memory on, default -1 (array of int)

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

[root@localhost ~]# ethtool -k slot0_GE4

Features for slot0_GE4:

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

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

tx-vlan-offload: on

ntuple-filters: off [fixed]

receive-hashing: on

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]

tx-mpls-segmentation: off [fixed]

fcoe-mtu: off [fixed]

tx-nocache-copy: off

loopback: off [fixed]

rx-fcs: off

rx-all: off

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

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

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

busy-poll: off [fixed]

tx-sctp-segmentation: off [fixed]

l2-fwd-offload: off [fixed]

hw-tc-offload: off [fixed]

[root@localhost ~]#

Hi there,

I'm using X710-DA4 with SR-IOV mode on Skylake servers.

latest fw and drivers (i40e) installed on system. and vf driver is added into blacklist.

there is a VF that belongs to a PF. and that VF is attached to a VM.

after that, I tried ping from VM to a pc that connected to the server port that has the PF.

it works well. ping packets are received by the pc.

the problem (or different behavior) is that,

even the PF link goes down using "ifconfig xx down or ip link set xxx down" but the VF still sending packet to the pc.

is this right behavior on X710/XL710?

if yes, any architectural/tech background that I can get?

Regards,

hi,

I am currently using a network adapter from Intel.I can see some information from the command line "lspci" and it is "Intel Corporation 82576 Gigabit Network Connection", so I think it is "Intel® 82576 Gigabit Ethernet Controller" but it seems there are two types of adapters under this category, one is 82576EB and the other one 82576NS. Are there any ways can allow customer to further find out what exact model of network adapter they are using? I have the Serial Number:"1CA2CE0341ADG18771-002" but I just done know how to use this number to search on the Intel website.

Thanks

I want to create Multi vlan for network card I210 and I217-LM on my PC.

but I always got "one or more VLAN(s) could not be created, Please check the adapter status and try again", meanwhile network card disabled.

my operation system is windows 764bit Ultimate.

after I tried several times, there were several virtual network card created, but no vlan. I even can not uninstall the created virtual network card.

anybody can give some suggestion?

hello

I designed a Thunderbolt dock with i210AT LAN. I want to know how to modify the "subsystem vender ID” and “subsystem ID.” I tried to run lanconfw64e.exe but cannot save.

Appreciate your help

Anderson

Hej,

I am looking for the NIC 82551IT for a Win 10 (IoT Enterprise) driver. We Need either the driver as binary or the source code. Any ideas?

We have hands on the source code of an INTEL NIC i210IT driver for Win 10. Would it make sense to take an old Linux driver and integrate it in the Win driver?

We use the INTEL NIC 82551IT in our hardware. The 82551IT is directly connected to PCI. Currently we operate a Microsoft WES with INTEL's original driver.

Best Regards,

Jürgen

Is there any Linux utility to do MDIO read/write for external PHY on  Xeon-D / X552  SOC running ixgbe driver 5.3.5?

I am sorry to hijack this thread.

We are also seeing the similar issue at our hosts. After upgrading Intel NIC firmware, the NICs do not detect the link anymore. They were fine before the NIC firmware update. We tried updating i40e driver to the latest available, but it did not help.

Host information

Model                                            Dell R630

Bios Version                                 2.7.1

I noticed the XXV710 is part of the Fontville series, which includes the X710 and XL710. Additionally the NVM package is the same for all 3 of these NICs.

Intel® Ethernet Controller XXV710-AM2 Product Specifications

Is it possible to flash the 4-port 10GE X710, or the 1-port 40GE XL710 to function as a XXV710? Even if it can only support 2x25G connections, it would be fine.

environment:

Redhat 7.4

ixgbe, ixgbevf  (82599es ethernet controller)

docker 1.13

requirement:

The docker container had to have a trunk port which is mapped to a VF.

docker guest running in privileged mode.

Problem:

when the container emits the q-in-q packets, the kernel drops as the packets are spoofed.

in the recv direction how can i classify based on the vlan (with no vlan interface in the container)?

Thanks for the help

We have Hyper-V Server on which we created VMSwitch (with Switch Embedded Teaming) on two built in Intel722 adapters.

On VMSwitch we have NetAdapter for Management OS with ip assigned(created along with vmswitch). After creation everything works fine until reboot, after which we are observing duplicates of packets ie:

18 bytes from xxx: icmp_seq=1 ttl=128

18 bytes from xxx: icmp_seq=1 ttl=128 (DUP!)

18 bytes from xxx: icmp_seq=2 ttl=128

18 bytes from xxx: icmp_seq=2 ttl=128 (DUP!)

If we remove VMSwitch and create it again, everything works fine until reboot.

MacAddress/IP configuration is always the same and don't change after reboot. We investigated the network, but it seems that those macaddressess exist only on that host and we see (using Wireshark/tcpdump) that duplicates are indeed coming from that server. If we use different network card (Intel x550) to create VMSwitch on that server it all works fine. Also if we use those cards without VMSwitch there are no duplicates.

Mobo: X11SPH-nCTF + built in Intel X722 for 10GBASE-T

Processor: Intel Xeon Silver 4110 2.1GHz

OS: MS Hyper-V Server 2016 Version  10.0.14393 Build 14393 + all updates (also tested on MS Windows Server Standard 2016 + all updates)

Driver: c:\windows\system32\drivers\i40eb65.sys (1.8.94.0, 996.54 KB (1,020,456 bytes), 2/19/2018 11:50 PM) (from latest 23.1 Driver Pack)

We don't see anything in logs. We tried reinstalling, even with different OS, situation seems to be the same.

We have the same OS + VMSwitch configuration on different Motherboards/Network Cards but there we don't observe any problems.

Are there any known bugs related to x722 and Microsoft VMSwitch or do you have any suggestion?