UNM2000

UNM2000
Network Convergence
Management System V2R7
Product Description
Version: A
Code: MN000004156
FiberHome Telecommunication Technologies Co., Ltd.
May 2019
Thank you for choosing our products.
We appreciate your business. Your satisfaction is our goal.

We will provide you with comprehensive technical support
and after-sales service. Please contact your local sales
representative, service representative or distributor for any
help needed at the contact information shown below.
Fiberhome Telecommunication Technologies Co., Ltd.
Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

Zip code: 430073
Tel: +6 03 7960 0860/0884 (for Malaysia)
+91 98 9985 5448 (for South Asia)
+593 4 501 4529 (for South America)
Fax: +86 27 8717 8521
Website: http://www.fiberhomegroup.com
Legal Notice
are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.
All rights reserved
No part of this document (including the electronic version) may be

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface
Version
Version Description
Initial version, corresponding to the software version

A
UNM2000 V2R7.
Related Documentation
Document Main Content Phase to Use
UNM2000 Network Convergence Introduces the product positioning,
Network
Management System V2R7 features, basic functions, network and
planning
Product Description application, and technical specification.
UNM2000 Network Convergence Introduces the installation flow and

Network
Management System V2R7 methods of the UNM2000 on the
deployment
Windows Installation Guide Windows standalone operating system.
UNM2000 Network Convergence Introduces the installation flow and

Network
Management System V2R7 methods of the UNM2000 on the SUSE
deployment
SUSELinux Installation Guide Linux standalone operating system.
UNM2000 Network Convergence Introduces the operation methods, main

Network
Management System V2R7 GUIs and precautions of the
maintenance
Operation Guide management functions.
PON Network Traffic and Quality

Introduces the installation flow and Network
Analysis System V2R7
methods of the product. deployment
Installation Guide
PON Network Traffic and Quality Introduces the operation methods, main
Network
Analysis System V2R7 Operation GUIs and indicator introduction of the
maintenance
Guide management functions.
Intended Readers
This manual is intended for the following readers:
u Network planning engineers
u Network deployment engineers
I
Terminology Conventions
Terminology Convention
FiberHome UNM2000 Network Convergence Management
UNM2000
System
Symbol Conventions
Symbol Convention Description
Note Important features or operation guide.
Possible injury to persons or systems, or cause traffic

Caution
interruption or loss.
Warning May cause severe bodily injuries.
➔ Jump Jumps to another step.
Cascading
→ Connects multi-level menu options.
menu
Bidirectional
↔ The service signal is bidirectional.
service
Unidirectional
→ The service signal is unidirectional.
service
II
Operation Safety Rules
The network management computer should be placed away

from direct sunlight, electromagnetic interference, heat source,
humidity and dust, and with at least 8 cm distance from other
objects in order to keep good ventilation.
Use UPS power supply to avoid loss of network management

data caused by accidental power failure.
The computer case, UPS power supply and switch (or hub)
should be connected to protection earth ground.
To shut down the network management computer, exit the

operation system normally and then shut off the power supply.
Do not exit the network management system when it is working

normally. Exiting the network management system does not
interrupt traffic in the network, but precludes centralized control
of the networked equipment.
The network management computer cannot be used for

purposes other than network management. Use of unidentified
memory devices should be prohibited so as to avoid computer
viruses.
Do not delete any file in the network management system

randomly or copy any irrelevant file into the network
management computer.
Do not visit Internet via the network management computer.

Doing so may increase data flow in the net card and hence
affects normal network management data transmission or
results in other accidents.
III
Do not perform service configuration or expansion during service
busy hours via the network management system.
Do not modify the network management computer’s protocol

settings, computer name or LAN settings. Doing so may result in
abnormal operation of network management system.
IV
V
VI
VII
Contents
Preface...................................................................................................................I
Operation Safety Rules .........................................................................................III
1 Overview ........................................................................................................1
1.1 Product Positioning...........................................................................2
1.1.1 Deployment of the UNM2000 in the TMN.............................2

1.1.2 Manageable Device Types..................................................2
1.2 Product Features ..............................................................................3
2 New Features .................................................................................................6
3 System Architecture........................................................................................8
3.1 Software Architecture........................................................................9
3.2 External Interface..............................................................................9
4 System Configuration Requirements ............................................................. 11
4.1 Hardware Configuration Requirements............................................12
4.2 Software Configuration Requirements .............................................14
5 Network and Application ...............................................................................16
5.1 UNM2000 Deployment Mode ..........................................................17
5.1.1 Centralized Deployment Mode ..........................................17

5.1.2 Distributed Deployment Mode ...........................................18
5.1.3 Cluster Disaster Tolerance Centralized Deployment Mode.19
5.1.4 Cluster Disaster Tolerance Distributed Deployment Mode..21
5.2 Network Mode between the UNM2000 and NE................................23
5.3 Network Example ...........................................................................24
6 Basic Function of the UNM2000 ....................................................................25
6.1 Configuration Management .............................................................26
6.2 Topology Management....................................................................30
6.3 Alarm Management ........................................................................34
6.4 Event Management.........................................................................40

6.5 Performance Management..............................................................41
6.6 Security Management .....................................................................44
6.7 Resource Management...................................................................50
6.8 Operation and Maintenance Management .......................................53
7 Technical Specifications................................................................................58
7.1 Management Capacity ....................................................................59
7.2 Performance Specification ..............................................................59
7.3 Standards.......................................................................................61
8 External Service Ports ..................................................................................63
Appendix A Abbreviations ............................................................................73

1 Overview
The UNM2000, developed by FiberHome, is used to manage the network devices

so as to improve the network maintenance efficiency and lower down the
maintenance cost.
Product Positioning
Product Features
Version: A 1
UNM2000 Network Convergence Management System V2R7 Product Description
1.1 Product Positioning
The UNM2000, a system managing the FiberHome communication devices, is the

major network management product of FiberHome in the future. It is used to provide
solutions related to NE management and network management, which lowers down
the customers' maintenance cost and improves the network management value.
1.1.1 Deployment of the UNM2000 in the TMN
The TMN provides hierarchical network architecture and standard network

interfaces. It is composed of the business management layer (BML), the network
management layer (NML), and the element management layer (EML). This type of
composition is called the network management architecture of the TMN.
The UNM2000 is located at the NML and EML in the TMN architecture and
manages the devices in the access network, transport network and IP network, as
shown in Figure 1-1.
Figure 1-1 Deployment of the UNM2000 in the TMN
1.1.2 Manageable Device Types
Table 1-1 lists the devices that can be managed by the UNM2000 V2R7.
2 Version: A
1 Overview
Table 1-1 Manageable Devices
Type Device Model
AN5516-04, AN5516-06, AN5116-02, AN5116-04B, AN5116-06B, AN6000-17 and

OLT
AN6001-G16
u GPON: AN5506-02-D/F, AN5506-04-B2/D/F1/FA/FAT, AN5506-07A/09A/10A
and AN5506-07B/09B/10B.
u XGPON: AN5646T/Q, AN5656T, AN5221-8N/16N/24N and AN5231-8N/16N/
24N.
ONU
u EPON: AN5006-07A/09A/10A and AN5006-07B/09B/10B.
u 10GEPON: AN5200-07A/09A/10A and AN5200-07B/09B/10B.
u HG6243C, HG6245D, HG6021C, HG6543C, HG6145E, HG6245P, HG6244C,
HG6249A, HG5245ST and HG5245SH.
MSAN AN5006-20, AN5006-30, AN5006-15, AN5006-16, AN5220 and AN5516.
1.2 Product Features
The UNM2000 improves the management capability, scalability and usability,

providing a new generation of client-oriented network management system.
Powerful Management Capability
The UNM2000 improves the management capability using the distributed

deployment and flexibly controls the management modules using the License
function.
u The UNM2000 supports the single-server centralized deployment mode, single-

system distributed deployment mode, cluster disaster tolerance centralized
deployment mode and cluster disaster tolerance distributed deployment mode.
u The UNM2000 improves the disaster tolerance by the cluster disaster tolerance
centralized deployment and the cluster disaster tolerance distributed
deployment, so as to provide users with a stable and reliable network
management system.
u The UNM2000 flexibly controls the functions and management capability using
the License function, so as to meet various requirements of subscribers. The
license will not be influenced by any changes of the network card.
Version: A 3
Flexible Scalability
The UNM2000 employs an industry-leading scalable modularized architecture

design to support the distributed and hierarchical database modules, service
configuration processing modules and common modules.
u The functional modules can be separated or combined, which meets users'

customization requirement.
u The loose coupling between functional modules enables users to upgrade and
maintain modules independently.
Better User Experience
The UNM2000 provides a new generation of the client-oriented network

management system.
u The UNM2000 provides completely new user experience through the CLI and
Web login modes.
u The UNM2000 keeps the consistent GUI style for each device using
modularized design.
Compatible with Multiple Operating Systems
As an independent application, the UNM2000 can be installed in different operation

systems based on different databases. The UNM2000 cannot only provide high-end
resolution for the large-scale network, but also provide low-cost resolution for small-
to medium-sized network.
u The UNM2000 can operate on the Windows, SUSE Linux and Solaris systems.
The client end and server end performance of the UNM2000 is irrelevant to the
operating system.
u The UNM2000 supports the MySQL, Oracle and SQLServer databases to meet
different requirements for users.
Standard and Unified Interface
The UNM2000 provides the standard and unified southbound and northbound
interfaces, which completely meet the requirements for the industry mainstream
OSS integration.
4 Version: A
1 Overview
u The functions of the unified southbound and northbound interfaces can cover
all devices in the network managed by the UNM2000.
u The southbound and northbound interfaces use the industry-leading interface

standard, which makes the interface maintenance cost-effective. The interfaces
can be extended and support diversified deployment.
Version: A 5
2 New Features
This chapter introduces the newly developed highlights and features of the
UNM2000 V2R7.
u The UNM2000, PAS and PON traffic tool fully support IPv4 and IPv6 dual-stack
management.
u Optimizes the resource statistics function.
4 Supports collecting networkwide statistics of the ONU weak optical power,

enabling clients to maintain the ONU weak optical power conveniently.
4 Supports automatically synchronizing the data of the newly added OLTs

with the resource statistics export task. This requires fewer manual
operations.
4 Supports collecting statistics of and exporting PON port running status,

OLT online status and ONU port uplink / downlink rate configurations, etc.
This meets users' statistics requirements.
u Supports deleting NEs and automatically upgrading ONUs, improving users'

operation efficiency.
u Supports customizing quick access for ONU service provisioning, managing

hand-in-hand topologies and optimizing the intensive merge tool.
u Enhances the License management and control capability, specifically, the

license supports controlling TL command sets and their usage time.
u Optimizes the PON traffic tool function.
4 Supports second-level traffic and traffic statistics of MSAN devices

(AN5516 MSAN common platform devices and AN5220 devices).
4 Optimizes the report export function; supports exporting data reports and
statistics and analysis graphs simultaneously.
4 Supports collecting statistics of uplink / downlink CRC errors of OLT uplink

ports and PON ports to help analyze the failure reason of the PON
network.
6 Version: A
2 New Features
4 Supports collecting statistics of and analyzing the traffic load of the OLT
uplink ports and PON ports, providing basic data for the planning of the
uplink ports and user resources.
4 Provides bandwidth utilization rankings, traffic analysis reports and link

bandwidth utilization reports for the OLT uplink ports, OLT PON ports and
ONU PON ports. This helps users analyze the traffic.
4 Provides area statistics and analysis function; collects statistics of and

analyzes traffic and physical resources by area.
u Supports the AN6000 V1R2 version.
Version: A 7
3 System Architecture
The following introduces the software architecture and external ports of the
UNM2000.
Software Architecture
External Interface
8 Version: A
3 System Architecture
3.1 Software Architecture
The UNM2000 adopts the client end - server mode. Figure 3-1 shows the software
architecture of the main modules in the system.
Figure 3-1 UNM2000 Software Structure
3.2 External Interface
The external interface is the channel for communication and data interaction
between the UNM2000 and the external system. The UNM2000 provides the
northbound interface and southbound interface to manage devices and help
network operators implement quick integration of the OSS and the UNM2000,
improving customer service quality.
Version: A 9
Northbound Interface
The UNM2000 northbound interface provides the network monitoring information,

such as alarms, inventory and performance, for the OSS system. Meanwhile, it
supports the network management functions, such as service configuration and
notification reporting. The UNM2000 can implement quick integration with OSS
systems through the UNM2000 northbound interface.
The UNM2000 supports the TL1, CORBA, WebService, Socket and SNMP
northbound interfaces.
Southbound Interface
The UNM2000 is connected with the devices through the southbound interface so
that the UNM2000 can manage the devices.
The connection between the UNM2000 and devices uses the SNMP, FTP / SFTP /
TFTP and Telnet / SSH protocols.
10 Version: A
4 System Configuration Requirements
This chapter introduces the hardware and software configuration requirements for
the computer on which the UNM2000 is to be installed.
Hardware Configuration Requirements
Software Configuration Requirements
Version: A 11
4.1 Hardware Configuration Requirements
This section introduces the UNM2000 server end and client end's requirements for
the hardware configuration.
Server End
The hardware configuration requirements of the UNM2000 server vary according to

the network scale. For detailed requirements, see Table 4-1.
Table 4-1 Hardware Configuration Requirements of the Server
Network CPU Clock CPU Hard Disk Hard Disk Network

Memory
Scale Rate Quantity Space Format Card
The format of the
disks on which
the database
5000 NEs and the
(MDU+OLT), 10-core / 2.5 UNM2000 will be
8 256G 4 TB 4*GE ports
1000000 GHz installed (disk C
ONUs and disk D by
default
respectively)
should be NTFS.
The format of the
disks on which
the database
5000 NEs and the
ONUs and disk D by
default
respectively)
should be NTFS.
12 Version: A
Table 4-1 Hardware Configuration Requirements of the Server (Continued)
Network CPU Clock CPU Hard Disk Hard Disk Network

Memory
Scale Rate Quantity Space Format Card
The format of the
disks on which
the database
3000 NEs and the
ONUs and disk D by
default
respectively)
should be NTFS.
The format of the
disks on which
the database
1000 NEs and the
ONUs and disk D by
default
respectively)
should be NTFS.
The format of the
disks on which
the database
and the
500 NEs
6-core / 2.5 UNM2000 will be
(MDU+OLT), 2 16G 1 TB 2*GE ports
GHz installed (disk C
50000 ONUs
and disk D by
default
respectively)
should be NTFS.
The format of the
disks on which
the database
and the
300 NEs
UNM2000 will be
(MDU+OLT), 4-core / 3GHz 1 16G 600 GB 2*GE ports
installed (disk C
30000 ONUs
and disk D by
default
respectively)
should be NTFS.
Version: A 13
Client End
Table 4-2 shows the hardware configuration requirements of the UNM2000 client
end.
Table 4-2 Hardware Configuration Requirements of the Client
CPU Mem- Hard Disk Hard Disk

Network Scale CPU Clock Rate Video Card
Quantity ory Space Format
Equivalent to
The format of the
more than
disk on which the
1000 OLTs that
Intel XeonE5-2637V2 UNM2000 will be 1 GB discrete
are fully 1 16G 1*2 TB
(4-core), 3.5 GHz installed (disk D graphics
configured and
by default)
connected with
should be NTFS.
ONUs
Equivalent to The format of the
500 to 1000 disk on which the
OLTs that are Intel i3-4130 (2-core), UNM2000 will be 1 GB discrete
1 8G 1*1 TB
fully configured 3.4 GHz installed (disk D graphics
and connected by default)
with ONUs should be NTFS.
100 to 500 disk on which the nVIDIA
Intel Core i5-4200U (1.
OLTs that are UNM2000 will be GT720M 1 GB
6G-2.6G/3M) (2-core), 1 8G 1*500 GB
fully configured installed (disk D discrete
3.4 GHz
and connected by default) graphics
less than 100 disk on which the
Intel Corei5-4200U (1. Intel HD 4400
OLTs that are UNM2000 will be
6G-2.6G/3M) (2-core), 1 4G 1*500 GB integrated
fully configured installed (disk D
3.4 GHz graphics
and connected by default)
4.2 Software Configuration Requirements
The software requirements for the computer running the UNM2000 server end are
as shown in Table 4-3.
14 Version: A
Table 4-3 Software Configuration Requirements for the Server End
Configuration Item Requirement
u Windows Server 2008 R2 Standard (64-bit)

Note: Install the SP1 patch first before installing the server
software in the Windows Server 2008 R2 Standard (64-bit)
system.
Operating System u Windows Server 2012 R2 Standard (64-bit)
u SUSE Linux Enterprise 11 (64-bit)

u SUSE Linux Enterprise 12 (64-bit)
Solaris 11 (64-bit)
SQL Server 2008 R2

Note: The SQL server database only supports the Windows
operating system.
Database MySQL 5.7.18
Oracle 11g
Note: The Oracle database only supports the SUSE Linux
Enterprise12 system.
JRE JDK 1.8.0
The software requirements for the computer running the UNM2000 client end are as
shown in Table 4-4.
Table 4-4 Software Configuration Requirements for the Client End
Configuration Item Requirement
u Windows 7, Windows 8 or Windows 10

Operating System
u Windows Server 2008 or Windows Server 2012
JRE JDK 1.8.0
Version: A 15
5 Network and Application
The UNM2000 can provide unified network management solutions for the transport
network, access network and IP network. It supports four different deployment
modes for you to choose flexibly according to your network scale and deployment
requirements.
UNM2000 Deployment Mode
Network Mode between the UNM2000 and NE
Network Example
16 Version: A
5.1 UNM2000 Deployment Mode
The UNM2000 supports the distributed deployment mode, centralized deployment

mode, cluster disaster tolerance centralized deployment mode and cluster disaster
tolerance distributed deployment mode. You can select the UNM2000 system
deployment mode according to the network scale and deployment requirement.
5.1.1 Centralized Deployment Mode
The centralized deployment mode adopts the network scheme of multiple client
ends - single server. In this mode, only one UNM2000 server supports the access
and operation of multiple client ends. This mode provides easy deployment scheme
and the cost is relatively low, which is applicable for medium and small-scale
network. Figure 5-1 shows the network diagram.
Version: A 17
Figure 5-1 Centralized Deployment Mode
5.1.2 Distributed Deployment Mode
In the distributed deployment mode, multiple servers bear the functions of the
UNM2000 server. The UNM2000 EMS services can be deployed onto different
servers, among which the services that cause much pressure, such as data
collection, alarms, performance, events, object access and service configuration,
supports multi-instance configuration to implement load balancing, enlarge the
management capacity and improve the performance. Figure 5-2 shows the network
in this deployment mode.
18 Version: A
Figure 5-2 Distributed Deployment Mode
5.1.3 Cluster Disaster Tolerance Centralized Deployment

