Date: Wed, 5 Dec 2001 10:34:56 -0500
Sender: "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From: Don Henderson <don.henderson@US.PWCGLOBAL.COM>
Subject: Re: Q about Microsoft NLB and Sas/IntrNet
Content-type: text/plain; charset=iso-8859-1
Yes, you have the right idea. There isn't any magic support for running
loadmgr on multiple machines on a cluster. The birdies at SAS tell me that
it would be a nice feature to add for failover capability. So maybe the
IntrNet users out there might want to provide feedback to Tech Spt. Maybe
it will make next years ballot if there is enough demand. What you should
- install load manager on one of the servers - choose whichever one is
perhaps faster, more stable, whatever
- the broker.cfg files on each machine should point to loadmgr on a
specific machine, not the cluster
- all of the broker.cfg's should stay in synch. If you wants to switch
loadmgr to a new machine (e.g., if the loadmgr system fails or is shut
down) you'll have to swap in new broker.cfg files manually.
"Søren Damgaard Laursen" <sdl@TDK.DK> wrote in message news:
> Hi Francesco
> Thanks for your quick response, but 'unfortunately' I know all of these
> things allready.
> I was just wondering if the was any speciel considerations to take into
> account regarding Sas/IntrNet, loadmanager, etc. when we want to use
> technologies on a web server cluster.
> "Francesco" <email@example.com> wrote in message
> > Hi Soren, you install the Load Manager on the machine where the web
> > resides, in your case your Win 2000 Box. On Windows, simply click in
> > program group -> IntrNet -> Create New IntrNet Service and then select
> > 'Configure the Load Manager'. This will create a Directory which will
> > contain
> > the Load Manager log as well as Load Manger program group which
> > icons to stop and start the load manager either interactively or as a
> > Windows
> > service.
> > To use the Load Manager you then have to create one (or more if you
> > them)
> > Pool Service, again from the Create New IntrNet Service icon. Just
> > the
> > simple steps. The last step in the wizard will show you the text to be
> > included in
> > your broker.cfg file. Something like this:
> > PoolService default
> > ServiceDescription "Default Pool Service"
> > ServiceAdmin "Admin Name"
> > ServiceAdminMail "firstname.lastname@example.org"
> > Server servername
> > ServiceTimeout 3600
> > Port 10
> > MinRun 3
> > IdleTimeout 30
> > FullDuplex True
> > ServiceLoadManager loadmanager_server:5001
> > SasCommand "\"d:\\Program Files\\SAS
> > \"d:\\SAS Services\\default\\appstart.sas\" +
> > -rsasuser -noterminal -nolog -SYSPARM "
> > # Uncomment the following lines if Spawner is used to start
> > # the SAS system (required if Load Manager is not running
> > # on this node.)
> > # SpawnerPort [port]
> > # Username [username]
> > # Password [password]
> > All you have to is to change 'servername' to your UNIX box where the
> > SAS server of the application dispatcher resides and this should work.
> > Please note that, unlike socket services, you do not specify a port for
> > the Pool Services. The Load Manager will assign automatically ports
> > whenever a SAS server is started. The only port you have to specify
> > esplicitly id the port used by the Load Manager (5001 in the example
> > above).
> > There are loads of other options that can be set, but I send you the
> > documentation for them.....
> > Hope this helps.
> > Regards, Francesco
> > Nemesi Ltd.
> > United Kingdom
> > "Søren Damgaard Laursen" <email@example.com> wrote in message
> > news:firstname.lastname@example.org...
> > > Hi there,
> > >
> > > In the near future we are considering moving our web-application
> > > win nt web-server and DEC Unix as a backend using Sas/Intrnet and
> > > manager, over to a windows 2000 Cluster utilizing Network Load
> Balancing -
> > > but still maintaining the unix as backend, of course!. This cluster
> > consists
> > > of two identical servers.
> > >
> > > Does anyone have any experience regarding the technical setup of the
> > > broker.cfg and the loadmanager.
> > >
> > > More specifically:
> > > Do we install the loadmanager on one server or both? Or should we
> > it
> > > on a different server outside the cluster?
> > > Are the broker.cfg identicial on the two servers?
> > >
> > > Any other tips are welcome..
> > >
> > > Thanks in advance
> > > Søren Laursen
> > > TDC Services IT.
> > >
> > >
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any