nanoGSM 4.1.8 circuitBSC System Release Note · At the IuBC interface (CBC – BSC interface), and...

The world's most deployed picocell

ip.access Ltd Building 2020 Cambourne Business Park Cambourne Cambridgeshire CB23 6DW United Kingdom

nanoGSM 4.1.8 circuitBSC System Release Note

NGSM_INST_525 1.0

NOTICES

This document is provided to you by or on behalf of ip.access Ltd (“ip.access”).

© ip.access Limited 2011.

The documentation and any software described herein and/or provided to you in conjunction with this documentation contain proprietary and confidential information of ip.access and may only be used subject to a license agreement containing restrictions on use and disclosure. They are also protected by copyright, patent rights and other intellectual and industrial property laws. The information contained in this document and any software described herein is subject to change without notice. If you find any problems in the documentation and/or the software please report them to us in writing. The document and/or the software are not warranted to be error-free. No right, title, license or interest in any physically or electronically distributed materials is transferred to you by such distribution. No part of this document and/or the software may be reproduced, displayed, copied, translated, adapted, downloaded, electronically transmitted, used or reproduced in any form including (without limitation) distribution or storage in a system for retrieval without our express written permission (which may be subject to conditions).

The documentation and/or software may provide links to Web sites and access to content, products, and services from third parties. ip.access is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. ip.access is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. ip.access is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

ip.access is the owner of the “ip.access”, “nanoGSM” and “nanoBTS” trademarks trademark and all associated trade names, logos and devices unless indicated to the contrary. Any other trademarks, logos and names appearing on in this document may be the property of their respective owners. ip.access Limited is a Private Limited Company Registered in England and Wales Company No. 03400157 Registered Office: Building 2020 Cambourne Business Park Cambourne CB23 6DW UK Tel: +44 (0) 1954 713 700 Fax: +44 (0) 1954 713 799 Further company information may be found at www.ipaccess.com.

nanoGSM 4.1.8 circuitBSC System Release Note © ip.access Ltd

REVISION HISTORY

Version Change Summary Date Author 0.1 Draft 06 Sep 2011 PB2 1.0 Released for SR4.1.8 28 Sep 2011 CFB


TABLE OF CONTENTS

1 INTRODUCTION ....................................................................................................... 1

1.1 Important Information about this System Release .............................................. 1

1.1.1 Important Upgrade Actions ......................................................................... 1

1.1.2 New Features added in this System Release ............................................. 1

1.1.3 Major Fixes ................................................................................................. 1

1.1.4 Hardware Changes..................................................................................... 1

1.1.5 New Software Components ........................................................................ 1

1.2 System Release Overview ................................................................................. 1

1.3 About this Release Note ..................................................................................... 1

2 NEW FEATURES IN THIS SYSTEM RELEASE ........................................................ 2

2.1 New Features introduced in this System Release .............................................. 2

2.2 All New Features introduced from System Release 4.1 ...................................... 2

2.2.1 Management Features ............................................................................... 2

2.2.2 GSM/GPRS Features ................................................................................. 3

3 SYSTEM COMPONENTS .......................................................................................... 5

3.1 Updated Software Components in this System Release ..................................... 5

3.2 Full Software Component List ............................................................................ 5

3.2.1 Optional System Components .................................................................... 8

4 INSTALLATION, UPGRADE AND DOWNGRADE INFORMATION ........................... 9

4.1 Installing a New SR4.1.8.0 nanoGSM System ................................................... 9

4.2 Upgrading from Previous System Releases to SR4.1.8.0 ................................... 9

4.2.1 Upgrade Procedure Requirements ............................................................. 9

4.2.2 Upgrade Documentation ........................................................................... 10

4.3 Downgrading from SR4.1.8.0 to Previous System Releases ............................ 11

4.3.1 Downgrade Procedure Requirements ....................................................... 11

4.3.2 Downgrade Documentation ...................................................................... 12

5 DOCUMENTATION ................................................................................................. 13

5.1 Manuals ........................................................................................................... 13

5.2 Online Help ...................................................................................................... 14

5.2.1 OMC-R Client Help ................................................................................... 15

5.2.2 Configuration Manager Help ..................................................................... 15

6 FIXED ISSUES ........................................................................................................ 16

6.1 Issues fixed in SR4.1.8.0 .................................................................................. 16






















7 KNOWN ISSUES AND WORKAROUNDS ............................................................... 31

7.1 Issues in SR4.1.8.0 .......................................................................................... 31

7.2 Detailed explanation of the known issues ......................................................... 33

nanoGSM 4.1.8 circuitBSC System Release Note Introduction © ip.access Ltd Page 1

1 INTRODUCTION This manual contains essential notes relating to the SR4.1.8.0 system release.

1.1 Important Information about this System Release

Read This First SR4.1.8.0 software will operate on the same hardware platform as a SR4.0/SR4.1 system.

1.1.1 Important Upgrade Actions None

1.1.2 New Features added in this System Release There are no new features added in this System Release.

1.1.3 Major Fixes This SR4.1.8.0 release includes all major and critical fixes implemented up to and including SR4.1.7.0.

1.1.4 Hardware Changes The SR4.1.8.0 release does not require any hardware changes.

1.1.5 New Software Components The SR4.1.8.0 release does not contain any new software components.

1.2 System Release Overview System Release SR4.1.8.0 is an update to the existing SR4.1 nanoGSM System.

1.3 About this Release Note This release note contains the following information:

• Summary of new features introduced or updated since SR4.0.

• Summary of system components of the nanoGSM system in this release.

• Installation, upgrade and downgrade information for the nanoGSM system.

• Summary of documentation:

A list of manuals and other documentation included in this system release – refer to this list to find in depth information about the nanoGSM system.

• Known issues and workarounds: A summary of outstanding issues in this release.

nanoGSM 4.1.8 circuitBSC System Release Note New Features in this System Release © ip.access Ltd Page 2

2 NEW FEATURES IN THIS SYSTEM RELEASE

2.1 New Features introduced in this System Release No new features have been added in this system release.

2.2 All New Features introduced from System Release 4.1 The following sections describe the new features added to the nanoGSM System from SR4.1. For more information on the new features introduced since SR4.0 see INST_509.

2.2.1 Management Features

Feature Summary Bulk Parameter Change

The Bulk Parameter Change feature enables OMC-R users to perform bulk changes to the configuration of single or multiple selected Managed Objects of ip.access BSSs. Bulk Parameter Change operation is performed in the following steps: Export the current configuration to XML format. Import the configurations from the XML file into the system. Modify similar configurations across multiple BSS. Scheduling option for these operations is provided to the operator to minimise the impact of loss of service due to these changes.

Heartbeat on AUX Notification Channel

The BSC sends heartbeat notifications periodically to the third party fault management system (Eg: NetExpert) indicating that the BSC is alive. The notification is sent through the CORBA interface. This helps the third party fault management system to be aware of the availability of the BSC.

OMC-R Performance Enhancements

The OMC-R performance enhancement feature primarily aims to improve the OMC-R client user experience. The following modifications are made for this purpose: Selective Management of OMC-R is enhanced to show the “Choose BSSs to Manage” dialog with every user log in. This allows the user to select only the required BSC to be managed. OMC-R client is enhanced to download only Configuration Management data or Fault Management data from the OMC-R server for the selected BSS by selecting appropriate check box in the “Choose BSSs to Manage” dialog. Polling interval is increased to five seconds from one second, if the OMC-R client is in idle state. During active state, the polling interval is one second. Class view in the OMC-R GUI is removed to reduce the memory consumption on the OMC-R client. Disconnected BSSs are shown to the user in the OMC-R GUI. However the user cannot make any configuration changes to the disconnected BSS.


Feature Summary OMC-R PM Aggregation Enhancements

To address issues with respect to the PM Aggregation feature it has been re-designed by changing database schema and introducing hourly and daily aggregation. The following changes have been done to improve overall usability of the system: Data loaded from the BSC performance logs will be loaded into the OMC-R as raw data. These measurements will be aggregated hourly and daily based on their types. Based on the time range selected or present appropriate aggregated values will be shown. If the time range selected is less than 1 day then raw data is shown. If the time range is between 1 to 14 days then hourly aggregation will be shown. For more than 14 days daily aggregated measurements will be shown. Over all user response time to generate reports has been improved significantly.

2.2.2 GSM/GPRS Features

Feature Summary Handover To UMTS

This feature allows multi-RAT capable MS to perform handovers from nanoGSM system to FDD UMTS cells. This is supported on EDGE BTS only. Handover from GSM to UMTS requires that the GSM BSS provide information on potential UMTS handover candidates for the MS to measure. The MS passes GSM and UMTS measurements to the GSM BSS. The Handover Required message from BSS to MSC is sent to indicate that a Handover to UMTS is desirable. If the Core Network determines that a handover to UMTS should be attempted, an Intersystem Handover to UTRAN message will be sent to the MS to initiate the handover. This feature also supports Handover to UMTS during SDCCH Phase of the call.

