05 BSS Administration of Performance Data# Oss3

1 © NOKIA BSS Administration of Performance data / Oss3.1ED3 / Feb 2006 / Twc

BSS Administration of Performance DataBSS Administration of Performance DataProcess SlidesProcess Slides

OSS3.1ED3


• Know the BSS measurement data transfer to NetAct at an overview level• List the BSC call control measurements and the observations• Know the administrational and the operational states of measurements• Describe the Nokia recommendations of output intervals for

measurements• Assess the influence of running measurements to the load of NetAct• Demonstrate measurement administration on network element level

using MML commands• Explain the structure of the PM database, i.e. the relationship between

raw measurements tables and views and the corresponding naming conventions

• Demonstrate basic SQL commands to check the PM database tables and the object tables in the OSS database

• Outline the role and purpose of the Performance Reliability Reporting tool

Module ObjectivesModule Objectives


• BSS Performance Data flow

• Overview of BSS Measurements and Observations

• Managing BSS measurements and observations with MML

• Checking the PM database with AoM and KPI Browser

• Structure of PM database for BSS measurements

• Checking the PM Database with SQL

• Performance Data Reliability

BSS Administration of Performance Data BSS Administration of Performance Data ModulesModules


BSS Dataflow OverviewBSS Dataflow Overview

PM AdministrationApplication

PM AdministrationApplication PM Admin

PM MeasurementCollection & StoringPM Measurement

Collection & Storing PM Results

CMISE

CMISE/FTAM

BSC

MML Terminal


BSS Measurement TransferBSS Measurement Transfer

NetAct

BSCMeasurements

Ringbuffer

Flag :•Open•Full•Waiting•Compressed•Transferred

edmmanmx

mecmanmx

/var/tmp

wbpmanmx

DB

Q3

CMISE

FTAM

• The measurements are collected and stored in the measurement file. The status flag of the file in question in the ring buffer is Open.

• When the file is full the flag is changed to Full.

• If the BSS Measurement Data Transfer feature is on the Flag is changed to Waiting (to get compressed).

• When the measurement file is compressed the Flag is changed to Compressed.

• CMISE sends a request with the name of the measurement file to the edmmanmx process that the measurement file is ready to be transferred.

• wtfmanmx receives the request including the measurement file name

• FTAM starts transferring the data from the ring buffer in the NEand stores the data in /var/tmp.

• wtfmanmx sends a message to the ring buffer via CMISE that the measurement file has been transferred. The flag is changed to Transferred.

• wbpmanmx reads the measurement files from /var/tmp and decodes the information and stores it in the NMS/2000 database.


BSC Measurements OverviewBSC Measurements Overview

More than 2500 counters !


BSC ObservationsBSC Observations

• BSC observations can be used in obtaining exact information on events in call handling

• BSC observation generates real-time observation records on various occasions

• Records are stored on disk files, which are transferred to NetAct for postprocessing

• All observations can be running simultaneously in a BSC. However, each observation type can have only one object at a time.

• Observations are event-triggered and after every observed event a record is generated in the network element. So they can generate a considerable load.


BSC ObservationsBSC Observations• SDCCH Observation (SDDCH_OBS)

• TCH Observation (TCH_OBS)

• Incoming Handover Observation (INC_HO_OBS)

• Outgoing Handover Observation (OUT_HO_OBS)

• Internal Handover Observation (INT_HO_OBS)

• Radio Measurement Reports

• Clear Code Observation (CC_OBS)

• ISDN Abis Observation (ISDN-ABIS)

• Dropped Call Observation (DC_OBS)

• Position Based Services Observation (PB_OBS)

• TBF Observations for GPRS Trace


Example: TCH Observation RecordExample: TCH Observation Record


States of a Measurement in BSCStates of a Measurement in BSC

• ADMIN. STATE: LOCKED or UNLOCKED

In the LOCKED state the measurement has not been started and the measurement parameters can be modified. In the UNLOCKED state it has been started and it will be performed according to the parameters.

• OPER. STATE; DISABLED or ENABLED

In DISABLED state the measurement has been started but is not running, in ENABLED state it is running.


BSS Measurement Recommendations (Extract)BSS Measurement Recommendations (Extract)

• Complete Description:

Measurement Descriptions and Recommendations (DN0169162)


PM PM Data flow Data flow and and handling handling Regional ClusterRegional Cluster

BSCBSC

UNIX Server

MeasurementFiles

Local NE

PM database

Nokia NetAct

PM Database

Local application•MML (Man Machine Language)

NetAct Start page: Reporter

Tools for Reporting•Report Builder•Report Browser•KPI Browser•Optional tools

Tools for PM Administration •Administration of Measurements

Youarehere

Youarehere

Trainer GuideYou can continue with the whiteboard drawing from the last chapter by adding “MML” under “local application”. The picture is now complete and will be only used, from now on, to point out the location of the tools, which are just explained.“The local application for managing PM data for the BSC is MML (Man Machine Language). It can be used by connecting a local VDU (Visual Display Unit) to the BSC itself or by opening a remote MML-session from NetAct.MML is a programming language, which uses no graphical unit. You can only start, stop and modify measurements with MML or investigate the state of created measurements. You cannot see the collected measurement values or create any reports.”


BSC Measurement Handling with MML (ZT?)BSC Measurement Handling with MML (ZT?)


GSM Measurement Handling (ZTP?)GSM Measurement Handling (ZTP?)


BSC Measurement ModificationBSC Measurement Modification• Command

• Result


PM PM Data flow Data flow and and handling handling Regional Cluster

BSCBSC

UNIX Server

MeasurementFiles

Local NE

PM database

Nokia NetAct

PM Database





Youarehere

Youarehere

Trainer Guide“The local tool MML and the centralised tool Administration of Measurements are both used for starting, stopping and modifying measurements, so they have to be synchronised to each other, i.e. a measurement which has been started locally in the BSC for example with MML should also be visible in Administration of Measurements application. Normally, that happens automatically. You can alsocheck yourself, if the synchronisation works correctly and perform the synchronisation manually, in case you detect a data inconsistency between local and centralised PM database.”


Measurement plan created fromNetAct and activated in BSC, containing one or more measurements

Synchronisation Synchronisation of of local and local and centralised centralised

measurementsmeasurements

Single measurement started locallyfrom BSC with MML and uploadedto NetAct => LOCAL_xxx


Synchronisation Synchronisation of of local and local and centralised centralised

measurementsmeasurements

In this dialog, you can interrogate the status of measurements directly from the network element(s) selected for upload. The upload operation will interrogate the selected network elements one by one. For instructions, see Uploading active plans.Note:If all the defined measurements are not running in all the defined network elements, the corresponding plan created by the user will be made inactive in the general measurement administration. If the new measurement(s) that are not defined in any plan are found to be running in the defined network elements, a new plan will be created in the general measurement administration.The new plan will contain the new measurement(s) with the NE list containing only the current network element. The plan state will be set to Active. The original plans created by the user will not be modified. If measurements are found to be running with different schedule or parameter values than the defined values in the plan, a new plan will be created in the general measurement administration. The new plan will contain the modified measurement(s) with the NE list containing only the current network element.


Synchronisation Synchronisation of local and of local and centralised centralised measurementsmeasurements


Check specific BSC measurementCheck specific BSC measurementwith Administration of Measurementswith Administration of Measurements

Check if measurement is runningExample: Load measurement

To verify that measurements are stored in the NetAct databaseOpen Administration of Measurements selecting Utils→PerformanceManagement →Administration of Measurements. For moreinformation on how to use Administration of Measurements refer toAdministration of Measurements Help.


Regional Cluster

PM PM Data flow Data flow and and handling handling

BSCBSC

UNIX Server

MeasurementFiles

Local NE

PM database

Nokia NetAct

PM Database





Youarehere

