Mapping VPLS Traffic to Specific LSPs
You can map VPLS traffic to specific LSPs by configuring forwarding table policies. This procedure is optional but can be useful. The following example illustrates how you can map lower priority VPLS routing instances to slower LSPs while mapping other higher priority VPLS routing instances to faster LSPs. In this example configuration, a-to-b1 and a-to-c1 are high-priority LSPs between the PE routers, while a-to-b2 and a-to-c2 are low-priority LSPs between the PE routers.
In the VPLS documentation, the word router in terms such as PE router is used to refer to any device that provides routing functions.
To map VPLS traffic, include the policy-statement vpls-priority statement:
policy-statement vpls-priority {
term a {
from {
rib mpls.0;
community company-1;
}
then {
install-nexthop lsp [ a-to-b1 a-to-c1 ];
accept;
}
}
term b {
from {
rib mpls.0;
community company-2;
}
then {
install-nexthop lsp-regex [ "^a-to-b2$" "^a-to-c2$" ];
accept;
}
}
}
community company-1 members target:11111:1;
community company-2 members target:11111:2;
You can include the policy-statement vpls-priority statement at the following hierarchy levels:
[edit policy-options][edit logical-systems logical-system-name policy-options]
Include the export statement to apply the vpls-priority policy to the forwarding table:
export vpls-priority;
You can include this statement at the following hierarchy levels:
[edit routing-options forwarding-table][edit logical-systems logical-system-name routing-options forwarding-table]
For more information about how to configure routing policies, see the Routing Policies, Firewall Filters, and Traffic Policers User Guide.