Must have hit reply instead of reply to all by mistake. I stand chastised.
I am not sure what the best way of solving this problem is, but it seems like it would be easiest to either turn off the ADDS while you were installing (if that is possible) or block the oscar subnet from accessing them. You could do that with some additional firewall rules or by just not connecting the switch to that network. All my ideas are hacks though, and don't really solve your problem elegantly. That might be something to put in a feature request (on sourceforge) for inclusion in a future version. On Fri, 25 Mar 2005 08:24:58 +0200, Mustaki Oren <[EMAIL PROTECTED]> wrote: > Hello again > > That's exactly what im trying to do > But for some reason the node after booting > tries to get the boel_binaries.tar.gz from the > Active Directory Domain Server and not from > The Head Node. > > Thanks > > BTW I think you should reply to the mailing list > So everybody can participate and learn > > Oren > > -----Original Message----- > From: Michael Edwards [mailto:[EMAIL PROTECTED] > Sent: Friday, March 25, 2005 7:09 AM > To: Mustaki Oren > Subject: Re: [Oscar-users] DHCP Issues with Oscar Cluster in Active > Directory Domain > > Oscar currently assumes that all services are running on the head node. > If you want to run on some other configuration, I would suggest first > setting up a traditional oscar head node on whatever machine you intend to > be the "head node" (your gateway machine or file server) and then once > everthing is set up figure out what changes need to be made to the various > images to support your more complicated network setup. > > On Thu, 24 Mar 2005 21:17:51 +0200, Mustaki Oren <[EMAIL PROTECTED]> > wrote: > > Greetings Everybody > > > > I've installed Oscar 4.0 On Linux Red Hat ES 3 Update 3 Configured it > > According to the notes I found in the "oscar4.0-readme.rh3as.txt " > > Document. > > The Oscar server resides on single subnet network which is 255.0.0.0 > > And begins with 8.xxx.xxx.xxx > > > > The Oscar server address is 8.90.209.1 ( 255.0.0.0 ) The node Which im > > trying to install is 8.90.209.2 ( 255.0.0.0 ) > > > > The Active Directory Domain Controllers Address is 8.130.39.1 ( > > 255.0.0.0 ) And 8.130.39.3 ( 255.0.0.0 ) The AD servers act as DHCP > > servers as well > > > > I've finished al the steps in the wizard and boot the first node The > > node start booting from the network Get pxelinux.cfg/default And start > > downloading the image. > > > > When it gets to the following part > > > > get_boel_binaries_tarball.tar.gz > > > > Instead of running : > > Rsync -av 8.90.209.1::/boot/i386/boel_binaries.tar.gz > > /tmp/boel_binaries And trying to get the tarball from the oscar server > > It runs: > > Rsync -av 8.130.39.1::/boot/i386/boel_binaries.tar.gz > > /tmp/boel_binaries It tries to get the tarball from the AD DHCP server > > And fails obviously > > > > Is there a way to configure the nodes to ignore certain DHCP servers > > Or to use only a Proffered one ( without creating a new subnet ) ? > > > > Thanks in Advance > > > > ------------------------------------------------------- > > SF email is sponsored by - The IT Product Guide Read honest & candid > > reviews on hundreds of IT Products from real users. > > Discover which products truly live up to the hype. Start reading now. > > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > > _______________________________________________ > > Oscar-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/oscar-users > > > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Oscar-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-users
