GGSN 5.0.1 Release Notes V 9.0.3

1
GGSN5.0.1
RELEASE NOTES
Document Version: 9.0.3 , Document Status : Standard
© Copyright Nortel 2009

All rights reserved.
Richardson, TX, U.S.A.
NORTEL CONFIDENTIAL: The information contained in this document is the property of

Nortel. Except as specifically authorized in writing by Nortel, the holder of this document shall
keep the information contained herein confidential and shall protect same in whole or in part from
disclosure and dissemination to third parties and use same for evaluation, operation, and
maintenance purposes only.
Release Notes for GGSN5.0.1

2
Publication History
VERSION DATE AUTHOR EXPLANATION OF AMENDMENTS
Aug 07, Praveen

1.0 Initial Release
2006 Araveti
Updated 5.0 Patch Ids in section 5.1.
Removed “Patches Sourced in 5.0” as this is redundant from 5.0 Release
Notes.
Remove duplicate entries from section 5.2 that are in 5.1
Removed internal CRs that are not customer related and updates some titles
Nov 03, Muralidhar from section 10.2
1.1
2006 Kolapalli Updated descriptions, impact and workarounds for better understanding
under “Detailed description of known issues”
Added description for CRs that are missing.
Updated the titles of some of the CRs in section 5.1
Updated active CABs
Patch Package 1, known issues, active CABs updated. Add new columns in
Jan 31,
1.2 Dan Gunther 6.1 Table 1 “Nature of Patch” and “Dependencies / Prerequisites”.
2007
Remove 5.0 Limitation section.
Update section 7 for configuration changes to OA&M servers and RADIUS
1.3 Feb 8, 2007 Dan Gunther trunk provisioning. Additional entry to section 10 for
Active CABs.
Feb 21,
1.4 Dan Gunther Update Active CABs.
2007
Patch Package 2, updates to Configurations and Recommendations, OA&M,
1.5 Apr 4, 2007 Dan Gunther Known Issues Deferred, Active CABs, Acronyms. Limitations Section 8
added.
May 30, David
1.6 Added “export config” limitation to Known Issues
2007 Corekin
June 18, Remove patch G501_01484327ACT_NETINET and add patch
2.0 Al Carriere
2007 G501_01484327AACT_NETINET
June 21, Added recently released EMG patches:
2.1 Al Carriere
2007 G501_01658130EMG_GTP and G501_01621446EMG_GTP.
Information related to Patch Package 3 added.
o Patches provided with load
o Patches Requiring Special Handling for Application or Removal
o GGSN5.0.1 Known Issues
August 14, Deepak o Active CABs
3.0
2007 Nagarajan Information related to CR ‘Q01724313 – SNTP server unsynchronized’
added to OA&M section.
Information related to CR ‘Q01647303-02 – Redundant CMC sends memory
size changed alarm to Active CMC’ added to OA&M section.
September Deepak Information related to 070828-30631/ Q01737685 added.

3.1
04, 2007 Nagarajan Information related to Q01522427-01 added.
September Deepak
3.2 Information related to 070912-44775/ Q01745586 added.
12, 2007 Nagarajan
Information related to Q01755670 added.
October 4, Deepak
3.3 Information related to
2007 Nagarajan
071004-66154/ Q01759935 added.

3
October 28, Deepak

3.4 Shaded patches listed in Table1 un-shaded after release of patch package 3.
2007 Nagarajan
October 31, Deepak
3.5 Patch G501_01730666EMG_EMS added to Table1
2007 Nagarajan
Information related to Q01780402 updated – Patch G501_01639302_GTP
November Deepak
3.6 requires all PDP contexts are deleted and traffic disabled before applying and
7, 2007 Nagarajan
un-applying this patch.
Information related to Q01784177 updated – PDP contexts must be deleted
November Deepak
3.7 prior to applying or un-applying patch package 3. Section Patch Package
19, 2007 Nagarajan
Application Instructions has been updated.
Information related patch package 4 updated. Please refer to Table1 for
details.
Review minutes updated.
January 11, Deepak
4.0.4 Special handling instructions for G501_01466350ACT_LI updated.
2008 Nagarajan
Information related to 071211-27286/ Q01801692 updated.
V status patches grayed out in Table1.
Info related to CR Q01798601 has been updated.
Information related patch package 4 version 2 updated. Patch
January 25, Deepak G501_01670464_CPM removed from Table1.
4.0.5
2008 Nagarajan Info related to CR Q01618197-05 updated.
Information related patch package 5 updated.

o Patch Package Application Instructions for Patch Package 5
o Table1 updated with patch package 5 and EMG patch details.
o Table 2 updated with special handling instructions for patch package 5
patches.
Information related 070420-05121 has been added.
April 8, Deepak
5.0 Information related to CR Q01743059-05 updated. The Field Application
2008 Nagarajan
Instructions for the patch G501_01743059AEMG_CONFMGR has been
updated. Please follow the instructions given in the special handling section
instead of the instructions on the patch PD file.
Information related to 061024-22500/ Q01489687 added.
Information related to 080218-84214/ Q01830205-01 added.
Information related to Q01795346-03 added.
May 13, Deepak
5.0.1 Information related to 080513-60317/ Q01874195 has been updated.
2008 Nagarajan
Added patch G501_01871586EMG_PAR, G501_01855017_GTP to Table 1
due to patch package 5 respin.
Reorganized Section 6.0 Patch Package Application and Removal with
June 11, additional steps.
5.0.2 Shijian Zhou
2008 Information related to CR Q01884435-01 (a known issue) has been updated.
The option to reboot the GGSN CMC2 cards for GGSN5.0.1 has been
removed.
Added information on Case 080721-16197/CR Q01903693 (a known issue)

July 22, to correct the erroneous texts in NTP 411-5221-926 Version 10.40 Nortel
5.0.3 Shijian Zhou
2008 GGSN User Guide -> Section Functional description -> GTP accounting ->
Accounting record generation -> G-CDR identification.
Added information on Case 080604-78158/CR Q01911533 (a known

August 12,
5.0.4
2008
Shijian Zhou issue) to clarify on the Maximum Bit Rate supported by Nortel
GGSN5.0.1 product.

4
Removed EMG patches G501_01877146EMG_SERVICES,

August 14, G501_01865914EMG_AAA, G501_01885754EMG_RPC,
5.0.5 Shijian Zhou
2008 G501_01899346EMG_GTP as they are not defined in the patch
package 5 version 4 Pd file.
Information related patch package 6 version 3 updated.
• Patch Package Application Instructions for Patch Package 6
October 24, Deepak • Table1 updated with patch package 6 and EMG patch details.
6.0
2008 Nagarajan • Table 2 updated with special handling instructions for patch package 6
patches.
• Information related to Q01933102-01 has been updated.
December Deepak
7.0 • Table1 updated with patch package 7 and EMG patch details.
08, 2008 Nagarajan
• Table 2 updated with special handling instructions for patch package 7
patches.
March 18, Deepak Pre-requisite patch for G501_01794436EMG_GTP – added to Patch

7.0.1
2009 Nagarajan Sequencing with Dependencies Resolved (Table1)
Patch G501_01589010_GTP incorrectly listed as part of patch package 7.

March 18, Deepak
7.0.2 This patch is part of patch package 2. The correction has been updated in
2009 Nagarajan
Table1.
Correction to Table1 updated.

March 23, Deepak - Few Activate-able patches did not have the ACT tag under the PKG
7.0.3
2009 Nagarajan column.
- Incorrect patch dependency for G501_01662594ACT_SVC.
Correction to Table1 updated.

March 24, Deepak
7.0.4 - G501_01839550EMG_GTP and G501_01799972BEMG_DCC included
2009 Nagarajan
twice.

May 14, • Table1 updated with patch package 8 and EMG patch details.
8.0 Bai Lin
2009 • Table 2 updated with special handling instructions for patch package 8
patches.
May 15,
8.0.2 Bai Lin Added quick links for the last 5 patches in Table 2
2009
Removed patches G501_01881900_GTPCMC, G501_01881900_GTPSSP

June 1, from patch package 8.
8.0.3 Shijian Zhou
2009 Clariry that patch package 8 does NOT require resync for application and
removal.

5
Removed patches G501_02005047_WRAP, G501_02002598_GTP from

patch package 8
July 20,
8.0.4 Bai Lin Added patch G501_01996131_GTP in patch package 8
2009
Removed patch G501_02002598_GTP from Table 2
Removed special handling for patch G501_02002598_GTP at Section 6.3.65
Removed patch G501_01818007_SVC from Table 1.

Aug 05,
8.0.5 Bai Lin Remove patch G501_01815175A_TIMESSP from Section 6.3 Patches
2009
Requiring Special Handling.

August 17,
9.0 Bai Lin • Table1 updated with patch package 9 and EMG patch details.
2009
• Table 2 updated with special handling instructions for patch package 9
patches.
Sep 16,
9.0.1 Bai Lin • Add Appendix C: Patch Obsoletion Table
2009
Oct 14, Troy • Remove patch G501_01996131_GTP from Table 1, and clean up some
9.0.2
2009 Ronholdt tables.
Oct 21, Troy

9.0.3 • Update Patch count from 304 to 302.
2009 Ronholdt

6
Table of Contents
1 Introduction........................................................................................................... 10
1.1 Purpose and Scope..........................................................................................10
1.2 Audience .........................................................................................................10
1.3 Software Load Line-up ...................................................................................10
2 Supported External Servers/Releases ................................................................... 11
3 Supported Software Upgrade Paths ...................................................................... 12
4 New Features and Enhanced Features .................................................................. 13
4.1 GGSN5.0 New Features .................................................................................13
4.2 Feature Patches Sourced in GGSN5.0.1 .........................................................15
4.3 Description of Enhancements in GGSN5.0.1 .................................................17
4.4 Feature Patches Sourced in GGSN5.0 ............................................................18
5 Issues Fixed/Corrected.......................................................................................... 19
5.1 Patches Sourced in GGSN5.0.1 ......................................................................19
5.2 Issues Fixed in GGSN5.0.1 and SCS5.0.2......................................................23
5.3 Patches Sourced in GGSN5.0 .........................................................................25
5.4 Issues Fixed in GGSN5.0 and SCS5.0.1.........................................................29
6 Patches Provided with Load.................................................................................. 33
6.1 Patch List ........................................................................................................33
6.2 Patch Package Application and Removal .......................................................54
6.2.1 Information on Previous Patch Packages...................................................54
6.2.2 Application and Removal Instructions for Patch Package 9......................54
6.2.2.1 Warnings and Notes..........................................................................54
6.2.2.2 Procedure to Apply Patch Package 9 ................................................55
6.2.2.3 Procedure to Remove Patch Package 9.............................................57
6.2.2.4 Special Handling Instructions ...........................................................57
6.3 Patches Requiring Special Handling ..............................................................58
6.3.1 G501_01584892EMG_PATCHMGR........................................................60
6.3.2 G501_01223788ACT_P2ROUTING ........................................................60
6.3.3 G501_01341393A_ACCT .........................................................................60
6.3.4 G501_FF01385579ACT_DCCCMC .........................................................60
6.3.5 G501_FF01385579ACT_DCCSSP ...........................................................61
6.3.6 G501_FF01385577ACT_ERCMC ............................................................61
6.3.7 G501_FF01385577_ERSSP ......................................................................61
6.3.8 G501_01510180_LI...................................................................................62
6.3.9 G501_01484327AACT_NETINET...........................................................62
6.3.10 G501_01527169AEMG_GTP ................................................................62
6.3.11 G501_FF01369144ACT_PPDCMC .......................................................63
6.3.12 G501_FF01369144_PPDSSP .................................................................63
6.3.13 G501_01467598_GTP ............................................................................63
6.3.14 G501_01450778ACT_IFMGR ...............................................................63
6.3.15 G501_01573968_TRMGR .....................................................................64
6.3.16 G501_01568521_SSC3...........................................................................64
6.3.17 G501_FF01567650ACT_IPCMC...........................................................64

7
6.3.18 G501_FF01567650_IPSSP .....................................................................65

6.3.19 G501_01591035_GTP ............................................................................66
6.3.20 G501_01595094AACT_AAA ................................................................66
6.3.21 G501_01614712ACT_DCC ...................................................................66
6.3.22 G501_01646145A_PPDSSP...................................................................66
6.3.23 G501_01334913_DST ............................................................................67
6.3.24 G501_01639302_GTP ............................................................................67
6.3.25 G501_01653102ACT_GTP ....................................................................67
6.3.26 G501_01726458_PPDCMC ...................................................................68
6.3.27 G501_01726458_PPDSSP......................................................................68
6.3.28 G501_01778204ACT_GTP ....................................................................68
6.3.29 G501_01783408_FLOWMGT ...............................................................68
6.3.30 G501_FF01727897_GTP........................................................................69
6.3.31 G501_01466350ACT_LI........................................................................69
6.3.32 G501_01743059AEMG_CONFMGR ....................................................69
6.3.33 G501_00950877_FLOWMGT ...............................................................70
6.3.34 G501_01529555_OVLD.........................................................................71
6.3.35 G501_01727860_XPIF ...........................................................................71
6.3.36 G501_01850843ACT_DCC ...................................................................71
6.3.37 G501_01733134A_ACCTCMC .............................................................71
6.3.38 G501_01733134_ACCTSSP ..................................................................72
6.3.39 G501_01831139ACT_ACCTCMC ........................................................72
6.3.40 G501_01760965_GTPSSP .....................................................................73
6.3.41 G501_01760965_GTPCMC ...................................................................73
6.3.42 G501_01548395_GTPCMC ...................................................................73
6.3.43 G501_01796399ACT_SIG .....................................................................73
6.3.44 G501_01502203ACT_ACCTSSP ..........................................................74
6.3.45 G501_01798767AACT_GTP .................................................................75
6.3.46 G501_01728656ACT_GTPPCMC .........................................................75
6.3.47 G501_01728656_GTPPSSP ...................................................................76
6.3.48 G501_01548395_GTPSSP .....................................................................76
6.3.49 G501_01505119ACT_SNTP..................................................................77
6.3.50 G501_01831139_ACCTSSP ..................................................................77
6.3.51 G501_01795346EMG_TARPATCHER.................................................77
6.3.52 G501_01855017_GTP ............................................................................78
6.3.53 G501_01839550EMG_GTP ...................................................................78
6.3.54 G501_01300738_AAA ...........................................................................78
6.3.55 G501_01799972BEMG_DCC................................................................78
6.3.56 G501_01088170_SSH ............................................................................78
6.3.57 G501_01814048ACT_DCCCMC and G501_01814048_DCCSSP .......79
6.3.58 G501_01892881_GTPCMC and G501_01892881_GTPSSP ................79
6.3.59 G501_01863890_LI................................................................................79
6.3.60 G501_01912068_RMC...........................................................................80
6.3.61 G501_01913874ACT_GTP ....................................................................82
6.3.62 G501_01950186ACT_GTP ....................................................................82
6.3.63 G501_01915668_SVC............................................................................83

8
6.3.64 G501_01867815_GTP ............................................................................83

6.3.65 G501_01815175A_TIMECMC ..............................................................83
6.3.66 G501_02002598_GTP ............................................................................84
6.3.67 G501_02015821_GTP ............................................................................84
6.3.68 G501_02005896_INIT............................................................................84
6.3.69 G501_02018947_SUBMGR...................................................................84
6.3.70 G501_FF02007643ACT_DCC ...............................................................85
7 Configuration Changes and Recommendations.................................................... 86
8 GGSN5.0.1 Limitations ........................................................................................ 88
8.1 Rebooting from Flash Not Supported.............................................................88
8.2 VLAN, VPN, IP Services ...............................................................................88
8.3 CTP V2 on the SCS GUI ................................................................................89
8.4 VNC Client Support .......................................................................................89
8.5 Telnet Sessions on the GGSN.........................................................................89
8.6 Aggr APN Sessions can’t be Monitored on SCS Client.................................89
8.7 GGSN Ethernet Limitations ...........................................................................89
8.8 Restrictions for the BGP/VLAN Feature Support ..........................................89
8.9 Billing Limitations..........................................................................................90
8.10 GGSN Patching Limitation.............................................................................90
8.10.1 Work-around ...........................................................................................90
9 OA&M .................................................................................................................. 92
10GGSN5.0.1 Known Issues ................................................................................... 95
10.1 Known Issues with Planned Patches...............................................................95
10.2 Known Issues Deferred to a Later Release.....................................................95
11Active CABs ...................................................................................................... 119
12Appendix A: VLAN BGP VPN Call Model...................................................... 120
13Appendix B: Previous Patch Package Instructions............................................ 121
13.1 Patch Package Application Instructions for Patch Package 3 ......................121
13.2 Patch Package Application Instructions for Patch Package 4 ......................122
13.3 Application and Removal Instructions for Patch Package 5 ........................122
13.3.1 Warnings and Notes..............................................................................123
13.3.2 Procedure to Apply Patch Package 5 ....................................................123
13.3.3 Procedure to Remove Patch Package 5.................................................125
13.3.4 Procedure to Recover the GGSN ..........................................................126
13.3.5 Application and Removal Instructions for Patch Package 6.................126
13.3.5.1 Warnings and Notes........................................................................126
13.3.5.2 Procedure to Apply Patch Package 6 ..............................................127
13.3.5.3 Procedure to Remove Patch Package 6...........................................129
13.3.6.4 Special Handling Instructions .........................................................132

9

14Appendix C: Patch Obsoletion Table ................................................................ 135
15References.......................................................................................................... 136
16Acronyms........................................................................................................... 137

10
1 Introduction
1.1 Purpose and Scope
This document is intended to outline the Release Information for Nortel GGSN5.0.1
product. It lists features/enhancements, customer issues resolved in this release, and
known/un-resolved issues. For more information on Nortel GGSN5.0.1 product, please
refer to the NTP documents related to the release.
GGSN5.0.1 is a maintenance release on top of GGSN5.0, so all Limitations and Feature

Descriptions of GGSN5.0 are carried forward in this document.
1.2 Audience
This document is intended for use by Nortel engineers, and/or customers with the
assistance of Nortel personnel. This document assumes that the reader has a working
knowledge of the GPRS/UMTS network and related components. For detailed
information on GPRS/UMTS and other related components, please refer to the
appropriate documentation listed in Section 14 “References”.
1.3 Software Load Line-up
This document focuses on the fixes and outstanding issues relating to the Nortel
GGSN5.0.1 software release.
The names of the Final Compile loads are:
SCS package: SCS GGSNS5.0.2_SCS5.0_14

GGSN: GGSNS5.0.1-isos-build-17
Note: The GGSNS5.0.1-isos-build-17 release is referred to as GGSN5.0.1 and the SCS

GGSNS5.0.2_SCS5.0_14 release is referred to as SCS5.0.2 for the remainder of the
document. The combined GGSN5.0.1 and SCS5.0.2 solution may be generically referred
to as GGSN5.0.1 in some instances.

11
2 Supported External Servers/Releases

This section lists the external servers used in the testing of the GGSN5.0.1 release and
their associated versions:
Software type Name Version

CGF NM5.01
PS5.4
MetaSolv Radius 5.0 SPE
DHCP 5.4 SPE
CMG WSB v3.3
WAP
Openwave 5.0.1
GGSN 5.0.1
Prepaid Service Builder

WIR 6.1
Performance Server V5.0
OA&M
Main Server V5.0
Legal Intercept Verint

Rel 5a
Wireless Village IM Followap

Rel v 3.0.35
Content Filtering Websense
V6.1

12
3 Supported Software Upgrade Paths

This section lists the supported upgrade paths of the GGSN5.0.1 release.
The supported upgrade paths for the SCS Server are as follows:
UPGRADING FROM: UPGRADING TO:

Release Build Release Build
SCS4.0.1 SCS GGSNS4.0.1_SCS4.0.1(4) SCS5.0.2 SCS GGSNS5.0.2_SCS5.0_14
SCS4.1 SCS GGSNS4.1_SCS5.0(89)
SCS4.1.2 SCS GGSNS4.1.2_SCS5.0(1)
SCS5.0.1 SCS GGSNS5.0.1_SCS5.0(6)
The supported upgrade paths for the GGSN are as follows:
UPGRADING FROM: UPGRADING TO:

Release Build Release Build
GGSN4.0.1 ggsns4.0.1-Dec12-4 GGSN5.0.1 GGSNS5.0.1-isos-build-17
GGSN4.1 ggsns4.1-isos-build-103
GGSN4.1.1 ggsns4.1.1-isos-build-9
GGSN5.0 ggsns5.0a-isos-build-46

13
4 New Features and Enhanced Features
4.1 GGSN5.0 New Features
This section describes the new features in the Nortel GGSN5.0 release. GGSN5.0.1 is a
maintenance release on top of GGSN5.0 and thus it also includes these features. For
more details on the features, refer to 411-5221-200 “Nortel GGSN and SCS What’s
New”.
PMID/Act ID Title
12205
MPLS RSVP-TE
24599
SSC3 Introduction
26431
3GPP Standards Conformance
26434
3GPP Rel 6 Dynamic Policy Control (Gx)
26513/ 28631/ 30020
3GPP Rel 6 Diameter Credit Control (Gy)
26932
Single APN Selectable Address Pools
27492
User Location Information
27566
Content Filtering
28687
GGSN5.0 Capacity Enhancements
28849
Availability Improvements
29332
GGSN5.0 Nodal Upgrade
29351
Parking Meter Time Event Charging
29420
IMS Interworking
29661
Configurable GGSN Source IP Address Selection
29766
Electronic Software Delivery
29937
Counters Enhancements
29946
Configurable Interim RADIUS Messages
29957
CBB HTTP Message Types
29998
Remote Upgrades
30077
SGSN Grouping

14
PMID/Act ID Title
30409
IP Services Support for IP-IP (Mobile IP)
30508
Distributed RADIUS AAA Optimization
32178
Radio Access Type Mapping
32179
CBB Blacklist
32001
Support for more CORBA CLI commands

15
4.2 Feature Patches Sourced in GGSN5.0.1
The following feature patches from previous releases are sourced in GGSN5.0.1 load.
Patch ID Title
G411_01275287ACT_QCTCMC and
CBB Usage Time Accounting (Removal of trailing QCT Timeout Period).
G411_01275287ACT_QCTSSP
G411_01339974AACT_GTPACCT Enhancement of SGSN Change Partial Billing
G411_01222356ACT_CTP Enhanced CTP Connection Management
G401_01264512ACT_SUBMGR Support of DHCP Relay Agent address field for VLAN VPN type
Q01275287 CBB Usage Time Accounting (Removal of trailing QCT Timeout

Period)
Description This feature removes the Quota Consumption Time (QCT) timeout
period from an envelope’s reported usage time. The QCT timeout
period continues to be used to determine the start/end of an
envelope. A checkbox is added on the SCS to enable/disable QCT
Removal on APN Accounting and Diameter Credit Control.
Limitation of the QCT Removal exists when 2 TOD boundaries are
crossed before a CCR (U) is sent after authorization, usage time
reported in CCR (T) will not be correct as documented in the FRS.
Q01339974 Enhancement of SGSN Change Partial Billing

Description If the "SGSN Change Partial Billing" option in the APN is selected,
a partial billing record is generated every time a SGSN address
change happens. If this option is not selected, the partial billing
record is generated when there are three SGSN address changes,
i.e., the number of SGSN addresses in the list reaches four. This
enhancement modifies this behavior. If the "SGSN Change Partial
Billing" option is not selected, an SGSN address change will never
generate a partial billing record, but the PDP context is updated
with the new SGSN address. A new checkbox "Max SGSN
Change Partial Billing” is added to the APN. Default value is
checked. If "SGSN Change Partial Billing" is checked, "Max
SGSN Change Partial Billing” will be grayed out. The "SGSN
Change Partial Billing" and "Max SGSN Change Partial Billing"
checkboxes apply only to SGSN changes where the previous and
new SGSN use the same version of GTP
Q01222356 Enhanced CTP Connection Management

16
Description This feature includes a deterministic way of identifying the active

SCP server. The first server configured in a given tariff profile is
designated as the primary server and the second one as secondary.
Active server determination is based on which server goes to
established state first and which server is configured to be primary.
The primary server has priority in becoming the active server. The
secondary server can become the active server only if the primary
server is not in established state. All CTP GPRS Service Requests
are sent to the active server.
Q01264512 Support of DHCP Relay Agent Address (AKA giaddr) Field for
VLAN VPN Type
Description This feature extends support for configuring the DHCP Relay
Agent address (AKA giaddr) field in the DHCP DISCOVERY and
DHCP REQUEST to also include the VLAN VPN type. The
current giaddr implementation allows the giaddr field to be
configured for the GRE VPN and Wireless ISP access models only.
This field allows certain DHCP servers receiving these messages
to allocate an IP address from same address pool as that which
contains the giaddr IP address.
Note: the DHCP Relay Agent address is configured in the DHCP
Profile so there are no SCS changes required.

17
4.3 Description of Enhancements in GGSN5.0.1
PMID/CR Title
Q01415218 Patch Management Enhancements on the SCS 5.0.2.
Q01415218 Patch Management Enhancements on the SCS 5.0.2

Description This feature makes the SCS 5.0.2 release aware of patch packages.
Starting with GGSN 5.0.1 patches, when Accepting/Deleting
patches (as well as adding/deleting patch rules to/from a patch
profile) the SCS will allow the user to auto-select patches that
belong to a patch package using a single click. This allows for
more convenient operations of patch acceptance and profile
creation. Please refer to the Nortel GGSN Provisioning Procedures
(NTP 411-5221-927), Appendix B “GGSN Patch Application” for
details. Please see the known issues under CR Q01415218 to see
the limitations of this feature.

18
4.4 Feature Patches Sourced in GGSN5.0
The following feature patches were produced in previous releases but have been sourced
in GGSN5.0 load. GGSN5.0.1 is a maintenance release on top of GGSN5.0 and thus it
also includes these feature patches.
Patch ID Title
G401_01086721ACT_PPP Secure PAP/CHAP L2TP negotiation requirement
G411_01155666ACT_GTP Prevention of Over Consumption for Real-time Charging.
G401_01171008ACT_GTP Disallow RADIUS INTERIM Messages

19
5 Issues Fixed/Corrected
5.1 Patches Sourced in GGSN5.0.1
The following patches have been sourced into GGSN5.0.1 load. All applicable Patch Ids
in prior releases are listed for convenience.
Case No.
Item Patch Id Title
CR No.
060404-96699/
1. G50_01362714_DCC Trap When Modifying DCC Tx Event Interval Timer
Q01362714
G41_01367368_TF 060503-26914
2. G411_01367368_TF 060503-27077/ CBB Policy with 256 URLs cause SSM Reset
G50_01367368_TF Q01367368
060518-44142
060518-44623
060518-44630
G411_01375654_SCP 060424-16736
3. SCP Task Suspension Due to Memory Access Error
G50_01375654_SCP 060424-17353
060510-34420
060510-35163/
Q01375654
060207-34367
060421-15294
060222-50389
060222-50386
060222-50431
060222-50521
G401_01355039_PPP 060222-50440
4. G411_01355039_PPP 060222-50435 SSP resets when GTP PPP proxy session is released
G50_01355039_PPP 060222-50433
060222-50539
060321-80598
060412-05416
060717-06951
060503-26917/
Q01355039
060526-54062
G411_01391931EMG_SUB 060627-87178
5. CMC Switchover Caused by GTP Task Stack Overflow
G50_01391931EMG_SUB 060627-87202/
Q01391931
060502-26220/
6. G50_01365576_ISN Static Routes Lost After CMC Switchover
Q01365576
060519-46139/ Certain CGF Profile Attributes Lost After CMC
7. G50_01378284_ISPMGR
Q01378284 Switchover
060502-26228/
8. G50_01365577_ISN SCS Trap Ports Reset to Default Values
Q01365577
060622-81950/
9. G50_01407739ACT_GTP Radius PAP Authentication Optional Functionality
Q01407739
060302-60438/ Robustness Enhancement When Sending Diameter
10. G50_01351011_DCC
Q01351011 Message
060614-72251
G411_01407019_DHCP 060627-86393
11. Some of DHCP Profiles Not Completely Loaded
G50_01407019_DHCP 060628-88411/
Q01407019

20
Case No.
Item Patch Id Title
CR No.
G411_01222356ACT_CTP
12. Q01222356 Enhanced CTP Connection Management
G50_01222356ACT_CTP
G41_01230242ACT_NETINET
051003-08010/
13. G411_01230242ACT_NETINET Large TCP Packets Are Fragmented
Q01230242
G50_01230242ACT_NETINET
G411_01241519ACT_GTP 051003-07995/
14. GGSN delays prepaid reauth requests by 500ms.
G50_01241519ACT_GTP Q01241519
G401_01264512ACT_SUBMGR Support of DHCP Relay Agent address for VLAN VPN
15. Q01264512
G50_01264512ACT_SUBMGR access model
16. G50_01267600_CF Q01267600 Content Filter Protocol Error During Concatenated WAP
G401_01271233_GTPP
G411_01271233_GTPP 051121-60377/
17. GTP Accounting Task Died Without Trace
G41_01271233_GTPP Q01271233
G50_01271233A_GTPP
G411_01275287ACT_QCTCMC/ CBB Usage Time Accounting (Removal of QCT
18. Q01275287
G411_01275287ACT_QCTSSP Timeout Period)
G50_01276610_IFMGR 051122-61341/ Not Able to Telnet Into GGSN On High "VXWORKS
19.
G411_01276610_IFMGR Q01276610 SYSTEM HEAP" Usage
G401_01279141_GTP
G41_01279141_GTP 051216-86298/
20. SSP Load Balance of Contexts Fails
G411_01279141_GTP Q01279141
G50_01279141_GTP
G41_01279218_DCC
051215-85044/
21. G401_01279218_DCC GGSN Doesn’t Apply the Correct Rule base
Q01279218
G411_01279218_DCC
051218-87338
G411_01279296_SUBMGR
22. 051218-87345/ CMC Switches Over Due to a Race Condition
G50_01279296_SUBMGR
Q01279296
G41_01279695_TF 051214-83588
23. G411_01279695_TF 051123-62855/ Incorrect billing of secure WAP1.2 traffic
G50_01279695_TF Q01279695
24. G50_01279806_GTP Q01279806 Radius Start And Stop Message Handling Corrections
G41_01286030_CLI
060103-96704
G401_01286030_CLI
25. 060131-26248/ GGSN is Not Adding APNs After a CMC Switchover
G411_01286030_CLI
Q01286030
G50_01286030_CLI
060601-58707
060113-07874
G401_01286969_GTP 060606-63211
SSP Core Dump Caused by Deleted Secondary PDP
26. G411_01286969_GTP 050906-77451
Context
G50_01286969_GTP 060207-33522
060222-50441/
Q01286969
G411_01293301_GTPCMC
G411_01293301_GTPSSP
G41_01293301_GTPCMC 051113-51687/
27. QHT Not Triggered After RAR Message
G41_01293301_GTPSSP Q01293301
G50_01293301_GTPCMC
G50_01293301_GTPSSP
G401_01296948EMG_SVC
G41_01296948EMG_SVC 060126-22338/
28. Flowcache Values Not Read After Reboot
G411_01296948EMG_SVC Q01296948
G50_01296948EMG_SVC
G401_01300526_GTP
060103-96953
G41_01300526_GTP
29. 060104-98715/ High Percentage of MMS Activation Discarded
G411_01300526_GTP
Q01300526
G50_01300526_GTP
G411_01303739EMG_ISPMGR 060131-25818/
30. Duplicate Entries In The Config Database
G50_01303739_ISPMGR Q01303739

21
Case No.
Item Patch Id Title
CR No.
G401_01311464_SVC
G41_01311464_SVC
31. Q01311464 Flowcache Display Error for Aggregate Sessions
G411_01311464_SVC
G50_01311464_SVC
G41_01319247_DCC
060223-52408/
32. G411_01319247_DCC Used-Service-Unit AVP Not Sent in CCR(F)
Q01319247
G50_01319247_DCC
G411_01319954A_HTTP 060111-05337/ CBB Under Rates Packets Retransmitted After FIN
33.
G50_01319954_TF Q01319954 Packet
G41_01323841_GTP
060201-27499/
34. G411_01323841_GTP Incorrect Coupon Volume Usage during DCC/CTP Calls
Q01323841
G50_01323841_GTP
060615-74124
G41_01335786_SCP 060205-31963
35. G411_01335786_SCP 060711-99985 SCP Connection Loss
G50_01335786_SCP 060222-50684/
Q01335786
060309-67531/
36. G411_01336395A_VPN OVLD condition on 13/1/2
Q01336395
060411-03912
G411_01339974AACT_GTPACCT
37. 060220-47796/ Enhancement of SGSN Change Partial Billing
G50_01339974ACT_GTPACCT
Q01339974
060321-81419/
38. G50_01343906_GTP Unacceptable Delivery of Erroneous SDU field of QoS
Q01343906
060309-67534
GGSN System Failure messages under 20 PDP
39. G411_01318950ACT_AAA 060111-06134/
request/sec load
Q01318950
G411_01227794AACT_SVC 060623-83134
40. G411_01227794BACT_SVC 050812-53738/ Some Dropped Packets Are Counted For Billing
G50_01227794ACT_SVC Q01227794
G41_01292925_TF
G411_01292925ACT_TF 051115-54191/ Fragmented WAP Packets Using Prepaid are Billed
41.
G411_01292925AACT_TF Q01292925 Incorrectly
G50_01292925_TF
Pipelined WAP Packets Using Prepaid are Billed
42. G41_01312654_TF Q01312654
Incorrectly
060217-45967/ Data Loss Due To MPLS MTU Restriction on GELC
43. G411_01319256ACT_ELCMGR
Q01319256 Card
060330-92032/
44. G50_01343947_DCC Incorrect G-CDR marking time stamp for DCC
Q01343947
G41_01351019EMG_PATCHER 060330-91382
45. G411_01351019EMG_PATCHER 060321-80711/ GGSN Patcher Traps on a Patch Profile Swap
G50_01351019EMG_PATCHER Q01351019
G411_01343948_DCC 060330-92070/
46. Wrong DCC handling with CCNA
G50_01343948_DCC Q01343948
G411_01356951_GTP 060321-80515/ Missing Tariff Change Usage Coupon After a ToD
47.
G50_01356951_GTP Q01356951 Event
Partial Billing updates with maximum CBB containers
48. G411_01346716ACT_GTPACCT Q01346716
for QCT
49.
G411_01389183_SVC 060512-37363/ SSP Traps Due to Uninitialized fields in New
50.
G50_01389183_SVC Q01389183 Conversation
G411_01378314ACT_PAR 060503-26719/
51. DIR Command Causes Overload.
G50_01378314ACT_PAR Q01378314
52. G50_01369200_AAA Q01369200 Radius Accounting Fails During Catchup

22
Case No.
Item Patch Id Title
CR No.
060522-47493
060526-53528
060817-47010
060907-69691
G411_01394307_SVC
53. 060710-98378 SSM Resets Under Certain Flow Migration Conditions
G50_01394307_SVC
060925-89764
060929-95587
060929-95863/
Q01394307
060518-44670
060518-44952
060807-30334
G411_01405498_CARDMGR Aux. Ethernet Management port on Standby CMC Down
54. 060323-84316
G50_01405498_CARDMGR After CMC Switch
060628-87725
060629-88913/
Q01405498
060614-73130
G411_01408229_SVC
060714-04504
55. G411_01408229A_SVC Retransmitted Packets Dropped
060510-34073/
G50_ 01408229_SVC
Q01408229
060705-93889/
56. G50_01424740EMG_GTP Correction of "CMC3 Unaligned Addr" Exceptions
Q01424740
060705-93889/
57. G50_01423912EMG_ISR Address Misalignment Could Lead to Card Reset
Q01423912
G411_01404173A_NTP 060524-50668/ NTP Synchronization Fails When Using Multicast Mode
58.
G50_01404173_NTP Q01404173 On CMC3
G411_01435989_GTP 060719-09790/ GGSN Reports Wrong Volume and Time Usages for
59.
G50_01435989_GTP Q01435989 Prepaid Subscribers
060627-86630/
60. G50_01436735_AAA Radius Accounting Records Not Always Written to Disk
Q01436735
060727-19072/
61. G50_01439788_ELCMGR SFC Switchover Causes Core Dump on CMC
Q01439788
060719-10022
061101-31138
G411_01487158EMG_GTP SSM Core Dump During GTP Tunnel Fall Forward
62. 061106-36179
G50_01487158EMG_GTP Procedure
061109-40711/
Q01487158
G411_01096501EMG_HDISK
050921-94252
G411_01096501EMG_PREREQ
63. 050302-72588/ Stateful Polling Of CMC3 Disk Drive Registers
G50_01096501EMG_HDISK
Q01096501
G50_01096501EMG_PREREQ
060728-20472/ Acct-Session-Id Not Included in RADIUS Accounting
64. G50_01441844_AAA
Q01441844 On/Off Messages
051121-59569
Debug Breakdown Counters for SYSFAIL.Other
65. G411_01270521_GTP 060828-58213/
Counter
Q01270521

23
5.2 Issues Fixed in GGSN5.0.1 and SCS5.0.2
The following issues are fixed in GGSN5.0.1 and SCS5.0.2 release. Following table
excludes the patches sourced in GGSN5.0.1 load listed in above table.
Case No.
Item Title
CR No.
041104-48917/
1 SSC Card Problem
Q01171194
060220-48715/
2 Problem with Device Monitoring VPN on SCS Client
Q01316540
050815-55023/
3 Crash In OSPF-VPRN Due to RPC Timeout from VPN to OSPF-VPRN
Q01206858
060323-84669
4 060324-84959/ Stack Trace Occurred When Sending Bad ESP Packets to GGSN
Q01214141
050729-38917
5 050629-07088/ Support of MAC Multicast Manual Entry in ARP Table
Q01252955
6 Q01258932 “show stats bcm5631” Displays Negative Values
Q01293128 HD 'busy bit' Issue Causes Faulty CMC switchover/
7
Q01293140 HD 'busy bit' Issue Results in Invalid Reload Message
051221-90542/
8 Passive FTP with Proxy
Q01306294
060209-37392/
9 CORBA Error Message Missing During Implementation of CBB/FW rules
Q01310691
060210-39281/
10 Online Help Incorrect for Session and Idle Timeout
Q01314287
060215-44273/
11 TEID of 0 being Rejected After SGSN Restart
Q01315453
060214-42404/
12 GGSN CLI Display "show gtp session" for MNC is Wrong
Q01316163
051017-21505/
13 Changes Needed For Critical Event Display on Disk Failure
Q01320813
050301-71469/
14 Ethernet Card Driver has an Etherleak Weakness
Q01340595
060119-14495/
15 Radius Provided Idle Timer Ignored by GGSN
Q01345443
060516-40553
16 060209-37618/ CMC3 Ethernet Port Is Down w/ Router 100Mb/s Full-Duplex
Q01375871
060517-41837/
17 Unexpected Behavior with SYSLOG Settings
Q01383822
060502-25430/
18 DCCA Debug Not Correct
Q01392230
060615-73705/
19 SCS Changes for “add prefix-list” CLI Command Missing
Q01402367
041208-85884/
20 Quickstart Validates Incorrect Slot Number
Q01189321
060828-58213
21 051121-59569/ Health Monitor Log Pegging SM.FailActPdpCtxt.SYSF.Other
Q01270521
060112-06779/
22 Taking Main OSPF Routing Process Off Causes Access Subscriber OSPF Off
Q01298251
060310-69107/
23 “Loaded VPN Not Found” Session Error Found
Q01340685

24
Case No.
Item Title
CR No.
060328-89402/
24 SSM Stuck in "need catchup" State While Recovering from a Crash.
Q01346890
060105-99643
060721-12698
25 Trace_tool Does Not Show RADIUS Messages
060913-77030/
Q01350922
060402-94154/
26 Time Stamp One Hour Behind.
Q01355036
060315-74796/
27 Counter for GTP Data Not Reported After SSM Crashes.
Q01368610
051207-75921/
28 'close gtp session' Does Not Close the Hung Session
Q01394343
060608-65955/
29 Gtpmgr Traps on Session Setup Due to NULL Pointer
Q01416171
060725-15601/
30 "close gtp session msisdn -force" Does Not Close the Hung Session
Q01449916
31 Q01455504 Uplink is Blocked When MSCC FUI Action Set to Redirect

25
5.3 Patches Sourced in GGSN5.0
Following patches are sourced into GGSN5.0 load. GGSN5.0.1 is a maintenance release
on top of GGSN5.0 and thus it also includes all the following patches.
Case No.
Item Patch Id Title
CR No.
G401_01112269_EMSCLIENT
1 G411_01112269_EMSCLIENT Q01112269 SCS Monitor Port Hung After SCS Upgrade
G41_01112269_EMSCLIENT
041029-42029
G401_01041640ACT_GTP Optionally Record Missed N3 Echo Response Logs in
2 050128-36907/
G411_01041640ACT_GTP Event Logs
Q01041640
G401_01088756_TF 050131-38682/
3 Service redirect accumulated fixes
G411_01088756_TF Q01088756
G401_01166315_IFMGR
050613-86914/ Generate GARP message on auxiliary Ethernet
4 G411_01166315_IFMGR
Q01166315 management
G41_01166315_IFMGR
G401_01225761_IFMGR
050809-49250/ Command “show ipsec interface” displays extra loop-
5 G411_01225761_IFMGR
Q01225761 back interfaces
G41_01225761_IFMGR
G401_01229182_DCC
050927-01226/
6 G411_01229182_DCC Diameter Connection Loss
Q01229182
G41_01229182_DCC
SSM fails due to wrong HTTP stream processor
7 G401_01244947A_TF Q01244947
assignment
G401_01252109_GTP
051024-30385/ Flow-label not always set in GTP V0 create/update
8 G411_01252109_GTP
Q01252109 response header
G41_01252109_GTP
050310-82427/
9 G401_01100242_GTP Diameter – PDP Context delete response.
Q01100242
050908-80817/
10 G401_Q01254961_SVC NULL pointer access issues
Q01254961
050328-00822
050407-13303
G401_01113502_TF SSM resets when a web anonymized URL address is
11 050413-19868
G41_01113502_TF passed in for a CBB policy
050516-55855/
Q01113502
G401_01140415_GTP
050307-77885/
12 G411_01140415_GTP IFMGR connection list corruption
Q01140415
G41_01140415_GTP
G411_01119420_DCC
13 Q01119420 CCR(T) not sent upon invalid CCA
G41_01119420A_DCC
G411_01119420_GTP
G41_01119420A_GTP
050629-06643/ Deliver packets received with a mismatched source IP
15 G41_01170977_SERVICES
Q01170977 address
16 G41_01171715_GTPP Q01171715 GGSN call failures due to CPU overload
G411_01231336_RPC 050930-06006/
17 User Data Plane loss after SSM failure
G41_01231336_RPC Q01231336
G411_01238107_OS
18 Q01238107 Cardmgr task creating invalid task delays
G41_01238107_OS
G411_01245233_ISPMGR 051101-38486/ Session Error when Trunk Interface is Added with
19
G41_01245233_ISPMGR Q01245233 Existing IP
20 G41_01257024_GTP Q01257024 CCR Final missing Rulebase-Id AVP

26
Case No.
Item Patch Id Title
CR No.
G401_01057942AACT_GTP
041213-90631/
21 G411_01057942ACT_GTP Disable CTP V1/V2 re-auth Message After GTP Update
Q01057942
G41_01057942ACT_GTP
G401_01075604_PSPMGR
040929-06407/
22 G411_01075604_GTP GGSN sends an Error Indication to SSGN
Q01075604
G41_01075604_GTP
G401_01118413_SSH 050225-68469/ CLI 'show log command' does not include SSH user
23
G411_01118413_SSH Q01118413 information.
G401_01124576_GTP
24 G411_01124576_GTP Q01124576 Sessions still active after Idle Timer expires.
G41_01124576_GTP
G401_01130138ACT_SUBMGR
050425-32309/ Cannot add Default Route to Access Subscriber
25 G411_01130138ACT_SUBMGR
Q01130138 Reachability
G41_01130138ACT_SUBMGR
G401_01141942_L2TP
050510-49512/
26 G411_01141942_L2TP LNS port change not recognized by GGSN LAC.
Q01141942
G41_01141942_L2TP
G401_01156698_DCC
050329-02535/
27 G411_01156698_DCC GGSN sends 2 MSCCs when ToD event occurs
Q01156698
G41_01156698_DCC
G411_01157893_TF
28 Q01157893 CBB under rates packets fragmented at IP layer.
G41_01157893_TF
G401_01158405EMG_GTP
050613-86771/
29 G411_01158405EMG_GTP GGSN AAA Manager memory leak
Q01158405
G41_01158405EMG_GTP
G401_01160744EMG_HTTP 050614-88968
CBB: Incorrect handling of multiple "HTTP/" in HTTP
30 G411_01160744EMG_HTTP 050905-77293/
response
G41_01160744EMG_HTTP Q01160744
G411_01165498_ISN 050624-01365/
31 Longer recovery time after a CMC switchover
G41_01165498_ISN Q01165498
G401_01178341_SVC
050627-02861/
32 G411_01178341_SVC GGSN SVC Manager memory leak
Q01178341
G41_01178341_SVC
G411_01183036_AAA Memory leak detected in GTP subsystem during soak
33 Q01183036
G41_01183036_AAA test
050818-59264
G401_01201191_GTP
050826-68563 GTP Response QoS element "Delivery of erroneous
34 G411_01201191_GTP
050921-94118/ SDU" incorrect.
G41_01201191_GTP
Q01201191
35 G411_01205797_VPN Q01205797 SSM Failure After Modifying VRF Profile
050908-81227
G411_01206947_CLOCK
36 050615-90022/ Incorrect time set on the GGSN
G41_01206947B_CLOCK
Q01206947
050901-74694
050901-74739
G401_01207989A_GTPACCT 050901-74766
Mismatched Duration with Open and Change Times in
37 G411_01207989AACT_ACCT 050902-75473
G-CDR
G41_01207989ACT_GTPACCT 050902-75510
050714-22256/
Q01207989
38 G411_01209134ACT_CTPCMC Q01209134 CTP zero Volume Auth Response.
39 G411_01209134ACT_CTPSSP Q01209134 CTP zero Volume Auth Response.
Volume based prepaid calls handled incorrectly with
40 G411_01209825_GTP Q01209825
QCT enabled
G401_01215447_GTPP
050726-34778/
41 G411_01215447_GTPP IPCMGR instance 76 memory leak
Q01215447
G41_01215447_GTPP

27
Case No.
Item Patch Id Title
CR No.
G411_01216017ACT_AAA 050921-94107/ DCC Server is Unresponsive After receipt of Service
42
G41_01216017ACT_AAA Q01216017 Profile
G411_01220788_TIMER SN Timer task failed as entry is not removed from the
43 Q01220788
G41_01220788_TIMER timer list.
G401_01222269_GTP 050819-61181/ Failed to generate partial G-CDRs when triggered by
44
G411_01222269_GTP Q01222269 TimeOfDay event
050928-01902/ Toggling "ignore DF bit" does not change MTU on
45 G411_01226041_VPN
Q01226041 VRF-VPN interface
G411_01226544_PSPMGR 050908-80411/ PDP Context rejected due to SSM stuck in "dumping
46
G41_01226544_PSPMGR Q01226544 core" status
G401_01228731EMG_HTTP
050927-01081/ SSM traps due to large number of "HTTP/" in a
47 G411_01228731EMG_HTTP
Q01228731 response packet
G41_01228731EMG_HTTP
G401_01229594_GTP
051005-09501/ GGSN send DCC CCR “Reauth’ and CCR QHT when it
48 G411_01229594_GTP
Q01229594 should not
G41_01229594A_GTP
050817-58016
050920-93400/
49 G411_01229609_GTP Incorrect billing in case of denied coupons.
Q01229609
Q01205868
050825-67082/
50 G411_01230812_IFMGR Line Card Programming Disabled for ALC Card
Q01230812
051007-12991/ Total Usage Report after Tariff Change Not Reported
51 G411_01234055_GTP
Q01234055 Correctly
050926-98964/
52 G411_01238332_BGP Failed to route MPLS VPN packets
Q01238332
051020-26944
G411_01241520_GTP
53 051020-26976/ Diameter Abort Message Led to CMC Switchover
G41_01241520_GTP
Q01241520
G411_01244237_DRIVER 051014-20335/
54 Management Port on Active CMC not accessible
G41_01244237_DRIVER Q01244237
051104-43022/ GGSN is not sending total time usage for a denied
55 G411_01250109_GTP
Q01250109 coupon.
051103-41530/ GGSN reporting wrong total time usage in the final
56 G411_01256686A_GTP
Q01256686 CCR
051117-57256
G411_01258511EMG_WAP
57 051123-63173/ WAP fragmented result SSP core dump
G41_01258511EMG_WAP
Q01258511
G401_01257941B_G50UPGRADE
58 Q01257941 Default ISP status down after upgrade
G411_01257941EMG_ISPMGR
59 G411_01098745_MPLS Q01098745 MPLS robustness patch
GGSN resync may result in an invalid connection to
60 G401_01207102_LI G411_01207102_LI Q01207102
ADMF
61 G411_01223788AACT_P2ROUTING * Q01223788 BGP capability not recognized by BGP peer
Incorrect handling of egress packets due to SSM
62 G411_01240398_TF G41_01240398_TF Q01240398
redundancy
G411_01267085_DCC No Rulebase-Id AVP sent in CCR(I) when no static
63 Q01267085
G41_01267085_DCC CBB is configured
060327-87915/
64 G411_01343676EMG_GTP Inaccurate CDRs are generated
Q0134676
060503-27145/
65 G411_01378249_GTP GGSN Handles Empty PAP Password Incorrectly
Q01378249
G411_01119420_DCC
G41_01119420A_DCC
G411_01119420_GTP
G41_01119420A_GTP

28
Case No.
Item Patch Id Title
CR No.
G41_01171008ACT_GTP
67 G401_01171008ACT_GTP Q01171008 Disallow RADIUS Interim Messages
G411_01171008ACT_GTP
* This patch is re-written to include two (2) additional message parameters that have not been sourced on time in
this release.

29
5.4 Issues Fixed in GGSN5.0 and SCS5.0.1
Following issues are fixed in GGSN5.0 release. GGSN5.0.1 is a maintenance release on

top of GGSN5.0 and thus it also includes all the following fixes. Following table
excludes the patches sourced in GGSN5.0 load listed in above table.
Case No.
Item Title
CR No.
041006-14445/
1 Not able to recover FELC Card 10 once its pulled out
Q01004653
050204-45527/
2 New commands should be described in the help menus
Q01077079
050203-43562/
3 L2TP Logic & Extended Lifetime Timer
Q01083852
050217-59657/
4 SSM 2 in slot 1 has missed poll 2 iterations.
Q01084380
050222-63027/
5 Mismatch with doc 411-5221-200: /etc/shasta/scs.conf is not backed up
Q01092730
050307-78913/
6 Show sgsntracker should give useful timestamps
Q01095367
050307-78905/
7 Process for populating image file MOTD w/copy image
Q01095385
050301-71975/
8 SCS accounting_time_interval modification
Q01097640
050310-82427/
9 Diameter – PDP Context delete response
Q01100242
050222-62944/
10 Log file not present in the backup to tape
Q01104429
050323-96952/
11 RADIUS Auth messages not captured by Trace_Tool for L2TP
Q01106127
050322-95532/
12 Diameter - Unknown-RuleBaseId-in-CCAInitial CCFH=continue
Q01106147
050303-74978/
13 VPRNLink stats not present in log monitor and inaccurate in the .acc file
Q01106161
050329-02064
050330-03691
14 050330-03860 Problems with stats after clock change to summertime
050331-05213/
Q01109663
050328-00822
050407-13303
15 050413-19868 SSM resets when a web anonymized URL address is passed in for a CBB policy
050516-55855/
Q01113502
041209-87023/
16 "WARNING, ALC slot 4 ICP 1 CAM 1 is FULL" log
Q01115006
050302-73775/
17 SCS mismatch timestamps
Q01119364
050417-24326/
18 CMC3 recovery time not reported in GGSN4.1Monitoring Guide
Q01121302
050414-22148/
19 HW and Install Document clarification needed
Q01121415
050321-93813/
20 IP routing table does not take over preferred BGP
Q01124968

30
Case No.
Item Title
CR No.
050427-35655/
21 Problems with RADIUS connection after resync
Q01126368
050427-35830/
22 GGSN responds to a DCC RAR from a different Server
Q01126382
050515-55517/
23 “show hist sm” output has wrong spelling for SM.NbrActCbbCtxt
Q01139502
050516-56988/
24 Entries are shown differently in SCS and “show hist” output
Q01139560
050307-77885/
25 IFMGR connection list corruption
Q01140415
050419-26586/
26 No warning occurs if an assigned network element is deleted
Q01142619
050126-33472/
27 FTB Duration field in G-CDR does not reflect record
Q01148817
050520-62972/
28 Single patch is downloaded to two directories on GGSN
Q01152063
050215-55943/
29 Idle timeout is not working to L2TP VPN
Q01154045
050418-24685
050804-44999
30 050411-17030 GGSN accounting CSV file start time is 1 second before the stop time
050714-22376/
Q01154106
050201-39273/
31 Interface responding to incorrect address
Q01169598
050607-80075/ With multiple profiles from RADIUS the call is rejected if the second profile contains upper
32
Q01170312 case letters
050708-15948/
33 “add arp” and “clear arp” behaving differently
Q01171066
050719-27126/
34 Cannot select correct SCS backup file for restore procedure
Q01179076
050714-22175/
35 GGSN out of sync after upgrade of SCS server
Q01182533
050728-38424/
36 Can not view security logs
Q01188024
050727-36208/
37 No status in monitor chassis for the management port in card 13.
Q01188508
050802-42139/
38 Service policies not supported on GGSN should be removed
Q01203290
050323-97002/
39 L2TP tunnel unusable when being deleted (LNS redundancy)
Q01203053
050901-74361/
40 Alarms in SCS GUI have incorrect severity and timestamp
Q01204634
050907-78707/
41 Session error in the SCS GUI after applying patches & resync
Q01209734
050809-49455/
42 Following an SCS rollback test, got an exception on the upgrade test
Q01209840
050824-65539/
43 Same MAC address on active/standby CMC mgmt-port
Q01213348

31
Case No.
Item Title
CR No.
050901-74694/
050901-74739/
050901-74766/
050902-75473/
050902-75510
44 G-CDR duration not the same as closing timestamp subtracted from opening timestamp
Q01213822/
Q01216002/
Q01216004/
Q01216010/
Q01216011
050902-75497/
45 GGSN erroneously reports billing data for hung GTP sessions
Q01214511
050906-78206/
46 Description for OAM SCP stats does not state for CTP-only
Q01216025
050922-95798
47 050926-99113/ Not possible to modify default-isp security policy
Q01222190
050915-88778/
48 BGP IOT Problem (Capability not recognized by BGP peer)
Q01223788
050926-99117/
49 Out of Sync because cpn list is linked to a firewall policy
Q01224118
050727-36301/
50 New accounting elements can not be displayed and added
Q01224315
050923-97694/
51 Problems when adding a new diameter profile
Q01226808
050920-92889/
52 SSM failure due to NULL flow
Q01228447
050912-83798
53 050912-83811/ Charging problems when a PDP context in use is reused
Q01231295
051006-11608/
54 No access rights to the tftpboot/patches to apply a patch
Q01241534
051020-26370/
55 Predictable TCP sequence numbering
Q01242166
051014-20711/
56 Documentation requires clarification on Charging Characteristics behavior
Q01248891
050928-02605/
57 GGSN does not close the PDP context when an CCA-Initial received with no MSCC AVP
Q01249313
051107-44767/
58 Wrong counters on APN_DATA_Stats
Q01250783
051020-26396/
59 Vulnerable LDAP directory
Q01258443
051102-40350/
60 Health check monitor procedure clarification
Q01258819
051109-47347/
61 ARP failure on Gi-interface
Q01261217
060202-29624/
62 SCSAdmin restore system script fails
Q01322881
060214-42611/
63 GGSN Event Diagnostic enabled after SCS upgrade
Q01319451
060307-65240/
64 Incorrect error displayed for RADIUS on SCS Client
Q01329834
060505-29642
060522-47469
65 Patches Get Stuck In A Loaded State
060822-51785/
Q01396921

32
Case No.
Item Title
CR No.
061026-25201
66 061122-55004/ SSP traps due to a NULL hostname in the HTTP request
Q01219437

33
6 Patches Provided with Load
6.1 Patch List

This section lists the current set of available patches in sequence with all dependencies
resolved.
In Table 1, the ordering of the GGSN5.0.1 patches in the table have pre-requisites
resolved. Pre-requisites are defined as patches that other patches require to be applied
first. Pre-requisites are documented in the Patch Description (PD) file associated with
each patch when there are dependencies.
The sequencing in Table 1 is not mandatory as long as the pre-requisites are satisfied.
Pre-requisites are summarized in Table 2 below for convenience.
Shaded patch rows indicate V status patches at the time of posting this version of this
document. Any other V status patches not included in Table 1 can be added to the end of
the profile.
Patches that are labeled “Commercially Restricted Feature” in the Nature of Patch
column have limited availability based on commercial arrangement. Please see the
warning in footnote number 1 at the end of Table 1. Detailed functional description
information on these features is available from Nortel Packet Core Product Line
Management to operators approved to use the functionality.
Table 1 provides the patch dependency list for a specific patch.

• M[list of patches] – Mutually Exclusive: A list of patches that cannot exist with
this patch in a patch profile.
• P[list of patches] – Prerequisite: A list of patches that are required before this
patch can be applied.
Table 1 also provides the disruptive nature of each patch:

• “Y” indicates that patch application or removal requires disruption to service on
the GGSN as specified in the patch PD file.
• “N” indicates that patch application or removal requires no disruption to service
on the GGSN.
• “?” indicates that disruption to service may be necessary for patch application or
removal. Assessment of the PD file contents and functionality in use are required
to make a determination of whether disruption to service is required.
• “O” indicates that disruption to service is optional for patch application or
removal. Assessment of the PD file contents and functionality in use are required
to make a choice.

34
Lastly, Table 1 indicates for each patch if special handling instructions are provided in
the Patch Description (PD) file. Please refer to Section 6.3 Patches Requiring Special
Handling for a summary of the special handling requirements for these patches.
Table 1: Patch Sequencing with Dependencies Resolved
Dependencies / Nature of Disruptive Special

Patch Id PKG Title CR Number
Prerequisites Patch Apply Remove Handling2
G501_01584892E L2TP Tunnels Bouncing
MG_PATCHMG EMG After Patch Profile Q01584892 Corrective N N Y
R Application
VLAN BGP VPN-bgp-
G501_01456493_
1 vprn task suspend on Q01456493 Corrective N N N
BGP
undebug bgp
Data packets were not
G501_01458665_
1 counted in GCDR Q01458665 Corrective N N N
GEN
container when no default
Set delete message N3/T3
G501_01339320 1/ Product
to 1/0 for slow SGSN Q01339320-06 N N N
ACT_GTP ACT Improvement
response
Customer SCP server
G501_01320881 1/
does not recognize the Q01320881-02 Corrective N N N
ACT_CTP ACT
CTP message.
G501_FF0132249 1/ Turn on In Seq. Handling
Q01322496-05 Corrective N N N
6ACT_INF ACT for CBB flows
CMC Switchover Due to
G501_01455385E
EMG Messaging Race Q01455385-03 Corrective N N N
MG_VPN
Condition Between Tasks
Cabcharge L2TP Commerciall
G501_FF0143578 1/
Authentication Feature Q01435785-01 y Restricted N N N
5ACT_INF ACT
Feature1
Confmgr Task
G501_01458672_
1 Suspension Due to Q01458672-01 Corrective N N N
CONFMGR
Memory Trampling
DCCv2 Customization - Commerciall
G501_FF0136803 1/
Essentials Feature Q01368038-03 y Restricted N N N
8ACT_INF ACT
Feature1
Wrong set of Rating
G501_01458800_
1 Groups reported in Q01458800 Corrective N N N
DCC
CCR(T)
Incorrect MSCC sent
G501_01461557_
1 when data sent after FUI Q01461557 Corrective N N N
DCC
Action TERMINATE.
G501_01223788 BGP capability not
1/
ACT_P2ROUTIN recognized by BGP peer Q01223788-08 Corrective N N ?
ACT
G
PDP Context Rejected
G501_01453702 1/
After Both LNS Servers Q01453702-02 Corrective Y Y N
ACT_L2TP ACT
Have Recovered
Service Redirect
G501_01465070_
1 downlink packets get Q01465070 Corrective N N N
SVC
rated at default rates
On switchover, GGSN
G501_01455575_
1 configuration is not Q01455575 Corrective N N N
RMC
loaded.
G501_01407873_ Invalid Start/Stop time in
1 Q01407873-02 Corrective N N N
STATS Overload stats

35

G501_01448864_ Bulk-Billing Buffer
1 Q01448864 Corrective N N N
GTP Overrun
GGSN Not Sending
G501_01471496_ RADIUS Access Request
AAA For Anonymous Auth
Call
G501_01471531_ Command to update
1 Q01471531 Corrective N Y N
CARDMGR SSC3 XFPGA firmware
Anonymous RADIUS
G501_01470153_
1 Auth option not working Q01470153 Corrective N N N
PPP
properly for PPP calls
G501_01472795_ SSM Reset Due To
SERVICES Corrupt WAP Packet
SSP resets when
G501_01477654
1 processing IP in IP Q01477654-01 Corrective Y Y N
GEN_SVC
encapsulated packets
G501_01425381 1/ Force Route
Q01425381-01 Corrective N N N
ACT_SPS ACT Advertisement for VPRN
CMC Switchover
G501_01303278_ occurred when LI
1 Q01303278-03 Corrective Y Y N
LI specific errors were
reported
No Coredump When
G501_01467399_
1 CMC Switchover Inside Q01467399-02 Corrective N N N
RMC
Interrupt Handler
"LI Only When
G501_01482527_
1 Roaming" Traces All Q01482527-02 Corrective N N N
LI
Targets
SFC Switch Does Not
G501_01476591_
1 Complete Without Q01476591-02 Corrective N N N
RMCMGR
Standby CMC
Incorrect G-CDR
G501_01341393
1 Duration and QoS Q01341393-10 Corrective Y Y Y
A_ACCT
Container ChangeTimes
After 2G/3G handover
G501_01463601_
1 the AVP RulebaseID is Q01463601 Corrective N N N
SUB
empty
G501_01447784 Some Packets Are Not
A_WAP Counted For Billing
G501_01220782_ CMC switchover caused
L2TP by suspended L2TP task
Parking Meter does not P[G501_0146155
G501_01456362_ handle time usage during 7_DCC
GTP reauths correctly G501_01341393
A_ACCT]
SUBMGR CLI
G501_01489025E
EMG commands can cause a Q01489025-02 Corrective N N N
MG_SUBMGR
CMC switchover
Incomplete Machine
G501_00958750_
1 Check Exception Q00958750-03 Corrective N N N
ISN
Information
Incorrect format of
G501_01475230_
1 CHAP password in IP Q01475230 Corrective N N N
AAA
call
SSM failure due to a
G501_01471454_
1 misconfigured CBB Q01471454-01 Corrective N N N
TF
policy

36

Synchronous RPC
G501_01461192_
1 deadlock in VPRN call Q01461192 Corrective N N N
VPN
model.
G501_01506406_ Time of Day Events P[G501_0145636
GTP Cause Inaccurate Billing. 2_GTP]
G501_01467598_ Wrong Byte Count For
SERVICES Tariff Switch CDR
Reduce TCP MSS to
G501_01448554_
1 optimize the operation of Q01448554-03 Corrective N N N
NETINET
CMC2 OAM port
No Coredump on CMC
G501_01497263_
1 Switchover if Active SFC Q01497263 Corrective N N N
SFC
is in Slot 8
Shasta hung/cored after
G501_01450817
1 adding AuxEth Mgmt(on Q01450817-04 Corrective N N N
A_IFMGR
ELC)
Parking Meter Charging Commerciall
G501_FF0138557 1/
Enhancement Feature Q01385579-02 y Restricted Y Y Y
9ACT_DCCCMC ACT
Feature1
Parking Meter Charging Commerciall
G501_FF0138557 1/ P[G501_0145636
Enhancement Feature Q01385579-02 y Restricted Y Y Y
9ACT_DCCSSP ACT 2_GTP]
Feature1
DCCv2 Envelope P[G501_0145880
Commerciall
G501_FF0138557 1/ Reporting Feature 0_DCC
Q01385577-02 y Restricted Y Y Y
7ACT_ERCMC ACT G501_01341393
Feature1
A_ACCT]
DCCv2 Envelope P[G501_0146155
Reporting Feature 7_DCC
G501_01456362_
Commerciall
G501_FF0138557 GTP
1 Q01385577-02 y Restricted Y Y Y
7_ERSSP5 G501_01341393
Feature1
A_ACCT
G501_01506406_
GTP]
Unexpected Partial G-
G501_01502203 1/ Product
CDRs Generated for Q01502203 N N N
ACT_GTPACCT ACT Improvement
Fallback/Fallforward
Invalid IP address for
G501_01505119 1/
SNTP Client Q01505119-01 Corrective N N Y
ACT_SNTP ACT
Configuration
Empty Rulebase ID AVP
G501_01502838_ P[G501_0146360
1 on DCC after an update Q01502838 Corrective N N N
SUB 1_SUB]
request.
L2TP Anonymous
G501_01520645_ Authentication With Null P[G501_0147015
PPP User Name Is 3_PPP]
Mishandled
GGSN Loses Sync with
G501_01532148_
1 SCS when Large Patch Q01532148 Corrective N N N
PATCHMGR
Profiles are Used
G501_01477576_ SSM Crashes Due To
SERVICES Incorrect Memory Access
Incorrect billing of
G501_01505992_
1 retransmitted fragmented Q01505992-01 Corrective N N N
TF
URLs
G501_01525283_ WAP2 redirect not
TF working

37

Inconsistent Byte Counts
G501_01531853_ P[G501_0145866
1 in CBB Extension and Q01531853 Corrective N N N
GTPACCT 5_GEN]
Traffic Volume Container
Call Setup Delay After
G501_01492892_
1 Processing RADIUS Q01492892-01 Corrective N N N
RPC
ACCESS ACCEPT
Support For Western
G501_01334913_
1 Australia Daylight Q01334913-07 Corrective Y Y Y
DST
Savings Time Rules
ADMF/DF connection
G501_01510180_
1 are not automatically Q01510180-02 Corrective N N Y
LI
restored
Some Null Radius
G501_01467417_
1 Attributes Fail Q01467417-02 Corrective N N N
GTP
Authentication
GTPBILL configuration
G501_01521498_
1 loss after manual CMC Q01521498 Corrective N N N
ISPMGR
switch
G501_01505394E Trap And Switchover
EMG Q01505394-01 Corrective N N N
MG_ACCT Freeing Billing Context
CMC Switchover Due to
G501_01522673E
EMG Invalid WRAP Reply Q01522673-01 Corrective N N N
MG_WRAP
Packet
G501_01570191E SSM Crashes Due To
EMG Q01570191-02 Corrective N N N
MG_SVC Poisoned Memory Access
SSM Traps & Usage after P[G501_FF01385
G501_01527169 update incorrect when 577_ERSSP]
EMG Q01527169 Corrective N N Y
AEMG_GTP Exclude QCT enabled M[G501_015271
69_GTP]
Incorrect Handling of
G501_01540209_
2 Denied Diameter Coupon Q01540209 Corrective N N N
DCC
rate
Adding Packet Spreading
G501_01525343_
2 Feature on the GELC Q01525343-01 Corrective ? ? N
XPIF
Card
PDP Context Rejected
G501_01457187 2/
Due To a Hung Session Q01457187-01 Corrective N N N
ACT_GTP ACT
On GGSN
Failure To Encode
G501_01498128_ MCC/MNC Values In
CTP SCP Messages For
CTPv1
The GGSN may Fail to
G501_01540483_
2 Respond to Create PDP Q01540483 Corrective N N N
GTP
Context Requests.
Dual Coupon Feature P[G501_FF01385
579ACT_DCCC Commerciall
G501_FF0136914 2/
Q01369144-01 MC y Restricted Y Y Y
4ACT_PPDCMC ACT
G501_FF0138557 Feature1
7ACT_ERCMC]
Wrong Reporting Reason
G501_01546309_
2 Sent After Parking Meter Q01546309 Corrective N N N
DCC
Quota Exhaustion.
Dual Coupon Feature P[G501_0145636
Commerciall
G501_FF0136914 2_GTP
2 Q01369144-01 y Restricted Y Y Y
4_PPDSSP G501_FF0138557
Feature1
7_ERSSP]

38

RADIUS Accounting
G501_01449995_
2 ON/OFF Message Sent Q01449995 Corrective N N N
AAA
Before BGP Peer Is Up
IP.OutDataPkt,
G501_01173295 2/
IP.IncDataOct and Q01173295-07 Corrective N N N
ACT_SVC ACT
IP.OutDataOct counters
G501_01481415_ Default route not set on
CONFIG Standby cmc
Wrong Byte Count For P[G501_0134139
Tariff Switch CDR 3A_ACCT]
G501_01467598_
2 Q01467598-05 M[G501_014675 Corrective N N Y
GTP
98ADBG_SERVI
CES]
G501_00789291_ SSC2 Card Fails To Boot
PSPMGR If SSC3 Card Active.
G501_01450778 2/ Increase the MTU Size of
Q01450778-01 Corrective O O O
ACT_IFMGR ACT Gn IP Interface on GELC
G501_01484327 Potential Call Processing
2/
AACT_NETINE Degradation Due To Q01484327-02 Corrective Y Y N
ACT
T Certain ARP Traffic
G501_01563238_ SSC card reset on flow
TF removal.
L2tpmgr Trap on CMC
G501_01540398_
2 During IP-L2TP Traffic Q01540398 Corrective N N N
L2TP
Run
Unexpected CDRs
G501_01485541_ Generated With
GTP Management Intervention
Cause
G501_01570531_ Critical alarm with "TLB
CONFMGR Load Exception"
Output of MSISDN/IMSI
G501_01573968_ P[G501_0146741
2 trace tool is missing some Q01573968 Corrective Y Y Y
TRMGR 3, 4 7_GTP]
information
Lower Network
G501_01565475_ Activation Rate Due to
GTP NoResp.FallBackFallFor
ward
G501_01571556_ Memory Leak during a
ISPMGR catchup scenario
Prerequisite For Patch
G501_01465128_
2 G501_01465128_POLM Q01465128-03 Corrective N N N
PREREQ
GR
RADIUS counter
G501_01544546_
2 RAD.AcctAvgRTT is not Q01544546-01 Corrective N N N
AAA
pegged.
Event Count not
G501_01564729_
2 Reported Correctly in Q01564729 Corrective N N N
GTPACCT
Billing
Autonomous Clean Up of
G501_01563634 2/ P[G501_0145718
GTP Sessions Stuck In Q01563634 Corrective N N N
ACT_GTP ACT 7ACT_GTP]
Disconnecting State
Historical Counters Are
G501_01579195_
2 Not Tracking Number Of Q01579195-01 Corrective N N N
AAA
Addresses In Blackout
CTP Server
G501_01566667_
2 Communication Remains Q01566667-01 Corrective N N N
SCP
in Connect Guard State

39

Show large policy may P[G501_0146512
G501_01522486_ cause CLI task stack 8_PREREQ]
POLMGR overflow M[G501_015224
86_WIND]
Incorrect Processing of
G501_01597060_ P[G501_FF01369
2 Re-Auth Response with Q01597060 Corrective Y N N
GTP 144_PPDSSP]
Multiple Coupons
Inconsistent Accounting P[G501_0134139
G501_01540279_ Session ID in L2TP and 3A_ACCT]
GTP RADIUS Messages M[G501_015368
49_PPP]
SSC3 Packets Drop on
G501_01568521_
2 bcm5631 (Port10 Buf Q01568521-02 Corrective N N Y
SSC3
Full Drops)
Radius PAP
G501_01407739 2/
Authentication Optional Q01407739-05 Corrective N N N
ACT_INF ACT
Functionality
G501_01571332_ Packets Dropped on the
2 Q01571332-02 Corrective N Y N
OS SSC3 Card
Enabling Lawful
G501_01466350 2/ Intercept to use VLAN Product
Q01466350-02 N N Y
ACT_LI ACT Connectivity to the Improvement
Network
PDP activation with
G501_01589010_
2 extended QoS values Q01589010 Corrective N N N
GTP
rejected by the GGSN
CMC Switchover Due To
G501_01658130E
EMG GTP Task Stack Q01658130 Corrective N N N
MG_GTP
Corruption
PCO IE Not Sent To
G501_01621446E
EMG Subscriber When Q01621446 Corrective N N N
MG_GTP
Invoking DHCP
Redundant RIP
G501_01640324 Instance Removed
EMG Q01640324 - Corrective N N N
EMG_ISN After GGSN Reboot Or
CMC Switchover
CMC Switchover Due
G501_01649169 Q01649169-
EMG to Suspended SCS - Corrective N N N
EMG_EMS 01
Monitor Task
VPRN Mesh Encrypted
G501_01034740 Q01034740-
3 Sessions Fail On SSC3 Corrective N N N
_SDK 03
Cards
GGSN drops packet
G501_01427052 Q01427052- P[G501_014650
3 following an out of Corrective N N N
_SVC 02 70_SVC]
sequence FIN
Scope & Policy
M[
G501_01571150 3/ Removal From The
Q01571150 G501_01571150 Corrective N N N
ACT_POLMGR ACT SSP May Cause
_POLMGR]
Service Degradation
Sub Commit Failure M[G501_01465
With Missing Service 128_POLMGR]
Policy Or Scope On
G501_01465128 SSM Q01465128- P[G501_014651
3 Corrective Y Y N
A_POLMGR 07 28_PREREQ
G501_01571150
ACT_POLMGR
]

40

G501_01508641 3/ GGSN Padding 'f' To
Q01508641 - Corrective N N N
ACT_DCC ACT IMSI In CCR Messages
CMC Reset and
G501_01510386 Switchover Due to Q01510386-
3 - Corrective N N N
_GTP Show GTP Session CLI 02
Command
IPSec Tunnel
G501_01574829 Modification Q01574829-
_IFMGR Impossible Because of 01
Session Errors
Reauth Response
G501_01579523 G501_FF01369
3 Handled Incorrectly If Q01579523 Corrective N N N
_GTP 144_PPDSSP
Parking Meter Is Active
SSM Trap Following
G501_01591035 DST Change Due To Q01591035-
3 Preventive ? ? Y
_GTP Absolute Lifetime 03
Triggers
PDP Context Deletion
G501_01592120 Q01592120- G501_01563634
3 Takes Too Long Under Corrective N N N
_GTP 01 ACT_GTP
Certain Error Condition
PDP Contexts Rejected
G501_01593019
3 After A Resync Due To Q01593019 - Corrective N N N
_GTP
A Large CBB Policy
GGSN Always Sends A
M[:
G501_01595094 3/ Password To RADIUS Q01595094-
G501_01595094 Corrective N N Y
AACT_AAA ACT Within Access 05
ACT_AAA]
Requests
Incorrect Values In M[:
Trace Tool Logs G501_01598374
G501_01598374 Q01598374-
3 _TRMGR] Corrective N N N
A_TRMGR 01
P[G501_015739
68_TRMGR]
3GPP Rel 6 Gy 3GPP TS
Diameter CC 32.299
G501_01614712 3/
Conformance Q01614712 - v6.7.0 N N O
ACT_DCC ACT
Conforman
ce
G501_01616587 Incorrect Statistic Q01616587-
_AAAMGR Duration Interval 01
G501_01622157 Potential SSP Invalid G501_FF01385
3 Q01622157 Preventive N N N
_GTP Data Access 577_ERSSP
Console Information
G501_01637622
3 Log 'spar_insert: bad Q01637622 - Corrective N N N
_DHCP
index'
PDP Context Fails To
G501_01639302 G501_01467598
3 Clean-up Under Certain Q01639302 Corrective N N Y
_GTP _GTP
Error Condition
No Information
G501_01639328 Provided in the Logs on
3 Q01639328 - Corrective N N N
_PSPMGR SSC3 Card or SSM
Reset
Dual Coupon Validity G501_FF01369
G501_01646145 Q01646145-
3 Timer 144ACT_PPDC Corrective N N N
A_PPDCMC 03
MC

41

Dual Coupon Validity M[:
Timer G501_Q016461
G501_01646145 Q01646145-
3 45_PPDSSP] Corrective O O O
A_PPDSSP 03
P[G501_FF0136
9144_PPDSSP]
Overwrite "Last Sent
G501_01649046 LCP Confreq" AVP G501_FF01435
_GTP with PAP for 785ACT_INF
Anonymous Auth
Consecutive Parking Commercia
G501_FF01510 3/ Meter Feature G501_01573968 lly
Q01510131 N N N
131ACT_CPM ACT _TRMGR Restricted
Feature1
First PM-series After M[:
Time Limit Trigger G501_01655676
G501_01655676 Begins One Second Q01655676- LTD_CPM]
3 Corrective N N N
_CPM Early 01 P[G501_FF0151
0131ACT_CPM
]
TCP MSS Clamping G501_01341393 Commercia
G501_FF01567
3/ A_ACCT lly
650ACT_IPCM Q01567650 O O O
ACT G501_01540279 Restricted
C
_GTP Feature1
TCP MSS Clamping Commercia
G501_FF01567 G501_01173295 lly
3 Q01567650 O O O
650_IPSSP ACT_SVC Restricted
Feature1
G501_01662594 3/ Allow VPN Uplink G501_FF01567
Q01662594 Corrective N N N
ACT_SVC ACT Multicast Passthrough 650_IPSSP
Trap Due To Nonzero
G501_01663833 Length NULL G501_01595094
3 Q01663833 N N N
_GTP Username RADIUS AACT_AAA
ACCESS Message
Duplicate IMSI/NSAPI
G501_01665758
3 Context Allowed to be Q01665758 - Corrective N N N
_GTP
Established
Cannot Establish BGP
G501_01672073
3 Peer When Using Q01672073 - Corrective N N N
_P2ROUTING
Extended Communities.
G501_01679901 Traffic Shaping Service
_SCHEDULER Corrections
Make Service Specific Commercia
G501_FF01385
G501_FF01643 Units Not Mandatory In lly
3 Q01643275 577ACT_ERC N N N
275_ERDCC VF DCC Envelope Restricted
MC
AVP Feature1
Incorrect User Name
G501_01648984 G501_01471496
EMG Length When Trim Q01648984 Corrective N N N
EMG_AAA _AAA
Option Is Enabled
CMC Switchover Due
G501_01730666 to Deletion of Traffic Q01730666-
EMG - Corrective N N N
EMG_EMS Profile with Long 01
Name
CMC Switchover Due P[G501_FF0136
To DCC Task Stack 9144ACT_PPD
G501_01693452 Corruption CMC
EMG Q01693452 Corrective N N N
EMG_DCC G501_FF01385
577ACT_ERC
MC]

42

Ensure Correct
G501_01084397 Q01084397-
4 Tracebacks on SSC3 - Corrective N N N
_ISN 01
are Generated
Failure To Bring the
G501_01296296 GELC/FELC In Service Q01296296-
_ELCMGR Following Manual 09
Reset
G501_01439788 SFC Switchover Causes Q01439788-
_ELCMGR CMC To Reset 05
Incorrect Time Usage
G501_01616522 Reported When Q01616522- P[G501_016461
4 Corrective N N N
_GTP Coupon Type Changes 01 45A_PPDSSP]
to PM
GCDRs Generated with P[G501_FF0138
Durations Larger Than 5577_ERSSP]
G501_01646131 Q01646131-
4 Maximum Allowed M[: Corrective N N N
_GTP 01
G501_01646131
LTD_GTP]
N3 Echo Response
G501_01653102 4/ Q01653102-
Message Event Logs - Corrective N N Y
ACT_GTP ACT 01
Always Enabled
Support For New P[G501_013349
Zealand Daylight 13_DST]
G501_01665444 Q01665444-
4 Savings Time Changes M[: Corrective N N N
A_NZDST 02
G501_01665444
_NZDST]
CMC Failure Due To
G501_01671291 Invalid CPU Free Q01671291-
_PSPMGR Memory Stats Reported 03
By SSP
G501_01678228 Unaligned Address P[G501_FF0156
_NETINET Warnings On SSC3 7650_IPSSP]
Tariff Switch For
G501_01685548 P[G501_014675
4 Prepaid Session Too Q01685548 Corrective N N N
_GTPACCT 98_GTP]
Early
L2TP Sessions Deleted P[G501_015022
G501_01692169
4 After IRAU Q01692169 03ACT_GTPAC Corrective N N N
_GTP
CT]
G501_01717665 Subscriber IP Address
_P2ROUTING Not Updated in FIB
False HCM Alarm Due
G501_01720452 to Incorrect Q01720452-
_GTP SM.FailActPdpCtxt.SY 01
SF.Other Peg
Incorrect Tariff Change
G501_01726458
4 Information For Q01726458 - Corrective N N Y
_PPDCMC
Prepaid
Incorrect Tariff Change P[
G501_01726458
4 Information For Q01726458 G501_01597060 Corrective N N Y
_PPDSSP
Prepaid _GTP]
Incorrect GCDR
P[
G501_01726913 Creation Due To
4 Q01726913 G501_01456362 Corrective N N N
_GTP Maximum Parking
_GTP]
Meters Reached
CMC Reset Due to
G501_01751739
4 "show elcmgr xpif" CLI Q01751739 - Corrective N N N
_ELCMGR
Command

43

Records Not
G501_01754747 Automatically Sent To
_AAA Recovered RADIUS
Server
GGSN Uses Wrong
G501_01758063
4 Diameter Termination Q01758063 - Corrective N N N
_GTP
Cause in CCR
Incorrect Timestamps
G501_01768103
4 for Local Address Pool Q01768103 - Corrective N N N
_AAA
Historical Statistic
SSM Trap Due to Data P[
G501_01772149
4 Access NULL Pointer Q01772149 G501_01564729 Corrective N N N
_GTPACCT
_GTPACCT]
G501_01777364 G-CDRs on CMC Disk
_GTPACCT Not Transferred to CGF
Incorrect DCC Tariff P[G501_FF0136
G501_01778204 4/ Time Change Report 9144ACT_PPD
Q01778204 Corrective N N Y
ACT_GTP ACT CMC]
SSM Missed Poll/Reset

G501_01783408 Due to Generated
4 Q01783408 - Corrective N N Y
_FLOWMGT Flows From P2P
Application
TCP MSS Config Not
P[G501_FF0156
G501_FF01727 Retained After
4 Q01727897 7650ACT_IPC Corrective N N Y
897_GTP Reboots, Resyncs and
MC]
CMC SOs
Switching The IP
G501_01647042
Address Allocation Q01647042-
EMG_P2ROUT EMG - Preventive N N N
Method Causes CMC 01
ING
Switchover
G501_01613913 SSM Reset Due To
Q01613913- P[G501_014727
EMG_SERVIC EMG Corrupt WAP Packet Corrective N N N
02 95_SERVICES]
ES
SSM Reset Due to
G501_01751095
EMG Incorrect Counter Q01751095 - Corrective N N N
EMG_L2TP
Handling in L2TP
Telnet to the GGSN
G501_01772089 P[G501_014674
EMG Fails With Possible Q01772089 Corrective N N N
EMG_PPP 17_GTP]
CMC Switchover
G501_01776053 Updating QoS profile
EMG_SUBMG EMG May Cause CMC Q01776053 - Corrective N N N
R Switchover
Primary Version DB M[: Y
G501_01743059
Not Saved To Disk Q01743059- G501_01743059 (Lab Test
AEMG_CONF EMG Corrective N N
Resulting in Out of 04 EMG_CONFM Instructio
MGR ns)
Sync GR]
EMG and Patch Package 5 patches
CMC Switchover M[:
Due To GTP Task G501_0145738
G501_01810161EMG_GT EM Stack Corruption Q0181016 7DBG_ACCT] Correctiv
N N N
P G 1 P[G501_FF013 e
85577ACT_ER
CMC]
CMC Switchover
G501_01809632EMG_SV EM Q0180963 Correctiv
Due to Memory - N N N
C G 2 e
Access Error

44

SSM Reset Due to
G501_01808187EMG_SV EM Access of Invalid Q0180818 P[G501_FF015 Correctiv
N N N
C G Subscriber 7 67650_IPSSP] e
Connection
L2TP Call With
G501_01792196EMG_GT EM RADIUS Accounting Q0179219 Preventiv
- N N N
P G May Cause NULL 6 e
Pointer Exception
Potential CMC
G501_01785485EMG_GT EM Switchover When Q0178548 Preventiv
- N N N
P G Closing DCC Prepaid 5 e
Calls
CMC Switchover
G501_01815222EMG_NE EM Q0181522 Preventiv
Due to Data Access - N N N
TINET G 2 e
Race Condition
CMC Switchover
G501_01694092EMG_GT EM Q0169409 Preventiv
Accessing Already - N N N
P G 2-01 e
Freed GTP Context
No Core Files Are
G501_01795346EMG_TA EM Q0179534 Correctiv
Generated After - N N Y
RPATCHER G 6 e
Processor Soft Reset
Potential SSM Reset
G501_01803858EMG_SE EM Q0180385 Correctiv
On CBB Policy - N N N
RVICES G 8 e
Modification
SSM Reset Due to P[-
G501_01839550EMG_GT EM Q0183955 Correctiv
Accessing Invalid G501_0172645 N N Y
P G 0 e
Data Context 8_PPDSSP]
CMC Target Patcher Q0187158
G501_01871586EMG_PA EM Correctiv
Task Becomes 6 - N N N
R G e
Unresponsive
G501_01818382_ISAKM IKE and IPSEC Q0181838 Correctiv
5 - N N N
P Tunnel Failures 2 e
Usage During Reauth
Q0172654 P[G501_016165 Correctiv
G501_01726540_PPDSSP 5 Not Considered As N N N
0 22_GTP] e
Before Coupon
The Order of Some P[G501_FF015
Q0179390 Correctiv
G501_01793902_GTP 5 PMs Is Reversed in 10131ACT_CP N N N
2 e
Record Extension M]
A Large Number of
G501_00950877_FLOW Q0095087 Preventiv
5 Flow Management - N N Y
MGT 7-05 e
Event Logs
Parking Meter Start
5/ M[:
G501_01728656ACT_GT Time Later Than Q0172865 Correctiv
AC G501_0172865 N N Y
PPCMC Close Time In 6-02 e
T 6ALTD_GTPP]
GCDR Container
Timestamp in M[:
Service Request G501_0176096
Earlier Than 5LTD_GTPCM
Absolute Coupon C]
Lifetime P[G501_014981
G501_01760965_GTPCM Q0176096 Correctiv
5 28_CTP Y Y Y
C 5-01 e
G501_0159103
5_GTP
G501_FF01369
144ACT_PPDC
MC]

45

SSM Reset During P[G501_017609
G501_01548395_GTPCM Q0154839 Correctiv
5 Time-of-Day Billing 65_GTPCMC] Y Y Y
C 5 e
Processing
Accounting Time M[:
Stamp Consistency G501_0145738
7DBG_ACCT
G501_0173313
4_ACCTCMC]
P[G501_015921
G501_01733134A_ACCT Q0173313 20_GTP Correctiv
5 Y Y Y
CMC 4 G501_0134139 e
3A_ACCT
G501_FF01567
650ACT_IPCM
C
G501_0181016
1EMG_GTP]
5/ Long Duration P[G501_017331
G501_01831139ACT_AC Q0183113
AC GCDRs After SSM 34A_ACCTCM N N Y
CTCMC 9
T Failures C]
VPRN Mesh
Encrypted Sessions Q0164915 Preventiv
G501_01649155_IPSEC 5 - N N N
Can Trigger Stack 5-01 e
Trace Event Logs
Unaligned Address Q0177383 P[G501_016782 Correctiv
G501_01773838_SVC 5 N N N
Warnings On SSC3 8 28_NETINET] e
SNMP Device Agent
G501_01812458_ISPMG IP Address Lost Over Q0181245 Correctiv
5 - N N N
R CMC Switchover and 8 e
Reload
GELC Fragmentation Y Y
M[:
Cache Enhancement (onl (onl
G501_0172786
for Gn y if y if
0LTD_XPIF] Y
Q0172786 Correctiv GEL GEL
G501_01727860_XPIF 5 P[G501_015253 (only if GELC
0-01 e C C
43_XPIF card exists)
card card
G501_0129629
exist exist
6_ELCMGR]
s) s)
Option To Add the M[:
CC-Total-Octets G501_0185084
5/ AVP to the Used- 3AAACT_DCC
G501_01850843ACT_DC Q0185084 Correctiv
AC Service-Unit AVP ] N N Y
C 3 e
T P[G501_FF013
69144ACT_PP
DCMC]
Support For Australia
Q0178843 P[G501_016654 Correctiv
G501_01788430_DST 5 Daylight Savings N N N
0 44A_NZDST] e
Time Changes
SSM Reset Due To Q0178718 Preventiv
G501_01787184_SVC 5 - N N N
Empty Flow List 4 e
Timestamp in M[:
Service Request G501_0176096
Earlier Than Q0176096 5LTD_GTPSSP Correctiv
G501_01760965_GTPSSP 5 Y Y Y
Absolute Coupon 5-01 ] e
Lifetime P[G501_016461
45A_PPDSSP]

46

Accounting Time P[G501_014675
Stamp Consistency 98_GTP
G501_0154027
9_GTP
G501_0163930
2_GTP
G501_0164613
G501_01733134_ACCTS Q0173313 1_GTP Correctiv
5 Y Y Y
SP 4 G501_0134139 e
3A_ACCT
G501_0176096
5_GTPSSP
G501_0152716
9AEMG_GTP
G501_FF01385
577_ERSSP]
First PM-series After P[G501_FF013
Time Limit Trigger Q0167046 85577_ERSSP Correctiv
G501_01670464_CPM 5 N N N
Begins One Second 4 G501_0165567 e
Early 6_CPM]
Parking Meter Start P[G501_014563
Time Later Than 62_GTP
G501_01728656_GTPPSS Close Time In Q0172865 G501_0167046 Correctiv
5 Y Y Y
P GCDR's Container 6-02 4_CPM e
G501_0173313
4_ACCTSSP]
SCS Region Server
G501_01801462_ELCMG Down While Resync Q0180146 Correctiv
5 - N N N
R Lead To Change 2 e
GELC Port Mode
SSM Reset During P[G501_017609
Time-of-Day Billing Q0154839 65_GTPSSP Correctiv
G501_01548395_GTPSSP 5 Y Y Y
Processing 5 G501_0173313 e
4_ACCTSSP]
Auto Re-auth Occurs
G501_017 P[G501_FF013
Following Coupon Correctiv
G501_01757795_GTP 5 57795_GT 69144_PPDSSP N N N
Switch from Non- e
P ]
QCT to QCT
Saving Primary
Config While
G501_01130502_POLMG Q0113050 Preventiv
5 Deleting Policies - N N N
R 2-01 e
Causes System
Restart
SSM Trap Due to P[G501_009508
Q0181126 Preventiv
G501_01811265_SVC 5 Access of NULL 77_FLOWMGT N N N
5 e
Flow Cache Pointer ]
Usage During Reauth P[G501_FF013
G501_01726540_PPDCM Q0172654 Correctiv
5 Not Considered As 69144ACT_PP N N N
C 0 e
Before Coupon DCMC]
Incorrect Envelope
Reported When Q0172640 P[G501_017265 Correctiv
G501_01726401_PPD 5 N N N
Switching From 1 40_PPDSSP] e
Non-QCT To QCT

47

Display Warning M[:
Service Package Not G501_0179876
Found In Event Log 7ACT_GTP]]
5/
G501_01798767AACT_G Q0179876 P[G501_017331 Correctiv
AC N N Y
TP 7 34A_ACCTCM e
T
C
G501_0154048
3_GTP]
5/ TEID Not
Q0179639 Correctiv
G501_01796399ACT_SIG AC Recognized In Pdp - N N Y
9 e
T Update Failures
5/ Long Duration
G501_01502203ACT_AC Q0150220 P[G501_017331 Correctiv
AC GCDRs for N N Y
CTSSP 3-06 34_ACCTSSP] e
T Fallback/Fallforward
Instance 84 Memory Q0152955 Correctiv
G501_01529555_OVLD 5 - N N ?
Leak in IPC Module 5 e
SSP1 Memory
Violation Errors Are Q0164916 Correctiv
G501_01649160_INF 5 - N N N
Not Printed To Event 0-01 e
Log
Incorrect Historical M[:
and "IDLE" HCM G501_0182678
G501_01826783A_STAT Statistics Q0182678 3_STATS] Correctiv
5 N N N
S 3-02 P[G501_016165 e
87_AAAMGR]
Long Duration
G501_01831139_ACCTS Q0183113 P[G501_017331 Correctiv
5 GCDRs After SSM N N Y
SP 9 34_ACCTSSP] e
Failures
Periodic Billing Not P[
Generating GCDRs G501_0183113
When Expected 9_ACCTSSP
G501_0154839
Q018550 Correctiv
G501_01855017_GTP 5 5_GTPSSP
e
N N Y
17-01 G501_0150220
3ACT_ACCTS
SP]

G501_01858692EMG_PP EM RADIUS Q0185869 - Corrective N N N
P G Authentication PPP 2
AVP Class Memory
Not Deallocated
G501_01865914EMG_A EM CMC3 Switchover Q0186591 - Corrective N N N

AA G w/wo SSC3 Reset 4-01
Due to RADIUS
Profile Modification
G501_01885754EMG_RP EM Active Call Q0188575 - Corrective N N N

C G Processing Stops for 4-01
Long Periods of
Time
G501_01898304EMG_GT EM CMC Switchover Q0189830 - Preventive N N N

P G During RADIUS 4
Authentication

48

G501_01794436EMG_GT EM CMC Switchover Q0179443 - Corrective N N N
P G Due to Accessing 6-01
Invalid GTP Context
G501_01899346EMG_GT EM CMC Switchover Q0189934 - Corrective N N N
P G Due To Accessing 6
Invalid Data Context
G501_01910948EMG_SV EM CMC Flowcache Q0191094 - Preventive N N N

C G Resources 8-01
Exhaustion
G501_01799972BEMG_D AC CMC Switchover Q0179997 M[501_017999 Preventive N N Y

CC T/ Due to Invalid 2 72EMG_DCC and
EM Message Size 501_01799972 Corrective
G AEMG_DCC]
P[G501_016934
52EMG_DCC]
G501_01910471EMG_IF EM CMC Switchover Q0191047 P[G501_FF015 Corrective N N N

MGR G Due To Incorrect 1 67650ACT_IPC
PPP GTP Connection MC]
Release
G501_01863562EMG_PO EM SSC3 Reset Due To Q0186356 - Corrective N N N

LMGR G CBB Policy Parse 3
Errors
G501_01877146EMG_SE EM SSM Reset Due To Q0187714 - Corrective N N N

RVICES G Long Flow Cache 6
Cleanup Time
G501_01088170_SSH 6 Secure Shell (SSH) Q0108817 - Preventive N N Y

Robustness 0-06
Improvements
G501_01531993_SVC 6 SSM Reset while Q0153199 - Corrective N N N

Taking Down A 3-02
VPN Subscriber
G501_01817401_GTP 6 Synchronous RPC Q0181740 P[G501_018311 Corrective N N N

Deadlock When 1 39ACT_ACCT
Moving Subscribers CMC]
G501_01845160_SVC 6 G-CDR CBB Q0184516 P[G501_FF015 Preventive N N N

Extension Records 0-02 67650_IPSSP]
On APNs Without
CBB Policy
G501_01885672_GTP 6 Stack Trace Due To Q0188567 - Corrective N N N

GTP Context Access 2
To Null Pointer
G501_01814048ACT_DC 6/ GGSN Encodes USU Q0181404 P[G501_018508 Conforman N N Y

CCMC AC AVP Non-Compliant 8 43ACT_DCC] ce
T with VF
Specification

49

G501_01623918_PATCH 6 CPU Overload Due Q0162391 - Corrective N N N
MGR to Patchmgr Task 8-01
Not Responding
G501_01892881_GTPCM 6 Periodic G-CDR Q0189288 P[G501_017331 Corrective Y Y Y

C May Be Generated 1-02 34A_ACCTCM
Early After ULI C]
Change
G501_01871689_DCC 6 DCC Messages Q0187168 M[G501_01871 Corrective N N N

Truncated Under 9-01 689LTD_DCC]
High Traffic P[G501_017999
72BEMG_DCC
]
G501_01858233_DCC 6 GGSN May Not Be Q0185823 M[G501_01858 Preventive N N N

Able to Establish 3-02 233DBG_DCC]
Connection to Its P[G501_018716
Diameter Peer 89_DCC]
G501_01900727_DCC 6 GGSN Fails to Q0190072 P[G501_018582 Corrective N N N

Establish Connection 7 33_DCC]
to Diameter Peer
G501_01300738_AAA 6 High CPU Utilization Q0130073 - Corrective N N N

When Writing 8-01
Radius Accounting
Files
G501_01866089_SCP 6 CTP Server Q0186608 - Corrective N N N

Connection Gets 9
Stuck in Connecting
State
G501_01898593_SERVIC 6 Deficiencies in Two Q0189859 - Corrective N N N

ES CLI Commands 3-01
G501_01902248_DCCCM 6 Unaligned Address Q0190224 P[G501_018582 Corrective N N N

C Warnings On CMC3 8-02 33_DCC]
G501_01874158_ISN 6 CMC Trap Due to Q0187415 - Corrective N N N

Closing Telnet 8-01
Session While in
VxWorks Shell
G501_01851188_DCC 6 GGSN Sends Q0185118 P[G501_015402 Corrective N N N

Terminate Request 8 09_DCC]
Session After
Receiving CCA
G501_01891689_GTP 6 GTP Data Q0189168 - Corrective N N N

OutErrIndMsg 9-01
Statistic Is Not
Displayed Correctly

50

G501_01892881_GTPSSP 6 Periodic G-CDR Q0189288 P[G501_018550 Corrective Y Y Y
May Be Generated 1-02 17_GTP]
Early After ULI
Change
G501_01860484_GTP 6 GGSN Does Not Q0186048 P[G501_017944 Corrective N N N

Take Down GTP 4-02 36EMG_GTP]
Session With a
Delete PDPC
Request
G501_01906302_AAA 6 Wrong VPN Local Q0190630 - Corrective N N N

Address In Radius 2
Messages After SSM
Reset
G501_01902248_DCCSS 6 Unaligned Address Q0190224 P[G501_017738 Corrective N N N

P Warnings On SSC3 8-02 38_SVC]
G501_01841263_ISPMG 6 GGSN Tries To Send Q0184126 - Corrective N N N

R Packets Through A 3-02
Disabled Interface
G501_01827380_IFMGR 6 GELC Fragmented Q0182738 - Corrective N N N
Hash Table Is Not 0-01
Updated When SSM
Is Disabled
G501_01814048_DCCSS 6 GGSN Encodes USU Q0181404 P[G501_016221 Conforman N N Y
P AVP Non-Compliant 8 57_GTP ce
with VF G501_0172640
Specification 1_PPD
G501_0175779
5_GTP]
G501_01904728EMG_GT EM CMC Switchover Q0190472 P[G501_018604 Corrective N N N
P G While Processing 8 84_GTP]
Error Indication
Message
G501_01877167EMG_IF EM CMC Switchover Q0187716 - Corrective N N N
MGR G While Deleting VPN 7
Subscriber
G501_01840578_LI 7 SSM Reset While Q0184057 P[G501_013032 Corrective N N N
Running Traffic With 8-02 78_LI,
Active LI Targets G501_0146635
0ACT_LI]
G501_01863890_LI 7 Potential LI CC Q0186389 P[G501_018405 Corrective N N Y
Packets Dropped 0-03 78_LI]
G501_01840579_MMC 7 Packet Loss In SFC Q0184057 P[G501_009508 Corrective N N N
During Heavy Traffic 9-01 77_FLOWMGT
With Large Packets ]
G501_01868228_OS 7 IP Packets Dropped Q0186822 P[G501_015713 Corrective N N N
Due to Exhaustion of 8-02 32_OS]
Receive Queue
G501_01948838_ELCMG 7 GELC Lockup Q0194883 - Preventive N N N
R Detection and 8-02
Recovery
G501_01912068_RMC 7 Management Port Q0191206 - Corrective N N ?
Settings Lost After 8
Resync

51

G501_01952553_IFMGR 7 Potential Packets Q0195255 - Corrective N N N
Dropped After CMC 3
Switchover
G501_01924305_GTPAC 7 GTP Accounting Q0192430 Preventive N N N
CT Task Hung When 5-01
Processing Regular
Billing Data
G501_01913874ACT_GT 7/ PDP Context Deleted Q0191387 P[G501_018928 Corrective N N Y
P AC Due To QoS 4-01 81_GTPCMC,
T MaxBitRate Set To G501_0158901
Zero 0_GTP,
G501_0162391
8_PATCHMGR
]
G501_01950186ACT_GT 7/ Increase MBR and Q0195018 - Corrective N N Y
P AC GBR for Downlink 6
T Data Throughput
G501_01559949_AAA 7 Clear RADIUS Q0155994 Corrective N N N
Profile Statistics Is 9-03
Not Supported
G501_01924682_AAA 7 Managing RADIUS Q0192468 P[G501_FF017 Corrective N N N
Accounting Records 2 27897_GTP]
Following Loss of
Communications
G501_01915668_SVC 7 Enhancement CLI to Q0191566 P[G501_019109 Corrective Y Y Y
Increase Flowcache 8-05 48EMG_SVC,
List Sizes on CMC G501_0192468
2_AAA]
G501_01645361_RT 7 Interface Ping Does Q0164536 - Corrective N N N
Not Use Routing 1
Table
G501_01871092_GTP 7 SHASTA VPN VSA Q0187109 - Corrective N N N
Not Included in G- 2-03
CDR for GRE PPP
Call
G501_01867815_GTP 7 N3 Counter Is Not Q0186781 P[G501_013393 Corrective N N Y
Uniquely Handled 5-02 20ACT_GTP,
Per PDP Context G501_0190472
8EMG_GTP]
G501_01902903_SVC 7 SSM Trap Due to Q0190290 P[G501_018112 Corrective N N N
Access of Corrupted 3 65_SVC]
Flow Cache Pointer
G501_01950157_PSEUD 7 Dumping Packets Q0195015 - Corrective N N N
O During Debug Can 7
Cause the Node to
Become
Unresponsive
Patch Package 8 patches
G501_01956568_I 8 Null-Pointer Access Stack Q01956568 Corrective N N N
SNCMC Trace in CMC3 is Printed
More Than Once
G501_01950900_S 8 Incorrect Statistic Q01950900 P[G501_018267 Corrective N N N
TATS Duration Interval 83A_STATS]
G501_019926 8 Incorrect Error Code Q01992673- - Corrective N N N

Reported by MSISDN 02
73_DCCCMC Trace Tool

52

G501_01939135_ 8 Session Timer Table Q01939135- M[G501_01939 Preventive N N N
GTP Corruption Due to Race 07 135LTD_GTP
Condition G501_0195770
3LTD_GTP]
P[G501_018856
72_GTP
G501_0150539
4EMG_ACCT]
G501_01979584_ 8 Unused Coupon Rate Q01979584 P[G501_FF013 Preventive N N N
GTP Might Be Lost 69144_PPDSSP
]
G501_01978420_S 8 SSM Reset Due to Invalid Q01978420 Preventive N N N
VC Memory Access
G501_01979441_S 8 SSM Reset Due to Q01979441- M[G501_01870 Preventive N N N
VC Flowcache Invalid 02 149DBG_SVC
Memory Access G501_0181800
7_SVC]
P[G501_017871
84_SVC
G501_0157019
1EMG_SVC]
G501_01815175A 8 Incorrect SSP Time Q01815175- M[G501_01815 Preventive N N Y
_TIMESSP Stamp 05 175_TIMESSP] &
Corrective
G501_01666559_ 8 CLI Enhancement to Q01666559- P[G501_015103 Corrective N N N
GTP Display Extended QoS 02 86_GTP
Profile Information G501_0173313
Element 4A_ACCTCMC
G501_0186781
5_GTP]
G501_01955265_ 8 Memory Leak On P1 Q01955265 Corrective N N N
RMC Module 18 (RPC)
Instance 01
G501_01815175A 8 Incorrect SSP Time Q01815175- M[G501_01815 Preventive N N Y
_TIMECMC Stamp 05 175_TIMECM &
C]P[G501_0163 Corrective
9328_PSPMGR
]
G501_01956568_I 8 Null-Pointer Access Stack Q01956568 P[G501_010843 Corrective N N N
SNSSP Trace in SSC3 is Printed 97_ISN]
More Than Once
G501_01967407_ 8 RADIUS Attribute Acct- Q01967407 Corrective N N N
AAA Delay-Time has Large
Value
G501_01959153_I 8 FELC Takes Long Time Q01959153 P[G501_014508 Corrective N N N
FMGR To Response After 17A_IFMGR]
Reseating Card
G501_01937813_S 8 Updated CBB Policy from Q01937813- P[G501_014651 Corrective N N N
VC Gx May Not Be Used 01 28A_POLMGR
After SSM Redundancy ]
G501_01992673_ 8 Incorrect Error Code Q01992673- Corrective N N N
DCCSSP Reported by MSISDN 02
Trace Tool

53

G501_01944567_ 8 Possible Authentication Q01944567- P[G501_018511 Corrective N N N
DCC Failure During 02 88_DCC]
CCR(I)/CCA(I) Exchange
Patch Package 9 patches
G501_02001740_S 9 Timestamp Of Statistics Is Q02001740 P[G501_018151 Corrective N N N
VCSSP Incorrect 75A_TIMESSP
G501_0195090
0_STATS]
G501_02019884_ 9 Support For Q02019884 P[G501_017884 Corrective N N N
DST America/Port-au-Prince 30_DST]
Daylight Savings Time
Changes
G501_02002598_ 9 Too Many GTP Billing Q02002598 M[G501_01996 Corrective N N Y
GTP Logs Generated 131_GTP]
P[G501_016490
46_GTP]
G501_02015821_ 9 PDP Contexts Not Q02015821 Corrective Y Y Y
GTP Removed After Session
Time Expires
G501_02001740_S 9 Timestamp Of Statistics Is Q02001740 P[G501_019509 Corrective N N N
VCCMC Incorrect 00_STATS
G501_0181517
5A_TIMECMC
G501_0146759
8_SERVICES
G501_0161658
7_AAAMGR]
G501_02004927_I 9 GDC Tool Unable To Q02004927- P[G501_018741 Corrective N N N
SN Telnet To CMC P1 To 01 58_ISN]
Collect Data
G501_02023483_ 9 RADIUS Accounting Q02023483- P[G501_019246 Corrective N N N
AAA Records Not Sent From 02 82_AAA]
Disk
G501_02005896_I 9 SSC 3 Cards Can Not Q02005896 Corrective N Y Y
NIT Generate Encrypted Data
Logs
G501_02018947_S 9 APN Configuration Errors Q02018947- Corrective Y Y Y
UBMGR Following CMC 01
Switchover or Reload
G501_02023131_ 9 Incorrect Buffer Usage Q02023131 Preventive N N N
NETINET Causes Hung tNetTask
G501_02005047_ 9 WRAP statistics are not Q02005047 Corrective N N N
WRAP collected for all ISPs
G501_FF0200764 9 DCC Empty Quota Q02007643 Commercia N N Y
3ACT_DCC Values lly
Restricted
Feature1
1
WARNING: DO NOT ACTIVATE THIS SOFTWARE PATCH AND/OR ANY OF ITS FEATURES UNLESS YOU ARE EXPLICITLY AUTHORIZED
BY NORTEL TO DO SO FOR YOUR NETWORK. THE SOFTWARE PROVIDED IS PROPRIETARY TO, AND A TRADE SECRET OF, NORTEL AND/OR
ITS SUPPLIERS. UNAUTHORIZED USE OF THIS PATCH COULD SUBJECT YOUR ORGANIZATION TO BOTH CRIMINAL AND CIVIL
LIABILITY. THE MERE RECEIPT OF THIS SOFTWARE PATCH DOES NOT CONSTITUTE AUTHORIZATION BY NORTEL OF THE RIGHT TO USE
IT. PLEASE CONTACT YOUR NORTEL REPRESENTATIVE SHOULD YOU DESIRE TO ACTIVATE THE FEATURES IN THIS SOFTWARE
PATCH. THANK YOU FOR YOUR COOPERATION.
2
If “Y”, please refer to section ‘Patches Requiring Special Handling for Application or Removal’ for a summary of the special
handling requirements. Refer to the patch PD file for detailed information.

54
3
Additional information in an Excel spread sheet as specified in the .PD file is available on nortel.com as
G501_01573968_TRMGR.xls.
4
Console ouput time stamps associated with events reported will be out of sequence, a tool to sort the events by time is availalble
on nortel.com as “GGSN Trace Tool Sorter” and dowloads as ttsort.pl.gz
5
Forward patch dependancy, see CAB 2007007839.
6
M[list of patches] – Mutually Exclusive: A list of patches that cannot exist with this patch in a patch profile.
7
P[list of patches] – Prerequisite: A list of patches that are required before this patch can be applied.
6.2 Patch Package Application and Removal
Starting with GGSN5.0.1 release, patches have been grouped together into packages so as
to limit customer impact.
Alert: An important alert has been added to Nortel GGSN5.0.1 NTP 411-5221-927 -
GGSN Provisioning Procedures - Appendix B: “GGSN Patch Application” - Section “
Procedure to update Patch Package” regarding the pre-requisite procedure described in
Step 8 of Section “Patching Prerequisites”.
Note: Step 8 of Section “Patching Requisites” must be executed on the SCS

server prior to the application of a new patch package. A restart of the SCS server
processes is also required. However, if the pre-requisites step has already been
performed during previous patch package application, you don’t need to do it again.
Please download the latest Provisioning Procedure NTP (v09.17 or higher).
6.2.1 Information on Previous Patch Packages
As of this date, a total of nine (9) patch packages (1, 2, 3, 4, 5, 6, 7, 8 and 9) have been
created for GGSN5.0.1 release. For application or removal instructions on patch package
8, 7, 6, 5, 4 and 3, please refer to Section 13 Appendix B “Previous Patch Package
Instructions” of this document.
6.2.2 Application and Removal Instructions for Patch Package 9
6.2.2.1 Warnings and Notes
The latest package for GGSN5.0.1 release is patch package 9. Prior to application of
patch package 9, it is assumed that the node is patch current to patch package 8 i.e. all
applicable patches from package 1 through 8 plus EMGs are applied on the node and

55
with all dependencies resolved. If the node baseline is not at patch package 8, the
instructions to apply patch package 9 may vary.
Warning: FTP'ing files to or from the GGSN during patch package application can cause
high GGSN CPU utilization that can impact the GGSN patching functionality. Users are
recommended to avoid running FTP to the GGSN or executing any other CLI commands
on GGSN during patch package application. Also, disable any auto FTP or CLI scripts
that may FTP files from the GGSN.
6.2.2.2 Procedure to Apply Patch Package 9
To apply patch package 9 to a GGSN node, please follow the steps below. If you are
unsure of the instructions, please contact Nortel Support for further clarification.
1. Make sure that Step 8 of Section “Patching Prerequisites” in Nortel GGSN5.0.1 NTP
411-5221-927 GGSN Provisioning Procedures - Appendix B: “GGSN Patch
Application” is executed. If the pre-requisites step has already been performed during
previous patch package application, simply skip and proceed to the next step.
2. FTP patch package 9 and all applicable EMG patch files to the SCS server under
/opt/patches directory. Refer to NTP 411-5221-927 Appendix B Section “FTP Patch
to SCS server” if needed.
3. Perform pre-application health checks following NTP 411-5221-927 Appendix B

Section “Pre-Application - Health Check Procedure”.
4. Log in as device_owner user from SCS client.
5. Accept patch package 9 and all applicable EMG patches from SCS client -> Patch
Manager -> Select Patch -> Click Update -> Click Add. Resolve dependency issues
(if any, refer to Table 1 and Table 2 if needed). Refer to NTP 411-5221-927
Appendix B Section “Auto Selection” if needed. For patch persistency details, refer to
NTP 411-5221-927 Appendix B Section “Accepting patches”.
6. Record the current active patch profile that is applied to the GGSN. You can find this
information from SCS client -> Patch Manager -> Device -> Select Region -> Select
GGSN.
7. Clone the active patch profile from Patch Manager window for use of patch
package9. A Patch Profile Configuration window will be opened automatically upon
the completion of the cloning. Refer to NTP 411-5221-927 Appendix B Section
“Clone Patch Profile” if needed.

56
Note: Patch profile cloning is the preferred method of patch package application.
In this method, the active patch profile is cloned to create a new patch profile. The
latest EMG patches and Patch package 9 patches are then added to this clone
patch profile. The clone patch profile is then swapped with the active patch
profile.
8. The auto pop-up window can be used to edit the newly cloned profile. The edit
window can also be opened manually from the Patch Manager. Make sure that the
patchable load matches the current GGSN5.0.1 software release. Refer to NTP 411-
5221-927 Appendix B Section “Editing a patch profile” if needed.
9. Add the latest EMG patches listed in Table 1 as patch rules to the cloned patch
profile.
10. Add patch package 9 patches as patch rules to the cloned patch profile. A single click
on patch package 9 will auto select/highlight all patches associated with the package.
Refer to NTP 411-5221-927 Appendix B Section “Steps to add patch rules using
Auto selection” if needed.
Note: The following patches (if present) must be removed from the profile prior to
applying PP9 patches. G501_01996131_GTP
1.Patch G501_02002598_GTP cannot be applied with these active patches:

G501_01996131_GTP
11. Verify if the cloned patch profile with the EMG and patch package 9 patches can be
applied to the GGSN. Refer to NTP 411-5221-927 Appendix B Section “Verify
Patch Profile” if needed. Monitor the GGSN terminal logs during this step to make
sure that the profile is ok for application.
Note: The total number of patches in the PP9 profile shall be 302. Please verify the
list with patch package PD file.
12. Swap the active patch profile with the cloned patch profile from SCS client (as
device_owner user) -> Patch Manager-> Device -> Select Region -> Select GGSN ->
Click Edit -> Select the cloned patch profile -> Click Ok. Refer to NTP 411-5221-927
Appendix B Section “Swapping a Patch Profile” if needed.
13. Verify that the node is patching current to patch package 9 from SCS client patch
manager.
Note: Resync is required for application of the patch package 9.
14. Perform post-application health checks on GGSN following NTP 411-5221-927

Appendix B Section “Post-Application - Health Check Procedure”.

57
6.2.2.3 Procedure to Remove Patch Package 9
This procedure details the steps to rollback patch package 9 to patch package 8.
1. Swap the current active patch package 9 profile with the previous patch package 8
profile from SCS client (as device_owner user). Refer to NTP 411-5221-927
2. Verify that the patch package 9 is removed from the GGSN while the node is restored
to previous patch package 8 from SCS client or GGSN.
Note: Resync is required for removal of patch package 9
3. Perform post-application health checks following NTP 411-5221-927 Appendix B

