Guest

Cisco LTE PDN Gateway

Release Notes for the Cisco LTE PDN Gateway Release 1.3.5 on the Cisco SAMI, Cisco IOS Release 12.4(24)T35c

  • Viewing Options

  • PDF (393.2 KB)
  • Feedback
Release Notes for Cisco LTE PDN Gateway Release 1.3.5 on the Cisco SAMI, Cisco IOS Software Release 12.4 (24)T35c

Table Of Contents

Release Notes for Cisco LTE PDN Gateway Release 1.3.5 on the Cisco SAMI,
Cisco IOS Software Release 12.4 (24)T35c

Contents

Cisco LTE PGW Overview

LTE Evolved Packet Core

Cisco LTE PGW Description

System Requirements

Memory Recommendations

Hardware and Software Requirements

Determining the Software Version

Upgrading to a New Software Release

MIBs

Limitations, Restrictions, and Important Notes

New and Changed Information

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T35c

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T34d

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3c

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3b

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3a1

Configuring Local Service Record Information Generation

Configuring Specification Compliance

Caveats

Caveats - Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c

Open Caveats

Resolved Caveats

Unreproducible Caveats

Caveats - Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d

Open Caveats

Resolved Caveats

Caveats - Cisco LTE PGW Release 1.3, Cisco IOS Release 12.4(24)T3c

Open Caveats

Resolved Caveats

Caveats - Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3b

Open Caveats

Resolved Caveats

Caveats - Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1

Open Caveats

Resolved Caveats

Caveats - Cisco LTE PGW Release 1.0, Cisco IOS Release 12.4(24)T3a

Open Caveats—Cisco LTE PGW

Open Caveats—Cisco SAMI

Related Documentation

Release-Specific Documents

Platform-Specific Documents

Documentation Modules

Implementing a Cisco LTE PGW Release 1.x on the Cisco SAMI

General Overview Documents

Documentation List by Task

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco LTE PDN Gateway Release 1.3.5 on the Cisco SAMI,
Cisco IOS Software Release 12.4 (24)T35c


June 22, 2011

Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c

This release note describes the requirements, dependencies, and caveats for the Cisco Long Term Evolution (LTE) Packet Data Network (PDN) Gateway (PGW) Release 1.x on the Cisco Service and Application Module for IP (SAMI). These release notes are updated as needed.

For a list of the software caveats that apply to Cisco LTE PGW, Cisco IOS Release 12.4(24)T3 releases, see the "Caveats" section and Caveats for Cisco IOS Release 12.4 T. The caveats document is updated for every maintenance release and is located on Cisco.com and the Documentation CD-ROM.

Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.4 located on Cisco.com.

Contents

This release note includes the following information:

Cisco LTE PGW Overview

System Requirements

MIBs

Limitations, Restrictions, and Important Notes

New and Changed Information

Caveats

Related Documentation

Implementing a Cisco LTE PGW Release 1.x on the Cisco SAMI

Obtaining Documentation and Submitting a Service Request

Cisco LTE PGW Overview

The following sections provide a brief overview of the Cisco LTE PGW:

LTE Evolved Packet Core

Cisco LTE PGW Description

LTE Evolved Packet Core

The Cisco LTE PGW is a service designed for LTE Evolved Packet Core (EPC). The EPC is the main component of the System Architecture Evolution (SAE). 3GPP designed SAE as a migration path for 3GPP systems. The SAE is the core network architecture of LTE communication.

The SAE is an evolution of the General Packet Radio Service (GPRS) and Universal Mobile Telecommunication System (UMTS) that provides a migration path for 3GPP systems with the following differences:

Simplified architecture

All IP network

Support for higher throughput and lower latency radio access networks (RANs)

Support for and mobility between 3GPP (GPRS, UMTS, and LTE) and non-3GPP access technologies.

The LTE EPC is made up of the following primary elements:

Mobility Management Entity (MME)

Serving Gateway (SGW)

Packet Data Network (PDN) Gateway (PGW)

Figure 1 shows the interworking (and interfaces) of the LTE EPC with different radio access technologies.


Note Cisco LTE PGW Release 1.x does not support the paths represented by dashed lines.


Figure 1 LTE Network Components with SGWs and PGWs Implemented on the Cisco Service and Application Module for IP in the Cisco 7600 Series Router

The following is a list of acronyms used in Figure 1.

Serving GPRS Support Node (SGSN)

UMTS Terrestrial Radio Access Network (UTRAN)

GSM EDGE Radio Access Network (GERAN)

Evolved UTRAN (E-UTRAN)

Mobility Management Entity (MME)

Serving Gateway (SGW)

PDN Gateway (PGW)

Charging Gateway Function (CGF)

Home Subscriber Server (HSS)

Policy and Charging Rules Function (PCRF)

Online Charging System (OCS)

Authentication, Authorization, and Accounting (AAA)

Diameter Credit Control Application (DCCA)

Cisco LTE PGW Description

For each UE associated with the EPC, there is at least one PGW providing access to the requested PDN. If a UE is accessing multiple PDNs, there could be more than one PGW for that UE.

For each UE associated with the EPS, there is at least one PGW providing access to the requested PDN. If a UE is accessing multiple PDNs, there could be more than one PGW for that UE.

The Cisco LTE PGW Release 1.0 and later provides the following support:

Mobility and Roaming

GTP-based S5/S8 interfaces

Gn/Gp interface support for pre Release 8 SGSNs

IP Addressing and Transport

IP Version 4 (IPv4) and IP Version 6 (IPv6) UEs

IPv4 and IPv6 transport

Stateless Address Autoconfig (SLAAC)

Local pools, static IP, and RADIUS

Overlapping IPv4 addresses

Authentication and Authorization

RADIUS AAA interface

RADIUS CoA and POD

AAA user profiles (for example, Quality of Service [QoS] and access control list [ACL])

AAA load balancing and failover

Policy and QoS

Gx interface for Dynamic Policy and Charging Control (PCC)

Static (local) policies

Bearer level QoS parameters (QoS Class Identifier [QCI], Address Resolution Protocol [ARP], guaranteed bit rate [GBR], maximum bit rate [MBR], APN-AMBR [APN Aggregate Maximum Bit Rate])

Gating, rate limiting and marking

Call Admission Control

Cisco CSG2 policy interfacing

Enhanced PCC for CSG2

Charging

GTP' offline charging

RADIUS off-line charging

Load balancing, failover, and local redirect of charging data

Application-based charging

Local storage of charging data

Security

Access Control Lists (per interface, per-APN)

Source and destination address verification

Duplicate IP address protection

Traffic redirection

Virtual Routing and Forwarding (VRF)-based traffic segregation

Control Plane Policing

Security events logging

High Reliability and Availability

99.999% service availability

Intra- and inter-chassis session redundancy (1:1, hot standby)

Hot swappable components

In service software upgrade

External gateway availability monitoring

Manual and automatic failovers

Overload Handling

Control plane throttling

Traps on high resource usage

Overload (degraded) mode of operation

Lawful Intercept

Content intercept (UDP-based)

SNMP Version 3 based install

Enterprise Features

VRF support

Per-enterprise authentication, authorization, and accounting

Enterprise-assigned IP-address

Operation, Management, and Performance

Command line interface and SNMP-based management

SNMP Version 1, Version 2, and SNMPv3 support

Key performance indicators and bulk statistics

Subscriber and call-based tracing and logging

Event-based diagnostics

Platform and feature MIBs

The Cisco LTE PGW runs on the Cisco Service and Application Module for IP (SAMI), a new-generation high performance service module for the Cisco 7600 Series Router platforms.

For more information about the Cisco SAMI, see the Cisco Service and Application Module for IP User Guide.

System Requirements

This section describes the system requirements for Cisco LTE PGW Release 1.x and includes the following sections:

Memory Recommendations

Hardware and Software Requirements

Determining the Software Version

Upgrading to a New Software Release

For hardware requirements, such as power supply and environmental requirements and hardware installation instructions, see the Cisco Service and Application Module for IP User Guide.

Memory Recommendations

Table 1 Images and Memory Recommendations for Cisco LTE PGW Release 1.x

Platforms
Feature Sets
Software Image
Recommended Flash Memory (MB)
Recommended DRAM
Memory (GB)
Runs
From

Cisco SAMI/
Cisco 7600

PGW Standard Feature Set

c7svcsami-l3ik9s-mz

128

2

RAM


Hardware and Software Requirements

Implementing a Cisco LTE PGW Release 1.x and later on the Cisco 7600 series internet router platform requires the following hardware and software.

Any module that has ports to connect to the network.

A Cisco 7600 Series Router and one of the following supervisor engines running Cisco IOS Release 15.0(1)S or later:

Cisco 7600 Series Supervisor Engine 720 with a Multiplayer Switch Feature Card 3 (WS-SUP720)

Cisco 7600 Series Supervisor Engine 720 with a Multilayer Switch Feature Card 3 and Policy Feature Card 3B (WS-SUP720-3B)

Cisco 7600 Series Supervisor Engine 720 with a Multilayer Switch Feature Card 3 and Policy Feature Card 3BXL (WS-SUP720-3BXL)

Cisco 7600 Series Supervisor Engine 32 with a Multiplayer Switch Feature Card (WS-SUP32-GE-3B) with LCP ROMMON Version 12.2(121) or later on the Cisco SAMI.

Cisco 7600 Series Supervisor Engine 32 with a Multilayer Switch Feature Card and 10-Gigabit Ethernet Uplinks (WS-SUP32-10GE-3B) with LCP ROMMON Version 12.2[121] or later on the Cisco SAMI.

Or one of the following Cisco 7600 series Route Switch Processors running Cisco IOS Release 15.0(1)S or later:

Cisco 7600 Series Route Switch Processor 720 with Distributed Forwarding Card 3C (RSP720-3C-GE)

Cisco 7600 Series Route Switch Processor 720 with Distributed Forwarding Card 3CXL (RSP720-3CXL-GE)

Cisco 7600 Series Route Switch Processor 720 with 10-Gigabit Ethernet Uplinks with Distributed Forwarding Card 3CXL (RSP720-3CXL-10GE)

For details on upgrading the Cisco IOS release running on the supervisor engine, refer to the "Upgrading to a New Software Release" section in the Release Notes for Cisco IOS Release 15.0S. For information about verifying and upgrading the LCP ROMMON image on the Cisco SAMI, refer to the Cisco Service and Application Module for IP User Guide.


Note The Cisco IOS Software required on the supervisor engine is dependent on the supervisor engine being used and the Cisco mobile wireless application running on the Cisco SAMI processors.


Cisco Service and Application Module for IP (Cisco Product Number: WS-SVC-SAMI-BB-K9). The Cisco SAMI must be running Cisco IOS Release 12.4(24)T35c or later.


Note The Cisco LTE PGW Release 1.x software application supports both the Cisco SAMI 1-GB memory default and the 2-GB memory option (Cisco Product Number: MEM-SAMI-6P-2GB[=]).


For security, the IPSec VPN Services Module.

For GTP-Session Redundancy, in addition to the required hardware and software, implementing GTP-Session Redundancy (GTP-SR) requires at minimum:

In a one-router implementation, two Cisco SAMIs in the Cisco 7600 Series Router, or

In a two-router implementation, one Cisco SAMI in each of the Cisco 7600 Series Routers.

Determining the Software Version

To determine the version of Cisco IOS Software running on your Cisco SAMI, log in to PPC3 and enter the show version EXEC command:

PGW# show version
Cisco IOS Software, SAMI Software (SAMI-L3IK9S-M), Experimental Version 
12.4(20100928:164957) 
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 28-Feb-11 09:49 by 

ROM: System Bootstrap, Version 12.4(20100716:044940) [sopm-smbu_lte_r1_5-CSCtf55588 105], 
DEVELOPMENT SOFTWARE

PGW-Flash uptime is 22 hours, 14 minutes
System returned to ROM by reload at 22:43:43 UTC Tue Feb 28 2011
System restarted at 22:49:02 UTC Tue Feb 28 2011
System image file is "c7svcsami-l3ik9s-mz"
Last reload reason: Reload command by admin

...

PGW# 

Upgrading to a New Software Release

For information on upgrading to a new software release, see the product bulletin Cisco IOS Software Upgrade Ordering Instructions at:

http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm

Upgrading the Cisco SAMI Software

For information on upgrading the Cisco SAMI software, see the Cisco Service and Application Module for IP User Guide:


Note The image download process automatically loads the Cisco IOS image onto the six SAMI processors.


MIBs

To obtain lists of supported MIBs by platform and Cisco IOS release, and to download MIB modules, go to:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

Limitations, Restrictions, and Important Notes

When configuring the Cisco LTE PGW, note the following:

The Cisco LTE PGW does not support the Cisco Express Forwarding (CEF) neighbor resolution optimization feature, which is enabled by default.

Therefore, to avoid the possibility of incomplete adjacency on VLAN interfaces for the redirected destination IP address and an impact to the upstream traffic flow for bearers/PDP sessions upon bootup, ensure that you configure the no ip cef optimize neighbor resolution command.

The number of bearer/PDP contexts supported on a PGW is dependent on the memory and platform in use and the PGW configuration (for example, whether Dynamic Feedback Protocol [DFP] is being used or the memory protection feature is enabled, and what rate of bearer creation is supported).

Table 2 lists the maximum number the Cisco SAMI with the 2-GB memory option can support:

Table 2 Number of Bearers/PDPs Supported in 2-GB SAMI

Bearer/PDP Type
Maximum Number per SAMI

GTPv2 bearer (IPv4 and IPv6)

380,000

GTPv1 PDP (IPv4 and IPv6)

800,000



Note When the maximum allowable number of bearers/PDP contexts is reached, the PGW refuses new mobile sessions until sessions are available.


To avoid issues with high CPU usage, we recommend the following configurations:

To reduce the CPU usage during bootup, disable logging to the console terminal by configuring the no logging console global configuration command.

To ensure that the HSRP interface does not declare itself active until it is ready to process a peer's hello packets, configure the delay period before the initialization of HSRP groups with the standby delay minimum 100 reload 100 interface configuration command under the HRSP interface.

To minimize issues with high CPU usage for additional reasons, such as periods of high PPP PDP processing (creating and deleting), disable the notification of interface data link status changes on all virtual template interfaces of the GGSN using the no logging event link-status interface configuration command.

! 
interface Virtual-Template1 
description GGSN-VT 
ip unnumbered Loopback0 
encapsulation gtp 
no logging event link-status
gprs access-point-list gprs 
end 

For Mobile Express Forwarding (MEF) support, the redirect all command must be configured under the APN.

Ensure that radius-server source ports extended command is configured (to enable 200 ports in the range from 21645 to 21844 to be used as the source ports for sending out RADIUS requests).

New and Changed Information

The following sections list new features and behavior changes in the Cisco IOS 12.4(24)T3 releases:

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T35c

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T34d

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3c

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3b

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3a1

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3a1

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T35c

There are no new implementations or behavior changes in Cisco PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T34d

There are no new implementations or behavior changes in Cisco PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3c

Cisco LTE PGW Release 1.3 introduces support for the following PCO options:

P-CSCF Address Request

IPv4 (0x0C) and IPv6 (0x01)

