Related Documentation

Phase to
Document Main Content
Use

UNM2000 Network Convergence Introduces the product positioning, features, basic

Network
Management System V2R7 Product functions, network and application, and technical
planning
Description specification.

Terminology Conventions

Terminology Convention

UNM2000 FiberHome UNM2000 Network Convergence Management System

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

New Features
This chapter introduces the newly developed highlights and features of the UNM2000 V2R7.

◆  The UNM2000, PAS and PON traffic tool fully support IPv4 and IPv6 dual-stack management.

◆  Optimizes the resource statistics function.

►  Supports collecting networkwide statistics of the ONU weak optical power, enabling
clients to maintain the ONU weak optical power conveniently.

►  Supports automatically synchronizing the data of the newly added OLTs with the
resource statistics export task. This requires fewer manual operations.

►  Supports collecting statistics of and exporting PON port running status, OLT online
status and ONU port uplink / downlink rate configurations, etc. This meets users'
statistics requirements.

◆  Supports deleting NEs and automatically upgrading ONUs, improving users' operation efficiency.

◆  Supports customizing quick access for ONU service provisioning, managing hand-in-hand topologies
and optimizing the intensive merge tool.

◆  Enhances the License management and control capability, specifically, the license supports controlling
 TL command sets and their usage time.

◆  Optimizes the PON traffic tool function.

►  Supports second-level traffic and traffic statistics of MSAN devices (AN5516 MSAN
common platform devices and AN5220 devices).

►  Optimizes the report export function; supports exporting data reports and statistics
and analysis graphs simultaneously.

►  Supports collecting statistics of uplink / downlink CRC errors of OLT uplink ports
and PON ports to help analyze the failure reason of the PON network.

►  Supports collecting statistics of and analyzing the traffic load of the OLT uplink ports
and PON ports, providing basic data for the planning of the uplink ports and user
resources.

►  Provides bandwidth utilization rankings, traffic analysis reports and link bandwidth
utilization reports for the OLT uplink ports, OLT PON ports and ONU PON ports.
This helps users analyze the traffic.

►  Provides area statistics and analysis function; collects statistics of and analyzes traffic
and physical resources by area.

◆  Supports the AN6000 V1R2 version.

Deployment of the UNM2000 in the TMN

The TMN provides hierarchical network architecture and standard network interfaces. It is composed of the business
management layer (BML), the network management layer (NML), and the element management layer (EML). This type
of composition is called the network management architecture of the TMN.
The UNM2000 is located at the NML and EML in the TMN architecture and manages the devices in the access network,
transport network and IP network, as shown in Figure 1 .

Figure 1   Deployment of the UNM2000 in the TMN

Manageable Device Types

Table 1 lists the devices that can be managed by the UNM2000 V2R7.

Table 1    Manageable Devices

Type Device Model

OLT AN5516-04, AN5516-06, AN5116-02, AN5116-04B, AN5116-06B, AN6000-17 and AN6001-G16

◆  GPON: AN5506-02-D/F, AN5506-04-B2/D/F1/FA/FAT, AN5506-07A/09A/10A

and AN5506-07B/09B/10B.

◆  XGPON: AN5646T/Q, AN5656T, AN5221-8N/16N/24N and

AN5231-8N/16N/24N.

ONU ◆  EPON: AN5006-07A/09A/10A and AN5006-07B/09B/10B.

◆  10GEPON: AN5200-07A/09A/10A and AN5200-07B/09B/10B.

◆  HG6243C, HG6245D, HG6021C, HG6543C, HG6145E, HG6245P, HG6244C,

HG6249A, HG5245ST and HG5245SH.

MSAN AN5006-20, AN5006-30, AN5006-15, AN5006-16, AN5220 and AN5516.

Product Features
The UNM2000 improves the management capability, scalability and usability, providing a new generation of client-
oriented network management system.

Powerful Management Capability

The UNM2000 improves the management capability using the distributed deployment and flexibly controls the
management modules using the License function.

◆  The UNM2000 supports the single-server centralized deployment mode, single-system distributed
deployment mode, cluster disaster tolerance centralized deployment mode and cluster disaster
tolerance distributed deployment mode.

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

◆  The UNM2000 flexibly controls the functions and management capability using the License function, so
as to meet various requirements of subscribers. The license will not be influenced by any changes of
the network card.

