UMC²

Unified Management Control

Centre V1R5

Product Description (PON)

Version: A/02

Code: MN000006078

FiberHome Telecommunication Technologies Co., Ltd.

December 2023
Copyright © FiberHome Telecommunication Technologies Co., Ltd. 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.

Trademarks and Permissions

and other FiberHome trademarks are trademarks of FiberHome Telecommunication Technologies

Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.

General Disclaimer

All or part of the products, services and features described in this document may not be within your purchase
scope or usage scope. In case of inconsistency, the contract shall prevail.

The information in this document may contain predictive statements. Actual results may differ materially from
those expressed or implied in predictive statements due to numerous factors. Therefore, such information is
provided for reference purpose only and constitutes neither an offer nor an acceptance.

Information in this document is subject to change without notice due to upgrade or other needs.

FiberHome Telecommunication Technologies Co., Ltd.

Address: No.6, Gaoxinsilu, High-Tech Development Zone, Wuhan, Hubei Province, P. R. China
Postcode: 430205
Website: http://www.fiberhome.com
Tel: +86 800-8800787; +86 400-8890787
 Preface

This document describes the positioning, architecture, operating environment, deployment

schemes, functions, features, and technical specifications of the UMC2 Unified
Management Control Centre. It helps readers get a comprehensive and in-depth
understanding of the product's network applications and technical parameters.

This document is intended for network planning engineers, system engineers, technical
support engineers and maintenance engineers.

Version

Version Description

A/02 Initial version for the UMC2 V1R5 (PON)

Symbol Conventions

Symbol Convention Description

Note Important features or operation guide.

Possible injury to persons or systems, or cause traffic interruption or

Caution
loss.

Warning May cause severe bodily injuries.

Contents

Preface ................................................................................................................... I

1 Overview ........................................................................................................1

1.1 Positioning.........................................................................................1

1.2 Highlights ..........................................................................................3

1.2.1 Unified Management-Control Platform ....................................3

1.2.2 Centralized Network Control ..................................................4
1.2.3 Intelligent and Easy OAM ......................................................5
1.2.4 Open Southbound and Northbound Interfaces ...........................6

1.3 New Features......................................................................................6

2 Architecture ...................................................................................................8

2.1 Software Architecture ..........................................................................8

2.2 Northbound Interfaces .........................................................................9

2.2.1 CORBA Interface..................................................................9

2.2.2 Socket Interface .................................................................. 10
2.2.3 XML Interface .................................................................... 13
2.2.4 SNMP Interface .................................................................. 14
2.2.5 TL1 Interface...................................................................... 15
2.2.6 REST Open API ................................................................. 16
2.2.7 WebService Interface ........................................................... 17

2.3 Southbound Interfaces ....................................................................... 18

3 Running Environment ................................................................................... 19

3.1 Hardware Environment ...................................................................... 19

3.2 Software Environment ....................................................................... 22

4 Deployment Schemes................................................................................... 25

4.1 Server Deployment Schemes .............................................................. 25

4.1.1 Centralized Deployment....................................................... 25

4.1.2 Distributed Deployment ....................................................... 26

4.2 Client Deployment Schemes ............................................................... 28

5 Functions ..................................................................................................... 30

5.1 Overview ......................................................................................... 30

5.2 Network Management........................................................................ 31

5.2.1 Security Management .......................................................... 31

5.2.2 Topology Management ........................................................ 38
5.2.3 Alarm Management ............................................................. 40
5.2.4 Performance Management .................................................... 47
5.2.5 Log Management ................................................................ 49
5.2.6 Resource Management......................................................... 50
5.2.7 Report Management ............................................................ 52
5.2.8 Configuration Management .................................................. 53
5.2.9 System Monitoring and Maintenance ..................................... 56
5.2.10 Access Network Management ............................................... 58

5.3 Network Analysis.............................................................................. 61

5.3.1 Network Traffic Analysis ..................................................... 61

5.3.2 Network Resource Analysis.................................................. 63
5.3.3 Network Quality Analysis .................................................... 68

6 Reliability ..................................................................................................... 71

6.1 Reliability Design ............................................................................. 71

6.1.1 Hardware Reliability............................................................ 71

6.1.2 Software Reliability............................................................. 73

6.2 Hot-Standby Disaster Recovery Scheme............................................... 75

6.3 DCN Protection Scheme .................................................................... 75

7 Technical Specifications .............................................................................. 77

7.1 Performance Specifications................................................................. 77

7.2 Management Capability ..................................................................... 79

7.2.1 Management Capacity ......................................................... 79

7.2.2 Equivalent Coefficient ......................................................... 79

8 PON Series ................................................................................................... 85

Appendix A Standard Compliance ............................................................... 88

Appendix B Service Ports ............................................................................ 90

Appendix C Abbreviations ......................................................................... 102

1 Overview

The UMC2 is a cloud-based unified management control centre developed by FiberHome

that integrates powerful network management, control and analysis. This chapter introduces
the positioning and features of the UMC2.

1.1 Positioning

This section introduces the positioning of the UMC2 Unified Management Control Centre.

Challenges

As the Internet industry rapidly develops and the cloud era dawns, network and information
services are provisioned not only to public users, but also to more and more traditional
businesses and industries. In this context, emerging technologies are sprouting up, such as
software-defined networking (SDN), network function virtualization (NFV), ultra
broadband network, cloud computing, big data and artificial intelligence (AI). This is
driving a new wave of innovation in network and information service infrastructures.

Nowadays, traditional network operations face the following challenges:

u Traditional networks are rigid, making it costly and time-consuming to expand

capacity. This fails to meet the elasticity demands of Internet, cloud computing and
Internet of things (IoT).

u Network services are provided by multiple professional networks with different

functions. However, their functions are fragmented severely with varying performance,
making it difficult to deploy and optimize end-to-end services.

u With ever-growing and unbalanced traffic, infrastructure networks are unable to

interact flexibly with cloud-based resource pools, and hence cannot allocate resources
on demand in a unified manner.

u Business growth leads to increasingly complex network architectures and topologies.

This necessitates automatic deployment, protection and OAM to cut OPEX.

To address these challenges, a new OAM platform that integrates management and control
is required between service apps and infrastructure networks. Such platform:

Version: A/02 1
UMC² Unified Management Control Centre V1R5 Product Description (PON)

u Enables automatic cloud-based deployment, flexible expansion and ready access based
on cloud-native microservice architecture.

u Integrates the functions of traditional network management system, SDN controller

and integrated OAM system, minimizing interaction and adaptation between
management and control and allowing management-control continuum and resource
sharing.

u Allocates and customizes network resources and capabilities through standard and
open interfaces, allowing continuous and fast innovation of services and apps.

Positioning

The figure below shows the positioning of the UMC² in a network.

Figure 1-1 Network Positioning

2 Version: A/02
 1 Overview

As a unified management-control system, the UMC2 abstracts physical-layer device

information, obtains network resources through standard southbound interfaces, and sends
control commands to physical-layer devices. It can adjust networks promptly in case of
network status changes, keeping services secure.

u The UMC2 manages and controls IP, transport and access devices at the lower layer,
and enables resource management, service configuration, protection and recovery
control, and OAM analysis.

u The UMC2 provides open northbound interfaces for the upper layer to integrate or
interconnect with OSSs, BSSs and service coordinators, and allows fast custom
development at the application layer.

1.2 Highlights

The UMC2 is a cloud-based unified management control centre developed by FiberHome

that integrates powerful network management, control and analysis.

1.2.1 Unified Management-Control Platform

The UMC2 incorporates the functions of a traditional network management system and an
SDN controller, enabling unified management and control of traditional networks and SDN
networks. With a unified network architecture and data model, the UMC 2 maximizes the
value of networks and allows networks to evolve in an easy and secure way.

Uniform GUI

u Uniform global topology and service configuration / management GUIs, allowing

unified management of existing networks and SDN networks

u Uniform alarm, performance, configuration and security management GUIs, delivering

superior OAM experience

Open Platform

u Fully open network platform, enabling flexible scheduling and customization of

network resources and capabilities

u Standard Restful northbound interfaces, enabling usage of upper-layer apps and

unified adaptation to lower-layer functions

Version: A/02 3
UMC² Unified Management Control Centre V1R5 Product Description (PON)

u SDN-oriented southbound interfaces, blocking the differences among infrastructure

resources and simplifying management and configuration of devices at the bottom
layer

Fast Deployment

u Service-oriented architecture system built on a cloud resource platform, allowing

automatic cloud deployment of servers

u Flexible scheduling of resources from resource pools for capacity expansion, and load
sharing by dynamically adjusting system pressure

u Automatic system upgrade and canary release of functions, catering for flexible and
variable upgrade requirements

High Security and Reliability

u Comprehensive security measures such as OS hardening, session encryption, anti-virus

and anti-spyware protections, system security scanning, and secondary authentication,
jointly assuring the security of network devices and the UMC²

u Effective control and flexible authority- and domain-based management, preventing

unauthorized access and keeping devices and the UMC² secure

u Multi-level protections for hardware, software and systems, minimizing possible

system damages and fulfilling high reliability

1.2.2 Centralized Network Control

The UMC2 offers an integrated solution for centralized network control, reducing skill
dependency and enabling agile service provisioning and better user experience.

Automatic Resource Discovery

The UMC² automatically discovers network resources such as NEs, subracks, cards and
ONUs, speeding up device deployment and capacity expansion.

ONU / OLT Pre-deployment

u ONU pre-deployment: pre-deploys offline ONUs in batches, making them plug-and-

play and free of commissioning.

4 Version: A/02
 1 Overview

u OLT pre-deployment: allows automatic configuration of OLTs, making them free of

commissioning after OLT hardware is installed on site.

1.2.3 Intelligent and Easy OAM

The UMC2 collects networkwide data in real time. Based on artificial intelligence and big
data technologies, it enables efficient OAM by effectively monitoring network traffic and
quality, accurately perceiving network trends, quickly identifying root causes of failures,
and timely giving warnings on performance deterioration and threshold-crossing traffic.

Network Traffic Measurement

The UMC² visualizes traffic distribution in areas, helping users quickly detect areas that
need special attention, grasp regional traffic trends, and identify hot services.

u Provides a traffic topology that visualizes traffic and quality distribution in areas,
enabling real-time monitoring of the entire network.

u Monitors the flow rate or bandwidth usage of a specified network resource in seconds
or minutes, helping network operators diagnose service failures efficiently.

u Monitors the performance indicators (flow rate and bandwidth usage) of networkwide
objects, marks threshold-crossing objects with tokens, and removes tokens from
objects that resume normal status, prompting maintainers to handle exceptions timely
to minimize impact on user services.

Network Resource Visualization

The UMC² displays the distribution and usage of network resources graphically, and
analyzes the usages of networkwide resources, helping users identify resource bottlenecks
and plan future capacity expansion.

u Collects physical and logical resource data, helping users understand the usages of
NEs, cards, ports, and other resources intuitively.

u Inspects network resource configuration and status automatically, outputs inspection

reports, and gives warnings timely, enabling users to regularly check and detect
abnormal objects in network resources, and hence quickly adjust network resources
and avoid possible failures and risks.

Version: A/02 5
UMC² Unified Management Control Centre V1R5 Product Description (PON)

u Checks the operation of OLTs, ONUs and cards to help users identify device
abnormalities in time, ensuring smooth service flow and secure network operation.

Network Quality Inspection

The UMC² detects various performance indicators and alarms in networks, such as
performance events and threshold-crossing alarms related to optical power, informing users
of changes in service bearer quality in real time.

u Analyzes optical power in multiple dimensions, and provides real-time optical power
measurement reports, optical power trend analysis and abnormal optical power
analysis. This helps users timely identify deterioration trends and take measures
accordingly for assured network quality.

u Reproduces the service path from an alarm source to an alarm destination, reads the
parameters of existing tests or those initiated on demand, and then delimits failures
based on test results, all in a hop-by-hop way.

1.2.4 Open Southbound and Northbound Interfaces

The UMC2 provides diverse open interfaces to productize network services and enable
coordinated innovation in the industry chain.

u Standard Restful northbound interfaces, providing open network management such as

resource / topology management and service configuration / maintenance for the upper
layer

u Standard and open northbound interfaces, through which innovative service apps can
be customized quickly for variable commercial scenarios and intelligent OAM

u Southbound interfaces connecting and managing physical-layer network devices

1.3 New Features

This system manages access network devices with the following features.

6 Version: A/02
 1 Overview

Feature Description

Optimized user security management

u Modifying and exporting user information in batches
u Viewing the user group where a user belongs or the users included in a
user group
User management
u Authority- and domain-specific management of REST Open API and TL1
northbound interface users
u Managing service password security of user groups
u Locking users and marking silent status

Web management of ODN topology views, which can be customized to get

ODN topology view real-time link / device states, and PON links' upstream / downstream traffic and
bandwidth usages.

Querying TL1 connection status, including TL1 thread mode, maximum

TL1 connection status
number of connections, actual number of connections, and connection / queue
query
details
Batch configuration Configuring and delivering TL1 commands in batches through importing a
of TL1 commands template

VEIP service
Collecting VEIP services' configuration data and enable status in a specified
configuration
range
statistics
Rack resource
Collecting rack resource data in a specified range
statistics

Version: A/02 7
2 Architecture

This chapter introduces the software architecture and southbound / northbound interfaces of
the UMC2.

2.1 Software Architecture

The UMC2 is a service-based modular network management system running on a cloud

platform. It comprises multiple logical modules such as network management, control and
analysis, and can be deployed in a flexible and modular way according to customers’
requirements. The figure below shows the software architecture of the UMC 2.

Figure 2-1 Software Architecture

The table below describes the main logical modules of the UMC2.

8 Version: A/02
 2 Architecture

Module Description
Manages alarms, configurations, resources, performance and security of devices, and
Management processes and stores massive information, providing support for upper-layer decision
making.

Provides unified abstract model and management for device resources and blocks their
Control
differences, enabling fast service provisioning and maintenance on different devices.

Provides a closed-loop OAM system that consists of network traffic analysis, resource
Analysis analysis, quality analysis and survivability analysis. It can detect potential risks and
give warnings and optimization suggestions based on AI and big data analysis.

2.2 Northbound Interfaces

The UMC2 northbound interfaces provide abundant network management and control
functions such as resource management, alarm management, performance management,
service provisioning, and testing & diagnosis for upper-layer network management systems
(NMSs). They enables fast and flexible integration with different upper-layer NMSs,
delivering premium QoS for customers.

2.2.1 CORBA Interface

This section introduces the protocol, performance specifications and functions of the UMC 2
CORBA northbound interface.

Interface Protocol

GIOP

Performance Specifications

Table 2-1 Performance Specifications of the CORBA Interface

Item Specification
Alarm reporting efficiency ≥ 500 entries/second
Alarm cache capacity in case of alarm storm ≥ 100 000 entries
Delay in querying a single configuration entry via the UMC² ≤ 1 second
Data returned ≤ 100 entries ≤ 3 seconds
Delay in querying batch data
100 entries < data returned ≤
via the UMC² ≤ 5 seconds
1000 entries

Version: A/02 9
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 2-1 Performance Specifications of the CORBA Interface (Continued)

Item Specification

Data returned ＞ 1000 entries ≤ 5 seconds per 1000 entries

Delay in generating full configuration files for 10 000 equivalent

< 90 minutes
NEs
Number of clients running tests concurrently ≥5

Functions

Table 2-2 Functions of the CORBA Interface

Category Function

Manage communication connections by ping, end sessions, query the

information of all supported managers, query the information of a specified
Common functions manager, obtain the event reporting channel, obtain the information of session
objects, obtain the information of the CORBA version compliant with TMF
specifications, query heartbeat parameters, etc.

Report alarms, synchronize alarms, query alarms, block alarms, filter alarms,
Alarm management
etc.
Performance
Query current / history performance, etc.
management

Notification and Send notifications for object creation / deletion, attribute change and status
event management change, file transfer status in pull mode or FTP mode, heartbeat reporting, etc.

2.2.2 Socket Interface

This section introduces the protocol, data format, performance specifications and functions
of the UMC2 Socket northbound interface.

Interface Protocol

u Resource data interface: SFTP / FTP

u Performance data interface: SFTP / FTP

u Alarm data interface:

4 Real-time alarm: Socket / TCP

4 Batch alarms: SFTP / FTP

10 Version: A/02
 2 Architecture

Data Format

u Resource data interface: XML

u Performance data interface: CSV

u Alarm data interface:

4 The message body of real-time alarm reports is in JSON format.

4 The alarm synchronization file is in TXT format. Each alarm message (alarm
generation or clearing) in the file is in JSON format.

