Bringing up interface eth0: e1000 device eth0 does not seem to be present, delaying initialization.

[jhutchinson74]

I performed a software reboot on the MSE3310.  After the reboot the MSE was no longer visible on the network.  I went and consoled into the device and it was operational.  I ran the msed stop and msed start commands.  I got this message when it tried to load eth0

Bringing up interface eth0:  e1000 device eth0 does not seem to be present, delaying initialization.

[FAILED]

Earlier in the day I had updgraded the firmware from 6.0 to 7.0.230.0.

Can I recover the eth0?  Is this related to the firmware upgrade? 

Thanks.

Jason

[blakekrone]

I know this will sound strange but have you tried switching the NIC that the MSE is using? I've seen this before where the MSE will swap the NICs around on you after an upgrade.

[michael.colles]

Any more info on this issue?  I just upgraded and had the same issue. 

I noticed this error at the end of the upgrade...

INIT: version 2.86 reloading

PCI: Enabling device 0000:04:00.4 (0140 -> 0143)

ipmi_si: Unable to find any System Interface(s)

The eth0 interface is also named....   __tmp1713034326 

[Brian Schultz]

Michael,

What did you find to resolve this?  We are having the exact same issue after an upgrade and reboot of the MSE to 7.2.110.0.  Eth0 does not seem to be present, but I can see from an ifconfig -a that it is now named __tmp1343987323.

When running the setup command, it does not appear that you can just swap the NIC's as it requires the default gateway to be on eth0.

Thanks,

Brian

[Tarik Admani]

Brian,

This looks like a redhat bug, if you have the mac address handy you should be able to modify the network script setting for eth0 and have it look like eth1 with the correct mac address:

https://bugzilla.redhat.com/show_bug.cgi?id=224662

Thanks,

Tarik Admani
*Please rate helpful posts*

[Tarik Admani]

Jason,

Here is another article that will help

http://blog.cvallance.net/?p=32

Thanks,

Tarik Admani
*Please rate helpful posts*

[Brian Schultz]

Tarik,

This procedure worked great!  After adding the HWADDR parameter to the eth0 config file and rebooting the server, we are now able to access the server on the network again.  Thank you very much for the quick reply!

Here is the procedure if others need this.

ifconfig -a showed the eth0 interface was renamed to _tmp462132856

[root@MSE-CPW-01 ~]# ifconfig -a

__tmp462132856 Link encap:Ethernet  HWaddr 00:15:17:F1:4D:C7

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

          Interrupt:169 Memory:e8180000-e81a0000

eth1      Link encap:Ethernet  HWaddr 00:15:17:F1:4D:C8

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

Then issued

vi /etc/sysconfig/network-scripts/ifcfg-eth0

to edit the file and add the HWADDR=xx:xx:xx:xx:xx:xx

Then issued a 'shutdown -r now' to reboot the server

After a reboot, network connectivity was restored!

Thanks!

Brian

[Tom]

That's one of them as this worked on one of my installations but not on another, though must say Thank You for posting this.  There's a number of solutions to this one generic error.  Turns out that renaming NIC's or UDEV rules also play a part here amongst a buch of other solutions for this generic error.  Here's an older post with several solutions in case the above doesn't work out.

Device eth0 does nto seem to be present

Cheers,