My Oracle Support Banner

Oracle Linux: Give Network Interfaces Persistent Names Without Changing The GRUB Boot Configuration (Kernel Parameter biosdevname Or net.ifnames) (Doc ID 2521902.1)

Last updated on MAY 15, 2020

Applies to:

Linux OS - Version Oracle Linux 7.0 and later
Oracle Cloud Infrastructure - Version N/A to N/A [Release 1.0]
Linux x86-64

Goal

Give Oracle Linux 7 (OL7) Network Devices A Persistent Name.

network interfaces on Oracle Linux 7 without touching biosdevname or net.ifnames.

Beginning with OL7,  network interfaces are named according to the biosdevname convention.  This convention chooses location-based device names, such as enp0s10, instead of the more-familiar eth0 scheme that was used previously.

There are existing KM documents that provide procedures to assign meaningful, persistent network interface names by adding biosdevname=0 or net.ifnames=0 to the kernel boot parameters. 

This document provides a preferred approach to having persistent network interface device names.  This technique does not require editing boot-critical files or altering the kernel command line in GRUB.

Using UDEV rules alone can achieve the same result.  There is no need to change the default boot parameters at all.  A system reboot is not necessary.

This is an alternative to the solution offered in Oracle Linux 7: How To Modify Network Interface Names (Doc ID 2080965.1).

 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
 Examining the available UDEV device attributes.
 Locating the UDEV rules.
 Creating a custom UDEV rule.
 Understanding why this custom UDEV rule  works.
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.