Known Behavior
25
Release 11.0.2
The enhancement to the CLI to support unnumbered reference to any kind of
interface rather than just loopback interfaces has consequences such as the
following: [Defect ID 47743]
If the references to shared interfaces appear in the
show configuration
output before the configuration for the interfaces they refer to, trying to
restore such a configuration with a script generated from
show
configuration
generates errors like the following:
% Error, line 3929:
host1(config-if)#ip share-interface FastEthernet 3/0.2
% No such interface
Unnumbered interfaces that refer to nonloopback interfaces (for example,
ip unnumbered fastEthernet 3/0.2
) and that appear in the
show
configuration
output before the interface referred to might generate
similar no such interface errors.
Work-around:
Run the script twice.
IP interface statistics become inconsistent when a slot is reset, because some
traffic (such as control traffic) might be destined for the SRP module and is
therefore counted elsewhere. [Defect ID 26697]
IPSec
When you shut down the only outgoing IP interface to the IP destinations of
IPSec tunnels, the tunnels remain in the up state rather than transitioning to
down. As a consequence, all IP routes that use these tunnels as next hops also
remain in the routing table. You can use dead keepalive detection (DPD) to
avoid this situation. DPD must be active, which requires both IPSec tunnel
endpoints to support DPD.
During a warm restart after a system failover, the SRP module can take several
minutes to resume the normal exchange of UDP/IP packets to applications.
During this restart time, the E Series router does not send or receive dead peer
detection (DPD) keepalives, which are used to verify connectivity between the
router and its peers. The length of the restart time depends on the number of
interfaces—if the restart time is too long, remote peers might determine that
the connection from them to the E Series router is broken and then shut down
an IPSec tunnel that has DPD enabled. In the worst case, all IPSec tunnels
might be shut down. [Defect ID 65132]
When the LAC–to–LNS data path runs over an MPLS tunnel and the MPLS
tunnel originates or terminates at the LAC on an ES2 10G LM or an ES2 10G
Uplink LM, the L2TP data traffic that originated or terminated at the LAC is
discarded. [Defect ID 87260]
