Dear All,

I am a bit of a linux newbie and have run into a problem.

i am trying to configure my cluster to run the Rocks cluster distro. This distro has some rather rigid rules regarding the naming of ethernet controllers

On the frontend machine (the one that everyone logs into)

eth0 must be the private network controller 10.1.1.1/255.0.0.0

eth1 must be the pulic network controller xxx.xxx.xxx.xxx/255.255.255.0

other controllers names are not important

OK, so here goes with my problem:
My machine has two onboard BC5705 controllers and one PCI D-Link DFE-570-TX controller.

I want to configure the machine such that

eth0 = BC5705 controller (fast for use with local traffic)

eth1 = D-Link DFE-570-TX controller (slow because it will ultimately be limited by the LAN connected to my machine)

eth2 = the other BC5705 (I intend to bond this with the other BC controller to increase bandwidth bewteen cluster nodes)

The distro is based upon RedHat and uses
ifcfg-eth* files in /etc/sysconfig/network-scripts/ to give IP addresses to each eth interface

I have configured them such that

[ifcfg-eth0]
DEVICE=eth0
onBOOT=yes
BOOTPROTO=static
IPADDR=10.1.1.1
NETMASK=255.0.0.0

[ifcfg-eth1]
DEVICE=eth1
onBOOT=yes
BOOTPROTO=static
IPADDR=***.***.***.*** [IP of machine]
NETMASK=255.255.255.0

[ifcfg-eth2]
DEVICE=eth2
onBOOT=yes
BOOTPROTO=static
IPADDR=10.1.1.2
NETMASK=255.0.0.0

and then in /etc/modules.conf

[modules.conf]
alias eth0 tg3
alias eth1 via-rhine
alias eth2 tg3

However, I am getting some errors upon boot..

I think that what is happening (though I am not sure why??) is that when the tg3 module loads up it finds any compatible interfaces and immediately assigns them tg3 so the ordering in my modules.conf file is ignored and when it gets to eth2 is gets confused....


Does anyone have any suggestions to fix my problem,

thanks in advance

Martyn