- 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 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 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 Dynamic PPPoE Subscriber Interface over ATM
This example illustrates a Point-to-Point Protocol
over Ethernet (PPPoE) over ATM configuration that creates a dynamic
PPPoE (pp0) subscriber interface over a static ATM underlying
interface on an MX Series router. The router must have Module
Port Concentrator/Modular Interface Card (MPC/MIC) interfaces that
use an ATM MIC with small form-factor pluggable transceiver (SFP).
You can also configure a static PPPoE interface over a static ATM underlying interface on an MX Series router with an ATM MIC with SFP installed. For information, see Example: Configuring a Static PPPoE Subscriber Interface over ATM.
Requirements
This example uses the following software and hardware components:
MX Series 5G Universal Routing Platform
ATM MIC with SFP (Model Number MIC-3D-8OC3-2OC12-ATM) and compatible MPC1 or MPC2
Before you begin:
Make sure the MX Series router you are using has an ATM MIC with SFP installed and operational.
For information about compatible MPCs for the ATM MIC with SFP, see the MX Series Interface Module Reference.
For information about installing MPCs and MICs in an MX Series router, see the Hardware Guide for your MX Series router model.
Make sure you understand how to configure and use static ATM interfaces.
Make sure you understand how to configure and use dynamic PPPoE subscriber interfaces.
For overview information, see Subscriber Interfaces and PPPoE Overview
For configuration instructions, see Configuring Dynamic PPPoE Subscriber Interfaces
Overview
By using the ATM MIC with SFP and a supported MPC, you can configure
an MX Series router to support dynamic PPPoE subscriber access
over an ATM network. PPPoE-over-ATM configurations on MX Series
routers consist of one or more dynamically created PPPoE (pp0) subscriber interfaces over a static ATM underlying interface. Most
PPPoE and subscriber services features supported on terminated connections
and tunneled (L2TP access concentrator, or LAC) connections are also
supported for PPPoE-over-ATM connections on an MX Series router.
Optionally, you can dynamically apply subscriber services such
as class of service (CoS) and firewall filters to the PPPoE subscriber
interface by configuring these services in the dynamic profile that
creates the pp0 subscriber interface. In this example,
the PPPoE dynamic profile (pppoe-profile) applies CoS traffic shaping
parameters to the dynamic pp0 subscriber interface. Configuring
CoS and firewall filters in this manner enables you to efficiently
and economically provide these services to PPPoE subscribers accessing
the router over an ATM network using ATM Adaptation Layer 5 (AAL5)
permanent virtual connections (PVCs).
This example includes the following basic steps to configure dynamic PPPoE-over-ATM subscriber access on an MX Series router:
Create a PPPoE dynamic profile named pppoe-profile for the
pp0subscriber interface that includes all of the following:The logical unit number, represented by the
$junos-interface-unitpredefined dynamic variableThe name of the underlying ATM interface, represented by the
$junos-underlying-interfacepredefined dynamic variableThe
serverstatement, which configures the router to act as a PPPoE serverNote:Configuring the router to act as a PPPoE client is not supported.
The unnumbered address (lo0.0) for the IPv4 (
inet) protocol familyCoS traffic shaping parameters
Statically configure the ATM physical interface at-1/0/0 with virtual path identifier (VPI) 3.
Statically configure logical unit 2 on the ATM physical interface (at-1/0/0.2) with at least the following properties:
PPPoE-over-ATM logical link control (LLC) encapsulation (
ppp-over-ether-over-atm-llc)Virtual circuit identifier (VCI) 2 on VPI 3. The combination of VPIs and VCIs provisions the ATM AAL5 PVC for access over the ATM network.
PPPoE-specific options at the
[edit interfaces interface-name unit logical-unit-number family pppoe]hierarchy level, including at least the name of the associated PPPoE dynamic profile (pppoe-profile) that creates the pp0 dynamic subscriber interfaceIn dynamic PPPoE-over-ATM configurations, each
pp0interface defined in the dynamic profile corresponds to a dynamic PPPoE subscriber interface.Note:For dynamic or static PPPoE-over-ATM configurations on MX Series routers, You must specify PPPoE-specific options in the
family pppoestanza at the[edit interfaces interface-name unit logical-unit-number]hierarchy level. Specifying PPPoE-specific options in thepppoe-underlying-optionsstanza at the[edit interfaces interface-name unit logical-unit-number]hierarchy level is not supported for these configurations.
Configuration
To configure a dynamic PPPoE subscriber interface over an underlying ATM interface, perform these tasks:
- CLI Quick Configuration
- Configuring the PPPoE Dynamic Profile
- Configuring the ATM Physical Interface
- Configuring the Dynamic PPPoE Subscriber Interface on Logical Unit 2
CLI Quick Configuration
To quickly configure this example, copy the
following commands, paste them in a text file, remove any line breaks,
change any details necessary to match your network configuration,
and then copy and paste the commands into the CLI at the [edit] hierarchy level.
# PPPoE Dynamic Profile set dynamic-profiles pppoe-profile interfaces pp0 unit "$junos-interface-unit" ppp-options chap set dynamic-profiles pppoe-profile interfaces pp0 unit "$junos-interface-unit" pppoe-options underlying-interface "$junos-underlying-interface" set dynamic-profiles pppoe-profile interfaces pp0 unit "$junos-interface-unit" pppoe-options server set dynamic-profiles pppoe-profile interfaces pp0 unit "$junos-interface-unit" no-keepalives set dynamic-profiles pppoe-profile interfaces pp0 unit "$junos-interface-unit" family inet unnumbered-address lo0.0 set dynamic-profiles pppoe-profile class-of-service traffic-control-profiles tcp-test shaping-rate 10m set dynamic-profiles pppoe-profile class-of-service interfaces pp0 unit "$junos-interface-unit" output-traffic-control-profile tcp-test # # ATM Physical Interface set interfaces at-1/0/0 atm-options vpi 3 # # Logical Unit 2 set interfaces at-1/0/0 atm-options vpi 3 set interfaces at-1/0/0 unit 2 encapsulation ppp-over-ether-over-atm-llc set interfaces at-1/0/0 unit 2 vci 3.2 set interfaces at-1/0/0 unit 2 family pppoe access-concentrator ac-pppoeoa set interfaces at-1/0/0 unit 2 family pppoe duplicate-protection set interfaces at-1/0/0 unit 2 family pppoe dynamic-profile pppoe-profile set interfaces at-1/0/0 unit 2 family pppoe max-sessions 3 set interfaces at-1/0/0 unit 2 family pppoe short-cycle-protection
Configuring the PPPoE Dynamic Profile
Step-by-Step Procedure
To configure the PPPoE dynamic profile for the pp0 subscriber interface:
Name the dynamic profile.
content_copy zoom_out_map[edit] user@host# edit dynamic-profiles pppoe-profile
Specify that you want to configure the
pp0(PPPoE) interface.content_copy zoom_out_map[edit dynamic-profiles pppoe-profile] user@host# edit interfaces pp0
Specify that you want to configure the logical unit represented by the
$junos-interface-unitpredefined variable.content_copy zoom_out_map[edit dynamic-profiles pppoe-profile interfaces pp0] user@host# edit unit $junos-interface-unit
The
$junos-interface-unitvariable is dynamically replaced with the actual unit number supplied by the network when the subscriber logs in.Configure PPPoE-specific options for the
pp0interface.Configure the ATM underlying interface represented by the
$junos-underlying-interfacepredefined variable.content_copy zoom_out_map[edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”] user@host# set pppoe-options underlying-interface $junos-underlying-interface
The
$junos-underlying-interfacevariable is dynamically replaced with the actual name of the underlying interface supplied by the network when the subscriber logs in.Configure the router to act as a PPPoE server, also known as a remote access concentrator.
content_copy zoom_out_map[edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”] user@host# set pppoe-options server
Configure Challenge Handshake Authentication Protocol (CHAP) authentication for the
pp0interface.content_copy zoom_out_map[edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”] user@host# set ppp-options chap
Disable sending keepalive messages on the interface.
content_copy zoom_out_map[edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”] user@host# set no-keepalives
Configure the protocol family for the
pp0interface.Specify that you want to configure the IPv4 (
inet) protocol family.content_copy zoom_out_map[edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”] user@host# edit family inet
Configure the unnumbered address for the protocol family.
content_copy zoom_out_map[edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit” family inet] user@host# set unnumbered-address lo0.0 user@host# up 4
Configure CoS traffic shaping parameters in the dynamic profile for the pp0 subscriber interface.
Specify that you want to configure CoS traffic shaping parameters.
content_copy zoom_out_map[edit dynamic-profiles pppoe-profile] user@host# edit class-of-service
Create a traffic-control profile.
content_copy zoom_out_map[edit dynamic-profiles pppoe-profile class-of-service] user@host# edit traffic-control-profiles tcp-test
Configure the traffic shaping rate.
content_copy zoom_out_map[edit dynamic-profiles pppoe-profile class-of-service traffic-control-profiles tcp-test] user@host# set shaping-rate 10m user@host# up 2
Apply the traffic shaping parameters to the pp0 dynamic subscriber interface.
content_copy zoom_out_map[edit dynamic-profiles pppoe-profile class-of-service] user@host# edit interfaces pp0 unit $junos-interface-unit
Apply the output traffic scheduling and shaping profile to the interface.
content_copy zoom_out_map[edit dynamic-profiles pppoe-profile class-of-service interfaces pp0 unit “$junos-interface-unit] user@host# set output-traffic-control-profile tcp-test
Results
From the [edit] hierarchy level in configuration
mode, confirm the results of the PPPoE dynamic profile configuration
by issuing the show dynamic-profiles pppoe-profile command.
If the output does not display the intended configuration, repeat
the instructions in this example to correct it.
[edit]
user@host# show dynamic-profiles pppoe-profile
interfaces {
pp0 {
unit "$junos-interface-unit" {
ppp-options {
chap;
}
pppoe-options {
underlying-interface "$junos-underlying-interface";
server;
}
no-keepalives;
family inet {
unnumbered-address lo0.0;
}
}
}
}
class-of-service {
traffic-control-profiles {
tcp-test {
shaping-rate 10m;
}
}
interfaces {
pp0 {
unit "$junos-interface-unit" {
output-traffic-control-profile tcp-test;
}
}
}
}
If you are done configuring the dynamic profile, enter commit from configuration mode.
Configuring the ATM Physical Interface
Step-by-Step Procedure
To configure the ATM physical interface:
Specify that you want to configure ATM-specific options on the physical interface.
content_copy zoom_out_map[edit interfaces at-1/0/0] user@host# edit atm-options
Configure one or more VPIs on the physical interface.
content_copy zoom_out_map[edit interfaces at-1/0/0 atm-options] user@host# set vpi 3
Results
From the [edit] hierarchy level in configuration
mode, confirm the results of the ATM physical interface configuration
by issuing the show interfaces at-1/0/0 command. If the
output does not display the intended configuration, repeat the instructions
in this example to correct it.
[edit]
user@host# show interfaces at-1/0/0
atm-options {
vpi 3;
}
If you are done configuring the ATM physical interface, enter commit from configuration mode.
Configuring the Dynamic PPPoE Subscriber Interface on Logical Unit 2
Step-by-Step Procedure
To configure the dynamic PPPoE subscriber interface on logical unit 2:
Configure PPPoE-over-ATM LLC encapsulation on the interface.
content_copy zoom_out_map[edit interfaces at-1/0/0 unit 2] user@host# set encapsulation ppp-over-ether-over-atm-llc
Configure the VCI for the logical interface.
content_copy zoom_out_map[edit interfaces at-1/0/0 unit 2] user@host# set vci 3.2
This statement configures VCI 2 on VPI 3.
Specify that you want to configure the PPPoE protocol family.
content_copy zoom_out_map[edit interfaces at-1/0/0 unit 2] user@host# edit family pppoe
Associate the interface with the dynamic profile that creates the dynamic PPPoE subscriber interface.
content_copy zoom_out_map[edit interfaces at-1/0/0 unit 2 family pppoe] user@host# set dynamic-profile pppoe-profile
Configure additional PPPoE-specific options for the dynamic subscriber interface.
content_copy zoom_out_map[edit interfaces at-1/0/0 unit 2 family pppoe] user@host# set max-sessions 3 user@host# set duplicate-protection user@host# set short-cycle-protection user@host# set access-concentrator ac-pppoeoa
Results
From the [edit] hierarchy level in configuration
mode, confirm the results of the dynamic PPPoE subscriber interface
configuration on logical unit 2 by issuing the show interfaces
at-1/0/0.2 command. If the output does not display the intended
configuration, repeat the instructions in this example to correct
it.
[edit]
user@host# show interfaces at-1/0/0.2
encapsulation ppp-over-ether-over-atm-llc;
vci 3.2;
family pppoe {
access-concentrator ac-pppoeoa;
duplicate-protection;
dynamic-profile pppoe-profile;
max-sessions 3;
short-cycle-protection;
}
If you are done configuring the dynamic PPPoE subscriber interface
on logical unit 2, enter commit from configuration
mode.
Verification
To confirm that the dynamic PPPoE subscriber interface is properly configured on ATM interface at-1/0/0.2, perform the following tasks:
- Verifying the ATM Physical Interface Configuration
- Verifying the Dynamic PPPoE Subscriber Interface Configuration on Logical Unit 2
- Verifying the PPPoE Underlying Interface Configuration
Verifying the ATM Physical Interface Configuration
Purpose
Verify that ATM physical interface at-1/0/0 is properly configured for use with ATM PVCs.
Action
From operational mode, issue the show interfaces
at-1/0/0 command.
For brevity, this show command output includes only
the configuration that is relevant to the at-1/0/0 physical interface.
Any other configuration on the system has been replaced with ellipses
(...).
user@host> show interfaces at-1/0/0
Physical interface: at-1/0/0, Enabled, Physical link is Up
Interface index: 173, SNMP ifIndex: 592
Link-level type: ATM-PVC, MTU: 2048, Clocking: Internal, SDH mode, Speed: OC3, Loopback: None, Payload scrambler: Enabled
Device flags : Present Running
Link flags : None
CoS queues : 8 supported, 8 maximum usable queues
Schedulers : 0
Current address: 00:00:5e:00:53:95
Last flapped : 2012-09-17 07:21:19 PDT (08:26:16 ago)
Input rate : 0 bps (0 pps)
Output rate : 0 bps (0 pps)
SDH alarms : None
SDH defects : None
VPI 3
Flags: Active
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input packets: 0
Output packets: 0
...Meaning
ATM-PVC in the Link-level Type field indicates
that encapsulation for ATM permanent virtual circuits is being used
on ATM physical interface at-1/0/0. The Active flag for
VPI 3 indicates that the virtual path is up and operational.
Verifying the Dynamic PPPoE Subscriber Interface Configuration on Logical Unit 2
Purpose
Verify that the dynamic PPPoE subscriber interface is properly configured on logical unit 2 (at-1/0/0.2).
Action
From operational mode, issue the show interfaces
at-1/0/0.2 command.
user@host> show interfaces at-1/0/0.2
Logical interface at-1/0/0.2 (Index 350) (SNMP ifIndex 1701)
Flags: Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPPoE-over-ATM-LLC
Input packets : 0
Output packets: 0
Protocol pppoe
Dynamic Profile: pppoe-profile,
Service Name Table: None,
Max Sessions: 3, Max Sessions VSA Ignore: Off,
Duplicate Protection: On, Short Cycle Protection: mac-address,
AC Name: ac-pppoeoa
VCI 3.2
Flags: Active
Total down time: 0 sec, Last down: Never
Input packets : 0
Output packets: 0
Meaning
PPPoE-over-ATM-LLC in the Encapsulation
field indicates that logical interface at-1/0/0.2 is properly configured
for PPPoE-over-ATM LLC encapsulation. Protocol pppoe indicates
that the PPPoE protocol family has been properly configured on the
logical interface. The Dynamic Profile field indicates that dynamic
profile pppoe-profile creates the dynamic PPPoE subscriber
interface. The Active flag for VCI 3.2 indicates that VCI 2
on VPI 3 is up and operational.
Verifying the PPPoE Underlying Interface Configuration
Purpose
Verify that the underlying interface is properly configured for dynamic PPPoE-over-ATM subscriber access.
Action
From operational mode, issue the show pppoe underlying-interfaces
at-1/0/0.2 command.
user@host> show pppoe underlying-interfaces at-1/0/0.2 detail at-1/0/0.2 Index 350 State: Static, Dynamic Profile: pppoe-profile, Max Sessions: 3, Max Sessions VSA Ignore: Off, Active Sessions: 0, Service Name Table: None, Duplicate Protection: On, Short Cycle Protection: mac-address, AC Name: ac-pppoeoa,
Meaning
This command indicates that ATM logical interface at-1/0/0.2
is properly configured as the PPPoE underlying interface. Static in the State field indicates that at-1/0/0/.2 is statically configured.
The Dynamic Profile field indicates that pppoe-profile is
the name of the dynamic profile used to create this interface. The
remaining fields display information about the PPPoE-specific interface
options configured for the PPPoE underlying interface at the [edit interfaces at-1/0/0 unit 2 family pppoe] hierarchy level.
