Configuring Peer Resynchronization For L2Tp Host Profiles And Aaa Domain; Map Tunnels - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12 Configuration Manual

Software for e series broadband services routers broadband access configuration guide
Hide thumbs Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - BROADBAND ACCESS CONFIGURATION GUIDE 2010-10-12:
Table of Contents

Advertisement

Configuring Peer Resynchronization for L2TP Host Profiles and AAA Domain Map Tunnels
Copyright © 2010, Juniper Networks, Inc.
The following list highlights differences between the failover protocol and silent failover
peer resynchronization methods:
With the L2TP failover protocol method, both endpoints must support the method or
recovery always fails. The L2TP failover protocol method also requires a non-failed
endpoint to wait an additional recovery time period while the failed endpoint is
recovering to prevent the non-failed endpoint from prematurely disconnecting the
tunnel. The additional recovery period makes L2TP less responsive to the loss of tunnel
connectivity.
Silent failover operates entirely within the failed endpoint and does not require
non-failed endpoint support—this improves interoperability between peers. Silent
failover does not require additional recovery time by the non-failed endpoint, which
also eliminates the potential for degraded responsiveness to the loss of tunnel
connectivity.
NOTE: L2TP silent failover is not supported on E3 ATM and CT1 line modules
in peer-facing configurations.
You can use the CLI or RADIUS to configure the resynchronization method for your router.
1.
Configuring Peer Resynchronization for L2TP Host Profiles and AAA Domain Map
Tunnels on page 389
2.
Configuring the Global L2TP Peer Resynchronization Method on page 390
Using RADIUS to Configure Peer Resynchronization on page 391
3.
The JunosE CLI enables you to configure the peer resynchronization method globally, for
a host profile, or for a domain map tunnel. A host profile or domain map tunnel
configuration takes precedence over the global peer resynchronization configuration.
When you change the peer resynchronization method, the change is not immediately
applied to existing tunnels. Tunnels continue using their current resynchronization method
until the next time the tunnel is reestablished.
Use the failover-resync command to configure the L2TP peer resynchronization method
for L2TP host profiles and AAA domain map tunnels. This command takes precedence
over the global peer resynchronization configuration.
Choose one of the following keywords to specify the peer resynchronization method:
failover-protocol—The tunnel uses the L2TP failover protocol method. If the peer
non-failed endpoint does not support the L2TP failover protocol, a failover forces
disconnection of the tunnel and all of its sessions.
failover-protocol-fallback-to-silent-failover—The tunnel uses the L2TP failover
protocol method; however, if the peer non-failed endpoint does not support the L2TP
failover protocol method, the tunnel falls back to using the silent failover method.
Chapter 13: Configuring an L2TP LNS
389

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents