Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Example: Configuring Static PPPoE MLPPP Subscribers

This example shows how to configure static Point-to-Point Protocol over Ethernet (PPPoE) MLPPP for terminated and tunneled subscribers.

Requirements

This example uses the following hardware and software components:

  • MX Series with MPC2s installed

  • Junos OS Release 13.3 or later

Before you configure static PPPoE MLPPP for terminated and tunneled subscribers, be sure you have:

Overview

An MLPPP subscriber consists of two IFLs (logical interfaces), a member link, and a bundle. For static MLPPP subscribers, you configure both member link and bundle IFLs manually. After you configure the subscriber’s interface using the family mlppp statement, before the member link IFL can start LCP (link control protocol) negotiation PPPoE session, you must also fully configure the member link’s bundle IFL. Figure 1 shows how the different types of traffic traverse through a network where the MX Series terminates PPPoE sessions.

Topology

Figure 1: PPP and MLPPP Traffic Terminated at MX SeriesPPP and MLPPP Traffic Terminated at MX Series

The following two domains are shown terminating traffic at the MX Series:

  • PPP domain—Contains data and voice traffic

  • MLPPP domain—Contains data traffic only

Configuration

To configure static PPPoE MLPPP for terminated and tunneled subscribers, perform these tasks:

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into 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 a Static pp0 Member Link IFL

Step-by-Step Procedure

The following example requires that you navigate various levels in the configuration hierarchy.

To configure the static PPPoE member link, you specify the static bundle using the family mlppp statement. PPPoE sessions are supported over the following underlying interfaces: Ethernet interfaces, static and dynamic VLAN, VLAN demultiplexing (demux) over Ethernet interfaces, and VLAN demux over aggregated Ethernet interfaces.

You must also configure the family inet statement in the pp0 interface for tunneled subscribers. The family inet statement enables the L2TP long route to be installed and supported for the lookup engine to steer control packets to the Routing Engine.

The following example shows how to configure pp0 member link IFL over static VLAN to support the following different types of subscribers:

  • si-1/0/0.1—Both terminated and tunneled PPP and MLPPP subscribers can log in successfully.

  • si-1/0/0.2—Only terminated MLPPP subscribers can log in successfully.

  • si-1/0/0.3—Terminated and tunneled MLPPP subscribers can log in successfully.

  1. Create the Gigabit Ethernet underlying interface for the PPPoE session, ge-3/0/0, and enable VLAN tagging.

    [edit interfaces]user@host# set ge-3/0/0 vlan-tagging

  2. For the ge-3/0/0 interface, configure PPP over Ethernet encapsulation for three VLANs.

    [edit interfaces ge-3/0/0]user@host# set unit 1 encapsulation ppp-over-ether vlan-id 1user@host# set unit 2 encapsulation ppp-over-ether vlan-id 2user@host# set unit 3 encapsulation ppp-over-ether vlan-id 3

  3. Configure the dynamic PPPoE pp0 subscriber interface to support PPPoE sessions.

    [edit interfaces]user@host# set pp0

  4. Configure the first of three logical interfaces.

    Step-by-Step Procedure
    1. Configure the first logical interface for the pp0 subscriber interface on the MX Series and set an interval of 30 seconds for the keepalive value.

      [edit interfaces pp0]user@host# set unit 1 keepalives interval 30

    2. Configure the underlying interface ge-3/0/0.1 and PPPoE server mode for a dynamic PPPoE logical interface in a dynamic profile.

      [edit interfaces pp0 unit 1]user@host# set pppoe-options underlying-interface ge-3/0/0.1 server

    3. Configure PPP-specific interface properties in a dynamic profile: pap and chap, and set the dynamic-profile to the services dynamic profile.

      Note:

      The dynamic profile is applied when Link Control Protocol (LCP) is negotiated in PPP.

      [edit interfaces pp0 unit 1]user@host# set ppp-options pap chap dynamic-profile pp0-l2l3-service prof

    4. Configure the static bundle for the PPPoE member link for MLPPP subscribers using the family mlppp statement.

      Note:

      The family mlppp statement determines whether MLPPP is supported for subscribers coming in from the underlying interface.

      [edit interfaces pp0 unit 1]user@host# set family mlppp bundle si-1/0/0.1

    5. Configure the family inet statement and the unnumbered address for the protocol family required for PPP subscribers for tunneled PPP and for MLPPP subscribers.

      [edit interfaces pp0 unit 1]user@host# set family inet unnumbered-address lo0.0

    6. (Optional) Enable the family inet6 statement and address for the mixed mode support for PPP and MLPPP subscribers.

      [edit interfaces pp0 unit 1]user@host# set family inet6 address 2001:db8:204::1:1:2/64

  5. Configure the second of three logical interfaces.

    Step-by-Step Procedure
    1. Configure the second logical interface for the pp0 subscriber interface on the MX Series and set an interval of 30 seconds for the keepalive value.

      [edit interfaces pp0]user@host# set unit 2 keepalives interval 30

    2. Configure the underlying interface ge-3/0/0.2 and PPPoE server mode for a dynamic PPPoE logical interface in a dynamic profile.

      [edit interfaces pp0 unit 2]user@host# set pppoe-options underlying interface ge-3/0/0.2 server

    3. Configure PPP-specific interface properties in a dynamic profile: pap, and set the dynamic-profile to the services dynamic profile.

      Note:

      The dynamic profile is applied when Link Control Protocol (LCP) is negotiated in PPP.

      [edit interfaces pp0 unit 2]user@host# set ppp-options pap dynamic-profile pp0-l2l3-service prof

    4. Configure the static bundle for the PPPoE member link for MLPPP subscribers using the family mlppp statement.

      Note:

      The family mlppp statement determines whether MLPPP is supported for subscribers coming in from the underlying interface.

      [edit interfaces pp0 unit 2]user@host# set family mlppp bundle si-1/0/0.2

  6. Configure the last of three logical interfaces.

    Step-by-Step Procedure
    1. Configure the third logical interface for the pp0 subscriber interface on the MX Series and set an interval of 30 seconds for the keepalive value.

      [edit interfaces pp0]user@host# set unit 3 keepalives interval 30

    2. Configure the underlying interface ge-3/0/0.3 and PPPoE server mode for a dynamic PPPoE logical interface in a dynamic profile.

      [edit interfaces pp0 unit 3]user@host# set pppoe-options underlying interface ge-3/0/0.3 server

    3. Configure PPP-specific interface properties in a dynamic profile: pap and chap, and set the dynamic-profile to the services dynamic profile.

      Note:

      The dynamic profile is applied when Link Control Protocol (LCP) is negotiated in PPP.

      [edit interfaces pp0 unit 3]user@host# set ppp-options pap chap dynamic-profile pp0-l2l3-service prof

    4. Configure the static bundle for the PPPoE member link for MLPPP subscribers using the family mlppp statement.

      Note:

      The family mlppp statement determines whether MLPPP is supported for subscribers coming in from the underlying interface.

      [edit interfaces pp0 unit 3]user@host# set family mlppp bundle si-1/0/0.3

    5. Configure tunneled subscribers.

      [edit interfaces pp0 unit 3]user@host# set family inet

  7. If you are done configuring the device, commit the configuration.

