(RADIATOR) LNS failover / load balancing

Jerome Fleury jeje at jeje.org
Thu Apr 28 15:32:02 CDT 2005 

This is mostly a load balancing issue rather than a failover one. Say you
have for example a LNS that can handle 3 times more sessions than an other
one, you need your radius to know that and load-balance the sessions
accordingly. 

An other point is that I have no clue how the LAC handles such a request:

Tunnel-Server-Endpoint = "x.x.x.x, y.y.y.y"

how does it decide that an LNS is not available ? on which criteria ? (what
are the timers, etc.) I prefer handling my own criteria, which I know are
good according to my network.

--On mercredi 27 avril 2005 11:47 +0200 "PREVOSTO, Laurent"
<laurent.prevosto at neuf.com> wrote:

> I don't really get it :
> 
> As I understand things, the LAC should be responsible for LNS failover,
> not the radius. Ideally, the radius just sends its conf to the LAC, for
> instance something like Tunnel-Server-Endpoint = "x.x.x.x, y.y.y.y" so
> you have Y as a backup of X (if this is the kind of conf your LAC can
> handle).
> 
> Of course you can use some hook that would test LNS availability before
> sending back the reply to the LAC but if you have too many of such things
> you may end up with a real bloated radius which is probably something you
> would like to avoid.
> 
> Regards
> 
> Laurent
> 
>> -----Message d'origine-----
>> De : owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] De
>> la part de jose.burgos at ono.es
>> Envoyé : lundi 25 avril 2005 12:16
>> À : radiator at open.com.au
>> Objet : RE: (RADIATOR) LNS failover / load balancing
>> 
>> 
>> Hello,
>> 
>> We are also interested in the failover issue (more than in load
>> balancing). Is it possible to define a main LNS and a backup one via
>> Radiator configuration in a simple way? In our config we have defined a
>> LNS for every LAC (here I add an example of what we have):
>> 
>> DEFAULT      NAS-IP-Address = "x.x.x.x"
>>              Tunnel-Type = 3, Tunnel-Medium-Type = 1,
>> Tunnel-Server-Endpoint = "y.y.y.y"
>> 
>> Thanks and regards,
>> 
>> 	Jose
>> -----Mensaje original-----
>> De: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] En
>> nombre de Hugh Irvine Enviado el: viernes, 22 de abril de 2005 1:34
>> Para: TEST
>> CC: radiator at open.com.au
>> Asunto: Re: (RADIATOR) LNS failover / load balancing
>> 
>> 
>> 
>> Hello -
>> 
>> The way I have done this in the past is with a session database in an
>> SQL database (Oracle in this particular case) with stored procedures in
>> the database to do the distribution of sessions accross the LNS
>> devices.
>> 
>> regards
>> 
>> Hugh
>> 
>> 
>> On 22 Apr 2005, at 02:54, TEST wrote:
>> 
>> > 
>> > 
>> > You're so right, sorry!
>> > 
>> > But this message is really Radiator related (query replace missed);
>> > before purchasing a licence I need to verify this crucial point. So
>> > how can I load balance Tunnel endpoints over several LNS cisco routers
>> 
>> > in a failure proof way.
>> > 
>> > Thank you.
>> > 
>> > Regards.
>> > 
>> > 
>> > Ingvar Berg (LI/EAB) wrote:
>> > 
>> >> You may have more success at the freeradius mailing list :-) /Ingvar
>> >> 
>> >> 
>> >>> -----Original Message-----
>> >>> From: owner-radiator at open.com.au
>> >>> [mailto:owner-radiator at open.com.au]On
>> >>> Behalf Of TEST
>> >>> Sent: den 21 april 2005 14:26
>> >>> To: radiator at open.com.au
>> >>> Subject: (RADIATOR) LNS failover / load balancing
>> >>> 
>> >>> 
>> >>> 
>> >>> Hi All,
>> >>> 
>> >>> I'm using freeradius1.0.2 to provide L2TP sessions authentications
>> >>> between 2 Redbak BAS and 3 Cisco LNS I can negociated L2TP LNS
>> >>> Tunnel endpoint sessions on a user base (staticly), but I would like
>> 
>> >>> to negociate the tunnel end point in a dynamic way to integrate
>> >>> failover and load balancing mechanisms between my 3 LNS.
>> >>> 
>> >>> So how can I permanently change the Freeradius Tunnel attributes
>> >>> based on the LNS activity or viability? Is some LNS "watchdog"
>> >>> provided to accurate LNS load activity in FreeRadius DB?
>> >>> 
>> >>> Thanks for your help.
>> >>> 
>> >>> With regards.
>> >>> 
>> >>> 
>> >> 
>> >> 
>> >> --
>> >> Archive at http://www.open.com.au/archives/radiator/
>> >> Announcements on radiator-announce at open.com.au
>> >> To unsubscribe, email 'majordomo at open.com.au' with 'unsubscribe
>> >> radiator' in the body of the message.
>> >> 
>> >> 
>> >> 
>> > 
>> > --
>> > Archive at http://www.open.com.au/archives/radiator/
>> > Announcements on radiator-announce at open.com.au
>> > To unsubscribe, email 'majordomo at open.com.au' with 'unsubscribe
>> > radiator' in the body of the message.
>> > 
>> > 
>> 
>> NB:
>> 
>> Have you read the reference manual ("doc/ref.html")?
>> Have you searched the mailing list archive
>> (www.open.com.au/archives/radiator)?
>> Have you had a quick look on Google (www.google.com)?
>> Have you included a copy of your configuration file (no secrets),
>> together with a trace 4 debug showing what is happening?
>> 
>> --
>> Radiator: the most portable, flexible and configurable RADIUS server
>> anywhere. Available on *NIX, *BSD, Windows, MacOS X.
>> -
>> Nets: internetwork inventory and management - graphical, extensible,
>> flexible with hardware, software, platform and database independence.
>> -
>> CATool: Private Certificate Authority for Unix and Unix-like systems.
>> 
>> --
>> Archive at http://www.open.com.au/archives/radiator/
>> Announcements on radiator-announce at open.com.au
>> To unsubscribe, email 'majordomo at open.com.au' with
>> 'unsubscribe radiator' in the body of the message.
>> 
>>  La informacion incluida en el presente correo electronico es
>> CONFIDENCIAL, siendo para el uso exclusivo del destinatario arriba
>> mencionado. Si usted recibe este mensaje y no es el destinatario senalado
>> le informamos de que esta prohibida cualquier utilizacion del mismo y le
>> rogamos que nos lo notifique inmediatamente y nos lo devuelva a la
>> direccion ariba mencionada.
>> En la medida en que el envio de este mensaje de correo electronico se
>> derive de las relaciones profesionales de CABLEUROPA, S.A.U. (ONO) con
>> Vd., le informamos de que vamos a tratar automatizadamente y de manera
>> confidencial su direccion de correo electronico, asi como el resto de los
>> datos de caracter personal que nos facilite o nos sean cedidos por un
>> tercero (los habitualmente incluidos en una tarjeta de visita), en un
>> fichero del que CABLEUROPA, S.A.U. (ONO) es titular y responsable, con la
>> finalidad de gestionar la agenda de contactos de nuestros empleados,
>> becarios y personal externo al servicio de la compania con centro de
>> trabajo en los locales de esta, para el envio de comunicaciones
>> profesionales y/o personales. Vd. consiente el tratamiento de los citados
>> datos para estos fines, pudiendo ejercitar sus derechos de acceso,
>> rectificacion, cancelacion y oposicion en ONO (Departamento Asesoria
>> Juridica, calle Basauri, 7-9, Urb. La Florida, Aravaca 28023 Madrid.
>> 
>> --
>> Archive at http://www.open.com.au/archives/radiator/
>> Announcements on radiator-announce at open.com.au
>> To unsubscribe, email 'majordomo at open.com.au' with
>> 'unsubscribe radiator' in the body of the message.
> 
> --
> Archive at http://www.open.com.au/archives/radiator/
> Announcements on radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.



jeje.

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.

More information about the radiator mailing list