Hi,

I recently bought a (second hand) Intel X540-T2 network adapter for my DIY-NAS (my workstation already has one).

Unfortunately, it seems to have problems booting on my ASUS Maximus 6 Gene board (Post code 55). I've narrowed down the problem to Dell's memory mapping of the firmware. It is a known problem with Dell X540-T2's and the Intel Z87/Z97 chipset when using 4 DIMMs. It can be fixed by removing on DIMM from the board, after which the board POSTs and boots without any problems. The Dell X540 does boots without any issues on the H110 and Z370 chipsets, even with all four DIMM slots populated.

The card I intended to use for my workstation is a passive one (Intel OEM) and this one boots just fine of my ASUS M6G board. Considering both NICs have an identical board (aside from the fan header on the Dell one), I suspect that the Dell card will still work when I flash it with the unmodified Intel firmware, correct? This should solve the EFI memory mapping problem that I encounter on my NAS.

Is what I'm trying to achieve possible? Or should I just get rid of the Dell X540 and buy a new OEM Intel card? I got the dell really cheap - and genuine X540's often go for over $300 used (not counting the potentially compromised chinese knock-offs)

I've done a bit of Google-Fu, but couldn't find the native Intel firmware anywhere.

I'm trying to install the Proset driver and utilities but the installation says it cannot find any Intel adapters.

Windows 10 found the adapter just fine and installed the Windows Update version of the drivers but I was hoping to experiment with teaming on this system.

Is this board fully supported?

Windows 10 Build 1709

Hi,

Problem: No MDC/MDIO signal

10G BASE –T PHY: Intel, X557-AT

Flash Image:

1. BDXDE_KR_BACKPLANE_LED_LO_NO_MNG_1.13v02_800006D1.bin

2. BDXDE_10GBASET_NO_MNG_1.13v02_800006B7.bin

===========Eth Info==================

root@genericx86-64:/dni# ethtool -i eth1

driver: ixgbe

version: 5.0.0-k

firmware-version: 0x800006a8

expansion-rom-version:

bus-info: 0000:04:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

===========Eth Info End==================

04:00.0 Ethernet controller: Intel Corporation Ethernet Connection X552 10 GbE Backplane

04:00.1 Ethernet controller: Intel Corporation Ethernet Connection X552 10 GbE Backplane

Description:

We try to do MDI single r/w through MSCA(0x0000425c) and MSRWD(0x00004260).

The rule and steps is shown below

04:00.0   [Base address]   + [offset]      [32 bits] [value]

devmem 0x383fff400000+0x0000425c 32 0x501dc501           //Address cycle    PHYAD = 0x00

devmem 0x383fff400000+0x00004260 32 0x00002001          //Test Mode 1

devmem 0x383fff400000+0x0000425c 32 0x541dc501          //Write operation

Is it correct?

We also try to use the tool of "lanconf64e" doing IEEE Tests, but we still cannot got MDC/MDIO signal.

Then, we upgrade flash to BDXDE_10GBASET_NO_MNG_1.13v02_800006B7.bin.

However, the situation is the same.

Another question is when we use BDXDE_10GBASET_NO_MNG_1.13v02_800006B7.bin, the eth cannot link up.

If we change the image to XXX_BACKPLANE..., it can link up in 1G. But, 10G doesn't work...

Why we can't get MDC/MDIO signal?

In backplane mode, why X557 only link up in 1G?

Could you give us some suggestions?

Thanks

I work in IT at a corporation where almost all of our current computers have the Intel Ethernet Connection l218-LM network adapters. I have seen 5 computers in the last 2 months come up with the error where this network suddenly stops working and produces Error Code 10: this device cannot start. I have searched high and low for a solution, and the ULP enable/disable utility is the only thing I haven't tried yet. Can someone please send the utility to me?

I have a Cougar Park WAV500 D3.1 Gateway which is in bridge mode. I want to revert it back to Gateway mode. What is the process to do a factory reset?

Hello

We are using following device on a HP RMS server.

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

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

We bind the two ethernet ports to a virtual machine with PCIe pass-through mode.  Then in the VM, we use DPDK to rx/tx packets over them.

However, we only can tx packets out, but failed to rx any packets. 

What's the possible matter? Is this PCIe pass-through + DPDK 16.11 mode can not work with X710 (i40e driver)? In the past, this mode works with Intel 82599 chip.

Now we did not change the mode, and  the application code we used to configure port/queue of X710 is just exactly the same as the one we used to configure 82599 port.

That's to say, same working way, same application code, we just replaced our NIC cards  then it works well for 82599 (driver ixgbe), but not work for X710.

Can you suggest how to solve this issue? Following is the driver info of i40e we used.

driver: i40e

version: 1.6.27-k

firmware-version: 5.60 0x800033b0 1.1752.0

expansion-rom-version:

bus-info: 0000:00:0e.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

What else information do you need so that you can help to identify the issue? Thanks.

Xiao Xiaohong from Nokia

My mail: xiaohong.xiao@nokia-sbell.com

I am bringing up a X540-BT2 design and noticed that shortly after reset that the SMBus Clock and Data line are driven low.

The PCIe interface is not being driven - no reference clock.

Is this an issue that has been seen by any other designers?

i want to enable Wake On Lan function

i am using :

OS : Windows 10 pro x64 Version 1709 OS 16299.192

MotherBoard : ASUS ROG STRIX X299-E Gaming

Network Adapter : Intel(R) Ethernet Connection (2) I219-V 12.15.23.8 (by SSU.exe)

i enable wake by pci-e on bios

disable fast boot

Using UEFI boot
but when i check about inter ethernet connection (2) I219-V , Wake On Lan function is N/A

is I219-V not support WOL or something i did wrong?

P.S Realtek 8822BE Wireless LAN 802.11ac PCI-E NIC can WOL but this need WIFI

and i am not sure can it really WOL

so i am asking for I219

thank you

Does the X540-T2 NIC supported on Windows Server 2016?

We have two Hyper-V 2016 servers in core mode, both have a pair of Intel X710 Adapters. Both have Hyper-V role enabled and the latest Intel firmware, drivers and Windows patches.

Using the PowerShell commands I see that the performance profile is "Standard server".  Normally if Hyper-V is detected the performance profile is automatically set to 'Virtualization' by the driver however this is not the case here.

I have tried to set this using this PowerShell command:

Set-IntelNetAdapterSetting -Name *X710* -RegistryKeyword PerformanceProfile -RegistryValue 5

But an error is thrown:

Set-IntelNetAdapterSetting : The setting could not be modified because the specified value is invalid for this device or setting.

Any suggestions please?

Hi,

I have a VM using SRIOV interfaces based on X710 interfaces. This VM is connected to a physical router through the VF.

I would like to enable vlan tagging on the VM.

I can ping the physical router from the VM if I'm not using VLAN tagging on the interface.

When I add VLAN tagging on the interface (on the VM and on the physical router), the network connectivity is broken.

The physical router correctly receives the packets/frames from the VM.

The VM receives the packets/frames but without a VLAN tag, it seems that the VLAN tag has been stripped.

Here are some informations on my setup:

[root@SLI-SRV3 sysadmin]# ethtool -i eth1

driver: i40e

version: 1.6.27-k

firmware-version: 6.00 0x800034e6 18.3.6

expansion-rom-version:

bus-info: 0000:19:00.0

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: yes

[root@SLI-SRV3 sysadmin]# ip link show eth1

3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq portid 246e967eaabe state UP mode DEFAULT qlen 1000

    link/ether 24:6e:96:7e:aa:be brd ff:ff:ff:ff:ff:ff

    vf 0 MAC 52:54:00:5d:6a:60, spoof checking on, link-state auto, trust off

