Network Convergence Management System V2.0R4 Product Description

UNM2000
Network Convergence
Management System V2.0R4
Product Description
Version: A
Code: MN000003315
FiberHome Telecommunication Technologies Co., Ltd.
August 2017
Thank you for choosing our products.
We appreciate your business. Your satisfaction is our goal.

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

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

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

reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface
Version
Version Description
A Initial version, corresponding to V2.0R4.
Related Documentation
Document Main Content Phase to Use
Introduces the functions, application
UNM2000 Network
scenarios and technical specifications
Convergence Management Network Planning
of the UNM2000 Network
System Product Description
Convergence Management System.
UNM2000 Network Introduces how to install the

Convergence Management UNM2000 Network Convergence Network
System Installation Guide Management System on the Windows deployment
(Based on Windows) operating system.
UNM2000 Network Introduces how to install the

Convergence Management UNM2000 Network Convergence Network
System Installation Guide Management System on the SUSE deployment
(Based on SUSELinux) Linux operating system.
UNM2000 Network Introduces the operation guidelines of

Network
Convergence Management the UNM2000 Network Convergence
maintenance
System Operation Guide Management System.
Network
UNM2000 Network The meaning and usage constraints of
maintenance /
Convergence Management shortcut menus and buttons in the
service
System GUI Reference menus and windows
deployment
Intended Readers
This manual is intended for the following readers:
u Network planning engineers
u Network monitoring engineers
u On-site maintenance engineers
I
Terminology Conventions
Terminology Convention
FiberHome UNM2000 Network Convergence Management
UNM2000
System
Symbol Conventions
Symbol Convention Description
Note Important features or operation guide.
Possible injury to persons or systems, or cause traffic

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

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

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

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

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

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

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

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

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

1.1.2 Manageable Device Types..................................................2
1.2 Product Feature ................................................................................3
1.3 System Configuration Requirements .................................................4
1.3.1 Hardware Configuration Requirements................................5

1.3.2 Software Configuration Requirements .................................7
2 Network and Application .................................................................................9
2.1 UNM2000 Deployment Mode ..........................................................10
2.1.1 Centralized Deployment Mode ..........................................10

2.1.2 Distributed Deployment Mode ........................................... 11
2.1.3 Cluster Disaster Tolerance Centralized Deployment Mode. 11
2.1.4 Cluster Disaster Tolerance Distributed Deployment Mode..13
2.2 Network Mode between the UNM2000 and NE................................15
2.3 Network Example ...........................................................................16
3 Basic Function of the UNM2000 ....................................................................17
3.1 Configuration Management .............................................................18
3.2 Topology Management....................................................................19
3.3 Alarm Management ........................................................................21
3.4 Event Management.........................................................................26
3.5 Performance Management..............................................................26
3.6 Security Management .....................................................................28
4 System Architecture......................................................................................34
4.1 Software Architecture......................................................................35

4.2 External Interface............................................................................36
5 Technical Specifications................................................................................37
5.1 Management Capacity ....................................................................38
5.2 Performance Specifications ............................................................38
5.3 External Server Port........................................................................39
5.4 Standards.......................................................................................40
Appendix A Abbreviations ............................................................................42

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

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

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

interfaces. It is composed of the business management layer (BML), the network
management layer (NML), and the element management layer (EML). This type of
composition is called the network management architecture of the TMN.
The UNM2000 locates 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.
2 Version: A
1 Overview
Table 1-1 Devices Managed by the UNM2000
Type Device Model
OLT AN5116-06B, AN5116-02, AN5116-06B, AN5516-04, AN5516-04B and AN5516-06

AN5506-04-FG, AN5506–04–FAT, AN5006-04-A, AN5006-04-B, AN5006-04-F,
ONU AN5506-01-A, AN5506-01-B, AN5006-01-A, AN5006-01-B, AN5646T and
AN5656T
MSAN AN5006–20, AN5006–30, AN5006–15, AN5006–16 and AN5220
1.2 Product Feature
The UNM2000 improves the management capability, scalability and usability to

provide a new generation of the client-oriented network management system.
Strong 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 four deployment modes: the single-server centralized

deployment mode, single-system distributed deployment mode, cluster disaster
tolerance centralized deployment mode and cluster disaster tolerance
distributed deployment mode.
u The UNM2000 improves the disaster tolerance by the cluster disaster tolerance
centralized deployment and the cluster disaster tolerance distributed
deployment, so as to provide users with a stable and reliable network
management system.
u The UNM2000 flexibly controls the functions and management capability using
the License function, so as to meet various requirements of subscribers.
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.
Version: A 3
u The functional modules are removable and assemble, which meets the
customization requirement for users.
u The loose coupling between functional modules ensures users to upgrade and
maintain modules independently.
User-friendliness
The UNM2000 provides a new generation of the client-oriented network

management system.
u The UNM2000 provides completely new user experience using the Web login
mode.
u The UNM2000 keeps the consistent GUI style for each device using
modularized design.
Compatible with Multiple Operation 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 operate on the Windows, SUSE Linux and Solaris systems.
The client end and server end performance of the UNM2000 is irrelevant to the
operating system.
u The UNM2000 supports the MySQL and SQLServer databases to meet

different requirements for users.
1.3 System Configuration Requirements
The following introduces the hardware and software configuration requirements for
the computer on which the UNM2000 is to be installed.
4 Version: A
1 Overview
1.3.1 Hardware Configuration Requirements
Server End
The hardware configuration requirements of the UNM2000 server vary according to

the network scale. For detailed requirements, see Table 1-2.
Table 1-2 Hardware Configuration Requirements of the Server End
Network CPU Clock Rate CPU Mem- Hard Hard Disk Format Network Card
Scale Quantity ory Disk
Space
The format of the disk

Equivalent to
on which the
more than
database and the
1000 OLTs Embedded double
Intel E7-8837 (8- UNM2000 will be
that are fully 4 64G 4*600GB Gb dual-port
core), 2.6GHz installed (disk C and
configured and network cards
disk D by default
connected
respectively) should
with ONUs
be NTFS
Equivalent to
on which the
500 to 1000
database and the
OLTs that are Intel XeonE7- Embedded double
UNM2000 will be
fully 4610V2 (8-core), 4 32G 4*600GB Gb dual-port
installed (disk C and
configured and 2.3GHz network cards
disk D by default
connected
with ONUs
be NTFS
Version: A 5
Table 1-2 Hardware Configuration Requirements of the Server End (Continued)
Network CPU Clock Rate CPU Mem- Hard Hard Disk Format Network Card
Scale Quantity ory Disk
Space

Equivalent to
on which the
100 to 500
database and the
OLTs that are Intel XeonE5- Embedded double
UNM2000 will be
configured and 3.3GHz network cards
disk D by default
connected
with ONUs
be NTFS
Equivalent to
on which the
less than 100
database and the
OLTs that are Intel XeonE5- Embedded single
UNM2000 will be
configured and 2.5 GHz network card
disk D by default
connected
with ONUs
be NTFS
6 Version: A
1 Overview
Client End
Table 1-3 shows the hardware configuration requirements of the UNM2000 client
end.
Table 1-3 Hardware Configuration Requirements of the Client End
Network Scale CPU Clock Rate CPU Mem- Hard Disk Hard Disk Video Card
Quantity ory Space Format
Equivalent to
The format of the
more than
disk on which the
1000 OLTs that
Intel XeonE5-2637V2 UNM2000 will be 1 GB discrete
are fully 1 16G 1*2TB
(4-core), 3.5GHz installed (disk D graphics
configured and
by default)
connected with
should be NTFS
ONUs
Equivalent to The format of the
500 to 1000 disk on which the
OLTs that are Intel i3-4130 (2-core), UNM2000 will be 1 GB discrete
1 8G 1*1TB
fully configured 3.4GHz installed (disk D graphics
and connected by default)
with ONUs should be NTFS
100 to 500 disk on which the nVIDIA
Intel Core i5-4200U (1.
OLTs that are UNM2000 will be GT720M 1GB
6G-2.6G/3M) (2-core), 1 8G 1*500GB
fully configured installed (disk D discrete
3.4GHz
and connected by default) graphics
less than 100 disk on which the
Intel Corei5-4200U (1. Intel HD 4400
OLTs that are UNM2000 will be
6G-2.6G/3M) (2-core), 1 4G 1*500GB integrated
fully configured installed (disk D
3.4GHz graphics
and connected by default)
1.3.2 Software Configuration Requirements
The software requirements for the computer running the UNM2000 server end are
as shown in Table 1-4.
Version: A 7
Table 1-4 Software Configuration Requirements of the Server End
Configuration Item Requirement
Windows Server 2008 R2 Standard (64-bit)
Operating system SUSE Linux Enterprise 11 (64-bit)
Solaris 11 (64-bit)
SQL Server 2008 R2

Database
MySQL 5.6
JRE JRE 1.6.0
The software requirements for the computer running the UNM2000 client end are as
shown in Table 1-5.
Table 1-5 Software Configuration Requirements of the Client End
Configuration Item Requirement
Operating system Windows 7 or Windows 8

JRE JRE 1.6.0
8 Version: A
2 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
Version: A 9
2.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.
2.1.1 Centralized Deployment Mode
The centralized deployment mode uses multi-client and single-server network

scheme. There is only one UNM2000 server, which supports access and operations
of multiple clients, applicable to the medium to small-sized networks. This
deployment mode is simple and the cost is low. Figure 2-1 shows the network in this
mode.
Figure 2-1 Centralized Deployment Mode
10 Version: A
2.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 2-2 shows the network
in this deployment mode.
Figure 2-2 Distributed Deployment Mode
2.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.
Version: A 11
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,
as shown in Figure 2-3.
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, as shown in Figure 2-4.
Figure 2-3 Local Centralized Deployment Mode of Cluster Disaster Tolerance
12 Version: A
Figure 2-4 Remote Centralized Deployment Mode of Cluster Disaster Tolerance
2.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. In the station,
the distributed deployment is adopted to achieve load balancing over several
servers and enlarge the management capacity. The number of servers in the active
station is consistent with that in the standby station, and they are backups to each
other.
Version: A 13
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,
as shown in Figure 2-5.
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, as shown in Figure 2-6.
Figure 2-5 Local Distributed Deployment Mode of Cluster Disaster Tolerance
14 Version: A
Figure 2-6 Remote Distributed Deployment Mode of Cluster Disaster Tolerance
2.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.
Version: A 15
u Disadvantage: if the network is faulty, the UNM2000 cannot operate because

the information channel of the managed network is interrupted.
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.
2.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 2-7.
Figure 2-7 Network Example
16 Version: A
3 Basic Function of the UNM2000
The following introduces the network management functions provided by the

UNM2000.
Configuration Management
Topology Management
Alarm Management
Event Management
Performance Management
Security Management
Version: A 17
3.1 Configuration Management
The UNM2000 provides the configuration management function for equipment in

the entire network. Users can perform various configurations on the equipment
using the UNM2000.
Full Service Configuration
u The broadband access equipment carries multiple services such as data, voice,
IPTV and CATV simultaneously. The UNM2000 provides a universal
configuration GUI for full service configuration. Users can configure multiple
services collectively using the UNM2000, which will greatly improve the
configuration efficiency.
u Aiming at the system objects, the UNM2000 provides shortcuts for service
configurations, and integrates individual Grid configuration GUIs into a main
GUI for configuration operations. That is, all the configuration commands and
ONU lists under the system objects are integrated into a service configuration
management GUI to facilitate service configuration operations of users.
Global Profile and Global Configuration
The UNM2000 provides the global profile and global configuration function. If
multiple NEs share the same or similar configuration, you can bind the global profile
to multiple NEs or deliver the global configuration to multiple NEs, so as to improve
the configuration efficiency. Meanwhile, the global profile and global configuration
are independent of the NE status and therefore the NEs can be configured in offline
status.
Checking the Configuration
The UNM2000 supports configuration data check. During service configuration, the
UNM2000 will automatically verify the validity of the configuration data. Once
detecting a configuration conflict or invalidity, the UNM2000 will prompt users to
modify the data until they are valid. The configuration check function effectively
improves the accuracy of the configurations and reduces the time spent in
eliminating service configuration errors. It improves the configuration efficiency.
18 Version: A
Exporting the Configuration File
The UNM2000 provides the configuration file export function. To vie the
configuration file of a device, you can export it first. The exported configuration file
will be saved to the file folder named by export time, convenient for you to view.
Pre-configuration
The UNM2000 supports the pre-configuration function. Before connecting the

equipment with the UNM2000, users can pre-configure the needed service on the
UNM2000. After connecting to the equipment normally, the UNM2000 will send the
pre-configured data to the equipment to complete the service configuration. The
pre-configuration function enables the services to be configured despite of the
connection status between the device and the UNM2000, improving the
configuration efficiency.
3.2 Topology Management
Topology management displays the connection status between the managed NEs in
topology graphics. Users can understand the network condition of the entire
network and monitor the operation status in real time by viewing the topology view.
Entire Network Monitoring Topology
The UNM2000 provides multiple topology management views to facilitate users to

manage equipment and network in multiple dimensions conveniently.
u Main topology view: The main topology view of the UNM2000 is composed of
the object tree pane and the physical topology view / customized view.
4 Object tree pane: Displays the hierarchical relationship of the network

structure in a tree-like structure. Click each node of the object tree and
locate each node position in the physical topology view / customized view.
4 Physical topology view: Displays the network connection relationship

between each device in the entire network.
4 Customized view: Users can customize the objects displayed in the view.
The view only displays the network connection relationship of the selected
objects.
Version: A 19
u Sub-topology view: Displays the physical units of a specific NE, including the
topology relationship of subracks, cards and interfaces.
u Thumbnail: 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 the Thumbnail view to have a overall view of the
entire network. The purplish red frame in the Thumbnail pane shows the
display area in the current view. Users can drag the frame using the mouse to
move the display area.
Topology Alarm and Status Display
The UNM2000 supports different colors and icons to represent the logical domains
and NE alarms / status, as shown in Figure 3-1 and Figure 3-2.
Figure 3-1 Logical Domain Icon Example
Figure 3-2 NE Icon Example
u Different NE node icons represent different equipment types.
u The ground color of the topology node icon indicates the polling status (normal,
unknown, communication interrupted, etc.) and alarm level of the NE. The
ground color of the icon displayed is the color of the highest alarm level.
Table 3-1 describes the alarm colors.
20 Version: A
Table 3-1 Alarm Color Description
Alarm Priority Alarm Color Description
Deep grey Communication interruption
Red Critical alarm

Orange Major alarm
Yellow Minor alarm

Blue Warning alarm
Green Normal
Light grey Unknown
u The icon frame indicates there is unconfirmed alarm on the monitored object.
The frame color represents the highest level of all the unconfirmed alarms.
u The icon at the top right corner of the monitored object prompts the latest
special alarm according to the definition. For the definition of special alarms,
you can view it through Legend on the toolbar of the topology view.
u The logical domain icon displays the highest-level alarm color of the NE nodes
in the logical domain and the latest special alarm icon.The UNM2000 supports
manually dragging or sorting the NEs in the logical domains, which is
convenient for searching NEs.
Access to Integrated Management
The UNM2000 provides the operation access method of the NEmanagement.

During the network maintenance, users can perform the Ping, physical configuration
inspection and alarm viewing operations on the equipment directly via the topology
view.
3.3 Alarm Management
Alarm management performs real-time monitoring on the faults and abnormalities

generated during device operation, and provides detailed information and analysis
of the alarm, so as to help isolate faults and handle them quickly.
Alarm Classification
The UNM2000 classifies the alarms according to the alarm levels and alarm
statuses.
Version: A 21
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 prompt alarm.
u Urgent 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 Prompt alarm: refers to the alarm which does not affect the existing services but
may influence services later; users 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.
The alarm frequently generated by the same object will be displayed as one
entry in the current alarm list. To query each alarm record, you can view the
alarm logs.
u Alarm history: the current alarms that have been handled will be alarm history
after a pre-set 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 users 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: users can view the current alarms and historical alarms of the
selected equipment in the UNM2000 window.
22 Version: A
u Alarm panel prompt: The alarm panel on the system homepage displays the
total number of current alarms in the 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 equipment, the

UNM2000 will generate an audio prompt. Meanwhile, the corresponding alarm
indicator LED will be illuminated in the color corresponding to the alarm level.
When alarms of multiple alarm levels exist, the alarm indicator LED will be
displayed in the color of the highest alarm level.
u Alarm sequence: users can set the alarm sequence according to their concern.
u Alarm information exporting and saving: users can export and save the alarm
information that they have viewed to an html, CSV or excel file, 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 equipment.
In this way, users can be acknowledgeable of the 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 equipment by means of automatic upgrade in the occasion of connection,
automatic polling, manual polling and Trap active report.
u Automatic upgrade in the occasion of connection: the UNM2000 will

automatically update the equipment data when connecting with the equipment.
After obtaining the latest data of the equipment, 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.
Version: A 23
u Automatic polling: The manager module of the UNM2000 will automatically poll
about the managed equipment at regular intervals. The equipment 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 users have selected the equipment, the UNM2000 will poll
about the selected equipment 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. When new
alarms are generated, the UNM2000 alarm panel will be automatically
refreshed, and the alarm list will be automatically refreshed to display the new
alarms so that you can understand the alarm information of the network in time.
Alarm Isolation
The UNM2000 supports the alarm isolation function, so that users can isolate the
alarm to the port level using the UNM2000.
Alarm Filtering
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, users can filter
them. The filtered alarms will not be displayed or saved. After the filter conditions
are set, the alarms meeting the conditions will be filtered.
24 Version: A
Alarm Confirmation and Saving
u Alarm confirmation: It is a way to identify whether an alarm is 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 supports the function of
confirming and clearing alarms with one click. It enables you to delete an alarm
after confirming it, improving the maintenance efficiency.
u Alarm saving: this function can save the historical alarms into files. 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 saving at specified time, saving by number of records, saving by
number of saved days or deleting directly.
Forwarding Alarms
Users 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 pre-set 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 level to highlight the focused 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 Users can set an alarm for their concerned parameter which is not currently
defined in the UNM2000 and set value range for generating the alarm. When
the equipment parameter reaches the set range, the UNM2000 will report the
alarm.
Version: A 25
3.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 prompt) according to the severity.
Viewing Events in the Entire Network
Users can view the events in the entire network or certain events according to
specified conditions, and save the query conditions to a profile.
Reporting Event Automatically
Users can set the automatic report of the events that meet the specified conditions,
including reporting the latest events in the Event Report tab. Users can also set the
automatic scrolling of the event list so that they can view the latest events in a timely
manner.
Tracing Signals
Users can trace the signal frames of the communication between the current IAD
and the voice communication card, so that they can detect the communication faults
in a timely manner. This function is only supported by the FTTH-type and FTTB-type
ONUs that support voice service.
3.5 Performance Management
The UNM2000 supports query of real-time performance data and comprehensive

management performance data. Users can monitor the real-time performance of the
equipment in the access network and compare 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:
26 Version: A
u Real-time performance: the current performance data of the equipment saved

on the equipment and read from the equipment by the UNM2000.
u Current performance: the average value of the performance data in the

specified 15-minute interval saved on the equipment. Users 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. Users can learn the performance parameter values and
have an ideal of the change in performance parameters displayed in different
forms. In this way, the network operation conditions and trends over time can
be identified, and network failure can be thus prevented.
u Performance saving: the UNM2000 can save the historical performance data
into files. 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, data saving according
to count of records, data saving according to number of days, or deleting data
directly.
Comparing Performance Data
The UNM2000 provides the function of performance comparison. The values of the
same performance parameter concerning the same port on the same equipment
collected in different cycles are put together. Users can use this function to compare
the instant performance data of selected equipment, 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.
Version: A 27
3.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 authorities
to users and restrict them to use the UNM2000 in appropriate scenarios.
User: The user whose uses the UNM2000 client.
User management: The username and its password uniquely determine the login,
operation and management authorities. After initial installation of the UNM2000, it
provides only one default user: admin. The admin user has all the operation
authorities and management authorities, and other users are directly or indirectly
created by the admin user.
User group: Indicates a set of users. After a user is added into a group, this user has
all the authorities bound with the group. The total authorities of the user include the
user's authorities and the authorities of the user group to which the user belongs.
User group management: The UNM2000 manages a group of users that have the
same authorities by creating a user group. This enables you to manage users in a
batch manner and lower down the management cost. The UNM2000 provides five
default user groups: Administrators, 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, administrative domain, operation authority and access control list (ACL).
28 Version: A
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.
Authorization and Domain Division
The UNM2000 supports authorization and domain division management, which only
allows the user to deliver the operations within its administrative domain 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 setting the domain authorities for 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 authorities 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.
Version: A 29
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.
30 Version: A
The UNM2000 supports the domain-based management via menu control as

follows:
u Object menu: The users with restricted authority on the domain cannot import
the management domain. 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 objects whose levels are higher than the
module 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 authorities.
4 Checking physical configuration: Only users with authorities on modules or

higher-level objects can check the physical configuration.
4 Basic operations on the objects at each level: Only users with authorities
on all the lower-level objects of the selected object can add / delete the
lower-level objects.
u The operation of viewing logs requires differentiation of the advanced

administrator and other system users. The users other than the advanced
administrator can only view their own logs.
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.
Version: A 31
u During network operation and maintenance, the network administrator can log
into the system as an advanced administrator and monitor the entire network. If
detecting any operation anomalies performed by a lower-level user, the network
administrator can log out the user (upon logout, the UNM2000 will automatically
save its topology) to ensure secure running of the system.
u When using the UNM2000 to maintain the network, users can manually lock
the UNM2000 client end if they will be 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 automatically so that the UNM2000 client will be
automatically locked when no operations are performed during the preset time
period to ensure security of the network and the EMS.
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, users 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 letter / number quantity of password, etc. Users 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.
32 Version: A
Log Management
The logs record the user operation information and the important events occurred 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 login, 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-secure 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 Northbound interface command logs: Records the operations performed

on the equipment by the users at the UNM2000 client end via the
northbound interface commands. The northbound interface command logs
include TL1 command logs and Web Service command 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 sever.
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.
Version: A 33
4 System Architecture
The following introduces the software architecture and external ports of the
UNM2000.
Software Architecture
External Interface
34 Version: A
4 System Architecture
4.1 Software Architecture
The UNM2000 adopts the client end - server mode. Figure 4-1 shows the software
architecture of the main modules in the system.
Figure 4-1 UNM2000 Software Structure
Version: A 35
4.2 External Interface

Northbound Interface
The UNM2000 supports the CORBA, TL1 and SOCKET northbound interfaces. 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 reporting
notification. The UNM2000 can implement quick integration with the OSS system
through the UNM2000 northbound interface to meet the requirements for integration
of different OSS systems.
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 TP4 and UDP protocols.
36 Version: A
5 Technical Specifications
The following introduces the technical specifications of the UNM2000.
Management Capacity
Performance Specifications
External Server Port
Standards
Version: A 37
5.1 Management Capacity
Each UNM2000 can manage 100 thousands NEs.
5.2 Performance Specifications
The following 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.
List of Performance Specifications
Table 5-1 shows the performance specifications of the UNM2000.
Table 5-1 List of Performance Specifications
Item Specification
UNM2000 startup time ＜10min

UNM2000 shutoff time ＜10s
Simultaneous client ends ≥100
Current alarm storage capacity 1000w
Historical alarm storage capacity Supporting records of more than six months.
Log storage capacity Supporting records of more than six months.
Number of users admitted 500

Number of user groups admitted 50
Number of object groups admitted 100
Number of operation groups admitted 255
Alarm response delay ＜10s
u Number of records≤10000:2s
Alarm query delay u 10000＜Number of records≤100000:8s
u 100000≤Number of records:20s
Alarm handling capability ≥100 alarms per second
Performance response delay ＜10s

u Number of records≤10000:2s
Performance query delay u 10000＜Number of records≤100000:8s
u 100000≤Number of records:20s
Maximum number of performance
10000
objects to be counted
38 Version: A
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.
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.
Sever-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.
5.3 External Server Port
If the firewall is deployed in the network, users should enable the external server
ports of the UNM2000 to ensure the normal communication. Table 5-2 shows the
external server ports used by the UNM2000.
Version: A 39
Table 5-2 Description of External Server Port
Destination Port Process of Destination Port Port Description
52001 to 52003 icegridregistry The port used by the icegridregistry process
52036 iceboxd RPC forwarding service
52051 iceboxd Static data service

52053 iceboxd Data proxy service
52052 iceboxd Access data collection service

52054 iceboxd License service
52081 iceboxd Log service
52082 iceboxd User management service
52091 iceboxd Object configuration service
52092 iceboxd Object access service
52111 iceboxd Global alarm service

52114 iceboxd Alarm notification service
52115 iceboxd Information transmission service
52112 iceboxd Alarm relevance analysis service
52113 iceboxd Alarm relevance analysis proxy service
52116 iceboxd NE alarm service

52131 iceboxd Global event service
52132 iceboxd NE event service
52151 iceboxd Global performance service
52152 iceboxd NE performance service
52171 iceboxd Main topology service
52173 iceboxd Custom topology service
52172 iceboxd NE sub-topology service
52203 iceboxd Service configuration service
52201 iceboxd Global service configuration service
52202 iceboxd Timing task management service
Extension service of the northbound

52252 iceboxd
interface service configuration
52251 iceboxd Active TL1 interface of the access network
5.4 Standards
The following introduces the standards and protocols followed by the UNM2000.
40 Version: A
u The UNM2000 and the interfaces connecting to the equipment support 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 networks such

as ITU-T M.3010, ITU-T M.3100, ITU-T M.3400 and ITU-T.X.721.
u Supports YD/T1475 (2006), YD/T1385-2005, YD/T1434-2006, etc.
u The CORBA northbound interface supports standards such as TMF513V3.2,

TMF608V3.5 and TMF814V3.2.
u The TL1 service supports standards such as DSLForumTR-069,

DSLForumWT-142 and SFF-8472.
Version: A 41
Appendix A Abbreviations
BML Business Management Layer
BMS Business Management System
Common Object Request Broker

CORBA
Architecture
CPU Central Processing Unit
DCC Data Communication Channel

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

GE Gigabit Ethernet
GNE Gate Network Element

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

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

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

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

Network Convergence Management System V2.0R4 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

Network Convergence Management System V2.0R4 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

A Initial version, corresponding to V2.0R4.

UNM2000 Network Introduces how to install the

UNM2000 Network Introduces how to install the

UNM2000 Network Introduces the operation guidelines of

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.

The network management computer should be placed away from

Use UPS power supply to avoid loss of network management

To shut down the network management computer, first exit the

Do not exit the network management system when it is working

The network management computer cannot be used for purposes

Do not delete any file in the network management system

Do not visit Internet via the network management computer.

Do not modify the network management computer’s protocol

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

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

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

1.2 Product Feature ................................................................................3

1.3 System Configuration Requirements .................................................4

1.3.1 Hardware Configuration Requirements................................5

2 Network and Application .................................................................................9

2.1 UNM2000 Deployment Mode ..........................................................10

2.1.1 Centralized Deployment Mode ..........................................10

2.2 Network Mode between the UNM2000 and NE................................15

2.3 Network Example ...........................................................................16

3 Basic Function of the UNM2000 ....................................................................17

3.1 Configuration Management .............................................................18

3.2 Topology Management....................................................................19

3.3 Alarm Management ........................................................................21

3.4 Event Management.........................................................................26

3.5 Performance Management..............................................................26

3.6 Security Management .....................................................................28

4.1 Software Architecture......................................................................35

5.1 Management Capacity ....................................................................38

5.2 Performance Specifications ............................................................38

5.3 External Server Port........................................................................39

Appendix A Abbreviations ............................................................................42

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

System Configuration Requirements

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 Devices Managed by the UNM2000

Type Device Model

OLT AN5116-06B, AN5116-02, AN5116-06B, AN5516-04, AN5516-04B and AN5516-06