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".
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:
What is happening here?
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
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
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
# 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?