Error with RHEL: bringing up interface eth1: Device eth0 has different MAC address
 

Let me know if this is either a networking questions or a virtualization question.

I'm working with RHEL 5 and have cloned a Linux machine in vCenter. Currently setting up the cloned machine with a new ip address and new hostname, when getting the following error:

RHEL bringing up interface eth1: Device eth0 has different MAC address than expected, ignoring

The odd thing is that is created three nics: eth0, eth0.bak (some sort of backup of eth0) and eth1. This did not happen a week earlier when we cloned another RHEL machine.

I am able to ping the loopback (127.0.0.1) any my private address (192.168.10.2). I have a ping sweep script (not allowed to install nmap) and I can only ping my address, not the machine on this subnet.

I tried the basics: ifupeth0; ifdowneth0 and ifupeth1 and ifdowneth0 and /etc/init.d/network restart | stop | start.

Also checked under /etc/sysconfig/network-scripts and there are two file, eth0 and eth1, both with the same mac address that shows was assigned/created by vCenter.

Also checking dmesg | grep eth0 and grep eth1 there was an issue with eth0 and vlan0 along 8021q frames, which gets into vlan tagging. Didn't go into anymore details...

I tried a few more things offered under this thread: http://linux.ittoolbox.com/groups/te...noring-3905913

Out of desperation and time, I logged in as root, backed up the ifcfg files for eth0 and eth1and from the GUI > System > Network. I deleted all of the nics and re-created 1, which the system created eth1 and restarted the network service. All of these came up ok. I then re-ran my ping sweep command and was able to hit all of the machines on the subnet.


So....I'm not sure what caused the error to begin with. Is it somethign with VMWare or is it some sort of networking issues?

BTW, there was an older thread from linuxquestions:

http://www.linuxquestions.org/questi...ss-4175437720/

That pointed to VMWare Tools as being the culprit, so at this point I'm at a loss.

thanks

If that box started life with only one nic, the VM creation sets up port forwarding to the main machine as a network. That way, it _may_just_ be expecting a vlan as eth1, not a real card. What I mean is

Main box e.g. 192.168.1.10 (192.168.1.10.1 imp[lied)
VM therefore would have to be 192.168.1.10.2 or higher

But you're running RHEL. Why ask us? You surely pay them for support. Ask them, and post here in case some others are interested.