SMS-Cell Broadcast with CBC (Optional)

This feature supports operation of SMS-Cell Broadcast controlled by an external Cell Broadcast Centre (CBC) using standard protocols at the external interfaces At the IuBC interface (CBC – BSC interface), and the Um interface (GSM air-interface), this feature is compliant with the relevant 3GPP specifications. The internal interfaces within the nanoGSM system use a mixture of standard and proprietary protocols. CBS messages are broadcasted to defined geographical areas known as cell broadcast areas. Individual CBS messages will be assigned their own geographical coverage areas by mutual agreement between the information provider and the PLMN operator. CBS messages are sent from the CBC to the cells, in accordance with the CBS’s coverage requirements.


Feature Summary Dynamic Half Rate AMR

This feature manages the allocation of channels within a single BTS. It allows air interface timeslots to be configured to be assignable as any or all of the following channel types: TCH/F, TCH/H (as well as optionally as PDCH) – see [GSM0502]. This feature provides for lowering blocking during periods of peak circuit traffic, by the allocation of TCH/H to support AMR Half rate speech calls. Depending on the configuration of this feature compared to that of the Dynamic PDCH feature, it may also enhance GPRS throughput by reducing the timeslot needs of the circuit switched traffic due to the use of AMR half rate.

nanoGSM 4.1.8 circuitBSC System Release Note System Components © ip.access Ltd Page 5

3 SYSTEM COMPONENTS

3.1 Updated Software Components in this System Release

Table 1 Updated nanoGSM Software Components

Name Description P/No Version # in this release

Filename(s) in distribution media

BTS software [168] GSM/GPRS nanoBTS software (for 165A, 165B, 165C and 165D only)

168 v200b140d0 168d473_v200b140d0.sdp 168d477_v200b140d0.sdp

BSC software Circuit BSC software 129A v226d0 bsc_129A001-4.1.226-0.i386.rpm

BSS Download Server

BSC download Server Application v73d0 ipaccess-download-server-4.1.73-0.i386.rpm

SSL Proxy SSL Proxy for secure A-bis signalling v169d0 ipaccess-subagent-sslproxy-4.1.169-0.i386.rpm

RTP Proxy RTP Proxy for secure and multiplexed A-bis user traffic

v169d0 ipaccess-subagent-rtpproxy-4.1.169-0.i386.rpm

Gb Over IP Gb Over IP v169d0 ipaccess-subagent-gbip-4.1.169-0.i386.rpm

3.2 Full Software Component List

Table 2 Full list of nanoGSM Software Components


Last updated in release


BTS software [168]

GSM/GPRS nanoBTS software (for 165A, 165B, 165C and 165D only)

168 v200b140d0 4.1.8.0 168d473_v200b140d0.sdp 168d477_v200b140d0.sdp

BSC Software Circuit BSC software 129A v226d0 4.1.8.0 bsc_129A001-4.1.226-0.i386.rpm

SSL Proxy SSL Proxy for secure A-bis signalling

v169d0 4.1.8.0 ipaccess-subagent-sslproxy-4.1.169-0.i386.rpm

RTP Proxy RTP Proxy for secure and multiplexed A-bis user traffic

v169d0 4.1.8.0 ipaccess-subagent-rtpproxy-4.1.169-0.i386.rpm

Gb Over IP Gb Over IP v169d0 4.1.8.0 ipaccess-subagent-gbip-4.1.169-0.i386.rpm

BSS Download Server

BSC download Server Application

v73d0 4.1.8.0 ipaccess-download-server-4.1.73-0.i386.rpm

Circuit BSC Software CD

Circuit BSC software upgrade CD

v148d0 4.1.8.0 4.1.8_circuit_v148.iso

OMC-R OMC-R server software 137 v257d0 4.1.7.0 omcr-4.1.257.0-1.i386.rpm


BTS software [119]