VIRSH network config:

    <interface type='hostdev' managed='yes'>

      <mac address='52:54:00:5d:6a:60'/>

      <driver name='vfio'/>

      <source>

        <address type='pci' domain='0x0000' bus='0x19' slot='0x02' function='0x0'/>

      </source>

      <alias name='hostdev0'/>

      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>

    </interface>

Any idea about what could be the issue ?

Thanks,

Stephane

Hello;

I have a Box (supermicro) with:

S.O :    FreeBSD 11.1-STABLE (FreeNAS)

NIC: - Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02).

- Intel(R) Ethernet Connection XL710/X722 Driver, Version - 1.7.12-k

- dev.ixl.0.fw_version: fw 5.0.40043 api 1.5 nvm 5.05 etid 80002a43 oem 1.261.0

I have issues with the connection  Flapping on the interfaces 10G and a lot of messages "ixl0: Malicious Driver Detection event 2 on TX queue 2, pf number 0"

I m trying to Upgrade the Firmware to 6.0.1; but the procedure (./nvmupdate64e) says:

Num Description                               Ver. DevId S:B    Status

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

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

                                                                                                             available

02) Intel(R) Ethernet Controller X710 for     5.05  1572 00:002     Update not

    10GbE SFP+                                                                                  available

Tool execution completed with the following status: Device not found.

Please tell me the correct way to write a new hardware MAC address and load firmware into a blank Intel 82574L Gigabit Ethernet Controller Chip under Windows 10 Embedded.

Windows would be running on a Qseven module board, and the 82574 chip is on an adapter module board attached to the Qseven module.

I have the same issue with FreeNAS 11.1-U1. I created a bug report for FreeNAS and they are looking into it, but they were a little perplexed that a newer driver for FreeBSD was available but wasn't imported into the FreeBSD repository even though Intel is supposed to have FreeBSD committers.

02) Intel(R) Ethernet Converged Network       5.05  1572 00:005 Update

    Adapter X710-2                                              available

I am updating the firmware now to 6.01... But I am fairly certain that will not work. From what I can see in the bug tracking and googling, this has been going on for a while and either keeps coming back or never gets fixed.

From what I can see, the responsibility is on Intel to fix this for good and get the committers to imported the latest drivers in the FreeBSD head.

Intel, can we please get a permanent fix please?

Hello,

my question is directed to Intel NIC developers - we (CDN77) are using your X520-DA2 cards in thousands of servers - we have discovered that two different X520-DA2 NICs we have in our network do use the SAME MAC address.

The conflicting MAC is 00:1b:21:bc:32:15.

Is this something what 'can happen from time to time'? It would be a real flaw in the design - this makes makes me think the duplicate MAC is caused by some Chinese copy of the genuine Intel NIC.

You can imagine what mess can this cause.

If it helps, I can send more detail information regarding both NICs.

Thank you!

Hi,

We are working on a i210 flash-less design in which the i210 operates in Serdes/1000Base-BX mode attached to an external optical module. We have already validated the design as it has passed all acceptance tests.

Our application requires changing the value of one register (Fiber Specific Control Register 2). This that can only be done from the driver. We have successfully tested it under Linux. We would like to make it also work under Windows 7 Embedded Edition. Is it possible for us to have access to the source code of the Windows version of the driver?

Thanks in advance.

Best regards,

Manuel

Hi,

I am observing a strange issue with i354 when auto-negotiation is turned off.

The device I have has 6 ethernet ports. Port 1 and 2 are based on i210 and port

3 to 6 are based on i354 (connected thru an external PHY). The CPU is Atom

Rangeley (4 core).

I have connected ports 3 and 4 back to back with an external cable. When the

link is forced to 100M/Full duplex with auto-negotiation off on both the ports,

the link does not come up.

Whereas the link comes up fine when eth3 (i354) and eth1 (i210) are connected

back to back and forced to 100M/Full duplex with auto-negotiation off.

This issue is seen with linux kernel (ubuntu 14.04).

Is this a known issue ?

Following are logs when running the test using ethtool from linux

admin@Ananda-Desk:~$ lspci | grep Ethernet

00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth2

00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth3

00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth4

00:14.3 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev

03)  - eth5

01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection

(rev 03) - eth0

02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection

(rev 03) - eth1

admin@Ananda-Desk:~$ ethtool -i eth3

driver: igb

version: 5.2.13-k

firmware-version: 0.0.0

bus-info: 0000:00:14.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: yes

supports-register-dump: yes

supports-priv-flags: no

[Force 100M/Full on eth3]

admin@Ananda-Desk:~$ sudo ethtool -s eth3 autoneg off duplex full speed 100

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes

admin@Ananda-Desk:~$ ethtool eth4

Settings for eth4:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: Yes

        Speed: 100Mb/s

        Duplex: Half

        Port: Twisted Pair

        PHYAD: 2

        Transceiver: internal

        Auto-negotiation: on

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes

[Force 100M/Full on eth4]

admin@Ananda-Desk:~$ sudo ethtool -s eth4 autoneg off duplex full speed 100

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ ethtool eth4

Settings for eth4:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: Unknown!

        Duplex: Unknown! (255)

        Port: Twisted Pair

        PHYAD: 2

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: no <<<<<<<<<<<<<<

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: Unknown!

        Duplex: Unknown! (255)

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: no <<<<<<<<<<<

[Connect cables between eth1 and eth3]

[Force 100M/Full on eth1]

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ sudo ethtool -s eth1 autoneg off duplex full speed 100

admin@Ananda-Desk:~$

admin@Ananda-Desk:~$ ethtool eth1