Mode
The cluster disaster tolerance centralized deployment mode includes one active
server and one standby server. When the active sever is faulty, the system will be
switched to the standby server to keep on the network monitoring, so as to
guarantee the uninterruptible system operation.
According to the deployment location of the active and standby servers, the cluster
disaster tolerance centralized deployment falls into local deployment and remote
deployment.
u Local deployment: The active and standby servers are deployed in the same
location, which are connected to the disk array using optical fiber connection.
Figure 5-3 shows the network diagram.
u Remote deployment: The active and standby servers are deployed in different
locations (equipment rooms or cities), which are connected to their respective
disk array. Figure 5-4 shows the network diagram.
Version: A 19
Figure 5-3 Local Centralized Deployment Mode of Cluster Disaster Tolerance
20 Version: A
Figure 5-4 Remote Centralized Deployment Mode of Cluster Disaster Tolerance
5.1.4 Cluster Disaster Tolerance Distributed Deployment

Mode
In the cluster disaster tolerance distributed deployment mode, the active and
standby stations form the cluster disaster tolerance system. When the active station
is faulty, the system will be switched to the standby station to keep on the network
monitoring, so as to guarantee the uninterruptible system operation. The distributed
deployment is also implemented within the station, so that the servers within the
station are load balanced and the management capacity is enhanced. The server
quantity in the active station is the same as that in the standby station. The servers
in the active and standby stations back up each other.
Version: A 21
According to the deployment location of the active and standby servers, the cluster
disaster tolerance distributed deployment falls into local deployment and remote
deployment.
u Local deployment: The active and standby servers are deployed in the same
location, which are connected to the disk array using optical fiber connection.
Figure 5-5 shows the network diagram.
u Remote deployment: The active and standby servers are deployed in different
locations (equipment rooms or cities), which are connected to their respective
disk array. Figure 5-6 shows the network diagram.
Figure 5-5 Local Distributed Deployment Mode of Cluster Disaster Tolerance
22 Version: A
Figure 5-6 Remote Distributed Deployment Mode of Cluster Disaster Tolerance
5.2 Network Mode between the UNM2000 and NE
The UNM2000 server communicates with the managed equipment via the in-band
network mode or out-of-band network mode.
In-band Network
The in-band network mode means to transmit the management data and the service
data of the equipment in one channel.
u Advantage: the network is flexible without any additional equipment, so that the
cost is relatively low.
u Disadvantage: if the network is faulty, the UNM2000 cannot operate because

the information channel of the managed network is interrupted.
Version: A 23
Out-of-band Network
The out-of-band network mode means transmitting the management data and
service data of the equipment in different channels. The management data channel
are the service data channel are mutually independent.
u Advantage: The device management channel is reliable. The UNM2000 can

locate the equipment information in the network in a timely manner to perform
real-time monitoring when the managed equipment is faulty.
u Disadvantage: The network is relatively complex. It is required to add devices

(maintenance channel) and the network construction cost is relatively high.
5.3 Network Example
The typical network mode of the UNM2000 is the single-system distributed

deployment mode. The UNM2000 connects with the NEs in out-of-band mode, as
shown in Figure 5-7.
Figure 5-7 Network Example
24 Version: A
6 Basic Function of the UNM2000
The following introduces the network management functions provided by the

UNM2000.
Configuration Management
Topology Management
Alarm Management
Event Management
Performance Management
Security Management
Resource Management
Operation and Maintenance Management
Version: A 25
6.1 Configuration Management
The UNM2000 provides the configuration management function for devices in the
entire network. You can perform various configurations on the devices using the
UNM2000.
Full Service Configuration
u The broadband access equipment carries multiple services such as data, voice,
IPTV and CATV simultaneously. The UNM2000 provides a universal
configuration GUI for full service configuration. You can configure multiple
services collectively using the UNM2000, which will greatly improve the
configuration efficiency.
u For system objects, the UNM2000 provides shortcuts for service configurations,
and integrates individual Grid configuration GUIs into a main GUI for
configuration operations. That is, all the configuration commands and ONU lists
under the system objects are integrated into a service configuration
management GUI to facilitate service configuration operations of users.
u The UNM2000 provides service configuration, ONU deauthorization, ONU

replacement, ONU activation / deactivation by the shortcut menu of the ONU
list.
Global Template and Global Configuration
u The UNM2000 provides the global profile and global configuration function. If
multiple NEs share the same or similar configuration, you can bind the global
profile to multiple NEs or deliver the global configuration to multiple NEs, so as
to improve the configuration efficiency.
u The global profile and global configuration are independent from the NE status,
so that the off-line NE configuration can be performed.
u The UNM2000 supports upgrade of ONUs in a batch manner.
26 Version: A
Hand-in-Hand Topology Management
u Supports managing association of double-MAC ONUs in the UNM2000.
u Views the hand-in-hand topology in real time and view the protection
information of the associated ONU.
SNMP Parameter Template Management
The UNM2000 provides the SNMP parameter template management function for
the SNMP v1/v2C/v3 versions, which is convenient for you to create, modify and
delete templates and bind NEs.
NE Communication Route Management
The UNM2000 provides management of manager programs and partition policies,

which means that you can create, delete and modify the manager programs and
partition polices.
Version: A 27
Pre-configuration
The UNM2000 supports the pre-configuration function. Before connecting the

equipment with the UNM2000, you can pre-configure the needed service on the
UNM2000. After connecting to the equipment normally, the UNM2000 will send the
pre-configured data to the equipment to complete the service configuration.
This function unties the service configuration from the status of connection between
the equipment and the UNM2000, and improves the configuration efficiency.
Network Access Status Management
The UNM2000 supports managing device register statuses. You can query the
register status of the device, set and deliver the resource management system
interconnection status of the device or selected card to initiate network access of
the device or selected card.
Signaling Tracing
The UNM2000 traces the signaling of the specified object and parses the real-time /
historical data packets. You can set the content displayed in the data packet and
save the collected data packet as a file.
28 Version: A
Configuration Synchronization
The UNM2000 supports synchronizing NE configurations. You can compare, upload

and download configurations of specified NEs so as to synchronize NE
configurations.
Migrating the PON Configuration
The UNM2000 supports PON configuration migration in the following three

scenarios:
u Migrates the ONUs between the PON ports of the same OLT / different OLTs.
u Migrates all / some ONUs from a PON port to another one.
u Migrates all / some ONUs from multiple PON ports located in different slots to
another PON port.
The configurations that can be migrated include LAN port service configuration,
voice port service configuration, bandwidth template binding information, VEIP data
service configuration, WAN connection service, WIFI service configuration, GPON
service bandwidth, QINQ domain template binding information, ONU management
VLAN, ONU port binding policy and ONU attribute configuration.
Checking the Configuration
The UNM2000 supports configuration data check. During service configuration, the
UNM2000 will automatically verify the validity of the configuration data. Once
detecting a configuration conflict or invalidity, the UNM2000 will prompt users to
modify the data until they are valid.
This function improves the configuration accuracy, saves the troubleshooting time
caused by service configuration faults at a later stage, and enhances the
configuration efficiency.
Configuration Backup
The UNM2000 provides the configuration backup function. You can set different
export tasks to export configuration files, NE software, card software or MAC
addresses of the PON port.
Version: A 29
The exported configuration file will be saved to the file folder named by export time,
convenient for you to view. You can also import the configuration file backed up on
the local computer to the UNM2000.
Upgrade
The UNM2000 supports system software upgrade, ONU batch upgrade, service
card batch upgrade and whole package upgrade by setting upgrade tasks.
Data Synchronization
The UNM2000 provides the software / hardware version upgrade, configuration

upload, NE automatic discovery and ONU service scheduled shutdown so as to
implement data synchronization between the UNM2000 and the NEs.
6.2 Topology Management
Topology management displays the status of the connection between the managed
NEs in topology graphics. You can understand the network condition of the entire
network and monitor the operation status in real time by viewing the topology view.
Entire Network Monitoring Topology
The UNM2000 provides multiple topology management views, which enables you to
manage devices and the network in multiple dimensions conveniently.
u Main topology view: The main topology view of the UNM2000 is composed of
the object tree pane and the physical topology view / customized view.
4 Object tree pane: Displays the hierarchy of the network structure in the tree
form. Click each node on the object tree to locate each node in the
physical topology view / customized view. It supports adjusting the
sequence of the objects on the object tree. When you log in to the
UNM2000 next time, the system displays objects in the sequence adjusted
last time.
4 Physical topology view: Displays the network connection relationship

between each device in the entire network.
30 Version: A
4 Custom view: You can customize the objects displayed in the view. The
view only displays the network connection relationship of the selected
objects.
4 You can set different background images for logical domains in the main
topology.
u Sub-topology view: Displays topological relationships between the physical

units, such as subracks, cards and interfaces, of a specific NE.
u Thumbnail: Displays the global view of the entire network.
If the current view cannot display the detailed condition of the entire network
due to the large scale of the network, you can view in the thumbnail. The
purplish red frame in the Thumbnail pane shows the display area in the current
view. You can drag the frame using the mouse to move the display area.
u Hot-spot area view: The UNM2000 automatically generates the hot-spot area
topology view according to your settings so that you can manage and monitor
the important devices by groups. The hot-spot area supports dragging,
zooming in, zooming out, selecting, moving and thumbnail view.
u Topology filter: The main topology can be filtered and displayed according to
your filtering settings.
4 You can set multiple logical domains, NEs and links as the filtering criteria.
The filtering result should match all the criteria. The UNM2000 performs
fuzzy match according to the logical domain, NE and connection name
entered.
4 The modified topology filtering setting takes effect on the current user. The
settings are still valid when the user log in again. If a user sets the filtering
criteria on multiple client ends simultaneously, only the latest setting will
take effect when he or she accesses the main topology next time.
Version: A 31
4 The main topology are filtered and displayed according to your filtering
settings. The objects set in the filtering criteria are displayed while those
not in the filtering criteria are not displayed.
u Service topology view: Graphically displays the end-to-end service traffic of the
ONU and differentiates path statuses by different colors.
Topology Alarm and Status Display
The UNM2000 supports different colors and icons to represent the logical domains
and NE alarms / statuses, as shown in Figure 6-1 and Figure 6-2.
32 Version: A
Figure 6-1 Logical Domain Icon Example
Figure 6-2 NE Icon Example
u Different NE node icons represent different device types.
u The ground color of the topology node icon indicates the polling status (normal,
unknown, communication interrupted, etc.) and alarm level of the NE. The
ground color of the icon shows the color of the highest-level alarm. Table 6-1
lists the color description.
Table 6-1 Alarm Color Description
Alarm Priority Color Description
Dark grey Communication interruption
Red Critical alarm

Orange Major alarm
Yellow Minor alarm

Blue Warning alarm
Green Normal
Light grey Unknown
u The icon border indicates there is an unconfirmed alarm on the monitored

object. The border color represents the highest level of all the unconfirmed
alarms.
u The icon at the top right corner of the monitored object prompts the latest
special alarm according to the definition. You can view the special alarm
definition by clicking Legend on the toolbar of the topology view.
Version: A 33
u The logical domain icon displays the highest-level alarm color of the NE nodes
in the logical domain and the latest special alarm icon. The UNM2000 supports
manually dragging or sorting the NEs in the logical domains, which is
convenient for searching NEs.
Access Method of Integrated Management
The UNM2000 provides the integrated access for NE management functions in the
topology view. During the network maintenance, you can perform the Ping, physical
configuration inspection and alarm viewing operations on the equipment directly via
the topology view.
6.3 Alarm Management
The alarm management is used to perform real-time monitoring on the failures and
abnormalities generated during device operation, and provide detailed information
and analysis of the alarms, so as to help isolate and handle failures quickly.
Alarm Classification
The UNM2000 classifies the alarms according to the alarm levels and alarm
statuses.
The UNM2000 sets the alarm levels according to the severity of the alarms.
Generally there are four alarm levels: the critical alarm, the major alarm, the minor
alarm, and the warning alarm.
u Critical alarm: Refers to the alarm which causes the service interruption and
requires immediate troubleshooting.
u Major alarm: Refers to the alarm which affects services and requires immediate
troubleshooting.
u Minor alarm: Refers to the alarm which does not affect services but requires
troubleshooting to avoid deterioration.
u Warning alarm: Refers to the alarm which does not affect the existing services
but may influence services later; you can decide whether to handle it as
desired.
34 Version: A
The UNM2000 classifies the alarms into the current alarms and the alarm history
according to the alarm statuses.
u Current alarm: The alarm data saved in the current alarm database of the
UNM2000.
The same alarm frequently generated by an object will be displayed as one

entry in the current alarm list. You can view the alarm log to query all the alarm
records.
u Alarm history: The current alarms that have been handled will be alarm history
after a preset period.
The alarm history will be saved into the alarm history database from the current
alarm database.
Entire Network Alarm Display
Alarm display is an important measure for informing you about the network
operation conditions in a timely manner. The UNM2000 provides multiple forms of
alarm display.
Below are the alarm display forms provided by the UNM2000:
u Alarm view: You can view the current alarms and historical alarms of the
selected device in the UNM2000 window.
4 View the alarm maintenance information to know information about alarm

causes, processing suggestions and maintenance experiences and so on.
4 View the alarm details to obtain the alarm name, location information and
additional information. View the additional information to know about the
performance value that exceeds the threshold and triggers the alarm.
u Alarm panel prompt: The alarm panel in the home page of the system can
display the total alarm number of each level in the entire network. The
UNM2000 can display the total number of the alarms that comply with the
profile conditions in the alarm panel according to the pre-set profile.
Version: A 35
u Alarm audio-video prompt: When an alarm occurs in the device, the UNM2000
will generate an audio prompt, and intelligently control the audio prompt play
time of various alarms. Meanwhile, the corresponding alarm indicator will be
illuminated in the color corresponding to the alarm level. When alarms of
several levels coexist, the alarm indicator LED will be illuminated in the color
corresponding to the alarm at the highest level among them.
u Alarm sequence: You can set the alarm sequence according to your concern.
u Alarm information exporting and saving: You can export and save the desired
alarm information in the format of TXT, Excel, CSV, XML, PDF or HTML, so as
to learn the historical operation conditions of the network.
Alarm Data Consistency
The UNM2000, as the network management system, should guarantee the

consistency between the alarm data it saves and the alarm data on the device. In
this way, you can learn practical network operation status in a timely manner via the
UNM2000. This raises high requirements on data consistency.
The UNM2000 ensures the consistency between the data it saves and the data on
the device by means of automatic update in the occasion of connection, automatic
polling, manual polling and Trap active reporting.
u Automatic update in the occasion of connection: The UNM2000 will

automatically update the device data when connecting with the device. After
obtaining the latest data of the device, the UNM2000 will compare the new data
with the old one. If the new data is the same with the old one, the UNM2000 will
not process the new data; if different, it will process only the different part of the
data.
u Automatic polling: The manager module of the UNM2000 will automatically poll
about the managed device at regular intervals. The device will report the latest
data to the UNM2000 after receiving the polling information, and the UNM2000
will compare the received new data with the old data. If the new data is the
same with the old one, the UNM2000 will not process the new data; if different,
it will process the different part of the data.
u Manual polling: After a device is selected, the UNM2000 will poll about the
selected device and process the newly received data following the automatic
polling principle.
36 Version: A
u Trap report: If a new alarm is generated in the equipment prior to the next
UNM2000 poll cycle, the equipment will report Trap to the UNM2000 in a timely
manner. The Trap contains the information of this change, and the UNM2000
will respond according to the information contained in the Trap. If a new alarm
is generated, the alarm panel of the UNM2000 will update automatically and the
alarm list will display the new alarm automatically, so that you can understand
the alarm information of the network in a timely manner.
Locating Alarms
The UNM2000 supports the alarm isolation function, so that you can isolate the
alarm to the port level using the UNM2000.
Alarm Shield
A large quantity of alarms may be generated during the network commissioning,

testing and maintenance process or the project installation commissioning and
cutover maintenance stages. For the alarms requiring no concern, you can shield
them. The shielded alarms will not be displayed or saved. After the shielding
conditions are set, the alarms meeting the conditions will be shielded.
Alarm Confirmation and Saving
u Alarm confirmation: the measure to identify whether the alarm has been
processed by the administrator. The confirmed status indicates that the alarm
has already been handled by the administrator; while the unconfirmed alarm
indicates that the alarm has not been handled yet. The UNM2000 provides
manual confirmation and automatic confirmation of alarms. The UNM2000
provides the function of confirming and clearing alarms with one click. It
enables you to delete an alarm simultaneously when confirming it, improving
the maintenance efficiency.
u Alarm saving: You can save the historical alarms into files or delete them
directly. The saved alarm data will be deleted from the UNM2000 to free up
space, so as to guarantee the stability and high efficiency of the UNM2000. The
UNM2000 supports data saving at regular intervals, data saving according to
count of records and data saving according to number of days.
Version: A 37
Alarm Clearing
Alarm clearing will change the status of the alarm to alarm clearing. The alarm can
be automatically or manually cleared.
u Automatic clearing: When a failure is eliminated, the device generates a

clearing alarm and automatically clears the original alarm. When the alarm is
automatically cleared by the device, the corresponding NE name is displayed in
the "Cleared By" column of the alarm.
u Manual clearing: If the UNM2000 does not receive the clearing alarm due to a
failure occurring in the network, you can clear the alarm manually.
Alarm Forwarding
You can set the alarm forwarding time for the alarm item. If the reported alarm
disappears within the set time period, the alarm will not be forwarded. However, if
the alarm persists at the end of the set time period, the alarm will be automatically
sent to the preset mobile phone or mail box of the maintenance staff, so that the
maintenance staffs can handle the network alarms in a timely manner.
Alarm Customization
u You can modify the alarm levels and highlight your concerned alarms. The
UNM2000 supports modification of alarm levels in different scopes in the entire
network, including levels of the global alarms, object alarms and alarms
concerning card / port types.
u You can set an alarm for your concerned parameter which is not defined
currently in the UNM2000 and set value range for generating the alarm. When
the device parameter reaches the set range, the UNM2000 will report the
alarm.
u The UNM2000 supports redefinition of alarm names. You can modify the pre-
defined alarm names to your desired ones according to the maintenance
requirements.
38 Version: A
Alarm Project Status
When an NE is installed, commissioned or tested, it will trigger some alarms and

