Supported Platforms
Related Documentation
- MX Series
- ATM for Subscriber Access Overview
- Configuring ATM for Subscriber Access
- Example: Configuring a Dynamic PPPoE Subscriber Interface over ATM
- Example: Configuring a Static PPPoE Subscriber Interface over ATM
- Example: Configuring a Static Subscriber Interface for IP Access over ATM
- Example: Configuring a Static Subscriber Interface for IP Access over Ethernet over ATM
Example: Configuring a Static PPP Subscriber Interface over ATM
This example illustrates a PPP-over-ATM (PPPoA) configuration that creates three static PPP logical subscriber interfaces 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).
Requirements
This example uses the following software and hardware components:
- 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
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 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.
- Make sure you understand how to configure and use static ATM interfaces.
- Create the dynamic profile (pppoa-cos-profile) and access
profile (pe-B-ppp-clients) referenced in the configuration.
- For information about creating a basic dynamic profile, see Configuring a Basic Dynamic Profile.
- For information about creating a dynamic profile for class of service (CoS) attributes, see Configuring Traffic Scheduling and Shaping for Subscriber Access.
- For information about creating an access profile for PPP Challenge Handshake Authentication Protocol (CHAP) authentication, see Configuring the PPP Challenge Handshake Authentication Protocol.
Overview
By using the ATM MIC with SFP and a supported MPC, you can configure an MX Series router to support PPP subscriber access over an ATM network. PPPoA configurations on MX Series routers consist of one or more statically created PPP logical subscriber interfaces over a static ATM underlying interface.
Optionally, you can use dynamic profiles to dynamically or statically apply subscriber services services, such as CoS and firewall filters, to the static PPP logical interface. Configuring CoS and firewall filters in this manner enables you to efficiently and economically provide these services to PPP subscribers accessing the router over an ATM network using ATM Adaptation Layer 5 (AAL5) permanent virtual connections (PVCs). This example uses a previously configured dynamic profile named pppoa-cos-profile to apply traffic scheduling and shaping parameters to logical interface at-1/0/1.2.
To configure PPPoA subscriber access on MX Series routers, you must configure the correct encapsulation type: atm-ppp-llc for PPPoA encapsulation with logical link control (LLC), or atm-ppp-vc-mux for PPPoA encapsulation with virtual circuit (VC) multiplexing. This example configures atm-ppp-llc as the encapsulation type on logical interface at-1/0/1.0, and atm-ppp-vc-mux as the encapsulation type on logical interfaces at-1/0/1.1 and at-1/0/1.2.
To provision the ATM AAL5 PVCs for access over the ATM network, you must also configure the virtual path identifiers (VPIs) on the ATM physical interface, and one or more virtual circuit identifiers (VCIs) for each VPI.
In PPPoA configurations, each statically configured logical interface (for example, at-1/0/1.0) corresponds to a PPP logical subscriber interface. This example configures three PPP logical subscriber interfaces over an ATM interface, as follows:
- The ATM physical interface (at-1/0/1) is statically configured with VPI 0 and VPI 2.
- Logical interface at-1/0/1.0 (logical unit 0) is configured with PPP-over AAL5 LLC encapsulation, VCI 0.120 (VCI 120 on VPI 0), PPP-specific options, and the IPv4 protocol family and address.
- Logical interface at-1/0/1.1 (logical unit 1) is configured with PPP-over-AAL5 VC multiplexing encapsulation, VCI 2.120 (VCI 120 on VPI 2), PPP-specific options, and the IPv4 protocol family and address.
- Logical interface at-1/0/1.2 (logical unit 2) is configured with PPP-over-AAL5 VC multiplexing encapsulation, VCI 2.121 (VCI 121 on VPI 2), PPP-specific options, and the IPv4 protocol family and address. The PPP-specific options include applying a dynamic profile named pppoa-cos-profile to the static PPP interface. The pppoa-cos-profile dynamic profile applies traffic scheduling and shaping parameters to the PPP logical subscriber interface.
Configuration
To configure static PPP logical subscriber interfaces over an ATM interface, perform these tasks:
- Configuring the ATM Physical Interface
- Configuring the Static PPP Subscriber Interface on Logical Unit 0
- Configuring the Static PPP Subscriber Interface on Logical Unit 1
- Configuring the Static PPP 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 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.[edit interfaces at-1/0/1]user@host# edit atm-options
- 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/1 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 Static PPP Subscriber Interface on Logical Unit 0
Step-by-Step Procedure
To configure the static PPP subscriber interface on logical unit 0:
- Configure PPP-over AAL5 LLC encapsulation on the logical
interface.[edit interfaces at-1/0/1 unit 0]user@host# set encapsulation atm-ppc-llc
- Configure the VCI for the logical interface.[edit interfaces at-1/0/1 unit 0]user@host# set vci 0.120
- Specify that you want to configure options for PPP CHAP
on the logical interface.[edit interfaces at-1/0/1 unit 0]user@host# edit ppp-options chap
- Assign the previously configured pe-B-ppp-clients access
profile to the PPP logical subscriber interface.[edit interfaces at-1/0/1 unit 0 ppp-options chap]user@host# set access-profile pe-B-ppp-clients
- Configure the local name used by the interface in CHAP
challenge and response packets.[edit interfaces at-1/0/1 unit 0 ppp-options chap]user@host# set local-name “pe-A-at-1/0/1”user@host# up 2
- Configure the transmission of keepalive messages on the
logical interface.[edit interfaces at-1/0/1 unit 0]user@host# set keepalives interval 5user@host# set keepalives up-count 6user@host# set keepalives down-count 4
- Configure the IPv4 (inet) protocol family and IP address.
Results
From the [edit] hierarchy level in configuration mode, confirm the results of the static PPP subscriber interface configuration on logical unit 0 by issuing the show interfaces at-1/0/1.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 PPP logical subscriber interface on logical unit 0, enter commit from configuration mode.
Configuring the Static PPP Subscriber Interface on Logical Unit 1
Step-by-Step Procedure
To configure the static PPP subscriber interface on logical unit 1:
- Configure PPP-over-AAL5 VC multiplexing encapsulation
on the logical interface.[edit interfaces at-1/0/1 unit 1]user@host# set encapsulation atm-ppc-vc-mux
- Configure the VCI for the logical interface.[edit interfaces at-1/0/1 unit 1]user@host# set vci 2.120
- Configure the transmission of keepalive messages on the
logical interface.[edit interfaces at-1/0/1 unit 1]user@host# set keepalives interval 6user@host# set keepalives up-count 6user@host# set keepalives down-count 4
- Configure the IPv4 (inet) protocol family and IP address.
Results
From the [edit] hierarchy level in configuration mode, confirm the results of the static PPP subscriber interface configuration on logical unit 1 by issuing the show interfaces at-1/0/1.1 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 PPP logical subscriber interface on logical unit 1, enter commit from configuration mode.
Configuring the Static PPP Subscriber Interface on Logical Unit 2
Step-by-Step Procedure
To configure the static PPP subscriber interface on logical unit 2:
- Configure PPP-over-AAL5 VC multiplex encapsulation on
the logical interface.[edit interfaces at-1/0/1 unit 2]user@host# set encapsulation atm-ppc-vc-mux
- Configure the VCI for the logical interface.[edit interfaces at-1/0/1 unit 2]user@host# set vci 2.121
- Specify that you want to configure options for PPP CHAP
on the logical interface.[edit interfaces at-1/0/1 unit 2]user@host# edit ppp-options chap
- Assign the previously configured pe-A-ppp-clients access
profile to the PPP logical subscriber interface.[edit interfaces at-1/0/1 unit 2 ppp-options chap]user@host# set access-profile pe-A-ppp-clients
- Configure the local name used by the interface in CHAP
challenge and response packets.[edit interfaces at-1/0/1 unit 2 ppp-options chap]user@host# set local-name “pe-A-at-1/0/1”
- Configure passive mode for CHAP authentication.
- Apply the previously configured pppoa-cos-profile dynamic
profile to the PPP logical subscriber interface.[edit interfaces at-1/0/1 unit 2 ppp-options]user@host# set dynamic-profile pppoa-cos-profileuser@host# up
- Configure the transmission of keepalive messages on the
logical interface.[edit interfaces at-1/0/1 unit 2]user@host# set keepalives interval 5user@host# set keepalives up-count 6user@host# set keepalives down-count 4
- Configure the IPv4 (inet) protocol family and IP address.
Results
From the [edit] hierarchy level in configuration mode, confirm the results of the static PPP subscriber interface configuration on logical unit 2 by issuing the show interfaces at-1/0/1.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 PPP logical subscriber interface on logical unit 2, enter commit from configuration mode.
Verification
To confirm that the PPPoA configuration is working properly, perform the following tasks:
- Verifying the ATM Physical Interface Configuration
- Verifying the Static PPPoA Configuration on Logical Unit 0
- Verifying the Static PPPoA Configuration on Logical Unit 1
- Verifying the Static PPPoA Configuration on Logical Unit 2
Verifying the ATM Physical Interface Configuration
Purpose
Verify that the at-1/0/1 physical interface is properly configured for use with ATM PVCs.
Action
From operational mode, issue the show interfaces at-1/0/1 command.
For brevity, this show command output includes only the configuration that is relevant to the at-1/0/1 physical interface. Any other configuration on the system has been replaced with ellipses (...).
user@host> show interfaces at-1/0/1
Physical interface: at-1/0/1, Enabled, Physical link is Down Interface index: 166, SNMP ifIndex: 593 Link-level type: ATM-PVC, MTU: 2048, Clocking: Internal, SONET mode, Speed: OC3, Loopback: None, Payload scrambler: Enabled Device flags : Present Running Down Link flags : None CoS queues : 8 supported, 8 maximum usable queues Schedulers : 0 Current address: 00:1f:12:bc:4a:96 Last flapped : 2012-06-29 15:35:29 PDT (2d 16:24 ago) Input rate : 0 bps (0 pps) Output rate : 0 bps (0 pps) SONET alarms : LOL, LOS SONET defects : LOL, LOS, LOP, BERR-SF, RDI-P VPI 0 Flags: Active Total down time: 0 sec, Last down: Never Traffic statistics: Input packets: 0 Output packets: 0 VPI 2 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/1. The Active flag for VPI 0 and VPI 2 indicates that these virtual paths are up and operational.
Verifying the Static PPPoA Configuration on Logical Unit 0
Purpose
Verify that the static PPP subscriber interface is properly configured on logical unit 0 (at-1/0/1.0).
Action
From operational mode, issue the show interfaces at-1/0/1.0 command.
user@host> show interfaces at-1/0/1.0
Logical interface at-1/0/1.0 (Index 337) (SNMP ifIndex 1979) Flags: Device-Down Point-To-Point Inverse-ARP SNMP-Traps 0x4000 Encapsulation: ATM-PPP-LLC Input packets : 0 Output packets: 0 Keepalive settings: Interval 5 seconds, Up-count 6, Down-count 4 Keepalive: Input: 0 (never), Output: 0 (never) LCP state: Down NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured, mpls: Not-configured CHAP state: Closed PAP state: Closed Protocol inet, MTU: 2034 Flags: Sendbcast-pkt-to-re, Protocol-Down Addresses, Flags: Dest-route-down Is-Preferred Is-Primary Destination: 192.122.13.12/30, Local: 192.122.13.13, Broadcast: 192.122.13.15 VCI 0.120 Flags: Active, Inverse-ARP Total down time: 0 sec, Last down: Never ARP statistics Received: 0, Sent: 0, Denied: 0, Operation not supported: 0, Bad packet length: 0, Bad protocol: 0, Bad protocol length: 0, Bad hardware length: 0, Dropped: 0 Last received: Never, Last sent: Never Input packets : 0 Output packets: 0
Meaning
ATM-PPP-LLC in the Encapsulation field indicates that logical interface at-1/0/1.0 is properly configured for PPP-over-AAL5 logical link control (LLC) encapsulation. Protocol inet indicates that the IPv4 protocol family has been properly configured on the logical interface. The Active flag for VCI 0.120 indicates that virtual circuit identifier (VCI) 120 on VPI 0 is up and operational.
Verifying the Static PPPoA Configuration on Logical Unit 1
Purpose
Verify that the static PPP subscriber interface is properly configured on logical unit 1 (at-1/0/1.1).
Action
From operational mode, issue the show interfaces at-1/0/1.1 command.
user@host> show interfaces at-1/0/1.1
Logical interface at-1/0/1.1 (Index 338) (SNMP ifIndex 1980) Flags: Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-PPP-VCMUX Input packets : 0 Output packets: 0 Keepalive settings: Interval 6 seconds, Up-count 6, Down-count 4 Keepalive: Input: 0 (never), Output: 0 (never) LCP state: Down NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured, mpls: Not-configured CHAP state: Closed PAP state: Closed Protocol inet, MTU: 2038 Flags: Sendbcast-pkt-to-re, Protocol-Down Addresses, Flags: Dest-route-down Is-Preferred Is-Primary Destination: 192.122.14.12/30, Local: 192.122.14.13, Broadcast: 192.122.14.15 VCI 2.120 Flags: Active, Inverse-ARP Total down time: 0 sec, Last down: Never ARP statistics Received: 0, Sent: 0, Denied: 0, Operation not supported: 0, Bad packet length: 0, Bad protocol: 0, Bad protocol length: 0, Bad hardware length: 0, Dropped: 0 Last received: Never, Last sent: Never Input packets : 0 Output packets: 0
Meaning
ATM-PPP-VCMUX in the Encapsulation field indicates that the logical interface at-1/0/1.1 is properly configured for PPP-over-AAL5 VC multiplexing encapsulation. Protocol inet indicates that the IPv4 protocol family has been properly configured on the logical interface. The Active flag for VCI 2.120 indicates that virtual circuit identifier (VCI) 120 on VPI 2 is up and operational.
Verifying the Static PPPoA Configuration on Logical Unit 2
Purpose
Verify that the static PPP subscriber interface is properly configured on logical unit 2 (at-1/0/1.2).
Action
From operational mode, issue the show interfaces at-1/0/1.2 command.
user@host> show interfaces at-1/0/1.2
Logical interface at-1/0/1.2 (Index 339) (SNMP ifIndex 1981) Flags: Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: ATM-PPP-VCMUX Input packets : 0 Output packets: 0 Keepalive settings: Interval 5 seconds, Up-count 6, Down-count 4 Keepalive: Input: 0 (never), Output: 0 (never) LCP state: Down NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured, mpls: Not-configured CHAP state: Closed PAP state: Closed Protocol inet, MTU: 2038 Flags: Sendbcast-pkt-to-re, Protocol-Down Addresses, Flags: Dest-route-down Is-Preferred Is-Primary Destination: 192.122.15.12/30, Local: 192.122.15.13, Broadcast: 192.122.15.15 VCI 2.121 Flags: Active Total down time: 0 sec, Last down: Never Input packets : 0 Output packets: 0
Meaning
ATM-PPP-VCMUX in the Encapsulation field indicates that the logical interface at-1/0/1.2 is properly configured for PPP-over-AAL5 VC multiplexing encapsulation. Protocol inet indicates that the IPv4 protocol family has been properly configured on the logical interface. The Active flag for VCI 2.121 indicates that virtual circuit identifier 121 on VPI 2 is up and operational.
Related Documentation
- MX Series
- ATM for Subscriber Access Overview
- Configuring ATM for Subscriber Access
- Example: Configuring a Dynamic PPPoE Subscriber Interface over ATM
- Example: Configuring a Static PPPoE Subscriber Interface over ATM
- Example: Configuring a Static Subscriber Interface for IP Access over ATM
- Example: Configuring a Static Subscriber Interface for IP Access over Ethernet over ATM
Published: 2013-02-11
Supported Platforms
Related Documentation
- MX Series
- ATM for Subscriber Access Overview
- Configuring ATM for Subscriber Access
- Example: Configuring a Dynamic PPPoE Subscriber Interface over ATM
- Example: Configuring a Static PPPoE Subscriber Interface over ATM
- Example: Configuring a Static Subscriber Interface for IP Access over ATM
- Example: Configuring a Static Subscriber Interface for IP Access over Ethernet over ATM