Table of Contents
Advertisement
Copyright © 2011, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
In an MPLS environment, the source NAT or PAT for traffic between two remote VPNs
does not work when the
vrf-table-label
inside-service interfaces are located. [PR/524294: This issue has been resolved.]
When VPLS is configured on the router, the following log messages will appear when
the interface goes down:
RT-HAL,rt_entry_delete_msg_proc,XXX: route add posthandler failed
RT-HAL,rt_msg_handler,XXX: route process failed
These messages can be ignored. [PR/524548: This issue has been resolved.]
After the MS-PIC's homing PE interfaces used for MVPN are taken offline and brought
back online, the following message may be logged: "flip-re0 fpc3 SLCHIP(0): %PFE-3:
Channel 8189 (iif=701) on stream 32 already exists." [PR/527813: This issue has been
resolved.]
The Packet Forwarding Engine incorrectly imposes a rate limit function for the
host-bound virtual LAN tagged packets with IEEE 802.1p value of 1. There is no
workaround. [PR/529862: This issue has been resolved.]
A router might send raw IPv6 host-generated packets over the Ethernet towards its
BGP IPv6 peers. [PR/536336: This issue has been resolved.]
BGP authentication does not work with the 64-bit Junos OS BGP route reflector on a
JCS platform. BGP sessions fail to establish, and the following error message is
observed: "... /kernel: tck_auth_ok Packet from XXX.XXX.XXX.XXX:XXXXX wrong MD5
digest." [PR/538076: This issue has been resolved.]
On M10i routers, an upgrade to Junos OS Release 10.2 fails and aborts when the PIC
combinations are verified. As a workaround, first verify the PIC combinations manually
against PSN-2010-06-777, then use the force option to override the warnings and force
the upgrade. [PR/540468: This issue has been resolved.]
In Junos OS Release 10.3, the following messages may be seen in the syslog: "/kernel:
sysctl_nd6_mmaxtries: 3, max solicit testing setting of paramsysctl_nd6_mmaxtries:
3, max solicit testing setting of paramsysctl_nd6_mmaxtries: 3, max solicit testing
setting of paramsysctl_nd6_mmaxtries: 3, max solicit testing setting of
paramsysctl_nd6_mmaxtries: 3, max solicit testing setting of param /kernel:
sysctl_nd6_prune: 1, retrans timer testing setting of paramsysctl_nd6_prune: 1, retrans
timer testing setting of paramsysctl_nd6_prune: 1, retrans timer testing setting of
paramsysctl_nd6_prune: 1, retrans timer testing setting of paramsysctl_nd6_prune: 1,
retrans timer testing setting of param." These messages are cosmetic. [PR/540808:
This issue has been resolved.]
During SNMP queries in Junos OS Release 10.2 and later, the size of the MIB2D process
might increase as a result of memory leaks in a statistics-associated library routine
(libstats). This causes the MIB2D process to crash as it reaches its maximum permitted
size. [PR/541251: This issue has been resolved.]
During router bootup, the error messages: "can't re-use a leaf (nd6_prune)!" and "can't
re-use a leaf (nd6_mmaxtries)!" display. [PR/543422: This issue has been resolved.]
option is removed from the VRF where the
73
Advertisement
Table of Contents
