Guest

Cisco LTE PDN Gateway

Release Notes for Cisco LTE PDN Gateway Release 1.x on the Cisco SAMI, Cisco IOS Release 12.4(24)T3a1

  • Viewing Options

  • PDF (280.1 KB)
  • Feedback
Release Notes for Cisco LTE PDN Gateway Release 1.x on the Cisco SAMI, Cisco IOS Software Release 12.4 T3a Releases

Table Of Contents

Release Notes for Cisco LTE PDN Gateway Release 1.x on the Cisco SAMI,
Cisco IOS Software Release 12.4 T3a Releases

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 Implementations and Behavior Changes in Cisco LTE SGW Release 1.1

Configuring Local Service Record Information Generation

Configuring Specification Conformance

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.0 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.x on the Cisco SAMI,
Cisco IOS Software Release 12.4 T3a Releases


September 30, 2010

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

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, Cisco IOS Release 12.4(24)T3a1 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 IOS Release 12.4(24)T3a, 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 Implementations and Behavior Changes in Cisco LTE SGW Release 1.1

Caveats

Related Documentation

Implementing a Cisco LTE PGW Release 1.0 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) that was designed by 3GPP to provide 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 Paths represented by dashed lines are not supported by Cisco LTE PGW Release 1.1.


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 might be more than one PGW for that UE.

For each UE associated with the EPS, there is at least one PDN gateway (PGW) providing access to the requested PDN. If a UE is accessing multiple PDNs, there may 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 (Quality of Service [QoS], access control list [ACL], etc.)

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

Inservice 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 Mutlilayer 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)T3a 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 above, 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-Sep-10 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 Sep 28 2010
System restarted at 22:49:02 UTC Tue Sep 28 2010
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 will be 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 Implementations and Behavior Changes in Cisco LTE SGW Release 1.1

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 Conformance

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 above implementation, the service record information is sent by the Cisco CSG to the Cisco LTE PGW, which 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 above implementation, service information is generated by the PGW and added by the PGW 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 between 1 and 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 between 1 and 4294967295. The default is 1.



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


Configuring Specification Conformance

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 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 pre-configured 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

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.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 should 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 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.

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 sychronization after a switchover occurs.

This condition occurs with IPv6 transport, and IPv6 neighbor discovery for the next hop fails for a period of time (approximately 3 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.0 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.