Juniper Networks JUNOS OS 10.4 - Manual (Page 96)

interface-mode trunk;
inner-vlan-id-list [ 10 20 40 50 ]; # Removed Accounting VLAN 30
}
}
}
NOTE: This is not a complete router configuration.
In this case, frames arriving on the interfaces are classified according to their bridge
domains and switched, if necessary, to the VPLS pseudowire trunk with an outer VLAN
tag of 200, except for Engineering frames. Engineering frames (VLAN 30) are only
switched within the interfaces listed within bridge domain
accounting and any statically
configured trunk interfaces and are prevented from crossing the VPLS pseudowire due
to the absence of VLAN 30 on the trunk.
Configuration of Tag Translation Using Dynamic Profiles
Consider a final case where the bridge domain VLANs need translation at the VPLS
pseudowire trunk interface. In this case,
sales (VLAN 10) is mapped to VLAN 110 and
engineering (VLAN 20) is mapped to VLAN 120.
This configuration adds tag translation to the VPLS pseudowire traffic.
[edit routing-instances green]
instance-type virtual-switch;
... # Other routing instance statements
protocols vpls {
site-range 10;
site sample-site-1 {
site-identifier 1;
}
associate-profile green_vpls_pw_4; # Apply profile here
}
... # Other routing instance statements
[edit dynamic-profiles]
green_vpls_pw_4 interfaces $junos-interface-ifd-name {
unit $junos-underlying-unit-number {
family bridge {
interface-mode trunk;
vlan-id-list [ 10 20 30 40 50 ]; # All VLANs
vlan-rewrite translate 110 10; # Sales VLAN
vlan-rewrite translate 120 20; # Engineering VLAN
}
}
}
NOTE: This is not a complete router configuration.
Copyright © 2013, Juniper Networks, Inc. 76
Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide