Specifications

•
In a highly scaled configuration, the reroute of transit RSVP LSPs can result in BGP flap
due to lack of keepalive messages being generated by the Routing Engine. PR946030
•
The RSVP bandwidth of the aggregated Ethernet (AE) bundle does not adjust properly
when a member link is added to AE interface, and at the same time an IP address is
removed from this AE bundle. PR948690
•
On IS-IS interfaces configured with point-to-point and ldp-synchronization, after a
change of IP address on the interface from the remote router, and if the old Label
Distribution Protocol (LDP) adjacency times-out after the new LDP adjacency is up,
the IS-IS protocol will be notified about the old LDP adjacency down event and the
LDP sync state will remain in "hold-down" even if the new LDP adjacency is up.
PR955219
•
When Packet Forwarding Engine fast reroute (FRR) applications are in use (such as
MPLS facility backup, fast-reroute, loop free alternates), a flap of the primary path
could be triggered due to an interface flap or by Bidirectional Forwarding Detection
(BFD) session flap. However, this interface/session flap might lead to a permanent
use of the backup path, which means the original primary path could not be active
again. PR955231
•
We add timer for all aggregate LDP prefixes but are not deleting it when the timer
expires because of a bug. Since the timer is not expiring, we never update the route for
any change. This will be sitting in the routing table as a stale entry. PR956661
•
The Label Distribution Protocol (LDP) feature is enabled and the background job "LDP
sync send filtered label job" is running, when shut down the LDP, due to LDP failing to
delete a job that didn't exist while shutting down, routing protocol process (rpd) might
crash. PR968825
Platform and Infrastructure
•
In an MX-VC environment, in certain situations the inter-chassis traffic might not be
equally balanced across all available vcp links after adding extra links. PR915383
•
Transit traffic is being improperly classified and competing with legitimate control
plane traffic. PR924807
•
With MX Series routers with MPCs or MICs, changing the MTU on one interface might
cause Layer 2 traffic interruption on other interfaces in the same FPC. PR935090
•
When chained-composite-nexthop ingress L3VPN is configured, and if two PEs are
directly connected, the unicast nexhhop on egress is IPv4 protocol encapsulated only
and no LSP label push, thus COS rewrite mask could not correctly set by IPv4 Unicast
nexthop, which leads to MPLS exp rewrite not working. PR941066
•
TWAMP connection/session will come up only if the session padding length is greater
than or equal to 27 bytes on the TWAMP Client. The valid range of padding length
supported by the TWAMP Server is 27 bytes to 1400 bytes. If IXIA is used as the TWAMP
Client, packet length range from 41 bytes to 1024 bytes is supported. PR943320
•
In a highly congested system (for example, high multicast traffic rate),
traffic/subscribers loss might occur while performing unified in-service software upgrade
(ISSU). PR945516
131Copyright © 2015, Juniper Networks, Inc.
Resolved Issues