14 0 51375 sgsn release notes mr

8/20/2019 14 0 51375 SGSN Release Notes MR

1/48

SGSN 14.0.51375 MR Release Note

The information in this document applies to StarOS™ Software Version

14.0.51375 supporting SGSN services in GPRS/UMTS networks.

August 30, 2013

Americas Headquarters

Cisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 527-0883

http://www.cisco.com/http://www.cisco.com/


2/48

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALLSTATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTYOF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPEDWITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITEDWARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, B erkeley (UCB) as part of UCB’s public domainversion of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL

FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSEOF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADEPRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO ORITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display

output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any u se of actual IP addresses or phone numbers in

illustrative content is unintentional and coincidental.

SGSN 14.0.51375 MR Release Note

© 2013 Cisco Systems, Inc. All rights reserved.


3/48

SGSN 14.0.51375 MR Release Note ▄

iii

CONTENTS

Resolved Issues .................................................................................................. 5

Enhancements in this Release ................................................................................................................. 5 CSCtx48558 - Assertion failure at sess/smgr sessmgr_gprs.c:11289 ..................................................... 5 CSCuc75534 - Assertion failure at sess/sgsn/sgsn-app/access/access_iu.c:5490 ................................. 6 CSCud53514 - Few instances of wrong volume reported in S-CDRs ..................................................... 6 CSCue60700 - 2G-actv-fail-phase-2-offload bulkstats not incrementing ................................................. 7 CSCue90907, CSCug56148 - Assertion failure at sess/sgsn/sgsn-app/gtp_c/gtapp_tun_fsm.c:871 ..... 7 CSCug64380 - mmgr in over state - using more memory than allocated ................................................ 7 CSCug89559 - Assertion Failure at sessmgr_li.c - function smgr_pack_li_iri_tlv_sgsn() ........................ 8

CSCug94567- sessmgr Assertion at dhost/dh_api.c:140 dh_api_get_sockets_handler() ....................... 8 CSCuh06175 - Session manager crash ................................................................................................... 9

CSCuh11223 - TW APTG-PDSN: Ping failed via SLOT-19 - 12.2(44990) .............................................. 9 CSCuh18616, CSCua16448 - Getting error in output of ‘Displaying Subscriber -map system errors’ ..... 9 CSCuh21971 - Assertion failure at sess/sgsn/sgsn-app/utils/sgsn_common_utils.c:276 ..................... 10 CSCuh30012 - Frequent traps EntStateOperEnabled Temp Sensor Card ........................................... 10 CSCuh37928 - ASR5K MOCN 3g->gt; non-MOCN 2g RAU is rejected ................................................ 10 CSCuh38613, CSCug31697 - mmgr Assertion failure at messenger/mempool.c:261 .......................... 11 CSCuh43185 - IMSI manager in WARN state on DMUX card ............................................................... 12 CSCuh49324 - Gmm T3312-timeout set to 60 has been modified to default value 54 ......................... 12 CSCuh49352, CSCuc31411 - gmm T3312-timeout set to 60 has been modified to default value 54 .. 13 CSCuh51615, CSCuh17028 - ASR 5K FA manager crashed and disabled CDMA nw followed byss7congestion ......................................................................................................................................... 13

CSCuh55225 - Syslog event: tacacs+ 37203 ........................................................................................ 13

CSCuh57031 - Crash: sessmgr_gprs_process_ggsn_dpc_req_in_sec_cpc_pend() ............................ 14

CSCuh57904 - Use of wrong sgtp-service for Suspend Procedure ....................................................... 15 CSCuh66423 - ASR5K SGSN PDPs stuck in Disconnection state and can't activate .......................... 15 CSCuh66495 - Asrt at sess/sgsn/sgsn-app/pmm/gprs_util.c, F: sessmgr_gprs_alloc_pdp_cb ............ 16 CSCuh66750 - Sessmgr crash at Assertion failure at sess/smgr/sessmgr_gprs_fsm.c:2092 ............... 16 CSCuh69750 - Show port datalink counters x/x tributary x generates npu crash .................................. 18 CSCuh72107 - Assert failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:10144 ............................... 18 CSCuh80786 - Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:9750 ............................ 18 CSCuh83303 - SCTP parameters cannot be changed for a second Peer-Server................................. 19 CSCuh83693 - AF sess/sgsn/sgsn-app/gtp_c/gtpapp_mm_fsm.c:527 ................................................. 19 CSCuh88619, CSCuh89454, CSCuh88751, CSCuh92239, CSCui01632 - Assertion failure atsess/sgsn/sgsn-app/gtp_c/gtapp_tun_fsm.c:6779 ................................................................................. 20 CSCuh88816 - Show call-control-profile full does not show lcs-related info. ......................................... 20 CSCuh91877 - Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:1335 ............................ 21

CSCuh91936 - FS 11: Segm fault sn_gt_send_self_initiated_err_response() ...................................... 21

CSCuh97691 - SM task restart Function: SmGenRestartPendingProcedure() ..................................... 22

CSCuh97968 - Attribute name mismatch for snmp trap 1186 and 1184 ............................................... 22 CSCui01679 - Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:3774 .............................. 23 CSCui02016 - Action-id mismatch CLI global-title-translation association and Config .......................... 23 CSCui03633 - Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:6311 .............................. 23 CSCui09027 - RNC status shown as ‘Unavailable’ even when the actual RNC link is UP ................... 24 CSCui12668 - sessmgr assert sess/sgsn/sgsn-app/dp/sn_dp_network.c:1370 .................................... 24


4/48

▀ Contents

▄ SGSN 14.0.51375 MR Release Note

iv

CSCui22961 - SGSN/MME: multiple sessmgr crashes due to Loss-of-Radio Coverage - LORC ......... 25 CSCui27241 - Assertion failure at sess/sgsn/sgsn-app/access/access_main.c:1236 ........................... 25

CSCui47095 - crash - 14.0(50083) - pmm_util_check_and_send_sgsn_context_ack_failure .............. 26

Unresolved Issues ............................................................................................ 27

Operator Notes .................................................................................................. 29 Operational Recommendations: ............................................................................................................. 29 Limitations ............................................................................................................................................... 29 Qualified for Lab and Trials..................................................................................................................... 30 Not Qualified ........................................................................................................................................... 30

Previously Resolved Issues ............................................................................ 31


5/48


5

Resolved Issues

This section contains information about issues resolved in this software release and enhancements that have been

created and verified for this release. For a summary of all resolved issues in earlier 14.0 releases, see Previously

Resolved Issues section.

Enhancements in this Release

This section begins with a listing of the CDETS IDs that represent all the customer-impacting enhancements in this

release; including:

Feature changes - new or modified features or behavior changes,

Command changes - changes to any of the CLI command syntax,

Performance indicator changes - new or modified bulk statistics, disconnect reasons, counters and/or fields innew or modified show command output.

CSCuh11223

CSCuh38613

CSCuh57904

CSCuh66423

CSCuh80786

CSCuh88619, CSCuh89454 CSCuh88816

CSCuh91936

CSCuh97968

CSCui22961

CSCtx48558 - Assertion failure at sess/smgr sessmgr_gprs.c:11289

Type

Fix

Problem Analysis

Accessing invalid clp results in a crash.

Problem Solution

A safety check is added to validate smid and de-allocating clp.


6/48

Resolved Issues


6

CSCuc75534 - Assertion failure at sess/sgsn/sgsn-app/access/access_iu.c:5490

Type

Fix

Problem Analysis

Consider the following scenario, where the “iu-release-complete-timeout” is configured greater than “iu-release-hold-

timeout”:

3g Attach, Activate

RAU Request

Auth/security procedure

SRNS procedure

RAB assignment request to RNC RAB assignment expiry

RAU Accept is sent to UE

Iu release request from RNC

No Iu release command

A crash is observed after “iu-release-hold-timeout”. The issue is observed when “iu-release-comp” timer is running, the

activity timer (started by sm-start-activity) expires and this leads to feeding of relReq again for the same iuConCb.

Problem Solution

The issue is resolved by verifying the “iu-state” before feeding relreq in case of activity-timer expiry.

CSCud53514 - Few instances of wrong volume reported in S-CDRs

Type

Fix

Problem Analysis

SGSN 3G and 2G services have different volume triggers(4Mb for 3G and 100 Kb for 2G) configured for CDR

generation. Consider the following scenario, RAT-trigger is disabled, the subscriber is initially attached in 3G and sends

downlink data greater than the 2G volume limit but has not reached the 3G limit. Handoff occurs from 3G to 2G andsession-recovery happens after the hand-off. When the session-manager recovers, the volume trigger for 2G will be

applied for the volume trigger. If subscriber receives any uplink data, a trigger will be generated since 2G volume has

already been reached. In this scenario, a bug in the code causes an integer over run error when calculating the uplink

volume counter. In the reverse scenario where uplink data is received the uplink data is received, after handoff and

session recovery when downlink data is sent it leads to over-run error in downlink volume counter.


7/48

Resolved Issues


7

Problem Solution

A common data structure was being called for every data transfer from the subscriber and this function expects that the

current data transfer is the sole reason for reaching the volume limit. In the scenario mentioned above, there is an inter-

technology handoff and with each technology having a different volume trigger, the volume limit can be reached earlier

in one technology but the CDR generation does not occur. The issue has been resolved by storing excess volumecounters in a separate buffer. This resolves the integer over-run error.

CSCue60700 - 2G-actv-fail-phase-2-offload bulkstats not incrementing

Type

Fix

Problem Analysis

The 2G-actv-fail-phase-2-offload bulk statistics are not incremented. At the Session Controller, the correspondingcounter was available for the sgsn-service while this counter is relevant to 2G activate.

Problem Solution

The issue is resolved and updation of the corresponding counter is corrected in the Session Controller.

CSCue90907, CSCug56148 - Assertion failure at sess/sgsn/sgsn-

app/gtp_c/gtapp_tun_fsm.c:871

Type

Fix

Problem Analysis

If a PDP is activated with fallback APN, then during post processing (post processing is a set of functions carried out at

the Session Management Module on the PDP after RAU/local PDP preservation) the PDP is de-activated (due to its

absence in the subscription). The SM and GTP module become asynchronous resulting in a crash.

Problem Solution

The PDP activated with fallback APN should not be de-activated during PDP post processing.

CSCug64380 - mmgr in over state - using more memory than allocated

Type

Fix


8/48

Resolved Issues


8

Problem Analysis

The Master Manager (mmgr) facility consumes more memory than allocated and enters a warn/over state. Master

Manager using the legacy heap allocation (SN_MALLOCs) for processing the RNCs resets the resource messages and

so on, this leads to fragmentation of memory and the mmgr enters a warn state.

Problem Solution

Using of Cache pools instead of the SN_MALLOCs for processing the RNCs, reset resource messages and so resolves

this issue. This is an optimized way of utilizing the memory within the memory limit set for the mmgr.

CSCug89559 - Assertion Failure at sessmgr_li.c - function

smgr_pack_li_iri_tlv_sgsn()

Type

Fix

Problem Analysis

When a duplicate activate request is handled, a timer is started to handle the activation request after clearing the

previous activation. During this period if a detach request is received, a LI event is triggered where a sub session is

expected to be present. But the activation request has not been handled and the sub-sessions are not created, leading to a

crash.

Problem Solution

LI events are valid when sub-sessions are present, in this scenario no sub-sessions are present prior to calling the LI

function. The issue is resolved, LI events are now ignored by providing a check for sub-session presence.

CSCug94567- sessmgr Assertion at dhost/dh_api.c:140

dh_api_get_sockets_handler()

Type

Fix

Problem Analysis

Data corruption results in this issue.

Problem Solution

A protective fix has been provided against the data corruption.


9/48

Resolved Issues


9

CSCuh06175 - Session manager crash

Type

Fix

Problem Analysis

APN re-mapping is enabled in the configuration, the UE sends junk APN. SGSN memory corruption occurs when the

SGSN tries to parse the junk APN, leading to a crash.

Problem Solution

When the SGSN is unable to parse the APN, re-mapping is not performed.

CSCuh11223 - TW APTG-PDSN: Ping failed via SLOT-19 - 12.2(44990)Type

Behavior Change

Feature Changes

Clearing DT Starchannel Registers

Previous Behavior: DT FPGA starchannel registers were not monitored earlier.

New Behavior: PSC2 or PSC3 DT-side starchannel registers are now monitored. So, if some critical bits are stuck in

the DT registers, then an NPUMgr restart is performed and the register bits are cleared as part the NPUMgr

initialization.

Impact on Customer: When the DT registers are stuck, NPUMgr restart will be occur which should automatically

resolve the issue.

CSCuh18616, CSCua16448 - Getting error in output of ‘Displaying Subscriber -mapsystem errors’

Type

Fix

Problem Analysis

A check for configuration errors is performed in the subscriber map even if no subscriber maps are present.

Problem Solution

Code is added to check for configuration errors in the subscriber map only if, atleast one subscriber map is present.


10/48

Resolved Issues


10

CSCuh21971 - Assertion failure at sess/sgsn/sgsn-

app/utils/sgsn_common_utils.c:276

Type

Fix

Problem Analysis

Network-sharing involving multiple Iups-services is not fully-qualified. The following scenario was leading to crashes:

Successful attach procedure in iups1

Attach request with imsi at RANAP in Iups2 (network-sharing enabled)

Auth/sec mode procedure

The handling of new-access after imsi is known but is not performed. This leads to non-updation of hlr-param and

leading to crash.

Problem Solution

HLR parameters are being updated now in above scenario to resolve the issue.

CSCuh30012 - Frequent traps EntStateOperEnabled Temp Sensor Card

Type

Fix

Problem Analysis

The system was called every 30 seconds to find the thermal status. Every time the driver sensor state was normal, the

thermal events were notified and the trap was sent each time.

Problem Solution

Send EntStateOperEnabled trap only when the previous thermal thresh state is not “OK” by checking the controller

alarm count. This problem has been fixed.

CSCuh37928 - ASR5K MOCN 3g->gt; non-MOCN 2g RAU is rejectedType

Fix


11/48

Resolved Issues


11

Problem Analysis

This issue is observed in network-sharing configurations with multiple Iups-services. If a Iups-service is changed from

non-network-sharing configuration to a network-sharing configuration, some RAI information is not added in the Link

Manager. The RAU request is being treated as non-local and forwarded to a non-anchoring smgr.

Problem Solution

The issue has been resolved as a part of fix for the PR CSCtx05296.

CSCuh38613, CSCug31697 - mmgr Assertion failure at messenger/mempool.c:261

Type

Fix + Enhancements

Problem Analysis

When the new reset resource arrives at the mmgr, a mmgr_reset_res_t is allocated and a “500” ms timer is started to free

it. Each reset-resource involves a broadcast to all Session Managers. The messenger prefers delivering responses from

peer-proclets over inbound-requests from others, which are themselves preferred over timer callbacks. So a Link

Manager sending an inbound request to the mmgr, and mmgr itself being bombarded with “384” responses for every

reset resource sent earlier. Over a period of time due to small reset resources like the one mentioned above, the mmgr

scheduling will be overwhelmed with too many requests from the Link Manager, and enormous number of responses

from the Session Manager and too many of local timers. Since local timers will starve in such a condition, this leads to a

memory crash.

Problem Solution

The issue is resolved through the following: Timer optimization:Timers are maintained per iups-service rather than per reset resource. This timer starts after

the first reset resource is received at the iups-service. On expiry of the timer, the reset resources received priorto the “500” ms are released and the timer will be re-started for next reset resource during the remaining period. This routine continues until all the reset resources are processed.

Messaging optimization: Reset resources are aggregated till “32” messages or for “100”ms and then broadcasted to the Session Managers. Responses from Session Managers are aggregated back to the mmgr andthe corresponding reset resources are released.

Protection against an attack: The Master manager is protected against the flurry of reset resources withlimiting the num ber of concurrent broadcasts. This is pegged at “10”, and “10*32” reset resources can be processed in “100”ms time duration. If the number of resources received are more than “10*32”, such resetresources are dropped and are pegged in the “Resource Reset Dropped” counter in “show gmm-sm statistics”.

Feature Changes

Throttle Handling Incoming RANAP Reset Resource Messages

Previous Behavior: No throttle mechanism existed to manage flurries of incoming RANAP reset resource messages.

New Behavior: RANAP reset resource request messages will be dropped after reaching a threshold of 10 concurrent

broadcasts from the Master Manager (MMgr) to the Session Managers (SessMgrs).


12/48

Resolved Issues


12

These drops will be pegged as “Resource Reset Dropped” and visible in the output of either command show gmm-sm

statistics or show gmm-sm statistics iups-service .

Performance Indicator Changes

show gmm-sm statistics

A new counter has been added to the output of the show gmm-sm statistics and the show gmm-sm statistics

iups-service iups-service_name to track the number of Resource Reset Requests dropped as a result of the new

throttling mechanism which handles flurries of these requests messages to the MMgr. The new counter listed below is

under the Ranap Procedures heading in the output display.

Resource Reset Dropped

CSCuh43185 - IMSI manager in WARN state on DMUX card

Type

Fix

Problem Analysis

The ptmsi-not-noted scenario was handled incorrectly leading to memory leakage as ptmsi mapping entry was not being

released.

Problem Solution

The fix resolves the memory utilization issue. This mechanism caters to identify all scenarios and releases the unused

ptmsi in the unexpected failure scenarios.

CSCuh49324 - Gmm T3312-timeout set to 60 has been modified to default value 54

Type

Fix

Problem Analysis

The “t3312” and “mr” timer are inter -dependent, issue is observed in the following scenarios:

While printing the “t3312” timer first and “mr” timer second and when the “t3312” is configure d more than the

default value.

While printing the “mr” timer first and the “t3312” second and when the “mr” timer is configured less than thedefault value.

In the above mentioned scenarios, when the chassis is re-loaded with the saved configuration, the timers are adjusted as

they violate the following rule:

mr timer >=t3312 + 4/t3312


13/48

Resolved Issues


13

Problem Solution

The printing order is adjusted based on the values.

CSCuh49352, CSCuc31411 - gmm T3312-timeout set to 60 has been modified to

default value 54

Type

Fix

Problem Analysis

The T3312 timer should be configured first to adjust the MR timer. Since MR and IDT are dependent of the T3312

timer. The order in which these timers are printed causes the issue.

Problem Solution

The issue is resolved by adjusting the order of printing the configuration.

CSCuh51615, CSCuh17028 - ASR 5K FA manager crashed and disabled CDMA nw

followed by ss7congestion

Type

Fix

Problem Analysis

The Link Managers are not sending the appropriate peer-server instances used in indirect routes.

Problem Solution

When PSPUP/DOWN events occur, the dpcs with matching peer-server ids will be notified to Master Manager.

CSCuh55225 - Syslog event: tacacs+ 37203

Type

Documentation

Problem Analysis

A description of the syslog event “37203” is required. Information on when this event is triggered and the impact it has

on production is required.


14/48

Resolved Issues


14

Problem Solution

A typical authentication session between TACACS+ client and server involves the following steps:

1. A Client establishes a TCP connection with the Server

2. The Client sends an AUTH/START message and the Server returns an AUTH/REPLY3. The Client sends an AUTH/CONT message (carrying username) and the Server returns an AUTH/REPLY

