Difference between revisions of "Consistent Network Device Naming"
Jump to navigation
Jump to search
↑
RHCSA & RHCE Red Hat Enterprise Linux 7: Training and Exam Preparation Guide (EX200 and EX300), Third Edition Paperback – 27 Mar 2015
by Asghar Ghori
Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| Line 2: | Line 2: | ||
* <code>[[eno]]#</code> | * <code>[[eno]]#</code> | ||
| − | * <code>[[ens]]#</code> | + | * <code>[[ens]]#</code>, 10 [[Gbps]] |
* [[eth]] | * [[eth]] | ||
Revision as of 13:48, 18 August 2020
https://en.wikipedia.org/wiki/Consistent_Network_Device_Naming
Examples:
ens3f0ens3f1
Device naming rules
- Onboard interfaces at firmware index numbers eno[1-N]
- Interfaces at PCI Express hotplug slot numbers ens[1-N]
- Adapters in the specified PCI slot, with slot index number on the adapter <templatestyles src="Mono/styles.css" />enp<PCI slot>s<card index no>
- If firmware information is invalid or rules are disabled, use traditional <templatestyles src="Mono/styles.css" />eth[0-N][1]
Related terms
See also
- KVM networking, virsh net, MacVTap, Macvtap logs, virtio,
trustGuestRxFilters - Linux Kernel: namespaces, Cgroups, OOM, proc, Linux Kernel changelog,
sysctl, userfaultfd, Grub, ENOSPC, ENOMEM, DKMS, syscall, Transparent huge pages, smatch, sysfs, vm.swappiness, CFS, Runlevel, Jens Axboe, Consistent Network Device Naming, Initial ramdisk (initrd),modprobe, MTD, Linux Kernel vulnerabilities,/sys/kernel/, KernelCare,unix://, Data Plane Development Kit (DPDK)
Advertising:
