[SOLVED] NIC missing after configuring it

larsen

Well-Known Member
Feb 28, 2020
168
20
58
We have a PVE 7.1 cluster wird just two nodes. I'm in the process of adding a SAN (total newbie here). The SAN will be connected via iSCSI using DAC.
Each Proxmox node has a separate 10Gb ethernet card with two ports.

I can see these ports as enp2s0f0 and enp2s0f1. They used to be shown in the output of "ip link".
4: enp2s0f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:8c:fa:5a:e9:38 brd ff:ff:ff:ff:ff:ff
5: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 00:8c:fa:5a:e9:39 brd ff:ff:ff:ff:ff:ff

After I configured IP addresses for both ports and activated the configuration, those are still shown in the GUI (inactive) but missing from "ip link".
I can query them, but not bring em up:
# ifquery enp2s0f0
auto enp2s0f0
iface enp2s0f0 inet static
address 10.10.10.200/24

# ifup enp2s0f0
warning: enp2s0f0: interface not recognized - please check interface configuration

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

auto enp2s0f0
iface enp2s0f0 inet static
address 10.10.10.200/24

auto enp2s0f1
iface enp2s0f1 inet static
address 10.11.10.220/24

auto vmbr0
iface vmbr0 inet static
address 192.168.120.15/24
gateway 192.168.120.1
bridge-ports eno1
bridge-stp off
bridge-fd 0

What is happening here?
 
Code:
warning: enp2s0f0: interface not recognized - please check interface configuration
warning: enp2s0f1: interface not recognized - please check interface configuration
 
Not yet. I wanted to avoid this and using ifupdown2 I understand this should be possible.
I could try it later today.
 
Turns out to be a problem with "failed to load because an unsupported SFP+ or QSFP module type was detected".
However, the workaround to "allow_unsupported_sfp=1" doesn't work, i.e. after loading the ixgbe module with that option, I still get the "unsupported" error message.

Will have to look if I can manually compile a newer version of ixgbe driver.
 
Couldn't get those cables to work. Had to switch to original Dell cables and now the interfaces are up.