Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 65

Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
On SG3 PICs (Multiservices 500) with graceful Routing Engine switchover (GRES),
wrong record values are seen for the IPv4 netflow export packets. This error occurs
when the route records are not installed. [PR/545422: This issue has been resolved.]
The IPv6 and MPLS route counts are not reflected in the output of the
accounting status command. [PR/550793: This issue has been resolved.]
User Interface and Configuration
In a router configured with a large number of interfaces, when few interfaces are
constantly added and deleted, a minor memory leak may be observed in the "pfed"
process. [PR/522346: This issue has been resolved.]
While a configuration with a long as-path is displayed in XML format using the
configuration | display xml | no-more
is wrongly displayed as </path instead of </path>. [PR/525772: This issue has been
resolved.]
The xnm service currently does not support logging of remote-host addresses in system
accounting. [PR/535534: This issue has been resolved.]
It is possible to login to J-Web from a web browser having a cipher strength of 40 and
56 bits. This could create a security issue. As a workaround, use a web browser that
supports 128 bit of cipher strength. [PR/539477: This issue has been resolved.]
The system continues to use the TACACS server configuration even after it is removed.
As a workaround, deactivate and reactivate the accounting configuration. [PR/544770:
This issue has been resolved.]
When the command is used to refresh a script file, the script does not refresh,
load set
and exits from the CLI after displaying the rpc-related errors. [PR/555316: This issue
has been resolved.]
VPNs
When two MVPN routing instances and at least one L2VPN routing instance are
configured, the commit fails with the following message: "RPD_RT_DUPLICATE_RD:
routing-instance xxx has duplicate route-distinguisher." As a workaround, configure
the route-distinguisher-id for each instance manually. [PR/511514: This issue has been
resolved.]
If a VPN routing and forwarding (VRF) instance contains a static route that is resolved
via a route that is auto-exported from another routing instance, the static route may
not be removed when the physical interface goes down. [PR/531540: This issue has
been resolved.]
When a CE-facing interface in a VPLS instance is deactivated, the routing protocol
process may get into a loop leading to a high CPU utilization. [PR/531987: This issue
has been resolved.]
Under certain circumstances, the container interfaces might not send the proper martini
modes to the routing protocol process. This results in incorrect control-word-related
command, the closing tag for the as-path <path>
show service
show
65