Technical Documentation

Technical Documentation

Content Explorer ^New

Enterprise MIBs

EOL Documentation

Feature Explorer

File Format Help

Portable Libraries

L2TP LAC on E Series Broadband Services Routers, Release 13.2

An L2TP access concentrator (LAC) receives packets from a remote client and forwards them to an L2TP network server (LNS), on a remote network. You can configure your E Series router to function as an LAC. This page provides information that describes how you can configure E Series routers to operate as a LAC device.

JunosE Software Documentation for E Series Broadband Services Routers, Release 13.2

Overview
Configuration
Administration
Troubleshooting

L2TP Functionalities

L2TP Terminology

Packet Fragmentation

L2TP Deployment
Implementing L2TP

L2TP Platform and Module Requirements

L2TP Module Requirements

L2TP Platform Considerations

L2TP References

L2TP Sessions and Tunnels

Sessions and Tunnels Supported

Stateful Line Module Switchover Platform Considerations

Methods of Mapping a User Domain to an L2TP Tunnel
Mapping a User Domain Name to an L2TP Tunnel Overview

Termination of PPP and L2TP Subscriber Sessions

VSAs for Dynamic IP Interfaces Overview

Overview of Mapping Application Terminate Reasons and RADIUS Terminate Codes

How L2TP Dial-Out Works

L2TP Dial-Out Overview

L2TP Dial-Out Platform Considerations

L2TP Dial-Out References

L2TP Dial-Out Network Model

L2TP Dial-Out Process

L2TP Dial-Out Operational States

L2TP Dial-Out Outgoing Call Setup Details

Configuring Settings for L2TP Destinations, Tunnels, and Sessions

Modifying L2TP LAC Default Settings for Managing Destinations, Tunnels, and Sessions

Generating UDP Checksums in Packets to L2TP Peers

Specifying a Destruct Timeout for L2TP Tunnels and Sessions

Preventing Creation of New Destinations, Tunnels, and Sessions

Shutting Down Destinations, Tunnels, and Sessions

Specifying the Number of Retransmission Attempts

Configuring an L2TP LAC

LAC Configuration Prerequisites

Mapping User Domain Names to L2TP Tunnels from Domain Map Tunnel Mode

Mapping User Domain Names to L2TP Tunnels from Tunnel Group Tunnel Mode

Mechanisms for Selecting Tunnels for PPP User Sessions
Configuring LAC Tunnel Selection Parameters

L2TP Destination Lockout Feature

Managing Address Changes Received from Remote Endpoints

Configuring LAC Tunnel Selection Parameters

Generating RX Speed Attribute Value Pair (AVP) on the LAC
Configuring the RX Speed on the LAC

Calling Number AVP in ICRQ Packets
Configuring Calling Number AVP Formats

Configuration Commands

aaa tunnel calling-number-format-fallback

aaa tunnel assignment-id-format

aaa tunnel client-name

aaa tunnel ignore

aaa tunnel password

aaa tunnel calling-number-format

bundled-group-id

bundled-group-id-overrides-mlppp-ed

default-upper-type mlppp

disable proxy lcp

enable proxy authenticate

l2tp destruct-timeout

l2tp destination profile

l2tp disable calling-number-avp

l2tp disable challenge

l2tp drain destination

l2tp drain tunnel

l2tp ignore-receive-data-sequencing

l2tp retransmission

l2tp shutdown destination

l2tp shutdown session

l2tp shutdown tunnel

l2tp tunnel short-drain-timeout

local ip address

radius remote-circuit-id-delimiter

radius remote-circuit-id-format

radius override calling-station-id remote-circuit-id

radius connect-info-format

radius calling-station-format

session-out-of-resource-result-code-override

tunnel password

Verifying Domain Maps and L2TP Tunnels with AAA

Monitoring the Mapping for User Domains and Virtual Routers with AAA

Monitoring Configuration of Tunnel Parameters with AAA

Monitoring Configured Tunnel Groups with AAA

Verifying the L2TP Tunnel Aggregated Settings
Monitoring Global Configuration Status on E Series Routers

Monitoring L2TP Destination Settings

Monitoring Detailed Configuration Information for Specified Destinations

Monitoring Configured and Operational Status of all Destinations

Monitoring Locked Out Destinations

Monitoring Configured Destination Profiles or Host Profiles

Viewing the Disconnect Cause-Codes for PPP Sessions
Monitoring Statistics on the Cause of a Session Disconnection

Viewing the Configured L2TP Session Details

Monitoring Detailed Configuration Information about Specified Sessions

Monitoring Configured and Operational Summary Status

Viewing L2TP Switch-Profiles
Monitoring Configured Switch Profiles on Router

Monitoring L2TP Tunnel Settings

Monitoring Detailed Configuration Information about Specified Tunnels

Monitoring Configured and Operational Status of All Tunnels

Monitoring L2TP Dial-Out Settings

Monitoring Chassis-wide Configuration for L2TP Dial-out

Monitoring Dial-out Targets within the Current VR Context

Monitoring Operational Status within the Current VR Context

Monitoring Status of Dial-out Sessions

Monitoring Commands

show aaa domain-map

show aaa tunnel-group

show aaa tunnel-parameters

show l2tp destination

show l2tp destination lockout

show l2tp destination profile

show l2tp received-disconnect-cause-summary

show l2tp dial-out

show l2tp dial-out session

show l2tp dial-out target

show l2tp dial-out virtual-router

show l2tp session

show l2tp switch-profile

show l2tp tunnel

Knowledge Base

L2TP LAC sessions stuck in "down" state.

L2TP LAC doesn't strip ENET Padding on Packets from Client

ERX L2TP LAC not accepting PPP data before tunnel ZLB ACK

L2TP LAC to LNS failover timing when using "l2tp retransmissions" parameter

ERX L2TP LAC does Not Strip ENET Pads from Packets from Client

How does an L2TP LAC report the ATM subinterface speed to an LNS?

L2TP LAC receiving accounting records for tunneled subscribers, even though tunnel-accounting is disabled

L2TP LAC. Sessions/tunnels to an LNS drop, when bouncing sessions tunneled to a second LNS

A malformed AVP can cause the ERX functioning as an L2TP LAC or LNS to reach 100% CPU utilization.

Sample L2TP Configuration with a Cisco LAC and an ERX LNS

Line Card Reset: type: unknown software error signature (0x1174094), file: ic1detector.cc, line: 717, message: ic1detector::requestRecovery executed forced IC crash last errno: 0x110001, after bouncing PPPoE client interface on L2TP LAC

erx1440 LAC unable to process more than 16K L2TP sessions when configured for larger B-RAS license

How can I predict L2TP Session IDs on the ERX LAC or LNS?

Receive Window Size of 64 on an ERX LNS is too large when the LAC is a Redback using a Receive Window Size of 10 resulting in failed L2TP sessions.

L2TP sessions fail on a LAC running an ISSU-capable release, with an uptime > 366 days

L2TP sessions from an e320 acting as a LAC fail to establish over a lm10 via a MPLS next-hop

ERX operating as an L2TP LNS will not negotiate multilink PPP with tunneled clients unless the LAC supplies proxy LCP information when establishing the tunnel.

L2TP sessions are not coming up to an e320 LAC over an lm10

ERX LAC sends L2TP ICCN packet that is rejected by LNS

ERX LAC L2TP Tunnel To Lucent LNS Fails

L2TP session at LAC not creating traffic-class queues

QoS Profile attachment through CoA (Service Manager) is not getting attached properly on L2TP-Session on LAC.

Downloads

Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices

Copyright© 1999-2012 Juniper Networks, Inc. All rights reserved.

|

|