Specifications

error=301 Nov 16 12:19:21 jtac-host jpppd: Profile: PPPoE-1-QoS variable:
$junos-cos-shaping-rate value: failed semantic check PR1042247
•
clear interfaces interface-set statistics all fails due to memory limitation. PR1045683
•
On MX Series routers (platforms) with Enhanced Switch Control Board (SCBE), when
the fan tray is inserted or pulled out, the chassisd process might crash. PR1048021
•
When Inherit is part of lower logical interface Unit, VRRPD parses it before Active. In
this case, VRRPD attaches a dummy Active to the Inherit, with the assumption that
the Active will be available soon and then replication of information from Active to
Inherit will take place. However, the replication of the priority was not done correctly
due to which the Inherit group was stuck with priority of 0. PR1051135
•
mru remains set at previous value after deleting mru under group-profile ppp-options.
PR1059720
Layer 2 Features
•
On multiple Routing Engines system with NSR enabled, if the FEC129 VPLS instance
has "no-tunnel-service" configured, the VPLS might show status as "OL" (no outgoing
label) after performing Routing Engine switchover. PR1050744
•
After FPC restart, bridge domain (BD) implicit filters for Ethernet ring protection
switching (ERPS) might get reprogrammed with wrong logical interface (ifl) index,
which cause ERPS to not work correctly. PR1021795
•
If a customer is using SNMP and performs an snmpwalk on the dhcp binding table, not
all of the entries may be displayed. This fix resolves that issue so that bindings for all
IP addresses are displayed. PR1033158
•
On a router with DHCP local server configured, if there are scaled number of DHCP
subscribers connected, most of the subscribers might get stuck in "RELEASE" status
after performing graceful Routing Engine switchover (GRES). PR1038385
•
In DHCP dynamic subscriber management scenario, when maintain DHCP subscribers
during interface delete is configured, some interface indices might be reused by a new
interface if system is under stress (such as high connection speed, many clients and
individual log files configured to be larger than 100M). In this case, it might result in
subscriber being associated with an interface that no longer exists. PR1044002
MPLS
•
Error "tag_icmp_route:failed to find a chain composite ahead of fwd nh" might be
observed when doing traceroute. PR999034
•
When configuring point-to-multipoint (P2MP) Label Distribution Protocol (LDP)
label-switched paths (LSPs), the labels will never be freed even though they are no
longer needed. This could lead to the MPLS label exhaustion eventually. To clear the
state, the rpd process will restart with core files. PR1032061
•
On the P2MP LSP transit router with link protection enabled, if the LSP is the last
subLSP, tearing the last subLSP (for example, an RESV tear message is received from
downstream router) might crash the routing protocol process (rpd). PR1036452
85Copyright © 2015, Juniper Networks, Inc.
Resolved Issues