Netnumen Training PDF

NetNumen U31 Introduction
Training Manual
Publishing Date (MONTH/DATE/YEAR) : 2013–01–15

This page is intentionally blank.
Contents
NetNumen U31(V12.12.20P01) Introduction ............... 1

1 System Overview....................................................... 2
1.1 Introduction to the System ..................................................... 2
1.2 Location of the Product on a Bearer Network ............................. 2
1.3 Typical Application Schemes.................................................... 3
1.4 System Features ................................................................... 5
1.5 Manageable NEs ................................................................... 6
1.6 Computer Ports Occupied by the System .................................. 8
2 New Features .......................................................... 15
2.1 New Functions .....................................................................15
2.2 Important Changes ...............................................................18
3 Product Functions ................................................... 21
3.1 Topology Management...........................................................21
3.2 Alarm Management...............................................................22
3.3 Performance Management .....................................................24
3.4 Security Management ...........................................................25
3.5 Configuration Management ....................................................28
3.6 Software Management ..........................................................29
3.7 Log Management ..................................................................30
3.8 Report Management..............................................................30
3.9 Database Management ..........................................................30
3.10 License Management ...........................................................31
4 Product Architecture ............................................... 33
4.1 Hardware Architecture...........................................................33
4.2 Software Architecture............................................................34
5 Product Interfaces .................................................. 37
5.1 Logical Interfaces .................................................................37
5.2 Physical Interfaces................................................................38
6 Networking Modes................................................... 39
6.1 Network Architecture Requirements ........................................39
6.2 Non-Cascade Networking Modes .............................................39
6.2.1 Non-Cascade Local Networking.......................................39
6.2.2 Non-Cascade Remote Networking ...................................40
6.2.3 Non-Cascade Integrated Networking ...............................42
6.3 Cascade Networking Modes....................................................43
6.3.1 Local Cascade Networking .............................................43
6.3.2 Remote Cascade Networking..........................................44
6.4 Distributed System ...............................................................45
7 Technical Specifications .......................................... 47
7.1 Performance Specifications ....................................................47
7.2 Interface Specifications .........................................................48
8 Compliant Standards ............................................... 49
Glossary ....................................................................109
NetNumen
U31(V12.12.20P01)
Introduction
After you have completed this course, you
will be able to:

>> Master NMS System Position and Hier-
archy
>> Master NMS Structure and Feature
>> Master NMS Networking and Applica-
tion
Confidential and Proprietary Information of ZTE CORPORATION 1

NetNumen U31 Introduction Training Manual
Chapter 1 System Overview

After you have completed this chapter, you will know:
>> Introduction to the System
>> Location of the Product on a Bearer Network
>> Typical Application Schemes
>> System Features
>> Manageable NEs
>> Computer Ports Occupied by the System
1.1 Introduction to the System

NetNumen is a network-layer network management system
based on a distributed, multi-process and modular design. can
uniformly manage the optical communication equipment of CTN,
SDH, WDM/OTN, Router, BRAS and Switch series.
The provides complete management functions, including con-
figuration management, alarm management, performance
management, maintenance management, end-to-end circuit
management, security management, system management, and
report management. It can manage multiple service types.
1.2 Location of the Product on a

Bearer Network
is a unified management platform that manages all types of equip-
ment of ZTE bearer networks, including CTN, SDH, WDM/OTN
equipment, routers, BRASs, and switches.
is a network management system that is located at the network
element management layer/subnetwork management layer and
performs the network element layer and network layer manage-
ment.
For the position of the in a bearer network, see Figure 1.
2 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 1 POSITION OF IN THE BEARER NETWORK
– BSS: Business Support System – CTN: Converged Packet Transport

– OSS: Operation Support System Network
– EMS: Network Element Manage- – BRAS: Broadband Remote Access
ment System Server
– NMS: Network Management Sys- – WDM: Wavelength Division Multi-
tem plexing
– NBI: North Bound Interface – OTN: Optical Transport Network
– IP: Internet Protocol – SDH: Synchronous Digital Hierar-
– LCT: Local Craft Terminal chy
1.3 Typical Application Schemes

The supports two application schemes:
� Application Scheme Without Protection
In the application scheme without protection, one server is
configured. If the server is faulty, the network may fail to be
managed. This scheme features low cost but it is less reliable.
In actual networking, the application scheme without protec-
tion provides two configuration modes.
� Integrated configuration
On one server, both the server and client are configured.
� Separated configuration
The server is configured on one server, and the client is
configured on another computer. The client is connected to
the server through the network protocol.

� Dual-Server Configuration for Hot Backup

In the dual-server configuration scheme, two servers providing
the same services are used. One acts as the primary server,
and the other acts as the standby one. The primary server,
also called active server, provides application services when
the system runs properly. The standby server monitors the
working status of the primary one. At the same time, the
primary server checks whether the standby server is working
properly. If the primary server fails to provide the applications,
the standby server takes over the primary one to provide key
application services and ensure the continuous running of the
system.
Dual-sever hot backup can be classified into local dual-sever
hot backup and remote dual-sever hot backup.
� In local dual-server hot backup, the primary server and the
standby server share the same disk array, and the data is
stored in an independent disk array. If the primary server
fails, the standby server takes over the primary server and
accesses the data in the disk array.
� In remote dual-server hot backup, a server is installed on
the primary server and the standby server respectively, and
the data on both servers is automatically synchronized.
If the primary server fails, the server is switched to the
standby server, which takes over the job of the primary
server.
For the local dual-sever hot backup, see Figure 2.
FIGURE 2 LOCAL DUAL-SERVER CONFIGURATION HOT BACKUP
For the remote dual-sever hot backup, see Figure 3.

FIGURE 3 REMOTE DUAL-SERVER CONFIGURATION HOT BACKUP
1. Remote dual-server heartbeat 3. Network interface between

network interface the NMS sever and client
2. Network interface for copying 4. Network interface between
data the NMS sever and the NE
1.4 System Features

Standard The follows the TMN and eTom models, and complies with TMN,
Compliance 3GPP, SNMP, NGOSS and NGMN standards.
Modularized The system can easily meet the requirements for managing new
Design devices and services due to its modularized architecture. The sys-
tem software consists of several modules, which can be distributed
on different computers. The distributed deployment of software
modules provides the processing capability of the system.
System Openness The system adopts the following technologies to support its open-
ness.
� The use of CORBA, SNMP and XML interfaces enables the sys-
tem to share both data and services with other service sys-
tems.
� The system is implemented by JAVA, which enables the system
to run on the Windows, UNIX or Linux operating system, so as
to meet the users’ demands for managing networks of different
scales.
� The system provides various external interfaces.
Operation Security The system uses the access right control and log records to ensure
the security of operations on it.
� Access Right Control
You can constrain the operation right of a user based on the
view of a controlled network, that is, the operations performed

by the user are limited to certain network elements with a cer-

tain granularity.
� Complete Log Records
By observing the log records, you can find unauthorized op-
erations in time to ensure the security of the system and the
managed network.
Ease of Use By using the topology navigation function on the system, you can
perform network management operations easily in an intuitive
way, for example, monitor the running status of the managed
network on the topological graph of the network.
The topological graph has different levels, for example, global
topology and local topology. The alarm information in the whole
network can be displayed on the topological graph or rack map
in real time. The system provides different audible and visual
alarm indications according to the severity of alarms. In addition,
the system supports the centralized management of performance
data in the whole network for convenient query, statistics, and
report.
Data Security The system adopts database backup and disk mirroring to ensure
the security of data in the system.
� Database Backup
The system provides diversified backup modes by supporting
the storage of data on another peripheral memory, such as
disk, tape, compact disk, or database. You can restore the
data backup on the peripheral memory to the system when
necessary.
� Disk Mirroring
When data mirroring is used, all data on the active disk is repli-
cated to the standby disk in real time for backup.
1.5 Manageable NEs

� SDH NEs
ZXMP S100, ZXMP S150, ZXMP S200, ZXMP S320, ZXMP S325,
ZXMP S330, ZXMP S335, ZXMP S360, ZXMP S380, ZXMP S385,
ZXMP S390, ZXONE 5800, ZXONE 5800-E.
� WDM/OTN NEs
ZXWM-32, ZXMP M600, ZXMP M720, ZXMP M721, ZXMP M800,
ZXWM M900, ZXMP M820, ZXMP M920, ZXONE 8000, ZXONE
8300, ZXONE 8500, ZXONE 8700 X32.
� CTN NEs
ZXCTN 6100, ZXCTN 6110, ZXCTN 6120, ZXCTN 6130, ZX-
CTN 6150, ZXCTN 6200, ZXCTN 6220, ZXCTN 6300, ZXCTN
6320, ZXCTN 6500-8, ZXCTN 6500-16L, ZXCTN 6500-32, ZX-
CTN 9002, ZXCTN 9004, ZXCTN 9008.
� UAS Products
ZXUAS 10600, ZXE10 UAS2500S, ZXUAS 10800E, ZXUAS
10400, ZXUAS 10800.

� Router
ZXR10 T8000-16, ZXR10 M6000-8, ZXR10 M6000-16, ZXR10
M6000-8s, ZXR10 M6000-5s, ZXR10 M6000-3s, ZXR10
T1200, ZXR10 T1200 BMSG, ZXR10 T600, ZXR10 T600 BMSG,
ZXR10 T128, ZXR10 T64E, ZXR10 GER, ZXR10 GER04, ZXR10
GER02, ZXR10 1822, ZXR10 1842, ZXR10 2842, ZXR10 2882,
ZXR10 3842, ZXR10 3884, ZXR10 1809, ZXR10 2822R, ZXR10
1842R, ZXR10 2842R, ZXR10 2882R, ZXR10 2822, ZXR10
2884, ZXR10 ZSR 3822, ZXR10 3844, ZXR10 3882, ZXR10
1822E, ZXR10 GAR 2604, ZXR10 GAR2608, ZXR10 GAR3608,
ZXR10 GAR7208, ZXR10 T16S, ZXR10 T16C, ZXR10 T32C,
ZXR10 T64C, ZXR10 T160, ZXR10 T1216, ZXR10 T1212,
ZXR10 6802, ZXR10 6804, ZXR10 6812, and ZXR10 6800.
� Switch
ZXR10 8902, ZXR10 8905, ZXR10 8908, ZXR10 8912, ZXR10
8902E, ZXR10 8905E, ZXR10 8908E, ZXR10 8912E, ZXR10
6902, ZXR10 6905, ZXR10 6908, ZXR10 T40G, ZXR10 T64G,
ZXR10 T160G, ZXR10 T240G, ZXR10 5224, ZXR10 5228,
ZXR10 5228-FI, ZXR10 5252, ZXR10 5928, ZXR10 5928-FI,
ZXR10 5928-PS, ZXR10 5928E, ZXR10 5928E-FI, ZXR10
5952, ZXR10 5952E, ZXR10 5916E, ZXR10 5128E, ZXR10
5116E, ZXR10 5128E-FI, ZXR10 5228A, ZXR10 5252A, ZXR10
3928A, ZXR10 3928A-FI, ZXR10 3952A, ZXR10 3228A, ZXR10
3228A-EI, ZXR10 3228A-FI, ZXR10 3252A, ZXR10 3206,
ZXR10 3226, ZXR10 3228, ZXR10 3226-FI, ZXR10 3252,
ZXR10 3906, ZXR10 3928, ZXR10 3928E, ZXR10 3928E-FI,
ZXR10 3952, ZXR10 3952E, ZXR10 59S STACK.
ZXR10 5109, ZXR10 5116, ZXR10 5116-FI, ZXR10 5116-SI,
ZXR10 5124, ZXR10 5124-FI, ZXR10 5124-SI, ZXR10 2920-SI,
ZXR10 2928-SI, ZXR10 2952-SI, ZXR10 2936-FI, ZXR10
2909-SI, ZXR10 2909-FU, ZXR10 2918-SI, ZXR10 2926-SI,
ZXR10 2910E-PS, ZXR10 2918E, ZXR10 2918E-PS, ZXR10
2928E, ZXR10 2952E, ZXR10 2609-LE, ZXR10 2818S-LE,
ZXR10 2826S-LE, ZXR10 2852S-LE, ZXR10 2609A, ZXR10
2618A, ZXR10 2626A, ZXR10 2826A, ZXR10 2826A-PS,
ZXR10 2609, ZXR10 2609-FU, ZXR10 2809, ZXR10 2809-FU,
ZXR10 2818S, ZXR10 2826S, ZXR10 2852S, ZXR10 2826E,
ZXR10 2618, ZXR10 2626, ZXR10 2609-EI, ZXR10 2818S-EI,
ZXR10 2826S-EI, ZXR10 3904F, ZXR10 3904, ZXR10 3206S,
ZXR10 2826, ZXR10 1816, ZXR10 29S STACK, ZXR10 5009.
ZXR10 5250-28TC, ZXR10 5250-52TC ZXR10 5250-28SM,
ZXR10 5250-28PM, ZXR10 5250-52PM, ZXR10 2928E-PS, and
ZXR10 2950-28PC.
� Government and Enterprise Network Products
ZXR10 5950-28TM, ZXR10 5950-28SM, ZXR10 5950-52TM,
ZXR10 5950-28PM, ZXR10 5950-24T, ZXR10 5950-48T, ZXR10
5250-24T, ZXR10 5250-52TM, ZXR10 3950-28TM, ZXR10
3950-28SM, ZXR10 3950-28PM, ZXR10 3950-52TS, ZXR10
2950-52TS, ZXR10 2950-28TC, ZXR10 2950-18TC, ZXR10
2950-18PC, ZXR10 2950-10PC, ZXR10 2850-18TM, ZXR10
2850-26TM, ZXR10 2850-52TC, ZXR10 2850-9TT, ZXR10
2850-9TS.

1.6 Computer Ports Occupied by

the System
Server and Client For the computer ports occupied by the server and client, refer to
Table 1.
TABLE 1 COMPUTER PORTS OCCUPIED BY THE SERVER AND CLIENT
N- Sou- Desti- Direc- Pro- Description

u- rce nation tion tocol
m- Port Port
b-
er
1 Ran- 20800- Client TCP File Transfer Protocol (FTP)

dom 20999 -> data transmission port
Server
2 Ran- 21100 Client TCP Java naming service port

dom -> for the main process
Server
3 Ran- 21101 Client TCP Naming service port for the

dom -> Cluster process, for Java
Server Message Service (JMS)
4 Ran- 21102 Client TCP Remote Method Invocation

dom -> (RMI) communication
Server server port for the Cluster
message server
5 Ran- 21103 Client TCP Remote invocation

dom -> adaptation port for the
Server Java naming service for
the main process
6 Ran- 21104 Client TCP Java naming service

dom -> invocation port for the
Server main process
7 Ran- 21105 Client TCP Enterprise Message Bus

dom -> (EMB) port for the main
Server process

Server main process
9 Ran- 21109 Client TCP Heartbeat detection port

dom -> for the F interface
Server

dom -> transaction management
Server for the main process
11 Ran- 21111 Client TCP FTP server control port

dom ->
Server


m- Port Port
b-
er
12 Ran- 21112 Client TCP Remote invocation port for

dom -> Java components of the
Server main process

Server Cluster process
14 Ran- 21114 Client TCP JMS port for the cluster

dom -> process
Server
15 Ran- 21118 Client TCP Bandwidth detection port

