{"id":5392,"date":"2014-09-01T17:31:05","date_gmt":"2014-09-01T09:31:05","guid":{"rendered":"https:\/\/webhostinggeeks.com\/howto\/?p=5392"},"modified":"2023-06-28T11:28:16","modified_gmt":"2023-06-28T11:28:16","slug":"new-naming-scheme-for-the-network-interface-on-rhel-7centos-7","status":"publish","type":"post","link":"https:\/\/webhostinggeeks.com\/howto\/new-naming-scheme-for-the-network-interface-on-rhel-7centos-7\/","title":{"rendered":"New Naming Scheme for the Network Interface on RHEL 7\/CentOS 7"},"content":{"rendered":"<p>Red Hat Enterprise Linux 7 (RHEL 7) and CentOS 7 have introduced a new naming scheme for network devices. This scheme aims to make network interfaces fully predictable and automatic, simplifying differentiation and facilitating seamless hardware replacement. This change affects both network adapters embedded on the motherboard (Lan-on-Motherboard) and additional adapters such as PCI network cards.<\/p>\n<p>Previously, Linux network interfaces used the naming convention eth[0123\u2026]. However, in RHEL7\/CentOS7, the default network interface name is based on firmware, topology, and location information. The new naming schemes supported by udev natively include:<\/p>\n<ul>\n<li>Names incorporating Firmware or BIOS provided index numbers for on-board devices (example: eno1)<\/li>\n<li>Names incorporating Firmware or BIOS provided PCI Express hotplug slot index numbers (example: ens1)<\/li>\n<li>Names incorporating physical location of the connector of the hardware (example: enp2s0)<\/li>\n<li>Names incorporating the interface\u2019s MAC address (example: enx78e7d1ea46da)<\/li>\n<li>The traditional unpredictable kernel-native ethX naming (example: eth0)<\/li>\n<\/ul>\n<p>The names have two character prefixes based on the type of interface: &#8216;en&#8217; for Ethernet, &#8216;wl&#8217; for wireless LAN (WLAN), and &#8216;ww&#8217; for wireless wide area network (WWAN).<\/p>\n<h3>Checking the Assigned Device Name<\/h3>\n<p>The ifconfig utility may not be installed by default in a minimal installation. You can use \u201cip link show\u201c, \u201cip addr\u201d or \u201cip address\u201d to display the auto assigned devices name. For example:<\/p>\n<pre>[root@centos7 ~]# ip link show\r\n1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT\r\n    link\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\r\n2: ens160: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc mq state UP mode DEFAULT qlen 1000\r\n    link\/ether 00:0c:29:ba:3e:fe brd ff:ff:ff:ff:ff:ff\r\n<\/pre>\n<pre>[root@centos7 ~]# ip address\r\n1: lo: &lt;LOOPBACK,UP,LOWER_UP&gt; mtu 65536 qdisc noqueue state UNKNOWN\r\n    link\/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00\r\n    inet 127.0.0.1\/8 scope host lo\r\n       valid_lft forever preferred_lft forever\r\n    inet6 ::1\/128 scope host\r\n       valid_lft forever preferred_lft forever\r\n2: ens160: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 1500 qdisc mq state UP qlen 1000\r\n    link\/ether 00:0c:29:ba:3e:fe brd ff:ff:ff:ff:ff:ff\r\n    inet 192.168.0.18\/24 brd 192.168.0.255 scope global dynamic ens160\r\n       valid_lft 604707sec preferred_lft 604707sec\r\n    inet6 fe80::20c:29ff:feba:3efe\/64 scope link\r\n       valid_lft forever preferred_lft forever\r\n<\/pre>\n<h2>Commands Mentioned<\/h2>\n<ul>\n<li><span class=\"fw-bold\">ip link show<\/span> \u2013 This command is used to display the state of all network interfaces.<\/li>\n<li><span class=\"fw-bold\">ip addr<\/span> or <span class=\"fw-bold\">ip address<\/span> \u2013 These commands are used to display all IP addresses assigned to your network interfaces.<\/li>\n<\/ul>\n<h2>Conclusion<\/h2>\n<p>The new naming scheme for network interfaces in RHEL 7\/CentOS 7 is a significant shift from the traditional ethX naming. It provides a more predictable and automatic way of identifying network interfaces, making it easier for system administrators to manage network configurations.<\/p>\n<p>By understanding the different naming schemes and how to check the assigned device name, you can effectively navigate this new system. The shift to this new naming scheme is designed to improve your experience as a system administrator, making it easier to differentiate between devices and seamlessly replace broken hardware.<\/p>\n<p>Remember, understanding the tools and systems you&#8217;re working with is the first step to mastering them.<\/p>\n<p>Happy hosting!<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<ol itemscope itemtype=\"https:\/\/schema.org\/FAQPage\">\n<li itemscope itemprop=\"mainEntity\" itemtype=\"https:\/\/schema.org\/Question\">\n<p class=\"fw-bold\" itemprop=\"name\">What is the purpose of the new naming scheme in RHEL 7\/CentOS 7?<\/p>\n<p itemprop=\"acceptedAnswer\" itemscope itemtype=\"https:\/\/schema.org\/Answer\">\n                <span itemprop=\"text\">The new naming scheme in RHEL 7\/CentOS 7 aims to make network interfaces fully predictable and automatic. It simplifies differentiation and facilitates seamless hardware replacement.<\/span>\n            <\/p>\n<\/li>\n<li itemscope itemprop=\"mainEntity\" itemtype=\"https:\/\/schema.org\/Question\">\n<p class=\"fw-bold\" itemprop=\"name\">What are the different types of naming schemes supported by udev?<\/p>\n<p itemprop=\"acceptedAnswer\" itemscope itemtype=\"https:\/\/schema.org\/Answer\">\n                <span itemprop=\"text\">udev supports naming schemes that incorporate Firmware or BIOS provided index numbers, PCI Express hotplug slot index numbers, physical location of the connector of the hardware, the interface\u2019s MAC address, and the traditional unpredictable kernel-native ethX naming.<\/span>\n            <\/p>\n<\/li>\n<li itemscope itemprop=\"mainEntity\" itemtype=\"https:\/\/schema.org\/Question\">\n<p class=\"fw-bold\" itemprop=\"name\">What do the two character prefixes in the names represent?<\/p>\n<p itemprop=\"acceptedAnswer\" itemscope itemtype=\"https:\/\/schema.org\/Answer\">\n                <span itemprop=\"text\">The two character prefixes represent the type of interface. &#8216;en&#8217; stands for Ethernet, &#8216;wl&#8217; for wireless LAN (WLAN), and &#8216;ww&#8217; for wireless wide area network (WWAN).<\/span>\n            <\/p>\n<\/li>\n<li itemscope itemprop=\"mainEntity\" itemtype=\"https:\/\/schema.org\/Question\">\n<p class=\"fw-bold\" itemprop=\"name\">How can I check the auto assigned device name?<\/p>\n<p itemprop=\"acceptedAnswer\" itemscope itemtype=\"https:\/\/schema.org\/Answer\">\n                <span itemprop=\"text\">You can use the commands \u201cip link show\u201c, \u201cip addr\u201d or \u201cip address\u201d to display the auto assigned device name.<\/span>\n            <\/p>\n<\/li>\n<li itemscope itemprop=\"mainEntity\" itemtype=\"https:\/\/schema.org\/Question\">\n<p class=\"fw-bold\" itemprop=\"name\">What is the ifconfig utility?<\/p>\n<p itemprop=\"acceptedAnswer\" itemscope itemtype=\"https:\/\/schema.org\/Answer\">\n                <span itemprop=\"text\">The ifconfig utility is a system administration tool used for network interface configuration. It is used to configure, manage and query network interface parameters. It is not installed by default in a minimal installation of RHEL 7\/CentOS 7.<\/span>\n            <\/p>\n<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"<p>Red Hat Enterprise Linux 7 (RHEL 7) and CentOS 7 have introduced a new naming scheme for network devices. This scheme aims to make network interfaces fully predictable and automatic,&#8230;<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"wds_primary_category":0,"footnotes":""},"categories":[2055,2058],"tags":[1251,1536,1717],"class_list":["post-5392","post","type-post","status-publish","format-standard","hentry","category-centos","category-rhel","tag-centos-6","tag-linux","tag-rhel-7"],"_links":{"self":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/5392","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/comments?post=5392"}],"version-history":[{"count":0,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/posts\/5392\/revisions"}],"wp:attachment":[{"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/media?parent=5392"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/categories?post=5392"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhostinggeeks.com\/howto\/wp-json\/wp\/v2\/tags?post=5392"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}