We use many radius servers over internet, located in differenct countries, and we use a single central database. We have a huge amount of the auth-request/accaunt-request (VoIP). All account info we replicate from each radius to the central database server where transaction monitor insert them to a database. All changes related to users replicated to the radius servers where special back-end inserts it to the fast-users file. In such way we have a simple single point of manage everything. Everything except database (IBM DB2) are self-made. In case of a radius server will crash, after fixing problem it is pushed the info it missed. If we want to stop a database, or transaction manager, we do it safe, because of replicated protocol used in both direction - from and to radius. In case of huge amount of CDR, we have not small traffic with CDR only (even we pack it to make it smaller), we can't use any XML-RPC because it will grow the traffic.
On Yesterday, Tim D. McCracken wrote: > > 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 > Gregory G. V. --------------- Any opinions in this posting are my own and not those of my present or previous employers. According Isham Research's Devil's IT Dictionary mainframe is: "an obsolete device still used by thousands of obsolete companies serving billions of obsolete customers and making huge obsolete profits for their obsolete shareholders. And this year's run twice as fast as last year's." - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