GSM/GPRS nanoBTS software (for 108# and 110#)

119 v300b55d0 4.1.4.0 119a473_v300b55d0.sdp 119a477_v300b55d0.sdp

BTS software [120]

GSM/GPRS nanoBTS software (for 139#, 140# and 178#)

120 v300b55d0 4.1.4.0 120a473_v300b55d0.sdp 120a477_v300b55d0.sdp

GNAT GPRS Network Address Translation

v55d0 4.1.3.0 ipaccess-gnat-55.0-0.i386.rpm

BSC SSD OS CD

BSC custom RHEL4 installation CD for SSD

v23b0d0 4.1.3.0 ipaccess-ssd-OS-CD-v23b0d0.iso

BSC hardening Circuit BSC IP security for BSC card

v24d0 4.1.3.0 bsc-hardening-4.1.24-0.i386.rpm

A-bis Hardening Circuit BSC IP Security for A-bis card

v23d0 4.1.3.0 abis-hardening-4.1.23-0.i386.rpm

Config Manager Configuration Manager 124A v125d0 4.1.2.0 ConfigurationManager_124_v125d0.msi

OMC-R RHEL4 platform

OS-dependent libraries and services for the OMC-R on RHEL4

4.1.2.0 perl-DBI-1.32-5.i386.rpm MySQL-client-classic-5.1.50-1.rhel4.i386.rpm MySQL-client-classic-5.1.50-1.rhel4.x86_64.rpm MySQL-server-classic-5.1.50-1.rhel4.i386.rpm MySQL-server-classic-5.1.50-1.rhel4.x86_64.rpm

OMC-R RHEL5 platform

OS-dependent libraries and services for the OMC-R on RHEL5

4.1.2.0 perl-DBI-1.32-5.i386.rpm MySQL-client-classic-5.1.50-1.rhel5.i386.rpm MySQL-client-classic-5.1.50-1.rhel5.x86_64.rpm MySQL-server-classic-5.1.50-1.rhel5.i386.rpm MySQL-server-classic-5.1.50-1.rhel5.x86_64.rpm

BSC OS Update

BSC OS Update v11d0 4.1.2.0 ipaccess-os-update-11.0-0.i386.rpm

Stretto Firmware for gateway card v19d0 4.1.2.0 stretto-19-0.i386.rpm

FR Frame Relay driver v21d0 4.1.1.0 ipaccess-fr-21-0.i386.rpm

FRIP FR/IP Converter software v40d0 4.1.1.0 ipaccess-frip-4.1.40-0.i386.rpm

Wireshark 1.2.8ipa36 4.1.1.0 wireshark-win32-1.2.8ipa36.exe

A-bis Utils Circuit BSC A-bis card utilities v32d0 4.0g ipaccess-abis-utils-32.0-0.i386.rpm

Base Library code shared between BSC/FRIP

v48d0 4.0g ipaccess-base-4.1.48-0.i386.rpm

Common Library code shared between BSC/OMC-R

v35d0 4.0g ipaccess-common-35.0.0-0.i386.rpm

Media Gateway MAC Configuration

Application that configures the MAC Addresses of the MGWs

v6d0 4.0g ipaccess-2mgw-install-4.1.6-0.i386.rpm


BSC Availability Monitor

BSC scripts for availability statistics

v6d0 3.2 ipaccess-bsc-availability-6.0-0.noarch.rpm

BTS Installer Tool for configuring and programming nanoBTS

144 v34d0 3.2 BTSInstaller_v34d0.msi

BSC CORBA Diagnostics

Utility to diagnose CORBA issues

v3d0 3.2 ipaccess-corbadiag-4.0.3-0.i386.rpm

Sigtran Sigtran Software v9d0 3.2 ipaccess-sigtran-9.0-0.i386.rpm

Lb Sigtran Sigtran Software for Lb v6d0 3.2 ipaccess-lbsigtran-6.0-0.i386.rpm

IPMI Modules Customised IPMI drivers for BSC CPU card

v5b4d0 3.2 ipaccess-ipmi-modules-5.4-0.i386.rpm

Orbacus Library code shared between BSC/OMC-R

4.1.1-4-0 3.2 orbacus-4.1.1_ipaccess-4.0.i386.rpm

BSC Non SMP Kernel

Non SMP Kernel of the BSC OS

2.6.9-55.EL Pre 3.2 kernel-2.6.9-55.EL.i686.rpm

BSC SMP Kernel

SMP Kernel of the BSC OS smp-2.6.9-55.EL

Pre 3.2 kernel-smp-2.6.9-55.EL.i686.rpm

BSC RAID OS CD

BSC custom RHEL4 installation CD for RAID

v16b8d0 Pre 3.2 ipaccess-raid-OS-CD-v16b8d0

eToken RTE Runtime Environment (Drivers and property editor) for BTS Installer security tokens

v3.65 Pre 3.2 RTE_3_65.msi

IPMI Tools Tool to check the version of IPMI Firmware

v1d0 Pre 3.2 ipmitool-v1d0.tgz

Java Java Runtime for OMC-R Java Runtime for BTS Installer

1.5.0-07 Pre 3.2 jre-1_5_0_07-linux-i586-rpm.bin jre-1_5_0_07-linux-amd64.rpm jre-1_5_0_07-windows-i586-p.exe

Keyboard Driver Updated RHEL Keyboard driver

1.12-2.el4.4 Pre 3.2 kbd-1.12-2.el4.4.i386.rpm

Orbacus-Java Orbacus Java ORB for OMC-R 4.1.3-1-8 Pre 3.2 orbacus-java-4.1.3_ip.access-1.8.i386.rpm

PP220 IPMI Firmware CD

IPMI firmware for PP220 BSC Card

v1.3d0 Pre 3.2 pp220-ipmi-firmware-v1.3-0.iso

nanoBTS BTS hardware (1800MHz) 108 or 139

N/A N/A

nanoBTS BTS hardware (1900MHz) 110 or 140

N/A N/A

nanoBTS BTS hardware (900MHz) 108G or 178

N/A N/A

nanoBTS BTS hardware (EDGE-I 1800MHz)

165A N/A N/A


165B N/A N/A


165C N/A N/A



165D N/A N/A


165E N/A N/A


165F N/A N/A


165G N/A N/A


165H N/A N/A

3.2.1 Optional System Components These optional components are supplied separately. When installing any optional components with this system release, only use the versions and distribution media shown here.

Table 3 Optional nanoGSM Software Components


Last updated in release


SNMP Agent SNMP Agent software 204A v222d0 4.0g ipaccess-snmp-agent-4.1.222.0.i386.rpm

nanoGSM 4.1.8 circuitBSC System Release Note Installation, Upgrade and Downgrade Information © ip.access Ltd Page 9

4 INSTALLATION, UPGRADE AND DOWNGRADE INFORMATION

Note: For the latest versions of the documents that are relevant to this System Release, see 5.1 Manuals.

Note: For PM Data Migration from BSC to OMC-R after upgrade refer to Technical Note TN_1057.

4.1 Installing a New SR4.1.8.0 nanoGSM System Refer to the following manuals for preparation information and installation instructions:

• NGSM_GST_120 nanoGSM System Planning Manual

• NGSM_GST_200 nanoGSM circuitBSC Installation Manual

• NGSM_GST_300 nanoBTS Installation Manual

• NGSM_GST_400 nanoGSM OMC-R Installation Manual

4.2 Upgrading from Previous System Releases to SR4.1.8.0

4.2.1 Upgrade Procedure Requirements The following tables define which procedures are required to be run when upgrading to this SR. The procedure definitions can be found in the associated upgrade manual, see section 4.2.2.

Table 4 Manual Upgrade Procedures to SR4.1.8.0

From SR Version Procedure Name SR4.1.7.0 SR4.1.2.0 to

SR4.1.6.0 SR4.1.1.0 Pre – SR4.1.1.0

OMC-R Upgrade Do not run Run Run See associated upgrade manual for required SR version.

BSC Upgrade Run Run Run

Config Manager Upgrade Do not run Do not run Run

BTS Installer Upgrade Do not run Do not run Do not run

BTS Upgrade Run Run Run


Table 5 Automated Upgrade Procedures to SR4.1.8.0

From SR Version Procedure Name SR4.1.7.0 SR4.1.2.0 to

SR4.1.6.0 SR4.1.1.0 Pre – SR4.1.1.0

OMC-R Upgrade Do not run Run Run See associated upgrade manual(s) for required SR version.

Automated BSS – Create Managed System Release

Run Run Run

Automated BSS – Distribute System Release to BSC

Run Run Run

Automated BSS – Upgrade BSC

Run Run Run

Automated BSS – Distribute System Release to BTS

Run Run Run

Automated BSS – Upgrade BTS

Run Run Run

Config Manager Upgrade Do not run Do not run Run

BTS Installer Upgrade Do not run Do not run Do not run

4.2.2 Upgrade Documentation Instructions for upgrading can be found in the relevant manual, see Table 6 below.

For anyone on a load before SR4.1 the system must first be upgraded to SR4.1.1.0 and then on to the required release.

Note: Only the upgrade paths described in the table are supported.

Table 6 Instruction Manuals for Upgrading

From SR To SR Upgrade Manual

4.1.7.0 4.1.8.0 NGSM_UPG_150

4.1.6.0 4.1.8.0 NGSM_UPG_150

4.1.5.0 4.1.8.0 NGSM_UPG_150

4.1.4.0 4.1.8.0 NGSM_UPG_150

4.1.3.0 4.1.8.0 NGSM_UPG_150

4.1.2.0 4.1.8.0 NGSM_UPG_150


4.1.1.0 4.1.8.0 NGSM_UPG_150

4.0g 4.1.1.0 NGSM_UPG_141

3.2 4.1.1.0 NGSM_UPG_121

3.1v 4.0g NGSM_UPG_110

Pre 3.1v 3.1v NGSM_UPG_100

4.3 Downgrading from SR4.1.8.0 to Previous System Releases

4.3.1 Downgrade Procedure Requirements The following tables define which procedures are required to be run when downgrading from this SR. The procedure definitions can be found in the associated downgrade manual, see section 4.3.2.

Table 7 Manual Downgrade Procedures from SR4.1.8.0.

To SR Version Procedure Name SR4.1.7.0 SR4.1.2.0 to

SR4.1.6.0 SR4.1.1.0 Pre – SR4.1.1.0

BTS Downgrade Run Run Run Downgrade to SR4.1.1.0 first and then see associated downgrade manual(s) for required SR version.

BTS Installer Downgrade Do not run Do not run Do not run

Config Manager Downgrade Do not run Do not run Run

BSC Downgrade Run Run Run

OMC-R Downgrade Do not run Run Run


Table 8 Automated Downgrade Procedures from SR4.1.8.0

To SR Version Procedure Name SR4.1.7.0 SR4.1.2.0 to

SR4.1.6.0 SR4.1.1.0 To pre –

SR4.1.1.0 BTS Installer Downgrade Do not run Do not run Do not run Downgrade to

SR4.1.1.0 first and then see associated downgrade manual(s) for required SR version.

Config Manager Downgrade Do not run Do not run Run

Automated BSS – nanoBTS Downgrade

Run Run Run

Automated BSS – BSC Downgrade

Run Run Run

OMC-R Downgrade Do not run Run Run

4.3.2 Downgrade Documentation Instructions for downgrading can be found in the relevant upgrade manual, see Table 9 below.

Note: Only the downgrade paths described in the table are supported.

Table 9 Instruction Manuals for Downgrading

From SR To SR Downgrade Manual

4.1.8.0 4.1.7.0 NGSM_UPG_150

4.1.8.0 4.1.6.0 NGSM_UPG_150

4.1.8.0 4.1.5.0 NGSM_UPG_150

4.1.8.0 4.1.4.0 NGSM_UPG_150

4.1.8.0 4.1.3.0 NGSM_UPG_150

4.1.8.0 4.1.2.0 NGSM_UPG_150

4.1.8.0 4.1.1.0 NGSM_UPG_150

4.1.1.0 4.0g NGSM_UPG_141

4.1.1.0 3.2 NGSM_UPG_121

4.0g 3.1v NGSM_UPG_110

3.1v Pre 3.1v NGSM_UPG_100

nanoGSM 4.1.8 circuitBSC System Release Note Documentation © ip.access Ltd Page 13

5 DOCUMENTATION

5.1 Manuals Getting Started Version NGSM_GST_110 nanoGSM System Product Description 5.0 NGSM_GST_120 nanoGSM System Planning Manual 9.0 NGSM_GST_200 nanoGSM circuitBSC Product Description 6.0 NGSM_GST_300 nanoBTS Product Description 8.0 NGSM_GST_400 nanoGSM OMC-R Product Description 6.0 Installation NGSM_INST_200 nanoGSM circuitBSC Installation Manual 14.0 NGSM_INST_300 nanoBTS Installation Manual 7.0 NGSM_INST_400 nanoGSM OMC-R Installation Manual 11.0 NGSM_INST_525 nanoGSM SR4.1.8 circuitBSC System Release Note (this manual) 1.0 Operations NGSM_OPM_100 nanoGSM System Operations Manual 2.0 NGSM_OPM_110 nanoGSM DMI User Manual 1.0 NGSM_OPM_120 nanoGSM System Maintenance Manual 1.0 NGSM_OPM_200 circuitBSC Operations Manual 5.0 NGSM_OPM_300 nanoBTS Operations Manual 2.0 NGSM_OPM_400 nanoGSM OMC-R Server Operations Manual 9.0 NGSM_OPM_410 nanoGSM OMC-R Client Operations Manual 5.0 NGSM_OPM_420 Configuration Manager Operations Manual 4.0 NGSM_OPM_800 NGSM CircuitBSC GbIP Feature Activation Manual 3.0 NGSM_OPM_801 NGSM OMCR ActiveStandby Feature Activation Manual 3.0 NGSM_OPM_802 NGSM Multiplexed Secure GPRS Abis Traffic Feature Activation Manual 1.0 NGSM_OPM_803 NanoGSM to 3G Reselection and Handover Feature Activation Manual 1.0 NGSM_OPM_804 NGSM BSS Radio Trace Feature Activation Manual 1.0 NGSM_OPM_805 NGSM E911 Support Feature Activation Manual 1.0 NGSM_OPM_806 NGSM TTY Support Feature Activation Manual 1.0 NGSM_OPM_807 NGSM A5/3 Feature Activation Manual 1.0 NGSM_OPM_808 NGSM SMS CellBroadcast Feature Activation Manual 2.0 NGSM_OPM_809 NGSM Dynamic Half Rate AMR Feature Activation Manual 1.0 NGSM_OPM_811 NGSM KPI Feature Activation Manual 4.0 NGSM_OPM_812 NGSM Bulk Parameter Change Feature Activation Manual 1.0 Reference NGSM_REF_110 nanoGSM MIB Configuration Management (CM) Reference Manual 6.0 NGSM_REF_115 nanoGSM MIB Configuration Management (CM) Delta Reference Manual 2.0


NGSM_REF_120 nanoGSM MIB Fault Management (FM) Reference Manual 6.0 NGSM_REF_130 nanoGSM MIB Fault Management (FM) Delta Reference Manual 3.0 NGSM_REF_140 nanoGSM Fault Management Interfaces 1.0 NGSM_REF_160 nanoGSM MIB Performance Management (PM) Reference Manual 6.0 NGSM_REF_170 nanoGSM MIB Performance Management (PM) Delta Reference Manual 8.0 NGSM_REF_200 nanoGSM BSC Open Source Software License Manual 1.0 NGSM_REF_300 nanoGSM BTS Open Source Software License Manual 1.0 NGSM_REF_400 nanoGSM OMCR Open Source Software License Manual 1.0 NGSM_TRB_200 nanoGSM BSC Troubleshooting Manual 1.0 NGSM_TRB_300 nanoGSM BTS Troubleshooting Manual 1.0 NGSM_TRB_400 nanoGSM OMCR Troubleshooting Manual 1.0 Upgrade NGSM_UPG_100 Interim Upgrade to SR3.1v 3.0 NGSM_UPG_110 SR4.0 Upgrade/Downgrade Procedure from SR3.1v 3.0 NGSM_UPG_121 SR4.1 Upgrade/Downgrade Procedure from SR3.2 8.0 NGSM_UPG_141 SR4.1 Upgrade/Downgrade Procedure from SR4.0 7.0 NGSM_UPG_150 SR4.1 Maintenance Release Upgrade/Downgrade Procedure 15.0 NGSM_UPG_200 SR4.0 circuitBSC Hardware Upgrade/Downgrade Procedure 7.0 Technical Notes TN_1016 BIOS Configuration storage in NVRAM 1.0 TN_1017 RTP Parameters Change After Upgrade 1.0 TN_1018 Optimising Cache Flushing on 4Gbyte BSCs 1.0 TN_1023 Abis card Temperature Threshold Correction 1.0 TN_1028 FR RPM Installation Problem in SR4.1.1 4.0 TN_1036 Workaround For Decreased OMC-R Performance 4.0 TN_1044 Optimising Cache Flushing on the OMCR Server 1.0 TN_1045 Filtering CORBA Alarms 1.0 TN_1057 PM Data Migration from BSC to OMCR 1.0 TN_1063 TJ Log Purge 1.0 TN_1064 Extended CBC Message ID Range 2.0

5.2 Online Help Online help is available for the OMC-R Client and Configuration Manager.


5.2.1 OMC-R Client Help There are three forms of online documentation available for the OMC-R Client:

• HTML Help

This is available from a link on the OMC-R web page used to start the OMC-R Client. The OMC-R HTML Help is accessed through your web browser.

• OMC-R User Manual PDF

This is also directly available from a link on the OMC-R web page used to start the OMC-R Client.

• Context Help in the OMC-R Client

The help pane in the OMC-R Client provides context sensitive help relating to the currently selected item or sub-item.

5.2.2 Configuration Manager Help Context sensitive online help is provided for Configuration Manager. Press F1, or click the Help button (if available), to see help about the current dialog box. Alternatively, select Help from the Configuration Manager Help menu. The online help contains:

• Information about how to use Configuration Manager

• A reference for the MIB (management information base) used by the BSC

nanoGSM 4.1.8 circuitBSC System Release Note Fixed Issues © ip.access Ltd Page 16

6 FIXED ISSUES

6.1 Issues fixed in SR4.1.8.0 MKS Id Product Summary

230667 nanoBTS EDGE Addition of a robustness check in a library routine.

262335 BSC The BSC does not log the PM counter ogHoCmd for handovers to UMTS.

274139 BSC The BSC is unable to handle SCCP messages greater than 8192 bytes.

286938 nanoBTS EDGE An internal frame counter readback failure may occasionally cause an assert in l1_edma.c.

314716 nanoBTS EDGE A network outage can cause an internal memory corruption with follow-on exception and BTS reset.

6.2 Issues fixed in SR4.1.7.0

MKS Id Product Summary

178033 nanoBTS EDGE Corruption of the TRX DL VBC causes subsequent failure and requires the BTS to be power cycled to recover.

252573 nanoBTS EDGE The BTS may reboot while in secure mode due to an assert in igki_sig.c#467:taskId=11.

257986 OMC-R The OMC-R copyright version year updated to 2011.

264534 OMC-R Updates to the KPI 'DL Receive Power Level' graph Y axis label.

272063 BSC Updates to handle the addition of a timestamp to the log file bts_connections.log.

284003 BSC Enhancement to the BSC installation procedure to improve date and time checking and enabling of NTP.

295908

300216

300261

304181

304260

Documentation/BSC Updates to NGSM_UPG_150 SR4.1 Maintenance Release Upgrade/Downgrade Procedure manual.

304496 Documentation/BSC Updates made to the NGSM_INST_200 nanoGSM circuitBSC Installation Manual and NGSM_OPM_200 circuitBSC Operations Manual.




218158 BSC Sufficient memory was unavailable internally in a method in the Managed Object Class.

251293 OMC-R Binary log files can fill up the space in /var partition.

258823 OMC-R Alarms were not reaching the OMC-R in time due to heavy processing of Transaction Journal files.

287174 BSC BSC does not send SI2quater messages to BTS when the 3G reselection list contains 2 ARFCNS.

292863 BSC Mobiles can lose their connection to the BTS following a RESET message from the BSC/CBC.

294671 BSC BSC initiated connections to the CBC may sometimes fail resulting in an alarm being generated.

296694 nanoBTS EDGE Misconfiguration of the BVCI in the MIB causes the BTS to reboot.

296947 Documentation/OMC-R Document updates to reflect the changes made to the Active Standby configuration.



281039 nanoBTS EDGE A small memory leak triggered in certain circumstances can after a long time result in a BTS reboot.

281472 nanoBTS Non-EDGE A small memory leak triggered in certain circumstances can after a long time result in a BTS reboot.

271969 nanoBTS EDGE Failure of sites to reconnect following IP interruption.

285016 nanoBTS Non-EDGE Failure of sites to reconnect following IP interruption.

274030 Documentation/BSC Document improvements for INST_200_circuitBSC_Manual.

286406 Documentation/BSC Document software release information updated in UPG_150_Upgrade Manual.




112977 Documentation/OMC-R Improvements to the OMCR Installation Guide.

152797

197035

197036

BSC Locking/unlocking a BTS can cause incorrect signalling to be sent to the CBC and also result in miscalculations for the number of complete and outstanding broadcasts.

163739

243300

BSC Improvements to BSC log file handling to utilise disk space efficiently.

Documentation changes required as a result of SR4.1.4 logrotate improvement/changes.

177000

143031

nanoBTS EDGE Gb stack memory leak resolved.

179213 Documentation/BSC Detailed procedure required to remove RAID objects while installing a BSC that uses SSD.

187590 Documentation/OMC-R OMC-R documentation does not contain a list of KPIs supported.

194127 nanoBTS EDGE General issues with the nanoBTS TRX after SR4.1.2.0 can lead to an unstable TRX.

197029 BSC BSC loses connectivity when changing a particular type of client pod configuration.

197035 nanoBTS Non-EDGE Strange behaviour from the IPAccess BSC when it responds to a “Message-Status-Query” initiated by the BMC.

197036 nanoBTS EDGE Strange behaviour from the IPAccess BSC when it responds to a “Message-Status-Query” initiated by the BMC.

197854 nanoBTS EDGE CBC message is not delivered to MS due to BTS ignoring Write messages.

198286 nanoBTS EDGE Misconfiguration of the BVCI in the MIB causes the BTS to reboot.

199073 nanoBTS EDGE Elevated rate of “TRX is not responding” alarms when used with a Booster.

202184 nanoBTS EDGE A Write message with high priority sent to the BTS always causes a Capacity Exceeded Error indication to the BSC.

206752 GNAT Fixing a number of Coverity detected issues in the GNAT.

208195 OMC-R MySQL Binary file backups set to auto-expire are not automatically deleted on expiry.

210148 BSC Change of time by date command or NTP can cause a miscalculation of the number of completed broadcasts.

211408 GNAT The GNAT core process aborts and restarts due to no available timer memory buffers.


212527 GNAT The GNAT core process mistakenly generates NSEI unknown or not provisioned alarm.

227571

243379

243510

BSC New Abis card hardening rules for the SMS-CB server to enable the use of the Abis ethernet daughter card for CBC connections.

224776 OMC-R The Very Short Calls Rate (VSCR) "Export KPI Data" and "KPI Graph" data values do not agree with hand calculated values.

226873 OMC-R “DL RTP Packet Jitter" - When the time range is more than 24 hours KPI export data and graph do not show the average of non-zero KPI's, instead it is incorrectly showing the sum of the non-zero KPI’s.

229311 BSC An issue in the Abis Connection Manager can cause the BSC to restart.

229870 Documentation/BSC Improvements to NGSM_OPM_800_GbIP_CircuitBSC_FeatureActivation for GbIP-SGSN connectivity details via supported Ethernet interfaces.

230315 nanoBTS EDGE Updates to cleanly stop the TRX DL VDC on an assert to resolve subsequent TRX boot timer expiry issues.

238958 OMC-R SNMP not sending traps after the OMC-R upgrade to SR 4.1.3.0.

239788 nanoBTS EDGE A single BTS after losing OML may not fully close the socket, resulting in the BTS going offline.

241114 BSC Modifying any BSC profile options may reduce BSC capacity.

242495 BSC BSC paging capacity improvements.

243580 Documentation/OMCR NGSM_UPG_150_SR41_Maintenance_Upgrade_v8 0.pdf for OMCR upgrade.

244416 BSC Improve actions for BSC file space low alarms.

248284 OMC-R The KPI generation feature does not work if “Previous Time Period” is selected in the GUI.

257025 GNAT GNAT core dumped due to memory corruption.


186670

225973

235261

249437

250006

258660

263107

263111

263616

264186

265563

265564

265842

268620

272067

BSC BSC outage due to thread dead lock.

255139 BSC Allow out of range cell broadcast message identifiers to be transmitted.

262119 BSC Ensure that cron daemon reloads internal tables correctly.

251925 nanoBTS EDGE Red/Blue LED pattern on BTS indicating power-cycle required..

263620 BSC Transactional journal logs are not purging.

267954

268667

nanoBTS EDGE SMS-CB RNC-CAPACITY-EXCEEDED indication messages are unexpectedly seen at the BSC.


296028 BSC BSC does not send SI2quater messages to BTS when the 3G reselection list contains 2 ARFCNS.

295769 BSC BSC initiated connections to CBC may sometimes fail resulting in an alarm being generated.


272985 nanoBTS EDGE Mobiles can lose the connection to the BTS following a RESET message from BSC/CBC.



269026 nanoBTS EDGE Red/Blue LED pattern on BTS indicating power-cycle required.


269028 BSC BSC service outage.

269420 BSC BSC generic core file seen in BSC.

269427 nanoBTS EDGE Cell Broadcast with CBC has mismatched scheduling messages.


260308 BSC Allow out of range cell broadcast message identifiers to be transmitted.

260785 BSC Missed call in site.

255365 nanoBTS EDGE There is a capacity error generated message from the BSC even after successful message reception or a reset message. Fixed with the below MKS 261449.

261449 nanoBTS EDGE A Write message with high priority sent to the BTS always causes a Capacity Exceeded Error indication to the BSC. This fixes MKS 255365.


206752 GNAT Fixing a number of Coverity detected issues in the GNAT.

211408 GNAT GNAT core aborts and restarts due to no timer memory buffers available.

212527 GNAT GNAT generating NSEI unknown or not provisioned alarm.

257025 GNAT GNAT core dumped due to memory corruption.



75901 OMC-R A warning message is required, if a user wants to modify an attribute which requires locking in bulk parameter operations.

78638 OMC-R It is not possible to save KPI graphs in the OMC-R client.

153311 OMC-R Error message not documented.

156585 OMC-R The PM database tables may keep growing as PM data older then PM_RETENSION_PERIOD is not accurately deleted.

157064 OMC-R Disable the raising of alarm ‘File-Copy-Failed’ when PM-Max-File-Limit is set to "No Files".

174826 OMC-R Updates to PM Aggregation code to improve performance.

187590 Documentation/OMC-R OMCR documentation does not contain a list of KPIs supported.

191354 BSC Change in the BSC Corba event persistence.

202234 GNAT GNAT core process can reboot or lock out individual BTS Gb links due to corrupt data structures.

212806 OMC-R Error message seen when retrieving daily raw KPI data.


143031 nanoBTS EDGE Timer buffer memory leak in the BTS Gb stack.

159591 nanoBTS EDGE BTS reboots due to assert when running NWL and scanning empty channels.

161162 nanoBTS EDGE AMR MF counters are not updated correctly.

176195 nanoBTS EDGE GPRS cell goes down when Abis supervision feature is disabled.

179220 nanoBTS EDGE BTS software fatal errors caused by memory allocation failure.

183779 nanoBTS EDGE Improvements to the TRX Boot Failure diagnostics.

185486 nanoBTS EDGE Incorrect BVCI in BSSGP Status PDU.

189201 nanoBTS EDGE A BTS with secure mandatory RSL fails to come up, except for the site manger object, after the BTS is loaded with v159b28d0 and IPA certificate.

192080 BSC Race condition causes BSC reset.



181992 BSC GPRS Objects failed to come up when the GPRS type is set to Secure Multiplex.


29567 BSC All Abis card static routes may get deleted when deleting only one static route using the BSC Config tool.

32278 BSC Negative altitude is incorrectly encoded.

This only impacts a BTS below sea level where a negative altitude is set. Service is not impacted, but E911 location requests reports a wrong altitude for the mobile if used in such a situation.

73916 BSC Slave RC object name changes to default during online morphing.

As per the morphing definition, the Radio Carrier object name should change from "Slave Radio Carrier (GMSK E-GSM 900)" to "Slave Radio Carrier (EDGE E-GSM 900)" on morphing.

74153 BSC Maximum of CTM Emergency calls are restricted to 4. BSC can support maximum number of 4 CTM calls simultaneously, irrespective of whether it is an emergency or non-emergency call.

74432 BSC The MIB default names for 'Site Manager' are unclear when creating a Site Manually.

The user is now given the option to create site manager for the required system release. For example “BTS Site Manager (SR4.1/4.0/3.2)”.

74801 BSC MGW configuration issue. The “/etc/dhcpd.conf” file in the BSC had an entry with filename "Stretto.cmp -fb" instead of filename "stretto.ini”. So the updated configuration file is not downloaded to the Media gateway.

75318 nanoBTS EDGE Location update not happening on EDGE BTS 850 for different types of MS.

75535

145840

nanoBTS EDGE The value of the preemptDlTbf counter in downlink TBFs MF is not updated properly.

77151 BSC Extended BCCH Frequency List IE of SystemInformation2ter message was not encoded as per the 3GPP spec.

“SystemInformation2ter” message now contains at least one 2G neighbouring cell description as part of "Extended BCCH Frequency List" IE

78718

124679

BSC The BSC does not recover automatically following an interruption of FRIP NSVC links.

78865 nanoBTS EDGE DL VBC doesn't initialise reliably at low temperatures.

80369 BSC Stopping the BSC application before other processes on which the BSC application is dependent can cause core dump on platform reboot or shutdown.


83118 BSC Check connectivity process does not run during fresh installation of the BSC.

86022 OMC-R GPRS NSVC and GPRS Cell objects are not ordered properly under the GPRS NSE Objects in the OMC-R Client.

The objects now have the order GPRS NSE -> GPRS Cell -> GPRS NSVC.

95831 nanoBTS EDGE Morphing fails from a SR4.0 Non-EDGE BTS to a SR4.1 High Power EDGE BTS with unable to complete auto software class change alarm.

95873 nanoBTS EDGE BTS code changes for supporting SMS-CB with CBC feature.

97787 BSC The BSC does not always use the optimal set of handovers when re-arranging calls to achieve the best channel usage for AMR and PDCH.

102709

119353

BSC Internal /var partition on SSD BSC card can get full after a very long time (e.g. a year).

105793 OMC-R When the OMCR-BSC link gets reconnected after being disconnected a null pointer exception is seen while retrieving alarm information from the CORBA events channel and also the BSC-OMCR state remains disconnected.

110398 Documentation The Bulk-Parameter Feature Document does not correctly describe the behaviour of the Modify Operation status in the case of an operation that is only partially successful.

112088 Config Manager Incorrect help text for ‘Allow Immediate Assignment on TCH/H’ attribute.

114205 Documentation The OS version needs to be listed at the very beginning of the OMCR installation/upgrade manuals.

114266 BSC The BSC SSL Control parameter was changed from Security Mandatory to Security Optional after upgrading to SR4.1.1.

114779

105710

117802

125430

OMC-R KPI graphing tool does not work when multiple PM log files for a particular BSC contain the same date/time in the log file names.

115167 OMC-R The pre-upgrade OMC-R backup can fail as the "/var/lib/ipaccess/omcr-server/bulkParameter/" directory may not be present following a fresh installation of the OMC-R.

123231 BSC The BSC is not updating CorbaAgentManager::mOmcrHeartbeatPeriod after changing the parameter Management Link Heartbeat Timeout to a value of more than 6 seconds.

123559 OMC-R Create/Delete operation can fail when the OMC-R is under heavy load.

123743 OMC-R HO failure rates can show negative values in the KPI graph.

124799 nanoBTS EDGE GPRS doesn't work when BTS cell parameters MCC/MNC/Cell id are changed in the BSC.

124816 nanoBTS EDGE BTS resets intermittently with the 'Fatal Error' alarm under heavy load conditions.


126759 nanoBTS EDGE TRX boot failure alarm appears as major in Config Manager but is defined as critical in the alarm specifications.

127215 BSC Mobile Terminating call failures due to paging message discarding at BSC.

128785 nanoBTS Non-EDGE When running the SNMP get-next command the BTS returns the wrong enterprise number 7968, it should be 7986 according to IANA database.

131965 BSC Addition of multiple static routes with the same ip-address, for both the BSC and Abis card, using the su config utility is allowed which can cause mis-configuration of the routing table on both the BSC and Abis card.

132552

133996

nanoBTS EDGE TRX resets with “WARN:OAM_RES:res_trx_status.c#231:TRX is not responding - reinitialising the unit.” when a large memcpy takes place. For example an iPhone spooling video from YouTube plus a Blackberry making repeated calls.

133601

136967

nanoBTS EDGE Improved diagnostics when the software watchdog is triggered.

133708

52523

109613

126109

126164

126294

130956

131963

135952

136408

137853

137913

138737

141595

BSC Secure GPRS feature stability and performance improvements. Improves the RTP statistics and prevent wrong counter values.

133948 nanoBTS EDGE Power cycle may be required to recover a BTS with the BSC fatal alarm “FATAL:HISR context:dd_hpi_isr”.

134363 Config Manager Config Manager can't edit attributes of a 006 version SR4.0 EDGE BTS BTS.

135071 nanoBTS EDGE Very infrequent assert in IP_STREAM task:igki_sig.c#862:signal->type != kiNullBuffer.type - Trying to destroy a NULL signal.

135668 OMC-R PM Data Cleanup Service takes a long time for a single run. Providing the index on MFAttributes table will make the delete operation on this table faster.

136215 nanoBTS EDGE Change in the location of BTS. Certificates cause EDGE sites to not come up after BSC Upgrade to SR4.1.1.2.


136693 nanoBTS EDGE SSL certificate download to BTS fails with 763:WARN:SW_DLD:sw_dld_sdp_fsm.c#1205:Error writing Flash security cache.

137864 BSC GBIP cannot be reinitialised using Config Manager.

138665 nanoBTS EDGE BTS can reset with the alarm TRX Proc:<In HWI>:l1_edma.c#1348 when dynamic AMR is enabled.

138686 nanoBTS EDGE BTS does not correctly validate the server certificate.

138702 nanoBTS EDGE BTS reset with igki_sig.c#738:pool <= KI_POOL_LARGEST.

138709 nanoBTS EDGE BTS memory pools may become full and raise BTS warning 'igki_sig.c#741:Pool2 nearly full'.

138825 nanoBTS EDGE If the Ethernet connection to a BTS fails such that the DHCP procedure does not complete, the BTS may require a power cycle to recover.

139436 BSC The BSC resets while decoding a 04:08 Handover Failure message received from MSC.

139621 Documentation A5/2 Encryption Algorithm supported by the nanoBTS is incorrectly described in the nanoBTS product description (NGSM_GST_300_nanoBTS_Prod_Desc).

139732 nanoBTS EDGE Possible flood of WARN:RM:rm_nm_bvc_flow.c#511:GPRS LLC PDU gauge=8 should be 0" alarms from BTS.

139811 BSC Performance counter shows incorrect values - hoCause(17).Handover by Causes (hoCause) section of MIB_PM_REF document does not contain new values.

141188 nanoBTS EDGE Throughput may be reduced when the BTS NSType is set to Secure Mux.

142212 BSC Lbsigtran RPM is installed by default during the fresh installation of the BSC. The Lbsigtran component in the BSC is optional and should not be installed by default.

142561 BSC Default routing interface cannot be set on both the BSC and Abis card.

142663 nanoBTS EDGE BTS resets when configuring the timeslot channels for the Dynamic AMR feature.

142865 nanoBTS EDGE Unable to make successful voice call after blocking/Unblocking OML Port.

143589 nanoBTS Non-EDGE GPRS doesn't work when BTS cell parameters MCC/MNC/Cell id are changed in the BSC.

143715 OMC-R perfLog files at the OMC-R that are older than PM-Retention-Period are aggregated at the OMCR.

143988 BSC Measurement of the counter “MIB_SUC_OG_TCH_HO_NEIGH_ID” in the BSC is done incorrectly as the counter is incremented for both TCH & SDCCH Handovers.


145481

95388

146146

146147

GNAT GNAT SGSN NSE alarms do not clear in third party management tools. The GNAT SGSN alarms have only one message to clear them. So some alarms remain active in NMS.

145657 OMC-R Use right set of formula for calculating Incoming (IC) and Outgoing (OC) Handover (HO) success rate KPI's.

Following formula is used for calculating above mentioned KPI's:

1) Incoming Handover Success Rate = sucIcHo *100 / icHoAlloc

2) Outgoing Handover Success Rate = sucOgHo *100 / ogHoCmd.

