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.]
■ 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.]
■ Route changes might not be updated in the PIC meta-db in cases where the route
messages that the PIC receives signify a change in the next-hop index.
[PR/512229]
User Interface and Configuration
■ The wildcard apply groups do not work properly in JUNOS Release 9.1 and above.
[PR/425355: This issue has been resolved.]
■ If a user in the Backup Routing Engine on a config-private mode activates graceful
Routing Engine switchover (GRES) and performs a commit synchronize, a
synchronization error might occur during the switchover. [PR/486637: This issue
has been resolved.]
■ Commit fails when the commit scripts are used and the configuration contains
a policy which uses an apply-group with a then action of 'then community +
export.' [PR/501876: This issue has been resolved.]
■
The load replace command does not consider the allow-configuration
configuration. [PR/501992: This issue has been resolved.]
■ In configure private mode, activating and deactivating two consecutive nested
objects can cause a syntax error during commit. [PR/506677: This issue has
been resolved.]
■ On M10i, M120, M320, and MX Series routers with dual Routing Engines running
JUNOS Release 9.4 or later, the dfwd process running on the backup Routing
80 ■ Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
To Next Page
Loading...
Need help?
General
