[j-nsp] QinQ on MX bridge-ing

[Robert Hass]

I'll try. But what about VLAN 102 and 103 ?
I have also IRB on VLAN 102


On Thu, Apr 16, 2015 at 1:40 AM, Chris Kawchuk <juniperdude at gmail.com>
wrote:

> Try this
>
> set interfaces ge-2/1/2 flexible-vlan-tagging
> set interfaces ge-2/1/2 mtu 9192
> set interfaces ge-2/1/2 encapsulation flexible-ethernet-services
> set interfaces ge-2/1/2 unit 100 encapsulation vlan-bridge
> set interfaces ge-2/1/2 unit 100 vlan-id 100
>
> set interfaces ge-2/1/3 flexible-vlan-tagging
> set interfaces ge-2/1/3 mtu 9192
> set interfaces ge-2/1/3 encapsulation flexible-ethernet-services
> set interfaces ge-2/1/3 unit 100 encapsulation vlan-bridge
> set interfaces ge-2/1/3 unit 100 vlan-id 100
>
> set interfaces ge-2/1/5 mtu 9192
> set interfaces ge-2/1/5 encapsulation ethernet-bridge
> set interfaces ge-2/1/5 unit 0 family bridge
>
> set protocols protection-group ethernet-ring erpsring1 data-channel vlan
> 100  //* if you're using ERPS for failover on a ring of EX42's, which you
> should -- to avoid using dreaded spanning tree protocols ;)
>
> set bridge-domains QinQ vlan-id 100
> set bridge-domains QinQ interface ge-2/1/2.100
> set bridge-domains QinQ interface ge-2/1/3.100
> set bridge-domains QinQ interface ge-2/1/5.0;
>
> 2/1/2 and 2/1/3 are the "trunk" ports, you only care about the outer tag
> here. (its double tagged coming in from the EX42, but you dont care at this
> point)
> 2/1/5 is the "access port" which pops the outer tag on egress, slaps it on
> on ingress; regardless if it's already tagged coming in.
>
> - CK.
>
>
>
>
>
>
>
>
>
>