NetNumen U31 R22 (V12.15.10) System Configuration Guide - V1.0

NetNumen™ U31 R22
Unified Network Management System

System Configuration Guide
Version: V12.15.10
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2014 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R4.0 2014-12-30 NetNumen™ U31 R22 (V12.15.10) Issued.
l Added “Configuring the BN-xTN Northbound TMF CORBA

(CMCC) Interface “, and “Configuring CMPP3.0 Forward”.
l Updated “Common Configurations”, “Product Configurations”
and “Alarm Forwording Installation”.
l Updated some configurition interfaces and menu items.
R3.1 2014-06-30 NetNumen™ U31 R22 (V12.14.10P02) Issued.

R3.0 2013-12-20 NetNumen™ U31 R22 (V12.14.10) Issued.
l Add “Configuring LDAP Authentication”.

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

Revision No. Revision Date Revision Reason
R2.2 2013-07-30 NetNumen™ U31 R22 (V12.13.10P02) was issued.
Updated “Configuring the Wireline NBI CORBA Interface”,

“Configuring the Wireline Northbound XML (MTOSI)
Interface”, “Configuring the BN-xTN Northbound CORBA
Interface”, “Configuring the BN-xTN Northbound SNMP
Interface”,“Configuring the United FTP (CSV) Inventory Interface
(xTN)” and “Configuring the FTP (CSV) Performance Interface
(xTN)”.
R2.1 2013-03-25 NetNumen™ U31 R22 (V12.13.10P01) was issued.
l Add “Configuring the Wireline Northbound CORBA Interface”,

“Configuring the Wireline Northbound XML (MTOSI)
Interface”, “BN Northbound Interface Configurations”, “N-IP
Configurations”, and “Wireline Common Configurations”.
R2.0 2012-12-30 NetNumen™ U31 R22 (V12.13.10) was issued.
Updated some configurition interfaces and menu items.
R1.0 2012-11-02 First edition.
Serial Number: SJ-20141211100735-006
Publishing Date: 2014-12-30 (R4.0)

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview of the Configuration Center ................................... 1-1
Chapter 2 Common Configurations ......................................................... 2-1
2.1 Configuring Common Properties ......................................................................... 2-1
2.1.1 Configuring the Server ............................................................................. 2-1
2.1.2 Configuring the Client ..............................................................................2-11
2.2 Configuring the Console ................................................................................... 2-14
2.3 Configuring the Unified Northbound Interface .................................................... 2-16
2.4 Configuring Symbol Localization ....................................................................... 2-19
2.5 Configuring the System Hierarchy .................................................................... 2-20
2.6 Updating the License File ................................................................................. 2-21
Chapter 3 Product Configurations............................................................ 3-1

3.1 Setting NE Types .............................................................................................. 3-1
3.2 Setting an NE Naming Rule ................................................................................ 3-2
3.3 Configuring Wireline NBI CORBA Interface ......................................................... 3-3
3.3.1 Configuration Steps .................................................................................. 3-3
3.3.2 Configuration Example ............................................................................. 3-6
3.4 Configuring Wireline NBI XML (MTOSI) Interface .............................................. 3-10
3.4.1 Configuration Steps ................................................................................ 3-10
3.4.2 Configuration Example ........................................................................... 3-13
3.5 BN Northbound Interface Configuration ............................................................. 3-20
3.5.1 Configuring the BN xTN Northbound CORBA Interface ............................. 3-20
3.5.2 Configuring the BN-xTN Northbound TMF CORBA (CTCC) Interface ........ 3-31
3.5.3 Configuring the BN-xTN Northbound TMF CORBA (CMCC) Interface ....... 3-40
3.5.4 Configuring BN xTN SNMP Interface ...................................................... 3-50
3.5.5 Configuring the Unified FTP (CSV) Inventory Interface ............................. 3-60
3.5.6 Configuring the FTP (CSV) Performance Interface .................................. 3-66
3.6 Configuring the BN-IP....................................................................................... 3-78
3.6.1 Configuring Performance Collection Granularity ....................................... 3-78
3.6.2 Configuring Deployment Mode for the Performance Collection Server ....... 3-79
3.6.3 Configuring Customized NE Types .......................................................... 3-79
3.6.4 Configuring the Customized Alarm Tool ................................................... 3-80
3.7 Configuring the Wireline Common Properties ..................................................... 3-84

3.7.1 Configuring FTP/SFTP Service ............................................................... 3-84
3.7.2 Configuring the SYSLOG NBI ................................................................. 3-85
3.7.3 Configuring Wireline IMS CORBA NAF .................................................... 3-87
Chapter 4 Configuration Information Import/Export ............................... 4-1

4.1 Exporting the Configuration Information .............................................................. 4-1
4.2 Importing the Configuration Information .............................................................. 4-1
Chapter 5 Configuring Database Connection Information .................... 5-1

Chapter 6 NTP Server Configuration ........................................................ 6-1
6.1 NTP Solution ..................................................................................................... 6-1
6.2 Configuring the Clock Source ............................................................................. 6-4
Chapter 7 Alarm Forwarding Installation ................................................ 7-1

7.1 Configuring the Server ....................................................................................... 7-1
7.1.1 Configuring the Mail Forwarding Mode ...................................................... 7-1
7.1.2 Configuring Short Message Sending Modes .............................................. 7-3
7.2 Configuring the Client ....................................................................................... 7-13
Chapter 8 Configuration of the Authentication Mode ............................. 8-1

8.1 Network Architecture Mode ................................................................................. 8-1
8.2 Installing the Cisco ACS ..................................................................................... 8-1
8.3 Configuring the Cisco ACS ................................................................................8-11
8.4 Configuring the U31 R22 Authentication Type ................................................... 8-17
Chapter 9 Configuring LDAP Authentication .......................................... 9-1

Chapter 10 Querying Installation Information ...................................... 10-1
Chapter 11 Distributed Performance Data Collection ........................... 11-1
11.1 Overview.........................................................................................................11-1
11.1.1 Introduction ...........................................................................................11-1
11.1.2 Distributed Collection Subsystem............................................................11-2
11.2 Distributed Performance Data Collection Solutions ............................................11-3
11.2.1 N + N Hot Standby.................................................................................11-4
11.2.2 N + K Cold Standby ...............................................................................11-5
11.3 Installation Overview........................................................................................11-6
11.3.1 Installation Plan .....................................................................................11-6
11.3.2 Hardware Architecture ...........................................................................11-6
11.3.3 Installation Flow.....................................................................................11-7
11.4 Performance Data Collection Server Configuration and Collector Installation .......11-7
11.4.1 Configuring the Distributed Performance Data Collection Server...............11-7
11.4.2 Installing a Collector ..............................................................................11-9
II

11.4.3 Starting a Collector .............................................................................. 11-11
11.5 Distributed Performance Data Collection Management..................................... 11-12
11.5.1 Managing a Collector ........................................................................... 11-12
11.5.2 Managing NE Load .............................................................................. 11-14
Glossary .......................................................................................................... I
III

This page intentionally left blank.
IV

About This Manual
Manual Description
This manual describes how to configure the configuration center of the NetNumenTM U31
R22 unified network management system.
Intended Readers
This manual is intended for:
l Planning engineers
l NMS monitoring personnel
l Maintenance engineers
What Is in This Manual

This manual contains the following chapters:
Chapter 1, Overview of the Describes the configuration center of the U31 R22 and the
Configuration Center related functions.
Chapter 2, Common Configurations Describes how to configure the common functions for the U31
R22 server.
Chapter 3, Product Configurations Describes the configuration items of the U31 R22 product.
Chapter 4, Configuration Describes how to import and export the configuration

Information Import/Export information.
Chapter 5, Configuring Database Describes how to connect the database.

Connection Information
Chapter 6, NTP Server Describes how to configure the NTP server.

Configuration
Chapter 7, Alarm Forwarding Describes how to configure the alarm forwarding server and
Installation the client.
Chapter 8, Configuration of the Describes how to configure U31 R22 authentication.

Authentication Mode
Chapter 9, Configuring LDAP Describes how to configure LDAP authentication.

Authentication
Chapter 10, Querying Installation Describes how to query the U31 R22 installation information.
Information
Chapter 11, Distributed Describes the distributed performance data collection.

Performance Data Collection

Conventions
This manual uses the following conventions.
Caution: indicates a potentially hazardous situation. Failure to comply can

result in moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a topic.
II

Chapter 1
Overview of the
Configuration Center
The U31 R22 provides the sever and client configuration centers that provide visualized
windows. You can view or set the related parameters of the system in the window.
l The server configuration center is used to set the U31 R22 server parameters.
l The client configuration center is used to set the U31 R22 client parameters.
Server Configuration Center
Note:
Before enabling the server configuration center, you must exit the U31 R22 server and the
U31 R22 client first.
l Enabling the server configuration center on Windows

On the computer where the U31 R22 server is installed, select Start > All Programs >
NetNumen(TM) U31 Unified Network Management System > U31 Config Center.
The NetNumen U31 Unified Network Management System - Configuration Center
window is displayed, see Figure 1-1.
1-1

NetNumen™ U31 R22 System Configuration Guide
Figure 1-1 NetNumen U31 Unified Network Management System - Configuration

Center Window
l Enabling the server configuration center on Solaris and Linux

1. Log in to the server where the U31 R22 is installed as the root user.
2. Open the directory installation directory/uif through the terminal.
3. Run the following command to enable the server configuration center.
sh.runPlugCenter.sh
Client Configuration Center

On the computer where the U31 R22 client is installed, select Start > All Programs
> NetNumen(TM) Unified Management System > NetNumen Config Center. The
NetNumen U31 Unified Management System - Configuration Center window is
displayed, see Figure 1-2.
1-2

Chapter 1 Overview of the Configuration Center
Figure 1-2 NetNumen U31 Unified Management System - Configuration Center Window
1-3

1-4

Chapter 2
Common Configurations
Table of Contents
Configuring Common Properties ................................................................................2-1
Configuring the Console ...........................................................................................2-14
Configuring the Unified Northbound Interface ..........................................................2-16
Configuring Symbol Localization ..............................................................................2-19
Configuring the System Hierarchy ...........................................................................2-20
Updating the License File ........................................................................................2-21
2.1 Configuring Common Properties

2.1.1 Configuring the Server
This procedure describes how to set common properties for the server.
Context
For the common property descriptions of the server, refer to Table 2-1.
Note:
The common properties of the server can be divided into global properties and advanced
properties. By default, advanced configuration items are hidden. You can click the Show
Advanced button to show advanced configuration items.
2-1

Table 2-1 Common Property Descriptions
Parameter Description
Global Basic Main node IP If the IP address of the U31 R22 server is
configuration configuration changed, the parameter needs to be modified.
This address must not be set to 127.0.0.1, and it
must be set to an actual IP address.
Use NAT Enables or disables network address translation.

This parameter is configured when a server
has multiple network interface cards and IP
addresses.
l Yes: indicates that the network address
translation is enabled.
l No: indicates that the network address
translation is disabled.
When the When the NAT function is used to automatically

NAT function obtain IP addresses, the IP address specified in
is used to this configuration item will not be obtained.
automatically Multiple IP addresses are separated by a
obtain IP semicolon, and the host name can be used.
addresses, the
IP address
specified
in this
configuration
item will not be
obtained
UMD timing Specifies the start time of UMD (one-key failure

collection start information collection) collecting EMS logs.
time Format of the start time for
UMD scheduled collection:
HH:mm:ss(HH:00–23,mm:00–59,ss:00–59).
Other The default value is recommended if no special

parameters configuration is required.
Clock Syn- Clock synchro- Enables or disables the clock synchronization

chronization nization detec- detection function.
tion switch l Yes: This function is enabled. The system
checks whether the server is synchronized
with the external clock source regularly. If
not, the system sends a warning alarm.
l No: This function is disabled.
2-2

Chapter 2 Common Configurations
Clock synchro- Cycle for checking whether the clock is

nization detec- synchronized between the EMS server and the
tion cycle external clock source.
This parameter is valid only when Clock
synchronization detection switch is enabled.
Range: 30–1440 minutes.
Threshold of Time offset threshold for determining whether

clock synchro- the clock is synchronized between the EMS
nization time server and the external clock source. When the
offset time offset is higher the threshold, the clock is
determined to be asynchronous.
This parameter is valid only when Clock
synchronization detection switch is enabled.
Range: 1–3600 seconds.
Switch of au- Determines whether to enable automatic

tomatic syn- synchronization when the time offset between
chronization if the EMS server and the external clock source is
time offset is higher than the threshold.
higher than the l Yes: The automatic synchronization is
threshold enabled.
l No: The automatic synchronization is
disabled.
SNMP SNMP proxy l Yes: enables the unified northbound SNMP

availability proxy.
l No: disables the unified northbound SNMP
proxy.
Other parameters of SNMP can be set only
when the parameter is set to Yes.
Other If SNMP proxy availability is enabled, these

parameters parameters need to be set.
File Transfer The type of Two types of file transfer are provided: FTP and
Configuration file transfer SFTP.
(FTP/SFTP)
FTP When the type of file transfer is FTP, this

Configuration configuration is valid.
l ftp Pport: If this configuration item is
modified, the corresponding item on the
firewall must be modified. Range: 0–65535.
l Range of FTP data link ports: The maximum
value should be set to 20979, and the
2-3

minimum value should be set as required

to avoid port conflict.
The maximum number of FTP data link
ports must be equal to or greater than the
maximum number of FTP/SFTP sessions.
If this configuration item is modified, the
corresponding item on the firewall must be
modified.
l The maximum value of FTP/SFTP session
counts: Sets the maximum number of
connections for the FTP/SFTP server.
l FTP mode: 0 indicates that the default data
link port number and range are used. 1
indicates that the local port range special
for the active mode is used. 2 indicates that
the operating system automatically selects
the local port, and it is applicable to the
scenarios where the firewall does not need
to be enabled.
l Active mode-specific local port range: Sets
the local port range special for the active
mode.
l Whether to start northbound FTP server:
Sets whether to enable the independent
northbound FTP server.
l Northbound FTP service port: If the
northbound FTP server is enabled,
the service port needs to be set. If
this configuration item is modified, the
corresponding item on the firewall must be
modified.
SFTP When the type of file transfer is SFTP, this

Configuration configuration is valid.
SFTP server port: Sets the port number of
the SFTP server. If this configuration item is
modified, the corresponding item on the firewall
must be modified.
Whether to l Yes: The FTP and SFTP servers are started

start FTP and simultaneously.
SFTP server l No: The FTP and SFTP servers are not
simultaneously started simultaneously.
The default: yes.
2-4

Log Log file Enables or disables log record.

configuration The logs that can be recorded include:
l DB log
l OS log
l netnumen log
l FTP/SFTP log
l FMSNMP log

Forward Forward type There are seven forwarding types, and the
default type is the alarm box.
l Alarm Box Forward
l GSM Modem Forward
l SMPP Forward
l CMPP Forward
l CMPP V3.0 Forward
l SGIP Forward
l SMGP Forward
The corresponding configurations of the
forwarding type you have set can be validated
only.
Country code All the SMS forwarding types require the country
code.
Mail Forward For details, refer to 7.1.1 Configuring the Mail

Forwarding Mode .
Whether use l Yes: The CMPP V3.0 protocol is used.

CMPP V3.0 l No: The CMPP protocol of an earlier version
is used.
Alarm Box For details, refer to 7.1.2.7 Configuring Alarm

Forward Box Forwarding Mode .
GSM Modem For details, refer to 7.1.2.1 Configuring GSM

Forward Modem Forwarding Mode .
SMPP For details, refer to 7.1.2.2 Configuring SMPP

Forward Forwarding Mode .
CMPP For details, refer to 7.1.2.3 Configuring the

Forward CMPP Forwarding .
CMPP V3.0 For details, refer to 7.1.2.4 Configuring CMPP3.0

Forward Forward.
2-5

SGIP Forward For details, refer to 7.1.2.5 Configuring SGIP

Forwarding Mode .
SMGP For details, refer to 7.1.2.6 Configuring SMGP

Forward Forwarding Mode .
Alarm Interval for Interval at which the network element

timed alarm synchronizes the current alarms at a specified
synchroniza- time (unit: hour).
tion It can be a decimal. Range: 0.5– 240 hours (10
days).

System Task The default value (1 day) is recommended if no

Backup Management: special configuration is required.
Execution
interval for
basic data
backup
Task The default value (60 days) is recommended if

Management: no special configuration is required.
Execution
interval for
whole DB
structure
backup
Task The default value (7 days) is recommended if no

Management: special configuration is required.
Execution
interval for file
backup

Days of
keeping log
data in the
database

Days of
keeping
history
alarm and
2-6

notification in
the database
Days to save The default value (7 days) is recommended if no

small-scale special configuration is required.
original PO
tables in pm
database

medium-scale special configuration is required.
original PO
tables in pm
database

large-scale special configuration is required.
original PO
tables in pm
database
Days to The default value (15 days) is recommended if

save ultra no special configuration is required.
large-scale
original PO
tables in pm
database
Days to save The default value (90 days) is recommended if

small-scale no special configuration is required.
hourly PO
tables in pm
database

medium-scale no special configuration is required.
hourly PO
tables in pm
database

large-scale no special configuration is required.
hourly PO
tables in pm
database

large-scale
2-7

hourly PO
tables in pm
database

small-scale no special configuration is required.
daily PO
tables in pm
database

medium-scale no special configuration is required.
daily PO
tables in pm
database

large-scale no special configuration is required.
daily PO
tables in pm
database

large-scale
daily PO
tables in pm
database
Encrypted Enable ssh for l Yes: The SSH is enabled to forward service.
Communica- MML l No: The SSH is disabled to forward service.
tions Configu- The setting does not affect manually added
ration processes.

System The total Set whether to enable monitoring on whole

Monitoring database database space.
space l Yes: enabled.
monitoring is l No: disabled.
turned on
Security Authentication For details, refer to 8.4 Configuring the U31 R22
type Authentication Type .

2-8

License License center The parameter needs to be set when the EMS is
IP authorized through the License center.
License center Spare IP address of the License center.

spare IP
Authorization Only when the EMS is authorized through the

entity ID License center and it needs to be accurately
defined, does this parameter need to be entered.
The entered value must be the same with the
License file. If no value is not entered, it indicates
that authentication is performed through the
default authentication entity ID.
NE Agent Configure the l 1: indicates that EMS IP address through

Configuration method of ob- which the system communicates to the NE
taining the IP proxy can be obtained. If no such an EMS
address of the IP address can be found, the IP address
EMS server, configured during EMS server installation or
for communi- the IP address corresponding with the host
cation with the name is displayed.
NE agent. l 2: indicates that the system obtains the IP
address of the EMS server entered by the
user during the creation of the NE agent.
Default: 1.
Performance The configuration of this item directly affects the

server performance, it is recommended not to
modify it without special requirements.
Polling Whether to -
print the polling
task execution
progress in
the NMS client
message area
Configure This function supports configuring one or multiple

source ports port addresses. Multiple port addresses should
for SNMP be separated by semicolons.
polling If the value of this configuration item is null, an
idle port will be selected randomly as the source
port for SNMP polling.
If a small number of source ports are configured,
the polling efficiency might be low. Therefore, it
is recommended to configure five source ports
for SNMP polling.
2-9

Topology Switch of l Yes: This function is enabled. The

Management whether to northbound files that the U32 requires are
generate generated at the scheduled time.
northbound l No: This function is disabled. No northbound
files for U32 at files are generated.
the scheduled
time
bn manager OID Use the default value.
PCM Switch Enables or disables the PCM function.

l Yes: The PCM function is enabled.
l No: The PCM function is disabled.
Enable this function if the U31 R22 has to
manage the PCM device.
to set table mode of performance Use the default value.

query client
Process UEP process Common Use the default value.

configuration config Configuration
> WEB
availability flag
Steps
1. From the Configuration Center navigation tree, select Common Configuration >
Common Property. The Sever tab is displayed, see Figure 2-1.
2-10

Figure 2-1 Server Configuration Tab
2. Select the configuration items, for example, Main node IP.

3. Enter an IP address in the Value of config text box.
4. Click Save All. A message box is displayed.
5. Click OK.
– End of Steps –
2.1.2 Configuring the Client

This procedure describes how to set common properties for the client.
Context
For the common property descriptions of the client, refer to Table 2-2.
Table 2-2 Common Property Descriptions
Basic Display logging in l Yes: indicates that SSH login options are displayed
Configuration with SSH on login in the login window.
window l No: indicates that SSH login options are not displayed
in the login window.
2-11

The export l 0: The maximum dimensions of the exported image

strategy of is 2000×2000. If the maximum dimensions of the
topology view exported image exceeds this threshold value, the
topology view is exported in different pages.
l 1: The topology should be exported in a single page,
with no size restrictions. If memory overflows during
the exporting process, the topology view is exported
in different pages. The maximum dimensions of the
exported image is 3000×3000.
Other parameters The default value is recommended if no special

configuration is required.
Alarm Alarm view Set the maximum number of alarm views. The default
maximum number is 10.
Include active -
alarms and
history alarms in
correlated alarm
table
MML Terminal Size of the Value range: 1 to 10240; unit: KB.

imported batch
file
Performance The maximum The default number is 20.

number of data
that can be
displayed on a
curve in the history
performance data
monitor chart
Bear Transfer Show Create Link Link graphical creation is not provided by default, because
Graphics it uses additional displaying resources.
CAC Check l Yes: Route calculation and parameter issue are

verified in accordance with the CAC rules.
l No: Bandwidth is not considered for route calculation,
and if verified bandwidth is insufficient, the parameter
can also be issued.
PCM Switch Enables or disables the PCM function.

l Yes: indicates that the function is supported.
l No: indicates that the function is not supported.
Enable this function when the U31 R22 has to manage the
PCM device.
2-12

Alarm View Maximum Sets the maximum of alarm windows that can be displayed.
The default value is 10.
The default port to connect to the JNDI Default port that is connected to the JNDI server. If this
server configuration item is changed, you need to modify the
corresponding port configuration on the firewall.
Steps
1. In the Configuration Center navigation tree, select Common Configuration >
Common Property. The Server tab is displayed.
2. Click the Client tab. The Client tab is displayed, see Figure 2-2.
Figure 2-2 Client Configuration Tab
3. Select a configuration item, such as Display logging in with SSH on login window.
4. Select the No option for Value of config.

6. Click OK.
2-13

2.2 Configuring the Console

You can manage the console instances and process instances through the system
configuration center.
Steps
Console. The Console area is displayed.
2. Add a process instance.
a. Right-click Console1, and then select Add process instance from the shortcut
menu. The Add process instance dialog box is displayed, see Figure 2-3.
Figure 2-3 Add Process Instance Dialog Box
b. Select a process from the Please select process name list, such as SFTP
Server.
c. Select the creation mode for the process instance. For the description of the
creation mode, refer to Table 2-3.
Table 2-3 Creation Modes for the Process Instance
Creation Mode Description
New process instance Creates a new process instance.
Select process instance Select Select process instance, and then select an
available process instance name.
2-14

d. Click OK.
e. Repeat Steps a through d to add other process instances.
3. Modify a console instance.
a. Right-click Console1, and then select Update console instance from the shortcut
menu. The Update console instance dialog box is displayed, see Figure 2-4.
Figure 2-4 Update Console Instance Dialog Box
b. Enter the IP address of the U31 R22 server in the Input new address text box.
c. Click OK.
4. Delete a console instance.
Caution!
After the console instance is deleted, the corresponding console will not be started.
a. Right-click Console1, and then select Remove console instance from the
shortcut menu. A message box is displayed.
b. Click Yes.
5. (Optional) Detect the port.
2-15

Note:
Before detecting the port, you need to exit the U31 R22 server.
a. Click Detect ports. A message box is displayed.

b. Click Yes.
The conflicting port that is detected is displayed in the window.
6. (Optional) Adjust the port.
Note:
Before adjusting the port, you need to exit the U31 R22 server.
a. Click Adjust ports. A message box is displayed.

b. Click Yes.
2.3 Configuring the Unified Northbound Interface

This procedure describes how to configure the unified northbound interfaces.
Unified northbound interfaces include a unified SNMP interface, unified MML interfaces
(alarm MML and common MML), and unified FTP interface (alarm FTP and performance
FTP).
Steps
1. In the Configuration Center navigation tree, select Common Property > Unified
Northbound Interface Configuration. The Unified Northbound Interface
Configuration area is displayed, see Figure 2-5.
2-16

Figure 2-5 Unified Northbound Interface Configuration Area
2. Select interfaces to be enabled as required. For example, to enable the performance

FTP interface, select the Perform FTP check box.
3. Set the interface parameters. For the parameter descriptions, refer to Table 2-4.
Table 2-4 Interface Parameter Descriptions
Alarm SNMP Enables or disables the alarm SNMP interface.

l To enable the interface, select the Alarm SNMP check box.
l To disable the interface, clear the Alarm SNMP check box.
Whether support l Yes: indicates that the MIB extension file is

Augment MIB File supported. The northbound SNMP interface
provides basic alarm attributes and extended
attributes.
l No: indicates that the MIB extension file is not
supported. The northbound SNMP interface
provides only basic alarm attributes.
If this function is selected, the related codes on the
NMS need to be modified. If not modified, the NMS
may fail to connect the interface after the EMS is
upgraded. Therefore, be careful to use the function.
2-17

SNMP Default Agent The default agent is compatible with all the old
version parameters. It is recommended that you
should use a new SNMP agent.
Other agents Multiple agents can be selected.
Alarm MML Enables or disables the alarm MML interface.

l To enable the interface, select the Alarm MML check box.
l To disable the interface, clear the Alarm MML check box.
Common Enables or disables the common MML interface.

MML l To enable the interface, select the Common MML check box.
l To disable the interface, clear the Common MML check box.
Alarm FTP Enables or disables the alarm FTP interface.

l To enable the interface, select the Alarm FTP check box.
l To disable the interface, clear the Alarm FTP check box.
Start the third FTP Select this check box to enable the third-party FTP,
and set the IP address, IP port, username, password,
and type of the third-party FTP.
Start Time Start time of enabling the alarm FTP interface.
MaxCount Maximum of exported alarms. The default value is

100,000.
Performance Enables or disables the performance FTP interface.

FTP l To enable the interface, select the Performance FTP check box.
l To disable the interface, clear the Performance FTP check box.
Data Storage Days Days of saving the data exported from the northbound
performance FTP interface. The default value is 5.
Start third FTP If this check box is selected, third-party FTP services
are enabled.

5. Click OK.
Note:
The configurations are validated after the common application progress is restarted.
2-18

2.4 Configuring Symbol Localization

This procedure describes how to configure symbol localization.
Steps
Symbol Localization . The Symbol Localization area is displayed, see Figure 2-6.
Figure 2-6 Symbol Localization Area
2. Set the symbol localization parameters. For the parameter descriptions, refer to Table
2-5.
Table 2-5 Parameter Descriptions for the Symbol Localization Configuration
Language Code Select a language code, for example, en stands for English.
Country/Region Code Select a country/region code, for example, US stands for the
United States.
List Separator Select a separator in the list, such as ,.
3. Click Save. A message box is displayed.

4. Click OK.
2-19

2.5 Configuring the System Hierarchy

When the U31 R22 NMS is managed hierarchically, you need to set hierarchical properties
for the U31 R22 server and client.
Steps
Hierarchy Configuration. The Hierarchy Configuration area is displayed, see
Figure 2-7.
Figure 2-7 Hierarchy Configuration Area
2. Configure the system hierarchy. For a description of the related parameters, refer to
Table 2-6.
Table 2-6 Hierarchy Configuration
Client configuration l No-hierarchical: disables the client hierarchical function.

l Hierarchical: enables the client hierarchical function.
2-20

Server configuration l No-hierarchical: disables the client hierarchical function.

l Lower layer: supports being the lower layer of the hierarchy for
enabling the northbound function.
l Upper layer: supports being the upper layer of the hierarch for
enabling the southbound function.
EMB transfer mode Enable or disable the EMB forwarding as required. If the EMB
forwarding is enabled, you must also enable the EMB forwarding for
the upper-level and lower-level NMSs.
l Direct
l Proxy

4. Click OK.
2.6 Updating the License File

You can update the license file through the configuration center when the old license file
is invalid or expired.
Steps
License File Updates. The License File Updates area is displayed.
2. Click Choose License File. The Open dialog box is displayed.
3. Select the license file, and click Open. A message box is displayed.
4. Click OK.
2-21

2-22

Chapter 3
Product Configurations
Table of Contents
Setting NE Types ......................................................................................................3-1
Setting an NE Naming Rule........................................................................................3-2
Configuring Wireline NBI CORBA Interface ...............................................................3-3
Configuring Wireline NBI XML (MTOSI) Interface ....................................................3-10
BN Northbound Interface Configuration ...................................................................3-20
Configuring the BN-IP ..............................................................................................3-78
Configuring the Wireline Common Properties ...........................................................3-84
3.1 Setting NE Types

This procedure describes how to set the NE types displayed in the U31 R22 EMS.
Steps
1. In the Configuration Center navigation tree, select Product Configuration > MOC
Type Configuration. The MOC Type Configuration area is displayed, see Figure
3-1.
Figure 3-1 MOC Type Configuration Area
3-1

2. Select the check box before the NE types to be displayed. Click Save. A message
box is displayed.
3. Click OK.
3.2 Setting an NE Naming Rule

If the naming rules defined for the same NE type are conflicting, you need to re-configure
the NE naming rules.
Steps
1. In the Configuration Center navigation tree, select Product Configuration > Rule
Configuration of MOC Name. The Rule Configuration of MOC Name area is
Figure 3-2 Rule Configuration of MOC Name Area
2. Select a naming rule from the Rule Name list.
3. Click the Save button. A message box is displayed.

4. Click OK.
3-2

Chapter 3 Product Configurations
3.3 Configuring Wireline NBI CORBA Interface

3.3.1 Configuration Steps
In the default configuration, the process of the wireline NBI CORBA interface is not enabled
with the system startup. You can perform the following steps to enable the interface and
configure the parameters including IP address, service ports, and NAT Switch.
Prerequisite
You have exited the U31 R22 server.
Context
After having configured the parameters, set up NetNumen U31 Unified Network
Management System-Console, then the configurations take effect.
Steps
1. In the Configuration Center navigation tree, select Product Configuration >
Wireline NBI Corba Configuration. The Wireline NBI Corba Configuration area
is displayed, see Figure 3-3.
Figure 3-3 Wireline NBI Corba Configuration Area
3-3

2. Select the Wireline CORBA Interface check box, and Wireline CORBA Process is
enabled.
The system automatically adds the process of this interface.
3. According to different situations, select relevant bind mode.
Note:
Bind Console IP is the default bind mode.
If... Then...
l the IP address of the OSS and the Select Bind Console IP.
IP address of theU31 R22 server Console IP is obtained by the system automatically.
are in the same network segment. You can check Console IP through the following
l Wireline CORBA interface uses the steps.
console IP address. i. In the Configuration Center navigation tree, se-
lect Common Configuration > Console.
ii. In the right window, right click Console1, select

Update console instance, check the current con-
sole IP address in the text box of Input new ad-
dress in the open dialog box.
l the IP address of the OSS and the Select Bind User IP.
IP address of theU31 R22 server User IP Configuration must be local IP address of
are in the same network segment. U31 R22 network card which connects the OSS.
l Wireline CORBA interface does
not use the console IP address,
and user specifies the interface IP
address.
the IP address of the OSS and the IP Select Bind HOST Name and set NAT Switch to
address of theU31 R22 server are in true.
different network segments, and NAT
i. HOST Configuration is configured with the U31
switch is needed.
R22 server hostname. The name can only con-
tains the following characters: letters, digits, "–",
and "_". Otherwise, you cannot normally enable
the CORBA interface.
ii. Open hosts-notebook in the following path of

server: C:\Windows\System32\drivers\e
tc. Add a redirection item to the hosts file. The
format of the item is: the IP address of the U31
R22 server before the NAT + the hostname of
3-4

If... Then...
the U31 R22 server. For example, the item is

"129.9.9.9 zte001".
iii. On the computer where the OSS is installed, open

the hosts file of the Windows system and add a
redirection item. The format of the item is: the IP
address of the U31 R22 server after the NAT + the
hostname of the U31 R22 server. For example,
the item is "10.10.10.9 zte001".
Note:
When the U31 R22 server is configured with multiple NICs, and Bind HOST Name is
selected for the wireline NBI CORBA Interface and the OSS binding mode, perform
the following steps:
l Adjust the NIC sequence to make the wireline NBI CORBA Interface NIC and
OSS communication NIC at the front.
l Add the mapping relation between the host name and the host IP to the hosts file
of the U31 R22 server. Add the mapping relation between the U31 R22 host name
and U31 R22 server name after NAT to the hosts file of the OSS server. The host
IP refers to the IP address that enables the U31 R22 server to communicate with
the OSS normally.
4. Set interface parameters by referring to Table 3-1.
Table 3-1 Parameter Descriptions for the Wireline NBI CORBA Interface
EMS Name Identifies the U31 R22 server.

Default value: ZTE/1.
Namingservice Port Port number for wireline NBI CORBA naming service.
Default value: 20266.
Notifyservice Port Port number for wireline NBI CORBA notification

service.
Default value: 20267.
CORBA Service If Using Fixed Port l Yes: The system uses the default CORBA service
Port port "20265".
l No: The CORBA service port is customized.
Default value: Yes.
CORBA Service Port number for CORBA interface service.

Port Default value: 20265.
3-5

NAT Switch true.

l true: If NAT is used in the network, the value is
set to this value.
l false: If NAT is not used in the network, the value
is set to this value.
Default value: false.
Enable Poducts If MSTP\CTN\OTN and (or) IP are selected, the

wireline NBI CORBA interface of the corresponding
product is enabled.
3.3.2 Configuration Example

This procedure uses a typical application scenario to describe how to connect the U31 R22
wireline NBI CORBA interface to the OSS provided by another manufacturer. A CORBA
TESTER is used to simulate the connection with the OSS, which is an OSS simulation tool
developed by ZTE Corporation.
In this example, the IP address of the OSS and the IP address of the U31 R22 server are
not in the same network segment. NAT switch is necessary, and so the binding mode uses
Bind HOST Name.
Prerequisite
l You have exited U31 R22 server.
l The wireline NBI CORBA interface, a software component of the U31 R22, is installed.
l The U31 R22 and the processes of the wireline NBI interface are operating properly.
l The following information is obtained from ZTE Corporation:
à IDL files
à CORBA naming tree information: ID="ZTE/T3", kind = "EMSFactory"

à Basic Data Table
à NetNumen U31 Unified Northbound CORBA Alarm Interface Standards
Context
Figure 3-4 shows an engineering application scenario. The U31 R22 and the wireline NBI
CORBA interface are installed on the same computer. The OSS is installed on another
computer.
The U31 R22 computer locates inside the DCN, and needs the NAT. The computer can
communicate with the OSS only after its IP address is translated to the IP address of the
public network. The IP address of the OSS is a public network IP address.
3-6

Figure 3-4 Interconnection Scenario of the Wireline NBI CORBA Interface
For the detailed information about the NMS and the computer, refer to Table 3-2.
Table 3-2 Interconnection Configuration Information of the Wireline NBI CORBA

Interface and the OSS
NMS Version IP Address Port ID
U31 R22 V12.15.10 Private network IP l Local service port ID of

address before the CORBA interface: 20265
NAT: 129.9.9.9 l Naming service port ID of
Public network CORBA interface: 20266
IP after the NAT: l Notification service port ID of
10.10.10.9 CORBA interface: 20267
OSS (CORBA TESTER) - 10.10.10.10 Naming service port ID of CORBA

interface: 20266
Steps
1. Create a U31 R22 user for the OSS.
Before interconnecting the U31 R22 with the OSS through the wireline NBI CORBA
interface, you need to create a NMS user on the U31 R22 to access the OSS. The
user must have the user permissions of "Administrator Role".
For how to create a NMS user, refer to Section "Creating a User".
2. Configure the wireline NBI CORBA interface.
3-7

Note:
The U31 R22 locates in the private network of the DCN, and has no public network IP.
The NAT is necessary. The computer can interconnect with the OSS only after its IP
address is translated to the IP address of the public network. In this case, Bind HOST
Name must be used as the binding mode between the wireline NBI CORBA interface
and the OSS.
a. On the computer where the U31 R22 server is installed, select Start > Programs
> NetNumen(TM) U31 Unified Network Management System > U31 Config
Center. The NetNumen U31 Unified Network Management System -
Configuration Center window is displayed.
b. From the Configuration Center navigation tree in the left pane, select
Product Configuration > Wireline NBI Corba Configuration. The parameter
configuration area is displayed is in the right pane.
c. In the right pane, select Bind HOST Name.
d. Set the value of HOST Configuration as zte001.
e. Open the hosts file from the following path of server: C:\Windows\System32\d
rivers\etc.
f. Add a redirection item at the end of the hosts file. The format of the item is: "Private
network IP address before the NAT U31 R22 server hostname". In this example,
the item is 129.9.9.9 zte001.
g. Configure the wireline NBI CORBA interface. For the detailed settings, refer to
Table 3-3.
Table 3-3 Wireline NBI CORBA Interface Configuration
Parameter Value
Namingservice Port 20266
Notifyservice Port 20267
CORBAService Port If Using Fixed Port Yes
CORBA Service 20265

Port
NAT Switch true
Enable Products MSTP/CTN/OTN, IP
h. Click Save, and then click OK in the confirmation message.
i. Click to exit the Configuration Center.
3-8

j. In the Start menu, select Programs > NetNumen(TM) U31 Unified Network
Management System > U31 Console, then NetNumen U31 Unified Network
Management System-Console is set up, and the Wireline NBI Corba
Namingservice Process1, Wireline NBI Corba Notifyservice Process1, and
Wireline NBI Corba Process1 are started.
3. Configure the OSS.
a. On the computer where the OSS is installed, open the %system%\system32\d
rivers\etc\hosts file.
b. Add a redirection item at the end of the hosts file. The format of the item is: "Public
network IP address after the NAT U31 R22 server hostname". In this example, the
format is " 10.10.10.9 zte001".
c. Start the U31 R22 server.
d. After the U31 R22 server and the processes of the wireline NBI CORBA interface
operate properly, start the OSS. Configure the interconnection. For the detailed
settings, refer to Table 3-4.
Table 3-4 OSS Interconnection Configuration
Parameter Value
The U31 R22 user name with the user