report them to the UNM2000. However, it is insignificant to process these alarms. In
this situation, you can set project (maintenance) status alarms to directly identify
and filter these alarms so as to quickly locate and process more important alarms.
You can set the maintenance status of the managed object through the default
project or the customized project. The managed objects include NEs, cards and
ports. You can also configure the maintenance status of the selected NE by the
shortcut menu of NE in the main topology, which is more convenient. After setting
the NE to the maintenance status, the maintenance status icon appears for this NE
in the main topology. The maintenance status alarm does not influence the color of
the NE.
Alarm Template Management
You can set multiple current alarm or alarm history query templates. The UNM2000
can open multiple alarm query windows concurrently so that you can monitor alarms
of different alarm templates.
Version: A 39
Alarm Flashing Rules
The UNM2000 supports creating, modifying and deleting alarm flashing rules. If an
alarm is regarded as a flashing alarm, only the frequency of the subsequent flashing
alarms that meet the criteria will be reported. The UNM2000 only displays the first
flashing alarm with the flashing icon. By clicking the flashing alarm, you can view the
details of all the flashing alarms.
Alarm Frequency Analysis
The UNM2000 supports creating, modifying and deleting frequency analysis rules.
After an alarm frequency analysis rule is set and the occurrence times of an alarm
over a specified time period exceed the preset number, the rule is triggered and the
UNM2000 will handle the alarm according to the preset policy.
6.4 Event Management
Events are the notifications generated in the normal system operation and prompt
users actively. The UNM2000 classifies the events into four levels (critical, major,
minor and warning) according to the severity.
Viewing Events in the Entire Network
You can view the events in the entire network or certain events according to
specified conditions, and save the query conditions to a profile.
40 Version: A
Reporting Events Automatically
You can set the automatic report of the events that meet the specified conditions,
including reporting the latest events on the Event Report tab. You can also set the
automatic scrolling of the event list so that you can view the latest events in a timely
manner.
Signaling Tracing
Tracing the signaling is used to trace the signaling frame of the communication
between the current IAD and the voice communication card, so as to find the
communication faults in a timely manner. This function is only supported by the
FTTH-type and FTTB-type ONUs that support voice service.
6.5 Performance Management
The UNM2000 supports query of real-time performance data and comprehensive

management performance data. You can monitor the real-time performance of the
equipment in the access network and compare it with the instant performance of the
equipment. This function helps users to learn the current operation conditions and
basic performance of the network, so as to prevent network faults and make
appropriate planning for the network operations.
Performance Classification
The UNM2000 can display the following three types of performance data:
u Real-time performance: The current performance data of the device are saved
at the device side and read by the UNM2000.
Version: A 41
u Current performance: The average value of the performance data in the

specified 15-minute interval saved on the device. You can query the current
performance data of the current 15-minute and the latest 1st to 16th 15-minute
intervals.
u Historical performance: The performance data saved in the UNM2000

database according to the performance collection settings, including the 15-
minute and 24-hour performance data.
Performance Display and Saving
u Performance display: The real-time performance and performance history data

can be displayed by lists, curves and charts. The current performance data can
be displayed by lists. You can learn the performance parameter values and
have an idea of the change in performance parameters displayed in different
forms. In this way, the network operation conditions and trends over time can
be identified, and network failure can be thus prevented.
u Performance saving: You can save the historical performance data into files or
delete them directly. The saved performance data will be deleted from the
UNM2000 to free up space to guarantee the stability and high efficiency of the
UNM2000. The UNM2000 supports data saving at regular intervals and data
saving according to number of days.
Performance Comparison
The UNM2000 provides the function of performance comparison. The values of the
same performance parameter concerning the same port on the same device
collected in different cycles are put together. You can use this function to compare
the instant performance data of the selected device, so as to have a visible
knowledge of the change in performance data, understand the network operation
conditions and change trend, prevent network faults, and make appropriate
planning for the network operation.
Performance Query Template
u The UNM2000 provides current / historical performance query template

management. It can save the performance query conditions as a query
template.
42 Version: A
u When creating a performance query template, you can copy from an existing
performance query template to create a new one.
Analysis of PON Traffic Statistics
The UNM2000 supports analyzing device traffic, optical power and device health by
charts.
Ranking Statistics (Top N)
The UNM2000 supports displaying the device PON traffic top ranking and device
health top ranking in charts.
Version: A 43
6.6 Security Management
The security management is used to prevent unauthorized login and operations so

as to ensure secure running of the network. The UNM2000 provides a series of
security policies, such as user management, authority and domain division
management, access control and user security to guarantee network security.
User Management
When planning the UNM2000 users, you can properly assign operation authority to
users and restrict them to use the UNM2000 in appropriate scenarios.
u User: The user who uses the UNM2000 client.
u User management: The username and its password uniquely determine the
login, operation and management authority. After initial installation of the
UNM2000, it provides only one default user: admin. The admin user has all the
operation authority and management authority, and other users are directly or
indirectly created by the admin user.
44 Version: A
u User group: Indicates a set of users. After a user is added into a group, this
user has all the authority bound with the group. The total authority of the user
includes the user's authority and the authority of the user group to which the
user belongs.
u User group management: By creating a user group, you can manage a batch of
users with the same authority. This function helps you manage users in a batch
manner and thus reduce the management cost. The UNM2000 provides five
default user groups: Administrators group, Security Admin Group, inspector
group, operator group and maintainer group.
The UNM2000 supports creating, modifying and deleting users.
When you create a user account, you need to set the user details, associated user
group, management domain, operation authority and access control list (ACL).
When a user enters incorrect passwords several times, this user will be locked, and
can be unlocked through the following ways:
u When the admin user is locked, it will be automatically unlocked after the preset
unlocking time expires.
u When a user other than the admin is locked, it will be automatically unlocked
after the preset unlocking time expires. It can also be manually unlocked by the
admin user.
Version: A 45
Authorization and Domain Division
The UNM2000 supports authorization and domain division management, which only
allows the user to deliver the operations within its domain authority scope to the NE.
Only the users belonging to the Security Admin Group can perform authorization
and domain division for other users.
u Domain division: Divides the objects (devices, services or data) in the network
into different domains. By assigning the domain authority to a user or user
group, the UNM2000 enables the user to perform operations on the objects
within its domain. Meanwhile, it supports directly assigning a device for a
specified user or user group. With domain division, the UNM2000 enables
different maintainers to manage network objects in different domains.
u Authorization division: With domain division, you can authorize a user or user
group by assigning a specific operation authority for it. With the authorization
division based on the domain division, you can enable the administrators with
different responsibilities (positions / operation and maintenance departments) in
the same area to have different operation authority on the managed objects
within the area.
The authorization and domain division function of the UNM2000 implements unified
management based on devices and authority assignment based on functions of the
devices.
The UNM2000 supports the domain-based management via the object tree as
follows:
u For a domain administrator user, the systems and cards not under his
management will not be displayed in the object tree tab.
u While displaying the alarm indicator LEDs, the system will filter the nodes that
are not under the management of the user and mark them with special icons.
Generally the filtering is performed on modules or objects of higher levels. As
for cards, the filtering is only performed on the EC2 card or the cards with
remote modules.
u The system filters the nodes that need not be displayed when generating the
object trees, including the object tree in the main GUI and the object trees in the
other operation GUIs.
46 Version: A
The UNM2000 supports the domain-based management via menu control as

follows:
u Object menu: Only users with full authority on the higher-level objects can add /
delete the lower-level objects or reset the card types; and only users with
authority on the module and its higher-level objects can check the physical
configuration.
u Main menu: The users with restricted authority on the domain cannot perform
the operations such as forcibly saving, importing and exporting. Also, they
cannot perform user management, domain management and command
authority management (which can only be executed by the advanced
administrators).
u The system filters the main menu and the object menu options (including
checking physical configuration, adding / deleting / importing / exporting logical
domains, and saving forcibly) according to the domain authority.
4 Checking physical configuration: Only users with authority on modules or

higher-level objects can check the physical configuration.
4 Basic operations on the objects at each level: Only users with authority on
all the lower-level objects of the selected object can add / delete the lower-
level objects.
u Only the users with authority on the system can set the performance collection
scheme.
Access Control
u To guarantee the security of the network, the UNM2000 allows the user to log in
only with the designated IP address and within the designated period of time.
Even if the ID and password of a certain user are stolen, the malicious user
cannot log in the UNM2000 server. In this way, the security of the UNM2000 is
enhanced.
u During network operation and maintenance, the network administrator can log
into the system as an advanced administrator and monitor the entire network. If
the operation of a user at a lower level is abnormal, the administrator can force
the user to log out (when the user logs out, the UNM2000 can save its topology
automatically), so as to guarantee the security of the system operation.
Version: A 47
u When using the UNM2000 to maintain the network, you can manually lock the
UNM2000 client end if you are away from the keyboard for a certain period of
time, so as to protect the account being used by an illegal user. You can also
set to lock the client end automatically, so that the client end will be locked
automatically if no operation is performed on the UNM2000 for a specified
period of time. This function guarantees the security of the UNM2000 and the
network.
u The UNM2000 can set the maximum times that one account logs into the same
UNM2000, so as to guarantee the network security.
User Security
For guaranteeing the security of the UNM2000 accounts, you can use the
UNM2000 to set the maximum / minimum length of password, the maximum /
minimum period of password validity, whether the password can be set similar to
historical one, the minimum number of letters / digits contained by a password. You
can also enable the unlogged-in user policy, and temporarily close or delete the
accounts that have not logged in the UNM2000 for a specified duration.
48 Version: A
Log Management
The logs record the user operation information and the important events occurring in
the system. By querying, gathering statistics of and saving logs regularly, the
administrator can detect illegal login and operations, and analyze the failures. By
browsing and gathering statistics of logs, the administrator can query the operation
information of the EMS and save the logs.
u Log type: The UNM2000 logs include operation logs, system logs, security logs
and northbound interface command logs.
4 Operation logs: Records the non-security-related operations performed by

users in the UNM2000, such as querying current alarms and ONU
authorization.
4 System logs: Records the operations automatically performed by the

UNM2000, such as scheduled tasks and system tasks.
4 Security log: Records the security-related operations performed in the

UNM2000, for example, user login and user logout.
4 Northbound interface command logs: Records the operations performed

