Renaming of pinned nic names

[Onkeldata]

I setup a PVE 9 to include in my Cluster. It pins the NIC names to static names. I didn't pay enough attention, and now my 10g NIC for the storage are nic4 and nic5. I'd like them to have a name like fiber10g1 and fiber10g2
Now, there are lot of "edit by hand" finds, but I'd like to think, there is a mechanic in pve to do this safely? I always can set it up again, but...

 

[cheiss]

Hi,

you can use the pve-network-interface-pinning tool: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_using_the_pve_network_interface_pinning_tool

Especially the section on pinning a specific interface should do the trick: https://pve.proxmox.com/pve-docs/pv...ool#:~:text=When pinning a specific interface

For example:

pve-network-interface-pinning generate --interface nic4 --target-name fiber10g1

 

[Onkeldata]

Hi,

you can use the pve-network-interface-pinning tool: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_using_the_pve_network_interface_pinning_tool

Especially the section on pinning a specific interface should do the trick: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_using_the_pve_network_interface_pinning_tool#:~:text=When pinning a specific interface

For example:

pve-network-interface-pinning generate --interface nic4 --target-name fiber10g1

Thank you for the fast response. But, this is not renaming the pin, it is the "first" pin.

 

[cheiss]

If they are named nic4 and nic5, then they are were already pinned by the installer. It's our default naming scheme.

Afterwards, you just need to remove the old file at /usr/local/lib/systemd/network/50-pmx-<oldname>.link.

 

[Onkeldata]

If they are named nic4 and nic5, then they are were already pinned by the installer. It's our default naming scheme.

Afterwards, you just need to remove the old file at /usr/local/lib/systemd/network/50-pmx-<oldname>.link.

Yes, that's what I tried to communicate. So, the removal of these links is all I need? Then I can pin the names I want? It read in the posts out there like other configuration files had to be edited, too.

 

[cheiss]

So, the removal of these links is all I need?

Yes.
- First run pve-network-interface-pinning as shown above
- Then, afterwards, remove the .link for the old interface name under /usr/local/lib/systemd/network/.
- Finally, reboot

The pve-network-interface-pinning takes care of updating all Proxmox-managed configuration files.
If you installed any additional, non-default services on the host that depend on interface name, you of course need to update them manually

 

[Onkeldata]

Yes.
- First run pve-network-interface-pinning as shown above
- Then, afterwards, remove the .link for the old interface name under /usr/local/lib/systemd/network/.
- Finally, reboot

The pve-network-interface-pinning takes care of updating all Proxmox-managed configuration files.
If you installed any additional, non-default services on the host that depend on interface name, you of course need to update them manually

This doesn't work, because pve-network-interface-pinning will not generate if there is a pinned name already. So, I'll have to remove the Links first. Now I'm not very confident in your answer, I'm sorry to say, as your way won't run in the first place.

 

[SteveITS]

name like fiber10g1 and fiber10g2

If you will use custom names you should see note "It is recommended to assign a name starting with en or eth..." Though the tool does use "nic..." as you found, so I would think that is also supported.