SJ - 20130524154927 - 005 - NetNumen U31 R18 V12 - 12 - 43 Perfor

NetNumen™ U31 R18
Unified Element Management System

Performance Management Operation Guide
Version: V12.12.43
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2013 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 ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2013-06-20 First edition
Serial Number: SJ-20130524154927-005
Publishing Date: 2013-06-20 (R1.0)
SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Contents
About This Manual ......................................................................................... I
Chapter 1 Performance Management Overview ...................................... 1-1
1.1 Introduction........................................................................................................ 1-1
1.2 Basic Concepts .................................................................................................. 1-2
1.3 Performance Management Flow.......................................................................... 1-3
1.4 Performance Management Window ..................................................................... 1-5
1.4.1 Overview ................................................................................................. 1-5
1.4.2 Menus for Performance Management ........................................................ 1-6
1.4.3 Toolbar Buttons Related to Performance Management ............................... 1-7
1.4.4 Navigation Pane....................................................................................... 1-7
1.4.5 Performance Management Toolbar............................................................ 1-7
1.5 Implicit Prerequisites .......................................................................................... 1-8
Chapter 2 Measurement Task Management............................................. 2-1

2.1 Overview ........................................................................................................... 2-1
2.1.1 Definition ................................................................................................. 2-1
2.1.2 Opening the Measurement Task Management Tab ..................................... 2-4
2.1.3 Measurement Task Management Toolbar................................................... 2-5
2.2 Creating a Measurement Task............................................................................. 2-6
2.3 Modifying a Measurement Task ......................................................................... 2-15
2.4 Deleting a Measurement Task ........................................................................... 2-15
2.5 Activating a Measurement Task......................................................................... 2-16
2.6 Suspending a Measurement Task...................................................................... 2-17
2.7 Verifying the Consistency Status of a Measurement Task.................................... 2-18
2.8 Synchronizing a Measurement Task .................................................................. 2-21
2.9 Synchronizing Measurement Tasks to the Lower-Layer System........................... 2-21
2.10 Refreshing Measurement Tasks ...................................................................... 2-24
2.11 Exporting a Measurement Task to a ZIP File..................................................... 2-24
2.12 Importing Measurement Tasks From an XML or ZIP File ................................... 2-25
2.13 Verifying the Integrity of Measurement Tasks.................................................... 2-27
Chapter 3 Counter and Index Management ............................................. 3-1

3.1 Overview ........................................................................................................... 3-1
3.1.1 Definition and Classification ...................................................................... 3-1
3.1.2 Opening the Counter and Index Management Tab ...................................... 3-3

3.1.3 Counter and Index Management Toolbar ................................................... 3-5
3.2 Viewing the Counters of a Type ........................................................................... 3-5
3.3 Index Management............................................................................................. 3-7
3.3.1 Creating an Index..................................................................................... 3-7
3.3.2 Creating an Index Group......................................................................... 3-14
3.3.3 Modifying a User-Defined Index .............................................................. 3-15
3.3.4 Modifying the Name of a User-Defined Index Group ................................. 3-16
3.3.5 Viewing the Information of an Existing Index ............................................ 3-16
3.3.6 Deleting a User-Defined Index ................................................................ 3-17
3.3.7 Moving a User-Defined Index to Another Group ....................................... 3-18
3.3.8 Exporting Indexes to an XML File ............................................................ 3-19
3.3.9 Importing Indexes From an XML File ....................................................... 3-20
3.3.10 Setting an Index as a Frequently-Used Index ......................................... 3-22
3.4 Displaying Counters and Indexes in Categories.................................................. 3-24
Chapter 4 Threshold Task Management................................................... 4-1

4.1 Overview ........................................................................................................... 4-1
4.1.1 Definition ................................................................................................. 4-1
4.1.2 Opening the Threshold Task Management Tab........................................... 4-1
4.1.3 Threshold Task Management Toolbar ........................................................ 4-2
4.2 Creating a Threshold Task .................................................................................. 4-3
4.3 Modifying a Threshold Task............................................................................... 4-13
4.4 Deleting a Threshold Task................................................................................. 4-15
4.5 Activating a Threshold Task .............................................................................. 4-16
4.6 Suspending a Threshold Task ........................................................................... 4-17
4.7 Exporting Threshold Tasks to a ZIP File ............................................................. 4-17
4.8 Importing Threshold Tasks From an XML or ZIP File........................................... 4-18
Chapter 5 Query Template Management .................................................. 5-1

5.1 Template Overview............................................................................................. 5-1
5.1.1 Opening the Template Management Tab.................................................... 5-1
5.1.2 Common Templates ................................................................................. 5-2
5.1.3 Query Templates ...................................................................................... 5-3
5.2 Creating a Common Template ............................................................................. 5-4
5.3 Creating a Query Template ................................................................................. 5-6
5.4 Modifying a Template.......................................................................................... 5-8
5.5 Deleting a Template............................................................................................ 5-9
5.6 Exporting Templates to an XML File................................................................... 5-10
5.7 Importing Templates from an XML File................................................................5-11
II

Chapter 6 Template Task Management .................................................... 6-1
6.1 Overview ........................................................................................................... 6-1
6.1.1 Opening the Template Task Management Tab ........................................... 6-2
6.1.2 Template Task Toolbars ............................................................................ 6-3
6.2 Creating a Query Template Task.......................................................................... 6-3
6.3 Creating a Common Template Task ..................................................................... 6-8
6.4 Modifying a Template Task ................................................................................ 6-13
6.5 Activating a Template Task................................................................................ 6-13
6.6 Suspending a Template Task............................................................................. 6-14
6.7 Managing the Running Result of a Template Task .............................................. 6-14
6.8 Ending a Template Task Ahead of Schedule....................................................... 6-16
6.9 Deleting a Template Task .................................................................................. 6-16
6.10 Cancelling the Execution of a Template Task in Waiting Status .......................... 6-17
Chapter 7 Performance Data Query.......................................................... 7-1

7.1 Overview ........................................................................................................... 7-1
7.2 Querying Performance Data................................................................................ 7-1
7.2.1 Querying Performance Data by Customized Conditions .............................. 7-2
7.2.2 Querying Performance Data by Measurement Task .................................. 7-10
7.2.3 Querying Performance Data by Common Template .................................. 7-12
7.2.4 Querying Performance Data by Query Template....................................... 7-13
7.3 Filtering and Rendering Performance Data by Index or Counter .......................... 7-13
7.3.1 Prerequisites.......................................................................................... 7-14
7.3.2 Filtering Performance Data Based on Logical And/Or Operation................ 7-15
7.3.3 Filtering Performance Data Based on Top N Operation ............................. 7-16
7.3.4 Filtering Performance Data Based on Busy Hour...................................... 7-18
7.3.5 Rendering Performance Data in the Query Results................................... 7-19
7.4 Managing Query Results of Performance Data................................................... 7-20
7.4.1 The Toolbar on the Query Result Tab....................................................... 7-20
7.4.2 Displaying Query Results in a Table......................................................... 7-21
7.4.3 Displaying Query Results in a Chart ........................................................ 7-22
7.4.4 Exporting Query Results ......................................................................... 7-23
Chapter 8 Performance Data Monitoring.................................................. 8-1

8.1 Overview ........................................................................................................... 8-1
8.2 Monitoring Performance Data in Real Time .......................................................... 8-1
8.3 Monitoring Historical Performance Data ............................................................... 8-5
Chapter 9 Performance Data Integrity Report ......................................... 9-1

9.1 Overview ........................................................................................................... 9-1
III

9.2 Verifying the Integrity of Performance Data .......................................................... 9-2
9.3 Exporting the Integrity Report to a File ................................................................. 9-7
9.4 Re-Collecting Performance Data of CDMA NEs ................................................... 9-7
Chapter 10 MO Group Management ....................................................... 10-1

10.1 Overview ....................................................................................................... 10-1
10.2 Creating a Group Type.................................................................................... 10-1
10.3 Creating a Group............................................................................................ 10-2
10.4 Creating Groups Automatically ........................................................................ 10-4
10.5 Using a Group................................................................................................ 10-7
Chapter 11 Excel Template Management ............................................... 11-1

11.1 Excel Template ................................................................................................11-1
11.2 Using an Excel Template..................................................................................11-3
Figures............................................................................................................. I
Tables .............................................................................................................V
Glossary .......................................................................................................VII
IV

About This Manual
Purpose
This manual provides explanations and instructions for performance management
operations in the NetNumen U31 R18 Unified Element Management System (NetNumen
U31).
Intended Audience
This manual is intended for:
l Maintenance engineers
l Network planning and optimization engineers
What Is in This Manual

This manual contains the following chapters:
Chapter Summary
1, Performance Management Explains the basic concepts of performance management and the
Overview general performance management flow in the NetNumen U31
system, and describes operation prerequisites and the performance
management window on the GUI of the NetNumen U31.
2, Measurement Task Provides instructions for measurement task management operations.

Management
3, Counter and Index Explains the classification of performance indexes and provides
Management instructions for counter and index management operations.
4, Threshold Task Provides instructions for threshold task management operations.

Management
5, Template Management Provides instructions for template (common template and query
template) management operations.
6, Template Task Describes the functions of template tasks and provides instructions
Management for template task management operations.
7, Performance Data Query Describes how to query performance data and how to manage query
results.
8, Performance Data Describes how to monitor performance data.

Monitoring
9, Performance Data Integrity Describes how to verify performance integrity and save an integrity
Report report.
10, Group Management Provides instructions for object group management operations.

Chapter Summary
11, Excel Template Provides instructions for Excel template management operations.
Management
Related Documentation
The following documentation is related to this manual:
l NetNumen U31 R18 Unified Element Management System Security Management
Operation Guide
l NetNumen U31 R18 Unified Element Management System Fault Management
Operation Guide
Conventions
This manual uses the following typographical conventions:
Typeface Meaning
Italics Variables in commands. It may also refer to other related manuals and documents.
Bold Menus, menu options, function names, input fields, option button names, check
boxes, drop-down lists, dialog box names, window names, parameters, and
commands.
Constant width Text that you type, program codes, filenames, directory names, and function
names.
Note: provides additional information about a certain topic.
II

Chapter 1
Performance Management
Overview
Table of Contents
Introduction ................................................................................................................1-1
Basic Concepts ..........................................................................................................1-2
Performance Management Flow.................................................................................1-3
Performance Management Window............................................................................1-5
Implicit Prerequisites ..................................................................................................1-8
1.1 Introduction
The NetNumenTM U31 R18 Unified Element Management System (NetNumen U31)
provides performance management functions that collect various data from the network
equipment and analyze the data. By using the performance management functions, the
network administrator can obtain complete operation data that indicates the network
status. With this information, the network administrator can make appropriate strategies
that ensure effective network operation.
The performance management functions of NetNumen U31 are classified into the following
seven categories:
l Customization of measurement tasks
This function is used to customize tasks that collect performance data as required.
l Counter and index management
Counter management is used to view counter details.
Index management is used to create, modify, and delete indexes.
l Performance threshold management
This function is used to set the upper and lower thresholds for key performance
indexes. If a threshold task is defined to monitor a key performance index, the system
will report a performance threshold crossing alarm by using the fault management
module when the index value exceeds the upper threshold or drops below the lower.
l Template management and template task management
This function is used to customize common templates, query templates, and
scheduled performance data query tasks.
l Performance data query
1-1

NetNumen™ U31 R18 Performance Management Operation Guide
This function is used to set multiple query conditions for querying performance data
that has been collected.
l Performance data monitoring
à Real-time performance data monitoring
à Historical performance data monitoring
l Performance data integrity query
This function used to query the data integrity in the database.
1.2 Basic Concepts

l Measured Object
A Measured Object (MO) can be a physical entity, a logic entity, or the combination
of physical entity and logic entity, which needs to be measured, for example, a base
station or a cell.
l Measurement Type
A measurement type refers to a performance object, which is a basic unit of
measurement tasks. It supports the measurement of different indexes of a measured
object, such as handover reason and call drop. Different measured objects have
different measurement types. Users can select specific measurement types in
accordance with the indexes to be measured.
The system defines some basic measurement types. The managed Network
Elements (NEs) automatically report the values of counters in these measurement
types without the need of creating related measurement tasks.
l Counter
A counter is a specific measurement item involved in a measurement type. Each
measurement type includes several counters.
l Index
An index is used to evaluate equipment performance. It is the arithmetic result of
several counters. The system provides predefined indexes for common applications.
Users can also customize indexes as needed.
l Collection Granularity
The collection granularity is the period for collecting data from boards in network
equipment. For general measurement tasks, the collection granularity is 15 minutes.
Performance data is collected with a particular delay, and a large amount of data can
be collected at one time.
For the real-time performance monitoring, the collection granularity can be set to 10
seconds, 30 seconds, 1 minute, or 3 minutes. The optional granularities vary with
products. The performance data is collected in near real-time, and a relatively small
amount of data can be collected at one time.
1-2

Chapter 1 Performance Management Overview
l Query Granularity
The query granularity is the granularity for summarizing performance data. For
a common performance data query, such as historical data query, query by task,
and query by template, the granularity can be set to 15 minutes (original collection
granularity), 1 hour, 1 week, or 1 month.
l QoS
The Quality of Service (QoS) contains requirements for a connection. The QoS is used
to solve network delay and congestion problems and can prevent important services
from being delayed or interrupted when the network is overloaded or congested.
l Measurement Task
A measurement task is a task defined for performance data measurement. After a
measurement task is created, the system automatically collects the values of required
performance parameters during the preset period, and gives the statistical result of
network performance, from which the operator can know the network operation status.
The system stores the performance data collected within the latest 180 days by
default. The storage period can be modified in the maintenance management module
as needed.
l Threshold Task
A threshold task is used to monitor specific performance data during a preset period.
As defined in a threshold task, when the value of an index or counter exceeds the
preset upper threshold or drops below the preset lower threshold, an alarm is raised.
The threshold alarm is cleared when the value of the index or counter is within the
preset threshold range during a later measurement period.
1.3 Performance Management Flow

Management Operation Flowchart
Figure 1-1 shows a general performance management flow in the NetNumen U31 system.
1-3

Figure 1-1 Performance Management Flow
Flowchart Description
Table 1-1 describes the basic performance management operations that a user can
perform after successfully starting the NetNumen U31 client and connecting it to the
server.
Table 1-1 Basic Performance Management Operations
Operation Description
Query performance data in real Queries real-time performance data by the granularity of 10
time seconds, 30 seconds, or 1 minutes. For details, refer to “8.2
Monitoring Performance Data in Real Time”.
Create a measurement task Creates a measurement task for collecting performance data
from managed Network Elements (NE). For details, refer to “2.2
Creating a Measurement Task”. The collected performance data
is automatically sent to the NetNumen U31 system.
Query historical performance Queries historical performance data from the data collected
data by measurement tasks. For details, refer to “7.2.1 Querying
Performance Data by Customized Conditions”.
Monitor historical performance Monitors the values of specific indexes or counters during a
data period. For details, refer to “8.3 Monitoring Historical Performance
Data”.
1-4

Operation Description
Verify the integrity of performance Verifies that all performance data of specific measured objects
data has been successfully collected and stored. For details, refer to
“9.2 Verifying the Integrity of Performance Data”.
Create a common or query Creates a common template or query template by setting specific
template query conditions. For details, refer to “5.2 Creating a Common
Template” and “5.3 Creating a Query Template”.
Create a template-based task Creates a query task based on a common or query template for
querying specific performance data periodically. For details, refer
to “6.2 Creating a Query Template Task” and “6.3 Creating a
Common Template Task”.
Manually query performance data Manually queries performance data by using a template-based
task. For details, refer to “7.2.3 Querying Performance Data by
Common Template” and “7.2.4 Querying Performance Data by
Query Template”.
Customize an index Customizes an index based on existing counters and indexes in

the system. For details, refer to “3.3.1 Creating an Index”.
Create a threshold task Creates a threshold task for monitoring specific performance
object. When the calculated value of a specific performance
object (an index or counter) is greater than a upper threshold
or less than a lower threshold preset in the task, a threshold
crossing alarm is reported to the fault management module of the
system. For details, refer to “4.2 Creating a Threshold Task”.
Note:
Performance data collection is the prerequisite for performance data management.
Appropriate measurement tasks must be created before other management operations
are performed.
1.4 Performance Management Window

1.4.1 Overview
Figure 1-2 shows an example of the Performance Management window, in which the
Measurement Task Management tab is displayed.
1-5

Figure 1-2 Performance Management Window
1. Menu bar 4. Performance management

2. Main toolbar toolbar
3. Performance data pane 5. Navigation pane
1.4.2 Menus for Performance Management

The Performance menu on the menu bar of the client window contains the following
commands:
l Realtime Performance Data Monitoring
l History Performance Data Monitoring
l History Performance Data Query
l Common Template Management
l Counter and Index Management
l Measurement Task Management
l Template Task Management
l Threshold Task Management
l Data Integrity Query
Users can click an appropriate command from the Performance menu to implement the
corresponding performance management function.
In addition to the Performance menu, the Performance Statistics submenu on the
Statistics menu also provides some commands for performance management, including:

l Template Task Management
l Common Template Management
1-6

1.4.3 Toolbar Buttons Related to Performance Management

The main toolbar in the client window provides some shortcut buttons related to
performance management functions.
For a description of the toolbar buttons, refer to Table 1-2.
Table 1-2 Buttons Related to Performance Management on the Main Toolbar
Button Function
Queries real-time performance data.
Queries historical performance data.
Manages counters and Indexes.
Manages measurement tasks.
1.4.4 Navigation Pane

The navigation pane organizes NEs, resource types, query templates, and element groups
in the form of a hierarchical tree for convenient performance management operations.
These trees are different from the topological trees in topology management or the other
modules of the NetNumen U31 system.
On the top of the navigation pane in the performance management window are four tabs:
l Model Management: The Resource Type tree on this tab displays the managed
object model, including counters and indexes, by resource type.
l NE Tree: The NE tree on this tab is similar to a topological tree, listing all managed
NEs that support performance management functions.
l Template Management: The template tree on this tab lists query templates
customized for quick performance data query. A common user can only view and
use query templates created by that user, while the administrator can view and use
query templates customized by all users. The tree also lists predefined and user
defined common templates.
l Group Management: The Group Tree on this tab lists all groups created by users
for convenient management of performance data.
1.4.5 Performance Management Toolbar

In the Performance Management window, multiple tabs can be open. Each tab has
a different performance management function. On the upper part of each tab is the
performance management toolbar, which provides shortcut buttons for quick operations.
The performance management toolbar varies with different tabs. Table 1-3 only describes
two common buttons on the performance management toolbar. For a description of other
special toolbar buttons, refer to the corresponding chapters in this manual.
1-7

Table 1-3 Performance Management Toolbar Buttons
Button Function
Customizes the display of columns by hiding or displaying some columns

of a table.
Searches for specific tasks or performance data.
1.5 Implicit Prerequisites

For all operations subsequent to this section, the following prerequisites may be presumed
to have been met:
l The NetNumen U31 client has been started and successfully connected to the server.
l The NetNumen U31 server is connected to lower-level NEs properly.
l The user has been granted with the performance management permission.
1-8

Chapter 2
Measurement Task
Management
Table of Contents
Overview ....................................................................................................................2-1
Creating a Measurement Task....................................................................................2-6
Modifying a Measurement Task ................................................................................2-15
Deleting a Measurement Task ..................................................................................2-15
Activating a Measurement Task ................................................................................2-16
Suspending a Measurement Task.............................................................................2-17
Verifying the Consistency Status of a Measurement Task .........................................2-18
Synchronizing a Measurement Task .........................................................................2-21
Synchronizing Measurement Tasks to the Lower-Layer System ...............................2-21
Refreshing Measurement Tasks ...............................................................................2-24
Exporting a Measurement Task to a ZIP File ............................................................2-24
Importing Measurement Tasks From an XML or ZIP File ..........................................2-25
Verifying the Integrity of Measurement Tasks............................................................2-27
2.1 Overview
2.1.1 Definition
A measurement task specifies the performance data collection methods and the
scheduling principle. In accordance with the task scheduling rule and collection granularity
defined in an activated measurement task, the system collects performance data and
stores collected data in the database of the system. The collected data is a basis for
operations including performance data query, performance monitoring, and data integrity
query.
A measurement task may involve multiple Network Elements (NEs) and multiple Measured
Objects (MOs). When synchronizing such a measurement task to related NEs, the system
converts the task into individual NE-based measurement tasks, each only involving one
NE and one MO. A measurement task created on the client can be regarded as a logical
task that involves one or multiple NE-based measurement tasks.
A measurement task has three important attributes: task status, task origin, and
consistency status. These attributes determine permitted operations in the measurement
task, as explained in the following sections.
2-1

The following describes the common operation flow of a measurement task:

1. Create a measurement task.
2. Activate the measurement task.
3. Check the task consistency and verify that the task is issued to relevant NEs
successfully.
a. If there is an NE-based measurement task whose status is Synchronization
Error, troubleshoot the fault or forcedly delete the NE-based measurement task.
b. Synchronize the measurement task, and reissue the NE-based measurement task
to the NE.
2.1.1.1 Task Status

A measurement task may be activated or suspended.
Note:
The Display Status drop-down list box can be used to show measurement tasks of a
specified status.
l When a measurement task is activated, the system collects performance data from
the specified measured objects in accordance with the settings of the task. Activated
measurement tasks cannot be modified or deleted.
l When a measurement task is suspended, the system does not run the task or collect
performance data required by the task. Only after the suspended measurement
task is successfully activated, will the system collect required performance data
in accordance with the task. Suspended measurement tasks can be modified,
activated, and deleted.
2.1.1.2 Task Origins

The origins of measurement tasks may differ depending on how the tasks are created. For
a description of four probable origins of a measurement task and the operations forbidden
by the system on measurement tasks with different origins, refer to Table 2-1.
Table 2-1 Task Origins
Origin Description Forbidden Operations
Client The origin of a measurement task is client None

when this task is created by using a client GUI
or MML terminal.
2-2

Chapter 2 Measurement Task Management
Origin Description Forbidden Operations
Threshold task The origin of a measurement task is threshold l Modify

task if this task is automatically generated l Activate
for performance data collection during the l Suspend
creation of a threshold task. l Delete
Note: To modify, activate,
suspend, or delete such
a measurement task, an
appropriate operation should
be performed on the threshold
task to which this task is
associated.
Superior task The origin of a measurement task is a l Modify

superior task if this task is assigned by an l Activate
upper-level NMS connected to the NetNumen l Suspend
U31 system. l Delete
Predefined task The origin of a measurement task in the l Modify

NetNumen U31 system is a predefined task. l Delete
Such measurement tasks are created by the
EMS during the system initialization.
Note:
GUI = Graphical User Interface
MML = Man-Machine Language
NMS = Network Management System
EMS = Element Management System
2.1.1.3 Consistency Status

The measurement tasks created by users in the NetNumen U31 system are logical tasks.
One logical task might include multiple NE-based measurement tasks that involves only
one measurement type. These NE-based tasks are sent to individual NEs.
The system considers that the status of a measurement task is consistent when all
of its NE-based measurement tasks are successfully synchronized to all related NEs.
Synchronization failure of any NE-based measurement task will result in inconsistent
status of the measurement task.
Table 2-2 describes the probable consistency status of a logical measurement task and
the forbidden operations on the measurement task in the corresponding status.
2-3

Table 2-2 Consistency Status Descriptions
Consistency Status Description Forbidden Operations
Normal The status of a measurement task is None

displayed as “Normal” when all its NE-based
measurement tasks are successfully
synchronized to the corresponding NEs.
Synchronization Error The status of a measurement task is displayed l Modify

as “Synchronization Error” when the system l Activate
fails to synchronize all or some of its NE-based l Suspend
measurement tasks to the corresponding NEs. l Delete
Synchronizing The status of a measurement task is displayed l Modify

as “Synchronizing” when the system is l Activate
synchronizing its NE-based measurement l Suspend
tasks to the corresponding NEs. l Delete
l Synchronize
Deletion Failure The status of a measurement task is displayed l Modify

as “Deletion Failure” when the system l Activate
fails to delete all or some of its NE-based l Suspend
measurement tasks. l Delete
Completed The status of a measurement task is displayed l Modify

as “Completed” when the end time of the l Activate
task is reached. The system stops collecting l Suspend
performance data from the corresponding
NEs and deems the measurement task as a
historical task.
Deleted The status of a measurement task is l Modify

displayed as “Deleted” when all its NE-based l Activate
measurement tasks are successfully deleted. l Suspend
The system deems the measurement task in
deleted status as a historical task.
2.1.2 Opening the Measurement Task Management Tab

This procedure describes how to open the Measurement Task Management tab in the
client window.
Steps
1. Select Performance > Measurement Task Management on the menu bar.
The Measurement Task Management tab is displayed in the client window, see
Figure 2-1.
2-4

Figure 2-1 Measurement Task Management Tab
– End of Steps –
2.1.3 Measurement Task Management Toolbar

On the upper part of the Measurement Task Management tab, there is a special toolbar,
which provides shortcut buttons for measurement task management. Some buttons on
the toolbar of the tab are unavailable, which can only be activated when an appropriate
measurement task is selected. For a description of the toolbar buttons, refer to Table 2-3.
Table 2-3 Measurement Task Management Tab Toolbar Buttons
Button Function Activated Condition
Creates a measurement task. -
Modifies a measurement task. When a suspended measurement task

is selected and its consistency status is
normal.
Deletes measurement task(s). When a suspended measurement task

normal.
Activates measurement task(s). When a suspended measurement task

normal.
Suspends measurement task(s). When an activated measurement task in

normal status, which is created through
a client, is selected.
Displays the information of a When a measurement task is selected.

measurement task.
Displays the consistency status of a When a measurement task is selected.

measurement task.
2-5

Button Function Activated Condition
Synchronizes measurement task(s) from When a measurement task is selected.

the server to related network elements.
Synchronizes measurement tasks by NE -

agent.
Refreshes the measurement task list. -
Two different buttons are displayed after -

the down arrow is clicked:
: Imports
measurement task(s) from an XML or
ZIP file.
:
Imports an XML or ZIP file, and uses the
imported file as a template for editing
a measurement task.
Exports measurement task(s) to a ZIP One or more measurement task(s) are

file. selected.
Checks the integrity of measurement -

tasks for performance objects of an NE
type.
2.2 Creating a Measurement Task

This procedure describes how to create a measurement task for collecting performance
data from specific MOs. The creation involves specifying the data collection method and
task scheduling rule. For one measurement ask, a maximum of 500 NEs and 5000 MOs
can be selected.
Context
An NE can report performance data only when a target object is configured on the NE and
a new measurement task is created for the target object. All measurement tasks in this
manual are created based on the perquisite that the corresponding target objects have
been configured.
Steps
1. On the Measurement Task Management tab, perform one of the following operations:
l On the toolbar, click .
l In the NE Tree, right-click a managed element, and then click Add Measurement
Task.
l In the task list, right-click an existing task, and then click Add Measurement Task.
2-6

The Add Measurement Task dialog box is displayed with three tabs: Measurement
Task, Location, and General. By default, the Measurement Task tab is displayed,
see Figure 2-2.
Figure 2-2 Add Measurement Task Dialog Box (Measurement Task Tab)
2. On the Measurement Task tab, select an NE type and an MO type, click a task
type, and then select the required Performance Object(s) (PO). For a description of
Measurement Task tab parameters, refer to Table 2-4.
Table 2-4 Measurement Task Tab Parameter Descriptions
Parameter Description Setting
NE type Specifies the type of the NE(s) that the new Select an NE type from the
task will be assigned to. The supported NE drop-down list.
types depend on the managed products
and the version of the NetNumen U31
system.
MO type Specifies the type of MO(s) that the Select an MO type from the
new task is intended for. The MO type drop-down list.
indicates the type of a managed element,
for example, a cell or carrier frequency.
2-7

Mode filter Specifies the wireless network mode of the If the specified NE type is
measurement task. multi-mode (for example, SDR),
and the specified MO type
supports multiple modes (for
example, Link (SDR)), the
Mode filter drop-down list box is
displayed.
Select a wireless system from
the Mode list.
Task type Provides two task types: Select a task type as needed.
l Normal: If this type is selected,
users must select specific POs to be
measured in the PO tree.
l All-PO: If this type is selected, there
is no need to select POs for the new
task because an All-PO measurement
task involves all POs of the selected
MO type.
PO Provides all POs of the selected MO type, Select one or multiple

meaning the types of counters that can be measurement types to determine
measured. the counters of which the
performance data is required.
Note:
The parameters NE type and MO type are associated with each other.
l After an NE type is selected from the NE type list, only the MO types supported
by the selected NE type are available on the MO type list.
l After an MO type is selected from the MO type list, only the NE types supporting
the selected MO type are available on the NE type list.
3. Select the Location tab. The Location tab is displayed, see Figure 2-3.
2-8

Figure 2-3 Add Measurement Task Dialog Box (Location Tab)
4. Select a wildcard level, NE(s) and/or MO(s) for the new task. For a description of
Location tab parameters, refer to Table 2-5.
Table 2-5 Location Tab Parameter Descriptions
Wildcard level The purpose of wildcard level is to facilitate the Select a wildcard level
selection of multiple objects in batches in the NE depending on the
location and MO location trees. The options measured objects to
in the Wildcard level list vary with the selected be selected.
NE type and MO type.
For example, if RNCV309 is selected from the
NE type list, and CPU(WCDMA) is selected from
the MO type list in step 2, three wildcard levels
are optional in the Wildcard level list.
l All: If All is selected, all nodes in the NE
tree and MO tree are selected by default.
l If the wildcard level All is selected, the
system will automatically involve the NEs
added to the system after the creation of
this measurement task. The system will
collect required performance data from the
later-added NEs. This wildcard level is not
2-9

recommended for the types of Measured

Objects that may collect large amount of
performance data.
l NE: If NE is selected, only specific NEs
need to be selected because all CPUs of the
selected NEs will be selected by default.
l CPU: If CPU is selected, users must select
both NEs and CPUs.
NE location The NE tree in the NE location pane lists all Expand the NE tree, and
managed NEs of the selected NE type. select the NE(s) whose
Note: A maximum of 500 NEs can be selected in performance data is
the NE tree for a measurement task. required.
MO location The MO tree in the MO location pane, listing all Expand the MO tree,
measured objects of the selected NEs, varies and select MO(s) whose
with the selected wildcard level. performance data is
Note: A maximum of 5000 MOs can be selected required.
in the MO tree for a measurement task.
Users are required to set MOs manually in the following cases:

l Creating a measurement task related to the MO type UMTS-AP(AG),
UMTS-RUAOffice(AG), UMTS-LAC(AG), or UMTS-VLAC(AG).
l Creating a threshold task or template task, or querying performance data
related to the MO type LTE-AP(AG), UMTS-AP(AG), UMTS-RUAOffice(ag),
UMTS-LAC(AG), or UMTS-VLAC(AG).
These MO types are available when the NE type is Multi-mode Controller (MO).
The following example describes how to set MOs manually when creating a
measurement task related to the MO type UMTS-RUAOffice(AG):
i. On the Location tab, select UMTS-RUAOffice(AG) from the Wildcard level list,
and select the desired NE in the NE location pane. A Manual Input node is
displayed under the NE node in the MO location pane, see Figure 2-4.
2-10

Figure 2-4 Add Measurement Task Dialog Box – Manual Input
ii. Double-click the Manual Input node. The Manual Input dialog box is displayed,
see Figure 2-5.
Figure 2-5 Manual Input Dialog Box
iii. Enter the actual attributes of the MO, and then click OK. The MO is displayed and
selected in the MO tree, see Figure 2-6.
2-11

Figure 2-6 Add Measurement Task Dialog Box – Manually Input MO
5. Select the General tab. The General tab is displayed, see Figure 2-7.
Figure 2-7 Create Measurement Task Dialog Box (General Tab)
2-12

6. Set the general information of the measurement task. For a description of General
tab parameters, refer to Table 2-6.
Table 2-6 General Tab Parameter Descriptions
Task name Specifies the name of the Use the default task name provided by the
measurement task. system, or enter a new task name.
Note: Be sure that the task name is unique
in the system.
Creator Specifies the creator of the This parameter is unmodifiable. The default
measurement task. creator of the measurement task is the
current login user.
Start time Specifies the start time of Select the check box, click the down
the period during which the arrow, and then set the start time of the
measurement task will be run. measurement task.
Note that the start time cannot be earlier
than the system time of the client.
End time Specifies the end time of Select the check box, click the down
the period during which the arrow, and then set the end time of the
measurement task will be run. measurement task.
Note that the end time must be later than
the start time.
Task status Provides the initial status of the Select an initial task status from the
measurement task: Activated drop-down list.
or Suspended. l If Activated is selected, the system
will run the measurement task after
successful creation and collect
performance data when the specified
start time is reached.
l If Suspended is selected, the system
will not run the measurement task after
successful creation until the task is
activated.
Granularity Provides the collection Select a collection granularity from the

granularity, meaning the drop-down list: 15 minutes, 30 minutes, or
cycle of collecting data from 1 hour.
NEs.
2-13

Effective date Specifies the exact execution The default setting is recommended.
date of the measurement task To cancel the measurement task on
in each week or month during specific day(s), select Week or Month.
the previously-set period. and then click those day(s) to remove their
Every day is selected by highlighting.
default.
Effective Time Specifies the time period(s) The default setting is recommended.
when the measurement task To set another period, delete the default
shall be performed during a setting, set the new period in From and To,
day. and then click Add.
The period from 00:00:00 to
24:00:00 is set by default,
which indicates the task is
effective for the entire day.
7. Click OK. A message confirming successful creation of a measurement task is

displayed.
If the measurement task is activated, the collected data is reported when the time is
reached at which the collection is scheduled.
After a measurement task is created, the system converts the task into individual
NE-based measurement tasks, each only involving one NE and one MO, and
then sends these NE-based measurement tasks to the corresponding Operation &
Maintenance Modules (OMMs) that manage the NEs. Upon receiving NE-based
measurement tasks, each OMM forwards the NE-based measurement tasks to the
corresponding NEs.
If the transfer of an NE-based measurement task fails, the measurement task
is marked “Synchronization Error...” in the Consistency Status column. In this
case, users must initiate a synchronization process for the measurement task after
troubleshooting the failure. For how to synchronize a measurement task, refer to 2.8
Synchronizing a Measurement Task.
Note:
If the new measurement task is not displayed, select the corresponding node in
the NE navigation tree or select another value from the Display Status list on the
upper-right of the Measurement Task Management tab.
8. Click OK. The created measurement task is displayed in the measurement task list on
the Measurement Task Management tab.
2-14

2.3 Modifying a Measurement Task

All the settings of a measurement task can be modified except the NE type, MO type,
mode, task type, and task status.
This procedure describes how to modify a measurement task.
Prerequisite
l The measurement task status is Suspended.
l The task consistency status is Normal.
l The task origin is Client.
Steps
1. On the Measurement Task Management tab, locate the measurement task to be
modified, and then perform either of the following operations:
l Click the task, and then click on the toolbar.
l Right-click the task, and then click Modify Measurement Task.
The Modify Measurement Task dialog box is displayed with three tabs:
Measurement Task, Location, and General.
2. Change the selection of PO(s) as needed on the Measurement Task tab.
3. Change the selection of NE(s) and MO(s) as needed on the Location tab.
4. Modify the general information of the measurement task as needed on the General
tab.
5. Click OK. The settings of the measurement task change accordingly. The system
synchronizes the modification to related NE(s) to apply the new settings.
2.4 Deleting a Measurement Task

This procedure describes how to delete a measurement task. One or multiple suspended
measurement tasks can be removed from the system at a time.
Prerequisite
l The task origin is Client.
Steps
deleted, and then perform either of the following operations:
2-15

Note:
To delete multiple measurement tasks, press and hold the Ctrl or Shift key while
selecting the measurement tasks.

l Right-click the task, and then click Delete Measurement Task.
The Delete Measurement Task dialog box is displayed.
2. Click Yes. The consistency status of the measurement task changes to “Deleted”, and
the measurement task becomes a historical task.
2.5 Activating a Measurement Task

The system does not run a suspended measurement task until the task is activated. One
or multiple suspended measurement tasks can be activated in the system.
During activation, the system first converts the measurement task into individual
NE-based measurement task(s) that can be identified and performed by NEs, and
then synchronizes the tasks to related NE(s). After successful synchronization of each
NE-based measurement task, the measurement task becomes activated, and the NE(s)
start collecting performance data on schedule and transferring collected performance
data to the NetNumen U31 server, on which the received performance data is stored in
the database.
This procedure describes how to activate a measurement task.
Prerequisite
Steps
activated, and then perform either of the following operations:
Note:
To activate multiple suspended measurement tasks, press and hold the Ctrl or Shift
key while selecting the measurement tasks.
2-16

Note:
If the system fails to activate the measurement task due to a synchronization error
of an NE-based measurement task, locate the NE-based measurement task and
the failure cause by checking the consistency status of the measurement task.
Refer to 2.7 Verifying the Consistency Status of a Measurement Task.
l Right-click the task, and then select Activate Measurement Task.
After the measurement task is successfully activated, the status of the measurement
task in the Task Status column changes from Suspended to Activated.
2.6 Suspending a Measurement Task

This procedure describes how to suspend a measurement task. Multiple tasks can be
suspended. If a measurement task is suspended, the related data is not collected when
the scheduled collection time is reached.
Prerequisite
l The measurement task status is Activated.
Steps
suspended, and then perform either of the following operations:
Note:
To suspend multiple measurement tasks, press and hold the Ctrl or Shift key while
selecting the measurement tasks.

l Right-click the task, and then click Suspend Measurement Task.
The status of the measurement task in the Task Status column changes from
Activated to Suspended.
2-17

2.7 Verifying the Consistency Status of a Measurement

Task
This procedure describes how to verify the consistency status of a measurement task.
A link problem between the NetNumen U31 system and an NE may result in the
synchronization failure of an NE-based measurement task. In this case, the NE cannot
create a measurement task or collect performance data as required by the NetNumen
U31 system.
The consistency status of a measurement task indicates whether all NE-based

measurement tasks involved in the measurement task have been successfully
synchronized to the related NEs. If so, the consistency status of a measurement task is
Normal . If not, the consistency status is Synchronization Error. For the meaning of
different consistency status, refer to 2.1.1.3 Consistency Status.
Users can check the status of each NE-based measurement task. If the consistency status
of an NE-based measurement task is Synchronization Error, the measurement task can
be activated if the measurement task status is Normal.
Steps
1. On the Measurement Task Management tab, locate the measurement task, and then
perform one of the following steps:
l Right-click the task, and then select View Consistency Status.
l Click the cell in the Consistency Status column of the task row.
The Consistency Status dialog box is displayed, showing the information and
consistency status of each NE-based measurement task involved in the measurement
task. See Figure 2-8.
2-18

Figure 2-8 Consistency Status Dialog Box
2. Perform appropriate operations on each NE-based measurement task by clicking the

corresponding buttons on the toolbar. For a description of the toolbar buttons, refer to
Table 2-7.
Table 2-7 Consistency Status Dialog Box Buttons Description
Button Function
Displays the details of an NE-based measurement task.
Synchronizes an NE-based measurement task to related NEs.
Synchronizes all NE-based measurement tasks in the dialog box to

corresponding NEs.
Deletes an NE-based measurement task.
Deletes all NE-based measurement tasks in “Created Error” status.
Displays the NE-based measurement tasks in the previous page.
Displays the NE-based measurement tasks in the next page.
For example, to view the details of an NE-based measurement task, select the task
and then click on the toolbar (or double-click the task). The Detail dialog box is
displayed, showing the detailed information of the NE-based measurement task, see
Figure 2-9.
2-19

Figure 2-9 Details Dialog Box
3.
Note:
If the consistency status of an NE-based measurement task is “Created Error”, analyze

the cause displayed in the Remark column, troubleshoot the failure, and then click
on the toolbar to synchronize the NE-based measurement task.
If multiple NE-based measurement tasks fail to be created, click to synchronize all
the NE-based measurement tasks after troubleshooting the creation failures.
4. (Optional) Perform the following operations on the NE-based measurement tasks

whose status is Synchronization Error:
l Troubleshoot the link faults between the NetNumen U31 system and the NEs, and
synchronize the measurement task.
After the NE-based measurement tasks are created successfully, the status of
them become Normal and the measurement task status also becomes Normal.
2-20

l Forcedly delete the NE-based measurement tasks whose status is

Synchronization Error, and verify that the measurement task status is Normal.
2.8 Synchronizing a Measurement Task

The consistency status of a measurement task is displayed as “Synchronization Error” if
the system fails to synchronize one or multiple NE-based measurement tasks to related
NEs when creating the task. Users can initiate the synchronization process to ensure that
the measurement task consistency between the NetNumen U31 system and related NEs.
This procedure describes how to synchronize a measurement task.
Steps
synchronized, and then perform either of the following operations:
Note:
To synchronize multiple measurement tasks in “Synchronization Error” status, press
and hold the Ctrl or Shift key while selecting these measurement tasks.

l Right-click the task, and then click Synchronize Measurement Task.
2. Verify the consistency status of the measurement task on the Consistency Status
column. The “Normal” status indicates that the measurement task has been
successfully synchronized.
The system starts synchronizing the measurement task from the server to related
NE(s). After the synchronization is completed, a message is displayed in the message
notification area on the status bar of the client window, indicating the synchronization
result.
2.9 Synchronizing Measurement Tasks to the

Lower-Layer System
This procedure describes how to synchronize measurement tasks to the lower-layer
system.
A lower-layer NE agent may be connected with several NEs. An NE may be assigned
multiple NE-based measurement tasks that are created in the different Element
Management Systems (EMSs).
2-21

This function first removes all existing NE-based measurement tasks from the NE agent,
and then synchronizes related measurement tasks in normal consistency status to the
NE agent. The NE agent then forwards the new NE-based measurement tasks to the
corresponding NEs.
The function commonly applies to NE upgrades or site transfers.
Prerequisite
The user has logged in to the system as the administrator.
Steps
1. On the Measurement Task Management tab, perform either of the following
operations:
l Click on the toolbar.
l Right-click any measurement task, and then select Synchronize Measurement
Task with Lower System.
The Synchronize Measurement Task with Lower System dialog box is displayed.
Note:
Only one NE agent can be selected because the system can only synchronize
measurement tasks for one NE agent at a time.
2. Select an NE type from the NE type list, and then select an NE agent from the NE
agent list under NE agent. See Figure 2-10.
2-22

Figure 2-10 Synchronize Measurement Task with Lower System Dialog Box
3. Click OK. The system starts synchronizing all related measurement tasks from the
server to the NEs managed by the selected NE agent. During the synchronization, the
consistency status of all related measurement tasks is displayed as “Synchronizing”
on the Consistency Status column.
After the synchronization is completed, you can view the synchronization result
in the operation log. The consistency status of each synchronized measurement
task becomes ‘Normal” in the NetNumen U31 system no matter whether the task is
successfully synchronized to the lower-layer system.
If the synchronization is successful, the task information in the lower-layer system is
the same as that in the NetNumen U31 system. If the synchronization fails, the task
information in the lower-layer system does not change.
2-23

2.10 Refreshing Measurement Tasks

Multiple users can manage a network by using different clients connected to the same
NetNumen U31 server. If another user performs some operations related to measurement
tasks, for example, creates a new measurement task, other users may not immediately
view the changes of measurement tasks on their clients due to different response time
between the server and different clients. In this case, other users can refresh the
measurement task list to synchronize the latest information of measurement tasks from
the server to their clients.
This procedure describes how to refresh measurement tasks.
Steps
operations:
l Right-click any measurement task, and then click Refresh Measurement Task.
The local client synchronizes the latest measurement task information from the server,
and then refreshes the measurement task list.
2.11 Exporting a Measurement Task to a ZIP File

This procedure describes how to export a measurement task to a ZIP file.
Steps
exported, and then perform either of the following operations:
Note:
To export multiple measurement tasks, press and hold the Ctrl or Shift key while
selecting these measurement tasks.

l Right-click the task, and then click Export Measurement Task.
The Export Measure Task dialog box is displayed.
2. Select the directory where the ZIP file is to be saved, use the default file name or
enter a new file name, and then click Save. A ZIP file containing the information of the
exported measurement task is displayed in the selected directory.
2-24

2.12 Importing Measurement Tasks From an XML or