146544 BSC BSC can become disconnected from the OMC-R Server during Alarm Storm.

146728 nanoBTS EDGE BTS resets when the ARFCN and power reduction is changed at the same time.

147288 BSC Support for new Media gateway firmware version 5.2 in the BSC.

147326

148044

nanoBTS EDGE When decoding a paging command the “l3_0858_parser.c:592 7 196 Opt Not parsed” BTS alarm may be seen as one of the optional IEs (eMLPP Priority which gives the priority of the voice call) is not decoded properly.

150624 BSC FRIP card could go down on BSC.

152130 nanoBTS Non-EDGE When modifying transmit power reduction configuration, Non Edge 1800 (139) BTS resets with SW Fatal error 4555:FATAL:HISR context:gki_os_signalling.c#454:Queue overflow in task 30.

152289 nanoBTS EDGE Low throughput on EDGE BTS.

154492 Documentation Changes to media gateway firmware download procedure in BSC upgrade documentation.

156968 BSC Large numbers of global pages can result in disruption of service by overloading the capacity of the BTS. A profile option "DiscardAllGlobalPaging” is provided to discard such messages.

157401 nanoBTS EDGE When there are 8 secure voice calls running on the BTS, the BTS can reset with FATAL:RSL:traffic_proxy.c#586:NULL != filter_p alarm.

