RE: [Emerald] 3com/Hiperarc

Ken Sorenson ( (no email) )
Mon, 15 Nov 1999 17:07:59 -0600

Thank you for the info, however, I am not sure I understand how the
duplication creates the situation of missing a stop transaction. In radius,
we are not seeing the users leave, so when they call in again, Radius will
not allow them on. Are we on the same page?

Ken

-----Original Message-----
From: emerald-request@iea-software.com
[mailto:emerald-request@iea-software.com] On Behalf Of Dale E. Reed Jr.
Sent: Monday, November 15, 1999 4:19 PM
To: emerald@iea-software.com
Subject: Re: [Emerald] 3com/Hiperarc

Ken Sorenson wrote:
>
> We have a problem with the radius stop information, as I have seen others
> lament here. Everything was working well for us, the only thing we did was
> update our DSP's to 2.06. and reloaded our 'arc information- now it's a
> problem.
>
> Anyone want to share their configs?

The one thing that i consistently seem with the USR gear, is that they
re-use the Acct-Session-ID values rather quickly. TO work around this
you can add the username to the Primary key of the calls table and it
will pretty much solve duplicate accounting records.

--

Dale E. Reed Jr.      Emerald and RadiusNT__________________________________________IEA Software, Inc.    www.iea-software.com

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



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