Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: (ASCEND) ppp/mp/mpp connection coronaries continued
Mine started much earlier than V.90. Turning LQM on seems to have reduced
it a lot, but not eliminated it entirely . . .
> -----Original Message-----
> From: Alex P [SMTP:alex@stomp.gomax.com]
> Sent: Monday, July 13, 1998 3:34 PM
> To: Tom Pepper
> Cc: Oliver J. Albrecht; ascend-users@bungi.com
> Subject: Re: (ASCEND) ppp/mp/mpp connection coronaries continued
>
> Same trouble here with modem connections. Started with the introduction
> of the V.90 code.
>
> Alex P
>
> On Sat, 11 Jul 1998, Tom Pepper wrote:
>
> > > >By `stopping' I mean that no packets flow between the two; the phone
> > > >lines are still connected, `show modems' says the interface is up,
> but I
> > > >cannot ping the max from home, and I cannot ping home from the max
> (once
> > > >I use another phone line to dial in through another system and telnet
> to
> > > >the max). (telnet, etc. don't work either, of course.)
> > >
> > > We're experiencing the same problem with a Max4000 and 6.1.0/6.1.3. In
> our
> > > setup it is *not* related to modem callers, ISDN users are getting it
> as
> > > well. Enabling/disabling LQM doesn't change it, only with LQM the
> ISDN/modem
> > > connection will eventually get terminated. We've got an open ticket
> with
> > > Ascend about this, but unfortunately the error doesn't show on a
> regular
> > > basis (sometimes after 5 minutes, at other times after 1-2 hours).
> I'm
> > > actually surprised that other people on this list aren't seeing this.
> >
> > We're experiencing the same problem on any Max or Pipeline running
> 6.x.x, or TNT
> > running 2.x, happening under the following conditions:
> >
> > Modem: TNT or Max 40xx is running 6.x.x, LQM on or off when MP is
> attempted /
> > used.
> >
> > ISDN: Since TNT still doesn't do ISDN callback, we don't use it. Max
> 40xx, any
> > version when a 6.x.x pipeline connects to it. We're using 5.0Ap44 on
> the 40xx's
> > for now until Ascend gets to work on the problem. It currently behaves
> with
> > Pipelines running 5.x. Problem exists regardless of LQM setting.
> >
> > DSL:
> > SDSL on TNT, SDSL P-T-P, no problems across the board. RADSL
> likewise.
> > IDSL works fine on Max 4002s w/ 5.x. Haven't tested with 6.x.
> > IDSL experiences the SAME problem w/ TNT 2.x, and ANY version of
> Pipeline
> > software, regardless of LQM.
> >
> > I've been unable to get TAC to realize that there's even a problem,
> since it
> > takes an hour or two to stop packet flow. As a result, I'm now working
> directly
> > with the DSL product manager for resolution on the issue (interop is a
> wonderful
> > thing.)
> >
> > I also have a hard time believing that no one else is experiencing
> problems
> > similar to these. Thought I'd make my voice heard.
> >
> > Regards,
> > -Tom
> >
> > ++ 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>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups: