Re: [Emerald] Work on SNMP Concurrency Checking

TIA ( (no email) )
Tue, 18 Apr 2000 19:18:38 -0500

The user login limit is set to 1. and the string after the User: was the
correct auth name. I now have no Concurrency Control, although I have it set
that way and have variable login limits set. It worked (Concurrency wise
minus the "hung" user) with the SNMP Concurrency Check not working because
the mib.txt was not in the Data Directory. Now the SNMP just sees the user
online, verifies that the user is online at the port the are listed on, then
lets the user on again. Any more help would greatly be appreciated.

----- Original Message -----
From: "Dale E. Reed Jr." <>
To: <>
Sent: Tuesday, April 18, 2000 5:46 PM
Subject: Re: [Emerald] Work on SNMP Concurrency Checking

> Randy Martin wrote:
> >
> > I don't mean to jump into the middle of this, but isn't the above the
> > NON-SNMP concurrency doing it's job correctly? It did the radcheckonline
> > and found the user already online. It doesn't seem to me that you should
> > need both? I don't have the SNMP concurrency setup, and everything works
> > just fine on our system. Is there only certain combinations of NAS's
> > that have a problem with the non-SNMP concurrency checking?
> >
> > >Apr 18 15:06:03 2000 [INFO]: SQL Statement: {CALL
> > >RadCheckOnlineSNMP('ejluckey')}
> > >Apr 18 15:06:03 2000 [INFO]: Server:tcm-glenelder
> > >SNMPUser:. User:ejluckey
> > >Sending Ack of id 111 to d12a4f23 (tcm-glenelder)
> Assuming that the customer's login limit is 1, the SNMP verified
> that the customer is indeed on-line and should not be allowed on
> again. If the string after the User: does not match the auth name,
> then the SNMP checking would ignore the on-line entry, to prevent
> false denial.
> --
> Dale E. Reed Jr. Emerald and RadiusNT
> __________________________________________
> IEA Software, Inc.
> For more information about this list (including removal) go to:

For more information about this list (including removal) go to: