Specifications

•
In current Junos OS, a PSM shows dc output value even though it is turned off by a
switch. This cosmetic bug causes miscalculation of actual usage in 'show chassis
power'. PR960865
•
Upon the deletion of a routing-instance and subsequent commit, error logs are
generated from each Type 1 - 3(non E3) based FPC. These logs are cosmetic and can
be ignored. PR964326
Routing Policy and Firewall Filters
•
Policy with Install-nexthop lsp might not work as expected when there is an LSP path
change triggering route resolution. PR931741
•
Configuration of an extended community such as: rt-import:*:* src-as:*:* fails because
the wildcard is not allowed during the configuration validation process. PR944400
Routing Protocols
•
On MX Series routers containing multiple Packet Forwarding Engines such as
MX240/MX480/MX960/MX2010/MX2020 routers, with DPC (Dense Port
Concentrator) or FPC (Flexible Port Concentrator) or with line cards designated with
"3D", RPD might restart when attempting to send a PIM assert message on an interface
(whose interface index exceeds 65536). It is likely that RPD restarts repeatedly, since
after RPD has restarted and protocols have converged, the same PIM assert will trigger
further RPD restarts. PR879981
•
On the first hop router if the traffic is received from a remote source and the
accept-remote-source knob is configured, the RPF information for the remote source
is not created. PR932405
•
Due to new features and the required infrastructure the rpd memory footprint has
increased by as much as 5% between Releases 12.3 and 13.3. PR957550
•
In scaled BGP routes environment, the BGP router has dual Routing Engines, graceful
Routing Engine switchover (GRES) and nonstop active routing (NSR) is configured,
after performing the operation of deactivate/activate BGP groups and commit the
configuration, the BGP router might be stuck in "not-advertising" state. PR961459
•
With BGP import policy as next-hop peer-address, if the local router receives inet (or
inet-vpn) flow network-layer reachability information (NLRI), routing protocol process
(rpd) might crash. Junos OS is designed to create a fictitious next hop for inet flow and
inet-vpn flow families as they don't send/expect-to-receive next hops. So in this case
when the import-policy set a non-null next-hop for the received inet (or inet-vpn) flow
route, it could not handle it properly which might result in rpd crash. PR966130
•
In a scaled setup, if BGP peers flap during an NSR, the sessions can end up out of sync
between the master and backup Routing Engines. To recover you can clear the affected
neighbors. PR966206
•
In a highly scaled setup after an NSR, some BGP sessions might be idle on both master
and backup Routing Engines. To recover, clear the affected peer using the CLI. PR967788
133Copyright © 2015, Juniper Networks, Inc.
Resolved Issues