dom -> for the client server
Server
16 Ran- 21128 Client TCP Secure File Transfer

dom -> Protocol (SFTP) server
Server port
17 Ran- 21133 Client TCP Port used by the upgrading

dom -> tool for automatic client
Server upgrade
18 Ran- 21140 Client TCP Secure Shell (SSH)

dom -> forwarding port
Server
19 Ran- 21199 Client TCP SSH forwarding port for

dom -> Man Machine Language
Server (MML) commands
20 Ran- 21 Client TCP Port for the FTP service of

dom -> the NMS server
Server
21 Ran- 21160 Client TCP ZXTIM400 polling tool port

dom ->
Server
22 Ran- 21162 Client TCP EMB port

dom ->
Server

dom ->
Server

dom ->
Server

dom ->
Server


m- Port Port
b-
er

dom ->
Server

dom ->
Server

dom ->
Server

dom ->
Server
30 Ran- 21138 Client TCP EMB port of the TOPO

dom -> process
Server
31 Ran- 21188 Client TCP RMI port used by the

dom -> Telnet tool
Server
32 Ran- 69 Client TCP Port used by the TFTP

dom -> protocol
Server
33 Ran- 20201 – Client TCP Port used for IP

dom 20220 -> management process
Server debugging
34 Ran- 20141 – Client TCP Port used for wireline

Server debugging
35 Ran- 20001 – Client TCP Port used for UEP

Server debugging
Server and OSS For the computer ports occupied by the server and Operation Sup-
port System (OSS), refer to Table 2.
TABLE 2 COMPUTER PORTS OCCUPIED BY THE SERVER AND OSS

m- Port Port
b-
er
1 Ran- 20800- OSS -> TCP FTP data transmission

dom 20999 Server port
2 Ran- 21111 OSS -> TCP FTP server port

dom Server


m- Port Port
b-
er
3 Ran- 21115 OSS -> TCP Common Object Request

dom Server Broker Architecture
(CORBA) naming service
port
5 Ran- 21126 OSS -> TCP CORBA notification service

dom Server port
6 Ran- 21128 OSS -> TCP SFTP server port

dom Server
7 Ran- 21161 OSS -> UDP Non-trap message port

dom Server for Simple Network
Management Protocol
(SNMP) v2C

dom Server for SNMP v3

dom Server for SNMP v1
10 Ran- 161 OSS -> UDP Port used for receiving

dom Server requests when the
operates as the SNMP
agent.
11 Ran- 21175 OSS -> TCP The port used by the for
dom Server communicating with OSS
when the fixed CORBA
service port is used
12 Ran- 21176 OSS -> TCP North Bound Interface

dom Server (NBI) naming service port
13 Ran- 21177 OSS -> TCP NBI notification service

dom Server port
14 Ran- 21178 OSS -> UDP NBI SNMP agent port

dom Server
15 Ran- 162 OSS -> UDP Default port for the SNMP
dom Server Trap message
Server and For the computer ports occupied by the server and the equipment,
Equipment refer to Table 3.
TABLE 3 COMPUTER PORTS OCCUPIED BY THE SERVER AND EQUIPMENT


m- Port Port
b-
er
1 Ran- 20 Server TCP FTP data transmission

dom -> NE port
2 Ran- 21 Server TCP FTP server control port

dom -> NE
3 Ran- 9023 Server TCP Telnet port used by the

dom -> NE OTN equipment
4 Ran- 1025- Server TCP Qx communication port

dom 1030 -> NE
5 Ran- 9998 Server TCP Qx communication i port

dom -> NE
6 Ran- 9999 Server TCP Qx communication port

dom -> NE
7 Ran- 12288- Server TCP Enables the communica-

dom 13311 -> NE tion port of the gateway
NE
8 Ran- 16384- Server TCP Enables the FTP control

dom 17407 -> NE port of the gateway NE
9 Ran- 20480- Server TCP Enables the Telnet port of

dom 21503 -> NE the gateway NE
10 57344- Random NE -> TCP Enables the FTP data

57407 Server transmission port of the
gateway NE
11 Ran- 20800- NE -> TCP FTP data transmission

dom 20999 Server port
12 Ran- 21111 NE -> TCP FTP server control port

dom Server
13 Ran- 23 Server TEL- TELNET port for the CTN

dom -> NE NET equipment
14 Ran- 22 Server TCP SSH protocol port

dom -> NE
15 Ran- 161 Server TCP Port occupied for the

dom -> NE NMS to acquire SNMP
messages
16 23742 23740 NE -> TCP Port opened in the

– Server distributed performance
23753 collection mode.
17 Ran- 9890 NE -> TCP Port used for the NMS

dom Server to enable the monitoring
device to send zero
deployment service TCP
messages.


m- Port Port
b-
er
18 Ran- 9835 – NE -> TCP TL1 northbound port

dom 9840 Server
19 Ran- 514 NE -> TCP SYSLOG receiving port

dom Server


Chapter 2 New Features
>> New Functions
>> Important Changes
2.1 New Functions

New Functions Compared with the V12.12.20P01, the V12.13.10 provides the fol-
Provided by lowing new functions, refer to Table 4.
V12.13.10
(Compared TABLE 4 NEW FUNCTIONS PROVIDED BY V12.13.10 (COMPARED WITH
With the THE V12.12.20P01)
V12.12.20P01)
N- Function Description
o-
.
1 Supports the ZXCTN Refer to “Manageable NEs ” in the

6500 V1.00R1 NetNumen™ Unified Network Management
System Product Description.
2 ZXCTN 9000 Refer to “Manageable NEs ” in the

(V2.08.33R1) NetNumen™ Unified Network Management
3 Monitors real-time Refer to “Basic Maintenance Operations”

MSTP traffic in the NetNumen™ Unified Network
Management System Operation Guide
(SDH NE Management).
4 DCN view Refer to “DCN Management” in the

NetNumen™ Unified Network Management
System Operation Guide (CTN NE
Management).
5 Virtual NEs, virtual Refer to “Topology Management” in the

links NetNumen™ Unified Network Management
System Operation Guide (Common
Operations).
6 Resource analysis Refer to “Report Management” in the

function NetNumen™ Unified Network Management
System Operation Guide (Common
Operations).
7 Supports the ZXR10 Refer to “Manageable Products” in the

5900E (V2.09.10) NetNumen™ Unified Network Management
System Operation Guide (Data Product NE
Management).

o-
.
8 Supports the ZXR10 Refer to “Manageable Products” in the

5960 (V2.09.10) NetNumen™ Unified Network Management
Management)
9 Supports ZXR10 Refer to “Manageable Products” in the

M6000 (V2.00.20) NetNumen™ Unified Network Management
(topology System Operation Guide (Data Product NE
management, alarm, Management)
performance, rack
diagram)

0 T8000 (V NetNumen™ Unified Network Management
2.00.20) (topology System Operation Guide (Data Product NE
performance, rack
diagram)

1 M6000-nS NetNumen™ Unified Network Management
(V2.00.20) (topology System Operation Guide (Data Product NE
performance, rack
diagram)
1 Supports Refer to “IPV6 Management” in the

2 IPV6 protocol NetNumen™ Unified Network Management
management System Operation Guide (Data Product NE
channel; supports Management).
browsing the IPV6
protocol
1 Supports configuring Refer to “DOT1X Management” in the
3 the 802.1X on NetNumen™ Unified Network Management
middle-end switches System Operation Guide (Data Product NE
Management).
1 Supports configuring Refer to “Configuring Common Template”

4 the QoS on in the NetNumen™ Unified Network
middle-end switches Management System Operation Guide
(Data Product NE Management).
1 Resource views Refer to “BN NE Resource View

5 support abnormal Management” in the NetNumen™ Unified
traffic monitoring Network Management System Operation
and packet Guide (Data Product NE Management).
performance reports
1 Creating links in Refer to “Creating a Link” in the

6 batches NetNumen™ Unified Network Management
Management).
1 Supports Refer to the NetNumen™ Unified Network

7 northbound interface Management System Northbound Interface
in XML User Guide (Data Products).
1 Transparent PW -
8

o-
.
1 Service parameter -
9 templates
2 Supports multiple- Refer to “Configuring SDH Services with

0 section SNCP SNCP” in the NetNumen™ U31 R22 Unified
Network Management System Operation
Guide (SDH End-to-End Management).
New Functions Compared with the V12.12.20, the V12.12.20P01 provides the fol-
Provided by lowing new functions, refer to Table 5.
V12.12.20P01
(Compared With TABLE 5 NEW FUNCTIONS OF THE V12.12.20P01
the V12.12.20)
o.
1 Supports the Refer to “Manageable NEs” in the

ZXCTN 6130 NetNumen™ Unified Network Management
2 The SDH Refer to “Creating SDH Services” in the

equipment NetNumen™ Unified Network Management
supports VC3 System Operation Guide (SDH NE
concatenation Management).
3 Supports Refer to “Data Backup and Restoration”

cross-version and in the NetNumen™ Unified Network
cross-scale data Management System Operation Guide
restoration (Common Operations).
4 Supports PCM Refer to “Installing the ” in the NetNumen™

equipment Unified Network Management System
Installation Guide.
5 Supports the IP Refer to the NetNumen™ Unified Network

RAN function Management System Operation Guide (IP
RAN Management).
6 Supports the Refer to the NetNumen™ Unified Network

ZXR10 6800 series Management System Operation Guide (Data
equipment Product NE Management).
7 The resource view Refer to the NetNumen™ Unified Network

supports topology Management System Operation Guide (Data
monitoring over Product NE Management).
CPU and memory

2.2 Important Changes

Changed Items in Compared with the V12.12.20P01, the following items in the
the V12.13.10 V12.13.10 are changed, refer to Table 6.
(Compared
With the TABLE 6 CHANGES OF V12.13.10 (COMPARED WITH V12.12.20P01)
V12.12.20P01)
o.
1 The MSTP EPS Refer to “Configuring Equipment-Level

protection can be Protection” in the NetNumen™ Unified
configured in the Network Management System Operation
end-to-end mode. Guide (SDH NE Management)
2 Real-time MSTP Refer to “Basic Maintenance Operations”

monitoring in the NetNumen™ Unified Network
Management System Operation Guide (SDH
NE Management).
3 Changes the Refer to “Maintenance Skills” in the

resource view NetNumen™ Unified Network Management
Management).

channel view NetNumen™ Unified Network Management
Management).

optical power view NetNumen™ Unified Network Management
Management).
6 Updates the Refer to the NetNumen™ U31 NMS R22

product function Unified Network Management System User
Guide.
7 Updates the IP Refer to the NetNumen™ Unified Network

RAN function Management System Operation Guide (IP
RAN Management).
8 Updates the Refer to “Installing the ” in the NetNumen™

installation scale Unified Network Management System
Software Installation Guide.
9 Updates the LCT Refer to the NetNumen™ Unified Network

product function Management System Local Craft Terminal
(User Guide)
10 Service cutover Refer to “Service Leasing” in the

System Operation Guide (CTN End-to-End
Management)
11 Improves the -
product operation

o.
12 Improves the Refer to “Protection Management” in the

WDM protection NetNumen™ Unified Network Management
subnetwork System Operation Guide (WDM/OTN NE
management Management)
13 Supports up to -
30000 equivalent
NEs
14 Improves the -
file management
backup policy: the
backup time and
space occupation
are reduced
15 Supports the ACL Refer to “ACL Management” in the

management NetNumen™ Unified Network Management
for 8900 serials System Operation Guide (Data Product NE
equipment Management).
16 Private network Refer to “Configuring a Route Viewer” in the

route monitoring NetNumen™ Unified Network Management
Management).
Changed Items in Compared with the V12.12.20, the following items are changed in
the V12.12.20P01 V12.12.20P01, refer to Table 7.
(Compared With
the V12.12.20) TABLE 7 NEW FUNCTIONS OF THE V12.12.20P01
o.
1 Changes the Refer to the “Installing the on Solaris”
SUN server section of the NetNumen™ Unified Network
model Management System Installation Guide.
2 Simplifies Refer to the “Installing the ” section of the

the software NetNumen™ Unified Network Management
installation disk System Installation Guide.
and changes
the installation
procedure
3 Optimizes -
the product
operation

o.
4 Changes the Refer to the following manuals:
fiber connection The “Fiber Connection” section of the
function NetNumen™ Unified Network Management
System Operation Guide (SDH NE
Management).
The “Fiber Connection” section of the
Management).
The “Fiber Connection” section of the
System Operation Guide (WDM/OTN NE
Management).
5 Optimizes the Refer to the “Managing Service Cutover”

service cutover section of the NetNumen™ Unified Network
function Management System Operation Guide
(SDH/OTN NE End-to-End Management).
6 TL1 and FTP Refer to the NetNumen™ Unified Network

northbound Management System Northbound Interface
supports the User Guide (Data Product).
5900E series
equipment
7 Supports Refer to the NetNumen™ Unified Network

daughter Management System Operation Guide (Data
cards on the Product NE Management).
2900E series
equipment
8 Supports the Refer to the NetNumen™ Unified Network

BRAS user Management System Operation Guide (Data
statistics Product NE Management).
management

Chapter 3 Product Functions
>> Topology Management
>> Alarm Management
>> Performance Management
>> Security Management
>> Configuration Management
>> Software Management
>> Log Management
>> Report Management
>> Database Management
>> License Management
3.1 Topology Management

The system is required to support the centralized management and
group management of all the managed devices due to the large
quantity and diversity of managed devices. The topology man-
agement module of the system provides various topology man-
agement functions to display the distribution and organization of
devices on topology views.
A topology view is divided into two parts: the navigation pane on
the left part, and the topology map on the right part. The naviga-
tion pane provides a network element tree that lists all the man-
aged network elements (NEs) in the system. The topology map
shows the managed NEs on a map according to their locations and
relations in the network. In addition, some alarm and configura-
tion information of NEs is also available on the topology view.
The following lists the topology management functions that you
can use in the system.
� Navigation
The NEs added in the system are listed on an NE tree in the
navigation pane, corresponding to the NE icons displayed on
the topology map. When you add or delete an NE through
shortcut menu on the NE tree, corresponding NE icon appears
or disappears on the topology map at the same time. You can
locate corresponding NE icon on the topology map by clicking
the NE on the NE tree. Besides some topology management
functions, the NE tree also provides the access to some other
management functions through shortcut menu, including con-
figuration management, fault management, and performance
management functions.
� Graphic Display

The topology map shows all NEs managed by the system as

well as their relations in the network. You can search for spe-
cific NEs on the topology map, lock some NE icons to prevent
them from being moved by other users, and view the statisti-
cal information of the NEs in the system, including NE quantity,
link quantity, group quantity, and alarm information.
� Display of NEs and Links
NEs and links between NEs that have connection relations are
displayed on the topology map. You can set the attributes of
an NE to determine whether to show its peripheral device.
� Topology Map Control
On the topology map, you can do the following operations.
� Drag, zoom in, and zoom out the topology map.
� Go to, back to, and forward to a specific NE or topology
layer.
� Search for specific NEs.
� Change the background of the topology map.
� Synchronize the configuration information of NEs on the
topology map from the server and refresh the display on
the client without changing the positions and connection
relations of those NEs.
� Select the layout mode of NE icons on the topology map,
including hierarchical layout, tree layout, radial tree layout,
spring embedded layout, and uniform length edges layout.
� Filtered Display
On the topology map, you can set filtering conditions to filter
the NEs or links that you do not concern from the topology
map. The filter conditions can be NE name, IP address, link
name, NE type, link type, and/or group type.
� Authorization-Based Data Display
To ensure the system security, the system only provides topol-
ogy management functions to authorized users.
� Alarm Display
On the topology map, an NE or link is highlighted in different
colors when some fault(s) occur in it according to the fault
severity and the acknowledgement status of corresponding
alarm(s).
� Group-Based View
To manage NEs more effectively, you can group NEs based on
certain rules. Then the topology map can arrange the NEs by
group.
3.2 Alarm Management

The fault management module monitors the operating status of
the equipment in real time. The alarm status is displayed by col-
ors. The fault management includes the following functions:

� Alarm Data Collection and Storage

The system collects alarm information sent by the managed
NEs in real time, converts the format of the alarm information
as required, and then stores all the alarm information in the
database. In addition, the fault management module can au-
tomatically save the alarm information into files according to
preset parameters.
� Graphic Display and Localization of Alarms
The system monitors the managed NEs in real time and dis-
plays the received alarm information on the client screen. On
the topology map, you can open the board management view
of a faulty NE to locate the board where an alarm is generated.
� Alarm Acknowledging and Unacknowledging
When an alarm is reported and displayed on the client screen,
you can acknowledge the alarm. The system saves the record
of your acknowledging operation. You can also cancel the
acknowledgement of an alarm, that is, unacknowledging the
alarm. All acknowledging and unacknowledging operations are
recorded, including the information of the users performing
the operations as well as the operation time.
By observing the acknowledgement status of alarms, you can
know the running status of the network, find the latest alarm
information quickly, and process the alarms respectively ac-
cording to their acknowledgement status.
� Real-Time Alarm Monitoring
The system shows real-time alarms in the form of list on the
client screen. In the alarm list, you can filter alarms by occur-
rence time or severity level. When the system receives new
alarms from managed NEs, it refreshes the alarm list auto-
matically.
� Alarm Clearing
The system automatically clears an alarm from the active alarm
list after the fault causing this alarm is removed.
� Alarm Synchronization
Alarm synchronization includes the synchronization of alarm
information between the server and the managed NEs (that is,
the alarm sources), and the synchronization of alarm informa-
tion between the client and the server.
supports two alarm synchronization modes: manual synchro-
nization and automatic synchronization.
� In the manual synchronization mode, the alarm synchro-
nization is initiated by a user.
� In the automatic synchronization mode, the alarm synchro-
nization is initiated by the system.
The system initiates an alarm synchronization process in the
following situations:
� The broken connection between the client and the server
recovers.
� The broken connection between the server and a managed
NE in the network recovers.

� The server is restarted.

� Output of Alarm Data
All alarm information can be output to *.txt, *.xls, *.pdf,
*.html, or *.csv files.
� Alarm Rule Management
The system supports the customization of various alarm rules
for managing and processing received alarms, such as alarm
storage, alarm filtering, alarm reclassification, and alarm cor-
relation.
For example, by creating an alarm filtering rule, you can filter
less important alarms and reduce the count of alarms displayed
on the client screen. In this way, you can easily find critical
alarms and handle them first.
A fault in an NE may cause several correlated alarms. By
setting a correlation rule, you can collapse a series of corre-
lated alarms caused by the same fault and reduce the count of
alarms displayed on the client screen.
� Modification of Alarm Settings
This function allows you to define the alarm management
mode, reset the indication colors of alarms, and set the thresh-
olds of environment parameters, for example, temperature,
humidity, and smog existence.
� Alarm Query and Statistic
The alarm query and statistic function enables you to query
alarms stored in the database and get a statistic report of these
alarms. By analyzing the alarm report, you can find problems
in the network and improve the network performance by re-
moving those problems. For example, you can query history
alarms, active alarms and notifications.
In addition, the system can count alarms according to their
types and severity levels, and indicate the distribution of dif-
ferent alarms by displaying the statistic information in various
chart forms.
3.3 Performance Management

The purpose of performance management is to improve the net-
work performance and efficiency and provide a basis as well as
suggestions for proper planning of network resources. The perfor-
mance management module of the system can collect the perfor-
mance data of network elements in the network. By observing and
analyzing the collected performance data, you can know the run-
ning status of equipment in the network, evaluate the efficiency of
equipment and the network, and monitor the quality of service in
the network.
The following lists the performance management functions that
you can use in the system.
� Data Query

You can query raw performance data stored in the database

after setting the query conditions, for example, NE type, time
period and performance object. The query result is displayed
in a list. You can print the query result or save it as a file.
� Data Synchronization
The system can automatically synchronize performance data
from the managed NEs to the server, and synchronize perfor-
mance data from the server to the client. You can also initiate
the synchronization of performance data through a client.
� Data Report
The system can generate a performance data statistic report
to show current KPIs, which can also be output as *.xls, *.pdf,
*.html, and *.txt files. A predefined template or user-defined
template can be used to generate the report you want.
In addition, you can create a report task by specifying the re-
port type, template, object, time, and file name. When the
preset is up, the system generates the customized report ac-
cording to the task. The customized task is stored in the data-
base, which can be queried, modified and deleted. After the
report is generated by the system, you can view the report and
save it as an *.xls file.
The system can send the periodically-generated report to a
user in the specified format through E-mail as required.
3.4 Security Management

The security management module of the system provides security
management functions to ensure that only authorized users can
access and manage network resources.
For better understanding of security management, the following
explains some basic concepts related to security management, in-
cluding role, role set, department, and user.
� Role
A role specifies the management permission for a user group,
including the operation permission and manageable resources.
� The operation permission allows the user group to use spe-
cific functional modules of the network management sys-
tem. For example, if a role has the operation permission of
the log management module, the users acting as the role
can perform log management operations, such as querying
logs and maintaining logs.
� The manageable resources refer to subnetworks and/or
network elements that can be managed by the role.
� Role Set
A role set is a set of roles. The management permission of a
role set involves the management permissions of all roles in
the role set.
� Department

Departments are specified in the network management sys-

tem to simulate the actual administrative departments. In this
way, the system administrator can conveniently organize and
manage users in the system. A newly-created user must be-
long to a department.
� User
A user is an operator who is authorized to log in to the system
and perform operations in the system. While creating a user,
the system administrator assigns the management permission
to the user by specifying a role or role set and allocates the
user to a department according to the actual situation.
For the model of relations among user, role, role set, department,
operation permission, and manageable resources involved in the
security management, see Figure 4.
FIGURE 4 RELATION MODEL OF SECURITY MANAGEMENT
The following explains the relation model of security management.

� A user is administered by a department.
� The management permission of a user depends on the role set
assigned to the user.
� A role set includes one role or a set of roles. Correspondingly,
the management permission of a role set is the collection of
management permissions of all roles in the role set.

� The management permission of a role depends on the oper-

ation permission and manageable resources specified for the
role.
The system provides the following security management functions.
� Security Event Recording
The system can record security events, for example, authenti-
cation failure, locking a user, and disabling a user. The system
administrator can know the situation of user accounts in the
system by observing the security event log.
� Reporting of Security-Related Alarms
The system can report alarms to the administrator when some
important security events occur, for example, a user account
is locked.
� Setting of Login Time Period
By using the security management module, you can set a limit
of the time period for a user. The user is allowed to log in to
the system only in this period.
� User Account Management
A user can query and change its password, policy, locking rule,
and validity period. For example, you can specify a rule like
this: if a user enters the wrong password three times, the user
account will be locked for the purpose of preventing unautho-
rized login.
� Login User Management
� Forcible Removal of Users
The super administrator of the system can remove a user
from the system forcibly to avoid unauthorized operations
performed by this user and ensure the system security.
� IP Address Setting of Super Administrator
You can set the IP address of the super administrator to ensure
the security of the super administrator account. After you set
the IP address, the super administrator can only log in to the
system on the client with the same IP address as the preset
one.
� User Password Modification
The super administrator of the system can change the pass-
words of all the other users.
� User Status Check
If you log in to the system as a super administrator, you can
check the locking status of other users, enable the automatic
unlocking function of other users, and set the unlocking time.
� Locking of Clients
If no operation is performed for on a client a long time, the
system will lock the client and force the login user on the client
to log out of the system. The user is required to log in to the
system again before performing any operation in the system.

3.5 Configuration Management

The configuration management module of the system allows you to
configure the managed NEs in the system. Different NEs support
different configuration management functions.
The CTN NE supports the following configuration:
� NE basic configuration
� Clock time configuration
� Interface configuration
� Protocol configuration
� Configuration for single NE service and end-to-end service
� OAM configuration
� Qos configuration
� Configuration for equipment-layer protection
� Configuration for network-layer protection
� Configuration for network expansion and shrink
� Alarm configuration
� Performance configuration
� Overhead configuration
� Port migration
� Channel view
� Resource view
� Optical power view
� Real-time traffic monitoring
The SDH NE supports the following configuration:
� Gateway NE configuration
� Clock configuration
NE time configuration
Service telephone configuration
NE and board configuration
Configuration for equipment-layer protection
� Configuration for network-layer protection
Configuration for single NE service and end-to-end service
� Ethernet service configuration
� Configuration for CTN and SDH mixed networking service
� Clock view
� Network maintenance
� Optical power view
� Data synchronization
The OTN NE supports the following configuration:

NE clock synchronization configuration
NE basic configuration
Protection configuration
Configuration for single NE service and end-to-end service
� APR-AOSD configuration
� Optical power configuration.
� Spectrum configuration
� Overhead configuration
� Service telephone configuration
The following hybrid networks are supported:
� Configuration for CTN and SDH mixed networking service
� Hybrid network composed of SDH and WDM/OTN NEs
� Hybrid network composed of CTN and router/switch NEs
The IP NE supports the following configuration:
� Basic NE configuration
� Interface configuration
� L2 configuration
� L3 configuration
� Configuration for single NE service and end-to-end service
� Security configuration
� UAS configuration
� OAM configuration
� QoS configuration
� Alarm configuration
� Performance configuration
3.6 Software Management

The system allows you to upgrade the board software in a batches,
load the equipment software, and manage the software versions.
In the system, you can conveniently load the software package
of new version to the managed bearer equipment. The system
can manage bearer equipment with different software versions.
You can conveniently switch the version to another for the equip-
ment when necessary. If the upgrade fails, the system enables
the equipment to roll its software back to the previous one.
The E300, T31, and U31 R22 can be upgraded to the current ver-
sion. The client software can be automatically downloaded from
the server.

3.7 Log Management

The system provides three types of logs: operation log, security
log, and system log.
� Operation Log records operation information, including user
name, operation level, operations, command function, opera-
tion object, object group, object address, start time, operation
result, cause of operation failure, operation end time, host ad-
dress, and access mode.
� Security Log records login information, including user name,
host address, log name, operation time, access mode and de-
tails of the log.
� System Log records the completion state of time tasks on the
server, including source, level, log name, details, host address,
start time, end time, and related log.
The log management module of the system provides the following
log management functions.
� Log Query
You can set filtering conditions to query specific logs in the
system, and save or print the query result.
� Log Backup
The system can back up the logs in the system as files accord-
ing to the specified number of days or storage capacity.
3.8 Report Management

The system provides a rich report resource for users to query in-
formation including configuration report, information report, sta-
tus report, and statistics report.
Users can check, export or print reports upon actual requirements.
3.9 Database Management

The system provides powerful database management functions to
ensure the security of the system database, including the backup,
restoration, and monitoring of database.
The database management functions include:
� Database Monitoring
If the database capacity reaches the preset threshold, the will
generate an alarm.
� Database Backup
� Offline Data Restoration
� Scheduled Backup

� Manual Backup
3.10 License Management

The purpose of license management is to control the management
authorities of the system and NEs.
� NE license management: controls the types and quantity of
manageable NEs.
� NMS license management: controls the NMS functions, such
as exceptional service management, service cutover manage-
ment, and northbound interface.


Chapter 4 Product Architecture
>> Hardware Architecture
>> Software Architecture
4.1 Hardware Architecture

The system adopts a client/server architecture. The client in the
system communicates with the server through TCP/IP.
The hardware configuration of the system depends on the scale
of the network to be managed and the system load. Generally, a
high configuration Unix/Windows series workstation is used as the
server because the server runs all core functional modules of the
system, stores and maintains massive network management data.
The configuration of the client is relatively lower because the task
of the client is connecting the server and displaying the operation
results. A personal computer (PC) can be used as the client of the
system.
In terms of logical structure, two types of devices are deployed at
the server: host and storage device.
� The host is the physical foundation of the system. It processes
data in the system. The system performance greatly depends
on the processor speed of the host.
� Storage devices are used to save the data in the system. For
storing large amounts of important data in the system, exter-
nal data storage devices with high capacity and reliability are
required besides the built-in disks in the host.
In terms of function, a server cluster, including application server
and database server, can be deployed at the server. These servers
can be configured together on the same host, or independently on
different hosts.
To ensure high availability and security, dual servers can be used
in the system, see Figure 5.

FIGURE 5 DUAL-SERVER SYSTEM
As shown in Figure 5, the dual-server system adopts the Veritas

Cluster solution to monitor the active and standby servers and
implement the switching between them. The disk array keeps the
consistency of the data between two servers through two routes.
When the active server fails, the Veritas Cluster System, which
monitors the heartbeat between dual servers, detects the fail-
ure. Then the Veritas Cluster System switches the system to the
standby server for providing continuous network management ser-
vices.
4.2 Software Architecture

Object-oriented technologies are adopted to design the software
based on JAVA 2 platform Enterprise Edition (J2EE). The software
modules can be deployed in an integrated or distribute way to
manage bearer network elements (NEs).
In addition, the software provides CORBA, SNMP, DB and File in-
terfaces for connecting the system to a upper integrated NMS or
Operation Support System (OSS).
By using the software, you can configure and maintain individual
bearer network elements, and implement the integrated monitor-
ing and maintenance of all network elements from the network
management point of view.
The system provides two software: server software and client soft-
ware.
� Server Software

Chapter 4 Product Architecture
The server software can be divided into several modules, each

of them implementing certain functions. For these modules
and their functions, refer to Table 8.
TABLE 8 SERVER SOFTWARE MODULES
Module Function
Network Provides northbound access function

management (NAF) to support the connection to a
interface module upper integrated NMS through northbound
interface.
Topology Provides topology management functions,

management module that is, the management of topology
objects.
Fault management Provides fault management functions, such

module as alarm collection, alarm query, and alarm
processing.
Performance Provides performance management

management module functions, such as the collection of NE
performance data, real-time performance
monitoring, and the report of threshold
crossing alarms.
Security Provides security functions, such as the

management module management of user rights and user
groups.
Configuration Provides configuration management

management module functions, such as the configuration of NEs,
and the query of configuration data.
Software Provides software management functions,

management module such as the query of software version,
software upgrade, activation and
deactivation of the software.
Log management Provides report management functions,

module such as the management of system
reports, user logs, and NE logs.
Report management Provides a report tool that can be used to

module customize specific reports.
Database Supports the management of Oracle

management module database, including database backup,
restoration, and monitoring.
Inventory Supports the addition, deletion,

management module modification, query, synchronization,
import and export of NE inventory data.
NE adaptation Acts as an adapter for connecting various

module NEs to the software.
� Client Software
The client software provides a graphic user interface (GUI).
After connecting to the server, the client displays the results of

