(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 360.
■
To specify a destruct timeout:
host1(config)#
l2tp destruct-timeout 1200
Related Topics
■
l2tp destruct-timeout
Preventing Creation of New Destinations, Tunnels, and Sessions
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:
1.
Preventing Creation of New Destinations, Tunnels, and Sessions on the
Router on page 340
2.
Preventing Creation of New Tunnels and Sessions at a Destination on page 341
3.
Preventing Creation of New Sessions for a Tunnel on page 341
4.
Specifying a Drain Timeout for a Disconnected Tunnel on page 341
Preventing Creation of New Destinations, Tunnels, and Sessions on the Router
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.
■
To prevent the creation of new destinations, tunnels, and sessions:
340
■
Preventing Creation of New Destinations, Tunnels, and Sessions
JUNOSe 11.0.x Broadband Access Configuration Guide
Summary of Contents for JUNOSE 11.0.X MULTICAST ROUTING
Page 6: ...vi...
Page 28: ...xxviii Table of Contents JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 36: ...xxxvi List of Tables JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 42: ...2 Managing Remote Access JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 204: ...164 Managing RADIUS and TACACS JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 292: ...252 Monitoring RADIUS Relay Server JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 336: ...296 RADIUS Client Terminate Reasons JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 368: ...328 Managing L2TP JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 444: ...404 PPP Accounting Statistics JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 494: ...454 Managing DHCP JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 510: ...470 DHCP Local Server Configuration Tasks JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 556: ...516 Configuring DHCP Relay Proxy JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 616: ...576 Managing the Subscriber Environment JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 674: ...634 Managing Subscriber Services JUNOSe 11 0 x Broadband Access Configuration Guide...
Page 767: ...Part 7 Index Index on page 729 Index 727...
Page 768: ...728 Index JUNOSe 11 0 x Broadband Access Configuration Guide...