[j-nsp] Stiching L2 to L3 on MX480

[Pshem Kowalczyk]

Hi,

Thank you for your replies on and off-list.
I'll be building this early next year.

kind regards
Pshem


On Fri, 22 Dec 2017 at 20:39 Wojciech Janiszewski <
wojciech.janiszewski at gmail.com> wrote:

> Hi Pshem,
>
> Yes, you can. Just as I described in my previous post.
>
> Regards,
> Wojciech
>
>
> 22.12.2017 00:43 "Pshem Kowalczyk" <pshem.k at gmail.com> napisał(a):
>
> Hi,
>
> Can we use this for non-BNG functions as well? Despite a large number all
> of those VLANs are 'static' customers.
>
> kind regards
> Pshem
>
>
> On Thu, 21 Dec 2017 at 23:01 <adamv0025 at netconsultings.com> wrote:
>
> > Hi Pshem,
> >
> > The feature designed specifically for what you are looking for is
> > pseudowire
> > headend (or pseudowire headed termination PWHT on junos). I'm just really
> > surprised no one mentioned it already.
> > The limit is 2048 in 15.1 and should be raised to around 15k on 17.1.
> > But as always you should do a fair amount of scaling and performance
> > testing
> > to see if it's suitable for your product scale and BW requirements.
> >
> > I feel your pain when I was designing Carrier Ethernet  solution several
> > years ago when there was no PWHE available had to use two routers at the
> > head-end one to terminate PW into qinq and other with L3 to VRF.
> > The only other option was bridge-domain per PW which obviously does not
> > scale (well not at scales I needed anyways).
> >
> > adam
> >
> > netconsultings.com
> > ::carrier-class solutions for the telecommunications industry::
> >
> > > -----Original Message-----
> > > From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On
> Behalf
> > > Of Pshem Kowalczyk
> > > Sent: Tuesday, December 19, 2017 10:07 PM
> > > To: juniper-nsp at puck.nether.net
> > > Subject: [j-nsp] Stiching L2 to L3 on MX480
> > >
> > > 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
> >
> >
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>