Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) Ticket #802135 - Disconnect Problems on 4048 with7.0.1



I am wondering if there is anyone out there using ASCEND equipment that is
not having this problem!!!!  I have used Ascend equipment for almost 3
years and the initial equipment worked very well (under 4.X.X software),
but since, there have been nothing but problems (for over a year and a
half) and this is what I have been seeing on this list from everyone!!  Is
Ascend 1) just not listening, 2) just doesn't care, 3) does not have the
technical capability to fix the problem, 4) too busy with other things to
worry about it, or 5) ALL OF THE ABOVE!  I find it hard to believe that a
company with the reputation that Ascend used to have would allow these
problems to persist for over a year and a half!  What would happen if we
all bought boxes from someone else....appears that Ascend feels they can
do whatever they want and we will continue to buy, use their products!!


Jim Williams                  Ntrnet Systems, Inc.
President/CEO                 Research Triangle Park, NC
jaw12@ntrnet.net              (919)484-0504 fax(919)484-0782


On Wed, 6 Jan 1999, Mark E. Dunlap wrote:

> I can not answer what the problem is but I have some ideas.
> I have seen problems with 33.6K modems or 56K modems that can not
> get a good 56K connection for what ever reason.  I believe this
> is a problem with Ascend's V.90/K56Flex support.  These same users
> are able to dial into my Ascend 4000 with V.34 modems with out
> any problems.  As soon as they attempt to dial one of the 56K
> servers running even just 6.1.0 or 7.0.0, they will train for
> ever and then hang up... Or they will connect but nothing will
> work.
> 
> Just my 2 cents.  They may or may not mean a thing.
> Mark E. Dunlap
> 
> "Steven T. Pierce" wrote:
> > 
> > I have had several users complaining of disconnects as of recent.
> > 
> > We are running Ascend Max 4048 with software 7.0.1 (no OSPF or RIP)
> > 
> > We have 2 locations with 144 ports (3 boxes) fed by Channelized T1s
> > 
> > We also have 2 locations with 46 / 92 ports fed by PRI.
> > 
> > Problems affect both locations and they are in different bell
> > territories (Ameritech PRI and Bellsouth CT1 and PRI)
> > 
> > How can I absolutely, positively guarantee that every setting in the Max
> > 
> > does not cause idle disconnects ( under ether ... answer...  mod
> > config... etc...)  I need explicit directions as I have double and
> > triple checked that I have Idle off or set to 0 (zero) every where I can
> > 
> > find it.
> > 
> > The disconnects codes being reported are :
> > 
> > 11   -  DCD detected, but went inactive    (what does this mean ?????)
> > 
> > 45  -   PPP LCP got terminate request from far end   (what does this
> > mean ?????)
> > 
> > 100 -   Session timeout  (what does this mean, does it indicate that the
> > 
> > Max is discontenting the user, or could it mean other things ?)
> > 
> > 185  -  Remote End hung up - signal lost form far end  (what does this
> > mean ????  what would be an example that could cause this ?)
> > 
> > I need specifics and examples to provide to my customers with the
> > complaints as it is starting to cause me to lose business...
> > 
> > Anyone on the list have any ideas ? suggestions ? help ?
> > 
> > Steven T. Pierce
> > stp@dynasty.net
> > Dynasty Online, Inc.
> > 
> > ++ Ascend Users Mailing List ++
> > To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> > To get FAQ'd:   <http://www.nealis.net/ascend/faq>
> 
> 
> "Steven T. Pierce" wrote:
> > 
> > I have had several users complaining of disconnects as of recent.
> > 
> > We are running Ascend Max 4048 with software 7.0.1 (no OSPF or RIP)
> > 
> > We have 2 locations with 144 ports (3 boxes) fed by Channelized T1s
> > 
> > We also have 2 locations with 46 / 92 ports fed by PRI.
> > 
> > Problems affect both locations and they are in different bell
> > territories (Ameritech PRI and Bellsouth CT1 and PRI)
> > 
> > How can I absolutely, positively guarantee that every setting in the Max
> > 
> > does not cause idle disconnects ( under ether ... answer...  mod
> > config... etc...)  I need explicit directions as I have double and
> > triple checked that I have Idle off or set to 0 (zero) every where I can
> > 
> > find it.
> > 
> > The disconnects codes being reported are :
> > 
> > 11   -  DCD detected, but went inactive    (what does this mean ?????)
> > 
> > 45  -   PPP LCP got terminate request from far end   (what does this
> > mean ?????)
> > 
> > 100 -   Session timeout  (what does this mean, does it indicate that the
> > 
> > Max is discontenting the user, or could it mean other things ?)
> > 
> > 185  -  Remote End hung up - signal lost form far end  (what does this
> > mean ????  what would be an example that could cause this ?)
> > 
> > I need specifics and examples to provide to my customers with the
> > complaints as it is starting to cause me to lose business...
> > 
> > Anyone on the list have any ideas ? suggestions ? help ?
> > 
> > Steven T. Pierce
> > stp@dynasty.net
> > Dynasty Online, Inc.
> > 
> > ++ 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>