[RADIATOR] Radiator Failover between two Accounting Databases

[Heikki Vatiainen]

On 05/15/2012 04:52 PM, Traiano Welcome wrote:

> I'm currently trying to work out a configuration that will allow my radiator server to send radius accounting packets to a failover database pair, with only one active master at a time, my objective is high availability.
> 
> I see the <AuthBy SQLRADIUS> seems to offer the kind of functionality I want, i.e, account to a designated primary db and fail over to a secondary db if the primary is unavailable for a given period of time.
> 
> Would a configuration based on this clause work for failover between DBs in the way I've described or am I misunderstanding it's intended use ?

Hello Traiano,

I think <AuthBy SQL> is what you should consider. Try something like this:

<AuthBy SQL>
    DBSource        dbi:...primaryDb
    DBUsername      username_for_primary_DB
    DBAuth          password_for_primary_DB

    DBSource        dbi:...secondaryDb
    DBUsername      username_for_secondary_DB
    DBAuth          password_for_secondary_DB

    # Rest of settings
</AuthBy>

In other words, define DBSource, DBUsername and DBAuth twice if you have
two databases. That will enable fail over functionality.

For more, please see the reference manual for version 4.9, section "5.31
<AuthBy SQL>". There is one paragraph discussing how the failover with
multiple databases works.

Thanks!
Heikki

-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS,
TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS,
NetWare etc.