Table Of Contents
Prerequisites for PPPoE Smart Server Selection
Information About PPPoE Smart Server Selection
Benefits of PPPoE Smart Server Selection
How to Configure PPPoE Smart Server Selection
Configuring BBA Group PADO Delay
Configuring PADO Delay Based on a Remote-ID or Circuit-Id
Configuring PPPoE Service PADO Delay
Configuration Examples for PPPoE Smart Server Selection
Configuring BBA Group PADO Delay: Example
Configuring PADO Delay: Example
Configuring PPPoE Service PADO Delay: Example
Verifying the PPPoE Service Match and PADODelay: Example
Feature Information for PPPoE Smart Server Selection
PPPoE Smart Server Selection
First Published: April 18, 2008Last Updated: October 2, 2009The PPPoE Smart Server Selection feature allows service providers to determine which Broadband Remote Access Server (BRAS) a PPP call will terminate on.
The PPPoE Smart Server Selection feature allows the user to configure a specific PPPoE Active Discovery Offer (PADO) delay for a received PPPoE Active Discovery Initiation (PADI) packet. The PADO delay establishes the order in which the BRASs respond to PADIs by delaying their responses to particular PADIs by various times.
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 PPPoE Smart Server Selection" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS 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
•Prerequisites for PPPoE Smart Server Selection
•Information About PPPoE Smart Server Selection
•How to Configure PPPoE Smart Server Selection
•Configuration Examples for PPPoE Smart Server Selection
•Feature Information for PPPoE Smart Server Selection
Prerequisites for PPPoE Smart Server Selection
To enable the PPPoE Smart Server Selection feature, you must have Cisco IOS Release 12.2(33)SB or a later release installed on your system.
It is recommended that you be familiar with RFC 2516 before configuring this feature. For more information, see the "Additional References" section.
Information About PPPoE Smart Server Selection
To enable the PPPoE Smart Server Selection feature you must understand the following concept:
•Benefits of PPPoE Smart Server Selection
Benefits of PPPoE Smart Server Selection
The PPPoE Smart Server Selection feature allows Internet service providers (ISPs) to perform the following tasks:
•Optimize their networks by predicting and isolating PPP calls to terminate on a particular BRAS.
•Establish a priority order among the BRASs by configuring varying degrees of delays in the broadband access (BBA) groups on different BRASs.
•Use circuit-ID and remote-ID tag matching with strings up to 64 characters in length.
•Use spaces in circuit-id, remote-id and PPPoE service name.
•Restrict the service advertisements from a BRAS in a PADO message.
•Apply a PADO transmission delay based on circuit-ID, remote-ID, and service name.
•Do partial matching on circuit-id, remote-id and service name.
How to Configure PPPoE Smart Server Selection
This section contains the following procedures:
•Configuring BBA Group PADO Delay (optional)
•Configuring PADO Delay Based on a Remote-ID or Circuit-Id (optional)
•Configuring PPPoE Service PADO Delay (optional)
Configuring BBA Group PADO Delay
Perform this task to allow all calls coming into a defined BBA group on a BRAS to be treated with the same priority. All incoming sessions for a particular group would have their PADO responses delayed by the configured number of milliseconds.
This task allows ISPs to establish a priority order among the BRASs by configuring varying degrees of delays in the BBA groups on different BRASs.
SUMMARY STEPS
1. enable
2. configure terminal
3. bba-group pppoe {group-name | global}
4. pado delay milliseconds
DETAILED STEPS
Troubleshooting Tips
Use the debug pppoe command to troubleshoot the PPPoE session.
Configuring PADO Delay Based on a Remote-ID or Circuit-Id
This task uses the pppoe server command to define a list of circuit-id and remote-id tags on a BRAS for a particular BBA group. The pppoe delay command is extended to specify delays based on the PPPoE circuit-ID or remote-ID tag.
All incoming calls are scanned and if the circuit-ID or remote-ID tags in the PADI match the list on the BRAS, then the PADO response will be delayed by the configured delay time. If there is no delay defined based on the circuit-ID or remote-ID, the per-PPPoE service delay is sought. It it is not found, the delay for the BBA group PADO is used. If no PPPoE delay is found, the PADO is sent without delay.
If there is no match and a BBA group PADO delay is configured under the same BBA group, then the PADO response is delayed by the configured delay time for that BBA group. If a BBA group PADO delay is not configured, then the PADO response is sent immediately.
With PPPoE smart server selection, users can do a partial match for a configured string by using a
circuit-ID or remote-ID delay configured for the PPPoE server (Partial matching is searching for parts of strings. It is used to search for similar strings.) The preference for matching the string is described in the task table.The following task defines a list of circuit-ID and remote-ID tags on a BRAS for a particular BBA group and configures the delay associated with the circuit-ID and remote-ID tags.
SUMMARY STEPS
1. enable
2. configure terminal
3. bba-group pppoe {group-name | global}
4. pppoe server circuit-id delay milliseconds string [contains] circuit-id-string
5. pppoe server remote-id delay milliseconds string [contains] circuit-id-string
6. pado delay circuit-id milliseconds
7. pado delay remote-id milliseconds
8. pado delay milliseconds
9. end
DETAILED STEPS
Troubleshooting Tips
Use the debug pppoe event command to verify the smart server PADO delay selection.
Configuring PPPoE Service PADO Delay
Perform this task to specify a delay based on the PPPoE service. A delay is applied to the PADO offering based on the service name match.
SUMMARY STEPS
1. enable
2. configure terminal
3. policy-map type service policymap-name
4. pppoe service policymap-name [delay] seconds
5. exit
6. bba-group [global | profile-name]
7. virtual template interface-number
8. service profile policymap-name seconds
9. service name match
10. end
DETAILED STEPS
Troubleshooting Tips
Use the debug pppoe event command to verify the service name match and PADO delay for a PPPoE service.
Configuration Examples for PPPoE Smart Server Selection
This section contains the following examples:
•Configuring BBA Group PADO Delay: Example
•Configuring PADO Delay: Example
•Configuring BBA Group PADO Delay: Example
•Verifying the PPPoE Service Match and PADODelay: Example
Configuring BBA Group PADO Delay: Example
The following example shows how to configure a BBA group for PADO delay:
bba-group pppoe server-selectionpado delay 45
Configuring PADO Delay: Example
The following example shows how to match the a b c@example.com string by using a circuit-ID or remote-ID delay configured for a PPPoE server:
ppoe server circuit-id delay 45 string a b c@example.compado delay circuit-id 35pppoe server remote-id string remote1pado delay remote-id 30pado delay 0The following example shows how to configure PADO delay based on the remote-ID or circuit-ID:
pppoe server remote-id delay 20 string contains TESTpppoe server remote-id delay 10 string XTHpppoe server remote-id delay 30 string XTH-TESTpppoe delay remote-id 40pado delay 50Generally, the first match found in the list is considered for the delay value. If the remote-ID in the client PPPoE tag contains
"XTH-TEST", then the delay value is 20. In this case, the first match succeeds and the configuration never reaches a delay of 30. If the remote-ID in the client PPPoE tag contains"TH- no", then no match is found.Configuring PPPoE Service PADO Delay: Example
The following example shows how to configure the PADO delay based on the PPPoE service:
policy-map type service XTH-servicespppoe service ILoBr delay 1000pppoe service xth-service1 delay 500pppoe service service-nodelay!bba-group pppoe SVC-groupvirtual-template 1service profile XTH-services 3service name match!Verifying the PPPoE Service Match and PADODelay: Example
The following example shows the output of the service name match and PADO delay for a PPPoE service using the show pppoe derived group group-name command. This command displays all the PPPoE services for the supported groups and also shows the associated delay for this service.
Router# show pppoe derived group SVC-groupDerived configuration from subscriber profile 'XTH-services':Service names: (<servicename>:<pado-delay>)ILoBr:1000, xth-service1:500, service nodelay:0Additional References
The following sections provide references related to the PPPoE Smart Server Selection feature.
Related Documents
Standards
MIBs
MIB MIBs LinkNone
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for PPPoE Smart Server Selection
Table 1 lists the release history for this feature.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS 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 Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0908R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses or phone numbers. Any examples, command display output, and 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.
© 2008-2009 Cisco Systems, Inc. All rights reserved.