UNM2000 Network Convergence Management System Product Description(Version B)

Prévia do material em texto

UNM2000
Network Convergence
Management System
Product Description
Version: B
Code: MN000001818
FiberHome Telecommunication Technologies Co., Ltd.
November 2014
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
Related Documentation
Document Description
UNM2000 Network Convergence
Management System Product
Description
Introduces the functions, application scenarios and
technical specifications of the UNM2000 Network
Convergence Management System.
UNM2000 Network Convergence
Management System Installation
Guide (Based on Windows)
Introduces how to install the UNM2000 Network
Convergence Management System on the Windows
operating system.
UNM2000 Network Convergence
Management System Installation
Guide (Based on Windows)
Introduces how to install the UNM2000 Network
Convergence Management System on the SUSE Linux
operating system.
UNM2000 Network Convergence
Management System Operation
Guide
Introduces the operation guidelines of the UNM2000
Network Convergence Management System.
I
Version
Version Description
A Initial version.
B
Revised the requirements for the matching software and
hardware of the product.
Intended Readers
This manual is intended for the following readers:
u Planning and designing engineers
u Commissioning engineers
u Operation and maintenance engineers
To utilize this manual, these prerequisite skills are necessary:
u Data communication technology
u Access network technology
II
Conventions
Terminology Conventions
Terminology Convention
UNM2000
FiberHome UNM2000 Network Convergence Management
System
Symbol Conventions
Symbol Convention Description
Note Important features or operation guide.
Caution
Possible injury to persons or systems, or cause traffic
interruption or loss.
Warning May cause severe bodily injuries.
➔ Jump Jumps to another step.
→
Cascading
menu
Connects multi-level menu options.
↔
Bidirectional
service
The service signal is bidirectional.
→
Unidirectional
service
The service signal is unidirectional.
III
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.
V
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.
VI
VII
VIII
Contents
Preface...................................................................................................................I
Related Documentation ...................................................................................I
Version ...........................................................................................................II
Intended Readers ...........................................................................................II
Conventions ..................................................................................................III
Operation Safety Rules ......................................................................................... V
1 Overview .....................................................................................................1-1
1.1 Product Positioning........................................................................1-2
1.1.1 Deployment of the UNM2000 in the TMN..........................1-2
1.1.2 Manageable Device Types...............................................1-2
1.2 Product Feature.............................................................................1-3
1.3 System Configuration Requirements ..............................................1-4
1.3.1 Hardware Configuration Requirements.............................1-4
1.3.2 Software Configuration Requirement................................1-6
2 Network and Application ..............................................................................2-1
2.1 UNM2000 Deployment Mode .........................................................2-2
2.1.1 Single-server Centralized Deployment Mode....................2-2
2.1.2 Single-system Distributed Deployment Mode ...................2-3
2.1.3 Cluster Disaster Tolerance Centralized Deployment Mode2-3
2.1.4 Cluster Disaster Tolerance Distributed Deployment Mode.2-4
2.2 Network Mode between the UNM2000 and NE...............................2-5
2.3 Network Example ..........................................................................2-6
3 Basic Function of the UNM2000 ...................................................................3-1
3.1 Configuration Management ............................................................3-2
3.2 Topology Management...................................................................3-3
3.3 Alarm Management .......................................................................3-5
3.4 Event Management........................................................................3-9
3.5 Performance Management...........................................................3-10
3.6 Security Management ..................................................................3-11
4 System Architecture.....................................................................................4-1
4.1 Software Architecture.....................................................................4-2
4.2 External Port..................................................................................4-2
5 Technical Specifications...............................................................................5-1
5.1 Management Capacity ...................................................................5-25.2 Performance Specifications ...........................................................5-2
5.3 External Server Port.......................................................................5-4
5.4 Standards......................................................................................5-5
Appendix A Abbreviations .......................................................................... A-1
Figures
Figure 1-1 Deployment of the UNM2000 in the TMN........................................1-2
Figure 2-1 Single-server Centralized Deployment Mode..................................2-2
Figure 2-2 Single-system Distributed Deployment Mode .................................2-3
Figure 2-3 Cluster Disaster Tolerance Centralized Deployment Mode..............2-4
Figure 2-4 Cluster Disaster Tolerance Distributed Deployment Mode...............2-5
Figure 2-5 Network Example ..........................................................................2-6
Figure 3-1 Logical Domain Icon Example ........................................................3-4
Figure 3-2 NE Icon Example ...........................................................................3-4
Figure 4-1 UNM2000 Software Architecture ....................................................4-2
Tables
Table 1-1 Manageable Devices of the UNM2000 ...........................................1-3
Table 1-2 Hardware Configuration Requirements of the Server End ...............1-5
Table 1-3 Hardware Configuration Requirements of the Client End ................1-6
Table 1-4 Software Configuration Requirements of the Server End ................1-7
Table 1-5 Software Configuration Requirements of the Client End..................1-7
Table 3-1 Alarm Color Description .................................................................3-4
Table 5-1 List of Performance Specifications .................................................5-2
Table 5-2 Description of External Server Port.................................................5-4
1 Overview
The following introduces the product orientation, product features and configuration
requirements of the UNM2000 Network Convergence Management System
(abbreviated as the UNM2000 hereinafter).
The UNM2000, developed by FiberHome, manages the access equipment and
meets the requirement of the access network operation and management.
Product Positioning
Product Feature
System Configuration Requirements
Version: B 1-1
UNM2000 Network Convergence Management System Product Description
1.1 Product Positioning
The following introduces the position of the UNM2000 in the TMN and the
manageable equipment category.
1.1.1 Deployment of the UNM2000 in the TMN
The TMN provides the hierarchical network architecture and standard network
interface. It is composed of business management layer (BML), service
management layer (SML), network management layer (NML) and element
management layer (EML). This is called the hierarchical management architecture
of the TMN.
The UNM2000 manages the access devices and locates at the EML, as shown in
Figure 1-1.
Figure 1-1 Deployment of the UNM2000 in the TMN
1.1.2 Manageable Device Types
The devices that can be managed by the UNM2000 are shown in Table 1-1.
1-2 Version: B
1 Overview
Table 1-1 Manageable Devices of the UNM2000
Type Device Model
OLT AN5516–01, AN5116–02, AN5116–06B, AN5516–04, AN5516–04B, AN5516–06.
ONU
AN5506-04-FG, AN5006-04-A, AN5006-04-B, AN5006-04-F, AN5506-01-A,
AN5506-01-B, AN5006-01-A, AN5006-01-B.
MSAN AN5006–20, AN5006–30, AN5006–15, AN5006–16
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.
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.
u The functional modules is removable and assemble, which meets the
customization requirement for users.
Version: B 1-3
UNM2000 Network Convergence Management System Product Description
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 new user experience using the Web login mode.
u The UNM2000 keeps the consistent GUI style for each equipment using
modularized design.
Compatible with Multiple Operation Systems
As an independent application, the UNM2000 can be installed in different operation
systems based on different databases. The UNM2000 can not only provide high-
end resolution for the large-scale network, but also provide low-cost resolution for
medium and small-scale network.
u The UNM2000 can operate in the Windows, Linux and Solaris systems. The
client end and server end performance of the UNM2000 is irrelevant to the
operation 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.
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.
1-4 Version: B
1 Overview
Table 1-2 Hardware Configuration Requirements of the Server End
Network
Scale
CPU Clock Rate CPU
Quantity
Mem-
ory
Hard
Disk
Space
Hard Disk Format Network Card
Equivalent to
more than
1000 OLTs
that are fully
configured and
connected
with ONUs
Intel E7-8837 (8-
core), 2.6GHZ
4 64G 4*600GB
The format of the disk
on which the
database and the
UNM2000 will be
installed (disk C and
disk D by default
respectively) should
be NTFS
Embedded double
Gb dual-port
network cards
Equivalent to
500 to 1000
OLTs that are
fully
configured and
connected
with ONUs
Intel XeonE7-
4610V2 (8-core),
2.3GHZ
4 32G 4*600GB
The format of the disk
on which the
database and the
UNM2000 will be
installed (disk C and
disk D by default
respectively) should
be NTFS
Embedded double
Gb dual-port
network cards
Equivalent to
100 to 500
OLTs that are
fully
configured and
connected
with ONUs
Intel XeonE5-
2667V2 (8-core),
3.3GHZ
2 32G 2*600GB
The format of the disk
on which the
database and the
UNM2000 will be
installed (disk C and
disk D by default
respectively) should
be NTFS
Embedded double
Gb dual-port
network cards
Equivalent to
less than 100
OLTs that are
fully
configured and
connected
with ONUs
Intel XeonE5-
2430V2 (6-core),
2.5 GHz
2 16G 2*600GB
The format of the disk
on which the
database and the
UNM2000 will be
installed (disk C and
disk D by default
respectively) should
be NTFS
Embedded single
Gb dual-port
network card
Version: B 1-5
UNM2000 Network Convergence Management System Product Description
Client End
Table 1-3 shows the hardware configuration requirementsof the UNM2000 client
end.
Table 1-3 Hardware Configuration Requirements of the Client End
Network Scale CPU Clock Rate CPU
Quantity
Mem-
ory
Hard Disk
Space
Hard Disk
Format
Video Card
Equivalent to
more than
1000 OLTs that
are fully
configured and
connected with
ONUs
Intel XeonE5-2637V2
(4-core), 3.5GHZ
1 16G 1*2TB
The format of the
disk on which the
UNM2000 will be
installed (disk D
by default)
should be NTFS
1 GB discrete
graphics
Equivalent to
500 to 1000
OLTs that are
fully configured
and connected
with ONUs
Intel i3-4130 (2-core),
3.4GHz
1 8G 1*1TB
The format of the
disk on which the
UNM2000 will be
installed (disk D
by default)
should be NTFS
1 GB discrete
graphics
Equivalent to
100 to 500
OLTs that are
fully configured
and connected
with ONUs
Intel Core i5-4200U (1.
6G-2.6G/3M) (2-core),
3.4GHz
1 8G 1*500GB
The format of the
disk on which the
UNM2000 will be
installed (disk D
by default)
should be NTFS
nVIDIA
GT720M 1GB
discrete
graphics
Equivalent to
less than 100
OLTs that are
fully configured
and connected
with ONUs
Intel Corei5-4200U (1.
6G-2.6G/3M) (2-core),
3.4GHz
1 4G 1*500GB
The format of the
disk on which the
UNM2000 will be
installed (disk D
by default)
should be NTFS
Intel HD 4400
integrated
graphics
1.3.2 Software Configuration Requirement
The software requirements for the computer running the UNM2000 server end are
as shown in Table 1-4.
1-6 Version: B
1 Overview
Table 1-4 Software Configuration Requirements of the Server End
Configuration Item Requirement
Operating system
Windows Server 2008 R2 Standard (64-bit)
Linux Enterprise 11 (64-bit)
Solaris 11 (64-bit)
Database
SQL Server 2008 R2
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
Version: B 1-7
2 Network and Application
The following introduces the UNM2000 network modes in different deployment
modes, the network mode of between the UNM2000 and the NEs, and the typical
network example.
UNM2000 Deployment Mode
Network Mode between the UNM2000 and NE
Network Example
Version: B 2-1
UNM2000 Network Convergence Management System Product Description
2.1 UNM2000 Deployment Mode
The UNM2000 supports the single-server distributed deployment mode, single-
system centralized deployment mode, cluster disaster tolerance centralized
deployment mode and cluster disaster tolerance distributed deployment mode.
Users can set the UNM2000 system deployment scheme according to the network
scale and deployment requirement.
2.1.1 Single-server Centralized Deployment Mode
The single-server 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 2-1 shows the network diagram.
Figure 2-1 Single-server Centralized Deployment Mode
2-2 Version: B
2 Network and Application
2.1.2 Single-system Distributed Deployment Mode
In the single system distributed deployment mode, multiple servers provide the
functions of the UNM2000 server end. The UNM2000 services can be distributed
into different servers, among which the heavily loaded services (such as data
collection, alarm, performance, event, object access and service configuration)
support multiple instance configuration, so that the load balancing, management
capacity expansion and performance improvement can be achieved. Figure 2-2
shows the network diagram.
Figure 2-2 Single-system 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. Figure 2-3 shows the network
diagram.
Version: B 2-3
UNM2000 Network Convergence Management System Product Description
Figure 2-3 Cluster Disaster Tolerance Centralized Deployment Mode
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. 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. Figure 2-4 shows the network
diagram.
2-4 Version: B
2 Network and Application
Figure 2-4 Cluster Disaster Tolerance Distributed Deployment Mode
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.
u Disadvantage: if the network is faulty, the UNM2000 cannot operate because
the information channel of the managed network is interrupted.
Version: B 2-5
UNM2000 Network Convergence Management System Product Description
Out-of-band Network
The out-of-band network mode means transmitting the management data and
service data of the equipment in different channels.
u Advantage: in the out-of-band network mode, the management data channel is
independent and is not influenced by whether the service data channel is
normal or not. Therefore, compared to the in-band network mode, the out-of-
band network mode provides more reliable equipment management channel.
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 out-of-band network mode requires an independent channel
for the UNM2000 to manage the network equipment and provide a
maintenance channel irrelevant to the service channel, so that the cost of
network setting 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.
Figure 2-5 shows the network diagram.
Figure 2-5 Network Example
2-6 Version: B
3 Basic Function of the UNM2000
The UNM2000 provides the management functions.
Configuration Management
Topology Management
Alarm Management
Event Management
Performance Management
Security Management
Version: B 3-1
UNM2000 Network Convergence Management System Product Description
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 configurationGUIs 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, users can bind the global
profile to multiple NEs or deliver the global configuration to multiple NEs, so as to
improve the configuration efficiency. The global profile and global configuration are
independent from the NE status, so that the off-line NE configuration can be
performed.
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 the they are valid. This function improves the configuration
accuracy, saves the troubleshooting time caused by service configuration faults at a
later stage, and enhances the configuration efficiency.
3-2 Version: B
3 Basic Function of the UNM2000
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. This
function unties the service configuration from the status of connection between the
equipment and the UNM2000, and improves 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 hierarchy of the network structure in the tree
form. 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.
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.
Version: B 3-3
UNM2000 Network Convergence Management System Product Description
If the current view cannot display the detailed condition of the entire network
due to the large scale of the network, users can view in the thumbnail. 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 shows the color of the highest-level alarm. Table 3-1
lists the color description.
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 Prompt alarm
Green Normal
3-4 Version: B
3 Basic Function of the UNM2000
Table 3-1 Alarm Color Description (Continued)
Alarm Priority Alarm Color Description
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. Users can view the special alarm
definition by clicking 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.
Access to Integrated Management
The UNM2000 provides the integrated access for NE network management
functions in the topology view. 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 the equipment operation and provides detailed information and
analysis of the alarm, so as to help users to isolate the faults and handle them
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 prompt alarm.
u Urgent alarm: refers to the alarm which causes the service interruption and
requires immediate troubleshooting.
Version: B 3-5
UNM2000 Network Convergence Management System Product Description
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 generated by the same object that has been frequently occurring will
be displayed as one item in the current alarm list. Users 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 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.
u Alarm board prompt: the alarm board 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 board according to the pre-set profile.
3-6 Version: B
3 Basic Function of the UNM2000
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 several levels coexist, the alarm indicator LED will be
illuminated in the color corresponding tothe alarm at the highest level among
them.
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.
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.
Version: B 3-7
UNM2000 Network Convergence Management System Product Description
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. If a new alarm
is generated, the alarm board of the UNM2000 will update automatically and
the alarm list will display the new alarm automatically, so that users can
understand the alarm information of the network in a timely manner.
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 users have configured
the filtering conditions, the alarms meeting the conditions will be filtered.
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.
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 data saving at regular intervals, data saving according to count of
records, data saving according to number of days, or deleting data directly.
3-8 Version: B
3 Basic Function of the UNM2000
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 Users can modify the alarm levels and highlight their 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 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.
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.
Version: B 3-9
UNM2000 Network Convergence Management System Product Description
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:
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.
3-10 Version: B
3 Basic Function of the UNM2000
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, datasaving 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.
3.6 Security Management
The security management aims at preventing illegal users from logging in the
UNM2000 and legal users from performing illegal operations on the UNM2000, so
as to guarantee the security of network operations. The UNM2000 provides
comprehensive security management by means of authorization and domain
division, access control, log management, and so on to guarantee the network
security to the largest extent.
Authorization and Domain Division
The UNM2000 introduces the concepts of user group, operation set and object set,
defines the users as the ones restricted to certain domains, and binds them to
operation sets, object sets and user groups respectively so as to enable role-based
and domain-based management.
u User group: The users that need uniform authorization are admitted to the
same user group. By assigning a certain authority to the user group, all the
member users in the group are authorized with the authority of the group. In this
way, user authorization can be implemented in an efficient way.
Version: B 3-11
UNM2000 Network Convergence Management System Product Description
u Operation set: An operation set is created and all the operation authorities
required by a service are entitled to the operation set. In this way, the
authorities can be allocated to the users or user groups concerned collectively
so as to enable quick allocation of the user authorities. When a certain user or
user group is bound to a certain operation set, the user or the user group will be
entitled with the authorities for reading and writing of the operation set as well
as the authorities for reading all the commands outside the operation set.
u Object set: By creating an object set and admitting the objects that can be
collectively managed to the set, users can assign a user or a user group to
manage the objects in this set, so as to reduce the management costs of the
administrators.
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.
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.
3-12 Version: B
3 Basic Function of the UNM2000
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.
u During the process of network operation and maintenance, the network
administrator can log in the UNM2000 as an advanced administrator and
monitor the entire network. If the operation of a user at a lower level is abnormal,
the administrator can force the user to log out (when the user logs out, the
UNM2000 can save its topology automatically), so as to guarantee the security
of the system operation.
Version: B 3-13
UNM2000 Network Convergence Management System Product Description
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. Users
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, 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.
Log Management
The UNM2000 provides the operation log, system log, security log and NE log. After
logging into the UNM2000 as the advanced administrator, the network manager can
learn of all the logged-in accounts and all the commands they have executed by
checking the corresponding logs. This can help detect the potential threats and
handle them in a timely manner to ensure the network security.
3-14 Version: B
4 System Architecture
The following introduces the software architecture and external ports of the
UNM2000.
Software Architecture
External Port
Version: B 4-1
UNM2000 Network Convergence Management System Product Description
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 Architecture
4.2 External Port
The UNM2000 supports the communication between the SNMP southbound
interface and the equipment.
4-2 Version: B
5 Technical Specifications
The following introduces the technical specifications of the UNM2000.
Management Capacity
Performance Specifications
External Server Port
Standards
Version: B 5-1
UNM2000 NetworkConvergence Management System Product Description
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
Alarm query delay
u Number of records≤10000:2s
u 10000＜Number of records≤100000:8s
u 100000≤Number of records:20s
Alarm handling capability ≥100 alarms per second
Performance response delay ＜10s
5-2 Version: B
5 Technical Specifications
Table 5-1 List of Performance Specifications (Continued)
Item Specification
Performance query delay
u Number of records≤10000:2s
u 10000＜Number of records≤100000:8s
u 100000≤Number of records:20s
Maximum number of
performance objects to be
counted
10000
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.
Version: B 5-3
UNM2000 Network Convergence Management System Product Description
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.
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
5-4 Version: B
5 Technical Specifications
Table 5-2 Description of External Server Port (Continued)
Destination Port Process of Destination Port Port Description
52203 iceboxd Service configuration service
52201 iceboxd Global service configuration service
52202 iceboxd Timing task management service
52252 iceboxd
Extension service of the northbound
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.
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: B 5-5
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 Gate Network Element
GUI Graphic User Interface
IP Internet Protocol
ITU-T
International Telecommunication Union-
Telecommunication Standardization Sector
NE Network Element
NEL Network Element Level
NML Network Management Layer
NMS Network Management System
OLT Optical Line Terminal
ONT Optical Network Terminal
ONU Optical Network Unit
SML Service Management Layer
SMS Service Management System
TCP Transfer Control Protocol
TL1 Transaction Language 1
TMN Telecommunications Management Network
UDP User Datagram Protocol
UPS Uninterrupted Power System
Version: B A-1
Product Documentation Customer Satisfaction Survery
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
	Thank you for choosing our products. 
	Legal Notice 
	Preface 
	Related Documentation 
	Version 
	Intended Readers 
	Conventions 
	Operation Safety Rules 
	Contents 
	Figures 
	Tables 
	1 Overview 
	1.1 Product Positioning 
	1.1.1 Deployment of the UNM2000 in the TMN 
	1.1.2 Manageable Device Types 
	1.2 Product Feature 
	1.3 System Configuration Requirements 
	1.3.1 Hardware Configuration Requirements 
	1.3.2 Software Configuration Requirement 
	2 Network and Application 
	2.1 UNM2000 Deployment Mode 
	2.1.1 Single-server Centralized Deployment Mode 
	2.1.2 Single-system Distributed Deployment Mode 
	2.1.3 Cluster Disaster Tolerance Centralized Deployment Mode 
	2.1.4 Cluster Disaster Tolerance Distributed Deployment Mode 
	2.2 Network Mode between the UNM2000 and NE 
	2.3 Network Example 
	3 Basic Function of the UNM2000 
	3.1 Configuration Management 
	3.2 Topology Management 
	3.3 Alarm Management 
	3.4 Event Management 
	3.5 Performance Management 
	3.6 Security Management 
	4 System Architecture 
	4.1 Software Architecture 
	4.2 External Port 
	5 Technical Specifications 
	5.1 Management Capacity 
	5.2 Performance Specifications 
	5.3 External Server Port 
	5.4 Standards 
	Appendix A Abbreviations