Managing The L2Tp Destination Lockout Process; Modifying The Lockout Procedure - Juniper JUNOSE SOFTWARE 11.0.X - BROADBAND ACCESS CONFIGURATION GUIDE 4-1-2010 Configuration Manual

JUNOSe 11.0.x Broadband Access Configuration Guide
2.
Related Topics

Managing the L2TP Destination Lockout Process

When multiple sets of tunneling parameters are available, L2TP uses a selection
algorithm to choose the best tunnel for subscriber traffic. As part of this selection
process, the JUNOSe software's L2TP implementation includes a lockout feature in
which the router locks out, or disregards, destinations that are assumed to be
unavailable.
By default, when a destination becomes unavailable, L2TP locks out that destination
for a lockout timeout of 300 seconds (5 minutes). After the lockout timeout expires,
L2TP assumes that the destination is now available and includes the destination
when performing the selection algorithm.
Tasks to manage the L2TP lockout process include:
1. Modifying the Lockout Procedure on page 360
2. Verifying That a Locked-Out Destination Is Available on page 362
3. Configuring a Lockout Timeout on page 362
4. Unlocking a Destination that is Currently Locked Out on page 362
5. Starting an Immediate Lockout Test on page 363

Modifying the Lockout Procedure

You can optionally configure your own lockout procedure by specifying the lockout
timeout you want to use or enabling a lockout test, or both. When the lockout timeout
expires, the destination is either immediately unlocked (if lockout testing is not
enabled) or begins the lockout test to verify that the destination is available.
L2TP performs the lockout test by attempting to establish a tunnel to the unavailable
destination. For the test, L2TP must first obtain the parameters for a tunnel to the
destination. If no such tunnel currently exists, L2TP must wait until it receives a new
session request that has tunnel parameters for the locked out destination. The
destination remains locked out while L2TP waits for the tunnel parameters and
becomes available only after successful completion of the lockout test. Therefore, if
lockout testing is enabled, the destination is actually locked out longer than the
lockout timer you specify.
360
Managing the L2TP Destination Lockout Process
Specify that the RX Speed AVP is always generated. If you do not specify this
command, the RX Speed AVP is generated only when the RX speed differs from
the TX speed.
host1(config)#l2tp rx-connect-speed-when-equal
atm atm1483 advisory-rx-speed
l2tp rx-connect-speed-when-equal command