Specifications

VPNs
•
Enhanced multicast VPNs traceoptions statement (M Series, MX Series, and T
Series)—Starting in Junos OS Release 13.3, the multicast VPNs traceoptions statement
has been enhanced starting in Junos OS Release 13.3. This statement can now be
configured at the [edit protocols mpvn] hierarchy level. In addition, the following
traceoption flags have been added: cmcast-join, inter-as-ad, intra-as-ad, leaf-ad,
mdt-safi-ad, source-active, spmsi-ad, tunnel, and umh.
[See Tracing MBGP MVPN Traffic and Operations.]
•
Enhanced egress protection in Layer 3 VPNs (M Series, MX Series, and T
Series)—Starting in Junos OS Release 13.3, enhanced point-of-local-repair (PLR)
functionality is available, in which the PLR reroutes service traffic during an egress
failure. As part of this enhancement, the PLR router no longer needs to be directly
connected to the protector router. Previously, if the PLR was not directly connected
to the protector router, the loop-free alternate route did not find the backup path to
the protector. A new configuration statement, advertise-mode, enables you to set the
method for the interior gateway protocol (IGP) to advertise egress protection
availability.
[See Configuring Layer 3 VPN Egress Protection with RSVP and LDP.]
•
Control word for BGP VPLS (M320 and MX Series)—For hash calculation, transit
routers must determine the payload. While parsing an MPLS encapsulated packet for
hashing, a transit router can incorrectly calculate an Ethernet payload as an IPv4 or
IPv6 payload if the first nibble of the DA MAC is 0x4 or 0x6, respectively. This false
positive can cause out-of-order packet delivery over a pseudowire. Starting in Junos
OS Release 13.3R3, this issue can be avoided by configuring a BGP VPLS PE router to
request that other BGP VPLS PE routers insert a control word between the label stack
and the MPLS payload.
•
Loop prevention in VPLS network due to MAC moves (MX Series)— Starting with
Junos OS Release 13.3R3, the base learning interface approach and the statistical
approach can be used to prevent a loop in a VPLS network by disabling the suspect
customer facing interface that is connected to the loop. Some virtual MACs can
genuinely move between different interfaces and such MACs can be configured to
ignore the moves. The cooloff time and statistical approach wait time are used internally
to find out the looped interface. The interface recovery time can be configured to
auto-enable the interface that gets disabled due to a loop in the network. To configure
these parameters of VPLS MAC moves, include the vpls-mac-move statement at the
[edit protocols l2-learning] hierarchy level. The show vpls mac-move-action instance
instance-name command displays the learning interfaces that are disabled, in a VPLS
instance due to a MAC move. The clear vpls mac-move-action interface ifl-name
command enables an interface disabled due to a MAC move.
Related
Documentation
Changes in Behavior and Syntax on page 54•
• Known Behavior on page 68
• Known Issues on page 70
53Copyright © 2015, Juniper Networks, Inc.
New and Changed Features