4. The Client sends an AUTH/CONT message (carrying password) and the Server returns an AUTH/REPLY.

The syslog event “37203” is triggered in one of the following scenarios:

An alternative server is unavailable after a protocol error occurs in any of the above mentioned steps.

The client fails to receive a reply from the server (after timeout) for Steps 2, 3, or 4 listed above.

The issue in this PR is observed due to the second reason, namely the client fails to receive a reply from the server (after

timeout) for Steps 2, 3, or 4.

CSCuh57031 - Crash: sessmgr_gprs_process_ggsn_dpc_req_in_sec_cpc_pend()

Type

Fix

Problem Analysis

Consider the following scenario:

Attach, activate primary PDP (nsapi 5)

Activate secondary (nsapi 6), Create PDP Context Request sent to GGSN, and with no Create PDP Context Response

from GGSN

MS init deactivation, teardown flag = 0 (nsapi 5)

Delete PDP Context Request message to GGSN with a response from GGSN

De-activate Acc to UE

Delete PDP Context Request (DPCQ) from GGSN with nsapi 6, td =1

When the DPCQ for nsapi 6 (secondary context) is processed, it is assumed that bundle API will return the other context

as it is a secondary context. But in this particular case, the other context is de-activated. So, the assumption is incorrect

and an ASSERT is fired causing the task to reload.

Problem Solution

ASSERT is removed and code added to ensure the Activate Secondary Reject is sent to the UE in the above mentioned

scenario.


15/48

Resolved Issues


15

CSCuh57904 - Use of wrong sgtp-service for Suspend Procedure

Type

Fix+ Behavior Change

Problem Analysis

Arrival of a BSSGP suspend message does not imply the presence of a subscriber. Therefore it is not possible to

determine the GPRS service from which the message arrived. Currently, a SGSN_CTX_REQ message is sent from the

first configured SGTP service.

Problem Solution

The first SGTP service associated with the first GPRS service configured is used to send the CONTEX_REQ message,

this prevents sending CONTEX_REQ message through the SGTP service associated with MME services.

Feature Changes

SGSN Context Request From GPRS Service

Previous Behavior: The SGSN initiates a SGSN context request with suspend header from the SGTP service that is

configured first.

New Behavior: The choice of SGTP service from which a SGSN context request message with a suspend header is

initiated is changed.The SGSN now initiates the SGSN context request with suspend header from the SGTP service

associated with the first configured GPRS Service.

Impact: Functionally there is no impact, only the IP address from which the SGSN context request with suspended

header is sent will be different.

CSCuh66423 - ASR5K SGSN PDPs stuck in Disconnection state and can't activate

Type

Behavior Change

Feature Changes

SGSN Response to Activation Request

Previous Behavior: If the SGSN receives an activation request from a de-activating context, the SGSN sends the SM

status.

New Behavior: If the SGSN receives an activation request from a deactivating context, the SGSN now cleans up the

disconnecting PDP and picks up the fresh activation.

In a 3G scenario, when bundle de-activation is in progress and PDP is in a disconnecting state, activations are handled

in the following manner:

1. The SGSN receives an activate Primary PDP context request, all the PDPs in the bundle are cleaned up and a freshactivation is picked up.


16/48

Resolved Issues


16

2. The SGSN receives a secondary activate PDP context request, SM status is sent.

CSCuh66495 - Asrt at sess/sgsn/sgsn-app/pmm/gprs_util.c, F:

sessmgr_gprs_alloc_pdp_cb

Type

Fix

Problem Analysis

A 2G GPRS attached MS tries to do three primary PDP-activations simultaneously whose identifiers like TI,NSAPI are

re-used in the latest PDP activation request. While trying to de-activate/de-allocate the existing duplicate PDP-contexts

with same TI and NSAPI, the Session Manager crashes due incorrect handling of the them.

Problem Solution

Code has been added to handle such situations, where the MS tries to do a primary PDP activation with NSAPI and TI

that are already in use with some other primary PDP-contexts of the same MS with SGSN.

CSCuh66750 - Sessmgr crash at Assertion failure at

sess/smgr/sessmgr_gprs_fsm.c:2092

Type

Fix

Problem Analysis

Consider the following scenarios listed below:

1. Scenario 1:

Attach in SGSN

Attach Accept (RA= RA1, ptmsi = PTMSI1)

Attach Complete

Moves to MME

No cancel location is sent to SGSN

Returns to SGSN

Attach request with tlli= derived from MME PTMSI

old-ra = mme RA

ptmsi = MME PTMSI

ad-ptmsi = PTMSI1


17/48

Resolved Issues


17

ad-RA = RA1.

Xid send out.

Attach again, the issue observed here is the gmm stack not detecting this is duplicate attach.

Attach fed to application fsm

The issue observed here is, the subscriber information related structure "smid" is cleaned up incorrectly and isused again

A crash occurs while accessing the freed smid

2. Scenario 2:

Attach

Attach accept with PTMSI1, RA1

Attach complete

ptmsi attach with addl-ptmsi=PTMSI1/addl-ra=RA1

Attach Accept

Attach again (repeat)



A crash occurs while accessing the freed smid.

3. Scenario 3:

Attach

Attach accept with PTMSI1, RA1

Attach complete

Ptmsi attach with addl-ptmsi=PTMSI1/addl-ra=RA1

Authentication Request

Attach again (repeat)



A crash occurs while accessing the freed smid.

In all of the above mentioned scenarios, the subscriber information related structure "smid" retrieved based on

additional ptmsi would be same as the current one. Clearing the “smid” retrieved from additional ptmsi is same as

clearing the currently used smid which leads to accessing the cleared smid structure which results in a segmentation

fault.

Problem Solution

The retrieved smid structure is verified against the present smid and de-allocation is not done if it is the same. For the

first scenario, added a check in gmm attach function which prevents sending of Duplicate Attach as Valid Attach to the

Application.


18/48

Resolved Issues


18

CSCuh69750 - Show port datalink counters x/x tributary x generates npu crash

Type

Fix

Problem Analysis

While collecting the aggregate statistics based on a 'tributary value' sn_npumgr_port_stat_get(), the function is called

with logical port id or with the tributary value requested. This leads to the npumgr de-reference to an invalid pointer as

it was expecting the logical port id. De-reference of the invalid pointer on fetching the aggregate logical statistics leads

to the npumgr crash.

Problem Solution

The logical port id validation is invalid in the above mentioned scenario. So the validation of logical port id is removed

from this function.

CSCuh72107 - Assert failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:10144

Type

Fix

Problem Analysis

The Session Manager re-starts with an assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:10144, a crash is

observed when the Context-Request is received after suspend operation in ms-page-resp-pending state. The user is

attached and activated in 3G, receives a suspend from 2G and the suspend operation is complete.After this an IRAT to 2G occurs and during the IRAT procedure, the MS is paged for downlink data and during page-

response pending, context-req is received from the peer SGSN. The sessMgr crashes in this scenario. The reason for

crash is that "mm_context->mm_flags.flags.is_ms_suspended" flag is not reset when the SGSN receives a context-req ,

resulting in an invalid suspend event being fed to SM module.

Problem Solution

Code is added to reset "mm_context->mm_flags.flags.is_ms_suspended" flag if context-req is received in page-rsp-

pending state. When the SGSN receives context-req , the "mm_context->mm_flags.flags.is_ms_suspended" flag will be

reset, and hence suspend event will not be fed to SM module.

CSCuh80786 - Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:9750

Type

Behavior Change


19/48


20/48

Resolved Issues


20

Cancel location received

SGSN context request with suspend, context response sent

Another SGSN context request

Problem Solution

The issue is resolved by doing a proper state change or cleanup in the above mentioned scenario.

CSCuh88619, CSCuh89454, CSCuh88751, CSCuh92239, CSCui01632 - Assertion

failure at sess/sgsn/sgsn-app/gtp_c/gtapp_tun_fsm.c:6779

Type

Behavior Change

Feature Changes

Delete PDP Context Request During Session Clean Up

Previous Behavior: Delete PDP context request is not sent during old session cleanup on Attach/RAU with additional

PTMSI/RAI.

New Behavior: Delete PDP context request is sent during old session cleanup on Attach/RAU with additional

PTMSI/RAI.

CSCuh88816 - Show call-control-profile full does not show lcs-related info.Type

Fix + Behavior Change

Problem Analysis

LCS related information was not added to the show output show call-control-profile full all.

Problem Solution

LCS related information is added to the show output show call-control-profile full all.

Feature Changes

LCS Information in Show Command

Previous Behavior: The show command show call-control-profile full alldoes not display any LCS

related information.

New Behavior: The show command show call-control-profile full allis updated to display LCS related

information.


21/48

Resolved Issues


21

Performance Indicator Changes

show call-control-profile full all

The following new LCS parameters are now displayed on execution of show call-control-profile full all

command:

Location Services for UMTS MT-LR

Location Services for GPRS MT-LR

Location Services for UMTS MO-LR

Location Services for GPRS MO-LR

Location Services for UMTS NI

Location Services for GPRS NI

CSCuh91877 - Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:1335

Type

Fix

Problem Analysis

When Loss of Radio Coverage (LORC) is enabled and UE is suspended for PS messages after IU is released, if the HLR

modifies the subscribed QoS for UE, it is queued and processed later. Once the UE does a RAU/ Service Request to

resume the PS services, the SGSN takes up the modification queued from the HLR and informs the GGSN of the QoS

change. Simultaneously, the SGSN also tries to inform that the UE is back in radio coverage area. This implies that the

SGSN is simultaneously providing two different kinds of information to the GGSN, which is not handled correctly.

Problem Solution

Once the UE sends a Service Request to resume the suspended Packet-switched services, modification from the HLR is

