[PVE-User] Interface not renamed...

[PVE-User] Interface not renamed...

[Marco Gaiarin]

I've upgraded a server from PVE7 to PV8, and (as expected) some interfaces
get renamed.

Really, i've upgraded TWO identical server (Dell T440), and one went
flawlessy, the other... and interface get NOT renamed, remain 'eth1':

 root@svpve2:~# ip link show eth1
 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
     link/ether 5c:6f:69:0f:99:79 brd ff:ff:ff:ff:ff:ff
     altname enp1s0f1

I've tried:

 root@svpve2:~# ip -force link set dev eth1 name ens1f1
 RTNETLINK answers: File exists

and:

 root@svpve2:~# ip link property add dev eth1 altname ens1f1
 RTNETLINK answers: File exists


but nothing work; there's something i can do whithout rebooting the server?


Thanks.

PS: port is on a dual-port pcie card, the other port on the same card works as expected:

 root@svpve2:~# ip link show ens1f0
 2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
     link/ether f4:ee:08:24:3a:ff brd ff:ff:ff:ff:ff:ff permaddr 5c:6f:69:0f:99:78
     altname enp1s0f0

-- 



_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Interface not renamed...

[Falko Trojahn]

Marco Gaiarin schrieb am 21.05.25 um 14:28:
 >
 > I've upgraded a server from PVE7 to PV8, and (as expected) some 
interfaces
 > get renamed.
 >
 > Really, i've upgraded TWO identical server (Dell T440), and one went
 > flawlessy, the other... and interface get NOT renamed, remain 'eth1':
Hi Marco,

you surely don't have any udev rules for this interface
e.g. left over from former system?

Cheers
Falko

_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Interface not renamed...

[Roland via pve-user]

[-- Attachment #1: Type: message/rfc822, Size: 9148 bytes --]

From: Roland <devzero@web.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>, Falko Trojahn <falko.trojahn@gmail.com>, Marco Gaiarin <gaio@lilliput.linux.it>
Subject: Re: [PVE-User] Interface not renamed...
Date: Fri, 23 May 2025 12:23:40 +0200
Message-ID: <d1f0f4d4-1589-4d35-bc6b-32194cf97721@web.de>

hello,

iirc, that can be a matter of the bios version installed.

https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf

roland


Am 23.05.25 um 12:16 schrieb Falko Trojahn:
> Marco Gaiarin schrieb am 21.05.25 um 14:28:
> >
> > I've upgraded a server from PVE7 to PV8, and (as expected) some 
> interfaces
> > get renamed.
> >
> > Really, i've upgraded TWO identical server (Dell T440), and one went
> > flawlessy, the other... and interface get NOT renamed, remain 'eth1':
> Hi Marco,
>
> you surely don't have any udev rules for this interface
> e.g. left over from former system?
>
> Cheers
> Falko
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Interface not renamed...

[Marco Gaiarin]

Mandi! Falko Trojahn
  In chel di` si favelave...

> you surely don't have any udev rules for this interface
> e.g. left over from former system?

No, i've not altered in any way udev rules...


Mandi! Roland
  In chel di` si favelave...

> iirc, that can be a matter of the bios version installed.

> https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf

We have upgarded 8 identical servers, upgrading to identical bios version;
this is the only one that have this trouble.

Anyway, i've found some more info:

 root@svpve2:~# ip link show | egrep '[0-9]+: '
 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
 2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
 3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000
 4: ens5f0np0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000
 5: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
 6: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000
 7: ens5f1np1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000
 8: idrac: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
 9: bond2: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
 10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
 11: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
 12: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP mode DEFAULT group default qlen 1000
 13: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
 [...] 

interface 'ens1f1' does not desappear, simply get not 'renamed' on boot, and
remain 'eth1'.

I've tried a manual:
	ip link set eth1 master bond1

and interface start working as expected.

If logs can be useful, if it is better to fire up a bug, say me.


Just i'm here, i've found also:

 root@svpve2:~# ip addr show ens1f0
 2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
     link/ether f4:ee:08:24:3a:ff brd ff:ff:ff:ff:ff:ff permaddr 5c:6f:69:0f:99:78
     altname enp1s0f0

and 'enp1s0f0' in 'altname' was the old interface name, that was in
/etc/network/interfaces; but at boot bond does not bind it, i was forced to
use the 'new' name.

'altname' work only insome aspect? Or simply, does not work for bonds?


Thanks.

-- 


_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Interface not renamed...

[Fiona Ebner]

Hi,
see also:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_naming_conventions

The recommended way to avoid such renaming issues is to pin the name
based on MAC address:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#network_override_device_names

Best Regards,
Fiona


_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user

Re: [PVE-User] Interface not renamed...

[Marco Gaiarin]

Mandi! Fiona Ebner
  In chel di` si favelave...

> see also:
> https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_naming_conventions
> 
> The recommended way to avoid such renaming issues is to pin the name
> based on MAC address:
> https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#network_override_device_names

Thanks, Fiona; but it is not the renaming 'per se' that scare me, was
written in the documentation, i was prepared of.

But probably i've found the culprit.


Systems get installed in some PVE 6.X version, and have a direct bond
between two nodes to manage replication and migration; in PVE6 we had some
trouble to setup jumbo frames for the bond, because some times the server
boot with MTU=9000 on the bond but not on the member link.

We solved it adding 'allow-bond2' to the member stanzas on
/etc/network/interfaces.


Seems to me that:

1) PVE 7 effectively rename interfaces; as just stated, this is expected, no
 trouble.

2) PVE 8 add 'ifupdown2', that is incompatible with 'allow-bond2' option AND
 in some way ''mangle' all the ifupdown -> ifupdown2 migration: server boot
with NO interface up, but also some other things seems does not work very
well.


Because i've still some server to migrate, i've removed 'allow-bond2'
options BEFORE initiate the upgrade PVE7 -> 8, and migration went smoothly,
precisely:
 - interface start at next boot
 - all interfece went up, even get renamed, because 'altname' get correctly
   used.


I hope i was clear. And useful. ;-)

-- 


_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user