Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) 32HDLC card
>From: Bruce Robertson <bruce@greatbasin.net>
>Date: Wed, 17 Sep 1997 00:07:00 -0700
>Subject: Re: (ASCEND) 32HDLC card
>
>>>>>> "Kevin" == Kevin Smith <kevin@ascend.com> writes:
> Kevin> Since the MAX40xx can have up to 4*30 (Europe) channels =
> Kevin> 120, and the base unit has 64 channels "built in", you
> Kevin> might need to add more 32HDLC cards to support more than 64
> Kevin> simultaneous HDLC sessions (1 frame-relay port T1/E1 can
> Kevin> use up 24/30 in one go)....
>
>Be careful doing this, though... we have a Max 4004 with an HDLC card,
>and once we approach 64 connections, we start getting messages like
>this, in diagnostic mode:
What level of microcode are you running, Ascend has a MAJOR HDLC design
problem that was introduce in 5.0ap16! That makes ISDN connectivity
under some-loads not possible!
Five weeks ago I documented and reported Ascend PR 126490 which has a
internal TR of 2554 and today I was told it will be another two weeks
before a solid fix will be release as part of a incremental release!
We have made the mistake here of using the same hunt group numbers to
support both ISDN and analog callers and are paying for it dialy! :((
The Max4004 and Max4048 can not support both ISDN and analog callers under
a ISDN load currently. The results we see is:
In the sysdlog we were getting c=2 p=10
and with tracing on we see!
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 95
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 120
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 121
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 126
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 128
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 129
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 130
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 131
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 132
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 133
WAN: WARNING -- CANT OPEN HDLC CHANNEL, route 135
and we also see
WAN-70: no tx buffer (ordinary prio)
We have seen this on all of our Ascend Max40xx boxes here! Some with only
one PRI and others with four PRI's. Since we mix ISDN and analog customers
here we need the newer modem code but are getting beaten by the ISDN bugs.
Regards,
Tom Wye
twye@bayarea.net
A very unhappy Ascend customer!
>
> Call stack: B01CB454 B0093F08 B00948E0 B0233348 B0181BC0 B0181B88
> WAN-419: no tx buffer (ordinary prio)
> Call stack: B01CB454 B0093F08 B00948E0 B0233348 B0181BC0 B0181B88
> WAN-419: no tx buffer (ordinary prio)
> Call stack: B01CB454 B0093F08 B00948E0 B0233348 B0181BC0 B0140998
> WAN-419: no tx buffer (ordinary prio)
>
>and performance goes down the tubes. Lost packets, mostly. I don't
>see how the thing has a chance of supporting 96 channels. Tech
>support has been no help, and we're about to ship the HDLC card back COD.
>
>
********************************************************************************
* Thomas J. Wye Tel: (408) 260-5000
* Bay Area Internet Solutions Fax: (408) 260-5003
* 900 Lafayette Street, Suite 710 E-mail: twye@BAYAREA.NET
* Santa Clara, CA 95050 HTTP: http://WWW.BAYAREA.NET
* Info Robot: INFO@BAYAREA.NET
* 33.6Kbps dial-up, 56Kbps-T1 (Leased*Frame Relay), server colocation,
* Virtual Domain hosting and World Wide Web development.
********************************************************************************
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>