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
