Sie sind auf Seite 1von 79
U2000 V200R015C10 Northbound Performance File Interface Developer Guide (NE- Based) Issue Draft A Date

U2000

V200R015C10

Northbound Performance File Interface Developer Guide (NE- Based)

Issue

Draft A

Date

2015-01-15

HUAWEI TECHNOLOGIES CO., LTD.

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

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

Email:

support@huawei.com

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

About This Document

About This Document

Scope

This document provides information about the U2000 northbound performance file interface. It also provides guidance for connecting the network management system (NMS).

This document only describes how to use and configure general functions and does not describe user-defined functions. If you want to know how to use and configure user-defined functions, apply for related function documents from Huawei.

Product Versions

The following table lists the product version related to this document.

Product Name

Version

U2000

V200R015C10

Intended Audience

This document is intended for:

Network management engineers

Change History

Draft A (2015-01-15)

This is a draft for V200R015C10. Compared with issue 01 (2014-04-15) of V200R014C00, the change is:

Added the introduction of export OSS performance items.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

About This Document

Organization

1 Overview of Northbound Performance File Interface

This chapter defines the northbound interface and the northbound performance file interface provided by the U2000.

2 Interconnection Commissioning of Northbound Performance File Interface

This chapter describes the process for interconnecting the NMS with the U2000 northbound performance file interface.

3 Introduction to Performance Result Export Files

This chapter describes the performance result files that are exported by NE and the parameters of performance result export services.

4 Troubleshooting Northbound Performance File Interface

The NMS interconnects with the U2000 through the northbound performance file interface. If a fault occurs when the NMS attempts to obtain performance data, rectify the fault by referring to the relevant troubleshooting suggestions given in this chapter.

5 Appendix

This chapter provides reference information about the northbound performance file interface.

Conventions

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol

Description

Indicates an imminently hazardous situation which, if not avoided, will result in death or serious

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

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

Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate

Indicates a potentially hazardous situation which, if not avoided, may result in minor or moderate injury.

Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data

Indicates a potentially hazardous situation which, if not avoided, could result in equipment damage, data loss, performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to personal injury.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

About This Document

Symbol

Description

Calls attention to important information, best practices and tips.

Calls attention to important information, best practices and tips.

NOTE is used to address information not related to personal injury, equipment damage, and environment deterioration.

General Conventions

The general conventions that may be found in this document are defined as follows.

Convention

Description

Times New Roman

Normal paragraphs are in Times New Roman.

Boldface

Names of files, directories, folders, and users are in boldface. For example, log in as user root.

Italic

Book titles are in italics.

Courier New

Examples of information displayed on the screen are in Courier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.

Convention

Description

Boldface

 

The keywords of a command line are in boldface.

Italic

 

Command arguments are in italics.

[

]

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

{

x | y |

}

Optional items are grouped in braces and separated by vertical bars. One item is selected.

[

x | y |

]

Optional items are grouped in brackets and separated by vertical bars. One item is selected or no item is selected.

{

x | y |

} *

Optional items are grouped in braces and separated by vertical bars. A minimum of one item or a maximum of all items can be selected.

[

x | y |

] *

Optional items are grouped in brackets and separated by vertical bars. Several items or no item can be selected.

GUI Conventions

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

About This Document

The GUI conventions that may be found in this document are defined as follows.

Convention

Description

Boldface

Buttons, menus, parameters, tabs, window, and dialog titles are in boldface. For example, click OK.

>

Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

Format

Description

Key

Press the key. For example, press Enter and press Tab.

Key 1+Key 2

Press the keys concurrently. For example, pressing Ctrl+Alt +A means the three keys should be pressed concurrently.

Key 1, Key 2

Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.

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.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

Contents

Contents

About This Document

ii

1

Overview of Northbound Performance File Interface

1

1.1 Definition of Northbound Interface

2

1.2 Definition of the Northbound Performance File Interface

2

1.3 Using the Northbound Performance File Interface

3

1.4 Technical Specifications of Northbound Performance File Interface

3

2

Interconnection Commissioning of Northbound Performance File Interface

5

2.1 Checking License (Performance File Interface)

7

2.2 Negotiating Interconnection Parameters of Performance File Interface

7

2.3 Modifying Parameters of Performance Export Services

14

2.4 Starting Performance Export

17

2.5 (Optional) Configuring the U2000 for Actively Uploading Files over the Northbound Interface

20

2.5.1 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Public and Private Keys)

20

2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication)

32

2.6 (Optional)Stopping Performance Export

39

2.7 Verifying Interconnection

42

3 Introduction to Performance Result Export Files

44

3.1

Description of Performance Result Export Files

45

3.1.1 Examples of Performance Result Export Files

45

3.1.2 Path of Performance Result Export Files

45

3.1.3 Default Naming Convention of Performance Result Export Files

46

3.1.4 User-defined Naming Convention of Performance Result Export Files

50

3.1.5 Format of Performance Result Export Files

52

3.1.6 Storage Specification of Performance Result Export Files

55

3.2

Configuration File of Performance Result Export Services

55

4 Troubleshooting Northbound Performance File Interface

58

4.1 Common Troubleshooting and Information Collection

59

4.2 Troubleshooting Performance File Export Failure

60

4.3 How to Set Northbound Interface Compatibility

61

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

Contents

4.4 How to Set Parameters in a Northbound Configuration File

62

5 Appendix

64

5.1 NEs Supported by Performance File Export

65

5.2 Measurement Attributes of an NE

69

5.3 Method of Obtaining Performance Counter Files of NEs

70

5.4 Method of Transferring Data Using PSFTP

70

5.5 Checking the Sybase Database Server Name

70

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

1 Overview of Northbound Performance File Interface

1 Overview of Northbound Performance File Interface

About This Chapter

This chapter defines the northbound interface and the northbound performance file interface provided by the U2000.

1.1 Definition of Northbound Interface

The northbound interface links the element management system (EMS) and the NMS.

1.2 Definition of the Northbound Performance File Interface

The U2000 northbound performance file interface is a type of northbound interface. The NMS obtains performance data (including the OSS performance measurement data) of NEs through the northbound performance file interface.

1.3 Using the Northbound Performance File Interface

This section describes how to use the northbound performance file interface when the U2000 system adopts different networking modes.

1.4 Technical Specifications of Northbound Performance File Interface

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

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

1 Overview of Northbound Performance File Interface

1.1 Definition of Northbound Interface

The northbound interface links the element management system (EMS) and the NMS.

The NMS obtains information about the network elements (NEs) managed by the EMS and delivers operation commands through the northbound interface. The NE information includes the alarm, configuration, performance, and inventory data. Figure 1-1 shows the position of the northbound interface in the network.

Figure 1-1 Position of the northbound interface

network. Figure 1-1 Position of the northbound interface In the communication network, the U2000 provides the

In the communication network, the U2000 provides the alarm, configuration, performance, and inventory data of NEs to the NMS through the northbound interface.

1.2 Definition of the Northbound Performance File

Interface

The U2000 northbound performance file interface is a type of northbound interface. The NMS obtains performance data (including the OSS performance measurement data) of NEs through the northbound performance file interface.

The NMS can use either of the following methods to obtain northbound performance files:

l

PULL: The NMS uses SFTP to obtain files from a specified path of the U2000 server.

l

PUSH: The U2000 automatically uploads files to a specified path of the NMS.

U2000 northbound file transfer supports the following protocols: SSH-based FTP.SFTP uses public-key/private-key encryption to encrypt data in the network. Data communication between two ends can therefore be performed in an encrypted channel.

The U2000 northbound performance file interface uses 3GPP TS 32.435 V7.2.0 specifications. For details about how to view the specifications and version, see fileFormatVersion descriptions in Format of Performance Result Export Files.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

1 Overview of Northbound Performance File Interface

1.3 Using the Northbound Performance File Interface

This section describes how to use the northbound performance file interface when the U2000 system adopts different networking modes.

For details about how to use the northbound performance interface in different networking modes, see Table 1-1.

Table 1-1 Usage of the northbound performance file interface

U2000 System

NMS and U2000 Interconnection Solution

Method for the NMS to Obtain Performance Files

Type

Single-server

Perform interconnection on the U2000 server.

Obtain performance files on the U2000 server.

system

HA System

Perform interconnection on the active U2000 server.

Obtain performance files on the active U2000 server.

 

Remote HA

   

system

OSS performance export files can be obtained on the active U2000 server.

SUN-based SLS

Perform interconnection on the master and slave U2000 servers.

Obtain performance files from each U2000 server where the MediationService service is deployed.

OSS performance export files can be obtained on the master U2000 server.

system

ATAE cluster

Perform interconnection on the master and slave U2000 servers.

Obtain performance files from each U2000 server where the MediationService service is deployed.

OSS performance export files can be obtained on the master U2000 server.

system

ATAE cluster online remote HA system

Perform interconnection on the master and slave servers of the active and standby U2000 sites.

Obtain performance files from each U2000 server where the MediationService service is deployed.

OSS performance export files can be obtained on the master U2000 server.

1.4 Technical Specifications of Northbound Performance

File Interface

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

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

1 Overview of Northbound Performance File Interface

Item

Value

Maximum re-upload attempts that are permitted after automatic file upload fails

3

Interval between re-upload attempts after an automatic file upload attempt fails (unit: minute)

15

Maximum FTP servers supported by automatic file upload

10

Maximum delay in exporting the performance result of a collection task (collection period: 15 minutes) through the northbound performance file interface

10

Maximum delay in exporting the performance result of a collection task (collection period: 30 minutes) through the northbound performance file interface

20

Maximum delay in exporting the performance result of a collection task (collection period: 60 minutes) through the northbound performance file interface

30

Maximum days within which performance export files can be saved on the U2000

7

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

2 Interconnection Commissioning of Northbound Performance File Interface

About This Chapter

This chapter describes the process for interconnecting the NMS with the U2000 northbound performance file interface.

2.1 Checking License (Performance File Interface)

Before interconnecting the U2000 to the NMS, make sure that the NMS is licensed to use the northbound performance file interface.

2.2 Negotiating Interconnection Parameters of Performance File Interface

This section describes the preparations for interconnecting the U2000 with the NMS.

2.3 Modifying Parameters of Performance Export Services

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

2.4 Starting Performance Export

Starting performance export is mandatory. This section describes how to set NE types and measurement periods for performance export. You can start performance export using commands or using the OSMU.

2.5 (Optional) Configuring the U2000 for Actively Uploading Files over the Northbound

Interface The U2000 can actively upload files to the NMS over the northbound interface. You can use either method to configure the U2000 for actively uploading files to the NMS over the northbound interface.

2.6 (Optional)Stopping Performance Export

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

2.7 Verifying Interconnection

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

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

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

2.1 Checking License (Performance File Interface)

Before interconnecting the U2000 to the NMS, make sure that the NMS is licensed to use the northbound performance file interface.

Do as follows to check that the NMS has the required license:

1. Log in to the U2000 client.

2. Choose License > OSS License Management > License Information (traditional style). Alternatively, double-click System Management in Application Center and choose License Management > License Information (application style). The License Information window is displayed.

3. Click the Resource Control Item tab. If Resource contains Performance File Interface, the NMS is authorized to use the performance file interface.

2.2 Negotiating Interconnection Parameters of Performance

File Interface

This section describes the preparations for interconnecting the U2000 with the NMS.

Obtaining Negotiated Interconnection Parameters

The negotiated interconnection parameters are as follows:

l

System parameters.

Solaris operating system: see Table 2-1.

SUSE Linux operating system and Oracle database: see Table 2-2.

SUSE Linux operating system and Sybase database: see Table 2-3.

l

File save parameters. For details, see Table 2-4.

l

NE measurement parameters. For details, see Table 2-5.

l

FTP parameters. For details, see Table 2-6.

Table 2-1 System parameters for Solaris operating system

Parameter

Value

Description

Operating system

Solaris

-

Database type

Sybase

-

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Parameter

Value

Description

Database name

l

The default database server name is DBSVR in the U2000 single-server or HA system.

-

l

The default database server name is DBSVR1 in the SUN SLS and ATAE Cluster system.

Query Sybase database name, refer to 5.5 Checking the Sybase Database Server Name.

Database user

-

Contact the U2000 administrator to obtain the password.

Database password

-

Contact the U2000 administrator to obtain the password.

Installation path of the U2000 server

/opt/oss/server

You are advised to use the default installation path. If the installation path has been changed during the installation, set this parameter to the actual installation path.

Table 2-2 System parameters for SUSE Linux operating system and Oracle database

Parameter

Value

Description

Operating system

SUSE Linux

-

Database type

Oracle

-

Database name

ossdb

-

Database user

itfndb

-

Database password

The default password of itfndb is Changeme_123

To improve system security, change the default database password upon first login and periodically change the password. The password change interval can be customized as required.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Parameter

Value

