IManager U2000 NBI FTP Performace

Performance Text NBI User Guide
Contents
3 Performance Text NBI User Guide
3.1 Reading Guide
3.2 Preview
3.2.1 Overview
3.3 System Overview
3.3.1 Introduction
3.3.2 Functions
3.3.3 Equipment Supported
3.3.4 Interface Position
3.3.5 Transmission Mode
3.3.6 Security Mechanism
3.3.7 High Availability
3.3.8 Protocols
3.3.9 Performance Indicator
3.4 Performance Management
3.4.1 Performance Management Objects
3.4.2 Basic Concept
3.4.3 Performance Monitoring Principle
3.5 Performance Management Process
3.6 Enabling Performance Monitoring On the U2000
3.6.1 Monitoring Performance Events on Transport NEs
3.6.1.1 Transfers NE Performance Collection
3.6.1.2 Transfers NE Performance Auto-Report
3.6.2 Monitoring Performance of PMS-Managed Objects
3.7 Preparing for a Deployment
3.7.1 Important Notes
3.7.2 Collecting Integration Parameters
3.8 Deploying and Configuring the Performance Text NBI
3.8.1 Overview
3.8.2 Configuration Requirements
3.8.3 Configuration Workflow
3.8.4 Checking the License
3.8.5 Logging in to NBI Config Tools
3.8.6 Configuring a Performance Indicator Template
3.8.7 Configuring the Performance Text NBI
3.8.8 Check the Performance Text File
3.8.9 Configuration Examples
3.8.9.1 Configuring Transport Performance Events
3.8.9.1.1 Description for Configuration Examples
3.8.9.1.2 Enabling Performance Event Monitoring
3.8.9.1.3 Configuring the Performance Text NBI
3.8.9.2 Configuring PMS Performance
3.8.9.2.1 Description for Configuration Examples
3.8.9.2.2 Creating a Performance Monitoring Instance
3.9 Obtaining the Performance Text File
3.9.1 File Export Path
3.9.2 File Naming Rule
3.9.3 Description of File Format
3.9.4 Setting Fields to Be Exported
3.9.5 Ensuring Data Integrity of Performance Text Files
3.9.6 Parsing Principle and Restriction
3.10 Maintaining the Performance Text NBI
3.10.1 Requirements for Maintenance Personnel
3.10.2 Routine Maintenance
3.10.3 Disabling and Deleting the Performance Text NBI
3.10.3.1 Logging In to the System Monitor Client
3.10.3.2 Stopping the Performance Text NBI
3.10.3.3 Disabling the Performance Text NBI
3.10.3.4 Restarting the Performance Text NBI
3.10.4 FAQs
3.10.4.1 The System Monitor Client Contains No Performance Text NBI Process.
3.10.4.2 What Is the Process Name of the Performance Text NBI?
3.10.4.3 Does the Performance Text NBI Depend on Other Processes?
3.10.4.4 How Do I Change the Folder Hierarchy of the performance text file?
3.10.4.5 How Do I Add the ResourceID Field to the performance text file?
3.10.4.6 How Do I Export the Performance Text File After the U2000 Is Installed?
3.10.4.7 How Is Performance Data Managed on the U2000?
3.10.4.8 Which Directory on the oss Do Performance Intermediate Files Locate In?
3.10.4.9 How Do I Configure the Directory for PMS Performance Intermediate Files?
3.11 Configuring the FTP Server
3.11.1 Configuring the FTP or SFTP Server on Windows
3.11.2 Configuring the FTP Service (Solaris)
3.11.3 Configuring the SFTP Server (Solaris)
3.11.4 Configuring the FTP or SFTP Service (SUSE Linux)
3.12 Replacing the Certificate of the NBI Config Tools
3.13 Revoking the Certificate of the NBI Config Tools
3.14 PNM Performance Collection Guideline
3.15 Glossary
3 Performance Text NBI User Guide

describes the entire configuration flow of the Performance Text NBI in terms of interface
functions, installation and configuration of the interfaces, and troubleshooting.
 Reading Guide
This topic describes recommended chapters for different readers.
 Preview
This topic describes the main contents of each chapter and provides recommended chapters for
different readers.
 System Overview
The Performance Text NBI is one of the NBIs provided by the U2000. Integrated with the OSS,
the Performance Text NBI can generate the performance text file for performance management.
 Performance Management
The U2000 provides the performance management system (PMS) and the NE Explorer to
manage the performance. The PMS and the NE Explorer collect NE performance data and save it
to the database, or converts it to intermediate files. The Performance Text NBI shields
differences of NE files and transfers the intermediate files to files in a unified format. The OSS
obtains and phrases the unified files conveniently, which reduces the time for system integration
and improves the efficiency.
 Performance Management Process

Integrated with the OSS, the Performance Text NBI exports the performance text file for
performance management. On the U2000, perform different settings upon different monitoring
objects.
 Enabling Performance Monitoring On the U2000

The U2000 can manage various NEs, including the transport, access, and datacom NEs.
Performance management modes and standards vary with NE types. The U2000 manages
different NEs in different ways. Before configuring the Performance Text NBI, configure
parameters based on the NE types or performance indicators to be monitored.
 Preparing for a Deployment

Before deploying the Performance Text NBI, you need to collect related configuration data.
Modifying some configuration items may require the restart of the U2000. Therefore, to prevent
service interruption, you need to apply for modifications in advance.
 Deploying and Configuring the Performance Text NBI

To export the performance text file after performance monitoring is enabled on the U2000,
deploy and configure the Performance Text NBI first.
 Obtaining the Performance Text File

The Performance Text NBI records performance data monitored by the U2000 in a unified
format and saves the data. The OSS needs to obtain and parse these files to analyze network
health status, provide optimization suggestions, and locate faults for troubleshooting. You can
customize parameters such as path for generating these files and export fields as required. In
addition, the Performance Text NBI provides a fault tolerance mechanism to collect data for the
previous period and generate a file in the current period.
 Maintaining the Performance Text NBI
This section describes how to maintain the Performance Text NBI periodically to keep it running
properly and provides troubleshooting for common problems.
 Configuring the FTP Server

The FTP protocol must be configured correctly on the U2000 server so that the OSS can access
the U2000 to obtain the performance text file using the FTP protocol.
 Replacing the Certificate of the NBI Config Tools

U2000 provides a default security certificate for encryption and authentication. It is
recommended that customers replace the default certificate with their security certificate.
Specifically, apply for a security certificate from a trusted CA and then use the certificate to
replace the original SSL certificate of the NBI Config Tools.
 Revoking the Certificate of the NBI Config Tools

This topic describes how to revoke the SSL certificate of the U2000 NBI Config Tools.
 PNM Performance Collection Guideline

During routine maintenance of cables, proactive network maintenance (PNM) analyzes the pre-
equalization coefficient between the cable modem (CM) and cable modem termination system
(CMTS) to discover faults on cable networks and determine the fault scope and locations. This
topic describes how to use the performance text NBI to report PNM performance indicators.
 Glossary
3.1 Reading Guide

This topic describes recommended chapters for different readers.
Intended Purpose Recommended Chapter

Audience
Network They are responsible for designing, System Overview and Configuring a
planning planning, and optimizing networks, and Performance Indicator Template are
engineer need to learn working principles, network recommended for reading.
positioning, and interface parameters
(export path and period) of
thePerformance Text NBI.
Application They are responsible for developing the Configuring a Performance Indicator Template,
developer OSS and need to learn basic principles and System Overview , Performance Management,
functions of the Performance Text NBI and Obtaining the Performance Text File are
and generation rules of the performance recommended for reading.
text file. For details about how to filter the
monitored performance indicators, see
Intended Purpose Recommended Chapter
Audience
Configuring a Performance Indicator Template.

For details about how to know generation
rules of the performance text file, see
Obtaining the Performance Text File.
Installation and They are responsible for monitoring the Performance Management Process, Enabling
commissioning performance of NEs and deploying and Performance Monitoring On the U2000 ,
engineer configuring the Performance Text NBI on Deploying and Configuring the Performance
the U2000. They do not need to know the Text NBI, and Configuring the FTP Server are
Data
configuration basic concepts and principles of recommended for reading.
engineer performance management. Complete the performance monitoring of
NEs on the U2000 by following the
procedure in Enabling Performance
Monitoring On the U2000.
Focus on Deploying and Configuring the
Performance Text NBI and complete the
deployment and configuration based on
the flowchart and procedure.
For details about how to start FTP
services, see Configuring the FTP Server.
System They are responsible for maintaining System Overview , Performance Management,
maintenance interfaces, diagnosing and troubleshooting and Maintaining the Performance Text NBI are
engineer faults and need to know the working recommended for reading.
principles of the Performance Text NBI.
Parent topic: Performance Text NBI User Guide
3.2 Preview
This topic describes the main contents of each chapter and provides recommended chapters for
different readers.
 Overview
This topic describes the main contents of each chapter.

3.2.1 Overview
This topic describes the main contents of each chapter.
Chapter Description
System Overview This chapter describes the features such as network positioning,
supported functions, security mechanism, and standards compliance
of the Performance Text NBI.
Performance Management This chapter describes the performance management on the U2000,
including managed objects, basic concepts and principles.
Performance Management Process This chapter describes the performance management process of the
U2000 and provides related notes and operation hyperlinks.
Enabling Performance Monitoring On This chapter describes how to monitor NE performance data on the
the U2000
U2000.
Deploying and Configuring the This chapter describes the process and procedure of deploying and
Performance Text NBI
configuring thePerformance Text NBI and provides configuration
examples.
Obtaining the Performance Text File This chapter describes generation rules, parsing principles and
restrictions of the performance text file.
Maintaining the Performance Text NBI This chapter describes routine maintenance operations of the
performance text file and describes how to rectify common faults.
Configuring the FTP Server This appendix describes the procedure of configuring FTP services
on theU2000 server.
Glossary This appendix provides terms, acronyms and abbreviations used in
the document.
Parent topic: Preview
3.3 System Overview

the Performance Text NBI can generate the performance text file for performance management.
 Introduction
the Performance Text NBI can export performance data from transport, access, and IP NEs
managed by the U2000. It uses FTP or SFTP to transmit performance data, which meets the
requirements of large volume data transmission on large-scale networks.
 Functions
Integrated with the OSS, the Performance Text NBI can be used to export the performance text
file for performance data management.
 Equipment Supported
 Interface Position
Performance Text NBI connects the OSS and the U2000. The OSS uses the Performance Text
NBI to obtain performance data on NEs managed by the U2000.
 Transmission Mode
Performance Text NBI supports file transmission in PULL or PUSH mode.
 Security Mechanism
The security of Performance Text NBI is based on the FTP or SFTP protocol.
 High Availability
The high availability (HA) of the Performance Text NBI is provided by the U2000. The OSS
processes the performance data file in different ways, depending on the deployment mode of
servers.
 Protocols
The Performance Text NBI uses the FTP or SFTP protocol to transmit the performance text file.
 Performance Indicator
This topic describes the performance indicators of the Performance Text NBI for exporting the
performance text file.
3.3.1 Introduction
the Performance Text NBI can export performance data from transport, access, and IP NEs
managed by the U2000. It uses FTP or SFTP to transmit performance data, which meets the
requirements of large volume data transmission on large-scale networks.
Huawei engineers have developed the Performance Text NBI based on the U2000 features. The
Performance Text NBI converts historical performance data collected by the U2000 to files in a
unified format and save them to a specified directory. A third-party NMS or the OSS can
function as the FTP client and obtain the required data from the specified directory for analysis
and use. The Performance Text NBI can also transmit performance text file to another FTP
server.
Parent topic: System Overview
3.3.2 Functions
Integrated with the OSS, the Performance Text NBI can be used to export the performance text
file for performance data management.
The Performance Text NBI provides the following functions:
 Generates the performance text file in a unified format (*.csv). For details about the file
format, see Description of File Format.
 Exports the performance text file based on the collection period (the period can be 5, 10, 15,
30, 60, 360, or 1440 minutes).
 Exports the performance text file at the scheduled time (5, 10, 15, 30, 60, 360, or 1440
minutes, the time must be longer than the collection period).
 Specifies the start time to export the performance text file.
 Checks data integrity of the performance text file. If the performance text file fails to be
generated, the data will be saved to the performance text file which will be generated in the
next period. (SDH, WDM and OTN performance data does not support this function.)
 Transmits the performance text file to the specified FTP or SFTP server.
 Exports the performance text file by indicator.
 Specifies the start time to delete the performance text file.
 Clears earlier performance text file periodically.
 Specifies the number of data records in a single file.
3.3.3 Equipment Supported

Transport Equipment
Table 1 Transport equipment supported by the performance text NBI
Feature MSTP Hybrid WDM OTN Hybrid TDM Packet PTN Marine
MSTP RTN RTN RTN
(TDM
Feature)
Performance √ √ √ √ √ √ √ √ ×
NOTE:
Submarine and North American equipment is not supported.
Router Equipment
Table 2 Router equipment supported by the performance text NBI
Feature NE Series CX Series Switch BRAS ATN Security
Performance √ √ √ × √ ×
NOTE:
The following devices are supported:
 NE series:(NE40/40E/40E-4/40E-X3/40E-X8/40E-X16 ,NE80/80E, NE5000E, NE5000E-Multi).
 CX series: CX600/600-4/600-8/600-16/600-X1/600-X2/600-X3/600-X4/600-X8/600-X16.
 Switches: Quidway S2300/3300/5300/9300
 BRAS: ME60/60-X3/-X8/60-X16
 ATN VRP series: ATN910/950/990
Access Equipment
Table 3 Access equipment supported by the performance text NBI
Feature MSAN/DSLAM FTTx
Narrowband Port Broadband Port FTTH FTTB/FTTC
Performance √ √ √ √

3.3.4 Interface Position
Performance Text NBI connects the OSS and the U2000. The OSS uses the Performance Text
NBI to obtain performance data on NEs managed by the U2000.
Figure 1 shows the position of the Performance Text NBI on the network.
Figure 1 Position of the Performance Text NBI on the network
NE (Network Element) A device on the network. NEs are managed by the U2000.
U2000 The NMS of Huawei. The U2000 uses a multi-process architecture

design. The Performance Text NBI is one component of the U2000.
You can customize performance indicators so that the Performance
Text NBI periodically generates performance text file for a third-party
NMS or the OSS.
Performance Text NBI One of the NBIs provided by the U2000, which is used to generate
performance text file and save it to a specified path.
OSS OSS: Obtains the performance text file as required.

3.3.5 Transmission Mode
Performance Text NBI supports file transmission in PULL or PUSH mode.
PULL Mode
In PULL mode, the OSS functions as the FTP client and obtains the performance text file from
the U2000 server which is used as the FTP server.
If the U2000 server is used as the FTP server, the OSS functions as the FTP client and obtains
the performance text file from the U2000 server.
Figure 1 Scenario in which the U2000 server and the FTP server are deployed on the same equipment
PUSH Mode
In PUSH mode, the U2000 functions as the FTP client to transmit the performance text file to the
customer-specified FTP server.
In PUSH mode, files can be transmitted in two ways, depending on whether a third-party FTP
server is deployed:
If the OSS server and the FTP server are deployed on the same equipment, the U2000 functions
as the FTP client and uses the Performance Text NBI to transmit the performance text file to the
OSS or FTP server.
Figure 2 Scenario in which the OSS server and the FTP server are deployed on the same equipment
If a third-party FTP server is deployed, the U2000 functions as the FTP client and transmits the
performance text file to the FTP server. The OSS can also be used as the FTP client to obtain the
performance text file from the FTP server.
Figure 3 Scenario in which a third-party FTP server is deployed
3.3.6 Security Mechanism

The security of Performance Text NBI is based on the FTP or SFTP protocol.
PULL Mode
In PULL mode, the U2000 server functions as the FTP server. The OSS functions as the FTP
client and obtains the performance text file from the U2000 server. To achieve this, the OSS
must have the read permission on the U2000 FTP server.
PUSH Mode
In PUSH mode, the U2000 functions as the FTP client and transmits the performance text file to
the FTP server. The FTP server can be the OSS or a customer-specified server. To achieve this,
the U2000 must have read and write permissions on the specified FTP server.
NOTICE:
SFTP is recommended for security. The SFTP protocol can be used to further enhance the
security. In SFTP mode, the FTP server allows you to obtain the performance text file only after
the correct SFTP key or the correct password is entered.
3.3.7 High Availability

The high availability (HA) of the Performance Text NBI is provided by the U2000. The OSS
processes the performance data file in different ways, depending on the deployment mode of
servers.
NOTICE:
 In PUSH mode, data is lost if the performance text file is transmitted during active/standby
switchovers of an HA system.
 In addition, data is lost if the performance text file is generated during active/standby
switchovers of an HA system.
 For details about HA switchover principles, see the iManager U2000 Administrator Guide.
PULL Mode
In PULL mode, the U2000 saves the performance data file to a local directory, and the OSS
functions as the FTP client to obtain the file automatically.
When a fault occurs in the HA system, the U2000 is automatically switched to the secondary
site. The OSS obtains the performance data file from the secondary site.
PUSH Mode
In PUSH mode, the U2000 transmits the performance data file to the customer-specified server.
1. When a fault occurs in the HA system, the U2000 is automatically switched to the secondary
site and transmits the performance data file to the specified server. The OSS does not need to
take any measures.
2. The U2000 may fail to upload performance data files to the FTP server because the FTP
server is not started or the network connections are in the abnormal state. If such faults
recover in a specified time, the U2000 uses its retransmission mechanism to upload the files
that are not uploaded successfully again. This mechanism ensures that the OSS can receive
performance data during the fault period and avoids performance text file loss.
NOTE:
 The fault recovery time is not longer than the time that the performance text file is saved on the server.
Otherwise, the U2000 automatically deletes files and files are lost. For details about how to set the time, see
Table 10.
 The FTP server on the OSS determines the retransmitted files due to a transmission failure based on the file
generation time.
3.3.8 Protocols
The Performance Text NBI uses the FTP or SFTP protocol to transmit the performance text file.
Figure 1 shows the protocol stack model used by the Performance Text NBI.
Figure 1 Protocol stack of the Performance Text NBI
3.3.9 Performance Indicator

This topic describes the performance indicators of the Performance Text NBI for exporting the
Table 1 lists indicators of the Performance Text NBI.
Table 1 Indicators of the Performance Text NBI
Item Indicator
Maximum number of connected  As the FTP client, the U2000 transmits files to one OSS only.
OSS  As the FTP server, the U2000 can be visited by a maximum of
three OSSs.
NOTE:
For the delay time to export performance text file, see Configuring the Performance Text NBI.
3.4 Performance Management

The U2000 provides the performance management system (PMS) and the NE Explorer to
manage the performance. The PMS and the NE Explorer collect NE performance data and save it
to the database, or converts it to intermediate files. The Performance Text NBI shields
differences of NE files and transfers the intermediate files to files in a unified format. The OSS
obtains and phrases the unified files conveniently, which reduces the time for system integration
and improves the efficiency.
 Performance Management Objects

 Basic Concept
This topic describes basic concepts in this document.
 Performance Monitoring Principle

The U2000 manages various NEs, including transport, IP, and access NEs. NE Explorer,
performance, and NBI modules of the U2000 work cooperatively to implement the process from
collecting performance data to generating the performance text file.
3.4.1 Performance Management Objects

NOTE:
 For details about performance events that are supported by the Performance Text NBI, see the iManager U2000
Performance Text NBI Performance Event List.
 For details about the version mapping, see the iManager U2000 Version Mapping.
Objects Managed by the PMS

The U2000 PMS monitors performance of most NEs. Objects managed by the PMS include:
 Routers and switches
 Access NEs
 PTN NEs
 The RMON performance of transport NEs
 RTN 900 series NEs
Objects Managed by the NE Explorer

The NE Explorer manages the following objects of transport NEs:
 Non-RMON performance of SDH or MSTP NEs
 Non-RMON performance of WDM or OTN NEs
 Non-RMON performance of RTN 600 series NEs
Parent topic: Performance Management
3.4.2 Basic Concept

This topic describes basic concepts in this document.
Resource
The U2000 defines all performance objects as resources. For example, NEs, boards, ports, and
links managed by the U2000. A resource can be a physical or logical entity.
Indicator and Indicator ID

The U2000 uses performance indicators to determine the resource usage and running status of
the network. The U2000 obtains the network running status by monitoring performance
indicators of managed objects.
The U2000 assigns an ID for each indicator. The indicator ID, along with the indicator group ID,
uniquely identifies the indicator.
The Performance Text NBI further divides the ID range for each indicator. This indicator ID can
uniquely identifies the indicator, without considering the indicator group ID.
 If a performance object is monitored by the PMS, its indicator ID defined by the Performance
Text NBI is the same as that defined by the U2000.
 If a performance object of transport NEs is monitored by the NE Explorer, its indicator ID
defined by the Performance Text NBI is that defined by the U2000 plus 1000000.
Indicator Group and Indicator Group ID

Only the NE Explorer can monitors performance (excluding the RMON) of transport SDH,
WDM, and OTN NEs. A performance event indicates a performance indicator. To facilitate
manage the performance events, the U2000 assigns all performance events to different groups.
The U2000 PMS manages other performance events. The U2000 assigns indicators to indicator
groups based on the attributes of indicators.
The Performance Text NBI redefines the indicator group, which is different from that defined by
the U2000. The indicator group of the Performance Text NBI is defined in the indicator filter
template. For details, see Configuring a Performance Indicator Template .
Performance Template
Performance templates include data monitoring template, performance event monitor status
template, TCA monitoring template, and performance threshold template.
 Data monitoring template: It applies to non-MSTP, non-WDM, and non-RTN NEs for
creating performance monitoring instances and collecting NE performance data.
 Performance event monitor status template: It applies to MSTP, WDM, and RTN NEs for
enabling or disabling performance event monitoring.
 TCA monitoring template: It applies to non-MSTP, non-WDM, and non-RTN NEs for
creating threshold monitoring instances. If the performance value exceeds the threshold, an
alarm occurs.
 Performance threshold template: It applies to MSTP, WDM, and RTN NEs for performance
event monitoring. If the performance value exceeds the threshold, a TCA event occurs.
NOTE:
The Performance Text NBI uses only the data performance template and the performance status monitor template
because they are used to collect NE performance data and generate performance text file.
Performance Monitoring Instance

Performance data on PMS-managed resources is collected using performance monitoring
instances. The Performance Text NBI uses collected data to generate performance data files. For
details about how to create performance monitoring instances, see Monitoring Performance of PMS-
Managed Objects .
A performance monitoring instance is a performance monitoring task. Integrating the

performance data template, the performance monitoring instance collects performance indicators
specified by the resource.
The mechanism can be described in a formula as "resource + template = instance".
NOTE:
Performance monitoring instances for transport performance events (non-RMON performance of MSTP, WDM, and
OTN NEs) managed by the NE Explorer cannot be created. To monitor these events, enable the performance
monitoring function in the NE Explorer. For details about how to enable the performance monitoring function, see
Transfers NE Performance Auto-Report.
The U2000 does not save the performance text file about NE Explorer-managed performance events. Historical
performance data, however, can be queried on NEs.
Indicator Template
The Performance Text NBI can generate performance text file for specified indicators or
indicator groups. To achieve this, you need to create an indicator template manually and use the
NBI Config Tools to export the template to the U2000.
For details about indicator templates, see Configuring a Performance Indicator Template .
3.4.3 Performance Monitoring Principle

The U2000 manages various NEs, including transport, IP, and access NEs. NE Explorer,
performance, and NBI modules of the U2000 work cooperatively to implement the process from
collecting performance data to generating the performance text file.
Figure 1 shows principles of the U2000 on monitoring the network, and performance data flows.
Figure 1 Performance monitoring principle
The following are details about performance data flows described in Figure 1.
 Data flow X indicates that the U2000 collects NE performance data.
 Data flow Y indicates that the U2000 generates a performance text file.
 Data flow Z indicates that the OSS obtains the performance text file from the U2000 using the
FTP/SFTP protocol. With the collated data, the OSS analyzes the health state of the live
network and provides optimization advice for customers to fast resolve the network problem.
As shown in the preceding figure, the dotted line area shows the U2000 internal data flow.
Different management objects are managed by different modules.
 For the RMON performance of PTN and transport NEs
 NEs generate performance data.
 Data flow A1 indicates that the NE Explorer obtains performance data from NEs
periodically (by NE management period).
 Data flow A2 indicates that the U2000 saves the collected performance data to the
database.
 Data flow A3 indicates that the performance module obtains performance data from the
database.
 Data flow A4 indicates that the performance module converts the performance data into an
intermediate file.
 Data flows A5 and A6 indicate that the NBI module converts the intermediate file to the
performance text file (by NBI module period).
 For the performance of transport SDH and OTN NEs
 Data flow B1 indicates that the NE Explorer obtains performance data from NEs
periodically (by NE management period).
 Data flow B2 indicates that the NE Explorer converts collected performance data into an
intermediate file.
 Data flows B3 and B4 indicate that the NBI module converts the intermediate file to the
 For the performance of IP, and access NEs.
 Data flow C1 indicates that the performance module obtains performance data from NEs
periodically (by data collection period).
 Data flow C2 indicates that the performance module saves the collected performance data
to the database.
 Data flow C3 indicates that the performance module converts the performance data into an
intermediate file.
 Data flows C4 and C5 indicate that the NBI module converts the intermediate file to the
3.5 Performance Management Process

Integrated with the OSS, the Performance Text NBI exports the performance text file for
performance management. On the U2000, perform different settings upon different monitoring
objects.
Figure 1 shows how the U2000 monitors performance objects and exports performance text file.
For details about related operations, see Table 1.
Figure 1 Performance Management Flowchart

Table 1 Operation Description
Operation Description Reference
Determine the performance Monitor operations are performed on Performance

monitoring object. different monitoring objects. Management
Objects
Monitor Synchronize NE The configuration may fail if NE data is Transfers NE

performance of data (optional). different from the U2000 data. Performance
Collection
transport NEs
(include Synchronize NE The U2000 fails to determine the correct
RMON). time (optional). occurrence time of performance events if NE
time is different from the U2000 time.
Therefore, perform the following settings:
 Synchronization between NE time and the
U2000 time
 Automatic synchronization of NE time
 Consistency between the NE time zone
and the Daylight Saving Time (DST)
Set the NE Enable 15-minute or 24-hour performance

performance monitoring on NEs and set the start time and
monitoring time. end time of performance monitoring.
NOTE:
If 24-hour performance monitoring is required,
set the start time as 00:00 (UTC).
Enable performance This operation is performed on boards. You

monitoring and can enable the performance monitoring and
auto reporting. auto reporting using the NE Explorer or by
applying templates to related boards.
Set performance To query and process NE performance data,

data collecting you can collect the performance data
automatically. automatically. Then the U2000 is able to
export the collection results and save the data
to text files. This reduces replicated
operations.
Deploy the To export the performance text file after Deploying and
Configuring the
Performance Text enabling the performance monitoring, deploy Performance Text
NBI. the Performance Text NBI first. NBI
Monitor Synchronize NE The configuration may fail if NE data is Transfers NE

performance of data (optional). different from the U2000 data. Performance Auto-
transport NEs Synchronize NE The U2000 fails to determine the correct Report
(exclude time (optional). occurrence time of performance events if NE
RMON). time is different from the U2000 time.
Therefore, perform the following settings:
U2000 time
and the Daylight Saving Time (DST)
Set the NE Enable 15-minute or 24-hour performance

performance monitoring on NEs and set the start time and
monitoring time. end time of performance monitoring.
NOTE:
If 24-hour performance monitoring is required,
set the start time as 00:00 (UTC).
Enable performance This operation is performed on boards. You

monitoring and can enable the performance monitoring and
auto reporting. auto reporting using the NE Explorer or by
applying templates to related boards.
Enable the export Modify trans_ems.cfg and enable the

function of performance data export function of
transport NEs. transport NEs.
Configuring the
Restart the NE Mandatory step: Transfers NE

Explorer. Performance Auto-
Log in to the System Monitor client to restart Report
the NE management process of monitored
objects. For details, see Transfers NE
Performance Auto-Report.
Monitor Synchronize NE Instance creation may fail if NE data is Monitoring

performance of data. different from the U2000 data. Performance of
PMS-Managed
PMS-managed Objects
objects. Synchronize NE The U2000 fails to determine the correct
time. occurrence time of performance events if NE
time is different from the U2000 time.
Therefore, the following items must be set:

U2000 time
and the DST.
Configure You can customize performance monitoring

monitoring templates for concerned performance
templates. indicators.
Create performance You can create performance monitoring

monitoring instances for concerned resources and bind
instances. them to the monitoring templates. The
U2000 then collects important performance
indicator data of the concerned resources.
Configuring the
3.6 Enabling Performance Monitoring On the

U2000
 Monitoring Performance Events on Transport NEs

To query and process NE performance data, you can collect the performance data automatically.
The U2000 supports periodical NE performance data collection in two modes: Transfers NE
Performance Collection or Transfers NE Performance Auto-Report. Then the U2000 is able
to export the collection results and save the data to text files. This reduces replicated operations.
 Monitoring Performance of PMS-Managed Objects
The U2000 uses the PMS to manage performance of transport, access, and IP NEs. The PMS
manages all the performance of PTN and RTN equipment. For other transport NEs, the PMS
manage the RMON performance, the NE Explorer manages None-RMON performance. The
PMS collects performance data, saves the data to the database, and generates intermediate files.
The Performance Text NBI converts the intermediate files to files in a unified format and
transmits them to the OSS.
3.6.1 Monitoring Performance Events on

Transport NEs
To query and process NE performance data, you can collect the performance data automatically.
The U2000 supports periodical NE performance data collection in two modes: Transfers NE
Performance Collection or Transfers NE Performance Auto-Report. Then the U2000 is able
to export the collection results and save the data to text files. This reduces replicated operations.
 Transfers NE Performance Collection

To query and process NE performance data, you can collect the performance data (including the
RMON performance) of transport NEs, including MSTP, WDM, PTN, RTN and OTN NEs, and
exports intermediate files automatically.
 Transfers NE Performance Auto-Report

The NE Explorer monitors the performance (excluding the RMON performance) of transport
NEs, including MSTP, WDM, and OTN NEs, and exports intermediate files. The Performance
Text NBI converts the intermediate files to files in a unified format and transmits them to the
OSS. The performance data will not be stored in the database after being exported to the
intermediate files.
Parent topic: Enabling Performance Monitoring On the U2000
3.6.1.1 Transfers NE Performance Collection

To query and process NE performance data, you can collect the performance data (including the
RMON performance) of transport NEs, including MSTP, WDM, PTN, RTN and OTN NEs, and
exports intermediate files automatically.
Application Scope
 Historical performance data, including 15-minute performance data and 24-hour performance
data, on MSTP, WDM, PTN, RTN and OTN NEs.
 Historical performance data of SDH NEs and RMON. The data include 15-minute
performance data and 24-hour performance data.
Context
For details about the performance of transport NEs, see Performance Management
(MSTP&WDM&RTN&PTN) in the U2000 Online Help and Operation Guide for Common
Features.
Procedure
1. Synchronize NE time.
a. Choose Configuration > NE Batch Configuration > NE Time Synchronization
(traditional style) from the main menu or select Fix-Network NE Configuration in
Application Center and choose Configuration > NE Batch Configuration > NE
Time Synchronization (application style) from the main menu.
b. Select NE1000 from the object tree and click .

c. Click Close in the dialog box.
d. Select one or more NEs from the list and click Synchronize with NM Time
e. In the confirmation dialog box, click Yes. In the Operation Result dialog box, click
Close
2. Synchronize NE data for NEs. In the Main Topology, right-click the required NE from the
Physical Root navigation tree and choose Synchronize NE Data from the shortcut menu.
3. Set the performance monitoring time of an NE.
a. Choose Performance > Set NE Performance Monitoring Time (traditional style)

from the main menu or select Fix-Network Performance in Application Center and
choose Performance Monitoring > Set NE Performance Monitoring Time
(application style) from the main menu.
c. Select the 15-Minute check box to enable 15-min monitoring and set the start time.
NOTE:
Select the 24-Hour check box to enable 24-hour monitoring if required.
d. Click Apply.
4. Optional: Enable performance monitoring by NE explorer.

a. In the NE explorer of the monitoring object, select the required board, select Function
Tree > Performance > Performance Monitor Status.
b. Enable the Monitor Status of the performance event to be monitored.
NOTE:
You must enable 15-Minute Auto-Report or 24-Hour Auto-Report of the performance event.
5. Collect the performance data automatically.
a. Choose Performance > NE Performance Collection from the main menu (traditional
style); alternatively, double-click Fix-Network Performance in Application Center
and choose Performance Monitoring > NE Performance Collection from the main
menu (application style).
b. In the window that is displayed, click the NE tab.
c. Select the desired NEs from the navigation tree in the left pane and click .
d. Click Query.
e. Set the Enabled for the NE, and click Apply.
f. Click the Collection Parameters tab.
g. Click Query.
h. Set the performance monitoring period and the period that the U2000 collects NE
performance data.
NOTE:
The U2000 starts periodical collection task based on the collection period that you set. The CSV files
containing the exported performance data are saved to U2000 installation
directory/server/var/dump/PerfFileData/trans/data/ by default.
i. Click Select Performance Event. In the Set Performance Event Collection dialog box
that is displayed, set whether the performance event to be collected by the U2000.
NOTE:
 You can click the Performance or RMON Performance tab according to the NE features. In the
lower pane of the dialog box, double-click the Collection column on the right of a performance event
and select Enable or Disable from the drop-down list.
 In the upper pane of the dialog box, you can set Performance Event and Collection and click Filter
to query the collection status of the performance event.
j. In the Set Performance Event Collection dialog box, click Apply to save the
configuration. In the dialog box that is displayed, click Closed.
k. In the Set Performance Event Collection dialog box, click Closed.
l. In the Collection Parameters window, click Apply. In the dialog box that is displayed,
click Closed.
Parent topic: Monitoring Performance Events on Transport NEs
3.6.1.2 Transfers NE Performance Auto-Report

The NE Explorer monitors the performance (excluding the RMON performance) of transport
NEs, including MSTP, WDM, and OTN NEs, and exports intermediate files. The Performance
Text NBI converts the intermediate files to files in a unified format and transmits them to the
OSS. The performance data will not be stored in the database after being exported to the
intermediate files.
Application Scope
data, on WDM and OTN NEs
 Historical performance data of SDH NEs. The data include 15-minute performance data, 15-
minute low performance (LP) data, 24-hour performance data, and unavailable second (UAS)
LP data
Context
For details about the performance of transport NEs, see Performance Management
(MSTP&WDM&RTN&PTN) in the U2000 Online Help and Operation Guide for Common
Features.
Procedure

Close
NOTE:
Select the 24-Hour check box to enable 24-hour monitoring if required.
d. Click Apply.
4. Enable performance monitoring by template.
a. Choose Performance > Performance Template Management > Performance Event

Monitor Status Template (traditional style) from the main menu or select Fix-
Network Performance in Application Center and choose Performance Monitoring >
Performance Template Management > Performance Event Monitor Status
Template (application style) from the main menu.
b. Set the performance event to be monitored to Enable in the list.
NOTE:
c. Click Save As and set the template name.
d. Click Apply To. In the dialog box that is displayed, select the required board from the
object tree and click OK.
e. The Operation Result dialog box is displayed, indicating that the operation is
successful. Then, click Close.
5. Optional: Enable performance monitoring by NE explorer.
a. In the NE explorer of the monitoring object, select the required board, select Function
Tree > Performance > Performance Monitor Status.
b. Enable the Monitor Status of the performance event to be monitored.
NOTE:
6. Enable the performance text file export function of transport NEs.

a. Enter the server/etc/oss_cfg/trans/core/conf directory.
b. Specifically, set the configuration item bSavePfmLog15mToFile in trans_ems.cfg file

to 1 (enable). The value is 0 (disable) by default.
c. #| Whether to Save 15min Performance Logs to Files, Instead of Database
(1-Enable, 0-Disable) bSavePfmLog15mToFile = 1
7. Restart the NE Explorer.