IPv4 DNS (0x03) and IPv6 DNS (0x0D)

Address Allocation from NAS (0x0A)

DHCPv4 (0x08)

(CSCtl99150)

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3b

Per CR 225, with Cisco LTE PGW Release 1.2, the Tracking Area Identity (TAI) and User Location Information (ECGI) are included in the change report action information element (IE), according to the received event trigger, in the following messages:

Create Session Response

Create Bearer Request

Modify Bearer Response

Update Bearer Request

Change Notification Response

(CSCth92541)

New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3a1

The following new feature and compliance change have been introduced in Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1:

Configuring Local Service Record Information Generation

Configuring Specification Compliance

Configuring Local Service Record Information Generation

By default, the Cisco LTE PGW obtains service record information from the Cisco CSG2. With Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1, service record information can be generated locally, without the Cisco CSG2.

Service Record Generation with a Cisco CSG2

When generating service record information with a Cisco CSG2, the following configuration must exist:

Service aware billing is enabled on the APN using the service-aware access-point configuration command.

The charging record type is set to pcdr using the charging record type access-point configuration command.

Traffic is redirected to the Cisco CSG2 using the redirect all access-point configuration command.

With the service record generation with a Cisco CSG2 implementation, the Cisco CSG2 sends the service record information to the Cisco LTE PGW, which then adds it to the CDR.

Service Record Generation without a Cisco CSG2

When generating service record information without a Cisco CSG2, the following configuration must exist:

Service aware billing is not enabled on the APN.

The charging record type is set to pcdr using the charging record type access-point configuration command.

Traffic is redirected directly to the Gi interface using the redirect all access-point configuration command.

With the service record without a Cisco CSG2 implementation, the PGW generates the service information and adds it to the CDR.


Note Service record information added by the PGW for non service aware APNs does not include information for the following fields that are defined as optional by the 3GPP specifications: time of last usage, time of last usage, and time usage.


To enable the PGW to generate service record information locally, complete the following tasks while in charging profile configuration mode.

Command
Purpose

Router(ch-prof-conf)# service id num

Configures the default service identifier for the service record information locally generated and added to the P-CDR by the PGW. The service identifier is used to identify the service or the service component to which the service data flow relates. (See Service-Identifier AVP as defined in TS 29.212.)

A valid value is a number from 1 through 4294967295. The default is 1.

Router(ch-prof-conf)# rating id num

Configures the default IP service flow identity. (See Rating-Group AVP as defined in TS 32.299.)

A valid value is a number from 1 through 4294967295. The default is 1.



Note For more information about configuring charging profiles, see the Cisco LTE PGW Configuration Guide.


Configuring Specification Compliance

Support for the following 3GPP specification change requests (CRs) records for 29.274 has been introduced in Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1:

CR 267—Serving Network

CR 358—Bearer QoS in modify bearer request

CR 430—UE Timezone and user location information (ULI) included in bearer response messages

CR 433—Correcting misaligned information element (IE) presence type statements

CR 451—Charging characteristics value for active PDN connections

CR 154—Offending IE in the cause IE

Additionally, commands to configure backward compliance have been added for the following 29.274 CRs:

CR 308—LBI clarifications for Gn/Gp handovers. By default, compliance for this CR 308 is enabled on the PGW, but by default is disabled on the SGW.

CR 324—APN-AMBR in the create/delete bearer request. Compliance must be enabled on the PGW and SGW. By default, compliance for this CR is disabled.

CR 137—Combined uplink and downlink traffic flow template (TFT) IEs. CR 137 Compliance must be enabled on the PGW and SGW. By default, compliance for CR 137 is disabled.

To configure compliance for the above CR, complete the following tasks:

Creating a Compliance Profile

Creating a Remote Path Group

Creating a Compliance Profile

Operators can create a compliance profile in which they configure CR compliance. Once a compliance profile has been created, it can be applied to a path group to a remote node. For information on creating a path group to a remote node, see"Creating a Remote Path Group" section.

To create a compliance profile and its CR configuration, complete the following tasks, beginning in global configuration mode:

 
Command
Purpose

Step 1 

Router(config)# gprs compliance profile name

Creates or modifies a compliance profile, where name is the name of the compliance profile.

Step 2 

Router(config-compl-profile)# cr 29.274-0308

Configures the gateway to comply with CR 308 (LBI clarifications for Gn/Gp handovers). On the PGW, CR 308 compliance is enabled by default. On the SGW, compliance is disabled by default.

Step 3 

Router(config-compl-profile)# cr 29.274-0324

Configures the gateway to comply with CR 324 (APN AMBR in the create/delete bearer request). On the PGW and SGW, CR 324 compliance is disabled by default.

Step 4 

Router(config-compl-profile)# cr 29.274-0137

Configures the gateway to comply with CR 137 (combine uplink and downlink TFT IEs). On the PGW and SGW, compliance is disabled by default.

Creating a Remote Path Group

Once a compliance profile has been configured, operators can create a path group. In the path group, the address of the remote node is configured and as well as the compliance profile to use.

 
Command
Purpose

Step 1 

Router(config)# gprs remote group name

Creates or modifies a remote path group, where name is the name of the group.

Step 2 

Router(config-remote-group)# compliance name

Applies a preconfigured compliance profile to the path group.

Step 3 

Router(config-remote-group)# ip address {v4 start_ipv4_addr end_ipv4_addr | v6 start_ipv6_addr end_ipv6_addr}

Configures an IP address range in the remote path group, where:

v4 start_ipv4_addr end_ipv4_addr—IPv4 address range.

v6 start_ipv6_addr end_ipv6_addr—IPv6 address range.

Caveats

This section contains the caveats for the following releases:

Caveats - Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c

Caveats - Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d

Caveats - Cisco LTE PGW Release 1.3, Cisco IOS Release 12.4(24)T3c

Caveats - Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3b

Caveats - Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1

Caveats - Cisco LTE PGW Release 1.0, Cisco IOS Release 12.4(24)T3a

Caveats describe unexpected behavior in Cisco IOS Software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.

All caveats in Cisco IOS Release 12.4 and Cisco IOS Release 12.4 T are also in Cisco IOS Release 12.4(22)YE.

For information on caveats in Cisco IOS Release 12.4, see Caveats for Cisco IOS Release 12.4.

For information on caveats in Cisco IOS Release 12.4 T, see Caveats for Cisco IOS Release 12.4T, which lists severity 1 and 2 caveats and select severity 3 caveats and is located on Cisco.com and the Documentation CD-ROM.

Using the Bug Navigator II

If you have an account with Cisco.com, you can use Bug Navigator II to find caveats the most current list of caveats of any severity for any software release. To reach Bug Navigator II, log in to Cisco.com and click Software Center: Cisco IOS Software: Cisco Bugtool Navigator II. Another option is to go directly to http://www.cisco.com/support/bugtools.

Caveats - Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c

This section lists the open, resolved and unreproducible caveats that pertain to Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

Open Caveats

Resolved Caveats

Unreproducible Caveats

Open Caveats


Note Caveats open in one release are also open in prior releases.


The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.

Cisco LTE PGW Caveats

Cisco SAMI Caveats

Cisco LTE PGW Caveats

This section lists the PGW caveats that are open with Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

CSCtq74610

The Cisco LTE PGW crashes when handling a RADIUS Change of Authorization (CoA) message from the Cisco CSG2 under stress conditions with a slow Policy and Charging Rules Function (PCRF).

This issue occurs under the following conditions:

200 calls per second creating 60K sessions.

Within 60 seconds of a CSR, an MBR is sent.

A slow PCRF results in several authentication/accounting failures.

Workaround: There is currently no known workaround.

CSCtq82202

In a redundant implementation, the standby PGW undergoes a self-induced reload when there is a lot of synchronization activity from the active PGW that was triggered by the creation of sessions due to create session requests and the deletion of sessions due to failure of either the bearer resource command (BRC) or the modify bearer command (MBC) procedures.

This condition occurs only when there are a high number of failures resulting from either BRC or MBC procedures.

Workaround: There is currently no known workaround.

Cisco SAMI Caveats

This section lists the SAMI caveats that are open with Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

CSCti31555

For dual stack sessions belonging to APNs with Mobile Express Forwarding (MEF) switching enabled, the "MEF uplink packets / links" field displays some non zero values immediately after the sessions come up.

This condition occurs when sessions belonging to an APN, which has dual stack configured (using the gtp bearer dual-addr access-point configuration command) and has MEF switching enabled. The show gprs gtp pdp-context tid command output displays some non zero values in the "MEF uplink packets / links" field.

Workaround: There is currently no known workaround.

Resolved Caveats

The following sections list the caveats that have been resolved with Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

Cisco LTE PGW Caveats

Cisco SAMI Caveats

Miscellaneous Caveats

Cisco LTE PGW Caveats

This section lists the PGW caveats that are resolved with Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

CSCtj11112

In a redundant implementation, the Cisco LTE PGW rejects a RADIUS Change of Authorization (CoA) because of an existing CoA outstanding error message on newly active PGW after switchover.

This condition is seen for existing sessions on the newly active PGW after a switchover with Cisco LTE PGW releases prior to Release 1.3.5.

CSCtj43523

The pre Release 8 Quality of Service (QoS) status counters are not incremented in the output of the show gprs qos status privileged EXEC command.

This condition occurs when a GTPv1 PDP context is created on a UMTS QoS class.

CSCtj99979

The Cisco LTE PGW does not delete PDP contexts after an idle PDP context timeout occurs.

This condition occurs when the session idle timeout is configured and a GTPv0 PDP is created and left idle. When the timeout occurs, the PDP is not deleted.

CSCtk83766

When the limit volume yyy command is configured under a charging profile, the limit volume yyy reset command does not work, and vice versa.

This condition occurs when the values for the two commands are not the same.

CSCto03189 3

When a BSM Resource Controller (BRC) is sent to the Cisco LTE PGW to replace the existing uplink (UL) and downlink (DL) install filters, the PGW replaces the UL filter, but it adds the filter received from the Policy Control and Charging Rules Function (PCRF) on the DL instead of replacing it.

This condition occurs when a Policy and Charging Control (PCC) session is created using the default settings and a BRC is sent to the PGW to replace existing filters.

CSCtq15406

Spurious memory access is seen on the Cisco LTE PGW when a GTPv2 session is created over GTPv0 because incorrect data structure is being accessed.

CSCtq17144

In a redundant implementation, the standby gateway has some stale sessions but the active gateway has none. The standby sessions should be in a "deleting" state.

CSCtq17447

On the Cisco LTE PGW a traceback occurs with the following message:

%SYS-2-BADSHARE: Bad refcount in datagram_don while session deletion

CSCtq17797

In a redundant implementation, a new standby gateway crashes during bulk sychronization.

This condition occurs when Quality of Service (QoS) profile on the Policy and Charging Rules Function (PCRF) is configured to initiate dedicated bearers.

CSCtq18845

The Cisco LTE PGW reloads.

This condition occurs after hours of 4G traffic running at high create/delete sessions per second rate (approximately 500 create/deletes per second) and a continuous fail/re-enable Policy and Charging Rules Function (PCRF).

CSCtq23278

The Cisco LTE PGW sends the incorrect SGSN address in the service container after an SGW handover.

This condition is seen when both the Cisco LTE SGW and a public land mobile network (PLMN) change occurs.

CSCtq42803

When a GTPv1 to GTPv2 handoff request is received for a GTPv1 PDP that is in the process of being deleted and waiting on the final SCU, the Cisco LTE PGW might crash.

This condition is seen under the following circumstances:

1. The path to the Cisco CSG2 is down.

2. The peer is restarted.

3. A GTPv1 to GTPv2 request is received for an existing PDP context.

CSCtq44823

In a redundant implementation, the active gateway does not synchronize Quality of Service (QoS) values that are received from the Policy and Charging Rules Function (PCRF) during negotiation to the standby gateway. This causes inconsistent redundant setups for QoS values and the standby will apply the default QoS values on the subscriber traffic after a switchover occurs.

This condition is seen on the standby gateway in a redundant implementation when the active gateway receives QoS values from PCRF during negotiation.

CSCtq45087

In a redundant implementation, the active gateway does not synchronize Maximum Bit Rate (MBR)/Guaranteed Bit Rate (GBR) uplink/downlink values negotiated by Policy and Charging Rules Function (PCRF) to the standby gateway. Therefore, the values are not reflected on the standby gateway.

This condition occurs on the standby gateway in a redundant implementation when the active gateway receives Quality of Service (QoS) values from PCRF.

CSCtq52753

When the default (empty) policy-profile is applied to an APN, the Cisco LTE PGW applies the Aggregate Maximum Bit Rate (AMBR) values to a GTPv1 session after a GTPv2 to GTPv1 handover occurs. Use the show gprs gtp pdp-context tid tid qos police privileged EXEC command to display the values applied to the session.

This condition occurs when policing is configure on an APN.

CSCtq54836

When a Tracking Area Identifier (TAI) change occurs from a User Location Information (ULI) type other than TAI or Routing Area Identifier (RAI), call detail records (CDRs) are closed with a public land mobile network (PLMN) ID change as the cause.

This condition occurs when the PGW receives a create session request with an ULI type other than TAI/RAI, and then receives a modify bearer request or delete session request with TAI/RAI.

CSCtq55745

After an enhanced quota server interface is unconfigured by using the ggsn quota-server server-name service-msg global configuration command, PDP contexts become stuck in a "deleting" state after issuing the clear gprs gtp pdp all privileged EXEC command.

This condition occurs when service-aware sessions exist, the enhanced quota server interface is unconfigured, and then the clear gprs gtp pdp context command is issued. Instead of being deleted, the service-aware PDP contexts become stuck in a deleting state.

CSCtq57150

In a redundant implementation, when the Cisco CSG2 path is down, stuck sessions are seen on the active PGW when the peer restarts and sends a new create request for an existing session.

This condition occurs only when the Cisco CSG2 path is down, there is an existing GTPv1 PDP context, and then the peer restarts and sends a new create request for the existing PDP.

CSCtq58699

GTPv1 PDP contexts remained stuck and are not deleted even after attempting to manually clear them when the path between the Cisco LTE PGW and Cisco CSG2 is flapping and Service Control Requests (SCRs) are being sent at a rate high enough to cause more than 12500 outstanding SCRs per Traffic and Control Plane processor (TCOP).

This condition occurs only when SCRs are timing out because the path between the PGW and CSG2 is flapping and a large number of pending SCRs exist in the system (more than 12500 SCRs per TCOP).

CSCtq60091

In a redundant implementation, PDP contexts are deleted after two switchovers occur.

This condition can be seen when a GTPv1 PDP is created, the active gateway reloads, a handoff from GTPv1 to GTPv2 occurs, and the active gateway reloads once again. The PDP context is not created on the standby gateway, but the PDP context exists on the active gateway.

CSCtq63301

In a redundant implementation, a traceback occurs on the active PGW during a switchover.

This condition occurs when a redundancy state changes when a GTPv2 PDP is in a half-created state.

CSCtq63866

The show gprs charging profile command displays an incorrect value for the Continue Option for Volume Limit trigger. The value displays as Enabled when it is Disabled, and vice versa.

