Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

First Published: February 3, 2003
Last Updated: March 28, 2011

The PPPoA/PPPoE Autosense for ATM PVCs feature enables a router to distinguish between incoming PPP over ATM (PPPoA) and PPP over Ethernet (PPPoE) over ATM sessions and to create virtual access based on demand for both PPP types.

The Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs feature enhances PPPoA/PPPoE autosense functionality by providing autosense support on multiplexer (MUX) and Subnetwork Access Protocol (SNAP)-encapsulated ATM permanent virtual circuits (PVCs).

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs" section.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Restrictions for Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

•Information About Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

•How to Configure PPPoA/PPPoE Autosense on ATM PVCs

•Configuration Examples for Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

•Additional References

•Feature Information for Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

•Glossary

Restrictions for Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

•Do not use this feature on a router that initiates PPPoA sessions.

•PPPoA does not support static IP assignments within virtual templates.

•The PPPoE autosense is supported only for SNAP-encapsulated sessions.

•This feature supports ATM PVCs. Switched virtual circuits (SVCs) are not supported.

Information About Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

•PPPoA/PPPoE Autosense

•Autosense of MUX/SNAP Encapsulation on ATM PVCs

•Benefits of Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

PPPoA/PPPoE Autosense

PPPoA/PPPoE autosense enables a router to distinguish between incoming PPPoA and PPPoE over ATM sessions and to create virtual access based on demand for both PPP types.

Autosense of MUX/SNAP Encapsulation on ATM PVCs

The Autosense of MUX/SNAP Encapsulation on ATM PVCs feature enables the PVC encapsulation type to be autosensed by the router. The router determines the encapsulation type of a PVC by looking at the encapsulation type of the first incoming packet. If the PVC encapsulation type is changed while the PPPoA or PPPoE session on the network access server (NAS) is still up, the incoming packet is dropped, the encapsulation type is reset to autosense, and all sessions are removed from the PVC. The next incoming packet will then determine the new encapsulation type of the PVC.

Benefits of Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

The Autosense of PPPoA/PPPoE for MUX or SNAP Encapsulation feature provides resource allocation on demand. For each PVC configured for both PPPoA and PPPoE, certain resources (including one virtual-access interface) are allocated upon configuration, regardless of the existence of a PPPoA or PPPoE session on that PVC. With the Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs feature, resources are allocated for PPPoA and PPPoE sessions only when a client initiates a session, thus reducing overhead on the network access server (NAS).

This feature also saves configuration time by eliminating the need to specify the encapsulation type when ATM PVCs are being provisioned and by eliminating the need to manually provision ATM PVCs each time the encapsulation type changes.

How to Configure PPPoA/PPPoE Autosense on ATM PVCs

•Configuring PPPoA/PPPoE Autosense on a PVC (required)

•Configuring PPPoA/PPPoE Autosense on a VC Class (required)

•Troubleshooting Tips (optional)

•Monitoring and Maintaining PPPoA/PPPoE Autosense for ATM PVCs (optional)

Configuring PPPoA/PPPoE Autosense on a PVC

Perform this task to configure PPPoA/PPPoE Autosense on a PVC.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface atm number[.subinterface-number {multipoint | point-to-point}]

4. pvc [name] vpi/vci

5. encapsulation aal5autoppp virtual-template number

6. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

interface atm number[.subinterface-number {multipoint | point-to-point}]

Example:

Router(config)# interface atm 2/2/0.2 multipoint

Specifies the ATM interface and optional subinterface and enters subinterface configuration mode.

Step 4 

pvc [name] vpi/vci

Example:

Router(config-subif)# pvc pvc1 45/54

Configures a PVC on the ATM interface or subinterface and enters ATM VC configuration mode.

Step 5 

encapsulation aal5autoppp virtual-template number

Example:

Router(config-if-atm-vc)# encapsulation aal5autoppp virtual-template 3

Configures PPPoA/PPPoE autosense on the PVC.

•Also specifies the virtual template interface to use to clone the new virtual-access interfaces for PPP sessions on this PVC.

Step 6 

end

Example:

Router(config-if-atm-vc)# end

Ends the session and enters privileged EXEC mode.

Configuring PPPoA/PPPoE Autosense on a VC Class

Note Virtual-access interfaces for PPPoE sessions are cloned from the virtual template interface specified in the virtual private dialup network (VPDN) group.

Perform this task to configure PPPoA/PPPoE autosense on a VC class.

SUMMARY STEPS

1. enable

2. configure terminal

3. vc-class atm vc-class-name

4. encapsulation aal5autoppp virtual-template number

5. exit

6. interface atm number[.subinterface-number {multipoint | point-to-point}]

7. class-int vc-class-name

8. end

9. show running-config

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

configure terminal

Example:

Router# configure terminal

Enters global configuration mode.

Step 3 

