Important: This PDG/TTG software release provides TTG functionality only. PDG functionality is not supported in this release.
•
•
• System Management Cards (SMCs): Provides full system control and management of all cards within the ASR 5000. Up to two SMC can be installed; one active, one redundant.
• Packet Services Cards (PSCs/PSC2s): Within the ASR 5000, PSCs/PSC2s provide high-speed, multi-threaded PDP context processing capabilities for 2.5G SGSN, 3G SGSN, and GGSN services. Up to 14 PSCs/PSC2s 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.
• Ethernet 10/100 and/or Ethernet 1000 Line Cards: Installed directly behind PSCs, these cards provide the physical interfaces to elements in the operator’s network. Up to 26 line cards should be installed for a fully loaded system with 13 active PSCs/PSC2s, 13 in the upper-rear slots and 13 in the lower-rear slots for redundancy. Redundant PSCs/PSC2s do 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 and every PSC/PSC2 in the system for redundancy. Two RCCs can be installed to provide redundancy for all line cards and PSCs/PSC2s.Important: Additional information pertaining to each of the application and line cards required to support GPRS/UMTS wireless data services is located in the Hardware Platform Overview chapter of the Product Overview Guide.
•
•
• Configure the IPv4 address for the service: This is the IP address of the TTG to which the UEs in the WLAN attempt to connect. The UEs send IKEv2 messages to this IP address, and the TTG uses the IP address to listen for these messages.
• Configure the name of the crypto template for IKEv2/IPSec: A crypto template is used to define an IKEv2/IPSec policy. It includes IKEv2 and IPSec parameters for keepalive, lifetime, NAT-T, and cryptographic and authentication algorithms. There must be one crypto template per PDG service.
• The name of the EAP profile: The EAP profile defines the EAP methods and associated parameters.
• Multiple authentication support: Multiple authentication is specified as a part of crypto template configuration.
• IKEv2 and IPSec transform sets: Transform set defines the negotiable algorithms for IKE SAs and Child SAs.
• The setup timeout value: This parameter specifies the session setup timeout timer value. The TTG terminates a UE connection attempt if the UE does not establish a successful connection within the specified timeout period.
• Max-sessions: This parameter sets the maximum number of subscriber sessions allowed by this PDG service.
• SGTP context and service: You create an SGTP context and service to enable GPRS Tunneling Protocol (GTP) on the TTG to use for sending packet data between the TTG and the GGSN.
• IKEv2 encryption protocols: AES-CBC with 128 bits, AES-CBC with 256 bits, 3DES-CBC, and DES-CBC
• IKEv2 pseudo-random functions: PRF-HMAC-SHA1, PRF-HMAC-MD5
• IKEv2 integrity: HMAC-SHA1-96, HMAC-MD5
• IKEv2 Diffie-Hellman groups: 1, 2, 5, and 14
• IPSec ESP (Encapsulating Security Payload) encryption: AES-CBC with 128 bits, AES-CBC with 256 bits, 3DES-CBC, and DES-CBC
• IPSec integrity: HMAC-SHA1-96, HMAC-MD5
• Committed Data Rate (CDR): The guaranteed rate (in bits per second) at which packets can be transmitted/received for the subscriber during the sampling interval. Note that the committed (or guaranteed) data rate does not apply to the Interactive and Background traffic classes.
• Peak Data Rate (PDR): The maximum rate (in bits per second) that subscriber packets can be transmitted/received for the subscriber during the sampling interval.
• 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.In the PDG Service Configuration Mode of the system’s CLI, you use the ip qos-dscp command to control DSCP markings for downlink packets sent over the Wu interface in IPSec tunnels, and use the ip gnp-qos-dscp command to control DSCP markings for uplink packets sent over the Gn' interface in GTP tunnels.
In the PDG Service Configuration Mode of the system’s CLI, the max-tunnels-per-ue command can be used to specify the maximum number of IKEv2/IPSec tunnels per subscriber session.Important: For more information on AAA configuration, refer to the AAA Interface Administration and Reference.
For more information about the Lawful Intercept feature, see the Lawful Intercept Configuration Guide.Important: For more information about session recovery support, refer to Session Recovery in the System Enhanced Feature Configuration Guide.
• 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 System Enhanced Feature Configuration Guide.
• System: Provides system-level statistics
• Card: Provides card-level statistics
• Port: Provides port-level statistics
• PDG: Provides PDG service statistics
• APN: Provides Access Point Name statisticsImportant: For more information on bulk statistic configuration, refer to the Configuring and Maintaining Bulk Statistics chapter of 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. Generation of specific traps can be enabled or disabled on the chassis. Ensuring that only important faults get displayed. SNMP traps are supported in both Alert and Alarm modes.
• 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 messages pertaining to the condition of a monitored value are generated with a severity level of WARNING. Logs are supported in both the Alert and the Alarm models.
• 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 to the Thresholding Configuration Guide.
•
•
•
•
![]() |
Cisco Systems Inc. |
Tel: 408-526-4000 |
Fax: 408-527-0883 |