Youarehere

Trainer Guide“When you have verified that the measurement you have started is really available in Administration of Measurements, you can check single counter values of that measurement in the KPI Browser”.


Check specific BSC measurementCheck specific BSC measurementwith KPI Browserwith KPI Browser

Check counter(s) from same measurement in KPI BrowserExample: load_rate

Select an active plan from the Active plans tab from either BSC, SGSN, RNC or GGSN. Click on the Plan details button and note active measurements from the Plan details window.Start the KPI Browser tool by selecting Start →Programs→ Nokia →Reporter → KPI Browser. For more information on how to use the KPI Browser, refer to the KPI Browser Help. You can open this Help from the KPI Browser Help menu.•Select the same measurement types you noted down.•Select the same network elements you noted down.•Create the report by clicking the query icon. A report will be created.•Verify that the measurements you noted down earlier are included in the report.


PM PM Data flow Data flow and and handling handling Regional Cluster

BSCBSC

UNIX Server

MeasurementFiles

Local NE

PM database

Nokia NetAct

PM Database





Youarehere

Youarehere

Trainer Guide“Instead of using graphical tools to investigate the contents of the NetAct PM database, you can also use a database language, i.e. SQL, to read certain information from the database tables directly. This is normally not needed, since the graphical tools offer a more convenient way to represent PM data, but it can be useful, if the graphical tools are not working or simply to understand the structure of the PM database a little better.”


Naming of database tablesNaming of database tables

• There are two different types of BSS measurement tables:

1. Raw Measurements tables, which are not transferred from the regional cluster to Global Reporter:

• P_<NETWORK ELEMENT>_<MEASUREM TYPE>, for example: P_NBSC_TRAFFIC

2. Summary measurements tables, which are used on the regional Cluster but which are also transferred to Global Reporter:

• P_HDBBSS_<NETWORK ELEMENT>_<MEASUREM TYPE>_<GR>, for example: P_HDBBSS_BTS_NBCCHLOF_<GR>• Where ‘HDB’ stands for “Historical Database”, e.g. tables used by NDW

• And <GR> stands for different time Granularities, i.e. WEEK, DAY, HOUR

• P_SUM_ _<NETWORK ELEMENT>_<MEASUREM TYPE>, for example, P_SUM_BSC_LOAD


Example: P_NBSC_TRAFFIC (Header)Example: P_NBSC_TRAFFIC (Header)


P_NBSC_TRAFFIC: Some Few Counters ...P_NBSC_TRAFFIC: Some Few Counters ...


Database viewsDatabase views

• User views are created on top of each measurement table.

• You should always use suitable views to access the database instead of accessing the tables directly.

• The view names and table names have different prefixes. Table names have the prefix P_ whereas view names have the prefix PS_ or PV_. PS_ views are used by the reporting applications and PV_ views are used by warehousing software to operate the data.


Checking PM database with SQLChecking PM database with SQL

tom:/m/home/omc (104) omc% sqlplus

SQL*Plus: Release 8.1.7.0.0 - Production on Mon Feb 14 20:01:19 2005

(c) Copyright 2000 Oracle Corporation. All rights reserved.

Enter user-name: rdrEnter password:

Connected to:Oracle8i Enterprise Edition Release 8.1.7.4.0 - 64bit ProductionJServer Release 8.1.7.4.0 - 64bit Production

SQL>

tom:/m/home/omc (104) omc% sqlplus

SQL*Plus: Release 8.1.7.0.0 - Production on Mon Feb 14 20:01:19 2005

(c) Copyright 2000 Oracle Corporation. All rights reserved.

Enter user-name: rdrEnter password:

Connected to:Oracle8i Enterprise Edition Release 8.1.7.4.0 - 64bit ProductionJServer Release 8.1.7.4.0 - 64bit Production

SQL>• Open an Xterm window and

start an SQL session with:

“sqlplus”

• Enter username and password, e.g. rdr/rdr

• Open an Xterm window and start an SQL session with:

“sqlplus”

• Enter username and password, e.g. rdr/rdr



SQL> select table_name from all_tables where table_name like 'P_NBSC_%';

TABLE_NAME------------------------------P_NBSC_ADJAC_CELL_MEAS_RESULTP_NBSC_AVAILP_NBSC_CCP_NBSC_CC_OBSP_NBSC_CC_PMP_NBSC_CHANNEL_FINDERP_NBSC_CI_RATIOP_NBSC_DC_OBSP_NBSC_DMRP_NBSC_DN2P_NBSC_DOWNLINK_MEAS_RESULTS

.

.

.

.

SQL> select table_name from all_tables where table_name like 'P_NBSC_%';

TABLE_NAME------------------------------P_NBSC_ADJAC_CELL_MEAS_RESULTP_NBSC_AVAILP_NBSC_CCP_NBSC_CC_OBSP_NBSC_CC_PMP_NBSC_CHANNEL_FINDERP_NBSC_CI_RATIOP_NBSC_DC_OBSP_NBSC_DMRP_NBSC_DN2P_NBSC_DOWNLINK_MEAS_RESULTS

.

.

.

.

•The BSC raw measurement tables start with P_NBSC.•To get a listing of all measurement tables, which start with this string, you can enter the command, shown in the picture on the left.



Enter:

Desc <Name_of_Database>

to see the description of the corresponding database table, i.e. the columns of the table

SQL> desc P_NBSC_LOAD;Name Null? Type

------------------------------- ---------------- -------------MEAS_TYPE NUMBERPERIOD_STOP NOT NULL VARCHAR2(16)PERIOD_DURATION NUMBER

INT_ID NOT NULL NUMBEROBJ_NAME NOT NULL VARCHAR2(8)OBJ_INDEX NOT NULL NUMBEROBJ_STATE NUMBER

PROC_PEAK_LOAD NUMBERLOAD_RATE NUMBERLOAD_DENOM1 NUMBERTIME_PROC_PEAK_LOAD VARCHAR2(16)

SUCC_SAMPLES NUMBERPERIOD_START_TIME NOT NULL DATEPERIOD_STOP_TIME DATEPERIOD_REAL_START_TIME DATEPERIOD_REAL_STOP_TIME DATE

BSC_GID NOT NULL NUMBER

SQL> desc P_NBSC_LOAD;Name Null? Type

------------------------------- ---------------- -------------MEAS_TYPE NUMBERPERIOD_STOP NOT NULL VARCHAR2(16)PERIOD_DURATION NUMBER

INT_ID NOT NULL NUMBEROBJ_NAME NOT NULL VARCHAR2(8)OBJ_INDEX NOT NULL NUMBEROBJ_STATE NUMBER

PROC_PEAK_LOAD NUMBERLOAD_RATE NUMBERLOAD_DENOM1 NUMBERTIME_PROC_PEAK_LOAD VARCHAR2(16)

SUCC_SAMPLES NUMBERPERIOD_START_TIME NOT NULL DATEPERIOD_STOP_TIME DATEPERIOD_REAL_START_TIME DATEPERIOD_REAL_STOP_TIME DATE

BSC_GID NOT NULL NUMBER



•Display the values of specific columns of the table, e.g. a counter name, by entering their names and separating them by comma, for example:

•Select <column_name_1>, <column_name_2>, <column_name_3> … etc. from <Name_of_Database>

SQL> select LOAD_RATE, PERIOD_REAL_START_TIME, OBJ_NAME from P_NBSC_LOAD

:LOAD_RATE PERIOD_REA OBJ_NAME------------ --------------- -------------

4 02.05.2005 MCMU0 02.05.2005 BCSU0 02.05.2005 BCSU

1193 02.05.2005 MB16 02.05.2005 OMU4 02.05.2005 MCMU4 02.05.2005 MCMU0 02.05.2005 BCSU0 02.05.2005 BCSU

1193 02.05.2005 MB:

516 rows selected.

SQL> select LOAD_RATE, PERIOD_REAL_START_TIME, OBJ_NAME from P_NBSC_LOAD

:LOAD_RATE PERIOD_REA OBJ_NAME------------ --------------- -------------

4 02.05.2005 MCMU0 02.05.2005 BCSU0 02.05.2005 BCSU

1193 02.05.2005 MB16 02.05.2005 OMU4 02.05.2005 MCMU4 02.05.2005 MCMU0 02.05.2005 BCSU0 02.05.2005 BCSU

1193 02.05.2005 MB:

516 rows selected.


BSS Managed Object Classes and IDsBSS Managed Object Classes and IDs

BSC

LAPD TRKT TCSM

FRBC

NSVC

BSTE

ADCE

BSTE

BAL

TREMAL

DMR

PCM

BTS

DN2

HOCPOCTRX

CHDMR

BCF

FUE

ACP

TRE

TID

FUETRE

DMR

TC

SB

RA

SM

SB

3

28

4

103

1 17

106

11

101

27 2925

24

15

124

124

124128

131 140 141

142

143

128

142143

232

232

232

471

465

464

115

5

SMLC

LCSE LMUARITT

REPE

DAP

716

717

719718720

721

ADJW

753

Object_class=3Object_class=3

General information of object class IDs in NED -> References -> Managed Object Reference

Glossary 1: ADCE, Adjacent Cell

3: BSC, Base Station Controller

4: BTS, Base Transceiver Station

5: CH, Radio channel

11: HOC, Handover Control

15: PCM, 2M Trunk

17: POC, Power Control

24: TRX, Transceiver

25: TC, Transcoder

27: BCF, Base Control Function

28: DN2, Dynamic Node

29: SM, Submultiplexer

101: LAPD, LAPD Link

103: BAL, BCCH Allocation List

106: MAL, Mobile Allocation List

115: TCSM, Transcoder/Submultiplexer

116: SMSC, Short Message Service Centre

128: BSTE, Base Station Transmission Equipment

131: TRKT, Trunk table

140: ACP, Autoconfiguration Pool

141: TID, Io Text

142: FUE, Functional Entity

143: SB, Supervision block

145: BTSM, BTS in MSC

146: BSCM, Base Station Controller in MSC

232: TRE, Transmission Equipment

716: DAP, Dynamic Abis Pool

717: SMLC, Standalone Serving Mobile Location Centre

718: RITT, Radio Interface Timing Transfer Table

719: LMUA, Location Measurement Unit Area

720: LCSE, Location Services Element

721: REPE, Repeater

753: ADJW, adjacency to WCDMA


BSS Managed Object Classes and IDsBSS Managed Object Classes and IDs

SQL> select oc_id,oc_abbreviation from utp_object_class order by oc_abbreviation;

OC_ID OC_ABBREVIATION---------- --------------------

1157 A2NE1158 A2ST

2 ACLO140 ACP730 ADAP

1 ADCE: :3 BSC

146 BSCM1305 BSCS128 BSTE

4 BTS: :

SQL> select oc_id,oc_abbreviation from utp_object_class order by oc_abbreviation;

OC_ID OC_ABBREVIATION---------- --------------------

1157 A2NE1158 A2ST

2 ACLO140 ACP730 ADAP

1 ADCE: :3 BSC

146 BSCM1305 BSCS128 BSTE

4 BTS: :

•To check the relationship between Object ID and Object Class with SQL, select oc_id and oc_abbreviation from the utp_object_class table.


Checking the database with SQLChecking the database with SQL

•Using the Object ID (e.g. 3 for BSC), you can output further details from the object table.

•Example: Output the names and IDs of all BSCs in the objects table

SQL> select name, int_id from objects where object_class=3;

NAME INT_ID----------------------------------BSC 0 120BSC-CSC6 306BSC-CSC5 313

SQL> select name, int_id from objects where object_class=3;