Flexible Scalability
The UNM2000 employs an industry-leading scalable modularized architecture design to support the distributed and
hierarchical database modules, service configuration processing modules and common modules.

◆  The functional modules can be separated or combined, which meets users' customization
requirement.

◆  The loose coupling between functional modules enables users to upgrade and maintain modules
independently.

Better User Experience

The UNM2000 provides a new generation of the client-oriented network management system.

◆  The UNM2000 provides completely new user experience through the CLI and Web login modes.

◆  The UNM2000 keeps the consistent GUI style for each device using modularized design.

Compatible with Multiple Operating Systems

As an independent application, the UNM2000 can be installed in different operation systems based on different databases.
The UNM2000 cannot only provide high-end resolution for the large-scale network, but also provide low-cost resolution
for small- to medium-sized network.

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

◆  The UNM2000 supports the MySQL, Oracle and SQLServer databases to meet different requirements
for users.
Standard and Unified Interface
The UNM2000 provides the standard and unified southbound and northbound interfaces, which completely meet the
requirements for the industry mainstream OSS integration.

◆  The functions of the unified southbound and northbound interfaces can cover all devices in the
network managed by the UNM2000.

◆  The southbound and northbound interfaces use the industry-leading interface standard, which makes
the interface maintenance cost-effective. The interfaces can be extended and support diversified
deployment.

System Architecture

Software Architecture
The UNM2000 adopts the client end - server mode. Figure 1 shows the software architecture of the main modules in the
system.

Figure 1   UNM2000 Software Structure

External Interface
The external interface is the channel for communication and data interaction between the UNM2000 and the external
system. The UNM2000 provides the northbound interface and southbound interface to manage devices and help network
operators implement quick integration of the OSS and the UNM2000, improving customer service quality.

Northbound Interface
The UNM2000 northbound interface provides the network monitoring information, such as alarms, inventory and
performance, for the OSS system. Meanwhile, it supports the network management functions, such as service
configuration and notification reporting. The UNM2000 can implement quick integration with OSS systems through the
UNM2000 northbound interface.

The UNM2000 supports the TL1, CORBA, WebService, Socket and SNMP northbound interfaces.

Southbound Interface
The UNM2000 is connected with the devices through the southbound interface so that the UNM2000 can manage the
devices.

The connection between the UNM2000 and devices uses the SNMP, FTP / SFTP / TFTP and Telnet / SSH protocols.

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.

Centralized Deployment Mode

The centralized deployment mode adopts the network scheme of multiple client ends - single server. In this mode, only
one UNM2000 server supports the access and operation of multiple client ends. This mode provides easy deployment
scheme and the cost is relatively low, which is applicable for medium and small-scale network. Figure 1 shows the
network diagram.
Figure 1   Centralized Deployment Mode

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 1 shows the network in
this deployment mode.

Figure 1   Distributed Deployment Mode

Cluster Disaster Tolerance Centralized Deployment Mode
The cluster disaster tolerance centralized deployment mode includes one active server and one standby server. When the
active sever is faulty, the system will be switched to the standby server to keep on the network monitoring, so as to
guarantee the uninterruptible system operation.

According to the deployment location of the active and standby servers, the cluster disaster tolerance centralized
deployment falls into local deployment and remote deployment.

◆  Local deployment: The active and standby servers are deployed in the same location, which are
connected to the disk array using optical fiber connection. Figure 1 shows the network diagram.

◆  Remote deployment: The active and standby servers are deployed in different locations (equipment
rooms or cities), which are connected to their respective disk array. Figure 2 shows the network
diagram.

Figure 1   Local Centralized Deployment Mode of Cluster Disaster Tolerance

Figure 2   Remote Centralized Deployment Mode of Cluster Disaster Tolerance
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.

According to the deployment location of the active and standby servers, the cluster disaster tolerance distributed
deployment falls into local deployment and remote deployment.

◆  Local deployment: The active and standby servers are deployed in the same location, which are
connected to the disk array using optical fiber connection. Figure 1 shows the network diagram.

◆  Remote deployment: The active and standby servers are deployed in different locations (equipment
rooms or cities), which are connected to their respective disk array. Figure 2 shows the network
diagram.

Figure 1   Local Distributed Deployment Mode of Cluster Disaster Tolerance

Figure 2   Remote Distributed Deployment Mode of Cluster Disaster Tolerance

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.

◆  Advantage: the network is flexible without any additional equipment, so that the cost is relatively low.

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

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

◆  Disadvantage: The network is relatively complex. It is required to add devices (maintenance channel)
and the network construction cost is relatively high.

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

Figure 1   Network Example

Technical Specifications
This chapter introduces the technical specifications of the UNM2000.

Management Capacity
Each UNM2000 can manage 100 thousand NEs.

Performance Specification
This section introduces the performance parameters supported by the UNM2000, including the startup / shutoff time,
number of simultaneous client logins, alarm / log capacity and processing capability, etc.

Performance Specification List

Table 1 shows the performance specifications of the UNM2000.

Table 1    Performance Specification List

Item Specification

UNM2000 startup time < 10 minutes

UNM2000 shutoff time ≤ 10 seconds

Concurrent client ends ≥ 500

Number of users admitted ≥ 2000

Number of online users ≥ 1000

Number of user groups admitted 50

Number of object groups admitted 100

Number of operation groups admitted 255

System homepage delay ≤ 10 seconds

Response time delay of a single operation ≤ 2 seconds

Response time delay of batch operations ≤ 5 seconds

Report generation time delay ≤ 8 seconds

Alarm throughput ≥ 1000 entries / second

Alarm response delay ≤ 10 seconds

Item Specification

◆  Number of records ≤ 10000: 2s

◆  10000 < number of

Alarm query delay records ≤ 100000: 8s

◆  100000 ≤ number of records: 20s

Alarm handling capability ≥ 100 entries / second

Performance statistics delay < 2 minutes

Performance response delay < 10s

◆  Number of records ≤ 10000: 2s

◆  10000 < number of

Performance query delay records ≤ 100000: 8s

◆  100000 ≤ number of records: 20s

Maximum number of performance objects to be

10000
counted

Configuration synchronization time delay < 2 minutes

Data export time delay ≤ 2 minutes/100M

Configuration storage duration Long-term operation

Current alarm storage capacity ≥ 500 000

Historical alarm storage capacity ≥ entries over three months

5-minute historical performance storage

≥ entries over one month
capacity

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

60-min historical performance storage capacity ≥ entries over one year

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

 Item Specification

Storage capacity of operation logs ≥ entries over six months

Storage capacity of monitoring data ≥ entries over six months

Packet Loss Rate and Performance of the UNM2000

High packet loss rate of the network will cause performance degradation of the UNM2000 and lower the success rate of
the UNM2000 in service distribution.

◆  When the network packet loss rate is lower than 10%, the success rate of the UNM2000 in service
distribution is not lowered visibly.

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

◆  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

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

◆  If the server manages more than 1000 OLTs and accesses 128 client ends, the bandwidth of the
communication between the server and each client end should be no less than 1G.

Server-Northbound Interface Bandwidth Requirements

◆  The bandwidth for the communication between the server and the northbound interface for the TL1
service should be no less than 100M.

◆  The bandwidth for the communication between the server and the CORBA northbound interface
should be no less than 100M.

◆  The bandwidth for the communication between the server and the WebService northbound interface
should be no less than 100M.

◆  The bandwidth for the communication between the server and the superior network management
system should be no less than 100M.

Standards
This section introduces the standards and protocols followed by the UNM2000.

◆  The interfaces between the UNM2000 and equipment comply with RFC standards such
as SNMP and MIB-II.

◆  Supports RFC Telnet/TCP/IP standards.

 ◆  Supports IETE RFC1901-1908 standards.

◆  Supports standards relevant to telecommunication management network such as ITU-T

M.3010, ITU-T M.3100, ITU-T M.3400 and ITU-T.X.721.

◆  The CORBA northbound interface complies with the TMF MTNM series standards.

◆  The WebService northbound interface supports the MTOSI 2.0 standard.

◆  The Socket northbound interface complies with the OMC system function specifications,
OMC system general technical specifications and OMC system northbound interface data
specifications.

◆  The TL1 service supports DSLForumTR-069, DSLForumWT-142 and SFF-8472 standards.

External Service Ports

If the firewall is deployed in the network, users should enable the external service ports of the UNM2000 to ensure the
normal communication. The external service ports used by the UNM2000 are listed below.

See tables 1-6

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

Operation Guide

Installation Guide