Description

Installation path of the U2000 server

/opt/oss/server

You are advised to use the default installation path. If the installation path has been changed during the installation, set this parameter to the actual installation path.

Table 2-3 System parameters for SUSE Linux operating system and Sybase dabatase

Parameter

Value

Description

Operating system

SUSE Linux

-

Database type

Sybase

-

Database name

l

The default database server name is DBSVR in the U2000 single-server or HA system.

-

l

The default database server name is DBSVR1 in the SUN SLS and ATAE Cluster system.

Query Sybase database name, refer to 5.5 Checking the Sybase Database Server Name.

Database user

-

Contact the U2000 administrator to obtain the password.

Database password

-

Contact the U2000 administrator to obtain the password.

Installation path of the U2000 server

/opt/oss/server

You are advised to use the default installation path. If the installation path has been changed during the installation, set this parameter to the actual installation path.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Table 2-4 File save parameters

Parameter

Default Value

Value Range

Description

Format of exported files

XML

-

Cannot be modified.

Days during which exported files can be saved

7

1-7

Expired files will be deleted automatically by the

U2000.

For details, see 3.2 Configuration File of Performance Result Export Services.

Delay in regularly deleting expired files (minutes)

30

0-1439

l

The U2000 triggers the timer to delete expired files after N minutes of 00:00:00 every day.

l

Method for converting time on the timer into minutes: If you need to delete expired files at 02:30:00 every day, set this parameter to 150 (2 x 60 + 30 =

150).

l

Regularly deleting expired files consumes system resources. The recommended value range is

30-360.

For details, see 3.2 Configuration File of Performance Result Export Services.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Table 2-5 NE measurement parameters

Parameter

Value Range

Example

Description

NE type name

-

MSCServerNE

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

Measurement period (minute)

15, 30, 60, 1440

60

Set this parameter to the actual measurement period. Use the measurement period of actual NEs to set this parameter.

Table 2-6 FTP parameters

 

FTP

Parameter

Value

Description

The U2000 serves as

FTP user name

ftpuser

Cannot be modified.

Password

The default

To improve system security, change the default database password upon first login and periodically change the password. The password change interval can be customized as required.

an FTP server (PULL).

NOTICE Using SFTP is recommended because of its higher security than FTP.

password:

Changeme_123

FTP port

20, 21

If you use FTP to transmit data, open the ports on the

U2000.

SFTP port

22

If you use SFTP to transmit data, open the port on the

U2000.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

FTP

Parameter

Value

Description

 

Export path

/opt/oss/server/var/

Cannot be modified.

fileint/pmneexport

NOTE In the SUN SLS and ATAE Cluster system, the performance result export files of NEs are saved only in the master server or a slave server that manages these NEs. The performance result export files of NEs managed by a slave server will not aggregate to the master server.

The U2000 serves as an FTP client (PUSH).

FTP user name

Provided by the NMS

For details, see 2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication).

NOTICE Using SFTP is recommended because of its higher security than FTP.

Password

Provided by the NMS

If the northbound FTP server updates the password regularly, modify FTP server settings. For details, see 2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication).

FTP port

20, 21

If you use FTP to transmit data, open the ports on the NMS.

SFTP port

22

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

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

FTP

Parameter

Value

Description

 

Export path

Provided by the NMS

For details, see 2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication).

Negotiating File Transfer Protocols

You need to negotiate between the U2000 and NMS to determine whether PUSH or PULL be used. You also need to negotiate between the U2000 and NMS to determine whether FTP or SFTP be used. You can then prepare for the interconnection according to the negotiated results by referring to Table 2-7.

Table 2-7 Guidance for setting file transfer

Mode

FTP

SFTP

PUSH: the

For details, see Step 7 of 2.5.1 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Public and Private Keys).

For details, see 2.5.1 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Public and Private Keys) or 2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication).

U2000

automatically

uploads files

PULL: the

If you use FTP to transfer files, enable FTP by referring to the section "Configuring the FTP Transmission Policy" described in the corresponding U2000 Administrator Guide.

The U2000 uses SFTP to transfer files by default.

NMS directly

obtains files

 

Obtaining the Performance Counter File of an NE

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

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Checking Performance Measurement

Northbound performance files are exported based on the performance measurement set on the U2000. Perform the following steps to ensure that performance measurement has been set correctly on the U2000:

1. Query measurement attributes of an NE.

Query measurement attributes such as default measurement counters, default measurement period, and report by all counters. For details, see 5.2 Measurement Attributes of an NE.

2. If you do not set performance measurement, northbound performance files can still be exported when the following requirements are met. Determine whether these requirements are met by referring to 5.2 Measurement Attributes of an NE.

a. The specified counters to be measured are included in the default measurement counters.

b. The specified measurement period is the default measurement period of the NE.

c. The default performance measurement is not modified or the NE still reports measurement results of all counters even if the measurement of some counters has been canceled.

3. If any NE type does not meet these requirements, perform the following steps to ensure that performance measurement has been set correctly on the U2000:

a. Log in to the U2000 client.

b. Choose Performance > Measurement Management (traditional style); alternatively, double-click Performance in Application Center and choose Measurement > Measurement Management (application style) . Confirm the measurement counters that are specified by the NMS have been set to performance measurement in the specified measurement period.

performance measurement in the specified measurement period. NOTE The U2000 does not export user-defined counters on

NOTE

The U2000 does not export user-defined counters on the U2000 client.

File Examples

You can obtain the examples of performance result export files of some common NE types from the 07.Northbound File\File Interface\Sample File\Performance File (NE-Based) northbound interface document directory.

Contact Huawei technical support to obtain the examples of performance result export files of specified NE types.

2.3 Modifying Parameters of Performance Export Services

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

Context

You can use either of the following methods to modify parameters of performance export services:

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

l

Modifying parameters of performance export services using commands

l

Modifying parameters of performance export services using the OSMU

Parameters of performance export services are saved in the /opt/oss/server/etc/ MediationService/MedExpParam.xml configuration file. For detailed description of the parameters in the configuration file, see 3.2 Configuration File of Performance Result Export Services.

Procedure

l Modifying parameters of performance export services using commands

parameters of performance export services using commands NOTICE l In an SLS system, you need to

NOTICE

l

In an SLS system, you need to perform the following steps only on the master and slave servers and do not need to perform them on the standby server.

l

In an HA or remote HA system, you need to perform the following steps only on the active server and do not need to perform them on the standby server.

l

