HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Naming convention for eth# interfaces
Operating System - Linux
1827858
Members
1743
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2011 06:52 AM
03-23-2011 06:52 AM
Is there a way to stop the eth# getting re-arranged in RHEL upon reboot and replacing. Any workwounds?
Thanks
Brian
Thanks
Brian
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2011 07:47 AM
03-23-2011 07:47 AM
Solution
Adjust the HWADDR= lines in each /etc/sysconfig/network-interfaces/ifcfg-eth* file to the way you want the NICs to be.
If you want the NIC with MAC address 11:22:33:44:55:66 to be eth0, then /etc/sysconfig/network-interfaces/ifcfg-eth0 should have this line:
HWADDR=11:22:33:44:55:66
If you need to replace the eth0 NIC, the new NIC will have a different MAC address than the old one. So edit the /etc/sysconfig/network-interfaces/ifcfg-eth0 to match the new situation, and the physical NIC -> eth# name will stay the same: if some hardware change would make it different, the OS will automatically re-arrange the cards to make them stay the way you want them.
If you want to completely disable the re-arrangement system and let the NIC names be assigned in the hardware detection order, then just remove the HWADDR= lines from all ifcfg-eth* files.
NOTE: the HWADDR= line will control the re-arrangement of eth# names; MACADDR= line would be used to assign custom MAC addresses to NICs. Don't confuse the two, and don't use them both on the same NIC.
MK
If you want the NIC with MAC address 11:22:33:44:55:66 to be eth0, then /etc/sysconfig/network-interfaces/ifcfg-eth0 should have this line:
HWADDR=11:22:33:44:55:66
If you need to replace the eth0 NIC, the new NIC will have a different MAC address than the old one. So edit the /etc/sysconfig/network-interfaces/ifcfg-eth0 to match the new situation, and the physical NIC -> eth# name will stay the same: if some hardware change would make it different, the OS will automatically re-arrange the cards to make them stay the way you want them.
If you want to completely disable the re-arrangement system and let the NIC names be assigned in the hardware detection order, then just remove the HWADDR= lines from all ifcfg-eth* files.
NOTE: the HWADDR= line will control the re-arrangement of eth# names; MACADDR= line would be used to assign custom MAC addresses to NICs. Don't confuse the two, and don't use them both on the same NIC.
MK
MK
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP