Hi All,

  We have "Intel Ethernet Converged Network Adapter XL710-QDA2".

  1) Configured in 2x40 mode

  2) The two ports on the board are connected back to back with below SFP:

        MACROREER

        40GBase-CU QSFP+ Cable 1m

      We are able to observe that the link status on both ports is UP. And, we are able to run tests between the ports.

  3) When we use the below Intel SFP's on both ports connected with MTP 24 fibre optical cable, the ports are not coming UP (Link status shows down)

        E40GQSFPSR

        QSFP-40G-SR4  16-26

        Class 1  21CFR1040.10

        LN#50 6/2007

        FTL410QE2C-IT

     Please help us in understanding why the ports are not coming up with the above mentioned Intel SPF's (point 3).

Is the optical cable we are using compatible with the SPF's or need to use some other optical cable or SFP to bring the ports UP?

Should we configure the board in any specific mode ?

Looking ahead for your response

Thanks in advance

-- Anand Prasad

Hello everyone,

I'm looking to purchase a 10gb network card to install into my Supermicro SYS-5018A-FTN4. I currently am running PFsense and I was wondering, the supermicro only has 1 pcie slot. Will this card be able to do one port for uplink and one port for downloads?

The network I want to install will be as followed.
Modem Arris SB8200> x540 T2 Pfsense box > Ubiquiti Networks US-16-XG > X540T1(homepc)

I have no professional experience in networking. This is purely for my home/hobby use.

Thanks for your help.

David Tiao

I was trying to install an intel pro/1000 pt dual-port card into a Ubuntu linux server computer and ran into the "NVM Checksum is Invalid" message.  I tried to run the bootutil utility on the card, but now only ports 1 & 2 show and the mac addresses are gone.  Is this card salvageable or is it bricked?  I ordered another single-port card, but does anyone know the proper way to handle this issue?

Brian

Hello,

I have downloaded both the 20.7.1 and 22.0.1 version of firmware update and tried to update the ROM from PXE to the EFI ROM.  Under both Linux and a UEFI shell, it fails every time.  This occurs both on a dual port Pro/1000 and a single port.  The Linux output is:

[root@testsystem BootUtil]# Linux_x64/bootutil64e -nic=2 -up=efi

Intel(R) Ethernet Flash Firmware Utility

BootUtil version 1.5.94.2

Copyright (C) 2003-2015 Intel Corporation

ERROR: Flash too small for the image

Port Network Address Location Series  WOL Flash Firmware                Version

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

  1   001B21009F04     1:00.0 Gigabit YES PXE                           1.3.35

  2   0015172EE90F    49:00.0 Gigabit YES PXE                           1.3.35

How do I flash an EFI ROM on this cards?  I can flash the PXE ROM on them, but not the EFI ROM.

Thanks in advance,

Marc

I have the same problem with kernel 4.4.77, ixgbe driver version 5.2.1 and ixgbevf 4.2.1. OS ALT Linux.

Spoof cheking was disabled, but no ping in two VM with the same vlan.

dmesg host:

[162311.173561] ixgbe 0000:05:00.1 eth0: 2 Spoofed packets detected

[162313.177679] ixgbe 0000:05:00.1 eth0: 1 Spoofed packets detected

[162315.181748] ixgbe 0000:05:00.1 eth0: 2 Spoofed packets detected

[162333.211099] ixgbe 0000:05:00.1 eth0: 1 Spoofed packets detected

[162337.217085] ixgbe 0000:05:00.1 eth0: 1 Spoofed packets detected

[162339.220074] ixgbe 0000:05:00.1 eth0: 2 Spoofed packets detected

# ip li show eth0

7: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq master ovs-system state UP mode DEFAULT group default qlen 1000

    link/ether a0:36:9f:25:80:5e brd ff:ff:ff:ff:ff:ff

    vf 0 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 1 MAC da:55:a4:db:0f:d5, spoof checking off, link-state auto, trust off, query_rss off

    vf 2 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 3 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 4 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 5 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 6 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 7 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 8 MAC 9a:1f:86:df:b1:d8, spoof checking off, link-state auto, trust off, query_rss off

    vf 9 MAC aa:b7:85:e1:1b:06, spoof checking off, link-state auto, trust off, query_rss off

    vf 10 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

    vf 11 MAC 9a:1f:86:df:b1:d8, spoof checking off, link-state auto, trust off, query_rss off

    vf 12 MAC aa:b7:85:e1:1b:06, spoof checking off, link-state auto, trust off, query_rss off

    vf 13 MAC 00:00:00:00:00:00, spoof checking off, link-state auto, trust off, query_rss off

Hi,

I have the exact same problem.

I have an eng sample from intel that has 4.16

Num Description                               Ver. DevId S:B    Status

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

01) Intel(R) Ethernet Converged Network       4.16  1583 00:008 Update not    

    Adapter XL710-Q2                                            available

How can i proceed

Thanks

Kalyan

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

I have struggeled a lot with a crazy weird issue. I have a Supermicro server, 16x2,5 drives in Raid, LSI Megaraid.  Server connected by a 82599 10Gbps network adapter to a Cisco switch, and 1Gbps to clients. To all my Windows 7 clients a get transfer speeds 115MB/sec. To my Windows 10 clients I only get ~45MB/sec. I was certain this had to have something to do with the windows installation, SMB  signing or similar. But after a total re-install of the server, it behaves the same. So in total confusion I tried connecting the server by the 1Gbps onboard adapter (Intel I350) to the switch, and voila, 115MB/sec to both Win7/10-clients.  This is of course not a solution since I need the 10Gbps bandwidth to my 9 clients. So to my big surprise it seems to be something fishy going on with the Intel 82599 adapter and Win10 clients, any ideas ?  Laters drivers installed. I have tested with default settings, tried the different profiles (standard, lo latency, web-server) and other settings a little randomly based on other comments online, but to further improvements.

For the record, I also have a couple of old Win2008 servers and these provide ~115Gbps to all clients.

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

Hi,

      we have an issue about the I210-IS, when we set the PCIE root port to "disable", the speed LED and active LED will light up.

when set it to "enable", and there was no link, the LEDs will go out.

We co-lay I210-AT and I210-IS on the schematic, and when mount I210-AT，there was no this issue.

Could you please check whether it is related to the EEPROM or not?

Our EEPROM version is 3.25

Thanks.

Vicky

I am using Wireshark on a machine that has ( from the registry via regedit ):
DriverDesc : Intel(R) Ethernet Connection (2) I219-LM

and I added:
MonitorMode : 1 ( REG_DWORD 32 bit )
as per Intel help forum:
https://communities.intel.com/thread/51323

That did not help

Problem is that Wireshark sees all the traffic to and from the machine it is on but not between two different machines; they are connected with a hub.

In Capture - Options - Input, the Promiscuous box is checked.

Has anyone encountered this?  Do you have a remedy? Is the Driver filtering out those other packets?

Thanks.
Boyd

Hello,

Environment:

OS:  Windows 10E X64 1703

CPU:  Intel i7-6700k 4GHz

RAM: 32GB

NIC:  Intel 1219V / 1211 (on-board) (using latest Intel ANS drivers)

MB:  Gigabyte H170N (r.1)

Router:  Netgear R7000 (DD-WRT)

Gateway: Arris SB 6190 (Comcast)

Background:

I've been using ANS Teaming on and off for the past 6 months.  The team has mostly worked up until a few days ago, and  I have no idea what might have changed in my environment or why this problem might have started.

I create the team generally following this method:

1. Install the ANS driver (reboot)

2.  Unplug NICs from router

3. setup switch: (from different LAN client)

     a. create LAG group

     b. assign ports to LAG group

     c. select static link aggregation on ports 3 & 4

     d. disable STP

     3. Enable TRUNK

4. Create static link aggregation team in ANS

5. Power off computer

6. Power off router

7. Plug NICs into router

8. Power on router

9. Power on computer

Team is created successfully.  (screenshot 1)

Issue:

Receinvg A LOT of errors/dropped connections on the team. If I run a speedtest (speedtest.net) and watch the team in real-time, Err/Drop numbers will spike drastically. There are no errors reported on the router syslog.

After TWO speedtests, the team will show approx Err: 2000 / Drop 4000 (Screenshot 2)

After 3 days of heavy traffic, the team will show approx Err: 50,000/ Drop: 80,000 (Screenshot 3)

Troubleshooting:

-Ran Intel ANS diagnostics: All tests passed

-Removing team

-Reinstalling NICs, and drivers

-Removing team, running speedtest on individual NICs (Very few err/drops)

-Replaced cables

Any ideas what might be happening?

Thanks,

SV

Screenshot 1:

Screenshot 2:

Screenshot 3:

Hi Folks,

  Working with VMWare Workstation Pro on an x64 Win10 enterprise machine (10.0.14393) (aka Redstone 1 or Anniversary Edition), attempting to get output from different VMs onto different .1q tagged VLANs on a trunk port.  Unfortunately, I'm having little success.

  Based on my reading, if I install the most current Intel driver package, 22.4.0.1, I should either be unable to create VLANs off the NIC (if I'm missing needed win10 updates), or they should work.  I seem to be in a middle ground of some kind.  I can create the VLANs just fine.  Unfortunately, I get untagged output from the physical port for everything assigned to any VLAN.  I doubt it's a sniffer problem since I can see .1q tags from a switch when capturing via the same external USB NIC.

  The Intel driver installer refers me to a list of required Win10 updates in a user guide that I'm not finding anywhere.  Any guidance would be most appreciated.

I have downloaded and installed the latest Intel Network Adapter Driver for Windows 7 (64-bit) marked as version 22.10. However, what ends up getting installed is version 22.9.6 which was the previous release.

Download Intel® Network Adapter Driver for Windows 7*

Not a big deal, everything functions fine, but is anyone else noticing this?

I've installed the driver PRO2K3XP_32 on HP Proliant ML350 Win 2003 Server, but the Intellan tree 1.3.6.1.4.1.343 is empty. How may I show the SNMP Lan Status?

I encountered the same Problem.

Additional Information:

before 23.07.17 the system worked properly with windows 10 64 home.

in the eventlog of the Adapter i can find an update from 23.07.17 22:23.

Since this update windows presents after system start an Intel 82579LM insted of Intel 82579V in the device manger.

A klick on the recongnize changed hardware button solves the Problem for some time, (I didn't test if it reoccures after longer work, e.g. one hour)

But always after a system reboot or cold boot the same problem occures again.

The latest driver is installed,

Cable an router checked.

Any suggestions?

Hello

I have an Intel server with Ubuntu 16.04.2

02:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)

02:00.1 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01)

I am unable to set mtu to a value higher than 1500, the error I get is:

SIOCSIFMTU: Invalid argument

I have downloaded and installed driver 4.6.4 and 5.0.4 and both DO NOT WORK

I have kernel

4.8.0-49-generic #52~16.04.1-Ubuntu SMP Thu Apr 20 10:55:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

I have tried issuing the following commands:

ethtool -K eno4 rx-vlan-filter off

ethtool -K eno3 rxvlan off

ethtool -K eno3 txvlan off

But still cannot set the mtu to a different value.

Can anybody help?

Thanks

Hi,

I am also encountering this issue (4-port card).

X710/X557-AT 10GBASE-T :  FW: 5.05

Any ideas? Can the feature be disabled in the driver?

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.

Using an updated driver, I cannot seem to get my interfaces up. Looks like the driver is not allowing the NIC to work due to the SFP+ module type, which worked previously on my Debian Stretch host. Clearly the NIC is detecting and reading the DAC, but I don't understand why it is not working. This is a 40G-breakout cable with 40-to-4x10G SFP+ DAC (TwinAx). I have tried adding the following to work around it, but it still does not work:

root@lab4:~# cat /etc/modprobe.d/i40e.conf

options i40e allow_unsupported_sfp=1

This was also discussed here, but there was no followup:

Intel Ethernet Drivers and Utilities / Mailing Lists

Output from dmesg:

[    4.439190] i40e 0000:08:00.3: PCI-Express: Speed 8.0GT/s Width x8

[    4.447918] i40e 0000:08:00.3: Features: PF-id[3] VFs: 32 VSIs: 34 QP: 8 RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA

[    4.453414] i40e 0000:08:00.2: Rx/Tx is disabled on this device because an unsupported SFP+ module type was detected.

[    4.465288] i40e 0000:08:00.2: Refer to the Intel(R) Ethernet Adapters and Devices User Guide for a list of supported modules.

Other pertinent output:

root@lab4:~# ethtool -m eth6

Identifier                                : 0x03 (SFP)

Extended identifier                       : 0x04 (GBIC/SFP defined by 2-wire interface ID)

Connector                                 : 0x21 (Copper pigtail)

Transceiver codes                         : 0x00 0x00 0x00 0x00 0x00 0x04 0x00 0x00

Transceiver type                          : FC: Copper Passive

Encoding                                  : 0x00 (unspecified)

BR, Nominal                               : 10300MBd

Rate identifier                           : 0x00 (unspecified)

Length (SMF,km)                           : 0km

Length (SMF)                              : 0m

Length (50um)                             : 0m

Length (62.5um)                           : 0m

Length (Copper)                           : 3m

Length (OM3)                              : 0m

Passive Cu cmplnce.                       : 0x01 (SFF-8431 appendix E) [SFF-8472 rev10.4 only]

Vendor name                               : Amphenol

Vendor OUI                                : 78:a7:14

Vendor PN                                 : 624400003

Vendor rev                                : A

Option values                             : 0x00 0x00

BR margin, max                            : 0%

BR margin, min                            : 0%

Vendor SN                                 : APF13470035GDT

Date code                                 : 131122

root@lab4:~# ethtool -i eth6

driver: i40e

version: 2.4.3

firmware-version: 6.01 0x800034af 1.1747.0

expansion-rom-version:

bus-info: 0000:08:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

root@lab4:~# ethtool eth6

Settings for eth6:

Supported ports: [ ]

Supported link modes:   Not reported

Supported pause frame use: Symmetric

Supports auto-negotiation: No

Advertised link modes:  Not reported

Advertised pause frame use: No

Advertised auto-negotiation: No

Speed: Unknown!

Duplex: Unknown! (255)

Port: Other

PHYAD: 0

Transceiver: internal

Auto-negotiation: off

Supports Wake-on: d

Wake-on: d

Current message level: 0x0000000f (15)

       drv probe link timer

Link detected: no

root@lab4:~# ip link show eth6

5: eth6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000

    link/ether 68:05:ca:2f:7c:b0 brd ff:ff:ff:ff:ff:ff