on the device by users on the UNM2000 client end via the northbound
interface commands. The northbound interface command logs include TL1
command logs, Web Service command logs, Socket logs and alarm logs.
u Log query / statistics: You can query logs by setting various query conditions,
such as user information, operation result, risk level, start time range, operation
name and operation objects to obtain the operation information of users in the
UNM2000 in real time.
u Log forwarding: The UNM2000 supports forwarding the UNM2000 operation

logs to the Syslog server to save various logs, providing reference for
maintenance and releasing the storage space of the UNM2000 server.
u Log saving: The UNM2000 can delete the log data from the database and save
them as files into the specified file folder to avoid that too many resources are
occupied by the log data and improve the running performance of the EMS.
The UNM2000 supports overflow saving and manual saving.
u Authority of viewing logs: The advanced administrator and other system users
have different authority to view logs. The users other than the advanced
administrator can only view their own logs.
Version: A 49
6.7 Resource Management
The UNM2000 provides the resource statistics and information import functions.
Detecting Physical Configuration
The UNM2000 provides the physical configuration detection function. It supports

detecting the incremental or full physical configurations of the NEs and
synchronizing the configuration of all NEs or a single NE.
Batch Operation
Performing batch operations on resources can reduce repeated operations so as to

improve the working efficiency.
u The UNM2000 supports modifying logical domains, NEs, card ports and ONU
names in a batch manner.
u The UNM2000 supports deleting NEs in a batch manner. You can select
multiple NEs in a batch manner to be deleted.
u The UNM2000 supports importing the template to query ONU information in a

batch manner.
Importing the ODN EMS Information
The UNM2000 supports importing the local ODN EMS information.
Tagging an NE
The UNM2000 enables you to mark the NE and query marks.
50 Version: A
Resource Statistics
The UNM2000 provides management of resource statistics and resource statistics

export tasks and supports automatically synchronizing new OLTs to the statistics
export tasks.
Statistics Type Statistics Item
u NE Resource Statistics
u Card Resource Statistics
u Port Resource Statistics
Physical Resource u ONU Resource Statistics
Statistics u ONU Port Resource Statistics
u MSAN Port Resource Statistics
u Area Statistics
u Equivalent NE Statistics
u ONU User Statistics

u Local VLAN Statistics
u NE MGC Service Statistics
u Device Type Statistics
u PON Device Capability Statistics
Other Type Statistics u ONU WAN Service Statistics
u ONU Out of Service Time Statistics
u Management VLAN Statistics
u LLDP Info Statistics
u ONU Local Manager Configuration Statistics
u Optical Power Statistics
Version: A 51
Statistics Type Statistics Item
u NE Resource Statistics Export

u Card Resource Statistics Export
u Port Resource Statistics Export
Physical Resource
u ONU Resource Statistics Export
Statistics Export
u ONU Port Resource Statistics Export
u MSAN Port Resource Statistics Export
u Area Statistics Export
u ONU User Statistics Export

u Local VLAN Statistics Export
u NE MGC Service Statistics Export
u Device Type Statistics Export
u ONU WAN Service Statistics Export
Statistics Export of
u ONU Out of Service Time Statistics Export
Other Types
u Management VLAN Statistics Export
u LLDP Info Statistics Export
u ONU Local Management Configuration Statistics Export
u PON Device Capability Statistics Export
u Optical Power Statistics Export
Figure 6-3 The Resource Statistics GUI
52 Version: A
Managing the NE Maintenance Information
The UNM2000 provides the NE maintenance information management function and

supports managing NE's physical location information and maintainer's contact
information so as to improve the operation and maintenance efficiency.
6.8 Operation and Maintenance Management
The UNM2000 integrates the automatic inspection, PON traffic analysis, resource
analysis and diagnosis and troubleshooting functions.
Automatic Inspection
u Inspection Template: Supports creating, modifying, deleting and viewing

inspection templates.
u Inspection Task: Supports creating, modifying, deleting and viewing inspection

tasks, and enabling / disabling, executing, suspending and stopping inspection
tasks.
u Inspection Result: Supports viewing inspection result and supports incremental

inspection on the inspection items that fail the inspection or have anomalous
commands.
u Inspection Report: Supports exporting the inspection reports in format of Excel

automatically or manually.
PON Traffic Analysis
The PON Traffic Analysis function, with visualized data analysis, intelligent warning
and alarm management and precise capacity analysis, helps you comprehensively
understand the service traffic and bandwidth usage of the PON network, gather
statistics on and analyze traffic growth trend and resource use efficiency of the PON
network and effectively predicts the necessity to expand the capacity of the network
resources and balance the optimization work so as to prevent network congestion
and guarantee the transfer quality of various services.
Version: A 53
u Supports analyzing the OLT uplink port, OLT PON port, ONU PON port and link
traffic.
u Supports displaying traffic trends of the OLT uplink port, OLT PON port and
ONU PON port in graphs.
u Supports analyzing the traffic of the port and hot-spot area.
u Supports ranking (Top N) the traffic of the OLT uplink port, OLT PON port and
ONU PON port.
u Supports collecting statistics of uplink / downlink CRC errors of OLT uplink

ports and PON ports to help analyze the failure reason of the PON network.
u Supports collecting statistics of and analyzing the traffic load of the OLT uplink
ports and PON ports, providing basic data for the planning of the uplink ports
and user resources.
u Provides bandwidth utilization rankings, traffic analysis reports and link

bandwidth utilization reports for the OLT uplink ports, OLT PON ports and ONU
PON ports. This helps users analyze the traffic.
u Provides area statistics and analysis function; collects statistics of and

analyzes traffic by area.
u Supports second-level traffic monitoring to help clients monitor the traffic of key
areas precisely.
54 Version: A
u The system, by monitoring the seven-day average of busy-hour downlink

bandwidth usage, adds tokens to the objects whose bandwidth usage exceeds
the threshold or removes tokens from the objects that resume normal state in a
timely manner, so as to remind maintainers to pay attention and take an active
part in network maintenance to reduce impact on user services.
u Provides management of performance threshold-crossing alarms and supports

pushing traffic threshold-crossing reports to the specified user.
Resource Analysis
The UNM2000 supports collecting statistics of physical resource online ratio and
network resource information by area.
u Physical resource statistics:
Table 6-2 Statistical Items of Physical Resource Online Ratio
Category Statistics Item
Total number of PON ports
PON port resource Number of online PON ports
PON port usage
Total number of OLT uplink ports
OLT uplink port resource Number of OLT uplink ports in use
OLT uplink port usage
Total number of ONUs

ONU resource
ONU online ratio
Version: A 55
Table 6-2 Statistical Items of Physical Resource Online Ratio (Continued)
Category Statistics Item
Total HGUs
Total SFUs
u Network resource statistics: Collects statistics on the number of OLTs, number

of OLTs with services configured and number of dual-uplink OLTs with services
configured.
u Supports exporting reports of physical resource online ratio statistics and

network resource information statistics.
Fault Diagnosis and Location
The UNM2000 supports the intelligent fault location function to quickly locate the
fault point, improving the fault isolation efficiency.
u Test for diagnosis: Provides network connectivity tests and service quality tests.
You can diagnose the network faults based on test results to narrow down the
fault range and shorten the time for fault isolation and repair.
4 Supports the PPPoE emulation test.
4 Supports detecting the uplink rate, downlink rate and bandwidth usage of
the ONU.
u Failure isolation: Graphically displays the end-to-end service traffic of the ONU
and differentiates port statuses by different colors.
4 Graphically displays the end-to-end service traffic of the ONU,

differentiates port statuses by different colors and analyzes the failure
location by the port status.
4 The alarm window supports navigating to the topology view or NE

manager via the shortcut menu.
4 Supports locating the faulty ports by viewing the ONU management status
and ONU running status in the NE manager.
u Transport service failure diagnosis:
4 Alarm monitoring:
56 Version: A
The maintenance engineer receives a great number of alarms reported by

an NE and wants to determine whether these alarms influence the
services or not. This function facilitates identifying the alarm that influences
the services from massive alarms and finding out the root alarm as far as
possible.
4 Service monitoring:
When monitoring services in a centralized manner in the UNM2000, the

maintenance engineer finds that the color of an alarm is changed and
needs to determine whether the alarm influences the services. In this
situation, the maintenance engineer can analyze the connection status of
the path and faulty point to find out the root alarm. If the root alarm cannot
be found, the UNM2000 displays the alarm of a hop that influences the
path, which prompts the maintenance engineer to access the failure
diagnosis function.
u Template settings: Quickly detects the failures with the system default template
or custom template.
Version: A 57
7 Technical Specifications
This chapter introduces the technical specifications of the UNM2000.
Management Capacity
Performance Specification
Standards
58 Version: A
7.1 Management Capacity
Each UNM2000 can manage 100 thousand NEs.
7.2 Performance Specification
This section introduces the performance parameters supported by the UNM2000,

including the startup / shutoff time, number of simultaneous client logins, alarm / log
capacity and processing capability, etc.
Performance Specification List
Table 7-1 shows the performance specifications of the UNM2000.
Table 7-1 Performance Specification List
Item Specification
UNM2000 startup time < 10 minutes

UNM2000 shutoff time ≤ 10 seconds
Concurrent client ends ≥ 500
Number of users admitted ≥ 2000
Number of online users ≥ 1000
Number of user groups
50
admitted
Number of object groups
100
admitted
Number of operation groups
255
admitted
System homepage delay ≤ 10 seconds
Response time delay of a
≤ 2 seconds
single operation
Response time delay of batch

≤ 5 seconds
operations
Report generation time delay ≤ 8 seconds

Alarm throughput ≥ 1000 entries / second
Alarm response delay ≤ 10 seconds
u Number of records ≤ 10000: 2s
Alarm query delay u 10000 < number of records ≤ 100000: 8s
u 100000 ≤ number of records: 20s
Version: A 59
Table 7-1 Performance Specification List (Continued)
Item Specification
Alarm handling capability ≥ 100 entries / second

Performance statistics delay < 2 minutes
Performance response delay < 10s
u Number of records ≤ 10000: 2s

Performance query delay u 10000 < number of records ≤ 100000: 8s
u 100000 ≤ number of records: 20s
Maximum number of
performance objects to be 10000
counted
Configuration synchronization
< 2 minutes
time delay
Data export time delay ≤ 2 minutes/100M

Configuration storage duration Long-term operation
Current alarm storage capacity ≥ 500 000

Historical alarm storage
≥ entries over three months
capacity
5-minute historical
≥ entries over one month
performance storage capacity
15-min historical performance

≥ entries over six months
storage capacity
60-min historical performance

≥ entries over one year
storage capacity
24-hour historical performance

≥ entries over one year
storage capacity
Storage capacity of operation

logs
Storage capacity of monitoring

data
Packet Loss Rate and Performance of the UNM2000
High packet loss rate of the network will cause performance degradation of the
UNM2000 and lower the success rate of the UNM2000 in service distribution.
u When the network packet loss rate is lower than 10%, the success rate of the
UNM2000 in service distribution is not lowered visibly.
60 Version: A
u When the network packet loss rate is higher than 10% but lower than 15%, the
success rate of the UNM2000 in service distribution is visibly lowered.
u When the network packet loss rate is higher than 15%, the performance of the
UNM2000 degrades sharply, and extensive service distribution failure occurs.
Server End-Client End Bandwidth Requirements
u If the server manages 1000 OLTs and accesses 128 client ends, the bandwidth
of the communication between the server and each client end should be no
less than 100M.
u If the server manages more than 1000 OLTs and accesses 128 client ends, the
bandwidth of the communication between the server and each client end
should be no less than 1G.
Server-Northbound Interface Bandwidth Requirements
u The bandwidth for the communication between the server and the northbound
interface for the TL1 service should be no less than 100M.
u The bandwidth for the communication between the server and the CORBA
northbound interface should be no less than 100M.
u The bandwidth for the communication between the server and the WebService
northbound interface should be no less than 100M.
u The bandwidth for the communication between the server and the superior
network management system should be no less than 100M.
7.3 Standards
This section introduces the standards and protocols followed by the UNM2000.
u The interfaces between the UNM2000 and equipment comply with RFC
standards such as SNMP and MIB-II.
u Supports RFC Telnet/TCP/IP standards.
u Supports IETE RFC1901-1908 standards.
u Supports standards relevant to telecommunication management network such

as ITU-T M.3010, ITU-T M.3100, ITU-T M.3400 and ITU-T.X.721.
Version: A 61
u The CORBA northbound interface complies with the TMF MTNM series
standards.
u The WebService northbound interface supports the MTOSI 2.0 standard.
u The Socket northbound interface complies with the OMC system function
specifications, OMC system general technical specifications and OMC system
northbound interface data specifications.
u The TL1 service supports DSLForumTR-069, DSLForumWT-142 and SFF-

8472 standards.
62 Version: A
8 External Service Ports
If the firewall is deployed in the network, users should enable the external service
ports of the UNM2000 to ensure the normal communication. The external service
ports used by the UNM2000 are listed below.
Table 8-1 Ports Between the Server and the NE
Source IP Source Destination IP Sink Port Process of Protocol Port Description

Address Port Address (Listening) the Sink Port
The FTP server

service port,
providing the FTP
The IP address file transfer
NE IP of the service. It is used
Any 20 FTP TCP
address UNM2000 to upgrade the NE
server software, back up
the NE data and
upload the NE
configuration.
The FTP server

service port,
providing the FTP
The IP address file transfer
NE IP of the service. It is used
Any 21 FTP TCP
address UNM2000 to upgrade the NE
server software, back up
the NE data and
upload the NE
configuration.
The alarm
reporting port,
which receives the
The IP address
alarms sent from
NE IP of the
Any 162 SNMP UDP the SNMP device.
address UNM2000
If it is disabled, the
server
UNM2000 will not
receive the alarms
from the device.
Version: A 63
Table 8-1 Ports Between the Server and the NE (Continued)
Source IP Source Destination IP Sink Port Process of Protocol Port Description

Address Port Address (Listening) the Sink Port
The Telnet
protocol port,
which is used by
The IP
the NE
address of
management
the Any NE IP address 23 Telnet TCP
process to
UNM2000
configure the
server
device and
synchronize
resources.
It communicates
with the device via
SNMP. It is the
operation and
maintenance port,
The IP which receives the
address of SNMP commands
the Any NE IP address 161 SNMP UDP sent from the
UNM2000 UNM2000 server.
server If it is disabled, the
communication
between the
UNM2000 and the
SNMP device will
fail.
It communicates
with the device via
SNMP. The device
4.0 version only
The IP supports the 162
address of port heartbeat
the Any NE IP address 162 SNMP UDP communication. If
UNM2000 it is disabled, the
server communication
between the
UNM2000 and the
SNMP device will
fail.
64 Version: A
Table 8-2 Ports between the Server and the Client
Sink Port
Source IP Source Destination Process of the
(Monitor- Protocol Port Description
Address Port IP Address Sink Port
ing)
The IP The IP
address of address of
The FTP service command
the Any the 21 FTP TCP
port.
UNM2000 UNM2000
client server
The IP The IP
The FTP service data port. It
is 20 in PORT mode and
the Any the 20 FTP TCP
based on the FTP
UNM2000 UNM2000
configuration in PASV mode.
client server
The IP The IP It is the management and
address of address of maintenance channel of the
the Any the 22 SSH TCP EMS server on Linux OS.
UNM2000 UNM2000 The UNM2000 does not use
client server this port itself.
The port used by Windows

OS remote desktop protocol
(RDP). The Windows
The IP The IP
provides the remote desktop
service via this port. It is
the Any the 3389 RDP TCP
enabled only when the
UNM2000 UNM2000
remote desktop is used to
client server
operate the Windows server.
The UNM2000 does not use
the port.
The IP
The IP address of
The tomcat9 monitoring port
address of the
The tomcat9 is used by the
the Any UNM2000 8080 tomcat9 TCP
UNM2000 client for
UNM2000 client
publishing.
client publishing
server
Version: A 65
Table 8-2 Ports between the Server and the Client (Continued)
Sink Port
ing)
The nginx is a high-

The IP The IP performance HTTP and
address of address of reverse proxy server. It is
the Any the 52302 nginx TCP used for communication
UNM2000 UNM2000 between the client and the
client server UNM2000 network
management tool.
The IP The IP
The port used by the
the Any the 52001 icegridregistry TCP
icegridregistry process
UNM2000 UNM2000
server server
The IP The IP
26011 to The dynamic port of the ICE
the Any the iceboxd TCP
26299 service
UNM2000 UNM2000
client server
Table 8-3 Ports Among Server's Internal Processes
Sink Port
ing)
The IP The IP
the Any the 1433 sqlservr TCP MSSQLSERVER
UNM2000 UNM2000
server server
The IP The IP
the Any the 3306 mysqld TCP MySQL
UNM2000 UNM2000
server server
The IP The IP
The port used by the MySQL
the Any the 1521 tnslsnr TCP
database
UNM2000 UNM2000
server server
66 Version: A
Table 8-3 Ports Among Server's Internal Processes (Continued)
Sink Port
ing)
The IP The IP
52001 to The port used by the
the Any the icegridregistry TCP
52003 icegridregistry process
UNM2000 UNM2000
server server
The icegridnode process
port. According to the
deployment scenario of the
UNM2000, each node listens
The IP The IP
to one port. For the device of
52004 to the version higher than V2.
the Any the icegridnode TCP
52005 0R4, there are two nodes:
UNM2000 UNM2000
UNMnode and PAS node. It
server server
is automatically expanded
according to the number of
nodes in distributed
deployment mode.
The IP The IP
The EMS component, which
26011 to is dynamically bound with the
the Any the iceboxd TCP
26299 listening port in the port
UNM2000 UNM2000
range.
server server
The IP The IP
unmcmservice
52301 to unmcfgdatamgr
the Any the TCP Network management tool
52310 unmservicemo-
UNM2000 UNM2000
nitor
server server
The IP The IP
address of address of The MySQL service, the
the Any the 60298 mysqld TCP default listening port of the
UNM2000 UNM2000 PAS database.
server server
The IP The IP
The global FTP service of the
the Any the 10201 iceboxd TCP
PAS.
UNM2000 UNM2000
server server
Version: A 67
Table 8-4 Ports Between the Server and the OSS
Sink Port
ing)
The port of the TAO_NT_

Naming_Service service
The IP
process. Naming_Service is
address of
tao_nt_ an open-source CORBA
OSSIP Any the 3075 TCP
cosnaming naming service process
UNM2000
based on ACE/TAO and is
server
used to register the CORBA
service object.
The port of the TAO_NT_

Notify_Service service
The IP
process. Notify_Service is an
address of
tao_nt_ open-source CORBA
OSSIP Any the 3078 TCP
cosnotification notification service process
UNM2000
based on ACE/TAO and is
server
used to send CORBA events
to OSS.
The port used by the icebox
The IP
process corresponding to
address of
unmnbi_corba_cmcc_main.
OSSIP Any the 23075 iceboxd TCP
The CORBA interface
UNM2000
complying with the TMF814
server
standards.
The TL1 interface complying
The IP
with the Telecom standards
address of
3333 to (3333 for alarms, 3334 for
OSSIP Any the iceboxd TCP
3337 services, 3335 for tests, 3336
UNM2000
for resources and 3337 for
server
the unified interface).
The IP The port used by the icebox

address of process corresponding to
OSSIP Any the 9000 iceboxd TCP unmnbi_tl1_fh_main. It is a
UNM2000 FiberHome private TL1
server interface.
68 Version: A
Table 8-4 Ports Between the Server and the OSS (Continued)
Sink Port
ing)
The FTP service port. The

The IP
UNM2000 serves as the FTP
address of
server end, and the OSS
OSSIP Any the 21 to 22 FTP/SFTP TCP
takes the initiative to obtain
UNM2000
the files exported by the TL1
server
or CORBA interface.
The IP
address of The command interface of
OSSIP Any the 4000 iceboxd TCP the interface complying with
UNM2000 the Mobile standards.
server
The IP
address of The socket alarm of the
OSSIP Any the 31232 iceboxd TCP interface complying with the
UNM2000 Mobile standards.
server
The IP
The WebService port, which
address of
8001 to can be modified and
OSSIP Any the iceboxd TCP
8005 customized according to the
UNM2000
specific project.
server
The IP
address of
OSSIP Any the 161 iceboxd UDP The SNMP alarm interface.
UNM2000
server
Version: A 69
Table 8-5 The Port Between the Active and Standby Stations of the VERITAS HA System
Sink Port
ing)
The IP The IP The Veritas GCO WAC

address of address of service port of the Veritas HA
Veritas GCO
the Any the 14155 TCP system, available to the port
WAC
UNM2000 UNM2000 of the remote connector in
server server WAN cluster.
The heartbeat port of the
The IP The IP
VVR active and standby
TCP, stations of the Veritas HA
the Any the 4145 VVR
UDP system. The VVR monitors
UNM2000 UNM2000
the transmission control layer
server server
of the system via this port.
The port used by the VVR

The IP The IP vradmind process of the
address of address of Veritas HA system. The
the Any the 8199 VVR vradmind TCP vradmind processes of the
UNM2000 UNM2000 active and standby stations
server server communicate with each other
via this port.
The port used by the VVR in.

The IP The IP vxrsyncd process of the
address of address of Veritas HA system. The
the Any the 8989 vxrsyncd TCP vxrsyncd processes of the
UNM2000 UNM2000 active and standby stations
server server communicate with each other
via this port.
The IP The IP Only when the server egress

address of address of port is enabled can the VCS
TCP,
the Any the 14141 VCS cluster command "hagui" run
UDP
UNM2000 UNM2000 across the firewall: VCS
server server engine.
70 Version: A
Table 8-5 The Port Between the Active and Standby Stations of the VERITAS HA System
(Continued)
Sink Port
ing)

the Any the 14150 VCS TCP cluster command "hagui" run
UNM2000 UNM2000 across the firewall: command
server server server.
the Any the 2821 VCS TCP cluster command "hagui" run
UNM2000 UNM2000 across the firewall: security
server server cluster
Table 8-6 Ports Between the PAS Database and the Process
Sink Port
ing)
The server The server

IP address IP address The port used by the MySQL
Any 60298 mysqld TCP
of the PAS of the PAS database
database database
The server The server
IP address IP address The port used by the Oracle
Any 60298 tnslsnr TCP
of the PAS of the PAS database
database database
The IP The IP
address of address of 60201 to The port used by the
Any icegridregistry TCP
the PAS the PAS 60203 icegridregistry process
server server
The IP The IP
Any 60206 icegridnode TCP The icegridnode process port
the PAS the PAS
server server
Version: A 71
Table 8-6 Ports Between the PAS Database and the Process (Continued)
Sink Port
ing)
The IP The IP
address of address of 60310 to The port used by the PAS
Any icebox_stlpd TCP
the PAS the PAS 60510 internal service process
server server
The IP The third-
address of party
Any 10201 icebox_stlpd TCP The global FTP service
the PAS service IP
server address
72 Version: A
Appendix A Abbreviations
BML Business Management Layer
BMS Business Management System
Common Object Request Broker

CORBA
Architecture
CPU Central Processing Unit
DCC Data Communication Channel

DCN Data Communication Network
DDN Digital Data Network
EML Element Management Layer
EMS Element Management System
EPON Ethernet Passive Optical Network
GPON Gigabit-Capable Passive Optical Network
FTP File Transfer Protocol

GE Gigabit Ethernet
GNE Gate Network Element

GUI Graphic User Interface
IP Internet Protocol
International Telecommunication Union-
ITU-T
Telecommunication Standardization Sector
NE Network Element
NEL Network Element Level
NML Network Management Layer
NMS Network Management System
OLT Optical Line Terminal
ONT Optical Network Terminal
ONU Optical Network Unit
SML Service Management Layer
SMS Service Management System
TCP Transfer Control Protocol

TL1 Transaction Language 1
TMN Telecommunications Management Network
UDP User Datagram Protocol
UPS Uninterrupted Power System
Version: A 73
Product Documentation Customer Satisfaction Survey
Thank you for reading and using the product documentation provided by FiberHome. Please take a moment to
complete this survey. Your answers will help us to improve the documentation and better suit your needs. Your
responses will be confidential and given serious consideration. The personal information requested is used for
no other purposes than to respond to your feedback.
Name
Phone Number
Email Address
Company
To help us better understand your needs, please focus your answers on a single documentation or a complete
documentation set.
Documentation Name
Code and Version
Usage of the product documentation:

1. How often do you use the documentation?
□ Frequently □ Rarely □ Never □ Other (please specify)
2. When do you use the documentation?
□ in starting up a project □ in installing the product □ in daily maintenance □ in trouble
shooting □ Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
□ 100% □ 80% □ 50% □ 0% □ Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
□ Satisfied □ Unsatisfied (your advice)
5. Which documentation form do you prefer?
□ Print edition □ Electronic edition □ Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?
□ Very □ Somewhat □ Not at all (your advice)
2. How do you like the language style of the documentation?
□ Good □ Normal □ Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?
4. Is the information complete in the documentation?
□ Yes
□ No (Please specify)
5. Are the product working principles and the relevant technologies covered in the documentation sufficient for
you to get known and use the product?
□ Yes
□ No (Please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
□ Yes (Please give an example)
□ No (Please specify the reason)
7. Which parts of the documentation are you satisfied with?
8. Which parts of the documentation are you unsatisfied with?Why?
9. What is your opinion on the Figures in the documentation?
□ Beautiful □ Unbeautiful (your advice)
□ Practical □ Unpractical (your advice)
10. What is your opinion on the layout of the documentation?

□ Beautiful □ Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you compare
our documentation to them?
Product documentations from other companies:
Satisfied (please specify)
Unsatisfied (please specify)
12. Additional comments about our documentation or suggestions on how we can improve:
Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
edit@fiberhome.com

UNM2000 - Network Convergence Management System V2R7 - Product Description - A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UNM2000 - Network Convergence Management System V2R7 - Product Description - A

Uploaded by

Copyright:

Available Formats

FiberHome Telecommunication Technologies Co., Ltd.

We appreciate your business. Your satisfaction is our goal.

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 67, Guanggu Chuangye Jie, Wuhan, Hubei, China

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

All rights reserved

No part of this document (including the electronic version) may be

Initial version, corresponding to the software version

UNM2000 Network Convergence Introduces the installation flow and

UNM2000 Network Convergence Introduces the installation flow and

UNM2000 Network Convergence Introduces the operation methods, main

PON Network Traffic and Quality

This manual is intended for the following readers:

u Network planning engineers

u Network deployment engineers

Symbol Convention Description

Note Important features or operation guide.

Possible injury to persons or systems, or cause traffic

Warning May cause severe bodily injuries.

➔ Jump Jumps to another step.

The network management computer should be placed away

Use UPS power supply to avoid loss of network management

To shut down the network management computer, exit the

Do not exit the network management system when it is working

The network management computer cannot be used for

Do not delete any file in the network management system

Do not visit Internet via the network management computer.

Do not modify the network management computer’s protocol

Operation Safety Rules .........................................................................................III

1.1 Product Positioning...........................................................................2

1.1.1 Deployment of the UNM2000 in the TMN.............................2

1.2 Product Features ..............................................................................3

2 New Features .................................................................................................6

3.1 Software Architecture........................................................................9

3.2 External Interface..............................................................................9

4 System Configuration Requirements ............................................................. 11

4.1 Hardware Configuration Requirements............................................12

4.2 Software Configuration Requirements .............................................14

5 Network and Application ...............................................................................16

5.1 UNM2000 Deployment Mode ..........................................................17

5.1.1 Centralized Deployment Mode ..........................................17

5.2 Network Mode between the UNM2000 and NE................................23

5.3 Network Example ...........................................................................24

6 Basic Function of the UNM2000 ....................................................................25

6.1 Configuration Management .............................................................26

6.2 Topology Management....................................................................30

6.3 Alarm Management ........................................................................34

6.4 Event Management.........................................................................40

6.6 Security Management .....................................................................44

6.7 Resource Management...................................................................50

6.8 Operation and Maintenance Management .......................................53

7.1 Management Capacity ....................................................................59

7.2 Performance Specification ..............................................................59

8 External Service Ports ..................................................................................63

Appendix A Abbreviations ............................................................................73

The UNM2000, developed by FiberHome, is used to manage the network devices

1.1 Product Positioning

The UNM2000, a system managing the FiberHome communication devices, is the

1.1.1 Deployment of the UNM2000 in the TMN

The TMN provides hierarchical network architecture and standard network

Figure 1-1 Deployment of the UNM2000 in the TMN

1.1.2 Manageable Device Types