Hi Pshem, I'd terminate l2circuits from ACX directly on pseudo-wire interfaces (psX).
By example: PE1: set chassis fpc 2 pic 1 tunnel-services bandwidth 10g set interfaces ps1 anchor-point lt-2/1/0 set interfaces ps1 flexible-vlan-tagging set interfaces ps1 unit 1234 vlan-id 1234 set interfaces ps1 unit 1234 family inet address 1.2.3.4/24 set protocols l2circuit neighbor 10.200.1.21 interface ps1.0 virtual-circuit-id 1 set protocols l2circuit neighbor 10.200.1.21 interface ps1.0 encapsulation-type ethernet set protocols l2circuit neighbor 10.200.1.21 interface ps1.0 ignore-mtu-mismatch set protocols l2circuit neighbor 10.200.1.21 interface ps1.0 pseudowire-status-tlv PE2: set interfaces ge-2/0/6 unit 1 encapsulation vlan-ccc set interfaces ge-2/0/6 unit 1 vlan-id-range 1-2000 set protocols l2circuit neighbor 10.200.1.1 interface ge-2/0/6.1 virtual-circuit-id 1 set protocols l2circuit neighbor 10.200.1.1 interface ge-2/0/6.1 encapsulation-type ethernet set protocols l2circuit neighbor 10.200.1.1 interface ge-2/0/6.1 ignore-mtu-mismatch Regards, Wojciech 2017-12-19 23:07 GMT+01:00 Pshem Kowalczyk <[email protected]>: > 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 [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
