Table of Contents
Advertisement
JUNOS OS 10.4 Release Notes
54
No ICMP host redirect messages are generated when there are multiple VLANs
configured on an interface (multiple logical interfaces on a single physical interface).
[PR/559317]
When the same local link address is configured on two interfaces, the message "/kernel:
ip6_getpmtu: Invalid Stored MTU" is displayed continuously. [PR/560079]
Routing Protocols
When aggregate interfaces are used for VPN applications, load balancing may not
occur with a Layer 2 circuit configuration. [PR/471935]
Under certain circumstances, the BGP path selection does not follow the local
preference. This might lead to incorrect BGP path selections. [PR/513233]
When the received next hop for a route has the same address of the EBGP peer to
which the route is readvertised, the next hop is erroneously set to the peer's address
instead of the next hop to self. [PR/533647]
When an interface is added to a routing instance with rpf-check enabled, the routing
protocol process might crash if a route-distinguisher is also changed at the same time.
[PR/539321]
In Junos OS Release 10.0 and later, a direct route to a VRF with a rib-group is not
advertised as an inet-vpn route to the IBGP neighbor due to the error "BGP label
allocation failure: Need a nexthop address on LAN." [PR/552377]
In some cases, the MX Series routers might not send the Link Layer Discovery Protocol
(LLDP) notification trap when the LLDP is disabled on the remote neighbor.
[PR/560855]
Once a routing protocol process is restarted due to a crash or a mastership switch, the
kernel and the routing protocol process flood branch nh reference counters might not
be in sync anymore. The exposure is high in NGEN-MVPN with many local receivers
and constant churn of join and prunes of multicast groups. The routing protocol process
might assert and restart while deleting a flooded nexthop. As a workaround, restart
the system, or deactivate all MVPN instances to get the kernel and the routing protocol
process to be in sync upon a routing protocol process restart. [PR/561127]
The 3D Packet Forwarding Engines might experience a rare transient error that
temporarily corrupts one of the lookup engines, resulting in packet loss. A set of
messages similar to the following is displayed:
fpc0 LU 0 PPE_7 Errors ucode data error 0x00000184
fpc0 PPE Thread Timeout Trap:
entry_index_nh
Count 10831395, PC 2c, 0x002c:
Reboot the Packet Forwarding Engine to clear this error state. [PR/564998]
The configuration of DSCP ReWrite rules on a 10-port 10-Gigabit Ethernet LAN/WAN
PIC with SFP+ might overwrite the DSCP value coming from the Routing Engine for a
host generated traffic. [PR/575259]
When a core-facing DPC is restarted, the message "mcsn: cannot perform nh operation
ADDANDGET nhop (null) type indirect index 0 errno 22" appears. A trigger also moves
Count 3, PC 20, 0x0020:
0x0020:
entry_index_nh PPE PPE HW Fault Trap:
entry_policer_nh
Copyright © 2011, Juniper Networks, Inc.
Advertisement
Table of Contents
