U2000 Northbound Performance File Interface Developer Guide (NE-Based)

U2000
V200R015C10
Northbound Performance File

Interface Developer Guide (NE-
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
(NE-Based) About This Document
About This Document
Scope
This document provides information about the U2000 northbound performance file interface. It
also provides guidance 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, the
change is:
Added the introduction of export OSS performance items.
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential ii

U2000
Organization
1 Overview of Northbound Performance File Interface
This chapter defines the northbound interface and the northbound performance file interface
provided by the U2000.
2 Interconnection Commissioning of Northbound Performance File Interface
This chapter describes the process for interconnecting the NMS with the U2000 northbound
performance file interface.
3 Introduction to Performance Result Export Files
This chapter describes the performance result files that are exported by NE and the parameters
of performance result export services.
4 Troubleshooting Northbound Performance File Interface
The NMS interconnects with the U2000 through the northbound performance file interface. If
a fault occurs when the NMS attempts to obtain performance data, rectify the fault by referring
to the relevant troubleshooting suggestions given in this chapter.
5 Appendix
This chapter provides reference information about the northbound performance file interface.
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.
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential iii

U2000
Symbol Description
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
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
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential iv

U2000
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.
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
(NE-Based) Contents
Contents
About This Document.....................................................................................................................ii

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

2.1 Checking License (Performance File Interface).............................................................................................................7
2.2 Negotiating Interconnection Parameters of Performance File Interface........................................................................7
2.3 Modifying Parameters of Performance Export Services..............................................................................................14
2.4 Starting Performance Export........................................................................................................................................17
2.5 (Optional) Configuring the U2000 for Actively Uploading Files over the Northbound Interface...............................20
2.5.1 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Public and Private Keys)
............................................................................................................................................................................................20
2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication)
............................................................................................................................................................................................32
2.6 (Optional)Stopping Performance Export......................................................................................................................39
2.7 Verifying Interconnection.............................................................................................................................................42
3 Introduction to Performance Result Export Files..................................................................44

3.1 Description of Performance Result Export Files..........................................................................................................45
3.1.1 Examples of Performance Result Export Files..........................................................................................................45
3.1.2 Path of Performance Result Export Files..................................................................................................................45
3.1.3 Default Naming Convention of Performance Result Export Files............................................................................46
3.1.4 User-defined Naming Convention of Performance Result Export Files...................................................................50
3.1.5 Format of Performance Result Export Files..............................................................................................................52
3.1.6 Storage Specification of Performance Result Export Files.......................................................................................55
3.2 Configuration File of Performance Result Export Services.........................................................................................55
4 Troubleshooting Northbound Performance File Interface.................................................58

4.1 Common Troubleshooting and Information Collection...............................................................................................59
4.2 Troubleshooting Performance File Export Failure.......................................................................................................60
4.3 How to Set Northbound Interface Compatibility.........................................................................................................61
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential vi

U2000
(NE-Based) Contents
4.4 How to Set Parameters in a Northbound Configuration File........................................................................................62
5 Appendix.......................................................................................................................................64
5.1 NEs Supported by Performance File Export................................................................................................................65
5.2 Measurement Attributes of an NE................................................................................................................................69
5.3 Method of Obtaining Performance Counter Files of NEs............................................................................................70
5.4 Method of Transferring Data Using PSFTP.................................................................................................................70
5.5 Checking the Sybase Database Server Name...............................................................................................................70
Issue Draft A (2015-01-15) Huawei Proprietary and Confidential vii

U2000
(NE-Based) 1 Overview of Northbound Performance File Interface
1 Overview of Northbound Performance File

Interface
About This Chapter
This chapter defines 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 the Northbound Performance File Interface

The U2000 northbound performance file interface is a type of northbound interface. The NMS
obtains performance data (including the OSS performance measurement data) of NEs through
the northbound performance file interface.
1.3 Using the Northbound Performance File Interface

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

This section describes the technical specifications related to the northbound performance 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 the Northbound Performance File

Interface
The U2000 northbound performance file interface is a type of northbound interface. The NMS
obtains performance data (including the OSS performance measurement data) of NEs through
the northbound performance file interface.
The NMS can use either of the following methods to obtain northbound performance files:
l PULL: The NMS uses SFTP to obtain files from a specified path of the U2000 server.
l PUSH: The U2000 automatically uploads files to a specified path of the NMS.
U2000 northbound file transfer supports the following protocols: SSH-based FTP.SFTP uses
public-key/private-key encryption to encrypt data in the network. Data communication between
two ends can therefore be performed in an encrypted channel.
The U2000 northbound performance file interface uses 3GPP TS 32.435 V7.2.0 specifications.
For details about how to view the specifications and version, see fileFormatVersion
descriptions in Format of Performance Result Export Files.

U2000
1.3 Using the Northbound Performance File Interface

This section describes how to use the northbound performance file interface when the U2000
system adopts different networking modes.
For details about how to use the northbound performance interface in different networking
modes, see Table 1-1.
Table 1-1 Usage of the northbound performance file interface
U2000 System NMS and U2000 Method for the NMS to Obtain
Type Interconnection Solution Performance Files
Single-server Perform interconnection on Obtain performance files on the

system the U2000 server. U2000 server.
HA System Perform interconnection on Obtain performance files on the active

the active U2000 server. U2000 server.
Remote HA
OSS performance export files can be
system
obtained on the active U2000 server.
SUN-based SLS Perform interconnection on Obtain performance files from each

system the master and slave U2000 U2000 server where the
servers. MediationService service is deployed.
obtained on the master U2000 server.
ATAE cluster Perform interconnection on Obtain performance files from each

system the master and slave U2000 U2000 server where the
servers. MediationService service is deployed.
ATAE cluster Perform interconnection on Obtain performance files from each

online remote HA the master and slave servers of U2000 server where the
system the active and standby MediationService service is deployed.
U2000 sites. OSS performance export files can be
1.4 Technical Specifications of Northbound Performance

File Interface
This section describes the technical specifications related to the northbound performance file
interface.

U2000
Item Value
Maximum re-upload attempts that are permitted after 3

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

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

upload
Maximum delay in exporting the performance result 10

of a collection task (collection period: 15 minutes)
through the northbound performance file interface


Maximum days within which performance export files 7

can be saved on the U2000

U2000
Northbound Performance File Interface Developer Guide 2 Interconnection Commissioning of Northbound
(NE-Based) Performance File Interface
2 Interconnection Commissioning of
Northbound Performance File Interface
About This Chapter
This chapter describes the process for interconnecting the NMS with the U2000 northbound
performance file interface.
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 Interconnection Parameters of Performance File Interface

This section describes the preparations for interconnecting the U2000 with the NMS.
2.3 Modifying Parameters of Performance Export Services

Modifying parameters is mandatory. This section describes how to modify parameters of
performance export services according to the negotiated parameters.
2.4 Starting Performance Export

Starting performance export is mandatory. This section describes how to set NE types and
measurement periods for performance export. You can start performance export using
commands or using the OSMU.
2.5 (Optional) Configuring the U2000 for Actively Uploading Files over the Northbound
Interface
The U2000 can actively upload files to the NMS over the northbound interface. You can use
either method to configure the U2000 for actively uploading files to the NMS over the
northbound interface.
2.6 (Optional)Stopping Performance Export

Stopping performance export is optional. This section describes how to stop performance export
of specified NE types with specified measurement periods. You can stop performance export
using commands or using the OSMU.
2.7 Verifying Interconnection

U2000
This section describes how to simulate the NMS to obtain performance files generated by the
U2000 in SFTP mode using the OSMU. You can determine whether the northbound performance
file interface can be interconnected with the NMS according to the obtained performance files.

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 Interconnection Parameters of Performance

File Interface
This section describes the preparations for interconnecting the U2000 with the NMS.
Obtaining Negotiated Interconnection Parameters

The negotiated interconnection parameters are as follows:
l System parameters.
– Solaris operating system: see Table 2-1.
– SUSE Linux operating system and Oracle database: see Table 2-2.
– SUSE Linux operating system and Sybase database: see Table 2-3.
l File save parameters. For details, see Table 2-4.
l NE measurement parameters. For details, see Table 2-5.
l FTP parameters. For details, see Table 2-6.
Table 2-1 System parameters for Solaris operating system
Parameter Value Description
Operating system Solaris -
Database type Sybase -

U2000
Database name l The default database -

server name is DBSVR in
the U2000 single-server
or HA system.
l The default database
server name is DBSVR1
in the SUN SLS and
ATAE Cluster system.
Query Sybase database
name, refer to 5.5 Checking
the Sybase Database Server
Name.
Database user - Contact the U2000

administrator to obtain the
password.
Database password - Contact the U2000

password.
Installation path of the /opt/oss/server You are advised to use the

U2000 server default installation path. If
the installation path has been
changed during the
installation, set this
parameter to the actual
installation path.
Table 2-2 System parameters for SUSE Linux operating system and Oracle database
Operating system SUSE Linux -
Database type Oracle -
Database name ossdb -
Database user itfndb -
Database password The default password of To improve system security,

itfndb is Changeme_123 change the default database
password upon first login and
periodically change the
password. The password
change interval can be
customized as required.

U2000

changed during the
installation path.
Table 2-3 System parameters for SUSE Linux operating system and Sybase dabatase
Operating system SUSE Linux -
Database type Sybase -
Database name l The default database -

server name is DBSVR in
the U2000 single-server
or HA system.
l The default database
server name is DBSVR1
in the SUN SLS and
ATAE Cluster system.
Query Sybase database
name, refer to 5.5 Checking
the Sybase Database Server
Name.
Database user - Contact the U2000

password.
Database password - Contact the U2000

password.

changed during the
installation path.

U2000
Table 2-4 File save parameters
Parameter Default Value Value Range Description
Format of exported XML - Cannot be modified.

files
Days during which 7 1-7 Expired files will be

exported files can be deleted
saved automatically by the
U2000.
For details, see 3.2
Configuration File
of Performance
Result Export
Services.
Delay in regularly 30 0-1439 l The U2000

deleting expired files triggers the timer
(minutes) to delete expired
files after N
minutes of
00:00:00 every
day.
l Method for
converting time
on the timer into
minutes: If you
need to delete
expired files at
02:30:00 every
day, set this
parameter to 150
(2 x 60 + 30 =
150).
l Regularly
deleting expired
files consumes
system resources.
The
recommended
value range is
30-360.
For details, see 3.2
Configuration File
of Performance
Result Export
Services.

U2000
Table 2-5 NE measurement parameters
Parameter Value Range Example Description
NE type name - MSCServerNE Set this parameter to

the actual NE type
name. For the names
of NE types managed
by the U2000, see 5.1
NEs Supported by
Performance File
Export.
Measurement period 15, 30, 60, 1440 60 Set this parameter to

(minute) the actual
measurement period.
Use the measurement
period of actual NEs
to set this parameter.
Table 2-6 FTP parameters
FTP Parameter Value Description
The U2000 serves as FTP user name ftpuser Cannot be modified.

an FTP server
(PULL). Password The default To improve system
password: security, change the
NOTICE
Using SFTP is Changeme_123 default database
recommended password upon first
because of its higher login and
security than FTP. periodically change
the password. The
password change
interval can be
customized as
required.
FTP port 20, 21 If you use FTP to

transmit data, open
the ports on the
U2000.
SFTP port 22 If you use SFTP to

transmit data, open
the port on the
U2000.

