Specifications

•
TXP with 13.1R4 might not trigger autoheal after 65535 CRC error event on inter-chassis
optical hsl2 link. Customer will need to do manual fabric plane reset to recover the
faulty SIBs after the 65535 CRC error event. PR988886
•
NPC core /../src/pfe/ukern/cpu-ppc/ppc603e_panic.c:68. PR989240
•
On logical-systems, backup rpd of logical systems is not getting SIGHUP when the
"commit fast-synchronize" statement at the [edit system] hierarchy level is enabled.
It causes the issue "restarting backup rpd" of logical systems (as part of recovery
mechanism). PR990347
•
When two midplane link errors are present between F13 and F2 Sibs then CLOS rerouting
logic does not work properly. This can introduce RODR packet drops and result in
destination errors in the plane. PR992677
•
"delete" or "deactivate" of apply-group defining the entire TACACS or RADIUS
configuration configured under [edit system apply-group <>] does not take effect on
commit. This could lead to TACACS or RADIUS based authentication to still continue
working despite removal (delete/deactivate) of configuration. PR992837
•
On MX Series router with MPCs or MICs or T4000 router with type5 FPC, if the CoS
scheduler is configured without transmit-rate while with buffer-size temporal, the
Packet Forwarding Engine might not allocate buffer for the associated queue. The
issue might lead to packets loss. PR999029
•
The configuration to be applied to the feature auto backup Routing Engine upgrade
for NON-GRES case when back up Routing Engine has unsupported CB. policy
FRU-UNSUPPORTED { events CHASSISD_FRU_UNSUPPORTED; attributes-match {
CHASSISD_FRU_UNSUPPORTED.fru-name matches CB; } then { event-script
auto-image-upgrade.slax; } } event-script { file auto-image-upgrade.slax; }
Recommended setting: -------------------- Since above
CHASSISD_FRU_UNSUPPORTED event generated for every 20 mins on box after boot
up, to stop from repetitive execution of this event policy, we can specify following
'within clause' in the event policy configuration. policy FRU-UNSUPPORTED { events
CHASSISD_FRU_UNSUPPORTED; within 1200 { not events
CHASSISD_FRU_UNSUPPORTED; } attributes-match {
CHASSISD_FRU_UNSUPPORTED.fru-name matches CB; } then { event-script
auto-image-upgrade.slax; } } event-script { file auto-image-upgrade.slax; } PR1000476
Routing Protocols
•
In PIM-SM network with "bootstrap routing" RP selection mechanism used, it is observed
that some bootstrap messages (BSMs) generation and forwarding behavior of Junos
OS does not conform to RFC standard, specifically in the section 3.2 (Bootstrap
message generation), 3.3 (Sending Candidate-RP-Advertisement Messages) and 3.4
(Creating the RP-Set at the BSR). PR871678
•
In Protocol Independent Multicast (PIM) scenario, if interface get deleted before the
(S,G) route is installed in the Routing Information Base (RIB), then this interface index
might be re-used by kernel for another interface and thus cause routing protocol process
(rpd) core. PR913706
Copyright © 2015, Juniper Networks, Inc.122
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series