UNM2000 V2R11 - Product Description

UNM2000
Network Convergence
Management System V2R11
Product Description
Version: B
Code: MN000004542
FiberHome Telecommunication Technologies Co., Ltd.
May 2020
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.fiberhome.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 V2R11.
Updated version, corresponding to the software version
B
UNM2000 V2R11SPC0200.
Related Documentation
Document Main Content Phase to Use
Introduces the product positioning,
Network
Product Description features, basic functions, network and
planning
application, and technical specification.
Introduces function overview and

coverage of the current version, and Network
Release Notes
function changes against the previous planning
version.
Introduces installation precautions /
Windows-based Installation Network
standards, and how to install and deploy
Guide deployment
the product in the Windows system.
Introduces installation precautions /

standards, and how to install and deploy Network
Linux-based Installation Guide
the product in the Linux system (SUSE deployment
or CentOS).
Introduces the operation methods, main

Operation Guide (Public GUIs, windows, menus and precautions Network
Functions) for management functions of the maintenance
product.
Introduces the installation methods, Network

Northbound Interface (TL1) User interface definitions and function management
Manual descriptions of the TL1 northbound and
interface. maintenance
I
Document Main Content Phase to Use
PON Network Traffic and Quality
Introduces the installation flow and Network
Analysis System Installation
methods of the product. deployment
Guide
PON Network Traffic and Quality Introduces the operation methods, main
Network
Analysis System Operation GUIs and indicators of the management
maintenance
Guide functions.
Intended Readers
This manual is intended for the following readers:
u Network planning engineers
u Network monitoring engineers
u On-site maintenance engineers
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
Contents
Preface...................................................................................................................I
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 Version Introduction ........................................................................................6
3 System Architecture........................................................................................7
3.1 Software Architecture........................................................................8
3.2 External Interface..............................................................................8
4 System Configuration Requirements .............................................................10
4.1 Hardware Configuration Requirements............................................ 11
4.2 Software Configuration Requirements .............................................13
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 ........................................................................37
6.4 Event Management.........................................................................43
6.5 Performance Management..............................................................44

6.6 Security Management .....................................................................47
6.7 Resource Management...................................................................53
6.8 Operation and Maintenance Management .......................................55
7 Technical Specifications................................................................................59
7.1 Management Capacity ....................................................................60
7.2 Performance Specification ..............................................................60
7.3 Standards.......................................................................................62
8 External Service Ports ..................................................................................63
Appendix A Abbreviations ............................................................................71

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

so as to improve the network maintenance efficiency and lower the maintenance
cost.
Product Positioning
Product Features
Version: B 1
UNM2000 Network Convergence Management System V2R11 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 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 V2R11.
2 Version: B
1 Overview
Table 1-1 Manageable Devices
Type Device Model
AN5516-04, AN5516-06, AN5116-06B, AN6000-2, AN6000-7, AN6000-15,

OLT
AN6000-17 and 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
AN5006-20, AN5006-30, AN5220, and AN5116-06B / AN5516-06 (PON / MSAN
MSAN
common platform)
EDFA HA1H11-19-16X, HA1H11-19-8X and HA9431-19-32X
u SX800: S4800-28T-GF, S4800-28T-GF-PE, S4820-10T-GF-PE, S4820-10T-

GF, S4820-28T-GF-PE, S5800-28F-S(-B), S5800-28F-S(-C), S5800-28T-S-E,
S5800-28T-S-PE(-C), S5800-28T-S-PE(-B), S5800-52T-S-PE(-B), S5800-52T-
Switch S-PE(-C) and S3652-PE
u S2200: S2208ME
u IPRAN: CiTRANS R820-4
u Others: S2208G-PAF
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.
Version: B 3
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.
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 operating

systems based on different databases, compatible with multiple OSs. The
UNM2000 can provide not only high-end solutions for large-scale networks, but also
low-cost solutions for small and medium-sized networks.
u The UNM2000 can run in the Windows, SUSE Linux, CentOS Linux or Solaris
operating system. The client and server performance of the UNM2000 is
irrelevant to the operating system.
4 Version: B
1 Overview
u The UNM2000 supports the MySQL, Oracle and SQLServer databases to meet
different requirements for users.
Standard and Unified Interface
The UNM2000 provides standard and unified southbound and northbound

interfaces, which completely meet the requirements for the industry mainstream
OSS integration.
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: B 5
2 Version Introduction
The UNM2000 V2R11 has the following new features:
u Manages the AN6000 series devices via a Webservice interface.
u Exports backup configuration data and collected performance data via SFTP
(not supported by the AN6000 series devices).
u Collects and exports data on ONU health, DBA service bandwidth and ONU
WAN connection services.
u Cuts over PON services intelligently.
u Updates the states of topology links for ONU services in real time.
u Upgrades and backs up device software via FTP.
u Displays the states of physical connections for OLTs automatically.
u Optimizes configuration migration related to ONU Layer 3 rate limit template

binding, ONU port rate limit template binding and ONU QinQ rate limits.
u Manages users of a built-in FTP server.
u Manages and maintains EDFA devices.
6 Version: B
3 System Architecture
This chapter introduces the software architecture and external ports of the
UNM2000.
Software Architecture
External Interface
Version: B 7
3.1 Software Architecture
The UNM2000 is a service-based and modularized network management system

running on a cloud platform. It comprises multiple logical modules such as basic
platform, device management, and intelligent operation & maintenance, and can be
deployed in a flexible and modularized manner according to customers’
requirements. Figure 3-1 shows the software architecture of the UNM2000.
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.
8 Version: B
3 System Architecture
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.
Version: B 9
4 System Configuration Requirements
This chapter introduces the hardware and software configuration requirements of

the UNM2000 server and client.
Hardware Configuration Requirements
Software Configuration Requirements
10 Version: B
4.1 Hardware Configuration Requirements
This section introduces the hardware configuration requirements of the UNM2000

server and client.
Hardware Configuration Requirements of the Server
The hardware configuration requirements of the UNM2000 server vary with the
network scale. For detailed requirements, see Table 4-1.
Table 4-1 Hardware Configuration Requirements of the Server
CPU Hard
CPU
Network Scale Clock Memory Disk Hard Disk Format Network Card
Quantity
Rate Space
The disks on which the

