Re: [Emerald] Work on SNMP Concurrency Checking

NCKCN ( (no email) )
Wed, 19 Apr 2000 09:54:29 -0500

Heres what I get when an user get "stuck" on. This is from a Cisco 2511. As
soon as I get one from a 3Com Total Control Hub, I will send that also.

================
radrecv: Request from host cefd3816 (rtr1-clifton) code=4, id=98, length=125

NAS-Identifier = 206.253.56.22
NAS-Port = 3
NAS-Port-Type = Async
User-Name = "sawilson"
Acct-Status-Type = Stop
Class =
"\006\000\000\000\001\006\006\000\000\000\002,\01200000E69\007\006\000\000\0
00\001\010\006\321*A\322*\006\000\006\025\201+\006\0006"
Invalid Attribute Length. Attribute: 52 Length:117
Resp Time: 0 Auth: 221/34 -> 255 Acct: 446/0/0 -> 446

radrecv: Request from host cefd3816 (rtr1-clifton) code=4, id=99, length=125

NAS-Identifier = 206.253.56.22
NAS-Port = 3
NAS-Port-Type = Async
User-Name = "sawilson"
Acct-Status-Type = Stop
Class =
"\006\000\000\000\001\006\006\000\000\000\002,\01200000E69\007\006\000\000\0
00\001\010\006\321*A\322*\006\000\006\025\201+\006\0006"
Invalid Attribute Length. Attribute: 52 Length:117
Resp Time: 0 Auth: 221/34 -> 255 Acct: 446/0/0 -> 446

Although the stop is recieved, somehow there's an error with an Attribute
Length. It gets the stop record twice.I'm guessing that the Calls table then
doesn't get updated. Any help?

----- Original Message -----
From: "Duane Schaub" <dschaub@terraworld.net>
To: <emerald@iea-software.com>
Sent: Wednesday, April 19, 2000 8:33 AM
Subject: RE: [Emerald] Work on SNMP Concurrency Checking

> I too see this - it has been suggested that the problem was that radius
did
> not recieve the stop packet. I personally feel that it is more of a
problem
> in that the stop packet is either not being generated or is fundamentally
> different in some way so that a radiusnt or sql error occurs and the calls
> table doesn't get updated. I haven't had the time to really debug this
part
> of the process, but it has rendendered login limits useless for three
years.
>
> SNMP may have been the solution for us in the past, but we are currently
> moving to the SWBell VPOP on a Nortel CVX-1800 and to my knowledge, they
> will not allow snmp traffic from a customer. They have a cool web page,
so
> it may be possible to write something that will parse the web page and
> update the tables.... but again - I really don't have time to mess with
> this.
>
> Duane.
>

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