Quantcast
Channel: Intel Communities : Unanswered Discussions - Wired Ethernet
Viewing all 1749 articles
Browse latest View live

i40e x710 4x10G card not working anymore with DAC

$
0
0

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


XL710-QDA2 on windows 10?

$
0
0

Hello everyone,

I'd like to use the XL710-QDA2 QSFP+ network adapter as PCIe expansion card to connect my workstation - Windows 10 PC to my centOS homeserver. However, Windows 10 seems to be lacking compatibility for this card according to official documentation. Can anyone confirm or deny this card would work in a W10 PC ?

Best regards,

i40e driver does not work due to the unsupported SFP+ module type

$
0
0

I compiled and installed the network adapter driver for PCIe 40 Gb Ethernet(version 3.4.2). The driver is also loaded in the kernel successfully (Ubuntu 16.04). However, when I connect QSFP+ cables I am getting the following error message:

Rx/Tx is disabled on this device because an unsupported SFP+ module type was detected.

 

Is this because I am not using Intel QSFP+ cables?

Is there any way to allow unsupported SFP?

 

Best,

Marjan

Teaming I210 with I217

$
0
0

Can an I210* and I217-LM be configured for teaming together?  In Windows 10 and Windows Server 2016?

 

Same questions for: I210 and I219-LM - can they be teamed?

 

* As an aside:  I'm a little confused by the I210 designation.  Can somebody clarify this for me?

  • I'm pretty sure these motherboards have an I210-AT NIC.
  • The Intel SSU tool identifies the NIC as I210 with no suffix.
  • I don't see an Ark page for I210, but there is a data sheet for I210.
  • There are Ark pages for the five I210 variants (I210-AS, I210-AT, I210-CS, I210-IS, I210-IT) listed in the "Ethernet Controller I210 Series" (Intel® Ethernet Controller I210 Series Product Specifications)
  • So are the five I210 variants all function- and feature- same?

Teaming Intel X520 10GbE Dual Port KX4-KR Mezz

$
0
0

Card is in a Dell PE M620.  Seeing multiple cases where trying to create a static link aggregation is failing with the message "All device in a Static Link Aggregation team must be capable of running at the same speed.  At least one device in the team is not capable of running at a lower speed."

 

This message appears even when trying to create a team with just one adapter.   Both the switch ports and the NICs are set to 10 Gb Full.  Operating system is WIndows Server 2012R2 but has also happened on Server 2008R2,

X550-T2 Yottamark valid, but MAC wrong?

$
0
0

Like others, I bought an X550-T2 (direct from Amazon themselves) and the Yottamark is valid, but the MAC doesn’t match.

 

Is this going to be an on-going production problem?

Media disconnect issue

$
0
0

Hi,

 

I have an Dell CS24-TY server fitted by manufacturer (as I know this series is made by Quanta) with a dual NIC (Intel® 82576) and with up to date Windows 2012 R2 OS. The two nic's are regularly configured in NIC-Team (but also where sometimes let alone). I noticed that from some time (let say some four, five months ago), regularly but in a random way Windows reports that media was disconnected. The only way to solve this condition is to restart the server. This bother me in many way since is my DNS server, my domain controller and so on. I may not believe that is a hardware condition since after reboot it restores connection. So before considering to buy another PCI-e NIC (that is somehow expensive) I try to find that maybe this condition is a kind of miss-configuration.

In Windows Event Viwer regularly I found entries like this:

//

Member Nic {b0978897-b852-4cef-a552-e0cc7adc0010} Disconnected.

//

The description for Event ID 27 from source e1iexpress cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

 

Intel(R) 82576 Gigabit Dual Port Network Connection

 

the message resource is present but the message is not found in the string/message table

//

followed at seconds

//

Member Nic {14ae3c8c-2f85-4b17-91d6-bf591a9014ef} Disconnected.

//

The description for Event ID 27 from source e1iexpress cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

 

Intel(R) 82576 Gigabit Dual Port Network... [5,0,1]

 

the message resource is present but the message is not found in the string/message table

//

After digging the event log I may find issues like this that by any appreciations are followed by a "natural" restore (a very temporary condition), but mainly after this I have to manually reboot the server.

 

Any hints to investigate this are welcomed.

Regards

Failure with IGB multicast group traffic after several days

$
0
0

Setup:

Debian 8 (Jessie)

Kernel: Linux 3.16.0-4-686-pae

IGB Driver: 5.3.5.12 (the same problem occurs with the original driver from Debian, 5.0.5-k)

 

After several days (between 2-20) our systems stop receiving multicast packets for certain groups they belong to. Each of these systems has two interfaces, an IGB and e1000e which are bonded together (Bonding Mode: fault-tolerance (active-backup)). The problem only ever occurs when the IGB is the Active Interface.

 

The switch to which the IGB interface is connected, is sending the relevant multicast packets to the Interface - this has been verified by using port-mirroring on the switch. However if I run tcpdump in non-promiscuous mode, I do not see any incoming packets for that group but I do see the outgoing IGMP Group Report.

Using tcpdump in promiscuous mode will reset the interface, which immediately fixes the problem and I will see the traffic.

 

Netstat always reports active membership of the intended groups:

root@vlab-210-03:~# netstat -gn

IPv6/IPv4 Group Memberships

Interface       RefCnt Group

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

lo              1      224.0.0.1

eth1            1      224.0.0.1

bond0           1      224.0.0.251

bond0           1      224.0.0.1

bond0           1      239.255.10.10

bond0           1      239.255.10.11

bond0           4      239.110.92.1

bond0           2      224.0.0.107

bond0           3      224.0.1.129

eth0            1      224.0.0.1

 

It is only ever the groups 239.255.10.10 and 239.255.10.11 which fail, and this only occurs when using the IGB interface. Other multicast traffic functions normally.

The two affected groups are carrying a large volume of video traffic.

 

The system is still running in a failed state, so I can query it for more information.

 

Thanks,

Tom.


netwerk verbinding verbreekt steeds

$
0
0

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

XXV710 firmware downgrade

$
0
0

Hello,

 

I have an XXV710 NIC with updated firmware version 6.02. I would like to downgrade it back to 5.51. I did not find the appropiate NVM Tool for that.

Is there a correct NVM tool for that and just I was not prudent enough, or I just cannot perform this downgrade?

 

Thanks and Regards,

János

I210 Ethernet controller

$
0
0

Hello,

 

I am engineering LAN with i210 ETH controller. I found out that Pull-up/Pull-down resistors Table have symbols Y and N which I do not understand what they mean. Could you help?

 

Pull-up-Pull-down.png

Where to buy genuine Intel NICs?

$
0
0

Hello,

 

Reading lots of stories about people getting knock-of Intel cards, even from "legit" vendors.

 

What is a good way to make sure that I get a genuine Intel part and not one of these "counterfeit" cards?

 

I am looking at an i350T4V2 or i350T2V2, but the prices are all over the place from $50 deals to $400.... So I don't know ho much I should pay or how to tell if it is a real card.

 

Any help greatly appreciated.

 

Thanks

 

JCL123

Omnipath support on Debian Stretch

$
0
0

We recently bought several Dell Poweredge C6420 with Omnipath adapters series 100. They are installed with Debian 9 (Stretch). Apparently, the Intel Omni-Path Fabric Software is supported only on some versions of RHEL (and friends such as Centos) ans SUSE. Is there any way (even not supported) to install the Omni-Path Fabric software on Debian 9?

Thank you for your help.

 

Best regards

 

Dominique Delande

I350 qp 1gb

$
0
0

Can anyone tell me which port on this network card is port 0?

I219-V looses 1Gb/s connection when streaming video

$
0
0

Hi,

 

I have an ASUS Pro Gaming mainboard, i7, 16Gb ram, W10 x64 with an integrated Intel NIC I219-V

When streaming large data, for example look at video movies from Youtube, it looses it's 1Gb/s connection with the switch.

When setting the NIC on 100Mb/s then there is no problem. Also when setting the read buffer from default 256 to 512 in advanced settings, it takes a lot longer before it fails.

Latest driver from Intel installed. Another NIC from other Vendor work fine on 1Gb/s, so external hardware is not the issue.

Other older drivers, also from ASUS itself has no positive effect.

 

Whats wrong ?


Problemas adaptador Intel Gigabit 82579V Windows 10

$
0
0

Hola! cuando inico el PC, no me arranca el adaptador de red, tengo que reiniciar el ordenador para que funcione, me pasa desde la última actualización de Windows 10 (1709), antes no tenía probelma alguno.

Qué solución tiene? Gracias.

iWARP for wan/www deployment

$
0
0

We've recently bought a new server with a Intel X722 controller. Which supports iWARP.


I've read white papers about iWARP benefits (performance benefits), however I couldn't find any information about drawbacks or use of iWARP on the world wide web.

It seems that iWARP is manly targeted at servers in a LAN network which transfer lots of data. But I couldn't find any details on WAN deployments.

 

When installing the Intel Proset drivers on Windows, we noticed the following:

  • User Mode iWARP provider is unchecked by default
  • We are specifically asked if we want to enable iWARP across IP subnets
  • When installing the iWARP provider the firewall rule for public network is unchecked by default.

 

This makes me believe that there are (security) Drawbacks to enabling iWARP accross IP subnets.
However I couldn't find any information about this and the build in documentation is vague on this subject.

 

Can someone tell me if if iWARP is safe to use across the world wide web? We aim to deploy this server as web and application server and expect to run several applications and websites which will be publicly accessible.

Intel Ethernet Connection I218-LM "this device cannot start. (Code 10)"

$
0
0

I have got that problem on few laptops Dell Precision 3150. I have tried different versions of drivers, bios and clean Windows installation and problem still persist.

Failure with IGB multicast group traffic after several days

$
0
0

Setup:

Debian 8 (Jessie)

Kernel: Linux 3.16.0-4-686-pae

IGB Driver: 5.3.5.12 (the same problem occurs with the original driver from Debian, 5.0.5-k)

 

After several days (between 2-20) our systems stop receiving multicast packets for certain groups they belong to. Each of these systems has two interfaces, an IGB and e1000e which are bonded together (Bonding Mode: fault-tolerance (active-backup)). The problem only ever occurs when the IGB is the Active Interface.

 

The switch to which the IGB interface is connected, is sending the relevant multicast packets to the Interface - this has been verified by using port-mirroring on the switch. However if I run tcpdump in non-promiscuous mode, I do not see any incoming packets for that group but I do see the outgoing IGMP Group Report.

Using tcpdump in promiscuous mode will reset the interface, which immediately fixes the problem and I will see the traffic.

 

Netstat always reports active membership of the intended groups:

root@vlab-210-03:~# netstat -gn

IPv6/IPv4 Group Memberships

Interface       RefCnt Group

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

lo              1      224.0.0.1

eth1            1      224.0.0.1

bond0           1      224.0.0.251

bond0           1      224.0.0.1

bond0           1      239.255.10.10

bond0           1      239.255.10.11

bond0           4      239.110.92.1

bond0           2      224.0.0.107

bond0           3      224.0.1.129

eth0            1      224.0.0.1

 

It is only ever the groups 239.255.10.10 and 239.255.10.11 which fail, and this only occurs when using the IGB interface. Other multicast traffic functions normally.

The two affected groups are carrying a large volume of video traffic.

 

The system is still running in a failed state, so I can query it for more information.

 

Thanks,

Tom.

Updating i210 firmware with EEUPDATE has intermittent bad results

$
0
0

Our proprietary motherboards have two i210-AT NIC's.  Our vendor currently supplies the boards with both NIC NVRAM's loaded with firmware version 3.16. 

 

We are trying to update the NIC's to firmware version 3.25 in our production process using Windows PE, but have encountered a strange intermittent problem.

 

The EEUPDATE command ("EEUPDATEW64e.exe  /All /D I210_Ver.3.25_20171012.bin") appears to be successful, per this output:

 

EEUPDATE v5.30.22.00

Copyright (C) 1995 - 2017 Intel Corporation

Intel (R) Confidential and not for general distribution.

 

NIC Bus Dev Fun Vendor-Device  Branding string

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

  1   1  00  00   8086-1533    Intel(R) I210 Gigabit Network Connection

  2   2  00  00   8086-1533    Intel(R) I210 Gigabit Network Connection

 

1: EEPROM Image Version: 3.25

2: EEPROM Image Version: 3.25

 

 

After cycling power to the board, we can confirm the NIC firmware version displayed in our BIOS settings.  Usually, we will see 3.25 for both NIC's, as expected. 

 

However on some units, the 2nd NIC will still report version 3.16 in the BIOS settings.  (As I understand, the BIOS code is reading the firmware version via an offset to PCI BAR1 address.)  In this case, the EEUPDATE tool does report firmware version 3.25 is installed.  It is not clear which is correct, EEUPDATE or the BIOS.

 

We can usually repair this problem when it happens by simply rerunning the same EEUPDATE command as above.  But this should not be necessary.

 

Any idea how we are getting this contradictory result, and what to do about it?

Viewing all 1749 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>