Hello,
I'm new to PVE, so I may don't know something.
In our installation, we have 2 HP servers with 3 modules of NICs on each:
- 2 NICs onboard
- 3 NICs on 1 PCI-X slot,
- 2 NICs on 1 PCI-E slot.
After first test install, problem arrised with interfaces name inconsistence.
Two exact same servers has diff interface naming, which is very inconvenient and inacceptable in production.
So my question, why PVE doesnt implemented this from the installation ?
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
My problem was solved after manual editing of grub's cfg (kernel boot behavior), but I lost many hours and was quite surprised.
/etc/default/grub
GRUB_CMDLINE_LINUX="biosdevname=1 net.ifnames=1"
cp /boot/grub/grub.cfg /boot/grub/grub.cfg-orig
grub-mkconfig -o /boot/grub/grub.cfg
# reboot
The result:
root@~# ip -br link show up
lo UNKNOWN 00:00:00:0
ens4f0 UP 00:26:55:e
enp67s4f0 UP 00:18:71:4
enp65s1 UP 00:18:71:4
enp65s2 UP 1c:c1:de:d
enp67s6f1 UP 1c:c1:de:d
I'm new to PVE, so I may don't know something.
In our installation, we have 2 HP servers with 3 modules of NICs on each:
- 2 NICs onboard
- 3 NICs on 1 PCI-X slot,
- 2 NICs on 1 PCI-E slot.
After first test install, problem arrised with interfaces name inconsistence.
Two exact same servers has diff interface naming, which is very inconvenient and inacceptable in production.
So my question, why PVE doesnt implemented this from the installation ?
https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
My problem was solved after manual editing of grub's cfg (kernel boot behavior), but I lost many hours and was quite surprised.
/etc/default/grub
GRUB_CMDLINE_LINUX="biosdevname=1 net.ifnames=1"
cp /boot/grub/grub.cfg /boot/grub/grub.cfg-orig
grub-mkconfig -o /boot/grub/grub.cfg
# reboot
The result:
root@~# ip -br link show up
lo UNKNOWN 00:00:00:0
ens4f0 UP 00:26:55:e
enp67s4f0 UP 00:18:71:4
enp65s1 UP 00:18:71:4
enp65s2 UP 1c:c1:de:d
enp67s6f1 UP 1c:c1:de:d