Intel X520 not showing correct interface name in linux

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

mauzilla

New Member
Aug 11, 2022
16
5
3
Not sure if this is normal, but I cannot get my network to work on a fibre card. Mine shows the following after modprobe driver restart:

23: side-9684-eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master ovs-system state DOWN mode DEFAULT group default qlen 1000
link/ether a0:36:9f:cc:56:c4 brd ff:ff:ff:ff:ff:ff
24: side-9825-eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop master ovs-system state DOWN mode DEFAULT group default qlen 1000
link/ether a0:36:9f:cc:56:c6 brd ff:ff:ff:ff:ff:ff

Normally interfaces are named differently. Looking at the below, I also cannot seem to find eth2 anywhere:

[352864.492373] ixgbe 0000:08:00.0 0000:08:00.0 (uninitialized): ixgbe_check_options: FCoE Offload feature enabled
[352864.492378] ixgbe 0000:08:00.0 0000:08:00.0 (uninitialized): allow_unsupported_sfp Enabled
[352864.523551] ixgbe 0000:08:00.0 0000:08:00.0 (uninitialized): WARNING: Intel (R) Network Connections are quality tested using Intel (R) Ethernet Optics. Using untested modules is not supported and may cause unstable operation or damage to the module or the adapter. Intel Corporation is not responsible for any harm caused by using untested modules.
[352864.660901] ixgbe 0000:08:00.0: Multiqueue Enabled: Rx Queue count = 12, Tx Queue count = 12 XDP Queue count = 0
[352864.662954] ixgbe 0000:08:00.0: 32.000 Gb/s available PCIe bandwidth (5 GT/s x8 link)
[352864.663279] ixgbe 0000:08:00.0 eth2: MAC: 2, PHY: 19, SFP+: 5, PBA No: G73129-008
[352864.663282] ixgbe 0000:08:00.0: a0:36:9f:cc:56:c4
[352864.663297] ixgbe 0000:08:00.0 eth2: Enabled Features: RxQ: 12 TxQ: 12 FdirHash
[352864.665386] ixgbe 0000:08:00.0 eth2: Intel(R) 10 Gigabit Network Connection
[352864.666229] ixgbe 0000:08:00.1 0000:08:00.1 (uninitialized): ixgbe_check_options: FCoE Offload feature enabled
[352864.713659] ixgbe 0000:08:00.0 side-9684-eth2: renamed from eth2
[352865.965204] ixgbe 0000:08:00.1: Multiqueue Enabled: Rx Queue count = 12, Tx Queue count = 12 XDP Queue count = 0
[352865.967291] ixgbe 0000:08:00.1: 32.000 Gb/s available PCIe bandwidth (5 GT/s x8 link)
[352865.967616] ixgbe 0000:08:00.1 eth2: MAC: 2, PHY: 1, PBA No: G73129-008
[352865.967619] ixgbe 0000:08:00.1: a0:36:9f:cc:56:c6
[352865.967639] ixgbe 0000:08:00.1 eth2: Enabled Features: RxQ: 12 TxQ: 12 FdirHash
[352865.969720] ixgbe 0000:08:00.1 eth2: Intel(R) 10 Gigabit Network Connection
[352866.018764] ixgbe 0000:08:00.1 side-9825-eth2: renamed from eth2
 

ericloewe

Active Member
Apr 24, 2017
299
136
43
30
What sort of system is this? Why is the weird naming a problem for you, have you enabled either link?
 

mauzilla

New Member
Aug 11, 2022
16
5
3
Dell R320 with XCP 8.2

First major issue is that the interface is renamed after each server / driver reload.

I have brought the interface up manually and assigned an IP address, however, I cannot ping any IP on the network.

Here is some info:

[16:33 xen10test ixgbe]# ethtool side-9684-eth2
Settings for side-9684-eth2:
Supported ports: [ FIBRE ]
Supported link modes: 10000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: 10000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 0
Transceiver: internal
Auto-negotiation: off
Supports Wake-on: d
Wake-on: d
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes

IP given is 10.1.3.241 with the firewall gateway being 10.1.3.1 (not that it would matter as I cannot even ping another IP on the same network 10.1.3.4)

Trying to ping IP I get:

[16:35 xen10test ixgbe]# ping 10.1.3.4
PING 10.1.3.4 (10.1.3.4) 56(84) bytes of data.
From 10.1.3.241 icmp_seq=1 Destination Host Unreachable
From 10.1.3.241 icmp_seq=2 Destination Host Unreachable
From 10.1.3.241 icmp_seq=3 Destination Host Unreachable
From 10.1.3.241 icmp_seq=4 Destination Host Unreachable
From 10.1.3.241 icmp_seq=5 Destination Host Unreachable
From 10.1.3.241 icmp_seq=6 Destination Host Unreachable

It's pinging from the correct interface obviously but cannot seem to get any network traffic. I also cannot ping the actual switch which is on the same network. Not sure how to further troubleshoot
 

mauzilla

New Member
Aug 11, 2022
16
5
3
XCP-ng using OVS? Is this inside a Linux VM?
Hi Sean, no this is for the hypervisor itself. I've got an Intel 10GB but my SFP+ modules are not compatible. Intel has a "unsupported" flag which I am trying to add, but I'm battling to get it working and suspect something is going wrong in the tech stack. I am installing Ubuntu now on the same machine to see if I can reproduce, if Ubuntu works I will open a support ticket with XCP
 

Sean Ho

seanho.com
Nov 19, 2019
775
359
63
Vancouver, BC
seanho.com
The side-9684-eth2 interface alias suggests OVS wants to take over all the NICs; you might need to create a virtual interface in OVS for the host rather than try to use the raw eth2 interface (some would consider it a security feature that the host doesn't have direct network access by default).

Ubuntu has its own complexity with netplan, but it should be easier at least to test out the ixgbe.allow_unsupported_sfp module flag.