Specifications

General Routing
•
The ingress family feature (uRPF) unicast Reverse Path Forwarding check execution
order was invalidated when (FBF) Filter Based Forwarding was enabled on MX Series
routers with MPCs or MICs. This solution repositions uRPF just prior to Filter Based
Forwaarding (FBF), so that both actions are compatible and applicable. This applies
to both IPv4 and IPv6. PR805599
•
On MX Series routers containing multiple Packet Forwarding Engines such as
MX240/MX480/MX960/MX2010/MX2020, with either MPC3E or MPC4E cards (MPC3
Type 3 3D/MPC4E 3D 2CGE+8XGE/MPC4E 3D 32XGE), if multicast traffic or Layer 2
flood traffic enters the router via these MPC3E or MPC4E line cards, these line cards
may exhibit a lockup, and one or more of their Packet Forwarding Engines corrupt traffic
towards the router fabric. PR931755
•
In the MX-VC scenario, have chassis fabric redundancy mode set to increased bandwidth
(root@user# set chassis fabric redundancy-mode increased-bandwidth). Then
configure the "offline-on-fabric-bandwidth-reduction" for any slot (root@user# set
chassis fpc <slot> offline-on-fabric-bandwidth-reduction). After that execute commit,
the commit check failed and chassisd crashed with core-dumps. PR932356
•
This problem occurs when a large amount of services and ams configuration is changed
in a single override operation. A workaround for this problem is to offline and online
the PIC during or after the configuration change. PR933674
•
In Junos OS versions later than 11.2 where IFL localization is enabled, Routing Engine
mastership switchover could lead to IFL indexes inconsistency in Ichip FPCs when
graceful Routing Engine switchover (GRES) is configured. This inconsistency could
gradually lead to IFL index overlaps and traffic blackholing. PR940122
•
When nonstop active routing (NSR) is configured and the memory utilization of rpd
process on the backup Routing Engine is high (1.4G or above), the rpd crash on backup
Routing Engine may bounce the BGP sessions on the master Routing Engine. PR942981
•
Under particular scenarios, commit action might lead the Context-Identifier to be
ignored when OSPF protocol refresh its database. Then the PE router will stop
advertising this Context-Identifier out. PR954033
•
FPC might lose the socket connection to the Routing Engine during the time kernel
live-core dump is active. IGP session might get dropped after the socket connection
got closed. The FPC will get restarted by the kernel once the live-core dump has finished.
PR954045
•
Software will monitor the FPD dial setting in SFC and LCC and raise a alarm if changed
during runtime. In SFC the config dial and in LCC M/S dial will be monitored. PR955319
•
"show interfaces et-x/y/z extensive" will display MRU now. MRU can be configured at
"set interfaces et-x/y/z gigether-options mru" If MRU is not configured then it is
defaulted to MTU + 8. MRU displayed from the CLI does not include the CRC. PR958162
•
To support control word on BGP-VPLS for M-320 (i-chip) and MX (DPC + MPC), below
2 config knobs are newly introduced. routing-instances { green { protocols { vpls { +
control-word; <<<<<<<<< new knob. + no-control-word; <<<<<<<< new knob. } } }
} To omit IP payload over ether-pw from hash-key for MX Series, A new knob like below
Copyright © 2015, Juniper Networks, Inc.112
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series