[j-nsp] Stiching L2 to L3 on MX480

[Chris Kawchuk]

1. Use VPLS and add a LDP "Mesh-group" to it -- this extends the L2CKT from the ACX via standard Martini/L2CKT to the MX.
2. Put an IRB inside the VPLS for the L3 routing into your inet.0 table (or whatever VRF of you choice)
3. Adjust the vpls type to "irb-only" so that it doesnt go down if no CE interfaces are detected. (may or may not need this though, as the L2CKT may be classified as a CE, can't remember)
4. Enforce QoS on the ACX at the hand-off point (policer inbound, shaper outbound)
5. If you have QinQ, pop the outer-tag on ingress at the ACX so that it appears only as CTAG to the VPLS on the MX.

- CK.


On 20 Dec 2017, at 9:07 am, Pshem Kowalczyk <pshem.k at gmail.com> wrote:

> Hi,
> 
> We have an existing setup consisting of a number of ACX5k and MX480 (single
> MPLS domain). We generally provide L2 services out of the ACXes and L3 out
> of the MXes. Now, a new requirement emerged to provide L3 (with features
> that ACX can't provide) in locations where we can't justify the MX.
> I'd like to know if it's possible to do the following (and if anything
> special is required on the MX)
> 1. Build a L2 PWE3 taking whole port on the ACX and logically terminate it
> on the MX
> 2. The logical port on the MX (I presume 'lt') will be used to terminate
> individual dot1q and QinQ services into L3 VPNs.
> 
> Looking at the documentation it appears to be possible, but I'd like to
> know what sort of limitations this solution might have, particularly when
> it comes to QoS on the MX.
> 
> kind regards
> Pshem
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp