Mapping Vpls Traffic To Specific Lsps - Juniper EX9200 Features Manual

Mapping VPLS Traffic to Specific LSPs

Copyright © 2016, Juniper Networks, Inc.
You can include this statement at the following hierarchy levels:
[edit routing-instances routing-instance-name provider-tunnel rsvp-te]
[edit logical-systems logical-system-name routing-instances routing-instance-name
provider-tunnel rsvp-te]
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,
are high-priority LSPs between the PE routers, while
a-to-c1
low-priority LSPs between the PE routers.
NOTE: 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 {
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
levels:
[edit policy-options]
[edit logical-systems logical-system-name policy-options]
Chapter 8: Configuring Point-to-Multipoint LSPs
policy-statement vpls-priority
statement at the following hierarchy
a-to-b1 and
and are
a-to-b2 a-to-c2
statement:
75