a. Log in to the System Monitor client.
b. On the Process Monitor tab, right-click the related NE management process for the
object of performance data collection and choose Stop from the shortcut menu.
c. Restart the NE Explorer after the NE management process is stopped.
Parent topic: Monitoring Performance Events on Transport NEs
3.6.2 Monitoring Performance of PMS-Managed

Objects
The U2000 uses the PMS to manage performance of transport, access, and IP NEs. The PMS
manages all the performance of PTN and RTN equipment. For other transport NEs, the PMS
manage the RMON performance, the NE Explorer manages None-RMON performance. The
PMS collects performance data, saves the data to the database, and generates intermediate files.
The Performance Text NBI converts the intermediate files to files in a unified format and
transmits them to the OSS.
Application Scope
data, on PTN NEs
data, on RTN NEs
 Historical RMON performance data, including 15-minute performance data and 24-hour
performance data, on transport NEs
 Historical performance data of access NEs
 Historical performance data of IP NEs
Context
For more details about the performance monitoring of PMS, see Performance Management
System (PMS) in the U2000 Online Help or the U2000 User Guide for PMS.
Procedure
1. Synchronize the NE time for transport and PTN NE.

Close
2. Synchronize NE time for access NEs. In the Main Topology, right-click the desired NE
from the Physical Root navigation tree and choose Set NE Time from the shortcut menu.
4. Create performance monitoring templates.
a. Choose Performance > Performance Template Management > Performance

Monitor Template (traditional style) from the main menu or select Fix-Network
Performance in Application Center and choose Performance Monitoring >
Performance Template Management > Performance Monitor Template (application
style) from the main menu.
b. In the left pane, select the resource type from the Resource Type tree and click Create.
c. In the Template Name text box, enter the data monitoring template name.
d. Select the performance indicator to be monitored.
NOTE:
Click Filter. You can filter the indicators by NE type.
e. Click OK.
5. Create performance monitoring instances.
a. Choose Performance > Performance Monitoring Management (traditional style)

choose Performance Monitoring > Performance Monitoring Management
b. In the left pane, select the resource type from the Resource Type tree and click Create.
The instance creation wizard is displayed.
c. Select the monitoring object. Select the resources in the Available Resources area and
click to move the resources to the Selected Resources area.
d. Click Next to select the data monitoring template and granularity.
NOTE:
The Performance Text NBI creates data monitoring instances only. Do not select a TCA monitoring
template for it.
e. Click Next to configure time information.
NOTE:
The default value can be used, which indicates the time setting takes effect immediately and always valid.
f. Click Next. The progress bar and results of instance creation are displayed.
g. Click Finish.
h. Optional: View the new instances in the Performance Monitoring Management

window. If Monitoring Status is Running, the instances are created successfully.
Parent topic: Enabling Performance Monitoring On the U2000
3.7 Preparing for a Deployment

Before deploying the Performance Text NBI, you need to collect related configuration data.
Modifying some configuration items may require the restart of the U2000. Therefore, to prevent
service interruption, you need to apply for modifications in advance.
 Important Notes
This topic describes the important notes for deploying and configuring the Performance Text
NBI.
 Collecting Integration Parameters

Integration parameters must be collected from OSS O&M engineers and confirmed before the
Performance Text NBI is deployed to ensure that the input parameters are correct; otherwise, the
OSS cannot get performance text file from U2000.
3.7.1 Important Notes

This topic describes the important notes for deploying and configuring the Performance Text
NBI.
Deploying and configuring the Performance Text NBI may affect the OSS and other components
of the U2000. Modifying configuration items may also depend on the U2000 components.
Therefore, confirm whether the configuration items to be modified will bring such kind of
impact and submit a request to the customer for approval before deploying and configuring the
Performance Text NBI.
NOTICE:
Deploying and configuring any parameters of the Performance Text NBI will cause the
performance text NBI service textagent to be restarted.
Parent topic: Preparing for a Deployment
3.7.2 Collecting Integration Parameters

Integration parameters must be collected from OSS O&M engineers and confirmed before the
Performance Text NBI is deployed to ensure that the input parameters are correct; otherwise, the
OSS cannot get performance text file from U2000.
Table 1 and Table 2 show the collected information.
NOTICE:
Collect general parameters only and use default values for advanced parameters.
Table 1 General parameters
Item Sample Description
Export Period Mode Single period Single period, Multi-period

If you need to export the performance data
with multiple period such as 5 or 15 minute
performance, select the single period. If you

choose Manual from the Duration Setting
drop-down list, you need to set the export
duration time for the required period.
Duration Setting Auto Auto, Manual

You can customize the export duration
performance text file. It is suggest you use the
default value.
Indicator - The U2000 only export the performance text

file of the indicators that in the template.
You can get or configure the indicator template
with the following methods.
 The default template provided in iManager
U2000Performance Text NBI Performance
Indicator Template.
 Configure the indicator template in
otherU2000, then export the template and
import to the required U2000.
 Configure the indicator template in the
required U2000.
File Export d:/oss/server/nbi/text/pfm_output U2000 is the FTP/SFTP server, the

Export Directory performance text file is exported in the U2000
server, the OSS get the performance text file as
FTP/SFTP client.
For Solaris or Linux, the ossuser user must
have read/write/execute permission for the
export directory.
Export FTP Mode: SFTP U2000 is an FTP/SFTP client and to the OSS
To is an FTP server. U2000 upload performance
FTP/SFTP Server IP: text file to the OSS server.
10.67.188.88 You must check the FTP/SFTP parameters
with the FTP/SFTP server manager.
FTP/SFTP Port: 23
FTP/SFTP User: perf_text_user
FTP/SFTP Password:
Changeme_123
FTP/SFTP Directory:
/u2000_nbi/text/pfm_output
SFTP Certificate: None
Table 2 Advanced Parameter
Log file Max. Logs 10 Indicates the maximum number of log files that
(10-20) can be exported at a time.
Max. Log 5 Indicates the maximum size of log files that can
Size (MB)(5- be exported at a time.
20)
Log Level Debug Indicates the log level. Logs are classified into
four levels, such as debugging, information,
warning, and error, based on the log importance.
This item is used to set the lower level threshold
of log files that can be exported. Log files of a
level lower than this threshold are not recorded.
Encoding format UTF-8 You must check the character set of the OSS,
then set the correct value. Current version
support two character set, such as UTF-8 and
GBK. The character set of performance text file
and OSS must be the same. If the character set
of performance text file for Performance Text
NBI is different from the OSS, the OSS maybe
can not parse the performance text file.
Time Format UTC time Indicates the time format. Two time formats are
available.
Setting the time format affects the name of
exported files. For details, see File Naming Rule.
Other Max Records 100000 Indicates the maximum number of records that a
in File file can contain. When the number of records is
larger than this value, new records are saved in
another file.
SN of the new file = SN of the existing file + 1.
Save Export 3 Indicates the duration for saving the exported

Table 2 Advanced Parameter
File For files on the local server.
Delete 2009-09-01 00:00:00 Indicates the start time of a scheduled task for
Historical File deleting a file. This time is the server time.
On
Parent topic: Preparing for a Deployment
3.8 Deploying and Configuring the

Performance Text NBI
To export the performance text file after performance monitoring is enabled on the U2000,
deploy and configure the Performance Text NBI first.
 Overview
This topic describes the background information and the terms involved in the process of
configuring the northbound interface.
 Configuration Requirements
The Performance Text NBI and the U2000 server run on the same equipment, and no additional
configuration is required. However, you must purchase a license before using the Performance
Text NBI.
 Configuration Workflow
To deploy the Performance Text NBI, check the license, configure the performance indicator
template, check whether the Performance Text NBI status, configure the NBI, and restart the
process. Configure the Performance Text NBI according to the check results.
 Checking the License

The U2000 controls the functions and available resources of the Performance Text NBI by the
license. Before using the Performance Text NBI, ensure that you have obtained its license and
ensure that the Performance Text NBI configurations in the license meet requirements.
 Logging in to NBI Config Tools

The NBI Config Tools is a graphical maintenance tool developed for the northbound interfaces
(NBIs) of iManager U2000. The MSuite is used to configure the NBIs.
 Configuring a Performance Indicator Template

The performance indicator template is an XML file that complies with the XML specifications.
You can enable performance monitoring on multiple indicators on the NMS, and export only the
performance text file for the required indicator. In this case, a performance indicator template is
required and indicators to be filtered are added to this template. For the U2000 V100R009C00
and later versions, you can use the NBI Config Tools to configure a performance indicator
template directly on the U2000 server. Alternatively, you can modify a performance indicator
template and import it into the U2000 server. One of the two modes must be performed.
Otherwise, the performance text file cannot be exported. It is recommended you use NBI Config
Tools to configure template. When upgrade with UExpert, the template will as same as the old
one. You must export the template from the source version U2000 then import it to the target
version if using other method to upgrade U2000.
 Configuring the Performance Text NBI

After the U2000 is installed, to enable the Performance Text NBI, you need to set the
Performance Text NBI parameters according to the NMS plan.
 Check the Performance Text File

After deploying the Performance Text NBI and enabling the performance monitoring on the
U2000, you need to check whether the performance text file is generated successfully to
determine the running status of the Performance Text NBI.
 Configuration Examples
This topic describes the procedure for enabling performance monitoring on the U2000,
deploying the Performance Text NBI, and obtaining the performance text file using examples.
3.8.1 Overview
This topic describes the background information and the terms involved in the process of
configuring the northbound interface.
Attention Item
 Northbound interface is an optional component of the U2000. A license is required for using
this function.
 The northbound interface system has been added automatically during the installation of
U2000. But you need to configure the parameters manually to enable the functions.
NOTICE:
 After the U2000 is installed, you need to start the NBI-related process. Then, you can
configure the parameters.
 After initializing the database of the U2000, you need to configure the northbound interface
again.
 You can configure only one IP address for one network interface. It is not allowed to set
multiple IP addresses for the same network interface. It is suggested that configure multiple
network interface for multiple IP address.
 If the NAT is used to transform addresses between the NBI Config Tools server and clients,
log in the NBI Config Tools client that installed on the U2000 server. Otherwise, the
operation may be failed.
 The U2000 server and the OSS must can communicate with each other. Otherwise, the OSS
cannot interconnect with the NBI of the U2000. Therefore, if the U2000 server is configured
with multiple network interface cards (NICs) and the NICs are in different network segments,
set the IP address for connecting to the OSS as the IP address of the U2000 server.
 You must configure the northbound interface again after the IP of NMS changed.
NBI Config Tools

Through the GUI of the NBI Config Tools, you can conveniently deploy the northbound
interface.
The NBI Config Tools is a graphical maintenance tool developed for the northbound interface of
Huawei iManager U2000, a type of Huawei network product. The MSuite is used to configure
the northbound interface.
MSuite
The MSuite is a graphical maintenance tool developed for the Huawei iManager U2000, a type
of Huawei network product. The MSuite is used to debug, maintain, and redeploy the U2000.
For U2000 northbound interface, MSuite is used to update the security certificates.
Refer to the MSuite part of the iManager U2000 Administrator Guide for the details about the
MSuite.
Parent topic: Deploying and Configuring the Performance Text NBI
3.8.2 Configuration Requirements

configuration is required. However, you must purchase a license before using the Performance
Text NBI.
NOTE:
For different versions of the U2000, the configuration requirements are different. For details, see the Software
Installation Guide.
Hardware Configuration
configuration is required. The hardware must be capable to run the U2000 server.
For details about hardware requirements on the U2000 server, see "Configuration Requirements"
in the iManager U2000 Software Installation Guide.
Software Configuration
The Performance Text NBI is integrated with the U2000 installation software and no additional
software configuration is required when installing the Performance Text NBI.
For details about software requirements on the U2000 server, see "Configuration Requirements"
in the iManager U2000 Software Installation Guide.
License
The U2000 uses a license to control the functions and available resources of the Performance
Text NBI. To enable the Performance Text NBI, purchase a U2000 license first. Ensure that the
license support Performance Text NBI functions before deploying the Performance Text NBI.
For details about the license, see Checking the License. If the license does not support the functions
or desired resources, contact Huawei engineers to apply for a license. For details about the
license and its application flow, see Applying for and Updating the License in the iManager
U2000 Administrator Guide and the iManager U2000 License Instructions.
3.8.3 Configuration Workflow

To deploy the Performance Text NBI, check the license, configure the performance indicator
template, check whether the Performance Text NBI status, configure the NBI, and restart the
process. Configure the Performance Text NBI according to the check results.
After the U2000 is installed, you need to deploy the Performance Text NBI to generate the
NOTE:
The monitoring mode is different for equipment. For details, see Performance Management Process and Enabling
Performance Monitoring On the U2000 .
Figure 1 shows the process of deploying the Performance Text NBI.

Figure 1 Flowchart of deploying the Performance Text NBI
3.8.4 Checking the License

The U2000 controls the functions and available resources of the Performance Text NBI by the
license. Before using the Performance Text NBI, ensure that you have obtained its license and
ensure that the Performance Text NBI configurations in the license meet requirements.
Prerequisites
 The U2000 has been installed.

 The U2000 license has been loaded.
 The U2000 has NE management licenses and functions properly.
Context
NOTICE:
 A license for performance management system is required for performance monitoring on the
U2000.
 In U2000 capacity expansion, NBI licenses need to be expanded.
Procedure
1. Log in U2000 server.
 On the Windows OS, log in the U2000 server as the Administrator user.
 On the Solaris or Linux OS, log in U2000 server as the ossuser user.
2. Open the directory that contain License. Use the text viewer to view the contents of the
License file. For the relationships between the control items in the U2000 license file and the
Performance Text NBI functional items, see Table 1.
NOTE:
 On the Windows OS, the license file is %IMAP_ROOT%\etc\conf\license\LIC_ONxxxxxxx.dat.
 On the Solaris or Linux OS, the license file is $IMAP_ROOT/etc/conf/license/LIC_ONxxxxxxx.dat.
Table 1 Description for license items
License Control Item Abbreviation Value
Per Equivalent NE License for LNSDPENEF01 0~500000

NBI-FTP Performance-
Transmission Network
Per Equivalent NE License for LNSDPENEF02 0~500000

NBI-FTP Performance-IP
Per PON Terminal Resource LNSDNELCR91 0~8000000

License for NBI-FTP
Performance-Access Network
Per CMC NE Resource License LNSDPENEC50 0~800000

for NBI-FTP Performance-
Access Network
Compatible License for FTP LNSDNELCR81 0~800000

Performance NBI-Access
Network
Per Broadband Port License for LNSDPENEC30 0~800000

NBI-FTP Performance-Access
Network
Per Narrowband Port License for LNSDPENEC23 0~800000

NBI-FTP Performance-Access
Network
3. If the license does not support the function needed, contact Huawei engineers to apply for
the license. For the license introduction and information on how to apply for a license, see
section Applying for and Updating the License in the iManager U2000 Administrator Guide.
3.8.5 Logging in to NBI Config Tools

The NBI Config Tools is a graphical maintenance tool developed for the northbound interfaces
(NBIs) of iManager U2000. The MSuite is used to configure the NBIs.
Prerequisites
 The nbi_configtools and is_server processes are running.

 The desired NBI process is running.
NBI Type Process
CORBA NBI  Naming_Service

 Notify_Service
 Agent_CORBA
XML NBI  xmlagent

 ActiveMQ
SNMP NBI snmpagent
Performance text NBI textagent
NOTICE:
If you do not want to use the default SSL certificate provided by the NBI Config Tools, apply for
a secure certificate and replace the original certificate with the new one. For details, see Replacing
the Certificate of the NBI Config Tools .
NOTICE:
If you need to log in to NBI Config Tools through port mapping, change the default value of the
configuration item referer_check in the server configuration file
server\etc\oss_cfg\nbi\configtool\conf\config.properties to false. This operation may bring
your system security risks. Exercise caution when performing this operation.
Context
Browser requirement:
Browser Requirements
Internet Explorer  Version: Internet Explorer 8.0, Internet Explorer 9.0, Internet Explorer 10.0
 Security level: Medium or Low.
 Internet Explorer must use a more secure TLS protocol (such as TLS 1.1 and
TLS 1.2) and disables the SSL protocol (such as SSL 2.0 and SSL 3.0) and TLS
1.0.
1. In the Internet Explorer, choose Tools > Internet Options from the main
menu. The Internet Options window is displayed.
2. Select the Advance tab, in the Settings area, select Use TLS 1.1, Use TLS
1.2 and clear Use SSL 2.0, Use SSL 3.0 and Use TLS 1.0.
Procedure
1. Open Internet Explorer, enter the address of the NBI Config Tools server in the address bar,
and press Enter. The NBI Config Tools Login dialog box is displayed.
NOTE:
Enter the address of the server, for example, https://IP:13231. The IP is the IP address of the local server
computer in a centralized system or the IS server computer in a distributed system. 13231 is the port ID.
2. Enter the user name, password, and verification code, and click Login.
NOTE:
In a centralized system, the NBI Config Tools can be logged in to as the user of the U2000. That is, the default
user name is admin, and the password is the default password of admin.
In a distributed system, the NBI Config Tools can be logged in to as the user of the SSO system administrator.
That is, the default user name is ssoadmin, and the default password is Changeme_123.
3.8.6 Configuring a Performance Indicator

Template
The performance indicator template is an XML file that complies with the XML specifications.
You can enable performance monitoring on multiple indicators on the NMS, and export only the
performance text file for the required indicator. In this case, a performance indicator template is
required and indicators to be filtered are added to this template. For the U2000 V100R009C00
and later versions, you can use the NBI Config Tools to configure a performance indicator
template directly on the U2000 server. Alternatively, you can modify a performance indicator
template and import it into the U2000 server. One of the two modes must be performed.
Otherwise, the performance text file cannot be exported. It is recommended you use NBI Config
Tools to configure template. When upgrade with UExpert, the template will as same as the old
one. You must export the template from the source version U2000 then import it to the target
version if using other method to upgrade U2000.
Reference
 For details about indicators, see the iManager U2000 Performance Text NBI Performance
Event List.
 For details about mapping relationships between indicators and device types, see the