In an ATAE cluster online remote HA system, you need to perform the following steps only on the master and slave servers (include active site and standby site) and do not need to perform them on the standby server.

1.

Log in to the U2000 server as user ossuser.

2.

Run the following commands to open the MedExpParam.xml configuration file:

-bash-3.00$ . /opt/oss/server/svc_profile.sh

-bash-3.00$ vi /opt/oss/server/etc/MediationService/MedExpParam.xml

Find the following two lines in the configuration file:

<FileSaveDay Name="Export file saving days" Value="7"/> <DelDelayTime Name="Delete export files time offset from 0:00" Value="30"/>

3.

Modify the MedExpParam.xml configuration file.

Modify the configuration items according to the negotiated parameters. The modified configuration items are as follows:

<FileSaveDay Name="Export file saving days" Value="5"/> <DelDelayTime Name="Delete export files time offset from 0:00" Value="150"/>

4.

Press Esc, and then run the :wq! command to save the modification and exit the vi editor.

5.

On the servers on which MediationService is deployed, run the following command to query the names of the current MediationService:

-bash-3.00$ svc_adm -cmd status | grep MediationService

The following command output is used as an example, the names of the current MediationService are MediationService0101, MediationService0102, and

MediationService0105.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

MediationService0101

[running

]

MediationService0102

[running

]

MediationService0105

[running

]

6. Run the following commands to restart MediationService:

-bash-3.00$ svc_adm -cmd restartsvc MediationService0101

-bash-3.00$ svc_adm -cmd restartsvc MediationService0102

-bash-3.00$ svc_adm -cmd restartsvc MediationService0105

7. Run the following command to check whether the services are running properly:

-bash-3.00$ svc_adm -cmd status | grep MediationService

If the system displays the following information, performance export services are running properly.

MediationService0101

[running

]

MediationService0102

[running

]

MediationService0105

[running

]

l Modifying parameters of performance export services using the OSMU of the master server (include the master server of site).

1. Start the Internet Explorer, type http://IP address of the U2000 server:8090 or https://IP address of the U2000 server:31123 in the Address bar, and then press Enter.

2. Log in to the OSMU as user ossuser.

3. Click NBI Management in the main window of the OSMU.

4. Choose NBI Management > Centralized Management > Northbound Configuration Parameters Settings from the navigation tree in the left pane. The Northbound Configuration Parameters Settings interface is displayed.

5. Select Northbound Performance File Interface (NE-Based) from the Northbound Interface Name drop-down list.

6. Select MedExpParam.xml - Basic from the Configuration file name drop-down list, modify parameters of performance export services according to the negotiated parameters.

For detailed description of the parameters, see 3.2 Configuration File of Performance Result Export Services.

7. Click Save after the modification is complete.

8. Select MedExpParam.xml - Advanced from the Configuration file name drop- down list, modify parameters of performance export services according to the negotiated parameters.

For detailed description of the parameters, see 3.2 Configuration File of Performance Result Export Services.

9. Click Save&Restart after the modification is complete.

You can view the progress of service restart in the Service Restarted Log area. The modified parameters take effect after all relevant services are restarted.

----End

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

2.4 Starting Performance Export

Starting performance export is mandatory. This section describes how to set NE types and measurement periods for performance export. You can start performance export using commands or using the OSMU.

Context

l

You can use either of the following methods to start performance export:

 

Starting performance export using commands

Starting performance export using the OSMU

 

l

Performance export files can be exported over the northbound interface only after you start performance export.

l

The minimum granularity you can set for performance export is NE type. After you set an NE type and measurement period, all measurement results of the NE type in the specified period will be exported over the northbound interface.

l

For the AP Manager, you need to start performance export services only on NEs and you can ignore the following steps performed on the U2000. For details, see the AP Manager VXXXRXXX Northbound Performance File Interface.

 
NOTICE

NOTICE

 

l

In an SLS system, you need to perform the following steps only on the master server and do not need to perform them on the slave or standby server.

l

In an HA or remote HA system, you need to perform the following steps only on the active server and do not need to perform them on the standby server.

l

In an ATAE cluster online remote HA system, you need to perform the following steps only on the master server (include active site and standby site) and do not need to perform them on the slave or standby server.

Procedure

l

Starting performance export using commands

1. Log in to the U2000 server as user ossuser.

2. Start the performance export script.

On a Sun or ATAE(Sybase) platform, the default installation directory of the U2000 server is /opt/oss/server, database server name is DBSVR, and user name is database administrator. The default password is Changeme_123, run the following commands:

-bash-3.00$ . /opt/oss/server/svc_profile.sh

-bash-3.00$ config_med_export.sh

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

NOTECommissioning of Northbound Performance File Interface When the Sybase database is used, the user must be

When the Sybase database is used, the user must be database administrator and the default password is Changeme_123. The default database server name is DBSVR in the U2000 single- server or HA system and the default database server name is DBSVR1 in the Sun-based SLS system and ATAE Cluster system. For details about how to query the name of the Sybase database, see 5.5 Checking the Sybase Database Server Name.

To improve system security, change the default database password upon first login and periodically change the password. The password change interval can be customized as required.

The system displays the following information:

Please input Database dbServer: DBSVR Please input Database userName: database administrator Please input Database password:

Please wait for a second while loading the tool Welcome To Med Export Service Configuration Tool ====================================================== Please select an operation type 1--Current Measurement Display 2--New Measurement Set

3--Exit

====================================================== Please select one operation [default is 3] :

On a HP or ATAE(Oracle) platform, the default installation directory of the U2000 server is /opt/oss/server, database server name is ossdb, and user name is itfndb. The default password is Changeme_123, run the following commands:

ossuser@osssvr-10:~>

ossuser@osssvr-10:~> config_med_export.sh

. /opt/oss/server/svc_profile.sh

NOTICEconfig_med_export.sh . / opt/oss/server/svc_profile.sh The user name of Oracle database is itfndb , and its

The user name of Oracle database is itfndb, and its default password is

Changeme_123.

To improve system security, change the default database password upon first login and periodically change the password. The password change interval can be customized as required.

The system displays the following information:

Please input Database dbServer: ossdb Please input Database userName: itfndb Please input Database password:

Please wait for a second while loading the tool Welcome To Med Export Service Configuration Tool ====================================================== Please select an operation type 1--Current Measurement Display 2--New Measurement Set

3--Exit

====================================================== Please select one operation [default is 3] :

where,

1: To view the preset types of NEs to be measured and their measurement periods.

2: To set a new measurement.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

3: To exit.

3. Set operation types according to the actual requirement.

