[j-nsp] MPLSoMPLS - horrible?

Herro91 herro91 at gmail.com
Thu Sep 30 07:42:03 EDT 2010


Hi Dale,

I've been working on a similar project for one of my customers. It can be a
little ugly in my opinion as you end up with a lot of extra protocols
running (potentially).

Juniper does have this really neat feature called Dynamic GRE tunnels which
really make enabling MPLS over GRE (over MPLS) easy to configure. It only
allows for L3VPN as LDP is not running as it uses BGP for label exchange. I
got this up and running really fast compared to my testing of a traditional
MPLS over GRE (over MPLS) solution which in my customer's case involved:

GRE, LDP, ISIS, iBGP in addition to their existing OSPF, eBGP configuration

Feel free to let me know your thoughts. BTW - CsC/InterAS is not involved at
all, so no coordination short of understanding your provider's max MTU and
perhaps QoS mappings (you'll need to map ToS/DSCP to GRE potentially) - I
have not tested this so far but Juniper has ways to copy these bits into the
GRE header.

Good luck....
On Thu, Sep 30, 2010 at 3:52 AM, Dale Shaw
<dale.shaw+j-nsp at gmail.com<dale.shaw%2Bj-nsp at gmail.com>
> wrote:

> Hi all,
>
> I'm pondering my first production use of MPLS and I'm looking for some
> free advice.
>
> I'm looking at building a new 'enterprise' network - an extranet of
> sorts - *on top of* a NSP's L3VPN service. It's all Ethernet. I'd like
> to be able to build my own pseudowires and create my own L3VPNs on top
> of the NSP's platform and without their involvement. In effect, my CE
> routers (from the NSP's perspective) become PE routers to *my*
> customers (3rd parties, e.g. business partners and suppliers).
>
> I suppose this means doing MPLSoMPLS, and actually depending on the
> upper layers in the protocol stack, it could end up looking pretty
> scary if you looked at what was being shifted around in the NSP's core
> :-)  (over and above MPLS, I'm thinking about how the stack looks when
> further encapsulation, such as IPSec, is used.)
>
> So, noting the protocol stack size and potential MTU issues, is anyone
> doing this? How are you distributing labels?
>
> Is it too horrible to even contemplate?
>
> I'd be looking at using J and/or SRX as the "CE-pseudo-PE" devices.
>
> Any pointers would be appreciated. I've only just embarked on this
> little adventure and I'm still relative new to Juniper platforms.
>
> Cheers,
> Dale
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list