Juniper Networks JUNOS OS 10.4 - Manual (Page 94)

interface-mode trunk; # This is the trunk
vlan-id-list [ 10 20 30 40 50 ];
}
}
}
... # More interface statements
This configuration switches the departmental VLAN traffic (sales, engineering, etc.)
bridge domains over the VPLS pseudowire trunk connecting to the other site.
Configuration of Routing Instance and Interfaces Using Dynamic Profiles
Here is how dynamic profiles can be applied to this basic configuration.
First, consider the requirement to push an outer VLAN tag value of 200 onto the VPLS
pseudowire frames on egress. Dynamic profiles easily satisfy this requirement.
[edit routing-instance 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_1; # Apply profile here
}
... # Other routing instance statements
[edit dynamic-profiles]
green_vpls_pw_1 interfaces $junos-interface-ifd-name {
unit $junos-underlying-unit-number {
vlan-id 200; # This is the outer tag
family bridge {
interface-mode trunk;
inner-vlan-id-list [ 10 20 30 40 50 ];
}
}
}
NOTE: This is not a complete router configuration.
With the dynamic profile, a packet in a frame arriving on an interface is classified as
belonging to one of the bridge domains (VLANs 10–50). At the egress of the trunk VPLS
pseudowire, the outer VLAN tag 200 is pushed onto the frame. At the ingress of the
pseudowire at the remote location, the outer VLAN tag 200 is removed and the frame
is delivered to the appropriate bridge domain.
But what if the packets associated with the Accounting VLAN are not to be forwarding
to the remote site? Dynamic profiles are useful here as well.
This configuration keeps the Accounting frames from reaching the remote site.
[edit routing-instances green]
Copyright © 2013, Juniper Networks, Inc. 74
Junos OS 13.1 MX Series 3D Universal Edge Routers Solutions Guide