Nokia BSS Gateway Config Distribution Note

Netcool Performance Manager for Wireless
Version 3.5.0.1
Nokia BSS Gateway Configuration Distribution Note
TIVOLI NETCOOL PERFORMANCE M ANAGER FOR WIRELESS NOKIA BSS GATEWAY CONFIGURATION DISTRIBUTION NOTE
Note: Before using this information and the product it supports, read the information in Notices on page 15.
This edition applies to IBM Tivoli Netcool Performance Manager for Wireless and to all subsequent 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 ADP Schedule Contract with IBM Corp.
Table of Contents
1 About this Documentation................................................................................................................. 1 1.1 Audience ......................................................................................................................................1 1.2 Required Skills and Knowledge ...................................................................................................1 2 Associated Documents ...................................................................................................................... 2 2.1 Referenced Documents ...............................................................................................................2 2.2 Other Related Documents............................................................................................................2 3 Introduction ......................................................................................................................................... 3 3.1 Vendor Gateway Version .............................................................................................................3 4 Release History ................................................................................................................................... 4 4.1 Release 3.5.0.1 ............................................................................................................................4 4.2 Release 3.4.0 ...............................................................................................................................4 4.3 Release 3.3.0 ...............................................................................................................................4 5 Data type and releases supported .................................................................................................... 6 5.1 Raw input files ..............................................................................................................................6 5.2 Hierarchy input files......................................................................................................................7 6 Configurations .................................................................................................................................... 8 6.1 Transfer Engine configuration ......................................................................................................8 6.2 Parser Engine configuration.........................................................................................................8 6.2.1 Initial PIF File Name Convention .............................................................................................8 6.2.2 Block Name..............................................................................................................................8 6.2.3 Counter Value ........................................................................................................................11 6.2.4 NETWORK_ID and REGION_ID ...........................................................................................11 6.3 Post Parser user configuration...................................................................................................11 6.3.1 Manipulation of Data blocks...................................................................................................11 6.3.2 Additional Block Output .........................................................................................................12 6.3.3 Additional Block Output (VENDOR NEUTRAL).....................................................................13 Appendix A Notices and Trademarks................................................................................................. 15
Nokia-BSS-GCDN - iii
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 all versions 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 architecture
This guide also assumes that you are familiar with your companys network and with procedures for configuring, monitoring, and solving problems on your network.
Nokia-BSS-GCDN - 1
2 Associated Documents
The following documentation accompanies this release:
2.1 Referenced Documents

Document Name [Gateways Install Note] Document Description This document describes the steps required to install and run a Gateway.
2.2 Other Related Documents

Document Name [Gateway Framework User Guide] [Nokia Ascii User Guide] Document Description Gateway Framework User Guide describing the management and configuration of the Gateway Framework. User Guide describing the management and configuration of the Vendor Gateway.
Nokia-BSS-GCDN - 2
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 the Vendor Gateway installation process, it must reference a Gateway Framework installation. This separation simplifies the maintenance and version control of multiple vendor Gateway installations on 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
Nokia-BSS-GCDN - 3
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#

N/A
Description
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#

N/A
Description
N/A
4.3 Release 3.3.0

Release date 16 August 2007. Listed below are the implementation to this release.
Nokia-BSS-GCDN - 4
Enhancement Description #
1 Support for Nokia BSS S11.5 BSC data.
Important Notes: Below are changes to the configuration entries for the Transfer Engine.
Nokia-BSS-GCDN - 5
5 Data type and releases supported

Gateway Configuration Release Directory s13 r12 s11.5
Vendor Performance data Nokia BSS Nokia BSS Nokia BSS
Supported Vendor Version S13, S12 S12 S11.5
5.1 Raw input files

Scope Input files names to expect Attended Format/Syntax BSC939822.1.200705052100.14972 Where BSC939822 NE ID 1 Measurement type 200705052100 Starting time of the measurement period 14972 Temporary ID. It is a unique identification which the ASCII file filter process gives to the file. Input file formats to expect Header format is as below:
<NE_TYPE><NE_ID>,<measurement type>,<measurement time>,<period duration>;
Counter data is as below:

<object ID>, <counter name>,<counter value>, <counter name>,<counter value>, ..., <counter name>,<counter value>; <object ID>,
Equipment/devices to expect data
Nokia NetAct Performance Management System

Nokia-BSS-GCDN - 6
Extraction mechanism Transfer mechanism
Nokia NetAct Performance Interface. Ftp
5.2 Hierarchy input files

Scope Input files names to expect Attended Format/Syntax 1) hierarchy.txt or hierarchy.dat 2) trxhier.txt or trxhier.dat 3) objects.txt or objects.dat Comma separated values with semi colon as line delimiter with the following fields for each file: 1) hierarchy.txt or hierarchy.dat
ASCII_ID,BTS_ID,BSCNAME,BTSNAME,BSNAME,LACID,CELL _ID,DEFTCH,DEFCCH;
Input file formats to expect
2) trxhier.txt or trxhier.dat
ASCII_ID,BTS_ID,TRX_ID,TRXNAME;
3) objects.txt or objects.dat
OBJECT_INSTANCE,NAME;
Equipment/devices to expect data Extraction mechanism Transfer mechanism
Nokia NetAct Performance Management System Hierarchy data is extracted using SQL extraction utility. FTP
Nokia-BSS-GCDN - 7
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 configuring Transfer engine can be found in the Gateway Framework User Guide.
6.2 Parser Engine configuration

Refer to the Nokia ASCII Gateway User Guide for the Engine Configuration for Nokia BSS. 6.2.1 Initial PIF File Name Convention Initial PIF file name is configured to have the following convention:
<BLOCK_NAME>-#-<STARDATE>-#-<STARTTIME>-#-<NETWORK_TYPE>-#-<BSC_ID>-#-<OMTYPE>-#-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.
Nokia-BSS-GCDN - 8
Measurement type correspondence in the performance raw files 1 2 3 4 5 6 7 9 10 11 12 13 14 15 27 29 50 51 52 53 54 55 56 57 58 59 60 61 62 63 65 66 67 68 69
Output Block Names P_NBSC_TRAFFIC P_NBSC_RES_AVAIL P_NBSC_RES_ACCESS P_NBSC_HO P_NBSC_POWER P_NBSC_LOAD P_NBSC_AVAIL P_NBSC_OSI1 P_NBSC_OSI2 P_NBSC_OSI3 P_NBSC_OSI4 P_NBSC_UNDEF_ADJ_CELL P_NBSC_RX_QUAL P_NBSC_HO_ADJ P_NBSC_GPRS_CELL_RESEL_OBS P_NBSC_DCB_OBS P_NBSC_CC P_NBSC_CC_PM P_NBSC_UNDERLAY P_NBSC_RX_STATISTICS P_NBSC_LINK_BALANCE P_NBSC_TIMING_ADVANCE P_NBSC_TRX_AVAIL P_NBSC_SERVICE P_NBSC_MS_SPEED P_NBSC_DUAL_BAND P_NBSC_CI_RATIO P_NBSC_HOT_SPOT P_NBSC_DMR P_NBSC_DN2 P_NBSC_ET_BSC P_NBSC_ET_TCSM P_NBSC_HIGH_SPEED_DATA P_NBSC_TRE P_NBSC_TRU_BIE
Nokia-BSS-GCDN - 9
69 70 71 72 73 74 74 75 76 77 78 79 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 513 516 517 518 519 520
P_NBSC_TRE_SEL P_NBSC_CHANNEL_FINDER P_NBSC_MS_CAPABILITY P_NBSC_PACKET_CONTROL_UNIT P_NBSC_RLC_BLOCKS_PER_TRX P_NBSC_FRAME_RELAY P_NBSC_FRAME_RELAY P_NBSC_DEF_ADJ_CELL P_NBSC_DYNAMIC_ABIS P_NBSC_FER P_NBSC_PBS P_NBSC_CODING_SCHEME P_NBSC_REVERSED_HUNTING P_NBSC_QOS P_NBSC_PBCCH_AVAIL P_NBSC_NON_BCCH_LAYER_OFFS P_NBSC_UTRAN_HO_ADJ_CELL P_NBSC_UTRAN_NCELL_SIG_LEVEL P_NBSC_CELL_RESELECTION P_NBSC_GPRS_RX_STAT P_NBSC_EQOS P_NBSC_GB_OVER_IP P_NBSC_TOTAL_FEP P_NBSC_DFCA P_NBSC_DFCA_ASSIGN P_NBSC_BSC_BSC P_NBSC_WPS P_NBSC_IMSI_HO P_NBSC_PS_DTM (S12 added) P_NBSC_CS_DTM (S12 added) P_NBSC_AMR_RX_QUAL (S12 added) P_NBSC_DFCA_SAIC (S12 added) P_NBSC_SOFT_CHANNEL_CAP P_NBSC_STM1 (S12 added) P_NBSC_SONET_SDH (S12 added) P_NBSC_PBS_AGGR (S12 VN - added) CELL_DATA (S12 VN - added) P_NBSC_CODING_SCHEME_MCS (S12 VNadded) P_NBSC_RES_ACCESS_AGGR (S12 VN - added)
Nokia-BSS-GCDN - 10
521 110 111 112 226 661 6610 990 6.2.3 Counter Value N/A
P_NBSC_POWER_AGGR (S12 VN added) P_NBSC_PCU_UTILIZATION (S13 added) P_NBSC_AMR_PPC (S13 added) P_NBSC_AMR_SIGNALLING (S13 added) P_NBSC_ABIS_D_CHANNEL (S13 added) P_NBSC_ASSOC_SET (S13 added) P_NBSC_ASSOC_INDEX (S13 added) P_NBSC_TOTAL_FEP_HEADER (S13 added)
6.2.4 NETWORK_ID and REGION_ID The Engine configuration extracts the following information from the directory path 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+02000000+0200_INode-GQ01 The NETWORK_ID is 1 and REGION_ID is 1
6.3 Post Parser user configuration

