Where is this feature documented? Thanks!
At 12:43 PM 6/25/99 -0400, you wrote:
>Yeah, SNMP concurrency checking is already in RadiusNT - the Enterprise
>edition. We upgraded to it last week and it works like a champ.
>
>Dave
>
>===================================================
> I N T E R N E T F O R B U S I N E S S
>Mercury Network http://www.tm.net/
>129 Ashman St / P O Box 117 Voice: 517-837-3790
>Midland, MI 48640-0117 Fax: 517-837-3780
>===================================================
>
>-----Original Message-----
>From: Jeff Woods <jwoods@deltacomm.com>
>To: radiusnt@iea-software.com <radiusnt@iea-software.com>
>Date: Friday, June 25, 1999 12:37 PM
>Subject: [RadiusNT] Concurrency Control
>
>
> >Dale et al:
> >
> >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?