database and the
5000 NEs (MDU
10-core / UNM2000 will be installed
+OLT), 1000000 8 256G 4 TB 4 × GE ports
2.5 GHz (disks C and D by default
ONUs
respectively) should be in
NTFS format.
database and the
5000 NEs (MDU
+OLT), 600000 4 128G 2 TB 4 × GE ports
ONUs
NTFS format.
database and the
3000 NEs (MDU
+OLT), 200000 2 64G 2 TB 4 × GE ports
ONUs
NTFS format.
database and the
1000 NEs (MDU
8-core / 2. UNM2000 will be installed
+OLT), 100000 2 32G 2 TB 4 × GE ports
5 GHz (disks C and D by default
ONUs
NTFS format.
Version: B 11
Table 4-1 Hardware Configuration Requirements of the Server (Continued)
CPU Hard
CPU
Network Scale Clock Memory Disk Hard Disk Format Network Card
Quantity
Rate Space

database and the
500 NEs (MDU
6-core / 2. UNM2000 will be installed
+OLT), 50000 2 16G 1 TB 2 × GE ports
5 GHz (disks C and D by default
ONUs
NTFS format.
database and the
300 NEs (MDU
+OLT), 30000 1 16G 600 GB 2 × GE ports
3GHz (disks C and D by default
ONUs
NTFS format.
12 Version: B
Hardware Configuration Requirements of the Client
Table 4-2 shows the hardware configuration requirements of the UNM2000 client.
Table 4-2 Hardware Configuration Requirements of the Client
Hard
CPU Clock CPU Graphics
Network Scale Memory Disk Hard Disk Format
Rate Quantity Card
Space
Equivalent to more The disk on which the

Intel XeonE5-
than 1000 OLTs that UNM2000 will be 1 GB
2637V2 (4-
are fully configured 1 16G 1 × 2 TB installed (disk D by discrete
core), 3.5
and connected with default) should be in graphics
GHz
ONUs NTFS format.
The disk on which the
Equivalent to 500 to
Intel i3-4130 UNM2000 will be 1 GB
1000 OLTs that are
(2-core), 3.4 1 8G 1 × 1 TB installed (disk D by discrete
fully configured and
GHz default) should be in graphics
connected with ONUs
NTFS format.
Intel Core i5- The disk on which the
Equivalent to 100 to nVIDIA
4200U (1.6G- UNM2000 will be
500 OLTs that are fully 1 × 500 GT720M 1
2.6G/3M) (2- 1 8G installed (disk D by
configured and GB GB discrete
core), 3.4 default) should be in
connected with ONUs graphics
GHz NTFS format.
Intel Corei5- The disk on which the
Equivalent to less than Intel HD
4200U (1.6G- UNM2000 will be
100 OLTs that are fully 1 × 500 4400
2.6G/3M) (2- 1 4G installed (disk D by
configured and GB integrated
core), 3.4 default) should be in
connected with ONUs graphics
GHz NTFS format.
4.2 Software Configuration Requirements
This section introduces the software configuration requirements of the UNM2000

server and client.
Version: B 13
Software Configuration Requirements of the Server
Table 4-3 Software Configuration Requirements of the Server
Configuration Item Requirement
Windows operating system:

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.
u Windows Server 2012 R2 Standard (64-bit)
Operating system
SUSE Linux operating system:
u SUSE Linux Enterprise 11 SP3 (64-bit)
u SUSE Linux Enterprise 12 SP5 (64-bit)
Solaris 11 (64-bit)
CentOS Linux operating system: CentOS Linux release 8.2.2004

(core)
SQL Server 2008 R2

Note: The SQL server database only supports the Windows operating
system.
u MySQL 5.7.18
Note: The MySQL 5.7.18 database only supports the SUSE
Linux Enterprise 11 system.
Database u MySQL 5.7.30
u MySQL 8.0.22
Note: The MySQL 8.0.22 database only supports the CentOS
Linux release 8.2.2004 system.
Oracle 11g
Note: The Oracle database only supports the SUSE Linux Enterprise
12 system.
JRE JDK 1.8.201

Internet protocol TCP/IPv4 and TCP/IPv6
Software Configuration Requirements of the Client
Table 4-4 Software Configuration Requirements of the Client
u Windows 7, Windows 8 or Windows 10

Operating system
u Windows Server 2008 or Windows Server 2012
JRE JDK 1.8.201
Internet protocol TCP/IPv4 and TCP/IPv6
14 Version: B
Table 4-4 Software Configuration Requirements of the Client (Continued)
Browser Chrome 70.0 or later versionsNote 1

Note 1: It is applicable to the scenario where the UNM2000 is accessed via a Web browser.
Version: B 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: B
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: B 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: B
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: B 19
Figure 5-3 Local Centralized Deployment Mode of Cluster Disaster Tolerance
20 Version: B
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: B 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: B
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: B 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: B
6 Basic Function of the UNM2000
This chapter 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: B 25
6.1 Configuration Management
The UNM2000 provides the configuration management function for devices in the
entire network. You can perform various configurations on devices using the
UNM2000.
Full Service Configuration
u The broadband access device 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 The UNM2000 provides a universal management GUI for configuring services

and querying status of switches.
u For system objects, the UNM2000 provides shortcuts for service configurations,
and integrates previous individual Grid configuration GUIs into a main GUI for
configuration operations. That is, all configuration commands for system
objects are integrated into a service configuration management GUI where you
can configure services directly.
u The UNM2000 provides service configuration, ONU deauthorization, ONU

replacement, ONU activation / deactivation by the shortcut menu of the ONU
list.
u The UNM2000 provides the Web configuration access to call a third-party Web
network management system to manage the S2208G-PAF switches.
Global Template and Global Configuration
u The UNM2000 provides the global template and global configuration functions.
If multiple NEs have the same or similar configuration, you can bind a global
template to these NEs or deliver the global configuration to these NEs. In this
way, configuration efficiency is improved.
u The global template and global configuration are independent of NE status.

NEs can be configured even if they are offline.
u The UNM2000 can upgrade ONUs in a batch manner.
26 Version: B
Hand-in-Hand Topology Management
u The UNM2000 can manage association of ONUs with double MAC addresses.
u The UNM2000 can display the hand-in-hand topology in real time and provide
the protection information of associated ONUs.
SNMP Parameter Template Management
The UNM2000 provides the SNMP parameter template management function for
the SNMP v1, v2C and v3 versions. You can create, modify or delete templates and
bind NEs with templates.
NE Communication Route Management
The UNM2000 provides management of manager programs and partition policies.

You can create, delete or modify manager programs and partition polices.
Version: B 27
Pre-configuration
The UNM2000 supports the pre-configuration function. Before connecting a device

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

and download configurations of specified NEs so as to synchronize NE
configurations.
Configuring NEs in Batches
The UNM2000 supports configuring NEs in batches, including calibrating time,

synchronizing alarms and saving configurations to Flash in batches.
Migrating PON Configurations
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 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, traffic policies bound to ONU ports and ONU attribute configuration.
Checking Configurations
The UNM2000 provides configuration data check. During service configuration, the
UNM2000 will automatically verify the validity of 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 errors at a later stage, and enhances the
configuration efficiency.
Version: B 29
Configuration Backup
The UNM2000 provides configuration backup. You can set different export tasks to
export configuration files, NE software, card software or MAC addresses of PON
ports.
Exported configuration files will be saved to file folders named by export time,
convenient for you to find and view desired files. 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 NEs.
Note:
Configurations cannot be imported into switches in a batch manner by

setting a configuration upload task on the UNM2000.
6.2 Topology Management
Topology management displays the status of connections between managed NEs in

a topology. You can understand the conditions of the entire network and monitor the
operation status in real time by browsing topology views.
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.
30 Version: B
4 Object tree pane: Displays the hierarchical relationship among objects in

the network in a tree-like structure. You can click a node on the object tree
to locate it in the physical topology view. Additionally, you can adjust the
sequence of objects on the object tree. When you log into the UNM2000
next time, the system displays objects in the sequence adjusted last time.
4 Physical topology view: Supports automatic physical topology discovery,

automatically updating and displaying the physical connections between
NEs.
4 You can set different background images for logical domains in the main
topology.
u Sub-topology view: Graphically displays the topology between OLT and ONU.
Version: B 31
u Bird-eye view: Displays the global view of the entire network.
When the network scale is too large and the current view cannot cover all the
network details, you can use Bird-eye view to have an overall view of the
entire network. The purplish red frame in the Bird-eye view pane shows the
displayed area in the current view. You can drag the frame using the mouse to
adjust the displayed area.
32 Version: B
u Hot region view: The UNM2000 automatically generates a topology view of the
hot region according to user-defined settings. In this way, you can manage and
monitor the important devices by groups.
u Topology filtering: 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 settings take effect for the current user and
maintain valid when the user logs in next time. If a user sets the filtering
criteria on multiple clients simultaneously, only the latest filtering settings
will take effect when he or she accesses the main topology next time.
4 The main topology is filtered and displayed according to your filtering

settings. The objects matching the filtering criteria are displayed while
those not matching the filtering criteria are not displayed.
u Service topology view: Graphically displays the end-to-end service traffic of

ONUs and differentiates path statuses by different colors.
Version: B 33
Topology Alarm and Status Display
The UNM2000 uses different colors and icons to represent logical domains and NE
alarms / statuses, as shown in and .
Figure 6-1 Example of the Logical Domain Icon
34 Version: B
Figure 6-2 Example of the NE Icon
u Different NE node icons represent different device types.
u The ground color of a topology node icon indicates the polling status (normal,
unknown, communication interrupted, etc.) and alarm level of the NE. The
displayed ground color of an icon represents the highest level of all alarms on
the NE. describes the alarm colors.
Table 6-1 Description of Alarm Color
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 whether there is an unconfirmed alarm on the

monitored object. The border color represents the highest level of all
unconfirmed alarms on the object.
u The icon at the top right corner of a monitored object indicates the latest special
alarm according to the definition. For the definition of special alarms, you can
view it through Legend on the toolbar of the topology view.
u A logical domain icon displays the color of the highest-level alarm and the icon
of the latest special alarm on the NE nodes in the logical domain. The
UNM2000 supports manually dragging or sorting NEs in a logical domain,
which is convenient for finding desired NEs.
Version: B 35
Fiber Cut Alarm and Status Display
If the fiber (trunk fiber or branch fiber) between the PON port and ONU is broken,
the UNM2000 will display the PON_LINK_LOSS or LINK_LOSS alarm, and the link
in the sub-topology view will turn red.
36 Version: B
Access Method of Integrated Management
The UNM2000 provides access to NE management functions in the topology.

During the network maintenance, you can perform the Ping, physical configuration
inspection and alarm viewing operations on a device directly in 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.
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.
Version: B 37
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.
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.
38 Version: B
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.
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.
Version: B 39
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.
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.
40 Version: B
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.
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.
Version: B 41
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.
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.
42 Version: B
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.
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.
Version: B 43
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.
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.
44 Version: B
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.
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.
Version: B 45
Ranking Statistics (Top N)
The UNM2000 supports displaying the device PON traffic top ranking and device
health top ranking in charts.
46 Version: B
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.
Version: B 47
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.
48 Version: B
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.
Version: B 49
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.
50 Version: B
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.
Version: B 51
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.
52 Version: B
6.7 Resource Management
The UNM2000 provides the resource statistics and information import functions.
Detecting Physical Configuration
The UNM2000 provides physical configuration detection. You can detect the
incremental or full physical configurations of access NEs and synchronize the
configurations 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 and delete them in a batch manner.
u The UNM2000 supports importing a template to query ONU information in a

batch manner.
Importing the ODN EMS Information
The UNM2000 supports importing the local ODN EMS information.
Marking an NE
The UNM2000 enables you to mark NEs and query marks.
Version: B 53
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
u ONU Resource Statistics
Physical Resource u ONU Port Resource Statistics
Statistics u MSAN Port Resource Statistics
u Area Statistics
u Equivalent NE Statistics
u Switch Port Resource Statistics
u Custom Statistics
u ONU User Statistics
u Local VLAN Statistics
u NE MGC Service Statistics
u Device Type Statistics
u PON Device Capability Statistics
u ONU WAN Service Statistics
Other Type 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
u GPON Service Bandwidth Statistics
54 Version: B
Statistics Type Statistics Item
u NE Resource Statistics Export

u Card Resource Statistics Export
u Port Resource Statistics Export
u ONU Resource Statistics Export
Physical Resource
u ONU Port Resource Statistics Export
Statistics Export
u MSAN Port Resource Statistics Export
u Area Statistics Export
u Switch Port Resource Statistics Export
u Custom 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
u GPON Service Bandwidth Statistics Export
Managing the NE Maintenance Information
The UNM2000 provides management of NE maintenance information and supports

managing NEs' physical location information and maintainer 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 fault diagnosis and location functions.
Automatic Inspection
u Inspection template: Supports creating, modifying, deleting and viewing

inspection templates.
Version: B 55
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 results and performing

incremental inspection on the inspection items that fail the inspection or have
command exceptions.
u Inspection report: Supports exporting inspection reports in Excel format

automatically or manually.
PON Traffic Analysis
The PON traffic analysis function features visualized data analysis, intelligent
warning and alarm management and precise capacity analysis. It helps you
comprehensively understand the service traffic and bandwidth usage of the PON
network, gather statistics of and analyze traffic growth trend and resource utilization
efficiency of the PON network, and effectively predict the necessity to expand the
capacity of network resources or balance and optimize resource allocation so as to
prevent network congestion and guarantee the transfer quality of various services.
u Provides the topology of the entire network, where threshold-crossing NEs are
highlighted and the corresponding information is provided. In this way, network
operators can directly view the traffic status of the entire network.
u Supports dynamically displaying traffic distribution of each area in a big-screen

GIS map. You can zoom in or out a focused area to display its multi-level traffic
information. In this way, traffic status is visualized.
u Supports analyzing the traffic of OLT uplink ports, OLT PON ports, ONU PON
ports and links.
56 Version: B
u Supports displaying traffic trends of OLT uplink ports, OLT PON ports and ONU
PON ports in graphs.
u Supports analyzing the traffic of ports and hot regions.
u Supports ranking Top N OLT uplink ports, OLT PON ports and ONU PON ports
by traffic.
u Supports collecting statistics of uplink / downlink CRC errors of OLT uplink

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

bandwidth utilization reports for OLT uplink ports, OLT PON ports and ONU
PON ports. This helps you 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.
u Supports custom token removing / adding rules. Monitors performance

indicators in the entire network, adds tokens to threshold-crossing objects, and
sends threshold-crossing alarms to a third-party. If an object with a threshold-
crossing token resumes normal, you can remove its token.
u Provides management of performance threshold-crossing alarms and supports

pushing traffic threshold-crossing reports to specified users.
Resource Analysis
The UNM2000 supports collecting statistics of physical resource online ratio and
network resource information by area.
u Physical resource statistics:
Version: B 57
Table 6-2 Statistics 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 online ratio

ONU resource
Total number of HGUs
Total number of SFUs
u Network resource statistics: Collects statistics of 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 statistics.
Fault Diagnosis and Location
The UNM2000 supports intelligent fault location. You can quickly locate a fault,
improving the fault isolation efficiency.
u Detection template: You can detect network access failures, IPTV program
interruption faults, WIFI service faults and voice service faults using system
default templates or self-defined templates.
u Detection and diagnosis: You can select an appropriate detection template

according to the fault type. The UNM2000 performs fault detection and
provides a fault diagnosis report.
u Diagnosis report: You can view the detection result and manually export an
intelligent fault location report in Excel format.
58 Version: B
7 Technical Specifications
This chapter introduces the technical specifications of the UNM2000.
Management Capacity
Performance Specification
Standards
Version: B 59
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 admitted 50
Number of object groups admitted 100
Number of operation groups admitted 255
System homepage delay ≤ 10 seconds
Response time delay of a single operation ≤ 2 seconds
Response time delay of batch operations ≤ 5 seconds
Report generation time delay ≤ 8 seconds
Alarm throughput ≥ 1000 entries / second
Alarm response delay ≤ 10 seconds
u Number of records ≤ 10000: 2s
u 10000 < number of records ≤ 100000:
Alarm query delay
8s
u 100000 ≤ number of records: 20s
Alarm handling capability ≥ 100 entries / second
Performance statistics delay < 2 minutes
Performance response delay < 10s
60 Version: B
7 Technical Specifications
Table 7-1 Performance Specification List (Continued)
Item Specification
u Number of records ≤ 10000: 2s

u 10000 < number of records ≤ 100000:
Performance query delay
8s
u 100000 ≤ number of records: 20s
Maximum number of performance objects to be
10000
counted
Configuration synchronization time delay < 2 minutes
Data export time delay ≤ 2 minutes/100M
Configuration storage duration Long-term operation
Current alarm storage capacity ≥ 500 000

Historical alarm storage capacity ≥ entries over three months
5-minute historical performance storage capacity ≥ entries over one month
15-min historical performance storage capacity ≥ entries over six months
60-min historical performance storage capacity ≥ entries over one year
24-hour historical performance storage capacity ≥ entries over one year
Storage capacity of operation logs ≥ entries over six months

Storage capacity of monitoring data ≥ entries over six months
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.
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.
Version: B 61
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.
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: B
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
Process
Source IP Source Destination Sink Port
of the Sink Protocol Port Description
Address Port IP Address (Listening)
Port
The FTP server service port,
The IP providing the FTP file transfer
NE IP address of the service. It is used to upgrade the
Any 20 FTP TCP
address UNM2000 NE software, back up the NE
server data and upload the NE
configuration.
The FTP server service port,

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

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

The IP
The IP address maintenance channel of the
address of the
of the UNM2000 Any 22 SSH TCP EMS server on Linux OS.
UNM2000
client The UNM2000 does not use
server
this port itself.
64 Version: B
Table 8-2 Ports between the Server and the Client (Continued)
Process
Sink Port
Source IP Source Destination of the
Address Port IP Address Sink
ing)
Port
The port used by Windows
OS remote desktop protocol
(RDP). The Windows
The IP provides the remote desktop
The IP address
address of the service via this port. It is
of the UNM2000 Any 3389 RDP TCP
UNM2000 enabled only when the
client
server remote desktop is used to
operate the Windows server.
The UNM2000 does not use
the port.
The IP
address of the The tomcat9 monitoring port
The IP address
UNM2000 The tomcat9 is used by the
of the UNM2000 Any 8080 tomcat9 TCP
client UNM2000 client for
client
publishing publishing.
server
The nginx is a high-
performance HTTP and
The IP
The IP address reverse proxy server. It is
address of the
of the UNM2000 Any 52302 nginx TCP used for communication
UNM2000
client between the client and the
server
UNM2000 network
management tool.
The IP
The IP address
address of the icegri- The port used by the
of the UNM2000 Any 52001 TCP
UNM2000 dregistry icegridregistry process
server
server
The IP
The IP address
address of the 26011 to The dynamic port of the ICE
of the UNM2000 Any iceboxd TCP
UNM2000 26299 service
client
server
Version: B 65
Table 8-3 Ports Among Server's Internal Processes
Sink Port Process of

Source IP Source Destination IP
(Monitor- the Sink Protocol Port Description
Address Port Address
ing) Port
The IP address The IP address
of the UNM2000 Any of the UNM2000 1433 sqlservr TCP MSSQLSERVER
server server
of the UNM2000 Any of the UNM2000 3306 mysqld TCP MySQL
server server
The port used by the
of the UNM2000 Any of the UNM2000 1521 tnslsnr TCP
MySQL database
server server
52001 to icegridreg- The port used by the
of the UNM2000 Any of the UNM2000 TCP
52003 istry icegridregistry process
server server
The icegridnode
process port. According
to the deployment
scenario of the
UNM2000, each node
listens to one port. For
The IP address The IP address the device of the version
52004 to
of the UNM2000 Any of the UNM2000 icegridnode TCP higher than V2.0R4,
52005
server server there are two nodes:
UNMnode and PAS
node. It is automatically
expanded according to
the number of nodes in
distributed deployment
mode.
The EMS component,
26011 to which is dynamically
of the UNM2000 Any of the UNM2000 iceboxd TCP
26299 bound with the listening
server server
port in the port range.
unmcmser-
vice
52301 to unmcfgda- Network management
of the UNM2000 Any of the UNM2000 TCP
52310 tamgr tool
server server
unmservi-
cemonitor
66 Version: B
Table 8-3 Ports Among Server's Internal Processes (Continued)

ing) Port
The IP address The IP address The MySQL service, the
of the UNM2000 Any of the UNM2000 60298 mysqld TCP default listening port of
server server the PAS database.
The global FTP service
of the UNM2000 Any of the UNM2000 10201 iceboxd TCP
of the PAS.
server server
Table 8-4 Ports Between the Server and the OSS
Sink Port
Source IP Source Destination IP Process of
Address Port Address the Sink Port
ing)
The port of the TAO_NT_

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