U2000
Export path /opt/oss/server/var/ Cannot be modified.

fileint/pmneexport NOTE
In the SUN SLS and
ATAE Cluster
system, the
performance result
export files of NEs are
saved only in the
master server or a
slave server that
manages these NEs.
The performance
result export files of
NEs managed by a
slave server will not
aggregate to the
master server.
The U2000 serves as FTP user name Provided by the For details, see 2.5.2
an FTP client NMS Configuring the
(PUSH). SFTP for Actively
NOTICE Transferring Files
Using SFTP is over the
recommended Northbound
because of its higher Interface
security than FTP.
(Password
Authentication).
Password Provided by the If the northbound

NMS FTP server updates
the password
regularly, modify
FTP server settings.
For details, see 2.5.2
Configuring the
SFTP for Actively
Transferring Files
over the
Northbound
Interface
(Password
Authentication).
FTP port 20, 21 If you use FTP to

transmit data, open
the ports on the
NMS.
SFTP port 22 If you use SFTP to

transmit data, open
the port on the NMS.

U2000
Export path Provided by the For details, see 2.5.2

NMS Configuring the
SFTP for Actively
Transferring Files
over the
Northbound
Interface
(Password
Authentication).
Negotiating File Transfer Protocols

You need to negotiate between the U2000 and NMS to determine whether PUSH or PULL be
used. You also need to negotiate between the U2000 and NMS to determine whether FTP or
SFTP be used. You can then prepare for the interconnection according to the negotiated results
by referring to Table 2-7.
Table 2-7 Guidance for setting file transfer
Mode FTP SFTP
PUSH: the For details, see Step 7 of For details, see 2.5.1 Configuring the SFTP
U2000 2.5.1 Configuring the for Actively Transferring Files over the
automatically SFTP for Actively Northbound Interface (Public and Private
uploads files Transferring Files over Keys) or 2.5.2 Configuring the SFTP for
the Northbound Actively Transferring Files over the
Interface (Public and Northbound Interface (Password
Private Keys). Authentication).
PULL: the If you use FTP to transfer The U2000 uses SFTP to transfer files by
NMS directly files, enable FTP by default.
obtains files referring to the section
"Configuring the FTP
Transmission Policy"
described in the
corresponding U2000
Administrator Guide.
Obtaining the Performance Counter File of an NE

Contact Huawei technical support to obtain the performance counter file of an NE. For details,
see 5.3 Method of Obtaining Performance Counter Files of NEs.

U2000
Checking Performance Measurement

Northbound performance files are exported based on the performance measurement set on the
U2000. Perform the following steps to ensure that performance measurement has been set
correctly on the U2000:
1. Query measurement attributes of an NE.

Query measurement attributes such as default measurement counters, default measurement
period, and report by all counters. For details, see 5.2 Measurement Attributes of an
NE.
2. If you do not set performance measurement, northbound performance files can still be
exported when the following requirements are met. Determine whether these requirements
are met by referring to 5.2 Measurement Attributes of an NE.
a. The specified counters to be measured are included in the default measurement
counters.
b. The specified measurement period is the default measurement period of the NE.
c. The default performance measurement is not modified or the NE still reports
measurement results of all counters even if the measurement of some counters has
been canceled.
3. If any NE type does not meet these requirements, perform the following steps to ensure
that performance measurement has been set correctly on the U2000:
a. Log in to the U2000 client.
b. Choose Performance > Measurement Management (traditional style);
alternatively, double-click Performance in Application Center and choose
Measurement > Measurement Management (application style) . Confirm the
measurement counters that are specified by the NMS have been set to performance
measurement in the specified measurement period.
NOTE
The U2000 does not export user-defined counters on the U2000 client.
File Examples
You can obtain the examples of performance result export files of some common NE types from
the 07.Northbound File\File Interface\Sample File\Performance File (NE-Based)
northbound interface document directory.
Contact Huawei technical support to obtain the examples of performance result export files of
specified NE types.
2.3 Modifying Parameters of Performance Export Services

Modifying parameters is mandatory. This section describes how to modify parameters of
performance export services according to the negotiated parameters.
Context
You can use either of the following methods to modify parameters of performance export
services:

U2000
l Modifying parameters of performance export services using commands

l Modifying parameters of performance export services using the OSMU
Parameters of performance export services are saved in the /opt/oss/server/etc/

MediationService/MedExpParam.xml configuration file. For detailed description of the
parameters in the configuration file, see 3.2 Configuration File of Performance Result Export
Services.
Procedure
l Modifying parameters of performance export services using commands
NOTICE
l In an SLS system, you need to perform the following steps only on the master and slave
servers and do not need to perform them on the standby server.
l 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 In an ATAE cluster online remote HA system, you need to perform the following steps
only on the master and slave servers (include active site and standby site) and do not
need to perform them on the standby server.
1. Log in to the U2000 server as user ossuser.

2. Run the following commands to open the MedExpParam.xml configuration file:
-bash-3.00$ . /opt/oss/server/svc_profile.sh
-bash-3.00$ vi /opt/oss/server/etc/MediationService/MedExpParam.xml
Find the following two lines in the configuration file:

<FileSaveDay Name="Export file saving days" Value="7"/>
<DelDelayTime Name="Delete export files time offset from 0:00" Value="30"/>
3. Modify the MedExpParam.xml configuration file.

Modify the configuration items according to the negotiated parameters. The modified
configuration items are as follows:
4. Press Esc, and then run the :wq! command to save the modification and exit the vi
editor.
5. On the servers on which MediationService is deployed, run the following command
to query the names of the current MediationService:
-bash-3.00$ svc_adm -cmd status | grep MediationService
The following command output is used as an example, the names of the current
MediationService are MediationService0101, MediationService0102, and
MediationService0105.

U2000
MediationService0101 [running ]
6. Run the following commands to restart MediationService:
-bash-3.00$ svc_adm -cmd restartsvc MediationService0101

7. Run the following command to check whether the services are running properly:
If the system displays the following information, performance export services are
running properly.
l Modifying parameters of performance export services using the OSMU of the master
server (include the master server of site).
1. Start the Internet Explorer, type http://IP address of the U2000 server:8090 or
https://IP address of the U2000 server:31123 in the Address bar, and then press
Enter.
2. Log in to the OSMU as user ossuser.
3. Click NBI Management in the main window of the OSMU.
4. Choose NBI Management > Centralized Management > Northbound
Configuration Parameters Settings from the navigation tree in the left pane. The
Northbound Configuration Parameters Settings interface is displayed.
5. Select Northbound Performance File Interface (NE-Based) from the Northbound
Interface Name drop-down list.
6. Select MedExpParam.xml - Basic from the Configuration file name drop-down
list, modify parameters of performance export services according to the negotiated
parameters.
For detailed description of the parameters, see 3.2 Configuration File of
Performance Result Export Services.
7. Click Save after the modification is complete.
8. Select MedExpParam.xml - Advanced from the Configuration file name drop-
down list, modify parameters of performance export services according to the
negotiated parameters.
For detailed description of the parameters, see 3.2 Configuration File of
Performance Result Export Services.
9. Click Save&Restart after the modification is complete.
You can view the progress of service restart in the Service Restarted Log area. The
modified parameters take effect after all relevant services are restarted.
----End

U2000
2.4 Starting Performance Export

Starting performance export is mandatory. This section describes how to set NE types and
measurement periods for performance export. You can start performance export using
commands or using the OSMU.
Context
l You can use either of the following methods to start performance export:
– Starting performance export using commands
– Starting performance export using the OSMU
l Performance export files can be exported over the northbound interface only after you start
performance export.
l The minimum granularity you can set for performance export is NE type. After you set an
NE type and measurement period, all measurement results of the NE type in the specified
period will be exported over the northbound interface.
l For the AP Manager, you need to start performance export services only on NEs and you
can ignore the following steps performed on the U2000. For details, see the AP Manager
VXXXRXXX Northbound Performance File Interface.
NOTICE
l In an SLS system, you need to perform the following steps only on the master server and
do not need to perform them on the slave or standby server.
l 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.
only on the master server (include active site and standby site) and do not need to perform
them on the slave or standby server.
Procedure
l Starting performance export using commands
2. Start the performance export script.
– On a Sun or ATAE(Sybase) platform, the default installation directory of the
U2000 server is /opt/oss/server, database server name is DBSVR, and user name
is database administrator. The default password is Changeme_123, run the
following commands:
-bash-3.00$ config_med_export.sh

U2000
NOTE
When the Sybase database is used, the user must be database administrator and the default
password is Changeme_123. The default database server name is DBSVR in the U2000 single-
server or HA system and the default database server name is DBSVR1 in the Sun-based SLS
system and ATAE Cluster system. For details about how to query the name of the Sybase
database, see 5.5 Checking the Sybase Database Server Name.
To improve system security, change the default database password upon first login and
periodically change the password. The password change interval can be customized as required.
The system displays the following information:
Please input Database dbServer: DBSVR
Please input Database userName: database administrator
Please input Database password:
Please wait for a second while loading the tool...
Welcome To Med Export Service Configuration Tool
======================================================
Please select an operation type
1--Current Measurement Display
2--New Measurement Set
3--Exit
======================================================
Please select one operation [default is 3] :
– On a HP or ATAE(Oracle) platform, the default installation directory of the

U2000 server is /opt/oss/server, database server name is ossdb, and user name is
itfndb. The default password is Changeme_123, run the following commands:
ossuser@osssvr-10:~> . /opt/oss/server/svc_profile.sh
ossuser@osssvr-10:~> config_med_export.sh
NOTICE
The user name of Oracle database is itfndb, and its default password is
Changeme_123.
To improve system security, change the default database password upon first login
and periodically change the password. The password change interval can be

Please input Database dbServer: ossdb
Please input Database userName: itfndb
======================================================
3--Exit
======================================================
where,
– 1: To view the preset types of NEs to be measured and their measurement periods.
– 2: To set a new measurement.

U2000
– 3: To exit.
3. Set operation types according to the actual requirement.
This section uses setting a new measurement as an example. Type 2.

New Measurement Set
======================================================
1--Show Available Measurements
2--Active Measurements
3--Deactive Measurements
4--Return to Main menu
======================================================
where,
– 1: To view the measurements that can be set currently.
– 3: To cancel a measurement.
– 4: To return to the main menu.
4. Set a measurement export.
This section uses setting a new measurement export as an example. Type 2.

Active Measurements
======================================================
Please input NeTypeName [default or 'b' to exit current menu] :
5. Type an NE type name to be set.
For example, if you want to set the NE type of MSCServer, type MSCServerNE.

Please input Period (like '60' means 60 minutes period) [default or 'b' to
exit current menu] :
6. Set the measurement period.
You can set only one measurement period at a time. For example, if you want to set
the period to 60 minutes, type 60.

You want active MSCServerNE with 60 minutes period, please input 'y' to
confirm, 'n' to ignore :
7. Confirm the settings.
After confirming the previous settings, type y.

8. Perform the following operations according to the actual requirement:
If you need to... Then...
Continue the settings Perform Step 5 to Step 8.

U2000
End the settings Type b to return to the previous step. Type 4 to return to the main
menu. Type 3 to exit the performance export script.
l Starting performance export using the OSMU of the master server (include the master
server of active site and standby site)
Enter.
6. Select tbl_MedExportMeas from the Configuration file name drop-down list, select
measurement periods for one or more NEs.
7. Click Update Measurements to start performance export.
----End
2.5 (Optional) Configuring the U2000 for Actively

Uploading Files over the Northbound Interface
The U2000 can actively upload files to the NMS over the northbound interface. You can use
either method to configure the U2000 for actively uploading files to the NMS over the
northbound interface.
2.5.1 Configuring the SFTP for Actively Transferring Files over the
Northbound Interface (Public and Private Keys)
When the U2000 server actively uploads files to the NMS over the northbound interface, the
U2000 server functions as an FTP client and the NMS functions as an FTP server. To ensure
data security during file transmission, you can set the SFTP encryption mode. If the U2000 server
is upgraded to V200R015C00 or a Later Version, please reconfigure the SFTP for actively
transferring files over the northbound interface according to this chapter.
Prerequisites
l Use PuTTY to log in to the U2000 server in SSH mode as user ossuser.For an HA system,
you have logged in to the active and standby servers.For a remote HA system, you have
logged in to the active and standby servers.For an SLS system, you have logged in to all
servers. For an advanced telecommunications application environment (ATAE) cluster
system, you have logged in to each server in the U2000 cluster. For an HA system, you
have logged in to the active and standby servers. For an ATAE cluster system, you have

U2000
logged in to each server in the U2000. For an HA or remote HA system, you have logged
in to the active and standby servers. For an SLS system, you have logged in to each server.
l You have logged in to the NMS server as user UserA.
UserA is the NMS server user. Replace it as required.
Context
l To set up an SFTP connection using public or private key authentication, save the U2000
server's public key file in the authorized_keys file of the related NMS server user. The
system performs authentication using the U2000 server's private key and the U2000 server's
public key stored on the NMS server. After the authentication is successful, the SFTP
connection is set up successfully. The U2000 server is not required to provide the NMS
login password.
l The public and private key authentication files can be encrypted or not. For encrypted public
and private key authentication files, set the password. If you forget the password, all public
and private key authentication files must be generated again, and the new files will replace
the existing files.
l Unless otherwise specified, perform the following operations on each server:
NOTE
l XFTPService0X01 indicates the XFTP service name of the U2000 server. Replace it as required.
l For a single-server system, the XFTP service name is XFTPService0101.The service is deployed
on the active server. The service name is XFTPService0101.The service is deployed on the active
and standby servers. The service name is XFTPService0101. For an SLS system, the service is
deployed on the master and slave servers. The service name for the master server is
XFTPService0101. The service name for the first slave server is XFTPService0201. The service
name for the second slave server is XFTPService0301. This method applies to the service names
for other servers.For an HA system, the service is deployed on the active server, on which the
service name is XFTPService0101. For an SLS system, the service is deployed on the master and
slave servers. The service name for the master server is XFTPService0101. The service name for
the first slave server is XFTPService0201. The service name for the second slave server is
XFTPService0301. This method applies to the service names of other servers. For an HA system,
the service is deployed on the active server. The service name is XFTPService0101. For a remote
HA system, the service is deployed on the active and standby servers. The service name is
XFTPService0101. For an SLS system, the service is deployed on the master and slave servers.
The service name for the master server is XFTPService0101. The service name for the first slave
server is XFTPService0201. The service name for the second slave server is XFTPService0301.
This method applies to other service names of other servers.For the virtual cluster system, the
service is deployed on the master and slave servers. The service name for the master server is
XFTPService0101. The service name for the first slave server is XFTPService0201. The service
name for the second slave server is XFTPService0301. This method applies to the service names
for other servers.
l When the XFTP service uploads files in FTP mode:
– If the northbound server runs the Linux or Unix operating system, use the vsftpd
software whose version is 2.0.5 or later.
– If the northbound server runs the Windows operating system, use the ftpserver service
delivered with the system.

U2000
NOTICE
l In an ATAE cluster online remote HA system, you need to perform the following steps only
on the master and slave servers (include active site and standby site) and do not need to
perform them on the standby server.
Procedure
Step 1 Public and private key files are generated on the U2000.
Generate encrypted Only perform Step 1.1 to Step 1.4.

public and private key
files.
Generate non-encrypted Only perform Step 1.5 to Step 1.8.

public and private key
files.
1. Run the following command on the U2000 server to check whether the .ssh directory exists
in the home directory.
$ cd /export/home/omc/.ssh/
l If No such file or directory is displayed, the .ssh directory is unavailable in the home
directory. Perform Step 1.3 after running the following command:
$ mkdir -p /export/home/omc/.ssh/
l If no command result is displayed, the .ssh directory is available in the home directory.
Perform Step 1.2.
2. Run the following command to check whether the id_rsa_pwd.pub file exists.
$ ls id_rsa_pwd.pub
l If the system displays id_rsa_pwd.pub: No such file or directory, perform Step 1.3
to create a public key file.
l If the system displays id_rsa_pwd.pub, perform Step 2.
3. Run the following command to create encrypted public and private key files.
$ . /opt/oss/server/rancn/bin/ssh-keygen.sh

U2000
If the system displays the following message, enter 1 to create encrypted public and private
key files.
------------------------------------------------------------------
Please select an operation type:
1--Generate PubKey File with Encrypt Key.
2--Generate PubKey File without Encrypt Key.
------------------------------------------------------------------
Please make a choice : 1
If the system displays the following message, enter /export/home/omc/.ssh/id_rsa_pwd.

Generating public/private rsa key pair.
Enter file in which to save the key (/export/ossuser/.ssh/id_rsa):
If the following message is displayed, enter the password twice. When $ is displayed, the
encrypted public key file is generated.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
NOTICE
l Keep the password for future use. If the password is lost, all public and private key files
must be generated again, and the new files will replace the existing files.
l The password can contain 8 to 30 characters, including lowercase letters a to z,
uppercase letters A to Z, digits 0 to 9, and special characters ]@%-=_.}{. To improve
password security, please use the following password policies:
l The password contains at least one uppercase letter.
l The password contains at least one lowercase letter.
l The password contains at least one digit.
l The password contains at least one special character.
4. Run the following commands to modify permission of the public key file.
$ chmod 600 id_rsa_pwd.pub

5. Run the following command on the U2000 server to check whether the .ssh directory exists
in the home directory.
$ cd ${HOME}/.ssh/
directory. After running the following command, perform Step 1.7.
$ mkdir -p ${HOME}/.ssh/
l If no command output is displayed, the .ssh directory is available in the home directory.
Perform Step 1.6.
NOTE
The ${HOME} parameter indicates the home directory of user ossuser.

6. Run the following command to check whether the id_rsa file exists.
$ ls id_rsa

U2000
l If the system displays id_rsa: No such file or directory, perform Step 1.7 to create
public and private key files.
l If the system displays id_rsa, perform Step 2.
7. Run the following command to create non-encrypted public and private key files.
$ . /opt/oss/server/rancn/bin/ssh-keygen.sh
If the system displays the following message, enter 2 to create non-encrypted public and
private key files.
------------------------------------------------------------------
Please select an operation type:
1--Generate PubKey File with Encrypt Key.
2--Generate PubKey File without Encrypt Key.
------------------------------------------------------------------
Please make a choice : 2
If the system displays information similar to the following, the non-encrypted public key
file has been created successfully:
Generating public/private rsa key pair.
Your identification has been saved in id_rsa.
Your public key has been saved in id_rsa.pub.
8. Run the following commands to modify permission of the public key file.
$ chmod 600 id_rsa_pwd.pub
Step 2 Enable public key authentication on the NMS.

1. Log in to the NMS server as user UserA. Run the cd ${HOME}/.ssh/ command to check
whether the .ssh directory exists in the home directory.
directory. After running the mkdir -p ${HOME}/.ssh/ command, perform Step 2.2.
l If no command result is displayed, the .ssh directory is available in the home directory.
Perform Step 2.2.
NOTE
The ${HOME} parameter indicates the home directory of user UserA.

2. Run the ls authorized_keys command to check whether the authorized_keys file exists.
l If the system displays authorized_keys: No such file or directory, run the touch
authorized_keys command to create the authorized_keys file. Then, perform Step
2.3.
l If the system displays authorized_keys, proceed to Step 2.3.
3. Copy the content of the id_rsa.pub or id_rsa_pwd.pub file on the U2000 server to the
authorized_keys file on the NMS server.

U2000
NOTICE
l For a non-encrypted public key file, copy the id_rsa.pub file's content.
If the id_rsa.pub file does not exist, copy the ${HOME}/.ssh/authorized_keys file's
content on the U2000 server.
l For an encrypted public key file, copy the id_rsa_pwd.pub file's content.
a. Run the cat id_rsa.pub or cat id_rsa_pwd.pub command on the U2000 server. The
content of the id_rsa.pub or id_rsa_pwd.pub file is displayed.
b. Run the vi command on the NMS server to write the content of the id_rsa.pub or
id_rsa_pwd.pub file into the authorized_keys file.
NOTICE
l The content to be written into the authorized_keys file cannot contain any line feed. If
any line feed exists, delete it.
l If the authorized_keys file contains any other data, perform a line feed operation. Then,
write the content.
4. Run the vi command to modify the /etc/ssh/sshd_config file and configure SFTP
parameters on the NMS server.
# su - root
Password: Password of user root
# vi /etc/ssh/sshd_config
Table 2-8 lists the parameters to be configured.
Table 2-8 Parameters to be configured for the SFTP
Parameter Value
RSAAuthentication yes
PubkeyAuthentica- yes
tion
AuthorizedKeysFile .ssh/authorized_keys
PasswordAuthentica- yes/no. This parameter specifies whether the password

tion authentication is used when the authentication of the public key
and private key fails. You are advised to set this parameter to
yes.
l yes: password authentication is used.
l no: password authentication is not used.

U2000
Parameter Value
MaxStartups Number of concurrent connections.

The calculation method is as follows:
1. Run the following command to query the number of the
SFTP tasks deployed on the U2000 server:
l If the installed U2000 server software is a Chinese
edition, run the following command:
# vi /opt/oss/server/etc/XFTPService/locale/zh_CN/
TaskInfoCache.xml
l If the installed U2000 server software is an English
edition, run the following command:
# vi /opt/oss/server/etc/XFTPService/locale/en_US/
TaskInfoCache.xml
......
<ftpset>
<dest>10.10.10.10</dest>
<localpath......
<localpath......
</ftpset>
......
The preceding command output is used as an example.

10.10.10.10 indicates the IP address of the northbound
server, and each localpath value corresponds to a task.
Record the number of tasks and enter :q! to exit the vi editor.
2. Run the following command to query the number of threads
occupied by the SFTP tasks:
# cat /opt/oss/server/etc/XFTPService/
ModuleParam.xml |grep TaskThreadNum
<param name="TaskThreadNum">10</param>
The preceding command output is used as an example. 10

indicates the number of threads occupied by the SFTP tasks.
Record the number of threads.
3. The number of concurrent connections is obtained by
multiplying the number of tasks by the number of occupied
threads.
NOTE
If you change the number of SFTP tasks, you must change the number
of concurrent connections at the same time.
5. Perform the following operations on the NMS server to check the SFTP service status.

U2000
If... Then...
The NMS server is The # ps -ef | grep sshd | grep -v grep

running Solaris OpenS root 27748 1 0 Dec 25 ? 2:13 /
usr/local/sbin/sshd
SH has root 21923 27748 0 11:11:31 ?
been 0:02 /usr/local/sbin/sshd -R
installe
l If the command output contains /usr/local/sbin/
d
sshd, the SFTP service is running. Run the
Run the following command to restart the SFTP service:
pkginf
# /etc/init.d/opensshd restart
o
OpenS l If no command output is displayed, the SFTP
SH service has not started. Run the following
comma command to start the SFTP service:
nd, and # /etc/init.d/opensshd start
the
followi
ng
comma
nd
output
is
display
ed:
Securit
y
OpenSSH
OpenSSH
Portabl
e for
Solaris

U2000
If... Then...
No # svcs -a | grep ssh

OpenS online 17:27:13 svc:/network/ssh:defaul
SH has l If the command output contains online, the SFTP
been service is running. Run the following command to
installe restart the SFTP service:
d
# svcadm restart svc:/network/ssh:default
Run the
l If the command output contains disabled, the
pkginf
SFTP service has not started. Run the following
o
command to start the SFTP service:
OpenS
SH # svcadm enable svc:/network/ssh:default
comma
nd, and
the
followi
ng
comma
nd
output
is
display
ed:
ERROR:
informa
tion
for
"OpenSS
H" was
not
found
The NMS server is running # service sshd status

SUSE Linux Checking for service sshd
running
l If the command result contains running, the SFTP

service is running. Run the following command to
restart the SFTP service:
# service sshd restart
l If the command result does not contain running,
the SFTP service is disabled. In this case, contact
Huawei technical support.
The NMS server is running any Contact Huawei technical support.

other OS
Step 3 If you use encrypted public and private key authentication files, perform Step 4. If you use non-
encrypted public and private key authentication files, perform Step 4.
1. Run the following command on the U2000 server to query the password for encrypting the
private key.

U2000
$ . /opt/oss/server/svc_profile.sh
$ XFTPPasswdEncrypt
When the following information is displayed, enter the encryption password twice.
Please Enter Password :
Please Re-enter Password :
NOTICE
l The encryption password must be the same as that in Step 1.3.
l Keep the encryption password for future use. If the encryption password is lost, all
public and private key files must be generated again, and the new files will replace the
existing files.
The following information is displayed. d67A29C93775A68AE21DDAF1052EBBD1 is

the encryption password.
Success. Encrpt passwd :d67A29C93775A68AE21DDAF1052EBBD1
$
2. Use the Vi command to change the values of IsSupportEncrpt, PrivateExKeyFile, and

EncrptKey in the ModuleParam.xml file.
This operation must be performed on each server where the XFTPService0X01 service is
deployed.
$ cd /opt/oss/server/etc/XFTPService
$ vi ModuleParam.xml
Table 2-9 Parameter description
Parameter Description
IsSupportEncrpt Change the value to 1, indicating that the encryption

password transfer mode is supported.
PrivateExKeyFile Set this parameter to the absolute path where the public
key file generated in Step 1.3 is saved, for example, /
export/home/omc/.ssh/id_rsa_pwd.
EncrptKey Enter the queried encryption password, for example,

d67A29C93775A68AE21DDAF1052EBBD1.
3. Run the following command to check whether the config file exists:
$ cd ${HOME}/.ssh/
$ ls config
NOTE
The ${HOME} parameter indicates the home directory of user ossuser.

U2000
l If config:No such file or directory is displayed, the config file does not exist. Perform
Step 3.4 after running the following command:
$ touch ${HOME}/.ssh/config
$ chmod 600 ${HOME}/.ssh/config
l If config is displayed, the config file exists. Proceed to Step 3.4.
4. Run the vi command to add the following contents to the config file:
$ cd ${HOME}/.ssh
$ vi config
IdentityFile /export/home/omc/.ssh/
id_rsa_pwd
IdentityFile ~/.ssh/id_rsa
NOTE
If the config file contains the preceding information, you do not need to modify the config file.
Step 4 Run the Vi command on the U2000 server to change the value of DefaultFTPType in the
ModuleParam.xml file.
deployed.
Search for the DefaultFTPType parameter and change the value to 1.
NOTE
If DefaultFTPType is set to 1, the SFTP encryption mode is used. If DefaultFTPType is set to 0, the
plaintext FTP mode is used.
To change the SFTP encryption mode to the plaintext FTP mode, change the value of DefaultFTPType
to 0 and restart the XFTPService0X01 service.
Using the plaintext FTP mode has security risks, It is recommended that you use the SFTP mode.
<GeneralParams>
…
<param name="DefaultFTPType">1</param>
…
</GeneralParams>
Step 5 Run the following command on the U2000 server to restart the XFTPService0X01 service to
make the modification take effect.
deployed.
$ svc_adm -cmd status | grep XFTP
You can obtain the service name of XFTPService0X01 for the server on which the current
operation is performed from the command output. XFTPService0X01 is used as an example.
Replace it as required.
$ svc_adm -cmd restartsvc XFTPService0X01

U2000
Step 6 Run the following command on the U2000 server to view the XFTPService0X01 service status.
deployed.
l If the XFTPService0X01 service is in the running state in the command output, the service
is running properly.
l If the XFTPService0X01 service is in the not running state in the command output, the
service is not started. When this occurs, contact Huawei technical support.
Step 7 Perform the following operations on the U2000 client to configure FTP server information:
2. 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).
In the Target Server Setting window, the configured FTP server information is displayed.
3. Select an FTP server whose information needs to be configured and click Add.
4. Set the FTP server parameters, as described in Table 2-10.
Table 2-10 Parameters in the Target Server Setting window
Module The module type consists of NBI FM, NBI CM, NBI PM, NBI Inventory,
Type/ CME NBI, CME NCCDM, License Management, NBI Server Backup,
Module NBI Log, EBC Counter, EBC Data, and LTE Trace Data. A module name
Name indicates that the configured FTP server is used to transfer the files
corresponding to the modules in the U2000. For example, if the module
name is northbound alarm, it indicates that the configured FTP server is
used to transfer the files of northbound alarm modules in the U2000
server.
Server IP IP address of the FTP server
User Name User name that is used to log in to the FTP server.
Password Password that is used to log in to the FTP server.
Confirm Enter the password that is used to log in to the FTP server again.
Password
Server Directory for storing a file after it is transferred to the FTP server.
Directory The directory name cannot contain the following special characters: colon
(:), asterisk (*), question mark (?), quotation mark ("), less than (<),
greater than (>), and vertical bar (|).
NOTE
When you log in to the U2000 server as user ftpuser, ensure that the server directory
starts with "/export/home/sysm", for example, "/export/home/sysm/ftproot".

U2000
Source Directory for storing the LTE Trace Data need to be uploaded.
Directory NOTE
This parameter only can be configured when you modify or add a FTP server whose
Module Name is LTE Trace Data.
File Whether to compress a file before transferring it.

Compressio l NONE: Transfer a file without compressing it.
n Type
l ZIP: Transfer a file after compressing it.
5. Click OK. The configuration setting is completed.
The added parameters are saved and displayed in the Target Server Setting window.
6. Choose Software > FTP Auto Upload Management > File Upload Browser (traditional
style); alternatively, double-click System Management in Application Center and choose
Settings > FTP Auto Upload Management > File Upload Browser (application style)
to check the status of the files to be uploaded.
The files to be uploaded and files that fail to be uploaded are displayed in the Upload File
Browser window.
----End
2.5.2 Configuring the SFTP for Actively Transferring Files over the
Northbound Interface (Password Authentication)
When the U2000 server actively uploads files to the NMS over the northbound interface, the
U2000 server functions as an FTP client and the NMS functions as an FTP server. To ensure
data security during file transmission, users can set the SFTP encryption mode.
Prerequisites
l Use PuTTY to log in to the U2000 server in SSH mode as user ossuser. For an HA system,
you have logged in to the active and standby servers.For a remote HA system, you have
logged in to the active and standby servers. For an SLS system, you have logged in to all
servers.For an advanced telecommunications application environment (ATAE) cluster
system, you have logged in to each server in the U2000 cluster.For an HA system, you have
logged in to the active and standby servers. For an ATAE cluster system, you have logged
in to each server in the U2000.For an HA or remote HA system, you have logged in to the
active and standby servers. For an SLS system, you have logged in to each server.
l You have logged in to the NMS server as user UserA.
UserA is an NMS server user. Replace it as required.
Context
l When the password authentication is used, the password for logging in to the NMS server
is required to set up an SFTP connection.
l Unless otherwise specified, perform the following operations on each U2000 server:

U2000
NOTE
XFTPService0X01 indicates the XFTP service name of the U2000 server. Replace it as required.
For a single-server system, the XFTP service name is XFTPService0101.The XFTP service is
deployed on the active server, and the service name is XFTPService0101. The XFTP service is
deployed on the active and standby servers, and the service name is XFTPService0101. For an SLS
system, the XFTP service is deployed on the master and slave servers, and the service name for the
master server is XFTPService0101. The service name for the first slave server is XFTPService0201.
The service name for the second slave server is XFTPService0301. This method applies to the service
names for other servers.For an HA system, the XFTP service is deployed on the active server, and
the service name is XFTPService0101. For an SLS system, the XFTP service is deployed on the
master and slave servers, and the service name for the master server is XFTPService0101. The service
name for the first slave server is XFTPService0201. The service name for the second slave server is
XFTPService0301. This method applies to the service names of other servers.For an HA system, the
XFTP service is deployed on the active server, and the service name is XFTPService0101. For a
remote HA system, the XFTP service is deployed on the active and standby servers, and the service
name is XFTPService0101. For an SLS system, the service is deployed on the master and slave
servers, and the service name for the master server is XFTPService0101. The service name for the
first slave server is XFTPService0201. The service name for the second slave server is
XFTPService0301. This method applies to other service names of other servers.
l When the XFTP service uploads files in FTP mode:
– If the northbound server runs the Linux or Unix operating system, use the vsftpd
software whose version is 2.0.5 or later.
– If the northbound server runs the Windows operating system, use the ftpserver service
delivered with the system.
only on the master and slave servers (include active site and standby site) and do not need
to perform them on the standby server.
Procedure
Step 1 Run the vi command to modify the /etc/ssh/sshd_config file and configure SFTP parameters on
the NMS server.
su - root
Password: Password of user root
# vi /etc/ssh/sshd_config
Table 2-11 lists the parameters to be configured.
Table 2-11 Parameters to be configured for the SFTP
Parameter Value
PasswordAuthentica- yes/no. Set this parameter to yes.

tion l yes: password authentication is used.
l no: password authentication is not used.

U2000
Parameter Value
MaxStartups Number of concurrent connections.

The calculation method is as follows:
1. Run the following command to query the number of the SFTP
tasks deployed on the U2000 server:
l If the installed U2000 server software is a Chinese edition,
run the following command:
# vi /opt/oss/server/etc/XFTPService/locale/zh_CN/
TaskInfoCache.xml
l If the installed U2000 server software is an English edition,
run the following command:
# vi /opt/oss/server/etc/XFTPService/locale/en_US/
TaskInfoCache.xml
......
<ftpset>
<dest>10.10.10.10</dest>
<localpath......
<localpath......
</ftpset>
......
The preceding command output is used as an example.

10.10.10.10 indicates the IP address of the northbound server,
and each localpath value corresponds to a task. Record the
number of tasks and enter :q! to exit the vi editor.
2. Run the following command to query the number of threads
occupied by the SFTP tasks:
# cat /opt/oss/server/etc/XFTPService/ModuleParam.xml |
grep TaskThreadNum
<param name="TaskThreadNum">10</param>
The preceding command output is used as an example. 10

indicates the number of threads occupied by the SFTP tasks.
Record the number of threads.
3. The number of concurrent connections is obtained by
multiplying the number of tasks by the number of occupied
threads.
NOTE
If you change the number of SFTP tasks, you must change the number of
concurrent connections at the same time.
Step 2 Perform the following operations on the NMS server to check the SFTP service status.

U2000
If... Then...
The NMS server is The # ps -ef | grep sshd | grep -v grep

running Solaris OpenSS root 27748 1 0 Dec 25 ? 2:13 /
usr/local/sbin/sshd
H has root 21923 27748 0 11:11:31 ? 0:02 /
been usr/local/sbin/sshd -R
installed
l If the command output contains /usr/local/sbin/
Run the sshd, the SFTP service is running. Run the following
pkginfo command to restart the SFTP service:
OpenSS
# /etc/init.d/opensshd restart
H
comman l If no command output is displayed, the SFTP service
d, and has not started. Run the following command to start
the the SFTP service:
followin # /etc/init.d/opensshd start
g
comman
d output
is
displaye
d:
Securit
y
OpenSSH
OpenSSH
Portabl
e for
Solaris

U2000
If... Then...
No # svcs -a | grep ssh

OpenSS online 17:27:13 svc:/network/ssh:defaul
H has l If the command output contains online, the SFTP
been service is running. Run the following command to
installed restart the SFTP service:
Run the # svcadm restart svc:/network/ssh:default
pkginfo
l If the command output contains disabled, the SFTP
OpenSS
service has not started. Run the following command
H
to start the SFTP service:
comman
d, and # svcadm enable svc:/network/ssh:default
the
followin
g
comman
d output
is
displaye
d:
ERROR:
informa
tion
for
"OpenSS
H" was
not
found
The NMS server is running SUSE # service sshd status

Linux Checking for service sshd
running
l If the command result contains running, the SFTP

service is running. Run the following command to
restart the SFTP service:
# service sshd restart
l If the command result does not contain running, the
SFTP service is disabled. In this case, contact Huawei
technical support.
The NMS server is running any Contact Huawei technical support.

other OS
Step 3 Perform the following operations on the U2000 server to change the value of the
DefaultFTPType parameter in the ModuleParam.xml file.
deployed.

U2000
Search for the DefaultFTPType parameter and change the value to 1.
NOTE
If DefaultFTPType is set to 1, the SFTP encryption mode is used. If DefaultFTPType is set to 0, the
plaintext FTP mode is used.
To change the SFTP encryption mode to the plaintext FTP mode, change the value of DefaultFTPType
to 0 and restart the XFTPService0X01 service.
<GeneralParams>
…
<param name="DefaultFTPType">1</param>
…
</GeneralParams>
Press Esc and run the :wq command to save the file and exit the vi editor.
Step 4 Run the following command on the U2000 server to restart the XFTPService0X01 service to
make the modification take effect.
deployed.
You can obtain the service name of XFTPService0X01 for the server on which the current
operation is performed from the command output. XFTPService0X01 is used as an example.
Replace it as required.
$ svc_adm -cmd restartsvc XFTPService0X01
Step 5 Run the following command on the U2000 server to view the XFTPService0X01 service status.
deployed.
l If the XFTPService0X01 service is in the running state in the command output, the service
is running properly.
l If the XFTPService0X01 service is in the not running state in the command output, the
service is not started. When this occurs, contact Huawei technical support.
Step 6 Perform the following operations on the U2000 client to configure FTP server information:
2. 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).
In the Target Server Setting window, the configured FTP server information is displayed.
3. Select an FTP server whose information needs to be configured and click Add.
4. Set the FTP server parameters, as described in Table 2-12.

U2000
Table 2-12 Parameters in the Target Server Setting window
Module The module type consists of NBI FM, NBI CM, NBI PM, NBI Inventory,
Type/ CME NBI, CME NCCDM, License Management, NBI Server Backup,
Module NBI Log, EBC Counter, EBC Data, and LTE Trace Data. A module name
Name indicates that the configured FTP server is used to transfer the files
corresponding to the modules in the U2000. For example, if the module
name is northbound alarm, it indicates that the configured FTP server is
used to transfer the files of northbound alarm modules in the U2000
server.
Server IP IP address of the FTP server
User Name User name that is used to log in to the FTP server.
Password Password that is used to log in to the FTP server.
Confirm Enter the password that is used to log in to the FTP server again.
Password
Server Directory for storing a file after it is transferred to the FTP server.
Directory The directory name cannot contain the following special characters: colon
(:), asterisk (*), question mark (?), quotation mark ("), less than (<),
greater than (>), and vertical bar (|).
NOTE
When you log in to the U2000 server as user ftpuser, ensure that the server directory
starts with "/export/home/sysm", for example, "/export/home/sysm/ftproot".
Source Directory for storing the LTE Trace Data need to be uploaded.
Directory NOTE
This parameter only can be configured when you modify or add a FTP server whose
Module Name is LTE Trace Data.
File Whether to compress a file before transferring it.

Compressio l NONE: Transfer a file without compressing it.
n Type
l ZIP: Transfer a file after compressing it.
5. Click OK. The configuration setting is completed.
The added parameters are saved and displayed in the Target Server Setting window.
6. Choose Software > FTP Auto Upload Management > File Upload Browser (traditional
style); alternatively, double-click System Management in Application Center and choose
Settings > FTP Auto Upload Management > File Upload Browser (application style)
to check the status of the files to be uploaded.
The files to be uploaded and files that fail to be uploaded are displayed in the Upload File
Browser window.
----End

U2000
2.6 (Optional)Stopping Performance Export

Stopping performance export is optional. This section describes how to stop performance export
of specified NE types with specified measurement periods. You can stop performance export
using commands or using the OSMU.
Context
You can use either of the following methods to stop performance export:
l Stopping performance export using commands
l Stopping performance export using the OSMU
NOTE
This section uses stopping the performance export task of MSCServerNE as an example.
l In an SLS system, you need to perform the following steps only on the master server and do not need
to perform them on the slave or standby server.
l 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 In an ATAE cluster online remote HA system, you need to perform the following steps only on the
master server (include active site and standby site) and do not need to perform them on the slave or
standby server.
Procedure
l Stopping performance export using commands
2. Start the performance export script.
– On a Sun or ATAE(Sybase) platform, the default installation directory of the
U2000 server is /opt/oss/server, database server name is DBSVR, and user name
is database administrator. The default password is Changeme_123, run the
following commands:
-bash-3.00$ config_med_export.sh
NOTE
When the Sybase database is used, the user must be database administrator and the default
password is Changeme_123. The default database server name is DBSVR in the U2000 single-
server or HA system and the default database server name is DBSVR1 in the Sun-based SLS
system and ATAE Cluster system. For details about how to query the name of the Sybase
database, see 5.5 Checking the Sybase Database Server Name.
To improve system security, change the default database password upon first login and
periodically change the password. The password change interval can be customized as required.
Please input Database dbServer: DBSVR
Please input Database userName: database administrator
======================================================

U2000

3--Exit
======================================================
– On a HP or ATAE(Oracle) platform, the default installation directory of the

U2000 server is /opt/oss/server, database server name is ossdb, and user name is
itfndb. The default password is Changeme_123, run the following commands:
ossuser@osssvr-10:~> . /opt/oss/server/svc_profile.sh
ossuser@osssvr-10:~> config_med_export.sh
NOTICE
The user name of Oracle database is itfndb, and its default password is
Changeme_123.
To improve system security, change the default database password upon first login
and periodically change the password. The password change interval can be

Please input Database dbServer: ossdb
Please input Database userName: itfndb
======================================================
3--Exit
======================================================
where,
– 1: To view the preset types of NEs to be measured and their measurement periods.
– 3: To exit.
3. Type 1 to query the current performance measurement export.
If the system displays the following information, there is one performance

measurement export task.
Current Measurement
NeTypeName Period
----------------------------------------------------------------
-----------
MSCServerNE 60
======================================================
3--Exit
======================================================

U2000
4. Type 2 to set a new measurement export task.

New Measurement Set
======================================================
======================================================
5. Type 3 to cancel a measurement export task.
When the system displays the following information, type MSCServerNE, 60, and
y to cancel the measurement export task.
Deactive Measurements
======================================================
MSCServerNE
Please input Period (like '60' means 60 minutes period) [default or 'b' to
exit
current menu] : 60
You want deactive MSCServerNE with 60 minutes period, please input 'y' to
confirm, 'n' to ignore : y
6. Type b to return to the previous step.

======================================================
======================================================
7. Type 4 to return to the main menu.

======================================================
3--Exit
======================================================
8. Type 1 to query the current performance measurement export.

None Measurement Set Now!!
======================================================
3--Exit
======================================================
9. Type 3 to exit the performance export script.

l Stopping performance export using the OSMU of the master server (include the
master server of active site and standby site)

U2000
Enter.
6. Select tbl_MedExportMeas from the Configuration file name drop-down list, clear
the measurement periods of one or more NEs.
7. After the setting is complete, click Update Measurements to stop performance
export.
----End
2.7 Verifying Interconnection

This section describes how to simulate the NMS to obtain performance files generated by the
U2000 in SFTP mode using the OSMU. You can determine whether the northbound performance
file interface can be interconnected with the NMS according to the obtained performance files.
Context
The NMS can use either of the following methods to obtain northbound performance files:
l PULL: The NMS uses SFTP to obtain files from a specified path of the U2000 server.
l PUSH: The U2000 automatically uploads files to a specified path of the NMS.
NOTE
This section uses the PULL mode as an example. You are required to obtain performance files from a server
deployed with a MediationService service. To check whether a MediationService service is configured on
a server, run the following commands on the server as user ossuser:
$ svc_adm -cmd status | grep MediationService
If the following information is displayed in the command output, the MediationService service has been
configured on the server:
MediationService0101 [running ] //0101 is the number of service,
only for example.
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.

U2000
Step 4 In the navigation tree in the left pane, choose NBI Management > Category Management >
File Interface > Performance File(NE-Based) Interface to open the Performance File(NE-
Based) Interface page.
Step 5 On the Query Performance Med DataExport Files tab page showing generated performance
files, you can click a file name and open or download it.
Step 6 Check whether the contents of the performance export file have been generated according to the
negotiated parameters. If the file contents are consistent with the negotiated parameters, the file
is correct.
For example, the contents of the performance file A20101231.0145+0800-0200
+0800_LTE_74_003.xml are provided below. This file contains performance results of the NE
LTE_74_003 from 01:45 to 02:00. The file export format, export period, and NE name are
consistent with the preset parameters. The performance export file is therefore correct. For more
example information, see 3.1.1 Examples of Performance Result Export Files.
Following is an example performance file:

<?xml version="1.0" encoding="UTF-8"?>
<measCollecFile xmlns="http://latest/nmc-omc/cmNrm.doc#measCollec"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://
latest/nmc-omc/cmNrm.doc#measCollec schema\pmResultSchedule.xsd">
<fileHeader fileFormatVersion="32.435 V7.2" vendorName="Huawei">
<fileSender elementType="eNodeB"/>
<measCollec beginTime="2010-12-31T01:45:00+08:00"/>
</fileHeader>
<measData>
<managedElement userLabel="LTE_74_003"/>
<measInfo measInfoId="1542455306">
<granPeriod duration="PT900S" endTime="2010-12-31T02:00:00+08:00"/>
<repPeriod duration="PT900S"/>
<measTypes>1542455422 1542455423 1542455424 1542455425 1542455426
1542455427 1542455428 1542455429 1542455430 1542455431 1542455432 1542455433
1542455434 1542455435 </measTypes>
<measValue measObjLdn="LTE_74_003/SCTP:LTE_74_003">
<measResults>849 382 511 701 809 224 811 136 318 628 856 449 987
297 </measResults>
</measValue>
</measInfo>
</measData>
<fileFooter>
<measCollec endTime="2010-12-31T02:00:00+08:00"/>
</fileFooter>
</measCollecFile>
NOTE
Some messages are displayed in multiple lines due to the large size of contents. In the actual file, these
messages are displayed in one line.
----End

U2000
(NE-Based) 3 Introduction to Performance Result Export Files
3 Introduction to Performance Result Export

Files
About This Chapter
This chapter describes the performance result files that are exported by NE and the parameters
of performance result export services.
3.1 Description of Performance Result Export Files

This section describes the examples, path, default naming convention, user-defined naming
convention, format, and storage specification of performance result export files.
3.2 Configuration File of Performance Result Export Services

This section describes the configuration file of performance result export services and the
configuration items in the configuration file.

U2000
3.1 Description of Performance Result Export Files

This section describes the examples, path, default naming convention, user-defined naming
convention, format, and storage specification of performance result export files.
3.1.1 Examples of Performance Result Export Files

This section provides the examples and description of performance result export files.
File Examples
You can obtain the examples of performance result export files of some common NE types from
the 07.Northbound File\File Interface\Sample File\Performance File (NE-Based)
northbound interface document directory.
Contact Huawei technical support to obtain the examples of performance result export files of
specified NE types.
File Description
When you interconnect the U2000 with the NMS, observe the following aspects:
l Performance counter names may be modified due to spelling mistakes. Therefore, it is
recommended that the NMS use a performance counter ID instead of a performance counter
name to map the value of measTypes. That is, it is recommended that the NMS keep the
default value of CounterMode.
l The counters in an exported file are sorted according to the value of CounterMode in the
configuration file MedExpParam.xml. When you add or cancel a measurement counter,
the absolute location of other counters may therefore be changed. When the NMS parses
a file, do not assume that a counter is fixed to a place. Otherwise, the expected counter may
be inconsistent with the actual one.
l The counter result can be NIL, indicating that a counter has a null or meaningless result.
The possible causes of displaying NIL are: The NE does not report the corresponding
counter result; the counter is a calculation counter and the corresponding formula has 0 as
the divisor.
3.1.2 Path of Performance Result Export Files

This section describes the path of performance result export files.
The default save path of performance result export files is /opt/oss/server/var/fileint/

[pmneexport|ebcneexport][/NeTypeDir]/neexport_yyyymmdd/neName. The meanings of the
variables are as follows:
l [pmneexport|ebcneexport]: The default value is pmneexport. The Event-Based Counter
(EBC) performance results are saved in ebcneexport.
l [/NeTypeDir]: refers to the type of an NE. The U2000 will add this subdirectory based on
the NeTypeDir definition only when the NeTypeDir information is configured in the
configuration file /opt/oss/server/etc/MediationService/MedExpParam.xml.

U2000
l yyyymmdd: date for exporting performance result files. The files that are exported on the
same day will be saved to the same directory.
l neName: refers to the name of an NE. This variable for a NodeB is the name of the RNC
managing the NodeB. If the RNC cannot be found, the directory is named default.
NOTE
The Event-Based Counter (EBC) obtains the performance measurement results of eNodeB,
BSC6900UMTS, BSC6900GU, BSC6900UMTS, BSC6900GU, and BTS3900 by collecting statistics
about activated user-defined counters based on the original event data of eNodeB, BSC6900UMTS,
BSC6900GU, BSC6900UMTS, BSC6900GU, and BTS3900. For details about EBC, see the EBC Online
Help.
3.1.3 Default Naming Convention of Performance Result Export

Files
This section describes the default naming convention of performance result export files.
Default Naming Convention

After performance results are exported, the exported files are named based on the following
naming convention: <Type><Startdate>.<Starttime>-[<Enddate>.]<Endtime>_<UniqueId>
[_-_<RC>][_P<i>].xml. Table 3-1 describes the fields in the default naming convention.
Table 3-1 Fields in the default naming convention
Field Description Format
<Type> Indicates whether l A indicates the performance result file

measurement results in a of a single NE in one measurement
performance result export period.
file are obtained from a l B indicates the performance result file
single NE or multiple NEs. of multiple NEs in one measurement
period. This value is not used currently.
l E indicates the EBC performance result
file that is exported for a single NE in
one measurement period.
<Startdate> Start date of a performance The format of the start date is

measurement period. YYYYMMDD.
For example, if a performance
measurement period starts on January 9,
2011, the value of <Startdate> is
20110109.

U2000
<Starttime> Start time of a performance The format of the start time is

measurement period. HHMMshhmm. The meaning of each field
is as follows:
l HH indicates the hour of a local time,
represented by two digits. The value
range is from 00 to 23.
For example, if it is 5 p.m. local time,
HH is 17.
l MM indicates the minute in one local
hour, represented by two digits. MM =
N x a measurement period, where N is a
positive integer and N < (60/
measurement period).
If the measurement period is set to 15,
the possible value of MM is 00, 15, 30,
or 45.
l s indicates the sign (+ or -) for marking
the difference between the local time
and Greenwich Mean Time (GMT).
If the difference is 0, s is -.
l hhmm indicates the difference between
the local time zone and the DST offset,
represented by four digits.
If the difference is eight hours, hhmm is
0800.
[<Enddate>] End date of a performance This field is currently not contained in the
measurement period. names of performance export files.
For the measurement of a single period, the
value of [Enddate] and that of
<Startdate> are the same.
<Endtime> End time of a performance <Endtime> and <Starttime> are in the

measurement period. same format.
The value of this field is the sum of the start
time and the measurement period.
For example, if <Starttime> is 1715+0800
and the measurement period is 15, the value
of <Endtime> is 1730+0800.
If the measurement period is set to 24 hours,
the value of <Endtime> and that of
<Starttime> are the same. For example, if
<Starttime> is 0000+0800 and the
measurement period is 1440, the value of
<Endtime> is 0000+0800.

U2000
<UniqueId> Unique identifier of an NE. l The value of a non-NodeB NE can be

either the NE name or NE ID.
l The value for a NodeB is RNC
name.NodeB name.
[_-_RC] Sign of a supplementary This field is added to separate a

collected file. supplementary collected file from an
initially exported file.
The format of this field is _-_
[ObjectTypeId_]
<YYYYMMDDhhmmss>. The meaning of
this field is as follows:
l [ObjectTypeId_] indicates the ID of a
measurement object corresponding to a
counter in a supplementary collected
file. This field is added to the exported
file only when data of a cBSC is
collected.
l <YYYYMMDDhhmmss> indicates the
time on the U2000 server when a
supplementary collected file is
generated.
For example, if a supplementary
collected file is generated at 17:34:12 on
January 9, 2011, the value of
<YYYYMMDDhhmmss> is
20110109173412.

U2000
[_P<i>] Identifier of a divided file. The performance result file will be

automatically divided into files when both
the following conditions are met:
l The NE type is BSC6910GSMNE,
BSC6910GUNE, or
BSC6910UMTSNE.
l The size of the raw performance results
reported from a single NE exceeds the
preset threshold of the performance
result file size. The default threshold is
60 MB, which is equal to the size of
performance results for about 3000 cell
objects. If the size exceeds the threshold,
the performance results of objects that
are not divided are written into the basic
performance result file, and the
performance results of divided objects
are written into divided files. Based on
the number of cells and the preset
threshold, the suffix of a divided file
starts from _P001 and increases by 1
each time. For example, the suffix is
_P001, _P002, or _P003.
Example File Names Defined by the Default Naming Convention

l A20100626.2315+0200-2330+0200_Rnc006.xml
It is a performance result file of an NE named Rnc006. It is generated on June 26, 2010
and contains performance data of Rnc006 from 23:15:00 to 23:30:00 local time. The local
time of the NE is 2 hours earlier than the GMT.
l A20100626.2315+0200-2330+0200_Rnc006_-_20100626235522.xml
It is a supplementary collected file that is generated when the time on the U2000 server is
23:55:22, June 26, 2010.
l A20101130.0830+0800-0900+0800_Cbsc001_-_1157627904_20101130104010.xml
It is a supplementary collected file of a cBSC whose measurement object type ID is
1157627904. This file is generated when the time on the U2000 server is 10:40:10,
November 30, 2010.
l A20101130.0830+0800-0900+0800_bsc01.xml, A20101130.0830+0800-0900
+0800_bsc01_P001.xml, A20101130.0830+0800-0900+0800_bsc01_P002.xml,
A20101130.0830+0800-0900+0800_bsc01_P003.xml
These files are measurement result files generated from 08:00 to 09:00 local time on
November 30, 2010 for the NE whose type is BSC6910GSMNE and name is bsc01. The
local time of the NE is 8 hours earlier than the GMT. Measurement result files are written
into four files. The results of objects that are not divided are written into the basic result
file A20101130.0830+0800-0900+0800_bsc01.xml. Based on the size of raw performance

U2000
results and preset threshold, the results of divided objects are written into the following
divided files: A20101130.0830+0800-0900+0800_bsc01_P001.xml, A20101130.0830
+0800-0900+0800_bsc01_P002.xml, and A20101130.0830+0800-0900
+0800_bsc01_P003.xml.
3.1.4 User-defined Naming Convention of Performance Result

Export Files
This section describes how to define a naming convention for performance result export files.
For details about how to modify a user-defined naming convention, see 2.3 Modifying
Parameters of Performance Export Services.
Syntax and Rules for Defining a Naming Convention

The following contents show the syntax for defining a naming convention. Table 3-2 describes
the fields in a user-defined naming convention.
<Expr> := <Element> <Separator> <Element> | <SetElem> <SetSep> <SetElem>
<Element> := "[" <Identifier> "]" | <String>
<SetElem> := <Element>
<Separator> := "-" | "_" | "."
<SetSep> := <Separator>
<String> := <Letter> | <Digit>
<Letter> := a | b | c | d | e | f | g | h | i | j | k
| l | m | n | o | p | q | r | s | t | u | v
| w | x | y | z | A | B | C | D | E | F | G
| H | I | J | K | L | M | N | O | P | Q | R
| S | T | U | V | W | X | Y | Z
<Digit> := 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9
<Identifier> := <FT> | <UniqueId> | <OptionalId>
<UniqueId> := "NeName" | "NeIP"
<OptionalId> := "StartTime" | "EndTime" | "NeType"
| "NodeId" | "PRNCN" | "PRNCId"| "Period"
<FT> := "PM"
Table 3-2 Description of the fields in a user-defined naming convention
Field Meaning Description
NeName Name of an NE. Mandatory.

A user-defined naming convention must
NeIP IP address of an NE.
contain either of the parameters.
StartTime Start time of a performance The format of the start time is

measurement period. HHMMshhmm. The meaning of each
field is as follows:
l HH indicates the hour of a local time,
represented by two digits. The value
range is from 00 to 23.
For example, if it is 5 p.m. local time,
HH is 17.
l MM indicates the minute in one local
hour, represented by two digits.
MM = N x a measurement period,

U2000
Field Meaning Description
EndTime End time of a performance where N is a positive integer and N <

measurement period. (60/measurement period).
If the measurement period is set to
15, the possible value of MM is 00,
15, 30, or 45.
l s indicates the sign (+ or -) for
marking the difference between the
local time and Greenwich Mean
Time (GMT).
If the difference is 0, s is -.
l hhmm indicates the difference
between the local time zone and the
DST offset, represented by four
digits.
If the difference is eight hours,
hhmm is 0800.
NeType Type of an NE. -
NodeId ID of an NE. -
NOTICE
NodeId is a customized parameter
and is not used in normal cases.
Before using this parameter,
contact Huawei technical support.
PRNCN Name of the RNC to which a Applicable only to NodeBs.

NodeB belongs.
PRNCId ID of the RNC to which a Applicable only to NodeBs.

NodeB belongs.
Period Performance measurement Value: 15, 30, 60, 1440

period. The unit is minute.
PM Sign of a performance result The value must be PM.

file.

U2000
NOTICE
The description of the naming convention is as follows:
l <UniqueId> is mandatory. A user-defined naming convention must contain either
NeName or NeIP.
l A user-defined naming convention does not contain the file name extension. For details
about the naming convention for the file name extension of a retrieved file or divided file,
see 3.1.3 Default Naming Convention of Performance Result Export Files.
l If a file cannot be named on the basis of the previous syntax and rules, the system exports
a performance result file and names it based on the default naming convention.
Example of a User-Defined Naming Convention

If a user-defined naming convention is [PM]_[NeName]_[NeType]_[StartTime]-[EndTime]
_[Period], you need to add the following content to the /opt/oss/server/etc/MediationService/
MedExpParam.xml file by referring to 2.3 Modifying Parameters of Performance Export
Services:
<FileNameRule Name="PM Export File naming rule" Value="[PM]_[NeName]_[NeType]_
[StartTime]-[EndTime]_[Period]"/>
The performance result export files for the NE RNC123 will be named
PM_RNC123_RNC_20100101.0000+0800-20100101.0030+0800_30.xml.
3.1.5 Format of Performance Result Export Files

This section describes the contents of performance result export files.
Format Description
The U2000 supports performance result export files in .xml format. Table 3-3 describes the
parameters of a performance result export file.
Table 3-3 Parameters of a performance result export file
measCol fileHeader fileFormatVersion The current version number is 32.435

lecFile V7.2, indicating that the version
complies with the 3GPP TS 32.435
V7.2.0 (2006-06) protocol.
vendorName Name of a vendor.
fileSender elementType Type of an NE.
measCollec beginTime Start time of the first measurement

period.
measData managedElement Name of an NE.

userLabel

U2000
measInfo measInfoId ID of a measurement unit.
granPeriod duration Current measurement period. The unit

is second and the format is PTnS.
For example, PT3600S indicates that
the current measurement period is
3,600 seconds.
endTime End time of the current measurement

period.
repPeriod duration Period of reporting measurement

results. The unit is second and the
format is PTnS.
measTypes Counter information, which

corresponds to the measurement result
in measValue.
measValue measObjLdn Name of a measured object.
measResults Measurement result. The order of the

results corresponds to the counter
order in measTypes.
suspect Result reliability flag. false indicates

reliability and true indicates
unreliability. The default value is
false and can be ignored.
fileFooter measCollec endTime End time of the last measurement

period.
A measurement object is named in the format of 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.
Example
The following is an example of a performance result export file:
<?xml version="1.0" encoding="utf-8"?>
<measCollecFile xmlns="http://latest/nmc-omc/cmNrm.doc#measCollec"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://latest/nmc-omc/cmNrm.doc#measCollec schema
\pmResultSchedule.xsd">
<fileHeader fileFormatVersion="32.435 V7.2" vendorName="Huawei">
<fileSender elementType="RNC"/>
<measCollec beginTime="2008-01-12T22:05:00+08:00"/>
</fileHeader>
<measData>
<managedElement userLabel="testRNC"/>
<measInfo measInfoId="67109391">
<granPeriod duration="PT300S" endTime="2008-01-12T22:10:00+08:00"/>
<repPeriod duration="PT300S"/>
<measTypes>67190519 67180678 67180677 </measTypes>
<measValue measObjLdn="testRNC/Cell:Label=CELL100, CellID=100">
<measResults>31 31 31 </measResults>
<suspect>true</suspect>
</measValue>
</measInfo>
</measData>
<fileFooter>
<measCollec endTime="2008-01-12T22:10:00+08:00"/>
</fileFooter>
</measCollecFile>
NOTE
l <suspect>true</suspect> is displayed only when the result is unreliable. If this parameter is not
included in the export file, the result is reliable.
l Some messages are displayed in multiple rows because the file has many contents. In the actual file,
these messages are displayed in one row.
l The coding scheme of Chinese XML files is GBK and that of English XML files is UTF-8.
l In schema\pmResultSchedule.xsd, schema indicates the name of the folder where the
pmResultSchedule.xsd file is located. You need to replace it with the actual one specified by the NMS.

U2000
3.1.6 Storage Specification of Performance Result Export Files

This section describes the save format and deletion policy of performance result export files.
Northbound performance files can be saved compressed or non-compressed. They are saved
compressed by default.
Northbound performance files can be saved on the U2000 for a maximum of seven days. By
default, they are saved for seven days. The U2000 automatically deletes files that expire.
The parameters for the storage specification of northbound performance files are defined in the
configuration file of performance export services. For details, see Parameters for Setting File
Export Specifications.
3.2 Configuration File of Performance Result Export

Services
This section describes the configuration file of performance result export services and the
configuration items in the configuration file.
Configuration File of Performance Result Export Services

The configuration file of performance result export services is /opt/oss/server/etc/
MediationService/MedExpParam.xml. You can modify the configuration items in this file to
set the performance export file format and manage exported files. For details, see 2.3 Modifying
Parameters of Performance Export Services.
NOTE
MeasInfoUpdateSpanMins, NeTypeDir, or FileNameRule does not exist in the configuration file by

default and need to be manually added. The format of these parameters are the same as that of other
parameters.
l After the MeasInfoUpdateSpanMins and DelDelayTime parameters are changed, restart all
MediationService[xxxx] services on the server.
l After the CounterMode, CounterFilterMode, FileSaveDay, StrSeparator, and IsGzip parameters
are changed, no service needs to be restarted, and the new parameter settings take effect 5 minutes
later.
l After the NeTypeDir parameter is added, no service needs to be restarted, and the new parameter
setting takes effect 5 minutes later. After the NeTypeDir parameter is deleted or changed, restart all
MediationService[xxxx] services on the server.
l After the FileNameRule parameter is changed or modified, no service needs to be restarted, and the
new parameter setting takes effect 5 minutes later. After the FileNameRule parameter is deleted, restart
all MediationService[xxxx] services on the server.
The following is an example of the MedExpParam.xml configuration file:

<?xml version="1.0" encoding="UTF-8"?>
<PMExpPara>
<CounterMode Name="Counter display way: 0 for counter name, 1 for counter ID"
Value="1"/>
<CounterFilterMode Name="Counter filter way: 0 for default,
1 for exporting the counters only setting measurement" Value="0"/>
<MeasInfoUpdateSpanMins Name="MeasInfo Update Span Time, in Minutes, valid
only
CounterFilterMode=1, 1440 for default" Value="1440"/>

U2000

<StrSeparator Name="Separator for counter name and string value, default is
blank"
Value=" "/>
<IsGzip Name="Compress file or not, 0 for no, 1 for yes" Value="1"/>
<FileNum Name="File number of split file." Value="3"/>
</PMExpPara>
NOTE
Some messages are displayed in multiple lines due to the large size of contents. In the actual file, these
messages are displayed in one line.
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.4 How to Set Parameters
in a Northbound Configuration File.
Parameters for Setting File Export Path

NeTypeDir (optional): where NeTypeName specifies an NE type and Path specifies a sub-
folder. You can set NeTypeDir so that performance result export files of an NE type are saved
to a specified sub-folder. You can set values to Path. For details about NeTypeName values,
see 5.1 NEs Supported by Performance File Export
Assume that the installation path of the U2000 server is /opt/oss/server, the example is as
following.
l If you set <NeTypeDir Name="special path for some ne type" NeTypeName="RNCNE|
NodeBNE" Path="wran"/>, performance result files of RNCNE and NodeBNE will be
exported to /opt/oss/server/var/fileint/pmneexport/wran/neexport_yyyymmdd.
l If you set <NeTypeDir Name="special path for some ne type"
NeTypeName="BSC6000NE" Path="gbss"/>, performance result files of BSC6000NE
will be exported to /opt/oss/server/var/fileint/pmneexport/gbss/neexport_yyyymmdd.
If the installation path has been changed during the installation, modify the path to the actual
installation path.
Parameters for Setting Performance Counters

l CounterMode: specifies the display and sort modes of counters in a performance result
export file. The default value is 1. You are advised to retain the default value.
– When value is set to 0, performance data in the exported file is displayed and sorted by
counter name. Counters in the exported file are displayed by counter name and sorted
alphabetically.
– When value is set to 1, performance data in the exported file is displayed and sorted by
counter ID. Counters in the exported file are displayed by counter ID and sorted by
number in ascending order.
l CounterFilterMode: specifies the filter mode of measurement counters that are exported
through the northbound interface. This parameter only applies to NEs that report all
counters and use the default measurement period. You can set this parameter to 0 or 1 to
set the filter mode of these NEs. For details about NE measurement attributes, see 5.2
Measurement Attributes of an NE.
The default value is 0.
– When the value is set to 0, measurement results of all NE counters will be exported.

U2000
– When the value is set to 1, measurement results of counters (including internal counters
for calculating these counters) that are being measured on the U2000 client will be
exported.
– By default, the northbound interface updates measurement information of counters
every 24 hours. The measurement results of newly-measured counters can be exported
to result files only after the northbound interface updates measurement information.
MeasInfoUpdateSpanMins (optional): specifies the period (in minutes) for the
northbound interface to synchronize the measuring counter information with the U2000
client. This parameter is valid only when CounterFilterMode is set to 1. The default
value is 1440. You are advised to retain the default value.
l StrSeparator: specifies the separators between counter names and the string format in a
performance result export file.
The default value is a space. If a counter name contains a space, use a semicolon (;) instead
of a space as the separator. You can use a space to separate counter IDs.
Parameters for Setting File Export Specifications

l FileSaveDay: specifies the days for storing performance result export files. The default
value is 7.
NOTICE
For an LTE network configured with 2000 equivalent NEs, if the 15–minute measurement
period is in use, the total size of result files exported in a day may reach 3 GB. In this case,
you are advised to set FileSaveDay to 3.
l DelDelayTime: specifies the delay (in minutes) between the timer for automatic deletion
of expired result files and 00:00:00 every day. The default value is 30, which indicates that
the system automatically deletes expired result files at 00:30:00 every day.
l IsGZip: specifies whether to compress the exported result files. The default value is 1.
– When value is set to 0, the system will not compress the exported result files.
– When value is set to 1, the system will compress the exported result files using the
UNIX standard to generate files in GZ format.

U2000
(NE-Based) 4 Troubleshooting Northbound Performance File Interface
4 Troubleshooting 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 attempts to obtain performance data, rectify the fault by referring
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, rectify the fault according to the troubleshooting suggestions
described in this section for the most common faults. If it is impossible to rectify a fault by using
these troubleshooting suggestions, contact Huawei technical support.
4.2 Troubleshooting Performance File Export Failure

This section describes how to troubleshoot the performance file export failure. One of the
following three causes can result in performance file export failure: the performance export
service is not started; NEs are disconnected; free disk space on the U2000 server is insufficient.
4.3 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.4 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, rectify the fault according to the troubleshooting suggestions
described in this section for the most common faults. If it is impossible to rectify a fault by using
these troubleshooting suggestions, contact Huawei technical support.
Common Troubleshooting
For details about how to rectify common faults that may occur when the NMS attempts to obtain
performance data, see Table 4-1.
Table 4-1 Common troubleshooting
Common Fault Troubleshooting Method
No performance file is exported. For details, see 4.2 Troubleshooting Performance File
Export Failure.
How to set parameters in a See 4.4 How to Set Parameters in a Northbound

northbound configuration file Configuration File.
Information Collection
If an unusual fault occurs when the NMS attempts to obtain performance data, collect relevant
information to help Huawei technical support personnel locate the fault. For details about how
to collect fault information, see Table 4-2.
Table 4-2 Description of information collection
Relevant Information Description
Operation information Record the operations performed before a fault occurs and the
troubleshooting measures taken later.
Version information Obtain version information about the U2000, NE mediations,

and NEs from each site.
IP information Obtain IP information about U2000 servers from each site.

U2000
Relevant Information Description
Log information NOTE

l In an SLS system, you need to perform the following steps only on
the master and slave servers and do not need to perform them on the
standby server.
l 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 In an ATAE cluster online remote HA system, you need to perform
the following steps only on the master and slave servers (include
active site and standby site) and do not need to perform them on the
standby server.
l Obtain log information from the /opt/oss/server/var/logs
directory. The trace file of the performance file interface in
this directory is iMAP.med[xxxx]_agent.trace.
l Obtain performance export files from the /opt/oss/server/
var/fileint/pmneexport directory.
l Obtain backup trace files from the /opt/oss/server/var/logs/
tracebak directory.
4.2 Troubleshooting Performance File Export Failure

This section describes how to troubleshoot the performance file export failure. One of the
following three causes can result in performance file export failure: the performance export
service is not started; NEs are disconnected; free disk space on the U2000 server is insufficient.
Description
No performance file exists in the export path. The NMS therefore fails to obtain performance
data of NEs.
Troubleshooting
One of the following three causes can result in performance file export failure:
l The performance export service is not started.
l NEs are disconnected.
l Free disk space on the U2000 server is insufficient.
Handling Performance Export Service Inactivation Faults

Query the status of MediationService to confirm that the performance export service is started.
If the service is not started, perform the following steps to start it:

2. Run the following commands to query the status of the performance export service:
-bash-3.00$ cd /opt/oss/server

U2000
-bash-3.00$ . ./svc_profile.sh
If the system displays the following information, the service is started:
3. If the service is not started, run the following command to start it (For example,
MediationService0101). You must start all MediationService[xxxx] services on the server.
-bash-3.00$ svc_adm -cmd startsvc MediationService0101
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 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.

U2000
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.
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.4 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.

U2000
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.
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
(NE-Based) 5 Appendix
5 Appendix
About This Chapter
This chapter provides reference information about the northbound performance file interface.
5.1 NEs Supported by Performance File Export

This section lists the names of the NE types whose performance data can be exported through
the U2000 northbound performance file interface.
5.2 Measurement Attributes of an NE

This section describes the measurement attributes of an NE.
5.3 Method of Obtaining Performance Counter Files of NEs

This section describes how Huawei technical support engineer obtain performance counter files
of NEs.
5.4 Method of Transferring Data Using PSFTP

This section describes how to transfer data using PSFTP. The command line mode on a local
PC does not support SFTP data transfer. If you use SFTP to transfer data, download the PSFTP
client.
5.5 Checking the Sybase Database Server Name

U2000
5.1 NEs Supported by Performance File Export

This section lists the names of the NE types whose performance data can be exported through
the U2000 northbound performance file interface.
Table 5-1 NE list
Index NE Type Name
A l AAANE
l AIMNE
l AP ManagerNE
l ATSNE
l AGCFNE
l AAAOMDNE
l AAABMPNE
l ASNGWNE
B l BSC6000NE
l BSCNE
l BSC6900GUNE
l BSC6900GSMNE
l BSC6900UMTSNE
l BSC6000GSMRNE
l BSC6000(R11+)NE
l BSC6810(R11+)NE
l BWANE
l BSC6910GUNE
l BSC6910GSMNE
l BSC6910UMTSNE
l BTS3900NE

U2000
Index NE Type Name
C l CAS9910NE
l CHLR9820NE
l CGNE
l CBSCNE
l CHLR-DCNE
l CHLR-SCNE
l CMGWNE
l CMSCNE
l CSCFNE
l CT800GLMSNE
l CGPOMUNE
l CCFNE
l CX600NE
D l DNS9816NE
l DNSNE
l DOPRANE
E l eNodeBNE
l eRelayNE
l ECO6910NE
l EERNE
l EIRNE
l ENSNE
l ETASNE
l EudemonNE
l ENUMNE
F l FIXMGWNE
l FMCMGWNE
G l GGSN80NE
l GLMSNE
l GMSNE
l GT800BSCNE
l GTASNE
l GUEIRNE
l GUHLRNE

U2000
Index NE Type Name
H l HANE
l HLR36NE
l HLR-DCNE
l HLRNE
l HLR-SCNE
l Horizon2GBSCNE
l Horizon3GRNCNE
l HRC-BSCNE
l HSSNE
l HSS9860NE
I l ICSNE
l iMSCNE
l IPCTRXNE
M l M800MSCNE
l MediationNE
l MediaX3600NE
l MGWNE
l MiniMGWNE
l MMENE
l MRFNE
l MRFPNE
l MRS6100NE
l MSCeNE
l MSCNE
l MSCServerNE
l MAG9811
l MICRO BTS3900
l MEDIAXNE
l MRP6600NE
l MRFCNE
l M-EIRNE
N NodeBNE

U2000
Index NE Type Name
P l pBTS3701NE
l PCU33NE
l PCUNE
l PDSNNE
l PDSNR01NE
l PGMNE
l POCNE
R l RACNE
l RCCNE
l RIMNE
l rMSCNE
l rMSCSvrNE
l RNCNE
l RouterNE
l RTNNE
l RMNE
l RCS9880NE
l RCS9880BMPNE
l RADIUSProxyNE
S l SAEGWNE
l SAE-HSSNE
l SBCNE
l SDCNE
l SE2600NE
l SG7000NE
l SGSNNE
l SHLRNE
l SIGNE
l SOFTX3000NE
l SPSNE
l SVNNE
l SwitchNE
l SE2900NE
l SPSV3NE
l SIGServerNE

U2000
Index NE Type Name
T l TDNodeBNE
l TD-RNCNE
l TGW1000NE
l tMSCNE
l tMSCSvrNE
l TSCNE
l ThirdPartyServerNE
U l UAGNE
l UANE
l UEIRNE
l UGCNE
l UGWNE
l UNPNE
l UPCCNE
l USCDBNE
l USNNE
l USU3900NE
l USU3910NE
l UIMNE
l UPANE
l UGW9500NE
l UPortalNE
V ViewPointNE
5.2 Measurement Attributes of an NE

This section describes the measurement attributes of an NE.
The measurement attributes of an NE are as follows:

l Default measurement counters: The U2000 enables performance measurement for these
counters by default. You do not need to set measurement for these counters.
l Default measurement period: A default measurement uses the default measurement period.
This attribute can be modified under guidance of Huawei technical support personnel. It is
recommended that you do not modify this attribute.
l Report by all counters: An NE reports the measurement results of all counters in a default
measurement period. An NE that reports by all counters reports measurement results of all
counters even if you have canceled the measurement of some counters on the U2000 client.

U2000
Not report by all counters: An NE reports only measurement results of counters that are set
to be measured on the U2000 client.
For details about the measurement attributes of an NE, see the Performance Counter
List.xls:
l Check the Measured Feature row in the About This Document sheet.
l Check the Default Measured(Yes/No) column in the Counters sheet.
NOTE
If a performance counter file does not contain the Measured Feature and Default Measured(Yes/No)
information, contact Huawei technical support.
5.3 Method of Obtaining Performance Counter Files of NEs

This section describes how Huawei technical support engineer obtain performance counter files
of NEs.
Visit http://support.huawei.com and then obtain performance counter files of a corresponding
NE version.
Following is an example of obtaining performance counter files of an BSC6910:
Software > Wireless Network > GSM&UMTS&LTE > SingleRAN > SingleRAN_MBSC
> BSC6910 > BSC6910 V100R016C00SPC600 > BSC6910 GSM V100R016C00SPC600
U2000 Mediation Documents-EN
5.4 Method of Transferring Data Using PSFTP

This section describes how to transfer data using PSFTP. The command line mode on a local
PC does not support SFTP data transfer. If you use SFTP to transfer data, download the PSFTP
client.
Procedure
Step 1 Huawei technical support engineer download the PSFTP client to a local PC from Software at
http://support.huawei.com.
Step 2 Double-click psftp.exe to start the PSFTP client.
Step 3 Run the following command to connect the target server:
psftp> open IP address of the target server
Step 4 Type the FTP user name and password.
----End
5.5 Checking the Sybase Database Server Name
Prerequisites
You have contacted Huawei technical support engineers to obtain PuTTY.zip at http://
support.huawei.com and decompressed it to your PC.Huawei technical support engineers can

U2000
quickly search for the tool package using its name as the keyword after clicking Search by
Category > Tools at http://support.huawei.com.
Procedure
Step 1 Use PuTTY to log in to the U2000 DB active node in SSH mode as user dbuser.
Step 2 Run the following command to view the name of the Sybase server:
$ ls /opt/sybase/ASE-15_0 |grep cfg |awk -F'.' '{print $1}' |uniq
In the following command output, the name of the database server is DBSVR1:
DBSVR1
----End


U2000 Northbound Performance File Interface Developer Guide (NE-Based)

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

U2000 Northbound Performance File Interface Developer Guide (NE-Based)

Încărcat de

Drepturi de autor:

Formate disponibile

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

Added the introduction of export OSS performance items.

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

2 Interconnection Commissioning of Northbound Performance File Interface

3 Introduction to Performance Result Export Files

4 Troubleshooting Northbound Performance File Interface

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

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

Calls attention to important information, best practices and

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

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

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

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

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 Northbound Performance File Interface..................5

3 Introduction to Performance Result Export Files..................................................................44

4 Troubleshooting Northbound Performance File Interface.................................................58

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

4.4 How to Set Parameters in a Northbound Configuration File........................................................................................62

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

1 Overview of Northbound Performance File

About This Chapter

1.1 Definition of Northbound Interface

1.2 Definition of the Northbound Performance File Interface

1.3 Using the Northbound Performance File Interface

1.4 Technical Specifications of Northbound Performance 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 the Northbound Performance File

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

1.3 Using the Northbound Performance File Interface

Table 1-1 Usage of the northbound performance file interface

Single-server Perform interconnection on Obtain performance files on the

HA System Perform interconnection on Obtain performance files on the active

SUN-based SLS Perform interconnection on Obtain performance files from each

ATAE cluster Perform interconnection on Obtain performance files from each

ATAE cluster Perform interconnection on Obtain performance files from each

1.4 Technical Specifications of Northbound Performance

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

Maximum re-upload attempts that are permitted after 3