Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Release Note page 58

JUNOS 10.1 Software Release Notes
Network Management
MPLS Applications
Platform and Infrastructure
58
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
SNMP may stop working after a router reboot, DPC/FPC/MPC restart, or a graceful
Routing Engine switchover. [PR/525002]
The column in the output of the
rt
counter in the output of the
when the per-packet load balancing is configured. [PR/22376]
The routing protocol process may sometimes crash at rsvp_find_lp_tag_route.
[PR/55748]
For point-to-multipoint label-switched paths configured for VPLS, the
command reports a 100 percent packet loss even though the VPLS connection
is active. [PR/287990]
The routing protocol process might crash with an assert in rsvp_PSB_set_selfID
while a graceful Routing Engine restart is performed when P2MP LSPs are present.
[PR/512890]
During an RSVP local repair process, when a link flaps or the IGP metric changes
along the LSP path, the routing protocol process scheduler slips. [PR/513312]
On T Series routers, a Layer 2 maximum transmission unit (MTU) check is not
supported for MPLS packets exiting the routing platform. [PR/46238]
When you configure a source class usage (SCU) name with an integer (for
example, 100) and use this source class as a firewall filter match condition, the
class identifier might be misinterpreted as an integer, which might cause the
filter to disregard the match. [PR/50247]
If you configure 11 or more logical interfaces in a single VPLS instance, VPLS
statistics might not be reported correctly. [PR/65496]
When a large number of kernel system log messages are generated, the log
information might become garbled and the severity level could change. This
behavior has no operational impact. [PR/71427]
In the situation where a Link Services (LS) interface to a CE router appears in
the VPN routing and forwarding table (VRF table) and a fragmentation is required,
Internet Control Message Protocol (ICMP) cannot be forwarded out of the LS
interface from a remote PE router that is in the VRF table. As a workaround,
include the statement at the
vrf-table-label
hierarchy level. [PR/75361]
routing-instance-name]
Traceroute does not work when ICMP tunneling is configured. [PR/94310]
If you ping a nonexistent IPv6 address that belongs to the same subnet as an
existing point-to-point link, the packet loops between the two point-to-point
interfaces until the time-to-live expires. [PR/94954]
command and the
show mpls lsp
show mpls lsp extensive command are incorrect
[edit routing-instances
active route
ping mpls