Settings for eth1:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: on (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes <<<<<<<<<<<<

admin@Ananda-Desk:~$ ethtool eth3

Settings for eth3:

        Supported ports: [ TP ]

        Supported link modes:   10baseT/Half 10baseT/Full

                                100baseT/Half 100baseT/Full

                                1000baseT/Full

        Supported pause frame use: Symmetric

        Supports auto-negotiation: Yes

        Advertised link modes:  Not reported

        Advertised pause frame use: Symmetric

        Advertised auto-negotiation: No

        Speed: 100Mb/s

        Duplex: Full

        Port: Twisted Pair

        PHYAD: 1

        Transceiver: internal

        Auto-negotiation: off

        MDI-X: off (auto)

Cannot get wake-on-lan settings: Operation not permitted

        Current message level: 0x00000007 (7)

                               drv probe link

        Link detected: yes <<<<<<<<<<<<

Hello,

Can I please ask clarifications on XL710 on VLAN steering. I have few questions regarding it on top of what was asked before. Really appreciate for your valuable input please

1. 7.4.8.4 "VEB/VEPA Switching Algorithm" states that filtering happens by MAC+VLAN. It is impossible to perform filtering by VLAN only, as I understand it is HW limitation.

XL710 has something called "7.4.8.2 S-comp Forwarding Algorithm" which looks like exactly what we want. It does forwarding of packets to specific VSI based on S-tag. S-tag is a part of "7.4.9.5.5.1 Add VSI (0x0210)" command. I guess we can configure several VSIs for expected S-tags. Can you help us understand how to use this algorithm please?

As I understood "port virtualizer" (7.4.2.4.3 "Cascaded VEB and port virtualizers") supposed to be configured to use this switching algorithm. In i40e driver (kernel or DPDK) I do not see anything related to configuration of "port virtualizers", except "i40e_aq_add_pvirt" function which is not used anywhere.

Is it possible to configure "port virtualizer" with existing latest i40e driver?

Another question is about "i40e_aq_set_vsi_uc_promisc_on_vlan" function in i40e driver (7.4.9.5.9.5 "Set VSI Promiscuous Modes"). It enables promiscuous mode for unicast packets with specific VLAN, so all packets with that VLAN will be replicated to configured VSI. In XL710 datasheet I`ve found that it works only in "Cloud VEB algorithm" (7.4.8.6). Can we somehow enable this algorithm with existing i40e drivers?

Thannk you so much

Hi,

I am observing a strange issue with i354 when auto-negotiation is turned off.

The device I have has 6 ethernet ports. Port 1 and 2 are based on i210 and port

3 to 6 are based on i354 (connected thru an external PHY). The CPU is Atom

Rangeley (4 core).

I have connected ports 3 and 4 back to back with an external cable. When the 
link is forced to 100M/Full duplex with auto-negotiation off on both the ports, 
the link does not come up.

Whereas the link comes up fine when eth3 (i354) and eth1 (i210) are connected 
back to back and forced to 100M/Full duplex with auto-negotiation off.

This issue is seen with DPDK (16.04) and also linux kernel (ubuntu 14.04).

Is this a known issue ?

Following are logs when running the test using ethtool from linux

admin@Ananda-Desk:~$ lspci | grep Ethernet
00:14.0 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)  - eth2
00:14.1 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)  - eth3
00:14.2 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)  - eth4
00:14.3 Ethernet controller: Intel Corporation Ethernet Connection I354 (rev 
03)  - eth5
01:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection 
(rev 03) - eth0
02:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection 
(rev 03) - eth1

admin@Ananda-Desk:~$ ethtool -i eth3
driver: igb
version: 5.2.13-k
firmware-version: 0.0.0
bus-info: 0000:00:14.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: no

[Force 100M/Full on eth3]

admin@Ananda-Desk:~$ sudo ethtool -s eth3 autoneg off duplex full speed 100

admin@Ananda-Desk:~$ ethtool eth3
Settings for eth3:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: off
        MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

admin@Ananda-Desk:~$ ethtool eth4
Settings for eth4:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Half
        Port: Twisted Pair
        PHYAD: 2
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: on (auto)
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes


[Force 100M/Full on eth4]

admin@Ananda-Desk:~$ sudo ethtool -s eth4 autoneg off duplex full speed 100
admin@Ananda-Desk:~$
admin@Ananda-Desk:~$ ethtool eth4
Settings for eth4:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: No
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 2
        Transceiver: internal
        Auto-negotiation: off
        MDI-X: on (auto)
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no       <<<<<<<<<<<<<<
admin@Ananda-Desk:~$ ethtool eth3
Settings for eth3:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: No
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: off
        MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: no    <<<<<<<<<<<



[Connect cables between eth1 and eth3]
[Force 100M/Full on eth1]

admin@Ananda-Desk:~$
admin@Ananda-Desk:~$ sudo ethtool -s eth1 autoneg off duplex full speed 100
admin@Ananda-Desk:~$
admin@Ananda-Desk:~$ ethtool eth1
Settings for eth1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: off
        MDI-X: on (auto)
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes <<<<<<<<<<<<

admin@Ananda-Desk:~$ ethtool eth3
Settings for eth3:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supported pause frame use: Symmetric
        Supports auto-negotiation: Yes
        Advertised link modes:  Not reported
        Advertised pause frame use: Symmetric
        Advertised auto-negotiation: No
        Speed: 100Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: off
        MDI-X: off (auto)
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes  <<<<<<<<<<<<


Thanks,
Ananda

Hi,

I have a XL710QDA2 40GB NIC and I also have the INTEL Ethernet QSFP+ cable. I have two problems:

1- This NIC does not get IPV4 address automatically. What should I do to force it to get IPV4 address upon boot?

2- I have tried to send packets through this NIC to other devices, but it can not forward any packet (IPV4, IPV6, or even broadcast packets). How can I enable the packet forwarding and receiving of this NIC?

Thanks for your time. I would appreciate it if you could help me out.

Best,

Marjan