■
Setting the TCP maximum segment size (MSS) may not change the actual MSS
value. [PR/514196: This issue has been resolved.]
■
On M120 and MX Series routers, when an AE interface (with LACP enabled) is
used as a core-facing interface for L3VPN, non-MPLS traffic received on the AE
interface can sometimes get black-holed. To recover from this state, deactivate
and activate the AE interface in the configuration. [PR/514278: This issue has
been resolved.]
■
When IGMP snooping is enabled, a multicast traffic drop might occur if an IGMP
join or leave occurs on other interfaces. [PR/515420: This issue has been
resolved.]
■
When the primary link flaps with the
route-memory-enhanced
statement enabled,
jtree might get corrupted and traffic forwarding is affected. As a workaround,
deactivate the
route-memory-enhanced
statement under the chassis stanza.
Changes to the
route-memory-enhanced
statement take effect only when Packet
Forwarding Engine is rebooted. [PR/517919: This issue has been resolved.]
■
On some M, MX, and T Series routers, when a firewall filter is applied on the
egress of an aggregate interface, packet loss may occur after adding, removing,
or changing the service configuration on the egress side of the aggregate interface.
As a workaround, deactivate and activate the output firewall filter on the aggregate
interface. [PR/517992: This issue has been resolved.]
■
When container AE interfaces are enabled on JUNOS Release 10.0 or 10.1, the
following message displays when one of the member links flap: “CHPJAR1-re0
fpc3 SCHED: %PFE-0: Thread 40 (PFE Manager) ran for 2015 ms without
yielding.” [PR/518714: This issue has been resolved.]
■
When the destination class usage (DCU) is configured with unicast reverse path
filter (uRPF) and egress forwarding-table filter within the VRF, a VPN route flap
might trigger a jtree memory leak. [PR/521609: This issue has been resolved.]
■
No NA packets are returned for NS requests with a static NDP, due to an issue
with the neighbor advertisement implementation for statically configured
neighbors. [PR/527779: This issue has been resolved.]
■
On some routers, enabling IP-payload-based load balancing for MPLS packets
can cause some pseudowire packets to be reordered. [PR/528657: This issue
has been resolved.]
70
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
