Anycast applicable to Radius Server Farm ?
joe_hznm at yahoo.com.sg
Mon May 8 15:23:40 UTC 2006
> Can you indicate in more detail what the problems
> were with the L4
We seperate our Radius servers into two farms, each
farm has a L4 switch in front. To our understanding,
radius authentication info. and accounting info. of a
PPPoE session should be processed by the same Radius
server. So, although L4 switch provides a single IP
for BRAS configuration each BRAS is specified a real
server IP in L4 switch. So, there comes the problem:
1) Load is not balanced automatically but by human
estimation; there is server whose load is twice of
some other server.
2) L4 switch becomes bottleneck of service
availability. In past years, L4 switch caused several
times of service failure. Just last friday, L4 switch
does not repond to any network packets while its
ethernet interface seems OK.
3) As L4 switch is the only entrance to a single
server farm, DoS attack or some other kind of software
bug will surely degrade security level. While, a farm
using ECMP rely on server groups to resist DoS attack.
4) Maintence is a little bit costy. Any maintence ,
no matter on radius server or on L4 switch, need a
scheduled time window.
5) Service protection is hard ( as you mentioned as
'cascade' one). As there are two server farms, if one
farm failed it takes ten or more minute to migrate
those Radius traffic to the other farm. This is
So, we consider to find a more scable, reliable,
secure and automatic multi-farm radius solution.
> If the loadbalancing is done by source/destination
> IP address pairs,
> then you can have problems when a target goes down,
> as all of the
> source/destination IP address pairs will get
> switched to another
> target which then gets into difficulty and you end
> up with a
> cascading failure. It is generally preferable to
> have the
> loadbalancing done on a weighted per-packet basis,
> distributed according to round-trip times.
> Also note that you can only do per-packet
> loadbalancing with simple
> RADIUS, things like EAP that require multiple
> exchanges of RADIUS
> requests typically require state to be maintained in
> the single
> RADIUS server that is processing the entire EAP
> On 8 May 2006, at 14:07, Joe Shen wrote:
> > Hi,
> > we have a radius server farm. there is a L4 switch
> > installed behind all servers. Incoming AAA packets
> > switched by L4 switch to different servers.
> > In previous days we met a couple of problems with
> > switch which degraded our service a lot. Could it
> > possible to implement IPv4 Anycast architecture
> > radius server farm? Could it be any problem with
> > procedure?
> > Any advice will be highly appreciated
> > Joe
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Movies - Search movie info and celeb
> profiles and photos.
> > http://sg.movies.yahoo.com/
> Have you read the reference manual ("doc/ref.html")?
> Have you searched the mailing list archive
> Have you had a quick look on Google
> Have you included a copy of your configuration file
> (no secrets),
> together with a trace 4 debug showing what is
> 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.
Do you Yahoo!?
Yahoo! Movies - Search movie info and celeb profiles and photos.
More information about the NANOG