Re: Ascend/Livingston interoperability (was Re: (PM) Explanation of alphabet soup? (fwd))

Tim Flavin (tim@i1.net)
Fri, 6 Feb 1998 23:40:49 -0600 (CST)

On Fri, 6 Feb 1998, Stefan Hudson wrote:

> On Fri, Feb 06, 1998 at 06:38:13PM -0800, MegaZone wrote:
> > Once upon a time Chris Trown shaped the electrons to say...
> > >MPPP=MP=Multilink PPP. A means of aggregating two B channels into 1 data pipe
> >
> > MP is Multilnk PPP is RFC1990. MPPP is *usually* MP, but it is bogus, don't
> > use it, use MP.
>
> Bad idea. There are some significant problems with using MP on a Pipeline box when
> connecting to Livingston. I've had problems like connection lockups, connection
> drops after exactly 1 minute, and not reconnecting properly after a disconnect.
> Setting the Ascend to MPP solves all problems. Ascend basically said to use MPP
> if it works. Yes, I know MPP should be the same as MP when connecting to something
> that doesn't support the proprietary extentions, like Livingston.
>

Haven't run into this problem with ComOS 3.7.2c3 or before personally, but
I only have 7 PRI's full of dedicated connections. I have seen this
happen with STAC-9 enabled.

> There are also some issues with the compression on Ascend-Livingston connections.
> Connections will freeze when the Ascend is set to STAC-9 and certain types of
> data are passed - our office staff found a specific web page that will hang the
> P50 in our office every time if compression is on. It seems to be worse on
> underpowered boxes like the P25. Of course, there are none of these problems
> between two Ascend boxes - or two Livingston boxes, presumably.
>

This one is most agrivating. Althou Jake said he has a P25 and a P50
client running STAC-9, so where is that config Jake? I seem to be able to
get between 10 minutes and 5 days uptime out of a Pipe with STAC-9
enabled, and yes, VJ is off. Connection is still up, but useless, passing
no data at all, either end can reset the connection and all is well again,
but for clients with servers, this is not acceptable, and as RFC compliant
as Livingston is, I'm sure it's a Assend problem. It's to the point that
we will tell clients that if you have an OR-U, we will help you all you
want, if you have a Pipeline, your support number is 1-800-4ASCEND. And
we will refuse business from new clients that insist on Ascend for their
end. After going out to their location with a P50 and a OR-U and dropping
them both on the ground, they choose the OR-U every time :P Plus I deduct
$25 commision from my sales people that sell Pipelines to clients, and add
$25 for selling OR-U's.

> I havn't had the time to sit down and report the problems properly. Resolving
> interoperability issues is usually a serious pain in the ass; it usually ends
> up turning into a finger pointing exercise between the two companies, with me
> stuck in the middle trying to coordinate things. Extremely time consuming.
>

I usually just experiance the Ascend finger pointing, then 3 releases
later it's in the bug fix of the week.

==============================================================
Tim Flavin Internet Access for St Louis & Chicago
Internet 1st, Inc Toll Free Sales & Support 800-875-3173
http://www.i1.net For more information email info@i1.net
==============================================================

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.