Specifications

•
The snmp trap generated when an ipv6 BFD session goes up/down does not contain
the ipv6 bfd session address. PR1018122
•
Junos OS implementation of RFC3107 uses unspecified label (0x000000) when
sending route with label withdrawn message. This means Junos OS sends 0x000000
instead of 0x800000 for label withdrawn, which is inconsistent with RFC3107.
PR1018434
•
Multicast packets might get dropped with NSR configured and graceful switch over of
the Routing Engine is performed. PR1020459
•
Establish two BFD sessions between two routers, one is single-hop BFD for directly
connected interface and the other is multi-hop MPLS OAM BFD. If configuring the
MPLS OAM on the same interface with single-hop BFD, when bringing down MPLS
OAM from the ingress, it might result in the OAM BFD session deleted on ingress but
it still receiving OAM BFD down packet from egress. Since there is no session matching
this BFD packet, it does a normal look up and brings down the single-hop BFD session
which is on the same interface. PR1021287
•
If auto-export feature is enabled together with rib-groups configuration option, the rpd
process might crash. PR1028522
•
In distributed BFD (which is enabled by default), if the CLIENT session (for example
BGP) flaps due to any reason, the multi-hop BFD session that comes Up after the flap
would not be delegated to FPC. PR1032617
•
When "clear bfd session" is issued immediately(before the Poll - Final sequence is
completed) post configuration check-in for interval change from higher to lower
minimum-interval value, BFD sessions do not revert to lower interval. PR1033231
•
Issue in populating IS-IS router table values. Some entries are not filled correctly. This
does not block/affect the functionality of IS-IS or other components. PR1040234
Services Applications
•
In the large scaled L2TP subscriber management environment (in this case, 60K tunnels
up with 1 session each). When logout and login 15K sessions, in rare condition, the jl2tpd
process (L2TP daemon) might crash. PR913576
•
If a destination-prefix or source-prefix is used like below example, the Network Address
Translation (NAT) rule and term names will be used to generate an internal jpool with
a form : _jpool_{rule_name}_{term_name}. If the generated jpool name exceeds 64
characters in length, it will get truncated. If the truncated jpool name get overlapped
with other generated jpool name it will lead to an inconsistent pool usage. user@router#
show services nat rule A_RULE_NAME_WHICH_IS_LONG_12345 { ... term
A_TERM_ALSO_WITH_LONG_NAME_1 { from { source-address { 10.20.20.1/32; } } then
{ translated { source-prefix 10.10.10.1/32; <--- translation-type { source static; } } } }
term A_TERM_ALSO_WITH_LONG_NAME_2 { from { source-address { 10.20.20.22/32;
} } then { translated { source-prefix 10.10.10.2/32; <--- translation-type { source static;
} } } } } First jpool =
_jpool_A_RULE_NAME_WHICH_IS_LONG_1234_A_TERM_ALSO_WITH_LONG_NAME_1
> 64 characters. Second jpool =
_jpool_A_RULE_NAME_WHICH_IS_LONG_1234_A_TERM_ALSO_WITH_LONG_NAME_2
Copyright © 2015, Juniper Networks, Inc.100
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series