Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) Ticket #802135 - Disconnect Problems on 4048 with 7. 0.1
I finally gave up on ascend. I went totally off the wall and tried a new
product from a new company, Assured Access. 99% of my problems are gone. No
more reboots. For information they are at < http://www.assuredaccess.com >.
This is not a sales pitch but a reality check. I am finally becoming a happy
camper. I know this forum is not a advertising forum but I got lucky met
them at ISP con and the rest is history. Hope this doesn't p*** anyone off.
I am also in no way affiliated with this company. I too needed a great
product to get my customers happy.
Bennie
**************************************
Bennie Warren
LemooreNet
320 West D Street
Lemoore, CA 93245
Phone: 559.924.5909
Fax 559.924.9578
bennie@lemoorenet.com
http://www.lemoorenet.com
**************************************
----------
>From: Jason Nealis <nealis@babylon.erols.com>
>To: "Todd A. Blank" <todd@thenap.com>
>Cc: Jim Williams <jaw12@ntrnet.net>, "Mark E. Dunlap" <mdunlap@ds.net>,
"Steven T. Pierce" <stp@Dynasty.Net>, ascend-users@bungi.com
>Subject: RE: (ASCEND) Ticket #802135 - Disconnect Problems on 4048 with 7. 0.1
>Date: Fri, Jan 8, 1999, 9:59 PM
>
>
>To be honest, I've about had it with Ascend, When it rains it fucking
>pours over here, My problems range but are not limited to :
>
>1)Receiving bad hardware from the start.
>2)Poor code, I have never been able to stabilize on any set of code.
>3)NO regression testing out of Alamdia, NOTHING. Trained Monkeys
>
>
>Let's put it this way, The last two days I have lived an absolute
>nightmare. I don't know if many of you know this, but I've been
>experiencing horrible problems with the New Ethernet II card on
>the TNT's, They are SUPPOSED to be full-duplex, but due to a problem
>with the card they reset the link every 2 minutes when running with
>a load
>
>I suggest people run through there sys-log and look for these types of
>messages :
>
>Jan 9 00:13:33 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:16:08 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:18:34 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:19:53 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:20:10 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:20:30 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:21:18 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:21:23 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:22:17 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>Jan 9 00:24:54 tnt1.lnh.md.rcn.net 1/2: 100BaseT: Link up
>
>So I had to back my entire network down to Half-Duplex so
>I would not excite this issue with the box. And I'm still awaiting a
>fix.
>
>The world needs a wake up call, Perforance, Code, Testing
>from Ascend is on a SERIOUS down-slide.
>
>Ascend has quickly gone back to the company of 2 years ago.
>
>Jason Nealis
>Director Internet Operations / Network Access
>Erols Internet (An RCN Company)
>
>
>
>
>
>
>On Thu, 7 Jan 1999, Todd A. Blank wrote:
>
>> I feel your pain brothers...
>>
>> Jason - you always seem to have the inside scoop - is Ascend going to do
>> anything about this?
>>
>> Todd Blank
>> Columbus NAP, Inc.
>>
>> > -----Original Message-----
>> > From: Jason Nealis [SMTP:nealis@babylon.erols.com]
>> > Sent: Wednesday, January 06, 1999 10:46 PM
>> > To: Jim Williams
>> > Cc: Mark E. Dunlap; Steven T. Pierce; ascend-users@bungi.com
>> > Subject: Re: (ASCEND) Ticket #802135 - Disconnect Problems on
>> > 4048 with 7.0.1
>> >
>> >
>> > Join the crowd, I'm getting a TON of disconnects over here, However I
>> > think there are other contributing factors also making things worse.
>> > But
>> > THERE IS A PROBLEM on my Ascend equipment, My customers/management are
>> > getting ready to toss me the fuck out the window if I don't get
>> > connections stable again over here.
>> >
>> > Jason Nealis
>> > Director Internet Operations / Network Access
>> > Erols Internet (An RCN Company)
>> >
>> >
>> > On Wed, 6 Jan 1999, Jim Williams wrote:
>> >
>> > > 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>
>> > >
>> >
>> > ++ 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>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>