Nokia BSS Gateway Config Distribution Note

7/30/2019 Nokia BSS Gateway Config Distribution Note

1/22

Netcool Performance Manager for Wireless

Version 3.5.0.1

Nokia BSS Gateway Configuration Distribution Note


2/22

TIVOLINETCOOLPERFORMANCE MANAGER FOR WIRELESSNOKIA BSSGATEWAY CONFIGURATION DISTRIBUTION NOTE

This edition applies to IBM Tivoli Netcool Performance Manager for Wireless and to allsubsequent releases and modifications until otherwise indicated in new editions.

Copyright International Business Machines Corporation, 2009. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADPSchedule Contract with IBM Corp.

Note: Before using this information and the product it supports, read the information inNotices on page 15.


3/22


Nokia-BSS-GCDN - iii

Table of Contents

1 About this Documentation ................................................................................................................. 1

1.1 Audience ......................................................................................................................................11.2 Required Skills and Knowledge ...................................................................................................1

2 Associated Documents ...................................................................................................................... 2

2.1 Referenced Documents ...............................................................................................................22.2 Other Related Documents............................................................................................................2

3 Introduction......................................................................................................................................... 33.1 Vendor Gateway Version .............................................................................................................3

4 Release History................................................................................................................................... 4

4.1 Release 3.5.0.1 ............................................................................................................................44.2 Release 3.4.0 ...............................................................................................................................44.3 Release 3.3.0 ...............................................................................................................................4

5 Data type and releases supported .................................................................................................... 6

5.1 Raw input files..............................................................................................................................65.2 Hierarchy input files......................................................................................................................7

6 Configurations .................................................................................................................................... 8

6.1 Transfer Engine configuration......................................................................................................8

6.2 Parser Engine configuration.........................................................................................................86.2.1 Initial PIF File Name Convention .............................................................................................86.2.2 Block Name..............................................................................................................................86.2.3 Counter Value........................................................................................................................116.2.4 NETWORK_ID and REGION_ID...........................................................................................11

6.3 Post Parser user configuration...................................................................................................116.3.1 Manipulation of Data blocks...................................................................................................116.3.2 Additional Block Output ......................................................................................................... 126.3.3 Additional Block Output (VENDOR NEUTRAL).....................................................................13

Appendix A Notices and Trademarks................................................................................................. 15


4/22


5/22


Nokia-BSS-GCDN - 1

1 About this Documentation

1.1 Audience

The target audience of this document is IBM Performance Manager for Wireless customers. They should be

familiar with telecommunication and IT principles and should also have a good understanding of Solaris.

IMPORTANT: Before attempting an installation of Performance Manager for Wireless you are strongly

advised to read the release notes and any readme files distributed with your Performance Manager for

Wireless software. Readme files and release notes may contain information specific to your installation not

contained in this guide. Failure to consult readme files and release notes may result in a corrupt, incomplete

or failed installation.

Note: Performance Manager for Wireless Administrators should not, without prior consultation and

agreement from IBM, make any changes to the Index Organized tables or database schema. Changes to the

Index Organized tables or database schema may result in corruption of data and failure of the Performance

Manager for Wireless System. This applies to all releases of Performance Manager for Wireless using allversions of interfaces.

1.2 Required Skills and Knowledge

This guide assumes you are familiar with the following:

General IT Principles

Sun Solaris Operating System

Oracle Database

Windows operating systems

Graphical User Interfaces

Network Operator's OSS and BSS systems architectureThis guide also assumes that you are familiar with your companys network and with procedures forconfiguring, monitoring, and solving problems on your network.


6/22


Nokia-BSS-GCDN - 2

2 Associated Documents

The following documentation accompanies this release:

2.1 Referenced Documents

Document Name Document Description

[Gateways Install Note] This document describes the steps required to install and

run a Gateway.

2.2 Other Related Documents

Document Name Document Description

[Gateway FrameworkUser Guide]

Gateway Framework User Guide describing themanagement and configuration of the Gateway

Framework.

[Nokia Ascii User

Guide]

User Guide describing the management and configuration

of the Vendor Gateway.


7/22


Nokia-BSS-GCDN - 3

3 Introduction

You should read this Distribution Note before proceeding to install the Gateway Configuration.

For information on the Gateway Framework, its configuration and use refer to the [Gateway

Framework User Guide].

The Gateway Framework and Vendor Gateway are supplied as separate packages. As part of theVendor Gateway installation process, it must reference a Gateway Framework installation. This

separation simplifies the maintenance and version control of multiple vendor Gateway installationson a single server.

This Distribution Note provides an overview of the release history of the Gateway Configuration.

3.1 Vendor Gateway Version

This Gateway Configuration requires the following Vendor Gateway:

- Nokia Ascii Gateway 3.5.0.2


8/22


Nokia-BSS-GCDN - 4

4 Release History

4.1 Release 3.5.0.1

Release date 05 November 2009.

Listed below are the enhancements to this release.

Enhancement

#

Description

1 Support for Nokia BSS S13 BSC data.

Listed below are the bugs fixed in this release.

Bug# DescriptionN/A N/A

4.2 Release 3.4.0

Release date 10 March 2008.

Listed below are the enhancements to this release.

Enhancement

#

Description

1 Support for Nokia BSS S12 BSC data.

Listed below are the bugs fixed in this release.

Bug# Description

N/A N/A

4.3 Release 3.3.0

Release date 16 August 2007.

Listed below are the implementation to this release.


9/22


Nokia-BSS-GCDN - 5

Enhancement

#

Description

1 Support for Nokia BSS S11.5 BSC data.

Important Notes:

Below are changes to the configuration entries for the Transfer Engine.


10/22


Nokia-BSS-GCDN - 6

5 Data type and releases supported

Gateway Configuration

Release Directory

Vendor Performance data Supported Vendor

Versions13 Nokia BSS S13, S12

r12 Nokia BSS S12

s11.5 Nokia BSS S11.5

5.1 Raw input files

Scope Attended Format/Syntax

Input files names to expect BSC939822.1.200705052100.14972

Where

BSC939822 NE ID1 Measurement type

200705052100 Starting time of the

measurement period14972 Temporary ID. It is aunique identification which

the ASCII file filterprocess gives to the file.

Input file formats to expect Header format is as below:

,,,;

Counter data is as below:

,,,,,...,,;,

Equipment/devices to

expect data

Nokia NetAct Performance Management

System


11/22


Nokia-BSS-GCDN - 7

Extraction mechanism Nokia NetAct Performance Interface.

Transfer mechanism Ftp

5.2 Hierarchy input files

Scope Attended Format/Syntax

Input files names to expect 1)hierarchy.txt or hierarchy.dat2) trxhier.txt or trxhier.dat

3)objects.txt or objects.dat

Input file formats to expect Comma separated values with semi

colon as line delimiter with the followingfields for each file:

1) hierarchy.txt or hierarchy.dat

ASCII_ID,BTS_ID,BSCNAME,BTSNAME,BSNAME,LACID,CELL_ID,DEFTCH,DEFCCH;

2) trxhier.txt or trxhier.dat

ASCII_ID,BTS_ID,TRX_ID,TRXNAME;

3) objects.txt or objects.dat

OBJECT_INSTANCE,NAME;

Equipment/devices toexpect data

Nokia NetAct Performance ManagementSystem

Extraction mechanism Hierarchy data is extracted using SQLextraction utility.

Transfer mechanism FTP


12/22


Nokia-BSS-GCDN - 8

6 Configurations

6.1 Transfer Engine configuration

Transfer engine can be configured to transfer raw input files into the Gateway

input processing directory (e.g., spool/input_d/). Instructions for configuringTransfer engine can be found in the Gateway Framework User Guide.

6.2 Parser Engine configurationRefer to the Nokia ASCII Gateway User Guide for the Engine Configuration forNokia BSS.

6.2.1 Initial PIF File Name Convention

Initial PIF file name is configured to have the following convention:

-#--#--#--#--#--#-I.pif

Where,STARTDATE: is in the format ddmmmyyyy,

STARTTIME: is in the format HH:MM,

NETWORK_TYPE: alpha characters of the first field of the raw file name,

BSC_ID: numeric characters of the first field of the raw file name,

OMTYPE: second field of the raw file name.

6.2.2 Block Name

The Object Management Type is mapped to the Block Name in the

NOKIA_BSS_Config.pm.


13/22


Nokia-BSS-GCDN - 9

Measurement

typecorrespondence

in theperformance

raw files Output Block Names

1 P_NBSC_TRAFFIC

2 P_NBSC_RES_AVAIL

3 P_NBSC_RES_ACCESS

4 P_NBSC_HO

5 P_NBSC_POWER

6 P_NBSC_LOAD

7 P_NBSC_AVAIL

9 P_NBSC_OSI1

10 P_NBSC_OSI2

11 P_NBSC_OSI3

12 P_NBSC_OSI4

13 P_NBSC_UNDEF_ADJ_CELL

14 P_NBSC_RX_QUAL

15 P_NBSC_HO_ADJ

27 P_NBSC_GPRS_CELL_RESEL_OBS

29 P_NBSC_DCB_OBS

50 P_NBSC_CC

51 P_NBSC_CC_PM

52 P_NBSC_UNDERLAY

53 P_NBSC_RX_STATISTICS

54 P_NBSC_LINK_BALANCE

55 P_NBSC_TIMING_ADVANCE

56 P_NBSC_TRX_AVAIL

57 P_NBSC_SERVICE

58 P_NBSC_MS_SPEED

59 P_NBSC_DUAL_BAND

60 P_NBSC_CI_RATIO

61 P_NBSC_HOT_SPOT

62 P_NBSC_DMR

63 P_NBSC_DN2

65 P_NBSC_ET_BSC

66 P_NBSC_ET_TCSM

67 P_NBSC_HIGH_SPEED_DATA

68 P_NBSC_TRE

69 P_NBSC_TRU_BIE


14/22


Nokia-BSS-GCDN - 10

69 P_NBSC_TRE_SEL

70 P_NBSC_CHANNEL_FINDER

71 P_NBSC_MS_CAPABILITY

72 P_NBSC_PACKET_CONTROL_UNIT73 P_NBSC_RLC_BLOCKS_PER_TRX

74 P_NBSC_FRAME_RELAY

74 P_NBSC_FRAME_RELAY

75 P_NBSC_DEF_ADJ_CELL

76 P_NBSC_DYNAMIC_ABIS

77 P_NBSC_FER

78 P_NBSC_PBS

79 P_NBSC_CODING_SCHEME

89 P_NBSC_REVERSED_HUNTING

90 P_NBSC_QOS91 P_NBSC_PBCCH_AVAIL

92 P_NBSC_NON_BCCH_LAYER_OFFS

93 P_NBSC_UTRAN_HO_ADJ_CELL

94 P_NBSC_UTRAN_NCELL_SIG_LEVEL

95 P_NBSC_CELL_RESELECTION

96 P_NBSC_GPRS_RX_STAT

97 P_NBSC_EQOS

98 P_NBSC_GB_OVER_IP

99 P_NBSC_TOTAL_FEP

100 P_NBSC_DFCA101 P_NBSC_DFCA_ASSIGN

102 P_NBSC_BSC_BSC

103 P_NBSC_WPS

104 P_NBSC_IMSI_HO

105 P_NBSC_PS_DTM (S12 added)

106 P_NBSC_CS_DTM (S12 added)

107 P_NBSC_AMR_RX_QUAL (S12 added)

108 P_NBSC_DFCA_SAIC (S12 added)

109 P_NBSC_SOFT_CHANNEL_CAP

513 P_NBSC_STM1 (S12 added)516 P_NBSC_SONET_SDH (S12 added)

517 P_NBSC_PBS_AGGR (S12 VN - added)

518 CELL_DATA (S12 VN - added)

519

P_NBSC_CODING_SCHEME_MCS (S12 VN-

added)

520 P_NBSC_RES_ACCESS_AGGR (S12 VN - added)


15/22


Nokia-BSS-GCDN - 11

521 P_NBSC_POWER_AGGR (S12 VN added)

110 P_NBSC_PCU_UTILIZATION (S13 added)

111 P_NBSC_AMR_PPC (S13 added)

112 P_NBSC_AMR_SIGNALLING (S13 added

)226 P_NBSC_ABIS_D_CHANNEL (S13 added)

661 P_NBSC_ASSOC_SET (S13 added)

6610 P_NBSC_ASSOC_INDEX (S13 added)

990 P_NBSC_TOTAL_FEP_HEADER (S13 added)

6.2.3 Counter Value

N/A

6.2.4 NETWORK_ID and REGION_ID

The Engine configuration extracts the following information from the directorypath where the raw input files are stored (if available).

NETWORK_ID - Second last directory in the path

REGION_ID - Last directory in the path

Example:

spool/input_d/NETWORK_1/REGION_1/A20070510.2300+0200-0000+0200_INode-GQ01

The NETWORK_ID is 1 and REGION_ID is 1

6.3 Post Parser user configuration

The following data blocks were manipulated to produce LIF output according to

the loader specification.

6.3.1 Manipulation of Data blocks

Output Block Names Post Parsing Rules Applied

P_NBSC_FRAME_RELAY SPLIT_RECORDS: Split DLCI countersfor each DLCI_#_ID to DLCI_ID under a

BEARER_ID into individual records. PIFoutput only.


16/22


Nokia-BSS-GCDN - 12

DATALINE_WHERE: Remove unused

DLCI records, where DLCI_ID is emptyor -1. PIF and LIF are output.

PIF_REMOVE: Remove the initial PIFfile.

P_NBSC_UNDERLAY PERLIZE: Populate the CELL_ID withHCELL_ID inserted from the hierarchy

data if empty. PIF and LIF are output.


P_NBSC_BSC_BSC PERLIZE: Include _ID suffix to SPCcounter name.


P_NBSC_UTRAN_HO_ADJ_CELL PERLIZE: Include _ID suffix to all

SAC, MNC and MCC counter names.

PIF_REMOVE: Remove the initial PIF

file.

All other blocks BATCHFILES: All other blocks arebeing batched into their respective blockname, date and time into LIF.

6.3.2 Additional Block Output

Additional Output Block

Names

Post Parsing Rules Applied

P_NBSC_FRAME_RELAY_GROUP ACCUMULATE: Aggregate DLCI

counters to BEARER_ID and NODE_IDlevel from the last PIF output for

P_NBSC_FRAME_RELAY above. LIFoutput only.

P_NBSC_UNDERLAY_INT_CELL The following rules are applied after the

last P_NBSC_UNDERLAY manipulationabove.

SPLIT_RECORDS: Split interferingCELL counters for each CELL#_ID to

CELL_ID into individual records. PIF


17/22


Nokia-BSS-GCDN - 13

output only.

PERLIZE: Rename CELL counters asper original raw counter names. LIF

output only.CELLDATA JOIN: Join P_NBSC_TRAFFIX and

P_NBSC_RES_AVAIL data blocks byCELL_ID and BTS_ID into CELLDATA

block. LIF output only.

P_NBSC_DFCA_SAIC_AGGR ACCUMULATE: Accumulates theP_NBSC_DFCA_SAIC counters at theCELL_ID level based on the PIF outputfor the block P_NBSC_DFCA_SAIC.

6.3.3 Additional Block Output (VENDOR NEUTRAL)

Additional Output Block

Names

Post Parsing Rules Applied

CELL_DATA JOIN: Joins the 2 blocks

P_NBSC_RES_AVAIL andP_NBSC_TRAFFIC based on the

CELL_ID.

P_NBSC_PBS_AGGR ACCUMULATE: Accumulates theP_NBSC_PBS counters at the NODE_ID

level based on the PIF output for theblock P_NBSC_PBS.

P_NBSC_CODING_SCHEME_MCS FILE_SPLIT: Splits theP_NBSC_CODING_SCHEME PIF recordsaccording to its CODING_SCHEME value

into individual PIF records for the block.

PERLIZE: All counters in this block aresuffixed with the string

MCS+. Output isthen left in its own PIF.

Counters undergo complex KPIcalculations


18/22


Nokia-BSS-GCDN - 14

JOIN: Joins the PIFs resulting from thePERLIZE rule into a single block called

P_NBSC_CODING_SCHEME_MCS.P_NBSC_RES_ACCESS_AGGR ACCUMULATE: Accumulates the

P_NBSC_RES_ACCESS counters at theCELL_ID level based on the PIF output

for the block P_NBSC_RES_ACCESS.

P_NBSC_POWER_AGGR ACCUMULATE: Accumulates theP_NBSC_POWER counters at theCELL_ID level based on the PIF outputfor the block P_NBSC_POWER.


19/22


Nokia-BSS-GCDN - 15

Appendix A Notices and Trademarks

This appendix contains the following:

Notices

Trademarks

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in other countries. Consult

your local IBM representative for information on the products and services currently available in your area.

Any reference to an IBM product, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product, program, or service that

does not infringe any IBM intellectual property right may be used instead. However, it is the user's

responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document.

The furnishing of this document does not grant you any license to these patents. You can send license

inquiries, in writing, to:

IBM Director of LicensingIBM Corporation

North Castle Drive

Armonk NY 10504-1785

U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property

Department in your country or send inquiries, in writing, to:

IBM World Trade Asia Corporation

Licensing2-31 Roppongi 3-chome

Minato-ku

Tokyo 106-0032

Japan.

The following paragraph does not apply to the United Kingdom or any other country where such provisions

are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATIONPROVIDES THIS PUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHER

EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF

NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some

states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this

statement may not apply to you.


20/22


Nokia-BSS-GCDN - 16

This information could include technical inaccuracies or typographical errors. Changes are periodically

made to the information herein; these changes will be incorporated in new editions of the publication. IBM

may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not inany manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the

materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without

incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the

exchange of information between independently created programs and other programs (including this one)

and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation

5300 Cork Airport Business Park

Kinsale RoadCork

Ireland.

Such information may be available, subject to appropriate terms and conditions, including in some cases,

payment of a fee.

The licensed program described in this document and all licensed material available for it are provided byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any

equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of those products, their

published announcements or other publicly available sources. IBM has not tested those products and cannot

confirm the accuracy of performance, compatibility or any other claims related to non-IBM products.

Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice,and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them

as completely as possible, the examples include the names of individuals, companies, brands, and products.

All of these names are fictitious and any similarity to the names and addresses used by an actual business

enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.


21/22


Nokia-BSS-GCDN - 17

Trademarks

IBM, IBM logo, Tivoli, and Netcool are trademarks of International Business Machines Corporation in the

United States, other countries or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the

United States and other countries.

Other company, product or service names may be trademarks or service marks of others.


22/22

IBM Copyright IBM Corporation 2009

International Business Machines Corporation5300 Cork Airport

Business ParkKinsale RoadCorkIreland

Printed in the Republic of IrelandAll Rights ReservedIBM, IBM logo, Tivoli, and Netcool are trademarksof International Business Machines Corporation inthe United States, other countries or both.

Other company, product and service names maybe trademarks or service marks of others.