Table of Contents
Advertisement
JunosE 11.3.0 Release Notes
L2TP
28
Known Behavior
The long duration for restart of a previously running application on the router also
occurs if you configured OSPF on the router and perform a stateful SRP switchover
process. This condition can occur even in environments that are not scaled to the
maximum limits and contain minimal subscriber connections or attribute definitions.
Because the IP application takes about 30-35 seconds to reinitialize and process
control packets after a stateful SRP switchover, and the continual increase in the
time needed for completion of IP reinitialization in JunosE releases (owing to
consumption of system resources for enhanced functionalities), we recommend that
you increase the hold timers for the associated protocols running on the router to
necessary levels so that graceful restart can function properly.
L2TP peer resynchronization enables an L2TP failed endpoint to resynchronize with
its peer non-failed endpoint. The JunosE Software supports failover protocol and
silent failover peer resynchronization methods. If you configure the silent failover
method, you must keep the following considerations in mind:
PPP keepalives—To ensure resynchronization of the session database, PPP
keepalives must be enabled on the L2TP data path. Without PPP keepalives,
silent failover might disconnect an established session if there is no user traffic
during failover recovery.
Asymmetric routes on different line modules—Asymmetric routes whose receive
and transmit paths use I/O paths on different line modules can result in
improperly handled line module control packets. If your network does include
this type of asymmetric route, tunnels using these routes might fail to recover
properly.
NAT dynamic translation generation affects the LNS session creation time. When
NAT dynamic translations and LNS sessions are created simultaneously, NAT
dominates the CPU cycles of the tunnel-service module, resulting in a delay in the
LNS session creation rate. The LNS session creation rate returns to its normal rate
when NAT dynamic translations are no longer being generated. [Defect ID 53191]
Work-around: When signaling performance must be optimal, avoid the
simultaneous configuration of NAT and LNS.
If you create an L2TP destination profile profileName, establish tunnels with the
profile, and then remove the profile, you cannot subsequently create another
destination profile using that same profileName until all the tunnels drain from the
previous instance of this destination profile. If you do not wait, the E Series router
displays a message similar to the following:
l2tp: Discarding incoming sccrq from vr default, remote address 192.168.100.1 - no destination
profile.
If you do not want to wait for the tunnels to drain, use a different name for the
destination profile. [Defect ID 32973]
Copyright © 2010, Juniper Networks, Inc.
Advertisement
Table of Contents
