🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: alt.bbs.internet
Article #1887

Re: Do not use UUNET for ISDN access

#1887
From: Jonah Yokubaitis
Date: Tue, 17 Sep 1996 00:00
60 lines
4288 bytes
Jeffrey D. LaCoursiere (lacoursj@dudemon.fastlane.net) wrote:
: 
: I have some insight here, as we have been benchmarking several models
: of ISDN equipment for the past few weeks.  Of the four units we are looking
: at (Bay Remote Annex 6300, Ascend Max400x and TNT, USR Total Control Hub,
: and Cisco (if it ever gets here) 5210), only the Cisco claims to "bond 
: across boxes".  Ascend claims to know about the problem, but chooses not 
: to ship their boxes with this feature as they claim it impacts performance.
: My fuzzy understanding of how it is accomplished involves all the term 
: servers on a segment broadcasting a proprietary protocol that informs the 
: others when the first B channel of an MPPP connection is accepted.  When 
: the second B channel is accepted, the server that accepted it *should* 
: know which server has the first channel, and proceeds to "forward" the 
: packet pieces to the first term server (over what protocol I am not 
: sure... perhaps just tunneled in IP?) for re-assembly.  I would accept 
: that there may be some latency in this process.  Don't forget traffic in 
: the other direction.  The server with the first channel will get the 
: traffic that is bound for the user, and will have to make some decision 
: to split it up and send pieces to the server with the second channel.

Ascends now support MPP accross multiple boxes.
 
: Ascend sales claims that this process impacts performance by 25% .

I wouldn't doubt it as bonding via ethernet is a _bad_ idea.
 
: 1.  Buy a bigger box.  Two of the vendors mentioned above claim that an OC3
: capable server will be available next year.  Thats somewhere in the 700 B 
: channel range, folks.  Might as well become your own local CO :)  This 
: solution is a good one, if the hardware is actually up to it.  It 
: probably scales *fairly* well, until the time (if it comes) that ISP's 
: will have to handle 25,000 simultaneous calls.  Even then, distributing 
: customers across a few tens of these monsters probably wouldn't be 
: extremely difficult.

Assuming that you are provisioning your PRIs without NFAS with 23B + D to
a T1.

That woudl give us :

23 (T1) * 28 == DS3 (T3) == 644 B channels
OC3 is ~ 3 DS3s == 644*3 == 1932 per OC3.

Now your chances of not achieving an MPP connection are slim :-)
 
: Has anyone come up with any other solutions?

Use Ascend's MPPP across multiple boxes. If you are using 4 PRI Ascends,
the chances of having 1 customer on 2 boxes is very slim.

Jonah

-- 
Jonah Barron Yokubaitis    | San Antonio (210) 272-8111
President                  | Austin	 (512) 472-2532
Texas.Networking Inc.	   | Houston	 (713) 222-2260		
barron@texas.net           | Boerne	 (210) 249-7058
Internet Access for Texas  | Georgetown  (512) 869-5947   
http://www.texas.net       | DrippingSprings   858-5092        
Technical Details
Message-ID: <51mngj$i0h@news2.texas.net>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <323cc940.261245176@news1.alterdial.uu.net> <Pine.BSF.3.91.960917083721.4780D-100000@dudemon.fastlane.net>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f9628,e83bc54c0148b90d
X-Google-Attributes: gidf9628,public
X-Google-Thread: fb39a,e83bc54c0148b90d
X-Google-Attributes: gidfb39a,public
X-Google-Thread: f6a4e,e83bc54c0148b90d
X-Google-Attributes: gidf6a4e,public
X-Google-Thread: fc7b2,e83bc54c0148b90d
X-Google-Attributes: gidfc7b2,public
X-Google-Thread: 10bd82,e83bc54c0148b90d
X-Google-Attributes: gid10bd82,public
X-Google-Thread: f5ebf,e83bc54c0148b90d
X-Google-Attributes: gidf5ebf,public
X-Google-Thread: 100579,e83bc54c0148b90d
X-Google-Attributes: gid100579,public
X-Google-Thread: f4f5d,e83bc54c0148b90d
X-Google-Attributes: gidf4f5d,public
From: barron@texas.net (Jonah Yokubaitis)
Subject: Re: Do not use UUNET for ISDN access
Date: 1996/09/17
Message-ID: <51mngj$i0h@news2.texas.net>
X-Deja-AN: 181218370
references: <323cc940.261245176@news1.alterdial.uu.net> <Pine.BSF.3.91.960917083721.4780D-100000@dudemon.fastlane.net>
followup-to: alt.bbs.internet,alt.internet,alt.internet.access.wanted,alt.internet.services,dfw.internet.providers,houston.internet.providers,me.internet,ne.internet.services,phl.internet
organization: Texas Networking, Inc.
newsgroups: alt.bbs.internet,alt.internet,alt.internet.access.wanted,alt.internet.services,dfw.internet.providers,houston.internet.providers,me.internet,ne.internet.services,phl.internet