GGSN_5.0.1_Release_Notes_V_9.0.3

1

Release Notes for GGSN5.0.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.

2


Publication History

VERSION DATE AUTHOR EXPLANATION OF AMENDMENTS

1.0 Aug 07, 2006

Praveen Araveti Initial Release

1.1 Nov 03, 2006

Muralidhar Kolapalli

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 from section 10.2 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

1.2 Jan 31, 2007 Dan Gunther

Patch Package 1, known issues, active CABs updated. Add new columns in 6.1 Table 1 “Nature of Patch” and “Dependencies / Prerequisites”. Remove 5.0 Limitation section.

1.3 Feb 8, 2007 Dan Gunther Update section 7 for configuration changes to OA&M servers and RADIUS trunk provisioning. Additional entry to section 10 for Active CABs.

1.4 Feb 21, 2007 Dan Gunther Update Active CABs.

1.5 Apr 4, 2007 Dan Gunther Patch Package 2, updates to Configurations and Recommendations, OA&M, Known Issues Deferred, Active CABs, Acronyms. Limitations Section 8 added.

1.6 May 30, 2007

David Corekin Added “export config” limitation to Known Issues

2.0 June 18, 2007 Al Carriere Remove patch G501_01484327ACT_NETINET and add patch

G501_01484327AACT_NETINET

2.1 June 21, 2007 Al Carriere Added recently released EMG patches:

G501_01658130EMG_GTP and G501_01621446EMG_GTP.

3.0 August 14, 2007

Deepak Nagarajan

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 o Active CABs 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.

3.1 September 04, 2007

Deepak Nagarajan

Information related to 070828-30631/ Q01737685 added. Information related to Q01522427-01 added.

3.2 September 12, 2007

Deepak Nagarajan Information related to 070912-44775/ Q01745586 added.

3.3 October 4, 2007

Deepak Nagarajan

Information related to Q01755670 added. Information related to

071004-66154/ Q01759935 added.

3



3.4 October 28, 2007

Deepak Nagarajan Shaded patches listed in Table1 un-shaded after release of patch package 3.

3.5 October 31, 2007

Deepak Nagarajan Patch G501_01730666EMG_EMS added to Table1

3.6 November 7, 2007

Deepak Nagarajan

Information related to Q01780402 updated – Patch G501_01639302_GTP requires all PDP contexts are deleted and traffic disabled before applying and un-applying this patch.

3.7 November 19, 2007

Deepak Nagarajan

Information related to Q01784177 updated – PDP contexts must be deleted prior to applying or un-applying patch package 3. Section Patch Package Application Instructions has been updated.

4.0.4 January 11, 2008

Deepak Nagarajan

Information related patch package 4 updated. Please refer to Table1 for details.

Review minutes updated. Special handling instructions for G501_01466350ACT_LI updated. Information related to 071211-27286/ Q01801692 updated. V status patches grayed out in Table1. Info related to CR Q01798601 has been updated.

4.0.5 January 25, 2008

Deepak Nagarajan

Information related patch package 4 version 2 updated. Patch G501_01670464_CPM removed from Table1.

Info related to CR Q01618197-05 updated.

5.0 April 8, 2008

Deepak Nagarajan

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. Information related to CR Q01743059-05 updated. The Field Application

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.

5.0.1 May 13, 2008

Deepak Nagarajan Information related to 080513-60317/ Q01874195 has been updated.

5.0.2 June 11, 2008 Shijian Zhou

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 additional steps.

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.

5.0.3 July 22, 2008 Shijian Zhou

Added information on Case 080721-16197/CR Q01903693 (a known issue) to correct the erroneous texts in NTP 411-5221-926 Version 10.40 Nortel GGSN User Guide -> Section Functional description -> GTP accounting -> Accounting record generation -> G-CDR identification.

5.0.4 August 12, 2008 Shijian Zhou

Added information on Case 080604-78158/CR Q01911533 (a known issue) to clarify on the Maximum Bit Rate supported by Nortel GGSN5.0.1 product.

4



5.0.5 August 14, 2008 Shijian Zhou

Removed EMG patches G501_01877146EMG_SERVICES, G501_01865914EMG_AAA, G501_01885754EMG_RPC, G501_01899346EMG_GTP as they are not defined in the patch package 5 version 4 Pd file.

6.0 October 24, 2008

Deepak Nagarajan

Information related patch package 6 version 3 updated. • Patch Package Application Instructions for Patch Package 6 • Table1 updated with patch package 6 and EMG patch details. • Table 2 updated with special handling instructions for patch package 6

patches. • Information related to Q01933102-01 has been updated.

7.0 December 08, 2008

Deepak Nagarajan

Information related patch package 7 updated. • Patch Package Application Instructions for Patch Package 7 • Table1 updated with patch package 7 and EMG patch details. • Table 2 updated with special handling instructions for patch package 7

patches.

7.0.1 March 18, 2009

Deepak Nagarajan

Pre-requisite patch for G501_01794436EMG_GTP – added to Patch Sequencing with Dependencies Resolved (Table1)

7.0.2 March 18, 2009

Deepak Nagarajan

Patch G501_01589010_GTP incorrectly listed as part of patch package 7. This patch is part of patch package 2. The correction has been updated in Table1.

7.0.3 March 23, 2009

Deepak Nagarajan

Correction to Table1 updated. - Few Activate-able patches did not have the ACT tag under the PKG column. - Incorrect patch dependency for G501_01662594ACT_SVC.

7.0.4 March 24, 2009

Deepak Nagarajan

Correction to Table1 updated. - G501_01839550EMG_GTP and G501_01799972BEMG_DCC included twice.

8.0 May 14, 2009 Bai Lin


patches.

8.0.2 May 15, 2009 Bai Lin Added quick links for the last 5 patches in Table 2

8.0.3 June 1, 2009 Shijian Zhou

Removed patches G501_01881900_GTPCMC, G501_01881900_GTPSSP from patch package 8.

Clariry that patch package 8 does NOT require resync for application and removal.

5



8.0.4 July 20, 2009 Bai Lin

Removed patches G501_02005047_WRAP, G501_02002598_GTP from patch package 8

Added patch G501_01996131_GTP in patch package 8 Removed patch G501_02002598_GTP from Table 2 Removed special handling for patch G501_02002598_GTP at Section 6.3.65

8.0.5 Aug 05, 2009 Bai Lin

Removed patch G501_01818007_SVC from Table 1. Remove patch G501_01815175A_TIMESSP from Section 6.3 Patches

Requiring Special Handling.

9.0 August 17, 2009 Bai Lin


patches.

9.0.1 Sep 16, 2009 Bai Lin • Add Appendix C: Patch Obsoletion Table

9.0.2 Oct 14, 2009

Troy Ronholdt

• Remove patch G501_01996131_GTP from Table 1, and clean up some tables.

9.0.3 Oct 21, 2009

Troy Ronholdt • Update Patch count from 304 to 302.

http://wds.us.nortel.com/patches/hidden/download.cgi?patch=G501_01815175A_TIMESSP&type=GGSN&rel=GGSNS5.0.1&prod=G501_&status=R&download=./Loads/GGSN/GGSNS5.0.1/G501_01815175A_TIMESSP.zip�

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 Application and Removal Instructions for Patch Package 7.................129 13.3.6.1 Warnings and Notes........................................................................129 13.3.6.2 Procedure to Apply Patch Package 7 ..............................................129 13.3.6.3 Procedure to Remove Patch Package 7...........................................131 13.3.6.4 Special Handling Instructions .........................................................132

13.3.7 Application and Removal Instructions for Patch Package 8.................132 13.3.7.1 Warnings and Notes........................................................................132 13.3.7.2 Procedure to Apply Patch Package 8 ..............................................132

9


13.3.7.3 Procedure to Remove Patch Package 8...........................................134 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

Radius 5.0 SPE

DHCP 5.4 SPE

CMG WSB v3.3Openwave 5.0.1

Service Builder WIR 6.1

Performance Server V5.0

Main Server V5.0

Verint Rel 5a

Followap Rel v 3.0.35

Websense V6.1

GG

SN 5

.0.1

Content Filtering

MetaSolv

PS5.

4WAP

Wireless Village IM

OA&M

Prepaid

Legal Intercept

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)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)

SCS5.0.2 SCS GGSNS5.0.2_SCS5.0_14

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 GGSN4.1 ggsns4.1-isos-build-103 GGSN4.1.1 ggsns4.1.1-isos-build-9 GGSN5.0 ggsns5.0a-isos-build-46

GGSN5.0.1 GGSNS5.0.1-isos-build-17

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 G411_01275287ACT_QCTSSP CBB Usage Time Accounting (Removal of trailing QCT Timeout Period).

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.

Item Patch Id Case No. CR No. Title

1. G50_01362714_DCC 060404-96699/ Q01362714 Trap When Modifying DCC Tx Event Interval Timer

2. G41_01367368_TF G411_01367368_TF G50_01367368_TF

060503-26914 060503-27077/ Q01367368

CBB Policy with 256 URLs cause SSM Reset

3. G411_01375654_SCP G50_01375654_SCP

060518-44142 060518-44623 060518-44630 060424-16736 060424-17353 060510-34420 060510-35163/ Q01375654

SCP Task Suspension Due to Memory Access Error

4. G401_01355039_PPP G411_01355039_PPP G50_01355039_PPP

060207-34367 060421-15294 060222-50389 060222-50386 060222-50431 060222-50521 060222-50440 060222-50435 060222-50433 060222-50539 060321-80598 060412-05416 060717-06951 060503-26917/ Q01355039

SSP resets when GTP PPP proxy session is released

5. G411_01391931EMG_SUB G50_01391931EMG_SUB

060526-54062 060627-87178 060627-87202/ Q01391931

CMC Switchover Caused by GTP Task Stack Overflow

6. G50_01365576_ISN 060502-26220/ Q01365576 Static Routes Lost After CMC Switchover

7. G50_01378284_ISPMGR 060519-46139/ Q01378284

Certain CGF Profile Attributes Lost After CMC Switchover

8. G50_01365577_ISN 060502-26228/ Q01365577 SCS Trap Ports Reset to Default Values

9. G50_01407739ACT_GTP 060622-81950/ Q01407739 Radius PAP Authentication Optional Functionality

10. G50_01351011_DCC 060302-60438/ Q01351011

Robustness Enhancement When Sending Diameter Message

11. G411_01407019_DHCP G50_01407019_DHCP

060614-72251 060627-86393 060628-88411/ Q01407019

Some of DHCP Profiles Not Completely Loaded

20



12. G411_01222356ACT_CTP G50_01222356ACT_CTP Q01222356 Enhanced CTP Connection Management

13. G41_01230242ACT_NETINET G411_01230242ACT_NETINET G50_01230242ACT_NETINET

051003-08010/ Q01230242 Large TCP Packets Are Fragmented

14. G411_01241519ACT_GTP G50_01241519ACT_GTP

051003-07995/ Q01241519 GGSN delays prepaid reauth requests by 500ms.

15. G401_01264512ACT_SUBMGR G50_01264512ACT_SUBMGR Q01264512 Support of DHCP Relay Agent address for VLAN VPN

access model 16. G50_01267600_CF Q01267600 Content Filter Protocol Error During Concatenated WAP

17.

G401_01271233_GTPP G411_01271233_GTPP G41_01271233_GTPP G50_01271233A_GTPP

051121-60377/ Q01271233 GTP Accounting Task Died Without Trace

18. G411_01275287ACT_QCTCMC/ G411_01275287ACT_QCTSSP Q01275287 CBB Usage Time Accounting (Removal of QCT

Timeout Period)

19. G50_01276610_IFMGR G411_01276610_IFMGR

051122-61341/ Q01276610

Not Able to Telnet Into GGSN On High "VXWORKS SYSTEM HEAP" Usage

20.

G401_01279141_GTP G41_01279141_GTP G411_01279141_GTP G50_01279141_GTP

051216-86298/ Q01279141 SSP Load Balance of Contexts Fails

21. G41_01279218_DCC G401_01279218_DCC G411_01279218_DCC

051215-85044/ Q01279218 GGSN Doesn’t Apply the Correct Rule base

22. G411_01279296_SUBMGR G50_01279296_SUBMGR

051218-87338 051218-87345/ Q01279296

CMC Switches Over Due to a Race Condition

23. G41_01279695_TF G411_01279695_TF G50_01279695_TF

051214-83588 051123-62855/ Q01279695

Incorrect billing of secure WAP1.2 traffic

24. G50_01279806_GTP Q01279806 Radius Start And Stop Message Handling Corrections

25.

G41_01286030_CLI G401_01286030_CLI G411_01286030_CLI G50_01286030_CLI

060103-96704 060131-26248/ Q01286030

GGSN is Not Adding APNs After a CMC Switchover

26. G401_01286969_GTP G411_01286969_GTP G50_01286969_GTP

060601-58707 060113-07874 060606-63211 050906-77451 060207-33522 060222-50441/ Q01286969

SSP Core Dump Caused by Deleted Secondary PDP Context

27.

G411_01293301_GTPCMC G411_01293301_GTPSSP G41_01293301_GTPCMC G41_01293301_GTPSSP G50_01293301_GTPCMC G50_01293301_GTPSSP

051113-51687/ Q01293301 QHT Not Triggered After RAR Message

28.

G401_01296948EMG_SVC G41_01296948EMG_SVC G411_01296948EMG_SVC G50_01296948EMG_SVC

060126-22338/ Q01296948 Flowcache Values Not Read After Reboot

29.

G401_01300526_GTP G41_01300526_GTP G411_01300526_GTP G50_01300526_GTP

060103-96953 060104-98715/ Q01300526

High Percentage of MMS Activation Discarded

30. G411_01303739EMG_ISPMGR G50_01303739_ISPMGR

060131-25818/ Q01303739 Duplicate Entries In The Config Database

http://wds.us.nortel.com/patches/Loads/GGSN/GGSNS4.1.1/G411_01276610_IFMGR.zip�

21



31.

G401_01311464_SVC G41_01311464_SVC G411_01311464_SVC G50_01311464_SVC

Q01311464 Flowcache Display Error for Aggregate Sessions

32. G41_01319247_DCC G411_01319247_DCC G50_01319247_DCC

060223-52408/ Q01319247 Used-Service-Unit AVP Not Sent in CCR(F)

33. G411_01319954A_HTTP G50_01319954_TF

060111-05337/ Q01319954

CBB Under Rates Packets Retransmitted After FIN Packet

34. G41_01323841_GTP G411_01323841_GTP G50_01323841_GTP

060201-27499/ Q01323841 Incorrect Coupon Volume Usage during DCC/CTP Calls

35. G41_01335786_SCP G411_01335786_SCP G50_01335786_SCP

060615-74124 060205-31963 060711-99985 060222-50684/ Q01335786

SCP Connection Loss

36. G411_01336395A_VPN 060309-67531/ Q01336395 OVLD condition on 13/1/2

37. G411_01339974AACT_GTPACCT G50_01339974ACT_GTPACCT

060411-03912 060220-47796/ Q01339974

Enhancement of SGSN Change Partial Billing

38. G50_01343906_GTP 060321-81419/ Q01343906 Unacceptable Delivery of Erroneous SDU field of QoS

39. G411_01318950ACT_AAA 060309-67534 060111-06134/ Q01318950

GGSN System Failure messages under 20 PDP request/sec load

40. G411_01227794AACT_SVC G411_01227794BACT_SVC G50_01227794ACT_SVC

060623-83134 050812-53738/ Q01227794

Some Dropped Packets Are Counted For Billing

41.

G41_01292925_TF G411_01292925ACT_TF G411_01292925AACT_TF G50_01292925_TF

051115-54191/ Q01292925

Fragmented WAP Packets Using Prepaid are Billed Incorrectly

42. G41_01312654_TF Q01312654 Pipelined WAP Packets Using Prepaid are Billed Incorrectly

43. G411_01319256ACT_ELCMGR 060217-45967/ Q01319256

Data Loss Due To MPLS MTU Restriction on GELC Card

44. G50_01343947_DCC 060330-92032/ Q01343947 Incorrect G-CDR marking time stamp for DCC

45. G41_01351019EMG_PATCHER G411_01351019EMG_PATCHER G50_01351019EMG_PATCHER

060330-91382 060321-80711/ Q01351019

GGSN Patcher Traps on a Patch Profile Swap

46. G411_01343948_DCC G50_01343948_DCC

060330-92070/ Q01343948 Wrong DCC handling with CCNA

47. G411_01356951_GTP G50_01356951_GTP

060321-80515/ Q01356951

Missing Tariff Change Usage Coupon After a ToD Event

48. G411_01346716ACT_GTPACCT Q01346716 Partial Billing updates with maximum CBB containers for QCT

49.

50. G411_01389183_SVC G50_01389183_SVC

060512-37363/ Q01389183

SSP Traps Due to Uninitialized fields in New Conversation

51. G411_01378314ACT_PAR G50_01378314ACT_PAR

060503-26719/ Q01378314 DIR Command Causes Overload.

52. G50_01369200_AAA Q01369200 Radius Accounting Fails During Catchup

http://47.103.88.61/cgi-bin/query-get-case?CaseId=060309-67534�

http://dpswww.ca.nortel.com/cgi-bin/quickcr.pl?cr_id=Q01318950&mode=txt�

22



53. G411_01394307_SVC G50_01394307_SVC

060522-47493 060526-53528 060817-47010 060907-69691 060710-98378 060925-89764 060929-95587 060929-95863/ Q01394307

SSM Resets Under Certain Flow Migration Conditions

54. G411_01405498_CARDMGR G50_01405498_CARDMGR

060518-44670 060518-44952 060807-30334 060323-84316 060628-87725 060629-88913/ Q01405498

Aux. Ethernet Management port on Standby CMC Down After CMC Switch

55. G411_01408229_SVC G411_01408229A_SVC G50_ 01408229_SVC

060614-73130 060714-04504 060510-34073/ Q01408229

Retransmitted Packets Dropped

56. G50_01424740EMG_GTP 060705-93889/ Q01424740 Correction of "CMC3 Unaligned Addr" Exceptions

57. G50_01423912EMG_ISR 060705-93889/ Q01423912 Address Misalignment Could Lead to Card Reset

58. G411_01404173A_NTP G50_01404173_NTP

060524-50668/ Q01404173

NTP Synchronization Fails When Using Multicast Mode On CMC3

59. G411_01435989_GTP G50_01435989_GTP

060719-09790/ Q01435989

GGSN Reports Wrong Volume and Time Usages for Prepaid Subscribers

60. G50_01436735_AAA 060627-86630/ Q01436735 Radius Accounting Records Not Always Written to Disk

61. G50_01439788_ELCMGR 060727-19072/ Q01439788 SFC Switchover Causes Core Dump on CMC

62. G411_01487158EMG_GTP G50_01487158EMG_GTP

060719-10022 061101-31138 061106-36179 061109-40711/ Q01487158

SSM Core Dump During GTP Tunnel Fall Forward Procedure

63.

G411_01096501EMG_HDISK G411_01096501EMG_PREREQ G50_01096501EMG_HDISK G50_01096501EMG_PREREQ

050921-94252 050302-72588/ Q01096501

Stateful Polling Of CMC3 Disk Drive Registers

64. G50_01441844_AAA 060728-20472/ Q01441844

Acct-Session-Id Not Included in RADIUS Accounting On/Off Messages

65. G411_01270521_GTP 051121-59569 060828-58213/ Q01270521

Debug Breakdown Counters for SYSFAIL.Other Counter

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.

Item Case No. CR No. Title

1 041104-48917/ Q01171194 SSC Card Problem

2 060220-48715/ Q01316540 Problem with Device Monitoring VPN on SCS Client

3 050815-55023/ Q01206858 Crash In OSPF-VPRN Due to RPC Timeout from VPN to OSPF-VPRN

4 060323-84669 060324-84959/ Q01214141

Stack Trace Occurred When Sending Bad ESP Packets to GGSN

5 050729-38917 050629-07088/ Q01252955

Support of MAC Multicast Manual Entry in ARP Table

6 Q01258932 “show stats bcm5631” Displays Negative Values

7 Q01293128 Q01293140

HD 'busy bit' Issue Causes Faulty CMC switchover/ HD 'busy bit' Issue Results in Invalid Reload Message

8 051221-90542/ Q01306294 Passive FTP with Proxy

9 060209-37392/ Q01310691 CORBA Error Message Missing During Implementation of CBB/FW rules

10 060210-39281/ Q01314287 Online Help Incorrect for Session and Idle Timeout

11 060215-44273/ Q01315453 TEID of 0 being Rejected After SGSN Restart

12 060214-42404/ Q01316163 GGSN CLI Display "show gtp session" for MNC is Wrong

13 051017-21505/ Q01320813 Changes Needed For Critical Event Display on Disk Failure

14 050301-71469/ Q01340595 Ethernet Card Driver has an Etherleak Weakness

15 060119-14495/ Q01345443 Radius Provided Idle Timer Ignored by GGSN

16 060516-40553 060209-37618/ Q01375871

CMC3 Ethernet Port Is Down w/ Router 100Mb/s Full-Duplex

17 060517-41837/ Q01383822 Unexpected Behavior with SYSLOG Settings

18 060502-25430/ Q01392230 DCCA Debug Not Correct

19 060615-73705/ Q01402367 SCS Changes for “add prefix-list” CLI Command Missing

20 041208-85884/ Q01189321 Quickstart Validates Incorrect Slot Number

21 060828-58213 051121-59569/ Q01270521

Health Monitor Log Pegging SM.FailActPdpCtxt.SYSF.Other

22 060112-06779/ Q01298251 Taking Main OSPF Routing Process Off Causes Access Subscriber OSPF Off

23 060310-69107/ Q01340685 “Loaded VPN Not Found” Session Error Found

24



24 060328-89402/ Q01346890 SSM Stuck in "need catchup" State While Recovering from a Crash.

25

060105-99643 060721-12698 060913-77030/ Q01350922

Trace_tool Does Not Show RADIUS Messages

26 060402-94154/ Q01355036 Time Stamp One Hour Behind.

27 060315-74796/ Q01368610 Counter for GTP Data Not Reported After SSM Crashes.

28 051207-75921/ Q01394343 'close gtp session' Does Not Close the Hung Session

29 060608-65955/ Q01416171 Gtpmgr Traps on Session Setup Due to NULL Pointer

30 060725-15601/ Q01449916 "close gtp session msisdn -force" Does Not Close the Hung Session

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.


1 G401_01112269_EMSCLIENT G411_01112269_EMSCLIENT G41_01112269_EMSCLIENT

Q01112269 SCS Monitor Port Hung After SCS Upgrade

2 G401_01041640ACT_GTP G411_01041640ACT_GTP

041029-42029 050128-36907/ Q01041640

Optionally Record Missed N3 Echo Response Logs in Event Logs

3 G401_01088756_TF G411_01088756_TF

050131-38682/ Q01088756 Service redirect accumulated fixes

4 G401_01166315_IFMGR G411_01166315_IFMGR G41_01166315_IFMGR

050613-86914/ Q01166315

Generate GARP message on auxiliary Ethernet management

5 G401_01225761_IFMGR G411_01225761_IFMGR G41_01225761_IFMGR

050809-49250/ Q01225761

Command “show ipsec interface” displays extra loop-back interfaces

6 G401_01229182_DCC G411_01229182_DCC G41_01229182_DCC

050927-01226/ Q01229182 Diameter Connection Loss

7 G401_01244947A_TF Q01244947 SSM fails due to wrong HTTP stream processor assignment

8 G401_01252109_GTP G411_01252109_GTP G41_01252109_GTP

051024-30385/ Q01252109

Flow-label not always set in GTP V0 create/update response header

9 G401_01100242_GTP 050310-82427/ Q01100242 Diameter – PDP Context delete response.

10 G401_Q01254961_SVC 050908-80817/ Q01254961 NULL pointer access issues

11 G401_01113502_TF G41_01113502_TF

050328-00822 050407-13303 050413-19868 050516-55855/ Q01113502

SSM resets when a web anonymized URL address is passed in for a CBB policy

12 G401_01140415_GTP G411_01140415_GTP G41_01140415_GTP

050307-77885/ Q01140415 IFMGR connection list corruption

13 G411_01119420_DCC G41_01119420A_DCC Q01119420 CCR(T) not sent upon invalid CCA

14 G411_01119420_GTP G41_01119420A_GTP Q01119420 CCR(T) not sent upon invalid CCA

15 G41_01170977_SERVICES 050629-06643/ Q01170977

Deliver packets received with a mismatched source IP address

16 G41_01171715_GTPP Q01171715 GGSN call failures due to CPU overload

17 G411_01231336_RPC G41_01231336_RPC

050930-06006/ Q01231336 User Data Plane loss after SSM failure

18 G411_01238107_OS G41_01238107_OS Q01238107 Cardmgr task creating invalid task delays

19 G411_01245233_ISPMGR G41_01245233_ISPMGR

051101-38486/ Q01245233

Session Error when Trunk Interface is Added with Existing IP

20 G41_01257024_GTP Q01257024 CCR Final missing Rulebase-Id AVP

26



21 G401_01057942AACT_GTP G411_01057942ACT_GTP G41_01057942ACT_GTP

041213-90631/ Q01057942 Disable CTP V1/V2 re-auth Message After GTP Update

22 G401_01075604_PSPMGR G411_01075604_GTP G41_01075604_GTP

040929-06407/ Q01075604 GGSN sends an Error Indication to SSGN

23 G401_01118413_SSH G411_01118413_SSH

050225-68469/ Q01118413

CLI 'show log command' does not include SSH user information.

24 G401_01124576_GTP G411_01124576_GTP G41_01124576_GTP

Q01124576 Sessions still active after Idle Timer expires.

25 G401_01130138ACT_SUBMGR G411_01130138ACT_SUBMGR G41_01130138ACT_SUBMGR

050425-32309/ Q01130138

Cannot add Default Route to Access Subscriber Reachability

26 G401_01141942_L2TP G411_01141942_L2TP G41_01141942_L2TP

050510-49512/ Q01141942 LNS port change not recognized by GGSN LAC.

27 G401_01156698_DCC G411_01156698_DCC G41_01156698_DCC

050329-02535/ Q01156698 GGSN sends 2 MSCCs when ToD event occurs

28 G411_01157893_TF G41_01157893_TF Q01157893 CBB under rates packets fragmented at IP layer.

29 G401_01158405EMG_GTP G411_01158405EMG_GTP G41_01158405EMG_GTP

050613-86771/ Q01158405 GGSN AAA Manager memory leak

30 G401_01160744EMG_HTTP G411_01160744EMG_HTTP G41_01160744EMG_HTTP

050614-88968 050905-77293/ Q01160744

CBB: Incorrect handling of multiple "HTTP/" in HTTP response

31 G411_01165498_ISN G41_01165498_ISN

050624-01365/ Q01165498 Longer recovery time after a CMC switchover

32 G401_01178341_SVC G411_01178341_SVC G41_01178341_SVC

050627-02861/ Q01178341 GGSN SVC Manager memory leak

33 G411_01183036_AAA G41_01183036_AAA Q01183036 Memory leak detected in GTP subsystem during soak

test

34 G401_01201191_GTP G411_01201191_GTP G41_01201191_GTP

050818-59264 050826-68563 050921-94118/ Q01201191

GTP Response QoS element "Delivery of erroneous SDU" incorrect.

35 G411_01205797_VPN Q01205797 SSM Failure After Modifying VRF Profile

36 G411_01206947_CLOCK G41_01206947B_CLOCK

050908-81227 050615-90022/ Q01206947

Incorrect time set on the GGSN

37 G401_01207989A_GTPACCT G411_01207989AACT_ACCT G41_01207989ACT_GTPACCT

050901-74694 050901-74739 050901-74766 050902-75473 050902-75510 050714-22256/ Q01207989

Mismatched Duration with Open and Change Times in G-CDR

38 G411_01209134ACT_CTPCMC Q01209134 CTP zero Volume Auth Response. 39 G411_01209134ACT_CTPSSP Q01209134 CTP zero Volume Auth Response.

40 G411_01209825_GTP Q01209825 Volume based prepaid calls handled incorrectly with QCT enabled

41 G401_01215447_GTPP G411_01215447_GTPP G41_01215447_GTPP

050726-34778/ Q01215447 IPCMGR instance 76 memory leak

27



42 G411_01216017ACT_AAA G41_01216017ACT_AAA

050921-94107/ Q01216017

DCC Server is Unresponsive After receipt of Service Profile

43 G411_01220788_TIMER G41_01220788_TIMER Q01220788 SN Timer task failed as entry is not removed from the

timer list.

44 G401_01222269_GTP G411_01222269_GTP

050819-61181/ Q01222269

Failed to generate partial G-CDRs when triggered by TimeOfDay event

45 G411_01226041_VPN 050928-01902/ Q01226041

Toggling "ignore DF bit" does not change MTU on VRF-VPN interface

46 G411_01226544_PSPMGR G41_01226544_PSPMGR

050908-80411/ Q01226544

PDP Context rejected due to SSM stuck in "dumping core" status

47 G401_01228731EMG_HTTP G411_01228731EMG_HTTP G41_01228731EMG_HTTP

050927-01081/ Q01228731

SSM traps due to large number of "HTTP/" in a response packet

48 G401_01229594_GTP G411_01229594_GTP G41_01229594A_GTP

051005-09501/ Q01229594

GGSN send DCC CCR “Reauth’ and CCR QHT when it should not

49 G411_01229609_GTP

050817-58016 050920-93400/ Q01229609 Q01205868

Incorrect billing in case of denied coupons.

50 G411_01230812_IFMGR 050825-67082/ Q01230812 Line Card Programming Disabled for ALC Card

51 G411_01234055_GTP 051007-12991/ Q01234055

Total Usage Report after Tariff Change Not Reported Correctly

52 G411_01238332_BGP 050926-98964/ Q01238332 Failed to route MPLS VPN packets

53 G411_01241520_GTP G41_01241520_GTP

051020-26944 051020-26976/ Q01241520

Diameter Abort Message Led to CMC Switchover

54 G411_01244237_DRIVER G41_01244237_DRIVER

051014-20335/ Q01244237 Management Port on Active CMC not accessible

55 G411_01250109_GTP 051104-43022/ Q01250109

GGSN is not sending total time usage for a denied coupon.

56 G411_01256686A_GTP 051103-41530/ Q01256686

GGSN reporting wrong total time usage in the final CCR

57 G411_01258511EMG_WAP G41_01258511EMG_WAP

051117-57256 051123-63173/ Q01258511

WAP fragmented result SSP core dump

58 G401_01257941B_G50UPGRADE G411_01257941EMG_ISPMGR Q01257941 Default ISP status down after upgrade

59 G411_01098745_MPLS Q01098745 MPLS robustness patch

60 G401_01207102_LI G411_01207102_LI Q01207102 GGSN resync may result in an invalid connection to ADMF

61 G411_01223788AACT_P2ROUTING * Q01223788 BGP capability not recognized by BGP peer

62 G411_01240398_TF G41_01240398_TF Q01240398 Incorrect handling of egress packets due to SSM redundancy

63 G411_01267085_DCC G41_01267085_DCC Q01267085 No Rulebase-Id AVP sent in CCR(I) when no static

CBB is configured

64 G411_01343676EMG_GTP 060327-87915/ Q0134676 Inaccurate CDRs are generated

65 G411_01378249_GTP 060503-27145/ Q01378249 GGSN Handles Empty PAP Password Incorrectly

66

G411_01119420_DCC G41_01119420A_DCC G411_01119420_GTP G41_01119420A_GTP

Q01119420 CCR(T) not sent upon invalid CCA

28



67 G41_01171008ACT_GTP G401_01171008ACT_GTP G411_01171008ACT_GTP

Q01171008 Disallow RADIUS Interim Messages

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


1 041006-14445/ Q01004653 Not able to recover FELC Card 10 once its pulled out

2 050204-45527/ Q01077079 New commands should be described in the help menus

3 050203-43562/ Q01083852 L2TP Logic & Extended Lifetime Timer

4 050217-59657/ Q01084380 SSM 2 in slot 1 has missed poll 2 iterations.

5 050222-63027/ Q01092730 Mismatch with doc 411-5221-200: /etc/shasta/scs.conf is not backed up

6 050307-78913/ Q01095367 Show sgsntracker should give useful timestamps

7 050307-78905/ Q01095385 Process for populating image file MOTD w/copy image

8 050301-71975/ Q01097640 SCS accounting_time_interval modification

9 050310-82427/ Q01100242 Diameter – PDP Context delete response

10 050222-62944/ Q01104429 Log file not present in the backup to tape

11 050323-96952/ Q01106127 RADIUS Auth messages not captured by Trace_Tool for L2TP

12 050322-95532/ Q01106147 Diameter - Unknown-RuleBaseId-in-CCAInitial CCFH=continue

13 050303-74978/ Q01106161 VPRNLink stats not present in log monitor and inaccurate in the .acc file

14

050329-02064 050330-03691 050330-03860 050331-05213/ Q01109663

Problems with stats after clock change to summertime

15

050328-00822 050407-13303 050413-19868 050516-55855/ Q01113502

SSM resets when a web anonymized URL address is passed in for a CBB policy

16 041209-87023/ Q01115006 "WARNING, ALC slot 4 ICP 1 CAM 1 is FULL" log

17 050302-73775/ Q01119364 SCS mismatch timestamps

18 050417-24326/ Q01121302 CMC3 recovery time not reported in GGSN4.1Monitoring Guide

19 050414-22148/ Q01121415 HW and Install Document clarification needed

20 050321-93813/ Q01124968 IP routing table does not take over preferred BGP

30



21 050427-35655/ Q01126368 Problems with RADIUS connection after resync

22 050427-35830/ Q01126382 GGSN responds to a DCC RAR from a different Server

23 050515-55517/ Q01139502 “show hist sm” output has wrong spelling for SM.NbrActCbbCtxt

24 050516-56988/ Q01139560 Entries are shown differently in SCS and “show hist” output

25 050307-77885/ Q01140415 IFMGR connection list corruption

26 050419-26586/ Q01142619 No warning occurs if an assigned network element is deleted

27 050126-33472/ Q01148817 FTB Duration field in G-CDR does not reflect record

28 050520-62972/ Q01152063 Single patch is downloaded to two directories on GGSN

29 050215-55943/ Q01154045 Idle timeout is not working to L2TP VPN

30

050418-24685 050804-44999 050411-17030 050714-22376/ Q01154106

GGSN accounting CSV file start time is 1 second before the stop time

31 050201-39273/ Q01169598 Interface responding to incorrect address

32 050607-80075/ Q01170312

With multiple profiles from RADIUS the call is rejected if the second profile contains upper case letters

33 050708-15948/ Q01171066 “add arp” and “clear arp” behaving differently

34 050719-27126/ Q01179076 Cannot select correct SCS backup file for restore procedure

35 050714-22175/ Q01182533 GGSN out of sync after upgrade of SCS server

36 050728-38424/ Q01188024 Can not view security logs

37 050727-36208/ Q01188508 No status in monitor chassis for the management port in card 13.

38 050802-42139/ Q01203290 Service policies not supported on GGSN should be removed

39 050323-97002/ Q01203053 L2TP tunnel unusable when being deleted (LNS redundancy)

40 050901-74361/ Q01204634 Alarms in SCS GUI have incorrect severity and timestamp

41 050907-78707/ Q01209734 Session error in the SCS GUI after applying patches & resync

42 050809-49455/ Q01209840 Following an SCS rollback test, got an exception on the upgrade test

43 050824-65539/ Q01213348 Same MAC address on active/standby CMC mgmt-port

31



44

050901-74694/ 050901-74739/ 050901-74766/ 050902-75473/ 050902-75510 Q01213822/ Q01216002/ Q01216004/ Q01216010/ Q01216011

G-CDR duration not the same as closing timestamp subtracted from opening timestamp

45 050902-75497/ Q01214511 GGSN erroneously reports billing data for hung GTP sessions

46 050906-78206/ Q01216025 Description for OAM SCP stats does not state for CTP-only

47 050922-95798 050926-99113/ Q01222190

Not possible to modify default-isp security policy

48 050915-88778/ Q01223788 BGP IOT Problem (Capability not recognized by BGP peer)

49 050926-99117/ Q01224118 Out of Sync because cpn list is linked to a firewall policy

50 050727-36301/ Q01224315 New accounting elements can not be displayed and added

51 050923-97694/ Q01226808 Problems when adding a new diameter profile

52 050920-92889/ Q01228447 SSM failure due to NULL flow

