Routing Policy and Firewall Filters
■
On some M, MX, and T Series routers, when a family CCC filter is applied on
multiple interfaces that belong to different L2VPN routing instances, packet loss
may occur after the routing instances are deactivated and activated. As a
workaround, deactivate and activate the CCC filter on the interfaces. [PR/521357:
This issue has been resolved.]
Routing Protocols
■
The backup Routing Engine may generate routing protocol process and kernel
cores if the BGP damping is configured along with nonstop active routing (NSR).
[PR/452217: This issue has been resolved.]
■
When l3vpn-composite-next-hop is configured, it should only be used by L3VPN
routes. However, non-L3VPN routes are also able to use it. [PR/496028: This
issue has been resolved.]
■
Upon a graceful Routing Engine switchover with NSR, the routing protocol process
will crash due to a wrong process for the PIM instance. [PR/503921: This issue
has been resolved.]
■
Nonstop routing (NSR) does not work correctly if an automatic route distinguisher
is used with an L2VPN routing-instance. [PR/513949: This issue has been
resolved.]
■
The output of the
show igmp snooping interface
command does not display
"-snooping," erroneously stating that IGMP itself is not running instead of
IGMP-snooping not running. [PR/516355: This issue has been resolved.]
■
The configured robust count value is not applied on the non-querier router when
it receives a robust count value of 0. It uses the default value (2) instead of the
configured value. [PR/520252: This issue has been resolved.]
■
The new NSR master may not send the OSPF hello messages immediately after
a switchover. [PR/522036: This issue has been resolved.]
■
After a graceful restart, the forwarding state of both provider edge routers might
get stuck at the pruned state. However, traffic flow is not affected. [PR/522179:
This issue has been resolved.]
■
When an l2circuit ID greater than 2,147,483,647 is configured, and l2circuit
tracing is enabled using the set protocols l2circuit traceoptions command, some
of the trace messages provide the wrong value (a negative number) for the virtual
circuit ID. [PR/523492: This issue has been resolved.]
■
The tag_encoder is unable to handle attempts to stack EXPLICIT_V6_ NULL (label
2) over an existing stack with label 2 on top. Additionally, the BGP module does
not send label 2 when readvertising a prefix from an inet6 unicast session to a
inet6 labeled-unicast session. [PR/523824: This issue has been resolved.]
■
On TX Matrix routers, the router can drop the PIM hello messages before a join
is triggered by the neighbor. This can cause multicast traffic to be dropped before
the next periodic join. [PR/529408: This issue has been resolved.]
■
When the labeled-unicast inet6 route is reflected by route reflectors, the label
might be set to explicit-null. [PR/534150: This issue has been resolved.]
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
71
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
