■
The routing protocol process might crash if the router receives a flow route with
a rate-limit bandwidth is less than 1000 bps. [PR/508715: This issue has been
resolved.]
■
In route reflector and ASBR VPN scenarios, the routing protocol process might
crash when 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.]
■
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.]
■
When an SIP ALG is enabled on ASPIC, MSPIC, or MSDPC, the PIC could crash
while freeing the Via header NAT port. [PR/490329: 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.]
■
In some call scenarios, the SIP ALG on a services PIC can cause NAT port leaks.
[PR/491220: This issue has been resolved.]
■
The
show services nat pool
name
CLI filter does not have any effect. [PR/493820:
This issue has been resolved.]
■
Under certain conditions, the replication socket between two Routing Engines
for the local policy decision function process (LPDFD) does not close properly.
This results in high CPU consumption by the LPDFD. As a workaround, restart
the local policy decision function process (LPDFD) on the master Routing Engine’s
restart local-policy-decision-function. [PR/495363: This issue has been resolved.]
■
Configuring different autonomous system types (origin and peer) toward two v5
servers does not work and origin is taken as the autonomous system type for
both flow servers. [PR/496954: This issue has been resolved.]
■
Following a JUNOS Software upgrade, the L2TP on an M7i router dumps core.
[PR/498423: This issue has been resolved.]
■
When the router reboots after an upgrade, the following commit error occurs:
“Cannot configure local-dump without configuring file name in neither
traceoptions nor output.” [PR/500365: This issue has been resolved.]
■
When a backup gateway is configured in any term under IPsec stanza, for any
subsequent terms where this backup gateway is now configured as the primary,
IPsec tunnel establishment will fail. [PR/510608: This issue has been resolved.]
■
When using a NAT DCE RPC ALG on a services PIC, the PIC might crash while
processing the binding request. [PR/510997: This issue has been resolved.]
84
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes