This is the default behavior of the MAX. The RADIUS RFC does NOT
the NAS to always try first the primary server. In fact, the idea of a
primary/secondary server is a Livingston idea that most people copied.
Ascend, suprise, uses the one the is responded the best. Until the
RADIUS server has a problem, it will not switch back.
> 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?
Point both of your RadiusNT servers at your primary DB. Thats the
easiest way to fix it. If your primary DB goes down, you can manually
switch them to the less recent, Secondary DB.
-- Dale E. Reed Jr. (firstname.lastname@example.org)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
For more information about this list, including removal,please see http://www.iea-software.com/maillist.html