53 050912-83798 050912-83811/ Q01231295

Charging problems when a PDP context in use is reused

54 051006-11608/ Q01241534 No access rights to the tftpboot/patches to apply a patch

55 051020-26370/ Q01242166 Predictable TCP sequence numbering

56 051014-20711/ Q01248891 Documentation requires clarification on Charging Characteristics behavior

57 050928-02605/ Q01249313 GGSN does not close the PDP context when an CCA-Initial received with no MSCC AVP

58 051107-44767/ Q01250783 Wrong counters on APN_DATA_Stats

59 051020-26396/ Q01258443 Vulnerable LDAP directory

60 051102-40350/ Q01258819 Health check monitor procedure clarification

61 051109-47347/ Q01261217 ARP failure on Gi-interface

62 060202-29624/ Q01322881 SCSAdmin restore system script fails

63 060214-42611/ Q01319451 GGSN Event Diagnostic enabled after SCS upgrade

64 060307-65240/ Q01329834 Incorrect error displayed for RADIUS on SCS Client

65

060505-29642 060522-47469 060822-51785/ Q01396921

Patches Get Stuck In A Loaded State

32



66 061026-25201 061122-55004/ Q01219437

SSP traps due to a NULL hostname in the HTTP request

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

Disruptive Special Patch Id PKG Title CR Number Dependencies /

Prerequisites Nature of

Patch Apply Remove Handling2

G501_01584892EMG_PATCHMGR

EMG L2TP Tunnels Bouncing After Patch Profile Application

Q01584892 Corrective N N Y

G501_01456493_BGP 1

VLAN BGP VPN-bgp-vprn task suspend on undebug bgp

Q01456493 Corrective N N N

G501_01458665_GEN 1

Data packets were not counted in GCDR container when no default


G501_01339320ACT_GTP

1/ ACT

Set delete message N3/T3 to 1/0 for slow SGSN response

Q01339320-06 Product Improvement N N N

G501_01320881ACT_CTP

1/ ACT

Customer SCP server does not recognize the CTP message.

Q01320881-02 Corrective N N N

G501_FF01322496ACT_INF

1/ ACT

Turn on In Seq. Handling for CBB flows Q01322496-05 Corrective N N N

G501_01455385EMG_VPN EMG

CMC Switchover Due to Messaging Race Condition Between Tasks



1/ ACT

Cabcharge L2TP Authentication Feature Q01435785-01

Commercially Restricted Feature1

N N N

G501_01458672_CONFMGR 1

Confmgr Task Suspension Due to Memory Trampling



1/ ACT

DCCv2 Customization - Essentials Feature Q01368038-03


N N N

G501_01458800_DCC 1

Wrong set of Rating Groups reported in CCR(T)


G501_01461557_DCC 1

Incorrect MSCC sent when data sent after FUI Action TERMINATE.


G501_01223788ACT_P2ROUTING

1/ ACT

BGP capability not recognized by BGP peer Q01223788-08 Corrective N N ?

G501_01453702ACT_L2TP

1/ ACT

PDP Context Rejected After Both LNS Servers Have Recovered

Q01453702-02 Corrective Y Y N

G501_01465070_SVC 1

Service Redirect downlink packets get rated at default rates


G501_01455575_RMC 1

On switchover, GGSN configuration is not loaded.


G501_01407873_STATS 1 Invalid Start/Stop time in

Overload stats Q01407873-02 Corrective N N N

35





G501_01448864_GTP 1 Bulk-Billing Buffer

Overrun Q01448864 Corrective N N N

G501_01471496_AAA 1

GGSN Not Sending RADIUS Access Request For Anonymous Auth Call


G501_01471531_CARDMGR 1 Command to update

SSC3 XFPGA firmware Q01471531 Corrective N Y N

G501_01470153_PPP 1

Anonymous RADIUS Auth option not working properly for PPP calls


G501_01472795_SERVICES 1 SSM Reset Due To

Corrupt WAP Packet Q01472795-02 Corrective N N N

G501_01477654GEN_SVC 1

SSP resets when processing IP in IP encapsulated packets


G501_01425381ACT_SPS

1/ ACT

Force Route Advertisement for VPRN Q01425381-01 Corrective N N N

G501_01303278_LI 1

CMC Switchover occurred when LI specific errors were reported


G501_01467399_RMC 1

No Coredump When CMC Switchover Inside Interrupt Handler


G501_01482527_LI 1

"LI Only When Roaming" Traces All Targets


G501_01476591_RMCMGR 1

SFC Switch Does Not Complete Without Standby CMC


G501_01341393A_ACCT 1

Incorrect G-CDR Duration and QoS Container ChangeTimes

Q01341393-10 Corrective Y Y Y

G501_01463601_SUB 1

After 2G/3G handover the AVP RulebaseID is empty


G501_01447784A_WAP 1 Some Packets Are Not

Counted For Billing Q01447784-02 Corrective N N N

G501_01220782_L2TP 1 CMC switchover caused

by suspended L2TP task Q01220782-06 Corrective N N N

G501_01456362_GTP 1

Parking Meter does not handle time usage during reauths correctly Q01456362

P[G501_01461557_DCC G501_01341393A_ACCT]

Corrective N N N

G501_01489025EMG_SUBMGR EMG

SUBMGR CLI commands can cause a CMC switchover


G501_00958750_ISN 1

Incomplete Machine Check Exception Information


G501_01475230_AAA 1

Incorrect format of CHAP password in IP call


G501_01471454_TF 1

SSM failure due to a misconfigured CBB policy


36





G501_01461192_VPN 1

Synchronous RPC deadlock in VPRN call model.


G501_01506406_GTP 1 Time of Day Events

Cause Inaccurate Billing. Q01506406 P[G501_01456362_GTP] Corrective N N N

G501_01467598_SERVICES 1 Wrong Byte Count For

Tariff Switch CDR Q01467598-01 Corrective N N N

G501_01448554_NETINET 1

Reduce TCP MSS to optimize the operation of CMC2 OAM port


G501_01497263_SFC 1

No Coredump on CMC Switchover if Active SFC is in Slot 8


G501_01450817A_IFMGR 1

Shasta hung/cored after adding AuxEth Mgmt(on ELC)


G501_FF01385579ACT_DCCCMC

1/ ACT

Parking Meter Charging Enhancement Feature Q01385579-02


Y Y Y

G501_FF01385579ACT_DCCSSP

1/ ACT

Parking Meter Charging Enhancement Feature Q01385579-02 P[G501_0145636

2_GTP]


Y Y Y

G501_FF01385577ACT_ERCMC

1/ ACT

DCCv2 Envelope Reporting Feature Q01385577-02

P[G501_01458800_DCC G501_01341393A_ACCT]


Y Y Y

G501_FF01385577_ERSSP5 1

DCCv2 Envelope Reporting Feature

Q01385577-02

P[G501_01461557_DCC G501_01456362_GTP G501_01341393A_ACCT G501_01506406_GTP]


Y Y Y

G501_01502203ACT_GTPACCT

1/ ACT

Unexpected Partial G-CDRs Generated for Fallback/Fallforward

Q01502203 Product Improvement N N N

G501_01505119ACT_SNTP

1/ ACT

Invalid IP address for SNTP Client Configuration

Q01505119-01 Corrective N N Y

G501_01502838_SUB 1

Empty Rulebase ID AVP on DCC after an update request.

Q01502838 P[G501_01463601_SUB] Corrective N N N

G501_01520645_PPP 1

L2TP Anonymous Authentication With Null User Name Is Mishandled

Q01520645 P[G501_01470153_PPP] Corrective N N N

G501_01532148_PATCHMGR 1

GGSN Loses Sync with SCS when Large Patch Profiles are Used


G501_01477576_SERVICES 1 SSM Crashes Due To

Incorrect Memory Access Q01477576-01 Corrective N N N

G501_01505992_TF 1

Incorrect billing of retransmitted fragmented URLs


G501_01525283_TF 1 WAP2 redirect not

working Q01520645 Corrective N N N

37





G501_01531853_GTPACCT 1

Inconsistent Byte Counts in CBB Extension and Traffic Volume Container

Q01531853 P[G501_01458665_GEN] Corrective N N N

G501_01492892_RPC 1

Call Setup Delay After Processing RADIUS ACCESS ACCEPT


G501_01334913_DST 1

Support For Western Australia Daylight Savings Time Rules

Q01334913-07 Corrective Y Y Y

G501_01510180_LI 1

ADMF/DF connection are not automatically restored


G501_01467417_GTP 1

Some Null Radius Attributes Fail Authentication


G501_01521498_ISPMGR 1

GTPBILL configuration loss after manual CMC switch


G501_01505394EMG_ACCT EMG Trap And Switchover

Freeing Billing Context Q01505394-01 Corrective N N N

G501_01522673EMG_WRAP EMG

CMC Switchover Due to Invalid WRAP Reply Packet


G501_01570191EMG_SVC EMG SSM Crashes Due To

Poisoned Memory Access Q01570191-02 Corrective N N N

G501_01527169AEMG_GTP EMG

SSM Traps & Usage after update incorrect when Exclude QCT enabled Q01527169

P[G501_FF01385577_ERSSP] M[G501_01527169_GTP]

Corrective N N Y

G501_01540209_DCC 2

Incorrect Handling of Denied Diameter Coupon rate


G501_01525343_XPIF 2

Adding Packet Spreading Feature on the GELC Card

Q01525343-01 Corrective ? ? N

G501_01457187ACT_GTP

2/ ACT

PDP Context Rejected Due To a Hung Session On GGSN


G501_01498128_CTP 2

Failure To Encode MCC/MNC Values In SCP Messages For CTPv1


G501_01540483_GTP 2

The GGSN may Fail to Respond to Create PDP Context Requests.


G501_FF01369144ACT_PPDCMC

2/ ACT

Dual Coupon Feature

Q01369144-01

P[G501_FF01385579ACT_DCCCMC G501_FF01385577ACT_ERCMC]


Y Y Y

G501_01546309_DCC 2

Wrong Reporting Reason Sent After Parking Meter Quota Exhaustion.


G501_FF01369144_PPDSSP 2

Dual Coupon Feature

Q01369144-01

P[G501_01456362_GTP G501_FF01385577_ERSSP]


Y Y Y

38





G501_01449995_AAA 2

RADIUS Accounting ON/OFF Message Sent Before BGP Peer Is Up


G501_01173295ACT_SVC

2/ ACT

IP.OutDataPkt, IP.IncDataOct and IP.OutDataOct counters


G501_01481415_CONFIG 2 Default route not set on

Standby cmc Q01481415-01 Corrective N N N

G501_01467598_GTP 2

Wrong Byte Count For Tariff Switch CDR

Q01467598-05

P[G501_01341393A_ACCT] M[G501_01467598ADBG_SERVICES]

Corrective N N Y

G501_00789291_PSPMGR 2 SSC2 Card Fails To Boot

If SSC3 Card Active. Q00789291-01 Corrective N N N

G501_01450778ACT_IFMGR

2/ ACT

Increase the MTU Size of Gn IP Interface on GELC Q01450778-01 Corrective O O O

G501_01484327AACT_NETINET

2/ ACT

Potential Call Processing Degradation Due To Certain ARP Traffic


G501_01563238_TF 2 SSC card reset on flow

removal. Q01563238-01 Corrective N N N

G501_01540398_L2TP 2

L2tpmgr Trap on CMC During IP-L2TP Traffic Run


G501_01485541_GTP 2

Unexpected CDRs Generated With Management Intervention Cause


G501_01570531_CONFMGR 2 Critical alarm with "TLB

Load Exception" Q01570531 Corrective N N N

G501_01573968_TRMGR 3, 4 2

Output of MSISDN/IMSI trace tool is missing some information

Q01573968 P[G501_01467417_GTP] Corrective Y Y Y

G501_01565475_GTP 2

Lower Network Activation Rate Due to NoResp.FallBackFallForward


G501_01571556_ISPMGR 2 Memory Leak during a

catchup scenario Q01571556-01 Corrective N N N

G501_01465128_PREREQ 2

Prerequisite For Patch G501_01465128_POLMGR


G501_01544546_AAA 2

RADIUS counter RAD.AcctAvgRTT is not pegged.


G501_01564729_GTPACCT 2

Event Count not Reported Correctly in Billing


G501_01563634ACT_GTP

2/ ACT

Autonomous Clean Up of GTP Sessions Stuck In Disconnecting State

Q01563634 P[G501_01457187ACT_GTP] Corrective N N N

G501_01579195_AAA 2

Historical Counters Are Not Tracking Number Of Addresses In Blackout


G501_01566667_SCP 2

CTP Server Communication Remains in Connect Guard State


39





G501_01522486_POLMGR 2

Show large policy may cause CLI task stack overflow Q01522486-06

P[G501_01465128_PREREQ] M[G501_01522486_WIND]

Corrective N N N

G501_01597060_GTP 2

Incorrect Processing of Re-Auth Response with Multiple Coupons

Q01597060 P[G501_FF01369144_PPDSSP] Corrective Y N N

G501_01540279_GTP 2

Inconsistent Accounting Session ID in L2TP and RADIUS Messages Q01540279-01

P[G501_01341393A_ACCT] M[G501_01536849_PPP]

Corrective N N N

G501_01568521_SSC3 2

SSC3 Packets Drop on bcm5631 (Port10 Buf Full Drops)


G501_01407739ACT_INF

2/ ACT

Radius PAP Authentication Optional Functionality


G501_01571332_OS 2 Packets Dropped on the

SSC3 Card Q01571332-02 Corrective N Y N

G501_01466350ACT_LI

2/ ACT

Enabling Lawful Intercept to use VLAN Connectivity to the Network

Q01466350-02 Product Improvement N N Y

G501_01589010_GTP 2

PDP activation with extended QoS values rejected by the GGSN


G501_01658130EMG_GTP EMG

CMC Switchover Due To GTP Task Stack Corruption


G501_01621446EMG_GTP EMG

PCO IE Not Sent To Subscriber When Invoking DHCP


G501_01640324EMG_ISN EMG

Redundant RIP Instance Removed After GGSN Reboot Or CMC Switchover

Q01640324 - Corrective N N N

G501_01649169EMG_EMS EMG

CMC Switchover Due to Suspended SCS Monitor Task

Q01649169-01 - Corrective N N N

G501_01034740_SDK 3

VPRN Mesh Encrypted Sessions Fail On SSC3 Cards


G501_01427052_SVC 3

GGSN drops packet following an out of sequence FIN

Q01427052-02

P[G501_01465070_SVC] Corrective N N N

G501_01571150ACT_POLMGR

3/ ACT

Scope & Policy Removal From The SSP May Cause Service Degradation

Q01571150 M[ G501_01571150_POLMGR]

Corrective N N N

G501_01465128A_POLMGR 3

Sub Commit Failure With Missing Service Policy Or Scope On SSM Q01465128-

07

M[G501_01465128_POLMGR]

P[G501_01465128_PREREQ G501_01571150ACT_POLMGR]

Corrective Y Y N

40





G501_01508641ACT_DCC

3/ ACT

GGSN Padding 'f' To IMSI In CCR Messages Q01508641 - Corrective N N N

G501_01510386_GTP 3

CMC Reset and Switchover Due to Show GTP Session CLI Command


G501_01574829_IFMGR 3

IPSec Tunnel Modification Impossible Because of Session Errors


G501_01579523_GTP 3

Reauth Response Handled Incorrectly If Parking Meter Is Active

Q01579523 G501_FF01369144_PPDSSP Corrective N N N

G501_01591035_GTP 3

SSM Trap Following DST Change Due To Absolute Lifetime Triggers

Q01591035-03 Preventive ? ? Y

G501_01592120_GTP 3

PDP Context Deletion Takes Too Long Under Certain Error Condition

Q01592120-01

G501_01563634ACT_GTP Corrective N N N

G501_01593019_GTP 3

PDP Contexts Rejected After A Resync Due To A Large CBB Policy


G501_01595094AACT_AAA

3/ ACT

GGSN Always Sends A Password To RADIUS Within Access Requests

Q01595094-05

M[: G501_01595094ACT_AAA]

Corrective N N Y

G501_01598374A_TRMGR 3

Incorrect Values In Trace Tool Logs Q01598374-

01

M[: G501_01598374_TRMGR] P[G501_01573968_TRMGR]

Corrective N N N

G501_01614712ACT_DCC

3/ ACT

3GPP Rel 6 Gy Diameter CC Conformance Q01614712 -

3GPP TS 32.299 v6.7.0 Conformance

N N O

G501_01616587_AAAMGR 3 Incorrect Statistic

Duration Interval Q01616587-01 - Corrective N N N

G501_01622157_GTP 3 Potential SSP Invalid

Data Access Q01622157 G501_FF01385577_ERSSP Preventive N N N

G501_01637622_DHCP 3

Console Information Log 'spar_insert: bad index'


G501_01639302_GTP 3

PDP Context Fails To Clean-up Under Certain Error Condition

Q01639302 G501_01467598_GTP Corrective N N Y

G501_01639328_PSPMGR 3

No Information Provided in the Logs on SSC3 Card or SSM Reset


G501_01646145A_PPDCMC 3

Dual Coupon Validity Timer Q01646145-

03

G501_FF01369144ACT_PPDCMC

Corrective N N N

41





G501_01646145A_PPDSSP 3

Dual Coupon Validity Timer Q01646145-

03

M[: G501_Q01646145_PPDSSP] P[G501_FF01369144_PPDSSP]

Corrective O O O

G501_01649046_GTP 3

Overwrite "Last Sent LCP Confreq" AVP with PAP for Anonymous Auth

Q01649046 G501_FF01435785ACT_INF Corrective N N N

G501_FF01510131ACT_CPM

3/ ACT

Consecutive Parking Meter Feature Q01510131 G501_01573968

_TRMGR


N N N

G501_01655676_CPM 3

First PM-series After Time Limit Trigger Begins One Second Early

Q01655676-01

M[: G501_01655676LTD_CPM] P[G501_FF01510131ACT_CPM]

Corrective N N N

G501_FF01567650ACT_IPCMC

3/ ACT

TCP MSS Clamping

Q01567650

G501_01341393A_ACCT G501_01540279_GTP


O O O

G501_FF01567650_IPSSP 3

TCP MSS Clamping

Q01567650 G501_01173295ACT_SVC


O O O

G501_01662594ACT_SVC

3/ ACT

Allow VPN Uplink Multicast Passthrough Q01662594 G501_FF01567

650_IPSSP Corrective N N N

G501_01663833_GTP 3

Trap Due To Nonzero Length NULL Username RADIUS ACCESS Message

Q01663833 G501_01595094AACT_AAA N N N

G501_01665758_GTP 3

Duplicate IMSI/NSAPI Context Allowed to be Established


G501_01672073_P2ROUTING 3

Cannot Establish BGP Peer When Using Extended Communities.


G501_01679901_SCHEDULER 3 Traffic Shaping Service

Corrections Q01679901 - Corrective N N N

G501_FF01643275_ERDCC 3

Make Service Specific Units Not Mandatory In VF DCC Envelope AVP

Q01643275 G501_FF01385577ACT_ERCMC


N N N

G501_01648984EMG_AAA EMG

Incorrect User Name Length When Trim Option Is Enabled

Q01648984 G501_01471496_AAA Corrective N N N

G501_01730666EMG_EMS EMG

CMC Switchover Due to Deletion of Traffic Profile with Long Name


G501_01693452EMG_DCC EMG

CMC Switchover Due To DCC Task Stack Corruption Q01693452

P[G501_FF01369144ACT_PPDCMC G501_FF01385577ACT_ERCMC]

Corrective N N N

42





G501_01084397_ISN 4

Ensure Correct Tracebacks on SSC3 are Generated


G501_01296296_ELCMGR 4

Failure To Bring the GELC/FELC In Service Following Manual Reset


G501_01439788_ELCMGR 4 SFC Switchover Causes

CMC To Reset Q01439788-05 - Corrective N N N

G501_01616522_GTP 4

Incorrect Time Usage Reported When Coupon Type Changes to PM

Q01616522-01

P[G501_01646145A_PPDSSP] Corrective N N N

G501_01646131_GTP 4

GCDRs Generated with Durations Larger Than Maximum Allowed Q01646131-

01

P[G501_FF01385577_ERSSP] M[: G501_01646131LTD_GTP]

Corrective N N N

G501_01653102ACT_GTP

4/ ACT

N3 Echo Response Message Event Logs Always Enabled

Q01653102-01 - Corrective N N Y

G501_01665444A_NZDST 4

Support For New Zealand Daylight Savings Time Changes Q01665444-

02

P[G501_01334913_DST] M[: G501_01665444_NZDST]

Corrective N N N

G501_01671291_PSPMGR 4

CMC Failure Due To Invalid CPU Free Memory Stats Reported By SSP


G501_01678228_NETINET 4 Unaligned Address

Warnings On SSC3 Q01678228 P[G501_FF01567650_IPSSP] Corrective N N N

G501_01685548_GTPACCT 4

Tariff Switch For Prepaid Session Too Early

Q01685548 P[G501_01467598_GTP] Corrective N N N

G501_01692169_GTP 4

L2TP Sessions Deleted After IRAU Q01692169

P[G501_01502203ACT_GTPACCT]

Corrective N N N

G501_01717665_P2ROUTING 4 Subscriber IP Address

Not Updated in FIB Q01717665 - Corrective N N N

G501_01720452_GTP 4

False HCM Alarm Due to Incorrect SM.FailActPdpCtxt.SYSF.Other Peg


G501_01726458_PPDCMC 4

Incorrect Tariff Change Information For Prepaid

Q01726458 - Corrective N N Y

G501_01726458_PPDSSP 4

Incorrect Tariff Change Information For Prepaid

Q01726458 P[ G501_01597060_GTP]

Corrective N N Y

G501_01726913_GTP 4

Incorrect GCDR Creation Due To Maximum Parking Meters Reached

Q01726913 P[ G501_01456362_GTP]

Corrective N N N

G501_01751739_ELCMGR 4

CMC Reset Due to "show elcmgr xpif" CLI Command


43





G501_01754747_AAA 4

Records Not Automatically Sent To Recovered RADIUS Server


G501_01758063_GTP 4

GGSN Uses Wrong Diameter Termination Cause in CCR


G501_01768103_AAA 4

Incorrect Timestamps for Local Address Pool Historical Statistic


G501_01772149_GTPACCT 4

SSM Trap Due to Data Access NULL Pointer Q01772149

P[ G501_01564729_GTPACCT]

Corrective N N N

G501_01777364_GTPACCT 4 G-CDRs on CMC Disk

Not Transferred to CGF Q01777364 - Corrective N N N

G501_01778204ACT_GTP

4/ ACT

Incorrect DCC Tariff Time Change Report Q01778204

P[G501_FF01369144ACT_PPDCMC]

Corrective N N Y

G501_01783408_FLOWMGT 4

SSM Missed Poll/Reset Due to Generated Flows From P2P Application

Q01783408 - Corrective N N Y

G501_FF01727897_GTP 4

TCP MSS Config Not Retained After Reboots, Resyncs and CMC SOs

Q01727897 P[G501_FF01567650ACT_IPCMC]

Corrective N N Y

G501_01647042EMG_P2ROUTING

EMG

Switching The IP Address Allocation Method Causes CMC Switchover

Q01647042-01 - Preventive N N N

G501_01613913EMG_SERVICES

EMG SSM Reset Due To Corrupt WAP Packet Q01613913-

02 P[G501_01472795_SERVICES] Corrective N N N

G501_01751095EMG_L2TP EMG

SSM Reset Due to Incorrect Counter Handling in L2TP


G501_01772089EMG_PPP EMG

Telnet to the GGSN Fails With Possible CMC Switchover

Q01772089 P[G501_01467417_GTP] Corrective N N N

G501_01776053EMG_SUBMGR

EMG Updating QoS profile May Cause CMC Switchover


G501_01743059AEMG_CONFMGR

EMG

Primary Version DB Not Saved To Disk Resulting in Out of Sync

Q01743059-04

M[: G501_01743059EMG_CONFMGR]

Corrective N N Y (Lab Test Instructions)

EMG and Patch Package 5 patches

G501_01810161EMG_GTP

EMG

CMC Switchover Due To GTP Task Stack Corruption Q0181016

1

M[: G501_01457387DBG_ACCT] P[G501_FF01385577ACT_ERCMC]

Corrective N N N

G501_01809632EMG_SVC

EMG

