Specifications

•
snmpwalk/snmpgetnext or "show snmp mib walk" fail when polling MPLSLSPOCTETS,
MPLSLSPPACKETS, MPLSLSPINFOOCTETS or MPLSLSPINFOPACKETS. PR981061
•
LSP metric modification leads to Constrained Shortest Path First(CSPF) computation
and resignaling. It should update RSVP routes directly. PR985099
•
In the MPLS environment with "egress-protection" configuration, there is a direct LDP
session between primary PE and protector. One context-id is configured as primary
PE's loopback address or any LDP enabled interface address. When delete the whole
apply-group or delete the ldp policy from apply-group, the routing protocol daemon
(rpd) might crash. PR988775
•
In the virtual private LAN service (VPLS) environment with multihoming (FEC 129) is
configured, when the router receives the label request for the Forwarding Equivalency
Class (FEC) 129, if there is no route for the specific FEC 129, the routing protocol daemon
might crash. PR992983
Network Management and Monitoring
•
Alarm management daemon runs on master and backup Routing Engine on dual
Routing Engine systems. There is a 80 megabyte alarm.db file that is copied over from
master Routing Engine to backup Routing Engine when the alarm-management daemon
has come up on both the Routing Engines. The basic issue is that alarm-management
daemon is trying to copy the alarm.db file over and over again in an infinite loop on the
system, causing CPU utilization to shoot up after every 20 seconds or so. PR988969
OpenFlow
•
OpenFlow v1.0 running on an MX Series router does not respond reliably to interface
up or down events within a specified time interval. Per a fix implemented in Junos OS
Release 13.3R3.6, OpenFlow v1.0 running on an MX Series router responds reliably to
interface up or down events if the echo interval timeout is set to 11 seconds or more.
PR989308
Platform and Infrastructure
•
Since the AC Power System on MX2020 is a N+N feed redundant and N+1 power supply
modules (PSMs) redundant, there are two separate input stages per PSM , each
connected to one of the two different/redundant feeds. However, only one stage is
active at a time. This means, the other input stage (unused input stage) may be bad
and system will not know about it till it tries to switch to it in case of a feed failure.
PR832434
•
When using OSPF/OSPFv3 with interface type point-to-point, it is possible that the
OSPF session (using multicast traffic exclusively) to come up before next-hop resolution
is done (ARP, or ND). In this case, transit traffic will be discarded, until resolution is
done. When you have multiple links available, then the route will be balanced using a
"unilist" next-hop. When one of the links in the "unilist" doesn’t have layer2 resolution,
these next-hops will actually drop traffic. The fix added by this PR will make unilist not
contain forwarding and non-forwarding at the same time. When the NH resolution will
be done, then the link will be added to the unilist. PR832974
119Copyright © 2015, Juniper Networks, Inc.
Resolved Issues