![]() |
Broadband Access Aggregation and DSL Configuration Guide, Cisco IOS Release 15S
|
||||||
PPP-Max-Payload and IWF PPPoE Tag Support
![]() |
|||||||
Contents
PPP-Max-Payload and IWF PPPoE Tag SupportLast Updated: December 12, 2012
The PPP-Max-Payload and IWF PPPoE Tag Support feature enables the Point-to-Point Protocol (PPP) over Ethernet (PPPoE) component to process the PPP-Max-Payload and Interworking Functionality (IWF) PPPoE tags in the PPPoE discovery frame:
Finding Feature InformationYour software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and 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 table at the end of this module. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Prerequisites for the PPP-Max-Payload and IWF PPPoE Tag Support FeatureTo enable the PPP-Max-Payload and IWF PPPoE Tag Support feature, you should have configured PPPoE profile. Restrictions for the PPP-Max-Payload and IWF PPPoE Tag Support FeaturePPPoE peers can negotiate only MRUs with a maximum of 1492 octets so that the PPPoE header and PPP protocol ID can be inserted in the PPPoE session data packet. Information About the PPP-Max-Payload and IWF PPPoE Tag Support FeatureAccommodating an MTU MRU Greater than 1492 in PPPoEPer the RFC, Accommodating an MTU/MRU Greater than 1492 in PPPoE, PPPoE peers can negotiate only MRUs with a maximum of 1492 octets so that the PPPoE header and PPP protocol ID can be inserted in the PPPoE session data packet. The maximum for an Ethernet payload is 1500 octets. RFC 2516 defines a new tag to allow PPPoE peers to negotiate PPP MRU greater than 1492 if the underlying networks can support an Ethernet payload of greater than 1500 bytes. To enable processing of this new tag, a command has been defined in the Cisco IOS command-line interface as tag ppp-max-payload.The PPP-Max-Payload and IWF PPPoE Tag Support feature enhances the PPPoE component so the tag ppp-max-payloadcommand can process the new tag to influence the Link Control Protocol (LCP) MRU negotiations for the PPP session based on the MRU value specified in the tag from the PPPoE client. Interworking FunctionalityThe DSL Forum defined IWF to define the process for conversion of PPP over ATM (PPPoA) sessions to PPPoE sessions at the digital subscriber line access multiplexer (DSLAM) to the BRAS. This functionality was defined to help the migration of DSLAM networks from ATM to Ethernet media. So, essentially, the PPPoA session comes in to the DSLAM over ATM and is converted to a PPPoE session at the DSLAM, which is then connected to the BRAS as a PPPoE session. Each PPPoA session is mapped to a corresponding PPPoE session. Typically, the BRAS is configured to limit PPPoE sessions originating from the same MAC address to protect itself from a DOS attack. This presents a problem for IWF PPPoE sessions because all PPPoE sessions originate from the same MAC address DSLAM. To overcome this issue, the IWF PPPoE tag is inserted at the DSLAM and read by the BRAS to distinguish the IWF PPPoE session from the regular PPPoE session during the PPPoE discovery frames. For more information about this subject, refer to the DSL Forum Technical Report 101: Migration to Ethernet-Based DSL Aggregation. How to Configure the PPP-Max-Payload and IWF PPPoE Tag Support Feature
Enabling the PPP-Max-Payload and IWF PPPoE Tag Support Feature
SUMMARY STEPS
DETAILED STEPS Disabling the PPP-Max-Payload and IWF PPPoE Tag Support FeatureThe tag ppp-max-payload command adjusts PPP MTU of the PPPoE session above the default maximum limit of 1492 bytes. But MTU values greater than 1492 can only be supported (with PPPoE) if the underlying Ethernet network supports these larger frames. Not all Ethernet networks support higher values. If your network does not support values higher than the default maximum, you should disable the PPP-Max-Payload and IWF PPPoE Tag Support feature by performing this task. DETAILED STEPS Configuration Examples for the PPP-Max Payload and IWF PPPoE Tag Support FeatureThis section provides a sample configuration showing the PPP-Max-Payload and IWF PPPoE Tag Support feature enabled and a configuration in which the effects of this feature are disabled:
Configuration with the PPP-Max-Payload and IWF PPPoE Tag Support Feature Enabled ExampleThe following configuration example shows the PPP-Max-Payload and IWF PPPoE Tag Support enabled to accept PPP-Max-Payload tag values from 1492 to 1892, limits the number of sessions per MAC address to 2000 when the IWF is present, and verifies that the PPP session can accept 1500-byte packets in both directions: bba-group pppoe global virtual-template 1 tag ppp-max-payload minimum 1492 maximum 1892 sessions per-mac limit 1 sessions per-mac iwf limit 2000 ! interface Virtual-Template 1 ! Additional ReferencesThe following sections provide references related to the PPP-Max-Payload and IWF PPPoE Tag Support feature. MIBsTechnical Assistance
Feature Information for PPP-Max Payload and IWF PPPoE Tag SupportThe following table provides release information about the feature or features described in this module. This table 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. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
GlossaryBBA --Broadband access. BRAS --Broadband Remote Access Server, typically acting as a PPPoE server. DOS --Denial of service (a form of security attacks). DSLAM --Digital subscriber line access multiplexer. IPCP --IP Control Protocol. IWF --Interworking Functionality (used to describe the PPPoA conversion to PPPoE sessions at the DSLAM). IWF PPPoE session --A PPPoE session from the DSLAM to the BRAS that is actually a PPPoA session from the end user to the DSLAM. LCP --Link Control Protocol. MRU --PPP maximum received unit as negotiated in LCP. MTU --Maximum transmission unit of an interface. PADO --PPPoE Active Discovery Offer. PADR --PPPoE Active Discovery Request. PADS --PPPoE Active Discovery Session Confirmation. PPP --Point-to-Point Protocol PPPoE --PPP over Ethernet protocol or PPPoE component. VPDN --virtual private dialup network. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R) 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. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||
|
|