CMC Switchover Due to Memory Access Error

Q01809632 - Correctiv

e N N N

44





G501_01808187EMG_SVC

EMG

SSM Reset Due to Access of Invalid Subscriber Connection

Q01808187

P[G501_FF01567650_IPSSP]

Corrective N N N

G501_01792196EMG_GTP

EMG

L2TP Call With RADIUS Accounting May Cause NULL Pointer Exception

Q01792196 - Preventiv

e N N N

G501_01785485EMG_GTP

EMG

Potential CMC Switchover When Closing DCC Prepaid Calls


e N N N

G501_01815222EMG_NETINET

EMG

CMC Switchover Due to Data Access Race Condition


e N N N

G501_01694092EMG_GTP

EMG

CMC Switchover Accessing Already Freed GTP Context

Q01694092-01 - Preventiv

e N N N

G501_01795346EMG_TARPATCHER

EMG

No Core Files Are Generated After Processor Soft Reset


e N N Y


EMG

Potential SSM Reset On CBB Policy Modification


e N N N

G501_01839550EMG_GTP

EMG

SSM Reset Due to Accessing Invalid Data Context

Q01839550

P[-G501_01726458_PPDSSP]

Corrective N N Y

G501_01871586EMG_PAR

EMG

CMC Target Patcher Task Becomes Unresponsive

Q01871586

- Corrective N N N

G501_01818382_ISAKMP 5 IKE and IPSEC

Tunnel Failures Q01818382 - Correctiv

e N N N

G501_01726540_PPDSSP 5 Usage During ReauthNot Considered As Before Coupon

Q01726540

P[G501_01616522_GTP]

Corrective N N N

G501_01793902_GTP 5 The Order of Some PMs Is Reversed in Record Extension

Q01793902

P[G501_FF01510131ACT_CPM]

Corrective N N N

G501_00950877_FLOWMGT 5

A Large Number of Flow Management Event Logs


e N N Y

G501_01728656ACT_GTPPCMC

5/ ACT

Parking Meter Start Time Later Than Close Time In GCDR Container

Q01728656-02

M[: G501_01728656ALTD_GTPP]

Corrective N N Y

G501_01760965_GTPCMC 5

Timestamp in Service Request Earlier Than Absolute Coupon Lifetime Q0176096

5-01

M[: G501_01760965LTD_GTPCMC] P[G501_01498128_CTP G501_01591035_GTP G501_FF01369144ACT_PPDCMC]

Corrective Y Y Y

http://wds.us.nortel.com/patches/hidden/download.cgi?patch=G501_01839550EMG_GTP&type=GGSN&rel=GGSNS5.0.1&prod=G501_&status=R&download=./Loads/GGSN/GGSNS5.0.1/G501_01839550EMG_GTP.zip�




45





G501_01548395_GTPCMC 5

SSM Reset During Time-of-Day Billing Processing

Q01548395

P[G501_01760965_GTPCMC]

Corrective Y Y Y

G501_01733134A_ACCTCMC 5

Accounting Time Stamp Consistency

Q01733134

M[: G501_01457387DBG_ACCT G501_01733134_ACCTCMC]P[G501_01592120_GTP G501_01341393A_ACCT G501_FF01567650ACT_IPCMC G501_01810161EMG_GTP]

Corrective Y Y Y

G501_01831139ACT_ACCTCMC

5/ ACT

Long Duration GCDRs After SSM Failures

Q01831139

P[G501_01733134A_ACCTCMC]

N N Y

G501_01649155_IPSEC 5

VPRN Mesh Encrypted Sessions Can Trigger Stack Trace Event Logs


e N N N

G501_01773838_SVC 5 Unaligned Address Warnings On SSC3

Q01773838

P[G501_01678228_NETINET]

Corrective N N N

G501_01812458_ISPMGR 5

SNMP Device Agent IP Address Lost Over CMC Switchover and Reload


e N N N

G501_01727860_XPIF 5

GELC Fragmentation Cache Enhancement for Gn

Q01727860-01

M[: G501_01727860LTD_XPIF] P[G501_01525343_XPIF G501_01296296_ELCMGR]

Corrective

Y (only if GELC card exists)



G501_01850843ACT_DCC

5/ ACT

Option To Add the CC-Total-Octets AVP to the Used-Service-Unit AVP Q0185084

3

M[: G501_01850843AAACT_DCC] P[G501_FF01369144ACT_PPDCMC]

Corrective N N Y

G501_01788430_DST 5 Support For Australia Daylight Savings Time Changes

Q01788430

P[G501_01665444A_NZDST]

Corrective N N N

G501_01787184_SVC 5 SSM Reset Due To Empty Flow List


e N N N

G501_01760965_GTPSSP 5

Timestamp in Service Request Earlier Than Absolute Coupon Lifetime

Q01760965-01

M[: G501_01760965LTD_GTPSSP] P[G501_01646145A_PPDSSP]

Corrective Y Y Y

46





G501_01733134_ACCTSSP 5

Accounting Time Stamp Consistency

Q01733134

P[G501_01467598_GTP G501_01540279_GTP G501_01639302_GTP G501_01646131_GTP G501_01341393A_ACCT G501_01760965_GTPSSP G501_01527169AEMG_GTP G501_FF01385577_ERSSP]

Corrective Y Y Y

G501_01670464_CPM 5

First PM-series After Time Limit Trigger Begins One Second Early

Q01670464

P[G501_FF01385577_ERSSP G501_01655676_CPM]

Corrective N N N

G501_01728656_GTPPSSP 5

Parking Meter Start Time Later Than Close Time In GCDR's Container

Q01728656-02

P[G501_01456362_GTP G501_01670464_CPM G501_01733134_ACCTSSP]

Corrective Y Y Y

G501_01801462_ELCMGR 5

SCS Region Server Down While Resync Lead To Change GELC Port Mode


e N N N

G501_01548395_GTPSSP 5

SSM Reset During Time-of-Day Billing Processing

Q01548395

P[G501_01760965_GTPSSP G501_01733134_ACCTSSP]

Corrective Y Y Y

G501_01757795_GTP 5

Auto Re-auth Occurs Following Coupon Switch from Non-QCT to QCT

G501_01757795_GTP

P[G501_FF01369144_PPDSSP]

Corrective N N N

G501_01130502_POLMGR 5

Saving Primary Config While Deleting Policies Causes System Restart


e N N N

G501_01811265_SVC 5 SSM Trap Due to Access of NULL Flow Cache Pointer

Q01811265

P[G501_00950877_FLOWMGT]

Preventive N N N

G501_01726540_PPDCMC 5

Usage During Reauth Not Considered As Before Coupon

Q01726540

P[G501_FF01369144ACT_PPDCMC]

Corrective N N N

G501_01726401_PPD 5

Incorrect Envelope Reported When Switching From Non-QCT To QCT

Q01726401

P[G501_01726540_PPDSSP]

Corrective N N N

47





G501_01798767AACT_GTP

5/ ACT

Display Warning Service Package Not Found In Event Log

Q01798767

M[: G501_01798767ACT_GTP]] P[G501_01733134A_ACCTCMC G501_01540483_GTP]

Corrective N N Y

G501_01796399ACT_SIG 5/ ACT

TEID Not Recognized In Pdp Update Failures


e N N Y

G501_01502203ACT_ACCTSSP

5/ ACT

Long Duration GCDRs for Fallback/Fallforward

Q01502203-06

P[G501_01733134_ACCTSSP]

Corrective N N Y

G501_01529555_OVLD 5 Instance 84 Memory Leak in IPC Module


e N N ?

G501_01649160_INF 5

SSP1 Memory Violation Errors Are Not Printed To Event Log

Q01649160-01 - Correctiv

e N N N

G501_01826783A_STATS 5

Incorrect Historical and "IDLE" HCM Statistics Q0182678

3-02

M[: G501_01826783_STATS] P[G501_01616587_AAAMGR]

Corrective N N N

G501_01831139_ACCTSSP 5

Long Duration GCDRs After SSM Failures

Q01831139

P[G501_01733134_ACCTSSP]

Corrective N N Y

G501_01855017_GTP 5

Periodic Billing Not Generating GCDRs When Expected

Q01855017-01

P[ G501_01831139_ACCTSSP G501_01548395_GTPSSP G501_01502203ACT_ACCTSSP]

Corrective N N Y

EMG and Patch Package 6 patches G501_01858692EMG_PPP

EMG

RADIUS Authentication PPP AVP Class Memory Not Deallocated

Q01858692

- Corrective N N N

G501_01865914EMG_AAA

EMG

CMC3 Switchover w/wo SSC3 Reset Due to RADIUS Profile Modification

Q01865914-01

- Corrective N N N

G501_01885754EMG_RPC

EMG

Active Call Processing Stops for Long Periods of Time

Q01885754-01

- Corrective N N N

G501_01898304EMG_GTP

EMG

CMC Switchover During RADIUS Authentication

Q01898304

- Preventive N N N

48





G501_01794436EMG_GTP

EMG

CMC Switchover Due to Accessing Invalid GTP Context

Q01794436-01

- Corrective N N N

G501_01899346EMG_GTP

EMG

CMC Switchover Due To Accessing Invalid Data Context

Q01899346

- Corrective N N N

G501_01910948EMG_SVC

EMG

CMC Flowcache Resources Exhaustion

Q01910948-01

- Preventive N N N

G501_01799972BEMG_DCC

ACT/ EMG

CMC Switchover Due to Invalid Message Size

Q01799972

M[501_01799972EMG_DCC 501_01799972AEMG_DCC] P[G501_01693452EMG_DCC]

Preventive and Corrective

N N Y

G501_01910471EMG_IFMGR

EMG

CMC Switchover Due To Incorrect PPP GTP Connection Release

Q01910471

P[G501_FF01567650ACT_IPCMC]

Corrective N N N

G501_01863562EMG_POLMGR

EMG

SSC3 Reset Due To CBB Policy Parse Errors

Q01863563

- Corrective N N N


EMG

SSM Reset Due To Long Flow Cache Cleanup Time

Q01877146

- Corrective N N N

G501_01088170_SSH

6 Secure Shell (SSH) Robustness Improvements

Q01088170-06

- Preventive N N Y

G501_01531993_SVC

6 SSM Reset while Taking Down A VPN Subscriber

Q01531993-02

- Corrective N N N

G501_01817401_GTP

6 Synchronous RPC Deadlock When Moving Subscribers

Q01817401

P[G501_01831139ACT_ACCTCMC]

Corrective N N N

G501_01845160_SVC

6 G-CDR CBB Extension Records On APNs Without CBB Policy

Q01845160-02

P[G501_FF01567650_IPSSP]

Preventive N N N

G501_01885672_GTP

6 Stack Trace Due To GTP Context Access To Null Pointer

Q01885672

- Corrective N N N

G501_01814048ACT_DCCCMC

6/ ACT

GGSN Encodes USU AVP Non-Compliant with VF Specification

Q01814048

P[G501_01850843ACT_DCC]

Conformance

N N Y

49





G501_01623918_PATCHMGR

6 CPU Overload Due to Patchmgr Task Not Responding

Q01623918-01

- Corrective N N N

G501_01892881_GTPCMC

6 Periodic G-CDR May Be Generated Early After ULI Change

Q01892881-02

P[G501_01733134A_ACCTCMC]

Corrective Y Y Y

G501_01871689_DCC

6 DCC Messages Truncated Under High Traffic

Q01871689-01

M[G501_01871689LTD_DCC]P[G501_01799972BEMG_DCC]

Corrective N N N

G501_01858233_DCC

6 GGSN May Not Be Able to Establish Connection to Its Diameter Peer

Q01858233-02

M[G501_01858233DBG_DCC]P[G501_01871689_DCC]

Preventive N N N

G501_01900727_DCC

6 GGSN Fails to Establish Connection to Diameter Peer

Q01900727

P[G501_01858233_DCC]

Corrective N N N

G501_01300738_AAA

6 High CPU Utilization When Writing Radius Accounting Files

Q01300738-01

- Corrective N N N

G501_01866089_SCP

6 CTP Server Connection Gets Stuck in Connecting State

Q01866089

- Corrective N N N

G501_01898593_SERVICES

6 Deficiencies in Two CLI Commands

Q01898593-01

- Corrective N N N

G501_01902248_DCCCMC

6 Unaligned Address Warnings On CMC3

Q01902248-02

