[SOLVED] Proxmox Renaming Interfaces: rename1 rename2 rename3 rename4

[oguruma]

Solution: The BIOS on my Supermicro X9LN4f+ motherbord was out of date by a version. Updating to BIOS version 3.3 fixed the problem, and now my interfaces are named appropriately (eno1/eno2 etc.).


I have a Motherboard with 4 NICs. I want to create 2 separate VMs and give each of those VMs their own NIC (each NIC will be placed in its own network segment via my router).

I cannot see how to manage the individual NICs in the Proxmox UI.

All I see is "rename 1" "rename 2" etc and nowhere do I see the motherboard's NICs.

How do I give each VM its own dedicated interface?

 

[Michael Dupree]

Create a bridge for each dedicated network you want to create (it doesn't matter if you have one VM or many). Add the VM and the specific network interface you want to use to the bridge.

I think that should work anyways.

 

[oguruma]

Create a bridge for each dedicated network you want to create (it doesn't matter if you have one VM or many). Add the VM and the specific network interface you want to use to the bridge.

I think that should work anyways.

I see how I can create a bridge, and I see how to add the VM to the bridge, but what I don't see is how to add the nic to that bridge...

 

[Stoiko Ivanov]

All I see is "rename 1" "rename 2" etc and nowhere do I see the motherboard's NICs.

that seems like it could be a problem with the NIC - check the journal since booting (`journalctl -b`) and `dmesg` for messages from the NIC / their driver

I hope this helps!

 

[oguruma]

that seems like it could be a problem with the NIC - check the journal since booting (`journalctl -b`) and `dmesg` for messages from the NIC / their driver

I hope this helps!

I found the following in the journal/dmesg.

Nothing that indicates to me what the actual problem is, though...

May 11 01:19:19 pve1 kernel: igb 0000:07:00.1: added PHC on eth1
May 11 01:19:19 pve1 kernel: igb 0000:07:00.1: Intel(R) Gigabit Ethernet Network Connection
May 11 01:19:19 pve1 kernel: igb 0000:07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:86:9e:b5
May 11 01:19:19 pve1 kernel: igb 0000:07:00.1: eth1: PBA No: 105900-000
May 11 01:19:19 pve1 kernel: igb 0000:07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
May 11 01:19:19 pve1 kernel: igb 0000:07:00.2: added PHC on eth2
May 11 01:19:19 pve1 kernel: igb 0000:07:00.2: Intel(R) Gigabit Ethernet Network Connection
May 11 01:19:19 pve1 kernel: igb 0000:07:00.2: eth2: (PCIe:5.0Gb/s:Width x4) 00:25:90:86:9e:b6
May 11 01:19:19 pve1 kernel: igb 0000:07:00.2: eth2: PBA No: 105900-000
May 11 01:19:19 pve1 kernel: igb 0000:07:00.2: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
May 11 01:19:19 pve1 kernel: igb 0000:07:00.3: added PHC on eth3
May 11 01:19:19 pve1 kernel: igb 0000:07:00.3: Intel(R) Gigabit Ethernet Network Connection
May 11 01:19:19 pve1 kernel: igb 0000:07:00.3: eth3: (PCIe:5.0Gb/s:Width x4) 00:25:90:86:9e:b7
May 11 01:19:19 pve1 kernel: igb 0000:07:00.3: eth3: PBA No: 105900-000
May 11 01:19:19 pve1 kernel: igb 0000:07:00.3: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
May 11 01:19:19 pve1 kernel: igb 0000:07:00.3 eno1: renamed from eth3
May 11 01:19:19 pve1 kernel: usb 1-1.3: new full-speed USB device number 3 using ehci-pci
May 11 01:19:19 pve1 kernel: igb 0000:07:00.0 rename2: renamed from eth0
May 11 01:19:19 pve1 kernel: usb 2-1.2: new high-speed USB device number 3 using ehci-pci
May 11 01:19:19 pve1 kernel: igb 0000:07:00.2 rename4: renamed from eth2
May 11 01:19:19 pve1 kernel: igb 0000:07:00.1 rename3: renamed from eth1
d

dmesg

 igb 0000:07:00.1: added PHC on eth1
[    2.702295] igb 0000:07:00.1: Intel(R) Gigabit Ethernet Network Connection
[    2.702297] igb 0000:07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:86:9e:b5
[ 2.702373] igb 0000:07:00.1: eth1: PBA No: 105900-000
[    2.702375] igb 0000:07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[    2.758087] igb 0000:07:00.2: added PHC on eth2
[    2.758088] igb 0000:07:00.2: Intel(R) Gigabit Ethernet Network Connection
[    2.758090] igb 0000:07:00.2: eth2: (PCIe:5.0Gb/s:Width x4) 00:25:90:86:9e:b6
[ 2.758164] igb 0000:07:00.2: eth2: PBA No: 105900-000
[    2.758165] igb 0000:07:00.2: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[    2.814200] igb 0000:07:00.3: added PHC on eth3
[    2.814202] igb 0000:07:00.3: Intel(R) Gigabit Ethernet Network Connection
[    2.814203] igb 0000:07:00.3: eth3: (PCIe:5.0Gb/s:Width x4) 00:25:90:86:9e:b7
[ 2.814277] igb 0000:07:00.3: eth3: PBA No: 105900-000
[    2.814279] igb 0000:07:00.3: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[    2.815981] igb 0000:07:00.3 eno1: renamed from eth3
[    2.869578] usb 1-1.3: new full-speed USB device number 3 using ehci-pci
[    2.877866] igb 0000:07:00.0 rename2: renamed from eth0
[    2.885588] usb 2-1.2: new high-speed USB device number 3 using ehci-pci
[    2.917849] igb 0000:07:00.2 rename4: renamed from eth2
[    2.941797] igb 0000:07:00.1 rename3: renamed from eth1

 

[Stoiko Ivanov]

hmm - this is sometimes due to a manual change in the netdev link files from systemd

please post the output of:
* `find /etc/udev`
* `find /etc -iname '*.link'
* `find /lib/systemd -iname '*.link'

 

[oguruma]

hmm - this is sometimes due to a manual change in the netdev link files from systemd

please post the output of:
* `find /etc/udev`
* `find /etc -iname '*.link'
* `find /lib/systemd -iname '*.link'

find /etc/udev returned

/etc/udev
/etc/udev/hwdb.d
/etc/udev/rules.d
/etc/udev/rules.d/60-bridge-network-interfaces.rules
/etc/udev/udev.conf

`find /etc -iname *.link didn't return anything

find /lib/systemd -iname *.link returned

/lib/systemd/network/99-default.link

 

[Stoiko Ivanov]

looks ok so far...

what's the content of:
/lib/systemd/network/99-default.link

 

[oguruma]

looks ok so far...

what's the content of:
/lib/systemd/network/99-default.link

[Link]

NamePolicy=keep kernel database onboard slot path
MACAddressPolicy=persistent

After doing some googling, isn't there supposed to be a /etc/udev/rules.d/70-persistent-net.rules file? There is no such file on this box...

Also, I booted this box from a Proxmox 5.4 and also a 6.1 USB drive, and it also wants to rename the NICs when booting from those, as well.

 

[Stoiko Ivanov]

Also, I booted this box from a Proxmox 5.4 and also a 6.1 USB drive, and it also wants to rename the NICs when booting from those, as well.

hmm - any available firmware updates (mainboard, NIC, BIOS, UEFI,....) - sometimes they fix those issues.

isn't there supposed to be a /etc/udev/rules.d/70-persistent-net.rules file?

not anymore - see https://wiki.debian.org/NetworkInterfaceNames , https://www.debian.org/releases/stable/amd64/release-notes/ch-information.html

 

[oguruma]

hmm - any available firmware updates (mainboard, NIC, BIOS, UEFI,....) - sometimes they fix those issues.


not anymore - see https://wiki.debian.org/NetworkInterfaceNames , https://www.debian.org/releases/stable/amd64/release-notes/ch-information.html

I'll be doing a BIOS update shortly. Looks like there is a new version available (I probably need to do it either way, since my current BIOS is pre-Spectre).

I will note, however, that I booted this machine off a Ubuntu Live USB drive and it names the NICs eno1 (instead of eth0?) eth1 eth2 and eth3.

 

[oguruma]

Just an update: I updated the BIOS on the motherboard and re-installed Proxmox (I don't know if that was necessary) and now the interfaces are named appropriately.

 

[Stoiko Ivanov]

Thanks for coming back and reporting your success!

 

[sidereus]

After installing Proxmox 6.3 I also got these infamous rename3, rename4, etc. again.
To fix it I had to edit the file /usr/lib/systemd/network/99-default.link

[Link]
#NamePolicy=keep kernel database onboard slot path
NamePolicy=path
MACAddressPolicy=persistent

Aftter apt dist-upgrade it appeared rewritten again, so edited it again. Now all is fine with interfaces names:

2: enp130s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:20:c2:a0 brd ff:ff:ff:ff:ff:ff
3: enp6s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:56:ad:34 brd ff:ff:ff:ff:ff:ff
4: enp130s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 90:e2:ba:20:c2:a1 brd ff:ff:ff:ff:ff:ff
5: enp6s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:56:ad:35 brd ff:ff:ff:ff:ff:ff
6: enp7s0f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:56:ad:34 brd ff:ff:ff:ff:ff:ff
7: enp7s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
    link/ether 0c:c4:7a:56:ad:37 brd ff:ff:ff:ff:ff:ff

lspci -tv view of this 4 ports ethernet board, where was 2 "rename" interfaces:

 \-[0000:00]-+-00.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2
             +-01.0-[01]--
             +-02.0-[02]--
             +-02.3-[03]----00.0  Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller
             +-03.0-[04-07]----00.0-[05-07]--+-01.0-[06]--+-00.0  Intel Corporation 82576 Gigabit Network Connection
             |                               |            \-00.1  Intel Corporation 82576 Gigabit Network Connection
             |                               \-02.0-[07]--+-00.0  Intel Corporation 82576 Gigabit Network Connection
             |                                            \-00.1  Intel Corporation 82576 Gigabit Network Connection

Seems that the system didn't understand 2 NICs at the same slot and generated "rename" names for it.