Hello Cortney -
On Mon, 31 Jul 2000, Cortney Thompson wrote:
> Hi all,
>
> I am not sure if this has been covered before, but I couldn't find mention
> of it in the manual or the web site. I want to make sure I am correct on
> just how this multiple DBSource works. If I put multiple DBSource,
> DBUsername, DBAuth under the same <AuthBY SQL> how is this handled?
> e.g. <AuthBy SQL>
> DBSource dbi:ODBC:radius1
> DBUsername Test
> DBAuth Testing
>
> DBSource dbi:ODBC:radius2
> DBUsername Test
> DBAuth Testing
> </AuthBY>
>
> If the primary server (radius1) becomes unreachable does the secondary
> (radius2) take over or does radiator try to do load balancing over
> both. What I am looking for is a way for radiator to fall back on a
> secondary SQL server during maintenance on the primary. However I need it
> to return back to the primary as soon as it can be reached again and stay
> with that server until the next maintenance period. Is this how the
> multiple DBSource works or am I off key?
>
Radiator will connect to the first DBSource when it starts up. If that database
target becomes unreachable, Radiator will fail-over to the second DBSource
listed, where it will remain until that one becomes unreachable. Radiator does
not do SQL load balancing.
If you want Radiator to move back to the first DBSource, you will have to make
the second one become unavailable to force that behaviour.
This behaviour is documented in section 6.25 in the Radiator 2.16.1 reference
manual (in the opening paragraphs, before section 6.25.1).
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
