Table of Contents
Advertisement
JUNOS OS 10.4 Release Notes
76
Services Applications
In Junos OS Release 10.0 and later, the routing instance name is restricted to 63
characters. [PR/533882: This issue has been resolved.]
The BGP_IPV4_NEXT_HOP field on the jflow v9 record matches the originator ID instead
of the BGP next hop. [PR/534598: This issue has been resolved.]
When traffic is forwarded in an L2TP session and a teardown request is received, the
ASPIC crashes with a memory access violation in mlppp_output. [PR/537225: This
issue has been resolved.]
On M Series routers configured for L2TP tunneling with several thousands of PPP
connections, when all the PPP sessions expire at the same time, the Multiservices PIC
might hang and become unusable. To recover the service, restart the PIC. [PR/541793:
This issue has been resolved.]
On Multiservices 500 PICs 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.]
command, the closing tag for the as-path <path>
Copyright © 2011, Juniper Networks, Inc.
show service
show
Advertisement
Table of Contents
