Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 63

Issues in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers
interfaces, a jtree corruption might occur when a flap from a member link in the
aggregate occurs on the remote end, or the FPC of the remote router is rebooted. To
avoid this issue, use the option (
indirect-next-hop routing-options forwarding-table
). The error message "PFE: Detected error nexthop:" indicates a jtree
indirect-next-hop
corruption. [PR/548436: This issue has been resolved.]
In a multicast VPN scenario, if the default-vpn-source is configured under protocol
PIM, then the FPC holding is configured, the MS-PIC might core when it is taken offline.
[PR/550061: This issue has been resolved.]
A kernel core is generated when a logical interface that is a member of an AE bundle
is activated and deactivated. [PR/553392: This issue has been resolved.]
Routing Protocols
The output of the command does not display the hello packet
show ospf statistics
statistics. [PR/427725: This issue has been resolved.]
The mirror receive task variable may not be cleared when the routing protocol process
is heavily scaled. Hence, the NSR replication for RIP status stays in the "InProgress"
state indefinitely. [PR/516003: This issue has been resolved.]
Under rare circumstances, multiple commits might crash both Routing Engines. The
routing protocol process dumps core and restarts only on the master Routing Engine.
This issue occurs when commits are executed within one minute. [PR/516479: This
issue has been resolved.]
Upon an NSR mastership switch or ISSU upgrade, the multicast resolve route for IPv4
224/4 or inet6 ff00::/8 might be missing within the forwarding-table. To recover from
this condition, deactivate and activate the protocol pim stanza, or restart the routing
protocol process. [PR/522605: This issue has been resolved.]
For Junos OS Release 9.5 and above, the BGP parse community begins with "0" as the
octal value. This behavior is different in earlier releases. [PR/530086: This issue has
been resolved.]
The overload bit in the ISIS LSP MT-TLV may trigger the IS-IS to install a default route
to the overload bit advertiser. And the output of the show isis database extensive
command displays an unknown TLV. [PR/533680: This issue has been resolved.]
The routing protocol process might crash due to an invalid prefix-length value in one
of the flow-spec routes. [PR/534757: This issue has been resolved.]
If there is enough join state associated with a neighbor and that neighbor goes down
and comes back up quickly, then that join state may be stranded in an unresolved state
until the clear pim join command is issued. [PR/539962: This issue has been resolved.]
On Type 2 Trio MPC, multiple changes to a single term in quick succession can cause
an incorrect filter state in the Packet Forwarding Engine. This causes the MPC to crash.
[PR/540674: This issue has been resolved.]
The routing protocol process might crash when a BGP connection attempt meets with
an RST from the peer. This is due to an unlikely race condition. [PR/540895: This issue
has been resolved.]
Copyright © 2010, Juniper Networks, Inc. 63