Something that is seemingly difficult to find clearly described in plain english for JunOS, is 801.ad L3 Service Provider tunnel termination.
Ie; QinQ tunnels to/from sites using the 0x88a8 ethertype, wherein you terminate to an L3 interface on the innermost vlan.
Unsurprsingly (perhaps), the config is largely similar between Cisco IOS and Juniper JunOS.
That said, both configs still feel somewhat bulky, but I think that's really just the nature of the beast.
Some config I've labbed, and also test against some non-production services on the MX platform follows;
interfaces { xe-0/1/0 { description "QinQ bundle from provider"; flexible-vlan-tagging; gigether-options { ethernet-switch-profile { tag-protocol-id 0x88a8; } } unit 1001 { description "CCI/NNI Tail 1001 to site Foocity"; encapsulation vlan-bridge; vlan-tags outer 0x88a8.1001 inner 10; } } irb { unit 1001 { description "CCI/NNI Tail 1001 to site Foocity"; family inet { address 10.0.0.1/29; } } } } bridge-domains { vlan1001 { description "Foocity"; domain-type bridge; vlan-id none; interface xe-0/1/0.1001; routing-interface irb.1001; } }
For comparison sake, and the non JunOS savvy, The Cisco 7600 (and mostly, ASR equivalent) is pretty similar. Just replace the sub-interface with the service instance stanza.
interface TenGigabitEthernet1/11 description QinQ bundle from provider no ip address dot1q tunneling ethertype 0x88A8 no keepalive service instance 1001 ethernet description CCI/NNI Tail 1001 to site Foocity encapsulation dot1q 1001 second-dot1q 10 rewrite ingress tag pop 2 symmetric bridge-domain 1001 ! interface Vlan1001 description CCI/NNI Tail 1001 to site Foocity ip address 10.0.0.1 255.255.255.248 ! vlan 1001 name Foocity ! end
