■
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 com
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
Engine might access the
/var/pdb/rdm.taf
file every 30 seconds, causing excessive
writes to the hard disk drive. This problem does not occur when GRES is enabled.
[PR/506691: This issue has been resolved.]
VPNs
■
When different prefixes are advertised to the same source by different PE routers,
an egress PE router is prevented from picking the lower prefix route for RPF
when the PR advertising the higher prefix loses its route to the source.
[PR/493835: This issue has been resolved.]
■
When multipath is enabled in a routing instance with NG MVPN, the traffic might
get dropped on the receiver PE. [PR/508090: This issue has been resolved.]
Previous Releases
Release 10.1R1
The following issues have been resolved since JUNOS Release 10.0R3. The identifier
following the description is the tracking number in our bug database.
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
73
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers