Specifications
•
Adding AE configuration and child interface configuration as two separate commits:
a. Add AE interface configuration, without adding child interface configuration.
b. Commit.
c. Add the child interface configuration (et interface configurations) for the AE
interface.
d. Commit.
PR901744
MPLS
•
In an RSVP P2MP crossover/pass-through scenario, more than one sub-LSP can use
the same PHOP and NHOP. If link protection is enabled in the above-mentioned
scenario, when a 'primary link up' event is immediately followed by a Path Tear message,
disassociation of the routes/nexthops are sequential in nature. When the
routes/nexthops disassociation is in progress, if a sub-LSP receives a path tear/PSB
delete will lead to this core file. PR739375
•
When a PTX Series router is a penultimate hop of one P2MP LSP branch and acts as
a transit LSR on another branch for the same P2MP LSP, the MPLS packets going out
from the penultimate hop branch might be tagged with an incorrect Ethertype field.
PR867246
•
RPD (routing-protocol process) generates a core file on receipt of an RESV message
with an unexpected next-hop address. To avoid the crash, drop the RESV message
with a different next-hop IP address, and then the LSP will time out due to lack of
refresh by the RESV message and the session is reset. PR887734
•
Changing the preference on an LSP was considered a catastrophic event, tearing down
the current path and then re-establishing a new one. This PR makes the preference
change minor and only needs a new path to be re-signalled in a make-before-break
manner. PR897182
183Copyright © 2015, Juniper Networks, Inc.
Resolved Issues