U2000 Northbound Performance File Interface Developer Guide (Measurement Unit-Based)

U2000
V200R015C10
Northbound Performance File

Interface Developer Guide
(Measurement Unit-Based)
Issue Draft A
Date 2015-01-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
U2000
Northbound Performance File Interface Developer Guide
(Measurement Unit-Based) About This Document
About This Document
Scope
This document provides information about the U2000 northbound performance file interface
(measurement unit-based). The document also provides operation guidelines for connecting the
network management system (NMS).
This document only describes how to use and configure general functions and does not describe
user-defined functions. If you want to know how to use and configure user-defined functions,
apply for related function documents from Huawei.
Product Versions
The following table lists the product version related to this document.
Product Name Version
U2000 V200R015C10
Intended Audience
This document is intended for:
Network management engineers
Change History
Draft A (2015-01-15)
This is a draft for V200R015C10. Compared with issue 01 (2014-04-15) of V200R014C00, no
change is made.
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential ii

U2000
Organization
1 Introduction to Northbound Performance File Interface
This chapter gives a definition of the northbound interface and the northbound performance file
interface provided by the U2000.
2 Interconnection Commissioning of the Northbound Performance File Interface
Before interconnecting the NMS with the U2000, you must conduct an interconnection test.
Based on the test result, you can determine whether the northbound performance file interface
meets the conditions for interconnecting with the NMS.
3 Introduction to Performance Data Export Tool and File
This chapter describes the performance data export tool and file.
4 Troubleshooting the Northbound Performance File Interface
The NMS interconnects with the U2000 through the northbound performance file interface. If
a fault occurs when the NMS is obtaining performance data, refer to the relevant troubleshooting
suggestions given in this chapter.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
General Conventions
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential iii

U2000
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential iv

U2000
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential v

U2000
(Measurement Unit-Based) Contents
Contents
About This Document.....................................................................................................................ii

1 Introduction to Northbound Performance File Interface......................................................1
1.1 Definition of Northbound Interface................................................................................................................................2
1.2 Definition of Northbound Performance File Interface...................................................................................................2
1.3 Using the Performance File Interface.............................................................................................................................2
1.4 Technical Specifications of Northbound File Interface..................................................................................................3
2 Interconnection Commissioning of the Northbound Performance File Interface...........4

2.1 Checking License (Performance File Interface).............................................................................................................5
2.2 Negotiating the Interconnection Parameters of the Performance File Interface.............................................................5
2.3 Exporting Performance Files..........................................................................................................................................7
2.3.1 Configuring the Performance Data Export Tool.........................................................................................................7
2.3.2 Setting Performance Data Export Tasks on the U2000 Client ...................................................................................9
2.3.3 Setting OSS Performance Data Export Tasks on the OSMU Client.........................................................................11
2.4 Verifying Interconnection.............................................................................................................................................11
2.5 (Optional) Starting and Stopping the Performance Data Export Tool.........................................................................12
3 Introduction to Performance Data Export Tool and File.....................................................15

3.1 Performance Data Export Tool.....................................................................................................................................16
3.2 Configuration File of the Performance Data Export Tool............................................................................................16
3.3 Performance Data Export File......................................................................................................................................20
4 Troubleshooting the Northbound Performance File Interface...........................................26

4.1 Common Troubleshooting and Information Collection...............................................................................................27
4.2 Troubleshooting the Performance File Export Failure.................................................................................................28
4.3 Troubleshooting the DST Identification Failure..........................................................................................................31
4.4 How to Set Northbound Interface Compatibility.........................................................................................................32
4.5 How to Set Parameters in a Northbound Configuration File........................................................................................33
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential vi

U2000
(Measurement Unit-Based) 1 Introduction to Northbound Performance File Interface
1 Introduction to Northbound Performance

File Interface
About This Chapter
This chapter gives a definition of the northbound interface and the northbound performance file
interface provided by the U2000.
1.1 Definition of Northbound Interface

The northbound interface links the element management system (EMS) and the NMS.
1.2 Definition of Northbound Performance File Interface

The northbound performance file interface is a type of northbound interface. Through the
northbound performance file interface, the NMS can obtain the performance data of NEs
(including the OSS performance measurement data).
1.3 Using the Performance File Interface

This section describes how to use the performance file interface when the U2000 system adopts
different networking modes.
1.4 Technical Specifications of Northbound File Interface

This section describes the technical specifications related to the northbound file interface.
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential 1

U2000
1.1 Definition of Northbound Interface

The northbound interface links the element management system (EMS) and the NMS.
The NMS obtains information about the network elements (NEs) managed by the EMS and
delivers operation commands through the northbound interface. The NE information includes
the alarm, configuration, performance, and inventory data. Figure 1-1 shows the position of the
northbound interface in the network.
Figure 1-1 Position of the northbound interface
In the communication network, the U2000 provides the alarm, configuration, performance, and
inventory data of NEs to the NMS through the northbound interface.
1.2 Definition of Northbound Performance File Interface

The northbound performance file interface is a type of northbound interface. Through the
northbound performance file interface, the NMS can obtain the performance data of NEs
(including the OSS performance measurement data).
NOTE
To use the northbound performance file interface, you must run the performance data export tool on the
U2000 server.
The performance data export tool is an U2000 service, PMExport. It automatically exports performance
files.
1.3 Using the Performance File Interface

This section describes how to use the performance file interface when the U2000 system adopts
different networking modes.
For details about how to use the northbound performance file interface in other networking
modes, see Table 1-1.

U2000
Table 1-1 Usage of the performance file interface
U2000 System Type NMS and U2000 Method for the NMS to
Interconnection Solution Obtain Performance Files
Single-server system Configure the performance Obtain performance files on

export tool on the U2000 the U2000 server.
server.
HA system Configure the performance Obtain performance files on

export tool on the active the active U2000 server.
Remote HA system U2000 server. OSS performance export files
can be obtained on the active
U2000 server.
1.4 Technical Specifications of Northbound File Interface

This section describes the technical specifications related to the northbound file interface.
Specification Item Value
Maximum re-upload attempts that are permitted after automatic 3

file upload fails
Interval between re-upload attempts after an automatic file 15

upload attempt fails (unit: minute)
Maximum FTP servers supported by automatic file upload 10

U2000
Northbound Performance File Interface Developer Guide 2 Interconnection Commissioning of the Northbound
(Measurement Unit-Based) Performance File Interface
2 Interconnection Commissioning of the

Northbound Performance File Interface
About This Chapter
Before interconnecting the NMS with the U2000, you must conduct an interconnection test.
Based on the test result, you can determine whether the northbound performance file interface
meets the conditions for interconnecting with the NMS.
2.1 Checking License (Performance File Interface)

Before interconnecting the U2000 to the NMS, make sure that the NMS is licensed to use the
northbound performance file interface.
2.2 Negotiating the Interconnection Parameters of the Performance File Interface

Before interconnecting the U2000 with the NMS, you need to check the license and negotiate
the interconnection parameters for the performance file interface. The performance file is
exported according to these parameters.
2.3 Exporting Performance Files

This section describes how to export performance files. Before interconnecting the NMS with
the U2000, you must export performance files to a specified path and verify whether the
U2000 meets the conditions for interconnection with the NMS.
2.4 Verifying Interconnection

This section describes how to simulate the NMS to obtain performance export files in SFTP
mode using the OSMU. Compare the parameters in an exported file with the negotiated
parameters. If the parameters in the exported file are consistent with the negotiated parameters,
the generated performance export file is correct and commissioning the northbound performance
file interface is successful.
2.5 (Optional) Starting and Stopping the Performance Data Export Tool
This section describes how to manually start and stop the performance data export tool.

U2000
2.1 Checking License (Performance File Interface)

Before interconnecting the U2000 to the NMS, make sure that the NMS is licensed to use the
northbound performance file interface.
Do as follows to check that the NMS has the required license:

1. Log in to the U2000 client.
2. Choose License > OSS License Management > License Information (traditional
style). Alternatively, double-click System Management in Application Center and
choose License Management > License Information (application style). The License
Information window is displayed.
3. Click the Resource Control Item tab. If Resource contains Performance File
Interface, the NMS is authorized to use the performance file interface.
2.2 Negotiating the Interconnection Parameters of the

Performance File Interface
Before interconnecting the U2000 with the NMS, you need to check the license and negotiate
the interconnection parameters for the performance file interface. The performance file is
exported according to these parameters.
The interconnection parameters for the performance file interface include the user name and
password for the NMS to log in to the U2000, the start time and format of the exported file, and
the fields in the exported file. Table 2-1 lists example performance file interface parameters.
The interconnection operations described in the following sections use this example as a
reference.
Table 2-1 Example of interconnection parameters
Parameter Type Parameter Parameter Value Description
User User Name ftpuser This parameter

cannot be modified.
Password The default password To improve system

is Changeme_123 security, change the
default database
password upon first
login and
periodically change
the password. The
password change
interval can be
customized as
required.
Export Path /opt/oss/server/var/ This parameter

fileint/pm cannot be modified.

U2000
Parameter Type Parameter Parameter Value Description
Content Selected Function Root node > RNC > This parameter can
Subsets Measurements be modified on the
related to U2000 client.
Algorithm >
Measurement of
Compressed Mode
per cell
Format Start Time 10/11/2008 17:00:00 This parameter can

be modified on the
U2000 client.
File Format CSV This parameter can

be modified on the
U2000 client.
Query result export 1 l The parameter

format can distinguish
additional data
that is collected
from data that is
usually exported.
l This parameter
can be modified
in the
configuration file
of the export tool.
Display time zone 1 l Displays the time

information zone information.
l This parameter
can be modified
in the
configuration file
of the export tool.
Display timezone 1 l Displays

offset information timezone offset
information.
l This parameter
can be modified
in the
configuration file
of the export tool.

U2000
2.3 Exporting Performance Files

This section describes how to export performance files. Before interconnecting the NMS with
the U2000, you must export performance files to a specified path and verify whether the
U2000 meets the conditions for interconnection with the NMS.
2.3.1 Configuring the Performance Data Export Tool

Based on the parameters negotiated with the NMS, you can modify the configuration files of
the performance data export tool. After restarting the performance data export tool, you can
export performance files based on the preset settings.
Prerequisites
You have logged in to the U2000 server as user ossuser.
Context
The performance data export tool is an U2000 service, PMExport. It automatically exports
performance files.
For details about the performance data export tool, see Introduction of Performance Data
Export Tool.
NOTICE
In an HA or remote HA system, you need to perform the following steps only on the active server
and do not need to perform them on the standby server.
Procedure
Step 1 Modify the configuration file of the performance data export tool.
1. Run the following commands to open the configuration file:
-bash-3.00$ cd /opt/oss/server/etc/PMExport/locale/en_US
-bash-3.00$ vi PMExpParam.xml
The contents of the opened configuration file are as follows:

<TimeSegmentSet>
<BeginTime Name="Begin time." Value="2006-10-29 00:00"/>
<EndTime Name="End Time." Value="2006-10-29 23:59"/>
</TimeSegmentSet>
<GeneralSet>
<CounterSortMode Name="Counter display and sort mode." Value="0"/>
<CounterValueFormat Name="Counter value fromat." Value="0"/>
<QueryTimeMode Name="Query result time mode." Value="0"/>
<DisplayTimeZone Name="Display time zone information." Value="0"/>
<DisplayDstOffSet Name="Display timezone offset information." Value="0"/>
<DeleteFileTime Name="Delete file time." Value="1:30"/>

U2000
<QueryHours Name="Query result hours." Value="5"/>

<QueryExportFormat Name="Query result export format." Value="0"/>
<FileExportMode Name="File export format." Value="1"/>
<OMCServerName Name="OMC server name." Value=""/>
<RANShared Name="RAN shared and result transmit mode" IsShared="0"/>
<GZip Name="Compress file or not." Value="0"/>
<TemplateMode Name="Template File Name Format" Value="0"/>
<IsLineCounter Name="line counter support or not." Value="0"/>
</GeneralSet>
<EffectiveSet>
<PMDBConnNum Name="PMDB database connection number." Value="20"/>
<MethodThreadNum Name="Active method's thread number." Value="2"/>
<TableThreadNum Name="Process table's thread number." Value="3"/>
<BulkReaderNum Name="Bulk read record number." Value="5000"/>
</EffectiveSet>
2. Modify configuration items.

Based on the negotiated parameters listed in 2.2 Negotiating the Interconnection
Parameters of the Performance File Interface, the modified configuration items are as
follows:
<DisplayDstOffSet Name=""Display timezone offset information." Value="1"/>
NOTE
For details about the configuration items, see 3.2 Configuration File of the Performance Data
Export Tool.
You can modify the parameters of the northbound configuration file either by running commands or
by using the OSMU. For details about the operations performed on the OSMU, see 4.5 How to Set
Parameters in a Northbound Configuration File.
3. Press Esc, and then run the :wq! command to save the modification and exit the vi editor.
Step 2 Check whether the performance data export tool is started.
-bash-3.00$ . /opt/oss/server/svc_profile.sh
-bash-3.00$ svc_adm -cmd status | grep PMExport
l If the following information is displayed, the tool has been started.

PMExport [running ]
Run the following command to restart the tool for the modifications to take effect.
-bash-3.00$ svc_adm -cmd restartsvc PMExport
l If the following information is displayed, the tool has not been started. you must start it.
PMExport [not running ]
Run the following command to start the performance data export tool:
-bash-3.00$ svc_adm -cmd startsvc PMExport
If the following information is displayed, the tool has been started successfully.
PMExport [running ]
l If no information is displayed, the tool has not been configured. You must configure it before
starting the tool.
1. Run the following command to configure the performance data export tool:
-bash-3.00$ config_pmexp_service.sh
If the following information is displayed, type y to confirm the information:
Enter y to install PMExport, or n to uninstall PMExport. (y/n):y

U2000
If the following information is displayed, the tool has been configured successfully.
Operation succeeded.
2. Run the following command to start the performance data export tool:
PMExport [running ]
----End
2.3.2 Setting Performance Data Export Tasks on the U2000 Client

This section describes how to set performance export tasks on the U2000 client before exporting
performance files.
Prerequisites
l You have logged in to the U2000 client.
l You have the following permission under Network Management Application: System
Maintenance > Operations of System Monitor and System Maintenance > Task
Management > Performance Data Export. For details about how to set user rights, see
U2000 Online Help.
Procedure
Step 1 Choose Maintenance > Task Management (traditional style); alternatively, double-click
System Management in Application Center and choose Task Schedule > Task
Management (application style). The Task Management window is displayed.
Step 2 Choose File Interface > Performance Data Export in the navigation tree to view a performance
data export task.
Step 3 Use either of the following methods to view the Attribute dialog box:
l Double-click a performance data export task in the task list.
l Select a performance data export task in the task list. Then click Attribute.
Step 4 In the Attribute dialog box, set the performance data export task.
1. Click the Common Parameter tab. Set Task Name and Begin Time.
NOTE
The value set for Begin Time of the performance data export task must be later than the current server
time.
2. Click the Extended Parameter tab. Set the extended parameters of the performance data
export task.
For details about the extended parameters of performance data export tasks, see Table
2-2.

U2000
Table 2-2 Extended parameters of performance data export tasks

Parameter Description
File Format The following three file formats are available:

l .csv
l .xml
l .txt
Hold Days Sets the hold days for an exported file. For example, if this
parameter is set to 7, the file can be saved for seven days after
the day it is exported and deleted after those seven days.
File Path Path for saving the exported file, which is set by the system.
This parameter cannot be modified.
Measure Period The following five measurement periods are available:

l 5 minutes
l 15 minutes
l 30 minutes
l 60 minutes
l 24 hours
Function Subsets 1. Select a measurement period from the Measure Period

drop-down list.
2. Select an export period from the Export Period drop-down
list. The export period must be equal to or greater than the
measurement period.
3. Enter the delay period in the Delay Period text box. The
export tool exports files according to the export period and
delay period.
4. Select the measurement subset.
Template To export performance data by using a template, you must select

the template and set the delay time.
NOTE
l For measurement subsets with the same measurement period, you can configure only one export
period.
l The delay time indicates the duration from the end time of a measurement period to the start time
on exporting the performance result of this measurement period.
l The style of files exported by Function Subsets is different from the style of files exported by
Template. Templates are created when you query performance data.
Step 5 Click OK.

The system saves the data export tasks. The export tool exports files based on the data export
tasks on schedule.
----End

U2000
2.3.3 Setting OSS Performance Data Export Tasks on the OSMU

Client
This section describes how to set OSS performance data export tasks on the OSMU client before
exporting the OSS performance files.
Prerequisites
You have logged in to the OSMU.
Context
The measurement period of the OSS performance data export task is 5 minutes. The export
period can be 60 minutes and 1440 minutes. The delay period is 5 minutes and cannot be
modified.
Procedure
Step 1 Start the Internet Explorer, type https://IP address of the U2000 server, and then press
Enter.
Step 2 Log in to the OSMU as user ossuser.
Step 3 In the main window of the OSMU, click NBI Management.
Step 4 In the navigation tree in the left pane, choose NBI Management > Centralized
Management > Northbound Configuration Parameters Setting. The Northbound
Configuration Parameters Setting window is displayed.
Step 5 Select Northbound Performance File Interface (Measurement Unit-Based) from the
Northbound Interface Name drop-down list box.
Step 6 Select PMExpParam.xml-OSSExp from the Configuration file name drop-down list box.
Step 7 Select Export Period (minutes).
Step 8 Click Save.
----End
2.4 Verifying Interconnection

This section describes how to simulate the NMS to obtain performance export files in SFTP
mode using the OSMU. Compare the parameters in an exported file with the negotiated
parameters. If the parameters in the exported file are consistent with the negotiated parameters,
the generated performance export file is correct and commissioning the northbound performance
file interface is successful.
Context
The NMS uses the SFTP to obtains files from the specified path on the U2000 server.

U2000
Procedure
Step 1 Start the Internet Explorer, type https://IP address of the U2000 server, and then press
Enter.
Step 2 Log in to the OSMU as user ossuser.
Step 3 In the main window of the OSMU, click NBI Management.
Step 4 In the navigation tree in the left pane, choose NBI Management > Category Management >
File Interface > Performance File (Measurement Unit-Based) Interface to open the
Performance File (Measurement Unit-Based) Interface page.
Step 5 On the Query Performance Measurement Unit-Based DataExport File tab page displaying
generated performance files, you can click a file name and open or download it.
Step 6 Check whether an exported performance file has been generated based on the negotiated
parameters. If it has been generated, the file is correct.
For example, obtain the performance file
pmresult_100665844_60_200811100900_200811101000_recover_200811101600.csv as
shown in Figure 2-1. The file name indicates that the data in the file is collected at 16:00, which
is not collected from 9:00 to 10:00. The data is consistent with the preset parameters, indicating
that the exported performance file is correct.
Figure 2-1 Exported performance file
----End
2.5 (Optional) Starting and Stopping the Performance Data

Export Tool
This section describes how to manually start and stop the performance data export tool.
Prerequisites
You have logged in to the U2000 server as user ossuser.
Context
performance files.
For details about the performance data export tool, see Introduction of Performance Data
Export Tool.

U2000
NOTICE
Procedure
l Start the performance data export tool.
1. Navigate to the U2000 installation directory.
The default installation directory is /opt/oss/server.
By default, run the following command:
-bash-3.00$ cd /opt/oss/server
2. Check whether the performance data export tool is started.
-bash-3.00$ . /opt/oss/server/svc_profile.sh
-bash-3.00$ svc_adm -cmd status | grep PMExport
– If the following information is displayed, the tool has been started.

PMExport [running ]
– If the following information is displayed, the tool has not been started. you must
start it.
PMExport [not running ]
Run the following command to start the performance data export tool:
PMExport [running ]
– If no information is displayed, the tool has not been configured. You must
configure it before starting the tool.
a. Run the following command to configure the performance data export tool:
If the following information is displayed, type y:
Enter y to install PMExport, or n to uninstall PMExport. (y/n):y
If no command output is displayed, the tool has been configured successfully.

b. Run the following command to start the performance data export tool:
If the following information is displayed, the tool has been started
successfully.
PMExport [running ]
l Stop the performance data export tool.

1. Navigate to the U2000 installation directory.
The default installation directory is /opt/oss/server.
By default, run the following command:

U2000
-bash-3.00$ cd /opt/oss/server
2. Run the following command to stop the performance data export tool:
-bash-3.00$ . ./svc_profile.sh
-bash-3.00$ svc_adm -cmd stopsvc PMExport
If the following information is displayed, the tool has been stopped successfully.
PMExport [stopped ]
3. Run the following command to uninstall the performance data export tool:
If the following information is displayed, type n:

Enter y to install PMExport, or n to uninstall PMExport. (y/n):n
If no command output is displayed, the tool has been uninstalled successfully.
----End

U2000
(Measurement Unit-Based) 3 Introduction to Performance Data Export Tool and File
3 Introduction to Performance Data Export

Tool and File
About This Chapter
This chapter describes the performance data export tool and file.
3.1 Performance Data Export Tool

performance files.
3.2 Configuration File of the Performance Data Export Tool

The configuration file of the performance data export tool is located in the directory /opt/oss/
server/etc/PMExport/locale/en_US/PMExpParam.xml. You can configure partial settings of
the export function. You can also modify the configuration file to set performance export options.
3.3 Performance Data Export File

This section describes the path, categories and quantities, and the rules for naming performance
export files. It also gives examples of illustrate performance export files.

U2000
3.1 Performance Data Export Tool

performance files.
After the performance data export tool starts, it automatically exports specified performance
results to a file when the preset period ends. The exported performance results still exist in the
performance database.
Typically, the performance export tool does not export user-defined counters on the U2000.
When exporting counters by using a template, this tool, however, can export user-defined
counters.
The U2000 can automatically upload exported files through FTP. Choose Software > FTP Auto
Upload Management > Target Server Settings (traditional style); alternatively, double-click
System Management in Application Center and choose Settings > FTP Auto Upload
Management > Target Server Settings (application style) on the client to set the relevant
parameters. After you set the parameters, the U2000 automatically uploads the exported files to
the specified FTP server every five minutes by default. The NMS can therefore obtain the
generated files. For details about how to configure this function, see the U2000 Online Help.
3.2 Configuration File of the Performance Data Export Tool

The configuration file of the performance data export tool is located in the directory /opt/oss/
server/etc/PMExport/locale/en_US/PMExpParam.xml. You can configure partial settings of
the export function. You can also modify the configuration file to set performance export options.
The contents of the configuration file are as follows:
NOTE
You are not required to restart the export tool after modifying BeginTime and EndTime of
<TimeSegmentSet>, but you must restart the export tool after modifying any of the other parameters.
<TimeSegmentSet>
<BeginTime Name="Begin time." Value="2006-10-29 00:00"/>
<EndTime Name="End Time." Value="2006-10-29 23:59"/>
</TimeSegmentSet>
<GeneralSet>
<CounterSortMode Name="Counter display and sort mode." Value="0"/>
<CounterValueFormat Name="Counter value fromat." Value="0"/>
<QueryTimeMode Name="Query result time mode." Value="0"/>
<DisplayDstOffSet Name="Display timezone offset information." Value="0"/>
<DeleteFileTime Name="Delete file time." Value="1:30"/>
<QueryHours Name="Query result hours." Value="5"/>
<FileExportMode Name="File export format." Value="1"/>
<OMCServerName Name="OMC server name." Value=""/>
<RANShared Name="RAN shared and result transmit mode" IsShared="0"/>
<GZip Name="Compress file or not." Value="0"/>
<TemplateMode Name="Template File Name Format" Value="0"/>
<IsLineCounter Name="line counter support or not." Value="0"/>
</GeneralSet>
<EffectiveSet>
<PMDBConnNum Name="PMDB database connection number." Value="20"/>
<MethodThreadNum Name="Active method's thread number." Value="2"/>

U2000
<TableThreadNum Name="Process table's thread number." Value="3"/>

<BulkReaderNum Name="Bulk read record number." Value="5000"/> </EffectiveSet>
The following sections describe the configuration items:
TimeSegmentSet
<TimeSegmentSet> configures a time segment for exporting results to a file.
l BeginTime
This item sets the start time for exporting results.
l EndTime
This item sets the end time for exporting results.
NOTE
The end time set must be later than the start time, If the span between the start time and the end time
is too long, the export function is affected. Therefore, you are advised to set the span to a maximum
of five hours. If you need to collect data over a long period, you can set the start time and the end
time for several different times. For example, if you need to collect the performance data from
2006-01-01 00:00 to 2006-01-01 10:00, you can collect the performance data from 2006-01-01 00:00
to 2006-01-01 05:00 first by entering BeginTime=2006-01-01 01:00, EndTime=2006-01-01
06:00 in the configuration file. After the performance data for this period has been exported, you can
then collect the performance data from 2006-01-01 05:05 to 2006-01-01 10:00 by entering
BeginTime=2006-01-01 06:05, EndTime=2006-01-01 11:00 in the configuration file.
Set the BeginTime to the sum of the start time for the first period in the missing file, the export
period, and the delay time. Set the EndTime to the sum of the start time for the last period in the
missing file, the export period, and the delay time. For example, if the export period is 30 minutes,
the delay time is 30 minutes, and the first period of the missing file is from 00:00 of 2008-03-31 to
00: 30 of 2008-03-31, BeginTime is 01: 00 of 2008-03-31. Based on the previous assumptions, if
the last period of the missing file is from 00:00 of 2008-04-01 to 00: 30 of 2008-04-01, the
EndTime is 01:00 of 2008-04-01.
After you set BeginTime and EndTime, the export tool starts collecting data within five minutes.
This does not affect the usual collection of data, the supplementary data collection based on period
can be performed at the same time as the usual data collection. After a period collection, if you do
not change the values of BeginTime and EndTime, the period collection will not be performed again.
The export tool performs supplementary data collection automatically on the hour. In this way, any
data that is delayed for saving to the database is collected. The time for automatic supplementary
data collection is determined by QueryHours.
GeneralSet
GeneralSet contains common configuration items, which can be modified as required.
l CounterSortMode
This item specifies the sequence of counters in result files, You are advised to set
CounterSortMode to 1.
– If CounterSortMode is set to 0, the counters in the exported file are arranged in
ascending order based on the character string lengths of counter names.
ascending order based on counter IDs.
ascending order based on the character string ASCII codes of counter names.
l CounterValueFormat
This item specifies the display mode of counter values in the result files.

U2000
– If CounterValueFormat is set to 0, the counter values of measurement units that

contain only non-character-string counters are not marked with quotation marks in the
exported result file. The counter values of measurement units that contain character-
string counters, however, are marked with quotation marks.
– If CounterValueFormat is set to 1, all the counter values in the exported result file are
marked with quotation marks.
– If CounterValueFormat is set to 2, none of the counter values in the exported result
file are marked with quotation marks.
l QueryTimeMode
This item specifies the time mode for querying the results.
– If QueryTimeMode is set to 0, the result is queried based on the server time and
displayed based on the NE time. The name of the result file uses the server time while
the start time in the file uses the NE time.
– If QueryTimeMode is set to 1, the result is queried based on the server time and
displayed based on the server time. The name of the result file and the start time in the
file both use the server time.
l DisplayTimeZone
This item specifies whether to display the time zone information.
– If DisplayTimeZone is set to 0, the system does not display the time zone information.
– If DisplayTimeZone is set to 1, the system displays the time zone information.
l DisplayDstOffSet
This item specifies whether to display the DST offset information.
– If DisplayDstOffSet is set to 0, the system does not display the DST offset information.
– If DisplayDstOffSet is set to 1, the system displays the DST offset information.
l DeleteFileTime
This item specifies the execution time for deleting overdue exported files.
By default, the system deletes any overdue exported files at 01:30 in the morning every
day.
l QueryHours
This item specifies the number of periods for querying the recollected results.
After this item is set, the system checks whether recollected data is available within the
specified time range once the timer has been triggered.
For example, if the value of QueryHours is set to 5, the system checks whether recollected
data is available within the time range 10:00 to 15:00 when the timer is triggered at 15:00.
If recollected data is available, that data is exported to the corresponding file.
l QueryExportFormat
This item specifies the implementation mode for exporting the recollected results.
– If QueryExportFormat is set to 0, the NMS exports all the results and re-writes the
existing exported files if the recollected data is available.
– If QueryExportFormat is set to 1, the NMS exports the recollected data to another
file. The file name is different, which is pmresult_measurement unit ID_measurement
period_start time_end time_recover_current system time.csv or
pmresult_measurement unit ID_measurement period_start time_end
time_recover_current system time.xml. The existing exported files are not changed.

U2000
NOTE
When QueryExportFormat is set to 1, the supplementary recovery export mode is adopted. In

this mode, the template-based export is not supported, and therefore you should exercise caution
when using the mode.
l FileExportMode
This item determines the format of file names.
– If FileExportMode is set to 0, a file name does not include the name of the host or the
name of the NE type.
– If FileExportMode is set to 1, a file name includes the name of the host and the name
of the NE type. The format of such file names is pmresult_Name of a host_Name of
the NE Type_measurement unit_measurement period_start time_end time.xml, for
example, pmresult_OSSsvr-
CDMA_HLR_150999067_5_200710121535_200710121540.xml.
NOTE
Name of the NE Type in the file name indicates all types of NEs with mediations installed for
the measurement unit ID. For example, pmresult_osssvr-1_BSC6900 GSM@BSC6900
UMTS@BSC6900 GU@RNC_67109473_30_200910220200_200910220230.xml.
l OMCServerName
This item specifies the name of the server. Its value is null by default.
– If the value of OMCServerName is not null, the name of the exported file is server
name_pmresult_measurement unit_measurement period_start time_end time.csv.
For example, if OMCServerName is set to MyServer, the name of the exported file
is MyServer_pmresult_function subset_measurement period_start time_end
time.csv.
– If the value of OMCServerName is null, the name of the exported file is
pmresult_function subset_measurement period_start time_end time.csv.
l RANShared
This item determines whether the RAN sharing mode is used. Its value is set to the common
mode by default.
– If IsShared is set to 0, RANShared is set to common mode.
– If IsShared is set to 1, RANShared is set to RAN sharing mode.
l GZip
This item determines whether to compress the result files.
– If the value of GZip is set to 0, the result files are not compressed.
– If the value of GZip is set to 1, the result files are compressed based on the UNIX
standard. The extension of the compressed file is gz.
l TemplateMode
This item specifies the format of the template name.
– If TemplateMode is set to 0, the template name is included in the name of the result
file.
– If TemplateMode is set to 1, the template ID is included in the name of the result file.
l IsLineCounter
This item determines whether to calculate the linear counters based on linear formulas.

U2000
– If IsLineCounter is set to 0 , the linear counters are calculated accbased on the original
counter formulas.
– If IsLineCounter is set to 1 , the linear counters are calculated based on linear formulas.
EffectiveSet
The <EffectiveSet> specifies export efficiency. You are not allowed to modify this parameter
because each configuration item is closely related to other configuration items.
l PMDBConnNum
This item specifies the number of connections allowed in the database.
l MethodThreadNum
This item specifies the number of threads for initializing the active thread mode.
l TableThreadNum
This item specifies the number of threads used by the timer for triggering the result
processing table.
l BulkReaderNum
This item specifies the number of results read in batches when the system queries the results
in the database result table.
3.3 Performance Data Export File

This section describes the path, categories and quantities, and the rules for naming performance
export files. It also gives examples of illustrate performance export files.
Path of Performance Export Files

The file export path is set uniformly using the integrated task management function. By default,
the files are exported to the /opt/oss/server/var/fileint/pm[/index] directory. After the
performance export tool starts, it automatically creates a folder in the directory on a daily basis.
The folders are named in the format of pmexport_Date of the day. All the files generated on
the same day are saved in the same folder.
For example, the pmexport_20060215 folder saves all the performance files exported on
February 15, 2006.
l [/index]: index number of an operator. The U2000 automatically creates this variable to
save performance export files for different operators when multiple operators share the
network.
l The U2000 automatically creates the FTP user and performance export directory. In
addition, the U2000 binds the directory with user rights to manage performance export
files.
l The NMS users can access the authorized directory through the SFTP to obtain performance
export files.
Categories and Quantities of Performance Export Files

Pay attention to the following two scenarios for exporting performance results:

U2000
l If function subsets are configured in performance files, save the results of each function
subset to a file.
l If templates are configured in performance files, save the results of each template to a file.
Rules for Naming Performance Export Files

l Exporting files not by template
The name of the file for saving performance results can be pmresult_Function subset
ID_Measurement period_Start time_End time.file type.
Performance export files support the following formats:
– .csv
– .xml
– .txt
For example, the name of the performance export file
pmresult_67109445_30_200507041030_200507041100.csv indicates that
– The time range is from 10:30 to 11:00 on July 4, 2005.
– The number of the function subset is 67109445.
– The measurement period is 30 minutes.
l Exporting files by template
A template supports the query of multiple function subsets at the same time.
The following describes the naming convention of the file that is used to save performance
results:
– If a template contains only one function subset and a template ID is configured
ID_Measurement period_Start time_End time_Template ID.csv or pmresult_Function
subset ID_Measurement period_Start time_End time_Template ID.xml.
pmresult_67109445_30_200507041030_200507041100_10001.csv indicates that
– The ID of the function subset is 67109445.
– The template ID is 10001.
– If a template contains only one function subset and a template name is configured
ID_Measurement period_Start time_End time_Template Name.csv or
pmresult_Function subset ID_Measurement period_Start time_End time_Template
Name.xml.
pmresult_67109445_30_200507041030_200507041100_TCPState.csv indicates
that
– The ID of the function subset is 67109445.

U2000
– The template name is TCPState.

– If a template contains multiple function subsets and a template ID is configured
The name of the file for saving performance results can be pmresult_Measurement
period_Start time_End time_Template ID.csv or pmresult_Measurement period_Start
time_End time_Template ID.xml.
pmresult_30_200507041030_200507041100_10001.csv indicates that
– The template ID is 10001.
– If a template contains multiple function subsets and a template name is configured
The name of the file for saving performance results can be pmresult_Measurement
period_Start time_End time_Template Name.csv or pmresult_Measurement
period_Start time_End time_Template Name.xml.
pmresult_30_200507041030_200507041100_ TCPState.csv indicates that
– The template name is TCPState.
Examples of Performance Export Files

l Performance export file in .csv format
In this example, the performance export file is in .csv format.
In the configuration file PMExpParam.xml, when the configuration item
CounterSortMode is set to 0 or 2, the exported result file is displayed based on the counter
name.
The following describes the exported result file:
– The first row is the title:
Result Time | Granularity Period | Object Name | Reliability | Name of
Counter 1 | Name of Counter 2 | ......
– The second row lists the units.

The unit is displayed if the unit exists; otherwise, Null is displayed. The second row is
as follows:
Null | Minutes | Null | Null | Unit of Counter 1 | Unit of Counter 2 | ......
– From the third row onwards, information about the performance results is displayed
based on the field name provided in the first row. Each result record occupies one row.
For example:
Result Time,Granularity Period,Object Name,Reliability,"ABNORMAL RELEASE
TIMES","CIRCUIT BLOCKED BY PEER END TIMES","MSG FORMAT ERROR TIMES","NO BLA TO
T13 TIMES","NO CLF TO T5 TIMES"
,Minutes,,,times,times,times,times,times
2005-12-6 4:30,30,"softx_test/Office:OFFICEDIR=2/ subRouteNo:SRC=2/
Group:TG=22",Reliable,11063,9071,24817,5903,5248 2005-12-6
4:30,30,"softx_test/Office:OFFICEDIR=3/ subRouteNo:SRC=3/Group:TG=3",Reliable,
6724,31445,31621,3221,21711

U2000
In the configuration file PMExpParam.xml, if the configuration item

CounterSortMode is set to 1, the exported result file is displayed based on the counter ID.
The following describes the exported result file:
The first row is the title:
Result Time | Granularity Period | Object Name | Reliability | ID of Counter 1
| ID of Counter 2 | ......
The second row lists the units. The unit is displayed if the unit exists; otherwise, Null is
displayed. The second row is as follows:
Null | Minutes | Null | Null | Unit of Counter 1 | Unit of Counter 2 | ......
From the third row onwards, information about the performance results is displayed based
on the field name provided in the first row.
For example:
Result Time,Granularity Period,Object
Name,Reliability,"84149755","84149756","84149757","84149758","84149759","84149
760","84149761","84149762"
,Minutes,,,times,times,times,times,times,times,times,times
2006-05-23 15:00,30,"msc_b035/MSCServer:msc_b035",Reliable,
9460,2824,31106,25564,5173,19433,16631,20223
l Performance export file in .xml format

In this example, the performance export file is in .xml format.
In the configuration file PMExpParam.xml, if the configuration item
CounterSortMode is set to 0 or 2, the exported result file is displayed based on the counter
name. The following describes the exported result file:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE mdc SYSTEM "MeasDataCollection.dtd">
<mdc>
<mfh> <cbt>200511200900</cbt> </mfh>
<md> <mi> <mts>200511200900</mts>
<gp>30</gp>
<mt>Duration of link in the In-service state</mt>
<mt>Number of signal units received in error</mt>
<mt>Duration of SL unavailability(for any reason)</mt>
<mt>Number of SIF and SIO octets transmitted</mt>
<mt>MSUs discarded due to SL congestion</mt>
<mv> <moid>msc_zd/MSCServer:msc_zd</moid>
<r>0</r> <r>0</r> <r>0</r> <r>0</r> <r>0</r>
<sf>false</sf> </mv> </mi> </md>
<mff> <ts>200511200930</ts> </mff>
</mdc>
Table 3-1 describes the functions of the main flags in the exported XML file.
Table 3-1 Format of exported XML files
Format Description
<mdc> Indicates that the content of the file is performance measurement data.
mdc is the abbreviation of MeasDataCollection.
<cbt> Indicates the start time for exporting performance measurement data.
cbt is the abbreviation of collectionBeginTime.
<md> Indicates the measurement results within an export period.

md is the abbreviation of measData.

U2000
Format Description
<mi> Indicates the measurement results within a measurement period.

mi is the abbreviation of measInfo.
<mts> Indicates the start time of a measurement period

mts is the abbreviation of measTimeStamp.
<gp> Indicates a measurement period.

gp is the abbreviation of granularityPeriod.
<mt> Indicates the name or ID of a measurement object or a measurement

counter.
mt is the abbreviation of measTypes.
<mv> Indicates the measurement results of a measurement object.

mv is the abbreviation of measValues.
<moid> Indicates a measurement object.

moid is the abbreviation of measObjInstId.
<r> Indicates the value of each measurement result.

r is the abbreviation of measResults.
<sf> Indicates the reliability of the value for an object.

l <sf>false</sf>: indicates that the value is reliable.
l <sf>false</sf>: indicates that the value is unreliable.
sf is the abbreviation of suspectFlag.
<ts> Indicates the end time for exporting performance measurement data.
ts is the abbreviation of TimeStamp.
It is assumed that CounterSortMode=1 is set.

In the configuration file PMExpParam.xml, when the configuration item
CounterSortMode is set to 1, the exported result file is displayed based on the counter
ID.
l Format of an object name
The format of an object name is NE name (the first level)/identifier of object name (the
second level):value of object name (the second level)/identifier of object name (the third
level):value of object name (the third level)/identifier of object name (the fourth
level):value of object name (the fourth level)/....

U2000
NOTE
l The "/" symbol indicates the separator for object levels.

l The first level provides the NE name without the object identifier. From the second level onwards,
the identifier of an object is put on the left of the ":" symbol, and the value of the object is put
on the right of the ":" symbol.
l The object name has two display modes:
l Displaying the name of the object directly.
The following uses the BTS object under BSC6900 GSM for example: BSC12/SITE: site1.
BSC12 is the NE name, and site1 is the name of the BTS object instance.
l Combining multiple property-value pairs (separated with a comma ) of the object to identify
the object.
The following uses the cell object under BSC6900 GSM for example: BSC12/GCELL:
LABEL= site1, CellIndex= xxxx, CGI= xxxxxxxxxxxxx.
If an object is identified based on the combination of property-value pairs, you should obtain
the value of each property based on the property name of this object instead of forcibly
specifying the location and number of properties for parsing the object information. When
the NMS is parsing the property names, ensure that the names are case insensitive.
Description of the Performance Data Export File

When you interconnect the U2000 with the NMS, you need to pay attention to the following
items:
l When you export performance data according to measurement units, the exported
measurement counters are the counter sets for measurement on the U2000 client.
l The counters in the exported file are sorted based on the rules for setting the
CounterSortMode parameter in the PMExpParam.xml file. Therefore, when you add or
cancel a measurement counter, the absolute location of the counter changes. When the NMS
parses the files, do not assume that a counter is in a fixed location, Otherwise, the expected
counter may be inconsistent with the actual counter.
l The result of a counter may be null. If the value is null, the corresponding counter has no
result or the result conveys no meaning. A null value is displayed when the NE does not
report the result of the corresponding counter, or the counter is a calculation counter. The
divisor in the corresponding formula is zero.
NOTE
l If the returned counter value is 999999999.000, the counter value reported by an NE exceeds the
upper threshold for storage.
l If the returned counter value is -999999999.000, the counter value reported by an NE exceeds the
lower threshold for storage.
l If the returned counter value is -999999999.999, the counter value reported by an NE is incorrect.
For example:
l The A=B+C format exists in the counter formula but the value of C is lost within a certain period.
l 0 is processes as the denominator in the counter formula.

U2000
Northbound Performance File Interface Developer Guide 4 Troubleshooting the Northbound Performance File
(Measurement Unit-Based) Interface
4 Troubleshooting the Northbound

Performance File Interface
About This Chapter
The NMS interconnects with the U2000 through the northbound performance file interface. If
a fault occurs when the NMS is obtaining performance data, refer to the relevant troubleshooting
suggestions given in this chapter.
4.1 Common Troubleshooting and Information Collection

If a fault occurs when the NMS attempts to obtain performance data through the northbound
performance file interface, handle the fault following the troubleshooting suggestions described
in this section for the most common faults. If it is not possible to handle the fault by using these
troubleshooting suggestions, collect information about the fault and contact Huawei technical
support.
4.2 Troubleshooting the Performance File Export Failure

This section describes how to troubleshoot any performance file export failure that occurs due
to the following causes: 1) The performance data export service is not started; 2) No NE data
exists in the performance result report; 3) Data of certain NEs fails to be saved to the database
within the specified time; 4) The NE time zone is incorrect; 5) NEs are disconnected; 6) There
is no free disk space on the U2000 server.
4.3 Troubleshooting the DST Identification Failure

This section describes how to handle the situation where the DST offset displayed in the name
of an exported file does not refer to the DST.
4.4 How to Set Northbound Interface Compatibility

This section describes how to set the FDN format and OMC ID of northbound interfaces so that
the northbound interfaces are compatible with earlier versions.
4.5 How to Set Parameters in a Northbound Configuration File

This section describes how to set parameters in the configuration file of a northbound interface.

U2000
4.1 Common Troubleshooting and Information Collection

If a fault occurs when the NMS attempts to obtain performance data through the northbound
performance file interface, handle the fault following the troubleshooting suggestions described
in this section for the most common faults. If it is not possible to handle the fault by using these
troubleshooting suggestions, collect information about the fault and contact Huawei technical
support.
Common Troubleshooting
For suggestions on how to handle common faults that may occur during the process of obtaining
performance data for the NMS, see Table 4-1.
Table 4-1 Troubleshooting common faults
Common Fault Troubleshooting Suggestion
The performance file is not exported. See 4.2 Troubleshooting the Performance
File Export Failure.
How to set parameters in a northbound See 4.5 How to Set Parameters in a

configuration file Northbound Configuration File.
Information Collection
If an unusual fault occurs when the NMS is obtaining performance data, collect information
about the fault to locate the fault. For details about how to collect fault information, see Table
4-2.
Table 4-2 Description of information collection
Related Information Description
Operation information Records any operations performed before a

fault occurs and the troubleshooting measures
taken later.
Version information You can obtain version information about the

U2000, NE mediations, and NEs from each
office.
IP information You can obtain IP information about U2000

servers for each office.

U2000
Related Information Description
Log information NOTE

In an HA or remote HA system, you need to
perform the following steps only on the active
server and do not need to perform them on the
standby server.
l You can obtain logs from the /opt/oss/
server/var/logs path. The .trace file in the
PMExport directory is
iMAP.pmexp_agent.trace.
l You can obtain the performance export
file from the /opt/oss/server/var/fileint/
pm/ path.
4.2 Troubleshooting the Performance File Export Failure

This section describes how to troubleshoot any performance file export failure that occurs due
to the following causes: 1) The performance data export service is not started; 2) No NE data
exists in the performance result report; 3) Data of certain NEs fails to be saved to the database
within the specified time; 4) The NE time zone is incorrect; 5) NEs are disconnected; 6) There
is no free disk space on the U2000 server.
Symptom
No performance files exist on the export path. The NMS cannot obtain the performance data of
the NE.
Troubleshooting
Generally, the export of performance files fails due to one of the following causes:
l The performance data export service has not been started.
l No NE data exists in the performance result report.
l Data of certain NEs fails to be saved to the database within the specified period.
l The NE time zone is incorrect.
l NEs are disconnected.
l No free disk space is available on the U2000 server.
Handling Performance Export Service Not Started Faults

View the status of the performance data export service. Determine whether the service has
started. If the service has not started, run the relevant commands to start it.
1. Log in to the U2000 server as user ossuser.
2. Determine the status of the performance export service.
$ cd /opt/oss/server
$ . ./svc_profile.sh

U2000
$ svc_adm -cmd status

If the following message is displayed, the service has started.
PMExport [running ]
3. If the service has not started, run the following command to start it:
$ svc_adm -cmd startsvc PMExport
Handling NE Data Unavailability Faults

The performance result report does not contain any NE data. As a result, no performance result
exists in the performance database and thus no performance export file is generated.
Query the function subset or template on the U2000 client. If no result is queried on the client,
it indicates that no data exists in the performance database and the performance export file cannot
be generated. Follow the steps below to determine the specific cause:
1. On the U2000 client, choose Maintenance > Task Management (traditional style);
alternatively, double-click System Management in Application Center and choose Task
Schedule > Task Management (application style). The Task Management window is
displayed.
NOTE
The U2000 displays information about the export result in Result Info only when it is exporting a
file.
2. In the navigation tree on the left, choose File Interface > Performance Data Export to
view the information in the Result Info area. If The result is empty, need not
write file. is displayed in Result Info, it indicates that the performance result report
does not contain any data.
Handling Data Saving Timeout Faults

Follow the steps below to determine whether certain data fails to be saved to the database within
the specified period.
1. If the northbound interface delays exporting the export file, determine whether the export
file is generated on the hour. If the generation time is a little later than an hour, the file is
generated during supplementary collection. In this case, data of certain NEs fails to be saved
to the database within the specified period.
2. Query the performance result report and determine whether any data fails to be saved to
the database within the specified period.
a. Query the performance result report.
Determine the name of the result report based on the number of the function subset
and the measurement period. The result report uses the following naming convention:
tbl_Result_subset number_measurement period. The measurement period can be 0,
1, 2, 3, or 4, which indicates 5, 15, 30, 60, and 1440 minutes, respectively.
b. Query the result report by using the SQL sentence. You can execute the SQL sentence
on the U2000 server to obtain all the results for the subset.
For example, the export period, measurement period, and delay time of the northbound
interface are 60 minutes respectively, and the function subset is 123456. If the
northbound interface fails to export the data from 10:00 a.m. to 11:00 a.m. on August
16, 2008 to a file, delays exporting data to a file, or exports incomplete data to a file,

U2000
you can query the results of all the measurement objects of that period (from 10:00
a.m. to 11:00 a.m. on August 16, 2008) on the client.
If working under Sybase, execute the following SQL sentence: select * from
tbl_Result_123456_3 where SvrStartTime >= '2008-08-16 10:00:00' and
SvrStartTime < '2008-08-16 11:00:00'
If working under Oracle, execute the following SQL sentence: select * from
tbl_Result_123456_3 where SvrStartTime >= to_date('2008-08-16
10:00:00','yyyy-MM-dd HH24:MI:SS') and SvrStartTime < to_date('2008-08-16
11:00:00','yyyy-MM-dd HH24:MI:SS')
3. Determine the value of InsertTime.
Determine the value of InsertTime based on the query result of the performance result
report.
l If the difference between the InsertTime and SvrEndTime of a measurement object is
greater than the specified delay time, that is, 60 minutes, the northbound interface delays
exporting the data.
l If the difference between the InsertTime and SvrEndTime of a measurement object is
greater than the specified time for supplementary collection (usually five hours), the
result of this measurement object cannot be exported to the export file.
l If the difference between the InsertTime and SvrEndTime of all the measurement objects
is greater than the specified time for supplementary collection, no export file is
generated.
Handling Incorrect NE Time Zone Faults

Based on the query result of the performance result report, determine whether the performance
file export failure is caused due to an incorrect NE time zone. For details, see Table 4-3.
Table 4-3 Identifying the NE time zone
Result Available Identification Method Conclusion
No Replace SvrStartTime in the If the performance result

original SQL sentence with report cannot be queried, it
StartTime. indicates that the time zone of
all the NEs in this subset is
incorrect.
Yes Compare StartTime with l If StartTime and

SvrStartTime. SvrStartTime are
consistent, it indicates
that the NE and the server
share the same time zone.
l If StartTime and
SvrStartTime are
inconsistent, it indicates
that the NE and the server
have different time zones.

U2000
Result Available Identification Method Conclusion
Determine the value of If the time zone is not the

TimezoneOffset for the NE. actual time zone of the NE, it
For example, if the value of indicates that the time zone of
TimezoneOffset is 480, it the NE is incorrect.
indicates the eighth time zone
(480/60 = 8).
Handling NE Disconnection Faults

1. On the U2000 client, choose Topology > Main Topology (traditional style); alternatively,
double-click Topo View in Application Center and choose Topology > Main
Topology (application style). In the Main Topology window, right-click the disconnected
NE and then choose Reconnect NE.
2. Verify the network and rectify the network fault.
3. Rectify the fault on the NE mediation. To reinstall the NE mediation, see the
Commissioning Guide of the corresponding U2000 networking mode.
Handling Insufficient Disk Space Faults on the U2000 Server

Clear the disk space on the U2000 server.
NOTICE
Confirm the files can be deleted before clearing the disk space. Deleting a file by mistake can
result in incorrect system operation. You are advised to clear the disk space by referring to the
Administrator Guide of the corresponding U2000 networking mode.
Solution
Contact Huawei technical support.
4.3 Troubleshooting the DST Identification Failure

This section describes how to handle the situation where the DST offset displayed in the name
of an exported file does not refer to the DST.
Symptom
The DST offset displayed in the name of an exported file does not refer to the DST.
Troubleshooting
1. When QueryExportFormat and QueryTimeMode are both set to 0, if NEs and the U2000
server are in different time zones, the result file is exported according to the server's time

U2000
while the contents of the result file are displayed according to each NE's time. For example,
NE1 and NE2 are located in the time zones GMT+4:00 and GMT+10:00 respectively while
the U2000 server is in the time zone GMT+8:00. In this instance, the result file is exported
according to the server's time, GMT+8:00, while the contents of the result file are displayed
according to the NE's time.
In this case, set QueryTimeMode to 1. Then, the results are exported according to the time
of the U2000 server.
2. Assume the U2000 is in the time zone GMT-5. The DST rule for 2006 specifies that you
should set the time to be one hour earlier from 02:00 on April 2 to 02:00 on October 29.
That is, set the time 02:00 to 03:00 on April 2, and then set the time 02:00 to 01:00 on
October 29. The rule for exporting the results for the repeated period from 01:00 DST to
02:00 on October 29 are as follows:
l When QueryExportFormat is set to 0 and QueryTimeMode is set to 0 or 1, if the
U2000 is in DST, the results of the last one or two periods from 01:00 DST time on
October 29 to 01:00 DST time on October 29 are exported with a one hour delay. The
results generated in the period from 01:00 DST on October 29 to 02:00 DST on October
29 and in the period from 01:00 on October 29 to 02:00 on October 29 are exported in
the same file. The DST identifies the period to which the data belong.
l When QueryExportFormat is set to 1 and QueryTimeMode is set to 0 or 1, if the
U2000 is in DST, the last one or two results generated in the period from 01:00 DST
on October 29th to 01:00 on October 29th are exported with a one hour delay. The data
generated in the period from 01:00 on October 29th to 02:00 on October 29th cannot
be exported.
In this case, set both QueryExportFormat and QueryTimeMode to 1. Then, the results are
exported according to the time of the U2000 server.
4.4 How to Set Northbound Interface Compatibility

This section describes how to set the FDN format and OMC ID of northbound interfaces so that
the northbound interfaces are compatible with earlier versions.
Prerequisites
You have logged in to the master OSMU server (include the master server of active site and
standby site) as user ossuser. OSMU address: https://U2000 master server IP:31123/
Procedure
Step 1 Click NBI Management on the main page of the OSMU.
Step 2 In the navigation tree of the left pane, choose NBI Management > Centralized
Management > Northbound Interface Compatibility Settings. The Northbound Interface
Compatibility Settings tab page is displayed.
Step 3 View the current FDN format and OMC ID of each northbound interface.
Step 4 Set the FDN format and OMC ID for each northbound interface based on telecom operators'
requirements.

U2000
NOTE
You can reset the FDN format, OMC ID, and SRAN northbound interface only after you have negotiated
with telecom operators.
Step 5 Select The northbound interface change has been discussed with the customer. The
customer demands the above settings.
Step 6 Click OK.
The system displays a message stating that some services will restart for the settings to take
effect.
Step 7 Click Yes to confirm the settings and restart the related services. Click No to cancel the settings.
----End
Follow-up Procedure
If the system displays a message stating that the related services fail to restart, these services do
not exist or there are other services being restarted. When this occurs, log in to the U2000 server
to install or manually restart the related services.
4.5 How to Set Parameters in a Northbound Configuration

File
This section describes how to set parameters in the configuration file of a northbound interface.
Prerequisites
You have logged in to the master OSMU server (include the master server of active site and
standby site) as user ossuser. OSMU address: https://U2000 master server IP:31123/
Context
For details about the configuration file of each northbound interface, see the related developer
guide.
Only the northbound performance file interface (NE-based) involves parameter reconfiguration
for slave servers. However, when you modify parameters through the OSMU, you need to modify
them only on the master server, and the slave server automatically synchronizes the
modifications.
Procedure
Step 1 Click NBI Management on the main page of the OSMU.
Step 2 Choose NBI Management > Centralized Management > Northbound Configuration
Parameters Settings. The Northbound Configuration Parameters Settings page is displayed.
Step 3 Select a northbound interface and its configuration file. Then set new values to parameters to be
modified in the configuration file.

U2000
NOTE
l If an interface is not installed, its configuration file cannot be modified. If you select an interface that
is not installed, a message is displayed, indicating that the interface is not installed and you can modify
its configuration file only after installation.
l You can click Reset to restore the modified parameters to their previous values.
l The modifications of parameters marked with * take effect only after you restart related services.
l Parameter validity check will check the validity of parameter values. For details about parameter value
ranges, see the parameter description in the related interface developer guide.
Step 4 Click Save for the modification to take effect.
You can view service restart logs in Service Restarted Log.
----End


U2000 Northbound Performance File Interface Developer Guide (Measurement Unit-Based)

Uploaded by

Document Information

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

U2000 Northbound Performance File Interface Developer Guide (Measurement Unit-Based)

Uploaded by

Copyright:

Available Formats

U2000

Northbound Performance File

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential i

About This Document

Product Name Version

Network management engineers

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential ii

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices and

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential iii

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential iv

Double-click Press the primary mouse button twice continuously and

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential v

About This Document.....................................................................................................................ii

2 Interconnection Commissioning of the Northbound Performance File Interface...........4

3 Introduction to Performance Data Export Tool and File.....................................................15

4 Troubleshooting the Northbound Performance File Interface...........................................26

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential vi

1 Introduction to Northbound Performance

About This Chapter

1.1 Definition of Northbound Interface

1.2 Definition of Northbound Performance File Interface

1.3 Using the Performance File Interface

1.4 Technical Specifications of Northbound File Interface

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential 1

1.1 Definition of Northbound Interface

Figure 1-1 Position of the northbound interface

1.2 Definition of Northbound Performance File Interface

1.3 Using the Performance File Interface

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential 2

Table 1-1 Usage of the performance file interface

Single-server system Configure the performance Obtain performance files on

HA system Configure the performance Obtain performance files on

1.4 Technical Specifications of Northbound File Interface

Specification Item Value

Maximum re-upload attempts that are permitted after automatic 3

Interval between re-upload attempts after an automatic file 15

Maximum FTP servers supported by automatic file upload 10

Issue Draft A (2015-01-15) Huawei Proprietary and Confidential 3

2 Interconnection Commissioning of the

About This Chapter

2.1 Checking License (Performance File Interface)

2.2 Negotiating the Interconnection Parameters of the Performance File Interface

2.3 Exporting Performance Files

2.4 Verifying Interconnection