All of the below refers to RadiusNT...
I don't know what it's like with other NASes, but with Ascend Maxes, there
are 3 IPs for AUTH and 3 IPs for ACCT for radius. If for some reason it's
not getting a response from the first, it'll try the second. If it doesn't
get a response there, it'll go to the third, then to the first... This
DOES occur with NT running just fine. Also, radius could be running
fine--if there's some delay in response time, the Max will switch. This
happens to us all the time. Radius never dies on us, but every so often
the Maxes will have some kind of problem communicating with it (I'm
guessing it times out or something), and accounting and/or authentication
will start going through our backup radius server (if radius is turned on).
As soon as I turn off radius on the backup server, everything goes right
back to the primary (without the primary radius server ever being
disabled/crashed/etc.)
Josh Hillman
hillman@talstar.com
> > De: Josh Hillman <admin-maillist@talstar.com>
> > Para: RadiusNT@iea-software.com
> > Assunto: Re: backup SQL servers?
> > Data: Quarta-feira, 3 de Dezembro de 1997 16:02
> >
> > From: Brian Lube <brian@mpinet.net>
> > Is there a way in RadiusNT to tell it to look at a different SQL server
> if
> > it does not get a response from the initial one? We are setting up a
> > backup SQL server, and I would like to have the Radius server be able
to
> > switch SQL servers on the fly if it is possible.
> >
> >
> > Go into your NAS and assign a secondary (and if applicable, tertiary)
> > radius server for either AUTH and/or ACCT. If the normal radius server
> > doesn't respond within a given period of time, it'll try the secondary
> and
> > so on.
> >
> > Josh Hillman
> > hillman@talstar.com