01-09 Managing the Performance

7/25/2019 01-09 Managing the Performance

1/42

9Managing the PerformanceAbout This Chapter

This part describes the functions, steps, and commands of the performance management.

9.1 Overview of the Performance Measurement

This part describes the objects and concepts concerning the performance measurement.

9.2 Description of Measurement Sets and Measurement Units

This part describes the measurement sets and measurement units.

9.3 Operations of the LMT Performance Measurement

This part describes the operations of the local maintenance terminal (LMT) performance

measurement.

9.4 Operations of the Performance Browser Tool

This part describes how to operate the performance browser tool.

9.5 Analyzing Performance Measurement Data

This part describes how to analyze the performance measurement data.

9.6 Clearing Faults of Performance Measurement

This part describes how to clear the faults of performance measurement.

HUAWEI GGSN9811 Gateway GPRS Support Node

Operation Guide 9 Managing the Performance

Issue 03 (2008-04-10) Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd

9-1


2/42

9.1 Overview of the Performance MeasurementThis part describes the objects and concepts concerning the performance measurement.

9.1.1 Structure of the Performance Measurement System

This part describes the structure of the performance measurement system.

9.1.2 Principle of the M2000 Performance Measurement

This part describes the principle of the M2000 performance measurement, measurement task

implementation, and measurement results.

9.1.3 Concepts of the Performance Measurement

This part describes the concepts of the performance measurement.

9.1.4 Relations Among Measurement Items, Measurement Units, and Measurement Sets

This part describes the relations among measurement items, measurement units, and

measurement sets.

9.1.1 Structure of the Performance Measurement System

This part describes the structure of the performance measurement system.

System Structure

The performance management system of the GGSN9811 consists of:

l GGSN9811/back administration module (BAM)

l Local maintenance terminal (LMT)

l iManager M2000 mobile element management system (M2000)

Figure 9-1shows the structure of performance management system of the GGSN9811.

Figure 9-1Structure of the performance management system of the GGSN9811

Modem

M2000

Server

LAN

M2000

Client

PSTN

ModemGGSN/BAM

Remote LMT

Local LMT

9 Managing the Performance


Operation Guide

9-2 Huawei Proprietary and Confidential


Issue 03 (2008-04-10)


3/42

GGSN9811/BAM

The GGSN9811 is a functional entity in the general packet radio service (GPRS)/Universal

mobile telecommunications system (UMTS) network. The BAM is the module of the operation

and maintenance (O&M) system of the GGSN9811. The BAM reports the performance

measurement statistics of the GGSN9811 to the M2000.

LMT

The LMT is connected to the GGSN9811 through the intranet, Internet, or modem. You can

locally or remotely operate and maintain the GGSN9811 through the LMT.

M2000

The M2000 is connected to the GGSN9811 through the BAM. The M2000 is an integrated O&M

system developed for the UMTS by Huawei. The NEs including the GGSN9811 in the UMTS

can be managed through the M2000.

The M2000 provides the following performance management functions through the graphic user

interface (GUI):

l Performance measurement task management

l Performance measurement task status management

l Performance measurement task threshold management

9.1.2 Principle of the M2000 Performance Measurement

This part describes the principle of the M2000 performance measurement, measurement task

implementation, and measurement results.

Performance Measurement Description File

The measurement items that are supported by the GGSN9811 are fixed. They are defined in the

GGSN9811 performance measurement description file.

This file describes all measurement items and relevant configuration that are supported by the

current version of the GGSN9811.

Performance Measurement Task Implementation and Result Generation

In performance measurement, the M2000 collects measurement data from the GGSN9811 basedon the default measurement task.

The default measurement task is defined in the default measurement task file. This file describes

the data to be collected for measurement items in the default measurement task.

According to the default measurement task file and the defined periods of the default tasks

described in the file, the GGSN9811 collects the data of relevant items. Then, the GGSN9811

generates a result file in which the data of each period of all the measurement tasks is recorded.

Collection and Analysis of Performance Measurement Result

If an M2000 subscribes to the notice from the GGSN9811, the GGSN9811 sends the generationnotice of the result file to the M2000.





9-3


4/42

The M2000 then FTP obtains the notice. At the same time, the M2000 analyzes the result. If a

performance specification exceeds the threshold, the system generates a performance threshold

alarm.

Figure 9-2shows the performance measurement function of the GGSN9811/M2000.

Figure 9-2Performance measurement function

Activate a default performancemeasurement task

M2000

Threshold alarm/Resultsubscription

M2000

Report performancemeasurement result

GGSN9811

Query performancemeasurement result

M2000

Analyzing performancemeasurement result

M2000

Subscribe notice to

GGSN9811

M2000M200

0M2000

M2000

Obtain measurement

result by the FTP

Save performancemeasurement result

9.1.3 Concepts of the Performance Measurement

This part describes the concepts of the performance measurement.

The structure of performance measurement system of the GGSN9811 is of four nodes:

l Level 1: measurement object

l Level 2: measurement set

l Level 3: measurement unit

l Level 4: measurement item

Measurement Objects

A measurement object defines what is measured. The object is a physical or logic entity, or a

combination of entities.

Table 9-1lists the measurement objects of the GGSN9811. These are the level-1 nodes in the

structure of performance measurement system.

The attribute of the measurement object defines what to be measured. The measurement object

may be physical items such as boards, or logic items. The measurement objects and measurement

items are related.

A measurement object defines a type. The object may involve many instances. In a specific

measurement task, the attribute of the object is the specific instance. If the average CPU usage

of boards is measured, the object is the boards. The boards of the GGSN9811 are an instance ofthe measurement object. When the measurement task is created, the boards must be specified.



Operation Guide



Issue 03 (2008-04-10)


5/42

The default measurement objects are boards and subracks of the GGSN9811.

Table 9-1Possible measurement objects in the GGSN9811 system

M2000 Object ID BAM Object ID Object Name

134218178 0 CG IP

134218179 1 IMSI

134218180 2 APN

134218181 5 Board

134218182 6 GGSN function

134218183 3 HPLMN

134218184 4 SGSN IP

Measurement Sets

The measurement set is the category of the measurement units.

The measurement set is a level-2 node in the structure of the performance measurement system

of the GGSN9811.

There is a one-to-many relation between measurement sets and measurement units. A

measurement set contains multiple measurement units. A measurement unit can belong to only

one measurement set.

Measurement Units

The measurement unit is the category of the measurement items.

The measurement unit is a level-3 node in the structure of the performance measurement system

of the GGSN9811.

There is a one-to-many relation between measurement units and measurement items. A

measurement unit contains multiple measurement items. A measurement item can belong to only

one measurement unit.

Measurement Items

The basic unit of performance measurement is called measurement item, such as the average

number of activated PDP contexts, peak throughput of the Gn interface, average CPU usage,

and number of successfully-created call detail records (CDRs).

The measurement item is a level-4 node in the structure of the performance measurement system

of the GGSN9811.

Measurement Thresholds

When the value of a measurement item is higher or lower than the critical value, the systemgenerates alarms. The critical value here is the measurement threshold. You can set the threshold.





9-5


6/42

You can perform the following operations on the measurement threshold:

l Set the thresholds of a specified task.

You can set the upper limit value, lower limit value, or both for a measurement item of a

task.

l Query the thresholds of a specified task.

You can browse all configured thresholds based on a task ID.

l Delete the thresholds of a specified task.

You can delete the configured threshold of a certain measurement item based on a task ID.

Measurement Results

When a measurement period is over, the GGSN9811 generates a result file for each default task.

If the file generation succeeds, the GGSN9811 sends a notice indicating that the measurement

result file is ready to the M2000 that subscribes to the notice. If the generation of the file fails,

the GGSN9811 sends a notice indicating that the measurement result file fails to the M2000.

After receiving the notice indicating the measurement result file is ready, the M2000 sends an

order to upload measurement result file to the GGSN9811. The GGSN9811 FTP uploads the

file to the directory specified by the M2000.

When the upload of the result file is complete, the GGSN9811 sends a notice indicating that the

file transfer is over to the M2000. If the upload fails, the GGSN9811 sends a notice indicating

the file transfer fails to the M2000.

9.1.4 Relations Among Measurement Items, Measurement Units,and Measurement Sets

This part describes the relations among measurement items, measurement units, and

measurement sets.

The measurement item is the basic unit of the performance measurement. It specifies the

measurement object, that is, what to be measured. For example, the number of Packet Data

Protocol (PDP) context activation successes is a measurement item.

For the convenience of managing large quantity of measurement items in the system, the items

are classified into three levels:

l Level 1: measurement set, containing several measurement units related to certain functions

of the system

l Level 2: measurement unit, containing several measurement items related to certain

functions of the system

l Level 3: measurement item, existing in the tree structure system of "measurement object

class->measurement set->measurement unit->measurement item"

Table 9-2lists the relations among measurement sets, measurement units, and measurement

items.



Operation Guide



Issue 03 (2008-04-10)


7/42

Table 9-2Relations among measurement sets, measurement units, and measurement items

Measurement Set Measurement Unit Measurement Item

Basic session measurement

(specified APN)

GTPv1 session measurement

(specified APN)

Number of GTPv1 MS-

initiated activation requests

Number of GTPv1 MS-

initiated successful

activations


(specified APN)

Session status measurement

(specified APN)

A measurement set contains one or multiple measurement units. A measurement unit contains

one or multiple measurement items.

For details on measurement sets, measurement units, and measurement items of the

GGSN9811, see the appendix of this document.

9.2 Description of Measurement Sets and MeasurementUnits

This part describes the measurement sets and measurement units.

9.2.1 Overview

This part describes the concepts of the measurement set and measurement unit.

9.2.2 Session Measurement

This part describes the measurement set and the measurement unit of the session measurement.

9.2.3 Forwarding Performance Measurement

This part describes the measurement set and the measurement unit of the forwarding performance

measurement.

9.2.4 Charging Measurement

This part describes the measurement set and the measurement unit of the charging measurement.

9.2.5 AAA Performance Measurement

This part describes the measurement set and the measurement unit of the authentication,

authorization and accounting (AAA) performance measurement.

9.2.6 Intelligent Service Performance Measurement

This part describes the measurement set and the measurement unit of the intelligent service

performance measurement.

9.2.7 PPP Control Plane Performance Measurement

This part describes the measurement set and the measurement unit of the Point-to-Point Protocol

(PPP) control plane performance measurement.

9.2.8 L2TP Control Plane Performance Measurement





9-7


8/42

This part describes the measurement set and the measurement unit of the Layer 2 Tunneling

Protocol (L2TP) control plane performance measurement.

9.2.9 Forwarding Performance Measurement (Specified APN)


measurement (specified APN).

9.2.10 DHCP Performance Measurement

This part describes the measurement set and the measurement unit of the Dynamic Host

Configuration Protocol (DHCP) performance measurement.

9.2.11 System Resource Measurement

This part describes the measurement set and the measurement unit of the system resource

measurement.

9.2.12 MIP FA Performance Measurement

This part describes the measurement set and the measurement unit of the Mobile Internet

Protocol (MIP) foreign agent (FA) performance measurement.

9.2.13 Signaling Message Error Cause Measurement

This part describes the measurement set and measurement unit of the signaling message error

cause measurement.

9.2.14 Traffic-Class-Based Basic Session Measurement

This part describes the measurement set and the measurement unit of the traffic-class-based

basic session measurement.

9.2.15 Traffic-Class-Based Forwarding Performance Measurement


forwarding performance measurement.

9.2.16 User Number MeasurementThis part describes the measurement set and the measurement unit of the user number

measurement.

9.2.17 Traffic-Class-Based APN Session Performance Measurement


access point name (APN) session performance measurement.

9.2.18 IMS Basic Session Service Measurement

This part describes the measurement set and the measurement unit of the IP multimedia

subsystem (IMS) basic session service measurement.

9.2.19 IMS Session Performance Measurement

This part describes the measurement set and the measurement unit of the IP multimediasubsystem (IMS) session performance measurement.

9.2.20 Layer 7 Parse Performance Measurement

This part describes the measurement set and the measurement unit of the layer 7 parse


9.2.21 Gy Interface Performance Measurement

This part describes the measurement set and the measurement unit of the Gy interface


9.2.22 Prepaid Service Measurement

This part describes the measurement set and the measurement unit of the prepaid service

measurement.



Operation Guide



Issue 03 (2008-04-10)


9/42

9.2.23 DiffServ PDP Context Measurement

This part describes the measurement set and the measurement unit of the differentiated service

(DiffServ) Packet Data Protocol (PDP) context measurement.

9.2.1 OverviewThis part describes the concepts of the measurement set and measurement unit.

Table 9-3lists 29 measurement sets and 31 measurement units of the GGSN9811.

Table 9-3Measurement sets and measurement units

Measurement Set Measurement Unit

Basic session measurement Basic session measurement

Forwarding performance measurement Forwarding performance measurement

G-CDR measurement G-CDR measurement

Ga interface performance measurement Ga interface performance measurement

AAA performance measurement AAA performance measurement

System resources measurement System resources performance measurement

Ga interface performance measurement

(specified CG)

Ga interface performance measurement

(specified CG)

Basic session measurement (specified APN) GTPv1 session measurement (specified

APN)

GTPv0 session measurement (specified

APN)

Session status measurement (specified APN)

User CDR measurement G-CDR measurement (specified IMSI)

AAA performance measurement (specified

APN)

AAA performance measurement (specified

APN)

PPP control plane performance measurement PPP control plane performance measurement

L2TP control plane performancemeasurement

L2TP control plane performancemeasurement

Intelligent service performance measurement Intelligent service performance measurement

DHCP performance measurement DHCP performance measurement

Forwarding performance measurement

(specified APN)

Forwarding performance measurement

(specified APN)

MIP FA performance measurement MIP FA performance measurement

Basic session measurement (specified

HPLMN)

Basic session measurement (specified

HPLMN)





9-9


10/42

Measurement Set Measurement Unit

Basic session measurement (specified SGSN) Basic session measurement (specified SGSN)

Signaling message error cause measurement Signaling message error cause measurement

Traffic-class-based basic session

measurement

Traffic-class-based basic session

measurement

Traffic-class-based forwarding performance

measurement

Traffic-class-based forwarding performance

measurement

User number measurement User number measurement

Traffic-class-based APN session

measurement

Traffic-class-based APN status measurement

Layer 7 resolution performance measurement Layer 7 resolution performance measurement

Gy interface performance measurement set Gy interface performance measurement

Prepaid service measurement set Prepaid service measurement

IMS session performance measurement IMS session performance measurement

IMS basic session service measurement IMS basic session service measurement

DiffServ PDP context counting and querying DiffServ PDP context measurement

NOTE

l The following sections are categorized in terms of functions. Thus, one section may contain different

measurement sets. The measurement sets are divided in terms of functions and objects.

l Different software versions may provide different measurement sets and measurement units.

9.2.2 Session Measurement

This part describes the measurement set and the measurement unit of the session measurement.

The basic session measurement collects the data relating to the session process in the GGSN.

The measured session process includes:

l Session activation

l Session deactivation

l Session modification

The main measurement items of the basic session include:

l Number of requests

l Number of successes

l Number of failures for various reasons

l Number of users

Table 9-4lists the measurement units relating to the session management.



Operation Guide



Issue 03 (2008-04-10)


11/42

Table 9-4Measurement units relating to the session management

Measurement Set Measurement Unit Description

Basic session measurement Basic session measurement Success rate of PDP context

activations, number of PDPcontext activation and

deactivation successes


(specified APN)


(specified APN)

Providing session

performance measurement

relating to a specified 3G

APN


(specified APN)

Providing session


relating to a specified 2G

APN

Session status measurement

(specified APN)

Providing status

measurement relating to a

specified APN


(specified HPLMN)


(specified HPLMN)

Providing session


specified HPLMN


(specified GGSN)


(specified GGSN)

Providing session


specified GGSN

9.2.3 Forwarding Performance Measurement


measurement.

The measurement relating to the forwarding performance management process includes

following information:

l Number of uplink packets on the Gn interface

l Number of downlink packets on the Gn interface

l Number of uplink packets on the Gi interface

l Number of downlink packets on the Gi interface

l GGSN average packet throughput

l Peak packet throughput

l Forwarding success rate

Table 9-5lists the measurement unit relating to the forwarding performance management.





9-11


12/42

Table 9-5Measurement unit relating to the forwarding performance management


Forwarding performance

measurement


measurement

Number of forwarding

packets, throughput,forwarding success rate of

the Gn and Gi interfaces

9.2.4 Charging Measurement

This part describes the measurement set and the measurement unit of the charging measurement.

The measurement relating to charging function provides the number of successful and failed G-

CDRs generated for all users or specified users.

Table 9-6lists the measurement units relating to the charging function.

Table 9-6Measurement units relating to the charging function


G-CDR measurement G-CDR measurement Counting the number of G-

CDRs generated for all users

of the system, including

successful and failed

generation of G-CDRs

Ga interface performancemeasurement

Ga interface performancemeasurement

Counting the following:

l Number of connection

interruptions between the

GGSN and the CG

l CG redirections

l Bytes and number of G-

CDRs sent to the CG from

the GGSN

Ga interface performance

measurement (specified CG)

Ga interface performance

measurement (specified CG)

Based on different IP

addresses of the CGs,

counting:

l Number of connection

interruptions between the

GGSN and the CG

l CG redirections

l Bytes and number of G-

CDRs sent to the CG from

the GGSN



Operation Guide



Issue 03 (2008-04-10)


13/42


User CDR measurement G-CDR measurement

(specified IMSI)

Counting the number of G-

CDRs generated for all users

of the system, including

successful and failed

generation of G-CDRs

9.2.5 AAA Performance Measurement

This part describes the measurement set and the measurement unit of the authentication,

authorization and accounting (AAA) performance measurement.

Table 9-7lists the measurement units relating to the AAA performance measurement.

Table 9-7Measurement units relating to the AAA performance measurement


AAA performance

measurement

AAA performance

measurement

Counting the following

information of the system:

l Number of authentication

request successes

l Number of charging

request successes

l Number of authenticationrequest attempts


request attempts

AAA performance

measurement (specified

APN)

AAA performance


APN)


information of a specified

APN:


request successes


request successes


request attempts


request attempts

9.2.6 Intelligent Service Performance Measurement

This part describes the measurement set and the measurement unit of the intelligent serviceperformance measurement.





9-13


14/42

Table 9-8lists the measurement unit relating to the intelligent service performance

measurement.

Table 9-8Measurement unit relating to the intelligent service performance measurement


Intelligent service


Intelligent service


Measuring the data relating

to intelligent sessions such

as:

l Number of intelligent PDP

context activation requests

l Number of intelligent PDP

context activation

successes

9.2.7 PPP Control Plane Performance Measurement

This part describes the measurement set and the measurement unit of the Point-to-Point Protocol

(PPP) control plane performance measurement.

The PPP control plane performance measurement includes:

l Total PPP negotiation packets

l LCP negotiation successes

l

LCP negotiation attemptsl IPCP negotiation successes

l IPCP negotiation attempts

Table 9-9lists the measurement unit relating to the PPP control plane performance.

Table 9-9Measurement unit relating to the PPP control plane performance


PPP control plane


PPP control plane



l Total PPP negotiation

packets

l LCP negotiation successes

l LCP negotiation attempts

l IPCP negotiation

successes

l IPCP negotiation attempts



Operation Guide



Issue 03 (2008-04-10)


15/42

9.2.8 L2TP Control Plane Performance Measurement

This part describes the measurement set and the measurement unit of the Layer 2 Tunneling

Protocol (L2TP) control plane performance measurement.

Table 9-10lists the measurement unit relating to the L2TP control plane performance

measurement.

Table 9-10Measurement unit relating to the L2TP control plane performance measurement


L2TP control plane


L2TP control plane



l Total L2TP control

packets

l Number of established

L2TP tunnels

l Number of established

L2TP sessions

9.2.9 Forwarding Performance Measurement (Specified APN)


measurement (specified APN).

Table 9-11lists the measurement unit relating to the forwarding performance measurement(specified APN).

Table 9-11Measurement unit relating to the forwarding performance measurement (specified

APN)




APN)



APN)


information of the specified

APN:

l Number of uplink and

downlink packets of theGn interface


downlink packets of the Gi

interface

l APN average packet

throughput

l APN forwarding success

rate





9-15


16/42

9.2.10 DHCP Performance Measurement

This part describes the measurement set and the measurement unit of the Dynamic Host

Configuration Protocol (DHCP) performance measurement.

Table 9-12lists the measurement unit relating to the DHCP performance measurement.

Table 9-12Measurement unit relating to the DHCP performance measurement


DHCP performance

measurement

DHCP performance

measurement


l Number of received

DHCP address allocation

requests

l Number of DHCP address

allocation successesl Number of DHCP address

allocation failures

9.2.11 System Resource Measurement

This part describes the measurement set and the measurement unit of the system resource

measurement.

Table 9-13lists the measurement unit relating to system operation status.

Table 9-13Measurement unit relating to system operation status


System resource

measurement

System resource

measurement

Providing the usage of the

system resources including

the CPU and memory

9.2.12 MIP FA Performance MeasurementThis part describes the measurement set and the measurement unit of the Mobile Internet

Protocol (MIP) foreign agent (FA) performance measurement.

Table 9-14lists the measurement unit relating to the MIP FA performance measurement.



Operation Guide



Issue 03 (2008-04-10)


17/42

Table 9-14Measurement unit relating to the MIP FA performance measurement


MIP FA performance

measurement

MIP FA performance

measurement

Providing the statistics such

as the total number of validregistration requests

recorded by FA and that of

received valid registration

responses

9.2.13 Signaling Message Error Cause Measurement

This part describes the measurement set and measurement unit of the signaling message error

cause measurement.

Table 9-15lists the measurement unit relating to the signaling message error cause

measurement.

Table 9-15Measurement unit relating to the signaling message error cause measurement


Signaling message error

cause measurement

Signaling message error

cause measurement

Providing the number of

signaling message errors

based on the causes

(collecting the statistics ofthe signaling of the Gn

interface)

9.2.14 Traffic-Class-Based Basic Session Measurement


basic session measurement.

Table 9-16lists the measurement unit relating to the traffic-class-based basic session

measurement.

Table 9-16Measurement unit relating to the traffic-class-based basic session measurement


Traffic-class-based basic

session measurement

Traffic-class-based basic

session measurement

Measuring basic sessions and

collecting statistics based on

the traffic class and user

priority level





9-17


18/42

9.2.15 Traffic-Class-Based Forwarding Performance Measurement


forwarding performance measurement.

Table 9-17lists the measurement unit relating to the traffic-class-based forwarding performancemeasurement.

Table 9-17Measurement unit relating to the traffic-class-based forwarding performance

measurement


Traffic-class-based

forwarding performance

measurement

Traffic-class-based

forwarding performance

measurement

Measuring the forwarding

performance of the Gn and Gi

interfaces and collecting the

statistics based on the traffic

class and user priority level

9.2.16 User Number Measurement

This part describes the measurement set and the measurement unit of the user number

measurement.

Table 9-18lists the measurement unit relating to the user number measurement.

Table 9-18Measurement unit relating to the user number measurement


User number measurement User number measurement Counting the current user

number and the maximum

user number

9.2.17 Traffic-Class-Based APN Session Performance Measurement

This part describes the measurement set and the measurement unit of the traffic-class-basedaccess point name (APN) session performance measurement.

Table 9-19lists the measurement unit relating to the traffic-class-based APN session




Operation Guide



Issue 03 (2008-04-10)


19/42

Table 9-19Measurement unit relating to the traffic-class-based APN session performance

measurement


Traffic-class-based APNsession performance

measurement

Traffic-class-based APNsession performance

measurement

Measuring the APN-basedbasic session performance

based on the traffic class and

user priority level

9.2.18 IMS Basic Session Service Measurement


subsystem (IMS) basic session service measurement.

Table 9-20lists the measurement unit relating to the IMS basic session service measurement.

Table 9-20Measurement unit relating to the IMS basic session service measurement


IMS basic session service

measurement

IMS basic session service

measurement

Counting the times for which

the GGSN sends the REQs,

authorization requests,

RPTs, DRQs, and SSCs to

the PDF and the times for

which the GGSN receives the

DECs and SSQs from the

PDF

9.2.19 IMS Session Performance Measurement


subsystem (IMS) session performance measurement.

Table 9-21lists the measurement unit relating to the IMS session performance measurement.

Table 9-21Measurement unit relating to the IMS session performance measurement


IMS session performance

measurement

IMS session performance

measurement

Measuring context activation

and deactivation of the APN-

based IMS media stream,

APN-based SGSN-initiated

media stream, and APN-

based PDF-initiated media

stream





9-19


20/42

9.2.20 Layer 7 Parse Performance Measurement

This part describes the measurement set and the measurement unit of the layer 7 parse


Table 9-22lists the measurement unit relating to the layer 7 parse performance measurement.

Table 9-22Measurement unit relating to the layer 7 parse performance measurement


Layer 7 resolution


Layer 7 resolution


Collecting statistics of the

performance specifications

of the content-based charging

layer 7 parse such as:


downlink packets

l Packet throughput

l Forwarding success rate

l Number and bytes of

HTTP/WAP/RTSP/FTP

uplink and downlink

packets

9.2.21 Gy Interface Performance MeasurementThis part describes the measurement set and the measurement unit of the Gy interface


Table 9-23lists the measurement unit relating to the Gy interface performance measurement.

Table 9-23Measurement unit relating to the Gy interface performance measurement


Gy interface performance

measurement

Gy interface performance

measurement

Collecting the statistics of the

throughput, number andbytes of uplink and downlink

packets of the Gy interface

9.2.22 Prepaid Service Measurement

This part describes the measurement set and the measurement unit of the prepaid service

measurement.

Table 9-24lists the measurement unit relating to the prepaid service measurement.



Operation Guide



Issue 03 (2008-04-10)


21/42

Table 9-24Measurement unit relating to the prepaid service measurement


Prepaid service measurement Prepaid service measurement Measuring the performance

specifications relating to theDiameter prepaid service

9.2.23 DiffServ PDPContext Measurement

This part describes the measurement set and the measurement unit of the differentiated service

(DiffServ) Packet Data Protocol (PDP) context measurement.

Table 9-25lists the measurement unit relating to the DiffServ PDP context measurement.

Table 9-25Measurement unit relating to the DiffServ PDP context measurement


DiffServ PDP context

measurement

DiffServ PDP context

measurement

Counting and querying the

real-time number of the

DiffServ PDP contexts

9.3 Operations ofthe LMT Performance Measurement

This part describes the operations of the local maintenance terminal (LMT) performance

measurement.

9.3.1 Managing Measurement Objects

This part describes how to manage the measurement objects.

9.3.2 Managing Measurement Task Files

This part describes how to manage the measurement task files.

9.3.3 Managing Measurement Result Files

This part describes how to manage the measurement result files.

9.3.4 Uploading Measurement Description Files

This part describes how to upload the measurement description files.

9.3.1 Managing Measurement Objects

This part describes how to manage the measurement objects.

9.3.1.1 Adding Measurement Objects

This part describes how to adding measurement objects.

9.3.1.2 Removing Measurement Objects

This part describes how to removing measurement objects.

9.3.1.3 Querying Measurement ObjectsThis part describes how to querying measurement objects.





9-21


22/42

Adding Measurement Objects

This part describes how to adding measurement objects.

ContextADD MEASOBJis used to add a measurement object. The measurement object is a certain

physical or logic resource entity in performance management. The objects added on other

management terminals such as the local maintenance terminal (LMT) or network elements (NEs)

are not displayed on the interface of the M2000. The objects added on the M2000 are suitable

only for the measurement objects of which the period is longer than 30 minutes.

If you add an existing object, a success message is returned.

Procedure

l Add a measurement object.

Add a measurement object. The object class is APN. The object instance is isp.com.

ADD MEASOBJ: MOC=APN, MOI="ISP.com";ADD MEASOBJ: MOC=IMSI,

MOI="460010";

l Add multiple measurement objects.

Add two measurement objects. The object class is APN. The object instances are isp1.com

and isp2.com.

ADD MEASOBJ: MOC=APN, MOI="isp1.com&isp2.com";

----End

Removing Measurement Objects

This part describes how to removing measurement objects.

Context

RMV MEASOBJis used to remove a measurement object. The objects measured by the M2000

must be removed from the interface of the M2000.

l If the value of the object class is not specified, all measured object class instances that can

be configured are removed.

l If the value of the object instance is not specified, all objects of this class are removed.

l If an object that does not exist is removed, a success message is returned.

Example

l Remove a measurement object.

Remove a measurement object. The object class is APN. The object instance is ISP.com.

RMV MEASOBJ: MOC = "APN", MOI = "ISP.com";


The object class is HPLMN. The object instance is 460123. The mobile country code is460. The mobile network code is 123.



Operation Guide



Issue 03 (2008-04-10)


23/42

RMV MEASOBJ: MOC=HPLMN, MOI="460123";


The object class is SGSN_IP. The object instance is 192.168.1.1.

RMV MEASOBJ: MOC= SGSN_IP, MOI="192.168.1.1";

Querying Measurement Objects

This part describes how to querying measurement objects.

Context

LST MEASOBJis used to query a measurement object.

In an object class, the object instances thatare collecting data is listed.

Example

Query a measurement object. The object class is APN.

LST MEASOBJ: MOC=APN;

The results are as follows:

+++ GGSN HUAWEI 2006-08-31 16:14:23 O&M #357 %%LST MEASOBJ: MOC=APN;%

% RETCODE = 0 Execution succeeded

Measurement Object List ----------------------- MOC MOI

APN huawei (Number of results = 1)

--- END

9.3.2 Managing Measurement Task Files

This part describes how to manage the measurement task files.

9.3.2.1 Verifying Task Files

This part describes how to verifying task files.

9.3.2.2 Activating Standby Task Files

This part describes how to activating standby task files.

9.3.2.3 Downloading Task Files

This part describes how to downloading task files.

9.3.2.4 Uploading Task Files

This part describes how to uploading task files.

9.3.2.5 Querying Task Files

This part describes how to querying task files.

Verifying Task Files

This part describes how to verifying task files.





9-23


24/42

Context

VRF DEFMEASis used to check whether the items and objects in the measurement task file

are valid and whether the active task file and the standby task file are consistent.

The file status in the measurement result is as follows:

l OK

The file is normal.

l CORRUPT

The file is abnormal.

l NONEXIST

The file does not exist.

The active task file is the file that is activated. When the standby task file is activated, it becomes

the active task file.

Example

Verify the task file.

VRF DEFMEAS:; +++ GGSN HUAWEI 2006-08-24 01:02:40 O&M #19 %%VRF

DEFMEAS:;%% RETCODE = 0 Execution succeeded

Default Measurement Files Status -------------------------------- FileName Status

DefaultMeas_Active.xml OKDefaultMeas_Standby.xml OK The standby file

is identical to active file? TRUE (Number of results = 3)

---END

Activating Standby Task Files

This part describes how to activating standby task files.

Context

ACT SDEFMEASis used to activate the standby task file.

The validity of the task file is checked when the standby task file is activated.

The standby task file becomes the active task file after activation. The original active task file

becomes the standby task file.

When the activation succeeds, the new task file takes effect immediately. The result file of the

current period is generated based on the new task file.

Example

Activate the standby task file.

ACT SDEFMEAS:;

Downloading Task Files

This part describes how to downloading task files.



Operation Guide



Issue 03 (2008-04-10)


25/42

Context

DLD DEFMEASis used to download the task file from the File Transfer Protocol (FTP) server

to the GGSN.

The active task file and standby task file are saved on the GGSN. The active task file is usedcurrently. The downloaded task file replaces the standby task file.

After the task file is downloaded to the master main control board, the file on the slave main

control board is synchronized automatically.

The downloaded task file replaces the standby task file.

Example

Download the task file.

l The source task file name is GGSN.

l The IP address of the FTP server is 10.10.10.10.

l The user name of the FTP server is Name.

l The password of the FTP server is password.

DLD DEFMEAS: SRCF = "/M2000/GGSN_DefaultMeas_Active.xml", IP =

"10.10.10.10", USR = "Name", PWD = "password";

Postrequisite

Uploading Task Files

This part describes how to uploading task files.

Context

ULD DEFMEASis used to upload the task file from the GGSN to the File Transfer Protocol

(FTP) server.

Before you run this command, you must check whether there is a file with the same name as the

file to be uploaded to the FTP server.

Example

Upload the task file.

l The task file type is ACTIVE.

l The destination task file name is GGSN.




ULD DEFMEAS: FT=ACTIVE,DSTF="GGSN_DefaultMeas_Active.xml",IP="10.10.10.10", USR="Name", PWD="*****";





9-25


26/42

Querying Task Files

This part describes how to querying task files.

ContextLST DEFMEASis used to check whether the active and standby task files exist on the

GGSN and to query the time when the files are created.

Example

Query the task file.

LST DEFMEAS: ; +++ GGSN HUAWEI 2006-08-24 23:59:59 O&M #1000 %% LSTDEFMEAS: ";%% RETCODE = 0 Execution succeeded

Default Measurement Files List ------------------------------ File

Name Generated Time

DefaultMeas_Active.xml 20060526.2230

DefaultMeas_Standby.xml 20060526.2230 (Numberof results = 2)

----END

9.3.3 Managing Measurement Result Files

This part describes how to manage the measurement result files.

9.3.3.1 Uploading Measurement Result Files

This part describes how to uploading measurement result files.

9.3.3.2 Removing Measurement Result Files

This part describes how to removing measurement result files.

9.3.3.3 Querying Measurement Result Files

This part describes how to querying measurement result files.

Uploading Measurement Result Files

This part describes how to uploading measurement result files.

Context

LST MEASRSTis used to upload the measurement result file.

When a measurement period is over, the GGSN generates a measurement result file for each

default measurement task.

You can query the generated result file with LST MEASRST.

Example

Upload the measurement result file.

l The file name is A20050526.2200+0800-2230+0800_EMS-NORMAL.mrf.

l The target directory is /M2000/measurement_results/.



Operation Guide



Issue 03 (2008-04-10)


27/42




ULD MEASRST: FN = "A20030526.2200+0800-2230+0800_EMS-NORMAL.mrf", DSTF = "/M2000/measurement_results/", IP =

"10.10.10.10", USR = "Name", PWD = "*****";

NOTE

The name of the A20050526.2200+0800-2230+0800_EMS-NORMAL.mrffile means that the

measurement time segment is from 22:00 to 22:30, May 26, 2005, East eight time zone and the measurement

period is the normal period.

Removing Measurement Result Files

This part describes how to removing measurement result files.

Context

RMV MEASRSTis used to remove the specified or all measurement result files from the

GGSN.

l You can query the generated result file with LST MEASRST.

l If the file name is not specified, all result files are removed.

Example

Remove a measurement result file. The file name is A20050526.2200+0800-2230+0800_EMS-

NORMAL.mrf.

RMV MEASRST: FN = "A20050526.2200+0800-2230+0800_EMS-

NORMAL.mrf";

Remove all the measurement result files.

RMV MEASRST:;

Querying Measurement Result Files

This part describes how to querying measurement result files.

Context

LST MEASRSTis used to query the measurement result file.

The information of the measurement result file includes the time when the measurement result

is generated.

Example

Query the measurement result file.

LST MEASRST:; +++ GGSN HUAWEI 2006-08-24 19:18:12 O&M #1000 %% LST

MEASRST: ;%% RETCODE = 0 Execution succeeded

Measurement Result(s) List -------------------------- File





9-27


28/42

Name Generated Time

A20060824.1030+0800-1100+0800_EMS-NORMAL.mrf 20060824.1106A20060824.1130+0800-1200+0800_EMS-NORMAL.mrf 20060824.1206 (Number

of results = 2)

--- END

9.3.4 Uploading Measurement Description Files

This part describes how to upload the measurement description files.

The measurement description file is stored in hd:/bam/ini/GGSN/measdefinitions.xml.

Upload the measurement description file. The target file name is GGSN. The IP address of the

File Transfer Protocol (FTP) server is 10.10.10.10. The user name of the FTP server is Name.

The password of the FTP server is password.

ULD MEASDEF: DSTF = "GGSN_MeasDefinitions.xml", IP ="10.10.10.10", USR = "Name", PWD = "*****";

9.4 Operations of the Performance Browser Tool

This part describes how to operate the performance browser tool.

9.4.1 Overview

This part describes the functions and the usage of the performance browser tool.

9.4.2 Configuring Network Elements

This part describes how to configure the network elements (NEs).

9.4.3 Downloading Measurement Results

This part describes how to download the measurement results.

9.4.4 Querying Measurement Results

This part describes how to query the measurement results.

9.4.5 Browsing Measurement Description Files

This part describes how to browse the measurement description files.

9.4.6 Managing Templates

This part describes the objects and the steps of the template management.

9.4.1 OverviewThis part describes the functions and the usage of the performance browser tool.

With the performance browser tool, you can browse the performance measurement results that

are saved in the network element (NE).

The performance browser tool provides the File Transfer Protocol (FTP) download function.

The local maintenance terminal (LMT) can be connected to the FTP server for transmitting the

performance data and files.

9.4.2 Configuring Network Elements

This part describes how to configure the network elements (NEs).



Operation Guide



Issue 03 (2008-04-10)


29/42

When the performance browse tool is started, you must configure the parameters relating to the

File Transfer Protocol (FTP) server of the NE. Then, you can download, query, or browse the

measurement results.

Choose System> Net Configurein the menu, and Net Configuredialog box is displayed. You

can set the FTP download parameters. Refer to Figure 9-3.

Figure 9-3Net Configure dialog box

Table 9-26lists the fields and description in the Net Configuredialog box.

Table 9-26Fields and description in the Net Configure dialog box

Field Description

NE name Set the name of the FTP server. It is often set

to the office name.

FTP config The FTP parameters can be configured when

this field is selected.

IP address Set the IP address and port number of the FTP

server. They are set to the IP address and port

number of the office. For example, if the IP

address of the office is 10.110.218.176, the IP

address is 10.110.218.176.

User Set the user name on the FTP server. For

example, the user GGSN9811 on the office is

10.110.42.12.





9-29


30/42

Field Description

Password Set the user password on the FTP server. For

example, the password for the user

GGSN9811 on the office 10.110.218.176 is

GGSN9811.

Local result Click button to choose and set the directory

for the files downloaded from the FTP server.

This directory is related to the installation

directory of the performance browser tool.

Server path Set the directory on the FTP server to save the

data. The default directory is the root

directory .

NOTEThe directories on the FTP servers of different

products are different.

l For example, the directory to save data on the

FTP server of the GGSN9811 is /bam/data/prf.

l The directory for the small cycle performance

data files is hd:/bam/data/prf-sp.

FTP configuration test Check whether the parameters in the FTP

configuration are configured successfully.

Click the button. Test Succeed!or Test

Failed!is displayed in the left area.

Target file Click button to choose and set the directory

for the measurement description file.The default directory is \adaptor\clientadaptor\product

name\product version\mml\en_US.

The file format is MeasDefinitions.xml.

For example, the directory for the

measurement description file is D:\HW

LMT\adaptor\clientadaptor\GGSN9811

\GGSN9811V800R005ENGC01B013\mml

\en_US. The measurement item file is

MeasDefinitions.xml.

Address list The FTP server address list is displayed. The

names cannot be the same when there are

multiple server names in the address list.

Add Add an FTP server. Add the configured NE

name to the address list.

Modify When an FTP server parameter is modified,

click the button to complete the modification

of NE configuration.

Delete Remove an FTP server from one or multiple

address lists.



Operation Guide



Issue 03 (2008-04-10)


31/42

9.4.3 Downloading Measurement Results

This part describes how to download the measurement results.

With the performance browser tool, you can:

l Import the measurement description file

l Export and browse the measurement result file

When the network element (NE) configuration is complete, choose System> Download

Measurement Results. The Download Measurement Resultsdialog box is displayed. Refer

to Figure 9-4.

Figure 9-4Download Measurement Results dialog box

The FTP server in the address list in the Net Configurewindow is displayed. Double-click the

