Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) 5.0Ap27 and the HDLC problem

My Max running 5.0Ap23 is 99+% ISDN calls and I have not seen this problem.
Current uptime is 23+ days.

I'm not complaining. :-) Just offering a datapoint.

At 07:49 PM 10/1/97 -0700, Kevin Smith wrote:
>At 11:15 PM 9/30/97 -0400, Jason Nealis wrote:
>>
>> OK, I'm confused, I must have missed Kevin's message, Is there a bug??
>>HDLC? ap27? say what? I've heard if you initiate a HDLC call into a ap27 
>>the box will explode. :) 
>>
>> Actually, I'm concerned, cause I'm about 3 hours away from deploying this
>>into my network. Can anyone confirm if there is an issue on HDLC calls?
>
>This thread started with a question about an HDLC related problem that was
>reported against 5.0Ap16. Since it's still on the open TR list, all patch 
>versions since then have this vulnerability. If you have been running any 
>of 5.0Ap16, 5.0Ap20, 5.0Ap23 or 5.0Ap24 and have not seen this problem, 
>then you are VERY UNLIKELY to see this problem in 5.0Ap27, since nothing has 
>changed with respect to it.
>
>How bad is the problem? 
>It is listed as HIGH priority in Engineering.
>A few customers have decided to remain on 5.0Ap13 because of it, they tend 
>to be >50% ISDN calls. If you are predominantly a modem service provider, 
>you are unlikely to see it at all. So far it has been reported by only a 
>handful (six) of customers (most MAX users have a vast majority of modem 
>customers rather than ISDN or a 50/50 mix).
>
>How does it manifest itself?
>The TR reports that after about 24 hours, the MAX stops accepting ISDN calls.
>There are debug messages that refer to HDLC resources being unavailable.
>Calls are disconnected with c=2, p=2.
>A system reset temporarily resolves the problem. 
>
>What to do if you are seeing it?
>Unless you have already done so, contact Ascend tech support and tell them
>you are experiencing the problem with ISDN calls failing - TR#2554. 
>If it is feasible to do so, you could down-grade the MAX to 5.0Ap13 until
>we announce the fix.
>
>In any extreme cases, ask to talk to the Escalations Director:
>
>>Any customers having this problem should call into support and then we will
>>get them the code [next week] and if it extends we will spread the Pri's out
>>across maxes.
>>
>>Tom
>
>*We have a fix for this in the incremental branch, but have not yet made a
>version that we feel to be stable enough to release. That should change
within
>the next week-or-so, and we will have the fix in the next major release which
>should also appear within the next few weeks.
>
>
>Kevin
>
>
>++ Ascend Users Mailing List ++
>To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd:	<http://www.nealis.net/ascend/faq>
>
>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>
References: