Downloads |
 Feedback
|
Table Of Contents
Broadband Scalability and Performance
Finding Feature Information in This Module
PPP Sessions and L2TP Tunnel Scaling
Restrictions for PPP Sessions and L2TP Tunnel Scaling
Configuring the Cisco ASR 1000 Series Router for High Scalability
Configuring Call Admission Control
Monitoring PPP Sessions Using the SNMP Management Tools
Configuring the Access Interface Input and Output Hold Queue
Configuring the keepalive Command
Scaling the L2TP Tunnel Configurations
Using the cisco-avpair="lcp:interface-config" RADIUS Attribute
Enhancing the Scalability of Per-User Configurations
Setting the VRF and IP Unnumbered Interface Configurations in User Profiles
Setting the VRF and IP Unnumbered Interface Configurations in Virtual Interface Templates
Redefining User Profiles to Use the ip:vrf-id and ip:ip-unnumbered VSAs
Walk-by User Support for PWLAN in ISG
Restrictions for Walk-by Session Support for PWLAN in ISG
ISG Scaling to Support Lite Sessions
Feature Information for Broadband Scalability and Performance
Broadband Scalability and Performance
The infrastructure of a service provider must be capable of supporting the services that an enterprise customer or Internet service provider (ISP) wants to offer its subscribers. The service provider must also be able to scale up to an expanding subscriber base. You can configure the Cisco ASR1000 Series Routers for high broadband scalability.
Finding Feature Information in This Module
Your software release might 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 Broadband Scalability and Performance" 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
This guide provides information about the following topics:
•
PPP Sessions and L2TP Tunnel Scaling
•
•
•
PPP Sessions and L2TP Tunnel Scaling
The ASR 1000 Series Routers are deployed in a variety of broadband deployment models for terminating Point-to-Point Protocol (PPP) Sessions and initiating or terminating Layer 2 Tunneling Protocol (L2TP) tunnels. The maximum number of PPP sessions and L2TP tunnels is dependent on the hardware combination. Table 18 lists the hardware combinations and the maximum number of PPP sessions and L2TP tunnels that are supported in Cisco IOS XE Release 3.3. For information about the restrictions for PPP sessions and L2TP tunnel scaling, see the "Restrictions for PPP Sessions and L2TP Tunnel Scaling" section.
Table 18 Maximum Number of PPP Sessions and L2TP Tunnels Supported on ASR 1000 Hardware
1001
Integrated
ESP-2.5G or ESP-5G
8000
4000
1002
Integrated RP1
ESP-5G
12000
6000
1004, 1006
RP1
ESP-10G or ESP-20G
24000
12000
1004, 1006
RP2
ESP-20G
32000
16000
1004, 1006, 1013
RP2
ESP-40G
320001 , 48000, or 64000
64000
1 32000 session scaling with RP2 and ESP-40G is fully supported without any additional restrictions. For restrictions on 48000 and 64000 see the "Restrictions for PPP Sessions and L2TP Tunnel Scaling" section.
Table 19 lists the virtual circuit limits for ASR 1000 ATM SPAs, effective from Cisco IOS XE Release 3.5.
Restrictions for PPP Sessions and L2TP Tunnel Scaling
This section lists the restrictions for the PPP sessions and L2TP tunnel scalability.
•
•
–
–
–
Note
•
–
–
–
–
Note
•
–
–
–
–
Note
•
•
IP Sessions Scaling
The ASR 1000 Series Routers can be deployed as an IP session aggregator. The maximum number of IP sessions that can be supported depends on the hardware combination. Table 20 lists the hardware combination and the maximum number of IP sessions that are supported.
The session limits apply to all variety of IP session initiators: DHCP, unclassified Mac address, unclassified IP, and RADIUS proxy.
Note
Layer 4 Redirect Scaling
The ASR 1000 supports the ability to redirect IP traffic within an ISG traffic class. Layer 4 redirect scaling is performed by the Quantum Flow Processor (QFP). The scaling limits are dependent on the ESP. Table 21 lists the ESP and the default per-session limit.
Configuring the Cisco ASR 1000 Series Router for High Scalability
The Cisco ASR 1000 Series Routers provide powerful performance and scalability for embedded services.
To achieve maximum scaling on the 1001, 1002, and 1004 chassis, IOS software redundancy must be disabled. For more information about restrictions and limitations, see the "Restrictions for PPP Sessions and L2TP Tunnel Scaling" section.
To ensure high scalability on the Cisco ASR 1000 Series Router, perform the following configuration tasks:
•
•
•
•
•
Configuring Call Admission Control
The Call Admission Control (CAC) feature is configured to protect the ASR 1000 processing resources that must be configured. CAC can restrict the media bandwidth dedicated to active calls when CPU utilization exceeds the configured threshold.
This section provides the following examples for configuring CAC:
Example: Configuring a PPPoE Sessionrouter(config)# call admission new-modelrouter(config)# call admission limit 1000router(config)# call admission cpu-limit 80router(config)# call admission pppoe 10 1Example: Configuring a PPPoA Sessionrouter(config)# call admission new-modelrouter(config)# call admission limit 1000router(config)# call admission cpu-limit 80router(config)# call admission pppoa 10 1Example: Configuring a VPDN Sessionrouter(config)# call admission new-modelrouter(config)# call admission limit 1000router(config)# call admission cpu-limit 80router(config)# call admission vpdn 10 1Control Plane Policing
The Control Plane Policing feature allows you to configure a QoS filter that manages the traffic flow of control plane packets to protect the control plane of Cisco IOS XE routers and switches against reconnaissance and denial-of-service (DoS) attacks. The control plane thus helps maintain packet forwarding and protocol states despite an attack or heavy traffic load on the router or switch.
For examples about configuring the Control Plane Policing feature, see the "Control Plane Policing" section in the Quality of Service Solutions Configuration Guide located at:
VPDN Group Session Limiting
Using the Virtual Private Dialup Network (VPDN) Group Session Limiting feature, you can limit the number of VPDN sessions allowed per VPDN group. VPDN session limits can increase performance and reduce latency for routers that are otherwise forced to operate at high capacity.
For more information about VPDN Group Session Limiting, see the feature documentation at:
http://www.cisco.com/en/US/docs/ios-xml/ios/vpdn/configuration/xe-3s/vpd-tunnel-mgmt.html
PPPoE Session Limiting
The PPPoE Session Limit Support feature prevents the router from using too much memory for virtual access by limiting the number of PPPoE sessions that can be created on a router or on all Ethernet interfaces and subinterfaces as well as ATM interfaces and subinterfaces.
For more information about PPPoE session limiting, see the feature documentation at:
http://www.cisco.com/en/US/docs/ios-xml/ios/bbdsl/configuration/xe-3s/bba-limit-legcfg-xe.html
Monitoring PPP Sessions Using the SNMP Management Tools
To prevent the virtual access subinterfaces from being registered with the Simple Network Management Protocol (SNMP) functionality of the router and using up the memory, do not use the SNMP management tools of the router to monitor PPP sessions. Use SNMP views to isolate the bulk queries and accidental requests.
Use the no virtual-template snmp command to disable the SNMP management tools:
Router(config)# no virtual-template snmpConfiguring the Access Interface Input and Output Hold Queue
The default value of Gigabit Ethernet and 10 Gigabit Ethernet interfaces is 375 packets for the input and output hold queues. If the interfaces are required to handle a high rate of control packets, such as LCP, IPCP, PPP, L2TP, and DHCP, the default value may not be sufficient. To ensure high scalability, set the access interface input and output hold queue to 4096:
Router(config)# interface gig1/0/0Router(config-if)# hold-queue 4096 inConfiguring the keepalive Command
For PPP sessions, the keepalive command sets the keepalive timer for a specific interface. To ensure proper scaling and to minimize CPU utilization, set the timer for 60 seconds or longer. The default value is 10 seconds:
interface Virtual-Template1ip unnumbered Loopback1keepalive 60no peer default ip addressppp authentication pap
Note
Scaling the L2TP Tunnel Configurations
To prevent head-of-the-line blocking of the IP input process and save system resources, configure the vpdn ip udp ignore checksum command:
Router(config)# vpdn ip udp ignore checksumWhen you configure this command, the router directly queues the L2TP Hello packets and Hello acknowledgements to the L2TP control process. We recommend that you configure this command in all the scaled LAC and LNS L2TP tunnel configurations.
If you do not configure the vpdn ip udp ignore checksum command, the L2TP software sends the packets to UDP to validate the checksum. When too many packets are queued to the IP input process, the router starts Selective Packet Discard (SPD) mechanism that causes IP packets to be dropped.
Note
Using the cisco-avpair="lcp:interface-config" RADIUS Attribute
When you use the lcp:interface-config RADIUS attribute to reconfigure the virtual access subscriber interface, call setup rate could be reduced on the Cisco ASR 1000 Series Aggregation Services Routers because the lcp:interface-config command syntax includes an IOS interface configuration command. This command is any valid IOS command that can be applied to an interface. When the lcp:interface-config attribute is downloaded from the RADIUS server to the Cisco ASR 1000 Series Aggregation Services Routers, the command parser is activated to configure the interface according to AV-pair, determining if the option is valid and then applying the configuration to the virtual access interface (VAI).
The subscriber session scaling on the Cisco ASR 1000 Series Aggregation Services Routers is not impacted by using the lcp:interface-config RADIUS attribute any more than if the equivalent IOS interface command was applied directly onto the virtual-template configuration and was cloned onto the VAI using that method. Using either the lcp:interface-config RADIUS attribute or the virtual-template to apply configuration onto the VAI it is the type of configuration being applied which may in a few cases affect the maximum subscriber session scale of the Cisco ASR 1000 Series Aggregation Services Routers.
Enhancing the Scalability of Per-User Configurations
To enhance scalability of per-user configurations without changing the router configuration, use the ip:vrf-id and ip:ip-unnumbered RADIUS attributes. These per-user vendor-specific attributes (VSAs) are used to map sessions to VRFs and IP unnumbered interfaces. The VSAs are applied to virtual access subinterfaces and are processed during PPP authorization.
The ip:vrf-id attribute is used to map sessions to VRFs. Any profile that uses the ip:vrf-id VSA must also use the ip:ip-unnumbered VSA to install IP configurations on the VAI that is to be created. The PPP that is used on a VAI to be created requires the ip:ip-unnumbered VSA. An Internet Protocol Control Protocol (IPCP) session is not established if IP is not configured on the interface. You must configure either the ip address command or the ip unnumbered command on the interface so that these configurations are present on the VAI that is to be created. However, specifying the ip address and ip unnumbered commands on a virtual template interface is not required because pre-existing IP configurations, if any, are removed when the ip:ip-vrf VSA is installed on the VAI. Therefore, any profile that uses the ip:vrf-id VSA must also use the ip:ip-unnumbered VSA to install IP configurations on the VAI that is to be created.
These per-user VSAs can be applied to VAIs. Therefore, the per-user authorization process does not require the creation of full VAIs, which improves scalability.
Setting the VRF and IP Unnumbered Interface Configurations in User Profiles
Although the Cisco ASR 1000 Series Router continues to support the lcp:interface-config VSA, the ip:vrf-id and ip:ip-unnumbered VSAs provide another way to set the VRF and IP unnumbered interface configurations in user profiles. The ip:vrf-id and ip:ip-unnumbered VSAs have the following syntax:
Cisco:Cisco-AVpair = "ip:vrf-id=vrf-name"Cisco:Cisco-AVpair = "ip:ip-unnumbered=interface-name"You should specify only one ip:vrf-id and one ip:ip-unnumbered value in a user profile. However, if the profile configuration includes multiple values, the Cisco ASR 1000 Series Router applies the value of the last VSA received, and creates a virtual access subinterface. If the profile includes the lcp:interface-config VSA, the router always applies the value of the lcp:interface-config VSA.
Setting the VRF and IP Unnumbered Interface Configurations in Virtual Interface Templates
You can specify one VSA value in a user profile on RADIUS and another value locally in the virtual template interface. The Cisco ASR 1000 Series Router clones the template and then applies the values configured in the profiles it receives from RADIUS, resulting in the removal of any IP configurations when the router applies the profile values.
Redefining User Profiles to Use the ip:vrf-id and ip:ip-unnumbered VSAs
The requirement of a full virtual access interface when using the lcp:interface-config VSA in user profiles can result in scalability issues, such as increased memory consumption. This situation is especially true when the Cisco ASR 1000 Series Router attempts to apply a large number of per-user profiles that include the lcp:interface-config VSA. Therefore, when updating your user profiles, we recommend that you redefine the lcp:interface-config VSA to the scalable ip:vrf-id and ip:ip-unnumbered VSAs.
The following example shows how to redefine a VRF named newyork using the ip:vrf-id VSA:
Change:Cisco:Cisco-Avpair = "lcp:interface-config=ip vrf forwarding newyork"To:Cisco:Cisco-Avpair = "ip:vrf-id=newyork"The following example shows how to redefine the Loopback 0 interface using the ip:ip-unnumbered VSA.
Change:Cisco:Cisco-Avpair = "lcp:interface-config=ip unnumbered Loopback 0"To:Cisco:Cisco-Avpair = "ip:ip-unnumbered=Loopback 0"
Walk-by User Support for PWLAN in ISG
In public wireless LAN (PWLAN) setups, a high number of ISG sessions might be unauthenticated sessions from wireless devices that do not use the PWLAN service. These sessions are referred to in this document as walk-by sessions, and users that use these sessions are referred to as walk-by users.
Walk-by sessions, if not dealt with in an optimized way, may consume a large portion of the hardware resources. This resource utilization may lead to an increase in the number of ISG routers required for a given PWLAN deployment. The concept of light-weight sessions is introduced to provide an optimization for walk-by sessions.
The features for walk-by users are configured on a default session acting as a template. Walk-by users are then assigned light-weight sessions that inherit features from a default session. The features are configured only once on the default session, thereby optimizing the resource usage.
A lite session is a light-weight unauthenticated ISG session that inherits default session services. Lite sessions are created on ISG to support walk-by users and optimize resource usage. A timer may be specified to limit the duration for which the lite session can utilize the public wireless LAN (PWLAN) services while remaining unauthenticated.
Restrictions for Walk-by Session Support for PWLAN in ISG
The restriction pertaining to the Walk-by Session Support for PWLAN in ISG feature includes:
•
Note
http://www.cisco.com/en/US/docs/ios-xml/ios/isg/configuration/xe-3s/isg-wlkby-supp.html
ISG Scaling to Support Lite Sessions
This section provides the ISG scaling numbers for supporting walk-by session.
Table 22 lists the hardware combinations and scale numbers for authenticated and walk-by users.
The scale numbers provided in the Table 22 assume the following reference configuration:
•
•
Any deviation from the conditions mentioned above may result in different scale numbers.
Table 22 ISG Scaling Numbers
RP2/ESP40
128 K
48 K
135
15
RP2/ESP100
224 K
48 K
135
15
1 For a redundant system, after a route processor (RP) switchover, the existing configuration in a forwarding processor (FP) takes some time to be cleaned up while new configuration (for walk-by users) is applied at a faster rate. In this scenario, if the system operates at the maximum scale before the switchover, the system might exceed the resource limit. Therefore, it is advisable to run a redundant system at a reduced scale.
2 The calls-per-second rates mentioned in the Table 22 are the target-sustained rates. However, after events such as failover or reload, the rates might exceed these numbers for some period before falling back to the sustained values.
Additional References
Related Documents
Standards
MIBs
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at this URL:
RFCs
Technical Assistance
Feature Information for Broadband Scalability and Performance
Table 23 lists the features in this module and provides links to specific configuration information.
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
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.
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
Copyright © 2008 - 2013 Cisco Systems, Inc. All rights reserved.