Notify_Service service
The IP address process. Notify_Service is an
tao_nt_
of the open-source CORBA
OSSIP Any 3078 cosnotifica- TCP
UNM2000 notification service process
tion
server based on ACE/TAO and is
used to send CORBA events
to OSS.
The port used by the icebox
The IP address process corresponding to
of the unmnbi_corba_cmcc_main.
OSSIP Any 23075 iceboxd TCP
UNM2000 The CORBA interface
server complying with the TMF814
standards.
Version: B 67
Table 8-4 Ports Between the Server and the OSS (Continued)
Sink Port
Source IP Source Destination IP Process of
Address Port Address the Sink Port
ing)
The TL1 interface complying

The IP address with the Telecom standards
of the 3333 to (3333 for alarms, 3334 for
OSSIP Any iceboxd TCP
UNM2000 3337 services, 3335 for tests,
server 3336 for resources and 3337
for the unified interface).
The port used by the icebox

The IP address
process corresponding to
of the
OSSIP Any 9000 iceboxd TCP unmnbi_tl1_fh_main. It is a
UNM2000
FiberHome private TL1
server
interface.
The FTP service port. The
The IP address UNM2000 serves as the FTP
of the server end, and the OSS
OSSIP Any 21 to 22 FTP/SFTP TCP
UNM2000 takes the initiative to obtain
server the files exported by the TL1
or CORBA interface.
The IP address
The command interface of
of the
OSSIP Any 4000 iceboxd TCP the interface complying with
UNM2000
the Mobile standards.
server
The IP address
The socket alarm of the
of the
OSSIP Any 31232 iceboxd TCP interface complying with the
UNM2000
Mobile standards.
server
The IP address The WebService port, which
of the 8001 to can be modified and
OSSIP Any iceboxd TCP
UNM2000 8005 customized according to the
server specific project.
The IP address
of the
OSSIP Any 161 iceboxd UDP The SNMP alarm interface.
UNM2000
server
68 Version: B
Table 8-5 The Port Between the Active and Standby Stations of the VERITAS HA System
Sink Port Process

Source IP Source Destination
(Monitor- of the Protocol Port Description
Address Port IP Address
ing) Sink Port
The Veritas GCO WAC service
The IP address The IP
Veritas port of the Veritas HA system,
of the address of
Any 14155 GCO TCP available to the port of the
UNM2000 the UNM2000
WAC remote connector in WAN
server server
cluster.
The heartbeat port of the VVR
The IP address The IP active and standby stations of
of the address of the Veritas HA system. The
Any 4145 VVR TCP, UDP
UNM2000 the UNM2000 VVR monitors the transmission
server server control layer of the system via
this port.
The port used by the VVR

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

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

of the address of port is enabled can the VCS
Any 14141 VCS TCP, UDP
UNM2000 the UNM2000 cluster command "hagui" run
server server across the firewall: VCS engine.
Only when the server egress

port is enabled can the VCS
of the address of
Any 14150 VCS TCP cluster command "hagui" run
UNM2000 the UNM2000
across the firewall: command
server server
server.
Only when the server egress
port is enabled can the VCS
of the address of
Any 2821 VCS TCP cluster command "hagui" run
UNM2000 the UNM2000
across the firewall: security
server server
cluster
Version: B 69
Table 8-6 Ports Between the PAS Database and the Process

ing) Port
The server IP The server IP The port used by
address of the Any address of the PAS 60298 mysqld TCP the MySQL
PAS database database database
The server IP The server IP The port used by
address of the Any address of the PAS 60298 tnslsnr TCP the Oracle
PAS database database database
The IP address The port used by
The IP address of the 60201 to icegridreg-
of the PAS Any TCP the icegridregistry
PAS server 60203 istry
server process
The IP address
The IP address of the The icegridnode
of the PAS Any 60206 icegridnode TCP
PAS server process port
server
The IP address The port used by
The IP address of the 60310 to icebox_
of the PAS Any TCP the PAS internal
PAS server 60510 stlpd
server service process
The IP address
The third-party icebox_ The global FTP
of the PAS Any 10201 TCP
service IP address stlpd service
server
70 Version: B
Appendix A Abbreviations
BML Business Management Layer
BMS Business Management System
CORBA Common Object Request Broker 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 Gateway Network Element
GUI Graphic User Interface
IP Internet Protocol
International Telecommunication Union-Telecommunication
ITU-T
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: B 71
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
[email protected]