first picked up and completed. This is followed by informing the GGSN that the UE is back in radio coverage area.

CSCuh91936 - FS 11: Segm fault sn_gt_send_self_initiated_err_response()

Type

Behavior Change

Feature Changes

SGSN Context Response Message To a Gn Interface

Previous Behavior: While a suspend from Gn interface is being processed, a BSSGP suspend is received. Currently no

response messages are sent to the Gn interface in such a scenario.


22/48

Resolved Issues


22

New Behavior: When a suspend from a Gn interface is being processed and BSSGP suspend is received, a SGSN_CTX

response message with imsi unknown is sent to the Gn interface.

CSCuh97691 - SM task restart Function: SmGenRestartPendingProcedure()

Type

Fix

Problem Analysis

The RNC rejects the RAB Modify Request and the RABs are up, the GGSN and MS have to be informed of the old

QoS. If Iu is released by the RNC at this time, it is handled incorrectly and a crash occurs.

Problem Solution

Iu release while informing the MS of Modify PDP is handled correctly and preservation is taken up to resolve the issue.

CSCuh97968 - Attribute name mismatch for snmp trap 1186 and 1184

Type

Fix+ Behavior Change

Problem Analysis

Mismatch in attribute is observed in the following traps:

starLocalUserAdded - trap code 1180

starLocalUserRemoved - trap code 1181

starOsShellAccessed - trap code 1183

starLicenseFeaturesModified - trap code 1185

starHiddenAccessDisabled - trap code 1187

This issue has occurred due to the support added for the PR CSCtr14406.

Problem Solution

The issue is resolved by the fix provided for the PR the “CSCuh35889”, merge issues are resolved and this fix is

available in this branch.

Feature Changes

Correct Context Object Names For Trap Numbers

Previous Behavior: The old system is declared with wrong context object names for the trap numbers

1180,1181,1183,1184,1185,1186, and 1187 in “starent.my” file.


23/48

Resolved Issues


23

New Behavior: The new system has correct context object names in “starent.my” file for the trap numbers

1180,1181,1183,1184,1185,1186, and 1187.

Impact: The customer can now see correct context object names in “starent.my” file for the trap numbers

1180,1181,1183,1184,1185,1186, and 1187.

CSCui01679 - Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:3774

Type

Fix

Problem Analysis

During an Intra-SGSN Inter-PLMN routing area update in 3G, for a PDP activated with default APN, an un-initialized

variable is used to negotiate the QOS resulting in undefined SGSN behavior.

Problem Solution

If a PDP is activated with default APN, QoS is not negotiated.

CSCui02016 - Action-id mismatch CLI global-title-translation association and Config

Type

Fix

Problem Analysis

The command show sccp statistics sccp-network 2 global-title-translation association

displays the action Id in the decreasing order of start-end-digit match. The action Id displayed is not the actual actionId

configured.

Problem Solution

The issue is resolved and the actual action Id is displayed.

CSCui03633 - Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:6311

Type

Fix

Problem Analysis

A subscriber has active PDP context with direct tunnel. During suspend handling, UPCQ is initiated by the SGSN. If a

UPCR is sent by GGSN with a “non-existent” cause code, the expected behavior according to the specification is the


24/48

Resolved Issues


24

context should be cleared. But the subscriber suspend event is queued, and later when the subscriber does an old RAU

to the peer SGSN the queued event is not taken up resulting in a crash.

Problem Solution

The issue is resolved, in the above mentioned scenario the queued event is taken up to ensure that the context is de-activated.

CSCui09027 - RNC status shown as ‘Unavailable’ even when the actual RNC link isUP

Type

Fix + Enhancement(s)

Problem Analysis

MMGR recovery due to memory overload or demux migration leads to missing status updates for RNC. As the result

RNC status remains unavailable even when links towards RNC are up.

Problem Solution

The Session Controller allows the Standby Session Managers along with Active Session Managers to fetch the status

updates.

Feature Changes

Status Updates to RNC

During MMGR recovery due to memory overload or demux migration leads to missing status updates for RNC.As the

result RNC status remains unavailable even when links towards RNC are up. The Session Controller allows the Standby

Session Managers along with Active Session Managers to fetch the status updates.

CSCui12668 - sessmgr assert sess/sgsn/sgsn-app/dp/sn_dp_network.c:1370

Type

Fix

Problem Analysis

When a Delete PDP request arrives in an Inter-RAT state, the data-plane is suspended for deletion and the event is

queued. Once the ISD comes from the HLR, this queued event is overwritten. Later when IRAT to 3G fails, the data

plane is informed to resume receiving the packets, but the data plane is already in suspended for deletion state therefore

a crash occurs.


25/48

Resolved Issues


25

Problem Solution

When the ISD arrives, queued de-activation event should not be overwritten.

CSCui22961 - SGSN/MME: multiple sessmgr crashes due to Loss-of-Radio

Coverage - LORC

Type

Behavior Change

Feature Changes

New Signaling Message to GGSN

Previous Behavior: When GGSN init UPCQ was received in PMM_IDLE state with PCO IE included, the GGSN wasnot informed that the MS is back in radio coverage area.

New Behavior: After GGSN init update is complete, a UPCQ is initiated to inform the GGSN that the UE is back in

radio coverage area.

CSCui27241 - Assertion failure at sess/sgsn/sgsn-app/access/access_main.c:1236

Type

Fix

Problem Analysis

Consider the following scenario:

3G ISRAU

3G RAU request for same ptmsi with old-RAI as 2G RAI

Auth/security/eir validation/glu/rau-accept

Iu release

Context request from peer

Old-iu-available-for-local-handoff is being set in case of ISRAU being fed in connected state, but this is not being

cleared as purpose of this is for local handoff.

Problem Solution

Flag is being cleared in appropriate state now.


26/48

Resolved Issues


26

CSCui47095 - crash - 14.0(50083) -

pmm_util_check_and_send_sgsn_context_ack_failure

Type

Fix

Problem Analysis

The “ack failure” function is called after the current access is released. Since the function uses current access in

mm_context, it seg faults when access is released.

Problem Solution

Moved the function above the release access to avoid seg fault.


27/48


27

Unresolved Issues

This section lists known issues that are not resolved in this software release. For details about any one of these

unresolved issues, use your browser to connect to the Cisco Bug Search tool at:

https://tools.cisco.com/bugsearch/

CSCts18024 - Line timing not working for OLC2 card

CSCua31103 - Nonfatal warning at messenger/xpt_tcp.c:1086

CSCua49785 - Wrong bulkstats data values are seen in sgsn schema

CSCua73108 - standby CLC2 card reboot results in traffic outage

CSCua80774 - SNMP trap notification ‘per -service-gprs-pdp-sessions’ is not triggered

CSCuc29026 - ASR5k OSPF/traffic not establishing after PSC card replacement CSCuc45160 - Unable to execute commands after ungraceful SMC switchover

CSCue73703 - No data possible after LTE to 2G RAU

CSCug73934 - Iu/S1 Flex in combined SGSN/MMEs - TAU fails GTP_IMSI_NOT_KNOWN

CSCug83549 - Content in SMC HD is unavailable after SMC Switchover for few minutes

CSCug87356 - [ATM]: qsaal layer links went down after executing following scenario

CSCui71028 - Assertion failure at csp/csp_api_utility.c:339


28/48


29/48


29

Operator Notes

Operational Recommendations:

As Part of PSC3 Support (CSCzn35460):

In Release 14.0 the SGSN now supports 8M attached subscribers and 16M PDP contexts. This enhanced support applies

only to PSC3 with 14.0. For PSC2 with 14.0, the previous support numbers of 4M attached subscribers and 8M PDP

contexts still applies.

Increase NRIs per SGSN (CSCtr81030):

Beginning with Release 14.0, the number of subscribers per sessmgr has increased. For this reason, it is strongly

recommended that at least 3 local NRIs be configured per SGSN to ensure smooth operation.

Prior to loading a Release 12.2 or higher, we recommend that copies of the original configuration file be made and

stored (with unique release-identifying titles) both in the Flash and off the chassis. Configuration files created and saved

in Release 12.2 and higher cannot be shared across multiple chassis due to a change in the encryption algorithm for

passwords and secrets. Changes to Releases 12.2 and higher modify encrypted data in the configuration file so that it

cannot be recognized by previous software builds. If it is necessary to revert to a previous build, the chassis must be

booted with the copy of the original configuration file. If this copy is not available, then the chassis will need to be

loaded as if it is a new chassis.

Caution: The use of test commands could adversely affect the operation of your system. It is recommended that

they only be used under the guidance and supervision of a qualified support representative. For customers using GnARP CLI as per PRs CSCua93724/ CSCua46775, rnc-arp-enable configuration under Iups Service 'must' be included, inaddition to enabling ARP under Operator Policy.

SGTP-Service Cannot Be Shared between MME and SGSN (CSCuf57224)

When using the associate command in GPRS Service configuration mode or SGSN Service configuration mode, only

one SGTP service can be associated with a single service definition. If co-located, the GPRS and SGSN services can

share the same SGTP service association or they can have different SGTP services associated. When an SGSN and an

MME are co-located, the GPRS or SGSN service cannot be associated with the same SGTP service that is used by the

MME.

Limitations

Pdp-type restriction (CSCtw75399) takes precedence over pdn-type override (CSCtw75239), if both areconfigured.

CSCzn35460: MMGR goes into warn state when SAU goes beyond 5.6 Mn. No session disconnects areobserved. This issue is not due to memory leak but fragmentation of memory. The issue is currently underinvestigation.


30/48

Operator Notes


30

Performance degradation is observed compared to 12.0. Below are the PRs tracking that issue:

CSCtz75162 / [14.0 Performance]-3G ActivateDeActivate Rate Performance degrade in V14

CSCtz69645 / [14.0 Performance] - 3G Attach Rate Performance degrades in V14.0 PSC3

CSCtz72234 / [14.0 Performance]-3G AttachDetach Rate Performance degrades in V14 PSC3

CSCua54645 / N-New / 14.0 Performance-Avrg sessmngr memory usage is increased in call model

CSCua54705 / [14.0 Performance]-Total CPU usage of sgtpcmgr is increased in callmodel

CSCua55140/ N-New / [14.0 Performance]-Avrg CPU-1 usage is increased in callmodel test

CSCua57721 / [14.0 Performance]-Avrg CPU usage of mmgr is increased in callmodel

CSCtz77883 / N-New / [14.0 Performance ]-PLM fig not reached for 3G throughput with 512B Packetsize

CSCua54591 / [14.0 Performance]-Avrg linkgr memory usage is increased in callmodel test

CSCua54942 / [14.0 Performance]-Avrg CPU usage of imsimgr is increased in callmodel

Qualified for Lab and Trials

CSCty73026 - Enhancement to show linecard dlci-utilization support filter criteria

CSCts34802 - R7 Location Services (LCS)

CSCzn37980 - All S4 SGSN functionality

Not Qualified

The following commands are visible on the SGSN but these commands are in development and are not ready for use:

mbms { gtpu-bind-address | policy }

snmp mib

The following disconnect reasons are visible on the SGSN but they are in development and are not ready for use:

sgsn-no-rab-for-gbr-bearer(444)

sgsn-nrspca-actv-rej-by-sgsn(515)

sgsn-nrspca-actv-rej-by-ms(516)

sgsn-dsd-allepswithdrawn(535)


31/48


31

Previously Resolved Issues

The following table lists issues that were resolved in previous 14.0 software releases.

For information about previous behavior changes or enhancements, refer to the Version 14.0 ASR 5x00 Release Change

Reference.

CDETS ID Headline Build No. Release Date

CSCub60821 [14.0] Bearer QCI is got changed from 3 to 2 after MS modify fails 50488 30-Jun-13

CSCub74386 [14.0] Wrong security mode used in v2 Identification Response 50488 30-Jun-13

CSCuc15768 Help String for prefer local / prefer fallback-for-dns need to change 50488 30-Jun-13

CSCud97187 [14.0] Session disconnect reason ‘sgsn-dsd-allepswithdrawn’required

50488 30-Jun-13

CSCue48704CSCuh51766

Transmitted Data not seen for one of the psp's in a specific scenario 50488 30-Jun-13

CSCuf07732 Kernel crash which lead to PSC migration 50488 30-Jun-13

CSCug81600CSCug81675

Session Manager Crash: MOCN 50488 30-Jun-13

CSCug83970CSCug30810

LI audit duration 50488 30-Jun-13

CSCug93414 CLI 'remove access-restriction-data' shall be extended to remove no-check

50488 30-Jun-13

CSCuh12281 [14.0] Help text of show s4-sgsn statistics smgr-instance is wrong 50488 30-Jun-13

CSCuh17028 Some MAP messages not sent out of SGSN 50488 30-Jun-13

CSCuh24628CSCty32423

sessmgr crash Assert failure at sess/sgsn/sgsn-app/pmm/pmm_proc.c:2814

50488 30-Jun-13

CSCuh29881 SM task restart Function: SmGenRestartPendingProcedure() 50488 30-Jun-13

CSCuh40954 Assertion failure at sess/sgsn/sgsn-app/db/sgsn?db?pmm.c:1840 50488 30-Jun-13

CSCuh40983 Assertion failure at sess/sgsn/sgsn-app/sm/smn_activate_fsm.c:2688 50488 30-Jun-13

CSCuh44450 Unable to apply license in 14.0 50488 30-Jun-13


32/48



32


CSCuh28528 2G call deleted by SGSN after failure of PSC which is handling 2Gcall

50176 10-Jun-13

CSCtn91917CSCtz63253

Signal 10: User defined signal 1 PC: [ 1d3730/A]npu_dev_spin_10us()

50083 31-May-13

CSCtx38103CSCua59318

E-UTRAN Service HO IE shall be supported in RANAP 50083 31-May-13

CSCtx85138 [14.0]APN-OI replacement field from HSS/HLR not handled properly by SGSN

50083 31-May-13

CSCty64119 [14.0][s6d]no field to store Visited-Network-Identifier 50083 31-May-13

CSCty79825 [14.0] MME FQDN must be initiated for DNS Query to identify peermme.

50083 31-May-13

CSCtz97262 [14.0]: show s4-sgsn statistics is not working correctly 50083 31-May-13

CSCua51754CSCue90817

Assertion failure at sess/sgsn/sgsn-app/db/sgsn_db_pmm.c:1676 50083 31-May-13

CSCub07110 sgsn change attribute is not displayed in ‘show gtpp group namedefault’

50083 31-May-13

CSCub10425 Decode Error:Invalid encoded EXTs Count in Reloc_reqd and Reloc

request

50083 31-May-13

CSCub28855CSCuc31410

Segmentation faultPC: sessmgr_gprs_handle_addl_ie_release_smid() 50083 31-May-13

CSCub32844CSCud91004

Intermittent duplicate SCCP Release for Empty-CR Connections 50083 31-May-13

CSCub45172 [14.0 S4-SGSN Load] : snaptr_handle_A_response() 50083 31-May-13

CSCub66808CSCub67832

Move the 2G link related functionality from LINKMGR to a separate process

50083 31-May-13

CSCub68092CSCub73537CSCug05664

Support configurable downlink data lock out timer 50083 31-May-13

CSCub89503 [FR]: ‘clear port datalink counter all’ cli is not clearing DLCI stats 50083 31-May-13

CSCub92217 [ATM]: ‘Show port npu counter’ CLI does not show port levelstatistics.

50083 31-May-13


33/48



33


CSCuc01188 Assertion failure at sess/sgsn/sgsn-app/gtp_c/gtapp_db.c:788 50083 31-May-13

CSCuc49196 Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:2351 50083 31-May-13

CSCuc53264 TACACS: Assertion failure at messenger/evt_timer.c:124 50083 31-May-13

CSCuc66062 RAU appears to be un-answered by SGSN 50083 31-May-13

CSCuc78596 Illegal characters in counter names from SGSN and System schema 50083 31-May-13

CSCuc98179 Fatal Signal 6: Aborted PC: [b7e2a491/X] kill() 50083 31-May-13

CSCud00285 Many RAU from UE with no response from SGSN after LTE to 2GRAU

50083 31-May-13

CSCud04518 Linkmgr uses DMA for communication with NPU 50083 31-May-13

CSCud14071 2G Intra/IRAT Rau Reject Cause for CHECK IMEI Timeout isincorrect

50083 31-May-13

CSCud33739 Assertion failure at sess/sgsn/sgsn-app/pmm/pmm_fsm.c:6280 50083 31-May-13

CSCud36376 New crash - Assertion failure at sess/sgsn/sgsn-app/pmm/pmm_fsm.c:5648

50083 31-May-13

CSCud43319 Assertion failure at libc.so.6/kill() 50083 31-May-13

CSCud50721CSCud76417

All vpnmgrs and one npuctrl in over state 50083 31-May-13

CSCud61994 SGSN/MME: Gn interface issue 50083 31-May-13

CSCud72241 Card Programmables show output corrected 50083 31-May-13

CSCud74965 Assertion failure at sess/egtp/egtpc/egtpc_evt_handler_func.c:2703 50083 31-May-13

CSCud76431 Assertion failure at sess/sgsn/sgsn-app/dp/sn_dp_network.c:1298 50083 31-May-13

CSCud80740 CLI to locally configure peer MME/SGSN address needed for SRNSin s4-SGSN

50083 31-May-13

CSCud82870CSCue46119

Merge tftp issue on Optical cards to v122.main branch 50083 31-May-13

CSCud83051CSCug97859

[14.0] 2g Israu isnt processed when subscriber comes from MME. 50083 31-May-13


34/48



34


CSCud84382 Sessmgr crash on SGSN SERCOM 50083 31-May-13

CSCud89444 Assertion failure at sess/sgsn/sgsn-app/pmm/pmm_fsm.c:5648 50083 31-May-13

CSCud89662 SGSN SMSO CDRs with invalid ‘eventTimeStamp’ 50083 31-May-13

CSCud92928 Wrong calltype for Heartbeat messages in ‘LI interface specification’ 50083 31-May-13


RMCTRL resource in WARN state 50083 31-May-13

CSCue06299 SGSN : ATM : LAB : Point to point host route not working,/30 route 50083 31-May-13

CSCue16728 GboIP: lock/unlock interface management commands do not lock all

NSVLs

50083 31-May-13

CSCue16777 gtpu-service config does not appear in ‘show configuration’ 50083 31-May-13

CSCue16890CSCtx83121

Assertion failure at messenger/xpt_tcp.c:2039 - SGSN 50083 31-May-13

CSCue23340 UPD_PDP_CNTXT Rejected by SGSN 50083 31-May-13

CSCue24226 ATM: APS: Wrong IP over ATM interface status 50083 31-May-13

CSCue26687 [14.0] S4-DP memory statistics should be shown 50083 31-May-13

CSCue30295 Network-overload-protection functionality stops after IMSI Managerrecovery

50083 31-May-13

CSCue30772 Assertion failure at sess/sgsn/stackmgr/sn_ccpu_sm_gprs_gmm.c 50083 31-May-13

CSCue40679 Linkmgr crash reported on configuration of instream,outstream params

50083 31-May-13

CSCue45285 Duplicate key violates unique constraint "dlci_util_current_pkey" 50083 31-May-13

CSCue45592 Assertion failure at sess/sgsn/sgsn-app/gtp_c/gtapp_enc_ie.c:1756 50083 31-May-13

CSCue46044 GboIP: Unblock/reset from BSS does not unblock all BVCIs 50083 31-May-13

CSCue50748 Assertion failure at sess/sgsn/imsimgr/imsimgr_util.c:135 50083 31-May-13

CSCue52636 Inappropriate severity level for some new R14 SNMP Traps 50083 31-May-13


35/48



35


CSCue53476 Sessmgr Assert sgsn-app/sm/smg_fsm_table.c:1536SmGenReallocNwResInd()

50083 31-May-13

CSCue53930 RAU in a common-cell results in RAU reject because of redirectcomplete

50083 31-May-13

CSCue56461 Issues with 'prefer' option in call-control-profile 50083 31-May-13

CSCue56888 Fatal Signal 11: Segmentation fault at PC:sessmgr_sgsn_get_mem_stats()

50083 31-May-13

CSCue62078 Wrong values on SYSTEM_TYPE in CDR 50083 31-May-13

CSCue62469 Software upgrade changes saved cc- profile to ‘no gtp send imeisv’ 50083 31-May-13

CSCue70892 SGSN/MME losing 'gtpc dns-sgsn context S1mme' conf after reload 50083 31-May-13

CSCue78607 2G Inter-SGSN RAU failures and MCC in dns query inversed 50083 31-May-13

CSCue83935 Assertion failure at sess/sgsn/sgsn-app/pmm/pmm_util.c:14350 50083 31-May-13

CSCue89718 Problem during Gb interface extension 50083 31-May-13

CSCue90907 Assertion failure at sess/sgsn/sgsn-app/gtp_c/gtapp_tun_fsm.c:871 50083 31-May-13

CSCue91149 New log type is flooding the logs after the SGSN upgrade to R14 50083 31-May-13

CSCue99776 Disable intracer reporting for 2G calls 50083 31-May-13

CSCuf20099 Huge value in rncUnsentDownlinkVolume of SGSN CDRs 50083 31-May-13

CSCuf21644 Inter SGSN Inter RAT RAU: wrong DNS query MCC encoding 50083 31-May-13

CSCuf28953 SGSN: Old RAI not correctly derived from RAU 50083 31-May-13

CSCuf46849 SGSN::IRAU failure after cleaning status entries in CCP 50083 31-May-13

CSCuf55736 'rNCUnsentDownlinkVolume' in SCDR to be limited to 4 bytes incustom11 50083 31-May-13

CSCuf57224 SGTP-Service cannot be shared between MME and SGSN - not indocs

50083 31-May-13

CSCuf65654 out_of_memory+0xe6/0xf0 - Demux PSC cards crashed 50083 31-May-13


36/48



36


CSCug01808 WARNING severity level NOT found for ‘SGSNRMMemWarn’trap

50083 31-May-13

CSCug02017 Wrong STATE, SEVERITY fields for some SDH traps in thestarent.my file

50083 31-May-13

CSCug05570 BSC Lock Statistics Modified 50083 31-May-13

CSCug08563 PC: [063194fd/X] pmm_ms_fsm_handle_sgsn_ctx_response() 50083 31-May-13

CSCug13753 PTMSI relocation cmd doesn't fill the correct RAI IE 50083 31-May-13

CSCug14763 Suspend/resume Notification retransmission stats to be displayed 50083 31-May-13

CSCug21561 Many SMGRs full call reject messages and some SMGRS in warnstate

50083 31-May-13

CSCug23354 3G GMM-SM counters showing abnormal values after upgrade toR14.0.48062

50083 31-May-13

CSCug26715 TCAP abort, on user attach attempt 50083 31-May-13

CSCug28708 SGSN: sessmgr crash "get_first_matched_pdp_rcrd_from" (14.048062)

50083 31-May-13

CSCug30668 GTPP_DATA_RECORD_TRANSFER_REQUEST_MSG flooded

in Intracer for 2G subs

50083 31-May-13

CSCug39686 Flush-LL in case of Intra SGSN ISHO 50083 31-May-13

CSCug44160CSCue27188

SGSN don't have the right PGW FTEID in CSR after SGWrelocation

50083 31-May-13

CSCug54631 [s4-sgsn] ISR IE miss in MBR to SGW if UE IRAT from low rangemme-group

50083 31-May-13

CSCug55229 [s4-sgsn] crash at sess/egtp/egtpc/egtpc_evt_handler_func.c:2100 50083 31-May-13

CSCug59879CSCtz98440

Crash @ sessmgr_sgsn_handle_new_call(*) 50083 31-May-13

CSCug70021 sgptcmgr crash - Fatal Signal 11 Segmentation fault 50083 31-May-13

CSCug74229 Session manager Crash in SGSN atsmn_preserve_handle_dp_mod_cnf()

50083 31-May-13


37/48



37


CSCug78291 Sessmgr crashes on SGSN: Assertion failures:ConvertGtpIpAddrToSmIpAddr

50083 31-May-13


49490 13-May-13

CSCug28708 SGSN: Session Manager crashes when fallback-to-first-in-subscription is configured

49490 13-May-13




49490 03-May-13

CSCug28708 SGSN: Session Manager crashes when fallback-to-first-in-subscription is configured

49490 03-May-13



CSCue46044 GboIP: Unblock/reset from BSS does not unblock all BVCIs 48817 15-Apr-13

CSCue53930 RAU in a common-cell results in RAU reject because of redirectcomplete

48817 15-Apr-13

CSCue62078 Wrong values on SYSTEM_TYPE in CDR 48817 15-Apr-13

CSCue72816 SCCP routes at SM/MM out-of sync (High Attach failure ratio inSGSN)

48817 15-Apr-13

CSCuf20112 standby QGLC ports in LAG have wrong link status "down" 48817 15-Apr-13

CSCuf20099 Huge value in rncUnsentDownlinkVolume of SGSNCDRs 48480 20-Mar-13

CSCub13928 npumgr crash::Nonfatal warning at messenger/xpt_tcp.c:1086 48062 20-Feb-13

CSCue03201 PC: [05926a27/X] sessmgr_flow_operation_callback() 48062 20-Feb-13

CSCtn89667 [S4-SGSN] Support to send UE timezone in gtpv2 “create sessionrequest”

47681 31-Jan-13

CSCtq06335 GGSN has wrong output for CLI show session setuptime 47681 31-Jan-13

CSCtu14184

CSCub81724

[SysTest] Assrt failure at rct/rct_spc.c:642 seen during SMCswitchover

47681 31-Jan-13


38/48



38


CSCtu26575 File next_seq_num.seq is not generated after R12.0.40405 upgrade 47681 31-Jan-13

CSCtw56268 Gb: 2G-ret-attch-accept counter increased (x4-5) since Rel 12upgrade

47681 31-Jan-13

CSCtw81486 Call distribution in Sessmgr are not even in SGSN 47681 31-Jan-13

CSCtx36987 SCDR gtpp out of order sequence numbers 47681 31-Jan-13

CSCtx70969 Power: Audible alarm does not clear after power failure 47681 31-Jan-13

CSCty25533 [14.0]:Retransmission of Secondary pdp context request handling 47681 31-Jan-13

CSCty41636 STM1/OC3 ATM Line Card stops passing traffic until reset 47681 31-Jan-13

CSCty63600 ISRAU rejected in 2G if Addtional Old RAI, P-TMSI Type IE's are present

47681 31-Jan-13

CSCty94212 [APS]: Card Reboot should be treated as SF in line with peer view 47681 31-Jan-13

CSCtz03600 Security mode is incorrect in EGTP_CONTEXT_RESPONSE in 2GOLD ISRAU

47681 31-Jan-13

CSCtz26111 Identification Request should not be triggered 47681 31-Jan-13

CSCtz30782

CSCtz35640

SGSN does not process NAS messages after RAB release 47681 31-Jan-13

CSCtz65102 SGSN Release RAB resources on DT call with GTP-U path Failure. 47681 31-Jan-13

CSCtz85522 [SNMP]:FractE1T1LMIUp traps r getting generated for paths havinge1 alarm

47681 31-Jan-13

CSCtz86094CSCtz88342CSCtz90969

CSCtu21092

CSCub04727

ATM Line Card without TX Traffic after PSC migration 47681 31-Jan-13

CSCtz97262CSCzn32101

[14.0]: “show s4-sgsn statistics is not working correctly” 47681 31-Jan-13

CSCua09885 SGSN sends wrong PLMN in Create-PDP ULI 47681 31-Jan-13

CSCua16745CSCub02831

Assertion failure at sess/sgsn/sgsn-app/gtp_c/gtapp_tun_fsm.c:2973 47681 31-Jan-13


39/48



39


CSCua21893 621932411 Assertion failure at sess/smgr/sessmgr_gprs.c:11519 47681 31-Jan-13

CSCua26068 [APS]:K1 byte is sending wrong value after card reboot 47681 31-Jan-13

CSCua28913 Assertion failure at sess/snx/drivers/sgsn-app/sgsn_app_drv.c:553 47681 31-Jan-13

CSCua46610 "rx total error bytes" counter incrementing after SMC switchover foractv

47681 31-Jan-13

CSCua60924 Incorrect sctp path Primary/active status in a particular scenario 47681 31-Jan-13

CSCua63204 LPM: NPU lookup table not updated on Routing tab change 47681 31-Jan-13

CSCua65427 Multiple linkmgr crashes -As. Fail.-

sess/sgsn/linkmgr/linkmgr_med.c:564

47681 31-Jan-13


Assertion failure at sess/sgsn/sgsn-app/access/access_iu.c:370 47681 31-Jan-13

CSCua73179 Assertion failure at sess/sgsn/sgsn-app/dp/sn_dp_network.c:1298 47681 31-Jan-13

CSCua74399 Fatal Signal 11: Segmentation faultsessmgr_gprs_fsm_state_intra_rau()

47681 31-Jan-13

CSCua81796CSCua09766

SRNS GnGp:SGSN is rejecting FWD_REL_REQ with no preamblefor Target-id

47681 31-Jan-13


Assertion failure at sess/sgsn/sgsn-app/app/sgsn_3g_2g_handover.c:517

47681 31-Jan-13

CSCub05407 Inconsistency in show lawful intercept all and full all 47681 31-Jan-13

CSCub10599 Multi-event sent in case of multi-target-already active PDP 47681 31-Jan-13

CSCub18864 Fatal Signal 11: Segmentation faultsessmgr_process_gprs_add_session_req

47681 31-Jan-13

CSCub23315 Clear SCTP statistics error 47681 31-Jan-13


IMSIMGR is in Warn state 47681 31-Jan-13

CSCub32085 After change in LAC, more attach and 3G RAU rejects (implicitdetach) observed

47681 31-Jan-13

CSCub34190 3G Visiting Subscriber count showing “0” at Delhi SGSN 47681 31-Jan-13


40/48



40


CSCub34934 Inter SGSN RAU failure 47681 31-Jan-13

CSCub42044 Assertion failure at sess/smgr/sessmgr_gprs.c:10316 47681 31-Jan-13

CSCub45643CSCuc04741CSCuc24353

LTE to 3G redirect failing 47681 31-Jan-13

CSCub54050 Assertion failure at sess/sgsn/sgsn-app/access/access_main.c:2725 47681 31-Jan-13

CSCub58699 SGTPC Manager and Link Manager in high memory state 47681 31-Jan-13

CSCub61089 Kernel crash and/or soft lockup after 208 days of uptime 47681 31-Jan-13

CSCub65605 Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:5796 47681 31-Jan-13

CSCub65696 Inconsistent value for "sgsn_3g_attached" counter in specific RA 47681 31-Jan-13

CSCub69352 Add logging to print SCTP links going down with reason 47681 31-Jan-13

CSCub69358 Enhance logs to print lwhen the NSVCI going down with the cause 47681 31-Jan-13

CSCub71327 Assertion failure at sess/sgsn/sgsn-app/sm/sm_gtp_msg.c:1425 47681 31-Jan-13

CSCub74278 [LCS] show sub sgsn-only full does not show any info of LCSsubscription

47681 31-Jan-13

CSCub81586 Enhance the NSVCI down SNMP trap 47681 31-Jan-13

CSCub83903 [MT-SMS]: Handling of Empty TC BEgin and CONT landing ondiff linkmgrs

47681 31-Jan-13

CSCub85044 SCTP Chunks are not padded to a multiple of 4 bytes 47681 31-Jan-13

CSCub85912 Default inroamer reject cause code 47681 31-Jan-13

CSCub88461 3G Attached stats showing more subscriber counts than actualnumbers

47681 31-Jan-13

CSCub90490 GMM implicit detach timer value 47681 31-Jan-13

CSCub92623CSCuc51662

Fatal Signal 11: Seg. fault -sma_lho_handle_irc_in_irc_n_rab_estb_rsp()

47681 31-Jan-13

CSCub93198 SGSN Node stopped responding after PSC card migration 47681 31-Jan-13


41/48



41


CSCub94839CSCud97666

ASR5K SGSN implicit detach sent during RA from 3G to 2G 47681 31-Jan-13

CSCuc03232 M3UA Wrong Error Code for M3UA_SGP_ASPTM_I_004 47681 31-Jan-13

CSCuc08320 Unable to add a specific operator policy 47681 31-Jan-13

CSCuc10531 3G-attach-fail-iu_release segregation (internal and external) 47681 31-Jan-13

CSCuc12638 Enhancement -Segregation of 3G activation failure/reject causecodes

47681 31-Jan-13

CSCuc21119 [14.0 S4-SGSNLoad]:sessmgr_gprs_process_update_correlation_id()

47681 31-Jan-13

CSCuc22130 Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:6015 47681 31-Jan-13

CSCuc25534 SGSN is restarting procedure when MS is re-sending APCQ onT3380 expiry

47681 31-Jan-13

CSCuc26816 SGSN IMSI Analysis Causing intermittent attach Reject. 47681 31-Jan-13

CSCuc44183 Assertion failure at sess/smgr/sessmgr_gprs_fsm_sm.c:14603 47681 31-Jan-13

CSCuc48871 HSPA QoS feature- Enhancement to prevent QoS re-negotiationfailures.

47681 31-Jan-13

CSCuc49976 Crash in pmm_map_fsm_handle_isd_ind_as_detached() 47681 31-Jan-13

CSCuc53264 TACACS: Assertion failure at messenger/evt_timer.c:124 47681 31-Jan-13

CSCuc53379CSCub93751

Sessmgr Crash- Fatal Signal 6: Aborted PC: [09f3e20b/X]free_acct()

47681 31-Jan-13

CSCuc55856 Sessmgr task instances in warning status 47681 31-Jan-13

CSCuc56495CSCuc63112

CSCud43394

Fatal Signal 11: Segmentation faultsgtpcmgr_process_fill_demux_stat()

47681 31-Jan-13

CSCuc58883 Assertion failure at sess/sgsn/sgsn-app/access/access_iu.c:6789 47681 31-Jan-13

CSCuc73538 [ATM]: IP-interface going down after PSC migration. 47681 31-Jan-13

CSCuc77166 Assertion failure at sess/sgsn/sgsn-app/sm/smg_fsm_table.c:5133 47681 31-Jan-13


42/48



42


CSCuc79207CSCud16741

Assertion failure at sess/sgsn/sgtpcmgr/sgtpcmgr_sgtp.c:1680 47681 31-Jan-13

CSCuc84188 [Crash]Assertion failure at sess/sgsn/sgsn-app/gtp_c/gtapp_enc_ie.c:152

47681 31-Jan-13

CSCuc88087 DPCQ should not be triggered in this scenario 47681 31-Jan-13

CSCuc91288 After PSC migration system un-responsive 47681 31-Jan-13

CSCuc94427 SR 623361415 - MAP error code mapping issue 47681 31-Jan-13

CSCuc95980 sessmgr crash, Fatal Signal 6: Aborted, PC: [b7e2a491/X] kill() 47681 31-Jan-13

CSCuc96212 Congestion-control policy comes twice in the configuration 47681 31-Jan-13

CSCuc96492 Access NPU RDRAM for forwarding lookup 47681 31-Jan-13

CSCuc97618 Syslogs full of "sgsn_sessmgr_update_gprs_ns_dest_inst Failed" 47681 31-Jan-13

CSCuc98179 Fatal Signal 6: Aborted PC: [b7e2a491/X] kill() 47681 31-Jan-13

CSCuc99697 [M3UAPCUnavailable] trap is generated every time DUNA isreceived from peer.

47681 31-Jan-13

CSCud00368 [SGSN] Assertion failure at

sess/sgsn/sgtpcmgr/sgtpcmgr_util.c:1230

47681 31-Jan-13


Support for modified SCDR fields. 47681 31-Jan-13

CSCud04626 [14.0] STATUS msg sent by SGSN after Attach complete 47681 31-Jan-13

CSCud08641 Assertion failure at sess/egtp/egtpc/egtpc_validate_evt.c:1539 47681 31-Jan-13

CSCud09727 14.0-Fatal Signal 11: Segmentation fault- pmm_get_context_from_msid()

47681 31-Jan-13

CSCud12250 3G MOCN - SGSN is sending incorrect RAI in Attach Accept 47681 31-Jan-13

CSCud16924 SGSN does not send GTP_RAN_INFO_RELAY_MSG to RAN 47681 31-Jan-13

CSCud18229 ASR5k SNMP traps stop being generated 47681 31-Jan-13

CSCud20425CSCtz09531

Fail to access to ASR5000 with tacacs+ and TELNET 47681 31-Jan-13


43/48



43


CSCud21929 The SGSN sends an invalid ULI in GTP-Update after SRNS 47681 31-Jan-13

CSCud23803 Should SGSN send feature BitMap IE in PTP BVC reset ? 47681 31-Jan-13

CSCud24810 Assertion failure at npu/npumgr/npumgr_port_handler.c:9602 47681 31-Jan-13

CSCud33031 Assertion failure at sess/sgsn/sgsn-app/pmm/pmm_fsm.c:6280 47681 31-Jan-13

CSCud36010CSCuc63520CSCuc50410

Fatal Signal 11: Segm.. PC: [066334ea/X]SmappHandleIncomingHandOffReq()

47681 31-Jan-13

CSCud36094 [14.0]Change display of PDN Allocation Type 47681 31-Jan-13

CSCud38545CSCub42141

Break up for 2G-attach-rej-network-failure and comb in bulkstatistics

47681 31-Jan-13

CSCud38565CSCub71229

Break up for 3G-attach-rej-network-failure and comb in bulkstatistics

47681 31-Jan-13

CSCud38571 Break up for 2G simple and comb attach failure in bulk statistics 47681 31-Jan-13

CSCud39033 No s4 subs in SGSN but it showed in statistics (sgsn-subs-type-s4) 47681 31-Jan-13

CSCud40833 SGSN sub-profile has incorrect APN list (diff. from HLR profile) 47681 31-Jan-13

CSCud43005 Segmentation Fault at pmm_app_fill_mm_debug_info() 47681 31-Jan-13

CSCud60630 Assertion failure at sess/sgsn/sgsn-app/pmm/pmm_fsm.c:6280 47681 31-Jan-13

CSCud61994 SGSN/MME: PDBN114G Gn interface issue 47681 31-Jan-13

CSCud66833 [14.0] P-GW-address config in apn-profile help text needs change 47681 31-Jan-13

CSCud69457 QGLC card upgrade fails with CLI crash on 12.0.46497 47681 31-Jan-13

CSCud73404 [14.0] PDP activation support if EPS subs available for non EPCdevice

47681 31-Jan-13

CSCud79150 [14.0] RAU Accept goes with wrong RAI value in Inbound InterSRNS

47681 31-Jan-13

CSCud84892 Several GB links not coming up when a uplink router reloaded 47681 31-Jan-13

CSCud88111 SGSN not answering all Attach requests 47681 31-Jan-13


44/48



44


CSCud90441 Service Request with Page Response without Page req initiated bySGSN

47681 31-Jan-13

CSCud93223 High rate (20%) of T3360/T3370 timeouts 47681 31-Jan-13

CSCud93692 ATM OLC card behind a standby PSC 47681 31-Jan-13


[14.0] description need to be changed for "queue-unknown-tlliexpiry-time"

47681 31-Jan-13

CSCud12250 3G MOCN - SGSN is sending incorrect RAI in Attach Accept 47045 21-Dec-12

CSCud33031 Assertion failure at sess/sgsn/sgsn-app/pmm/pmm_fsm.c:6280 46803 07-Dec-12

CSCud36010 Fatal Signal 11: Segm.. PC: [066334ea/X]SmappHandleIncomingHandOffReq()

46803 07-Dec-12

CSCud40833 SGSN sub-profile has incorrect APN list (diff. from HLR profile) 46803 07-Dec-12


Support for modified SCDR fields. 46551 23-Nov-12

CSCud00368 [SGSN] Assertion failure atsess/sgsn/sgtpcmgr/sgtpcmgr_util.c:1230

46551 23-Nov-12

CSCud09727 14.0-Fatal Signal 11: Segmentation fault-

pmm_get_context_from_msid()

46551 23-Nov-12


Need a per RNC CLI to control ARP inclusion in RAB req - problemre-opened.

46345 07-Nov-12

CSCua60924 Incorrect SCTP path primary/active status in a particular scenario 46345 07-Nov-12

CSCua96149 Assertion.../sgsn-app/gtp_c/gtapp_enc_ie.c:152sn_gt_encode_cause_ie()

46345 07-Nov-12

CSCub28951 Non-fatal warning at messenger/xpt_tcp.c:1086 46345 07-Nov-12

CSCuc06178 SFTP connection to ASR5K fails with public key 46345 07-Nov-12

CSCuc15969 Error BSSGP decoding messages in Monitor Subscriber 46345 07-Nov-12

CSCuc25534 SGSN is restarting procedure when MS is re-sending APCQ onT3380 expiry

46345 07-Nov-12


45/48



45


CSCuc52120CSCtz00983

RAI-FQDN-based DNS Resolution for non-LocalRAIs. 46345 07-Nov-12

CSCuc54908 14.0-MME/SGSN Combo -sgtpcmgr- Seg fault -snx_add_small_dbufs()

46345 07-Nov-12

CSCzn22926 Trap is not cached by the WEM when a OAM cable is unplugged 46345 07-Nov-12

CSCzn33011CSCuc36053CSCuc36179CSCuc36486

SGSN not sending proper QoS values in activate accept 46345 07-Nov-12

CSCub45643 LTE to 3G redirect failing 46033 19-Oct-12

CSCub60700 PC: [035bfcc1/X] sessmgr_get_s4_sgsn_gtpu_stats() 46033 19-Oct-12

CSCuc28574 Assertion failure at sess/aaamgr/aaamgr_handler.c:53078 46033 19-Oct-12

CSCuc48161 SGSN sends "PS LCS Not Supported ByUE" in UGL to HLR butLCS is disabled

46033 19-Oct-12

CSCtn89667 [S4-SGSN] Support to send UE timezone in gtpv2c “create sessionrequest”

45722 28-Sept-12

CSCto55464 Response for XID negotiation should not be sent in this scenario. 45722 28-Sept-12

CSCtq20863 Flush LL Message Sent to BSC When Intra-RAU Occurs in SGSNfrom a Different Cell

45722 28-Sept-12

CSCtr20596 [S4-SGSN] Recovery of SGW tunnels and PDN connections to besupported

45722 28-Sept-12

CSCtr82390 [12.2]: Gmm-sm Stats is pegged wrongly in this scenario 45722 28-Sept-12

CSCts71327 [S4-SGSN]SGSN shall set initial attach indicator bit in UGL/ULR 45722 28-Sept-12

CSCtw71458 PSCA, PPC cards to be included in "StarentCardType" object ID 45722 28-Sept-12

CSCtx68408CSCtw77656CSCtw89737CSCua60627

Segregate RAU Failure due to Ongoing procedure - referCSCtw89737

45722 28-Sept-12

CSCtx89243 M-LMGR bounces fill up “show messenger bounces” in non-SGSNSSDs

45722 28-Sept-12


46/48



46


CSCty32423 Assertion failure at sess/sgsn/sgsn-app/pmm/pmm_proc.c:2788 - 2crashes

45722 28-Sept-12

CSCty60455 Receiver Window Credit = 1048576 in Init Ack when configured as32768

45722 28-Sept-12

CSCty66505 [12.0] Minor display error for following IRAT counters. 45722 28-Sept-12

CSCtz25837 [Scale] sgsn-sys 86401 error:sgsn_sessmgr_update_gprs_ns_dest_inst Failed

45722 28-Sept-12

CSCtz30291 [14.0]: Granularity difference for t3323 while displaying andconfiguring

45722 28-Sept-12


Ares testctrl fails to start during MIO switchover & DPC restart 45722 28-Sept-12


ARP IE is included in RAB messages only if configured in apn- profile

45722 28-Sept-12

CSCub18978 Authentication Frequency is not working for 2G (GPRS) access-type 45722 28-Sept-12

CSCub28951 Nonfatal warning at messenger/xpt_tcp.c:1086 45722 28-Sept-12


CDR record opening time is greater than the filename 45722 28-Sept-12

CSCub55089 [14.0] "treat-as-hplmn" not seen in config mode in call-control- profile

45722 28-Sept-12

CSCub56059 SGSN must re-establish DT when GGSN changes it GTPU TEID inUPCR

45722 28-Sept-12

CSCub89748 Samsung Galaxy S - 3g to 2g handover failing with 14.0.44093 45722 28-Sept-12

CSCzm65084 IP route overwritten when entered for point-to-point link 45722 28-Sept-12

CSCzn26096 Configuration change for sctp-max-in-strms and sctp-max-out-strms

on SGSN

45722 28-Sept-12

CSCzn29099 SNMP - Unknown type of card in the SNMP trap 45722 28-Sept-12

CSCzn34172 [11.0 Longevity] Assertion failure at sess/sgsn/sgsn-app/dp/sn_dp_util.

45722 28-Sept-12

CSCzn40829 Wrong Total-Attach-Failure counter value 45722 28-Sept-12


47/48



47


CSCua55325 [custom41] Pdp Type displayed wrongly in monitor protocol 44756 6-Aug-12

CSCua55378 [custom41] Inconsistent representation of True Boolean Values inencoding

44756 6-Aug-12

CSCub07526 S-SMO-CDR triggering difference in 12.0 and 14.0 44756 6-Aug-12

CSCub12399 [14.0 Platform] Data stops on OLC2 card on task kill of npumgr inPSC2

44756 6-Aug-12

CSCts37482 Support for ASCII SCDR format 44668 31-Jul-12

CSCts54628 Starting value for GPRS ciphering algorithm input always the same 44668 31-Jul-12

CSCtz51789 Segmentation fault - boxer/pmm_util_handle_addl_ie_release_mm_context()

44668 31-Jul-12

CSCua29780 SCTP Asymmetric traffic flow 44668 31-Jul-12

CSCua40921 SNMP Fatal Signal 11: Segmentation faultsnmp_retrieve_one_port_data()

44668 31-Jul-12

CSCua66309 Fatal Signal11:Segmentation faultPC:03a5281c/X]smgr_is_local_rai

44668 31-Jul-12

CSCua75039 PDP-override statistics under show gmm-sm statistics need to be

enhanced

44668 31-Jul-12

CSCzn40829 Wrong Total-Attach-Failure counter value 44668 31-Jul-12

CSCua33403 [CLC2] E1/Low Order Path/Higher order path/LMI alarm detectionfailure.

44668 31-Jul-12

CSCua35729 Assertion failure at sess/smgr/sessmgr_nlp.c:508 44668 31-Jul-12

CSCua49139 Assertion failure at sess/sgsn/imsimgr/imsimgr_util.c:2088 44668 31-Jul-12

CSCua57465

CSCua57487

[custom 41]Segfault PC: [0eb1834c/X]

GtppPrintSGSNPDPRecordCustom2_cgf()

44668 31-Jul-12

CSCua66309 Fatal Signal11:Segmentation faultPC:03a5281c/X]smgr_is_local_rai

44668 31-Jul-12

CSCua69730 Assertion failure at sess/sgsn/sgsn-app/sm/smapp_interface.c:2763 44668 31-Jul-12

CSCua69834 Assertion failure at sess/sgsn/sgsn-app/gtp_c/gtapp_tun_fsm.c:9702 44668 31-Jul-12


48/48



CSCua73137 PC: [05f40c6b/X]sgsn_app_pmm_gtp_send_ms_info_change_notif_req(

44668 31-Jul-12

CSCtq29807 CLI to limit number of SCTP chunks per message 44093 29-Jun-12

CSCts54628 Starting value for GPRS ciphering algorithm input always the same 44093 29-Jun-12

CSCty60455CSCua54617

Receiver Window Credit = 1048576 in Ini

14 0 51375 sgsn release notes mr

Documents