[c-nsp] Inverse multiplexing DS3s to larger interfaces?
Matthew Crocker
matthew at crocker.com
Wed Feb 23 15:26:55 EST 2005
This most likely will not work. A POS-OC12 card is an OC-12c and
cannot be 'channelized', it cannot be chopped up into 12 STS1s. A
CHOC-12-DS3 card is an OC-12 card which is channelized and can be
chopped up into STS1s (DS3 + SONET wrapper). With a CHOC-12 you will
still see each individual DS-3 in the router with individual interfaces
and the same 8 interface limit applies. If you have DS-3 hand off from
your carrier then you the carrier must have some type of fiber mux
nearby. DS-3 can only run 400 feet on coax. I would force your
carrier to support/provide OC-n service of the correct size for your
needs. GigE would probably be better if you can swing it.
-Matt
On Feb 23, 2005, at 2:43 PM, Peyton Koran wrote:
> You could use a DS3 to OC12 Multiplexer from someone like Kentrox.
> Then
> bond the different circuits from each vendor, and create sub
> interfaces.
> This would not completely remove your problem, but it would give you
> less of
> one.
> -----------------------------------------------------------------------
> -----
> -----------------------------------------------------------------------
> -----
> Peyton Koran
> Uplogix, Inc.
> 512-857-7026
> pkoran at uplogix.com
>
>
>> From: "Anthony D Cennami" <acennami at neupath.com>
>> Date: Wed, 23 Feb 2005 13:32:38 -0500 (EST)
>> To: "Thomas D.Simes" <simestd at netexpress.com>
>> Cc: cisco-nsp at puck.nether.net
>> Subject: Re: [c-nsp] Inverse multiplexing DS3s to larger interfaces?
>>
>> Your carrier(s) will need to support the layer 2 imux solution on
>> their
>> end as well, not the same thing as l3 load balancing or virtual
>> channels.
>>
>> an ons will obviously support this, but your carrier would have to
>> perform
>> the same thing on their end; whatever the equipment you use.
>>
>>
>>>
>>> We've currently got a pair of GSRs tied together with 7 DS3s from two
>>> different carriers and are load balancing via OSPF. This
>>> method has worked pretty well, but the technique tops out at
>>> maximum-paths 8 on the GSR.
>>>
>>> I'm looking for a more scalable way to multiplex these DS3s into
>>> something larger and feed them into my GSRs to reduce the number of
>>> layer 3 paths between the two locations.
>>>
>>> Going to larger interfaces is currently not an option with one of the
>>> carriers, and we want to maintain dual carriers for redundancy if
>>> possible. We're currently using the 6 Port Packet over DS3 cards and
>>> the interfaces don't support multilink PPP or multilink frame-relay.
>>>
>>> What have folks used that worked well for this application?
>>>
>>> The Cisco ONS 15454 using enhanced DS3 cards looks like it
>>> might be a possibility, but I don't have any experience with the
>>> platform.
>>>
>>> TIA!
>>>
>>> --
>>> Tom
>>>
>>> =====================================================================
>>> =
>>> "Z-80 system stack overflow. Shut 'er down Scotty, the system's
>>> sucking mud" - Error message on TRS 80 Model-16B
>>>
>>> Thomas D. Simes
>>> simestd at netexpress.com
>>> =====================================================================
>>> =
>>> _______________________________________________
>>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>>
>> _______________________________________________
>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
More information about the cisco-nsp
mailing list