Option: Selecting an LSP for the VPLS Routing Instance to Traverse
If you have two or more equal-cost-path LSPs between your VPLS PE router sites, you can select an LSP over which the VPLS traffic will travel. To select an LSP for VPLS traffic, assign the VPLS instance to a BGP community, define a policy that directs community traffic over a specified LSP, and then apply the policy to the forwarding table.
To configure a BGP community, include the community community-name statement at
the [edit policy-options] hierarchy level. Be sure to specify
the vrf-export or vrf-target values from the
VPLS routing instance as community identifiers with the members community-ids statement at the [edit policy-options community community-name] hierarchy level.
To create a policy that sends community traffic
over a specific LSP, include the community community-name statement at the [edit policy-options policy-statement policy-name term term-name from] hierarchy level and the install-nexthop lsp lsp-name statement at the [edit policy-options policy-statement policy-name term term-name then] hierarchy level. To apply the policy to the forwarding table, include
the export policy-name statement at
the [edit routing-options forwarding-table] hierarchy level.
[edit]
routing-options {
autonomous-system 69;
forwarding-table {
export LSP-policy;
}
policy-options {
policy-statement LSP-policy {
term a {
from community gold;
then {
install-nexthop lsp pe1-to-pe2;
accept;
}
}
}
community gold members target:11111:1;
}
}