Juniper JUNOS OS 10.4 - RELEASE NOTES Release Note page 52

JUNOS OS 10.4 Release Notes
52
ABTX-2 lcc2-master /kernel: if_pfe: Error 4 (Exists Already) on IF command
23 (IFL add)
LABTX-2 lcc2-master /kernel: if_pfe: Error 9 (No IFL) on IF command 34
(IFL config encap)
LABTX-2 lcc2-master /kernel: if_pfe: Error 9 (No IFL) on IF command 33
(IFL config flags)
LABTX-2 lcc2-master /kernel: if_pfe: Error 9 (No IFL) on IF command 201
(Unknown)
LABTX-2 lcc2-master /kernel: if_pfe: Error 5 (Invalid) on IF command 87
(Ae add IFL)
LABTX-2 lcc2-master lcc2-fpc0 IF: ifl_add() duplicate subunit 0 (ifd 243)
LABTX-2 lcc2-master lcc2-fpc0 NH(nh_ucast_l2rw_add): Invalid ifl index
125
LABTX-2 lcc1-master lcc1-fpc3 NH: Null ifl (87)
When these messages are displayed, the state of the Packet Forwarding Engine can
be corrupted and might cause the FPCs to crash at a later time. Hence, it is
recommended that upon encountering these error messages, reboot the router or
reboot the FPCs under a maintenance window.
As a workaround, split the operation into two commits, that is, remove the interface
from one bundle and perform a commit, and then add it to another bundle and perform
a commit. [PR/565658]
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 instances with scaled LACP configurations, the periodic packet management process
(ppmd) might experience memory leaks. [PR/547484]
When a policy matching an extended community using a 4-byte AS and a wildcard is
configured, the match condition might fail to match the relevant communities. As a
workaround, configure exact matches. [PR/550539]
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]
On an NSR LDP, an LDP database entry mismatch exists between the master and the
backup Routing Engines. The backup Routing Engine does not replicate the LDP socket
with the error "jsr_sdrl_set_data: No space dlen." [PR/552945]
When a default route target is sent by a BGP peer, th eBGP does not track the VPN
routes covered by this route target. When the default route target goes away, the BGP
Copyright © 2010, Juniper Networks, Inc.