P[G501_01858233_DCC]

Corrective N N N

G501_01874158_ISN

6 CMC Trap Due to Closing Telnet Session While in VxWorks Shell

Q01874158-01

- Corrective N N N

G501_01851188_DCC

6 GGSN Sends Terminate Request Session After Receiving CCA

Q01851188

P[G501_01540209_DCC]

Corrective N N N

G501_01891689_GTP

6 GTP Data OutErrIndMsg Statistic Is Not Displayed Correctly

Q01891689-01

- Corrective N N N

50





G501_01892881_GTPSSP

6 Periodic G-CDR May Be Generated Early After ULI Change

Q01892881-02

P[G501_01855017_GTP]

Corrective Y Y Y

G501_01860484_GTP

6 GGSN Does Not Take Down GTP Session With a Delete PDPC Request

Q01860484-02

P[G501_01794436EMG_GTP]

Corrective N N N

G501_01906302_AAA

6 Wrong VPN Local Address In Radius Messages After SSM Reset

Q01906302

- Corrective N N N

G501_01902248_DCCSSP

6 Unaligned Address Warnings On SSC3

Q01902248-02

P[G501_01773838_SVC]

Corrective N N N

G501_01841263_ISPMGR

6 GGSN Tries To Send Packets Through A Disabled Interface

Q01841263-02

- Corrective N N N

G501_01827380_IFMGR

6 GELC Fragmented Hash Table Is Not Updated When SSM Is Disabled

Q01827380-01

- Corrective N N N

G501_01814048_DCCSSP

6 GGSN Encodes USU AVP Non-Compliant with VF Specification

Q01814048

P[G501_01622157_GTP G501_01726401_PPD G501_01757795_GTP]

Conformance

N N Y

EMG and Patch Package 7 patches G501_01904728EMG_GTP

EMG

CMC Switchover While Processing Error Indication Message

Q01904728

P[G501_01860484_GTP]

Corrective N N N

G501_01877167EMG_IFMGR

EMG

CMC Switchover While Deleting VPN Subscriber

Q01877167

- Corrective N N N

G501_01840578_LI

7 SSM Reset While Running Traffic With Active LI Targets

Q01840578-02

P[G501_01303278_LI, G501_01466350ACT_LI]

Corrective N N N

G501_01863890_LI

7 Potential LI CC Packets Dropped

Q01863890-03

P[G501_01840578_LI]

Corrective N N Y

G501_01840579_MMC

7 Packet Loss In SFC During Heavy Traffic With Large Packets

Q01840579-01

P[G501_00950877_FLOWMGT]

Corrective N N N

G501_01868228_OS

7 IP Packets Dropped Due to Exhaustion of Receive Queue

Q01868228-02

P[G501_01571332_OS]

Corrective N N N

G501_01948838_ELCMGR

7 GELC Lockup Detection and Recovery

Q01948838-02

- Preventive N N N

G501_01912068_RMC

7 Management Port Settings Lost After Resync

Q01912068

- Corrective N N ?

51





G501_01952553_IFMGR

7 Potential Packets Dropped After CMC Switchover

Q01952553

- Corrective N N N

G501_01924305_GTPACCT

7 GTP Accounting Task Hung When Processing Regular Billing Data

Q01924305-01

Preventive N N N

G501_01913874ACT_GTP

7/ ACT

PDP Context Deleted Due To QoS MaxBitRate Set To Zero

Q01913874-01

P[G501_01892881_GTPCMC, G501_01589010_GTP, G501_01623918_PATCHMGR]

Corrective N N Y

G501_01950186ACT_GTP

7/ ACT

Increase MBR and GBR for Downlink Data Throughput

Q01950186

- Corrective N N Y

G501_01559949_AAA 7 Clear RADIUS Profile Statistics Is Not Supported

Q01559949-03

Corrective N N N

G501_01924682_AAA 7 Managing RADIUS Accounting Records Following Loss of Communications

Q01924682

P[G501_FF01727897_GTP]

Corrective N N N

G501_01915668_SVC 7 Enhancement CLI to Increase Flowcache List Sizes on CMC

Q01915668-05

P[G501_01910948EMG_SVC, G501_01924682_AAA]

Corrective Y Y Y

G501_01645361_RT 7 Interface Ping Does Not Use Routing Table

Q01645361

- Corrective N N N

G501_01871092_GTP 7 SHASTA VPN VSA Not Included in G-CDR for GRE PPP Call

Q01871092-03

- Corrective N N N

G501_01867815_GTP 7 N3 Counter Is Not Uniquely Handled Per PDP Context

Q01867815-02

P[G501_01339320ACT_GTP, G501_01904728EMG_GTP]

Corrective N N Y

G501_01902903_SVC 7 SSM Trap Due to Access of Corrupted Flow Cache Pointer

Q01902903

P[G501_01811265_SVC]

Corrective N N N

G501_01950157_PSEUDO

7 Dumping Packets During Debug Can Cause the Node to Become Unresponsive

Q01950157

- Corrective N N N

Patch Package 8 patches G501_01956568_ISNCMC

8 Null-Pointer Access Stack Trace in CMC3 is Printed More Than Once

Q01956568

Corrective N N N

G501_01950900_STATS

8 Incorrect Statistic Duration Interval

Q01950900

P[G501_01826783A_STATS]

Corrective N N N

G501_01992673_DCCCMC

8 Incorrect Error Code Reported by MSISDN Trace Tool

Q01992673-02

- Corrective N N N

52





G501_01939135_GTP

8 Session Timer Table Corruption Due to Race Condition

Q01939135-07

M[G501_01939135LTD_GTP G501_01957703LTD_GTP] P[G501_01885672_GTP G501_01505394EMG_ACCT]

Preventive N N N

G501_01979584_GTP

8 Unused Coupon Rate Might Be Lost

Q01979584

P[G501_FF01369144_PPDSSP]

Preventive N N N

G501_01978420_SVC

8 SSM Reset Due to Invalid Memory Access

Q01978420 Preventive N N N

G501_01979441_SVC

8 SSM Reset Due to Flowcache Invalid Memory Access

Q01979441-02

M[G501_01870149DBG_SVC G501_01818007_SVC] P[G501_01787184_SVC G501_01570191EMG_SVC]

Preventive N N N

G501_01815175A_TIMESSP

8 Incorrect SSP Time Stamp

Q01815175-05

M[G501_01815175_TIMESSP]

Preventive & Corrective

N N Y

G501_01666559_GTP

8 CLI Enhancement to Display Extended QoS Profile Information Element

Q01666559-02

P[G501_01510386_GTP G501_01733134A_ACCTCMC G501_01867815_GTP]

Corrective N N N

G501_01955265_RMC

8 Memory Leak On P1 Module 18 (RPC) Instance 01


G501_01815175A_TIMECMC

8 Incorrect SSP Time Stamp

Q01815175-05

M[G501_01815175_TIMECMC]P[G501_01639328_PSPMGR]

Preventive & Corrective

N N Y

G501_01956568_ISNSSP

8 Null-Pointer Access Stack Trace in SSC3 is Printed More Than Once

Q01956568 P[G501_01084397_ISN]

Corrective N N N

G501_01967407_AAA

8 RADIUS Attribute Acct-Delay-Time has Large Value


G501_01959153_IFMGR

8 FELC Takes Long Time To Response After Reseating Card

Q01959153

P[G501_01450817A_IFMGR]

Corrective N N N

G501_01937813_SVC

8 Updated CBB Policy from Gx May Not Be Used After SSM Redundancy

Q01937813-01

P[G501_01465128A_POLMGR]

Corrective N N N

G501_01992673_DCCSSP

8 Incorrect Error Code Reported by MSISDN Trace Tool

Q01992673-02

Corrective N N N

53





G501_01944567_DCC

8 Possible Authentication Failure During CCR(I)/CCA(I) Exchange

Q01944567-02

P[G501_01851188_DCC]

Corrective N N N

Patch Package 9 patches G501_02001740_SVCSSP

9 Timestamp Of Statistics Is Incorrect

Q02001740 P[G501_01815175A_TIMESSP G501_01950900_STATS]

Corrective N N N

G501_02019884_DST

9 Support For America/Port-au-Prince Daylight Savings Time Changes

Q02019884 P[G501_01788430_DST]

Corrective N N N

G501_02002598_GTP

9 Too Many GTP Billing Logs Generated

Q02002598 M[G501_01996131_GTP] P[G501_01649046_GTP]

Corrective N N Y

G501_02015821_GTP

9 PDP Contexts Not Removed After Session Time Expires

Q02015821 Corrective Y Y Y

G501_02001740_SVCCMC

9 Timestamp Of Statistics Is Incorrect

Q02001740 P[G501_01950900_STATS G501_01815175A_TIMECMC G501_01467598_SERVICES G501_01616587_AAAMGR]

Corrective N N N

G501_02004927_ISN

9 GDC Tool Unable To Telnet To CMC P1 To Collect Data

Q02004927-01

P[G501_01874158_ISN]

Corrective N N N

G501_02023483_AAA

9 RADIUS Accounting Records Not Sent From Disk

Q02023483-02

P[G501_01924682_AAA]

Corrective N N N

G501_02005896_INIT

9 SSC 3 Cards Can Not Generate Encrypted Data Logs

Q02005896 Corrective N Y Y

G501_02018947_SUBMGR

9 APN Configuration Errors Following CMC Switchover or Reload

Q02018947-01

Corrective Y Y Y

G501_02023131_NETINET

9 Incorrect Buffer Usage Causes Hung tNetTask

Q02023131 Preventive N N N

G501_02005047_WRAP

9 WRAP statistics are not collected for all ISPs


G501_FF02007643ACT_DCC

9 DCC Empty Quota Values

Q02007643 Commercially Restricted Feature1

N N Y

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.






http://dpswww.ca.nortel.com/cgi-bin/quickcr.pl?cr_id=Q02004927-01&mode=txt�










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 Appendix B Section “Swapping a Patch Profile” if needed.

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

G501_01484327AACT_NETINET Potential Call Processing Degradation Due To Certain ARP Traffic

G501_01527169AEMG_GTP SSM Traps & Usage after update incorrect when Exclude QCT 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 G501_01814048_DCCSSP

GGSN Encodes USU AVP Non-Compliant with VF 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 Patch Application Handling 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 Patch Application Handling 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. Patch Removal Handling 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 Patch Application Handling 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

61


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. Patch Removal Handling 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.5 G501_FF01385579ACT_DCCSSP Patch Application Handling 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. Patch Removal Handling 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.6 G501_FF01385577ACT_ERCMC Patch Application Handling 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. Patch Removal Handling 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.7 G501_FF01385577_ERSSP Patch Application Handling 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

62


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. Patch Removal Handling 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.8 G501_01510180_LI Patch Application Handling 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 Patch Application Handling 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. Note: This patch replaces G501_01484327ACT_NETINET. If this patch is applied you must remove it before applying this patch. Patch Removal Handling 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.10 G501_01527169AEMG_GTP Patch Application Handling This patch should not be applied during traffic. 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.

63


6.3.11 G501_FF01369144ACT_PPDCMC Patch Application Handling 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. Patch Removal Handling 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.12 G501_FF01369144_PPDSSP Patch Application Handling 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. Patch Removal Handling 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.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 Patch Application Handling 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. Patch Removal Handling 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 Patch Application and Removal Handling 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 Patch Application Handling 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 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. For details on special handling details for patch G501_FF01567650_IPSSP, please refer to G501_FF01567650_IPSSP. Patch Removal Handling 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 Patch Application Handling 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. 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.

66


Patch Removal Handling 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.

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.19 G501_01591035_GTP Patch Application and Removal Handling Exercise CAB 2007007824. 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.

6.3.20 G501_01595094AACT_AAA Patch Application Handling 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 Patch Application and Removal Handling 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 Patch Application and Removal Handling 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 Patch Application and Removal Handling 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 Patch Application and Removal Handling 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 Patch Application Handling Apply this patch together with patch G501_01726458_PPDSSP.

Patch Removal Handling Unapply this patch together with patch G501_01726458_PPDSSP.

6.3.27 G501_01726458_PPDSSP Patch Application Handling Apply this patch together with patch G501_01726458_PPDCMC. Patch Removal Handling 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. Patch Application Handling 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. Patch Removal Handling 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 prior to patch application may have incorrect time stamps. 3. Re-Sync the GGSN. 4. Unapply this patch through the SCS client. 5. Verify that the patch is properly removed. 6. Verify there is no abnormal activity present after patch removal. 7. Allow new GTP sessions on the GGSN. 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.

