Specifying The Vt Interfaces Used By Vpls Routing Instances; Understanding Pim Snooping For Vpls - Juniper EX9200 Features Manual

VPLS Feature Guide for EX9200 Switches

Specifying the VT Interfaces Used by VPLS Routing Instances

Understanding PIM Snooping for VPLS

38
By default, the Junos OS automatically selects one of the virtual tunnel (VT) interfaces
available to the router for de-encapsulating traffic from a remote site. The Junos OS
cycles through the currently available VT interfaces, regularly updating the list of available
VT interfaces as new remote sites are discovered and new connections are brought up.
However, you can also explicitly configure which VT interfaces will receive the VPLS
traffic.
By including the tunnel-services
routing-instance-name protocols vpls]
particular VPLS routing instances be forwarded to specific VT interfaces. Doing so allows
you to load-balance VPLS traffic among all the available VT interfaces on the router.
The tunnel-services statement includes the following options:
—Specifies the VT interfaces acceptable for use by the VPLS routing instance.
devices
If you do not configure this option, all VT interfaces available to the router can be used
for de-encapsulating traffic for this instance.
—Specifies the primary VT interface to be used by the VPLS routing instance.
primary
The VT interface specified is used to de-encapsulate all VPLS traffic from the MPLS
core network for this routing instance. If the VT interface specified is unavailable, then
one of the other acceptable VT interfaces (specified in the devices option) is used for
handling the VPLS traffic. If you do not configure this option, any acceptable VT interface
can be used to de-encapsulate VPLS traffic from the core.
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 specify that traffic for a particular VPLS routing instance be forwarded to specific VT
interfaces, include the
tunnel-services
tunnel-services {
devices device-names;
primary primary-device-name;
}
These statements can be configured at the following hierarchy levels:
[edit routing-instances routing-instance-name protocols vpls]
[edit logical-systems logical-system-name routing-instances routing-instance-name
protocols vpls]
There are two ways to direct PIM control packets:
By the use of PIM snooping
statement at the [edit routing-instances
hierarchy level, you can specify that traffic for
statement:
Copyright © 2016, Juniper Networks, Inc.