interfacege-0/0/0.1;
...# Other interfaces and statements forSales
}
engineering{
vlan-id20;
interfacege-1/0/2.0;
...# Other interfaces and statements forEngineering
}
accounting{
vlan-id30;
interfacege-2/0/3.0;
...# Other interfaces and statements forAccounting
}
others{
vlan-id—list[ 40 50 ]; # Other departements
}
}
protocolsvpls {
site-range10;
sitesample-site-1 {
site-identifier1;
}
}
...# Other statements for instance Blue
[editinterfaces]
ge-0/0/1{
unit0 {
vlan-id100;
}
}
ge-3/0/0{
unit0 {
familybridge {
interface-modetrunk; # This is the trunk
vlan-id-list[ 10 20 30 40 50 ];
}
}
}
...# More interface statements

Thisconfiguration switches the departmental VLAN traffic(sales, engineering, etc.)

bridgedomains over the VPLS pseudowire trunk connecting tothe other site.

Configurationof Routing Instance and InterfacesUsing Dynamic Profiles

Hereis how dynamic profiles can be applied to this basic configuration.

First,consider the requirement to push an outer VLAN tag valueof 200 onto the VPLS

pseudowireframes on egress. Dynamic profiles easilysatisfy this requirement.

[editrouting-instance green]
instance-typevirtual-switch;
...# Other routing instance statements
protocolsvpls {
site-range10;
69Copyright© 2010, Juniper Networks,Inc.
Chapter6: Dynamic Profiles forVLAN Interfaces and Protocols