Re: [RadiusNT] Concurrency Control

Jeff Woods ( )
Fri, 25 Jun 1999 13:28:11 -0400

Typo/brain fart on my part -- yes, the CallsOnline table, which is not
cleared in the case of a reboot. I'd rather have concurrency done by SNMP
than by examining this table. Folks have said it is doable, but I don't
find the documentation for it....

At 01:03 PM 6/25/99 -0400, you wrote:
>From: Jeff Woods <>
> >I believe the concurrency checks that RadNT 2.5 performs are invalid. By
> >relying solely on the contents of the Calls table, you create
> >problems. For example, if a NAS spontaneously reboots (as is happening
> >frequently with the latest PM-3 code), the calls table isn't cleared, and
> >Stop records never come. Anyone who was online at the time of the reboot
> >CANNOT log on again until someone manually clears the calls table. Since
> >these reboots are so common with the PM-3 these days, this is a Bad Thing
> >(tm). Wouldn't using an SNMP check (or in the case of multiple NAS's, a
> >series of checks) to determine if the user is online, and how many times,
> >be better?
>I don't know of a perfect solution to this, but the Calls table isn't
>related to this. It's the CallsOnline "view."