Bug 481024

Can you provide the /etc/sysconfig/network-scripts/ifcfg-eth0 config file.

Given that a 'sleep 10' fixes it & running manually fixes it, it sounds like there's a race condition.

I just had a similar issue on 2 Dell PER900, and I used the same fix, "sleep 10", that worked 95% of the time.

I finally tracked the issue: these 2 servers have some DELL packages installed (OpenManage Server Administrator), and it seems that some of the services installed by OMSA conflict with Xen's boot order.

I temporarily resolved the issue by disabling a service named "instsvcdrv" (Systems Management Device Drivers init script). Of course, OMSA doesn't work anymore.

I'm not the original bug reporter, but if that can help, here is the content of my /etc/sysconfig/network-scripts/ifcfg-eth0:
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=none
HWADDR=00:22:19:A6:A7:28
ONBOOT=yes
NETMASK=255.255.255.0
IPADDR=172.16.38.170
GATEWAY=172.16.38.1
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes

Mine are nothing special. This server is also a Dell, but none of the Dell apps are installed - it's mostly a pure RHEL5 system.

# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth0
DHCPCLASS=
HWADDR=00:22:19:99:E2:5D
ONBOOT=yes
IPADDR=209.239.12.43
BOOTPROTO=static
GATEWAY=209.239.12.1
NETMASK=255.255.255.192

I am having this same issue. I haven't tried the "sleep" workaround above, but manually restarting network-bridge resolves the issue.

I'm experiencing this problem with RHEL Desktop 5.4 on a Dell M90 laptop.

Not sure if this will have any relevance to this issue, but I have a couple of Dell servers running RHEL 5 with Xen that are not experiencing this issue. One of those servers (a 2600) is fully updated, the other (a T310) is at 5.4 but is missing some of the more recent updates. Neither of those servers, nor may M90, are running OpenManage. The M90 and T310 are using 64-bit versions of RHEL, the 2600 is using a 32-bit version.

This is the contents of ifcfg-eth0 from my M90. Network Manager is used for network connectivity, so "ONBOOT=no" is set.

# Broadcom Corporation NetXtreme BCM5752 Gigabit Ethernet PCI Express
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:1C:23:08:6F:A3
ONBOOT=no
TYPE=Ethernet
USERCTL=no
IPV6INIT=no
PEERDNS=yes

Let me know if I can provide any additional information.

(In reply to comment #3)
> I just had a similar issue on 2 Dell PER900, and I used the same fix, "sleep
> 10", that worked 95% of the time.
> 
> I finally tracked the issue: these 2 servers have some DELL packages installed
> (OpenManage Server Administrator), and it seems that some of the services
> installed by OMSA conflict with Xen's boot order.
> 
> I temporarily resolved the issue by disabling a service named "instsvcdrv"
> (Systems Management Device Drivers init script). Of course, OMSA doesn't work
> anymore.
> 
> I'm not the original bug reporter, but if that can help, here is the content of
> my /etc/sysconfig/network-scripts/ifcfg-eth0:
> # Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
> DEVICE=eth0
> BOOTPROTO=none
> HWADDR=00:22:19:A6:A7:28
> ONBOOT=yes
> NETMASK=255.255.255.0
> IPADDR=172.16.38.170
> GATEWAY=172.16.38.1
> TYPE=Ethernet
> USERCTL=no
> IPV6INIT=no
> PEERDNS=yes    

Why are you using BOOTPROTO=none? Shouldn't this be static?

For getting the IP address from DHCP I use:

DEVICE=ethX
BOOTPROTO=dhcp
ONBOOT=yes
HWADDR=xx:xx:xx:xx:xx:xx

Could you try using similar configuration except you have the definition for static like:

DEVICE=ethX
BOOTPROTO=static
ONBOOT=yes
HWADDR=xx:xx:xx:xx:xx:xx
NETMASK=255.255.255.0
IPADDR=172.16.38.170
GATEWAY=172.16.38.1

And retest?

Thanks,
Michal

Thomas,
any updates on that?

Michal

We are not able to reproduce this problem and have no response from reporter. We are closing this bz. If you met this problem feel free to reopen bz with additional data.