158116 BSC Intermittent handover failure from BSC to Macro GSM due to the Handover Required message sometimes being formatted incorrectly..

161138 nanoBTS Non-EDGE Non EDGE BTS does not correctly validate the server certificate.

163893 Documentation Minor changes required in the downgrade of the OMC-R section in the document (NGSM_UPG_150_SR41_Maintenance_Upgrade).

165118 OMC-R Cannot generate the KPI graph of the Aggregation data "CS Pages" for BSC.

166522 BSC Remove “Db viewer” and “Offline” upgrade components, as these features are no longer supported.


167686

167230

BSC GPRS NSE toggles during ftp download with GBIP and Secure Mux GPRS combination resulting in low data throughput and GBIP link bouncing.

168000

168491

nanoBTS EDGE When performing a video download with GBIP configured, the BTS may reset with the warning (WARN:GBHSS_STACK:cspl.c#2354:Assert:((QV_ALLOC_MAGIC == q->allocated) || (QV_NOT_ALLOC_MAGIC == q->allocated)):prtfn.c:347).


199928 nanoBTS EDGE BTS may reset with an assert in the OAM_IM task when PM stats are enabled. OAM_IM:links_distributed_interface.c#679:encode_p != ie_p trx_boot_failure.

199927 nanoBTS EDGE idle_watch_doc.c#403 Binst NL assert.

199635 GNAT Loss of GPRS due to GNAT failure in BSC.

108163 GNAT Loss of GPRS due to GNAT failure in BSC.


175354 nanoBTS EDGE BTS may lock up in field due to loss of OML or IP Connectivity.


157283 OMC-R The OMC-R Server would benefit from a configurable alarm filter.

159540 OMC-R Changes to OMCR polling rate of BSC.


135778 nanoBTS EDGE EDGE sites are not coming up after upgrade to SR4.1.1.2.

136105 nanoBTS EDGE Potential issue with Secure GPRS when used in EDGE BTS.

136530 Documentation Highlight that additional ports must be open if secure GPRS is used.



87899 OMC-R Resolving deadlock issues in SR4.1 OMC-R.

97286 BSC GSM 12.21 Message decode errors.

104915 BSC Flexwave Manager alarms not according to alarm specification.

115061 BSC Kernel 2.6.9-55.Elsmp panic while upgrading the BSC from SR3.2b to SR4.1.1.0 after previous downgrade.

115168 OMC-R Poor performance for users with many user settings.

115206 nanoBTS EDGE Secure/Multiplex GPRS NSE/cell goes down when RTP subagent is reinitialised.

115285 BSC When using CF storage the format_cf script fails if its geometry is different than the hard coded values in script.

116761 BSC Status of BSC RACK Objects are shown incorrectly in Config Manager.

119885 BSC Provide ownership of naming service and notification service database folder to ipacommon user.

120288 nanoBTS EDGE Low GPRS throughput caused by BVC flow control.

121812 nanoBTS Non-EDGE Fix problem with warnings about malformed GPRS packets appearing in logs.

124272 BSC FAN or PSU object status is incorrectly reported on platform monitor startup (see also work-around listed against MKS125086 listed in the known issues section at the end of this document).

124491 Documentation Section referred for Immediate Assignment MF in page 6 of the document NGSM_REF_170_MIB_PM_Delta_v4_0, is incorrect.

125139 BSC When enabling secure multiplex GPRS certain sites still use port 23000.

126629 nanoBTS EDGE GPRS may not come up after reconfiguring BTS from multiplex to secure multiplex.

126228 BSC Wrong measurements from "sucIcHo" counter.

129042 nanoBTS EDGE Edge BTS resets with loss of OML during PS load rig run.

131931 nanoBTS EDGE Problem in IP channel tasks which don't respond to idle watchdog pings, resulting in a loss of RSL reset of the BTS.

132050 BSC Loss of GPRS due to use of reserved values by BTS in header tags. BSC updated to ignore header tags sent with reserved values.

132288 nanoBTS Non-EDGE Multiplexer decode failed dropping packet header length 4, Secure GPRS NSE fails to come up.


132639/

126281

BSC Resolved problems with GPRS, in particular when security/multiplexer is enabled.

132842 Documentation DMI user is disabled after an upgrade from SR3.2 to SR4.1.


90991 Documentation BOOTPROTO entry for the Abis card incorrect in System Planning Manual and HW Upgrade manual.

102753 Documentation System Planning manual GST_120 does not mention IML and Secure IML ports and their behaviour.

111474 Documentation During a fresh installation of OMC-R 4.1 the

"/var/lib/ipaccess/omcr-server/bulkParameter/" will not be present.

112205 Documentation Lb interface configuration needs to be updated in Config Manager manual.

113618 Documentation Instructions to add second MGW card to the circuitBSC needs to be updated.

114205 Documentation OS version needs to be listed at the very beginning of the installation/upgrade manuals.

113195 Documentation Mistakes in the upgrade/downgrade manual UPG_150.

116829 Documentation The dynamic AMR FD is missing from the SR4.1.1.0 document set.

nanoGSM 4.1.8 circuitBSC System Release Note Known Issues and Workarounds © ip.access Ltd Page 31

7 KNOWN ISSUES AND WORKAROUNDS

7.1 Issues in SR4.1.8.0

MKS Id Product Summary Network Impact Workaround

31557 nanoBTS EDGE Mismatch in chanReq Counter in MF_CCCH_UTILISATION measurement.

Wrong counter values are displayed.

Divide measurement by 2.

76073 Config Manager The Encryption Preferred List is empty in Config Manager.

If the encryption list is blank while attempting handover, handover will fail with cause no encryption.

If the user does not want encryption, the “No Encryption” option should be selected.

82784 Config Manager T3121 expiry is in seconds instead of ms and the minimum value is only 1 second.

None The timer should be configured as if it were ms. For example, for a 3 second timer, enter the value 3000.

83848 nanoBTS Non-EDGE

Software error fifodrv.c#1904 when booting site

Negligible - 90s delay while BTS boots again.

None.

108884 OMC-R Unable to update “objectName" attribute of the BSS object.

The OMC-R client hangs indefinitely.

None.

113178 OMC-R SR4.1.1 OMC-R client startup issues with a user created prior to SR4.1 upgrade.

None. As for almost all "can't log on" issues which are due to problems with the user settings table, a workaround is to drop the table.

159244 BSC BSC is not validating the incoming CBC connection IP Address.

None. Fix mis-configuration of CBC.

165197 OMC-R Exceptions observed while decommissioning the BSC.

None. From the MySQL prompt, delete the row from BSCInformation table where bssFDQN is null and bssId for which it is showing as null/Not available.

169900 nanoBTS EDGE Very high BTS ”UDP overflow alarm on port 23000” seen during FTP download with GbIP and Normal GPRS configured.

Too many alarms can overload OMC-R

Filter the ”UDP overflow alarm on port 23000” using the technical note

NGSM_TN_1045.

173078 nanoBTS Non-EDGE

BTS resets due to timeslot overrun ASSERT in DSP code when 4 1Mb FTP downloads run simultaneously for 30 minutes.

30 second outage. Restrict the number of PDCHs to 4 on non EDGE BTSs.


199875 nanoBTS EDGE Secure GPRS Cell is not coming up after changing the NV attributes and reinitializing the BTS

Secure GPRS does not work with Fallback OML

To enable fallback OML turn off secure GPRS

205351 BSC Currently the OMC-R server sometimes inconsistently updates the BSC information in the database.

Occasionally Log into the OMC-R server using PuTTY session:

1. List the BSCs using the command:

/etc/init.d/ipaccess-bss-manager list

2. Note the BSC(s) [and their "Bss Id" value] with name being shown as "Name not available".

3. For each BSC with name shown as "Name not available" decommission the BSC using the following command:

/etc/init.d/ipaccess-bss-manager decommission <bssId>

Replace the <bssId> with the "Bss Id" noted in step 2.

223740 OMC-R Active Standby failure due to insufficient permission for the root user to replicate the data.

Replicating the database dump from master to slave will fail.

1) Launch a PuTTY session to the slave machine and login as the root user.