UNM2000 V2R11 - Product Description

Uploaded by

Copyright:

Available Formats

UNM2000 V2R11 - Product Description

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 V2R11 - Product Description

Uploaded by

Copyright:

Available Formats

UNM2000

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

Introduces function overview and

Introduces installation precautions /

Introduces the operation methods, main

Introduces the installation methods, Network

This manual is intended for the following readers:

u Network planning engineers

u Network monitoring engineers

u On-site maintenance 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.

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

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

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

2 Version Introduction ........................................................................................6

3.1 Software Architecture........................................................................8

3.2 External Interface..............................................................................8

4 System Configuration Requirements .............................................................10

4.1 Hardware Configuration Requirements............................................ 11

4.2 Software Configuration Requirements .............................................13

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 ........................................................................37

6.4 Event Management.........................................................................43

6.5 Performance Management..............................................................44

6.7 Resource Management...................................................................53

6.8 Operation and Maintenance Management .......................................55

7.1 Management Capacity ....................................................................60

7.2 Performance Specification ..............................................................60

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

Appendix A Abbreviations ............................................................................71

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

Table 1-1 Manageable Devices

Type Device Model

AN5516-04, AN5516-06, AN5116-06B, AN6000-2, AN6000-7, AN6000-15,

EDFA HA1H11-19-16X, HA1H11-19-8X and HA9431-19-32X