Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring a Static PPPoE Subscriber Interface over ATM

 

This example illustrates a Point-to-Point Protocol over Ethernet (PPPoE) over ATM configuration that creates a static 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 dynamic 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 Dynamic 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:

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

  2. Make sure you understand how to configure and use static ATM interfaces.

    See ATM Interfaces Overview.

Overview

By using the ATM MIC with SFP and a supported MPC, you can configure an MX Series router to support static PPPoE subscriber access over an ATM network using ATM Adaptation Layer 5 (AAL5) permanent virtual connections (PVCs). PPPoE-over-ATM configurations on MX Series routers consist of one or more statically created PPPoE (pp0) logical 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.

This example include the following basic steps to configure static PPPoE-over-ATM subscriber access on an MX Series router:

  1. Statically configure ATM physical interface at-1/0/6 with virtual path identifier (VPI) 6.

  2. Statically configure logical unit 2 on the ATM physical interface (at-1/0/6.2) with the following properties:

    • PPPoE-over-ATM logical link control (LLC) encapsulation (ppp-over-ether-over-atm-llc)

    • Virtual circuit identifier (VCI) 2 on VPI 6. The combination of VPIs and VCIs provisions the ATM AAL5 PVC for access over the ATM network.

    • (Optional) PPPoE-specific options at the [edit interfaces interface-name unit logical-unit-number family pppoe] hierarchy level

      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.

  3. Statically configure the pp0 logical subscriber interface (pp0.2) with at least the following properties:

    • The name of the underlying ATM interface (at-1/0/6.2)

    • The server statement, which configures the router to act as a PPPoE server

    • The unnumbered address (lo0.0) for the inet (IPv4) or inet6 (IPv6) protocol family

    In static PPPoE-over-ATM configurations, each pp0 logical interface configured at the [edit interfaces pp0 unit logical-unit-number] hierarchy level corresponds to a static PPPoE subscriber interface.

Configuration

To configure a static PPPoE subscriber interface over an underlying ATM interface, perform these tasks:

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 ATM Physical Interface

Step-by-Step Procedure

To configure the ATM physical interface:

  1. Specify that you want to configure ATM-specific options on the physical interface.
  2. Configure one or more VPIs on the physical interface.

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/6 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 Encapsulation, VCI, and PPPoE Options on Logical Unit 2

Step-by-Step Procedure

To configure encapsulation, VCI, and PPPoE options on logical unit 2:

  1. Configure PPPoE-over-ATM LLC encapsulation on the interface.
  2. Configure the VCI for the logical interface.

    This statement configures VCI 2 on VPI 6.

  3. Specify that you want to configure the PPPoE protocol family.
  4. Configure additional PPPoE-specific options for the dynamic subscriber interface.

Results

From the [edit] hierarchy level in configuration mode, confirm the results of the configuration on logical unit 2 by issuing the show interfaces at-1/0/6.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 logical unit 2, enter commit from configuration mode.

Configuring the Static PPPoE Subscriber Interface

Step-by-Step Procedure

To configure the static PPPoE subscriber interface:

  1. Specify that you want to configure the pp0 subscriber interface on logical unit 2.
  2. Specify that you want to configure PPP options for the subscriber interface.
  3. Configure Challenge Handshake Authentication Protocol (CHAP) authentication for the subscriber interface.
  4. Specify that you want to configure PPPoE-specific options.
  5. Associate the PPPoE subscriber interface with the underlying ATM interface.
  6. Configure the router to act as a PPPoE server, also known as a remote access concentrator.
  7. Configure the interval for sending keepalive requests.
  8. Specify that you want to configure the IPv4 (inet) protocol family.
  9. Configure the unnumbered address for the protocol family.

Results

From the [edit] hierarchy level in configuration mode, confirm the results of the static PPPoE subscriber interface configuration by issuing the show interfaces pp0 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 static PPPoE subscriber interface, enter commit from configuration mode.

Verification

To confirm that the static PPPoE subscriber interface pp0.2 is properly configured on ATM underlying interface at-1/0/6.2, perform the following tasks:

Verifying the ATM Physical Interface Configuration

Purpose

Verify that ATM physical interface at-1/0/6 is properly configured for use with ATM PVCs.

Action

From operational mode, issue the show interfaces at-1/0/6 command.

For brevity, this show command output includes only the configuration that is relevant to the at-1/0/6 physical interface. Any other configuration on the system has been replaced with ellipses (...).

user@host> show interfaces at-1/0/6

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/6. The Active flag for VPI 6 indicates that the virtual path is up and operational.

Verifying the Encapsulation, VCI, and PPPoE Options Configuration on Logical Unit 2

Purpose

Verify that the encapsulation, VCI, and PPPoE settings have been properly configured on logical unit 2 (at-1/0/6.2).

Action

From operational mode, issue the show interfaces at-1/0/6.2 command.

user@host> show interfaces at-1/0/6.2

Meaning

PPPoE-over-ATM-LLC in the Encapsulation field indicates that logical interface at-1/0/6.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 Active flag for VCI 6.2 indicates that VCI 2 on VPI 6 is up and operational.

Verifying the Static PPPoE Subscriber Interface Configuration

Purpose

Verify that the static PPPoE subscriber interface (pp0.2) is properly configured.

Action

From operational mode, issue the show interfaces pp0 command.

user@host> show interfaces pp0

Meaning

PPPoE in the Link-level type field indicates that PPPoE encapsulation is in use on the pp0 physical interface. PPPoE in the Encapsulation field indicates that PPPoE encapsulation is also in use on the pp0.2 logical subscriber interface. The Underlying interface field indicates that at-1/0/6.2 is properly configured as the underlying interface for the static PPPoE subscriber interface. Protocol inet indicates that the IPv4 protocol family is properly configured on the pp0.2 logical subscriber interface.

Verifying the PPPoE Underlying Interface Configuration

Purpose

Verify that the underlying interface is properly configured for static PPPoE-over-ATM subscriber access.

Action

From operational mode, issue the show pppoe underlying-interfaces at-1/0/6.2 extensive command.

user@host> show pppoe underlying-interfaces at-1/0/6.2 extensive

Meaning

This command indicates that ATM logical interface at-1/0/6.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 remaining fields display information about the PPPoE-specific interface options configured for the PPPoE underlying interface at the [edit interfaces at-1/0/6 unit 2 family pppoe] hierarchy level. The Lockout Time fields, which appear in this command only when you display the extensive level of output, show the minimum lockout time (120 seconds) and maximum lockout time (240 seconds) configured for the PPPoE underlying interface.