This section uses setting a new measurement as an example. Type 2.

The system displays the following information:

New Measurement Set ====================================================== 1--Show Available Measurements 2--Active Measurements 3--Deactive Measurements 4--Return to Main menu ====================================================== Please select one operation [default is 4] :

where,

1: To view the measurements that can be set currently.

2: To set a new measurement.

3: To cancel a measurement.

4: To return to the main menu.

4. Set a measurement export.

This section uses setting a new measurement export as an example. Type 2.

The system displays the following information:

Active Measurements ====================================================== Please input NeTypeName [default or 'b' to exit current menu] :

5. Type an NE type name to be set.

For example, if you want to set the NE type of MSCServer, type MSCServerNE.

The system displays the following information:

Please input Period (like '60' means 60 minutes period) [default or 'b' to exit current menu] :

6. Set the measurement period.

You can set only one measurement period at a time. For example, if you want to set the period to 60 minutes, type 60.

The system displays the following information:

You want active MSCServerNE with 60 minutes period, please input 'y' to confirm, 'n' to ignore :

7. Confirm the settings.

After confirming the previous settings, type y.

The system displays the following information:

Please input NeTypeName [default or 'b' to exit current menu] :

8. Perform the following operations according to the actual requirement:

If you need to

Then

Continue the settings

Perform Step 5 to Step 8.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

If you need to

Then

End the settings

Type b to return to the previous step. Type 4 to return to the main menu. Type 3 to exit the performance export script.

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

1. Start the Internet Explorer, type http://IP address of the U2000 server:8090 or https://IP address of the U2000 server:31123 in the Address bar, and then press Enter.

2. Log in to the OSMU as user ossuser.

3. Click NBI Management in the main window of the OSMU.

4. Choose NBI Management > Centralized Management > Northbound Configuration Parameters Settings from the navigation tree in the left pane. The Northbound Configuration Parameters Settings interface is displayed.

5. Select Northbound Performance File Interface (NE-Based) from the Northbound Interface Name drop-down list.

6. Select tbl_MedExportMeas from the Configuration file name drop-down list, select measurement periods for one or more NEs.

7. Click Update Measurements to start performance export.

----End

2.5 (Optional) Configuring the U2000 for Actively Uploading Files over the Northbound Interface

The U2000 can actively upload files to the NMS over the northbound interface. You can use either method to configure the U2000 for actively uploading files to the NMS over the northbound interface.

2.5.1 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Public and Private Keys)

When the U2000 server actively uploads files to the NMS over the northbound interface, the U2000 server functions as an FTP client and the NMS functions as an FTP server. To ensure data security during file transmission, you can set the SFTP encryption mode. If the U2000 server is upgraded to V200R015C00 or a Later Version, please reconfigure the SFTP for actively transferring files over the northbound interface according to this chapter.

Prerequisites

l Use PuTTY to log in to the U2000 server in SSH mode as user ossuser.For an HA system, you have logged in to the active and standby servers.For a remote HA system, you have logged in to the active and standby servers.For an SLS system, you have logged in to all servers. For an advanced telecommunications application environment (ATAE) cluster system, you have logged in to each server in the U2000 cluster. For an HA system, you have logged in to the active and standby servers. For an ATAE cluster system, you have

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

logged in to each server in the U2000. For an HA or remote HA system, you have logged in to the active and standby servers. For an SLS system, you have logged in to each server.

 

l

You have logged in to the NMS server as user UserA.

 

UserA is the NMS server user. Replace it as required.

Context

 

l

To set up an SFTP connection using public or private key authentication, save the U2000 server's public key file in the authorized_keys file of the related NMS server user. The system performs authentication using the U2000 server's private key and the U2000 server's public key stored on the NMS server. After the authentication is successful, the SFTP connection is set up successfully. The U2000 server is not required to provide the NMS login password.

l

The public and private key authentication files can be encrypted or not. For encrypted public and private key authentication files, set the password. If you forget the password, all public and private key authentication files must be generated again, and the new files will replace the existing files.

l

Unless otherwise specified, perform the following operations on each server:

 
NOTE

NOTE

 
 

l

XFTPService0X01 indicates the XFTP service name of the U2000 server. Replace it as required.

l

For a single-server system, the XFTP service name is XFTPService0101.The service is deployed on the active server. The service name is XFTPService0101.The service is deployed on the active and standby servers. The service name is XFTPService0101. For an SLS system, the service is deployed on the master and slave servers. The service name for the master server is XFTPService0101. The service name for the first slave server is XFTPService0201. The service name for the second slave server is XFTPService0301. This method applies to the service names for other servers.For an HA system, the service is deployed on the active server, on which the service name is XFTPService0101. For an SLS system, the service is deployed on the master and slave servers. The service name for the master server is XFTPService0101. The service name for the first slave server is XFTPService0201. The service name for the second slave server is XFTPService0301. This method applies to the service names of other servers. For an HA system, the service is deployed on the active server. The service name is XFTPService0101. For a remote HA system, the service is deployed on the active and standby servers. The service name is XFTPService0101. For an SLS system, the service is deployed on the master and slave servers. The service name for the master server is XFTPService0101. The service name for the first slave server is XFTPService0201. The service name for the second slave server is XFTPService0301. This method applies to other service names of other servers.For the virtual cluster system, the service is deployed on the master and slave servers. The service name for the master server is XFTPService0101. The service name for the first slave server is XFTPService0201. The service name for the second slave server is XFTPService0301. This method applies to the service names for other servers.

 

l

When the XFTP service uploads files in FTP mode:

If the northbound server runs the Linux or Unix operating system, use the vsftpd software whose version is 2.0.5 or later.

If the northbound server runs the Windows operating system, use the ftpserver service delivered with the system.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Commissioning of Northbound Performance File Interface NOTICE l In an SLS system, you need to perform

NOTICE

l

In an SLS system, you need to perform the following steps only on the master and slave servers and do not need to perform them on the standby server.

l

In an HA or remote HA system, you need to perform the following steps only on the active server and do not need to perform them on the standby server.

l

In an ATAE cluster online remote HA system, you need to perform the following steps only on the master and slave servers (include active site and standby site) and do not need to perform them on the standby server.

Procedure

Step 1

Public and private key files are generated on the U2000.

If you need to

Then

Generate encrypted public and private key files.

Only perform Step 1.1 to Step 1.4.

Generate non-encrypted public and private key files.

Only perform Step 1.5 to Step 1.8.

1. Run the following command on the U2000 server to check whether the .ssh directory exists in the home directory.