vc-class atm vc-class-name

Example:

Router(config)# vc-class atm vc1

Creates and names a map class and enters VC class configuration mode.

Step 4 

encapsulation aal5autoppp virtual-template number

Example:

Router(config-vc-class)# encapsulation aal5autoppp virtual-template 4

Configures PPPoA/PPPoE autosense.

•Also specifies the virtual template interface to use to clone the new virtual-access interfaces for PPP sessions on this PVC.

Step 5 

exit

Example:

Router(config-vc-class)# exit

Returns to global configuration mode.

Step 6 

interface atm number[.subinterface-number {multipoint | point-to-point}]

Example:

Router(config)# interface atm 2/2/0.2 multipoint

Specifies the ATM interface and enters subinterface configuration mode.

Step 7 

class-int vc-class-name

Example:

Router(config-subif)# class-int vc1

Applies the VC class to all VCs on the ATM interface or subinterface.

Step 8 

end

Example:

Router(config-subif)# end

Ends the session and enters privileged EXEC mode.

Step 9 

show running-config

Example:

Router#  show running-config

Verifies whether the PPPoA/PPPoE autosense configuration is successful.

Troubleshooting Tips

To troubleshoot PPP sessions establishment, use the following commands:

•debug ppp authentication

•debug ppp negotiation

To troubleshoot the establishment of PPP sessions that are authenticated by a RADIUS or TACACS server, use the following commands:

•debug aaa authentication

•debug aaa authorization

Caution Use debug commands with extreme caution because they are CPU-intensive and can seriously impact your network.

Monitoring and Maintaining PPPoA/PPPoE Autosense for ATM PVCs

Perform this task to monitor and maintain PPPoA/PPPoE autosense for ATM PVCs. The show commands can be used in any order.

SUMMARY STEPS

1. enable

2. show atm pvc [ppp]

3. show caller

4. show interface virtual-access interface-number

5. show user

6. show vpdn

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2 

show atm pvc [ppp]

Example:

Router# show atm pvc ppp

Checks that the PVC contains the PPPoA session after the client at the other end of the PVC has initiated a PPPoA session.

Step 3 

show caller

Example:

Router# show caller

Displays caller information.

•Use this command to:

–Display individual users and consumed resources on the NAS.

–Inspect active call statistics for large pools of connections. (The debug commands produce too much output and tax the CPU too heavily.)

–Display the absolute and idle times for each user. The current values for both of these settings are displayed on the tty line and the asynchronous interface. Users that have been idle for unacceptably long periods of time can be easily identified. You can use this information to define timeout policies and multiple grades of services for different users.

Step 4 

show interface virtual-access interface-number

Example:

Router# show interface virtual-access 1

Displays information about the virtual-access interface, link control protocol, protocol states, and interface statistics.

•The status of the virtual-access interface should read: Virtual-Access3 is up, line protocol is up

Step 5 

show user

Example:

Router# show user

Displays information about the active lines on the router.

Step 6 

show vpdn

Example:

Router# show vpdn

Displays basic information about all active VPDN tunnels.

Configuration Examples for Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

•Example: PPPoA/PPPoE Autosense on an ATM PVC

•Example: PPPoA/PPPoE Autosense on a VC Class

•Example: PPPoA/PPPoE Autosense on Multiple VC Classes and Virtual Templates

Example: PPPoA/PPPoE Autosense on an ATM PVC

The following example shows how to configure the NAS with PPPoA/PPPoE autosense on PVC 30/33: 

! Configure PPP Autosense 

!

interface atm 0/0/0.33 multipoint

 pvc 30/33 

  encapsulation aal5autoppp virtual-template 1

  protocol pppoe

!

interface virtual-template 1

 ip unnumbered fastethernet 0/0/0

 ip route-cache cef

!

interface fastethernet 0/0/0

 ip address 10.1.1.1 255.255.255.0

!

Example: PPPoA/PPPoE Autosense on a VC Class

The following example shows how to configure the NAS with PPPoA/PPPoE autosense on the VC class called MyClass. The MyClass VC class applies PPPoA/PPPoE autosense to all PVCs on the ATM 0/0/0.99 interface. 

! Configure PPP Autosense

!

vc-class atm MyClass

 encapsulation aal5autoppp virtual-template 1

!

interface atm 0/0/0.99 multipoint

  class-int MyClass

  no ip directed-broadcast

  pvc 20/40

  pvc 30/33 

  protocol pppoe

!

interface virtual-template 1

  ip unnumbered fastethernet 0/0/0

  ip route-cache cef

!

interface fastethernet 0/0/0

 ip address 10.1.1.1 255.255.255.0

!

Example: PPPoA/PPPoE Autosense on Multiple VC Classes and Virtual Templates

The following example shows how to handle PPPoA and PPPoE sessions separately using two virtual templates: 

interface atm 0/0/0.3 multipoint

 no ip directed-broadcast

 class-int pppauto

!

interface atm 0/0/0.9 multipoint

 ip address 10.16.40.1 255.255.0.0

 no ip directed-broadcast

!

interface virtual-template 1

 ip unnumbered atm 0/0/0.9

 ip route-cache cef

 no ip directed-broadcast

 peer default ip address pool pool-1

 ppp authentication pap

!

interface virtual-template 2

 ip unnumbered atm 0/0/0.9

 ip route-cache cef

 no ip directed-broadcast

 peer default ip address pool pool-2

 ppp authentication chap

!

interface fastethernet 0/0/0

 ip address 10.1.1.1 255.255.255.0

!

vc-class atm pppauto

 encapsulation aal5autoppp virtual-template 2

!

Note Whenever possible, configure PPPoA and PPPoE to use the same virtual template. Using separate virtual templates leads to the inefficient use of virtual access because the maximum number of virtual-access interfaces will have to be precloned twice: once for PPPoE and once for PPPoA. If PPPoA and PPPoE use the same virtual template, the maximum number of virtual-access interfaces can be precloned once and used for PPPoA and PPPoE as needed.

Additional References

Related Documents

Related Topic
Document Title

Cisco IOS commands

Cisco IOS Master Commands List, All Releases

ATM commands: complete command syntax, defaults, command mode, command history, usage guidelines, and examples.

Cisco IOS Asynchronous Transfer Mode Command Reference

WAN commands: complete command syntax, defaults, command mode, command history, usage guidelines, and examples.

Cisco IOS Wide-Area Networking Command Reference


Standards

Standard
Title

None

—


MIBs

MIB
MIBs Link

None

To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs


RFCs

RFC
Title

None

—


Technical Assistance

Description
Link

The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html


Feature Information for Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

Table 1 lists the release history for this feature.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Table 1 Feature Information for Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

Feature Name
Releases
Feature Information

PPPoA/PPPoE Autosense for ATM PVCs

Cisco IOS XE Release 3.3S

The PPPoA/PPPoE Autosense for ATM PVCs feature enables a router to distinguish between incoming PPP over ATM (PPPoA) and PPP over Ethernet (PPPoE) over ATM sessions and to create virtual access based on demand for both PPP types.

The following sections provide information about this feature:

•Configuring PPPoA/PPPoE Autosense on a PVC

•Configuring PPPoA/PPPoE Autosense on a VC Class

Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs

Cisco IOS XE Release 3.3S

The Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs feature enhances PPP over ATM (PPPoA)/PPP over Ethernet (PPPoE) autosense functionality by providing autosense support on MUX- and SNAP-encapsulated ATM permanent virtual circuits (PVCs).

The following sections provide information about this feature:

•Configuring PPPoA/PPPoE Autosense on a PVC

•Configuring PPPoA/PPPoE Autosense on a VC Class

The following command was introduced or modified: encapsulation aal5autoppp virtual-template.


Glossary

cloning—Creating and configuring a virtual-access interface by applying a specific virtual template interface. The template is the source of the generic user information and router-dependent information. The result of cloning is a virtual-access interface configured with all the commands in the template.

LCP—Link Control Protocol. Protocol that establishes, configures, and tests data-link connections for use by PPP.

NAS—network access server. A device providing local network access to users across a remote access network such as the public switched telephone network (PSTN).

PPP—Point-to-Point Protocol. A protocol that encapsulates network layer protocol information over point-to-point links. PPP is defined in RFC 1661.

PPPoA—PPP over ATM.

PPPoE—PPP over Ethernet.

precloning—Cloning a specified number of virtual-access interfaces from a virtual template at system startup or when the command is configured.

PVC—permanent virtual circuit (or connection). Virtual circuit that is permanently established. PVCs save bandwidth associated with circuit establishment and teardown in situations where certain virtual circuits must exist all the time. In ATM terminology, called a permanent virtual connection.

VC—virtual channel. Logical circuit created to ensure reliable communication between two network devices. A VC is defined by a VPI/VCI pair and can be either permanent (PVC) or switched (SVC).

virtual-access interface—Instance of a unique virtual interface that is created dynamically and exists temporarily. Virtual-access interfaces can be created and configured differently by different applications, such as virtual profiles and virtual private dialup networks. Virtual-access interfaces are cloned from virtual template interfaces.

virtual template interface—A logical interface configured with generic configuration information for a specific purpose or configuration common to specific users, plus router-dependent information. The template takes the form of a list of Cisco IOS interface commands that are applied to virtual-access interfaces, as needed.

VPDN—virtual private dialup network. A system that permits dial-in networks to exist remotely from home networks, while giving the appearance of being directly connected.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2003-2011 Cisco Systems, Inc. All rights reserved.