JunosE 11.3.x Broadband Access Configuration Guide
Specifying a Destruct Timeout for L2TP Tunnels and Sessions
Related
Documentation
Preventing Creation of New Destinations, Tunnels, and Sessions
Preventing Creation of New Destinations, Tunnels, and Sessions on the Router
346
You can specify the maximum time period, in the range 10–3600 seconds
(1 hour), for which the router attempts to maintain dynamic destinations, tunnels, and
sessions after they have been destroyed. The router uses a timeout of 600 seconds by
default.
This command facilitates debugging and other analysis by saving underlying memory
structures after the destination, tunnel, or session is terminated.
Any specific dynamic destination, tunnel, or session may not be maintained for this entire
time period if the resources must be reclaimed early to allow new tunnels to be
established.
TIP: If you use the l2tp destination lockout timeout command to configure
an optional lockout timeout, always configure the destruct timeout to be
longer than the lockout timeout. The destruct timeout overrides the lockout
timeout—when the destruct timeout expires, all information about the locked
out destination is deleted, including the lockout timeout and lockout test
settings. See "Managing the L2TP Destination Lockout Process" on page 365.
To specify a destruct timeout:
host1(config)#l2tp destruct-timeout 1200
l2tp destruct-timeout
You can configure several L2TP drain operations, which determine how the router creates
new L2TP destinations, tunnels, and sessions. You can manage the following features:
Preventing Creation of New Destinations, Tunnels, and Sessions on the
1.
Router on page 346
Preventing Creation of New Tunnels and Sessions at a Destination on page 347
2.
Preventing Creation of New Sessions for a Tunnel on page 347
3.
4.
Specifying a Drain Timeout for a Disconnected Tunnel on page 347
You use the l2tp drain command to prevent the creation of new destinations, tunnels,
and sessions on the router.
The l2tp drain command and the l2tp shutdown command both affect the administrative
state of L2TP on the router. Although each command has a different effect, the no version
of each command is equivalent. Each command's no version leaves L2TP in the enabled
state.
Copyright © 2010, Juniper Networks, Inc.