The continuity trigger for duration should be enabled if continuity trigger for volume is disabled and the continuity trigger for duration should be disabled if continuity trigger for volume is enabled.

CSCtq67546

In a redundant implementation, when a standby to active switchover occurs when there are existing PDP contexts waiting on the final SCU to be received from the Cisco CSG2, the final usage might be lost.

This condition occurs when the newly active PGW does not wait on the SCU and deletes the PDP contexts as soon as the its redundancy state changes to active. This issue is seen only when PGW switchover occurs and there are PDPs contexts waiting for final SCU from the Cisco CSG2.

CSCtq71043

On the Cisco LTE PGW, the following syslog message might appear:

Syslog %GPRSFLTMG-3-GPRS_CHARGING_NO_CDR: No Open CDR

This condition occurs when the quota server interface on the PGW is overloaded, or in any other situation where "Out of Order Usage Messages" (SCUs) are received by the PGW.

The usage reporting reason is falsely interpreted on the PGW. If the usage report reason is is interpreted as PDP closure, the existing CDR might be closed, and all subsequent usage for the PDP context might not be reported and the syslog message appears.

Cisco SAMI Caveats

This section lists the Cisco SAMI caveats that are resolved with Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

CSCtk12410

When two Cisco SAMIs are configured as an active standby pairs, any unexpected reload of one of the processors in the standby SAMI can cause the active SAMI to reload because of an RF induced self-reload.

This condition occurs if the HSRP priority of the standby SAMI is greater than the priority of the active SAMI, either because of explicit configuration or based on the IP address of the active and standby SAMIs.

CSCto98454

Upstream data packets are dropped in the Cisco SAMI IXP network processor path. Issuing the show gprs gtp pdp-context tid tid privileged EXEC command displays the number of Mobile Express Forwarding (MEF) dropped packets incrementing.

This condition occurs when the L2/MAC address to redirect address (Cisco CSG2) is not resolved.

Miscellaneous Caveats

This section lists a miscellaneous Cisco IOS software caveat that is resolved with Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

CSCtc68037

A Cisco IOS device might experience an unexpected reload as a result of mtrace packet processing

Unreproducible Caveats

This section lists caveats that are unreproducible in Cisco LTE PGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.

CSCtq63118

After a system reload, both gateways in a redundant implementation might end up in an active or active-drain state. This condition is rarely seen, and only occurs when both gateways in a redundant implementation are reloaded at almost the same time. This condition is more likely to occur when the Stream Control Transmission Protocol (SCTP) connectivity for the redundant configuration is lost.

CSCtq54934

An SNMP getmany request triggered on ciscoGprsAccPtMIB from an SNMP manager on the gateway times out without receiving a response for a objects in ciscoGprsAccPtMIB.

This condition occurs when the SNMP getmany request is continuously triggered (in a loop) on the ciscoGprsAccPtMIB.

CSCtq74652

When Remote Console and Logging (RCAL) is enabled on the Cisco SAMI, the RCAL show proc cpu and the show proc memory commands cause the TCOP CPU to become stuck at 99% usage.

This CPU issue is observed after a few hours of experiencing the following conditions:

a. 66K sessions are created and deleted at 300 calls per sec.

b. Standby gateway is continuously reloading.

c. The charging gateway interface is flapping.

d. A script is executed every 5 seconds that executes the following commands

show proc cpu | include five seconds

show gprs gtp status | inc activated session

show gprs gtp status | inc activated sessions

show proc mem | include Processor

show proc mem | include I/O

Caveats - Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d

This section contains open and resolved caveats that pertain to Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.

Open Caveats


Note Caveats open in one release are also open in prior releases.


The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.

Cisco LTE PGW Caveats

Cisco SAMI Caveats

Cisco LTE PGW Caveats

There are no known PGW caveats open in Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.

Cisco SAMI Caveats

This section lists the SAMI caveats that are open with Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.

CSCti31555

For dual stack sessions belonging to APNs with Mobile Express Forwarding (MEF) switching enabled, the "MEF uplink packets / links" field displays some non zero values immediately after the sessions come up.

This condition occurs when sessions belonging to an APN, which has dual stack configured (using the gtp bearer dual-addr access-point configuration command) and has MEF switching enabled. The show gprs gtp pdp-context tid command output displays some non zero values in the "MEF uplink packets / links" field.

Workaround: There is currently no known workaround.

Resolved Caveats

The following sections list the caveats that have been resolved with Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.

Cisco LTE PGW Caveats

Cisco SAMI Caveats

Cisco LTE PGW Caveats

This section lists the PGW caveats that are resolved with Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.

CSCtn10003

When Remote Console and Logging (RCAL) is enabled on the Cisco Service and Application Module for IP (SAMI), the following error messages displays when a create context request is received, or a GTPv2 to GTPv1 handoff occurs on the PGW with the Radio Access Technology Type (RAT) type "5" (HSPA EVOLUTION):

SAMI 1/4: Jun  8 04:47:42.859: %GTP-0-NORESOURCE: GSN: 0.0.0.0, TID: 00, APN: NULL, 
Reason: Invalid RAT value for recommended RAT IE

The RAT type is set to null.

CSCtq22874

The Cisco SAMI running the Cisco LTE PGW Release 1.3.4 image might not generate service records as part of the call detail record (CDR) contents.

This condition occurs when the PGW has a configuration under the APNs to generate local P-CDRs (no service aware command and charging record type pcdr command configuration), and there should be some PDP session establishments taking place with these APNs.

CSCtq24403

The active and standby gateways have a mismatch in the number of sessions after some create PDP context failures, or PDP contexts are deleted in the active gateway.

CSCtq42159

The Cisco LTE PGW might see constant high CPU usage (>90%) and could possibly not recover from that condition.

This condition might occur when a GTPv0 create request is received on an existing GTPv1 PDP while that GTPv1 PDP is waiting to be deleted.

When PDP contexts are being deleted at a high rate, some PDP contexts are in a delete pending queue waiting to be deleted. If a GTPv0 create request is received for one of these GTPv1 PDPs in the delete pending queue, the create request continuously gets enqueued for processing in a loop, and causes the high CPU on the PGW.

CSCtq43085

After a mediation device (MD) is attached to the Cisco LTE PGW, an "SNMP QFULL_ERR" error message is received if MD statistics are polled from the PGW.

This condition occurs when the ifIndex on the Proxy Control Processor (PCOP) and Traffic and Control Plane processors (TCOPs) becomes out of sync when the snmp-server ifindex persist command is configure and interfaces are added or removed at the PCOP.

When an MD attach occurs with the PCOP interface ifIndex, the MD entry is created at the PCOP. If the same ifIndex is not valid on the TCOPs, the MD creation fails at the TCOPs. Upon an MD statistics query, the PGW attempts to aggregate values per TCOP. Since the MD entry is not present at the TCOPs, they do not respond to the aggregation process, and the process times out after approximately 10 seconds. During this 10 second, a lot of SNMP packets are queued and queue overflow occurs, which results in a "SNMP QFULL_ERR" error.

CSCtq440383

The LTE SGW or LTE PGW might log "Active Charging Gateway NOT matching on Processors"

This condition occurs when the Cisco SAMI is running the Cisco LTE SGW Release 1.x or the Cisco LTE PGW Release 1.x images.

CSCtq71301

An "INVALID_ID: bad id in id_get (Out of IDs!) (id: 0x0)" syslog message is generated on the standby SGW/PGW. This syslog message is a generic one and does not always indicate the issue.

This condition occurs when more that 16384 paths are created (but do not necessarily exist simultaneously) and are synchronized to the standby gateway.

If on the standby gateway, the show gprs redundancy command output displays a count more than 16384 in the Path Setup messages field, this is probably the issue.

