(RADIATOR) Load balancer for Radius

[Frank Danielson]

My first recommendation for load balancing Radiator is to use an instance or
two of Radiator in front of your existing servers to distribute requests.
Check out AuthBy LOADBALANCE and the related AuthBy VOLUMEBALANCE and AuthBy
ROUNDROBIN.

If you are not adverse to some coding you can use AuthBy SQLRADIUS to do
some cool stuff. For example you could have a script that sends
Status-Server requests to your downstream servers to see what the current
load is and if they are up or not and update your table of available servers
based on those results.

Of course all of your RADIUS clients should be configured with a primary and
secondary RADIUS server and appropriate retry timeouts.

0% packet loss during server failover may be an unrealistic goal.

Frank Danielson
Infrastructure Architect

ClearSky Mobile Media
56 E. Pine St.
Orlando, FL 32801
USA


-----Original Message-----
From: S H A N [mailto:shanali at magix.com.sg]
Sent: Thursday, May 27, 2004 10:34 AM
To: radiator
Subject: (RADIATOR) Load balancer for Radius


hi,
	i would like to seek recommendation on deploying load-balancers in
radius environment. i have expr. two load-balancers Cisco CSS10000 and
Foundary and observed that in case of failure of one of the radius servers
the fail-over doesn't really happen without 0% pkt loss.

	tips on common load-balancer deployment for radius techniques and
obvious watch-outs along with recommended load-balancer products are more
than welcome.

rgds,

S H A N

--
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.