I think there are some previous threads on the subject of using a load balancer. The best thing to do is not use a load balancer, as it creates a single point of failure. Better to use the multiple radius server parameters built into most NASes.
I use 1 sql server per FR - running on the same server. This is very simple which suits me fine. Use at least 2 FR servers. For max reliability they should each be mulit-homed or, better yet, diversely located in different locations on different upstream providers. There are a variety of ways to replicate the data between them. The best (IMHO) is probably to have a master sql database (maybe on your provisioning system) and replicate it out to the radius servers. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Joel Vandal > Sent: Wednesday, February 19, 2003 2:33 PM > To: [EMAIL PROTECTED] > Subject: Re: most redundant Radius system > > > > >Any idea on the redundant Radius system scheme with MySQL? > > Our redundant setup: > > 2 x Radius server > 1 x Load Balancer (Alteon) (hehe bought one on ebay for 20$us good deal) > 3 x XMLRPC server > 3 x mySQL server > > Our Radius server connect to our Load Balancer that send request to one of > our 3 XMLRPC server. > > Each XMLRPC server send Authentication/Authorization request to > mySQL server > (round-robin/failover) > > For Accounting request, if the main mySQL server is down, then the request > is "cached" and re-send when the main mySQL is running. > > Each XMLRPC & mySQL server are on a "virtual server" so we need only 3 > computers for these task but each computer are RAID5 & RAID50 hardware > adapter and multiple power supply (2 x HP LC2000 and 1 x HP LH4 Quad-Xeon) > > -- > Joel Vandal > > > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