ZIP File
This procedure describes how to import multiple measurement tasks from a ZIP or XML
file. Two import methods are supported:
l Importing the file and using it as the template: This method uses the imported file as
the template and allows users to modify the task information in the file before importing
the measurement task.
l Importing the file: This method imports the measurement task from the file directly.
Users can quickly create new measurement tasks by importing predefined measurement
tasks from an XML or ZIP file. To prevent an import failure caused by incorrect information
format, an existing measurement task can be exported to a file from the system and used
as a template. Users can edit the information of the measurement task based on this file,
and then import the modified file to the system.
Prerequisite
l The XML or ZIP file that contains the information for the measurement tasks to be
imported has been prepared.
l The format of measurement task information in the file complies with the one required
by the system.
l Each measurement task defined in the XML or ZIP file has a unique name that differs
from any existing measurement task in the system.
Steps
l To import the file and use it as the template, perform steps 1 to 5.
l To import the measurement task directly from the file, perform steps 6 to 7.

operations:
l Right-click a task in the measurement task list, and select Import the File and
Use It as Template.
l Click the drop-down arrow of the button , and select Import the File and Use
It as Template from the drop-down list.
The Import Measurement Task dialog box is displayed, see Figure 2-11.
2-25

Figure 2-11 Import Measurement Task Dialog Box
2. Select the file to be imported.

3. Click Open. The Import Measurement Task dialog box is displayed, see Figure 2-12.
Figure 2-12 Import Measurement Task Dialog Box
2-26

Note:
The Import Measurement Task dialog box displays the information of the first
measurement task contained in the imported file.
4. Modify the parameters in the Import Measurement Task dialog box, and click OK.
The first measurement task is imported.
5. If the imported file includes the information of multiple tasks, another Import
Measurement Task dialog box is displayed, listing the information of another
measurement task. Modify the information of different tasks individually to import all
tasks.
operations:
l Right-click a task in the measurement task list, and select Import the File.
l Click the drop-down arrow of the button , and select Import the File from the
drop-down list.
The Import Measurement Task dialog box is displayed, see Figure 2-11.
7. Select the file to be imported, and click OK. The measurement tasks included in the
file are imported.
2.13 Verifying the Integrity of Measurement Tasks

This procedure describes how to verify the measurement task integrity of some
Performance Objects (POs).
The purpose of the measurement task integrity verification is to ensure that all performance
data is collected by the system for accurate analysis of network performance.
If a PO is not involved in any measurement task, the system will not collect related
performance data. By verifying the integrity of measurement tasks in the system, users
can get the information of POs for which no measurement task has been created.
l If a PO has been involved in an existing measurement task, its task status is displayed
as “Created”, which indicates some measurement task involving this PO has been
created in an NE managed by the system.
l If a PO has not been involved in any existing measurement task, its task status is
displayed as “Uncreated”, which indicates no measurement task involving this PO
has been created in the system.
Steps
1. On the toolbar of the Measurement Task Management tab, click . The
Measurement Task Integrity dialog box is displayed, see Figure 2-13.
2-27

Figure 2-13 Measurement Task Integrity Dialog Box
2. Select an NE type from NE Type, and select a task status from Show Type.
For a description of Measurement Task Integrity dialog box parameters, refer to Table
2-8.
Table 2-8 Measurement Task Integrity Dialog Box Parameter Descriptions
Parameter Description Example
NE Type Provides the optional NE types, which determine RNCV309

the POs whose measurement task integrity shall be
checked.
Mode If the specified NE type is multi-mode (for example, WCDMA

SDR), the Mode drop-down list box is displayed.
Select a wireless system of the measurement task from
the Mode drop-down list.
Show Type Determines the display of check results by task status: All
Created, Uncreated, or All.
l If Created is selected, the system will display POs
that measurement tasks have been created for.
l If Uncreated is selected, the system will display
POs that no measurement task has been created
for.
l If All is selected, the system will display all POs,
including those involved in some measurement
tasks and those not involved in any measurement
task.
2-28

3. Click Set. The Set PO dialog box is displayed, listing all MO types of the selected NE
type, see Figure 2-14.
Figure 2-14 Set PO Dialog Box
4. Select an MO type to select all POs of this type, or expand the MO type and select
specific POs. After selecting all POs to be checked, click OK to return to the
Measurement Task Integrity dialog box.
5. Click Check.
If the selected number of MO is greater than 20, a confirmation box is displayed,
indicating that the check process may take a long time. Click Yes to continue.
When a message is displayed, indicating that the integrity verification is completed,

click OK.
The Measurement Task Integrity dialog box displays the task status of the selected
POs, including both “Created” and “Uncreated” status, see Figure 2-15. For example,
“Uncreated” status indicates that no measurement task is created for the PO (as
specified in the PO Name column) of the NE specified in the NE Name column.
2-29

Figure 2-15 Measurement Task Integrity Dialog Box
For the POs whose task status is “Uncreated”, users can manually create the
measurement tasks of these POs:
i. In the Measurement Task Integrity dialog box displaying the verification results,
click Create.
If the number of uncreated tasks is greater than 20, a confirmation box is displayed,
asking whether to create the measurement tasks. Click Yes. A message indicating
that the system starts creating tasks is displayed.
ii. Click OK.

The system begins the creating measurement tasks for the POs, and the message
notification area on the status bar displays the creation results.
iii. Click Check again. The task status of all POs changes into “Created”, see Figure
2-16.
2-30

Figure 2-16 Results of Automatic Measurement Task Creation
iv. Click Close. The Measurement Task Management tab is displayed.
A measurement task is created for the POs on the Measurement Task

Management tab. Double-click the measurement task to view its details, see
Figure 2-17. The automatically-created measurement task involves the POs
whose task status used to be “Uncreated” in the integrity verification results.
2-31

Figure 2-17 Details of Automatically-Created Measurement Task
2-32

Chapter 3
Counter and Index
Management
Table of Contents
Overview ....................................................................................................................3-1
Viewing the Counters of a Type ..................................................................................3-5
Index Management.....................................................................................................3-7
Displaying Counters and Indexes in Categories........................................................3-24
3.1 Overview
The NetNumen U31 system organizes counters and predefined indexes by resource type.
In addition to viewing the information of the existing counters and indexes, users can define
new indexes based on these predefined counters and indexes, and group the created
indexes by type for effective management. A user-defined index can be modified, deleted,
and moved between different groups.
Users can monitor important counters and key performance indexes by creating
appropriate threshold tasks. When detecting that the value of the specified counter or
key performance index is out of a preset threshold range, the system reports a threshold
crossing alarm.
Note:
The index management function is unavailable for CDMA network elements in the
NetNumen U31 system.
3.1.1 Definition and Classification

Definition of Counter and Index
Counters and indexes are basic objects in performance management.
l Counter
A counter is a statistical item of a Measured Object (MO) type, for example, “Mean
ratio of the CPU usage (%)”, and “Iu Uplink volume of signalling plane (KB)”. An MO
type includes several counters.
3-1

l Index
An index is a value based on the calculation by several counters. It is used to evaluate
the performance of network device.
The system predefines some indexes for common applications. Users can also
customize indexes as needed. Each index is specified by several attributes, including
index name, formula, thresholds, and value type.
For counters, users can view the details. For indexes, users can perform a collection
of operations, including creating, modifying, viewing, deleting, moving, exporting,
importing indexes.
Index Classification
Indexes can be classified by their importance and origin.
l Index classification by importance
Indexes can be grouped into the following three types by importance.

à Key Performance Index (KPI)
A KPI is an index indicating key system performance. Because KPIs are

important for evaluating the performance of a network, threshold tasks can be
created to monitor KPIs. After threshold ranges at different severity levels are
set for a KPI in a threshold task, the system will report a threshold crossing alarm
with the corresponding severity (critical, major, minor, or warning) when the KPI
value exceeds a preset threshold range.
à Performance Index (PI)
A PI is a common index used to evaluate the system performance.
à Statistical Performance Index (SPI)

An SPI is the count of a measured object based on a statistical rule. The
statistical rule of an SPI must be a valid logical expression. For example, the
logical expression “call completion ratio ≥ 95%” is used to count the number of
serving cells in which the call completion ratio is equal to or higher than 95%.
The formula of an SPI can only contain counters. No KPI, PI, or other SPI can
be used in an SPI formula.
l Index classification by origin

Indexes can also be classified into two types by origin.
à Predefined indexes
The NetNumen U31 system predefines some KPIs, PIs and SPIs for different
measured objects. These indexes cannot be modified or deleted.
à User-Defined indexes
3-2

Chapter 3 Counter and Index Management
The NetNumen U31 system also supports the customization of KPIs, PIs and
SPIs. User-defined KPIs that are not used in any template or task can be modified
and deleted.
Note:
A KPI or PI corresponds to one measured object; while an SPI corresponds to one type of
measured objects.
Index Usage
l To know the operation status of the network.
Users can observe the variation of indexes during a past period by querying the values
of indexes.
l To set threshold tasks.
Users can get the alarm information quickly when the value of a KPI exceeds the
specified threshold after creating threshold tasks for some KPIs.
Only KPIs can be monitored by threshold task. PI and SPI cannot be used in threshold
tasks.
3.1.2 Opening the Counter and Index Management Tab

This procedure describes how to open the Counter and Index Management tab in the
client window.
Steps
1. To open the Counter and Index Management tab, select Performance > Counter
and Index Management from the menu.
The Counter and Index Management tab is displayed in the client window, with the
Model Management tab displayed in the navigation pane, see Figure 3-1.
3-3

Figure 3-1 Counter and Index Management Tab
The Resource Type tree on the Model Management tab organizes counters and
indexes by resource type, see Figure 3-2. The Resource Type tree provides three
default index groups for each MO type to organize indexes by type, which are Key PI,
Ordinary PI, and Statistics PI. These default groups are deemed as the root groups.
To effectively manage user-defined indexes of different types, users can create index
groups (sub-groups) under a root group, and then move user-defined indexes into
different groups based on particular rules.
Figure 3-2 Resource Type Tree
1. Product type 3. Measured object type

2. Network element type 4. Counter type
3-4

3.1.3 Counter and Index Management Toolbar

On the upper part of the Counter and Index Management tab, there is a special toolbar,
which provides shortcut buttons for index management. Some buttons on the toolbar of
the tab are unavailable, which can be activated when an appropriate index is selected. For
a description of the toolbar buttons, refer to Table 3-1.
Table 3-1 Counter and Index Management Tab Toolbar Buttons
Button Function
Creates an index.
Modifies a user-defined index.
Deletes a user-defined index.
Displays the information of an index.
Moves a user-defined index to another index group.
Sets an index as a frequently-used index.
Restores a frequently-used index to a common one.
Refreshes the counter an index information in the system.
Imports indexes from an XML file to the system.
Exports indexes of all or selected rows to an XML file.
3.2 Viewing the Counters of a Type

This procedure describes how to view all counters of a specific counter type.
Steps
1. In the Performance Management window, expand the Resource Type tree in the left
Model Management navigation pane, and then locate the MO type, for example, Cell
(UMTS), see Figure 3-3.
3-5

Figure 3-3 Resource Type Tree
2. Expand the MO type (Cell (UMTS)) node, and then perform either of the following
operations:
Note:
To display all counters of the MO type, you can right-click the MO type node or the
Counter node, and then select Show Counter.
l Expand the Counter node under the MO type, and then click the desired counter
type, for example, Statistics of cell access control.
l Click the Counter node, and then double-click the counter type displayed on the
Counter and Index Management tab.
All counters of the selected counter type are displayed on the Counter and Index
Management tab, see Figure 3-4.
3-6

Figure 3-4 Counters of a Specific Counter Type
3.3 Index Management

3.3.1 Creating an Index
In the NetNumen U31 system, users can create a new index in accordance with the actual
needs by specifying the index name, description, formula, exception value, index type,
value type, NE type, MO type, and thresholds. The user created indexes can be used for
querying the performance data and creating threshold tasks.
This procedure describes how to create a KPI of an MO type.
Steps
1. In the Resource Type tree of the Model Management navigation pane, expand the
target NE node, for example, Multi-mode controller(MO), locate the MO type for
which a KPI needs to be created, for example, ImaGroup(V4).
2. Expand the MO type node, and perform either of the following steps:
l Right-click the Key PI node, and then select New Index.
l Cick the Key PI node, and then click on the toolbar of the Counter and Index
Management tab.
The New Index dialog box is displayed with three tabs: Basic Information, Index
Formula, and Preset Threshold. By default, the Basic Information tab is displayed,
see Figure 3-5.
3-7

Figure 3-5 Create Index Dialog Box (Basic Information Tab)
3. On the Basic Information tab, set the basic information for the index. For a description
of Basic Information parameters, refer to Table 3-2.
Table 3-2 Basic Information Tab Parameter Descriptions
Name Specifies the name for the Enter a character string as the index name,
index to be created. and ensure that the index name is unique in
the system.
Description Specifies the other Leave this box blank if no other information
information for the index is needed.
as needed.
NE type Provides the network element Select an NE type for the index to be created,
types that the index can which determines the counters to be used for
belong to. the index.
MO type Provides the measured object Select an MO type for the index to be created,
type that the index belongs to. which determines the counters to be used for
the index.
Mode filter Specifies the radio access This parameter is displayed when the NE
system that the index is used type selected from NE type is multi-mode,
for. and the MO type selected from MO type
supports multi-mode.
Select a radio access system from the
drop-down list.
3-8

Display format Provides the data types, Select a data type for the index to be created.
including Integer, Long, The following describes the constraint
Float, Percent, and Boolean relationship between index type and data
(1/0). type.
l For KPI, the data type can be Integer,
Long, Float, Percent or Boolean (1/0).
l For PI, the data type can be Integer,
Long, Float, or Percent.
l For SPI, the data type can only be
Boolean (1/0).
Format Provides specific formats Select a specific format if the index to be

for indexes with a value created has a float or percent value.
in float or percent format.
This drop-down list is only
available when Float or
Percent is selected from the
Display format drop-down
list.
Set alarm code Specifies the alarm code of Use the default alarm code 1513, or select
the threshold crossing alarm another alarm code in the range from 1000
that may be reported by the through 1099 from the drop-down list.
system when the index value Note:
exceeds a threshold range. l Only KPIs require an alarm code. This
parameter is unavailable for a PI or SPI.
l If the data type of the index to be created
is Boolean (1/0), no alarm code is
required.
Set value to Specifies a special string or Select Special String (Null), or select Index
the index which an exception value for the Value and type an exception value.
denominator is index to be created, which is Note: This parameter is not required when
0 the calculation result when the index value format is Boolean (1/0).
the denominator of the index Example:
formula is zero. An index formula is “Node B Average CE
Utilization, UL(%)=[Summation of Utilization
Ratio of Uplink NodeB CE(%)]/[Statistics
Times of Utilization Ratio of Downlink NodeB
CE]”. The index value format is "Percent".
If the index exception value is "100", then
“Node B Average CE Utilization, UL(%)” is
100% when [Statistics Times of Utilization
Ratio of Downlink NodeB CE] is zero.
3-9

4. Select the Index Formula tab. The Index Formula tab is displayed, see Figure 3-6.
Figure 3-6 Add Index Dialog Box (Index Formula Tab)
Note:
Users can enter a keyword in the Enter query content text box to search for the target
counter or index, or use the on-screen keyboard in the Edit Formula area to edit the
formula directly.
5. Edit the index formula by clicking the appropriate counters or indexes in the tree in
the Counter And Index For Select pane and necessary operators on the on-screen
keyboard in accordance with their orders in the formula.
For a description of the four special keys on the on-screen keyboard, refer to Table
3-3.
Table 3-3 On-Screen Keyboard Special Key Descriptions
Key Description Example
C C is a prefix used to indicate a counter. C310810040
Gr Gr is a variable used to indicate a collection granularity. -

The unit of Gr is seconds. If the granularity of a record is
15 minutes, the value of Gr is 900. The actual value of
Gr depends on the granularity of each record in the query
results.
3-10

Key Description Example
P P is a prefix used to indicate a performance index. P300790
NO NO indicates the number of measured objects. When the -

system calculates the value of the new index, it gives a
value to NO in accordance with the actual statistical mode
of measured objects.
l If the system queries the index from the original object,
for example, a specific cell, the value of NO is 1.
l If the system queries the index based on a collection of
measured objects, for example, all cells of the same
Radio Network Controller (RNC), the value of NO is the
number of cells belonging to this RNC.
l If the system queries the index based on all measured
objects in the network, the value of NO is the number
of all cells in the network.
The edited formula is displayed in two styles under Edit formula: name style and ID
style, see Figure 3-7.
Figure 3-7 Name Style and ID Style of an Index Formula
6. (Optional) Select the Preset QoS tab. The Preset QoS tab is displayed, see Figure
3-8.
3-11

Figure 3-8 Create Index Dialog Box (Preset Threshold Tab)
Note:
The Preset QoS tab is only available for a KPI whose data type is not Boolean (0/1).
Skip this step for a PI, SPI, or a Boolean KPI to be created.
7. Select a direction, and set the thresholds and corresponding hysteresis (delta).
For a description of Preset QoS tab parameters, refer to Table 3-4.
Table 3-4 Preset QoS Tab Parameter Descriptions
Direction Each index has a direction characteristic Select a direction in accordance

that determines the rule for setting with the characteristics of the
thresholds for it. The following three index to be created.
direction types are optional: l Select Up for such indexes
l Up: An index in “Up” direction that threshold crossing
indicates that the performance alarms are reported when
indicated by the index is considered their values are higher than
acceptable when its value is not too the corresponding preset
large. Call Drop Rate and Bit Error thresholds.
Rate are examples of such indexes. l Select Down for such
l Down: An index in “Down” direction indexes that threshold
indicates that the performance crossing alarms are
indicated by the index is considered reported when their
3-12

acceptable when its value is not too values are lower than
small. Call Completion Rate is an the corresponding preset
example of such indexes. thresholds.
l Up and Down: An index in “Up and l Select Up and Down for
Down” direction indicates that the such indexes that follow
performance indicated by the index the alarm threshold rules
is considered acceptable when its in both “Up” and “Down”
value is appropriate, not too large or directions.
small. For example, the environment
temperature and the rotation speed of
fans should be within a proper range,
which cannot be too high or too low.
The thresholds in both “Up” direction
and “Down” direction need to be set
for such indexes.
Up Four thresholds at different severity levels When the direction is "Up",

Threshold/Down (critical, major, minor, and warning) can set the thresholds on the Up
Threshold be set. Threshold tab based on the
l For a "Up" type alarm threshold, the following constraints:
higher the threshold is, the higher l warning alarm threshold
severity level the reported alarm < minor alarm threshold -
will be. The threshold of "Up" type delta
decreases with the descending of l minor alarm threshold <
alarm severity. major alarm threshold -
l For a "Down" type alarm threshold, delta
the lower the threshold is, the higher l major alarm threshold <
severity level the generated alarm critical alarm threshold -
will be. The threshold of "Down" type delta
increases with the descending of When the direction is "Down",
alarm severity. set the thresholds on the Down
A performance threshold consists of a Threshold tab based on the
threshold value and a delta (hysteresis following constraints:
value). The purpose of a delta is to l warning alarm threshold
avoid frequent switching between alarm > minor alarm threshold +
raising and clearing. A performance delta
threshold with a delta actually provides l minor alarm threshold >
two thresholds: a upper threshold and major alarm threshold +
a lower threshold. For example, If the delta
threshold for raising a critical alarm is 30% l major alarm threshold >
and the corresponding delta is 2%, then critical alarm threshold +
the upper threshold of the performance delta
index is 32%; while the lower threshold is When the direction is
28%. If the delta of a threshold is 0, it can “UpAndDown”, set the
3-13

be considered that the upper threshold thresholds on both Up

and the lower threshold are equal. threshold and Down threshold
When the measured value reaches or tabs.
exceeds a threshold for the first time
(compared with the previous value), the
system generates a threshold crossing
alarm. When the measured value is lower
than a threshold or multiple thresholds
(compared with the previous value), the
system clears the threshold crossing
alarm.
For example, to create an index reflecting the usage ratio of signalling channel, first
analyze the characteristic of this index. The usage ratio of signalling channels is the
proportion of available signalling channels in the network to all signalling channels. A
smaller usage ratio of signalling channel indicates poorer network quality. This index
is an index in the “Down” direction.
l Select Down.
l Enter 60 in the Warning box, and enter 2 in the corresponding Delta box.
l Enter 50 in the Minor box, and enter 2 in the corresponding Delta box.
l Enter 40 in the Major box, and enter 2 in the corresponding Delta box.
l Enter 30 in the Critical box, and enter 2 in the corresponding Delta box.
8. Click OK. The system verifies the validity of the index formula.
l If the index formula is invalid, an error message is displayed, prompting the failure
of index creation.
l If the index formula is valid, the system prompts the successful creation of the
index, assigns a unique ID to the new index and adds it to the index list.
3.3.2 Creating an Index Group

To effectively manage user-defined indexes of different types, users can create index
groups (sub-groups) under a root group (Key PI, Ordinary PI, or Statistics PI).
This procedure describes how to create an index group for grouping user-defined KPIs
under Key PI.
Steps
1. In the Model Management navigation pane, expand the target measured object node
in the Resource Type tree, and then locate the MO type. for which a KPI group is to
be created.
3-14

2. Expand the MO type node, right-click the Key PI node, and then select New Group.
The New Group dialog box is displayed, see Figure 3-9.
Figure 3-9 New Group Dialog Box
3. Enter a name for the new index group in the Group Name text box.
4. Click OK. The created index group is displayed under the Key PI node in the Resource
Type tree.
Note:
l User-defined KPIs can be moved to the group as needed.
l The index group can be modified or deleted as needed. If the index group is
deleted, the indexes included in the group are automatically moved to the index
type node that they previously belong to.
3.3.3 Modifying a User-Defined Index

In the NetNumen U31 system, users can modify an existing user-defined index except its
MO type, NE type, and data type.
Note:
l The default indexes provided by the system cannot be modified.
l Only one index can be modified at a time.
l The MO type, NE type, and value type (display format) cannot be modified.
This procedure describes how to modify a user-defined KPI.
3-15

Steps
1. In the Model Management navigation pane, expand the Resource Type tree, and
then locate the MO type of the user-defined KPI to be modified.
2. Expand the MO type node, and then click the Key PI node. All KPIs of the MO type
are displayed on the Counter and Index Management tab.
3. In the index list, locate the user-defined KPI to be modified, and then perform either of
the following operations:
l Right-click the KPI, and then click Modify Index.
l Click the KPI, and then click on the toolbar.
The Modify Index dialog box is displayed.
4. Modify the user-defined KPI on corresponding tabs, as needed, and then click OK.
3.3.4 Modifying the Name of a User-Defined Index Group

This procedure describes how to modify the name of a user-defined KPI group.
Steps
then locate the MO type whose user-defined KPI group needs to be modified.
2. Expand the MO type node and the Key PI node to locate the index group to be
modified.
3. Right-click the index group, and then select Modify Business Type. The Modify
Business Type dialog box is displayed.
4. Enter a new name in the Group Type text box.
5. Click OK. The name of the user-defined KPI group is changed.
3.3.5 Viewing the Information of an Existing Index

Users can view the detailed information of an existing index in the system.
This procedure describes how to view the information of a KPI.
Steps
then locate the MO type of the KPI to be viewed, for example, RNC (UMTS).
(RNC (UMTS)) are displayed on the Counter and Index Management tab.
3. In the index list, locate the KPI to be viewed, and then perform one of the following
operations:
3-16

Note:
A keyword can be entered in the Enter filter text box on the toolbar to filter the KPIs
and quickly locate the KPI to be viewed when large amounts of KPIs are displayed on
the Counter and Index Management tab.
l Double-click the row of the KPI.

l Click the KPI, and then click on the toolbar.
l Right-click the KPI, and then select View Index.
The View Index dialog box is displayed.
4. View the information of the index on corresponding tabs.
5. Click OK. The View Index dialog box closes.
3.3.6 Deleting a User-Defined Index

One or multiple unused user-defined performance indexes can be deleted from the system.
This procedure describes how to delete a user-defined KPI from the system.
Prerequisite
If the user-defined index to be deleted is a KPI, ensure that it is not used in any threshold
task.
Steps
then locate the MO type of the KPI to be deleted.
3. In the index list, locate the user-defined KPI to be deleted, and then perform either of
Note:
To delete multiple user-defined indexes, press and hold the Ctrl or Shift key while
selecting these indexes.
l Right-click the index, and then click Delete Index.

l Click the index, and then click on the toolbar.
3-17

The Confirm pop-up confirmation box is displayed.

4. Click OK.
3.3.7 Moving a User-Defined Index to Another Group

Multiple sub-groups can be created under a root group as needed. User-defined indexes
of the same group type can be moved between the root group and a sub-group, or between
two sub-groups.
Note:
Only user-defined indexes can be moved between index groups of the same type.
This procedure describes how to move a user-defined KPI from the Key PI root group to
a sub-group.
Prerequisite
Multiple index groups have been created.
Steps
then locate the MO type of the user-defined KPI to be moved.
2. Expand the MO type node, and then click the Key PI node. All KPIs and KPI groups
of the MO type are displayed on the Counter and Index Management tab.
3. In the index list, locate the KPI to be moved, and then perform either of the following
operations:
Note:
To move multiple user-defined indexes to the same group, press and hold the Ctrl or
Shift key while selecting these indexes.
l Right-click the index, and then click Move Index.

The Move Index dialog box is displayed, see Figure 3-10.
3-18

Figure 3-10 Move Index Dialog Box
4. Click the group to which the user-defined index is to be moved, and then click OK. A
confirmation box is displayed, indicating that the index is successfully moved to the
target group.
5. Click OK.
3.3.8 Exporting Indexes to an XML File

One or multiple indexes in the system can be exported to an XML file. If an exported index
references other indexes in its formula, the referenced indexes are also exported to the
XML file.
This procedure describes how to export multiple KPIs of an MO type to an XML file.
Steps
1. Expand the Resource Type tree, and then locate the MO type of the user-defined
indexes to be exported.
3. Press and hold the Ctrl or Shift key while selecting each index to be exported, and
then perform either of the following operations:
3-19

l Right-click any selected index, and then select Export Indexes of Selected
Rows or Export Indexes of All Rows.
l Click the down arrow of the button on the toolbar, and select Export Indexes
of Selected Rows or Export Indexes of All Rows from the drop-down list.
The Save dialog box is displayed, see Figure 3-11.
Figure 3-11 Save Dialog Box
4. Set the file name and saving path, set the file format to XML, and click Save. A
message box is displayed, indicating that the index information is successfully
exported.
5. Click OK.
3.3.9 Importing Indexes From an XML File

This procedure describes how to import indexes from an XML file.
Prerequisite
The XML file containing the information of predefined indexes has been prepared, in which
the index information is organized in the required format that can be identified by the
system.
3-20

Note:
Users can export some indexes from the system first, and then use the exported file as a
template to edit the information of indexes to be imported.
Steps
1. In the Model Management navigation pane, click an index node (Key PI, Ordinary PI,
or Statistics PI). The related indexes are displayed in the right pane.
2. Perform either of the following operations:
l Click on the toolbar of the Counter and Index Management tab.
l Right-click an index in the right pane, and select Import Index.
3. The Import Index dialog box is displayed, see Figure 3-12.
Figure 3-12 Import Index Dialog Box
4. Select the XML file that contains the information of indexes to be imported, and click
Open. The Import Index is displayed, listing the imported indexes, see Figure 3-13.
3-21

Figure 3-13 Import Index Dialog Box (Imported Indexes)
Note:
If the name or ID of an index to be imported is the same as that of an existing index
in the system, the system will prompt the failure of importing this index. If Enabled
Index Conflict Options is selected, the system allows an imported index to have the
same name as an existing index.
l For an index whose name is identical with that of an existing index in the system,
only Overwrite can be selected in the Import Index dialog box to import it from
the XML file. The system will replace the existing index with the imported one.
l For an index whose ID is identical with that of an existing index in the system,
Overwrite or Append can be selected in the Import Index dialog box. If
Overwrite is selected, the system will replace the existing index with the imported
one. If Append is selected, the system will assign a new ID to the index and
import this index as a new index.
5. Select the index(es) to be imported, and then click Import. The imported indexes are
listed in the right pane.
3.3.10 Setting an Index as a Frequently-Used Index

A special attribute can be set for an index to indicate that this index is frequently used.
This function can be used when users are concerned about specific indexes. After a user
3-22

sets the performance management preferences to display only frequently-used indexes,

only frequently-used indexes are visible in the client window, and only performance data
related to these indexes can be queried.
This procedure describes how to set a KPI as a frequently-used index.
Steps
then locate the MO type of the KPI to be set.
2. Expand the MO type node, and then click the Key PI node. Alll KPIs of the MO type
3. Locate the KPI to be set, and then perform either of the following operations:
Note:
To set multiple indexes at a time, press and hold the Ctrl or Shift key while selecting
these indexes.
l Right-click the index, and then select Set Frequently Used Index.
A symbol ( ) is displayed in the corresponding cell on the Frequently Used Index
column.
4. (Optional) To restore the frequently-used index to a common index, perform either of
l Right-click the index, and then select Cancel Frequently Used Index.
5. (Optional) To display only frequently-used indexes in the client window, perform the
following operations:
a. Select System > Customize > Performance Management Preferences from the
menu bar. The Performance Management Preference dialog box is displayed,
see Figure 3-14.
3-23

Figure 3-14 Performance Management Preference Dialog Box
b. Select Frequently Used Index from the Show Index list.

c. Click OK.
3.4 Displaying Counters and Indexes in Categories

This procedure describes how to display performance indexes and counters in categories
as required on the Counter and Index Management tab.
Steps
1. In the Resource Type tree on the Counter and Index Management tab, right-click a
node, and select a menu item from the shortcut menu as required.
If… Then…
Display all performance objects is All performance objects under the node are displayed.
selected
Display counters and indexes is All counters and indexes under the node are displayed.
selected
Display customized indexes is

All customized indexes under the node are displayed.
selected
The Counter node and its sub-nodes do not support the
operation.
3-24

If… Then…
Display system indexes is selected

All system indexes under the node are displayed.
The Counter node and its sub-nodes do not support the

operation.
Display counters is selected

All counters under the node are displayed.
The Key Performance Index (KPI) node, Performance

Index (PI) node, and Statistics Performance Index (SPI)
node do not support the operation.
3-25

This page intentionally left blank.
3-26

Chapter 4
Threshold Task Management
Table of Contents
Overview ....................................................................................................................4-1
Creating a Threshold Task..........................................................................................4-3
Modifying a Threshold Task ......................................................................................4-13
Deleting a Threshold Task ........................................................................................4-15
Activating a Threshold Task......................................................................................4-16
Suspending a Threshold Task ..................................................................................4-17
Exporting Threshold Tasks to a ZIP File ...................................................................4-17
Importing Threshold Tasks From an XML or ZIP File ................................................4-18
4.1 Overview
4.1.1 Definition
A threshold task can be defined as monitoring specific measurement data during a preset
period. When the calculated value of a specific performance object (an index or counter)
is larger than a upper threshold or smaller than a lower threshold preset in the task, a
threshold crossing alarm is reported to the fault management module of the NetNumen
U31 system. The threshold crossing alarm is cleared when the calculated value during a
later measurement period is within the preset threshold range.
When a threshold task is created, the system automatically creates a measurement task
to collect the performance data required for the calculation of index values. The origin of
this measurement task is identified as threshold task.
Note:
The threshold task function is unavailable for CDMA network elements in the NetNumen
U31 system.
4.1.2 Opening the Threshold Task Management Tab

This procedure describes how to open the Threshold Task Management tab in the client
window.
4-1

Steps
1. To open the Threshold Task Management tab, select Performance > Threshold
Task Management on the menu bar.
The Threshold Task Management tab is displayed. To display all created threshold
tasks in the system, click the root node on the NE tree, see Figure 4-1.
Figure 4-1 Threshold Task Management Tab
4.1.3 Threshold Task Management Toolbar

On the upper part of the Threshold Task Management tab, there is a special toolbar,
which provides shortcut buttons for threshold task management. Some buttons on the
toolbar of the tab are unavailable, which can only be activated when an appropriate
threshold task is selected. For a description of the toolbar buttons, refer to Table 4-1.
Table 4-1 Threshold Task Management Tab Toolbar Buttons
Button Function Activated
Creates a threshold task. -
Modifies a threshold task. When a suspended threshold task

is selected.
Deletes threshold task(s). When a suspended threshold task

is selected.
Activates threshold task(s). When a suspended threshold task

is selected.
4-2

Chapter 4 Threshold Task Management
Button Function Activated
Suspend threshold task(s). When an activated threshold task

is selected.
Displays the information of a threshold When a threshold task is selected.

task.
Refreshes the threshold task list. -
Imports threshold task(s) from an XML -

or ZIP file.
Exports threshold task(s) to a ZIP file. When some threshold task(s) is

selected.
4.2 Creating a Threshold Task

A threshold task can be created for monitoring important KPI(s) and/or counter(s). When
the value of a monitored KPI or counter exceeds the preset threshold, a threshold-crossing
alarm is reported in the system.
Note:
Only KPIs and counters can be used in a threshold task.
This procedure describes how to create a threshold task.
Steps
1. On the Threshold Task Management tab, perform one of the following operations:
l On the toolbar, click .
l In the navigation pane, expand the NE tree, right-click an NE node, and then
select Add Threshold Task.
l In the task list, right-click an existing task, and then select Add Threshold Task.
The Add Threshold Task dialog box is displayed with three tabs: Threshold Task,
Location, and General. By default, The Threshold Task tab is displayed, see Figure
4-2.
4-3

Figure 4-2 Add Threshold Task Dialog Box (Threshold Task Tab)
2. On the Threshold Task tab, select an NE type and an MO type, and then add the
index(es) to be monitored. For a description of Threshold Task tab parameters, refer
to Table 4-2.
Table 4-2 Threshold Task Tab Parameter Descriptions
NE type Provides the NE types for selection, Select an NE type depending on the
which determine the indexes and KPIs and/or counters to be monitored.
counters that can be used in the
threshold task.
MO type Provides the available MO types Select an NE type depending on the

of the selected NE type, which KPIs and/or counters to be monitored.
determines the indexes and
counters that can be used in the
threshold task.
4-4

Mode filter Specifies the radio access system Select a radio access system from the
of the threshold task. drop-down list.
This parameter is displayed when
the NE type selected from NE type
is multi-mode, and the MO type
selected from MO type supports
multi-mode.
Condition Sets a Boolean index as the If the selected MO types include

prerequisite for deciding whether a Boolean index, the Condition
to raise an alarm. Only when the drop-down list box is displayed, see
Boolean index value is true will the Figure 4-3. Select a Boolean index
index set in the Threshold Index from the list.
area be used to decide whether to
raise an alarm.
For example, you can set a
boolean-type index whose
formula is C901470001 (number
of transmitting the SUSPEND
message) > 10. If you select the
Boolean index in the Condition
drop-down list as the prerequisite,
when the number of transmitting
the SUSPEND message is over 10,
the system will check the indexes
set in the Threshold index area to
decide whether to raise an alarm.
Threshold Index Specifies the indexes and/or Click Add index... to add KPIs and/or
counters related to the threshold counters to be monitored.
task. l If a counter is selected, thresholds
should be set for the counter.
l If a KPI is selected, the default
threshold settings of the KPI can
be directly used or modified as
needed.
Additional Displays the additional information Add an explanation for

Information of the threshold task. threshold-crossing alarms that may be
reported, and handling suggestions of
the alarms if needed when setting the
added counter or index.
4-5

Figure 4-3 Add Threshold Task Dialog Box (Condition List)
The following example describes how to set the parameters on the Threshold Task
tab:
a. Select an NE type from the NE type drop-down list, for example, Multi-mode
controller(MO).
b. Select an MO type from the MO type drop-down list, for example, Cell(UMTS).
c. Click Add Index under Threshold index. The Select Indices/Counters dialog
box is displayed. See Figure 4-4.
4-6

Figure 4-4 Select Indices/Counters Dialog Box
d. Expand the Counter node, select the counter(s) to be monitored , and then click
OK. The selected counters are listed in the Add Threshold Task dialog box, see
Figure 4-5.
Figure 4-5 Counters Added
e. To delete a selected counter or index, click the counter or index record, and click
Delete Index.
f. Set new thresholds for each counter or KPI:
4-7

Note:
If only KPI(s) are selected for the threshold task and there is no need to modify
their thresholds, skip this step.
The modification of KPI thresholds during threshold task creation is only valid for
the task. The modification does not affect the default thresholds of the KPI.
Double-click the counter directly, or select the counter first and then click Modify
Threshold. The Modify Threshold dialog box is displayed. See Figure 4-6.
Figure 4-6 Modify Threshold Dialog Box
Note:
For the description and setting instructions of the parameters in the Modify
Threshold dialog box, refer to 3.3.1 Creating an Index.
g. Set thresholds and deltas (hysteresis values) corresponding to four different

severity levels, type additional information about the task or alarm handling
suggestion in the Additional Information box, and then click OK.
4-8

Figure 4-7 Add Threshold Task (Location Tab)
4. Select the location of managed elements from which the performance data shall be
collected. For a description of the Location tab parameters, refer to Table 4-3.
Table 4-3 Location Tab Parameter Descriptions
Parameter Description
Monitor Level The monitor level refers to the level on which the index value or counter
value is collected or calculated. Threshold crossing alarms are also
reported on this level. The options of this parameter vary with different
NE types and MO types.
In this example, NE type is “BSC(GV3)”, and MO type is “BVC(GSM)”.
l If “BSC Managed NE” NE Layer is selected, the summarized
values include the counters and indexes included in the serving
cells related to the base stations under the SGSNs managed by
the BSCs. If the collected value exceeds a specified threshold, the
corresponding BSC will report an alarm.
The counters included in the index are summarized by BSC first, and
then calculation is performed based on the index formula.
l If “SGSN” MO Layer is selected, the summarized values include the
counters and indexes included in the serving cells related to the base
4-9

stations under the SGSNs. If the collected value exceeds a specified

threshold, the corresponding SGSN will report an alarm.
The counters included in the index are summarized by SGSN first,
and then calculation is performed based on the index formula.
l If “Base Station” MO Layer is selected, the summarized values
include the counters and indexes included in the serving cells related
to the base stations. If the collected value exceeds a specified
threshold, the corresponding base station will report an alarm.
The counters included in the index are summarized by base station
first, and then calculation is performed based on the index formula.
l If “Cell” MO Layer is selected, the system compares the values of
the indexes and counters related to the serving cell with the specified
thresholds. If any value exceeds a threshold, the corresponding
serving cell will report an alarm.
Wildcard Level The purpose of wildcard level is to facilitate the selection of multiple
objects in batch on the NE location and MO location trees. The options in
the Wildcard Level drop-down list box vary with the selected NE type
and MO type.
In this example, the NE type is “BSC(GV3)”, and the MO type is
“BSC(GSM)”. The optional wildcard levels include:
l All: All nodes on the NE tree and MO tree are selected by default.
l NE: The user only needs to select specific NEs. All CPUs of the
selected NEs are selected by default.
l BVC: The user needs to select specific serving cells.
NE Location Lists the NEs that can be selected for the threshold task.
MO Location Lists the MO(s) that can be selected for the threshold task.
5. Select the General tab. The General tab is displayed, see Figure 4-8.
4-10

Figure 4-8 Add Threshold Task Dialog Box (General Tab)
6. Set the general information of the threshold task. For a description of the General tab
parameters, refer to Table 4-4.
Table 4-4 General Tab Parameter Descriptions
Task name Specifies the name of the new Use the default task name generated by the
threshold task. system or enter a unique name in the box
for clear identification of the task.
Creator Specifies the creator of the This parameter is unmodifiable. It is set as

new threshold task. the current login user by default.
Start time Specifies the start time of the Set the start time of the threshold task. Be
period during which the new sure that the start time is later than the
threshold task will be effective. current system time of the client.
End time Specifies the end time of the Set the end time of the threshold task. Be
period during which the new sure that the end time is later than the start
threshold task will be effective. time.
4-11

Task status Specifies the initial status of l Select Activated to make the new
the new threshold task. threshold task apply immediately after
it is successfully created, or
l Select Suspended to suspend the new
threshold task after it is successfully
created.
Granularity Provides the cycle for Select a granularity from the drop-down list.
performance data collection:
15 minutes, 30 minutes and 1
hour.
Effective date Specifies the exact running Set the effective date weekly or monthly by
date of the threshold task in clicking a date directly to select or deselect
each week or month during it. The highlighted dates are effective date
the previously-set period. when the threshold task shall be performed.
Effective time Specifies the time period(s) The period from 00:00:00 to 24:00:00 is
when the threshold task shall set by default, which indicates the task is
be performed during a day. effective for the entire day. To set another
period, delete the default setting, set the
new period and click Add.
Note:
If the threshold task contains only basic measurement type counters or indexes
made up of only such counters, the system will not generate a new measurement
task.
7. Click OK. The created threshold task is displayed on the Threshold Task
Management tab.
At the same time, an associated measurement task is displayed on the Measurement
Task Management tab, which is automatically generated by the system for collecting
performance data required by the threshold task.
If the threshold task is activated, the system compares the collected and calculated
values with the thresholds. Once the value of an index or counter exceeds a
threshold, a threshold crossing alarm on a specific severity level is reported to the
fault management module of the system.
4-12

Example
If the user-defined index, “the usage ratio of signalling channel”, is used in a threshold
task, the thresholds set for this index are as follows:
Severity Threshold (Unit: %) Delta (Unit: %)
Critical 30 1
Major 40 1
Minor 50 2
Warning 60 3
Table 4-5 explains how the reported threshold crossing alarm varies with the index value.
Table 4-5 Alarm Variation Due to Index Value Change
Index Value Change Alarm Severity Change
When the index value (60–3)% A threshold crossing alarm at Warning level is reported.
decreases to
(50–2)% The severity level of the threshold crossing alarm is upgraded
from Warning to Minor.

from Minor to Major.

from Major to Critical.
When the index value (60+3)% The threshold crossing alarm at Warning level is cleared.
increases to
(50+2)% The severity level of the threshold crossing alarm is degraded
from Minor to Warning.

from Major to Minor.

from Critical to Major.
4.3 Modifying a Threshold Task

The settings of a threshold task can be modified, including the selected indexes and
counters, monitor level, wildcard level, NE location, MO location, task name, start time,
end time, granularity, effective date and time period.
4-13

Note:
l The start time of a threshold task can be modified only when the current time is earlier
than the start time.
l Only one threshold task can be modified at a time.
This procedure describes how to modify a suspended threshold task on the Threshold
Task Management tab.
Prerequisite
l The threshold task to be modified is suspended.
l The consistency status of each measurement task associated with the threshold task
is normal.
l The Display Status is All task(s).
Steps
1. In the navigation pane, expand the NE tree, and then click the related NE. All threshold
tasks of this NE are displayed on the Threshold Task Management tab, see Figure
4-9.
Figure 4-9 Threshold Tasks of an NE
2. In the task list, locate the threshold task to be modified, and then perform either of the
l Right-click the task, and then select Modify Threshold Task from the shortcut
menu.
The Modify Threshold Task dialog box is displayed, see Figure 4-10.
4-14

Figure 4-10 Modify Threshold Task Dialog Box
3. Modify the parameters of the threshold task as needed on the Threshold Task,
Location, and General tabs.
4. Click OK.
4.4 Deleting a Threshold Task

One or multiple unused threshold tasks can be removed from the system.
This procedure describes how to delete a threshold task.
Prerequisite
l The threshold task to be deleted is suspended.
is normal.
Steps
tasks related to this NE are displayed on the Threshold Task Management tab.
2. In the task list, locate the threshold task to be delete, and then perform either of the
4-15

Note:
To delete multiple suspended threshold tasks, press and hold the Ctrl or Shift key
while selecting these threshold tasks.
l Right-click the task, and then click Delete Threshold Task.

The Delete Threshold Task dialog box is displayed.
3. Click OK. The threshold task and all associated measurement tasks are removed from
the Threshold Task Management tab.
4.5 Activating a Threshold Task

The system starts collecting required performance data and calculating the index values
only when a threshold task is activated.
This procedure describes how to activate a suspended threshold task.
Prerequisite
l The threshold task to be activated is suspended.
is normal.
Steps
2. In the task list, locate the threshold task to be activated, and then perform either of the
Note:
To activate multiple suspended threshold tasks, press and hold the Ctrl or Shift key
while clicking these threshold tasks.
l Right-click the task, and then click Activate Threshold Ttask.

4-16

The status of the threshold task changes from Suspended to Activated.

4.6 Suspending a Threshold Task

This procedure describes how to suspend an activated threshold task.
Prerequisite
l The threshold task to be suspended is activated.
is normal.
Steps
2. In the task list, locate the threshold task to be suspended, and then perform either of
Note:
To suspend multiple activated threshold tasks, press and hold the Ctrl or Shift key
while selecting these threshold tasks.
l Right-click the task, and then select Suspend Threshold Task.

The status of the threshold task changes from Activated to Suspended.
4.7 Exporting Threshold Tasks to a ZIP File

One or multiple threshold tasks can be exported to a ZIP file.
This procedure describes how to export multiple threshold tasks of the same NE to a ZIP
file.
Steps
2. Press and hold the Ctrl or Shift key, click the threshold tasks to be exported, and then
perform either of the following operations:
4-17

l Right-click any selected task, and then click Export Threshold Task.
The Export Threshold Task dialog box is displayed.
3. Select the directory where the ZIP file is to be saved, use the default file name or
enter a new file name, and then click Save. The ZIP file containing the information of
exported threshold tasks is displayed in the selected directory.
4.8 Importing Threshold Tasks From an XML or ZIP File

Users can quickly create new threshold tasks by importing predefined threshold tasks from
an XML or ZIP file. To prevent an import failure caused by incorrect information format, it
is recommended to export an existing threshold task from the system and use the result
file containing the exported information as a template. Users can edit the information of
the threshold task based on this file, and then import the modified file to the system.
This procedure describes how to import threshold tasks from a predefined XML file.
Prerequisite
l The XML or ZIP file containing the information of threshold tasks to be imported has
been prepared.
l The format of threshold task information in the file complies with the format required
by the system.
l The names of the threshold tasks to be imported are different from those of the existing
threshold tasks in the system.
Steps
1. In the navigation pane, expand the NE tree, click the related NE, and then perform
either of the following operations:
l Right-click any threshold task in the task list, and then click Import Threshold
Task.
The Import Threshold Task dialog box is displayed.
2. Select the directory where the XML file is saved, select the XML file to be imported,
and then click Open. The imported threshold tasks are displayed in the task list on the
Threshold Task Management tab.
4-18

Chapter 5
Query Template Management
Table of Contents
Template Overview.....................................................................................................5-1
Creating a Common Template ....................................................................................5-4
Creating a Query Template.........................................................................................5-6
Modifying a Template .................................................................................................5-8
Deleting a Template....................................................................................................5-9
Exporting Templates to an XML File .........................................................................5-10
Importing Templates from an XML File .....................................................................5-11
5.1 Template Overview

The NetNumen U31 system provides templates for querying performance data. A template
contains preset conditions for querying different types of data. Two types of templates are
available: common template and query template.
5.1.1 Opening the Template Management Tab

This procedure describes how to open the Template Management tab in the client window.
Steps
1. To open the Template Management tab, perform either of the following operations:
l Click the Template Management tab in the left navigation pane of the
Performance Management window.
l Select Performance > Template Management on the menu bar.
l Select Statistics > Performance Statistics > Template Management on the
menu bar.
The Template Management tab is displayed, see Figure 5-1.
5-1

Figure 5-1 Template Management Tab
2. (Optional) In the template tree, select History Performance Data Query Template
or Common Template to use query templates or common templates for further
operation.
5.1.2 Common Templates

A common template specifies query conditions for performance data query, including
Network Element (NE) type, Measured Object (MO) type, Performance Object (PO),
location, query granularity and valid time period. The common template can be used
to query specific performance data. It can also be used in a template task to schedule
periodic performance data query.
In the NetNumen U31 system, some predefined common templates are available, such as,
“Cell Performance and Utilization Report”, “Cell Traffic Performance Report”, and “NodeB
Performance and Utilization Report”, which are marked as system-defined. Users can also
customize common templates, which will be marked as user-defined in the system.
Users can perform the following operations on common templates:

l Creating a common template
l Modifying a common template
l Deleting a common template
l Exporting and importing a common template
5-2

Chapter 5 Query Template Management
Common Template Permissions

In the NetNumen U31 system, different users may be allocated with different permissions
on system-defined common templates and user-defined ones. The following are two
examples:
l If a user account is granted with the View Common Template permission, this user
can only view the information of common templates after logging in to the system.
l If a user account is granted with the Common Template Operation permission, this
user can create, modify, delete, and import common templates after logging in to the
system. In addition, a user can modify the common template created by that user.
For how to allocate common template permissions to a user, refer to the NetNumen U31
R18 Unified Element Management System Security Management Operation Guide. Figure
5-2 shows the permissions that can be granted to a user.
Figure 5-2 Common Template Operations
5.1.3 Query Templates

A query template specifies the conditions for querying performance data. Query templates
can be used to carry out multiple queries in the same query mode.
To create a query template, users need to specify not only NE type, MO type, and POs,
but also NE location, MO location, and query execution time.
Users can either use a query template to create query template tasks that query
performance data automatically on scheduled time, or execute a query based on the
query template immediately.
Query templates in a NetNumen U31 system can be exported and then imported to another
NetNumen U31 system.
5-3

On the Template Tree tab, users can create, modify, import, export, delete, save, and run
query templates.
5.2 Creating a Common Template

A common template can be created with preset query conditions (such as, NE type, MO
type, and POs).
Note:
For Code Division Multiple Access (CDMA) NEs, a maximum of 40 indexes and counters
can be selected in a common template. For other NEs, a maximum of 300 indexes and
counters can be selected in a common template.
This procedure describes how to create a common template.
Prerequisite
l The Template Management tab is displayed in the Performance Management
window.
l The user logging in to the NetNumen U31 system has been granted with the “Common
Template Operation” permission.
Steps
1. In the Template Management tree in the right pane, select the Common Template
node.
2. Click on the toolbar of the Template Management tab. The Add Common
Template dialog box is displayed, see Figure 5-3.
5-4

Figure 5-3 Add Common Template Dialog Box
Note:
For a description of parameters in the New Common Template dialog box, such as
NE Type, MO Type, and PO, refer to 2.2 Creating a Measurement Task.
3. Enter a name for the common template to be created in the Name box.
4. Enter the additional information for the new common template in the Description box.
5. Select an appropriate access type for the template. The options are:
l Share: Any one can view, modify, and delete the template.
l Private: Only the creator can view, modify, and delete the template.
l Public: Only the creator can modify and delete the template. Other users can
view the template.
6. Select an NE type from the NE type list.

7. Select one or multiple MO types from the MO type list.
8. Select the counters and/or indexes to be queried in the Measurement Object Type
tree.
9. To set rendering and filtering rules for displaying queried performance data, click
Logic, TopN, and/or Busy Hour in the Selected indices/counters pane, and
perform appropriate operations as required. For the details of how to set rendering
and filtering rules, refer to 7.3 Filtering and Rendering Performance Data by Index or
Counter.
5-5

Note:
The Logic, TopN, and Busy Hour buttons are unavailable when the common template
is created for CDMA NEs.
10. Click OK. The created common template is displayed in the template list on the
Template Management tab.
5.3 Creating a Query Template

This procedure describes how to create a query template in Direct execution mode.
Steps
1. In the Template Management tree in the right pane, select the History Performance
Data Query Template node.
2. Click on the toolbar of the Template Management tab. The Add Template dialog
box is displayed, see Figure 5-4.
Figure 5-4 Add Template Dialog Box
3. Set template parameters in the Add Template dialog box. For a description of the
parameters, refer to Table 5-1.
Table 5-1 New Template Dialog Box Parameter Descriptions
Name Template name.
5-6

Operation mode Specifies the execution method of the template. The options are:
l Confirm before execution: During the execution of the template,
users can modify the template parameters in a pop-up dialog box.
l Direct execution: During the execution of the template, users
cannot modify the template. The template is executed directly.
Access type Specifies the operation permissions for the created template. The
options are:
l Share: Any one can view, modify, and delete the template.
l Private: Only the creator can view, modify, and delete the
template.
l Public: Only the creator can modify and delete the template.
Other users can view the template.
4. Click OK. The Add Query Template dialog box is displayed, see Figure 5-5.
Figure 5-5 Add Query Template Dialog Box
Note:
The query template parameters are similar to those for the customized query
of performance data. For details, refer to 7.2.1 Querying Performance Data by
Customized Conditions.
5-7

5. Set query conditions on the Indices Selection, Object Selection, and Time
Selection tabs, and then click OK. The created query template is displayed in the
Template Management tree.
5.4 Modifying a Template

This procedure describes how to modify a user-defined common template.
The procedures for modifying a common template and a query template are the same. The
modifiable parameters of a user-defined common templates include: name, description,
NE type, MO type, performance objects, location group, query granularity, and effective
time.
The modifiable parameters of a query template include: target index, query object, and
query time.
Note:
The default common templates provided by the system cannot be modified.
Prerequisite
The user logging in to the NetNumen U31 system has been granted with the “Common
Steps
1. On the Template Management tab, locate the template to be modified, and then
perform either of the following operations:
l Right-click the template, and then select Modify Template.
l Click the template, and then click on the toolbar.
The Modify Common Template dialog box is displayed, see Figure 5-6.
5-8

Figure 5-6 Modify Common Template Dialog Box
2. Modify the information of the common template as needed, and then click OK.
5.5 Deleting a Template

This procedure describes how to delete a template, using the user-defined common
template as an example.
Unused user-defined common templates or query templates can be deleted from the
system. The procedures for deleting a common template or a query template are similar.
Note:
l The system–defined common templates cannot be deleted.
l A template used by any template task cannot be deleted.
Prerequisite
l The user logging in to the NetNumen U31 system has been granted with the “Common
Steps
1. On the Template Management tab, locate the common template to be deleted, and
5-9

Note:
To delete multiple user-defined common templates, press and hold the Ctrl or Shift
key while selecting these common templates.
l Right-click the template, and then click Delete Template.

l Click the template, and then click on the toolbar.
A confirmation box is displayed.
2. Click OK.
5.6 Exporting Templates to an XML File

One or multiple common templates or query templates can be exported to an XML file.
The procedure for exporting common templates is similar to that for exporting query
templates. This procedure describes how to export multiple common templates to an
XML file as an example.
Prerequisite
The user logging in to the NetNumen U31 system has been granted with the “Common
Steps
1. On the Template Management tab, select the common templates to be exported, and
then perform either of the following steps:
l Right-click any selected common template, and then select Export Selected
Template(s) or Export All Templates.
l Click the down arrow of the button on the toolbar, and select Export Selected
Template(s) or Export All Templates from the drop-down list.
The Export Template dialog box is displayed, see Figure 5-7.
5-10

Figure 5-7 Export Template Dialog Box
2. Set the file name and saving path, and then click Save. A pop-up confirmation box is
displayed.
3. Click OK. An XML file containing the information of the exported common templates
is created in the selected directory.
5.7 Importing Templates from an XML File

This procedure describes how to import templates from an XML file to the system, using
the common template as an example.
Note:
The file for importing templates must meet the format required by the system. To achieve
this, users can export a template first, and then edit the exported file.
Prerequisite
l The user logging in to the NetNumen U31 system has been granted with the template
operation permission.
l The XML file containing the information of templates to be imported has been
prepared.
l The template information in the XML file meets the format required by the system.
5-11

Steps
1. On the Template Management tab, perform either of the following operations:
l Right-click any existing common template, and then click Import Template.
The Import Template dialog box is displayed.
2. Select the directory where the XML file is saved, select the XML file to be imported,
and then click Open.
Another Import Template dialog box is displayed, listing all common templates defined
in the selected XML file, see Figure 5-8.
Figure 5-8 Import Template Dialog Box
3. Click Overwrite or Append.

l If Overwrite is selected, the system will overwrite an existing common template
when an imported template has the same ID and name with this existing template.
l If Append is selected, an error message will be displayed when the system
detects that a template to be imported has the same ID and name with an existing
template.
4. Select the common templates to be imported, and then click OK. A message
confirming the successful import is displayed.
5. Click OK. The imported common templates are displayed on the Template
Management tab.
5-12

Chapter 6
Template Task Management
Table of Contents
Overview ....................................................................................................................6-1
Creating a Query Template Task.................................................................................6-3
Creating a Common Template Task............................................................................6-8
Modifying a Template Task .......................................................................................6-13
Activating a Template Task .......................................................................................6-13
Suspending a Template Task....................................................................................6-14
Managing the Running Result of a Template Task ....................................................6-14
Ending a Template Task Ahead of Schedule.............................................................6-16
Deleting a Template Task .........................................................................................6-16
Cancelling the Execution of a Template Task in Waiting Status.................................6-17
6.1 Overview
A common template or query template can be used to schedule a performance data
query task (template task). The system automatically starts performance data query in
accordance with the settings in the template task and saves the query results on the
server.
Users can view the execution result of a predefined template task to get the required
performance data. By using a template task, users do not need to set every query condition
because the common template or query template in the template task already defines some
query conditions, such as query granularity, NE location, and MO location.
Note:
The system only supports concurrent running of a few template tasks due to its capability
limits. Different run times are recommended if multiple template tasks are scheduled in
the system.
The following describes the common operation flow of a template task:
1. Create a common or query template.

2. Create a common or query template task.
3. Activate the template task.
4. If it is required to end the template task ahead of time, complete the template task.
6-1

5. The template task execution can be canceled as required, and the task can be
automatically executed at the next specified time point.
6.1.1 Opening the Template Task Management Tab

This procedure describes how to open the Template Task Management tab in the client
window.
Steps
1. To open the Template Task Management tab, perform either of the following
operations:
l Select Performance > Template Task Management from the menu.
l Select Statistics > Performance Statistics > Template Task Management from
the menu.
The Template Task Management tab is displayed, see Figure 6-1.
Figure 6-1 Template Task Management Tab
1. Template task pane 2. Task result pane
The template task pane on the upper part of the Template Task Management tab
lists all created template tasks in the system. After a task template is selected in
the template task pane, the task result pane on the lower part of the Template Task
Management tab lists the execution results of the task if the task has been run.
6-2

Chapter 6 Template Task Management
6.1.2 Template Task Toolbars

On the upper part of the template task pane, there is a toolbar, which provides shortcut
buttons for template task management. For a description of these toolbar buttons, refer to
Table 6-1.
Table 6-1 Toolbar Buttons for Template Task Management
Button Function
Creates a new template task based on a query template.
Creates a new template task based on a common template.
Modifies a template task.
Displays the information of a template task.
Deletes a template task.
Queries performance data in accordance with the selected template

task.
Activates a template task.
Suspends a template task.
Ends a template task.
Refreshes template tasks.
On the upper part of the task result pane is a toolbar, which provides buttons for exporting
or running a template task. For the description of these toolbar buttons, refer to Table 6-2.
Table 6-2 Toolbar Buttons for Managing Template Task Results
Button Function
Exports task results.
Runs a template task again.
6.2 Creating a Query Template Task

This procedure describes how to create a query template task.
6-3

Context
The system can periodically query performance data in accordance with the parameter
setting of a query template task, and generate a query result file.
A query template already defines the performance objects to be queried and the query
time. For a template task based on the query template, the following task parameters must
be set: start time, end time, running period, and the type of result files to be generated.
In addition, the result files generated after the system runs the template task can be
transferred to and saved on a File Transfer Protocol (FTP) server, or sent to relevant
personnel by using E-mail. To use these functions, special settings need to be
implemented during the creation of the template task.
Note:
Before using the E-mail notification and file transfer functions, ensure that the parameters
of the E-mail server and FTP server have been properly set in the NetNumen
Configuration Center of the NetNumen U31 system. For how to set the necessary
parameters for E-mail and FTP functions, refer to the NetNumen U31 R18 Unified
Element Management System Fault Management Operation Guide.
Prerequisite
The query template used for creating a template task is available in the system.
Steps
1. On the Template Task Management tab, perform either of the following operations:
l Click on the toolbar of the template task pane.
l Right-click any existing template task, and then select Add Query Template Task.
The Add Query Template Task dialog box is displayed, see Figure 6-2.
6-4

Figure 6-2 Add Query Template Task Dialog Box
2. Enter a name for the new template task in the Task Name box.
Note:
After the query template is selected, users can click Modify... to modify the query
conditions of the query template in the displayed dialog box as needed.
3. Select the query template to be used from the Template Name drop-down list.
4. Select Start Time and End Time, and then set the start time and end time in the
corresponding drop-down lists.
5. Select an initial status for the new query template task, Activated or Suspended.
6. Select a file type for saving the task results on the server.
Note:
The supported file types might vary with different versions.
6-5

7. Select an execution period for the new template task under Task execution plan.
l If By day is selected, the system will execute the template task at 5:00 A.M. every
day during the specified period to query the performance data of the previous day.
l If By week is selected, the system will run the template task at 5:00 A.M. on the
first day of every week during the specified period to query the performance data
of the previous week.
l If By month is selected, the system will run the template task at 5:00 A.M. on the
first day of every month during the specified period to query the performance data
of the previous month.
Note:
A customized running period is recommended because the system only supports

concurrent running of a few template tasks. If multiple template tasks are created
in the system, it is required to set different run times for these tasks.
l If Customize is selected, users can customize the running period for the template
task under the activated Execution time area and Query time section area, see
Figure 6-3.
Figure 6-3 Customizing the Running Cycle of a Template Task
8. (Optional) To send the information of task running results to relevant personnel by

using E-mail, and/or transfer the result files to an FTP server, click Forwarding Setup,
and then set the necessary parameters on the Email Forward tab and/or FTP Push
tab in the Forwarding Setup dialog box, see Figure 6-4 and Figure 6-5.
6-6

Figure 6-4 Forwarding Setup Dialog Box – Email Forward Tab
Figure 6-5 Forwarding Setup Dialog Box – FTP Push Tab
l To send the running results of the template task to related personnel by using
E-mail, select Enable on the Email Forward tab. Then enter the E-mail
addresses to which the result files shall be sent in the Email address box.
The system provides the default E-mail title and content format, which can be
modified as needed.
l To forward the result files of the template task to an FTP server, select Enable on
the FTP Push tab. Then set the following parameters.
6-7

Protocol Provides the protocols that can be used for file transfer: FTP and
Secure File Transfer Protocol (SFTP).
IP address Specifies the IP address of the FTP server.
User name Specifies the user name used to log in to the FTP server.
Password Specifies the login password of the FTP server.
Port Specifies the port No. through which the files will be transferred.
Sub folder Specifies the path where the transferred files will be saved on the
FTP server.
After specifying the FTP server information, click Test Connection to verify that
the FTP server can be successfully connected.
9. Click OK. The created query template task is displayed on the Template Task
Management tab.
6.3 Creating a Common Template Task

This procedure describes how to create a template task involving one common template.
Context
The system can periodically query performance data in accordance with the parameter
setting of a common template task, and generate a query result file.
In a common template, some query conditions are preset, such as NE type, MO type,
and POs for performance data query. One or multiple common templates can be used in
a template task. For a template task based on common template, additional parameters
shall be set, including NE location, MO location, query time, start time, end time, task
schedule and the type of result files.
Prerequisite
The common template to be used for creating a template task is available in the system.
Steps
1. On the Template Task Management tab, perform either of the following operations:
l Right-click any existing template task, and then click Add Common Template
Task.
The Add Common Template Task dialog box is displayed with three tabs: Basic
Information, Location Information, and Time Information. By default, the Basic
Information tab is displayed, see Figure 6-6.
6-8

Figure 6-6 Add Common Template Task Dialog Box (Basic Information Tab)
2. On the Basic Information tab, set the basic information for the new template task:
a. Enter a name for the task in the Task name box.
Note:
Multiple common templates can be selected for a template task.
b. Select the common template to be used from the Template name drop-down list.
c. Select Start time and End time, and then set the start time and end time in the
corresponding drop-down lists as needed.
d. Select an initial status for the template task, Activated or Suspended.
6-9

Note:
If XLS is selected, the Format template check box is activated. Users can select
Format template and click the Select Format Template button to select a format
template in the displayed Open dialog box. Then the task results will be saved in
XLS files in accordance with the selected format template after the task is run.
For more information about the format template, refer to 11.1 Excel Template.
By default, the exported file has no title. To add a title to the exported file, select
the Contains the title check box.
e. Select a file type for saving the task results on the server.
Note:
A customized running period is recommended because the system only supports
concurrent running of a few template tasks. If multiple template tasks are created
in the system, uses must set different run times for these tasks.
f. Select a running cycle for the new template task under Task execution plan: By
day, By week, By month, or Customize.
If Customize is selected, users can customize the running cycle for the template
task under the activated Execution time area and Query time section area.
Note:
For the detailed instructions of execution plan settings, refer to 6.2 Creating a
Query Template Task.
g. To forward the information of task results to related personnel via E-mail, and/or
transfer the task result files to an FTP server, click the Forwarding Setup button
and then set the necessary parameters in the displayed Forwarding Setup dialog
box.
3. Select the Location Information tab. The location parameters are displayed, see
Figure 6-7.
6-10

Figure 6-7 Add Common Template Task Dialog Box (Location Information Tab)
Note:
The available parameters on the Location Information tab depend on the selected
common template.
4. On the Location Information tab, set the location information for the task:
Note:
If multiple common templates are selected for the template task, users must select
each common template and set the location information for it in accordance with the
following steps.
a. Select a template from the Template list.

b. Select a group mode for grouping the performance data in the query results from
the Location group list.
c. Select a location type, for example, Common location.
6-11

The following describes two location types:

l Common location: displays NE locations and MO locations. When this type
is selected, users are required to select a wildcard level, NE locations, and
MO locations.
l Topology group location: displays an NE tree. Users can select required
NEs or topology groups (created in the Topology Management window) in
the NE tree.
d. Select a wildcard level for quick selection of MOs from the Wildcard Level list.
e. Select NEs in the NE tree in the NE location pane.

f. Select MOs in the MO tree in the MO location pane.
5. Select the Time Information tab. The Time Information tab is displayed, see Figure
6-8.
Figure 6-8 Create Common Template Task (Time Information Tab)
6. On the Time Information tab, set the schedule information of the task.
a. Select a granularity by clicking the corresponding option button in the Query
granularity area.
b. Set the effective date weekly or monthly, and select specific days in the Effective
date area.
6-12

The highlighted dates are effective date when the task shall be performed. Click
a date to select or deselect it.
c. Set the effective time period(s) when the task shall be performed in the Effective
time area.
The period from 00:00:00 to 24:00:00 is set by default, which indicates the task is
effective for the entire day. To set another period, delete the default setting, set
the new period and click Add.
7. Click OK. The created common template task is displayed on the Template Task
Management tab.
6.4 Modifying a Template Task

This procedure describes how to modify a template task on the Template Task
Management tab.
Prerequisite
The template task to be modified is suspended.
Steps
1. On the Template Task Management tab, locate the template task to be modified, and
l Click the template task, and then click on the toolbar.
l Right-click the template task, and then click Modify Template Task.
The Modify Template Task dialog box is displayed.
2. Modify the template task parameters as needed.
3. Click OK.
6.5 Activating a Template Task

If a template task is suspended, the system will not run this task to query required
performance data. This procedure describes how to activate a suspended template task.
Prerequisite
The template task to be activated is suspended.
Steps
1. On the Template Task Management tab, locate the template task to be activated, and
6-13

Note:
To activate multiple template tasks, press and hold the Ctrl or Shift key while selecting
these template tasks.

l Right-click the template task, and then click Activate Template Task.
The status of the template task changes from Suspended to Activated.
6.6 Suspending a Template Task

This procedure describes how to suspend an activated template task.
Prerequisite
The template task to be suspended is activated.
Steps
1. On the Template Task Management tab, locate the template task to be suspended,
and then perform either of the following operations:
Note:
To suspend multiple template tasks, press and hold the Ctrl or Shift key while selecting

l Right-click the template task, and then select Suspend Template Task.
The status of the template task changes from Activated to Suspended.

6.7 Managing the Running Result of a Template Task

The system generates a query result file and saves the file on the server each time the
template task is run. Time stamps are used to distinguish query result files generated for
the same template task.
6-14

If an E-mail forwarding rule and/or FTP transferring rule is set, the system will send the
information of the result file to relevant personnel, and/or transfer the result file to the
specified FTP server.
The following management operations can be performed on the running result files of a
template task:
l View all running result files of the template task.
l Copy a result file from the server to a local client.
l Re-query and refresh the performance data in a result file.
This procedure describes how to perform these management operations.
Prerequisite
The template task has been run in the system.
Steps
1. To view all running result files of the template task, click the template task in the
template task pane. The information of all generated result files is displayed in the
task result pane on the lower part of the Template Task Management tab, see Figure
6-9.
Figure 6-9 Execution Result of a Template Task
2. To copy a result file from the server to a local client, perform the following operations:
a. click the result file in the task result pane, and then click on the toolbar. The
Save dialog box is displayed.
b. Select the directory where the file is to be saved, and then click Save. The saved
result file is displayed in the selected directory on the client.
6-15

3. To re-query and refresh the performance data in a result file, run the template task
again to query the required performance data by clicking the result file row and then
clicking on the toolbar.
After the system successfully queries the required performance data, the result file is
refreshed and the file name changes with the time stamp updated.
6.8 Ending a Template Task Ahead of Schedule

An activated or suspended template task can be forcibly ended before the preset end
time of the task. After a template task is ended ahead of schedule, its status changes
to completed, and the system will no longer execute this template task even though the
end time of the task is not reached. A template task ended ahead of schedule cannot be
activated again.
This procedure describes how to end a template task ahead of schedule.
Steps
1. On the Template Task Management tab, locate the template task to be ended, and
Note:
To end multiple template tasks, press and hold the Ctrl or Shilf key while selecting

l Right-click the template task, and then click Finish Template Task.
2. Click OK. The status of the template task changes to Finished.
6.9 Deleting a Template Task

This procedure describes how to delete a suspended template task.
Prerequisite
The template task to be deleted is suspended.
6-16

Steps
1. On the Template Task Management tab, locate the template task to be deleted, and
Note:
To delete multiple template tasks, press and hold the Ctrl or Shift key while selecting

l Right-click the template task, and then click Delete Template Task.
2. Click OK. The deleted template task is removed from the Template Task Management
tab.
6.10 Cancelling the Execution of a Template Task in

Waiting Status
When a scheduled time is reached for executing a particular template task, if some other
tasks are still being executed in the task queue on the server, the template task status is
Waiting, indicating that the template task is waiting in the task queue. Users can cancel
the execution for this time. When the next scheduled time is reached, the template task
will be automatically executed.
This procedure describes how to cancel the execution of a template task that is in Waiting
status.
Prerequisite
At least one template task is available in the system.
Steps
1. Click the Template Task Management tab in the left navigation pane. All template
tasks are displayed in the right pane.
2. Right-click a template task that is in Waiting status, and select Cancel Waiting.
6-17

6-18

Chapter 7
Performance Data Query
Table of Contents
Overview ....................................................................................................................7-1
Querying Performance Data .......................................................................................7-1
Filtering and Rendering Performance Data by Index or Counter ...............................7-13
Managing Query Results of Performance Data.........................................................7-20
7.1 Overview
The NetNumen U31 system collects performance data from managed Network Elements
(NEs) in accordance with created measurement tasks, and then stores the collected
performance data in its database. Users can query specific performance data from the
database.
The query results of performance data can be displayed in table or different chart formats.
Users can set filtering and rendering rules to customize the display of performance data
in the query results. In addition, the query results can be exported and saved as a TXT,
HTM, PDF, XLS, or CSV file, and printed as a performance data report.
7.2 Querying Performance Data
Note:
Performance data can be successfully queried from the database of the NetNumen U31
system only when the following conditions are met:
l Appropriate measurement task(s) have been created and run to collect the
performance data from the corresponding NEs.
l The collected performance data has been successfully stored in the database.
The following methods can be used to query performance data in the NetNumen U31
system:
l Querying performance data by customized conditions

l Querying performance data by measurement task
l Querying performance data by query template
l Querying performance data by common template
7-1

7.2.1 Querying Performance Data by Customized Conditions

This procedure describes how to set conditions to query specific performance data from
the database of the NetNumen U31 system.
When a conflict exists between query conditions, for example, a selected counter or index
does not support the selected location group, the system will prompt the conflict cause
and continue the query operation in accordance with the query conditions. However, the
query results will not contain the data of this counter or index. Users are recommended to
reset the query conditions before querying performance data in the occurrence of a query
condition conflict.
The system cannot query too much data from the database at a time due to the processing
capability limit. The following are the limits for selecting performance objects.
l A maximum of 300 indexes and/or counters can be selected in the Measure Object
Type tree. For performance data query from Code Division Multiple Access (CDMA)
NEs, the number is 40.
l A maximum of 100 NE locations can be selected on the NE tree in the NE Location
pane.
l A maximum of 200 Measured Object (MO) locations can be selected in the MO
Location pane.
Steps
1. In the client window, perform one of the following operations:
Note:
To query performance data of a specific NE, users can expand the NE tree on the
NE Tree tab in the navigation pane to locate the NE, click the NE node on the NE
tree and then perform one of the following operations, or right-click the NE node and
then select History Performance Data Query from the shortcut menu. The History
Performance Data Query dialog box will be displayed with this NE selected on the
Object Selection tab.
l Select Performance > History Performance Data Query from the menu.
l Select Statistics > Performance Statistics > History Performance Data Query
from the menu.
The Performance Data Query dialog box is displayed with three tabs:
Indices/Counters Selection, Object Selection, and Time Selection. By default,
the Indices/Counters Selection tab is displayed, see Figure 7-1.
7-2

Chapter 7 Performance Data Query
Figure 7-1 History Performance Data Query Dialog Box (Indices/Counters Selection
Tab)
2. On the Indices/Counters Selection tab, select the performance indexes to be

queried.
a. Select an NE type from the NE type drop-down list, for locating the indexes and
counters to be queried.
If multiple NE types are selected, the available MO type options in the MO type
drop-down list include the collection of MOs related to all NE types.
If the selected NE type is multi-mode (for example, Multi-mode Controller (MO)),
and the selected MO type supports multi-mode (for example, AAL2 Ap(V4)), the
Mode filter drop-down list box is displayed.
b. Select an MO type from the MO type drop-down list for locating the indexes and
counters to be queried.
c. (Optional) Select the Calculate data integrity check box.
Note:
If CDMA NEs are selected for performance data query, the Calculate data
integrity check box is not available.
After an NE type is selected, the Calculate data integrity check box is displayed
above the NE type drop-down list. Users can select this check box to know the
7-3

integrity of queried performance data, meaning the proportion of actually-obtained

performance data in the query results to the required performance data.
For example, select RNCV309 from the NE type drop-down list box, and select
UTRAN Cell (WCDMA) from the MO type drop-down list. If an RNC controls 100
cells and the system only successfully obtains the performance data of 60 cells
after querying the database, the data integrity is displayed as 60%.
d. In the MO Type tree, select the counters and indexes.
e. Set the filtering and rendering rules for the indexes and counters in the right
Selected indices/counters pane as needed.
Note:
The Logic, TopN, and Busy Hour buttons are not available in Selected
Indices/Counters pane when CDMA NEs are selected for performance data
query, meaning that no filtering and rendering rules can be set for performance
data of CDMA NEs in the NetNumen U31 system.
For the details of how to set a filtering and rendering rule for an index or counter,
refer to 7.3 Filtering and Rendering Performance Data by Index or Counter.
3. Select the Object Selection tab. The Object Selection tab is displayed, see Figure
7-2.
Figure 7-2 History Performance Data Query Dialog Box (Object Selection Tab)
7-4

4. Set parameters on the Object Selection tab. For a description of the Object
Selection tab, refer to Table 7-1.
Table 7-1 Object Selection Tab Parameter Descriptions
Location group Specifies the method for grouping queried performance data. The
available options include:
l Group by “Office” object
l Group by “RNS Subnetwork” object
l Group by “RNC Managed NE” object
l Group by “Office” object
PLMN For the UMTS products, if the specified MO type is RNC logical cell,
The PLMN check box will be displayed in the Location group list.
For a shared network, if this check box is selected, the query result will
be grouped by both the group method specified in the Location group
and the telecom operator.
Location type Location type. The options are Common location, Group location,
and Topology group location.
l Common location: When this type is selected, users are required
to select a wildcard level, NE locations, and MO locations.
l Group location: This location type is only available when the
same NE type and MO type are selected as some MO groups
(previously-created on the Group Management tab in the
navigation pane). When this type is selected, users are required to
select one or multiple groups in the group tree.
l Topology group location: Users can select required NEs or
topology groups (previously-created in the Topology Management
window) in the NE tree.
Wildcard level Select a wildcard level from the drop-down list.

It is recommended to select All. The specified performance data of all
NEs in the whole network is queried, and there is no need to set the
NE location and MO location.
NE location Select the NEs whose performance data is to be queried in the NE tree.
A maximum of 100 NE locations can be selected.
MO location Select the MOs whose performance data is to be queried in the MO

Tree.
A maximum of 200 MO locations can be selected.
5. Select the Time Selection tab. The Time Selection tab is displayed.
7-5

Figure 7-3 Performance Data Query (Time Selection Tab)
Note:
In a system with NetNumen U31 clients and managed NEs distributed in different time
zones, the following two additional options are displayed on the Time Selection tab:
l NE Wall-Time: If this option is selected, the system will convert the time
period entered on the Time Selection tab to the NE time zone, query required
performance data, and display the query results by time zone of the managed
NEs.
l Client Time Zone (GMT+08:00): If this option is selected, the system will convert
the time period entered on the Time Selection tab to the client time zone, query
required performance data, and display the query results by time zone of the local
client.
6. On the Time Selection tab, set a query granularity and the time period.
a. Select a granularity for grouping the queried performance data under Query
granularity.
In addition to five fixed query granularities (15 minutes, 30 minutes, one hour, one
day, one week, and one month), the system supports the customization of three
kinds of query granularities. These are:
l All the customized hours group: If this query granularity is selected, the
system will summarize the queried performance data of each collection group
7-6

during the hour-based period from the start time to the end time into one
record.
For example, select Group by "CPU" object from the Location group list on
the Object Selection tab, select All the customized hours group and then
Customize under Time settings on the Time Selection tab, set the start
time to 2011-01-17 01:00:00, and set the end time to 2011-01-18 00:00:00.
The system will query the performance data during the customized 23 hours
and summarize the performance data of each CPU during this period into one
record.
l All the customized days group: If this query granularity is selected, the
system will summarize the queried performance data of each collection group
during the day-based period from the start time to the end time into one record.
For example, select Group by "CPU" object from the Location group list
on the Object Selection tab, select All the customized days group and
then select Customize under Time settings on the Time Selection tab, set
the start time to 2011-01-14 00:00:00, and set the end time to 2011-01-18
00:00:00. The system will query the performance data during the customized
four days and summarize the performance data of each CPU during this
period into one record.
l 24-hour group: This query granularity is only applicable for querying the
performance data of only one index or counter.
If this query granularity is selected, the system will summarize the queried
performance data of each collection group during the customized period by
hour.
For example, select this query granularity to query the data of an index from
2011-01-14 00:00:00 to 2011-01-18 00:00:00. After the system successfully
obtains the performance data, it displays the performance data of each object
during these four days in 24 columns, each indicating the data in a hour, for
example, from 0:00 to 1:00, from 1:00 to 2:00, ..., from 23:00 to 24:00.
b. Set the query period under Time settings: a day, a week, a month, a holiday, or
a customized period.
c. Set the effective date weekly or monthly, and select specific days under Effective
date.
The highlighted dates are effective date when the task shall be performed. Click
a date to select or deselect it.
d. Set the effective time period(s) when the task shall be performed under Effective
time.
The period from 00:00:00 to 24:00:00 is set by default, which indicates the task is
effective for the entire day. To set another period, delete the default setting, set
the new period and click Add.
7-7

7. (Optional) To save the query conditions as a query template, perform the following
operations:
a. Click the Save as Query Template button. The Add Template dialog box is
displayed, see Figure 7-4.
Figure 7-4 Add Template Dialog Box
b. Enter a name for the template, select an operation mode, select an access type,
and then click OK.
8. Click OK in the History Performance Data Query dialog box. A new tab is displayed
in the client window, displaying the query results in table format.
Note:
After the setting of query conditions in the Performance Data Query dialog box is
completed, the query conditions can be saved as a query template as follows:
The following are four examples of the query results based on different query
granularities.
l Query granularity: 1 hour
7-8

Figure 7-5 Query Results of Performance Data (1)
l Query granularity: All the customized hours group
l Query granularity: All the customized days group
l Query granularity: 24-hours group
7-9

7.2.2 Querying Performance Data by Measurement Task

In the NetNumen U31 system, measurement tasks are created to collect the values of
specific counters from some managed NEs. Users can use an existing measurement task
for quick query of related performance data.
This procedure describes how to use an existing measurement task to query performance
data. For the instructions for setting specific parameters, refer to 7.2.1 Querying
Performance Data by Customized Conditions.
Steps
1. Select Performance > Measurement Task Management from the menu. The
Measurement Task Management tab is displayed.
2. Locate the measurement task to be used, right-click the measurement task, and then
select Query PM Data by Task. The History Performance Data Query dialog box is
displayed with three tabs: Indices Selection, Object Selection, and Time Selection.
By default, the Indices Selection tab is displayed, see Figure 7-9.
7-10

Figure 7-9 Using a Measurement Task for Performance Data Query (1)
Note:
The system can only query a maximum of 300 counters and/or indexes.
3. On the Indices Selection tab, cancel the selection of the counters not required, and
select the indexes to be queried as needed.
4. Select the Object Selection tab. The Object Selection tab is displayed.
5. Re-select the NEs and MOs as needed.
6. Select the Time Selection tab. The Time Selection tab is displayed.
Note:
If the settings on the Time Selection tab are not changed, the system will query
the performance data at the original granularity (15 minutes) during the period from
00:00:00 on the previous day to the current time.
7. Select a query granularity and set the time period during which the performance data
is required, see Figure 7-10.
7-11

Figure 7-10 Using a Measurement Task for Performance Data Query (2)
8. Click OK. A new tab is displayed in the client window, displaying the query results in
table format.
7.2.3 Querying Performance Data by Common Template

A common template can be used to query performance data from specific POs, which are
preset in the common template.
This procedure describes how to use a common template to query performance data.
Prerequisite
l A common template is created.
l The performance data to be queried has been collected by appropriate measurement
task(s) and stored in the database.
Steps
1. Select Performance > Template Management from the menu. The Template
Management tab is displayed.
2. Locate the common template to be used, and then perform either of the following
operations:
l Click the common template, and then click on the toolbar.
l Right-click the common template, and then select Query by Template.
The History Performance Data Query dialog box is displayed.
7-12

Note:
A common template only presets some conditions, such as NE type, MO type,
PO, query granularity, and valid period. Users need to set the NE location MO
location for the performance data query. For operation details, refer to 7.2.1 Querying
Performance Data by Customized Conditions.
3. Modify the query conditions as needed, and specify the NE location and MO location.
4. Click OK. A new tab is displayed in the client window, displaying the query results in
table format.
7.2.4 Querying Performance Data by Query Template

This procedure describes how to use a query template for querying performance data .
Prerequisite
l A query template is created.
l The performance data to be queried has been collected by appropriate measurement
task(s) and stored in the database of the system.
Steps
1. In the Performance Management window, click the Template Tree tab of the
navigation pane. The Template Management tab is displayed in the right pane.
2. Locate the query template to be used, right-click the template, and the select Query
by Template.
l If the operation mode of the query template is Pop-up window, users can modify
the query conditions in the displayed the History Performance Data Query dialog
box, and click OK to execute the query template. For operation details, refer to
7.2.1 Querying Performance Data by Customized Conditions.
l If the operation mode of the query template is Direct execution, the system
executes the query template directly.
7.3 Filtering and Rendering Performance Data by Index

or Counter
In the NetNumen U31 system, users can specify a filtering rule to determine the display
of performance data (indexes and counters) in the query results and a rendering rule to
highlight specific performance data. These rules can be set when a user:
7-13

l Creates a common template.

l Creates a query template.
l Sets query conditions for performance data query.
One of the following three filtering rules can be used according to the characteristics of
indexes and/or counters to be displayed in the query results.
l Performance data filtering based on logical And/Or operation
After a filtering rule based on logical And/Or operation is set, the system will display
the query results of counters and indexes only when the result of logical And operation
of each index and counter is true, or the result of logical Or operation of any index or
counter is true.
l Performance data filtering based on Top N operation
After a filtering rule based on Top N operation is set, the system will only display the
Top N values of indexes or counters in the query results.
l Performance data filtering based on busy hours
After a filtering rule based on busy hours is set, the system will only display the
maximum or minimum values of indexes and counters collected during the busy
hours in the query results.
7.3.1 Prerequisites
Before filtering and rendering performance data by index or counter, users must select the
required counters and indexes in one of the following dialog boxes.
l New Common Template
Figure 7-11 New Common Template Dialog Box with Counters and Indexes
Selected
7-14

Figure 7-12 History Performance Data Query Dialog Box with Counters and
Indexes Selected
7.3.2 Filtering Performance Data Based on Logical And/Or

Operation
This procedure describes how to set a rule based on logical And/Or operation in the History
Performance Data Query dialog box for filtering performance data in the query results.
Steps
1. In the History Performance Data Query dialog box, click the Logic button under
Selected indices/counters. The Logical Filtering/Rendering dialog box is
displayed.
2. Select a filter type: And or Or.

3. Set the filtering conditions for each index or counter to be set.
a. Click the corresponding cell on the Filter Operator column, and then select an
operator from the drop-down list.
b. Enter a value in the corresponding cell on the Filter Value column.
Figure 7-13 shows an example of the Logic Filtering/Rendering dialog box in which
the filtering condition is set for each index and counter.
7-15

Figure 7-13 Setting a Logical Filtering Rule
4. Click OK.
l If the filter type And is selected, the system will display the query results of all
counters and indexes only when the result of logical And operation of each index
and counter is true.
l If the filter type Or is selected, the system will display the query results of all
counters and indexes only as long as the result of logical Or operation of any
index or counter is true.
7.3.3 Filtering Performance Data Based on Top N Operation

This procedure describes how to set a rule based on Top N operation in the Performance
Data Query dialog box for filtering performance data in the query results.
Steps
1. In the History Performance Data Query dialog box, click the TopN button under
Selected Indices/Counters. The TopN Filtering/Rendering dialog box is displayed.
2. Select a filter type: No Group, Group by Time, or Group by Location.
This procedure describes these three filter types with an example.
If a radio network has 10 RNCs, each having 1000 cells, the radio network has 10,000
cells in total. The query results of a cell performance index or counter at the granularity
of one hour during an entire day (24 hours) may involve 240,000 records (10000*24).
If conditions are set to filter the records of the index or counter in accordance with the
7-16

Top 5 values, the system returns different query results when different filter types are
selected.
l If No Group is selected, the system will query the performance data and only
display the Top 5 values in the query results. If several values are tied for one of
the Top 5 places, the system will only select and display the first collected one.
The No Group filter type is used for analyzing the maximum or minimum values
of all performance data.
l If Group by Time is selected, the system will query the performance data and
display the Top 5 values in the query results of each hour, returning 120 (5*24)
records. The Group by Time filter type is used for analyzing the best or worst
object (for example, the best cell or worst cell) at specific time point during a
period.
l If Group by Location is selected, the system will query the performance data
and display the Top 5 values of each object during 24 hours, returning 50,000
records (5*10000). The Group by Location filter type is used for analyzing the
performance of each object at the best time or worst time during a period.
3. Set the filtering condition for the index or counter to be filtered.

a. Click the corresponding cell on the Filter Operator column, and then select Top
Max or Top Min from the drop-down list.
b. Select a value from the corresponding drop-down list box on the Filter Value
column.
Figure 7-14 shows an example of the TopN Filtering/Rendering dialog box in

which the filtering condition is set for an index.
Figure 7-14 Setting a Top N Filtering Rule
7-17

4. Click OK.
7.3.4 Filtering Performance Data Based on Busy Hour

The query results of performance data can be filtered based on a predefined busy hour.
Users can set conditions to display the maximum or minimum values during the busy hour.
Only one counter or index can be selected to define the busy hour. For example, the index
“Call Drop Ratio” is used to define the busy hour, and the filtering condition “Busy hour
max” is selected for this index. Then the busy hour is the hour during which the sum of
the index values in a cell is the maximum. In accordance with this filtering condition, the
system will filter out the values of the other indexes and counters in this busy hour and
only display the queried data in the query results. In this way, the performance data of
related indexes and counters during the busy hour can be analyzed to locate the cause of
the maximum call drop ratio.
This procedure describes how to set a rule based on busy hour in the History
Performance Data Query dialog box for filtering performance data in the query results.
Steps
1. In the History Performance Data Query dialog box, click the Busy Hour button
under Selected Indices/Counters. The Busy Hour Filtering/Rendering dialog box
is displayed.
2. Click the cell corresponding to the index to be used for defining the busy hour on the
Filter Operator column, and then select Busy hour-max or Busy hour-min from the
drop-down list, see Figure 7-15.
7-18

Figure 7-15 Setting a Busy Hour-Based Filtering Rule
3. Click OK.
7.3.5 Rendering Performance Data in the Query Results

Users can set a threshold-based rendering rule for an index or counter to determine the
background color and font color of the index values displayed on the query result tab. When
the index value is within the threshold range at a level, it will be displayed in accordance
with the preset rendering rule.
The following example describes how to set a rendering rule for an index in the Logical
Filter/Render dialog box.
Prerequisite
One of the following three dialog boxes is displayed when a filtering rule or query conditions
are set:
l Logic Filtering/Rendering dialog box

l TopN Filtering/Rendering dialog box
l Busy Hour Filtering/Rendering dialog box
Steps
1. In the Logic Filtering/Rendering dialog box, click the cell corresponding to the index
on the Rendering column. The Threshold Rendering dialog box is displayed, see
Figure 7-16.
7-19

Figure 7-16 Threshold Rendering Dialog Box
2. Select a threshold direction in accordance with the characteristics of the index: Up or

Down.
3. Select a threshold level, type a threshold value, and then select the required
background color and the font color.
For the relationships between threshold direction and threshold levels with two typical
indexes, refer to Table 7-2.
Table 7-2 Relationships Between Threshold Direction and Threshold Direction
Level Mean Ratio of CPU Usage Call Setup Success Rate Severity
(Up) (Down)
Level 1 >= 90 <= 20 Critical
Level 2 >= 80 <= 35 Major
Level 3 >= 75 <= 40 Minor
Level 4 >= 70 <= 45 Warning
4. Select Label, and then enter the label content in the corresponding box as needed to
add a label to the index values meeting the rendering conditions.
5. Click OK.
The system analyzes the query results and compares the queried value with the
threshold. If an index value is higher (Up direction) or lower (Down direction) than the
corresponding threshold, the system displays the index value in the preset font color
and shades it with the preset background color.
7.4 Managing Query Results of Performance Data

7.4.1 The Toolbar on the Query Result Tab
After successful performance data query, the query results are displayed on a new tab
in the client window. On the upper part of the query result tab, there is a toolbar, which
7-20

provides shortcut buttons for the management of the query result. For a description of
these toolbar buttons, refer to Table 7-3.
Table 7-3 Query Result Tab Toolbar Buttons
Button Function
Resets query conditions to start another performance data query.
Goes to the first page of the query results.
Goes to the previous page of the query result.
Goes to the next page of the query result.
Goes to the last page of the query result.
Goes to the specified page when the queried data is displayed on

multiple pages.
Exports the query results on the current page.
Exports all query results.
Displays the query results in chart format.
Sorts the query results in ascending or descending order of a specific

parameter.
Prints the query results.
Saves the query conditions as a query template.
Refreshes the query result.
7.4.2 Displaying Query Results in a Table

The query results of performance data are displayed on a tab in table format by default.
Users can switch the display format of performance data between table and chart.
Prerequisite
The performance data query results are displayed in chart format.
Steps
1. Click the Table tab at the bottom of the query result tab.
7-21

7.4.3 Displaying Query Results in a Chart

The query results of performance data are displayed in table format by default on a tab.
Users can switch the display format of performance data between table and chart.
This procedure describes how to switch the display format of the query results from table
to chart.
Steps
1. On the tab that shows the performance query result, click on the toolbar. The chart
settings are displayed, see Figure 7-17.
Figure 7-17 Chart Settings
2. Select the chart type, chart style, chart attribute, specify the objects and indexes, and
click Apply. The chart is displayed, see Figure 7-18.
7-22

Figure 7-18 Chart Result
7.4.4 Exporting Query Results

The query results of performance data can be exported to a TXT, HTM, PDF, XLS, or CSV
file. The system can export a maximum of 10,000 data records. If the query results have
more than 10,000 data records, the system will truncate the exceeding part when exporting
the query results.
Note:
When exporting the query results to an XLS file, users can use a predefined Excel template
to arrange the queried performance data in specific format. For the information about Excel
templates, refer to 11.1 Excel Template.
This procedure describes how to export the queried performance data to a TXT, HTM,
PDF, XLS, XLSX, PRN, or CSV file.
Prerequisite
The performance data query results are displayed on a tab in the client window.
Steps
1. Click or on the toolbar of the query result tab. The Save dialog box is displayed.
2. Select the directory where the file is to be saved.
7-23

3. Enter a name for the file.

4. Select a file type from the Files of type drop-down list.
5. Click Save. A file containing the queried performance data is displayed in the selected
directory.
7-24

Chapter 8
Performance Data Monitoring
Table of Contents
Overview ....................................................................................................................8-1
Monitoring Performance Data in Real Time ................................................................8-1
Monitoring Historical Performance Data .....................................................................8-5
8.1 Overview
The NetNumen U31 system provides two methods for monitoring performance data:
l Real-time performance data monitoring
This method is used to query near real-time performance data.

l Historical performance data monitoring
This method is used to query the values of counters and indexes related to specified
monitored location within specified period of time.
8.2 Monitoring Performance Data in Real Time

This function is used to obtain performance data in near real-time due to the feature that
the system can collect performance data at various granularities, such as 10 seconds,
30 seconds, and one minute. When the collection granularity is 10 seconds, only a small
amount of performance data can be queried at a time. The maximum number of measured
objects and counters is different for products of various wireless systems.
For common performance data query methods, the minimum optional granularity is 15
minutes. At this granularity level, the collected data has some delay, but a relatively greater
number of counters and indexes related to a greater number of MOs can be queried.
Note:
Not all counters and indexes of all MOs support the real-time monitoring. The system only
lists the supported MOs with supported counters and indexes for selection.
The CDMA Network Elements (NEs) do not support real-time performance data
monitoring.
This procedure describes how to create a task for obtaining real-time performance data.
8-1

Steps
1. In the client window, perform either of the following operations:
l Select Performance > Realtime Performance Data Monitoring from the menu.
The Add Realtime Performance Data Monitoring dialog box is displayed, see Figure
8-1.
Figure 8-1 Add Realtime Performance Data Monitoring Dialog Box
2. Select an appropriate NE type from the NE type drop-down list.

3. Select an MO type from the MO type drop-down list.
If the selected NE type is multi-mode (for example, Multi-mode Controller(MO)) and
the selected MO type supports multi-modes (for example, AAL2 PathTp(V4)), the
Mode filter drop-down list box is displayed. Users should select a wireless system
from the Mode filter list.
4. (Optional) Select Task Life Cycle, and then enter a new cycle to change the life cycle
of the task as needed (value range: 0–1440, unit: minute).
By default, the system queries 60–minute performance data.
5. Click the Select Indices/Counters... button. The Select Indices/Counters dialog

8-2

Chapter 8 Performance Data Monitoring
Figure 8-2 Select Indices/Counters Dialog Box
Note:
A maximum of 100 counters and/or indexes can be selected for real–time performance
data monitor.
6. Select the counters and/or indexes to be queried, and then click OK.
7. Click the Select Locations... button. The Select Locations dialog box is displayed,
see Figure 8-3.
Figure 8-3 Select Locations Dialog Box
8-3

Note:
A maximum of 64 MO locations can be selected for real–time performance data
monitor.
8. Select the NEs and the MOs whose performance data is to be queried, and then click
OK.
Note:
The optional granularities vary with products of different communication modes.
9. Select a granularity from the Collection granularity drop-down list. The granularity
options vary with different product types.
10. (Optional) Save the query results in a TXT or CSV file on the local client.
a. Select Save data to file, and then click . The Save dialog box is displayed
b. Select the directory where the file is to be saved, enter a name for the file, select
a file type from the Files of type drop-down list, and then click Save.
11. Click OK. The system starts querying the required performance data collected from
the time when the task is created, and then displays the query results in table format
on a new tab, see Figure 8-4.
Figure 8-4 Realtime Performance Data Monitoring Tab (Table Format)
To display the query results in line chart format, click Graphics on the upper part of
the query result tab, see Figure 8-5.
8-4

Figure 8-5 Realtime Performance Data Monitoring Tab (Chart Format)
On the query result tab, appropriate buttons on the toolbar can be used to perform the
corresponding functions. For a description of these toolbar buttons, refer to Table 8-1.
Table 8-1 Toolbar Buttons on the Realtime Performance Data Monitoring Tab
Button Function
Modifies query conditions.
Activates the suspended real-time query of performance data.
Suspends the real-time query of performance data.
Changes the performance data displayed in the line chart.
8.3 Monitoring Historical Performance Data

This procedure describes how to create a task that monitors historical performance data.
Context
This function is used to query performance data of specified indexes or counters in specific
locations during a specified period of time.
The optional query granularities include 15 minutes, 30 minutes, and one hour.
The historical performance data monitor has the following restrictions:
8-5

l A maximum of 30 performance data monitoring tasks can be executed at the same

time.
l In the index and counter navigation tree, a maximum of 300 objects can be selected.
In the NE location list, a maximum of 100 locations can be selected. In the MO list, a
maximum of 200 MOs can be selected.
l The monitoring chart supports a maximum of six curves. The number of curves =
Monitored number of indexes or counters * the number of locations. If the limit on the
number of curves is exceeded, uses need to reduce either the number of locations or
the number of indexes or counters.
l For the setting of TOP MAX5 or TOP MIN 5, a maximum of two indexes or counters
can be specified.
For the CDMA NEs, TOP MAX5 and TOP MIN 5 settings are not supported.
l The index bar chart supports a maximum of six monitoring tasks. Each monitoring
task can only monitor one index or counter and a maximum of 30 measured objects.
l The monitor start time must be later than the current time, because this function is
used to monitor the performance data at a period of time after the current time.
Prerequisite
Appropriate measurement task(s) have been created for collecting the performance data
to be monitored.
Steps
1. Select Performance > History Performance Data Monitoring from the menu.
The History Performance Data Monitoring dialog box is displayed with two tabs,
Index/Counter Selection and Location Selection. By default, the Index/Counter
Selection tab is displayed, see Figure 8-6.
8-6

Figure 8-6 History Performance Data Monitoring Dialog Box (Index/Counter

Selection Tab)
Note:
l Thresholds can be set for each index or counter in the corresponding cell on the
Threshold (up) and Threshold (down) column in the right pane. If the value of
the monitored index is greater than the threshold (up) or lower than the threshold
(down), the system will highlight this value in the monitoring results.
l If the selected NE type is multi-mode (for example, Multi–mode Controller(MO))
and the selected MO type supports multi-modes (for example, AAL2 PathTp(V4)),
the Mode Filter drop–down list box is displayed. Users should select a wireless
system from the Mode filter list.
2. On the Index/Counter Selection tab, select the NE type and MO type, and then select
the index(es) and/or counter(s) to be monitored in the Available Indices/Counter
pane. The selected indexes and/or counters are displayed in the right pane.
3. Enter a name for the performance data monitoring task in the Task Name box.
4. Select a query granularity from the Query Granularity list: 15 minutes, 30 minutes,
or 1 hour.
8-7

Note:
If the start time is not set, the system will set the monitoring task start time by using
the time when the monitoring task is created.
5. Select Start Time and End Time, and then set the start time and end time of the
monitoring period.
6. Select a display mode for the monitoring results.
For a description of three optional display modes, refer to Table 8-2.
Table 8-2 Three Display Modes of Monitoring Results
Display Mode Description Limitation
Index trend chart If this mode is selected, the system will A maximum of six curves
display the monitoring results of each index can be displayed.
or counter in a trend curve by location and
time.
Index bar chart The value of each measured object is -

displayed in a bar chart.
Realtime top 5 If this mode is selected, the system will Only two objects
monitoring chart display the monitoring results of five (counter and/or index)
positions where the monitored indexes or can be monitored at the
counters have Top 5 maximum values. same time under this
display mode.
Realtime last 5 If this mode is selected, the system will Only two objects
monitoring chart display the monitoring results of five (counter and/or index)
positions where the monitored indexes or can be monitored at the
counters have Top 5 minimum values. same time under this
display mode.
8-8

Figure 8-7 History Performance Data Monitoring Dialog Box (Location Tab)
8. Select a data grouping mode from the Location Group drop-down list box, and select
the location of NEs and MOs.
9. Click OK. A new tab is displayed in the client window, showing the monitoring results
based on the specified granularity till the end time of the monitoring task is reached.
Figure 8-8 shows an example of the monitoring tab when the display mode Index
trend chart is selected.
Figure 8-8 Monitoring Results of Performance Data
8-9

8-10

Chapter 9
Performance Data Integrity
Report
Table of Contents
Overview ....................................................................................................................9-1
Verifying the Integrity of Performance Data.................................................................9-2
Exporting the Integrity Report to a File........................................................................9-7
Re-Collecting Performance Data of CDMA NEs .........................................................9-7
9.1 Overview
The integrity of collected performance data is the base that ensures data accuracy in the
query, statistics, analysis and report of performance data.
NetNumen U31 collects performance data in accordance with the conditions specified in
created measurement tasks and stores the collected performance data in its database
when the connections between the NetNumen U31 server and the corresponding
Operation & Maintenance Modules (OMMs), which are operating properly, are normal.
If the connection between an OMM and the server is interrupted, or a Network Element
(NE) agent is not started, the NetNumen U31 server will fail to collect performance data
from the NE(s) managed by the NE agent. The collection failure impairs the integrity of
performance data.
NetNumen U31 provides the function of performance data integrity report as an assistant
for verifying the integrity of collected performance data. By using this function, users can
verify the integrity of performance data of each measurement type stored in the database to
locate the period(s) in which some performance data is absent. If some performance data
is detected absent in the database, a re-collection process can be initiated for collecting
the performance data and storing the collected data in the database.
The following gives a general flow for verifying performance data integrity.
1. Create measurement task(s) for collecting performance data.
2. Verify the integrity of collected performance data.
3. If some performance data is missing, locate the cause ruining the performance data
integrity.
4. Re-collect the missing performance data.
5. Verify the integrity of performance data again.
The performance data of Code Division Multiple Access (CDMA) NEs is stored in their
OMMs instead of the database of the NetNumen U31 system. The NetNumen U31
9-1

server periodically obtains performance data from the OMMs and generates performance
data files that can be forwarded to an upper-layer network management system through
FTP. If the system fails to generate some required performance data files due to missing
performance data, the performance data re-collection function can be used to obtain the
missing performance data from the OMMs.
9.2 Verifying the Integrity of Performance Data

This procedure describes how to verify the integrity of performance data collected from
specific measured objects.
Prerequisite
l Appropriate measurement task(s) have been created and run to collect the
performance data from the corresponding NEs.
l The collected performance data has been successfully stored in the database.
l The NetNumen U31 system is properly connected with the target OMM .
Steps
1. Select Performance > Data Integrity Query from the menu. The Add Data Integrity
Query dialog box is displayed with three tabs: Object Selection, Location Selection,
and Time Selection. By default, the Object Selection tab is displayed, see Figure
9-1.
9-2

Chapter 9 Performance Data Integrity Report
Figure 9-1 Add Data Integrity Query Dialog Box (Object Selection Tab)
Note:
If the selected NE type is multi-mode (for example, Multi-mode Controller(MO)) and
the selected MO type supports multi-modes (for example, AAL2 PathTp(V4)), the
Mode filter drop-down list box is displayed. Users should select a wireless system
from the Mode filter list.
2. On the Object Selection tab, select the NE type and the MO type, and then select the
PO(s) to be checked.
3. Select the Location Selection tab. The Location Selection tab is displayed, see
Figure 9-2.
9-3

Figure 9-2 Add Data Integrity Query Dialog Box (Location Selection Tab)
Note:
l When Wildcard level is NE, a maximum of 100 NE locations can be selected.
l When Wildcard level is a specific measured object, a maximum of 50 NE
locations can be selected because only the MO trees of 50 NEs can be loaded
in the system.
l A maximum of 200 MO locations can be selected.
4. Select a wildcard level, and then select the NE(s) and MO(s).
5. Select the Time Selection tab. The Time Selection tab is displayed, see Figure 9-3.
9-4

Figure 9-3 Add Data Integrity Query (Time Selection Tab)
Note:
Only Original Table is available in the Query Data Source drop-down list because
the system only supports the integrity verification of raw performance data collected
from NEs.
6. Set the period during which the performance data is to be checked.

7. Click OK. A Data Integrity Query tab is displayed in the client window, displaying the
integrity of the selected POs, see Figure 9-4.
9-5

Figure 9-4 Data Integrity Query Tab
On the Data Integrity Query tab, the Integrity Status column indicates the
performance data integrity.
l “Have Data” indicates that the performance data at each collection point (every
15 minutes by default) during the query period is available.
l “No Data” indicates that no performance data at each collection point is queried.
If the query period is a day and the system succeeded to query the performance data at
collection points during a period (00:00:00 to 11:00:00) but failed to query performance
data at collection points during another period (11:00:00 to 00:00:00), the integrity
query results will be displayed on two rows, with the integrity status as “Have Data” on
one row and “No Data” on the other.
Users can perform the operations based on the data integrity results by using the
toolbar buttons on the Data Integrity Query tab. For a description of these toolbar
buttons, refer to Table 9-1.
Table 9-1 Data Integrity Query Tab Toolbar Buttons
Button Function
Sets conditions to verify the integrity of other performance data.
Changes the current conditions to verify the integrity of performance

data again.
Refreshes the data integrity report on the tab.
Sets conditions to re-collect specific performance data.
9-6

Button Function
Re-collects all the missing performance data based on the verification

results. This button is activated only when a row indicating “No Data”
is selected.
Exports the verification results of performance data integrity as a report.
Prints the verification results of performance data integrity.
9.3 Exporting the Integrity Report to a File

The integrity report of performance data can be exported to an XML, TXT, HTM, PDF, CSV,
or XLS file.
This procedure describes how to export an integrity report of performance data to a file.
Prerequisite
The verification results of performance data integrity is displayed on the Data Integrity
Query tab.
Steps
1. On the Data Integrity Query tab, click on the toolbar. The Save dialog box is
displayed.
2. Select the directory where the report file is to be saved, enter a name for the file, and
then select a file type from the Files of type drop-down list.
3. Click Save. The performance data integrity report is displayed in the selected directory.
9.4 Re-Collecting Performance Data of CDMA NEs

The collection of performance data of CDMA products may miss the data of some
granularities, and the automatic re-collection may be delayed. This procedure describes
how to re-collect the missing performance data of CDMA NEs.
The principle of CDMA performance data re-collection is described as follows:
1. Scan the performance data files existing in the NetNumen U31 system, and compare
the existing files with the list of required performance data files, and estimate the
missing files.
2. Collect the missing performance data files.
9-7

Prerequisite
l The CDMA product has been selected during the installation of the NetNumen U31
system.
l The FTP function is enabled on the target OMM.
l The target OMM supports data collection through FTP.
l The NetNumen U31 communicates properly with the target OMM.
l The current user of the NetNumen U31 system is granted with the data re-collection
permission.
Steps
1. On the menu bar, select Performance > CDMA Product > FTP Performance Data
Re-collection. The FTP Performance Data Re-collection dialog box is displayed,
see Figure 9-5.
Figure 9-5 FTP Performance Data Re-collection Dialog Box
2. Click Select. The Select OMM Node dialog box is displayed, see Figure 9-6.
9-8

Figure 9-6 Select OMM Node Dialog Box
The Unavailable OMM node area displays all the OMM nodes that do not support
manual re-collection of performance data, and the corresponding reasons, such as
the OMM version too low.
3. Add the target OMM nodes in the right box, and click OK. The FTP Performance Data
Re-collection dialog box is displayed.
4. Set the start time and end time for scanning files in the Start time box and End time
box.
Granularity (min) defines the performance data generation period. The value is
defined by the system and cannot be modified by the user.
5. Click Scan to start scanning existing performance data files.

After the scanning process is completed, the missing performance data files are
displayed in Waiting to re-collect status. See Figure 9-7.
9-9

Figure 9-7 Missing Data Files
6. Click Re-collect. The system starts collecting data and initiates scheduled scanning
program to check whether the target file is obtained. The target files are in
Re-collecting status.
During the re-collection process, click Refresh. The latest data collection status is
displayed.
After the re-collection process is completed, the results are displayed in the FTP
Performance Data Re-collection dialog box, see Figure 9-8.
9-10

Figure 9-8 Re-Collection Results
l Success: The re-collection of the file is successful. The obtained file is saved in
the \ums-server\works\global\runtime\northbound\ftp\cdma_wim
ax\pm\BSSB directory on the NetNumen U31server.
l Timed out: The system fails to obtain the target file after 10 minutes. For these
files, verify that the file is complete on the OMM, and carry out the re-collection
process again in the NetNumen U31 system.
9-11

9-12

Chapter 10
MO Group Management
Table of Contents
Overview ..................................................................................................................10-1
Creating a Group Type .............................................................................................10-1
Creating a Group......................................................................................................10-2
Creating Groups Automatically .................................................................................10-4
Using a Group ..........................................................................................................10-7
10.1 Overview
The NetNumen U31 system allows users to group Measured Objects (MOs) for easy
performance management operations. Users can first create a group type that specifies
the NE type, MO type and wildcard level, and then add multiple groups of this group
type. The MO groups of the same type have the same NE type, MO type and wildcard
but different NE location and MO location. The group information can be used when a
user needs to select NEs and MOs for other performance management operations, for
example, query performance data of specific NEs quickly without selecting NEs and MOs
one at a time.
Note:
The MO group management functions are only applicable to specific NE types.
10.2 Creating a Group Type

This procedure describes how to create a group type.
Steps
1. In the Performance Management window, click the Group Management tab on the
top of the navigation pane, see Figure 10-1.
10-1

Figure 10-1 Group Management Tab
2. Right-click Group Tree, and then click New Group Type. The New Group Type dialog
Figure 10-2 New Group Type Dialog Box
3. Enter a name for the new group type in the Group type name box, select an NE
type, an MO type and a wildcard level, and then click OK. The created group type is
displayed under the Group Tree node.
Note:
The following operations can be performed on the created group type:
l Creating a group of the group type.
l Modifying the group type.
l Viewing the information of the group type.
l Deleting the group type.
10.3 Creating a Group

This procedure describes how to create a group.
10-2

Chapter 10 MO Group Management
Prerequisite
A group type has been created.
Steps
1. In the Performance Management window, click the Group Management tab in the
navigation pane.
2. Right-click the group type in the Group Tree, and then select New Group. The New
Group dialog box is displayed, see Figure 10-3.
Figure 10-3 New Group Dialog Box
Note:
The NE type, MO type and wildcard level of the group to be created inherits the settings
of the selected group type. Whether the NE location and MO location needs to be set
depends on the wildcard level.
3. Enter a name for the new group in the Group name box, select NEs in the NE location
pane, and/or select the MOs in the MO location pane.
4. Click OK. The created group is displayed under the group type in the Group Tree.
10-3

Note:
The following operations can be performed on the created group:
l Modifying the group,
l Viewing the information of the group,
l Deleting the group.
For an example of how to use a group, refer to 10.5 Using a Group.
10.4 Creating Groups Automatically

The NetNumen U31 system can automatically group the managed objects by a specific
attribute, for example, group GSM cells with the same Location Area Code (LAC) value
and group AAL2 Signalling Protocol (A2SP) offices with the same module number.
Note:
This function is only applicable to GSM and UMTS NEs.
This procedure describes how to group GSM cells by LAC automatically.
Steps
1. In the left navigation pane of the Performance Management window, click the Group
Management tab, and then right-click the root node (Group Tree). All optional
automatic group types are displayed on the shortcut menu, see Figure 10-4.
Figure 10-4 Shortcut Menu for Automatic Group Type Creation
10-4

Note:
If a group type is already automatically created in the system, the corresponding
command on the shortcut menu is unavailable, meaning that this group type cannot
be created repeatedly.
2. Select a group type （for example, Cell Group by LAC (GSM)） from the shortcut
menu. The group type Cell Group by LAC (GSM) is displayed in the group tree, see
Figure 10-5. Multiple groups are created under this group type. Each group contains
the cells with the same LAC value in the entire network.
Figure 10-5 Automatically Created Group Type and Groups
Note:
The name of an automatically created group type is the same as that on the shortcut
menu.
The name of an automatically created group depends on the scope of the objects being
grouped by the system.
l If the system groups objects with the same attribute value by NE for a group type,
the group name is in the format of "wildcard level_NE ID_attribute name_attribute
value", for example, "CELL(GSM)_bsc124_mnc0_mcc460".
l If the system groups objects with the same attribute value in the entire network,
the group name is in the format of "wildcard level_attribute name_attribute value",
for example, "CELL(GSM)_LAC_3".
3. (Optional) To manage the automatically created group type, perform appropriate

operations as needed.
l To view the details of the group type, right-click the group type in the group tree,
and then select View Group Type from the shortcut menu.
10-5

l To obtain the latest group information for the group type, right-click the group type
in the group tree, and then select Synchronize.
Note:
When some object change occurs, such as a change of attribute value, addition
of an object with the same attribute value, or deletion of a group member, users
need to update the group information for the automatically created group type by
performing the synchronization operation.
l To delete the group type, right-click the group type in the group tree, and then
click Delete.
4. (Optional) To view the details of an automatically created group, right-click the
corresponding node in the group tree, and then select View Group from the shortcut
menu. The View Group dialog box is displayed, see Figure 10-6.
Figure 10-6 View Group Dialog Box
10-6

10.5 Using a Group

After a group is created, users can use the group to quickly select measured objects when
the selected NE type and MO type is the same as those preset in this group. The group
location option is available only when the same NE type and MO type are selected.
This procedure describes how to use a group when querying performance data.
Prerequisite
The group to be used has been created in the system, and the NE type and MO type of
this group are known.
Steps
1. In the Performance Management window, select Performance > History
Performance Data Query on the menu bar. The History Performance Data Query
dialog box is displayed.
2. On the Index/Counter Selection tab, select the same NE type and MO type as the
group, and then select the counters and indexes to be queried, see Figure 10-7.
Figure 10-7 History Performance Data Query Dialog Box (Index/Counter Tab)
3. Click the Object Selection tab. The Object Selection tab is displayed, see Figure
10-8.
10-7

Figure 10-8 Object Selection Tab – Common Location
4. Select a location group from the Location group list, and click Group location. The
available groups are displayed, see Figure 10-9.
Figure 10-9 Object Selection Tab – Group Location
5. Select one or multiple groups as required in the Group tree.
6. Click the Time Selection tab, and then set the time periods for performance data
query.
10-8

7. Click OK.
10-9

10-10

Chapter 11
Excel Template Management
Table of Contents
Excel Template.........................................................................................................11-1
Using an Excel Template ..........................................................................................11-3
11.1 Excel Template

A predefined Excel template can be used to arrange the queried performance data in
the generated report file when the data is exported to an XLS file. Users can use the
Microsoft Excel to customize appropriate Excel templates for report files, and then upload
the customized templates to the NetNumen U31 server.
Users can select Statistics > Excel Template Management from the main menu to open
the Excel Template Management dialog box, which lists the templates under the ums-se
rver\works\global\runtime\excel-template path on the NetNumen U31 server.
Users can upload, download, and delete templates.
Figure 11-1 shows an example of the Excel template.
Figure 11-1 Excel Template Example
A standard Excel template contains four fields: TITLE, HEAD, DATA, and SUM. For a
description of the four fields, refer to Table 11-1.
11-1

Table 11-1 Four Fields in an Excel Template
Field Description Instruction
TITLE (Mandatory) Specifies the position Additional information is required for the report
and format of the additional when a user attempts to export the query
information about the report to be results of performance data to an XLS report
generated, including report name, file. For detailed instructions, refer to 11.2
measurement type, query time, Using an Excel Template.
editor, and creation time.
HEAD (Optional) Specifies the position and The system will use the head on the query
format of the table head in the report result tab as the default table head in the report
to be generated. to be generated. Users can customize the table
head as needed in this field. Special characters
are allowed in the customized table head.
DATA (Mandatory) Specifies the position The font and format of each column in the
and format of performance data corresponding column of the report can be set
in the report to be generated in as needed.
accordance with the query results of In addition, users can define conditional
performance data. format for a column in Excel to color specific
performance data. The system will apply the
preset format if the data exported to a cell of
the column meets the specified condition.
SUM (Optional) Counts the performance The prerequisites of successfully counting of

data in a column and specifies the performance data and displaying of data sums
format of the sum. in the report are:
l The cells in each column contain the
exported performance data, meaning the
column is not null.
l A blank row is reserved between DATA
and SUM fields.
Note:
l If a user adds other characters or images in an Excel template, these characters or
images will be displayed in the generated XLS file.
l Excel templates containing macros are not supported.
Figure 11-2 shows the major parts of the contents in an XLS file containing the exported
performance data, which uses the example Excel template displayed in Figure 11-1.
11-2

Chapter 11 Excel Template Management
Figure 11-2 Generated Report Based on an Excel Template
1. TITLE 3. DATA
2. HEAD 4. SUM
11.2 Using an Excel Template

This procedure describes how to use an Excel template for exporting the query results of
performance data to a report in XLS format.
Prerequisite
The query results of performance data are displayed on a tab.
Steps
1. On the query result tab, click on the toolbar. The Save dialog box is displayed, see
Figure 11-3.
Figure 11-3 Save Dialog Box
2. Select Microsoft Office Excel (*.xls) from the Files of type drop-down list.
3. Select the directory where the report is to be saved from the Save in drop-down list.
11-3

4. Click Template. The Template dialog box is displayed. Click the template to be used,
and then click Open.
5. Cancel the selection of Title, Type, Query Time, Editor, and/or Create Time as
needed.
6. Click Save. The performance data in the query results is exported to an XLS file in
accordance with the format specified in the Excel template.
Example
The customized Excel template can also be used to format the query result files based on
a common template task.
1. On the Template Task Management tab, click . The Add Common Template Task
dialog box is displayed.
2. Select XLS as the File type, and the Format template check box is activated, see
Figure 11-4.
Figure 11-4 Add Common Template Task Dialog Box
3. Select the Format template check box, and then click the Select Format Template
button. The Open dialog box is displayed.
4. Select an Excel template, and click Open. The Add Common Template Task dialog
box is displayed.
5. Click OK. The system will generates the result file in accordance with the format of the
selected Excel template.
11-4

Figures
Figure 1-1 Performance Management Flow .............................................................. 1-4
Figure 1-2 Performance Management Window ......................................................... 1-6
Figure 2-1 Measurement Task Management Tab ...................................................... 2-5
Figure 2-2 Add Measurement Task Dialog Box (Measurement Task Tab) .................. 2-7
Figure 2-3 Add Measurement Task Dialog Box (Location Tab) .................................. 2-9
Figure 2-4 Add Measurement Task Dialog Box – Manual Input ............................... 2-11
Figure 2-5 Manual Input Dialog Box ........................................................................ 2-11
Figure 2-6 Add Measurement Task Dialog Box – Manually Input MO ...................... 2-12
Figure 2-7 Create Measurement Task Dialog Box (General Tab)............................. 2-12
Figure 2-8 Consistency Status Dialog Box .............................................................. 2-19
Figure 2-9 Details Dialog Box ................................................................................. 2-20
Figure 2-10 Synchronize Measurement Task with Lower System Dialog Box ........... 2-23
Figure 2-11 Import Measurement Task Dialog Box .................................................. 2-26
Figure 2-12 Import Measurement Task Dialog Box.................................................. 2-26
Figure 2-13 Measurement Task Integrity Dialog Box ............................................... 2-28
Figure 2-14 Set PO Dialog Box ............................................................................... 2-29
Figure 2-15 Measurement Task Integrity Dialog Box ............................................... 2-30
Figure 2-16 Results of Automatic Measurement Task Creation ............................... 2-31
Figure 2-17 Details of Automatically-Created Measurement Task............................ 2-32
Figure 3-1 Counter and Index Management Tab ....................................................... 3-4
Figure 3-2 Resource Type Tree ................................................................................ 3-4
Figure 3-3 Resource Type Tree ................................................................................ 3-6
Figure 3-4 Counters of a Specific Counter Type........................................................ 3-7
Figure 3-5 Create Index Dialog Box (Basic Information Tab) ..................................... 3-8
Figure 3-6 Add Index Dialog Box (Index Formula Tab) ............................................ 3-10
Figure 3-7 Name Style and ID Style of an Index Formula........................................ 3-11
Figure 3-8 Create Index Dialog Box (Preset Threshold Tab).................................... 3-12
Figure 3-9 New Group Dialog Box .......................................................................... 3-15
Figure 3-10 Move Index Dialog Box ........................................................................ 3-19
Figure 3-11 Save Dialog Box .................................................................................. 3-20
Figure 3-12 Import Index Dialog Box....................................................................... 3-21
Figure 3-13 Import Index Dialog Box (Imported Indexes) ........................................ 3-22

Figure 3-14 Performance Management Preference Dialog Box............................... 3-24

Figure 4-1 Threshold Task Management Tab ............................................................ 4-2
Figure 4-2 Add Threshold Task Dialog Box (Threshold Task Tab).............................. 4-4
Figure 4-3 Add Threshold Task Dialog Box (Condition List)....................................... 4-6
Figure 4-4 Select Indices/Counters Dialog Box ......................................................... 4-7
Figure 4-5 Counters Added....................................................................................... 4-7
Figure 4-6 Modify Threshold Dialog Box ................................................................... 4-8
Figure 4-7 Add Threshold Task (Location Tab) .......................................................... 4-9
Figure 4-8 Add Threshold Task Dialog Box (General Tab) ....................................... 4-11
Figure 4-9 Threshold Tasks of an NE ...................................................................... 4-14
Figure 4-10 Modify Threshold Task Dialog Box ....................................................... 4-15
Figure 5-1 Template Management Tab...................................................................... 5-2
Figure 5-2 Common Template Operations................................................................. 5-3
Figure 5-3 Add Common Template Dialog Box.......................................................... 5-5
Figure 5-4 Add Template Dialog Box......................................................................... 5-6
Figure 5-5 Add Query Template Dialog Box .............................................................. 5-7
Figure 5-6 Modify Common Template Dialog Box...................................................... 5-9
Figure 5-7 Export Template Dialog Box ................................................................... 5-11
Figure 5-8 Import Template Dialog Box ................................................................... 5-12
Figure 6-1 Template Task Management Tab.............................................................. 6-2
Figure 6-2 Add Query Template Task Dialog Box ...................................................... 6-5
Figure 6-3 Customizing the Running Cycle of a Template Task ................................. 6-6
Figure 6-4 Forwarding Setup Dialog Box – Email Forward Tab ................................. 6-7
Figure 6-5 Forwarding Setup Dialog Box – FTP Push Tab ........................................ 6-7
Figure 6-6 Add Common Template Task Dialog Box (Basic Information Tab) ............ 6-9
Figure 6-7 Add Common Template Task Dialog Box (Location Information
Tab) ...................................................................................................... 6-11
Figure 6-8 Create Common Template Task (Time Information Tab) ......................... 6-12
Figure 6-9 Execution Result of a Template Task...................................................... 6-15
Figure 7-1 History Performance Data Query Dialog Box (Indices/Counters
Selection Tab)......................................................................................... 7-3
Figure 7-2 History Performance Data Query Dialog Box (Object Selection
Tab) ........................................................................................................ 7-4
Figure 7-3 Performance Data Query (Time Selection Tab) ........................................ 7-6
Figure 7-4 Add Template Dialog Box......................................................................... 7-8
Figure 7-5 Query Results of Performance Data (1) ................................................... 7-9
II

Figures

Figure 7-8 Query Results of Performance Data (4) ................................................. 7-10
Figure 7-9 Using a Measurement Task for Performance Data Query (1) ................. 7-11
Figure 7-10 Using a Measurement Task for Performance Data Query (2)................ 7-12
Figure 7-11 New Common Template Dialog Box with Counters and Indexes
Selected ............................................................................................... 7-14
Figure 7-12 History Performance Data Query Dialog Box with Counters and
Indexes Selected .................................................................................. 7-15
Figure 7-13 Setting a Logical Filtering Rule............................................................. 7-16
Figure 7-14 Setting a Top N Filtering Rule.............................................................. 7-17
Figure 7-15 Setting a Busy Hour-Based Filtering Rule ............................................ 7-19
Figure 7-16 Threshold Rendering Dialog Box.......................................................... 7-20
Figure 7-17 Chart Settings ...................................................................................... 7-22
Figure 7-18 Chart Result......................................................................................... 7-23
Figure 8-1 Add Realtime Performance Data Monitoring Dialog Box .......................... 8-2
Figure 8-2 Select Indices/Counters Dialog Box ......................................................... 8-3
Figure 8-3 Select Locations Dialog Box .................................................................... 8-3
Figure 8-4 Realtime Performance Data Monitoring Tab (Table Format) .................... 8-4
Figure 8-5 Realtime Performance Data Monitoring Tab (Chart Format) ..................... 8-5
Figure 8-6 History Performance Data Monitoring Dialog Box (Index/Counter
Selection Tab)......................................................................................... 8-7
Figure 8-7 History Performance Data Monitoring Dialog Box (Location Tab) ............. 8-9
Figure 8-8 Monitoring Results of Performance Data.................................................. 8-9
Figure 9-1 Add Data Integrity Query Dialog Box (Object Selection Tab) .................... 9-3
Figure 9-2 Add Data Integrity Query Dialog Box (Location Selection Tab) ................. 9-4
Figure 9-3 Add Data Integrity Query (Time Selection Tab)......................................... 9-5
Figure 9-4 Data Integrity Query Tab .......................................................................... 9-6
Figure 9-5 FTP Performance Data Re-collection Dialog Box ..................................... 9-8
Figure 9-6 Select OMM Node Dialog Box.................................................................. 9-9
Figure 9-7 Missing Data Files ................................................................................. 9-10
Figure 9-8 Re-Collection Results ............................................................................ 9-11
Figure 10-1 Group Management Tab ...................................................................... 10-2
Figure 10-2 New Group Type Dialog Box ................................................................ 10-2
Figure 10-3 New Group Dialog Box......................................................................... 10-3
Figure 10-4 Shortcut Menu for Automatic Group Type Creation .............................. 10-4
III

Figure 10-5 Automatically Created Group Type and Groups ................................... 10-5
Figure 10-6 View Group Dialog Box ........................................................................ 10-6
Figure 10-7 History Performance Data Query Dialog Box (Index/Counter
Tab) ...................................................................................................... 10-7
Figure 10-8 Object Selection Tab – Common Location............................................ 10-8
Figure 10-9 Object Selection Tab – Group Location ................................................ 10-8
Figure 11-1 Excel Template Example ...................................................................... 11-1
Figure 11-2 Generated Report Based on an Excel Template ................................... 11-3
Figure 11-3 Save Dialog Box .................................................................................. 11-3
Figure 11-4 Add Common Template Task Dialog Box.............................................. 11-4
IV

Tables
Table 1-1 Basic Performance Management Operations............................................. 1-4
Table 1-2 Buttons Related to Performance Management on the Main Toolbar ........... 1-7
Table 1-3 Performance Management Toolbar Buttons ............................................... 1-8
Table 2-1 Task Origins .............................................................................................. 2-2
Table 2-2 Consistency Status Descriptions ............................................................... 2-4
Table 2-3 Measurement Task Management Tab Toolbar Buttons............................... 2-5
Table 2-4 Measurement Task Tab Parameter Descriptions ........................................ 2-7
Table 2-5 Location Tab Parameter Descriptions ........................................................ 2-9
Table 2-6 General Tab Parameter Descriptions ....................................................... 2-13
Table 2-7 Consistency Status Dialog Box Buttons Description ................................ 2-19
Table 2-8 Measurement Task Integrity Dialog Box Parameter Descriptions ............. 2-28
Table 3-1 Counter and Index Management Tab Toolbar Buttons ............................... 3-5
Table 3-2 Basic Information Tab Parameter Descriptions .......................................... 3-8
Table 3-3 On-Screen Keyboard Special Key Descriptions ....................................... 3-10
Table 3-4 Preset QoS Tab Parameter Descriptions ................................................. 3-12
Table 4-1 Threshold Task Management Tab Toolbar Buttons..................................... 4-2
Table 4-2 Threshold Task Tab Parameter Descriptions.............................................. 4-4
Table 4-3 Location Tab Parameter Descriptions ........................................................ 4-9
Table 4-4 General Tab Parameter Descriptions ....................................................... 4-11
Table 4-5 Alarm Variation Due to Index Value Change ............................................ 4-13
Table 5-1 New Template Dialog Box Parameter Descriptions .................................... 5-6
Table 6-1 Toolbar Buttons for Template Task Management ....................................... 6-3
Table 6-2 Toolbar Buttons for Managing Template Task Results ................................ 6-3
Table 7-1 Object Selection Tab Parameter Descriptions ............................................ 7-5
Table 7-2 Relationships Between Threshold Direction and Threshold
Direction ................................................................................................ 7-20
Table 7-3 Query Result Tab Toolbar Buttons ........................................................... 7-21
Table 8-1 Toolbar Buttons on the Realtime Performance Data Monitoring Tab ........... 8-5
Table 8-2 Three Display Modes of Monitoring Results............................................... 8-8
Table 9-1 Data Integrity Query Tab Toolbar Buttons .................................................. 9-6
Table 11-1 Four Fields in an Excel Template ........................................................... 11-2

Tables
VI

Glossary
A2SP
- AAL2 Signalling Protocol
CDMA
- Code Division Multiple Access
EMS
- Element Management System
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communications
GUI
- Graphical User Interface
KPI
- Key Performance Indicator
LAC
- Location Area Code
MML
- Man Machine Language
MO
- Measured Object
NE
- Network Element
NMS
- Network Management System
OMM
- Operation & Maintenance Module
PI
- Performance Index
PLMN
- Public Land Mobile Network
PO
- Performance Object
QoS
- Quality of Service
VII

RNC
- Radio Network Controller
SFTP
- Secure File Transfer Protocol
SPI
- Statistical Performance Index
VIII

SJ - 20130524154927 - 005 - NetNumen U31 R18 V12 - 12 - 43 Perfor

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SJ - 20130524154927 - 005 - NetNumen U31 R18 V12 - 12 - 43 Perfor

Uploaded by

Copyright:

Available Formats

NetNumen™ U31 R18

Unified Element Management System

Revision No. Revision Date Revision Reason

R1.0 2013-06-20 First edition

Serial Number: SJ-20130524154927-005

Publishing Date: 2013-06-20 (R1.0)

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Chapter 2 Measurement Task Management............................................. 2-1

Chapter 3 Counter and Index Management ............................................. 3-1

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Chapter 4 Threshold Task Management................................................... 4-1

Chapter 5 Query Template Management .................................................. 5-1

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Chapter 7 Performance Data Query.......................................................... 7-1

Chapter 8 Performance Data Monitoring.................................................. 8-1

Chapter 9 Performance Data Integrity Report ......................................... 9-1

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Chapter 10 MO Group Management ....................................................... 10-1

Chapter 11 Excel Template Management ............................................... 11-1

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

What Is in This Manual

2, Measurement Task Provides instructions for measurement task management operations.

4, Threshold Task Provides instructions for threshold task management operations.

8, Performance Data Describes how to monitor performance data.

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Note: provides additional information about a certain topic.

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

1.2 Basic Concepts

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

1.3 Performance Management Flow

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Figure 1-1 Performance Management Flow

Table 1-1 Basic Performance Management Operations

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Customize an index Customizes an index based on existing counters and indexes in

1.4 Performance Management Window

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Figure 1-2 Performance Management Window

1. Menu bar 4. Performance management

1.4.2 Menus for Performance Management

l History Performance Data Query

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

1.4.3 Toolbar Buttons Related to Performance Management

Table 1-2 Buttons Related to Performance Management on the Main Toolbar

Queries real-time performance data.

Queries historical performance data.

Manages counters and Indexes.

Manages measurement tasks.

1.4.4 Navigation Pane

1.4.5 Performance Management Toolbar

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

Table 1-3 Performance Management Toolbar Buttons

Customizes the display of columns by hiding or displaying some columns

Searches for specific tasks or performance data.

1.5 Implicit Prerequisites

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

SJ-20130524154927-005|2013-06-20 (R1.0) ZTE Proprietary and Confidential

The following describes the common operation flow of a measurement task:

2.1.1.1 Task Status

2.1.1.2 Task Origins

Table 2-1 Task Origins

Origin Description Forbidden Operations