U2000 Trace Server UMTS Throughput Stat Northbound File Interface Developer Guide (OFFE00046978 - PMD8906ZH A)

U2000
V200R018C10
Trace Server UMTS Throughput Stat
Northbound File Interface Developer
Guide
Issue 01
Date 2018-02-05
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. 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 01 (2018-02-05) Huawei Proprietary and Confidential i

Copyright © Huawei
Technologies Co., Ltd.
U2000
Trace Server UMTS Throughput Stat Northbound File
Interface Developer Guide About This Document
About This Document
Overview
This document provides information about the UMTS Throughput Stat Northbound File
Interface of the Trace Server. It also provides guidance for interconnecting with the network
management system (NMS).
When the Trace Server collects NE data, such as, CHR, MR, and trace data, filters the data,
and provides the data for the U2000, upper-layer applications, and NMSs, collection, storage,
and transmission of personal data, such as MSISDNs, IMSIs, IMEIs, and cell IDs are
involved. If the storage directory space or the storage duration reaches specified thresholds,
data will be automatically deleted. NMSs protect personal data in information sent to NMSs.
NE-provided data supports the anonymization capability for sensitive data sources, and the
Trace Server provides the anonymization capability when data is moved out of the live
network. To ensure personal data security, comply with applicable state laws or enterprise
privacy policies and take sufficient measures.Trace Server.
Product Version
This document applies to the following products and versions.
Product Name Product Version
U2000 V200R018C10
Intended Audience
This document is intended for network management engineers.
Issue 01 (2018-02-05) Huawei Proprietary and Confidential ii

Copyright © Huawei
U2000
Change History
03 (2018-05-30)
This is the third commercial release for V200R018C10. Compared with 02 (2018-04-28) for
V200R018C10, this issue adds descriptions of GSM throughput stat and WLAN events.
Organization
1 Overview of the Result File Interface
This chapter describes the definition of the northbound interface and the result file interface
provided by the Trace Server.
2 Overview of Result Files
This chapter describes the result files for users to easily locate and obtain the files.
3 Managing Northbound Users in RAN Sharing Scenarios
This section describes how to manage northbound users in RAN sharing scenarios. In such
scenarios, multiple operators can share one radio access network (RAN). Northbound files
reported by one NE contain northbound data from different operators. The Trace Server
identifies different operators according to the PLMN in the northbound files and saves
generated northbound result files in different directories. Operators create specified
northbound users to obtain required northbound result files in FTP mode.
4 Process for Interconnecting the Throughput Stat Data Northbound Result File Interface
This chapter describes the process for interconnecting the NMS with the Trace Server by
using the throughput stat data northbound result file interface.
5 Troubleshooting for the Throughput Stat Data Northbound Result File Interface
The NMS is interconnected with the Trace Server through the throughput stat data northbound
result file interface. If problems occur when getting throughput stat data northbound of NEs
on the network, you can solve problems using the methods described in this section.
6 Appendix
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.
Issue 01 (2018-02-05) Huawei Proprietary and Confidential iii

Copyright © Huawei
U2000
Symbol Description

avoided, may result in minor or moderate injury.

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and
tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
General Conventions
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 Terminal display is in Courier New.
Command Conventions
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.
Issue 01 (2018-02-05) Huawei Proprietary and Confidential iv

Copyright © Huawei
U2000
GUI Conventions
Boldface Buttons, menus, parameters, tabs, windows, 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 Operation
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 Operation
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and
quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Issue 01 (2018-02-05) Huawei Proprietary and Confidential v

Copyright © Huawei
U2000
Interface Developer Guide Contents
Contents
About This Document....................................................................................................................ii

1 Overview of the Result File Interface........................................................................................1
1.1 Definition of the Northbound Interface..........................................................................................................................1
1.2 Definition of the Northbound Trace Result File Interface..............................................................................................2
1.3 Technical Specifications for the Throughput Stat Data Northbound Result File Interface............................................2
2 Overview of Result Files..............................................................................................................4

2.1 Types of Throughput Stat Data Northbound Result Files..............................................................................................4
2.2 Save Path of Throughput Stat Data Northbound Result Files........................................................................................5
2.3 Naming Conventions of Throughput Stat Data Northbound Result Files......................................................................5
2.4 Generation Periods of Throughput Stat Data Northbound Result Files.........................................................................7
2.5 Formats of Throughput Stat Data Northbound Result Files...........................................................................................7
3 Managing Northbound Users in RAN Sharing Scenarios..................................................12

3.1 Creating Northbound Users..........................................................................................................................................13
3.2 Viewing Northbound Users..........................................................................................................................................15
3.3 Modifying Northbound User Passwords......................................................................................................................16
3.4 Deleting Northbound Users..........................................................................................................................................17
3.5 Deleting Northbound User PLMNs..............................................................................................................................19
3.6 Configuring the Northbound RAN Sharing Function Switch......................................................................................20
4 Process for Interconnecting the Throughput Stat Data Northbound Result File
Interface............................................................................................................................................23
4.1 Negotiating Interconnection Parameters for the Throughput Stat Data Northbound Result File Interface.................25
4.2 Setting the SAU IP Address on NEs.............................................................................................................................28
4.3 Delivering the throughput stat data northbound Event Subscription...........................................................................28
4.3.1 Subscribing to a UMTS Cell Trace Task...................................................................................................................29
4.3.2 GUIs for UMTS Northbound Interface Trace...........................................................................................................30
4.3.3 Parameters for Subscribing to a UMTS NE Trace Task............................................................................................31
4.4 Commissioning the Interconnection of the Throughput Stat Data Northbound Result File Interface.........................34
4.5 Optional: Setting the Northbound Push FTP Server (Trace Server Co-deployed with the U2000 in the ATAE Cluster
System)...............................................................................................................................................................................35
4.6 Optional: Setting the Northbound Push FTP Server (ATAE Cluster and Virtual Cluster, Standalone).......................36
5 Troubleshooting for the Throughput Stat Data Northbound Result File Interface......40
Issue 01 (2018-02-05) Huawei Proprietary and Confidential vi
Copyright © Huawei
U2000
Interface Developer Guide Contents
5.1 Troubleshooting and Information Collection...............................................................................................................41

5.2 Handle the Problem That No Throughput Stat Data Northbound Result File Is Generated........................................42
5.3 Setting the SFTP Public and Private Key Authentication for the Northbound Push FTP Server.................................43
5.4 How Do I Check the Problem that CHR Data Is Unreported to the Trace Server.......................................................49
5.5 How Do I Set the DST?................................................................................................................................................51
6 Appendix.......................................................................................................................................54
6.1 Supported NE types and versions.................................................................................................................................54
6.2 UMTS Event List.........................................................................................................................................................55
Issue 01 (2018-02-05) Huawei Proprietary and Confidential vii

Copyright © Huawei
U2000
Trace Server UMTS Throughput Stat Northbound File Overview of the Result File InterfaceOverview of the
Interface Developer Guide Result File Interface
1 Overview of the Result File Interface
About This Chapter

This chapter describes the definition of the northbound interface and the result file interface
provided by the Trace Server.
1.1 Definition of the Northbound Interface
The northbound interface is the interface between the element management system (EMS)
and the NMS.
1.2 Definition of the Northbound Trace Result File Interface
The northbound trace result file interface provided by the Trace Server is a northbound
interface. Through this interface, the NMS obtains northbound trace result files stored on the
Trace Server.
1.3 Technical Specifications for the Throughput Stat Data Northbound Result File Interface
This section describes the technical specifications for the throughput stat data northbound
result file interface.
1.1 Definition of the Northbound Interface

The northbound interface is the interface between the element management system (EMS)
and the NMS.
The NMS obtains NE data, such as NE trace result data, from the EMS and issues commands
over the northbound interface. Figure 1.1 shows the northbound interface.
Issue 01 (2018-02-05) Huawei Proprietary and Confidential 1

Copyright © Huawei
U2000
Figure 1.1 Northbound interface
1.2 Definition of the Northbound Trace Result File

Interface
The northbound trace result file interface provided by the Trace Server is a northbound
interface. Through this interface, the NMS obtains northbound trace result files stored on the
Trace Server.
The Trace Server supports the following protocols for transferring northbound trace result
files:
 File Transfer Protocol (FTP): the common FTP protocol.
 Secure File Transfer Protocol (SFTP): the SSH-based FTP transmission mode.
You are advised to use the SFTP protocols because the SFTP protocols is more secure than the FTP
protocols.
1.3 Technical Specifications for the Throughput Stat Data

Northbound Result File Interface
This section describes the technical specifications for the throughput stat data northbound
result file interface.
Table 1.1 describes the technical specifications for the UMTS throughput stat northbound file
interface provided by the Trace Server.

Copyright © Huawei
U2000
Table 1.1 Technical specifications for the UMTS throughput stat northbound file interface
Specification Value
Maximum period during which throughput 72

stat data northbound result files are stored
on the Trace Server (unit: hour)
Maximum size of a throughput stat data 180
northbound result file that can be saved on a
Trace Server (unit: GB)
northbound result file that can be saved on NOTE
the shared space (unit: GB)  If the size of files saved on the shared space
is less than 256 GB and the storage period
does not expire, trace result files generated by
the Trace Server are not deleted.
 If the size of files saved on the shared space
is greater than 256 GB and the storage period
does not expire, files generated by application
systems (except the Trace Server) and trace
result files generated by the Trace Server are
deleted in sequence before sizes of the files
are less than their respective storage
specifications or the size of files saved on the
share space is less than 256 GB.
 If the space usage of the export/home
directory is higher than 80%, data is deleted
from the shared space.

northbound result file that can be saved on a
high-specification VM (unit: GB)
northbound result file that can be saved on NOTE
the shared space of the high-specification  If the size of files saved on the shared space
VM (unit: GB) of the high-specification VM is less than
1024 GB and the storage period does not
expire, trace result files generated by the
Trace Server are not deleted.
 If the size of files saved on the shared space
of the high-specification VM is greater than
1024 GB and the storage period does not
expire, files generated by application systems
(except the Trace Server) and trace result files
generated by the Trace Server are deleted in
sequence before sizes of the files are less than
their respective storage specifications or the
size of files saved on the share space of the
high-specification VM is less than 1024 GB.
 If the space usage of the export/home
directory is higher than 80%, data is deleted
from the shared space.

Copyright © Huawei
U2000
Interface Developer Guide Overview of Result FilesOverview of Result Files
2 Overview of Result Files
About This Chapter

This chapter describes the result files for users to easily locate and obtain the files.
To obtain result samples, contact Huawei technical support engineers.
2.1 Types of Throughput Stat Data Northbound Result Files

The Trace Server generates NE northbound result files based on the corresponding NE data.
2.2 Save Path of Throughput Stat Data Northbound Result Files
After collecting and processing NE data, the Trace Server saves throughput stat data
northbound result files in the /export/home/omc/var/fileint/TSNBI/ path of the server where
the NE is located. The Trace Server creates subdirectories in the directory.
2.3 Naming Conventions of Throughput Stat Data Northbound Result Files
The Trace Server saves NE data as throughput stat data northbound result files.
2.4 Generation Periods of Throughput Stat Data Northbound Result Files
This section describes the generation periods of throughput stat data northbound result files.
2.5 Formats of Throughput Stat Data Northbound Result Files
This section describes the formats of throughput stat data northbound result files.
2.1 Types of Throughput Stat Data Northbound Result

Files
The Trace Server generates NE northbound result files based on the corresponding NE data.

Copyright © Huawei
U2000
2.2 Save Path of Throughput Stat Data Northbound Result

Files
After collecting and processing NE data, the Trace Server saves throughput stat data
northbound result files in the /export/home/omc/var/fileint/TSNBI/ path of the server where
the NE is located. The Trace Server creates subdirectories in the directory.
The rule for creating subdirectories is as follows:
UMTS_PCHR/yyyymmdd/NE identifier/.
 yyyymmdd indicates the date when a throughput stat data northbound result file is
generated.
 NE identifiers include NEFDN and neName. The FDN is a unique attribute of the NEs, and the
value range is 256 to 2945727. The neName is user-defined and unique in the same EMS.
 The IP address of the server where the NE resides can be queried through the Maintenance > Trace
Server Maintenance > Query Subscription Information function of the U2000 client. For details
about operations in the Query Subscription Information window, press F1 in the window to view
the help information.
 The configuration item can be modified on the U2000 client. For details, see Modifying
Configuration Items in 4.1Negotiating Interconnection Parameters for the Throughput Stat Data
Northbound Result File Interface.
 After the configuration item is modified or the NE is renamed, historical data will not be modified to
prevent the NMS from collecting data repeatedly.
 When the configuration item is modified to neName as the output directory, neName can not name
as ...
 The dataList subdirectory in the /export/home/omc/var/fileint/TSNBI/UMTS_PCHR/ directory
stores the index files whose names start with Datalist. These index files help the FTP server quickly
send the throughput stat data northbound result files from the Trace Server to the NMS.
For example:
 When NE identifier is NEFDN, if a UMTS_PCHR result file is generated on May 11,
2014, the /export/home/omc/var/fileint/TSNBI/UMTS_PCHR/20140511/NEFDN/
directory is automatically created for saving all UMTS_PCHR result files that were
generated on May 11, 2014.
 When NE identifier is neName, if a UMTS_PCHR result file is generated on May 11,
2014, the /export/home/omc/var/fileint/TSNBI/UMTS_PCHR/20140511/neName/
directory is automatically created for saving all UMTS_PCHR result files that were
generated on May 11, 2014.
2.3 Naming Conventions of Throughput Stat Data

Northbound Result Files
The Trace Server saves NE data as throughput stat data northbound result files.
The naming conventions are as follows:
 When the NE identifier is NEFDN,
naming conventions for a UMTS_PCHR result file are
<NEFDN>_<No>_<StartTime>_<EndTime>_<SN>.<FilePostfix>.gz.
 When the NE identifier is neName,

Copyright © Huawei
U2000
naming conventions for a UMTS_PCHR result file are

<neName>_<No>_<StartTime>_<EndTime>_<SN>.<FilePostfix>.gz.
Table 1.2 Parameter of naming conventions

Parameter Description
NEFDN or neName NE identifiers include NEFDN and neName. You can be

modified on the U2000 client. For details, see Modifying
Configuration Items in 4.1Negotiating Interconnection
Parameters for the Throughput Stat Data Northbound Result
File Interface.
No Combination of the RNC subrack number, slot number, and
SPU number for UMTS_STDM result files
StartTime Start time in the name of an NE-reported file. The format is
YYYYMMDDhhmmssDST, where YYYY indicates the year,
MM indicates the month, DD indicates the day, hh indicates
the hour, mm indicates the minute, and ss indicates the second.
DST is optional, depending on whether the NE is in daylight
saving time (DST) mode.
EndTime End time in the name of an NE-reported file. The format is
YYYYMMDDhhmmssDST, where YYYY indicates the year,
MM indicates the month, DD indicates the day, hh indicates
the hour, mm indicates the minute, and ss indicates the second.
DST is optional, depending on whether the NE is in daylight
saving time (DST) mode.
SN Generated series number of the file. Value range: 0000 to
9999. The serial number ranges from 0000 to 9999 cyclically.
FilePostfix File name extension.
The extension is log for UMTS_PCHR result files.
If another NE uploads no files or no NEs upload files for a long time, the end time increases by one file
generation period in the name of the last NE-reported file.
For example:
 When the NE identifier is NEFDN, the subrack number is 02, the slot number is 00, the
SPU number is 58, the SN is 1234, the start time in an NE-reported file is 2014-05-11
17:30:30, the end time in the NE-reported file is 2014-05-11 17:32:40, the name of the
generated UMTS_PCHR result file is
NEFDN_020058_20140511173030_20140511173240_1234.log.gz.
 When the NE identifier is neName, the subrack number is 02, the slot number is 00, the
SPU number is 58, the SN is 1234, the start time in an NE-reported file is 2014-05-11
17:30:30, the end time in the NE-reported file is 2014-05-11 17:32:40, the name of the
generated UMTS_PCHR result file is
neName_020058_20140511173030_20140511173240_1234.log.gz.

Copyright © Huawei
U2000
2.4 Generation Periods of Throughput Stat Data

Northbound Result Files
This section describes the generation periods of throughput stat data northbound result files.
When the volume or generation period of northbound analysis result UMTS_PCHR is greater
than those specified in 4.1Negotiating Interconnection Parameters for the Throughput Stat
Data Northbound Result File Interface, northbound analysis result files are generated. The
default generated file size and generation period are 10 MB and 5 minutes, respectively.
 If the NE does not report the new data file for at least 30 minutes or the Trace Server service stops,
NE northbound result files are also generated.
 If the NE identifier has been modified, NE northbound result files are also generated.
2.5 Formats of Throughput Stat Data Northbound Result

Files
This section describes the formats of throughput stat data northbound result files.
A UMTS throughput stat data northbound result file consists of a file header and a file body,
as shown in Figure 1.2. The file header provides the file information. The file body consists of
all events reported from the NE. Each event consists of an event header and the event content.
Figure 1.2 Format of a UMTS throughput stat data northbound result file
Format of a UMTS Throughput Stat Data Northbound Result File Header
Table 1.1 Format of a UMTS throughput stat data northbound result file header
Field Data Type and Length Description
Data Version N/A Version information

>Main Version UINT8 Main version

Copyright © Huawei
U2000
Field Data Type and Length Description
>Sub Version UINT8 Sub version

Spare OCTET STRING (30) Spare
 If the > symbol is displayed before a field, the field is a sub-field. For example, if the seven fields A,
>B, >C, >>D, >>E, >F, and G are available in the file in sequence, fields B, C, and F are the sub-
fields of field A, and fields D and E are the sub-fields of sub-field C.
 The invalid byte is filled with FF and the invalid bit is filled with 0 in the fields.
Format of a UMTS Throughput Stat Data Northbound Event Header
Table 1.1 Format of a UMTS throughput stat data northbound event header
Data Type and
Field Description Introduced In
Length
Event ID UINT16 Event identifier SRAN11.0

Event length
Length from the
Event Length UINT16 character after this SRAN11.0
field to the end of
the log
RNC ID UINT16 RNC identifier SRAN11.0
U-RNTI N/A U-RNTI SRAN11.0
Identifier of the
>Serving RNC ID BIT STRING (12) SRAN11.0
serving RNC
>SRNTI BIT STRING (20) SRNTI SRAN11.0
Local time
CHR: call
connection setup
Date Time N/A SRAN11.0
time
MR: measurement
report time
Year
>Year UINT8 Difference between SRAN11.0
the current year and
the year 2000
Month
>Month UINT8 SRAN11.0
Value range: 1 to 12
Day
>Day UINT8 SRAN11.0

Copyright © Huawei
U2000
Data Type and

Length
Hour
>Hour UINT8 SRAN11.0
Minute
>Minute UINT8 SRAN11.0
Second
>Second UINT8 SRAN11.0
Tick
>Tick UINT8 SRAN11.0
Unit: 10 ms
Daylight saving time
(DST) flag
>DSTFlag UINT8 SRAN11.0
0: non-DST
1: DST
OCTET STRING
Spare Spare N/A
(4)
If NE-reported data contains the incorrect year, month, and day, the year, month, and day are
0-1-1 in the northbound analysis result. If NE-reported data contains the incorrect hour,
minute, and second, the hour, minute, and second are 23-59-59 in the northbound analysis
result. You are advised to prevent data analysis problems caused by data errors.
For security purpose, message fields that involve subscriber privacy are anonymized.
Formats of UMTS Throughput Statistical Data Event Content
Table 1.1 Format of the PS Throughput Period Stat (0x1101) event content
Data Type and
Length
Record time
It is the time relative
to Date Time in the
Record time UINT32 event header. SRAN11.0
Unit: 10 ms
Invalid value: all Fs
RAB ID UINT8 RAB identifier SRAN11.0

Copyright © Huawei
U2000
Data Type and

Length
PS Traffic Statistic PS traffic statistic

N/A SRAN11.0
Info List information list
Number of cells
>Cell Count UINT8 SRAN11.0
Value range: 1 to 6
Cell statistic
>Cell Statistic Info information list
N/A SRAN11.0
List
Statistic cycle: 60s
Cell identifier
The high 16 bits are
>>Cell ID UINT32 the RNC ID, and the SRAN11.0
low 16 bits are the
cell ID.
HSDPA RLC SDU
>>HSDPA Data throughput capacity
UNIT32 SRAN11.0
Volume
Unit: byte
HSDPA data
transmission time
>>HSDPA Data
UNIT16 Sample size: SRAN11.0
Transmission Time
scheduling interval
Unit: 1 ms
HSUPA RLC SDU
>>HSUPA Data throughput capacity
UNIT32 SRAN11.0
Volume
Unit: byte
HSUPA Data
>>HSUPA Data transmission time
UNIT16 SRAN11.0
Transmission Time Sample size: 100 ms
Unit: 1 ms
Downlink DCH
>>DL DCH Data RLC SDU
UNIT32 throughput capacity SRAN11.0
Volume
Unit: byte
Downlink DCH data
transmission time
>>DL DCH Data
UNIT16 Sample size: TTI*10 SRAN11.0
Transmission Time
ms at least
Unit: 1 ms
Uplink DCH RLC
>>UL DCH Data SDU throughput
UNIT32 capacity SRAN11.0
Volume
Unit: byte

Copyright © Huawei
U2000
Data Type and

Length
Uplink DCH data

transmission time
>>UL DCH Data
UNIT16 Sample size: TTI*10 SRAN11.0
Transmission Time
ms at least
Unit: 1 ms
FACH RLC SDU
>>FACH Data throughput capacity
UNIT32 SRAN11.0
Volume
Unit: byte
FACH data
>>FACH Data transmission time
UNIT16 SRAN11.0
Unit: 1 ms
RACH RLC SDU
>>RACH Data throughput capacity
UNIT32 SRAN11.0
Volume
Unit: byte
RACH data
>>RACH Data transmission time
UNIT16 SRAN11.0
Unit: 1 ms

Copyright © Huawei
U2000
Trace Server UMTS Throughput Stat Northbound File Managing Northbound Users in RAN Sharing Scenarios
Interface Developer Guide Managing Northbound Users in RAN Sharing Scenarios
3 Managing Northbound Users in RAN

Sharing Scenarios
About This Chapter

This section describes how to manage northbound users in RAN sharing scenarios. In such
scenarios, multiple operators can share one radio access network (RAN). Northbound files
reported by one NE contain northbound data from different operators. The Trace Server
identifies different operators according to the PLMN in the northbound files and saves
generated northbound result files in different directories. Operators create specified
northbound users to obtain required northbound result files in FTP mode.
3.1 Creating Northbound Users
This section describes how to create specified northbound users using the northbound user
configuration tool, helping operators obtain required northbound result files.
3.2 Viewing Northbound Users
This section describes how to view created northbound users, their permissions, and PLMNs
using the northbound user configuration tool.
3.3 Modifying Northbound User Passwords
This section describes how to modify the password of a created northbound user using the
northbound user configuration tool. To improve data security, properly keep the password of
the northbound user and change it periodically.
3.4 Deleting Northbound Users
This section describes how to delete northbound users who are not used any more using the
northbound user configuration tool.
3.5 Deleting Northbound User PLMNs
This section describes how to delete northbound user PLMNs using the northbound user
configuration tool.
3.6 Configuring the Northbound RAN Sharing Function Switch

Copyright © Huawei
U2000
This section describes how to configure the RAN function control item on the Trace Server
over the GSM, UMTS, or LTE northbound file interfaces using the northbound user
configuration tool. By default, the RAN sharing function is disabled.
3.1 Creating Northbound Users

This section describes how to create specified northbound users using the northbound user
configuration tool, helping operators obtain required northbound result files.
Prerequisites
You have obtained passwords of users ossuser and root on the U2000 server (Trace Server
co-deployed with the U2000 in the ATAE cluster system) or on the Trace Server (Trace Server
independently deployed in an ATAE cluster system).
Context
To improve security of users' passwords, set passwords based on the following rules:
 A password must contain 8 to 30 characters.
 A password must contain at least one uppercase letter.
 A password must contain at least one lowercase letter.
 A password must contain at least one digit.
 A password must contain at least one special character @%-=_.]{}
 A password must not be the same as the user name or the reverse order of the user name.
 A password cannot contain three or more consecutive characters that are the same (for
example, AAA and 111).
 The number of neighboring digits or letters is limited to four pairs
For example, the password Changeme_121212 does not meet this complexity
requirement because 121212 has a total of five pairs of digits (12 is a pair, 21 is another
pair, and so on).
 A password must not contain any spaces.
 A password must not be one of the 12 passwords that are recently used.
Procedure
Step 1 Use PuTTY to log in to the U2000 master server (Trace Server co-deployed with the U2000
in the ATAE cluster system) or Trace Server master server (Trace Server independently
deployed) in SSH mode as user ossuser.
Step 2 Run the following command to switch to user root:
~> su - root
Password:Password of root
Step 3 Run the following commands to run the RAN sharing northbound user configuration tool:
 For the Trace Server independently deployed, run the following command.
# cd /opt/oss/server/rancn/bin

Copyright © Huawei
U2000
 For the Trace Server co-deployed with the U2000 in the ATAE cluster system, run the
following command.
# cd /opt/oss/server/rancn/tools/TSTools
# sh setRANSharingUser.sh
Step 4 When the following information is displayed, enter B or b and press Enter:
Please select an operation type.
A--Show the northbound user list.
B--Create a northbound user.
C--Reconfigure the password of northbound user.
D--Delete a northbound user or a single PLMN.
E--Set the GUL switch.
Q--Exit
Please select:
Step 5 When the following information is displayed, enter the northbound user name and press
Enter:
Please enter your user name.
Step 6 When the following information is displayed, enter the PLMN of the northbound user and
press Enter:
Please enter your PLMN number.
Step 7 When the following information is displayed, choose Yy or Nn to determine whether

northbound users need to access the public data and press Enter:
Are you sure you want to view common data? [Yy/Nn]:[default=Y]
Step 8 When the following information is displayed, enter the password of the northbound user and
press Enter. You need to enter the new password twice.
New Password: password of northbound user
Reenter New Password: password of northbound user
Step 9 If the following information is displayed, the RAN sharing northbound user has been created
successfully. Otherwise, contact Huawei technical support.
User Northbound user name created successfully.
----End
Follow-up Procedures
 If the PLMN needs to be separately added for created northbound users, repeat the
operations from Step 1 to Step 7 and enter the PLMN to be added in Step 6. When the
following information is displayed, the PLMN has been added successfully. Otherwise,
contact Huawei technical support.
The northbound user already exists.
User northbound user name created successfully.
 If access permissions of created northbound users on public data need to be changed,

perform the operations from Step 1 to Step 7. Reconfigure the access permissions for
northbound users in Step 7. When the following information is displayed, the

Copyright © Huawei
U2000
permissions have been changed successfully. Otherwise, contact Huawei technical

support.
The northbound user already exists.
User northbound user name created successfully.
TC
After the access permissions of northbound users on public data are changed, you must log in to the
Trace Server again to make the change take effect.
3.2 Viewing Northbound Users

This section describes how to view created northbound users, their permissions, and PLMNs
using the northbound user configuration tool.
Prerequisites
Procedure
~> su - root
following command.
Step 4 When the following information is displayed, enter A or a and press Enter to view the created
RAN sharing northbound users:
Q--Exit
Please select:

Copyright © Huawei
U2000
Step 5 When information similar to the following is displayed, you can view created northbound
users, their permissions to access public data, and PLMNs of all users:
-----------------------------------------------
Username CommonData PLMN
user1 Y 1111,22222,333333
user2 Y 44444
user3 N 555555
-----------------------------------------------
----End
3.3 Modifying Northbound User Passwords

This section describes how to modify the password of a created northbound user using the
northbound user configuration tool. To improve data security, properly keep the password of
the northbound user and change it periodically.
Prerequisites
Context
To improve security of users' passwords, set passwords based on the following rules:
 A password must contain 8 to 30 characters.
 A password must contain at least one uppercase letter.
 A password must contain at least one lowercase letter.
 A password must contain at least one digit.
 A password must contain at least one special character @%-=_.]{}
 A password must not be the same as the user name or the reverse order of the user name.
 A password cannot contain three or more consecutive characters that are the same (for
example, AAA and 111).
 The number of neighboring digits or letters is limited to four pairs
For example, the password Changeme_121212 does not meet this complexity
requirement because 121212 has a total of five pairs of digits (12 is a pair, 21 is another
pair, and so on).
 A password must not contain any spaces.
 A password must not be one of the 12 passwords that are recently used.
Procedure

Copyright © Huawei
U2000
~> su - root
following command.
Step 4 When the following information is displayed, enter C or c and press Enter:
Q--Exit
Please select:
Step 5 When the following information is displayed, enter the northbound user name to be modified
and press Enter:
Please enter the user name.
Step 6 When the following information is displayed, enter the new password of the northbound user
and press Enter. You need to enter the new password twice.
Changing password for Northbound user name.
New Password: password of northbound user
Reenter New Password: password of northbound user
Step 7 If the following information is displayed, the password of the northbound user has been
modified successfully. Otherwise, contact Huawei technical support engineers.
Password changed.
----End
3.4 Deleting Northbound Users

This section describes how to delete northbound users who are not used any more using the
northbound user configuration tool.
Prerequisites
Procedure
Copyright © Huawei
U2000
~> su - root
following command.
Step 4 When the following information is displayed, enter D or d and press Enter:
Q--Exit
Please select:
Step 5 When the following information is displayed, enter B or b and press Enter:
A--Delete a single PLMN under a user.
B--Delete a northbound user.
Q--Exit
Please select:
Step 6 When the following information is displayed, enter the northbound user name to be deleted,
user1 for example, and press Enter:
Please enter the user name to delete:
user1
Step 7 When the following information is displayed, enter Y or y and press Enter:
User user1 has the following PLMNs:
1111 22222 333333
Are you sure you want to delete all PLMNs under user user1? [Yy/Nn]
The operation will delete all NBI result files under the PLMN.
The operation will take a few minutes.
Please select:
Step 8 If the following information is displayed, the northbound user user1 has been deleted
successfully. Otherwise, contact Huawei technical support engineers.
User user1 deleted successfully.
----End

Copyright © Huawei
U2000
3.5 Deleting Northbound User PLMNs

This section describes how to delete northbound user PLMNs using the northbound user
configuration tool.
Prerequisites
Procedure
~> su - root
following command.
Step 4 When the following information is displayed, enter D or d and press Enter:
Q--Exit
Please select:
Step 5 When the following information is displayed, enter A or a and press Enter:
A--Delete a single PLMN under a user.
B--Delete a northbound user.
Q--Exit
Please select:
Step 6 When the following information is displayed, enter the northbound user name to be deleted
that the PLMN belongs to, user1 for example, and press Enter:
Please enter the user name to delete:
user1

Copyright © Huawei
U2000
Step 7 When the following information is displayed, enter the PLMN to be deleted, 1111 for
example, and press Enter:
User user1 has the following PLMNs:
1111 22222 333333
Please enter the PLMN:
1111
Step 8 When the following information is displayed, enter Y or y and press Enter:
Are you sure you want to delete a single PLMN? [Yy/Nn]
The operation will delete all NBI result files under the PLMN.
The operation will take a few minutes.
Please select:
Step 9 If the following information is displayed, the value 1111 of the PLMN for northbound user
user1 has been deleted successfully. Otherwise, contact Huawei technical support.
Single PLMN under user user1 deleted successfully.
----End
3.6 Configuring the Northbound RAN Sharing Function

Switch
This section describes how to configure the RAN function control item on the Trace Server
over the GSM, UMTS, or LTE northbound file interfaces using the northbound user
configuration tool. By default, the RAN sharing function is disabled.
Prerequisites
Context
After the RAN sharing function is enabled, the Trace Server saves northbound analysis result
files in the /export/home/sysm/export/home/omc/var/fileint/TSNBI/shared/ directory and
creates subdirectories under this directory.
 If PLMN values are not all Fs, the subdirectory naming conventions are PLMN
value/Result File Name/yyyymmdd/NE identifier/.
 If PLMN values are all Fs, the subdirectory naming conventions are
commonData/Result File Name/yyyymmdd/NE identifier/.
Procedure

Copyright © Huawei
U2000
~> su - root
following command.
Step 4 When the following information is displayed, enter E or e and press Enter:
Q--Exit
Please select:
Step 5 When the following information is displayed, enter B or b and press Enter (enabling the
UMTS RAN sharing function is used as an example here):
-----------RAN Sharing Switch Status-----------
A.GSM-------off
B.UMTS------off
C.LTE-------off
-----------------------------------------------
A--Set the GSM switch status.
B--Set the UMTS switch status.
C--Set the LTE switch status.
Q--Exit
Please select:
Step 6 When the following information is displayed, enter ON or on and press Enter (enabling the
UMTS RAN sharing function is used as an example here):
Are you sure you want to set the status of the UMTS switch? [ON/OFF]
Step 7 If the following information is displayed, the UMTS RAN sharing function has been enabled
successfully. Otherwise, contact Huawei technical support.
UMTS switch set successfully.
-----------RAN Sharing Switch Status-----------
A.GSM-------off
B.UMTS------on
C.LTE-------off
-----------------------------------------------
A--Set the GSM switch status.
B--Set the UMTS switch status.
C--Set the LTE switch status.

Copyright © Huawei
U2000
Q--Exit
Please select:
Step 8 Type Q and press Enter. Return to the RAN sharing northbound user configuration tool main
interface.
Step 9 Type Q and press Enter. Exit the RAN sharing northbound user configuration tool.
Step 10 Run the following commands to restart the Trace Server services.
# exit
~> . /opt/oss/server/svc_profile.sh
~> stop_svc
If the command output contains Finished stopping the service., Trace Server services
have been stopped successfully.
~> start_svc
If the command output contains Finished starting the system., the Trace Server service
has been started successfully.
following command.
~> svc_deploy -cmd querysvc | awk '{print $2}' | grep 'TSCollector' | xargs -L1
svc_adm -cmd restartsvc
Step 11 Run the following commands to verify that the Trace Server services are restarted
successfully:
~> svc_adm -cmd status -sysagent all | grep TSCollector | grep "not running"
When there is no information displayed, the Trace Server services are restarted successfully.
----End

Copyright © Huawei
Process for Interconnecting the Throughput Stat Data
U2000 Northbound Result File InterfaceProcess for
Trace Server UMTS Throughput Stat Northbound File Interconnecting the Throughput Stat Data Northbound
4 Process for Interconnecting the

Throughput Stat Data Northbound Result File
Interface
About This Chapter

This chapter describes the process for interconnecting the NMS with the Trace Server by
using the throughput stat data northbound result file interface.
Figure 11.1 lists the process for interconnecting the throughput stat data northbound result file
interface.

Copyright © Huawei
Figure 11.1 Flow chart of process for interconnecting the throughput stat data northbound result
file interface
4.1 Negotiating Interconnection Parameters for the Throughput Stat Data Northbound Result
File Interface
This section describes the preparations for interconnecting the Trace Server with the NMS.
4.2 Setting the SAU IP Address on NEs
The SAU IP address is used by the SAU to communicate with an RNC. The northbound
interface supports EMS SAUs only. If the SAU IP address has been configured, skip this
section.
4.3 Delivering the throughput stat data northbound Event Subscription
Before configuring the throughput stat data northbound interface, you need to start an event
subscription task. NEs upload the data to the Trace Server and the Trace Server automatically
generates a northbound result file.
4.4 Commissioning the Interconnection of the Throughput Stat Data Northbound Result File
Interface
The NMS obtains throughput stat data northbound result files generated by the Trace Server
by using FTP or SFTP. Based on the files, you can determine whether the throughput stat data
northbound result interface meets the requirements for interconnecting with the NMS.
4.5 Optional: Setting the Northbound Push FTP Server (Trace Server Co-deployed with the
U2000 in the ATAE Cluster System)
Before commissioning the XFTP northbound file push function, you need to set an FTP server
to receive data. After the FTP server is set successfully, the Trace Server will scan the
northbound files every 5 minutes and push the scanned files to the specified FTP server.

Copyright © Huawei
4.6 Optional: Setting the Northbound Push FTP Server (ATAE Cluster and Virtual Cluster,
Standalone)
4.1 Negotiating Interconnection Parameters for the

Throughput Stat Data Northbound Result File Interface
This section describes the preparations for interconnecting the Trace Server with the NMS.
Checking the License

Perform the following steps to check whether the U2000 is licensed to use the trace result file
interface:
1. Log in to the M2000 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 the Throughput statistic
data BIN file interface - WRAN item, click the Function Control Item tab. If
Function contains the Trace data BIN file interface item, the throughput stat data
northbound result file interface is available. If there is no license, the throughput stat data
northbound result file interface is unavailable. If you need to use this function, contact
Huawei technical support engineers.
Negotiated Interconnection Parameters

Table 1.1 describes the parameters.
Table 1.1 Negotiated interconnection parameters

FTP Parameter Parameter Description
(Recommended) If FTP user name Value: ftpuser or the northbound user in

the Trace Server RAN sharing scenery.
serves as an FTP
server, the NMS Password For details about how to obtain the
obtains files from password, contact the Trace Server
the Trace Server. administrator.
FTP port Value: 21
If you use FTP to transfer files, open the
port on the Trace Server.
SFTP port Value: 22
If you use SFTP to transfer files, open the
port on the Trace Server.

Copyright © Huawei
FTP Parameter Parameter Description
Path for saving files After collecting and processing NE-reported

data, the Trace Server saves northbound
analysis result files on the server managing
NEs.
 If RAN sharing is enabled, the Trace
Server saves northbound analysis result
files in the
/export/home/omc/var/fileint/TSNBI/s
hared/ directory and creates
subdirectories.
 If RAN sharing is disabled, the Trace
Server saves northbound analysis result
files in the
/export/home/omc/var/fileint/TSNBI/
directory and creates subdirectories.
If the Trace Server FTP user name Provided by the NMS.
serves as an FTP
client, it Password Provided by the NMS.
automatically
FTP port Value: 21
uploads files to the
NMS. If you use FTP to transfer files, open the
port on the NMS.
SFTP port Value: 22
If you use SFTP to transfer files, open the
port on the NMS.
Path for saving files Provided by the NMS.
Trace Server uploads trace result files to this
path of NMS.
Modifying Configuration Items

Prerequisites
 The U2000 has loaded the licenses related to northbound trace.
 You have logged in to the U2000 client.
Procedure
1. Choose Maintenance > Trace Server Maintenance > Trace Server Parameter
Settings (traditional style) or double click Trace and Maintenance in Application
Center and choose Trace Server Maintenance > Trace Server Parameter Settings
(application style).
2. In the navigation tree, choose the OSSii item to set.
3. Set related parameters in the right area box by referring to Table 1.1.

Copyright © Huawei
Table 1.1 OSSii parameter settings

Area Box Name Parameter Name Parameter Description
OSSii parameter settings Storage duration Storage duration of the NBI

result file directory on the
server
Value range: 1 to 72 (hour)
Default value: 72
NE identifier NBI result file naming
convention, which can be set
by selecting the NE
identifier
Values: NE Name and NE
FDN
Default value: NE FDN
Generated file size Minimum size of generated
NBI result files
Values: 1, 5, 10, 15, and 30
(MB)
Default value: 10
File generation period Generation period of NBI
result files
Values: 1, 5, and 10 (minute)
Default value: 5
Subscription time offset Start subscription time NBI subscription allows you
setting to issue subscription
commands at a time earlier
than the predefined
subscription start time to
ensure integrity of NBI
result data, considering the
subscription issuing
duration.
Values: 0, 5, 10, and 15
(minute)
Default value: 10

Copyright © Huawei
Area Box Name Parameter Name Parameter Description
Stop subscription time NBI subscription allows you

to stop subscription at a time
later than the predefined
subscription end time to
ensure integrity of NBI
result data, considering
delays in southbound data
reporting and northbound
data processing.
Values: 0, 5, 10, and 15
(minute)
Default value: 15
4. If other Trace Server parameters need to be set, click Apply and set these parameters. If
the parameter setting is complete, click OK.
5. Re-log in to U2000 client.
4.2 Setting the SAU IP Address on NEs

