Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LQM In 6.1.7 (ASCEND)
>Was the LQM problem corrected in 6.1.7? I'm wondering if I should leave it
>switched on when I upgrade or would be better served turning it off . . .
I don't know. I don't run any dial-up into our 4000 anymore; we moved all
that to a TNT. I assume that TNT 2.1.9 is pretty much Max 6.1.7, and I
haven't upgraded from 2.1.3 yet.
The LQM problem Ascend knew of, TR2288, was fixed in 2.1.0 according to the
release notes. I tried LQM with 2.1.0 at the time, and found that it was
still broken. I reported that to Ascend, referring to the ticket I still
have open on the issue.
When I saw that neither the 2.1.3 or 2.1.9 release notes made mention of
any LQM fix, I got worried and started persuing it again. I am once again
actively working with Ascend on the issue. They are currently attempting to
reproduce the problem with the specific devices that we experienced the
problem with, which was Pipeline 15s and 25s, and Netopia ISDN routers.
The specific problem we had was that these devices would be immediately
disconnected, and then again try to reconnect only to be disconnected
continuously. You could occasionally get a packet through...
It appears that there is currently no TR open on the issue, which was a
shock to me. I had thought that there was a TR on it, and was expecting a
fix in 2.1.9. Doh.
If any of you have open tickets, or do know of a TR, please let me know so
that I can refer to your issues in my ticket.
We're about to try LQM again under 2.1.3. I'll let y'all know.
Peter Lalor Infoasis
plalor@infoasis.com http://www.infoasis.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>
References: