03 OS86073EN41GLN1 Admin of Perf Data Exercise

8/18/2019 03 OS86073EN41GLN1 Admin of Perf Data Exercise

http://slidepdf.com/reader/full/03-os86073en41gln1-admin-of-perf-data-exercise 1/27

OS86073EN41GLN1Issue 2.0

© Nokia Siemens Networks 1 (27)

OSS4.1

NetAct - Administration ofPerformance Data

Exercise SCN



NetAct - Administration of Performance Data

2 (27) © Nokia Siemens Networks OS86073EN41GLN1Issue 2.0

Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Siemens Networks trainingdocumentation, product documentation and slide presentation material, all of which are

forthwith known as Nokia Siemens Networks training material, are the exclusive property ofNokia Siemens Networks. Nokia Siemens Networks owns the rights to copying,modification, translation, adaptation or derivatives including any improvements ordevelopments. Nokia has the sole right to copy, distribute, amend, modify, develop, license,sublicense, sell, transfer and assign the Nokia Siemens Networks training material.Individuals can use the Nokia training material for their own personal self-development only,those same individuals cannot subsequently pass on that same Intellectual Property toothers without the prior written agreement of Nokia Siemens Networks. The Nokia SiemensNetworks training material cannot be used outside of an agreed Nokia Siemens Networkstraining session for development of groups without the prior written agreement of NokiaSiemens Networks.

Indemnity

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the

use of Nokia Siemens Networks´ customers only for the purposes of the agreement underwhich the document is submitted, and no part of it may be reproduced or transmitted in anyform or means without the prior written permission of Nokia Siemens Networks. Thedocument has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networkswelcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia Siemens Networks and thecustomer. However, Nokia Siemens Networks has made all reasonable efforts to ensurethat the instructions contained in the document are adequate and free of material errors andomissions. Nokia Siemens Networks will, if necessary, explain issues which may not becovered by the document.

Nokia Siemens Networks' liability for any errors in the document is limited to thedocumentary correction of errors. Nokia Siemens Networks WILL NOT BE RESPONSIBLEIN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES,INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arisefrom the use of this document or the information in it.

This document and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA Siemens Networks logo is a registered trademark of Nokia Siemens NetworksCorporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.






Contents

1 Administration of MGW Performance Data......................................... 4

1.1 Handling the MGW Element Manager (NEMU)....................................... 4 1.2 NE Measurement Explorer ...................................................................... 5 1.3 Creating an Object List ............................................................................ 6 1.4 Starting your measurement ..................................................................... 7 1.5 NE Threshold Management..................................................................... 8 1.6 KPI Management................................................................................... 10

1 Introduction to MSC Measurements .................................................. 13 1.1 User interface ........................................................................................ 17 1.2 Traffic measurements (Team 1-4) ......................................................... 18

2 Traffic Observation and GSM Measurement..................................... 24 2.1 Traffic observations (Team1)................................................................. 24 2.2 GSM measurements (Team2-4)............................................................ 26

3 Further Reading................................................................................... 30




4 (27) © Nokia Siemens Networks OS86073EN41GLN1

1 Administration of MGW PerformanceData

1.1 Handling the MGW Element Manager (NEMU)

Open an Appl ica t ion Launcher session to your MGW. Use IP

address, user name and password provided by the trainer or openit from TOP-level User Interface from the pop-up menu.

1. Which applications can be useful for measurementadministration in MGW?

Solution:

Regional Cluster Regional Cluster

RNCMGW

UNIX Server

Measurement

Files

Local NE

PM database

Nokia NetAct

PM Database

Local applicat ion

•NEMU (Network Element

Management Unit)

•MML (Man Machine Language)

NetAct Start page: Report er

Tools for Report ing

•Report Builder •Report Browser •KPI Browser •O ptional tools

Tools for PM Administ rati on

•Administ rati on of M easurements

Youarehere

Youarehere

Regional Cluster Regional Cluster

RNCMGW

UNIX Server

Measurement

Files

Local NE

PM database

Nokia NetAct

PM Database

Local applicat ion

•NEMU (Network Element

Management Unit)

•MML (Man Machine Language)

NetAct Start page: Report er

Tools for Report ing

•Report Builder •Report Browser •KPI Browser •O ptional tools

Tools for PM Administ rati on

•Administ rati on of M easurements

Youarehere

Youarehere



Contents



2. What is the purpose of NE Threshold Management ?

Solution:

3. What is the purpose of the NE Measurement Exp lorer ?

Solution:

4. How do you administrate platform statistic measurements?

Solution:

1.2 NE Measurement Explorer

The statistical data of basic performance counters is collected inthe network element to give the operator information about theperformance level of usage and malfunctions encountered in thenetwork element. This information is valuable when monitoring theoperation of the network element, in troubleshooting and when

planning the configuration and capacity needs of the networkelement (see e.g. NED Multimedia Gateway -> Reference ->Counters/Performance Indicators -> MGW Performance Countersdn0158188).

For the correct run of this exercise it is mandatory that youfocus only on the measurements of your team. Please useonly the following measurements:

Team Measurement Identification (MID)

Team 1 Interface specific TC measurement200

Team 2 ATM Layer PerformanceMeasurement: 210

Team 3 Unit Load Measurement 250

Team 4 Availability Performance Measurement260





Table 1 Platform statistic measurements to be used by the exercise teams

1.3 Creating an Object List

1. With which MML command group do you create an objectlist?

Solution

2. How long is the measurement identifier? Is this parameter

obligatory?Solution

3. The same measurement can have several object lists.Therefore, if you use a certain measurement, it will have aspecific object list identifier number (OID). Which numberscan you use for the OID?

Solution

4. Is the object list name (OLN) an obligatory parameter? Howlong can the OLN be?

Solution

5. Find now the appropriate object identifiers (IDx) for yourmeasurement (use the documentation for this task).

MID ID1 ID2 ID3 ID4

6. Define now for both of your measurements appropriateobject lists. Choose names and numbers according to yourteam name and team number.

Solution 1



Contents



Solution 2

1.4 Starting your measurement

1. Before you start your measurement you have to check if it isalready active. Which MML command do you use to performthis check?

Solution

2. Which possibilities are provided by the parameter ICH in theprevious command?

Solution

3. If your measurement is already active you have to stop itbefore you can start it again with your desired parameters.With which MML command do you stop an activemeasurement?

Solution

4. How do you have to choose the name for your measurementin the MML starting command ZT2S?

Solution

5. What are the default value and the maximum value for theResult Accumulation Period (RAP)?

Solution

6. Start now your first measurement with the lowest possibleRAP. The measurement shall start at the current time.Choose for all other parameters the default values.

Solution





7. How can you change the period of the day when reports areprinted out?

Solution

8. Does the measurement by default have a stop date?

Solution

1.5 NE Threshold Management

A new threshold for the counter ALL_TDM_CAS_UNSUCCESS shallbe created, if the value 100 is exceeded.

1. Start Application Launcher from OSS to open the MGWElement Manager and click on NE Threshold Management.

Solution

2. What is the first step to define a new threshold rule?

Solution

3. Select measurement type Connection Measurement fromthe combo box on the right side of the tab. What happens?

Solution

4. Type the name of the Rule in the text field and the descriptionfor the Rule in the text area

Solution

5. Select Log Action “Write Log and make alarm” from thecombo box. What are the other options?

Solution

6. Define Threshold Rule



Contents



• Type Threshold Rule in the Alarm rule text area

• You can use logical operators (AND, OR, NOT),comparison operators (>, >=, <, <=, =) and

parenthesis.

• Add counters and KPIs by clicking the Add

Counter or Add KPI button

• It is recommended to insert counter and KPI namesby using these buttons to avoid misspelling.

Solution

7. Click the Validate button to check the syntax of the Rule. Is

that step obligatory?Solution

8. Click the Save button or select Threshold -> Save toNetwork Element . What happens?

Solution

9. Go to tab Threshold Evaluat ion and create a New

Evaluat ion . Then apply your new rule to all Unit types under“your” MGW and choose a continuous schedule.

Solution

10. Check the active alarms with MGW Element Manager FaultManagement application. Which alarm is raised, if thethreshold is exceeded? Check, if this alarm appears. (Tip:With the View -dialog, you can filter alarms for a certain alarm

number.)Solution

11. Which a kind of information can be found in thesupplementary info field of this alarm?

Solution





12. Which conditions must be fulfilled for the alarm to appear?

Solution

1.6 KPI Management

A new KPI “Cell Ratio VP” shall be created, which represents theratio of the number of ingress cells received from virtual pathconnection and the number of egress cells transmitted to virtualpath connection.

If not already open, start Application Launcher from OSS to openThe MGW Element Manager and click on NE Threshold

Management .

Solution

1. How can you start to create a new KPI?

Solution

2. Select the measurement type from the combo box on theright side of the tab. What measurement type must beselected to find the appropriate counters?

Solution

3. Type the name of the KPI in the text field and the descriptionfor the KPI in the text area. Make sure, that you take anotherKPI name than the other groups.

Solution

4. Define KPI formula.

• Type KPI formula in the Formula of KPI text field

• Add counters and KPIs by clicking the Add

Counter or Add KPI button

Solution



Contents



5. Click the Validate button to check the syntax of the formula.

Solution

6. Click the Save button, Save button or select KPI -> Save KPI .

Solution

7. Check, if the new KPI has been created. Where can you findit?

Solution

8. Does the KPI also appear in NetAct Reporter tools?

Solution





1 Introduction to MSC Measurements

By analysing the traffic administration report the operator canmonitor the performances of the network, which can be dividedinto six groups:

1. Call traffic performance

2. Signalling traffic performance

3. Mobility performance

4. Security performance

5. Load and availability performance

6. Services performance.

To get the report for each performance, the operators have todefine and start different types of measurements, observationsor supervisions. There are many commands introduced for theNSS statistics function.

Traffic administration MML commands can be divided into thefollowing main groups:

Traffic Measurements

Traffic Observations

GSM MeasurementsTraffic Supervisions

Load Observations

Field Reporting

GSM Tracing

ReportsTraffic data

Figure 1. Traffic administration



Introduction to MSC Measurements







The creation of the traffic data depends on the type of thatmeasurement, observation or supervision.

Traffic measurements1. Define object list.

There are nine objects, which can be measured anddefined by different command groups:

− Circuit groups TG

− Destination-specific TD

− Control unit TN

− Traffic categories TR

− Cell TK

− Announcement channels TF

− Internal announcements TF

− Directivity (from incoming circuit groups) TG , TD

− Directivity (from incoming destination) TD

2. Create traffic measurement for the created object.

Command group TM

3. Start the created traffic measurement.

Command group TM

Start the Data service unit measurement T2

4. Stop the created traffic measurement.

Command group TM

Stop the Data service unit measurement T2

Traffic observation

1. Set the observation.

Command group TO

2. Remove the observation.

Command group TO






Traffic supervision

1. Activate the supervision.

− Disturbance TC

− Circuit seizure TE

− Circuit seizure times TT

2. Stop the supervision you just started.

Command group TC, TE,TT

GSM measurements

1. Create the measurement.− VLR TP

− HLR TP

− HO (handover) TP

− AUC (authentication) TP

− EIR TP

2. Start the measurement you created.

Command group TP

3. Stop the measurement.

Command group TP

Load observation

1. Set objects under observation.

These are the objects that the users can set for loadobservation:

− Circuit groups TL

− Control units TL

− Computer units TL

− Message bus TL

2. Start the load observation.

Command group TL

3. Stop the load observation.





Command group TL






Field reporting

1. Activate field reporting.

− Reporting on subscriber facilitiesTU

− Reporting on restarts TU

− Reporting on service level data TU

2. Print intermediate report.

Command groupTU

3. Stop field reporting.

Command groupTU

GSM tracing

1. Activate subscriber tracing.

− In the MSC/VLR MW

− In the HLR MT

2. Deactivate subscriber tracing.

−

In the MSC/VLR MW − In the HLR MT





1.1 User interface

Figure 2 presents the MML commands used to create, start orstop the measurements.

DX 200 MSC01 2000-12-13 14:53:32

TRAFFIC ADMINISTRATION

? ..... DISPLAY MENU

2 ..... MEASUREMENT HANDLING

B ..... SUPERVISION OF CIRCUIT GROUP AVAILABILITY

C ..... SUPERVISION OF DISTURBANCES

D ..... DESTINATION OBJECT LISTS

E ..... SUPERVISION OF CIRCUIT SEIZURE

F ..... ANNOUNCEMENT OBJECT LISTS

G ..... CIRCUIT GROUP OBJECT LISTS

K ..... CELL OBJECT LISTS

L ..... LOAD OBSERVATION

M ..... TRAFFIC MEASUREMENT

N ..... CONTROL UNIT OBJECT LISTS

O ..... TRAFFIC OBSERVATION

P ..... GSM MEASUREMENT HANDLING

R ..... TRAFFIC CATEGORY OBJECT LISTS

T ..... SUPERVISION OF CIRCUIT SEIZURE TIMES

U ..... FIELD REPORTING

W ..... FIELD REPORTING OF ROUTING COMPONENTS

Z; .... RETURN TO MAIN LEVEL

Figure 2. Traffic administration command groups






1.2 Traffic measurements (Team 1-4)

The normal sequence when starting a traffic measurement:

1. Define the measurement object to the appropriate objectlist.

2. Create the traffic measurement, including name, object listnumber etc.

3. Check connections of the logical files.

4. Start the traffic measurement.

For the correct run of this exercise it is mandatory that you

focus only on the measurements of your team. Please useonly the following measurements:

Team Measured object

Team 1 Circuit Group

Team 2 Cell

Team 3 Destination

Team 4 Control Unit

Exercise

1. Find out the purpose of your measurement in NED.

Solution:

2. Check, if your measurement is already running. How can

you do that?

Command:

• If your measurement is not yet active, perform the nextsteps in order to generate a new measurement.





