Re: RadiusNT session identifier

Mitchell B. Wagers ( (no email) )
Tue, 24 Feb 1998 15:38:11 -0800

You need a scheduled reboot cycle based on the number of calls a NAS gets.
Eventually, there will be duplicates, the ID's just aren't infinite. So,
you have to clear the calls table on a scheduled bases too. I compile ours
into a very detailed analysis table(s) every month, because that is our
billing cycle. I reboot the access servers every 4 months or so.

You won't get duplicate primary keys if the primary keys are in place. If
everything else is working correctly, then you might want to increase the
time that NAS waits for a response before retransmitting.

At 02:24 PM 2/24/98 -0500, you wrote:
>Does the AcctSessionID originate from the NAS? We are getting duplicate
>primary keys for the Calls table and was wondering if this could be from
>shutting off the USR Total Control.
>Thanks, Ray
>At 10:11 AM 2/24/98 -0800, you wrote:
>> wrote:
>>> Does RadiusNT (and RADIUS generally) maintain a kind of session identifier
>>> in alfanumeric form, that could be used to resolve nested
>>> start-start-stop-stop patterns of the same user, in the authentication
>>> in text mode.
>>The RADIUS protocols specifies that each accounting packet should
>>have a AcctSessionID variable that is unique for each session from the
>>NAS. You can use the NASIdentifier and AcctSessionID to track start
>>and stop pairs.
>>> How can I control (enable-dissable) multiple concurrent logins?
>>You have to use RadiusNT with a database (ODBC mode).
>>Dale E. Reed Jr. (
>> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
>> Internet Solutions for Today |
>> ----------------------------------------------------------
>> RadiusNT Mailing List
> ----------------------------------------------------------
> RadiusNT Mailing List