Previous Releases - Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note

Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
the following error message is displayed "Internet Explorer was not able to open the
Internet site."
This issue also appears in the following places on the J-Web interface:
maintain->config management->history
maintain->customer support->support information->Generate Reports
Troubleshoot port->Generate Reports
maintain->files
Monitor->Routing->Route Information->Generate Reports
[PR/542887]
The J-Web pages loads inconsistently when Add IPv4 or IPv6 filters are used in the
Internet Explorer and Firefox Web browsers. [PR/543607]
After the "delete:" action is performed, the "replace" actions do not take effect in the
"load replace terminal" operation. [PR/556971]
The javascript error, "Object Expected" occurs when J-Web pages are navigated before
the page loads completely. [PR/567756]
VPNs
On a router configured for nonstop active routing (NSR) (the
is included at the
[edit routing-options]
switchover occurs after the configuration for routing instances changes in certain ways,
the BGP sessions between PE and CE routers might not be established after the
switchover. [PR/399275]
The routing protocol process crashes when the rd value of an old instance is different
from the rd value of a new instance in the VLAN ID. [PR/512499]

Previous Releases

Release 10.3R2
The following issues have been resolved since Junos OS Release 10.3R2. The identifier
following the description is the tracking number in our bug database.
Class of Service
When a VLAN ID is changed, the following message appears in the messages log:
"COSD_GENCFG_WRITE_FAILED: GENCFG write failed for Classifier to IFL 74. Reason:
File exists." This log message appears when the configuration is committed with VPLS
configured on the Gigabit Ethernet interface, and a class-of-service classifier or rewrite
rules that contain IEEE 802.1P on the interface are used. [PR/408552: This issue has
been resolved.]
When a logical interface set has a shaping-rate less than the sum of transmit-rates of
its queues and when the configuration is corrected so that the logical interface set gets
the correct shaping-rate, ADPC might crash. [PR/523507: This issue has been resolved.]
nonstop-routing
hierarchy level), if a nonstop active routing
statement
55