On Wed, Jan 04, 2012 at 07:22:11PM -0500, Digimer wrote:

On 01/04/2012 06:52 PM, Jeff wrote:

...

Just installed centos 6.2. I run and ifconfig -a I see and em1 em2 and lo interface. If I go to /etc/sysconfig/network-scripts, I don't see an ifcfg-eth0. If I run ifup eth0 it comes back with "Device eth0 does not seem to be present, delaying initialization". Anybody have a clue? Thanks in advance.

The names of the devices are starting to change. The 'emX' are likely your interfaces. If you check you should have ifcfg-emX files. If you would like to rename them, you can follow this;

Not sure about RH 6.x, but in Fedora 16 and up, one also should remove the biosdevname package (rpm -e biosdevname) if they want to go back to the ethX naming scheme.

http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming

and

http://fedoraproject.org/wiki/Talk:Features/ConsistentNetworkDeviceNaming

On 5 January 2012 22:57, Jeff jtunix@gmail.com wrote:

Thanks for the help and info!

Here's the relevant link from the upstream vendor's release notes: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/6.1_Releas...

Naming convention for network interfaces

Traditionally, network interfaces in Linux are named eth[X]. However, in many cases, these names do not correspond to actual labels on the chassis. Modern server platforms with multiple network adapters can encounter non-deterministic and counterintuitive naming of these network interfaces. Red Hat Enterprise Linux 6.1 introduces biosdevname, an optional convention for naming network interfaces. biosdevname assigns names to network interfaces based on their physical location. Note, however that biosdevname is disabled by default, except for a limited set of Dell systems. Refer to the Red Hat Knowledge Base for further information on using biosdevname.