close
keyboard_arrow_left
Table of Contents
- play_arrow Configuring Dynamic VLANs for Subscriber Access Networks
- play_arrow Dynamic VLAN Overview
- Subscriber Management VLAN Architecture Overview
- Dynamic 802.1Q VLAN Overview
- Static Subscriber Interfaces and VLAN Overview
- Pseudowire Termination: Explicit Notifications for Pseudowire Down Status
- Configuring an Access Pseudowire That Terminates into VRF on the Service Node
- Configuring an Access Pseudowire That Terminates into a VPLS Routing Instance
- play_arrow Configuring Dynamic Profiles and Interfaces Used to Create Dynamic VLANs
- Configuring a Dynamic Profile Used to Create Single-Tag VLANs
- Configuring an Interface to Use the Dynamic Profile Configured to Create Single-Tag VLANs
- Configuring a Dynamic Profile Used to Create Stacked VLANs
- Configuring an Interface to Use the Dynamic Profile Configured to Create Stacked VLANs
- Configuring Interfaces to Support Both Single and Stacked VLANs
- Overriding the Dynamic Profile Used for an Individual VLAN
- Configuring a VLAN Dynamic Profile That Associates VLANs with Separate Routing Instances
- Automatically Removing VLANs with No Subscribers
- Verifying and Managing Dynamic VLAN Configuration
- play_arrow Configuring Subscriber Authentication for Dynamic VLANs
- Configuring an Authentication Password for VLAN or Stacked VLAN Ranges
- Configuring Dynamic Authentication for VLAN Interfaces
- Subscriber Packet Type Authentication Triggers for Dynamic VLANs
- Configuring Subscriber Packet Types to Trigger VLAN Authentication
- Configuring VLAN Interface Username Information for AAA Authentication
- Using DHCP Option 82 Suboptions in Authentication Usernames for Autosense VLANs
- Using DHCP Option 18 and Option 37 in Authentication Usernames for DHCPv6 Autosense VLANs
- play_arrow Configuring VLANs for Households or Individual Subscribers Using ACI-Based Dynamic VLANs
- Agent Circuit Identifier-Based Dynamic VLANs Overview
- Configuring Dynamic VLANs Based on Agent Circuit Identifier Information
- Defining ACI Interface Sets
- Configuring Dynamic Underlying VLAN Interfaces to Use Agent Circuit Identifier Information
- Configuring Static Underlying VLAN Interfaces to Use Agent Circuit Identifier Information
- Configuring Dynamic VLAN Subscriber Interfaces Based on Agent Circuit Identifier Information
- Verifying and Managing Agent Circuit Identifier-Based Dynamic VLAN Configuration
- Clearing Agent Circuit Identifier Interface Sets
- play_arrow Configuring VLANs for Households or Individual Subscribers Using Access-Line-Identifier Dynamic VLANs
- Access-Line-Identifier-Based Dynamic VLANs Overview
- Configuring Dynamic VLANs Based on Access-Line Identifiers
- Defining Access-Line-Identifier Interface Sets
- Configuring Dynamic Underlying VLAN Interfaces to Use Access-Line Identifiers
- Configuring Static Underlying VLAN Interfaces to Use Access-Line Identifiers
- Configuring Dynamic VLAN Subscriber Interfaces Based on Access-Line Identifiers
- Verifying and Managing Configurations for Dynamic VLANs Based on Access-Line Identifiers
- Clearing Access-Line-Identifier Interface Sets
- play_arrow High Availability for Service VLANs
-
- play_arrow Configuring DHCP Subscriber Interfaces
- play_arrow VLAN and Demux Subscriber Interfaces Overview
- play_arrow Configuring Sets of Demux Interfaces to Provide Services to a Group of Subscribers
- play_arrow Configuring Dynamic Demux Interfaces That are Created by DHCP
- play_arrow Configuring DHCP Subscriber Interfaces over Aggregated Ethernet
- Static and Dynamic VLAN Subscriber Interfaces over Aggregated Ethernet Overview
- Static or Dynamic Demux Subscriber Interfaces over Aggregated Ethernet Overview
- Configuring a Static or Dynamic VLAN Subscriber Interface over Aggregated Ethernet
- Configuring a Static or Dynamic IP Demux Subscriber Interface over Aggregated Ethernet
- Configuring a Static or Dynamic VLAN Demux Subscriber Interface over Aggregated Ethernet
- Example: Configuring a Static Subscriber Interface on a VLAN Interface over Aggregated Ethernet
- Example: Configuring a Static Subscriber Interface on an IP Demux Interface over Aggregated Ethernet
- Example: Configuring IPv4 Static VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server
- Example: Configuring IPv4 Dynamic VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server
- Example: Configuring IPv6 Dynamic VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server
- Example: Configuring IPv4 Dynamic Stacked VLAN Demux Interfaces over an Aggregated Ethernet Underlying Interface with DHCP Local Server
- play_arrow Using Dynamic Profiles to Apply Services to DHCP Subscriber Interfaces
- play_arrow Configuring DHCP IP Demux and PPPoE Demux Interfaces Over the Same VLAN
- play_arrow Providing Security for DHCP Interfaces Using MAC Address Validation
- play_arrow RADIUS-Sourced Weights for Targeted Distribution
- play_arrow Verifying Configuration and Status of Dynamic Subscribers
-
- play_arrow Configuring PPPoE Subscriber Interfaces
- play_arrow Configuring Dynamic PPPoE Subscriber Interfaces
- Subscriber Interfaces and PPPoE Overview
- Dynamic PPPoE Subscriber Interfaces over Static Underlying Interfaces Overview
- Configuring Dynamic PPPoE Subscriber Interfaces
- Configuring a PPPoE Dynamic Profile
- Configuring an Underlying Interface for Dynamic PPPoE Subscriber Interfaces
- Configuring the PPPoE Family for an Underlying Interface
- Ignoring DSL Forum VSAs from Directly Connected Devices
- Example: Configuring a Dynamic PPPoE Subscriber Interface on a Static Gigabit Ethernet VLAN Interface
- play_arrow Configuring PPPoE Subscriber Interfaces over Aggregated Ethernet Examples
- Example: Configuring a Static PPPoE Subscriber Interface on a Static Underlying VLAN Demux Interface over Aggregated Ethernet
- Example: Configuring a Dynamic PPPoE Subscriber Interface on a Static Underlying VLAN Demux Interface over Aggregated Ethernet
- Example: Configuring a Dynamic PPPoE Subscriber Interface on a Dynamic Underlying VLAN Demux Interface over Aggregated Ethernet
- play_arrow Configuring PPPoE Session Limits
- play_arrow Configuring PPPoE Subscriber Session Lockout
- play_arrow Configuring MTU and MRU for PPP Subscribers
- play_arrow Configuring PPPoE Service Name Tables
- Understanding PPPoE Service Name Tables
- Evaluation Order for Matching Client Information in PPPoE Service Name Tables
- Benefits of Configuring PPPoE Service Name Tables
- Creating a Service Name Table
- Configuring PPPoE Service Name Tables
- Assigning a Service Name Table to a PPPoE Underlying Interface
- Configuring the Action Taken When the Client Request Includes an Empty Service Name Tag
- Configuring the Action Taken for the Any Service
- Assigning a Service to a Service Name Table and Configuring the Action Taken When the Client Request Includes a Non-zero Service Name Tag
- Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information
- Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for Dynamic PPPoE Interface Creation
- Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
- Reserving a Static PPPoE Interface for Exclusive Use by a PPPoE Client
- Example: Configuring a PPPoE Service Name Table
- Example: Configuring a PPPoE Service Name Table for Dynamic Subscriber Interface Creation
- Troubleshooting PPPoE Service Name Tables
- play_arrow Changing the Behavior of PPPoE Control Packets
- play_arrow Monitoring and Managing Dynamic PPPoE for Subscriber Access
-
- play_arrow Configuring ATM for Subscriber Access
- play_arrow Configuring ATM to Deliver Subscriber-Based Services
- play_arrow Configuring PPPoE Subscriber Interfaces Over ATM
- play_arrow Configuring ATM Virtual Path Shaping on ATM MICs with SFP
- play_arrow Configuring Static Subscriber Interfaces over ATM
- play_arrow Verifying and Managing ATM Configurations
-
- play_arrow Troubleshooting
- play_arrow Contacting Juniper Networks Technical Support
- play_arrow Knowledge Base
-
- play_arrow Configuration Statements and Operational Commands
list Table of Contents
Configuring L2TP Client Access to Support MLPPP for Static Subscribers
date_range
06-Dec-23
To enable MLPPP over LT2P network server (LNS) support for MX Series, you must indicate whether MLPPP is supported for static subscribers from a particular L2TP client (LAC) by configuring the multilink statement currently supported in access profile. Access profiles define how to validate Layer 2 Tunneling Protocol (L2TP) connections and session requests. Within each L2TP access profile, you configure one or more clients (LACs). You can configure multiple access profiles and multiple clients within each profile.
With mixed mode support, the multilink statement enables MLPPP but does not set it. However, if you do not configure the multilink statement, MLPPP is not supported for static LAC subscribers.
The following two examples show L2TP access profile configurations for an MLPPP-capable static L2TP client and non-multilink (single link) static L2TP client.
To configure an L2TP access profile for MLPPP-capable static L2TP clients:
MLPPP is first negotiated with static subscribers coming from the LAC peer group profile, ce-lac-1-gp, but then switches to PPP if the subscriber rejects MLPPP. The following shows sample output for MLPPP-capable static L2TP client:
content_copy zoom_out_map
access profile {
ce-l2tp-profile1 {
client ce-lac-1 {
user-group-profile ce-lac-1-gp;
l2tp {
interface-id not-used;
lcp-renegotiation;
maximum-sessions-per-tunnel 2000;
shared-secret "$9$2wgUHQF/9pB";
aaa-access-profile ce-aaa-profile;
multilink;
}
}
}
}To configure an L2TP access profile for non-MLPPP, or single link static L2TP clients, repeat Step 1 through Step 7 for configuring an L2TP access profile for multilink-capable static L2TP clients. Do not set l2tp multilink.
Only PPP is negotiated with static subscribers from the LAC peer group profile, ce-lac-2-gp, and an LCP configuration request from the customer premises equipment (CPE) with maximum received reconstructed unit (MRRU) option is rejected. The following shows sample output for single link static L2TP client:
content_copy zoom_out_map
access profile {
ce-l2tp-profile1 {
client ce-lac-2 {
user-group-profile ce-lac-1-gp;
l2tp {
interface-id not-used;
maximum-sessions-per-tunnel 1000;
shared-secret "$9$2aBcXyz/2lP";
aaa-access-profile ce-aaa-profile;
## multilink not entered, static subscriber is single link only
}
}
}
}