Re: [Emerald] Calls not being cleared

Josh Hillman ( (no email) )
Wed, 29 Sep 1999 10:44:41 -0400

From: Malcolm Joosse <>
> We are having a problem with one of our NASes rebooting.

What kind of NAS is it?

> After the reboot Emerald shows the users as still being logged in, but
> are not as they get disconnected after the reboot.
> I think this is because the NAS does not give an accounting record for the
> disconnection.
> What I would like to know is, if I stop/start RadiusNT they still show as
> being connected. The only way I have been able to remove them is using
> clear connection button in Emerald.
> Is there a better way ?

I had the same thing happen on Sunday to TWO of our Maxes (reasons, still
unknown) and we had 247 failed login attempts ("Over Login Limit") before I
realized that they reset. We've been using the SNMP concurrency checking,
but it appears that there's either something wrong with it or it wasn't
working at all in the first place--I still haven't determined it. It was
running fine when I tested it a couple of weeks ago.

Anyway, here's the script that I use in ISQL/w so I don't have to open up
Emerald and hit Clear for every individual user. The way it's written
below, is that it clears the users on all of our Maxes. In the case with
Sunday, I kept only "Max 2" and "Max 3" in the list, since those were the
two that had reset themselves.
To get the names of your NASes, just run "select * from servers" in ISQL.

SET sp.AcctStatusType = 0
FROM ServerPorts sp, Servers s
WHERE sp.ServerID = s.ServerID
AND sp.AcctStatusType = 1
AND (s.Server = 'Max 1'
OR s.Server = 'Max 2'
OR s.Server = 'Max 3'
OR s.Server = 'Max 4'
OR s.Server = 'Max 5')


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