Section “Post-Application - Health Check Procedure”.
6.2.2.4 Special Handling Instructions
This section is required only if a patch is listed in Table 2 of Section 6.3 and
applied/removed individually other than through the patch package process described
above.
A few patches within patch package 9 and new EMG patches, if applied or removed
individually, require special handling. For more details, please refer to Section 6.3
Patches Requiring Special Handling. If patch package process is followed, simply ignore
this Section 6.2.2.4.

58
6.3 Patches Requiring Special Handling
Note: This section is applicable only if a patch listed in Table 2 is applied or removed
individually rather than through a patch package process describled in Section 6.2. If
Section 6.2 are followed, this Section 6.3 may be ignored.
This section covers special procedures or actions that need to be executed on the GGSN per
individual patch operation basis:
• Prior to and following the application of an individual patch
• Prior to and following the removal of an individual patch
This section only applies to the patches listed below in Table 2.
NOTE: Patches requiring only a resync after patch application are not covered in this
section. Table 1 above (heading titled ‘Disruptive Apply”) and patch PD files should be
reviewed to identify those details.
Table 2: Patches Covered in this Section

Patch ID Title
G501_01584892EMG_PATCHMGR L2TP Tunnels Bouncing After Patch Profile Application
G501_01223788ACT_P2ROUTING BGP capability not recognized by BGP peer
G501_01341393A_ACCT Incorrect G-CDR Duration and QoS Container ChangeTimes
G501_FF01385579ACT_DCCCMC Parking Meter Charging Enhancement Feature
G501_FF01385579ACT_DCCSSP Parking Meter Charging Enhancement Feature
G501_FF01385577ACT_ERCMC DCCv2 Envelope Reporting Feature
G501_FF01385577_ERSSP DCCv2 Envelope Reporting Feature
G501_01510180_LI ADMF/DF connection are not automatically restored
Potential Call Processing Degradation Due To Certain ARP
G501_01484327AACT_NETINET
Traffic
SSM Traps & Usage after update incorrect when Exclude QCT
G501_01527169AEMG_GTP
enabled
G501_FF01369144ACT_PPDCMC Dual Coupon Feature
G501_FF01369144_PPDSSP Dual Coupon Feature
G501_01467598_GTP Wrong Byte Count For Tariff Switch CD
G501_01450778ACT_IFMGR Increase the MTU Size of Gn IP Interface on GELC
G501_01573968_TRMGR Output of MSISDN/IMSI trace tool is missing some information
G501_01568521_SSC3 SSC3 Packets Drop on bcm5631 (Port10 Buf Full Drops)
G501_FF01567650ACT_IPCMC TCP MSS Clamping
G501_FF01567650_IPSSP TCP MSS Clamping
G501_01591035_GTP SSM traps on different cards
G501_01595094AACT_AAA GGSN Always Sends A Password To RADIUS Within Access
Requests
G501_01614712ACT_DCC 3GPP Rel 6 Gy Diameter CC Conformance
G501_01646145A_PPDSSP Dual Coupon Validity Time
G501_01334913_DST Support For Western Australia Daylight Savings Time Rules
G501_01639302_GTP PDP Context Fails To Clean-up Under Certain Error Condition
G501_01653102ACT_GTP N3 Echo Response Message Event Logs Always Enabled
G501_01726458_PPDCMC Incorrect Tariff Change Information For Prepaid
G501_01726458_PPDSSP Incorrect Tariff Change Information For Prepaid
G501_01778204ACT_GTP Incorrect DCC Tariff Time Change Report
G501_01783408_FLOWMGT SSM Missed Poll/Reset Due to Generated Flows From P2P

59
Application
G501_FF01727897_GTP TCP MSS Config Not Retained After Reboots, Resyncs and
CMC SOs
G501_01466350ACT_LI Enabling Lawful Intercept to use VLAN Connectivity to the
Network
G501_01743059AEMG_CONFMGR Primary Version DB Not Saved To Disk Resulting in Out of
Sync
G501_00950877_FLOWMGT A Large Number of Flow Management Event Logs
G501_01529555_OVLD Instance 84 Memory Leak in IPC Module
G501_01727860_XPIF GELC Fragmentation Cache Enhancement for Gn
G501_01733134A_ACCTCMC Accounting Time Stamp Consistency
G501_01733134_ACCTSSP Accounting Time Stamp Consistency
G501_01831139ACT_ACCTCMC Long Duration GCDRs After SSM Failures
G501_01760965_GTPSSP Timestamp in Service Request Earlier Than Absolute Coupon
Lifetime
G501_01760965_GTPCMC Timestamp in Service Request Earlier Than Absolute Coupon
Lifetime
G501_01796399ACT_SIG TEID Not Recognized In Pdp Update Failures
G501_01798767AACT_GTP Display Warning Service Package Not Found In Event Log
G501_01728656ACT_GTPPCMC Parking Meter Start Time Later Than Close Time In GCDR
Container
G501_01728656_GTPPSSP Parking Meter Start Time Later Than Close Time In GCDR's
Container
G501_01505119ACT_SNTP Invalid IP address for SNTP Client Configuration
G501_01831139_ACCTSSP Long Duration GCDRs After SSM Failures

G501_01795346EMG_TARPATCHER No Core Files Are Generated After Processor Soft Reset
G501_01548395_GTPCMC SSM Reset During Time-of-Day Billing Processing
G501_01548395_GTPSSP SSM Reset During Time-of-Day Billing Processing
G501_01502203ACT_ACCTSSP Long Duration GCDRs for Fallback/Fallforward
G501_01850843ACT_DCC Option To Add the CC-Total-Octets AVP to the Used-Service-
Unit AVP
G501_01855017_GTP Periodic Billing Not Generating GCDRs When Expected
G501_01839550EMG_GTP SSM Reset Due to Accessing Invalid Data Context
G501_01865914EMG_AAA CMC3 Switchover w/wo SSC3 Reset Due to RADIUS Profile
Modification
G501_01799972BEMG_DCC CMC Switchover Due to Invalid Message Size
G501_01088170_SSH Secure Shell (SSH) Robustness Improvements
G501_01814048ACT_DCCCMC and GGSN Encodes USU AVP Non-Compliant with VF
G501_01814048_DCCSSP Specification
G501_01892881_GTPCMC and G501_01892881_GTPSSP Periodic G-CDR May Be Generated Early After ULI Change
G501_01863890_LI Potential LI CC Packets Dropped

G501_01912068_RMC Management Port Settings Lost After Resync
G501_01913874ACT_GTP PDP Context Deleted Due To QoS MaxBitRate Set To Zero
G501_01950186ACT_GTP Increase MBR and GBR for Downlink Data Throughput
G501_01915668_SVC Enhancement CLI to Increase Flowcache List Sizes on CMC
G501_01867815_GTP N3 Counter Is Not Uniquely Handled Per PDP Context
G501_01815175A_TIMECMC Incorrect SSP Time Stamp
G501_02002598_GTP Too Many GTP Billing Logs Generated
G501_02015821_GTP PDP Contexts Not Removed After Session Time Expires
G501_02005896_INIT SSC 3 Cards Can Not Generate Encrypted Data Logs
G501_02018947_SUBMGR APN Configuration Errors Following CMC Switchover or
Reload
G501_FF02007643ACT_DCC DCC Empty Quota Values

60
6.3.1 G501_01584892EMG_PATCHMGR
Patch Application Handling

This patch MUST be the first patch in the profile.
6.3.2 G501_01223788ACT_P2ROUTING

Do not activate patch when MPLS is turned on in the network.
Contact next level of support before activating this patch.
Patch Removal Handling

When patch is de-activated, BGP peer connection might not get re-established.
Contact next level of support before de-activating the patch.
6.3.3 G501_01341393A_ACCT

This patch should not be applied during traffic. After this patch is applied, a Resync is
required as specified in the Patch Description (PD) file
Prior to patch application, all new PDP sessions should be disallowed and all existing PDP
sessions closed. Step by step instructions for patch application are specified in the Patch
Description (PD) file.

This patch should not be unapplied during traffic. Prior to patch removal, all new PDP
sessions should be disallowed and all existing PDP sessions closed. Step by step
instructions for patch removal are specified in the Patch Description (PD) file.
6.3.4 G501_FF01385579ACT_DCCCMC


61

6.3.5 G501_FF01385579ACT_DCCSSP


6.3.6 G501_FF01385577ACT_ERCMC


6.3.7 G501_FF01385577_ERSSP


62

6.3.8 G501_01510180_LI

If GGSN already lost ADMF/DF connection and ping test from GGSN to ADMF is
successful prior to apply this patch, a dummy change to the ADMF address from SCS LI
profile is required to restore the connection. Applying this patch alone will not fix an
already broken connection.
6.3.9 G501_01484327AACT_NETINET

Note: This patch replaces G501_01484327ACT_NETINET. If this patch is applied you

must remove it before applying this patch.

6.3.10 G501_01527169AEMG_GTP

This patch should not be applied during traffic.

63
6.3.11 G501_FF01369144ACT_PPDCMC


6.3.12 G501_FF01369144_PPDSSP


6.3.13 G501_01467598_GTP
Patch Application and Removal Handling

Application of this patch within one minute of the hour boundary will result in a skipped
TOD execution for that hour.
6.3.14 G501_01450778ACT_IFMGR

After activating this patch one of the following actions needs to be taken for the change to
take effect:

64
1) GELC card disable/enable and a dummy change(such as check/uncheck the

"accounting enabled" check box on SCS GUI) on the GELC IP interface.
In a non-redundant GELC configuration, a service outage will occur. To minimize

the impact in this case, the patch needs to be activated/deactivated in a maintenance
window.
OR
2) Resync the ggsn.
Step by step instructions for patch are specified in the Patch Description (PD) file.

After deactivating this patch GELC card disable/enable and a dummy change(such as
check/uncheck the "accounting enabled" check box on SCS GUI) on the GELC IP interface
is nessecary.
Step by step instructions for patch are specified in the Patch Description (PD) file.
6.3.15 G501_01573968_TRMGR

If trace tool output files have been collected in /disk/log/trace/, and customer wishes to save
them, do so before application and remove from the directory. Step by step instructions for
patch are specified in the Patch Description (PD) file as well as additional notes.
6.3.16 G501_01568521_SSC3
NOTE: If a SFC switchover occurs, then a resync is required after the SFC switchover is
completed as per CAB 2007007717.
Patch Applicaton Handling

Make sure that the SSC3 FPGA load is 12 or higher before applying this patch.
6.3.17 G501_FF01567650ACT_IPCMC

The patch G501_FF01567650ACT_IPCMC should be activated only for those customers
requiring the functionality available when this patch is active.
The patch G501_FF01567650ACT_IPCMC must be applied and activated before the patch
G501_FF01567650_IPSSP.

65
The patch G501_FF01567650ACT_IPCMC should not be applied during traffic. After this
patch is applied and activated, a GGSN Resync is required as specified in the Patch
For details on special handling details for patch G501_FF01567650_IPSSP, please refer to
G501_FF01567650_IPSSP.

The patch G501_FF01567650_IPSSP should be removed either before or at the same time
that patch G501_FF01567650ACT_IPCMC is removed.
For details on special handling details for patch G501_FF01567650_IPSSP, please refer to
G501_FF01567650_IPSSP.
Note: For all the GGSN nodes in a SCS region, removal of a patch rule(s) from an active
patch profile will cause unapplication of that patch(es) from all the GGSN nodes that has
the same active patch profile. The preferred method is to first clone the active patch profile.
Remove the applicable patch rules from the clone patch profile. Then swap the active patch
profile with the cloned patch profile on all the GGSN nodes that do not require the patch
functionality. Please refer to Nortel GGSN 5.0.1 NTP 411-5221-927 GGSN Provisioning
Procedures –Appendix B, “GGSN patch application” for details on patch profile cloning
and swapping procedures.
Patch G501_FF01567650ACT_IPCMC should not be unapplied during traffic. Prior to

patch removal, all new PDP sessions should be disallowed and all existing PDP sessions
closed. Step by step instructions for patch removal are specified in the Patch Description
(PD) file.
6.3.18 G501_FF01567650_IPSSP

The patch G501_FF01567650ACT_IPCMC must be applied and activated before
G501_FF01567650_IPSSP.
The patch G501_FF01567650_IPSSP should not be applied during traffic. After this patch
is applied, a GGSN Resync is required as specified in the Patch Description (PD) file.

66

The patch G501_FF01567650_IPSSP should be removed either before or at the same time
that patch G501_FF01567650ACT_IPCMC is removed.
Note: For all the GGSN nodes in a SCS region, removal of a patch rule(s) from an active
patch profile will cause unapplication of that patch(es) from all the GGSN nodes that has
the same active patch profile. The preferred method is to first clone the active patch profile.
Remove the applicable patch rules from the clone patch profile. Then swap the active patch
profile with the cloned patch profile on all the GGSN nodes that do not require the patch
functionality. Please refer to Nortel GGSN 5.0.1 NTP 411-5221-927 GGSN Provisioning
Procedures –Appendix B, “GGSN patch application” for details on patch profile cloning
and swapping procedures.
6.3.19 G501_01591035_GTP

Exercise CAB 2007007824.
required as specified in the Patch Description (PD) file.
6.3.20 G501_01595094AACT_AAA

If the functionality of this patch is desired, it should be activated along with activating patch
G501_01407739ACT_INF.
6.3.21 G501_01614712ACT_DCC

This patch must be activated if running Diameter Gy.
Step by step instructions for patch application are specified in the Patch Description (PD)
file.
6.3.22 G501_01646145A_PPDSSP

A resync is needed if G501_FF01369144ACT_PPDCMC is activated.

67
Step by step instructions for patch application are specified in the Patch Description (PD)
file.
6.3.23 G501_01334913_DST

Western Australia DST changes were delivered with this patch. The changes will not be
effective if the patch is removed and re-applied after initial application. The transition to
and from the DST time will not happen at the correct times.
Perform a resync after the patch G501_01334913_DST is re-applied to ensure DST

changes happen at the correct time.
6.3.24 G501_01639302_GTP

G501_01639302_GTP patches both CMC and SSP and introduced a callback function to
safe guard the delete PDP request messages sent between the CMC and SSP. There is one
minute delay between patch applied on the CMC and patch applied on all SSPs. During this
time the following event log might be generated:
Fri 19-Oct-2007 00:53:01 13/1/1:RPC Manager 75 1 1 MINOR

Module gtp/0 on node 11/3/3 did not respond to an RPC request from module gtp/0 on
node 13/1/1 - timed out after 11696 msec (op 78, xid 696143751, life 9500, intvl
500)
It is recommend that all PDP contexts are deleted and traffic disabled before applying and
unapplying this patch.
6.3.25 G501_01653102ACT_GTP
Activating the patch disables the logging of the N3 Echo logs to the GGSN event log file.
The N3 echo logs indicates that the SGSN did not respond back to the GGSN initiated echo
request within "T3" seconds after "N3" retries causing all sessions on that GTP path to be
taken down.
Here are the examples of the logs:
24-Aug-2007 14:18:26 14/1/1:gtp,0: 31, 1, MAJOR,

EchoReqTimerCallbackV0:(Missed N3 Echo Responses from SGSN 1.2.3.4
24-Aug-2007 14:30:46 14/1/1:gtp,0: 31, 1, MAJOR,

EchoReqTimerCallbackV1Sig:(Missed N3 Echo Responses from SGSN 1.2.3.4

68
24-Aug-2007 14:30:46 14/1/1:gtp,0: 31, 1, MAJOR,

EchoReqTimerCallbackV1Data:(Missed N3 Echo Responses from SGSN 1.2.3.4
Note: Activate this patch only if this functionality is required.
6.3.26 G501_01726458_PPDCMC

Apply this patch together with patch G501_01726458_PPDSSP.

Unapply this patch together with patch G501_01726458_PPDSSP.
6.3.27 G501_01726458_PPDSSP

Apply this patch together with patch G501_01726458_PPDCMC.

Unapply this patch together with patch G501_01726458_PPDCMC.
6.3.28 G501_01778204ACT_GTP
The Tariff-Time-Change AVP allows a DCC server to specify a time at which the GGSN will
process a tariff change. It includes the time in seconds since January 1, 1900, 00:00 UTC, when the
tariff of the service will be changed. Prior to the patch application, the GGSN incorrectly converts
the number of seconds to an internal time representation that causes the tariff change to be processed
early by the number of leap seconds (currently 23).
When this patch is activated, the GGSN will compensate the leap seconds by adding it to the Tariff-
Time-Change received.
Please review the patch PD file for more details.
DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS

FUNCTIONALITY.
6.3.29 G501_01783408_FLOWMGT
Please review the patch PD file for details of this patch.
Note: A flow management policy must be applied for this patch to be effective. Please refer
to NTP 216313-B for details on provisioning of the flow management policy.

69
For detailed information, please refer to bulletin: 2007007825.
6.3.30 G501_FF01727897_GTP
This patch is only executed if patch G501_FF01567650ACT_IPCMC is

activated.
6.3.31 G501_01466350ACT_LI
LI (Lawful Interception) on the GGSN can be configured with either a VLAN access
connection or an IPSEC tunnel as the under laying connection to the LI server.
When G501_01466350ACT_LI is activated, LI over the VLAN access connection is

activated.
Note: Activate G501_01466350ACT_LI only when VLAN is needed for the LI ISP. Do not
activate patch G501_01466350ACT_LI if LI over an IPSEC tunnel is needed.
6.3.32 G501_01743059AEMG_CONFMGR
Note: The following steps are only for Lab testing. Patch application on the live site
does not require a resync or the procedure execution.
The Lab Test Instructions for the patch G501_01743059AEMG_CONFMGR has been
updated. Please follow the instructions given below instead of the instructions on the patch
PD file.
1. Verify the current timestamp on the GGSN using 'show time', make sure it is set
correctly.
2. If the GGSN has a standby CMC card, verify the standby CMC is in redundant state by
executing 'show card' on the GGSN.
3. Make a note of the timestamp on the following files /disk/config/primary/VERDB.CFG
and /disk/config/qs1/VERDB.CFG. Login to the standby CMC card and make a note of
the timestamp of VERDB.CFG in both /disk/config/primary and /disk/config/qs1.
Note: The timestamp returned on active CMC may not exactly match with the standby
CMC. There is usually a few seconds difference.
ggsn-139(SHASTA)# dir /disk/config/primary/VERDB.CFG

size date time attr name
---------- ------ ----- ---- -------
16384 28-Feb-2008 21:43:56 rw /disk/config/primary/VERDB.CFG
ggsn-139(SHASTA)# dir /disk/config/qs1/VERDB.CFG

size date time attr name

70
---------- ------ ----- ---- -------

16384 28-Feb-2008 21:43:56 rw /disk/config/qs1/VERDB.CFG
4. Login as 'device_owner' user to the SCS client. From Patch Manager-> Patch Profile,
add a new patch profile. Click OK to save the Patch Profile. This action modifies both
/disk/config/primary/VERDB.CFG and /disk/config/qs1/VERDB.CFG.
Note: Adding a patch rule is not needed.
5. Wait for 120 seconds
6. Check the timestamp on VERDB.CFG on both /disk/config/primary and
/disk/config/qs1 (using step 3). Notice the timestamp of
/disk/config/primary/VERDB.CFG does not get updated. Login to the standby CMC,
notice the timestamp of /disk/config/primary/VERDB.CFG have not been updated also.
7. Reset the active CMC card by pressing the reset button on the faceplate of the CMC
card.
Note: If the active CMC is on slot 13, and a standby CMC card exists in slot 14,
resetting the CMC will make the CMC card in slot 14 to come back as the active CMC.
8. After the GGSN reboot's, check the GGSN status from the SCS client. The GGSN will
be out of sync.
9. Resync the GGSN.
10. After the GGSN comes back insync, apply the patch
G501_01743059AEMG_CONFMGR to the active patch profile.
11. Repeat steps (1-5), then check the timestamp of VERDB.CFG on both
/disk/config/primary and /disk/config/qs1. Verify the timestamp on both primary
primary and qs1 have been updated from the previous timestamp (from step 3). Login to
the standby CMC and verify the timestamp on the files have been updated also.
12. Reset the active CMC card by pressing the reset button on the faceplate of the CMC
card.
Note: If the active CMC is on slot 13, and a standby CMC card exists in slot 14,
resetting the CMC will make the CMC card in slot 14 to come back as the active CMC.
13. On GGSN reboot, verify the GGSN is insync from the SCS client.
6.3.33 G501_00950877_FLOWMGT
When a Flow Management Policy is applied to a subscriber template, and the mobile using
the subscriber template sends data flows more than the configured flow limit, the following
type of flow management event messages may fill up the GGSN's event logs:
"INFO, Flow Management Service: Subscriber (910000000000002-83 ssg-131-wireless)
incurs pkt drop due to reaching MAX flow limit, drop count since previous MAX event log:
0, (Flows: Maximum configured 500, currently allocated 500(prflows 0)).
When this patch, new CLI commands have been implemented to enable and disable the
flow management event logging. The new CLI commands are:
- "enable flowmgt event logging".
- "disable flowmgt event logging".
- "show flowmgt event logging".

71
6.3.34 G501_01529555_OVLD
The patch fixes a memory leak on the SSPs related to overload statistic collection. Since the
leak rate is small relative to the total SSM memory, the cumulative leak can be ignored as
long as no SSP memory overload alarms have been seen. Please note that the leaked
memory cannot be freed unless a GGSN reboot/resync is performed, but this is not
recommended unless a memory overload alarm has already been raised.
6.3.35 G501_01727860_XPIF
If GELC cards are present at the time of this patch application, a resync must be performed.
If GELC cards are installed after this patch has already been applied, no resync is required.
6.3.36 G501_01850843ACT_DCC
NOTE: DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS

FUNCTIONALITY.
The following details are taken from the patch PD file.
Problem Description:
Some DCC servers expect the CC-Total-Octets AVP to be reported as part of
the Used-Service-Unit AVP.
Impact:
Prepaid calls may not be successful when using a DCC server that expects
the CC-Total-Octets AVP.
Solution:
Allow the user to enable the inclusion of CC-Total-Octets AVP to the
Used-Service-Unit AVP message.
6.3.37 G501_01733134A_ACCTCMC
DO NOT APPLY OR UNAPPLY THE PATCH DURING TRAFFIC.BOTH BOTH

G501_01733134A_ACCTCMC AND G501_01733134_ACCTSSP MUST APPLIED
TOGETHER.

1. Disallow new GTP sessions on the GGSN.
2. Close all active GTP sessions on the GGSN and flush the billing.
Any current billing files left on either CMC disk prior to patch
application may still have incorrect time stamps.

72
3. Re-Sync the GGSN.

4. Apply this patch via the SCS client.
5. Verify there is no abnormal activity present after patch
application.
6. Allow new GTP sessions on the GGSN.
7. This patch will apply to the CMC.

Any current billing files left on either CMC prior to patch application
may have incorrect time stamps.
4. Unapply this patch through the SCS client.
5. Verify that the patch is properly removed.
removal.
Note: If the patch is added during patch package 5 addition,

G501_01733134A_ACCTCMC will be automatically added pior to
G501_01733134_ACCTSSP.
6.3.38 G501_01733134_ACCTSSP
DO NOT APPLY OR UNAPPLY THE PATCH DURING TRAFFIC.

BOTH G501_01733134A_ACCTCMC AND G501_01733134_ACCTSSP MUST
APPLIED TOGETHER.
Please refer to the patch G501_01733134A_ACCTCMC (above) for details.
Note: The patch PD file for G501_01733134_ACCTSSP refers to patch

G501_01733134_ACCTCMC. This patch has been recompiled as
G501_01733134A_ACCTCMC.
Note: If the patch is added during patch package 5 addition,

G501_01733134A_ACCTCMC will be automatically added pior to
G501_01733134_ACCTSSP.
6.3.39 G501_01831139ACT_ACCTCMC
Apply G501_01831139ACT_ACCTCMC before G501_01831139_ACCTSSP.

73
6.3.40 G501_01760965_GTPSSP
1. Disallow new sessions and close all existing sessions.

2. Resync GGSN.
3. Mark G501_01760965_GTPCMC and G501_01760965_GTPSSP as persistent and apply
the patches through the SCS client.
4. Verify the patches have been applied on CMC and SSP successfully.
5. Allow new sessions.
6. Verify there is no abnormal activity present after patch application.
6.3.41 G501_01760965_GTPCMC
Please refer to the patch G501_01760965_GTPSSP (above) for details.
6.3.42 G501_01548395_GTPCMC
The following instructions are applicable only when adding the patch individually.

Note: BOTH G501_01548395_GTPSSP AND G501_01548395_GTPCMC MUST
APPLIED TOGETHER.

2. Mark G501_01548395_GTPCMC and G501_01548395_GTPSSP as persistent. Apply

2. Remove patch G501_01548395_GTPCMC and G501_01548395_GTPSSP through
the SCS client.
3. Verify the patches have been removed from CMC and SSP successfully.
5. Verify no abnormal behavior present.
Note: When patch package 5 is added, a patch rule for G501_01548395_GTPCMC will be
added prior to G501_01548395_GTPSSP.
6.3.43 G501_01796399ACT_SIG

74

FUNCTIONALITY.
When a GTP V1 update PDP request is received with a known TEID but no PDP context
matches the NSAPI, an update response is sent with cause 192 ("Non Existent").
The response TEID is populated with the TEID-C associated with the GGSN tunnel
and not the TEID-C received in the update PDP request message. The SGSN may not
recognize the TEID leading to a retry and timeout scenario.
Impact:
The SGSN may not recognize the TEID leading to a retry/timeout scenario resulting
in a context deletion.
Solution:
When the patch is activated, if an update PDP response is sent with a cause value
of 192 ("Non Existent") the TEID is populated with the value received from
the update PDP request message. If no TEID-C is provided in the update PDP request
message a TEID of 0 is returned.
6.3.44 G501_01502203ACT_ACCTSSP

FUNCTIONALITY.
Note: The patch G501_01502203ACT_GTPACCT must be activated along with this patch
for the functionality to work correctly.
Patch G501_01502203ACT_GTPACCT was created to fix the issue of unexpected
partial GCDRs generated for Fallback/Fallforward scenario. When the
patch is activated, long duration GCDRs are generated if there were a
Fallback/Fallforward update requests without a QoS or RAT change.
Impact:
The GGSN generates GCDRs with a duration longer than expected in the scenario
mentioned above.
Solution:
Make sure that in case of Fallback or Fallforward, the container will be
closed on the backend only if there was a QoS or RAT change. In case of an

75
SGSN change, a partial GCDR is generated only if "SGSN Change Partial Billing"
is enabled.
6.3.45 G501_01798767AACT_GTP

FUNCTIONALITY.
There are two problems that are addressed with this patch:
1. When creating PDP sessions with service packages applied, if some service
packages are not found in GTP manager because some messages for updating
service packages from SUBSCRIBER manager to GTP manager timed out, system
failures will occur and it may not be possible to bring up the sessions until
the GGSN is reloaded.
2. When deleting a secondary session, if the delete times out, the secondary
session will be hung in the disconnecting state. This hung session cannot be
cleaned up and may cause the primary session to be deleted.
Impact:
1. System failures occur but there is no warning message indicating the cause
of the failures.
2. The hung secondary session may cause its primary session to be deleted.
Solution:
1. If this patch is activated, a warning message "Service Package not found,
svcpkg_id = XX, merge_id = XX name = XXXX" is displayed in the event log to
indicate the system status so that the GGSN can be recovered with appropriate
action. When this warning message appears in the event log, the GGSN needs to
be reloaded to resolve the problem.
2. Hung sessions caused by this scenario are cleaned up successfully and

correctly. The fix for this problem is always available regardless of whether this patch is
activated or de-activated.
6.3.46 G501_01728656ACT_GTPPCMC
DO NOT ACTIVATE THIS PATCH UNLESS YOU UNDERSTAND AND REQUIRE

THIS FUNCTIONALITY.
An infrequent billing issue has been observed where a Parking Meter (PM) is reported
which has a start timestamp later time than the close time of the GCDR QoS container.

76
Impact:
When this issue occurs, it causes an incorrect subscriber billing due to a time difference
between the PM timestamp and the GCDR changeTime.
Solution:
When this patch is activated, validation of PM timestamps will be performed on the GGSN
prior to sending the records, and any PMs with timestamps later than the GCDR
changeTime will be discarded. The CBB counts for the discarded PMs will be retained in
the record.
6.3.47 G501_01728656_GTPPSSP
DO NOT APPLY OR UNAPPLY THE PATCH DURING TRAFFIC.

Note: This patch will apply to the SSP.
Any current billing files left on either CMC disk prior to patch
application may still have incorrect time stamps.

Any current billing files left on either CMC prior to patch application
may have incorrect time stamps.
4. Unapply this patch through the SCS client.
removal.
6.3.48 G501_01548395_GTPSSP
The following instructions are applicable only when adding the patch individually.

Note: BOTH G501_01548395_GTPSSP AND G501_01548395_GTPCMC MUST
APPLIED TOGETHER.

77

2. Mark G501_01548395_GTPCMC and G501_01548395_GTPSSP as persistent. Apply
application.

2. Remove patch G501_01548395_GTPCMC and G501_01548395_GTPSSP through
the SCS client.
3. Verify the patches have been removed from CMC and SSP successfully.
5. Verify no abnormal behavior present.
Note: When patch package 5 is added, a patch rule for G501_01548395_GTPCMC will be
added prior to G501_01548395_GTPSSP.
6.3.49 G501_01505119ACT_SNTP
With this patch activated, if the SNTP server IP address configured on the SCS
has 0 as the last octet (x.y.z.0), the IP address on the GGSN will have 255 as
the last octet (x.y.z.255).

FUNCTIONALITY.
6.3.50 G501_01831139_ACCTSSP
Apply G501_01831139ACT_ACCTCMC before G501_01831139_ACCTSSP.
6.3.51 G501_01795346EMG_TARPATCHER
This information is related to CR Q01795346-03.
There are scenarios where a GGSN core dump won't be generated even after the patch is
applied. They are:
1. CMC card needs to maintain 1GB +100MB margin on the disk, if the disk space falls
below that, core dump is not allowed if a SSM crash occurred.

78
2. The GGSN does not allow more than 2 simultaneous core dumps if there are more than 2
SSM’s went down at the same time.
6.3.52 G501_01855017_GTP
Apply G501_01502203ACT_ACCTSSP, G501_01831139_ACCTSSP,

G501_01548395_GTPSSP before G501_01855017_GTP.
6.3.53 G501_01839550EMG_GTP

G501_01726458_PPDSSP must be applied before G501_01839550EMG_GTP can be
applied.
6.3.54 G501_01300738_AAA

Patch G501_01300738_AAA will apply to CMC and SSP. A resync of the GGSN will be
needed under the following circumstances after patch application only:
a) CMC3 cards are used.

b) There exists a RADIUS profile with three or more RADIUS servers.
c) The RADIUS profile for qualification "b)" is bound to an access group.
Prior to performing the resync please ensure to mark the patch persistent.
6.3.55 G501_01799972BEMG_DCC

