Imagine if your 'primary' server was down. Each authentication/accounting
request would have to 'double-dip' to get responded to in the event of a
prolonged outage.
What we've done over here is set up a scheduled task that stops/restarts
radius on our secondary servers occasionally to 'nudge' radius back onto the
primary.
= K
-----Original Message-----
From: Brandon Bryant <nailer@midlink.com>
To: 'emerald@iea-software.com' <emerald@iea-software.com>
Date: Monday, December 21, 1998 8:58 AM
Subject: [Emerald] Revelation
>I ran into an interesting situation that I was wondering if anyone else has
>seen.
>
>We have two Ascend Maxes and two radius servers running RadiusNT. In the
>MAX setup, I set the primary auth server and the secondary auth server
>accordingly.
>
>Now, what is happening is when the primary goes down or is unavailable, the
>MAX switches to the secondary. Then never switches back to the primary.
>
>So, we replicate our db at night from primary to secondary. So any change
>we make to the db during the day is null and void if the server was down
>before. It was driving us nuts until I figured that out over the weekend.
> I'm going to start a ticket with Ascend today, but has anyone else run
>into this, and if so, how did you fix it?
>
>
>For more information about this list, including removal,
>please see http://www.iea-software.com/maillist.html
>
For more information about this list, including removal,
please see http://www.iea-software.com/maillist.html