Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Duplicate Radius Entries
> Acct Timeout=1 ?? Should this be raised ??
Yes.
If you are seeing large numbers of duplicate accounting messages, then your
timeout is too short. Increase the timeout to something more appropriate
for your environment.
Try starting at 30 seconds.
You normally pick a maximum value that you are willing to wait before you
say that the server has failed. This is normally around 15-30 seconds,
depending on the number of clients the RADIUS server has.
Some people want to make sure that they only have a maximum of one outstanding
request per connection on the NAS. This works out to be about 80 seconds
with three RADIUS servers and an average of 12 minute connections.
ACTIME / (NSERVS * 3)
The upper bound for a reasonable timeout is probably around 420 seconds on
a fully loaded MAX with three servers. You can see you have quite a bit of
room to play before you come close.
(ACTIME * MAXIDS) / (NLINES * (NSERVS * 3))
ACTIME = (average connection time in seconds)
NLINES = (number of channels or connections on the NAS)
NSERVS = (number of accounting servers)
MAXIDS = (maximum number of active outstanding accounting messages)
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>