Red Hat Bugzilla – Bug 125652
installer can use eth0 but not eth2 (all adapters are Broadcomm)
Last modified: 2013-07-02 22:20:29 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510
Description of problem:
(all this is from memory, I am currently in my hotel. I could not file
earlier as I was stuck in a server room without external connectivity)
When trying to kickstart an IBM x445 with 4 Broadcomm network
adapters, I am able to use eth0 as ksdevice, but not eth2.
Customer tells me they were unable to use eth2 with RHEL 3 U1 but that
the problem went away on a subsequent up2date run. (Their machine has
no problem using eth2 under kernel 2.4.21-15.EL, which is weird
because kernel-BOOT-2.4.21-15.EL exhibits the problem descibed below.)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot the RHEL 3 U2 i386 kernel and initrd via pxe
2. attempt a kickstart install with ksdevice=eth2
3. DHCP address is assigned fine at boot time, but only then
Actual Results: When the kernel has booted and the installer tries to
get an IP address via DHCP, it times out.
The DHCP server sees no request coming in.
I did verify that eth2 is what I expect (i.e. the MAC address is the
right one), I did also verify that the booted kernel is indeed
Setting an IP address by hand (when anaconda prompts me to do so) does
not help either, the interface is reported as up but I am both unable
to ping another machine.Trying to ping the machine from an external
box is not possible either (host unreachable)
arp shows me entries with 'incomplete', ther eis not a singe good entry.
setting the arp entries by hand does not help either.
Expected Results: being able to kickstart over eth2
switching the cables in eth0 and eth2, followed by using ksdevice=eth0
works just like expected.
The problem is that customer will have to rewire 30+ machines and
update all documentation (MAC addresses are documented here).
I'll get customer to subscribe to this bug as I am only on-site for
one more day.
It would be really nice if we could give an estimate on how long this
may take to fix so that customer can decide between rewiring and waiting.
tg3 updates should have fixed this?