Specifications

•
PIC level "account-layer2-overhead" knob with ethernet-bridge doesn't add
"Adjustment Bytes". As a workaround, configure it under interface level. PR946131
•
Egress multicast statistics display incorrectly after flapping of ae member links on
M320 or T Series FPC (M320 non-E3 FPC and T Series non-ES FPC). PR946760
•
With scaled configuration of ATM VCs (~4000 VCs) on a single
MIC-3D-8OC3-2OC12-ATM ATM MIC, the MIC might crash. The crash is not seen with
lower scale (i.e. less than 3500 VCs per MIC). PR947434
•
When configuring "no-readvertise" flag to existing static route, then this static route
will not exported to other VPN routing and forwarding (VRF) tables from onwards
which is expected. However, for the static route that has already exported to other
VRF tables before "no-readvertise" configuration, no deletion event occurs. Also, the
"rt-export" bit still set for the static route which is exported to other routing tables after
"no-readvertise" configuration. PR950994
•
CLI command "show interfaces queue" does not account for interface queue drops
due to Head drops. This resulted in the "Queued" packets/bytes counter to be less
than what was actually received and dropped on that interface queue. This PR fixes
this issue. Head-drops, being a type of RED mechanism, are now accounted under the
"RED-dropped" section of the CLI command "show interfaces queue". PR951235
•
In a scaled network and on a multi-chassis platform with BGP ECMP configured, when
the master Routing Engine of line-card chassis (LCC) crashes, LCC would go through
a reboot process to bring up the backup Routing Engine, during which the neighbor
session of BGP over aggregated Ethernet (AE) interface might get broken. This is
because the Unilist NHs of the AE are stuck at standby state and therefore no traffic
can be transmit through. PR953365
•
On systems running Junos OS Release 13.3R1 and nonstop active routing (NSR) is
enabled, when "switchover-on-routing-crash" under [edit set system] hierarchy is set,
Routing Engine switchover should happen only when the routing protocol process
(rpd) crashes. But unexpected Routing Engine switchover can be seen when performing
the CLI command "request system core-dump routing running" to manually generate
a rpd live core. PR954067
•
If an aggregated Ethernet (AE) interface has the "scaled" member-link scheduling
mode (which is the default mode), and multiple forwarding-classes map to a same
queue, then the actual transmit-percent might be unable to reach the configured
scheduler. PR954789
•
Default threshold for ES-FPC errors is 1 for major errors and 10 for minor errors, when
the threshold is reached, some actions (for example,
alarm|offline-pic|log|get-state|offline|reset) will be taken by FPC as configured. This
feature is designed for permament/real errors. The issue here is that even some transient
errors (eg, link flaps) will also trigger the default action. In some cases, it might cause
panic for the FPC. PR961165
•
Sessions are getting reset when SFW rule and/or NAT term are added/deleted in a
service set having NAT also. PR961353
•
On T Series or M320 routers with OSPF knob, if have large-scale routes (for example,
180K Composite Nexthop), when do costing-out and costing-in operations along with
127Copyright © 2015, Juniper Networks, Inc.
Resolved Issues