sj-20141121113158-004-netnumen u31 r06 (v12.14.30) unified element management system performance...

NetNumen™ U31 R06Unified Element Management System

Performance Management Description

Version: V12.14.30

ZTE CORPORATIONNo. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://support.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright © 2014 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2014-11-30 First edition

Serial Number: SJ-20141121113158-004

Publishing Date: 2014-11-30 (R1.0)

SJ-20141121113158-004|2014-11-30 (R1.0) ZTE Proprietary and Confidential

ContentsChapter 1 Implementation Principle ......................................................... 1-1

Chapter 2 Basic Concepts......................................................................... 2-1

Chapter 3 Performance Management Functions..................................... 3-13.1 Performance Index Management......................................................................... 3-1

3.2 Measurement Task Management......................................................................... 3-1

3.3 Performance Data Query .................................................................................... 3-1

3.4 Performance Data Export.................................................................................... 3-2

3.5 Performance Data Recollection ........................................................................... 3-2

3.6 Performance Threshold Alarm............................................................................. 3-4

Glossary .......................................................................................................... I

I


This page intentionally left blank.

II


Chapter 1Implementation PrincipleFor the overall performance management flow in the NetNumen U31 system, see Figure1-1.

Figure 1-1 Overall Performance Management Flow

The overall performancemanagement flow in the NetNumen U31 system includes creatinga measurement task, storing performance data, displaying performance data, exportingdata through the northbound interface, and checking thresholds.

1. After a performance measurement task is created on the NetNumen U31, theNetNumen U31 server delivers the task to the NE.

2. The NE reports the performance data to the NetNumen U31 server in accordance withthe granularity and other conditions specified in the measurement task.

3. The NetNumen U31 server stores the performance data in its database.4. Maintenance personnel query the performance data, which can be displayed on the

client in accordance with customized query conditions.

1-1


NetNumen™ U31 R06 Performance Management Description

5. If any threshold task is created, that is, a threshold for an index is set, the NetNumenU31 server enables threshold-based determination when the NE reports performancedata. If the index reaches the threshold, a corresponding alarm is reported anddisplayed on the client.

6. The performance data from the NE can be sent to the upper-layer NMS through thenorthbound interface of the NetNumen U31 server so that maintenance personnel cananalyze the data.

1-2


Chapter 2Basic ConceptsMOC

MOC is the combination of objects with the same properties, such as the IMSI number.

MO

MO can be a physical entity, a logical entity or the combination of the physical entity andlogical entity, which needs to be measured, such as the entire office and a destinationcode.

PO

PO is the basic measurement unit and can measure different MO indexes. Each MO typehas several POs. You can select a PO based on the index to be measured, such as theIMSI flow measurement.

Counter

Counter is a specific measurement index contained in the PO. Each PO has severalcounters. A counter may consist of the following items:

l Counter ID: ID of a performance index.l Description: Description of the performance counters.l Triggers: The measurement triggering point describes the triggering process of a

performance counter.l Collection Method: Collection methods of the performance counters.

Collection methods of the performance counters are described in Table 2-1.

Table 2-1 Collection Method

Value Name Description

CC Accumulation

Counter

It traces the accumulated changes of an event in the collection

granularity (such as PDP activation), and the value of the

counter generally is incremented in an unidirectional way.

Gauge Measurement

Counter

It traces the event data that changes continuously in the

aspect of time, and it can change bidirectionally (meaning that

it can increase or decrease).

Sample Sampling

Counter

It replaces the old data in the counter according to the

reported event data, and the collected data when the collection

granularity period ends is the latest reported event data.

2-1



Value Name Description

TA Time Average

Counter

It samples the value of continuously changing even data every

10 seconds, and calculates and reports the average value of

all 10 - second data when the collection granularity ends.

Max Maximum Value

Counter

It generally obtains the event data every 10 seconds (the data

may be the sampling value of the continuous event data, or

may be the variation of the data over 10 seconds), and only

the maximum result is saved in the counter. In addition, data

reported by this counter is the maximum value of a module

or a unit over the collection granularity period. Data of each

