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
vrf-table-label
statement at the
[edit routing-instances
routing-instance-name
]
hierarchy level. [PR/75361]
■
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]
■
On T Series and M320 routers, multicast traffic with the "do not fragment" bit
is being dropped due to configuring a low MTU value. The router might stop
forwarding all traffic transiting this interface if the
clear pim join
command is
executed. [PR/95272]
■
A firewall filter that matches the forwarding class of incoming packets (that is,
includes the
forwarding-class
statement at the
[edit firewall filter
filter-name
term
term-name
from]
hierarchy level) might incorrectly discard traffic destined for the
Routing Engine. Transit traffic is handled correctly. [PR/97722]
■
The JUNOS Software does not support dynamic ARP resolution on Ethernet
interfaces that are designated for port mirroring. This causes the Packet
Forwarding Engine to drop mirrored packets. As a workaround, configure the
next-hop address as a static ARP entry by including the
arp
ip-address
statement
at the
[edit interfaces
interface-name
]
hierarchy level. [PR/237107]
■
When you perform an in-service software upgrade (ISSU) on a routing platform
with an FPC3 or an Enhanced FPC3 with 256 MB of memory and the number
of routes in the routing table exceeds 750,000, route loss might occur. If route
loss occurs, as a workaround, perform either of the following tasks:
■
Replace the FPC3 or Enhanced FPC3 with another FPC that has more
memory, or
■
After the ISSU is complete, reboot only the FPC3 or Enhanced FPC3.
[PR/282146]
■
For Routing Engines rated at 850 MHz (which appear as
RE-850
in the output of
the
show chassis hardware
command), messages like the following might be
written to the system log when you insert a PC Card: “bad Vcc request” and
“Device does not support APM.” Despite the messages, operations that involve
the PC card work properly. [PR/293301]
■
On a Protected System Domain, an FPC might generate a core file and stop
operating under the following conditions:
■
A firewall policer with a large number of counters (for example, 20,000) is
applied to a shared uplink interface, and
■
The FPC that houses the interface does not have a sufficiently powerful CPU.
As a workaround, reduce the number of counters or install a more powerful FPC.
[PR/311906]
■
When a CFEB failover occurs on an M10i or M7i router that has had 4000 or
more IFLs, the following message appears:
IFRT: 'IFD ioctl' (opcode 10) failed
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
59
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
