Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 61

Copyright © 2010, Juniper Networks, Inc.
Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
Network Management
The SNMP process might restart when a core dump is generated. [PR/517230: This
issue has been resolved.]
In Junos OS Release 10.2 and later, the size of the MIB2D process might increase as a
result of memory leaks. This causes the MIB2D process to crash as it reaches its
maximum permitted size. [PR/546872: This issue has been resolved.]
In Junos OS Release 9.2 and later, a memory leak occurs in the subagent in a scenario
where the snmpd process is not running, or there are issues in communication with a
subagent and traps are being generated by the subagent. [PR/547003: This issue has
been resolved.]
When the firewall filter policer configuration is changed, the SNMP MIBs might not
update correctly. As a result, the counters are inaccessible. [PR/555719: This issue has
been resolved.]
Platform and Infrastructure
Redirect drops that are not real errors is taken into account for "Iwo HDRF" error
statistics that is reported in the output of the
I-chip based routers. Since redirect drops are expected in a VPLS (and Ethernet in
general) environment, this behavior could be misleading. [PR/430344: This issue has
been resolved.]
After an 8216 Routing Engine upgrade to Junos OS Release 9.6 with "chassis"
deactivated, the backup Routing Engine starts to reboot with the panic message "panic:
filter_idx_alloc: invalid filter index," and crashes when the chassis configuration is
enabled and committed. After the Routing Engine finally comes online, the CLI response
is slow and the Routing Engine reboots again after approximately three minutes. To
stop these reboots, deactivate the chassis on the backup Routing Engine. [PR/489029:
This issue has been resolved.]
On T Series routers, the FPC might continuously reboot upon installation. [PR/510414:
This issue has been resolved.]
When the system default-router a.b.c.d
installed in the Packet Forwarding Engine. [PR/523663: This issue has been resolved.]
In an MPLS environment, the source NAT or PAT for traffic between two remote VPNs
does not work when the
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.]
show pfe statistics errors
command is used, the default route is not
option is removed from the VRF where the
vrf-table-label
command on
61