Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Disconnects rampant
We found the same thing. Ever since the beginning of this year when we found
that setting LQM on completely stopped the "Motorola Lifestyle going to
sleep" problem, we have been rampant proponents of using LQM with Maxes and
TNTs. The first thing we did after loading ap33 was turn LQM off and test
with a Motorola Lifestyle. This was because several fixes listed implied the
problem had been fixed. Ha! Well I guess we could have pretended to have
been surprised when the problem showed but we were stunned when we turned
LQM on and the problem was still there - worse than ever! I've never seen a
box wiped and the old configuration loaded so fast.
We also had an interesting comment from one of the major K56 importers. I
overheard a conversation where he was discussing the difference in
performance between us and one of our competitors who also runs all Ascend
but not LQM. The comment was that we were faster because they couldn't stop
the modem going to sleep with the competitor. This fits in with what we had
discovered - all modems seem to have this problem of going to sleep, it was
just that the AT&T chipset was the worst culprit.
When is this problem going to get fixed? I am sick to death of capturing the
debug and documenting the problem every time Ascend says the problem has
been fixed and we find YET AGAIN that it hasn't. I quite happly accept that
the chipset used in the Lifestyles (AT&T) is a non-V.34 compliant piece of
crap, because there are several other modem brands with the chipset that
have the same problem. However none of the other access box manufacturers
seem to have this problem so why can't Ascend get their proverbial together
and fix it?
-----Original Message-----
From: Darkshot <darkshot@chudys.com>
To: ascend-users@bungi.com <ascend-users@bungi.com>
Date: Saturday, 29 November 1997 04:33
Subject: (ASCEND) Disconnects rampant
>We're still getting a lot of disconnects on our users, at 5.0Ap33. I
>can't really blame the users as it's now happening to all of us; I used
>to leave mine nailed-up for days at the time and now it's impossible
>UNLESS I leave some sort of activity going bi-directionally. A straight
>FTP download, say, won't work- it has to be a (sleep 10;date) kind of
>thing running in a telnet session.
>
>I haven't had an idle timout enabled on my maxen in months, and checking
>the TSidle stuff shows that it's still disabled.
>
>I remember some posts months back about this, but I paid no particular
>attention to them, as I was no experiencing the problem at the time.
>
>Did Ap33 change something, or wake something up that didn't used to
>matter? What can I check for?
>
>Or more likely, what idiotic mistake am I making NOW? ;-)
>
>'Shot
>++ Ascend Users Mailing List ++
>To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
smime.p7s