iManager U2000 Version Mapping.
 U2000 provide the performance indicator template with recommended indicators, see
iManager U2000 Performance Text NBI Performance Indicator Template.
The preceding documents are provided at http://support.huawei.com/. You can contact Huawei
engineers for these documents.
Access http://support.huawei.com/ and choose Support > Software > Fixed Network > SingleOSS-
FBB > SingleOSS-FBB > U2000 Common > iManager U2000. Then select the software
version and download the following packages.
 NBI Documents: includes the iManager U2000 Performance Text NBI Performance Event
List and iManager U2000 Performance Text NBI Performance Indicator Template.
 Common Documents: includes the iManager U2000 Version Mapping.
NOTE:
Select the corresponding base version if the patch version does not contain the preceding documents.
Indicator Description
The Performance Text NBI allows you to filter performance indicators according to indicator
IDs. Only indicators configured in the performance indicator template can export performance
data. In addition, you can redefine indicator names.
NOTICE:
 When you configure a performance indicator template for transport SDH or WDM equipment,
an offset of 1,000,000 must be added to the indicator ID. If the indicator ID in preceding
reference documents is 1, the indicator ID must be configured as 1,000,001 in the
performance indicator template.
 After an upgrade, the U2000 client may display different indicator IDs and indicator names.
For details, see the performance indicator lists for versions before and after the upgrade.
 To ensure NBI compatibility, the indicator names and indicator group names in the
performance text file must be the same as those before the upgrade. Therefore, the indicator
names and indicator group names exported in theperformance text file after the upgrade may
be different from those displayed on the U2000 client.
Indicator Group Description

The Performance Text NBI does not allow you to filter performance indicators according to
indicator group IDs.
Indicator groups for the Performance Text NBI have no relationship with those in reference
documents.
You can customize indicator group parameters for the Performance Text NBI, which include the
ID, name, and description, and assign different indicator groups for indicators.
NOTICE:
The user-defined indicator group ID cannot be left blank, and the indicator group name cannot
contain the following special characters: \/:*?"<>|;
 Indicator group ID: generating directory names listed in the third file export path. For details,
see File Export Path.
 Indicator group name: table heading information in the performance text file. For details, see
Description of File Format.
 Indicator group description: table heading information in the performance text file. For
details, see Description of File Format.
Restriction
NOTICE:
 Filter criteria must be specified between this pair of markers (<Filter></Filter>).
 The indicator group ID in the same filter template cannot be left blank.
 Indicator IDs support only alphanumeric letters and hyphens (-).
Procedure
 Configure the indicator template manually.
NOTE:
You can get the indicator template as the following. Here describes an example for empty template.
 The typical template provided in iManager U2000 Performance Text NBI Performance Event List.
 Export the template from the U2000 server that the Performance Text NBI have deployed in.
 Export the empty template from the U2000 server that the Performance Text NBI have not deployed in.
4. On the NBI Config Tools client, choose NBI > Configure Performance Text NBI from
the Main Menu. The dialog box is displayed.
5. On the General tab, click Export. After you choose the local path, click OK to save the
indicator template.
By default, the template name is indicator.xml. The default template is blank.
6. Navigate to a local directory and use a text editor to open the indicator.xml file.
7. Edit the indicator.xml file.
Table 1 describes definitions for XML labels.
Table 1 Definitions for labels in the performance indicator template
Label Description Example

The follow-up filter criterion is
commented out and invalid.
<Filter></Filter> All filter criteria are between -

this pair of markers.
<IndicatorGroup id="AAA" Indicates the information <IndicatorGroup id="PMS"

name="BBB" about the indicator group to be name="PMS Port RMON"
desc="CCC"></IndicatorGroup> exported. desc="PMS Port RMON
Performance">
AAA: indicator group ID, a
character string.
BBB: indicator group name, a
character string.
CCC: indicator group
description, a character string.
<Indicator id= Indicates the indicator ID to be <Indicator id=

"xXXX">YYY</Indicator> exported. "2">Memory
XXX: indicator ID, an integer. Usage</Indicator>
YYY: indicator name, a If the indicator ID of exported
character string. If this field is performance data is 2, the
left blank, use the default indicator name is renamed
value. Memory Usage.
For details about the indicator
ID and indicator name, see the
iManager U2000 Performance
Text NBI Performance Event
Table 1 Definitions for labels in the performance indicator template
Label Description Example
List.
Example
NOTE:
This template example consists of two indicator groups. In this example, performance data of the following
indicators is exported. Filter criterion for the indicator group whose ID is 10,000 is commented out and is
invalid.
Indicator groups with the ID of Basic Device:

 This indicator group includes indicators 1, 2, and 401.
 In the performance text file and the file name, the IndicatorGroupID field is Basic Device.
 In the performance text file, the Indicator Group Name field in the table heading is Basic Device
Group.
 In the performance text file, the Indicator Group Description field in the table heading is Basic
Device Performance.
Indicator groups with the ID of 7:

 This indicator group includes indicators 43, 44, 45, and 46.
 In the directory name the performance text file and the file name, the IndicatorGroupID field is 7.
 In the performance text file, the Indicator Group Name field in the table heading is UDP Delay and
Packet Loss.
 In the performance text file, the Indicator Group Description field in the table heading is UDP Delay
and Packet Loss.
<?xml version="1.0" encoding="UTF-8"?>

<Filter xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3school.com.cn file:///">


<IndicatorGroup id="Basic Device" name="Basic Device Group"
desc="Basic Device Performance">
<Indicator id="1">CPU Usage</Indicator>
<Indicator id="2">Memory Usage</Indicator>
<Indicator id="401">Static Active Route Numbe</Indicator>
</IndicatorGroup>
<IndicatorGroup id="7" name="UDP Delay and Packet Loss" desc="UDP
Delay and Packet Loss">
<Indicator id="43">Avg. Delay</Indicator>
<Indicator id="44">Packet Loss Ratio</Indicator>
<Indicator id="45">Min. Delay</Indicator>
<Indicator id="46">Max. Delay</Indicator>
</IndicatorGroup>
</Filter>
9. On the General tab, click Import. Choose the modified template, and click Open to
import the indicator template.
 Configure the indicator template by NBI Config Tools. Alternatively, you can import the
indicator template then modify the template by NBI Config Tools.
NOTE:
For the U2000 V100R009C00 and later versions, you can use the Modify function of NBI Config Tools to
configure a performance indicator template directly on the U2000 server. You need not to import the indicator
template.
1. Click Modify, choose the required indicator in the dialog box.
2. Choose the required indicator in the navigation tree.
If Then
There is no Existing Template. Indicates there is no template in U2000 server. Click PMS
Indicators or Transport Indicators, expand the indicator node,
and select the indicators that belong to the indicator group.
There is Existing Template. Indicates there is no template in U2000 server. You can do the
following operations.
 To insert the indicator groups or indicators, right-click the
If Then
indicator group or indicator in the Existing Template and

choose Insert Indicators Before the Node or Insert
Indicators After the Node from the shortcut menu.
 To customize the attributes of indicator group or indicator,
right-click the indicator group or indicator in the Existing
Template and choose Modify from the shortcut menu. You
can not modify the indicator ID.
 Select the indicators in PMS Indicators or Transport
Indicators, the selected indicators will add in the current
template.
NOTE:
 For PMS indicators, the GUI displays the indicators that belong to the existing performance monitoring
template only. You must create a performance monitoring template with the indicators to be monitored
on the U2000 client if you cannot find the indicators.
 You can insert indicators of one indicator group at one time.
 You must set the indicator sequence carefully. The indicator sequence in the GUI is the same as the
indicator sequence in the performance text file. The OSS may be unable to parse the performance text
file because of the modification of the indicator sequence.
3. Click OK.
Follow-up Procedure
 After configure the template manually, you need to import the template to U2000 server. For
details, see Configuring the Performance Text NBI.
 You need to import the template to U2000 server if configure the template by NBI Config
Tools.
3.8.7 Configuring the Performance Text NBI

After the U2000 is installed, to enable the Performance Text NBI, you need to set the
Performance Text NBI parameters according to the NMS plan.
Prerequisites
 The NBI maintenance tool is running normally.

 After the U2000 is installed, the Performance Text NBI process is not running by default. You
have started the textagent process manually.
 The U2000 license includes the Performance Text NBI functions.
Procedure
1. Log in to NBI Config Tools. For details, see Logging in to NBI Config Tools .
2. On the NBI Config Tools client, choose NBI > Configure Performance Text NBI from the
Main Menu. The dialog box is displayed.
3. In the General area, set parameters for the export time.

 If you need to export performance data in a single period, select Single period and set the
parameters.
 If you need to export performance data in multiple periods, select Multi-period, click
Configure Multi-Period Export, and set parameters in the displayed dialog box.
Figure 1 shows the relationships between the collection period, data export period, data export
duration, and export start time. You are advised to set the export start time to be the same as
the performance event start time. If the export start time is later than the performance event
start time, the time for generating a performance file is delayed.
Figure 1 Data export duration
Table 1 Parameters for the export time
Parameter Description Value
Duration Setting Indicates the export duration mode. Auto, Manual
Collection Period (min) The Performance Text NBI classifies 5, 10, 15, 30, 60, 360, and 1440
the performance data by collection minutes
period, and you can export the data
by the period.
Data Export Period (min) Indicates the interval for exporting 5, 10, 15, 30, 60, 360, and 1440
data through the Performance Text minutes
NBI. You can customize this
parameter and are advised to set the
data export period as same as the
correspond collection period.
Data Export Duration Indicates the duration for exporting When Duration Setting is Manual,
(min) data on the device to the you need to set Data Export
performance text file. Duration manually.
NOTICE:
Table 1 Parameters for the export time
If the data export duration is incorrectly

configured, the performance text file
cannot be generated. Set this parameter
by following Table 2 and Table 3.
Export Start Time Indicates the first time when data is yyyy-mm-dd hh:mm:ss
exported. Do not set the export start For example: 2009-09-01 01:00:00
time to any time between 23:00:00
and 01:00:00. Otherwise, a data error
will occur due to DST switching.
Click .... Set the export start time in
the displayed dialog box.
4. Configure the export duration.

 Select Auto. The Performance Text NBI sets the delay time automatically.
 Select Manual. You need to set the data export duration manually as follows.
NOTICE:
The data export duration is related to the device type. Therefore, exercise caution when
setting this parameter. Table 2 and Table 3 show the recommended values.
If there are multiple equipment types, set the parameters to the maximum value.
For details about the device type, see the U2000 Product Description.
Transport NEs only support 15-minute and 24-hour performance data collection. When the
collection period is set to 15 minutes, modify the transport performance saving duration as
follows if the configured file export delay is greater than 1 hour:
c. Enter the server/etc/oss_cfg/trans/core/conf directory.
d. Specifically, set the configuration item PfmCollFilesReserve in trans_ems.cfg file to a
value greater than the result of (File export delay/15+1). For example, if the file export
delay is 120 minutes, set the value of PfmCollFilesReserve to 9.
#| Specify how long in minutes the performance files will be reserved.
PfmCollFilesReserve = 9
Table 2 Data export duration (min) with 50,000 performance instances
Collection IP/PTN6900/PTN7900 SDH/MSTP/WDM/OTN/RTN600 PTN900/PTN1900/PTN3900/RTN300/RTN90

Period RMON Common (Non-
(min) RMON)
5 35 - - -
10 40 - - -
15 45 60 45 60
30 60 - - -
60 90 - - -
360 - - - -
1440 1470 1470 1470 1470
Table 3 Data export duration (min) with 50,000 to 150,000 performance instances
Collection IP/PTN6900/PTN7900 SDH/MSTP/WDM/OTN/RTN600 PTN900/PTN1900/PTN3900/RTN300/RTN90

Period
(min) RMON Common (Non-
RMON)
5 - - - -
10 - - - -
15 45 60 45 60
30 60 - - -
60 90 - - -
360 - - - -
1440 1470 1470 1470 1470
5. Configure the performance indicators to be exported. As Table 4 shown, three modes are
supported.
NOTICE:
 You must import the template with valid data or configure the template by NBI Config
Tools. In addition, the indicator group ID in the performance file template to be imported
cannot be left blank. Otherwise, the performance text file cannot export. It is suggested
that you import the typical template then modify it by NBI Config Tools to fulfill the
requirement.
 For details about the indicator template, see Configuring a Performance Indicator Template .
 Manually configuring indicator filter templates is complex. Using the templates provided
by the U2000 is recommended. For details, see the iManager U2000 Performance Text
NBI Performance Indicator Template.
Table 4 Configuration Mode
Configuration Description
Mode
Full Import Indicates import the indicator template to U2000 server. The template will replace
the old template in U2000 server. The performance text file export with the new
template.
Incremental Import Indicates import the indicator template to U2000 server.

 If there is an old template in the U2000 server, the new indicators in the new
template will add in the old template.
 If there is an old template in the U2000 server, the performance text file export
with the new template.
NOTE:
An incremental import does not affect the sequence of the existing indicators in the
template.
An incremental import does not delete existing indicators from the template.
Modify Configure the indicators in the template.

 If there is no indicator template in U2000 server, select the required indicators
then create the new template.
 If there is a indicator template in U2000 server, you can modify the current
template.
Table 5 Scenes and Operations
Scenes Operations
Deploy the Performance 7. Obtain the typical template from iManager U2000Performance Text
Text NBI in U2000 for NBIPerformance Indicator Template.
the first time. 8. Click Import.
9. Set the Import Mode to Full Import, click Browse to choose the
template, and then click Open to import the typical template to U2000.
10. Click OK. In the dialog box that is displayed, click OK to complete the
template import.
11. Check the imported indicators, and click OK.
12. Optional: Click Modify to modify the template, and choose the required
indicators and delete the unnecessary indicators.
Table 5 Scenes and Operations
Scenes Operations
Alternatively, you can click Modify to create a new template.
After upgrade, the After upgrade, the template is as same as the prior version, you need not to do
monitored indicators any operations.
have not changed.
After upgrade, the 13. After upgrade, the template is as same as the prior version.
monitored indicators 14. Click Modify to modify the template, choose the required indicators and
have changed. delete the unnecessary indicators.
Figure 2 Modify Indicators
6. Optional: If you have already configured the performance indicators on the server, click
Export to download the performance indicator file. Then you can import the template to
otherU2000s.
7. Optional: In the File Export area, set the file export directory and the FTP server
parameters. If you need to upload the performance text file to a specified FTP or SFTP
server, set parameters listed in Table 6.
NOTICE:
 When you log in to the NBI Config Tools server remotely, you need to enter the export
directory manually. Ensure that the directory is correct.
 SFTP is recommended for security.
Table 6 Parameters for FTP or SFTP settings
Export Directory Indicates the directory for storing the Example: U2000 INSTALL
performance text file on the local computer. PATH/server/nbi/text/pfm_output.
NOTICE:
The NBI Config Tools GUI hides the U2000 server
installation path. You can set Export Directory to
any directory under the U2000 installation path.
The default directory is U2000 INSTALL
PATH/server/nbi/text/pfm_output
If the OPENSSH or a third-party plug-in is

used, the export directory must be an
authorized directory of the OPENSSH or plug-
in.
Ensure that user ossuser has sufficient
permission (read, write, and execute) for the
configured export directory.
Export To Indicates the upload mode of the performance  Export to local server
text file.  Export to remote FTP/SFTP
 Local server: The performance text file is server
stored on a local FTP server. The OSS
obtains the files by accessing the local
server in FTP mode.
 Remote FTP server: The performance text
file is directly uploaded to a specified
remote FTP server in FTP mode.
NOTE:
 If the value of this parameter is set to Remote
FTP server, the system records operation logs
by Data Export Period. To query operation
logs, choose System > Log Management >
Query Operation Logs on the U2000 client.
 This is the directory for saving the performance
text file. You need to set this directory as the
FTP directory.
When Export To is set to Remote FTP server, you need to set the following FTP parameters.
FTP Mode Indicates the type of the FTP protocol that is FTP, SFTP
Table 6 Parameters for FTP or SFTP settings
used. For example, FTP or SFTP. Default: SFTP
FTP/SFTP Server Indicates the IP address of the OSS FTP/SFTP IP address

IP Address server.
NOTE:
Do not set the IP address of the U2000 server to
the IP address of the FTP/SFTP server, because the
uploaded performance text files will not be
automatically deleted, causing insufficient hard
disk space of the U2000 server.
FTP/SFTP Port Indicates the port ID of the OSS FTP/SFTP Default: 22

server.
FTP/SFTP User Indicates the user name for visiting the OSS N/A
Name FTP/SFTP server.
FTP/SFTP Indicates the password for visiting the OSS N/A

Password FTP/SFTP server.
FTP/SFTP Indicates the destination address of the OSS N/A

Directory FTP/SFTP server for data uploading.
SFTP Certificate Indicates the SFTP certificate. You need to Absolute directory/SFTP key file
enter the right SFTP key in the SFTP key
authentication mode.
NOTE:
 Before using the FTP protocol, you need to configure the FTP server. For details, see Configuring the FTP
Server.
 If you need to use the SFTP protocol, enter the correct file directory and file name for the SFTP key file.
8. In the Advanced area and set the advanced parameters. Generally, advanced parameters are
optional (default values are recommended). Advanced parameters are independent of each
other and no configuration order is required.
. Set the filter criteria for exporting product log files.
Table 7 Log file
Item Description Value
Max. Logs Indicates the maximum number Range: 10 to 20

of log files that can be exported at Default Value: 20
a time.
Max. Log Size Indicates the maximum size of Range: 5 to 20 MB

log files that can be exported at a Default Value: 20 MB
time.
Log Level Indicates the log level. Logs are  Debug

classified into four levels, such as  Information (Default)
debugging, information, warning,  Warning
and error, based on the log
 Error
importance.
This item is used to set the lower
level threshold of log files that
can be exported. Log files of a
level lower than this threshold are
not recorded.
a. Set the encoding format of the performance text file.
Table 8 Encoding format
Encoding Format Indicates the encoding format.  UTF-8 (Default)

There are three encoding formats.  GBK
Table 8 Encoding format
 GB2312
