vlan-tagsouter 200 inner 100;
}
}
NOTE: Thisis not a complete routerconfiguration.
Withthis configuration, broadcast packetsinside frames arriving with VLAN identifier
100on ge-0/0/1 are normalized to a frame with VLAN identifier 100 (in this case, they
areunchanged). The broadcast packetand frames egressing ge-0/0/2 or ge-0/0/3 are
unchangedas well, according to the interfaceconfiguration. Frames egress the VPLS
pseudowirein routing instance greenwith an outer VLAN tag value of 200 pushed on top
ofthe normalized value.
Related
Documentation
MXSeries Ethernet Services Routers SolutionsPage•
•DynamicProfiles for VPLS Pseudowireson page 63
•Example:Configuring VPLS Pseudowires with Dynamic Profiles—ComplexSolutions
onpage 68
Example:Configuring VPLS Pseudowires with Dynamic Profiles—ComplexSolutions
Dynamicprofilesfor VPLS pseudowires can be helpful in a variety of VLAN configurations.
Thissection explores some of these situations throughexamples.
NOTE: Theseexamples are not completerouter configurations.
Allof the examples in this section address the same basic topology.A routing instance
blueuses a trunk bridge to connect different departments in an organization,each with
theirown VLANs, at two different sites. The organizationuses a BGP-based VPLS with
avirtual switch to accomplish this.
•ConfigurationofRouting Instance and Interfaces WithoutDynamic Profiles on page 68
•Configurationof Routing Instance and InterfacesUsing Dynamic Profiles on page 69
•Configurationof TagTranslation Using Dynamic Profileson page 72

Configurationof Routing Instance and InterfacesWithout Dynamic Profiles

Thebasic configuration of routing instanceand interfaces without dynamic profiles
follows:
[editrouting-instance blue]
instance-typevirtual-switch;
route-distinguisher10.1.1.10:1;
vrf-targettarget:1000:1;
interfacege-3/0/0;# The trunk interface
bridge-domains{
sales{
vlan-id10;
Copyright© 2010, Juniper Networks,Inc.68
Junos10.4 MX Series Ethernet ServicesRouters Solutions Guide