Known Behavior
25
Release 10.3.2
L2TP
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]
Line Module Redundancy
On E120 routers and E320 routers, redundant IOAs have a temperature sensor,
and the
show environment all
command lists the temperature of IOAs in their
associated slots.
On ERX routers, redundant I/O modules do not have a temperature sensor.
Therefore, the
show environment all
command output lists the primary I/O
module temperature in the slot of the line module that is responsible for the I/O
module.
