•
•
• For more information on authentication features, refer to the Network Access and Charging Management Features section in this overview.For more information on QoS features, refer to the Quality of Service Management Features section in this overview.For more information on policy and charging features, refer to the Network Access and Charging Management Features section in this overview.
•
• System Management Cards (SMCs): Provides full system control and management of all cards within the chassis. Up to two SMCs can be installed; one active, one redundant.
• Packet Services Cards (PSCs): The PSCs provide high-speed, multi-threaded PDP context processing capabilities for HSGW services. Up to 14 PSCs can be installed, allowing for multiple active and/or redundant cards.
• Switch Processor Input/Outputs (SPIOs): Installed in the upper-rear chassis slots directly behind the SMCs, SPIOs provide connectivity for local and remote management, central office (CO) alarms. Up to two SPIOs can be installed; one active, one redundant.
• Line Cards: Installed directly behind PSCs, these cards provide the physical interfaces to elements in the eHRPD data network. Up to 26 line cards can 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 not require line cards.
• Redundancy Crossbar Cards (RCCs): Installed in the lower-rear chassis slots directly behind the SPCs/SMCs, RCCs utilize 5 Gbps serial links to ensure connectivity between Ethernet 10/100 or Ethernet 1000 line cards 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 LTE/SAE services is located in the Hardware Platform Overview chapter of the Product Overview Guide.
STa InterfaceGxa InterfaceImportant: To configure the basic service and functionality on the system for the HSGW service, refer to the configuration examples provided in the HSGW Administration Guide.
Important: Registration Revocation functionality is also supported for Proxy Mobile IP. However, only the P-GW can initiate the revocation for Proxy-MIP calls. For more information on MIP registration revocation support, refer to the Mobile IP Registration Revocation chapter in the 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 PSC. In this mode, recovery is performed by using the mirrored “standby-mode” session manager task(s) running on active PSCs. The “standby-mode” task is renamed, made active, and is then populated using information from other tasks such as AAA manager.
• Full PSC recovery mode: Used when a PSC hardware failure occurs, or when a PSC migration failure happens. In this mode, the standby PSC is made active and the “standby-mode” session manager and AAA manager tasks on the newly activated PSC perform session recovery.Important: For more information on session recovery support, refer to the Session Recovery chapter in the System Enhanced Feature Configuration Guide.
Important: Due to additional memory requirements, this service can only be used with 8GB Packet Service Cards (PSCs).
Important: ITC includes the class-map, policy-map and policy-group commands. Currently ITC does not include an external policy server interface.
•
• Congestion Condition Thresholds: Thresholds dictate the conditions for which congestion control is enabled and establishes limits for defining the state of the system (congested or clear). These thresholds function in a way similar to operation thresholds that are configured for the system as described in the Thresholding Configuration Guide. The primary difference is that when congestion thresholds are reached, a service congestion policy and an SNMP trap, starCongestion, are generated.
• Port Utilization Thresholds: If you set a port utilization threshold, when the average utilization of all ports in the system reaches the specified threshold, congestion control is enabled.
• Port-specific Thresholds: If you set port-specific thresholds, when any individual port-specific threshold is reached, congestion control is enabled system-wide.
• Service Congestion Policies: Congestion policies are configurable for each service. These policies dictate how services respond when the system detects that a congestion condition threshold has been crossed.Important: For more information on congestion control, refer to the Congestion Control chapter in this guide.
Important: For more information on IP access control lists, refer to the IP Access Control Lists chapter in the System Enhanced Feature Configuration Guide.
•Important: P-GW management functionality is enabled by default for console-based access. For GUI-based management support, refer to the Web Element Management System section in this chapter. For more information on command line interface based management, refer to the Command Line Interface Reference and P-GW Administration Guide.
• System: Provides system-level statistics
• Card: Provides card-level statistics
• Port: Provides port-level statistics
• Context: Provides context-level statistics
• IP Pool: Provides IP pool statistics
• MAG: Provides Mobile Access Gateway statistics
• ECS: Provides Enhanced Charging Service statistics
• RADIUS: Provides AAA RADIUS statisticsImportant: For more information on bulk statistic configuration, refer to the Configuring and Maintaining Bulk Statistics chapter in the System Administration Guide.
• 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 WEM support, refer to the WEM Installation and Administration Guide.
Important: For more information on IP header compression support, refer IP Header Compression chapter in System Enhanced Feature Configuration Guide.
Important: For more information on IP header compression support, refer IP Header Compression chapter in System Enhanced Feature Configuration Guide.
Important: For more information on traffic policing and shaping, refer to the Traffic Policing and Shaping chapter in the System Enhanced Feature Configuration Guide.
• PDN Access: Subscriber IP traffic is routed over an IPSec tunnel from the system to a secure gateway on the packet data network (PDN) as determined by access control list (ACL) criteria.
• Mobile IP: Mobile IP control signals and subscriber data is encapsulated in IPSec tunnels that are established between foreign agents (FAs) and home agents (HAs) over the Pi interfaces.Important: Once an IPSec tunnel is established between an FA and HA for a particular subscriber, all new Mobile IP sessions using the same FA and HA are passed over the tunnel regardless of whether or not IPSec is supported for the new subscriber sessions. Data for existing Mobile IP sessions is unaffected.
Important: For more information on IPSec support, refer to the IP Security chapter in the System Enhanced Feature Configuration Guide.
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |