■
In an NSR configuration, the backup Routing Engine can lose the connection to
the active Routing Engine during a configuration commit. The problem occurs
more often when the configuration includes a large number of routing instances.
This is caused by the routing protocol process on the backup Routing Engine
leaking file descriptors during commit synchronization. To recover, restart the
routing protocol process on the backup Routing Engine. [PR/506883: This issue
has been resolved.]
■
When the
routing-instances
routing-instances-name
routing-options multipath
vpn-unequal-cost equal-external-internal
statement is configured, some VPN routes
learned from different route reflectors can be shown as multipath. [PR/507236:
This issue has been resolved.]
■
The routing protocol process might crash if the router receives a flow route with
a rate-limit bandwidth less than 1000 bps. [PR/508715: This issue has been
resolved.]
■
When more than 200 IGMP/MLD source-specific multicast groups (232.0.0.0/8)
are configured statically on an interface, and when an unrelated configuration
is committed, some groups are removed and added immediately after. This
causes packet drops on those groups. [PR/509013: This issue has been resolved.]
■
Nonstop routing (NSR) does not work correctly if an automatic route distinguisher
is used with a L2VPN routing-instance. [PR/513949: This issue has been resolved.]
■
In route reflector and ASBR VPN scenarios, the routing protocol process might
crash as changes occur to a prefix in the primary table at the same time as BGP
tries to send out updates via the secondary table. [PR/515626: This issue has
been resolved.]
Services Applications
■
If the Juniper-Firewall-Attribute attribute in a RADIUS server configuration file
names a policer that sets a bandwidth limit for Layer 2 Tunneling Protocol (L2TP)
sessions but not an exclude-bandwidth limit, the bandwidth limit might not be
set correctly. [PR/254503: This issue has been resolved.]
■
On M Series routers (M120 and M320) with many service sets configured with
IDP policies, kernel messages are seen in the messages file once traffic passes
through these service sets. These messages stop when the traffic is stopped.
[PR/462580: This issue has been resolved.]
■
A static route pointing to a destination is incorrectly added for a source NAT
when a next-hop type service set is used. [PR/476165: This issue has been
resolved.]
■
Flow monitoring records are not generated as fragmented IPv6 packets are not
getting sampled. [PR/478571: This issue has been resolved.]
■
MSDPC might crash while running a combination of SIP and other ALGs due to
a possible double freeing of memory. [PR/491218: This issue has been resolved.]
■
The SIP ALG on the services PIC might cause NAT port leaks in some call
scenarios. [PR/491220: This issue has been resolved.]
■
The l2tp on an M7i LNS crashes following an upgrade from JUNOS Release 9.3R1
to 9.6R2. [PR/498423: This issue has been resolved.]
72
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes