大网数据广告活动
服务器运维问答

What controls the NIC naming convention after fresh Ubuntu 20.04 install?

· 52CE 我爱测

This is a fresh install Ubuntu server 20.04.04 system. I'm using networkd and netplan to configure networking. I did not do any custom install steps, just loaded the .iso and installed Ubuntu server through the prompts. When thes…

问题原文

原帖链接 · Rino Bino · CC BY-SA 4.0

This is a fresh install Ubuntu server 20.04.04 system. I'm using networkd and netplan to configure networking. I did not do any custom install steps, just loaded the .iso and installed Ubuntu server through the prompts.

When these machines were shipped from the vendor, Ubuntu was already installed and the network interfaces were named ens1f0 and ens1f1:

root@oldHost2:~# sudo lshw -C network |grep "logical name"
       logical name: ens1f0
       logical name: ens1f1
       logical name: bond0

However after reinstalling the OS (before running netplan) I get....

root@freshHost1:~# sudo lshw -C network |grep "logical name"
       logical name: ens1f0np0
       logical name: ens1f1np1
       logical name: bond0

Across all my sites, we use a netplan config that assumes ens1f0 and ens1f0. I would like all interfaces to match this.

I know you can set the interface name with set-name in netplan (as defined in https://ubuntu.com/server/docs/network-configuration) however you need to already match the interface somehow (using Mac address, etc) which is going to make auto-provisioning a nightmare (if not impossible). A chicken/egg scenario. I have hundreds of machines to provision and I would like to template out my netplan config without knowing the Mac addresses.

I know you can also group together the interfaces in netplan:

  ethernets:
    eports:
      match:
        name: ens*

Which may work for my case, but not all the systems have a simple two NIC setup like this so I'm not sure what the best course of action will be.

My questions to ServerFault...

  • Since this logical name is set before Netplan is even ran, what is deciding on this name? How can I override it during OS install/provision?
  • What does the np0 and np1 mean in the interface names?

已采纳解答

原帖链接 · alex.forencich · CC BY-SA 4.0

This is determined by systemd based on information about the device. The name can be influenced by several different factors, including BIOS, other devices that might be installed, linux version, and driver version. See https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html for how systemd constructs the names.

For example, slot numbers may or may not be associated with PCIe slots. I think this at least somewhat related to BIOS/ACPI, but there could be other factors. On one of my machines, a NIC installed in one slot enumerates as enpN, and the same NIC when moved to a different slot enumerates as ensN.

I have heard of cases where PCIe bus numbers are assigned differently under certain conditions, such as the presence of a thunderbolt device during boot. Ultimately this is probably the fault of the system BIOS for not reserving PCIe bus numbers correctly for the thunderbolt port.

As far as what you're seeing with np0 and np1, the p0 and p1 are physical port names coming from devlink __devlink_port_phys_port_name_get. Presumably devlink support was added to the NIC driver, which caused the np0/np1 to appear. If you update the older system to the same kernel version, the naming should also change.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2022-03-29)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。