Performance Specifications

Table 2-3 Performance Specifications of the Resource Data Interface

Item Meaning Specification

Number of required fields of the interface/total number of required fields of
= 100%
the UMC2 × 100%
Field integrity
Number of optional fields of the interface/total number of optional fields of
≥ 90%
the UMC2 × 100%
Number of records on the interface/number of records on the UMC 2 ×
Record integrity ≥ 99%
100%
Full data: delay in generating full resource files = time when file generation
≤ 30 minutes
ends - time when file generation starts (0 or 12 o'clock)
Data delay
Incremental data: delay in generating an incremental data file = time when
file generation ends - time when file generation starts (at X0 or X5 minutes) ≤ 1 minute
Note 1

Data storage duration Duration for storing resource interface data files ≥ 7 days

Concurrent connections Number of concurrent FTP client connections ≥ 10

The values of fields for various resource objects must be correctly
Correctness of data associated if any association exists.
≥ 99%
association Correctness of data association = number of records with consistent data
association/total number of records × 100%
Note 1: An incremental data interface generates a file every five minutes. That is, when the minute value of the current time
ends with 0 or 5, a new incremental resource file is generated based on resource data changes (adding, deletion or
modification) over last five minutes.

Table 2-4 Performance Specifications of the Performance Data Interface

Item Meaning Specification

Number of required fields of the interface/total number of required fields of
Field integrity ≥ 99.5%
the UMC2 × 100%

Version: A/02 11
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 2-4 Performance Specifications of the Performance Data Interface (Continued)

Item Meaning Specification

Number of optional fields of the interface/total number of optional fields of
≥ 90%
the UMC2 × 100%
Number of records on the interface/number of records on the UMC 2 ×
Record integrity ≥ 99%
100%
Delay in generating a performance measurement file = time when file
Performance data delay ≤ 10 minutes
generation ends - time when a performance measurement period ends

Proportion of Proportion of supplementary data collection records = number of

supplementary data supplementary data collection records over a period/total number of records ≤ 1%
collection records over the same period on the UMC2 × 100%

Number of resource object rmUIDs in performance data that can be

Data object consistency matched in resource data/total number of resource object rmUIDs in ≥ 99%
performance data

Data storage duration Duration for storing performance interface data files ≥ 7 days

Concurrent connections Number of concurrent FTP client connections ≥ 10

Delay of data reported over the first measurement period after a new NE
New NE access report
accesses the network = start time of measurement data first reported - ＜ 15 minutes
delay
network access time of the new NE
Delay of data reported over the first measurement period after an NE
NE recovery report delay recovers = end time of measurement data first reported after recovery - ＜ 15 minutes
recovery time of the NE

Table 2-5 Performance Specifications of the Alarm Data Interface

Item Meaning Specification

Number of alarms received by an upper-layer NMS/number of alarms on

Alarm integrity = 100%
the UMC2 × 100%
Alarm delay Time when the UMC2 sends an alarm - alarm occurrence time ≤ 5 seconds
Number of alarms output by the northbound interface in correct time
sequence/total number of alarms × 100%. The time sequence of alarms
Alarm time sequence = 100%
output by the northbound interface must be consistent with that of alarms
received by the UMC2.

Number of resource object rmUIDs in alarm data that can be matched in

Data object consistency ≥ 99%
resource data/total number of resource object rmUIDs in alarm data

Alarm interface Capability of the UMC2 to report full alarm messages (including active and ≥ 1000 entries/
throughput rate cleared alarms) in real time to each upper-layer NMS second
Delay in generating an
Time for packing 10 000 current active alarms as an interface file ≤ 5 seconds
current active alarm file

12 Version: A/02
 2 Architecture

Table 2-5 Performance Specifications of the Alarm Data Interface (Continued)

Item Meaning Specification

Number of alarm entries Number of real-time alarm entries cached by the UMC2 interface for
≥ 1000 entries
cached in real time synchronizing alarms by messages in case of a transient network failure

Concurrent alarm
Number of upper-layer NMSs that receive alarms ≥ 10
connections
Concurrent FTP
Number of concurrent FTP client connections ≥5
connections
Data storage duration Duration for storing alarm interface data files ≥ 7 days
NE access or recovery Number of alarms reported to an upper-layer NMS after an NE accesses the
= 100%
alarm integrity network or recovers from a failure/number of alarms on the UMC 2 × 100%

Table 2-6 Reliability Requirements for Interfaces

Item Specification

Availability ≥ 99.9% (7 × 24)

Mean time to repair (MTTR) ≤ 2 hours

Mean time between repairs (MTBR) ≤ 3 times/year

Functions

Table 2-7 Functions of the Socket Interface

Function Description
Resource Exports resource data on the UMC2 as an XML file to an FTP server at a scheduled
management time.
Performance Exports performance data on the UMC2 as a CSV file to an FTP server
management automatically.

Alarm
Reports alarms in real time, and synchronizes alarms by messages or by files.
management

2.2.3 XML Interface

This section introduces the protocol, data format, performance specifications and functions
of the UMC2 XML interface.

Interface Protocol

SOAP

Version: A/02 13
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Data Format

XML

Performance Specifications

Table 2-8 Performance Specifications of the Access Domain XML Interface

Item Meaning Specification

Response delay from the start of one operation

GUI response delay ≤ 2 seconds
to the display of result feedbacks

Response delay for querying one specified

Response delay for querying ≤ 3 seconds
device / card / port
device / card / port
Response delay for querying all cards of a
information ≤ 60 seconds
specified device

Functions

Table 2-9 Functions of the Access Domain XML Interface

Category Function
Configuration Adds / removes / configures ONUs, activates / deactivates ports (such as ONU
management data and voice ports), and binds / unbinds QinQ domain templates.
Resource Queries basic resource information, such as the basic configurations, status,
management optical module information and LAN port status of an ONU.

2.2.4 SNMP Interface

This section introduces the protocol, performance specifications and functions of the UMC 2
SNMP northbound interface.

Interface Protocol

SNMP v1 / v2c / v3

14 Version: A/02
 2 Architecture

Performance Specifications

Table 2-10 Performance Specifications of the SNMP Interface

Item Meaning Specification

Delay in reporting Time interval from reception of device alarms by the

≤ 10 seconds
alarms UMC2 to reception of alarms by an NMS

Time required to
Time required to refresh the current performance table on
refresh current ≤ 5 minutes
the UMC2
performance

Performance query
Time required to complete performance query ≤ 15 minutes
time

Functions

Table 2-11 Functions of the SNMP Interface

Category Function
Reports alarms in real time, and queries current alarms and alarms in a specified
Alarm management
time period.

Performance
Queries current performance.
management

2.2.5 TL1 Interface

This section introduces the protocol, performance specifications and functions of the UMC 2
TL1 northbound interface.

Interface Protocol

TL1

Performance Specifications

Table 2-12 Performance Specifications of the TL1 Northbound Interface

Interface Item Specification

- Maximum number of concurrent TCP connections 32
Service Number of work orders User service provisioning / deletion ＞2
provisioning per minute supported by User service suspension / recovery /
＞4
interface a single connection modification

Version: A/02 15
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 2-12 Performance Specifications of the TL1 Northbound Interface (Continued)

Interface Item Specification

Delay in response to an internal line test, external line test,
Integrated testing < 1 minute
SELT, DELT or incoming / outgoing call emulation test
interface
Delay in response to a query command < 5 seconds
Normal < 10 seconds
Alarm delay
Alarm storm < 30 seconds
Integrated alarm
Delay in synchronizing 1000 alarm entries ≤ 10 minutes
interface
＞ 20 entries /
Alarm throughput
second
Delay in querying batch Data returned ≤ 500 entries < 5 seconds
Integrated query data Data returned ＞ 500 entries < 10 seconds
interface 10 000 ports
Full configuration export efficiency
per minute

Functions

Table 2-13 Functions of the TL1 Interface

Category Function
Service provisioning Provisioning IPTV, broadband and VoIP services in FTTx scenarios

Integrated test Querying states of devices or ports such as PON, XDSL and POTS

Integrated alarm Alarm subscription, filtering, acknowledgment, clearing and so on

Querying device and service resources, reporting resource changes, exporting

Integrated query
all resource data, and so on

2.2.6 REST Open API

This section introduces the protocol, data format, performance specifications and functions
of the UMC2 REST Open API.

Interface Protocol

Restful

16 Version: A/02
 2 Architecture

Performance Specifications

Table 2-14 Performance Specifications of the REST Open API

Item Description Specification

Request packet
Length of the HTTP request packet ≤ 2 MBytes
length
Request response
HTTP request response time ≤ 5 minutes
time
Number of
Number of HTTP concurrent requests ≥ 100
concurrent requests

Function

Table 2-15 Functions of the REST Open API

Function Description
Resource
Queries resource data, and subscribes to / reports resource change events.
management

Performance
Queries instantaneous data of resource performance indicators.
management

Alarm management Queries real-time alarm data, and subscribes to / reports alarm correlations.

2.2.7 WebService Interface

This section introduces the protocols and functions of the UMC2 WebService interface.

Interface Protocol

XML, XSD (XMLSchema)

Functions

Table 2-16 Functions of the WebService Interface

Category Function
Session control Supports password authentication and HTTPS protocol.

Service provisioning
Adds / configures / deletes ONUs, configures VLANs, etc.
interface
Test interface Queries configuration data of ONUs.

Version: A/02 17
UMC² Unified Management Control Centre V1R5 Product Description (PON)

2.3 Southbound Interfaces

The UMC2 connects to network devices at the physical layer via southbound interfaces for
management and control.

u Telemetry: remote collection of data from physical or virtual devices for monitoring
and analysis. It offers real-time high-speed data collection in push mode, providing a
data basis for locating network failures and optimizing network quality.

u Netconf+Yang:

4 Network Configuration Protocol (Netconf) is an XML-based network

management protocol. It provides programmable mechanisms to manage and
configure network devices.

4 Through a Netconf interface, the UMC2 delivers configurations, reads device

states, issues control commands and reports events.

4 Yang is a data modeling language used to model configuration and state data
manipulated by Netconf.

u SNMP: network management protocol that allows collecting network management

information from devices. Its functions include

4 Viewing or modifying parameters of devices

4 Identifying device failures, diagnosing faults, planning capacities, and generating

reports

4 Managing devices automatically by blocking their physical differences

4 Enhancing security with authentication and encryption

18 Version: A/02
3 Running Environment

This chapter introduces the recommended running environment for the UMC2 server and
client.

3.1 Hardware Environment

This section introduces the hardware configuration principles and suggestions for the UMC 2
server and client.

Configuration Principles

Follow the principles below when planning hardware configurations for the UMC 2 server
and client.

u Consider the current network type, network size, future expansion requirements and
hardware upgrade costs to choose the best configuration scheme.

4 Network size is defined based on the number of equivalent NEs. For details about
how to calculate equivalent NEs, see Equivalent Coefficient.

4 The hardware configurations of a large-sized network apply to a small-sized

network, whereas the hardware configurations of a small network do not apply to
a large network.

u Use an independent UPS for the UMC² server to avoid hardware damages due to
power failures.

u Use identical hardware configurations for active and standby servers in the cluster hot-
standby disaster recovery scheme.

Recommended Configurations for Virtual Servers in a PON

Manage- Configuration
ment VM Type vCPU Memory Common Disk Array Disk Array VM Count
Capacity Count (G) Storage (G) Storage (G) IOPS
300 000 UMC²
16 64 500 1000 3000 2
equivalent database
NEs Basic function 16 64 500 200 - 3

Version: A/02 19
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Manage- Configuration
ment VM Type vCPU Memory Common Disk Array Disk Array VM Count
Capacity Count (G) Storage (G) Storage (G) IOPS
Northbound
16 64 500 200 - 4
interface
NE
16 64 500 200 - 6
management
PAS app 16 64 500 0 - 8
PAS database 16 64 500 25000 3000 8
Web & PON
value-added 16 64 500 4000 - 16
app

Web value-
added 16 64 500 6600 3000 5
database
Total - 832 3328 26000 268600 - 52
UMC²
16 64 600 1000 3000 1
database
Basic function 16 64 600 200 - 2
Northbound
16 64 600 200 - 2
interface
NE
16 64 600 200 - 3
150 000 management

equivalent PAS app 16 64 600 0 - 3

NEs PAS database 16 64 600 25000 6000 5
Web & PON
value-added 16 64 600 3000 - 10
app

Web value-
added 16 64 600 5500 3000 3
database
Total - 464 1856 17400 173900 - 29
UMC²
16 3000 1
database 64 1100 1000
Basic function - -
50 000
Northbound
equivalent 16 64 600 200 - 1
interface
NEs
NE
16 64 600 200 - 1
management
PAS app 16 64 1100 25000 - 2

20 Version: A/02
 3 Running Environment

Manage- Configuration
ment VM Type vCPU Memory Common Disk Array Disk Array VM Count
Capacity Count (G) Storage (G) Storage (G) IOPS
PAS database 6000 -
Web & PON
value-added 16 64 600 2000 - 4
app

Web value-
added 16 64 600 5500 3000 1
database
Total - 160 640 7500 64900 - 10
UMC²
3000 1
database
Basic function 16 64 1100 1000 - -
Northbound
- -
interface
NE
16 64 600 200 - 1
20 000 management

equivalent PAS app - 1

16 64 1100 20000
NEs PAS database 6000 -
Web & PON
value-added 16 64 600 1000 - 3
app

Web value-
added 16 32 600 2200 3000 1
database
Total - 112 416 5200 26400 - 7

Recommended Hardware Configurations for a PC Client

Item Specification

CPU 3 GHz, 4-core

Memory 16 GB
Hard disk space 100 GB
Resolution 1920 × 1080

Version: A/02 21
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Recommended Hardware Configurations for a Web Client

Item Specification

CPU 2.6 GHz, 2-core

Memory 8 GB
Hard disk space 8 GB
Resolution 1920 × 1080

3.2 Software Environment

This section introduces the recommended software, bandwidth and IP configurations for the
UMC2 server and client.

Recommended Software Configurations for a Server

Table 3-1 Configurations Applicable to Access Products

Item Version Remark

Windows Server 2012/2019 Standard (64-
Windows OS -
bit)

Operating SUSE Linux Enterprise Server 12 SP5+

system SUSE Linux Enterprise Server 15 SP4
Linux OS -
Kylin Linux Advanced Server release V10
(x86_64)

Suitable for Windows, Kylin Linux

UMC² MySQL 5.7 or later
and SUSE Linux OSs
Suitable for Windows, Kylin Linux
PAS MySQL 5.7 or later
and SUSE Linux OSs
Database
For installing the Web & value-added
database
Web & value-added MongoDB 3.6.16 or 3.6.17
MongoDB 3.6.16 to be installed for a
Kylin Linux OS

VMware ESXi 6.7 update2

Virtual platform software For creating a virtual environment
FitOS 6.0
Installed separately on a UMC2 web
JDK JDK 1.8 201 server
Installed separately on a Linux OS

22 Version: A/02
 3 Running Environment

Recommended Software Configurations for a Client

Table 3-2 Configurations Applicable to Access Products

Item Version Remark

u Recommended: Windows 10
Operating system u Compatible with Windows 7/8/11 -
Professional
u Chrome 80.0.3987.132 (64-bit) For accessing the UMC2 web system
Browser u FireFox 86.0 (64-bit) and the microservice cloud platform
u Microsoft Edge 85.0.564.63 monitoring center

Recommended Bandwidth Configurations

Table 3-3 Bandwidth Calculation

Management Capacity
CIR (Mbit/s) MBR (Mbit/s)
(Equivalent NEs)
20000 12 108
50000 27 254
150000 76 743
300000 149 1475

Table 3-4 Bandwidth Requirements

Item Bandwidth Description

Heartbeat link 2 Mbit/s For transmitting heartbeat detection signals

VVR data synchronization link 200 Mbit/s For synchronizing the UMC² database

Transmission channel between

1 Gbit/s For connecting virtual machines in a LAN
virtual machines in a LAN
CIR (N refers to the number of equivalent NEs):
u N > 56: 2048k + (N-56) × 0.5k
Link connecting a device to the u N ≤ 56: 2 Mbit/s
100 Mbit/s to 1 Gbit/s
UMC² MBR (N refers to the number of equivalent NEs):
u N > 56: 10240k + (N-56) × 5k
u N ≤ 56: 10 Mbit/s
Device control plane
1 Gbit/s to 10 Gbit/s PCEP and BGP-LS channels
bandwidth
Link between the server and N (number of clients) × 20 Mbit/s; Min. 100 Mbit/s
≥ 100 Mbit/s
client recommended if N < 5
50 Mbit/s × actual number of alarms per second/1000 +
Link between the server and
≥ 10 Mbit/s number of equivalent NEs (10 thousand) × 7 Mbit/s × 10/
the upper-layer OSS
actual required time + 2 Mbit/s

Version: A/02 23
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Recommended IP Address Configurations

Follow the principles below when planning IP resources for the UMC2.

u Required IP resources include heartbeat IP address, VVR data replication IP address,

OSS access IP address, client access IP address, device communication IP address, and
communication IP address between UMC² servers.

u OSS and client access IP addresses belong to the same network and can be identical.

u Except for heartbeat and VVR data replication IP addresses, all others are
recommended to be configured as floating IP addresses. This can ensure normal
operation of the UMC2 after an active-standby switchover.

u The heartbeat, VVR data replication and floating IP addresses are required only when
a hot backup scheme is planned.

24 Version: A/02
4 Deployment Schemes

The UMC2 provides a unified networkwide management solution for access networks. It
can be applied to various management scenarios through multiple deployment schemes.

4.1 Server Deployment Schemes

The UMC2 server can be deployed in a centralized or distributed way. Centralized

deployment is suitable for small-sized networks, and distributed deployment for medium-
and large-sized networks.

4.1.1 Centralized Deployment

Centralized deployment requires only one server that runs all UMC2 processes and allows
access and operations from multiple clients.

Such server can be a physical or virtual machine, either of which is configured identically in
hardware and software. The following introduces centralized deployment on a virtual
machine as an example.

Network Scheme

The centralized deployment scheme is simple and cost-effective. However, it is less reliable
and risk resistant, and hence only applicable to small-sized networks, as shown in
Figure 4-1.

Note:

vCenter is a client installed with VMware management software, which is used

for managing virtual machines on a private cloud platform.

Version: A/02 25
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Figure 4-1 Network Scheme of Centralized Deployment

4.1.2 Distributed Deployment

In distributed deployment, basic core services, database services, PAS app services, value-
added services and other components are deployed on different servers. Such deployment
makes the UMC2 more scalable, available and reliable, as shown in Figure 4-2.

26 Version: A/02
 4 Deployment Schemes

Figure 4-2 Logical Relationships Among Components in Distributed Deployment

Network Scheme

Distributed deployment is applicable to medium- and large-sized networks. When a

network contains more than 20 000 equivalent NEs, it is recommended to deploy the UMC 2
on virtual machines as shown in Figure 4-3.

Note:

The figure below gives an example of networking. Contact FiberHome technical

support engineers for actual applicable solutions.

Version: A/02 27
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Figure 4-3 Network Scheme of Distributed Deployment

4.2 Client Deployment Schemes

UMC2 clients can be deployed in both browser/server (B/S) and client/server (C/S)
architectures, as shown in the figure below.

u In C/S mode, a user visits http://server IP:8080/webstart/ via a browser and

downloads client software from the UMC2 server to install and deploy a client.

u In B/S mode, a user accesses the UMC2 via a browser, without installing any client
software.

28 Version: A/02
 4 Deployment Schemes

Figure 4-4 Client Deployment Network

Version: A/02 29
5 Functions

The UMC2 offers a full range of management, control and intelligent analysis / optimization
for cloud-based networks.

5.1 Overview

The UMC2 can be accessed via a client or a browser, providing the following functions.

u Security management: Provides complete security policies for managing system

security and user security / authority / login / data to keep the UMC 2 system secure.

u Topology management: Provides multiple views to show topologies of managed NEs

and their connections, helping users learn networking and monitor networkwide
operation in real time.

u Alarm management: Provides a centralized access to alarms about NEs and system
services, enabling fast location and handling of existing failures in a network and
hence keeping services running as expected.

u Performance management: Collects, analyzes and processes networkwide performance

data, giving an understanding of current network operation and performance. This
allows measures taken in time to prevent network failures and carrier networks
planned wisely.

u Log management: Generates logs about user login / operation and system operation to
further secure the system.

u Resource management: Configures, queries and measures physical and logical

resources, and exports query / measurement results in various formats.

u Report management: Allows customizing reports on performance / alarms / services /

resources and exports reports as required in various scenarios.

u Configuration management: Offers common configurations for NEs (including

subracks, cards and ports), maintenance states of networkwide devices, communication
parameters, software repository, software upgrade tasks, etc.

u System monitoring and maintenance: Provides web-based NMS management tools to

monitor and maintain the UMC² system, including managing its service processes,
monitoring its server resources and importing / exporting configurations.

30 Version: A/02
 5 Functions

u Access network management: Enables unified management of NEs and services in

networkwide access domains, including NE / service configuration and service query /
diagnosis / cutover / adjustment, to cater for network convergence.

u Network traffic analysis: Monitors and analyzes networkwide traffic, including

displaying networkwide traffic in topology, monitoring traffic in seconds / minutes,
measuring service traffic in an area, generating basic traffic reports, and offering
optimization suggestions for adjusting and planning networks.

u Network resource analysis: Analyzes networkwide resource usages and predicts

development trends to identify resource bottlenecks and plan future expansion
accordingly; inspects an entire network regularly from the aspects of NE and network
states / configurations to prevent device and network failures.

u Network quality analysis: Enables end-to-end performance monitoring on optical

power, service delay, signaling delay, packet loss rate, jitter and TCP throughput,
showing real-time changes in service quality.

u Intelligent report: Collects, queries and exports custom reports on networkwide

physical resources and network states, and provides their statistics charts.

5.2 Network Management

The UMC2 provides complete NE-level and network-level management for security,
topology, configuration, resources, alarms, performance, logs, inventory, reports, and
system monitoring / maintenance. It manages FiberHome devices in access, transport and IP
domains in a unified way to cater for network convergence.

5.2.1 Security Management

With complete security management over the system, users, user authority and security
policies, the UMC2 denies illegal access and unauthorized operations, keeping itself and
network devices secure.

Version: A/02 31
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Figure 5-1 Security Management Mechanism

System Security Management

The UMC2 improves defense capabilities through security hardening, virus prevention,
security scanning and data security protocols.

u Security hardening: OS patches are updated and default OS parameters are modified to
keep system data secure and complete.

u Virus prevention: The UMC2 software is strictly tested to ensure that its releases are
safe and virus-free.

u IPS/IDS: The system is verified to be safe by security tools such as NSFOCUS WVSS
and Nmap.

u Web security: Web service resources are accessed through secure HTTPS connections
with the following security measures.

4 The SSL certificate v3 is used, and its key length is 2048 bits.

4 Weak encryption algorithms such as MD5 and 3DES are not used.

4 Version information displayed on error pages is masked to avoid version-specific

vulnerabilities.

u Secure data transmission: Secure transmission protocols such as TLS 1.2 or later,
SNMP v3 and SFTP are enabled to keep data secure over a network.

u Secure data storage: Important data is dumped to a local server or an FTP server.

The UMC2 keeps the system secure through user security policies for accounts, passwords,
access control and login modes.

32 Version: A/02
 5 Functions

u Account policies: Minimize security risks of a UMC2 account by specifying

4 Minimum length of a username

4 Automatic unlocking time

4 Delay for login or unlocking failures

4 Maximum number of illegal login attempts that triggers account locking

4 Policy for inactive accounts

4 Policy for forcing idle clients offline

u Password policies: Improve password complexity to keep accounts safe by setting

4 General policies: minimum / maximum password length of ordinary / super users,

time interval between two identical passwords, minimum / maximum number of
days in which a password is effective, number of days before expiry when the
system starts displaying password expiry prompts, limits on how a new password
cannot be similar to old ones, etc.

4 Advanced policies: minimum number of characters in a new password that are

different from those in the old one, minimum number of letters / uppercases /
lowercases / numerals / special characters in a password, number of successive
characters in a username that cannot be included by a password, limits on how a
password cannot contain repeated character sequences or spaces, etc.

4 Other policies:

¡ Passwords are not displayed in plain text.

¡ Contents in the password text box cannot be copied.

¡ Users can modify their passwords after verifying the old ones.

¡ Passwords are sent as encrypted over a network.

¡ Passwords are encrypted for local storage.

u User login mode: When maintaining the system, set the system to single-user mode to
prevent interference from other users.

4 Single-user mode: Only one admin user can log in through one client. All other
online users are logged out.

4 Multi-user mode: Multiple users can log in simultaneously.

u Access control policies: Only users with matching MAC or IP addresses can log in,
keeping the system secure.

Version: A/02 33
UMC² Unified Management Control Centre V1R5 Product Description (PON)

4 System access control list: An allowable IP / MAC address range is set and
applied to all users.

4 User access control list: An access control list is set and applied to a specified
user only.

u Login time range control: Users are restricted to log in only within a specified time
period, making the system more secure.

u User authentication: After an authentication server is set, users are authenticated via
LDAP, RADIUS or TACACS+ before logging in, keeping user accounts safe.

u Integrity check: The UMC² provides file integrity check for system installation
packages, dump files and backup files to prevent them from being damaged or
counterfeited.

User Security Management

By authorizing users, the UMC2 grants users appropriate authority for their operations and
duties, ensuring secure operations on the UMC2.

u User: A username and its unique password determine the login, operation and
management authority of a UMC2 user.

4 The user admin is a default system administrator that can operate and manage all
objects. It cannot be deleted or modified.

4 To create a new user, set its basic information, authority, management domain,
access control and other parameters.

u User group: a collection of users with identical authority. Add users requiring the same
authority to a user group. By assigning certain management domains and authority to
the user group, all members are granted the authority of the group. In this way, users
are authorized in batches.

The following default user groups are available on the UMC2.

4 Administrators Group: Has all authority except security management.

4 Security Administrator Group: Has the authority related to security management

over networkwide objects, including adding a user, logging out a user, modifying
a user's management domain, and second authorization. It cannot be modified.

4 Inspector Group: Has the Assembly of Application Inspectors authority over

Assembly of Objects. Users in this group can only query and collect data, and
cannot create objects or configure parameters.

34 Version: A/02
 5 Functions

4 Operator Group: Has the Assembly of Application Operators authority over

Assembly of Objects. Users in this group have not only all the authority of
Inspector Group, but also the authority for non-risk or low-risk operations in
configuration, creation, and deletion, such as setting port attributes, creating NEs,
and modifying alarm levels.

4 Maintainer Group: Has the Assembly of Application Maintainers authority

over Assembly of Objects. Users in this group have not only all the authority of
Inspector Group and Operator Group, but also the authority for risky
operations in configuration, deletion and download, such as setting scheduled
tasks, activating or deleting services, and resetting cards.

User Authority Management

The UMC2 provides effective control over users' access and operation authority. Each legal
user can use authorized functional modules and commands only. Hence the UMC 2 and
network devices can run safely.

As illustrated in Figure 5-2, a user's authority consists of the management domain and
operation authority directly assigned to him / her plus those assigned to his / her user group.

Figure 5-2 User Authority Management

u Management domain: a collection of objects managed by a user or user group. NEs or

other objects beyond the domain are not displayed.

4 With management domains assigned, engineers in different OAM departments

manage network objects in their respective domains. NEs are the minimal objects
that can be added to / removed from a management domain.

Version: A/02 35
UMC² Unified Management Control Centre V1R5 Product Description (PON)

4 An object set can be created to include individual NEs, all NEs of a type, a global
logical domain or another object set. When being bound to an object set, a user or
user group can manage all objects in it.

u Operation authority: a collection of specific operations available to a user or user

group.

4 With operation authority assigned, OAM engineers at varying levels can have
different operation authority in a domain.

4 An operation set can be created to include required specific operations or another

operation set. When being bound to an operation set, a user or user group can
quickly have all operation authority in it.

4 Menu functions are the minimal operation authority that can be allocated.
Ordinary users can only perform low-risk operations, minimizing security risks.

4 Custom operation sets in the current system can be easily migrated to another
system.

u Two levels of security administrator groups are available in the system, i.e., security
administrator groups and sub-domain security administrator groups. A sub-domain
security administrator group is created and assigned a management domain by a
security administrator. It only has the application authority for security management.

u Security administrators can compare the authority of two users as needed to check their
authority differences.

u Security administrators perform second authorization for risky operations. They further
evaluate whether such operations are necessary and harmful. In this way,
misoperations can be avoided to the utmost extent.

u Security management authority is managed by level. A non-administrator user with

security management authority cannot authorize other users beyond his / her own
authority. This avoids unauthorized access.

u Access to logs are managed based on authority and domain. Users can view logs only
within their authority and domain range. This ensures information security.

Session Management

u A security administrator can manage user sessions and related operations on the UMC 2.
Once detecting any anomaly in a lower-level user, a security administrator can log him
/ her out forcibly to keep the system safe.

36 Version: A/02
 5 Functions

u A client can be locked.

4 Locking a client automatically: When this function is enabled, a client will be

locked automatically if no operation is done within a specified period.

4 Locking a client manually: If no operation is required on a client for the present, it

can be locked manually to prevent unauthorized access.

u A client can be unlocked.

4 If an admin account is locked on a client, he or she can enter his / her account
password to unlock it.

4 If a non-admin account is locked on a client, he or she can enter his / her account
password to unlock it, or log out and then log in again using another account. If
this user forgets his / her password, the admin user can reset his / her password to
unlock this account.

u The maximum number of sessions can be set for a user group in the range of 0 to 100.

u The maximum number of online users can be set in the range of 0 to 255.

License Management

The UMC2 license can be managed in a graphic user interface that provides

u A temporary license with a 30-day validity period

u Prompts at a 10-minute interval for renewing the license that will expire in 30 days or
less

u Machine ID for renewing the license

u License management, allowing query of license validity and control items and license
renewal

u Information such as name, description, value, consumption and consumption alarm

threshold of resource control items like NEs, cards, ports, cross-connect capacity and
online users

u Information such as name, description and availability of function control items like
intelligent OAM

u Reports on license usage, such as license state

Version: A/02 37
UMC² Unified Management Control Centre V1R5 Product Description (PON)

5.2.2 Topology Management

Topology management displays connection states of managed NEs in topology views.

Main Topology and Its Functions

The main topology view and its functions are as follows.

Figure 5-3 Main Topology View (Access Domain)

Table 5-1 Functions of the Main Topology

No. Name Function

Displays all managed logical domains and NEs in a tree structure. Users can quickly locate
(1) Browse tree
an NE by searching.

Allows quick access to the functions in the topology view. Users can
u Switch to another view, adjust view mode, lock / refresh a view, and save / export views
as images.
(2) Shortcut icon bar
u Create logical domains / NEs / links, set layouts, filter topology objects, and set
topology attributes.
u Zoom in / out the entire view, and zoom in part of a view.

38 Version: A/02
 5 Functions

Table 5-1 Functions of the Main Topology (Continued)

No. Name Function

u Displays information such as name / IP address / link status of all managed NEs, logical
(3) Main topology domains and links.
u Creates logical domains, NEs and links and hides nodes via shortcut menus.

Displays information of topology objects and customizes common operations like opening
(4) Information panel
NE managers, and querying current / history alarms and performance.

Displays overall layout of a network, allowing fast location of the area displayed in the main
(5) Thumbnail view
topology view.

Topology Icons and State Display

Different colors and small icons represent alarms and states of logical domains or NEs, as
shown in Figure 5-4 and Figure 5-5. Table 5-2 and Table 5-3 describe topology icons and
alarm colors.

Figure 5-4 Example of the Logical Domain Icon

Figure 5-5 Example of the NE Icon

Version: A/02 39
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 5-2 Topology Icons

Icon Description
Indicates unacknowledged alarms of a monitored object. The border color represents the highest level of
Icon border
all unacknowledged alarms on an object.

Small icon 1 Indicates the latest special alarm.

Small icon 2 Indicates the communication type of an NE.

Small icon 3 Indicates that this is a mirror NE.

Logical domain
Shows all NEs in a logical domain after this icon is double-clicked.
icon
NE icon Indicates an NE type.

Shows the color of the highest-level alarm in an NE or a logical domain. Table 5-3 describes the
Icon ground color
meaning of colors.

Table 5-3 Alarm Colors of Topology Icons

Alarm Level Color Description

Dark gray Communication interruption alarm

Red Critical alarm

Orange Major alarm

Yellow Minor alarm

Blue Warning alarm

Automatic Discovery of Physical Topologies

The UMC2 automatically discovers physical topology resources such as NEs, subracks,
cards and links, speeding up device deployment and capacity expansion.

ODN Topology View

The UMC2 manages ODN topology views, including maintaining or creating default and
custom ODN topology views, checking topology relationships among physical units of NEs
such as subracks / cards / ports, and querying alarm data and ONU RTT values.

5.2.3 Alarm Management

The UMC2 provides powerful alarm management for monitoring failures and anomalies in
device operation in real time. It allows users to analyze and handle alarms efficiently. The
figure below shows the flow of managing alarms.

40 Version: A/02
 5 Functions

Figure 5-6 Flow of Alarm Management

Alarm Data Consistency

The UMC2 ensures alarm data consistency with devices through automatic synchronization,
manual synchronization, automatic polling and proactive trap reporting. Hence, users can
learn actual running states of a network in time via the UMC2.

Synchronization
Description
Type

The UMC2 automatically synchronizes alarms with all devices after its services start up, and with a
Auto synchronization
device that recovers from a communication interruption.

Manual
The UMC2 allows synchronizing alarms with devices manually.
synchronization

Automatic polling The manager module of the UMC2 polls all managed devices automatically at regular intervals.

If a new alarm occurs on a device prior to the next poll, the device will actively report this alarm to the
Trap reporting
UMC2. Then the UMC2 will respond according to the information contained in the alarm.Note 1

Note 1: When a new alarm occurs, the UMC2 will automatically update its alarm panel and display the new alarm in its alarm
list. Hence, users can learn the alarm information of a network timely.

Alarm Reporting

The UMC2 can block or customize alarms and set alarm frequency analysis and merging
rules. Hence, users can set alarm reporting as desired.

Version: A/02 41
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Function Description
Numerous useless alarms may be generated during device installation / commissioning / testing / maintenance
/ cutover. By blocking these useless alarms, users can focus on important alarms. The UMC 2 provides
u Northbound interface alarm blocking. When some alarms need not be reported to third-party network
management systems through northbound interfaces, these alarms can be blocked by setting blocking
rules for northbound interfaces, allowing alarms to be handled more efficiently.
u Current alarm blocking. Unimportant alarms can be blocked in the current alarm list, allowing more
efficient troubleshooting. After alarm blocking rules are set, blocked alarms are neither displayed on the
GUI nor saved in the database.
u Alarm blocking for a specified object.
Alarm
blocking 4 Users can customize alarm blocking status of a designated object (NE, card or port).
4 Alarm codes are classified by interface, card and general types so that they can be filtered from
different dimensions.

u Alarm toggling rules. With alarm toggling rules, matching alarms can be blocked, allowing efficient
troubleshooting.
u Project-state alarm tasks. By adding an NE, card or port to a project-state alarm task, northbound
interfaces will not report its alarms to upper-layer network management systems.
u Alarm blocking data report. You can query alarm blocking details of a specified object and export them
as reports.

The UMC2 allows

u Modifying alarm levels to highlight focused alarms. Alarm levels can be modified in different scopes,
such as for all objects, for a device or for a device type.
Custom alarms u Re-defining alarm names according to OAM requirements.
u Customizing special alarms. When a special alarm occurs on an NE, its icon will be displayed at the
upper right corner of the NE icon.
u Customizing alarms for MON interfaces so that external alarm types can be easily identified.

Alarm Users can set alarm frequency analysis rules. These rules will be triggered when the number of designated
frequency alarms exceeds the preset threshold in a time period. Then the UMC 2 will process these alarms according to
analysis rules the preset policies.

Networkwide Alarm Monitoring

The UMC2 monitors alarms in the entire network and displays them in multiple ways,
keeping users informed of network running status in time.

42 Version: A/02
 5 Functions

Table 5-4 Functions of Networkwide Alarm Monitoring

Item Function
u Alarm report: Displays alarms of different levels in different colors in a table and provides related
information such as alarm name, source, location and frequency.
u Alarm sorting: Allows sorting alarms by desired indicator.
Alarm display u Alarm filtering: Gets rids of numerous alarms. Users can filter alarms by a combination of criteria
such as alarm name, object, level, status, type, last occurrence time and clear time to easily view
their focused alarms.
u Alarm location: Provides detailed location information of an alarm to identify its associated object.

u Queries the following alarm information of a specified object.

4 Current alarms. Users can view current alarms of a network, a card, or objects matching filter
criteria.

4 History alarms. Users can view history alarms of a network, a card, or objects matching filter
criteria.

Alarm browsing 4 Reported alarms. Users can view the alarms that meet reporting rules.
4 Alarm logs. Users can view alarm logs of a network or objects matching filter criteria.
4 Reported events. Users can view events of a network or objects matching filter criteria.
u Queries alarms of a specified object with an alarm template.
The system allows creating, viewing, searching for, modifying, deleting, adding to favorites and
sharing query / collection templates for current / history alarms or alarm logs and events.

The alarm panel on the homepage of the system displays the total number of current alarms at each
level in an entire network.
The UMC2 can display the total number of alarms matching a preset template in the alarm statistics
Alarm panel
window of the alarm panel. Such alarm data can be presented in a table, pie chart or bar chart, for
example, Top 10 Alarms, Alarm Duration, Top 10 Alarm Source, Alarm Level and Alarm Status
charts.
u Alarm blocking. Blocked alarms are neither saved into the UMC2 database nor displayed on the
screens. Hence, users can focus on alarms requiring attention.
u Alarm location. A selected alarm can be located on the alarmed topology object through this
shortcut menu option. Physical alarms can be narrowed down to a specific card panel.
u Alarm reversion. If an alarm is set to reverse mode, its status displayed is contrary to that actually
reported. In this way, unimportant alarms can be blocked for the moment.
Shortcut menus for
u Remote notification of alarms. The UMC2 informs off-site engineers of a network failure by email
handling alarms
or SMS.
u Alarm data exporting. Alarm data can be exported, saved and printed in HTML, CSV, EXCEL,
TXT or XML format. Hence, users can learn historical operation conditions of a network. For easy
data collection, the UMC² allows exporting current alarms across a network and history alarms by
day.
u Alarm acknowledgment. An acknowledged alarm means it has been handled by an administrator.

Version: A/02 43
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 5-4 Functions of Networkwide Alarm Monitoring (Continued)

Item Function
Common alarm
Querying alarms by template, setting query criteria, acknowledging alarms, clearing alarms, etc.
handling buttons

u Alarm handling suggestions cover alarm causes, handling suggestions, maintenance experiences
Alarm maintenance
and so on.
information
u Alarm details show detailed information such as name and location of an alarm.

Alarm Analysis and Handling

By analyzing and handling alarms through the UMC2, OAM engineers can quickly locate
and remove network failures to keep networks running as expected.

Function Sub-function Description

Locates an alarmed NE in a topology view or an alarmed card / port in an NE manager based
Locating alarms on current / history alarms or alarm logs, and identifies the cause of a failure quickly, allowing
more efficient troubleshooting.

Sets an alarm to reverse mode as needed. Then its status displayed is opposite to that actually
Reversing alarm status reported by a device. That is, before the device alarm ends, it is not displayed on the UMC²
screens. In this way, useless alarms are blocked.

Distinguishes a root alarm from its derivative alarms through analysis based on user-defined
Alarm correlation analysis alarm correlation rules. This helps users find out a root alarm and identify the cause of a
failure, allowing more efficient troubleshooting.

Queries alarms of NEs at two ends of an optical fiber to locate alarms quickly, allowing
Fiber associated alarm settings
efficient OAM.
Sets key alarms and the time when a key alarm prompting rule takes effect. When a key alarm
Key alarm prompt rule settings
occurs, it is reported to users in a striking way.

Alarm threshold settings Configures and manages alarm thresholds, allowing efficient and easy OAM.

Collects alarm information according user-defined statistics criteria. Such criteria include
Alarm statistics
time, alarm type / level / classification / status, NE, or a combination of the above.

Queries alarm logs based on set query criteria or a specified query template. Such logs include
Querying alarm
basic information (alarm level, name, status, location and so on), alarm start / end time, and
logs
handling measures / result.
Alarm logs
Collecting
Collects current alarm logs based on set statistics criteria or a specified statistics template, and
current alarm
displays the result in diverse ways, such as table, chart and curve comparison chart.
logs

Alarm / Customizes alarm reporting rules (including basic information, filter criteria, alarm source,
Setting alarm
event advanced information, rule triggering event and prompt tone settings), and reports alarms
reporting
reporting accordingly.

44 Version: A/02
 5 Functions

Function Sub-function Description

Querying
reported alarms Queries detailed information about reported alarms / events and processes reported data.
/ events
Converting
alarms to Converts an alarm to an event as necessary.
events
Converting
events to Converts an event to an alarm as necessary.
alarms
Checks history alarm / event data in the database periodically, and dumps it automatically to a
Overflow specified file or deletes it directly when it reaches the preset overflow threshold and database
dump capacity limits.
Alarm /
Users can query overflow dump records, and view or download specified dump data.
event dump
Runs a manual dump taskNote 1 to dump history alarm / event dataNote 2 to a specified file or
Manual dump delete it directly.
Users can query manual dump records, and view or download specified dump data.

Note 1: A dump task can be modified but cannot be deleted or created.

Note 2: Dumped data is saved in CSV format by default.

Alarm Levels

UMC2 alarms come in four levels: critical, major, minor and warning. Alarms at different
levels require different handling methods as shown below.

Alarm LevelNote 1 Color Meaning Coping Policy

Alarms and events that cause service

Immediate troubleshooting is required.
interruption or NE failure, for example,
Critical Red Otherwise, a network may break
managed NE communication interruption or
down.
LOS.
Alarms and events that influence devices or
Timely troubleshooting is required to
Major Orange services, for example, fan alarms or unsaved
avoid a device failure.
configurations.

Alarms and events that do not affect devices or

Troubleshooting is needed to eliminate
Minor Yellow services, for example, laser temperature alarms
potential risks in advance.
or threshold-crossing alarms.

Alarms and events that do not affect existing

Troubleshooting may be needed as
Warning Blue services but may influence services later, for
appropriate.
example, ambient temperature warning.

Note 1: Different prompt tones can be set for different alarm levels. When an alarm appears, a client computer will produce a
corresponding prompt tone.

Version: A/02 45
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Alarm States

Table 5-5describes alarm states and Figure 5-7 shows how alarm states are converted.

Table 5-5 Alarm States

Category Alarm State Description

Indicates whether an alarm is handled by an administrator. An acknowledged alarm
has been handled while an unacknowledged one has not. Alarms can be
acknowledged manually or automatically.
Acknowledg- Acknowledged or u Manual acknowledgment: Alarms are acknowledged via the shortcut menu in
ment unacknowledged the alarm browsing window.
u Automatic acknowledgment: After this function is enabled, alarms are
acknowledged automatically according to automatic or delayed acknowledgment
rules.
Indicates whether an alarm is cleared. An alarm is cleared after its causes are
removed.
Cleared or
Clearing u Alarms can be cleared automatically from a device or the UMC², or manually by
uncleared
a user.
u Alarms can be cleared manually or automatically.

Figure 5-7 Conversion Between Alarm States

Alarm Classification

Alarms can be categorized as follows according to their states and functions.

Category Description

Current alarm Alarm saved in the current alarm database of the UMC². Note 1
State Alarm converted from cleared current alarms after a preset delay, and moved from the
History alarm
current alarm database to the history alarm database

Alarm related to NE communication and port connection, such as opposite

Function Communication alarm
communication interruption, fiber cut and incorrect fiber connections.

46 Version: A/02
 5 Functions

Category Description

Alarm related to service quality, such as bad network service and performance
QoS alarm
threshold crossing.

Alarm related to hardware or optical port failures, such as power failure and loss of
Device alarm
optical port.

Alarm related to running environments of devices, such as over-high ambient

Environment alarm
temperature and over-low humidity.

Alarm related to the UMC² and device security, such as system out of service and
Security alarm
mismatch of alarmed card types.

Alarm related to system processing or system anomaly, such as upgrade failure and
Processing failure alarm
management card communication interruption.

Note 1: Identical alarms repeatedly generated by an object is displayed as one entry in the current alarm list. To view each
alarm record, check alarm logs.

5.2.4 Performance Management

The UMC2 gets performance data from devices, and allows browsing, analyzing and
managing such data. This helps users understand the current operating status and basic
performance of a network, take measures accordingly to prevent network failures, and plan
carrier networks wisely.

Performance Collection

The UMC2 provides the following performance collection functions.

u Performance collection task management

4 Collection task: created based on NE types to collect performance data regularly.

Such data can be collected over 15 minutes or 24 hours.

4 Indicator set: a set of performance indicators, which can be selected as

performance codes to be measured to speed up creation of a collection task.

4 Threshold set: a set of performance thresholds, which can be selected as the

performance threshold range of a new collection task.

u Management on performance indicator set templates for PON devices

4 Creates PON device performance indicator set templates and binds them to OLT
NEs.

Version: A/02 47
UMC² Unified Management Control Centre V1R5 Product Description (PON)

4 Sets the performance indicator set templates bound to different object types on an
OLT. Only performance indicator sets in these templates are reported.

u Second-level traffic performance management: Measures and analyzes NEs' traffic

performance in seconds.

Performance Query and Analysis

The UMC2 provides the following performance query and analysis functions.

u History performance query: Queries history performance of a specified object like an

NE, card, port or service, and displays the values or changes of performance
parameters in a table or chart.

u History performance trend analysis:

4 Displays history performance trends in a table, curve chart or bar chart, allowing
analysis of performance changes in multiple dimensions.

4 Exports and prints history performance trend data, allowing easy integration and
analysis of performance data.

u Performance comparison: Compares specified performance indicators of desired

objects (cards or ports) in two or more designated performance collection areas. This
gives a clear understanding of performance changes and helps plan networks wisely.

u History threshold-crossing performance query: Queries history performance threshold-

crossing records of a specified card or port, providing data support for network
planning.

u Performance query template management: Provides current / history performance

query templates and threshold-crossing performance query templates. Performance
query criteria can be saved as a query template for future reuse and fast query.

u Performance report exporting: Exports performance tables in TXT, Excel, CSV, XML,
PDF or HTML format.

Performance Dump

The UMC2 provides the following performance dump functions.

u Performance data dumped to a specified path and deleted from the database. This frees
up database space, keeping the UMC² stable and efficient.

48 Version: A/02
 5 Functions

u Overflow dumping and manual dumping allowed. Dumped data is saved to a file or
deleted directly.

u Dumped performance data accessible or downloadable via the UMC2 client

5.2.5 Log Management

Log management includes querying / collecting / forwarding / dumping logs. Network

administrators can view logs to learn the operation status and records of the UMC 2. This
provides an important basis for fault location and troubleshooting.

Log Type

The types of managed logs are as follows:

u System log: Records information of system related operations on clients, including

danger levels, sources, time, operation terminals and results.

u Operation log: Records detailed information of all operations on clients, including

operation names, danger levels, usernames, login modes, user types and operation time
/ terminals / objects / results.

u Security log: Records detailed information of security related operations on clients,

including security time, danger levels, usernames, login modes, user types, operation
time / terminals / objects.

u Alarm log: Records all alarms received by the UMC². Each alarm is displayed as one
entry.

u Northbound interface command log (access domain): Records operation information of

northbound interface commands, including TL1 / Web Service / Socket / REST Open
API command logs, and alarm journals.

Log Management

The UMC2 allows querying / collecting / forwarding / dumping logs, as described in

Table 5-6.

Version: A/02 49
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 5-6 Functions of Log Management

Function Description
Logs are queried to get data about operations and status of the system.
Querying logs u High query efficiency with log query templates and previews
u Query results exported as reports in format of HTML, EXCEL, CSV, XML, TXT or PDF

Logs are collected based on existing data in the database. If the database is empty, no data can be
obtained.
Collecting logs u Configurable row and column headings in collection result tables to collect all types of logs
u High collection efficiency with log collection templates
u Collection results exported as reports in format of HTML, EXCEL, CSV, XML, TXT or PDF

Multiple log forwarding servers can be created. Different types of logs can be forwarded to specified
Forwarding logs
Syslog servers, freeing up storage space of the UMC2 server.

Logs can be dumped through

u Overflow dump: The UMC2 periodically checks logs in the database. When reaching the preset
Dumping logs overflow threshold, logs will be dumped automatically to a specified file or deleted directly.
u Manual dump: A dump task can be run manually to dump logs to a specified file or delete them
directly.

5.2.6 Resource Management

Resource management refers to managing physical and logical resources across a network.
The UMC2 provides a unified management GUI where networkwide resources can be
configured, collected and queried in batches.

Detecting Physical Resource Configurations

The UMC2 can detect incremental or full physical configurations of connected NEs, and
synchronize configurations with all NEs or a single NE to keep data consistency.

Configuring Physical Resources in Batches

Physical resources such as NEs and optical fibers can be configured in batches, allowing
more efficient OAM.

u Modifying names of logical domains, NEs and card ports in batches

u Querying ODU information of an OLT, including optical splitter information and the
association between ONUs and optical splitters. Longitude and latitude data and types
of optical splitters can be imported in batches.

50 Version: A/02
 5 Functions

u Configuring ODN information in batches through templates

u Importing NE configurations through EXCEL or CSV files to add NEs to the main
topology in batches

u Deleting NEs and connected access devices in batches

u Querying ONUs in batches by importing an ONU identifier template

u Deauthorizing abnormal ONUs in batches

u Importing NE coordinates (GIS data) through EXCEL files to modify the longitudes
and latitudes of NEs in batches

u Querying all unauthorized ONUs connected to OLTs across a network in batches

Querying and Collecting Resource Data

On the UMC2, users can query and measure usages of physical and logical resources in real
time or at preset time and export the result as a report.

Function Description
Queries real-time information such as quantity, usage, and anomalies of resources like NEs,
Querying resources
cards, ports, subracks, slots, wavelengths, IP addresses, services, alarms and performance.

Collects and filters physical or logical resource data based on the selected object and statistics
Collecting resource data
template within a designated statistics range.

Exports physical or logical resource data manually or at a preset time. Users can choose the
Exporting resource data
export method and content as desired.

Managing Other Resources

u Configuration verification: verifying OLT / ONU configurations, including LACP

configurations, OSPF startup status, OSPF neighbor status, and ONU POTS port status

u NE maintenance data management: querying and editing information about NE

locations and maintenance engineers. With such information, network administrators
can quickly contact maintenance engineers for troubleshooting.

u Card software version checking:

4 Querying software versions of all cards on an NE

4 Comparing the current version of a card and that in the software repository

u NE labeling: labeling important NEs so that they can be rapidly found later by
querying labels

Version: A/02 51
UMC² Unified Management Control Centre V1R5 Product Description (PON)

u Label query: locating an NE quickly in the topology view by keywords in its label

u Object group management: adding resource objects to an object group to facilitate

batch selection and operation

u Gateway type configuration: configuring gateway types, actual models and

manufacturer identifiers of ONUs from different manufacturers. Hence, their gateway
types can be identified when a resource management system (RMS) delivers network
access configurations of enterprise gateways.

u Custom attribute management: customizing attributes of NEs, PON ports and ONUs.
After custom attributes are added, users can view names and values of custom
attributes in the attributes window.

u PON private line OAM: managing ONUs connected to different OLTs in a unified way

5.2.7 Report Management

The UMC2 provides powerful report management. It can generate various types of reports
in real time or at preset time. Hence, users can easily measure the operation status and
quality of networkwide resources, and plan networks wisely.

The UMC2 manages reports as follows.

u Reports can be exported in two ways.

4 Manual export: Exports statistics / query results to reports manually.

4 Automatic export at a preset time: Exports statistics / query results to reports

automatically by creating scheduled tasks.

u Reports can be exported to files in multiple formats such as xls, xlsx, csv, html, pdf, txt,
and xml.

u Reports can be exported to a local path or FTP server.

u Report templates can be created to collect common data rapidly.

u Report data can be displayed in a graphical way (bar chart / line chart / pie chart).

Report Types

Table 5-7 lists available report types for PON solutions.

52 Version: A/02
 5 Functions

Table 5-7 PON Reports

Type Description Export Mode

Collects details of physical resources such as NEs, ports, cards, u Manual

Physical resource report
ONUs, and ONU / MSAN ports. u Automatic
Collects details of logical resources such as ONU users, local
u Manual
Logical resource report VLANs, PON device capacities, LLDP data, optical power, and
u Automatic
DBA service bandwidths.
u Collects information about OLTs, including hardware /
software / service / network / health states, and NE / network
configurations. u Manual
Inspection report
u Collects operating states and software versions of MDUs. u Automatic
u Collects the results of software and hardware checks on UMC²
servers.
Measures traffic and bandwidth usages of upstream links and ports
u Manual
Traffic report (OLT upstream ports, OLT PON ports, OLT VLAN ports, MSAN
u Automatic
upstream ports, MSAN service ports and ONU PON ports).

Measures optical powers of OLT upstream ports, OLT PON ports

u Manual
Optical power report and ONU PON ports, and gets information about objects with
u Automatic
abnormal optical power across a network.

5.2.8 Configuration Management

Configuration management includes managing basic information and common

configurations of networks and NEs. It is the core management function of the UMC 2.

Managing Basic NE Configurations

NEs’ basic parameters are configured in NE managers. Users can operate a single NE in an
NE manager and configure / manage / maintain an NE and its subracks, cards or ports
hierarchically.

An NE manager is organized in a tree structure that allows quick access to functions. Users
can select a desired object, and then a function node from the tree to open the corresponding
configuration GUI.

The figure below shows the GUI and functions of an NE manager.

Version: A/02 53
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Figure 5-8 NE Manager (Access NE)

Table 5-8 Components of an NE Manager

No. Function Description

(1) Device tree Displays the subracks and cards on an NE.

(2) Attributes page Displays the attributes of subracks and cards.

(3) Subrack view Displays card panels and alarm indicators on cards.

(4) List of ports Displays all the parameters of ports.

(5) Operation tree Displays the common functions available to an object selected in the device tree.

54 Version: A/02
 5 Functions

Table 5-9 Main Configurations in an NE Manager

Object Main Configurations

u Adding, deleting or moving a subrack

u Setting slot offsets
u Modifying attributes of a subrack
Subrack
u Viewing alarms or performance of an NE or subrack
u Adding or deleting all cards
u Querying the serial number of a subrack

u Adding, deleting, modifying or replacing a card

u Configuring all parameters of a card
Card u Viewing alarms and performance of a card
u Viewing status and description of a card
u Querying the serial number of a card

u Checking port status such as alarms and usage

Port
u Setting and displaying port remarks

Managing Common Configurations

The UMC2 manages common configurations as follows.

u Managing SNMP parameter templates of versions v1, v2c and v3, such as template
creation / modification / deletion / binding with NEs

u Managing NE communication routes:

4 Managing manager programs of NEs, such as manager program creation /

deletion / modification

4 Creating a partition policy for a manager program. When MAs are created, the
system will automatically add all NEs that meet the partition policy into the
specified manager program.

u Managing global templates

4 Binding global templates to access NEs of the same type in batches

4 Delivering global configurations to access NEs of the same type in batches

u Managing the hand-in-hand topology

4 Managing association of ONUs with double MAC addresses

4 Displaying the hand-in-hand topology and showing protections for associated

ONUs

Version: A/02 55
UMC² Unified Management Control Centre V1R5 Product Description (PON)

u Managing OLT slice resource templates in a unified way, such as template creation /
modification / deletion

u Virtualizing a physical OLT into multiple logical slices and allocating them to different
customers on demand. Logical slices share physical resources such as devices and
lines.

u Configuring and binding ONU capability set templates to enable fast adaptation of
new ONUs

u Managing network access status

4 Querying network access states of access NEs or selected line cards

4 Initiating a network access request for an access NE or a selected line card

4 Setting interconnection with an RMS for an access NE or a selected line card

u Tracing signaling frames on the line between an IAD and a voice communication card
to identify communication failures timely

u Moving logical domains in batches to a specified logical domain

5.2.9 System Monitoring and Maintenance

With Web-based network management tools, the UMC² provides system monitoring and
maintenance such as managing UMC² service processes, monitoring UMC² server resources
and importing / exporting configurations.

Managing Processes

On the process management page, all UMC² services' startup status and related processes
are displayed in a table. OAM engineers have access to the following functions.

Table 5-10 Process Management

Function Description
Starting / stopping / restarting a
Starts / stops / restarts a selected service.
service
Starting / stopping / restarting the
Starts /stops / restarts all UMC² services.
UMC²
Refreshing Refreshes all UMC² services.
Exporting dump / log files with one Manually generates the dump / log of the selected service and export it to the specified
click FTP server.

56 Version: A/02
 5 Functions

Managing Resources

On the resource management page, OAM engineers can monitor the running statuses of the
operation system, network management system and databases, and learn the system
resource usages timely. Table 5-11 describes the functions available.

Table 5-11 Functions of Resource Management

Monitored Object Monitored Item

Host, Host Name, Operating System, CPU Utilization, Total CPU, Memory Utilization, Total
Operation System
Memory (MB), Disk Utilization

Network Management
Server Name, Host, CPU Utilization, Memory Utilization (MB), Handle Number
System

ID, Database Name, Database Type, Database Application, Used Data Space (MB), Total Data
Database
Space (MB), Data Space Utilization

Querying History Data

In the History Data GUI, OAM engineers can query history data of Operation System,
Network Management System and Database. The query results are displayed in a curve
chart.

Setting Resource Monitoring Thresholds

Administrators can set alarm thresholds for the operating system, network management
system and databases, and retention periods for history and log data.

Importing / Exporting Configurations

On the Import/Export page, UMC2 system and app configurations can be restored or
backed up.

The functions available vary with users with different authority as follows.

User Function Available Description

Importing / exporting all Imports / exports UMC2 app configurations, including global
configurations parameters / user accounts / alarms / performance / services / logs.
Administrator Restores / backs up UMC2 system configurations, including
System restoration / backup programs, services and scripts that help guarantee normal operation of
the UMC².
Inspector Exporting all configurations Exports UMC2 app configurations to a default local path.

Version: A/02 57
UMC² Unified Management Control Centre V1R5 Product Description (PON)

User Function Available Description

System backup Exports UMC2 system configurations to a default local path.

5.2.10 Access Network Management

This section introduces NE and service management on an access network.

Basic Functions for Access NEs

The UMC2 can manage OLT, MDU, WPON and xDSL NEs.

Through an NE manager, the basic functions for a single NE are managed in a unified way.
Available functions include basic NE configurations, NE service configuration, local service
configuration, system software upgrade / backup, NE configuration import / export, and line
card / ONU upgrade.

Network Access Management

Users can query, configure and deliver network access status of access NEs on the UMC 2.
Specifically, they can

u Query / configure / deliver network access status of OLT NEs and line cards.

u Query / configure / deliver resource interconnection status of OLT NEs and line cards.

u Query ONU RMS failure information.

u Query network access interception logs of ONUs.

Authorization Management

Users can manage authorization status of line cards and ONUs. Specifically, they can

u Authorize and deauthorize card configuration.

u Configure an ONU whitelist.

u Manage authentication modes of ONUs and PON ports.

u Query authorized and unauthorized ONUs.

u Authorize and deauthorize ONUs.

58 Version: A/02
 5 Functions

Hand-in-Hand Topology Management

By managing hand-in-hand topologies, you can visually check status and alarm information
of PON ports, ONUs and trunk / branch fibers in a topology view in real time. With ONU
association on the UMC², an ONU with dual PON ports are identified as one object. This
allows easy OAM with more efficient inspection and troubleshooting.

Cutover Management

Cutover management on access network services means adjusting network services in

batches. It includes managing service cutover tasks and executing service cutover.

Eight scenarios supported: PON card 1:1 cutover, PON card N:1 cutover, PON card 1:N
cutover, PON port 1:1 cutover, PON port N:1 cutover, PON port 1:N cutover, PON port
partial cutover and VLAN cutover.

Intelligent Provisioning

Intelligent provisioning allows importing OLT configuration templates to the UMC 2 and
then delivering them to specified OLTs in batches. This allows provisioning services
remotely in batches.

Available functions include

u Importing / exporting / deleting / re-uploading configuration templates.

u Deploying OLTs of a specified type in batches remotely.

u Viewing current and historical service provisioning records.

ONU Pre-deployment

ONU pre-deployment means importing ONU configuration templates into the UMC 2 to
complete batch pre-deployment of ONUs. When these ONUs are connected, the OLT
automatically delivers pre-deployment configurations to them, making them plug-and-play.

Available functions include

u Configuring ONUs through templates, such as configuring ONU authorization /

deauthorization, OLT QinQ domains and VEIP data services.

u Executing / monitoring / querying pre-deployment tasks.

Version: A/02 59
UMC² Unified Management Control Centre V1R5 Product Description (PON)

OLT Pre-deployment

The UMC2 can import OLT pre-deployment configurations and complete batch pre-
deployment of offline OLTs. When these OLTs are connected, the UMC2 automatically
delivers pre-deployment configurations to them, making them plug-and-play.

Available functions include

u Importing pre-configuration templates or configuring OLT pre-deployment tasks.

u Viewing / importing / exporting / querying pre-deployment tasks.

Batch Configuration of VLANs for OLTs

The UMC2 can configure VLANs for one or more OLTs in batches.

Centralized Management of ONUs on PON Private Lines

The UMC² manages ONUs in a centralized way. It manages ONUs connected to different
OLTs by group, and collects the state or alarm data of ONUs or ONU groups.

u Batch import of ONUs: The UMC2 manages ONUs on PON private lines in a
centralized way. By configuring an ONU list template, you can import ONUs in
batches as per the set grouping criteria.

u Fast import of a single ONU: The UMC2 allows searching for a desired ONU in the
ONU query list and importing it as per the set grouping criteria.

u Fiber cut / power failure prompts: The UMC2 monitors fiber cut and power failure of
private line ONUs in real time, and displays pop-up prompts accordingly.

Batch Configuration of TL1 Commands

The UMC2 can configure TL1 commands in batches by importing a TL1 command
template.

u Template download: A custom import template can be downloaded to import the TL1
commands to be delivered.

u Template import: The imported template is verified based on TL1 command types, and
then the TL1 commands included in the template can be delivered to objects in
batches.

60 Version: A/02
 5 Functions

5.3 Network Analysis

The UMC2 provides powerful network analysis, that is, network traffic / quality / resource /
survivability analysis. Such analysis capability ensures stable and healthy network operation.

5.3.1 Network Traffic Analysis

The UMC2 visualizes traffic of networkwide resources through real-time data collection,
intelligent analysis and threshold-crossing warning. It enables users to quickly identify
trends of area traffic and hot services, and provides data support for network tuning.

Real-Time Traffic Topology

Through a traffic topology view, users can monitor operation status of network devices and
links in real time and control networking globally.

u A topology comprises a main topology and multiple sub-topologies. Users can drill
down to NE sub-topologies from the main topology.

u NE health status and link traffic data are displayed in the topology view.

u When the number of threshold-crossing alarms exceeds the limit, the system colors the
related NEs / links and shows the number of threshold-crossing alarms by bubbles.
This feature helps users easily monitor the quality of the entire network in real time.

Area Service Traffic Analysis

By analyzing the distribution and trend of area service traffic, the system helps operators
grasp the overall traffic of various services in a network.

In PON solutions, available features are

u Measuring the total traffic of a PON network in a specified area and displaying its
trend in a bar chart

u Measuring bandwidth usages of PON ports in a specified area and displaying port
percentages in a pie chart

u Measuring upstream link traffic in a specified area and displaying it in a table

u Measuring the percentage of threshold-crossing upstream links and displaying it in a

bar chart

Version: A/02 61
UMC² Unified Management Control Centre V1R5 Product Description (PON)

u Monitoring performance through second-level traffic reports and trend charts on OLT
upstream ports and PON ports

u Analyzing bandwidth usage anomalies of OLT upstream ports / PON ports, such as
threshold-crossing times and duration of upstream / downstream bandwidth usages for
OLT upstream ports / PON ports in a specified area

Threshold-Crossing Traffic Analysis (Adding / Removing Tokens)

By monitoring performance indicators (flow rate and bandwidth usage) of objects across a
network, the UMC² adds tokens to threshold-crossing objects, or removes tokens from
restored objects, reminding OAM engineers to handle objects with tokens in time.

Available features are as follows.

u In PON solutions, the system monitors networkwide objects like ports and services,
and reminds OAM engineers to focus on and handle faults in time by adding red,
orange and yellow tokens. This allows proactive network maintenance and speeds up
troubleshooting.

u The system reports the data of objects with red, orange or yellow tokens to a third
party through northbound interfaces. This function cuts the workload of OAM
engineers and improves OAM efficiency.

Basic Traffic Reports

In PON solutions, the UMC2 collects traffic data of ports or links, and exports this data to
reports in various formats.

u OLT upstream port basic traffic report

u OLT PON port basic traffic report

u ONU PON port basic traffic report

u Link basic traffic report

u MSAN upstream port basic traffic report

u MSAN service port basic traffic report

62 Version: A/02
 5 Functions

Automatic Traffic Reports

In PON solutions, the UMC2 can automatically generate reports by specified cycle (day /
week / month) and send notifications to specified email addresses. If an upload policy is set,
the UMC2 can automatically save reports locally or upload them to a specified server via
FTP / SFTP.

Network Type Report

OLT upstream port traffic analysis report

OLT PON port traffic analysis report

ONU PON port traffic analysis report

MSAN upstream port traffic analysis report

PON MSAN service port traffic analysis report

Upstream link traffic area statistics report

Upstream link traffic threshold-crossing percentage report

Network resource information area statistics report

15-minute raw performance data report

5.3.2 Network Resource Analysis

The UMC2 measures and analyzes the usage and running status of network resources in real
time. It helps users grasp the current network capacity and analyze bottlenecks of network
resources. In this way, the UMC2 provides data support for expansion or optimization of
network resources.

PON Reports

In PON solutions, the UMC2 measures physical and network resources. Available features
are

u General report: Manages resource statistics report templates, displays reports and
exports reports at preset time.

u Physical resource statistics: Collects NE / card / port / ONU / ONU port resource data
and exports statistics reports, providing reference for load balancing.

u Network status statistics: Collects ONU health, optical power and VEIP data service
configuration data and exports statistics reports, keeping OAM engineers informed of
current resource usages and prepared for subsequent network resource planning.

Version: A/02 63
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Automatic Resource Inspection

In routine maintenance, when configurations and states of network resources (NEs, cards,
ports, services, etc.) become abnormal, maintenance engineers have to spend much time in
locating and troubleshooting. To address this issue, the UMC2 provides automatic
inspection to check for abnormal indicators in network resources periodically, preventing
device failures and network anomalies in advance. Available features are

u Inspection report: Gives network health scores and levels for monitoring health
indicators of inspection items at any time.

u Early warning indication: Marks device data exceeding usage thresholds in special
colors to show risks in advance.

Automatic inspection covers NE status, NE configuration, network configuration, and

network status. Available features are as follows.

Table 5-12 Automatic Inspection Items in PON Solutions

Inspection Item Function

Card status check When a card is present, it passes the check; otherwise, it fails the check.

If a card's temperature is within the preset range, it passes the check;

Card temperature check
otherwise, it fails the check.
If a core switch card's CPU usage is within the preset range, it passes the
MCU CPU utilization check
check; otherwise, it fails the check.

MCU memory utilization If a core switch card's memory usage is within the preset value range, it
check passes the check; otherwise, it fails the check.

If a fan is found with alarms, it fails the check; otherwise, it passes the
Device fan check
check.
OLT device
If a core switch card's reset count is within the preset value range over a
hardware status MCU reset check
specified time range, it passes the check; otherwise, it fails the check.

If the Flash remaining space is within the preset value range, it passes the
Flash remaining space check
check; otherwise, it fails the check.
If ambient humidity is within the preset value range, it passes the check;
Ambient humidity check
otherwise, it fails the check.
If ambient temperature is within the preset value range, it passes the check;
Temperature check
otherwise, it fails the check.

Long-term inactive ONU If an ONU's out-of-service time is within the value range, it passes the
check check; otherwise, it fails the check.

OLT device If an NE's software version is in the list of allowed versions, it passes the
NE software version check
software status check; otherwise, it fails the check.

64 Version: A/02
 5 Functions

Table 5-12 Automatic Inspection Items in PON Solutions (Continued)

Inspection Item Function

If a card's software version is in the list of allowed versions, it passes the
Card software version check
check; otherwise, it fails the check.

PON port protection group If a PON port protection group's management status or operation status is
status check abnormal, it fails the check; otherwise, it passes the check.

If access control is enabled for Telnet, SSH and SNMP, it passes the check;
Firewall open status check
otherwise, it fails the check.
If a patch version is in the list of allowed versions, it passes the check;
Patch legality
otherwise, it fails the check.
If an ONU's software version is in the list of allowed versions, it passes the
ONU software version check
check; otherwise, it fails the check.
If an ONU's hardware version is in the list of allowed versions, it passes
ONU hardware version check
the check; otherwise, it fails the check.
If an NE is found with system interruption alarms, it fails the check;
NE monitoring check
otherwise, it passes the check.

If an NE is found with one of focused alarms, it fails the check; otherwise,

NE alarm check
it passes the check.

Frequent fiber cut alarm If an ONU's fiber cut alarm count is within a preset value range over a
check specified time period, it passes the check; otherwise, it fails the check.

If a port is found with link interruption, signal deterioration (over-high link

GE and 10GE port working
attenuation) or other alarms, it fails the check; otherwise, it passes the
status check
check.
MAC address aging time If MAC address aging time is equal to the threshold, it passes the check;
OLT device check otherwise, it fails the check.
service status Check a PON port's Rx CRCs three times in a row at an interval of one
PON port error packet check minute and compare the CRCs to see whether the CRCs increase every
time. If yes, it fails the check; otherwise, it passes the check.

Upstream optical path's error Compare a link's performance value with that over last 15 minutes. If no
code check change is found, it passes the check; otherwise, it fails the check.

Upstream bandwidth usage If an upstream port's bandwidth usage is within the preset value range, it
check passes the check; otherwise, it fails the check.

Card performance If a card's all performance classification switches are turned on, it passes
classification switch check the check; otherwise, it fails the check.

Dual upstream link protection If dual upstream link protection is configured, it passes the check;
status check otherwise, it fails the check.
If both active and standby cards are present, they pass the check;
Dual MCU check
OLT device otherwise, they fail the check.
configuration If dual power sources are configured correctly, they pass the check;
Dual power check
otherwise, they fail the check.

Version: A/02 65
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 5-12 Automatic Inspection Items in PON Solutions (Continued)

Inspection Item Function

If a trap server is not in the list of allowed servers, the number of trap
NE trap server configuration
servers exceeds the preset value, or the trap server address is not
check
configured, it fails the check; otherwise, it passes the check.

NE SNMP read / write If the SNMP read / write community name is in the list of illegal
community name check community names, it fails the check; otherwise, it passes the check.

OLT configuration data auto If the configuration saving period and frequency are within the preset value
saving check range, they pass the check; otherwise, they fail the check.

If the difference between device time and local time is within the value
NE time setting check
range, it passes the check; otherwise, it fails the check.

If the NTP is enabled and the NTP server address is legal, it passes the
Clock check
check; otherwise, it fails the check.
If multiple upstream ports join the same VLAN in UNTAG mode or
OLT device Upstream port ring network
loopback detection is not enabled, it fails the check; otherwise, it passes
network hidden danger check
the check.
configuration
Broadcast / unknown unicast
If packet suppression settings of an upstream port meet the expectation, it
/ unknown multicast
passes the check; otherwise, it fails the check.
suppression check

Anti-MAC address spoofing If MAC anti-spoofing settings meet the expectation, it passes the check;
check otherwise, it fails the check.
IP address check against the If an NE's IP address is within the preset value range, it passes the check;
planning otherwise, it fails the check.

Card protection switching If switching occurs between active and standby cards, it fails the check;
check otherwise, it passes the check.

OLT device Aggregation port protection If switching occurs in a PON port protection group, it fails the check;
network status switching check otherwise, it passes the check.

If the Tx / Rx optical power is within the preset value range, it passes the
Working optical power check
check; otherwise, it fails the check.

Optical module type match If the optical module is present, and the optical module type and port type
check are inconsistent, it fails the check; otherwise, it passes the check.

If a trap server is not in the list of allowed servers, the number of trap
NE trap server configuration
servers exceeds the preset value, or the trap server address is not
check
configured, it fails the check; otherwise, it passes the check.

NE SNMP read / write If the SNMP read / write community name is in the list of illegal
MDU equipment
community name check community names, it fails the check; otherwise, it passes the check.
status
If the difference between device time and local time is within the value
NE time setting check
range, it passes the check; otherwise, it fails the check.

If ambient temperature is within the preset value range, it passes the check;
Temperature check
otherwise, it fails the check.

66 Version: A/02
 5 Functions

Table 5-12 Automatic Inspection Items in PON Solutions (Continued)

Inspection Item Function

If a core switch card's CPU usage is within the preset value range, it passes
MCU CPU usage check
the check; otherwise, it fails the check.

MCU memory utilization If a core switch card's memory usage is within the preset range, it passes
check the check; otherwise, it fails the check.
If a fan is found with alarms, it fails the check; otherwise, it passes the
Device fan check
check.
If an NE is found with one of focused alarms, it fails the check; otherwise,
NE alarm check
it passes the check.

IP address check against the If an NE's IP address is within the preset range, it passes the check;
planning otherwise, it fails the check.
If an NE's software version is in the list of allowed versions, it passes the
NE software version check
MDU equipment check; otherwise, it fails the check.
software status If an NE's software version is in the list of allowed versions, it passes the
Card software version check
check; otherwise, it fails the check.
If the UMC² server's CPU usage, memory usage and hard disk usage are
UMC² server usage check
within the preset range, it passes the check; otherwise, it fails the check.

If all processes in the list of startup processes are properly started, their
process IDs are consistent with initial process IDs (no abnormal restart),
UMC² server NE software process check
and their CPU and memory usages are within the preset range, they pass
software and
the check; otherwise, they fail the check.
hardware check
If the total consumption of all license control items does not exceed the
UMC² license check
limit, it passes the check; otherwise, it fails the check.

If the data space usage and log space usage are within the preset range,
UMC² database check
they pass the check; otherwise, they fail the check.

Information statistics of
pluggable optical modules

Faulty card check

u Problem level: warning (default), general or severe
PON port CRC error packet
u Failure alarmNote 1: Select All (default), Single Alarm, Multiple Alarm
statistics
OLT device and and Empty
Faulty port optical module
health statistics u Port type: PON port, upstream port, PON port / upstream port (default)
statistics
and empty
Unplugged module statistics

Fan statistics
GPON / EPON mixed
insertion statistics
OLT security If a device uses an SSH protocol of reference version or later, it is secure;
NE SSH configuration check
configuration otherwise, it is insecure.

Version: A/02 67
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 5-12 Automatic Inspection Items in PON Solutions (Continued)

Inspection Item Function

NE SNMP configuration If a device uses an SNMP protocol of reference version or later, it is
check secure; otherwise, it is insecure.
Auto system log upload FTP If a device uses SFTP for automatic system log uploading, it is secure;
type check otherwise, it is insecure.
If a device can be accessed through Telnet, it is insecure; otherwise, it is
Device Telnet service check
secure.
If a device uses a TLS protocol of reference version or later, it is secure;
Device TLS version check
otherwise, it is insecure.

5.3.3 Network Quality Analysis

The UMC2 monitors various optical performance indicators, and measures usages of
networkwide resources, keeping users informed of service quality changes and resource
usage trends in real time.

PON Faults

The UMC2 provides multi-dimensional optical power analysis. It helps users grasp network
quality in real time, discover deterioration trends in time, and ensure network security. In
PON solutions, available features are

u Abnormal optical power analysis: Queries networkwide optical power anomalies.

Displays the number and proportion of OLT upstream ports, OLT PON ports and ONU
PON ports with weak optical signals by area or OLT NE. Instructs users to check the
cause of weak optical power of ports and eliminate network failures in time.

u ONU low optical power analysis: Provides rules to determine why low optical power
occurs. Classifies and marks ONUs with low optical power. Provides detailed reports
on ONU low optical power, instructing users to analyze causes and rectify ONUs with
low optical power.

u Optical path fault delimitation: Analyzes optical path alarms and states in real time
based on big data and AI algorithm model, identifies fault types automatically and
delimits faults.

4 Trunk optical path failure

4 Branch optical path failure

68 Version: A/02
 5 Functions

4 Drop optical path failure

4 Central office optical module failure

4 Remote optical module failure

4 ONU power dump

u Device health analysis: The UMC2 analyzes health status of devices to identify
exceptions in network resources in advance. This ensures proper device operation,
smooth service flow, and high network security.

4 OLT health analysis: Counts the number / duration / start time of interruptions for
OLTs, helping OAM engineers locate the cause of failure.

4 Card health analysis: Measures card temperature, CPU usage, memory usage and
other abnormal data to help OAM engineers find faulty OLT cards and handle
them timely. This function ensures proper device operation, smooth service flow,
and high network security.

4 ONU health analysis: Counts the number / duration of interruptions, fiber cuts,
and power failures for ONUs, helping OAM engineers locate the cause of
failures.

u Automatic optical power report: The UMC2 can automatically generate reports by
specified cycle (day / week / month) and send notifications to specified email
addresses. If an upload policy is set, the UMC2 can automatically save reports locally
or upload them to a specified server via FTP / SFTP.

Table 5-13 Automatic Reports for PONs

Report Type Applicable Object Type

OLT Uplink Port

Optical power report OLT PON Port
ONU PON Port

Version: A/02 69
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 5-13 Automatic Reports for PONs (Continued)

Report Type Applicable Object Type

MSAN Uplink Port

70 Version: A/02
6 Reliability

The UMC2 is highly reliable. It can prevent possible risks to ensure safe system operation.

6.1 Reliability Design

The UMC2 provides reliable hardware configurations and software / system designs to
prevent unknown risks. In this way, the UMC2 ensures safe operation of the system and can
well cope with unexpected events caused by external environment, misoperation and
system failure.

6.1.1 Hardware Reliability

The UMC2 provides a detailed and highly reliable hardware protection scheme to prevent
unknown risks of hardware. This ensures safe and stable operation of the system.

The UMC2 can automatically analyze the health status of current network hardware. It can
display the cause of anomalies, locate abnormal hardware, and help solve hardware failures.

Protection Mechanism

When the hardware with redundancy protection fails, its backup hardware is activated and
takes over services. This keeps the UMC2 operating system and app services free from
influence.

Protection Capability

Figure 6-1 and Table 6-1 show the protection schemes and capability of the hardware.

Version: A/02 71
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Figure 6-1 Hardware Reliability Protection Scheme

Table 6-1 Hardware Reliability Protection Scheme

Protection
Protection Scheme Protection Capability
Type

u Management system: dual IIC management

networks
Hardware
u Fans: primary fan unit having 10 groups of u RPO = 0Note 1
redundancy
cooling modules, each group in 1+1 redundancy u RTO = 0Note 2
protection
u Power supply: power modules in N+1 or N+N
redundancy

FiberHome, based on VMware vSphere HA, defines all

physical servers as a cluster and specifies an idle server
Physical server
as the protection one. When a physical server in the u RPO = 0
1:N cluster
cluster fails, the virtual machine on it will be u RTO ≤ 15 minutes
protection
automatically switched to the protection physical
server, restart and keep running.

72 Version: A/02
 6 Reliability

Table 6-1 Hardware Reliability Protection Scheme (Continued)

Protection
Protection Scheme Protection Capability
Type

FiberHome server: Configures two drives of each blade

u RPO = 0
RAID as RAID1.
u RTO = 0
Disk array: RAID5 + Hot Spare

Note 1: Recovery point objective (RPO): Denotes the maximum tolerable amount of data loss in the
event of a failure or disaster.
Note 2: Recovery time objective (RTO): Denotes the maximum acceptable time to recover a network or
apps and regain data after a failure or disaster.

6.1.2 Software Reliability

The UMC2 provides a detailed and highly reliable protection scheme for apps to prevent
unknown software risks, keeping the UMC2 secure and stable.

Protection Mechanism

The protection mechanism includes monitoring system processes in real time and backing
up / recovering data. In this way, the UMC2 prevents software failures and ensures stable
operation.

Protection Capability

Table 6-2 describes the protection scheme and capability for software.

Version: A/02 73
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 6-2 Software Reliability Protection Scheme

Protection Type Protection Scheme Protection Capability

u Process restart: Monitors the system process status in real

time. If a certain process in the services is aborted or faulty,
the UMC2 will try to restart the process in N (user-defined)
consecutive attempts. If the failure persists, an alarm will be
reported to remind users to handle it manually.
u Automatic switching of application services:
u Restart time of a process < 5
4 Veritas hot standby deployment scheme: When active
minutes
and standby nodes are working as expected, only the
u Application service switching:
App protection service on the active node is running. If the service
process of the active node is faulty, the UMC2 will 4 RPO = 0Note 1
automatically start the service on the standby node and
switch to the service instance thereon.
4 RTO < 1 minuteNote 2

4 Cluster deployment scheme: When cluster nodes are

working properly, they are multi-active. If one of them
is faulty, other nodes will share the load carried by the
faulty node, and continue to provide services in load-
balanced way.

u RAID: RAID5+Hot Spare

u Data backup and recovery: Backs up and recovers data
quickly using backup files when an exception occurs on the
UMC2.
u Two-disk-array disaster-recovery deployment scheme: u Backup duration < 60 minutes
Data protection u Recovery duration < 120
4 Local HA system with two disk arrays: Protects data by
minutes
mirror copy of disks.

4 Remote HA system with two disk arrays: Synchronizes

VVR data to the remote disaster-recovery station
through a private line for data replication.

Note 1: Recovery point objective (RPO): Denotes the maximum tolerable amount of data loss in the event of a failure or
disaster.
Note 2: Recovery time objective (RTO): Denotes the maximum acceptable time to recover a network or apps and regain data
after a failure or disaster.

74 Version: A/02
 6 Reliability

6.2 Hot-Standby Disaster Recovery Scheme

UMC2 servers are deployed with cluster hot-standby disaster recovery to improve reliability.
If the active station fails, applications on the UMC2 are switched to the standby station,
allowing uninterrupted operation.

Protection Mechanism

In the cluster hot-standby disaster recovery scheme, the UMC2 uses the Veritas remote hot
standby technology to enable real-time data synchronization between active and standby
stations and dynamically monitor the running status of the UMC2. When the active station
fails, the protection mechanism works as follows:

u Applications are automatically switched to the standby station and the network is still
being monitored. This ensures normal operation of the system.

u When the original active station recovers, users can manually perform switching by
one click at the active station to restore the original active-standby relationship.

Protection Capability

Item Specification Remark

Mean time between failures A failure refers to a database
More than six months
(MTBF) crash.
A failure refers to a database
Mean time to repair (MTTR) No more than 15 minutes
crash.
In a deployment scheme with
Switching time No more than 20 minutes physical computers, failure
detection time is excluded.
Note 1: When the heartbeat link is interrupted, an active-active situation may occur. Handle as follows.

u During short interruption, do not issue configuration data to avoid loss of such data after
heartbeat recovery.

u During long interruption, manually switch to the standby station and configure services as
needed, which will be synchronized to the active station after heartbeat recovery.

6.3 DCN Protection Scheme

The UMC2 connects to the active and standby GNEs through a DCN. This method allows a
more reliable communication between the UMC2 and the device.

Version: A/02 75
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Protection Mechanism

When an active GNE is faulty, the UMC2 can automatically switch to communicate with the
standby GNE. This ensures the UMC2 communicates properly with other NEs in the GNE
group.

Protection Scheme

Users can set a GNE group and set the active and standby GNEs in this GNE group on the
UMC2. Normally, the UMC2 forwards messages and communicates with other NEs in this
GNE group through the active GNE NE. When the active GNE fails, the standby GNE
takes over.

76 Version: A/02
7 Technical Specifications

This chapter describes technical specifications of the UMC2.

7.1 Performance Specifications

This section introduces performance specifications of the UMC2.

Table 7-1 System Availability

Item Specification
Annual system availability for managing up to 300 000 equivalent NEs ≥ 99.9% (7 × 24)

Mean time to repair (MTTR) for managing up to 300 000 equivalent NEs ≤ 2 hours
Frequency of failure (MTBR) for managing up to 300 000 equivalent NEs ≤ three times/year

Automatic switching time when the core host node service deployed by
≤ 5 seconds
the UMC² is abnormal
Migration time for management tasks when adding or reducing
≤ 5 seconds
application host nodes online, or deleting host nodes

Migration time for proactive discovery and handling of host node failures
≤ 5 seconds
and automatic task migration

Table 7-2 System Processing Capability – PON Solutions

Item Specification

Total users ≤ 2000

Online users ≤ 1000
Concurrent users ≤ 1000
System homepage delay (time from clicking “exe” to the display of
≤ 10 seconds
the main screen at the client)

System global startup time for 5000 NEs ≤ 60 seconds

System global startup time for 10 000 NEs ≤ 120 seconds
System global startup time for 100 000 NEs ≤ 300 seconds
Screen response delay for a single operation ≤ 2 seconds
Screen response delay for batch operations ≤ 5 seconds
Topology drag response time, hold response time < 300 milliseconds
Report generation delay ≤ 8 seconds
Current alarm management capacity for a single NE ≤ 100 000

Version: A/02 77
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 7-2 System Processing Capability – PON Solutions (Continued)

Item Specification
Current alarm management capacity for less than 10 000 NEs ≤ 1 million
Current alarm management capacity for 100 000 NEs ≤ 2 million
Single-instance current alarm processing efficiency (throughput) > 1500 alarms per second

Multi-instance current alarm processing efficiency (throughput) ≤ 5000 alarms per second

Alarm delay (time from the occurrence of an alarm on an NE to the

≤ 5 seconds
display of the alarm on the UMC²)

History alarm management capacity for less than 10 000 NEs ≤ 100 million
History alarm management capacity for 100 000 NEs ≤ 1 billion
Arrival time of the first batch of current / history alarms < 1 second
30 000 current / history alarm loading time ≤ 5 seconds
2 million current / history alarm loading time ≤ 5 minutes
Main topology alarm statistics display time for 100 000 current alarm
< 3 seconds
statistics (current template)

Main topology alarm statistics display time for 2 million current alarm
< 7 seconds
statistics (current template)

Time for displaying alarm indicators after an NE manager is opened < 1 second
Time for displaying alarm statistics after an NE manager is opened < 1 second
History performance single-instance management equivalent NE count ≤ 1300
History performance management capacity for less than 10 000 NEs ≤ 200 billion
History performance management capacity for 100 000 NEs ≤ 2 000 billion
Arrival time of the first batch of history performance data < 1 second
30 000 history performance loading time ≤ 5 seconds
2 million history performance loading time ≤ 5 minutes
Performance statistics delay (time from the end of a performance
≤ 2 minutes
statistics cycle to storage of performance data in the database)

Event management capacity for a single NE 100 000

Event management capacity for less than 10 000 NEs 1 000 000
Event management capacity for 100 000 NEs 5 000 000
Single-instance event processing efficiency (throughput) > 1500 events per second

Multi-instance event processing efficiency (throughput) ≤ 5000 events per second

Configuration data synchronization delay (time from modification of

≤ 2 minutes
NE configuration data to storage of such data in the database)

78 Version: A/02
 7 Technical Specifications

Table 7-3 Data Dump Capability

Item Specification
Configuration data Long-term storage

Number of active alarms ≤ 500 000

History alarm ≤ 3 months
Number of middleware cache alarms ≤ 200 000
15-minute performance indicator ≤ 6 months
24-hour performance indicator ≤ 1 year

Self-monitoring data ≤ 6 months

Operation log data ≤ 6 months
Statistics report ≤ 2 years

7.2 Management Capability

Management capability refers to how many network resources that the UMC 2 can manage.
The management capability of the UMC2 is measured by management capacity and the
number of managed equivalent NEs.

7.2.1 Management Capacity

The table below describes the maximum management capacity of a single UMC2 system.

Table 7-4 System Management Capacity

Item Sub-Item Specification

NE Equivalent NEs 300 000

7.2.2 Equivalent Coefficient

Equivalent NE is an NE analogy method based on a unified standard. The number of NEs

that can be managed by the UMC2 depends on the types of NEs. To simplify description
and calculation of management capability, the number of different types of NEs and ports
are converted into equivalent NEs according to how much system resources they occupy.
This method provides a unified calculation standard to measure management capacity.

Version: A/02 79
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Calculation of Equivalent NEs

UMC2 equivalent NEs are calculated based on the following principles.

u Equivalent coefficient is used to convert physical resources to equivalent NEs. It is the

ratio of resources occupied by a physical NE (subrack) to those occupied by an
equivalent NE. Equivalent coefficient = resources occupied by a physical NE (subrack)
/ resources occupied by an equivalent NE. Generally port resources are counted.

u Number of equivalent NEs on the UMC2 = ∑number of physical NEs × equivalent

coefficient

u A UMC2 system can manage up to 300 000 equivalent NEs and 100 clients.

7.2.2.1 Equivalent Coefficients of OLT NEs

The table below lists equivalent coefficients of OLT NEs.

Physical NE Type Equivalent Coefficient

AN5116-04B 0.64
AN5116-06B 5.12
AN5516-04 0.64
AN5516-06 1.92
AN6000-15 4.8
AN6000-17 5.44
AN6000-2 0.64
AN6000-7 2.24
AN6001-G16 5.44

7.2.2.2 Equivalent Coefficients of ONU NEs

The table below lists equivalent coefficients of ONU NEs.

Physical NE Type Equivalent Coefficient

AN1100-D4 0.02
AN1100-D4W 0.02
AN5006-01-A 0.04
AN5006-01-B 0.06
AN5006-01-B1 0.06
AN5006-02 0.04

80 Version: A/02
 7 Technical Specifications

Physical NE Type Equivalent Coefficient

AN5006-02A 0.04
AN5006-02-A 0.04
AN5006-02-B 0.06
AN5006-03 0.04
AN5006-03-AK 0.04
AN5006-03B 0.04
AN5006-03C 0.04
AN5006-04 0.06
AN5006-04C 0.06
AN5006-04-CC 0.04
AN5006-04-CC-W 0.04
AN5006-04-D 0.04
AN5006-04F1 0.06
AN5006-04P1 0.06
AN5006-04P2 0.06
AN5006-04P3 0.04
AN5006-04P4 0.06
AN5006-04P4-F 0.06
AN5006-04P4-FX 0.06
AN5006-05 0.06
AN5006-05A 0.06
AN5006-05C 0.06
AN5006-06A 0.06
AN5006-06A-A 0.08
AN5006-06B 0.08
AN5006-06D 0.08
AN5006-07A 0.08
AN5006-07-AK 0.06
AN5006-07B 0.12
AN5006-07C 0.12
AN5006-08A 0.02
AN5006-08B 0.08
AN5006-09A 0.06
AN5006-09-AK 0.04
AN5006-09B 0.08
AN5006-09C 0.04
AN5006-10 0.1
AN5006-10-AK 0.08
AN5006-10B 0.16

Version: A/02 81
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Physical NE Type Equivalent Coefficient

AN5006-11 0.02
AN5006-12 0.02
AN5006-15 0.02
AN5006-16 0.04
AN5006-20 0.64
AN5006-30 2.56
AN5121-4E 0.04
AN5121-4EP 0.04
AN5121-4G 0.04
AN5121-4GP 0.04
AN5121-8ER 0.04
AN5121-8GR 0.04
AN5141 0.04
AN5161-CEF 0.04
AN5161-CGF 0.04
AN5171F 0.02
AN5172-8GR 0.02
AN5172-8GR-FTTH 0.02
AN5172F 0.02
AN5200-04A 0.04
AN5200-07A 0.08
AN5200-07-AK 0.08
AN5200-07B 0.12
AN5200-09A 0.06
AN5200-09B 0.08
AN5200-10A 0.1
AN5200-10B 0.16
AN5220 0.64
AN5221-16N 0.06
AN5221-16NP 0.06
AN5221-24N 0.08
AN5221-24NP 0.08
AN5221-8N 0.04
AN5221-8NP 0.04
AN5231-16N 0.1
AN5231-16T-EG 0.1
AN5231-24N 0.14
AN5231-8N 0.06
AN5261-CNFP-A 0.06

82 Version: A/02
 7 Technical Specifications

Physical NE Type Equivalent Coefficient

AN5340 0.04
AN5342 0.06
AN5346 0.06
AN5506-01-A1 0.04
AN5506-01-B1 0.06
AN5506-01-VP 0.02
AN5506-02-A 0.04
AN5506-02-AKW 0.04
AN5506-02-B 0.06
AN5506-02-D 0.04
AN5506-02-F 0.06
AN5506-04-A 0.04
AN5506-04-A1 0.04
AN5506-04-B 0.06
AN5506-04-B2 0.06
AN5506-04-C1 0.06
AN5506-04-CA 0.04
AN5506-04-CC 0.04
AN5506-04-CC-W 0.04
AN5506-04-D 0.04
AN5506-04-F1 0.06
AN5506-04-FA 0.06
AN5506-04-FAT 0.06
AN5506-04-G1 0.06
AN5506-04-P1 0.04
AN5506-06-E 0.06
AN5506-06-EG 0.04
AN5506-06-G 0.04
AN5506-07-A1 0.06
AN5506-07-A1K 0.06
AN5506-07-A2 0.06
AN5506-07-B 0.1
AN5506-07-B1 0.1
AN5506-09-A1 0.04
AN5506-09-A1K 0.04
AN5506-09-B1 0.06
AN5506-10-A1 0.08
AN5506-10-A1K 0.08
AN5506-10-B1 0.14

Version: A/02 83
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Physical NE Type Equivalent Coefficient

AN5600-01 0.04
AN5640 0.04
AN5642 0.06
AN5646 0.06
AN5646Q 0.06
AN5646T 0.06
AN5656T 0.06
AN6006-02 0.04
AN6006-07 0.08
EPONCURRENCYSFU 0.08
EPONUNKOWN 0.06
GPONCURRENCYSFU 0.06
GPONUNKOWN 0.06
HG220 0.02
HG226 0.02
HG260 0.02
HG261 0.02
HG266 0.02
HG268 0.02
HG5245SH 0.02
HG5245ST 0.02
HG6021C 0.02
HG6145E 0.02
HG6243C 0.02
HG6244C 0.02
HG6245D 0.02
HG6245P 0.02
HG6249A 0.02
HG6543C 0.02
HG-A8-C 0.02
HG-E8-C 0.02
OTHER_ONU1 0.06
OTHER_ONU2 0.06
OTHER_ONU3 0.04
OTHER_ONU4 0.06
OTHER_ONU6 0.02
OTHER_ONU7 0.06

84 Version: A/02
8 PON Series

Table 8-1 and Table 8-2 list the PON series devices supported on the UMC².

Note:

The ONUs not listed in the tables are supported through ONU capacity set
templates.

Table 8-1 NE Devices

Type Model

AN5116-04B
AN5116-06B
AN5116-02
AN5116-06
AN5116-01
AN5516-04
OLT
AN5516-06
AN6000-15
AN6000-17
AN6000-2
AN6000-7
AN6001-G16
AN5006-04P4

AN5006-11

AN5006-12

AN5006-20

Independent NE MDU / AN5006-30

ONU AN5006-15

AN5006-16

AN5172-8GR

AN5220

AN5506-10-B

Version: A/02 85
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table 8-2 ONU Devices

Type Model

AN5600-01
AN5640
AN5642
AN5646
AN5646T
AN5656T
XGPON ONU AN5646Q
AN5006-20 / 30
AN5221-8N / 8NP / 16N / 16NP / 24N / 24NP

AN5231-8N / 16N / 24N

AN5261-CNFP-A

HG5245ST / H

AN5506-01-A1 / B1

AN5506-02-A / B / D / F / AKW
AN5506-04-A / B / D
AN5506-04-A1 / B2 / C1 / F1 / G1
AN5506-04-CA / CC / CC-W / FA / FAT / P1
AN5506-07-A1 / A2 / B / B1 / A1K

AN5506-06-E / G / EG

AN5506-09-A1 / A1K / B1

AN5506-10-A1 / A1K / B1

GPON ONU AN5006-15 / 20 / 30

AN5121-4G / 4GP / 8GR

AN5220

AN5172-8GR / 8GR-FTTH

AN5161-CGF
HG6021C, HG6145E, HG6243C, HG6245D, HG6543C, HG6244C,
HG6245P, HG6249A

HG260, HG261, HG266, HG268

HG-A8-C

HG-E8-C

Universal EPON SFU

EPON ONU AN5006-01-A / B
AN5006-02-A

86 Version: A/02
 8 PON Series

Table 8-2 ONU Devices (Continued)

Type Model

AN5006-03, AN5006-03-AK, AN5006-03B / C

AN5006-04C, AN5006-04-E / CC / D, AN5006-04-CC-W, AN5006-

04F1, AN5006-04P2 / P3 / P4, AN5006-04P4-F / FX

AN5006-05C

AN5006-06A / B / D, AN5006-06A-A, AN5006-06C

AN5006-07A / B, AN5006-07-AK, AN5006-07C

AN5006-09A / B, AN5006-09-AK, AN5006-09C

AN5006-10, AN5006-10B, AN5006-10-AK

AN5006-12, AN5006-15, AN5006-16, AN5006-20, AN5006-30

AN5121-4E / 4EP, AN5121-8ER

AN5161-CEF

AN5200-04A

AN5200-07-AK, AN5200-07A / B

AN5200-09A / B

AN5200-10A / B

AN5340, AN5346, AN5342

HG220, HG226

Version: A/02 87
 Appendix A Standard Compliance

The UMC2 complies with ITU-T, IETF and TMF MTNM standards and protocols.

Table A-1 describes the standards and protocols in details.

Table A-1 Standards and Protocols

Number Title
ITU-T G.8080 Automatic switched transport network architecture

ITU-T G.852.3 Topology management

ITU-T G.874 Management aspects of the optical transport network element

Optical transport network: Protocol-neutral management information model for

ITU-T G.874.1
the network element view
ITU-T G.7712 Architecture and specification of Data Communication Network

ITU-T G.7718 Protocol - Neutral Management Information model for the control plane view
ITU-T M.3000 Overview of TMN recommendations
ITU-T M.3010 Principles for a telecommunications management network
ITU-T M.3100 Generic network information model
ITU-T M.3400 TMN management functions

Management Framework for Open Systems Interconnection (OSI) for CCITT

ITU-T X.700
Applications

ITU-T X.720 Management information model

ITU-T X.721 Management information definition

RFC 793 Transmission Control Protocol (Darpa Internet Program Protocol Specification)

Structure of Management Information for Version 2 of the Simple Network

RFC 1902
Management Protocol

RFC 1903 Textual Conventions for Version 2 of the Simple Network Management Protocol

Conformance Statements for Version 2 of the Simple Network Management

RFC 1904
Protocol
RFC 1905 Protocol Operations for Version 2 of the Simple Network Management Protocol

RFC 1906 Transport Mappings for Version 2 of the Simple Network Management Protocol

Management Information Base for Version 2 of the Simple Network

RFC 1907
Management Protocol

Coexistence Between Version 1 and Version 2 of the Internet-standard Network

RFC 1908
Management Framework
RFC 5277 NETCONF Event Notification

88 Version: A/02
 Appendix A Standard Compliance

Table A-1 Standards and Protocols (Continued)

Number Title
RFC 5440 Path Computation Element (PCE) Communication Protocol (PCEP)

RFC 6241 Network Configuration Protocol (NETCONF)

RFC 6242 Using the NETCONF Protocol over Secure Shell (SSH)

RFC 6991 Common YANG Data Types

RFC 8071 NETCONF call home and RESTCONF call home
Path Computation Element Communication Protocol (PCEP) Extensions for
RFC 8231
Stateful PCE
Optimizations of Label Switched Path State Synchronization Procedures for a
RFC 8232
Stateful PCE
RFC 8299 YANG Data Model for L3VPN Service Delivery

RFC 8346 A YANG Data Model for Layer 3 Topologies

RFC 8453 Framework for Abstraction and Control of TE Networks (ACTN)

RFC 8454 Information Model for Abstraction and Control of TE Networks (ACTN)

RFC 8466 A YANG Data Model for L2VPN Service Delivery

RFC 8040 RESTCONF Protocol
TMF513 Multi-Technology Network Management - information model

TMF513 V3.2 Multi-Technology Network Management (MTMN) Business Agreement

TMF608 Multi-Technology Network Management - business model

TMF608 V3.5 Multi-Technology Network Management (MTMN) Information Agreement

TMF814 Multi-Technology Network Management - Solution Conformance Statement

TR512 v1.4 OnfCoreIm-info

Version: A/02 89
 Appendix B Service Ports

If a firewall is deployed in networks, external service ports of the UMC 2 should be enabled
to ensure proper communication. These service ports are listed as follows.

Table B-1 Ports Connecting the Server and Clients

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
IP segment Port only used to operate
of the the Windows server
server 3389 through a remote
cluster desktop, and not used by
Remote
disaster the UMC².
server Client IP
Inbound TCP Any recovery
mainte- segment
network /
nance Port used by the Linux
server
22 system for remote
manage-
security maintenance.
ment
network
IP segment
of the
server
cluster
Server disaster Port used for pinging the
Client IP
availability Inbound ICMP Any recovery - server to check its
segment
detection network / availability.
server
manage-
ment
network

90 Version: A/02
 Appendix B Service Ports

Table B-1 Ports Connecting the Server and Clients (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
FTP service common
port for NE software
management and reports.
The UMC² server and
client transfer files
20, 21
(including NE software
packages, NE
configuration files and
reports) via FTP on this
port.

Sock proxy protocol port,

allowing a client isolated
1080
from device networks to
IP segment access devices.
of the
Tomcat listening port
server
8080 used for releasing OMC
cluster
clients.
disaster
UMC² rich Client IP Port used by the
Inbound TCP Any recovery
client segment 8500 microservice registry
network /
center.
server
Port used for
manage-
26011 to communication between
ment
26499 the icebox service and
network
client.
Specified data port range
28001 to
in FTP passive transfer
29000
mode.
Port used by the UMC²
ICE bus registry to
52001
discover the IP addresses
of other ICE services.
Nginx service port used
for communication
52302 between the client and
the OMC NMS
Management Tool.

Nginx service port used

Client IP Web server
Web client Inbound TCP Any 80, 443 for accessing the OMC
segment IP
via a browser.

Version: A/02 91
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table B-1 Ports Connecting the Server and Clients (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
NMS Management Tool
used for importing /
exporting UMC²
22302
configurations and
starting / stopping UMC²
services.
Port used by the
microservice O&M
8088 center for software
deployment and
monitoring.

Table B-2 Ports Connecting the Server and Devices

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
Port used for reporting
device performance
20, 21 actively and backing up
Proactive configurations on the
reporting UMC².
NE IP Server NIC
from Inbound TCP Any SFTP service
segment IP segment 22
devices – communication port.
reliability Specified data port range
28001 to
in FTP passive transfer
29000
mode.
4334 Netconf callhome port.

SSH protocol port that

sets up SSH connections
for delivering
Device configurations and
Server NIC IP NE IP
monitoring Outbound TCP Any 22, 830 control commands,
segment segment
– reliability reading device status and
configurations, and
listening to device event
reports.

92 Version: A/02
 Appendix B Service Ports

Table B-2 Ports Connecting the Server and Devices (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
Telnet protocol port used
by NE management
23, 2650 processes to configure
devices and synchronize
resources.
Port mode used by an
FTP tool such as Winscp
logging into a device to
21 get device configuration
files, with specified data
port range from 28001 to
29000.
DHCP service common
port used by NEs to get
Auto IP IP addresses
Inbound /
allocation UDP Any Any Any 67, 68 automatically. It uses
outbound
to NEs broadcast addresses, and
so its IP addresses are
unlimited.

Proactive Port used by devices to

7887 to
reporting report alarms and events
7889
from NE IP Server NIC to the UMC² actively.
Inbound UDP Any
devices – segment IP segment Port used by access
no 162 devices for private
connection SNMP report.

Port used by the UMC² to

7887 to
check device status and
Device 7889
issue commands.
monitoring Server NIC IP NE IP
Outbound UDP Any Port used by the UMC² to
– no segment segment
check access device
connection 161, 162
status and issue
commands.
Device Port used for pinging
NE IP
availability Outbound ICMP Any Any - NEs to check their
segment
detection availability.

Version: A/02 93
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table B-3 Ports Used by the Server's Internal Processes

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
Port used by Windows
OS remote desktop
protocol (RDP), only for
3389 operating the Windows
server through a remote

IP segment desktop (not used by the

of the UMC²).

server Used in automatic

cluster installation and
Server
disaster deployment of the
internal Inbound /
TCP Any Any recovery distributed UMC2
mainte- outbound
network / system, with the
nance
server 5985 WindowRM service
manage- enabled first.
ment Not required if automatic
network installation and
deployment is not
applied.

Port used by the Linux

22 system for remote
security maintenance.
IP segment
of the
server
cluster
Internal disaster Port used for pinging the
Inbound /
availability ICMP Any Any recovery - server to check its
outbound
detection network / availability.
server
manage-
ment
network

94 Version: A/02
 Appendix B Service Ports

Table B-3 Ports Used by the Server's Internal Processes (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
IP segment MSSQL server (UMC²,
1433
IP segment of of the value-added app).
the server server 3306,
MySQL database
cluster cluster 26500,
(UMC², Web, PAS).
disaster disaster 60298
Inbound /
Database TCP recovery Any recovery
outbound Cetus MySQL cluster
network / network / 6001,
middleware, for PAS
server server 7001
large capacity.
management manage-
ment Mongo DB (value-added
network 26501
network app).

Shared port, requiring

authentication before
445
configuration
synchronization.

Veritas Enterprise
2148 Administrator (VEA)
Server 2148.

IP segment Heartbeat port for VVR

IP segment of of the active and standby

the server server stations in the Veritas HA

Veritas system. VVR listens to
cluster cluster 4145
disaster the transmission control
disaster disaster
recovery Inbound / layer of the system via
TCP recovery Any recovery
backup outbound this port.
network / network /
system –
server server Veritas Scheduler Service
TCP
management manage- 4888 used to launch the
network ment configured schedule.
network Veritas message service,
5634
using HTTPS.

Symantec Plugin Host

Service Solutions
Configuration Center
7419
(SFWConfigPanel.exe)
CCF Engine
(CEngineDriver.exe).

Version: A/02 95
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table B-3 Ports Used by the Server's Internal Processes (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
Port used by the VVR
vradmind process of the
Veritas HA system. The
8199 vradmind process
communicates between
active and standby
stations via this port.

Port used by the VVR in.

vxrsyncd process of the
Veritas HA system. The
8989 vxrsyncd process
communicates between
active and standby
stations via this port.

Veritas High Availability

Engine Veritas Cluster
Manager (Java console)
14141
(ClusterManager.exe)
VCS Agent driver
(VCSAgDriver.exe).
14144 VCS notification.
Server egress port, which
needs to be enabled to
allow VCS cluster
14150
command "hagui"
running across the
firewall.
Veritas GCO WAC
service port of the Veritas
14155 HA system, used by the
remote connector in a
WAN cluster.
Random port for
49152 to
transferring
65535
synchronization packets.

96 Version: A/02
 Appendix B Service Ports

Table B-3 Ports Used by the Server's Internal Processes (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
Veritas Enterprise
3207 Administrator (VEA)
Server.
Heartbeat port for VVR
active and standby
stations in the Veritas HA
4145 system. VVR listens to
the transmission control
IP segment
layer of the system via
IP segment of of the
this port.
the server server
Veritas
cluster cluster Veritas High Availability
disaster
disaster disaster Engine Veritas Cluster
recovery Inbound /
UDP recovery Any recovery Manager (Java console)
backup outbound 14141
network / network / (ClusterManager.exe)
system –
server server VCS Agent driver
UDP
management manage- (VCSAgDriver.exe).
network ment 14144 VCS notification.
network Veritas GCO WAC
service port of the Veritas
14155 HA system, used by the
remote connector in a
WAN cluster.
Random port for
49152 to
transferring
65535
synchronization packets.

Port allocated randomly

IP segment
26011 to and automatically for
IP segment of of the
26299 internal communication
the server server
ICE among IceBox services.
cluster cluster
communi- Port used by the UMC²
disaster disaster
cation Inbound / ICE bus registry to
TCP recovery Any recovery 52001
between outbound discover the IP addresses
network / network /
UMC² of other ICE services.
server server
services. Icegridnode process port,
management manage-
52002 to allocated according to
network ment
52036 host SNs for bus internal
network
communication.

Version: A/02 97
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table B-3 Ports Used by the Server's Internal Processes (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
FTP service general port
for performance
collection and reports,
through which files (like
20, 21
northbound files, PAS
IP segment files, reports) are
IP segment of of the transfered based on FTP
the server server within the UMC² server.
Assisted
cluster cluster Tomcat listening port
communi-
disaster disaster 8080 used for releasing OMC
cation Inbound /
TCP recovery Any recovery
among outbound clients.
network / network /
UMC² FTP port dedicated for
server server 10201
services transferring PAS files.
management manage-
Port allocated to each
network ment
26300 to service in a fixed way for
network
26499 internal communication
among icebox services.

Specified data port range

28001 to
in FTP passive transfer
29000
mode.
NMS Management Tool
22301 to unmcmservice, for
22303 monitoring and
controlling UMC² status.
IP segment
NMS Management Tool
IP segment of of the 22304 to
nmcfgdatamgr, for
the server server 22309
managing UMC² data.
cluster cluster
NMS Management Tool
UMC² disaster disaster
Inbound / 22310, unmservicemonitor, for
service TCP recovery Any recovery
outbound 52310 starting services
monitoring network / network /
automatically.
server server
management manage- Nginx is a high-

network ment performance HTTP and

network reverse proxy server. It is

52302 used for communication
between the client and
the OMC NMS
Management Tool.

98 Version: A/02
 Appendix B Service Ports

Table B-3 Ports Used by the Server's Internal Processes (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
Port used by the python
service to receive
commands from the
5000
O&M center in case of
IP segment
distributed microservice
IP segment of of the
deployment.
the server server
cluster cluster Port used by the
disaster disaster 8088 microservice O&M
Microser- Inbound /
TCP recovery Any recovery center.
vice outbound
network / network / Port used by the
server server 8500 microservice registry
management manage- center.
network ment Port used by the
network 26300 distributed microservice
deployment proxy.
9201 to Port used by the
9202 microservice sidecar.
IP segment
IP segment of of the
the server server
cluster cluster Nginx is a high-
Web client disaster disaster performance HTTP and
Inbound /
on the TCP recovery Any recovery 80, 443 reverse proxy server. It is
outbound
server network / network / used for accessing the
server server OMC via a browser.
management manage-
network ment
network

Version: A/02 99
UMC² Unified Management Control Centre V1R5 Product Description (PON)

Table B-3 Ports Used by the Server's Internal Processes (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
IP segment 9876 RocketMQ-Nameserver.
IP segment of of the 10909 to
RocketMQ-Broker.
Internal the server server 10912
communi- cluster cluster
cation disaster disaster
Inbound /
among TCP recovery Any recovery
outbound Port used for
value- network / network / 26500 to
communication among
added server server 26999
web app services.
services management manage-
network ment
network
IP segment
IP segment of of the
the server server Port used for time
Time cluster cluster synchronization among
synchroni- disaster disaster servers. Time of Web
Inbound /
zation UDP recovery Any recovery 123 servers should be
outbound
among network / network / synchronized with that of
servers server server active nodes on the
management manage- UMC².
network ment
network

Table B-4 Ports Connecting the Server and the OSS

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
FTP port used for
20, 21 transferring data files to a
northbound interface.
SFTP port used for
transferring data files
North- 22
securely to a northbound
bound Northbound
Inbound TCP OSS IP Any interface.
common server IP
FTP service port used for
service
10201 transferring PAS
performance data.

Specified data port range

28001 to
in FTP passive transfer
29000
mode.

100 Version: A/02

 Appendix B Service Ports

Table B-4 Ports Connecting the Server and the OSS (Continued)

Firewall Source IP/ Source Sink IP/

Direction Protocol Sink Port Description
Rule Segment Port Segment
Activemq listening port,
61616 used with a northbound
interface.
SNMP service port. It
SNMP Inbound / Northbound can be configured and
UDP OSS IP Any 161 to 162
interface outbound server IP modified (without
conflicts) as needed.
3075 to
CORBA bus service.
3080
TMF814-compliant
CORBA Northbound CORBA interface, used
Inbound TCP OSS IP Any
interface server IP by the IceBox process
23075
corresponding to
unmnbi_corba_cmcc_-
main.
TL1 interface used by the
3333 to IceBox process
3337 corresponding to

TL1 Northbound unmnbi_tl1_ctc_main.

Inbound TCP OSS IP Any
interface server IP Mobile access TL1
4000
interface.
6000 Project TL1 interface.
9000 Private TL1 interface.
8001 to
Web service port.
8005
WebSer-
Northbound Port listening to
vice Inbound TCP OSS IP Any 8011
server IP operation services.
interface
Port listening to httpd
8020
services.
Socket Northbound 31232 to
Inbound TCP OSS IP Any Socket service ports.
interface server IP 31272

Version: A/02 101

 Appendix C Abbreviations

CPU Central Processing Unit

DCC Data Communication Channel

DCN Data Communication Network
EMS Element Management System

FTP File Transfer Protocol

GE Gigabit Ethernet

GNE Gateway Network Element

ICMP Internet Control Message Protocol

IP Internet Protocol
International Telecommunication Union-
ITU-T
Telecommunication Standardization Sector
NE Network Element
NMS Network Management System

NTP Network Time Protocol

NETCONF Network Configuration Protocol

OMC Operations Maintenance Center

OTDR Optical Time-Domain Reflectometer

OAM Operation, Administration and Maintenance

OSS Operation Support System

REST Representational State Transfer

SLA Service-Level Agreement

SDN Software-Defined Networking

SNMP Simple Network Management Protocol

TCP Transfer Control Protocol

TL1 Transaction Language 1

TE Traffic Engineering

TMN Telecommunications Management Network

UDP User Datagram Protocol

VLAN Virtual Local Area Network

XML Extensible Markup Language

102 Version: A/02