User name
permission of "Administrator Role".
Password The password of the U31 R22.
Computer name of the wireline NBI The name of the computer where the wireline
CORBA interface NBI CORBA interface is installed. It is zte001
in this example.
Naming service port ID of the wireline NBI The naming service port ID of the wireline NBI
CORBA interface CORBA interface. It is 20266 in this example.
Because the OSS developed by different manufacturers provide different

functions, the information required for interconnecting the OSS with the wireline
NBI CORBA interface may vary. Contact ZTE technical support if necessary.
4. Verify the interconnection result.
a. In the CORBA TESTER login window, enter the username, password, and set
CORBA Type to U3/T3 CORBA.
b. Click the Host Name option button, enter zte001 in the Host Name text box, and
enter 20266 in the Port text box.
c. Click OK. The main window of CORBA TESTER is displayed.

d. Select Notify & Monitor > Alarm Monitor from the menu bar. The Alarm Monitor
tab is displayed, see Figure 3-5.
3-9

Figure 3-5 Notification Report of the Alarm Information
e. Select Alarm > Get All Active Alarms of EMS from the menu bar. The Get All
Active Alarms of EMS tab is displayed, see Figure 3-6.
Figure 3-6 Querying Alarm Information
3.4 Configuring Wireline NBI XML (MTOSI) Interface

3.4.1 Configuration Steps
In the default configuration, the process of the wireline northbound XML (MTOSI) interface
is not enabled with the system startup. You can perform the following steps to enable
the interface and configure the parameters including command parameters and notify
parameters.
Prerequisite
Context
Steps
Wireline NBI XML(MTOSI) Configuration. The Wireline NBI XML(MTOSI)
3-10

Figure 3-7 Wireline NBI XML(MTOSI) Configuration Area
2. Select the Wireline NBI XML(MTOSI) check box, and Wireline NBI XML(MTOSI)
Process is enabled.
The system automatically adds the process of this interface.
Table 3-5 Parameter Descriptions for the Wireline NBI XML (MTOSI) Interface
Common Web Server IP IP address that is used to access the Web server.
Command l The value ".0.0.0" indicates any IP address can access
Parameter the Web server.
Config l If you input a specified IP address, OSS only can acess
the Web server through this IP address.
Max Iteration Maximum of iterators that are generated during the running
Number of the wireline northbound XML (MTOSI) interface.
Default value: 500.
Using HTTP Mode When choosing Using HTTP Send Notificatiion, the HTTP
protocol is recommended.
3-11

The Web service uses the HTTP protocol. Enter the service
port number of the HTTP protocol in the text box of Value of
config of Port Configuration.
Default Value: 20268.
Using HTTPS Mode When Choosing Using JMS Send Notificatiion, the HTTPS
protocol is recommended.
The Web service uses the HTTPS protocol. Enter the service
port number of the HTTPS protocol in the text box of Value
of config of Port Configuration, and set If Authentication
and SSL Security Password.
Default Value: port number is 20268, and If Authentication
is No.
Common Notify Name Sets the identification name of the U31 R22 in the MTOSI
Notify notice.
Parameter Default Value: ZTE/U31.
Config
If Cache Subscribe Enables or disables the notification cache mechanism.
Theme The setting is valid after Using JMS Send Notificatiion is
selected.
l Yes: indicates that the mechanism is enabled. If the
communication between the client and the MTOSI
interface is disconnected, the notifications generated
during the disconnected period will be cached in
the notification proxy. When the communication is
reconnected, the notifications are reported.
l No: indicates that the mechanism is disabled.
Default Value: No.
Heartbeat Interval Interval when the U31 R22 server sends a heartbeat
notification to the Web server (unit: ms).
Connect Time Interval when the wireline northbound XML (MTOSI)

Check Interval interface scans the database (unit: ms).
When a scanning period is over, the interface directly report
or cache the notice in accordance with the cache mechanism
settings.
Using HTTP Send Determines whether the U31 R22 server sends a notification.
Notification Default Value: Using HTTP Send Notificatiion.
UsingJMS Send Determines whether the U31 R22 server sends a notification
Notification through an agent. If the mode is selected, the IP address
and port of JMS must be set.
3-12

4. Click Save, and click OK in the confirmation message box.

3.4.2 Configuration Example

This procedure uses the SoapUI tool as an example to simulate the OSS connection
operations. The connection functions that can be implemented through the SoapUI tool
are: querying NE information of XML(MTOSI) interfaces, enabling notification monitor,
subscribing notifications, and canceling subscribed notifications.
Prerequisite
l The instances of the U31 R22 wireline NBI XML(MTOSI) interface are added.
l The U31 R22 and the processes of the U31 R22 MTOSI XML northbound interface
are operating normally.
l The WSDL files associated with the wireline NBI XML(MTOSI) interface are obtained
from ZTE.
Context
Figure 3-8 shows an engineering application scenario. The wireline NBI XML(MTOSI)
interface uses the HTTP mode to directly report the notice. The Web service protocol
uses the HTTP protocol. The administration domain of the equipment to be managed by
the interface is ZTE/U31(BN).
Figure 3-8 Interconnection Scenario of the Wireline NBI XML (MTOSI) Interface
3-13

Table 3-6 Interconnection Configuration Information of the Wireline NBI XML(MTOSI)

NMS Version IP Address Port Number
OSS (SoapUI) V3.6.1 10.10.10.10 -
U31 R22 V12.15.10 10.10.10.9 20268
Steps
1. Set the parameters of the wireline NBI XML(MTOSI) interface.
b. From the Configuration Center navigation tree in the left pane, select Product
Configuration > Wireline NBI XML(MTOSI) Configuration. The parameter
c. In the right pane, select Wireline NBI XML(MTOSI).
d. Configure the wireline NBI XML(MTOSI) interface. For the detailed settings, refer
to Table 3-7.
Table 3-7 Parameter Descriptions for the Wireline NBI XML(MTOSI) Interface
Parameter Value
Common Web Server IP Enters the IP address of the Web service of the
Command XML(MTOSI) interface accessed by the upper-layer
Parameter network management. The IP address is 10.10.10.9.
Config
Max Iteration 1000
Number
Using HTTP Select this mode, and the port is set as 20268.
Mode
Common Notify Notify Name Uses the default value ZTE/U31.

Parameter
If Cache Yes: enable the cache mechanism.
Config
Subscribe
Theme
Heartbeat Uses the default value 60000 ms.

Interval
Connect Time Uses the default value 3600000 ms.

Check Interval
Using Select this mode which indicates the direct report

HTTP Send mode.
Notification
3-14

e. Click Save, and then click OK in the confirmation message.

f. Click to exit the Configuration Center.
g. Select Start > Programs > NetNumen(TM) U31 Unified Network Management
System > U31 Console, then NetNumen U31 Unified Network Management
System-Console is set up and the Wireline NBI XML(MTOSI) Process is started.
2. Add a project file to the OSS.
a. Start the SoapUI tool. The main window is displayed.
b. In the main window, select File > New soapUI Project. The New soapUI Project
dialog box is displayed.
c. In the Project Name text box, enter the project name.
d. Click Browse.. behind the Initial WSDL/WADL text box. The WSDL files are
displayed.
e. Click OK. The newly added project is under the Projects navigation tree.
f. Repeat Step 2–5 to add WSDL files of other modules.
3. Query NE information.
a. In the Projects navigation tree, select
ManagedElementRetrievalSoapHttpBinding > getAllManagedElements.
b. Double-click getAllManagedElements. In the drop-down menu of the address
bar, select [edit current...]. The Edit endpoint dialog box is displayed.
c. In the text box, modify the IP address to 10.10.10.9, and change the port number
to 20268 as shown in Figure 3-9.
Figure 3-9 Edit endpoint Dialog Box-Modifying the IP Address and Port Number
d. Click OK. The endpoint values in the dialog box is edited to the set values, see
Figure 3-10.
Figure 3-10 GetAllManageElements_M Window
e. Edit items in the .xml file, including the user name and password of assessing
network management system as shown in the Figure 3-11. The format is user
name:password. In this example, user name is admin, and the password is empty.
3-15

Figure 3-11 Input Parameters of Accessing Network Management System
f. Click . The interface performs the query operation.

After querying, the query results of the network elements information are
Figure 3-12 Querying Results
3-16

4. Enable the notification monitoring.

a. In the Projects navigation tree, right-click the project name. Select New
MockService from the shortcut menu. The New MockService dialog box is
displayed.
b. Enter HttpNotify. Click OK. The newly added HttpNotify is under the Projects
navigation tree.
c. In the Projects navigation tree, select NotificationConsumerSoapHttpBinding
> notify. Right-click notify. Select Add to MockService from the shortcut menu.
The Add to MockService dialog box is displayed.
d. From the drop-down list in the Add to MockService dialog box, select the newly
created HttpNotify. Click OK. The Add to MockService dialog box is displayed.
Click OK. The newly added node is display, see Figure 3-13.
Figure 3-13 Newly Added Node
e. In the Projects navigation tree, double-click HttpNotify. The HttpNotify window

is displayed.
f. Click . The MockService Options dialog box is displayed.

g. In the Host text box, enter the IP address of the OSS, which is 10.10.10.10. For
details, see Figure 3-14.
Figure 3-14 MockService Options Dialog Box-Entering the IP Address
h. Click OK. The HttpNotify window is displayed.

i. Click . Enable the MockService to monitor the HTTP report notification.
3-17

In the lower Message Log area, the text results are displayed.
5. Subscribe notifications.
a. In the Projects navigation tree, select NotificationProducerSoapHttpBinding >
subscribe > subscribe.
b. Double-click subscribe. The subscribe window is displayed.
c. Edit items in the .xml file, including the endpoint value, user name and password
of network management system, IP and port of the monitoring notification, and
monitoring notification type. For details, see Figure 3-15.
Table 3-8 Parameter Description for Subscribing Notifications
endpoint Input the IP address and port number of the wireline NBI
XML(MTOSI) interface.
security Input the user name and password of accessing the network
management system, the format is user name:password.
consumerEpr Input the IP address and port number of monitoring notification.
topic Input the type of monitoring notification, including Inventory, Fault,

Protection.
Figure 3-15 Subscribe Window-Modifying Values
d. Click . The system performs the subscription operation. When the operation
is completed, the execution results are displayed in the subscribe window. The
activityStatus value is SUCCESS. The subscriptionID value is 1.
3-18


is displayed. In the Message Log area, the subscribed notifications are updated.
f. Double-click a message. Check the detailed information of the notifications.
6. Cancel subscribed notifications.
a. In the Projects navigation tree, select NotificationProducerSoapHttpBinding >
unsubscribe > Unsubscribe.
b. Double-click Unsubscribe. The Unsubscribe window is displayed.
c. Edit items in the .xml file, including the endpoint, security, subscription ID, and
topic in accordance with Figure 3-16.
Figure 3-16 Unsubscribe Window-Modify the Values of Parameters
d. Click . The system performs the subscription operation. When the operation is
completed, the execution results are displayed in the Unsubscribe window. The
activityStatus value is SUCCESS.
is displayed. In the Message Log area, the notification information is not updated.
f. Click .
3-19

3.5 BN Northbound Interface Configuration

BN northbound interfaces include northbound xTN CORBA interfaces, BN northbound
TMF CORBA interfaces, BN northbound xTN SNMP interfaces, and BN NBI FTP
interfaces.
Operation Support System (OSS) manages the U31 R22 through these interfaces.
Note:
If BN equipment installation is selected in the process of installing the U31 R22 EMS, the
system automatically installs the BN northbound interfaces. The related processes of the
interfaces are not enabled with the system startup.
In the system configuration center, select the check box in front of the corresponding
interface. The system automatically adds the related processes of the interface. The
following procedures describe the configuration steps and applications of BN northbound
interfaces.
3.5.1 Configuring the BN xTN Northbound CORBA Interface

3.5.1.1 Configuration Steps
By default, the process of the BN xTN CORBA interface is not enabled when the system
is started. You can perform the following operations to start the interface and set the
corresponding parameters, including the EMS name, IP address, and service ports.
Prerequisite
Context
After parameter configuration, start NetNumen U31 Unified Network Management
System-Console. The parameter configurations of the interface are applied.
Steps
1. In the Configuration Center navigation tree, select Product Configuration
> BN Northbound Interface Configuration. The BN Northbound Interface
3-20

Figure 3-17 BN Northbound Interface Configuration Area - BN xTN Corba Interface
2. Select the BN xTN Corba check box to enable the BN xTN Corba interface.
3. Select the corresponding binding mode based on different scenarios.
Note:
By default, the Bind Console IP mode is selected.
If... Then...
l The IP address of the OSS and the Click the Bind Console IP option button.
IP address of the U31 R22 server Console IP is read by the system automatically.
are in the same network segment. You can perform the following steps to query Console
l The BN xTN Corba interface uses IP.
the console IP address. i. In the Configuration Center navigation tree, se-
ii. In the right pane, right-click Console1, and se-

lect Update console instance from the shortcut
menu. The Update console instance dialog box
is displayed.
3-21

If... Then...
The IP address displayed in the Input new

address text box is the current console IP
address.
l The IP address of the OSS and the Click the Bind User IP option button.
IP address of the U31 R22 server The value of User IP Configuration must be a local
are in the same network segment. IP address.
l The BN xTN Corba interface uses
an IP address specified by the user
instead of the console IP address.
l The IP address of the OSS and Click the Bind Host Name option button.
the IP address of the U31 R22
i. The value of HOST Configuration is the U31 R22
server are not in the same network
server name, which can only be comprised of let-
segment.
ters, digits, dashes and underscore characters.
l NAT is implemented.
Otherwise, the xTN Corba interface cannot be en-
abled properly.
ii. Open the hosts file in the following path of the

server: C:\Windows\System32\drivers\e
tc. Add a redirection entry to the hosts file. The
format of the entry is: the IP address of the U31
R22 server before NAT + the hostname of the U31
R22 server. For example, the entry is "129.9.9.9
zte001".

redirection entry to the hosts file. The format of
the entry is: the IP address of the U31 R22 server
after NAT + the hostname of the U31 R22 server.
For example, the entry is "10.10.10.9 zte001".
l The IP address of the OSS and the Click the Bind Console IP option button.
IP address of the U31 R22 server Console IP is read by the system automatically.
are in the same network segment. You can perform the following steps to query Console
l The BN xTN Corba interface uses IP.
the console IP address. i. In the Configuration Center navigation tree, se-
ii. In the right pane, right-click Console1, select Up-

date console instance from the shortcut menu.
The Update console instance dialog box is dis-
played.
3-22

If... Then...
The IP address displayed in the Input new

address text box is the current console IP
address.
l The IP address of the OSS and the Click the Bind User IP option button.
IP address of the U31 R22 server The value of User IP Configuration must be the
are in the same network segment. local IP address.
l The BN xTN Corba interface does
not use the console IP address but
is designated by the user.
l The IP address of the OSS and Click the Bind Host Name option button.
the IP address of the U31 R22
server are not in the same network
server name, which can only be comprised by let-
segment.
ters, digits, "–", and "_". Otherwise, the xTN Corba
l NAT switch is implemented.
interface cannot be enabled normally.
ii. Open the hosts files in the following path of

the server: C:\Windows\System32\drivers
\etc. Add a redirection entry to the hosts file.
The format of the item is: the IP address of the
U31 R22 server before the NAT + the hostname
of the U31 R22 server. For example, the entry is
"129.9.9.9 zte001".

redirection entry to the hosts file. The format of the
item is: the IP address of the U31 R22 server after
the NAT + the hostname of the U31 R22 server.
For example, the item is "10.10.10.9 zte001".
Note:
If the U31 R22 server is configured with multiple NICs and the binding mode between
the BN xTN Corba interface and the OSS is set to Bind Host Name, perform the
following operations on the BN xTN CorbaU31 R22 server.
l Adjust the NIC sequence to make the NIC that is responsible for the
communication between the BN xTN Corba interface and the OSS at the front.
l Add the mapping relation between host names and host IP addresses to the hosts
file of the U31 R22 server. Add the mapping relation between the U31 R22 host
names and U31 R22 server IP addresses after NAT to the hosts file of the OSS
server. The host IP addresses refer to the IP addresses that enable the U31 R22
server to communicate with the OSS properly.
3-23

4. Set interface parameters. For a description of the parameters, refer to Table 3-9.
Table 3-9 Parameter Descriptions for the BN xTN Corba Interface Configuration

Default: ZTE/1.
Namingservice Port Port number for naming services.

Default: 21176.
Notifyservice Port Port number for notification services.

Default: 21177.
CORBA If Using Fixed l Yes: The system uses the default CORBA service port
Service Port Port "21175".
l No: The CORBA service port is customized.
Default: Yes.
CORBA Port number for BN xTN Corba interface services.

Service Port Default: 21175.
3.5.1.2 Configuration Example

This procedure describes how to connect BN xTN CORBA interface to an OSS of another
manufacture through a typical application scenario. This procedure uses the CORBA
TESTER as an example to simulate the OSS to perform the interconnections. The CORBA
TESTER is an OSS simulation tool developed by ZTE.
not in the same network segment. In this case, NAT is required and the binding mode uses
Bind Host Name.
Prerequisite
l You have exited the U31 R22 server.
l You have configured an instance for the U31 R22 BN xTN CORBA interface.
l The processes of the U31 R22 and the U31 R22 BN xTN CORBA interface are
operating properly.
l The following documents have been obtained from ZTE:
à IDL files

à Basic data table
à NetNumen U31(BN) NBI xTN CORBA Interface Standards
3-24

Context
For the engineering application scenario, see Figure 3-18. The U31 R22 and the BN xTN
computer.
The U31 R22 computer is located inside the DCN network. The computer can
communicate with the OSS only after the IP address is translated to a public-network IP.
The IP address of the OSS is a public-network IP address.
Figure 3-18 Interconnection Scenario of the BN xTN CORBA Interface
For the detailed settings of the NMS and the computers, refer to Table 3-10.
Table 3-10 Interconnection Configuration Between the BN xTN CORBA Interface and
the OSS
U31 R22 V12.14.10P0 Private-network IP address l Local service port ID of the

2 before NAT: 129.9.9.9 BN xTN CORBA interface:
Public-network IP address 21175
after NAT: 10.10.10.9 l Naming service port ID of the
BN xTN CORBA interface:
21176
l Notification service port
ID of the BN xTN CORBA
interface: 21177
OSS (CORBA - 10.10.10.10 Naming service port ID of the BN

TESTER) xTN CORBA interface: 21176
Steps
3-25

Before interconnecting the U31 R22 to the OSS through the BN TMF CORBA interface,
you must create an EMS user on the U31 R22 to interconnect to the OSS. This user
must have the administrator rights. For the detailed procedure, refer to Creating a
User.
2. Configure parameters for the BN xTN CORBA interface.
Note:
The U31 R22 is located inside the DCN network and has no public-network IP address.
Therefore, NAT technology must be used. The computer can interconnect to the OSS
only after its IP address is translated to a public-network IP address. In this case, Bind
Host name must be used as the binding mode between the BN xTN CORBA interface
and the OSS.
Configuration > BN Northbound Interface Configuration. The parameter
c. From the BN Northbound Interface Configuration navigation tree in the right
pane, select BN xTN CORBA.
d. Click the Bind Host Name option button.
e. Set the value of HOST Configuration to zte001.
f. Open the hosts file in the following directory on the server: C:\Windows\Syste
m32\drivers\etc.
g. Add a redirection entry at the end of the hosts file. The format of the entry is:
"Private network IP address before the NAT U31 R22 server hostname". In this
example, the entry is 129.9.9.9 zte001.
h. Configure the BN xTN CORBA interface. For the detailed settings, refer to Table
3-11.
Table 3-11 BN xTN CORBA Interface Configuration
Parameter Value
Namingservice Port 21176
Notifyservice Port 21177
3-26

Parameter Value
CORBAService Port If Using Fixed Port Yes
CORBA Service 21175

Port
i. Click Save. A confirmation message box is displayed.

j. Click OK.
k. Click to exit the Configuration Center.
l. Select Start > Programs > NetNumen(TM) U31 Unified Network Management
System > U31console. Then NetNumen U31 Unified Network Management
System-Console window is displayed and BN xTN Corba Namingservice
Process1, BN xTN Corba Notifyservice Process1, BN xTN Corba Process1,
and BN xTN CORBA Notify Process1 are started automatically.
3. Set OSS parameters.
a. On the OSS computer, open the %system%\system32\drivers\etc\hosts file.
b. Add a redirection entry at the end of the hosts file " 10.10.10.9 zte001".
c. Run the U31 R22 server.
d. After the U31 R22 server and the process of the BN xTN CORBA interface run
properly, run the OSS. For the OSS interconnection information, refer to Table
3-12.
Table 3-12 OSS Interconnection Information
Information Description
User name Enter the U31 R22 user name with the administrator rights.
Password Enter the U31 R22 password.
Host name of the BN xTN Enter the computer name where the BN xTN CORBA
CORBA interface interface is located. It is zte001 in this example.
Naming service port ID of the Enter the naming service port ID of the BN xTN CORBA
BN xTN CORBA interface interface. It is 21176 in this example.
Because the OSSs developed by different manufacturers provide different

functions, the information required for interconnecting the OSS with the BN xTN
CORBA interface may vary. Contact ZTE technical support when necessary.
4. Obtain and verify the CORBA TESTER tool.
a. Obtain the CORBA TESTER tool from the following directory: installation
path\ums-server\utils\BN_xTN_CorbaTester.
b. In the CORBA TESTER login window, enter the user name and password. Set
CORBA Type to U3/T3 CORBA.
3-27

c. Select the Host Name check box, and then set Host Name to zte001 and set Port
to 21176.
d. Click OK. The main window of the CORBA TESTER is displayed.
e. Select Resource Management > EMS/NE Management. The EMS/ME
Management window is displayed.
The information of all managed NEs is displayed in the window.
f. Select an NE and switch to the Real Time Monitor Information tab. The
information marked in red rectangle (see Figure 3-19) is displayed, indicating that
the CORBA TESTER is connected to the CORBA interface successfully.
Figure 3-19 Real-Time Monitoring Information
g. On the OutPut tab, the detailed information about how the CORBA TESTER is
connected to the CORBA interface is displayed, see Figure 3-20.
3-28

Figure 3-20 Output Information
h. On the Alarm Report tab, the alarms raised on the NE are displayed, see Figure
3-21.
3-29

Figure 3-21 Alarm Report Information

a. In the main window of the CORBA TESTER tool, select Notify & Monitor > Alarm
Monitor. The Alarm Monitor tab is displayed. The alarm information reported by
the EMS is displayed, see Figure 3-22.
b. Select Alarm > Get All Active Alarms of EMS. The Get All Active Alarms of
EMS tab is displayed. Click Synchronize. The alarm information on the EMS is
3-30

3.5.2 Configuring the BN-xTN Northbound TMF CORBA (CTCC)

Interface
The TMF CORBA(CTCC) interface is specially developed for the WDM networks of
China Telecom and is in compliance with the TMF standards. By default, the process
of the BN TMF CORBA(CTCC) Interface is not enabled when the system is started.
You can perform the following operations to start the interface and set the corresponding
parameters, including the EMS name, IP address, and service ports.
Prerequisite
Context
Steps
1. From the Configuration Center navigation tree, select Product Configuration
Figure 3-24 BN Northbound Interface Configuration Area – BN TMF CORBA(CTCC)

Interface
3-31

2. Select the BN TMF CORBA(CTCC) check box to enable the BN TMF CORBA(CTCC)
interface.
Note:
If... Then...
l The IP address of the OSS and Click the Bind Console IP option button.
the IP address of the U31 R22 Console IP is read by the system automatically.
server are in the same network You can perform the following steps to query Console IP.
segment. i. In the Configuration Center navigation tree, select
l The BN TMF CORBA(CTCC) Common Configuration > Console.
interface uses the console IP
ii. In the right pane, right-click Console1, and select Up-
address.
date console instance from the shortcut menu. The
Update console instance dialog box is displayed.
The IP address displayed in the Input new address
text box is the current console IP address.
l The IP address of the OSS and Click the Bind User IP option button.
the IP address of the U31 R22 The value of User IP Configuration must be a local IP
server are in the same network address.
segment.
l The BN TMF CORBA(CTCC)
interface uses an IP address
specified by the user instead of
the console IP address.
l The IP address of the OSS Click the Bind Host Name option button.
and the IP address of the U31
R22 server are not in the same
server name, which can only be comprised of letters,
network segment.
digits, dashes and underscore characters. Otherwise,
the TMF CORBA(CTCC) interface cannot be enabled
properly.
ii. Open the hosts file in the following path of the server:
C:\Windows\System32\drivers\etc. Add a
entry is: the IP address of the U31 R22 server before
NAT + the hostname of the U31 R22 server. For
example, the entry is "129.9.9.9 zte001".
3-32

If... Then...
iii. On the computer where the OSS is installed, open the

hosts file of the Windows system and add a redirection
entry to the hosts file. The format of the entry is: the
IP address of the U31 R22 server after NAT + the host-
name of the U31 R22 server. For example, the entry is
"10.10.10.9 zte001".
Note:
the BN TMF CORBA(CTCC) interface and the OSS is set to Bind Host Name, perform
the following operations on the U31 R22 server.
communication between the BN TMF CORBA(CTCC) interface and the OSS at
the front.
Table 3-13 Parameter Descriptions for the BN TMF CORBA(CTCC) Interface

Configuration

Default: ZTE/1.

Default: 20213.

Default: 20214.
CORBA If Using Fixed l Yes: The system uses the designated port number. The
Service Port Port default value is 20215.
l No: The system automatically assigns the port number.
Default: Yes.
CORBA Port number for BN TMF CORBA(CTCC) interface services.

3-33


This procedure describes how to connect the BN TMF CORBA(CTCC) interface to an
OSS of another manufacture through a typical application scenario. This procedure uses
the Corba Tester FOR TMF CORBA as an example to simulate the OSS to perform the
interconnections.
Bind Host Name.
Prerequisite
l The Corba Tester FOR TMF CORBA tool has been obtained.
l You have configured an instance for the U31 R22 BN TMF CORBA interface.
l The processes of the U31 R22 and the U31 R22 BN TMF CORBA interface are
operating properly.
à IDL files
à Basic data table
à NetNumen U31(BN) NBI TMF CORBA(CTCC) Interface Standards
Context
For the engineering application scenario, see Figure 3-25. The U31 R22 and the BN TMF
computer.
communicate with the OSS only after the IP address is translated to a public-network IP
address through the NAT. The IP address of the OSS is a public-network IP address.
3-34

Figure 3-25 Interconnection Scenario of the BN TMF CORBA(CTCC) Interface
For the detailed settings of the EMS and the computers, refer to Table 3-14.
Table 3-14 Interconnection Configuration Between the BN TMF CORBA(CTCC) Interface

and the OSS
U31 R22 V12.15.10 Private-network IP address l Local service port ID of

before NAT: 129.9.9.9 the TMF CORBA(CTCC)
Public-network IP address interface: 20215
after NAT: 10.10.10.9 l Naming service port ID of
the TMF CORBA(CTCC)
interface: 20213
l Notification service port ID
of the TMF CORBA(CTCC)
interface: 20214
OSS (Corba - 10.10.10.10 Naming service port ID of the TMF

Tester For TMF CORBA(CTCC) interface: 20213
CORBA))
Steps
Before interconnecting the U31 R22 to the OSS through the BN TMF CORBA(CTCC)
interface, you must create an EMS user on the U31 R22 to interconnect to the
OSS. This user must have the administrator rights. For the detailed procedure,
refer to Section 6.7.1 Creating a User in the NetNumen™ U31 R22 Unified Network
Management System Operation Guide (Common Operations).
2. Configure parameters for the BN TMF CORBA(CTCC) interface.
3-35

Note:
Host name must be used as the binding mode between the BN TMF CORBA interface
and the OSS.
pane, select BN TMF Corba(CTCC).
m32\drivers\etc.
h. Configure the BN TMF CORBA interface. For the detailed settings, refer to Table
3-15.
Table 3-15 BN TMF CORBA(CTCC) Interface Configuration
Parameter Value
CORBAService Port Set If Using Fixed Port to Yes and set CORBA Service Port
to 20215.
Namingservice Port Use the default value (20213).
Notifyservice Port Use the default value (20214).

j. Click OK.
3-36

System-Console window is displayed and BN TMF Corba(CTCC)
Namingservice Process1, BN TMF Corba(CTCC) Notifyservice Process1,
and BN TMF Corba(CTCC) Process1 are started automatically.
d. After the U31 R22 server and the process of the BN TMF CORBA(CTCC) interface
run properly, run the OSS. For the OSS interconnection information, refer to Table
3-16.
Enter the computer name where the BN TMF

Host name of the BN TMF
CORBA(CTCC) interface is located. It is zte001 in this
CORBA(CTCC) interface
example.
Naming service port ID of

Enter the naming service port ID of the BN TMF
the BN TMF CORBA(CTCC)
CORBA(CTCC) interface. It is 21176 in this example.
interface

functions, the information required for interconnecting the OSS to the BN TMF
CORBA interface may vary. Contact ZTE technical support if necessary.
4. Verify the CORBA TESTER tool.
a. In the Corba Tester FOR TMF CORBA login window, enter the user name and
password. Set CORBA Type to U3/T3 CORBA.
b. Select the Host Name check box, and then set Host Name to zte001 and set Port
to 20213.
c. Click OK. The main window of the Corba Tester FOR TMF CORBA is displayed.
d. Select Resource Management > EMS/ME Management. The EMS/ME

e. Select an NE and switch to the Real Time Monitor Information tab. The
information marked in the red rectangle (see Figure 3-26) is displayed, indicating
3-37

that the Corba Tester FOR TMF CORBA is successfully connected to the
CORBA interface.
f. On the OutPut tab, the detailed information about how the Corba Tester FOR
TMF CORBA is connected to the CORBA interface is displayed, see Figure 3-27.
3-38

g. On the Alarm Report tab, the alarms raised on the NE are displayed, see Figure
3-28.

a. In the main window of the Corba Tester FOR TMF CORBA tool, select Notify
& Monitor > Alarm Monitor. The Alarm Monitor tab is displayed. The alarm
information reported by the EMS is displayed, see Figure 3-29.
3-39

b. From the Corba Tester FOR TMF CORBA menu, select Alarm > Get ALL Active
Alarms of EMS. The Get ALL Active Alarms of EMS tab is displayed. Click the
Synchronizing All Active Alarm By Cond. Set the alarm level and alarm cause
in the displayed dialog box. The alarm information on the EMS is displayed, see
Figure 3-30.
3.5.3 Configuring the BN-xTN Northbound TMF CORBA (CMCC)

Interface
The TMF CORBA(CMCC) interface is applicable to the WDM networks of China Telecom,
including WDM and CTN equipment, and it is in compliance with the TMF standards. By
default, the process of the BN TMF CORBA(CMCC) is not enabled when the system
is started. You can perform the following operations to start the interface and set the
corresponding parameters, including the EMS name, IP address, and service ports.
Prerequisite
3-40

Context
Steps
1. From the Configuration Center navigation tree, select Product Configuration
Figure 3-31 BN Northbound Interface Configuration Area - BN TMF CORBA(CMCC)

Interface
2. Select the BN TMF CORBA(CMCC) check box to enable the BN TMF CORBA(CMCC)
interface.
Note:
3-41