management operations in the system. On the GUI, you can

operate and maintain the NEs managed by the system.

Chapter 5 Product Interfaces
>> Logical Interfaces
>> Physical Interfaces
5.1 Logical Interfaces

Internal The internal interfaces of the system refers to the communication
Interfaces interfaces between the server and the client. They adopt TCP/IP
for communication. In the system, the server and the client com-
municate with each other through a Local Area Network (LAN) or a
Wide Area Network (WAN). The communication bandwidth is equal
to or greater than 2Mbps.
Southbound Southbound interfaces refer to the communication interfaces be-
Interfaces tween and the managed NEs.
The supports the SNMP, Syslog, Telnet/SSH, FTP/TFTP, and private
interfaces.
Northbound The northbound interfaces locate between and the upper inte-
Interfaces grated NMS/OSS (Operation Support System). The upper inte-
grated NMS/OSS can manage the northbound interfaces through .
The northbound interfaces have comply with special interface
standards that specify the information model, interface technical
modes, and interface functions for the connection between the
EMS/NMS and the upper integrated NMS/OSS. The northbound
interfaces are the basis for centralized network management and
integrated management and maintenance.
For the position of northbound interfaces in the network, refer to
the section of Position.
provides the following northbound interfaces:
� CORBA northbound interface
CORBA is a standard for the distributed computer environment
and the computer network interconnection. can interact with
the upper integrated NMS/OSS through the CORBA interface
that complies with the TMF standards and protocols.
The CORBA interface of supports the functions such as config-
uration management, alarm management, performance man-
agement, and property management.
� SNMP northbound alarm interface
provides the SNMP northbound alarm interface, which sends
the alarm message to the upper integrated NMS/OSS.
� FILE/FTP northbound interface
The FILE/FTP northbound interface obtains the information
of all the NEs in the network, the network topology, history

alarms, and history performances. Then, it composes files

based on the above information and sends the files to the FTP
server. The upper integrated NMS/OSS can get these files
from the FTP server.
� XML northbound interface
Through the XML northbound interface, the upper integrated
NMS/OSS can perform uniform management of all the ZTE
transmission equipment.
� TL1 northbound
The upper-layer network management systems/OSS can per-
form the configuration management and resource manage-
ment for IP equipment via the U31 R22 TL1 northbound in-
terfaces.
5.2 Physical Interfaces

For the physical interfaces provided by the system, refer to Table
9.
TABLE 9 PHYSICAL INTERFACES
Interface Type Description
10M/100M adaptive
Used to connect 10M/100M Ethernet
Ethernet interface
GE interface Used to connect a Gigabit Ethernet
Used to connect a packet switched

X.25 interface
network

Chapter 6 Networking Modes
>> Network Architecture Requirements
>> Non-Cascade Networking Modes
>> Cascade Networking Modes
>> Distributed System
6.1 Network Architecture

Requirements
For the bandwidth requirement for the network architecture, refer
to Table 10.
TABLE 10 BANDWIDTH REQUIREMENT FOR THE NETWORK ARCHITECTURE
Item Bandwidth
Bandwidth between the client and At least 2 Mbit/s is recommended.

the server
Bandwidth between the primary At least 10 Mbit/s is

server and the standby server recommended.
6.2 Non-Cascade Networking

Modes
The system generally adopts a non-cascade networking mode, in
which a single server is used to manage the whole network. The
management capability of the system is measured based on this
networking mode.
The following three non-cascade networking modes are available:
� Non-Cascade Local Networking
� Non-Cascade Remote Networking
� Non-Cascade Integrated Networking
6.2.1 Non-Cascade Local Networking
Non-cascade local networking is the most common networking

mode used by centralized network management systems. It is a
simple networking mode, in which the server, clients and NEs are

all located in the same Local Area Network (LAN) and connected
with each other through Ethernet. In this networking mode, the
server connects to the managed NEs through LAN.
The following describes the topology of this networking mode and
the required devices for the local networking.
� Topology
For the topology of the non-cascade local networking of , see
Figure 6.
FIGURE 6 NON-CASCADE LOCAL NETWORKING
6.2.2 Non-Cascade Remote Networking
The system supports various non-cascade remote networking

modes, in which the clients are located remotely from the server.
Different remote networking modes have the same network
topology and follow the same networking principle. Specific
transmission equipment is used to connect the system to a Wide
Area Network (WAN). The server and the client are located in
different LANs with corresponding routers and hubs.
The non-cascade remote networking supports the transmission
over leased line of Digital Data Network (DDN), E1 line, or High-
data-rate Digital Subscriber Line (HDSL).
The following introduces the remote networking based on DDN
leased line transmission mode and E1 transmission mode, which
are commonly used in the actual telecommunication networks due
to their quality and cost advantages.
� Remote Networking Based on DDN Leased Line

The stable and reliable DDN provides a high transmission rate

from 64kbps to 2Mbps. In this remote networking mode,
routers and baseband MODEMs are used. At the server, a
hub is connected to a router and the router is connected to
the leased line of the DDN through a baseband MODEM. The
remote client is connected to the leased line in the same way
through its Ethernet interface.
For the remote networking of the system based on DDN leased
line, see Figure 7.
FIGURE 7 NON-CASCADE REMOTE NETWORKING OVER DDN
� Remote Networking Based on E1 Transmission

In the non–cascade remote networking over E1 transmission,
E1 (2Mbit/s) lines are used to transmit IP packets. At both ends
of an E1 line, timeslot extractors are needed. The maximum
transmission rate of each timeslot is 64kbps. By the channel-
ization technology, N timeslots can be used together to get a
rate of N×64kbps, which meets the requirements for different
transmission rates. A router and a channelized E1 module can
be used together as a stable and reliable timeslot extractor.
For the remote networking of the system based on E1 trans-
mission, see Figure 8.

FIGURE 8 NON-CASCADE REMOTE NETWORKING BASED ON E1

TRANSMISSION NETWORK
6.2.3 Non-Cascade Integrated

Networking
The integrated networking is a combination of local networking

and remote networking. Local NEs/clients and remote NEs/clients
coexist in this networking mode. For the topology of the integrated
networking over DDN, see Figure 9.

FIGURE 9 NON-CASCADE INTEGRATED NETWORKING OVER DDN
6.3 Cascade Networking Modes

Multiple servers can be cascaded to manage a large-scale network.
The lower-level servers manage part of the network, responding
to the requests and processing the data coming from this part.
The upper-lever server connects to multiple lower-level servers,
processing the information from the lower-level servers and re-
sponding to the requests from the upper-level clients. It manages
the whole network through lower-level servers.
The cascade networking can be classified into local cascade net-
working and remote cascade networking according to the physical
relations between the upper-level server and lower-level servers.
6.3.1 Local Cascade Networking
When the scale of a network is so large that a single system can-

not manage the whole network, the cascade networking mode can
be used to increase the management capacity. In this networking
mode, the lower-level servers manage the devices in correspond-
ing areas. They are integrated and connected to the upper-level

server through LAN. Therefore, the upper-level server can imple-

ment the centralized management of the whole network.
In the local cascade networking mode, the upper-level server and
lower-level servers are located in the same LAN. Any of the non-
cascade networking modes described earlier can be used for each
server and the clients corresponding to it.
For example, the following illustrates the networking of a sys-
tem, where the local cascade networking mode is used for the up-
per-level server and two lower-level servers, and the non-cascade
local networking mode is used for each server and corresponding
clients, see Figure 10.
FIGURE 10 LOCAL CASCADE NETWORKING
The upper-level server and the lower-level servers are integrated

in the same LAN, and each server has corresponding clients, see
Figure 10.
Note:
For the logical model of upper-level client and lower-level clients,
see Figure 10. Physically, the management processes of the lower-
level clients can be deployed on the upper-level client.
6.3.2 Remote Cascade Networking
In the remote cascade networking mode, the upper-level server

and the lower-level servers are connected through DDN or E1
transmission network. All non-cascade networking modes de-
scribed earlier can be used for each server and corresponding
client.
For the topology of a remote cascade networking mode, see Figure
11.

FIGURE 11 REMOTE CASCADE NETWORKING
The upper-level server and lower-level servers are integrated

through E1 transmission network instead of a LAN, see Figure 11.
6.4 Distributed System

The commercial application capability meeting the requirement of
high capacity and load is a key point for a centralized network man-
agement system, which has a bottleneck of load processing due
to huge amount of performance and alarm data. The distributed
deployment of the centralized network management system can
improve the overall processing capability of the system, eliminat-
ing the bottleneck of load processing.
The system supports the flexible deployment of its functional mod-
ules on different servers in a distributed way. The distributed de-
ployment not only improves the system stability, but also provides
convenience for troubleshooting and module upgrade.
The distributed system is designed on the application layer, which
follows the same basic principle as other application systems.
There is no uniform requirement for the topology of the dis-
tributed system. For a typical topology of a distributed network
management system, in which the database server, application

server and access server are deployed in a distributed way, see

Figure 12.
FIGURE 12 TYPICAL DISTRIBUTED DEPLOYMENT OF THE SYSTEM
The following distributed deployment modes are available for a

centralized network management system:
� Distributed Deployment of Database
In this mode, the database is independently deployed on a
server.
� Distributed Deployment of Access Servers
Distributed deployment of access servers supports access of
multiple subsystems to the centralized network management
system for the purpose of centralized management. For exam-
ple, three access servers can be arranged to access nine radio
network subsystems to the centralized network management
system. Each server supports the access of three radio net-
work subsystems. The functions of an access server include
transferring information between upper-level and lower-level
interfaces, collecting the data and storing the data in the data-
base.
� Distributed Deployment of Application Servers
In this mode, fault management server, performance manage-
ment server and other management servers are deployed in-
dependently according to the actual needs.

Chapter 7 Technical Specifications
>> Performance Specifications
>> Interface Specifications
7.1 Performance Specifications

For the performance specifications of the system, refer to Table
11.
TABLE 11 PERFORMANCE SPECIFICATIONS
Item Specification
System response � When the equipment operates properly, the

time response time for user operations is less than
3 s.
� When the equipment operates abnormally
(frequent alarms occur), the response time for
user operations is less than 30 s.
Mean response time for alarm display, which refers

to the duration from the time when NE generates
an alarm to that when EMS displays the alarm, is
less than 10 s.
Mean system response time, which refers to the

duration from the time when an alarm is reported
to that when the client displays the alarm, is less
than 3 s.
Master/slave When the hot standby redundancy is used for the

network network management, the time for switching the
management master and slave network management system is
system less than 10 min.
performance
Data storage Alarm data storage time: It can be configured by

capacity users. The default value is 6 months.
Performance data storage time: It can be

configured by users. The 15–min performance
history data generated in at least 3 months and the
24–hour performance history data generated in at
least 6 months can be stored.
System log storage time: It can be configured by

users. The default value is 6 months.
Security and operation log storage time: It can be

configured by users. The default value is 6 months.

Note:
When the system operates with full load, the system response time
should not be larger than 150% of the above specifications.
7.2 Interface Specifications

provides a diversity of interfaces, including:
� Communication interfaces between the system and managed
NEs, adopting SNMP, TELNET/SSH, FTP, and SYSlog.
� File transfer interfaces between the system and managed NEs,
adopting FTP.
� Physical Interfaces
� 10M/100M adaptive Ethernet interfaces
� GE interface for connecting to Gigabit Ethernet
� X.25 interface for connecting to Packet Switched (PS) net-
work

Chapter 8 Compliant Standards
complies with the following recommendations and standards.

� ITU-T Recommendations
� ITU-T M.3000, Overview of TMN recommendations
� ITU-T M.3010, Principles for a Telecommunications man-
agement network
� ITU-T M.3016, TMN security overview
� ITU-T M.3020, TMN Interface Specification Methodology
� ITU-T M.3100, Generic Network Information Model
� ITU-T M.3101, Managed Object Conformance Statements
for the Generic Network Information Model
� ITU-T M.3200, TMN management services and telecommu-
nications managed areas: overview
� ITU-T M.3300, TMN F interface requirements
� ITU-T M.3400, TMN Management Function
� ITU-T Temporary Document 69 (IP Experts): Revised draft
document on IP access network architecture
� ITU-T X.701-X.709, Systems Management framework and
architecture
� ITU-T X.710-X.719, Management Communication Service
and Protocol
� ITU-T X.720-X.729, Structure of Management Information
� ITU-T X.730-X.799, Management functions
� RFC Standards
� RFC1157, Simple Network Management Protocol
� RFC1213, Management Information Base for Network Man-
agement of TCP/IP based internets: MIB-II
� RFC1901, Introduction to Community-based SNMPv2
� RFC1902, Structure of Management Information for Ver-
sion 2 of the Simple Network Management Protocol (SN-
MPv2)
� RFC1903, Textual Conventions for Version 2 of the Simple
Network Management Protocol (SNMPv2)
� RFC1905, Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)
� RFC2037, Entity MIB using SMIv2
� RFC2233, The Interface Group MIB using SMIv2

� RFC1558, A String Representation of LDAP Search Filters

� RFC1777, Lightweight Directory Access Protocol
� RFC1778, The String Representation of Standard Attribute
Syntaxes
� RFC1959, An LDAP URL Format
� RFC2251, Lightweight Directory Access Protocol (v3)
� TMF Standards
� GB901, A Service management Business Process Model
� GB921, Enhanced Telecom Operations Map
� GB909, Generic Requirements for Telecommunications
Management Building Blocks
� GB908, Network Management Detailed Operations Map
� GB914, System Integration Map
� GB917, SLA Management Handbook V1.5
� NMF038, Bandwidth Management Ensemble V1.0
� TMF508, Connection and Service Management Information
Model Business Agreement
� TMF801, Plug and Play Service Fulfillment Phase 2 Valida-
tion Specification V1.0
� TMF605, Connection and Service Management Information
Model
� NMF037, Sub-System Alarm Surveillance Ensemble V1.0
� OMG Standards
� Interworking Between CORBA and TMN System Specifica-
tion V1.0
� Specifications by Ministry of Information Industry and
China Telecom
� YD/T 852-1996 General Principles for the Design of
Telecommunications Management Network (TMN)
� YD/T 871-1996 Generic Information Model of Telecommu-
nications Management Network (TMN)

Quick Start
Basic Operation Flow
Figure 13 shows the basic operation flow of system.
FIGURE 13 OPERATION FLOW OF THE
1. Start the server program

Starting the server program is the premise of using the network
management system.
Caution:
Do not start/shut down the server program frequently.
2. Log in to the client portal

The entrances of the management modules are integrated in
the client portal. The user can quickly enter the management
views through the client portal.
3. Log in to the client.
The user interfaces of the system are integrated in the client.
After logging in to the client, you can perform the relevant
management operations.

4. Perform management operations

� Customization of GUI elements
To customize the parameters such as system parameters,
login user information, performance module parameters,
alarm sound and color, and holiday information.
� management
The user can create and manage the information of the .
� Topology management
The user can query and present the network topology and
the service topology in the topology management view.
� Security management
The user can manage the department, user, role, role set,
operation set, and user account rule in the security man-
agement view.
� Alarm management
The user can perform the functions of alarm monitor,
alarm query, alarm statistics, and alarm configuration in
the alarm management view.
� Performance management
The user can query and collect the performance data in the
performance management view.
� Routine maintenance
The user can perform the functions of log management, se-
curity management, and system maintenance in the view.
� Log management
The user can perform the functions of viewing, querying,
and exporting logs in the log management view.
System Startup and Exit
Starting the Server
Abstract This procedure describes how to start the server on Windows.
Prerequisites You have installed the server software successfully.
Steps � On the desktop of the Windows operating system, select Start
> All Programs > NetNumen Unified Management Sys-
tem > NetNumen Console, and the Console dialog box is
displayed.
Note:
� automatically starts all procedures and not manual opera-
tions is required.
� The EMS console startup file console.bat is located in the
ums-server directory in the path where the EMS is in-
stalled.
END OF STEPS

Logging in to the Client

Abstract This procedure describes how to log into the client on Windows.
Prerequisites
Ensure that the server is running properly.
Steps 1. On the desktop of the Windows operating system, select Start
> Programs > NetNumen Unified Management System >
NetNumen Client, and the Login dialog box is displayed.
2. Enter User Name, Password, and Server Address in the

Login window.
Caution:
In the , the default user name is admin, and the password is
null. Be sure to modify the password of the admin user after
successful login for the first time to ensure the account secu-
rity.
Tip:
In the Login window, click on the right side of the server

address to display the Config Bureau dialog box. In the Con-
fig Bureau dialog box, you can configure bureau name and the
corresponding server address. The configuration information
will be displayed in the drop-down list of the Server Address
to facilitate the user to select.
3. Click OK.
END OF STEPS
Portal Operations
About Portal

The provides a client portal as a unified login interface. After start-

ing the client portal, you can start the client or other specific man-
agement tools by clicking corresponding links. The started client
or other management modules can communicate with the server
and load data from the server directly.
Logging in to the Client Portal
Abstract The provides a client portal as a unified login interface. After start-
ing the client portal, you can start the client or other specific man-
agement modules by clicking corresponding links. The started
client or other management modules can communicate with the
server and load data from the server directly.
Prerequisites The server is operating properly.
Steps 1. On the desktop of the Windows operating system, click Start,
point to Programs > NetNumen U31 Unified Network
Management System, and click U31 Client Portal. The
Login dialog box is displayed.
2. Enter the User Name, Password, and Server Address.
Caution:
For the , the default user is admin, and the password is null.
The user should modify the password after login.
3. Click OK.
END OF STEPS
Result After successful login, the Portal dialog box is displayed, see
Figure 14.

FIGURE 14 PORTAL
The buttons in Portal dialog box are described as follows:
Button Description
Screen Lockup
Log out
Exit
About
Start the U31 client
Start alarm management module
Start performance management module
Start system maintenance module
Locking the Portal Screen

Abstract This procedure describes how to lock the portal screen.
Prerequisites You have logged in to the client.
Steps 1. In the Portal dialog box, click on the toolbar. The Confirm
dialog box is displayed.

2. Click OK.
END OF STEPS
Logging out of the Portal

Abstract This procedure describes how to log out of the portal.
Prerequisites You have logged in to the client portal.
Steps 1. In the Portal dialog box, click on the toolbar. A Confirm

2. Click OK.
END OF STEPS
Exiting the Portal

Abstract This procedure describes how to exit the portal.
Steps 1. In the Portal dialog box, click on the toolbar. A Confirm

2. Click OK.
END OF STEPS
Starting the Client

Abstract Portal provides shortcut for the user to access the main window
of the system. By portal, the user can access the main window
without entering password.
Steps � In the Clients area of the Portal dialog box, click Client to
display the Client window.
� In the Clients area of the Portal dialog box, click Fault Man-
agement to display the Fault Management dialog box.
� In the Clients area of the Portal dialog box, click Perfor-
mance Management to display the Performance Manage-
ment dialog box.
� In the Clients area of the Portal dialog box, click Mainte-
nance to display the Maintenance dialog box.
END OF STEPS
System Setting
Setting System Parameters
Abstract During the system setting, you can change the waiting time before
automatic system locking or logout, and set the maximum number
of system messages displayed on the client window.
Prerequisites You have the authority of system setting.
Steps 1. In the main window of the client window, select System >
Customize > System Setting. The System Setting dialog
box is displayed.
2. Configure the parameters in the Autolock Setting page.

Parame- Description
ter
Enabled Select whether to enable the autolock function.
Idle time Enter the Idle time for automatic screen lock. (Value
(mi- range: 1–6000)
nute(s))
Lock type Select locking type, including:

� Lock Screen: return to the Unlock dialog box.
Click OK to unlock the screen.
� Lock Operation: The GUI will be visible, but
operations are disable. Press shortcut key
<Ctrl+U> to unlock the operation.
3. Click the Auto Logout. The Auto Logout page is displayed.

Configure the parameters in the Auto Logout page.
Parame- Description
ter
Enabled Whether to enable the automatic logout function.
Idle Time Select the Enabled check box, and enter a waiting
time in the text box. (Value range: 1 to 5000)
4. Click the Message Area tab. The Message Area page is dis-
played. Set the parameters in the Message Area page.
Parameter Description
Set Hint Maximum count of hint message. (Value range:

Message Count 1 to 5000)
Set Error Maximum count of hint message. (Value range:

Message Count 1 to 5000)
5. Click the Query Settings tab. The Query Settings page is

displayed. Configure the parameters in the Query Settings
page.
Query results Enter the maximum count of query results that

count in one can be shown on each page. (Value range:
page 50–500)
This setting is effective only for the query of
past data. It does not restrict the query of
current alarms.
6. Click the Window tab, and set the related parameters.

Keep the position and Select the Enabled check box, when
the size of the main you enable the client, the position and
window the same as in size of the main window will be the same
the last logout as this logout.
7. Click the Tooltip tab, and set the related parameters.
Number of seconds Value range: 1 to 1000.

before hiding tooltip
8. Click OK.
END OF STEPS
Setting the Information of Login User

Abstract This section describes how to configure the e-mail address and the
telephone number of the user.
Prerequisites You have the authority to perform this operation.
Steps 1. On the main interface of the of the client window, select Sys-
tem > Customize > Login User Info Setting. The Login
User Info Setting dialog box is displayed.
2. Set parameters in the Login User Info Setting page.
E-mail You must enter the full E-mail address. For example,
Address test@zte.com.cn
Phone � Enter a fixed or mobile phone number.

Number
� It supports numbers and half-angle connector
"-".
� More than one number should be separated by
English comma.

3. Click OK.
END OF STEPS
Setting Performance Management Preferences

Abstract This section describes how to set the relative parameters of per-
formance management module.
Steps 1. From the main menu of the client window, select System >
Customize > Performance Management Preferences.
The Performance Management Preferences dialog box is
displayed.
2. Set parameters in the dialog box.
Default dis- The meaning of each option is as follows:

play status
in the Meas- � All current tasks: displays all the current
urement tasks
Task Man- � Activated tasks: displays the activated tasks
agement
area � Suspended tasks: displays suspended tasks
� Deleted failed tasks: displays the tasks of
which consistent state is “ Failed to delete”
� Inconsistent tasks: displays the tasks of
which consistent state is “Inconsistent”
� History tasks: displays the history tasks
� All tasks: displays current and history tasks
Default dis- The meaning of each option is as follows:

play sta-
tus in the � Activated tasks: displays the activated
Threshold threshold task
Task Man- � Suspended tasks: displays the suspended
agement threshold task
area
� All tasks: displays all the suspended threshold
tasks
Time It is the time format in the performance query

Format in result.
the Result
File of
Template
Task area
Show In- The meaning of each option is as follows:

dex in the
Counter and � All indexes: displays all the performance
Index Man- indexes
agement � Frequently used indexes: displays the
area frequently used indexes
�
3. Click OK.

Note:
The configuration becomes effective when you log into the
client again.
END OF STEPS
Setting Alarm Sounds and Colors

Abstract To customize the alarm sounds and colors for clearly prompted
faults, perform the following steps:
Prerequisites You have the authority to set the alarm sounds and colors.
Customize > Alarm Sound and Color Setting, and the
Alarm Sound and Color Setting dialog box is displayed.
2. Set parameters on the Sound Setting tab.
Parame- Description
ter
Sound Set sounds for the alarms of four different levels

When respectively.
Reporting
Setting � Choose...: Choose a sound file.
� Audition: Play the chosen sound.
� Mute: If you select this check box, the fault
won’t be prompted with sound.
Sound You can only select from the two following sound
Model models.
� Sound According to the Highest Severity
Unacknowledged Alarm: select it, and the
options for sound lasting time is Short Sound
or Continuous Sound
� Receiving Alarm Message: Select it, and then
select the Sound When Restoring check box.
Click the Setting button to set this sound in the
pop-up dialog box.
Restore to Click the Restore to default button to restore

default default alarm sound.

3. Click the Color Setting tab. The Color Setting page is dis-
played.
4. On the Color Setting page, click the drop-down box on the
right side of alarm level to set colors for the alarms.

5. Click OK.
END OF STEPS
Setting Holiday Information

Abstract The purpose of setting holiday information is to help the statistics
of data in holidays, especially performance data. You can use the
preset holiday information to query the performance data during
a holiday, which makes it unnecessary to set the query period.
For example, to query the performance data in Dec. 25, you can
select the holiday “Christmas” to set the query period directly.
Prerequisites You have the authority to set holiday information.
Customize > Holiday Configuration. The Holiday Config-
uration dialog box is displayed, see Figure 15.

FIGURE 15 HOLIDAY CONFIGURATION DIALOG BOX
2. Add a holiday.
i. In the Holiday Configuration dialog box, click Create.
The Create Holiday dialog box is displayed, see Figure
16.
FIGURE 16 CREATE HOLIDAY DIALOG BOX
ii. Set the parameters in the Create Holiday dialog box.

Holiday Enter the name of holiday. The name supports

Name the following characters: (), %, _, -, and &.
Begin Date Enter the month and the date that the holiday
begins.
End Date Enter the month and the date that the holiday
ends.
Please select Select a year from the drop-down list.

the year
iii. Click OK.

3. Modify a holiday.
i. Select the holiday to be modified from the Create Holiday
dialog box.
ii. Click Modify. The Modify Holiday dialog box is displayed,
see Figure 17.
FIGURE 17 MODIFY HOLIDAY DIALOG BOX
iii. Modify the configuration properties for the holiday.
Start date Holiday start date.
End date Holiday end date.
Please select The configured start and end dates are only
the year effective in the selected year.
Select All Years If this check box is selected, the configured

start and end dates are effective in all the
years.

iv. Click OK.

4. Delete a holiday.
i. Select the holiday to be deleted from the Create Holiday
dialog box.
ii. Click Delete. The Delete Holiday dialog box is displayed,
see Figure 18.
FIGURE 18 DELETE HOLIDAY DIALOG BOX
iii. Set the properties in the Delete Holiday dialog box.
Please select Select a year to be deleted from the list.

the year
iv. Click OK.

END OF STEPS
User Interface Management

Closing the Current Window
Abstract By default, different activated application views are displayed on
the client window in an embedded way.
Prerequisites Before you begin, make sure that you have logged in to client.
Steps 1. Close the current window by doing one of the following steps:
� From the main menu of the client window, select Window
> Close Current Window.
� Click at the right-top corner of the client main interface.

� On the right-top corner of the client main interface, click

the button on the right of the button. Select Close
Current Window.
END OF STEPS
Closing All Views

Abstract By default, different activated application views are embedded in
the client window.
Steps 1. Close all application views by using one of the following steps:
> Close All Windows.
� At the right-top corner of the client main interface, click the
button on the right of the button. Select Close All
Windows.
END OF STEPS
Closing Other Windows

Abstract When there are several windows open, you can close all the other
windows except the current window.
Prerequisites � You have logged in to the client.
� You have opened several application views in the client window.
Steps � Close all application views by using one of the following steps:
> Close Other Windows.
� At the right-top corner of the client main interface, click
the button on the right of the button. Select Close
Other Windows.
END OF STEPS
Showing or Hiding the Toolbar

Abstract The user may show or hide the toolbar of the client window. For
the first startup of the system, the toolbar of the main view is
visible by default. After the first time, the display status of toolbar
on the main view for each login is consistent with the status before
the operator last exits the system.
Steps 1. When the toolbar is in showing status, select Window > Tool
Bar to hide the toolbar.
2. When the toolbar is in hiding status, select Window > Tool
Bar to display the toolbar.
END OF STEPS
Showing or Hiding the Status Bar

Abstract The user may show or hide the status bar of the client window. For
the first startup of the system, the status bar of the main interface
is visible by default. Then, the display status of status bar on the
main interface for each login is consistent with the status before
the operator last exits the system.
Steps 1. When the status bar is in showing status, select Window >
Status Bar to hide the status bar.
2. When the status bar is in hiding status, select Window > Sta-
tus Bar to display the status bar.
END OF STEPS
Showing and Hiding the Message Area

Abstract The Show Message dialog box is not visible on the client window
by default when you start the client for the first time. You can
select to show the message area or not. When you start the client
again, whether the message area is displayed depends on the state
of the message area before the client was closed last time.
Prerequisites Before you begin, make sure that you have logged in to the client.
Steps 1. When the message area is in showing status, select Window
> Message Area to hide the message area.
2. When the toolbar is in hiding status, select Window > Mes-
sage Area to display the message area.
END OF STEPS
Configuring the Toolbar

Abstract The toolbar in the client only display the buttons of some common
functional modules by default, such as viewing topology, system
monitoring, task management, and alarm monitoring. You can set
the toolbar as required so that it displays or hides the buttons of
the functional modules.
Prerequisites The toolbar is displayed.
Steps 1. Display a corresponding button of a functional module.
i. Right-click the blank area where the client toolbar is lo-
cated. A shortcut menu is displayed, see Figure 19.

FIGURE 19 TOOLBAR
ii. Select a check box to be displayed in the toolbar, such as

Log Management.
2. Hide a button of a functional module. The following step takes
Alarm Monitoring as an example.
i. On the client toolbar, right-click the corresponding button,
and select Hide this buttion:Alarm Monitoring from the
shortcut menu, see Figure 20.
FIGURE 20 HIDING THE BUTTON
END OF STEPS
Other Functions
Locking the Screen
Abstract You can lock the screen operation when you want to leave for a
short time without exiting the client window. After the screen is
locked, only you (that is, the current login user) or the system
administrator can unlock the screen.

� If the screen is unlocked by the current user, the client window

appears with the same view displayed before the screen locking
operation.
� If the screen is unlocked by the administrator, the client window
is displayed with the Topology Management view displayed
by default.
Prerequisites You have the authority to lock the screen.
Before you begin, make sure that
Steps 1. Perform one of the following operations to open the Select
Lock Type dialog box.
� Select System > Lock Screen on the main menu.
� Click the shortcut button on the tool bar.
2. Select a locking type.
TABLE 12 PARAMETER DESCRIPTION OF SELECT LOCK TYPE DIALOG BOX
Parame- Description
ter
Lock The GUI will not be visible.

Screen Unlock method: enter the correct user name and
password in the Unlock dialog box, and click OK.
Lock The GUI will be visible but operations are disabled.

Operation Unlock method: press <Ctrl+U>. The Unlock
dialog box is displayed. Enter the correct user name
and password, and click OK.
3. Click OK to display the Confirm dialog box.

4. Click OK.
END OF STEPS
Logging Out of the System

Short Description Logout is unavailable if you log in from the portal. It is only avail-
able in the main view of client. If you execute the operation of
logout, you will exit from the client and enter Login dialog box.
Steps 1. Open the Confirm dialog box by performing one of the follow-
ing operations:

� Select System > Logout on the main menu.
� Click on the toolbar.

2. Click OK.
END OF STEPS
Setting the Password of the Current Login User

Abstract This procedure describes how to set a new login password.
Steps 1. In the client window, select System > User Password Set-
ting. The User Password Setting dialog box is displayed,
see Figure 21.
FIGURE 21 USER PASSWORD SETTING DIALOG BOX
2. Set the new password.
Parame- Description
ter
Old Enter the current password. If the current password is

Password null, you do not need to enter.
User Enter the new password. The new password must be

Password different from the last five passwords.
Confirm Enter the new password again to confirm. User

Password Password must be consistent with Confirm
Password.
3. Click OK, and the Confirm message box is displayed.

4. Click OK.
END OF STEPS
Viewing the System Time

Abstract The time of the client and the server may be different. You can
check the current time of the server on the client window.

Prerequisites You have the authority to view the system time.

Steps 1. In the client window, select System > Query System Time.
The Query System Time message box is displayed, see Figure
22.
FIGURE 22 QUERY SYSTEM TIME MESSAGE BOX
END OF STEPS
Copying, Clearing, Configuring Messages

Abstract This section describes how to copy, clear, and configure the mes-
sages in message area.
Steps 1. You can do one of the following to open the Show Message
dialog box.
� In the client main menu, select Window > Show Message
from the main menu.
� Double-click at the bottom left corner of the client win-

dow.
2. Perform the operations of copying, clearing, and configuring as
needed.
Task Operation Method Operation Result
Copy In the Show Message dialog The selected message

Selected box, select the message to be is copied to the
Mes- clipboard
sage copied, and then click .
Copy All All the messages in

mes- Click in the Show Message the Show Message
sages dialog box. dialog box are copied
to the clipboard

Task Operation Method Operation Result
Clear All the messages in

All Mes- Click the button in the the Show Message
sages Show Message dialog box. dialog box are cleared
Set In the Show Message dialog Set maximum number

Mes- messages successfully
sage box, click . Enter the
Count maximum number messages
in the Set Message Count
dialog box, and then click OK.
END OF STEPS
Topology Management
Topology Management Functions
Overview The provides a series of topology management functions, includ-
ing:
� Viewing and editing network resource locations, network ar-
chitectures, links and connections, and service distribution in
different service systems.
� Displaying topological relationships between service subnet-
works along with access management.
Function � Topology Display
Description
The system displays network resources by combining the Net-
work Element (NE) tree and the topology graph. Users can
manage network resources in different views.
� Topology Operations
The provides the following topology operations:
� Searching topology nodes
� Switching between different views
� Backing up and printing the topology graph
� Moving topology graph
� Changing the displaying structure of topology graph
� Displaying full-screen view
� Setting the network layout
� Operations on groups
� Operations on links
� Operations on NEs
� Expanding and collapsing the topology graph
� Customizing elements on Graphic User Interface (GUI)
� Viewing the rack diagram
� Monitoring Function
The topology view provides a dynamic network topology graph,
displaying the operation status of managed networks in real
time. It monitors configuration changes and fault alarms.

The topology graph also displays records of adding and deleting

NEs and the configuration information of NEs, while informing
users of these changes. By using regular synchronization, you
cannot only view dynamic status of configuration changes in
network devices, but also set the updating cycle of configura-
tion information.
Fault Monitoring: The topology graph can display fault gener-
ated in lower-level network element management systems in
the format of visual and audio alarms.
The system also distinguishes between different alarm sever-
ity levels by using different icon colors of faulty NEs. Acknowl-
edged, unacknowledged, handled and removed faults are also
displayed in different ways.
Introduction to Topology Management View
Topology Topology Management view is shown in Figure 23.
Management View
FIGURE 23 TOPOLOGY MANAGEMENT VIEW
1. NE tree
2. Topology Graph Toolbar
3. Topology Graph
4. Pane of Filter, legend and display
overview
5. Alarm and performance pane
6. Prompt message area

Note:
Select an NE on the NE Tree or in the topology graph to display
the alarms of this NE on the Active Alarms tab of the alarm and
performance pane. Right-click an alarm to handle it. Double-click
an alarm to open a dialog box that displays detailed information
of the NE alarms. See .
Topology Menu The commands on the Topology menu are shown in Figure 24.
FIGURE 24 TOPOLOGY MENU
Topology Graph � The NE tree lists all nodes in the network, while the topology
and NE Tree graph shows all nodes on the current layer.
� The topology graph shows the network structure of devices
managed by the system. The graph reflects filiations between
devices in a hierarchical way and displays connection relations
between devices with lines.
� The system keeps the synchronization between the NE tree
and the topology map. Moreover, the NE tree provides the
navigation function for the topology graph.
Topology Graph On the top of the topology map is the topology toolbar, see Figure
Toolbar 25. You can use the buttons on the toolbar to perform basic oper-
ations on the topology graph.
FIGURE 25 TOPOLOGY GRAPH TOOLBAR
The functions on the toolbar are described in Table 13.
TABLE 13 DESCRIPTION OF TOPOLOGY TOOLBAR BUTTONS
Button Function
Select: By clicking this button and then clicking an

NE or link on the topology map, and the NE or link
node is selected.
Pan: Used to move the area displayed on the

topology graph.

Button Function
Zoom in: used to zoom in the map.
Zoom out: used to zoom out the map.
Cancel: used to cancel the last zooming action.
Zoom Reset: used to display the map in accordance

with the default scale of the system.
Fit to Content: used to show the entire graph in the

current window area of the topology view.
Regional Zoom: If you select a region and click this

button, only the selected area in the current window
is displayed.
Lock Position: After being locked, the NE cannot be

moved.
Save Position: save the position information on the

topology graph.
Search: used to search nodes by name, type,

description or location.
Network Layout: select different layout policies to

show the objects on the topology graph in different
ways.
Full Screen: display the NE tree, Filter, Legend, and

Display areas on the full screen.
Go to: locate a certain node on the graph.
Back to: displays the map layer of the previous

operation. This button changes in accordance with
map layer change.
Forward to: displays the map layer of the previous

operation. This button changes in accordance with
map layer change.
Export: export the information of all nodes on the

current layer to a local file.
Table: show the information of all nodes on the

current layer in a list.
Display topology: show the information of all nodes

on the current map layer on the topology graph.
Hide Filter and Legend Area: used to hide the pane

of filter, legend, and display overview.
Display Filter and Legend Area: used to display the

pane of filter, legend, and display overview.

Pane of "Filter", On the right of the topology map is the pane of "Filter", "Legend",
"Legend", and "Display" overview.
and "Display"
overview � You can set filtering conditions in the filter to only show the
contents meeting the conditions on the view.
� The legend explains the icons of all NE types, alarm colors and
status icons.
� In the display overview, you can set whether to show node
name, link name and the message window on the topology
management view and determine the contents displayed in the
message window.
Note:
If the pane of Filter, Legend and Display Overview is not displayed
on the Topology Management view, click the button to show
the pane on the right.
Alarm and The alarm and performance pane lists the alarm and performance
Performance Pane messages of the selected NE.
NE Icons NE icons refer to the icon of devices on the topology graph, see
Figure 26.
FIGURE 26 NE ICONS
The icon color indicates the following information:

� Blue: NE does not raise any alarm.
� Other colors: the highest-level alarm existing on the NE.
Alarm colors represent alarm severity levels. For details, see
Figure 27.
FIGURE 27 ALARM COLOR ILLUSTRATION
Point the cursor to an NE icon and a message box appears to show

the statistic information of related alarms.

Custom User Interface

Customizing Icons by NE Type
Abstract You can customize images corresponding to different NE types on
the topology map and the NE Tree.
Prerequisites The new image file meets system requirements and is stored on
the Client.
Steps 1. On the menu bar, select Topology > Customize GUI Ele-
ments. The Customize GUI Elements dialog box is dis-
played.
2. Click the Customize Type Image tab to display the Cus-
tomize Type Image page.
3. Click the button after icon to be replaced, and the Open

4. Select a file in the Open dialog box.
Note:
The icon image file must meet the following requirements:
� The selected image file must not exceed 50K.
� The icon of an NE tree node must not be more than 25*25
pixels.
� The icon of a topology node must not be more than 50*50
pixels.
5. Click Open to return to the Customize Type Image page.

6. Click the OK button.
END OF STEPS
Customizing Link Appearance

Abstract This section describes how to set link linearity and width.
Context You can customize the linearity and line width displayed on the
topology map for links. To do this, perform the following steps:
played.
2. Click the Customize Link Appearance tab. The Customize
Link Appearance page is displayed.
3. Click the link attribute box to be modified to display the drop-
down box.
4. Select the linearity and width you need from the drop-down
menu.
5. Click OK.
END OF STEPS
Customizing Status Icons

Abstract You can customize the icon of each status.

Prerequisites The new image file meets system requirements and is stored on
the local computer.
Context
played.
2. Click the Customize Status Image tab to display the Cus-
tomize Status Image page.
3. Click the button after the image to be replaced to open the

Open dialog box.
4. Select a file from the Open dialog box.
Note:
The icon image file must meet the following requirements: The
selected image file must not exceed 50K. The icon of an NE
tree node must not be more than 25*25 pixels. The icon of a
topology node must not be more than 50*50 pixels.
5. Click the Open button to return to the Customize Status Im-

age page.
END OF STEPS
Customizing Status Colors

Abstract You can customize colors corresponding to each status.
Context Reference:
� RGB (Red, Green, Blue).
� HSB (Hue, Saturation, Brightness)
played.
2. Click Customize Status Color option to display status color
settings on the right pane.
3. Click the button in the Status Color field. The Chooser

Status Color dialog box is displayed.
Note:
The Swatches tab is displayed by default.
4. Blocks of different colors are displayed in the middle. Select

the color as required, and click Preview button to see the
effect. The last chosen color is displayed in the first box under
the Recent section.

Note:
The HSB and the RGB of the selected color can be adjusted
on the other two tabs. HSB and RGB settings are interrelated.
Adjusting one of them will change the other.
5. Click the HSB tab.

To set HSB, perform one of the following operations:
� Click the option button before H, S, and B, and drag the
color slider.
� Enter a value.
� Click the spin box to set a value.
Note:
The parameters set here affect those on the RGB tab.
6. Click the RGB tab.

To set RGB, perform one of the following operations:
� Drag the slider after each color.
� Enter a value.
� Click the spin box to set a value.
7. Click the OK button to finish setting and close the Customize
GUI Elements dialog box. The color is changed by now.
8. Click OK.
END OF STEPS
Customizing Status Order

Abstract You can select the status icons to be displayed on the user interface
and the order in which they are displayed. The higher-order icons
are displayed to the left. Three icons can be displayed on the
topology graph, while one icon can be displayed on the NE tree.
To replace the status icons, refer to “Customizing Status Icons” in
this chapter.
played.
2. Click the Customize Status Order option to display the Cus-
tomize Status Order page on the right pane.
3. In the Displayed Status Icon box, select icons that are not
displayed.
4. Click to move the icon to the Undisplayed Status Icon

list.

Button Function
Add all icons to Displayed Status Icon list.
Add selected icons to Displayed Status Icon list.
Move all icons to Undisplayed Status Icon list.
Move selected icons to Undisplayed Status Icon list.
Move selection to the icon above the selected one.
Move selection to the icon below the selected one.
5. Click OK.
Note:
Click the Default button to restore default settings.
END OF STEPS
Customizing Tooltips
Abstract On the topology graph, a tip is displayed when you point to a node.
You can customize node tips, or hint messages, in the topology
view. The node tip includes: the node name, status, alarms, de-
scription, product mode, and performance information.
played.
2. Click Customize Tooltip option to display node tip settings on
the right pane.
3. Select an NE type in the Type list box.
4. On the Basic information tab and Pm tab, select the tip mes-
sage to be displayed.
5. Click the OK button to finish setting.
END OF STEPS
Customizing Alarm Prompting Type

Abstract You can customize the alarm prompting type of the nodes on the
topology graph. The prompting type includes:
� Show Alarm Bubble
� Show alarm border
� Alarm flashing

Context
played.
2. Click Customize Alarm option to display alarm prompting set-
tings on the right pane.
3. Select the check box before each prompting type according to
the description and your needs.
4. Click OK to finish setting.
END OF STEPS
Customizing Other Elements

Abstract You can customize other elements displayed in the Topology
Management view.
played.
2. Click Other option to display settings of other elements on the
right pane.
� Select Show Status Icon check box under Tree Config-
ure group box to show status icon.
� Under the Topology Configure group box:
� Select Parent Node of Layer is visible to show parent
node.
� Select Show coordinate of cursor on Status Bar
show coordinate of cursor.
� Select Show Longitude and Latitude Line to show
the longitude and latitude lines.
� Set the Longitude and Latitude Line Color.
� Set the Label Color.
� Set Background Color.
� Set Label Font Size.
� Set Min Combine Line Number.
Note:
Min Combine Line Number: When the number of links be-
tween two NEs is equal to or greater than the value, all the
link lines can be collapsed to display only one line, which can
be expanded again into multiple lines.
3. Click Set to save the settings.

END OF STEPS
Functions on Topology Menu

This chapter provides instructions on topology management oper-

ations by using the commands on the Topology menu.
Opening the Topology Management View
Context Log in to the client, and the system opens the Topology view
by default. If you open another view later, perform the following
steps to switch to Topology view again.
Steps 1. Perform one of the following optional operations to open the
Topology view.
� On the menu bar, select Topology > View Topology.
� Click the button on the toolbar.

� Select Topology Management in the drop-down menu on
top right.
END OF STEPS
Refreshing Topology Data

Context When more than one user is operating on the topology graph at
the same time, refreshing is necessary. If one user modifies the
topology graph on his or her client and has uploaded modification
to the server, you can refresh the topology to get latest data from
the server.
Steps 1. On the menu bar, select Topology > Refresh Data to refresh
topology data.
END OF STEPS
Result In the message area, double-click . The Show Message dialog

box is displayed, which shows refreshed results, see Figure 28.
FIGURE 28 SHOW MESSAGE DIALOG BOX
Exporting GUI Display Style


Context You can export the GUI display style to a ZIP file. The exported file
includes all the configuration data in Customize GUI Elements
dialog box and your selections of legend display, overview map,
NE location and lock status, and the map configuration. To export
GUI display style, perform the following steps:
Steps 1. On the menu bar, select Topology > Export GUI Display
Style. The Save dialog box is displayed.
2. Set file path and name in Save in box and File name text box
respectively.
3. Click the Save button to export all display settings to a ZIP file.
END OF STEPS
Importing GUI Display Style

Abstract The user may export the current display style into a ZIP file, which
can later be imported to another client with the same topology data
to realize consistency in display style between clients.
Steps 1. On the menu bar, select Topology > Import GUI Display
Style. The Open dialog box is displayed.
2. Select a zip file from the Look in box.
3. Click the Open button to import the file, and the display style
of the current client changes accordingly.
END OF STEPS
Configuring Alarm Display Method

Showing and Setting the NE Monitoring Table
Abstract You can view the monitoring information and acknowledgment sta-
tus of NEs in the monitoring table at the bottom of Topology Man-
agement view. You can also set the monitoring mode in the table.
Steps 1. On the main menu, select Topology > Show NE Monitoring
Alarm Table to show the monitoring table at the bottom of
the client.
Note:
Select an NE in the topology graph or on the NE Tree, and the
alarm information of the NE is displayed on the Active Alarms.
2. Select filter conditions from the Perceived Severity and ACK

state drop-down menu to set the monitoring information you
want to see.
3. You can use the buttons on the monitoring pane to handle
the monitoring information.Table 14 shows specific functions
of buttons.

TABLE 14 TOOLBAR ON MONITORING PANE
Func- Bu- Operation

tion tton
Ex- 1. Click the button to open the Save dialog box.

porting
moni- 2. Set file path, name, and type.
toring
infor-
3. Click the Save button, and a message box is
mation displayed prompting success.
Print- 1. Click the button to open the Print Setup dialog

ing box.
moni-
toring 2. Set printing parameters.
infor-
mation 3. Click the Print button.
At most 5000 records can be printed at a time.
Pin Used to stop refreshing the NE monitoring table.

table The current page will remain unchanged.
Cus- 1. Click to open the Customize Display Col-

tomize umns dialog box.
display
col- 2. select the check boxes corresponding to the
umns columns you want to show on the table.
3. Click right or left arrow to add or remove the
columns, and click up or down arrow to adjust
the sequence of columns displayed on the ta-
ble.
4. Double-click an item in the “Undisplayed Col-
umn” to display the column. Double-click an
item in the “Displayed Column” to move that
filed to “Undisplayed Column” list.
5. Click OK button to finish setting.
4. To view the details of an alarm in the NE monitoring table,

double-click corresponding row to open the Details dialog box.
5. In the detailed monitoring dialog box, click the Handling Mea-
sure tab to view or edit the handling measures.
6. Click the Close button to close the dialog box.
Note:
If you have edited the handling measures, click the Save but-
ton before closing the dialog box.
7. In the dialog box showing the details of an alarm, you can

perform the operations by performing the following operations.

TABLE 15 VIEW DETAILS OF ALARM INFORMATION
Function Operation
View previous Click this button to show the details of the

message previous alarm message in the dialog box.
View next Click this button to show the details of the next
message alarm message in the dialog box.
Acknowledge an Click this button to acknowledge the current

alarm alarm.
Cancel Cancel acknowledgement of an

acknowledgment acknowledged alarm, whose status
turns to “Unacknowledged” accordingly.
Add comments 1. Click to open the Comment dialog box.

2. Type the comments or description in the
text box, and click the OK button.
Clear contents To clear the contents of this monitoring record,

click the button and click OK button in the
pop-up Confirm dialog box.
Forward message 1. Click the button to open the Forwarding

to related Setup dialog box.
personnel via
SMS or E-mail 2. Select the forwarding mode: E-mail or/and
SMS.
Export the 1. Click to open the Save dialog box.

current message
2. Set file name, path, and type.
3. Click the Save button. You will be promp-
ted of successful export.
END OF STEPS
Showing Primary Monitor Alarm Table

Abstract You can query primary monitor alarms based on their severity in
accordance with query conditions that are preset.
Steps 1. On the main menu, select Topology > Show Primary Moni-
tor Alarm Table to display the Primary Monitor Alarm page
at the bottom of the client.
2. Set query conditions to query the monitor information of pri-
mary alarms.
i. On the Primary Monitor Alarm tab, click . The Set

Monitor Condition dialog box is displayed.
ii. Select an NE from the Location tab in the Set Monitor
Condition dialog box.
You can select NEs by performing one of the following op-
erations:

– NE type: Select an NE type from the NE type list. If this

is not configured, all NE types are queried by default.
– NE tree: Expand the NE tree, and select the NE you
want to query.
iii. Click the Alarm code tab and select an alarm code.
iv. Click to move selected alarm code(s) to the selected box

on the right.
v. Click the Time tab to set alarm generating time.
vi. Click the Others tab to set other parameters.
– Alarm type: Select the check box to select the alarm
types to be queried.
– Data type: Select the check box to select the data
types to be queried.
– Perceived severity: Select the check box to select the
perceived severity to be queried.
– ACK state: Select the check box to select alarms to be
queried in corresponding acknowledgement status.
– NE IP: If you want to query the alarm of a specified
NE, enter the NE IP.
– Click the Advanced button to display the Advanced
dialog box, and set advanced parameters.
– (Un)ACK user ID: Exact Match: set the exact
matched user ID. (the user who acknowledges or
unacknowledges the alarm)
– Remark: Fuzzy Match: set additional character
string to find alarms by fuzzy matching.
– Comment: Fuzzy Match: set fuzzy matching
through additional character string.
– Visible: Select the check box to query visible
alarms.
– Invisible: Select the check box to query invisible
alarms.
Note:
The alarm levels and confirm status can also be set by
selecting options from the Perceived severity and ACK
state drop-down menus.
vii. Click OK.

END OF STEPS
Result The queried result is displayed in the Primary Monitor Alarm

window at the bottom of the Topology Management view.
Common Topology Management Operations
This chapter describes common topology management operations
that you can perform by using the commands from the shortcut

menu of a node on either the NE tree or the topology graph of the

Topology Management view.
Setting Node Rules
Abstract Set rules for a node (except actual microwave NE nodes) in the
topology graph or on the NE tree, including location, device type,
and IP address. The topological objects created afterwards will be
set under node that can best match its rules.
Prerequisites You have the right to perform this operation.
Steps 1. In the Topology Management view, right-click an NE, and
select Topology Management > Set Rule from the shortcut
menu. The Set Rules dialog box is displayed.
Select a rule from the following list: IP Address Rule, Device
Type Rule, and Location Rule.
2. Select rules form the Rule Type drop-down list.
3. Configure the rules.
Rule Type Operation Method
IP Address Enter the IP address in the text box. Use “;” to

Rule separate multiple IP addresses. The following three
formats of strings can be used:
� A singe IP address, for example, 1.2.3.4
� An IP address range from a smaller address to
a larger one connected with “-“, for example,
10.10.1.5–10.10.2.6
� IP address with “*” used at head or end to
substitute for multiple characters
Not Equals: Does not match the IP address
Location Enter the location in the text box. Use “;” to

Rule separate multiple locations.
� “*” can replace any characters, while “?” only
replace one character.
� “\*” represents for the character “*, while “\?”
represents for the character “?”.
Not Equals: Does not match the input location.
Ignore Case: No case-sensitive
Device Type � Select the known device type: Select the device
Rule
type, and then click
� Enter the device type manually
� “*” can replace any characters, while “?”
only replace one character.
� “\*” represents for the character “*, while
“\?” represents for the character “?”.
Not Equals: Does not match the input location.
Ignore Case: No case-sensitive
4. Click Save.

Note:
The objects created before the rule is enabled are not affected
by the rule.
END OF STEPS
Setting Members of a Node

Steps 1. In the Topology Management view, right-click a node, and
select Topology Management > Set Member from the
shortcut menu. The Set Member dialog box is displayed.
2. In the Set Member dialog box, click the Add button. The
Select Node dialog box is displayed.
3. Select the member node.
4. Click the OK button to return to the Select Member dialog
box. The node you select in the Select Node dialog box will
become a member of the node you select in step 1.
Note:
In the Set Member dialog box, click the Delete button to
remove that member.

END OF STEPS
Moving a Node
Abstract You can move a node to another place (except actual microwave
NE nodes) on the NE Tree.
select Topology Management > Move Node from the short-
cut menu. The Move Group and NE dialog box is displayed.
2. Select a new parent node on the NE tree.
3. Click the OK button. The node is moved to the specified place
on the NE Tree.
END OF STEPS
Showing Statistics of a Node

Abstract You can view the statistics of a node on the NE tree, including the
number of its child NEs, and that of related groups and links.
Context
select Topology Management > Show Statistical Infor-

mation from the shortcut menu. The Statistical Informa-

tion dialog box is displayed, see Figure 29.
FIGURE 29 STATISTICAL INFORMATION DIALOG BOX
END OF STEPS
Switching to Fault Management View

Abstract You can select an NE and switch to the Fault Management view to
handle the fault alarms of that NE. To do this, perform the following
steps:
point to Fault Management from the shortcut menu to open
a submenu.
END OF STEPS
Switching to Performance Management View

Abstract You can select an NE and switch to the Performance Manage-
ment view to manage performance data of that NE. To do this,
perform the following steps:


point to Performance Management from the shortcut menu
to open a submenu.
END OF STEPS
Viewing the Alarm Count of a Node

Context You can quickly view the number of current alarms and total alarms
of an NE on the topology graph. To view alarm details, see Unified
Network Management System Performance Management Opera-
tion Guide.
Steps 1. On the NE tree or topology graph, suspend the mouse on the
NE for seconds, and the alarm information will appear auto-
matically.
END OF STEPS
Operations on NE Tree
Introduction to NE Tree
The NE Tree is to the left of the topology graph, see Figure 30.
FIGURE 30 NE TREE
The NE tree has a hierarchical structure based on parent-child re-

lationship, with the server as the root node. The node has the
following types: sub-networks, managed NEs, and groups.
The function unique to the NE tree is to find a node on the tree. You
can also perform many other operations on the NE nodes, similar
to those on the topology graph.
Searching a Node on the NE Tree
Abstract This section describes how to quickly find a node on the NE tree.
Prerequisites Before you begin, make sure that
� You have logged in to the client.
� You have the authority to perform this operation.
� You have some information of the node you want to find, such
as a keyword of its name or IP address.
Steps 1. Type the keyword, such as the name, in the text box Enter
query content.

FIGURE 31 TYPING A KEYWORD
2. Click button to execute the filter.

END OF STEPS
Operations on Topology Graph

This chapter describes how to perform operations unique to topol-
ogy graph.
Topology Layer Operations
The topology graph is divided into layers. Select a node on the NE
tree, and the topology graph shows all nodes on the current layer
under the same node, see Figure 32.
FIGURE 32 CURRENT LAYER
Operations on the topology layer are described in the next few

topics.
Going to the Upper Layer
Abstract This section describes how to see the topology graph of the upper
layer.


� The current layer is under a parent-node layer.
Steps 1. On the topology graph, right-click the blank, and select To
Upper Layer from the shortcut menu.
END OF STEPS
Expanding and Collapsing a Node

Abstract On the current layer, you can expand a node to show its child nodes
at the same time and collapse it to hide the child nodes. Collapsing
is the opposite operation of expanding.
� The current node has at least one child node.
Steps 1. Expand a node: Right-click a node to be expanded on topology
graph, and select Topology Management > Show Node's
Sublayer from the shortcut menu.
2. Collapse a node: Right-click a node to be collapsed on topology
graph, and select Topology Management > Hide Node's
Sublayer from the shortcut menu.
END OF STEPS
Expanding and Collapsing All Nodes on the Current Layer

Abstract This procedure describes how to expand and collapse all nodes on
the current layer.
� The current layer has parent nodes.
Context On the current map layer, you can expand all parent nodes and
collapse all expanded nodes.
� Expanding all nodes: to expand all parent nodes on the current
layer and display all their child nodes in one layer.
� Collapsing all nodes: to collapse all the expanded nodes.
Steps 1. Expanding all nodes: Right-click the blank of the topology
graph, and select Show Sublayer from the shortcut menu.
All sub-layers are then shown on the current layer.
2. Collapsing all nodes: Right-click the blank of the topology
graph, and select Hide Sublayer from the shortcut menu.
All expanded sub-nodes are then hided, with all their parent
nodes being displayed.
END OF STEPS
Going to Lower Layer



� The current node has sub-nodes.
Context To see the lower layer of the topology graph, perform the following
steps:
Steps 1. Right-click a parent node on the topology graph, and select
Topology Management > To Lower Layer from the shortcut
menu.
END OF STEPS
Functions of Toolbar buttons

On the top of the topology graph is the topology toolbar, as shown
in Figure 33. You can use the buttons on the toolbar to perform
basic operations on the topology graph.
FIGURE 33 TOPOLOGY GRAPH TOOLBAR
For the description about buttons, refer to . The common functions

that use buttons are described below.
Moving the Topology Graph
Abstract You can move the topology graph about in the current view to
display the information out of the current view.
Context
Steps 1. Click button on the toolbar.

2. Drag the cursor in the graph pane to move the topology graph.
END OF STEPS
Locking and Unlocking the Topology Graph

Abstract NEs can be moved on the topology graph if the topology graph is
not locked. After lockup, NEs cannot be moved.
Context The locking and unlocking operation is applicable only to the cur-
rent user.
Steps 1. Locking the topology graph: Click to lock NEs on the topol-
ogy graph.

2. Unlocking the topology graph: Click to unlock NEs on the

topology graph.
END OF STEPS
Setting Network Layout

Abstract You can select the network layout type of NEs on the topology
graph. To do this, perform the following steps:
Steps 1. Click button on the toolbar. The Network Layout dialog

box is displayed.
2. Select a layout type from the Layout Strategy list box.
Note:
Refer to the layout example in the Sample box when you select
a layout type.
The layout type options include:

� Hierarchical Layout
� Tree Layout
� Radial Tree Layout
� Spring Embedded Layout
� Uniform Length Edges Layout
3. Click OK button.
END OF STEPS
Switching to the Graph of Another Node

Abstract You can switch the graph to another node you have viewed. Note
that only the node(s) you have viewed during this login can be
switched to.
Steps 1. Click the button. The list of nodes you have viewed is
displayed.
2. Choose a node you want view on the list.

END OF STEPS

Searching a Topology Node

Abstract You can search the node by name, type, position, IP address, or
description.
Prerequisites You have some information of the node, such as the name, type,
coordinate range, or IP address.
Steps 1. Click the button on the toolbar. The Search dialog box is
displayed.
2. Select an optional button after Find Type.
� and: To search the node(s) that meet(s) all conditions you
select.
� or: To search the node(s) that meet(s) one of the condi-
tions you select.
3. Select the conditions from the check boxes after Search Con-
ditions.
4. Configure the condition value in the corresponding condition
tabs.
5. Select the Case Sensitive check box.
6. Click the Search button.
END OF STEPS
Result � A table is displayed below the topology graph to show the

search result.
� If no matching nodes are found, the Confirm is displayed, in-
forming you about that result.
Displaying the Topology Map on Full Screen
Context You can display the topology graph on full screen. If the topology
graph is displayed not on full screen, you have to drag the graph
to view the part not displayed. Full-screen view displays all infor-
mation, thus making it unnecessary to move the graph.
Steps 1. Click button on the toolbar.
Note:
Click the button to exit full-screen display.
END OF STEPS
Exporting the Topology Graph

Abstract You can export the topology graph to a local file.

Steps 1. Click button on the toolbar. The Save dialog box is dis-
played.
2. Select a file path in Save in box.
3. Set the file name and type.
� File name: Type the file name. It is better to use the name
of a group or an NE.
� Files of type: the options include jpg and png.
4. Click the Save button. The Confirm dialog box is displayed.
The exported graph is saved with the name and type specified
under the designated path.
END OF STEPS
Showing the Topology Information in Table

Context You can list the NEs on the topology graph in a table. To do this,
perform the following steps:
Steps 1. Click the button, and the topology information is listed in a

table.
2. Click button to return to the topology graph.

END OF STEPS
Printing Topology Information

Abstract You can only print the NE list when they are displayed in table,
instead of being presented in topology graph.
� The printer is operating normally and is properly connected to
the client.
Steps 1. On the topology toolbar, click the button, and the Print
Setup dialog box is displayed.
2. On the General tab, set Printer, Print Range and Copies.
3. Click the Page Setup tab to set Paper Size, Orientation,
and Margins.
4. Click the Advanced tab to set advanced parameters.
5. Click the Preview All button to open the Print Preview dialog
box, in which you can preview printing result.
6. Click the button in the Print Preview dialog box to carry

out printing operation.

The Confirm dialog box is displayed, prompting you of printing

success.
7. Click OK button to close the dialog box.
END OF STEPS
Customizing Displaying Content on Topology Graph

Abstract You can select the contents you want to display on the topology
graph. For example, the notification message is displayed only
when you select the Enable Message Notification check box.
Steps 1. Click the button on the toolbar.

� If the topology information is listed in table, the Customize
Display Columns dialog box is displayed..
� If the topology information is displayed on topology graph,
the Display dialog box is displayed.
2. Select the contents you want to display.
3. Click the OK button. The content displayed in the topology
graph is updated in accordance with the configuration.
END OF STEPS
Displaying or Hiding the Pane of Filter, Legend, and Display

Overview
Abstract This topic introduces how to hide or show the pane of Filter, Leg-
end, and Display Overview, on the right of the Topology Man-
agement View.
Context
Steps 1. Click on the toolbar. The Legend tab is displayed in the

right pane.
Tip:
Click Filter below the Legend page. The Filter dialog box is
displayed.
Click Config Displaying Content below the Legend page,
and then you can set displaying content in the Topology Man-
agement view.
END OF STEPS

Result If the pane is displayed, the button turns to button. Click

the latter button to hide the pane of filter, legend, and display
overview.
Display Filter Settings
Setting Topology Nodes on Filter Tree
Abstract This topic describes the procedure to set filtering conditions on the
topological filter tree to get the desired topology view.
� The pane of legend, filter, and display overview is open.
Steps 1. On the right pane of the Topology Management view, click
the filter tab. The Filter dialog box is displayed.
The Filter dialog box has two sub-pages, of which the Filter
Tree is displayed by default.
Note:
If the pane of Filter, Legend and Display Overview is not dis-
played on the Topology Management view, click the but-
ton to show the pane on the right.
2. Expand the resource tree to view detailed nodes.

3. Select the check box before the nodes you want to display. The
checked nodes are displayed on the topology graph.

4. Click OK. The selected NEs are displayed on the topology

graph.
END OF STEPS
Setting Topology Nodes by Using Condition Filter

Abstract If the topology graph is complex or that the user only needs nec-
essary information, using the condition filter can remove some
information. Set filtering conditions on the Condition Filter page
to get required topological view.
� The pane of legend, filter, and display overview is open.
Context
Steps 1. On the right pane of the Topology Management view, click
the Filter tab. The Filter dialog box is displayed.

Note:
If the pane of Filter, Legend and Display Overview is not dis-
played on the Topology Management view, click the but-
ton to show the pane on the right.
2. Select the Condition Filter optional button on the Filter dialog

box.
3. Select the Filter type.
� or: The NEs or Groups meeting one of the conditions will
be displayed after filtering.
� and: Only the NEs or Groups meeting both conditions will
be displayed after filtering.
4. Type the filter condition in the NE(Group) name and IP ad-
dress text boxes.
5. Type the link name in the Link Name text box.
Note:
You can also use the following wild cards: "?" represents one
character, while "*" represents two characters.
Use ";" to separate more than one IP addresses. You can enter
three types of IP address:
1. A single IP address, for example, 1.2.3.4.
2. An IP address range from a smaller address to a larger
one connected with “-“, for example, 10.197.0.0-
10.197.255.255.
3. IP address with “*” used at head or end to substitute
for multiple characters, for example, *.10.10.10 and
10.197.10.*.
6. Click the OK button to display the nodes that meet the filter
conditions on the topology graph.
END OF STEPS
Configuring a Map
Abstract You can import a map to the current topology graph to manage
NEs on the map.
Context � The system provides a default map as the background of the
topology graph.
� The imported map file should be less than 1MB, and in the
format of gif or jpg.

Steps 1. Right-click the blank of the topology graph, and select Config-
ure Map from the shortcut menu. The Configure Map dialog
box is displayed.
2. Click the Import button under the File Setting group box to
select a map file.
To... Do...
Importing a specific map 1. Click Import button.

2. Select a map file in the pop-up dia-
log box.
3. Click Open.
Import a default map Click Default.
3. Set the longitude and latitude ranges under the Map Range
group box.
Note:
You can only set the longitude and latitude ranges for imported
map.
Parameter Description Value Range Default Value
Start Starting [-180, 180] -180

Longitude longitude of
the map range.
End Ending [-180, 180] 180

Longitude longitude of
the map range.
Start Starting [-90, 90] 90

Latitude latitude of the
map range.
End Latitude Ending latitude [-90, 90] -90

of the map
range.
Tip:
Suspend the cursor on the longitude or latitude setting box, the
range will be displayed, such as latitude W:[-180, 0], E:[180,
0].
4. Click Set to save the settings. The imported map will be dis-
played as the background of the topology graph.
END OF STEPS
Group Management Operations

Overview of Groups
The system supports the grouping of managed NEs for easier man-
agement. The NEs can be grouped by type or by location.
Creating a Common Group
Abstract In the topology view, NEs can be divided into logical groups. This
grouping process does not depend on the actual physical connec-
tions between the NEs.
Prerequisites You have the user permissions of "Maintenance Role" or above.
Steps 1. Right-click a blank area in the Topology Management view,
and select Create Object > Common Group. The Create
Common Group dialog box is displayed, see Figure 34.
FIGURE 34 CREATE COMMON GROUP DIALOG BOX

2. To set the attributes of the common group, refer to the follow-

ing table.
Attrib- Description
ute
Parent Click Select and select a node (other group or NE)

Node where you want to create a group.
Name Enter the group ID. Common groups under one parent
node cannot have the same name.
Descrip- Enter the supplementary information.

tion
Rule Type No rule No rule is required.
IP Enter the IP address manually.

address If Not Equals is selected, the entered IP
rule rule is excluded.
Location Enter the location manually.

rule � If Not Equals is selected, the entered
location is excluded.
� If Ignore Case is selected, the entered
location is case-insensative.
Device Select Select Device Type or Input

type rule Device Type.
� If Not Equals is selected, the entered
device type is excluded.
� If Ignore Case is selected, the entered
device type is case-insensative.
Note:
If the Successively Create check box is selected, after a com-
mon group is created, the Create Common Group dialog box
is displayed automatically to create another common group.
3. Click OK.
END OF STEPS
Result In the left NE Tree in the Topology Management view, the new
group is displayed under the selected parent node.
Creating a Type Group
Abstract In the topology view window, NEs can be divided into logical
groups. This grouping process does not depend on the actual
physical connections between the NEs. This topic describes the
procedure for creating type groups.
Context The type groups cannot have the same name under the same par-
ent node.

Creation of type groups is based on equipment type. You can ei-

ther create a single group, or create multiple groups in batches.
and select Create Object > Type Group from the menu. The
Create Type Group dialog box is displayed, see Figure 35.
FIGURE 35 CREATE TYPE GROUP DIALOG BOX
2. Click the Select... button. The Select Node dialog box is

displayed.
3. Select the parent node of the new group, and then click OK.

Note:
The parent node here can be other groups or NEs.
4. (Optional) Create a batch of groups.

i. Click the Create a batch of groups tab.
ii. Select all the device types.
iii. Click OK to create the groups in batches.
Groups of all selected equipment types are created and all
groups are located under the selected parent node.
5. (Optional) Create a single group.
i. Click the Create a single group tab.
ii. Enter the Group Name and Group Description.
iii. Select the Rule Type. The writing specifications vary with
rule types. Enter the rule based on the message.
Note:
The rules for the type groups contain the following: No
Rule/IP Address Rule/Location Rule/Device Type Rule. All
writing specifications are given in the bottom of the dialog
box.
iv. Click OK.

The new single group is displayed under the selected parent
node
END OF STEPS
Creating a Location Group

Abstract In the topology view, NEs can be divided into logical groups. This
grouping process does not depend on the actual physical connec-
tions between the NEs. This topic describes the procedure.
and select Create Object > Location Group from the menu.
The Create Location Group dialog box is displayed, see
Figure 36.

FIGURE 36 CREATE LOCATION GROUP DIALOG BOX
2. Click Select.... The Select Node dialog box is displayed.

3. Select the parent node of the new group, and then click OK.
Note:
The parent node here can be other groups or NEs.
4. Enter the Group Name and Group Description.

5. Enter the self-defined rules in Rule Type. The writing spec-
ifications vary with rule types. Enter the rule based on the
message.
Note:
� The location groups contains the following rules types: No
Rule/IP Address Rule/Location Rule/Device Type Rule. All
writing specifications are given in the bottom of the dialog
box.
� Select Successively Create. After the creation, the Cre-
ate Location Group dialog box is automatically displayed
to realize the successively creation.
6. Click OK.
END OF STEPS

Result The new location group is displayed under the selected parent
node.
Setting Members
Abstract You can allocate members for an NE or a group as sub-nodes of
the NE or group.
Steps 1. In the Topology Management view, select an NE or a group
in the object tree in the left pane.
2. Right-click Topology Management > Set Member from the
pop-up menu. The Set Member dialog box is displayed.
3. (Optional) Add a member.
Note:
Only an NE but not a group can be added as a member.
i. Select a NE from the Available Items area, and click .

ii. Click OK.
The added member is displayed in the group.
4. (Optional) Delete a member.
i. Select an NE in the Selected Items area, and click .

ii. Click OK.

The member is not listed in the group.

END OF STEPS
Deleting a Group
Abstract You can delete groups as required.
� You have logged in to client.
� You have the right to perform this operation.
� The group is created.
Steps 1. On the NE tree or the topology graph, right-click a group, and
select Topology Management > Delete Type Group from
the shortcut menu. The Confirm dialog box is displayed.
Note:
The right-click menus vary with the types of objects.
2. Click the OK button to delete the selected group.

END OF STEPS
Result Delete the specific group successfully.

Viewing Attributes of a Group
Abstract This section describes how to view the topology information of a
group.
� You have the right to perform this operation.
� The group is created.
Steps 1. On the NE tree or the topology graph, right-click a group,
and select Topology Management > View Type Group At-
tributes to open the View Group dialog box.
Note:
The right-click menus vary with the types of objects.
To view the group attributes, you can also display the topol-
ogy information in table. For this operation, see “Showing the
Topology Information in Table” in the chapter “Operations on
Topology Graph”.
END OF STEPS

Glossary
3GPP
3rd Generation Partnership Project
BRAS
Broadband Remote Access Server
CORBA
Common Object Request Broker Architecture
CTN
Converged packet Transport Network
DB
DataBase
DDN
Digital Data Network
EMB
Enterprise Message Bus
FTP
File Transfer Protocol
GUI
Graphical User Interface
HDSL
High-data-rate Digital Subscriber Line
IP
Internet Protocol
IP
Intelligent Peripheral
J2EE
JAVA 2 platform Enterprise Edition
JMS
Java Message Service
KPI
Key Performance Indicator
LAN
Local Area Network
MML
Man Machine Language
MODEM
Modulator-Demodulator
NAF
Northbound Adapter Function
NBI
NorthBound Interface
NE
Network Element

NMS
Network Management System
OSS
Operation Support System
OTN
Optical Transport Network
PS
Packet Switched
RMI
Remote Method Invocation
SDH
Synchronous Digital Hierarchy
SFTP
Secure File Transfer Protocol
SMS
Short Message Service
SNMP
Simple Network Management Protocol
SSH
Secure Shell
TCP
Transfer Control Protocol
TMN
Telecommunications Management Network
UDP
User Datagram Protocol
WAN
Wide Area Network
WDM
Wavelength Division Multiplexing
XML
eXtensible Markup Language

Netnumen Training PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Netnumen Training PDF

Enviado por

Direitos autorais:

Formatos disponíveis

NetNumen U31 Introduction

Publishing Date (MONTH/DATE/YEAR) : 2013–01–15

NetNumen U31(V12.12.20P01) Introduction ............... 1

will be able to:

Confidential and Proprietary Information of ZTE CORPORATION 1

Chapter 1 System Overview

1.1 Introduction to the System

1.2 Location of the Product on a

2 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 1 POSITION OF IN THE BEARER NETWORK

– BSS: Business Support System – CTN: Converged Packet Transport

1.3 Typical Application Schemes

Confidential and Proprietary Information of ZTE CORPORATION 3

� Dual-Server Configuration for Hot Backup

FIGURE 2 LOCAL DUAL-SERVER CONFIGURATION HOT BACKUP

For the remote dual-sever hot backup, see Figure 3.

4 Confidential and Proprietary Information of ZTE CORPORATION

FIGURE 3 REMOTE DUAL-SERVER CONFIGURATION HOT BACKUP

1. Remote dual-server heartbeat 3. Network interface between

1.4 System Features

Confidential and Proprietary Information of ZTE CORPORATION 5

by the user are limited to certain network elements with a cer-

1.5 Manageable NEs

6 Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 7

1.6 Computer Ports Occupied by

TABLE 1 COMPUTER PORTS OCCUPIED BY THE SERVER AND CLIENT

N- Sou- Desti- Direc- Pro- Description

1 Ran- 20800- Client TCP File Transfer Protocol (FTP)

2 Ran- 21100 Client TCP Java naming service port

3 Ran- 21101 Client TCP Naming service port for the

4 Ran- 21102 Client TCP Remote Method Invocation

5 Ran- 21103 Client TCP Remote invocation

6 Ran- 21104 Client TCP Java naming service

7 Ran- 21105 Client TCP Enterprise Message Bus

8 Ran- 21106 Client TCP Java naming service

9 Ran- 21109 Client TCP Heartbeat detection port

10 Ran- 21110 Client TCP Java naming service

11 Ran- 21111 Client TCP FTP server control port

8 Confidential and Proprietary Information of ZTE CORPORATION

N- Sou- Desti- Direc- Pro- Description

12 Ran- 21112 Client TCP Remote invocation port for

13 Ran- 21113 Client TCP Java naming service

14 Ran- 21114 Client TCP JMS port for the cluster

15 Ran- 21118 Client TCP Bandwidth detection port

16 Ran- 21128 Client TCP Secure File Transfer

17 Ran- 21133 Client TCP Port used by the upgrading

18 Ran- 21140 Client TCP Secure Shell (SSH)

19 Ran- 21199 Client TCP SSH forwarding port for

20 Ran- 21 Client TCP Port for the FTP service of

21 Ran- 21160 Client TCP ZXTIM400 polling tool port

22 Ran- 21162 Client TCP EMB port

23 Ran- 21163 Client TCP EMB port

24 Ran- 21170 Client TCP EMB port

25 Ran- 21171 Client TCP EMB port

Confidential and Proprietary Information of ZTE CORPORATION 9

N- Sou- Desti- Direc- Pro- Description

26 Ran- 21172 Client TCP EMB port

27 Ran- 21173 Client TCP EMB port

28 Ran- 21174 Client TCP EMB port

29 Ran- 21179 Client TCP EMB port

30 Ran- 21138 Client TCP EMB port of the TOPO

31 Ran- 21188 Client TCP RMI port used by the