The SAU IP address is used by the SAU to communicate with an RNC. The northbound
interface supports EMS SAUs only. If the SAU IP address has been configured, skip this
section.
Prerequisites
 The SAU IP address has been planned.
Procedure
Step 1 Choose Topology > Main Topology (traditional style); alternatively, double-click Topo View
in Application Center and choose Topology > Main Topology (application style) . The
Main Topology window is displayed.
Step 2 In the topology navigation tree or topology view, select an NE you want to modify.
Step 3 Right-click the NE and choose Properties from the shortcut menu.
Step 4 In the Properties dialog box, modify the SAU IP Address.
Currently, this function applies to the following NEs: BSC6900 UMTS, BSC6900 GU, BSC6910
UMTS, and BSC6910 GU.
Step 5 Click OK.
If you modify NE property, after click OK, a tip is displayed as following: Please ensure that the
correct attributes, some changes may have broken station property risks, such as: IP Address, NE
Connection Mode, OSS Authentication Mode, and so on. Are you sure you want to continue?.

Copyright © Huawei
----End
4.3 Delivering the throughput stat data northbound Event

Subscription
Before configuring the throughput stat data northbound interface, you need to start an event
subscription task. NEs upload the data to the Trace Server and the Trace Server automatically
generates a northbound result file.
4.3.1 Subscribing to a UMTS Cell Trace Task

This section describes how to subscribe to an NE trace task. You can subscribe to an UMTS
NE trace task to obtain the trace files that the Trace Server northbound interface has analyzed
from a specified directory on the U2000 for northbound interconnection.
Prerequisites
 You have purchased the license for UMTS cell trace.
 You have installed the mediations of UMTS NEs and NEs are accessed to U2000
successfully.
 You must have the operation permission Trace Server NBI.
Context
After the NE version is upgraded, do not resubscribe to the messages that have been
subscribed to on the U2000 client.
Procedure
Step 1 Choose Monitor > Trace Server NBI > UMTS (traditional style); alternatively, double-click
Trace and Maintenance in Application Center and choose Trace Server NBI > UMTS
(application style). The UMTS Trace Server NBI window is displayed.
Step 2 In the NE navigation tree, choose an NE type, an NE version, and NE information.
NE Name, Subscribed Status, Start Time, End Time, Collection State, Collection Time,
and Operation Result are displayed on the right pane.
Step 3 In the right pane, select an NE to which subscription is to be issued, right-click the NE, and
choose Subscribe from the shortcut menu.
Step 4 In the Message Settings area, select the message contents that you want to subscribe to.
The Message Settings area displays the message contents supported by the NE, the message
contents that you have subscribed to, and subscribe to a failed message.
 If many message contents are available, enter the message keywords in the Find Message text box
and click Previous or Next to search for the required message contents.
 To subscribe to all message contents or cancel the subscription of all message contents, you can
right-click in the message list in the Message Settings area and choose Select All or Clear All from
the shortcut menu to quickly subscribe to or cancel the subscription of all message contents.

Copyright © Huawei
 For message contents to be subscribed to, right-click the message setting list of the Message
Settings area and choose Export or Import from the shortcut menu to export configured message
contents from existing message configurations or import configured message contents to existing
message configurations.
Step 5 In the displayed dialog box, set required subscription parameters in Time Parameter Settings
area.
Collection time in the Time Parameter Settings area is used to control the time segment for data
reporting. After this parameter is set to a time segment, the Trace Server processes and reports data
collected within the time segment. For example, if the subscription start time is 2016–07–22 10:05, the
subscription end time is 2016–07–23 10:05, and Collection time is set to 11:00 to 12:00, the Trace
Server processes and reports data collected from 2016–07–22 11:00:00 to 2016–07–22 11:59:59. If
Collection time is not set to a specific value (Collection time is deselected), the Trace Server processes
and reports data collected from the subscription start time to the subscription end time.
Step 6 Click Apply.

The subscription task is started, and NE subscription information is displayed in the right
pane.
----End
4.3.2 GUIs for UMTS Northbound Interface Trace

This section describes the function of each component in the UMTS Trace Server NBI
window.
Figure 6.1 shows the UMTS Trace Server NBI window. Table 1.1 describes the window
shown in Figure 6.1.
Figure 6.1 UMTS Trace Server NBI-main window

Copyright © Huawei
Table 1.1 UMTS Trace Server NBI-main window

No. Name Description
1 NE By default, the NE navigation tree is displayed by

navigation network topology.
tree
2 Import and NE selected state support import and export functions.
export
buttons
3 Message Allows users to set messages provided by NEs.
setting area
4 Detailed Displays detailed subscription information.
subscription NOTE
information If different licences of Trace Server northbound file interface are
area loaded, the displayed message list is different too.
5 Button bar Provides the apply and cancel functions.
4.3.3 Parameters for Subscribing to a UMTS NE Trace Task

This section describes the parameters for subscribing to UMTS NE trace tasks.
Table 1.2 Parameters for subscribing to a UMTS NE trace task

Area Parameter Description
NE By default, the NE navigation tree is displayed by

network topology.
Time Start Time Indicates the subscription start time.
Parameter
Settings End Time Indicates the subscription end time.
Collection Indicates the specific hour-level time segment for
Time subscription.
You can specify some hour-level time segments
intersecting with the subscription start time and end time
as the subscription time segments.
Default value: All day
Message Find Message You can type the keywords and click Previous or Next
Settings to search for the required messages.
Message ID Uniquely identifies a message.
Message Indicates the name of a message.
Name
Message Type Indicates the type of a message.

Copyright © Huawei
Area Parameter Description
Export Allows you to export message events configured on

existing NEs and import them to message configurations
on other NEs to configure message events quickly. You
can also export a template that is not configured with
message events, set required message events, and import
the configured template to NE message configurations.
CSV, XLS, and XLSX export files are available.
Import Allows you to import recently exported message event
configurations or manually modified message event
templates to NE message configurations to configure
message events quickly.
Message events to be imported are in the unavailable
and selected state. If the message events are contained in
the imported file, the message events are in the available
state. Otherwise, status of the message events remains
unchanged.
CSV, XLS, and XLSX import files are available.
Detailed NE Name Indicates the name of the NE whose data needs to be
subscription subscribed to.
information
area Subscribed Indicates the existing subscription status. Values of the
Status parameter are as follows:
 Subscribing: indicates that the Trace Server is issuing
subscription to a target NE.
 Subscribed: indicates that the Trace Server issues
subscription to a target NE successfully.
 Unsubscribed: indicates that the Trace Server has
issued no subscription to a target NE or canceled
subscription to a target NE.
 Unsubscribing: indicates that the Trace Server is
canceling subscription to a target NE.
Start Time Indicates the subscription start time.
End Time Indicates the subscription end time.
Collection Indicates whether the Trace Server is collecting data
State from a selected NE. Values of the parameter are as
follows:
 Running: indicates that the Trace Server is collecting
data from a target NE.
 Idle: indicates that the Trace Server collects no data
from a target NE.
Collection Indicates the specific hour-level time segment for
Time subscription in a day.
Operation Summarizes successful and failed subscription
Result information.

Copyright © Huawei
Table 1.3 Shortcut menus for UMTS NE subscription

The portal for UMTS NE subscription: Select the NE to be subscribed to in the left NE
navigation tree in the UMTS Trace Server NBI window and select a subscription record in the
NE subscription information list in the right area.
Shortcut Menu Description
Subscribe Allows you to subscribe to a UMTS NE trace task. The Subscribe

page displays events whose subscription is issued on the U2000
client.
Subscribe all NEs Allows you to subscribe to all selected UMTS NE trace tasks.
View details Allows you to view the detailed subscription information. Related
parameters cannot be modified. The detailed subscription page
displays events whose subscription has been issued and taken effect.
You can view subscription details on the Subscribe page at off-peak
hours.
Unsubscribe Allows you to unsubscribe to a UMTS NE trace task.
Unsubscribe all Allows you to unsubscribe to all selected UMTS NE trace tasks.
NEs.
Table 1.4 Shortcut menu for message settings

You can right-click the Message Settings area on the Subscribe page and choose an item
from the shortcut menu to manage messages.
Select ALL Allows you to select all message events

quickly.
Clear ALL Allows you to deselect all message events
quickly.
Export Allows you to export message events
configured on existing NEs and import them
to message configurations on other NEs to
configure message events quickly. You can
also export a template that is not configured
with message events, set required message
events, and import the configured template
to NE message configurations.
CSV, XLS, and XLSX export files are
available.
Import Allows you to import recently exported
message event configurations or manually
modified message event templates to NE
message configurations to configure

Copyright © Huawei
message events quickly.

Message events to be imported are in the
unavailable and selected state. If the
message events are contained in the
imported file, the message events are in the
available state. Otherwise, status of the
message events remains unchanged.
CSV, XLS, and XLSX import files are
available.
4.4 Commissioning the Interconnection of the Throughput

Stat Data Northbound Result File Interface
The NMS obtains throughput stat data northbound result files generated by the Trace Server
by using FTP or SFTP. Based on the files, you can determine whether the throughput stat data
northbound result interface meets the requirements for interconnecting with the NMS.
Prerequisites
 The NMS and the Trace Server are connected properly.
 You have obtained the IP address of the Trace Server (the FTP server) and the FTP user
name and password.
 You have obtained the throughput stat data northbound result file name and save path.
For details, see 2Overview of Result Files.
 You have deliveried an event subscription task. For details, see 4.3.1Error: Reference
source not found.
 You have logged in to the NMS server.
Context
The NMS obtains northbound result files from a specified directory on the Trace Server using
FTP or SFTP.
Procedure
Step 1 Log in using FTP or SFTP.
If you need to... Run the following command...
Log in using FTP ftp IP address of the Trace Server
Log in using SFTP sftp user name@IP address of the Trace Server
You are advised to use the SFTP protocols because the SFTP protocols is more secure than the FTP
protocols.

Copyright © Huawei
Step 2 Type the user name and the password as prompted.

Step 3 Run the following command to set the save path for throughput stat data northbound result
files on the Trace Server.
> cd /export/home/omc/var/fileint/TSNBI/FileType/yyyymmdd/NE identifier/
FileType indicates the data type, such as UMTS_PCHR. yyyymmdd indicates the date and NE identifier
contains neName and NEFDN.
Step 4 Run the following command to set the destination save path for throughput stat data
northbound result files on the NMS. (The directory /opt/file is used as an example).
> lcd /opt/file
Step 5 Run the following command to set the transfer mode to binary mode if files are obtained by
using FTP. Otherwise, skip this step.
> bin
Step 6 Run the following command to obtain files.
> get Northbound result file name
Step 7 Run the bye command to exit FTP or SFTP after files have been downloaded.
Step 8 Check the obtained throughput stat data northbound files.
1. Based on the file name, check that the NE information and time are consistent with those
of the task issued by a customer.
2. Parse the throughput stat data northbound files. For details, see 2.5Formats of
Throughput Stat Data Northbound Result Files.
The northbound throughput stat data northbound result file interface meets the
interconnection conditions if the results in the files are consistent with the signaling
information that a customer subscribes to. Otherwise, contact Huawei technical support
engineer.
----End
4.5 Optional: Setting the Northbound Push FTP Server

(Trace Server Co-deployed with the U2000 in the ATAE
Cluster System)
Prerequisites
 The Trace Server and the U2000 server are connected properly.
 The mediation software of the NE on the LTE network has been installed on the U2000
server.

Copyright © Huawei
 The U2000 has loaded the licenses related to northbound trace.

 You must have the permission of file server setting.
 Subscription has been delivered to the Trace Server, and a trace file has been generated
in /export/home/omc/var/fileint/TSNBI/ on the Trace Server boards.
If you need to set the transmission mode between the Trace Server co-deployed with the U2000 in the
ATAE cluster system and the upper-layer NMS for the public and private key authentication to SFTP,
perform the instruction provided in section Configuring the SFTP for Actively Transferring Files
over the Northbound Interface (Public and Private Keys) for a specific U2000 networking mode in
the administrator guide.
Procedure
Step 1 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).
The Target Server Setting window is displayed.
Step 2 Set Module Type to Trace Server NBI and click Add. The Target Server Settings dialog
box is displayed.
Step 3 In the Target Server Settings dialog box, set Server IP, User Name, Password, Server
Directory, Source Directory, and File Compression Type parameters.
Figure 3.1 is the GUI for Target Server Settings
Figure 3.1 GUI for Target Server Settings
----End

Copyright © Huawei
4.6 Optional: Setting the Northbound Push FTP Server

(ATAE Cluster and Virtual Cluster, Standalone)
Prerequisites
 The Trace Server software has been installed.
 The PC communicates with the Trace Server properly.
 You have logged in to the master Trace Server as user ossuser using PuTTY.
 To set the transmission mode for the public and private key authentication to SFTP,
follow the instructions provided in 5.3Setting the SFTP Public and Private Key
Authentication for the Northbound Push FTP Server.
Context
You can set information about multiple northbound FTP servers.
Procedure
Step 1 Use PuTTY to log in to the master Trace Server in SSH mode as user ossuser.
Step 2 Run the following commands to run the set_xftp_config.sh script:
~> cd /opt/oss/server/rancn/bin
~> sh set_xftp_config.sh
1. When the following information is displayed, type Y to configure XFTP information, or
type N to exit the configuration.
Are you sure you want to set XFTP push config[Y: enter, N:quit]
2. Type Y to configure XFTP information.

When the following information is displayed, type the IP address of the northbound FTP
server.
Please enter the IP address of FTP server:
If type the IP address of the northbound FTP server to exist in the configuration file, the
system display the following information:
Do you want to modify or delete the exist info[1: modify, 2: delete, 3: cancel]
 Type 1 to modify the northbound FTP server information of this IP address, Type 2 to delete the
northbound FTP server information of this IP address, Type 3 to cancel.
3. When the following information is displayed, type the local path to which the result files
need to be pushed, for example, /export/home/omc/var/fileint/TSNBI.
Please enter the directory of local:
4. When the following information is displayed, type 1 to set the automatic upload of trace
result files.
Please enter the push status[0: disable, 1: enable]:

Copyright © Huawei
5. Set the connection mode between the northbound FTP server and the Trace Server as
prompted.
Please enter the FTP type [0: FTP, 1:SFTP, default: 1]:
6. Type the command port number of the northbound FTP server as prompted.
Please enter the port of FTP server [default: 22(sftp)]:
If the SFTP protocol is used, the default value is 22. If the FTP protocol is used, the default value is 21.
7. Type the user name of the northbound FTP server as prompted.
Please enter the username of FTP server:
 Ensure that users can log in to the northbound FTP server using the specified protocol and
port.
 If public and private key authentication is used, the user name must be the same as that for
logging in to the NMS mentioned in section 5.3Setting the SFTP Public and Private Key
Authentication for the Northbound Push FTP Server.
8. If you set the FTP connection mode to SFTP in Step 2.5, based on the system output, set
whether the public key authentication is used. Y indicates that public key authentication
is used, and N indicates that it is not used. If you do not set the FTP connection mode to
SFTP, go to Step 2.10. For details about how to set the public and private key
authentication, see 5.3Setting the SFTP Public and Private Key Authentication for the
Northbound Push FTP Server.
Use the Public and Private Keys or not [Yy/Nn]?
9. If you select Y to use the public key authentication, based on system output, set whether
the password authentication is used at the same time. If you do not select Y, go to Step
2.10.
Set the password or not? [Yy/Nn]
Select Y to use the password authentication and perform the following steps. Otherwise,
go to Step 2.11.
10. Type the password of the user for the northbound FTP server as prompted.
Please enter the password of FTP user:
11. Set the path to which trace result files are uploaded on the northbound FTP server as
prompted, for example, /TSNBI.
Please enter the directory of FTP server:
Ensure that the specified user has the read and write permission on the path. And special
characters :& * \ " ' < > ? can not appear.
12. When the following information is displayed, you need to determine whether to add
another northbound FTP server.
Are you sure you want to set XFTP push config[Y: enter, N:quit]

Copyright © Huawei
If you type Y, the preceding steps are performed again to add another northbound FTP
server. If you type N, the northbound FTP server configuration exits.
Step 3 Select whether to restart the TSXFTPService service as prompted.
Do you want to restart all TSXFTPService?[Y: enter, N:quit]
 If you type Y. the system displays the following information, TSXFTPService service
has been restarted successfully.
restart TSXFTPServices, please wait
restart TSXFTPServices successfully.
 If you type N, the northbound FTP server configuration exits. If you need to restart the
TSXFTPService service manually, perform the following steps.
In order to restart the services more quickly, you are advised to restart the Trace Server
services by Step 4.
Step 4 Run the following commands to restart the Trace Server services:
~> stop_svc
If the command output contains Finished stopping the service., Trace Server services have
been stopped successfully.
~> start_svc
If the command output contains Finished starting the system., the Trace Server service has
been started successfully.
Step 5 Run the following commands to verify that the Trace Server services are restarted
successfully:
~> svc_adm -cmd status -sysagent all | grep TSCollector | grep "not running"
When there is no information displayed, the Trace Server services are restarted successfully.
----End

Copyright © Huawei
U2000 Troubleshooting for the Throughput Stat Data
Trace Server UMTS Throughput Stat Northbound File Northbound Result File InterfaceTroubleshooting for the
Interface Developer Guide Throughput Stat Data Northbound Result File Interface
5 Troubleshooting for the Throughput Stat

Data Northbound Result File Interface
About This Chapter

The NMS is interconnected with the Trace Server through the throughput stat data northbound
result file interface. If problems occur when getting throughput stat data northbound of NEs
on the network, you can solve problems using the methods described in this section.
5.1 Troubleshooting and Information Collection
If faults occur when the NMS attempts to obtain throughput stat data northbound results of
NEs through the throughput stat data northbound result file interface, you can handle the
faults by referring to common troubleshooting methods. If uncommon faults occur, you need
to collect information about the faults and contact Huawei technical support engineers.
5.2 Handle the Problem That No Throughput Stat Data Northbound Result File Is Generated
Either of the following causes may lead to the problem that no throughput stat data
northbound result file is generated: NEs are disconnected, or free disk space of the Trace
Server is insufficient. This section describes how to handle this problem in either of the two
situations.
5.3 Setting the SFTP Public and Private Key Authentication for the Northbound Push FTP
Server
When the trace server actively uploads files to the NMS over the northbound interface, the
trace server functions as an FTP client and the NMS functions as an FTP server. The plaintext
FTP mode is used by default. To ensure data security during file transmission, you can set the
SFTP encryption mode.
5.4 How Do I Check the Problem that CHR Data Is Unreported to the Trace Server
5.5 How Do I Set the DST?
DST is optional, depending on whether the NE is in daylight saving time (DST) mode. The
DST identifier is disabled by default.

Copyright © Huawei
5.1 Troubleshooting and Information Collection

If faults occur when the NMS attempts to obtain throughput stat data northbound results of
NEs through the throughput stat data northbound result file interface, you can handle the
faults by referring to common troubleshooting methods. If uncommon faults occur, you need
to collect information about the faults and contact Huawei technical support engineers.
Common Troubleshooting
Table 1.1 lists methods for handling common faults that may occur when the NMS collects
throughput stat data northbound of NEs.
Table 1.1 Common troubleshooting

Common Fault Troubleshooting Method
No throughput stat data northbound result See 5.2Handle the Problem That No
file is generated. Throughput Stat Data Northbound Result
File Is Generated.
Information Collection
If uncommon faults occur when the NMS attempts to obtain the throughput stat data
northbound of the NEs, you need to collect related information to locate the faults. For details
about how to collect fault information, see Table 1.1.
Table 1.1 Information collection

Related 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 Trace
Server, U2000, NE mediations, and NEs.
IP information Obtain IP addresses of the Trace Server and
the U2000 server.
Log information Obtain log file from the Trace Server boards'
/opt/oss/server/var/logs/iMAP.tscollector
XXXX_agent.trace, and
/export/home/omc/var/logs/TS_CBB/XX/
XX/CBB.log paths.
NOTE
 The first two digits XX together of the
tscollectorXXXX indicate the server number
and the last two digits XX together indicate
the number of the service on the server.
 The first two digits XX together of the
/export/home/omc/var/logs/TS_CBB/XX/X
X indicate the server number and the last two
digits XX together indicate the number of the

Copyright © Huawei
Related Information Description

service on the server.
5.2 Handle the Problem That No Throughput Stat Data

Northbound Result File Is Generated
Either of the following causes may lead to the problem that no throughput stat data
northbound result file is generated: NEs are disconnected, or free disk space of the Trace
Server is insufficient. This section describes how to handle this problem in either of the two
situations.
Problem Description
No throughput stat data northbound result file is generated in the path, and the NMS cannot
collect throughput stat data northbound results of NEs.
Problem Analysis
Either of the following causes can result in the problem:
 NEs are disconnected.
 Free disk space on the Trace Server is insufficient.
Analysis of Disconnected NEs

1. Choose Topology > Main Topology (traditional style); alternatively, double-click Topo
View in Application Center and choose Topology > Main Topology (application style)
on the U2000 client, right-click the disconnected NE, and then choose Enable Ne
Connection from the shortcut menu.
2. Verify that the network connection is normal.
3. Debug the NE mediation.If you need to reinstall the NE mediation, see Commissioning
Guide of the corresponding U2000 networking mode.
Analysis of the Insufficient Free Disk Space of the Trace Server

Clear the disk space of the Trace Server.
You must check whether files can be deleted when clearing the disk space. If you delete the
files by mistake, the system may run improperly.
Solution
Contact Huawei technical support engineers.

Copyright © Huawei
5.3 Setting the SFTP Public and Private Key

Authentication for the Northbound Push FTP Server
When the trace server actively uploads files to the NMS over the northbound interface, the
trace server functions as an FTP client and the NMS functions as an FTP server. The plaintext
FTP mode is used by default. To ensure data security during file transmission, you can set the
SFTP encryption mode.
Prerequisites
 Use Putty to log in to the trace server in SSH mode as user ossuser. For the Trace Server
independently deployed in an ATAE cluster system, log in to all the boards.
 You have logged in to the NMS server as user UserA.
UserA is the NMS server user. Replace it as required.
Context
 To set up an SFTP connection using public or private key authentication, save the trace
server's public key file in the authorized_keys file of the related NMS server user. The
system performs authentication using the trace server's private key and the trace server's
public key stored on the NMS server. After the authentication is successful, the SFTP
connection is set up successfully. It is not required to provide the NMS login password.
 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.
 When the XFTP service uploads files in FTP mode, the Linux or Unix operating system
of the northbound server should use the vsftpd software whose version is 2.0.5 or later.
The northbound server with Windows operating system is not supported.
Procedure
Step 1 Public and private key files are generated on the trace server.
If you need to... Then...
Generate encrypted Only perform Step 1.1 to Step 1.4.

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

encrypted public and
private key files.
1. Run the following command on the trace server to check whether the .ssh directory
exists in the home directory.
~> cd /export/home/omc/.ssh/
− If No such file or directory is displayed, the .ssh directory is unavailable in the
home directory. Perform Step 1.2 after running the following command:
~> mkdir -p /export/home/omc/.ssh/
~> cd /export/home/omc/.ssh/

Copyright © Huawei
− 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 modify the rights of the omc directory and the .ssh
directory.
~> chmod 755 /export/home/omc/
~> chmod 755 /export/home/omc/.ssh/
3. Run the following command to check whether the id_rsa_pwd.pub file exists.
~> ls id_rsa_pwd.pub
− If the system displays id_rsa_pwd.pub: No such file or directory, perform Step
1.4 to create a public key file.
− If the system displays id_rsa_pwd.pub, perform Step 2.
4. Run the following command to create encrypted public and private key files.
~> ssh-keygen -t rsa
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:
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.
5. Run the following command on the trace server to check whether the .ssh directory
exists in the home directory.
~> cd /export/ossuser/.ssh/
home directory. After running the following command, perform Step 1.6.
~> mkdir -p /export/ossuser/.ssh/
− If no command output is displayed, the .ssh directory is available in the home
6. Run the following command to modify the rights of the ossuser directory and the .ssh
directory.
~> chmod 755 /export/ossuser/
~> chmod 755 /export/ossuser/.ssh/
7. Run the following command to check whether the id_rsa file exists.
~> ls id_rsa
− If the system displays id_rsa: No such file or directory, perform Step 1.8 to create
public and private key files.
− If the system displays id_rsa, perform Step 2.

Copyright © Huawei
8. Run the following command to create non-encrypted public and private key files.
~> ssh-keygen -t rsa -b 1024 -f id_rsa -N ""
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.
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.
home directory. After running the mkdir -p ${HOME}/.ssh/ command, perform
Step 2.2.
− If no command result is displayed, the .ssh directory is available in the home
The ${HOME} parameter indicates the home directory of user UserA.

2. Run the following command to modify the rights of the ${HOME} directory and the .ssh
directory.
chmod 755 ${HOME}/
chmod 755 ${HOME}/.ssh/
3. Run the ls authorized_keys command to check whether the authorized_keys file exists.
− 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.4.
− If the system displays authorized_keys, proceed to Step 2.4.
4. Run the following command to modify the right of the authorized_keys file.
chmod 644 ${HOME}/.ssh/authorized_keys
5. Copy the content of the id_rsa.pub or id_rsa_pwd.pub file on the trace server to the
authorized_keys file on the NMS server.
 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 trace server server.
 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 trace 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.

Copyright © Huawei
 The content to be written into the authorized_keys file cannot contain any line feed. If
any line feed exists, delete it.
 If the authorized_keys file contains any other data, perform a line feed operation. Then,
write the content.
6. 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 1.1 lists the parameters to be configured.
Table 1.1 Parameters to be configured for the SFTP

Parameter Value
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys
PasswordAuthenticatio yes/no. This parameter specifies whether the password
n authentication is used when the authentication of the public key
and private key fails. You are advised to set this parameter to yes.
 yes: password authentication is used.
 no: password authentication is not used.
7. Perform the following operations on the NMS server to check the SFTP service status.

Copyright © Huawei
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
H has /usr/local/sbin/sshd
been root 21923 27748 0 11:11:31 ?
installed 0:02 /usr/local/sbin/sshd -R
Run the  If the command output contains /usr/local/sbin/sshd,
pkginfo the SFTP service is running. Run the following
OpenSS command to restart the SFTP service:
H
comman # /etc/init.d/opensshd restart
d, and  If no command output is displayed, the SFTP service
the has not started. Run the following command to start
followin the SFTP service:
g # /etc/init.d/opensshd start
comman
d output
is
displaye
d:
Securit
y
OpenSSH
OpenSSH
Portabl
e for
Solaris

Copyright © Huawei
If... Then...
No # svcs -a | grep ssh

OpenSS online 17:27:13 svc:/network/ssh:defaul
H has
been  If the command output contains online, the SFTP
installed service is running. Run the following command to
restart the SFTP service:
Run the
pkginfo # svcadm restart svc:/network/ssh:default
OpenSS  If the command output contains disabled, the SFTP
H service has not started. Run the following command
comman to start the SFTP service:
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 # service sshd status

SUSE Linux Checking for service sshd
running
 If the command result contains running, the SFTP
service is running. Run the following command to
restart the SFTP service:
# service sshd restart
 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 the public and private key authentication with a password is used, run the following
commands on the Trace Server to query the password code for the public and private key and
then perform Step 4. If the public and private key authentication without a password is used,
do not run the following commands but go to Step 4.
For the Trace Server independently deployed on an ATAE cluster, run the following
commands:

Copyright © Huawei
~> ssl_adm -cmd encryptpassword Changeme_123

The following message is displayed as the text after encryption:
b273290137C725168F52F3D7E1EA8670
Password Changeme_123 must be the same as that entered in Step 1.4.
Step 4 Run the following commands on the Trace Server to change the XFTP configuration file.
commands:
~> cd /opt/oss/server/etc/TSXFTPService
~> vi xftpconfig.xml
Table 1.1 Parameter description

Parameter Description
PrivateKeyFile Set this parameter to the absolute path where the public
key file generated in Step 1.8 is saved, for example,
/export/ossuser/.ssh/id_rsa.
IsSupportEncrpt If the public and private key authentication with a
password is used, the value is 1. If the public and private
key authentication without a password is used, the value
is 0.
PrivateExKeyFile Set this parameter to the absolute path where the public
key file generated in Step 1.4 is saved, for example,
/export/home/omc/.ssh/id_rsa_pwd.
EncrptKey Enter the queried encryption password, for example,
b273290137C725168F52F3D7E1EA8670.
For example:
<commconfig>
……
<PrivateKeyFile>/export/ossuser/.ssh/id_rsa</PrivateKeyFile>
<IsSupportEncrpt>0</IsSupportEncrpt>
<PrivateExKeyFile>/export/home/omc/.ssh/id_rsa_pwd</PrivateExKeyFile>
<EncrptKey></EncrptKey>
……
</commconfig>
If the configuration file xftpconfig.xml does not contain the preceding configuration items, add them
manually, as described in the example.
Step 5 Run the following commands to restart the XFTP service on the trace server.
commands to restart the TSXFtpService service:
# . /opt/oss/server/svc_profile.sh

Copyright © Huawei
# svc_adm -cmd status | grep TSXFTPService

If the following information is displayed, the TSXFtpService service name is
TSXFTPServiceXY01.
TSXFTPServiceXY01 [running ]
# svc_adm -cmd restartsvc TSXFTPServiceXY01

If the following information is displayed, TSXFTPServiceXY01 service has been restarted
successfully.
TSXFTPServiceXY01.....................running
svc_adm : info : START finished.
The process whose name contains XY01 is a multi-instance process, where XY01 indicates the process
number. XY varies from the server where the process is deployed.
----End
5.4 How Do I Check the Problem that CHR Data Is

Unreported to the Trace Server
Symptom
CHR data is unreported to the Trace Server.
Possible Causes
CHR data reporting is disabled.
Procedure
Step 1 Log in to the U2000 client
Step 2 Navigate to the MML Command window using the following methods:
 Choose Maintenance > MML Command from the main menu (traditional style);
alternatively, double-click Trace and Maintenance in Application Center and choose
Maintenance > MML Command from the main menu (application style).
 Navigate to the MML Command window using the main topology for an NE that
supports the device maintenance. In this method, only the MML commands supported by
the NE are displayed.
Choose Topology > Main Topology. The Main Topology window is displayed. Choose
Multimode Base Station View, Physical Root, or Electronic View from the Current
View drop-down list box. In the topology navigation tree or topology view, right-click an
NE and choose Device Maintenance from the shortcut menu, click MML Command
tab in the Device Maintenance window.
Step 3 Select one or multiple NEs for which MML commands need to be executed.
Step 4 Click to switch to the command mode.

Copyright © Huawei
Step 5 Run the following commands to check the whether data reporting has been enabled.
Table 1.1 Commands for checking the CHR reporting status of UMTS NEs
Command Expected Execution Result
LST UEVENTCHRSWITCH Information similar to the following is

displayed, indicating that the value of Event
CHR Process Switch is ON.
List Event CHR Process Switch
----------------------------- Event CHR
Process Switch = ON
LST URNCCHRSCOPE Information similar to the following is

displayed, indicating that the value of CHR
Scope Control Switch is ON.
The result is as follows: List RNC CHR
Switch Scope -------------------------
CHR Scope Control Switch = ON
LST UMMRNCCHRSCOPE: Information similar to the following is

AppType=EMS; displayed, indicating that the value of CHR
Scope Control Switch is ON or
DEPEND_CELL_SWITCH.
The result is as follows: List
Application Type-Oriented RNC CHR
Switch Scope
---------------------------------------
------------ Application Type
= EMS CHR Scope Control Switch = ON
The following commands are available for R015C00SPC580 and later NEs and unavailable for NEs
whose versions are earlier than R015C00SPC580.
 LST URNCCHRSCOPE
 LST UMMRNCCHRSCOPE: AppType=EMS;
Step 6 Set required parameters by following the instructions provided in the MML command help if
displayed information does not meet expectations.
----End
5.5 How Do I Set the DST?

DST is optional, depending on whether the NE is in daylight saving time (DST) mode. The
DST identifier is disabled by default.

Copyright © Huawei
Prerequisites
 You have obtained the IP addresses of the master Trace Server (Trace Server
independently deployed) or the U2000 master server (Trace Server co-deployed with the
U2000 in the ATAE cluster system).
 You have obtained the password of user ossuser.
For ATAE platform, you need to obtain the password of user OSMU Web.
For Virtual platform, you need to obtain the password of user admin.
 You have configured the Trust Relationship Between the Trace Server and the U2000
Server.
Context
The following command output is for reference only.
Procedure
Step 2 Run the following commands to modify the configuration file.
 Run the following commands to disable DST.
~> sed -i "/<UsingDST/s/<UsingDST value=\".*\"/<UsingDST
value=\"false\"/g" /opt/oss/server/etc/TSCollector/GUDataHandleCfg.xml
 Run the following commands to enable DST.
~> sed -i "/<UsingDST/s/<UsingDST value=\".*\"/<UsingDST value=\"true\"/g"
/opt/oss/server/etc/TSCollector/GUDataHandleCfg.xml
Step 3 Run the following commands to confirm that the change was successful.
~> grep UsingDST /opt/oss/server/etc/TSCollector/GUDataHandleCfg.xml
 When information similar to the following is displayed, DST is enabled.
<UsingDST value="true"/>
 When information similar to the following is displayed, DST is disabled.

<UsingDST value="false"/>
Step 4 Run the following command to synchronize the configuration file to other server:
~> /opt/oss/server/rancn/bin/copy_file_to_all_board.sh
/opt/oss/server/etc/TSCollector/GUDataHandleCfg.xml
Step 5 Stop Trace Server services.
 For ATAE platform, perform the following operations.
c. Type the following website in the Address bar of the browser on the PC and press
Enter. Then, log in to the OSMU as an OSMU web user.
https://<public IP address of the OSMU server>:30088/osmu or https://private IP
address of the OSMU server>:30084/osmu
d. In the navigation tree, choose Service System > Service Management > Board
Services.

Copyright © Huawei
e. On the Board Services tab page in the right pane, confirm that the Trace Server
boards are in the Normal state.
f. Select the check box of the system whose Subsystem contains TS, and click Stop
to stop services.
g. In the displayed confirmation dialog box, click Yes.
h. In the displayed dialog box, click OK.
 For Virtual platform, perform the following operations.
i. Open the browser and type https://Service IP address of the vOSMU:31945 in the
address box. Then, log in to the vOSMU as an admin user.
j. Choose Application > Service Management > Start and Stop Services from the
vOSMU main menu. The Start and Stop Services page is displayed.
k. Click following the Trace Server, check and confirm that the Trace Server
service nodes are in the Running state.
If the service nodes are in other state excluding Running and Stopped, contact
Huawei technical support.
l. Click following Trace Server nodes to stop the Trace Server services.
Step 6 Start Trace Server services.
 For ATAE platform, perform the following operations.
m. In the navigation tree, choose Service System > Service Management > Board
Services.
n. On the Board Services tab page in the right pane, confirm that the Trace Server
boards are in the Normal state.
o. Select the check box of the system whose Subsystem contains TS, and click Start.
p. In the displayed confirmation dialog box, click Yes.
q. In the displayed dialog box, click OK.
 For Virtual platform, perform the following operations.
r. Choose Application > Service Management > Start and Stop Services from the
vOSMU main menu. The Start and Stop Services page is displayed.
s. Click following the Trace Server, whose Trace Server nodes detailed
information is to be viewed.
가 If any board is in the Fault state, contact Huawei technical support.
나 If none of the boards is in the Fault state, go to Step 6.c.
t. Check and confirm that the Trace Server service nodes are in the Stopped state.
u. Click Start and Stop Services on the left navigation tree, back to Start and Stop
Services page.
v. Click following Trace Server to start the Trace Server services.

w. In the displayed Warning dialog box, click OK.
x. In the displayed Prompt dialog box, click OK.
You can click Task Information List in the Prompt dialog box or choose System
> Task Manager > Task Information List from the main menu to view the
progress and execution result of the task.
다 When Task Status is Execution Succeeded, Trace Server services have been
started.

Copyright © Huawei
라 When Task Status is Execution Failed, contact Huawei technical support.

----End

Copyright © Huawei
U2000
Interface Developer Guide AppendixAppendix
6 Appendix
About This Chapter

6.1 Supported NE types and versions
6.2 UMTS Event List
6.1 Supported NE types and versions

Table 1.1 lists types and versions of the Supported NE required for the throughput stat data
northbound result file.
Table 1.1 Related NE types and versions

NE Type NE Version Remarks
BSC6900 BSC6900 GU V900R020C10 -

BSC6900 UMTS V900R020C10
BSC6900 GU V900R020C00
BSC6900 GU V900R019C10
BSC6900 GU V900R019C00
BSC6900 GU V900R018C10
BSC6900 GU V900R018C00
BSC6910 BSC6910 GU V100R020C10 -
BSC6910 GU V100R020C00

Copyright © Huawei
U2000
Interface Developer Guide AppendixAppendix
NE Type NE Version Remarks

BSC6910 GU V100R019C10
BSC6910 GU V100R019C00
BSC6910 GU V100R018C10
BSC6910 GU V100R018C00
6.2 UMTS Event List

Table 1.2 describes the event list supported by the UMTS throughput stat data files.
Table 1.2 UMTS throughput stat data event list

Event ID Event Name Initial NE Version
0x1101 PS Throughput Stat SRAN11.0

Copyright © Huawei

U2000 Trace Server UMTS Throughput Stat Northbound File Interface Developer Guide (OFFE00046978 - PMD8906ZH A)

Încărcat de

Informații document

Titlu original

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 Trace Server UMTS Throughput Stat Northbound File Interface Developer Guide (OFFE00046978 - PMD8906ZH A)

Încărcat de

Drepturi de autor:

Formate disponibile

U2000

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential i

About This Document

Product Name Product Version

Issue 01 (2018-02-05) Huawei Proprietary and Confidential ii

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 01 (2018-02-05) Huawei Proprietary and Confidential iii

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Times New Roman Normal paragraphs are in Times New Roman.

Boldface The keywords of a command line are in boldface.

Issue 01 (2018-02-05) Huawei Proprietary and Confidential iv

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

Issue 01 (2018-02-05) Huawei Proprietary and Confidential v

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

2 Overview of Result Files..............................................................................................................4

3 Managing Northbound Users in RAN Sharing Scenarios..................................................12

5.1 Troubleshooting and Information Collection...............................................................................................................41

Issue 01 (2018-02-05) Huawei Proprietary and Confidential vii

1 Overview of the Result File Interface

About This Chapter

1.1 Definition of the Northbound Interface

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 1

Figure 1.1 Northbound interface

1.2 Definition of the Northbound Trace Result File

1.3 Technical Specifications for the Throughput Stat Data

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 2

Maximum period during which throughput 72

Maximum size of a throughput stat data 720

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 3

2 Overview of Result Files

About This Chapter

To obtain result samples, contact Huawei technical support engineers.

2.1 Types of Throughput Stat Data Northbound Result Files

2.1 Types of Throughput Stat Data Northbound Result

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 4

2.2 Save Path of Throughput Stat Data Northbound Result

2.3 Naming Conventions of Throughput Stat Data

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 5

naming conventions for a UMTS_PCHR result file are

Table 1.2 Parameter of naming conventions

NEFDN or neName NE identifiers include NEFDN and neName. You can be

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 6

2.4 Generation Periods of Throughput Stat Data

2.5 Formats of Throughput Stat Data Northbound Result

Format of a UMTS Throughput Stat Data Northbound Result File Header

Data Version N/A Version information

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 7

Field Data Type and Length Description

>Sub Version UINT8 Sub version

Format of a UMTS Throughput Stat Data Northbound Event Header

Event ID UINT16 Event identifier SRAN11.0

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 8

Data Type and

Formats of UMTS Throughput Statistical Data Event Content

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 9

Data Type and

PS Traffic Statistic PS traffic statistic

Issue 01 (2018-02-05) Huawei Proprietary and Confidential 10