We just tried using Mike's hint, but then on reboot the client started just eth0 and ignored eth1.
Do you have more details, such as WHEN is the correct time to edit that file? Teresa -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Michael Chase-Salerno Sent: Friday, July 26, 2002 2:50 PM To: Teresa Carrigan Cc: Oscar-users List Subject: Re: [Oscar-users] two NICs per client a problem again You can force the eth1 to be used on the nodes by adding the following to the systemconfig.conf in the image(s), eg /var/lib/systemimager/images/oscarimage/etc/systemconfig/systemconfig.conf [INTERFACE0] DEVICE = eth1 Mike On Fri, 2002-07-26 at 14:43, Teresa Carrigan wrote: > Yes we did get our cluster to run by the workaround of changing the private > network to use the integrated NICs and the public network the nice new "we > bought them just for the cluster project" NICs. > > The integrated NICs are 3com 3C920, supposedly compatible with 3C905C-TX. > Besides all the warnings about "avoid using 3com cards" we would *really* > prefer to use the NICs that we bought for the cluster project. > > >From what we can determine/guess, Oscar sets up the clients to use their > eth0 cards in cluster communications. Is there a way to change this so that > the clients use their eth1 cards instead? Or a way to fool the clients into > ignoring the integrated NIC, which will be used when the machines boot to > Win2K? > > Teresa W. Carrigan > Professor of Computer Science > Blackburn College > Carlinville, IL 62626 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users
