RE: [Emerald] Malformed Data in Calls Table

Beachlink Administrator ( (no email) )
Thu, 29 Jun 2000 10:06:12 -0400

You may also want to enable SNMP checking. That has solved everything for
me. Even if the CALLS table shows the customer is still online, SNMP
checking will actually query the NAS to see if that user is online. It is
very slick, and has relieved the headaches involved in the "over login
limit" scenario you describe.

See http://www.iea-software.com/radiusnt/faqs/SNMP-Concurrency.html for
instructions.

--Gary Walworth
admin@beachlink.com

> "Robert H. Clugston" wrote:
>
> > List,
> > I'm reviewing my calls table to see if I can find out
> why some of my users
> > are getting "over login limit" errors. I ran this query:
> > SELECT
> > DISTINCT Calls.UserName,
> > Calls.AcctSessionTime,
> > Calls.NASIdentifier,
> > Calls.NASPort,
> > Calls.CallDate,
> > Calls.CallerID
> > FROM
> > Emerald.dbo.Calls Calls
> > WHERE
> > Calls.UserName = 'user'
> > ORDER BY
> > Calls.CallDate ASC
> >
> > When I was searching throught the results I noticed
> that there was alot of
> > data that looked corrupt. Any idea if this is a problem or is this is
> > normal?
> >
> > For more information about this list (including removal) go to:
> > http://www.iea-software.com/support/maillists/liststart
>
> If your NAS crashes (no BBU) or for any other reason does not
> send the Stop packet.
> Emerald will believe they are still online and they must be
> cleared from the Online
> screen manually.
>
> I was also getting duplicate packets (Session IDs) that it was
> not receiving properly
> for obvious reasons.
> I cleared old data, older than 2 months (or the affected period)
> and the accounting
> began working properly again.

For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart