Load over the 100mb port and then run the cluster over the 1000mb port.
Inorder to load over the 1000mb port you just need a new kernel for
systemimager.

Brian Messenger

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Morgan
Sackett
Sent: Thursday, October 17, 2002 9:35 AM
To: [EMAIL PROTECTED]
Subject: Re: [Oscar-users] gigabit and oscar


So does the new systemimagaer now work with clients that only have GigE?
  Currently only our server is using GigE.  The clients are all stuck on
100mb as it was too much of a pain in the neck to have it automatically
load from 100mb, then reconfigure itself to load on the GigE.
Especially with all of the changes that would have to been made in the
dhcpd.conf on the server.


Sean Dague wrote:
> Can you try the latest systemconfigurator 2.0.1, I changed the ordering
> here, and it may just work for you all now.
>
>       -Sean
>
> On Tue, Oct 15, 2002 at 09:58:41AM -0700, Brian Messenger wrote:
>
>>It was not really oscar, It was systemconfigurator.  Systemconfigurator
>>seems to 'flop' the two interfaces when it is run on that particular
board.
>>You might want to just fix the modules.conf on one and copy it to the
>>others.  I know there is a more graceful way of making systemconfigurator
>>not do this, but I am unsure what I did to last time.
>>
>>Brian Messenger
>>  -----Original Message-----
>>  From: [EMAIL PROTECTED]
>>[mailto:[EMAIL PROTECTED]]On Behalf Of Tim
>>  Sent: Tuesday, October 15, 2002 8:03 PM
>>  To: [EMAIL PROTECTED]
>>  Subject: [Oscar-users] gigabit and oscar
>>
>>
>>    I am building an Oscar cluster using v1.3 with 17 nodes including
master
>>with rhat 7.2 on a supper micro p4dpr-igm motherboard - which consist of
>>dual onboard nics 10/100 and 100/1000 intel gigabit adapter,, I was able
to
>>install the compute nodes fine, but as soon as I went into the clients I
>>could not ping out at all, so what I found out was that when Oscar
installed
>>its image it aliased eth0 as e1000(gig) and eth1 as eepro100(10/100)  in
>>/etc/modules.conf so I simply did and ifdown on eth0 and and ifup on eth1
>>that resolved my pinging issue, but now I could only ping with 10/100 and
>>when I tried to bring the eth0 up and switch the connection over to the
gig
>>connection I could not ping and still can not, does anyone know what I
might
>>do to fix this??
>>
>>
>>
>>  PS. I am using a gig switch that is working fine.. and gigE cable
>>
>>
>
>





-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users




-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to