•
• System Management Cards (SMCs): Provides full system control and management of all cards within the ASR 5000 platform. Up to two SMC can be installed; one active, one redundant.
• Packet Services Cards (PSCs): Within the ASR 5000 platform, PSCs provide high-speed, multi-threaded PPP processing capabilities to support either PDSN/FA or HA services. Up to 14 PSCs can be installed, allowing for multiple active and/or redundant cards.
• Switch Processor Input/Outputs (SPIO): Installed in the upper-rear chassis slots directly behind the SPCs/SMCs, SPIOs provide connectivity for local and remote management, Central Office (CO) alarms. Up to two SPIOs can be installed; one active, one redundant.
• Ethernet 10/100 and/or Ethernet 1000/Quad Gig-E Line Cards (QGLC): Installed directly behind PSCs, these cards provide the RP, AAA, PDN, and Pi interfaces to elements in the data network. Up to 26 line cards should be installed for a fully loaded system with 13 active PSCs, 13 in the upper-rear slots and 13 in the lower-rear slots for redundancy. Redundant PSCs do no not require line cards.
• Redundancy Crossbar Cards (RCCs): Installed in the lower-rear chassis slots directly behind the SMCs, RCCs utilize 5 Gbps serial links to ensure connectivity between Ethernet 10/100 or Ethernet 1000 line cards/QGLCs and every PSC in the system for redundancy. Two RCCs can be installed to provide redundancy for all line cards and PSCs.Important: Additional information pertaining to each of the application and line cards required to support CDMA2000 wireless data services is located in the Product Overview Guide.
Important: To configure the basic service and functionality on the system for PDSN service, refer configuration examples provide in the PDSN Administration Guide.
• Priority: Dictates the order in which the servers are used allowing for multiple servers to be configured in a single context.
• Routing Algorithm: Dictate the method for selecting among configured servers. The specified algorithm dictates how the system distributes AAA messages across the configured AAA servers for new sessions. Once a session is established and an AAA server has been selected, all subsequent AAA messages for the session will be delivered to the same server.Important: For more information on RADIUS AAA configuration, refer AAA Interface Administration and Reference.
Important: For more information on Access Control List configuration, refer IP Access Control List chapter in System Enhanced Feature Configuration Guide.
• IP Pool-based Next Hop Forwarding - Forwards data packets based on the IP pool from which a subscriber obtains an IP address.
• ACL-based Policy Forwarding - Forwards data packets based on policies defined in Access Control Lists (ACLs) and applied to contexts or interfaces.
• Subscriber specific Next Hop Forwarding - Forwards all packets for a specific subscriber.Important: Due to additional memory requirements, this service can only be used with 8GB Packet Accelerator Cards (PACs) or Packet Service Cards (PSCs)
Important: For more information on AAA Server Group configuration, refer AAA Interface Administration and Reference.
Important: For more information on IP pool overlapping configuration, refer VLANs chapter in System Enhanced Feature Configuration Guide.
• Static Routes: The system supports the configuration of static network routes on a per context basis. Network routes are defined by specifying an IP address and mask for the route, the name of the interface in the currant context that the route must use, and a next hop IP address.
• Open Shortest Path First (OSPF) Protocol version 2: A link-state routing protocol, OSPF is an Interior Gateway Protocol (IGP) that routes IP packets based solely on the destination IP address found in the IP packet header using the shortest path first. IP packets are routed “as is”, meaning they are not encapsulated in any further protocol headers as they transit the network.
• Border Gateway Protocol version 4 (BGP-4): The system supports a subset of BGP (RFC-1771, A Border Gateway Protocol 4 (BGP-4)), suitable for eBGP support of multi-homing typically used to support geographically redundant mobile gateways, is supported.
•
•
• Route Policy: Routing policies modify and redirect routes to and from the system to satisfy specific routing needs. The following methods are used with or without active routing protocols (i.e. static or dynamic routing) to prescribe routing policy:
• Route Access Lists: The basic building block of a routing policy, route access lists filter routes based upon a specified range of IP addresses.
• IP Prefix Lists: A more advanced element of a routing policy. An IP Prefix list filters routes based upon IP prefixes.
• AS Path Access Lists: A basic building block used for Border Gateway Protocol (BGP) routing, these lists filter Autonomous System (AS) paths.
• Route Maps: Route-maps are used for detailed control over the manipulation of routes during route selection or route advertisement by a routing protocol and in route redistribution between routing protocols. This detailed control is achieved using IP Prefix Lists, Route Access Lists and AS Path Access Lists to specify IP addresses, address ranges, and Autonomous System Paths.
• Equal Cost Multiple Path (ECMP): ECMP allows distribution of traffic across multiple routes that have the same cost to the destination. In this manner, throughput load is distributed across multiple path, typically to lessen the burden on any one route and provide redundancy. The mobile gateway supports from four to ten equal-cost paths.Important: For more information on IP Routing configuration, refer Routing chapter in System Enhanced Feature Configuration Guide.
•Important: For more information on command line interface based management, refer Command Line Interface Reference and PDSN Administration Guide.
• Card: Provides card-level statistics
• Port: Provides port-level statistics
• BCMCS: Provides BCMCS service statistics
• FA: Provides FA service statistics
• HA: Provides HA service statistics
• IP Pool: Provides IP pool statistics
• MIPv6HA: Provides MIPv6HA service statistics
• PPP: Provides Point-to-Point Protocol statistics
• RADIUS: Provides per-RADIUS server statistics
• ECS: Provides Enhanced Charging Service Statistics
• Alert: A value is monitored and an alert condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval.
• Alarm: Both high and low threshold are defined for a value. An alarm condition occurs when the value reaches or exceeds the configured high threshold within the specified polling interval. The alert is generated then generated and/or sent at the end of the polling interval.
• SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/or clear) of each of the monitored values.
• Logs: The system provides a facility called threshold for which active and event logs can be generated. As with other system facilities, logs are generated Log messages pertaining to the condition of a monitored value are generated with a severity level of WARNING.
• Alarm System: High threshold alarms generated within the specified polling interval are considered “outstanding” until a the condition no longer exists or a condition clear alarm is generated. “Outstanding” alarms are reported to the system's alarm subsystem and are viewable through the Alarm Management menu in the Web Element Manager.Important: For more information on threshold crossing alert configuration, refer Thresholding Configuration Guide.
Important: For more information on IP header compression support, refer IP Header Compression chapter in System Enhanced Feature Configuration Guide.
• Task recovery mode: Wherein one or more session manager failures occur and are recovered without the need to use resources on a standby PAC. In this mode, recovery is performed by using the mirrored “standby-mode” session manager task(s) running on active PACs. The “standby-mode” task is renamed, made active, and is then populated using information from other tasks such as AAA manager.
• Full PAC recovery mode: Used when a PAC hardware failure occurs, or when a PAC migration failure happens. In this mode, the standby PAC is made active and the “standby-mode” session manager and AAA manager tasks on the newly activated PAC perform session recovery.Important: For more information on session recovery support, refer Session Recovery chapter in System Enhanced Feature Configuration Guide.
Important: For more information on L2TP Access Concentrator support, refer L2TP Access Concentrator chapter in System Enhanced Feature Configuration Guide.
Important: For more information on L2TP LNS support support, refer L2TP Access Concentrator chapter in System Enhanced Feature Configuration Guide.
Important: For more information on Proxy Mobile IP configuration, refer Proxy Mobile IP chapter in System Enhanced Feature Configuration Guide.
Important: For more information on IPSec support, refer IP Security chapter in System Enhanced Feature Configuration Guide.
• Committed Data Rate (CDR): The guaranteed rate (in bits per second) at which packets may be transmitted/received for the subscriber during the sampling interval.
• Peak Data Rate (PDR): The maximum rate (in bits per second) that packets may be transmitted/received for the subscriber during the sampling interval.
• Burst-size: The maximum number of bytes that may be transmitted/received for the subscriber during the sampling interval for both committed (CBS) and peak (PBS) rate conditions. This represents the maximum number of tokens that can be placed in the subscriber's “bucket”. Note that the committed burst size (CBS) equals the peak burst size (PBS) for each subscriber.
• Drop: The offending packet is discarded.
• Transmit: The offending packet is passed.
• Lower the IP Precedence: The packet's ToS octet is set to “0”, thus downgrading it to Best Effort, prior to passing the packet.
• Buffer the Packet: The packet stored in buffer memory and transmitted to subscriber once traffic flow comes in allowed bandwidth.Important: For more information on per subscriber traffic policing and shaping, refer Traffic Policing and Shaping chapter in System Enhanced Feature Configuration Guide.
Important: For more information on intelligent traffic control support, refer Intelligent Traffic Control chapter in System Enhanced Feature Configuration Guide.
• Change of Authorization: The system supports CoA messages from the AAA server to change data filters associated with a subscriber session. The CoA request message from the AAA server must contain attributes to identify NAS and the subscriber session and a data filter ID for the data filter to apply to the subscriber session.
• Disconnect Message: The DM message is used to disconnect subscriber sessions in the system from a RADIUS server. The DM request message should contain necessary attributes to identify the subscriber session.Important: For more information on dynamic RADIUS extensions support, refer CoA, RADIUS, And Session Redirection (Hotlining) chapter in System Enhanced Feature Configuration Guide.
Important: Subscriber AAA interfaces should always be configured using Ethernet line card interfaces for the highest performance. The out-of-band local context should not be used for service subscriber AAA functions.
• Simple IP: The mobile user is dynamically assigned an IP address from the service provider. The user can maintain this address within a defined geographical area, but when the user moves outside of this area, their IP address will be lost. This means that whenever a mobile user moves to a new location, they will need to re-register with the service provider to obtain a new IP address.
• Mobile IP: The mobile subscriber uses either a static or dynamically assigned IP address that belongs to their home network. As the subscriber roams through the network, the IP address is maintained providing the subscriber with the opportunity to use IP applications that require seamless mobility such as performing file transfers.
• Proxy Mobile IP: Provides a mobility solution for subscribers whose Mobile Nodes (MNs) do not support the Mobile IP protocol. The PDSN/FA proxy the Mobile IP tunnel with the HA on behalf of the MS. The subscriber receives an IP address from either the service provider or from their home network. As the subscriber roams through the network, the IP address is maintained providing the subscriber with the opportunity to use IP applications that require seamless mobility such as transferring files.
Important: The chassis simultaneously supports GRE protocols with key in accordance with RFC-1701/RFC-2784 and “Legacy” GRE protocols without key in accordance to RFC-2002.
• Scenario 1: The AAA server specifies an IP address that the PDSN allocates to the MN from one of its locally configured static pools.
• Scenario 2: The HA assigns an IP address to the MN from one of its locally configured dynamic pools.
•
•
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |