I've done it -- currently in production serving an environment with over 80,000 users. No issues.
If you're load balancing TACACS+ you should enable stickiness so that the session remains pinned to one Radiator server. If load balancing simple RADIUS, just do a simple serverfarm and load balance with a "least connections" or round robin LB algorithm. Hope this helps. -james On Thu, May 10, 2012 at 5:15 AM, Janssen, G.H.C. (Gaston) <[email protected]> wrote: > Hi, > > We'd like to load balance RADIUS requests over several RADIATOR servers. > Therefor we will use an external hardware load balancer: a Cisco ACE (service > module). > Is there anyone who has experience with this kind of combination, i.e > RADIATOR & Cisco ACE. > > Any (white) papers on this subject are welcome, either so any ACE > configuration examples. > > We are particulairy interested in field experiences in the combination Cisco > ACE / RADIATOR. > > > (We already have taken notice of the Cisco configuration guide "Configuring > RADIUS Load Balancing" > which in genaral describes it, but is not product specific (in this case > RADIATOR) :) > > Regards, > Gaston > > _______________________________________________ > radiator mailing list > [email protected] > http://www.open.com.au/mailman/listinfo/radiator _______________________________________________ radiator mailing list [email protected] http://www.open.com.au/mailman/listinfo/radiator
