Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) RE: Uh Oh . . .
Hmmm. Okay, the local Ascend hack was actually on site a few months back
and confirmed that no, nothing was _obviously_ wrong with the config
(Columbus, OH - Morningstar is right down the road). I understand how
analog connections can be rocky at times, but this seems reproducible enough
to mitigate that.
I am interested, though, in your comments about the site CO being a problem.
It would not be the first time, but how could they possibly dork up a PRI T1
such that analog connections work great for 15 to 90 minutes, then lose
connectivity (line stays up), and then maybe even recover?
If what you're driving at is, "Well maybe in that particular case it was the
user's modem, and then in another it was a noisy phone line, and in a third
it was the user's CO, and in the fourth it was the user's mediocre TCP/IP
stack" then I guess I can let it go, but that's not what's going on here. I
don't like it any better than the next guy, but the common element in all
these "one off" bad calls is the Max at my end.
Any thoughts from anyone, please feel free to share. I'll shut up now.
M
> -----Original Message-----
> From: Matt Holdrege [SMTP:matt@ascend.com]
> Sent: Tuesday, August 11, 1998 9:49 AM
> To: Lynch, Mark
> Cc: ascend-users@max.bungi.com
> Subject: RE: Uh Oh . . .
>
> You're not a moron. :)
>
> It's just that there are a heck of a lot of variables. First of all, it
> could be a telco issue at your site, your CO, the users site or his CO. It
> could be a brand of modem. Yes you can use modemdiags in debug to
> troubleshoot further. Or you could call our support line to have someone
> step through your config to look for any issues.
>
>
> At 08:12 AM 8/11/98 -0400, Lynch, Mark wrote:
> >!
> >
> >Really? I thought it was pretty clear, moreso the first time around than
> >the message below, but reasonably straightforward none the less. I also
> got
> >the impression that a lot of other folks were seeing very similar
> symptoms?
> >
> >I'm certainly open to suggestions though. Let's say I get the benefit of
> >the doubt and I'm not a moron. Of the dozens of possible causes, which
> >might be the most obvious for me to consider? Or, better still, perhaps
> >there are debug monitor commands I could use on the Max to observe
> details
> >of the connection failure? Believe me, I'd love to blame it on the
> user's
> >modem configuration at this point . . .
> >
> >M
> >
> >> -----Original Message-----
> >> From: Matt Holdrege [SMTP:matt@ascend.com]
> >> Sent: Monday, August 10, 1998 4:30 PM
> >> To: Lynch, Mark
> >> Cc: ascend-users@max.bungi.com
> >> Subject: Re: Uh Oh . . .
> >>
> >> Sorry, I can't answer vague questions very well. Dozens of things could
> be
> >> causing your problem. It's needs a lot more debugging.
> >>
> >> At 01:15 PM 8/10/98 -0400, Lynch, Mark wrote:
> >> >
> >> >Matt,
> >> >
> >> >Silence is the scary part and I haven't heard your opinion on this
> yet.
> >> >Should I be worried?
> >> >
> >> >-----------------------------------------------------
> >> >Mark:
> >> >
> >> >This problem exists all over the board, even up to IDSL switched MP
> >> >connections via Max TNT and Pipelines.
> >> >
> >> >I've heard nothing concerning a fix.
> >> >
> >> >-Tom
> >> >
> >> >>For the Ascend boys (Matt, et al) specifically:
> >> >>
> >> >>Gentlemen,
> >> >>
> >> >>On my very simple, whitebread Max 4K I've got a recurring insidious
> >> problem
> >> >>with analog PPP connections losing their network connectivity. The
> line
> >> >>stays up, but the TCP/IP just "goes away". Sometimes it comes back
> >> after a
> >> >>few minutes, sometimes the user has to start over.
> >> >>
> >> >>Thanks to Peter Lalor for clueing me in about LQM. Turning that on
> (I
> >> >>haven't made the jump to 6.1.x yet) reduced the frequency of the
> >> problem,
> >> >>but did not eliminate it altogether. I've seen other folks here
> remark
> >> on
> >> >>similar symptoms in their configurations. Thanks to all, by the way,
> >> for
> >> >>sharing and offering suggestions.
> >> >>
> >> >>My question for you is this:
> >> >>
> >> >>I understand work is furiously underway on the next release of 6.1.x
> >> that's
> >> >>really going to fix a lot of things. Is my problem one of the things
> >> fixed
> >> >>in this pending (or any) release? Right now I'm at 5.0Ap51, waiting
> for
> >> >the
> >> >>smoke to clear in 6.1.x.
> >> >>
> >> >>I guess another way to put this same question is, "Is Ascend aware of
> >> and
> >> >>working on a solution for this problem"? Believe me, for the longest
> >> time
> >> >I
> >> >>thought it was pilot error, but after having read this list for a
> couple
> >> of
> >> >>months I'm happy (and saddened) to see it's not just me.
> >> >>
> >> >>So what do you fellows think?
> >> >>
> >> >
> >> >
> >
> Matt Holdrege http://www.ascend.com matt@ascend.com
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>