Cisco LTE Serving Gateway on the Cisco SAMI, Cisco IOS Release 12.4(24)T33f
Available Languages
Table Of Contents
Hardware and Software Requirements
Determining the Software Version
Upgrading to a New Software Release
Limitations, Restrictions, and Important Notes
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T33f
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T32f
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T31f
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3f
Lookup Thread Health Monitoring
Write Memory Command Disabled on the TCOPs
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3e
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
Caveats - Cisco LTE SGW Release 1.3.7c, Cisco IOS Release 12.4(24)T33f
Caveats - Cisco LTE SGW Release 1.3.7b, Cisco IOS Release 12.4(24)T32f
Caveats - Cisco LTE SGW Release 1.3.7a, Cisco IOS Release 12.4(24)T31f
Caveats - Cisco LTE SGW Release 1.3.7, Cisco IOS Release 12.4(24)T3f
Caveats - Cisco LTE SGW Release 1.3.6, Cisco IOS Release 12.4(24)T3e
Caveats - Cisco LTE SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c
Caveats - Cisco LTE SGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d
Caveats - Cisco LTE SGW Release 1.3, Cisco IOS Release 12.4(24)T3c
Caveats - Cisco LTE SGW Release 1.2, Cisco IOS Release 12.4(24)T3b
Caveats - Cisco LTE SGW Release 1.1, Cisco IOS Release 12.4(24)T3a1
Caveats - Cisco LTE SGW Release 1.0, Cisco IOS Release 12.4(24)T3a
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco LTE Serving Gateway Release 1.3.7c on the Cisco SAMI,
Cisco IOS Software Release 12.4(24)T33f
Latest Publication Date: April 30, 2012, Cisco IOS Release 12.4(24)T33f
Last Publication Date: April 11, 2012, Cisco IOS Release 12.4(24)T32f
This release note describes the requirements, dependencies, and caveats for the Cisco Long Term Evolution (LTE) Serving Gateway (SGW) 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 the Cisco LTE SGW, Cisco IOS Releases 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:
•
MIBs
•
•
Cisco LTE SGW Overview
The following sections provide a brief overview of the Cisco LTE SGW:
LTE Evolved Packet Core
The Cisco LTE SGW 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:
•
•
•
•
The LTE EPC is made up of the following primary elements:
•
•
•
Figure 1 shows the interworking (and interfaces) of the LTE EPC with different radio access technologies.
Note
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.
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco LTE SGW Description
For each UE associated with the EPS, there is a single SGW at any given time.
The Cisco LTE SGW Release 1.x supports GTP-based non-roaming and roaming architectures, and control and data plane functions defined by 3GPP TS 23.401 for 3GPP access networks.
The Cisco LTE SGW provides the following support:
•
•
•
•
•
•
•
•
The Cisco LTE SGW 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 SGW Release 1.x and includes the following sections:
•
•
•
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
Hardware and Software Requirements
Implementing a Cisco LTE SGW Release 1.x on the Cisco 7600 series internet router platform requires the following hardware and software.
•
•
–
–
–
–
–
Or one of the following Cisco 7600 series Route Switch Processors running Cisco IOS Release 15.0(1)S or later:
–
–
–
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
•
Note
•
•
–
–
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:
SGW# show versionCisco IOS Software, SAMI Software (SAMI-L3IK9S-M), Experimental Version 12.4(20110919:095523)Copyright (c) 1986-2011 by Cisco Systems, Inc.Compiled Thu 22-Sep-11 17:06 byROM: System Bootstrap, Version 12.4(24r)MDB, RELEASE SOFTWARE (fc1)SGW uptime is 6 hours, 49 minutesSystem returned to ROM by address error at PC 0x977A0A4, address 0x977A0A4 at 11:24:24 UTC Thu Sep 22 2011System restarted at 17:13:18 IST Thu Sep 22 2011...SGW#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
MIBs
To view a list of MIBs supported by Cisco IOS Release 12.4(24)T33f, see the Cisco LTE Serving Gateway Configuration Guide.
Limitations, Restrictions, and Important Notes
When configuring the Cisco LTE SGW, note the following:
•
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 Cisco LTE SGW on the Cisco SAMI with the 2-GB memory option can support 380000 PDN connections and the 380000 of default bearers. When the maximum allowable number of bearers/PDP contexts is reached, the SGW refuses new mobile sessions until sessions are available.
•
–
–
–
!interface Virtual-Template1description GGSN-VTip unnumbered Loopback0encapsulation gtpno logging event link-statusgprs access-point-list gprsendNew 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)T33f
There are no new implementations or behavior changes in Cisco SGW Release 1.3.7c, Cisco IOS Release 12.4(24)T33f.
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T32f
There are no new implementations or behavior changes in Cisco SGW Release 1.3.7b, Cisco IOS Release 12.4(24)T32f.
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T31f
There are no new implementations or behavior changes in Cisco SGW Release 1.3.7a, Cisco IOS Release 12.4(24)T31f.
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3f
Cisco LTE SGW Release 1.3.7, Cisco IOS Release 12.4(24)T3f introduces the following enhancements, new implementations, and behavior changes:
•
•
Enhanced show Command Output
The following show commands have been enhanced in Cisco IOS Release 12.4(24)T3f:
show gprs charging statistics
The gprs charging statistics command output has been enhanced to include the following charging counters:
Total Number of Containers sent in CDR output msgs 0Total Number of Services sent in CDR output msgs 0* CDR Closed with causeNormal Release: 0 Abnormal Release: 0Volume Limit: 0Time Limit: 0SGSN Change: 0Management Intervention: 0 Management Intervention Partial: 0RAT Change: 0QOS Change: 0ULI Change: 0DT Change: 0Tariff Time Change: 0MS TimeZone Change: 0Container Count: 0Service Record Limit: 0Collection Timeout 0SGSN PLMN-ID Change: 0SGSN and PLMN-ID Change: 0
Note
show tech
The show tech command has been enhanced to include output for the show ip traffic command and the show sctp statistics command. Additionally, "dma controller statistics" are collected as part of the show platform command and displayed in the enhanced show tech command output.
Note
show gprs gtp statistics
The show gprs gtp statistics command output has been enhanced to include a "UP Req rejected for no S1-U (S) counter, which displays the number of times UBReq has been rejected at the SGW with no S1-U path.
Note
Lookup Thread Health Monitoring
The Cisco SAMI IXP has more than 50 lookup threads. In prior releases, if a few threads failed, the system did not report the failure right away, but continued to operate in a degraded mode.
Cisco IOS Release 12.4(24)T3f introduces a new mechanism that monitors the health of the lookup threads every second to ensure that the threads are functioning properly. If eight threads report a failure, the mechanism resets the system.
The following syslog message is printed to the PPC if the monitor mechanism detects a stuck thread:
SAMI 3/3: Oct 28 07:22:57.771: %PLATFORM-3-DP_IXP_THR_WARN: IXP:0 thread blocked. me:10 thr:7 num_consecutive_fail:3Once eight threads become stuck, the monitor mechanism prints the following syslog message and reloads the card:
SAMI 3/3: Oct 28 07:22:57.771: %PLATFORM-0-DP_IXP_MULT_THR_FAIL: IXP:0 multiple:8 threads hungBy default, the lookup thread monitor mechanism is enabled for both Cisco SAMI IXPs. To disable the monitor mechanism, use the no sami ixp monitor enable command. To re-enable the monitor mechanism, use the sami ixp monitor enable command.
Note
Write Memory Command Disabled on the TCOPs
With Cisco IOS Release 12.4(24)T3f, the write memory command is disabled on the Cisco SAMI Traffic and Control Plane processors (TCOPs). Disabling the write memory command on the TCOPs prevents unnecessary and redundant writes to NVRAM that previously occurred when using schedule jobs (cron table jobs) that executed the write memory command.
Note
SNMP Changes
In the CISCO-GGSN-EXT-MIB, the SNMP GetNext (snmpgetnext, snmpwalk) and the SNMP GetBulk (snmpbulkget) requests are disabled for the GGSN Subscriber table (cGgsnExtSubscriberTable). The entries of the GGSN Subscriber table are now available only through an SNMP GetOne request (snmpget).
Note
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3e
With Cisco LTE PGW Release 1.3.6, the following syslog messages have been introduced that identify a restart counter change has occurred that resulted in a particular MME being reloaded and the deletion of all contexts linked to that MME.
SAMI 3/4: %LTE_GTPV2-4-LTE_RESTART_COUNTER_CHANGED: GSN: 6.6.6.1, Sig src addr: 12.12.12.36, TID: 1111051000000021, MME: 12.12.12.36 Restart counter changed from 10 to 2, -Traceback= 0x9DC6904z 0x9E65E24z 0x9E948F4z 0x9E91804z 0x9E1CB2Cz 0xA279560z 0xA2795D0z 0x9E16654z 0x9E91584z 0x9E808A4z 0x9E88EECz 0x9E93F3Cz 0x830D7C0z 0x99C1DB8z 0x99C54BCzWhere,
•
•
•
•
•
The traceback is harmless and associated with the syslog message.
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T35c
There are no new implementations or behavior changes in Cisco SGW 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 SGW 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 SGW Release 1.3, Cisco IOS Release 12.4(24)T3c introduces support for the 3GPP change request (CR) 278. CR 278 specifies that when the SGW receives an Error Indication either for a Radio Network Controller (RNC) or from an eNodeB, it sends a Downlink Data Notification message to the S4 SGSN or to the MME, respectively. (CSCtj66053)
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3b
In compliance with Release 8.2.0, the following behavior changes have been introduced in Cisco IOS Release 12.4(24)T3b.
•
•
New Implementations and Behavior Changes in Cisco IOS Release 12.4(24)T3a1
Support for the following 3GPP specification CRs records for 29.274 has been introduced in Cisco LTE SGW Release 1.1, Cisco IOS Release 12.4(24)T3a1:
•
•
•
•
•
•
Additionally, commands to configure backward compliance have been added for the following 29.274 CRs:
•
•
•
To configure compliance for the above CR, complete the following tasks:
•
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:
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.
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.
Note
This section contains the caveats for the following releases:
•
•
•
•
•
•
•
•
•
•
•
Caveats - Cisco LTE SGW Release 1.3.7c, Cisco IOS Release 12.4(24)T33f
This section lists the open, resolved and unreproducible caveats that pertain to Cisco LTE SGW Release 1.3.7c, Cisco IOS Release 12.4(24)T33f.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
The following Cisco LTE SGW caveats are open in Cisco LTE SGW Release 1.3.7c, Cisco IOS Release 12.4(24)T33f.
•
The Cisco LTE SGW might drop update PDP context requests because of an International Mobile Subscriber Identity (IMSI) mandatory information element (IE) missing error. This condition occurs during a GTPv0-to-GTPv1 handoff or during a GTPv2-to-GTPv1 handoff if the IMSI is not present in the update PDP context request. The PGW/SGW considers this a mandatory IE instead of an optional ID, and drops the incoming request.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW Cisco Express Forwarding (CEF) packet drop counter increments.
This condition occurs when the Cisco LTE SGW is configured to buffer packets. When configured to buffer packets, the SGW buffers packets on a per bearer basis. SGW buffering is limited to 20 packets per second (pps) per bearer. The SGW drops packets exceeding this rate, which causes the CEF packet drop counter to increment.
Workaround: There is currently no known workaround.
•
Incorrect values for APN counters display when a PDP is reassigned to a different Traffic and Control Plane processor (TCOP).
This condition occurs only when a PDP is reassigned to a different TCOP.
Workaround: There is currently no known workaround.
•
The following syslog message might seen:
%IPC-3-SAMI_SM_FAIL_DUP_MSISDN: Unexpected condition: TCOP in IMSI-Sticky doesn't match with MSISDN-Sticky.This message might be seen with one of the following:
a.
b.
The message does not appear to impact any functionality.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW reloads during the PDP clean up function.
This reload occurs with the following conditions:
–
–
Workaround: There is currently no known workaround.
•
When polling of cGgsnExtSubscriberTable for GTPv2 calls, the trailing zeros of mobile station ISDN (MSISDNs) are ignored.
When there are calls whose MSISDN has trailing zeros, snmpget appears to function properly, even if the zeros are omitted, as seen in the following example command output:
pgw-03#show gprs gtp pdp-context msisdnTID MS Addr Source SGW Addr SGSN Addr MSISDN APN2233445566110010 10.0.3.230 LOCAL 111.111.111.13 N/A 2233445566110000 broadbandAlthough there is only one session, the following snmpget returns same value:
snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.12.50.50.51.51.52.52.53.53.54.54.49.49CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."223344556611" = STRING: 2233445566110010snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.14.50.50.51.51.52.52.53.53.54.54.49.49.48.48CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."22334455661100" = STRING: 2233445566110010snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.16.50.50.51.51.52.52.53.53.54.54.49.49.48.48.48.48CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."2233445566110000" = STRING: 2233445566110010Workaround: Ensure that the scenario like below does not occur (two calls with the same MSISDN, minus two trailing zeros at the end of one):
pgw-03#show gprs gtp pdp-context msisdnTID MS Addr Source SGW Addr SGSN Addr MSISDN APN2233445566110010 10.0.3.230 LOCAL 111.111.111.13 N/A 2233445566110000 broadband9933445566113314 10.0.3.250 LOCAL 111.111.111.13 N/A 22334455661100 broadband•
Negative values for global and path statistics are retrieved by the Mobile Wireless Transport Manager (MWTM) when polling standby gateway.
This condition occurs when the MWTM polls the GTP-MIB and the GTPv2-MIB on the standby gateway.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW does not send user location information (ULI) to the Cisco LTE PGW in the correct order. Therefore, the PGW sends incorrect ULI in P-CDRs.
This condition occurs when the SGW receives multiple ULI types. The SGW parses the ULI correctly, however, it does not send the ULI to the PGW in the correct order.
Workaround: There is currently no known workaround.
•
There are no counters present to verify the drops from pending_requestQ per PDP.
A maximum of 16 PDPs can be queued for processing. Currently, there are no counters to check the current status of the queue, and to see if any messages are dropped from the queue.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW sends the incorrect PDP type in S-CDRs.
This condition occurs after a GTPv1-to-GTPv2 handover. The PDN type is a conditional informational element (IE) in the create session request and is not sent from the MME in the create request for a GTPv1-to-GTPv2 handoff.
Workaround: There is currently no known workaround.
•
The Cisco LTE gateways print the following error message to the console if they receive a Version Not Supported message from the charging gateway.
%GTP-0-CORRUPTED_GTP_BYTE_STREAM: Corrupted byte stream, GSN: 172.16.57.15, Closing socket%GTP-0-PACKETPARSINGERROR: GSN: 172.16.78.83, TID: 00, APN: NULL, Reason: LFN in CHRG msg should be set%GTP-0-PACKETPARSINGERROR: GSN: 172.16.57.15, TID: 00, APN: NULL, Reason: Unexpected message 0x1AThis condition occurs because the Cisco LTE gateways are unable to parse the Version Not Supported packet. The TCP connection between LTE gateways and the charging gateway is re-established to recover from this condition.
Workaround: There is currently no known workaround.
•
Spurious memory access or crash occurs when executing the show gprs gtp pdp-context tid command or the show gprs gtp pdp-context imsi.
This condition occurs when the show gprs gtp pdp-context detailed output is waiting at the automore prompt, and a session or PDP context is modified by some control plane event that modifies or frees data structures.
Workaround: Before executing the show gprs gtp pdp-context command, disable the Cisco IOS automore feature by executing the terminal length 0 command in EXEC mode on the PCOP.
•
The Cisco LTE SGW sends a wild card "*" as the access point name in S-CDRs.
This condition occurs when an access point name in a create session request does not match any access point name in the APN list configured on the SGW.
Workaround: Configure all access point names to be used in the access point list.
•
The primary charging gateway is active on the Proxy Control Processor (PCOP) and the secondary charging gateway is active on the Traffic and Control Plane processors (TCOPs).
This condition occurs when the Version Not Support message is received on the gateway PCOP.
Workaround: The workaround for this condition is present in the code. The PCOP detects the mismatch of charging gateways on different processors and disconnects and reestablishes the TCP connection with the primary charging gateway.
Cisco SAMI Caveats
The following Cisco SAMI caveats are open with Cisco IOS Release 12.4(24)T33f.
•
In a redundant implementation, one of the Cisco SAMIs remains in a STANDBY-COLD state indefinitely. When in a STANDBY-COLD state, sessions are not sychronized to the standby Cisco SAMI.
This condition is seen on occasions when both of the Cisco SAMIs that are a part of a redundant implementation are reloaded at very close times.
Workaround: Reload the Cisco SAMI that is in STANDBY-COLD state.
•
On rare occasions, a Cisco SAMI coming up as a standby (in a redundant implementation) reloads immediately after booting up because of IXP network processor health monitoring failures.
These IXP health monitoring failures are only seen on Cisco SAMIs coming up as the standby gateway in a redundant implementation.
Workaround: The Cisco SAMI reloads correctly on its own on the next attempt.
•
The Cisco SAMI reloads due to an LCP-to-PPC health monitoring failure.
This reload occurs only when the very rare condition of a flash operation happening at the same time a software issues causes a crash.
Workaround: There is currently no known workaround.
•
The Cisco SAMI reboots with following logs displaying at the supervisor console:
Card in module slot_num, is being power-cycled off (Module not responding to Keep Alive polling)After the reload, the dir core: in LCP does not contain any logs that indicate the reason for the reload.
It is not clear what conditions trigger this error since there were no specific activities going through the LCP at the time the reload occurred.
Workaround: There is currently no known workaround.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.3.7c, Cisco IOS Release 12.4(24)T33f.
Cisco LTE SGW Caveats
This section list the SGW caveat that has been resolved in Cisco LTE SGW Release 1.3.7c, Cisco IOS Release 12.4(24)T33f.
•
The active Cisco LTE SGW crashes during the rare scenario in which an N3 x T3 transmission period timeout occurs for a Downlink Data Notification (DDN) message sent by the SGW to the MME at the same time a GTPv1-toGTPv2 handoff in progress for a session fails on the SGW.
In detail, this crash occurs with the following scenario:
a.
b.
c.
d.
e.
f.
g.
Cisco SAMI Caveats
There are no Cisco SAMI caveats newly resolved with Cisco LTE PGW Release 1.3.7c, Cisco IOS Release 12.4(24)T33f.
Caveats - Cisco LTE SGW Release 1.3.7b, Cisco IOS Release 12.4(24)T32f
This section lists the open, resolved and unreproducible caveats that pertain to Cisco LTE SGW Release 1.3.7b, Cisco IOS Release 12.4(24)T32f.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
The following Cisco LTE SGW caveats are open in Cisco LTE SGW Release 1.3.7b, Cisco IOS Release 12.4(24)T32f.
•
The Cisco LTE SGW might drop update PDP context requests because of an International Mobile Subscriber Identity (IMSI) mandatory information element (IE) missing error. This condition occurs during a GTPv0-to-GTPv1 handoff or during a GTPv2-to-GTPv1 handoff if the IMSI is not present in the update PDP context request. The PGW/SGW considers this a mandatory IE instead of an optional ID, and drops the incoming request.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW Cisco Express Forwarding (CEF) packet drop counter increments.
This condition occurs when the Cisco LTE SGW is configured to buffer packets. When configured to buffer packets, the SGW buffers packets on a per bearer basis. SGW buffering is limited to 20 packets per second (pps) per bearer. The SGW drops packets exceeding this rate, which causes the CEF packet drop counter to increment.
Workaround: There is currently no known workaround.
•
Incorrect values for APN counters display when a PDP is reassigned to a different Traffic and Control Plane processor (TCOP).
This condition occurs only when a PDP is reassigned to a different TCOP.
Workaround: There is currently no known workaround.
•
The following syslog message might seen:
%IPC-3-SAMI_SM_FAIL_DUP_MSISDN: Unexpected condition: TCOP in IMSI-Sticky doesn't match with MSISDN-Sticky.This message might be seen with one of the following:
a.
b.
The message does not appear to impact any functionality.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW reloads during the PDP clean up function.
This reload occurs with the following conditions:
–
–
Workaround: There is currently no known workaround.
•
When polling of cGgsnExtSubscriberTable for GTPv2 calls, the trailing zeros of mobile station ISDN (MSISDNs) are ignored.
When there are calls whose MSISDN has trailing zeros, snmpget appears to function properly, even if the zeros are omitted, as seen in the following example command output:
pgw-03#show gprs gtp pdp-context msisdnTID MS Addr Source SGW Addr SGSN Addr MSISDN APN2233445566110010 10.0.3.230 LOCAL 111.111.111.13 N/A 2233445566110000 broadbandAlthough there is only one session, the following snmpget returns same value:
snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.12.50.50.51.51.52.52.53.53.54.54.49.49CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."223344556611" = STRING: 2233445566110010snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.14.50.50.51.51.52.52.53.53.54.54.49.49.48.48CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."22334455661100" = STRING: 2233445566110010snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.16.50.50.51.51.52.52.53.53.54.54.49.49.48.48.48.48CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."2233445566110000" = STRING: 2233445566110010Workaround: Ensure that the scenario like below does not occur (two calls with the same MSISDN, minus two trailing zeros at the end of one):
pgw-03#show gprs gtp pdp-context msisdnTID MS Addr Source SGW Addr SGSN Addr MSISDN APN2233445566110010 10.0.3.230 LOCAL 111.111.111.13 N/A 2233445566110000 broadband9933445566113314 10.0.3.250 LOCAL 111.111.111.13 N/A 22334455661100 broadband•
Negative values for global and path statistics are retrieved by the Mobile Wireless Transport Manager (MWTM) when polling standby gateway.
This condition occurs when the MWTM polls the GTP-MIB and the GTPv2-MIB on the standby gateway.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW does not send user location information (ULI) to the Cisco LTE PGW in the correct order. Therefore, the PGW sends incorrect ULI in P-CDRs.
This condition occurs when the SGW receives multiple ULI types. The SGW parses the ULI correctly, however, it does not send the ULI to the PGW in the correct order.
Workaround: There is currently no known workaround.
•
There are no counters present to verify the drops from pending_requestQ per PDP.
A maximum of 16 PDPs can be queued for processing. Currently, there are no counters to check the current status of the queue, and to see if any messages are dropped from the queue.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW sends the incorrect PDP type in S-CDRs.
This condition occurs after a GTPv1-to-GTPv2 handover. The PDN type is a conditional informational element (IE) in the create session request and is not sent from the MME in the create request for a GTPv1-to-GTPv2 handoff.
Workaround: There is currently no known workaround.
•
The Cisco LTE gateways print the following error message to the console if they receive a Version Not Supported message from the charging gateway.
%GTP-0-CORRUPTED_GTP_BYTE_STREAM: Corrupted byte stream, GSN: 172.16.57.15, Closing socket%GTP-0-PACKETPARSINGERROR: GSN: 172.16.78.83, TID: 00, APN: NULL, Reason: LFN in CHRG msg should be set%GTP-0-PACKETPARSINGERROR: GSN: 172.16.57.15, TID: 00, APN: NULL, Reason: Unexpected message 0x1AThis condition occurs because the Cisco LTE gateways are unable to parse the Version Not Supported packet. The TCP connection between LTE gateways and the charging gateway is re-established to recover from this condition.
Workaround: There is currently no known workaround.
•
Spurious memory access or crash occurs when executing the show gprs gtp pdp-context tid command or the show gprs gtp pdp-context imsi.
This condition occurs when the show gprs gtp pdp-context detailed output is waiting at the automore prompt, and a session or PDP context is modified by some control plane event that modifies or frees data structures.
Workaround: Before executing the show gprs gtp pdp-context command, disable the Cisco IOS automore feature by executing the terminal length 0 command in EXEC mode on the PCOP.
•
The Cisco LTE SGW sends a wild card "*" as the access point name in S-CDRs.
This condition occurs when an access point name in a create session request does not match any access point name in the APN list configured on the SGW.
Workaround: Configure all access point names to be used in the access point list.
•
The primary charging gateway is active on the Proxy Control Processor (PCOP) and the secondary charging gateway is active on the Traffic and Control Plane processors (TCOPs).
This condition occurs when the Version Not Support message is received on the gateway PCOP.
Workaround: The workaround for this condition is present in the code. The PCOP detects the mismatch of charging gateways on different processors and disconnects and reestablishes the TCP connection with the primary charging gateway.
Cisco SAMI Caveats
The following Cisco SAMI caveats are open with Cisco IOS Release 12.4(24)T32f.
•
In a redundant implementation, one of the Cisco SAMIs remains in a STANDBY-COLD state indefinitely. When in a STANDBY-COLD state, sessions are not sychronized to the standby Cisco SAMI.
This condition is seen on occasions when both of the Cisco SAMIs that are a part of a redundant implementation are reloaded at very close times.
Workaround: Reload the Cisco SAMI that is in STANDBY-COLD state.
•
On rare occasions, a Cisco SAMI coming up as a standby (in a redundant implementation) reloads immediately after booting up because of IXP network processor health monitoring failures.
These IXP health monitoring failures are only seen on Cisco SAMIs coming up as the standby gateway in a redundant implementation.
Workaround: The Cisco SAMI reloads correctly on its own on the next attempt.
•
The Cisco SAMI reloads due to an LCP-to-PPC health monitoring failure.
This reload occurs only when the very rare condition of a flash operation happening at the same time a software issues causes a crash.
Workaround: There is currently no known workaround.
•
The Cisco SAMI reboots with following logs displaying at the supervisor console:
Card in module slot_num, is being power-cycled off (Module not responding to Keep Alive polling)After the reload, the dir core: in LCP does not contain any logs that indicate the reason for the reload.
It is not clear what conditions trigger this error since there were no specific activities going through the LCP at the time the reload occurred.
Workaround: There is currently no known workaround.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.3.7b, Cisco IOS Release 12.4(24)T31f.
Cisco LTE SGW Caveats
This section lists the SGW caveats that are resolved in Cisco LTE SGW Release 1.3.7b, Cisco IOS Release 12.4(24)T32f.
•
Cisco LTE SGW might not respond to a Modify Bearer Command message from Mobility Management Entity (MME).
This happens when MME sends Modify Bearer Command request to the SGW as part of a 3G-to-4G handoff procedure. The SGW does not support the Modify Bearer Command message; therefore it might not might not respond to the message or might respond incorrectly.
Cisco SAMI Caveats
The following Cisco SAMI caveats are resolved with Cisco LTE SGW Release 1.3.7b, Cisco IOS Release 12.4(24)T32f.
•
Crashinfo and Debuginfo contains only one single line. This condition is not specific to any crash and can occur because of an RF-induced reload, software crash, health monitoring failure, etcetera.
•
After a reload, the show version command output displays the reload reason as "System returned to ROM by error - Bus Error, PC 0x0."
This condition occurs when a PPC encounters a machine check exception due to a PC bus error.
•
The show version command output after a Cisco SAMI reload displays the Proxy Control Processor (PCOP) reload reason as "reloaded by admin" when a Traffic and Control Processor (TCOP) reloads because of a machine check exception (PC bus error).
This condition exists with a Cisco SAMI reload due to the machine check exception (PC bus error) seen in a TCOP.
Unreproducible Caveats
The following caveats have not been reproduced with Cisco LTE PGW Release 1.3.7b, Cisco IOS Release 12.4(24)T32f.
•
A Traffic and Control Plane processor (TCOP) triggers RF-induced reload of the standby.
This condition occurs due to an "Out of Window" data reception in the TCOP.
•
The Cisco SAMI reloads with the following error message:
%SAMI-2-SAMI_SYSLOG_CRIT: SAMI 1/0: %SAMI-2-443001: System experienced fatal failure.Service name:System Manager (core-server)(30380) has terminated on receiving signal 11,reloading systemAs part of the crash info, the core file "qnx_1_io-net_114693_core" is generated. "114693" is the process ID for network I/O support (io-net), and might vary from case to case.
Conditions that might cause this reload are not known.
Caveats - Cisco LTE SGW Release 1.3.7a, Cisco IOS Release 12.4(24)T31f
This section lists the open, resolved and unreproducible caveats that pertain to Cisco LTE SGW Release 1.3.7a, Cisco IOS Release 12.4(24)T31f.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
The following Cisco LTE SGW caveats are open in Cisco LTE SGW Release 1.3.7a, Cisco IOS Release 12.4(24)T31f.
•
The Cisco LTE SGW might drop update PDP context requests because of an International Mobile Subscriber Identity (IMSI) mandatory information element (IE) missing error. This condition occurs during a GTPv0-to-GTPv1 handoff or during a GTPv2-to-GTPv1 handoff if the IMSI is not present in the update PDP context request. The PGW/SGW considers this a mandatory IE instead of an optional ID, and drops the incoming request.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW Cisco Express Forwarding (CEF) packet drop counter increments.
This condition occurs when the Cisco LTE SGW is configured to buffer packets. When configured to buffer packets, the SGW buffers packets on a per bearer basis. SGW buffering is limited to 20 packets per second (pps) per bearer. The SGW drops packets exceeding this rate, which causes the CEF packet drop counter to increment.
Workaround: There is currently no known workaround.
•
The counters for the G-PDU bits in the Cisco Mobile Wireless Transport Manger (MWTM) display a negative value.
Workaround: There is currently no known workaround.
•
Incorrect values for APN counters display when a PDP is reassigned to a different Traffic and Control Plane processor (TCOP).
This condition occurs only when a PDP is reassigned to a different TCOP.
Workaround: There is currently no known workaround.
•
The following syslog message might seen:
%IPC-3-SAMI_SM_FAIL_DUP_MSISDN: Unexpected condition: TCOP in IMSI-Sticky doesn't match with MSISDN-Sticky.This message might be seen with one of the following:
a.
b.
The message does not appear to impact any functionality.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW reloads during the PDP clean up function.
This reload occurs with the following conditions:
–
–
Workaround: There is currently no known workaround.
•
When polling of cGgsnExtSubscriberTable for GTPv2 calls, the trailing zeros of mobile station ISDN (MSISDNs) are ignored.
When there are calls whose MSISDN has trailing zeros, snmpget appears to function properly, even if the zeros are omitted, as seen in the following example command output:
pgw-03#show gprs gtp pdp-context msisdnTID MS Addr Source SGW Addr SGSN Addr MSISDN APN2233445566110010 10.0.3.230 LOCAL 111.111.111.13 N/A 2233445566110000 broadbandAlthough there is only one session, the following snmpget returns same value:
snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.12.50.50.51.51.52.52.53.53.54.54.49.49CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."223344556611" = STRING: 2233445566110010snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.14.50.50.51.51.52.52.53.53.54.54.49.49.48.48CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."22334455661100" = STRING: 2233445566110010snmpget -v 2c 130.130.0.10 -c abc cGgsnExtSubscriberTid.16.50.50.51.51.52.52.53.53.54.54.49.49.48.48.48.48CISCO-GGSN-EXT-MIB::cGgsnExtSubscriberTid."2233445566110000" = STRING: 2233445566110010Workaround: Ensure that the scenario like below does not occur (two calls with the same MSISDN, minus two trailing zeros at the end of one):
pgw-03#show gprs gtp pdp-context msisdnTID MS Addr Source SGW Addr SGSN Addr MSISDN APN2233445566110010 10.0.3.230 LOCAL 111.111.111.13 N/A 2233445566110000 broadband9933445566113314 10.0.3.250 LOCAL 111.111.111.13 N/A 22334455661100 broadband•
Negative values for global and path statistics are retrieved by the Mobile Wireless Transport Manager (MWTM) when polling standby gateway.
This condition occurs when the MWTM polls the GTP-MIB and the GTPv2-MIB on the standby gateway.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW does not send user location information (ULI) to the Cisco LTE PGW in the correct order. Therefore, the PGW sends incorrect ULI in P-CDRs.
This condition occurs when the SGW receives multiple ULI types. The SGW parses the ULI correctly, however, it does not send the ULI to the PGW in the correct order.
Workaround: There is currently no known workaround.
•
There are no counters present to verify the drops from pending_requestQ per PDP.
A maximum of 16 PDPs can be queued for processing. Currently, there are no counters to check the current status of the queue, and to see if any messages are dropped from the queue.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW sends the incorrect PDP type in S-CDRs.
This condition occurs after a GTPv1-to-GTPv2 handover. The PDN type is a conditional informational element (IE) in the create session request and is not sent from the MME in the create request for a GTPv1-to-GTPv2 handoff.
Workaround: There is currently no known workaround.
•
The Cisco LTE gateways print the following error message to the console if they receive a Version Not Supported message from the charging gateway.
%GTP-0-CORRUPTED_GTP_BYTE_STREAM: Corrupted byte stream, GSN: 172.16.57.15, Closing socket%GTP-0-PACKETPARSINGERROR: GSN: 172.16.78.83, TID: 00, APN: NULL, Reason: LFN in CHRG msg should be set%GTP-0-PACKETPARSINGERROR: GSN: 172.16.57.15, TID: 00, APN: NULL, Reason: Unexpected message 0x1AThis condition occurs because the Cisco LTE gateways are unable to parse the Version Not Supported packet. The TCP connection between LTE gateways and the charging gateway is re-established to recover from this condition.
Workaround: There is currently no known workaround.
•
Spurious memory access or crash occurs when executing the show gprs gtp pdp-context tid command or the show gprs gtp pdp-context imsi.
This condition occurs when the show gprs gtp pdp-context detailed output is waiting at the automore prompt, and a session or PDP context is modified by some control plane event that modifies or frees data structures.
Workaround: Before executing the show gprs gtp pdp-context command, disable the Cisco IOS automore feature by executing the terminal length 0 command in EXEC mode on the PCOP.
•
The Cisco LTE SGW sends a wild card "*" as the access point name in S-CDRs.
This condition occurs when an access point name in a create session request does not match any access point name in the APN list configured on the SGW.
Workaround: Configure all access point names to be used in the access point list.
•
The primary charging gateway is active on the Proxy Control Processor (PCOP) and the secondary charging gateway is active on the Traffic and Control Plane processors (TCOPs).
This condition occurs when the Version Not Support message is received on the gateway PCOP.
Workaround: The workaround for this condition is present in the code. The PCOP detects the mismatch of charging gateways on different processors and disconnects and reestablishes the TCP connection with the primary charging gateway.
Cisco SAMI Caveats
The following Cisco SAMI caveats are open with Cisco IOS Release 12.4(24)T31f.
•
In a redundant implementation, one of the Cisco SAMIs remains in a STANDBY-COLD state indefinitely. When in a STANDBY-COLD state, sessions are not sychronized to the standby Cisco SAMI.
This condition is seen on occasions when both of the Cisco SAMIs that are a part of a redundant implementation are reloaded at very close times.
Workaround: Reload the Cisco SAMI that is in STANDBY-COLD state.
•
On rare occasions, a Cisco SAMI coming up as a standby (in a redundant implementation) reloads immediately after booting up because of IXP network processor health monitoring failures.
These IXP health monitoring failures are only seen on Cisco SAMIs coming up as the standby gateway in a redundant implementation.
Workaround: The Cisco SAMI reloads correctly on its own on the next attempt.
•
A Traffic and Control Plane processor (TCOP) triggers RF induced reload of the standby.
This condition occurs due to an "Out of Window" data reception in the TCOP.
Workaround: There is currently no known workaround.
•
The Cisco SAMI reloads due to an LCP-to-PPC health monitoring failure.
This reload occurs only when the very rare condition of a flash operation happening at the same time a software issues causes a crash.
Workaround: There is currently no known workaround.
•
The Cisco SAMI reboots with following logs displaying at the supervisor console:
Card in module slot_num, is being power-cycled off (Module not responding to Keep Alive polling)After the reload, the dir core: in LCP does not contain any logs that indicate the reason for the reload.
It is not clear what conditions trigger this error since there were no specific activities going through the LCP at the time the reload occurred.
Workaround: There is currently no known workaround.
•
The Cisco SAMI reloads with the following error message:
%SAMI-2-SAMI_SYSLOG_CRIT: SAMI 1/0: %SAMI-2-443001: System experienced fatal failure.Service name:System Manager (core-server)(30380) has terminated on receiving signal 11,reloading systemAs part of the crash info, the core file "qnx_1_io-net_114693_core" is generated. "114693" is the process ID for network I/O support (io-net), and might vary from case to case.
Conditions that might cause this reload are not known.
Workaround: There is currently no known workaround.
•
Crashinfo and Debuginfo contains only one single line. This condition is not specific to any crash and can occur because of an RF-induced reload, software crash, health monitoring failure, etcetera.
Workaround: There is currently no known workaround.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.3.7a, Cisco IOS Release 12.4(24)T31f.
Cisco LTE SGW Caveats
This section lists the SGW caveats that are resolved in Cisco LTE SGW Release 1.3.7a, Cisco IOS Release 12.4(24)T31f.
•
SGW call data records (SGW-CDRs) report more volume upload and download bytes than the PDN CDRs (PGW-CDRs) for the session.
The following actions cause the S-CDR traffic volume count to be higher than the P-CDR service record count:
a.
b.
c.
•
The standby gateway reloads due to a Stream Control Transmission Protocol (SCTP) failure because of the interface queue of a Traffic and Control Plane processors TCOP reaches maximum capacity.
This condition occurs when a lot of GTPv2-C messages are sent and the interface queue on the TCOP reaches the maximum value of 600. The queue fills for one of the following two reasons:
a.
b.
•
On the Cisco LTE SGW, there might be a case when sending an Update Bearer Request (UBR) results in a a loop. This loop condition occurs when the UBR is rejected while a Re-Auth-Request (RAR) triggered UBR is retried and the S1-U is established, and subsequent UBRs are rejected.
•
The Cisco LTE SGW might reload when the eNodeB is not reachable during data path setup and the SGW is still trying to resolve the MAC, and the data path towards eNodeB is cleaned due to some other trigger such as a RAB or session deletion.
This reload is seen only if an eNodeB is not reachable during path setup and at the same time, data path deletion is triggered by another even such as the receipt of a RAB or session deletion.
Also, this reload occurs only if the time events are not handled in the correct sequence due to a TCOP processing a high load.
•
The S-CDR byte count is not correct.
This condition occurs with the data bytes in a container closed with Cause for Record Closing.
Cisco SAMI Caveats
The following Cisco SAMI caveat is resolved with Cisco LTE SGW Release 1.3.7a, Cisco IOS Release 12.4(24)T31f.
•
After certain types of reloads (specified below), the Proxy Control Processor (PCOP) reports the reload reason as "Returned to Rommon due to PC Bus Error 0x0." The Debuginfo collected for the PCOP as part of the reload is truncated.
This condition occurs with the following:
a.
b.
c.
Caveats - Cisco LTE SGW Release 1.3.7, Cisco IOS Release 12.4(24)T3f
This section lists the open, resolved and unreproducible caveats that pertain to Cisco LTE SGW Release 1.3.7, Cisco IOS Release 12.4(24)T3f.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
The following Cisco LTE SGW caveats are open in Cisco LTE SGW Release 1.3.7, Cisco IOS Release 12.4(24)T3f.
•
The Cisco LTE SGW might drop update PDP context requests because of an IMSI mandatory IE missing error. This condition occurs during a GTPv0-to-GTPv1 handoff or during a GTPv2-to-GTPv1 handoff if the IMSI is not present in the update PDP context request. The SGW considers this a mandatory IE instead of an optional ID, and drops the incoming request.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW Cisco Express Forwarding (CEF) packet drop counter increments.
This condition occurs when the Cisco LTE SGW is configured to buffer packets. When configured to buffer packets, the SGW buffers packets on a per bearer basis. SGW buffering is limited to 20 packets per second (pps) per bearer. The SGW drops packets exceeding this rate, which causes the CEF packet drop counter to increment.
Workaround: There is currently no known workaround.
•
The following syslog message might seen:
%IPC-3-SAMI_SM_FAIL_DUP_MSISDN: Unexpected condition: TCOP in IMSI-Sticky doesn't match with MSISDN-Sticky.This message might be seen with one of the following:
a.
b.
The message does not appear to impact any functionality.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW reloads during the PDP clean up function.
This reload occurs with the following conditions:
–
–
Workaround: There is currently no known workaround.
•
RF-induced reloads are triggered by the TCOPs. This condition occurs in an Active/Standby redundant implementation.
Workaround: There is currently no known workaround.
•
SGW call detail records (S-CDRs) report more volume upload and download bytes than the PDN CDRs (P-CDRs) for the session.
The following actions cause the S-CDR traffic volume count to be higher than the P-CDR service record count:
a.
b.
c.
Workaround: There is currently no known workaround.
Cisco SAMI Caveats
The following Cisco SAMI caveats are open with Cisco IOS Release 12.4(24)T3f.
•
In a redundant implementation, one of the Cisco SAMIs remains in a STANDBY-COLD state indefinitely. When in a STANDBY-COLD state, sessions are not sychronized to the standby Cisco SAMI.
This condition is seen on occasions when both of the Cisco SAMIs that are a part of a redundant implementation are reloaded at very close times.
Workaround: Reload the Cisco SAMI that is in STANDBY-COLD state.
•
On rare occasions, a Cisco SAMI coming up as a standby (in a redundant implementation) reloads immediately after booting up because of IXP network processor health monitoring failures.
These IXP health monitoring failures are only seen on Cisco SAMIs coming up as the standby gateway in a redundant implementation.
Workaround: Reload the Cisco SAMI. The module usually reloads correctly on the next attempt.
•
The Cisco SAMI reloads because of a health monitoring failure and the following syslog message is generated:
%PLATFORM-4-DP_HM_WARN: Failed to receive response from IXP1 in 22 retries, system will reboot if it continues to fail receiving response in another 8 retries (i.e. in the next 80 secs.) Check `sami health-monitoring' configuration and see `show sami health-monitoring' for more infoThis condition occurs when the Cisco SAMI network processor (IXP) fails to respond to health monitor messages sent from a PowerPC (PPC).
Workaround: There is currently no known workaround.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.3.7, Cisco IOS Release 12.4(24)T3f.
Cisco LTE SGW Caveats
This section lists the SGW caveats that are resolved in Cisco LTE SGW Release 1.3.7, Cisco IOS Release 12.4(24)T3f.
•
When an snmpwalk is run on a complete Management Information Base (MIB) Object Identifier (OID) tree against an SGW or PGW that has no bearers/PDPs, the CPU usage is approximately 20 percent. With 50,000 create and delete session requests, but no snmpwalk running, the CPU usage is approximately 20 percent. However, when an snmpwalk and the 50,000 create and delete session requests are combined, the CPU usage climbs to 99 percent.
The high CPU condition is seen when the 50,000 create and delete session requests and an snmpwalk of the entire MIB tree occur at the same time.
•
The SNMP-ENGINE process might leak memory on the PGW/SGW gateways when the path history table is polled.
•
GTP Version 1 (GTPv1) PDPs become stuck during standby-to-active switchover.
This condition occurs with the Cisco LTE SGW or Cisco LTE PGW when PDPs are being deleted because of a new recovery information element (IE) value in the active gateway, which indicates a path restart, while the standby gateway is coming up and starts receiving bulk synchronization for create PDPs from the active gateway.
The active gateway immediately reloads after the bulk synchronization when there are PDPs remaining on the restarting path of the active gateway.
•
The mobile station ISDN (MSISDN) is not present in SGW call detail records (S-CDRs). This condition occurs after a 3G-to4G handoff.
•
A high CPU is seen on the Cisco LTE gateway (PGW or SGW) with an SNMP GetBulk request on an object identifier (OID) polls the subscriber table.
•
The gateway crashes when displaying path history tables. The path history tables are not empty and entries change simultaneously when the show gprs gtp path history command is executed.
Cisco SAMI Caveats
The following Cisco SAMI caveats are resolved with Cisco LTE SGW Release 1.3.7, Cisco IOS Release 12.4(24)T3f.
•
A specific configuration sequence causes a configuration download/parse error on the SAMI.
The condition is logged as follows:
SAMI 1/3: Feb 18 09:27:43.779: %IPC-0-CFG_DOWNLOAD_ERROR: Configurationdownload/parse error: Failed to download config on one or more processors,traffic will get blocked -Process= "Init", ipl= 0, pid= 3If inter-device redundancy is configured, a peer SAMI might reload with the redundancy framework (RF)/Cisco IOS Hot Standby Routing Protocol (HSRP) state broken.
The following configuration sequence causes the configuration download/parse error:
a.
b.
c.
d.
After the reload, the SAMI receives the configuration download/parse error.
•
A configuration download error occurs with the following message:
%IPC-0-CFG_DOWNLOAD_ERROR: Configuration download/parse error: Failed to downloadconfig on one or more processors, traffic will get blocked -Process= "Init", ipl= 0,pid= 3This condition occurs when the erase bootflash command is issued on the PCOP.
•
When the Cisco SAMI IXP statistics counters increase to larger values, writing those values to print buffer causes the following traceback:
SAMI 2/3: 000049: Sep 17 22:08:58: %SAMI-4-WARNING: Unexpected condition: Badstring length, output truncated -Process= "Virtual Exec", ipl= 0, pid= 243, -Traceback= 0x4586BB38z 0x4586BC28z 0x4586F7B8z 0x448A9B0Cz 0x44888930z0x4585E9ACz 0x44888A98z 0x448A9B0Cz 0x448D06F0z 0x459906F8z0x45993DFCzATTSGW52#This traceback is visible when the show tech command or show sami ixp statistics command is executed. Additionally, this traceback causes no functional impact and is more likely to occur if the Cisco SAMI has been up for multiple days.
•
While debugging, it is observed on rare occasions that all of the lookup threads become stuck, resulting in the IXP not processing any packets. The Cisco SAMI IXP has more than 50 look threads. If a few threads fail, the system might not report the failure right away, but continue to work in degraded mode.
•
Scheduled jobs (cron table jobs) execute the write memory command on the Cisco SAMI TCOPs. The cron job is a distributed command, which means it is propagated to the TCOPs.
The Cisco SAMI single IP architecture does not use TCOP configuration files in NVRAM. The TCOP configurations are driven by the PCOP, which retrieves the configuration file from the supervisor. Executing the write memory command in the TCOPs saves the configuration in the TCOP NVRAM. This is an unnecessary and redundant write to NVRAM.
With this fix, the write memory command is disabled at the TCOPs.
•
The Cisco LTE SGW sends a modify bearer response with a cause code reserved value "0" when it receives a modify bearer request for an eNodeB update that does not contain User Location Information.
Caveats - Cisco LTE SGW Release 1.3.6, Cisco IOS Release 12.4(24)T3e
This section lists the open, resolved and unreproducible caveats that pertain to Cisco LTE SGW Release 1.3.6, Cisco IOS Release 12.4(24)T3e.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
The following SGW caveat is open in Cisco LTE SGW Release 1.3.6, Cisco IOS Release 12.4(24)T3e.
•
When an snmpwalk is run on a complete Management Information Base (MIB) Object Identifier (OID) tree against an SGW or PGW that has no bearers/PDPs, the CPU usage is approximately 20 percent. With 50,000 create and delete session requests, but no snmpwalk running, the CPU usage is approximately 20 percent. However, when an snmpwalk and the 50,000 create and delete session requests are combined, the CPU usage climbs to 99 percent.
The high CPU condition is seen when the 50,000 create and delete session requests and an snmpwalk of the entire MIB tree occur at the same time.
Workaround: There is currently no known work around.
•
The Cisco SAMI reloads because of a health monitoring failure and the following syslog message is generated:
%PLATFORM-4-DP_HM_WARN: Failed to receive response from IXP1 in 22 retries, system will reboot if it continues to fail receiving response in another 8 retries (i.e. in the next 80 secs.) Check `sami health-monitoring' configuration and see `show sami health-monitoring' for more infoThis condition occurs when the Cisco SAMI network processor (IXP) fails to respond to health monitor messages sent from a PowerPC (PPC).
Workaround: There is currently no known workaround.
•
GTP Version 1 (GTPv1) PDPs become stuck during standby-to-active switchover. This condition occurs with the Cisco LTE SGW or Cisco LTE PGW when PDPs are being deleted because of a new recovery information element (IE) value in the active gateway, which indicates a path restart, while the standby gateway is coming up and starts receiving bulk synchronization for create PDPs from the active gateway.
The active gateway immediately reloads after the bulk synchronization when there are PDPs remaining on the restarting path of the active gateway.
Workaround: There is currently no known workaround.
•
The Cisco LTE SGW Cisco Express Forwarding (CEF) packet drop counter increments.
This condition occurs when the Cisco LTE SGW is configured to buffer packets. When configured to buffer packets, the SGW buffers packets on a per bearer basis. SGW buffering is limited to 20 packets per second (pps) per bearer. The SGW drops packets exceeding this rate, which causes the CEF packet drop counter to increment.
Workaround: There is currently no known workaround.
•
The Cisco Mobile Wireless Transport Manager (MWTM) displays negative values for free memory.
Workaround: There is currently no known workaround.
Cisco SAMI Caveats
There are no known Cisco SAMI caveats open with Cisco IOS Release 12.4(24)T3e.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.3.6, Cisco IOS Release 12.4(24)T3e.
Cisco LTE SGW Caveats
This section lists the SGW caveat that is resolved with Cisco LTE SGW Release 1.3.6, Cisco IOS Release 12.4(24)T3e.
•
When an snmpwalk is run on a complete Management Information Base (MIB) Object Identifier (OID) tree against an SGW or PGW that has no bearers/PDPs, the CPU usage is approximately 20 percent. With 50,000 create and delete session requests, but no snmpwalk running, the CPU usage is approximately 20 percent. However, when an snmpwalk and the 50,000 create and delete session requests are combined, the CPU usage climbs to 99 percent.
The high CPU condition is seen when the 50,000 create and delete session requests and an snmpwalk of the entire MIB tree occur at the same time.
•
The PDP context becomes stuck on the Cisco LTE Serving Gateway (SGW).
This condition occurs when a delete session request is sent to the Mobile Management Entity (MME) for the PDP when the SGW is waiting for a delete bearer response message from the MME.
•
Lawful interception fails to do provision a mediation device (MD) and an snmpset request returns a "No-Creation" error. Additionally, an snmpwalk returns nothing from the SNMP Mediation Table.
This condition occurs only when the incorrect ifIndex is used in snmpset.
Cisco SAMI Caveats
This section lists the Cisco SAMI caveats that are resolved with Cisco LTE SGW Release 1.3.6, Cisco IOS Release 12.4(24)T3e.
•
The ucdump -t command does not recognize VLAN and L2VD tables as valid arguments.
The condition relates only to the display of the VLAN and L2VD tables using the ucdump -t command from the IXP console. The tables are setup correctly and traffic is forwarded successfully based on these tables.
•
The Cisco SAMI IXP micro-engine threads used to configure data paths might take a lock on tables and not freeing it, thereby holding the lock indefinitely.
This fix catches these issues for debugging purposes. Use the ucdump -t LOCK command to dump debugging information when a lock is held infinitely.
•
Continuous IXP IPC failure error messages are seen from the Cisco SAMI:
%PLATFORM-3-SAMI_IPC_IXP_FAIL: IPC timed out for IXP<ixp no> for Msgcode <msg>, Num tries: <tries>This condition typically occurs when the Cisco SAMI IXP stops processing IPC messages from the Cisco SAMI processors.
•
The syslog messages "PLATFORM-3-SAMI_IPC_IXP_FAIL:" is observed when the Cisco SAMI IXP receives out of order configuration messages, for example, when the IXP receives a modify PDP request before a create PDP request or after a free PDP message.
•
The Cisco SAMI reloads with the following syslog error message
"%PLATFORM-1-DP_HM_FAIL: Failed to receive response from IXP<1/2>. Check `sami health-monitoring' configuration and see `show sami health-monitoring' for more info"The condition occurs when the network processor (IXP) fails to respond to Health Monitoring (HM) messages sent by the SAMI PowerPCs (PPCs).
The IXP maintains packets, including HM messages, in DRAM buffers. The pointers to these buffers (also known as the buffer handles) are maintained by q-arrays. Expected behavior is that the q-arrays provide valid buffer handles, however, when a Null (invalid) buffer handle is de-queued by q-array, the hardware assist, which maintains the q-array buffer becomes corrupted and the IXP reaches a state where it does not process incoming packets any longer.
Caveats - Cisco LTE SGW 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 SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
This section lists the SGW caveats that are open in Cisco LTE SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.
•
Sessions remain stale in the Cisco LTE SGW.
This condition occurs when a bearer resource create (BRC) is sent with a bidirectional traffic flow template (TFT) from the Mobility Management Entity (MME), and the SGW forwards the same to Cisco LTE PGW. The PGW rejects the BRC and replies to the SGW with bearer resource failure indication (BRFI). The SGW rejects the BRFI from the PGW.
Workaround: Reconnect or perform a local clear on the SGW to remove the stale session.
Cisco SAMI Caveats
This section lists the SAMI caveats that are open with Cisco LTE SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.
•
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.
•
Mobile Express Forwarding (MEF) stops forwarding packets in the Cisco LTE SGW.
This condition occurs when the Cisco LTE SGW receives a packet in which the inner IP packet is malformed. Specifically, the length field of the inner packet has a corrupted value.
Workaround: Disable MEF using the no mef access-point configuration command.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.
Cisco LTE SGW Caveats
This section lists the SGW caveats that are resolved with Cisco LTE SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.
•
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.
•
In a redundant implementation, the requested APN Aggregate Maximum Bit Rate (APN-AMBR) values are not synced to the standby Cisco LTE SGW.
This condition occurs when the session is created.
•
The Cisco LTE SGW crashes when a error indication is received from eNodeB/Radio Network Controller (RNC) for a dual-stack APN PDP context.
This condition occurs when change request (CR) 278 of 3GPP TS 29.274 is enabled on the SGW by using the cr LTE compliance profile command, and the dual-stack session is deleted in the eNodeB/RNC and the SGW forwards downstream data to it.
•
A progressive memory leak occurs on the Cisco LTE SGW Proxy Control Processor (PCOP) when there is a Connection Set Identifier (CSID) delete PDP connection response failure received.
5C79CCB4 148 45DB85BC 52 SingleIP PCOP S Single IP GGSN Parser0x45DB85BC:lte_singleip_sm_parse_gtp(0x45db8500)+0xbcThis condition occurs when the SGW deletes a set of PDP contexts that have a common CSID and sends a delete PDN connection request to the Cisco LTE PGW. The PGW returns a negative response.
•
Downstream data traffic is sent to the Cisco LTE SGW instead of an SGSN when a GTPv1 to GTPv2 handover failure occurs because of Quality of Service (QoS).
This condition occurs with the following sequence of events:
1.
2.
3.
•
In a redundant implementation, a memory leak occurs on the active Cisco LTE SGW Traffic and Control Plane processors (TCOPs) after a couple of hours of continuous traffic and PDP context creates and deletes.
This condition occurs when the path protocol to the charging gateway is TCP (gprs charging path-protocol tcp).
Cisco SAMI Caveats
This section lists the Cisco SAMI caveats that are resolved with Cisco LTE SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.
•
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.
•
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 IEThe RAT type is set to null.
Miscellaneous Caveats
This section lists a miscellaneous Cisco IOS software caveat that is resolved with Cisco LTE SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.
•
A Cisco IOS device might experience an unexpected reload as a result of mtrace packet processing.
Unreproducible Caveats
This section lists a caveats that are unreproducible in Cisco LTE SGW Release 1.3.5, Cisco IOS Release 12.4(24)T35c.
•
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 upon a reload at almost the same time of both gateways in a redundant implementation. This condition is more likely to occur when the Stream Control Transmission Protocol (SCTP) connectivity for the redundant configuration is lost.
•
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 issue is observed after a few hours under the following conditions:
a.
b.
c.
d.
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 SGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d
This section contains open and resolved caveats that pertain to Cisco LTE SGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
There are no known SGW caveats open in Cisco LTE SGW 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 SGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.
•
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.
•
Mobile Express Forwarding (MEF) stops forwarding packets in the Cisco LTE SGW.
This condition occurs when the Cisco LTE SGW receives a packet in which the inner IP packet is malformed. Specifically, the length field of the inner packet has a corrupted value.
Workaround: Disable MEF using the no mef access-point configuration command.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.
Cisco LTE SGW Caveats
This section lists the SGW caveat that is resolved with Cisco LTE SGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.
•
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.
•
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 SGW Release 1.3.4, Cisco IOS Release 12.4(24)T34d.
Caveats - Cisco LTE SGW Release 1.3, Cisco IOS Release 12.4(24)T3c
This section contains open and resolved caveats that pertain to Cisco LTE SGW Release 1.3, Cisco IOS Release 12.4(24)T3c.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
There are no known SGW caveats open in Cisco LTE SGW Release 1.3, Cisco IOS Release 12.4(24)T3c.
Cisco SAMI Caveats
This section lists the Cisco SAMI caveat that is open with Cisco LTE SGW Release 1.3, Cisco IOS Release 12.4(24)T3c.
•
Mobile Express Forwarding (MEF) stops forwarding packets in the Cisco LTE SGW.
This condition occurs when the Cisco LTE SGW receives a packet in which the inner IP packet is malformed. Specifically, the length field of the inner packet has a corrupted value.
Workaround: Disable MEF using the no mef access-point configuration command.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.3, Cisco IOS Release 12.4(24)T3c.
Cisco LTE SGW Caveats
This section lists the SGW caveats that are resolved with Cisco LTE SGW Release 1.3, Cisco IOS Release 12.4(24)T3c.
•
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.
•
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.
•
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.
•
A crash occurs on the standby SGW when synchronizing SNMP MIB information. This condition occurs because MIB information is being synchronized from the PCOP and TCOPs when it should only be sychronized from the PCOP.
Cisco SAMI Caveats
There are no Cisco SAMI caveats newly resolved with Cisco LTE SGW Release 1.3, Cisco IOS Release 12.4(24)T3c.
Caveats - Cisco LTE SGW Release 1.2, Cisco IOS Release 12.4(24)T3b
This section contains open and resolved caveats that pertain to Cisco LTE SGW Release 1.2, Cisco IOS Release 12.4(24)T3b.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
There are no known SGW caveats open in Cisco LTE SGW Release 1.2, Cisco IOS Release 12.4(24)T3b.
Cisco SAMI Caveats
This section lists the Cisco SAMI caveat that is open with Cisco LTE SGW Release 1.2, Cisco IOS Release 12.4(24)T3b.
•
Mobile Express Forwarding (MEF) stops forwarding packets in the Cisco LTE SGW.
This condition occurs when the Cisco LTE SGW receives a packet in which the inner IP packet is malformed. Specifically, the length field of the inner packet has a corrupted value.
Workaround: Disable MEF using the no mef access-point configuration command.
Resolved Caveats
The following sections list the caveats that have been resolved with Cisco LTE SGW Release 1.2, Cisco IOS Release 12.4(24)T3b.
Cisco LTE SGW Caveats
This section lists the SGW caveats that are resolved with Cisco LTE SGW Release 1.2, Cisco IOS Release 12.4(24)T3b.
•
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.
b.
c.
d.
e.
Issue the show processor cpu command to display that the Proxy Control Processor (PCOP) stays at 98% for a long time.
•
For dual-stack or IPv6 only sessions, the Cisco LTE SGW returns the prefix in the Create Session Request it received from the mobile management entity (MME) instead of sending the prefix length that Cisco LTE PGW returns in the Create Session Response.
This condition occurs only when the UE uses dual-stack (IPv4 and IPv6) and IPv6 sessions.
Cisco SAMI Caveats
The following Cisco SAMI caveat is resolved with Cisco LTE SGW Release 1.2, Cisco IOS Release 12.4(24)T3b.
•
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.
Caveats - Cisco LTE SGW Release 1.1, Cisco IOS Release 12.4(24)T3a1
This section contains open and resolved caveats that pertain to Cisco LTE SGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.
Open Caveats
Note
The following sections document possible unexpected behavior and describe only severity 1 and 2 caveats and select severity 3 caveats.
Cisco LTE SGW Caveats
There are no known Cisco LTE SGW caveats open for Cisco LTE SGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.
Cisco SAMI Caveats
This section lists the Cisco SAMI caveats that are open with Cisco LTE SGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.
•
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.
Resolved Caveats
There are no newly resolved caveats with Cisco LTE SGW Release 1.1, Cisco IOS Release 12.4(24)T3a1.
Caveats - Cisco LTE SGW Release 1.0, Cisco IOS Release 12.4(24)T3a
This section contains the following types of caveats that pertain to Cisco LTE SGW Release 1.0, Cisco IOS Release 12.4(24)T3a.
Open Caveats—Cisco LTE SGW
There are no Cisco LTE SGW caveats open for Cisco IOS Release 12.4(24)T3a.
Open Caveats—Cisco SAMI
This section lists the SAMI caveats that are open with Cisco IOS Release 12.4(24)T3a.
•
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
The following documents are specific to Cisco IOS Release 12.4 and are located at Cisco.com:
•
Documentation > Cisco IOS Software > Cisco IOS Software Releases 12.4 Mainline > Release Notes
•
Documentation > Cisco IOS Software > Cisco IOS Software Releases 12.4 T > Release Notes
Note
•
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:
•
•
–
–
–
•
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
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.
This document is to be used in conjunction with the Cisco LTE SGW Configuration Guide and the Cisco LTE SGW Command Reference publications.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Copyright © 2012, Cisco Systems, Inc.
All rights reserved.
Feedback