Configuring a Static Inline Services MLPPP Bundle IFL

Step-by-Step Procedure

The following example requires that you navigate various levels in the configuration hierarchy.

To configure the static inline services (si) interface MLPPP bundle IFL, you specify the encapsulation multilink-ppp statement within the si interface. The si interface anchors the bundle interface.

You can also set these optional MLPPP parameters: MRRU, short sequence, and fragment-threshold. The following example shows how to configure the static si interface MLPPP bundle IFL:

  1. Create the static (si) interface MLPPP bundle IFL si-5/0/0 with a unit of 100.

    [edit interfaces]user@host# set si-5/0/0 unit 100

  2. Configure the encapsulation multilink-ppp statement to enable MLPPP bundling for the si-5/0/0.100 interface.

    [edit interfaces si-5/0/0.100]user@host# set encapsulation multilink-ppp

  3. Configure the following MLPPP options for this example:

    • mrru—Specifies the maximum received reconstructed unit value ranging from 1500 through 4500 bytes.

    • fragment-threshold—Applies to all packets and forwarding classes, ranging from 128 through 16,320 bytes.

    • short-sequence—Determines the header format for the MLPPP. Default is long-sequence.

    [edit interfaces si-5/0/0.100]user@host# set mrru 1500user@host# set fragment-threshold 640user@host# set short-sequence

  4. Enable support for static si interface IFL dynamic services by configuring the ppp-options dynamic profile statement.

    [edit interfaces si-5/0/0.100]user@host# set ppp-options dynamic-profile l2l3-service-prof

  5. If you are done configuring the device, commit the configuration.

Results

From configuration mode, confirm your configuration by entering the show interfaces command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Verification

Confirm that the configuration is working properly.

Verifying the Bundle IFL Information

Purpose

Verify that the bundle IFL information is correct for PPPoE MLPPP subscribers.

Action

Meaning

Due to the particulars of implementation, the following error counts associated with a bundle always display 0: packet drops (bytes), fragment drops (bytes), fragment timeout, missing sequence number, out-of-order sequence number, out-of-range sequence number, packet data buffer overflow and fragment data buffer overflow, and MRRU exceeded.

Verifying the Member Link IFL Information

Purpose

Verify that the member link IFL information is correct for subscribers.

Action

Meaning

Logical interface pp0.1073756923 has been configured with PPPoE, multilink bundle si-1/0/0.1073756924, and protocol mlppp.

Verifying the Subscriber Information

Purpose

Verify that the subscriber information for static MLPPP over PPPoE is correct.

Action

Meaning

Subscriber information has been configured for static PPPoE with interface pp0.20, and static MLPPP with interface si-1/0/0.1020.