My nics renamed after upgrading from 5.4 to 6.0

fxandrei

Renowned Member
Jan 10, 2013
156
15
83
So i had some strange behavior while upgrading a cluster that had proxmox 5.4 (upgrade to 6.0).
So i followed the upgrade instructions and everything went quite well untill i restarted the servers, after upgrading to buster.
So on 2 of the servers (the 3rd server is actually a vm that exists just for the minimum 3 servers cluster requirement) after i rebooted i saw that all the nics on my second network card were renamed.
So i have 2 network cards, each with 4 ports. One internal card, and one additionall card.
The additional card had all its ports renamed.
So from something like ens8fp1 i had something line ens1fp0. The stranger thing was that 2 of the ports were renamed to "rename6" and "rename7" on one server . The other server had the same thing.

So what i did is go to /etc/network/interfaces and update all the names like they are now.

Everything seems to work now, but i dont understand what happened.

By the way, if i go in the proxmox gui and look at the network interfaces, the "rename8" port and "rename7" port has type "Unknown". Is there anything i can do about this ?!
 
  • Like
Reactions: rjdiniz
It was stated as an expected deviation in the release notes. You should make it a point to read them before committing to a major version change:
https://pve.proxmox.com/wiki/Roadmap#Proxmox_VE_6.0

From the release notes:

Linux Kernel
  • Updated 5.0 Kernel based off the Ubuntu 19.04 "Disco" kernel with ZFS.
  • Intel in-tree NIC drivers are used:
    • Many recent improvements to the kernel networking subsystem introduced incompatibilities with the out of tree drivers provided by Intel, which sometimes lag behind on support for new kernel versions. This can lead to a change of the predictable network interface names for Intel NICs.

By the way, if i go in the proxmox gui and look at the network interfaces, the "rename8" port and "rename7" port has type "Unknown". Is there anything i can do about this ?!

You can specify specific information about your nic's using Udev (in debian).
 
  • Like
Reactions: fxandrei
So i had some strange behavior while upgrading a cluster that had proxmox 5.4 (upgrade to 6.0).
So i followed the upgrade instructions and everything went quite well untill i restarted the servers, after upgrading to buster.
So on 2 of the servers (the 3rd server is actually a vm that exists just for the minimum 3 servers cluster requirement) after i rebooted i saw that all the nics on my second network card were renamed.
So i have 2 network cards, each with 4 ports. One internal card, and one additionall card.
The additional card had all its ports renamed.
So from something like ens8fp1 i had something line ens1fp0. The stranger thing was that 2 of the ports were renamed to "rename6" and "rename7" on one server . The other server had the same thing.

So what i did is go to /etc/network/interfaces and update all the names like they are now.

Everything seems to work now, but i dont understand what happened.

By the way, if i go in the proxmox gui and look at the network interfaces, the "rename8" port and "rename7" port has type "Unknown". Is there anything i can do about this ?!

I am also going through this, but it was in the upgrade to new HD's ... I decided to install version 6.1-2 and presented the same conditions "rename6" and "rename9" ... funny it is in version 5.4 it didn't have that! I'll edit / etc / network / interfaces as you did and see if it works ...
 
  • Like
Reactions: fxandrei

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!