NAME INT_ID----------------------------------BSC 0 120BSC-CSC6 306BSC-CSC5 313

Tip! To see the structure of objects table, enter: desc objects



•You can also specify the SQL query for a certain managed object (here BSC) with a certain int_id, here 306 (BSC int_id).

SQL> select LOAD_RATE, PERIOD_REAL_START_TIME, OBJ_NAME from P_NBSC_LOAD where int_id = 306;

LOAD_RATE PERIOD_REA OBJ_NAME------------- -------------- ------------

20 03.05.2005 OMU20 03.05.2005 OMU20 03.05.2005 OMU20 03.05.2005 OMU19 03.05.2005 OMU17 03.05.2005 OMU20 03.05.2005 OMU20 03.05.2005 OMU19 03.05.2005 OMU30 03.05.2005 OMU

SQL> select LOAD_RATE, PERIOD_REAL_START_TIME, OBJ_NAME from P_NBSC_LOAD where int_id = 306;

LOAD_RATE PERIOD_REA OBJ_NAME------------- -------------- ------------

20 03.05.2005 OMU20 03.05.2005 OMU20 03.05.2005 OMU20 03.05.2005 OMU19 03.05.2005 OMU17 03.05.2005 OMU20 03.05.2005 OMU20 03.05.2005 OMU19 03.05.2005 OMU30 03.05.2005 OMU


Checking the database with SQLChecking the database with SQL

You can also copy and paste a KPI or report description from the Reporting tools to an SQL window e.g. to execute them or modify them.

selecttrunc(PS_HDBBSS_NBR_LOAD_RAW.period_start_time, 'DD') as "Day0",'load_rate' as fact, sum(PS_HDBBSS_NBR_LOAD_RAW.load_rate) as resultfromPS_HDBBSS_NBR_LOAD_RAW, object bsc_objectswherebsc_objects.object_class = 3 andPS_HDBBSS_NBR_LOAD_RAW.int_id = bsc_objects.int_id and

( PS_HDBBSS_NBR_LOAD_RAW.period_start_time >= (to_date('2005.05.12 23:59:59', 'YYYY.MM.DD HH24:MI:SS')-(2*7)) and PS_HDBBSS_NBR_LOAD_RAW.period_start_time < to_date('2005.05.12 23:59:59', 'YYYY.MM.DD HH24:MI:SS') )group bytrunc(PS_HDBBSS_NBR_LOAD_RAW.period_start_time, 'DD')

selecttrunc(PS_HDBBSS_NBR_LOAD_RAW.period_start_time, 'DD') as "Day0",'load_rate' as fact, sum(PS_HDBBSS_NBR_LOAD_RAW.load_rate) as resultfromPS_HDBBSS_NBR_LOAD_RAW, object bsc_objectswherebsc_objects.object_class = 3 andPS_HDBBSS_NBR_LOAD_RAW.int_id = bsc_objects.int_id and



Checking PM database with SQLChecking PM database with SQLselecttrunc(PS_HDBBSS_NBR_LOAD_RAW.period_start_time, 'DD') as "Day0", 'load_rate' as fact, sum(PS_HDBBSS_NBR_LOAD_RAW.load_rate) as resultfromPS_HDBBSS_NBR_LOAD_RAW, object bsc_objectswherebsc_objects.object_class = 3 andPS_HDBBSS_NBR_LOAD_RAW.int_id = bsc_objects.int_id and


selecttrunc(PS_HDBBSS_NBR_LOAD_RAW.period_start_time, 'DD') as "Day0", 'load_rate' as fact, sum(PS_HDBBSS_NBR_LOAD_RAW.load_rate) as resultfromPS_HDBBSS_NBR_LOAD_RAW, object bsc_objectswherebsc_objects.object_class = 3 andPS_HDBBSS_NBR_LOAD_RAW.int_id = bsc_objects.int_id and


05 BSS Administration of Performance Data# Oss3

Documents

Transcript of 05 BSS Administration of Performance Data# Oss3