Re: (ASCEND) MAX 4K/6K CODE

[Dana Hudes <dhudes@hq.smartworld.net>]

Regarding PPP LQM, it should be configurable someplace on the MAX what
is the acceptable quality. You could set it for something generous like
70%. Think about that -- 3 out of 10 packets don't get through.
I have not tried this on the Ascend gear but on cisco and Bay gear I do
it, with the LQM set to tear down the line at 85 or 90%. If things get
that bad on a T1, I want ops to call the carrier.

Another option I suppose is just to monitor LQM but set it to something
ludicrous like 20% so even if 8 out of 10 packets don't make it you'll
keep the line up.



On Tue, 2 May 2000 maxed_out_user@hotmail.com wrote:

> >From my experience, it's always been these three factors causing most
> disconnects issues I've encountered:
> 
> 1. Incompatible modem code (on the client side or the server side).
> 2. Line errors
> 3. LQM
> 
> 1. Incompatible modem code
> 
> Looks like your Max 4000 is not up to par with the Max 6000 (and could
> be the problem here).  Version 7.0.22 has newer V.90 code than version
> 6.1.7 and has been pretty good for me.  There is a 7.0.22 for Max 4000s
> so it might be best to upgrade.  Then as long as the client modem is
> using the latest V.90 drivers, it's usually not a modem incompatibility
> issue.
> 
> 2. Line errors
> 
> Conveniently, I happened to have written this step on another e-mail to
> someone else in this thread, so I'll just repeat it here:
> 
> "You can check your own T1 lines for errors on the Max.  You have to TAB
> 
> over to one of the 8 status windows on the right (let's say you choose
> the one on the bottom right).  Then ESC until you're at the Main Status
> Menu.  Then arrow down to one of the 2 Net/T1 slots (depending on if the
> 
> T1 is plugged into Wan 1 or 2, go into the first Net/T1, if Wan 3 or 4,
> then go into the second Net/T1).  Once in there, go into either FDL 1 or
> 
> FDL 2 stats (again, depends on which WAN port you have your lines
> plugged into).  Note the FDL stats for the current period and the last
> 24 hours (the left column).  If you left arrow out and go back into the
> current period, see if the ES (errored seconds) stats goes up.  If so,
> then you are currently receiving framing errors from telco.  If the last
> 
> 24 hours shows a lot of errors, then you can count on this being a phone
> 
> company problem."
> 
> 3. LQM
> 
> Line Quality Monitoring (LQM) is a PPP implementation where the line is
> monitored for good or bad line quality.  I think the spec is not clear
> on how to consider a line good or bad and so might be the reason why
> Ascend's don't do it well.  I would make sure this is turned off because
> leaving it on causes a lot of disconnects:
> 
> Ethernet->Answer->PPP Options->LQM=No
> 
> 
> 
> We are using max 4k's and 6k's software version 6.1.7(4k) and 7.0.22(6k)
> 
> We are using all CH T1's, no PRI
> 
> Most of our users are working fine, but some are having ongoing
> disconnect problems.
> 
> I totally understand the CHEAP modems out there and the problems with
> them.  But, what concerns me now is that I have a good modem in my
> machine at the house and am seeing some disconnect issues recently.
> 
> What is a GOOD code for these machines that is stable that will solve
> the disconnect issues.
> 
> Other than the disconnects we do not have trouble with these machines,
> but we are not trying anything fancy either.
> 
> Thanks,
> John
> 
> ++ 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>