
Routing Protocols
■
If a static route points 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 dumps core due to a soft assertion failed:
"rt_notbest_sanity: Path selection failure" in rt_table.c. As a workaround, use
the
bgp path-selection external-router-id
statement or the
bgp path-selection
always-compare-med
statement. [PR/451021: This issue has been resolved.]
■
When a PIC with a PIM-enabled interface is brought online, the router may send
the first PIM hello slightly before the interface comes up. This causes the router
to drop the first PIM hello message towards its neighbor. [PR/482903: This issue
has been resolved.]
■
After a graceful Routing Engine switchover (GRES) event with NSR enabled and
a scaled L3VPN eBGP test, some BGP sessions fail due to an expired hold down
timer if the hold-down timer is lower than the default 30 seconds. To avoid this
issue, set the hold-down timer to the default value of 30 seconds. [PR/501796:
This issue has been resolved.]
■
In an NSR configuration, the backup Routing Engine can lose the connection to
the active Routing Engine during a configuration commit. The problem occurs
more often when the configuration includes a large number of routing instances.
This is caused by the routing protocol process on the backup Routing Engine
leaking file descriptors during commit synchronization. To recover, restart the
routing protocol process on the backup Routing Engine. [PR/506883: This issue
has been resolved.]
■
When the
routing-instances
routing-instances-name
routing-options multipath
vpn-unequal-cost equal-external-internal
statement is configured, some VPN routes
learned from different route reflectors can be shown as multipath. [PR/507236:
This issue has been resolved.]
■
The routing protocol process might crash if the router receives a flow route with
a rate-limit bandwidth less than 1000 bps. [PR/508715: This issue has been
resolved.]
■
When more than 200 IGMP/MLD source-specific multicast groups (232.0.0.0/8)
are configured statically on an interface, and when an unrelated configuration
is committed, some groups are removed and added immediately after. This
causes packet drops on those groups. [PR/509013: This issue has been resolved.]
■
Nonstop routing (NSR) does not work correctly if an automatic route distinguisher
is used with a L2VPN routing-instance. [PR/513949: This issue has been resolved.]
■
In route reflector and ASBR VPN scenarios, the routing protocol process might
crash as changes occur to a prefix in the primary table at the same time as BGP
tries to send out updates via the secondary table. [PR/515626: This issue has
been resolved.]
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
79
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers