wikiSupermicro X12SPL-F with Proxmox VE 7 ethX instead of enoX NICs with BIOS 1.1
On systems with Supermicro X12SPF-L, using BIOS version 1.1 causes problems with naming the onboard network interfaces in Proxmox VE. The Onboard NICs are displayed, for example, as eth2 or eth4 instead of eno1 and eno2. A BIOS update on version 1.1c solves the problem.
Problem
Instead of Predictable Network Interface Names such as eno1 or eno2, the Onboard NICs are configured as eth* after starting Proxmox VE. The concret interface name varies from reboot to reboot, for example:[1]
First reboot:
[ 2.341072] igb 0000:02:00.0: added PHC on eth2 [ 2.341073] igb 0000:02:00.0: eth2: (PCIe:2.5Gb/s:Width x1) 3c:ec:ef:7b:92:27 [ 2.341116] igb 0000:02:00.0: eth2: PBA No: 010A00-000
Second reboot:
[ 2.363561] igb 0000:02:00.0: added PHC on eth4 [ 2.363563] igb 0000:02:00.0: eth4: (PCIe:2.5Gb/s:Width x1) 3c:ec:ef:7b:92:27 [ 2.363607] igb 0000:02:00.0: eth4: PBA No: 010A00-000
During a conventional boot process, SystemD converts the respective eth* interfaces into predictable, stable network interface names during the boot process using the Predictable Network Interface Names rules.
The Supermicro X12SPL-F experiences enumeration issues with BIOS version 1.1. A similar issue was previously encountered with the Supermicro X9DRi-LN4F+ motherboard.[2]
Affected hardware
The following hardware is affected:
- Supermicro X12SPL-F mainboard with BIOS version 1.1
Solution
An update on BIOS version 1.1c solves the problem. The enumaration does function with the new BIOS.
More information
- Proxmox using eth-naming + alt-names in network interfaces (forum.proxmox.com, 08.02.2022)
References
- ↑ Predictable Network Interface Names (systemd.io) As the driver probing is generally not predictable for modern technology this means that as soon as multiple network interfaces are available the assignment of the names eth0, eth1 and so on is generally not fixed anymore and it might very well happen that eth0 on one boot ends up being eth1 on the next.
- ↑ eno1 switches to different ethernet ports on motherboard after reboot (www.reddit.com, 05.10.2018) The BIOS does not correctly enumerate the ethernet interfaces, so the predictable naming system finds a name collision and stops renaming, thats why there are interfaces named rename2, rename3... This issue has been discussed at the Ubuntu bug tracker. [...] After talking to a SuperMicro technician, they had an update to v3.3 [...], it solves this issue along with Spectre and other fixes.
 |
Author: Werner Fischer Werner Fischer, working in the Knowledge Transfer team at Thomas-Krenn, completed his studies of Computer and Media Security at FH Hagenberg in Austria. He is a regular speaker at many conferences like LinuxTag, OSMC, OSDC, LinuxCon, and author for various IT magazines. In his spare time he enjoys playing the piano and training for a good result at the annual Linz marathon relay.
|
 |
Author: Jonas Sterr Jonas Sterr has been working for Thomas-Krenn for several years. Originally employed as a trainee in technical support and then in hosting (formerly Filoo), Mr. Sterr now mainly deals with the topics of storage (SDS / Huawei / Netapp), virtualization (VMware, Proxmox, HyperV) and network (switches, firewalls) in product management at Thomas-Krenn.AG in Freyung.
|
 |
Translator: Alina Ranzinger Alina has been working at Thomas-Krenn.AG since 2024. After her training as multilingual business assistant, she got her job as assistant of the Product Management and is responsible for the translation of texts and for the organisation of the department.
|
