Routing Protocols
■
If a static route is pointing to a discard configuration, a failure might occur when
the router attempts to collect the multicast statistic data. [PR/434298: This issue
has been resolved.]
■
Deleting a logical system causes the routing protocol process to be stuck in an
infinite loop. [PR/439000: This issue has been resolved.]
■
The routing protocol process periodically dumps core due to a failed soft assertion:
"rt_notbest_sanity: Path selection failure" in rt_table.c. [PR/451021: This issue
has been resolved.]
■
If the routing protocol process (rpd) experiences a restart, it may not receive the
first PIM hello packet from a PIM neighbor after the restart. This may delay the
establishment of PIM neighbors, and therefore multicast traffic convergence, for
up to twice the PIM hello interval. [PR/452751: This issue has been resolved.]
■
When the last CE interface in a VPLS instance goes down, pseudowires in the
VPLS instance are also removed. However, multicast snooping process does not
remove the logical interface indices corresponding to these pseudowires from
the OIF list of the default bd, mg, vlan routes. This leaves the multicast snooping
routes in an inconsistent state.
When a CE interface comes up again, new pseudowire comes up and OIF list
for the default bd, mg, vlan route is updated by the multicast snooping process.
The kernel finds a stale iflindex for the old pseudowire in the OIF list and rejects
the next-hop add. This problem persists until the multicast snooping process is
restarted. [PR/467347: This issue has been resolved.]
■
If a router modifies the next-hop protocol to self (for example, using an export
policy with next-hop-self) on a peer group containing "internal" peers, and
nonstop routing is configured on the router, the routing protocol process may
send duplicate updates to the peers in this peer group during a Routing Engine
switchover. [PR/468505: This issue has been resolved.]
■
When running PIM and a link flap occurs, the routing protocol process might
crash. [PR/480422: This issue has been resolved.]
■
When a PIC with a PIM-enabled interface is brought online, the router might
send the first PIM hello slightly before the interface comes up. This causes the
router to drop the first PIM hello message to its neighbor. [PR/482903: This issue
has been resolved.]
■
Whenever a graceful Routing Engine switchover (GRES) is performed, the BMP
header for the consequent updates may become corrupted until the BMP session
is deactivated and activated. [PR/486068: This issue has been resolved.]
■
The output of the
show igmp interfaces
command might display the configured
IGMP query-interval value incorrectly in the output. [PR/488146: This issue has
been resolved.]
■
In some conditions where the next-hop information must be merged for a new
configuration, some next-hop information does not merge correctly, causing the
routing protocol process to crash. [PR/489220: This issue has been resolved.]
90
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