Cisco SAMI Caveats

There are no Cisco SAMI caveats newly resolved with Cisco LTE PGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.

Caveats - Cisco LTE PGW Release 1.3, Cisco IOS Release 12.4(24)T3c

This section contains open and resolved caveats that pertain to Cisco LTE PGW Release 1.3, Cisco IOS Release 12.4(24)T3c.

Open Caveats


Note Caveats open in one release are also open in prior releases.


The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.

Cisco LTE PGW Caveats

There are no known PGW caveats open in Cisco LTE PGW Release 1.3, Cisco IOS Release 12.4(24)T3c.

Cisco SAMI Caveats

This section lists the SAMI caveats that are open with Cisco LTE SPW Release 1.3, Cisco IOS Release 12.4(24)T3c.

CSCti31555

For dual stack sessions belonging to APNs with Mobile Express Forwarding (MEF) switching enabled, the "MEF uplink packets / links" field displays some non zero values immediately after the sessions come up.

This condition occurs when sessions belonging to an APN, which has dual stack configured (using the gtp bearer dual-addr access-point configuration command) and has MEF switching enabled. The show gprs gtp pdp-context tid command output displays some non zero values in the "MEF uplink packets / links" field.

Workaround: There is currently no known workaround.

Resolved Caveats

The following sections list the caveats that have been resolved with Cisco LTE PGW Release 1.3, Cisco IOS Release 12.4(24)T3c.

Cisco LTE PGW Caveats

This section lists the PGW caveats that are resolved with Cisco LTE PGW Release 1.3, Cisco IOS Release 12.4(24)T3c.

CSCtj80560

The Cisco LTE PGW crashes because of incorrect routing.

Because of an increased latency in setting up a Policy and Charging Control (PCC) session, the SGSN performs a GTP version fallback from GTPv1 to GTPv0. In this scenario, the PGW attempts to clean up the pending GTPv1 session and create a GTPv0 context. While cleaning up the GTPv1 session, the PGW crashes.

CSCtj99555

The Cisco GGSN/Cisco LTE PGW crashes when an snmpwalk is made over cGtpPathStatisticsTable. This condition occurs when paths are created and removed (PDPs are created and deleted, or charging gateways are configured and unconfigured) during the snmpwalk.

CSCtk75845

Rulebase IDs are not synchronized between the active and standby PGWs.

This condition occurs because the active PGWs sychronize the rulebase IDs only when the APNs are configured for service-aware charging. Therefore, rulebase IDs are not synchronized for APNs without the service-aware configuration.

CSCtl93281

The standby PGW crashes during a 4G session creation for an existing 3G session.

This condition occurs when there is an existing GTPv1 session and the PGW receives a GTPv2 session with the same IMSI and attempts to sychronize the newly arrived GTPv2 session to the standby PGW.

CSCtl88898

The Cisco LTE SGW and Cisco LTE PGW ignore the User Location Information (ULI) information element (IE) when it is sent in a delete session request.

CSCtn08442

The standby PGW crashes during the create IPv6 default and dedicated bearer process.

This condition occurs when the rulebase IDs are sychronized from the active PGW to the standby PGW because of a null pointer access during the attribute decode.

CSCtn12288

An infinite loop causes the watchdog timer to reload the PGW.

This condition occurs while the PGW is constructing a GTPv1 update response packet for a PDP on a service aware APN.

CSCtn12329

Traceback for a GTPv1 PDP update with service aware charging enabled.

This condition occurs when service aware billing is configured and the PGW sends an update request to the SGSN and illegal memory access occurs.

CSCtn14284

An AAA access-request returns with an internal error, and on the Cisco GGSN or Cisco LTE PGW the following unconditional bug information is printed: "AAA had an unexpected return."

This condition occurs when an access-request is sent to the AAA server during periods of stress conditions on the client process and a failure to build the RADIUS packet occurs.

CSCtn25629

SNMP query for entPhysicalParentRelPos returns an incorrect value. This condition occurs because the SNMP query returns negative values because of an error in initialization of the data structure containing the processor details.

CSCtn31609

SNMP query for cpmCPUTotalPhysicalIndex returns an incorrect value. This condition occurs when the SNMP query is made for cpmCPUTotalPhysicalIndex 1, and an invalid value of 0 (zero) is returned instead of 2 because of an initialization error of the related table.

CSCtn40983

Crash occurs while executing a show command for a PDP that is in a deleting state.

This condition occurs when the user issues a show command for a PDP that is already being deleted and waits on the "more" prompt while the contents of the PDP are deleted, and then continues with the show command, which attempts to access the freed PDP contents.

CSCtn19492

PDP becomes stuck when the RADIUS connection with the Cisco CSG2 is lost during the deleting state.

This condition occurs when the reply from the Cisco CSG2 is delayed or lost.

Cisco SAMI Caveats

There are no Cisco SAMI caveats newly resolved with Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3c.

Caveats - Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3b

This section contains open and resolved caveats that pertain to Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3b.

Open Caveats


Note Caveats open in one release are also open in prior releases.


The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.

Cisco LTE PGW Caveats

There are no known Cisco LTE PGW caveats open in Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3b.

Cisco SAMI Caveats

This section lists the SAMI caveats that are open with Cisco LTE SPW Release 1.2, Cisco IOS Release 12.4(24)T3b.

CSCti31555

For dual stack sessions belonging to APNs with Mobile Express Forwarding (MEF) switching enabled, the "MEF uplink packets / links" field displays some non zero values immediately after the sessions come up.

This condition occurs when sessions belonging to an APN, which has dual stack configured (using the gtp bearer dual-addr access-point configuration command) and has MEF switching enabled. The show gprs gtp pdp-context tid command output displays some non zero values in the "MEF uplink packets / links" field.

Workaround: There is currently no known workaround.

Resolved Caveats

The following sections list the caveats that have been resolved with Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3b.

Cisco LTE PGW Caveats

This section lists the PGW caveats that are resolved with Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3b.

CSCth54731

During a GTPv2 to GTPv1 handoff, the radio access technology (RAT) type from the GTPv2 session is copied into the GTPv1 session without verifying if the GTPv2 RAT type is valid for the GTPv1 session. Therefore, the interim accounting messages are sent with an invalid RAT type for the GTPv1 session.

This condition occurs when the RAT type is E-UTRAN and a handover from GTPv2 to GTPv1 occurs.

CSCti93827

The following error message displays on the console and some IPv6 addresses are not released into the pool after a session deletion, however, the addresses are assigned in subsequent session creations.

IPC-3-SAMI_IPV6_POOL_FAIL: Unexpected condition: Malloc Failure for IPv6 Pool Mgmt 
Module

This condition occurs when the Cisco LTE PGW is configured with 500 APNs, all of which have different VRFs and accounting and charging enabled, and the PGW receives continuous session create, modify, and delete requests at 750 calls per second (cps).

CSCtj06869

A Traffic and Control Plane Processor (TCOP) spikes for a long time during an SNMP query with 192K static traffic, 192K create/delete requests, and 192K create at 1200 cps.

This condition occurs with the following sequence of events:

a. Reload gateways

b. Create 192K static dual-stack sessions with traffic

c. Create/delete 192K at 1200CPS in a loop

d. Create 192K at 120CPS with same International Mobile Subscriber Identity (IMSI) as in Step c

e. On the SNMP server, do an snmpwalk and getmany on cGgsnExtMIB

Issue the show processor cpu command to display that the Proxy Control Processor (PCOP) stays at 98% for a long time.

CSCtj09958

Some sessions are not synchronized to the standby Cisco LTE PGW when Gx is enabled for dual stack sessions with the DHCP option.

When the PGW is configured with 500 APNs, all of which have different VRFs, Policy and Charging Control (PCC), accounting, charging, and DHCP proxy address allocation for IPv4 addresses, and redundancy configured, this condition occurs after approximately 38,000 sessions are created.

CSCtj29343

The Cisco LTE PGW reports that the Dynamic Feedback Protocol (DFP) high threshold has been reached and is congested due to low processor memory.

This condition occurs after a switchover with 800K GTPv1 Gx sessions with charging enabled (time trigger set at five minutes and the volume trigger 1 Mb).

CSCtj42310

When the Cisco LTE PGW dynamically assigns IPv6 prefixes to the UEs from a local pool or from a RADIUS pool name or RADIUS prefix in response to a IPv6 router solicitation from the UE, the PGW must send an IPv6 router advertisement with the UE's prefix information with the lower 64 bits of the IPv6 address in the prefix extension set to zero. The PGW incorrectly sends the non zero UE's interface ID in the lower 64 bits.

This condition occurs with an IPv6 solicitation from a UE using an IPv6 address.

CSCtj45011

Lawful Intercept does not intercept GTPv0 Intercept Related Information (IRI) and Content of Communication (CC) packets. A show wire issued on the Cisco LTE PGW displays that no packets are being intercepted for the generic stream. The mediation device (MD) also does not show any HI2_IRI or HI3_CC packets intercepted when context requests and date were sent to a specific International Mobile Subscriber Identity (IMSI) session.

CSCtj79577

When IPv6 primary and secondary DNS addresses are configured under an APN in the Active PGW, and an IPv6 session is created, the primary and secondary DNS addresses for that session are not synchronized to Standby PGW.

This condition occurs when IPv6 DNS addresses are configured in the APN in the Active PGW, and an IPv6 session is synchronized to the Standby PGW.

CSCtj83311

The charging characteristics received in a GTPv2 message do no get synchronized from the Active to the Standby Cisco LTE PGW.

This condition applies to all GTPv2 PDP contexts.

CSCtk01630

In compliance with the Release 8.2.0 Create Session Request, the first byte of the mobile station ISDN (MSISDN) number is removed.

CSCtk05719

Downstream traffic fails at the Cisco LTE PGW for IPv6 PDP contexts.

This issue is seen in all Cisco LTE PGW and Cisco GGSN releases when the IPv6 address is dynamically allocated, and the UE modifies the interface ID.

CSCtk82421

The Cisco LTE PGW clears the Autonomous bit while installing the MS prefix in the Interface Data Block (IDB), which causes the IPv6 ND RA message to be sent with the Autonomous bit not set.

This condition occurs only when the UE requests dynamic IPv6 prefix allocation from the Cisco LTE PGW.

Cisco SAMI Caveats

This section lists the Cisco SAMI caveats that are resolved with Cisco LTE PGW Release 1.2, Cisco IOS Release 12.4(24)T3b.

CSCth91677

The UE is unable to acquire an IPv6 address.

This condition occurs when the Cisco LTE PGW dynamically assigns IPv6 prefixes from the UEs from a local pool or from a RADIUS pool name or RADIUS prefix. The IPv6 router solicitation from the UE is lost and therefore, the UE is unable to acquire its IPv6 address.

CSCti63031

Data packets to or from the MSs are dropped for APNs with VRFs when IXP switching is enabled (the default).

This condition occurs when the Cisco LTE PGW is configured with 500 APNs, all of which are configured with a different VRF and the redirect all ip command. Traffic for MSs from some of the 500 APNs is dropped at the IXP. The show mef access-point command displays an all zeros MAC address, for example, Redirect MAC Address: 0000.0000.0000.

CSCti79332

When the PGW is switching traffic at a high data rate (approximately 1.2 mpps) for more than 48 hours, the following error message along with a traceback is seen,

%PLATFORM-3-SAMI_INTRHOG: DMA interrupt is running for (xxx)usecs, more than 
(xxx)usecs.

This condition occurs when the PGW is connected to a Cisco CSG2 and there are 380K enabled sessions distributed over 500 APNs, all of which are configured with a different VRF, and the Gx and PCC features enabled, and the PGW is switching upstream and downstream data to these sessions at a high rate (1.2 million packets per second [mpps]) for more than 48 hours.

Caveats - Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1

This section contains open and resolved caveats that pertain to Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.

Open Caveats

Resolved Caveats

Open Caveats


Note Caveats open in one release are also open in prior releases.


The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.

Cisco LTE PGW

Cisco SAMI

Cisco LTE PGW

The following PGW caveats are open in Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.

CSCti93827

The following error message displays on the console and some IPv6 addresses are not released into the pool after a session deletion, however, the addresses are assigned in subsequent session creations.

IPC-3-SAMI_IPV6_POOL_FAIL: Unexpected condition: Malloc Failure for IPv6 Pool Mgmt 
Module

This condition occurs when the Cisco LTE PGW is configured with 500 APNs, all of which have different VRFs and accounting and charging enabled, and the PGW receives continuous session create, modify, and delete requests at 750 cps.

Workaround: There is currently no known workaround, however, the addresses that were not deleted in the pool are not leaked since they are assigned to new users on subsequent session creations.

CSCtj09958

Some sessions are not synchronized to the standby PGW, when Gx is enabled for dual stack sessions with the DHCP option.

When the PGW is configured with 500 APNs, all of which have VRF, Policy and Charging Control (PCC), accounting, charging, and DHCP proxy address allocation for IPv4 addresses, and redundancy configured, this condition occurs after approximately 38,000 sessions are created.

Workaround: There is currently no known workaround.

Cisco SAMI

This section lists the SAMI caveats that are open with Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.

CSCti31555

For dual stack sessions belonging to APNs with MEF switching enabled, "MEF uplink packets / links" field displays some non zero values immediately after the session comes up.

This condition occurs when sessions belonging to an APN, which has dual stack configured (using the gtp bearer dual-addr access-point configuration command) and has MEF switching enabled (using the redirect all ip access-point command). The show gprs gtp pdp-context tid command output displays some non zero values in the "MEF uplink packets / links" field.

Workaround: There is currently no known workaround.

CSCti63031

Data packets to or from the mobiles are dropped for APNs with VRF when IXP switching is enabled (the default).

This condition occurs when the PGW is configured with 500 APNs, all of which are configured with a different VRF and the redirect all ip command. Traffic for mobiles from some of the 500 APNs is dropped at the IXP. The show mef access-point command displays an all zeros MAC address, for example, Redirect MAC Address: 0000.0000.0000.

Workaround: Before any sessions are open for mobiles under an APN, issuing the ping command to the redirect addresses configured under the affected APNs triggers an Address Resolution Protocol (ARP) request that resolve the issue. Alternately, if there are a huge number of APNs with redirect addresses configured, saving the configuration and reloading the PGW resolves the issue.

CSCti79332

When the PGW is switching traffic at a high data rate (approximately 1.2 million packets per seconds [mpps]) for more than 48 hours, the following error message along with a traceback is seen,

%PLATFORM-3-SAMI_INTRHOG: DMA interrupt is running for (xxx)usecs, more than 
(xxx)usecs.

This condition occurs when the PGW is connected to a Cisco CSG2 and there are 380K enabled sessions distributed over 500 APNs, all of which are configured with a different VRF, and the Gx and PCC features enabled, and the PGW is switching upstream and downstream data to these sessions at a high rate (1.2 mpps) for more than 48 hours.

Workaround: There is currently no known workaround.

Resolved Caveats

The following sections list caveats that have been resolved with Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1. Only severity 1 and 2 caveats and select severity 3 caveats are listed.

Cisco LTE PGW

Cisco SAMI

Cisco LTE PGW

The following PGW caveats are resolved in Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.

CSCth24607

A fatal error occurs on the active PGW after the virtual-template interface is modified and sessions are cleared using the clear gprs gtp pdp-context command.

CSCth45430

A traceback is seen on the Cisco LTE PGW. This condition occurs with downstream traffic greater than 1500 over IPv6 PDPs.

CSCth52695

The show sami sm imsi output fails to display existing PDP sessions. Additionally, after some time, the gprs gtp pdp tid command output also displays nothing.

This condition occurs with IPv6 create requests with different restart counters.

CSCth55339

Tracebacks are observed with GTP Version 0 (GTPv0) PDPs on IPv6 transport handoffs to GTPv1 on IPv4 transport, and again with handoffs to GTPv0 on IPv4 transport.

This condition occurs only when the handoff is between different IPv6/IPv4 transport.

Cisco SAMI

There are no SAMI caveats resolved with Cisco LTE PGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.

Caveats - Cisco LTE PGW Release 1.0, Cisco IOS Release 12.4(24)T3a

This section contains the following types of caveats that pertain to Cisco LTE PGW Release 1.0, Cisco IOS Release 12.4(24)T3a.

Open Caveats—Cisco LTE PGW

Open Caveats—Cisco SAMI

Open Caveats—Cisco LTE PGW

This section documents possible unexpected behavior by Cisco LTE PGW Release 1.0, Cisco IOS Release 12.4(24)T3a and describes only severity 1 and 2 caveats and select severity 3 caveats.

CSCth20123

Some sessions are deleted on the new standby PGW during the bulk synchronization after a switchover occurs.

This condition occurs with IPv6 transport, and IPv6 neighbor discovery for the next hop fails for approximately three minutes after the reload.

Workaround: Configure a static neighbor-to-IPv6 address mapping for the nexthop address for all GTP paths (for example ipv6 1:1:1:1::1 GigabitEthernet0/0.100 0022.3344.5566).

CSCth24607

A fatal error occurs on the active PGW after the virtual-template interface is modified and sessions are cleared using the clear gprs gtp pdp-context command.

Workaround: There is currently no known workaround.

CSCth45430

A traceback is seen on the Cisco LTE PGW. This condition occurs with downstream traffic greater than 1500 over IPv6 PDPs.

Workaround: There is currently no known workaround.

CSCth52695

The show sami sm imsi output fails to display existing PDP sessions. Additionally, after some time, the gprs gtp pdp tid command output also displays nothing.

This condition occurs with IPv6 create requests with different restart counters.

Workaround: There is currently no known workaround.

CSCth55339

Tracebacks are observed with GTP Version 0 (GTPv0) PDPs on IPv6 transport handoffs to GTPv1 on IPv4 transport, and again with handoffs to GTPv0 on IPv4 transport.

This condition occurs only when the handoff is between different IPv6/IPv4 transport.

Workaround: There is currently no known workaround.

Open Caveats—Cisco SAMI

This section lists the SAMI caveats that are open with Cisco LTE PGW Release 1.0, Cisco IOS Release 12.4(24)T3a.

CSCtg64608

The Cisco LTE gateway allows out of sequence traffic. This condition occurs when sending upstream traffic with the sequence number set to FFFF only with Mobile Express Forwarding (MEF). With Cisco Express Forwarding (CEF), the packets are dropped as designed.

Workaround: Use CEF instead of MEF.

Related Documentation

Except for feature modules, documentation is available as printed manuals or electronic documents. Feature modules are available online on Cisco.com.

Use these release notes with these documents:

Release-Specific Documents

Platform-Specific Documents

Cisco IOS Software Documentation Set

Release-Specific Documents

The following documents are specific to Cisco IOS Release 12.4 and are located at Cisco.com:

Cisco IOS Release 12.4 Mainline Release Notes

Documentation > Cisco IOS Software > Cisco IOS Software Releases 12.4 Mainline > Release Notes

Cisco IOS Release 12.4 T Release Notes

Documentation > Cisco IOS Software > Cisco IOS Software Releases 12.4 T > Release Notes


Note If you have an account with Cisco.com, you can use Bug Navigator II to find caveats of any severity for any release. You can reach Bug Navigator II on Cisco.com at http://www.cisco.com/support/bugtools.


Product bulletins, field notices, and other release-specific documents on Cisco.com at:

Documentation > Cisco IOS Software > Cisco IOS Software Releases 12.4 Mainline

Platform-Specific Documents

These documents are available for the Cisco 7600 series router platform on Cisco.com and the Documentation CD-ROM:

Cisco Service and Application Module for IP User Guide

Cisco 7600 series routers documentation:

Cisco 7600 Series Internet Router Installation Guide

Cisco 7600 Series Internet Router Module Installation Guide

Cisco 7609 Internet Router Installation Guide

Cisco 7600 series router documentation is available at:

http://www.cisco.com/en/US/products/hw/routers/ps368/products_installation_guides_books_list.html

Cisco IOS Software Documentation Set

The Cisco IOS software documentation set consists of the Cisco IOS configuration guides, Cisco IOS command references, and several other supporting documents that are shipped with your order in electronic form on the Documentation CD-ROM, unless you specifically ordered the printed versions.

Documentation Modules

Each module in the Cisco IOS documentation set consists of two books: a configuration guide and a corresponding command reference guide. Chapters in a configuration guide describe protocols, configuration tasks, Cisco IOS Software functionality, and contain comprehensive configuration examples. Chapters in a command reference guide list command syntax information. Use each configuration guide with its corresponding command reference. On Cisco.com at:

Documentation > Cisco IOS Software > Cisco IOS Software Releases 12.4 Mainline > Command References

Documentation > Cisco IOS Software > Cisco IOS Software Releases 12.4 Mainline > Command References > Configuration Guides


Note To view a list of MIBs supported by Cisco, by product, go to: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml


Implementing a Cisco LTE PGW Release 1.x on the Cisco SAMI

The following sections list related documentation (by category and then by task) to use when you implement a Cisco LTE PGW on the Cisco SAMI platform.

General Overview Documents

Core Cisco 7609 Router Documents

http://cisco.com/en/US/products/hw/routers/ps368/tsd_products_support_series_home.html

Documentation List by Task

For the most up-to-date list of documentation on the Cisco 7600 Series Router, refer to the Cisco 7600 Series Routers Documentation Roadmap on Cisco.com at:

http://cisco.com/en/US/docs/routers/7600/roadmaps/7600map.html

Getting Started

Cisco 7600 Series Internet Router Essentials

http://cisco.com/en/US/products/hw/routers/ps368/products_quick_start09186a0080092248.html

Regulatory Compliance and Safety Information for the Cisco 7600 Series Internet Routers

http://www.cisco.com/en/US/partner/docs/routers/7600/Hardware/RCSI/78_13690.html

Unpacking and installing the Cisco 7600 router:

Cisco 7600 Internet Router Installation Guide

http://www.cisco.com/en/US/partner/docs/routers/7600/Hardware/Chassis_Installation/7600_Series_Router_Installation_Guide/pref.html

Installing the supervisor module and configuring the router (basic configuration, such as VLANs, IP):

Cisco 7600 Series Internet Router Module Installation Guides

http://www.cisco.com/en/US/partner/products/hw/routers/ps368/prod_installation_guides_list.html

Cisco IOS Software Configuration Guide that applies to the latest release at the time of FCS

Installing and completing the Cisco SAMI configuration:

Cisco 7600 Series Internet Router Module Installation Guides

http://www.cisco.com/en/US/partner/products/hw/routers/ps368/prod_installation_guides_list.html

Cisco Service and Application Module for IP User Guide

http://www.cisco.com/en/US/docs/wireless/service_application_module/sami/user/guide/samiv1.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.