2) At the shell prompt run following commands:

# echo "GRANT ALL ON *.* TO 'root'@'%' IDENTIFIED BY 'rootDB';" | mysql -uroot -prootDB

# echo "FLUSH PRIVILEGES;" | mysql -uroot -prootDB

3) Exit the PuTTY session.

4) Continue with step -

"Configure OMCR Active Standby" on the master OMC-R server.

226832 Config Manager Multiple foreign 3G Cells are getting created with exactly the same input values.

3G Cells can be configured incorrectly.

None.

245101 nanoBTS EDGE BTS resets if T3113 set to over 25000

BTS may reset. Do not set T3113 to over 25,000.

262335 BSC failOgHoRecon counter becomes bigger than OgHoCmd counter in the BSC PM logs. Documentation of OgHoCmd needs updating.

The Outgoing HO KPI Performance will be wrong with these counters.

None.


272305 nanoBTS EDGE BTS lock/unlock causes the BTS to never send the GSM08:58 default broadcast message.

Low. After locking/unlocking a BTS, change the default background message in Config Manager to an artificial value and then back to the original value.

304862 BSC Automated BSS upgrade fails while creating the required software release from OMC-R client.

Major Manual upgrade.

7.2 Detailed explanation of the known issues MKS ID 31557 TT No. - Product nanoBTS EDGE Title Mismatch in chanReq Counter in

MF_CCCH_UTILISATION Measurement. Severity Minor Detail Double-incrementing of the MF_CCCH_UTILISATION counter. The

previous fix for this issue has been removed as it caused unwanted side-effects.

Frequency Always Network Impact Wrong counter values are displayed. Work around Divide measurement by 2.

MKS ID 76073 TT No. - Product BSC Title The Encryption Preference List in Config Manager is empty.

Severity Major Detail The Encryption Preference List in Config Manager is empty.

Frequency Always Network Impact If the encryption list is blank while attempting handover, handover will

fail with cause no encryption.

Work around If the user does not want encryption, the “No Encryption” option should be selected.


MKS ID 82784 TT No. - Product Config Manager Title T3121 expiry is in seconds instead of ms and the minimum value is

only 1 second. Severity Minor Detail This is just a display problem where T3121 timer value should be in

milliseconds instead of seconds.

Frequency Always Network Impact None Work around The timer should be configured as if it were ms. For example for a 3

second timer, enter the value 3000.

MKS ID 83848 TT No. - Product nanoBTS Non-EDGE Title Software error fifodrv.c#1904 when booting site. Severity Major Detail Sometimes the FIFO driver runs out of queue space if the other end

is busy.

Frequency Once Network Impact Negligible - 90s delay while BTS boots again. Work around None required, BTS will reboot automatically.


MKS ID 108884 TT No. - Product OMC-R Title Unable to update "objectName" attribute of the BSS object.

Severity Minor Detail This happens only when the BSS attribute modification is required

because the BSS MO [details] is unavailable while trying to modifiy the BSS MO attribute(s). This causes the code to throw a NullPointerException and subsequently the client hangs.

Frequency Always Network Impact The OMC-R client hangs indefinitely. Work around None

MKS ID 113178

TT No. - Product OMC-R Title SR4.1.1 OMC-R Client Startup issues with a user created prior to

SR4.1 upgrade.

Severity Critical Detail This is a problem where there are too many rows in the user settings

table.

Frequency Always Network Impact The OMC-R client is unable to start Work around As for almost all "can't log on" issues which are due to problems with

the user settings table, a workaround is to drop the table.


MKS ID 159244

TT No. - Product BSC Title BSC is not validating the incoming CBC connection IP Address.

Severity Minor Detail The BSC fails to validate the remote IP address on incoming CBC

connections and may accept a connection in error from a mis-configured CBC.

Frequency Always Network Impact Mis-configurations of more than one CBC may result in the wrong

CBC connecting to a BSC. Work around Fix mis-configuration of CBC.

MKS ID 165197

TT No. - Product OMC-R Title Exceptions observed while decommissioning the BSC.

Severity Critical Detail While decommissioning if more than 1 entry is found in the

BscInformation table then an exception is thrown - "More than one entity matches the finder criteria".

Frequency Always Network Impact None Work around From MySQL prompt, delete the row from BSCInformation table

where bssFDQN is null and bssId for which it is showing as null/Not available.


MKS ID 169900

TT No. - Product nanoBTS EDGE Title IPA BTS - UDP Packets Discarded - UDP overflow alarm on port

23000.

Severity Minor Detail Under heavy load conditions the BTS may discard some NS/IP data

packets to preserve service. Frequency Observed only with GB/IP when using normal GPRS configuration

(i.e. not multiplex or secure). Network Impact Too many alarms can overload the OMC-R.

Work around Filter the ”UDP overflow alarm on port 23000” using the technical note NGSM_TN_1045.

MKS ID 173078 TT No. - Product nanoBTS Title BTS resets due to timeslot overrun ASSERT in DSP code when 4

1Mb FTP downloads run simultaneously for 30 minutes.

Severity Critical Detail When doing sustained continuous traffic loading tests on several

mobiles at the same time a BTS software error was seen on a Non-EDGE multi-TRX BTS.

Frequency Always Network Impact 30 second outage

Work around Restrict the number of PDCHs to 4 on the non EDGE BTSs.


MKS ID 199875 TT No. - Product nanoBTS EDGE Title A BTS configured with a secure GPRS cell does not come up after

changing the NV attributes and reinitialising the BTS. Severity Major Detail The Fallback OML state machine is not working properly (this is the

feature whereby a second OML IP address is specified in the NV Attributes typically via BTS Installer). This is particularly noticeable if security is enabled, but may also apply to non-secure use cases too. The state machine neither times out (to use the alternate address), nor uses the supplied port numbers correctly.

Frequency Seen twice. Network Impact Secure GPRS does not work with Fallback OML. Work around To enable Fallback OML turn off secure GPRS.


MKS ID 205351 TT No. - Product BSC Title For the some of the BSC's, the BSS name is displayed as "Not

Available" which is incorrect. Severity Major Detail The current design of the OMC-R server may sometimes

inconsistently handle the BSC information while the BSC is registering with the OMC-R. Due to this the BSC [object] name and other attributes of the BSC may not get updated in the database. Since the "name attribute" is not properly updated, running /etc/init.d/ipaccess-bss-manager list command will show [Name not available]. This is known to happen at the time of upgrade/installation only.

Frequency Occasionally Network Impact None. Work around 1. List the BSSs using the command:

/etc/init.d/ipaccess-bss-manager list 2. For the BSS with name set to "Name not available" note the "Bss Id". 3. Decommission the BSS with name shown as "Name not available" using the following command: /etc/init.d/ipaccess-bss-manager decommission <Bss Id> Replace the <BssId> with the "Bss Id" noted in step 2.


MKS ID 223740 TT No. - Product OMC-R Title Active Standby Configuration is failing.

Severity Critical Detail While doing the active standby configuration, a MySQL DB

permission issue when replicating the database dump from master to slave is failing.

Frequency Seen twice. Network Impact Replicating the database dump from master to slave will fail.

Work around 1) Launch a PuTTY session to the slave machine and login as the root user. 2) At the shell prompt run following commands: # echo "GRANT ALL ON *.* TO 'root'@'%' IDENTIFIED BY 'rootDB';" | mysql -uroot -prootDB # echo "FLUSH PRIVILEGES;" | mysql -uroot -prootDB 3) Exit the PuTTY session. 4) Continue with step - "Configure OMCR Active Standby" on the master OMC-R server.

MKS ID 226832 TT No. Product Config Manager Title Unique check for Foreign 3G Cell managed objects.

Severity Major Detail While creating foreign 3G cells using v125d0, multiple foreign 3G

cells are getting created with exactly the same input value.

Frequency Always. Network Impact 3G Cells can be configured incorrectly.

Work around None.


MKS ID 245101 TT No. - Product nanoBTS EDGE Title BTS resets if T3113 set to over 25000.

Severity Major Detail BTS may reset if T3113 set to over 25000

Exact cause as yet unknown Frequency Always Network Impact BTS may reset

Work around Do not set T3113 to over 25,000

MKS ID 262335 TT No. Product BSC Title failOgHoRecon counter becomes bigger than OgHoCmd counter in

the BSC PM logs. Severity Major Detail failOgHoRecon counter becomes bigger than OgHoCmd counter in

the BSC PM logs – documentation requires an update.

Frequency always Network Impact The outgoing HO KPI performance will be wrong with these counters. Work around None.


MKS ID 272305 TT No. Product nanoBTS EDGE Title Default broadcast message is no longer sent after a BTS lock/unlock.

Severity Minor Detail BTS lock/unlock causes the BTS to never send the GSM 08:58

default broadcast message.

Frequency Always Network Impact BTSs having been locked never send the default broadcast message

again until a power cycle is performed.

Work around After locking/unlocking a BTS, change the default background message in the Config Manager to an artificial value and then back to the original value.

MKS ID 304862 TT No. - Product BSC Title Automated BSS upgrade fails while creating the required Software

Release from OMC-R client Severity Major Detail BSC upgrade intermittently fails at validation step, just before the

BSC is upgraded. Issue under further investigation. The issue is seen from 4.1.5.0 onwards.

Frequency Intermittent. Network Impact Automated upgrade of BSC may fail. Work around Manual upgrade.

nanoGSM 4.1.8 circuitBSC System Release Note · At the IuBC interface (CBC – BSC interface), and...

Documents

Transcript of nanoGSM 4.1.8 circuitBSC System Release Note · At the IuBC interface (CBC – BSC interface), and...