[c-nsp] Bridging T1s together on PA-MC-T3

[Jared Mauch]

	What you are describing sounds like you want to place the two
interfaces either

	1) in a VRF so they can only talk to each other
	2) in a locally terminated *oMPLS/xconnect situation.

	You are likely to do best with the VRF as it's more likely to be
supported in what you are doing, but requires you to play a 'higher level'
role in the network.  The final choice would be to just get the carrier
to x-connect the two circuits together, or use a series of external M13's
to do it yourself.

	- Jared

On Tue, Sep 13, 2011 at 09:10:27AM -0600, Nick Voth wrote:
> Folks,
> 
> I'm hoping this is easy/obvious question, but I've looked around and can't
> find the config I'm looking for.
> 
> I have several channelized DS3s coming in and terminating on PA-MC-T3 cards.
> I use those for regular "ppp" T1 circuits out to client sites.
> 
> I now have the need to "bridge" 2 client sites together, and am wondering if
> there's a way to bridge 2 individual T1 circuits together on one DS3 card.
> 
> The 2 client sites don't need access to our LAN or Internet. This would
> literally be a private line connection between the 2 sites, with us in the
> middle bridging them together.
> 
> The client's Internet access is totally separate from this proposed
> solution.
> 
> I know I can have the local telco just do a point-to-point circuit between
> the 2 client sites, but then we wouldn't have any visibility for up/down
> monitoring, etc.
> 
> Any advice would really help.
> 
> Thanks,
> 
> -Nick Voth
> 
> 
> 
> _______________________________________________
> 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/

-- 
Jared Mauch  | pgp key available via finger from jared at puck.nether.net
clue++;      | http://puck.nether.net/~jared/  My statements are only mine.