(RADIATOR) Radiator cluster or resilience

[Hugh Irvine]

Hello Eddie -

As a RADIUS server, Radiator is usually set up and configured on (at  
least) 2 machines (primary and secondary).

All RADIUS client devices are configured with both primary and  
secondary RADIUS server targets, and automatically failover to the  
secondary if there is no response from the primary.

More complex arrangements are possible utilising load-balancers and  
so on.

For an overview of the RADIUS protocol please refer to the RFC's  
("doc/rfc2865.txt" and "doc/rfc2866.txt" or www.ietf.org).

regards

Hugh


On 27 Apr 2008, at 02:22, Eddie Chu wrote:

> Dear Sir,
>
>   How can Radiator achieve cluster, resilience or auto failover  
> requirement.
>
>
> Eddie Chu
>
> --
> 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.



NB:

Have you read the reference manual ("doc/ref.html")?
Have you searched the mailing list archive (www.open.com.au/archives/ 
radiator)?
Have you had a quick look on Google (www.google.com)?
Have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
Have you checked the RadiusExpert wiki:
http://www.open.com.au/wiki/index.php/Main_Page

-- 
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, MacOS X.
Includes support for reliable RADIUS transport (RadSec),
and DIAMETER translation agent.
-
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.


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