<Details any post parser process, i.e. unpegging, aggregation, info insert, and block join> 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 P_NBSC_FRAME_RELAY Post Parsing Rules Applied SPLIT_RECORDS: Split DLCI counters for each DLCI_#_ID to DLCI_ID under a BEARER_ID into individual records. PIF output only.
Nokia-BSS-GCDN - 11
DATALINE_WHERE: Remove unused DLCI records, where DLCI_ID is empty or -1. PIF and LIF are output. PIF_REMOVE: Remove the initial PIF file. P_NBSC_UNDERLAY PERLIZE: Populate the CELL_ID with HCELL_ID inserted from the hierarchy data if empty. PIF and LIF are output. PIF_REMOVE: Remove the initial PIF file. P_NBSC_BSC_BSC PERLIZE: Include _ID suffix to SPC counter name. PIF_REMOVE: Remove the initial PIF file. 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 are being batched into their respective block name, date and time into LIF.
6.3.2 Additional Block Output Additional Output Block Post Parsing Rules Applied Names P_NBSC_FRAME_RELAY_GROUP ACCUMULATE: Aggregate DLCI counters to BEARER_ID and NODE_ID level from the last PIF output for P_NBSC_FRAME_RELAY above. LIF output only. P_NBSC_UNDERLAY_INT_CELL The following rules are applied after the last P_NBSC_UNDERLAY manipulation above. SPLIT_RECORDS: Split interfering CELL counters for each CELL#_ID to CELL_ID into individual records. PIF
Nokia-BSS-GCDN - 12
output only. PERLIZE: Rename CELL counters as per original raw counter names. LIF output only. CELLDATA JOIN: Join P_NBSC_TRAFFIX and P_NBSC_RES_AVAIL data blocks by CELL_ID and BTS_ID into CELLDATA block. LIF output only. ACCUMULATE: Accumulates the P_NBSC_DFCA_SAIC counters at the CELL_ID level based on the PIF output for the block P_NBSC_DFCA_SAIC.
P_NBSC_DFCA_SAIC_AGGR
6.3.3 Additional Block Output (VENDOR NEUTRAL) Additional Output Block Names CELL_DATA Post Parsing Rules Applied JOIN: Joins the 2 blocks P_NBSC_RES_AVAIL and P_NBSC_TRAFFIC based on the CELL_ID. ACCUMULATE: Accumulates the P_NBSC_PBS counters at the NODE_ID level based on the PIF output for the block P_NBSC_PBS.
P_NBSC_PBS_AGGR
P_NBSC_CODING_SCHEME_MCS FILE_SPLIT: Splits the P_NBSC_CODING_SCHEME PIF records according to its CODING_SCHEME value into individual PIF records for the block. PERLIZE: All counters in this block are suffixed with the string MCS+<CODING_SCHEME>. Output is then left in its own PIF. Counters undergo complex KPI calculations
Nokia-BSS-GCDN - 13
JOIN: Joins the PIFs resulting from the PERLIZE 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 the CELL_ID level based on the PIF output for the block P_NBSC_RES_ACCESS. ACCUMULATE: Accumulates the P_NBSC_POWER counters at the CELL_ID level based on the PIF output for the block P_NBSC_POWER.
P_NBSC_POWER_AGGR
Nokia-BSS-GCDN - 14
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 IBM product, 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 Licensing IBM 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 Licensing 2-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 CORPORATION PROVIDES 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.
Nokia-BSS-GCDN - 15
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 this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any 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 Road Cork 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 by IBM 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.
Nokia-BSS-GCDN - 16
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.
Nokia-BSS-GCDN - 17
IBM
Copyright IBM Corporation 2009 International Business Machines Corporation 5300 Cork Airport Business Park Kinsale Road Cork Ireland Printed in the Republic of Ireland All Rights Reserved IBM, IBM logo, Tivoli, and Netcool are trademarks of International Business Machines Corporation in the United States, other countries or both. Other company, product and service names may be trademarks or service marks of others.

Nokia BSS Gateway Config Distribution Note

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nokia BSS Gateway Config Distribution Note

Uploaded by

Copyright:

Available Formats

Netcool Performance Manager for Wireless

Nokia BSS Gateway Configuration Distribution Note

1 About this Documentation

1.2 Required Skills and Knowledge

2.1 Referenced Documents

2.2 Other Related Documents

3.1 Vendor Gateway Version

Listed below are the bugs fixed in this release. Bug#

4.2 Release 3.4.0

Listed below are the bugs fixed in this release. Bug#

4.3 Release 3.3.0

5 Data type and releases supported

Supported Vendor Version S13, S12 S12 S11.5

5.1 Raw input files

Counter data is as below:

Equipment/devices to expect data

Nokia NetAct Performance Management System

Extraction mechanism Transfer mechanism

Nokia NetAct Performance Interface. Ftp

5.2 Hierarchy input files

Input file formats to expect

Equipment/devices to expect data Extraction mechanism Transfer mechanism

6.2 Parser Engine configuration

Measurement type correspondence in the performance raw files 1 2 3 4 5 6 7 9 10 11 12 13 14 15 27 29 50 51 52 53 54 55 56 57 58 59 60 61 62 63 65 66 67 68 69

Example: spool/input_d/NETWORK_1/REGION_1/A20070510.2300+02000000+0200_INode-GQ01 The NETWORK_ID is 1 and REGION_ID is 1

6.3 Post Parser user configuration

Appendix A Notices and Trademarks

You might also like