FUNCTIONALITY.
Please refer the patch PD file for details of the fix.
6.3.56 G501_01088170_SSH
If SSH is enabled on the GGSN and the Operator can telnet but not SSH, a CMC resync or
reload is required after patch application.

79
6.3.57 G501_01814048ACT_DCCCMC and G501_01814048_DCCSSP

FUNCTIONALITY.
6.3.58 G501_01892881_GTPCMC and G501_01892881_GTPSSP
Path application instructions:

1. Both G501_01892881_GTPCMC and G501_01892881_GTPSSP must apply together.
Apply the patches via the SCS client.
application.
3. This patch will apply to CMC.
Patch removal instructions:

1. Unapply both patches G501_01892881_GTPCMC and G501_01892881_GTPSSP via
the SCS client.
3. Verify there is no abnormal behavior present after
patch removal.
6.3.59 G501_01863890_LI
The patch increases the LI TCP send buffer size of the DF connection from the default
to 256kB.
Note: If the GGSN is configured with a LI Profile and the ADMF connection is up, then
following section must be followed.
To verify if the GGSN is configured with a LI Profile:
a. Log in to the GGSN as LI user. Please contact your network administrator for the LI
username/ password for the GGSN and SCS client.
b. Issue the command to verify if a LI Profile is configure.
show li
c. If a LI Profile is configured, issue the following command to verify if the connection to

the LI server is established.
show socket isp= li_default_isp

80
If a LI Profile is not configured or the TCP connection is up, please contact the network
administrator to verify the same.
If a LI Profile is configured and the TCP connection to the LI server is up, please proceed to
the instructions given below to reset the TCP connection.
• The ADMF can send a reset request to GGSN.

• Modify the LI profile configuration on the GGSN.
To modify the LI Profile on the GGSN:

a. Log in from the SCS client as LI user
b. From Access Properties-> LI Profiles-> Select the LI Profile and click Edit.
c. Make a note if the ADMF Port Number 1 settings.
d. Modify the ADMF Port Number1 settings to a dummy numbers. Click OK to save
the changes.
e. Edit the LI Profile and set the ADMF Port Number setting to match the original port
number. Click OK to save the changes.
f. Log in as the LI user to the GGSN. Verify the ADMF connection to the LI server.
show socket isp=li_default_isp
6.3.60 G501_01912068_RMC
When the speed and mode configuration are changed for the management ports and then
the 'save config qs1' command is issued to store the new settings, the "ether mode" field of
'show bootorder' command is not stored accordingly. A resync will cause the management
ports to be set back to a previous configuration displayed in the "ether mode" field.
1. Make a note of the active and standby CMC card. Issue the command:
show card
Here is an example:
13 CMC /CMC Enabled Standby (Redundant)

14 CMC /CMC Enabled Active
2. Make a note of the ethernet port settings (PHY configured) on the active and
standby CMC.
show port ethernet slot= 13 port= 5

show port ethernet slot= 14 port= 5
Here is an example:
ggsn-139(SSU)# show port ethernet slot= 13 port= 5

81
Fri 12-Dec-2008 12:59:35 CST

Ethernet port 13/5 is Up
Admin state: Enabled
PHY configured: 100Mb/s, full-duplex PHY actual: 100Mb/s, full-
duplex
PHY OUI 00:08:95
MAC Addr.for 802.1q Conns: Per Port
ggsn-139(SSU)# show port ethernet slot= 14 port= 5

Fri 12-Dec-2008 12:59:38 CST
Ethernet port 14/5 is Up
Admin state: Enabled
PHY configured: 100Mb/s, full-duplex PHY actual: 100Mb/s, full-
duplex
PHY OUI 00:08:95
MAC Addr.for 802.1q Conns: Per Port
3. Issue the command:
show bootorder
4. Verify the ether mode settings matches the configured settings from ‘show port
ethernet’ output. Here is an example:
ether mode (pm) : 0x711711
^ ^
The first number (7) in the "ether mode" field corresponds to the management port on slot
14.
The fourth number (7) in the "ether mode" field corresponds to the management port on slot
13.
The "ether mode" display can be decoded using the following table:
0 - Auto-negotiation ON Speed 10 mbs Mode Half Duplex
1 - Auto-negotiation OFF Speed 10 mbs Mode Half Duplex
2 - Auto-negotiation ON Speed 100 mbs Mode Half Duplex
3 - Auto-negotiation OFF Speed 100 mbs Mode Half Duplex
4 - Auto-negotiation ON Speed 10 mbs Mode Full Duplex
5 - Auto-negotiation OFF Speed 10 mbs Mode Full Duplex
6 - Auto-negotiation ON Speed 100 mbs Mode Full Duplex
7 - Auto-negotiation OFF Speed 100 mbs Mode Full Duplex
If the port settings from ‘show port ethernet’ and ‘ether mode’ from ‘show bootorder’
matches, no manual configuration change is required.
From the example capture above for ‘show port ethernet’ and ‘ether mode’ in ‘show
bootorder’, the active (slot 14) and standby CMC (slot 13) are set as 100Mb/s, full-duplex.
This matches the ‘ether mode’ settings from ‘show bootorder’ – Auto negotiation disabled,
port statically configured with 100Mb/s, full-duplex.

82
Fixing ether mode mismatch:

Upon patch application, any erroneous bootorder "ether mode" display will not be
automatically corrected. In order to correct it, the management port configuration needs to
be changed to a different speed/mode setting. The configuration can be set back to the
desired setting afterwards.
The following commands can be used:

1. To display the current port configuration:
show port ethernet [slot=]<slot> [port=]<port>
Example:
show port ethernet 14 5
2. To change the port configuration:
set port ethernet [slot=]<slot> [port=]<port>

[speed={s10mbs,s100mbs,s1gbs} duplex={full,half}]
[mac_per_conn={yes,no}] [autosense]
Example:
set port ethernet slot= 14 port= 5 speed= s100mbs duplex= full
3. To display the current bootorder "ether mode" setting:
show bootorder
6.3.61 G501_01913874ACT_GTP

FUNCTIONALITY.
6.3.62 G501_01950186ACT_GTP

FUNCTIONALITY.

83
6.3.63 G501_01915668_SVC
Field Application Instructions

2. Verify there is no abnormal activity present after patch application. If you see the "Patch
status Out of Sync" event, please contact next level of support.
Patch Removal Instructions

1. Unapply this patch via the SCS client.
3. Verify there is no abnormal behavior present after patch removal.
4. Resync the GGSN.
6.3.64 G501_01867815_GTP
The prerequisite patch G501_01339320ACT_GTP for G501_01867815_GTP, when

activated, takes precedence over this patch. Please refer to G501_01339320ACT_GTP PD
file for more detail.
6.3.65 G501_01815175A_TIMECMC
The prerequisite patch G501_01639328_PSPMGR for G501_01815175A_TIMECMC,

when activated, takes precedence over this patch. Please refer to
G501_01639328_PSPMGR PD file for more detail.

1. Apply this patch and patch G501_01815175A_TIMESSP via the SCS client.
application.
Note: Patches not marked persistent, will not reapply in

the event of a switchover, card reset or resync. In these
cases reapply the patch from the SCS. Patches of type
DBG (debug), should not be marked persistent unless
specifically instructed.

1. Unapply this patch and patch G501_01815175A_TIMESSP via the SCS client.
3. Verify there is no abnormal behavior present after

84
patch removal.
6.3.66 G501_02002598_GTP

1. Unapply patch G501_01996131_GTP.

4. Follow field application procedures for G501_01996131_GTP and re-apply the patch.
6.3.67 G501_02015821_GTP

1. Mark the patch persistent.
3. Resync the GGSN.

6.3.68 G501_02005896_INIT

4. Resync the GGSN or Disable/Enable all of the SSC 3 cards for the functionality to be
removed.
6.3.69 G501_02018947_SUBMGR

85
1. Mark the patch persistent.

3. Resync the GGSN.
Note: Failure to resync the GGSN after applying this patch can result in the APN
configuration being lost after a subsequent CMC switchover or reload.

6.3.70 G501_FF02007643ACT_DCC

FUNCTIONALITY.

1. Apply this patch via the SCS client, and Activate it only if the functionality is desired.

1. Deactivate this patch and unapply this patch via the SCS client.

86
7 Configuration Changes and Recommendations
• If the customer wants to change their call model, e.g. from Services to Aggregation, a
resync of the GGSN is recommended. This is applicable to this release and prior
releases.
• "BSN default load directory” or “default_BSN_load directory” refers to the 'isn'

directory.
For example: /disk/image/<default_BSN_load>/cmc is /disk/image/isn/cmc.
• After upgrade to SCS5.0.2, OA&M Servers will require a data path update to reflect the
new directory structure, “/opt/shasta/scs502/log/preside” is the new path.
• For GGSN5.0 and later releases, RADIUS authentication and accounting messages are
processed by the SSPs to improve the activation rate for GGSN call models. The
following configuration change is required for proper RADIUS communication and
distributed AAA feature to work as designed.
1. Login to the SCS GUI as the Gi ISP user.

2. Click on the GGSN device.
3. Select the trunk interfaces tab.
4. For all the Gi interfaces, enable the "Allow tunnel termination" checkbox.
5. Repeat the above steps for all Gi ISPs.
• Procedure for Modifying the default ISP IP address:
This procedure modifies the default ISP IP address for the device owner using the SCS
client. When modifying an existing ISP IP address on the GGSN, it is necessary to
perform a resync of the GGSN afterwards to activate the change and to ensure the
integrity of the accounting data reported by the GGSN. The ISP IP address change
should be performed after traffic has been migrated away from the GGSN to minimize
potential for billing data loss.
Changes to the ISP IP address require extensive changes on the existing configuration
on the GGSN and are extremely CPU intensive. As a result, they hinder GGSN's ability
to handle traffic while the changes are taking effect. Furthermore, these changes may
also corrupt or cause billing data to be lost, or the GGSN could go "Out Of Sync".
Warning:
This activity should be performed only during a maintenance window.
To modify the Default ISP IP address for device_owner using the SCS client, follow
these steps:

87
1. Log into the SCS using a user that has Device Owner privileges.
2. In the Device Manager window, select the appropriate region.
3. Remove GGSN from DNS pool.
4. If accounting statistics are turned on for the GGSN, the profile associated to the
GGSN must be cleared and the user must wait until all pending accounting
statistics are sent to the SCS before continuing. In the Access Properties tab,
manually record the ISP Accounting Profile, so that you can reconfigure it later.
5. Select the Clear button corresponding to the ISP Accounting Profile.
6. Highlight the GGSN, then right-click on it. Select Configure -> Routing... from
the object menu.
7. Enter the new ISP Default IP Address and click OK.
Note: This entry must match the IP address for the GGSN management ethernet
port.
8. Follow the procedure “Resynchronize the GGSN,” to activate the IP address
change to the ISP.
9. Reconfigure the accounting statistics profile to the SCS, if it was cleared in Step
4. Click the Select button corresponding to the ISP Accounting Profile.
10. From the ISP Accounting Profile select window, click on the profile recorded in
Step 4 and click the OK button.
The GGSN is now ready to start handling traffic again.

88
8 GGSN5.0.1 Limitations
8.1 Rebooting from Flash Not Supported

The option to reboot a GGSN5.0.1 image from CMC-2 /flash is no longer
supported. For more details on this issue, please refer to CR Q01884435-01.
As a precaution, the following bootorder settings are recommended for a CMC-
2 configuration.
Note: Prior to setting boot file3 (f3) and boot file 4 (f4) below, issue the
commands “dir /disk/image/isn” and “dir /flash/image/isn” to confirm that the
isn image is present on the disk as well as on the flash. If any of the isn images
is not present, do not set the corresponding boot file path.
Boot file1 (f1): /disk/image/<current GGSN load directory>/cmc

Boot file2 (f2): /disk/image/<previous GGSN load directory>/cmc
Boot file3 (f3): /disk/image/isn/cmc
Boot file4 (f4): /flash/image/isn/cmc
8.2 VLAN, VPN, IP Services

• The application of any IP service to a GRE, VLAN, or IPSEC interface is not
supported. These types of interfaces are referred to as access interfaces on the
GGSN. One step in provisioning such an access interface is the configuration of
an "access subscriber" via the SCS subscriber GUI. The access subscriber is
provisioned using the same GUI as are mobile subscriber templates. It is
possible to add IP services such as firewall or traffic shaping to the access
subscriber. The GGSN will not apply these IP services to the access subscriber.
No error is generated. IP services applied to mobile subscribers using GRE,
VLAN, or other types of access interfaces continue to be supported as previously.
This limitation is introduced effective with the GGSN.4.1 software release.
Patch G321_01081352F_SERVICES in the GGSN3.2.1 software release first
introduced this restriction.
• The VPN plus Internet (VPN+I) option is not supported. When configuring a
VPN on the GGSN (using the "VPN" GUI of the SCS) a selection must be made
whether the VPN is "VPN only" or "VPN+I." The VPN+I option allows mobile
subscriber packets to exit the VPN to the enclosing ISP and then be routed out
the Gi interface of the ISP. Packets returned to the ISP are moved into the VPN
to reach the mobile subscriber. This functionality is not supported on the GGSN
because it requires a firewall policy on the access interface (GRE, VLAN, etc.)
of the VPN. Accordingly, the VPN+I option is not supported; only the VPN-only
option may be selected when provisioning a VPN. This limitation is introduced
effective with the GGSN4.1 software release.

89
8.3 CTP V2 on the SCS GUI

• Version 2 of CTP Protocol shows on SCS GUI in the Tariff Profile, but Version
2 of the CTP Protocol is not supported. If Version 2 is chosen, CTP V1 is
performed.
8.4 VNC Client Support

• Some versions of VNC Unix Client Software are not compatible with the SCS
Client, which inhibits the SCS Client from opening.
o Supported Configuration
VNC Client using the 3.3 protocol – VNC Server for Win32 4.0
VNC Servers: vnc_sun4_sosV_5.5 and VNC 3.3.3r2 Binary
Distribution for Unix platforms
8.5 Telnet Sessions on the GGSN

• No more than 19 telnet sessions on the GGSN should be open at any one time.
8.6 Aggr APN Sessions can’t be Monitored on SCS Client

• PDP sessions, which are associated with services APN calls, can also be
monitored under Monitor---> ISP window. However, PDP sessions, which are
associated with Aggregation APNs, will not be reflected in the counters under
Monitor --->ISP window.
8.7 GGSN Ethernet Limitations

• CMC ports are not intended to carry traffic at the rate of a line card but rather are
for OA&M purposes.
• Multiple Ethernet connections with overlapping sub-nets for different ISPs are
supported with the following one restriction: The overlapping subnets must be
on different Ethernet ports (even being shared by the same EPIF). This
restriction is required for ARP and multicast forwarding.
8.8 Restrictions for the BGP/VLAN Feature Support

• With default config for overload if CMC3 P1 (routing processor) went into
overload with 100% CPU occupancy, Overload level indicated is normal and
takes 10 mins for the level to indicate level 3.
• ‘show overload cpu’ command shows 100% CPU for P1 even when the ‘show
cpu’ command shows 85% idle.
• When RADIUS server is inside VPN, during resync, Acct ON message is sent
from the ISP before BGP neighbor is up. Only after the BGP neighbor is
established, GGSN will get routes to the RADIUS server.
• When Ethernet port is configured with multiple ethernet access connections with
unique IP address. When sending data from a server in the subnet as the ethernet
access interface, there is no response (ethernet connection does not respond to
ARP requests). After initiating 1 ping packet from the GGSN ISP (through

90
VPN) to the same host, ping response is received and after that, data can be sent
from the server to the ethernet interface. An ARP request is sent by the server
but it does not get an ARP response.
• It takes 5 minutes (3x100 seconds) to get the GGSN into overload.
• When the BGP neighbor for the GGSN VPRN goes down, the BGP connection
for the VPRN is deleted after 120 to 160 seconds. Data from the mobile could be
forwarded through the VPRN for this duration.
• RADIUS Accounting-ON packets may be lost if the BGP neighbor has not been
established before Acct-ON packets are sent. This can be seen if there are more
than 120 VPRN's with BGP enabled are configured.
• Need to add summary routes for all contiguous address pool ranges from
RADIUS/ DHCP.
8.9 Billing Limitations

• Dropped packets due to TCP out of sequence scenario for postpaid billing and
CTP V1 billing will not be counted for billing.
• Dropped packets due to a Firewall policy will not be counted for billing.
8.10 GGSN Patching Limitation

When adding new patches (patch rules) to an active patch profile (patch profile
applied to the GGSN), users have an option to select multiple patches (patch
rules) from the Patch Select dialog window.
If a user selects multiple patches rules, the operation can result in failure to apply
most of the selected patches. This fact is communicated to the user via SCS
session errors.
8.10.1 Work-around
If the number of patch rules to be added to the active patch profile is 5 or less,
then:
1. From the Add Patch Rule dialog, set the Patch Rule Prefix.
2. Click the Select button. This will open the Patch Select dialog.
3. Select only one patch from the list and click OK.
Note: For Activatable patches, please select the appropriate patch Directive.
4. Click OK again to close the Add Patch Rule dialog.

5. Repeat the above steps to add the other patch rules.
If the number of patch rules to be added to the active patch profile is greater than
5, then:
1. Clone the active patch profile.

91
2. Add the new patches (as patch rules) to the clone patch profile. When
adding the patch rules, multiple patches can be selected from the Patch
Select dialog window if the profile is not applied to a GGSN.
3. To apply the added patches to a GGSN, swap the active patch profile for
that device with the clone patch profile under the Patch Manager's
Devices tab.
For detailed steps on GGSN patching, please refer to Nortel GGSN Provisioning
Procedures NTP: 411-5221-927.

92
9 OA&M
• This release introduces an additional line in the output of certain CLI commands. This
information is being provided in case customer utilizes downstream processing that has
rigid dependencies on the previous releases CLI output format.
The additional line is a time stamp, which has been added to enhance supportability.
This line appears as the first line in the CLI output when any of the following
commands are used:
4. Any show command
5. Any trace command
6. Any traceroute command
7. Any ping command
Example:
shasta-167(SSU)# show card
Wed 23-Aug-2006 10:40:25 CDT

SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup;
C - catching up; D - in delete
U - up; X - failed; '-' - disabled; * - not
present
M - failover move in progress;
v - uncommunicative; d - dumping core; L - loading
T - temporarily down
~ - spared overflow pool; ^ - spared failover
pool
ALC port states: U - up; D - down (alarm)
ELC/GELC port states: U /- up; D - down (link fail)
CT3/COC3 port states: + - up; '-' - down (alarm)
Slot Configured/Found Enabled Info

---- ----------------------- -------- -----
1 SSC /SSC Enabled U U U U
4 ALC /ALC Enabled D D D D [ICP Rev. 1.7]
5 ALC /ALC Enabled U U U U [ICP Rev. 1.7]
6 ELC /ELC Enabled U U U U U U U U
7 SFC /SFC Enabled 10G Active [FPGA Rev. 2.0]
8 SFC /SFC Enabled 10G Standby [FPGA Rev. 2.0]
9 GELC /GELC Enabled U [FPGA Rev. 0.5] [GBIC
Multi]
10 ELC /ELC Enabled U U U U U U U U
12 SSC /SSC Enabled - U U U
13 CMC /CMC Enabled Standby (Redundant)
14 CMC /CMC Enabled Active

93
• When the CLI commands reload, reboot, or shutdown are typed on the active or stand-
by CMC, the following event log will be displayed.
"System reloaded by task: cli (initiator: USER, how: 0x01, reload code: 2)"
When system is rebooted due to disk failure or software failure, the following event
log will be displayed.
"System reloaded by task: <task_name>(initiator: SYSTEM, how: 0x01, reload

code: 2)"
• Following overload messages have not been documented earlier:
1. INFO Overload: Resource memory has been enabled.

This is an event log to inform that the overload control has been enabled for
memory resource.
2. INFO Overload: Resource cpu has been enabled.
CPU usage.
3. INFO Overload: Resource interrupt has been enabled.
interrupt.
• Whenever the file descriptor count reaches a threshold value of 900 a new event log is
generated. This event log is not cleared. The event log will be as below:
25-Sep-2006 13:58:38 13/1/2:iSOS,0: 15, 1, CRITICAL, Number of Sockets has

reached 911
• Critical Hard Disk Failure Alarm event log has been added to inform the craftsperson of
a needed reset to possibly recover an uncommunicative hard disk:
"DISKMGR: Re-seat card in slot <slot>. ATA Controller Failure. Please
contact Nortel Product Support"
W-NMS support of this additional alarm starts with release OAM05.0.0.6.
W-NMS of a prior release ( OAM05.0.0.3, .4 or .5 ), will treat this alarm in GGSN5.0.1

as an “unknown alarm”.
• For SCP and DCC tasks, whenever the system file descriptors which are also used for
sockets, reaches a usage count threshold value of 900 a new event log is generated. This
event log is not cleared. The event log will be as below:
25-Sep-2006 13:58:38 13/1/2:iSOS,0: 15, 1, CRITICAL, Number of Sockets has

reached 911

94
• An event log is generated by the GGSN when the Simple Network Time Protocol
(SNTP) server sends a message containing a Leap Indicator(LI) equaling 3. Per
specification RFC 2030, a Network Time Protocol (NTP) header containing a LI value
of 3 signals an unhealthy server. The SNTP server has lost synchronization with its
clocking source. The GGSN will discard the message received from the server. An
example of the log follows:
Thu 12-Apr-2007 03:12:29 13/1/1:SNTP client 0 1 1 MINOR SNTP
server 2.191.21.62 unsynchronized
Remedial action must be taken on the SNTP server to clear up the issue
• During a GGSN resync or when a new standby CMC (CMC2 or CMC3) card is
inserted, the GGSN will generate a memory changed information alarm to indicate that
the standby CMC has sent it's information to the active CMC.
Thu 26-Apr-2007 00:32:17 14/1/1:CMC Manager 2 26 1 INFO Standby CMC CPU

memory size has been saved on the Active CMC.
On the Main Server, an alarm similar to the example below can be seen.
"GSNS-GGSNB|| | |500F0000|2007/04/26|00:32:17|CFDFF014|` Unknown SNMPv1
enterprise trap received; OID: 1.3.6.1.4.1.3199.10.28.2; Specific code: 23`
SMDR@mainsoama1` GMDR@mainsoama1" alarm.
This alarm does not have any service impact.
• The new counter SM.FailActPdpCtxt.NoResp.UDPThresholdReject has been

introduced in GGSN 5.0.1. This counter replaces the GGSN 4.1.1 counter
SM.FailActPdpCtxt.NORA.UDPThresholdReject.
• (Case: 070420-05121) The following INFO debug event log is for internal Nortel
information only and no action is required on the part of the Operator.
Fri 20-Apr-2007 14:45:19 13/1/1:DBG Manager 0 1 1 INFO DBGMSG_I:
The system time is being changed from Fri Apr 20 14:13:44 2007 to Fri Apr 20
14: 45:19

95
10 GGSN5.0.1 Known Issues
10.1 Known Issues with Planned Patches

Following are a list of known issues for which patches are under development.
Item # CR/Case Number Title

1
10.2 Known Issues Deferred to a Later Release.

Following are a list of known issues from prior releases that are deferred to a later release.
All these are minor issues that either do not have service impact or happen rarely. Titles are
linked to the specific description text that follows.
Item # CR/Case Number Title

1 Q01057908 SCS CORBA Should Use Specific Port
2 Q01271795 AAA RPC Timeout on Shasta Console
3 060321-80730/ Ancillary APN Statistics are not Reported in SCS Client
Q01388481
4 060322-82159/ Removing SFC Card Generates Alarm With Wrong Card Type
Q01388490
5 Q01364423 Old SSH Daemon
6 Q01125437-03 Critical Flag for the vxTicks Rollover After 414 Days
7 Q01419965 PDP Context to Change QoS is Rejected with Cause Value #C9
8 Q01256954 NTP Alarms and Logs have 22 Seconds Offset from GGSN System Time due to Leap Seconds
9 Q01416176 Error in SFC Upgrade to SFC2 Followed by CMC2 to CMC3
10 Q01415179 “netcli” Task Not Responding
11 Q01416166 All SSP Processor Load is High in Low Traffic
12 Q01421724 Maximum Number of Sessions Allowed for Shasta ("show sspmgr...") Incorrect
13 060620-79108/ SMNbrCtxtPrepaidToNoPrepCCNotApp Does Not Peg
060620-79108
Q01415964
14 Q01242539 Move snoop/unsnoop Command to Shastamode
15 Q01276698-01 SSC3 Unaligned Address Logs Generated
16 Q01248108-01 SCS Does Not Report a Warning that SSM is Dumping Core Files when SSM is Reset on the
SCS
17 060807-30268 “show fib” Command Crashes SSH Session
Q01437456-01
18 Q01368945 Show Policy Command Traps when the CBB Rule has Huge Amount of URL Rates
19 Q01438441 VLAN BGP VPN-P1 Remains at 100% CPU with No Activations
20 Q01309183-01 Radius Accounting: acct_terminate_cause Value Incorrect
21 Q01405536 No OSPF NSSA Type in the CORBA Script
22 Q01399606 IPSEC Policy Failed when Adding by CORBA Script
23 Q01445382 Inband ATM and Ethernet Quickstart Menu Validators have Bugs
24 Q01444455 VLAN BGP VPN-90% Memusage on CMC P0 for 145k Sessions
25 Q01371321-01 Port Speed Failure with 100 Full Duplex on CMC3
26 Q01413467 After Disabled Line Card and CMC Switch Conns and Subs have “cfgerror”
27 Q01449951 Incorrectly Allowing Auxiliary Ethernet Management to be Configured on CMC3
28 Q01426053 Traffic Shaper Policy Not Controlling Rate.
29 Q01414166 Issues with LAC & LNS Host Name in L2TP LAC Tunnel Configuration

96
30 Q01437759 GGSN Shasta Crash when "DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE" over

Gx
31 Q01415715 VLAN BGP VPN-Ethernet Access Interface Not Responding to ARP Requests
32 Q01257792 GGSN Not Reachable During Security Tests with Malicious Data GGSN not reachable / Traffic
limitation feature
33 Q01452583 SWERR Due to Long Delay of Entering Quickstart After "init config qs1"
34 Q01456293 “^C” Directory Created in /disk/config-Unable to Resync
35 060829-61111/ "netcli" Task Exception
Q01454341-01
36 Q01462283 VLAN BGP VPN-Option to Add Summary Routes for VPRN must be Added
37 Q01455174 Second Reporting Reason AVP Not Seen for Simultaneous Expiry QHT & Quota
38 Q01457222 setup.sh File in sslpkg.tar for Solaris must have Execute Permission.
39 Q01462200 OSPF Retransmission Interval of 1 Causes a Trap on CMC3
40 Q01449897 Management Interface Statistics for Multicast Packets are Incorrect
41 060320-80001/ All Fan Failure Caused Alarms aren’t Seen in SCS GUI
Q01388459
42 Q01456600 /tftpboot/patches Not created for New Install and Upgrade.
43 Q01465222 Upgrade Issues when $SCS_ROOT has install/bin Directory.
44 Q01471485 Switch SFC Causes OSPF Routing Problem on GGSN
45 Q01468365 "Trim User Name" password (Radius) Configured from SCS Not Sent to GGSN SSG.
46 Q01478125 IPC Issue may Cause RPC Timeouts
47 Q01447275 "HELP" on Accounting Billing Tab Does Not Show "exclude QCT"
48 Q01485201 Cannot Retrieve Session Details With IP Address
49 Q01451146 CORBA: Unit specified wrongly in "help" for "fltBillTimeLimit".
50 Q01493169 File Open Error During Startup
51 Q01455174-01 2nd Reporting Reason AVP not seen for simultaneous expiry QHT & quota
52 Q01415218 SCS only recognizes a new patch package when added for the first time
53 Q01596975 Corbashell CLI “create vprn” not working
54 Q01660775 “export config” does not work with uppercase config file parameter.
55 Q01617053 CMC3 dumps generated with wrong time
56 070828- "show card" CLI output for disabled Ethernet slot and port is incorrect
30631/Q01737685
57 070912-44775/ SCS Editing of Networks Objects Doesn't Save Changes
Q01745586
58 Q01755670 Session errors observed on the SCS after reposition FELC card on the GGSN
59 071004-66154/ Resync required after Reapplication of patch G501_01334913_DST
Q01759935
60 071211-27286/ Dynamic L2TP Tunnel selection not compliant with RFC2868
Q01801692
61 Q01618197-05/ 64 bit GGSN counters may roll over at 2^32-1
Q01618197-02
62 061024-22500/ Unknown “healthcheck” Commands During start-up
Q01489687
63 080218-84214/ Modifying Primary Diameter Server
Q01830205
64 080218-84214/ Problem with fallback from SSC3 to SSC2
Q01830205
65 Q01884435-01 Unable to copy GGSN image to /flash
66 080721-16197/ Erroreous Values of chargingIDs for CMC Reboot or Switchover

Q01903693
67 080604-78158/ Clarification on the Maximum Bit Rate Supported by Nortel GGSN5.0.1.
Q01911533

97
Detailed Description of Known/Deferred Items
Q01057908 SCS CORBA Should Use Specific Port

Description According to ports and services used by WMS4.2 NTP doc, sec 3.8: SCS
Server port usage, the recommended port for CORBA is >1023. There is
no specific port listed. It is requested that a specific port be used.
Impact No service impact. If the selected port is already in use, there will be
collision with other application ports.
Workaround Configure CORBA during installation to listen on a specific port.
Q01271795 AAA RPC Timeout on Shasta Console

Description AAA RPC time-outs are observed on the Shasta console. This can be
seen in following scenarios: An address pool is deleted and added or it is
modified.
Impact No service impact. The request to get the RADIUS server statistics and
the statistics for that interval will not be reported to the Log server.
However, the collection of statistics would resume normally for the next
interval of statistics collection.
Workaround None
060321-80730/ Ancillary APN Statistics are not Reported in SCS Client

Q01388481
Description Ancillary APN statistics are not presented to the SCS server
Impact No service impact. Can not view these statistics from the SCS.
Workaround The statistics can be viewed from the GGSN CLI.
060322-82159/ Removing SFC Card Generates Alarm With Wrong Card Type
Q01388490
Description When the standby SFC card is removed from the GGSN shelf, the trap
generated shows an incorrect card type.
Impact No service impact. The alarm is not cleared when the standby SFC card
is reinserted into the shelf.
Workaround Login to the SCS and manually clear the alarm

98
Q01364423 Old SSH Daemon

Description GGSN supports both SSH version 1 and version 2. SSH version 1 needs
to be disabled.
Impact No service impact. Currently SSH version 1 is also supported on
GGSN5.0.
Workaround N/A
Q01125437-03 Critical Flag for the vxTicks Rollover After 414 Days
Description The vxTicks counter used by many GGSN applications rolls over after
414.25 days uptime and may cause some issues on the GGSN. A critical
flag is required to warn the operators of an approaching 414 day uptime
deadline.
Impact Some of the SSMs will crash (if been up 414 days), while some others
will have a memory leak but stay up. These SSMs might crash under
heavy load.
- RPC timeouts from ifmgr (SSM ifmgr not responding to CMC ifmgr).
- CMC and some of the SSM CPU "total" statistics are incorrect.
Workaround Reload the GGSN to reset the clock.
Q01419965 Update PDP Context to Change QoS is Rejected with Cause Value #C9
Description The problem is seen when a PDP context with streaming class becomes
inactive, then the RNC will send a sccp RAB Release Request with cause
value of "User-Inactivity." It is expected to have the PDP context
preserved and the RAB gets released by sending RAB Release Command
from the SGSN. This causes the SGSN to send an update PDP context to
GGSN but GGSN rejects the update with cause value #C9.
Impact Streaming PDP session gets deactivated
Workaround None
Q01256954 NTP Alarms and Logs have 22 Seconds Offset from GGSN System
Time due to Leap Seconds
Description NTP Alarms and Logs have 22sec offset from GGSN system time. This
is the remaining issue from 22sec time leap related to POSIX compliant
servers. Only alarms and logs seem to be affected and there is no end-
user impact.
Impact No service impact. NTP Alarms impacted.
Workaround None

99
Q01416176 Error in SFC Upgrade to SFC2 Followed by CMC2 to CMC3

Description CMC2 to CMC3 upgrade fails after upgrading SFC1 to SFC2. “copy
image” does not work if SFC is upgraded prior to CMC.
Impact CMC2 to CMC3 upgrade fails.
Workaround Upgrade CMC2 to CMC3 first and then upgrade SFC1 to SFC2.
Q01415179 “netcli” Task Not Responding

Description netcli trap was generated. netcli is the task that manages CLI sessions.
Impact No service impact since netcli is not a critical task.
Workaround N/A
Q01416166 All SSP Processor Load is High in Low Traffic

Description With little or no traffic running on the GGSN, the SSP load was around
30 to 40% although the CMC processor load remained fairly low (around
6%)
Impact No service impact.
Workaround N/A
Q01421724 Maximum Number of Sessions Allowed for Shasta Incorrect

Description When issuing the command "show sspmgr rm detail", the maximum
number allowed for the whole GGSN doesn't add up correctly.
Impact No service impact. Incorrect CLI output.
Workaround None
Q01415964 SMNbrCtxtPrepaidToNoPrepCCNotApp Does Not Peg.

Description In case of CCA with result code "Diameter Credit Control Not
Applicable" the counter
SM.NbrCtxtPrepaidToNonPrepaid.CCNotApp.Apn didn't peg.
Impact No service impact. Can not identify number of CCAs with result code
"Diameter Credit Control Not Applicable".
Workaround None

100
Q01242539 Move snoop/unsnoop Command to Shastamode

Description The GGSN NTP's refer to a base troubleshooting guide that describes the
usage of the snoop command in detail. This should be moved to
shastamode.
Impact If a snoop/unsnoop command is used on a live site, an outage will occur
resulting the total loss of traffic.
Workaround Do not use snoop/unsnoop commands in live network.
Q01276698-01 SSC3 Unaligned Address Logs Generated
Description During a traffic run some SSC3 unaligned address logs are generated
Impact No service impact. This log is only for informational purpose.
Workaround None.
Q01248108-01 SCS Does Not Report a Warning that SSM is Dumping Core Files
when SSM is Reset on the SCS
Description SCS does not report a warning if SSM is dumping core when trying to
reset the SSM on the SCS.
Impact No service impact. If the user resets the SSM while it is dumping core,
the incomplete core will hinder root cause analysis for the reset.
Workaround Check the status of the SSM on the GGSN.
Q01437456-01 “show fib” Command Crashes SSH Session

Description The use of "show fib" under a SSH session crashes the SSH session.
Impact No service impact. Will loose the connection that uses SSH.
Workaround None
Q01368945 Show Policy Command Traps when the CBB Rule has Huge Amount
of URL Rates
Description The show policy command traps when the CBB rule has 512 URL rates
in the policy.
Impact No service impact. The trap kills the CLI window by disconnecting from
the device.
Workaround Reestablish telnet session to the GGSN.

101
Q01438441 VLAN BGP VPN-P1 Remains at 100% CPU with No Activations

Description ‘show overload cpu’ command shows 100% CPU for P1 even when the
‘show cpu’ command shows 85% idle.
Impact No service impact. Incorrect information given leading to confusion..
Workaround None.
Q01309183-01 Radius Accounting: acct_terminate_cause Value Incorrect

Description For DHCP Relay session with Radius Acct, GGSN is incorrectly
populating the acct_terminate_cause value as '0'. As per RFC 2866, value
'0' is not a defined value.
Workaround None
Q01405536 No OSPF NSSA Type in the CORBA Script

Description The NSSA type in CORBA script for OSPF routing configuration is not
valid.
Impact No service impact. Can not create OSPF configuration using CORBA
script.
Workaround Configure NSSA type in the SCS GUI
Q01399606 IPSEC Policy Failed when Adding by CORBA Script

Description After configuring the IPSEC policy by using the CORBA script, the
policy and rules are showing on the SCS GUI but when the IPSEC call
was made, an error is showing on the Debug.
Impact IPSEC calls fail.
Workaround The user has to login the SCS GUI and open up the IPSEC policy.
Click each rule and save it

102
Q01445382 Inband ATM and Ethernet Quickstart Menu Validators have Bugs.
Description When a value is given in ATM management interface field and ATM
management interface IP address is empty, it displays an error ”Invalid
IP prefix for auxiliary management interface“ but still configures it.
When Ethernet management interface field is empty and an IP
address is given in Ethernet management interface IP address field, it
doesn’t display any error but doesn't configure it also.
When ATM management interface is empty and an IP address is
given in ATM management interface IP address field, it doesn't
display any error and configures it.
Impact No service impact. GGSN does not display error messages.
Workaround None.
Q01444455 VLAN BGP VPN-90% Memusage on CMC P0 for 145k Sessions

Description VLAN BGP VPN shows 90% memusage on CMC P0 for 145k sessions.
Impact None.
Workaround None.
Q01371321-01 Port Speed Failure with 100 Full Duplex on CMC3

Description Management port hangs when the speed is set to 100 Full Duplex on both
sides.
Impact No service impact. Loss of management connectivity.
Workaround Set the port setting to autosense but it only works at 100 Half Duplex.
Q01413467 After Disabled Line Card and CMC Switch Conns and Subs have
“cfgerror”
Description When the Gn and the Gi line cards with the GUI are disabled and after a
CMC switchover from CLI is performed the line card remained in
disabled state. When it was enabled from the GUI the card came up, but
all connections were in down state and subscribers had config error.
Impact During recovery we have 4-5 min outage.
Workaround Resync or do a second CMC switchover.

103
Q01449951 Incorrectly Allowing Auxiliary Ethernet Management to be Configured

on CMC3
Description CMC3 has only 1 port. However, GGSN allows the configuration of
Auxiliary Ethernet management interface on CMC3.
Impact No service impact. After adding Aux Ethernet port to CMC card, user is
no longer able to telnet to GGSN via regular (primary) Mgmt interface.
User can only login to GGSN via the console port.
Workaround Login via Console and disable new auxiliary Ethernet management
interface.
Q01426053 Traffic Shaper Policy Not Controlling Rate.

Description To limit line rates the rate is set to 32 Bytes/second. After a couple of
minutes the traffic shaper wasn't used and messaging flowed at normal
rate.
Impact Packets are allowed at higher rate and not dropped.
Workaround N/A
Q01414166 Issues with LAC & LNS Host Name in L2TP LAC Tunnel
Configuration
Description 1. When either "LAC Host name" or "LNS Host name" is changed
(modified), all PDP Context sessions associated with that APN (L2TP
tunnel) are deleted without issuing a warning message.
2. SCS GUI does not allow empty name with error message. However,
when just space(s) is entered, GUI takes it. But blank or empty name is
invalid.
Impact All subscribers on the L2TP tunnel are dropped.
Workaround None
Q01437759 GGSN Crash when

"DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE" over Gx
Description GGSN crash (core) when
"DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE" result code
in CCA sent over Gx interface. GGSN handles the same message on Gy
interface with out any issues as expected. This code is intended only for
Gy or Gx/Gy.
Impact Loss of billing and service outage.
Workaround Do not configure diameter to send this code on only Gx interface.

104
Q01415715 VLAN BGP VPN-Ethernet Access Interface Not Responding to ARP

Requests
Description When Ethernet port is configured with multiple Ethernet access
connections with unique IP addresses the data transfer from a server in
the same subnet as the Ethernet access interface may not be possible. The
reason for this behavior is that Ethernet connection does not respond to
ARP requests. After a successful round trip of a ping packet from the
GGSN ISP (through VPN) to the same host, data can be sent from the
server to the Ethernet interface.
Impact GGSN maybe unreachable until an ARP response is sent out.
Workaround Ping from the ISP through VPN to the server.
Q01257792 GGSN Not Reachable During Security Tests with Malicious Data
Description The GGSN is not reachable during load tests with normal and malicious
data. The GGSN was stable, but the administrative interfaces are not
reachable during test from another machine.
Impact No service impact. The GGSN is not reachable for the operator anymore.
Workaround N/A.
Q01452583 SWERR Due to Long Delay of Entering Quickstart After "init config
qs1"
Description SWERR is seen after entering quickstart information from console
during the reboot.
Impact No service impact. This SWERR is a traceback for debugging purposes.
Workaround N/A

105
Q01456293 “^C” Directory Created in /disk/config-Unable to Resync

Description On the GGSN, there a ^C directory created in /disk/config. Customer is
not sure if ^C directory can be created in 5.0.1 MAINTENANCE GGSN
load. The GGSN has CMC3 card.
Impact No service impact. When ^C directory exists in /disk/config, init config
primary is not possible even when the GGSN load is 5.0.1. So resync will
not be possible.
Workaround To recover
1. ^C needs to be deleted from both active and standby CMC:
cd /disk/config
cd "^c"
remove file *
cd ../
remove file "^c"
2. Perform a CLI reboot
reboot
3. When GGSN comes back up, perform:
init config primary
4. Perform resync
If init config primary does not work, then the user will need to revert
to 5.0/ 4.1 and repeat the above steps.
Q01454341 "netcli" Task Exception

Description Software exception in “netcli” task was observed on GGSN event log.
Impact No service impact. “netcli” is not a critical task and restarts itself.
Workaround N/A

106
Q01462283 VLAN BGP VPN-Option to Add Summary Routes for VPRN must be
Added
Description Option to add summary routes from SCS for VPRN must be added.
Impact CMC P1 goes into overload .
Workaround Have an address pool with matching subnet mask for the VPRN
Q01455174 Second Reporting Reason AVP Not Seen for Simultaneous Expiry
QHT & Quota
Description Quota & idle timer expire simultaneously when QHT=QCT then the
Reporting Reason is only observed for IDLE TIMER expiry and not
QUOTA EXHAUSTED.
Workaround None.
Q01457222 setup.sh File in sslpkg.tar for Solaris must have Execute Permission.
Description setup.sh file packaged with sslpkg.tar.Z file must have execute file
permission by default but does not.
Impact No service impact. setup.sh in sslpkg.tar can not run.
Workaround User must set execute file permission for setup.sh.
Q01462200 OSPF Retransmission Interval of 1 Causes a Trap on CMC3

Description If the OSPF Retransmission Interval is configured as 1 when the GGSN
is equipped with CMC-3 cards causes a trap and CMC switchover.
Impact CMC switchover.
Workaround Configure the OSPF Retransmission interval greater than 1.
Q01449897 Management Interface Statistics for Multicast Packets are Incorrect

Description The interface statistics for the management ports are incorrect for
received multicast packets.
Impact No service impact. No multicast packets statistics on management ports.
Workaround None.

107
Q01388459 All Fan Failure Caused Alarms aren’t Seen in SCS GUI
Description Could not see a Fan Dead alarm reported in the Alarm Manager GUI of
the SCS Client when the fan was pulled out of the GGSN.
Impact Not all alarms regarding fan failure are reported to the SCS.
Workaround None.
Q01456600 /tftpboot/patches Not Created for New Install and Upgrade.

Description /tftpboot/patches is not created for both new install of SCS 5.0.1 and on
upgrade.
Impact No service impact. Without this directory, SCS Patch Manager will not
be able to accept patches and apply patches to GGSN.
Workaround Manually create the /tftpboot/patches.

108
Q01465222 Upgrade Issues when $SCS_ROOT has install/bin Directory.

Description While performing a SCS 5.0.1 or 5.0.2 upgrade, if the current SCS
(4.x.x/5.0.1) installation directory has 'install' directory, this gets copied
over to $SCS5.0_ROOT (for SCS 5.0.1 or 5.0.2) during rollingSCS.sh
step. 'install' directory has all the installation files needed for 5.0 and will
be overwritten by the old SCS 'install'.
Impact No service impact. SCS upgrade fails.
Workaround Verify the current SCS installation directory and remove install, setup.sh
and rollingSCS.sh scripts if present before the installation
Q01471485 Switch SFC Causes OSPF Routing Problem on GGSN

Description After a couple of SFC card switch (command “switch sfc”) OSPF routes
are missing.
Impact It was not possible to make PDP context any more.
Workaround None.
Q01468365 "Trim User Name" password (Radius) Configured from SCS Not Sent
to GGSN.
Description "Trim User Name" password (Radius profile) configured from SCS is not
sent to the GGSN properly.
Impact No service impact. “Trim User Name” is not currently used on GGSN.
Workaround Set password same as APN name on RADIUS server.

109
Q01478125 IPC Issue may Cause RPC Timeouts

Description When a synchronous RPC is sent from CMC to SSP, in a rare scenario
the incoming RPC messages on CMC can be queued up but the task may
not process them immediately.
Impact This may potentially cause a delay in processing the RPC messages.
Workaround None.
Q01447275 "HELP" on Accounting Billing Tab Does Not Show "exclude QCT"
Description The Help window does not show “help” description for “Exclude QCT”
checkbox.
Workaround None.
Q01485201 Cannot Retrieve Session Details With IP Address

Description “show gtp session <isp> <vpn> <ip>” does work when trying to
retrieve session information for the ip address.
Impact No service impact. Session information of a VPN subscriber can not be
retrieved.
Workaround Session details can be retrieved using SCS.
Q01451146 CORBA: Unit specified wrongly in "help" for "fltBillTimeLimit".

Description CORBA shell command "modify gtp device ?" displays help. The unit
for FTB Time limit is wrongly specified as Kbytes. Needs to be changed
to "minutes".
Impact System help display value misleading.
Workaround None.

110
Q01493169 File Open Error During Startup

Description During startup, the following error can be seen once:
AAA Manager 0 25 1 CRITICAL AAA: initRadpFile-<926>: Error
0x380003 reported while performing disk operation FOPEN on
/disk/acct/radius/profile/PROFIND.050
Impact None. This is normal, because the file:
'/disk/acct/radius/profile/PROFIND.050'
does not exist yet. At this time, we initialize the Radius Acct disk profile
file by creating the "/disk/acct/radius/profile/PROFIND.050" file for the
first time. The file will be created next.
If the Error code is not 0x380003 or the line number is different from 926,
then it can be a real error.
Workaround None.
Q01455174-01 2nd Reporting Reason AVP not seen for simultaneous expiry QHT &
quota
Description If THRESHOLD or QUOTA_EXHAUSTED occur at the same time as
one of the Multiple-Services-Credit-Control level Reasons, then the
Reporting-Reason AVP shall be included both at the MSCC level and in
the Used-Served-Units AVP.
Impact Incomplete billing record generated.
Workaround None.
Q01415218 SCS only recognizes a new patch package when added for the first time
Description SCS only recognizes a new patch package when it is added to the system
for the first time. At that time the the information of this patch package
will be persistent with the SCS. Any later changes in the same patch
package will not be recognized or identified by the SCS. For example, if
the customer removes and then adds the exact same patch package, the
SCS will not identify the latest version as a new patch package. The SCS
will not inform the customer to update the system and it will only keep
the information from the first time it recognized this package. Also, if
there are two different versions of the same patch package, the SCS only
recognizes the higher version.
Impact Customer can not delete and add the same patch package or manage
patches with the older version of a patch package.
Workaround None.

111
Q01596975 Corbashell CLI “create vprn” not working

Description NTP 411-5221-929.03.03 titled “GGSN Corbashell CLI Guide”
documented syntax parameter for create vprn is not consistent with the
response of the software. The last parameter should be
“vprn_encap_type”, not “vprn_type”.
Impact Provisioning via corbashell will fail.
Workaround Modify corbashell scripts with correct parameter identification.
Q01660775 “export config” does not work with uppercase config file parameter.
Description The error, “Configuration export failed: Success” is displayed when not
entering in all lower case “qs1”, or “primary” as the configuration
database names to the export config CLI command.. Also, not all the file
contents are stored in the selected text file. For example the command
“export config config=QS1 outfile=testqs1” will result in this error. The
command “export config config=qs1 outfile=testqs1” will work correctly.
Impact Can not save configuration files to text files.
Workaround When using the “export config” command use in all lower case the
database configuration names.
Q01617053 CMC3 core dumps generated with wrong time

Description The CMC core file time stamp will not match site time if a timezone is
set (regardless of whether NTP is in use).
Impact This is a day one issue. The timestamps for CMC core files will be off by
a few hours (if a timezone is set on the GGSN). However, both the event
logs on the GGSN and the core files themselves contain the exact time of
the crash, so there is no impact on crash analysis based on the core files.
Workaround None.
070828-30631/ "show card" CLI output for disabled Ethernet slot and port is incorrect
Q01737685
Description When an active Ethernet cable is plugged into a disabled FELC port, the
"show card" output on the GGSN shows the port status as "UP".
Impact No service impact. The port status on the GGSN is displayed as UP
though the port is disabled on the SCS.
Workaround From the SCS client, modify the administrative status of the FELC port to
UP, then click OK. Modify the administrative status of the FELC port
back to Down, click OK. The CLI output will indicate the port as
disabled.

112
070912-44775/ SCS Editing of Networks Objects Doesn't Save Changes

Q01745586
Description In the SCS GUI under Service Policies -> Service Objects -> Network
Objects, if a change is made to an existing "Network Object" the change
is not always saved after selecting "OK".
Impact Network object changes will be lost without displaying a warning to the
user.
Workaround From any service policy using the "Network Object" perform the required
changes to the object and then save the policy. The "Network Object"
changes are then saved successfully
Q01755670 Session errors observed on the SCS after reposition FELC card on the
GGSN
Description Inserting a new FELC card into a non high density slot (green colour on
the chasis) will result in session errors on the SCS for ports 5 through 8.
Impact No service impact, other than the session errors.
Workaround Performing a resync on the GGSN will allow the SCS to correctly
configure the FELC card to contain 4 ports instead of 8 in a non high
density slot.
071004-66154/ Resync required after Reapplication of patch G501_01334913_DST

Q01759935
Description Western Australia DST changes were delivered by the patch
G501_01334913_DST. The changes will not be effective if the patch is
removed and re-applied after initial application.
Impact The transition to and from the DST time will not happen at the correct
times.
Workaround Perform a resync after the patch G501_01334913_DST is re-applied to
ensure DST changes happen at the correct time.
071211-27286/ Dynamic L2TP Tunnel selection not compliant with RFC2868

Q01801692
Description When a Tunnel-Server-endpoint is changed on the RADIUS server
without modifying the corresponding Tunnel-assignment-Id, the L2TP
tunnel selection is done incorrectly. Calls are still established to the old
Tunnel-server-endpoint.
Impact Call failure since GGSN attempts to setup the call to the old LNS server
address.
Workaround GGSN expects the Tunnel-assignment-ID(tunnel name) to be unique for
each Tunnel-server-endpoint for a given ISP. The RADIUS server needs

113
to be configured to return a unique Tunnel-assignment-ID for each LNS

server address.
Q01618197-05 64 bit GGSN counters may roll over at 2^32-1

Description The following 64 bit counters can roll over when their values reach
2^32 - 1 (4294967295) on GGSN’s equipped with CMC3 or SSC3 card
types. This issue affects both the counters displayed via CLI commands
and those spooled to the SCS.
Trunk Stats: (CLI: show interface name=<interface>)
ifi_ipackets
ifi_opackets
ifi_ibytes
ifi_obytes
ifi_imcasts
ifi_imcastbytes
ifi_omcasts
ifi_omcastbytes
ifip_implspackets
ifip_omplspackets
ifip_implsbytes
ifip_omplsbytes
Device Stats:
ssp_driver_pkts_rcvd
cmc_driver_pkts_rcvd
encrypt_pkts_processed
ISP Stats:
ips_total
ips_out_pkt
inc_data_oct
out_data_oct
APN Data Stats:
(CLI: show stats hist apndata isp=<gi_isp_name> apn=<apn_name>)
IncDataPkt
OutDataPkt
IncDataOct
OutDataOct
GTP Data Stats: (CLI: show stats hist gtpdata isp=<gn_isp>)
All counters
IPSEC Stats: (CLI: show stats hist ipsec isp=<ipsec_isp>)
ipsecOctetsRECV
ipsecOctetsSENT
ipsecPktDISC
ipsecPktRECV
ipsecPktSENT
L2TP Stats: (CLI: show stats hist l2tp isp=<l2tp_isp>)
L2tpOctetsRECV
L2tpOctetsSENT
L2tpPktDISC
L2tpPktRECV
L2tpPktSENT
GRE Stats: (CLI: show stats gre isp=<gre_isp>)

114
GreOctetsRcvd (not displayed on CLI)

GreOctetsSent (not displayed on CLI)
GrePktsRcvd
GrePktsSent
GrePktsDiscMem
GrePktsDiscTunl
GrePktsDiscRte
GrePktsDiscProto
GrePktsDiscSR
GrePktsDiscBadsum
GrePktsDiscBadkey
GrePktsDiscSeqPres
GrePktsDiscNoIFP
GrePktsDiscIPQFull
MPLS Stats: (CLI: show stats hist mpls isp=<mpls_isp> vrf=<vrf_name>)
mpls_OctetsRcvd
mpls_OctetsSent
mpls_PktsRcvd
mpls_PktsSent
Impact Statistics impacted if the GGSN is equipped with SSC3 cards or CMC3
cards.
Workaround None. Issue resolved in GGSN 6.0 (Q01618197-02).
061024-22500/ Unknown “healthcheck” Commands During Start-up

Q01489687
Description The CLI healthcheck commands to monitor profiles in GGSN 4.1.1 were
removed and new ones were created in GGSN 5.0.1. Therefore, the
GGSN 4.1.1 healthcheck commands will fail during start up after
upgrading from GGSN 4.1.1 to GGSN 5.0.1 and subsequent GGSN
resync..
Following is an example from the event log display that reports the issue:
Tue 24-Oct-2006 11:32:06 13/1/1:CONFIG 0 10 1 MINOR Command 'set
healthcheck network-threshold 90' failed: cli: Unknown Command
Tue 24-Oct-2006 11:32:06 13/1/1:CONFIG 0 10 1 MINOR Command 'set

healthcheck nodal-threshold 95' failed: cli: Unknown Command
Tue 24-Oct-2006 11:32:06 13/1/1:CONFIG 0 10 1 MINOR Command

'enable healthcheck' failed: cli: Unknown Command
Details on the healthcheck command differences between GGSN 4.1.1

and GGSN 5.0.1 are included below:
GGSN 4.1.1:
set healthcheck
usage: set healthcheck nodal-threshold
[threshold=]<success_threshold>
usage: set healthcheck network-threshold
[threshold=]<success_threshold>

115
GGSN 5.0.1
set healthcheck
usage: set healthcheck [profile =]<profile>
[healthcheck_enabled=]{yes,no}[network_threshold=]
<network_threshold> [nodal_threshold=]<nodal_threshold>
[att_acts_threshold=]<att_acts_threshold>
Impact These errors should be ignored.

Workaround None. Issue resolved in GGSN 6.0 (Q01489687).
080218-84214/ Modifying Primary Diameter Server

Q01830205-01
Description In an ISP spanning configuration (1 ISP is configured with mulitple
GGSN's), on a Diameter Profile for the ISP, SCS client will not permit
the following configuration.
Here is an example, ISP A is configured with GGSN A and GGSN B.

Servers 1.1.1.1 and 2.2.2.2 are configured on the Diameter Profile.
Diameter Profile on ISP A:

Server Is Primary GGSN
1.1.1.1 Yes GGSN A
No GGSN B
2.2.2.2 No GGSN A
Yes GGSN B
The error returned on the SCS client when adding this configuration is
"Only one primary server is allowed for one profile".
Impact SCS client will not permit one DCC server to be the primary server on
GGSN A and another DCC server to be the primary on GGSN B.
Workaround User can assign each GGSN with a primary server as long as it is within
the same server address.
If the active server needs to be switched:
1. Edit the Diameter Profile-> Servers-> Select the diameter server
assigned currently as Primary-> Select the GGSN-> Uncheck the
'Primary' checkbox. Repeat this step for all GGSN's.
2. Select the diameter server to be active-> Select the GGSN->
check 'Primary'. Repeat this step for all GGSN's.
Issue resolved in GGSN 6.0 (Q01830205).

116
080513-60317/ Problem with fallback from SSC3 to SSC2

Q01874195
Description During a SSC3 -> SSC2 downgrade procedure, the command

"gtpbill flush billing isp=<Ga ISP>" is issued as mentioned in the
Hardware NTP 411-5221-923.
The CLI display is stuck with the values below:
"Bulk Update In Prog: Yes"

"Outstanding SSP Reps: 32 "
The above example is for a 4 SSC card line up

(4 SSC x 4 SSM x 4 SSP = 64 SSP processors).
Impact User will not know when the GTP billing information have been flushed.
Workaround The problem happens due to a minor software bug. SSC3 cards have 2
SSP's per SSM, while SSC2 cards have 4 SSP's per SSM. The software is
calculating the Outstanding SSP Reps with SSC2 cards at 64. So the
command will never complete with SSC3 cards, as there are only 32
SSP's. When the Outstanding SSP Reps is 32, the command is essentially
finished and customer may continue at that point.
Q01884435-01 Unable to Copy GGSN5.0.1 Image to CMC-2 /flash
Description The CMC-2 flash storage has limited capacity of about 48MB. The
GGSN5.0.1 image size is around 47MB. The copy fails since the disk
does not write the image from the netcli task to /flash if it has reached a
critical threshold disk capacity of 72%.
Impact Cannot boot GGSN5.0.1 image from CMC-2 /flash.
Workaround CMC-2 /flash can be used for the base image ISN to provide card access
in case of disk failure. The /flash has been eliminated from the next-
generation CMC-3 as disk operation is deemed reliable.
080721-16197/ Erroreous Values of chargingIDs for CMC Reboot or Switchover

Q01903693
Description In NTP 411-5221-926 Version 10.40 (or higher) Nortel GGSN User
Guide -> Section Functional description -> GTP accounting ->
Accounting record generation -> G-CDR identification, erroreously
states that “The frequency of the Charging ID file update is every
600,000 charging IDs used”, and that “A 32-bit Local Record Sequence
Number is then immediately incremented by a value of 300,000”.

117
Original Erroneous Text:

“To ensure uniqueness in the event of a system failure, the last used
chargingID is periodically stored to non-volatile storage on both active
and inactive CMC cards. The frequency of the Charging ID file update is
every 600,000 charging IDs used. In the event of a CMC reboot or
switchover, the newly active CMC will read the values from the file on
local disk. A 32-bit Local Record Sequence Number is then immediately
incremented by a value of 300,000. This value is then immediately
written back to the file on disk and also sent to the inactive CMC.”
Impact The erroneous text gives the customer an impression that the uniqueness
of the values of ChargingIDs is not properly maintained for CMC reboot
or switchover.
Workaround Update the release notes to state the correct text as shown below:
To ensure uniqueness in the event of a system failure, the last used

chargingID is periodically stored to non-volatile storage on both active
and inactive CMC cards. The frequency of the Charging ID file update is
every 300,000 charging IDs used. In the event of a CMC reboot or
switchover, the newly active CMC will read the current value of the
Charging ID from the file on local disk. This value is then immediately
incremented by 600,000, written back to the file on disk, and also sent to
the inactive CMC.
080604-78158/ Clarification of the Maximum Bit Rate Supported by Nortel

GGSN5.0.1
Q01911533
Description In NTP 411-5221-926 Version 10.40 (or higher) Nortel GGSN5.0.1 User
Guide -> Functional description -> Section 3-22 -> HSDPA Parameters,
information on Maximum Bit Rate may be misleading.
Original Text:
“Nortel Networks GGSN receives the new HSDPA values in the Quality
of Service (QoS) parameter IE. HSDPA parameters in the QoS IE are
optional parameters. When a QoS parameter is sent with Rel 5 QoS
parameters, then the first 12 octets are sent as the negotiated R99 QoS
parameters. If octet Maximum bit rate for downlink (extended) or
Guaranteed bit rate for downlink (extended) is received with a value
greater than 0x4A, Nortel Networks GGSN returns a value of 0x4A in
the response.”

118
Impact The original text underlined above on Maximum Bit Rate may give
customer a wrong impression that Nortel GGSN is not in compliance
with the 3GPP TS.
Workaround Update the release notes to clearly state that Nortel GGSN in it's PDP
activation response QoS field returns the same QoS it receives in the
activation request message and that the data rate limits are as listed in in
3GPP TS 24.008 Version 5.8.0 are enforced.

119
11 Active CABs
CBS CAB # Title Comments
2006007102 BGP Prefix-list not being loaded after switchover of CMC Card
2006007026 CMC-3 Management Port Configuration Recommandations
CMC-3 Trap and Switchover When OSPF Retransmission Interval Is
2006007476
Configured As a Value of 1 Second
2006007540 2007 Daylight Saving Time changes for the GGSN
2006007704 CMC switchover may lose pre-existing CGF profile
2007007717 SFC Switchover Causes Failed Connections
2007007716 Show Policy Command May Suspend Tasks
2007007732 Script setup.sh failed during upgrade SCS to 5.0.2
GGSN SSM's May Trap Following Daylight Savings Time Change Due
2007007824
To Prepaid Absolute Lifetime Configuration
Flow Management Policy Activation Procedure to prevent Flow Cache
2007007825
Exhaustion due to Virus/Worm Attacks
Identification of Virus/Worm Infected Ports and Activation of Firewall
2007007826
Security Service Policy
GGSN: G501_01341393A_ACCT and G50_01341393_ACCT Forward
2007007839
Patch Dependencies
2007007769 2007 Daylight Saving Time changes for the GGSN SCS
2007007816 Unexpected Patch Profile Update While SCS Device Configuration
2007008017 After Upgrade, "Show Socket" Command Shows TCP Ports In Status
"Close_Wait"
2007008016 IP Address Pool Modification in Traffic can Cause CMC Switchover
2007007839 G501_01341393A_ACCT and G50_01341393_ACCT Forward Patch
Dependencies
2007007938 Usage of "snoop" and "unsnoop" CLI commands will cause an outage
2007008429 Introducing GGSN Data Collector
2007008323 SCS session errors may occur following SFC2 upgrade
2007008266 ISP Node Firewall Policy can Cause RADIUS Responses to be Dropped
2008008932 VxWorks Counter Roll-over Issue
2008009192 GGSN Patching Limitation

120
12 Appendix A: VLAN BGP VPN Call Model

The advantage of this call model is static reachablities need not be maintained on the GGSN
or at the far-end of the VPN. BGP routing protocol dynamically updates route changes
between the GGSN and the far-end VPN router.
In this call model, the GGSN connection ISP can be connected to an MPLS Provider Edge
(PE) router with a VLAN access connection. BGP routing is enabled on the VLAN access
subscriber. This particular BGP implementation is called Exterior BGP (eBGP) where the
GGSN and the BGP neighbor are in different Autonomous systems (AS).
With this topology, all VPN routes that are learned from the GGSN and from the respective
CE-VPN-network will be advertised across the MPLS backbone using the existing MPLS
iBGP session between the PE-routers or route reflectors.
Configuration on GGN:
To configure this call model on the GGSN please refer to the Nortel GGSN Provisioning
Procedures (NTP 411-5221-927), Section 5-55 “Configure VLAN eBGP VPN”.
VLAN BGP VPN Recommendations:

For a list of known issues and recommendations for this call model please refer to Nortel
GGSN Provisioning Procedures (NTP 411-5221-927), Section 5-77 “Restrictions”.

121
13 Appendix B: Previous Patch Package Instructions

Alert: An important alert has been added to Nortel GGSN5.0.1 NTP 411-5221-927 -GGSN
Provisioning Procedures - Appendix B: “GGSN Patch Application” - Section “ Procedure to
update Patch Package” regarding the pre-requisite procedure described in Step 8 of Section
“Patching Prerequisites”.
Note: Step 8 of Section “Patching Requisites” must be executed on the SCS server
prior to the application of a new patch package. A restart of the SCS server processes
is also required. However, if the pre-requisites step has already been performed during
previous patch package application, you don’t need to do it again.
Please download the latest Provisioning Procedure NTP (v09.17 or higher).
13.1 Patch Package Application Instructions for Patch Package 3

Patch profile cloning is the preferred method of patch package application. In this method,
the active patch profile (the patch profile applied to the GGSN) is cloned to create a new
patch profile. Patch package 3 patches and any EMG patches listed in
Table 1 are added to this clone patch profile. The clone patch profile is then swapped with
the active patch profile.
For detailed instructions, please refer to Nortel GGSN 5.0.1 NTP 411-5221-927 GGSN
Provisioning Procedures –Appendix B, “Procedure to update Patch Package”.
recommended to avoid running FTP to the GGSN during patch package application. Also,
disable any auto FTP scripts that may FTP files from the GGSN.
It is recommended to apply the patch package during a maintenance window to avoid

impact of call processing.
A few patches within patch package 3 require special handling. Please refer to section
Patches Requiring Special Handling for Application or Removal for a summary of the
special handling requirements for these patches.
Application and unapplication of patch package 3 requires:
• All PDP contexts on the GGSN be deleted and traffic disabled.

• A GGSN resync.
• Enable traffic back on the GGSN.

122
For detailed instructions, please refer to Nortel GGSN 5.0.1 NTP 411-5221-923 Hardware
Installation and Maintenance Guide - section “Manual GGSN shutdown, resync, or CMC
switchover”
13.2 Patch Package Application Instructions for Patch Package 4
Application of patch package 4 does not require a GGSN resync. A few patches within
patch package 4 and new EMG patches require special handling. Please refer to section
Patches Requiring Special Handling for Application or Removal for a summary of the
special handling requirements for these patches.
Patch profile cloning is the preferred method of patch package application. In this method,
the active patch profile (the patch profile applied to the GGSN) is cloned to create a new
patch profile. Patch package 4 patches and any EMG patches listed in
Table 1 are added to this clone patch profile. The clone patch profile is then swapped with
the active patch profile.
For detailed instructions, please refer to Nortel GGSN 5.0.1 NTP 411-5221-927 GGSN
Provisioning Procedures –Appendix B, “Procedure to update Patch Package”. Please
download the latest Provisioning Procedure NTP (v09.17 or higher).
recommended to avoid running FTP to the GGSN during patch package application. Also,
disable any auto FTP scripts that may FTP files from the GGSN.
Warning: It is recommended to apply the patch package during a maintenance window to

avoid impact of call processing.
Warning: When a patch profile with a combination of patch package 1, 2, 3 and 4 is

unapplied and reapplied:
• All PDP contexts on the GGSN must be deleted and traffic disabled.
• Unapply (or reapply) the patch profile with the patch packages.
• Perform a GGSN resync.
• Enable traffic back on the GGSN.
For detailed instructions to disallow traffic and enable traffic after resync, please refer to
Nortel GGSN 5.0.1 NTP 411-5221-923 Hardware Installation and Maintenance Guide -
section “Manual GGSN shutdown, resync, or CMC switchover”
13.3 Application and Removal Instructions for Patch Package 5

123
13.3.1 Warnings and Notes
The latest package for GGSN5.0.1 release is patch package 6. Prior to application of patch
package 6, it is assumed that the node is patch current to patch package 5 i.e. all applicable
patches from package 1 through 5 plus EMGs are applied on the node and with all
dependencies resolved. If the node baseline is not at patch package 5, the instructions to
apply patch package 6 may vary.
recommended to avoid running FTP to the GGSN or executing any other CLI commands on
GGSN during patch package application. Also, disable any auto FTP or CLI scripts that
may FTP files from the GGSN.
Warning: Always apply patch package 5 patches during a maintenance window. DO NOT
apply patch package 5 patches with traffic enabled on the GGSN. Applying patch package 5
patches during traffic will cause SSM’s to reset. If patch package 5 is applied during traffic,
Section 6.2.2.4 Procedure to Recover the GGSN can be used to restore the GGSN.
Note: For detailed instructions on patch profile cloning, applying/removing a patch

package, please refer to Nortel GGSN 5.0.1 NTP 411-5221-927 (v09.17 or higher) GGSN
Provisioning Procedures - Appendix B: “GGSN Patch Application” - Section “Procedure to
update Patch Package”.
Note: For detailed instructions to disallow/enable traffic, close/transfer billing records,

delete PDP contexts, etc., please refer to Nortel GGSN5.0.1 NTP 411-5221-923 GGSN
Hardware Installation and Maintenance Guide - Appendix C: “Product Maintenance
Procedures” - Section “Manual GGSN shutdown, resync, or CMC switchover”
13.3.2 Procedure to Apply Patch Package 5
To apply patch package 5 to a GGSN node, please follow the steps below. If you are unsure
of the instructions, please contact Nortel Support for further clarification.
/opt/patches directory. Refer to NTP 411-5221-927 Appendix B Section “FTP Patch to
SCS server” if needed.


124
Manager -> Select Patch -> Click Update -> Click Add. Resolve dependency issues (if
any). Refer to NTP 411-5221-927 Appendix B Section “Auto Selection” if needed. For
patch persistency details, refer to NTP 411-5221-927 Appendix B Section “Accepting
patches”.
GGSN.
7. Clone the active patch profile from Patch Manager window for use of patch package 5.
A Patch Profile Configuration window will be opened automatically upon the
completion of the cloning. Refer to NTP 411-5221-927 Appendix B Section “Clone
Patch Profile” if needed.
Note: Patch profile cloning is the preferred method of patch package application. In
this method, the active patch profile is cloned to create a new patch profile. The
latest EMG patches and Patch package 5 patches are then added to this clone patch
profile. The clone patch profile is then swapped with the active patch profile.
8. The auto pop-up window can be used to edit the newly cloned profile. The edit window
can also be opened manually from the Patch Manager. Make sure that the patchable load
matches the current GGSN5.0.1 software release. Refer to NTP 411-5221-927
Appendix B Section “Editing a patch profile” if needed.
9. Add the latest EMG patches listed in Table 1 as patch rules to the cloned patch profile.
Note: Patch G501_01810161EMG_GTP must be added to the clone patch profile

prior to patch package 5 patches. The required EMG patch list can be found in patch
package 5 PD file.
10. Add patch package 5 patches as patch rules to the cloned patch profile. A single click on
patch package 5 will auto select/highlight all patches associated with the package.
Resolve dependency issues (if any). Refer to NTP 411-5221-927 Appendix B Section
“Steps to add patch rules using Auto selection” if needed.
11. Verify if the cloned patch profile with patch package 5 patches can be applied to the
GGSN. Refer to NTP 411-5221-927 Appendix B Section “Verify Patch Profile” if
needed. Monitor the GGSN terminal logs during this step to make sure that the profile
is ok for application.
12. Disallow traffic to the GGSN and delete all PDP contexts on the GGSN from SCS client
(as Gn ISP user). Refer to NTP 411-5221-923 Appendix C if needed.

125
13. Close billing records on GGSN and if applicable transfer them to the CGF. Refer to
NTP 411-5221-923 Appendix C if needed.
14. Perform a GGSN resync from SCS client.
15. Verify the current patch package application status from SCS client -> Patch Manager -
> Device -> Select GGSN -> Double Click. You should see that packages 1 through 4
are applied while package 5 is unapplied.
17. Perform a GGSN resync again from SCS client.
manager.
19. Enable traffic back on the GGSN from SCS client (as Gn ISP user). Refer to NTP 411-
5221-923 Appendix C if needed.

13.3.3 Procedure to Remove Patch Package 5
This section is only needed if a rollback is required. If this occurs, please follow the steps
below to remove patch package 5.
1. Disallow traffic to the GGSN from SCS client (as Gn ISP user). Refer to NTP 411-
2. Delete all PDP contexts on SGSN from SCS client (as Gn ISP user) Refer to NTP 411-
3. Close billing records on GGSN and transfer them to the CGF. Refer to NTP 411-5221-
923 Appendix C if needed.
profile from SCS client (as device_owner user). Refer to NTP 411-5221-927 Appendix
B Section “Swapping a Patch Profile” if needed.

126
6. Verify that the patch package 5 is removed from the GGSN while the node is restored to
previous patch package 4 from SCS client or GGSN.
7. Enable traffic back to the GGSN from SCS client (as Gn ISP user). Refer to NTP 411-

13.3.4 Procedure to Recover the GGSN
In case patch package 5 is applied during traffic thus has caused the SSM’s to reset, the
following steps may be used to recover the GGSN. Otherwise, simply ignore this section.
1. Disallow traffic to the GGSN and delete all PDP contexts on the GGSN from SCS client
(as Gn ISP user). Refer to NTP 411-5221-923 Appendix C if needed.
2. Close billing records on GGSN and if applicable transfer them to the CGF. Refer to
NTP 411-5221-923 Appendix C if needed.
3. Double check the current active patch profile is for patch package 5 from SCS client (as
device_owner user).
5. Verify that the node is patching current to patch package 5 from SCS client.
6. Enable traffic back on the GGSN from SCS client (as Gn ISP user). Refer to NTP 411-


127

patches”.
GGSN.

128
Important Note:
The following activatable EMG patch is available. Please refer to the patch PD file to
verify if the functionality is needed prior to activating the patch.
• G501_01799972BEMG_DCC
Important Note:
EMG patch G501_01799972BEMG_DCC is a pre-requisite patch for patch package 6.
Please add the patch prior to adding patch package 6. If the functionality is not required,
the patch directive must be set to Deactivate.
patch package 6 will auto select/highlight all patches associated with the package. Refer
to NTP 411-5221-927 Appendix B Section “Steps to add patch rules using Auto
selection” if needed.
Important Note:
The following activatable patch is available. Please refer to the patch PD file to verify
if the functionality is needed prior to activating the patch. If the functionality is not
required, the patch directive must be set to Deactivate.
• G501_01814048ACT_DCCCMC
applied to the GGSN. Refer to NTP 411-5221-927 Appendix B Section “Verify Patch
Profile” if needed. Monitor the GGSN terminal logs during this step to make sure that
the profile is ok for application.
manager.

129



130

patches”.
GGSN.
Important Note:
EMG patch G501_01904728EMG_GTP is a pre-requisite patch for patch package 7.
Please add the patch prior to adding patch package 7.

131
Important Note:
The following activatable patch is available. Please refer to the patch PD file to verify
if the functionality is needed prior to activating the patch. If the functionality is not
required, the patch directive must be set to Deactivate.
• G501_01913874ACT_GTP
• G501_01950186ACT_GTP
manager.
14. Please review the special handling section for the following patches. If applicable,
please execute the patch application steps.
• G501_01863890_LI
• G501_01912068_RMC
• G501_01867815_GTP

Note: A GGSN resync is required following a roll back from package 7 to patch package 6.

132
3. Perform a GGSN resync.

13.3.6.4 Special Handling Instructions
This section is required only if a patch is listed in Table 2 of Section 6.3 and
applied/removed individually other than through the patch package process described above.
A few patches within patch package 7 and new EMG patches, if applied or removed
individually, require special handling. For more details, please refer to Section 6.3 Patches
Requiring Special Handling. If patch package process is followed, simply ignore this
Section 6.2.2.4.

133

any, refer to Table 1 and Table 2 if needed). Refer to NTP 411-5221-927 Appendix B
Section “Auto Selection” if needed. For patch persistency details, refer to NTP 411-
5221-927 Appendix B Section “Accepting patches”.
GGSN.

134
Note: The following patches (if present) must be removed from the profile prior to
applying PP8 patches. G501_01939135LTD_GTP, G501_01818007_SVC
1.Patch G501_01939135_GTP cannot be applied with these active patches:

G501_01939135LTD_GTP
2.Patch G501_01979441_SVC cannot be applied with these active patches:
G501_01818007_SVC
Note: The total number of patches in the PP8 profile shall be 293. Please verify the list
with patch package PD file.
manager.
Note: Resync is NOT required for application of the patch package 8.

Note: Resync is NOT required for removal of patch package 8


135
Appendix C: Patch Obsoletion Table
# Patch PKG Replaced By
1 G501_01450817_IFMGR 1
2 G501_01282575ACT_GTPACCT 1
3 G501_01447784_WAP 1
4 G501_01478082_GTP 1
5 G501_01341393_ACCT 1
6 G501_01484327ACT_NETINET 1 G501_01484327AACT_NETINET
7 G501_01522486_WIND 2
8 G501_01536849_PPP 2 G501_01540279_GTP
9 G501_01571150_POLMGR 2
10 G501_01527169_GTP 2 G501_01527169AEMG_GTP
11 G501_01465128_POLMGR 2 G501_01465128A_POLMGR
12 G501_01595094ACT_AAA 2 G501_01595094AACT_AAA
13 G501_Q01646145_PPDSSP 3 G501_01646145A_PPDSSP
14 G501_01665444_NZDST 3 G501_01665444A_NZDST
15 G501_01743059EMG_CONFMGR 4 G501_01743059AEMG_CONFMGR
16 G501_01818007_SVC 5 G501_01979441_SVC
17 G501_01826783_STATS 5 G501_01826783A_STATS
18 G501_01797315EMG_GTPACCT 6
19 G501_01815175_TIMECMC 8 G501_01815175A_TIMECMC
20 G501_01815175_TIMESSP 8 G501_01815175A_TIMESSP
21 G501_01996131_GTP 8 G501_02002598_GTP

136
14 References
1. 411-5221-004 GGSN and SCS Documentation
2. 411-5221-200 GGSN and SCS What's New
3. 411-5221-206 GGSN Billing Samples
4. 411-5221-309 GGSN and SCS Upgrade Manual
5. 411-5221-502 GGSN Troubleshooting Guide
6. 411-5221-921 GGSN Alarms Reference Manual
7. 411-5221-922 GGSN CLI Guide
8. 411-5221-923 GGSN Hardware and Maintenance Guide
9. 411-5221-924 GGSN Monitoring Guide
10. 411-5221-926 GGSN User Guide
11. 411-5221-927 GGSN Provisioning Procedures
12. 411-5221-928 GGSN RADIUS Interface Guide
13. 411-5221-929 GGSN CORBA shell CLI Guide
14. 411-5221-930 GGSN CORBA API Guide

137
15 Acronyms
AAA Authentication, Authorization and Accounting

AAAmgr AAA Manager
ACK ACKnowledgement
ADMF ADMinistration Function
ALC ATM Line Card
API Application Programming Interface
APN Access Point Name
AVP Attribute Value Pair
BGP Border Gateway Protocol
CAB Customer Advisory Bulletin
CBB Content Based Billing
CCA Credit Control Answer
CCFH Credit Control Failure Handling
CCR Credit Control Request
CDR Call Detail Record
CFS Content Filtering Server
CGF Charging Gateway Functionality
CHAP Challenge Handshake Authentication Protocol
CLI Command Line Interface
CMC Control and Management Card
CORBA Common Object Request Broker Architecture
CPU Control Processor Unit
CR Change Request
CSV Comma Separated Value
CTP Card Telephony Protocol
DCC Diameter Credit Control
DHCP Dynamic Host Configuration Protocol
ESP Encapsulating Security Payload
FLEC Fast Ethernet Line Card
FSIC Field Safe Internal Counters
FTB Frame Transport Bus
GARP Gratuitous Address Resolution Protocol
G-CDR GGSN Call Detail Record
GGSN Gateway GPRS Support Node
Gi GPRS IP Interface
GPP Generation Partnership Project
GPRS General Packet Radio Service
GRE Generic Route Encapsulation

138
GTP GPRS Tunneling Protocol

GTP' Enhanced GPRS Tunneling Protocol
GUI Graphical User Interface
HTTP Hyper Text Transfer Protocol
ICP Intelligent Cell Parser
IE Information Element
IFMGR InterFace Manager
IMS IP Multimedia Subsystem
IOT Inter Operability Testing
IP Internet Protocol
IPCMGR IP Control Manager
IPSEC IP Security
ISP Internet Service Provider
KB Kilobyte
L2TP Layer 2 Tunneling Protocol
LAC Location Area Code
LDAP Lightweight Directory Access Protocol
LNS L2TP Network Server
MAC Media Access Control
MB Megabyte
MPLS Multi Protocol Label Switching
MSCC Multiple Service Credit Control
MTU Maximum Transmission Unit
NTP Nortel Technical Publication / Network Time Protocol
OAM Operations, Administration & Maintenance
PAP Password Authentication Protocol
PC Packet Core
PDP Packet Data Protocol
PE Provider Edge
PLM Product Line Management
PS Packet Service / Packet Switched
QCT Quota Consumption Time
QHT Quota Hold Time
RADIUS Remote Authentication Dial-In User Server/Service
RAR Re-Authentication Request
RPC Remote Procedure Call
RSVP-TE Resource Reservation Protocol - Traffic Engineering
SCP Service Control Point
SCS Service Creation System
SER Services Edge Router
SGSN Serving GPRS Support Node

139
SNMP Simple Network Management Protocol

SSC Subscriber Service Card
SSH Secure Shell
SSM Subscriber Service Module
SSP Subscriber Service Processor
SVC Switched Virtual Circuit
TCP Transmission Control Protocol
TEID Tunnel Endpoint Identifier
TLV Type Length Value
ToD Time of Day
UMTS Universal Mobile Telecommunications System
URL Uniform Resource Locator
VLAN Virtual Local Area Network
VLR Visitor Location Register
VPN Virtual Private Network
VR Virtual Router
W-NMS Wireless Network Management System
WAP Wireless Application Protocol

GGSN 5.0.1 Release Notes V 9.0.3

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GGSN 5.0.1 Release Notes V 9.0.3

Uploaded by

Copyright:

Available Formats

1

© Copyright Nortel 2009

Richardson, TX, U.S.A.

NORTEL CONFIDENTIAL: The information contained in this document is the property of

Release Notes for GGSN5.0.1

VERSION DATE AUTHOR EXPLANATION OF AMENDMENTS

Aug 07, Praveen

September Deepak  Information related to 070828-30631/ Q01737685 added.

Release Notes for GGSN5.0.1

VERSION DATE AUTHOR EXPLANATION OF AMENDMENTS

October 28, Deepak

 Information related patch package 5 updated.

 Added information on Case 080721-16197/CR Q01903693 (a known issue)

 Added information on Case 080604-78158/CR Q01911533 (a known

Release Notes for GGSN5.0.1

VERSION DATE AUTHOR EXPLANATION OF AMENDMENTS

 Removed EMG patches G501_01877146EMG_SERVICES,

March 18, Deepak  Pre-requisite patch for G501_01794436EMG_GTP – added to Patch

 Patch G501_01589010_GTP incorrectly listed as part of patch package 7.

 Correction to Table1 updated.

 Correction to Table1 updated.

 Information related patch package 8 updated.

 Removed patches G501_01881900_GTPCMC, G501_01881900_GTPSSP

Release Notes for GGSN5.0.1

VERSION DATE AUTHOR EXPLANATION OF AMENDMENTS

 Removed patches G501_02005047_WRAP, G501_02002598_GTP from

 Removed patch G501_01818007_SVC from Table 1.

 Information related patch package 9 updated.

Oct 21, Troy

Release Notes for GGSN5.0.1

Release Notes for GGSN5.0.1

6.3.18 G501_FF01567650_IPSSP .....................................................................65

Release Notes for GGSN5.0.1

6.3.64 G501_01867815_GTP ............................................................................83

Release Notes for GGSN5.0.1

13.3.7.3 Procedure to Remove Patch Package 8...........................................134

Release Notes for GGSN5.0.1

GGSN5.0.1 is a maintenance release on top of GGSN5.0, so all Limitations and Feature

1.3 Software Load Line-up

The names of the Final Compile loads are:

SCS package: SCS GGSNS5.0.2_SCS5.0_14

Note: The GGSNS5.0.1-isos-build-17 release is referred to as GGSN5.0.1 and the SCS

Release Notes for GGSN5.0.1

2 Supported External Servers/Releases

Software type Name Version

Prepaid Service Builder

Legal Intercept Verint

Wireless Village IM Followap

Release Notes for GGSN5.0.1

3 Supported Software Upgrade Paths

UPGRADING FROM: UPGRADING TO:

The supported upgrade paths for the GGSN are as follows:

UPGRADING FROM: UPGRADING TO:

Release Notes for GGSN5.0.1

4 New Features and Enhanced Features

4.1 GGSN5.0 New Features

Release Notes for GGSN5.0.1

Release Notes for GGSN5.0.1

4.2 Feature Patches Sourced in GGSN5.0.1

Q01275287 CBB Usage Time Accounting (Removal of trailing QCT Timeout

Q01339974 Enhancement of SGSN Change Partial Billing

Q01222356 Enhanced CTP Connection Management

September Deepak Information related to 070828-30631/ Q01737685 added.

Information related patch package 5 updated.

Added information on Case 080721-16197/CR Q01903693 (a known issue)

Added information on Case 080604-78158/CR Q01911533 (a known

Removed EMG patches G501_01877146EMG_SERVICES,

March 18, Deepak Pre-requisite patch for G501_01794436EMG_GTP – added to Patch

Patch G501_01589010_GTP incorrectly listed as part of patch package 7.

Correction to Table1 updated.

Correction to Table1 updated.

Information related patch package 8 updated.

Removed patches G501_01881900_GTPCMC, G501_01881900_GTPSSP

Removed patches G501_02005047_WRAP, G501_02002598_GTP from

Removed patch G501_01818007_SVC from Table 1.

Information related patch package 9 updated.