From: Karl Hanzel <karl@uc...> - 2005-07-28 21:00:14
Previously, i had writ:
> ...'Burned myself a KNOPPIX/OpenSSI Live CD, and am able to boot off of
> it just fine with a dual-Opteron box. With a crossover cable in place
> between 1st ethernet ports, i'm not getting a second box to boot via
'Finally figured out what was going on.
Our boxes have dual Gig-e ports (Broadcom). Fedora (that we've been
running on them) identifies the two ports differently than Knoppix. A
port with one MAC address is identified as "eth0" under one OS, but as
"eth1" under the other. I had assumed that what was eth0 under Fedora
would manifest itself as the "first ethernet port" found under Knoppix,
but that's not so.
'Dunno if there's a right/wrong*... but there's obviously at least a
difference, and that was what was throwing me. I moved my crossover cable
to the other ports, specified the other port's MAC addr, and -viola-.
The curious thing is that i thought i had tried that initially w/o
success. I probably did, but using a switch rather than a crossover
cable, and perhaps the switch is mis-configured (other tests indicate as
much). 'Something to be said for the simplicity of a cable in a situation
* i'd give the edge to Fedora, which hands the lower eth# to the lower
MAC# ... 'just seems more sensible.
UCAR/COMET Systems Administrator
From: Brian J. Watson <Brian.J.W<atson@hp...> - 2005-07-29 00:31:27
Karl Hanzel wrote:
> 'Finally figured out what was going on.
> Our boxes have dual Gig-e ports (Broadcom). Fedora (that we've been
> running on them) identifies the two ports differently than Knoppix. A
> port with one MAC address is identified as "eth0" under one OS, but as
> "eth1" under the other. I had assumed that what was eth0 under Fedora
> would manifest itself as the "first ethernet port" found under Knoppix,
> but that's not so.
It's not exactly Knoppix's behavior that you're seeing. Most Linux
distros, including Knoppix, configure NICs during the initscript phase
of booting. OpenSSI requires that the cluster interconnect NIC be
configured much earlier, during the initrd (boot ramdisk) phase before
the node joins the cluster (or forms it, in the case of the first node).
With OpenSSI for most distros, the driver needed for the cluster
interconnect is known at the time of building the initrd (this is done
when the OpenSSI kernel package is installed). On Knoppix, I had to
build the initrd before creating the ISO image, knowing that it would be
run on a wide variety of hardware. To solve this problem, I loaded all
the common NIC drivers into the initrd. I also added a crude algorithm
that loads each driver in alphabetical order until `ifconfig -a' returns
To make a long story short, whichever NIC's driver appeared first in
alphabetical order is the one designated eth0 by OpenSSI/Knoppix. The
behavior on regular Knoppix might be more like what you're used to on
Hope this helps explain things a bit better.