$

cd /export/home/omc/.ssh/

l

If No such file or directory is displayed, the .ssh directory is unavailable in the home directory. Perform Step 1.3 after running the following command:

$ mkdir -p /export/home/omc/.ssh/

$ cd /export/home/omc/.ssh/

l

If no command result is displayed, the .ssh directory is available in the home directory. Perform Step 1.2.

2. Run the following command to check whether the id_rsa_pwd.pub file exists.

$

ls id_rsa_pwd.pub

l

If the system displays id_rsa_pwd.pub: No such file or directory, perform Step 1.3 to create a public key file.

l

If the system displays id_rsa_pwd.pub, perform Step 2.

3. Run the following command to create encrypted public and private key files.

$ . /opt/oss/server/rancn/bin/ssh-keygen.sh

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

If the system displays the following message, enter 1 to create encrypted public and private key files.

------------------------------------------------------------------

Please select an operation type:

1--Generate PubKey File with Encrypt Key. 2--Generate PubKey File without Encrypt Key.

------------------------------------------------------------------

Please make a choice : 1

If the system displays the following message, enter /export/home/omc/.ssh/id_rsa_pwd.

Generating public/private rsa key pair. Enter file in which to save the key (/export/ossuser/.ssh/id_rsa):

is displayed, the

If the following message is displayed, enter the password twice. When $ encrypted public key file is generated.

Enter passphrase (empty for no passphrase):

Enter same passphrase again:

NOTICE(empty for no passphrase): Enter same passphrase again: l Keep the password for future use. If

l

Keep the password for future use. If the password is lost, all public and private key files must be generated again, and the new files will replace the existing files.

l

The password can contain 8 to 30 characters, including lowercase letters a to z,

