Hi:

One simple method is instead of using the SystemImager kernel, use
UYOK kernel (which would essentially be your Red Hat kernel).  Barring
that, there should be a way to use udev to pin down which nic to use.

These information should be available in our Wiki: http://wiki.systemimager.org.

Good luck,

Bernard

On Wed, Sep 24, 2008 at 6:55 AM, Brodie, Kent <[EMAIL PROTECTED]> wrote:
> Been using SI a lot now- multiple architectures and systems.   Currently
> using 4.1.6-1.
>
> On my latest/newest set of servers (Sun x2200), I'm having a devil of a
> time with the network interfaces.
>
> On my golden client, my network scripts look like this:
>
> Ifcfg-eth0:
>
> # Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
> DEVICE=eth0
> BOOTPROTO=static
> BROADCAST=141.106.224.255
> HWADDR=00:1E:68:86:5F:18
> IPADDR=141.106.224.133
> NETMASK=255.255.255.0
> NETWORK=141.106.224.0
> ONBOOT=yes
>
> Ifcfg-eth1: (onboot-no, this is disabled)
>
> # Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
> DEVICE=eth1
> BOOTPROTO=dhcp
> HWADDR=00:1E:68:86:5F:19
> ONBOOT=no
> DHCP_HOSTNAME=zephir0.phys.mcw.edu
>
>
> Which basically says, Eth0 is the primary interface- the one I want to
> use, ETH1 is disabled in the config.
>
>
> But after the systems get imaged, I end up with this:
>
> Ifcfg-eth0:
> # Broadcom Corporation NetXtreme BCM5715 Gigabit Ethernet
> DEVICE=eth0
> ONBOOT=yes
> BOOTPROTO=dhcp
> HWADDR=00:1e:68:4a:2e:9b
>
> Ifcfg-eth1:
> DEVICE="eth1"
> ONBOOT="yes"
> BOOTPROTO="none"
> IPADDR="141.106.224.136"
> NETMASK="255.255.255.0"
> NETWORK="141.106.224.0"
> BROADCAST="141.106.224.255"
>
>
> Which is basically *backwards*- and unuseable, as ETH1 isn't even
> connected.
>
> I have tried overrides and such with no success.    I am aware that
> systemconfigurator can possibly be configured to order the Ethernet
> devices BASED ON MODULE NAME, but in my case-- eth0 and eth1 use the
> SAME module name.    So, that doesn't work.
>
> It seems like while my redhat kernel detects things in the order I want,
> while in the boel environment as the system is being imaged, the order
> is reversed.
>
> Any idea how I can control this?    Totally frustrating.   I have a
> *LOT* of nodes- I really do not want to have to log onto each one after
> I image it and re-write the network scripts.
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> sisuite-users mailing list
> sisuite-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sisuite-users
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to