- 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 MLPPP for Subscriber Access
- play_arrow MLPPP Support for LNS and PPPoE Subscribers Overview
- MLPPP Overview
- MLPPP Support for LNS and PPPoE Subscribers Overview
- Supported Features for MLPPP LNS and PPPoE Subscribers on the MX Series
- Mixed Mode Support for MLPPP and PPP Subscribers Overview
- Understanding DVLAN (Single/Dual tag) for Subscriber Services Scaling (Junos Evolved for ACX7100-48L Devices)
- play_arrow Configuring MLPPP Link Fragmentation and Interleaving
- play_arrow Configuring Inline Service Interfaces for LNS and PPPoE Subscribers
- play_arrow Configuring L2TP Access Client for MLPPP Subscribers
- play_arrow Configuring Static MLPPP Subscribers for MX Series
- play_arrow Configuring Dynamic MLPPP Subscribers for MX Series
- play_arrow Configuring Dynamic PPP Subscriber Services
- Dynamic PPP Subscriber Services for Static MLPPP Interfaces Overview
- Hardware Requirements for PPP Subscriber Services on Non-Ethernet Interfaces
- Configuring PPP Subscriber Services for MLPPP Bundles
- Enabling PPP Subscriber Services for Static Non-Ethernet Interfaces
- Attaching Dynamic Profiles to MLPPP Bundles
- Example: Minimum MLPPP Dynamic Profile
- Example: Configuring CoS on Static LSQ MLPPP Bundle Interfaces
- play_arrow Monitoring and Managing MLPPP 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
ON THIS PAGE
Example: Configuring a Static PPPoE Subscriber Interface on a Static Underlying VLAN Demux Interface over Aggregated Ethernet
This example shows how you can configure static PPPoE subscriber interfaces over aggregated Ethernet bundles to provide subscriber link redundancy.
Requirements
PPPoE over VLAN demux interfaces over aggregated Ethernet requires the following hardware and software:
MX Series 5G Universal Routing Platforms
MPCs
Junos OS Release 11.2 or later
No special configuration beyond device initialization is required before you can configure this feature.
Overview
Aggregated Ethernet bundles enable link redundancy between the router and networking devices connected by Ethernet links. This example describes how to configure link redundancy for static PPPoE subscribers over aggregated Ethernet interface with an intermediate static VLAN demux interface. Sample tasks include configuring a two-member aggregated Ethernet bundle on ae0, configuring a static VLAN demux interface, demux0.100, that underlies the PPPoE subscriber interface, pp0.100, and configuring the PPPoE subscriber interface including characteristics of the PPPoE family.
This example does not show all possible configuration choices.
Configuration
Procedure
CLI Quick Configuration
To quickly configure link redundancy for static PPPoE subscribers over a static VLAN demux interface over aggregated Ethernet, copy the following commands, paste them in a text file, remove any line breaks, and then copy and paste the commands into the CLI.
[edit] set chassis aggregated-devices ethernet device-count 1 set interfaces ge-5/0/3 gigether-options 802.3ad ae0 set interfaces ge-5/0/3 gigether-options 802.3ad primary set interfaces ge-5/1/2 gigether-options 802.3ad ae0 set interfaces ge-5/1/2 gigether-options 802.3ad backup set interfaces ae0 flexible-vlan-tagging set interfaces ae0 aggregated-ether-options link-protection edit interfaces demux0 unit 100 set vlan-id 100 set demux-options underlying-interface ae0 set family pppoe access-concentrator pppoe-server-1 set family pppoe duplicate-protection set family pppoe max-sessions 16000 top edit interfaces pp0 unit 100 set pppoe-options underlying-interface demux0.100 set pppoe-options server set family inet unnumbered-address lo0.0 top
Step-by-Step Procedure
The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.
To configure link redundancy for static PPPoE subscribers over a static VLAN demux interface over aggregated Ethernet:
Define the number of aggregated Ethernet devices on the router.
content_copy zoom_out_map[edit chassis] user@host# set aggregated-devices ethernet device-count 1
Configure a two-link aggregated Ethernet logical interface to serve as the underlying interface for the static VLAN demux subscriber interface. In this example, the LAG bundle is configured for one-to-one active/backup link redundancy. To support link redundancy at the MPC level, the LAG bundle attaches to ports from two different MPCs.
content_copy zoom_out_map[edit interfaces] user@host# set ge-5/0/3 gigether-options 802.3ad ae0 user@host# set ge-5/0/3 gigether-options 802.3ad primary user@host# set ge-5/1/2 gigether-options 802.3ad ae0 user@host# set ge-5/1/2 gigether-options 802.3ad backup
Enable link protection on the aggregated Ethernet logical interface and configure support for single and dual (stacked) VLAN tags.
content_copy zoom_out_map[edit interfaces] user@host# set ae0 aggregated-ether-options link-protection user@host# set ae0 flexible-vlan-tagging
Configure the VLAN demux interface over the aggregated Ethernet logical interface.
content_copy zoom_out_map[edit interfaces] user@host# set demux0 unit 100 vlan-id 100 user@host# set demux0 unit 100 demux-options underlying-interface ae0
Configure the PPPoE family attributes on the VLAN demux interface.
content_copy zoom_out_map[edit interfaces] user@host# set demxu0 unit 100 family pppoe access-concentrator pppoe-server-1 user@host# set demux0 unit 100 family pppoe duplicate-protection user@host# set demux0 unit 100 family pppoe max-sessions 16000
Configure the VLAN demux interface as the underlying interface on which the PPPoE logical interface is created.
content_copy zoom_out_map[edit interfaces] user@host# set pp0 unit 100 pppoe-options underlying-interface demux0.100 user@host# set pp0 unit 100 pppoe-options server user@host# set pp0 unit 100 family inet unnumbered-address lo0.0
Results
From configuration mode, confirm the aggregated device configuration by entering the show chassis command. Confirm the interface configuration by entering the show interfaces command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.
[edit]
user@host# show chassis
aggregated-devices {
ethernet {
device-count 1;
}
}
[edit]
user@host# show interfaces
ge-5/0/3 {
gigether-options {
802.3ad {
ae0;
primary;
}
}
}
ge-5/1/2 {
gigether-options {
802.3ad {
ae0;
backup;
}
}
}
ae0 {
flexible-vlan-tagging;
aggregated-ether-options {
link-protection;
}
}
demux0 {
unit 100 {
vlan-id 100;
demux-options {
underlying-interface ae0;
}
family pppoe {
access-concentrator pppoe-server-1;
duplicate-protection;
max-sessions 16000;
}
}
}
pp0 {
unit 100 {
pppoe-options {
underlying-interface demux0.100;
server;
}
family inet {
unnumbered-address lo0.0;
}
}
}
If you are done configuring the device, enter commit from configuration mode.
Verification
To confirm that the configuration is working properly, perform these tasks:
- Verifying the Aggregated Ethernet Interface Configuration
- Verifying the demux0 Interface Configuration
- Verifying the pp0 Interface Configuration
Verifying the Aggregated Ethernet Interface Configuration
Purpose
Verify that the interface values match your configuration, the link is up, and traffic is flowing.
Action
From operational mode, enter the show interfaces redundancy command.
user@host> show interfaces redundancy Interface State Last change Primary Secondary Current status ae0 On primary ge-5/0/3 ge-5/1/2 both up
From operational mode, enter the show interfaces ae0 command.
user@host> show interfaces ae0
Physical interface: ae0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 606
Link-level type: Ethernet, MTU: 1522, Speed: 1Gbps, BPDU Error: None,
MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled,
Flow control: Disabled, Minimum links needed: 1, Minimum bandwidth needed: 0
Device flags : Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Current address: 00:00:5e:00:53:d0, Hardware address: 00:00:5e:00:53:d0
Last flapped : 2011-03-11 13:24:18 PST (2d 03:34 ago)
Input rate : 1984 bps (2 pps)
Output rate : 0 bps (0 pps)
Logical interface ae0.32767 (Index 69) (SNMP ifIndex 709)
Flags: SNMP-Traps 0x4004000 VLAN-Tag [ 0x0000.0 ] Encapsulation: ENET2
Statistics Packets pps Bytes bps
Bundle:
Input : 371259 2 46036116 1984
Output: 0 0 0 0
Protocol multiservice, MTU: Unlimited
Flags: Is-PrimaryMeaning
The show interfaces redundancy output shows the redundant link configuration and that both link interfaces are up. The show interfaces ae0 output shows that the aggregated Ethernet interface is up and that traffic is being received on the logical interface.
Verifying the demux0 Interface Configuration
Purpose
Verify that the VLAN demux interface displays the configured PPPoE family attributes and the member links in the aggregated Ethernet bundle.
Action
From operational mode, enter the show interfaces demux0 command.
user@host> show interfaces demux0.100
Logical interface demux0.100 (Index 76) (SNMP ifIndex 61160)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.100 ]
Encapsulation: ENET2
Demux:
Underlying interface: ae0 (Index 199)
Link:
ge-5/0/3
ge-5/1/2
Input packets : 2
Output packets: 18575
Protocol pppoe
Dynamic Profile: none,
Service Name Table: None,
Max Sessions: 16000, Duplicate Protection: On,
AC Name: pppoe-server-1Alternatively, you can enter show pppoe underlying-interfaces detail to display the state and PPPoE family configuration for all configured underlying interfaces.
Meaning
The output shows the name of the underlying interface, the member links of the aggregated bundle, and the PPPoE family configuration. The output shows packet counts when traffic is present on the logical interface.
Verifying the pp0 Interface Configuration
Purpose
Verify that the interface values match your configuration.
Action
From operational mode, enter the show interfaces pp0 command.
user@host> show interfaces pp0.100
Logical interface pp0.100 (Index 71) (SNMP ifIndex 710)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPPoE
PPPoE:
State: SessionUp, Session ID: 1,
Session AC name: pppoe-server-1, Remote MAC address: 00:00:5e:00:53:34,
Underlying interface: demux0.100 (Index 70)
Link:
ge-5/0/3.32767
ge-5/1/2.32767
Input packets : 18572
Output packets: 18572
Keepalive settings: Interval 10 seconds, Up-count 1, Down-count 3
Keepalive: Input: 0 (never), Output: 18566 (00:00:02 ago)
LCP state: Opened
NCP state: inet: Opened, inet6: Not-configured, iso: Not-configured, mpls:
Not-configured
CHAP state: Closed
PAP state: Success
Protocol inet, MTU: 1500
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Primary
Local: 45.63.24.1Meaning
This output shows information about the PPPoE logical interface created on the underlying VLAN demux interface. The output includes the PPPoE family and aggregated Ethernet redundant link information, and shows input and output traffic for the PPPoE interface.