module or unit is independent, therefore, it is meaningless to

combine them by module, and they cannot be provided to

the background as the original data for calculating the peak

KPI of the NE.

Peak Peak Value

Counter

It calculates the peak data of an event in the whole NE using

the peak value algorithm, and the results of this counter are

gathered and displayed on the OMP.

SIMax Maximum

Counter for

Status Check

Some internal counters for resource management are saved

in the measured network element which reads these counters

according to the preset sampling frequency. The measurement

value for the status check is very important at the beginning of

each collection cycle. At the end of each collection cycle, a

valid collection result is calculated according to all sampling

within this period. SIMax is applied for the maximum occasion.

SIMin Minimum

Counter for

Status Check







within this period. SIMin is applied for the minimum occasion.

SIMean Average

Counter for

Status Check







within this period. SIMean is applied for the average occasion.

KPI

KPI is used as the criterion for evaluating the stability and security of the network operation.

2-2


Chapter 2 Basic Concepts

KPI is a compound counter customized by maintenance engineers through arithmeticoperation based on several counters, including:

l User-defined KPI

This kind of KPI is created on the NetNumen U31 client by maintenance engineersthrough arithmetic operation based on the existing counters. You can view, modifyand delete the created KPI.

l System-defined KPI

This kind of KPI is defined by the system. The maintenance engineers can only viewthe KPI on the NetNumen U31 client. The modification and deletion operation are notallowed.

Note:

A KPI can be used to query performance data or create a threshold task.

PI

PI is used as the criterion for evaluating the equipment performance. Similar to KPI, thePI is obtained through arithmetic operation based on several counters. You can create PIsas needed.

Note:

A PI can only be used to query performance data.

Collection Granularity

Collection granularity is the period of collecting the performance data from the front-endNE. The collection granularity can be set to 5 minutes, 15 minutes, and 1 hour etc.

Query Granularity

Query granularity is the period of querying the performance data based on themeasurement task. The query granularity can be set to 5 minutes, 15 minutes, 30minutes, 1 hour and 1 day.

2-3



Note:

The query granularity must be greater than or equal to the collection granularity preset inthe measurement task.

Performance Measurement Task

A performance measurement task defines how to collect, store and transmit performancedata, and how to display and handle the data.

The performancemeasurement task specifies the time and period of collection, the specificPO index and the type of performance data to be collected.

After a performance measurement task is created on the NetNumen U31 client, the systemautomatically collects specified performance parameters within the preset period. Thesystem also gives the statistical result of network performance, from which maintenanceengineers can know the network operation status in time.

Performance Threshold Task

The performance threshold task is also called the QoS task. QoS is a network securitymechanism and technology used to solve problems, such as network delay andcongestion. In an overloaded or congested network, QoS can protect important servicesfrom being delayed or discarded and ensure high-efficiency of the network operation.

In a performance threshold task, the time and the specific PO index, for which the thresholdcalculation is performed, are defined. If the calculation result exceeds the preset thresholdrange, a performance threshold crossing alarm is generated and reported to the faultmanagement system, reminding you of the network operation errors.

2-4


Chapter 3Performance ManagementFunctionsTable of ContentsPerformance Index Management................................................................................3-1Measurement Task Management................................................................................3-1Performance Data Query............................................................................................3-1Performance Data Export ...........................................................................................3-2Performance Data Recollection ..................................................................................3-2Performance Threshold Alarm....................................................................................3-4

3.1 Performance Index ManagementThe performance indexes are consists of:

l Counterl Key Performance Index (KPI)l Ordinary Performance Index (PI)

Some common performance indexes are predefined in the system. The maintenanceengineers can create customized KPIs or PIs based on their needs. The customized indexalso can be used for setting the alarm threshold task.

3.2 Measurement Task ManagementA measurement task defines how to collect, store, and transmit performance data andhow to process and present the performance data. The system collects performance dataand generates the measurement report based on task scheduling rules and the specificgranularity.

For a performance measurement task, the maintenance engineer specifies the NE tobe measured, the MO type, the time interval for collecting performance data, and theentire period for collecting performance data. The NetNumen U31 server delivers themeasurement task to the NE. The NE reports the performance data to the NetNumenU31 server in accordance with the granularity and other conditions specified in themeasurement task.

3.3 Performance Data QueryThe NetNumen U31 supports querying performance data manually based on:

3-1



l User-defined conditions

The maintenance engineers query NE performance data based on customizedconditions.

l Tasks

The maintenance engineers query NE performance data related to the task based onperformance measurement task.

l Templates

The maintenance engineers execute the performance data query template manually,and queries NE performance data based on the preset conditions in the template.

3.4 Performance Data ExportThe NetNumenU31 system supports exporting the performance query data in the followingtwo ways:

l Manually exporting the performance data

After querying the performance data, you can manually export the performance datainto files in CSV, XLS, XLSX, XML, TXT, PDF or HTM formats.

l Automatically exporting the performance data periodically

The system supports querying the performance data by using a template task, andthen exporting the data into files in CSV, XLS, XLSX, XML, TXT, PDF or HTM formats.In addition, NetNumen U31 can send the query result to a specified Email address orto an FTP server.

3.5 Performance Data RecollectionFor how to recollect performance data in the NetNumen U31 system, see Figure 3-1.

3-2


Chapter 3 Performance Management Functions

Figure 3-1 Flow of Recollecting Performance Data

If the collected performance data in the NetNumen U31 is incomplete, recollect the NEperformance data through automatic or manual recollection.

1. The NetNumen U31 server delivers a performance measurement task to an NE underits management.

2. When a measurement period comes, the NE reports the performance data specifiedin the measurement task to the NetNumen U31 server.

3. The NetNumen U31 server gathers and stores the performance data.4. The NetNumen U31 server determines whether any performance data in a specified

period is missing. Maintenance personnel can manually check whether any data ismissing.

5. For the missing NE performance data, the NetNumen U31 server sends a request tothe NE for data recollection. Maintenance personnel also can manually recollect themissing performance data.

6. The NE reports the missing performance data to the server.7. The NetNumen U31 server displays the NE performance data on the client in

accordance with the customized query conditions.

3-3



3.6 Performance Threshold AlarmFor the flow of generating and removing a performance threshold alarm in the NetNumenU31 system, see Figure 3-2.

Figure 3-2 Flow of Generating and Removing a Performance Threshold Alarm

The performance threshold management function monitors the values of tested indexes.If users have set a threshold task and thresholds for a certain index, the NetNumen U31server will enable threshold-based determination upon data report. If the index valueexceeds the threshold, a corresponding threshold alarm is reported and displayed on theclient.

3-4


Chapter 3 Performance Management Functions

1. When a measurement period comes, an NE reports the performance data specified inthe measurement task to the NetNumen U31 server.

2. The NetNumen U31 server checks whether any threshold has been preset for indexesmeasured in the measurement period.

3. If a threshold is preset, the NetNumen U31 server compares the reported performancedata with the preset threshold.

4. The NetNumen U31 server determines whether the NE performance index valuemeets the alarm generating/removing conditions.

5. If the NE performance index value has met the alarm generating/removing conditions,the NetNumen U31 server continues checking whether a threshold alarm for thisperformance index.l Have a threshold alarm for this performance index: Update the alarm informationl Have no threshold alarm for this performance index: Exists in the current system

6. If the NE performance index value has met the alarm generating conditions, and nothreshold alarm for this index exists in the current system, a corresponding thresholdalarm is generated. If the NE performance index value has met the alarm removingconditions, and a threshold alarm for this index exists in the current system, anotification message is generated notifying to remove the threshold alarm.

3-5



This page intentionally left blank.

3-6


GlossaryFTP- File Transfer Protocol

KPI- Key Performance Indicator

KPI

MO- Measured Object

MOC- Measurement Object Class

NE- Network Element

NMS- Network Management System

PI- Performance Index

PO- Performance Object

QoS- Quality of Service

I


sj-20141121113158-004-netnumen u31 r06 (v12.14.30) unified element management system performance...

Documents