3. Define the objects to the object list. Create an object list foryour measurement.

Command: Tip: If you just want to add specific cells (and not all) by

their LAC and CI, you can check the available pairs withZEDO;)

4. Create the traffic measurements using the object lists youcreated in the previous exercise (define the output delayswith a one minute interval).

Command:

5. Which logical output file does your measurement usetowards the NetAct interface? Hint: Use NED to find thisinformation.

Solution:

6. Check if the logical file is connected to the NetAct interface.If not, connect it.

Command:

7. Start the traffic measurements.

Command:

8. If possible, due to the testbed conditions, generate callsduring the measurement interval.

Solution:






9. Open the NetAct start page and start the KPI Browser.Which KPI folder contains the same counter as defined in

your measurement?

Solution:

10. Open the NetAct start page and start the KPI Browser .Which KPI folder contains the same counter as defined inyour measurement?

Solution:

11. Create a KPI report, by either selecting the whole KPIfolder or just some single KPIs. Choose a relative timeperiod of 2 weeks (default) and “your” MSC as networkelement.

Solution:

12. Can you see any measurement results in the graph ortable? If yes, interpret the report. If not, discuss the reasonswhy nothing is displayed.

Solution:





2 Traffic Observation and GSMMeasurement

For the correct run of this exercise it is mandatory that youfocus only on the measurements of your team. Please useonly the following measurements:

Team Measured object

Team 1 2.1 Traffic Observation

Team 2 2.2 GSM Measurement: VLR

Team 3 2.2 GSM Measurement: HLR

Team 4 2.2 GSM Measurement: AC

2.1 Traffic observations (Team1)

Set the following traffic observations ON:

• Circuit observation

• Failed calls.

1. What is the purpose of the traffic observation? Hint: UseNED M13.3 (or newer) Product Description to find theanswer).

Command:



Traffic Observation and GSM Measurement



2. Which logical file does your measurement use towards theNetAct interface?

Solution:

3. Check that the logical file is connected to the NetActinterface. If not, connect it.

Command:

4. Set circuit observations and observation of failed calls on(hint: select circuits of MGW. (Tip: Interrogate existingcircuits (to MGW) with the MML-command ZRCI).

Command:

5. If possible due to the testbed conditions, make a call to anymobile subscriber number.

Command:

6. If possible, make also a call to a non-existing PSTNnumber.

Command:

7. Open the NetAct start page and start the application GSMObservat ion Reports . How can you create a table, whichdisplays the results of your observation?

Solution:





8. Can you see any observation results in the table? If yes,interpret the report. If not, discuss the reasons why nothingis displayed.

Solution:

9. Reset circuit and failed call observation.

Command:

2.2 GSM measurements (Team2-4)

The normal sequence when starting a GSM measurement is:

• Create the GSM measurement including measurementtype, name, measurement time etc.

• Check the connections of the logical files.

• Start the GSM measurement.

Team GSM Measurement

Team 2 VLR

Team 3 HLR

Team 4 AC

1. What is the purpose of the traffic observation? Hint: UseNED M13.3 (or newer) Product Description to find theanswer).

Command:

2. Which logical file does your measurement use towards theNetAct interface?



Traffic Observation and GSM Measurement



Solution:

3. Check that the logical file is connected to the NetActinterface. If not, connect it.

Command:

4. Check, if your GSM measurement is active.

Command:

5. If your measurement is not yet created and active, modifythe GSM Measurement characteristics for VLR or HLRmeasurement in the MSC, resp. the AC measurement inHLR (giving the output interval every 15 minutes).

Command:

6. Activate your GSM Measurement in MSC or HLR.

Command: ZTPS:AUC,<name>;

7. If possible, due to the testbed conditions, generate callsand location updates during the measurement interval.

Command:

8. Open the NetAct start page and start the KPI Browser .Which KPI folder contains the same counter as defined inyour measurement?

Solution:





9. Create a KPI report, by either selecting the whole KPIfolder or just some single KPIs. Choose a relative timeperiod of 2 weeks (default) and “your” MSC as networkelement.

Solution:

10. Can you see any measurement results in the graph ortable? If yes, interpret the report. If not, discuss the reasonswhy nothing is displayed.

Solution:

11. Restore the original situation.

Stop the VLR, HLR and AC measurements. (Note: Youcannot remove the measurements.)

Command:



Further Reading

3 Further Reading NED NetAct:

• Administration of Measurements Help (DN00296155)

• Database Descriptions for MGW Measurements(DN00292856)

• Database Description for 2G/3G Mobile Circuit CoreMeasurements

• Reporter and Performance Management Principles(DN978605)

NED M13.0 Product Documentation:

•

NSS Statistics (DN97102002)

Documents

03 OS86073EN41GLN1 Admin of Perf Data Exercise