- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Redhat 5 missing eth0
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
01-25-2014 06:56 AM
01-25-2014 06:56 AM
Redhat 5 missing eth0
Hi,
We are running Redhat 5 in DL380. The system was using eth0 for network interface. We shutdown the system to replace the rack. After the server powerup, eth0 is missing.
The following was performed with the output:
#ifconfig eth0 up
eth0: unknown interface: no such device
#/etc/init.d/network restart
Bringing up interfac eth0: dvice eth0 does not seem to present, delaying initialisation
Any advise is appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-29-2014 06:31 AM
01-29-2014 06:31 AM
Re: Redhat 5 missing eth0
Which generation of DL380?
Does "lspci | grep -i ethernet" detect any network interfaces? If not, there might be a physical connection issue, e.g. when the server was moved, a card might have risen a bit in its slot, causing an incomplete connection. (The solution for that is to power down the server, open it and then make sure that all the cards are all the way in their slots, and the riser module is completely seated on the system board.)
Does "ifconfig -a" display any network interfaces other than the loopback device? If not, it might be a kernel module loading issue: for example, you might have been previously running an older kernel with an add-on NIC driver, and when the system was rebooted, it started using the latest kernel... which might not have a corresponding add-on driver module.
If "ifconfig -a" displays other network interfaces but not eth0, check the HWADDR lines in your /etc/sysconfig/network-scripts/ifcfg-* files. The MAC address of eth0 should be listed in /etc/sysconfig/network-scripts/ifcfg-eth0 only. If the same HWADDR line is listed in other ifcfg-* files, the ifup script might become confused and think that the network interface needs to be renamed to something other than eth0.
Note that HWADDR line and MACADDR lines in ifcfg-* files seem very similar, but have very different purposes:
- HWADDR means "these are the settings for a NIC with this MAC address". If a NIC has a different ethN name but the correct MAC address, the system will automatically rename it. This ensures the other NIC names won't get reassigned if you add/remove a single NIC to/from the system.
- MACADDR means "change the MAC address of this NIC to this value". This can be useful if you replace a broken NIC on a system that has software licenses locked to a particular MAC address.
Obviously, you should never use HWADDR and MACADDR together, or great confusion will result. By default, RHEL 5 adds HWADDR to each ifcfg-* file the first time a new NIC is detected. In some cases, an administrator might prefer the "old RedHat Linux way" of NIC name allocation: that can be done by removing all the HWADDR lines from all ifcfg-* files.