Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

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).

Note: 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

• Junos OS Release 12.2
• MX Series 3D Universal Edge Router
• ATM MIC with SFP (Model Number MIC-3D-8OC3-2OC12-ATM) and compatible MPC1 or MPC2

1. 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 3D Universal Edge Routers Line Card Guide .
   • For information about installing MPCs and MICs in an MX Series router, see the Hardware Guide for your MX Series router model.
2. Make sure you understand how to configure and use static ATM interfaces.

   See ATM Interfaces Overview.

3. 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 Using Dynamic Profiles

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).

1. Create a PPPoE dynamic profile named pppoe-profile for the pp0 subscriber interface that includes all of the following:
   • The logical unit number, represented by the $junos-interface-unit predefined dynamic variable
   • The name of the underlying ATM interface, represented by the $junos-underlying-interface predefined dynamic variable
   • The server statement, which configures the router to act as a PPPoE server

     Note: Configuring the router to act as a PPPoE client is not supported.

   • The unnumbered address (lo0.0) for the IPv4 (inet) protocol family
   • CoS traffic shaping parameters
2. Statically configure the ATM physical interface at-1/0/0 with virtual path identifier (VPI) 3.
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 interface

     In dynamic PPPoE-over-ATM configurations, each pp0 interface 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 pppoe stanza at the [edit interfaces interface-name unit logical-unit-number] hierarchy level. Specifying PPPoE-specific options in the pppoe-underlying-options stanza 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:

• 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.

Configuring the PPPoE Dynamic Profile

Step-by-Step Procedure

1. Name the dynamic profile.
   [edit]user@host# edit dynamic-profiles pppoe-profile
2. Specify that you want to configure the pp0 (PPPoE) interface.
   [edit dynamic-profiles pppoe-profile]user@host# edit interfaces pp0
3. Specify that you want to configure the logical unit represented by the $junos-interface-unit predefined variable.
   [edit dynamic-profiles pppoe-profile interfaces pp0]user@host# edit unit $junos-interface-unit

   The $junos-interface-unit variable is dynamically replaced with the actual unit number supplied by the network when the subscriber logs in.

4. Configure PPPoE-specific options for the pp0 interface.
   1. Configure the ATM underlying interface represented by the $junos-underlying-interface predefined variable.
      [edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”]user@host# set pppoe-options underlying-interface $junos-underlying-interface

      The $junos-underlying-interface variable is dynamically replaced with the actual name of the underlying interface supplied by the network when the subscriber logs in.

   2. Configure the router to act as a PPPoE server, also known as a remote access concentrator.
      [edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”]user@host# set pppoe-options server
5. Configure Challenge Handshake Authentication Protocol (CHAP) authentication for the pp0 interface.
   [edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”]user@host# set ppp-options chap
6. Disable sending keepalive messages on the interface.
   [edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”]user@host# set no-keepalives
7. Configure the protocol family for the pp0 interface.
   1. Specify that you want to configure the IPv4 (inet) protocol family.
      [edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit”]user@host# edit family inet
   2. Configure the unnumbered address for the protocol family.
      [edit dynamic-profiles pppoe-profile interfaces pp0 unit “$junos-interface-unit” family inet]user@host# set unnumbered-address lo0.0user@host# up 4
8. Configure CoS traffic shaping parameters in the dynamic profile for the pp0 subscriber interface.
   1. Specify that you want to configure CoS traffic shaping parameters.
      [edit dynamic-profiles pppoe-profile]user@host# edit class-of-service
   2. Create a traffic control profile.
      [edit dynamic-profiles pppoe-profile class-of-service]user@host# edit traffic-control-profiles tcp-test
   3. Configure the traffic shaping rate.
      [edit dynamic-profiles pppoe-profile class-of-service traffic-control-profiles tcp-test]user@host# set shaping-rate 10muser@host# up 2
   4. Apply the traffic shaping parameters to the pp0 dynamic subscriber interface.
      [edit dynamic-profiles pppoe-profile class-of-service]user@host# edit interfaces pp0 unit $junos-interface-unit
   5. Apply the output traffic scheduling and shaping profile to the interface.
      [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.

If you are done configuring the dynamic profile, enter commit from configuration mode.

Configuring the ATM Physical Interface

Step-by-Step Procedure

1. Specify that you want to configure ATM-specific options on the physical interface.
   [edit interfaces at-1/0/0]user@host# edit atm-options
2. Configure one or more VPIs on the physical interface.
   [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.

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

1. Configure PPPoE-over-ATM LLC encapsulation on the interface.
   [edit interfaces at-1/0/0 unit 2]user@host# set encapsulation ppp-over-ether-over-atm-llc
2. Configure the VCI for the logical interface.
   [edit interfaces at-1/0/0 unit 2]user@host# set vci 3.2

   This statement configures VCI 2 on VPI 3.

3. Specify that you want to configure the PPPoE protocol family.
   [edit interfaces at-1/0/0 unit 2]user@host# edit family pppoe
4. Associate the interface with the dynamic profile that creates the dynamic PPPoE subscriber interface.
   [edit interfaces at-1/0/0 unit 2 family pppoe]user@host# set dynamic-profile pppoe-profile
5. Configure additional PPPoE-specific options for the dynamic subscriber interface.
   [edit interfaces at-1/0/0 unit 2 family pppoe]user@host# set max-sessions 3user@host# set duplicate-protectionuser@host# set short-cycle-protectionuser@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.

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 (...).

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:1f:12:bc:4a: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.

  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.

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.