| On Feb 20, 2004, at 6:41 AM, Alan DeKok wrote: | | > "Sudhagar Chinnaswamy" <[EMAIL PROTECTED]> wrote: | >> The failover doesn't work if the "synchronous" parameter is set to | >> "yes". Can someone explain this behaviour ? | > | > It's probably a bug in the server. I don't think that | configuration | > has been well tested. | > | Isn't this actually correct? According to the DOCS, if Synchronous is | set to Yes, then all of the other parameters should be set to 0. How | will the server 'know' what the retry_delay, retry_count, and | dead_time | are?
Radius client (NAS or any external Radius server) may not have the information that more than one Radius server serves this particular realm. I believe, mostly the Radius server at top of the hierarchy will have this fail-over information. Also configuring FailOver at large volume of NASes is difficult compared to configuration at Radius Server, which is fewer in number compared to NAS. It might be a good idea to support fail-over in this configuration too.
The recommended configuration is to set 'Synchronus = no' for that setup for specifically the reasons mentioned.
You can't have both the NAS *and* the RADIUS server handling retransmissions and timeouts for what are hopefully obvious reasons.
If you need failover, you cannot set 'Synchronus = Yes'.
-Chris
-- \\\|||/// \ StarNet Inc. \ Chris Parker \ ~ ~ / \ Wholesale Internet \ Director, Engineering | @ @ | \ http://www.starnetusa.net \ (847) 963-0116 oOo---(_)---oOo--\------------------------------------------------------ \ Outpace the Competition - http://www.getmespeed.com
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