Patch Application Handling Note: BOTH G501_01548395_GTPSSP AND G501_01548395_GTPCMC MUST APPLIED TOGETHER. 1. Disallow new sessions and close all existing sessions. 2. Mark G501_01548395_GTPCMC and G501_01548395_GTPSSP as persistent. Apply the patches through the SCS client. 3. Verify the patches have been applied on CMC and SSP successfully. 4. Allow new sessions. 5. Verify there is no abnormal activity present after patch application. Patch Removal Handling 1. Disallow new sessions and close all existing sessions. 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. 4. Allow new sessions. 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


DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS FUNCTIONALITY. The following details are taken from the patch PD file. Problem Description: 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 DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS FUNCTIONALITY. Note: The patch G501_01502203ACT_GTPACCT must be activated along with this patch for the functionality to work correctly. The following details are taken from the patch PD file. Problem Description: 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 DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS FUNCTIONALITY. Problem Description: 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. Problem Description: 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. Patch Application Handling Note: This patch will apply to the SSP. 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. 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. Patch Removal Handling 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 prior to patch application may have incorrect time stamps. 3. Re-Sync the GGSN. 4. Unapply this patch through the SCS client. 5. Verify that the patch is properly removed. 6. Verify there is no abnormal activity present after patch removal. 7. Allow new GTP sessions on the GGSN.

6.3.48 G501_01548395_GTPSSP The following instructions are applicable only when adding the patch individually.

Patch Application Handling Note: BOTH G501_01548395_GTPSSP AND G501_01548395_GTPCMC MUST APPLIED TOGETHER.

77


1. Disallow new sessions and close all existing sessions. 2. Mark G501_01548395_GTPCMC and G501_01548395_GTPSSP as persistent. Apply the patches through the SCS client. 3. Verify the patches have been applied on CMC and SSP successfully. 4. Allow new sessions. 5. Verify there is no abnormal activity present after patch application. Patch Removal Handling 1. Disallow new sessions and close all existing sessions. 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. 4. Allow new sessions. 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). DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS 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 Patch Application Handling G501_01726458_PPDSSP must be applied before G501_01839550EMG_GTP can be applied.

6.3.54 G501_01300738_AAA

Patch Application Handling 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 DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS 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.



http://wds.us.nortel.com/patches/hidden/redirect.cgi?patch=G501_01300738_AAA&type=GGSN&rel=GGSNS5.0.1&prod=G501_&status=S&download=./Loads/GGSN/GGSNS5.0.1/G501_01300738_AAA.zip�

http://wds.us.nortel.com/patches/hidden/redirect.cgi?patch=G501_01300738_AAA&type=GGSN&rel=GGSNS5.0.1&prod=G501_&status=S&download=./Loads/GGSN/GGSNS5.0.1/G501_01300738_AAA.zip�

79


6.3.57 G501_01814048ACT_DCCCMC and G501_01814048_DCCSSP DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS FUNCTIONALITY. Please refer the patch PD file for details of the fix.

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. 2. Verify there is no abnormal activity present after patch 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. 2. Verify that the patch is properly removed. 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 Problem Description: 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 DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS FUNCTIONALITY. Please refer the patch PD file for details of the fix.

6.3.62 G501_01950186ACT_GTP DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS FUNCTIONALITY. Please refer the patch PD file for details of the fix.

83


6.3.63 G501_01915668_SVC Field Application Instructions 1. Apply this patch via the SCS client. 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. 3. This patch will apply to CMC. Patch Removal Instructions 1. Unapply this patch via the SCS client. 2. Verify that the patch is properly removed. 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. Field Application Instructions 1. Apply this patch and patch G501_01815175A_TIMESSP via the SCS client. 2. Verify there is no abnormal activity present after patch application. 3. This patch will apply to CMC. 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. Patch Removal Instructions 1. Unapply this patch and patch G501_01815175A_TIMESSP via the SCS client. 2. Verify that the patch is properly removed. 3. Verify there is no abnormal behavior present after

84


patch removal.

6.3.66 G501_02002598_GTP Field Application Instructions 1. Unapply patch G501_01996131_GTP. 2. Apply this patch via the SCS client. 3. Verify there is no abnormal activity present after patch application. 4. This patch will apply to CMC. Patch Removal Instructions 1. Unapply this patch via the SCS client. 2. Verify that the patch is properly removed. 3. Verify there is no abnormal behavior present after patch removal. 4. Follow field application procedures for G501_01996131_GTP and re-apply the patch.

6.3.67 G501_02015821_GTP Field Application Instructions 1. Mark the patch persistent. 2. Apply this patch via the SCS client. 3. Resync the GGSN. 4. Verify there is no abnormal activity present after patch application. 5. This patch will apply to CMC. Patch Removal Instructions 1. Unapply this patch via the SCS client. 2. Verify that the patch is properly removed. 3. Verify there is no abnormal behavior present after patch removal.

6.3.68 G501_02005896_INIT Patch Removal Instructions 1. Unapply this patch via the SCS client. 2. Verify that the patch is properly removed. 3. Verify there is no abnormal behavior present after patch removal. 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 Field Application Instructions

85


1. Mark the patch persistent. 2. Apply this patch via the SCS client. 3. Resync the GGSN. 4. Verify there is no abnormal activity present after patch application. 3. This patch will apply to CMC. 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.

Patch Removal Instructions 1. Unapply this patch via the SCS client. 2. Verify that the patch is properly removed. 3. Verify there is no abnormal behavior present after patch removal.

6.3.70 G501_FF02007643ACT_DCC DO NOT ACTIVATE UNLESS YOU UNDERSTAND AND REQUIRE THIS FUNCTIONALITY. Field Application Instructions 1. Apply this patch via the SCS client, and Activate it only if the functionality is desired. 2. Verify there is no abnormal activity present after patch application. 3. This patch will apply to CMC. Patch Removal Instructions 1. Deactivate this patch and unapply this patch via the SCS client. 2. Verify that the patch is properly removed. 3. Verify there is no abnormal behavior present after patch removal.

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 2 SSC /SSC Enabled U U U U 3 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 11 SSC /SSC Enabled 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. This is an event log to inform that the overload control has been enabled for CPU usage.

3. INFO Overload: Resource interrupt has been enabled. This is an event log to inform that the overload control has been enabled for 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/

Q01388481 Ancillary APN Statistics are not Reported in SCS Client

4 060322-82159/ Q01388490

Removing SFC Card Generates Alarm With Wrong Card Type

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/

060620-79108 Q01415964

SMNbrCtxtPrepaidToNoPrepCCNotApp Does Not Peg

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

Q01437456-01 “show fib” Command Crashes SSH Session

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/

Q01454341-01 "netcli" Task Exception

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/

Q01388459 All Fan Failure Caused Alarms aren’t Seen in SCS GUI

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-

30631/Q01737685 "show card" CLI output for disabled Ethernet slot and port is incorrect

57 070912-44775/ Q01745586

SCS Editing of Networks Objects Doesn't Save Changes

58 Q01755670 Session errors observed on the SCS after reposition FELC card on the GGSN 59 071004-66154/

Q01759935 Resync required after Reapplication of patch G501_01334913_DST

60 071211-27286/ Q01801692

Dynamic L2TP Tunnel selection not compliant with RFC2868

61 Q01618197-05/ Q01618197-02

64 bit GGSN counters may roll over at 2^32-1

62 061024-22500/ Q01489687

Unknown “healthcheck” Commands During start-up

63 080218-84214/ Q01830205

Modifying Primary Diameter Server

64 080218-84214/ Q01830205

Problem with fallback from SSC3 to SSC2

65 Q01884435-01 Unable to copy GGSN image to /flash

66 080721-16197/ Q01903693

Erroreous Values of chargingIDs for CMC Reboot or Switchover

67 080604-78158/

Q01911533 Clarification on the Maximum Bit Rate Supported by Nortel GGSN5.0.1.

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

2006007476 CMC-3 Trap and Switchover When OSPF Retransmission Interval Is 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

2007007824 GGSN SSM's May Trap Following Daylight Savings Time Change Due To Prepaid Absolute Lifetime Configuration

2007007825 Flow Management Policy Activation Procedure to prevent Flow Cache Exhaustion due to Virus/Worm Attacks

2007007826 Identification of Virus/Worm Infected Ports and Activation of Firewall Security Service Policy

2007007839 GGSN: G501_01341393A_ACCT and G50_01341393_ACCT Forward 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”. 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 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). 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 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.


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. 1. Make sure that Step 8 of Section “Patching Prerequisites” in Nortel GGSN5.0.1 NTP






124



5. Accept patch package 5 and all applicable EMG patches from SCS client -> Patch

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



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.


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.


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.

20. Perform post-application health checks on GGSN following NTP 411-5221-927

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

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-

5221-923 Appendix C if needed. 2. Delete all PDP contexts on SGSN from SCS client (as Gn ISP user) Refer to NTP 411-

5221-923 Appendix C if needed.

3. Close billing records on GGSN and transfer them to the CGF. Refer to NTP 411-5221-923 Appendix C if needed.

4. Swap the current active patch package 5 profile with the previous patch package 4



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-5221-923 Appendix C if needed.

8. Perform post-application health checks following NTP 411-5221-927 Appendix B

Section “Post-Application - Health Check Procedure”.

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-5221-923 Appendix C if needed.

7. Perform post-application health checks following NTP 411-5221-927 Appendix B



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

127










5. Accept patch package 6 and all applicable EMG patches from SCS client -> Patch 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”.





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

128


latest EMG patches and Patch package 6 patches are then added to this clone patch profile. The clone patch profile is then swapped with the active patch profile.



9. Add the latest EMG patches listed in Table 1 as patch rules to the cloned patch profile. 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.

10. Add patch package 6 patches as patch rules to the cloned patch profile. A single click on

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





manager.

129



13.3.5.3 Procedure to Remove Patch Package 6 This procedure details the steps to rollback patch package 6 to patch package 5.










411-5221-927 GGSN Provisioning Procedures - Appendix B: “GGSN Patch

130


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.






5. Accept patch package 7 and all applicable EMG patches from SCS client -> Patch 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”.









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.

10. Add patch package 7 patches as patch rules to the cloned patch profile. A single click on

patch package 7 will auto select/highlight all patches associated with the package. Refer

131


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_01913874ACT_GTP • G501_01950186ACT_GTP

11. Verify if the cloned patch profile with the EMG and patch package 7 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.




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

15. Perform post-application health checks on GGSN following NTP 411-5221-927

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

13.3.6.3 Procedure to Remove Patch Package 7 This procedure details the steps to rollback patch package 7 to patch package 6. Note: A GGSN resync is required following a roll back from package 7 to patch package 6.





132


3. Perform a GGSN resync. 4. Perform post-application health checks following NTP 411-5221-927 Appendix B


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.





411-5221-927 GGSN Provisioning Procedures - Appendix B: “GGSN Patch

133


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.






5. Accept patch package 8 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”.









10. Add patch package 8 patches as patch rules to the cloned patch profile. A single click on patch package 8 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.

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.


13.3.7.3 Procedure to Remove Patch Package 8 This procedure details the steps to rollback patch package 8 to patch package 7. 1. Swap the current active patch package 8 profile with the previous patch package 7




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

http://wds.us.nortel.com/patches/hidden/download.cgi?patch=G501_01527169AEMG_GTP&type=GGSN&rel=GGSNS5.0.1&prod=G501_&status=R&download=./Loads/GGSN/GGSNS5.0.1/G501_01527169AEMG_GTP.zip�

http://wds.us.nortel.com/patches/hidden/download.cgi?patch=G501_01818007_SVC&type=GGSN&rel=GGSNS5.0.1&prod=G501_&status=R&download=./Loads/GGSN/GGSNS5.0.1/G501_01818007_SVC.zip�

http://wds.us.nortel.com/patches/hidden/download.cgi?patch=G501_01996131_GTP&type=GGSN&rel=GGSNS5.0.1&prod=G501_&status=R&download=./Loads/GGSN/GGSNS5.0.1/G501_01996131_GTP.zip�

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

Documents

GGSN_5.0.1_Release_Notes_V_9.0.3