NOTE: Thisis not a complete routerconfiguration.
Inthis case, frames arriving on the interfaces areclassified according to their bridge
domainsand switched,if necessary, to the VPLS pseudowiretrunk, except for Engineering
frames.Engineering frames (VLAN 30) are only switched within the interfaceslisted
withinbridge domain accounting and any statically configuredtrunk interfaces and are
preventedfrom crossing the VPLS pseudowiredue to the absence of VLAN 30 on the
trunk.
Wecan combine the two examplesand use dynamic profiles to forward the frames
(otherthan accounting frames) to the remote sitewith an out tag of 200.
Thisconfigurationkeeps the Accounting framesfrom reaching the remote site and pushes
anouter tag of 200 on VPLS pseudowire traffic.
[editrouting-instances green]
instance-typevirtual-switch;
...# Other routing instance statements
protocolsvpls {
site-range10;
sitesample-site-1 {
site-identifier1;
}
associate-profilegreen_vpls_pw_3;# Apply profile here
}
...# Other routing instance statements
[editdynamic-profiles]
green_vpls_pw_3interfaces $junos-interface-ifd-name{
unit$junos-underlying-unit-number {
vlan-id200; # This is the outer tag
familybridge {
interface-modetrunk;
inner-vlan-id-list[ 10 20 40 50 ]; # Removed AccountingVLAN 30
}
}
}
NOTE: Thisis not a complete routerconfiguration.
Inthis case, frames arriving on the interfaces areclassified according to their bridge
domainsand switched, if necessary, tothe VPLS pseudowire trunk with an outer VLAN
tagof 200, except for Engineering frames. Engineeringframes (VLAN 30) are only
switchedwithin the interfaces listed within bridgedomain accounting and any statically
configuredtrunk interfaces and are preventedfrom crossing the VPLS pseudowire due
tothe absence of VLAN 30 on the trunk.
71Copyright© 2010, Juniper Networks,Inc.
Chapter6: Dynamic Profiles forVLAN Interfaces and Protocols