b. Set the time format of the performance text file.
Table 9 Time format
Time Format Indicates the time format. Two time formats are  UTC time (default)
available.  Local time
Setting the time format affects the name of exported
files. For details, see File Naming Rule.
c. Set the other parameters listed in Table 10.
Table 10 Parameters for other settings
Max Records in File Indicates the maximum number of records Default value: 100000
that a file can contain.
When the number of records is larger than
this value, new records are saved in another
file.
SN of the new file = SN of the existing file +
1.
Save Export File For Indicates the duration for saving the exported Default value: 3 days
files on the local server.
Delete Historical File On Indicates the start time of a scheduled task for Year-Month-Day hour:
deleting a file. This time is the server time. minute: second
For example, 2009-09-01
15:50:00
Decompressing Specifies whether to compress performance  YES

Performance Files Before files to packages in .gz format before the  NO (default)
Upload performance files are uploaded.
9. Click Save, the dialog box displayed prompt restart the NBI processes for the updates to take
effect. Click OK, the dialog box displayed prompt successfully saved. Click OK to complete
the configuration.
NOTICE:
If you click Cancel in the dialog box displayed prompting you to restart the NBI processes
for the updates to take effect, the user configurations are saved only on the configuration
page but not applied to the configuration file. In this case, the configurations will not take
effect even after the related NBI process is restarted.
10. Log in to the System Monitor. For details, see iManager U2000 Administrator Guide.
11. On the System Monitor client, check Status of the textagent process. If the process is in the
Running state, the Performance Text NBI is enabled successfully.
3.8.8 Check the Performance Text File

After deploying the Performance Text NBI and enabling the performance monitoring on the
U2000, you need to check whether the performance text file is generated successfully to
determine the running status of the Performance Text NBI.
Prerequisites
 The Performance Text NBI is deployed.
 Monitoring instances are created or performance event monitoring is enabled.
Procedure
1. According to the Data Export Period, wait for a certain period of time (one period plus file
export delay).
For example, if Data Export Period is 15 minutes, wait for 35 to 50 minutes.
2. Log in to the U2000 server, and navigate to the directory for the performance text file
according to the Export Directory.
For example, if the export directory is /opt/oss/server/nbi/text/pfm_output, open a terminal
and enter the following command to navigate to the directory.
# cd /opt/oss/server/nbi/text/pfm_output
3. Check whether the associated directory structure and *.csv files are generated.
NOTE:
If no exported directory is generated or no CSV files are generated in the generated exported directed, file
export fails. For details, see the FAQs.
4. Open the *.csv files and view data.
3.8.9 Configuration Examples

This topic describes the procedure for enabling performance monitoring on the U2000,
deploying the Performance Text NBI, and obtaining the performance text file using examples.
Two different configuration examples are provided based on the different ways of enabling
performance monitoring on the U2000.
 Configuring Transport Performance Events

Most transport performance events are managed by NE management processes except RMON
performance events. This topic describes the procedure for configuring transport performance
monitoring and obtaining the performance text file.
 Configuring PMS Performance

The performance management system (PMS) manages performance of IP, access, security, PTN
NEs and RMON performance of transport NEs. This topic describes how to monitor
performance indicators managed by the PMS on the U2000, deploy the Performance Text NBI,
and generate the performance text file.
3.8.9.1 Configuring Transport Performance

Events
Most transport performance events are managed by NE management processes except RMON
performance events. This topic describes the procedure for configuring transport performance
monitoring and obtaining the performance text file.
 Description for Configuration Examples

This topic describes the networking scenario and data plan for a transport performance
configuration example.
 Enabling Performance Event Monitoring

For performance events managed by transport NE management process, you need to enable the
performance event monitoring on the U2000.

This topic describes how to configure the Performance Text NBI to generate the performance
text file after performance event monitoring is enabled.
Parent topic: Configuration Examples
3.8.9.1.1 Description for Configuration

Examples
This topic describes the networking scenario and data plan for a transport performance
configuration example.
Networking Scenario
As shown in Figure 1, the U2000 monitors performance data on the 12-N1SL16 board of NE 1
and NE2 and the Performance Text NBI generates a performance text file based on collected
performance data and saves this file to the U2000 server. The U2000 functions as the FTP server
(IP address: 10.71.224.13; port number: 21). The OSS logs in to the U2000 server as a client
(user name: u2000; password: u2000ftp) and obtains the performance text file in the related
directory.
Figure 1 Network topology
Data Plan
The Table 1 lists data plan for performance event monitoring.
Table 1 Data plan for performance event monitoring
Item Data
NE Type OptiX OSN 3500
Monitoring Object 1 NE1-12-N1SL16
Monitoring Object 2 NE2-12-N1SL16
Performance Event  Transmitted Optical Power of Local Transmitter

Type  Received Optical Power of Local Receiver
Performance 15 minutes
Monitoring Period
The Table 2 lists the parameter planning for the Performance Text NBI.
Table 2 Data plan for the Performance Text NBI
Item Data
Collection Period 15 minutes
Data Export Period 15 minutes
Data Export Duration 45 minutes
Export Indicator TPLCUR (current output optical power of the laser), TPLMAX (maximum
output optical power of the laser), and TPLMIN (minimum output optical power
of the laser)
RPLCUR (current input optical power of the laser), RPLMAX (maximum input
optical power of the laser), and RPLMIN (minimum input optical power of the
laser)
Export Directory /opt/oss/server/nbi/text/pfm_output
Export Option Export to a local server.
The Table 3 lists the parameter planning for the FTP server.
Table 3 Data plan for the FTP server
Item Data
IP Address 10.71.224.13
Port 21
User Name ftpuser
Password Changeme_123
NOTICE:
To ensure the security of the U2000, remember to change the default passwords of U2000 and
update the passwords regularly, passwords must be complex enough.
The password must meet the following requirements to safeguard your user account.
1. It is a character string consisting of 8 to 16 characters.
2. It contains at least four types of the following characters:
 Lowercase letter: a-z
 Uppercase letter: A-Z
 Digit: 0–9
 Special character: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ | [ { } ] ; : ' " , < . > / ? or space.
Parent topic: Configuring Transport Performance Events
3.8.9.1.2 Enabling Performance Event

Monitoring
For performance events managed by transport NE management process, you need to enable the
performance event monitoring on the U2000.
Procedure
1. Optional: Synchronize NE data for NEs. In the Main Topology, right-click the required NE
from the Physical Root navigation tree and choose Synchronize NE Data from the shortcut
menu.
2. Optional: Synchronize NE time.
b. Select NE1 and NE2 from the object tree and click .
c. Click Close in the dialog box that is displayed.
d. Select NE1 and NE2 in the list and click Synchronize with NM Time.
e. Click Yes in the dialog box that is displayed. Click Close in the Operation Result
dialog box.

b. Select NE1 and NE2 from the object tree and click .
NOTE:
The start time should be later than the current time on the U2000.
d. Click Apply.
4. Enable performance monitoring status by template.

a. Choose Performance > Performance Template Management > Performance Event
Monitor Status Template (traditional style) from the main menu or select Fix-
Network Performance in Application Center and choose Performance Monitoring >
Performance Template Management > Performance Event Monitor Status
Template (application style) from the main menu.
b. In the Performance Event Monitor Status Template window, set the Monitor Status
and 15-Minute Auto-Report of Transmitted Optical Power of Local Transmitter
and Received Optical Power of Local Receiver to Enabled.
c. Click Save As and set the template name to optical_power.
d. Click Apply To. In the dialog box that is displayed, select the 12-N1SL16 board of NE1
and NE2 from the object tree and click OK.
e. The Operation Result dialog box is displayed, indicating that the operation is
successful. Then click Close.
5. Optional: Enable performance monitoring status by NE explorer.
a. In the NE explorer of NE1 or NE2, select the board 12-N1SL16 to be monitored, and
choose Function Tree > Performance > Performance Monitoring Status.
b. Enable the Monitor Status and 15-Minute Auto-Report of the performance event to be
monitored.

This topic describes how to configure the Performance Text NBI to generate the performance
text file after performance event monitoring is enabled.
Prerequisites
The performance event monitoring is enabled on the U2000.
Procedure
1. Enable the function of exporting transport performance data.
NOTE:
To export the performance text file for transport performance events, modify the trans_ems.cfg file and restart
the related NE management process.
a. Navigate to the server/etc/oss_cfg/trans/core/conf directory.
b. Set the following parameter in the trans_ems.cfg configuration file to 1 (Enable). The
default value is 0 (Disable).
c. #| Whether to Save 15min Performance Logs to Files, Instead of Database
(1-Enable, 0-Disable) bSavePfmLog15mToFile = 1
d. Log in to the System Monitor client. Then restart the associated NE management
process based on objects on which performance data is collected.
2. Configure parameters for the Performance Text NBI.
a. On the NBI Config Tools client, choose NBI > Configure Performance Text NBI
from the Main Menu. The dialog box is displayed.
b. In the General area, set basic configuration parameters.
In this example, Single period is selected, because only performance data of a 15-
minute collection period needs to be exported.
 Collection period: 15 minutes
 Data export period: 15 minutes
 Data export duration: 45 minutes
 Export directory: /opt/oss/server/nbi/text/pfm_output
 Export option: export to a local server
 Indicator Setting: Select the indicator_MSTP_Common.xml performance indicator
template from the iManager U2000 Performance Text NBI Performance Indicator
Template.zip file and edit the template. Specifically, retain only the following
indicators:
 TPLCUR
 TPLMAX
 TPLMIN
 RPLCUR
 RPLMAX
 RPLMIN
c. Click Save, the dialog box displayed prompt restart the NBI processes for the updates to
take effect. Click OK, the dialog box displayed prompt successfully saved. Click OK to
complete the configuration.
3. The OSS logs in to the U2000 as an FTP client and obtains the performance text file. First
create an FTP user for the OSS on the U2000 and set a password.
 User name: ftpuser_oss
 Password: Changeme_123
 Root directory: /opt/oss/server/nbi/text/pfm_output
d. Log in to the Solaris OS as user root.
e. Open a terminal window and run the following commands:

f. # useradd -u 1000 -g ossgroup -d /opt/oss/server/nbi/text/pfm_output -m
ftpuser_oss
g. # passwd ftpuser_oss
h. New password:Changeme_123
i. Re-enter new password:Changeme_123
NOTE:
 In preceding commands, 1000 is the user ID. The user ID begins with 1000. Use 1001, 1002, or a
larger number as the user ID if 1000 has been used.
 The name of the user created by running the useradd command can be customized. If the created user
'ftpuser_oss' already exists on the U2000, you can change the user name and create the user again.
 Ensure that new users have read permission on the export directory of the performance text file.
 To ensure the security of the U2000, remember to change the default passwords of U2000 and update
the passwords regularly, passwords must be complex enough.
After the procedure is complete, the OSS can log in to the U2000 server with the user name
of ftpuser_oss. The root directory is /opt/oss/server/nbi/text/pfm_output. The OSS can
directly read the performance text file exported and saved in this directory.
3.8.9.2 Configuring PMS Performance

The performance management system (PMS) manages performance of IP, access, security, PTN
NEs and RMON performance of transport NEs. This topic describes how to monitor
performance indicators managed by the PMS on the U2000, deploy the Performance Text NBI,
and generate the performance text file.
 Description for Configuration Examples

This topic describes the networking scenario and data plan for a PMS performance configuration
example.
 Creating a Performance Monitoring Instance

Performance monitoring instances are required to collect performance data for performance
managed by the PMS.

This topic describes how to configure the Performance Text NBI to generate performance data
files.
Parent topic: Configuration Examples
3.8.9.2.1 Description for Configuration

Examples
This topic describes the networking scenario and data plan for a PMS performance configuration
example.
Networking Scenario
As shown in Figure 1, the U2000 monitors CPU usage and memory usage of routers A, B, and C.
The Performance Text NBI processes the intermediate files generated by the PMS and generates
the performance text file. The OSS functions as an FTP server (IP address: 10.71.224.24; port
number: 21). The U2000 logs in to the OSS server as an FTP client (user name: ftpuser;
password: Changeme_123) and uploads the performance text file.
Figure 1 Network topology
Data Plan
The Table 1 lists the data plan for performance monitoring.
Table 1 Data plan for performance monitoring
Item Data
NE Type NE40E
Monitoring object Router A, Router B, and Router C
Performance CPU Usage

Indicator Memory Usage
Performance 5 minutes
Monitoring Period
The Table 2 lists the parameter planning for the Performance Text NBI.
Table 2 Parameter planning for the Performance Text NBI

Item Data
Collection Period 5 minutes
Data Export Period 5 minutes
Data Export Duration 35 minutes
Export Indicator CPU Usage

Memory Usage
Export Directory /opt/oss/server/nbi/text/pfm_output
Export Option Export to remote FTP server
The Table 3 lists the parameter planning for the FTP server.
Table 3 Data plan for the FTP server
Item Data
IP Address 10.71.224.24
Port 21
User Name ftpuser
Password Changeme_123
Upload Directory /ftptext/pfm_output/
NOTICE:
 Digit: 0–9
Parent topic: Configuring PMS Performance

3.8.9.2.2 Creating a Performance Monitoring
Instance
Performance monitoring instances are required to collect performance data for performance
managed by the PMS.
Prerequisites
 Users have the license to create a monitoring instance.
 The SNMP protocol version is SNMP v2c or later versions for creating NEs. Otherwise, the
U2000 cannot successfully collect performance data.
Procedure
1. Synchronize NE time. In the Main Topology, right-click the required equipment in the
Physical Root navigation tree and choose Set NE Time from the shortcut menu.
NOTE:
Synchronizing NE time takes some time. Please wait.

Close
3. Create data monitoring template.
a. Choose Performance > Performance Template Management > Performance

Monitor Template (traditional style) from the main menu or select Fix-Network
Performance in Application Center and choose Performance Monitoring >
Performance Template Management > Performance Monitor Template (application
style) from the main menu.
b. Choose NE > Router/Switch/MA/ME NE > Router and Switch NE from the

navigation tree, and click Create.
c. In the Template Name text box, enter the name of the data monitoring template. For
example, CPU_Memory.
d. Choose the performance indicators to be monitored. For example, select CPU Usage
and Memory Usage in Basic Device Indicators group.
NOTE:
You can filter indicators according to equipment types by clicking Filter.
e. Click OK.
4. Create performance monitoring instances.
a. Choose Performance > Performance Monitoring Management (traditional style)

choose Performance Monitoring > Performance Monitoring Management
b. Choose NE > Router/Switch/MA/ME NE > Router and Switch NE from the

navigation tree, and click Create. The instance creation wizard is displayed.
c. Select the objects to be monitored. In the Available Resources area, select target
resources and click to move the selected resources to the Selected Resources
area.
d. Click Next to select the data monitoring template and granularity. For example:
 Data Monitoring Template: CPU_Memory

 Granularity: 5 Min
e. Click Next to configure time information.
NOTE:
Retain the default time settings, which means that data collection starts immediately after the instances are
created and the performance monitoring is enabled.
f. Click Next to display the progress and result of instance creation.
g. Click Finish.
h. Query the instance in the Performance Monitoring Management window. If

Monitoring Status is Running, the instance is created successfully.
5. Optional: View the real-time performance. Right-click the instance (NE40E-
92_5_CPU_Memory in this example) and choose Real Time Monitoring from the shortcut
menu. You can view the real-time performance of CPU Usage and Memory Usage.

This topic describes how to configure the Performance Text NBI to generate performance data
files.
Prerequisites
 You have created a performance monitoring instance on the U2000.

 The FTP server is functioning properly.
Procedure
1. Log in to NBI Config Tools. For details, see Logging in to NBI Config Tools .
2. On the NBI Config Tools client, choose NBI > Configure Performance Text NBI from the
Main Menu. The dialog box is displayed.
3. In the General area, set basic configuration parameters.
In this example, Single period is selected, because only performance data of a 5-minute
collection period needs to be exported.
 Collection period: 5 minutes
 Data export period: 5 minutes
 Data export duration: 35 minutes
 Export option: export to a remote FTP server
 FTP mode: FTP
 IP address for the FTP/SFTP server: 10.71.224.24
 FTP/SFTP port number: 21
 FTP/SFTP user name: ftpuser
 FTP/FT password: Changeme_123
 FTP/SFTP upload directory: /ftptext/pfm_output/
 Indicator Setting: Select the indicator_RouterAndSwitch.xml performance indicator
template from the iManager U2000 Performance Text NBI Performance Indicator
Template.zip file and edit the template. Specifically, retain only two indicators: CPU
usage and memory usage.
4. Click Save, the dialog box displayed prompt restart the NBI processes for the updates to take
effect. Click OK, the dialog box displayed prompt successfully saved. Click OK to complete
the configuration.
Result
The configuration will take effect after 15 minutes.
3.9 Obtaining the Performance Text File

The Performance Text NBI records performance data monitored by the U2000 in a unified
format and saves the data. The OSS needs to obtain and parse these files to analyze network
health status, provide optimization suggestions, and locate faults for troubleshooting. You can
customize parameters such as path for generating these files and export fields as required. In
addition, the Performance Text NBI provides a fault tolerance mechanism to collect data for the
previous period and generate a file in the current period.
NOTICE:
 Configure the Performance Text NBI using the NBI Config Tools properly before obtaining
the performance text file.
 For performance of SDH, WDM, and OTN devices, stop the NE management process on the
System Monitor client and restart the service for the configuration to take effect.
 File Export Path

The Performance Text NBI generates three types of file directories based on different
configuration files.
 File Naming Rule

To facilitate management, a fixed rule is used to name the performance text file.
 Description of File Format

The performance data file generated by the Performance Text NBI records performance in a
fixed format. The performance text NBI parses the fields in the following table heading and
obtains required performance data.
 Setting Fields to Be Exported

This topic describes how to set fields to be exported for the performance text file. In the
PMExport.xml file, set the configuration item CsvHead to define fields to be exported to the
 Ensuring Data Integrity of Performance Text Files

During the generation of a performance text file, performance data may be incomplete or the
performance file fails to be generated due to an exception. The Performance Text NBI is able to
automatically detect such an exception and generates the related data in a file in the next period.
 Parsing Principle and Restriction

When parsing the performance text file, you need to keep version compatibility and flexibility.
This topic describes the parsing principles and restrictions during software development.
3.9.1 File Export Path