uppercase letters A to Z, digits 0 to 9, and special characters ]@%-= password security, please use the following password policies:

}{. To improve

l

The password contains at least one uppercase letter.

l

The password contains at least one lowercase letter.

l

The password contains at least one digit.

l

The password contains at least one special character.

4. Run the following commands to modify permission of the public key file.

$ cd /export/home/omc/.ssh/

$ chmod 600 id_rsa_pwd.pub

5. Run the following command on the U2000 server to check whether the .ssh directory exists in the home directory.

$

cd ${HOME}/.ssh/

l

If No such file or directory is displayed, the .ssh directory is unavailable in the home directory. After running the following command, perform Step 1.7.

$

mkdir -p ${HOME}/.ssh/

l

If no command output is displayed, the .ssh directory is available in the home directory. Perform Step 1.6.

NOTEis available in the home directory. Perform Step 1.6 . The ${HOME} parameter indicates the home

The ${HOME} parameter indicates the home directory of user ossuser.

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

$ ls id_rsa

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

l

If the system displays id_rsa: No such file or directory, perform Step 1.7 to create public and private key files.

l

If the system displays id_rsa, perform Step 2.

7. Run the following command to create non-encrypted public and private key files.

$ . /opt/oss/server/rancn/bin/ssh-keygen.sh

If the system displays the following message, enter 2 to create non-encrypted public and private key files.

------------------------------------------------------------------

Please select an operation type:

1--Generate PubKey File with Encrypt Key. 2--Generate PubKey File without Encrypt Key.

------------------------------------------------------------------

Please make a choice : 2

If the system displays information similar to the following, the non-encrypted public key file has been created successfully:

Generating public/private rsa key pair. Your identification has been saved in id_rsa. Your public key has been saved in id_rsa.pub.

8. Run the following commands to modify permission of the public key file.

$ cd /export/home/omc/.ssh/

$ chmod 600 id_rsa_pwd.pub

Step 2

Enable public key authentication on the NMS.

1. Log in to the NMS server as user UserA. Run the cd ${HOME}/.ssh/ command to check whether the .ssh directory exists in the home directory.

l

If No such file or directory is displayed, the .ssh directory is unavailable in the home directory. After running the mkdir -p ${HOME}/.ssh/ command, perform Step 2.2.

l

If no command result is displayed, the .ssh directory is available in the home directory. Perform Step 2.2.

NOTE

NOTE

The ${HOME} parameter indicates the home directory of user UserA.

2. Run the ls authorized_keys command to check whether the authorized_keys file exists.

l

If the system displays authorized_keys: No such file or directory, run the touch authorized_keys command to create the authorized_keys file. Then, perform Step

2.3.

l

If the system displays authorized_keys, proceed to Step 2.3.

3. Copy the content of the id_rsa.pub or id_rsa_pwd.pub file on the U2000 server to the authorized_keys file on the NMS server.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

NOTICECommissioning of Northbound Performance File Interface l For a non-encrypted public key file, copy the

l

For a non-encrypted public key file, copy the id_rsa.pub file's content.

If the id_rsa.pub file does not exist, copy the ${HOME}/.ssh/authorized_keys file's content on the U2000 server.

l

For an encrypted public key file, copy the id_rsa_pwd.pub file's content.

a.

Run the cat id_rsa.pub or cat id_rsa_pwd.pub command on the U2000 server. The content of the id_rsa.pub or id_rsa_pwd.pub file is displayed.

b.

Run the vi command on the NMS server to write the content of the id_rsa.pub or id_rsa_pwd.pub file into the authorized_keys file.

NOTICEor id_rsa_pwd.pub file into the authorized_keys file. l The content to be written into the authorized_keys

l

The content to be written into the authorized_keys file cannot contain any line feed. If any line feed exists, delete it.

l

If the authorized_keys file contains any other data, perform a line feed operation. Then, write the content.

4. Run the vi command to modify the /etc/ssh/sshd_config file and configure SFTP parameters on the NMS server.

# su - root

Password: Password of user root

# vi /etc/ssh/sshd_config

Table 2-8 lists the parameters to be configured.

Table 2-8 Parameters to be configured for the SFTP

Parameter

Value

RSAAuthentication

yes

PubkeyAuthentica-

yes

tion

AuthorizedKeysFile

.ssh/authorized_keys

PasswordAuthentica-

yes/no. This parameter specifies whether the password authentication is used when the authentication of the public key and private key fails. You are advised to set this parameter to yes.

tion

l

yes: password authentication is used.

l

no: password authentication is not used.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Parameter

Value

MaxStartups

Number of concurrent connections.

The calculation method is as follows:

1. Run the following command to query the number of the SFTP tasks deployed on the U2000 server:

l

If the installed U2000 server software is a Chinese edition, run the following command:

vi /opt/oss/server/etc/XFTPService/locale/zh_CN/ TaskInfoCache.xml

#

l

If the installed U2000 server software is an English edition, run the following command:

vi /opt/oss/server/etc/XFTPService/locale/en_US/ TaskInfoCache.xml

#

 

<ftpset>

<dest>10.10.10.10</dest>

<localpath

<localpath

</ftpset>

The preceding command output is used as an example. 10.10.10.10 indicates the IP address of the northbound server, and each localpath value corresponds to a task. Record the number of tasks and enter :q! to exit the vi editor.

2. Run the following command to query the number of threads occupied by the SFTP tasks:

cat /opt/oss/server/etc/XFTPService/ ModuleParam.xml |grep TaskThreadNum

#

<param name="TaskThreadNum">10</param>

The preceding command output is used as an example. 10 indicates the number of threads occupied by the SFTP tasks. Record the number of threads.

3. The number of concurrent connections is obtained by multiplying the number of tasks by the number of occupied threads.

NOTE If you change the number of SFTP tasks, you must change the number of concurrent connections at the same time.

5. Perform the following operations on the NMS server to check the SFTP service status.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

If

Then

 

The NMS server is running Solaris

The

#

ps -ef | grep sshd | grep -v grep

 

OpenS

root 27748

1

0

Dec 25 ?

2:13 /

 

SH has

usr/local/sbin/sshd root 21923 27748

0 11:11:31 ?

been

0:02 /usr/local/sbin/sshd -R

 

installe

l

If the command output contains /usr/local/sbin/ sshd, the SFTP service is running. Run the following command to restart the SFTP service:

d

Run the

pkginf

#

/etc/init.d/opensshd restart

 

o

 

OpenS

l

If no command output is displayed, the SFTP

SH

service has not started. Run the following

comma

command to start the SFTP service:

 

nd, and

#

/etc/init.d/opensshd start

the

 

followi

ng

comma

nd

output

is

display

ed:

Securit

y

OpenSSH

OpenSSH

Portabl

e for

Solaris

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

If

Then

 
 

No

#

svcs -a | grep ssh

OpenS

online

17:27:13 svc:/network/ssh:defaul

SH has

l

If the command output contains online, the SFTP

been

service is running. Run the following command to

installe

restart the SFTP service:

d

#

svcadm restart svc:/network/ssh:default

Run the

l

If the command output contains disabled, the SFTP service has not started. Run the following command to start the SFTP service:

pkginf

o

OpenS

SH

#

svcadm enable svc:/network/ssh:default

comma

 

nd, and

the

followi

ng

comma

nd

output

is

display

ed:

ERROR:

informa

tion

for

"OpenSS

H" was

not

found

The NMS server is running SUSE Linux

#

service sshd status

Checking for service sshd running

 

l

If the command result contains running, the SFTP service is running. Run the following command to restart the SFTP service:

#

service sshd restart

l

If the command result does not contain running, the SFTP service is disabled. In this case, contact Huawei technical support.

The NMS server is running any other OS

Contact Huawei technical support.

Step 3

If you use encrypted public and private key authentication files, perform Step 4. If you use non- encrypted public and private key authentication files, perform Step 4.

1. Run the following command on the U2000 server to query the password for encrypting the private key.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

$ . /opt/oss/server/svc_profile.sh

$ XFTPPasswdEncrypt

When the following information is displayed, enter the encryption password twice.

Please Enter Password :

Please Re-enter Password :

NOTICEtwice. Please Enter Password : Please Re-enter Password : l The encryption password must be the

l

The encryption password must be the same as that in Step 1.3.

l

Keep the encryption password for future use. If the encryption password is lost, all public and private key files must be generated again, and the new files will replace the existing files.

The following information is displayed. d67A29C93775A68AE21DDAF1052EBBD1 is the encryption password.

Success. Encrpt passwd :d67A29C93775A68AE21DDAF1052EBBD1

$

2. Use the Vi command to change the values of IsSupportEncrpt, PrivateExKeyFile, and EncrptKey in the ModuleParam.xml file.

This operation must be performed on each server where the XFTPService0X01 service is deployed.

$ cd /opt/oss/server/etc/XFTPService

$ vi ModuleParam.xml

Table 2-9 Parameter description

Parameter

Description

IsSupportEncrpt

Change the value to 1, indicating that the encryption password transfer mode is supported.

PrivateExKeyFile

Set this parameter to the absolute path where the public key file generated in Step 1.3 is saved, for example, / export/home/omc/.ssh/id_rsa_pwd.

EncrptKey

Enter the queried encryption password, for example,

d67A29C93775A68AE21DDAF1052EBBD1.

3. Run the following command to check whether the config file exists:

$ cd ${HOME}/.ssh/

$ ls config

NOTEthe config file exists: $ cd ${HOME}/.ssh/ $ ls config The ${HOME} parameter indicates the home

The ${HOME} parameter indicates the home directory of user ossuser.

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

l

If config:No such file or directory is displayed, the config file does not exist. Perform Step 3.4 after running the following command:

$ touch ${HOME}/.ssh/config

$ chmod 600 ${HOME}/.ssh/config

l

If config is displayed, the config file exists. Proceed to Step 3.4.

4. Run the vi command to add the following contents to the config file:

$ cd ${HOME}/.ssh

$ vi config

IdentityFile /export/home/omc/.ssh/ id_rsa_pwd IdentityFile ~/.ssh/id_rsa

/export/home/omc/.ssh/ id_rsa_pwd IdentityFile ~/.ssh/id_rsa NOTE If the config file contains the preceding

NOTE

If the config file contains the preceding information, you do not need to modify the config file.

Step 4

Run the Vi command on the U2000 server to change the value of DefaultFTPType in the ModuleParam.xml file.

This operation must be performed on each server where the XFTPService0X01 service is deployed.

$ cd /opt/oss/server/etc/XFTPService

$ vi ModuleParam.xml

Search for the DefaultFTPType parameter and change the value to 1.

NOTE

NOTE

 

If DefaultFTPType is set to 1, the SFTP encryption mode is used. If DefaultFTPType is set to 0, the plaintext FTP mode is used.

To change the SFTP encryption mode to the plaintext FTP mode, change the value of DefaultFTPType to 0 and restart the XFTPService0X01 service.

Using the plaintext FTP mode has security risks, It is recommended that you use the SFTP mode.

 

<GeneralParams>

<param name="DefaultFTPType">1</param>

</GeneralParams>

Step 5

Run the following command on the U2000 server to restart the XFTPService0X01 service to make the modification take effect.

This operation must be performed on each server where the XFTPService0X01 service is deployed.

$ . /opt/oss/server/svc_profile.sh

$ svc_adm -cmd status | grep XFTP

You can obtain the service name of XFTPService0X01 for the server on which the current operation is performed from the command output. XFTPService0X01 is used as an example. Replace it as required.

$ svc_adm -cmd restartsvc XFTPService0X01

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Step 6

Run the following command on the U2000 server to view the XFTPService0X01 service status.

This operation must be performed on each server where the XFTPService0X01 service is deployed.

$

svc_adm -cmd status | grep XFTP

l

If the XFTPService0X01 service is in the running state in the command output, the service is running properly.

l

If the XFTPService0X01 service is in the not running state in the command output, the service is not started. When this occurs, contact Huawei technical support.

Step 7

Perform the following operations on the U2000 client to configure FTP server information:

1. Log in to the U2000 client.

2. Choose Software > FTP Auto Upload Management > Target Server Settings (traditional style); alternatively, double-click System Management in Application Center and choose Settings > FTP Auto Upload Management > Target Server Settings (application style).

In the Target Server Setting window, the configured FTP server information is displayed.

3. Select an FTP server whose information needs to be configured and click Add.

4. Set the FTP server parameters, as described in Table 2-10.

Table 2-10 Parameters in the Target Server Setting window

Parameter

Description

Module

The module type consists of NBI FM, NBI CM, NBI PM, NBI Inventory, CME NBI, CME NCCDM, License Management, NBI Server Backup, NBI Log, EBC Counter, EBC Data, and LTE Trace Data. A module name indicates that the configured FTP server is used to transfer the files corresponding to the modules in the U2000. For example, if the module name is northbound alarm, it indicates that the configured FTP server is used to transfer the files of northbound alarm modules in the U2000 server.

Type/

Module

Name

Server IP

IP address of the FTP server

User Name

User name that is used to log in to the FTP server.

Password

Password that is used to log in to the FTP server.

Confirm

Enter the password that is used to log in to the FTP server again.

Password

Server

Directory for storing a file after it is transferred to the FTP server.

Directory

The directory name cannot contain the following special characters: colon (:), asterisk (*), question mark (?), quotation mark ("), less than (<), greater than (>), and vertical bar (|).

NOTE When you log in to the U2000 server as user ftpuser, ensure that the server directory starts with "/export/home/sysm", for example, "/export/home/sysm/ftproot".

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Parameter

Description

Source

Directory for storing the LTE Trace Data need to be uploaded.

Directory

NOTE This parameter only can be configured when you modify or add a FTP server whose Module Name is LTE Trace Data.

File

Whether to compress a file before transferring it.

Compressio

n Type

l

NONE: Transfer a file without compressing it.

l

ZIP: Transfer a file after compressing it.

5. Click OK. The configuration setting is completed.

The added parameters are saved and displayed in the Target Server Setting window.

6. Choose Software > FTP Auto Upload Management > File Upload Browser (traditional style); alternatively, double-click System Management in Application Center and choose Settings > FTP Auto Upload Management > File Upload Browser (application style) to check the status of the files to be uploaded.

The files to be uploaded and files that fail to be uploaded are displayed in the Upload File Browser window.

----End

2.5.2 Configuring the SFTP for Actively Transferring Files over the Northbound Interface (Password Authentication)

When the U2000 server actively uploads files to the NMS over the northbound interface, the U2000 server functions as an FTP client and the NMS functions as an FTP server. To ensure data security during file transmission, users can set the SFTP encryption mode.

Prerequisites

 

l

Use PuTTY to log in to the U2000 server in SSH mode as user ossuser. For an HA system, you have logged in to the active and standby servers.For a remote HA system, you have logged in to the active and standby servers. For an SLS system, you have logged in to all servers.For an advanced telecommunications application environment (ATAE) cluster system, you have logged in to each server in the U2000 cluster.For an HA system, you have logged in to the active and standby servers. For an ATAE cluster system, you have logged in to each server in the U2000.For an HA or remote HA system, you have logged in to the active and standby servers. For an SLS system, you have logged in to each server.

l

You have logged in to the NMS server as user UserA.

 

UserA is an NMS server user. Replace it as required.

Context

 

l

When the password authentication is used, the password for logging in to the NMS server is required to set up an SFTP connection.

l

Unless otherwise specified, perform the following operations on each U2000 server:

U2000

Northbound Performance File Interface Developer Guide (NE-Based)

2 Interconnection Commissioning of Northbound Performance File Interface

Commissioning of Northbound Performance File Interface NOTE XFTPService0X01 indicates the XFTP service name of the

NOTE

XFTPService0X01 indicates the XFTP service name of the U2000 server. Replace it as required.

For a single-server system, the XFTP service name is XFTPService0101.The XFTP service is deployed on the active server, and the service name is XFTPService0101. The XFTP service is deployed on the active and standby servers, and the service name is XFTPService0101. For an SLS system, the XFTP service is deployed on the master and slave servers, and the service name for the master server is XFTPService0101. The service name for the first slave server is XFTPService0201. The service name for the second slave server is XFTPService0301. This method applies to the service names for other servers.For an HA system, the XFTP service is deployed on the active server, and the service name is XFTPService0101. For an SLS system, the XFTP service is deployed on the master and slave servers, and the service name for the master server is XFTPService0101. The service name for the first slave server is XFTPService0201. The service name for the second slave server is XFTPService0301. This method applies to the service names of other servers.For an HA system, the XFTP service is deployed on the active server, and the service name is XFTPService0101. For a remote HA system, the XFTP service is deployed on the active and standby servers, and the service name is XFTPService0101. For an SLS system, the service is deployed on the master and slave servers, and the service name for the master server is XFTPService0101. The service name for the first slave server is XFTPService0201. The service name for the second slave server is XFTPService0301. This method applies to other service names of other servers.

l

When the XFTP service uploads files in FTP mode:

If the northbound server runs the Linux or Unix operating system, use the vsftpd software whose version is 2.0.5 or later.

If the northbound server runs the Windows operating system, use the ftpserver service delivered with the system.

l

In an SLS system, you need to perform the following steps only on the master and slave servers and do not need to perform them on the standby server.

l

In an HA or remote HA system, you need to perform the following steps only on the active server and do not need to perform them on the standby server.

l

In an ATAE cluster online remote HA system, you need to perform the following steps only on the master and slave servers (include active site and standby site) and do not need to perform them on the standby serve