Re: (ASCEND) Max 6000 - LAN security errors during heavy load

["J. Wells" <jwells@sd79.bc.ca>]

At 01:16 PM 4/12/99 -0400, Troy Settle wrote:
>With the d/p codes of 101/67, have you checked to see if that user was
>already logged on at the time?
>
>Seems that people like to share usernames and passwords.  IIRC, the 101
>can be caused when people attempt multiple logins.
 [...]

Thanks for the suggestion. (Ascend also suggested this.) However, I've run
my syslogs through an AWK script to look for this (by tracing the progress
of each call) and it is only rarely the problem.

For example, in last week's log there were 81 calls with the problem (LAN
security error, c=101, p=76) but only two of them were due to attempted
simultaneous logins. In the case of all the other problem calls, checking
the progress of each call shows that the affected user was not logged in at
the time of the problem. E.g., 

<call setup>
4/8/99, 1:55:36 PM, ... LAN session up, <user> [MBID 341; ->...]
<user's on>
4/8/99, 3:13:40 PM, ... LAN session down, <user> [MBID 341; ->...] 
4/8/99, 3:13:41 PM, ... call 23 CL 0K  u=<user> c=45 p=60 s=28800 r=26400  
<call cleanup>

There is no other reference to <user> in the syslog until:

<call setup>
4/8/99, 3:48:26 PM, ... LAN security error, <user> [MBID 368; ->...] 
4/8/99, 3:48:30 PM, ... call 51 CL 0K  u=<user> c=101 p=67 s=28800 r=26400
<call cleanup>

Must be something else, or the MAX must still think <user> is on even after
syslog and RADIUS accounting have shown them off.

>--
>  Troy Settle <st@i-Plus.net>
>  Network Administrator, iPlus Internet Services
>  http://www.i-Plus.net
>
>
>
>On Fri, 9 Apr 1999, J. Wells wrote:
>
>> At 05:09 PM 4/9/99 -0500, John Coy wrote:
>> >I have several MAX 6000 terminal servers on my network.
>> >I've been experiencing some intermittant problems lately
>> >which appear to crop up when the terminal server is heavily
>> >loaded.  I am running the 7.0.4 firmware.
>> >
>> >What appears to happen is when the Max has more than 72 connections,
>> >it will give a LAN security error when a user is logging in.
>> >There is no reason for this (ie: the RADIUS server is running fine,
>> >the user is not already logged in, the user supplied the correct
>> >username and password).
>> >
>> >Rebooting the MAX makes the problem go away.
>> >
>> >The problem is intermittant.
>> >
>> >Has anyone else experienced these same problems?  Info/Feedback
>> >would be greatly appreciated.
>> 
>> We have a related problem with a MAX 2024, running 7.0.3 (but the problem
>> has likely been there with various 6.x.x releases too)
>> 
>> Some users, some times, get immediately disconnected after authenticating.
>> Syslog shows these calls connecting, and following modem negotiation the
>> RADIUS server log shows that authentication was successful. However, the
>> MAX then immediately disconnects the user. Syslog then gets warning saying
>> "LAN security error" for the username. A few seconds later syslog and
>> RADIUS accounting record the end of the call, with the username and a
>> disconnect code of 101 (invalid user) and progress code of 67. (The RADIUS
>> accounting log has only a STOP record and doesn't show the username.)
>> 
>> Our MAX isn't heavily loaded, and I haven't been able to correlate this
>> problem to anything else. Between 5% and 10% of our calls end with this
>> c=101, p=67 combination.
>> 
>> I wish I had an answer, but I don't. We've got a ticket with Ascend on
>> this, and as requested sent them a wanNext trace of one such call, but
>> haven't (yet?) heard back anything helpful.
>> 
>> John Wells
>> School District 79 - Cowichan Valley
>> Duncan, BC, Canada
>> jwells@sd79.bc.ca

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>