PPPoE Smart Server Selection
First Published: April 18, 2008
Last Updated:
June 19, 2009
The 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 you to configure a specific PPP over Ethernet (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
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 XE 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
•Information About PPPoE Smart Server Selection
•How to Configure PPPoE Smart Server Selection
•Configuration Examples for PPPoE Smart Server Selection
•Additional References
•Feature Information for PPPoE Smart Server Selection
Information About PPPoE Smart Server Selection
To enable the PPPoE Smart Server Selection feature, you should understand the following concept:
•Benefits of PPPoE Smart Server Selection
Benefits of PPPoE Smart Server Selection
PPPoE Smart Server Selection provides the following benefits for the Internet service providers (ISPs):
•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 remote ID, circuit ID, and PPPoE service names.
•Restrict the service advertisements from a BRASs in a PADO message.
•Apply a PADO transmission delay based on circuit ID, remote ID, and service name.
•Do partial matching on service name, remote ID, and circuit ID.
How to Configure PPPoE Smart Server Selection
This section contains the following procedures:
•Configuring BBA Group PADO Delay (optional)
•Configuring PPPoE Service PADO Delay (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
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. •Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
bba-group pppoe {group-name | global}
Router(config)# bba-group pppoe server-selection |
Defines a PPP over Ethernet (PPPoE) profile, and enters BBA group configuration mode. •The global keyword creates a profile, which serves as the default profile for any PPPoE port that is not assigned a specific profile. |
Step 4 |
pado delay milliseconds
Router(config-bba-group)# pado delay 45 |
Sets the time by which a PADO response is delayed for a BBA group. Note Setting a value of 0 means no transmission delay. Setting a value of 9999 means setting an infinite time (PADO is never sent). |
Troubleshooting Tips
Use the debug pppoe command to troubleshoot the PPPoE session.
Configuring PADO Delay Based on 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, you 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 DETAILED STEPS table.
Perform this task to define 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] remote-id-string
6. pado delay circuit-id milliseconds
7. pado delay remote-id milliseconds
8. pado delay milliseconds
9. end
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. •Enter your password if prompted. |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
bba-group pppoe {group-name | global}
Router(config)# bba-group pppoe server-selection |
Defines a PPPoE profile, and enters BBA group configuration mode. •The global keyword creates a profile that serves as the default profile for any PPPoE port. |
Step 4 |
pppoe server circuit-id delay milliseconds string [contains] circuit-id-string
Router(config-bba-group)# pppoe server circuit-id delay 45 string circuit ATM1/0/0 VC 0/100 |
(Optional) Specifies the delay to be applied based on the PPPoE tag circuit ID from the client. •The contains keyword can find a partial match for this delay statement. •The value for the circuit-id-string argument can contain spaces when enclosed with double quotation marks (for example, " circuit ATM1/0/0 VC 0/100"). |
Step 5 |
pppoe server remote-id delay milliseconds string [contains] remote-id-string
Router(config-bba-group)# pppoe server remote-id delay 30 string XTH-TEST
|
(Optional) Specifies the delay to be applied based on the PPPoE tag remote ID from the client. •The contains keyword can find a partial match for this delay statement. •The value for the remote-id-string argument can contain spaces when enclosed with double quotation marks (for example, "subscr mac 1111.2222.3333"). |
Step 6 |
pado delay circuit-id milliseconds
Router(config-bba-group)# pado delay circuit-id 35 |
(Optional) Finds a match based on the PPPoE group circuit ID delay if configured. •If a circuit ID cannot be matched partially, a delay is applied based on any circuit ID that is present. |
Step 7 |
pado delay remote-id milliseconds
Router(config-bba-group)# pado delay remote-id 30 |
(Optional) Finds a match based on the PPPoE group remote ID delay if configured. |
Step 8 |
pado delay milliseconds
Router(config-bba-group)# pado delay 45 |
(Optional) Uses the group PADO delay configuration. •The PADO delay value is sought if the PADO delay is not found after several attempts. |
Step 9 |
end
Router(config-bba-group)# end |
Ends the configuration session and returns to privileged EXEC mode. |
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. exit
5. bba-group [global | profile-name]
6. virtual-template interface-number
7. service profile policymap-name refresh minutes
8. service name match
9. end
DETAILED STEPS
|
|
|
Step 1 |
enable
Router> enable |
Enables privileged EXEC mode. •Enter your password if prompted.5 |
Step 2 |
configure terminal
Router# configure terminal |
Enters global configuration mode. |
Step 3 |
policy-map type service policymap-name
Router(config)# policy-map type service serv3 |
Places the router in service policy map configuration mode, and defines the name of service policy map. |
Step 4 |
exit
Router(config)# exit |
Exits configuration mode and returns to EXEC command mode. |
Step 5 |
bba-group pppoe [global | profile-name]
Router(config-bba-group)# bba-group pppoe global |
Defines a PPPoE profile, and enters BBA group configuration mode. •The global keyword creates a profile that serves as the default profile for any PPPoE port. |
Step 6 |
virtual-template interface-number
(config-bba-group)# virtual-template 20 |
Specifies the virtual template interface number for the BBA group, and places the router in configuration BBA group mode. |
Step 7 |
service profile subscriber-profile-name refresh minutes
Router(config-bba-group)# service profile serv3 refresh 30 |
Specifies the subscriber profile to be associated with the BBA group, and the refresh interval minutes for the service profile. |
Step 8 |
service name match
Router(config-bba-group)# service name match |
Matches the requested tag for the PPPoE global group. Note The service name match command must be configured per the PPPoE service delay. The requested service by the client should also be configured on the BRAS to ensure PADO response from the BRAS. |
Step 9 |
end
(config-bba-group)# end |
Ends the configuration session and returns to privileged EXEC mode. |
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 provides the following configuration examples:
•Configuring BBA Group PADO Delay: Example
•Configuring PADO Delay: Example
•Configuring PPPoE Service PADO Delay
•Verifying the PPPoE Service Match and PADO Delay: Example
Configuring BBA Group PADO Delay: Example
The following example shows how to configure a BBA group for PADO delay:
Router(config)# bba-group pppoe server-selection
Router(config-bba-group)# pado delay 45
Configuring PADO Delay: Example
The following example shows how to match the string by using a circuit ID or remote ID delay configured for PPPoE server:
Router(config-bba-group)# pppoe server circuit-id delay 45 string "subscr mac
1111.2222.3333"
Router(config-bba-group)# pado delay circuit-id 35
Router(config-bba-group)# pado delay remote-id 30
The following example shows how to configure PADO delay based on the remote ID or circuit ID:
Router(config-bba-group)# pppoe server remote-id delay 20 string contains TEST
Router(config-bba-group)# pppoe server remote-id delay 10 string XTH
Router(config-bba-group)# pppoe server remote-id delay 30 string contains XTH-TEST
Generally, 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:
Router(config)# policy-map type service XTH-services
Router(config-service-policymap)# pppoe service ILoBr delay 1000
Router(config-service-policymap)# pppoe service xth-service1 delay 500
Router(config-service-policymap)# pppoe service service-nodelay
Router(config-service-policymap)# exit
Router(config)# bba-group pppoe server-selection
Router(config-bba-group)# service svc-group
Router(config-bba-group)# service profile XTH-services
Router(config-bba-group)# service name match
Router(config-bba-group)# virtual-template 1
Verifying the PPPoE Service Match and PADO Delay: 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 prints all the PPPoE services for the supported groups and also shows the associated delay for this service.
Router# show pppoe derived group svc-group
Derived configuration from subscriber profile 'XTH-services':
Service names: servicename:pado-delay
ILoBr:1000, xth-service1:500, service nodelay:0
Additional References
The following sections provide references related to the PPPoE Smart Server Selection feature.
Related Documents
Standards
MIBs
|
|
None |
To locate and download MIBs for selected platforms, Cisco IOS XE releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs |
RFCs
|
|
RFC 2516 |
A Method for Transmitting PPP over Ethernet (PPPoE) |
Technical Assistance
|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
http://www.cisco.com/techsupport |
Feature Information for PPPoE Smart Server Selection
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 Cisco IOS XE 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 XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.
Table 1 Feature Information for PPPoE Smart Server Selection
|
|
|
PPPoE Smart Server Selection |
Cisco IOS XE Release 2.4 |
PPPoE Smart Server Selection allows service providers to determine which Broadband Remote Access Server (BRAS) a PPP call will terminate on. |
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, 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, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, 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. (0903R)
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.
© 2008-2009 Cisco Systems, Inc. All rights reserved.