ifd 153; does not exist
IFRT: 'IFD Ether autonegotiation config' (opcode 163) failed
The message has no operational impact. When the backup CFEB becomes the
active CFEB, the message will not display. [PR/400774]
■
On M7i routers, kernel panic may occur during route changes. [PR/439420]
■
In some cases, the alarms displayed in FPM and the alarms shown using the
show chassis alarms sfc 0
command mismatch. [PR/445895]
■
The SFC management interface
em0
is often displayed as
fxp0
in several warning
messages. [PR/454074]
■
The VPN label does not get pushed on the label stack for Routing
Engine–generated traffic with l3vpn-composite-next-hop activated. As a
workaround, configure per-packet load balancing to push the VPN/tunnel labels
correctly. [PR/472707]
■
An invalid IP protocol version is served as a valid version. The JUNOS router
forwards IP packets with version field set to values other than 4 and 6, for
example, 11 or any (unassigned). [PR/481071]
■
The tty sessions to a router can cause a null pointer de-reference. [PR/502816]
■
The TTL for a GRE-encapsulated IPv6 packet malfunctions as the TTL on the wire
is one less than the CLI-configured tunnel TTL. [PR/506454]
■
The VPN PIM neighborship over the mt- interfaces may not recover after a
graceful Routing Engine switchover. [PR/511366]
■
Setting the TCP maximum segment size (MSS) may not change the actual MSS
value. [PR/514196]
■
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]
■
When IGMP snooping is enabled, a multicast traffic drop might occur if an IGMP
join or leave occurs on other interfaces. [PR/515420]
■
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]
Routing Policy and Firewall Filters
■
If a routing protocol running an MSDP receives an SA that is filtered via the MSDP
import policy, it will still create a forwarding entry if it subsequently receives a
(*,G) join for that group. [PR/63053]
■
The following features are not supported in a 12-16x10G DPC:
■
Known unicast and unknown unicast types in the input match condition
'Traffic-type' in a family bridge/VPLS
■
The following match conditions do not work:
60
■
Issues in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes