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

M2000
V200R009
M2000 Northbound Performance File Interface

Developer Guide (Measurement Unit-Based)
Issue
01
Date
2009-07-30
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any
assistance, please contact our local office or company headquarters.
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
Copyright Huawei Technologies Co., Ltd. 2009. 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 the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

M2000
M2000 Northbound Performance File Interface Developer
Guide (Measurement Unit-Based)
Contents
Contents
About This Document.....................................................................................................................1
1 Introduction to Northbound Performance File Interface (Measurement Unit-Based)
...........................................................................................................................................................1-1
1.1 Definition of Northbound Interface.................................................................................................................1-2
1.2 Definition of Northbound Performance File Interface (Measurement Unit-Based).......................................1-2
2 Introduction to Performance Data Export Tool and File (Measurement Unit-Based)

...........................................................................................................................................................2-1
2.1 Performance Data Export Tool (Measurement Unit-Based)...........................................................................2-2
2.2 Configuration file of the Performance Data Export Tool (Measurement Unit-Based)...................................2-2
2.3 Performance Data Export File (Measurement Unit-Based)............................................................................2-6
2.4 Operations Related to the Performance Data Export Tool (Measurement Unit-Based).................................2-9
2.4.1 Modifying the Configuration File of the Performance Data Export Tool (Measurement Unit-Based)
.......................................................................................................................................................................2-10
2.4.2 Setting Export Tasks on the M2000 Client (Measurement Unit-Based).............................................2-13
2.4.3 Starting the Performance Data Export Tool (Measurement Unit-Based)............................................2-15
2.4.4 Stopping the Performance Data Export Tool (Measurement Unit-Based)...........................................2-15
3 Interconnection Commissioning of the Northbound Performance File Interface

(Measurement Unit-Based)..........................................................................................................3-1
3.1 Negotiating the Interconnection Parameters of the Performance File Interface (Measurement Unit-Based)
...............................................................................................................................................................................3-2
3.2 Exporting Performance Files (Measurement Unit-Based)..............................................................................3-3
3.2.1 Modifying the Configuration File of the Performance Data Export Tool (Measurement Unit-Based)
.........................................................................................................................................................................3-4
3.2.2 Setting an Performance Export Task (Measurement Unit-Based).........................................................3-5
3.2.3 Checking Exported Performance Files (Measurement Unit-Based)......................................................3-6
3.2.4 Commissioning the Interconnection of the Performance File Interface (Measurement Unit-Based)
.........................................................................................................................................................................3-7
3.2.5 Usage of the Performance File Interface (Measurement Unit-Based)...................................................3-8
4 Troubleshooting for the Northbound Performance File Interface (Measurement UnitBased)...............................................................................................................................................4-1

4.1 Common Troubleshooting and Information Collection (Measurement Unit-Based).....................................4-2
4.2 Troubleshooting the Performance File Export Failure (Measurement Unit-Based).......................................4-3
4.3 Troubleshooting the Failure of DST Identification.........................................................................................4-6
Issue 01 (2009-07-30)

Contents
M2000
Index.................................................................................................................................................i-1
ii

Issue 01 (2009-07-30)
M2000
Figures
Figures
Figure 1-1 Location of the northbound interface.................................................................................................1-2
Figure 3-1 Exported performance file..................................................................................................................3-7
Issue 01 (2009-07-30)

iii
M2000
Tables
Tables
Table 2-1 Parameters of performance data export tasks.....................................................................................2-14
Table 3-1 Example of interconnection parameters...............................................................................................3-2
Table 3-2 Parameter setting..................................................................................................................................3-5
Table 3-3 Usage of the performance file interface...............................................................................................3-8
Table 4-1 Common troubleshooting.....................................................................................................................4-2
Table 4-2 Description of information collection..................................................................................................4-2
Table 4-3 Identifying the NE time zone...............................................................................................................4-5
Issue 01 (2009-07-30)

M2000
About This Document
About This Document
Purpose
This document provides the information about M2000 Northbound performance file interface
(Measurement Unit-Based). The document also provides the operation guide for connecting the
NMS.
Related Versions
The following table lists the product versions related to this document.
Product Name
Version
M2000
V200R009
Intended Audience
The intended audiences of this document are:
l
Network administrator
Update History
01 (2009-06-30)
Initial release. Also, the first formal release.
Organization
1 Introduction to Northbound Performance File Interface (Measurement Unit-Based)
This provides the definition of the northbound interface and the definition of the northbound
performance file interface provided by the M2000.
2 Introduction to Performance Data Export Tool and File (Measurement Unit-Based)
This describes the performance data export tool and file.
3 Interconnection Commissioning of the Northbound Performance File Interface
(Measurement Unit-Based)
Issue 01 (2009-07-30)

M2000
About This Document
Before interconnecting the NMS with the M2000, you must conduct an interconnection
commissioning. Based on the commissioning result, determine whether the northbound
performance file interface meets the conditions for interconnecting with the NMS.
4 Troubleshooting for the Northbound Performance File Interface (Measurement UnitBased)
The NMS interconnects with the M2000 through the northbound performance file interface. If
a fault occurs when the NMS is obtaining performance data, refer to relevant troubleshooting
methods in this chapter.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol
Description
Indicates a hazard with a high level of risk, which if not
avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or supplement
important points of the main text.
General Conventions
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
2

Issue 01 (2009-07-30)
M2000
About This Document
The command conventions that may be found in this document are defined as follows.
Convention
Description
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.
Convention
Description
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 .
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.
Issue 01 (2009-07-30)

M2000
About This Document
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 01 (2009-07-30)
M2000
1 Introduction to Northbound Performance File Interface

Introduction to Northbound Performance

File Interface (Measurement Unit-Based)
About This Chapter

This provides the definition of the northbound interface and the definition of the northbound
performance file interface provided by the M2000.
1.1 Definition of Northbound Interface
The northbound interface is an interface between the Element Management System (EMS) and
the Network Management System (NMS).
1.2 Definition of Northbound Performance File Interface (Measurement Unit-Based)
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.
Issue 01 (2009-07-30)

1-1
1 Introduction to Northbound Performance File Interface

M2000
1.1 Definition of Northbound Interface

The northbound interface is an interface between the Element Management System (EMS) and
the Network Management System (NMS).
On the northbound interface, the NMS obtains the information about the NEs managed by the
EMS and delivers operation commands. The NE information includes the alarm, configuration,
performance and inventory data. The Northbound interface is as shown in Figure 1-1.
Figure 1-1 Location of the northbound interface
In the mobile communication network, the M2000 is an EMS. The M2000 reports the alarm,
configuration, performance and inventory data 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.
NOTE
To use the northbound performance file interface, you must run the performance data export tool on the
M2000 server.
1-2

Issue 01 (2009-07-30)
M2000
2 Introduction to Performance Data Export Tool and File

Introduction to Performance Data Export

Tool and File (Measurement Unit-Based)
About This Chapter

This describes the performance data export tool and file.
2.1 Performance Data Export Tool (Measurement Unit-Based)
The performance export tool automatically exports performance results.
2.2 Configuration file of the Performance Data Export Tool (Measurement Unit-Based)
The configuration file of the performance data export tool exists in the directory /export/home/
omc/var/etc/PMExport/PMExpParam.xml. You can configure the partial settings of the
export function. You can modify the configuration file to set the performance export.
2.3 Performance Data Export File (Measurement Unit-Based)
This describes the path, categories and quantities, and rules for naming performance export files.
This also gives examples to illustrate performance export files.
2.4 Operations Related to the Performance Data Export Tool (Measurement Unit-Based)
Starting the performance export tool and stopping the performance export tool.
Issue 01 (2009-07-30)

2-1

M2000
2.1 Performance Data Export Tool (Measurement UnitBased)

The performance export tool automatically exports performance results.
After the performance 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.
The M2000 can automatically upload the exported files through FTP. You can choose
Software > FTP Auto Upload Management > Target Server Setting on the client to set
relevant parameters. After you set the parameters, by default, the M2000 automatically uploads
the exported files to the specified FTP server every five minutes. Thus, the NMS can obtain the
generated files. For details about how to configure the function, see the M2000 Online Help.
2.2 Configuration file of the Performance Data Export Tool

The configuration file of the performance data export tool exists in the directory /export/home/
omc/var/etc/PMExport/PMExpParam.xml. You can configure the partial settings of the
export function. You can modify the configuration file to set the performance export.
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>. For the modification of other parameters, you must restart the export tool.
<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"/>
<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"
TransmitMode="2"/>
<GZip Name="Compress file or not." Value="0"/>
<TemplateMode Name="Template File Name Format" Value="0"/>
</GeneralSet>
<EffectiveSet>
<PMDBConnNum Name="PMDB database connection number." Value="10"/>
<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>
The following part describes the configuration items:

2-2

Issue 01 (2009-07-30)
M2000

TimeSegmentSet
<TimeSegmentSet> configures a time segment for exporting results to a file.
l
BeginTime
This item sets the start time for exporting results.
EndTime
This item sets the end time for exporting results.
NOTE
The set end time 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 not more
than five days.If you plan to collect the data of a long period, you can configure the start time and
the end time for several times. For example, if you plan to collect the performance data from
2006-01-01 to 2006-01-10, you can collect the performance data from 2006-01-01 to 2006-01-05
first by setting BeginTime=2006-01-01 00:00, EndTime=2006-01-05 00:00 in the configuration file.
After the performance data within the period is exported, you can collect the perform data from
2006-01-05 to 2006-01-10 by setting the BeginTime=2006-01-05 00:05, EndTime=2006-01-10
00:00 in the configuration file.
Set the BeginTime to be the sum of the begin time of the first period in the missing file, the export
period, and the delay time. Set the EndTime to be the sum of the begin time of the last period in the
missing file, the export period, and the delay time. For instance, 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 31st, March,
2008 to 00: 30 of 31st, March, 2008, the BeginTime is 01: 00 of 31st, March, 2008. Based on the
previous assumptions, if the last period of the missing file is from 00:00 of 1st, April, 2008 to 00: 30
of 2nd, April, 2008, the EndTime is 01:00 of 1st, April, 2008.
After you set the BeginTime and the EndTime, the export tool collects the data of the set period
within five minutes. The period collection is mainly used for manual supplementary collection. Not
affecting the normal collection, the supplementary collection based on period can be performed at
the same time with the normal collection. After the period collection, you can set the same value for
the BeginTime and the EndTime for prevention purposes. In addition, the manual supplementary
collection differs from the automatic collection of the collection tool. The export tool performs the
automatic collection at the round clock. In this way, any data that is delayed for accessing the database
is collected. The time for automatic supplementary collection is based on QueryHours.
GeneralSet
GeneralSet contains common configuration items, which can be modified as required.
l
CounterSortMode
This item sets the sequence of counters in the result file.
If the value of CounterSortMode is set to 0, the counters in the exported file are
arranged in ascending order based on the character string sizes of counter names.
arranged in ascending order based on counter IDs.
arranged in ascending order based on the character string ASCII codes of counter names.
CounterValueFormat
This item sets a display mode for counter values in the result file.
Issue 01 (2009-07-30)
If the value of CounterValueFormat is set to 0, the counter values of the measurement

unit that contains only non-character-string counters are not marked with quotation
2-3

M2000
marks in the exported result file. The counter values of the measurement unit that
contains character-string counters, however, are marked with quotation marks.
If the value of CounterValueFormat is set to 1, all the counter values in the exported
result file are marked with quotation marks.
If the value of CounterValueFormat is set to 2, none of the counter values in the

exported result file are marked with quotation marks.
QueryTimeMode
This item sets a time mode for querying results.
If the value of QueryTimeMode is set to 0, the result is queried according to server

time and displayed according to NE time. The name of the result file is server time and
the start time in the file is NE time.
If the value of QueryTimeMode is set to 1, the result is queried according to server

time and displayed according to server time. The name of the result file is server time
and the start time in the file is server time.
DisplayTimeZone
This item sets whether to display the time zone information.
If the value of DisplayTimeZone is set to 0, the system does not display the time zone
information.
If the value of DisplayTimeZone is set to 1, the system displays the time zone
information.
DisplayDstOffSet
This item sets whether to display the DST offset information.
If the value of DisplayDstOffSet is set to 0, the system does not display the DST offset
information.
If the value of DisplayDstOffSet is set to 1, the system displays the DST offset
information.
DeleteFileTime
This item sets the execution time for deleting the overdue exported files.
By default, the system deletes the overdue exported files at 01:30 in the morning every day.
QueryHours
This item sets the number of periods for querying the recollected results.
After this item is set, the system checks whether there is recollected data available within
the set time range once the timer is triggered.
For example, if the value of QueryHours is set to 5, the system checks whether there is
the recollected data available within the time range 10:00 to 15:00 when the timer is
triggered at 15:00. If the recollected data is available, the data is exported to the
corresponding file.
QueryExportFormat
This item sets the implementation mode for exporting the recollected results.
2-4
If the value of QueryExportFormat is set to 0, export all the results and re-write the
existing exported files if the recollected data is available.
If the value of QueryExportFormat is set to 1, export 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
Issue 01 (2009-07-30)
M2000

time_recover_current system time.xml. The existing exported files do not have any
change.
l
FileExportMode
This item sets the format of file names.
If the value of FileExportMode is set to 0, a file name does not include the name of
the host or the name of the NE type.
If the value of FileExportMode is set to 1, a file name includes the name of the host
and the name of the NE type. The format of a file name is pmresult_Name of a
host_Name of the NE Type_measurement unit_measurement period_start time_end
time.xml, such as pmresult_M2000svrCDMA_HLR_150999067_5_200710121535_200710121540.xml.
OMCServerName
This item sets the name of the server. The 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 the value of OMCServerName is set to MyServer, the name of an
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.
RANShared
This item sets whether the RAN sharing mode is used. The value is common mode by
default.
If IsShared is set to 0, you can infer that RANShared is common mode.
If IsShared is set to 1, you can infer that RANShared is RAN sharing mode.
For the RAN sharing mode, you can set the TransmitMode parameter to determine the
mode to forward non-cell data. TransmitMode = 0 indicates that the data is forwarded
to all operators. TransmitMode = 1 indicates that the data is forwarded to none of the
operators. TransmitMode = 2 indicates that the data is forwarded to only primary
operators.
GZip
This item sets 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 according to the UNIX
standard. The extension of the compressed file is gz.
TemplateMode
This item sets the format of the template name.
If the value of TemplateMode is set to 0, the template name is contained in the name
of the result file.
If the value of TemplateMode is set to 1, the template ID is contained in the name of

the result.
EffectiveSet
The <EffectiveSet> portion is a parameter for setting the export efficiency. You are not allowed
to modify the parameter because each configuration item is closely related to other configuration
items.
Issue 01 (2009-07-30)

2-5

l
M2000
PMDBConnNum
This item sets the number of connections allowable for the database.
MethodThreadNum
This item sets the number of threads for initializing the active thread mode.
TableThreadNum
This item sets the number of threads used by the timer for triggering the result processing
table.
BulkReaderNum
This item sets the number of results read in batches at a time when the system queries results
in the database result table.
2.3 Performance Data Export File (Measurement UnitBased)

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

The file export path is set uniformly by the integrated task management function. By default,
the files are exported to the /export/home/omc/var/fileint/pm/ directory. After the performance
export tool starts, it creates a folder in the directory automatically on a daily basis. The folders
are named in the pmexport_Date of the day format. The files that are 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.
The M2000 automatically creates the FTP user and performance export directory. In addition,
the M2000 binds the directory with user rights to manage performance export files.
The NMS user can access the authorized directory through the FTP to obtain performance export
files.
Categories and Quantities of Performance Export Files

When performance results are exported, note the following two scenarios:
l
If function subsets are configured in performance files, save the result of each function
subset to a file.
If templates are configured in performance files, save the result 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:
2-6
.csv
Issue 01 (2009-07-30)
M2000
.xml
.txt

For example, the name of the performance export file

pmresult_67109445_30_200507041030_200507041100.csv indicates:
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.
Exporting files by template

A template can support the query of multiple function subsets at the same time.
The rules for naming the file that is used to save performance results are as follows:
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:
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:
The ID of the function subset is 67109445.
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:
Issue 01 (2009-07-30)
The template ID is 10001.
If a template contains multiple function subsets and a template name is configured

2-7

M2000
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:
The template name is TCPState.
Examples of Performance Export Files

l
An example of the performance export file in .csv format

In this example, the performance export file is set in .csv format.
In the configuration file PMExpParam.xml, the configuration item CounterSortMode,
which is set to 0 or 2, determines that the exported result file is displayed by the counter
name.
The exported result file is as follows.
As the title, the first row is as follows:
Result Time | Granularity Period | Object Name | Reliability | Name of Counter 1 | Name of
The second row lists the units.

The unit is displayed if the unit exists; otherwise, Null is displayed. The second row is
shown as follows:
Null | Minutes | Null | Null | Unit of Counter 1 | Unit of Counter 2 | ......
From the third row, the information about the performance results is displayed according
to the field name in the first row. Each result record occupies one row.
For example:
Result Time,Granularity Period
,Object Name,Reliability,"ABNORMAL RELEASE TIMES
","CIR
It is assumed that CounterSortMode=1 is set.

which is set to 1, determines that the exported result file is displayed by the counter ID.
The exported result file is as follows.
The first row is the title, as follows:
Result Time | Granularity Period | Object Name | Reliability | ID of Counter 1 | ID of Counter
The second row lists the units. The unit is displayed if the unit exists; otherwise, Null is
displayed. The second row is shown as follows:
Null | Minutes | Null | Null | Unit of Counter 1 | Unit of Counter 2 | ......
From the third row, the information about the performance results is displayed according
to the field name in the first row.
For example:
Result Time,Granularity Period,Object Name,Reliability,"84149755","84149756",
"84149757","84149758","84149759","84149760","84149761","84149762",Minutes,,,ti
mes,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
2-8
An example of the performance export file in .xml format

Issue 01 (2009-07-30)
M2000

In this example, the performance export file is set in .xml format.

which is set to 0 or 2, determines that the exported result file is displayed by the counter
name. The exported result file is as follows.
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE mdc SYSTEM "MeasDataCollection.dtd"><mdc> <
<sf></sf> indicates the reliability of the value for a object. sf is the abbreviation of
suspect flag.
<sf>false</sf>: indicates reliable.
<sf>true</sf>: indicates unreliable.
It is assumed that CounterSortMode=1 is set.

In the configuration file PMExpParam.xml, the configuration item CounterSortMode
which is set to 1, determines that the exported result file is displayed by 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)/....
NOTE
The "/" symbol indicates the separator of object levels.

The identifier of an object at a layer is located on the left of the ":" symbol. The value of an object
at a layer is located on the right of the ":" symbol.
For example:
The name of an object with two levels can be RNC4/Cell:22081.
The name of an object with three levels can be RNC4/MTP3BLinkSet:0/MTP3BLinkt:0.
Description of the Performance Data Export File

When you interconnect the M2000 with the NMS, you need to pay attention to the following
items:
l
When you export the performance data according to measurement units, the exported
measurement counters are the counters set for measuring on the M2000 client.
The counters in the exported file are sorted according to 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 place. If you assume that the
counter is in a fixed place, the expected counter may be inconsistent with the actual counter.
The result of a counter may be null. If the value is null, it indicates that the corresponding
counter has no result or the result conveys no meaning. The possible causes of a null value
are as follows: 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.
2.4 Operations Related to the Performance Data Export Tool

Starting the performance export tool and stopping the performance export tool.
Issue 01 (2009-07-30)

2-9

M2000
2.4.1 Modifying the Configuration File of the Performance Data Export Tool (Measurement
Unit-Based)
Modifying parameters of the configuration file of the performance data export tool, such as
BeginTime, EndTime, CounterSortMode, CounterValueFormat, QueryTimeMode,
DisplayTimeZone, and so on.
2.4.2 Setting Export Tasks on the M2000 Client (Measurement Unit-Based)
You can set performance export tasks on the M2000 client.
2.4.3 Starting the Performance Data Export Tool (Measurement Unit-Based)
This describes the procedure for starting the performance data export tool.
2.4.4 Stopping the Performance Data Export Tool (Measurement Unit-Based)
This describes the procedure for stopping the performance data export tool.
2.4.1 Modifying the Configuration File of the Performance Data

Export Tool (Measurement Unit-Based)
Modifying parameters of the configuration file of the performance data export tool, such as
BeginTime, EndTime, CounterSortMode, CounterValueFormat, QueryTimeMode,
DisplayTimeZone, and so on.
Context
NOTE
You are not required to restart the export tool after modifying BeginTime and EndTime of
<TimeSegmentSet>. For the modification of other parameters, you must restart the export tool.
Procedure
Step 1 Modify BeginTime.
This item sets the start time for exporting results.
Step 2 Modify EndTime.
This item sets the end time for exporting results.
NOTE
The set end time 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 not more than five hours.
If you plan to collect the data of a long period, you can configure the start time and the end time for several
times. For example, if you plan 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 setting
BeginTime=2006-01-01 00:00, EndTime=2006-01-01 05:00 in the configuration file. After the
performance data within the period is exported, you can collect the perform data from 2006-01-01 05:05
to 2006-01-01 10:00 by setting the BeginTime=2006-01-01 05:05, EndTime=2006-01-01 10:00 in the
configuration file.
After you set the BeginTime and the EndTime, the export tool collects the data of the set period within
five minutes. The period collection is mainly used for manual supplementary collection. Not affecting the
normal collection, the supplementary collection based on period can be performed at the same time with
the normal collection. After the period collection, you can set the same value for the BeginTime and the
EndTime for prevention purposes. In addition, the manual supplementary collection differs from the
automatic collection of the collection tool. The export tool performs the automatic collection at the round
clock. In this way, any data that is delayed for accessing the database is collected. The time for automatic
supplementary collection is based on QueryHours.
2-10

Issue 01 (2009-07-30)
M2000

Step 3 Modify GeneralSet.

GeneralSet contains common configuration items, which can be modified as required.
Step 4 Modify CounterSortMode.
This item sets the sequence of counters in the result file.
l
If the value of CounterSortMode is set to 0, the counters in the exported file are arranged
in ascending order based on the character string sizes of counter names.
in ascending order based on counter IDs.
in ascending order based on the character string ASCII codes of counter names.
Step 5 Modify CounterValueFormat.

This item sets a display mode for counter values in the result file.
l
If the value of CounterValueFormat is set to 0, the counter values of the measurement unit
that contains only non-character-string counters are not marked with quotation marks in the
exported result file. The counter values of the measurement unit that contains character-string
counters, however, are marked with quotation marks.
If the value of CounterValueFormat is set to 1, all the counter values in the exported result
file are marked with quotation marks.
If the value of CounterValueFormat is set to 2, none of the counter values in the exported
result file are marked with quotation marks.
Step 6 Modify QueryTimeMode.

Set the displayed time mode of the query results by changing the value of the
QueryTimeMode.
l
If the value of QueryTimeMode is set to 0, the query results are displayed in mode of NE
time.
If the value of QueryTimeMode is set to 1, the query results are displayed in mode of server
time.
Step 7 Modify DisplayTimeZone.

This item sets whether to display the time zone information.
l
If the value of DisplayTimeZone is set to 1, the system displays the time zone information.
If the value of DisplayTimeZone is set to 0, the system does not display the time zone
information.
Step 8 Modify DisplayDstOffSet.

This item sets whether to display the DST offset information.
l
If the value of DisplayDstOffSet is set to 1, the system displays the DST offset information.
If the value of DisplayDstOffSet is set to 0, the system does not display the DST offset
information.
Step 9 Modify DeleteFileTime.

This item sets the execution time for deleting the overdue exported files.
By default, the system deletes the overdue exported files at 01:30 in the morning every day.
Issue 01 (2009-07-30)

2-11

M2000
Step 10 Modify QueryHours.

This item sets the number of periods for querying the recollected results.
After this item is set, the system checks whether there is recollected data available within the
set time range once the timer is triggered.
For example, if the value of QueryHours is set to 5, the system checks whether there is the
recollected data available within the time range 10:00 to 15:00 when the timer is triggered at
15:00. If the recollected data is available, the data is exported to the corresponding file.
<EffectiveSet> is a parameter for setting export efficiency. The configuration items are mutually
dependent. The configuration of this item cannot be modified.
Step 11 Modify QueryExportFormat.
This item sets the implementation mode for exporting the recollected results.
l
If the value of QueryExportFormat is set to 0, export all the results and re-write the existing
exported files if the recollected data is available.
If the value of QueryExportFormat is set to 1, export 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 do not have any change.
Step 12 Modify FileExportMode.

This item sets the format of file names.
l
If the value of FileExportMode is set to 0, a file name does not include the name of the host
or the name of the NE type.
If the value of FileExportMode is set to 1, a file name includes the name of the host and the
name of the NE type. The format of a file name is pmresult_Name of a host_Name of the
NE Type_measurement unit ID_measurement period_start time_end time.xml, such as
pmresult_M2000svr-CDMA_HLR_150999067_5_200710121535_200710121540.xml.
Step 13 Modify OMCServerName.

This item sets the name of the server. The value is null by default.
l
If the value of OMCServerName is not null, the name of the exported file is server
name_pmresult_function subset_measurement period_start time_end time.csv. For
example, if the value of OMCServerName is set to MyServer, the name of an 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.
Step 14 Modify RANShared.

This item sets whether the RAN sharing mode is used. The value is common mode by default.
l
If IsShared is set to 0, you can infer that RANShared is common mode.
If IsShared is set to 1, you can infer that RANShared is RAN sharing mode.
For the RAN sharing mode, you can set the TransmitMode parameter to determine the mode
to forward non-cell data. TransmitMode = 0 indicates that the data is forwarded to all
operators. TransmitMode = 1 indicates that the data is forwarded to none of the operators.
TransmitMode = 2 indicates that the data is forwarded to only primary operators.
2-12

Issue 01 (2009-07-30)
M2000

Step 15 Modify GZip.

This item sets whether to compress the result files.
l
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 according to the UNIX standard.
The extension of the compressed file is gz.
Step 16 Modify TemplateMode.

This item sets the format of the template name.
l
If the value of TemplateMode is set to 0, the template name is contained in the name of the
result file.
If the value of TemplateMode is set to 1, the template ID is contained in the name of the
result file.
Step 17 Modify PMDBConnNum.

This item sets the number of connections allowable for the database
Step 18 Modify MethodThreadNum.
This item sets the number of threads for initializing the active thread mode.
Step 19 Modify TableThreadNum.
This item sets the number of threads used by the timer for triggering the result processing table.
Step 20 Modify BulkReaderNum.
This item sets the number of results read in batches at a time when the system queries results in
the database result table.
----End
2.4.2 Setting Export Tasks on the M2000 Client (Measurement UnitBased)

You can set performance export tasks on the M2000 client.
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Choose Maintenance > Task Management. 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.
Select a performance data export task in the task list. Then click Attribute.
Step 4 Click the Extended Parameter tab.

Issue 01 (2009-07-30)

2-13

M2000
Step 5 Set the performance data export task.

Table 2-1 describes the parameters of a performance data export task.
Table 2-1 Parameters of performance data export tasks
Parameter
Description
File Format
Three formats are available, that is,

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

l
5 minutes
15 minutes
30 minutes
60 minutes
24 hours
1. Select the measure period from the Measure Period drop-down

tab.
2. Select the export period from the Export Period drop-down list.
The export period must be equal to or greater than the measure
period.
3. Input the delay period to the Delay Period textbox. The export
tool exports files according to the export period and delay period.
4. Select the measure subset.
Template
To export the performance data by using a template, you need to

select the template and set the delay time.
NOTE
For measurement subsets with the same measurement period, you can configure only one export period.
Step 6 Click OK.

Then the system saves the export task, according to which the export tool exports files at the
scheduled time.
----End
2-14

Issue 01 (2009-07-30)
M2000

2.4.3 Starting the Performance Data Export Tool (Measurement

Unit-Based)
This describes the procedure for starting the performance data export tool.
Prerequisite
Log in to the M2000 server as root.
Context
The performance export tool is a service, PMExport, provided by the M2000. It starts and stops
after the M2000 starts and stops. You can start the performance export tool manually during the
operation of the M2000.
Procedure
Step 1 Go to the M2000 installation folder.
The default M2000 installation path is /opt/OMC.
# cd /opt/OMC
Step 2 Start the performance export tool.
# . ./svc_profile.sh
# svc_adm -cmd startsvc PMExport
The performance export tool starts successfully if the following prompt is displayed:
PMExport
[running
----End
2.4.4 Stopping the Performance Data Export Tool (Measurement

Unit-Based)
This describes the procedure for stopping the performance data export tool.
Prerequisite
Log in to the M2000 server as root.
Context
The performance export tool is a service, PMExport, provided by the M2000. It starts and stops
after the M2000 starts and stops. You can stop the performance export tool manually during the
operation of the M2000.
Procedure
Step 1 Go to the M2000 installation folder.
The default M2000 installation path is /opt/OMC.
Issue 01 (2009-07-30)

2-15

M2000
# cd /opt/OMC
Step 2 Stop the performance export tool.
# svc_adm -cmd stopsvc PMExport
The performance export tool stops if the following prompt is displayed:
PMExport............................stopped
------------cost: 3*1500(msec)-----------svc_adm : info : INDIE_STOP finished
If the following message is displayed, you can infer that the performance export tool is not
running:
svc_adm:error:service is not running
----End
2-16

Issue 01 (2009-07-30)
M2000
3 Interconnection Commissioning of the Northbound

Performance File Interface (Measurement Unit-Based)
Interconnection Commissioning of the
Northbound Performance File Interface

About This Chapter

Before interconnecting the NMS with the M2000, you must conduct an interconnection
commissioning. Based on the commissioning result, determine whether the northbound
performance file interface meets the conditions for interconnecting with the NMS.
3.1 Negotiating the Interconnection Parameters of the Performance File Interface (Measurement
Unit-Based)
Before interconnecting the M2000 with the NMS, you need to check the license and negotiate
the interconnection parameters of the performance file interface. The performance file is
exported according to the negotiated parameters.
3.2 Exporting Performance Files (Measurement Unit-Based)
This describes how to export performance files. Before interconnecting the NMS with the
M2000, you need to export the performance files to the specified path. Based on the exported
files, determine whether the M2000 meets the conditions for interconnection with the NMS.
Issue 01 (2009-07-30)

3-1

M2000
3.1 Negotiating the Interconnection Parameters of the

Before interconnecting the M2000 with the NMS, you need to check the license and negotiate
the interconnection parameters of the performance file interface. The performance file is
exported according to the negotiated parameters.
Checking License
Before connecting the M2000 to the NMS, check whether the NMS is licensed to use the
performance file interface.
1.
Log in to the M2000 client.
2.
Choose Help > License Information. The License Information window is displayed.
3.
Click the Function control item tab. If License name contains Performance File
Interface, you can infer that the NMS is authorized to use the performance file interface.
Negotiating the Interconnection Parameters

The interconnection parameters of the performance file interface include the user name and
password for the NMS to log in to the M2000, the start time and format of the exported file, and
the fields in the exported file. Table 3-1 lists an example of a group of performance file interface
parameters. The following interconnection operations take this example as a reference.
Table 3-1 Example of interconnection parameters
3-2
Parameter Type
Parameter
Parameter Value
Description
User parameters
User Name
ftpuser
This parameter is not

modifiable.
Password
ftpuser
This parameter is
modifiable.
Export Path
/export/home/omc/
var/fileint/pm
This parameter is not

modifiable.
Content parameter
Selected Function
Subsets
Root node > RNC >

Measurements
related to
Algorithm >
Measurement of
Compressed Mode
per cell
This parameter is
modifiable on the
GUI of the M2000
client.
Format parameters
Start Time
10/11/2008 17:00:00
This parameter is
modifiable on the
GUI of the M2000
client.

Issue 01 (2009-07-30)
M2000
Parameter Type

Parameter
Parameter Value
Description
File Format
CSV
This parameter is
modifiable on the
GUI of the M2000
client.
Query result export

format
The parameter can

distinguish the
data that is
additionally
collected from the
data that is
normally
exported.
This parameter is
modifiable in the
configuration file
of the export tool.
Display the time

zone information.
This parameter is
modifiable in the
configuration file
of the export tool.
Display timezone
offset
information.
This parameter is
modifiable in the
configuration file
of the export tool.
Display time zone

information
Display timezone
offset information
3.2 Exporting Performance Files (Measurement Unit-Based)

This describes how to export performance files. Before interconnecting the NMS with the
M2000, you need to export the performance files to the specified path. Based on the exported
files, determine whether the M2000 meets the conditions for interconnection with the NMS.
3.2.1 Modifying the Configuration File of the Performance Data Export Tool (Measurement
Unit-Based)
Based on the parameters negotiated with the NMS, you can modify the configuration files of
the performance data export tool.
3.2.2 Setting an Performance Export Task (Measurement Unit-Based)
This describes how to set a task of automatically exporting performance data files on the
M2000 client.
3.2.3 Checking Exported Performance Files (Measurement Unit-Based)
Issue 01 (2009-07-30)

3-3

M2000
This describes how to obtain and check the exported performance file in the export path. You
can obtain the exported performance file from the export path. Compare parameters in the
exported file and the negotiated parameters. If the parameters in the exported file are consistent
with the negotiated parameters,you can infer that the generated performance export file is correct.
3.2.4 Commissioning the Interconnection of the Performance File Interface (Measurement UnitBased)
This describes how to simulate the NMS to obtain the performance file generated by the
M2000 through the FTP. According to the obtained performance file, you can determine whether
the northbound performance file interface meets the conditions for interconnecting with the
NMS.
3.2.5 Usage of the Performance File Interface (Measurement Unit-Based)
This describes how to use the performance file interface when the M2000 system adopts different
networking modes.
3.2.1 Modifying the Configuration File of the Performance Data

Export Tool (Measurement Unit-Based)
Based on the parameters negotiated with the NMS, you can modify the configuration files of
the performance data export tool.
Prerequisite
You have logged in to the M2000 server as user root.
Procedure
Step 1 Run the following commands to open the configuration file:
# cd /export/home/omc/var/etc/PMExport
# 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"/>
<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"
TransmitMode="2"/>
<GZip Name="Compress file or not." Value="0"/>
<TemplateMode Name="Template File Name Format" Value="0"/>
</GeneralSet>
<EffectiveSet>
<PMDBConnNum Name="PMDB database connection number." Value="10"/>
<MethodThreadNum Name="Active method's thread number." Value="2"/>
<TableThreadNum Name="Process table's thread number." Value="3"/>
3-4

Issue 01 (2009-07-30)
M2000

<BulkReaderNum Name="Bulk read record number." Value="5000"/>

</EffectiveSet>
Step 2 Modify configuration items.

Based on the negotiated parameters listed in Table 3-1, the modified configuration items are as
follows:
<DisplayDstOffSet Name=""Display timezone offset information." Value="1"/>
NOTE
For meanings of the configuration items, see 2.4.1 Modifying the Configuration File of the Performance
Data Export Tool (Measurement Unit-Based).
Step 3 Press Esc and run the :wq! command. Save the file and exit the vi editor.
Step 4 Restart the performance data export tool for the modifications to take effect.
# svc_adm -cmd restartsvc PMExport
After restarting the tool, execute the following command to check whether the tool is running
properly:
# svc_adm -cmd status | grep PMExport
If the system returns the following message, you can infer that the performance data export tool
runs properly.
PMExport
[running
----End
3.2.2 Setting an Performance Export Task (Measurement UnitBased)

This describes how to set a task of automatically exporting performance data files on the
M2000 client.
Prerequisite
You have logged in to the M2000 client.
Procedure
Step 1 Choose Maintenance > Task Management. The Task Management window is displayed.
Step 2 From the navigation tree on the left, choose File Interface > Performance Data Export to
view a task record.
Step 3 Double-click the task record to view the Attribute dialog box. Set relevant parameters by
referring to Table 3-2.
Table 3-2 Parameter setting
Issue 01 (2009-07-30)
Tab
Parameter
Parameter Value
Common Parameters
Task Name
Export the performance data.

3-5
M2000

Tab
Extended Parameters
Parameter
Parameter Value
Start Time
10/11/2008 17:00:00
File Format
CSV
Hold Days
Export Period
15 minutes
Delay Time(Minute)
Function Subsets
Display the subset for the

measurement.
Selected Function Subsets
Root
node>RNC>Measurements
related to
Algorithm>Measurement of
Compressed Mode per cell
NOTE
The start time must be later than the current time of the server.
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.
The style of files exported by Function Subsets is different from the style of files exported by
Template. Templates are created when you query the performance result.
Step 4 Click OK to save the export task.

The export tool can export files based on the export task on schedule.
----End
3.2.3 Checking Exported Performance Files (Measurement UnitBased)

This describes how to obtain and check the exported performance file in the export path. You
can obtain the exported performance file from the export path. Compare parameters in the
exported file and the negotiated parameters. If the parameters in the exported file are consistent
with the negotiated parameters,you can infer that the generated performance export file is correct.
Context
The northbound file interface allows you to obtain files through the SFTP or FTP. This section
takes the FTP as an example.
Procedure
Step 1 Check whether any performance export file is generated.
3-6

Issue 01 (2009-07-30)
M2000

Check whether any performance export file is generated in the /export/home/omc/var/fileint/

pm/ directory. If no performance export file is generated, see 4 Troubleshooting for the
Northbound Performance File Interface (Measurement Unit-Based).
Step 2 Obtain the performance export file from the /export/home/omc/var/fileint/pm/ directory.
All the performance export files are saved to the /export/home/omc/var/fileint/pm/ directory
by default. If the directory does not exist, the export tool can create the directory automatically
during the export.
Step 3 Check whether the performance export file is generated based on the negotiated parameters. If
yes, you can infer that the file is correct.
Obtain the performance file
pmresult_1275072017_15_200811101500_200811101515_recover_200811101700.csv as
shown in Figure 3-1. Based on the filename,you can infer that the data in the file is collected at
17:00,which is not collected from 15:00 to 15:15. The data is consistent with the preset
parameters. This indicates that the performance export file is correct.
Figure 3-1 Exported performance file
----End
3.2.4 Commissioning the Interconnection of the Performance File

Interface (Measurement Unit-Based)
This describes how to simulate the NMS to obtain the performance file generated by the
M2000 through the FTP. According to the obtained performance file, you can determine whether
the northbound performance file interface meets the conditions for interconnecting with the
NMS.
Prerequisite
The communication between the NMS and the M2000 is normal.
Context
The NMS can use either of the following methods to obtain performance file:
l
The NMS uses the FTP to obtain the file from the specified path of the M2000 server.
The M2000 uploads the file to the NMS.

NOTE
This part takes the first method as an example.
Procedure
Step 1 Under the Microsoft Windows operating system, choose Start > Run. In the dialog box, enter
ftp IP address of the M2000 server to enable the FTP login.
Issue 01 (2009-07-30)

3-7

M2000
Step 2 Enter the user name and password of the FTP.

Step 3 Download the performance file from the specified path of the M2000 server to the specified
local path in ASCII mode. In this case, the specified path is D:\.
For example:
ftp>
ftp>
ftp>
ftp>
ftp>
cd /export/home/omc/var/fileint/pm/pmexport_20081110
lcd d:\
asc
get pmresult_1275072017_15_200811101500_200811101515_recover_200811101700.csv
quit
Step 4 Check the downloaded performance file.

For details, see 3.2.3 Checking Exported Performance Files (Measurement Unit-Based). If
the performance file is generated according to the negotiated parameters, you can infer that the
northbound performance file interface meets the interconnection conditions.
----End
3.2.5 Usage of the Performance File Interface (Measurement UnitBased)

This describes how to use the performance file interface when the M2000 system adopts different
networking modes.
The M2000 system can adopt the following networking modes: single-server system, HA
system, remote HA system, and SLS system. For details about how to use the northbound
performance file interface in different networking modes, see Table 3-3.
Table 3-3 Usage of the performance file interface
3-8
M2000 System Type
Use Reference
Single-server system
Refer to this document.
HA system
Refer to this document.
Remote HA system
Refer to this document and the relevant

documents of the remote HA system.
SLS system
Refer to this document and the relevant

documents of the SLS system.

Issue 01 (2009-07-30)
M2000
4 Troubleshooting for the Northbound Performance File

Troubleshooting for the Northbound
Performance File Interface (Measurement UnitBased)

About This Chapter
The NMS interconnects with the M2000 through the northbound performance file interface. If
a fault occurs when the NMS is obtaining performance data, refer to relevant troubleshooting
methods in this chapter.
4.1 Common Troubleshooting and Information Collection (Measurement Unit-Based)
If a fault occurs when the NMS attempts to obtain performance data through the northbound
performance file interface, handle the fault according to common troubleshooting methods. If
it is not possible to handle the fault by using common troubleshooting methods, collect
information about the fault and contact Huawei engineers for assistance.
4.2 Troubleshooting the Performance File Export Failure (Measurement Unit-Based)
This describes how to troubleshoot the 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) Free disk space is
unavailable on the M2000 server.
4.3 Troubleshooting the Failure of DST Identification
This describes how to handle the situation when the DST offset displayed in the name of an
exported file does not refer to the DST.
Issue 01 (2009-07-30)

4-1

M2000
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 according to common troubleshooting methods. If
it is not possible to handle the fault by using common troubleshooting methods, collect
information about the fault and contact Huawei engineers for assistance.
Common Troubleshooting
For the methods of handling common faults that may occur during the process of obtaining
performance data for the NMS, see Table 4-1.
Table 4-1 Common troubleshooting
Common Fault
Troubleshooting Method
The performance file is not exported.
See 4.2 Troubleshooting the Performance

File Export Failure (Measurement UnitBased).
Information Collection
If an unusual fault occurs when the NMS is obtaining performance data, you need to collect the
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
4-2
Related Information
Description
Operation information
Record the operations performed before a

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

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

servers from each office.
Log information
You can obtain logs from the /opt/OMC/

var/logs path. The .trace file in the
PMExport directory is
iMAP.pmexp_agent.trace.
You can obtain the performance export file

from the /export/home/omc/var/fileint/
pm/ path.

Issue 01 (2009-07-30)
M2000

4.2 Troubleshooting the Performance File Export Failure

This describes how to troubleshoot the 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) Free disk space is
unavailable on the M2000 server.
Symptom
No performance files exist in the export path. The NMS cannot obtain the performance data of
the NE.
Troubleshooting
Generally, the export of performance files fails due to the following causes:
l
The performance data export service is not started.
No NE data exists in the performance result report.
Data of certain NEs fails to be saved to the database within the specified period.
The NE time zone is incorrect.
NEs are disconnected.
Free disk space is unavailable on the M2000 server.
Handling the Fault of Performance Export Service Inactivation

View the status of the performance data export service. Check whether the service is started. If
the service is not started, run the relevant commands to start it.
1.
You have logged in to the M2000 server as user root.
2.
Check the status of the performance export service.

# cd /opt/OMC
# svc_adm -cmd status
If the following message is displayed, you can infer that the service is activated.
PMExport [running
3.
If the service is not started, run the following command to start it:
# svc_adm -cmd startsvc PMExport
Handling the Fault of NE Data Unavailability

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 M2000 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. Do as follows to determine the specific cause:
Issue 01 (2009-07-30)

4-3

1.
M2000
On the M2000 client, choose Maintenance > Task Management. The Task
Management window is displayed.
NOTE
The M2000 displays the 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 the Fault of Data Saving Timeout

Do as follows to check whether certain data fails to be saved to the database within the specified
period.
1.
If the northbound interface delays exporting the export file, check whether the export file
is generated at a full hour. If the generation time is a little later than the full hour, you can
infer that the file is generated because of 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 check whether any data fails to be saved to the
database within the specified period.
(1) Query the performance result report.
Determine the name of the result report according to the number of the function subset
and the measurement period. The result report is named in the following format:
tbl_Result_subset number_measurement period. The measurement period can be 0,
1, 2, 3, and 4, which indicates 5, 15, 30, 60, and 1440 minutes, respectively.
(2) Query the result report by using the SQL sentence. You can execute the SQL sentence
on the M2000 server to obtain all the results of 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. 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, the northbound interface delays exporting the data to a file, or the
northbound interface exports the data to a file on schedule but the file is incomplete,
while 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 the 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 the 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 according the query result of the performance result
report.
l
4-4
If the difference between 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.
Issue 01 (2009-07-30)
M2000

If the difference between 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.
If the difference between InsertTime and SvrEndTime of all the measurement objects is
greater than the specified time for supplementary collection, no export file is generated.
Handling the Fault of Incorrect NE Time Zone

Based on the query result of the performance result report, determine whether the performance
file export failure is caused due to the 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

original SQL sentence with
StartTime.
If the performance result

report can be queries, it
indicates that the time zone of
all the NEs in this subset is
incorrect.
Yes
Compare StartTime with

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

TimezoneOffset of the NE.
For example, if the value of
TimezoneOffset is 480, it
indicates the eighth time zone
(480/60 = 8).
If the time zone is not the

actual time zone of the NE, it
indicates that the time zone of
the NE is incorrect.
Handling the Fault of NE Disconnection

1.
On the M2000 client, choose Topology > Main Topology. In the Main Topology window,
right-click the disconnected NE and then choose Reconnect NE.
2.
Check the network and rectify the network fault.
3.
Rectify the fault on the NE mediation. If you have to reinstall the NE mediation, see the
Commissioning Guide of the corresponding M2000 networking mode.
Handling the Fault of disk space insufficiency of the M2000 server

Clear the disk space of the M2000 server.
Issue 01 (2009-07-30)

4-5

M2000
CAUTION
You must check whether the files can be deleted when clearing the disk space. If you delete a
file by mistake, the system may fail to run properly. You are advised to clear the disk space by
referring to the Administrator Guide of the corresponding M2000 networking mode.
Solution
Contact Huawei engineers for assistance.
4.3 Troubleshooting the Failure of DST Identification

This describes how to handle the situation when 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 is both set to 0, if NEs and the M2000
server are in different time zones, for example, NE1 and NE2 are respectively located in
the time zones GMT+4:00 and GMT+10:00 and the M2000 server is in GMT+8:00, the
result file is exported according to the GMT+8:00 of the server and the contents of the result
file are displayed according to NE time.
In this case, set QueryTimeMode to 1. Then, the results are exported according the time of
the M2000 server.
2.
Suppose the M2000 is in the time zone GMT-5. The DST rule of 2006 specifies that you
should set the time one hour earlier from 02:00 on April 2nd to 02:00 on October 29th.
That is, set the time 02:00 to 03:00 on April 2nd, and then set the time 02:00 to 01:00 on
October 29th. For the period from 01:00 DST to 02:00 on October 29th, the rule for
exporting results of this repeated period is as follows:
l
When QueryExportFormat is set to 0 and QueryTimeMode is set to 0 or 1, if the

M2000 is in DST, the results of the last one or two periods from the time 01:00 DST
on October 29th to the time 01:00 DST on October 29th are exported with one hour
delay. The results generated in the period from 01:00 DST on October 29th to 02:00
DST on October 29th and in the period from 01:00 on October 29th to 02:00 on October
29th are exported in the same file. The DST identifies the period to which the data
belong.
When QueryExportFormat is set to 1 and QueryTimeMode is set to 0 or 1, if the

M2000 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 an 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 QueryExportFormat and QueryTimeMode both to 1. Then, the results are
exported according the time of the M2000 server.
4-6

Issue 01 (2009-07-30)
M2000
Index
Index
D
DST, 2-10
E
EMS, 1-2
I
interface
Northbound interface, 1-2
M
M2000, 1-2
modifying
configuration file of the performance data export
tool, 2-10
N
NMS, 1-2
P
performance export
file
category and quantity, 2-6
naming rule, 2-6
path, 2-6
operation
start, 2-15
stop, 2-15
tool, 2-2
configuration file, 2-2
Issue 01 (2009-07-30)

i-1

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

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

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

Hochgeladen von

Copyright:

Verfügbare Formate

M2000

M2000 Northbound Performance File Interface

Huawei Proprietary and Confidential

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

Trademarks and Permissions

Huawei Proprietary and Confidential

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

3 Interconnection Commissioning of the Northbound Performance File Interface

4 Troubleshooting for the Northbound Performance File Interface (Measurement UnitBased)...............................................................................................................................................4-1

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

About This Document

About This Document

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

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

Book titles are in italics.

Examples of information displayed on the screen are in

Huawei Proprietary and Confidential

About This Document

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

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

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

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Huawei Proprietary and Confidential

About This Document

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

1 Introduction to Northbound Performance File Interface

Introduction to Northbound Performance

About This Chapter

Huawei Proprietary and Confidential

1 Introduction to Northbound Performance File Interface

1.1 Definition of Northbound Interface

1.2 Definition of Northbound Performance File Interface

Huawei Proprietary and Confidential

2 Introduction to Performance Data Export Tool and File

Introduction to Performance Data Export

About This Chapter

Huawei Proprietary and Confidential

2 Introduction to Performance Data Export Tool and File

2.1 Performance Data Export Tool (Measurement UnitBased)

2.2 Configuration file of the Performance Data Export Tool

The following part describes the configuration items:

Huawei Proprietary and Confidential

2 Introduction to Performance Data Export Tool and File

If the value of CounterValueFormat is set to 0, the counter values of the measurement

2 Introduction to Performance Data Export Tool and File

If the value of CounterValueFormat is set to 2, none of the counter values in the