FTP server name to connect to the server. When the connection is complete, in FTP Server

Directoryin Download Measurement Results, all measurement result files with the extension

name as mrf are listed. The local files are listed in Local Directory.

Select all measurement result files. You can choose multiple files by pressing Shift. Then, clickDownload. The progress bar is displayed. The downloading process may last two to five minutes

when multiple files are downloaded.

When the process is complete, open the directory tree data\176\60 in Local Directory.

Directories are generated based on dates. For example, the measurement result files with

measurement period of 60 minutes on October 18, 2006 are saved in data\176\60\20061018.

9.4.4 Querying Measurement Results

This part describes how to query the measurement results.

Choose System> Query Performance Results. The Query Performance Resultsdialog boxis displayed. Refer to Figure 9-5and Figure 9-6.





9-31


32/42

Figure 9-5Query Performance Results window Counters Information

Figure 9-6Query Performance Results window Time Information

Table 9-27lists the fields and description.



Operation Guide



Issue 03 (2008-04-10)


33/42

Table 9-27Fields and description in the Query Performance Resultswindow

Tab Field Description

Counters information Measurement object class Select the measurement

counters in the order ofmeasurement object class ->

measurement families ->

measurement units. Click ->

or >>to add the counters. All

selected counters are listed in

Selected Counters.

Measurement sets

Measurement units

Available counters

Selected counters

Time information Query mode Period: The value can be 5,

15, 30, or 60 minutes.

Date/time There are three mode for

selecting date and time:

Today: The date is today.

You can also set the time

range by setting the start time

and the end time.

Specified time: It is a

continuous time period. You

can set the start date, end

date, start time, and end time.

For example, from 12:23 on

September 20 to 15:23 on

September 22.

Specified range: It is a time

range in a certain date range.

You can set the start date, end

date, start time, and end time.

For example, from 12:23 to

15:23 from September 20 to

September 22.

When the counters and time are selected, click Query, and then the progress bar is displayed.

When the progress bar is complete, the data of the specified counters in the specified time isdisplayed in time sequence.

9.4.5 Browsing Measurement Description Files

This part describes how to browse the measurement description files.

The measurement description file describes the following information of the network element

(NE) product version:

l Measurement object class

l Measurement item

l Measurement granularity period





9-33


34/42

The performance browser tool uses this file to explain the measurement result file.

You can know about the measurement items and objects provided by the NE through the

measurement description file.

Choose System> Browse Description File. The Browse Description Filedialog box isdisplayed. Refer to Figure 9-7.

Figure 9-7Browse Description File dialog box

9.4.6 Managing Templates

This part describes the objects and the steps of the template management.

9.4.6.1 Creating Customized Templates

You can save the measurement items as a customized template. Then, you can browse the

measurement description file in the form of template, thus simplifying the procedure for querying

the measurement items.

9.4.6.2 Modifying Customized TemplatesYou can modify the customized template by using the template modification function.

9.4.6.3 Deleting Customized Templates

You can delete the customized templates that are created.

9.4.6.4 Using Customized Templates

The performance browse tool provides the function that the items of the same measurement

object can be saved as a customized template, which simplifies the procedure for querying the

results.



Operation Guide



Issue 03 (2008-04-10)


35/42

Creating Customized Templates

You can save the measurement items as a customized template. Then, you can browse the

measurement description file in the form of template, thus simplifying the procedure for querying

the measurement items.

Context

To create a customized template, perform the following steps:

Procedure

Step 1 In the Browse Description Filewindow of the navigation tree, you can open the Adddialogbox in two ways:

l Right-click Custom Template. Choose Addin the shortcut menu.

l Click Custom Template. Choose Template> Add.

Step 2 Click the measurement objects, sets, units, or items in Available Countersin the Adddialog

box displayed. Then, add them to Selected Countersby clicking .

Step 3 Click Save Template. The Informationdialog box is displayed. Type the template name.

Step 4 Click OK.

----End

Modifying Customized Templates

You can modify the customized template by using the template modification function.

Context

To modify a customized template, perform the following steps:

Procedure

Step 1 In the Browse Description Filewindow of the navigation tree, you can open the Modifydialogbox in two ways:

l Right-click the customized template to be modified. Choose Modifyin the shortcut menu.

l Click the customized template to be modified. Choose Template> Modify.

Step 2 Choose the measurement sets, units, or items of the same measurement object in the Modifydialog box displayed. Click Save Template.

Step 3 Click OKin the Confirmdialog box displayed.

----End

Postrequisite

NOTE

You cannot modify the measurement object when modifying the customized template.





9-35


36/42

Deleting Customized Templates

You can delete the customized templates that are created.

ContextTo delete a template, perform the following steps:

Procedure

Step 1 In the Browse Description Filewindow of thenavigation tree, you can open the Deletedialogbox in two ways:

l Right-click the template to be deleted. Choose Deletein the shortcut menu.

l Click the template to be deleted. Choose Template> Delete.

Step 2 Click OKin the Confirmdialog box displayed.

----End

Using Customized Templates

The performance browse tool provides the function that the items of the same measurement

object can be saved as a customized template, which simplifies the procedure for querying the

results.

Context

To query the created templates, perform the following steps:

Procedure

Step 1 In the Browse Description Filewindow of the navigation tree, you can open the QueryPerformance Resultsdialog box in two ways:

l Double-click the template to be queried.

l Press Enter.

Step 2 Set Query Modeand Date/Timein the Query Performance Resultsdialog box displayed.

Step 3 Click Queryto query the items in the template.

----End

9.5 Analyzing Performance Measurement Data

This part describes how to analyze the performance measurement data.

9.5.1 Method for Analyzing Data

This part describes how to analyze the data.

9.5.2 Combined Analysis on Items Relating to the GGSN and SGSNThis part describes the combined analysis on items relating to the GGSN and SGSN.



Operation Guide



Issue 03 (2008-04-10)


37/42

9.5.1 Method for Analyzing Data

This part describes how to analyze the data.

The performance measurement data can be analyzed in following ways:

l Independent analysis on the data of a certain measurement item

Through this analysis, you can infer whether the data is within the reasonable range. The

system is abnormal when the data is extremely high or extremely low.

The analysis on the data of the same measurement item for different load-sharing

measurement objects can show whether the load sharing is normal.

l Comparative analysis on the data in different periods of a certain measurement item

Through this analysis, you can infer whether any burst change occurs. In general, the burst

change is related to the system processing abnormality.

For example, if the number of activation successes in the same period decreases to a largeextent, the activation processing function of the system may be abnormal. You must locate

and clear the fault.

l Comparative analysis on the data of multiple measurement items of a measurement unit

Through this analysis, you can infer whether the relations between measurement items are

normal. For example, you can infer whether the ratio is disproportional.

The main factor of the same category of measurement items can be determined. For

example, by comparing different activation failure causes, you can find that the possibility

of a certain cause may be obviously greater.

l Comparative analysis on the data in the same period of measurement items of multiple

measurement units

This analysis can be used to locate the fault in a complex process.

For example, by comparing the measurement item of the authentication and activation

process errors, you can locate the fault of activation failures due to authentication failures.

9.5.2 Combined Analysis on Items Relating to the GGSN and SGSN

This part describes the combined analysis on items relating to the GGSN and SGSN.

In the packet switched (PS) domain of the general packet radio service (GPRS)/universal mobile

telecommunications system (UMTS) network, the SGSN and the GGSN are two closely related

network elements (NEs). Some performance specifications of the GGSN and SGSN such as

forwarding performance measurement and session measurement must be analyzed jointly.

Table 9-28Analysis on forwarding performance measurement

GGSN Item SGSN Item Analytic Description

Peak byte throughput of the

Gn interface

GTP peak traffic processed

by the Gn interface (kbit/s)

If the difference between the

value for the GGSN and that

for the SGSN is great, it

indicates that the packet loss

over the Gn interface is

serious.





9-37


38/42


Peak packet throughput of

the Gn interface

GTP peak packets processed

by the Gn interface (packet/s)

If the difference between the

value for the GGSN and that

for the SGSN is great, it

indicates that the packet loss

over the Gn interface is

serious.

Uplink bytes of the Gn

interface

Total GTP data traffic sent

through the Gn interface

(KB)

If the value for the GGSN is

smaller than that for the

SGSN and the difference is

great, it indicates that the

uplink packet loss over the

Gn interface is serious.

Uplink packets of the Gn

interface

Total GTP packets sent

through the Gn interface(KB)


smaller than that for theSGSN and the difference is


uplink packet loss over the


Downlink bytes of the Gn

interface

Total GTP data traffic

received through the Gn

interface (KB)


greater than that for the



downlink packet loss over the


Downlink packets of the Gn

interface

Total GTP packets received

through the Gn interface

(KB)





downlink packet loss over the


Table 9-29Analysis of basic session measurement items


PDP context activation

attempts

2G MS activate session

requests + 2G network

activate session requests +


requests + 3G network

activate session requests


smaller than that for the

SGSN, the processing at the

SGSN causes many

activation failures. Besides,

the uplink packets may be

lost on the Gn signaling

plane.



Operation Guide



Issue 03 (2008-04-10)


39/42


Successful PDP context

activations


succeed + 2G network

activate session succeed + 3G

MS activate session succeed

+ 3G network activate

session succeed




SGSN makes many

successfully activated flows

on the GGSN unable to

continue. Besides, the uplink

packets may be lost on the Gn

signaling plane.

Failed PDP context

activations

3G activation failures (due to

GGSN rejection) + 2G

activation failures (due to

GGSN rejection)




SGSN makes many

activation rejected flows on

the GGSN unable to

continue. Besides, the uplink

packets may be lost on the Gn

signaling plane.

Average activated PDP

contexts

Average 3G activation

session users + Average 2G

activation session users

The two parameters must be

the same on the GGSN and

the SGSN. If the difference is

great, check whether packets

are lost on the Gn signaling

plane.

Maximum simultaneouslyactivated PDP contexts

Maximum 3G activationsession users + Maximum 2G

activation session users

The two parameters must bethe same on the GGSN and




plane.

PDP context deactivation

attempts

2G MS deactivate session

request + 2G SGSN

deactivate session requests +


requests + 3G SGSN

deactivate session requests






plane.

Successful PDP context

deactivations


successes + 2G SGSN

deactivate session successes

+ 3G MS deactivate session

successes + 3G SGSN

deactivate session successes






plane.





9-39


40/42

9.6 Clearing Faults of Performance Measurement

This part describes how to clear the faults of performance measurement.

9.6.1 No Performance Measurement Result Generated Due to System Time Changed

This part describes fault 1, that is, no performance measurement result is generated because the

system time is changed.

9.6.2 Number of Deactivation Successes Larger than That of Deactivation Requests Due to the

Period Spanned by a Process

This part describes fault 2, that is, the number of deactivation successes is larger than that of

deactivation requests because the process spans the period.

9.6.3 No Measurement Result Due to Configuration Data Modified

This part describes fault 3, that is, no measurement result is available because the configuration

data is modified.

9.6.1 No Performance Measurement Result Generated Due toSystem Time Changed

This part describes fault 1, that is, no performance measurement result is generated because the

system time is changed.

l Fault description

After the measurement task is created, the measurement result file of a certain period is not

generated, while the measurement result files of other periods are normal.

l

Cause analysisThe log files show that the system time is changed in the period when the measurement

result file is not generated. The measurement result file of corresponding measurement

period may be lost if the system time is changed manually or by the Network Time Protocol

(NTP) server.

l Conclusion

The system time cannot be change at random.

l Comment

The measurement result file of corresponding measurement period cannot be generated if

the system time is changed. If the system time is changed to earlier time, the previous

measurement result files are overwritten. This operation must be avoided.

9.6.2 Number of Deactivation Successes Larger than That ofDeactivation Requests Due to the Period Spanned by a Process

This part describes fault 2, that is, the number of deactivation successes is larger than that of

deactivation requests because the process spans the period.

l Fault description

Observethe performance measurement data, and you can find that the number of

deactivation successes is larger than that of deactivation requests in a record. Refer to the

following:

MS init PDP ctx deact = 1 Ms init PDP ctx deact success = 2



Operation Guide



Issue 03 (2008-04-10)


41/42

l Cause analysis

The performance measurement data is reported based on the periods. By analyzing the

context data during the performance test process, you can find that the number of

deactivation successes is not recorded in the previous measurement data.

The deactivation is being performed when the data is reported in the previous period. Thusthe measurement of the deactivation successes does not start and the success times are

counted into the measurement data of the next period. Therefore, the number of deactivation

successes is larger than that of deactivation requests in the next data.

l Conclusion

If the measurement data is reported when the process is not complete, the success times are

counted into the measurement data of the next period. Therefore, the number of deactivation

successes is larger than that of deactivation requests.

l Comment

The performance measurement data must be analyzed in association with the context data

in the related periods. Otherwise, you may misunderstand the measurement data.

9.6.3 No Measurement Result Due to Configuration Data Modified

This part describes fault 3, that is, no measurement result is available because the configuration

data is modified.

l Fault description

The measurement data of one access point name (APN) is normal all the time; however,

no measurement result is reported since 16: 00.

l Cause analysis

Query the measurement task status, and you can find that the task is normal. Check the

signaling link, and you can find that the APN is deleted.

l Conclusion

The measurement object is deleted. Therefore, the measurement task must be deleted.

l Comment

Any modification to the configuration data relating to the measurement object may lead to

measurement abnormality of the object.





9-41


42/42

01-09 Managing the Performance

Documents

Transcript of 01-09 Managing the Performance