The Performance Text NBI generates three types of file directories based on different
configuration files.
In the PMExport.xml file, modify the FileGenMode parameter to define the structure of a file
directory for saving the exported performance text file.
NOTE:
The PMExport.xml file is saved in the following paths:
 Windows: %IMAP_ROOT%\etc\nbi\text.
 Solaris and Linux: $IMAP_ROOT/etc/nbi/text.
The default root directories for the exported performance text file are as follows:
 Window: %IMAP_ROOT%\nbi\text\pfm_output.
 Solaris and Linux: $IMAP_ROOT/nbi/text/pfm_output.
Table 1 Description of the configuration item for setting the structure of the file directory
Configuration Mode Sample Description

Item
FileGenMode Mode <FileGenMode>1</FileGenMode> Subdirectories are generated based on

1 the export date. This mode is the
same as that of the U2000
V100R001C00.
This is the default mode.
Mode <FileGenMode>2</FileGenMode> Files are exported directly to the root

2 directory.
Mode <FileGenMode>3</FileGenMode> The file directory structure is as

3 follows: indicator group
ID/collection period/date/time. (IG
ID/Interval/date/time)
This mode is not recommended.
Ensure that the indicator group ID is
not blank in indicator filter templates.
Mode 1
As shown in Figure 1, the performance text file is exported to the directory named by Date.
Performance data of the same day is exported to the same directory.
Figure 1 Sample directory in mode 1
Mode 2
As shown in Figure 2, the performance text file is exported to the root directory.
Mode 3
As shown in Figure 3, the directory name for exported files contains Indicator ID, Collection
Period, Date, Time in sequence.
Parent topic: Obtaining the Performance Text File
3.9.2 File Naming Rule

To facilitate management, a fixed rule is used to name the performance text file.
The performance text file is named as follows:
 Non-blank indicator group ID in the indicator filter template:
PM_IGIndicatorGroupID_Granularity_Timestamp_SerialNumber.csv
 Blank indicator group ID in the indicator filter template:
PM_Granularity_Timestamp_SerialNumber.csv
Table 1 File naming rules
Field in the File Name Description
PM_ Indicates the fixed prefix.
IGIndicatorGroupID Indicates the Indicator group ID. It is the Indicator Group ID field set in
the indicator filter template. If the Indicator Group ID field is left blank,
this field does not exist.
Granularity Indicates the performance data collection granularity.
Timestamp Indicates the end time of performance data collection. The format of this
field is yyyymmddhhmmZ, in which Z indicates the UTC time. If there is
no Z in this format, this field indicates the local time.
SerialNumber Indicates the serial number of the file. This field is used to prevent oversize
of the performance text file. The value of this field begins with 01. If the
number of performance data records in a file exceeds the preset value, a
new file is generated and the field is increased by one.
For details about the maximum records in a single file, see the advanced
settings in the Configuring the Performance Text NBI.
For example, the following is a name for the performance text file:
PM_IG500012_15_200911281100Z_01.csv
3.9.3 Description of File Format

The performance data file generated by the Performance Text NBI records performance in a
fixed format. The performance text NBI parses the fields in the following table heading and
obtains required performance data.
The format of the performance text file is CSV. Table 1 and Table 2 show the heading and its
description of a performance text file.
Table 1 Heading in the file

Indicat Indicator Collectio Number of
or Group n End Data
Group Descriptio Time Records
Name n
DeviceI DeviceNa Resource ResourceNa CollectionTi GranularityPer Indicat Indicat ..

D me ID me me iod or or .
name1 name2
... ... ... ... ... ... ... ... ..

.
Table 2 Description of each field in the heading
Ref Attribute Name Data Format Description Example
H.1 Indicator Group String Indicates the indicator RS Bit Error

Name group name. You can
customize it.
H.2 Indicator Group String Indicates indicator RS Bit Error

Description group description. You
can customize it.
H.3 Collection End Time Datetime Indicates the result of 2009-11-28 10:00:00
export begin time minus
the file export duration.
For example, if the
export task begins at
2010-10-10 10:00 and
the export duration is 20
minutes, the collection
end time is at 2010-10-
10 09:40.
H.4 Record Number Number Indicates the number of 6

data records in this file.
H.5 DeviceID Number Indicates device ID (NE 3145897

ID). It is unique on the
entire network managed
by the U2000.
H.6 DeviceName String Indicates device name OptiX RTN 910

(NE name). All NEs are
named on the U2000.
H.7 ResourceID String Indicates resource ID. It NE = 3145897, S = 8,

is used to locate the CP = -1, PP = ||1|
Table 2 Description of each field in the heading
Ref Attribute Name Data Format Description Example
position of performance.
The specific rule is that
a multi-level ASCII
character string table
with separators is used.
For example, the format
of a physical port is NE
= 1234, FR = 1, S = 1,
PP = 12.
NOTICE:
This field is not displayed
by default.
H.8 ResourceName String Indicates the resource NE = 350, board =

name. It defines the EG16, and port = 4
location of performance.
You can find the
location through the
U2000.
H.9 CollectionTime Datetime Indicates the end time of 2009-11-28 17:30:00

performance collection.
H.10 GranularityPeriod Number Indicates the granularity 15

of performance
collection.
H.11 Indicator name1 String Indicates indicator Regenerator section

names. One indicator background error
group contains multiple
indicators.
H.12 Indicator name2 String Indicates indicator Regenerate section

names. One indicator errored second.
group contains multiple
indicators.
Sample
Collect performance data of S5328 through the performance text NBI. Figure 1 shows the
generated performance text file.
Figure 1 A sample for the performance text file
Table 3 lists the meanings of fields in the sample for the performance text file in Figure 1.
Table 3 Meanings of the fields in the sample for the performance text file
Field in the Example Description Data Type
packets Statistics Indicator Name of the indicator group. String
packets Statistics Indicator Description of the indicator group String
2009-08-21 12:30 Performance data before 2009- Datetime

08-21 12:30.
53 The performance data file has 53 Number

records in total.
DeviceID Device ID Number
DeviceName Device name String
ResourceID Resource ID String
ResourceName Resource name String
CollectionTime Performance collection time Datetime
GranularityPeriod Performance collection Number

granularity
Table 3 Meanings of the fields in the sample for the performance text file
Field in the Example Description Data Type
CPU Usage Name of an indicator (an String

Memory Usage indicator group can contain
multiple indicators)
3.9.4 Setting Fields to Be Exported

This topic describes how to set fields to be exported for the performance text file. In the
PMExport.xml file, set the configuration item CsvHead to define fields to be exported to the
NOTE:
In the CsvHead configuration item, set the value of a field to TRUE if you want to display the
field data in the performance text file. Set the value of a field to FALSE if you do not want to
display the field data in the performance text file.
NOTE:
For example, the value of ResourceID is FALSE by default. This means that the ResourceID field is not included
in the performance text file by default.
Sample configuration of CsvHead is as follows:
CsvHead>
<Line1>
<IndicatorGroupName>TRUE</IndicatorGroupName>
<IndicatorGroupDescription>TRUE</IndicatorGroupDescription>
<FileCreationTime>TRUE</FileCreationTime>
<NumberOfDataRecords>TRUE</NumberOfDataRecords>
</Line1>
<Line2>
<DeviceID>TRUE</DeviceID>
<DeviceName>TRUE</DeviceName>
<ResourceID>FALSE</ResourceID>
<ResourceName>TRUE</ResourceName>
<CollectionTime>TRUE</CollectionTime>
<GranularityPeriod>TRUE</GranularityPeriod>
</Line2>
</CsvHead>
3.9.5 Ensuring Data Integrity of Performance

Text Files
During the generation of a performance text file, performance data may be incomplete or the
performance file fails to be generated due to an exception. The Performance Text NBI is able to
automatically detect such an exception and generates the related data in a file in the next period.
NOTICE:
 Data lost during active/standby switchovers is not generated.
 Only RMON equipment is supported for transport NEs.
When a performance text file is generated, the U2000 automatically detects data integrity of the
file.
The U2000 generates the performance text file periodically based on the preset generation time.
When generating a file, the U2000 automatically detects the integrity of the file. If the U2000
detects that the file is abnormal or the file fails to be generated, related performance data will be
generated as a performance text file in the next period.
3.9.6 Parsing Principle and Restriction

When parsing the performance text file, you need to keep version compatibility and flexibility.
This topic describes the parsing principles and restrictions during software development.
File Path
As shown in Table 1, the performance text file supports three automatically generated path
structures.
Table 1 File path mode
Path Mode Description Usage Principle
Mode 1 The performance text file of the same day This is the default mode and is
is exported to the same directory. recommended.
Mode 2 All files are exported to the root directory. The rule for obtaining files is simple but a
directory contains a large number of files.
Mode 3 Subdirectories are generated based on This mode is used during upgrades.
Indicator Group ID/Collection Ensure that the indicator group ID is not
Period/Date/Time. blank in performance indicator filter
templates.
File Row Sequence

The performance text file uses indicators as the table heading and each performance indicator
occupies one row.
NOTICE:
Only the indicator name, rather than the row number, is used to identify a unique indicator.
 The U2000 earlier than V100R005SPC500 supports export of all indicators and the indicator
sequence and the number of indicators in the performance text file varies with versions.
Therefore, the row number cannot be used as the parsing rule. Otherwise, an error occurs
during parsing when the number of indicators increases or decreases.
 The U2000 V100R005SPC500 and later versions must use performance indicator filter
templates. The indicator sequence and number of indicators in the performance text file
change only after the templates are modified. It is not recommended that the row number be
used as the parsing rule for future indicator expansion.
Fields Cannot Be Parsed

Fields listed in Table 2 cannot be parsed.
Table 2 Fields cannot be parsed

Field Description
ResourceID This field cannot be parsed. The rule for filling in this field is internally
defined by the U2000. The rule may change after a version upgrade.
ResourceName This field cannot be parsed. The rule for filling in this field is internally
defined by the U2000. The rule may change after a version upgrade.
Performance Generation Object

Because the current version cannot parse the ResourceID and ResourceName fields, the
performance generation objects can be located to specified NEs by using the DeviceID and
DeviceName fields.
Repeated Transport Performance Events

Transport performance indicators may belong to multiple logical function blocks but only one is
valid. When repeated performance indicator names exist, select a value of such performance
indicators. Specifically, use the non-zero value as the value of repeated performance indicators.
If all values are 0, the value of the performance indicators is 0.
3.10 Maintaining the Performance Text NBI

This section describes how to maintain the Performance Text NBI periodically to keep it running
properly and provides troubleshooting for common problems.
For more details about the U2000 maintaining, see the iManager U2000 Routine Maintenance.
 Requirements for Maintenance Personnel

This section describes the requirements for maintenance personnel.
 Routine Maintenance
Routine maintenance allows you to detect faults such as malfunctions during system operation in
a timely manner and take measures to handle the problem. By performing routine maintenance,
hidden problems are detected and resolved to prevent accidents. Performing routine maintenance
once a week is recommended.
 Disabling and Deleting the Performance Text NBI

Disable or delete the Performance Text NBI if the U2000 does not need to provide the external
 FAQs
This section describes how to confirm common faults and troubleshoot common faults in the
system.
3.10.1 Requirements for Maintenance

Personnel
This section describes the requirements for maintenance personnel.
To ensure smooth maintenance and rapid problem solving, the maintenance personnel must:
 Be familiar with the basic operations of the PC, Sun workstation, Windows, Solaris and Linux
operating systems.
 Have a good understanding of the performance management technology and Performance
Text NBI principle.
 Understand concepts of the telecommunication management network (TMN) and know the
basic networking architecture of the U2000 well.
 Be familiar with the configuration and the operations of enabling and disabling the
Performance Text NBI interface.
NOTE:
For workstation maintenance, see the maintenance manual provided by its supplier.
Parent topic: Maintaining the Performance Text NBI
3.10.2 Routine Maintenance

Routine maintenance allows you to detect faults such as malfunctions during system operation in
a timely manner and take measures to handle the problem. By performing routine maintenance,
hidden problems are detected and resolved to prevent accidents. Performing routine maintenance
once a week is recommended.
Checking the Running Status of the Performance Text NBI Process

1. Log in to the System Monitor.
 In a high availability (HA) system, log in to the System Monitor of the primary site to
perform this operation.
 In a distributed system, log in to the System Monitor of the master server to perform this
operation.
2. Check the running status of the textagent process (Service is textagent). If the running
status is Running, the Performance Text NBI service runs properly.
3. Check the running status of all services with Process Group as Performance Manager. If
the running status of all services is Running, the performance management system (PMS)
runs properly.
4. Check whether the NE management processes run properly for different managed NEs.
Backing up the Logs of the Performance Text NBI

The log information of the Performance Text NBI is saved in the /opt/backup/var/logs/nbi/text
(Windows) or D:\backup\var\logs (Solaris or Linux) directory. Back up the log files
periodically to prevent them from occupying much of the system disk space. The log files record
the running information of the Performance Text NBI. If an error occurs when the Performance
Text NBI is running, you can refer to the log files for troubleshooting. If you want to back up the
log information of the Performance Text NBI, manually copy the log information to a specified
directory.
3.10.3 Disabling and Deleting the Performance

Text NBI
Disable or delete the Performance Text NBI if the U2000 does not need to provide the external
 Logging In to the System Monitor Client

The U2000 System Monitor Client uses the client/server model. To perform an operation, you
need to log in to the server through the U2000 client.
 Stopping the Performance Text NBI

If you do not need to use the Performance Text NBI, stop the Performance Text NBI service by
using the System Monitor client.
 Disabling the Performance Text NBI

You can disable the Performance Text NBI, the Performance Text NBI service does not start
with the U2000 next time the U2000 is started.
 Restarting the Performance Text NBI
When the Performance Text NBI service is in the stopped state, you can restart the service in the
System Monitor client.
3.10.3.1 Logging In to the System Monitor

Client
The U2000 System Monitor Client uses the client/server model. To perform an operation, you
need to log in to the server through the U2000 client.
Prerequisites
Before login, ensure that the U2000 client and server are connected properly and that the server
works correctly.
Context
 The default port number of the server is 31030. Do not change it in normal conditions.
Otherwise, you cannot log in to the U2000 server.
 The login modes include the SSL mode and common mode. In SSL mode, the data is
encrypted when being transmitted between the client and the server. In common mode, the
data is not encrypted during transmission. To ensure the security of data transmission, you are
recommended to use the Security (SSL) mode.
 The port used for login in common mode is different from that in SSL mode. The port number
is 31030 in common mode, and 31080 in security (SSL) mode.
 After last login, if you do not log in again during the preset period, your account hibernates or
the U2000 deletes the account.
 If you never use a new user account for login, the U2000 does not invalidate or delete the
account.
Procedure
1. Double-click the shortcut icon of U2000 System Monitor on the desktop to start the system
monitor client.
NOTE:
In the Solaris and Linux OS , login to the OS of the server as the ossuser user. Run the following command to
start the system monitor client.
$ cd /opt/oss/client
$ ./startup_sysmonitor_global.sh
/opt/oss is the default installation path for the U2000. You can change it as required.
2. In the Login dialog box, select a server by selecting an IP address or host name from the
Server drop-down list.
NOTE:
If the list does not contain a server, do as follows:
a. Click on the right of the Server drop-down list.

b. In the Server List dialog box, click Add.
c. In the Add Server Information dialog box, specify Name and Server Name(or IP Address), and then
select a login mode. Click OK.
d. In the Server List dialog box, click OK.
3. In the Login dialog box, enter the user name and password.
The user name and password are the same as those used on the U2000 client.
4. Click Login.
NOTE:
 If the user name and the password are correct, the Loading dialog box is displayed, showing the loading
progress.
 If the user name or password is incorrect, the Information dialog box is displayed, prompting that you
cannot log in.
 If the password will expire in the specified days, a dialog box is displayed, prompting you to change the
password before the expiration date.
Parent topic: Disabling and Deleting the Performance Text NBI
3.10.3.2 Stopping the Performance Text NBI

If you do not need to use the Performance Text NBI, stop the Performance Text NBI service by
using the System Monitor client.
Prerequisites
 On Solaris or Linux, you have the ossuser user rights.

 On Windows, you have the administrator user rights.
 In an HA system, the Performance Text NBI is configured at the primary site.
 The U2000 have been started.
 The Performance Text NBI service (textagent) service is in the Running state.
Context
NOTE:
After the Performance Text NBI is deployed, the default start mode is Automatic. The Performance Text NBI
service (textagent) starts with the U2000.
Procedure
2. On the System Monitor, enter the Service Monitor tab.
3. Right-click the textagent service and choose Stop the Service from the shortcut menu.
4. In the dialog box that is displayed, click Yes.
5. In the System Monitor client, check Status of the relevant Performance Text NBI service
(textagent). If the status is Stopped, the operation is successful.
3.10.3.3 Disabling the Performance Text NBI

You can disable the Performance Text NBI, the Performance Text NBI service does not start
with the U2000 next time the U2000 is started.
Prerequisites
 The Performance Text NBI service (textagent) is in the Stopped state.
Procedure

3. Right-click textagent service and choose Startup Mode > Disabled from the shortcut
menu.
4. In the System Monitor client, check Startup Mode of the relevant Performance Text NBI
(textagent) service. If it is Disabled, the operation is successful.

3.10.3.4 Restarting the Performance Text NBI
When the Performance Text NBI service is in the stopped state, you can restart the service in the
System Monitor client.
Prerequisites

 The Performance Text NBI service (textagent) is in the Stopped state.
Procedure
3. Right-click the textagent service and choose Start the Service from the shortcut menu.
4. In the System Monitor client, check Status of the relevant Performance Text NBI service. If
textagent is Running, the operation is successful.
3.10.4 FAQs
This section describes how to confirm common faults and troubleshoot common faults in the
system.
 The System Monitor Client Contains No Performance Text NBI Process.
 What Is the Process Name of the Performance Text NBI?
 Does the Performance Text NBI Depend on Other Processes?
 How Do I Change the Folder Hierarchy of the performance text file?
 How Do I Add the ResourceID Field to the performance text file?
 How Do I Export the Performance Text File After the U2000 Is Installed?
 How Is Performance Data Managed on the U2000?
 Which Directory on the oss Do Performance Intermediate Files Locate In?
 How Do I Configure the Directory for PMS Performance Intermediate Files?

3.10.4.1 The System Monitor Client Contains
No Performance Text NBI Process.
Question
After the Performance Text NBI is deployed, the System Monitor client contains no textagent
process.
Answer
1. View the license on the U2000 client, check whether there are is a Performance Text NBI
license. If no, apply a license for the Performance Text NBI. After the license is installed,
deploy the Performance Text NBI again.
2. On non-Windows, check whether all files in server/etc/conf have the rights of ossuser and
ossgroup if this issue persists after confirming that the U2000 has a license for the
Performance Text NBI. If no, run the following command as user root:
chown -R ossuser:ossgroup /opt/oss/server/etc/conf
Parent topic: FAQs
3.10.4.2 What Is the Process Name of the

Performance Text NBI?
Question
What is the process name of the Performance Text NBI? Can I view the process name on the
System Monitor client?
Answer
The process name of the Performance Text NBI is textagent. The following information is
displayed on the System Monitor client:
 Service name: textagent
 Process group: NBI
 Process name: textagent
Parent topic: FAQs

3.10.4.3 Does the Performance Text NBI
Depend on Other Processes?
Question
Does the Performance Text NBI depend on other processes for its export function?
Answer
1. The Performance Text NBI process itself does not depend on other processes for its startup.
However, the TXTNBIDm for performance management must be in the running state if the
Performance Text NBI functions are used.
Information about the Performance Text Process is as follows:
 Service name: TXTNBIDm
 Process group: performance management
 Process name: TXTNBIDm
Parent topic: FAQs
3.10.4.4 How Do I Change the Folder Hierarchy

of the performance text file?
Question
The Performance Text NBI can generate different directory hierarchies and export the
performance text file to related directories based on customers requirements.
Answer
Currently, the Performance Text NBI supports three folder hierarchies. For details, see the File
Export Path.
Parent topic: FAQs

3.10.4.5 How Do I Add the ResourceID Field to
the performance text file?
Question
How do I add the ResourceID field to the performance text file?
Answer
By default, the ResourceID field in the performance text file is not displayed. To display the
ResourceID field, modify the configuration file.
1. Log in to the server of the U2000.
 On Windows, log in to the server as user administrator.
 On Solaris or Linux, log in to the server as user ossuser.
2. Modify the PMExport.xml configuration file. Specifically, change the value of ResourceID
to TRUE.
<ResourceID value="TRUE"/>
NOTE:
3. Reconfigure the Performance Text NBI.
Parent topic: FAQs
3.10.4.6 How Do I Export the Performance Text

File After the U2000 Is Installed?
Question
How do I use the Performance Text NBI to export the performance text file for performance
integration after a U2000 is installed?
Answer
Perform the following steps:

1. Confirm the type of performance object to be exported. For details, see the Performance
Management Objects .
2. Confirm that the performance resources to be exported are being monitored.

Before performance text file is exported, its resources must be monitored on the U2000.
Different performance monitoring objects have different monitoring methods. Perform steps
depending on the performance type. For details, see the Enabling Performance Monitoring On the
U2000.
For more details about how to monitor performance, see the Online Help by pressing F1 on
the U2000 client.
 To export performance data of SDH, WDM, RTN, or PTN equipment, see the
Performance Management (MSTP&PTN).
 To export performance data of IP and access equipment, or RMON performance of
transport equipment, see the Performance Management System (PMS).
3. Confirm that Performance Text NBI has been deployed. For details about how to deploy the
Performance Text NBI, see Deploying and Configuring the Performance Text NBI .
4. Browse historical performance data of the performance instance on the U2000 client. If no
historical performance data exists, the Performance Text NBI cannot export the performance
text file.
5. Confirm that the NE time zone and server time zone are consistent. If inconsistent, the
Performance Text NBI cannot export the performance text file.
Parent topic: FAQs
3.10.4.7 How Is Performance Data Managed on

the U2000?
Question
The current U2000 can manage router, switch, transport, access, and PTN NEs. How does the
U2000 manage their performance data? What are the differences?
Answer
The current U2000 manages performance data as follows:

 The transport NE management processes monitor and output performance data except RMON
performance of transport equipment. The performance data includes SDH, WDM, and OTN
performance events.
 The performance management system (PMS) manages performance data of other equipment,
such as RMON performance of transport equipment and performance of PTN, IP, and access
equipment.
Parent topic: FAQs
3.10.4.8 Which Directory on the oss Do

Performance Intermediate Files Locate In?
Question
Transport NE management processes and the PMN export performance intermediate files. The
Performance Text NBI processes these files and output the final performance text file. Which
directory on the oss do performance intermediate files locate in?
Answer
 If the performance data of SDH, WDM or OTN equipment is exported, confirm that
performance intermediate files exist in the default export directory
server/var/PerfFileData/data(or server/var/dump/PerfFileData/trans/data). If no, an
exception occurs during the performance data export of the transport NE management
processes.
NOTICE:
The U2000 does not support the function of configuring the directory for transport non-
RMON performance intermediate files.
 If performance of other equipment is exported, confirm that performance intermediate files

exist in the directory d:\PerfFileData\pms for Windows (or /opt/backup/pms for Solaris). If
no, an exception occurs during performance export of the PMS.
NOTE:
The U2000 V100R007C00 and later versions support the function of configuring the directory for exported PMS
performance intermediate files. For details, see How Do I Configure the Directory for PMS Performance
Intermediate Files?.
Parent topic: FAQs

3.10.4.9 How Do I Configure the Directory for
PMS Performance Intermediate Files?
Question
By default, performance intermediate files are exported to the directory on the installation path
of the U2000. On a large-scale network with many IP or access equipment, performance
intermediate files will occupy too much disk space, which may affect the U2000 performance.
Therefore, it is recommended to export the PMS performance intermediate files to a disk where
the U2000 is not installed.
The U2000 V100R006C00 and later versions support the function of manually configuring the
directory for PMS performance intermediate files. How do I configure the directory for PMS
performance intermediate files?
Answer
 Modify the FileGenPath configuration item and configure the storage directory for
performance intermediate files in the
server/etc/oss_cfg/pms/common/pms/conf/NBI_Config_File.xml configuration file.
 For example, on a Windows-based U2000, modify the configuration item as follows to
export performance intermediate files to the D:\pmdata directory.
<FileGenPath value="D:\pmdata" />
 On a Solaris- or Linux-based U2000, modify the configuration item as follows to export
performance intermediate files to the /opt/pmdata directory.
<FileGenPath value="/opt/pmdata" />
 NOTICE:
 By default, the configuration item is commented out. If the configuration item needs to be
configured, cancel the comment and change the value in the configuration item to an
absolute directory on the U2000 server.
 The U2000 user ossuser has read and write permissions for the configured directory.
 Ensure that no data folder irrelated to performance intermediate files exists in the
configured directory, because the U2000 will automatically create the data directory.
 The configured directory has sufficient disk space.
 Set permissions for user ossuser to operate the configured directory. For details, see the
iManager U2000 Administrator Guide.
For example, run the following commands to set the owner of the /opt/pmdata directory to
ossuser and configure read and write permissions for the user:
# chown -R ossuser:ossgroup /opt/pmdata

# chmod 777 /opt/pmdata
 The following calculation method of disk space is only for reference:
 Disk space required by one monitoring instance in a single collection period: 0.15 KB +
0.01 KB * indicator number
 Disk space required by one monitoring instance in one day: 0.15 KB + 0.01 KB * indicator
number * (1440/minutes in a collection period)
 Disk space required by all monitoring instances in one day: instance number * (0.15 KB +
0.01 KB * indicator number) * (1440/minutes in a collection period)
Example
Use a typical network of IP routers as an example. A total of 100,000 monitoring instances
are configured, the collection period is 15 minutes, and the number of indicators is 23.
The consumed disk space in one day is: 100000 * (0.15 KB + 0.01 KB * 23) * (1440/15) =
3.48 GB
By default, performance intermediate files are stored for three days on the U2000. The totally
consumed disk space is: 3.48 GB * 3 = 17.4 GB
Parent topic: FAQs
3.11 Configuring the FTP Server

The FTP protocol must be configured correctly on the U2000 server so that the OSS can access
the U2000 to obtain the performance text file using the FTP protocol.
 Configuring the FTP or SFTP Server on Windows

NE software communicates with the client or NEs through the FTP or SFTP protocol for NE
upgrade, data backup, and patch installation. This topic describes how to create a FTP user and
password, enable and disable the FTP or SFTP service, test FTP or SFTP, and configure the file
transfer protocol on windows OS.
 Configuring the FTP Service (Solaris)

The Solaris-based U2000 uses the FTP function provided by the Solaris OS. This section
describes how to configure the FTP server on Solaris 10.
 Configuring the SFTP Server (Solaris)

The Solaris-based U2000 uses the SFTP function provided by the Solaris OS or OpenSSH.
OpenSSH is recommended. This section describes how to configure the SFTP server on Solaris
10.
 Configuring the FTP or SFTP Service (SUSE Linux)

The DC communicates with clients or NEs by using the FTP or SFTP protocol to upgrade NEs,
back up data, and install patches. The U2000 installed on a SUSE Linux OS uses the FTP or
SFTP service provided by the OS. This topic describes how to create a FTP or SFTP user and
transfer protocol on SUSE Linux.
3.11.1 Configuring the FTP or SFTP Server on

Windows
NE software communicates with the client or NEs through the FTP or SFTP protocol for NE
upgrade, data backup, and patch installation. This topic describes how to create a FTP user and
transfer protocol on windows OS.
Context
 To use the service of a third-party tool for file transfer, make sure that the third-party tool
configured as the FTP/SFTP server is started, and stop the FTP/SFTP service of the U2000
server.
 The file transfer parameters set on the U2000 must be the same as the parameters set on the
FTP or SFTP server.
 To ensure the security of the U2000, passwords must be complex enough. For example, a
password must contain eight or more characters of two types. The allowed characters are
digits, letters, and special characters. Remember to change passwords regularly.
NOTICE:
You are advised to set the read-only permission for OSS users that obtain performance files
through FTP or SFTP.
Procedure
 Configuring the FTP server using the third-party tool apache-ftpserver
NOTE:
 apache-ftpserver is automatically installed along with the U2000TCATU2000. Therefore, you do not need
to configure the FTP server after the U2000TCATU2000 is installed.
 apache-ftpserver is not the only third-party tool that can be used to configure the FTP server. Do not use
wftpd32.exe to configure the FTP server; otherwise, remote database backup fails.
3. Visit http://mina.apache.org/ftpserver-project/downloads.html and download the latest apache-

ftpserver package.
4. Decompress the apache-ftpserver package. You can decompress it to d:\.
5. Navigate to d:\ftpserver\apache-ftpserver-1.0.5\res\conf and open the ftpd-typical.xml

file.
Add the anon-enabled, max-logins, and encrypt-passwords attributes.
NOTE:
The key attributes are described as follows:
 anon-enabled: whether to allow anonymous access. If it is set to true, anonymous access is allowed. If it
is set to false, anonymous access is prohibited. To ensure system security, set it to false.
 max-logins: the maximum number of login users.
 port: FTP port number.
 encrypt-passwords: If this attribute is not set, the password is in cipher text by default. If this attribute is
set to clear, the password is in plain text. Set it to clear.
6. Navigate to d:\ftpserver\apache-ftpserver-1.0.5\res\conf and open the users.properties

file.
a. The default user name is admin. To change the user name, replace all
ftpserver.user.admin with ftpserver.user.XXXX. XXXX indicates the new user
name.
b. Set the ftpserver.user.XXXX.userpassword password.
c. Set the ftpserver.user.XXXX.homedirectory password as blank, as shown in the
following figure.
7. Install the ftpd service.
. Choose Start > Run. In the Run dialog box, enter cmd and press Enter to open the
CLI.
a. Enter d: and press Enter.
b. Run the following command to navigate to the directory where ftpd.exe is stored:
D:\> cd ftpserver\apache-ftpserver-1.0.5\bin
c. Set environment variables.
 FTPD_HOME=apache-ftpserver directory, for example,

FTPD_HOME=D:\ftpserver\apache-ftpserver-1.0.5
 JAVA_HOME=JRE directory, for example, JAVA_HOME=D:\ftpserver\jre
 JVM=jvm.dll directory, for example, JVM=D:\ftpserver\jre\bin\server\jvm.dll
d. Run the following command to start the ftpd service.
D:\ftpserver\apache-ftpserver-1.0.5\bin> ftpd.bat res/conf/ftpd-
typical.xml
If FtpServer started is displayed, the FTP service has been started.
NOTICE:
The FTP service is stopped if the CLI for configuring the FTP service is closed.
Therefore, close this CLI only after the FTP service use is complete.
8. Run ftp IP address in the CLI.
NOTE:
 IP address: system IP address of the computer where the Apache FtpServer ftp service is running.
 If a message is displayed indicating that the folder cannot be accessed, configuring the Apache
FtpServer ftp service fails. Shut down the firewall.
9. Enter user name and password as prompted.
If the message 230 User logged in, proceed. is displayed, the Apache FtpServer ftp
service is configured successfully.
 Configuring the SFTP server by using the third-party tool CYGWIN+OpenSSH
The SFTP service is automatically installed, when the U2000 is installed. User created for
SFTP services is ftpuser by default.
The ftpuser user is a computer administrator. To ensure the security of the U2000, to set the
default password and root path, perform the following steps.
0. Open a CLI.
1. Run the following commands to navigate to the OpenSSH installation directory in the
NMS installation path, for example, D:\oss\server\common\dc\3rdTool\cygwin.
2. > D:
> cd D:\oss\server\common\dc\3rdTool\cygwin
3. Run the following commands to uninstall OpenSSH.

> Uninstall.bat
4. Run the following commands, then, enter the password and root path as prompted.
> modify_sftp_config.bat
 password: To ensure the security of the U2000, passwords must be complex enough.
For example, a password must contain eight or more characters of two types. The
allowed characters are digits, letters, and special characters. Remember to change
passwords regularly. For example, Changeme_123.
 root path: For example, D:\.
5. Run the following commands to start OpenSSH.

> StartService.bat
NOTE:
 After the SFTP server is configured, if you want to start the SFTP service during the other follow-up
operations, the following command is recommended. Because the following command is simple without
entering the OpenSSH installation directory.
> net start sshd
The SFTP service has been started if the following information is displayed.
The CYGWIN ssh service has been started.
 After the SFTP server is configured, if you want to stop the SFTP service during the other follow-up
operations, the following command is recommended. Because the following command is simple without
entering the OpenSSH installation directory.
> net stop sshd
The SFTP service has been stoped if the following information is displayed.
The CYGWIN ssh service has been stoped.
Parent topic: Configuring the FTP Server
3.11.2 Configuring the FTP Service (Solaris)

The Solaris-based U2000 uses the FTP function provided by the Solaris OS. This section
describes how to configure the FTP server on Solaris 10.
Prerequisites
Log in to the Solaris OS as user root.
Context
Assume that the configuration environment of the FTP server is as follows:

 The root directory of the FTP service is /opt/oss/server/nbi/text/pfm_output.
 The user name of the FTP server is nbiftpuser and the password is Changeme_123.
NOTE:
If you have logged in to the Solaris-based U2000 as user root, the root directory of the FTP server is / and the user
name is root.
NOTICE:
 Digit: 0–9
Procedure
1. View the user group which the root directory /opt/oss/server/nbi/text/pfm_output belongs
and the user group permissions.
2. # ls -l /opt/oss/server/nbi/text
Display the root directory /opt/oss/server/nbi/text/pfm_output belongs "ossgroup" and the
user group permissions "r-x" as follows.
drwxr-x--- 8 ossuser ossgroup 1024 December 26 12:00 pfm_output
3. Create an FTP user.

4. # useradd -d /opt/oss/server/nbi/text/pfm_output -g ossgroup -s /bin/bash
nbiftpuser
5. # passwd nbiftpuser
6. New Password: Changeme_123
Re-enter new Password: Changeme_123
NOTE:
 Set the name of the new user to nbiftpuser and set the root directory to
/opt/oss/server/nbi/text/pfm_output.
 Set the password of the nbiftpuser user to Changeme_123. No information is displayed when the new
password is set and verified.
 You can modify the password by the command passwd UserName. For example, passwd nbiftpuser
indicates modify the password of user nbiftpuser.
NOTICE:
To ensure the security of the NMS, passwords must be complex enough. For example, a
password must contain six or more characters of two types. The allowed characters are
digits, letters, and special characters.
7. Optional: Change the root directory if the nbiftpuser user already exists.
# usermod -d /opt/oss/server/nbi/text/pfm_output -g ossgroup nbiftpuser
NOTE:
Change the root directory of the nbiftpuser user to /opt/oss/server/nbi/text/pfm_output.
8. Empower the user group members /opt/oss/server/nbi/text/pfm_output perform, read

permission.
9. # chmod 550 /opt/oss/server/nbi/text/pfm_output
NOTE:
Log in to the Solaris OS as user nbiftpuser, the user needs to have sufficient permissions on the root directory
/opt/oss/server/nbi/text/pfm_output. Otherwise, it will not be able to access to the root directory.
10. Stop the FTP service.

11. # svcadm disable ftp
12. Start the FTP service.

13. # svcadm enable ftp
14. Check whether the FTP service has been started.

# svcs | grep ftp
If the following message is displayed, it indicates that the FTP service is started.
online 22:07:11 svc:/network/ftp:default
NOTE:
If the FTP service is abnormal, stop the FTP service first and run a command to start the FTP service again.
3.11.3 Configuring the SFTP Server (Solaris)

The Solaris-based U2000 uses the SFTP function provided by the Solaris OS or OpenSSH.
OpenSSH is recommended. This section describes how to configure the SFTP server on Solaris
10.
Prerequisites
Log in to the Solaris OS as user root.
Context
Assume that the configuration environment of the SFTP server is as follows:

 The root directory of the SFTP service is /opt/oss/server/nbi/text/data.
 The user name of the SFTP server is u2000sftp and the password is u2000.
 The SFTP service uses port 22.
NOTE:
You need to manually create the root directory of the SFTP service and set its user group and permission to
ossgroup and rwx respectively.
Procedure
1. Run the following command to create the /opt/oss/server/nbi/text/data directory:
# mkdir -p /opt/oss/server/nbi/text/data
2. Run the following command to change the user group of this directory to ossgroup:
# chgrp -R ossgroup /opt/oss/server/nbi/text/data
3. Run the following command to grant rights to the user group, enabling all members in it to
have the read permission for the /opt/oss/server/nbi/text/data directory:
4. # chmod 550 /opt/oss/server/nbi/text/data
5. Create an SFTP user and add it to the ossgroup user group. Then this user has the read and
write permissions for the /opt/oss/server/nbi/text/data directory. The following uses the
creation of the u2ksftp user as an example.
6. # useradd -d /opt/oss/server/nbi/text/data -g ossgroup -s /bin/bash
u2ksftp
7. # passwd u2ksftp
8. New Password: u2000
Re-enter new Password: u2000
NOTE:
 The user name is u2ksftp and the root directory is /opt/oss/server/nbi/text/data.
 The user password is u2000. The password is not displayed during its setting and confirmation.
 You can also run the passwd User name command to change the password of a user. For example, run the
passwd u2ksftp command to change the password of the u2ksftp user.
NOTICE:
To ensure system security, set the password and periodically change it based on the
following password complexity requirements:
 The password contains at least six characters.
 The password is a combination of at least two types of the following characters: digit,
letter, and special character.
9. Run the following commands to enable recommended OpenSSH.

10. # cd /opt/oss/server/common/dc/3rdTool/openssh
11. # ./chroot_ssh.sh enable
12. # ./ssh_adm.sh start
13. Run the following command to check whether OpenSSH has been started:
14. # ./check_ssh.sh
A message similar to the following is displayed:
System SSH : [ not running ]
New SSH : [ running ][ chroot ]
15. Use the SFTP service carried by the system.
NOTICE:
By default, the SFTP service carried by the system is not used. Use OpenSSH to ena ble
SFTP.
a. Stop OpenSSH.
b. # cd /opt/oss/server/common/dc/3rdTool/openssh
c. # ./chroot_ssh.sh disable
d. # ./ssh_adm.sh stop
e. Run the following command to check whether OpenSSH has been stopped:
f. # ./check_ssh.sh
A message similar to the following is displayed:
System SSH : [ not running ]
New SSH : [ not running ][ not chroot ]
g. Verify that the ssh process is running for enabling the SFTP service.
Run the following command to check whether the ssh process is running on the Solaris
OS:
# svcs -a |grep ssh
 If a message similar to the following information is returned, the ssh process is in the
running state.
online May_04 svc:/network/ssh:default
 If the ssh process is not in the running state, run the following command to enable it:
 maintenance May_04 svc:/network/ssh:default

 svcadm disable svc:/network/ssh:default
svcadm enable svc:/network/ssh:default
h. Modify the configuration file manually. In the /etc/ssh/sshd_config file, change

PasswordAuthentication no to PasswordAuthentication yes.
Example:
# vi /etc/ssh/sshd_config
Modify the PasswordAuthentication no to PasswordAuthentication yes, and run the
:wq! command to save the settings and exit.
NOTE:
You need to modify PermitRootLogin no to PermitRootLogin yes for user root to access the SFTP
server.
i. Run the following command to restart the SFTP service:

# svcadm refresh svc:/network/ssh:default
16. Optional: Generate an authentication file for the SFTP service on the OSS SFTP server. The
following is an example for Solaris 10.
The private key file id_rsa and public key file id_rsa.pub can be generated by running the
./ssh-keygen -t rsa command. Save these two files in the specified directory of the SFTP
server.
# cd /usr/bin
# ./ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (//.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in //.ssh/id_rsa.
Your public key has been saved in //.ssh/id_rsa.pub.
The key fingerprint is:
91:e1:14:fb:88:e3:94:b9:6f:06:c4:e1:db:8d:75:bd root@T522022589
NOTICE:
If you use the NBI Config Tools to deploy the Performance Text NBI in SFTP mode,
transfer the private key file to the U2000 server. When selecting the SFTP certificate,
specify the correct absolute path and filename of the private key file on the U2000 server.
The public key file is in the OSS SFTP server.
After you transfer the private key file to the U2000 server, grant the permission to read the
private key file to user ossuser.
# cat /.ssh/id_rsa.pub >> /.ssh/authorized_keys
3.11.4 Configuring the FTP or SFTP Service

(SUSE Linux)
The DC communicates with clients or NEs by using the FTP or SFTP protocol to upgrade NEs,
back up data, and install patches. The U2000 installed on a SUSE Linux OS uses the FTP or
SFTP service provided by the OS. This topic describes how to create a FTP or SFTP user and
transfer protocol on SUSE Linux.
Context
NOTE:
To use a third-party FTP or SFTP service, install and enable it manually. The U2000 installed on a SUSE Linux OS
uses the FTP or SFTP service provided by the OS to ensure security.
 In the case of the Solaris- or Linux-based U2000, the FTP or SFTP function provided by the
Solaris or Linux OS is used.
 The root directory, user name, and password of the FTP or SFTP service must be the same as
those that are set on the U2000 client.
 In a distributed system, you need to configure the FTP or SFTP service on the master server
and the slave server that is deployed with the access NE management instance by following
the same procedure.
 To ensure the security of the U2000, passwords must be complex enough. For example, a
password must contain eight or more characters of two types. The allowed characters are
digits, letters, and special characters. Remember to change passwords regularly.
 Users created for FTP and SFTP services are ftpuser by default.
Procedure
 Configure the FTP service.
1. Log in to the Linux OS as user root.
2. Run the following command to create a root path for an FTP user:
# mkdir -p root path of ftp user
NOTE:
root path of ftp user: root path for an FTP user to transfer files. For example, /tftpboot.
3. To create an FTP user and set its user name and password, run the following commands:
4. # useradd -d root path of ftp user -g ossgroup -s /bin/bash ftpuser
5. # passwd ftpuser
6. New Password:
7. Re-enter new Password:
NOTE:
 ftpuser: A FTP user, ftpuser, is automatically created after the U2000 is installed.
 If a message indicating that ftpuser already exists, skip this step.
 If ftpuser does not exist because it has been deleted for example, the preceding message is not
displayed and this step must be performed.
 Multiple users can use a FTP service. A SUSE Linux OS has a default FTP user, root user. The root
path is /.
 ftpuser password:To ensure the security of the U2000, passwords must be complex enough. For
example, a password must contain eight or more characters of two types. The allowed characters are
digits, letters, and special characters. Remember to change passwords regularly. For example,
Changeme_123.
8. Restart the FTP service.

 Run the following command to start the FTP service:
# service vsftpd start
 Run the following command to stop the FTP service:

# service vsftpd stop
9. NOTE:
 To change the ftpuser password, run the passwd ftpuser command.
 To modify the root path of the ftpuser because of reasons such as insufficient path space, run the
usermod -d new root path of ftp user ftpuser command and restart the FTP service.
 Configure the SFTP service.

1. Log in to the Linux OS as user root.
2. Run the following command to create a root path for an SFTP user:
# mkdir -p root path of sftp user
NOTE:
root path of sftp user: root path for an FTP user to transfer files. For example, /tftpboot.
3. To create an SFTP user and set its user name and password, run the following commands:
4. # useradd -d root path of sftp user -g ossgroup -s /bin/bash ftpuser
5. # passwd ftpuser
6. New Password:
7. Re-enter new Password:
NOTE:
 ftpuser: A SFTP user, ftpuser, is automatically created after the U2000 is installed.
 If a message indicating that ftpuser already exists, skip this step.
 If ftpuser does not exist because it has been deleted for example, the preceding message is not
displayed and this step must be performed.
 Multiple users can use a SFTP service. A SUSE Linux OS has a default SFTP user, root user. The root
path is /.
 ftpuser password:To ensure the security of the U2000, passwords must be complex enough. For
example, a password must contain eight or more characters of two types. The allowed characters are
digits, letters, and special characters. Remember to change passwords regularly. For example,
Changeme_123.
8. Restart the SFTP service.

 Run the following command to start the SFTP service:
# service sshd start
 Run the following command to stop the SFTP service:

# service sshd stop
9. NOTE:
 To change the ftpuser password, run the passwd ftpuser command.
 To modify the root path of the ftpuser because of reasons such as insufficient path space, run the
usermod -d new root path of sftp user ftpuser command and restart the SFTP service.
 Configuring the File Transfer Protocol Configure the file transfer protocol as supported,
ensuring that file transfer services between NEs and the U2000 server function properly.
1. Choose Administration > NE Software Management > FTP Settings from the main
menu.
2. In the dialog box that is displayed, click the Transfer Protocol tab. Select a proper
protocol from the Protocol drop-down list for file transfer between NEs and the U2000
server.
3. Click OK.
3.12 Replacing the Certificate of the NBI Config

Tools
U2000 provides a default security certificate for encryption and authentication. It is
recommended that customers replace the default certificate with their security certificate.
Specifically, apply for a security certificate from a trusted CA and then use the certificate to
replace the original SSL certificate of the NBI Config Tools.
Windows OS
1. Log in to the server where the NBI Config Tools resides.
2. Back up the original certificate keystore.jks on the server. For example, copy the
keystore.jks file and rename it as keystore.jks_bak.
3. Copy the new certificate to the original certificate path to replace the keystore.jks
certificate. The name of the new certificate must be changed to keystore.jks.
4. Go to the encryption tool directory, and run the GenerateNBPass.bat -e command to
encrypt the certificate password.
After the following information is displayed, enter N:

check complexity of password or not(Y/N,default is 'Y',need check and
suggest this. if enter 'N', then will not check.):
Enter the initial password to be encrypted for two consecutive times.

$ enter password:
$ re-enter password:
NOTICE:
To ensure the security of the U2000, remember to change the default passwords of U2000
and update the passwords regularly, passwords must be complex enough.
a. It is a character string consisting of 8 to 18 characters.
b. Not be the same as or the reverse of the user name.
c. It contains at least three types of the following characters:
 Digit: 0-9
 Special character: =~@#^*-_+[{}]:./;?.
d. On UNIX or Linux OS, if a pound key (#) is used as the first character of the password,
you need to add a slash (\) before the pound key.
The ciphertext after encryption is returned:

Encrypt password result: b273290137C725168F52F3D7E1EA8670
5. Add the encrypted password to the KeyStorePassword configuration item.

 The configuration file path is server\etc\oss_cfg\nbi\configtool\conf\config.properties.
 The configuration item name is KeyStorePassword.
6. Restart the NBI Config Tools process nbi_configtools on the System Monitor client.
Linux/Solaris OS
1. Log in to the server where the NBI Config Tools resides as the ossuser user.
2. Run the following commands to back up the original certificate keystore.jks on the server:
3. $ cd $OSS_ROOT/server/etc/ssl/nbi/configtool/certificate
4. $ cp keystore.jks keystore.jks_bak
5. Copy the new certificate to the original certificate path to replace the keystore.jks
certificate. The name of the new certificate must be changed to keystore.jks.
6. Go to the encryption tool directory, and run the following commands to encrypt the
certificate password:
7. $ cd $OSS_ROOT/server/nbi/tools/encrypt
8. $ ./GenerateNBPass -e
After the following information is displayed, enter N:

check complexity of password or not(Y/N,default is 'Y',need check and
suggest this. if enter 'N', then will not check.):
Enter the initial password to be encrypted for two consecutive times.

$ enter password:
$ re-enter password:
NOTICE:
To ensure the security of the U2000, remember to change the default passwords of U2000
and update the passwords regularly, passwords must be complex enough.
a. It is a character string consisting of 8 to 18 characters.
b. Not be the same as or the reverse of the user name.
c. It contains at least three types of the following characters:
 Digit: 0-9
 Special character: =~@#^*-_+[{}]:./;?.
d. On UNIX or Linux OS, if a pound key (#) is used as the first character of the password,
you need to add a slash (\) before the pound key.
The ciphertext after encryption is returned:

Encrypt password result: b273290137C725168F52F3D7E1EA8670
9. Add the encrypted password to the KeyStorePassword configuration item.

 The configuration file path is server\etc\oss_cfg\nbi\configtool\conf\config.properties.
 The configuration item name is KeyStorePassword.
3.13 Revoking the Certificate of the NBI Config

Tools
This topic describes how to revoke the SSL certificate of the U2000 NBI Config Tools.
Windows OS
1. Log in to the server where the NBI Config Tools resides.
2. Modify the server/etc/oss_cfg/nbi/configtool/conf/config.properties file by adding the path
and name of the certificate to be revoked to the CRLFile configuration item. By default, the
CRLFile configuration item is left blank. To revoke a certificate, enter the correct path and
name of the certificate to be revoked.
3. Copy the CRL file huaweiossCA.crl to the server/etc/ssl/nbi/configtool/certificate

directory.
Linux/Solaris OS
1. Log in to the server where the NBI Config Tools resides as the ossuser user.
2. Use the vi editor to modify the server/etc/oss_cfg/nbi/configtool/conf/config.properties
file by adding the path and name of the certificate to be revoked to the CRLFile
configuration item. By default, the CRLFile configuration item is left blank. To revoke a
certificate, enter the correct path and name of the certificate to be revoked.
3. Use FTP as the ossuser user to upload the CRL file huaweiossCA.crl to the
$OSS_ROOT/server/etc/ssl/nbi/configtool/certificate directory.
4. Change the permission of the certificate to be revoked to 600.
5. $ cd $OSS_ROOT/server/etc/ssl/nbi/configtool/certificate
6. $ chmod 600 huaweiossCA.crl
3.14 PNM Performance Collection Guideline

During routine maintenance of cables, proactive network maintenance (PNM) analyzes the pre-
equalization coefficient between the cable modem (CM) and cable modem termination system
(CMTS) to discover faults on cable networks and determine the fault scope and locations. This
topic describes how to use the performance text NBI to report PNM performance indicators.
Application Scenario
In cable networking scenarios, the OLT works as the master subrack and connects to the
MA5633 (remote extended subrack) on the optical node through a GPON cascading board. The
CM connected to the MA5633 provides cable TV (CATV), Internet access and telephone
services.
The U2000 collects PNM pre-equalization performance indicators and reports the indicator
values to the OSS through the performance text NBI.
NE Restrictions
NE type:
 MxU: MA5633
 OLT: D-CMTS NEs V800R016C00 and later versions, such as MA5600T, MA5603T,
MA5608T, MA5680T, MA5683T, and MA5800. The control board must be SCUV and
support the MA5633 extended subracks.
Configuration Description
 Modifying configuration files

 File path: D:\oss\server\etc\oss_cfg\pms\cbb\pmslib\conf\DLMParams.cfg
 Configuration item: IS_BT_OR_DT = 1
 Creating PNM monitoring templates for CMs
 The NE type is OLT or MDU. If the resource types PNM-CM Primary Downstream
Channel and PNM-CM Upstream Channel are selected, set the indicators to be
monitored and monitoring period.
NOTE:
In centralized management networking scenarios, set the role type to OLT. In independent management
networking scenarios, set the role type to MDU. For details about the configuration procedures, see the
U2000 Online Help.
 Configuring instances for the performance text NBI

 The collection period and file export period can be set to 60 minutes, 360 minutes or 24
hours.
3.15 Glossary
F
FTP
File Transfer Protocol
I
IIS
internet information service
IP
Internet Protocol
N
NBI
northbound interface
NE
network element
R
RMON
remote monitor
S
SFTP
Secure File Transfer Protocol
T
TCP
Transmission Control Protocol

IManager U2000 NBI FTP Performace

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IManager U2000 NBI FTP Performace

Uploaded by

Copyright:

Available Formats

Performance Text NBI User Guide

3 Performance Text NBI User Guide

 Performance Management Process

 Enabling Performance Monitoring On the U2000

 Preparing for a Deployment

 Deploying and Configuring the Performance Text NBI

 Obtaining the Performance Text File

 Configuring the FTP Server

 Replacing the Certificate of the NBI Config Tools

 Revoking the Certificate of the NBI Config Tools

 PNM Performance Collection Guideline

3.1 Reading Guide

Intended Purpose Recommended Chapter

Configuring a Performance Indicator Template.

Parent topic: Performance Text NBI User Guide

Parent topic: Performance Text NBI User Guide

Parent topic: Preview

3.3 System Overview

Parent topic: Performance Text NBI User Guide

Parent topic: System Overview

Parent topic: System Overview

3.3.3 Equipment Supported

Table 2 Router equipment supported by the performance text NBI

Feature NE Series CX Series Switch BRAS ATN Security

Table 3 Access equipment supported by the performance text NBI

Feature MSAN/DSLAM FTTx

Narrowband Port Broadband Port FTTH FTTB/FTTC

Parent topic: System Overview

U2000 The NMS of Huawei. The U2000 uses a multi-process architecture

OSS OSS: Obtains the performance text file as required.

Parent topic: System Overview

Parent topic: System Overview

3.3.6 Security Mechanism

Parent topic: System Overview

3.3.7 High Availability

Parent topic: System Overview

Parent topic: System Overview

3.3.9 Performance Indicator

Table 1 Indicators of the Performance Text NBI

Parent topic: System Overview

3.4 Performance Management

 Performance Management Objects

 Performance Monitoring Principle

Parent topic: Performance Text NBI User Guide

3.4.1 Performance Management Objects

Objects Managed by the PMS

Objects Managed by the NE Explorer

Parent topic: Performance Management

3.4.2 Basic Concept

Indicator and Indicator ID

Indicator Group and Indicator Group ID

Performance Monitoring Instance

A performance monitoring instance is a performance monitoring task. Integrating the

Parent topic: Performance Management

3.4.3 Performance Monitoring Principle

Parent topic: Performance Management

3.5 Performance Management Process

Figure 1 Performance Management Flowchart

Operation Description Reference

Determine the performance Monitor operations are performed on Performance

Monitor Synchronize NE The configuration may fail if NE data is Transfers NE

Set the NE Enable 15-minute or 24-hour performance

Enable performance This operation is performed on boards. You

Set performance To query and process NE performance data,