■
The routing protocol process may core frequently because of malformed BGP
updates generated by the JUNOS Software. This might be because of the total
length and the path attribute length. [PR/489891: This issue has been resolved.]
■
When multicast RPF routes are configured, the
show route rib-groups
command
causes the routing protocol process (RPD) to go into an infinite loop. [PR/490390:
This issue has been resolved.]
■
The MPLS LSPs are not advertised as links into the non-backbone OSPF areas,
even though they are configured to be advertised. [PR/491692: This issue has
been resolved.]
■
The PIM running in the main instance might stop working if the PIM is configured
in a no-forwarding routing instance. [PR/492017: This issue has been resolved.]
■
If there are enough routing instances with PIM configured, and there is enough
IGMP/MLD join state present and a configuration change is made, a routing
protocol process scheduler slip might occur. [PR/493062: This issue has been
resolved.]
■
On an unnumbered Ethernet interface in P2P mode, OSPF does not skip
validation of the network mask received in the hello packets. This could result
in a failure to bring up an adjacency on such interfaces while interoperating with
other vendors. As a workaround, convert the interface to a regular numbered
interface on both sides. [PR/493206: This issue has been resolved.]
■
In a NSR configuration, the backup Routing Engine can lose the connection to
the active Routing Engine during 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 is less than 1000 bps. [PR/508715: This issue has been
resolved.]
■
In route reflector and ASBR VPN scenarios, the routing protocol process might
crash when 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
■
91
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