If... Then...
l The IP address of the OSS and Click the Bind Console IP option button.
the IP address of the U31 R22 Console IP is read by the system automatically.
server are in the same network You can perform the following steps to query Console IP.
segment. i. In the Configuration Center navigation tree, select
l The BN TMF CORBA(CMCC) Common Configuration > Console.
uses the console IP address.
ii. In the right pane, right-click Console1, and select Up-
date console instance from the shortcut menu. The
Update console instance dialog box is displayed.
The IP address displayed in the Input new address
text box is the current console IP address.
l The IP address of the OSS and Click the Bind User IP option button.
the IP address of the U31 R22 The value of User IP Configuration must be a local IP
server are in the same network address.
segment.
l The BN TMF CORBA(CMCC
uses an IP address specified by
the user instead of the console
IP address.
l The IP address of the OSS Click the Bind Host Name option button.
and the IP address of the U31
R22 server are not in the same
server name, which can only be comprised of letters,
network segment.
digits, dashes and underscore characters. Otherwise,
the TMF CORBA(CMCC) interface cannot be enabled
properly.
ii. Open the hosts file in the following path of the server:
C:\Windows\System32\drivers\etc. Add a
entry is: the IP address of the U31 R22 server before
NAT + the hostname of the U31 R22 server. For
example, the entry is "129.9.9.9 zte001".
iii. On the computer where the OSS is installed, open the

hosts file of the Windows system and add a redirection
entry to the hosts file. The format of the entry is: the
IP address of the U31 R22 server after NAT + the host-
name of the U31 R22 server. For example, the entry is
"10.10.10.9 zte001".
3-42

Note:
the BN TMF CORBA(CMCC) interface and the OSS is set to Bind Host Name, perform
the following operations on the U31 R22 server.
communication between the BN TMF CORBA(CMCC) interface and the OSS at
the front.
Table 3-17 Parameter Descriptions for the BN TMF CORBA(CMCC) Interface

Configuration

Default: ZTE/1.

Default: 20213.

Default: 20214.
CORBA If Using Fixed l Yes: The system uses the designated port number. The
Service Port Port default value is 20215.
l No: The system automatically assigns the port number.
Default: Yes.
CORBA Port number for BN TMF CORBA(CMCC) interface services.


This procedure describes how to connect the BN TMF CORBA interface to an OSS of
another manufacture through a typical application scenario. This procedure uses the
Corba Tester FOR TMF CORBA as an example to simulate the OSS to perform the
interconnections.
3-43

Bind Host Name.
Prerequisite
l The Corba Tester FOR TMF CORBA tool has been obtained.
l You have configured an instance for the U31 R22 BN TMF CORBA interface.
l The processes of the U31 R22 and the U31 R22 BN TMF CORBA(CMCC) interface
are operating properly.
à IDL files
à Basic data table
à NetNumen U31(BN) NBI TMF CORBA(CMCC) Interface Standards
Context
For the engineering application scenario, see Figure 3-32. The U31 R22 and the BN TMF
computer.
communicate with the OSS only after the IP address is translated to a public-network IP
address through the NAT. The IP address of the OSS is a public-network IP address.
Figure 3-32 Interconnection Scenario of the BN TMF CORBA(CMCC) Interface
For the detailed settings of the EMS and the computers, refer to Table 3-18.
3-44

Table 3-18 Interconnection Configuration Between the BN TMF CORBA(CMCC)

U31 R22 V12.15.10 Private-network IP address l Local service port ID of the

before NAT: 129.9.9.9 BN TMF CORBA(CMCC)
Public-network IP address interface: 20215
after NAT: 10.10.10.9 l Naming service port ID of
the BN TMF CORBA(CMCC)
interface: 20213
l Notification service port ID of
interface: 20214
OSS(Corba - 10.10.10.10 Naming service port ID of the BN

Tester FOR TMF CORBA(CMCC) interface:
TMF CORBA) 20213
Steps
Before interconnecting the U31 R22 to the OSS through the BN TMF CORBA interface,
you must create an EMS user on the U31 R22 to interconnect to the OSS. This user
must have the administrator rights. For the detailed procedure, refer to Section 6.7.1
Creating a User in the NetNumen™ U31 R22 Unified Network Management System
Operation Guide (Common Operations).
2. Configure parameters for the BN TMF CORBA(CMCC) interface.
Note:
Host name must be used as the binding mode between the BN TMF CORBA interface
and the OSS.
3-45


pane, select BN TMF CORBA(CMCC).
m32\drivers\etc.
h. Configure the BN TMF CORBA interface. For the detailed settings, refer to Table
3-19.
Table 3-19 BN TMF CORBA (CMCC) Interface Configuration
Parameter Value
CORBAService Port Set If Using Fixed Port to Yes and set CORBA Service Port
to 20215.
Namingservice Port Use the default value (20213).
Notifyservice Port Use the default value (20214).

j. Click OK.
System-Console window is displayed and BN TMF Corba(CMCC) Process
1, BN TMF Corba(CMCC) Namingservice Process1, BN TMF Corba(CMCC)
Notifyservice Process1, and BN xTN NBI Common Process 1, and BN TMF
Corba(CMCC) Notify Process 1 are started automatically.
d. After the U31 R22 server and the process of the BN TMF CORBA(CMCC) interface
run properly, run the OSS. For the OSS interconnection information, refer to Table
3-20.
3-46

Enter the computer name where the BN TMF

Host name of the BN TMF
CORBA(CMCC) interface is located. It is zte001 in this
CORBA(CMCC) interface
example.
Naming service port ID of

Enter the naming service port ID of the BN TMF
CORBA(CMCC) interface. It is 21176 in this example.
interface

functions, the information required for interconnecting the OSS to the BN TMF
CORBA(CMCC) interface may vary. Contact ZTE technical support if necessary.
4. Obtain and verify the CORBA TESTER tool.
a. In the Corba Tester FOR TMF CORBA login window, enter the user name and
password. Set CORBA Type to U3/T3 CORBA.
b. Select the Host Name check box, and then set Host Name to zte001 and set Port
to 20213.
c. Click OK. The main window of the Corba Tester FOR TMF CORBA window is
displayed.
d. Select Resource Management > EMS/ME Management. The EMS/ME
e. Select an NE and switch to the Real Time Monitor Information tab. The
information marked in the red rectangle (see Figure 3-33) is displayed, indicating
that the Corba Tester FOR TMF CORBA is successfully connected to the
CORBA interface.
3-47

f. On the OutPut tab, the detailed information about how the CORBA TESTER is
connected to the CORBA interface is displayed, see Figure 3-34.
3-48

g. On the Alarm Report tab, the alarms raised on the NE are displayed, see Figure
3-35.

a. In the main window of the Corba Tester FOR TMF CORBA tool, select Notify
& Monitor > Alarm Monitor. The Alarm Monitor tab is displayed. The alarm
information reported by the EMS is displayed, see Figure 3-36.
3-49

b. Select Alarm > Get All Active Alarms of EMS. The Get All Active Alarms of
EMS tab is displayed. Click the Synchronizing All Active Alarm By Cond. The
alarm information on the EMS is displayed, see Figure 3-37.
3.5.4 Configuring BN xTN SNMP Interface

In the default configuration, the process of the BN-xTN northbound SNMP interface is
not enabled with the system startup. You can perform the following steps to enable the
interface and configure the parameters including IP address, trap address, and protocol
version of proxy.
Prerequisite
Context
3-50

Steps
Figure 3-38 BN Northbound Interface Configuration Area-BN-xTN SNMP
2. Select the BN-xTN SNMP check box, and BN-xTN SNMP is enabled.
3. Set the parameters by referring to Table 3-21.
Table 3-21 Parameter Descriptions for the BN-xTN SNMP Interface

Default value: ZTE/1.
3-51

SNMP SNMP Proxy Port Service port of the SNMP proxy agent.
Proxy Default value: 21178.
Host Con-
Using Console IP If the SNMP proxy host and the EMS console use the same
figuration
(Console IP) IP address, the Using Console IP check box must be
selected.
Default value: Using Console IP.
Using User IP (User If the SNMP proxy host and the EMS console use different IP
IP Configuration) addresses, the Using User IP check box must be selected.
If this item is selected, User IP Configuratiion need to be
configured.
Trap Address Input "the IP address of OSS" and "the port number by which
OSS receives trap", the format is "IP address:port number".
The port number uses the default value "162". For example,
10.8.8.213:162.
When more than one trap address are needed, the format is
"IP1:Port1 IP2:Port2 IP3:Port3...", using space to separate
the different addresses. The system supports 10 addresses
at most.
Proxy Using V1 If the SNMP version is V1, this mode must be selected. The
Community value needs to be set, and the default value
is public.
Community value needs to be set, and the default value
is public.
Security Name, Security Level, Authentication Protocol,
Authentication Password, Encryption Protocol, and
Encryption Password values need to be set.

In this procedure, the interconnection process between the U31 R22 BN xTN SNMP
interface and the OSSs of other manufacturers are described through a typical application
scenario. This manual describes how to simulate the OSS to perform the interconnections
by describing the SNMP interface. SNMP uses the UDP protocol, which uses the IP
interconnection that is applicable to all the network environment.
Prerequisite
3-52

l You have added the instance for the U31 R22 BN xTN SNMP interface.
l Processes of the U31 R22 and the U31 R22 BN xTN SNMP interface are working
properly
l You have acquired MIB files, basic data table and NetNumen U31 (BN) NBI SNMP
Interface Standards from ZTE.
Context
For the engineering application scenario, see Figure 3-39. The U31 R22 and the BN xTN
SNMP interface are installed on the same computer. The OSS is installed on another
computer.
Figure 3-39 Interconnection Scenario of the BN xTN SNMP Interface
For details of the NMS and the computers, refer to Table 3-22.
Table 3-22 Configuration Interconnection Between the BN xTN SNMP Interface and
the OSS
U31 R22 V12.15.10 10.10.10.9 SNMP service port ID: 21178
OSS (SnmpB) V0.8 10.10.10.10 Trap port ID: 162
Steps
Before interconnecting the U31 R22 with the OSS through the BN xTN SNMP interface,
you need to create an NMS user on U31 R22 to interconnect with the OSS. The user
must have the administrator right. Refer to "6.7.1 Creating a User" in NetNumen U31
R22 Unified Network Management System Operation Guide (Common Operations)
for the creation method.
2. Set common parameters for the BN xTN SNMP interface.
3-53

c. In the right pane, select the BN xTN SNMP check box.
d. Configure the BN xTN SNMP interface. For the detailed settings, refer to Table
3-23.
Table 3-23 Descriptions for BN xTN SNMP Interface Configuration
SNMP Proxy Host SNMP Proxy Port Use the default value: 21178.
Configuration
Using User IP (User Select Using User IP, and configure the value
IP Configuration) of User IP Configuration with 10.10.10.9.
Trap Address 10.10.10.10:162
Proxy Using V2 Select Proxy Using V2, and configure

Community with the default value public.
e. Click Save, and then click OK in the confirmation message.
f. Click to exit the Configuration Center.

g. In the Start menu, select Programs > NetNumen U31 Unified Network
Management System > U31 Console. The NetNumen U31 Unified Network
Management System-Console window is displayed and the BN xTN SNMP
Process1 is started.
3. Import MIB Files.
Note:
The OSS NMS import MIB files in accordance with the sequence listed in the
readme.txt file. Read the instructions of the OSS NMS before importing the MIB files.
a. Copy all the MIB files to the mibs folder in the SnmpB installation directory, for
example: C:\Program Files\SnmpB\mibs.
b. Start the SnmpB program.
c. Click the Modules tab.
3-54

d. In the Available MIB modules filed, select all the copied MIB files in step 1. Click
, and the selected MIB files are added into the Loaded MIB modules bar
a. On the Tree tab of SNMPB, click , Agent Profiles dialogue box is displayed.
b. Set parameters by referring to Table 3-24.
Table 3-24 OSS Parameter Configuration
Parameter Description Value
Name The name of the agent server. ZTE/1
Agent IP address of BN xTN SNMP 10.10.10.9

Address/Name interface.
Agent Port SNMP Proxy Port. 21178
Retries Trying times of accessing the 1

interface.
3-55

Parameter Description Value
Timeout Trying time of accessing the 3

interface every time.
Supported SNMP Select the protocol version of SNMPV2

Version SNMP.
Figure 3-40 Agent Profiles dialogue box
c. Choose Options > Preferences... from the main menu, Preferences dialogue
box is displayed.
d. In the left navigation tree, click Traps, and then set Port number in the right pane
as shown in Figure 3-41.
3-56

Figure 3-41 Set Trap Port Number
e. In the Agent Profiles dialogue box, expand profile node on the left.
f. Click Snmpv1/v2c, and set Read community and Write community in the right
pane as shown in Figure 3-42.
Figure 3-42 Set Communities of SNMP V1/V2
Note:
The values of Read community and Write community must be the same. The
default value is public.
g. Click get-bulk, and then set Non repeaters and Max repetitions in the right pane
as shown inFigure 3-43.
3-57

Figure 3-43 Set Get-Bulk
h. Click OK.
If NMS data can be acquired normally, NE information is sent back. All the
information is saved in the zteuManagedElementEntry list in the MIB databse.
Use get, get-next, and get-bulk to query information from MIB.

a. On the Tree tab of SNMPB, expand MIB Tree as shown in Figure 3-44.
Figure 3-44 Expand MIB Tree
b. Right click the MIB node to be queried, such as zteuEMSEntry, and then select
Get Bulk. The query command is delivered, and then the query results are
displayed in the right pane.
c. Right click MIB node, and then select Walk or Table View as shown in Figure
3-45, the results are displayed in the right pane by text or table list.
3-58

Figure 3-45 Select the Displaying Mode of Querying Results
d. In SnmpB, click the Traps tab. The Traps tab is displayed.

e. Select a Trap message from the Trap log column.
l The Trap Content pane displays the Trap message content.
l The Trap info pane displays the detailed information about the Trap message.
For a trap message received by the OSS, see Figure 3-46.
Figure 3-46 Received Trap Message
For the property description about the trap message, refer to Table 3-25.
Table 3-25 Trap Message Property Description
Property Description
Name The name of the Trap information.
Oid The exclusive identifier that identify the Trap message. Detailed
information in the MIB table can be located in the MIB table.
3-59

Property Description
Description Detailed description of the Trap message.
3.5.5 Configuring the Unified FTP (CSV) Inventory Interface

In the default configuration, the process of the unified FTP (CSV) inventory interface is
not enabled with the system startup. You can perform the following steps to enable the
interface and configure the parameters including path of local data saving, local data
keep days, collection time, collection interval, file format, transfer mode, and inventory
file setting.
Prerequisite
Context
Steps
3-60

Figure 3-47 BN Northbound Interface Configuration Area-Unified FTP(CSV)

Inventory Interface
2. Select the BN NBI FTP check box.

3. Select the BN xTN Unified FTP (CSV) Inventory Interface check box.
This interface is enabled.

Table 3-26 Parameter Descriptions for the Unified FTP (CSV) Inventory Interface
Path Of Local Data This directory is used to save the data collected in the PULL mode and
Saving the data failed to be transmitted in the PUSH mode.
The default path is \ums-server\works\global\runtime\nort
hbound\ftp\bn\unified. The default path cannot be modified.
Local Data Keep Days The period that the data collected in the PULL mode and the data
failed to be transmitted in the PUSH mode are saved under the local
directory.
If the storage period reaches the configured keeping days, the system
deletes the data automatically.
Default value: 7 days.
3-61

Collecting Time Start time of collecting inventory data.

l If the start time of the unified FTP (CSV) inventory interface is
earlier than the delay collection time, the system collects inventory
information at the delay collection time on the day when the unified
FTP (CSV) inventory interface is enabled.
l If the start time of the unified FTP (CSV) inventory interface is
later than the delay collection time, the system collects inventory
information at the delay collection time on the next day when the
unified FTP (CSV) inventory interface is enabled.
Default value: 22:00:00.
Collecting Interval The interval between two collections.

Range: 1-30 (unit: day).
Default value: 1 day.
If Compress File Determines whether the generated inventory data file is compressed.
l Yes: indicates that the inventory data file is compressed.
l No: indicates that the inventory data file is not compressed.
Default value: Yes.
FTP Transfer Mode The following two FTP transmission modes are supported:
l PULL mode: The acquired data is saved under the FTP server
path provided by the NMS (local data directory: installation
directory\ums-server\works\global\runtime\nort
hbound\ftp\bn\unified).
The OSS can log in to the server to acquire needed files.
User name: nbiftpunified, password: zte_ftpunified1, port: 21
l PUSH mode: The NMS uploads the generated files to the FTP
server of the OSS.
If the PUSH mode is selected, configured the IP address, port,
user name, password, and FTP type (FTP or SFTP) of the
specified server. The default port for FTP is 21, and the default
port for SFTP is 22.
If the Use SFTP check box is selected, but the designated server
is the FTP server rather than the SFTP server, the uploading may
fail.
Default value: PULL.
3-62

Inventory File Setting Includes inventory file mode and inventory types.
l Two inventory file modes are provided:
à one type to one file: The system generates multiple .csv files
in accordance with different interface types selected.
à all type to one file: All the information of different interface

types selected are saved in a single .csv file.
This strategy is only supported by four interface types:
ManagedElement, Equipment, EquipmentHolder, or
Terminal Point.
l Inventory types include ManagedElement, EquipmentHolder,
Equipment, Terminal Point, Subnetwork Connection, Cross
Connection, Protect Group, Ethernet Service, Topolink, and VLAN
information.
Default value: inventory file mode is one type to one file, and no
inventory types is selected.

6. Click OK.

This procedure uses a typical application scenario as an example to describe the
interconnection process between the U31 R22 unified FTP (CSV) inventory interface and
the OSS of other manufacturers. This example uses FileZilla as FTP client to illustrate.
Prerequisite
l The U31 R22 and the processes of the U31 R22 northbound FTP interface are
operating normally.
l The following information is obtained from ZTE:
à Basic Data Table
à NetNumen U31(BN) NBI FTP Interface Standards
Context
Figure 3-48 shows an engineering application scenario.
3-63

Figure 3-48 Interconnection Scenario of the Unified FTP (CSV) Inventory Interface
Table 3-27 Interconnection Configuration Information of the FTP and the OSS
NMS Version IP Address
OSS - 10.10.10.10
U31 R22 V12.14.10P02 10.10.10.9
Steps
1. Configure the parameters for unified FTP (CSV) inventory interface.
c. In the right pane, select BN NBI FTP, and expand this node.
d. Select BN xTN Unified FTP (CSV) Inventory Interface.
e. Set the parameters. For a description of the parameters, refer to Table 3-28.
Table 3-28 Unified FTP (CSV) Inventory Interface Configuration
Parameter Value
Local Data Keep Days Use the default value: 7 days.

The system will automatically delete the data which has been kept
in the Path Of Local Data Saving for 7 days .
3-64

Parameter Value
Collecting Time The value is 03:00:00.

l If the start time of the unified FTP (CSV) inventory interface
(xTN) is earlier than 03:00:00, the system collects inventory
information at 03:00:00 on the day when the unified FTP (CSV)
inventory interface (xTN) is enabled.
l If the start time of the unified FTP (CSV) inventory interface
(xTN) is later than 03:00:00, the system collects inventory
information at 03:00:00 on the next day when the unified FTP
(CSV) inventory interface (xTN) is enabled.
Collecting Interval Use the default value: 1 day.
If Compress File Yes: the inventory data file is compressed.
FTP Transfer Mode Use the default value: PULL.

The acquired data is saved under the FTP server path
provided by the NMS (local data directory: installation
directory\ums-server\works\global\runtime\northbo
und\ftp\bn\unified).
The OSS can log in to the server to acquire needed files.
User name: nbiftpunified, password: zte_ftpunified1, port: 21
Inventory File Setting Inventory file mode is one type to one file, and select all the
inventory types including ManagedElement, EquipmentHolder,
Equipment, Terminal Point, Subnetwork Connection, Cross
Connection, Protect Group, Ethernet Service, Topolink, and VLAN.
f. Click Save, and then click OK in the confirmation message.

g. Click to exit the Configuration Center.
h. In the Start menu, select Programs > NetNumen U31 Unified Network
Management System-Console is set up, and BN NBI FTP Process1 is started.
a. On the computer where the OSS is installed, start the FTP client FileZilla.
b. After the U31 R22 server, the processes of the unified FTP (CSV) inventory
interface (xTN), and FileZilla operate properly, input accessing parameters by
referring to Table 3-29.
Table 3-29 Parameter Descriptions for Accessing Information
Parameter Value
Host The IP address of FTP server: 10.10.10.9.
Username The user name of the FTP server: nbiftpunified.
Password The password to log in to the FTP server: zte_ftpunified1.
3-65

Parameter Value
Port The port of the FTP server: 21.
Figure 3-49 Accessing Information of FileZilla
c. Click Quickconnect.
After you log in to the FTP server successfully, you can locate the directory of the
northbound interface data, and access all the files under this directory.
3.5.6 Configuring the FTP (CSV) Performance Interface

In the default configuration, the process of the FTP (CSV) performance interface is not
enabled with the system startup. You can perform the following steps to enable the
interface and configure the parameters including local data save path, data keep days,
collection parameters of managed NE data and performance.
Prerequisite
Context
Steps
3-66

Figure 3-50 BN Northbound Interface Configuration Area-FTP (CSV) Performance

Interface
2. Select the BN NBI FTP check box.

3. Select the BN xTN FTP(CSV) Performance Interface check box.
This interface is enabled.
4. Set the parameters. For a description of the parameters, refer to Table 3-30.
Table 3-30 Parameter Descriptions for the FTP (CSV) Performance Interface
Local data save path This directory is used to save the data collected in the
PULL mode and the data failed to be transmitted in the
PUSH mode.
The default path is \ums-server\works\global\ru
ntime\northbound\ftp\bn\xtn. The default path
cannot be modified.
3-67

Local Data Keep Days The period that the data collected in the PULL mode
and the data failed to be transmitted in the PUSH mode
are saved under the local directory.
If the storage period reaches the configured keeping
days, the system deletes the data automatically.
Default value: 7 days.
Collection Man- Whether to enable the function of managedelement data collection.

agedelement l If the check box is selected, the function of managedelement data
Data collection is enabled. You can configure the detailed collection
parameters.
l If the check box is not selected, the function of managedelement data
collection is disabled.
By default, the check box is not selected.
Collection Time The collection time for the NE data.

l If the start time of the FTP (CSV) performance
interface (xTN) is earlier than the delay collection
time, the system collects the NE information at the
delay collection time on the day that the FTP (CSV)
performance interface (xTN) is enabled.
interface (xTN) is later than the delay collection
time, the system collects the NE information at the
delay collection time on the next day that the FTP
(CSV) performance interface (xTN) is enabled.
Collection Interval The interval between two collections.

Range: 1–30 (unit: day)
If Compress File Determines whether the generated data file is

compressed.
l Yes: indicates that the managed element data file
is compressed.
l No: indicates that the managed element data file
is not compressed.
Default value: Yes.
FTP Transfer Includes two modes:

Mode l PULL mode: The acquired data is saved
under the FTP server path provided by the
NMS (local data directory: installation
directory\ums-server\works\global\run
time\northbound\ftp\bn\united).
3-68

The OSS can log in to the server to acquire needed

files.
User name: nbiftpxtn, password: zte_ftpxtn1, port:
21
l PUSH mode: The NMS uploads the generated files
to the FTP server of the OSS.
If the PUSH mode is selected, configured the IP
address, port, user name, password, and FTP type
(FTP or SFTP) of the specified server. The default
port for FTP is 21, and the default port for SFTP
is 22.
If the Use SFTP check box is selected, but the
designated server is the FTP server rather than the
SFTP server, the uploading may fail.
Collection Whether to enable the function of 15–minute history performance collection.

15min History l If the check box is selected, the function of 15–minute historyl
Performance performance collection is enabled. You can set the detailed collection
Data parameters.
l If the check box is not selected, the function of 15–minute history
performance collection is disabled.
Delay Collecting The collection time for the 15–minute history

Time performance data.
The time set here is the delay collection time relative
to 00:00:00. After the delay collection time is set,
the collection time for an entire day is also set. For
example, if the delay collection time is 03:20:00, the
interval is 2 hours, the collection time for each day is
01:20:00, 03:20:00, ......, 23:20:00. For the detailed
collection rules, refer to section "Specifications for
FTP Interface File" in NetNumen U31 R22Unified
Network Management System Northbound FTP-CSV
Performance Management Interface for Transport
Network (User Guide).
Collection Interval The interval between two collections. Unit: hour.

Available values: 1, 2, 3, 4, 6, 8, and 12.
Default value: 2 hours.
If Compress File Determines whether the generated performance data

file is compressed.
3-69

l Yes: the collected data are generated in

compressed files.
l No: the collected data are generated in files rather
than compressed files.
Default value: Yes.
If Auto Collect The Whether to recollect the performance data of the

Data Of Yesterday previous day.
l Yes: recollect the missed performance data of the
previous day and today.
l No: recollect the missed performance data of today.
Default value: No.
If Save File By Whether to generate a .csv or csv.gz performance file

Managed Element for each NE (when you configure the If Compress File
with Yes, the file format is .csv.gz).
l Yes: the system generates a .csv or csv.gz
performance file for each NE.
l No: all the performance files generated by the
system is saved in one .csv or csv.gz performance
file.
Default value: No.
Filter By The performance item whose data must be collected.

Performance If there are multiple performance items, separate them
Parameters with "," (half-entrance mode).
When you enter no performance item, all the
performance items are collected by default.
For the performance item parameters, refer to the
EMS/NMS performance parameter file.
By default, no performance item is entered.
FTP Transfer FTP transmission mode contains the following two

Mode modes:
l PULL: The data acquired by the NMS is saved
under the FTP server path provided by the NMS
(directory of the local data: installation
time\northbound\ftp\bn\xtn).
The OSS can log in to the server to acquire files.
21
l PUSH: The NMS uploads the generated files to the
FTP server of the OSS .
To use the PUSH mode, you must set the specified
server IP address, port, user name, password and
3-70

FTP type (FTP or SFTP). The default port for FTP

is 21, and the default port for SFTP is 22.
If you select Use SFTP, but the specified server is
the FTP server rather than the SFTP server. The
uploading may fail.
Collection Whether to enable the function of 24–hour history performance data

24h History collection.
Performance l If the check box is selected, the function of 24–hour history performance
Data data collection is enabled. You can set the detailed collection
parameters.
l If the check box is not selected, the function of 24–hour history
performance data collection is disabled.
Delay Collecting The collection time for the 24–hour history performance
Time data.
The time set here is the delay collection time relative
to 00:00:00. After the delay collection time is set, the
collection time for each time is also set. For example, if
the delay collection time is 03:20:00, the interval is 1 day,
the system collects the 24–hour performance data from
00:00:00 of the previous day to 23:59:59 at 03:20:00.
For the detailed collection rules, refer to section
"Specifications for FTP Interface File" in NetNumen U31
R22Unified Network Management System Northbound
FTP-CSV Performance Management Interface for
Transport Network (User Guide).
Collection Interval The interval between two collections.

Range: 1–30 (unit: day).
If Compress File Determines whether the generated performance data

file is compressed.
l Yes: the collected data are generated in
compressed files.
l No: the collected data are generated in files rather
than compressed files.
Default value: Yes.
Automatically Whether to recollect the performance data of the

Collection data previous day.
of past 24 hours l Yes: recollect the missed performance data of the
previous day and today.
3-71

l No: recollect the missed performance data of today.

For details, refer to section "Specifications for
FTP Interface File" in NetNumen U31 R22Unified
Network Management System Northbound FTP-CSV
Performance Management Interface for Transport
Network (User Guide).
Default value: No.
If Save File By Whether to generate a .csv or csv.gz performance file

Managedelement for each NE (when you configure the If Compress File
with Yes, the file format is .csv.gz).
l Yes: the system generates a .csv or csv.gz
performance file for each NE.
l No: all the performance files generated by the
system is saved in one .csv or csv.gz performance
file.
Default value: No.
Filter By The performance item whose data must be collected.

Performance If there are multiple performance items, separate them
Parameters with "," (half-entrance mode).
When you enter no performance item, all the
performance items are collected by default.
For the performance item parameters, refer to the
EMS/NMS performance parameter file.
By default, no performance item is entered.
FTP Transfer FTP transmission mode contains the following two

Mode modes:
l PULL: The data acquired by the NMS is saved
under the FTP server path provided by the NMS
time\northbound\ftp\bn\xtn).
21
l PUSH: The NMS uploads the generated files to the
FTP server of the OSS .
To use the PUSH mode, you must set the specified
server IP address, port, user name, password and
FTP type (FTP or SFTP). The default port for FTP
is 21, and the default port for SFTP is 22.
3-72

If you select Use SFTP, but the specified server is

the FTP server rather than the SFTP server. The
uploading may fail.

6. Click OK.

This section uses a typical application scenario as an example to describe the
interconnection process between the U31 R22 FTP (CSV) performance interface and the
OSS of other manufacturers. This example uses FileZilla as FTP client to illustrate.
Prerequisite
l The processes of the U31 R22 and the U31 R22 northbound FTP interface are
operating normally.
à Basic Data Table
à NetNumen U31(BN) NBI FTP Interface Standards
Context
Figure 3-51 shows an engineering application scenario.
3-73

Figure 3-51 Interconnection Scenario of the FTP (CSV) Performance Interface
Table 3-31 Interconnection Configuration Information of the FTP and the OSS
NMS Version IP Address
OSS - 10.10.10.10
U31 R22 V12.15.10 10.10.10.9
Steps
1. Configure the parameters for FTP (CSV) performance interface.
c. In the right pane, select BN NBI FTP.

d. Select BN xTN FTP (CSV) Performance Interface.
e. Set parameters by referring to Table 3-32.
3-74

Table 3-32 FTP (CSV) Performance Interface) Configuration
Parameter Value
Local Data Keep Days Use the default value: 7 days.

The system will automatically delete the data which
has been kept in the Local data save path for 7
days.
Collection Man- Select the check box, and enable the function of managedelement data
agedelement collection.
Data
Collection Time The value is configured with 03:00:00.
interface (xTN) is earlier than 03:00:00, the
system collects the NE information at 03:00:00
on the day that the FTP (CSV) performance
interface (xTN) is enabled.
interface (xTN) is later than 03:00:00, the
system collects the NE information at 03:00:00
on the next day that the FTP (CSV) performance
interface (xTN) is enabled.
Collection Use the default value: 1 day.

Interval
If Compress File Yes: the collected data are generated in compressed

files.
FTP Transfer Use the default value: PULL.

Mode The acquired data is saved under the
FTP server path provided by the NMS
(local data directory: installation
directory\ums-server\works\global
\runtime\northbound\ftp\bn\united).
The OSS can log in to the server to acquire needed
files.
21.
3-75

Parameter Value
Collection Select the check box, and enable the function of 15–minute history
15min History performance data collection.
Performance
Delay Collecting The value is configured with 03:20:00.
Data
Time
Collection Use the default value: 2 hours.

Interval

files.
If Auto Collect Yes: recollect the missed performance data of the

The Data Of previous day and today.
Yesterday
If Save File No: all the performance files generated by the system
By Managed is saved in one .csv or csv.gz performance file.
Element
Filter By By default, enter no performance item, and all the

Performance performance items are collected.
Parameters

Mode The data acquired by the NMS is saved under
the FTP server path provided by the NMS
directory\ums-server\works\global\runti
me\northbound\ftp\bn\xtn).
21
Collection Select the check box, and enable the function of 24–hour history
24h History performance data collection.
Performance
Delay Collecting Use the default value: 02:00:00.
Data
Time
Collection Use the default value: 1 day.

Interval

files.
Automatically Yes: recollect the missed performance data of the

Collection data of previous day and today.
past 24 hours
If Save File By No: all the performance files generated by the system
Managedelement is saved in one .csv or csv.gz performance file.
3-76

Parameter Value
Filter By By default, enter no performance item, and all the

Performance performance items are collected.
Parameters

Mode he data acquired by the NMS is saved under
the FTP server path provided by the NMS
directory\ums-server\works\global\runti
me\northbound\ftp\bn\xtn).
21
f. Click Save, and then click OK in the confirmation message.

g. Click to exit the Configuration Center.
h. In the Start menu, select Programs > NetNumen U31 Unified Network
Management System-Console is set up, and BN NBI FTP Process1 is started.
a. On the computer where the OSS is installed, start the FTP client FileZilla.
b. After the U31 R22 server, the processes of the FTP (CSV) performance interface
(xTN), and FileZilla operate properly, input accessing parameters by referring to
Table 3-33.
Table 3-33 Parameter Descriptions for Accessing Information
Parameter Value
Host The IP address of FTP server: 10.10.10.9.
Username The user name of the FTP server: nbiftpxtn.
Password The password to log in to the FTP server: zte_ftpxtn1.
Port The port of the FTP server: 21.
Figure 3-52 Accessing Information of FileZilla
c. Click Quickconnect.
3-77

After you log in to the FTP server successfully, you can locate the directory of the
northbound interface data, and access all the files under this directory.
3.6 Configuring the BN-IP

3.6.1 Configuring Performance Collection Granularity
This procedure describes how to configure performance collection granularity.
Collection granularity refers to the execution period of a performance task, including 5
minutes and 15 minutes. The default value is 15 minutes.
Steps
BN-IP Configuration > Performance Collection Configuration Granularity. The
Performance Collection Configuration Granularity area is displayed, see Figure
3-53.
Figure 3-53 Performance Collection Configuration Granularity Area
2. From the Collection Granularity (min) list, select a collection period.

4. Click OK.
3-78

3.6.2 Configuring Deployment Mode for the Performance Collection

Server
This procedure describes how to configure deployment mode for the performance
collection server.
The deployment mode of the server includes: normal deployment patterns, N + N
deployment model, and N + K deployment model.
Steps
1. In the Configuration Center navigation tree, select Product Configuration > BN-IP
Configuration > Performance Collection Server Configuration. The Performance
Collection Server Configuration area is displayed, see Figure 3-54.
Figure 3-54 Performance Collection Server Configuration Area
2. From the Deployment mode list, select a deployment mode.
4. Click OK.
3.6.3 Configuring Customized NE Types

This procedure describes how to configure customized NE types. You can customize NE
types through this function.
3-79

Prerequisite
The NE type file in ZIP format is ready.
Steps
Configuration > Customized NE Type. The Customized NE Type area is displayed,
see Figure 3-55.
Figure 3-55 Customized NE Type Area
2. Click the button. The Open dialog box is displayed.

3. Select the customized NE type file, and click Open to return to the Configuration
Center window.
4. Click the Execute button.
3.6.4 Configuring the Customized Alarm Tool

This procedure describes how to configure the customized alarm tool.
The customized alarm tool provides a user-defined alarm function to manage the
third-party equipment alarms.
Prerequisite
Before customizing alarms, you need to know the related information of Trap messages:
TrapOID, variable OID, variable value, variable type and variable name.
3-80

Steps
Configuration > Customized Alarm Tool.
2. Click the Customized Alarm Tool button. The Customized Alarm Tool dialog box is
displayed.
For a description of the Customized Alarm Tool window, refer to Table 3-34.
Table 3-34 Description for the Customized Alarm Tool Window
To... Do...
Add an alarm tool template

Click .
Import a defined alarm tool

Click .
template parameter to the
table
Export an alarm tool

Click .
template parameter from
the table to the local
directory
Modify an alarm tool Select the alarm tool template parameter in the table, and click
template parameter .
Delete an alarm tool

Select the alarm tool template parameter in the table, and click .
template parameter that
are not required
3. Click the button. The New Alarm dialog box is displayed, see Figure 3-56.
3-81

Figure 3-56 New Alarm Dialog Box
For the alarm parameter descriptions, refer to Table 3-35.
Table 3-35 Alarm Parameter Descriptions
TrapOID The character string consists of dots and digits, and begins with a dot.
Device type Support a single device type or multiple device types. Dots must be
used to separate from multiple device types, for example, ZXR10
2918E, ZXR10 2952E.
Alarm code Value range: 41 to 2147483647.
Alarm name A maximum of 120 characters is allowed.
Alarm or notification Includes Alarm, Restore, and Notification.
Severity Includes Critical, Major, Minor, and Warning.
Alarm type Includes Communications Alarm, Processing Error Alarm, Quality of

Service Alarm, Equipment Alarm, and Environmental Alarm.
4. Click in the Variable Information area. The New Variable dialog box is displayed,
see Figure 3-57.
3-82

Figure 3-57 New Variable Dialog Box
For the variable parameter descriptions, refer to Table 3-36.
Table 3-36 Variable Parameter Descriptions
Variable oid The character string consists of dots and digits, and begins with a dot.
Variable name A maximum of 120 characters is allowed.
Variable type Includes Default, TIMESTAMP, MAC, and DateandTime.
Primary key l If this check box is selected, it indicates that the primary key is
enabled.
l If this check box is cleared, it indicates that the primary key is
disabled.
Enumerate This parameter is optional. If it is selected, the enumeration value

and meaning must be set.
5. Click OK to return the New Alarm dialog box.
6. (Optional) Click the Advan... button to set handling suggestions. The Advanced
7. Click OK to return the Customized Alarm Tool dialog box.
3-83

8. (Optional) Click the button to synchronize the alarm to the database.

3.7 Configuring the Wireline Common Properties

3.7.1 Configuring FTP/SFTP Service
This procedure describes how to configure FTP/SFTP service. Users can use the
FTP/SFTP service provided by the system or external FTP/SFTP service.
Steps
Wireline Common Configuration > FTP/SFTP Service. The FTP/SFTP Service
area is displayed, see Figure 3-58.
Figure 3-58 FTP/SFTP Service Area
l If you need to use the FTP/SFTP service provided by the system, clear the Use
Outside FTP Server and Use Outside SFTP Server check boxes.
l If you need to use external FTP/SFTP service, select the Use Outside FTP
Server or Use Outside SFTP Server check box.
When the external FTP or SFTP server is selected, all the users in the list following
the check box must be added to the FTP or SFTP server.
2. (Optional) Modify the FTP/SFTP service user.
3-84

a. Select the user that you want to modify, and click Modify. The Modify FTP/SFTP
User dialog box is displayed.
b. Modify IP Address, Password and (or) Mai Dir. Click Save. A dialog box is
displayed. Click OK.
3.7.2 Configuring the SYSLOG NBI

This procedure describes how to configure the SYSLOG northbound interface.
Steps
Wireline Common Configuration > SYSLOG NBI Configuration. The SYSLOG
NBI Configuration area is displayed, see Figure 3-59.
Figure 3-59 SYSLOG NBI Configuration Area
2. Select the Enable SYSLOG NBI check box.

3. Click the Add button. The Add SYSLOG Server dialog box is displayed, see Figure
3-60.
3-85

Figure 3-60 Add SYSLOG Server Dialog Box
For the SYSLOG server parameter descriptions, refer to Table 3-37.
Table 3-37 SYSLOG Server Parameter Descriptions
Parameter Name
OSS Name Identifies an OSS.
Host IP address of the SYSLOG server.
Company ID Identifies a company.
Facility Value range: 0 to 23. The default value is 1.
Msg Class Includes Msg Assembler for Pccw, Msg Assembler for Human
Telecom, Mag Assembler for SS, and Universal Msg Assembler. The
default message class is Msg Assembler for Pccw.
Port Value range: 1 to 65536. The default value is recommended.
NE Type Types of network elements managed by the EMS.
4. Click the Confirm button to return to the Configuration Center window.

6. Click OK.
3-86

3.7.3 Configuring Wireline IMS CORBA NAF

This procedure describes how to configure the network application function of wireline IMS
CORBA.
Steps
Wireline Common Configuration > Wireline IMS CORBA NAF Configuration.
The Wireline IMS CORBA NAF Configuration area is displayed, see Figure 3-61.
Figure 3-61 Wireline IMS CORBA NAF Configuration Area
2. Select the Northbound CORBA Specification check box, and select a specification
from the list.
3. Set the CORBA IP address, for example, 10.10.10.10.
Note:
The CORBA IP address must be set to the address that can communicate with external
devices.
3-87

5. Click OK.
3-88

Chapter 4
Configuration Information
Import/Export
Table of Contents
Exporting the Configuration Information .....................................................................4-1
Importing the Configuration Information .....................................................................4-1
4.1 Exporting the Configuration Information

This procedure describes how to export the common configuration items in the
configuration center to the specified directory in XML format. The default directory is
installation directory\uif\export\.
Steps
1. In the Configuration Center navigation tree, select Export or Import > Export. The
Export area is displayed.
2. Click Execute.
4.2 Importing the Configuration Information

This function provides a method for modifying the configuration parameters in batches.
Prerequisite
The uep-config.xml is under the specified file, and the specified default directory is insta
llation directory\uif\import\.
Steps
1. In the Configuration Center navigation tree, select Export or Import > Import. The
Import area is displayed.
2. Click Execute.
4-1

4-2

Chapter 5
Configuring Database
Connection Information
When the database connection information changes, you need to set the related
information in the configuration center.
Steps
1. In the Configuration Center navigation tree, select Database Connection >
Database Connection Configuration. The database connection information is
displayed in the right pane, see Figure 5-1.
Figure 5-1 Database Connection Information Area
2. Set the database connection parameters. For a description of the parameters, refer
to Table 5-1.
5-1

Table 5-1 Parameter Descriptions for Configuring the Database Connection
Database Type Database type of the U31 R22 server, including Oracle and Microsoft
SQL Server.
Oracle Connection Set the following parameters for the Oracle database only:
Type l Sid
l Servicename
Database IP Hostname Enter an IP address or host name of the computer on which the U31
R22 server database is installed.
Database Port Set the port number of the database instance. The default value is
recommended.
If several database instances have been created, use the port number
of the instance used by the U31 R22 system.
Oracle SID or Service Enter the System Identifier (SID) only when the database is an Oracle
Name database.
Database Superuser Enter a superuser name of the database.

Name
Password Enter a password of the superuser.
3. Click Test Data Connection.

A message is displayed, indicating the database is successfully connected. The
database connection information is successfully configured.
4. Click Save.
5-2

Chapter 6
NTP Server Configuration
Table of Contents
NTP Solution ..............................................................................................................6-1
Configuring the Clock Source ....................................................................................6-4
6.1 NTP Solution

Solaris, AIX, and Linux operating systems are installed with the NTP v3 or NTP v4 program
in general. The Windows operating system is installed with the SNTP service. These
systems use NTP v3, NTP v4, and SNTP to create a clock synchronization based on the
operating systems so as to reduce the coupling with the NMS program.
The U31 R22 provides the NTP v4 service program for the Windows system. The Windows
NTP v4 can establish clock service network with Windows NTP v4, Solaris NTP, Aix NTP,
and Linux NTP to provide clock services.
Implementation Solution for the Cross-Operating System Environment

Implementation Solution
l Windows operating system uses the NTPv4 service provided by the NMS platform.
If the current platform is installed with the NTPv4 service in the Windows environment,
you can use this method for the network synchronization.
The NMS platform provides the NTP v4 program for the Windows operating system.
The Windows system that uses the NTP v4 can perform clock synchronization with
the AIX NTP, Solaris NTP, Linux NTP, and Windows NTP v4 networks. Meaning that
the Windows system that uses the NTP v4 can operate as the clock synchronization
server or the client for the AIX NTP, Solaris NTP, Linux NTP, and Windows NTP v4.
The *nix operating system (including Solaris, Linux, and AIX) and the Windows
operating system using the NTPv4 can operate as the NTP client or server. The NTP
client that uses automatic synchronization can operate as the NTP client for other
systems (NTP clock source) simultaneously. See Figure 6-1.
6-1

Figure 6-1 NTPv4 Service Network Provided by the NMS Platform
Note:
If the level of the Linux server does not exceed 15, it still can be used as the clock
source of other NTP client.
l Windows operating system uses the SNTP service provides by the operating system.
The Windows operating system using SNTP can both work as the NTP client and NTP
server.
à When the Windows operating system operates as the NTP client, the server can
be Windows or *nix. Therefore, NTP automatic synchronization can be achieved.
à When the Windows operating system works as the NTP server, if the environment
of the system that requests for synchronization has the *nix system environment
(including Solaris, Linux, and AIX), the NTP client for the *nix must manually
perform synchronizations through the ntpdate command (the *nix that works as
the client must close the local NTP service, and thus cannot work properly as the
NTP client at the same time). You must use the cron service of the *nix for the
automatic synchronization, see Figure 6-2.
Figure 6-2 SNTP Service Network Provided by the Operating System
6-2

Chapter 6 NTP Server Configuration
l Windows operating system uses the SNTP service provided by the NMS platform.
In the engineering environment deployed by the NetNumen unified NMS, if the
Windows operating system without the NTPv4 installed is used as the NTP clock
source, you can enable the SNTP service of the NMS. You must also enable the
SNTP client of the NMS for the environment that synchronizes with the system for so
as to synchronize the NTP client of the NMS. See Figure 6-3.
Figure 6-3 SNTP Service Network Provided by the NMS Platform
Dual-Server Environment Implementation Solution

In the dual-server environment, the system switches between the main server and the
standby server. As the switching proceeds, the system resources (including external
service system process, related services, and external access entrance) also perform the
corresponding switchover. For example, the external floating IP address will be switched
from the source host IP address to the sink host IP address.
Compared to the usual network services, NTP service has one significant difference: After
the local NTP service is enabled, if the local IP address changes, the local NTP service
cannot deal with the requests at the NTP client for the new IP address. You must enable
the NTP server to deal with the requests at the NTP client for the new IP address.
l Solution one: The NTP client synchronizes with the actual IP addresses of the
dual-server
The dual-server system is formed by host A and host B. The host A has a real IP
address, which is 192.168.0.21. The floating IP address that provides services is
192.168.0.31. For the NTP client, the actual IP addresses for host A and B, and the
floating IP address are visible. At this moment, you can set the IPP addresses for the
available NTP server to be the actual IP addresses for host A and B at the NTP client,
that is 192.168.0.11 and 192.168.0.21.
l Solution two: The NTP client synchronizes with the floating IP address
The dual-server system is formed by host A and host B. The host A has a real IP
address, which is 192.168.0.11. The host B also has a real IP, which is 192.168.0.31.
The floating IP address that provides services is 192.168.0.31. For the NTP client,
6-3

the IP addresses for the host A and B are invisible, but the floating IP address for the
dual-server system is visible. At this moment, you can set the available NTP server IP
address to be the floating IP 192.168.0.31 at the NTP client. Locate the NTP service
restart script in the system environments for host A and host B. Add the script into
the resource management for the dual-server software. The resource relies on the
floating IP resource.
6.2 Configuring the Clock Source

The U31 R22 system provides the local clock source and an external clock source. This
procedure describes how to configure the clock source.
Context
l Local clock source: The local clock operates as the clock source to provide clock
service for external devices.
l External clock source: An external clock server serves as a clock source, and the
local server provides clock service for other clients.
Steps
l Enable the local clock source.
1. In the Configuration Center navigation tree, select OS NTP Configuration > OS
NTP Configuration. The OS NTP Configuration area is displayed, see Figure
6-4.
Figure 6-4 OS NTP Configuration Area
2. Click the Enable the local clock source option button.

3. Click the Apply button. A message box is displayed, indicating NTP start success.
4. Click OK.
6-4

Chapter 6 NTP Server Configuration
l Enable an external clock source.

1. In the Configuration Center navigation tree, select OS NTP Configuration > OS
NTP Configuration. The OS NTP Configuration area is displayed.
2. Click the Enable external clock source option button.
3. Enter the IP address of the main clock server in the Main clock server IP text box.
4. (Optional) Select the IP Standby clock server IP check box, and enter the IP
address of the standby clock server.
5. Click the Apply button. A message box is displayed, indicating NTP start success.
6. Click OK.
Note:
To synchronize clock, click the Execute button following Manual
synchronization.
6-5

6-6

Chapter 7
Alarm Forwarding Installation
When you install the alarm forwarding, you must also install anther two software, mail
server and Short Message (SM) center.
Table of Contents
Configuring the Server ...............................................................................................7-1
Configuring the Client...............................................................................................7-13
7.1 Configuring the Server

In order to effectively execute the alarm forwarding rules, you must set related parameters
for the alarm forwarding mail sending mode or SM sending mode at the server U31 R22
client. For example, country code, mail server address, and mail server user name.
7.1.1 Configuring the Mail Forwarding Mode

If you select mail sending mode as the alarm forwarding rule, you must set related
parameters for the mail sending mode in the U31 R22 server.
Steps
Common Property.
2. On the Server tab, select Global Configuration > Forward > Mail Forward. The
mail forwarding configuration area is displayed, see Figure 7-1.
7-1

Figure 7-1 Mail Forwarding Mode Configuration
3. Set values for the configuration items. For a description of the parameters , refer to
Table 7-1.
Table 7-1 Mail Forwarding Configuration
Configuration Item Description
Mail server IP IP address of the mail server.
Mail server port Port of the mail server.
Mail server need auth l Yes: the mail server needs the authentication.
l No: the mail server does not need the authentication.
Mail server username User name for the mail server.
Mail server password Password for the mail user.
Mail server’s FromAddress Mail box for sending mails.
Mail encoding l 1: use the gbk encoding mode.

l 2: use the gb2312 encoding mode.
l 3: use the us-ascii encoding mode.
l 4: use the utf-8 encoding mode.
Mail text format l 1: indicates the text/html format.

l 2: indicates the text/plain format.
Whether use ssl to send mail l Yes: ssl mode is used to send mails
or not l No: ssl mode is not used to send mails
7-2

Chapter 7 Alarm Forwarding Installation
Configuration Item Description
Whether supported ssl l Yes: the server provides the ssl certificate.
certificate by mail server l No: the server does not provide the ssl certificate.
4. Click Save All. A confirmation message box is displayed.

5. Click OK.
7.1.2 Configuring Short Message Sending Modes

When you select short messages to forward alarms, you must set the related parameters
in the U31 R22 server for the SM sending mode.
The following SM sending modes are provided.

l GSM Modem Forward
If the communication protocol of the SM center is GSM, the GSM modem forwarding
mode must be configured.
l SMPP Forward
If the communication protocol of the SM center is SMPP, the SMPP forwarding mode
must be configured.
l CMPP Forward
If the communication protocol of the SM center is CMPP, the CMPP forwarding mode
must be configured.
l SGIP Forward
If the communication protocol of the SM center is SGIP, the SGIP forwarding mode
must be configured.
l SMGP Forward
If the communication protocol of the SM center is SMGP, the SMGP forwarding mode
must be configured.
l Alarm Box Forward
If SMs are forwarded through the alarm box, the alarm box forwarding mode must be
configured.
l Mail Forward
If SMs are forwarded privately, the mail forwarding mode must be configured.
7.1.2.1 Configuring GSM Modem Forwarding Mode

If the communication protocol for the SM center is Global System for Mobile
Communications (GSM), you should select GSM modem forwarding mode and set the
7-3

related parameters, such as GSM Modem equipment serials, GSM part times, and
GSM receiver number.
Steps
Common Property.
2. On the Server tab, select Global Configuration > Forward > Forward type. Select
1 from the Value of config list.
3. On the Server tab, select Global Configuration > Forward > Country Code. Enter
a value in the Value of config text box.
4. On the Server tab, select Global Configuration > Forward > GSM Modem Forward.
The area for configuring the GSM Modem forwarding is displayed, see Figure 7-2.
Figure 7-2 Configuring GSM Modem Forwarding
5. Configure the GSM Modem forwarding.

a. Select a parameter under the GSM Modem Forward node. For example, select
GSM Modem equipment serials.
b. Enter a serial port for sending short messages in the Value of config text box.
c. Refer to step i and step ii to configure other parameters.
7-4

7. Click OK.
7.1.2.2 Configuring SMPP Forwarding Mode

If the communication protocol for the SM center is SMPP, you should select SMPP
forwarding mode and set the related parameters, SMPP IP, SMPP port, and SMPP
username.
Steps
Common Property.
4. On the Server tab, select Global Configuration > Forward > SMPP Forward. The
SMPP forwarding configuration area is displayed, see Figure 7-3.
Figure 7-3 Configuring SMPP Forwarding
5. Configure the SMPP forwarding.

a. Select a parameter under the SMPP Forward node. For example, select SMPP
IP.
b. Enter the IP address of the SMPP gateway in the Value of config text box.
7-5


7. Click OK.
7.1.2.3 Configuring the CMPP Forwarding

If the communication protocol for the SM center is CMPP, you should select CMPP
forwarding mode and set the related parameters, such as CMPP IP and CMPP port.
Steps
Common Property.
4. On the Server tab, select Global Configuration > Forward > CMPP Forward. The
CMPP forwarding configuration area is displayed, see Figure 7-4.
Figure 7-4 Configuring CMPP Forwarding
5. Configure the CMPP forwarding.
7-6

a. Select a parameter under the CMPP Forward node. For example, select CMPP
IP.
b. Enter the IP address of the CMPP gateway in the Value of config text box.
7. Click OK.
7.1.2.4 Configuring CMPP3.0 Forward

If the communication protocol for the SM center is CMPP3.0, you should select CMPP3.0
forwarding mode and set the related parameters, such as CMPP V3.0 IP and CMPP port.
Steps
Common Property.
4. On the Server tab, select Global Configuration > Forward > Wether use CMPP
V3.0. Select Yes.
5. On the Server tab, select Global Configuration > Forward > CMPP V3.0 Forward.
The CMPP 3.0 forwarding configuration area is displayed, see Figure 7-5.
7-7

Figure 7-5 Configuring CMPP3.0 Forwarding
6. Configure the CMPP3.0 forwarding.

a. Select a parameter under the CMPP3.0 Forward node. For example, select
CMPP V3.0 IP
b. Enter the IP address of the CMPP gateway in the Value of config text box.
c. Refer to step i and step ii to configure other parameters
8. Click OK.
7.1.2.5 Configuring SGIP Forwarding Mode

If the communication protocol for the SM center is SGIP, you should select SGIP forwarding
mode and set the related parameters, such as SGIP IP, SGIP port, and Login name.
Steps
Common Property.
7-8

4. On the Server tab, select Global Configuration > Forward > SGIP Forward. The
SGIP forwarding configuration area is displayed, see Figure 7-6.
Figure 7-6 Configuring SGIP Forwarding
5. Configure the SGIP forwarding.

a. Select a parameter under the SGIP Forward node. For example, select SGIP IP.
b. Enter the IP address of the SGIP gateway in the Value of config text box.

7. Click OK.
7.1.2.6 Configuring SMGP Forwarding Mode

If the communication protocol for the SM center is SMGP, you should select SMGP
forwarding mode and set the related parameters, such as SMGP IP, SMGP port, and
Login name.
Steps
Common Property.
7-9

4. On the Server tab, select Global Configuration > Forward > SMGP Forward. The
SMGP forwarding configuration area is displayed, see Figure 7-7.
Figure 7-7 Configuring SMGP Forwarding
5. Configure the SMGP forwarding.

a. Select a parameter under the SMGP Forward node. For example, select SMGP
IP.
b. Enter the IP address of the SMGP gateway in the Value of config text box.

7. Click OK.
7.1.2.7 Configuring Alarm Box Forwarding Mode

When you select the alarm box to forward SMs, you need to set the related parameters.
7-10

Steps
Common Property.
4. On the Server tab, select Global Configuration > Forward > Alarm Box Forward.
The alarm box forwarding configuration area is displayed, see Figure 7-8.
Figure 7-8 Configuring Alarm Box Forwarding
5. Set the IP address of the alarm box for forwarding SMs.

7. Click OK.
7.1.2.8 Configuring Mail Forwarding Mode

In this forwarding mode, you can send SMs to the designated EMB privately.
Steps
1. From the Configuration Center navigation tree, select Common Configuration >
Common Property.
7-11

2. On the Server tab, select Global Configuration > Forward > Forward type. Set
Value of config to 5.
3. Select Global Configuration > Forward > Country Code. Enter a value in the Value
of config text box.
4. Select Global Configuration > Forward > GSM Modem Forward, see Figure 7-9.
Figure 7-9 GSM Modem Forwarding Mode
5. Set the related parameters of the GSM modem forwarding mode.

a. Select the parameter item that needs to be set, for example, GSM Modem
equipment serials.
b. In the Value of config text box, enter the serial port used to sending SMs.
c. Refer to Step a through Step b to set other parameter items.

7. Click OK.
7-12

7.2 Configuring the Client

In the U31 R22 client, after you have created an alarm forwarding rule, the alarms
that comply with the conditions are sent to the specified personnel in mails or SMs in
accordance with the rules.
Note:
For the client configuration method, refer to the “alarm forwarding” and “Alarm Rule
Management” inNetNumen™ U31 R22 Unified Network Management System Operation
Guide (Common Operations).
7-13

7-14

Chapter 8
Configuration of the
Authentication Mode
Table of Contents
Network Architecture Mode ........................................................................................8-1
Installing the Cisco ACS .............................................................................................8-1
Configuring the Cisco ACS .......................................................................................8-11
Configuring the U31 R22 Authentication Type .........................................................8-17
8.1 Network Architecture Mode

For the network architecture of the U31 R22 NMS that uses the TACACS + authentication
mode for login, see Figure 8-1.
Figure 8-1 Network Architecture
The principle of the U31 R22 NMS that uses the TACACS + authentication mode for logging
in is as follows:
1. The U31 R22 client sends the login request to the U31 R22 server.
2. The U31 R22 server (TACACS + client) invokes the TACACS + authentication mode
to acquire the TACACS + server address, port, and communication key.
3. The connection between the U31 R22 server (TACACS + client) and the TACACS +
server is established.
4. TACACS + server verifies the transmitted user name and password, and then returns
to the verification status.
5. The U31 R22 sever (TACACS + client) checks whether the authentication passes.
l If the authentication passes, the U31 R22 client is logged in successfully.
l If the authentication cannot pass, the U31 R22 client cannot be not logged in.
8.2 Installing the Cisco ACS

This procedure describes how to install the Cisco ACS.
8-1

Prerequisite
You have installed the Java virtual machine.
Steps
1. Double-click Setup.exe. The Setup dialog box is displayed, see Figure 8-2.
Figure 8-2 Setup Dialog Box
2. Click ACCEPT. The Welcome dialog box is displayed, see Figure 8-3.
8-2

Chapter 8 Configuration of the Authentication Mode
Figure 8-3 Welcome Dialog Box
3. Click Next. The IMPORTANT NOTICE dialog box is displayed, see Figure 8-4.
8-3

Figure 8-4 IMPORTANT NOTICE Dialog Box
4. Click Next. The Before You Begin dialog box is displayed, see Figure 8-5.
8-4

Figure 8-5 Before You Begin Dialog Box
5. Select all the options, and then click Next. The Choose Destination Location dialog
box is displayed, see Figure 8-6.
8-5

Figure 8-6 Choose Destination Location Dialog Box
6. Set the installation path for the program, and then click Next. The Authentication
Database Configuration dialog box is displayed, see Figure 8-7.
8-6

Figure 8-7 Authentication Database Configuration Dialog Box
7. Select an ACS account type, and then click Next.
After the installation is finished, the Advanced Options dialog box is displayed, see
Figure 8-8.
8-7

Figure 8-8 Advanced Options Dialog Box
8. Select all the options, and then click Next. The Active Service Monitoring dialog box
is displayed, see Figure 8-9.
Figure 8-9 Active Service Monitoring Dialog Box
8-8

For the parameter configuration descriptions, refer to Table 8-1.
Table 8-1 Parameter Configuration Description
Enable Log-in Monitoring If you select it, a detection is required when you log in to the ACS.
Enable Mail Notifications If you select it, mail reminder is enabled.
9. Click Next. The CiscoSecure ACS Service Initiation dialog box is displayed, see
Figure 8-10.
Figure 8-10 CiscoSecure ACS Service Initiation Dialog Box-1
10. Set a password, and then click Next. The CiscoSecure ACS Service Initiation dialog
8-9

Figure 8-11 CiscoSecure ACS Service Initiation Dialog Box-2
11. Click Next. The Setup Complete dialog box is displayed, see Figure 8-12.
Figure 8-12 Setup Complete Dialog Box
8-10

12. Click Finish.

Result
After the Cisco ACS installation is finished, the related services will be enabled. You can
view the corresponding services in the Windows system service. For the main Cisco ACS
services, see Figure 8-13.
Figure 8-13 Cisco ACS Services
8.3 Configuring the Cisco ACS

After the installation is finished, you must configure the Cisco ACS to achieve the
authentication function.
Steps
1. Open a Web browser, and enter http://127.0.0.1:2002 in the address bar to log in to
the ACS system.
2. Set an administrator account.
a. Click Administration control. The Administration control dialog box is
Figure 8-14 Adding an Administrator
8-11

b. Click Add Administrator. The Add Administrator dialog box is displayed.

c. Set an administrator name, and then click Submit.
Note:
Set the other parameters as needed.
3. Add the TACACS+ client.

a. Click Network Configuration. The Network Configuration dialog box is
Figure 8-15 Network Configuration Dialog Box
b. Click Add Entry below AAA Client. The Add AAA Client dialog box is displayed,
see Figure 8-16.
8-12

Figure 8-16 Add AAA Client Dialog Box
c. Set a client name, IP address, and key. Click Submit + Apply.
Note:
Keep the default values for other parameters.
4. Set the TACACA+.

a. Click Interface configuration. The Interface configuration dialog box is
Figure 8-17 Interface configuration Dialog Box
8-13

b. Click the TACACS+ (Cisco) link. The TACACS+ (Cisco) dialog box is displayed,
see Figure 8-18.
Figure 8-18 TACACS+ (Cisco)
c. Select the related options as needed. Click Submit.

5. Set a user group.
a. Click Group Setup. The Group Setup dialog box is displayed, see Figure 8-19.
8-14

Figure 8-19 Group Setup
b. Select a group from the Group list. Click Edit Settings. The Group Settings
c. Set the related information for the user group, see Figure 8-20.
Figure 8-20 Setting a User Group Level
Note: Set the user group level parameters as needed. Keep the default values
for other parameters.
d. Click Submit + Restart.

6. Add a user.
a. Click User Setup. The Select dialog box is displayed, see Figure 8-21.
Figure 8-21 Select Dialog Box
8-15

Note: The user name must be the same as the user name for logging in to
the EMS.
b. Enter a user name in the User text box. Click Add/Edit. The User Setup window
is displayed.
c. Set the related user information, see Figure 8-22.
Figure 8-22 User Setup
8-16

Note: Set the user group level parameters as needed. Keep the default values
for other parameters.
d. Click Submit.
8.4 Configuring the U31 R22 Authentication Type

The U31 R22 NMS provides authentication modes for multiple login modules. You can
select an authentication mode as needed. The following procedure describes how to
configure the tacacs authentication.
Context
The U31 R22 NMS uses the uep authentication by default.
Steps
1. Configure the TACACS+ server constants.
a. In the U31 R22 server, open the file installation path\ums-server\work
s\global\deploy\deploy-usf.properties.
b. Delete the (#)s before the following three configuration items and set the
corresponding values:
l usf.user.tacacsserver.ip=10.10.10.4 (TACACS+ client IP address)
l usf.user.tacacsserver.port=49 (TACACS+server port)
l usf.user.tacacsserver.secretkey=secret (TACACS+key set by the server)
2. Configure the user authentication type.
a. In the Configuration Center navigation tree, select Common Configuration >
Common Property.
b. On the Server tab, select Global Configuration > Security > Authentication
type. The authentication type is displayed in the right pane, seeFigure 8-23.
8-17

Figure 8-23 Configuring User Authentication Type
c. Select tacacs.true from the Value of config list.

d. Click Save.
8-18

Chapter 9
Configuring LDAP
Authentication
Lightweight Directory Access Protocol (LDAP) authentication uses the LDAP server to
store user information. If the U31 R22 server receives user login requests, it forwards the
login requests to the LDAP server for authentication. After the authentication is successful,
the user information of the LDAP server is synchronized to the U31 R22 server, which is
used for authority.
The building of the LDAP server will not described in this procedure.
Steps
1. Log in to the U31 R22 server as the administrator.
2. Modify the deploy-usf.properties file in the directory ums-server\works\gl

obal\deploy. For the modification description, refer to Table 9-1.
Table 9-1 Modification Descriptions for the deploy-usf.properties File
Modification Item Description
usf.user.authentication = ldap No need to be modified.
usf.user.ldapserver.initctx=com.sun.jndi.l No need to be modified.

dap.LdapCtxFactory
usf.user.ldapserver.rootdn= l If OPEN LDAP is used as the LDAP

server, this property should be consistent
with the rootdn value of the slapd.conf file
in the LDAP server.
l If Windows Active Directory is used as the
LDAP server, this property is associated
with the domain name of the AD. For
example, if the domain name is cdyjs.com,
this property is set to DC=cdyjs,DC=com.
usf.user.ldapserver.secretkey= It should be consistent with the rootpw value of

the slapd.conf file in the LDAP server. If the AD
is used, this property does not need to be set.
usf.user.ldapserver.host=ldap://127.0.0.1:389 Modify the IP address of the LDAP server to

127.0.0.1. In SSL mode, this property is set to
ldap://ip:636.
9-1

Modification Item Description
usf.user.ldapserver.isActiveDirectory=false l false: Active Directory is not used as the

LDAP server.
l true: Active Directory is used as the LDAP
server.
usf.user.ldapserver.SSL=false Whether to support the SSL detection. Only

the AD supports this mode.
usf.user.ldapserver.keystore.path= Path for logging in to the LDAP server

certificate in SSL mode, for example, D:
/ssh/keystore.
usf.user.ldapserver.keystore.password= Password for logging in to the LDAP server

certificate in SSL mode.
usf.sm.authentication.type=ldap.true;uep.true Log in to the U31 R22 client in LDAP mode.

If login fails, then log in to the U31 R22 client
in UEP mode.
3. Modify the deploy-*.xml files in the directory \ums-server\procs\bsf\services

\.
Annotate the <exclude name="usf-user-ldap.par"/> property in these files.
4. Refer to the following example to modify file ldap_authenticate.properties in
the directory ums-server\procs\bsf\services\usf-user-ldap.par\conf.
# LDAP SERVER USER's DN PREFFIX
DN_PREFFIX= cn=
# LDAP SERVER USER's DN SUFFIX
DN_SUFFIX= ou=colaboradores,ou=usuarios,ou=brt,o=btp
# USER FILTER PREFFIX
USER_FILTER_PREFFIX= (cn=
# USER FILTER SUFFIX
USER_FILTER_SUFFIX= )
# LDAP SERVER GROUP's BASEDN
ROLE_BASEDN= ou=groups,ou=brt,O=btp
# LDAP SERVER GROUP's FILTER PREFFIX
ROLE_FILTER_PREFFIX= (member=
# LDAP SERVER GROUP's FILTER SUFFIX
ROLE_FILTER_SUFFIX= )
# THE MAP OF COLUMN ROLENAME
ROLENAME= cn
# THE MAP OF COLUMN USERNAME
USERNAME= cn
9-2

Chapter 9 Configuring LDAP Authentication
Note:
If Windows Active Directory is used as the LDAP server, DN_PREFFIX should be set
to null and DN_SUFFIX should be set to @domain name (for example, if the domain
name of the AD is cdyjs.com, DN_SUFFIX is set to @cdyjs.com.
5. Execute operationmodel.bat(.sh) in the directory ums-server\utils\oper

ationmodel.
6. Enable the U31 R22 server.
7. Log in to the U31 R22 as the administrator, and then create the role defined in the
LDAP server.
Caution!
The username should be consistent with the role name defined in the LDAP server.
9-3

9-4

Chapter 10
Querying Installation
Information
This procedure describes how to query the U31 R22 installation information, including the
installation type, program area path, installation scale, hierarchy support, and the installed
product information.
Steps
1. In the Configuration Center navigation tree, select System Information >
Installation Information. The installation information is displayed in the right pane,
see Figure 10-1.
Figure 10-1 Viewing the Installation Information
2. (Optional) To export the installation information into an xml file, click export.
10-1

10-2

Chapter 11
Distributed Performance
Data Collection
Table of Contents
Overview ..................................................................................................................11-1
Distributed Performance Data Collection Solutions...................................................11-3
Installation Overview ................................................................................................11-6
Performance Data Collection Server Configuration and Collector Installation ...........11-7
Distributed Performance Data Collection Management........................................... 11-12
11.1 Overview
11.1.1 Introduction
Distributed Collection Solution
With increasing access and aggregate devices and enlarging network scale, traditional
central performance servers are facing tremendous performance data collection demands.
In response to this problem, distributed collection solutions are developed to improve the
capability of performance data collection servers by using distributed collectors to share
the load of the master server.
Principle
Distributed collection uses collectors to collect performance data. The architecture
consists of a database, a server, and multiple collectors. For the architecture of distributed
collection, see Figure 11-1.
11-1

Figure 11-1 Distributed Collection Architecture
The operating principle is as follows:

A performance task is created in the EMS server. When the task is executed, the EMS
server allocates the task to all collectors, and these collectors collect performance data
from devices and report the data to the EMS server.
11.1.2 Distributed Collection Subsystem

Application
The U31 R22 distributed performance data collection subsystem consists of a database,
a performance server, and multiple collectors.
l Database
The database system supports multiple databases (for example, Oracle and SQL
Server) by encapsulating the standard Java Database Connectivity (JDBC) interface.
The database system can run on the performance server or on an independent server.
l Performance server
The performance server end is based on the J2EE. It supports multiple operating
systems, including the Windows operating system and various Unix operating
systems.
The performance server cluster communicates with collectors in RMI or EJB mode to
control and manage the collectors.
11-2

Chapter 11 Distributed Performance Data Collection
l Collector
A collector is based on the J2EE. It supports multiple operating systems, including the
Windows operating system and various Unix operating systems.
Depending on their capabilities, different collectors support different number of tasks.
They collect performance data from the managed network devices and report the data
to the performance server periodically.
Data Synchronization
Data synchronization is divided into the following four types:
l Collection task synchronization and collection data synchronization
à Collection task synchronization

After the performance server distributes a task, no matter whether the task is
distributed successfully or not, a response is returned. If the task fails to be
distributed, it is distributed repeatedly until it is distributed successfully.
à Collection data synchronization
Data synchronization is performed every one hour. Missing data can be obtained
from collectors.
l Automatic synchronization and manual synchronization
à Automatic synchronization
The collectors report collected data periodically and maintain synchronized with
the performance server. In the hot standby solution, automatic synchronization
can ensure that the missing data during active/standby handovers can be
recollected.
à Manual synchronization
The performance server can be synchronized with the collectors manually.
Data Cache
After collectors collect data, they do not report it immediately. Instead, they save it in the
memory.
After a task is completed, the corresponding data is saved to a txt file and compressed into
a zip file before being sent to the performance server.
11.2 Distributed Performance Data Collection Solutions

There are two solutions for the U31 R22 distributed performance data collection
subsystem: N + N hot standby and N + K cold standby solutions.
These two solutions have their advantages and disadvantages. For details, refer to Table
11-1.
11-3

Table 11-1 Advantages and Disadvantages of the Two Solutions
Solution Advantage Disadvantage
N + N hot standby Packets will not be lost during This solution requires a large number of
selector handovers. backup servers, which is very expensive.
N + K cold standby This solution only requires Packets may be lost during selector
a small number of backup handovers.
servers, which is less
expensive than the N + N
hot standby solution.
11.2.1 N + N Hot Standby

The N + N hot standby solution means that performance data collection tasks run on 2N
performance connection servers. In these servers, N servers are active servers, and N
servers are backup servers. The active and standby collectors share the tasks equally and
provide backup mutually. However, only the active servers report data to the performance
server. For the architecture of this solution, see Figure 11-2.
Figure 11-2 N + N Hot Standby Architecture
The following uses collector 2 as an example to describe the operating principle between
servers:
11-4

1. The distributed performance data collection task runs on both active collector 2 and
standby collector 2. Active collector 2 reports the data.
2. If the active server detects that active collector 2 fails, it switches the tasks to standby
collector 2, and the original active collector 2 becomes a standby collector. The original
standby collector 2 collects the missing data from the time when the fault is detected,
and reports the data. The original active collector checks the status of the active server
periodically through polling.
3. If a collector detects that the active server fails, it performs polling to check the standby
server. If the standby server operates properly, the collectors are switched to the
standby server, and the data is reported to the standby server.
4. If both the active and the standby servers fail, data is compressed into a zip file. It is
reported when any of the servers recovers.
11.2.2 N + K Cold Standby

The N + K cold standby solution means that there are N + K collectors, among which,
N collectors are active collectors, and K collectors are standby collectors. Distributed
performance data collection tasks run on the active collectors, and no task runs on the
active standby collectors. For the architecture of this solution, see Figure 11-3.
Figure 11-3 N + K Cold Standby
The following uses collector 6* (standby collector) as an example to describe the operating
principle between servers:
11-5

1. If the active server detects that collector 1 fails, it switches the tasks performed by
collector 1 to collector 6*. After the operation, collector 1 becomes a standby server.
The active collectors check the status of the active server periodically through polling.
2. If an active collector detects that the active server fails, it checks the standby server
through polling. If the active server operates properly, the collectors are switched to
the standby server, and data is reported to the standby server.
3. If both the active and the standby servers fail, data is compressed into a zip file. It is
reported when any of the servers recovers.
11.3 Installation Overview

11.3.1 Installation Plan
Checking Server Status
The system uses the N + N solution.
Collectors have polling tasks. They check the EMS server status periodically.
l If the EMS server operates properly, collectors check data consistency, primarily check
collection task consistency.
l If the EMS server is not in proper status for three times continuously, the collectors
are switched to the standby server, and the data is reported to the standby server.
l If both the active and the standby servers fail, data is saved into a zip file. It is reported
when any of the servers recovers.
Checking Collector Status

A standby collector is assigned for each active collector.
The active server performs polling to check the status of each collector periodically. If an
active collector fails, it switches the corresponding tasks to the standby collector.
11.3.2 Hardware Architecture

For the hardware architecture of the U31 R22 distributed collection subsystem, see Figure
11-4.
11-6

Figure 11-4 Hardware Architecture
11.3.3 Installation Flow

For the installation flow, refer to Table 11-2.
Table 11-2 Distributed Performance Data Collection Subsystem Installation Flow
Step Operation
1 Configure a performance data collection server.
2 Install a collector.
3 Start a collector.
11.4 Performance Data Collection Server Configuration

and Collector Installation
11.4.1 Configuring the Distributed Performance Data Collection
Server
After you have installed the U31 EMS server and the client software, you need to configure
the distributed performance data collection mode.
11-7

Note:
When you install the EMS server and the client software, you can configure the collection
mode in the U31 Config Center window.
Steps
1. In the Windows operating system, select Start > All Programs > U31 Config Center.
The Netnumen U31 Unified Network Management System-Configuration Center
Figure 11-5 Configuration Center Window
2. On the Server tab, select Product Configuration > BN-IP Configuration >
Performance Collection Server Configuration in the left navigation tree. The
Performance Collection Server Configuration tab is displayed, see Figure 11-6.
11-8

Figure 11-6 Performance Collection Server Configuration Tab
3. Select N+N Deployment Model or N+K Deployment Model from the Deployment
mode drop-down list and click Save.
11.4.2 Installing a Collector

You can install a collector by using the dual-server cluster installation package.
Normally, a collector is installed on an independent server or PC. The operating system
used by the collector must be consist with that used by the EMS system. The following
are the requirements for hardware:
l CPU: 2 × 4 cores
l CPU speed: >=2 GHz
l Memory: >=16 GB
l Hard disk: >=300 GB
Prerequisite
Files in the installation package are copied from the installation directory \packages\ip
_collector to the packages directory.
11-9

Steps
1. In a Windows operating system, run the setup_ip_collector.bat file (in a
Solaris operating system, run the setup_ip_collector.sh file). The Choose the
language for installation dialog box is displayed, see Figure 11-7.
Figure 11-7 Choose the Language for Installation Dialog Box
2. Enter 1 to select the English language and press the Enter key. The following dialog
Figure 11-8 Input Installation Directory Dialog Box
3. Enter the path in the Installation Directory line and press the Enter key.
The system automatically install the collector.
4. When it needs to set the parameters for the configuration center, the Config Center
11-10

Figure 11-9 Config Center Window
Set the IP addresses of the collector and the server.

5. Click the Process Config tab. The Process Config tab is displayed, see Figure 11-10.
Figure 11-10 Process Config Tab
a. To add another collector, click Add.

b. (Optional) To delete a collector, click Remove.
6. Click OK to complete the configuration.
11.4.3 Starting a Collector

Before you bind a collector to an NE, you must start the collector console.
This procedure describes how to start a collector in a Window operating system.
Prerequisite
The EMS server and the client are started. For details, refer to the Starting the U31 R22
On the Windows OS procedure in the NetNumen U31 R22 Unified Network Management
System Single Server Installation Guide.
Steps
1. In a Window operating system, run the run.bat file (in a Solaris system, run the run.sh
file) in the directory of the collector.
The collector console page is displayed, see Figure 11-11.
11-11

Figure 11-11 Collector Console age
If the collector process is started and displayed in the Log area, the collector is started
successfully.
11.5 Distributed Performance Data Collection

Management
11.5.1 Managing a Collector
This procedure describes how to set the group name of a collector, the operation state of
the collector, and how to synchronize the collector information.
Prerequisite
The U31 R22 distributed performance data collection system (N + N or N + K solution) is
installed.
Steps
1. On the home page of the EMS system, select Configuration > BN-IP NE
Confiuration > BN-IP NE Resource Configuration. The BN-IP NE Resource
Configuration page is displayed.
2. In the Resource Node navigation tree, select Performance Management

> Distributed Acquisition Management > Acquisition Management. The
Acquisition Management tab is displayed.
11-12

Figure 11-12 Acquisition Management Tab (N+N Hot Standby)
Figure 11-13 Acquisition Management Tab (N+K Cold Standby)
3. Double-click the cell in Group, Working state or Priority columns to set the group
name and the operation state of the corresponding collector.
Figure 11-14 Setting Group Name and Operation State (N+N Hot Standby)
Figure 11-15 Setting Group Name and Operation State (N+K Cold Standby)
Note:
l In N+N hot standby deployment mode, a group can contain up to two collector,
and only one collector can be in Work status.
l In N+K cold standby deployment mode, a collector (collector A or B) cannot be
switched over if both collectors are in Work or Standby status, or this collector is
in Standby status
4. Click on the toolbar to save the configuration.
11-13

5. (Optional) To switch the collector state, click one or multiple collectors and click
on the toolbar.
6. (Optional) To synchronize the information of one or multiple collectors, select the
collector(s), and click on the toolbar.
11.5.2 Managing NE Load

This procedure describes how to set the selector group to which an NE belongs and thus
to bind the NE to a selector.
Prerequisite
The U31 R22 distributed performance data collection system (N + N or N + K solution) is
installed.
Steps
1. On the homepage of the EMS system, select Configuration > BN-IP NE Confiuration
> BN-IP NE Resource Configuration. The BN-IP NE Resource Configuration page
is displayed.
2. Select the device type to be configured from the Device type drop-down list on the
BN-IP NE Resource Configuration page.
3. In the Resource Node navigation tree, select Performance Management >
Distributed Acquisition Management > Load NE Management. The Load NE
Management tab is displayed.
Figure 11-16 Load NE Management Tab (N+N Hot Standby)
11-14

Figure 11-17 Load NE Management Tab (N+K Cold Standby)
4. Double-click the cell in the Group column of the corresponding NE and select the
selector group to which the NE belongs.
You can select a collector group only in N+N hot standby deployment mode.
5. Click . Set collection parameters as required. For a description of the parameters,

refer to Table 11-3.
Table 11-3 Collection Parameter Descriptions
Polling interval Interval at which the collector polling is performed.
Polling frequency Number of times that collector polling is performed.
Clear data N days Clears the performance collection results generated N days ago.
before
Temporary file storage Sets the directory where performance files are temporarily saved on
directory the EMS server,
6. Set the selector groups for each NE and click to bind the NE to the collector.
7. (Optional) To synchronize the NE load information, click on the toolbar.
After you synchronize the NE load information, click to refresh the load information.
The NE load information is then displayed on the Load NE Management tab.
11-15

11-16

Glossary
CMPP
- China Mobile Point to Point
CORBA
- Common Object Request Broker Architecture
DCN
- Data Communications Network
EJB
- Enterprise JavaBean
EMB
- Enterprise Message Bus
GSM
- Global System for Mobile Communications
IP
- Internet Protocol
J2EE
- JAVA 2 platform Enterprise Edition
JDBC
- Java Database Connectivity
JMS
- Java Message Service
LDAP
- Lightweight Directory Access Protocol
NAT
- Network Address Translation
NTP
- Network Time Protocol
OSS
- Operation Support System
RMI
- Remote Method Invocation
SGIP
- Short Message Gateway Interface Protocol
SID
- System Identifier

SM
- Short Message
SMGP
- Short Message Gateway Protocol
SMPP
- Short Message Peer to Peer Protocol
SNTP
- Simple Network Time Protocol
II

NetNumen U31 R22 (V12.15.10) System Configuration Guide - V1.0

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

NetNumen U31 R22 (V12.15.10) System Configuration Guide - V1.0

Hochgeladen von

Copyright:

NetNumen™ U31 R22

Unified Network Management System

Revision No. Revision Date Revision Reason

R4.0 2014-12-30 NetNumen™ U31 R22 (V12.15.10) Issued.

l Added “Configuring the BN-xTN Northbound TMF CORBA

R3.1 2014-06-30 NetNumen™ U31 R22 (V12.14.10P02) Issued.

l Updated “Common Configurations”, “Product Configurations”

R3.0 2013-12-20 NetNumen™ U31 R22 (V12.14.10) Issued.

l Add “Configuring LDAP Authentication”.

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

R2.2 2013-07-30 NetNumen™ U31 R22 (V12.13.10P02) was issued.

Updated “Configuring the Wireline NBI CORBA Interface”,

R2.1 2013-03-25 NetNumen™ U31 R22 (V12.13.10P01) was issued.

l Add “Configuring the Wireline Northbound CORBA Interface”,

R2.0 2012-12-30 NetNumen™ U31 R22 (V12.13.10) was issued.

Updated some configurition interfaces and menu items.

R1.0 2012-11-02 First edition.

Serial Number: SJ-20141211100735-006

Publishing Date: 2014-12-30 (R4.0)

Chapter 3 Product Configurations............................................................ 3-1

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

Chapter 4 Configuration Information Import/Export ............................... 4-1

Chapter 5 Configuring Database Connection Information .................... 5-1

Chapter 7 Alarm Forwarding Installation ................................................ 7-1

Chapter 8 Configuration of the Authentication Mode ............................. 8-1

Chapter 9 Configuring LDAP Authentication .......................................... 9-1

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

What Is in This Manual

Chapter 4, Configuration Describes how to import and export the configuration

Chapter 5, Configuring Database Describes how to connect the database.

Chapter 6, NTP Server Describes how to configure the NTP server.

Chapter 8, Configuration of the Describes how to configure U31 R22 authentication.

Chapter 9, Configuring LDAP Describes how to configure LDAP authentication.

Chapter 11, Distributed Describes the distributed performance data collection.

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

Caution: indicates a potentially hazardous situation. Failure to comply can

Note: provides additional information about a topic.

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

Server Configuration Center

l Enabling the server configuration center on Windows

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

Figure 1-1 NetNumen U31 Unified Network Management System - Configuration

l Enabling the server configuration center on Solaris and Linux

Client Configuration Center

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

2.1 Configuring Common Properties

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

Table 2-1 Common Property Descriptions

Use NAT Enables or disables network address translation.

When the When the NAT function is used to automatically

UMD timing Specifies the start time of UMD (one-key failure

Other The default value is recommended if no special

Clock Syn- Clock synchro- Enables or disables the clock synchronization

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential

Clock synchro- Cycle for checking whether the clock is

Threshold of Time offset threshold for determining whether

Switch of au- Determines whether to enable automatic

SNMP SNMP proxy l Yes: enables the unified northbound SNMP

Other If SNMP proxy availability is enabled, these

FTP When the type of file transfer is FTP, this

SJ-20141211100735-006|2014-12-30 (R4.0) ZTE Proprietary and Confidential