One server not having interfaces named like others.

H

Howard A2 Labs

New Member
Proxmox Subscriber
Jun 9, 2025
8
1
3
Hello, I've got 4 identical Cisco UCS servers I just installed Proxmox on.

3 of them have the typical eno* names for the network interfaces.

One of them however does not for the four main 25gb links, they only gets enp* names. This prevents uniform network configurations from being functional.

This seems unusual to me as they are literally identical hardware and installs. dmesg shows the names being assigned but doesn't really have any clues as to why one doesn't act the same.

Code: 
root@pve1:~# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
2: enp64s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    altname enxd4eb6802122c
3: enp64s0f1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    altname enxd4eb6802122d
4: enp64s0f2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    altname enxd4eb6802122e
5: enp64s0f3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    altname enxd4eb6802122f
6: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    altname enp1s0f0
    altname enx488b0a446cb2
7: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    altname enp1s0f1
    altname enx488b0a446cb3
8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000

root@pve2:~# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
2: eno5: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    altname enp64s0f0
    altname enx84ebefbbcfc8
3: eno6: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    altname enp64s0f1
    altname enx84ebefbbcfc9
4: eno7: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    altname enp64s0f2
    altname enx84ebefbbcfca
5: eno8: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    altname enp64s0f3
    altname enx84ebefbbcfcb
6: eno1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    altname enp1s0f0
    altname enx488b0a447c52
7: eno2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    altname enp1s0f1
    altname enx488b0a447c53
8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
 
If you have used another pcie slot or another pcie card in your server then network interfaces can be named differently.
To have your interface names uniform you can (and should) pin your network interface names. On a kernel update or when adding additional pcie hardware your interface names could change and you loose network connectivity.

Just be cautios with the chosen name, it should not be the same as the kernel would choose otherwise you could get name conflicts.
https://pve.proxmox.com/wiki/Network_Configuration go to manual method, systemd link file example.

In PVE 9 there is a pve-network-interface-pinning tool to help with that.
 
You must log in or register to reply here.
Top Bottom